MDS Activity Monitoring Command

The mdsMonitor command outputs information regarding the MDM

activities that are currently being processed by an MDM Server. This

information spans all repositories loaded on the specified MDM Server.

The information displayed by the mdsMonitor command is formatted in

rows and columns, as shown in Figure 111.

S
Locks
Elapsed

ThrId t Username Protocol Command
Data Synch Time,ms Connection Repository

==============================================================================

2160 R Admin
MDSAdmin VerifyRep
SS
--
7440 MDM Console XYZ_BP

2622 W ATran

6507 R

CatMgr

Itsam

ImportRecords

GetActivityIn

- X* - -

-- --

5234 MDM Data Ma XYZ_BP

0

Figure 111. Output from the mdsMonitor command

Each row of output data represents a single command being processed

by the MDM Server. Each column contains information about the

current state of that command, as described in Table 111.

Table 111. mdsMonitor Columns

1

Only displayed when –W flag is added to the mdsMonitor command.

MDM Console
381

Column Description ThrId Thread number of the MDS activity processing the command St The current state of the command: W -- Waiting for a lock R -- Running Username The MDM user that issued the command Protocol The MDM internal protocol used to access the MDM Server Command The command or MDM Server method currently being processed. Locks Lock information is displayed in the format AB CD, where: A describes the state of the MDM Server data lock. B describes the state of the MDM Repository data lock. C describes the state of the MDM Server synch lock. D describes the state of the MDM Repository synch lock. The possible states for a lock are: -- No lock requested - -- Share lock requested S* -- Share lock acquired S -- eXclusive lock requested X* -- eXclusive lock acquired X Elapsed Time Elapsed time in MS since the activity started. Connection The MDM client application which triggered the command request. Repository The MDM repository for which the command was requested 1 Remote Host If the command was triggered by an MDM client application, the name of the machine on which the MDM client application is running.

Part 14: CLIX Command Line Interface

With mdsMonitor you can quickly view the activities on an MDM

Server and identify any performance bottlenecks in your system.

Figure 111, for example, shows that the user “Admin” issued a

VerifyRep command for the repository XYZ_BP. The VerifyRep

command acquired shared server and repository data locks, and the

operation has been running for 7440 milliseconds.

It also shows that user “ATran” launched an ImportRecords operation

on the same repository, and that this operation has been waiting 5234

milliseconds for an exclusive data lock before it can begin.

TIP ►► The standard output of the mdsMonitor command is limited

to a width of 80 characters. If you issue the command with the [–W]

flag, the output is expanded to a width of 120 characters. With the

wider output, MDM adds the Remote Host column and relaxes the

cutoff limit for displaying name data in a column.

NOTE ►► mdsMonitor output is provided as a “snapshot” but can

be refreshed every certain number of seconds if the command is

issued with the [-T seconds] flag. Some commands may be

requested, executed, and completed within this interval and so will not

appear in the output.

NOTE ►► Only information regarding data locks and synchronization

locks is displayed in the Locks column. Information about locks used

by other MDM activities is not currently shown.

NOTE ►► The mdsMonitor command is itself reported as the

GetActivityIn command in the mdsMonitor output.

NOTE ►► mdsMonitor output changed from MDM 7.1 to MDM 7.1

SP2 to make it more readable. This section describes the updated

format.