This topic describes in detail the contents of the Customization Input File (mqsicompcif), which holds configuration data needed for component customization. See Example Customization Input File (mqsicompcif) and use it to collect your configuration information.
All environment variables need to be made explicit in mqscompcif. For example do not use $JAVAHOME; write the full path of the Java home directory. This is because ENVFILE is parsed by BPXBATCH before the shell environment for the started task has been created, and BPXBATCH does not recognize the use of $ to indicate environment variables.
Each component must have a component name and a component key.
Component name | Broker | User Name Server |
Component key | MQP1BRK | MQP1UNS |
Create the started task procedure with the same name as your broker to avoid confusion. Although your started task and broker can have different names, it is easier to manage if you make the broker component name and component key the name of the started task procedure. However, you are free to choose your own values as long as they comply with the requirements below. Additionally, you are recommended to choose uppercase-only names.
= (equals)
- (dash)
_ (underscore)
. (dot)
If you expect to trace the operation of an execution group, restrict the name of the execution group to include only the valid alphabetic and numeric characters listed above (US English alphabet only). The trace commands do not support the use of special characters for an execution group name.
The acceptable characters are representations in code page 1047. Because component names are part of the messages displayed on the system log, ensure that your broker names contain only characters that your system log can display. You are recommend to use digits and uppercase letters.
Select a name that fits your installation naming convention and have the broker name as part of the data set name. For example, use WMQI.MQP1BRK.CNTL or MQ.MQP1BRK.BIPCNTL, where MQP1 is the queue manager being used. WebSphere Business Integration Event Broker, DB2, WebSphere MQ and z/OS administrators need UPDATE access to this PDSE.
Add the name of the PDSE to your copy of the Customization planning checklist for z/OS.
Add the name of the started task procedure to your copy of the Customization planning checklist for z/OS.
/usr/lpp/java/IBM/J1.4/bin/java
Take
the path up to, but not including, the bin directory, as
your JAVAHOME. Add this path to your copy of the Customization planning checklist for z/OS.WebSphere Business Integration Event Broker for z/OS allows you to register a component to the Automatic Restart Manager (ARM).
When customizing a broker for the first time, you can allow USE_ARM to default to NO. Revisit it when you prepare your production system. To enable ARM, you can change this value and recustomize
To register a component to ARM at startup, set USE_ARM to YES. You then have to supply values for the variables ARM_ELEMENTNAME and ARM_ELEMENTTYPE.
ARM_ELEMENTNAME can be a maximum of 8 characters in length, because WebSphere Business Integration Event Broker adds a prefix of SYSWMQI. For example, if you supply the value MQP1BRK to ARM_ELEMENTNAME, the element you define in your ARM policy is SYSWMQI_MQP1BRK.
Description | Name |
Switch that determines whether ARM will be used (YES or NO). | USE_ARM |
ARM element name | ARM_ELEMENTNAME |
ARM element type | ARM_ELEMENTTYPE |
Add these values to the Customization planning checklist for z/OS.
Related concepts
Broker
Broker domain
User Name Server
Related tasks
Editing the Customization Input File (mqsicompcif) for a broker
Editing the Customization Input File (mqsicompcif) for a User Name Server
Checking the level of Java
Related reference
Customization planning checklist for z/OS
Example Customization Input File (mqsicompcif)
Notices |
Trademarks |
Downloads |
Library |
Support |
Feedback
![]() ![]() |
ae13910_ |