RE: QUser and jdbc access to os400

Hi Colin,

        Thanks for your response. I am concerned with the user id that my db
triggers show which is gotten from the program status data structure as in :
     D                SDS
     D PgmNam            *PROC
     D UserId                254    263

        Which works for all current native accesses.  How would I find the 
'Current
User' at the trigger level?

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 Colin Williams
Sent: Thursday, May 11, 2006 9:09 AM
To: Java Programming on and around the iSeries / AS400
Subject: Re: QUser and jdbc access to os400


Rick,

QUSER is the user shown on WRKACTJOB, but there is also the current user,
which will be the profile that initiated the connection.

I believe from V5R4 the current user will also be shown on WRKACTJOB, and
not just QUSER

For audit purposes you need to pick up the current user

cheers
Colin.W


On 11/05/06, Rick DuVall <R_C_DuVall@xxxxxxxxxx> wrote:
>
> Hi Everybody,
>
>        I am experimenting with interactive java clients for accessing
> os400 data.
> One thing that strikes me immediately is that even if I open up jdbc
> access
> to the box,  which I can do on a userid level, all updates/inserts to the
> DB
> are attributed to QUSER no matter what userid/password is used to initiate
> the connection. We carefully track DB modifications on the userid level
> and
> this invalidates all that.  Am I missing something?  This seems kinda
> lame.
> I suppose unless someone can show me my error, I will use a back end rpg
> server that spawns off jobs using sockets under the incoming Userid to
> manage the db updates.  So, am I missing something here?  What is the best
> practice?
>
> Thanks!
>
> Rick DuVall