I believe that if the profile/password is not valid, the API will return an
error that you can test.

Jeff Young
Sr. Programmer Analyst

On Tue, Jun 10, 2014 at 1:52 PM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

On 6/10/14 10:30 AM, Monnier, Gary wrote:

Have you thought of using the QSYCHGPR (Change last signed on date)
API in conjunction with a profile swap/unswap?

There is no profile swap/unswap involved. In this, or in any other
client-server product we've developed. That's why I've never actually used
the profile handle returned from QSYGETPH. And the indirect way we spawn
child-server jobs virtually guarantees that the 20k limit on any given
job's profile handles can never be approached, much less exceeded.

The problem is that this doesn't apply to a web service (which, unlike a
child-server job, has no real reason to run under the user's profile).

And what does a call to an API that updates the last-signed-on date have
to do with password checking, anyway?

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.

This thread ...


Return to Archive home page | Return to MIDRANGE.COM home page