KDS_HUB_TCP_PIPES_PORT_NUM
This parameter contains the well-known port for the hub monitoring server for the IP.SPIPE communication protocol (the TCP/IP protocol that supports Secure Sockets Layer communications over IPV4), specified during configuration of a remote monitoring server
- Required or optional
- Required for remote Tivoli Enterprise Monitoring Servers that use the IP.SPIPE protocol for communications with the hub
- Location where the parameter value is stored
- KDSENV member of the rhilev.rte.RKANPARU library
for the runtime environment of the remote monitoring server
- Parameter name
- KDE_TRANSPORT (IP.SPIPE PORT option)
Example:
KDE_TRANSPORT=\ IP.SPIPE PORT:3660
- Default value
3660
- Permissible values
1
-65535
- PARMGEN name
- KDS_HUB_TCP_PIPES_PORT_NUM
- Description
- Well-known port for the hub monitoring server for the IP.SPIPE
communication protocol (the TCP/IP protocol that supports Secure Sockets
Layer communications over IPV4), specified during configuration of
a remote monitoring server. This protocol is available for a monitoring
server on a z/OS® system at
release level V1R7 or higher.
The value specified for this parameter must match the value set for the KDS_TEMS_TCP_PIPES_PORT_NUM parameter in the runtime environment where the hub is configured, or the value set for an equivalent parameter of a distributed hub.
- Related parameters
-
- KDS_TEMS_TCP_PIPES_PORT_NUM
- KDS_TEMS_TCP_HOST
- KDS_TEMS_COMM_PROTOCOLn
- KDS_HUB_* parameters (values for the Primary HUB TEMS that the z/OS Remote TEMS reports to)
- KDS_X_HUB_* parameters (values for the Standby HUB TEMS that the z/OS Remote TEMS connects to)