Autoinstall of consoles install flow

  1. The modify command comes into DFHZCNA via a CIB (Command Input Buffer) from MVS™ when a user types a console command for CICS®.
  2. DFHZCNA scans the Console Control Elements for a matching console name. If no CCE is found and autoinstall for consoles is enabled, an Autoinstall Work Element is created and added to the AWE queue.
  3. DFHZACT scans the AWE queue and attaches the CATA transaction.
  4. The CATA transaction calls DFHZATA, which sees that the AWE is for a console (sometimes called a Console Work Element) and calls DFHZATA2.
  5. DFHZATA2 proceeds as follows:
    1. It finds the console models (AICONS is supplied in group DFHTERMC).
    2. If SIT AICONS(YES) is specified, the models are passed to the autoinstall user-replaceable program, which returns the termid. The default autoinstall user-replaceable program returns the last four characters of the console name.
    3. If SIT AICONS(AUTO) is specified, DFHZGBM is called to get a name in the console bitmap, in the form ¬AAA. The autoinstall user-replaceable program is not called.
    4. It calls DFHZCP FUNCTION(INSTALL).
    5. It issues EXEC CICS SYNCPOINT.
    6. It signs on if using preset security of USERID=*EVERY|*FIRST specified in the AI model TYPETERM.
    7. It gets a TIOA to hold the data specified in the command. For example, if /f jobname,CEMT I TE is typed at the console, CEMT I TE is put into the TIOA.
    8. It calls DFHZATT to attach the transaction specified in the MODIFY command (for example, CEMT).


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