Unavailability of a database
The conditions that make an entire database unavailable for both read and update are the following.
- A
STOPcommand has been issued for the database. - A
DBRECOVERY(DBR) command has been issued for the database. - DBRC authorization for the database has failed.
The conditions that make a database available for read but not for update are:
- A
DBDUMPcommand has been issued for the database. - The database access value is RD (read).
In a data-sharing environment, the command or error that created any of these conditions may have originated on the other system which is sharing data.
Whether a program is scheduled or whether an executing program can schedule a PSB when the database is unavailable depends on the type of program and the environment:
- A batch program
IMS does not schedule a batch program when one of the databases that the program can access is not available.
In a non-data sharing environment, DBRC authorization for a database may fail because the database is currently authorized to a DB/DC environment. In a data-sharing environment, a CICS® or a DBCTL master terminal global command to recover a database or to dump a database may make the database unavailable to a batch program.
The following conditions alone do not cause a batch program to fail during initialization:- A PCB refers to a HALDB.
- The use of DBRC is suppressed.
- An online or BMP program in the DBCTL environment.
When a program executing in this environment attempts to schedule with a PSB containing one or more full-function databases that are unavailable, the scheduling is allowed. If the program does not attempt to access the unavailable database, it can function normally. If it does attempt to access the database, the result is the same as when the database is available but some of the data in it is not available.