Preparing to run CSQ4IVP1 for a queue-sharing group
Before you run CSQ4IVP1:
- Add the Coupling Facility structure that the IVP uses to your CFRM policy data set, as described in Task 10: Set up the Coupling Facility. The supplied samples use a structure called APPLICATION1, but we can change this if you want.
- 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.
- Change the name of the Coupling Facility structure used in thlqual.SCSQPROC(CSQ4IVPG) if necessary.
- 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 WebSphere MQ libraries, the national language you want to use, the four-character WebSphere MQ queue manager name, and the destination for the job output.
- Update RACF to allow CSQ4IVP1 to access its resources if WebSphere MQ security is active.
To run CSQ4IVP1 when WebSphere 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. 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 WebSphere MQ security is active. The RACF commands to activate WebSphere MQ security are shown in Figure 6. This example assumes that the queue manager name is CSQ1 and that the user ID of the person running sample CSQ4IVP1 is TS101.
Figure 6. RACF commands for CSQ4IVP1 for a queue-sharing groupRDEFINE MQQUEUE CSQ1.CSQ4IVPG.** PERMIT CSQ1.CSQ4IVPG.** CLASS(MQQUEUE) ID(TS101) ACCESS(UPDATE)