RE: Job ran halfway thru, then vanished except for 2 QPDSPJOB spool files in QEZDEBUG.

Jim,

Oddly enough, this process, afaik, is setup so the program and job will
keep executing, as you point out.

And, this process used to be submitted, back in the day, but it was decided
to make it interactive and train the user to always stay at the screen
until the process was finished. What used to happen was it would crash
in the evening, but we wouldn't know until the next day.

I'm told the EOD process used to have problems several times a week.

With improvements, that is down to maybe once or twice a month.

Thanks,

John

<snip>
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
</snip>