See Application programming for DBCTL.
- Data availability is always active. This means that a transaction can
fail after PSB schedule because of unavailable data.
- New CICS® transaction abend codes and messages.
- Access needed to an MVS™ console (referred to in this book as DBCTL console--see
also Operator communication with DBCTL -- overview) to take databases offline.
- Migrating CICS shared database and "native" IMS™ batch programs
to use BMPs.
- New DL/I requests.
- DEDB subset pointers.
- Batch programs migrated to DBCTL must issue checkpoints and be restartable
from the last checkpoint. You will have to change any existing batch jobs
to do this before you can run them on DBCTL.
[[ Contents Previous Page | Next Page Index ]]