Jon,
It's not a cure all for *NOLIST. If *NOLIST would not have gone to a
spool file then *NOLIST would not go to a "pending" job either. So I
imagine it shouldn't take up more than having the spool file would.
What it is a cure all for is people who do a WRKSPLF and get anal about
the spooled joblogs and delete them.
WRKJOB
Job: ROBHQ1 User: ROB Number: 746831
SIGNOFF *NOLIST
Sign back on
WRKJOB 746831/ROB/ROBHQ1
Job 746831/ROB/ROBHQ1 not found.
WRKJOB
Job: ROBHQ1 User: ROB Number: 750266
SIGNOFF *LIST
Sign back in
WRKJOB 750266/ROB/ROBHQ1
1. Display job status attributes
Status of job . . . . . . . . . . . . . . . : JOBLOG PENDING
4. Work with spooled files
(No spooled output files)
10. Display job log, if active, on job queue, or ***PENDING***
...
SIGNOFF *LIST
136 - RTVJOBA CURUSER(&USER)
140 - RETURN
Job 750266/ROB/ROBHQ1 ended on 04/16/09 at 11:17:50; .032 seconds used;
end code 0 .
(Note: The RTVJOBA & RETURN are from a command exit point program that
narcs on users with certain authority.)
And what's a little dasd among friends?
DSPSYSSTS
System ASP . . . . . . : 5433 G
% system ASP used . . : 58.8224
So I've got 90 disk arms and probably 36 of them are available. (I know
they're balanced and that's not really how it works.)
Rob Berendt
As an Amazon Associate we earn from qualifying purchases.