Re: RPGLE Stored procedure user.

["Haas, Matt" <matt.haas@xxxxxxxxxxx>]

This will result in the name of the user used to make the database connection. If you are establishing DB connections for each user using their credentials, this will be okay but if you are using a connection pool of some sort, it will not be what you want. If you are using a connection pool, you'll need to pass in the user name to the stored procedure so it can be written to the database from the parameter.

Matt

------------------------------
date: Wed, 20 Oct 2010 10:17:11 -0500
from: BMay@xxxxxxxxx
subject: Re: [WEB400] RPGLE Stored procedure user.

Try having your program use the Current User instead of the Job User in 
PSDS...  Off the top of my head, I think the Current User is in positions 
358-367.

Brian May
Project Lead
Management Information Systems
Garan, Incorporated
Starkville, Mississippi



"Kevin Bucknum" <Kevin@xxxxxxxxxxxxxxxxxxx> 
Sent by: web400-bounces@xxxxxxxxxxxx
10/20/2010 10:12 AM
Please respond to
Web Enabling the AS400 / iSeries <web400@xxxxxxxxxxxx>


To
<web400@xxxxxxxxxxxx>
cc

Subject
[WEB400] RPGLE Stored procedure user.






Not sure if this belongs here or in the RPG400 or SQL lists, but I'll
start it here.

We are migrating our green screen applications to web using PHP. As part
of this I have created several stored procedures that call some utility
programs to avoid having to move too much business logic into the PHP
for the time being. I just ran into my first program where I do actual
updates on files. In most of our files we track the user that created
the record, and retrieve this from positions 254-263 in the program
status data structure. Unfortunately this contains QUSER when called
from my stored procedure. I searched, and haven't really come across
anything that seems relevant.  Anyone know of a work around for this?
Here is my stored procedure creation statement if it helps any:
<snip>