OPSLOG wrap condition relief in OPS/MVS Event management and Automation
Article ID: 93260
Updated On:
Products
Issue/Introduction
Each message in the OPSLOG has a unique identifier named "message number". This number grows for the life of the OPSLOG dataset and spams the value of BROWSEMAX. It keeps growing until it reaches its maximum value of 2147483647.
When this happens the OPSLOG dataset becomes unusable.
Environment
OPS/MVS
Resolution
We recommend defining a secondary OPSLOG dataset and switch to this secondary dataset when the message number reaches 80% of its maximum value. At this time OPS/MVS issues the message OPS3445O.
We deliver a sample rule in the library CCLXRULS with name OPS3445O that is triggered by this message.
We also deliver a sample REXX program with the same name OPS3445O in the library CCLXSAMP.
The rule and the REXX in conjunction perform an automatic switch from the primary OPSLOG to the secondary and back to the primary when necessary. Before switching from one OPSLOG to the other, the programs resets the dataset that will become the new "live" OPSLOG.
Additional Information
Feedback
