After upgrading the operating system the standard TSO logon screen is seen instead of the ACF2 TSO logon prompts. What is causing this?

Products

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

Issue/Introduction

After upgrading the operating system the standard TSO logon screen is seen instead of the CA-ACF2 TSO logon prompts. What is causing this?

Environment

Release:
Component: ACF2MS

Resolution

The ACF2 TSO front end, ACF82FLD, dynamically implants itself as IKJEFLD. The presence of the native IKJEFLD1 module in SYS1.LINKLIB takes precedence over the existence of ACF2 version of IKJEFLD (ACF82FLD), causing the native TSO logon screen to be invoked.

If you want to use an authorized logon preprompt exit with ACF2, you can link module USREFLD1 into the ACF82LD1 load module which resides in the ACF2 CAILOAD. USREFLD1 is taken after standard ACF2 processing and ACF2 will enable ACF82LD1 to get control as IKJEFLD1 if the CA ACF2 GSO TSO IKJEFLD1 option is turned on.

Therefore, with ACF2 whether you choose to use an authorized logon preprompt exit or not, the presence of IKJEFLD1 in SYS1.LINKLIB will cause the CA-ACF2 TSO signon to be bypassed and the native TSO signon will be used.

If you simply rename or delete IKJEFLD1 in SYS1.LINKLIB normal ACF2 TSO signon will resume.