tivoli workload scheduler -...

Tivoli WorkloadSchedulerPlus Module User’s GuideVersion 7.0

Tivoli Workload Scheduler Plus Module User’s Guide (May 2000)

Copyright Notice

Copyright ©2000 by Tivoli Systems Inc., an IBM Company, including this documentation and all software. All rightsreserved. May only be used pursuant to a Tivoli Systems Software License Agreement or Addendum for Tivoli Products toIBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in aretrieval system, 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 Tivoli Systems. Tivoli Systems grants youlimited permission to make hardcopy or other reproductions of any machine-readable documentation for your own use,provided that each such reproduction shall carry the Tivoli Systems copyright notice. No other rights under copyright aregranted without prior written permission of Tivoli Systems. The document is not intended for production and is furnished“as is” without warranty of any kind. All warranties on this document are hereby disclaimed including the warrantiesof merchantability and fitness for a particular purpose.

Note to U.S. Government Users—Documentation related to restricted rights—Use, duplication or disclosure is subject torestrictions set forth in GSA ADP Schedule Contract with IBM Corporation.

Trademarks

The following product names are trademarks of Tivoli Systems or IBM Corporation: AIX, IBM, MVS, OPC, Tivoli, andTME.

Tivoli is a registered trademark or trademark of Tivoli Systems Inc. in the United States, other countries or both. InDenmark, Tivoli is a trademark licensed from Kjøbenhavns Sommer - Tivoli A/S.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks or registered trademarks of Microsoft Corporationin the United States, other countries, or both.

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

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

Other company, product, and service names mentioned in this document 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, or services isnot intended to imply that only Tivoli Systems or IBM products, programs, or services can be used. Subject to TivoliSystem’s or IBM’s valid intellectual property or other legally protectable right, any functionally equivalent product, program,or service can be used instead of the referenced product, program, or service. The evaluation and verification of operation inconjunction with other products, except those expressly designated by Tivoli Systems or IBM, are the responsibility of theuser.

Tivoli Systems or IBM may have patents or pending patent applications covering subject matter in this document. Thefurnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to theIBM Director of Licensing, IBM Corporation, North Castle Drive, Armonk, New York 10504-1785, U.S.A.

Contents

Figures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Preface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixWho Should Read This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Prerequisite and Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

What This Guide Contains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Conventions Used in This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

Contacting Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Installation Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Hardware Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Chapter 2. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Installing from the Tivoli Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Installing from the Command Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Setting the TWS Installation Options . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Tivoli Plus Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Tivoli Plus Unique Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Adding TME 10 Products after Installation . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installing Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Starting the TWS Plus module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Launching the TWS Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 3. Software Distribution . . . . . . . . . . . . . . . . . . . . . . . . 17Creating the tws_cpu.map File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

Example Entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

iiiTivoli Workload Scheduler Plus Module User’s Guide

Before and After Programs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuring File Packages for UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuring File Packages for Windows NT . . . . . . . . . . . . . . . . . . . . . . . . 23

Installing TWS on All Configured Platforms . . . . . . . . . . . . . . . . . . . . . . . . 25

Installing TWS on a Single Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Chapter 4. Distributed Monitoring . . . . . . . . . . . . . . . . . . . . . . . 29Using TWS Plus Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Viewing the Status of Monitored Resources . . . . . . . . . . . . . . . . . . . . . . . . . 31

Monitored Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Host status Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Application Status (batchman) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Application Status (netman). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Application Status (mailman). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Application Status (jobman). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

TWS SpaceFree. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

TWS SpaceUsed (stdlist) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

TWS SpaceUsed (schedlog). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Page-Outs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

iv Version 7.0

Swap Space Available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Chapter 5. Enterprise Event Management . . . . . . . . . . . . . . 41Setting Up the Tivoli Enterprise Console . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Tivoli Enterprise Console Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Configuring the Logfile Adapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Configuring the Non-TME Logfile Adapter . . . . . . . . . . . . . . . . . . . . . 44

Configuring the TME Logfile Adapter . . . . . . . . . . . . . . . . . . . . . . . . . 44

Events and Rules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

TWS Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Distributed Monitoring Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Chapter 6. TWS Plus Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Starting the Job Scheduling Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

TWS Network Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

TWS Reporting Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

TWS Plus Module Configuration Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Running a TWS Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Modifying a TWS Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Modifying a Job for Each Run. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Modifying a Job for a Single Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Appendix. Event Configuration Reference. . . . . . . . . . . . . . 61TWS Plus Module Configuration Files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

BmEvents Configuration File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

BmEvents Configuration File Defaults . . . . . . . . . . . . . . . . . . . . . . . . . 64

On the TWS Master workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

vTivoli Workload Scheduler Plus Module User’s Guide

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

vi Version 7.0

Figures

1. Install Product window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72. Product Install window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83. Set TWS Install Options icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94. Set TWS Install Options icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115. TWS Plus for Tivoli Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126. Tivoli Plus Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137. TWS Task Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148. Sample TWS Server Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159. Setup TWS Unix Client Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

10. Setup TWS Windows NT Client Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2411. Subscribers window.. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2612. Install UNIX TWS Clients window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2713. Distribute Profiles window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3014. TWS Server and Client Distribution Lists . . . . . . . . . . . . . . . . . . . . . . . . . . . 3015. TWS Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3116. Setup EventServer for TWS window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4217. Edit Job window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5918. Execute Task window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

viiTivoli Workload Scheduler Plus Module User’s Guide

viii Version 7.0

Preface

The Tivoli Workload Scheduler Plus Module User’s Guide providesinformation on how to set up and use the Tivoli Workload Scheduler(TWS) Plus module. This module provides the managementinstrumentation for specific use with the Tivoli Frameworkenvironment. Using the TWS Plus Module, the TWS application canbe managed across a multi-platform network from a single location.

Who Should Read This GuideThis guide is for system administrators who use the Tivoli Plus forWorkload Scheduler module to monitor the Workload Scheduler jobscheduling environment.

Users of the guide should have some knowledge of:

¶ Tivoli Management Environment

¶ Tivoli Plus modules

¶ Tivoli Workload Scheduler application environment

¶ UNIX and Windows NT operating systems

Prerequisite and Related DocumentsThe following document contains information related to Tivoli Plusfor Workload Scheduler:

¶ Tivoli Workload Scheduler User’s Guide

Provides information about setting up and managing the TivoliWorkload Scheduler job scheduler.

¶ Tivoli Plus User’s Guide

Provides general information on using Tivoli Plus to monitorproduction control applications.

What This Guide ContainsThis manual includes the following sections:

ixTivoli Workload Scheduler Plus Module User’s Guide

Chapter 1Introduction—provides an introduction to the product andgeneral considerations.

Chapter 2Installation—describes how to install and distribute theTivoli Workload Scheduler Plus Module.

Chapter 3Software Distribution—provides information on using theSoftware Distribution features of the TWS Plus Module.

Chapter 4Distributed Monitoring—provides information aboutpreconfigured monitors available for identifying events inTivoli Workload Scheduler.

Chapter 5Enterprise Event Management—provides information onconfiguring the logfile adapter and the event rules used bythe TWS Plus Module.

Chapter 6TWS Plus Tasks—provides procedures for using the TWSPlus module for Tivoli Workload Scheduler.

Appendix AEvent Configuration Reference—provides detailedinformation on the trigger events for the TWS Plus module.

Conventions Used in This GuideThe following conventions are used in this guide to describe thespecial terms or commands. These conventions have the followingmeanings:

Bold Commands, keywords, file names, or other information thatyou must use literally appear bold.Names of windows,dialogs, and other controls also appear bold.

Italics Variables and values that you must provide appear in italics.

MonospaceCode examples appear in monospace font.

x Version 7.0

Contacting Customer SupportIf you are entitled to Tivoli customer support, you can findfrequently updated information about configuring and using Tivoliproducts from the Tivoli Customer Support home page athttp://www.tivoli.com/support/. This site includes the followinglinks:

¶ Updated versions of these release notes:http://www.tivoli.com/support/Prodman/html/RN.html

¶ Updated versions of Tivoli documentation:http://www.tivoli.com/support/documents/

¶ Searchable support databases:http://www.tivoli.com/tivoli.ww.reg/rform?lang=english

¶ Access to product patches:http://www.tivoli.com/support/patches/

¶ Access to training schedules:http://www.tivoli.com/services/education/

¶ Access to Tivoli documentation survey:http://www.tivoli.com/support/survey/

Visit the Tivoli Customer Support site for this information andadditional customer services. These URLs do require a password andID. If you do not have access privileges or are unsure of your ID orpassword, send e-mail [email protected]. Include your nameand your company name in this correspondence.

You can order additional copies of product documentation bysending e-mail or calling one of the following locations:

¶ U.S. Customer E-mail: [email protected]

¶ U.S. Telephone: 1-800-879-2755

¶ Canada Telephone: 1-800-426-4968

¶ International Telephone: (770) 863-1234

Please provide the title and version number of the document that youare ordering.

xiTivoli Workload Scheduler Plus Module User’s Guide

xii Version 7.0

Introduction

The Tivoli Workload Scheduler Plus module (TWS Plus module)provides an integration of the Tivoli TME environment with theTWS job scheduler. This module provides the following features formanaging the TWS application:

¶ Icons for launching the TWS application

¶ Subscription lists for clients and servers

¶ File Packages for Tivoli Software Distribution

¶ Monitors for Tivoli Distributed Monitoring

