The results of a monitoring server self-describing agent product installation, along with the current detected version of manually installed monitoring server products, are stored in the local monitoring server application properties (TAPPLPROPS) table.
The tacmd listappinstallrecs command returns the application support install records and displays the current self-describing agent product install status for all monitoring servers in the environment. Remember that these commands are not available when the Tivoli Enterprise Monitoring Server is not running. If the Tivoli Enterprise Monitoring Server and the Tivoli Enterprise Portal Server are both started, you can also see self-describing agent information and settings in the Audit Logs workspace.
This example shows how you can use the tacmd listappinstallrecs -t TEMS -d command to display the SDA_STATE of all active monitoring servers:
tacmd listappinstallrecs -t TEMS -d HUB/RTEMS PRODUCT VERSION GRPID ID IDVER SEEDSTATE STATE STATUS GBLTMSTMP RESOURCE QIBDUP LSTDATE LOCFLAG CATINSTMP CATINSVER MANUALINST CATSDA CONTENTS HUB_LZ TEMS 5530 SDA_STAT 0 1110610114348000 111061011434800 SDA_STATE=ON;SDA_STATUS=0; RTEMS_LZ TEMS 5530 SDA_STAT 0 1110610114022000 1110610114022000 SDA_STATE=ON;SDA_STATUS=0;
tacmd listappinstallrecs -t TEMS-d HUB/RTEMS PRODUCT VERSION GRPID ID IDVER SEEDSTATE STATE STATUS GBLTMSTMP RESOURCE QIBDUP LSTDATE LOCFLAG CATINSTMP CATINSVER MANUALINST CATSDA CONTENTS RTEMS_WIN TEMS 5530 SDA_STAT 0 1110608112310000 11106081000 SDA_STATE=OFF;SDA_STATUS=10; HUB_WIN TEMS 5530 SDA_STAT 0 1110609101851000 11106091000 SDA_STATE=OFF;SDA_STATUS=16;
0 | SDA is Enabled |
1 | SDA disabled because init failed. Contact ITM Support. |
2 | SDA disabled because of an internal error. Contact ITM Support. |
3 | SDA disabled because TEMS_MANIFEST_PATH is not set in the TEMS environment file. Please supply a valid value. |
4 | SDA disabled because TEMS_MANIFEST_PATH is not set in the TEMS environment file. Please supply a valid value. |
5 | SDA disabled because TEMS_MANIFEST_PATH is not set in the TEMS environment file. Please supply a valid value. |
6 | SDA disabled because KMS_SDA is set to a value other than Y or N. Please supply a valid value. |
7 | SDA disabled because of an internal error. Contact ITM Support. |
8 | SDA disabled because of an internal error. Contact ITM Support. |
9 | SDA disabled because of an internal error. Contact ITM Support. |
10 | SDA disabled because KMS_SDA=N at the HUB TEMS. Please enable SDA at the HUB TEMS. |
11 | SDA disabled because an SDA configuration error has disabled SDA at the HUB TEMS. Please correct the error at the HUB TEMS. |
12 | SDA disabled because the HUB TEMS cannot be reached. Verify that the HUB TEMS is running and can be reached by the RTEMS. |
13 | SDA disabled because of an internal error. Contact ITM Support. |
14 | SDA disabled because of an internal error. Contact ITM Support. |
15 | SDA disabled because of an internal error. Contact ITM Support. |
16 | SDA disabled because KMS_SDA=N. |
17 | SDA disabled because FTO is configured. |
HUB/RTEMS | PRODUCT | VERSION | GRPID | ID | IDVER | SEEDSTATE | STATE | STATUS |
HUB_LZ | A4 | 06230000 | 5655 | TMS | 06230000 | 0 | ||
HUB_LZ | HD | 06230000 | 5655 | TMS | 06230000 | Y | IC | 0 |
HUB_LZ | HD | 06230000 | 5655 | TPW | 06230000 | IC | 0 | |
HUB_LZ | LZ | 06230000 | 5655 | TPS | 06230000 | IC | 0 | |
HUB_LZ | NT | 06230000 | 5655 | TMS | 06230000 | 0 | ||
HUB_LZ | TEMS | 5530 | SDA_STAT | 0 | ||||
HUB_LZ | TM | 06230000 | 5655 | TMS | 06230000 | 0 | ||
HUB_LZ | 11 | 06230000 | 5655 | TMS | 06230000 | ME | 1005 | |
RTEMS_LZ | A4 | 06230000 | 5655 | TMS | 06230000 | 0 | ||
RTEMS_LZ | LZ | 06230000 | 5655 | TMS | 06230000 | Y | IC | 0 |
RTEMS_LZ | R6 | 06230000 | 5655 | TMS | 06230000 | 0 | ||
RTEMS_LZ | TEMS | 5530 | SDA_STAT | 0 | ||||
RTEMS_LZ | 11 | 06230000 | 5655 | TMS | 06230000 | Y | ME | 1014 |
The HUB/RTEMS column lists the node name of the Tivoli Enterprise Monitoring Server where the record was collected. Rows with IC in the STATE column stand for self-describing agent Install Complete. You can also see in this example that the hub monitoring server and the remote monitoring server both have an appinstallrecs entry for Tivoli Enterprise Monitoring Server (TMS) application support, but the hub monitoring server has two additional appinstallrecs entries for Tivoli Enterprise Portal Server support (TPS) and Tivoli Enterprise Portal Browser Client support (TPW) packages. The additional appinstallrecs entries are displayed because hub monitoring server also collects TPS and TPW packages so the portal server can collect these packages from the hub monitoring server.
IR | Install Request New install request on the work queue. |
IM | Install Metadata Retrieve the install request from the work queue and begin the metadata install and autorefresh work. |
MC | Metadata Complete Metadata install and autorefresh has completed. |
IC | Install Complete SDA application support has completed successfully. |
ME | Metadata Error Metadata Installation Error. STATUS code provides additional information. |
1002 | TEMS memory allocation error. |
1003 | Some SDA input argument passed to the TEMS was invalid. |
1004 | A target file was not found. |
1005 | Unknown SDA error occurred. |
1007 | Error occurred in the KT1 file transfer layer that was not covered by another status code. |
1011 | Manifest file parsing error on the TEMS, some unexpected content found in manifest file. |
1014 | Hub TEMS reports Unknown SDA error occurred. |
1015 | Expected length of an input argument is wrong. |
1016 | STATE updated by SDA work flow manager. |
1017 | Retryable Error. Usually a file transfer RPC timeout error when the TEMS tries to retrieve the SDA jar files from an agent. Retry this request after the time interval specified by the agent variable TEMA_SDA_RETRY_WAIT has expired. |
1018 | TEMS Auto-refresh error in catalog cache processing. |
1019 | TEMS Auto-refresh error in attribute cache processing. |
1020 | TEMS Auto-refresh error in OTEA cache processing. |