|
Sounds like the best plan. Jerry Quoting Pete Massiello <pmassiello@xxxxxxxxxxxxxxxx>: > Why not run a program that right before you go into restricted mode and > end the UPS Monitor program, to set it to delayed some number of seconds, > so that during the SAVE21 it doesnt shut the system down during a quick > blip of power, only when it goes longer then your duration that you set > before going into restricted state. > > Pete > > ---------------------------- Original Message ---------------------------- > Subject: SavSys21/power failure/pwrdwnsys *immed > From: "Jerry Draper" <midrangel@xxxxxxxxxxxxx> > Date: Mon, November 28, 2005 6:01 pm > To: midrange-l@xxxxxxxxxxxx > -------------------------------------------------------------------------- > > > 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. > > > > > > > -- > 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. > >
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.