¶ Tivoli Enterprise Console events and rule sets customized forTWS

¶ TWS-specific tasks and jobs

Note: Tivoli Software Distribution and Tivoli DistributedMonitoring applications must be installed and configuredbefore their corresponding Tivoli Plus feature is operational.

Installation RequirementsBefore installing TWS Plus module into TME, make certain youreview the requirements in this section.

The following table provides the context and authorization rolerequired to install TWS Plus module.

1

1Tivoli Workload Scheduler Plus Module User’s Guide

1.In

trod

uctio

n

Activity Context Required Role

Installing TWS Plusmodule

TME install_product

In order for the TWS Plus module to function correctly, it must beinstalled on the following machines:

¶ Tivoli server

¶ Tivoli Enterprise Console server (if there is one)

¶ Optional: TWS master workstation.

Software RequirementsThe following software is required and must be installed prior toinstalling the TWS Plus module:

¶ Tivoli Framework version 3.6 or higher

¶ Tivoli Workload Scheduler version 7.0

The TWS Plus module has features that require the following TivoliFramework products:

¶ Tivoli Software Distribution

¶ Tivoli Software Distribution Gateway (required for distributingfile packages to endpoints)

¶ Tivoli Distributed Monitoring Universal Monitors

¶ Tivoli Enterprise Console

If these applications are not installed, then the specific featurerequiring these products will not work.The TWS Plus moduleinstallation enables you to incrementally re-install the TWS Plusmodule features if you purchase the missing products at a later date.

Hardware RequirementsThe following table provides the client and server disk spacerequirements for TWS Plus module. This space is in addition to thespace requirements for the management platform, the Tivoliapplication, and the TWS engine.

Installation Requirements

2 Version 7.0

The TWS Plus module is installed on the TME server, the TivoliEnterprise Console server (if you have the Tivoli EnterpriseConsole), and the TWS master workstation. The space requirementsare the same for all of these machines. The TWS Plus module usesplatform-independent shell and Perl scripts, which allows themodule’s requirements to remain consistent from platform toplatform.

Platforms Binaries Message Catalogs

AIX 1575K 568K

HP-UX 1575K 568K

SVR4 1575K 568K

SunOS 1575K 568K



1.In

trod

uctio

n


4 Version 7.0

Installation

This chapter contains information on how to install the TWS Plusmodule to the Tivoli TME Desktop. The TWS Plus module must beinstalled from within the Tivoli TME Desktop.

Installing from the Tivoli DesktopUse the following steps to install the TWS Plus module.

1. Open the Tivoli TME Desktop.

2. From the Desktop menu, select the Install > Install Product...option. This displays the Install Product dialog. If the TWSPlus module is listed in the Select Product to Install field, skipto step 2. If it is not listed, follow the instructions below:

a. Press the Select Media... button to display the FileBrowserdialog.

b. The File Browser dialog enables you to find or specify thepath to the installation media.

c. If you already know the path to the product CD-ROM:

¶ Enter the full path in the Path Name field.

¶ Press the Set Path button to change to the specifieddirectory.

2


2.In

stallation

¶ Press the Set Media & Close button to save the newmedia path and return to the Install Product dialog. Thedialog now contains a list of products that are availablefor installation.

d. If you do not know the exact path to the product CD-ROM:

¶ From the Hosts scrolling list, choose the host on whichthe install media is mounted. Choosing a host updatesthe Directories scrolling list to show the directories ofthe host you chose.

¶ From the Directories scrolling list, choose the directorycontaining the install media.

¶ Press the Set Media & Close button to save the newmedia path and return to the Install Product dialog.The dialog now contains a list of products that areavailable for installation.

3. Select Plus Module Support (Link binaries) = 3.1.n from theSelect Product to Install list.

Installation from the Tivoli Desktop

6 Version 7.0

4. Use the arrow keys to move the machine names from theAvailable Clients field to the Clients to Install field to specifythe clients on which the Link binaries will be installed.

5. Press the Install button to install the Link binaries.

6. Press the Continue Install button to begin installation or pressthe Cancel button to abort installation.

Figure 1. Install Product window



2.In

stallation

7. Press the Close button when the Product Install Status dialogindicates that installation is complete.

8. Select TWS Plus module from the Select Product toInstalllist.

9. Use the arrow keys to move the machine names from theAvailable Clients field to the Clients to Install field to specifythe clients on which the Link binaries will be installed.

10. To specify the clients on which the Link binaries will beinstalled, use the arrow keys to move machine names from theAvailable Clients field to the Clients to Install On field.

11. Press the Install button to install the TWS Plus module.

Figure 2. Product Install window


8 Version 7.0

The installation process prompts you with the Install Optionsdialog.

This dialog allows you to specify the name of the TWS userand the path to the directory where TWS is installed.

When installing on the TME server:

¶ If TWS is not installed on the Tivoli Server, the TWS userand installation directory should be set to match those onthe TWS Master workstation.

¶ If TWS is installed on the Tivoli Server, specify the TWSuser and directory that is used on the Tivoli server.

12. Enter the TWS user name.

13. Enter the TWS installation directory path.

14. Enter the Job Scheduling Console installation directory path.

15. Click the Set and Close button. This returns you to the InstallProduct dialog.

16. Click the Install button to continue with the Installation. TheProduct Install dialog is displayed. This dialog provides the listof operations that take place when installing the software. Thisdialog also warns you of any problems that you may want tocorrect before you install the TWS Plus module.

Figure 3. Set TWS Install Options icon



2.In

stallation

17. Press the Continue Install button to begin the installationprocess, or press the Cancelbuttonto abort the installationprocess.

18. When the installation is complete, the install dialog displays acompletion message at the bottom of the Product Installdialog.

19. Press the Closebutton when the Product Install status dialogindicates that the installation is complete.

Installing from the Command LineThe following example command installs the TWS Plus module:winstall -c path -i TWS TWSUSER=TWS TWSDIR=/usr/TWS

JSCONSOLEDIR=/usr/TWS/JSCONSOLE

where:

-cpath Specifies the path to the CD-ROM image.

-sinst_serverSpecifies the server on which the product is to be installed.

-iix_fileSpecifies the index file from which the product is to beinstalled.

TWSUSER=Specifies the TWS user name.

TWSDIR=Specifies the directory where the TWS executables arelocated.

JSCONSOLEDIR=Specifies the directory where the TWS executables arelocated.

See the winstall command in the Tivoli Management PlatformReference Manual for more information.


10 Version 7.0

Setting the TWS Installation OptionsIn order for several tasks in this module to execute properly, youmust specify the TWS user name and the path to the TWSexecutable files. This can be specified during installation or afterinstallation using the Set TWS Install Options icon in the TWSPlus module collection. Without this information, several of the tasksfor this module fail due to path problems.

This task should be run on TWS agents where the Plus module hasnot been installed and whose TWS directory is different than the onespecified when the Plus module was installed on the TME Server.This task must be executed on all Managed Nodes and TMAs thatare part of the TWS environment. If this task is not executed, manyof the tasks for this module will fail as well as some of thedistributed monitors.

Tivoli Plus IconsThe Tivoli Plus icons can be activated in either of two ways:

¶ Opening or executing the icon by double-clicking on it with theleft mouse button. In many cases, double-clicking executes anactivity (such as a task) without opening another dialog layer.

¶ Displaying the icon’s pull-down menu by pressing and holdingthe right mouse button

Figure 4. Set TWS Install Options icon

Installing from the Command Line


2.In

stallation

Generally, either method may be used to access a particular function.There are cases, however, where a particular function can only beaccessed using one of these methods.

The following icon represents the Tivoli Plus for TWS resources:

Click on this icon to view the commands and monitors for the TWSPlus module.

Tivoli Plus Unique FeaturesTivoli Plus modules use the term profile manager in a somewhatdifferent way than do the other Tivoli products. In a Tivoli Plusmodule, a profile manager’s primary function is as a subscriptionlist. A subscription list identifies the machines that tasks and jobs runon when executed. Subscription lists can contain machine names orother profile managers. Adding a profile manager to a subscriptionlist is simply a way of subscribing several machines at a time ratherthan adding each one individually.

The Tivoli Plus User’s Guide describes the function of profilemanagers in the Tivoli Plus modules in more detail. For moreinformation, see Chapter 2, “Understanding Subscribers and Targets”in the Tivoli Plus User’s Guide.

Figure 5. TWS Plus for Tivoli Icon

Tivoli Plus Icons

12 Version 7.0

Adding TME 10 Products after InstallationIf you install Distributed Monitoring, Software Distribution, or theEnterprise Console after you have installed the TWS Plus module,you must reinstall the TWS Plus module to gain the benefits of theadded application. If you have additional questions, please contactTivoli Customer Support at 1-800-TIVOLI-8.

Installing UpgradesUse the same procedure for upgrading a Tivoli Plus module as youused to install the module.

Note: If you have modified any of the scripts in the module, youshould copy them to a temporary directory before upgrading,as the upgrade process will overwrite the existing files.

Starting the TWS Plus moduleAll Tivoli Plus modules are kept in a collection under the TivoliPlusicon on the TME desktop. The following icon represents the TivoliPlus collection:

Once a Tivoli Plus module has been installed, its icon appears in theTivoli Plus collection. Each Tivoli Plus module has a separate icon,so there may be many icons to choose from.

