retention period, archive logs (ARCRETN), storage management subsystem (SMS), log inventory, BSDS, recovery, recover log inventory, BSDS (bootstrap data set), bootstrap data set (BSDS)" /> Automatic archive log data set deletion

 

Automatic archive log data set deletion

We can use a DASD or tape management system to delete archive log data sets automatically. The retention period for WebSphere MQ archive log data sets is specified by the retention period field ARCRETN in the CSQ6ARVP installation macro (see the WebSphere MQ for z/OS System Setup Guide for more information). This value is passed to the management system in the JCL parameter RETPD.

The default for the retention period specifies that archive logs are to be kept for 9999 days (the maximum possible). We can change the retention period but ensure that we can accommodate the number of backup cycles that you have planned for.

WebSphere MQ uses the retention period value as the value for the JCL parameter RETPD when archive log data sets are created.

The retention period set by MVS/DFP's storage management subsystem (SMS) can be overridden by this WebSphere MQ parameter. Typically, the retention period is set to the smaller value specified by either WebSphere MQ or SMS. The storage administrator and WebSphere MQ administrator must agree on a retention period value that is appropriate for WebSphere MQ.

Note:
WebSphere MQ does not have an automated method to delete information about archive log data sets from the BSDS, because some tape management systems provide external manual overrides of retention periods. Therefore, information about an archive log data set can still be in the BSDS long after the data-set retention period has expired and the data set has been scratched by the tape management system. Conversely, the maximum number of archive log data sets might have been exceeded and the data from the BSDS might have been dropped before the data set has reached its expiration date.

If archive log data sets are deleted automatically, remember that the operation does not update the list of archive logs in the BSDS. We can update the BSDS with the change log inventory utility, as described in Changing the BSDS. The update is not essential. Recording old archive logs wastes space in the BSDS, but does no other harm.