I need help with utside for MAX for OS/2 please.

I used to know how to do this with OPUS and a utility for DOS under QEMM,
but now need to enable this for MAX under OS/2.  The Sysop menu for MAX has
an OUTSIDE option which is supposed to let the Sysop drop to the system and
then return.  I've reached a point at one site where I need to be able to
remotely log in to a system which has failed in another completely
different OS/2 telecommunications system operation and hard reboot the
entire box from afar for debugging purposes.  Driving back and forth fifty
miles to do this is not acceptable.

Long ago I've set remote systems to come back through the reboot to
whatever the desired application mix needs to be.  And there is a
reasonably safe way to exectute a reboot with the Gamma Tech Utilities
REBOOT.EXE per my research at this.  REBOOT.EXE performs an orderly
shutdown and the then equivalent of  which brings this
box, including the BINK/MAX operation back up at square one, including the
other communications applications too.

When the other remote applications are jammed, I can still get to the
Bink/Max line and  .. could .. drop to the system with utside.

I've tried this with a local login.  I can then execute a batch file or the
REBOOT utility at that point and get the entire box back including the
jammed other communications applications if I am locally at the site on a
local login.  But I can't call the system remotely over a phone line and do
this.  From a remote access operation the utside Sysop menu jams
the box on the Bink/Max side as well and all is lost.  Hi ho, hi, ho, it's
fifty miles we go, gloom.

Is this a DOORWAY sort of deal?  What do I need to do with the MAX setup to
enable this from a remote login?  In OPUS I used to also be able to do this
with the interesting but very dangerous total remote command language which
was built into OPUS .. but that's aother story too.

As an alternative, there used to be a DOS utility you could use with QEMM
that would bootstrap monitor a modem port.  If it detected a phone line
ringing say 20 times without answer, it would then execute another serial
port line state change, yanking DTR or whatever.  You could use that state
change to pull a relay which would do a button reboot.  That's *NOT* the
way to shut down an errant OS/2 system with dirty byte re-romp through
CHKDSK and so on.  But one might be able to take that signal on a more
civiizied path and write a REXX script or other small custom program which
would yank GTU's REBOOT chain as well.

Any suggestions would be appreciated.


--> Sleep well; OS/2's still awake! ;)

Mike {at} 1:117/3001

--- Maximus/2 3.01