Customizing the broker JCL

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 Customizing the broker component data set.

All JCL has a standard header, comprising:
  1. A brief description of its function.
  2. A description where further information can be found, relating to the function of the JCL.
  3. If appropriate, a topic number.
  4. The section listing the JCL variables themselves.
  5. Each JCL file defines its own STEPLIB
  6. Some JCL files, for example, BIPRELG might require DB2 defined in the STEPLIB for a broker component. This must be removed from the JCL if the component is either a Configuration Manager or User Name Server, as it is not required.

You can customize the files using an ISPF edit macro that you have to tailor, or you can make changes to each of the PDSE members manually.

BIPEDIT is a REXX program that can be used to assist you in customizing your JCL. Once you have customized BIPEDIT you can run this REXX program against the other JCL files to change their JCL variables.

First of all, customize the renamed BIPEDIT file using the information you collected in:
Next, you must activate the renamed BIPEDIT file before you customize any other JCL files. Do this by running the following TSO command:
    ALTLIB ACTIVATE APPLICATION(EXEC) DA('COMPONENTDATASET')
where 'COMPONENTDATASET' is identical to ++COMPONENTDATASET++.

This command is active for the local ISPF session for which it was issued. Note, that if you have split screen sessions, the other sessions are not able to use this. If you use ISPF option 6 to issue the command, use ISPF option 3.4 to edit the data set; this enables you to use the edit command.

You can then edit each JCL file and run the renamed BIPEDIT exec by typing its name on the command line (for example MQ01EDBK). You might want to use View instead of Edit on a member until any problems in your REXX program are resolved. Alternatively, you can Cancel the Edit session instead of using Save.

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.

Some JCL files include ++OPTIONS++ for a command, these must be replaced with additional optional parameters specific to the command on z/OS, or removed. It is likely that you will have to do this in addition to running BIPEDIT. If you do not require any additional options, remove ++OPTIONS++ using the following command:
     "c ++OPTIONS++ '' all" 
where ' ' represents two single quotation marks.

Save the edit macro and run this macro against all the members except the edit macro itself.

If the user ID submitting the BIPCBRK command has the appropriate DB2 and WebSphere MQ authorities, you can ignore the optional mqsicreatebroker parameters -1, -2, and -3.

If it is your intention to have different administrators create the DB2 and WebSphere MQ resources, you can consider using one of these optional parameters; see the mqsicreatebroker command for further information.

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. You must do this each time you update BIPBPROF for the changes to take effect.
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.
Related concepts
Brokers
Broker domains
Related tasks
Creating a broker on z/OS
Customizing the broker component data set
Related reference
mqsicreatebroker command