Testing UADS TSO Logon with no ACF2

book

Article ID: 130369

calendar_today

Updated On:

Products

CA ACF2 CA ACF2 - DB2 Option CA ACF2 for zVM CA ACF2 - z/OS CA ACF2 - MISC

Issue/Introduction



Establishing a break glass ID (ID already in UADS).
Issued a 'P ACF2' and ACF2 ended. Message '*ACF8A017 ACF2 TERMINATION COMPLETE'.
Issued a 'LOGON APPLID(TSO)'.
Message 'ACF82002 ACF2, SYSTEM NOT AVAILABLE, TRY LATER. ACF82904 ACF2, SESSION TERMINATED..

The UAD ID also exists in ACF2..
What is the procedure for shutting down ACF2 to test the UADS logon process?
Is there a special way to logon with ACF2 down to utilize UADS?

Environment

Release:
Component: ACF2MS

Resolution

The TSO logon, without ACF2 active, using SYS1.UADS, can only occur if ACF2 has not been started since IPL.
There is a parameter to use at logon time - FORCE - that will enable a logon to occur - but only if ACF2 has not already been started.

When you start ACF2 there is a communications vector table (accvt) created - if ACF2 is stopped, the ACCVT is still allocated.
The FORCE parameter at logon is disabled if ACF2 has been started... to stop someone shutting down ACF2 and then starting up a TSO session using UADS information.

To be able to logon with UADS you will need to IPL and not start ACF2.