Preparing z/OS to run WebSphere Application Server
Procedure
- Make sure that the UNIX System
Services environment is active and that the BPXPRMxx settings in effect
meet or exceed the following minimum values:
MAXTHREADS: 10000 MAXTHREADTASKS: 5000 MAXFILEPROC: 10000 MAXSOCKETS (AF_INET domain): 12000 SHRLIBRGNSIZE: 67000000 (134000000 recommended)
- Make sure that each WebSphere® Application Server for z/OS® server address space, as well as
OMVS or batch job address spaces that run Java™ virtual machines, have access to enough virtual memory below
the 2-gigabyte bar. (A Java virtual machine requires at least 500M of virtual memory, for example.)
All WebSphere
Application Server address spaces should be given at least 1024M of virtual memory.
To do this: Specify REGION=0 (or a suitably large value, such as 1500M) for all batch job, started task and WLM job steps for WebSphere Application Server.
Either specify MAXASSIZE(2147483647) or some similarly large value in BPXPRMxx to provide a large system-wide default address space size for Unix System Services address spaces, or set the ASSIZEMAX value in RACF® (or similar security system) for each WebSphere Application Server for z/OS client or server user ID, including IDs used to run the batch Postinstaller or similar processes:ALTUSER WASUTIL1 OMVS(ASSIZEMAX(1073741824)) to allow WASUTIL1 a 1-gigabyte address space
- If you use localization and alternate code pages with UNIX System
Services, make sure that all WebSphere Application Server
for z/OS server, administrator and client user IDs
(any user IDs that run WebSphere Application Server
for z/OS scripts) are run with environment variables
LANG and LC_ALL both set to the same locale based on code page IBM-1047.
Settings based on any other code page can cause the scripts to fail.
See Changing the Locale in the Shell in UNIX System Services User's Guide for more information.
- Make sure that the /tmp directory
has at least 20 megabytes of free space.
WebSphere Application Server for z/OS makes extensive use of the /tmp directory.
You can use the df -kP /tmp shell command to show the number of available 1K blocks in the /tmp directory HFS. Divide the number of available 1K blocks by 1024 to determine the number of megabytes of free space.
If your /tmp directory resides in a permanent read-write HFS, use the confighfs command in /usr/lpp/dfsms/bin to extend it as necessary. For example, the following command will add an additional 10 MB of space to the HFS in which /tmp resides:
/usr/lpp/dfsms/bin/confighfs -x 10m /tmp
If your /tmp directory resides in a temporary file system (TFS), modify the MOUNT statement in BPXPRMxx that defines it to add additional space. To define a 20 MB TFS and mount it at /tmp, for example, use the following MOUNT command:
MOUNT FILESYSTEM('/TMP') TYPE(TFS) MOUNTPOINT('/tmp') PARM('-s 20')Note: If you do not specify a space ('-s') value, then the undesirably small default of 1 megabyte will be used. - Determine the full dataset names of the following system
datasets used by WebSphere Application Server for z/OS:
- SCEERUN
- Language Environment® runtime library
- SCEERUN2
- Language Environment runtime library
- SIEALNKE
- System SSL runtime library
- SCLBDLL2
- 64-bit support code
Also, determine whether these datasets are in the system link pack area (LPA) or link list. Record this information on the worksheet.
- Make sure that all the following datasets are APF authorized:
- cee_hlq.SCEERUN
- cee_hlq.SCEERUN2
- sys_hlq.SIEALNKE
- clb.SCLBDLL2
- Make sure that any IEFUSI or JES2/JES3 exits on your system do not restrict WebSphere Application Server for
z/OS address spaces
to an address space size of less than 768 MB.
Each WebSphere Application Server for z/OS address space should have a region size of at least 768 MB. All WebSphere Application Server for z/OS cataloged procedures are shipped with a default of REGION=0M.
- Make sure that the TSO segment default region size for WebSphere Application Server for z/OS installer and administrator TSO user IDs is at least 768 MB.
- Verify in your BPXPRMxx that Unix Domain
Sockets are configured, e.g.:
FILESYSTYPE TYPE(UDS) ENTRYPOINT(BPXTUINT) NETWORK TYPE(UDS) DOMAINNAME(AF_UNIX) DOMAINNUMBER(1)


File name: tins_prepzos.html