CPI Communications failures

For a CPI Communications driven LU 6.2 conversation, IMS TM is not involved and places no restrictions on your choice of either committing or backing out updates.

Session failure
In the event of a session failure, a CPI Communications driven application program can provide full integrity by issuing commit (SRRCMIT) or a backout (SRRBACK) calls. If an LU 6.2 session fails during an LU 6.2 conversation, you can end the conversation or continue processing.
System failure
When the IMS system fails during a CPI Communications driven LU 6.2 conversation, IMS determines whether to resolve in-doubts for IMS-protected resources. Examples of IMS-protected resources are IMS DB databases, Db2 for z/OS® databases, and IMS TM messages.
Recovery processing for CPI Communications driven application programs
If your application programs require recovery assistance, they should use the implicit API provided by IMS rather than the CPI API. Implicit support allows application programs that do not normally use LU 6.2 protocols to use LU 6.2 devices.

Parent topic: IMS failure recovery