Re: SEP debug and RUN SQL Scripts...

Let me provide an example...

Say I have a application running on a Windows web server.

That app may use a single IBM i user ID to connect to the system, call it
MYAPPUSR.

I could code the app the set for instance, the windows user name of the
user using the app in CLIENT_USERID.

Charles


On Wed, Jan 31, 2018 at 1:45 PM, Charles Wilt <charles.wilt@xxxxxxxxx>
wrote:

The special register don't mean anything...just a way for an ODBC/JDBC app
to pass info to the system.

Buck's question was regarding what user ID you actually use to sign onto
the sessions...

Charles

On Wed, Jan 31, 2018 at 12:23 PM, Robert Rogerson <rogersonra@xxxxxxxxx>
wrote:

Thanks Charles but I think Buck found the problem.

I called the procedure from both interfaces and then looked at the job
logs on the system. It was then I noticed at the start of the sessions
where they were different.

ACS -

The following special registers have been set: CLIENT_ACCTNG: Windows
7;SSL=false;admin_user=true, CLIENT_APPLNAME: IBM i Access Client
Solutions - Run SQL Scripts, CLIENT_PROGRAMID:
file:/D:/Robert/IBM/ClientSolutions/acsbundle.jar, CLIENT_USERID: User,
CLIENT_WRKSTNNAME: 10.200.60.78

iNav -

The following special registers have been set: CLIENT_ACCTNG: ,
CLIENT_APPLNAME: System i Navigator - Run SQL Scripts, CLIENT_PROGRAMID:
cwbunnav.exe, CLIENT_USERID: RROGERSON, CLIENT_WRKSTNNAME: ISSDESKTOP2


Should the CLIENT_USERID on ACS be RROGERSON? If so, how do I set it
(I've tried searching myself as well as google)

Thanks,

Rob



On 1/31/2018 1:20 PM, Buck Calabro wrote:

On 1/31/2018 1:03 PM, Robert Rogerson wrote:

In the new Run SQL Scripts (ACS) I call the stored procedure and it

completes and does not break.

Is this session using the same user profile specified in the SEP?

--
This is the Rational Developer for IBM i / Websphere Development Studio
Client for System i & iSeries (WDSCI-L) mailing list
To post a message email: WDSCI-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/wdsci-l
or email: WDSCI-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/wdsci-l.