KDS_TEMS_TCP_PIPES_PORT_NUM

This parameter specifies the well-known port for the monitoring server for the IP.SPIPE communication protocol (the TCP/IP protocol that supports Secure Sockets Layer communications over IPV4).

Required or optional
Required if you specified IP.SPIPE as a communication protocol for the Tivoli Enterprise Monitoring Server
Location where the parameter value is stored
KDSENV member of the rhilev.rte.RKANPARU library for the runtime environment of the monitoring server
Parameter name
KDE_TRANSPORT (IP.SPIPE PORT option)

Example:

KDE_TRANSPORT=\
    HTTP:1920\
    IP.SPIPE PORT:3660\
Default value
3660 or the value set for the RTE_TCP_PORT_NUM parameter
Permissible values
1 - 65535
PARMGEN name
KDS_TEMS_TCP_PIPES_PORT_NUM
Description
Well-known port for the monitoring server for the IP.SPIPE communication protocol (the TCP/IP protocol that supports Secure Sockets Layer communications over IPV4). This protocol is available for a monitoring server on a z/OS® system at release level V1R7 or higher.

Tivoli® Management Services reserves a default well-known port for the first process started on a system (normally, the monitoring server). For monitoring agents and other components, an algorithm based on the port number assigned to the monitoring server calculates the listening port to reserve. A port number cannot be assigned to a component if it is already reserved for another component or application.

The default listening port number for the monitoring server for IP.SPIPE is 3660 or the value set for the RTE_TCP_PORT_NUM parameter. You might find it necessary to change the setting under some conditions; for example, when the port assigned to a component by the algorithm is already reserved by another application or component. For a remote Tivoli Enterprise Monitoring Server, the port number must be the same as that of the hub.

For detailed information about assigning port numbers, see Port number assignments.

Related parameters