Testing for queue sharing groups

The basic installation verification program CSQ4IVP1 tests non-shared queues.

CSQ4IVP1 can be used whether the queue manager is a member of a queue sharing group or not. After running the basic IVP, we can test for shared queues by using the CSQ4IVP1 installation verification program with different queues. Also this tests that Db2 and the coupling facility are set up correctly.

Preparing to run CSQ4IVP1 for a queue sharing group

Before you run CSQ4IVP1:

1. Add the coupling facility structure that the IVP uses to your CFRM policy data set, as described in Set up the coupling facility. The supplied samples use a structure called APPLICATION1, but you can change this if we want.
2. Check that the IVP entries are in the CSQINP2 data set concatenation in the queue manager startup program. The IVP entries are supplied in member thlqual.SCSQPROC(CSQ4IVPG). If they are not, add the definitions supplied in thlqual.SCSQPROC(CSQ4IVPG) to your CSQINP2 concatenation. If the queue manager is currently running, we need to restart it so that these definitions can take effect.
3. Change the name of the coupling facility structure used in thlqual.SCSQPROC(CSQ4IVPG) if necessary.
4. The sample JCL, CSQ4IVPS, required to run the installation verification program for a queue sharing group is in library thlqual.SCSQPROC.

   Customize the CSQ4IVPS JCL with the high-level qualifier for the IBM MQ libraries, the national language we want to use, the four-character IBM MQ queue manager name, and the destination for the job output.

5. Update RACF to allow CSQ4IVP1 to access its resources if IBM MQ security is active.

   To run CSQ4IVP1 when IBM MQ security is enabled, we need a RACF user ID with authority to access the objects. For details of defining resources to RACF, see Set up security on z/OS . The user ID that runs the IVP must have the following access authority in addition to that required to run the basic IVP:

   Authority	Profile	Class
   UPDATE	ssid.CSQ4IVPG.**	MQQUEUE

   These requirements assume that all IBM MQ security is active. The RACF commands to activate IBM MQ security are shown in Figure 1. This example assumes that the queue manager name is CSQ1 and that the user ID of the person running sample CSQ4IVP1 is TS101.

   RDEFINE MQQUEUE CSQ1.CSQ4IVPG.**
   PERMIT CSQ1.CSQ4IVPG.** CLASS(MQQUEUE) ID(TS101) ACCESS(UPDATE)
   

Running CSQ4IVP1 for a queue sharing group

When you have completed these steps, start your queue manager. If the queue manager is already running and you have changed CSQINP2, we must stop the queue manager and restart it.

The IVP runs as a batch job. Customize the job card to meet the submission requirements of our installation.

Check the results of CSQ4IVP1 for a queue sharing group

The IVP for queue sharing groups works in the same way as the basic IVP, except that the queues that are created are called CSQIVPG. xx. Follow the instructions given in Check the results of CSQ4IVP1 to check the results of the IVP for queue sharing groups.

Parent topic: Testing a queue manager on z/OS