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.

Table 1. User ID checking against profile name for batch connections
Alternate user ID specified on open? hlq.ALTERNATE.USER.userid profile hlq.CONTEXT.queuename profile hlq.resourcename profile
No - JOB JOB
Yes JOB JOB ALT
Key:

    ALT
    Alternate user ID.

    JOB

    • The user ID of a TSO or USS sign-on.
    • The user ID assigned to a batch job.
    • The user ID assigned to a started task by the STARTED class or the started procedures table.
    • The user ID associated with the executing Db2® stored procedure

A Batch job is performing an MQPUT1 to a queue called Q1 with RESLEVEL set to READ and alternate user ID checking turned off.

Checks made at different RACF®(r) access levels for batch connections and User ID checking against profile name for batch connections show that the job user ID is checked against profile hlq.Q1.