RE: Job User Identity

Charles,

Here is the help text for current user

Current User Profile - Help

Specifies the profile under which the initial thread is running at this time.

For jobs that swap user profiles, this user profile name and the user portion of the job name can be different.

And here is the help text for job user identity

Job User Identity - Help

Specifies the job user identity for the job at this time. This value is the name of the user profile by which this job is known to other jobs. It is used for authorization
checks when other jobs attempt to operate against this job. This value is not used for authorization checks within this job. Also, the job does not inherit any of the
other attributes associated with the user profile.

You see them changing in server jobs as a way to minimize the number of jobs (in your case QZDASOINIT jobs) that have to be running. Without such a mechanism you would have each ODBC/JDBC connection having to start a new job every time a SQL statement was issued by the client. By swapping user profiles all the overhead associated with starting and stopping QZDASOINIT is minimized.

Thanks,

Gary Monnier
IT Software Engineer CSM, CSPO


-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Boyle, Doreen
Sent: Monday, April 11, 2016 1:34 PM
To: Midrange Systems Technical Discussion
Subject: RE: Job User Identity

Thank you Charles

The user couldn't figure out why his name was on the job, he didn't have any queries running. So if I understand correctly JSMITH had a QZDASOINIT job running, with him showing both current and job user, then JDOE made an ODBC connection and an API did a profile swap and changed the current user to JDOE? Sorry this is kind of confusing.

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Charles Wilt
Sent: Monday, April 11, 2016 2:06 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxx>>
Subject: Re: Job User Identity

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<mailto: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<mailto: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<mailto: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<mailto:support@xxxxxxxxxxxx> for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto: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<mailto: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<mailto:support@xxxxxxxxxxxx> for any subscription related questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxx<mailto: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<mailto: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<mailto:support@xxxxxxxxxxxx> for any subscription related questions.