OS/2 APAR Extract CONTENTS ________ OS2APAR SEARCH processed on 05/04/1995 at 14:12 . . . . . . . . . . . . . 2 1 hit from search 'II07331' in PC/AC. . . . . . . . . . . . . . . . . . . 2 II07331 (Hit 1 of 1) . . . . . . . . . . . . . . . . . . . . . . . . . . 3 II07331 Summary Text . . . . . . . . . . . . . . . . . . . . . . . . . 3 II07331 Submitter . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 II07331 Responder . . . . . . . . . . . . . . . . . . . . . . . . . . . 7 OS2APAR 1 OS/2 APAR Extract OS2APAR SEARCH PROCESSED ON 05/04/1995 AT 14:12 _______________________________________________ 1 HIT FROM SEARCH 'II07331' IN PC/AC. _____________________________________ 1 II07331 CLOSED INFOPCLIB SB93/10/15 DD SEV3 CAN I OS2APAR 2 OS/2 APAR Extract II07331 (HIT 1 OF 1) ____________________ II07331 SUMMARY TEXT APAR= II07331 SER= PIN=INFOPCLIB-151 DD DOC POSSIBLE VTAM APARS THAT MAY BE RELATED TO NETVIEW DM/2 OPERATION. STAT= CLOSED CAN FESN5NFO000-000 CTID= II0000 ISEV= 3 SB93/10/15 RC93/10/26 CL93/12/08 PD94/12/13 SEV= 3 PE= TYPE= I RCOMP= INFOPCLIB PC LIB INFO ITE RREL= R001 FCOMP= PFREL= F TREL= T ACTION= SEC/INT= DUP/ USPTF= PDPTF= DUPS 0 DW93/10/15 RT SC FT RE PT UP LP PV AP EN FL LC94/12/13 RU94/12/13 OT CT FR TD TYPE OF SOLUTION= PROJECTED CLOSE CODE= CUST INST LVL/SU= FAILING MODULE: FAILING LVL/SU= SYSROUTE OF: RET APAR= PS= STATUS DETAIL= RELIEF AVAILABLE= COMP OPER ENV= II07331 SUBMITTER SYSRES= SYSIN= SYSOUT= CPU= RE-IPL= OPTYPE= SPECIAL ACTIVITY= REGRESSION= PRE-SCREEN NO.= RSCP= RS000 ERROR DESCRIPTION: ================================================================ The following was created to highlight possible VTAM apars that may be related to the operation of NvDM/2. Please refer to the actual VTAM apar for your release for additional information. Last Updated: 10/15/93 MJY ================================================================ ================================================================ START OF APAR ================================================================ APAR= OY55526 SER= PIN=568508501-731 MS MSGIST663I APPCCMD CONTROL=OPRCNTL,QUALIFY=CNOS FAILS WITH RC00080000 WHEN SLU IS ONLY SINGLE SESSION CAPABLE SB92/06/18 RC92/06/19 CL92/08/05 PD92/08/18 SEV= 2 RCOMP= 568508501 VTAM V3 MVS/ESA RREL= R401 FAILING MODULE= ISTNSCBQ FAILING LVL/SU= Z32 SYSROUTE OF: RET APAR= PS= S COMP OPER ENV= 401 OS2APAR 3 OS/2 APAR Extract PROBLEM SUMMARY: **************************************************************** * USERS AFFECTED: All APPC users. * **************************************************************** * PROBLEM DESCRIPTION: APPCCMD CONTROL=OPRCNTL,QUALIFY=CNOS * * fails with RC00080000 when slu is only * * single session capable. * **************************************************************** * RECOMMENDATION: Apply ptf when available. * **************************************************************** VTAM APPC is building a BIND with a logmode of SNASVCMG to send TO A SINGLE SESSION CAPABLE LU (UNAWARE THAT IT IS SINGLE SESSION AT THIS POINT). BEFORE THE BIND IS PASSED TO LUS, APPC CALCULATES THE OFFSET OF THE START OF THE LOGMODE IN THE BIND IN CASE THE BIND IS REJECTED FOR LACK OF PARALLEL SESSION CAPABILITY. WHEN APPC WAS FIGURING OUT THE OFFSET OF THE LOGMODE INTO THE BIND HE WAS USING THE REAL LENGTH OF THE PLU NAME (THE PLU NAME IS A VARIABLE LENGTH FIELD IN FRONT OF THE LOGMODE) THAT LUS IS GOING TO STICK INTO THE BIND. WHEN THE BIND IS REJECTED BY THE SLU FOR SINGLE SESSIONS CAPABILITY THE OFFSET OF THE LOGMODE IS PASSED BACK IN THE LAST 2 BYTES OF THE X'0835XXXX' SENSE. BUT, LUS CONVERTS THIS SENSE ASSUMING THAT THE APPLICATION (IN THIS CASE VTAM APPC) USED AN 8 BYTE PLU NAME IN ITS CALCULATION OF THE OFFSET. AS APPC VTAM WAS USING THE VARIABLE LENGTH PLU NAME AND LUS WAS ASSUMING THAT THE APPL WAS USING AN 8 BYTE PLU NAME, APPC WAS NOT CATCHING THE FACT THAT THE SLU WAS SINGLE SESSION CAPABLE. PROBLEM CONCLUSION: ISTNSCBQ HAS BEEN CHANGED TO USE AN 8 BYTE PLU NAME WHEN FIGURING OUT THE OFFSET OF THE LOGMODE IN THE BIND. TEMPORARY FIX: COMMENTS: MODULES/MACROS: ISTAMU ISTNSCBQ SRLS: NONE RTN CODES: APPLICABLE COMPONENT LEVEL/SU: R301 PSY UY82657 UP92/08/24 P F207 R401 PSY UY82659 UP92/08/24 P F207 R431 PSY UY82660 UP92/08/24 P F207 ================================================================ END OF APAR ================================================================ ================================================================ START OF APAR ================================================================ APPC SESSION BIND FAILS WITH 08350026 ON A LU6.2 SESSION. OY60647 R431, OY62580 R303, OY62806 R101, OY64480 R401, and OY66081 R301. APAR= OY60647 SER= IN INCORROUT APPC SESSION BIND 08350026. LU6.2 RCOMP= 568508501 VTAM V3 MVS/ESA RREL= R431 PV93/03/05 AP EN FL FAILING MODULE= ISTNSCBA FAILING LVL/SU= 431 OS2APAR 4 OS/2 APAR Extract COMP OPER ENV= 431 PROBLEM SUMMARY: **************************************************************** * USERS AFFECTED: All users with VTAM APPC APPLS (APPC=YES) * * acting as a SLU (VTAM APPC APPL receives * * the BIND). Also COMM MANAGER users with * * JR06747 applied. * **************************************************************** * PROBLEM DESCRIPTION: APPC session setup fails with BIND * * error sense 08350026. * **************************************************************** * RECOMMENDATION: * **************************************************************** VTAM receives a BIND request with SESSION INSTANCE IDENTIFIER SUBFIELD of x'03' and a format byte of x'01'. In the BIND response, VTAM echoes x'03' (SSI) and x'01'(format byte) back to the device. The device expects the format byte in the response to be a x'02' as stated in the SNA NETWORK PRODUCT FORMATS manual (LY43-0081-1), chapter 7. Per SNA protocol, x'02' should be used in RSP(BIND) in response to format x'01' in BIND. Therefore, the device rejects the BIND with 08350026 because the USER DATA SESSION INSTANCE IDENTIFIER SUBFIELD format byte is incorrect. PROBLEM CONCLUSION: To insure the BIND response will be sent using the correct architectural protocol the following changes were made : 1) In ISTNSCBA, in new segment CHKSID, if the format byte of the SESSION INSTANCE IDENTIFIER SUBFIELD is x'01' then VTAM will CIDCTL find the FMCBEXT to obtain the PCID. If a PCID is found then the PCID will be saved in the SABSESID and a new bit will be set in the SAB (SABNARCH) to indicate new architecture is being implemented. In ISTNSCBB, if SABNARCH is on then x'02' will be sent in the BIND response. When the received BIND Request indicates new method (X'01'), the external changes will be: A) VTAM APPC APPLs will now see the full 8 byte PCID reported reported in RPL6SSID field for APPCCMDs CONTROL = ALLOC or CONTROL = RCVFMH5. This topic will be updated in the VTAM Programming for LU 6.2 as follows : - Chapter 7: DESCRIPTION OF THE SESSION IDENTIFIER 0-n the PCID from the CV60 when the Session Instance Identifier structure data subfield is format x'01'. B) Products that interrogate this field within the BIND Response will now see the new format X'02'. While the session is active, the PCID portion of the FQPCID will be used as the session identifier. 2) In ISTNSCBA, in new segment CHKSID, if the format byte of the SESSION INSTANCE IDENTIFIER SUBFIELD is not x'01' then VTAM will handle the BIND response using the old architecture. The first byte of SABSESID will be set to x'00' or x'F0' depending on which name is greater OS2APAR 5 OS/2 APAR Extract between the PLU and the SLU. The remaining 7 bytes of SABSESID will be the SSI SUBFIELD. In ISTNSCBB, if SABNARCH is off, then the BIND response will contain what was saved in SABSESID. (This session is using the old architecture protocol. While the session is active, the session identifier will be x'00' or x'F0' and 7 bytes of the SSI SUBFIELD.) MODULES/MACROS: ISTNSCBA ISTNSCBB ISTSAB ADDITIONAL SYMPTOMS: SNA Report Code / Sense / Sns Data / Return 0835 0026 0028 002A 0835002A APPLICABLE COMPONENT LEVEL/SU: R431 PSY UY91597 UP93/04/28 P F304 LOCAL FIX: Regress JR06747. ================================================================ END OF APAR ================================================================ R210 R220 R110 R111 +==============================================================+ ! KEYWORDS for SEARCH: ANX0901E MSGANX0901E ANX0910 ! ! INFOPALIB INFOPCLIB NETVIEW DM NvDM/2 DM/2 DM2 PS/2 OS/2 ! ! NDMINFO RALINFO NDM2INFO VTAM CONNECTION FAILURE APPC ERROR ! !--------------------------------------------------------------! ! COMPONENTS THAT APPLY: ! ! COMPID REL FMID FESN PRODUCT ! ! 562143900 210 n/a 0966237 NetView DM/2 V2 ! ! 562143900 220 n/a 0966237 NetView DM/2 V2.1 ! ! 562116700 100 n/a 0963312 NetView DM/2 V1 ! +==============================================================+ LOCAL FIX: Regress JR06747. ================================================================ END OF APAR ================================================================ R210 R220 R110 R111 +==============================================================+ ! KEYWORDS for SEARCH: ANX0901E MSGANX0901E ANX0910 ! ! INFOPALIB INFOPCLIB NETVIEW DM NvDM/2 DM/2 DM2 PS/2 OS/2 ! ! NDMINFO RALINFO NDM2INFO VTAM CONNECTION FAILURE APPC ERROR ! !--------------------------------------------------------------! ! COMPONENTS THAT APPLY: ! ! COMPID REL FMID FESN PRODUCT ! ! 562143900 210 n/a 0966237 NetView DM/2 V2 ! ! 562143900 220 n/a 0966237 NetView DM/2 V2.1 ! ! 562116700 100 n/a 0963312 NetView DM/2 V1 ! +==============================================================+ OS2APAR 6 OS/2 APAR Extract II07331 RESPONDER PROBLEM SUMMARY: PROBLEM CONCLUSION: TEMPORARY FIX: COMMENTS: This info apar was created and will update to reflect possible VTAM apars related to the successful operation of NvDM2 MODULES/MACROS: SRLS: RTN CODES: APPLICABLE COMPONENT LEVEL/SU: CIRCUMVENTION: MESSAGE TO SUBMITTER: OS2APAR 7