Receiving channels using LU 6.2

The user IDs checked depend on the PUTAUT option of the channel and on whether one or two checks are to be performed.

Table 1. User IDs checked against profile name for LU 6.2 channels
PUTAUT option specified on receiver or requester channel hlq.ALTERNATE.USER.userid profile hlq.CONTEXT.queuename profile hlq.resourcename profile
DEF, 1 check - CHL CHL
DEF, 2 checks - CHL + MCA CHL + MCA
CTX, 1 check CHL CHL CHL
CTX, 2 checks CHL + MCA CHL + MCA CHL + ALT
ONLYMCA, 1 check - MCA MCA
ONLYMCA, 2 checks - MCA MCA
ALTMCA, 1 check MCA MCA MCA
ALTMCA, 2 checks MCA MCA MCA + ALT
Key:

    MCA (MCA user ID)
    The user ID specified for the MCAUSER channel attribute at the receiver; if blank, the channel initiator address space user ID of the receiver or requester side is used.

    CHL (Channel user ID)

      Requester-server channels
      If the channel is started from the requester, there is no opportunity to receive a network user ID (the channel user ID).

      If the PUTAUT parameter is set to DEF or CTX on the requester channel, the channel user ID is that of the channel initiator address space of the requester because no user ID is received from the network.

      If the PUTAUT parameter is set to ONLYMCA or ALTMCA, the channel user ID is ignored and the MCA user ID of the requester is used.

      Other channel types
      If the PUTAUT parameter is set to DEF or CTX on the receiver or requester channel, the channel user ID is the user ID received from the communications system when the channel is initiated.

      • If the sending channel is on z/OS®, the channel user ID received is the channel initiator address space user ID of the sender.
      • If the sending channel is on a different platform (for example, AIX or HP-UX), the channel user ID received is typically provided by the USERID parameter of the channel definition.

      If the user ID received is blank, or no user ID is received, a channel user ID of blanks is used.

    ALT (Alternate user ID)
    The user ID from the context information (that is, the UserIdentifier field) within the message descriptor of the message. This user ID is moved into the AlternateUserID field in the object descriptor before an MQOPEN or MQPUT1 call is issued for the target destination queue.