Re: Inconsistent results from the QSYGETPH API

You don't say what the "flakiness" is but two ideas:

1. You are passing a password length of x'00000010' which indicates a
16-byte password. Is this really what you want? If you're really using
10-bytes passwords then perhaps your testing is finding trailing blanks
while the Lansa call is causing non-blank trailing characters.

2. You are using the job default CCSID when calling the API. Is it possible
in the web scenario that the job default CCSID is not set properly?

Just two items that jump out at me.
Bruce

On Tue, Oct 13, 2009 at 7:26 PM, Pete Wood <acedanger49@xxxxxxxxx> wrote:

I'm trying to authenticate users using their System i user id and password.
I pieced together a CL program to successfully call the QSYGETPH API but
I'm
having inconsistent results. If I debug the program, I get the expected
results every time (validated user id/pw combo, wrong password, user
profile
not found, etc). It is when I call the program from the web where the
flakiness begins. My "call stack" is a LANSA program calling the CL program
and the CL program calling the QSYGETPH API.

I have verified that the program is receiving the data as I expect it to be
passed. The entire CL program can be seen here - http://bit.ly/1wEkNP.
Would
anybody help me shed some light on why this program is behaving this way?

Thanks in advance,
Pete

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.