Re: RPGLE Stored procedure user.

Actually - this program is a bad example as I do actually have the
option to pass in a user and override the one from the program status
data structure. But most of our programs don't do that. We don't do any
kind of connection pooling and require valid signons for all the
database and store procedure calls, so current user sounds like the way
to go. We had the program status data structure mapped to an external
file, but it had 334-429 mapped as unused. I've updated the file and
have recompiles going on all the objects that used it. Hopefully in a
little while I can change it to use the current user and only have to
modify future utility programs to use that as well.

Thanks.

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of Nathan Andelin
Sent: Wednesday, October 20, 2010 11:36 AM
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] RPGLE Stored procedure user.

Good point, Matt. I noticed the 10 Character @PUSER input parameter
that Kevin
specified in the procedure declaration. If that contains the correct
user ID,
why not use it. You probably don't want the user that the DB server job
is
running under.

-Nathan



----- Original Message ----
From: "Haas, Matt" <matt.haas@xxxxxxxxxxx>
To: "web400@xxxxxxxxxxxx" <web400@xxxxxxxxxxxx>
Sent: Wed, October 20, 2010 9:34:04 AM
Subject: Re: [WEB400] RPGLE Stored procedure user.

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