Re: SavSys21/power failure/pwrdwnsys *immed

If so, the answer is clear.
1. CL to change the values from standard to restricted state needs.
2. CL to run after the backup to revert to normal operations.

We had a one second power failure blip that caused our system to do a pwrdwnsys

*immed with no ipl restart during an unattended GO SAVE option 21 routine.

That wrecked my weekend.

We have a CL that runs constantly in QCTL that monitors the msg queue specified

in the system value QUPSMSGQ.  In this way we get complete control of our

system during a power failure. We modified some CL we got from IBM Boulder for

this purpose.  It works fine.  We can send messages, ignore short power blips,
take the system down in a controlled way, etc. using this CL.

The above problem occurs because the SavSys21 ends the monitor program when it

takes the system into a restricted state even though its running in QCTL. When

the one second power blip occurs, the system discovers that the msg queue
specified in QUPSMSGQ is NOT being monitored (true) and so causes a pwrdwnsys
*immed.

How can the UPS be monitored during a SavSys12?

Jerry Draper
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.