Re: An old 'mystery job'

[CRPence <CRPbottle@xxxxxxxxx>]

On 1/3/11 2:07 PM, DrFranken wrote:
> <<SNIP>>
>
> On this device WRKJOB DSP020604 came up with only one job, no biggie
> as it's been a holiday and one job does in fact mean the device is
> still used. Or does it? The job is dated 10/29/2005 and its status
> is *OUTQ. OK that's a long time ago so let's just see what output it
> has waiting. So I check WRKJOB option 4 and, there is nothing there!
>
> Has anyone seen this? A job still in the system through more than 5
> years dozens of IPLs an O/S Upgrade (to V454) with no spooled files.
>
> I'm afraid a RCLSTG may be in our future here....

  Using RCLSTG to fix one anomaly is generally not a preferable option. 
 Probably better to use a feature(s) intended on resolving such an 
issue more directly.  I believe the ENDJOB feature can provide 
resolution for that scenario by using the parameters to remove all spool 
files and prevent logging for the job.  Even without the ability of 
ENDJOB to effect removal, there are also IBM service\support tool(s) 
that should be able to resync the work control block job table and spool 
control block tables; I do not recommend calling some program alluded to 
effect such correction, just because some reference on another similar 
issue was made in another message\post.

  I would suggest to first attempt the appropriately modified [i.e. 
corrected JOB() spec] CL request to:

 ENDJOB JOB(######/TheUsrPrf/DSP020604) OPTION(*IMMED)
   SPLFILE(*YES) LOGLMT(0) ADLINTJOBS(*ALL)

Regards, Chuck