× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




Have never done anything other than an *Immed (after ending all subsystems,
etc.). I've never really run into anyone that did otherwise (CEs,
consultants, admins), although what you're saying makes sense!





"Pete Massiello"
<pmassiello-ml@it
echsol.com> To
Sent by: "'Midrange Systems Technical
midrange-l-bounce Discussion'"
s@xxxxxxxxxxxx <midrange-l@xxxxxxxxxxxx>
cc

01/12/2008 02:58 Subject
PM RE: Controlled versus immediate.


Please respond to
Midrange Systems
Technical
Discussion
<midrange-l@midra
nge.com>






I NEVER do a PWRDWNSYS *IMMED, I always delay using a controlled end of at
least 30 to 60 seconds. Just figures it gives the system time to close
everything properly and complete any I/Os before shutting down.

JMHO

Pete

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, January 11, 2008 2:00 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Controlled versus immediate.

Been suggested that I replace using
ENDSBS *ALL *IMMED
with
ENDSBS *ALL *CNTRLD DELAY(120)
That I can understand because of the .0005% of programmers who actually
use the shutdown op code or check for that particular status when doing an
i/o or something.

It was also suggested that I change
PWRDWNSYS OPTION(*IMMED) RESTART(*YES *FULL) IPLSRC(B)
to
PWRDWNSYS OPTION(*CNTRLD) DELAY(120) RESTART(*YES *FULL) IPLSRC(B)
If I've already done the ENDSBS, and waited for the appropriate message in
QSYSOPR, that what's the benefit?

Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.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.




--
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.


_____________________________________________________________________________

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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.