Re: CPF1001

[D.BALE@xxxxxxxxxxxxx]

Rob,

Actually, I _am_ able to IPL with PWRDWNSYS.  It's just that the CPF1001 gives
the perception that the system does not actually know whether the command
executed or not.  Perhaps the DELAY(3600) and the fact that there are still
active subsystems out there causes CPF1001; it will eventually execute, but
the job itself is ending *now*, and it ain't waiting to find out whether
PWRDWNSYS was successful.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952

-------------------- Original Message --------------------
Dan,

Sometimes there are jobs that will not die no matter what.  You can try
ENDJOB, ENDJOBABN, PWRDWNSYS, but sometimes you just have to IPL manually.
Before you do that try *IMMED on your PWRDWNSYS.  But if you can IPL with
PWRDWNSYS, (which looks like you can't) normally I set my panel to B and do
PWRDWNSYS *IMMED RESTART(*YES) IPLSRC(B).  I can understand not wanting to,
if you don't want to leave the A side, (you're riding a dinosaur into the
sunset and you don't want to mess with what is perceived to be working).





                    D.BALE@handleman.co

                    m                          To:     MIDRANGE-L@midrange.com

                    Sent by:                   cc:

                    owner-midrange-l@mi        Subject:     CPF1001

                    drange.com





                    10/03/00 09:52 AM

                    Please respond to

                    MIDRANGE-L









Submitted "PWRDWNSYS OPTION(*CNTRLD) DELAY(3600) RESTART(*YES) IPLSRC
(*PANEL)"
to batch with SCDDATE & SCDTIME specified.  Job started at the specified
time,
and the command was, in fact, actually executed, but got a weird message
immediatly following the PWRDWNSYS in the job log:

CPF1001    Escape                  20    10/01/00   06:00:01   ...
  Message . . . . :   Wait time expired for system response.

  Cause . . . . . :   The job was waiting for a response from a system job.
This
     message may occur if the related class object contains a DFTWAIT value
that
     is too small.  The requested function may or may not have been
processed.


Immediately following this message was the normal job completion message,
CPF1164.

Can anyone shed light on this?  I was really perplexed on the last
statement,
"The requested function may or may not have been processed."  That's pretty
scary.

Dan Bale
IT - AS/400
Handleman Company
248-362-4400  Ext. 4952
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---