CEDA
The CICS transaction used to define resources such as programs, transactions and files, and install them in a running CICS region.
Also written CSD, resource definition online, RDO, DFHCSDUP, CEDA INSTALL
CEDA is the CICS transaction for defining resources. Before CICS can run a transaction, it needs to know the transaction ID, the program behind it, the files it uses and the screens it sends. CEDA is where those definitions are created and changed.
Definitions are stored in the CSD, the CICS system definition file, and grouped into named groups, usually one or a few for each application. CEDA DEFINE creates a definition and CEDA INSTALL makes it active in the running region, without restarting CICS. A list of groups is installed automatically each time the region starts from scratch.
CEDA and CEMT are easy to confuse. CEDA works with definitions: what a resource should be. CEMT works with installed resources: their current state in the running region, such as whether a file is open, or loading a new copy of a program.
The same definitions can also be made in batch with the DFHCSDUP utility, which many sites use so that changes go through change control.
Where can I learn this hands-on?
Right here, at ZedBank. You take a junior job at a simulated bank and learn each part of the work by doing it, with Zed beside you. There's nothing to install.
Start at ZedBankRelated
- CEMTThe CICS transaction used to see and change what is running in a region, enquiring on resources and acting on them.
- CICS regionOne running copy of CICS, with its own programs, files and users. A site typically runs several.
- Transaction IDA four-character code that tells CICS which program to run, typed on the screen or triggered by a key.
- CICSThe transaction manager that runs online mainframe applications, and the software behind a great many screens bank staff use.
- Change controlThe process every change goes through before reaching production: reviewed, approved, scheduled and reversible.