Previous Topic: Automate Journal OffloadNext Topic: Practices for Monitoring and Managing Your Operation


Automate Log Offload

Use the Write-to-Operator exit (WTOEXIT) to automate the offloading of log information.

Business Value:

This practice avoids processing delays caused when a CA IDMS system must wait for space in the log area.

Additional Considerations:

A CA IDMS central version uses its log area to record runtime events such as task failures, configuration changes and resource shortages. The log may also be used to record statistics for performance monitoring and chargeback purposes. If its log area becomes full, a central version must wait until the ARCHIVE LOG utility is executed to archive the information and reclaim space in the area. To avoid processing delays, it is critical to run this utility in a timely fashion.

A central version has a single log area. As the log fills CA IDMS issues DC050001 messages indicating the percentage of the area that has been used. Usually an operator must respond to this message by submitting a job to offload the log information. You can eliminate the need for operator intervention and ensure immediate archive job submission by using a Write-to-Operator exit routine. The WTO exit intercepts and reviews the message to the operator and responds by automatically submitting a job to offload the log.

A sample WTO exit module called WTOEXIT is assembled and linked during CA IDMS configuration. It looks for DC050001 messages. Each time one is encountered the exit submits the contents of the file identified by a PLOGJOB DD statement that must be included in your startup JCL. To use the sample WTOEXIT, specify the load module name as a startup parameter to your central version.

More Information:

For information about the WTOEXIT user exit and sample routines, see the CA IDMS System Operations Guide.