CICS automation and recovery scenarios

(ZOS) CICS automation and recovery scenarios

This article explains different scenarios for CICS automation and recovery.

Task CICS automation and recovery scenarios
Startup CICS and any required CICS products, such as CICS Transaction Gateway, need to be properly installed, initialized, and started before any work flows to a CICS-enabled WebSphere Application Server controller.
Shutdown Shutdown the WAS controller that uses CICS as a backing store, then shut down the CICS service.
Handling in-flight or indoubt transactions if there is a failure If there is an error during processing, both CICS and WAS for z/OS rely on the underlying RRS subsystem to handle all rollback notifications to the registered interests. In the case of inflight transactions, RRS will notify all participants that a rollback is required, and normal rollback processing will occur in each registered party. In the case of indoubt transactions, it may be necessary to recycle the WAS for z/OS Application Control/Server region to release any pending transaction in CICS.
How to determine if CICS is running This is installation dependent.
Troubleshoot the failure of CICS web transactions that trigger the error WSIFIOException Failure occurs because the CICS resource adapter cannot access the CTG*.so files, which the adapter requires for running the Web Services Invocation Framework (WSIF). Solve the problem with the following steps:

Copy the CTG*.so files into the /lib directory of our Application Server installation. For example, the/lib directory might have the following path: WebSphere/V7R0/AppServer1/lib/.
Restart the CICS web transaction service over WSIF.

What happens to CICS if WAS for z/OS goes down? Should WAS for z/OS happen to go down, one of two situations could occur:

If WAS for z/OS and CICS are currently engaged in a unit of work, then RRS processing would occur and it may be necessary to recycle the application control server regions to release pending transactional work in CICS.
If WAS for z/OS and CICS are not currently engaged in a unit of work, CICS is not affected.

What happens to other subsystems if CICS goes down? Not applicable
Where to find more information CICS Operations and Utilities Guide

Diagnose problems (using diagnosis tools)
Automation and recovery scenarios and guidelines

Task	CICS automation and recovery scenarios
Startup	CICS and any required CICS products, such as CICS Transaction Gateway, need to be properly installed, initialized, and started before any work flows to a CICS-enabled WebSphere Application Server controller.
Shutdown	Shutdown the WAS controller that uses CICS as a backing store, then shut down the CICS service.
Handling in-flight or indoubt transactions if there is a failure	If there is an error during processing, both CICS and WAS for z/OS rely on the underlying RRS subsystem to handle all rollback notifications to the registered interests. In the case of inflight transactions, RRS will notify all participants that a rollback is required, and normal rollback processing will occur in each registered party. In the case of indoubt transactions, it may be necessary to recycle the WAS for z/OS Application Control/Server region to release any pending transaction in CICS.
How to determine if CICS is running	This is installation dependent.
Troubleshoot the failure of CICS web transactions that trigger the error WSIFIOException	Failure occurs because the CICS resource adapter cannot access the CTG.so files, which the adapter requires for running the Web Services Invocation Framework (WSIF). Solve the problem with the following steps: Copy the CTG.so files into the /lib directory of our Application Server installation. For example, the/lib directory might have the following path: WebSphere/V7R0/AppServer1/lib/. Restart the CICS web transaction service over WSIF.
What happens to CICS if WAS for z/OS goes down?	Should WAS for z/OS happen to go down, one of two situations could occur: If WAS for z/OS and CICS are currently engaged in a unit of work, then RRS processing would occur and it may be necessary to recycle the application control server regions to release pending transactional work in CICS. If WAS for z/OS and CICS are not currently engaged in a unit of work, CICS is not affected.
What happens to other subsystems if CICS goes down?	Not applicable
Where to find more information	CICS Operations and Utilities Guide