II13406: OS/390 IBM COMMUNICATION SERVER V2R10: SC31-8726-00 IP CONFIGURATION REFERENCE TCPIPINFO BOOKAPAR

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • INTRAN

Error description

Local fix

  • ===========================================================
    INFOAPAR for OS/390 IBM Communications Server IP Configuration
    Reference V2R10. SC31-8726-01
    ===========================================================
    This information apar is available in the z/OS DOC APARs and
    PTF ++HOLD DOC data document, which can be found at:
    http://publibz.boulder.ibm.com:80/cgi-bin/bookmgr_OS390
    /BOOKS/ZIDOCMST/CCONTENTS
    ===============================================================
    In Appendix A. Using Translation Tables, under Running CONVXLAT
    in BATCH: replace the example with:
    //S00100    EXEC PGM=CONVXLAT,
    // PARM='''TCP3AS.SEZATCPX(FRENCH)'' ''USER3.STANDARD.TCPXLBIN''
    //SYSPRINT  DD SYSOUT=*
    //SYSIN     DD DUMMY,BLKSIZE=80
    ===============================================================
    In Chapter 2. TCP/IP Profile Statements (PROFILE.TCPIP), DEVICE
    and LINK Statement Virtual Devices, add this as the first note:
    The device_name or link_name must not start with VIPAD, as this
    a restricted keyword.
    ===============================================================
    In Chapter 6. OMPROUTE, in OSPF_INTERFACE, RIP_INTERFACE, and
    INTERFACE sections, change the Name parameter description to
    The name of the interface. Must match the link name coded for
    the corresponding IP address on the HOME statement in the
    TCP/IP profile. Valid values are any string from 1 - 16
    characters in length. If an exact IP address match is not found,
    then this parameter is used first when searching wildcard
    addresses. If a name match is not found, then the most specific
    wildcard address that matches is used. The same wildcard address
    can be configured more than once with unique names.
    ===============================================================
    In "Chapter 6. OMPROUTE", under DEFAULT_ROUTE statement, add the
    following to the Name parameter description:
    VIPA interfaces cannot be used as the interface_name.
    ===============================================================
    In Chapter 2. TCP/IP Profile Statements (PROFILE.TCPIP, under
    GATEWAY Statement Usage Notes, change the seventh bullet to:
    Static indirect routes cannot be added to the routing table if
    a direct route does not already exist in the routing table to
    the firsthop IP address. To ensure that the indirect static
    routes are processed as expected, code a route as the indirect
    routes as follows:
    GATEWAY
    9 = U42TR 4096 0.255.192.0 0.67.0.0
    9.67.128.87 9.67.17.10 U42TR 4096 HOST
    9.67.128.117 9.67.17.10 U42TR 4096 HOST
    9.67.134.212 9.67.17.10 U42TR 4096 HOST
    
    The static direct route allows the stack to process the indirect
    routes during initialization.
    ===============================================================
    In Chapter 12. File Transfer Protocol (FTP), under FTP Server
    User Exits, in the first sentence of the fifth paragraph, change
    FTPCHKIP to FTCHKIP.
    ================================================================
    In Chapter 29. Operator Commands and System Administration, in
    the DISPLAY TCPIP,,HELP Parameters section, change the PKTTRACE
    description to: Show help on the VARY PKTTRACE command.
    ===============================================================
    In Chapter 6. OMPROUTE, under the Subnet parameter description
    for OSPF_INTERFACE, add this:
    
    For a VIPA interface, this option suppresses advertisement of
    the VIPA host route. Normally CS for z/OS advertises both a
    host route and a subnet route for owned VIPA interfaces. With
    this option set to YES, only the subnet route is advertised.
    Note:
    Do not use this option for dynamic VIPAs, or for any VIPA whose
    subnet may exist on multiple hosts. If you do, problems will
    occur routing to all VIPAs that share the subnet.
    
     Valid Values are YES or NO.
    ================================================================
    In Chapter 2. TCP/IP Profile Statements (PROFILE.TCPIP), in the
    parameter descriptions for UDPCONFIG Statement, change the text
    for UDPSENDBFRSIZE to: UDPSENDBFRSIZE can be coded with any
    value that falls in the range of 1 to 65535.
    
    And change the description of UDPRCVBUFRSIZE to: UDPRCVBUFRSIZE
    can be coded with any value that falls in the range of 1 to 6553
    5.
    ===============================================================
    In Chapter 1. Configuration Data Sets, in Table 1. TCP/IP
    Configuration Data Sets, remove "3. hlq.PAGENT.CONF" in the
    PAGENT.CONF row.
    
    In Chapter 17. OS/390 UNIX Policy Agent and SLA Subagent, under
    Pagent Search Order, remove "4. hlq.PAGENT.CONF" from the list.
    =============================================================
    In Chapter 20. Remote Print Server (LPD), in the SERVICE
    statement, change the parameter description of OUTPUT=name
    to:
    
    Specifies the name of an OUTPUT JCL statement that contains
    additional spool parameters.
    
    Add the following in the Example section of the SERVICE
    statement:
    
    * OUTPUT JCL statement
    
    OUTPUT=LPD1
    
    Add the following line to the code sample shown in LPD Server
    Cataloged Procedure (LPSPROC) section.
    //LPD1 OUTPUT DEFAULT=YES,DEST=PRTNAME
    =============================================================
    In Chapter 17. OS/390 UNIX Policy Agent and SLA Subagent, in
    PolicyAction Statement, under PolicyScope parameter description
    move the Note beginning with "When TR is specified for scope,"
    to directly under the Parameter heading under the PolicyRule
    statement section.
    =============================================================
    In Chapter 25. SMTP Server, under NJENODENAME Statement, add
    the following note after the first paragraph:
    Note: NJENODENAME is location sensitive.
    =============================================================
    In Chapter 2. TCP/IP Profile Statements (PROFILE.TCPIP), under
    VIPADYNAMIC Statement, in the Modifying section, add this to
    the end of item 3: These changes will be communicated to any
    stacks backing up the distribution of this DVIPA unless the
    backup stack has its own VIPADISTRIBUTE statement coded.
    =============================================================
    In Chapter 2. TCP/IP Profile Statements (PROFILE.TCPIP), under
    PORTRANGE Statement, change jobname parameter description to:
    This specifies the MVS job name that can use the port. For UDP
    only one job name can be associated with a port.
    Note: For TCP, the same port(s) can be reserved multiple times
    for different job names by using a PORT statement. This can be
    useful if you have different servers or clients with different
    job names that need access to the port. For more information,
    see PORT statement.
    =============================================================
    In Chapter 2. TCP/IP Profile Statements (PROFILE.TCPIP), in
    DEVICE and LINK Statements section, under Missing Interrupt
    Handler (MIH) Considerations:, add the following note after
    the first paragraph:
    Note: D IOS,MIH will not show 00:00 for the MIH time on the
    read channel even though is has been configured off by VTAM.
    =============================================================
    In Chapter 5. OROUTED Server, under OROUTED parameters section,
    add the following:
    -s   Supply all routes. This parameter is the default and
    will disable all other RIP Supply filters.
    =============================================================
    In Chapter 2. TCP/IP Profile Statements (PROFILE.TCPIP), in
    GATEWAY Statement, add the following Note to max_packet_size
    parameter description:
    See the Usage Notes below for packet size considerations.
    =============================================================
    In Specifying the SNMPQE Parameters, under Specifying the SNMPQE
    Parameters, add the following note to the Notes section:
    3. When starting SNMPQE in batch, the 'POSIX(ON)' parameter
    should not be used.  This will alter the search order the Query
    Engine uses to find it's configuration files, and may prevent it
    from locating any configuration files not explicitly pointed to
    using a standard environment variable.  It can also have other
    unexpected results.
    ==============================================================
    In Chapter 2. TCP/IP Profile Statements (PROFILE.TCPIP), under
    PORT and PORTRANGE statements, add the following note to the
    note list under the jobname parameter description:
    The name of the VTAM started task for the UDP ports used for
    Enterprise Extender (EE) network connections.
    Also, add this note to the SAF keyword description:
    Note: The SAF keyword is ignored when VTAM opens a UDP port for
    Enterprise Extender (EE) network connections.  However, it can
    still be used to prevent other address spaces that are using
    the same name as the VTAM started task from opening the port.
    ==============================================================
    In Chapter 2. TCP/IP Profile Statements (PROFILE.TCPIP), under
    BEGINROUTES Statement and the GATEWAY Statement, in the Usage
    Notes section, replace the text only for the bullet beginning
    with "Static indirect routes cannot be added..." with the
    following text:
    Static indirect routes cannot be added to the routing table if
    a direct route does not already exist in the routing table to
    the first hop IP address. To ensure that the indirect static
    routes are processed as expected, code the direct route for the
    first hop gateway prior to the indirect route.
    ===============================================================
    In Chapter 17. OS/390 UNIX Policy Agent and SLA Subagent, under
    ServicePolicyRules Statement, make the following changes to the
    SourcePortRange and DestinationPortRange descriptions.
    
    In SourcePortRange - change second paragraph to:
    SourcePortRange contains the port range of the local 390 host
    that are communicating with the remote hosts.
    
    In DestinationPortRange - change the first paragraph to:
    The remote port range. This field consists of two port numbers,
    separated by a space, where the first port number is less than
    or equal to the second port number. The default is 0, which is
    all inclusive.
    
    And change the second paragraph to:
    DestinationPortRange contains the port range of the
    remote hosts that are communicating with the local 390 host.
    ===============================================================
    In Chapter 25. SMTP Server, under NJENODENAME Statement,
    add the following Usage Note:
    The NJENODENAME statement if specified must precede any of
    the following statements, ALTNJEDOMAIN, MAILER, NJEDOMAIN,
    and SMSGAUTHLIST in the SMTP Configuration Data Set.
    ===============================================================
    In Chapter 25. SMTP Server, under SMTP Configuration Data Set
    Statements, in MAXMAILBYTES Statement, add the following to
    the second Usage Note:
    This may vary with configuration of DF/SMS on your system.
    However, in general the allocation used for the NOTE data sets
    is equivalent to specifying SPACE=(6233,(aaaaa,bbbb)), where
    aaaa=round((MAXMAILBYTES/4000)+1) and bbbb=round(aaaa/2).
    ===============================================================
    In Chapter 11. Telnet, under SCANINTERVAL and TIMEMARK
    Statements, add the following Usage Note:
    .
    The smallest SCANINTERVAL value specified in the profile
    is used to determine how often all connections are checked.
    A very small SCANINTERVAL specified anywhere in the profile
    can cause frequent checking of all connections, not only
    the connections mapped to that PARMGROUP or Port where the
    value was specified. Refer to the scaninterval and timemark
    information in the Timer section of IP Configuration Guide
    for more details.
    ==============================================================
    

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II13406

  • Reported component name

    PA LIB INFO ITE

  • Reported component ID

    INFOPALIB

  • Reported release

    001

  • Status

    INTRAN

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2002-09-12

  • Closed date

  • Last modified date

    2004-06-24

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels



Rate this page:

(0 users)Average rating

Document information


More support for:

z/OS family

Software version:

001

Operating system(s):

MVS, OS/390, VSE/ESA, z/OS, z/VM

Reference #:

II13406

Modified date:

2004-06-24

Translate my page

Machine Translation

Content navigation