MIDRANGE dot COM Mailing List Archive



Home » JAVA400-L » May 2006

Fw: QUser and jdbc access to os400



fixed

Have a look at my WRKODBCJOB command.

http://home.columbus.rr.com/jbmmdietz/iseries.html

It  will help you identify the current user attached to the JDBC/ODBC 
requests.

_____________________________
Bryan Dietz 
Aktion Associates 


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





Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact