×
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.
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
As an Amazon Associate we earn from qualifying purchases.
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
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
