|
I looked over the TAATOOLS specs and they are similar. Germane question is: When running a SavSys21 and the system goes into a restrictive state my UPS monitor pgm is ended so I have to fly blind until the SavSys21 is complete to avoid the pwrdwnsys *immed situation. Does TAATOOLS get around this issue? Jerry Quoting Al Barsa <barsa@xxxxxxxxxxxxxxxxxxx>: > > Hi, > > You may find this tool helpful: > > http://www.taatool.com/document/L_upsmon.htm > > You will note that the documentation for coding to these system values had > both logic and syntax errors in all releases before V5R3. I haven't > checked V5R3 yet. > > Al > > Al Barsa, Jr. > Barsa Consulting Group, LLC > > 400>390 > > "i" comes before "p", "x" and "z" > e gads > > Our system's had more names than Elizabeth Taylor! > > 914-251-1234 > 914-251-9406 fax > > http://www.barsaconsulting.com > http://www.taatool.com > http://www.as400connection.com > > > > > Al Mac > <macwheel99@sigec > om.net> To > Sent by: Midrange Systems Technical > midrange-l-bounce Discussion > s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx> > cc > > 11/28/2005 06:46 Subject > PM Re: SavSys21/power > failure/pwrdwnsys *immed > > Please respond to > Midrange Systems > Technical > Discussion > <midrange-l@midra > nge.com> > > > > > > > Is there a collection of settings in Work System Values, other than your > standard one, that permits the UPS to protect us if there is a short > duration power outage during a backup, or other restricted state scenario? > > 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. > > I have noticed that there is other stuff that is stopped or delayed during > restricted state such as GO POWER and GO CLEANUP > > >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. > > > > -- > 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-2025 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.