OPSMVS - OPS takes an ABEND X'000C3000' OPINBO+X43D4

Document ID : KB000050787
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

OPSMVS - OPS takes an ABEND X'000C3000' OPINBO X43D4 ?.When client attempts to get into OPSLOG they may receive the following error: 'Checkpoint processing suspended'.

Solution:

The error occurs as a result of the OPSLOG MSGID numbering scheme hitting the 2 gig limit.

This abend happens if the message number reached the maximum of 2 gig.
X'7FFFFFFF' or decimal 2147483647. You can check the BROWSECHECKNUM parameter. If the value is near 2147483647 then you have the same problem.
If this is the case then the only way to repair it is to reallocate a new OPSLOG DIV dataset to restart the numbering then cycle OPS to pick it up. A number greater than x'7FFFFFFF' (decimal - 2147483647) can not be recorded in OPSLOG, thus you must create a allocate a new DIV dataset to restart the message numbering scheme...sample jcl in OPS.CNTL(DEFDIV). This has no effect on the SYSCHK1 DIV dataset so no need to redefine SYSCHK1. We also recommend utilizing multiple OPSLOG support where you can define multiple OPSLOGs when OPS starts up. Then we provide a sample rule: SAMPLE.RULES(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.