When diagnosing problems with autoinstall, consult the following list. If you have a problem with autoinstall of APPC devices, and the following list does not resolve the problem, see Diagnosing APPC autoinstall problems.
Most autoinstall problems can be grouped into three categories:
The first category of problem is caused by CICS being in the wrong state to accept an autoinstall, for example, CICS is shutting down or AUTOINSTALL is disabled (message DFHZC2433).
The second category of problem arises when the two BIND images match, but the BIND is rejected by the actual device (message DFHZC2403). For information about valid BIND parameters, consult the 3274 Control Unit Description and Programmer’s Guide, GA23-0061.
The BIND image is contained in the CINIT RU passed to the LOGON exit. This is shown in trace point ID AP FC8A.
The reason for the third category of problem should be shown in the contents of the associated DFHZC69xx message on the CADL log. For example, message DFHZC6987 shows a BIND image mismatch between the incoming CINIT and the best available model (unlikely).
The length of each BIND image is found in the halfword preceding the image. A comparison is made for the smaller of the two length values, but not exceeding X'19' (decimal 25) bytes. The comparison is accomplished by an XC (exclusive OR) of the two BIND images into a work area. The result is ANDed with a mask that defines the required settings.
Additional bits are reset if the LU type, found in byte 14 of the BIND image, is 1, 2, 3, or 4. The final result in the work area must be 256 bytes of X'00'; any other value causes DFHZATA to reject the LOGON and write message DFHZC6987 to the CADL log.
For autoinstall to function correctly, three items must match:
When diagnosing APPC autoinstall problems, first refer to Diagnosing autoinstall problems. Most of points in that topic apply to APPC autoinstall problems except for points that refer to autoinstall models.
Any APPC autoinstall problem should be accompanied by message DFHZC6920 to 23. These messages each have exception trace entries which should trace enough information to allow you to diagnose the problem.
There are three autoinstall instances of DFHZC2411:
There are two additional instances of DFHZC2433:
There are two additional instances of DFHZC3482: