IBM Tivoli Monitoring, Version 6.3

tacmd listSdaStatus

Description

Use the tacmd listSdastatus command to display the SDA Enablement status for a monitoring server. You can display the SDA Enablement status for a list of monitoring servers or for all monitoring servers (default action). The SDA suspend state for the hub monitoring server is also provided if the command is issued to an ITM V6.3.0 (or later) hub monitoring server. The SDA suspend state defines the SDA activity for all the monitoring servers attached to the hub monitoring server. See the tacmd suspendSda and tacmd resumeSda commands for more information.

You must log in by using the tacmd login command before running the listSdaStatus command.

SDA Enablement status is indicated by the values of HUB/RTEMS name, STATE, and STATUS:
HUB/RTEMS name
The SDA Enablement status for the managed server name listed.
STATE
The values for SDA STATE are ON, OFF or ERROR, where
  • ON indicates that the server SDA function is active and operational.
  • OFF indicates that the server SDA function is not active and not operational. The state might be OFF if the KMS_SDA environment variable has not been set to Y or because the hub monitoring server is not active.
  • ERROR indicates that the server is configured for SDA. However, the server cannot perform SDA due to an error. The error might indicate a local error or if the server is a remote monitoring server, an error during synchronization or connection to the hub monitoring server. If the hub monitoring server’s SDA Enablement status is ERROR, the remote monitoring server SDA Enablement status will not indicate ERROR, but instead, OFF.
STATUS
See Table 1 to determine SDA STATUS error codes, symbols, explanations, and your response.
Table 1. SDA STATUS error codes
Value Symbol (KFASDM_CONFIG_*) Explanation Response
0 ST_Success SDA is operational. None.
1 SDM_InitError An error occurred while SDA was initializing, updating the SDA_STATE record, or while retrieving or processing the Suspend record. Contact Tivoli customer support.
2 ITM_HOME_
Missing
Indicates a non-MVS error only: on Windows - CANDLE_HOME undefined, on UNIX - CANDLEHOME undefined (possibly an installation error) Contact Tivoli customer support.
3 MANIFEST_PATH_
Missing
The TEMS environment variable TEMS_MANIFEST_PATH is undefined or the value is the empty string. This variable is defined by the installation program. If the configuration file has been edited, verify that the variable still exists and identifies a valid directory. If the predefined variable was not altered, contact Tivoli customer support.
4 MANIFEST_PATH_
TooLong
The path name specified through the TEMS_MANIFEST_PATH environment variable exceeds 512 characters. Redefine the manifest directory at a location whose path name is less than or equal to 512 characters.
5 MANIFEST_PATH_
NotFound
The directory specified through the TEMS_MANIFEST_PATH environment variable was not found. This variable is defined by the installation program. If the configuration file has been edited, verify that the value identifies a valid directory. If the predefined variable was not altered, contact Tivoli customer support.
6 SDM_ENABLED_
UnknownValue
The value assigned to the KMS_SDA environment variable is not valid. Assign a value of either Y|y (enabled) or N|n (disabled).
7 DISTREQMGR_
InitFailed
For remote TEMS only: the creation of the Distributed Request Monitor thread failed. Contact Tivoli customer support.
8 NOTIFICATIONMGR_
InitFailed
The creation of the thread to monitor the hub's TAPPLOGT table failed. In the case of a remote TEMS, this error can also occur if the creation of the thread to monitor the remote TEMS TAPPLOGT table failed. Contact Tivoli customer support.
9 REQUESTMGRTHREAD_
NotCreated
The creation of the Workload Manager thread failed. Contact Tivoli customer support.
10 HUB_SDA_Disabled For remote TEMS only: SDA has been disabled at the remote TEMS because SDA is disabled at the hub. This is the default configuration in which the TEMS is installed. To activate SDA, enable it at the hub.
11 HUB_SDA_Error For remote TEMS only: SDA has been disabled at the remote TEMS because SDA functions at the hub are inoperative. Run the listSdaStatus -n *HUB command to determine the nature of the error at the hub. Then refer to this table for the appropriate response.
12 HUB_SDA_
Unknown
For remote TEMS only: SDA has been disabled because the state of SDA at the hub is unknown> This error might indicate a communication failure with the hub. Once the remote TEMS re-establishes the connection to the hub, the error should be resolved. If not, contact Tivoli customer support.
13 HUB_SDA_
CommFailed
Unused. Not applicable.
14 BROADCASTMGR_
InitFailed
The creation of the Broadcast Manager thread failed. Contact Tivoli customer support.
15 BROADCASTMGRTHREAD_
NotCreated
Unused. Not applicable.
16 SDA_No The environment variable KMS_SDA has been set to N. None.
17 CMS_FTO_
Configured
For ITM v6.2.3 Fix Pack 1 or later hub only: SDA has been disabled because FTO is enabled on the hub. Prior to ITM v6.2.3 Fix Pack 1, FTO and SDA were mutually exclusive. Select one or the other or upgrade the hub to ITM v6.2.3 Fix Pack 1 or later.

CLI syntax

tacmd listSdaStatus
                      [ {-n |--temsname} TEMS... ]
  

where:
-n|--temsname

Specify one or more monitoring server names to display SDA Enablement status. If this option is not specified, the SDA Enablement status is displayed for all online monitoring servers that are able to perform SDA.

If a monitoring server specified by the –n|--temsname option is not online, is not SDA capable, or is not registered with the HUB, then a warning is displayed.

CLI example

The following example lists the SDA Enablement status for a specific set of monitoring servers.
Note: The ITM V6.3.0 hub monitoring server's output includes the SDA suspend state only if the monitoring server is suspended.
tacmd listsdastatus –n REMOTE_1 REMOTE_2 REMOTE_3

KUILSS200W: REMOTE_2 is not online and SDA enablement cannot be provided.

HUB/RTEMS   STATE    STATUS
REMOTE_1    ON       0
REMOTE_3    OFF      16
The following example lists the SDA Enablement status for a set of specified monitoring servers. In this example, assume that the second remote monitoring server is REMOTE_B. The error message reflects the incorrect name listed in the command.
tacmd listsdastatus –n REMOTE_A REMOTEB

KUILSS202W: TEMS name : REMOTEB is not connected to this HUB. Verify the input 
is correct and retry.

HUB/RTEMS   STATE   STATUS
REMOTE_A    ON      0
The following example lists the SDA Enablement for a set of monitoring servers that are SDA capable and online. The acting hub monitoring server (ITM V6.3.0) is HUB_A. HUB_A is configured for FTO. HUB_B is the FTO peer. The current suspend state is ON. The environment includes several remote monitoring servers including versions above V6.3.0. The uplevel version remote monitoring server has a new SDA failure STATUS.
tacmd listsdastatus

KUILSS203I:  SDA functions are suspended.
.

HUB/RTEMS     STATE     STATUS
HUB_A         ON        0
HUB_B         ON        0
RTEMS_6.3.0   ON        0
RTEMS_6.2.3   ON        0
RTEMS_6.3.1   ERROR     18

Related commands

tacmd suspendSda

tacmd listappinstallrecs

tacmd resumeSda

Return to Table 1.



Feedback