Use the following steps to see the modules included in your TivoliPlus collection:

1. From the main TME desktop, double-click on the TivoliPlusicon.

Figure 6. Tivoli Plus Icon

Adding TME 10 Products after Installation


2.In

stallation

2. The TivoliPlus window displays an icon for each Tivoli Plusmodule installed.

3. Double-click on the TWS Plus for Tivoli icon to open themodule, or select Open from the TWS Plus for Tivoli icon’spop-up menu. This displays the icons representing the tasks andother tools for managing the TWS job scheduler. There are 36icons in the TWS Plus module representing TWS servers,monitors, reporting commands, and configuration commands.

Figure 7. TWS Task Icons

Starting the TWS Plus module

14 Version 7.0

Launching the TWS ApplicationWhen TWS Plus module is installed on a TWS server, theinstallation process identifies that a TWS Master is installed andcreates an icon to launch the Job Scheduling Console. If the TWSPlus module is not installed on the TWS master this icon will notappear. In the case where the PLUS module is not installed on theTWS master, the task JSConsole should be used to launch the JobScheduling Console.

Each TWS server has its own icon for launching the TWSapplication from that server site. For example, for a server namedlondon the following icon appears:

When you right click on this server icon the Job SchedulingConsole command is displayed. This command can be used to openthe Job Scheduling Console from within the Tivoli Framework.

Figure 8. Sample TWS Server Icon

Launching the TWS Application


2.In

stallation

16 Version 7.0

Software Distribution

The TWS Plus module includes a hierarchical, pre-configured TivoliSoftware Distribution file package for distributing and installing toTWS clients. Using the TWS Plus module and Tivoli SoftwareDistribution, you can install the TWS application across a UNIX orWindows NT network.

Installing TWS clients is a two-stage process.

1. Set up the TWS installation file packages.

2. Distribute the file packages to the appropriate client workstations.

You set up the TWS installation by configuring a Tivoli SoftwareDistribution file package for each platform on which you areinstalling TWS. For example, if you are installing TWS on a groupof Solaris and Windows NT workstations, you need to configure twoTivoli Software Distribution file packages, one for each platform.

You distribute the configured file packages by running the InstallTWS Clients task. This task installs TWS on the selectedsubscribers.

Creating the tws_cpu.map FileEach TWS workstation installed needs several unique pieces ofinformation, such as its own TWS workstation name, and the nameof the workstation’s TWS Master. A file called tws_cpu.map is usedto distribute this information with the configured file package. This

3


3.S

oftw

areD

istribu

tion

file, which has a simple text format, must be created and includedwith the distribution package. You should have only one copy of thisfile.

A sample file is included in the Tivoli installation directory:bin/generic_unix/TME/PLUS/TWS/tws_cpu.map

This file is required for installation of TWS machines. This file mustcontain one line for each host you wish to install TWS on. Theformat of the entries is:hostname:cpuname:type:master_host:master_tws:

where:

hostnameSpecify the name of the host to install on. The value ofhostname needs to match the results of the uname -ncommand on the host in question.

cpunameSpecify the TWS workstation name for the host. Theworkstation name must conform to the TWS characterrestrictions for workstation names.

type Specify the type of TWS workstation. The valid values fortype are:

¶ master

¶ fta

¶ sagent

¶ backup

master_hostSpecify the workstation name of the host to be designated asthe TWS Master Domain Manager.

master_twsSpecify the TWS name of the Master Domain Managerworkstation.

Creating the tws_cpu.map File

18 Version 7.0

Example EntriesA series of example entries is listed below.

¶ This is an example of a standard agent workstation:dev_12:dev12:sagent:tivoli:tmaster

¶ This is an example of a standalone workstation:noonan:noonan:master:noonan:noonan

¶ This is an example of a FTA workstation:wopr:wopr:fta:tivoli:tmaster

¶ This is an example of a backup workstation:tron:tron:backup:tivoli:tmaster

Before and After ProgramsDuring the package distribution, before and after programs are run toset up a machines environment for TWS.

The before programs on UNIX will create the TWS user in the/etc/passwd file if the user does not exist. It will also create thegroup unison in the /etc/group directory if it does not exist.

The after program on both UNIX and Windows NT will use thetws_cpu.map file to add the TWS workstation to the TWS Masterusing the Add Workstation task.

On UNIX, the after program will update the system startup files tostart TWS when the system reboots.

Configuring File Packages for UNIXWhen configuring a Tivoli Software Distribution file package to beused with TWS Plus module, you need to establish the location ofthe TWS installation directories so that Tivoli Software Distributioncan locate the installation binaries when installing TWS clients.

Use the following steps to set up Tivoli Software Distribution toinstall TWS on each UNIX platform. Online help is available.

Creating the tws_cpu.map File


3.S

oftw

areD

istribu

tion

Note: You need to complete the Setup TWS Unix Client Installwindow for each of the various UNIX platforms on whichyou will be running the TWS application. For example,SunOS will require a different Courier file package thanSolaris.

1. Select the Run job... option from the Setup TWS UNIX ClientInstall icon’s pop-up menu to display the setup window.

Configuring File Packages for UNIX

20 Version 7.0

The Setup TWS Unix Client Install window allows you toconfigure the client installation parameters for a UNIX platform.

2. Select the type of operating system on which you will berunning. If the operating system is not on the list, enter it in theOther field.

Figure 9. Setup TWS Unix Client Install



3.S

oftw

areD

istribu

tion

3. Select the TME Node type, either Managed Node or Endpoint.

4. Identify the location of the TWS source binaries as follows:

a. In the Managed Node Name field, enter the name of theTME server or the managed node where the TWS sourcebinaries are located.

b. In the Get TWS Files from field, select whether the fileswill come directly from a tar file or device or from anuncustomized TWS directory.

Note: You cannot select the Tar File of Device option whenthe source files reside on a Windows NT.

c. In the Path to the Tar File, Device or Directory field, enterthe directory path where the device, tar file, or uncustomizedTWS binaries can be found.

d. If you are installing from a tar file or device, the systemneeds a directory in which to unpack these files beforedistribution. Enter the path to the directory that you choosefor this purpose in the 50 Mb Temp Directory field.

5. After you have installed TWS from a device or tar file, you canuse the scratch directory as the source of the TWS binaries forsubsequent installations. To do this, select Uncustomized TWSDirectory from the Get TWS Files from field and then enter thepath to the scratch directory in the Path to the Tar File, Deviceor Directory field. When you distribute or install TWS for thefirst time, the system creates subdirectories in the directory thatyou specified for the TWS binaries. These subdirectories arenamed with the following format:interpreter_type/TWS

where interpreter_type refers to the platform on which TWSwas installed. On subsequent installations, be sure to specify thefull path name including the additional directories. For example,if the original path was:

/usr/TWS/TWS4.4.7


22 Version 7.0

and you installed on a solaris2 platform, you would specify:

/usr/TWS/TWS4.4.7/solaris2/TWS

6. Identify the destination of the TWS source binaries as follows:

a. In the TWS User Name field enter the name of the TWSuser account.

b. In the TWS Home Directory field, enter the path to theTWS directory where the binaries and libraries for the TWSclient will be distributed and installed.

c. Enter the UNIX user ID in the UNIX User ID for UserTWS field.

d. Enter the UNIX group ID in the UNIX Group ID for Groupunison field.

7. Enter the path name to the TWS workstation map file on theTivoli server. This file contains one line for each workstation onwhich you are installing TWS. The file is necessary for providingcertain information such as the validation code for theworkstation. You create this file and then enter the path name toit on the TWS CPU Map File Path on Tivoli Server field. Seethe online help for assistance in creating this file. The onlinehelp includes an example map file.

8. Press the Set and Close button to set all of the information youhave entered.

Configuring File Packages for Windows NTWhen configuring a Tivoli Software Distribution file package to beused with TWS Plus module, you need to establish the location ofthe TWS installation directories so that Tivoli Software Distributioncan locate the installation executable files when installing TWSclients.

Use the following steps to set up Tivoli Software Distribution toinstall TWS on the Windows NT platform. Online help is available.



3.S

oftw

areD

istribu

tion

1. Select the Run job... option from the Setup TWS Windows NTClient Install icon’s pop-up menu to display the setup window.

The Setup TWS Windows NT Client Install window allowsyou to configure the client installation parameters for WindowsNT.

2. Identify the location of the TWS source files as follows:

a. In the Managed Node Name field, enter the name of theTME server or the managed node where the TWS Installationfiles are located.

b. In the Path to TWS Installation Files: field, enter the pathto the /TWS directory where the installation files are saved.The path must be fully qualified, but not include the /TWSdirectory itself. For example, if the installation files reside in:

Figure 10. Setup TWS Windows NT Client Install

Configuring File Packages for Windows NT

24 Version 7.0

D:/TWS/I386/TWS

The specified path for this field should be:D:/TWS/I386

3. In the TWS Installation Directory field, enter the targetdirectory for the TWS Installation files. The distribution creates aTWS directory, so specify the directory where you want /TWSinstalled.

4. In the TWS Response File Information field, enter the path tothe installation response file (TWS.iss). TWS provides tworesponse files:NCPNCUST.ISS

UCPNCUST.ISS

Modify one of these files to specify the TWS user and password.The NCPNCUST.ISS is for a new installation and theUCPNCUST.ISS is for an update. One of these files must belocated on the TMR server.

