Creating the Configuration Manager component

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

Before you start

Complete 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 you expect that a different administrator will create the WebSphere MQ resources, 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. To run this job, you must have 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. Ensure that the jobs have run successfully:
    • Check the STDOUT stream in the JOBLOG.
    • View STDOUT for any errors and checking forBIP8071I: Successful command completion.
If you encounter any problems, delete the Configuration Manager and recreate it using the following procedure. You must have 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.

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
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009. All Rights Reserved.
Last updated : 2009-01-07 15:40:16

ae24250_