IBM E027SLL-H - Tivoli Monitoring - PC, Руководство по устранению неисправностей

Страница: 116 / 310

Repairing TCP/IP service initialization failures:
About this task
Use the following steps to ensure the TCP/IP transport service is available:
Note: Failure at any of the following prevents the TCP/IP service from initializing
in the address space.
1. Ensure the INITAPI service is successful. See “The INITAPI call.”
2. Ensure the Name Resolution is successful. See “Name Resolution” on page 99.
3. Ensure the first SEND ran without error. See “The First SEND” on page 99.
The INITAPI call
IBM's implementation of TCP/IP requires that an address space perform an
INITAPI before issuing an TCP/IP service request. The INITAPI establishes a
communication pipe between the TCP/IP and the OMEGAMON Platform address
space. The INITAPI identifies the TCP/IP stack to be used by name. The TCP/IP
stack name used in the INITAPI is configured in the KLXINTCP member of
RKANPAR. This step must complete successfully. An INITAPI failure is fatal: no
TCP/IP services are available to the address space.
Confirming that the INITAPI call was successful:
The following messages indicate a successful INITAPI:
KLXIN001 HPNS INTERFACE AVAILABLE
KLXIN001 SOCKET INTERFACE TO TCPIPL AVAILABLE
Repairing the INITAPI call failures:
Most of INITAPI failures are the result of the wrong name specified in KLXINTCP.
The following is a classic example of an INITAPI failure:
KLVIN405 STARTUP MODULE: KLXINTCP, SEQUENCE(1), USING RKANPAR MEMBER KLXINTCP
KLXIN001 TCP/IP CONFIGURATION: TCP/IP_USERID=TCPIPG
KLXIN003 TCP/IP INTERFACE INITIALIZED
KLXIN009 SOCKET INTERFACE TO TCPIPG UNAVAILABLE: RC(FFFFFFFF) ERRNO(000003F3)
KLXIN004 TCP/IP INTERFACE NOT OPENED: RC(4)
Notice that the INITAPI failure is characterized by a return code of (-1) and an
ERRNO value, in this case X'3F3' or decimal 1011. ERRNO-s have names. These
names are found in TCPERRNO.H and decimal 1011 is EIBMBADTCPNAME. The
most common INTIAPI ERRNOs are EMVSINITIAL (156),
EIBMBADTCPNAME(1011), and no-name(10218).
Reasons for INITAPI failures include:
v
The name specified in KLXINTCP is wrong. TCP/IP_USERID is selected based
on the specification for TCPIPJOBNAME found in the file pointed to by
SYSTCPD in the TCP/IP started task JCL. The default (if no TCPIPJOBNAME
exists) is TCPIP. There exists field documentation on the RACF
®
procedure.
These two items should be checked first.
v
The started task name does not have RACF authority for the OMVS segment.
All address spaces must be given RACF (or ACF2) permission for the OMVS
segment to use TCP/IP services. Failure to grant this permission (which is
granted to the started task name) can result in INITAPI failures.
v
MAXPROCUSER has been exceeded. For MAXPROCUSER problems, you can
use console operator command SETOMVS MAXPROCUSER=xxx to increase the
current MAXPROCUSER value (as seen by D OMVS,O).
98
IBM Tivoli Monitoring: Troubleshooting Guide