WebSphere Message Brokers
File: ae22290_
Writer: Bill Oppenheimer

Task topic

This build: July 31, 2007 21:28:14

Creating the User Name Server component

This is part of the larger task of creating a User Name Server on z/OS.

Before you start

Before starting this task, you must have completed Customizing the User Name Server JCL.

If the user ID submitting the BIPCRUN command has the appropriate WebSphere MQ authorities, you can ignore the optional mqsicreateusernameserver 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 mqsicreateusernameserver command for further information.

  1. Submit job BIPCRUN with option -1. This job creates the User Name Server 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 User Name Server.
  2. Edit BIPCRUN 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 by:
    • Checking the STDOUT stream in the JOBLOG.
    • Viewing STDOUT for any errors and checking forBIP8071I: Successful command completion.
If you encounter any problems, delete the User Name Server and recreate it using the following procedure. Note that you need the appropriate authority to run the jobs.
  1. Edit and configure job BIPDLUN.
  2. Run job BIPDLUN with the same option, or options, that caused the problems when you ran the BIPCRUN job.
  3. Correct the problems and run the BIPCRUN job again.
Related concepts
User Name Server
Related tasks
Creating a User Name Server on z/OS
Customizing the User Name Server JCL
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2007Copyright IBM Corporation 1999, 2007. All Rights Reserved.
This build: July 31, 2007 21:28:14

ae22290_ This topic's URL is: