IBM E027SLL-H Troubleshooting Guide - Page 118

v Presence of the well known port on the TCP/IP Port List. The RACF permission problem might not be detected until the failure of the first network I/O. The "KDCR0_Send" request fails with Errno 2: EACCESS. This failure can occur with the first use of the started task name. A similar problem results in EACCESS: the well-known port is defined on the TCP/IP port list. ISPF Option 6, "netstat portlist" confirms the presence of the well-known port in the TCP/IP reserved port list. The well-known port should not be on this list. SNA service initialization The IBM Tivoli MonitoringAddress Spaces can configure be configured to use SNA exclusively, or in conjunction with TCP/IP, as a transport service. This configuration is done in the environment member (xxxENV) of RKANPAR. If SNA services are viewed as optional, then removal of KDCFC_ALIAS, KDCFC_MODE, and KDCFC_TPNAME from the xxxENV member of RKANPAR will effectively disable use of SNA. Initializing the SNA: The following messages are printed in the RAS1/ RKLVLOG when the local SNA configuration is processed from the XXXENV member of RKANPAR: kbbssge.c,52,"BSS1_GetEnv") KDCFP_ALIAS=KDCFC_ALIAS=KLXBS_ALIAS="ASIAGLB" kbbssge.c,52,"BSS1_GetEnv") KDCFP_TPNAME=KDCFC_TPNAME=KLXBS_TPNAME="SNASOCKETS" kbbssge.c,52,"BSS1_GetEnv") KDCFP_MODE=KDCFC_MODE=KLXBS_MODE="CANCTDCS" kdes1rp.c,140,"getEnv") AF_SNA configuration: Alias(ASIAGLB) Mode(CANCTDCS) TpName(SNASOCKETS) KDCFC_ALIAS identifies the APPL definition of the Independent Logical Unit to be used in this process. KDCFC_MODE identifies the LOGMODE name, the same name found in the LOGMODE specification of the KDCFC_Alias APPL definition. KDCFC_TPNAME is the Transaction Processing Name. The message which indicates the LOCALLU is operational (the configuration is good) is the "transport opened" message: kde1otp.c,118,"KDE1I_OpenTransportProvider") Transport opened: com1/sna.pipe Repairing SNA initialization failures: The following reasons for SNA initialization failures: v The ILU configured for use is not available to the application. The ACBNAME (or APPLNAME) is properly defined in SYS1.VTAMLST but not in the connectable state (CONCT). The ACB must be varied ACTIVE to NET prior to Omegamon Platform Address Space startup. The MVS command to verify the state of the ACB is "D NET, ID=acbname,E" . v The ILU is available but not a valid LU6.2 definition. In this case, it is a KBBCM001 message with an SNA sense code found in the RAS1/RKLVLOG. Diagnose the 8-byte SNA sense code (typically, 087Dnnnn) using the "SNA Formats and Protocol" manual. v The LOGMODE is not a valid LU6.2 LOGMODE, or the LOGMODE and MODETAB specification associated with the ILU definition are not the same, by name, on both systems hosting the endpoints. This is most likely the case for SNA session establishment hangs. The message in the RKLVLOG is "Receive XID pending: NULL", and it is followed by another RPC timeout message. The Server list IBM Tivoli Monitoring processes build and query a list of possible Tivoli Enterprise Monitoring Server hub addresses, called the Server list. This server list contains 100 IBM Tivoli Monitoring: Troubleshooting Guide