Re: PWRDWNSYS - Trivia

[Chris.Whisonant@xxxxxxxxxxxxx]

Pretty certain that it cannot be stopped. However, if you're worried about
that happening you have a few options:

1. chgcmddft - change DELAY from 3600 to *NOLIMIT. This will only power
down the system after the last job completes. However, in a controlled end
no new jobs are allowed. Not necessarily a good option, but gives you ample
time to keep the system up and let jobs end normally. Just gently get all
users to sign off...

2. It looks like IBM is getting with the program in V5R2! - I'm looking at
the V5R2 infocenter and in the syntax there appears to be a new parameter -
CONFIRM. I'm not sure what the default is, though:

CONFIRM
       Specifies whether the request should be confirmed before the system
       is powered down.


       *ENVVAR: The value in environment variable QIBM_PWRDWNSYS_CONFIRM is
       used to determine whether the request should be confirmed. If the
       value is set to *INTERACT, *YES, or *NO, the action described below
       for that value is taken. If the environment variable is not defined
       or not set to one of these values, then there is no confirmation.
       System initiated power downs do not use the environment variable.


       *INTERACT: A confirmation panel is displayed when the PWRDWNSYS
       command is issued in an interactive job. There is no confirmation
       when the PWRDWNSYS command is issued in a non-interactive job.


       *YES: A confirmation panel is displayed when the PWRDWNSYS command
       is issued in an interactive job. An inquiry message is sent to
       QSYSOPR when the PWRDWNSYS command is issued in a non-interactive
       job.


       *NO: There is no confirmation when the PWRDWNSYS command is issued

3. Have an exit program for QIBM_QWC_PWRDWNSYS exit point.




Chris Whisonant
Comporium
IBM Certified Specialist
(803) 326-7270
mailto:chris.whisonant@comporium.com