XMA: Measure Mover Keeps Abending

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 process ancestry.  If XYGATE SecurityOne is not installed on the system, then there is no need to configure a Measure mover.  Any Measure mover configured on a system without SecurityOne installed should be stopped and deleted.

If XYGATE SecurityOne is installed and the WHO resolver is in use, then XYPRO Support should be contacted for help in determining why the mover keeps abending.


If the Measure mover was automatically configured and started using the XMA Mover Discover process:

 If the Discover option was selected to automatically add movers, it will search the system for all installed XYGATE products, as well as Safeguard, EMS, Base24 and Measure.  It will then configure the mover settings for the products found and store these settings in a user-named edit file.  This edit file can then be edited to select which movers should be added before executing the step that creates them.  This avoids having to delete any undesired or unnecessary mover later.   Chapter 3, Installing XMA in the XMA 2.65 manual provides more information on the Discover process and modifying the edit file to prevent movers from being added automatically to the XMA pathway configuration.


If you are unable to locate the solution needed or if you need additional assistance, please Click Here to open a case from our Customer Care Portal.

    • 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: Safeguard Mover Abends After Pathway Reset and Daylight Savings has ended

      Use the following steps in order to resolve this condition: You will need the last record processed by the Safeguard mover. TACL> VOLUME $<XMA Database Volume/Subvolume> TACL> SQLCI >> SELECT LASTRECORDGMTTSTMP FROM SFGST BROWSE ACCESS; SQL ...

    • XMA: Error 72 - Mover Deadlock Condition

      To reduce the transaction size in the SLSENDER, follow these steps below: Volume to the XMA Installation Subvolume (ie. VOLUME $<VOL>.XYGATEMA) Run XMA INSTALLATION to attach the XYGATEMA segment Type: XMA_MANAGER to manage the pathway Select 2: ...

    • 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: Can't start iTP Webserver Mover - SQL Error

      Probable cause is that the iTP webserver mover is attempting to process a file type that is not yet supported. Several file formats are not currently supported by the iTP mover: HTTPD log support. The format is not CLF format but a hybrid of access ...