Tivoli Manager for Domino Reference Guidepublib.boulder.ibm.com/tividd/td/TDSdomino/GC32... · The...

Tivoli Manager for DominoReference GuideVersion 3.1.0 GC32-0675-00

Tivoli Manager for DominoReference GuideVersion 3.1.0 GC32-0675-00

Tivoli Manager for Domino Reference Guide

Copyright Notice

© Copyright IBM Corporation 2001. All rights reserved. May only be used pursuant to a Tivoli Systems SoftwareLicense Agreement, an IBM Software License Agreement, or Addendum for Tivoli Products to IBM Customer orLicense Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrievalsystem, or translated into any computer language, in any form or by any means, electronic, mechanical, magnetic,optical, chemical, manual, or otherwise, without prior written permission of IBM Corporation. IBM Corporation grantsyou limited permission to make hardcopy or other reproductions of any machine-readable documentation for your ownuse, provided that each such reproduction shall carry the IBM Corporation copyright notice. No other rights undercopyright are granted without prior written permission of IBM Corporation. The document is not intended forproduction and is furnished “as is” without warranty of any kind. All warranties on this document are herebydisclaimed, including the warranties of merchantability and fitness for a particular purpose.

U.S. Government Users Restricted Rights—Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corporation.

Trademarks

IBM, the IBM logo, Tivoli, the Tivoli logo, Tivoli Enterprise Console, and Tivoli Manager for Domino are trademarksor registered trademarks of International Business Machines Corporation or Tivoli Systems Inc. in the United States,other countries, or both.

Lotus and Lotus Notes are registered trademarks of Lotus Development Corporation. Domino is a trademark of LotusDevelopment Corporation.

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, orboth.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product, and service names may be trademarks or service marks of others.Notices

References in this publication to Tivoli Systems or IBM products, programs, or services do not imply that they will beavailable in all countries in which Tivoli Systems or IBM operates. Any reference to these products, programs, orservices is not intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subjectto valid intellectual property or other legally protectable right of Tivoli Systems or IBM, any functionally equivalentproduct, program, or service can be used instead of the referenced product, program, or service. The evaluation andverification of operation in conjunction with other products, except those expressly designated by Tivoli Systems orIBM, are the responsibility of the user. Tivoli Systems or IBM may have patents or pending patent applicationscovering subject matter in this document. The furnishing of this document does not give you any license to thesepatents. You can send license inquiries, in writing, to the IBM Director of Licensing, IBM Corporation, North CastleDrive, Armonk, New York 10504-1785, U.S.A.

Contents

Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiWho Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

What This Guide Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Using the Guide Online. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Viewing Online Help. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Accessing Publications Online . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Ordering Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Providing Feedback about Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Running Tivoli Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Running Tivoli Commands on UNIX. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Running Tivoli Commands on Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Where to Find Additional Information about Shells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Establishing the Tivoli Environment within a Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Establishing the Tivoli Environment on an Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Tivoli Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Common Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Entering Database Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Database Names and Domino Performance Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Return Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 2. Real-Time Monitors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Comm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Database.RM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Disk.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Domino. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

iiiTivoli Manager for Domino Reference Guide

Generic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

MemoryAssessment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

MTA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

NET.<PortName> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

NETBIOS.<PortName> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

nntp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

NNTP.<RemoteServerName>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

POP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

QOS.Mail.ISpy.<servername>.ResponseTime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Real Time Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Server.Health.Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

SMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

SMTPMTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

SMTP.<Name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

SPIN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

SwapDisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Web Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

XPC.<PortName> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Chapter 3. Statistics Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

Agent’s last return code. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Cluster Availability Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

Comm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Database Frequency. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Database.RM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Database.Statistics.Async. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Database.Statistics.Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Data Rollup Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

iv Version 3.1.0

Db.Corruption.Async . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Db.Corruption.Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Db.Template.Async . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Db.Template.Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Disk.SYS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Domino. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Endpoint Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Generic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

ICM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

IMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

LDAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

LogQuery (Log.nsf) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

LogQuery (Field Name). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

LogQuery (Form Name) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119

LogQuery (Found string) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

LogQuery (Note ID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121

Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

MailByDest.<DestServerName>. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

Mailn.box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Mail Trace. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Mail.Waiting.Async . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

Mail.Waiting.Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

MemoryAssessment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

MTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

NET.<PortName> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

NETBIOS.<PortName> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

nntp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

NNTP.<RemoteServerName> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

Object . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

POP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

QOS.Mail.ISpy.<servername>.ResponseTime . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Replication check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

vTivoli Manager for Domino Reference Guide

Replication (Database Replication Info) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157

Replication (Duration) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

Replication (End Time) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

Replication (Hit/Miss/Manual) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Replication (ID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

Replication (Remote server name) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Replication (Replication Events) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Replication (Server Name). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Replication (server name that initiated replication) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Replication (Start Time). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Server Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Server.Health.Async. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Server.Health.Sync. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173

SMTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175

SMTPMTA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

SMTP.<Name> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

SPIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

Stalled.Mail.Async. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Stalled.Mail.Sync. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

SwapDisk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Tdp Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Transaction Log File Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

Transaction Logging Archival Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

UserMail.Statistics.Async. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

UserMail.Statistics.Sync. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192

Web Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194

XPC.<PortName> . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197

Chapter 4. Domino Performance Station Monitors . . . . . . . . . . . . . . . . . . . . . . 199DPSCalendarEntry. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

DPSDatabaseAccess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

DPSIntegrity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204

DPSMail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

DPSNABSearch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

DPSNetEcho . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

vi Version 3.1.0

DPSReplicateLocal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

DPSWebAccess . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Chapter 5. Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215Activate Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

Archive Transactional Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

Check Database Corruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

Check Health. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

Check Inactive Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

Check Replication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226

Clean Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

Configure Notes Client Install 3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229

Configure Notes Client Upgrade 3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

Configure TEC for TMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Delete Server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Get ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

Inactivate Transaction Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

Incremental Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

Mail Waiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Modify Database ACLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Purge Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

Query Activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Query Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Query Database Activity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Query Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Query NAB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

Query Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

Query Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Query Transaction Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Reboot Station. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Recycle NT Server Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Recycle Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 265

Remote Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 266

Restore Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

Selective Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 269

Start Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 270

viiTivoli Manager for Domino Reference Guide

Start Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Start Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

Start Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

Start Station Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

Stop Engine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 275

Stop Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 276

Stop Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Stop Station. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 278

Stop Station Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 279

Verify Mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

Chapter 6. Domino Performance Station Commands . . . . . . . . . . . . . . . . . . . 281wdpsaddserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

wdpscreate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

wdpsdelete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

wdpsintegrity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

wdpsprobeonce . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

wdpsprobestatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

wdpsqueryservers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

wdpsreboot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

wdpsremoveserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

wdpsstart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

wdpsstartengine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

wdpsstartmonitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 295

wdpsstop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 296

wdpsstopengine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 297

wdpsstopmonitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

Chapter 7. Domino Server Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 299wtmdaclmod . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 302

wtmdactivatedbs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

wtmdarchivetranslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

wtmdcheckhealth . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 307

wtmdcheckrep . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 308

wtmdchkdbcorruption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 310

wtmdchkinactusers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311

wtmdcleandb . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 312

viii Version 3.1.0

wtmdcreateserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

wtmddbactivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 317

wtmddeletemail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 319

wtmddeleteserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 320

wtmdgetacl . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 321

wtmdinactivatetranslog. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 323

wtmdincrementalbackup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 324

wtmdlocateserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 325

wtmdmailwaiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 326

wtmdpurgemail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 327

wtmdqueryactivate. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 328

wtmdquerybackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 329

wtmdquerydoc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 330

wtmdquerylog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

wtmdquerynab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

wtmdqueryrestore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

wtmdquerystat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 335

wtmdquerytranslog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 336

wtmdrecyclentsvrsvc . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 337

wtmdrecycleserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 338

wtmdremoteconsole . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 339

wtmdrestoredbs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 340

wtmdselectivebackup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 342

wtmdstartengine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 343

wtmdstartmonitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344

wtmdstartserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

wtmdstopengine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

wtmdstopmonitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

wtmdstopserver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

wtmdverifymail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

Appendix A. Operator Groups. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351Numeric Operator Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

String Operator Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

Status Operator Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 355

ixTivoli Manager for Domino Reference Guide

x Version 3.1.0

Preface

The Tivoli Manager for Domino Reference Guide provides a summary of Tivoli Manager forDomino tasks, monitors, and commands.

Who Should Read This GuideThe target audience for this guide is system managers who use Lotus Domino to managenetworked databases. Users of the guide should have some knowledge of the UNIX orWindows NT operating system and Lotus Domino administration.

Related Documents¶ Tivoli Manager for Domino User’s Guide

¶ Tivoli Framework User’s Guide

¶ Tivoli Framework Planning and Installation Guide

¶ Tivoli Framework Reference Manual

¶ Tivoli Software Distribution User’s Guide

¶ Tivoli Software Distribution Reference Manual

¶ Tivoli Distributed Monitoring User’s Guide

¶ Tivoli Enterprise Console User’s Guide (Volumes I and II)

What This Guide ContainsThis guide contains the following sections:

¶ Chapter 1, “Introduction”

Describes how to run Tivoli commands

¶ Chapter 2, “Real-Time Monitors”

Describes the Tivoli Manager for Domino real-time monitoring collection

¶ Chapter 3, “Statistics Monitors”

Describes the Tivoli Manager for Domino statistics monitoring collection

¶ Chapter 4, “Domino Performance Station Monitors”

Describes the Domino Performance Station monitoring collection

¶ Chapter 5, “Tasks”

Describes Tivoli Manager for Domino tasks

¶ Chapter 6, “Domino Performance Station Commands”

Describes Domino Performance Station commands

¶ Chapter 7, “Domino Server Commands”

Describes Domino server commands

¶ Appendix A, “Operator Groups”

Defines the conditions that must occur for a monitor to send an alert

xiTivoli Manager for Domino Reference Guide

Conventions Used in This GuideThe guide uses several typeface conventions for special terms and actions. Theseconventions have the following meaning:

Bold Commands, keywords, file names, authorization roles, URLs, or otherinformation that you must use literally appear like this, in bold. Names ofwindows, dialogs, and other controls also appear like this, in bold.

Italics Variables and values that you must provide appear like this, in italics. Wordsand phrases that are emphasized also appear like this, in italics.

Monospace Code examples, output, and system messages appear like this, in amonospace font.

Using the Guide OnlineThis document is available in the following formats for viewing online:

¶ An Adobe Acrobat (.pdf) file in the doc directory of the installation CD for the product.Use the Adobe Acrobat Reader, Version 3.0 or later, to view and print the manual. Youcan use the ar405eng.exe executable in the extras directory of the Tivoli Manager forDomino installation CD to install Version 4.0 of the reader.

¶ A set of .html files in the doc directory of the installation CD for the product. You canuse any Web browser to view and print these files.

Viewing Online HelpOnline help is available in several forms:

¶ Desktop — Access online help by clicking the Help buttons in dialog boxes.

¶ Commands — You can display command syntax and parameter information forcommand line interface (CLI) commands by typing the name of the command at acommand prompt and pressing the Enter key.

¶ Management Console — Access help by pressing the F1 key in the managementconsole.

Accessing Publications OnlineThe Tivoli Customer Support Web site (http://www.tivoli.com/support/) offers a guide tosupport services (the Customer Support Handbook); frequently asked questions (FAQs); andtechnical information, including release notes, user’s guides, redbooks, and white papers.You can access Tivoli publications online at http://www.tivoli.com/support/documents/.The documentation for some products is available in PDF and HTML formats. Translateddocuments are also available for some products.

To access most of the documentation, you need an ID and a password. To obtain an ID foruse on the support Web site, go to http://www.tivoli.com/support/getting/.

Resellers should refer to http://www.tivoli.com/support/smb/index.html for moreinformation about obtaining Tivoli technical documentation and support.

Business Partners should refer to “Ordering Publications” on page xiii for more informationabout obtaining Tivoli technical documentation.

xii Version 3.1.0

Note: For NetView OS/390 customers, additional support is also available on theNETVIEW CFORUM (Customer Forum) through the IBMLink system. This forum ismonitored by NetView developers who answer questions and provide guidance. Whena problem with the code is found, you are asked to open an official problemmanagement record (PMR) to get resolution.

Ordering PublicationsOrder Tivoli publications online athttp://www.tivoli.com/support/Prodman/html/pub_order.html or by calling one of thefollowing telephone numbers:

¶ U.S. customers: (800) 879-2755

¶ Canadian customers: (800) 426-4968

Providing Feedback about PublicationsWe are very interested in hearing about your experience with Tivoli products anddocumentation, and we welcome your suggestions for improvements. If you have commentsor suggestions about our products and documentation, contact us in one of the followingways:

¶ Send e-mail to [email protected].

¶ Fill out our customer feedback survey at http://www.tivoli.com/support/survey/.

Contacting Customer SupportThe Tivoli Customer Support Handbook at http://www.tivoli.com/support/handbook/provides information about all aspects of Tivoli Customer Support, including the following:

¶ Registration and eligibility.

¶ How to contact support, depending on the severity of your problem.

¶ Telephone numbers and e-mail addresses, depending on the country you are in.

¶ What information you should gather before contacting support.

xiiiTivoli Manager for Domino Reference Guide

xiv Version 3.1.0

Introduction

This book is a reference manual designed for use with the procedures described in the TivoliManager for Domino User’s Guide. It provides alphabetical listings and detailed descriptionsof the following:

¶ Real-time monitors — These monitors are scheduled, asynchronous monitors for datathat you can monitor at intervals of less than an hour. You can use a singleasynchronous monitor to return multiple values; for example, when you want to checkall databases on a server at specific intervals.

¶ Statistics monitors — These monitors monitor data hourly, daily, or weekly. Thesynchronous monitors in this collection enable Tivoli Distributed Monitoring to start adata collection process on an endpoint. The asynchronous monitors in each collectionprovide for single monitors that return multiple values, such as a single monitor thatchecks on all databases on a server.

¶ Domino Performance Station monitors — These monitors are distributed to DominoPerformance Stations. They measure end-user response times so you can track servicelevel objectives for Lotus Notes users.

¶ Tivoli Manager for Domino tasks

¶ Domino Performance Station commands

¶ Server commands

Running Tivoli CommandsTivoli commands enable you to perform system operations from a UNIX or Windows NTcommand line interface (CLI) instead of using the Tivoli desktop. These commands arereferred to as Tivoli CLI commands.

It is often convenient or more appropriate to invoke a Tivoli management applicationoperation from the command line than from the graphical user interface. For example:

¶ You may not have access to a graphical user interface, perhaps because you have dialedin over a modem.

¶ A number of operations are going to be grouped together inside a shell script.

All Tivoli CLI commands begin with the letter w to identify them as Tivoli commands.Command names use a w+verb+object syntax, which matches the way you would think ofthe action. For example, to create a monitor, use the waddmon command. To delete amonitor, use the wdelmon command.

1

1Tivoli Manager for Domino Reference Guide

1.In

trod

uctio

n

Most Tivoli commands are run within a shell on a managed node or on a TMR server. Ashell is a command interpreter that enables the operating system to process commands. Youcan run commands from a shell command line or include them in shell scripts, on eitherUNIX or Windows NT operating systems.

Before running Tivoli commands, you must set the Tivoli environment variables for theshell. The managed node or TMR server installation process supplies the scripts to set theTivoli environment variables. The procedures to run these scripts are described in “Settingthe Tivoli Environment on UNIX” on page 3 and “Setting the Tivoli Environment onWindows NT” on page 3.

You must also have the appropriate Tivoli authorization role for running each command. TheTivoli authorization role required for running a command is specified in the referenceinformation for the command.

Note: A few Tivoli commands can run on an endpoint. To set the Tivoli environmentvariables on an endpoint, see “Establishing the Tivoli Environment on an Endpoint”on page 4.

Running Tivoli Commands on UNIXShells are provided with UNIX operating systems. Tivoli commands can run in the Bourne,Korn, C, and bash shells. The Bourne shell is considered the standard UNIX shell and isincluded with every UNIX system. The Korn shell supports the features of the Bourne shelland has extensions applicable only to the Korn shell. The C shell is named as such becauseof its closeness to C programming language syntax. The bash shell supports many featuresof the UNIX shells and can be used on both UNIX and Windows NT systems.

Running Tivoli Commands on Windows NTWhen you install a Windows NT managed node or Windows NT TMR server, theinstallation process copies the bash shell executable file to the machine. The bash shellsupports many UNIX commands and UNIX command syntax; for example, the forwardslash (/) for the directory separator. The bash shell supports the features of the Bourne shellplus it has some extensions applicable only to the bash shell.

Note: You can use the Windows NT MS-DOS shell instead of the bash shell to run mostTivoli commands (after you set the Tivoli environment variables with the%SystemRoot%\system32\drivers\etc\Tivoli\setup_env command). However, somecommands and Tivoli tasks may require a bash shell to run successfully. All examplesof Tivoli commands in Tivoli publications are shown using bash shell syntax.

Where to Find Additional Information about ShellsThe following lists include resources where you can find additional information about thevarious shells. These resources were available at the time the lists were created. The lists donot show all of the material that is available, and Tivoli does not provide opinions orrecommendations about any of these resources.

UNIX shells:

¶ UNIX in a Nutshell: A Desktop Quick Reference for System V Release 4 and Solaris 7(O’Reilly Nutshell handbook) by Arnold Robbins. ISBN: 1-56592-427-4.

¶ Portable Shell Programming: An Extensive Collection of Bourne Shell Examples byBruce Blinn. ISBN: 0-13-451494-7.

2 Version 3.1.0

¶ Learning the Korn Shell (O’Reilly Nutshell handbook) by Bill Rosenblatt and MikeLoukides. ISBN: 1-56592-054-6.

¶ UNIX C Shell Desk Reference by Martin Arick. ISBN: 0-47-155680-7.

Bash shell:

¶ Learning the bash Shell (O’Reilly Nutshell handbook) by Cameron Newham and BillRosenblatt. ISBN: 1-56592-347-2.

¶ A Brief Introduction to the bash Shell by Jane Anna Langley.http://www.cs.ups.edu/acl/unix_talk/bash.html

¶ Bash FAQ (GNU documentation). http://www.delorie.com/gnu/docs/bash/FAQ

¶ Bash Reference Manual (GNU documentation).http://www.gnu.org/manual/bash/index.html

¶ bash command reference information (GNU documentation).http://www.delorie.com/gnu/docs/bash/bash.1.html

Establishing the Tivoli Environment within a ShellWhen you install a managed node or TMR server, the installation process supplies shellsetup scripts. You use these scripts to set the environment variables needed for runningTivoli commands.

Setting the Tivoli Environment on UNIXThe following steps describe how to set the Tivoli environment within a UNIX shell:

1. Log in to a UNIX managed node or TMR server.

2. Run the appropriate setup script for the shell.

For the Bourne, Korn, or bash shell, run the following command:. /etc/Tivoli/setup_env.sh

For the C shell, run the following command:source /etc/Tivoli/setup_env.csh

Setting the Tivoli Environment on Windows NTThe following steps describe how to set the Tivoli environment and start a bash shell onWindows NT.

1. Log in to a Windows NT managed node or TMR server.

2. Open a command window.

3. Run the following command in the command window to set Tivoli environmentvariables:%SystemRoot%\system32\drivers\etc\Tivoli\setup_env.cmd

4. Run either of the following commands in the command window to start the bash shell:sh

—OR—bash


1.In

trod

uctio

n

Establishing the Tivoli Environment on an EndpointWhen you install an endpoint, the installation process supplies setup scripts. You use thesescripts to set the environment variables needed for running Tivoli commands on an endpoint.

The following steps describe how to set the Tivoli environment on an endpoint:

1. Log in to an endpoint.

2. Open a command window.

3. Run the appropriate setup script in the command window. Setup scripts for the differentendpoint operating systems are shown in the following table.

OperatingSystem Setup Script Location Setup Script Name

AIX, Solaris /etc/Tivoli/lcf/endpoint_label lcf_env.sh (for Bourne, Korn, and bashshells)

—OR—

lcf_env.csh (for C shell)

Windows NT %SystemRoot%\Tivoli\lcf\endpoint_label

lcf_env.cmd (for MS-DOS) orlcf_env.sh (for bash shell)

Tivoli Command SyntaxThe following special characters define Tivoli command syntax:

[ ] Identifies elements that are optional. Those not enclosed in brackets are required.

... Indicates that you can specify multiple values for the previous element. Separatemultiple values by a space, unless otherwise directed by command information.

If the ellipsis for an element follows a closing bracket, use the syntax within thebrackets to specify multiple values. For example, to specify two administrators forthe option [–a admin]..., use –a admin1 –a admin2.

If the ellipsis for an element is within the brackets, use the syntax of the lastelement to specify multiple values. For example, to specify two hosts for the option[–h host...], use –h host1 host2.

| Indicates mutually exclusive information. You can use the element on either the leftor right of the vertical bar.

{ } Delimits a set of mutually exclusive elements when one of them is required. If theelements are optional, they are enclosed in brackets ([ ]).

In addition to the special characters, the typeface conventions described in the Preface ofthis document are used.

Following are two examples:

¶ wcrtpr [–a admin]... [–s region] [–m resource]... name

The name argument is the only required element for the wcrtpr command. The bracketsaround the options indicate they are optional. The ellipsis after the –a admin and –mresource options indicate you can use those options multiple times to specify multipleadministrators and resources, respectively.

4 Version 3.1.0

¶ wchkdb [–o outfile] [–u] [–x] {–f infile | –i | object...}

The –f, –i, and object elements are mutually exclusive. The braces surrounding themindicate that one of these elements is required. If you specify the object argument, youcan specify more than one object.

Common ParametersThis section describes the names used to refer to Domino servers, Domino PerformanceStations, Tivoli endpoints, and hosts.

Domino Server NameThe Domino server name is assigned to the Domino server when the server isinstalled using standard Domino procedures. This name is usually a string comprisedof a server and domain, such as Domino1/Org. The variable for this name isServerName

Domino Performance Station NameThe Domino Performance Station name is assigned to the station when it is createdwithin Tivoli Manager for Domino. This name is used exclusively by DominoPerformance Station commands. This label is usually a string, such as Station1. Thevariable for this label is DPSName.

Endpoint NameThe endpoint label is assigned when the endpoint is created within the Tivolienvironment. This label is used by some Tivoli Manager for Domino commands, butit cannot be assigned or modified by a Tivoli Manager for Domino command. Thislabel is usually a string, such as Endpoint1. The variable for this label isEndpointName.

Host NameThe host name is the name assigned to the server within the network. This name isused by some Tivoli Manager for Domino commands, but it cannot be assigned ormodified by a Tivoli Manager for Domino command. The format of this name isdetermined by the network. The name might be a string, such asacme.sp.dynamite.com, or an IP address, such as 123.123.123.1. The variable forthis label is HostName. The host name can be determined by typing hostname at thecommand line.

Entering Database NamesThree types of databases are used in Tivoli Manager for Domino:

¶ Domino databases (files that end in .nsf)

¶ Domino database templates (files that end in .ntf)

You can enter a list of database names, separated either by semicolons or by commas,depending on the command. Each item in the list can be one of the following:

¶ A fully qualified path and name from the system root

¶ A fully qualified path and name from the Domino data directory

¶ A fully qualified path and partial name from the system root

¶ A fully qualified path and partial name from the Domino data directory


1.In

trod

uctio

n

You can include both database files (.nsf) and database template files (.ntf).

ConventionsThe following conventions apply:

¶ Place an –s at the end of the name to search subdirectories. You can use this option onlywhen you request a partial name.

¶ You can use either backward slashes (\) or forward slashes (/) in the path.

¶ In UNIX, if the first character is /, the path is assumed to be a fully qualified path fromthe root directory. (A fully qualified path from the root directory is supported only forDomino version 5.0.)

¶ In NT systems, if the first characters are x:/ (where x: is a drive letter), the path isassumed to be fully qualified.

¶ A partial name can be *.nsf, *.ntf, or *.* for both .nsf and .ntf files. The wildcardcharacter * cannot be used in the database name. For example, lo*.nsf cannot besubstituted for log.nsf.

ExamplesIf you are running Domino version 5.0 and the Domino data directory is/lotus/domino/partserver1, the following would be allowed:

¶ mail -s or mail/*.* -s or /lotus/domino/partserver1/mail/*.* -s.

Includes all the .nsf and .ntf database files in the mail directory and its subdirectories inthe Domino data directory.

¶ mail/acmemail.nsf or /lotus/domino/partserver1/mail/acmemail.nsf

Includes the acemail.nsf file in the given directory.

¶ *.* or /lotus/domino/partserver1/*.*

Includes all of the .nsf and .ntf files in the Domino data directory.

¶ *.nsf -s or /lotus/domino/partserver1/*.nsf -s

Includes all of the .nsf files in the Domino data directory and its subdirectories.

¶ c:\private_directory\*.ntf -s

Includes all the .ntf files in root directory private_directory and its subdirectories inNT systems.

¶ /private_directory/*.ntf -s

Includes all the .ntf files in root directory private_directory and its subdirectories inUNIX systems.

¶ mail/*.nsf -s; *.ntf; c:\private_directory\private.ntf

Includes all the .nsf files in the directory mail and its subdirectories, all the .ntf files inthe Domino data directory, and the file c:\private_directory\private.ntf.

The following examples would not be allowed because you cannot use the wildcardcharacter in the database name:mail/coyote*.nsf

/lotus/domino/partserver1/mail/coyote*.nsf

The following example might return an error:mail

6 Version 3.1.0

Where mail is assumed to be the file mail.nsf. If there is such a file, it will be returned.Otherwise an error is returned.

Database Names and Domino Performance StationsDatabase names used with Domino Performance Station commands must adhere to thefollowing guidelines:

¶ All database file and directory names are relative to the Lotus Notes data directoryunless otherwise specified.

¶ Only a single database file name can be used. Multiple filenames are not allowed.

¶ No wildcards are allowed.

Return MessagesWhen you run a command, Tivoli Manager for Domino does one of the following:

¶ If the command executed successfully, the Success message is displayed.

¶ If you omitted a value or used the wrong syntax, help text is displayed showing thecorrect format for the command.

¶ If the command does not execute successfully, an error message is returned.

For common errors, one of the following error messages is usually returned.

An out of memory error occurredThe system ran out of memory attempting to perform this action. Contact Tivolisupport. See “Contacting Customer Support” on page xiii for details.

An unexpected exception occurred.An unexpected exception occurred. Ensure the server and addin are running and tryagain. Restart the addin. If the problem persists, contact Tivoli customer support. See“Contacting Customer Support” on page xiii for details.

Cannot allocate memory.A failure occurred while communicating with the Tivoli Manager for Domino addin.Possibly the server was shut down while this command was executing. Ensure theserver and addin are running and try again. Restart the addin. If the problem persists,contact Tivoli customer support. See “Contacting Customer Support” on page xiii fordetails.

Cannot connect to Tivoli addin. Either the Domino server is down or the Tivoli addin isnot running.

A failure occurred while communicating with the Tivoli Manager for Domino addin.Possibly the server was shut down while this command was executing. Ensure thatthe server and addin are running and try again. Restart the addin. If the problempersists, contact Tivoli customer support. See “Contacting Customer Support” onpage xiii for details.

Cannot initialize TCP/IP communication with Tivoli addin. Either the Domino server isdown or the Tivoli addin is not running.



1.In

trod

uctio

n

Cannot read result from Tivoli addin. Either the Domino server is down or the Tivoliaddin is not running.


Cannot write command to Tivoli addin. Either the Domino server is down or the Tivoliaddin is not running.

A failure occurred while communicating with the Tivoli Manager for Domino addin.Possibly the server was shut down while this command was executing. Ensure theserver and addin are running and try again. Restart the addin. If the problem persists,contact Tivoli customer support. See “Contacting Customer Support” on page xiii fordetails.

Endpoint UnavailableThe endpoint where the Domino Performance Station resides is unavailable.

Error, The specified INI file name is invalidThe specified INI file name is not valid. It should contain a path and filename butdoes not. Contact Tivoli support. See “Contacting Customer Support” on page xiiifor details.

Error, Unable to Enumerate NT Services, possible Registry corruptionThe system received an error from NT when attempting to get a list of serviceregistry entries. This indicates an NT failure that will require assistance fromMicrosoft Corporation.

Error, Unable to open NT Service Entry, possible Registry corruptionThe system received an error attempting to access an NT service registry. Thisindicates an NT failure that will require assistance from Microsoft Corporation.

Error, Unable to open NT Service Manager, possible Registry corruptionAn attempt to open the NT service registry failed, indicating a problem with the NTservice registry. This indicates an NT failure that will require assistance fromMicrosoft Corporation.

Error, Unable to query NT Service status, possible Registry corruptionAn NT failure occurred in attempting to query the NT Service configuration. Thiserror indicates an NT failure that will require assistance from Microsoft Corporation.

Not AuthorizedYou do not have authority to execute this command. Check the Administrators TMRresource roles to ensure that the appropriate role is enabled.

There is no NT Registry service entry for the specified Domino Server with thespecified INI file

The system locates NT service registry entries for servers based on their INI filepath, but no INI file is associated with this server object. Check the service registryand install the Lotus Domino service component to ensure that this server is addedto the service registry.

Tivoli addin cannot read from client socket.A failure occurred while communicating with the Tivoli Manager for Domino addin.Possibly the server was shut down while this command was executing. Ensure the

8 Version 3.1.0

server and addin are running and try again. Restart the addin. If the problem persists,contact Tivoli customer support. See “Contacting Customer Support” on page xiii fordetails.

Tivoli addin cannot write to client socket.A failure occurred while communicating with the Tivoli Manager for Domino addin.Possibly the server was shut down while this command was executing. Ensure theserver and addin are running and try again. Restart the addin. If the problem persists,contact Tivoli customer support. See “Contacting Customer Support” on page xiii fordetails.

Tivoli addin return result of size zero.A failure occurred while communicating with the Tivoli Manager for Domino addin.Possibly the server was shut down while this command was executing. Ensure theserver and addin are running and try again. Restart the addin. If the problem persists,contact Tivoli customer support. See “Contacting Customer Support” on page xiii fordetails.

Unknown StationThe Domino Performance Station name you specified is not valid.

You specified an endpoint name that is not known to the systemThe endpoint associated with this server is not recognized by the system. This errorcan occur if the endpoint is removed from the environment but the Domino serverobject is not deleted. To resolve this error, delete the Domino server object.


1.In

trod

uctio

n

10 Version 3.1.0

Real-Time Monitors

This chapter lists the Tivoli Manager for Domino real-time monitors alphabetically. Eachentry provides complete information on the capabilities and settings for the monitor.

The real-time monitoring collection contains scheduled, asynchronous monitors thatefficiently capture statistics on the Domino server at high frequency so you can managecritical system levels. You can run these monitors together on the same schedule and providea snapshot of the system state. These monitors also provide the status of many Dominoprocesses, such as the Agent Manager process, the Cluster Database process, the ClusterReplicator process, and the Replication process. In Domino, you can display these statisticsby running the show stat command.

Domino statistics are separated into groups corresponding to the groups in the Dominoserver. One Tivoli Manager for Domino real-time monitor is provided for each Dominostatistics group. Refer to the Domino documentation for more information about Dominostatistics.

The Tivoli Manager for Domino real-time monitors always run as a group. You cannot set aschedule for an individual real-time monitor. Instead, you set the schedule for all thereal-time monitors in a profile. You can set this schedule using the Real Time Monitoringmonitor. For more information on scheduling, refer to the Tivoli Manager for Domino User’sGuide.

For help on selecting a monitor, see the Tivoli Manager for Domino User’s Guide. For helpon selecting which statistics to include in the monitor, see the monitor definitions in theremainder of this chapter.

Table 1 summarizes the real-time monitors.

Table 1. Domino V5.0 Real Time Monitor CollectionMonitor CLI Name Description

Agent RTAgent Monitors agent statistics.

Calendar RTCalendar Monitors calendar statistics.

Comm RTComm Monitors network communication statistics.

Database RTDatabase Monitors database statistics.

Database.RM RTDatabaseRM Monitors statistics related to transactionallogging.

Disk RTDisk Monitors disk-related statistics.

Disk.SYS RTDiskSys Monitors statistics related to the NetWareSYS file.

2


2.R

eal-Time

Mo

nito

rs

Table 1. Domino V5.0 Real Time Monitor Collection (continued)Monitor CLI Name Description

Domino RTDomino Monitors statistics reported by the showstat domino command.

Generic RTGeneric Monitors generic statistics.

Mail RTMail Monitors mail statistics.

Memory RTMemory Monitors memory statistics.

MemoryAssessment RTMemoryAssessment Monitors Mail Router statistics.

MTA RTMTA Monitors mail transfer agents statistics.

NET.<PortName> RTNET.<PortName> Monitors Internet-related statistics.

NETBIOS.<PortName> RTNETBIOS Monitors NetBIOS statistics.

nntp RTNNTP Monitors NNTP statistics.

NNTP.<RemoteServerName> RTNNTP.<RemoteServerName>

Monitors NNTP statistics for a remoteserver.

Object RTObject Monitors object statistics.

POP3 RTPOPthree Monitors POP3 statistics.

QOS.Mail.ISpy.<servername>.ResponseTime

RTQOS Monitors mail probe response time.

Real Time Monitoring RealTimeSetup Schedules when a real-time monitoringprofile runs.

Replication RTReplication Monitors statistics reported by the showstat replica command.

Server.Health.Sync RTServer Monitors server health.

Server RTServer.Health.Sync Monitors server statistics.

SMTP RTSMTP Monitors SMTP statistics.

SMTPMTA RTSMTPMTA Monitors the SMTP Mail Transfer Agentstatistics.

SMTP.<Name> RTSMTP.<Name> Monitors specific SMTP statistics.

SPIN RTSPIN Monitors SPIN statistics.

SwapDisk RTSwapDisk Monitors SwapDisk statistics.

Web Monitor RTWeb Monitors Web Retriever statistics.

XPC.<PortName> RTXPC.<PortName> Monitors XPC statistics.

12 Version 3.1.0

Agent

DescriptionMonitors statistics related to the Agent Manager process.

Domino Versions Supported4.6.4 and higher, 5.0.x

Authorization Roleadmin

Target EndpointsDomino Server

Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Agent monitor; a description of each attribute follows.

Click Attributes to display the Agent Monitor Attribute dialog and select the desiredattribute.

Agent.Daily.AccessDenialsReports the number of access denials for agents over a day.

Agent.Daily.ScheduledRunsReports the number of scheduled runs in a day.

Agent.Daily.TriggeredRunsReports the number of triggered agent runs in a day.

Agent.Daily.UnsuccessfulRunsReports the number of unsuccessful agent runs in a day.

Agent.Hourly.AccessDenialsReports the number of agent access denials in an hour.

Agent.Hourly.ScheduledRunsReports the number of scheduled runs in an hour.

Agent.Hourly.TriggeredRunsReports the number of triggered agent runs in an hour.

Agent.Hourly.UnsuccessfulRunsReports the number of unsuccessful agent runs in an hour.

CLI SyntaxRTAgent –a <Attribute>

where:


2.R

eal-Time

Mo

nito

rs

<Attribute> The Agent monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTAgent" -a "Agent.Hourly.UnsuccessfulRuns""MailServerProfile"

14 Version 3.1.0

Calendar

DescriptionMonitors statistics related to the Calendar Manager process.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Calendar monitor; a description of each attribute follows.

Click Attributes to display the Calendar Monitor Attribute dialog and select the desiredattribute.

Calendar.Total.All.Appointments.ReservationsDisplays the total number of appointments and reservations in scheduling.

Calendar.Total.All.Users.ResourcesDisplays the total number of users and resources in scheduling.

Calendar.Total.ApptsDisplays the total number of appointments in scheduling

Calendar.Total.ReservationsDisplays the total number of reservations in scheduling.

Calendar.Total.ResourcesDisplays the total number of resources in scheduling.

Calendar.Total.UsersDisplays the total number of users in scheduling

CLI SyntaxRTCalendar –a <Attribute>

where:

<Attribute> The Calendar monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTCalendar" -a "Calendar.Total.Appts""MailServerProfile"


2.R

eal-Time

Mo

nito

rs

Comm

DescriptionMonitors statistics related to Domino network communications.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Comm monitor; a description of each attribute follows.

Click Attributes to display the Comm Monitor Attribute dialog and select the desiredattribute.

Comm.Appletalk.AppleTalk.StatsLoggedReports the number of Appletalk statistics logged.

Comm.Netware.SPXII.StatsLoggedReports the number of SPXII statistics logged.

Comm.NumOldSessionsClosedReports the number of sessions closed by the Notes server to accommodate newusers.

CLI SyntaxRTComm –a <Attribute>

where:

<Attribute> The Comm monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTComm" -a "Comm.Netware.SPXII.StatsLogged""MailServerProfile"

16 Version 3.1.0

Database

DescriptionMonitors statistics relating to database activity on a Domino server.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Database monitor; a description of each attribute follows.

Click Attributes to display the Database Attribute dialog and select the desired attribute.

Database.BufferControlPool.PeakReports the peak number of database buffer control pools.

Database.BufferControlPool.SizeReports the size of database control pools.

Database.BufferControlPool.UsedReports the number of used database buffer control pools.

Database.BufferPool.AllocatedReports the number of database control pools allocated.

Database.BufferPool.IRISOpenContainersReports the number of IRIS open containers for database buffer pools.

Database.BufferPool.Maximum.MegabytesReports the maximum size of database control pools.

Database.BufferPool.Peak.MegabytesReports the peak number of database buffer pools.

Database.BufferPool.PerCentReadsInBufferReports the percentage of buffer pool reads.

Database.BufferPool.MM.ReadsReports the number of database buffer pool reads.

Database.BufferPool.MM.UsedReports the number of used database buffer pools.


2.R

eal-Time

Mo

nito

rs

Database.BufferPool.MM.WritesReports the number of database buffer pool writes.

Database.DbCache.CurrentEntriesReports the current number of entries in the database cache.

Database.DbCache.HighWaterMarkReports the period of most activity in the database cache.

Database.DbCache.HitsReports the number of hits to the database cache.

Database.DbCache.InitialDbOpensReports the number of times the database cache opened the database.

Database.DbCache.LookupsReports the number of lookups to the database cache.

Database.DbCache.MaxEntriesReports the maximum number of entries in the database cache.

Database.DbCache.OvercrowdingRejectionsReports the number of rejections due to overcrowding in the database cache.

Database.ExtMgrPool.PeakReports the peak number of external manager pools used.

Database.ExtMgrPool.UsedReports the number of external manager pools.

Database.NIFPool.PeakReports the peak number of database network information file (NIF) pools.

Database.NIFPool.UsedReports the number of database NIF pools.

Database.NSF.FreeHandleStack.FreeHandleStackHitsReports the number of database free handle stack hits.

Database.NSF.FreeHandleStack.HandleAllocationsReports the number of database free handle stack allocations.

Database.NSF.FreeHandleStack.MissRateReports the database free handle stack miss rate.

Database.NSFPool.PeakReports the peak number of database NSF pools.

Database.NSFPool.SizeReports the size of database NSF pools.

Database.NSFPool.UsedReports the number of database NSF pools.

CLI SyntaxRTDatabase –a <Attribute>

where:

<Attribute> The Database monitor attribute.

18 Version 3.1.0

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTDatabase" -a "Database.BufferPool.Allocated""MailServerProfile"


2.R

eal-Time

Mo

nito

rs

Database.RM

DescriptionMonitors statistics related to transactional logging.

Domino Versions Supported5.0.x



Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Database.RM monitor; a description of each attribute follows.

Click Attributes to display the Database.RM Attribute dialog and select the desiredattribute.

Database.RM.Current.K.Restart.Redo.HoldReports the number of changes on the log but not yet in the database.

Database.RM.Current.K.UnCommitted.Undo.HoldReports the number of changes held back by long running transactions.

Database.RM.Current.MaxChkptScan.msecReports the number of transactions per minute from the current checkpoint.

Database.RM.LastChkpt.Avg.K.Logged.PerTranReports the average transaction size from the last checkpoint.

Database.RM.LastChkpt.Interval.SecReports the time since the last checkpoint.

Database.RM.LastChkpt.K.LoggedReports the amount of data logged in the checkpoint interval.

Database.RM.LastChkpt.TimeReports the time of the last checkpoint.

Database.RM.LastChkpt.Total.DBsReports the databases open or in DBCache at the time of the last checkpoint.

Database.RM.LastChkpt.TransReports actual transactional logging type transactions (API calls that did databaseupdates).

20 Version 3.1.0

Database.RM.Peak.Avg.K.Logged.PerTranReports the average size of transactions from the peak checkpoint.

Database.RM.Peak.Interval.SecReports the time interval before the peak checkpoint.

Database.RM.Peak.K.LoggedReports the amount of data logged in the interval before the peak checkpoint.

Database.RM.Peak.TimeReports the time of the peak checkpoint.

Database.RM.Peak.Total.DBsReports the databases open or in DBCache at the time of the peak checkpoint.

Database.RM.Peak.TransReports actual transactional logging type transactions from the peak checkpoint (APIcalls that did database updates).

Database.RM.Peak.Trans.PerMinReports the number of transactions per minute from the peak checkpoint.

Database.RM.Restart.Duration.SecReports the time (in seconds) that it took to apply the incomplete changes after acrash.

Database.RM.Restart.K.AppliedReports the amount of incomplete changes detected and applied in KB. For example,22MB in 33sec.

Database.RM.Restart.TimeReports the time that the server was started.

Database.RM.SinceChkpt.K.LoggedReserved for Lotus Corporation internal use.

Database.RM.SinceChkpt.TransReserved for Lotus Corporation internal use.

Database.RM.SinceStartup.AbortsReports the number of failed transactions since the server was started.

Database.RM.SinceStartup.Critical.Log.TimesReports the number of times the system ran critically log full since the server wasstarted.

Database.RM.SinceStartup.Log.Recs.AnalyzedReserved for Lotus Corporation internal use.

Database.RM.SinceStartup.Log.Recs.AppliedReserved for Lotus Corporation internal use.

Database.RM.SinceStartup.Log.Recs.ReadReserved for Lotus Corporation internal use.

Database.RM.SinceStartup.Log.Recs.AppliedReserved for Lotus Corporation internal use.

Database.RM.SinceStartup.Log.Recs.ReadReserved for Lotus Corporation internal use.


2.R

eal-Time

Mo

nito

rs

Database.RM.SinceStartup.Log.Recs.WrittenReserved for Lotus Corporation internal use.

Database.RM.SinceStartup.M.LoggedReports how much log has been written (in MB) since the server was started.

Database.RM.SinceStartup.TransReports actual transactional logging type transactions from the peak checkpoint (APIcalls that did database updates).

Database.RM.Sys.LoggedReports whether Sys.Logged is enabled or disabled. If disabled, no otherDatabase.RM stats are shown.

Database.RM.Sys.Log.TypeReports whether Logging style is circular or archive.

Database.RM.Sys.M.Chkpt.IntervalReserved for Lotus Corporation internal use.

Database.RM.Sys.M.Log.SizeReserved for Lotus Corporation internal use.

Database.RM.Sys.M.Redo.LimitReserved for Lotus Corporation internal use.

Database.RM.Sys.PhaseReports the transactional logging phase.

CLI SyntaxRTDatabaseRM –a <Attribute>

where:

<Attribute> The RMDatabase monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTDatabaseRM" -a "Database.RM.Last.Chkpt.Trans""MailServerProfile"

22 Version 3.1.0

Disk

DescriptionMonitors disk-related statistics.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Disk monitor; a description of each attribute follows.

Click Attributes to display the Disk Drive dialog and select the desired attribute.

Disk Drive Select the drive letter or location of the drive you would like to monitorfrom the following choices: C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q,R, S, T, U, V, W, X, Y, Z, /, Vol0, Vol1, Vol2, Vol3

You can monitor each drive for either free space or size in bytes.

CLI SyntaxRTDisk –a Disk.<Drive>.<Attribute>

where:

<Drive> The drive letter or location of the drive you would like to monitor from thefollowing choices: C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U,V, W, X, Y, Z, /, Vol0, Vol1, Vol2, Vol3

<Attribute> Free space or size in bytes.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTDisk" -a "Disk.C.Free" "MailServerProfile"

waddmon "Domino v5.0 Real Time Collection" "RTDisk" -a "Disk.C.Size" "MailServerProfile"


2.R

eal-Time

Mo

nito

rs

Disk.SYS

DescriptionMonitors statistics related to the NetWare SYS file.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Disk.SYS monitor; a description of each attribute follows.

Click Attributes to display the DiskSys Monitor Attribute dialog and select the desiredattribute.

Disk.SYS.AvailableBlocksReports the number of available disk blocks on a NetWare SYS volume.

Disk.SYS.AvailableDirectorySlotsReports the number of available directory slots on a NetWare SYS volume.

Disk.SYS.DriveNumberReports the physical driver number of a NetWare SYS volume.

Disk.SYS.FreeReports the amount of free space on a NetWare SYS volume.

Disk.SYS.NotYetPurgableBlocksReports the number of blocks that cannot be purged on a NetWare SYS volume.

Disk.SYS.NumberReports the volume number of a NetWare SYS volume.

Disk.SYS.PurgableBlocksReports the number of blocks that can be purged on a NetWare SYS volume.

Disk.SYS.SizeReports the size of a NetWare SYS volume.

Disk.SYS.StartingBlockReports the physical block number where a NetWare SYS volume starts.

Disk.SYS.TotalBlocksReports the number of physical blocks a NetWare SYS volume spans.

24 Version 3.1.0

Disk.SYS.TotalDirectorySlotsReports the number of directory slots a NetWare SYS volume spans.

CLI SyntaxRTDiskSys –a <Attribute>

where:

<Attribute> The Disk.SYS monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTDiskSys" -a "Disk.SYS.Size" "MailServerProfile"


2.R

eal-Time

Mo

nito

rs

Domino

DescriptionMonitors numeric statistics from the Domino server.

Domino Versions Supported4.6.4 or higher, 5.0.x



Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Domino monitor; a description of each attribute follows.

Click Attributes to display the Domino Monitor Attribute dialog and select the desiredattribute.

Domino.Command.CreateDocumentCounts the “CreateDocument” URLs that have come into the server since the serverwas last started.

Domino.Command.DeleteDocumentCounts the “DeleteDocument” URLs that have come into the server since the serverwas last started.

Domino.Command.EditDocumentCounts the “EditDocument” URLs that have come into the server since the serverwas last started.

Domino.Command.LoginCounts the “Login” URLs that have come into the server since the server was laststarted.

Domino.Command.NavigateCounts the “Navigate” URLs that have come into the server since the server was laststarted.

Domino.Command.OpenAboutCounts the “OpenAbout” URLs that have come into the server since the server waslast started.

Domino.Command.OpenAgentCounts the “OpenAgent” URLs that have come into the server since the server waslast started.

26 Version 3.1.0

Domino.Command.OpenDatabaseCounts the “OpenDatabase” URLs that have come into the server since the serverwas last started.

Domino.Command.OpenDocumentCounts the “OpenDocument” URLs that have come into the server since the serverwas last started.

Domino.Command.OpenElementCounts the “OpenElement” URLs that have come into the server since the serverwas last started.

Domino.Command.OpenFormCounts the “OpenForm” URLs that have come into the server since the server waslast started.

Domino.Command.OpenHelpCounts the “OpenHelp” URLs that have come into the server since the server waslast started.

Domino.Command.OpenIconCounts the “OpenIcon” URLs that have come into the server since the server waslast started.

Domino.Command.OpenNavigatorCounts the “OpenNavigator” URLs that have come into the server since the serverwas last started.

Domino.Command.OpenServerCounts the “OpenServer” URLs that have come into the server since the server waslast started.

Domino.Command.OpenViewCounts the “OpenView” URLs that have come into the server since the server waslast started.

Domino.Command.ReadFormCounts the “ReadForm” URLs that have come into the server since the server waslast started.

Domino.Command.SearchSiteCounts the “SearchSite” URLs that have come into the server since the server waslast started.

Domino.Command.SearchViewCounts the “SearchView” URLs that have come into the server since the server waslast started.

Domino.Command.TotalCounts the total number of URLs that have come into the server since the serverwas last started.

Domino.Command.UnknownCounts the total number of unknown URLs that have come into the server since theserver was last started.

Domino.Requests.Per1Hour.TotalReports the number of requests during the past hour.


2.R

eal-Time

Mo

nito

rs

Domino.Requests.Per1Minute.TotalReports the number of requests during the past minute.

Domino.Requests.Per5Minute.TotalReports the number of requests during the last five minutes.

CLI SyntaxRTDomino –a <Attribute>

where:

<Attribute> The Domino monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTDomino" -a "Domino.Command.Total""MailServerProfile"

28 Version 3.1.0

Generic

DescriptionMonitors a process using a generic argument. Use this monitor to gather statistics for whichno monitor currently exists.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Generic monitor; a description of Generic Argument follows.

Generic ArgumentIs the process on which you want to gather statistics.

CLI SyntaxRTGeneric –a <Argument>

where:

<Argument> The generic argument to monitor.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTGeneric" -a "server.foo" "MailServerProfile"


2.R

eal-Time

Mo

nito

rs

Mail

DescriptionMonitors numeric statistics related to mail routing.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Mail monitor; a description of each attribute follows.

Click Attributes to display the Mail Attribute dialog and select the desired attribute.

Mail.AverageServerHopsReports the average number of server hops for mail delivery.

Mail.AverageSizeDeliveredReports the average size of mail delivered.

MAIL.DeadReports the number of dead (undeliverable) messages in MAIL.BOX.

MAIL.DeliveredReports the number of mail messages moved into MAIL.BOX by a router.

Mail.DeliveriesReports the count of actual mail items delivered (may be different fromMAIL.Delivered, which counts individual messages).

Mail.HoldNumber of mail messages in the message queue on hold.

Mail.IMAP.Cache.MsgInsertAttemptsReports the number of times an IMAP server attempted to insert a message into thecache.

Mail.IMAP.FindCacheAttemptedReports the number of times an IMAP server attempted to find a message in thecache.

Mail.IMAP.NumCacheHitsReports the number of messages the IMAP server found in the cache.

30 Version 3.1.0

Mail.IMAP.NumMsgInsertedInCacheNumber of messages the IMAP server inserted into cache.

Mail.MaximumServerHopsReports when the maximum number of server hops for mail delivery is reached.

Mail.MaximumSizeDeliveredReports when the maximum size of mail delivered is reached.

Mail.MinimumServerHopsReports when the minimum number of server hops for mail delivery is reached.

Mail.MinimumSizeDeliveredReports when the minimum size of mail delivered is reached.

Mail.PeakByteTransferRateReports the peak transfer rate.

Mail.PeakMessagesTransferredReports the peak number of messages transferred.

Mail.PeakMessageTransferRateReports the peak message transfer rate.

Mail.PeakTotalBytesTransferredReports the highest number of bytes transferred.

MAIL.TotalFailuresReports the total number of mail failures.

Mail.TotalKBTransferredReports the total of mail transferred in kilobytes.

MAIL.TotalRoutedReports the number of mail messages moved from MAIL.BOX to other servers fordelivery.

Mail.TotalRouted.SMTPReports the number of mail messages moved from MAIL.BOX via SMTP.

Mail.TotalRouted.NRPCReports the number of mail messages moved from MAIL.BOX via NRPC.

MAIL.TransferFailuresReports the number of mail messages the router was unable to transfer.

MAIL.TransferredReports the number of mail messages the router attempted to transfer.

MAIL.WaitingReports the number of outgoing mail messages in MAIL.BOX waiting for transfer.

MAIL.WaitingforDNSNumber of mail messages in MAIL.BOX waiting for DNS.

MAIL.WaitingRecipientsReports the number of mail messages in MAIL.BOX awaiting delivery into a user’smail files.


2.R

eal-Time

Mo

nito

rs

CLI SyntaxRTMail –a <Attribute>

where:

<Attribute> The Mail monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTMail" -a "Mail.AverageSizeDelivered""MailServerProfile"

32 Version 3.1.0

Memory

DescriptionMonitors numeric statistics related to server system memory.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Memory monitor; a description of each attribute follows.

Click Attributes to display the Memory Attribute dialog and select the desired attribute.

Mem.AllocatedReports the total amount of memory allocated by the server.

Mem.Allocated.ProcessReports the total amount of non-shared memory allocated by individual processes.

Mem.Allocated.SharedReports the total amount of server memory allocated as shared memory.

Mem.FreeReports the amount of free memory available to the server.

Mem.FTVDKMaxBufferSizeUsedReports the maximum FTVDK buffer size used.

Note: You can use this attribute on Domino Version 5.0 servers only.

Mem.PhysicalRamReports the total amount of physical memory on the server.

Mem.QuotaReports the maximum memory that can be allocated by the server.

Mem.SwapFile.SizeReports the size (in bytes) of a system swap file.


2.R

eal-Time

Mo

nito

rs

CLI SyntaxRTMemory –a <Attribute>

where:

<Attribute> The Memory monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTMemory" -a "Mem.Allocated" "MailServerProfile"

34 Version 3.1.0

MemoryAssessment

DescriptionMonitors the Domino Server Memory Assessment statistic by checking theNSF_Buffer_Pool_Size setting in the notes.ini file.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Agent monitor; a description of the Memory Attribute follows.

Memory AttributeMem.Availability is the only attribute available at this time.Mem.Availability returns the amount of available memory.

CLI SyntaxRTMemoryAssessment –a <MemoryAttribute>

where:

<MemoryAttribute>Mem.Availability is the only attribute available at this time.Mem.Availability returns the amount of available memory.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTMemoryAssessment" -a "Mem.Availability""MailServerProfile"


2.R

eal-Time

Mo

nito

rs

MTA

DescriptionMonitors statistics related to various Mail Transfer Agents.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the MTA monitor; a description of each attribute follows.

Click Attributes to display the MTA Attribute dialog and select the desired attribute.

MTA.ccMail.DeadReports the total number of ccMail MTA transmission failures that result in an NDRor UMN.

MTA.ccMail.TotalKBTransferredReports the total number of ccMail MTA transfers in kilobytes (inbound andoutbound).

MTA.ccMail.TotalRoutedReports the total number of recipients of ccMail MTA messages routed (inbound andoutbound).

MTA.ccMail.TransferFailuresReports the number of ccMail MTA transmission failures that result in an NDR orUMN.

MTA.ccMail.TransferredReports the number of ccMail MTA transferred (inbound and outbound).

MTA.ccMail.WaitingReports the number of messages waiting in ccMail MTA work queues.

MTA.ccMail.WaitingRecipientsReports the number of responsible recipients for waiting mail held in inbound andoutbound work queues.

36 Version 3.1.0

MTA.Smtp.DeadReports the number of dead messages in the Simple Message Transmission Protocol(SMTP)/Multi-Purpose Internet Mail Extensions (MIME) MTA inbound andoutbound work queues.

MTA.Smtp.TotalKBTransferredReports the total number of SMTP/MIME MTA transfers in kilobytes (inbound andoutbound).

MTA.Smtp.TotalRoutedReports the total number of recipients of SMTP/MIME MTA messages routed(inbound and outbound).

MTA.Smtp.TransferFailuresReports the number of SMTP/MIME MTA transmission failures that resulted in anNDR or UMN.

MTA.Smtp.TransferredReports the number of SMTP/MIME MTA transferred (inbound and outbound).

MTA.Smtp.WaitingReports the number of messages waiting in SMTP/MIME MTA work queues.

MTA.Smtp.WaitingRecipientsReports the number of responsible recipients for waiting mail held in inbound andoutbound work queues.

MTA.X400.DeadReports the number of dead messages in X400 MTA inbound and outbound workqueues.

MTA.X400.TotalKBTransferredReports the total number of X400 MTA transfers in kilobytes (inbound andoutbound).

MTA.X400.TotalRoutedReports the total number of recipients of X400 MTA messages routed (inbound andoutbound).

MTA.X400.TransferFailuresReports the number of X400 MTA transmission failures that resulted in an NDR orUMN.

MTA.X400.TransferredReports the number of X400 MTA transferred (inbound and outbound).

MTA.X400.WaitingReports the number of messages waiting in X400 MTA work queues.

MTA.X400.WaitingRecipientsReports the number of responsible recipients for waiting mail held in inbound andoutbound work queues.

CLI SyntaxRTMTA –a <Attribute>

where:

<Attribute> The MTA monitor attribute.


2.R

eal-Time

Mo

nito

rs

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTMTA" -a "MTA.ccMail.Dead" "MailServerProfile"

38 Version 3.1.0

NET.<PortName>

DescriptionMonitors Internet-related statistics.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the NET.<PortName> monitor; a description of each attribute follows.

Click Attributes to display the Device dialog and select the desired attribute.

BytesReceivedReports the number of network bytes received.

BytesSentReports the number of bytes sent.

Sessions.Established.IncomingReports the number of incoming sessions established.

Sessions.Established.OutgoingReports the number of outgoing sessions established.

Sessions.LimitReports the number of sessions at limit.

Sessions.LimitMaxReports the number of sessions at maximum limit.

Sessions.LimitMinReports the number of sessions at minimum limit.

Sessions.PeakReports the peak number of sessions.

Sessions.RecycledReports the number of sessions that were recycled.

Sessions.RecyclingReports the number of sessions recycling.


2.R

eal-Time

Mo

nito

rs

CLI SyntaxRTNET.<PortName> –a Net.<Device>.<Statistic>

where:

<PortName> The name of the port from which to collect the statistics.

<Device> The device to monitor from the following list: COM1, COM2, COM3,COM4, COM5, LAN0, LAN1, LAN2, SPX, TCPIP, TCP, VINES

<Statistic> The information received from the device. The choices are:


BytesSent Reports the number of bytes sent.






Sessions.Peak Reports the peak number of sessions.



CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTNET.Port1" -a "Net.COM1.BytesSent""MailServerProfile"

40 Version 3.1.0

NETBIOS.<PortName>

DescriptionMonitors NetBIOS statistics for each port that is specified in the port name.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the NETBIOS.<PortName> monitor; a description of each attribute follows.

Click Attributes to display the NETBIOS Monitor Port Attribute dialog and select thedesired attribute.

Note: The statistics described in the following attributes can be collected from the followingports: LAN0, LAN1, LAN2. The port is listed before the attribute on the NETBIOSMonitor Port Attribute dialog.

CommandBlocks.AvailableReports the number of Network Basic Input/Output System (NetBIOS) commandblocks available.

CommandBlocks.TotalReports the total number of NetBIOS command blocks.

Errors.AlignmentReports the number of NetBIOS alignment errors.

Errors.CollisionsReports the number of NetBIOS collisions.

Errors.CRCReports the number of NetBIOS cyclic redundancy check (CRC) errors.

Packets.ReceivedReports the number of NetBIOS packets received.

Packets.TransmittedReports the number of NetBIOS packets transmitted.

Receiver.Resources.ExhaustedReports the number of exhausted NetBIOS resources.


2.R

eal-Time

Mo

nito

rs

ReportPeriodMinutesReports the number of minutes since the last update.

Sessions.InUseReports the number of NetBIOS sessions in use.

Sessions.MaximumReports the maximum number of NetBIOS sessions.

Session.DataPacketSizeReports the size of a NetBIOS data packet.

Transmissions.AbortedReports the number of NetBIOS transmissions aborted.

Transmissions.RetriedReports the number of NetBIOS transmissions retried.

CLI SyntaxRTNETBIOS –a NETBIOS.<Port>.<Statistic>

where:

<Port> The name of the port from which to collect the statistics from the followingoptions: LAN0, LAN1, LAN2.

<Statistic> The type of information you want to receive from the device from thefollowing choices:

CommandBlocks.AvailableReports the number of Network Basic Input/Output System(NetBIOS) command blocks available.




Errors.CRCReports the number of NetBIOS cyclic redundancy check (CRC)errors.



Rec.Res.ExhaustedReports the number of exhausted NetBIOS resources.



42 Version 3.1.0





CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTNETBIOS" -a "NETBIOS.LAN1.Transmissions.Retried""MailServerProfile"


2.R

eal-Time

Mo

nito

rs

nntp

DescriptionMonitors statistics related to a Network News Transport Protocol (NNTP) server (Dominonews server).




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the nntp monitor; a description of each attribute follows.

Click Attributes to display the NNTP Monitor Attribute dialog and select the desiredattribute.

NNTP.Articles.PostedReports the number of news articles posted to the NNTP server.

NNTP.Articles.SentReports the number of news articles sent from the NNTP server.

NNTP.Bytes.ReceivedReports the number of bytes received by the NNTP server.

NNTP.Bytes.SentReports the number of bytes sent from the NNTP server.

NNTP.Pull.Articles.FailedReports the number of failed news article transfers received by the NNTP serverduring pull feeds.

NNTP.Pull.Articles.OfferedReports the number of news articles offered by the NNTP server during pull feeds.

NNTP.Pull.Articles.RequestedReports the number of news articles requested from the NNTP server during pullfeeds.

NNTP.Pull.Articles.TransferredReports the number of news articles transferred by the NNTP server during pullfeeds.

44 Version 3.1.0

NNTP.Push.Articles.FailedReports the number of failed news article transfers by the NNTP server during pushfeeds.

NNTP.Push.Articles.OfferedReports the number of failed news articles offered by the NNTP server during pushfeeds.

NNTP.Push.Articles.RequestedReports the number of news articles requested from the NNTP server during pushfeeds.

NNTP.Push.Articles.TransferredReports the number of news articles transferred by the NNTP server during pushfeeds.

NNTP.Sessions.Accept.QueueReports the number of incoming sessions to be processed in the NNTP listener workqueue.

NNTP.Sessions.ActiveReports the current number of NNTP server tasks.

NNTP.Sessions.Inbound.BytesReceivedReports the total number of bytes received by a NNTP server.

NNTP.Sessions.Inbound.BytesSentReports the total number of bytes sent by a NNTP server.

NNTP.Sessions.Inbound.Non-SSLReports the number of NNTP server inbound non-Secure Socket Layer (SSL)connections.

NNTP.Sessions.Inbound.SSLReports the number of NNTP server inbound SSL connections.

NNTP.Sessions.Inbound.SSL.Bad_HandshakeReports the number of NNTP server SSL handshake failures.

NNTP.Sessions.Inbound.TotalReports the total number of NNTP server inbound connections (SSL and non-SSL).

NNTP.Sessions.Outgoing.non-SSLReports the number of outgoing non-SSL TCP connections.

NNTP.Sessions.Outgoing.SSLReports the number of outgoing SSL TCP connections.

NNTP.Sessions.PeakReports the peak number of NNTP server tasks since server startup.

NNTP.Sessions.Threads.BusyReports the number of NNTP server tasks that are currently running.

NNTP.Sessions.Threads.IdleReports the number of NNTP server tasks that are currently idle.

NNTP.Sessions.TotalReports the total number of NNTP server tasks since server startup.


2.R

eal-Time

Mo

nito

rs

CLI SyntaxRTNNTP –a <Attribute>

where:

<Attribute> The NNTP monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTNNTP" -a "NNTP.Sessions.Peak" "MailServerProfile"

46 Version 3.1.0

NNTP.<RemoteServerName>

DescriptionMonitors statistics related to a remote NNTP server.

Domino Versions Supported4.6, 5.0.x



Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the NNTP.<RemoteServerName> monitor; a description of the Remote Server Nameattribute follows.

Remote Server NameThe name of the server you want to monitor.

CLI SyntaxRTNNTP.<RemoteServerName>

where:

RemoteServerNameThe name of the server you want to monitor.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTNNTP.jerry" "MailServerProfile"


2.R

eal-Time

Mo

nito

rs

Object

DescriptionMonitors statistics related to the shared mail store.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Object monitor; a description of each attribute follows.

Click Attributes to display the Object Monitor Attribute dialog and select the desiredattribute.

Object Monitor AttributeReports the number of objects shared by xx users (where xx represents the number ofusers). You may choose a specific number from 1–20 or choose the optionObject.Mailobj.NSF.SharedBy.Greater that specifies a number of users greaterthan 20.

CLI SyntaxRTObject –a <Attribute>

where:

<Attribute> The object monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTObject" -a "Object.Mailobj.NSF.SharedBy.18""MailServerProfile"

48 Version 3.1.0

POP3

DescriptionMonitors statistics related to Post Office Protocol 3 (POP3).




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the POP3 monitor; a description of each attribute follows.

Click Attributes to display the POP3 Attribute dialog and select the desired attribute.

POP3.Sessions.Accept.QueueReports the number of incoming sessions to be processed in the POP3 listener workqueue.

POP3.Sessions.ActiveReports the current number of POP3 server tasks.

POP3.Sessions.Inbound.BytesReceivedReports the total number of bytes received by a POP3 server.

POP3.Sessions.Inbound.BytesSentReports the total number of bytes sent by a POP3 server.

POP3.Sessions.Inbound.Non-SSLReports the number of inbound POP3 server Transmission Control Protocol (TCP)connections.

POP3.Sessions.Inbound.SSLReports the number of inbound POP3 server SSL connections.

POP3.Sessions.Inbound.SSL.Bad_HandshakeReports the number of POP3 server SSL handshake failures.

POP3.Sessions.Inbound.TotalReports the number of inbound POP3 server connections (SSL and non-SSL).

POP3.Sessions.PeakReports the peak number of POP3 server tasks since server startup.


2.R

eal-Time

Mo

nito

rs

POP3.Sessions.Threads.BusyReports the number of POP3 server tasks currently running.

POP3.Sessions.Threads.IdleReports the number of POP3 tasks currently idle.

POP3.Sessions.TotalReports the total number of POP3 server tasks since server startup.

CLI SyntaxRTPOPthree –a <Attribute>

where:

<Attribute> The POP3 monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTPOPthree" -a "POPThree.Sessions.Peak""MailServerProfile"

50 Version 3.1.0


DescriptionMonitors mail probe response time.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor this monitor; a description of each attribute follows.

ServerName AttributeThe name of the server.

CLI SyntaxRTQOS –a <attribute>

where

<attribute>The QOS attribute QOS.Mail.ISpy.<servername>.ResponseTime.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTQOS" -a "QOS.Mail.ISpy.brisbane.ResponseTime"


2.R

eal-Time

Mo

nito

rs

Real Time Monitoring

DescriptionTo schedule when a real-time monitoring profile runs.

This monitor is required for using the real-time monitors with Tivoli Manager for Domino.This monitor specifies the schedule at which all real-time monitors are run. Only oneinstance of this monitor can be distributed to a Domino server. Attempting to distribute asecond instance of this monitor will cause an error to occur.

The Tivoli Manager for Domino real-time monitors always run as a group. You cannot set aschedule for an individual real-time monitor. Instead, you set the schedule for all thereal-time monitors in a profile. In a sense, this monitor is a scheduler for groups of real-timemonitors.

By default, this monitor sets a real-time monitoring profile to run every five minutes onweekdays (Monday through Friday), during two separate sessions: daylight hours and in theevening hours.

Note: It is desirable to make the combined length of the daytime and nighttime intervalsless than 24 hours, total. That way, real-time monitoring ceases when server activityis low or while you recycle servers and perform other maintenance operations.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Real Time Monitoring monitor; a description of each attribute follows.

Interval The interval (in minutes) at which all real-time monitors should run.

Weekdays The days of the week to run real-time monitors, where 1=Sunday,2=Monday, ..., 7=Saturday.

StartDay The time of the day at which to start running real-time monitors.

52 Version 3.1.0

EndDay The time of the day at which to stop running real-time monitors.

Note: You can have two different times during the day to run real-time monitors; however,if you only require one scheduled time then leave the Start Night and End Nightattributes blank.

StartNight The time of the evening at which to start running real-time monitors.

EndNight The time of the evening at which to stop running real-time monitors.

CLI SyntaxRealTimeSetup –a <Interval> –a <Weekdays> –a <StartDay> –a <EndDay>–a <StartNight> –a <EndNight>

where:

<Interval> The interval (in minutes) at which all real-time monitors should run.

<Weekdays> The days of the week to run real-time monitors, where 1=Sunday,2=Monday, ..., 7=Saturday.

<StartDay> The time of the day at which to start running real-time monitors.

<EndDay> The time of the day at which to stop running real-time monitors.

Note: You can have two different times during the day to run real-time monitors, however ifyou only require one scheduled time then leave the Start Night and End Nightattributes blank.

<StartNight> The time of the evening at which to start running real-time monitors.

<EndNight> The time of the evening at which to stop running real-time monitors.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RealTimeSetup" -a "5" -a "23456"-a "9AM" -a "5PM" -a "6PM" -a "11PM" "MailServerProfile"


2.R

eal-Time

Mo

nito

rs

Replication

DescriptionMonitors numeric statistics related to database replication.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Replication monitor; a description of each attribute follows.

Click Attributes to display the Replication Attribute dialog and select the desired attribute.

Replica.Cluster.CacheHandlesReports the number of handles cached by a cluster.

Replica.Cluster.Docs.AddedReports the number of documents added by a cluster replicator.

Replica.Cluster.Docs.DeletedReports the number of documents deleted by a cluster replicator.

Replica.Cluster.Docs.UpdatedReports the number of documents updated by a cluster replicator.

Replica.Cluster.FailedReports the number of failed replications since server startup.

Replica.Cluster.Files.LocalReports the number of cluster replicas on this server.

Replica.Cluster.Files.RemoteReports the number of cluster replicas on other servers in the cluster.

Replica.Cluster.Retry.SkippedReports the number of times the cluster replicator did not attempt replicationbecause the server was unreachable.

Replica.Cluster.Retry.WaitingReports the number of replicas currently waiting for replication retry attempts.

Replica.Cluster.SecondsOnQueueReports the time in seconds that the cluster replicator was on queue.

54 Version 3.1.0

Replica.Cluster.SecondsOnQueue.AvgReports the average time in seconds that the cluster replicator was on queue.

Replica.Cluster.SecondsOnQueue.MaxReports the maximum time in seconds that the cluster replicator was on queue.

Replica.Cluster.ServersReports the number of other servers in the cluster that are receiving replicationsfrom this server.

Replica.Cluster.SessionBytes.InReports the number of incoming bytes to the cluster replicator.

Replica.Cluster.SessionBytes.OutReports the number of outgoing bytes to the cluster replicator.

Replica.Cluster.SuccessfulReports the number of successful replications since server startup.

Replica.Cluster.WorkQueueDepthReports the current number of modified databases in the queue that are waiting to bereplicated by the cluster replicator to other servers.

Replica.Cluster.WorkQueueDepth.AvgReports the average number of modified databases in the queue that are waiting tobe replicated by the cluster replicator to other servers.

Replica.Cluster.WorkQueueDepth.MaxReports the maximum number of modified databases in the queue that are waiting tobe replicated by the cluster replicator to other servers.

Replica.Docs.AddedReports the number of documents added to the server’s databases by replication.

Replica.Docs.DeletedReports the number of documents deleted from the server’s databases by replication.

Replica.Docs.UpdatedReports the number of documents updated in the server’s databases by replication.

Replica.FailedReports the number of attempted replications that returned an error.

Replica.SuccessfulReports the number of replication attempts that returned no errors.

CLI SyntaxRTReplication –a <Attribute>

where:

<Attribute> The Replication monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTReplication" -a "Replica.Successful" "MailServerProfile"


2.R

eal-Time

Mo

nito

rs

Server

DescriptionMonitors Domino server statistics.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Server monitor; a description of each attribute follows.

Click Attributes to display the Server Attribute dialog and select the desired attribute.

Server.AvailabilityIndexReports the current percentage index of server availability. Zero (0) indicates noavailable resources; a value of 100 indicates complete server availability.

Server.AvailabilityThresholdReports the current setting of the availability threshold of a server. When theavailability index of a server drops below its availability threshold, the serverbecomes busy.

Server.BusyTimeQuery.ReceivedCountReports the number of queries to busy time in scheduling.

Server.BusyTimeQuery.Returned.Objects.SchedulesReports the number of responses to queries to busy time in scheduling.

Server.Cluster.AvailabilityIndexReports the current percentage index of server availability. Zero (0) indicates noavailable resources; a value of 100 indicates complete server availability.

Server.Cluster.AvailabilityThresholdReports the current setting of the availability threshold of a server. When theavailability index of that server drops below its availability threshold, the serverbecomes busy.

Server.Cluster.OpenRedirects.FailoverByPath.SuccessfulReports the number of times a server successfully redirected a client to anothercluster member after the client failed to open a database by path name.

56 Version 3.1.0

Server.Cluster.OpenRedirects.FailoverByPath.UnsuccessfulReports the number of times a server was not able to redirect a client to anothercluster member after the client failed to open a database by path name.

Server.Cluster.OpenRedirects.Failover.SuccessfulReports the number of times that a server successfully redirected a client to anothercluster member after the client failed to open a database by replica ID.

Server.Cluster.OpenRedirects.Failover.UnsuccessfulReports the number of times that a server was not able to redirect a client to anothercluster member after the client failed to open a database by replica ID.

Server.Cluster.OpenRedirects.LoadBalanceByPath.SuccessfulReports the number of times a server successfully redirected a client to anothercluster member after the client tried to open a database by path name when theserver was busy.

Server.Cluster.OpenRedirects.LoadBalanceByPath.UnsuccessfulReports the number of times a server was not able to redirect a client to anothercluster member after the client tried to open a database by path name when theserver was busy.

Server.Cluster.OpenRedirects.LoadBalance.SuccessfulReports the number of times a server successfully redirected a client to anothercluster member after the client tried to open a database by replica ID when theserver was busy.

Server.Cluster.OpenRedirects.LoadBalance.UnsuccessfulReports the number of times a server was unable to redirect a client to anothercluster member after the client tries to open a database by replica ID when theserver was busy.

Server.Cluster.OpenRequest.ClusterBusyReports the number of times a client tried to open a database on the server when theserver was busy and, on every available member.

Server.Cluster.OpenRequest.DatabaseOutOfServiceReports the number of times a client tried to open a database that is marked as outof service on the server.

Server.Cluster.OpenRequest.LoadBalancedReports the number of times a client tries to open a database on the server, when theserver is busy and on every available member.

Server.Cluster.ProbeCountReports the number of times a server completed a probe request of the other clustermembers.

Server.Cluster.ProbeErrorReports the number of times that a server receives an error when probing anotherserver.

Server.Cluster.ProbeTimeoutReports the interval (in minutes) at which the intracluster probe or cluster memberheartbeat occurs.

Server.Cluster.Trans.IntervalAvgTimeReports the average time interval of cluster transactions.


2.R

eal-Time

Mo

nito

rs

Server.Cluster.Trans.IntervalInMinutesReports the interval between cluster transactions in minutes.

Server.Cluster.Trans.IntervalInSecondsReports the interval between cluster transactions in seconds.

Server.Cluster.Trans.IntervalsUseInAvgReports the current setting for the number of intervals used to capture transactiondata used to calculate workload balance.

Server.Cluster.Trans.LastIntervalAvgTimeReports the last average interval time of cluster transactions.

Server.Cluster.Trans.NormalizeValueReports the current setting of acceptable average transaction time for a server inmilliseconds.

Server.Cluster.Trans.RunningCountReports the number of cluster transactions.

Server.MinIdleDisconnectReports the minimum number of minutes for disconnect.

Server.OpenRequest.MaxusersReports the number of open requests for maximum users.

Server.OpenRequest.PreV4ClientsReports the number of open requests for pre-R4 clients.

Server.OpenRequest.RestrictedReports the number of open requests for restricted clients.

Server.OpenRequest.V4ClientsReports the number of open requests for R4 clients.

Server.Ports.RS232Reports the number of RS232 serial ports on the server.

Server.Sessions.DroppedReports the number of sessions dropped in mid-transaction.

Server.TasksReports the number of tasks currently running on the server.

Server.Trans.PerMinuteReports the number of server transactions in the last minute.

Server.Trans.PerMinute.PeakReports the highest number of transactions during a one-minute interval.

Server.Trans.TotalReports the number of transactions processed since the server started.

Server.UsersReports the number of users with open sessions on the server.

Server.Users.1MinPeakReports the peak number of users over one minute.

Server.Users.5MinPeakReports the peak number of users over five minutes.

58 Version 3.1.0

Server.Users.PeakReports the peak number of concurrent users since the server was started.

Server.WorkThreadsReports the maximum number of concurrent transactions to create.

CLI SyntaxRTServer –a <Attribute>

where:

<Attribute> The Server monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTServer" -a "Server.Trans.Total" "MailServerProfile"


2.R

eal-Time

Mo

nito

rs

Server.Health.Sync

DescriptionMonitors the health of all server tasks.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Server.Health.Sync monitor; a description of Server Task Names (note.ini) attributefollows..

Server Task Names (notes.ini)Type the name of any server tasks you want to monitor. The name of the task mustbe entered as it appears in your notes.ini file, under servertasks. Multiple addinscan be monitored by separating the entries with commas (,).

CLI SyntaxRTServer.Health.Sync –a <ServerTaskNames>

where:

ServerTaskNameThe name of any server task(s) you want to monitor.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTServer.Health.Sync" -a stopserver "MailServerProfile"

60 Version 3.1.0

SMTP

DescriptionMonitors statistics related to Simple Mail Transfer Protocol (SMTP).




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the SMTP monitor; a description of each attribute follows.

Click Attributes to display the SMTP Attribute dialog and select the desired attribute.

SMTP.Messages.ProcessedReports the number of Simple Mail Transfer Protocol (SMTP) messages processed.

SMTP.Sessions.Accept.QueueReports the number of SMTP listener work queues of incoming sessions to beprocessed.

SMTP.Sessions.ActiveReports the number of active SMTP server tasks.

SMTP.Sessions.Inbound.BytesReceivedReports the number of bytes received by an SMTP server.

SMTP.Sessions.Inbound.BytesSentReports the number of bytes sent by an SMTP server.

SMTP.Sessions.Inbound.Non-SSLReports the number of SMTP server inbound TCP connections (non-SSL).

SMTP.Sessions.Inbound.SSLReports the number of SMTP server inbound SSL connections.

SMTP.Sessions.Inbound.SSL.Bad_HandshakeReports the number of SMTP server SSL handshake failures.

SMTP.Sessions.Inbound.TotalReports the total number of SMTP server inbound connections (SSL and non-SSL).

SMTP.Sessions.PeakReports the peak number of SMTP server tasks since server startup.


2.R

eal-Time

Mo

nito

rs

SMTP.Sessions.Threads.BusyReports the number of SMTP server tasks currently running.

SMTP.Sessions.Threads.IdleReports the number of SMTP server tasks currently idle.

SMTP.Sessions.TotalReports the total number of SMTP server tasks since server startup.

CLI SyntaxRTSMTP –a <Attribute>

where:

<Attribute> The SMTP monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTSSMTP" -a "SMTP.Session.Peak" "MailServerProfile"

62 Version 3.1.0

SMTPMTA

DescriptionMonitors statistics related to the SMTP Mail Transfer Agent.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the SMTPMTA monitor; a description of each attribute follows.

Click Attributes to display the SMTPMTA Attribute dialog and select the desired attribute.

SMTPMTA.ConvFailuresReports the total number of Simple Message Transfer Protocol Message TransferAgents (SMTP MTA) conversion failures.

SMTPMTA.DeadReports the number of dead SMTP MTA messages.

SMTPMTA.DeliveredReports the number of SMTP MTA messages delivered.

SMTPMTA.HighInBoundReports the highest number of inbound processes.

SMTPMTA.HighOutBoundReports the highest number of outbound processes.

SMTPMTA.InBoundBytesReports the number of inbound bytes.

SMTPMTA.InBoundSizeReports the size of the largest inbound message.

SMTPMTA.OutBoundBytesReports the number of outbound bytes.

SMTPMTA.OutBoundSizeReports the size of the largest outbound message.

SMTPMTA.TotalRoutedReports the total number of SMTP MTA messages routed.


2.R

eal-Time

Mo

nito

rs

SMTPMTA.TransFailuresReports the number of SMTP MTA transmission failures.

SMTPMTA.TransferredReports the number of SMTP MTA messages transferred.

SMTPMTA.WaitingReports the number of SMTP MTA messages waiting.

SMTPMTA.WaitingConvReports the amount of mail waiting to be converted.

SMTPMTA.WaitingRecipientsReports the amount of mail waiting to be delivered.

SMTPMTA.WaitingTransReports the amount of mail waiting to be transferred.

CLI SyntaxRTSMTPMTA –a <Attribute>

where:

<Attribute> The SMTPMTA monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTSMTPMTA" -a "SMTPMTP.Dead" "MailServerProfile"

64 Version 3.1.0

SMTP.<Name>

DescriptionMonitors statistics related to the named SMTP device.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the SMTP.<Name> monitor; a description of the SMTP Device attribute follows.

SMTP DeviceThe name of the device you want to monitor. The following statistics are currentlyimplemented: MsgSizeKBytes, MsgRecipients, or SessionDuration.

CLI SyntaxRTSMTP.<Name>

where:

<Name> The name of the device to monitor. The following statistics are currentlyimplemented: MsgSizeKBytes, MsgRecipients, or SessionDuration.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTSMTP.MsgRecipients" "MailServerProfile"


2.R

eal-Time

Mo

nito

rs

SPIN

DescriptionMonitors statistics related to SPIN. (For Lotus Corporation internal use only.)




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the SPIN monitor; a description of each attribute follows.

Click Attributes to display the SPIN Attribute dialog and select the desired attribute.

SPIN.AvtIterToHitReports the average ratio of SPIN lock iterations to hits.

SPIN.DelaysReports the count of SPIN lock delays.

SPIN.DelaysMsecsReports the duration of SPIN lock delays in microseconds.

SPIN.FRWSemGetReadExtReports the SPIN lock FRW semaphore read.

SPIN.FRWSemPutReadExtReports the SPIN lock FRW semaphore put.

SPIN.HitsReports the number of SPIN lock hits.

SPIN.MaxDelayMaskReports the SPIN lock maximum delay mask.

SPIN.MaxDelayMsecsReports the SPIN lock maximum delay in microseconds.

CLI SyntaxRTSPIN –a <Attribute>

where:

<Attribute> The SPIN monitor attribute.

66 Version 3.1.0

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTSPIN" -a "SPIN.Delays" "MailServerProfile"


2.R

eal-Time

Mo

nito

rs

SwapDisk

DescriptionMonitors statistics related to SwapDisk.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the SwapDisk monitor; a description of each attribute follows.

SwapDisk.FreeReports the number of free bytes on the disk that contains the swap file for a server.

CLI SyntaxRTSwapDisk –a <SwapDiskAttribute>

where:

<SwapDiskAttribute>The only option at this time is SwapDisk.Free. SwapDisk.Free returns the numberof free bytes on the disk that contains the swap file for a server.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTSwapDisk" -a "SwapDisk.Free" "MailServerProfile"

68 Version 3.1.0

Web Monitor

DescriptionMonitors numeric statistics related to the Web Retriever process.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Web Monitor; a description of each attribute follows.

Click Attributes to display the Web Monitor Attributes dialog and select the desiredattribute.

Web.Retriever.Access.FTPReports the number of FTP retriever accesses.

Web.Retriever.Access.GopherReports the number of Gopher retriever accesses.

Web.Retriever.Access.HTTPReports the number of HTTP retriever accesses.

Web.Retriever.Bytes.ReceivedReports the number of retriever bytes received.

Web.Retriever.Bytes.SentReports the number of retriever bytes sent.

Web.Retriever.ImageCache.HitsReports the number of successful accesses on the retriever image cache.

Web.Retriever.ImageCache.MissesReports the number of unsuccessful accesses on the retriever image cache.

Web.Retriever.Process.Num.ActiveReports the number of active retriever processes.

Web.Retriever.Process.Access.FTPReports the number of retriever process FTP accesses.

Web.Retriever.Process.Access.GopherReports the number of retriever process Gopher accesses.


2.R

eal-Time

Mo

nito

rs

Web.Retriever.Process.Bytes.ReceivedReports the number of bytes sent by a retriever process.

Web.Retriever.Process.Bytes.SentReports the number of bytes received by a retriever process.

Web.Retriever.Process.ProcessIDReports the process ID number.

Web.Retriever.Process.URLs.FailedReports the number of failed retriever process URLs.

Web.Retriever.Process.URLs.RequestedReports the number of requested retriever process URLs.

Web.Retriever.Process.URLs.SucceededReports the number of successful retriever process URLs.

Web.Retriever.Process.Access.HTTPReports the number of retriever process HTTP accesses.

Web.Retriever.Process.Num.BusyReports the number of busy retriever processes.

Web.Retriever.Process.Num.IdleReports the number of idle retriever processes.

Web.Retriever.Process.Num.MaximumReports the maximum number of retriever processes.

Web.Retriever.URLs.FailedReports the number of failed retriever URLs.

Web.Retriever.URLs.RequestedReports the number of retriever URLs requested.

Web.Retriever.URLs.SucceededReports the number of retriever URLs that have been successfully accessed.

Web.Retriever.VPOOL.Max.BufReports the number of buffer VPOOLs that have reached maximum size.

Web.Retriever.VPOOL.Max.ElementReports the number of element VPOOLs that have reached maximum size.

Web.Retriever.VPOOL.Max.MarkerReports the number of marker VPOOLs that have reached maximum size.

Web.Retriever.VPOOL.Max.TextReports the number of text VPOOLs that have reached maximum size.

Web.Retriever.VPOOL.Max.URLReports the number of URL VPOOLs that have reached maximum size.

CLI SyntaxRTWeb –a <Attribute>

where:

<Attribute> The Web Monitor attribute.

70 Version 3.1.0

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTWeb" -a "Web.Retriever.Access.FTP" "MailServerProfile"


2.R

eal-Time

Mo

nito

rs

XPC.<PortName>

DescriptionMonitors statistics related to the XPC console port. XPC is the Lotus communicationsprotocol for use with modems.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the XPC.<PortName> monitor; a description of each attribute follows.

XPC Monitor Port AttributeClick the button to the right of this text box to open the XPC Monitor PortAttribute dialog box, from which you can select from the following monitors forthe port you want to monitor:

Errors.CRCReports the number of cyclic redundancy check (CRC) errors on the serialport.

Errors.PortReports the number of port errors on the serial port.

Errors.RetransmittedPacketsReports the number of retransmitted packets on the serial port.

Sessions.ActiveReports the number of active sessions on the serial port.

Speed.CarrierReports the carrier speed on the serial port.

Speed.PortReports the port speed on the serial port.

UserBytes.ReceivedReports the number of user bytes received on the serial port.

UserBytes.SentReports the number of user bytes sent on the serial port.

72 Version 3.1.0

UserMsgs.ReceivedReports the number of user messages received on the serial port.

UserMsgs.SentReports the number of user messages sent on the serial port.

CLI SyntaxRTXPC.<PortName> –a <Attribute>

where:

<PortName> The name of the port to monitor.

<Attribute> The RTXPC Monitor attribute.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "RTXPC.Port1" -a "UserMsgs.Sent""MailServerProfile"


2.R

eal-Time

Mo

nito

rs

74 Version 3.1.0

Statistics Monitors

This chapter lists the Tivoli Manager for Domino statistics monitors alphabetically. Eachentry provides complete information on the capabilities and settings for the monitor.

The statistics monitoring collection includes synchronous and synchronous/asynchronousmonitors.

Synchronous monitors can monitor a single resource. For example, you can configure onesynchronous monitor to return the values on the mem.free statistic.

Synchronous/asynchronous (sync/async) monitors return values on multiple statistics. Forexample, you can configure a sync/async monitor to check the size of multiple Dominodatabases. Sync/async monitors consist of one synchronous monitor and one or moreasynchronous monitors. When you configure a sync/async monitor, synchronous monitorsare run according to their specified schedule, gathering information for multiple resourcesand asynchronous monitors run individually to return values for each statistic to DistributedMonitoring.

Table 2 summarizes the Domino Statistics monitors.

Table 2. Domino Statistics Monitor CollectionMonitor CLI Name Description

Agent Agent Monitors statistics related to the AgentManager process.

Agent’s last return code AgentRunInfo Returns the value of the agent’s lastreturn code.

Calendar Calendar Monitors statistics related to the CalendarManager process.

Cluster Availability Status ClusterStatus Monitors the availability of a Dominocluster.

Comm Comm Monitors statistics related to Dominonetwork communications.

Data Rollup Interval DataRollupInterval Monitors the data rollup interval.

Database Database Monitors statistics related to databaseactivity on the Domino Server.

Database Frequency DatabaseFrequency Reports the frequency of reads, writes, oruses on the server.

Database.RM DatabaseRM Monitors statistics related to transactionallogging.

Database.Statistics.Async DbStatisticsAsync Monitors database statistics

3


3.S

tatisticsM

on

itors

Table 2. Domino Statistics Monitor Collection (continued)Monitor CLI Name Description

Database.Statistics.Sync DbStatisticsSync Monitors database statistics

Db.Corruption.Async DbCorruptionAsync Monitors database corruption.

Db.Corruption.Sync DbCorruptionSync Monitors database corruption.

Db.Template.Async DbTemplateAsync Monitors changes in the databasetemplate.

Db.Template.Sync DbTemplateSync Monitors changes in the databasetemplate.

Disk Disk Monitors disk-related statistics.

Disk.SYS DiskSys Monitors statistics related to the NetWare

Domino Domino Monitors numeric statistics from theDomino server.

Endpoint Monitor TMAEndpointStatus Monitors a Tivoli endpoint.

Generic Generic Monitors a process using a genericargument.

ICM ICM Monitors Internet Cluster Managerstatistics.

IMAP IMAP Monitors statistics related to Internet MailAccess Protocol (IMAP).

LDAP LDAP Monitors statistics related to LightweightDirectory Access Protocol (LDAP).

LogQuery (Log.nsf) LogQuerySync Monitors a database log for specifiedstrings.

LogQuery (Found string) LogQueryFoundString-Async

Monitor strings found in the log.

LogQuery (Form Name) LogQueryFormName-Async

Returns the form name in which thestrings were found.

LogQuery (Field Name) LogQueryFieldName-Async

Returns the field in which the stringswere found.

LogQuery (Note ID) LogQueryNoteIDAsync Returns the note ID in which the stringswere found.

Mail Mail Monitors numeric statistics related to mailrouting.

MailByDest.<DestServerName>

MailByDest Monitors mail by destination server name.

Mailn.box MailnBox Monitors mailbox routing configurations.

Mail.Waiting.Async MailWaitingAsync Monitors mail waiting in the specifiedmailbox.

Mail.Waiting.Sync MailWaitingSync Monitors mail waiting in the specifiedmailbox.

Memory Memory Monitors numeric statistics related toserver system memory.

MemoryAssessment MemoryAssessment Monitors the Domino Server MemoryAssessment statistic.

Mail Trace MailTrace Traces mail activities.

76 Version 3.1.0


MTA MTA Monitors statistics related to various MailTransfer Agents.

NET.<PortName> NET.<PortName> Monitors Internet-related statistics.

NETBIOS.<PortName> NETBIOS Monitors NetBIOS statistics for each portthat is specified in the port name.

nntp NNTP Monitors statistics related to a NetworkNews Transport Protocol.



Monitors statistics related to a remoteNNTP server.

Object Object Monitors statistics related to the sharedmail store.

POP3 POPthree Monitors statistics related to Post OfficeProtocol 3 (POP3).


QOS Monitors mail probe response time.

Replication Replication Monitors numeric statistics related todatabase replication.

Replication check ReplicationCheckSync Compares actual replications to scheduledreplications.

Replication (DatabaseReplication Info)

ReplicationDBInfoAsync Returns replication database information.

Replication (Duration) ReplicationDurationAsync Returns the duration in time of thereplication.

Replication (End Time) ReplicationEndTimeAsync Returns the replication end time.

Replication(Hit/Miss/Manual)

ReplicationHitMissAsync Indicates whether the replication occurredas scheduled, did not occur as scheduled,or was performed manually.

Replication (ID) ReplicationIDAsync Returns the ID assigned to the replicationoccurrence.

Replication (Remote servername)

ReplicationRemoteSRV-Async

Returns the name of the remote server inthe replication.

Replication (ReplicationEvents)

ReplicationEventsAsync Returns a list of the events that occurredduring the replication.

Replication (Server Name) ReplicationServerName-Async

Returns the name of the source server inthe replication.

Replication (server namethat initiated replication)

ReplicationInitiatedBy-Async

Returns the name of the server initiatingthe replication.

Replication (Start Time) ReplicationStartTimeAsync Returns the replication start time.

Server Server Monitors Domino server statistics.

Server Availability DominoServerAvailable Monitors server availability.

Server.Health.Async ServerHealthAsync Monitors the server’s health.

Server.Health.Sync ServerHealthSync Monitors the server’s health.

SMTP SMTP Monitors statistics related to Simple MailTransfer Protocol.


3.S

tatisticsM

on

itors


SMTPMTA SMTPMTA Monitors statistics related to the SMTPMail Transfer Agent.

SMTP.<Name> SMTP.<Name>.<Attribute>

Monitors statistics related to the namedSMTP device.

SPIN SPIN Monitors statistics related to SPIN.

Stalled.Mail.Async StalledMailAsync Checks for stalled mail in the mailbox.

Stalled.Mail.Sync StalledMailSync Checks for stalled mail in the mailbox.

SwapDisk SwapDisk Monitors statistics related to SwapDisk.

Tdp Schedule TdpSchedule Monitors statistics related to schedulingof Tivoli Data Protection processes.

Transaction Log File Size TransLogSize Monitors the size of the log files.

Transaction LoggingArchival Status

TransLogStatus Checks that transaction logs are beingarchived.

UserMail.Statistics.Async UMStatisticsAsync Monitors user mail file statistics.

UserMail.Statistics.Sync UMStatisticsSync Monitors user mail file statistics.

Web Monitor Web Monitors numeric statistics related to theWeb Retriever process.

XPC.<PortName> XPC.<PortName> Monitors statistics related to the XPCconsole port.

78 Version 3.1.0

Agent

DescriptionMonitors statistics related to the Agent Manager process.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Agent monitor; a description of each attribute follows.

Click Attributes to display the Agent Monitor Attribute dialog and select the desiredattribute.

Agent.Daily.AccessDenialsReports the number of access denials for agents over a day.

Agent.Daily.ScheduledRunsReports the number of scheduled runs in a day.

Agent.Daily.TriggeredRunsReports the number of triggered agent runs in a day.

Agent.Daily.UnsuccessfulRunsReports the number of unsuccessful agent runs in a day.

Agent.Hourly.AccessDenialsReports the number of agent access denials in an hour.

Agent.Hourly.ScheduledRunsReports the number of scheduled runs in an hour.

Agent.Hourly.TriggeredRunsReports the number of triggered agent runs in an hour.

Agent.Hourly.UnsuccessfulRunsReports the number of unsuccessful agent runs in an hour.

CLI SyntaxAgent –a <Attribute>

where:


3.S

tatisticsM

on

itors

<Attribute> The Agent monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "Agent" -a "Agent.Hourly.UnsuccessfulRuns""MailServerProfile"

80 Version 3.1.0

Agent’s last return code

DescriptionChecks whether a database agent ran as scheduled. If the agent ran within the time framespecified, it returns the agent’s return code. Otherwise, the NO DATA message is returned.The monitor must be scheduled in accordance with the agent’s schedule.



Target EndpointsLotusDominoServer

Desktop OptionsThe following shows the Add Monitor to TME 10 Monitoring Profile dialog box for thismonitor.

Database NameThe name of the database to which the agent belongs.

Agent NameThe agent name.

Time FrameThe elapsed time in minutes between the time the agent last ran and the time theagent monitor runs.

CLI SyntaxAgentRunInfo –a <DatabaseName> –a <AgentName> –a <TimeFrame>

where:

<DatabaseName>The name of the database to which the agent belongs.

<AgentName>The agent name.

<TimeFrame>The elapsed time in minutes between the time the agent last ran and the time theagent monitor runs.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "AgentRunInfo" -a "support.nsf"-a "Assign Support Rep" -a 30 "MailServerProfile"


3.S

tatisticsM

on

itors

Calendar

DescriptionMonitors statistics related to the Calendar Manager process.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Calendar monitor; a description of each attribute follows.

Click Attributes to display the Calendar Monitor Attribute dialog and select the desiredattribute.

Calendar.Total.All.Appointments.ReservationsDisplays the total number of appointments and reservations in scheduling.

Calendar.Total.All.Users.ResourcesDisplays the total number of users and resources in scheduling.

Calendar.Total.ApptsDisplays the total number of appointments in scheduling

Calendar.Total.ReservationsDisplays the total number of reservations in scheduling.

Calendar.Total.ResourcesDisplays the total number of resources in scheduling.

Calendar.Total.UsersDisplays the total number of users in scheduling

CLI SyntaxCalendar –a <Attribute>

where:

<Attribute> The Calendar monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "Calendar" -a "Calendar.Total.Appts""MailServerProfile"

82 Version 3.1.0

Cluster Availability Status

DescriptionVerifies that at least one of the clustered servers is running. This monitor should be usedonly with Domino servers that are part of a Domino cluster. This monitor pings the assignedserver. If the server responds to the ping, the monitor returns a zero (0) value. If the serverdoes not respond, the monitor pings the other members of the cluster in turn, returning azero (0) at the first response to the ping.

The following table lists the return values for the Cluster Availability Status monitor:

0 At least one server in the cluster responded

1 The server responded but is not in a cluster

2 The cluster is unavailable; none of the servers responded

3 The server did not respond and is not in a cluster




Desktop OptionsNone

CLI SyntaxClusterStatus

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "ClusterStatus" "MailServerProfile"


3.S

tatisticsM

on

itors

Comm

DescriptionMonitors statistics related to Domino network communications.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Comm monitor; a description of each attribute follows.

Click Attributes to display the Comm Monitor Attribute dialog and select the desiredattribute.

Comm.Appletalk.AppleTalk.StatsLoggedReports the number of Appletalk statistics logged.

Comm.Netware.SPXII.StatsLoggedReports the number of SPXII statistics logged.

Comm.NumOldSessionsClosedReports the number of sessions closed by the Notes server to accommodate newusers.

CLI SyntaxComm –a <Attribute>

where:

<Attribute> The Comm monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "Comm" -a "Comm.Netware.SPXII.StatsLogged""MailServerProfile"

84 Version 3.1.0

Database

DescriptionMonitors statistics relating to database activity on a Domino server.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Database monitor; a description of each attribute follows.

Click Attributes to display the Database Attribute dialog and select the desired attribute.

Database.BufferControlPool.PeakReports the peak number of database buffer control pools.

Database.BufferControlPool.SizeReports the size of database control pools.

Database.BufferControlPool.UsedReports the number of used database buffer control pools.

Database.BufferPool.AllocatedReports the number of database control pools allocated.

Database.BufferPool.IRISOpenContainersReports the number of IRIS open containers for database buffer pools.

Database.BufferPool.Maximum.MegabytesReports the maximum size of database control pools.

Database.BufferPool.Peak.MegabytesReports the peak number of database buffer pools.

Database.BufferPool.PerCentReadsInBufferReports the percentage of buffer pool reads.

Database.BufferPool.MM.ReadsReports the number of database buffer pool reads.

Database.BufferPool.MM.UsedReports the number of used database buffer pools.


3.S

tatisticsM

on

itors

Database.BufferPool.MM.WritesReports the number of database buffer pool writes.

Database.DbCache.CurrentEntriesReports the current number of entries in the database cache.

Database.DbCache.HighWaterMarkReports the period of most activity in the database cache.

Database.DbCache.HitsReports the number of hits to the database cache.

Database.DbCache.InitialDbOpensReports the number of times the database cache opened the database.

Database.DbCache.LookupsReports the number of lookups to the database cache.

Database.DbCache.MaxEntriesReports the maximum number of entries in the database cache.

Database.DbCache.OvercrowdingRejectionsReports the number of rejections due to overcrowding in the database cache.

Database.ExtMgrPool.PeakReports the peak number of external manager pools used.

Database.ExtMgrPool.UsedReports the number of external manager pools.

Database.NIFPool.PeakReports the peak number of database network information file (NIF) pools.

Database.NIFPool.UsedReports the number of database NIF pools.

Database.NSF.FreeHandleStack.FreeHandleStackHitsReports the number of database free handle stack hits.

Database.NSF.FreeHandleStack.HandleAllocationsReports the number of database free handle stack allocations.

Database.NSF.FreeHandleStack.MissRateReports the database free handle stack miss rate.

Database.NSFPool.PeakReports the peak number of database NSF pools.

Database.NSFPool.SizeReports the size of database NSF pools.

Database.NSFPool.UsedReports the number of database NSF pools.

CLI SyntaxDatabase –a <Attribute>

where:

<Attribute> The Database monitor attribute.

86 Version 3.1.0

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "Database" -a "Database.BufferPool.Allocated""MailServerProfile"


3.S

tatisticsM

on

itors

Database Frequency

DescriptionReports the frequency of reads, writes, or uses on the server. This monitor can providereports of daily, weekly, monthly, or total activity on a specific database.





Database NameThe database to monitor.

FrequencyThe time period during which you want to collect information about database access.The options are PreviousDay, PreviousWeek, PreviousMonth, andTotalsSinceCreation. Click the Attributes button to display the Frequency dialogbox for this argument.

Type The type of access you want to collect information about. The options are Reads,Writes, and Uses. Click the Attributes button to display the Type dialog box forthis argument.

CLI SyntaxDatabaseFrequency –a <DatabaseName> –a <Frequency> –a <Type>

where:

<DatabaseName>The database to monitor.

<Frequency>The time period during which you want to collect information about database access.The options are PreviousDay, PreviousWeek, PreviousMonth, andTotalsSinceCreation.

<Type>The type of access you want to collect information about. The options are Reads,Writes, and Uses.

88 Version 3.1.0

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "DatabaseFrequency" -a "Names.nfs"-a "PreviousMonth" -a "Uses" "MailServerProfile"


3.S

tatisticsM

on

itors

Database.RM

DescriptionMonitors statistics related to transactional logging.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogbox for this monitor; a description of each attribute follows.

Click the Attributes button to display the Database.RM Attribute dialog box for thismonitor.

Database.RM.Current.K.Restart.Redo.HoldReports the number of changes on the log but not yet in the database.

Database.RM.Current.K.UnCommitted.Undo.HoldReports the number of changes held back by long running transactions.

Database.RM.Current.MaxChkptScan.msecReports the number of transactions per minute from the current checkpoint.

Database.RM.LastChkpt.Avg.K.Logged.PerTranReports the average transaction size from the last checkpoint.

Database.RM.LastChkpt.Interval.SecReports the time since the last checkpoint.

Database.RM.LastChkpt.K.LoggedReports the amount of data logged in the checkpoint interval.

Database.RM.LastChkpt.TimeReports the time of the last checkpoint.

Database.RM.LastChkpt.Total.DBsReports the databases open or in DBCache at the time of the last checkpoint.

Database.RM.LastChkpt.TransReports actual transactional logging type transactions (API calls that did databaseupdates).

90 Version 3.1.0

Database.RM.Peak.Avg.K.Logged.PerTranReports the average size of transactions from the peak checkpoint.

Database.RM.Peak.Interval.SecReports the time interval before the peak checkpoint.

Database.RM.Peak.K.LoggedReports the amount of data logged in the interval before the peak checkpoint.

Database.RM.Peak.TimeReports the time of the peak checkpoint.

Database.RM.Peak.Total.DBsReports the databases open or in DBCache at the time of the peak checkpoint.

Database.RM.Peak.TransReports actual transactional logging type transactions from the peak checkpoint (APIcalls that did database updates).

Database.RM.Peak.Trans.PerMinReports the number of transactions per minute from the peak checkpoint.

Database.RM.Restart.Duration.SecReports the time (in seconds) that it took to apply the incomplete changes after acrash.

Database.RM.Restart.K.AppliedReports the amount of incomplete changes detected and applied in KB. For example,22MB in 33sec.

Database.RM.Restart.TimeReports the time that the server was started.

Database.RM.SinceChkpt.K.LoggedReserved for Lotus Corporation internal use only.

Database.RM.SinceChkpt.TransReserved for Lotus Corporation internal use only.

Database.RM.SinceStartup.AbortsReports the number of failed transactions since the server was started.

Database.RM.SinceStartup.Critical.Log.TimesReports the number of times the system ran critically log full since the server wasstarted.

Database.RM.SinceStartup.Log.Recs.AnalyzedReserved for Lotus Corporation internal use only.

Database.RM.SinceStartup.Log.Recs.AppliedReserved for Lotus Corporation internal use only.

Database.RM.SinceStartup.Log.Recs.ReadReserved for Lotus Corporation internal use only.

Database.RM.SinceStartup.Log.Recs.WrittenReserved for Lotus Corporation internal use.

Database.RM.SinceStartup.M.LoggedReports how much log has been written (in MB) since the server was started.


3.S

tatisticsM

on

itors

Database.RM.SinceStartup.TransReports actual transactional logging type transactions from the peak checkpoint (APIcalls that did database updates).

Database.RM.Sys.LoggedReports whether Sys.Logged is enable or disabled. If disabled, no otherDatabase.RM statistics are shown.

Database.RM.Sys.Log.TypeReports whether logging type is Circular or Archive.

Database.RM.Sys.M.Chkpt.IntervalReports the checkpoint interval.

Database.RM.Sys.M.Log.SizeReports the maximum log size defined.

Database.RM.Sys.M.Redo.LimitReports the recommended maximum Redo. Hold span before aggressive flushingoccurs.

Database.RM.Sys.PhaseReports the transactional logging phase.

CLI SyntaxDatabaseRM –a <Attribute>

where:

<Attribute> The Database.RM monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "DatabaseRM" -a "Database.RM.Last.Chkpt.Trans""MailServerProfile"

92 Version 3.1.0

Database.Statistics.Async

DescriptionMonitors database statistics.





Channel NameThe channel name. You must assign this monitor the same channel name as theDatabase.Statistics.Sync monitor. Avoid using this channel name for any othermonitors.

CLI SyntaxDbStatisticsAsync –a <ChannelName>

where:

<ChannelName>The channel name. You must assign this monitor the same channel name as theDatabase.Statistics.Sync monitor. Avoid using this channel name for any othermonitors.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "DbStatisticsAsync" -a "Mail" "MailServerProfile"


3.S

tatisticsM

on

itors

Database.Statistics.Sync

DescriptionMonitors database statistics.





Channel NameThe channel name. If the channel has already been created (using a DistributedMonitoring command, for example), then enter the name of the existing channel.You must assign this monitor the same channel name as theDatabase.Statistics.Async monitor. Avoid using this channel name for any othermonitors.

Monitor AttributeClick the Attributes button to display the Monitor Attribute dialog box for thisargument.

Size The current size of the database in kilobytes.

WhiteSpace The size of the database white space.

SizeLimit The database size limit in kilobytes.

Uses The uses of the database.

Reads The number of database reads.

Writes The number of database writes.

Database File SpecificationType the name of the database file. Use semicolons to separate multiple file names.

CLI SyntaxDbStatisticsSync –a <ChannelName> –a <MonitorAttribute> –a <DatabaseFileSpec>

where:

94 Version 3.1.0

<ChannelName>The channel name. If the channel has already been created (using a DistributedMonitoring command, for example), then enter the name of the existing channel.You must assign this monitor the same channel name as theDatabase.Statistics.Async monitor. Avoid using this channel name for any othermonitors.

<MonitorAttribute>Takes one of the following values:

Size The current size of the database in kilobytes.

WhiteSpace The size of the database white space.

SizeLimit The database size limit in kilobytes.

Uses The uses of the database.

Reads The number of database reads.

Writes The number of database writes.

<DatabaseFileSpec>The name of the database file. Use semicolons to separate multiple file names.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "DbStatisticsSync" -a "Mail" -a "10"-a "C:\names.nsf" "MailServerProfile"


3.S

tatisticsM

on

itors

Data Rollup Interval

DescriptionMonitors the data rollup interval.




Desktop OptionsNone

CLI SyntaxDataRollupInterval

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "DataRollupInterval" "MailServerProfile"

96 Version 3.1.0

Db.Corruption.Async

DescriptionMonitors for corrupt database views.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogbox for this monitor.

Channel NameThe channel name. You must assign this monitor the same channel name as theDb.Corruption.Sync monitor. Avoid using this channel name for any other monitors.

CLI SyntaxDbCorruptionAsync –a <ChannelName>

where:

ChannelNameThe channel name. You must assign this monitor the same channel name as theDb.Corruption.Sync monitor. Avoid using this channel name for any other monitors.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "DbCorruptionAsync" -a "Names" "MailServerProfile"


3.S

tatisticsM

on

itors

Db.Corruption.Sync

DescriptionMonitors for corrupted database views.





Channel NameThe channel name. If the channel has already been created (using a DistributedMonitoring command, for example), then enter the name of the existing channel.You must assign this monitor the same channel name as the Db.Corruption.Asyncmonitor. Avoid using this channel name for any other monitors.

Database File SpecificationThe name of the database file to monitor for corruption. If omitted, all databases aremonitored.

CLI SyntaxDbCorruptionSync –a <ChannelName> –a <DatabaseFileSpec>

where:

<ChannelName>The channel name. If you already created the channel (using a DistributedMonitoring command, for example), then enter the name of the existing channel.You must assign this monitor the same channel name as the Db.Corruption.Asyncmonitor. Avoid using this channel name for any other monitors.

<DatabaseFileSpec>The name of the database file to monitor for corruption. If omitted, all databases aremonitored.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "DbCorruptionSync" -a "Names" -a "Names.nsf""MailServerProfile"

98 Version 3.1.0

Db.Template.Async

DescriptionMonitors changes in the database template.





Channel NameThe channel name. You must assign this monitor the same channel name as theDb.Template.Sync monitor. Avoid using this channel name for any other monitors.

CLI SyntaxDbTemplateAsync –a <ChannelName>

where:

<ChannelName>The channel name. You must assign this monitor the same channel name as theDb.Template.Sync monitor. Avoid using this channel name for any other monitors.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "DbTemplateAsync" -a "Mail" "MailServerProfile"


3.S

tatisticsM

on

itors

Db.Template.Sync

DescriptionMonitors changes in the database template.





Channel NameThe channel name. If the channel has already been created (using a TivoliDistributed Monitoring command, for example), then enter the name of the existingchannel. You must assign this monitor the same channel name as theDb.Template.Async monitor. Avoid using this channel name for any other monitors.

File SpecificationType the path and file name of the .ntf file to monitor

Number of DaysType the number of days since the last change. This value is used as an upper limitfor change notification.

CLI SyntaxDbTemplateSync –a <ChannelName> –a <FileSpec> –a <Days>

where:

<ChannelName>The channel name. If the channel has already been created (using a TivoliDistributed Monitoring command, for example), then enter the name of the existingchannel. You must assign this monitor the same channel name as theDb.Template.Async monitor. Avoid using this channel name for any other monitors.

<FileSpec>The path and file name of the .ntf file to monitor

<Days>The number of days since the last change. This value is used as an upper limit forchange notification.

100 Version 3.1.0

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "DbTemplateSync" -a "Mail" -a "*.ntf" -a "10""MailServerProfile"


3.S

tatisticsM

on

itors

Disk

DescriptionMonitors disk-related statistics.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Disk monitor; a description of each attribute follows.

Disk Drive Select the drive letter or location of the drive you would like to monitorfrom the dialog displayed by clicking the Attributes button to the right ofthis text box.

Disk AttributeSelect whether to monitor the selected drive for free space or size in bytesfrom the dialog displayed by clicking the Attributes button to the right ofthis text box.

CLI SyntaxDisk –a Disk.<Drive>.<Attribute>

where:

<Drive> The drive letter or location of the drive you would like to monitor from thefollowing choices: C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U,V, W, X, Y, Z, /, Vol0, Vol1, Vol2, Vol3

<Attribute> Free space or size in bytes.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "Disk" -a "Disk.C.Free" "MailServerProfile"

waddmon "Domino v5.0 Statistics Collection" "Disk" -a "Disk.C.Size" "MailServerProfile"

102 Version 3.1.0

Disk.SYS

DescriptionMonitors statistics related to the NetWare SYS file.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Disk.SYS monitor; a description of each attribute follows.

Click Attributes to display the DiskSys Monitor Attribute dialog and select the desiredattribute.

Disk.SYS.AvailableBlocksReports the number of available disk blocks on a NetWare SYS volume.

Disk.SYS.AvailableDirectorySlotsReports the number of available directory slots on a NetWare SYS volume.

Disk.SYS.DriveNumberReports the physical driver number of a Network SYS volume.

Disk.SYS.FreeReports the amount of free space on a NetWare SYS volume.

Disk.SYS.NotYetPurgableBlocksReports the number of blocks that cannot be purged on a NetWare SYS volume.

Disk.SYS.NumberReports the volume number of a NetWare SYS volume.

Disk.SYS.PurgableBlocksReports the number of blocks that can be purged on a NetWare SYS volume.

Disk.SYS.SizeReports the size of a NetWare SYS volume.

Disk.SYS.StartingBlockReports the physical block number where a NetWare SYS volume starts.

Disk.SYS.TotalBlocksReports the number of physical blocks a NetWare SYS volume spans.


3.S

tatisticsM

on

itors

Disk.SYS.TotalDirectorySlotsReports the number of directory slots a NetWare SYS volume spans.

CLI SyntaxDiskSys –a <Attribute>

where:

<Attribute> The Disk.SYS monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "DiskSys" -a "Disk.SYS.Size" "MailServerProfile"

104 Version 3.1.0

Domino

DescriptionMonitors numeric statistics from the Domino server.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Domino monitor; a description of each attribute follows.

Click Attributes to display the Domino Monitor Attribute dialog and select the desiredattribute.

Domino.Command.CreateDocumentCounts the “CreateDocument” URLs that have come into the server since the serverwas last started.

Domino.Command.DeleteDocumentCounts the “DeleteDocument” URLs that have come into the server since the serverwas last started.

Domino.Command.EditDocumentCounts the “EditDocument” URLs that have come into the server since the serverwas last started.

Domino.Command.LoginCounts the “Login” URLs that have come into the server since the server was laststarted.

Domino.Command.NavigateCounts the “Navigate” URLs that have come into the server since the server was laststarted.

Domino.Command.OpenAboutCounts the “OpenAbout” URLs that have come into the server since the server waslast started.

Domino.Command.OpenAgentCounts the “OpenAgent” URLs that have come into the server since the server waslast started.


3.S

tatisticsM

on

itors

Domino.Command.OpenDatabaseCounts the “OpenDatabase” URLs that have come into the server since the serverwas last started.

Domino.Command.OpenDocumentCounts the “OpenDocument” URLs that have come into the server since the serverwas last started.

Domino.Command.OpenElementCounts the “OpenElement” URLs that have come into the server since the serverwas last started.

Domino.Command.OpenFormCounts the “OpenForm” URLs that have come into the server since the server waslast started.

Domino.Command.OpenHelpCounts the “OpenHelp” URLs that have come into the server since the server waslast started.

Domino.Command.OpenIconCounts the “OpenIcon” URLs that have come into the server since the server waslast started.

Domino.Command.OpenNavigatorCounts the “OpenNavigator” URLs that have come into the server since the serverwas last started.

Domino.Command.OpenServerCounts the “OpenServer” URLs that have come into the server since the server waslast started.

Domino.Command.OpenViewCounts the “OpenView” URLs that have come into the server since the server waslast started.

Domino.Command.ReadFormCounts the “ReadForm” URLs that have come into the server since the server waslast started.

Domino.Command.SearchSiteCounts the “SearchSite” URLs that have come into the server since the server waslast started.

Domino.Command.SearchViewCounts the “SearchView” URLs that have come into the server since the server waslast started.

Domino.Command.TotalCounts the total number of URLs that have come into the server since the serverwas last started.

Domino.Command.UnknownCounts the total number of unknown URLs that have come into the server since theserver was last started.

Domino.Requests.Per1Hour.TotalReports the number of requests during the past hour.

106 Version 3.1.0

Domino.Requests.Per1Minute.TotalReports the number of requests during the past minute.

Domino.Requests.Per5Minute.TotalReports the number of requests during the last five minutes.

CLI SyntaxDomino –a <Attribute>

where:

<Attribute> The Domino monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "Domino" -a "Domino.Command.Total" "MailServerProfile"


3.S

tatisticsM

on

itors

Endpoint Monitor

DescriptionMonitors a Tivoli endpoint, indicating whether it is up or down.



Target EndpointsTivoli Endpoint


TMA Endpoint LabelType the label (or name) of the Tivoli Management Agent endpoint you want tomonitor. The endpoint label is assigned when the endpoint is created in the Tivolienvironment.

CLI SyntaxTMAEndpointStatus –a <TMAEndpoint>

where:

<TMAEndpoint>The label (or name) of the Tivoli Management Agent endpoint you want to monitor.The endpoint label is assigned when the endpoint is created in the Tivolienvironment.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "TMAEndpointStatus" -a "sales-dubai""MailServerProfile"

108 Version 3.1.0

Generic

DescriptionMonitors a process using a generic argument. Use this monitor to gather statistics for whichno monitor currently exists.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Generic monitor; a description of Generic Argument follows.

where:

Generic ArgumentThe process on which you want to gather statistics.

CLI SyntaxGeneric –a <Argument>

where:

<Argument> The generic argument to monitor.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "Generic" -a "server.foo" "MailServerProfile"


3.S

tatisticsM

on

itors

ICM

DescriptionMonitors Internet Cluster Manager (ICM) statistics.




Desktop OptionsThe following shows the Add Monitor to TME 10 Monitoring Profile dialog box for thismonitor; a description of each attribute follows.

Click the Attributes button to display the ICM Attribute dialog box for this monitor.

ICM.Command.Redirects.ClusterBusyReports the number of commands received when all servers are busy.

ICM.Command.Redirects.SuccessfulReports the number of successful redirects.

ICM.Command.Redirects.UnsuccessfulReports the number of unsuccessful redirects.

ICM.Command.TotalReports the total number of commands received.

ICM.Command.UnknownReports the number of unknown commands received.

ICM.Receive.ErrorReports the number of commands not received because of errors.

ICM.Requests.Per1Hour.TotalReports the number of requests received in the last hour.

ICM.Requests.Per1Minute.TotalReports the number of requests received in the last minute.

ICM.Requests.Per5Minutes.TotalReports the number of requests received in the last five minutes.

ICM.Sessions.Threads.BusyReports the number of ICM server tasks currently running.

110 Version 3.1.0

ICM.Sessions.Threads.IdleReports the number of ICM server tasks currently idle.

ICM.Sessions.TotalReports the total number of ICM server tasks run since server startup.

CLI SyntaxICM –a <Attribute>

where:

<Attribute> An ICM monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "ICM" -a "ICM.Receive.Error" "MailServerProfile"


3.S

tatisticsM

on

itors

IMAP

DescriptionStatistics related to Internet Mail Access Protocol (IMAP).





Click the Attributes button to display the IMAP Attribute dialog box for this monitor.

IMAP.Sessions.AcceptQueueDisplays the IMAP listener work queues of incoming sessions to be processed.

IMAP.Sessions.ActiveReports the current number of active IMAP server tasks.

IMAP.Sessions.Inbound.BytesReceivedReports the total number of bytes received by an IMAP server.

IMAP.Sessions.Inbound.BytesSentReports the total number of bytes sent by an IMAP server.

IMAP.Sessions.Inbound.Non-SSLReports the number of incoming IMAP server non-Secure Socket Layer (SSL)Transmission Control Protocol (TCP) connections.

IMAP.Sessions.Inbound.SSLReports the number of incoming IMAP server SSL connections.

IMAP.Sessions.Inbound.SSL.Bad_HandshakeReports the number of IMAP server SSL handshake failures.

IMAP.Sessions.Inbound.TotalReports the total number of incoming IMAP server connections (both SSL andnon-SSL).

IMAP.Sessions.PeakReports the peak number of IMAP server tasks since server startup.

112 Version 3.1.0

IMAP.Sessions.Threads.BusyReports the number of IMAP server tasks currently running.

IMAP.Sessions.Threads.IdleReports the number of IMAP server tasks currently idle.

IMAP.Sessions.TotalReports the total number of IMAP server tasks since server startup.

CLI SyntaxIMAP –a <Attribute>

where:

<Attribute> An IMAP monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "IMAP" -a "IMAP.Sessions.Active" "MailServerProfile"


3.S

tatisticsM

on

itors

LDAP

DescriptionMonitors statistics related to Lightweight Directory Access Protocol (LDAP).





Click the Attributes button to display the LDAP Attribute dialog box for this monitor.

LDAP.Sessions.AcceptQueueDisplays the Lightweight Directory Access Protocol (LDAP) listener work queues ofincoming sessions to be processed.

LDAP.Sessions.ActiveReports the current number of active LDAP server tasks.

LDAP.Sessions.Inbound.BytesReceivedReports the total number of bytes received by an LDAP server.

LDAP.Sessions.Inbound.BytesSentReports the total number of bytes sent by an LDAP server.

LDAP.Sessions.Inbound.Non-SSLReports the number of incoming LDAP server non-Secure Socket Layer (SSL)Transmission Control Protocol (TCP) connections.

LDAP.Sessions.Inbound.SSLReports the number of incoming LDAP server SSL connections.

LDAP.Sessions.Inbound.SSL.Bad_HandshakeReports the number of LDAP server SSL handshake failures.

LDAP.Sessions.Inbound.TotalReports the total number of incoming LDAP server connections (both SSL andnon-SSL).

LDAP.Sessions.PeakReports the peak number of LDAP server tasks since server startup.

114 Version 3.1.0

LDAP.Sessions.Threads.BusyReports the number of LDAP server tasks currently running.

LDAP.Sessions.Threads.IdleReports the number of LDAP server tasks currently idle.

LDAP.Sessions.TotalReports the total number of LDAP server tasks since server startup.

CLI SyntaxLDAP –a <Attribute>

where:

<Attribute> An LDAP monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "LDAP" -a "LDAP.Sessions.Active" "MailServerProfile"


3.S

tatisticsM

on

itors

LogQuery (Log.nsf)

DescriptionQueries a form in the log file for specified strings.

Upon scheduled execution, this monitor checks the Log.nsf documents for the time framespecified. The information returned includes the following:

¶ Found string

¶ Form name where the string was found.

¶ Field name where the string was found.

¶ Note ID where the string was found.





Channel NameThe channel name. If the channel has already been created (using a DistributedMonitoring command, for example), then enter the name of the existing channel.The name you specify for this channel must also be specified for all the LogQueryasynchronous monitors’ channel names. Avoid using this channel name for any othermonitors.

Form NameThe name of the form to search for in the log file. If no form is specified, all of thelog.nsf forms are searched.

Include StringA string to include in the search. Exclude string takes precedence over the includestring.

Exclude StringA string to exclude in the search. Exclude string takes precedence over the includestring.

116 Version 3.1.0

Time FrameThe time in minutes to search in the log file.

CLI SyntaxLogQuerySync –a <ChannelName> –a <FormName> –a <IncludeString>–a <ExcludeString> –a <TimeFrame>

where:

<ChannelName>The channel name. If the channel has already been created (using a DistributedMonitoring command, for example), then enter the name of the existing channel.The name you specify for this channel must also be specified for all the LogQueryasynchronous monitors’ channel names. Avoid using this channel name for any othermonitors.

<FormName>The name of the form to search for in the log file. If no form is specified, all of thelog.nsf forms are searched.

<IncludeString>A string to include in the search. Exclude string takes precedence over the includestring.

<ExcludeString>A string to exclude in the search. Exclude string takes precedence over the includestring.

<TimeFrame>The time in minutes to search in the log file.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "LogQuerySync" -a "LogQuery" -a "events" -a "week26"-a "month03" -a "60" "MailServerProfile"


3.S

tatisticsM

on

itors

LogQuery (Field Name)

DescriptionReturns the field name in which the requested strings were found in the Log.nsf file.





Channel NameThe channel name. The channel name specified as the Log Query (Log.nsf) channelname must also be specified as the channel name for all Log Query asynchronousmonitors. Avoid using this channel name for any other monitors.

CLI SyntaxLogQueryFieldNameAsync –a FieldName-<ChannelName>

where:

<ChannelName>The channel name. The channel name specified as the Log Query (Log.nsf) channelname must also be specified as the channel name for all Log Query asynchronousmonitors. Avoid using this channel name for any other monitors.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "LogQueryFieldNameAsync" -a "FieldName-Mail""MailServerProfile"

118 Version 3.1.0

LogQuery (Form Name)

DescriptionReturns the form name in which the requested strings were found in the Log.nsf file.






CLI SyntaxLogQueryFormNameAsync –a FormName-<ChannelName>

where:


CLI Examplewaddmon "Domino v5.0 Statistics Collection" "LogQueryFormNameAsync" -a "FormName-Mail""MailServerProfile"


3.S

tatisticsM

on

itors

LogQuery (Found string)

DescriptionReturns values for strings found statistics in the Log.nsf file.






CLI SyntaxLogQueryFoundStringAsync –a FoundString-<ChannelName>

where:


CLI Examplewaddmon "Domino v5.0 Statistics Collection" "LogQueryFoundStringAsync" -a "FoundString-Mail""MailServerProfile"

120 Version 3.1.0

LogQuery (Note ID)

DescriptionReturns the note ID in which the requested strings were found in Log.nsf file.






CLI SyntaxLogQueryNoteIDAsync –a NoteID-<ChannelName>

where:


CLI Examplewaddmon "Domino v5.0 Statistics Collection" "LogQueryNoteIDAsync" -a "NoteID-Mail""MailServerProfile"


3.S

tatisticsM

on

itors

Mail

DescriptionMonitors numeric statistics related to mail routing.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Mail monitor; a description of each attribute follows.

Click Attributes to display the Mail Attribute dialog and select the desired attribute.

Mail.AverageServerHopsReports the average number of server hops for mail delivery.

Mail.AverageSizeDeliveredReports the average size of mail delivered.

MAIL.DeadReports the number of dead (undeliverable) messages in MAIL.BOX.

MAIL.DeliveredReports the number of mail messages moved into MAIL.BOX by a router.

Mail.DeliveriesReports the count of actual mail items delivered (may be different fromMAIL.Delivered, which counts individual messages).

Mail.HoldNumber of mail messages in the message queue on hold.

Mail.IMAP.Cache.MsgInsertAttemptsReports the number of times an IMAP server attempted to insert a message into thecache.

Mail.IMAP.FindCacheAttemptedReports the number of times an IMAP server attempted to find a message in thecache.

Mail.IMAP.NumCacheHitsReports the number of messages the IMAP server found in the cache.

122 Version 3.1.0

Mail.IMAP.NumMsgInsertedInCacheNumber of messages the IMAP server inserted into cache.

Mail.MaximumServerHopsReports when the maximum number of server hops for mail delivery is reached.

Mail.MaximumSizeDeliveredReports when the maximum size of mail delivered is reached.

Mail.MinimumServerHopsReports when the minimum number of server hops for mail delivery is reached.

Mail.MinimumSizeDeliveredReports when the minimum size of mail delivered is reached.

Mail.PeakByteTransferRateReports the peak transfer rate.

Mail.PeakMessagesTransferredReports the peak number of messages transferred.

Mail.PeakMessageTransferRateReports the peak message transfer rate.

Mail.PeakTotalBytesTransferredReports the highest number of bytes transferred.

MAIL.TotalFailuresReports the total number of mail failures.

Mail.TotalKBTransferredReports the total of mail transferred in kilobytes.

MAIL.TotalRoutedReports the number of mail messages moved from MAIL.BOX to other servers fordelivery.

Mail.TotalRouted.SMTPReports the number of mail messages moved from MAIL.BOX via SMTP.

Mail.TotalRouted.NRPCReports the number of mail messages moved from MAIL.BOX via NRPC.

MAIL.TransferFailuresReports the number of mail messages the router was unable to transfer.

MAIL.TransferredReports the number of mail messages the router attempted to transfer.

MAIL.WaitingReports the number of outgoing mail messages in MAIL.BOX waiting for transfer.

MAIL.WaitingforDNSNumber of mail messages in MAIL.BOX waiting for DNS.

MAIL.WaitingRecipientsReports the number of mail messages in MAIL.BOX awaiting delivery into a user’smail files.


3.S

tatisticsM

on

itors

CLI SyntaxMail –a <Attribute>

where:

<Attribute> The Mail monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "Mail" -a "Mail.AverageSizeDelivered""MailServerProfile"

124 Version 3.1.0

MailByDest.<DestServerName>

DescriptionMonitors statistics related to mail addressed to the specified remote server.





Remote Server NameType the name of the remote server to which you are delivering mail.

MailByDest AttributeClick the Attributes button to display the MailByDest Attribute dialog box for thisargument.

Delivered Reports the number of mail messages delivered to the remote server.

TotalFailures Reports the number of mail delivery failures to the remote server.

TotalRouted Reports the total number of mail messages routed to the remoteserver.

CLI SyntaxMailByDest –a <RemoteServerName> –a <Attribute>

where:

<RemoteServerName>The name of the remote server to which you are delivering mail.

<Attribute>You can select from the following options:

Delivered Reports the number of mail messages delivered to the remote server.

TotalFailures Reports the number of mail delivery failures to the remote server.

TotalRouted Reports the total number of mail messages routed to the remoteserver.


3.S

tatisticsM

on

itors

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "MailByDest" -a "sales-dubai" -a "Delivered""MailServerProfile"

126 Version 3.1.0

Mailn.box

DescriptionMonitors the use of router mailbox databases.





MailBox FileClick the Attributes button to display the MailBoxFile dialog box. Select one of thefollowing options:

¶ Mail1

¶ Mail2

¶ Mail3

¶ Mail4

¶ Mail5

These entries correspond to router mailbox databases that are available to theDomino server.

Mailn.box attributeClick the Attributes button to display the Mailn.BoxFile attribute dialog box.Select one of the following options:

total Reports the total number of messages in the mailbox.

dead Reports the number of dead messages in the mailbox.

waiting Reports the number of messages awaiting transmission.

CLI SyntaxMailnBox –a <MailnBoxFile> –a <Mailn.box_Attribute>

where:


3.S

tatisticsM

on

itors

<MailnBoxFile>Enter one of the following options:

Mail1, Mail2, Mail3, Mail4, Mail5

These entries correspond to router mailbox databases that are available to theDomino server.

<Mailn.box_Attribute>Enter one of the following options:

total Reports the total number of messages in the mailbox.

dead Reports the number of dead messages in the mailbox.

waiting Reports the number of messages awaiting transmission.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "MailnBox" -a "Mail1" -a dead "MailServerProfile"

128 Version 3.1.0

Mail Trace

DescriptionTraces mail activities. Triggers the Tivoli addin to start/stop tracing the mail. A return valueof “0” indicates that the monitor executed successfully. The following information isgathered when Mail Trace is enabled:

¶ Mail Type

¶ Sender’s name

¶ Post date

¶ Number of recipients

¶ File attachment size

¶ Message Size

For incoming messages, the following data is also gathered:

¶ List of Domino hub names and the time spent in each hub

¶ Delivery date




Desktop OptionsThe following shows the Add Monitor to the TME 10 Distributed Monitoring Profiledialog box for this monitor; a description of each attribute follows.

Click the Attributes button to display the Mail Trace Attributes dialog box for thismonitor.

Mail Trace AttributesSelect one of the following options:

NONE Trace none of the mail.

Incoming Trace incoming mail.

Outgoing Trace outgoing mail.


3.S

tatisticsM

on

itors

Incoming/OutgoingTrace incoming and outgoing mail.

CLI SyntaxMailTrace –a <MailTraceAttribute>

where:

<MailTraceAttribute>Takes one of the following values:

None Trace none of the mail.

Incoming Trace incoming mail.

Outgoing Trace outgoing mail.

Incoming/OutgoingTrace incoming and outgoing mail.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "MailTrace" -a "Incoming" "MailServerProfile"

130 Version 3.1.0

Mail.Waiting.Async

DescriptionReports the number of mail messages waiting in the specified mailbox.





Channel NameThe channel name. You must assign this monitor the same channel name as theMailWaiting.Sync monitor. Avoid using this channel name for any other monitors.

CLI SyntaxMailWaitingAsync –a <ChannelName>

where:

<ChannelName>The channel name. You must assign this monitor the same channel name as theMailWaiting.Sync monitor. Avoid using this channel name for any other monitors.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "MailWaitingAsync" -a "Mail" "MailServerProfile"


3.S

tatisticsM

on

itors

Mail.Waiting.Sync

DescriptionMonitors the number of mail messages waiting in the specified mailbox.





Channel NameThe channel name. If you already created the channel (using a DistributedMonitoring command, for example), then enter the name of the existing channel.You must assign this monitor the same channel name as the MailWaiting.Asyncmonitor. Avoid using this channel name for any other monitors.

CLI SyntaxMailWaitingSync –a <ChannelName>

where:

<ChannelName>The channel name. If you already created the channel (using a DistributedMonitoring command, for example), then enter the name of the existing channel.You must assign this monitor the same channel name as the MailWaiting.Asyncmonitor. Avoid using this channel name for any other monitors.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "MailWaitingSync" -a "Mail" "MailServerProfile"

132 Version 3.1.0

Memory

DescriptionMonitors numeric statistics related to server system memory.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Memory monitor; a description of each attribute follows.

Click Attributes to display the Memory Attribute dialog and select the desired attribute.

Mem.AllocatedReports the total amount of memory allocated by the server.

Mem.Allocated.ProcessReports the total amount of non-shared memory allocated by individual processes.

Mem.Allocated.SharedReports the total amount of server memory allocated as shared memory.

Mem.FreeReports the amount of free memory available to the server.

Mem.FTVDKMaxBufferSizeUsedReports the maximum FTVDK buffer size used.

Note: You can use this attribute on Domino Version 5.0.x servers only.

Mem.PhysicalRamReports the total amount of physical memory on the server.

Mem.QuotaReports the maximum memory that can be allocated by the server.

Mem.SwapFile.SizeReports the size (in bytes) of a system swap file.


3.S

tatisticsM

on

itors

CLI SyntaxMemory –a <Attribute>

where:

<Attribute> The Memory monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "Memory" -a "Mem.Allocated" "MailServerProfile"

134 Version 3.1.0

MemoryAssessment

DescriptionMonitors the Domino Server Memory Assessment statistic by checking theNSF_Buffer_Pool_Size setting in the notes.ini file.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Agent monitor; a description of the Memory Attribute follows.

where:

Memory AttributeMem.Availability is the only attribute available at this time. Mem.Availabilityreturns the amount of available memory.

CLI SyntaxMemoryAssessment –a <MemoryAttribute>

where:

<MemoryAttribute>Mem.Availability is the only attribute available at this time. Mem.Availabilityreturns the amount of available memory.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "MemoryAssessment" -a "Mem.Availability""MailServerProfile"


3.S

tatisticsM

on

itors

MTA

DescriptionMonitors statistics related to various Mail Transfer Agents.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the MTA monitor; a description of each attribute follows.

Click Attributes to display the MTA Attribute dialog and select the desired attribute.

MTA.ccMail.DeadReports the total number of ccMail MTA transmission failures that result in an NDRor UMN.

MTA.ccMail.TotalKBTransferredReports the total number of ccMail MTA transfers in kilobytes (inbound andoutbound).

MTA.ccMail.TotalRoutedReports the total number of recipients of ccMail MTA messages routed (inbound andoutbound).

MTA.ccMail.TransferFailuresReports the number of ccMail MTA transmission failures that result in an NDR orUMN.

MTA.ccMail.TransferredReports the number of ccMail MTA transferred (inbound and outbound).

MTA.ccMail.WaitingReports the number of messages waiting in ccMail MTA work queues.

MTA.ccMail.WaitingRecipientsReports the number of responsible recipients for waiting mail held in inbound andoutbound work queues.

136 Version 3.1.0

MTA.Smtp.DeadReports the number of dead messages in the Simple Message Transmission Protocol(SMTP)/Multi-Purpose Internet Mail Extensions (MIME) MTA inbound andoutbound work queues.

MTA.Smtp.TotalKBTransferredReports the total number of SMTP/MIME MTA transfers in kilobytes (inbound andoutbound).

MTA.Smtp.TotalRoutedReports the total number of recipients of SMTP/MIME MTA messages routed(inbound and outbound).

MTA.Smtp.TransferFailuresReports the number of SMTP/MIME MTA transmission failures that resulted in anNDR or UMN.

MTA.Smtp.TransferredReports the number of SMTP/MIME MTA transferred (inbound and outbound).

MTA.Smtp.WaitingReports the number of messages waiting in SMTP/MIME MTA work queues.

MTA.Smtp.WaitingRecipientsReports the number of responsible recipients for waiting mail held in inbound andoutbound work queues.

MTA.X400.DeadReports the number of dead messages in X400 MTA inbound and outbound workqueues.

MTA.X400.TotalKBTransferredReports the total number of X400 MTA transfers in kilobytes (inbound andoutbound).

MTA.X400.TotalRoutedReports the total number of recipients of X400 MTA messages routed (inbound andoutbound).

MTA.X400.TransferFailuresReports the number of X400 MTA transmission failures that resulted in an NDR orUMN.

MTA.X400.TransferredReports the number of X400 MTA transferred (inbound and outbound).

MTA.X400.WaitingReports the number of messages waiting in X400 MTA work queues.

MTA.X400.WaitingRecipientsReports the number of responsible recipients for waiting mail held in inbound andoutbound work queues.

CLI SyntaxMTA –a <Attribute>

where:

<Attribute> The MTA monitor attribute.


3.S

tatisticsM

on

itors

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "MTA" -a "MTA.ccMail.Dead" "MailServerProfile"

138 Version 3.1.0

NET.<PortName>

DescriptionMonitors Internet-related statistics.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the NET.<PortName> monitor; a description of each attribute follows.

DeviceSelect the device you would like to monitor from the dialog displayed by clickingthe Attributes button to the right of this text box.

StatisticSelect the statistic you want to monitor from the dialog displayed by clicking theAttributes button to the right of this text box. The statistics are:










3.S

tatisticsM

on

itors



CLI SyntaxNET.<PortName> –a Net.<Device><Statistic>

where:

<PortName>The name of the port from which to collect the statistics.

<Device>The device to monitor from the following list: COM1, COM2, COM3, COM4,COM5, LAN0, LAN1, LAN2, SPX, TCPIP, TCP, VINES

<Statistic>The information received from the device. The choices are:











CLI Examplewaddmon "Domino v5.0 Statistics Collection" "NET.Port1" -a "Net.COM1.BytesSent""MailServerProfile"

140 Version 3.1.0

NETBIOS.<PortName>

DescriptionMonitors NetBIOS statistics for each port that is specified in the port name.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the NETBIOS.<PortName> monitor; a description of each attribute follows.

Click Attributes to display the NETBIOS Monitor Port Attribute dialog and select thedesired attribute.

Note: The statistics described in the following attributes can be collected from the followingports: LAN0, LAN1, LAN2. The port is listed before the attribute on the NETBIOSMonitor Port Attribute dialog.

NETBIOS Monitor Port AttributeSelect the port on which to run this monitor from the dialog displayed by clickingthe Attributes button to the right of this text box.

NetBios Monitor AttributeSelect the attribute you want to monitor from the dialog displayed by clicking theAttributes button to the right of this text box. The attributes are:

CommandBlocks.AvailableReports the number of Network Basic Input/Output System (NetBIOS)command blocks available.






3.S

tatisticsM

on

itors



Rec.Res.ExhaustedReports the number of exhausted NetBIOS resources.






Transmissions.RetriedReports the number of NETBIOS transmissions retried.

CLI SyntaxNETBIOS –a NETBIOS.<Port>.<Statistic>

where:

<Port>The name of the port from which to collect the statistics from the following options:LAN0, LAN1, LAN2.

<Statistic>The type of information you want to receive from the device from the followingchoices:

CommandBlocks.AvailableReports the number of Network Basic Input/Output System (NetBIOS)command blocks available.







142 Version 3.1.0

Receiver.Resources.ExhaustedReports the number of exhausted NetBIOS resources.







CLI Examplewaddmon "Domino v5.0 Statistics Collection" "NETBIOS" -a "NETBIOS.LAN1.Transmissions.Retried""MailServerProfile"


3.S

tatisticsM

on

itors

nntp

DescriptionMonitors statistics related to a Network News Transport Protocol (NNTP) server (Dominonews server).




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the nntp monitor; a description of each attribute follows.

Click Attributes to display the NNTP Monitor Attribute dialog and select the desiredattribute.

NNTP.Articles.PostedReports the number of news articles posted to the NNTP server.

NNTP.Articles.SentReports the number of news articles sent from the NNTP server.

NNTP.Bytes.ReceivedReports the number of bytes received by the NNTP server.

NNTP.Bytes.SentReports the number of bytes sent from the NNTP server.

NNTP.Pull.Articles.FailedReports the number of failed news article transfers received by the NNTP serverduring pull feeds.

NNTP.Pull.Articles.OfferedReports the number of news articles offered by the NNTP server during pull feeds.

NNTP.Pull.Articles.RequestedReports the number of news articles requested from the NNTP server during pullfeeds.

NNTP.Pull.Articles.TransferredReports the number of news articles transferred by the NNTP server during pullfeeds.

144 Version 3.1.0

NNTP.Push.Articles.FailedReports the number of failed news article transfers by the NNTP server during pushfeeds.

NNTP.Push.Articles.OfferedReports the number of failed news articles offered by the NNTP server during pushfeeds.

NNTP.Push.Articles.RequestedReports the number of news articles requested from the NNTP server during pushfeeds.

NNTP.Push.Articles.TransferredReports the number of news articles transferred by the NNTP server during pushfeeds.

NNTP.Sessions.Accept.QueueReports the number of incoming sessions to be processed in the NNTP listener workqueue.

NNTP.Sessions.ActiveReports the current number of NNTP server tasks.

NNTP.Sessions.Inbound.BytesReceivedReports the total number of bytes received by a NNTP server.

NNTP.Sessions.Inbound.BytesSentReports the total number of bytes sent by a NNTP server.

NNTP.Sessions.Inbound.Non-SSLReports the number of NNTP server inbound non-Secure Socket Layer (SSL)connections.

NNTP.Sessions.Inbound.SSLReports the number of NNTP server inbound SSL connections.

NNTP.Sessions.Inbound.SSL.Bad_HandshakeReports the number of NNTP server SSL handshake failures.

NNTP.Sessions.Inbound.TotalReports the total number of NNTP server inbound connections (SSL and non-SSL).

NNTP.Sessions.Outgoing.non-SSLReports the number of outgoing non-SSL TCP connections.

NNTP.Sessions.Outgoing.SSLReports the number of outgoing SSL TCP connections.

NNTP.Sessions.PeakReports the peak number of NNTP server tasks since server startup.

NNTP.Sessions.Threads.BusyReports the number of NNTP server tasks that are currently running.

NNTP.Sessions.Threads.IdleReports the number of NNTP server tasks that are currently idle.

NNTP.Sessions.TotalReports the total number of NNTP server tasks since server startup.


3.S

tatisticsM

on

itors

CLI SyntaxNNTP –a <Attribute>

where:

<Attribute> The NNTP monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "NNTP" -a "NNTP.Sessions.Peak" "MailServerProfile"

146 Version 3.1.0


DescriptionMonitors statistics related to a remote NNTP server.

Domino Versions Supported4.6.x, 5.0.x



Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the NNTP.<RemoteServerName> monitor; a description of the Remote Server Nameattribute follows.

where:

Remote Server NameThe name of the server you want to monitor.

NNTP AttributeSelect the attribute you want to monitor from the dialog displayed by clicking theAttributes button to the right of this text box. The attributes are:

Articles.PostedReports the number of news articles posted to the NNTP server.

Articles.SentReports the number of news articles sent from the NNTP server.

Bytes.ReceivedReports the number of bytes received by the NNTP server.

Bytes.SentReports the number of bytes sent from the NNTP server.

Pull.Articles.FailedReports the number of failed news article transfers received by the NNTPserver during pull feeds.

Pull.Articles.OfferedReports the number of news articles requested from the NNTP server duringpull feeds.


3.S

tatisticsM

on

itors

Pull.Articles.RequestedReports the number of news articles requested from the NNTP server duringpull feeds.

Pull.Articles.TransferredReports the number of news articles transferred by the NNTP server duringpull feeds.

Push.Articles.FailedReports the number of failed news article transfers by the NNTP serverduring push feeds.

Push.Articles.OfferedReports the number of failed news articles offered by the NNTP serverduring push feeds.

Push.Articles.RequestedReports the number of news articles requested from the NNTP server duringpush feeds.

Push.Articles.TransferredReports the number of news articles transferred by the NNTP server duringpush feeds.

CLI SyntaxNNTP.<RemoteServerName>.<Attribute>

where:

<RemoteServerName>The name of the server you want to monitor.

<Attribute>The NNTP Attribute you want to monitor.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "NNTP.jerry.Push.Articles.Transferred""MailServerProfile"

148 Version 3.1.0

Object

DescriptionMonitors statistics related to the shared mail store.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Object monitor; a description of each attribute follows.

Click Attributes to display the Object Monitor Attribute dialog and select the desiredattribute.

Object Monitor AttributeReports the number of objects shared by xx users (where xx represents the number ofusers). You may choose a specific number from 1–20 or choose the optionObject.Mailobj.NSF.SharedBy.Greater, which specifies a number of users greaterthan 20.

CLI SyntaxObject –a <Attribute>

where:

<Attribute> The object monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "Object" -a "Object.Mailobj.NSF.SharedBy.18""MailServerProfile"


3.S

tatisticsM

on

itors

POP3

DescriptionMonitors statistics related to Post Office Protocol 3 (POP3).




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the POP3 monitor; a description of each attribute follows.

Click Attributes to display the POP3 Attribute dialog and select the desired attribute.

POP3.Sessions.Accept.QueueReports the number of incoming sessions to be processed in the POP3 listener workqueue.

POP3.Sessions.ActiveReports the current number of POP3 server tasks.

POP3.Sessions.Inbound.BytesReceivedReports the total number of bytes received by a POP3 server.

POP3.Sessions.Inbound.BytesSentReports the total number of bytes sent by a POP3 server.

POP3.Sessions.Inbound.Non-SSLReports the number of inbound POP3 server Transmission Control Protocol (TCP)connections.

POP3.Sessions.Inbound.SSLReports the number of inbound POP3 server SSL connections.

POP3.Sessions.Inbound.SSL.Bad_HandshakeReports the number of POP3 server SSL handshake failures.

POP3.Sessions.Inbound.TotalReports the number of inbound POP3 server connections (SSL and non-SSL).

POP3.Sessions.PeakReports the peak number of POP3 server tasks since server startup.

150 Version 3.1.0

POP3.Sessions.Threads.BusyReports the number of POP3 server tasks currently running.

POP3.Sessions.Threads.IdleReports the number of POP3 tasks currently idle.

POP3.Sessions.TotalReports the total number of POP3 server tasks since server startup.

CLI SyntaxPOPthree –a <Attribute>

where:

<Attribute> The POP3 monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "POPthree" -a "POPThree.Sessions.Peak""MailServerProfile"


3.S

tatisticsM

on

itors


DescriptionMonitors mail probe response time.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor this monitor; a description of each attribute follows.

ServerName AttributeThe name of the server.

Suffix The only attribute currently supported is ResponseTime.

CLI SyntaxQOS –a <attribute>

where

<attribute>The QOS attribute QOS.Mail.ISpy.<servername>.ResponseTime.

CLI Examplewaddmon "Domino v5.0 Real Time Collection" "QOS" -a "QOS.Mail.ISpy.brisbane.ResponseTime"

152 Version 3.1.0

Replication

DescriptionMonitors numeric statistics related to database replication.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Replication monitor; a description of each attribute follows.

Click Attributes to display the Replication Attribute dialog and select the desired attribute.

Replica.Cluster.CacheHandlesReports the number of handles cached by a cluster.

Replica.Cluster.Docs.AddedReports the number of documents added by a cluster replicator.

Replica.Cluster.Docs.DeletedReports the number of documents deleted by a cluster replicator.

Replica.Cluster.Docs.UpdatedReports the number of documents updated by a cluster replicator.

Replica.Cluster.FailedReports the number of failed replications since server startup.

Replica.Cluster.Files.LocalReports the number of cluster replicas on this server.

Replica.Cluster.Files.RemoteReports the number of cluster replicas on other servers in the cluster.

Replica.Cluster.Retry.SkippedReports the number of times the cluster replicator did not attempt replicationbecause the server was unreachable.

Replica.Cluster.Retry.WaitingReports the number of replicas currently waiting for replication retry attempts.

Replica.Cluster.SecondsOnQueueReports the time in seconds that the cluster replicator was on queue.


3.S

tatisticsM

on

itors

Replica.Cluster.SecondsOnQueue.AvgReports the average time in seconds that the cluster replicator was on queue.

Replica.Cluster.SecondsOnQueue.MaxReports the maximum time in seconds that the cluster replicator was on queue.

Replica.Cluster.ServersReports the number of other servers in the cluster that are receiving replicationsfrom this server.

Replica.Cluster.SessionBytes.InReports the number of incoming bytes to the cluster replicator.

Replica.Cluster.SessionBytes.OutReports the number of outgoing bytes to the cluster replicator.

Replica.Cluster.SuccessfulReports the number of successful replications since server startup.

Replica.Cluster.WorkQueueDepthReports the current number of modified databases in the queue that are waiting to bereplicated by the cluster replicator to other servers.

Replica.Cluster.WorkQueueDepth.AvgReports the average number of modified databases in the queue that are waiting tobe replicated by the cluster replicator to other servers.

Replica.Cluster.WorkQueueDepth.MaxReports the maximum number of modified databases in the queue that are waiting tobe replicated by the cluster replicator to other servers.

Replica.Docs.AddedReports the number of documents added to the server’s databases by replication.

Replica.Docs.DeletedReports the number of documents deleted from the server’s databases by replication.

Replica.Docs.UpdatedReports the number of documents updated in the server’s databases by replication.

Replica.FailedReports the number of attempted replications that returned an error.

Replica.SuccessfulReports the number of replication attempts that returned no errors.

CLI SyntaxReplication –a <Attribute>

where:

<Attribute> The Replication monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "Replication" -a "Replica.Successful""MailServerProfile"

154 Version 3.1.0

Replication check

DescriptionCompares actual replications to scheduled replications during the time frame specified.




Desktop OptionsThe following shows the Add Monitor to TME 10 Monitoring Profile dialog box for thismonitor; a description of each field follows.

Channel NameThe channel name. If you already created the channel (using a DistributedMonitoring command, for example), then enter the name of the existing channel.The name you specify for this channel must also be specified for all Replicationasynchronous monitor channel names. Avoid using this channel name for any othermonitors.

Include StringThe string to include in the replication check. If specified, affects only theReplication (Replication Events) and Replication (Database Replication info)asynchronous monitors. Exclude string takes precedence over include string.

Exclude StringThe string to exclude in the replication check. If specified, affects only theReplication (Replication Events) and Replication (Database Replication info)asynchronous monitors. Exclude string takes precedence over include string.

Time FrameThe time frame to include in the check. The time frame is the number of minutesbetween the running of the monitor and the last replication.

CLI SyntaxReplicationCheckSync –a <ChannelName> –a <IncludeString> –a <ExcludeString>–a <TimeFrame>

where:

<ChannelName>The channel name. If you already created the channel (using a Distributed


3.S

tatisticsM

on

itors

Monitoring command, for example), then enter the name of the existing channel.The name you specify for this channel must also be specified for all Replicationasynchronous monitor channel names. Avoid using this channel name for any othermonitors.

<IncludeString>The string to include in the replication check.

<ExcludeString>The string to exclude in the replication check.

<TimeFrame>The time frame to include in the check. The time frame is the number of minutesbetween the running of the monitor and the last replication.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "ReplicationCheckSync" -a "Mail" -a "week45"-a "week02" -a 60 "MailServerProfile"

156 Version 3.1.0

Replication (Database Replication Info)

DescriptionReturns replication database information.





Channel NameThe channel name you specified for the Replication check monitor. This channelname must also be specified as the channel name for all Replication asynchronousmonitors. Avoid using this channel name for any other monitors.

CLI SyntaxReplicationDBInfoAsync –a DBInfo-<ChannelName>

where:

<ChannelName>The channel name you specified for the Replication check monitor. This channelname must also be specified as the channel name for all Replication asynchronousmonitors. Avoid using this channel name for any other monitors.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "ReplicationDBInfoAsync" -a "DBInfo-Mail""MailServerProfile"


3.S

tatisticsM

on

itors

Replication (Duration)

DescriptionReturns the duration in time of the replication.






CLI SyntaxReplicationDurationAsync –a Duration-<ChannelName>

where:


CLI Examplewaddmon "Domino v5.0 Statistics Collection" "ReplicationDurationAsync" -a "Duration-Mail""MailServerProfile"

158 Version 3.1.0

Replication (End Time)

DescriptionReturns the replication end time.






CLI SyntaxReplicationEndTimeAsync –a EndTime-<ChannelName>

where:


CLI Examplewaddmon "Domino v5.0 Statistics Collection" "ReplicationEndTimeAsync" -a "EndTime-Mail""MailServerProfile"


3.S

tatisticsM

on

itors

Replication (Hit/Miss/Manual)

DescriptionIndicates whether the replication occurred as scheduled, did not occur as scheduled, or wasperformed manually.






CLI SyntaxReplicationHitMissAsync –a HitMiss-<ChannelName>

where:


CLI Examplewaddmon "Domino v5.0 Statistics Collection" "ReplicationHitMissAsync" -a "HitMiss-Mail""MailServerProfile"

160 Version 3.1.0

Replication (ID)

DescriptionReturns the unique ID assigned to the replication occurrence.






CLI SyntaxReplicationIDAsync –a REPL_ID-<ChannelName>

where:


CLI Examplewaddmon "Domino v5.0 Statistics Collection" "ReplicationIDAsync" -a "REPL_ID-Mail""MailServerProfile"


3.S

tatisticsM

on

itors

Replication (Remote server name)

DescriptionReturns the name of the remote server in the replication.






CLI SyntaxReplicationRemoteSRVAsync –a RemoteSRV-<ChannelName>

where:


CLI Examplewaddmon "Domino v5.0 Statistics Collection" "ReplicationRemoteSRVAsync" -a "RemoteSRV-Mail""MailServerProfile"

162 Version 3.1.0

Replication (Replication Events)

DescriptionReturns a list of the events that occurred during the replication.






CLI SyntaxReplicationEventsAsync –a Events-<ChannelName>

where:


CLI Examplewaddmon "Domino v5.0 Statistics Collection" "ReplicationEventsAsync" -a "Events-Mail""MailServerProfile"


3.S

tatisticsM

on

itors

Replication (Server Name)

DescriptionReturns the name of the source server in the replication.






CLI SyntaxReplicationServerNameAsync –a ServerName-ChannelName>

where:


CLI Examplewaddmon "Domino v5.0 Statistics Collection" "ReplicationServerNameAsync" -a "ServerName-Mail""MailServerProfile"

164 Version 3.1.0

Replication (server name that initiated replication)

DescriptionReturns the name of the server initiating the replication.






CLI SyntaxReplicationInitiatedByAsync –a InitiatedBy-<ChannelName>

where:


CLI Examplewaddmon "Domino v5.0 Statistics Collection" "ReplicationInitiatedByAsync" -a "InitiatedBy-Mail""MailServerProfile"


3.S

tatisticsM

on

itors

Replication (Start Time)

DescriptionReturns the replication start time.






CLI SyntaxReplicationStartTimeAsync –a StartTime-<ChannelName>

where:


CLI Examplewaddmon "Domino v5.0 Statistics Collection" "ReplicationStartTimeAsync" -a "StartTime-Mail""MailServerProfile"

166 Version 3.1.0

Server

DescriptionMonitors Domino server statistics.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Server monitor; a description of each attribute follows.

Click Attributes to display the Server Attribute dialog and select the desired attribute.

Server.AvailabilityIndexReports the current percentage index of server availability. Zero (0) indicates noavailable resources; a value of 100 indicates complete server availability.

Server.AvailabilityThresholdReports the current setting of the availability threshold of a server. When theavailability index of a server drops below its availability threshold, the serverbecomes busy.

Server.BusyTimeQuery.ReceivedCountReports the number of queries to busy time in scheduling.

Server.BusyTimeQuery.Returned.Objects.SchedulesReports the number of responses to queries to busy time in scheduling.

Server.Cluster.AvailabilityIndexReports the current percentage index of server availability. Zero (0) indicates noavailable resources; a value of 100 indicates complete server availability.

Server.Cluster.AvailabilityThresholdReports the current setting of the availability threshold of a server. When theavailability index of that server drops below its availability threshold, the serverbecomes busy.

Server.Cluster.OpenRedirects.FailoverByPath.SuccessfulReports the number of times a server successfully redirected a client to anothercluster member after the client failed to open a database by path name.


3.S

tatisticsM

on

itors

Server.Cluster.OpenRedirects.FailoverByPath.UnsuccessfulReports the number of times a server was not able to redirect a client to anothercluster member after the client failed to open a database by path name.

Server.Cluster.OpenRedirects.Failover.SuccessfulReports the number of times that a server successfully redirected a client to anothercluster member after the client failed to open a database by replica ID.

Server.Cluster.OpenRedirects.Failover.UnsuccessfulReports the number of times that a server was not able to redirect a client to anothercluster member after the client failed to open a database by replica ID.

Server.Cluster.OpenRedirects.LoadBalanceByPath.SuccessfulReports the number of times a server successfully redirected a client to anothercluster member after the client tried to open a database by path name when theserver was busy.

Server.Cluster.OpenRedirects.LoadBalanceByPath.UnsuccessfulReports the number of times a server was not able to redirect a client to anothercluster member after the client tried to open a database by path name when theserver was busy.

Server.Cluster.OpenRedirects.LoadBalance.SuccessfulReports the number of times a server successfully redirected a client to anothercluster member after the client tried to open a database by replica ID when theserver was busy.

Server.Cluster.OpenRedirects.LoadBalance.UnsuccessfulReports the number of times a server was unable to redirect a client to anothercluster member after the client tries to open a database by replica ID when theserver was busy.

Server.Cluster.OpenRequest.ClusterBusyReports the number of times a client tried to open a database on the server when theserver was busy and, on every available member.

Server.Cluster.OpenRequest.DatabaseOutOfServiceReports the number of times a client tried to open a database that is marked as outof service on the server.

Server.Cluster.OpenRequest.LoadBalancedReports the number of times a client tries to open a database on the server, when theserver is busy and on every available member.

Server.Cluster.ProbeCountReports the number of times a server completed a probe request of the other clustermembers.

Server.Cluster.ProbeErrorReports the number of times that a server receives an error when probing anotherserver.

Server.Cluster.ProbeTimeoutReports the interval (in minutes) at which the intracluster probe or cluster memberheartbeat occurs.

Server.Cluster.Trans.IntervalAvgTimeReports the average time interval of cluster transactions.

168 Version 3.1.0

Server.Cluster.Trans.IntervalInMinutesReports the interval between cluster transactions in minutes.

Server.Cluster.Trans.IntervalInSecondsReports the interval between cluster transactions in seconds.

Server.Cluster.Trans.IntervalsUseInAvgReports the current setting for the number of intervals used to capture transactiondata used to calculate workload balance.

Server.Cluster.Trans.LastIntervalAvgTimeReports the last average interval time of cluster transactions.

Server.Cluster.Trans.NormalizeValueReports the current setting of acceptable average transaction time for a server inmilliseconds.

Server.Cluster.Trans.RunningCountReports the number of cluster transactions.

Server.MinIdleDisconnectReports the minimum number of minutes for disconnect.

Server.OpenRequest.MaxusersReports the number of open requests for maximum users.

Server.OpenRequest.PreV4ClientsReports the number of open requests for pre-R4 clients.

Server.OpenRequest.RestrictedReports the number of open requests for restricted clients.

Server.OpenRequest.V4ClientsReports the number of open requests for R4 clients.

Server.Ports.RS232Reports the number of RS232 serial ports on the server.

Server.Sessions.DroppedReports the number of sessions dropped in mid-transaction.

Server.TasksReports the number of tasks currently running on the server.

Server.Trans.PerMinuteReports the number of server transactions in the last minute.

Server.Trans.PerMinute.PeakReports the highest number of transactions during a one-minute interval.

Server.Trans.TotalReports the number of transactions processed since the server started.

Server.UsersReports the number of users with open sessions on the server.

Server.Users.1MinPeakReports the peak number of users over one minute.

Server.Users.5MinPeakReports the peak number of users over five minutes.


3.S

tatisticsM

on

itors

Server.Users.PeakReports the peak number of concurrent users since the server was started.

Server.WorkThreadsReports the maximum number of concurrent transactions to create.

CLI SyntaxServer –a <Attribute>

where:

<Attribute> The Server monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "Server" -a "Server.Trans.Total" "MailServerProfile"

170 Version 3.1.0

Server Availability

DescriptionMonitors server availability.




Desktop OptionsNone.

CLI SyntaxDominoServerAvailable

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "DominoServerAvailable" "MailServerProfile"


3.S

tatisticsM

on

itors

Server.Health.Async

DescriptionReturns information on the server’s health, such as the name of each server task and whetherit is Up, Down, or Hung.





Channel NameThe channel name. You must assign this monitor the same channel name as theServer.Health.Sync monitor. Avoid using this channel name for any other monitors.

CLI SyntaxServerHealthAsync –a <ChannelName>

where:

<ChannelName>The channel name. You must assign this monitor the same channel name as theServer.Health.Sync monitor. Avoid using this channel name for any other monitors.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "ServerHealthAsync" -a "Mail" "MailServerProfile"

172 Version 3.1.0

Server.Health.Sync

DescriptionMonitors the server’s health. Checks the ServerTasks line of the notes.ini file and identifiestasks that should run.





Channel NameThe channel name. If you already created the channel (using a DistributedMonitoring command, for example), then enter the name of the existing channel.You must assign this monitor the same channel name as the Server.Health.Asyncmonitor. Avoid using this channel name for any other monitors.

Server Task NamesThe name any custom addin task you wish to monitor. The name of the task must beentered as it appears in your notes.ini file, under servertasks. Multiple addins canbe monitored by separating the entries with commas (,).

Server Task Friendly NamesThe name of the task as seen on the server console.

CLI SyntaxServerHealthSync –a <ChannelName> –a <ServerTaskNames>–a <ServerTaskFriendlyNames>

where:

<ChannelName>The channel name. If you already created the channel (using a DistributedMonitoring command, for example), then enter the name of the existing channel.You must assign this monitor the same channel name as the Server.Health.Asyncmonitor. Avoid using this channel name for any other monitors.

<ServerTaskNames>The name of any custom addin task you wish to monitor. The name of the task must


3.S

tatisticsM

on

itors

be entered as it appears in your notes.ini file, under servertasks. Multiple addinscan be monitored by separating the entries with commas (,).

<ServerTaskFriendlyNames>The name of the task as seen on the server console.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "ServerHealthSync" -a "Mail"-a "MailFrequency" -a "MailTime" "MailServerProfile"

174 Version 3.1.0

SMTP

DescriptionMonitors statistics related to Simple Mail Transfer Protocol (SMTP).




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the SMTP monitor; a description of each attribute follows.

Click Attributes to display the SMTP Attribute dialog and select the desired attribute.

SMTP.MessagesProcessedReports the number of Simple Mail Transfer Protocol (SMTP) messages processed.

SMTP.Sessions.Accept.QueueReports the number of SMTP listener work queues of incoming sessions to beprocessed.

SMTP.Sessions.ActiveReports the number of active SMTP server tasks.

SMTP.Sessions.Inbound.BytesReceivedReports the number of bytes received by an SMTP server.

SMTP.Sessions.Inbound.BytesSentReports the number of bytes sent by an SMTP server.

SMTP.Sessions.Inbound.Non-SSLReports the number of SMTP server inbound TCP connections (non-SSL).

SMTP.Sessions.Inbound.SSLReports the number of SMTP server inbound SSL connections.

SMTP.Sessions.Inbound.SSL.Bad_HandshakeReports the number of SMTP server SSL handshake failures.

SMTP.Sessions.Inbound.TotalReports the total number of SMTP server inbound connections (SSL and non-SSL).

SMTP.Sessions.PeakReports the peak number of SMTP server tasks since server startup.


3.S

tatisticsM

on

itors

SMTP.Sessions.Threads.BusyReports the number of SMTP server tasks currently running.

SMTP.Sessions.Threads.IdleReports the number of SMTP server tasks currently idle.

SMTP.Sessions.TotalReports the total number of SMTP server tasks since server startup.

CLI SyntaxSMTP –a <Attribute>

where:

<Attribute> The SMTP monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "SSMTP" -a "SMTP.Session.Peak" "MailServerProfile"

176 Version 3.1.0

SMTPMTA

DescriptionMonitors statistics related to the SMTP Mail Transfer Agent.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the SMTPMTA monitor; a description of each attribute follows.

Click Attributes to display the SMTPMTA Attribute dialog and select the desired attribute.

SMTPMTA.ConvFailuresReports the total number of Simple Message Transfer Protocol Message TransferAgents (SMTP MTA) conversion failures.

SMTPMTA.DeadReports the number of dead SMTP MTA messages.

SMTPMTA.DeliveredReports the number of SMTP MTA messages delivered.

SMTPMTA.HighInBoundReports the highest number of inbound processes.

SMTPMTA.HighOutBoundReports the highest number of outbound processes.

SMTPMTA.InBoundBytesReports the number of inbound bytes.

SMTPMTA.InBoundSizeReports the size of the largest inbound message.

SMTPMTA.OutBoundBytesReports the number of outbound bytes.

SMTPMTA.OutBoundSizeReports the size of the largest outbound message.

SMTPMTA.TotalRoutedReports the total number of SMTP MTA messages routed.


3.S

tatisticsM

on

itors

SMTPMTA.TransFailuresReports the number of SMTP MTA transmission failures.

SMTPMTA.TransferredReports the number of SMTP MTA messages transferred.

SMTPMTA.WaitingReports the number of SMTP MTA messages waiting.

SMTPMTA.WaitingConvReports the amount of mail waiting to be converted.

SMTPMTA.WaitingRecipientsReports the amount of mail waiting to be delivered.

SMTPMTA.WaitingTransReports the amount of mail waiting to be transferred.

CLI SyntaxSMTPMTA –a <Attribute>

where:

<Attribute> The SMTPMTA monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "SMTPMTA" -a "SMTPMTP.Dead" "MailServerProfile"

178 Version 3.1.0

SMTP.<Name>

DescriptionMonitors statistics related to the named SMTP device.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the SMTP.<Name> monitor; a description of the attributes follows.

where:

SMTP DeviceThe name of the device you want to monitor. The following statistics are currentlyimplemented: MsgSizeKBytes, MsgRecipients, or SessionDuration.

SMTP AttributeSelect the attribute you want to monitor from the dialog displayed by clicking theAttributes button to the right of this text box. The attributes are:

Ave Reports the average number of SMTP tasks running at the same timeon the selected device.

Count Reports the number of SMTP tasks currently running on the selecteddevice.

Max Reports the peak number of SMTP tasks running at the same timesince device startup.

Total Reports the total number of SMTP tasks run since device startup.

Min Reports the lowest number of SMTP tasks running at the same timesince device startup.

CLI SyntaxSMTP.<Name>.<Attribute>

where:


3.S

tatisticsM

on

itors

<Name>The name of the device to monitor. The following statistics are currentlyimplemented: MsgSizeKBytes, MsgRecipients, or SessionDuration.

<Attribute>The SMTP attribute to monitor. The attributes are:

Ave Reports the average number of SMTP tasks running at the same timeon the selected device.

Count Reports the number of SMTP tasks currently running on the selecteddevice.

Max Reports the peak number of SMTP tasks running at the same timesince device startup.

Total Reports the total number of SMTP tasks run since device startup.

Min Reports the lowest number of SMTP tasks running at the same timesince device startup.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "SMTP.MsgRecipients.Ave" "MailServerProfile"

180 Version 3.1.0

SPIN

DescriptionMonitors statistics related to SPIN. (For Lotus Corporation internal use only.)




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the SPIN monitor; a description of each attribute follows.

Click Attributes to display the SPIN Attribute dialog and select the desired attribute.

SPIN.AvtIterToHitReports the average ratio of SPIN lock iterations to hits.

SPIN.DelaysReports the count of SPIN lock delays.

SPIN.DelaysMsecsReports the duration of SPIN lock delays in microseconds.

SPIN.FRWSemGetReadExtReports the SPIN lock FRW semaphore read.

SPIN.FRWSemPutReadExtReports the SPIN lock FRW semaphore put.

SPIN.HitsReports the number of SPIN lock hits.

SPIN.MaxDelayMaskReports the SPIN lock maximum delay mask.

SPIN.MaxDelayMsecsReports the SPIN lock maximum delay in microseconds.

CLI SyntaxSPIN –a <Attribute>

where:

<Attribute> The SPIN monitor attribute.


3.S

tatisticsM

on

itors

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "SPIN" -a "SPIN.Delays" "MailServerProfile"

182 Version 3.1.0

Stalled.Mail.Async

DescriptionReturns the number of seconds mail is stalled in each specified mail box. Stalled mail ismail that stays in the specified mailbox for more than the Time in Queue you specified inthe Stalled.Mail.Sync monitor.





Channel NameThe channel name. You must assign this monitor the same channel name as theStalled.Mail.Sync monitor. Avoid using this channel name for any other monitors.

CLI SyntaxStalledMailAsync –a <ChannelName>

where:

<ChannelName>The channel name. You must assign this monitor the same channel name as theStalled.Mail.Sync monitor. Avoid using this channel name for any other monitors.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "StalledMailAsync" -a "Mail" "MailServerProfile"


3.S

tatisticsM

on

itors

Stalled.Mail.Sync

DescriptionChecks for stalled mail in the specified mailboxes. Stalled mail is mail that stays in thespecified mailbox for more time than specified in the Time in Queue argument for thismonitor.





Channel NameThe channel name. If you already created the channel (using a DistributedMonitoring command, for example), then enter the name of the existing channel.You must assign this monitor the same channel name as the Stalled.Mail.Asyncmonitor. Avoid using this channel name for any other monitors.

Time in Queue (seconds)The time, in seconds, used to determine if a message is stalled.

CLI SyntaxStalledMailSync –a <ChannelName> –a <TimeInQueue>

where:

<ChannelName>The channel name. If you already created the channel (using a DistributedMonitoring command, for example), then enter the name of the existing channel.You must assign this monitor the same channel name as the Stalled.Mail.Asyncmonitor. Avoid using this channel name for any other monitors

<TimeInQueue>The time, in seconds, used to determine if a message is stalled.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "StalledMailSync" -a "Mail" -a 10 "MailServerProfile"

184 Version 3.1.0

SwapDisk

DescriptionMonitors statistics related to SwapDisk.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the SwapDisk monitor; a description of each attribute follows.

where:

SwapDisk.FreeReports the number of free bytes on the disk that contains the swap file for a server.

CLI SyntaxSwapDisk –a <SwapDiskAttribute>

where:

<SwapDiskAttribute>The only option at this time is SwapDisk.Free. SwapDisk.Free returns the numberof free bytes on the disk that contains the swap file for a server.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "SwapDisk" -a "SwapDisk.Free" "MailServerProfile"


3.S

tatisticsM

on

itors

Tdp Schedule

DescriptionMonitors statistics related to scheduling of Tivoli Data Protection processes.





Time IntervalThe time interval to be monitored.

Time UnitClick Attributes to button to display the Time Unit dialog box. Select fromMinutes, Hours, Days, Weeks, or Months.

Type Click the Attributes button to display the Type dialog box. Select one of thefollowing:

Selective BackupSelective backup of database.

Incremental BackupIncremental backup of database.

RestoreRestore database using archived data.

ActivateActivate restored database.

Archive Transaction LogArchive transaction log.

Inactivate Transaction LogInactivate transaction log.

Log FileThe name of the log file.

186 Version 3.1.0

CLI SyntaxTdpSchedule –a <TimeInterval> –a <TimeUnit> –a <Type> –a <LogFile>

where:

<TimeInterval>The time interval to be monitored.

<TimeUnit>The unit of time to use from the following: Minutes, Hours, Days, Weeks, orMonths.

<Type>The attribute to monitor from the following:

Selective BackupSelective backup of database.

Incremental BackupIncremental backup of database.

RestoreRestore database using archived data.

ActivateActivate restored database.

Archive Transaction LogArchive transaction log.

Inactivate Transaction LogInactivate transaction log.

<LogFile>The name of the log file.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "TdpSchedule" -a "1" -a "hours"-a "Selective Backup" -a "c:\lotus\domino\data\tmdlog\tdp.log" "MailServerProfile"


3.S

tatisticsM

on

itors

Transaction Log File Size

DescriptionMonitors the size of the log files.

Domino Versions Supported4.6, 5.0.x



Desktop OptionsThe following shows the Add Monitor to the TME 10 Distributed Monitoring Profiledialog box for this monitor; a description of each field follows.

Click the Attributes button to display the Transaction Log Monitors dialog box for thismonitor.

Transaction Log MonitorsSelect one of the following:

Total SizeThe total size of the transaction log files.

Disk FreeTotal amount of free disk space.

Estimated Disk FreeEstimated amount of free disk space.

CLI SyntaxTransLogSize –a <TransactionLogMonitors>

where:

<TransactionLogMonitors>Specify one of the following attributes to monitor:

Total SizeThe total size of the transaction log files.

Disk FreeTotal amount of free disk space.

Estimated Disk FreeEstimated amount of free disk space.

188 Version 3.1.0

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "TransLogSize" -a "Total Size" "MailServerProfile"


3.S

tatisticsM

on

itors

Transaction Logging Archival Status

DescriptionChecks that transaction logs are being archived.




Desktop OptionsNone.

CLI SyntaxTransLogStatus

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "TransLogStatus" "MailServerProfile"

190 Version 3.1.0

UserMail.Statistics.Async

DescriptionReturns the database name and the requested attribute value for each user mail databasefound.





Channel NameThe channel name. You must assign this monitor the same channel name as theUserMail.Statistics.Sync monitor. Avoid using this channel name for any othermonitors.

CLI SyntaxUMStatisticsAsync –a <ChannelName>

where:

<ChannelName>The channel name. You must assign this monitor the same channel name as theUserMail.Statistics.Sync monitor. Avoid using this channel name for any othermonitors.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "UMStatisticsAsync" -a "Mail" "MailServerProfile"


3.S

tatisticsM

on

itors

UserMail.Statistics.Sync

DescriptionMonitors user mail file statistics.





Channel NameThe channel name. If you already created the channel (using a DistributedMonitoring command, for example), then enter the name of the existing channel.You must assign this monitor the same channel name as theUserMail.Statistics.Async monitor. Avoid using this channel name for any othermonitors.

Monitor AttributeClick Attributes button to display the Monitor Attribute dialog box. Select one ofthe following:

Size The size of the mail database in kilobytes.

WhiteSpace The amount of white space in the mail database.

SizeLimit The size limit of the mail database in kilobytes.

Uses The number of uses of the mail database.

Reads The number of reads of the mail database.

Writes The number of writes of the mail database.

CLI SyntaxUMStatisticsSync –a <ChannelName> –a <MonitorAttributes>

where:

<ChannelName>The channel name. If you already created the channel (using a DistributedMonitoring command, for example), then enter the name of the existing channel.

192 Version 3.1.0

You must assign this monitor the same channel name as theUserMail.Statistics.Async monitor. Avoid using this channel name for any othermonitors.

<MonitorAttributes>Can have a value of one of the following:

Size The size of the mail database in kilobytes.

WhiteSpace The amount of white space in the mail database.

SizeLimit The size limit of the mail database in kilobytes.

Uses The number of uses of the mail database.

Reads The number of reads of the mail database.

Writes The number of writes of the mail database.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "UMStatisticsSync" -a "Mail" -a writes"MailServerProfile"


3.S

tatisticsM

on

itors

Web Monitor

DescriptionMonitors numeric statistics related to the Web Retriever process.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the Web Monitor; a description of each attribute follows.

Click Attributes to display the Web Monitor Attributes dialog and select the desiredattribute.

Web.Retriever.Access.FTPReports the number of FTP retriever accesses.

Web.Retriever.Access.GopherReports the number of Gopher retriever accesses.

Web.Retriever.Access.HTTPReports the number of HTTP retriever accesses.

Web.Retriever.Bytes.ReceivedReports the number of retriever bytes received.

Web.Retriever.Bytes.SentReports the number of retriever bytes sent.

Web.Retriever.ImageCache.HitsReports the number of successful accesses on the retriever image cache.

Web.Retriever.ImageCache.MissesReports the number of unsuccessful accesses on the retriever image cache.

Web.Retriever.Process.Num.ActiveReports the number of active retriever processes.

Web.Retriever.Process.Access.FTPReports the number of retriever process FTP accesses.

Web.Retriever.Process.Access.GopherReports the number of retriever process Gopher accesses.

194 Version 3.1.0

Web.Retriever.Process.Bytes.ReceivedReports the number of bytes sent by a retriever process.

Web.Retriever.Process.Bytes.SentReports the number of bytes received by a retriever process.

Web.Retriever.Process.ProcessIDReports the process ID number.

Web.Retriever.Process.URLs.FailedReports the number of failed retriever process URLs.

Web.Retriever.Process.URLs.RequestedReports the number of requested retriever process URLs.

Web.Retriever.Process.URLs.SucceededReports the number of successful retriever process URLs.

Web.Retriever.Process.Access.HTTPReports the number of retriever process HTTP accesses.

Web.Retriever.Process.Num.BusyReports the number of busy retriever processes.

Web.Retriever.Process.Num.IdleReports the number of idle retriever processes.

Web.Retriever.Process.Num.MaximumReports the maximum number of retriever processes.

Web.Retriever.URLs.FailedReports the number of failed retriever URLs.

Web.Retriever.URLs.RequestedReports the number of retriever URLs requested.

Web.Retriever.URLs.SucceededReports the number of retriever URLs that have been successfully accessed.

Web.Retriever.VPOOL.Max.BufReports the number of buffer VPOOLs that have reached maximum size.

Web.Retriever.VPOOL.Max.ElementReports the number of element VPOOLs that have reached maximum size.

Web.Retriever.VPOOL.Max.MarkerReports the number of marker VPOOLs that have reached maximum size.

Web.Retriever.VPOOL.Max.TextReports the number of text VPOOLs that have reached maximum size.

Web.Retriever.VPOOL.Max.URLReports the number of URL VPOOLs that have reached maximum size.

CLI SyntaxWeb –a <Attribute>

where:

<Attribute> The Web Monitor attribute.


3.S

tatisticsM

on

itors

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "Web" -a "Web.Retriever.Access.FTP""MailServerProfile"

196 Version 3.1.0

XPC.<PortName>

DescriptionMonitors statistics related to the XPC console port. XPC is the Lotus communicationsprotocol for use with modems.




Desktop OptionsThe following shows the Add Monitor to TME 10 Distributed Monitoring Profile dialogfor the XPC.<PortName> monitor; a description of each attribute follows.

XPC Monitor Port AttributeSelect the port you would like to monitor from the dialog displayed by clicking theAttributes button to the right of this text box.

XPC Monitor AttributeSelect the attribute you want to monitor from the dialog displayed by clicking theAttributes button to the right of this text box. The attributes are:

Errors.CRCReports the number of cyclic redundancy check (CRC) errors on the serialport.

Errors.PortReports the number of port errors on the serial port.

Errors.RetransmittedPacketsReports the number of retransmitted packets on the serial port.

Sessions.ActiveReports the number of active sessions on the serial port.

Speed.CarrierReports the carrier speed on the serial port.

Speed.PortReports the port speed on the serial port.

UserBytes.ReceivedReports the number of user bytes received on the serial port.


3.S

tatisticsM

on

itors

UserBytes.SentReports the number of user bytes sent on the serial port.

UserMsgs.ReceivedReports the number of user messages received on the serial port.

UserMsgs.SentReports the number of user messages sent on the serial port.

CLI SyntaxXPC.<PortName> –a <Attribute>

where:

<PortName> The name of the port to monitor.

<Attribute> The XPC Monitor attribute.

CLI Examplewaddmon "Domino v5.0 Statistics Collection" "XPC.Port1" -a "UserMsgs.Sent" "MailServerProfile"

198 Version 3.1.0

Domino Performance Station Monitors

This chapter lists the Domino Performance Station monitors alphabetically. Each entryprovides complete information on the capabilities and settings for the monitor.

Domino Performance Station monitors determine end-user response times so you can trackservice level objectives for Lotus Notes users.

Table 3 summarizes the Domino Performance Station monitors.

Table 3. Domino Performance Station MonitorsMonitor CLI Name Description

DPSCalendarEntry DPSCalendarEntry Monitors calendar entry performance.

DPSDatabaseAccess DPSDatabaseAccess Monitors database access performance.

DPSIntegrity DPSIntegrity Monitors station status.

DPSNABSearch DPSNABSearch Monitors performance of NAB search.

DPSNetEcho DPSNetEcho Monitors performance of network echo.

DPSReplicateLocal DPSReplicateLocal Monitors performance of local replication.

DPSMail DPSRoundtripMail Monitors performance of round-trip mail.

DPSWebAccess DPSWebAccess Monitors web access performance.

4


4.D

om

ino

Perfo

rman

ceS

tation

Mo

nito

rs

DPSCalendarEntry

DescriptionCreates and deletes a calendar event entry in the mail database of the probe user associatedwith the specified server. Returns the time required to complete this transaction inmilliseconds.



Target EndpointsDomino Performance Station

Desktop OptionsThe following shows the Add Monitor to TME 10 Monitoring Profile dialog box for thismonitor; a description of each text box follows.

Test ID A numeric ID for the probe configuration.

Server The name of the server.

Interval The number of minutes between probes. Click Attributes and select fromthe displayed options. You can select an interval of 10 minutes, 30 minutes,1 hour, 4 hours, or 8 hours.

CLI SyntaxDPSCalendarEntry –a <TestID> –a <ServerName>–a {10_min | 30_min | 1_hour | 4_hour | 8_hour}

where:

<TestID> A numeric ID for the probe configuration.

<ServerName>The name of the server.

Interval The number of minutes between probes. You can select an interval of 10minutes, 30 minutes, 1 hour, 4 hours, or 8 hours.

CLI Examplewaddmon "Domino Performance Station Collection" DPSCalendarEntry -a 000000 -a tokyo -a 30_min"MailServerProfile"

200 Version 3.1.0

Usage NotesBecause this monitor requires a server name as an argument, you must use thewdpsaddserver command to add the server configuration information to that station’ssupported server list. A monitor distributed with a server name that is unsupported by thestation subscriber is ignored.

To ensure that the probe user ID has access to required Notes and system resources, you canexecute the probe on a one-time basis for predeployment tests and diagnostics. The one-timeprobe can be executed only from the command line using the wdpsprobeonce command.Results from a probe once are formatted as a sequence of transaction information. The firstline is the main transaction, and the next line contains subtransaction details. Each line isformatted as:transaction_name: status: other_info


4.D

om

ino

Perfo

rman

ceS

tation

Mo

nito

rs

DPSDatabaseAccess

DescriptionOpens a Notes database, verifies that it is open, and closes it. Returns the time required toaccess the specified database, in milliseconds.





Test ID A numeric ID for the probe configuration.



Database The name of the database to test.

CLI SyntaxDPSDatabaseAccess –a <TestID> –a <ServerName>–a {10_min | 30_min | 1_hour | 4_hour | 8_hour} –a <DatabaseName>

where:

<TestID> A numeric ID for the probe configuration.



<DatabaseName>The name of the database to test.

CLI Examplewaddmon "Domino Performance Station Collection" DPSDatabaseAccess -a 000000 -a tokyo -a 30_min-a names.nsf "MailServerProfile"

202 Version 3.1.0




4.D

om

ino

Perfo

rman

ceS

tation

Mo

nito

rs

DPSIntegrity

DescriptionMonitors performance stations for availability and status. If the status is Up, the controllerand scheduled probes are up and running. If the status is Down, one of the components isnot running. The components include the performance station controller and probes. Detailedinformation can be obtained with the wdpsintegrity command.

In most cases, you can correct a down status by restarting the controller. If the statusreturned is Recurring Error, one or more of the probes is consistently generating errors.You can find the probe or probes generating the errors using the wdpsintegrity command. Inmost cases, this error is caused by not testing a probe configuration before deploying it as amonitor. You can usually resolve the error by correcting the probe attributes and/orredistributing the Sentry profile.

Note: An instance of this monitor is automatically distributed to the station when the stationis created with the wdpscreate command. It is not necessary to create anotherinstance of this monitor unless the Sentry engine is cleared.




Desktop OptionsNone

CLI SyntaxDPSIntegrity

CLI Examplewaddmon "Domino Performance Station Collection" DPSIntegrity "MailServerProfile"

Usage NotesBesides acting as a monitor for the station itself, this monitor indicates the state of a testedserver. A Recurring Error state indicates that the host or resources on that host areunavailable. In this way, the station serves as a proxy monitor.

204 Version 3.1.0

DPSMail

DescriptionGenerates mail traffic from a Notes client between a source Notes server and a target server.Tracks and returns the time, in milliseconds, required to send a simulated mail message to aserver. This probe periodically polls the mail database on the source server to match thee-mail responses with the messages sent, returning a round-trip time value in milliseconds.





Test ID A unique numeric ID for the probe configuration.



Message Size (bytes)The message size in bytes.

Destination ServerThe name of the destination server.

Destination AddressThe destination address.

CLI SyntaxDPSRoundtripMail –a <TestID> –a <ServerName>–a {10_min | 30_min | 1_hour | 4_hour | 8_hour} –a <MessageSize>–a <DestinationServer> –a <DestinationAddress>

where:

<TestID> A unique numeric ID for the probe configuration.


4.D

om

ino

Perfo

rman

ceS

tation

Mo

nito

rs



<MessageSize>The message size in bytes.

<DestinationServer>The name of the destination server.

<DestinationAddress>The destination address.

CLI Examplewaddmon "Domino Performance Station Collection" DPSRoundTripMail -a 000000 -a tokyo -a 30_min-a 100 -a Server/Dev -a User/Dev "MailServerProfile"

Usage NotesThis monitor does not open the mail database on the target server. The generated mail isnever read or deleted. To keep the target database from growing too large, you must run aNotes agent periodically to delete the test mail.

Because this monitor requires a server name as an argument, you must use thewdpsaddserver command to add the server configuration information to that station’ssupported server list. A monitor distributed with a server name that is unsupported by thestation subscriber is ignored.


206 Version 3.1.0

DPSNABSearch

DescriptionTracks the time required to search a specified server’s Name and Address Book (NAB) for aspecified string. Returns the required time in milliseconds.







Interval The time between probes. You can select an interval of 10 minutes, 30minutes, 1 hour, 4 hours, or 8 hours.


View The name of the database view to test.

Pattern The pattern (string) to search for in the database view.

CLI SyntaxDPSNABSearch –a <TestID> –a <ServerName>–a {10_min | 30_min | 1_hour | 4_hour | 8_hour} –a <DatabaseName> –a <View>–a <Pattern>

where:





4.D

om

ino

Perfo

rman

ceS

tation

Mo

nito

rs


<View> The name of the database view to test.

<Pattern> The pattern (string) to search for in the database view.

CLI Examplewaddmon "Domino Performance Station Collection" DPSNABSearch -a 000000 -a tokyo -a 30_min-a names.nsf -a People -a Smith "MailServerProfile"



208 Version 3.1.0

DPSNetEcho

DescriptionTransfers a configurable number of bytes using TCP or UDP to the server’s echo port (7)where the data are received and reflected back. Tracks and returns the time, in milliseconds,required to simulate the sending of a specified network data packet to a server using thespecified protocol.








Protocol The protocol to use for the test packet. Select tcp for Transmission ControlProtocol or udp for User Datagram Protocol.

Packet Size The packet size in bytes.

CLI SyntaxDPSNetEcho –a <TestID> –a <ServerName>–a {10_min | 30_min | 1_hour | 4_hour | 8_hour} –a {tcp | udp} –a <Packet>–a <Pattern>

where:





4.D

om

ino

Perfo

rman

ceS

tation

Mo

nito

rs

Protocol The protocol to use for the test packet. Select tcp for Transmission ControlProtocol or udp for User Datagram Protocol.

<Packet> The packet size in bytes.

<Pattern> The pattern (string) to search for in the database view.

CLI Examplewaddmon "Domino Performance Station Collection" DPSNetEcho -a 000000 -a tokyo -a 30_min-a tcp -a 1000 -a Smith "MailServerProfile"

Usage NotesCommon service port (echo port 7) must be enabled on the server that is being measured.



210 Version 3.1.0

DPSReplicateLocal

DescriptionReplicates a Notes database from the source server to the client workstation. Tracks andreturns the time, in milliseconds, required to simulate a replication against a database on aspecified server.









CLI SyntaxDPSReplicateLocal –a <TestID> –a <ServerName>–a {10_min | 30_min | 1_hour | 4_hour | 8_hour} –a <DatabaseName>

where:

<TestID> A unique numeric ID for the probe configuration




CLI Examplewaddmon "Domino Performance Station Collection" DPSReplicateLocal -a 000000 -a tokyo -a 30_min-a names.nsf "MailServerProfile"


4.D

om

ino

Perfo

rman

ceS

tation

Mo

nito

rs



212 Version 3.1.0

DPSWebAccess

DescriptionResolves the server name, opens port 80/1080, and retrieves text, embedded frames, andimages. Tracks and returns the response time, in milliseconds, required to access a web pagefrom the specified server.








URL The relative URL of the web page to access.

Error Text The error text to search for. The probe searches for this text on the openedpage. If the text is not found, the test is successful.

CLI SyntaxDPSWebAccess –a <TestID> –a <ServerName>–a {10_min | 30_min | 1_hour | 4_hour | 8_hour} –a <URL> –a <ErrorText>

where:

<TestID> A unique numeric ID for the probe configuration



<URL> The relative URL of the web page to access.


4.D

om

ino

Perfo

rman

ceS

tation

Mo

nito

rs

<ErrorText> The error text to search for. The probe searches for this text on the openedpage. If the text is not found, the test is successful.

CLI Examplewaddmon "Domino Performance Station Collection" DPSWebAccess -a 000000 -a tokyo -a 30_min-a index.html -a "Error 404" "MailServerProfile"

Usage NotesThis monitor does not execute Java™ scripts and applets.



214 Version 3.1.0

Tasks

A task is an operation or set of operations that is performed routinely. This chapter lists theTivoli Manager for Domino tasks alphabetically and describes how to configure and runeach task. Table 4 summarizes these tasks.

The Tivoli Manager for Domino tasks are grouped into the following task libraries:

¶ Client Distribution Operations 3.1 — Tasks that distribute Lotus Notes client softwareto client workstations.

¶ Domino Performance Station Tasks — Tasks that start, stop, and reboot DominoPerformance Stations.

¶ Domino Server Tasks — Tasks that perform server and database operations.

¶ TMD Configuration — A task that configures Tivoli Manager for Domino to sendevents to the Tivoli Enterprise Console.

You can run most Tivoli Manager for Domino tasks using the following methods:

¶ From the Tivoli desktop.

¶ From the command line using the command for the task.

¶ From the command line using the wruntask command.

You can find additional information about tasks in the Tivoli Manager for Domino User’sGuide. Chapter 7, Working with Tasks and Jobs, describes how to set up and run tasks andjobs, as well as how to create customized tasks.

Table 4. Tivoli Manager for Domino TasksTask Name Command Description

Client Distribution Operations 3.1

Configure Notes ClientInstall 3.1

None Distributes Lotus Notes client software toworkstations.

Configure Notes ClientUpgrade 3.1

None Distributes Lotus Notes client software toworkstations.

Domino Performance Station Tasks

Reboot Station wdpsreboot Reboots the operating system on thespecified Domino Performance Station.

Start Station wdpsstart Starts the specified Domino PerformanceStation controller and its probes.

Stop Station wdpsstop Stops the specified Domino PerformanceStation controller and its probes.

5


5.Tasks

Table 4. Tivoli Manager for Domino Tasks (continued)Task Name Command Description

Start Station Monitors wdpsstartmonitors Starts monitors on the specified DominoPerformance Station.

Stop Station Monitors wdpsstopmonitors Stops monitors on the specified DominoPerformance Station.

Domino Server Tasks

Activate Databases wtmdactivatedbs Brings restored databases online(“activates” the databases) for use by thespecified Domino server.

Archive Transactional Log wtmdarchivetranslog Archives Domino transactional log files ifarchival logging is in effect on the Dominoserver.

Check Database Corruption wtmdcheckdbcorruption Checks the specified database forcorruption.

Check Health wtmdcheckhealth Returns information on the health of allDomino and Tivoli Manager for Dominoprocesses running on the specified Dominoserver.

Check Inactive Users wtmdchkinactusers Checks for users who have not accessed thespecified Domino server within the numberof days specified.

Check Replication wtmdcheckrep Checks whether a Domino server replicatedaccording to the schedule defined by itsname and address book (NAB).

Clean Database wtmdcleandb Removes entries made before the specifieddate from the Tivoli Manager for Dominomonitoring database.

Delete Server wtmddeleteserver Deletes the specified Domino server objectfrom the Tivoli environment.

Get ACLs wtmdgetacl Returns a list of all database Access ControlList (ACL) entries and the access levels forthe specified databases on the specifiedserver.

Inactivate TransactionLogging

wtmdinactivatetranslog Inactivates transactional logs on thespecified Domino server.

Incremental Backup wtmdincrementalbackup Performs an incremental backup ofdatabases on a Domino server.

Mail Waiting wtmdmailwaiting Lists all the currently waiting mail in theserver mailboxes on the specified server.

Modify Database ACLs wtmdaclmod Modifies the Access Control List (ACL)entries for the specified databases on thespecified server.

Purge Mail wtmdpurgemail Lists and optionally purges all mail in thespecified mail file that meets or exceeds thespecified age and message-size criteria.

Query Activate wtmdqueryactivate Returns a list of databases that have beenrestored but not yet activated on thespecified server.

216 Version 3.1.0

Table 4. Tivoli Manager for Domino Tasks (continued)Task Name Command Description

Query Backup wtmdquerybackup Returns a list of all database template (.ntf)and database (.nsf) files on the specifiedserver.

Query Database Activity wtmddbactivity Checks specified database files on aDomino server for activity within aspecified number of days and activity type.

Query Log wtmdquerylog Queries the log files on the specified server.

Query NAB wtmdquerynab Queries the Name and Address Book(NAB) on the specified Domino server.

Query Restore wtmdqueryrestore Returns a list of all backed-up databaseversions for the specified Domino server.

Query Statistics wtmdquerystat Queries the Domino server statistics on thespecified server.

Query Transaction Log wtmdquerytranslog Returns a list of the transaction logsarchived on the Tivoli Storage Managerserver for the specified Domino server.

Recycle NT Server Service wtmdrecyclentsvrsvc Stops and restarts the Windows NT Serverservice on Windows NT.

Recycle Server wtmdrecycle Stops and restarts the Domino serverprocess on the specified Domino server.

Remote Console wtmdremoteconsole Executes a Domino server command on thespecified Domino server and returns theresults in the remote console.

Restore Databases wtmdrestoredbs Restores the specified database on theselected server from backups on the TivoliStorage Manager server.

Selective Backup wtmdselectivebackup Performs a selective backup on thespecified databases on the specified Dominoserver.

Start Engine wtmdstartengine Starts the local Tivoli Enterprise Consoleevent engine on the specified server.

Start Monitors wtmdstartmonitors Starts monitoring on the specified server.

Start Server wtmdstartserver Starts the Domino server process on thespecified server.

Stop Engine wtmdstopengine Stops the Tivoli Enterprise Console eventengine on the specified server.

Stop Monitors wtmdstopmonitors Stops monitoring on the specified server.

Stop Server wtmdstopserver Stops the Domino server process on thespecified servers.

Verify Mail wtmdverifymail Checks all NAB mail user entries againstthe mail files that exist on the specifiedDomino server and returns a list of all mailfiles without NAB entries.

TMD Configuration

Configure TEC for TMD None Configures the Tivoli Enterprise Console tohandle Domino events.


5.Tasks

Activate Databases

DescriptionBrings restored databases online (“activates” the databases) for use by the specified Dominoserver.

If the database is logged, use the –DATE option to restore all transactional log files up tothe date and time you specify.

Equivalent to the Tivoli Data Protection command domdsmc activatedbs/applylogs=date_time.

Authorization RoleDomino_TDP_Admin

Task LibraryDomino Server Tasks

Target EndpointsLotusDominoServer object

Desktop OptionsNone

CLI Syntax¶ Using the wtmdactivatedbs command:

wtmdactivatedbs <ServerName> [–DATE=<DateTime> | NOW]

where:


DATE <DateTime> is the date up to which you want to restore transactionallogs. If included, this option restores the transactional log entries to thedatabase from the date of the last database restoration up to the datespecified. If the date is not specified, the transactional logs are notrestored. To restore the logs up until the current time, use–DATE=NOW.

The format for date and time is MM/DD/YYYY,HH:MM:SS, whereMM=month, DD=day, YYYY=year, HH=hour, MM=minute, andSS=second.

¶ Using the wruntask command:

Activate Databases [–a DATE=<DateTime> | NOW]

where:

DATE <DateTime> is the date up to which you want to restore transactionallogs. If included, this option restores the transactional log entries to thedatabase from the date of the last database restoration up to the datespecified. If the date is not specified, the transactional logs are notrestored. To restore the logs up until the current time, use–DATE=NOW.

218 Version 3.1.0

The format for date and time is MM/DD/YYYY,HH:MM:SS, whereMM=month, DD=day, YYYY=year, HH=hour, MM=minute, andSS=second.

CLI ExampleThe following example activates the server tokyo and restores transactional log entriescreated before September 1, 2001 at 13:45:30.

¶ Using the wtmdactivatedbs command:wtmdactivatedbs tokyo -DATE=09/01/2001,13:45:30

¶ Using the wruntask command:wruntask -t "Activate Databases" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo-a DATE="09/01/2001,13:45:30"

Usage NotesNone.


5.Tasks

Archive Transactional Log

DescriptionArchives Domino transactional log files if archival logging is in effect on the Dominoserver. It first checks if any log files are ready for archiving, then archives the files on theTivoli Storage Manager server.

Equivalent to the Tivoli Data Protection command domdsmc archivelogs.




Desktop OptionsNone

CLI Syntax¶ Using the wtmdarchivetranslog command:

wtmdarchivetranslog <ServerName>

where:



Archive Transactional Log

CLI ExampleThe following example archives transactional log files on server tokyo.

¶ Using the wtmdarchivetranslog command.wtmdarchivetranslog tokyo

¶ Using the wruntask command.wruntask -t "Archive Transactional Log" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesNone.

220 Version 3.1.0

Check Database Corruption

DescriptionChecks the specified database for corruption. You can check for corruption by server,database, or database view. A fix is run for each corrupt database to correct the corruption.When it completes, a list of all corrupt databases is returned, along with a flag statingwhether the corruption was fixed.

Authorization RoleDomino_Admin or Domino_User



Desktop OptionsRefer to the CLI Syntax section for a list of the arguments for this task.

CLI Syntax¶ Using the wtmdchkdbcorruption command:

wtmdchkdbcorruption <ServerName> [<DatabaseName; ...>] [<View, ...> | ALL]

where:


<DatabaseName; ...>The fully qualified path and filename of the database. You can specifymultiple databases by separating the names with semicolons.

<View, ...> The name of a view. You can specify multiple views by separating thenames with commas. ALL specifies all views for the specifieddatabases.


Check Database Corruption [–a <DatabaseName; ...> ] [–a <View, ...> | ALL]

where:


<View, ...> The name of a view. You can specify multiple views by separating thenames with commas. ALL specifies all views for the specifieddatabases.

CLI ExampleThe following example checks db1.ntf and db2.ntf on server tokyo for corruption.

¶ Using the wtmdchkcorruption command:wtmdchkdbcorruption tokyo C:\data\db1.ntf;C:\data\db2.ntf ALL



5.Tasks

wruntask -t "Check Database Corruption" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo-a "C:\data\db1.ntf;C:\data\db2.ntf" -a ALL

Usage NotesNone

222 Version 3.1.0

Check Health

DescriptionReturns information on the health of all Domino and Tivoli Manager for Domino processesrunning on the specified Domino server. Checks the status (Running, Stopped, Hung, orUnconfigured) of the following Domino processes: Tivoli Addin, Core Database Server,Event Monitor, Billing Manager, Cluster Database Directory, Cluster Replicator, HTTPServer, Web Retriever, SMTP Server, NNTP Server, LDAP Server, POP3 Server, IMAPServer, Replication Server, Mail Router, Statistics Monitor, Agent Manager, Admin Process,Schedule Manager, and Calendar Manager.





CLI Syntax¶ Using the wtmdcheckhealth command:

wtmdcheckhealth <ServerName> [–TASK=<Task, ...>] [–NAME=<Name, ...>]

where:


TASK <Task, ...> is the exact name of any third-party addin task in thenotes.ini file. You can specify multiple tasks by separating them withcommas.

NAME <Name, ...> is the exact name of any third-party addin task on the serverconsole. You can specify multiple tasks by separating them withcommas.


Check Health [–a TASK=<Task, ...>] [–a NAME=<Name, ...>]

where:

TASK <Task, ...> is the exact name of any third-party addin task in thenotes.ini file. You can specify multiple tasks by separating them withcommas.

NAME <Name, ...> is the exact name of any third-party addin task on the serverconsole. You can specify multiple tasks by separating them withcommas.

CLI ExampleThe following example checks the health of processes on Domino server tokyo.

¶ Using the wtmdcheckhealth command:


5.Tasks

wtmdcheckhealth tokyo -TASK=caddin -NAME=custaddin

¶ Using the wruntask command:wruntask -t "Check Health" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo-a TASK=caddin -a NAME=custaddin

Usage NotesNone.

224 Version 3.1.0

Check Inactive Users

DescriptionChecks for users who have not accessed the specified Domino server within the number ofdays specified. A list of all users who meet the criteria is returned.





CLI Syntax¶ Using the wtmdchkinactusers command:

wtmdchkinactusers <ServerName> <Days>

where:


<Days> The minimum number of days since users last connected to the specifiedserver.


Check Inactive Users –a <Days>

where:


CLI ExampleThe following example checks for users who have been inactive on the server tokyo for thelast 120 days.

¶ Using the wtmdchkinactusers command:wtmdchkinactusers tokyo 120

¶ Using the wruntask command:wruntask -t "Check Inactive Users" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo -a 120

Usage NotesNone.


5.Tasks

Check Replication

DescriptionChecks whether a Domino server replicated according to the schedule defined by its nameand address book (NAB).

Authorization RoleDomino_Admin




CLI Syntax¶ Using the wtmdcheckrep command:

wtmdcheckrep <ServerName> {INC=<IncludeString> | EXC=<ExcludeString>}[DATE=<StartDate>]

where:


INC <IncludeString> is a semicolon-separated list of strings that must be included inthe search criteria for the replication report.

EXC <ExcludeString> is a semicolon-separated list of strings that must be excluded inthe search criteria for the replication report.

DATE <StartDate> is the date and time on which to check replication. The date mustbe in the following format: MM/DD/YYYY,HH:MM:SS, where MM=month,DD=day, YYYY=year, and optionally, HH=hour, MM=minute, and SS=second.If no date is specified, the replication check is performed for the previous week.


Check Replication {–a INC=<IncludeString> | EXC=<ExcludeString>}[–a DATE=<StartDate>]

where:

INC <IncludeString> is a semicolon-separated list of strings that must be included inthe search criteria for the replication report.

EXC <ExcludeString> is a semicolon-separated list of strings that must be excluded inthe search criteria for the replication report.

DATE <StartDate> is the date and time on which to check replication. The date mustbe in the following format: MM/DD/YYYY,HH:MM:SS, where MM=month,DD=day, YYYY=year, and optionally, HH=hour, MM=minute, and SS=second.If no date is specified, the replication check is performed for the previous week.

226 Version 3.1.0

CLI ExampleThe following example verifies that replication occurred on the server tokyo.

¶ Using the wtmdcheckrep command:wtmdcheckrep tokyo INC=solserver DATE=07/17/2001

¶ Using the wruntask command:wruntask -t "Check Replication" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo-a INC=solserver -a Date=07/17/2001

Usage NotesThe following information about the replication instance is returned:

¶ The name of the local or remote Domino database that was replicated

¶ The timestamp for the replication instance

¶ The time it took for the replication to complete in minutes

¶ Events that occurred during this replication instance

The following data about the replication database is returned:

¶ The name of the local Domino database that was replicated

¶ The name of the remote Domino database that was replicated

¶ Replication access level for the database

¶ Number of documents added to the local database during this replication

¶ Number of documents deleted from the local database during this replication

¶ Number of documents updated on the local database during this replication

¶ Kilobytes received for this replication

¶ Kilobytes sent for this replication

¶ Replication direction (pull, push, pull-push, pull-pull)


5.Tasks

Clean Database

DescriptionRemoves entries made before the specified date from the Tivoli Manager for Dominomonitoring database.





CLI Syntax¶ Using the wtmdcleandb command:

wtmdcleandb <Date>

where:

<Date> A date in the format mm-dd-yyyy. Entries made before this date areremoved.


Clean Database –a <date>

where:

<Date> A date in the format mm-dd-yyyy. Entries made before this date areremoved.

CLI ExampleThe following example removes entries made before January 1, 2001 from the monitoringdatabase.

¶ Using the wtmdcleandb command:wtmdcleandb 01-01-2001

¶ Using the wruntask command:wruntask -t "Clean Database" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo-a 01-01-2001

228 Version 3.1.0

Configure Notes Client Install 3.1

DescriptionRefer to Appendix F, Installing and Upgrading Notes Clients, in the Tivoli Manager forDomino User’s Guide for information on using this task.


Task LibraryClient Distribution Operations 3.1

Target EndpointsTivoli managed node

Desktop OptionsThe following shows the Configure Notes Client Install 3.1 dialog; a description of eachfield follows.

This task has the following arguments:

Enter a new or existing configuration nameEnter the desired configuration name. Short names without spaces are preferred. Thisshould be a word that describes this particular set of selected options

Destination PlatformSelect one of the available choices. This task must be executed once for eachoperating system to be installed.

Managed Node NameEnter the name of the managed node where the client source resides.


5.Tasks

Source DirectoryEnter the full directory path for Notes on the source. The appropriate platform filesshould exist in this directory path.

Source Notes.ini File (Full Path):Enter the full pathname of the source notes.ini file; for example,/opt/lotus/notesr4/notes.ini or c:\WINNT\NOTES.INI.

Target DirectoryEnter the full directory path for Notes on the target. The default is C:\.

Notes.ini Target DirectoryEnter the directory for the target notes.ini file; for example,/opt/lotus/notesr4/notes.ini or c:\WINNT\NOTES.INI.

Free Space (Mbytes)Enter the amount of disk space, in MB, required for the client installation.

Userid (UNIX Only)Enter the UNIX user ID that should own all of the Notes file.

Groupid (UNIX Only)Enter the UNIX group ID for all of the Notes files.

CLI SyntaxConfigure Notes Client Install 3.1 –a <ConfigurationName> –a <DestinationPlatform>–a <ManagedNodeName> –a <SourceDirectory> –a <SourceNotesFile>–a <FreeSpace> –a <TargetDirectory> –a <NotesTargetDirectory>

where:

<ConfigurationName>The configuration name. Short names without spaces are preferred. This should be aword that describes this particular set of selected options.

<DestinationPlatform>The destination platform. This task must be executed once for each operating systemto be installed. The following options are available:

win95 Specify win 95 for Windows 95 or Windows 98.

w32-ix86 WindowsSpecify w32-ix86 for Windows 2000 or Windows NT.

<ManagedNodeName>The name of the managed node where the client source resides.

<SourceDirectory>The full directory path for Notes on the source. The appropriate platform filesshould exist in this directory path.

<SourceNotesFile>The full pathname of the source notes.ini file; for example,/opt/lotus/notesr4/notes.ini or c:\WINNT\NOTES.INI.

<FreeSpace>The amount of disk space, in MB, required for the client installation.

<TargetDirectory>The full directory path for Notes on the target. The default is C:\.

230 Version 3.1.0

<NotesTargetDirectory>Enter the full directory path for Notes on the target. The default is C:\.

CLI Examplewruntask -t "Configure Notes Client Install 3.1" -l "Client Distribution Operations 3.1"-h @ManagedNode:hjchao -a "ConfigurationAA" -a "w32-ix86" -a hjchao -a "C:\test\notes"-a "C:\test\notes\notes.ini" -a 95 -a "C:\" -a "C:\Windows"

Usage NotesNone.


5.Tasks

Configure Notes Client Upgrade 3.1

DescriptionRefer to Appendix F, Installing and Upgrading Notes Clients, in the Tivoli Manager forDomino User’s Guide for information on using this task.


Task LibraryClient Distribution Operations 3.1


Desktop OptionsThe following shows the Configure Notes Client Upgrade 3.1 dialog; a description of eachfield follows.

This task has the following arguments:

Enter a new or existing configuration nameEnter the desired configuration name. Short names without spaces are preferred. Thisshould be a word that describes this particular set of selected options.

Upgrade TypeUpgrade from the current Notes client version to the new Notes client version.

Destination PlatformSelect one of the available choices. This task must be executed once for eachInterpreter Type to be installed.

232 Version 3.1.0

Managed Node NameThe name of the managed node where the client source resides.

Source DirectoryThe full directory path for Notes on the source. The appropriate platform files mustexist in this directory path.

Source Data DirectoryThe directory which contains the Notes client data files of the reference copy in themanaged node. Example: C:\Notes\Data.

Target DirectoryEnter the full directory path for Notes on the target. Default is C:\

Target Data DirectoryThe directory where the Notes client data will be copied to the target machine. Forexample: C:\Notes\Data.

Target Notes.ini File (Full Path)Enter the directory for the target notes.ini file. For example:/opt/lotus/notesr4/notes.ini, or c:\WINNT\NOTES.INI.

Free Space (Mbytes)Enter the amount of disk space, in Mbytes, required for the client installation.

Userid (UNIX only)Enter the userid that should own all of the Notes files.

Groupid (UNIX only)Enter the groupid for all of the Notes files.

CLI SyntaxConfigure Notes Client Upgrade 3.1–t <TaskName> –a <UpgradeType>–a <DestinationPaltform> –a <ManagedNodeName> –a <SourceDirectory>–a <SourceDataDirectory> –a <FreeSpace> –a <TargetDirectory>–a <TargetDataDirectory> –a <NotesTargetDirectory> –a <UserID>–a <GroupID>

where

<ConfigurationName>The configuration name. Short names without spaces are preferred. This should be aword that describes this particular set of selected options.

<UpgradeType>Upgrade from the current Notes client version to the new Notes client version.

<DestinationPlatform>You must be execute this task once for each Interpreter Type to be installed. Thefollowing options are available:

win95 Specify this option for Windows 95 or Windows 98.

w32-ix86Specify this option for Windows NT.

aix4-r1Specify this option for IBM RS/6000 / AIX 3.2 or IBM RS/6000 / AIX 4.1.


5.Tasks

solarisSpecify this option for SPARC / Solaris.

<ManagedNodeName>The name of the managed node where the client source resides.

<SourceDirectory>The full directory path for Notes on the source. The appropriate platform files mustexist in this directory path.

<SourceDataDirectoryThe directory which contains the Notes client data files of the reference copy in themanaged node. Example: C:\Notes\Data.

<FreeSpace>The amount of space, in MB, required for the client installation.

<TargetDirectory>The full directory path for Notes on the target. Default is C:\

<TargetDataDirectory>The directory where the Notes client data will be copied to the target machine.Example: C:\Notes\Data

<NotesTargetDirectory>Enter the full directory path for Notes on the target. Default is C:\

<UserID>Enter the userid that should own all of the Notes files (UNIX only).

<GroupID>Enter the groupid for all of the Notes files (UNIX only).

CLI Examplewruntask -t "Configure Notes Client Upgrade 3.1" -l "Client Distribution Operations 3.1"-h @ManagedNode:hjchao -a "Configuration3" -a "4xto50" -a "w32-ix86" -a hjchao-a "C:\test\notes" -a "C:\test\notes\data" -a 95 -a "C:\notes" -a "C:\notes\data"-a "C:\notes\notes.ini"

Usage NotesNone.

234 Version 3.1.0

Configure TEC for TMD

DescriptionConfigures the Tivoli Enterprise Console to handle Domino events and sets up an eventgroup to view the events. Configuration is accomplished by importing new classes and rules,installing new event sources, compiling the new rule base, adding event group filters, thenstopping and restarting the event server. The task can only be executed against a TivoliEnterprise Console server.

After entering the name of the new rule base, you must decide whether to clone the activerule base, clone another rule base, or not clone any rule base. If you attempt to both clonethe active rule base and enter the name of an existing rule base, a task error occurs.

Authorization Rolesenior

Task LibraryTMD Configuration


Desktop OptionsThis task has the following arguments:

Enter the name for the Domino rule baseEnter a descriptive configuration name with no spaces. To modify a current rulebase, enter the rule base name. Do not attempt to modify the default rule base nameor enter Default in the text box. The Tivoli command wlsrb provides a list of allrule bases. To create a new rule base, enter the name of the new rule base, or usethe default.

Clone currently ACTIVE rule baseSelecting this button clones the new rule base from the active rule base.

Create New Rule Base without cloningSelecting this button creates a new rule base. Enter the name of the new rulebase inthe Rule Base to clone text box, or use the default provided.

Specify a rule base to cloneSelecting this button specifies a rule base to clone. Enter the name of the managednode where the client source resides in the Rule Base to clone text box.

Rule base to cloneIf you are creating a new rule base, enter the name of the rule base you want toclone in this text box. If you have not previously created a new rule base, you maywant to clone an existing rule base (that is, Default). If you attempt to select thisoption, as well as selecting the button for cloning the active rule base, a task erroroccurs.

Event group nameWhen configuring the event server for Domino events, you may also want to createa new event group to receive those events in the event console. To do this, select theCreate Event Group button. Use the default event group or enter a different groupname.


5.Tasks

Restart Event ServerWhen the event server is configured, you must restart it for the changes to takeplace. You can restart the event server immediately following configuration byselecting the Restart Event Server button. If you want to start the event serverlater, do not select the Restart Event Server button.

CLI SyntaxRefer to the Release Notes for information on running this task from the command line.

Usage NotesNone

236 Version 3.1.0

Delete Server

DescriptionDeletes the specified Domino server object from the Tivoli environment. Cleans up allmodifications made to the system for managing this server with Tivoli Manager for Domino,including removing entries within events, removing entries from the notes.ini file, andremoving any program files placed on the endpoint. The Domino server continues to be anendpoint in the Tivoli management region.




Desktop OptionsNone

CLI Syntax¶ Using the wtmddeleteserver command:

wtmddeleteserver <ServerName>

where:



Delete Server

CLI ExampleThe following example deletes the Domino server tokyo.

¶ Using the wtmddeleteserver command:wtmddeleteserver tokyo

¶ Using the wruntask command:wruntask -t "Delete Server" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesNone.

See AlsoNone.


5.Tasks

Get ACLs

DescriptionReturns a list of all database Access Control List (ACL) entries and the access levels for thespecified databases on the specified server.





CLI Syntax¶ Using the wtmdgetacl command:

wtmdgetacl <ServerName> <DatabaseName; ...>

where:


<DatabaseName; ...>The name of the database to query. If specifying multiple databases, usesemicolons to separate the names.


Get ACLs –a <DatabaseName; ...>

where:

<DatabaseName; ...>The name of the database to query. If specifying multiple databases, usesemicolons to separate the names.

CLI ExampleThe following command gets ACL information for the database file acls.nsf on the servertokyo.

¶ Using the wtmdgetacl command:wtmdgetacl tokyo acls.nsf

¶ Using the wruntask command:wruntask -t "Get ACLs" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo -a acls.nsf

Usage NotesNone.

238 Version 3.1.0

Inactivate Transaction Logging

DescriptionInactivates transactional log files on the specified Domino server. Queries the databasebackups to determine which log files are required by active databases on the Domino serveryou specified and inactivates any log files that are not required.

Equivalent to the Tivoli Data Protection command domdsmc inactivatelogs.




Desktop OptionsNone

CLI Syntax¶ Using the wtmdinactivatetranslog command:

wtmdinactivatetranslog <ServerName>

where:



Inactivate Transaction Logging

CLI ExampleThe following example inactivates transactional logs on the server tokyo.

¶ Using the wtmdinactivatetranslog command:wtmdinactivatetranslog tokyo

¶ Using the wruntask command:wruntask -t "Inactivate Transaction Logging" -l "Domino Server Tasks"-h @LotusDominoServer:tokyo

Usage NotesNone


5.Tasks

Incremental Backup

DescriptionPerforms an incremental backup of databases on a Domino server. Equivalent to the TivoliData Protection command domdsmc incremental.

An incremental backup performs a full backup of the specified databases that meet at leastone of the following conditions:

¶ The database is within the Domino data path or symbolically linked to the Domino datapath by directory or database links.

¶ If the database has archive logging enabled, the Database Instance Identifier (DBIID)has changed. (See the Domino server documentation for more information on the DBIIDand when it can change.)

¶ If the database is not logged, it has been modified since the last backup occurred (dataand non-data modification dates are checked).

¶ The database is new or newly included in the backup.

An incremental backup performs the following functions:

¶ Backs up any new databases.

¶ Backs up any unlogged databases that have changed since the last backup.

¶ Backs up any logged databases in which the DBIID has changed.

¶ Inactivates database backups that are no longer needed.





CLI Syntax¶ Using the wtmdincrementalbackup command:

wtmdincrementalbackup <ServerName> <DatabaseName, ...>

where:


<DatabaseName, ...>The database name relative to the server’s data directory. Use commas toseparate database names.


Incremental Backup –a <DatabaseName, ...>

240 Version 3.1.0

where:


CLI ExampleIn the following example, an incremental backup will be performed on two databases on theserver tokyo.

¶ Using the wtmdincrementalbackup command:wtmdincrementalbackup tokyo C:\data\db1.ntf,C:\data\db2.ntf

¶ Using the wruntask command:wruntask -t "Incremental Backup" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo-a C:\data\db1.ntf,C:\data\db2.ntf

Usage NotesNone.


5.Tasks

Mail Waiting

DescriptionLists all the currently waiting mail in the server mailboxes on the specified server. Returnsthe number of messages waiting to be sent, the mailbox in which the mail is waiting, thedestination address, the sender, and the time the mail entered the queue.




Desktop OptionsNone

CLI Syntax¶ Using the wtmdmailwaiting command:

wtmdmailwaiting <ServerName>

where:



Mail Waiting

CLI ExampleThe following example checks for mail waiting on server tokyo:

¶ Using the wtmdmailwaiting command:wtmdmailwaiting tokyo

¶ Using the wruntask command:wruntask -t "Mail Waiting" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesNone

242 Version 3.1.0

Modify Database ACLs

DescriptionModifies the Access Control List (ACL) entries for the specified databases on the specifiedserver. The command returns a list of all the ACLs for the database specified.





CLI Syntax¶ Using the wtmdaclmod command:

wtmdaclmod <ServerName> <DatabaseName>ADD=[<user_name>][DEL=<user_name>][MOD=<user_name>][OLD=<user_name>]CHG=[<user_name>][CLRP=<num_list>][SETP=<num_list>][INVP=<num_list>][LEVEL={NOACCESS | DEPOSITOR |READER | AUTHOR | EDITOR | DESIGNER | MANAGER}][FLAG=AUTHOR_NOCREATE | FLAG=SERVER |FLAG=NODELETE | CREATE_PRAGENT |FLAG=CREATE_PRFOLDER | FLAG=PERSON | FLAG=GROUP |FLAG=CREATE_FOLDER | FLAG=CREATE_LOTUSSCRIPT |FLAG=PUBLICREADER | FLAG=PUBLICWRITER |FLAG=MONITORS_DISALLOWED | FLAG=RELEASE_LOCKED_DOC |FLAG=ADMIN_READERAUTHOR | FLAG=ADMIN_SERVER]

where:


<DatabaseName>Specifies the name of the database whose ACL you want to modify. Usesemicolons to separate multiple database names.

<username> The user.

<num_list> Specifies the list of privilege numbers in the ACL

ADD The option <username> adds a new username to the ACL.

DEL Deletes the username from the ACL. All other options are ignored.

MOD Modifies the existing username’s ACL


5.Tasks

OLD Must be used in conjunction with CHG. The old username is replacedwith the new username, specified in CHG parameter.

CHG Must use in conjunction with OLD. CHG replaces the user namespecified in OLD parameter.

CLRP Will CLEAR the privilege numbers in the ACL

SETP Will SET the privilege numbers in the ACL

INVP Will INVERT the privilege numbers in the ACL.n\

LEVEL Only one of the following can be set: NOACCESS, DEPOSITOR,READER, AUTHOR, EDITOR, DESIGNER

FLAG You can set one or more of the following options, however you can onlyset one option in a single use of this command.

AUTHOR_NOCREATEAuthors can’t create new notes

SERVEREntry represents a Server

NODELETEUser cannot delete notes

CREATE_PRAGENTUser can create personal agents

CREATE_PRFOLDERUser can create personal folders

PERSONEntry represents a Person

GROUPEntry represents a group

CREATE_FOLDERUser can create and update shared views and folders. Thisenables an Editor to assume some Designer-level access.

CREATE_LOTUSSCRIPTUser can create LotusScript.

PUBLICREADERUser can read public notes.

PUBLICWRITERUser can write public notes.

MONITORS_DISALLOWEDUser cannot register monitors for this database.

RELEASE_LOCKED_DOCUser can release locked documents.

ADMIN_READERAUTHORAdmin server can modify reader and author fields in thedatabase.

244 Version 3.1.0

ADMIN_SERVEREntry is administration server.


Modify Database ACLs<db_name>[ADD=<username>][DEL=<username>][MOD=<username>][OLD=<username>][CHG=<username>][CLRP=<num_list>][SETP=<num_list>][INVP=<num_list>][LEVEL={NOACCESS | DEPOSITOR |READER | AUTHOR | EDITOR | DESIGNER | MANAGER}][FLAG=AUTHOR_NOCREATE | FLAG=SERVER |FLAG=NODELETE | CREATE_PRAGENT |FLAG=CREATE_PRFOLDER | FLAG=PERSON | FLAG=GROUP |FLAG=CREATE_FOLDER | FLAG=CREATE_LOTUSSCRIPT |FLAG=PUBLICREADER | FLAG=PUBLICWRITER |FLAG=MONITORS_DISALLOWED | FLAG=RELEASE_LOCKED_DOC |FLAG=ADMIN_READERAUTHOR | FLAG=ADMIN_SERVER]

where:

<db_name>Specifies a semicolon-separated list of Domino database names for which tomodify the ACL information.

<username>Specifies the user.

<num_list>Specifies the list of privilege numbers in the ACL

ADD The option <username> adds a new username to the ACL

DEL Deletes the username from the ACL. All other options are ignored.

MOD Modifies the existing username’s ACL

OLD Must be used in conjunction with CHG. The old <username> is replaced withthe new <username>, specified in CHG parameter.

CHG Must use in conjunction with OLD. CHG replaces the user name specified inOLD parameter.

CLRP Will clear the privilege numbers in the ACL

SETP Will set the privilege numbers in the ACL

INVP Will invert the privilege numbers in the ACL.

LEVELOnly one of the following can be set: NOACCESS, DEPOSITOR, READER,AUTHOR, EDITOR, DESIGNER


5.Tasks

FLAGYou can set one or more of the following options, however you can only set oneoption in a single use of this command.

AUTHOR_NOCREATEAuthors can’t create new notes

SERVEREntry represents a Server

NODELETEUser cannot delete notes

CREATE_PRAGENTUser can create personal agents

CREATE_PRFOLDERUser can create personal folders

PERSONEntry represents a Person

GROUPEntry represents a group

CREATE_FOLDERUser can create and update shared views and folders. This enables anEditor to assume some Designer-level access.

CREATE_LOTUSSCRIPTUser can create LotusScript.

PUBLICREADERUser can read public notes.

PUBLICWRITERUser can write public notes.

MONITORS_DISALLOWEDUser cannot register monitors for this database.

RELEASE_LOCKED_DOCUser can release locked documents.

ADMIN_READERAUTHORAdmin server can modify reader and author fields in the database.

ADMIN_SERVEREntry is administration server.

CLI ExampleThe following command adds a user Joe Brown to the ACL of the tokyo server in theAsia-Pacific domain. Note that the fully qualified format for a name in Lotus Notes is validin this context. The LEVEL argument gives the user the Designer privilege for names.nsf,and the FLAG argument defines the user as a Person in Notes.

¶ Using the wtmdaclmod command:wtmdaclmod tokyo/Asia-Pacific names.nsf ADD="Joe Brown/Asia-Pacific" LEVEL=DESIGNERFLAG=PERSON


246 Version 3.1.0

wruntask -t "Modify Database ACLs" -l "Domino Server Tasks" -h @LotusDominoServer:utah-a names.nsf -a ADD="Joe Brown/Asia-Pacific" -a LEVEL=DESIGNER -a FLAG=PERSON

Usage NotesNone

See AlsoGet ACLs


5.Tasks

Purge Mail

DescriptionLists and optionally purges all mail in the specified mail file that meets or exceeds thespecified age and message-size criteria. If you specify both options, both criteria must bemet for mail to be purged.





CLI Syntax¶ Using the wtmdpurgemail command:

wtmdpurgemail <ServerName> [–DB=<MailDatabaseName>] [–OLDER=<Days> |–LARGER=<Kilobytes>] [–PURGE]

where:


DB <MailDatabaseName> is the name of the mail database file to check,relative to the data directory. If omitted, all mail database files arechecked.

OLDER <Days> is the maximum message age allowed; all older messages arepurged.

LARGER <Kilobytes> is the maximum message size allowed, in kilobytes; alllarger messages are purged.

PURGE If specified, all mail passing the check is purged. If not specified, allmail passing the check is only reported.


Purge Mail [–a DB=<MailDatabaseName>] [–a OLDER=<Days>]

[–a LARGER=<Kilobytes>] [–a PURGE]

where:

DB <MailDatabaseName> is the name of the mail database file to check,relative to the data directory. If omitted, all mail database files arechecked.


248 Version 3.1.0

LARGER <Kilobytes> is the maximum message size allowed, in kilobytes; alllarger messages are purged.

PURGE If specified, all mail passing the check is purged. If not specified, allmail passing the check is only reported.

CLI ExampleThe following example purges messages older than 365 days and larger than 10,000kilobytes in all mail files on the server tokyo.

¶ Using the wtmdpurgemail command:wtmdpurgemail tokyo -OLDER=365 -LARGER=10000 -PURGE

¶ Using the wruntask command:wruntask -t "Purge Mail" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo -a OLDER=365-a LARGER=10000 -PURGE

Usage NotesThe following information is returned for each mail file found:

¶ Count — The number of mail files where messages were purged

¶ Mail Database — The databases from which messages were purged

¶ Messages — The number of messages purged from that database

¶ Size — The total size (in kilobytes) of the messages

¶ Total — The total number of messages and total size of the messages for all mail files


5.Tasks

Query Activate

DescriptionReturns a list of databases that have been restored but not yet activated on the specifiedserver.

Equivalent to the Tivoli Data Protection command domdsmc query pendingdbs.




Desktop OptionsNone

CLI Syntax¶ Using the wtmdqueryactivate command:

wtmdqueryactivate <ServerName>

where:



Query Activate

CLI ExampleThe following example lists databases that have been restored but not yet activated on servertokyo.

¶ Using the wtmdqueryactivate command:wtmdqueryactivate tokyo

¶ Using the wruntask command:wruntask -t "Query Activate" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesThe following information is returned for each database found:

¶ Database — The database path and filename.

¶ Restored — The date on which the database was restored.

¶ Size — The size of the database in kilobytes (Kb).

¶ Logged — Whether the database has logging enabled.

¶ Database Title — Name of the database.

250 Version 3.1.0

Query Backup

DescriptionReturns a list of all database template (.ntf) and database (.nsf) files on the specified server.You can specify a database name if desired.

Equivalent to the Tivoli Data Protection command domdsmc query domino.




Desktop OptionsRefer to the CLI Syntax section for a list of the arguments for this task. If no database nameis entered, all databases in all directories are listed.

CLI Syntax¶ Using the wtmdquerybackup command:

wtmdquerybackup <ServerName> [<DatabaseName>]

where:


<DatabaseName, ...>Defines the database name relative to the server’s data directory. Use commas toseparate database names. If omitted, all databases in all directories are shown.


Query Backup [–a <DatabaseName, ...>]

where:


CLI ExampleThe following example returns information on databases for the server tokyo.

¶ Using the wtmdquerybackup command:wtmdquerybackup tokyo

¶ Using the wruntask command:wruntask -t "Query Backup" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesFor each database found, the following information is returned:

¶ Database — The database path and filename

¶ Last Modified Date — Date on which the database was last modified


5.Tasks

¶ Size — Size of the database in kilobytes

¶ Logged — Whether the database has logging enabled

¶ Database Title — Name of the database

252 Version 3.1.0

Query Database Activity

DescriptionChecks the specified database files on a Domino server for activity within the specifiednumber of days and the specified activity type. Returns a list of database files that have nothad any activity within the number of days specified.





CLI Syntax¶ Using the wtmddbactivity command:

wtmddbactivity <ServerName> <DatabaseName; ...> <Days> [ACTIVITY=<ActivityType; ...>]

where:


<DatabaseName; ...>The database files to check against. You can specify multiple databases byseparating the names with semicolons.

<Days>The number of days without activity.

ACTIVITY<ActivityType; ...> specifies the type of activity to check for. If you omit thisoption, the command checks for data and non-data modification. If you list morethan one type, use semicolons to separate listed types and enclose the statementin double quotes (for example, "ACTIVITY=N;R;W").

The activity types are the following:

A All activities

B Document read/write activities

D Data modification activities

M Data/non-data modification activities

N Non-data modification

R Document read activities

W Document write activities


5.Tasks


Query Database Activity –a <DatabaseName; ...> –a <Days> [–a ACTIVITY=

<ActivityType; ...>]

where:

<DatabaseName; ...>The database files to check against. You can specify multiple databases byseparating the names with semicolons.


ACTIVITY<ActivityType; ...> specifies the type of activity to check for. If you omit thisoption, the command checks for data and non-data modification. If you list morethan one type, use semicolons to separate listed types and enclose the statementin double quotes (for example, "ACTIVITY=N;R;W").


A All activities







CLI ExampleThe following example checks for any activity in the last 90 days on the server tokyo:

¶ Using the wtmddbactivity command:wtmddbactivity tokyo "C:\data\db1.ntf;C:\data\db2.ntf" 90 ACTIVITY=A

¶ Using the wruntask command:wruntask -t "Query Database Activity" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo-a C:\data\db1.ntf;C:\data\db2.ntf -a 90 -a ACTIVITY=A

Usage NotesNone

See AlsoNone

254 Version 3.1.0

Query Log

DescriptionQueries the log files on the specified server. You can limit the search by including orexcluding a text string.



Desktop OptionsLotusDominoServer object

Target EndpointsTivoli gateway or Tivoli Management Region server


CLI Syntax¶ Using the wtmdquerylog command:

wtmdquerylog <ServerName> [–FORM=<Form; ...>] {–INC=<IncludeString; ...> |–EXC=<ExcludeString; ...>} [–DATE=<StartDate>]

where:


FORM<Form; ...> is the form. You can specify multiple forms by separating them withsemicolons. If no form is specified, all forms will be searched.

session Session

activity Activity

events Miscellaneous Events

replication Replication

routing Mail Routing

call Phone Call

incoming Phone Call - Incoming

outgoing Phone Call - Outgoing

size Size

nntp NNTP Events

usage Object Store Usage

passthru Passthru Connection


5.Tasks

INC <IncludeString> is a semicolon-separated list of strings that must be included inthe search criteria.

EXC <ExcludeString> is a semicolon-separated list of strings that are not included inthe search criteria.

DATE <StartDate> is the date in the following format: MM/DD/YYYY [hh:mm]. MM= Month, DD = Day, YYYY = Year, and optional hh = Hour, mm = Minute. Ifno date is specified, the log file is searched from a week before the current date.If no hh:mm is specified, 12:00 AM is used.


Query Log [–a FORM=<Form; ...>] {–a INC=<IncludeString> |

EXC=<ExcludeString>} [–a DATE=<StartDate>]

where:


session Session

activity Activity




call Phone Call



size Size

nntp NNTP Events



INC <IncludeString> is a semicolon-separated list of strings that must be included inthe search criteria.

EXC <ExcludeString> is a semicolon-separated list of strings that are not included inthe search criteria.

DATE <StartDate> is the date in the following format: MM/DD/YYYY [hh:mm]. MM= Month, DD = Day, YYYY = Year, and optional hh = Hour, mm = Minute. Ifno date is specified, the log file is searched from a week before the current date.If no hh:mm is specified, 12:00 AM is used.

CLI ExampleThe following example queries the log file on the server tokyo and searches the formssession and events for the strings aixserver and Unable to replicate on date 07/12/2000.

¶ Using the wtmdquerylog command:wtmdquerylog tokyo -FORM=session;events -INC=aixserver;"Unable to replicate" -DATE=07/12/2001

256 Version 3.1.0

¶ Using the wruntask command:wruntask -t "Query Log" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo-a Form=session;events -a INC=aixserver;"Unable to replicate" -a Date=07/12/2001

Usage NotesThe following information is returned:

¶ Form — Name of the form where the string was found.

¶ Field — Name of the field where the string was found.

¶ DOCID — ID of the document where the string was found.

¶ FoundEntry — The string that was found.


5.Tasks

Query NAB

DescriptionQueries the Name and Address Book (NAB) on the specified Domino server and returnsinformation about each server that is found.

Authorization RoleDomino_User



Desktop OptionsNone

CLI Syntax¶ Using the wtmdquerynab command:

wtmdquerynab <ServerName>

where:



Query NAB

CLI ExampleThe following example queries the NAB on Domino server tokyo.

¶ Using the wtmdquerynab command:wtmdquerynab tokyo

¶ Using the wruntask command:wruntask -t "Query NAB" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesThe following information is returned:

¶ Count — The number of servers located.

The following information is returned for each server:

¶ Server Name — The Domino server name.

¶ Host — The host name of the Domino server.

¶ Cluster — The name of the Domino cluster to which the server belongs. Null isreturned if the server does not belong to a cluster.

¶ Network — The name of the network the Domino server communicates with.

¶ Release — The Domino release that runs on the server.

¶ OS — The operating system that the Domino server is running.

258 Version 3.1.0

Query Restore

DescriptionReturns a list of all backed-up database versions for the specified Domino server. If COUNTis specified, it returns up to the specified number of backup versions for each database (ifpresent).

Equivalent to the Tivoli Data Protection command domdsmc query dbbackup/inactive=<yes/no>.





CLI Syntax¶ Using wtmdqueryrestore

wtmdqueryrestore <ServerName> [–DB=<DatabaseName, ...>] [–COUNT=<Count>]

where:


DB <DatabaseName, ...> is the name of a database relative to the server’s datadirectory. Use commas to separate multiple database names. If this option isomitted, all databases in all data directories are listed.

COUNT<Count> is the maximum number of backup versions to query. The default isALL.


Query Restore [–a DB=<DatabaseName, ...>] [–a COUNT=<Count>]

where:

DB <DatabaseName, ...> is the name of a database relative to the server’s datadirectory. Use commas to separate multiple database names. If this option isomitted, all databases in all data directories are listed.

COUNT<Count> is the maximum number of backup versions to query. The default isALL.

CLI ExampleThe following example returns information on backed-up databases for the server tokyo.

¶ Using the wtmdqueryrestore command:wtmdqueryrestore tokyo


5.Tasks

¶ Using the wruntask command:wruntask -t "Query Restore" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesFor each database found, the following information is returned:


¶ Backup Date — The date on which the database was last backed up

¶ Size — The size of the database in kilobytes (Kb)

¶ Active — Whether the current database is active


¶ Backup Time Stamp — Time of backup

¶ Database Title — The name of the database

260 Version 3.1.0

Query Statistics

DescriptionQueries the Domino server statistics on the specified server.





CLI Syntax¶ Using the wtmdquerystat command:

wtmdquerystat <ServerName> <StatName>

where:


<StatName>The name of a statistic. You can use the * wildcard. For example, mem.* returnsall statistics that match the mem name. You can specify statistics or statisticgroups in the format group_name.*, where all statistics that match the groupname are returned.


Query Statistics –a <StatName>

where:

<StatName>The name of a statistic. You can use the * wildcard. For example, mem.* returnsall statistics that match the mem name. You can specify statistics or statisticgroups in the format group_name.*, where all statistics that match the groupname are returned.

CLI ExampleThe following example queries the server tokyo for statistics related to memory.

¶ Using the wtmdquerystat command:wtmdquerystat tokyo mem.*

¶ Using the wruntask command:wruntask -t "Query Statistics" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo -a mem.*

Usage NotesNone


5.Tasks

Query Transaction Log

DescriptionReturns a list of the transactional log files archived on the Tivoli Storage Manager server forthe specified Domino server. To archive transactional log files, use thewtmdarchivetranslog command. Equivalent to the Tivoli Data Protection commanddomdsmc query logarchive.




Desktop OptionsNone

CLI Syntax¶ Using the wtmdquerytranslog command:

wtmdquerytranslog <ServerName>

where:



Query Transaction Log

CLI ExampleThe following example returns a list of the archived transactional log files for the servertokyo.

¶ Using the wtmdquerytranslog command:wtmdquerytranslog tokyo

¶ Using the wruntask command:wruntask -t "Query Transaction Log" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesNone

See AlsoThe following information is returned:

¶ Log Archive Date — The date on which the log was archived

¶ Name of Log File — The name of the log file

¶ A/I — Flag indicating whether the log is active or inactive

¶ Size — The size of the log file in kilobytes

¶ Logger ID — The ID of the log file

262 Version 3.1.0

Reboot Station

DescriptionReboots the operating system on the specified Domino Performance Station.

The Tivoli Management Agent process restarts automatically if it is configured as aWindows NT service. If the process is not configured as a service, you must restart itmanually.

Authorization RoleDomino_DPS_Admin

Task LibraryDomino Performance Station Tasks


Desktop OptionsNone

CLI SyntaxReboot Station

CLI ExampleThe following example shows how to run this task from the command line using thewruntask command:wruntask -t "Reboot Station" -l "Domino Performance Station Tasks"-h @DominoPerformanceStation:DPS1-Berlin

Usage NotesNone


5.Tasks

Recycle NT Server Service

DescriptionStops and restarts the Windows NT Server service on Windows NT.

The Windows NT operating system runs a server service to provide the following basicservices to all local servers:

¶ Remote procedure call (RPC) support

¶ File, print, and named pipe sharing

You can recycle the server service whenever necessary.




Desktop OptionsNone

CLI Syntax¶ Using the wtmdrecyclentsvrsvc command:

wtmdrecyclentsvrsvc <ServerName>

where:



Recycle NT Server Service

CLI ExampleThe following example stops and restarts the Windows NT Server Service on the Dominoserver named tokyo.

¶ Using the wtmdrecyclentsvrsvc command:wtmdrecyclentsvrsvc tokyo

¶ Using the wruntask command:wruntask -t "Recycle NT Server Service" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesNone

264 Version 3.1.0

Recycle Server

DescriptionStops and restarts the Domino server process on the specified Domino server. Should onlybe used on servers that are not running Windows NT.




Desktop OptionsNone

CLI Syntax¶ Using the wtmdrecycleserver command:

wtmdrecycleserver <ServerName>

where:



Recycle Server

CLI ExampleThe following example stops and restarts the Domino server process on the server namedtokyo:

¶ Using the wtmdrecycle command:wtmdrecycleserver tokyo

¶ Using wruntask command:wruntask -t "Recycle Server" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesNone


5.Tasks

Remote Console

DescriptionExecutes a Domino server command on the specified Domino server and returns the resultsin the remote console. You can run any valid Domino server command. For help on Dominoserver commands, see the Domino documentation.





CLI Syntax¶ Using the wtmdremoteconsole command:

wtmdremoteconsole <ServerName> <Command>

where:


<Command>The command to execute. Commands consisting of more than one word must beenclosed in double quotation marks.


Remote Console –a <Command>

where:


CLI ExampleThe following example starts HTTP on the server tokyo.

¶ Using the wtmdremoteconsole command:wtmdremoteconsole tokyo "start http"

¶ Using the wruntask command:wruntask -t "Remote Console" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo-a "start http"

Usage NotesNone

266 Version 3.1.0

Restore Databases

DescriptionRestores the specified database on the selected server from backups on the Tivoli StorageManager server.

If you include the date and time, the database is restored using the backup image and thetransactional log entries are restored. If you omit the date and time, the database is restoredfrom the backup image but the transactional log entries are not updated.

If you want to activate the database (bring it back on line), use the ACTIVATE option. Ifyou omit this option, the database is restored but not brought back on line; you can use thewtmdactivatedbs command to activate the restored database.

Equivalent to the Tivoli Data Protection command domdsmc restore.



Target EndpointsLotusDominoServers object


CLI Syntax¶ Using the wtmdrestoredbs command:

wtmdrestoredbs <ServerName> <DatabaseName, ...> [–DATE=<Date> | NOW][–REPLACE=Yes | No] [–ACTIVATE]

where:


<DatabaseName, ...>The database name relative to the server’s data directory. You canspecify multiple databases by separating the names with commas. Youcan use directories and wild cards.

DATE If specified, <Date> defines the date of the backup to use whenrestoring. The format is MM/DD/YYYY,HH:MM:SS, where DD=Day,MM=Month, YYYY=Year, HH=Hour, MM=Minute, and SS=Second.–DATE is specific to the preceding database and restores thetransactional log entries to the database from the date of the databasebackup until the specified date. If a date is not specified, thetransactional logs are not restored. To restore the logs up until thecurrent time, use –DATE = NOW. You can use directories and wildcards.


5.Tasks

REPLACE Specifies whether or not to replace the existing database with therestored database.

ACTIVATE If specified, activates the database after the restore completes. If you donot select this option, the database is restored but not activated.


Restore Databases –a <DatabaseName, ...> [–a DATE=<Date> | NOW] [–aREPLACE=

Yes | No] [–a ACTIVATE]

where:

<DatabaseName, ...>The database name relative to the server’s data directory. You canspecify multiple databases by separating the names with commas. Youcan use directories and wild cards.

DATE If specified, <Date> defines the date of the backup to use whenrestoring. The format is MM/DD/YYYY,HH:MM:SS, where DD=Day,MM=Month, YYYY=Year, HH=Hour, MM=Minute, and SS=Second.–DATE is specific to the preceding database and restores thetransactional log entries to the database from the date of the databasebackup until the specified date. If a date is not specified, thetransactional logs are not restored. To restore the logs up until thecurrent time, use –DATE = NOW. You can use directories and wildcards.

REPLACE Specifies whether or not to replace the existing database with therestored database.

ACTIVATE If specified, activates the database after the restore completes. If you donot select this option, the database is restored but not activated.

CLI ExampleThe following example restores databases db1.ntf and db2.ntf on server tokyo.

¶ Using the wtmdrestoredbs command:wtmdrestoredbs tokyo c:\data\db1.ntf,c:\data\db2.ntf

¶ Using the wruntask command:wruntask -t "Restore Databases" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo-a C:\data\db1.ntf,C:\data\db2.ntf

Usage NotesNone

268 Version 3.1.0

Selective Backup

DescriptionPerforms a selective backup of the specified databases on the specified Domino server.

Unlike an incremental backup, it is not necessary for the database to meet a set of criteriabefore being backed up. A selective backup unconditionally backs up all specified databases.

Equivalent to the Tivoli Data Protection command domdsmc selective.





CLI Syntax¶ Using the wtmdselectivebackup command:

wtmdselectivebackup <ServerName> <DatabaseName, ...>

where:




Selective Backup –a <DatabaseName, ...>

where:


CLI ExampleThe following example backs up databases db1.ntf and db2.ntf on Domino server tokyo.

¶ Using the wtmdselectivebackup command:wtmdselectivebackup tokyo c:\data\db1.ntf, c:\data\db2.ntf

¶ Using the wruntask command:wruntask -t "Selective Backup" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo-a C:\data\db1.ntf, C:\data\db2.ntf

Usage NotesNone


5.Tasks

Start Engine

DescriptionStarts the local Tivoli Enterprise Console event engine on the specified server.

The Tivoli Manager for Domino event engine is a standalone version of the Tivoli EnterpriseConsole event engine. The standalone engine analyzes all event information on a Dominoserver and sends significant event information to the Tivoli Enterprise Console. Becauseevent data is filtered locally, the Domino server sends less event information to the TivoliEnterprise Console for processing, thereby decreasing network traffic and improvingresponse time.




Desktop OptionsNone

CLI Syntax¶ Using the wtmdstartengine command:

wtmdstartengine <ServerName>

where:



Start Engine

CLI ExampleThe following example starts the event engine on server tokyo:

¶ Using the wtmdstartengine command:wtmdstartengine tokyo

¶ Using the wruntask command:wruntask -t "Start Engine" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesNone

270 Version 3.1.0

Start Monitors

DescriptionStarts monitoring on the specified server.




Desktop OptionsNone

CLI Syntax¶ Using the wtmdstartmonitors command:

wtmdstartmonitors <ServerName>

where:



Start Monitors

CLI ExampleThe following example starts monitoring on the server tokyo:

¶ Using the wtmdstartmonitors command:wtmdstartmonitors tokyo

¶ Using the wruntask command:wruntask -t "Start Monitors" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesNone


5.Tasks

Start Server

DescriptionStarts the Domino server process on the specified server.




Desktop OptionsNone

CLI Syntax¶ Using the wtmdstartserver command:

wtmdstartserver <ServerName>

where:



Start Server

CLI ExampleThe following example starts the Domino server process on server tokyo:

¶ Using the wtmdstartserver command:wtmdstartserver tokyo

¶ Using the wruntask command:wruntask -t "Start Server" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

272 Version 3.1.0

Start Station

DescriptionStarts the controller and its probes on the specified Domino Performance Station.




Desktop OptionsNone

CLI Syntax¶ Using the wdpsstart command:

wdpsstart <DPSName> [–c]

where:

<DPSName> The name of the Domino Performance Station.

[–c] Cleans up the cache and cancels any pending probe tests.


Start Station

CLI ExampleThe following example starts Domino Performance Station DPS1-Berlin.

¶ Using the wdpsstart command:wdpsstart DPS1-Berlin

¶ Using the wruntask command:wruntask -t "Start Station" -l "Domino Performance Station Tasks"-h @DominoPerformanceStation:DPS1-Berlin

Usage NotesNone


5.Tasks

Start Station Monitors

DescriptionStarts monitors on the specified Domino Performance Station.




Desktop OptionsNone

CLI Syntax¶ Using the wdpsstartmonitors command:

wdpsstartmonitors <DPSName>

where:



Start Station Monitors

CLI ExampleThe following example starts monitoring on the Domino Performance Station namedDPS1-Berlin.

¶ Using the wdpsstartmonitors command:wdpsstartmonitors DPS1-Berlin

¶ Using the wruntask command:wruntask -t "Start Station Monitors" -l "Domino Performance Station Tasks"-h @DominoPerformanceStation:DPS1-Berlin

Usage NotesNone

274 Version 3.1.0

Stop Engine

DescriptionStops the Tivoli Enterprise Console event engine on the specified server.





Desktop OptionsNone

CLI Syntax¶ Using the wtmdstopengine command:

wtmdstopengine <ServerName>

where:



Stop Engine

CLI ExampleThe following example stops the event engine on server tokyo:

¶ Using the wtmdstopengine command:wtmdstopengine tokyo

¶ Using the wruntask command:wruntask -t "Stop Engine" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesNone


5.Tasks

Stop Monitors

DescriptionStops monitoring on the specified server. The addin will be notified when an asynch monitorstops.




Desktop OptionsNone

CLI Syntax¶ Using the wtmdstopmonitors command:

wtmdstopmonitors <ServerName>

where:



Stop Monitors

CLI ExampleThe following example stops monitoring on the server tokyo:

¶ Using the wtmdstopmonitors command:wtmdstopmonitors tokyo

¶ Using the wruntask command:wruntask -t "Stop Monitors" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesNone

276 Version 3.1.0

Stop Server

DescriptionStops the Domino server process on the specified server.

Equivalent to the Lotus Domino console quit command.




Desktop OptionsNone

CLI Syntax¶ Using the wtmdstopserver command:

wtmdstopserver <ServerName>

where:



Stop Server

CLI ExampleThe following example stops server tokyo.

¶ Using the wtmdstopserver command:wtmdstopserver tokyo

¶ Using the wruntask command:wruntask -t "Stop Server" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesNone


5.Tasks

Stop Station

DescriptionStops the specified Domino Performance Station controller and its probes. This commandstops only the Domino Performance Station controller and does not affect other processesrunning on the client.




Desktop OptionsNone

CLI Syntax¶ Using the wdpsstop command:

wdpsstop <DPSName>

where:



Stop Station

CLI ExampleThe following example stops the Domino Performance Station named DPS1-Berlin:

¶ Using the wdpsstop command:wdpsstop DPS1-Berlin

¶ Using the wruntask command:wruntask -t "Stop Station" -l "Domino Performance Station Tasks"-h @DominoPerformanceStation:DPS1-Berlin

Usage NotesNone

See AlsoDomino Performance Station tasks: Start Station

278 Version 3.1.0

Stop Station Monitors

DescriptionStops monitoring on the specified Domino Performance Station.




Desktop OptionsNone

CLI Syntax¶ Using the wdpsstopmonitors command:

wdpsstopmonitors <DPSName>

where:



Stop Station Monitors

CLI ExampleThe following example stops monitoring on the Domino Performance Station namedDPS1-Berlin.

¶ Using the wdpsstopmonitors command:wdpsstopmonitors DPS1-Berlin

¶ Using the wruntask command:wruntask -t "Stop Station Monitors" -l "Domino Performance Station Tasks"-h @DominoPerformanceStation:DPS1-Berlin

Usage NotesNone


5.Tasks

Verify Mail

DescriptionChecks all Name and Address Book (NAB) mail user entries against the mail files that existon the specified Domino server and returns a list of all mail files without NAB entries.




Desktop OptionsNone

CLI Syntax¶ Using the wtmdverifymail command:

wtmdverifymail <ServerName>

where:



Verify Mail

CLI ExampleThe following example checks NAB user entries against the mail files on the server tokyo:

¶ Using the wtmdverifymail command:wtmdverifymail tokyo

¶ Using the wruntask command:wruntask -t "Verify Mail" -l "Domino Server Tasks" -h @LotusDominoServer:tokyo

Usage NotesFor each mail file without an NAB entry, the following data is returned.

¶ MFNAME — Specifies the names of the mail files without NAB entries.

280 Version 3.1.0

Domino Performance Station Commands

This chapter describes the Domino Performance Station commands.

A Domino Performance Station is a Lotus Notes 5.0 client that can be used to measure theperformance of a Domino server. You can find more information about Domino PerformanceStations in the Tivoli Manager for Domino User’s Guide.

All Domino Performance Station commands are run from a Tivoli managed node.

Table 5 summarizes the Domino Performance Station commands.

Table 5. Domino Performance Station CommandsCommand Description

wdpsaddserver Adds a server that can be probed by the specified DominoPerformance Station.

wdpscreate Creates a new Domino Performance Station object and installs therequired software on the specified endpoint.

wdpsdelete Deletes the specified Domino Performance Station and all relatedsoftware on the specified endpoint.

wdpsintegrity Queries the specified Domino Performance Station for its currentstatus.

wdpsprobeonce Probes the specified Domino server once and returns the results.

wdpsprobestatus Queries a Domino Performance Station for results from thewdpsprobeonce monitor.

wdpsqueryservers Queries the specified Domino Performance Station to determine whichservers can be probed from that station.

wdpsreboot Reboots the specified Domino Performance Station.

wdpsremoveserver Removes a server from the list of servers that can be probed by thespecified Domino Performance Station.

wdpsstart Starts the specified Domino Performance Station.

wdpsstartengine Starts the Tivoli Event Engine on the specified Domino PerformanceStation.

wdpsstartmonitors Starts monitoring on the specified Domino Performance Station.

wdpsstop Stops the specified Domino Performance Station.

wdpsstopengine Stops the Tivoli Event Engine on the specified Domino PerformanceStation.

wdpsstopmonitors Stops monitoring on the specified Domino Performance Station.

6


6.D

om

ino

Perfo

rman

ceS

tation

Co

mm

and

s

To run Domino Performance Station commands, you must have one of the followingauthorization roles:

¶ Domino_DPS_Admin

¶ Domino_DPS_User

Table 6 lists the commands that can be run by each authorization role:

Table 6. Authorization Roles for Domino Performance Station CommandsAuthorization Role Command

Domino_DPS_Admin All

Domino_DPS_User wdpsintegritywdpsprobeoncewdpsprobestatuswdpsqueryservers

282 Version 3.1.0

wdpsaddserver

DescriptionAdds the specified server to the list of servers that can be probed by the specified DominoPerformance Station. You must specify a value for each variable.


CLI Syntaxwdpsaddserver <DPSName> <ServerName> <HostName> <IDPathFile> <Password><MailDB>

where:



<HostName> The host name or IP address of the machine on which the Domino serverresides.

<IDPathFile> The path and filename of the Lotus Notes user ID file used to probe theDomino server. You can enter the path and filename as absolute or relativeto the Lotus Notes data directory.

<Password> The password to use with the ID file. You can enter the <Password> or –p.If you enter –p, you are prompted to enter the password after you pressenter.

<MailDB> The relative path to the user’s mail database on the server.

CLI ExampleThe following example adds the server tokyo to Domino Performance Station DPS1-Berlin:wdpsaddserver DPS1-Berlin tokyo sp.acme.dynamite.com c:\idfiles\testuser.id Cartoonc:\lotus\notes\mail

Return ValuesIf successful, the command returns the message Success.

If unsuccessful, the command returns one of the following error messages:

¶ ID File Not Found — The ID file you specified could not be found.

¶ Server Already Supported — The server you specified is already configured forprobing by this station.


6.D

om

ino

Perfo

rman

ceS

tation

Co

mm

and

s

wdpscreate

DescriptionThis command creates a new Domino Performance Station and installs all of the requiredsoftware on the endpoint.

Before running this command, install the Lotus Notes 5.0 client on the endpoint. Also,include the full path and file name of the notes.ini file. This file is created when you installthe Lotus Notes client.

The name you assign to the new Domino Performance Station is used by other DominoPerformance Station commands to refer to this station. Use a name that you will recognize,such as ServerNameDPS.

To achieve accurate probing, your Domino Performance Stations should be Notes clientcomputers that are dedicated to running probe tests. This prevents distortion introduced byusers performing unrelated activities. A dedicated station should reside on the same subnet asthe server or servers it tests.


CLI Syntaxwdpscreate <DPSName> <EndpointName> <INIPathFile>

where:

<DPSName> The name you are assigning to the new Domino Performance Station.

<EndpointName>The name of the endpoint on which to create the new Domino PerformanceStation.

<INIPathFile> The fully qualified path and file name of the notes.ini file on the client.

CLI ExampleThe following example creates DPS DPS1-Berlin on endpoint jakarta.wdpscreate DPS1-Berlin jakarta C:\lotus\notes.ini



¶ Invalid INI file specified — The .ini file you specified could not be found. Ensure thatyou entered the path and file name correctly.

¶ Station Already Exists — The name you assigned to the station is already in use.Assign a different name to the new station.

¶ Endpoint not running NT — The endpoint is not running Windows NT. DominoPerformance Stations must run on Windows NT clients.

284 Version 3.1.0

wdpsdelete

DescriptionDeletes the specified Domino Performance Station and all of the associated software from itsendpoint.


CLI Syntaxwdpsdelete <DPSName>

where:


CLI ExampleThe following example deletes Domino Performance Station DPS1-Berlin:wdpsdelete DPS1-Berlin


The following message indicates that the station you specified does not exist: ABA000000Station does not exist


6.D

om

ino

Perfo

rman

ceS

tation

Co

mm

and

s

wdpsintegrity

DescriptionQueries the status of the specified Domino Performance Station. Returns the status of thestation controller and probes currently running on it.

Authorization RoleDomino_DPS_Admin or Domino_DPS_User

CLI Syntaxwdpsintegrity <DPSName>

where:


CLI ExampleThe following example checks integrity on the Domino Performance Station DPS1-Berlin:wdpsintegrity DPS1-Berlin


If unsuccessful, the command returns an error messages. The state of the components is oneof the following:

¶ Up — Indicates the Domino Performance Station component is running.

¶ Down — Indicates the Domino Performance Station component is not running.

¶ Recurring Error — Indicates that there are errors in the transactions of the probe.

The following error message shows that the controller and the probe are not running.Performing integrity check

Component State========================================Controller Down000000.serverA Down

286 Version 3.1.0

wdpsprobeonce

DescriptionUse this command to probe the specified Domino Performance Station for the specifiedtransaction and to retrieve the results. You must specify the station name, the name of theDomino server, and the function to be probed. Include any variable information needed forthe function you specify. You can also enter a timeout value for the probe.

The command returns the probe output, which indicates that the transaction executedsuccessfully, and returns any other relevant data, such as the amount of time to complete thetransaction and a probe ID. If the command times out, it returns the probe ID. Use the probeID number to retrieve the probe information by running the wdpsprobestatus command.You can define only one probe function per command execution.


CLI Syntaxwdpsprobeonce <DPSName> <ServerName> {DPSRoundTripMail <MessageSize><DestinationServer> <DestinationAddress> DPSReplicateLocal <RemoteDatabase> |DPSDatabaseAccess <DatabaseName> | DPSWebAccess <URL> <ErrorText> |DPSNABSearch <DatabaseName> <View> <Pattern> | DPSCalendarEntry |DPSNetEcho <Protocol> <PacketSize>} [–t = <Seconds>]

where:



DPSRoundTripMailThe time required to send a mail message of the specified size from thestation to a Domino server and back. <MessageSize> is the size, in bytes, ofthe test message. <DestinationServer> is the name of the server that is hometo the destination address. <DestinationAddress> is the target recipient of thetest mail message.

DPSReplicateLocalReplicates a server database to a Notes client. <RemoteDatabase> is the pathand file name of the remote database to replicate, relative to the Dominodata directory.

DPSDatabaseAccessAccesses the specified database. <DatabaseName> is the path and name ofthe database.

DPSWebAccessAccesses the Web page specified in the URL. <URL> is the URL of the Webpage to be opened. <ErrorText> is the error text on which to search. If thetext contains spaces, enclose it in quotes. (If the error text is not found, thetransaction completed successfully.)

DPSNABSearchSearches the Name and Address Book (NAB) of the specified databasewithin the specified view for the specified pattern. <DatabaseName> is the


6.D

om

ino

Perfo

rman

ceS

tation

Co

mm

and

s

path and file name of the NAB database to search. <View> is the NAB viewto search. <Pattern> is the pattern the probe searches for in the NABdatabase.

DPSCalendarEntryCreates an entry in the calendar for the test user. The entry is deleted whenthe probe is completed.

DPSNetEcho Sends a packet of binary data from the Domino Performance Station to theDomino server. <Protocol> is the name of the protocol to use for the testpacket. Enter tcp for TCP/IP or udp for UDP. <PacketSize> is the packetsize in bytes.

–t <Seconds> is the number of seconds before timeout occurs. Set this optionalparameter to end the probe if it does not complete in the number of secondsspecified.

CLI ExampleThe following example probes Domino Performance Station DPS1-Berlin:wdpsprobeonce DPS1-Berlin D01ML233 DPSReplicateLocal mail3/aaronzz.nsf

Return ValuesIf successful, the command returns the probe output, which is specific to each probe. Thefollowing example shows successful results of probe output. If the probe times out, it returnsa probe ID. You can check the status of the probe ID using wdpsprobestatus command.Probing ... (This might take a few minutes)

Transaction breakdown========================================Main : Ok : 9.353 sec

Success


¶ Server not supported — The server’s configuration information has not been added tothis station using the wdpsaddserver command.

¶ Invalid Probe Specified — You specified an invalid probe function. In most cases, youentered the name of the function incorrectly.

288 Version 3.1.0

wdpsprobestatus

DescriptionQueries a Domino Performance Station for results from a wdpsprobeonce test. You mustknow the probe ID, which is returned when the wdpsprobeonce command times out.

If the data from the original probe is available, the data is returned. If the probe has expired,a message to that effect is returned. If the probe has not yet returned data, a message to theeffect is returned.


CLI Syntaxwdpsprobestatus <DPSName> <ProbeID>

where:


<ProbeID> The ID assigned to the probe. You receive this ID when you run a probeusing the wdpsprobeonce command and it times out.

CLI ExampleThe following example probes the Domino Performance Station named DPS1-Berlin usingprobe ID 1102.wdpsprobestatus DPS1-Berlin 1102

Return ValuesOne of the following messages is returned from the original probe.

¶ Data Currently Not Available — The data from the probe is not yet available.

¶ Probe No Longer Running — The probe expired without returning any data.


6.D

om

ino

Perfo

rman

ceS

tation

Co

mm

and

s

wdpsqueryservers

DescriptionQueries the specified Domino Performance Station to determine which Domino servers canbe probed from that station.


CLI Syntaxwdpsqueryservers <DPSName>

where:


CLI ExampleThe following example queries the Domino Performance Station DPS1-Berlin for theservers that can be probed from that station.wdpsqueryservers DPS1-Berlin

Return ValuesThis command returns the following output:Count: 2

Server Host ID File Mail DB----------------------------------------------------------------Speedy/Acme sp.dev.acme.com probe0.id mail/probe0.nsfSlowpoke/Acme sl.dev.acme.com d:\ids\rtp.id mail/rtp.nsf

where:

¶ Count — The number of Domino servers that can be probed.

¶ Server — The names of the servers that can be probed.

¶ Host — The host machines on which the servers are running.

¶ ID File — The test user ID file. A test Notes User ID is designated to run probesagainst this server. This ID File must be found on the Domino Performance Station.

¶ Mail DB — The mail database used in testing the server.

290 Version 3.1.0

wdpsreboot

DescriptionReboots the Domino Performance Station workstation’s operating system. The TivoliManagement Agent process restarts automatically if it is configured as a Windows NTservice. If the process is not configured as a service, the process will not restartautomatically and you must restart the process manually.


CLI Syntaxwdpsreboot <DPSName>

where:


CLI ExampleThe following example reboots the Domino Performance Station named DPS1-Berlin:wdpsreboot DPS1-Berlin

Return ValuesIf successful, the command returns Success.

If unsuccessful, the command returns an error message.


6.D

om

ino

Perfo

rman

ceS

tation

Co

mm

and

s

wdpsremoveserver

DescriptionRemoves the specified server from the list of servers that can be probed by the specifiedDomino Performance Station.


CLI Syntaxwdpsremoveserver <DPSName> <ServerName>

where:



CLI ExampleThe following example removes the server tokyo from the list of servers that can be probedby Domino Performance Station DPS1-Berlin:wdpsremoveserver DPS1-Berlin tokyo


If unsuccessful, the command returns the following message:

¶ Server Not Supported — The server you specified is not supported by this station.Specify a different station.

292 Version 3.1.0

wdpsstart

DescriptionStarts the controller and its probes on the specified Domino Performance Station.


CLI Syntaxwdpsstart <DPSName> [–c]

where:


[–c] Cleans up the cache and cancels any pending probe tests.

CLI ExampleThe following example starts Domino Performance Station DPS1-Berlin.wdpsstart DPS1-Berlin


If unsuccessful, the following message is returned:

¶ Already Running — The specified Domino Performance Station controller is alreadyrunning.


6.D

om

ino

Perfo

rman

ceS

tation

Co

mm

and

s

wdpsstartengine

DescriptionStarts the local event engine on the specified Domino Performance Station. The event enginemonitors event data and relays it to the Tivoli Enterprise Console.


CLI Syntaxwdpsstartengine <DPSName>

where:


CLI ExampleThe following example starts the event engine on Domino Performance StationDPS1-Berlin.wdpsstartengine DPS1-Berlin


If unsuccessful, the command returns the following error message:

¶ Engine Already Started — The event engine on the specified station is alreadyrunning.

294 Version 3.1.0

wdpsstartmonitors

DescriptionStarts monitors on the specified Domino Performance Station.


CLI Syntaxwdpsstartmonitors <DPSName>

where:


CLI ExampleThe following example starts monitoring on the Domino Performance Station namedDPS1-Berlin.wdpsstartmonitors DPS1-Berlin



¶ Monitoring Already Started — Probes have already been started on the specifiedstation.


6.D

om

ino

Perfo

rman

ceS

tation

Co

mm

and

s

wdpsstop

DescriptionStops the specified Domino Performance Station controller and its probes. This commandstops only the Domino Performance Station controller and does not affect other processesrunning on the client.


CLI Syntaxwdpsstop <DPSName>

where:


CLI ExampleThe following example stops the Domino Performance Station named DPS1-Berlin:wdpsstop DPS1-Berlin


If unsuccessful, the command returns the following error message.

¶ Engine Already Stopped — The Domino Performance Station controller is alreadystopped.

296 Version 3.1.0

wdpsstopengine

DescriptionStops the local Tivoli Event Console event engine on the specified Domino PerformanceStation.


CLI Syntaxwdpsstopengine <DPSName>

where:


CLI ExampleThe following example stops the event engine on Domino Performance StationDPS1-Berlin:wdpsstopengine DPS1-Berlin

Return ValuesIf successful, the command returns the Success message.


¶ Engine Already Stopped — The event engine on the Domino Performance Station youspecified is already stopped.


6.D

om

ino

Perfo

rman

ceS

tation

Co

mm

and

s

wdpsstopmonitors

DescriptionStops monitoring on the specified Domino Performance Station.


CLI Syntaxwdpsstopmonitors <DPSName>

where:


CLI ExampleThe following example stops monitoring on the Domino Performance Station namedDPS1-Berlin.wdpsstopmonitors DPS1-Berlin



¶ Monitoring Already Stopped — Probes have already been stopped on the specifiedstation.

298 Version 3.1.0

Domino Server Commands

This chapter describes the Tivoli Manager for Domino server commands.

All Domino server commands are run from a Tivoli gateway or Tivoli Management Regionserver.

Before running Domino server commands, you must install and configure the Dominoserver. In addition, you must establish the Tivoli environment.

Table 7 summarizes the Tivoli Manager for Domino server commands.

Table 7. Domino Server CommandsCLI Name Task Name Description

wtmdaclmod Modify DatabaseACLs

Modifies the Access Control List (ACL) entries for thespecified database on the specified Domino server

wtmdactivatedbs Activate Database Activates all restored databases on the selectedDomino server

wtmdarchivetranslog ArchiveTransactionalLogs

Archives the transactional logs on the specifiedDomino server

wtmdchkdbcorruption Check DatabaseCorruption

Checks for corruption in the specified database on thespecified Domino server

wtmdcheckhealth Check Health Checks the health of all Domino processes running onthe specified Domino server

wtmdchkinactusers Check InactiveUsers

Checks for inactive users in the specified number ofdays on the specified Domino server

wtmdcheckrep Check Replication Verifies that the database was replicated in accordancewith the schedule posted in the NAB on the specifiedserver

wtmdcleandb Clean Database Removes specified entries from the specified database

wtmdcreateserver Not accessiblefrom the desktop

Creates a new Domino server object

wtmddbactivity Query DatabaseActivity

Checks the specified databases on the specifiedDomino server for the specified activities

wtmddeletemail Delete Mail Deletes the first mail message in the specified mailboxon the specified Domino server

wtmddeleteserver Delete Server Deletes an existing Domino server object

wtmdgetacl Get ACL Returns a list of all ACL entries for a specifieddatabase on the specified Domino server

7


7.D

om

ino

Server

Co

mm

and

s

Table 7. Domino Server Commands (continued)CLI Name Task Name Description

wtmdinactivatetranslog InactivateTransactionLogging

Deletes all inactive transactional logs on the specifiedDomino server

wtmdincrementalbackup IncrementalBackup

Performs an incremental backup on the specifieddatabase on the specified Domino server

wtmdlocateserver Locate Server Locates any configured Domino servers on thespecified endpoint

wtmdmailwaiting Mail Waiting Returns a list of all the currently waiting mail on thespecified Domino server

wtmdpurgemail Purge Mail Purges specified mail on the specified Domino server

wtmdqueryactivate Query Activate Returns a list of all databases that have been restoredbut not yet activated on the specified Domino server

wtmdquerybackup Query Backup Returns a list of all NTF and NSF database files on thespecified Domino server

wtmdquerydoc Query Document Returns the specified log file from the specifiedDomino server

wtmdquerylog Query Log Queries the log file on the specified Domino server

wtmdquerynab Query NAB Queries the Name and Address Book (NAB) on thespecified Domino server

wtmdquerytranslog Query TransactionLog

Returns a list of archived transactional logs fromspecified Domino server

wtmdqueryrestore Query Restore Returns a list of all databases that have been backedup on the specified Domino server

wtmdquerystat Query Statistics Queries the specified statistics on the specified Dominoserver

wtmdrecyclentsvrsvc Recycle NTServer Service

Stops and restarts the Domino server process on thespecified Windows NT server

wtmdrecycleserver Recycle Server Stops and restarts the Domino server process on thespecified Domino server

wtmdremoteconsole Check RemoteConsole

Executes a command on the console of the specifiedDomino server

wtmdrestoredbs Restore Database Restores the specified databases on the specifiedDomino server

wtmdselectivebackup Selective Backup Backs up the specified database on the specifiedDomino server

wtmdstartengine Start Engine Starts the Tivoli Enterprise Console event engine onthe specified Domino server

wtmdstartmonitors Start Monitors Starts the Distributed Monitoring engine on thespecified Domino server

wtmdstartserver Start Server Starts the Domino server process on the specifiedDomino server

wtmdstopengine Stop Engine Stops the Tivoli Enterprise Console event engine onthe specified Domino server

wtmdstopmonitors Stop Monitors Stops the Distributed Monitoring engine on thespecified Domino server

300 Version 3.1.0

Table 7. Domino Server Commands (continued)CLI Name Task Name Description

wtmdstopserver Stop Server Stops the Domino server process on the specifiedDomino server

wtmdverifymail Verify Mail Compares NAB mail user entries against the mail fileson the specified Domino server

To run Domino server commands, you must have the appropriate authorization role. Notethat authorization roles are not hierarchical in structure; the user must be specificallyassigned a role to have the privileges of that role. For example, a Domino_Admin must alsobe assigned as a Domino_User in order to run commands. Tivoli Manager for Domino usesthe following authorization roles:

¶ Domino_Admin

¶ Domino_User

¶ Domino_TDP_Admin

Table 8 lists the commands that can be run by each authorization role:

Table 8. Authorization Roles for Server CommandsAuthorization Role Command

Domino_Admin wtmdaclmod, wtmdcleandb, wtmdcreateserver, wtmddeletemail,wtmddeleteserver, wtmdgetacl, wtmdpurgemail, wtmdquerylog,wtmdrecycleserver, wtmdrecyclentsvrsvc, wtmdremoteconsole,wtmdstartserver, wtmdstopserver, Start Engine, Stop Engine, StartMonitors, Stop Monitors

Domino_User wtmdchkdbcorruption, wtmdcheckhealth, wtmdchkinactusers,wtmdcheckrep, wtmddbactivity, wtmdlocateserver, wtmdmailwaiting,wtmdquerydoc, wtmdquerynab, wtmdquerystat, wtmdverifymail

Domino_TDP_Admin wtmdactivatedbs, wtmdarchivetranslog, wtmdinactivatetranslog,wtmdincrementalbackup, wtmdqueryactivate, wtmdquerybackup,wtmdqueryrestore, wtmdquerytranslog, wtmdrestoredbs,wtmdselectivebackup


7.D

om

ino

Server

Co

mm

and

s

wtmdaclmod

DescriptionModifies the Access Control List (ACL) entries for the specified databases on the specifiedserver. The command returns a list of all the ACLs for the database specified.


CLI Syntaxwtmdaclmod <ServerName> <DatabaseName> <argument>

where:

<ServerName>Specifies the name of the Domino server.

<DatabaseName>Specifies the name of the database whose ACL you want to modify. Use semicolons toseparate multiple database names.

<argument>Specifies a change to make in the ACL.

[ADD=<user_name, ...>]Adds the specified username to the ACL.

[CHG=<user_name, ...>]Use with the OLD parameter to change old_username to the new_usernamespecified by the CHG parameter.

[CLRP=<number, ...>]Clears the listed privilege numbers in the ACL.

[DEL=<user_name, ...>]Deletes the specified username from the ACL. If used, all other options areignored.

[INVP=<number, ...>]Inverts the listed privilege numbers in the ACL.

[LEVEL = {NOACCESS | DEPOSITOR | READER | AUTHOR | EDITOR |DESIGNER | MANAGER}]

Defines the access level. You can assign only one option.

NOACCESSThe user does not have access to the database.

DEPOSITORThe user can create documents, but documents in the database viewsare not visible.

READERThe user can read documents in a database.

AUTHORThe user can create documents and edit documents that he or she hascreated.

302 Version 3.1.0

EDITORThe user can create documents and edit all documents.

DESIGNERThe user can modify all database design elements and can modifyreplication formulas, and can create a full text index. Designers can alsoperform all operations that the Editor, Author, Reader, and Depositoraccess levels perform.

MANAGERThe user can modify ACL settings, encryption settings, and replicationssettings, and also can delete a database, as well as perform alloperations that the other access levels perform.

[MOD=<user_name, ...>]Modifies the ACL of username.

[OLD=<user_name, ...>]Use with the CHG parameter to change old_username to the new_usernamespecified by the CHG parameter.

[SETP=<number, ...>]Sets the listed privilege numbers in the ACL.

[FLAG=AUTHOR_NOCREATE SERVER NODELETE CREATE_PRAGENTCREATE_PRFOLDER PERSON GROUP CREATE_FOLDERCREATE_LOTUSSCRIPT PUBLICREADER PUBLICWRITERMONITORS_DISALLOWED RELEASE_LOCKED_DOCADMIN_READERAUTHOR ADMIN_SERVER]

Defines access flags. You can use any or all of the options listed.

AUTHOR_NOCREATEAuthors are not permitted to create new notes.

SERVERThe entity is a server.

NODELETEThe user cannot delete notes.

CREATE_PRAGENTThe user can create personal agents.

CREATE_PRFOLDERThe user can create personal folders.

PERSONThe entry is a person.

GROUPThe entry is a group.

CREATE_FOLDERThe user can create and update shared views and folders.

PUBLICREADERThe user can read public notes.

CREATE_LOTUSSCRIPTThe user can create a LotusScript.


7.D

om

ino

Server

Co

mm

and

s

PUBLICWRITERThe user can write public notes.

MONITORS_DISALLOWEDThe user cannot register monitors for this database.

RELEASE_LOCKED_DOCThe user can release locked documents.

ADMIN_READERAUTHORThe administration server can modify reader and author fields indatabase.

ADMIN_SERVERThe entry is an administration server.

CLI ExampleThe following command adds a user Joe Brown to the ACL of the tokyo server in theAsia-Pacific domain. Note that the fully qualified format for a name in Lotus Notes is validin this context. The LEVEL argument gives the user the Designer privilege for names.nsf,and the FLAG argument defines the user as a Person in Notes.wtmdaclmod tokyo/Asia-Pacific names.nsf ADD="Joe Brown/Asia-Pacific" LEVEL=DESIGNERFLAG=PERSON

Return ValuesThis command returns a list of all the ACLs for the database specified.

If unsuccessful, the command returns one or more of the following error codes:

¶ Unknown User or Group — You specified an unknown user or group name.

¶ Invalid Privilege — You specified an invalid privilege.

¶ Invalid Level — You specified an invalid access level.

¶ Invalid Flags — You specified invalid flags.

¶ Cannot Remove and Modify – You illegally specified the –REMOVE flag with the–PRIV, –LEVEL, or –FLAGS options.

See Alsowtmdgetacl

304 Version 3.1.0

wtmdactivatedbs

DescriptionBrings restored databases online (“activates” the databases) for use by the specified Dominoserver.

If the database is logged, use the –DATE option to restore all transactional log files up tothe date and time you specify.

Equivalent to the Tivoli Data Protection command domdsmc activatedbs/applylogs=date_time.


CLI Syntaxwtmdactivatedbs <ServerName> [–DATE=<DateTime> | NOW]

where


DATE <DateTime> is the date up to which you want to restore transactional logs. Ifincluded, this option restores the transactional log entries to the databasefrom the date of the last database restoration up to the date specified. If thedate is not specified, the transactional logs are not restored. To restore thelogs up until the current time, use –DATE=NOW.

The format for date and time is MM/DD/YYYY,HH:MM:SS, whereMM=month, DD=day, YYYY=year, HH=hour, MM=minute, and SS=second.

CLI ExampleThe following example activates the server tokyo and restores transactional log entriescreated before September 1, 2001 at 13:45:30.wtmdactivatedbs tokyo -DATE=09/01/2001,13:45:30


If unsuccessful, the following error message is returned:

¶ Database not activated — The database you specified is locked by the server.


7.D

om

ino

Server

Co

mm

and

s

wtmdarchivetranslog

DescriptionArchives Domino transactional log files if archival logging is in effect on the Dominoserver. It first checks if any log files are ready for archiving, then archives the files on theTivoli Storage Manager server.

Equivalent to the Tivoli Data Protection command domdsmc archivelogs.


CLI Syntaxwtmdarchivetranslog <ServerName>

where:


CLI ExampleThe following example archives transactional log files on server tokyo.wtmdarchivetranslog tokyo


306 Version 3.1.0

wtmdcheckhealth

DescriptionReturns information on the health of all Domino and Tivoli Manager for Domino processesrunning on the specified Domino server. Checks the status (Running, Stopped, Hung, orUnconfigured) of the following Domino processes: Tivoli Addin, Core Database Server,Event Monitor, Billing Manager, Cluster Database Directory, Cluster Replicator, HTTPServer, Web Retriever, SMTP Server, NNTP Server, LDAP Server, POP3 Server, IMAPServer, Replication Server, Mail Router, Statistics Monitor, Agent Manager, Admin Process,Schedule Manager, and Calendar Manager.


CLI Syntaxwtmdcheckhealth <ServerName> [–TASK=<Task, ...>] [–NAME=<Name, ...>]

where:


TASK <Task, ...> is the exact name of any third-party addin task in the notes.inifile. You can specify multiple tasks by separating them with commas.

NAME <Name, ...> is the exact name of any third-party addin task on the serverconsole. You can specify multiple tasks by separating them with commas.

CLI ExampleThe following example checks the health of processes on Domino server tokyo.wtmdcheckhealth tokyo -TASK=caddin -NAME=custaddin

Return ValuesThis command returns a list of the Domino and Tivoli Manager for Domino processes andtheir states (Running, Stopped, Hung, or Unconfigured). The following is an example of asuccessful return of this command.Tivoli Addin RunningAgent Manager RunningAdmin Process RunningSchedule Manager RunningCalendar Manager RunningCore database server RunningStatistics Monitor RunningMail Router RunningReplication Server RunningIMAP Server RunningPOP3 Server RunningLDAP Server RunningNNTP Server RunningSMTP Server RunningWeb Retriever RunningCluster Replicator RunningHTTP Server RunningCluster Database Directory RunningBilling Manager RunningEvent Monitor Running


7.D

om

ino

Server

Co

mm

and

s

wtmdcheckrep

DescriptionChecks whether a Domino server replicated according to the schedule defined by its nameand address book (NAB).


CLI Syntaxwtmdcheckrep <ServerName> {INC=<IncludeString> | EXC=<ExcludeString>}[DATE=<StartDate>]

where:


INC <IncludeString> is a semicolon-separated list of strings that must be included in thesearch criteria for the replication report.

EXC <ExcludeString> is a semicolon-separated list of strings that must be excluded in thesearch criteria for the replication report.

DATE <StartDate> is the date and time on which to check replication. The date must be inthe following format: MM/DD/YYYY,HH:MM:SS, where MM=month, DD=day,YYYY=year, and optionally, HH=hour, MM=minute, and SS=second. If no date isspecified, the replication check is performed for the previous week.

CLI ExampleThe following example verifies that replication occurred on the server tokyo.wtmdcheckrep tokyo INC=solserver DATE=07/17/2001

Return ValuesThe following information about the replication instance is returned:

¶ The name of the local or remote Domino database that was replicated

¶ The timestamp for the replication instance

¶ The time it took for the replication to complete in minutes

¶ Events that occurred during this replication instance

The following data about the replication database is returned:

¶ The name of the local Domino database that was replicated

¶ The name of the remote Domino database that was replicated

¶ Replication access level for the database

¶ Number of documents added to the local database during this replication

¶ Number of documents deleted from the local database during this replication

¶ Number of documents updated on the local database during this replication

¶ Kilobytes received for this replication

¶ Kilobytes sent for this replication

308 Version 3.1.0

¶ Replication direction (pull, push, pull-push, pull-pull)

The following is an example of a successful return of this command.=========================================================================

Server Name := dmserver1/DomStarted := 07/17/2000 11:09:04 AMFinished := 07/17/2000 11:09:07 AMHIT/MISS/MANUAL: MANUAL

Remote Server := Solserver/DomInitiated By := dmserver1/DomElapsed Time := 0.05 minutes

Events:

Database Access Added Deleted Updated KB Rec. KB Sent From

Solserver names.nsf Manager 0 0 1 0.22 5.77 dmserver1 names.nsf (PUSH)Solserver admin4.nsf Manager 2 0 0 0.27 2.24 dmserver1 admin4.nsf (PUSH)=========================================================================

Server Name := dmserver1/DomStarted := 07/17/2000 12:00:20 PMFinished := 07/17/2000 12:00:32 PMHIT/MISS/MANUAL: HIT

Remote Server := dmserver2/DomInitiated By := dmserver1/DomElapsed Time := 0.20 minutes


7.D

om

ino

Server

Co

mm

and

s

wtmdchkdbcorruption

DescriptionChecks the specified database for corruption. You can check for corruption by server,database, or database view. A fix is run for each corrupt database to correct the corruption.When it completes, a list of all corrupt databases is returned, along with a flag statingwhether the corruption was fixed.


CLI Syntaxwtmdchkdbcorruption <ServerName> [<DatabaseName; ...>] [<View, ...> | ALL]

where:



<View, ...> The name of a view. You can specify multiple views by separating thenames with commas. ALL specifies all views for the specified databases.

CLI ExampleThe following example checks db1.ntf and db2.ntf on server tokyo for corruption.wtmdchkdbcorruption tokyo C:\data\db1.ntf;C:\data\db2.ntf ALL

Return ValuesIf successful, the command returns the following:

¶ Count: n — The number of corrupt databases on the specified server.

For each corrupted database found, the command returns the following information:

¶ Database — The name of the corrupted database.

¶ View — The name of the corrupted view.

¶ Status — Flag indicating that the database is Fixed or Corrupt.

The following example shows a successful return of this command.COUNT 1:

Database View StatusC:\data\db1.ntf Look Fixed

310 Version 3.1.0

wtmdchkinactusers

DescriptionChecks for users who have not accessed the specified Domino server within the number ofdays specified. A list of all users who meet the criteria is returned.


CLI Syntaxwtmdchkinactusers <ServerName> <Days>

where



CLI ExampleThe following example checks for users who have been inactive on the server tokyo for thelast 120 days.wtmdchkinactusers tokyo 120

Return ValuesThis command returns the following codes:

¶ Count — The number of users who have not connected during the specified time.

For each server, the following information is returned:

¶ User — The user’s name.

¶ Date — The date on which the user last connected.

The following is an example of a successsful return of this command.COUNT 1:

User DateTom Cat 10-11-1962 10:00


7.D

om

ino

Server

Co

mm

and

s

wtmdcleandb

DescriptionRemoves entries made before the specified date from the Tivoli Manager for Dominomonitoring database.


CLI Syntaxwtmdcleandb <Date>

where:

<Date> A date in the format mm-dd-yyyy. Entries made before this date are removed.

CLI ExampleThe following example removes entries made before January 1, 2001 from the monitoringdatabase.wtmdcleandb 01-01-2001


If unsuccessful, one of the following error messages is returned.

¶ RIM object does not exist — Unable to locate RIM object TMD.

¶ RIM Host Unavailable — Unable to connect to RIM database host. Either the RIMparameters are incorrect or the RDBMS is not responding.

¶ Date format not supported — The date format specified is not supported.

312 Version 3.1.0

wtmdcreateserver

DescriptionCreates a new Domino server object in the Tivoli environment. If the server has Tivoli DataProtection installed, this command can be used to configure Tivoli Data Protection options.

This command verifies the location of the server and the notes.ini file, creates the serverobject, and modifies the server’s notes.ini file. Final configuration occurs when you start theserver (see the wtmdstartserver command). The server object can then be managed byTivoli Manager for Domino and users can interact with the server.

Before you run this command, you can run the wtmdlocateserver command to retrieve thefollowing information about the server. You will need this information when you run thewtmdcreateserver command.

¶ The server name

¶ The name of the domain in which the server is located

¶ The fully qualified path and filename of the notes.ini file

¶ An available port within the default range of 3000 to 9999


CLI Syntaxwtmdcreateserver <ServerName> <EndpointName> <INI_PathFile> <PolicyRegion> <Port>[–TD=<TDP_Directory>] [–AD=<API_Directory>] [–TC=<TDP_ConfigFile>][–TO=<TDP_OptionsFile>] [–TU=<TDP_Username>] [–TP=<TDP_Userpassword>][–TYPE=MAIL, WEB, MAILROUTER, DATABASE, NEWS][–PASS=<ID_FilePassword>]

where:

<ServerName>Specifies the label you assign to the Domino server object. No default labelis used.

<EndpointName>Specifies the name of the endpoint on which to create the Domino serverobject.

<INI_PathFile>Specifies the fully qualified path and name of the server’s notes.ini file.

<PolicyRegion>Specifies the policy region to which this server is added.

<Port> Specifies the TCP/IP port in use on this server.

TD <TDP_Directory> is the directory where Tivoli Data Protection for Dominois installed.

AD <API_Directory> is the directory where the Tivoli Data Protection API filesare installed.

TC <TDP_ConfigFile> is the name of the Tivoli Data Protection configuration


7.D

om

ino

Server

Co

mm

and

s

file, relative to the Tivoli Data Protection directory (unless the full path andname are specified). The default file is domdsm.cfg.

TO <TDP_OptionsFile> is the name of the Tivoli Data Protection file, relative tothe Tivoli Data Protection directory. The default file is dsm.opt.

TU <TDP_Username> is the name of the Tivoli Data Protection user.

TP <TDP_Userpassword> is the password of the Tivoli Data Protection user.

TYPE Specifies the type of server you are creating: Mail, Web, Mail Router,Database, or News. If you assign more than one type, separate types withcommas.

PASS <ID_FilePassword> is the password of the server’s ID file.

CLI ExampleThe following example creates the Domino server tokyo.wtmdcreateserver "tokyo" "atlantic-lcf" "/data/lotus/notes/notes.ini" "Cats" 3102 -TYPE=MAIL-TD=/opt/tivoli/tsm/client/domino/bin -AD=/opt/tivoli/tsm/client/api/bin -TC=domdsm.cfg-TO=dsm.opt -TU=user -TP=password

Return ValuesIf successful, this command returns the message Success.

If unsuccessful, the command might return one of the following error messages:

¶ Error, Unable to copy the tivoli addin processes.

An unknown failure occurred while copying the addin into the Notes executabledirectory. Contact Tivoli customer support.

¶ Error, During configuration, NotesInitExtended1 Failed

The NotesInitExtended1 file failed during configuration. Stop and restart the server andtry again.

¶ Error, During configuration, unable to locate server name.

The server could not be located during configuration. Stop and restart the server.

¶ Error, During configuration unable to locate server task information innotes ini file

A line starting with servertasks= could not be found in the notes.ini file. Be sure thenotes.ini file has a valid servertasks= line. Edit the file if needed.

¶ Error, Unable to dynamically load the Notes DLL

The system could not locate the Notes DLL files. Be sure the Domino server is installedcorrectly.

¶ Error, unable to locate the NotesInitExtended API in the notes dll.

The NotesInitExtended API entry point does not exist in the the Notes DLL files. Besure the Domino server is installed correctly.

¶ Error, unable to locate the NotesTerm API in the notes dll

The NotesTerm API entry point does not exist in the Notes DLL files. Be sure theDomino server is installed correctly.

¶ Error, unable to locate the OsGetEnvironment API in the notes dll

The OsGetEnvironment API entry point does not exist in the Notes DLL files. Be surethe Domino server is installed correctly.

314 Version 3.1.0

¶ Error, unable to locate the OsSetEnvironment API in the notes dll

The OsSetEnvironment API entry point does not exist in the Notes DLL files. Be surethe Domino server is installed correctly.

¶ Error, unable to locate the SeckFMGetUserName API in the notes dll

The SeckFMGetUserName API entry point does not exist in the Notes DLL files. Besure the Domino server is installed correctly.

¶ Error, unable to locate the NSFRemoteConsole API in the notes dll

The NSFRemoteConsole API entry point does not exist in the Notes DLL files. Be surethe Domino server is installed correctly.

¶ Error, unable to locate the OSLockObject API in the notes dll

The OSLockObject API entry point does not exist in the Notes DLL files. Be sure theDomino server is installed correctly.

¶ Error, unable to locate the OSUnlockObject API in the notes dll

The OSUnlockObject API entry point does not exist in the Notes DLL files. Be sure theDomino server is installed correctly.

¶ Error, unable to locate the OSLoadString API in the notes dll

The OSLoadString API entry point does not exist in the Notes DLL files. Be sure theDomino server is installed correctly.

¶ Error, unable to locate the OSMemFree API in the notes dll

The OSMemFree API entry point does not exist in the Notes DLL files. Be sure theDomino server is installed correctly.

¶ Error, NotesInitExtended Call failure

The call to initialize Lotus Notes failed. Stop and restart the server.

¶ Error, SECKFMGetUserName Call failure, unable to locate theTMDServerObjectLabel

The getusername call returned an error. Stop and restart the server.

¶ Error, unable to get the ServerTasks entry from the notes.ini file

A line starting with servertasks= could not be found in the notes.ini file. Be sure thenotes.ini file has a valid servertasks= line. Edit the file if needed.

¶ Error, No response from the console when starting the Tivoli Addin, TheAddin might not have started

Starting the addin did not return a response. Check the server console to see if the addinis running. If not, start it manually.

¶ Error, An unknown error occurred when attempting to start the TivoliAddin

Starting the addin returned an unknown error. Check the server console to see if theaddin is running. If not, start it manually.

¶ You specified an endpoint that is currently not connected to the system

The endpoint you specified is not connected to the system. Be sure the endpoint iscommunicating correctly with the Tivoli environment.

¶ A failure occurred while attempting to add a value to the ApplSvcsAttribute Cache


7.D

om

ino

Server

Co

mm

and

s

This message indicates an internal failure. Contact Tivoli customer support. See“Contacting Customer Support” on page xiii.

¶ Failure setting attributes for Lotus Domino Server


¶ The system is unable to locate the specified Policy Region

The system cannot locate the Tivoli Manager for Domino policy region. Be sure theproduct is installed correctly.

¶ An error occurred attempting to create the specified Policy Region


¶ An error occurred attempting to set the state of the object

This message indicates an internal failure. Contact Tivoli customer support.

¶ An error occurred while attempting to move an object between PolicyRegions


¶ Error, the specified object label is already in use

The object label specified is already in use. Choose another label for this server.

316 Version 3.1.0

wtmddbactivity

DescriptionChecks the specified database files on a Domino server for activity within the specifiednumber of days and the specified activity type. Returns a list of database files that have nothad any activity within the number of days specified.


CLI Syntaxwtmddbactivity <ServerName> <DatabaseName; ...> <Days> [ACTIVITY=<ActivityType; ...>]

where:


<DatabaseName; ...>The database files to check against. You can specify multiple databases by separatingthe names with semicolons.


ACTIVITY<ActivityType; ...> specifies the type of activity to check for. If you omit this option,the command checks for data and non-data modification. If you list more than onetype, use semicolons to separate listed types and enclose the statement in doublequotes (for example, "ACTIVITY=N;R;W").


A All activities







CLI ExampleThe following example checks for any activity in the last 90 days on the server tokyo:wtmddbactivity tokyo "C:\data\db1.ntf;C:\data\db2.ntf" 90 ACTIVITY=A

Return ValuesThe command returns the following information:

¶ Count — The number of activity types to check.

¶ Activity Type — The activity type checked.

¶ COUNT: n — The number of matching database files for each activity.


7.D

om

ino

Server

Co

mm

and

s

¶ Database — The database file and path name.

¶ Last Activity — The last activity date for the database.

The following example shows the return of this command:

Number of Activity Types = 6

ACTIVITY TYPE : Data/Non Data Modified TimeCOUNT 1:

Database File Last Data/Non Data Modified TimeC:\data\russ.ntf 10-10-1999 10:01

ACTIVITY TYPE : Data Modified TimeCOUNT 1:

Database File Last Data Modified TimeC:\data\russ.ntf 10-10-1999 10:01

ACTIVITY TYPE : Non Data Modified TimeCOUNT 1:

Database File Last Non Data Modified TimeC:\data\russ.ntf 10-10-1999 9:01

ACTIVITY TYPE : Read/Write Activity TimeCOUNT 1:

Database File Last Read/Write TimeC:\data\russ.ntf 10-10-1999 10:01

ACTIVITY TYPE : Read Activity TimeCOUNT 1:

Database File Last Read TimeC:\data\russ.ntf 10-10-1999 10:01

ACTIVITY TYPE : Write Activity TimeCOUNT 1:

Database File Last Write TimeC:\data\russ.ntf 10-10-1999 10:01

318 Version 3.1.0

wtmddeletemail

DescriptionDisplays information about the first mail message in the specified mailbox.

To delete the message, you must specify the –PURGE option. You must also specify theNotes ID and the sender of the message.


CLI Syntaxwtmddeletemail <ServerName> [–MB=<Mailbox>] [–PURGE] [–PI=<PurgeID>][–PS=<PurgeSender>]

where:


MB <Mailbox> specifies the mailbox. The default is mail.box.

PURGE If specified, the first message is deleted when used with the –PI and –PSoptions. If not specified, the message is listed.

PI <PurgeID> specifies the Notes ID of the message to delete. It is used with–PURGE.

PS <PurgeSender> specifies the sender of the message. It is used with–PURGE.

CLI ExampleThe following example reports the first mail item in mailbox mail.box on the server tokyo.wtmddeletemail tokyo -mb=mail.box

Posted Date Note ID Sender Recipient(s)07/01/2000 10:00:00 AM 1234 Sales/Acme Wiley Coyote/Desert

The following example deletes the first item, which is Notes ID 2302, sent by Tom Smithon domain Cats on server tokyo.wtmddeletemail tokyo -mb=mail/tsmith.nsf -PURGE -pi=2302 -ps=CN="TomSmith/org=Cats"

Return ValuesIf successful, this command returns the Success message.

If unsuccessful, this command returns the following error codes:

¶ Invalid Mailbox Specified — You specified an invalid mailbox.

¶ No Mail Waiting — No mail is waiting in the queue to delete.


7.D

om

ino

Server

Co

mm

and

s

wtmddeleteserver

DescriptionDeletes the specified Domino server object from the Tivoli environment. Cleans up allmodifications made to the system for managing this server with Tivoli Manager for Domino,including removing entries within events, removing entries from the notes.ini file, andremoving any program files placed on the endpoint. The Domino server continues to be anendpoint in the Tivoli management region.


CLI Syntaxwtmddeleteserver <ServerName>

where


CLI ExampleThe following example deletes the Domino server tokyo.wtmddeleteserver tokyo

Return ValuesIf successful, this command returns the message Success.

If unsuccessful, this command returns an error message.

320 Version 3.1.0

wtmdgetacl

DescriptionReturns a list of all database Access Control List (ACL) entries and the access levels for thespecified databases on the specified server.


CLI Syntaxwtmdgetacl <ServerName> <DatabaseName; ...>

where:


<DatabaseName; ...>The name of the database to query. If specifying multiple databases, use semicolonsto separate the names.

CLI ExampleThe following command gets ACL information for the database file acls.nsf on the servertokyo.wtmdgetacl tokyo acls.nsf

Return ValuesFor each ACL entry, the following data is returned.

¶ User Name — The user or group name.

¶ Access Level — Access level for the user or group

¶ Privileges — If available, the privilege name set for the user or group

¶ Access Flags — A list of access flags for the user or group

The following is an example of successful return of this command for database file acls.nsf.

====================================================================Database Name: c:\lotus\Domino\DMServer1\acls.nsfUser Name = -Default-Access Level = Reader

Access Flags :Privileges =

User Name = Joe BrownAccess Level = Manager

Access Flags :Privileges = (Privilege 1)[Marketing]

User Name = jackAccess Level = Reader

Access Flags :


7.D

om

ino

Server

Co

mm

and

s

User can create personal folders.Entry represents a Person.User can read public notes.

Privileges =

322 Version 3.1.0

wtmdinactivatetranslog

DescriptionInactivates transactional log files on the specified Domino server. Queries the databasebackups to determine which log files are required by active databases on the Domino serveryou specified and inactivates any log files that are not required.

Equivalent to the Tivoli Data Protection command domdsmc inactivatelogs.


CLI Syntaxwtmdinactivatetranslog <ServerName>

where:


CLI ExampleThe following example inactivates transactional logs on the server tokyo.wtmdinactivatetranslog tokyo




7.D

om

ino

Server

Co

mm

and

s

wtmdincrementalbackup

DescriptionPerforms an incremental backup of databases on a Domino server. Equivalent to the TivoliData Protection command domdsmc incremental.

An incremental backup performs a full backup of the specified databases that meet at leastone of the following conditions:

¶ The database is within the Domino data path or symbolically linked to the Domino datapath by directory or database links.

¶ If the database has archive logging enabled, the Database Instance Identifier (DBIID)has changed. (See the Domino server documentation for more information on the DBIIDand when it can change.)

¶ If the database is not logged, it has been modified since the last backup occurred (dataand non-data modification dates are checked).

¶ The database is new or newly included in the backup.

An incremental backup performs the following functions:

¶ Backs up any new databases.

¶ Backs up any unlogged databases that have changed since the last backup.

¶ Backs up any logged databases in which the DBIID has changed.

¶ Inactivates database backups that are no longer needed.


CLI Syntaxwtmdincrementalbackup <ServerName> <DatabaseName, ...>

where:


<DatabaseName, ...>The database name relative to the server’s data directory. Use commas to separatedatabase names.

CLI ExampleIn the following example, an incremental backup will be performed on two databases on theserver tokyo.wtmdincrementalbackup tokyo C:\data\db1.ntf,C:\data\db2.ntf



¶ Invalid database specified — The database you specified could not be found.

324 Version 3.1.0

wtmdlocateserver

DescriptionLocates any configured Domino servers on the specified endpoint. You can run thiscommand before running the wtmdcreateserver command to retrieve the data you need tocreate a Domino server object.

In Windows, this command searches the registry for Domino server entries. In UNIX, thiscommand searches /opt/lotus/.install.dat for Domino server references. Because Domino 4.6does not create an install.dat file, Domino 4.6 servers on UNIX machines cannot be locatedusing this command.

The command ignores any servers already configured for Tivoli Manager for Domino.


CLI Syntaxwtmdlocateserver <EndpointName>

where:

<EndpointName>The name of the endpoint.

CLI ExampleThe following example locates Domino servers on the endpoint labeled endpoint3.wtmdlocateserver endpoint3

Return ValuesThis command returns the following information::

¶ The common Domino server name

¶ The name of the domain in which the server is located

¶ The fully qualified path and filename of the notes.ini file

¶ An available port within the default range of 3000 to 9999

For example:Server Name Domain INI PortFreddy/Sales/Acme1 AcmeUS C:\domino\notes.ini 3000Speedy/Acme2 AcmeUK C:\lotus\notes.ini 3001


7.D

om

ino

Server

Co

mm

and

s

wtmdmailwaiting

DescriptionLists all the currently waiting mail in the server mailboxes on the specified server. Returnsthe number of messages waiting to be sent, the mailbox in which the mail is waiting, thedestination address, the sender, and the time the mail entered the queue.


CLI Syntaxwtmdmailwaiting <ServerName>

where:


CLI ExampleThe following example checks for mail waiting on server tokyo:wtmdmailwaiting tokyo

Return ValuesThis command returns the following codes:

¶ Count — The number of messages waiting to be sent.

The command returns the following information for each message waiting to be sent:

¶ Mailbox — The mailbox that the mail is waiting in.

¶ Destination — The mail’s destination address.

¶ Sender — The sender’s name.

¶ Time in Queue — The time the mail entered the queue.

¶ Note ID — The Note ID of the mail document.

The following example shows a successful return of this command.COUNT 3:

Mailbox Destination Sender Entered Queue Note IDMail.box Russ Grer/Acme Systems Bob/IBM 05-11-2000 00:02:05 1234

326 Version 3.1.0

wtmdpurgemail

DescriptionLists and optionally purges all mail in the specified mail file that meets or exceeds thespecified age and message-size criteria. If you specify both options, both criteria must bemet for mail to be purged.


CLI Syntaxwtmdpurgemail <ServerName> [–DB=<MailDatabaseName>] [–OLDER=<Days> |–LARGER=<Kilobytes>] [–PURGE]

where:


DB <MailDatabaseName> is the name of the mail database file to check,relative to the data directory. If omitted, all mail database files are checked.


LARGER <Kilobytes> is the maximum message size allowed, in kilobytes; all largermessages are purged.

PURGE If specified, all mail passing the check is purged. If not specified, all mailpassing the check is only reported.

CLI ExampleThe following example purges messages older than 365 days and larger than 10,000kilobytes in all mail files on the server tokyo.wtmdpurgemail tokyo -OLDER=365 -LARGER=10000 -PURGE

Return ValuesThe following information is returned for each mail file found:

¶ Count — The number of mail files where messages were purged

¶ Mail Database — The databases from which messages were purged

¶ Messages — The number of messages purged from that database

¶ Size — The total size (in kilobytes) of the messages

¶ Total — The total number of messages and total size of the messages for all mail files

The following example shows a successful return of this command:COUNT: 2Mail Database Messages Size (KB)C:\data\russ.ntf 20 5C:\data\tam.ntf 12 13.2

TOTAL Messages Size (KB)32 18.2


7.D

om

ino

Server

Co

mm

and

s

wtmdqueryactivate

DescriptionReturns a list of databases that have been restored but not yet activated on the specifiedserver.

Equivalent to the Tivoli Data Protection command domdsmc query pendingdbs.


CLI Syntaxwtmdqueryactivate <ServerName>

where:


CLI ExampleThe following example lists databases that have been restored but not yet activated on servertokyo.wtmdqueryactivate tokyo

Return ValuesThe following information is returned for each database found:

¶ Database — The database path and filename.

¶ Restored — The date on which the database was restored.

¶ Size — The size of the database in kilobytes (Kb).

¶ Logged — Whether the database has logging enabled.

¶ Database Title — Name of the database.

For example:COUNT 1:

Database Restored on Size Logged TitleC:\data\db1.ntf 04-10-2000 10:01 100 No System Documents

328 Version 3.1.0

wtmdquerybackup

DescriptionReturns a list of all database template (.ntf) and database (.nsf) files on the specified server.You can specify a database name if desired.

Equivalent to the Tivoli Data Protection command domdsmc query domino.


CLI Syntaxwtmdquerybackup <ServerName> [<DatabaseName>]

where:



CLI ExampleThe following example returns information on databases for the server tokyo.wtmdquerybackup tokyo

Return ValuesFor each database found, the following information is returned:


¶ Last Modified Date — Date on which the database was last modified

¶ Size — Size of the database in kilobytes


¶ Database Title — Name of the database

For example:

COUNT: 2

Database Last Modification Size Logged TitleC:\data\db1.ntf 10-10-1999 10:01 100 No System DocumentsC:\data\db1.nsf 05-11-1987 22:10 5 No System Documents


7.D

om

ino

Server

Co

mm

and

s

wtmdquerydoc

DescriptionReturns the full text of a log file from the specified Domino server.


CLI Syntaxwtmdquerydoc <ServerName> <FieldName> <DocID>

where:


<FieldName> The field name.

<DocID> The ID number of the document you are requesting.

CLI ExampleThe following example returns document 9710 from server tokyo.wtmdquerydoc tokyo events 9710

Return ValuesIf successful, the command returns the text of the requested document.

If unsuccessful, the command returns one of the following messages:

¶ The document ID specified is incorrect — You specified an invalid document ID.

¶ The field name specified cannot be found — The field name you entered cannot befound.

The following example shows a successful return of this command.=================================================================07/12/2000 11:33:22 AM Begin scan of databases to be consistency checked07/12/2000 11:33:22 AM End scan of databases: 1 found07/12/2000 11:33:23 AM Database Replicator started07/12/2000 11:33:28 AM Mail Router started for domain TESTDOM07/12/2000 11:33:28 AM Router: Internet SMTP host rsaghafi in domain dev.tivoli.com07/12/2000 11:33:33 AM Index update process started07/12/2000 11:33:38 AM Stats agent started07/12/2000 11:33:43 AM Agent Manager started07/12/2000 11:33:44 AM AMgr: Executive '1' started07/12/2000 11:33:48 AM dmserver1/TestDom is the Administration Server of the Domino Directory.07/12/2000 11:33:48 AM Administration Process started07/12/2000 11:33:53 AM Schedule Manager started07/12/2000 11:34:03 AM Event Monitor started07/12/2000 11:34:08 AM Lotus Domino Server started, running Release 5.0.2c07/12/2000 11:34:08 AM Server started on physical node RSAGHAFI07/12/2000 11:34:09 AM JVM: Java Virtual Machine initialized.07/12/2000 11:34:18 AM Database Server started

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

330 Version 3.1.0

wtmdquerylog

DescriptionQueries the log files on the specified server. You can limit the search by including orexcluding a text string.


CLI Syntaxwtmdquerylog <ServerName> [–FORM=<Form; ...>] {–INC=<IncludeString; ...> |–EXC=<ExcludeString; ...>} [–DATE=<StartDate>]

where:



session Session

activity Activity




call Phone Call



size Size

nntp NNTP Events



INC <IncludeString> is a semicolon-separated list of strings that must be included in thesearch criteria.

EXC <ExcludeString> is a semicolon-separated list of strings that are not included in thesearch criteria.

DATE <StartDate> is the date in the following format: MM/DD/YYYY [hh:mm]. MM =Month, DD = Day, YYYY = Year, and optional hh = Hour, mm = Minute. If no dateis specified, the log file is searched from a week before the current date. If nohh:mm is specified, 12:00 AM is used.

CLI ExampleThe following example queries the log file on the server tokyo and searches the formssession and events for the strings aixserver and Unable to replicate on date 07/12/2000.wtmdquerylog tokyo -FORM=session;events -INC=aixserver;"Unable to replicate" -DATE=07/12/2001


7.D

om

ino

Server

Co

mm

and

s

Return ValuesThe following information is returned:

¶ Form — Name of the form where the string was found.

¶ Field — Name of the field where the string was found.

¶ DOCID — ID of the document where the string was found.

¶ FoundEntry — The string that was found.

For example:Form= EventsField= EventsDOCID= 9710Found Entry:07/12/2000 11:34:32 AM Unable to replicate with server dmserver2/TestDom:Server not responding

If unsuccessful, the command returns one of the following messages:

¶ Invalid Form — You specified an invalid form name

¶ Invalid Start Date — You specified an invalid start date

¶ Invalid Stop Date — You specified an invalid stop date

332 Version 3.1.0

wtmdquerynab

DescriptionQueries the Name and Address Book (NAB) on the specified Domino server and returnsinformation about each server that is found.


CLI Syntaxwtmdquerynab <ServerName>

where:


CLI ExampleThe following example queries the NAB on Domino server tokyo.wtmdquerynab tokyo


¶ Count — The number of servers located.

The following information is returned for each server:

¶ Server Name — The Domino server name.

¶ Host — The host name of the Domino server.

¶ Cluster — The name of the Domino cluster to which the server belongs. Null isreturned if the server does not belong to a cluster.

¶ Network — The name of the network the Domino server communicates with.

¶ Release — The Domino release that runs on the server.

¶ OS — The operating system that the Domino server is running.

The following example shows output from a successful return of this command.===================================================================Server Name = CN=AIXserver/O=TomHost = niagara.dev.acme.comCluster =Network = TCPIPRelease = Release 5.0.1OS = AIX

===================================================================Server Name = CN=dmserver1/O=Tom1Host = niagara.dev.acme.comCluster =Network = TCPIP NetworkRelease = Release 5.0.2cOS = Windows/NT 4.0 Intel Pentium


7.D

om

ino

Server

Co

mm

and

s

wtmdqueryrestore

DescriptionReturns a list of all backed-up database versions for the specified Domino server. If COUNTis specified, it returns up to the specified number of backup versions for each database (ifpresent).

Equivalent to the Tivoli Data Protection command domdsmc query dbbackup/inactive=<yes/no>.


CLI Syntaxwtmdqueryrestore <ServerName> [–DB=<DatabaseName, ...>] [–COUNT=<Count>]

where:


DB <DatabaseName, ...> is the name of a database relative to the server’s data directory.Use commas to separate multiple database names. If this option is omitted, alldatabases in all data directories are listed.

COUNT<Count> is the maximum number of backup versions to query. The default is ALL.

CLI ExampleThe following example returns information on backed-up databases for the server tokyo.wtmdqueryrestore tokyo

Return ValuesFor each database found, the following information is returned:


¶ Backup Date — The date on which the database was last backed up

¶ Size — The size of the database in kilobytes (Kb)

¶ Active — Whether the current database is active


¶ Backup Time Stamp — Time of backup

¶ Database Title — The name of the database

334 Version 3.1.0

wtmdquerystat

DescriptionQueries the Domino server statistics on the specified server.


CLI Syntaxwtmdquerystat <ServerName> <StatName>

where:


<StatName>The name of a statistic. You can use the * wildcard. For example, mem.* returns allstatistics that match the mem name. You can specify statistics or statistic groups inthe format group_name.*, where all statistics that match the group name arereturned.

CLI ExampleThe following example queries the server tokyo for statistics related to memory.wtmdquerystat tokyo mem.*

Return ValuesThe following example shows output of a successful return of this command.Mem.Allocated.Process 6939788Mem.Allocated.Shared 23923858Mem.Availability PlentifulMem.Free 313,446,400Mem.PhysicalRAM 267821056

If the command fails, it returns one of the following error messages:

¶ The requested statistic(s) is not available — You requested an invalid statistic.

¶ An instance named ″Tun xxa″ of resource ″LotusDominoServer″ was not found —The server name is invalid.


7.D

om

ino

Server

Co

mm

and

s

wtmdquerytranslog

DescriptionReturns a list of the transactional log files archived on the Tivoli Storage Manager server forthe specified Domino server. To archive transactional log files, use thewtmdarchivetranslog command. Equivalent to the Tivoli Data Protection commanddomdsmc query logarchive.


CLI Syntaxwtmdquerytranslog <ServerName>

where:


CLI ExampleThe following example returns a list of the archived transactional log files for the servertokyo.wtmdquerytranslog tokyo


¶ Log Archive Date — The date on which the log was archived

¶ Name of Log File — The name of the log file

¶ A/I — Flag indicating whether the log is active or inactive

¶ Size — The size of the log file in kilobytes

¶ Logger ID — The ID of the log file

For example:Count 2Log File Archive Date Size Active Log File IDc:\log\log1.log 10-10-1999 10:01 100 No 10c:\log\log2.log 05-11-2000 22:01 10 Yes 22

336 Version 3.1.0

wtmdrecyclentsvrsvc

DescriptionStops and restarts the Windows NT Server service on Windows NT.

The Windows NT operating system runs a server service to provide the following basicservices to all local servers:

¶ Remote procedure call (RPC) support

¶ File, print, and named pipe sharing

You can recycle the server service whenever necessary.


CLI Syntaxwtmdrecyclentsvrsvc <ServerName>

where:


CLI ExampleThe following example stops and restarts the Windows NT Server Service on the Dominoserver named tokyo.wtmdrecyclentsvrsvc tokyo




7.D

om

ino

Server

Co

mm

and

s

wtmdrecycleserver

DescriptionStops and restarts the Domino server process on the specified Domino server. Should onlybe used on servers that are not running Windows NT.


CLI Syntaxwtmdrecycleserver <ServerName>

where:


CLI ExampleThe following example stops and restarts the Domino server process on the server namedtokyo:wtmdrecycleserver tokyo


If unsuccessful, the command returns the message Server Not Found, which indicates thatthe Domino server process cannot be located on the server you specified.

338 Version 3.1.0

wtmdremoteconsole

DescriptionExecutes a Domino server command on the specified Domino server and returns the resultsin the remote console. You can run any valid Domino server command. For help on Dominoserver commands, see the Domino documentation.


CLI Syntaxwtmdremoteconsole <ServerName> <Command>

where:



CLI ExampleThe following example starts HTTP on the server tokyo.wtmdremoteconsole tokyo "start http"

Return ValuesReturns the result from the server’s console.


7.D

om

ino

Server

Co

mm

and

s

wtmdrestoredbs

DescriptionRestores the specified database on the selected server from backups on the Tivoli StorageManager server.

If you include the date and time, the database is restored using the backup image and thetransactional log entries are restored. If you omit the date and time, the database is restoredfrom the backup image but the transactional log entries are not updated.

If you want to activate the database (bring it back on line), use the ACTIVATE option. Ifyou omit this option, the database is restored but not brought back on line; you can use thewtmdactivatedbs command to activate the restored database.

Equivalent to the Tivoli Data Protection command domdsmc restore.


CLI Syntaxwtmdrestoredbs <ServerName> <DatabaseName, ...> [–DATE=<Date> | NOW][–REPLACE=Yes | No] [–ACTIVATE]

where:


<DatabaseName, ...>The database name relative to the server’s data directory. You can specifymultiple databases by separating the names with commas. You can usedirectories and wild cards.

DATE If specified, <Date> defines the date of the backup to use when restoring.The format is MM/DD/YYYY,HH:MM:SS, where DD=Day, MM=Month,YYYY=Year, HH=Hour, MM=Minute, and SS=Second. –DATE is specificto the preceding database and restores the transactional log entries to thedatabase from the date of the database backup until the specified date. If adate is not specified, the transactional logs are not restored. To restore thelogs up until the current time, use –DATE = NOW. You can use directoriesand wild cards.

REPLACE Specifies whether or not to replace the existing database with the restoreddatabase.

ACTIVATE If specified, activates the database after the restore completes. If you do notselect this option, the database is restored but not activated.

CLI ExampleThe following example restores databases db1.ntf and db2.ntf on server tokyo.wtmdrestoredbs tokyo c:\data\db1.ntf,c:\data\db2.ntf

340 Version 3.1.0





7.D

om

ino

Server

Co

mm

and

s

wtmdselectivebackup

DescriptionPerforms a selective backup of the specified databases on the specified Domino server.

Unlike an incremental backup, it is not necessary for the database to meet a set of criteriabefore being backed up. A selective backup unconditionally backs up all specified databases.

Equivalent to the Tivoli Data Protection command domdsmc selective.


CLI Syntaxwtmdselectivebackup <ServerName> <DatabaseName, ...>

where:


<DatabaseName, ...>The database name relative to the server’s data directory. Use commas to separatedatabase names.

CLI ExampleThe following example backs up databases db1.ntf and db2.ntf on Domino server tokyo.wtmdselectivebackup tokyo c:\data\db1.ntf, c:\data\db2.ntf




342 Version 3.1.0

wtmdstartengine

DescriptionStarts the local Tivoli Enterprise Console event engine on the specified server.



CLI Syntaxwtmdstartengine <ServerName>

where:


CLI ExampleThe following example starts the event engine on server tokyo:wtmdstartengine tokyo

Return ValuesIf successful, the command returns the message Rule Engine Successfully Started.

If unsuccessful, the command returns the following error message.

¶ TEC Engine is already running — The event engine on the Domino server youspecified is already started.


7.D

om

ino

Server

Co

mm

and

s

wtmdstartmonitors

DescriptionStarts monitoring on the specified server.


CLI Syntaxwtmdstartmonitors <ServerName>

where:


CLI ExampleThe following example starts monitoring on the server tokyo:wtmdstartmonitors tokyo

Return ValuesIf successful, the command returns the message Monitors Successfully Started.


¶ Monitoring Already Started — Monitoring on the specified server is already started.

344 Version 3.1.0

wtmdstartserver

DescriptionStarts the Domino server process on the specified server.


CLI Syntaxwtmdstartserver <ServerName>

where:


CLI ExampleThe following example starts the Domino server process on server tokyo:wtmdstartserver tokyo

Return ValuesIf successful, the command returns the message Server Successfully Started.

If unsuccessful, the command returns one of following error messages:

¶ The Lotus Domino Server is already running. — The server you attempted to start isalready running.

¶ An instance named ″abc″ of resource ″LotusDominoServer″ was not found. — ADomino server object with the name given does not exist.


7.D

om

ino

Server

Co

mm

and

s

wtmdstopengine

DescriptionStops the Tivoli Enterprise Console event engine on the specified server.



CLI Syntaxwtmdstopengine <ServerName>

where:


CLI ExampleThe following example stops the event engine on server tokyo:wtmdstopengine tokyo

Return ValuesIf successful, the command returns the message Rule Engine Successfully Stopped.


¶ TEC Engine is Already Stopped — The event engine is already stopped.

346 Version 3.1.0

wtmdstopmonitors

DescriptionStops monitoring on the specified server. The addin will be notified when an asynch monitorstops.


CLI Syntaxwtmdstopmonitors <ServerName>

where:


CLI ExampleThe following example stops monitoring on the server tokyo:wtmdstopmonitors tokyo

Return ValuesOne of the following values will be returned:

¶ Monitors Successfully Stopped — Monitoring stopped successfully.

¶ Monitoring Already Stopped — Monitoring on the specified server is already stopped.


7.D

om

ino

Server

Co

mm

and

s

wtmdstopserver

DescriptionStops the Domino server process on the specified server.

Equivalent to the Lotus Domino console quit command.


CLI Syntaxwtmdstopserver <ServerName>

where:


CLI ExampleThe following example stops server tokyo.wtmdstopserver tokyo

Return ValuesIf successful, the command returns the message Server Successfully Stopped.

If unsuccessful, the command returns a common error message or one of the following errormessages:

¶ Cannot connect to Tivoli addin. Either the Domino server is down or the Tivoliaddin is not running. — The Domino server you specified is already stopped.

¶ An instance named ″abc″ of resource ″LotusDominoServer″ was not found. — TheDomino server object with the name given does not exist.

348 Version 3.1.0

wtmdverifymail

DescriptionChecks all Name and Address Book (NAB) mail user entries against the mail files that existon the specified Domino server and returns a list of all mail files without NAB entries.


CLI Syntaxwtmdverifymail <ServerName>

where:


CLI ExampleThe following example checks NAB user entries against the mail files on the server tokyo:wtmdverifymail tokyo

Return ValuesFor each mail file without an NAB entry, the following data is returned.

¶ MFNAME — Specifies the names of the mail files without NAB entries.

The following example shows output of a successful return of this command.Found Extra mail databasesC:\data\mail\mail1.nsf


7.D

om

ino

Server

Co

mm

and

s

350 Version 3.1.0

Operator Groups

The Edit Monitor dialog contains the trigger when menu, which allows you to define theconditions that must occur for a monitor to send an alert. The values displayed in this menuvary, depending on whether the monitor uses a numeric value, a string value, or a statusmessage. These options are defined in operator groups. Each option of an operator groupserves as a mathematical or logical evaluator. Each operator description includes the valuefor the waddmon –R argument. The quotation marks for each operator are required. If youwant to specify the (never) operator from the command line, omit the –R argument.

Numeric Operator GroupTo define the threshold value, select one of the following options and enter a number in theargument field.

(never)Does not trigger a response. This value only affects the specific response level, notthe entire monitor.

Greater thanRecords the value of each sample, compares it to the specified value, and triggers aresponse when the current value is greater than the specified value. Because itchecks only against the current sample, this type of threshold can trigger after anysample. This operator can be specified at the command line by entering “>”.

Less thanRecords the value of each sample, compares it to the specified value, and triggers aresponse when the current value is less than the specified value. Because it checksonly against the current sample, this type of threshold can trigger after any sample.This operator can be specified at the command line by entering “<”.

Equal toRecords the value of each sample, compares it to the specified value, and triggers aresponse when the current value is equal to the specified value. Because it checksonly against the current sample, this type of threshold can trigger after any sample.This operator can be specified at the command line by entering “=”.

Not equalRecords the value of each sample, compares it to the specified value, and triggers aresponse when the current value is not equal to the specified value. Because itchecks only against the current sample, this type of threshold can trigger after anysample. This operator can be specified at the command line by entering “!=”.

Increases beyondCompares the current value against the previous value and triggers only if the

A


A.

Op

erator

Gro

up

s

current value is greater than both the previous value and the threshold specified inthe argument field. This operator can be specified at the command line by entering“->>”.

Decrease belowRecords the value of each sample and triggers a response when the previousresource value is above the threshold specified in the text field, but the current valueis below the specified threshold. This operator can be specified at the command lineby entering “-<<”.

Increase ofChecks the current value against the previous value and triggers a response when thedifference is greater than or equal to the threshold value. This operator can bespecified at the command line by entering “->=”.

% increase ofChecks the current value as a percentage of the previous value and triggers aresponse when the current value has increased over the previous value by thespecified percentage. This operator can be specified at the command line by entering“%>=”.

Changes byMeasures an absolute difference between the previous and current value. Thisoperator can be specified at the command line by entering “+>”.

Outside rangeCompares each sample against the defined range limit and triggers a response whenthe current value falls outside the specified range. Because the range check is madeagainst the current sample, this monitor type can trigger after any sample. To definethe acceptable range, enter a lower and upper limit separated by a dash in theargument field. This operator can be the argument field. This operator can bespecified at the command line by entering “<>”.

String Operator GroupTo define the threshold value, select one of the following options and enter a string (whichcan include wildcard characters) in the argument field.

(never)Indicates the response level does not trigger a response. This value only affects thespecific response level, not the entire monitor.

Equal toRecords the value of each sample, compares it to the specified value, and triggers aresponse when the current value is equal to the specified value. Because it checksonly against the current sample, this type of threshold can trigger after any sample.This operator can be specified at the command line by entering “==”.

Not equal toRecords the value of each sample, compares it to the specified value, and triggers aresponse when the current value is not equal to the specified value. Because itchecks only against the current sample, this type of threshold can trigger after anysample. This operator can be specified at the command line by entering “!=”.

MatchesChecks the value returned by the query script against the threshold value providedfor user-defined and asynchronous string monitors. A response is triggered if the

352 Version 3.1.0

response matches the value provided. The query program is named in the AddMonitor to Tivoli Distributed Monitoring Profile dialog. This operator can bespecified at the command line by entering “=x”.

MismatchesChecks the value returned by the query script against the threshold value providedfor the user-defined and asynchronous string monitors. A response is triggered if theresponse does not match the value provided. The query program is named in theAdd Monitor to Tivoli Distributed Monitoring Profile dialog. This operator canbe specified at the command line by entering “!x”.

Changes toCompares the current value (returned by the query script and compared to thethreshold value provided for user-defined and asynchronous string monitors) againstthe previous value. A response is triggered if the current value matches the valueprovided, but the previous value did not. The query program is named in the AddMonitor to Tivoli Distributed Monitoring Profile dialog. This operator can bespecified at the command line by entering “->”.

Changes fromCompares the current value (returned by the query script value and compared to thethreshold value provided for user-defined and asynchronous string monitors) againstthe previous value. A response is triggered if the current value does not match thevalue provided, but the previous value did. The query program is named in the AddMonitor to Tivoli Distributed Monitoring Profile dialog. This operator can bespecified at the command line by entering “-<”.

Status Operator GroupTo define the status value, select one of the following options. The resource to be monitoredis named in the Add Monitor to Tivoli Distributed Monitoring Profile dialog.

(never)Indicates the response level does not trigger a response. This value only affects thespecific response level, not the entire monitor.

Is up/availableChecks the status of system resources, such as daemons, host, and print queues. Aresponse is triggered if the resource is available. This operator can be specified atthe command line by entering “==” “up”.

Is down/unavailableChecks the status of system resources, such as daemons, hosts, and print queues. Aresponse is triggered if the resource is not available. This operator can be specifiedat the command line by entering “==” “down”.

Becomes availableChecks the status of system resources, such as daemons, host, and print queues. Aresponse is triggered if the resource was not available in the previous sample and isavailable in the current sample. This operator can be specified at the command lineby entering “->” “up”.

Becomes unavailableChecks the status of system resources, such as daemons, host, and print queues. A


A.

Op

erator

Gro

up

s

response is triggered if the resource was available in the previous sample and is notavailable in the current sample. This operator can be specified at the command lineby entering “->” “up”.

Same asChecks the return string. A response is triggered if the return string matches the oneprovided. To define the threshold value, enter a string in the argument field. Thisoperator can be specified at the command line by entering “>”.

Different fromChecks the return string. A response is triggered if the return string is not the sameas the one provided. This operator can be specified at the command line by entering“>”.

354 Version 3.1.0

Index

Special Characters.nsf files, listing for backup 251, 329.ntf files, listing for backup 251, 329

AAccess Control List (ACL) entries

changing 243, 302viewing 238, 321

access levels, viewing 238, 321Activate Databases task 218agent, database, verifying schedule 81Agent Manager process, monitoring 13, 79Agent monitor

Real-Time collection 13Statistics collection 79

Agent’s Last Return Code monitor 81Archive Transactional Log task 220arguments, generic, monitoring 29, 109asynchronous monitors, about 75, 199availability of servers, monitoring 171

Bbackups, database

incremental 240, 324listing backup versions 259, 334listing database files 251, 329restoring and activating 267, 340selective 269, 342

bash shell 2Bourne shell 2

CC shell 2calendar event entry, monitoring the time required to create and

delete from a Domino Performance Station 200Calendar Manager process, monitoring 15, 82Calendar monitor


Check Database Corruption task 221Check Health task 223Check Inactive Users task 225Check Replication task 226Clean Database task 228Cluster Availability Status monitor 83

clustered servers, checking status 83Comm monitor


commandsrunning 1running on UNIX 2running on Windows NT 2special characters 4syntax 4

commands, Dominoquit 277, 348show stat 11

commands, Domino server, executing 266, 339commands, Tivoli Manager for Domino

wdpsaddserver 283wdpscreate 284wdpsdelete 285wdpsintegrity 286wdpsprobeonce 287wdpsprobestatus 289wdpsqueryservers 290wdpsreboot 291wdpsremoveserver 292wdpsstart 293wdpsstartengine 294wdpsstartmonitors 295wdpsstop 296wdpsstopengine 297wdpsstopmonitors 298wtmdaclmod 302wtmdactivatedbs 305wtmdarchivetranslog 306wtmdcheckhealth 307wtmdcheckrep 308wtmdchkdbcorruption 310wtmdchkinactusers 311wtmdcleandb 312wtmdcreateserver 313wtmddbactivity 317wtmddeletemail 319wtmddeleteserver 320wtmdgetacl 321wtmdinactivatetranslog 323wtmdincrementalbackup 324wtmdlocateserver 325wtmdmailwaiting 326wtmdpurgemail 327wtmdqueryactivate 328wtmdquerybackup 329wtmdquerydoc 330wtmdquerylog 331wtmdquerynab 333wtmdqueryrestore 334wtmdquerystat 335


Ind

ex

commands, Tivoli Manager for Domino (continued)wtmdquerytranslog 336wtmdrecyclentsvrsvc 337wtmdrecycleserver 338wtmdremoteconsole 339wtmdrestoredbs 340wtmdselectivebackup 342wtmdstartengine 343wtmdstartmonitors 344wtmdstartserver 345wtmdstopengine 346wtmdstopmonitors 347wtmdstopserver 348wtmdverifymail 349

communications, Domino network, monitoring 16, 84Configure TEC for TMD task 235corrupt database views, monitoring for 97, 98

Ddata rollup interval, monitoring 96Data Rollup Interval monitor 96database, monitoring, removing entries from 228, 312database, user mail, obtaining values for 191database agent, verifying schedule 81database backups

incremental 240, 324listing backup versions 259, 334listing database files 251, 329selective 269, 342

Database Frequency monitor 88Database monitor


Database.RM monitorReal-Time collection 20Statistics collection 90

Database.Statistics.Async monitor 93Database.Statistics.Sync monitor 94databases

access time, monitoring from a Domino PerformanceStation 202

ACL entries, viewing 238, 321activating a restored database 218, 305activity, checking for 253, 317activity, monitoring 17, 85checking for and fixing corruption 221, 310monitoring for corrupt views 97, 98read/write activity, monitoring 88replication, monitoring 54, 153restored but not activated 250, 328restoring and activating 267, 340router mailbox, monitoring use of 127statistics, monitoring 93, 94template, monitoring changes in 99, 100

Db.Corruption.Async monitor 97Db.Corruption.Sync monitor 98Db.Template.Async monitor 99Db.Template.Sync monitor 100

Delete Server task 237Disk monitor


disk space, monitoring 23, 102Disk.SYS monitor


domain, server, identifying 325Domino cluster, checking status of servers 83Domino monitor


Domino network communications, monitoring 16, 84Domino news server, monitoring 44, 144Domino news server (remote), monitoring 47Domino Performance Station monitoring collection, about 1,

199Domino Performance Stations

adding a server to be probed 283availability, monitoring 204calendar performance, monitoring 200controller and probe status 286creating 284database access time, monitoring 202deleting 285mail response time, monitoring 205NAB search time, monitoring 207network performance, monitoring 209network recommendations 284performance, measuring 287performance issues 284probe ID, obtaining 287probe ID, viewing data from 289rebooting 263, 291replication time, monitoring 211servers probed by 290starting monitoring 274, 295starting the controller and probes 273, 293starting the local event engine 294status, monitoring 204stop probing a server from 292stopping monitoring 279, 298stopping the controller and probes 278, 296stopping the local event engine 297web page access time, monitoring 213

Domino server commands, executing 266, 339Domino Server Memory Assessment statistic, monitoring 35,

135Domino server process

checking the health of 223, 307restarting 265, 338starting 272, 345stopping 277, 348

DPSCalendarEntry monitor 200DPSDatabaseAccess monitor 202DPSIntegrity monitor 204DPSNABSearch monitor 207DPSNetEcho monitor 209DPSReplicateLocal monitor 211DPSRoundTripMail monitor 205

356 Version 3.1.0

DPSWebAccess monitor 213

Eendpoint

monitoring 108setting up the Tivoli environment on 4

Endpoint Monitor monitor 108event engine, local

starting on a Domino Performance Station 294stopping on a Domino Performance Station 297

event engine, Tivoli Enterprise Consolestarting 270, 343stopping 275, 346

event group, setting up 235events, configuring the Tivoli Enterprise Console to

handle 235

GGeneric monitor


Get ACLs task 238

IICM monitor 110IMAP monitor 112Inactivate Transaction Logging task 239Incremental Backup task 240incremental database backups 240, 324Internet Cluster Manager (ICM) statistics, monitoring 110Internet Mail Access Protocol (IMAP) statistics,

monitoring 112Internet-related statistics, monitoring 39, 139

KKorn shell 2

LLDAP monitor 114Lightweight Directory Access Protocol (LDAP) statistics,

monitoring 114log files

monitoring archiving of 190monitoring the size of 188querying 255, 331

log files (continued)viewing contents of 330

Log.nsf filefield name where strings were found 118form name where strings were found 119note ID where strings were found 121querying for a string 116statistics on strings found 120

LogQuery (Field Name) monitor 118LogQuery (Form Name) monitor 119LogQuery (Found string) monitor 120LogQuery (Log.nsf) monitor 116LogQuery (Note ID) monitor 121

Mmail

addressed to a remote server, monitoring statistics relatedto 125

comparing NAB mail user entries to mail files 280, 349database, user, monitoring statistics relating to 191deleting 319file, user, monitoring statistics relating to 192listing 248, 327listing waiting mail 242, 326number of messages waiting in mailbox 131, 132purging 248, 327response time, monitoring from a Domino Performance

Station 205routing, monitoring 30, 122stalled, monitoring 183, 184tracing 129viewing 319

mail filelisting mail in 248, 327purging mail from 248, 327

Mail monitorReal-Time collection 30Statistics collection 122

mail probes, monitoring response time 51, 152mail store, shared, monitoring 48, 149Mail Trace monitor 129Mail Transfer Agent (SMTP), monitoring statistics related

to 63, 177Mail Transfer Agents, monitoring 36, 136Mail.Waiting.Async monitor 131Mail.Waiting.Sync monitor 132Mail Waiting task 242mailbox databases, router, monitoring use of 127mailboxes

deleting first message in 319listing waiting mail 242, 326monitoring stalled mail in 183, 184number of messages waiting in 131, 132viewing first message in 319

MailByDest.<DestServerName> monitor 125Mailn.box monitor 127memory, monitoring 33, 133


Ind

ex

Memory monitorReal-Time collection 33Statistics collection 133

MemoryAssessment monitorReal-Time collection 35Statistics collection 135

Modify Database ACLs task 243monitor triggers 351monitoring

starting on a Domino Performance Station 274, 295starting on a server 271, 344stopping on a Domino Performance Station 279, 298stopping on a server 276, 347

monitoring, scheduling with the Real Time Monitoringmonitor 52

monitoring collectionsDomino Performance Station 1, 199real-time 1, 11statistics 1, 75

monitoring database, removing entries from 228, 312monitors

AgentReal-Time collection 13Statistics collection 79

Agent’s Last Return Code 81Calendar


Cluster Availability Status 83Comm


Data Rollup Interval 96Database


Database Frequency 88Database.RM


Database.Statistics.Async 93Database.Statistics.Sync 94Db.Corruption.Async 97Db.Corruption.Sync 98Db.Template.Async 99Db.Template.Sync 100Disk


Disk.SYSReal-Time collection 24Statistics collection 103

DominoReal-Time collection 26Statistics collection 105

DPSCalendarEntry 200DPSDatabaseAccess 202DPSIntegrity 204DPSNABSearch 207DPSNetEcho 209DPSReplicateLocal 211

monitors (continued)DPSRoundTripMail 205DPSWebAccess 213Endpoint Monitor 108Generic


ICM 110IMAP 112LDAP 114LogQuery (Field Name) 118LogQuery (Form Name) 119LogQuery (Found string) 120LogQuery (Log.nsf) 116LogQuery (Note ID) 121Mail


Mail Trace 129Mail.Waiting.Async 131Mail.Waiting.Sync 132MailByDest.<DestServerName> 125Mailn.box 127Memory


MemoryAssessmentReal-Time collection 35Statistics collection 135

MTAReal-Time collection 36Statistics collection 136

NET.<PortName>Real-Time collection 39Statistics collection 139

NETBIOS.<PortName>Real-Time collection 41Statistics collection 141

nntpReal-Time collection 44Statistics collection 144

NNTP.<RemoteServerName>Real-Time collection 47Statistics collection 147

ObjectReal-Time collection 48Statistics collection 149

POP3Real-Time collection 49Statistics collection 150

QOS.Mail.ISpy.<servername>.ResponseTimeReal-Time collection 51Statistics collection 152

Real Time Monitoring 52Replication


Replication (Database Replication Info) 157Replication (Duration) 158Replication (End Time) 159Replication (Hit/Miss/Manual) 160

358 Version 3.1.0

monitors (continued)Replication (ID) 161Replication (Remote Server Name) 162Replication (Replication Events) 163Replication (Server Name) 164Replication (server name that initiated replication) 165Replication (Start Time) 166Replication Check 155Server


Server Availability 171Server.Health.Async 172Server.Health.Sync


SMTPReal-Time collection 61Statistics collection 175

SMTP.<Name>Real-Time collection 65Statistics collection 179

SMTPMTAReal-Time collection 63Statistics collection 177

SPINReal-Time collection 66Statistics collection 181

Stalled.Mail.Async 183Stalled.Mail.Sync 184SwapDisk


Tdp Schedule 186Transaction Log File Size 188Transaction Logging Archival Status 190UserMail.Statistics.Async 191UserMail.Statistics.Sync 192Web Monitor


XPC.<PortName>Real-Time collection 72Statistics collection 197

MTA monitorReal-Time collection 36Statistics collection 136

NNAB

comparing mail user entries to mail files 280, 349monitoring search time from a Domino Performance

Station 207querying 258, 333replication schedule 226, 308

NET.<PortName> monitorReal-Time collection 39Statistics collection 139

NETBIOS.<PortName> monitorReal-Time collection 41Statistics collection 141

NetBIOS statistics, monitoring 41, 141NetWare SYS file, monitoring 24, 103network communications, Domino, monitoring 16, 84Network News Transport Protocol remote server statistics,

monitoring 47Network News Transport Protocol server statistics,

monitoring 44, 144network performance, monitoring from a Domino Performance

Station 209NNTP.<RemoteServerName> monitor


nntp monitorReal-Time collection 44Statistics collection 144

NNTP remote server statistics, monitoring 47NNTP server statistics, monitoring 44, 144notes.ini file 35, 135, 173, 237, 313, 320, 325NSF_Buffer_Pool_Size setting in notes.ini file 35, 135numeric statistics, monitoring 26, 105

OObject monitor


operator groups 351

PPOP3 monitor


POP3 statistics, monitoring 49, 150ports

available for a server 325monitoring NetBIOS statistics 41, 141XPC console, monitoring statistics related to 72, 197

Post Office Protocol 3 statistics, monitoring 49, 150probe ID

obtaining 287viewing data from 289

probesmeasuring performance 287starting 273, 293stopping 278, 296

probes, mail, monitoring response time 51, 152process, Domino server

checking the health of 223, 307restarting 265, 338starting 272, 345stopping 277, 348

processes, monitoringAgent Manager 13, 79


Ind

ex

processes, monitoring (continued)Calendar Manager 15, 82Tivoli Data Protection 186Web Retriever 69, 194

Purge Mail task 248

QQOS.Mail.ISpy.<servername>.ResponseTime monitor


Query Activate task 250Query Backup task 251Query Database Activity task 253Query Log task 255Query NAB task 258Query Restore task 259Query Statistics task 261Query Transaction Log task 262

Rread activity, monitoring 88Real-Time monitoring collection, about 1, 11Real Time Monitoring monitor 52Reboot Station task 263rebooting Domino Performance Stations 263, 291Recycle NT Server Service task 264Recycle Server task 265Remote Console task 266replication

comparing actual to scheduled 155duration of 158end time 159events that occurred during replication 163ID for replication occurrence 161monitoring related statistics 54, 153name of server initiating replication 165name of source server 164remote server name 162schedule 226, 308start time 166time, monitoring from a Domino Performance Station 211verifying 160viewing database replication information 157

Replication (Database Replication Info) monitor 157Replication (Duration) monitor 158Replication (End Time) monitor 159Replication (Hit/Miss/Manual) monitor 160Replication (ID) monitor 161Replication (Remote Server Name) monitor 162Replication (Replication Events) monitor 163Replication (Server Name) monitor 164Replication (server name that initiated replication)

monitor 165Replication (Start Time) monitor 166Replication Check monitor 155

Replication monitorReal-Time collection 54Statistics collection 153

Restore Databases task 267restoring databases 267, 340rollup interval, monitoring 96router mailbox databases, monitoring use of 127rule base, setting up 235

Sscheduling monitors with the Real Time Monitoring

monitor 52Selective Backup task 269selective database backups 269, 342Server Availability monitor 171server commands, executing 266, 339Server.Health.Async monitor 172Server.Health.Sync monitor


Server monitorReal-Time collection 56Statistics collection 167

server process, Dominorestarting 265, 338starting 272, 345stopping 277, 348

Server service (Windows NT), restarting 264, 337server statistics, monitoring 56, 167servers

availability, monitoring 171clustered, checking status 83creating in the Tivoli environment 313deleting from the Tivoli environment 237, 320domain, identifying 325health, monitoring 60, 172, 173memory, monitoring 33, 133notes.ini file 325ports available for 325probed by a Domino Performance Station 290probing by Domino Performance Stations 283replication, verifying 226, 308statistics, querying 261, 335stop probing from a Domino Performance Station 292tasks, monitoring 60, 172, 173viewing information about 258, 325, 333

service level objectives, tracking 199shared mail store, monitoring 48, 149shells

bash 2Bourne 2C 2establishing the Tivoli environment in 3Korn shell 2UNIX 2

show stat command 11Simple Mail Transfer Protocol (SMTP), monitoring statistics

related to 61, 175

360 Version 3.1.0

Simple Mail Transfer Protocol (SMTP) devices, monitoringstatistics related to 65, 179

Simple Mail Transfer Protocol (SMTP) Mail Transfer Agent,monitoring statistics related to 63, 177

SMTP.<Name> monitorReal-Time collection 65Statistics collection 179

SMTP, monitoring statistics related to 61, 175SMTP devices, monitoring statistics related to 65, 179SMTP Mail Transfer Agent, monitoring statistics related to 63,

177SMTP monitor


SMTPMTA monitorReal-Time collection 63Statistics collection 177

SPIN, monitoring statistics related to 66, 181SPIN monitor


stalled mail, monitoring 183, 184Stalled.Mail.Async monitor 183Stalled.Mail.Sync monitor 184Start Engine task 270Start Monitors task 271Start Server task 272Start Station Monitors task 274Start Station task 273statistics, monitoring

database 93, 94Domino Server Memory Assessment 35, 135Internet Cluster Manager (ICM) 110

statistics, server, querying 261, 335Statistics monitoring collection, about 1, 75statistics related to, monitoring

Agent Manager process 13, 79Calendar Manager process 15, 82database activity 17, 85database replication 54, 153disk space 23, 102Domino network communications 16, 84Domino news server 44, 144Domino news server (remote) 47Domino servers 56, 167Internet 39, 139Internet Mail Access Protocol (IMAP) 112Lightweight Directory Access Protocol (LDAP) 114mail addressed to a remote server 125mail routing 30, 122Mail Transfer Agents 36, 136memory 33, 133NetBIOS 41, 141NetWare SYS file 24, 103Network News Transport Protocol (NNTP) remote

server 47Network News Transport Protocol (NNTP) server 44, 144numeric statistics 26, 105Post Office Protocol 3 (POP3) 49, 150shared mail store 48, 149Simple Mail Transfer Protocol (SMTP) 61, 175

statistics related to, monitoring (continued)SMTP devices 65, 179SMTP Mail Transfer Agent 63, 177SPIN 66, 181SwapDisk 68, 185Tivoli Data Protection 186transactional logging 20, 90user mail file 192Web Retriever process 69, 194XPC console port 72, 197

Stop Engine task 275Stop Monitors task 276Stop Server task 277Stop Station Monitors task 279Stop Station task 278SwapDisk, monitoring statistics related to 68, 185SwapDisk monitor


synchronous monitors, about 75, 199system memory, monitoring 33, 133

Ttasks

Activate Databases 218Archive Transactional Log 220Check Database Corruption 221Check Health 223Check Inactive Users 225Check Replication 226Clean Database 228Configure TEC for TMD 235Delete Server 237Get ACLs 238Inactivate Transaction Logging 239Incremental Backup 240Mail Waiting 242Modify Database ACLs 243Purge Mail 248Query Activate 250Query Backup 251Query Database Activity 253Query Log 255Query NAB 258Query Restore 259Query Statistics 261Query Transaction Log 262Reboot Station 263Recycle NT Server Service 264Recycle Server 265Remote Console 266Restore Databases 267Selective Backup 269Start Engine 270Start Monitors 271Start Server 272Start Station 273Start Station Monitors 274


Ind

ex

tasks (continued)Stop Engine 275Stop Monitors 276Stop Server 277Stop Station 278Stop Station Monitors 279Verify Mail 280

Tdp Schedule monitor 186template, database, monitoring changes in 99, 100Tivoli Data Protection

commandsdomdsmc activatedbs 218, 305domdsmc archivelogs 220, 306domdsmc inactivatelogs 239, 323domdsmc incremental 240, 324domdsmc query dbbackup 259, 334domdsmc query domino 251, 329domdsmc query logarchive 262, 336domdsmc query pendingdbs 250, 328domdsmc restore 267, 340domdsmc selective 269, 342

configuring 313monitoring schedules 186

Tivoli Enterprise Consoleconfiguring 235starting the local event engine on a Domino Performance

Station 294stopping the local event engine on a Domino Performance

Station 297Tivoli Enterprise Console event engine

starting 270, 343stopping 275, 346

Tivoli environmentestablishing in a shell 3establishing on an endpoint 4establishing on UNIX 3establishing on Windows NT 3

Tivoli Management Agentrestarting after a reboot 263, 291

Tivoli Manager for Dominoadding a server to 313deleting a server from 237, 320

Transaction Log File Size monitor 188Transaction Logging Archival Status monitor 190transactional log files

archiving 220, 306inactivating 239, 323listing archived files 262, 336monitoring archiving of 190monitoring the size of 188restoring before activating the database 218, 305restoring during a database restore 267, 340

transactional logging, monitoring 20, 90triggers for monitors 351

UUNIX

running commands on 2

UNIX (continued)setting up the Tivoli environment 3shell 2

user mail database, obtaining values for 191user mail file, monitoring statistics relating to 192UserMail.Statistics.Async monitor 191UserMail.Statistics.Sync monitor 192

VVerify Mail task 280views, corrupt, monitoring for

disk space 97, 98

Wwdpsaddserver command 283wdpscreate command 284wdpsdelete command 285wdpsintegrity command 286wdpsprobeonce command 287wdpsprobestatus command 289wdpsqueryservers command 290wdpsreboot command 291wdpsremoveserver command 292wdpsstart command 293wdpsstartengine command 294wdpsstartmonitors command 295wdpsstop command 296wdpsstopengine command 297wdpsstopmonitors command 298Web Monitor monitor


web page access time, monitoring from a Domino PerformanceStation 213

Web Retriever process, monitoring statistics related to 69, 194Windows NT

running commands on 2setting up the Tivoli environment 3

Windows NT Server service, restarting 264, 337write activity, monitoring 88wtmdaclmod command 302wtmdactivatedbs command 305wtmdarchivetranslog command 306wtmdcheckhealth command 307wtmdcheckrep command 308wtmdchkdbcorruption command 310wtmdchkinactusers command 311wtmdcleandb command 312wtmdcreateserver command 313wtmddbactivity command 317wtmddeletemail command 319wtmddeleteserver command 320wtmdgetacl command 321wtmdinactivatetranslog command 323wtmdincrementalbackup command 324

362 Version 3.1.0

wtmdlocateserver command 325wtmdmailwaiting command 326wtmdpurgemail command 327wtmdqueryactivate command 328wtmdquerybackup command 329wtmdquerydoc command 330wtmdquerylog command 331wtmdquerynab command 333wtmdqueryrestore command 334wtmdquerystat command 335wtmdquerytranslog command 336wtmdrecyclentsvrsvc command 337wtmdrecycleserver command 338wtmdremoteconsole command 339wtmdrestoredbs command 340wtmdselectivebackup command 342wtmdstartengine command 343wtmdstartmonitors command 344wtmdstartserver command 345wtmdstopengine command 346wtmdstopmonitors command 347wtmdstopserver command 348wtmdverifymail command 349

XXPC.<PortName> monitor


XPC console port, monitoring statistics related to 72, 197


Ind

ex

364 Version 3.1.0

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC32-0675-00

Date post:	18-Jan-2020
Category:	Documents
Upload:	others
View:	21 times
Download:	0 times