II13647: Z/OS CS V1R4: SC31-8776-02 IP CONFIGURATION REFERENCE TCPIPINFO BOOKAPAR (CONT OF II13245)

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

  • =============================================================
    In Chapter 13. File Transfer Protocol (FTP), under the
    FTPOSTPR user exit section, in the paragraph that starts with:
    The following parameter list is passed to FTPOSTPR:
    add this note below +72's value description:
    Note: Anything that was written to the scratch pad by FTPOSTPR
    prior to the completion of the USER/PASS command is lost.
    
    n the same chapter, under the FTCHKJES user exit section,
    in the paragraph that contains:
    The following parameter list is passed to FTCHKJES:
    add this note below +56's value description:
    Note: Anything that was written to the scratch pad by FTCHKJES
    prior to the completion of the USER/PASS command is lost.
    =============================================================
    In Chapter 23. 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 2. TCP/IP profile (PROFILE.TCPIP) and configuration
    statements, under the GATEWAY statement, in the Gateway Default
    Network Specification: section of the syntax diagram, change to:
    
     |_ _DEFAULTNET_ __first_hop__link_name__max_packet_size__0__>
       |_DEFAULT____|                       |_DEFAULTSIZE__|
    
    
    Add the following parameter description to the list:
    
    
    Specifies the default to use for any network not explicitly
    routed. DEFAULTNET can be specified only once. For the
    DEFAULTNET keyword to take effect, you must specify a GATEWAY
    statement that defines the route to the first_hop.
    
    Add the following under the DEFAULT parameter description:
    
    There is no difference between a DEFAULT route and a DEFAULTNET
    route, and that the precedence is determined by the order in
    which the routes are coded within the GATEWAY statement.
    =============================================================
    In Chapter 19. z/OS UNIX System Services 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 28. SMTP Server, under NJENODENAME Statement, add
    the following note after the first paragraph:
    Note: NJENODENAME is location sensitive.
    =============================================================
    In Chapter 2. TCP/IP Profile (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 Chapter 11. TN3270 Telnet Server, in the Telnet parameter
    statements table, change LUSSESSIONPEND and NOLUSSESSIONPEND
    to LUSESSIONPEND and NOLUSESSIONPEND.
    =============================================================
    In Chapter 2. TCP/IP profile (PROFILE.TCPIP) and configuration
    statements, 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 13. File Transfer Protocol (FTP), under the
    PORTCOMMAND statement, change the first paragraph to:
    Use the PORTCOMMAND statement to specify whether the PORT
    command will be accepted or rejected.  If REJECT is coded,
    this will limit the use of commands such as GET, PUT, MPUT,
    MGET and APPEND in PROXY mode.  If not in PROXY mode and REJECT
    is coded, this will cause the ftp server to use the same
    ephemeral port for the data connect that is used for the control
    connection.  This will cause delays when issuing multiple
    commands that use the data connection.
    =============================================================
    In Chapter 2. TCP/IP profile (PROFILE.TCPIP) and configuration
    statements, 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 (PROFILE.TCPIP) and configuration
    statements, 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 Appendix D. SMF Type 119 Records, change the last example
    in the first section from: EZASMF77 FTP=YES API=YES TELNET=YES
    HEADER=YES STAT=YES to:
    EZASMF77 FTP=YES,API=YES,TELNET=YES,HEADER=YES,STAT=YES
    =============================================================
    In Chapter 5. TCPIP.DATA Configuration Statements, under
    RESOLVERUDPRETRIES Statement, add the following Usage Note:
    A RESOLVERUDPRETRIES value of 0 indicates that the resolver
    should not attempt to contact any name servers.
    =============================================================
    In Chapter 2. TCP/IP profile (PROFILE.TCPIP) and configuration
    statements, in INTERFACE statement - IPAQENET6 interfaces
    statement, change the syntax diagram as follows:
    1. Add a continuation < to the end of the first line.
    2. Delete this line:
    
    >--| Interface Definition |------------------------><
    =============================================================
    In Appendix D. SMF type 119 records, under UDP Socket Close
    Record, add a third note:
    The local IP address will be 0.0.0.0 unless the application
    explicitly binds to a local IP address on this socket.
    =============================================================
    In Chapter 2. TCP/IP profile (PROFILE.TCPIP) and configuration
    statements, in the Modifying section, under DYNAMICXCF, remove
    the following:
    To change the IP address, all the XCF devices must first be
    stopped. Issue Display TCPIP,procname,NETSTAT,DEV to get a
    list of all of the currently defined devices. The names of
    devices generated by XCF Dynamics can either be IUTSAMEH or
    the cpname of another VTAM in the sysplex. After all of the
    names have been determined, issue VARY TCPIP,,STOP commands
    for each of the devices. After all the devices have been
    stopped, respecify the IPCONFIG DYNAMICXCF statement with
    the new IP address.
    ==============================================================
    In Chapter 2. TCP/IP profile (PROFILE.TCPIP) and configuration
    statements, 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 (PROFILE.TCPIP) and configuration
    statements 27, 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 19. z/OS UNIX system services Policy Agent and
    SLA subagent, in 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 28. 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 28. SMTP Server, under the Secure Statement,
    add the following Usage Note:
    Do not use the GLOBALTCPIPDATA file and SECURE, if you
    want to use a different domain origin then what is specified
    in the GLOBALTCPIPDATA file.  The domain origin that is
    specified in the GLOBALTCPIPDATA file will be used in the
    MAIL FROM statement.
    ===========================================================
    In Chapter 13. File Transfer Protocol (FTP), under the
    ANONYMOUS statement, under Usage Notes, change the following:
    If you specify ANONYMOUS without a user ID:
    - The user ID ANONYMOUS must be defined and must have a z/OS
    UNIX
    segment defined or defaulted.
    to
    
    If you specify ANONYMOUS without a user ID:
    - The user ID ANONYMO must be defined and must have a z/OS UNIX
    segment defined or defaulted.
    ================================================================
    In Chapter 13. File Transfer Protocol (FTP), under FTPLOGGING
    statement, add this Tip to the TRUE parameter description:
    Tip: If TRUE is used, a long delay in login processing might
    occur
    because the FTP server will issue a DNS query to resolve the
    remote
    host IP address.
    ===============================================================
    In Chapter 30. SNTP daemon, add this Restriction to the end
    of the first section:
    Restriction: If using AUTOLOG to start SNTPD, code NOAUTOLOG
    on the port statement for SNTPD.  There is a timing window
    where SNTPD brings down the listen on port 123 and if AUTOLOG
    checks for the listen, AUTOLOG will cancel SNTPD.
    ===============================================================
    In Chapter 11. TN3270 Telnet Server, in Table 17. Device type
    and logmode table. add this row above LINEMODE:
    IBM-DYNAMIC         ,D4C32XX3
    ===============================================================
    In Chapter 13. File Transfer Protocol (FTP), under
    ASATRANS statement, add this sentence after the first
    one in the section:
    Refer to "Using Optional Control Characters" in DFSMS:
    Using Data Sets for a discussion of ANSI control characters.
    ===============================================================
    In Chapter 28. SMTP server, under RESTRICT statement, change the
    syntax diagram parameter from TRANSFERTO to TRANSFERTO_touserid.
    Change the parameter name in the list to TRANSFERTO_touserid.
    Also, change the description of userid from "of the user." to
    "of the restricted users."
    ===============================================================
    In Chapter 2. TCP/IP profile (PROFILE.TCPIP) and configuration
    statements, add the following to the end of the VLANID id parame
    description for the DEVICE and LINK statement MPCIPA devices:
    =====================================================
    For general networking hardware attachment information and
    considerations associated with the IBM zSeries platform,
    refer to the following Web site:
    http://www.ibm.com/support/docview.wss?rs=852&uid=swg27005024
    ================================================================
    Additionally, add the above sentence under INTERFACE statement
    - IPAQENET6 interfaces at the end of the NONROUTER and VLANID id
    parameter descriptions.
    ===============================================================
    In Chapter 28. 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. TN3270 Telnet Server, 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.
    ===========================================================
    In Chapter 11. TN3270 Telnet Server, under Rules for LU name
    specification add the following rule:
    .
    The ascending order of characters is 0-9, A-Z, @, #, $.
    ============================================================
    In Chapter 2. TCP/IP profile (PROFILE.TCPIP) and configuration
    statements, under the PORTRANGE statement, change the first
    paragraph under jobname parameter description to the following:
                                                                  .
    This specifies the MVS job name that can use the port. For UDP
    and TCP only one job name can be associated with a port. If a
    TCP port needs to be reserved for multiple jobs names, see the
    Port Statement.
    

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

  • APAR number

    II13647

  • 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

    2003-07-23

  • Closed date

  • Last modified date

    2005-06-16

  • 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

Add comments

Document information


More support for:

z/OS family

Software version:

001

Operating system(s):

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

Reference #:

II13647

Modified date:

2005-06-16

Translate my page

Machine Translation

Content navigation