XMA: SLSENDER - Steps to follow for SLSENDER When Upgrading to XMA 2.65

XMA: SLSENDER - Steps to follow for SLSENDER When Upgrading to XMA 2.65

The upgrade to XMA 2.65 makes changes to the SYSLOGQ table.  Consequentially, this could cause fatal errors for SLSENDER when it it initially started following the upgrade.  This is due to outstanding TMF transactions that remains until they are aborted TMF following the XMA pathway shutdown.  The following is a method of avoiding issues of this type.

1.  Stop SLSENDER using Option 21, Maintain Administrative Servers from the Movers Management Menu in XMA_MANAGER before starting the XMA upgrade. This option allows the server to cleanup
     outstanding TMF transactions before shutting down.  
 
      Example:

       RUN $<vol>.XYGATEMA.XMA INSTALL
       XMA_MANAGER
       Select Option 2, Movers
       Select Option 21, Maintain Administrative Servers
       Select Option 3, Stop SLSENDER

       Return to the XMA_MANAGER Main Menu to stop the remaining servers and shut down XMA pathway.  From the XMA_MANAGER Main Menu:

        Option 1, Pathway
        Option 3, Stop

Following the XMA pathway shutdown, a FUP LISTOPENS against the SYSLOGQ table should show if any outstanding TMF transactions still have it open.

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: SLSENDER fails to start after upgrading to Merged Audit 2.65

      There is a known issue where SLSENDER will not start after upgrading to XMA 2.65. If the customer cannot start SLSENDER after upgrading, the post upgrade steps below can be used. If we know a customer will be upgrading to XMA 2.65, pre-upgrade steps ...

    • XMA: How to uninstall SLSENDER.

      As the SLSENDER is configured and added to the XMA pathway when the customer follows the installation process in the XMA manual. The following procedure can be used to manually stop the SLSENDER , remove any records that have been generated, and stop ...

    • XMA: TMF is keeping active transactions open for SLSENDER after SLSENDER and XMA Pathway are stopped

      The reason for this behavior because is the XMA TACL routines are shutting down the pathway with the Pathmon command ?SHUTDOWN2, MODE IM, UNTIL DONE?. The ?MODE IM? means that it stops the servers immediately but does not close them. This allows them ...

    • 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: ...

    • XS1 - Upgrading from Version 1.90 to Version 1.97

      Please review this entire KB before starting any upgrade from XS1 v1.90 to release 1.97. 1. Review the document "XS1 v1.97 Installation and Set Up Guide. It contains a section, "Upgrading from XS1 1.90 to 1.97" that contains steps to follow when ...