Error messages to monitor during commitment control
Several different error messages can be returned by the commit or rollback operations or sent to the job log, depending on the type of message and when the error occurred.
The error messages can occur during the following processing:
- Normal commit or rollback processing
- Commit or rollback processing during job process end
- Commit or rollback processing during activation group end
You cannot monitor for any of the following messages during activation group end or job process end. Also, you can only monitor for CPFxxxx messages. CPDxxxx messages are always sent as diagnostic messages, which cannot be monitored. Any errors encountered when ending an activation-group-level commitment definition during activation group end or ending any commitment definition during job end are left in the job log as diagnostic messages.
Error messages related to commitment control to look for are as follows:
- CPD8351
- Changes might not have been committed.
- CPD8352
- Changes not committed at remote location &3.
- CPD8353
- Changes to relational database &1 might not have been committed.
- CPD8354
- Changes to DDM file &1 might not have been committed.
- CPD8355
- Changes to DDL object &1 might not have been committed.
- CPD8356
- Rolled back changes might have been committed.
- CPD8358
- Changes to relational database &1 might not have been rolled back.
- CPD8359
- Changes to DDM file &1 might not have been rolled back.
- CPD835A
- Changes to DDL object &3 might not have been rolled back.
- CPD835C
- Notify object &1 in &2 not updated.
- CPD835D
- DRDA® resource does not allow SQL cursor hold.
- CPF835F
- Commit or rollback operation failed.
- CPD8360
- Members or files or both were already deallocated.
- CPD8361
- API exit program &1 failed during commit.
- CPD8362
- API exit program &1 failed during roll back.
- CPD8363
- API exit program &1 ended after &4 minutes during commit.
- CPD8364
- API exit program &1 ended after &4 minutes during rollback.
- CPD836F
- Protocol error occurred during commitment control operation.
- CPD83D1
- API resource &4 cannot be last agent.
- CPD83D2
- Resource not compatible with commitment control.
- CPD83D7
- Commit operation changed to rollback.
- CPD83D9
- A heuristic mixed condition occurred.
- CPF83DB
- Commit operation resulted in rollback.
- CPD83DC
- Action If Problems Used to determine commit or rollback operation; reason &2.
- CPD83DD
- Conversation ended; reason &1.
- CPD83DE
- Return information not valid.
- CPD83EC
- API exit program &1 voted rollback.
- CPD83EF
- Rollback operation started for next logical unit of work.
- CPF8350
- Commitment definition not found.
- CPF8355
- ENDCMTCTL not allowed. Pending changes active.
- CPF8356
- Commitment control ended with &1 local changes not committed.
- CPF8358
- Notify object &1 in &2 not updated.
- CPF8359
- Rollback operation failed.
- CPF835A
- End of commitment definition &1 canceled.
- CPF835B
- Errors occurred while ending commitment control.
- CPF835C
- Commitment control ended with remote changes not committed.
- CPF8363
- Commit operation failed.
- CPF8364
- Commitment control parameter value is not valid. Reason code &3.
- CPF8367
- Cannot perform commitment control operation.
- CPF8369
- Cannot place API commitment resource under commitment control; reason code &1.
- CPF83D0
- Commitment operation not allowed.
- CPF83D2
- Commit complete == Resynchronization in progress has been returned.
- CPF83D3
- Commit complete == Heuristic Mixed has been returned.
- CPF83D4
- Logical unit of work journal entry not sent.
- CPF83E1
- Commit operation failed due to constraint violation.
- CPF83E2
- Rollback operation required.
- CPF83E3
- Requested nesting level is not active.
- CPF83E4
- Commitment control ended with resources not committed.
- CPF83E6
- Commitment control operation completed with resynchronization in progress.
- CPF83E7
- Commit or rollback of X/Open global transaction not allowed.
Parent topic:
Commitment control errors