Modules

The relationships between the components of RDO, and the components of some of the services it uses, are shown in Figure 1.
Figure 1. RDO interfaces
Daigram showing the components involved in resource definition online (RDO) and the relationships between them.

DFHEDAP and DFHEDAD control the CEDA, CEDB, and CEDC transactions. They provide screen management for the transactions, and invoke DFHAMP to implement any actions that are required.

DFHSII1 invokes DFHAMP when CICS® is cold started, to install resource definitions for the current run. These resource definitions are specified by the GRPLIST system initialization parameter. DFHSII1 passes the GRPLIST system initialization parameter to DFHAMP.

DFHAMP, the allocation management program, manages all requests to view, change, and install resources. It uses the services provided by other parts of RDO, and by the resource managers:
  • DFHAMP invokes DFHPUP and DFHDMP to read, write, and update resource definitions on the CSD data set:
    • DFHPUP, the parameter utility program, converts resource definition data between the parameter list format provided by DFHAMP and the record format needed by the CSD.
    • DFHDMP, the CSD management program, manages I/O of resource definition data to and from the CSD data set.
  • DFHAMP invokes DFHTOR, the terminal object resolution program, to merge TERMINAL, TYPETERM, CONNECTION, and SESSION definitions:
    • When requests are made to install TERMINALs, TYPETERMs, CONNECTIONs, and SESSIONs, DFHTOR merges TYPETERM and TERMINAL information, and also CONNECTION and SESSION information, and passes this merged information back to DFHAMP.
    • DFHAMP passes the merged definitions to DFHZCQ to install in the running CICS system. Any merged TERMINAL definitions that are to be used as autoinstall terminal models are passed to the autoinstall terminal model (AITM) manager.
    • When TYPETERM definitions are installed, DFHTOR records the information about the CICS global catalog for subsequent use.
    • When the CHECK command is issued, DFHTOR checks the appropriate TERMINAL, TYPETERM, CONNECTION, and SESSION definitions for consistency.
  • DFHAMP calls the appropriate resource managers to install resources in the running CICS system:
    • DFHZCQ is invoked to install CONNECTION, SESSION, and TERMINAL definitions.
    • DFHAMXM is invoked to install TRANSACTION and PROFILE definitions.
    • DFHPGDD is invoked to install PROGRAM, MAPSET, and PARTITIONSET definitions.
    • These subroutine “gates” are called to install resources related to file control:
      • FCMT, for FCT entries
      • FCRL, for LSR pools
      • FCDN, for DSN blocks
      • FCFS, to open and close files
      • AFMT, for AFCT entries for files.
    • The AITM manager is invoked, using an AITM ADD_REPL_TERM_MODEL subroutine call (see Autoinstall terminal model manager), to install autoinstall terminal models.
    • The partner resource manager is invoked to install partner resources for the SAA communications interface.
DFHEICRE processes all the EXEC CICS CREATE commands. It builds an internal DEFINE command for the resource to be created, and passes it to DFHCAP for interpretation. The encoded command is then passed directly to DFHAMP to install the resource in the running system. The CSD file is not accessed at all during this processing.

DFHCSDUP, the offline CICS system definition utility program, uses batch versions of routines from DFHPUP and DFHDMP to read, write, and update resource definitions on the CSD data set (see CSD utility program (DFHCSDUP)).

For a detailed description of how the CEDA transaction handles terminal resources, see Terminal control.



dfhs3c00894.html | Timestamp icon Last updated: Monday, 5 June 2017