Creating the broker component

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

Before you start

Before starting this task, you must have completed Priming DB2.

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

  1. Submit job BIPCRBK with option -1. This job creates the files and directories that are placed in the default storage group. You must run this job first, and to do this you need authority to access the broker root directory.
  2. Edit BIPCRBK 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. Edit BIPCRBK and submit the job with option -3. This job creates the DB2 queues. If you do not have the requisite authority, ask your DB2 system administrator to run the job.
  4. 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 broker and recreate it using the following procedure. Note that you need the appropriate authority to run the jobs.
  1. Edit and configure job BIPDLBK.
  2. Run job BIPDLBK with the same option, or options, that caused the problems when you ran the BIPCRBK job.
  3. Correct the problems and run the BIPCRBK job again.
Related concepts
Brokers
Broker domains
Related tasks
Creating a broker on z/OS
Priming DB2
Related reference
mqsicreatebroker command