There are two options:
I. The administrator can reallocate a new OPSLOG DIV dataset in order to restart the numbering, and then cycle OPS to pick it up. A number greater than x'7FFFFFFF' (decimal - 2147483647) can not be recorded in OPSLOG, so you must allocate a new OPSLOG DIV dataset to restart the message numbering scheme. Look for the DEFDIV member in your hlq.CCLXCNTL dataset. Read the documented steps in the information header and review the statements of the member. It is the REXX program that you need to edit and run.
II. Follow the Best Practices recommendation to utilize multiple OPSLOG support where you can define multiple OPSLOGs when OPS starts up. Then we provide a sample rule: CCLXSAMP(OPS3445O)..that will monitor the current OPSLOG and automatically 'hot-swap' to another OPSLOG when it approaches a preset threshold of the 2 gig limit.