Note: For more information on how to modify the ISS file, refer tothe TWS Planning and Installation Guide.

5. In the TWS CPU Map File Path on Tivoli Server field, enterthe path to the TWS_cpu.map file. This file containsinformation about the CPUs in a TWS network.

6. Press the Set and Close button to set all of the information youhave entered.

Installing TWS on All Configured PlatformsAfter you have configured a Tivoli Software Distribution filepackage for each platform on which you wish to install TWS, youare ready to install TWS on these platforms. Output for eachplatform is sent to the source machine in the following directory:/tmp/TWS_client_install.platform_name

where platform_name refers to the operating system on which TWSwas installed.

Configuring File Packages for Windows NT


3.S

oftw

areD

istribu

tion

You will use either the Install NT TWS Clients icon or the InstallUNIX TWS Clients icon to install TWS. If you wish to view theTivoli Software Distribution file packages that you have created,select the Open... option from the Install NT/UNIX TWS Clientsicon’s pop-up menu.

Use the following steps to install TWS clients.

1. Select the Subscribers... option from the Install NT/UNIX TWSClients icon’s pop-up menu. The Subscribers dialog isdisplayed.

2. Specify the subscription lists to which you want to install TWSby using the left-arrow and right-arrow buttons to move thedesired lists into the Current Subscribers field. When finished,press the Set Subscriptions & Close button.

3. Select the Distribute option from the Install NT/UNIX TWSClients icon’s pop-up menu. Selecting this option installs TWSonto the client machines listed on the subscription lists that youchose.

Figure 11. Subscribers window.

Installing TWS on All Configured Platforms

26 Version 7.0

Installing TWS on a Single PlatformIf you want to install TWS on only one operating system platform,you can distribute the Tivoli Software Distribution file package thatonly applies to that platform.

Use the following steps to install TWS on a single platform.

1. Select the Open... option from the Install NT/UNIX TWSClients icon’s pop-up menu.

2. In the Install NT/UNIX TWS Clients window, select theSubscribers... option from the pop-up menu of the iconrepresenting the file package for the platform on which you wishto install TWS.

Note: If you want to distribute to the default subscribers,double-click the icon.

3. Specify the subscription lists to which you want to install TWSon a single platform by using the left-arrow and right-arrowbuttons to move the desired lists into the Current Subscribersfield. When finished, press the Set Subscriptions & Closebutton.

Figure 12. Install UNIX TWS Clients window.

Installing TWS on a Single Platform


3.S

oftw

areD

istribu

tion

4. Select the Distribute option from the icon’s pop-up menu.Selecting this option installs TWS onto the client machines listedon the subscription lists that you chose.

Note: You may need to increase the disk_max parameter inSoftware distribution. The TWS file package requires 120MB. Please consult your Tivoli Software Distributiondocumentation for more information.

Installing TWS on a Single Platform

28 Version 7.0

Distributed Monitoring

The TWS Plus module provides the ability to monitor criticalresources with Tivoli Distributed Monitoring. The DistributedMonitoring monitors enable you to manage different aspects of theoperating system, such as processes, swap space, directory size, orthe TWS server. These monitors allow you to quickly identify andrespond to potential problems so that system downtime is avoided.

Using TWS Plus MonitorsThe TWS monitors check the status of the TWS server, the status ofprocesses, disk space, directory size, and so forth on the remotemachines. Although the TWS Plus monitors come already defined tomonitor resources specific to Workload Scheduler, you can addmonitors from the Tivoli Distributed Monitoring collection.

Before the TWS Plus monitors are operational, they must bedistributed to their subscription lists. To distribute a monitor, simplyselect the Distribute... option from the monitor’s pop-up menu andthen click on the Distribute Now button.

4


4.D

istribu

tedM

on

itorin

g

After installation, the monitors are ready to be distributed to theirdefault subscription list. The TWS Central Monitors are distributedto the Tivoli server. The TWS Remote Monitors are distributed tothe TWS Server List and the TWS Client List.

The default subscription list can be viewed or changed by using theSubscribers... option from the monitor’s pop-up menu.

Selecting the options on a Workload Scheduler monitor’s pop-upmenu displays the usual Tivoli Distributed Monitoring windows.Refer to the Tivoli Distributed Monitoring documentation for moredetailed information on using these windows.

The following commands are displayed when right clicking on theWorkload Scheduler Central Monitors icon.

Command Description

Properties Displays the Distributed Monitoring Profile Propertieswindow, which includes functions for adding, deleting,and editing monitors.

Distribute Displays the Distribute Profiles window for distributingmonitors to those managed nodes (machines) andprofiles included on the monitor’s subscription list.

Figure 13. Distribute Profiles window.

Figure 14. TWS Server and Client Distribution Lists

Using TWS Plus Monitors

30 Version 7.0

Command Description

Subscribers Displays the Subscribers window for specifying towhich subscription list the monitor is distributed.

Viewing the Status of Monitored ResourcesUse the Indicators for TWS Monitors icon to view the status ofthe monitored resources.

The thermometer on the TWS monitor icons rise as the status of amonitored resource changes from a “normal” to a “warning,”“severe,” or “critical” status.

Open the TWS Central Monitors or TWS Remote Monitors iconto view the status of the TWS server or the resources on remotemachines. For each monitored resource, the monitor only reports themost urgent status received within a recent time frame. The monitorreport are organized so that the most urgent status level appears atthe top of the report.

Monitored ResourcesThe following table indicates the network resources that TWS Plusmonitors.

Monitored Resource Icon Name

Host Status TWS Central Monitors

Figure 15. TWS Monitors

Using TWS Plus Monitors


4.D

istribu

tedM

on

itorin

g

Monitored Resource Icon Name

Application status (batchman) TWS Remote Monitors

Application status (netman)

Application status (mailman)

Application status (JOBMAN) (Windows NT only)

Application status (jobman) (UNIX only)

TWS SpaceFree ()

TWS SpaceUsed (stdlist)

TWS SpaceUsed (schedlog)

Page-outs ()

Swap space available ()

Host status AvailabilityMonitors whether the status of a host is up or down.

DescriptionThis Host Statusmonitoring source checks the status of any host orother resource on the network that can respond to a ping request.This monitor checks specifically to see whether the targeted hostsare up or down.

This monitor checks the host status every 15 minutes.

The following table lists the pre-configured actions for thismonitoring source:

Severity Trigger When Default Actions

Fatal N/A None

Critical Becomes unavailable Send event to the TivoliEnterprise Console.Change icon.

Severe N/A None

Warning N/A None

Monitored Resources

32 Version 7.0


Informational Becomes available Send event. Chalngeicon

Normal N/A None

Normal zero N/A None

Always N/A None

Monitors that are defined with this monitoring source use statusoperators to evaluate data. You can select the trigger when pop-upmenu of the Edit Distributed Monitoring Monitor dialog todisplay a list of the available operators.

Application Status (batchman)Monitors whether the batchman process is up and running.

DescriptionThis monitor runs every minute. The following table lists thepre-configured actions for this monitoring source:


Fatal N/A None

Critical N/A Send event to the TivoliEnterprise Console.Change icon.

Severe N/A None

Warning N/A None

Informational Becomes available Send event. Changeicon

Normal N/A None

Normal-zero N/A None

Always N/A None

Host status Availability


4.D

istribu

tedM

on

itorin

g

Application Status (netman)Monitors whether the netman process is up and running.



Fatal N/A None


Severe N/A None

Warning N/A None


Normal N/A None


Always N/A None

Application Status (mailman)Monitors whether the mailman process is up and running.



Fatal N/A None


Severe N/A None

Warning N/A None

Application Status (netman)

34 Version 7.0



Normal N/A None


Always N/A None

Application Status (jobman)Monitors whether the jobman process is up and running. There aretwo versions of this event class monitor, one for UNIX and one forWindows NT. The uppercase JOBMAN event class monitor is forWindows NT and the lowercase jobman event class monitor is forUNIX.



Fatal N/A None

Critical Becomes unavailable Send event to the TivoliEnterprise Console.Change icon

Severe N/A None

Warning N/A None


Normal N/A None


Always N/A None

Application Status (mailman)


4.D

istribu

tedM

on

itorin

g

TWS SpaceFreeMonitors the amount of free disk space in the Workload Schedulerdirectory.

DescriptionThis monitor runs every 15 minutes. The following table lists thepre-configured actions for this monitoring source:


Fatal N/A None

Critical Less than 2 MB Send event to the TivoliEnterprise Console.Change icon.

Severe Less than 4 MB Send event. Changeicon

Warning Less than 6 MB Send event. Changeicon

Informational Less than 6 MB Send event. Changeicon

Normal N/A None


Always N/A None

TWS SpaceUsed (stdlist)Monitors the amount of disk blocks used by the Workload Schedulerstdlist directory.



Fatal N/A None

Critical N/A N/A

TWS SpaceFree

36 Version 7.0


Severe Greater than 50,000blocks

Send event to the TivoliEnterprise Console.Change icon

Warning Greater than 40,000blocks

Send event. Changeicon

Informational Less than 40,000blocks


Normal N/A N/A


Always N/A N/A

TWS SpaceUsed (schedlog)Monitors the amount of disk blocks used by the Workload Schedulerschedlog directory.



Fatal N/A None

Critical N/A None

Severe Greater than 50,000blocks

Send event to the TivoliEnterprise Console.Change icon.

