Requirements for TCP/IP communication protocols
The Tivoli Enterprise Monitoring Server and the OMEGAMON enhanced 3270 user interface have special TCP/IP requirements. You must also provide a TCP/IP started task name.
Review the following TCP-related requirements.
- Default OMVS segment
- To use the TCP/IP communication protocols, a Tivoli Enterprise Monitoring Server on a z/OS® system requires a default OMVS segment. See the z/OS Communications Server IP Configuration Guide for an explanation of how to provide an OMVS segment. The OMVS segment is also required for the Tivoli OMEGAMON enhanced 3270 user interface.
- UID for the enhanced 3270 user interface started task
- The enhanced 3270 user interface uses BPXmmm services, which are part of z/OS UNIX® System Services, for TCP/IP. So a user ID defined with an OMVS segment must be created for the enhanced 3270 user interface started task.
- TCP/IP stack name
- You are prompted for a TCP/IP started task name when you create a runtime environment and when you configure a monitoring server or monitoring agent. In a new runtime environment, the default value for the TCP/IP started task name is an asterisk (*). This default, which uses the first TCP/IP stack that was started, is suitable if the LPAR contains a single TCP/IP stack.
If the LPAR contains more than one TCP/IP stack, you can specify the started task name of the TCP/IP stack you want to use; or you can specify the number sign (#), which is translated to a blank and allows the TCP/IP environment to choose the stack to use, either through TCP/IP definitions or through the use of the SYSTCPD DD statement.
Whichever method is used to select a TCP/IP stack in a multi-stack environment, the Tivoli Management Services components continue to use that stack, even if a different stack becomes the primary stack. Therefore, in a multi-stack environment, it is best to specify the started task name of the TCP/IP stack to be used, rather than specifying a wildcard or a blank.
- Access privileges for unreserved ports
- If the TCP/IP stack is configured with statement PORT UNRSV and is controlled by SAF resource checking (keyword SAF), users must have READ access to the following SAF resources in the SERVAUTH class:
- EZB.PORTACCESS.sysname.tcpname.UNRSVUDP
- EZB.PORTACCESS.sysname.tcpname.UNRSVTCP