Configuring for recovery of CICS-managed resources
This section describes what to do to ensure that you can recover the resources controlled by CICS® on behalf of your application programs.
- Recovering resources in the Liberty JVM server
Using Java™ Transaction API (JTA) to coordinate transactional updates. CICS recoverability options are limited for local and remote transactions. - Recovery for transactions
CICS recoverability options are limited for local and remote transactions. - Recovery for files
A CICS file is a logical view of a physical data set, defined to CICS in a file resource definition with an 8-character file name. - Recovery for intrapartition transient data
This section deals with both backward and forward recovery of intrapartition transient data. - Recovery for extrapartition transient data
CICS does not recover extrapartition data sets. If you depend on extrapartition data, you will need to develop procedures to recover data for continued execution on restart following either a controlled or an uncontrolled shutdown of CICS. - Recovery for temporary storage
This section deals with both backward and forward recovery of temporary storage. - Recovery for web services
If your web services use the WebSphere® MQ transport and persistent messages, you can use BTS to ensure that messages are recovered in the event of a CICS system failure. - Using a program error program (PEP)
The program error program (PEP) gains control after all program-level ABEND exit code has executed and after dynamic transaction backout has been performed.
dfht22f.html |
Last updated: Sunday, 4 June 2017