Warning Greater than 40,000blocks

Send event. Changeicon.

Informational Less than 40,000blocks


Normal N/A None


Always N/A None

TWS SpaceUsed (stdlist)


4.D

istribu

tedM

on

itorin

g

Page-OutsMonitors the number of kilobytes per second paged out on amachine.



Fatal N/A None

Critical N/A None

Severe Greater than 100 KB Send event to the TivoliEnterprise Console.Change icon

Warning Greater than 50 KB Send event. Changeicon

Informational Less than 50 KB Send event. Changeicon

Normal N/A None


Always N/A None

Swap Space AvailableMonitors the amount of available swap space.



Fatal N/A None

Critical Less than 10 MB Send event to the TivoliEnterprise Console.Change icon

Page-Outs

38 Version 7.0


Severe Less than 20 MB Send event. Changeicon

Warning Less than 25 MB Send event. Changeicon

Informational Greater than 25 MB Send event. Chalngeicon

Normal N/A None


Always N/A None

Swap Space Available


4.D

istribu

tedM

on

itorin

g

Swap Space Available

40 Version 7.0

Enterprise Event Management

The TWS Plus Module provides a set of filters for identifying eventsand a set of predefined correlation rules to automate the task ofresponding to specific events.

An event is any significant change in the state of system resourcesor an application. In the case of TWS Plus Module, an event is achange in a monitored resource that affects TWS or activity from theTWS application. Examples of events are the starting and stoppingof a process or a host going down.

Event management provides a predefined or automated response tospecific events, so that potential problems are identified andresponded to before causing system down time. For example, if aprocess fails, the Tivoli Enterprise Console can automatically rerunthe process. The Tivoli Enterprise Console can also notify the systemadministrator of repeated process failures that may indicate a moresevere problem with an application or the network.

For some events, there is no automated response except to bedisplayed in the Tivoli Enterprise Console.

Setting Up the Tivoli Enterprise ConsoleThe following describes the configuration activity that occurs whensetting up the Tivoli Enterprise Console to be used with Tivoli Plusfor TWS. This activity takes place on the Tivoli Enterprise Consoleand TWS servers.

5


5.E

nterp

riseE

vent

Man

agem

ent

Tivoli Enterprise Console ServerThe Tivoli Enterprise Console is set up to:

¶ Recognize and accept TWS events.

¶ Respond to TWS events according to the predefined rules.

¶ Notify the system administrator of the events received and theaction taken.

Tivoli Plus for TWS performs most of the setup activityautomatically.

To set up the Tivoli Enterprise Console:

1. Select the Run job... option from the Setup EventServer forTWS icon’s pop-up menu.

2. Enter the necessary information in the Setup EventServer forTWS window. Online help is available to assist you.

This screen allows you to select the rule base that you want tocontain the TWS event classes and rules.

Figure 16. Setup EventServer for TWS window.

Setting Up the Tivoli Enterprise Console

42 Version 7.0

Note: To keep an uncorrupted copy of the default rule base, do notenter Default in the New Rule Base Name field. Copy theDefault rule base and modify the copy.

3. Create a new rule base (by entering a new name) or modify anexisting rule base (by entering an existing name).New Rule Base name:

Tivoli Plus

4. New rule bases are created by copying (cloning) and modifyingan existing one. If you are creating a new rule base, enter thename of the rule base to be copied in the following field:Rule Base to clone:

Default

5. If you are creating a new rule base, specify the path name to thedirectory on the Tivoli Enterprise Console server in which youwant to create the new rule base. Only use the following field ifyou are creating (not modifying) a rule base.Path for new Rule Base:

/usr/tec_rules/TivoliPlus

6. Use the following optional field to display TWS related eventson a particular system administrator’s event console. To makethis assignment, enter the name that appears under the desiredsystem administrator’s Event Console icon.Name of Event Console to configure (optional):

7. Press the Set and Close button when finished.

Configuring the Logfile AdapterThis section contains information on configuring the logfile adapterfor TWS Masters. There are two command icons used to do this:

¶ Configure Non-TME Logfile Adapter (for ManagedNodesonly)

¶ Configure TME Logfile Adapter (for endpoints only)

The logfile is used to relay event notification from TWS to TivoliPlus.

Setting Up the Tivoli Enterprise Console


5.E

nterp

riseE

vent

Man

agem

ent

The Configure Non-TME / TME Logfile Adaptercommand createsthe file BmEvents.conf on the TWS home directory. This filecontains a parameter FILE= used to specify the path and filenameof the logfile.

After the command has been executed, TWS must be stopped andrestarted on the TWS Master workstation.

For more information on the BmEvents.conf file refer to “BmEventsConfiguration File” on page 63.

Configuring the Non-TME Logfile AdapterTo configure the logfile adapter on a TWS system that is a managednode:

1. Install the Logfile Adapter manually.

2. Execute the Configure Non-TME Logfile Adapter command.

3. In the Configure Non-TME Logfile Adapterwindow, specifythe path to the logfile adapter installation directory.

4. Click the set and close the window the execute the command.This command performs the following actions

¶ Configures the Logfile Adapter to read events from the TWslog file

¶ Configures TWS to send events to the logfile

Configuring the TME Logfile AdapterTo configure the logfile adapter on a TWS server that is an endpoint,you must have ACP installed in your TMR:

1. Distribute the logfile adapter to the TWS endpoint using ACP.

2. Execute the Configure TME Logfile Adapter command.

3. This command performs the following:

¶ Configures the Logfile Adapter to read events from the TWSlogfile.

¶ Configures TWS to send events to the logfile.

Configuring the Logfile Adapter

44 Version 7.0

Events and RulesTivoli Plus for TWS configures the Tivoli Enterprise Console toreceive events from TWS and Tivoli Distributed Monitoring. TheTivoli Enterprise Console classifies the events and then matchesthem against the rule base to see if the event has a predefined rule(automated response).

TWS EventsThe following table describes the TWS Plus Module events andrules. The table is organized according to the message that the TivoliEnterprise Console sends to the system administrator for each TWSevent. The percent sign (%s) in the messages indicates a variable.The definition for each variable follows the message.

TWS Log File Event Messages

″TWS process %s has been reset on host %s″ (program_name, host_name)

Event Description: Event Class:Event Severity:

TWS daemon process reset. TWS_Process_Reset.HARMLESS.

″TWS process %s has been reset on host %s″ (program_name, host_name)


TWS NT daemon process reset. TWS_Process_Reset.HARMLESS.

″TWS process %s is gone on host %s″ (program_name, host_name)


TWS process gone. TWS_Process_Gone. Severity:CRITICAL.

″TWS process %s has abended on host %s″ (program_name, host_name)


TWS process abends. TWS_Process_Abend. Severity:CRITICAL.

″Job %s.%s failed, no recovery specified″ (schedule_name, job_name)

Event Description: Event Class:Event Severity: Automated Action:Correlation Activity:

Job abends, no recovery specified. TWS_Job_Abend.CRITICAL. Mail job stdlist to user TWS (UNIXonly). If this job had abended more than once withina 24 hour window, send a″TWS_Job_Repeated_Failure″ event.

″Job %s.%s failed, recovery job will be run then schedule %s will be stopped″(schedule_name, job_name, schedule_name)

Events and Rules


5.E

nterp

riseE

vent

Man

agem

ent



Job abends, recovery step is run recovery job thenstop schedule. TWS_Job_Abend. CRITICAL. Mailjob stdlist to user TWS (UNIX only). If this job hadabended more than one time within a 24 hourwindow, send a ″TWS_Job_Repeated_Failure″ event.

″Job %s.%s failed, this job will be rerun″ (schedule_name, job_name)


Job abends, recovery step is rerun job.TWS_Job_Abend. CRITICAL. Mail job stdlist to userTWS (UNIX only). If this job had abended more thanone time within a 24 hour window, send aTWS_Job_Repeated_Failure″ event.

″Job %s.%s failed, this job will be rerun after the recovery job″ (schedule_name,job_name)


Job abends, recovery step is rerun after recovery job.TWS_Job_Abend. CRITICAL. Mail job stdlist to userTWS (UNIX only). If this job had abended more thanone time within a 24 hour window, send a″TWS_Job_Repeated_Failure″ event.

″Job %s.%s failed, continuing with schedule %s″ (schedule_name, job_name,schedule_name)


Job abends, recovery step is continue with schedule.TWS_Job_Abend. CRITICAL. Mail job stdlist to userTWS (UNIX only). If this job had abended more thanone time within a 24 hour window, send a″TWS_Job_Repeated_Failure″ event.

″Job %s.%s failed, running recovery job then continuing with schedule %s″(schedule_name, job_name, schedule_name)


Job abends, recovery step is run recovery job andcontinue with schedule. TWS_Job_Abend.CRITICAL. Mail job stdlist to user TWS (UNIXonly). If this job had abended more than one timewithin a 24 hour window, send a″TWS_Job_Repeated_Failure″ event.

″Failure while rerunning failed job %s.%s″ (schedule_name, job_name)

Events and Rules

46 Version 7.0



Rerun of abended job abends. TWS_Job_Abend.CRITICAL. Mail job stdlist to user TWS (UNIXonly). If this job had abended more than one timewithin a 24 hour window, send a″TWS_Job_Repeated_Failure″ event.

″Failure while recovering job %s.%s″ (schedule_name, job_name)


