For information about installing WebSphere Business Integration Event Broker on z/OS using SMP/E, refer to the WebSphere Business Integration Event Broker for z/OS Program Directory.
On WebSphere Business Integration Event Broker V5 for z/OS, the main JCL used to start a broker has changed. You need to recustomize to get the new JCL into the PDS.
Deploying a message flow, which 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 is held on to for the life of the new address space.
Certain USS system parameters might affect the start of a new execution group address space, if set incorrectly. These include IPCSEMNIDS, IPCSHMNIDS, IPCSHMNSEGS. You need a minimum of three semaphores for each execution group address space started. You should set IPCSEMNIDS set at 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 should set IPCSEMNIDS at 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 need to set IPCSHMNSEGS at a value that exceeds the potential number of execution groups for each broker.
Bipservice and bipbroker now in the same address space (control address space). After a DataFlowEngine address space has been started on z/OS, the stepname of the address space has the following value:
The stepname is not guaranteed to be a unique value. But you are recommended to ensure that the last eight characters of any execution group labels that are deployed to a z/OS broker are unique and only alphanumeric. An execution group label has a maximum size of 3000 bytes.
On z/OS, all address spaces have a joblog where BIP messages issued by WebSphere Business Integration Event Broker appear. Additionally, all messages appear on the syslog and important operator messages are filtered to the console using MPF (Message Processing Facility). To prevent the operators console receiving unnecessary BIP messages, you should configure MPF to suppress all BIP messages, with exception of important messages that you want to see. You do not need to have the USS SYSLOG configured.
Related tasks
Installing service on z/OS
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ah01790_ |