RE: A job that just won't die... -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

From: rob@xxxxxxxxx

We only keep spool files for so many days - without exceptions. So, when
I did a WRKJOB RHI101C and found this I was a little stunned:
Entered
Job User Number Type -----Status----- System
RHI101C JONI36 814775 BATCH OUTQ 11/12/04
RHI101C MARILK70 814778 BATCH OUTQ 11/12/04

So I select each job and took option 4. Work with spooled files. (No
spooled output files). Then I took option 41. End job. I changed the
defaults so that it looked like this:
ENDJOB ?*JOB(814775/JONI36/RHI101C)
OPTION(*IMMED)
SPLFILE(*YES)
LOGLMT(0)
However, there are STILL there.
Trust me, we've IPLed, upgraded the OS, etc, since then.

Old brain cells are firing, Rob, so take this with a grain of salt, but I
seem to remember somebody having this problem and it didn't go away until
they did a RCLSPLSTG. For some reason the spooled file got "stuck" during
the delete process: they weren't there to be deleted, but they stuck around
in spirit, kinda like Bruce Willis in The Sixth Sense.

Maybe your job sees dead print files.

Joe

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

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.