Design overview

The relevant parts of the EXEC interface are as follows:
  • The initial command processors, DFHEIP or DFHEIG.
    • DFHEIP is called when an EXEC CICS command is executed in an AMODE(24) or AMODE(31) user application program.
    • DFHEIG is called when an EXEC CICS command is executed in an AMODE(64) user application program.
    A parameter list is passed, in which the first argument (referred to as arg-zero) contains a group code and a function code as the first two bytes.
    • The group code in general indicates the CICS® component associated with the command being executed. In subsequent processing, it is this code alone that determines which EXEC processor module is called from DFHEIP or DFHEIG.
    • The function code identifies the actual command being executed.

    DFHEIP and DFHEIG are link-edited with other modules to form the application interface program (DFHAIP) load module.

  • A set of EXEC processor modules that the initial command processor calls, which perform the first level of analysis of the command being executed. The processor then calls the appropriate CICS domain to complete the execution of the command.
  • A set of EXEC stubs. For COBOL, PL/I, and C, there is one stub for each application language. For assembler language, there is one stub for AMODE(24) or AMODE(31) applications, and one stub for AMODE(64) applications. The appropriate stub must be link-edited at the front of each CICS application program, and provides the mechanism for getting to the correct entry points in the command processor.
  • The DFHAPLI module, which is called at the initialization and termination of each application program.


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