|
From job . . . . . . . . . . . : QTFTP00026
Have you checked QAUDJRN for password failure entries? Use journal codeT
entry type PW. Position 1 in the entry specific data shows theviolation
type and starting in position 2 is the user profile job user where thedisabled?
failure occurred. You can find the complete layout in appendix F of the
security reference manual.
Types of failures are...
A APPC bind failure.
C User authentication with the CHKPWD command failed.
D Service tools user ID name not valid.
E Service tools user ID password not valid.
P Password not valid.
Q Attempted signon (user authentication) failed because user profile is
disabled.
R Attempted signon (user authentication) failed because password was
expired.
This audit record might not occur for some user authentication
mechanisms.
Some authentication mechanisms do not check for expired passwords.
S SQL Decryption password is not valid.
U User name not valid.
X Service tools user ID is disabled.
Y Service tools user ID not valid.
Z Service tools user ID password not valid
Gary Monnier
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Glenn Gundermann
Sent: Friday, July 24, 2015 7:59 AM
To: Midrange Systems Technical Discussion
Subject: What is causing a user profile to be disabled?
Hi folks,
Is there a way to find out what is causing a user profile to be
is
I suspect it's an FTP process from another server that is causing this.
When I press Help on CPF1393 in QHST, there is very little information.
device *N
network address *N
subsystem QSYSWRK
This is happening several times each day. What's funny is that nobody
complaining about a process not working but obviously if they have thelist
wrong password something has got to be failing.
Any guidence would be appreciated.
Yours truly,
Glenn Gundermann
Email: glenn.gundermann@xxxxxxxxx
Work: (416) 675-9200 ext. 89224
Cell: (416) 317-3144
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxxlist
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.