Enhanced scheduling

DBCTL supports enhanced scheduling. That is, PSB scheduling completes successfully, even if some of the full function databases or DEDB areas it requires are not available.

Full function databases that have been stopped or locked by the commands /STOP, /DBRECOVERY, or /LOCK, or that are unavailable for update because a /DBDUMP command has been issued, do not cause scheduling failures. Instead, the application program is prevented from accessing only the unavailable database(s) or area(s). Application programs can have read access to databases that have been made unavailable for update by the /DBDUMP command. If a program issues a call to an unavailable database or area, a transaction abend is issued. To avoid this happening, you can issue requests, after a PSB has been scheduled, to obtain information regarding the availability of each database and to indicate that your program will handle data availability status codes. These requests are described in Obtaining information about database availability and Accepting database availability status codes.