Task 6: Create procedures for the WebSphere MQ queue manager
Repeat this task for each WebSphere MQ queue manager.
You might need to perform this task when migrating from a previous version.
For each WebSphere MQ subsystem defined in the subsystem name table, create a cataloged procedure in a procedure library for starting the queue manager.
The IBM-supplied procedure library is called SYS1.PROCLIB, but your installation might use its own naming convention.
The name of the queue manager started task procedure is formed by concatenating the subsystem name with the characters MSTR. For example, subsystem CSQ1 has the procedure name...
CSQ1MSTRYou need one procedure for each subsystem you define.
IBM recommends that a subsystem called CSQ1MSTR is created initially for installation verification and testing purposes.
Two sample started task procedures are provided in...
thlqual.SCSQPROCMember CSQ4MSTR uses one page set for each class of message, member CSQ4MSRR uses multiple page sets for the major classes of message. Copy one of these procedures to member xxxxMSTR (where xxxx is the name of your WebSphere MQ subsystem) of your SYS1.PROCLIB or, if you are not using SYS1.PROCLIB, your procedure library. Copy the sample procedure to a member in your procedure library for each WebSphere MQ subsystem that you define.
When you have copied the members, we can tailor them to the requirements of each subsystem, using the instructions in the member. We can also use symbolic parameters in the JCL to allow the procedure to be modified when it is started.
If you have several WebSphere MQ subsystems, you might find it advantageous to use JCL include groups for the common parts of the procedure, to simplify future maintenance.
You must concatenate thlqual.SCSQANLx, where x is the language letter for your national language, before thlqual.SCSQAUTH in the STEPLIB DD statement.
If you are using queue-sharing groups, the STEPLIB concatenation must include the DB2 runtime target library SDSNLOAD, and it must be APF-authorized. This library is only required in the STEPLIB concatenation if it is not accessible through the linklist or LPA.
Before you start the queue manager, set up WebSphere MQ data set and system security by:
- Authorizing the queue manager started task procedure to run under your external security manager.
- Authorizing access to the queue manager data sets.
We can add the exit library (CSQXLIB) to this procedure later if you want to use queue manager exits. You will need access to the Language Environment (LE) runtime library SCEERUN to do this; if it is not in your link list (SYS1.PARMLIB(LNKLSTkk)), concatenate it in the STEPLIB DD statement. You also need to stop and restart your queue manager.