Just a guess Rob, but maybe a little cleanup of your job tables would
help.
Maybe try
CHGIPLA CHKJOBTBL(*ALL)
or
CHGIPLA CHKJOBTBL(*ALL) CPRJOBTBL(*ALL)
And check (and change back) after the next IPL.
Could be a spool file object was damaged and consequently removed and the
job table was never updated. If you had an abnormal IPL at any point, the
"CHKJOBTBL" would have run as default, but if not, it is never checked.
The CPRJOBTBL is just a nice "100,000" mile tune-up option (your milage
may vary).
-----midrange-l-bounces@xxxxxxxxxxxx wrote: -----
To: midrange-l@xxxxxxxxxxxx
From: rob@xxxxxxxxx
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Date: 07/09/2007 09:14AM
Subject: A job that just won't die...
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.
Rob Berendt
--
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com
midrange.com
