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 for z/OS application control server region are run. |
Shutdown |
Shutdown the WebSphere
Application Server for z/OS application control region 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 WebSphere Application Server 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 WebSphere Application Server 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. |
What happens to CICS
if WebSphere Application Server for z/OS goes down? |
Should WebSphere
Application Server for z/OS happen to go down, one of two situations could
occur:
- If WebSphere Application Server for z/OS and CICS are currently engaged
in a unit of work, then RRS processing as described above would occur and
it may be necessary to recycle the application control server regions to release
pending transactional work in CICS.
- If WebSphere Application Server 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 |