IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Customizing the broker JCL

This subtask is part of the larger task of creating a broker on z/OS®.

Before you start

Before starting this task, you must have completed Customizing the broker component data set.

All JCL has a standard header, which includes the following items:

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.

Each JCL file defines its own STEPLIB.

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

BIPEDIT is a REXX program that you can use to help you customize your JCL. After you have customized BIPEDIT, you can run this REXX program against the other JCL files to change their JCL variables.

When you update BIPBPROF (the broker profile), the changes are not accessible until you run BIPGEN to copy the profile to the file system and create the ENVFILE. You must run BIPGEN each time you update BIPBPROF for the changes to take effect. If you have integration server specific profiles, and you change either BIPBPROF or BIPEPROF (renamed to the integration server label), you must also run BIPGEN.

Customize the renamed BIPEDIT file. Use the information you collected in:
- Installation information - broker
- Component information - broker
Activate the renamed BIPEDIT file before you customize other JCL files, 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. If you have split screen sessions, the other sessions are not able to use this command. If you use ISPF option 6 to issue the command, use ISPF option 3.4 to edit the data set, which enables you to use the edit command.
Edit each JCL file. Run the renamed BIPEDIT file by typing its name on the command line (for example MQ01EDBK). Instead of editing a member, you might want to View it until you have resolved all problems in your REXX program. Alternatively, you can Cancel the Edit session instead of saving it.
You must set a value for all the variables listed in the JCL; if you do not do so, the JCL does not work correctly.

Some JCL files include ++OPTIONS++ for a command; you must replace them with additional optional parameters specific to the command on z/OS, or remove them. Typically, you must replace or remove these options in addition to running BIPEDIT. If you do not require additional options, remove ++OPTIONS++ by 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 BIPCRBK command has the appropriate WebSphere® MQ authorities, you can ignore the optional mqsicreatebroker parameters -1 and -2.

If you expect different administrators to create the WebSphere MQ resources, you can consider using one of these optional parameters; see mqsicreatebroker command for further information.

You must be aware that another process might be using the current ENVFILE, therefore you must consider whether updating the current ENVFILE in the file system might have other effects.

ae22460_.htm |

Last updated Friday, 21 July 2017