PM83736: SEVERAL RANGES OF VALUES FOR POOLLIMIT ARE BEING REJECTED

Obtain the fix for this APAR.

APAR status

• Closed as unreproducible in next release.

Error description

• Attempts to perform an OBEYFILE to update the value specified
  for POOLLIMIT on the GLOBALCONFIG statement may be rejected with
  the following error:
  
  EZZ0683I GLOBALCONFIG POOLLIMIT CONTAINS AN INCORRECT VALUE xxxx
  
  This error normally means that the value is outside of the
  acceptable range (10M to 2047M, or 0), or that it is a reduction
  from the current value which would cause pool (private) storage
  to become CONSTRAINED because of the current usage (as shown by
  the DISPLAY TCPIP,,STOR command).  However, none of these limits
  apply.
  
  For example:  Specifying 51M will work, but 52M will fail.
  

Local fix

• Ensure that the value specified provides the largest result for
  the following formula (use K specifications instead of M for
  the best results):
  
     MOD( nnn * 80, 4294967296 )
  
  Or, disable POOLLIMIT by specifying 0.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of the IBM Communications Server   *
  *                 for z/OS Version 1 Release(s) 13 IP          *
  ****************************************************************
  * PROBLEM DESCRIPTION: User issued a Vary Obeyfile command to  *
  *                      change a POOLLIMIT keyword using a      *
  *                      valid value, but got the following      *
  *                      message:                                *
  *                      EZZ0683I GLOBALCONFIG POOLLIMIT         *
  *                      CONTAINS AN INCORRECT VALUE             *
  *                      The same error message can also be      *
  *                      issued for ECSALIMIT problems.          *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  EZZ0683I message is issued for the following reason:
  When calculating 80% of the new value of the POOLLIMIT, the
  code first multiplies the new value by 80 and then divides by
  100. Only one register is used for the multiplication, so if
  the product is larger than 4 bytes, the overflow bytes are lost.
  The code then divides the 4 bytes by 100 so the resulting
  value could end up being less than the current value.
  +-------------------------------------------------------------+
  + 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

Temporary fix

Comments

• EZBTIGBL will be changed to correctly handle POOLLIMIT and
  ECSALIMIT values during profile processing.
  

APAR Information

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

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

  UK92927

Modules/Macros

• EZBTIGBL
  

Fix information

• Fixed component name

  TCP/IP V3 MVS

• Fixed component ID

  5655HAL00

Applicable component levels

• R1D0 PSY UK92927

     UP13/04/23 P F304

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.