XMA: Cannot Start $XMA Pathway - Startup attempt fails with no errors

XMA: Cannot Start $XMA Pathway - Startup attempt fails with no errors

Check the HOMETERM value in the MACONF file.  The MACONF file is found in the XYGATEMA installation subvolume.  The HOMETERM value must be a valid / existing home terminal process name.

Sample MACONF file:

PATHMON_NAME                $XMA
PRIORITY                           030
PERUSE_OBJECT                \MYSYS.$SYSTEM.SYSTEM.PERUSE
COLLECTOR                        $S
COMPANY_NAME                "XYGATE MERGED AUDIT"
HOMETERM                      $VHS
MACRO_NAME                    XMA

If the HOMETERM is $VHS, make sure that $VHS has been started.  If the HOMETERM name is another invalid or non-existent process, replace it with a valid HOMETERM value, exit the MACONF file and retry the XMA pathway startup.



If this article did not provide a solution, please open a case with our support team by sending an email message to support@xypro.com.

    • 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 change HOMETERMs for all the SERVERCLASSes in the Pathway

      Shutdown the pathway -- XMA_PWSTOP to create PWSTATE file Edit the pathway config file -- open PWSTATE file in XMAPW subvol and change the HOMETERMs Cold start the pathway ? XMA_PWCOLD If this article did not provide a solution, please open a case ...

    • XMA: Pathway 1163 Licensing error on startup

      FIX: Identify the XYGATEOS ACL FOGROUP that restricted access using XOS_EXPLAIN. Logon as the owner of the XYGATEOS installation. TACL> VOLUME $<Volume>.<XYGATEOS Installation Subvolume> TACL> RUN XOS INSTALL TACL> XOS_EXPLAIN Access check:READ FILE ...

    • XMA: Mover cannot be started - no saveabends and no EMS errors

      Check to make sure that the name of the object program for the XMA pathmon process, (e.g. $XMA) is PATHMON,usually $SYSTEM.SYSTEM.PATHMON. This is because XMA relies on the program name to identify a process a being a pathway process. Any XMA ...

    • XMA: XMA_MANAGER macro fails with [Check_SQLCompileNeeded] error

      The XMA SQL database needs to be recompiled for this error to be resolved. 1) stop XMA XMA_PWSTOP 2) Update the database statistics and re SQLCOMPILE all the XMA programs XMA_SQLCOMPALL 3) Start XMA XMA_PWCOOL If you are unable to locate the solution ...