To provide symmetry of control over the autoinstall process, the autoinstall control program is also invoked when an autoinstalled APPC connection is deleted.
Invoking the control program at DELETE enables you to reverse the processes carried out at the INSTALL event. For example, if the control program at INSTALL incremented a count of the total number of automatically installed resources, then the control program at DELETE would decrement that count.
Input to the program is by a communication area, addressed by DFHEICAP. The layout of the communication area is shown in Figure 38.
Fullword 1 Standard Header
Byte 1 Function Code (X'F5' or X'F6')
Bytes 2 - 3 Component Code Always "ZC"
Byte 4 Reserved Always X'00'
Fullword 2 SYSID of deleted connection
Fullword 3 NETNAME of deleted connection
Bytes 1-2 NETNAME length
Bytes 3-10 NETNAME
The Function Code byte (byte 1 of fullword 1) indicates why the user program has been invoked:
Any autoinstalled APPC connection entry is deleted if the connection is discarded (using the CEMT DISCARD command). In addition, connection entries can be deleted when the terminal or system logs off, or is disconnected from CICS®. This kind of "implicit deletion" occurs for the following types of APPC autoinstalled connection:
These are deleted when the terminal user logs off, after the expiry of the AILDELAY system initialization value.
Synclevel 1-only APPC connections autoinstalled via a BIND request (except for limited resource connections installed on a CICS generic resource member--see next section) are implicitly deleted at the following times:
Synclevel 2-capable APPC connections installed by a BIND request are implicitly deleted only if they are installed on a CICS generic resource member, and an affinity is ended. Otherwise, they are never implicitly deleted.
The same applies to synclevel 1-only, limited resource connections that are installed on a CICS generic resource member.