WebSphere Application Server V7.0: Concepts ... - IBM Redbooks

► MEMLIMIT setting in the JCL or in the PARMLIB member SMFPRMxx.
It specifies the limit on the use of virtual storage above 2 GB for a single
address space. If you specify a JVM heap greater than 2 GB, it may extend up
into this range. A value of MEMLIMIT=NOLIMIT means it will not be limited
above the 2 GB bar.
Message BBOO0331I is issued during server startup to tell you what
MEMLIMIT value was used for the address space, and where it came from
(an exit, JCL, and so forth).
System exits
Make sure that the IEFUSI- and JES2/JES3 exits defined on your z/OS operating
system do not limit the virtual region size for the WebSphere Application Server
address spaces.
14.4 Load modules in the HFS
14.4.1 Overview
Note: Although this modification/check is stated in the installation guide, there
is sometimes the tendency to skip over basic steps when you already have a
version of the WebSphere Application Server installed on your system.
However due to the theoretically larger heap sizes the values needs to be
adjusted in most environments.
This section describes the new way that z/OS components are installed in
WebSphere Application Server for z/OS V7.0.
In previous releases of WebSphere Application Server for z/OS the product was
shipped as both HFS content and z/OS datasets. This was different from the
other platform packaging. It also required two sets of executables to be kept in
sync. If not kept in sync, difficult-to-debug code-level-mismatch problems could
occur.
In WebSphere Application Server for z/OS V7.0, the load modules ship in the
AppServer/lib directory with the rest of the runtime. This change reduces the
installation and management complexity, and eliminates a common source of
errors.
436 WebSphere Application Server V7.0: Concepts, Planning, and Design