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


  1.  Home
  2. MIDRANGE-L
  3. September 2014

Using QSYGETPH to get profile handle is failing

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