With 2 CA Top Secret systems not sharing the security file, but using CPF to keep the security files in sync, if an ACID has the NOPWCHG attribure on 1 system but not on the other system, and that ACID changes the password at signon time on the system where it does not have the NOPWCHG attribute, the password change is propagated to the system where the ACID has NOPWCHG. Why?
This is functioning as intended. When the user changes the password on the system where NOPWCHG is not on the ACID and it propagates to the prod system where NOPWCHG is on the acid, the change on the receiving system is done as a command, not a signon. The NOPWCHG attribute only prevents ACIDs from changing passwords at signon or initiation.