RE: probably dreaming but...

If you use *DETATCH you will no longer be able to search by job (since the 'job' as such is no longer in the system); you'll have to know which output queue has the joblogs you're looking for. And then search the queue looking for the file with the right date and then the right job...

One thing to spread out the joblogs- we assign a different joblog output queue for each day of the week (and 1 for weekends). So today's joblogs will be in output queue JOBLOGFR.


Paul E Musselman
PaulMmn@xxxxxxxxxxxxx

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark S Waterbury
Sent: Thursday, March 08, 2018 5:34 PM
To: midrange-l@xxxxxxxxxxxx
Subject: Re: probably dreaming but...

Don,

If that system is at least on V5R4 or above, there is a relatively new
system value that might help -- QSPLFACN -- Spool file action.  Here is
the help text for that system value:

Spooled file action - Help

 *KEEP       When the job ends, as long as at least one spooled file for
             the job exists in the system auxiliary storage pool (ASP 1)
             or in a basic user ASP (ASPs 2-32), the spooled files are
             kept with the job and the status of the job is updated to
             indicate that the job has completed.  If all remaining
             spooled files for the job are in independent ASPs (ASPs
             33-255), the spooled files will be detached from the job and
             the job will be removed from the system.

 *DETACH     When the job ends, the spooled files are detached from the
             job and the job is removed from the system.

Detach may be what you are looking for ... the spool files remain, but
the "job table" entries are freed up much sooner. This is especially
important for system that run many, many jobs per day.

Hope that helps,

Mark S. Waterbury