Recovery job abends. TWS_Job_Abend. CRITICAL.Mail job stdlist to user TWS (UNIX only). If this jobhad abended more than one time within a 24 hourwindow, send a ″TWS_Job_Repeated_Failure″ event.

″Multiple failures of Job %s#%s in 24 hour period″ (schedule_name, job_name)


Same job fails more than once in 24 hours.TWS_Job_Repeated_Failure. CRITICAL.

″Job %s.%s did not start″ (schedule_name, job_name)


Job failed to start. TWS_Job_Failed. CRITICAL.

″Job %s.%s has started on CPU %s″ (schedule_name, job_name, cpu_name)

Event Description: Event Class:Event Severity: Correlation Activity:

Job started. TWS_Job_Launched. HARMLESS. Closeopen job prompt events related to this job.

″Job %s.%s has successfully completed on CPU %s″ (schedule_name, job_name,cpu_name)


Job completed successfully. TWS_Job_Done.HARMLESS. Close open job started events for thisjob and auto-acknowledge this event.

″Job %s.%s suspended on CPU %s″ (schedule_name, job_name, cpu_name)


Job suspended. TWS_Job_Suspended. WARNING.

(TWS Prompt Message)


Job recovery prompt issued.TWS_Job_Recovery_Prompt. WARNING.

″Schedule %s has failed″ (schedule_name)


Schedule abends. TWS_Schedule_Abend. CRITICAL.If event is not acknowledged within 15 minutes, sendmail to ″TWS″ user (UNIX only).

″Schedule %s is stuck″ (schedule_name)

Events and Rules


5.E

nterp

riseE

vent

Man

agem

ent



Schedule stuck. TWS_Schedule_Stuck. CRITICAL. Ifevent is not acknowledged within 15 minutes, sendmail to ″TWS″ user (UNIX only).

″Schedule %s has started″ (schedule_name)


Schedule started. TWS_Schedule_Started.HARMLESS. Close all related schedule stuck orschedule abend events related to this schedule.

″Schedule %s has completed″ (schedule_name)


Scheduled completed successfully.TWS_Schedule_Done. HARMLESS. Close all relatedschedule started events and auto-acknowledge thisevent.

(Global Prompt Message)


Global prompt issued. TWS_Global_Prompt.WARNING.

(Schedule Prompt’s Message)


Schedule prompt issued. TWS_Schedule_Prompt.WARNING.

(Job Recovery Prompt’s Message)


Job recovery prompt issued. TWS_Job_Prompt.WARNING.

″Comm link from %s to %s unlinked for unknown reason″ (hostname, to_cpu)


TWS link to cpu dropped for unknown reason.TWS_Link_Dropped. WARNING.

″Comm link from %s to %s unlinked via unlink command″ (hostname, to_cpu)


TWS link to cpu dropped by unlink command.TWS_Link_Dropped. HARMLESS.

″Comm link from %s to %s dropped due to error″ (hostname, to_cpu)


TWS link to cpu dropped due to error.TWS_Link_Dropped. CRITICAL.

″Comm link from %s to %s established″ (hostname, to_cpu)

Events and Rules

48 Version 7.0



TWS cpu link to cpu established.TWS_Link_Established. HARMLESS. Close relatedLink_Dropped or Link_Failed events andauto-acknowledge this event.

″Comm link from %s to %s down for unknown reason″ (hostname, to_cpu)


TWS link to cpu failed for unknown reason.TWS_Link_Failed. CRITICAL.

″Comm link from %s to %s down due to unlink″ (hostname, to_cpu)


TWS link to cpu failed due to unlink.TWS_Link_Failed. HARMLESS.

″Comm link from %s to %s down due to error″ (hostname, to_cpu)


TWS cpu link to cpu failed due to error.TWS_Link_Failed. CRITICAL.

″Comm link from %s to %s established″ (hostname, to_cpu)


TWS link to cpu established. TWS_Link_Established.HARMLESS. Close related Link_Dropped orLink_Failed events and auto-acknowledge this event.

″Active manager % for domain %″ (cpu_name, domain_name)


TWS domain manager switch has occurred.TWS_Domain_Manager_Switch HARMLESS.

Distributed Monitoring EventsThe following table describes the events and rules that TivoliDistributed Monitoring may use when monitoring TWS resources.The table is organized according to the Tivoli Distributed Monitoringmonitor that sends the event to the Tivoli Enterprise Console.

Since Tivoli Distributed Monitoring messages follow a standardformat, these messages are not reproduced in the table. Thefollowing is an example of a Tivoli Distributed Monitoring message:Distributed Monitoring TWS RemoteMonitors/Application status on host noonan Tues June 0208:00:00 1998

Status: >>> critical <<<

Events and Rules


5.E

nterp

riseE

vent

Man

agem

ent

Application status (jobman) Changes to down(Previous: up Current: down Effective: down)Daemon: jobman

Tivoli Distributed Monitoring Event Messages

batchman, mailman, netman, jobman, and Daemon Status


batchman, mailman, netman, or jobman becomeunavailable. universal_application. CRITICAL.

batchman, mailman, netman, jobman, and Daemon Status

Event Description: Event Class:Event Severity: CorrelationActivity:

batchman, mailman, netman, or jobman becomeunavailable. universal_application. HARMLESS. Closerelated universal_application down events andauto-acknowledge this event.

Host Status


TWS master host becomes unavailable. universal_host.CRITICAL.

Host Status


TWS master host becomes available. universa_host.CRITICAL. Close related universal_host down events andauto-acknowledge this event.

TWS stdlist Directory Size

Event Description: Event Class:Event Severity: DistributedMonitoring Activity:

TWS stdlist directory gets larger than 50000 blocks.TWS_DiskUsed. CRITICAL. Mail message to ″TWS″user.



TWS stdlist directory gets larger than 40000 blocks.TWS_DiskUsed. WARNING.



TWS stdlist directory gets smaller than 40000 blocks.TWS_DiskUsed. HARMLESS. Close all open DistributedMonitoring events related to size of stdlist directory onthis host.

TWS schedlog Directory Size

Event Description: Event Class:Event Severity: DistributedMonitoring Activity:

TWS schedlog directory gets larger than 50000 blocks.TWS_DiskUsed. CRITICAL. Mail message to ″TWS″user.


Events and Rules

50 Version 7.0



TWS schedlog directory gets larger than 40000 blocks.TWS_DiskUsed. WARNING.



TWS schedlog directory gets smaller than 40000 blocks.TWS_DiskUsed. HARMLESS. Close all open DistributedMonitoring events related to size of schedlog directory onthis host.

Available Swap Space


Swap space decreases below 10 mb on a machine.Universal_swapavail. CRITICAL.



Swap space decreases below 20 mb on a machine.Universal_swapavail. MINOR.



Swap space decreases below 25 mb on a machine.Universal_swapavail. WARNING.



Swap space increases above 25 mb on a machine.Universal_swapavail. HARMLESS. Close all openDistributed Monitoring events related to swap availableon this host.

TWS Directory Free Space


Disk space available in the TWS directory decreasesbelow 2 mb on a machine. Universal_diskavail.CRITICAL.



Disk space available in the TWS directory decreasesbelow 4 mb on a machine. Universal_diskavail. MINOR.



Disk space available in the TWS directory decreasesbelow 6 mb on a machine. Universal_diskavail.WARNING.


Events and Rules


5.E

nterp

riseE

vent

Man

agem

ent



Disk space available in the TWS directory increasesabove 6 mb on a machine. Universal_diskavail.HARMLESS. Close all open Distributed Monitoringevents related to swap available on this host.

Monitor: Kilobytes Paged Out


Kilobytes paged out per second increases above 100 on amachine. Universal_pageouts. CRITICAL.



Kilobytes paged out per second increases above 50 on amachine. Universal_pageouts. MINOR.



Event Description: second decreases below 50 on amachine. Universal_pageouts. HARMLESS. Close allopen Distributed Monitoring events related to pageouts onthis host.

Events and Rules

52 Version 7.0

TWS Plus Tasks

The TWS Plus Module provides a number of task icons that enableyou to execute TWS commands on multiple machines and operatingsystems, configure features of the TWS Plus Module, or distributesoftware to workstations in the TMR. These tasks are ready to beexecuted as soon as you have installed the TWS Plus Module.Simply double-click on the task icon to execute the TWS command.You can also modify the default execution characteristics of aparticular task, such as where the output of a task is displayed andon which machines the task will run. You may also specify whethera task runs serially on each workstation, in parallel on all machines,or staged in groups of machines.

Note: The term task or job in TME refers to the execution of iconson the TME desktop. In TWS terminology, these iconsrepresent commands that can be run on individual or multipleworkstations in a TWS network.

Starting the Job Scheduling ConsoleThere are two ways to start the Job Scheduling Console in the TWSPlus module:

¶ Select the workstation icon (for example, TWS@london) andeither double-click the icon or right-click the icon and select theJSConsole command from the pop up window. The workstationicon is only displayed if the TWS Plus Module was installed ona Managed Node with the TWS Engine.

6


6.T

WS

Plu

sTasks

¶ Select the JSConsole command icon from the task list. Beforethis command can be used make sure that you run the Set TWSInstall Options task and specify the Job Scheduling ConsoleInstallation directory.

TWS Network CommandsThis section provides a list of the network task icons in the TWSPlus Module and the specific TWS commands that these iconsexecute.

