CA OPS/MVS OPS3781S ABEND X'000C3000' occurred at OPINBO - OPSLOG process.

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

CA OPS/MVS OPSLOG processing gets an ABEND X'000C3000' OPINBO...'. The error occurs as a result of the OPSLOG message ID (MSGID) numbering scheme hitting the 2 Gigabyte limit. When a client attempts to go into OPSLOG, they may receive the following error: 'Checkpoint processing suspended'.


This abend happens if the message number reached the maximum of 2 gig.(X'7FFFFFFF' or decimal 2147483647). You can check the BROWSECHECKNUM parameter in OPSVIEW 4.1.1 to see the current value of the message number. If the value is near 2147483647, then you have the 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, 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.

  1. Execute this REXX program in your TSO foreground via the EXECUTE command: EXEC 'hlq.CCLXCNTL(DEFDIV)'
  2. Verify the Return Codes for each requested allocation are zero.  
  3. Recycle OPS to pick up the change in OPSLOGs.                              



Additional Information:

Other abend references for the same problem in other releases.

CA OPS/MVS 12.2 - OPS3781S ABEND X'000C3000' occurred at OPINBO X'0000430C'

CA OPS/MVS 12.1 - OPS3781S ABEND X'000C3000' occurred at OPINBO+X'0000430C