Re: Job ran halfway thru, then vanished except for 2 QPDSPJOB spoolfiles in QEZDEBUG.

I''ve not had experience at 7.1 with this, but have often seen interactive programs,
run from an iSeries Access for Windows session, where user X's out of screen,
the program & job will keep executing until it reaches the point of needing to
interact with the display (display results, change screen, any message handling that appears at bottom of screen, or even return to menu screen).
That usually creates a CPF "I/O" message. However, you have multiple activation groups, perhaps some exception error handling in the code.
If this does not require a screen - submit it (if the lights blinked out, you could have same effect)..
jim franz

----- Original Message ----- From: "John Rusling" <jrusling@xxxxxxxxxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>
Sent: Wednesday, May 02, 2012 5:44 PM
Subject: Re: Job ran halfway thru, then vanished except for 2 QPDSPJOB spoolfiles in QEZDEBUG.

Thanks Gary, Rob, Chuck,

I did get dsplog to reveal this -

CPF1164 00 COMPLETION Job 812082/UROPER/CNSRDC9 ended on 05/01/12 at 16:13:24; .889 seconds used; end code 0
CNSRDC9 UROPER 812082 QWTMCEOJ 0000 05/01/12 16:13:24.379108 UROPER


As the job is no longer in the system, because it "thinks" it ran normally
I can't do the dspjoblog against it as Chuck suggested but I did post the
spool files generated yesterday.

QPDSPJOB1 spool file -
http://code.midrange.com/e48c1a3d72.html

QPDSPJOB2 spool file -
http://code.midrange.com/d446885f24.html


John
(taking my thinking cap off now)
--
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.