Exit point considerations for a new instance - Assure_Secure_File_Transfer_ - Assure_Elevated_Authority_Manager_(EAM) - Assure_Secure_File_Transfer_PGP - Assure_Encryption - Assure_Secure_File_Transfer - Required_for_All_Modules - Assure_Monitoring_and_Reporting_(AMR) - Assure_Security_Multi-Factor_Authentication_(MFA) - Assure_DB2_Data_Monitor_(DB2MON) - Assure_System_Access_Manager_(SAM) - Assure_Secure_File_Transfer_with_PGP - 7.0

If you have existing applications that use IBM i exit points to monitor the system, you need to confirm that the exit points used will not conflict with the exit points that you will use in Assure System Access Manager. This is required for new installations that have applied a license key for any of the following features that use IBM i exit points:

Required for Licensed Feature Assure System Access Manager Assure Secure File Transfer

The Assure System Access Manager feature cannot coexist with other applications that use the same IBM i exit points that it uses. Most of the IBM i exit points used support only one exit program. One notable exception is the QIBM_QCA_RTV_COMMAND exit point, which supports a maximum of ten retrieve command exit programs for each command.

For a complete list of the exit points used by Assure System Access Manager and their restrictions, see the Assure System Access Manager User Guide. If you need to use  existing exit programs provided by other applications, contact your Precisely Support representative for advice.

Activating or deactivating a program on an exit point often requires that services or servers on the IBM i system are stopped and restarted. After the initial installation of Assure Security, you may need to end other applications that use exit points before upgrading your Assure Security instance.