Joblog considerations that can affect communications error recovery

You should consider whether to generate job logs when an error condition occurs and the active jobs are ended. Producing job logs can use considerable system resources, especially during error recovery in which many jobs end at one time. In this case, it may be better to not generate job logs. If you do not produce job logs, you will not have any data for analysis if something goes wrong. There is a trade-off to be made.

To configure your system so that job logs are not generated, do the following:

• Set the DEVRCYACN parameter to *ENDJOBNOLIST. There is also a QDEVRCYACN system value for ease of configuration.
  Note:
  The QDSCJOBITV system value determines when the unused disconnected jobs are ended.
• Change the job description (or the job itself through an initial program for the user profile) to LOGLVL(4 0 *NOLIST). With this description, the job logs are not generated if jobs end normally, but are generated if jobs end abnormally.
  Note:
  Disconnected jobs also use resources. The System Work Control Block Table can grow, which has other side effects. Do not disconnect from jobs to which you will never reconnect.

  If some of your users reconnect after a failure, however, the disconnect options can offer increased performance for them.

• For advanced configuration pages, see the Communications Configuration book.
• For more information about iSeries™ communications, see the Communications Management book.
• For system management pages, see the Work Management book.

For related information, see:

• Considerations for jobs that can affect error recovery
• Considerations for communications-related system values