ACF2 - USERID DEFINED TO ACF2, NOT TO UADS. LOGON ATTEMPT ABORTED
search cancel

ACF2 - USERID DEFINED TO ACF2, NOT TO UADS. LOGON ATTEMPT ABORTED

book

Article ID: 195516

calendar_today

Updated On:

Products

ACF2 ACF2 - DB2 Option ACF2 for zVM ACF2 - z/OS ACF2 - MISC LDAP SERVER FOR Z/OS PAM CLIENT FOR LINUX ON MAINFRAME WEB ADMINISTRATOR FOR TOP SECRET

Issue/Introduction

Having an issue with TSO profiles not synchronising on SYSA.

Our 'sys1.uads' had to be corrected at mid-day today for a handful of users that were getting the following error when attempting to logon to TSO on SYSA.

Is there a command that we can run to have these users in sync with the sys1.uads dataset?

Here is the error:

ACF82102 USERID xxxxxx DEFINED TO ACF2, NOT TO UADS. LOGON ATTEMPT

ABORTED                                                            

IKJ601I TSO LOGON ATTEMPTING RETRY. ABEND 913, USER UNKNOWN , PROC

UNKNOWN                                                           

Environment

Release : 16.0

Component : CA ACF2 for z/OS

Resolution

Regarding error message……

ACF82102 USERID xxxxxx DEFINED TO ACF2, NOT TO UADS. LOGON ATTEMPT ABORTED



User xxxxxx tried to logon to TSO using a TSO user ID that is defined in the CA ACF2 Logonid database, BUT NOT in UADS.

The xxxxxx user ID must be defined in both the CA ACF2 Logonid and UADS databases before TSO access is permitted.



Please have your Security Administrator define User xxxxxx back in UADS.