Icon Name TWS Command Description

Start TWS Servers start Starts the TWSproduction processes.

TWS CPU link link Opens TWS links forinter-workstationcommunications.

TWS CPU Unlink unlink Disablesinter-workstationcommunication.

TWS Start CPU link start Starts the TWSproduction processes ona workstation.

TWS Stop CPU unlink stop Stops the TWSproduction processes ona workstation.

Shutdown TWS Servers unlink @ stopshutdown

Unconditionally stopsthe TWS productionprocesses.

TWS Limit Job Stream limit sched Changes the job limitfor a schedule.

Starting the Job Scheduling Console

54 Version 7.0

TWS Reporting CommandsThis section provides a list of the reporting task icons in the TWSPlus Module and the specific TWS report commands that these iconsexecute.

Icon Name TWS Command Description

TWS Cross ReferenceReport

xref Prints a TWS Report12-Cross Referencereport.

TWS Job DetailsListing

rep1 Prints the TWS JobDetails Listing report

TWS Prompt MessagesListing

rep2 Prints the TWS PromptMessages Listingreport.

TWS User CalendarListing

rep3 Prints the TWS UserCalendar Listing report.

TWS User ParametersListing

rep4a Prints the TWS UserParameters Listingreport.

TWS Resource Listing rep4b Prints the TWSResource Listing report.

TWS Job HistoryListing

rep7 Prints the TWS Report07-Job History Listingreport.

TWS Job Histogram rep8 Prints the TWS Report08-Job Histogramreport.

TWS Preview PlanReport

rep11 Prints the TWS Report11-Planned ProductionSchedule report.

TWS Plan Report reptr Prints the TWS reports:09A through 10B.

TWS Reporting Commands


6.T

WS

Plu

sTasks

TWS Plus Module Configuration TasksThis section provides a list of the default configuration tasksavailable with the TWS Plus Module. Many of these tasks are usedto configure a specific feature of the TWS Plus module.

Icon Name Description

Indicators for TWS Monitors Display the status of the resources onTWS workstations. The monitorsdisplay the most critical value of theitems they are monitoring. For moreinformation refer to “DistributedMonitoring” on page 29.

TWS Client List Displays a list of TWS workstations(usually FTAs) that you are monitoringwith the TWS Monitors.

TWS Server List Displays a list of TWS Masters. Allreports and task icons are run againstthe subscribers to this list.

About TWS Displays information about theinstallation of TWS such as the versionlevel and the installation directory.

Configure Non-TME LogfileAdaptor

Configures 3.2 Framework logfileadapters. This is part of theconfiguration process for eventmanagement. For more informationrefer to “Configuring the LogfileAdapter” on page 43.

Configure TME Logfile Adaptor Configures 3.6 Framework logfileadapters. This is part of theconfiguration process for eventmanagement. For more informationrefer to “Configuring the LogfileAdapter” on page 43.

Create TWS Subscriber List Creates a subscription list similar to theTWS Master List.

TWS Plus Module Configuration Tasks

56 Version 7.0


Get TWS Installation Options Displays installation options such as:TWS user name, TWS home directory,and the Job Scheduling Consoleinstallation directory.

Install NT TWS Clients Used to distribute TWS Windows NTfile packages to workstations on theclient list.

Install UNIX TWS Clients Used to distribute TWS UNIX filepackages to workstations on the clientlist. For more information refer to“Software Distribution” on page 17.

JSConsole Enables you to open the JobScheduling Console from the TivoliFramework Desktop. For moreinformation refer to “SoftwareDistribution” on page 17.

Set TWS Install Options Specify the installation options: TWSuser name, TWS home directory, andthe Job Scheduling Console installationdirectory.

Setup Event Server for TWS Configures the TEC Server torecognize the TWS events.

Setup TWS Master Distribution Configures a file package to distributethe even format files for TWS. Thesefiles must be distributed to the nodewhere the logfile adapter is runningbefore the configure logfile adaptercommand is executed.

Setup TWS UNIX Client Install Enables you to configure an TWSinstallation package for UNIX clients.This job requires Tivoli SoftwareDistribution be installed. For moreinformation refer to “SoftwareDistribution” on page 17.



6.T

WS

Plu

sTasks


Setup TWS Windows NT ClientInstall

Enables you to configure an TWSinstallation package for Windows NTclients. This job requires TivoliSoftware Distribution be installed. Formore information refer to “SoftwareDistribution” on page 17.

TWS Central Monitors Displays a universal host monitor whenthe TWS master is on a managed nodeand the TWS Plus module has beeninstalled.

TWS Remote Monitors Displays the monitors for TWS processstatus, and TWS directory usage, pageouts, and swap space.

TWS Master ConfigurationDistribution

Distributes the file package created bySetup TWS Master Distribution.

Running a TWS JobAll TWS Plus module jobs can be run immediately after installation.You can run a task library job from the desktop only.

To run a TWS Job with the default execution characteristicsDouble-click on the icon or select Run job... from the icon’s pop-upmenu.

If TWS Plus module requires further information to execute the job,a pop-up dialog appears prompting you for the information. Onlinehelp is available to assist you in completing these dialogs. The joboutput is displayed on the desktop or sent to a file as specified.

Modifying a TWS JobYou can modify the execution characteristics of a Job for each timethe job is run or for one particular job only.

Modifying a Job for Each RunUse the following steps to modify a Job for each time it is run:


58 Version 7.0

1. Select the Modify job... option from the task’s pop-up menu.

2. Make any changes in the Edit Job window. Online help isavailable to assist you.

Note: Be sure to specify on which managed nodes and end pointsthe job will run.

3. Click on the Change & Close button when finished.

Figure 17. Edit Job window.

Modifying a TWS Job


6.T

WS

Plu

sTasks

Modifying a Job for a Single RunUse the following steps to modify a job for only a single executionof the job. The next time you run the same job, it will return to thedefault execution characteristics.

1. Select the Run on selected subscribers... option from the task’spop-up menu.

2. Make the necessary changes in the Execute Task window.Online help is available to assist you.

3. Click on the Execute button when finished.

Figure 18. Execute Task window.

Modifying a TWS Job

60 Version 7.0

Event Configuration Reference

The TWS Plus Module events are listed in the following table. Theevents (101-252) indicate the status of TWS job scheduling activity.

A


A.

Even

tC

on

figu

ration

Referen

ce

Event # Message Type Positional Variables

101 102 103104 105*204

Job abend Jobfailed Job launchedJob done Jobsuspended, untiltime expired Jobrecovery promptissued

1 Event number. 2 workstation name of the schedule. 3Schedule name. 4 Job name. For jobs submitted with ator batch, if the name supplied by the user is not unique,this is the TWS-generated name, and the name suppliedby the user appears as variable 8 below. 5 workstationname on which the job runs. 7 Job state, indicated byan integer: 1 (ready), 2 (hold), 3 (exec), 5 (abend), 6(succ), 7 (cancl), 8 (done), 13 (fail), 16 (intro), 23(abenp), 24 (succp), 25 (pend). 8 Job’s submitted (real)name. For jobs submitted with at or batch, this is thename supplied by the user if not unique. The uniquename generated by TWS appears as variable 4 above. 9User name under which the job runs. 10 Name of thejob’s script file, or the command it executes. Whitespace is replaced by the octal equivalent; for example, aspace appears as \040. 11 The rate at which an ″every″job runs, expressed as hhmm. If every was not specifiedfor the job, this is -32768. 12 Job recovery step,indicated by an integer: 1 (stop), 2 (stop after recoveryjob), 3 (rerun), 4 (rerunafter recovery job), 5 (continue),6 (continue after recovery job), 10 (this is the rerun ofthe job), 20 (this is the run of the recovery job). 13 Anevent timestamp. This is the local time on theworkstation where the job event occurred. It isexpressed as: yyyymmddhhmmss00 (that is, year,month, day, hour, minute, second, hundredths alwayszeroes). 14 The prompt number, or zero if there is noprompt. 15 The prompt text, or TWS error message.

151 152 153154 155*

Schedule abendSchedule stuckSchedule startedSchedule doneSchedulesuspended, untiltime expired

1 Event number. 2 workstation name of the schedule. 3Schedule name. 4 Schedule state, indicated by aninteger: 1 (ready), 2 (hold), 3 (exec), 4 (stuck), 5(abend), 6 (succ),7 (cancl). 5 TWS error message, ifany.

201 Global promptissued

1 Event number. 2 Prompt name. 3 Prompt number. 4Prompt text.

202 Schedule promptissued

1 Event number. 2 workstation name of the schedule. 3Schedule name. 4 Prompt number. 5 Prompt text.


62 Version 7.0

Event # Message Type Positional Variables

203 Job prompt issued 1 Event number. 2 workstation name of the schedule. 3Schedule name. 4 Job name. 5 workstation name of thejob. 6 Prompt number. 7 Prompt text.

251 252 Link dropped Linkfailed

1 Event number. 2 The ″to″ workstation name. 3 Linkstate, indicated by an integer: 1 (unknown), 2 (downdue to an unlink), 3 (down due to an error), 4 (up). 4TWS error message.

301 Domain Managerswitch

1 Event number. 2 The workstation name for the downmanager. 3 The domain name. 4 Event time stamp.

TWS Plus Module Configuration Files

BmEvents Configuration FileThe BmEvents configuration file is namedTWShome/BmEvents.conf. Use it to configure the TWS productionprocesses on each workstation that has an agent installed. Itscontents are described below.

