Re: Job User Identity

[Charles Wilt <charles.wilt@xxxxxxxxx>]

Authority comes from the CURRENT USER only.

Every job in the system starts under a user ID.  When the job starts, the
job user and the current user are the same.   In the case of pre-start jobs
like QZDASOINIT, the job user is a system profile, QUSER.

JOB USER never changes, CURRENT USER changes when the job uses API to swap
to another profile.

For the QZDASOINIT jobs, the profile swap happen when someone connects to
the system using ODBC/JDBC/OLEDB.  The credentials they use to connect are
used to swap CURRENT USER of the servicing QZDASOINIT job so that the
connected user is working within his/her own authority.

Charles

On Mon, Apr 11, 2016 at 1:10 PM, Boyle, Doreen <doreen.boyle@xxxxxxx> wrote:

> Can someone please explain Job User Identity to me, and exactly what
> controls it.
>
> I noticed a QZDASOINIT job with different names for current user and Job
> User Identity.  I googled and read some blurbs, but was getting a little
> confused about threads, *SYSTEM and *DEFAULT values etc.  Is it that the
> current user JSMITH submitted a query job that runs a batch job that has
> multi threads in it and needs to use the profile JDOE listed as the Job
> User Identity to perform more functions???
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxx for any subscription related
> questions.