Updating Techniques, SYNCPOINT, and Logging › Special Logging Commands Considerations › CICS User Logging Differences Summary

CICS User Logging Differences Summary

Note: Be aware that the CA Datacom/DB record-at-a-time commands involving logging (COMIT, LOGCP, LOGCR, LOGIT, LOGLB, LOGTB, and ROLBK) will function differently beginning with CA Datacom CICS Services Version 14.0 than in r11 or r2.6.

CA Datacom CICS Services Version 14.0 has the following major changes concerning user issued log commands (LOGxx):

• All COMIT, LOGCP, LOGCR, LOGTB, and ROLBK commands invoke either a CICS SYNCPOINT or a SYNCPOINT ROLLBACK regardless of how many resource managers are involved be it only CA Datacom/DB, or CA Datacom/DB and others also such as DB2. A SYNCPOINT will be issued whether it is a single-phase or two-phase commit. This simplifies the complexity for the user from CA Datacom CICS Services r11.
• LOGIT and LOGLB are issued only to the default CA Datacom/DB Multi-User known as MUF1 in DBEC. In CA Datacom CICS Services r11, the same transaction involving requests to different CA Datacom/DB connections could log the LOGIT to different CA Datacom/DB Multi-Users depending on the order of requests made by the transaction. This has been simplified for the user. It will always go to the first defined connection.
• Although CA Datacom CICS Services replaced five of these commands with a SYNCPOINT type request, the original command is still logged on the CA Datacom/DB LXX except in the case where the log command was not needed. See User Issued Log Commands.

In legacy applications issuing these LOGxx commands, for detailed description of each command and how it is used under the various conditions, see User Issued Log Commands.