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.
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.
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.
"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.