Creating the Configuration Manager component

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

Before you start

Before starting this task, you must have completed Customizing the Configuration Manager JCL.

If the user ID submitting the BIPCRCM command has the appropriate WebSphere MQ authorities, you can ignore the optional mqsicreateconfigmgr parameters -1 and -2. If it is your intention to have a different administrator create the WebSphere MQ resources, you can consider using one of these optional parameters; see the mqsicreateconfigmgr command for further information.

  1. Submit job BIPCRCM with option -1. This job creates the Configuration Manager together with the files and directories that are placed in the registry. You must run this job first, and to do this you need authority to access the Configuration Manager.
  2. Edit BIPCRCM and submit the job with option -2. This job creates the WebSphere MQ queues. If you do not have the requisite authority, ask your WebSphere MQ system administrator to run the job.
  3. Start of changeEnsure that the jobs have run successfully by:
    • Checking the STDOUT stream in the JOBLOG.
    • Viewing STDOUT for any errors and checking forBIP8071I: Successful command completion.
    End of change
If you encounter any problems, delete the Configuration Manager and recreate it using the following procedure. Note that you need the appropriate authority to run the jobs.
  1. Edit and configure job BIPDLCM.
  2. Run job BIPDLCM with the same option, or options, that caused the problems when you ran the BIPCRCM job.
  3. Correct the problems and run the BIPCRCM job again.
If you want to migrate the Configuration Manager from another platform to z/OS, for example, migrating a Version 5 Configuration Manager from Windows XP, you need to do some additional customization to include JDBC into the BIPCRCM job.
  1. Locate the JDBC classes in your USS environment; for example the file db2jcc.jar can be in /usr/lpp/db2710/db2710/jcc/classes/.
  2. Edit the BIPCPROF file and add the following lines before the line containing export CLASSPATH=, so that the file looks like this:
    DB2=/usr/lpp/db2710/db2710
    CP=$CP:$DB2/jcc/classes/sqlj.zip                             
    CP=$CP:$DB2/jcc/classes/db2jcc.jar                           
    CP=$CP:$DB2/jcc/classes/db2jcc_javax.jar                     
    CP=$CP:$DB2/jcc/classes/db2jcc_license_cisuz.jar             
    export CLASSPATH=$CP 
  3. Before the line containing export LIBPATH=$LP insert the following lines to add the files to the LP, as follows:
    LP =$LP:$DB2/jcc/lib
    export LIBPATH=$LP      
  4. After the final export PATH statement add the following line:
    export PATH=$PATH:$DB2/jcc/bin 
  5. Save the file, submit the BIPGEN job, and check the output to make sure the changes you just made are present.
  6. Edit the BIPCRCM job to define the remote database, user ID, and password for the remote database you want to use; for example:
    mqsicreateconfigmgr -                                          
    VCP2CMGR   -                                                   
    -q VCP2 -                                                      
    -n //kbynl76.alpha.ibm.com:50000/WBIV5CFG -                  
    -u fred -p xxxxxxx
    In the preceding example:
    • VP2CMGR is the Configuration Manager name
    • -n is the location of the remote database
    • //kbynl76.alpha.ibm.com is the machine containing the DB2 instance
    • 50000 is the port number
    • WBIV5CFG is the database name on that DB2 instance; this information is passed to the JDBC connect call
    • -u is the Windows user ID, in this case fred
    • -p is the password value
You can determine the port number as follows:
  1. From the UDB control center, right-click on the DB2 instance.
  2. Select Setup Communications....
  3. Enter the user ID and password, if required.
The properties box contains the address and port number for this DB2 instance.

Note that the BIPCRCM job can take several minutes to run, depending on the content of the remote database.

Related concepts
Configuration Manager
Related tasks
Creating a Configuration Manager on z/OS
Customizing the Configuration Manager JCL