Re: Job User Identity -- MIDRANGE-L

Ok, so JDOE somehow started the PJ. Is it just one job? Or all of the
QZDASOINIT ones?

Did you look at the subsystem description?

There is a command, Start Pre-start Job STRPJ.

But it's not like a SBMJOB. You have to point it to a SBSD that has a
pre-start job entry for the job you want to start. Also, if the jobs are
already running, STRPJ can't be used to start more.

Charles

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

No I guess I said that wrong. There was a QZDAOSINIT job with User Quser
in subsystem QUSRWORK, it was a PJ prestart job. The current user was
JSMITH the job user identity was JDOE Set by *SYSTEM. JDOE said she didn't
have any queries running and wondered why her name was on that job. When I
looked later both current user and job user identity was JDOE on that job.
Didn't know exactly how to explain it to her.
________________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxx> on behalf of Charles
Wilt <charles.wilt@xxxxxxxxx>
Sent: Monday, April 11, 2016 5:20 PM
To: Midrange Systems Technical Discussion
Subject: Re: Job User Identity

So what that's saying is that JSMITH actually started a QZDASOINIT job
somehow...that was later reused by JDOE.

Off the top of my head, I don't know how JSMITH would have done that...

What is the job type? Pre-start jobs should have Type=PJ

What subsystem? If you do a DSPSBSD for that subsystem and select option
10-Prestart job entries, what is shown as the user profile for the
QZDASOINIT job?
Program Library User Profile
QNPSERVS QSYS QUSER
QRWTSRVR QSYS QUSER
QSCWCHPS QSYS QUSER
QZDASOINIT QSYS QUSER
QZDASSINIT QSYS QUSER

Charles

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

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>
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>
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.

--
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.
--
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.

--
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.
--
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.