Since every machine and it's applications are different IBM has chosen
(correctly in my view) to leave that to you.
You could always build an PWRDWNSYS exit program (QIBM_QWC_PWRDWNSYS) to
perform the functions the way you would like them done. Most of my
customers prefer to shut down applications "nicely" so that databases are
closed properly etc. As Pete indicated ALWAYS go to a restricted state
first then power down.
For those that like to power off the system (Using any manner you choose:
white button, HMC power off, literally pulling the plug) all you're doing is
corrupting the databases that actually run IBM i and then forcing the system
to attempt a recovery when it powers on. Most of the time that recovery
works, until it doesn't.
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Tuesday, January 17, 2017 6:49 AM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Leaving IBM i on vs. sleep mode and fire it up now and then
Since the steps needed for a proper power down are so critical, why hasn't
IBM coded these steps as part of the PWRDWNSYS?
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rob
Berendt
Sent: Tuesday, January 17, 2017 7:12 AM
To: Midrange Systems Technical Discussion
Subject: RE: Leaving IBM i on vs. sleep mode and fire it up now and then
That link is nice. It specifically says this about using the white
button:
<snip>
Caution: Do not use this function on a system that has a low or failed write
cache battery, as thousands of pages of disk storage can be lost.
This type of IPL will be marked abnormal and will incur significant IPL
recovery.
</snip>
The suggested steps are the following:
- Quiesce your user applications. Follow any suggestions from your software
vendors.
- ENDTCPSVR *MGTC
- ENDTCPSVR *CIMOM
- ENDTCP
- ENDSBS *ALL *CNTRLD DELAY(120)
- PWRDWNSYS OPTION(*CNTRLD) DELAY(120)
- DSPJOBLOG OUTPUT(*PRINT)
- SIGNOFF *LIST
Let me explain. If you do not end tcp first the ENDSBS will NOT kill all of
the tasks starting with the last couple of releases. This is documented.
This can cause issues for running tasks while you "thought"
you were in a restricted state.
Failing to end Management Central and CIMOM prior to ending TCP can cause
corruption. Been there, done that, have the scars.
When you use *CNTRLD there are flags set on the system and even your user
written applications can check for these and end in an orderly fashion.
Even RPG supports %shtdn: dou F3 or %shtdn Granted not all applications
code to these flags but allow those which do the opportunity to use that
time. After all some poor slob had to write that code, respect their
effort.
Yes you can enter a few quick commands after entering PWRDWNSYS; if you do
it controlled.
If you've already brought the system down into restricted state, and then
issue a PWRDWNSYS *CNTRLD then doing the SIGNOFF will kill the last
remaining job and cut the remaining delay off of your outage.
Either 7.3 or 7.2 added ABNENDDLY to the ENDSBS command. If you have a job
which will not end without using ENDJOBABN then the ABNENDDLY parameter will
automatically issue this after the requisite 10 minutes (that's a minimum,
you can override that with a longer delay on this command).
I've never messed with the ENDSBSOPT parameter on both ENDSBS and PWRDWNSYS.
I kind of like the CONFIRM parameter on the PWRDWNSYS command.
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept 1600 Mail
to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
From: "midrange" <franz9000@xxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 01/16/2017 10:41 PM
Subject: RE: Leaving IBM i on vs. sleep mode and fire it up now and
then
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>
Did I miss it or did no one check for an IBM doc on this?
http://www-01.ibm.com/support/docview.wss?uid=nas8N1016455
Depends on the size of your system
What you are running
Cache battery status
Pwrdwnsys *immed /*cntrld, or panel function or white button
Also - I work on a system with very large virtual opticals - we always do
ENDSBS *ALL first as Pete said (and that can be 10 - 15 minutes or more)
and then pwrdwnsys *cntrld...
Jim Franz
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Steinmetz, Paul
Sent: Monday, January 16, 2017 10:08 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Leaving IBM i on vs. sleep mode and fire it up now and then
< recommend ENDSBS *ALL (pick your time frame 30 or 60 seconds) before
issuing the PWRDWNSYS command.
I have found that some Java related jobs/tasks can take 120 to 180 seconds
to end.
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Pete Massiello - ML
Sent: Monday, January 16, 2017 7:28 PM
To: Midrange Systems Technical Discussion
Subject: RE: Leaving IBM i on vs. sleep mode and fire it up now and then
Not what you want to do. You are doing more of a controlled pull the plug
from the wall that way.
You are always better off shutting the machine down normally. Which
contrary to opinion is to bring the system to a restricted state from the
console, AND THEN issue the PWRDWNSYS command. I always tell my customers
only use the *IMMED when the building is on fire. You are better to let
the system come after all the jobs are ended, that is why I always
recommend ENDSBS *ALL (pick your time frame 30 or 60 seconds) before
issuing the PWRDWNSYS command.
Pete
Pete Massiello
iTech Solutions
http://www.itechsol.com
http://www.iInTheCloud.com
Office: 203-744-7854
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Bradley Stone
Sent: Monday, January 16, 2017 4:48 PM
To: Midrange Systems Technical Discussion
Subject: Re: Leaving IBM i on vs. sleep mode and fire it up now and then
I must have read something wrong a few years ago. I've had in my head
that it was doing some sort of suspend. You know how reading IBM docs
is..
haha..
So, on my 515 (V5R4) holding the power button down for 5 seconds (while
the display counts down) is the same as issuing PWRDWNSYS *IMMED? Seems
that way. :)
Brad
www.bvstools.com
On Mon, Jan 16, 2017 at 3:44 PM, Marc Rauzier <marc.rauzier@xxxxxxxxx>
wrote:
Le 16/01/2017 à 03:36, Richard Schoen a écrit :
Is there really such thing as sleep mode ?
It does exist for IBM i on Power Systems.
The name of this function is Partition Suspend and Resume. It was
provided by 7.1 TR2 and requires using VIOS.
When I did PWRDWNSYS on our old 515 the power supply the fans would
still
spin, but I didn't know there was a way to suspend via the white
button.
Regards,
Richard Schoen
Director of Document Management
e. richard.schoen@xxxxxxxxxxxxxxx
p. 952.486.6802
w. helpsystems.com
------------------------------
message: 3
date: Sun, 15 Jan 2017 10:17:10 -0600
from: Bradley Stone <bvstone@xxxxxxxxx>
subject: Leaving IBM i on vs. sleep mode and fire it up now and then
I have v7r3 development box (power 8) that I leave on all the time.
My question is with my older 515 running V5R4. I normally put it to
sleep by holding the power button. Then when I need to do some work
on it I fire it up.
This is normally about 2-5x a month.
Would it be better for the 515 machine to just leave it running? Or
is the sleep/wake cycle not a huge issue with this hardware?
Brad
www.bvstools.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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
http://amzn.to/2dEadiD
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
http://amzn.to/2dEadiD
--
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.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link:
http://amzn.to/2dEadiD
midrange.com
