|
Does CL have something like RPG's %shutdown (or whatever that is)?
Therefore, if you did a controlled shutdown the cl program could check for
that upon return.
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: Paul Therrien <ptherrien@xxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 01/03/2013 04:13 PM
Subject: RE: PWRDWNSYS in CL program
Sent by: midrange-l-bounces@xxxxxxxxxxxx
I don't think it will.
Or it really doesn't matter in the case of doing a PWRDWNSYS *IMMED.
Perhaps you want to issue the PWRDWNSYS *IMMED from the main program.
Paul
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jeff Crosby
Sent: Thursday, January 03, 2013 3:05 PM
To: Midrange Systems Technical Discussion
Subject: Re: PWRDWNSYS in CL program
I'm reevaluating my entire power handling program(s).
The main power handling program, once it's gotten a CPF1816, meaning power
is out, calls a subprogram to do the bulk of the work and decision making.
If that subprogram receives a message of a weak battery, it does a
PWRDWNSYS *IMMED, sets parameter &RETURN to "Y" and returns to the main
program.
The main program, seeing the "Y" returned to it, does a DLCOBJ on the
message queue it's been monitoring and ends itself. I was just wondering
if it ever even would get back to the main program.
On Thu, Jan 3, 2013 at 3:30 PM, <rob@xxxxxxxxx> wrote:
if you NEED it to go on, you could try delayed with a small delay.
Most of the time I will do
PWRDWNSYS OPTION(*CNTRLD) DELAY(120) RESTART(*YES) DSPJOBLOG
OUTPUT(*PRINT) SIGNOFF *LIST after I've already ended to a restricted
state. Stays running to either
1 - Two minutes has past
2 - I execute the SIGNOFF *LIST
Getting ready to IPL a new lpar...
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: Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 01/03/2013 03:22 PM
Subject: PWRDWNSYS in CL program
Sent by: midrange-l-bounces@xxxxxxxxxxxx
If a PWRDWNSYS *IMMED is issued in a CL program, does the CL program
stay on that statement until that job is bombed? Or does it start the
power down sequence and then move on?
If someone wants to test it today and let me know, that would be
swell. :)
Thanks.
--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com
The opinions expressed are my own and not necessarily the opinion of
my company. Unless I say so.
--
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.
--
Jeff Crosby
VP Information Systems
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com
The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
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.
--
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.
As an Amazon Associate we earn from qualifying purchases.
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.