Tivoli Header

User's Guide

wdmlseng

Returns a list and the status of all resource models that have been distributed on a specified endpoint.

Syntax

wdmlseng -e endpoint [-verbose] [-xml]

wdmlseng -e endpoint -p profile#region [-verbose] [-xml]

wdmlseng -e endpoint -p profile#region -r resource_model [-verbose] [-xml]

wdmlseng -e endpoint -p profile#region -r resource_model -i indication [-verbose] [-xml]

Description

This command returns a list of all the resource models that have been distributed on the specified endpoint. The status of each resource model is also displayed. Some status codes are standard; others are defined by the user in the Tivoli Monitoring Workbench, in which case they are accompanied by a user-defined reason code.

The status can be one of the following:

Disabled: The resource model has been distributed but not started.
Error: An error has occurred with the Tivoli Monitoring engine, possibly due to a failure in the resource monitoring agent.
Failed reason code: A resource model has failed.
Failed after recovery reason code: A resource model has failed after the recovery operation has tried running it three times (see "Recovering").
Failing reason code: The endpoint engine tries to run the resource model once every three minutes, indefinitely.
Missing prerequisites: One or more prerequisites of the resource model is not being met. For example, if you distribute the Print resource model to a Windows NT system, this status is generated because the resource model works only with Windows 2000.
Not compiled: The resource model has not been compiled.
Recovering reason code: The endpoint engine tries to run the resource model once every cycle, for three cycles only, after which the status is changed to failed after recovery.
Retrying reason code: The endpoint engine tries to run the resource model three times in each cycle, indefinitely.
Running: The resource model is running.
Scheduled: The resource model has been scheduled to be started.
Stopped: The resource model has been stopped. It is compiled and enabled and is not in an error state but it is not running and is not scheduled.
Unable to start reason code: A resource model has been unable to start.

Several examples of the output are given

The first shows the output received when sending a request at endpoint level (with just the endpoint specified) and without the verbose option:

Forwarding the request to the engine...
The following profiles are running:
myprofile#ucaselli-region
    TMW_Processor            :Running
[ucaselli][y:/w32-ix86/cdrom]

The second output example shows the same endpoint with the verbose setting:

Forwarding the request to the engine...
The following profiles are running:
myprofile#ucaselli-region
    TMW_Processor            :Running
        TMW_ProcessorBusy                             100 %
        TMW_HighProcesses                             100 %
        TMW_CPUCantKeepUpWithHW                       100 %
        TMW_HWKeepingCPUBusy                          100 %
        TMW_BusyHardware                              100 %
        TMW_HighPercentUsageDelta                     100 %
[ucaselli][y:/w32-ix86/cdrom]

The third output example shows the same endpoint with the verbose setting in XML format:

Forwarding the request to the engine...
The following profiles are running:
<Profiles>
   <Profile Name="myprofile#ucaselli-region">
      <RMs>
         <RM Name="TMW_Processor" Status="Running">
            <Indications>
               <Indication Name="TMW_ProcessorBusy" Health="100">
                  </Indication>
               <Indication Name="TMW_HighProcesses" Health="100">
                  </Indication>
               <Indication Name="TMW_CPUCantKeepUpWithHW" Health="100">
                  </Indication>
               <Indication Name="TMW_HWKeepingCPUBusy" Health="100">
                  </Indication>
               <Indication Name="TMW_BusyHardware" Health="100">
                  </Indication>
               <Indication Name="TMW_HighPercentUsageDelta" Health="100">
                  </Indication>
            </Indications>
         </RM>
      </RMs>
   </Profile>
</Profiles>

Options

-e endpoint

Specifies the endpoint on which the command is to be performed.

-i indication

Specifies the indication on which the command is to be performed. If the indication is not specified the command is performed on all indications in the specified resource model.

-p profile#region

Defines the profile on which the command is to be performed. If the profile is not specified, the command will be performed on all profiles at the endpoint. The profile name must always be fully qualified with the policy region name in the syntax shown.

Note:

To obtain a listing of the complete names of all the profiles that are on an endpoint, issue the following command:

wdmlseng -e endpoint

-r resource_model

Specifies the resource model on which the command is to be performed. If the resource model is not specified the command is performed on all resource models in the specified profile.

-verbose

Displays all indications for each resource model. The worst instance key (if it exists) and the status (consolidation level) of each indication are also displayed. The consolidation level indicates the completion status of the generated occurrences that are required to trigger the particular event.

If a profile is specified, all indications are displayed for each resource model of that profile.

If a resource model is also specified, all instances are displayed for each indication of that resource model.

If an indication is also specified, all categories (the indication's string property value) and metrics (the indication's numeric property value) data are displayed for each instance.

-xml

Displays the output in XML format.

Authorization

Requires the super, senior, admin or user roles.

Examples

This example shows the command necessary to list all the resource models at the endpoint MyEndpoint with full details of all indications in XML format:
```
wdmlseng -e MyEndpoint -verbose -xml
```
This example shows the command necessary to list all the resource models in the profile MyProfile at the endpoint MyEndpoint with full details of all indications in XML format:
```
wdmlseng -e MyEndpoint -p MyProfile -verbose -xml
```
This example shows the command necessary to list the resource model MyResourceModel in the profile MyProfile at the endpoint MyEndpoint with full details of all indications in XML format:
```
wdmlseng -e MyEndpoint -p MyProfile -r MyResourceModel -verbose -xml
```
This example shows the command necessary to list the indication MyIndication in the resource model MyResourceModel in the profile MyProfile at the endpoint MyEndpoint with full details of all indications in XML format:
```
wdmlseng -e MyEndpoint -p MyProfile -r MyResourceModel -i MyIndication 
-verbose -xml
```

See Also

wdmcmd

wdmeng

wdmtrceng

[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]