|
How is your QUPSDLYTIM system value set? The way the help text for the value reads is that it only cares about the monitored/unmonitored status of the monitorong message queue if the system value is set to *NOMAX. If you're wanting the notification of the power change and a chance to handle the shutdown manually (or programatically) while your program is running rather, you might want to look at setting the value to the maximum number rather than *NOMAX. That way the system should always wait the maximum amount of time before doing a powerdown on it's own (99999 seconds or 27+ hours). We desired the notification aspect of the monitoring cable (monitoring program sends alerts to our pager), but didn't ever want the system to power down on it's own. We chose the 99999 seconds over *NOMAX because of situations we could foresee with the notification message queue being unallocated. I'm thinking that the 99999 seconds value should cover the situation you ran into also. I think the only condition that should drop us quickly without control at this point is if we are on no utility power (batter mode) and the UPS sends a low battery signal while on battery. Jerry Draper <midrangel@trilos oft.com> To Sent by: midrange-l@xxxxxxxxxxxx midrange-l-bounce cc s@xxxxxxxxxxxx Subject SavSys21/power failure/pwrdwnsys 11/28/2005 06:01 *immed PM Please respond to Midrange Systems Technical Discussion <midrange-l@midra nge.com> 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. _____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com _____________________________________________________________________________ ForwardSourceID:NT000336BE _____________________________________________________________________________ Scanned by IBM Email Security Management Services powered by MessageLabs. For more information please visit http://www.ers.ibm.com _____________________________________________________________________________
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.