GH> where:
GH> /a - shutdown after xxxx seconds
GH> /d - shutdown on YYYYMMDD (Year, Month, Day)
GH> /t - shutdown on HHMM (24 hour format)
GH> /b - reboot after shutdown has completed
GH> /? - show a help screen
GH> SHUTDOWN without options will shutdown the system immediately
GH> You cannot use the /a option in combination with /d
GH> and/or /t. Command line parsing is case sensitive so
GH> you should use /a instead of /A.
I sniffed it out and picked it up off OS2site.
In raw form it works on this box from which I'm posting these replies which is
MCP2 XRC05 level. And Herbert, yes I do have a paid for eCs 1.2r here, but not
installed as there are serious reasons I haven't been able to move to eCs with
hundreds of thousands of files and stuff on all the machines which absolutely
create a ZOO with any form of migration from Warp4 in eCS.
So what I did was pick off SHTDWN16.ZIP off the site above. Then after
verifying that it does work and doesn't seem to trash any open applications on
this system I write a REXX script file. Put a complete ID and password setup
into that REXX script file. That gives me something from which I can call into
the somewhat jammed HyperHost at this remote site, pop this from the still
totally working Bink/MAX system there. I can thence, from a secured
standpoint, in theory, force this remote reboot there. That site, already set
up to come back up fully fuctional with the exact desired applications running
from a cold boot, should be stable this way.
Now all I've got to do is wait until I get back out there miles and miles from
here to test it, see if it will work without this crazy not enough memory error
from a jam-me deal. The UPS system has enough to hold if up over 36 hours
without any power if needed. But a power off failure does this same thing that
the Remote Reboot does from HyperHost. So maybe I now have a way to avoid ride
time!
We'll see. Thank you both.
--> Sleep well; OS/2's still awake! ;)
Mike @ 1:117/3001
--- Maximus/2 3.01
* Origin: Ziplog Public Port (1:117/3001)
