|
- Description:
- Checks whether the port range specified by INADDRANYPORT and INADDRANYCOUNT
in the BPXPRMxx parmlib member is reserved for OMVS on this stack,
when operating in a CINET environment. A port range is reserved on
a TCP/IP stack using the PORTRANGE TCP/IP profile statement. The tcpipstackname suffix
is the job name of the TCP/IP stack to which this check applies. Use
CSTCP_CINET_PORTRNG_RSV_* to reference this check for all stacks.
- Reason for check:
- When operating in a CINET environment, the range of ports defined
as available for CINET use by the INADDRANYPORT and INADDRANYCOUNT
parameters in the BPXPRMxx parmlib member should be reserved (using
the PORTRANGE TCP/IP profile statement) on every TCP/IP stack. This
prevents a TCP/IP stack from allocating a port that CINET might subsequently
attempt to use, which could result in an ABEND and the following message:
BPXF219I A SOCKETS PORT ASSIGNMENT CONFLICT EXISTS BETWEEN UNIX SYSTEM SERVICES AND TCPIPstackname
- z/OS® releases the check
applies to:
- z/OS V1R10 and later.
- User override of IBM® values:
- The following shows the default keywords for the check, which
you can override on either a POLICY statement in the HZSPRMxx parmlib
member or on a MODIFY command. This statement may be copied and modified
to override the check defaults:
UPDATE
CHECK(IBMCS,CSTCP_CINET_PORTRNG_RSV_tcpipstackname)
DATE('date_of_the_change')
REASON('Your reason for making the update.')
ACTIVE
SEVERITY(MEDIUM)
INTERVAL(ONETIME)
- Debug support:
- No
- Verbose support:
- No
- Parameters accepted:
- No
- Reference:
- For more information on using multiple instances of TCP/IP in
a CINET environment, see Considerations
for multiple instances of TCP/IP in z/OS Communications Server: IP Configuration Guide.
- Messages:
- This check issues the following exception messages:
See z/OS Communications Server: IP Messages Volume 2 (EZB, EZD).
- SECLABEL recommended for multilevel security users:
- SYSLOW - see z/OS Planning for Multilevel Security and the Common Criteria for
information on using SECLABELs.
|