PI47559: A LARGE AMOUNT OF COMMON STORAGE IS BEING USED WHEN THERE IS A L ARGE NUMBER OF WEBSPHERE CELLS ON A SINGLE Z/OS SYSTEM.

8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.17: WebSphere Application Server V8.5.5 Fix Pack 17
8.5.5.20: WebSphere Application Server V8.5.5.20
8.5.5.18: WebSphere Application Server V8.5.5 Fix Pack 18
8.5.5.19: WebSphere Application Server V8.5.5 Fix Pack 19
8.5.5.16: WebSphere Application Server V8.5.5 Fix Pack 16
8.5.5.21: WebSphere Application Server V8.5.5.21

APAR status

• Closed as program error.

Error description

• WebSphere Application Server for z/OS loads a separate copy of
  load module (BBODPCRT) into common storage for each node,
  including the Daemon. For a single cell with a Daemon,
  Deployment Manager node, and Application Server node, that is
  three copies of BBODPCRT per cell. Systems with a large
  number of cells configured use a large amount of common
  storage.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server for z/OS V8.5                        *
  ****************************************************************
  * PROBLEM DESCRIPTION: Significant amount of common storage    *
  *                      used for bbodpcrt when there is a       *
  *                      large number of cells on a single       *
  *                      z/OS system even though they are        *
  *                      at the same fixpack level.              *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Systems with a large number of WebSphere Application Server for
  z/OS cells configured with multiple nodes in them use a
  significant amount of common storage for module bbodpcrt. This
  is because the daemon loads a copy of bbodpcrt from the HFS
  into common storage for use by the cell and a copy of bbodpcrt
  for each node is loaded from the HFS into LPA. For a single
  cell with a Daemon, deployment manager node, and application
  server node, that is three copies of bbodpcrt.
  

Problem conclusion

• Updated the code to attempt to load bbodpcrt from LPA using a
  fixpack specific name. If found the LPA copy will be used
  instead of loading bbodpcrt from the HFS into LPA. This allows
  the LPA copy to be shared thus reducing the number of copies
  specifically loaded from the HFS into LPA.
  
  The fixpack specific name for 8.5.5.8 is BBO85508.
  
  To verify the fixpack specific name you can look at the build
  level string in the bbgubinf dll. For 8.5.5.8 the build level
  string will contain BBODPCRT=BBO85508.
  
  For the fixpack specific named LPA copy to be loaded
  and used, lib/s390-common/bbodpcrt needs to be copied
  from the HFS into a dataset, the member renamed to
  the fixpack level specific name, and then put into LPA.
  
  The following is an example command to copy bbodpcrt
  from the HFS into a partitioned dataset.
  cp -Xv /V8R5/lib/s390-common/bbodpcrt "//'HLQ.LOAD'"
  
  Note when changing fixpack levels, bbodpcrt must be put into
  LPA by its fixpack specific level name before starting the
  daemon and servers. If bbodpcrt was not put into LPA before
  starting the daemon and servers, the cell must be stopped and
  restarted at a previous fixpack level,  the fixpack
  specific level named bbodpcrt added to LPA and then restart
  the cell at the new fixpack level.
  
  Note when running with an ifix that has native changes,
  the fixpack specific named bbodpcrt in LPA will not be used.
  
  Note do not delete the fixpack specific named bbodpcrt
  from LPA unless you are sure there are no servers or
  daemons currently using it. Deleting bbodpcrt while it is
  still in use will cause abends.
  
  APAR PI47559 is currently targeted for inclusion in Fix Pack
  8.5.5.8 of WebSphere Application Server V8.5.
  
  Please refer to the Recommended Updates page for delivery
  information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  
  In addition, please refer to URL:
  http://www.ibm.com/support/docview.wss?rs=404&uid=swg27006970
  for Fix Pack PTF information.
  

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

• Fixed component name

  WEBSPHERE FOR Z

• Fixed component ID

  5655I3500

Applicable component levels

• R850 PSY

     UP