RE: Modifying CHGPWD -Reply -- MIDRANGE-L

Changing the command in QSYS may help, but the real question is: When 
signing on, if the user's password is expired does OS/400 a) exec the 
*libl/chgpwd command, b) exec qsys/chgpwd, c) call *libl/QMNCGPWD , d) call 
qsys/QMNCGPWD, e) do something else.

If the answer is a or c then he can solve the problem with something higher 
in the library list than qsys.

If the answer is b then he can solve the problem by changing qsys/chgpwd, 
maybe. IBM commands don't pay attention to the CPP specified on the command 
definition. They use an index into the system reference table to jump 
directly to the address for the CPP. This index is stored in the command 
header. If the CHGCMD command resets this entry then he is all set, if not 
then he has a problem. This option is also subject to the general rule of 
"don't touch qsys!"

If the answer is d then he is generally screwed. You CANNOT replace the 
program in qsys or the base command would not work, unless you also changed 
the system reference table, (Use Alter Storage in SST if you want to, I 
know I don't)

If the answer is e then all bets are off.

-Walden

-------------------------------
Walden Leverich
Tech Software
walden@techsoftinc.com
www.techsoftinc.com

-----Original Message-----
From:   DAsmussen@aol.com [SMTP:DAsmussen@aol.com]
Sent:   Sunday, October 05, 1997 5:35 PM
To:     MIDRANGE-L@midrange.com
Subject:        Re: Modifying CHGPWD -Reply

Matthias,

In a message dated 97-10-04 20:49:40 EDT, you write:

> >Hope this finds everyone well after COMMON,  sounds like the problem is
>  >not the authority of the command but who is trying to run it... in your
case
>  >you must make sure the CL that you wrote is owned bu QSECOFR or a
>  >Group or User that has *SECADM , that is required to chg user profiles,
>  >after checking that make sure your program is running as user profile
>  >*owner not *user.... you can check this with DSPPGM and it can be
>
>  Thanks for your suggestion.
>  Unfortunately it did not help. All objects used are owned by QSECOFR
>  with PUBLIC(*USE). The CL is running as *OWNER.

OK, I've been quiet about this but, lacking a definitive response, I used
DSPCMD to see that the CPP for this command is hard-coded to QMNCGPWD in
QSYS.  You should (given enough authority) be able to change the command to
use either *LIBL or some other with the CHGCMD command.  You might want to
consider the little-known "product library" function of commands to point 
to
your desired library (appears either before or after "current" library, I
don't don't remember) and always before User Libraries.

HTH,

Dean Asmussen
Enterprise Systems Consulting, Inc.
Fuquay-Varina, NC  USA
E-Mail:  DAsmussen@AOL.COM

"The difference between genious and stupidity is that genious has its
limits." -- Anonymous
+---
| 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
+---

+---
| 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
+---