|
midrange.com
According to the help, it will do the auto shutdown when not allocated only
with the *NOMAX setting. Because of this (at least for my purposes), the
99999 seconds is a MUCH better setting.
"Chris Bipes"
<chris.bipes@cros
s-check.com> To
Sent by: "Midrange Systems Technical
midrange-l-bounce Discussion"
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc
11/29/2005 10:47 Subject
PM RE: SavSys21/power
failure/pwrdwnsys *immed
Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>
You are not sending a message but putting the message queue into break
mode, thus allocating the message queue. QSYSOPR is placed in to break
mode by the Save21 program. This does work, cause I have done it before.
If the message queue is allocated, the system does not start a power down
immediately upon signal of power failure. It basically puts a message in
to the UPSMSGQ and lets your program handle the power failure. If you have
a UPS monitoring program that does not allocate the message queue, your
system will shut down immediately. In fact I am willing to bet that the
system does not know if a server job or interactive job has the message
queue allocated, just that it is.
Chris Bipes
Information Services Director
CrossCheck, Inc.
707.586.0551, ext. 1102
707.585.5799 FAX
Chris.Bipes@xxxxxxxxxxxxxxx
www.Cross-Check.com
NOTE: This e-mail may contain restricted confidential information and
privileged material for the sole use of the intended recipient. Any review
or distribution by others is strictly prohibited. If you are not the
intended recipient, please contact the sender and delete all copies.
** Sent from OWA **
________________________________
From: midrange-l-bounces@xxxxxxxxxxxx on behalf of Al Barsa
Sent: Tue 11/29/2005 5:49 PM
To: Midrange Systems Technical Discussion
Subject: RE: SavSys21/power failure/pwrdwnsys *immed
My hunch is that you cannot send a message in a restricted state. I
certainly have experimented with this during my save-while-active testing,
and it failed.
_____________________________________________________________________________
Scanned by IBM Email Security Management Services powered by MessageLabs.
For more information please visit http://www.ers.ibm.com
_____________________________________________________________________________--
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.
ForwardSourceID:NT000338AA
_____________________________________________________________________________
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-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.
