× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Kevin,

current user is relatively new...heck prior to v5r4 WRKACTJOB just
showed the job user.

You may want to consider changing the name of the existing variable to
JOBUSER or some such, then reuse the existing name for the current
user field.... as for the most part if you want the user profile,
current user is what you want. In a green screen program, they'd be
the same.

UNLESS, your applications themselves make use of the swap profile
APIs...then the swapped to profile shows up as the current user (which
is how the IBM host servers work) You may be doing it for IFS
authority since the IFS doesn't support adopted authority.

HTH,
Charles

On Wed, Oct 20, 2010 at 12:53 PM, Kevin Bucknum
<Kevin@xxxxxxxxxxxxxxxxxxx> wrote:
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



--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.




Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550

--
This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
To post a message email: WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/web400
or email: WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/web400.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 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 copyright@midrange.com.

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