This is part of the larger task of creating a broker on z/OS.
Before
you start
Before starting this step, you must have completed Creating the component dataset.
All JCL has a standard
header, comprising:
- A brief description of its function.
- A description where further information can be found, relating to the
function of the JCL.
- If appropriate, a topic number.
- The section listing the JCL variables themselves.
Customize all the JCL you copied to the broker dataset (detailed
in
Creating the component dataset) using the information
you collected in:
For every JCL variable (for example
++HOME++) replace
each instance
with the information collected; for example:
"c ++home++ /u/mq01brk
all".
You must set a value for
all the variables listed in the JCL; if you do not do so, the JCL will not
work correctly.
Where JCL includes
++OPTIONS++ for
a command, this
must be replaced with additional optional parameters
specific to the command on
z/OS, or removed.
If you do not require any additional options, remove
++OPTIONS++ using
the following command:
"c ++OPTIONS++ '' all"
where
' ' represents two single quotation marks.
Do not
set any of the optional pass parameters (-1, -2, or -3) in BIPCRBK at
this time because you want to create the registry, the WebSphere MQ queues,
and the DB2 tables and indexes.
When you update
BIPBPROF (the broker
profile), the changes are not accessible until you run
BIPGEN to
copy the profile to the HFS and create the
ENVFILE.
Note: You
need to be aware that another process might be using the current ENVFILE,
so you need to consider whether updating the current ENVFILE in
the HFS will have any impact.