IMS programming integrity and recovery considerations
IMS provides support for protecting data integrity for application programs.
How IMS protects data integrity: commit points
When an online program accesses the database, it is not necessarily the only program doing so. IMS and
Db2 for z/OS®
make it possible for more than one application program to access the data concurrently without endangering the integrity of the data.
Planning for program recovery: checkpoint and restart
Recovery in an IMS application program that accesses
Db2 for z/OS
data is handled by both IMS and
Db2 for z/OS
. IMS coordinates the process, and
Db2 for z/OS
handles recovery of
Db2 for z/OS
data.
Data availability considerations
The following information describes the conditions that could cause data to become unavailable in a full-function database and the program calls that allow your program to manage data under these conditions.
Use of STAE or ESTAE and SPIE in IMS programs
IMS uses STAE or ESTAE routines in the control region, the dependent (MPP, IFP, BMP) regions, and the batch regions. In the control region, STAE or ESTAE routines ensure that database logging and various resource cleanup functions are complete.
Parent topic:
Analyzing IMS application processing requirements