Diagnosing autoinstall problems
- The autoinstall model table (AMT) in an SDUMP
- CEMT INQUIRE AUTINSTMODEL to show which models are installed
- TC level-1 trace, point ID AP FC8A, which shows the CINIT RU contained in the AWE on entry to DFHZATA
- CADL, CSMT, and CSNE logs:
- Autoinstall messages (DFHZC69xx)
- Builder messages (DFHZC59xx, DFHZC62xx, and DFHZC63xx)
- Terminal error messages
- Information produced by DFHZNAC
- Dump taken in the user install program (the CICS®-supplied default is DFHZATDX).
- CICS rejects the LOGON request (message DFHZC2411 on the CSNE log).
- The device rejects the actual BIND parameters (message DFHZC2403 on the CSNE log).
- DFHZATA diagnoses a problem (message DFHZC69xx on the CADL log).
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, see Descriptions of common problems in subarea networks in z/OS Communications Server: SNA Diagnosis or IBM 3274 controller diagnosis in GDDM Diagnosis.
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.
- The CINIT BIND image taken from the LOGMODE entry specified for the LU in the VTAMLST
- The CICS MODEL BIND image built according to the specifications in the TYPETERM and TERMINAL entries
- Device characteristics.