II12868: HIGH ECSA USAGE WITH *MASTER* ADDRES SPACE ON SYSTEMS RUNNING 'WAS 4.0 FOR Z/OS AND OS/390' MODULE PREFIX BBO*

APAR status

• INTRAN

Error description

• ECSA usage on systems which run WAS 4.0 for z/OS and OS/390 or
  Component Broker Release 3.02 is traditionally high.  This is
  due to the fact that the product modules, (prefixed with
  BBOxxxx) being loaded into the LPA area.
  .
    WebSphere Application Server Enterprise Edition for OS/390
  (5647BSS00)  and WebSphere Application Server V4.0 for z/OS
  and OS/390 (5655A9801), (both referred to as WebSphere
  Server from here on) customers should be aware of the
  storage requirements for the product runtime code.
    The WebSphere Application Server product runtime modules
  will be placed in LPA after IPL of the system.  The modules
  need to be added to LPA after IPL, LPALSTxx cannot be used.
    This is required because the modules are shipped in PDSE
  datasets.
  .
    If CSA is not increased prior to IPL and thus prior to
  loading WebSphere Application Server modules into LPA, this
  will result in ECSA being used to hold the modules and the
  system could run out of ECSA.  CSA must be increased prior to
  the IPL of the system where the WebSphere Application Server
  modules will be placed in LPA.  The customer should also
  monitor ECSA after this happens the modules are added, to
  ensure there is enough CSA allocated.
  .
  The following instructions appear in the WebSphere
  Application Server V4.0 for z/OS and OS/390 Installation
  and Customization book, GA22-7834, on this subject.
  .
  WebSphere for z/OS differs from previous application servers
  in its use of memory. WebSphere for z/OSs implementation
  takes advantage of OS/390 or z/OSs efficient memory
  management, but, like many of todays newer application
  servers and languages, it is a large consumer of memory. You
  may experience some changes from your existing memory usage
  patterns. This section outlines changes you might need to
  make. Follow these recommendations:
  .
  1. We recommend you dynamically load the run time in the link
  pack area (LPA) because the size of the load modules are
  large, and many address spaces need to refer to those load
  modules. The load modules for the run time comprise about
  200 MB in size. Remember to increase the size of your CSA
  page data set accordingly.
  .
  Because you are using dynamic LPA, you will run out of ECSA
  after an IPL if you do not increase CSA at IPL time. You
  should monitor ECSA after dynamically loading the run time
  into LPA.
  .
  2. If you choose to place the load modules in steplib or in
  the link list, you must allow for the additional 200 MB as
  part of each address spaces region.
  A typical WebSphere for z/OS basic installation consists of
  9 address spaces, each of which reference most of the 200 MB
  of load modules.
  .
  3. In addition to placing the load modules in the link pack
  area, give each address space a dynamic area of at least
  128 MB.
  .
  4. Check to see whether your installation limits region sizes
  through the IEFUSI exit, JES exits, or TSO segment defaults.
  All of the WebSphere for z/OS JCL procedures are shipped with
  a default REGION=0M, which means you should give them as
  large a region as possible. If you choose to run from the
  link pack area, you will need a minimum of 128 MB for the
  dynamic area.
  If you choose to run from the link list you will need a
  minimum of 328 MB (200 MB for load modules and 128 MB for
  the dynamic area).
  .
  If your IEFUSI exit routine limits the maximum region to a
  size smaller than what you need (128 MB minimum when you run
  from the link pack area or 328 MB minimum when  you run from
  the link list), you will get an abend. To fix the problem,
  either change the IEFUSI exit routine to allow a larger
  default region, or change the JCL REGION= parameter to the
  size needed.
  .
  Your installation may limit (control) the specification of
  REGION=, usually through the JES2 EXIT06 exit or the JES3
  IATUX03 exit. If so, relax this restriction for the
  WebSphere for z/OS JCL procedures.
  .
  Finally, check your TSO segment default region size and
  change, if necessary.
  .
  *** IMPORTANT NOTE ***
  When using SETPROG to load the BBOxxx modules into the LPA,
  be sure to purge modules with the same name as those from
  BBO.SBBOLPA, BBO.SBBOLOAD, or BBO.SBBOLD2 that are already
  in the LPA.
  Failure to do so will result in an increase in ECSA usage,
  due to the fact that there will be duplicate copies of these
  modules in LPA.
  

Local fix

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