- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- unable to shutdown with a batch job
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2010 08:38 AM
тАО10-25-2010 08:38 AM
$ type mydetached.com
$ set verify
$ run sys$system:loginout.exe /detatched /input=sys$manager:myshutdown.com -
/output=opa0:
$ type myshutdown.com
$ set proc/priv=all
$ set verify
$ run sys$system:sysman
show environment
shutdown node/minutes=0 /reason="test shutdown"
Here's the output..
$ @mydetached
$ set verify
$ run sys$system:loginout.exe /detatched /input=sys$manager:myshutdown.com -
/output=opa0:
%RUN-S-PROC_ID, identification of created process is 00000247
Console output...
Monday
October 25, 2010
10:47:03
$ run sys$system:sysman
show environment
%SYSMAN-I-ENV, current command environment:
Local node only
shutdown node/minutes=0 /reason="test shutdown"
%SYSMAN-I-SHUTDOWN, SHUTDOWN request sent to node ADAS21
SYSTEM job terminated at 25-OCT-2010 10:47:04.26
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2010 08:53 AM
тАО10-25-2010 08:53 AM
Re: unable to shutdown with a batch job
Dan
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2010 09:46 AM
тАО10-25-2010 09:46 AM
Re: unable to shutdown with a batch job
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2010 12:27 PM
тАО10-25-2010 12:27 PM
Re: unable to shutdown with a batch job
I'm not sure what abrsvc means either. From your log file the shutdown request has certainly been sent - I don't know why it didn't act.
I'd suggest you send the log to a file, rather than OPA0:, and perhaps put a WAIT at the end to make sure stopping the process doesn't somehow block the shutdown.
I seem to recall a new feature specifically intended to allow a shutdown from BATCH, I thought it was the SYSMAN SHUTDOWN command!
Another option is to run SHUTDOWN.COM itself detached, or at least run your own procedure which invokes SHUTDOWN with appropriate parameters (see default SYSTEM LOGIN.COM for symbol definitions).
If all else fails, I've got some programs which will crash a system on demand, including some logic to synchronize crashing a number of cluster nodes simultaneously - we use it to simulate site failures.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2010 03:53 PM
тАО10-25-2010 03:53 PM
Re: unable to shutdown with a batch job
something else to try:
SYSMAN> SHUTDOWN NODE/MINUTES=1
maybe the SHUTDOWN/MINUTES=0 is done in the context of the current process? If you put in a delay, SYSMAN must fire up a detached process to do it for you.
(sorry, this isn't something I'm going to test for you... ;-)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2010 07:57 PM
тАО10-25-2010 07:57 PM
SolutionTo avoid having to create another command file for input to SYSMAN consisting of multiple lines, issue the SYSMAN SHUTDOWN command as a single line command.
Try this (and no, I've not tested it for you):
MYSHUTDOWN.COM
$ set noon
$ set proc/priv=all
$ set verify
$ shutdown0 := "mcr sysman shutdown node /min=0/noauto"
$ shutdown0
$ wait 00:10:00
$ exit
Of course, the final exit should never happen.
Cheers, Colin (http://www.xdelta.co.uk).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-25-2010 10:19 PM
тАО10-25-2010 10:19 PM
Re: unable to shutdown with a batch job
$
$! Script BATCHREBOOT.COM performs a system reboot from a detached process.
$! Not depending of the communication with the user.
$
$
$ if f$getjpi("", "mode") .eqs. "OTHER" then goto DETA
$
$ run sys$system:loginout/deta/proc=prov/uic=[system] -
/output=sys$manager:batchreboot.out-
/error=sys$manager:batchreboot.err-
/input=sys$manager:batchreboot.com
$ exit
$
$
$ DETA:
$ set veri
$ @sys$system:shutdown 0 Omstart yes no later yes none
Y
$
Kjell
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО10-26-2010 07:32 AM
тАО10-26-2010 07:32 AM