Ansicht
Dokumentation

CPF83E4 - Commitment control ended with resources not committed. ( OS/400 )

Fill RESBD Structure from EBP Component Structure   Fill RESBD Structure from EBP Component Structure  
This documentation is copyright by IBM.


Message : CPF83E4
Commitment control ended with resources not committed.

Message Long Text :

Cause . . . . . : Pending changes for some resources were rolled back at the time commitment control was ended for commitment definition &8 with logical unit of work identifier &11. Local and remote resources were registered when the commit definition was rolled back. There are &7 journals with a total of &4 record level changes. There are &5 object level changes. There are &6 API commitment resources. There are &2 protected and &3 unprotected remote resources.
Recovery . . . : No recovery is required. Use the COMMIT or ROLLBACK command before ending commitment control to avoid this situation. API commitment resources must be removed using the Remove Commitment Resource API (QTNRMVCR). If protected conversations are being used, end the conversations normally using the correct synchronization level.
Technical description . . . . . . . . : The commitment definition identifier is &9. The activation group number is &10. The lock space id is &16. The lock space associated space id is &17. The XID is &18.

Message File : QCPFMSG
Library Message File : QSYS2924


BAL_S_LOG - Application Log: Log header data   ABAP Short Reference  
This documentation is copyright by IBM.

Length: 3238 Date: 20240419 Time: 133152     sap01-206 ( 3 ms )