Related Articles
XMA: FUP RELOAD does not reclaim space
When running FUP RELOAD, specify NEW option as highlighted below. FUP RELOAD $SYSTEM.XMADAT.<table name>,NEW,RATE 30,SLACK 0 Below description of NEW option is from HPE FUP manual. NEW specifies to perform a new reload operation on <filename> even if ...
XMA:Ways to address SQL error due to error 45 in AUDDET or AUDSESS
Below are the Steps for ?Option 1? clean up the obsolete data records: Step: Option 1.0. Logon as an owner of XMA installation and install XMA macro at TACL Step: Option 1.1. Stop XMA Pathway by running the XMA_PWSTOP macro at TACL (or at the ...
XMA: Error compiling CNVRTIP when upgrading to XMA 2.41
Purging CNVRTIP from the XYGATEMA subvol and running XMA_MANAGER again will allow the upgrade to proceed as expected. TACL> VOLUME <XMA INSTALLATION VOLUME/SUBVOLUME> TACL> XMA INSTALL TACL> XMA_VOLUME TACL> FUP PURGE CNVRTIP TACL> XMA_MANAGER Note: ...
XYGATE: Installing XMA using XAI
Copy the following file, to your Desktop as an icon, from the following link. \\fs.xypro.com\filesrv\HP\HP_XYGATE_DISTRIBUTION\Release_tracking Click on the icon to open the file. Click on the ?Summary? tab at the bottom of the file. You will see the ...
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 ...