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

> On 3/8/2018 4:56 PM, Don Brown wrote:

Whether they go to print or stay pending they are still in the system work
control block tables and included in the jobs in the system.

One system I look after has a large number of jobs in the system, well
large for a small system and this has resulted in the system managing 9
work control block tables which in turn when the system is busy results in
drops in SNMP reporting.

The next option is to copy the spool files to a database file and delete
them to reduce the number of jobs and thereby reduce the number of work
control block tables and hopefully stop the drop outs in SNMP reporting.

I am sure if I do some searching there will already be a utility that does
this ?

Thanks

Don Brown




From: "Rob Berendt" <rob@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Date: 09/03/2018 02:30 AM
Subject: Re: probably dreaming but...
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Oh you still have your job logs go to print. How quaint. We changed our
system value QLOGOUTPUT that they do not go to output queue but stay
pending instead.
https://code.midrange.com/b48ca0836c.html
See the parameter for table(qsys2.joblog_info('*')) to pick a different
job than the current one.

See also: WRKJOBLOG.

Rob Berendt