Autoinstall of APPC device logon flow
This section describes the flow of control for an APPC parallel
session device (or single session via a BIND) that is to be logged
on by autoinstall.
- When an APPC device attempts to logon, z/OS® Communications Server drives the logon
exit DFHZLGX if a CINIT is received, or the SCIP exit DFHZBLX if a
BIND is received.
Note that DFHZBLX is a new z/OS Communications Server exit module that is called by DFHZSCX if an LU62 BIND has been received.
In the following circumstances, an APPC LU is a candidate for autoinstall.- If the connection is not already defined to CICS®.
- If the connection is not already installed.
- If the autoinstall user program (specified by the AIEXIT system initialization parameter) exists and caters for functions 2-4 as well as functions 0-1.
- If the z/OS Communications Server ACB is open.
- If it is an APPC parallel session connection.
- If it is an APPC single session connection with an incoming BIND (as opposed to CINIT - which uses terminal autoinstall).
- If ISC=YES is specified in the SIT.
- If the maximum number of concurrent logon requests (specified by AIQMAX) has not been exceeded.
- If the customer has installed the correct 'template' connection that is to be 'cloned' (or copied) to create the new connection.
If a match is found and AUTOINSTALL is enabled (TCTVADEN is set), CICS verifies that the terminal is eligible for autoinstall. Processing then consists of:- Building an autoinstall work element (AWE) by issuing an MVS™ GETMAIN for subpool 1.
- Copying the CINIT RU (DFHZLGX) or BIND (DFHZBLX) into the AWE.
- Adding the AWE to the end of the AWE chain, which is chained from the TCT prefix.
- Later, the AWE is actioned by DFHZACT attaching transaction CATA. For every AWE on the AWE chain, the DFHZATA autoinstall program is dispatched, passing to DFHZATA the AWE's address.
- The DFHZATA program:
- Validates the BIND image passed in the AWE. If the image is not valid, issue message DFHZC6901.
- Calls DFHZGAI Function(CREATE_CLONE_BPS) to create a Builder Parameter
Set from which to create the new connection ('clone'). This is done
by calling the customer supplied autoinstall user exit program (which
can be based on DFHZATDY) in which the customer chooses which 'template'
connection the new connection should be copied from.
If at any point DFHZGAI finds a problem it issues message DFHZC6920 or DFHZC6921 or DFHZC6922 with an exception trace entry which will explain the reason for failure.
- Issue DFHZCP function(INSTALL) to create the CONNECTION, MODEGROUP and SESSIONs, based on the attributes of the template connection.
- For parallel sessions with an incoming BIND, chose the SNASVCMG
secondary session and call DFHZGAI (SET_TCTTE_FOR_OPNDST). This mimics
code in DFHZBLX to check the session against the incoming BIND.
If at any point DFHZGAI finds a problem it issues message DFHZC6923 with an exception trace entry which explains the reason for failure.
- For parallel session with an incoming CINIT, chose the SNASVCMG primary session.
- If the installation was successful, commit the CONNECTION and queue it for logon processing. The new CONNECTION is queued for OPNDST processing.
- Free the AWE.