Re: Modifying CHGPWD

["Matthias Oertli" <oertlim@xxxxxxxxxxxxxxxx>]

On Mon, 29 Sep 1997 09:57:44 -0400, Al Barsa, Jr. wrote:

>>I've got no problem with the CL, DDS and the duplicated command,
>>it all works.
>>The real problem is this: if a userprofile is set to PWDEXP(*YES),
>>when that person next logs in the system requests a password change.
>>On pressing enter the 400 sends CPI2240 (Not allowed to change
>>password because you don't have authority to CHGPWD command)
>>Now the library, the CL, the DDS and the Command all are 
>>PUBLIC(*USE) which should be sufficient.
>>There must be a catch somewhere...
>>Anyone have an idea?
>
>The shipped public authority for CHGPWD is *USE.  Make sure that your
>command has not been changed.  The design of the AS/400 insures that
>changed public authorities will survive from release to release.  As a
>matter of fact, there's no way to restore authority for a command object
>onto a system without deleting the pre-existing command first.  If your
>command defaults have been changed from default and you want to reset them,
>you have to go to another system, and do DSPOBJAUT to an output file, etc...
>
I'm not quite sure what this has to do with the problem. My QSYS/CHGPWD
command's authority was never changed, it's as shipped by IBM.
There is no authority problem with QSYS/CHGPWD, there seems to be a
problem with the duplicate even though the authorities are set as mentioned
above.

Thanks,
Matthias
------------------------------------------------------------------------------------------------
Matthias Oertli, Sydney, Australia 

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to "MIDRANGE-L@midrange.com".
| To unsubscribe from this list send email to MAJORDOMO@midrange.com
|    and specify 'unsubscribe MIDRANGE-L' in the body of your message.
| Questions should be directed to the list owner/operator: david@midrange.com
+---