Security scenario: queue sharing group on z/OS
In this scenario, an application uses the MQPUT1 call to put messages to queues on queue manager QM1. Some of the messages are then forwarded to queues on QM2, using TCP and LU 6.2 channels. The application is a batch application, and the messages are put using the MQPMO_SET_ALL_CONTEXT option.
This is illustrated in Figure 1.
The following assumptions are made about the queue managers:- All the required IBM MQ definitions have been predefined or have been made through the CSQINP2 data set processed at queue manager startup.
If they have not, we need the appropriate access authority to the commands needed to define these objects.
- All the RACF profiles required have been defined and appropriate access authorities have been granted, before the queue manager and channel initiators started.
If they have not, we need the appropriate authority to issue the RACF commands required to define all the profiles needed and grant the appropriate access authorities to those profiles. You also need the appropriate authority to issue the MQSC security commands to start using the new security profiles.
- Security switch settings for queue sharing group scenario
Switch settings and RACF profiles. - Queue manager QM1 in queue sharing group scenario
Queues and channels for QM1. - Queue manager QM2 in queue sharing group scenario
Queues and channels for QM2. - User IDs used in queue sharing group scenario
Explanation of the user IDs in the scenario. - Security profiles and accesses required for queue sharing group scenario
Security profiles and accesses for either a batch or CICS implementation of the queue sharing group scenario.
Parent topic: Security scenarios
Related information