Re: probably dreaming but...

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