II05399: DIAGNOSIS TECHNIQUES FOR MSGDFHZC5995 OR MSGDFH5995.

APAR status

• Closed as canceled.

Error description

• ***************************************************************
  *                                                             *
  * -SUBJECT OF INFO APAR- MSGDFHZC5995                         *
  *                                                             *
  ***************************************************************
  +-------------------------------------------------------------+
  ] THIS INFO APAR IS AN ATTEMPT TO DOCUMENT SOME TECHNIQUES    ]
  ] FOR DIAGNOSING PROBLEMS RESULTING IN MSGDFH5995 OR          ]
  ] MSGDFHZC5995.  THE INITIAL DESCRIPTIONS WERE BASED ON ONE   ]
  ] LONG RUNNING PROBLEM IN A CICS RELEASE 3.2.0 SYSTEM.        ]
  ] THESE TECHNIQUES ARE THEREFORE NOT ALL ENCOMPASSING OF ALL  ]
  ] PROBLEMS THAT RESULT IN THE DFHZC5995.  THEY ARE ALSO NOT   ]
  ] NECESSARILY RESTRICTED TO CICS 3.2.0.  ALSO, ANY OTHER HINTS]
  ] TECHNIQUES, OR TIPS ARE DEFINITELY WELCOME.                 ]
  ]-------------------------------------------------------------]
  ]                                                             ]
  ]  MESSAGE DFH5995 OR DFHZC5995 IS ISSUED FROM MODULE DFHZCQIS]
  ]DURING INSTALL PROCESSING FOR A TERMINAL.  THE MESSAGE IS    ]
  ]ISSUED IF THERE IS NO ENTRY IN THE CICS MAINTAINED TABLE OF  ]
  ]TERMINAL TYPE BIND IMAGES THAT MATCHES THE BIND IN USE.  THE ]
  ]BIND IN USE WILL EITHER BE THE BIND IMAGE CREATED BY CICS    ]
  ]FROM THE TYPETERM DEFINITIONS AND PLACED IN THE BUILDER      ]
  ]PARAMETER SET FOR NON-AUTOINSTALL TERMINALS OR THE BIND IMAGE]
  ]IN THE CINIT RU FOR AUTOINSTALL TERMINALS.                   ]
  ]                                                             ]
  ]  THE CICS TABLE OF DEVICE TYPES (ZRTTE) IS DEFINED USING    ]
  ]MACROS IN MODULE DFHZCQRT.  EACH DEVICE TYPE HAS A RESOURCE  ]
  ]TYPE CODE (RTC) AND SUBTYPE.  THESE ARE DECLARED IN THE      ]
  ]DFHZRTTE CALL FOR EACH DEVICE TYPE.  THE NAME OF THE BIND    ]
  ]IMAGE USED FOR THIS DEVICE IS ALSO SPECIFIED ON THIS MACRO   ]
  ]CALL.  FOR EXAMPLE, A 3277 NON-SNA DEVICE MAY HAVE AN RTC OF ]
  ]145 AND SUBTYPE 0 AND USE THE BIND IMAGE S3270.  THE BIND    ]
  ]IMAGES MAY BE FOUND AT THE END OF THE SOURCE FOR DFHZCQRT.  A]
  ]TYPICAL EXAMPLE OF A ZCQRT ENTRY WILL LOOK LIKE THIS:        ]
  ]                                                             ]
  ] 9101@@@@ D7F1F4F5 F0F0F140 @@@@XXXX                         ]
  ]  ]   ]    ]                 ]   ]                           ]
  ]  ]   ]    ]                 ]    INDEX NUMBER               ]
  ]  ]   ]    ]                  DISPLACEMENT TO BIND IMAGE     ]
  ]  ]   ]     8 BYTE PATTERN NAME                              ]
  ]  ]    DISPLACEMENT TO PATTERN                               ]
  ]   RTC AND SUBTYPE CODES                                     ]
  ]                                                             ]
  ]                                                             ]
  ]                                                             ]
  ]  FOR EACH DEVICE A TYPICAL BIND IMAGE IS DEFINED ALONG WITH ]
  ]A MASK.  THIS MASK IS USED DURING DFHZCQIS PROCESSING AND IS ]
  ]EXPLAINED BELOW.                                             ]
  ]                                                             ]
  ]  WHAT DFHZCQIS DOES IS TO GO THROUGH THE CICS TABLE CHECKING]
  ]FOR A DEVICE TYPE THAT MATCHES THE BIND IMAGE IN THE BPS OR  ]
  ]CINIT RU.  DFHZCQIS COMPARES THE RTC AND SUBTYPE IN THE BPS  ]
  ](ZCQPSRTC AND ZCQPSLTS) WITH THAT IN THE CURRENT TABLE ENTRY.]
  ]IF THEY DON'T MATCH THEN THE NEXT TABLE ENTRY IS CHECKED.  IF]
  ]A MATCH IS FOUND THEN A CALL TO INTERNAL PROCEDURE BINDCHK IS]
  ]MADE.                                                        ]
  ]                                                             ]
  ]  BINDCHK COMPARES THE BIND IN USE (BPS OR CINIT) WITH THE   ]
  ]BIND IN ZRTTE IGNORING THOSE BITS INDICATED BY THE MASK.  IF ]
  ]A BIT IS OFF IN THE MASK THEN THE CORRESPONDING BIT IN THE   ]
  ]BIND IS NOT CHECKED.  ALL OTHER BITS MUST MATCH EXACTLY UP TO]
  ]A LENGTH SET AS THE MINIMUM OF THE BIND IN USE LENGTH AND    ]
  ]ZRTTE BIND IMAGE LENGTH.                                     ]
  ]                                                             ]
  ]  IF BINDCHK FINDS A MATCHING BIND IMAGE THEN DFHZCQIS WILL  ]
  ]CALL TABLE BUILDER SERVICES (DFHTBS) TO BUILD THE TCTTE FOR  ]
  ]THAT DEVICE TYPE USING THE INFORMATION ("PATTERN") FROM      ]
  ]ZRTTE.  IF THE BIND IMAGES DON'T MATCH THEN DFHZCQIS WILL    ]
  ]CHECK THE NEXT ENTRY IN ZRTTE.                               ]
  ]                                                             ]
  ]  IF DFHZCQIS FAILS TO FIND A MATCHING BIND IMAGE THEN       ]
  ]DFH5995 IS ISSUED AND THE INSTALL FAILS.                     ]
  ]                                                             ]
  ]  NOW THE PROBLEM IS HOW TO FIND OUT WHY THE INSTALL FAILED!!]
  ]                                                             ]
  ]  THE FIRST POINT TO CONSIDER IS WHETHER WE ARE DEALING WITH ]
  ]A NON-AUTOINSTALL OR AUTOINSTALL TERMINAL.  FOR THE          ]
  ]NON-AUTOINSTALL CASE THE BIND IN USE IS THE BPS BIND IMAGE.  ]
  ]FOR AUTOINSTALL THE BIND IN USE IS IN THE CINIT RU.          ]
  ]                                                             ]
  For an AUTOINSTALL terminal, this message can often be the
  result of a user forcing a model selection out of their
  AUTOINSTALL exit.  A good (and easy) initial approach is to
  have the user run with the supplied AUTOINSTALL exit DFHZATDX.
  This way, if there is a matching model (that would NOT have
  any problem getting installed) it will be selected and can be
  compared to the one that the user's exit was trying to 'force'.
   If thereis no good match, a DFH5987 will be issued that will
  assist in analysis by showing the incoming CINIT BIND etc.
  
  ]  YOU MAY BE ABLE TO GET BPS BY GOING TO THE STORAGE DFHZATA ]
  ]IS USING TO STORE PARMLISTS.  A TRACE WILL SHOW THAT RIGHT   ]
  ]AFTER THE XCTL TO DFHZATA, IT DOES A GETMAIN FOR USER24      ]
  ]STORAGE.  THE PARMLIST IS STORED IN ZATA'S STORAGE IN THE    ]
  ]FOLLOWING FORMAT:                                            ]
  ]                                                             ]
  ]  E910E804 00000000 XXXXXXXX XXXXXXXX AAAAAAAA BBBBBBBB      ]
  ]  ]         ]                           ]         ]          ]
  ]  ]          RETURN CODE                ]       BIND ADDRESS ]
  ]   REQUEST BYTES                         BPS ADDRESS         ]
  ]                                                             ]
  ]                                                             ]
  ]  UNFORTUNATELY THE BPS ADDRESS WILL PROBABLY NOT BE VALID BY]
  ]THE TIME A DFHZC5995 DUMP IS PRODUCED BECAUSE DFHZCQIS REUSES]
  ]THAT AREA.  HOWEVER THE BPS ITSELF SHOULD BE STORED IN THAT  ]
  ]STORAGE AREA AND YOU MAY BE ABLE TO PICK IT OUT BY JUST      ]
  ]SCANNING THE STORAGE.  YOU SHOULD BE ABLE USE THE BIND       ]
  ]ADDRESS TO GO FIND THE BIND.                                 ]
  ]                                                             ]
  ]  TO OBTAIN THE BPS IN USE YOU CAN USE THE TRANSACTION CSFE  ]
  ]WITH THE ZCQTRACE OPTION.  YOU NEED TO KNOW THE TERMINAL ID. ]
  ]THIS PRODUCES A SERIES OF MINI TRANSACTION DUMPS WITH ABEND  ]
  ]CODE AZQX (WHERE X INDICATES WHICH MODULE IN DFHZCQ00 HAS    ]
  ]PRODUCED THE DUMP).  THE TRACING POINTS AND ASSOCIATED       ]
  ]DUMP-CODE ARE GIVEN BELOW:-                                  ]
  ]                                                             ]
  ]  ON EXIT FROM :                                             ]
  ]                                                             ]
  ]     MODULE       DUMPCODE                                   ]
  ]    DFHTRZCP        AZQC                                     ]
  ]    DFHTRZYP        AZQY                                     ]
  ]    DFHTRZZP        AZQZ                                     ]
  ]    DFHTRZXP        AZQX                                     ]
  ]    DFHTRZIP        AZQI                                     ]
  ]    DFHTRZPP        AZQP                                     ]
  ]    DFHZCQIQ        AZQQ                                     ]
  ]                                                             ]
  ]  ON ENTRY TO :                                              ]
  ]                                                             ]
  ]     MODULE       DUMPCODE                                   ]
  ]    DFHZCQIS        AZQS                                     ]
  ]                                                             ]
  ]  THE SEGMENT STORAGE PRODUCED FOR EACH DUMP SHOWS THE BPS AT]
  ]EACH STAGE OF ITS CREATION.  THE ONE WE ARE INTERESTED IN FOR]
  ]DFH5995 PROBLEMS IS THE DUMP WITH CODE 'AZQS'.  THIS SHOWS   ]
  ]THE BPS IN ITS FINAL STATE.  THE RTC AND SUBTYPE CAN BE SEEN ]
  ]AT OFFSET X'6' INTO THE SEGMENT STORAGE.  REMEMBER THESE ARE ]
  ]THE HEX VALUES AND THE VALUES GIVEN IN DFHZCQRT SOURCE ARE   ]
  ]DECIMAL.  THE BPS DATA AREA IS LAID OUT IN THE DATA AREAS    ]
  ]MANUALS UNDER THE HEADING ZCQPS.  USE THIS INFORMATION TO    ]
  ]FIND THE BIND IMAGE.                                         ]
  ]                                                             ]
  ]  A VTAM BUFFER TRACE OR THE SOURCE FOR THE VTAM LOGMODE     ]
  ]TABLE CAN BE USED TO OBTAIN THE BIND IMAGE IN THE CINIT RU   ]
  ]WHEN CONSIDERING AN AUTOINSTALL SCENARIO.                    ]
  ]                                                             ]
  ]  FOR AUTOINSTALL FAILURES THE FIRST CHECK IS TO COMPARE THE ]
  ]LOGMODE ENTRY BEING USED WITH THOSE SUPPLIED IN APPENDIX A OF]
  ]THE CUSTOMISATION GUIDE.  THESE MATCH EXACTLY (OR SHOULD     ]
  ]MATCH) THE ENTRIES IN ZRTTE FOR EACH DEVICE TYPE.  SEE APAR  ]
  ]PN00404 FOR AN EXAMPLE OF THIS.  HOPEFULLY THIS CAN LEAD TO A]
  ]QUICK RESOLUTION OF THE PROBLEM.                             ]
  ]                                                             ]
  ]  IF THIS DOESN'T REVEAL A PROBLEM THEN IT IS NECESSARY TO   ]
  ]FIND THE ENTRY IN ZRTTE AND COMPARE THE BIND IMAGE THERE WITH]
  ]THE BIND IN USE TO FIND THE MISMATCH.                        ]
  ]                                                             ]
  ]  TO FIND THE ZRTTE BIND IMAGE YOU NEED THE RTC AND SUBTYPE  ]
  ]FROM THE BPS.  REMEMBER THESE ARE HEX VALUES AND THOSE IN THE]
  ]SOURCE OF DFHZCQRT ARE IN DECIMAL.  NOW YOU NEED TO FIND THE ]
  ]MATCHING RTC AND SUBTYPE IN THE SOURCE FOR DFHZCQRT.  YOU CAN]
  ]THEN FIND WHAT BIND IMAGE IS USED BY CICS TO COMPARE WITH THE]
  ]BIND IN USE.                                                 ]
  ]                                                             ]
  ]  FOR EXAMPLE, IF THE BPS HAS X'9101' AT +X'6' THIS INDICATES]
  ]RTC(145) AND SUBTYPE(001).  IN DFHZCQRT LOOK FOR THE DFHZRTTE]
  ]MACRO WITH THE PARAMETER RTC(145) SUBTYPE(1) SPECIFIED.      ]
  ]NOTE, IF THE SUBTYPE IS ZERO THEN THERE WILL BE NO SUBTYPE   ]
  ]PARM SPECIFIED ON THE MACRO.  THERE MAY BE MORE THAN ONE     ]
  ]DEVICE TYPE FOR THIS RTC AND SUBTYPE BUT THEY WILL USE       ]
  ]DIFFERENT BIND IMAGES.  YOU CAN NOW GET THE NAME OF THE BIND ]
  ]IMAGE.  FOR RTC(145) SUBTYPE(1) THERE ARE TWO ENTRIES ONE    ]
  ]USING BIND IMAGE S3270 AND THE OTHER S327N.  IN THE SOURCE   ]
  ]FOR DFHZCQRT FIND THE BIND IMAGE AND MASK DEFINED AND COMPARE]
  ]THEM WITH THE BIND IN USE.  YOU CAN NOW TELL WHICH BITS      ]
  ]MISMATCH.                                                    ]
  ]                                                             ]
  ]  IF THERE IS A MISMATCH THEN THE PROBLEM CAN BE FIXED EITHER]
  ]BY MODIFYING THE TYPETERM DEFINITION TO SET THE BIT CORRECTLY]
  ]IN THE BPS BIND IMAGE OR BY MODIFYING THE LOGMODE ENTRY FOR  ]
  ]AUTOINSTALL TERMINALS.                                       ]
  ]                                                             ]
  ]  THE MISMATCH MAY BE OCCURRING BECAUSE OF AN ERROR IN CICS  ]
  ]CODE, EITHER IN THE ZRTTE TABLE OR AN INVALID SETTING OF A   ]
  ]BIT IN THE BPS BIND IMAGE.  THESE SHOULD BE APARED.  (SEE    ]
  ]PN00351 FOR AN EXAMPLE OF THE LATTER).                       ]
  ]                                                             ]
  ]                                                             ]
  ]-------------------------------------------------------------]
  ]                                                             ]
  ] - TO THE CUSTOMER: IF YOU HAVE SUGGESTIONS TO IMPROVE THIS  ]
  ]   INFORMATIONAL APAR, PLEASE SUBMIT A PROBLEM RECORD TO     ]
  ]   CICS LEVEL 2 USING THE APPROPRIATE COMPONENT ID.          ]
  ]                                                             ]
  ]             WE APPRECIATE YOUR SUGGESTIONS.                 ]
  ]                                                             ]
  ]-------------------------------------------------------------]
  ] DESCRIPTION                    COMPID    FESN    REL - AREL ]
  ] CICS/OS/VS 370   1.7.0         5740XX100 6515302  702  G02  ]
  ]                  170                             R702 RG02  ]
  ]                                                             ]
  ] CICS/OS/VS XA    1.7.0         5740XX100 6515302  703  G03  ]
  ]                  170                             R703 RG03  ]
  ]                                                             ]
  ] CICS/MVS         2.1.1         566540301 6540301  113  211  ]
  ]                                                  R113 R211  ]
  ]                                                             ]
  ] CICS/ESA         3.1.1         566540301 6540301  312  311  ]
  ]                                                  R312 R311  ]
  ]                                                             ]
  ] CICS/ESA         3.2.0         566540301 6540301  320  320  ]
  ]                                                  R320 R320  ]
  ]                                                             ]
  ]                  **** CICS/DOS/VSE/ESA ****                 ]
  ] DESCRIPTION                    COMPID    FESN    REL - AREL ]
  ] CICS/DOS/VS      1.6.0 RYO/GEN 5746XX300 6615302  838  H38  ]
  ]                  160                             R838 RH38  ]
  ]                                                             ]
  ] CICS/DOS/VS      1.6.0 PROD    5746XX300 6615302  938  I38  ]
  ]                  160                             R938 RI38  ]
  ]                                                             ]
  ] CICS/DOS/VS      1.6.0 GEN     5746XX300 6615302  147  A47  ]
  ]                  160                             R147 RA47  ]
  ]                                                             ]
  ] CICS/DOS/VS      1.7.0 RYO     5746XX300 6615302  969  I69  ]
  ]                  170                             R969 RI69  ]
  ]                                                             ]
  ] CICS/DOS SPOOLER 1.7.0 PROD    5746XX300 6615302  970  I70  ]
  ]                  170                             R970 RI70  ]
  ]                                                             ]
  ] CICS/VSE         1.7.0 PROD    5746XX300 6615302  169  A69  ]
  ]                  170                             R169 RA69  ]
  ]                                                             ]
  ] CICS/VSE SPOOLER 1.7.0 GEN     5746XX300 6615302  170  A70  ]
  ]                                                  R170 RA70  ]
  ]                                                             ]
  ] CICS/VSE         1.7.0 GEN     5746XX300 6615302  171  A71  ]
  ]                  170                             R171 RA71  ]
  ]                                                             ]
  ] CICS/VSE/ESA     2.1.0 RCF     568602601 0662216  313  CA3  ]
  ]                  210                             R313 RCA3  ]
  ]                                                             ]
  ] CICS/VSE/ESA     2.1.0 GEN     568602601 0662216  312  CA2  ]
  ]                  210                             R312 RCA2  ]
  ]                                                             ]
  ] CICS/VSE/ESA     2.1.0 PROD    568602601 0662216  311  CA1  ]
  ]                  210                             R311 RCA1  ]
  ]                                                             ]
  ]                  **** CICS/CMS/VM ****                      ]
  ] DESCRIPTION                    COMPID    FESN    REL - AREL ]
  ] CICS/CMS         1.1.0         566879501 6479501  110  110  ]
  ]                                                  R110 R110  ]
  ]                                                             ]
  ] CICS/VM          1.1.0         568401101 8401101  110  110  ]
  ]                                                  R110 R110  ]
  ] CICS/VM          1.2.0         568401101 8401101  120  120  ]
  ]                                                  R120 R120  ]
  ]                                                             ]
  ]-------------------------------------------------------------]
  ] END OF INFO                                                 ]
  +-------------------------------------------------------------+
  

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

• INFO APAR
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels