MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » January 2013

Re: PWRDWNSYS



fixed

<snip>
Wouldn't it be documented somewhere that the
PWRDWNSYS *CNTRLD performs differently
from PWRDWNSYS *IMMED from a disk cache perspective?
</snip>

That's the million dollar question. If I look at the help on PWRDWNSYS
you see nothing of the sort. You do see that
Note: When *IMMED is specified while the system is operating under
auxiliary power,
or if the delay time specified in the Controlled end delay time (DELAY)
parameter ends while the system is under auxiliary power...
To me that sounds like six of one, a half dozen of another. Same thing.

Numerous types of powering down the system are discussed at
http://www-01.ibm.com/support/docview.wss?uid=nas161209687dac0128386256d630055b0b0
and only those performed by control panel functions are flagged as cache
hazardous.

http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/index.jsp?topic=/p7ed5/ared5exusesasfab.htm
just mentions pwrdwnsys and makes no differentiation between *CNTRLD and
*IMMED. PDF version available at
http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/ared5/ared5.pdf

In a hardware manual available at
http://pic.dhe.ibm.com/infocenter/powersys/v3r1m5/topic/arect/arect.pdf
says use *IMMED in talking about very general terms in starting/stopping.

And more searching at ibm.com for pwrdwnsys cache look like

PCI card
If you are installing 5580 or 5581, go to Type 5708, auxiliary-write cache
IOA for more .... When all jobs are complete, type pwrdwnsys *immed on an
OS/400 ...
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/rzame/rzamepci.htm


PCI Card V5R3 - IBM
If you are installing 5580 or 5581, go to Type 5708, auxiliary-write cache
IOA for more .... When all jobs are complete, type pwrdwnsys *immed on an
OS/400 ...
http://publib.boulder.ibm.com/infocenter/iseries/v5r3/topic/rzame/eng47451.pdf


So I'd love to see some IBM documentation that a *CNTRLD is better for
cache. Oh, sure, I strongly recommend bringing the system down to a
restricted state by first shutting down applications you know you have
controlled ways, like:
- ENDDOMSVR of domino servers
- Changing data queues for never ending programs which are written to
check them.
- Sending break messages to users imploring them to finish up and sign
off.
And then after that running
ENDSBS SBS(*ALL) DELAY(300)
and after you receive the message the system ended to restricted state
PWRDWNSYS *CNTRLD DELAY(120)
SIGNOFF *LIST
I do agree that *CNTRLD does allow applications that are written to check
for system shutdown to shut down more gracefully, but I'm not sold that it
does a magical job on cache.


Rob Berendt





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact