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



rob@xxxxxxxxx wrote:

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:

I regularly use DELAY() to give system code time to do its clean-n-neat shutdown work rather than to let 'applications' shutdown nicely. I.e., I rarely expect that some everyday application code path is going to poll for shutdown status; but I _do_ expect things like the Mail Server Framework or whatever to be very well behaved in that respect.

If it so happens that a Payroll app or some app based on stored procs or whatever handles system shutdown nicely, so much the better.

PWRDWNSYS doesn't matter quite so much to me because the "system" is generally already ended when PWRDWNSYS is executed. But adding DELAY() rarely makes a lot of difference there since I also signoff right after the command is entered. The signoff ends the last job, so the delay period actually ends when the console job ends, not two minutes later.

Tom Liotta


As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.