Re: CHGUSRPRF and the audit journal -- MIDRANGE-L

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

Martin Rowe wrote on 02/15/2006 04:52:32 PM:

> On 15/02/06, Shalom Carmel <shalom@xxxxxxxxxx> wrote:
> > I tested the CHGUSRPRF command on a V5R2 server, and discovered
> that not all
> > changes create an audit entry.
> > For example, changing the password expiry interval for a user does not
> > create any audit entry.
> > Seems a bit problematic, doesn't it?
> > Does anyone know what changes are actually logged in the audit journal?
>
> Shalom
>
> Look at the system supplied journal outfile for Change Profile -
> QASYCPJ5. That tells you the fields that are tracked. We're on V5R2
> too and the expiry interval isn't there.

Martin,

The Password Expiration Interval is one of the new fields that was added to
the CP audit record in V5R4. The other new field in this audit record is
one for Password Confirmation Conformance. This field can be used to let
you know when someone used CHGUSRPRF to set a password that does not meet
the password rules for the system.

Ed Fishel,
edfishel@xxxxxxxxxx

This mailing list archive is Copyright 1997-2025 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.