So what do you get when you run DSPLOG JOB(812082/UROPER/CNSRDC9)? Any indication of what was running just before completion?
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Rusling
Sent: Wednesday, May 02, 2012 2:45 PM
Subject: Re: Job ran halfway thru, then vanished except for 2 QPDSPJOB spool files 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 -
QPDSPJOB2 spool file -
(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,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l