All ACF2 LOGONIDs deleted by mistake and need to be restored
search cancel

All ACF2 LOGONIDs deleted by mistake and need to be restored

book

Article ID: 199596

calendar_today

Updated On:

Products

ACF2 ACF2 - z/OS ACF2 - MISC

Issue/Introduction

All of our ACF2 LOGONIDs were deleted by mistake by the Security Administrator. The ACF2 alternate database are now in use.  What is needed to restore the ACF2 primary logonid database?

Environment

Release : 16.0

Component : CA ACF2 for z/OS

Resolution

Using the ACF2 backup file, an IDCAMS REPRO is needed into the primary logonid database.  An example of the job is the nightly backup processing that deletes/defines the alternate databases, and then does a REPRO of the backup files into the new alternate databases.  After that process runs successfully, the databases can be switched back.  

Additional Information

Any changes that took place between the time of the backup and the restore will be lost.  That would include any logonids added or deleted, and any user password changes.  The ACF2 reports (ACFRPTLL) against the SMF data will help with redoing any of those tasks, except password changes.  The users will need to do that themselves again.