WebSphere Message Brokers
File: ae24240_
Writer: Bill Oppenheimer

Task topic

This build: July 31, 2007 21:28:37

Customizing the Configuration Manager JCL

This is part of the larger task of creating a Configuration Manager on z/OS.

Before you start

Before starting this step, you must have completed Customizing the Configuration Manager component data set.

Each JCL file defines its own STEPLIB. 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, because 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 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 BIPCPROF (the Configuration Manager profile), the changes are not accessible until you run BIPGEN to copy the profile to the file system and create the ENVFILE. You must do this each time you update BIPCPROF for the changes to take effect, which happens when you restart the Configuration Manager.

Do not set either of the optional pass parameters (-1 or -2) in BIPCRCM at this time because you want to create the registry and the WebSphere MQ queues.

  1. Customize the renamed BIPEDIT file. Use the information you collected in:
  2. 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.

  3. Edit each JCL file. Run the renamed BIPEDIT exec by typing its name on the command line (for example MQ01EDCM). Instead of editing a member, you might want to View it until you have resolved any 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 will 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. 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 of the members except the edit macro itself.

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 file system will have any impact.

Related concepts
Configuration Manager
Related tasks
Creating a Configuration Manager on z/OS
Customizing the Configuration Manager component data set
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:28:37

ae24240_ This topic's URL is: