II12499: Z/OS CS V1R2: SC31-8776-01 IP CONFIGURATION REFERENCE TCPIPINFO BOOKAPAR

APAR status

• INTRAN

Error description

Local fix

• ===========================================================
  INFOAPAR for z/OS Communications Server IP Configuration
  Reference V1R2. SC31-8776-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 the Index, disregard (remove) the index entry for
  OTELNETD:  invoking otelnetd 852. This entry was in error.
  =========================================================
  In Chapter 6. OMPROUTE, section Environment Variables, add
  the following before the OMPRPUTE_DEBUG_FILE paragraph:
  
  OMPROUTE_OPTIONS
  
  The OMPROUTE_OPTIONS variable is used by OMPROUTE to set
  various controls for OMPROUTE processing.  Currently only
  the hello_hi option is supported.  The syntax of this new
  variable is OMPROUTE_OPTIONS=hello_hi
  
  The default value for OMPROUTE_OPTIONS is NO hello_hi. This
  will allow normal OMPROUTE processing of OSPF packets in the
  order they are received.
  
  Specifying OMPROUTE_OPTIONS=hello_hi will change the way
  OMPROUTE processes the OSPF Hello packets.  These packets
  will be given a higher priority than other updates and
  processed by the first available OMPROUTE task ahead of
  other received packets.  Prior to specifying this parameter,
  customers must be cognizant of the impact to their network of
  processing hello packets out of the received order sequence.
  ===========================================================
  In Chapter 30. Remote Execution, under RXUEXIT User Exit Sample,
  add the second and third lines shown below to the sample (the
  first and fourth lines are included here ONLY to indicate where
  to insert the second and third lines).
  
  RXUEXIT CSECT                 Establish the RXUEXIT csect
  RXUEXIT AMODE 31
  RXUEXIT RMODE ANY
          USING RXUEXIT,12      Establish code addressability
  ===============================================================
  In Chapter 1. Configuration Data Sets, Table 1. TCP/IP
  Configuration Data Sets, change the "Copied From" column in row
  PAGENT.CONF from SEZAINST(PAGENT) to
  /usr/lpp/tcpip/samples/pagent.conf
  and change the RSVPD.CONF row, Copied From column from:
  No sample provided to: /usr/lpp/tcpip/samples/rsvpd.conf
  ==============================================================
  In Chapter 2. TCP/IP Profile (PROFILE.TCPIP), add the following
  note to the SMFCONFIG Statement Usage Notes:
  If running with multiple stacks and SMF client recording is
  desired, ensure that the SMFCONFIG statement is defined in
  all stacks.
  ===============================================================
  In Chapter 2. TCP/IP Profile Statements (PROFILE.TCPIP), under
  the IPCONFIG Statement Usage Notes, add the following note
  between the third and fourth bullet:
  When using Dynamic XCF for Sysplex configuration, code
  XCFINIT=YES in the VTAM start options. This ensures that
  XCF connections will be established to other VTAMs in a sysplex
  at VTAM initialization. Refer to z/OS IBM Communications
  Server: SNA Resource Definition Reference for directions for
  coding the XCFINIT VTAM start option. The DISPLAY NET,VTAMOPTS
  can be used to determine the XCFINIT setting.
  ===============================================================
  In Chapter 2. TCP/IP Profile (PROFILE.TCPIP), under the PORT
  Statement section, add the following Usage Note:
  If you use the procname.identifier method of starting an
  application, specify the identifier as the jobname on the PORT
  reservation statement.
  =============================================================
  In Chapter 2. TCP/IP Profile (PROFILE.TCPIP), under
  BSDROUTINGPARMS Statement, add the following to the dest_addr
  parameter description: If you specify the destination address
  and are using OROUTED,the other end of the point-to-point
  link must be running RIP also.
  ============================================================
  In Chapter 2. TCP/IP Profile (PROFILE.TCPIP), under
  PRIMARYINTERFACE Statement, add the following to the Usage
  Note list: If you want to code a Dynamic VIPA as a
  PRIMARYINTERFACE, it must be done by the OBEYFILE, because
  of the way Dynamic VIPA links are added.
  ===============================================================
  In Chapter 2. TCP/IP Profile (PROFILE.TCPIP), under the AUTOLOG
  Statement, add the following to the end of the first paragraph:
  Do not use AUTOLOG to automatically start generic servers (those
  without affinity to a specific stack) such as FTP and the BIND 9
  name server. Instead, use some other automation outside of
  AUTOLOG to automatically start generic servers.  For more
  information about generic servers, refer to the z/OS
  Communications Server: IP Configuration Guide.
  =============================================================
  In Chapter 2. TCP/IP Profile (PROFILE.TCPIP), DEVICE and LINK
  Statement CLAW Devices, add the following P2MP parameter
  to the LINK syntax:
  >>--LINK ...--device_name-------......
                              |    |
                              -P2MP-
  
  Add the following to the parameter description list:
  P2MP
       Treat this CLAW link as a point-to-multipoint link.
       The default is point-to-point.
  
  Add this to the Usage notes list:
  Point-to-multipoint RIP neighbors with which omproute will
  exchange routing information are learned via RIP_INTERFACE
  NEIGHBOR statements or upon receipt of a RIP Update from the
  same subnet neighbor.
  ==============================================================
  In Chapter 19. z/OS UNIX System Services Policy Agent and SLA
  Subagent, under the SetSubnetPrioTosMask Statement section,
  change the value 0 to 4 in the syntax diagram and in the second
  paragraph under the parameter description of PriorityTosMapping
  as follows: "...to a device priority value of 4, and a user...".
  ==============================================================
  In Chapter 13. File Transfer Protocol (FTP), under the
  JESINTERFACELEVEL Statement, add this note after the third
  paragraph: Note: To use the FTP JES SAPPI interface, you need
  update authority.
  ===============================================================
  In Chapter 6. OMPROUTE, under the RIP_INTERFACE Statement
  parameter description for Send_Poisoned_Reverse_Routes, add the
  following as the last sentence:
  If NO is specified, OMPROUTE still uses split horizon.
  ===============================================================
  In Chapter 11. TN3270 Server Telnet, make the following changes:
  * Change the chapter title to TN3270 Telnet Server
  * Under CLIENTAUTH statement, Usage Note 1 - change
    TELENETGLOBALS to TELNETGLOBALS
  * Under MSG07 statement, Usage Notes-change TELENETGLOBALS to
    TELNETGLOBALS
  * Make same change as directly above for page 387
  * Under SNAEXT statement, Usage Note 1 - change TELENETGLOBALS
    to TELNETGLOBALS
  * Under ALLOWAPPL statement, last sentence under
    application_name parameter description should read: A single
    * should allow all applications.
  * Under LINEMODEAPPL statement, last sentence under
    application_name parameter description should read:
    "...followed by a 1 to 8 character application name.
  * Under LINEMODEAPPL statement, under the Client_Identifier
    parameter description, change the last statement to : If no
    client identifier is specified, then it is considered the
    NULL client identifier.
  * Under PRTMAP statement, change PORTMAP in the first sentence
    to PRTMAP
  * RESTRICTAPPL statement, the last sentence under
    application_name parameter description should read: A
    single * allows all users.
  * Under RESTRICTAPPL statement, the USERD user_id parameter,
    the last sentence should read: A single * allows all users.
  ==============================================================
  In Chapter 2. TCP/IP Profile (PROFILE.TCPIP), under the GATEWAY
  Statement section, change the second sentence under the DEFAULT
  parameter description to:
  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 11. TN3270 Server Telnet, under the DEBUG statement
  syntax diagram, move JOBLOG above the line and move CONSOLE
  below the line in the last section of the diagram.
  ==============================================================
  In Chapter 19. z/OS UNIX System Services Policy Agent and SLA
  Subagent, under the SetSubnetPrioTosMask Statement, add the
  following note between the first and second paragraphs:
  OSA Microcode level 3C is recommended for full hardware support
  of VLAN mapping.
  ==============================================================
  In Chapter 11. TN3270 Server Telnet, in Table 20, Client
  Identifier Types and Definitions, switch the definitions for
  DestIPGrp and DestIP.
  ==============================================================
  In Chapter 11. TN3270 Server Telnet, in TN3270E Statements,
  change the last Usage Note to:
  NOTN3270E is useful in the unlikely case there are a significant
  number of clients that cannot tolerate negotiating for a TN3270E
  connection. Most clients do not have a problem with the TN3270E
  specification, but in the unlikely case that some do, specify
  and map NOTN3270E to that set of clients.
  ==============================================================
  In Chapter 11. TN3270 Server Telnet, in SNAEXT Statements,
  change the last Usage Note to:
  NOSNAEXT is useful in the unlikely case there are a significant
  number of clients  that cannot tolerate the negotiation of these
  functions. Most clients do not have a problem with the SNAEXT
  specification in the server, but, in the unlikely case
  that some do, specify and map NOSNAEXT to that set of clients.
  ===============================================================
  In Chapter 2. TCP/IP Profile (PROFILE.TCPIP), under the GATEWAY
  statement, Note 3 change the first sentence to:
  When an incorrect GATEWAY statement entry is encountered, the
  remaining entries are ignored. Subsequent GATEWAY statements in
  the same profile or obeyfile are processed.
  =======================================================
  Chapter 19 zoS/390 UNIX System Services Policy Agent and SLA
  Subagent, under ServicePolicyRules Statement, add Usage Note:
  add this Usage Note:
  The weight of ServicePolicyRules is determined by the number
  of parameter are specified in the ServicePolicyRules. The
  parameters that affect this weight are:
  
  Source address
  Destination address
  Source port
  Destination port
  Interface
  Protocol
  Direction NOT equal to BOTH
  Policy scope NOT equal to BOTH
  In Chapter 23. Remote Print Server (LPD), add the following
  after Sample LPD Server Configuration Data Set (LPDDATA)
  
  
  Specifying LPD Server Parameters
  
  LPDDATA='data_set_name'
  Specifies the fully qualified name of the data set containing
  the LPD configuration statements. This data set can be
  sequential or a memeber of a PDS.
  
  LPDPRFX='PREFIX your_prefix'
  Specifies the high-level qualifier to be used for temporary data
  sets created by the LPD server. Include both the PREFIX
  keyword and your qualifier in the quoted string. The qualifier
  can be up to 26 characters. If it is blank, it defaults to the
  procedure name. The LPD task requires the authority to create
  and modify data sets with this prefix.
  
  DIAG='options'
  Specifies any of the following diagnostic options in a quoted
  string of keywords separated by blanks. For example:
  DIAG='VERSION TRACE'
  
  VERSION
  Displays the version number.
  
  TYPE
  
  Activates high-level trace facility in the LPD server.
  Significant events, such as the receipt of a job for printing,
  are recorded in the //SYSOUT DD data set specified in your
  LPD server cataloged procedure.
  
  TRACE
  
  Causes a detailed trace of activities within the LPD server
  to record in the //SYSOUT DD data set specified in your LPD
  server cataloged procedure. The detailed tracing can be also
  activated with the DEBUG statement in the LPD server configur-
  ation data set and with the TRACE command of the SMSG interface.
  
  Note: The JCL PARM= statement has a limit of 100 characters.
  ================================================================
  In Chapter 2. TCP/IP Profile (PROFILE.TCPIP), in the PORTRANGE
  Statement section, remove SHAREPort from the syntax diagram and
  also from the list of parameters.
  ==============================================================
  In Chapter 11. TN3270 Server Telnet, TELNETDEVICE Statement,
  add this under telnet_device_type:
  When defining a TELNETDEVICE telnet_device_type, do not code
  IBM in the prefix, although the result when issuing DISPLAY
  TELNET will display IBM.
  ================================================================
  In Chapter 2. TCP/IP Profile PROFILE.TCPIP), IPCONFIG Statement,
  add this note to the PERCONNECTION parameter description:
  Note: For more information about EE load balancing and standard
  logic for a UDP application, refer to z/OS Communications
  Server: SNA Network Implementation Guide.
  ================================================================
  In Chapter 11. TN3270 Telnet, TELNETDEVICE Statement, add this
  under telnet_device_type:
  When defining a TELNETDEVICE telnet_device_type, do not code
  IBM in the prefix, although the result when issuing DISPLAY
  TELNET will display IBM.
  ================================================================
  In Chapter 2. TCP/IP Profile (PROFILE.TCPIP), under GATEWAY
  Statement, change GATEWAY to GATEway in syntax diagram.
  

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

• 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