Past OPSLOG processes issued a OPS3445O OPSLOG message number approaching "wrap" condition when the OPSLOG DIV dataset was about to fill up with event messages. Customers needed to perform an archive of the data to a dataset to continue writing to the current OPSLOG.
Does the new OPSLOG archival process available with release 12.2 provide any relief for the situation where message OPS3445O OPSLOG message number approaching "wrap" condition is issued? Or, do we still need to handle this condition ourselves?
CA OPS/MVS Event Management and Automation release 12.2
The new Archive process for OPSLOG is a started task that creates an OPSLOG archive GDG dataset from the current OPSLOG triggered by your choice of time of day or number of event messages. This method should prevent the wrap condition by the frequency of the archive if the GDG dataset is available.