User IDs for resource security (MQOPEN, MQSUB, and MQPUT1)
This information shows the contents of the user IDs for normal and alternate user IDs for each type of connection. The number of checks is defined by the RESLEVEL profile. The user ID checked is that used for MQOPEN, MQSUB, or MQPUT1 calls.
Note: All user ID fields are checked exactly as they are received. No conversions take place, and, for example, three user ID fields containingBob,
BOB, and
bobare not equivalent.
- User IDs checked for batch connections
The user ID checked for a batch connection depends on how the task is run and whether an alternate user ID has been specified. - User IDs checked for CICS connections
The user IDs checked for CICS connections depend on whether one or two checks are to be carried out, and whether an alternate user ID is specified. - User IDs checked for IMS connections
The user IDs checked for IMS connections depend on whether one or two checks are to be performed, and whether an alternate user ID is specified. If a second user ID is checked, it depends on the type of dependent region and on which user IDs are available. - User IDs used by the channel initiator
This collection of topics describes the user IDs used and checked for receiving channels and for client MQI requests issued over server-connection channels. Information is provided for TCP/IP and for LU6.2 - User IDs used by the intra-group queuing agent
The user IDs that are checked when the intra-group queuing agent opens destination queues are determined by the values of the IGQAUT and IGQUSER queue manager attributes.
Parent topic: User IDs for security checking on z/OS