× 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.



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?



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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 [javascript protected email address].

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