XMA: How to decrease the maximum CPU busy percentage for a mover

XMA: How to decrease the maximum CPU busy percentage for a mover

The maximum CPU busy for a mover can be configured within XMA_MANAGER.

If the CPU Usage is greater than or equal to the percentage specified in CPU Busy, the MOVER will sleep for a random interval of 1 to 3 seconds.

The default value is 30%. If desired, a lower (or higher) value can be specified. (Steps Below)

>run xma install  
>XMA_MANAGER
>2.movers
>12. alter pathway
>4. ems
    >enter the mover name
>5. CPU Busy Percent
>R. to run 


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: MADELDBC Process using increased CPU resources.

      Upgrade to XMA 2.45 or later. Workaround: If unable to immediately upgrade to XMA 2.47, a filter can be added tot he FILTERS file that should assist in cleaning up the database. FILTERDEFBEGIN $DB_CLEANUP STATUS ACTIVE MOVER_BEGIN MOVER_SELECT_BEGIN ...

    • 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: 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: SLSENDER is busy

      Use the XMA_SQLCOMPALL macro to generate a new optimized query plan, which will then be used when compiling the objects. TACL> VOLUME $SYSTEM.XYGATEMA TACL> RUN XMA INSTALL TACL> XMA_PWSTOP TACL> XMA_SQLCOMPALL TACL> XMA_PWCOOL The XMA_SQLCOMPALL ...

    • XMA: Changing Transaction Size for Cleanup/Archive Params

      There are 2 solutions, one for XMA v1.90 and later, and pre-v1.90 pre-v1.90 Perform the following commands, substituting the actual volume name XMA is installed in for $volume in the following steps; INSERT INTO $volume.XMADAT.PARAMS VALUES ("ARCHIVE ...