Security profiles and accesses required for the two queue manager scenario
Information about the security profiles and accesses required for either a batch or CICS® implementation of the two queue manager scenario.
The following table shows the security profiles that are required to enable the two queue manager scenario to work. Additional security profiles are also needed, depending on whether you are doing a batch or a CICS implementation of the scenario. For further information see Security profiles required for a batch application and Security profiles required for a CICS application.
| Class | Profile | User ID | Access |
|---|---|---|---|
| MQCONN | QM1.CHIN | MOVER1 | READ |
| MQADMIN | QM1.RESLEVEL | BATCHID CICSAD1 MOVER1 | NONE |
| MQADMIN | QM1.CONTEXT.** | MOVER1 | CONTROL |
| MQQUEUE | QM1.SYSTEM.COMMAND.INPUT | MOVER1 | UPDATE |
| MQQUEUE | QM1.SYSTEM.CHANNEL.SYNCQ | MOVER1 | UPDATE |
| MQQUEUE | QM1.SYSTEM.CHANNEL.INITQ | MOVER1 | UPDATE |
| MQQUEUE | QM1.SYSTEM.COMMAND.REPLY.MODEL | MOVER1 | UPDATE |
| MQQUEUE | QM1.SYSTEM.ADMIN.CHANNEL.EVENT | MOVER1 | UPDATE |
| MQQUEUE | QM1.QM1.TO.QM2.TCP | MOVER1 | ALTER |
| MQQUEUE | QM1.QM1.TO.QM2.LU62 | MOVER1 | ALTER |
| MQQUEUE | QM1.QM1.TO.QM2.TLS | MOVER1 | ALTER |
| MQCONN | QM2.CHIN | MOVER2 | READ |
| MQADMIN | QM2.RESLEVEL | MOVER2 | NONE |
| MQADMIN | QM2.CONTEXT.** | MOVER2 | CONTROL |
| MQQUEUE | QM2.SYSTEM.COMMAND.INPUT | MOVER2 | UPDATE |
| MQQUEUE | QM2.SYSTEM.CHANNEL.SYNCQ | MOVER2 | UPDATE |
| MQQUEUE | QM2.SYSTEM.CHANNEL.INITQ | MOVER2 | UPDATE |
| MQQUEUE | QM2.SYSTEM.COMMAND.REPLY.MODEL | MOVER2 | UPDATE |
| MQQUEUE | QM2.SYSTEM.ADMIN.CHANNEL.EVENT | MOVER2 | UPDATE |
| MQQUEUE | QM2.DLQ | MOVER2 | UPDATE |