I've seen this on some system jobs in the past.
This may be normal in certain cases with certain jobs.
I think an IPL clears the issue.
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H. H. Lampert
Sent: Monday, June 09, 2014 8:14 PM
To: Midrange Systems Technical Discussion
Subject: So far, nothing's worked, Re: Job is in OUTQ status, but its spool files are all FIN . . . .
On 6/9/14 2:24 PM, Lance Gillespie wrote:
End the job *IMMED with Delete Spool Files *YES.
It will then tell you that there were no spool files you silly person,
but the job will be gone along with all the *FIN spool files.
It's all still there. And yet it thinks it's gone. Or maybe it's all gon, but thinks it's still there. Either way, it's bizarre.
Any other ideas?
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