I work with the OPS/MVS Team here at CA. You are correct that the error you're receiving occurs when you've reached the maximum messagenum allowed in an OPSLOG - resulting in wrapping of the log. This can be confirmed by entering the OPSLOG and issuing a 'D DATE TIME MSGNO'. once entered, scroll to the top of the OPSLOG and record the number. Then, scroll to the bottom. The lower number should be higher than the top.
If you define a new OPSLOG and utilize the OPS3445O sample rule in the OPS CCLXSAMP sample directory, you can prevent the OPSLOG from wrapping and avoid a recycle of OPS.
Hope that helps,
Justin