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 step, 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 which 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.

If you encounter any problems, edit and configure job BIPDLCM. Run job BIPDLCM with the same option, or options, that caused the problems when you ran the BIPCRCM job. Note that you need the appropriate authority to run the jobs.

Correct the problems and run the BIPCRCM job again.

Start of changeIf you want to migrate the Configuration Manager from other platforms to z/OS, for example, migrating a Version 5 Configuration Manager from Windows XP, you need to do some additional customizing to include JDBC into the BIPCRCM job.End of change

Start of changeLocate the JDBC classes in your USS environment, for example the file db2jcc.jar can be in /usr/lpp/db2710/db2710/jcc/classes/ .End of change

Start of change Edit the BIPCPROF file and add the following before the line containing export CLASSPATH=, so it looks like:
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 
End of change
Start of changeBefore the line containing export LIBPATH=$LP insert the following lines to add the files to the LP, so it looks like:
LP =$LP:$DB2/jcc/lib
export LIBPATH=$LP      
End of change
Start of changeAfter the final export PATH statement add the following:
export PATH=$PATH:$DB2/jcc/bin 
End of change

Start of changeSave the file, submit the BIPGEN job, and check the output to make sure the changes you just made are present.End of change

Start of changeEdit theBIPCRCM job to define the remote database, user Id, and password for the remote database you want to use. In the following command:
mqsicreateconfigmgr -                                          
VCP2CMGR   -                                                   
-q VCP2 -                                                      
-n //kbynl76.alpha.ibm.com:50000/WBIV5CFG -                  
-u fred -p xxxxxxx
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.
-p
Is the password value.
End of change
Start of changeYou 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.End of change

Start of changeNote that the BIPCRCM job can take several minutes to run, depending on the content of the remote database.End of change

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