PM48924: HARD LOOP IN TCPIP ENCOUNTERED AFTER ISSUING OBEYFILE ON IPSEC STATEMENT BLOCK WITH IPSECRULE/IPSEC6RULE BUT WITHOUT ENDIPSEC

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• TCPIP was started with IP security definitions in the TCPIP
  profile. A VARY TCPIP,,OBEYFILE was issued to update the IPSEC
  statement block with new IPSECRULE/IPSEC6RULE definitions. The
  ENDIPSEC statement in the block was missing, resulting in a
  hard loop for the TCPIP address space with the following message
  issued continuously to the system console:
  
    EZZ0318I END OF FILE WAS FOUND ON LINE 8 AND IPSECRULE, OR
             IPSEC6RULE OR ENDIPSEC WAS EXPECTED
  
  The loop occurs in the IP security keyword parser in
  csect EZACFPSE as part of the TCPIP configuration component.
  

Local fix

• Ensure that the OBEYFILE used for the IP security definitions
  contains a complete block of IPSEC/ENDIPSEC statements.
  
  
  
  KEYWORDS:
  EZACFPSE IPSEC ENDIPSEC IPSECRULE IPSEC6RULE OBEYFILE SECURITY
  IPSECURITY TCPIP PROFILE LOOP EZZ0318I
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release(s)  11, 12, and   *
  *                 13 IP                                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Hard loop in TCPIP address space        *
  *                      during syntax error processing for      *
  *                      stack profile dataset                   *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The TCPIP stack was started using a profile containing
  IP security definitions.  A change was later made to
  update these definitions.  An inadvertent error resulted
  in a missing ENDIPSEC statement for an IPSEC statement
  block.  When an OBEYFILE was issued for this profile,
  the TCPIP stack went into a hard loop issuing the
  following message to the system console:
  
  EZZ0318I END OF FILE WAS FOUND ON LINE 8 AND IPSECRULE, OR
           IPSEC6RULE OR ENDIPSEC WAS EXPECTED
  +-------------------------------------------------------------+
  + Please check our Communications Server for OS/390 homepages +
  + for common networking tips and fixes.  The URL for these    +
  + homepages can be found in Informational APAR II11334.       +
  +-------------------------------------------------------------+
  

Problem conclusion

• Module EZACFPSE has been amended to correctly process
  the error condition where an IPSEC block is coded without
  an ending ENDIPSEC statement.
  
  * Cross Reference between External and Internal Names
  

Temporary fix

• *********
  * HIPER *
  *********
  

Comments

APAR Information

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

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

  UK72619 UK72620 UK72621

Modules/Macros

• EZACFPSE
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R1B0 PSY UK72619

     UP11/11/02 P F111

• R1C0 PSY UK72620

     UP11/11/02 P F111

• R1D0 PSY UK72621

     UP11/11/02 P F111

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.