APAR status
Closed as canceled.
Error description
CICS AUTOINSTALL FAILURE WITH MESSAGE DFH5923 AFTER APPLICATION OF PL16388 CUSTOMERS MAY ENCOUNTER AUTOINSTALL FAILURES INDICATED BY MSGDFH5923I OR MSGDFH2411I (MSGDFH2411). AFTER APPLICATION OF PL16388, WHEN THE SEND AND/OR RECEIVE RU SIZES ARE SPECIFIED IN THE TYPETERM ENTRY, IF THE RU SIZES ARE ALSO SPECIFIED IN THE LOGMODE TABLE ENTRY THEY MUST BE LESS THAN THE VALUE SPECIFIED IN THE TYPETERM. FOR EXAMPLE, IF YOU CODE A RECEIVE RU SIZE OF 256 IN THE TYPETERM BUT HAVE 1024 CODED IN THE LOGMODE TABLE ENTRY, THE INSTALL REQUEST WILL FAIL WITH A MESSAGE DFH5923 GIVEN. TO VERIFY THIS CONDITION YOU MUST COMPARE THE LOGMODE TABLE DATA WITH THE CICS DATA FOUND IN THE MODEL ENTRY ON THE RESTART DATA SET. THE RSD MAY BE PRINTED USING AMSPRINT. THE MODEL ENTRIES ARE IDENTIFIED BY THE CHARACTERS TORMM, (CONSULT THE CADL MESSAGE LOG FOR THE MODEL BEING USED FOR THE INSTALL). THE BIND IMAGE IS FOUND AT THE END OF THE MODEL IN QUESTION. IF THE LOGMODE ENTRY INFORMATION IS NOT AVAILABLE, YOU MAY OBTAIN THE BIND INFORMATION FROM THE CINIT RU. THE CINIT RU CAN BE FOUND IN A VTAM BUFFER TRACE DURING THE AUTOINSTALL REQUEST. ONCE YOU HAVE THE CINIT BIND AND THE MODEL BIND, THE BYTES WHICH ARE CHECKED ARE FOUND AT OFFSET 10 AND 11 (DECIMAL). OFFSET 10 IS THE RECEIVE RU SIZE AND 11 IS THE SEND RU SIZE. IN THE EXAMPLE THE MODEL BIND WILL HAVE AN X'85' AT OFFSET 10 WHILE THE CINIT BIND WILL HAVE AN X 87' AT OFFSET 10. SINCE THE CINIT VALUE IS LARGER THAN THE MODEL SIZE THE INSTALL REQUEST WILL TERMINATED WITH A MESSAGE DFH5923. FOR AN AUTOINSTALLED TERMINAL, SPECIFYING A NON-ZERO RECEIVESIZE/SENDSIZE WILL INDICATE TO CICS WHAT THE MAXIMUM OR ACTUAL VALUE OF THE RECEIVE/SEND RUSIZE MAY BE. IF THE APPROPRIATE RUSIZE WITHIN THE CINIT BIND IMAGE (SPECIFIED IN THE VTAM LOGMODE ENTRY) HAS A NON-ZERO VALUE THEN THE TYPETERM RECEIVESIZE/SENDSIZE WILL BE USED TO INDICATE THE MAXIMUM VALUE. HOWEVER: IF THE APPROPRIATE RUSIZE WITHIN THE CINIT BIND IMAGE IS ZERO THEN THE TYPETERM RECEIVESIZE/SENDSIZE WILL BE USED. THE FOLLOWING EXAMPLES DESCRIBE THE RESULTING BIND RECEIVE RUSIZES FROM A SET OF INPUT CINIT RUSIZES AND TYPETERM RECEIVESIZE. (THE SAME RULES APPLY TO THE SEND RUSIZE AND TYPETERM SENDSIZE). THE CINIT BIND RUSIZE (FROM LOGMODE TABLE) IS GREATER THAN ZERO BUT LESS THAN THE TYPETERM RECEIVESIZE, CICS USES THE CINIT RUSIZE. THE CINIT SIZE IS GREATER THAN ZERO AND IS GREATER THAN THE TYPETERM RECEIVESIZE (WHICH IS GREATER THAN ZERO), CICS WILL REJECT THE LOGON WITH MSGDFH5923. THE CINIT SIZE IS GREATER THAN ZERO AND THE TYPETERM RECEIVESIZE IS ZERO, CICS USES THE CINIT RUSIZE. THE CINIT SIZE IS ZERO AND THE TYPETERM RECEIVESIZE IS GREATER THAN ZERO, CICS WILL USE THE RECEIVESIZE VALUE. THE CINIT SIZE IS ZERO AND THE TYPETERM RECEIVESIZE IS ZERO, THIS WILL RESULT IN A ZERO RUSIZE WHICH IS ONLY VALID FOR BISYNC DEVICES. PL21136 ADDRESSES A PROBLEM CAUSED WHEN THE RUSIZES ARE SET TO ZERO IN THE TYPETERM AND LOGMODE ENTRY. THE RESULTING BIND IMAGE CONTAINS X'40' IN BOTH THE SEND AND RECEIVE RUSIZE FOR NON-SNA TERMINALS. THE FIX FOR PL21136 "MUST" BE APPLIED WHEN NON-SNA TERMINALS ARE IN USE. FOR BISYNC TERMINALS RU SIZES MUST BE SET TO ZERO (00) IN THE TYPETERM AND LOGMODE TABLE ENTRIES. FAILURE TO SET THE RU SIZES TO ZERO MAY RESULT IN INTERMITTENT MSGDFH3424 ERROR MESSAGES. MSGDFHZC3424 DFHZC3424 THIS INFORMATION IS ALSO APPLICABLE TO APAR PL18595 FOR CICS MVS RELEASE 2.1 COMPID 566540301. FOR DOS, APAR IS PL18597. ADDED FOR SEARCHABILITY 5746XX300 RI69 RA69 RA71 R170 MSGDFH5963 MSGDFH5963E ADDITIONAL KEYWORDS: 566540301 R321 321 V321 CICS/ESA 565501800 R410 410 R100 100 565514700 R300 300 R530 530 R200 200 R520 520 R510 510 5697E9300 R610 610 R620 620 R630 630 MSGDFHZC5963 DFHZC5963 MSGDFHZC6903 DFHZC6903
Local fix
JIM GRAUEL CICS LEVEL 2 RALEIGH
Problem summary
Problem conclusion
Temporary fix
Comments
INFORMATION APAR
APAR Information
APAR number
II03226
Reported component name
PB LIB INFO ITE
Reported component ID
INFOPBLIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1988-01-06
Closed date
1988-01-06
Last modified date
2004-09-16
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
[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
13 December 2020