IBM Support

PQ04110: PRIMARYINTERFACE STATEMENT RESTRICTS ORDER OF OFFLOAD APIS IN THE HOME LIST.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • PRIMARYINTERFACE statement restricts the order of Offload API
    links in the HOME list.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All users of TCP/IP for MVS; Offload         *
    *                 and HOME                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION: PRIMARYINTERFACE restricts use of       *
    *                      Offload API link.   In addition,        *
    *                      correct displaying of msgEZB7843E.      *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    If an Offload link is not the first entry in the HOME list, the
    API link is not used. This limits the benefit of Offload when
    multiple links are defined.
    
    If VARSUBNETTING option is specified in ASSORTEDPARMS and
    there are no subnet mask mismatches in BSDROUTINGPARMS, message
    EZB7843E is inadvertently issued.
    The ASSORTEDPARMS section needs to be placed BEFORE
    the BSDROUTINGPARMS section of the TCPIP.Profile if
    using the VARSUBNETTING parm.
    

Problem conclusion

  • The PRIMARYINTERFACE statement was intended to allow an Offload
    link to be first in the HOME list. In order that the Offload
    link can be used in any order and in combination with VIPA
    links, Offload links may now be placed in the HOME list. This
    removes the usefulness of PRIMARYINTERFACE. The same logical
    result can be achieved by placing the link that should be first
    in the HOME list in the first position.
    
    PRIMARYINTERFACE will still function as before and Offload links
    not positioned in the HOME list will be placed at the end of the
    list. This preserves the previous function. However, a new
    message EZB8095W will be issued if a PRIMARYINTERFACE statement
    is found, reminding the programmer that the same effect is seen
    by placing that link first in the HOME list.
    
    Offload API links will be used to communicate when the Offload
    link is used for connections.
    
    The IP address for Offload links is taken from the LINK
    statement and not the HOME entry. The IP address in the HOME
    entry for an Offload link is ignored.
    
    In addition, message EZB7843E was inadvertently displayed when
    there are no subnet mask mismatches in BSDROUTINGPARMS. While no
    harm is being done to TCPIP processing, the circumvention was to
    code the VARSUBNETTING option even though fixed-length subnet
    masks were coded. Code was modified to prevent displaying this
    message when VARSUBNETTING is not specified. Also, VARSUBNETTING
    option requires that ASSORTEDPARMS statement be defined before
    the GATEWAY and BSDROUTINGPARMS statements to ensure proper
    processing of subnet masks. A new message EZB7844E will be
    displayed in the event of incorrect placement of ASSORTEDPARMS.
    
                                  - - -
             THE FOLLOWING TCPIP PUBLICATION(S) WILL BE UPDATED:
                                  - - -
    TITLE: TCP/IP V3R2 for MVS: Messages and Codes (SC31-7132-02)
    
    ----------------------------------------------------------------
    PAGES:
    CHAPTER:            TOPIC: "TCPIP Messages"
    PARAGRAPH:          FIGURE:
    ADD:
      EZB8095W  Link linkname added to top of HOME list,
                consider adding as first HOME entry
      Severity: Warning
      Explanation: A PRIMARYINTERFACE statement was found in the
      Profile dataset. While PRIMARYINTERFACE is supported it can be
      replaced by placing the LINK as the first entry in the HOME
      list.
      System Action:  TCPIP continues.  linkname is placed at the
      top of the HOME list.
      User or Operator Action: None
      System programmer Action:  The message can be bypassed by
      placing linkname in the HOME list.
      Procedure Name: ProcessPrimaryInterfaceStatement
    
    ----------------------------------------------------------------
    CHANGE: Message description for EZB7844 (existing description
            is obsolete)
    TO:
      EZB7844E VARSUBNETTING option requires ASSORTEDPARMS
               to be placed before GATEWAY and BSDROUTINGPARMS
      Severity: Recoverable Error
      Explanation: VARSUBNETTING option was found in ASSORTEDPARMS
      statement and variable-length subnet masks coded in the
      GATEWAY and BSDROUTINGPARMS statements may have failed to be
      processed correctly. The subnet masks in the GATEWAY statement
      may be flagged with errors and for the subnet masks in the
      BSDROUTINGPARMS, they are changed to fixed- length subnet
      masks.
      System Action: TCPIP continues.
      User or Operator Response: None
      System Programmer Response: Move ASSORTEDPARMS statement to
      before GATEWAY and BSDROUTINGPARMS statements for correct
      processing of variable-length subnet masks.
      Source Data Set: TCPARSE
      Procedure Name: ParseOption
    
    ----------------------------------------------------------------
    
    TITLE: TCP/IP V3R2 for MVS: Customization and Administration
                                Guide (SC31-7134-04)
    ----------------------------------------------------------------
    PAGES: 58
    CHAPTER:            TOPIC: "ASSORTEDPARMS Statement"
    PARAGRAPH:          FIGURE:
    CHANGE: VARSUBNETTING parameter
    
      Enables variable subnetting and supernetting support in
      TCP/IP.  Variable-length subnet masks may be coded on the
      GATEWAY and BSDROUTINGPARMS statements.  Also, this option
      allows variable-length subnet masks to be included in RIP
      Version 2 packets via RouteD application for dynamic
      updates to the IP routing table.  The default is no
    | variable subnetting.  When using this parameter, the
    | ASSORTEDPARMS statement must be placed before the GATEWAY
    | and BSDROUTINGPARMS statements.
    
    ----------------------------------------------------------------
    
    * Cross Reference between External and Internal Names
    EZAAA00K (MSTCP   )  EZABB02Y (TCPARSE )  EZABB035 (TCPREQU )
    

Temporary fix

Comments

  • ×**** AE97/07/14 FIX IN ERROR. SEE APAR PQ06354  FOR DESCRIPTION
    ×**** PE97/07/29 FIX IN ERROR. SEE APAR PQ06897  FOR DESCRIPTION
    

APAR Information

  • APAR number

    PQ04110

  • Reported component name

    TCP/IP V3 MVS

  • Reported component ID

    5655HAL00

  • Reported release

    320

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    YesSpecatt / New Function / Xsystem

  • Submitted date

    1997-05-02

  • Closed date

    1997-06-29

  • Last modified date

    1997-12-16

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

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

    UQ06759 PQ06176

Modules/Macros

  • EZAAA00K EZABB02Y EZABB035
    

Publications Referenced
SC31713203    

Fix information

  • Fixed component name

    TCP/IP V3 MVS

  • Fixed component ID

    5655HAL00

Applicable component levels

  • R320 PSY UQ06759

       UP97/07/29 P F707

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"320","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSCY4DZ","label":"DO NOT USE"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"320","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
16 December 1997