Best Practices for Managing Job Logs on IBM i
Note: This is publication is now archived. For reference only.
Many environments keep spooled job logs for some period of time for diagnostic purposes. However, keeping job logs, whether as spooled files or in a pending state, consumes a permanent job structure for each job. On some of the largest IBM i installations, these job logs are the major reason for large numbers of jobs on the system. The actual number of active jobs is relatively small compared to the total number of jobs on the system.
At this time, IBM does not increase the number of jobs on the system. Detaching spooled files is one method you can use to manage large numbers of spooled files.
In this technote, we provide some best practices on managing job logs.
Dawn May, Angela Newton, Mike Russell, Dan Tarara, and Kevin Vette
IBM Rochester Development Team
The material included in this document is in DRAFT form and is provided 'as is' without warranty of any kind. IBM is not responsible for the accuracy or completeness of the material, and may update the document at any time. The final, published document may not include any, or all, of the material included herein. Client assumes all risks associated with Client's use of this document.