Anything in QHST (DSPLOG) or QAUDJRN (DSPJRN) for the job in question?

Gary Monnier

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of John Rusling
Sent: Wednesday, May 02, 2012 12:30 PM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: Job ran halfway thru, then vanished except for 2 QPDSPJOB spool files in QEZDEBUG.

We have an interactive, end of day job that the user keys a date into, then enter's to run (interactively) some CL's and RPGs.

Yesterday the job was started, but never finished. We talked to the user this morning who declared that nothing unusual happened when she ran it yesterday.

I can't find anything, anywhere in the system to show how/why this happened.

If our in-house log file hadn't revealed this, we would have had no clue that anything was out of the ordinary ...

No qsysopr message was generated, the qezdebug spool files merely contain some job stats info. No escape msg info or anything like that.
Dsplog command doesn't reveal anything.

We've resolved that an admin or developer accidentally wacked it
the user did 'something' not normal, somehow to end it.
(Although, we don't give them that much power)

Does this sound familiar to anyone, has this happened to you before, or anyone have a hint or insight?

We've moved on but... it's bugging me and i just thought i'd ask.


John B
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

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by 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].