ACFRPTPW - A report that can be run against the SMF data. This will show
many different reasons as to why a logon wasn't any good. ie - password
not matched, invalid syntax, password expired. There is a pre-processor
utility as generally ACF2 logs to a SMF record ( we're 230 ) and the
pre-processor breaks them out for the various reports. This can be done
via the ISPF panels as well as batch jobs. That I know of, and we have
users timing out here all the time, ACF2 does not cut an entry for that.
On 5/12/2016 2:48 PM, Donald Likens wrote:
I am sure this is not the correct place to ask this question but I hope someone
can help me (or at least direct me to the correct place to ask this question).
Note: We are supporting a client with ACF2... We do not have an ACF2 license at
our shop.
We are assisting a customer in trying to determine why they are getting so many ‘Invalid
Password\Authority’ ("P") ACF2 SMF records. It seems like most of these records are
being written when there is no invalid passwords by the user. It appears after a successful login
after idle timeout, ACF2 is cutting an ‘Invalid Password\Authority’ ("P") SMF record.
Can anyone help us to identify a field and values in the SMF record that would allow us to
distinguish between a true “invalid password” and a false-positive after a user is timed out?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
--
Brian W. France
Systems Administrator (Mainframe)
Pennsylvania State University
Administrative Information Services - Infrastructure/SYSARC
Rm 25 Shields Bldg., University Park, Pa. 16802
814-863-4739
[email protected]
"To make an apple pie from scratch, you must first invent the universe."
Carl Sagan
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
