XMA does not update added partitions if the XMA MOVER programs become invalid.

XMA does not update added partitions if the XMA MOVER programs become invalid.

Executing the XMA_SQLCOMPALL macro is required to validate all XMA object programs.

Step 1: Stop XMA pathway via XMA_MANAGER
Step 2: Load XMA Defines
TACL> XMA_LOAD_DEFINES
Step 3: Load XMA Defines
TACL> XMA_SQLCOMPALL
Step 4: Run SQL statement to ensure there are no XMA objects that are marked invalid.
TACL> SQLCI SELECT PROGRAMNAME, VALID FROM =XMA_CAT_PROGRAMS;
Note: the SQL statement above will display XMA object programs and their marked valid value. 
In here, Y is valid, N is invalid.
Step 5: Start XMA pathway via XMA_MANAGER

    • Related Articles

    • XMA: Newly added EPS Mover abends and will not start

      If a newly added EPS mover is abending and will not start steps should be taken to ensure both the UALOGD and UALOGD0 can be accessed by Merged Audit. Please check both files have appropriate guardian security and that there is no safeguard ACL ...

    • XMA: How to update audit file mask of a mover

      The audit file mask can not be updated. A new mover has to be added and the old mover can be deleted if desired. This applies to all the movers. If this article did not provide a solution, please open a case with our support team by sending an email ...

    • XMA: Measure Mover Keeps Abending

      Is XYPRO SecurityOne installed? The Measure mover is not designed to collect system performance metrics. It is designed to only capture process information for the XYGATE SecurityOne WHO Resolver. The MEASURE mover collects information regarding ...

    • XMA: XUA Mover abends when processing XUA protocol types

      Solution: Upgrade to XMA 2.45 or other Cause: XMA 2.43 and older could not properly extract protocol from XUA audits The issue is addressed in XMA Version 2.45 * ITID 245-13395 Update to Extract protocol type from XYGATE User Authentication (XUA) ...

    • XMA: How to Change the Safeguard Mover's IGNORE READ RECORDS parameter

      By default the Safeguard mover ignores the extraneous secondary READ records for file access attempts. If you wish to change the setting: XMA_MANAGER / Mover Menu / Option 12 / Parameters Menu /Option 12: Show Read Details If set to TRUE, the ...