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.
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.
If 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.
Locate the JDBC classes
in your USS environment, for example the file db2jcc.jar
can be in /usr/lpp/db2710/db2710/jcc/classes/ .
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
LP =$LP:$DB2/jcc/lib export LIBPATH=$LP
export PATH=$PATH:$DB2/jcc/bin
Save the file, submit the BIPGEN job, and check
the output to make sure the changes you just made are present.
mqsicreateconfigmgr - VCP2CMGR - -q VCP2 - -n //kbynl76.alpha.ibm.com:50000/WBIV5CFG - -u fred -p xxxxxxx
Note that the BIPCRCM job can take
several minutes to run, depending on the content of the remote
database.