#commentA comment line.

OPTIONS=MASTER|OFFIf set to MASTER, this workstation will report all jobscheduling events for all workstations in the TWS network.If set to OFF, no job scheduling events are reported by thisworkstation. If omitted, it defaults to MASTER on themaster workstation, and OFF on other workstations.

This variable is required only if the master workstation willnot be used to report job scheduling events for the network.For example, if the master workstation is not a managednode (muagent is not installed), you should set this variableto MASTER on a backup master workstation that has anagent installed.



A.

Even

tC

on

figu

ration

Referen

ce

EVENT=n[n...]The list of events to be reported. Event numbers must beseparated by at least one space. If omitted, the eventsreported by default are:51 101 102 105 151 152 155 201 202 203 204 251 252 301

Event 51 causes mailman and batchman to report the factthat they were restarted. Events 1, 52, and 53 are not validin this file.

If the EVENT parameter is included, it completely overridesthe defaults. To remove only event 102 from the list, forexample, you must enter the following:EVENT=51 101 105 151 152 155 201 202 203 204 251 252 301

PIPE=filenameIf set, job scheduling events are written to a FIFO file.

FILE=filenameIf set, job scheduling events are written to an ascii logfile.

BmEvents Configuration File DefaultsA BmEvents configuration file is included with TWS. It containsseveral comment lines, and the following parameter setting:FILE=/user/TWS/event.log

This causes events to be reported as follows:

¶ If installed on the master workstation, it will report all jobscheduling events (101-252) for all workstations in the network.If installed on any other workstation, no job scheduling eventswill be reported. The process restart event (51) is reportedregardless of the workstation type.

¶ The following events are reported:51 101 102 105 151 152 155 201 202 203 204 251 252 301

On the TWS Master workstationOn the TWS master workstation in the configuration fileTWShome/BmEvents.conf, the following statement:FILE=/TWShome/event.log


64 Version 7.0

instructs TWS’s production processes, mailman and batchman, towrite their messages to a log file named TWShome/event.log. Theevent.log file is monitored using the TME Logfile Adapter. Theevent.log file is created when batchman comes up ( a conman stopand start brings up batchman).



A.

Even

tC

on

figu

ration

Referen

ce

66 Version 7.0

Glossary

The terms in this glossary explain some of the concepts used by theTivoli Plus modules. Many of these terms are used by other Tivoliproducts and you may find a fuller explanation by referring to theproduct-specific documentation. Certain terms, although used byother Tivoli products, have a particular meaning when applied to theTivoli Plus modules.

A

Automated responseA predefined response to particular events that is automatically executed by theTivoli Enterprise Console. For example, if the Tivoli Enterprise Console detects thata process has terminated early, it can automatically restart the process without theintervention of the system administrator.

C

Correlation activityThe activity of using the Tivoli Enterprise Console’s rules to correlate separateevents to a common cause. For example, the Tivoli Enterprise Console may receiveseveral ″NFS server not responding″ events from several applications, as well as a″host down″ event for the NFS server. The Tivoli Enterprise Console can thencorrelate the various ″NFS server not responding″ events to their common cause, thefact that the NFS server has gone down.

E

EventAn event is a significant change in the state of a system resource or application. Forexample, the normal starting and stopping of a process are events as well as theabnormal termination of a process or having a server go down. Events are sent byTivoli Sentry (which monitors system resources) to the Tivoli Enterprise Consoleregarding those events that effect the availability of the production controlapplication. The production control application also sends events to the TivoliEnterprise Console regarding its activity.

Event classThe different types of events that the event server is configured to receive aredefined as event classes. Each class defines the possible attributes, or slots, for thatclass. An example of an event class is a Machine_Down class, representing amachine going offline.


Glo

ssary

Event groupAn event group is a configured logical area of responsibility. It notifies users that anevent matching a specified set of criteria has occurred. Event groups are configuredon the event server to create a single alarm indicator that represents many differentevents that are meaningfully related. Each event group has its own icon on the eventconsole. An example of an event console is a ″Network″ event group configured toreceive all events relating to the enterprise network.

Event managementThe monitoring and automatic response by the Tivoli Enterprise Console to thoseevents that pertain to the availability and activity of the production controlapplication. For example, if the event is the abnormal termination of a process,event management would be the detection of this condition and an automatic,predefined response, such as running the process again. For some events, the onlyresponse required is to display the event in the Tivoli Enterprise Console. TivoliPlus modules use the Tivoli Enterprise Console to provide event management.

Execution targetA machine on which a job or other activity is carried out when the job or activity isexecuted. For example, if an application is being installed on a particular server,then that server is the target of the installation activity.

J

JobA job is a task pre-configured to run on selected targets and generate output in aspecific manner. See Task.

M

Managed nodeA machine that is being managed by the Tivoli Management Environment and anyof the TME related products.

Monitored resourceA monitored resource can be virtually any enterprise entity, such as a machine, afile system, a process, or a router. Tivoli Sentry uses various types of monitors toascertain the status of these resources.

P

Production controlThe management of a particular aspect of network or system resources. An exampleof a production control application is a job scheduler. Tivoli Plus modules integrate

68 Version 7.0

the Tivoli Management Environment with other applications in the following areasof production control: job scheduling backup and restore, security, help desk, andoutput management.

Profile managerProfile managers have a more limited function in Tivoli Plus modules than they doin other Tivoli products. In a Tivoli Plus module, a profile manager is a subscriptionlist. See Subscription list.

R

RuleRules describe actions that should be performed when a particular event is receivedby the event server. Matching events to predefined responses allows for theautomation of certain aspects of network management. For example, if the event isthe early termination of a process and the predefined response is to restart theprocess, then the process is automatically restarted without the intervention of asystem administrator. Rules are also used to correlate events to other events.

Rule baseThe collection of rules that the Tivoli Enterprise Console uses to provide eventmanagement.

S

Sentry activityActivity that Tivoli Sentry takes in response to changes in its monitored resources.An example of a Sentry activity is the automatic truncation of a monitored log filewhen it surpasses a specified size.

Subscription listA list that identifies on which machines a particular task or other activity will beexecuted. A subscription list contains the names of managed nodes (machines) orprofile managers. In Tivoli Plus modules, a profile manager functions as asubscription list. Including a profile manager on a subscription list (in effect, a ″listwithin a list) is a way of subscribing several machines at a time without having toadd each one individually.

T

TaskA task is a Tivoli Management Environment Resource that encapsulates repetitive orscripted operations. Tivoli Plus modules come with a default set of tasks to makemanagement of the associated application simpler. These tasks are typicallyconfigured as jobs, with default targets and characteristics, but may also be run with


Glo

ssary

customized execution characteristics. An example is a ″Reset Print Queue″ taskwhich prompts for the name of a print queue to reset.

70 Version 7.0

Index

AACF 44adding TME 10 products after installation 13

Bbatchman daemon 33batchman status 33BMEVENTS.CONF file, defaults 64BMEVENTS.CONF file, TWS Master 64

Cconfiguring file packages 19configuring the logfile adapter 43

Ddistributed monitoring 29

Eevent

Maestro 45Sentry 49

event management 41EVENT parameter 64events 45, 61

Ffeatures 12file packages, configuring 19, 23FILE parameter 64

Hhost status 32

Iicons 11installation requirements 1

hardware 2software 2

installation upgrades 13installing

requirements for 1installing the logfile adapter 43installing Tivoli Plus for Maestro 5installing Tivoli Plus for Maestro, command

line 10installing TWS 17, 25, 27

JJob Scheduling Console, starting 15jobman daemon 35jobs, TWS Plus module 53


Ind

ex

Kkilobytes paged out 38

Llaunching TWS 15logfile adapter 43

MMaestro home directory 36MAGENT.P file 64mailman daemon 34managing events 41modifying a TWS Plus job 58modules

starting 13viewing 13

monitored resources 31jobman daemon 35kilobytes paged out 38Maestro directory 36mailman daemon 34schedlog directory 37stdlist directory 36swap space 38

monitoring resources 29monitors, using 29

Nnetman daemon 34

OOPTIONS parameter 63

PPIPE parameter 64procedure

configuring file packages 23installing Tivoli Plus for Maestro 5setting up the Tivoli Enterprise Console 41starting a module 13

procedure, starting TWS 15profile manager 12

Rrequirements

hardware 2installation 1software 2

resource monitoring 29rule 45running a TWS Plus job 58running tasks 58

Sschedlog directory 37setting up

Tivoli Enterprise Console 41setting up a TWS install 17setting up file packages 17software distribution, TWS engine 17software requirements 2software upgrades 13starting

module 13starting TWS 15stdlist directory 36subscription list 12swap space 38

72 Version 7.0

Ttask library 53Tivoli Distributed Monitoring 29Tivoli Enterprise Console

setup 41Tivoli Plus for Maestro

icons 11installation 5unique features 12

Tivoli Plus modulesoverview 11viewing 13

Tivoli Software Distribution setup 19traps 61TWS Plus job, modifying 58TWS Plus job, running 58TWS Plus Module

events 62

Uusing monitors 29

Vviewing, Tivoli Plus modules 13viewing monitored resources 31


Ind

ex

74 Version 7.0

Printed in the United States of Americaon recycled paper containing 10%recovered post-consumer fiber.

GC31-8401-02