RE: QUser and jdbc access to os400

Thanks Everybody!

        I figured out what was happening.  My triggers are called dynamically 
and
are compiled to run in the *caller ag.  The QZDASOINIT jobs did not have my
test lib in their liblist so when the main trigger fired it 'found' the
production version of the trigger, not the one I had so painstakingly
altered to use the 'Current' user id. <self deprecating chuckle/> Tripped up
by the LibList...

        The 'D UserId                358    367' is indeed the actual user that 
I
needed and I am sure that any of the other suggestions would do as well.  Oh
well - Thanks Again for all the help!

Regards,

Rick DuVall
Systems Manager
Dealer's Auto Auction of Okc
1028 S. Portland
Oklahoma City, OK 73108
(405) 947-2886
rick@xxxxxxxxxx

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx]On Behalf Of Gary L Peskin
Sent: Thursday, May 11, 2006 1:45 PM
To: 'Java Programming on and around the iSeries / AS400'
Subject: RE: QUser and jdbc access to os400


Try calling QUSRJOBI and, in format JOBI0600, use:

296     128     CHAR(10)        Job user identity

Gary

> -----Original Message-----
> From: java400-l-bounces+garyp=firstech.com@xxxxxxxxxxxx
> [mailto:java400-l-bounces+garyp=firstech.com@xxxxxxxxxxxx] On
> Behalf Of Rick DuVall
> Sent: Thursday, May 11, 2006 1:35 PM
> To: Java Programming on and around the iSeries / AS400
> Subject: RE: QUser and jdbc access to os400
>
> in my trigger :
>       * ------------------------------------
>       *        Program Status Data Structure
>       * ------------------------------------
>      D                SDS
>      D ThisPgm           *PROC
>      D UserId                358    367
>
>       and the value that I get is "QUSER".
>
> I have removed the trigger (this is in a test library that I
> can lock), recompiled it and re-added it.  Ran my java test
> and updated some records
> and the User the trigger got is "QUSER"... (QSQRUN3   QUSER
> )  I can't
> seem to find the proper QZDASOINIT   QUSER  or
> QZRCSRVS     QUSER
>
>       it seems to change in mid stream? or something.  I'm confused.
>
> Regards,
>
> Rick DuVall
> Systems Manager
> Dealer's Auto Auction of Okc
> 1028 S. Portland
> Oklahoma City, OK 73108
> (405) 947-2886
> rick@xxxxxxxxxx
>
> -----Original Message-----
> From: java400-l-bounces@xxxxxxxxxxxx
> [mailto:java400-l-bounces@xxxxxxxxxxxx]On Behalf Of David Gibbs
> Sent: Thursday, May 11, 2006 12:58 PM
> To: Java Programming on and around the iSeries / AS400
> Subject: Re: QUser and jdbc access to os400
>
>
> Rick DuVall wrote:
> >     so do you use the
> > 91 5B CHAR(10) Current user profile
> >     in the JOBI0600 Format?
>
> That's what I would use, yes.  I haven't actually used it, so
> I can't say 100% for sure.
>
> >     And will that return the User that initiated the jdbc
> connection?  It
> does
> > not appear that the 'Current User' that Colin mentioned returns the
> *actual*
> > current user - it still returns QUSER in my tests.
>
> How are you invoking the program again?  A trigger?
>
> To be honest, I would be very shocked if OS400 security
> wasn't enforced by switching user handles in the JDBC server job.
>
> david
>