Re: QUser and jdbc access to os400 -- JAVA400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: QUser and jdbc access to os400
From: David Gibbs <david@xxxxxxxxxxxx>
Date: Thu, 11 May 2006 13:57:40 -0500
List-archive: <http://archive.midrange.com/java400-l>
List-help: <mailto:java400-l-request@midrange.com?subject=help>
List-id: Java Programming on and around the iSeries / AS400 <java400-l.midrange.com>
List-post: <mailto:java400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/java400-l>, <mailto:java400-l-request@midrange.com?subject=unsubscribe>

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

Follow-Ups:

RE: QUser and jdbc access to os400 , Rick DuVall

This mailing list archive is Copyright 1997-2026 by midrange.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 on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.