This is part of the larger task of customizing your z/OS environment.
WebSphere Message Broker requires the setup of some UNIX System Services system parameters. You can use the SETOMVS operator command for dynamic changes or the BPXPRMxx PARMLIB member for permanent changes. See the z/OS UNIX System Services Planning manual for more information.
You can use the D OMVS,O command to display your current OMVS options (view the syntax for this command).
Do not include the broker addresses if you use the IEFUSI exit to limit the region size of OMVS address spaces.
Set the UNIX System Services parameters as follows:
Description | Parameter | Value |
The maximum core dump file size (in bytes) that a process can create. Allow an unlimited size. | MAXCORESIZE | 2 147 483 647 |
The CPU time (in seconds) that a process is allowed to use. Allow an unlimited CPU time. | MAXCPUTIME | 2 147 483 647 |
The address space region size. Set to the size of the biggest address space. | MAXASSIZE | > 1 073 741 824 A minimum of 393 216 000 bytes is required. |
Specifies the maximum number of threads that a single process can have active. Depends on the definitions of message flows. | MAXTHREADS MAXTHREADTASKS | The value of MAXTHREADS and MAXTHREADTASKS depends
on your application. To calculate the value needed for each message flow:
|
Deploying a message flow, that starts an execution group in a new address space, uses USS Semaphore and SharedMemorySegment resources. In particular, each new address space uses a semaphore and SharedMemorySegment. The SharedMemorySegment is deleted immediately after the new address space has started, but the semaphore remains for the life of the new address space.
You must set IPCSEMNIDS to a value four times the number of potential execution group address spaces on a system.
You need one SharedMemorySegment for each execution group address space started. You must set IPCSEMNIDS to a value that exceeds the number of potential execution group address spaces on a system.
A control address space (BIPSERVICE and BIPBROKER processes) can be attached to many SharedMemorySegments - potentially, one for each execution group address space started for that broker. You must set IPCSHMNSEGS to a value that exceeds the potential number of execution groups for each broker.
Ensuring sufficient space for temporary files
The environment variable TMPDIR is the path name of the directory being used for temporary files. If it is not set, the z/OS shell uses /tmp.
When starting WebSphere Message Broker components, sufficient space is required in the directory referenced by TMPDIR. In particular, Java needs sufficient space to hold all JAR files required by WebSphere Message Broker.
If you do not allocate sufficient space, the execution group address spaces will abend with a 2C1 code.
Allow at least 50 MB of space in this directory for broker components and 10 MB of space for Configuration Manager components. More space might be needed if you deploy large user-defined nodes or other JAR files to the broker component.
Defining WebSphere Message Broker files as shared-library programs
/usr/lpp/mqsi/bin/* /usr/lpp/mqsi/lil/* /usr/lpp/mqsi/lib/* /usr/lpp/mqsi/lib/wbirf/* /usr/lpp/mqsi/lib/wbimb/* /usr/lpp/mqsi/lib/wbieb/*
extattr +l /usr/lpp/mqsi/bin/*
-rwxr-x--- a-s- 1 USER GROUP 139264 Mar 15 10:05 bipimainwhere s shows that the program is enabled to run in a shared address space.
/D OMVS,LIMITS