RE: Using QSYGETPH to get profile handle is failing

["John R. Smith, Jr." <smith5646@xxxxxxxxx>]

I'm going to bet they are passing parameters 5 & 6.  I will verify later
today and update this chain.

I saw the comment about the expired password in the documentation but if the
password is set to *NONE can it be expired because *NONE says there isn't
one?
 

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Scott
Klement
Sent: Friday, September 12, 2014 1:58 AM
To: Midrange Systems Technical Discussion
Subject: Re: Using QSYGETPH to get profile handle is failing

Hi John,

The 7.1 documentation for QSYGETPH can be found here:
http://www-01.ibm.com/support/knowledgecenter/ssw_ibm_i_71/apis/QSYGETPH.htm

Or, here's a shorter one, easier to use from E-mail
http://tinyurl.com/QSYGETPH

There are certain IBM accounts (see the link above) that you cannot get a
profile handle for, no matter what your authorities, et al are.

Also, *NONE will not work for an expired password.

Also, you must ensure that you are NOT passing parameters 5 & 6 (length &
CCSID of password) when you use a special value like *NOPWD.  It will always
fail if you specify *NOPWD/*NOPWDCHK/*NOPWDSTS.  (I don't remember when this
rule was added, it might've been V5R3?  But I know it was added for security
reasons, and broke backward compatibilty with some programs.)

Maybe of the above things explains your problem?  If not, I would definitely
read over the 7.1 version of the docs and see if that helps.


On 9/11/2014 10:29 PM, John R. Smith, Jr. wrote:
> I have a client on V7R1 that is trying to retrieve a profile handle for a
> profile that does not have a password (*NONE) and their program is
receiving
> CPF22E5 - No password associated with user profile &1.  The profile is not
> disabled and the profile running the job is *SECOFR and has all the
> appropriate *SECOFR authorities (*ALLOBJ, *SECADM, etc.).  They are using
> QSYGETPH with the password parameter = *NOPWD.
>
>
>
> Per the IBM documentation (V5R2 is the only version I could find anything
> on).
>
>
>
> If the password is *NOPWD or *NOPWDCHK, the user requesting the profile
> handle must have *USE authority to the user profile.
>
>
>
> Also, per the IBM documentation (also V5R2).
>
> No profile handle is created in the following situations:
>
> *	The user profile is disabled and *NOPWDCHK is not specified for the
> password parameter, or *NOPWDCHK was specified but the user requesting the
> profile handle does not have *ALLOBJ or *SECADM special authority.
> *	The password has expired and *NOPWDCHK is not specified for the
> password parameter, or *NOPWDCHK was specified but the user requesting the
> profile handle does not have *ALLOBJ or *SECADM special authority.
> *	The password is *NONE, and *NOPWD or *NOPWDCHK is not specified for
> the password parameter.
>
> Does anyone have any idea why this is failing?