RE: Job system values

I think I stated in that thread that I knew a vast majority of the total jobs were finished and were waiting disposition of the spool files.
We delete all spool files over 90 days old - no exceptions.
Not really having a performance issue at this time but we had some vouchers which were about to expire so we figured let's use them.

One performance issue we were having may have been exacerbated by some of these small values. We were having an issue that people using the old Client Access were effectively performing a denial of service attack on our machine because of constant retries. Instead of handling it at the server level IBM said we needed to patch each client. Which makes as much sense as leaving your door open with high end electronics clearly visible in a bad neighborhood and trying to educate all the neighbors on how to properly sing Kumbaya and respect your property.
BTW the patch helped.
Having a higher additional active job may have also helped.

I do like your comment on reviewing periodically. And that is something we gained by this performance review. However some general recommendations would be nice. One simple review would be to print system values and there is a comparison in that report between your values and IBM defaults. Perhaps with newer versions of the OS they changed defaults and one should be able to justify why you vary from the defaults?
Justification should have enough details to see if the justification is dated. For example "Based on performance evaluation we set these values to..." is not enough details while "Based on a performance evaluation on our B10 running OS/400 Version 1.2, running mainly BPCS V... we set these values to..."

Rob Berendt