Documente Academic
Documente Profesional
Documente Cultură
Version 1.0
August 23, 1996
Tivoli/Plus for AutoSys Users Guide (August 23, 1996) Copyright Notice
Copyright 19911996 by Tivoli Systems Inc., including this documentation and all software. All rights reserved. May only be used pursuant to a Tivoli Systems Incorporated Software License Agreement or Addendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval 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 Inc. This document was prepared by Tivoli Systems Inc., and was printed in the United States of America. All software has been developed at private expense and is commercially available at published prices.
Associated Copyrights
Portions copyright 1989 by the Eric C. Cooper, Carnegie Mellon University. All rights reserved. Portions copyright 1990, 1991 by the University of Utah and the Center for Software Science (CSS). All rights reserved. Portions copyright 1989 by Digital Equipment Corporation. All rights reserved. Portions copyright 1989, 1990, 1991 by Massachusetts Institute of Technology. All rights reserved. Portions copyright 1986 by University of Toronto. All rights reserved. Portions copyright 1989, 1990, 1991 by Larry Wall. All rights reserved. Portions copyright 1990 by Alfalfa Software Incorporated.All rights reserved. Portions copyright 1992, 1993 by Free Software Foundation, Inc. All rights reserved. Portions copyright 1982, 1986, 1991 by Regents of the University of California. All rights reserved. Portions copyright 1988, 1989, 1991 by Jef Poskanzer. All rights reserved. Portions copyright 1991, 1992 by RSA Data Security, Inc. All rights reserved. Portions copyright 1982, 1988, 1989 by Walter Tichy. All rights reserved. Portions copyright 1990, 1991 by Paul Eggert. All rights reserved. Portions copyright 1990, 1992 by Hewlett-Packard Company. All rights reserved. Portions copyright 1989, 1993 by Jim Frost. All rights reserved. Portions copyright 1990 by GROUPE BULL. All rights reserved. Portions copyright 1991-1994 by JSB Computer Systems Ltd. All rights reserved. Portions copyright 1995 by Intel Corporation. All rights reserved. Portions copyright by DataFocus Incorporated. All rights reserved. Portions copyright 1992-1994 by Michael A Cooper. All rights reserved.
Trademarks
Tivoli Management Environment, Tivoli Management Platform, Tivoli Management Framework, Tivoli Application Service, Tivoli/ADE, Tivoli/Admin, Tivoli/AEF, Tivoli/Courier, Tivoli/EIF, Tivoli/Enterprise Console, Tivoli/FSM, Tivoli/Inventory, Tivoli/net.Commander, Tivoli/Plus, Tivoli/Print, Tivoli/Sentry, Tivoli/UserLink, Tivoli/Workload, and TME are trademarks of Tivoli Systems Inc.
Product and company names mentioned in this document are trademarks or registered trademarks of their respective manufacturers. Patent pending.
Monitored Resources .......................................................................................... 3-7 Host Status ................................................................................................. 3-8 Event Processor Log File Size ................................................................... 3-9
ii
Version 1.0
Preface
Preface
The Tivoli/Plus for AutoSys Users Guide describes specic features and procedures for using the Tivoli/PlusTM for AutoSys module. This module was jointly developed by Tivoli Systems Inc. and Platinum Technology Inc. and provides an integration of the AutoSysTM workload management application with the Tivoli Management EnvironmentTM (TME). Through this integration, the Tivoli/Plus for AutoSys module delivers the system management capabilities of TME for specic use with AutoSys. Using Tivoli/Plus for AutoSys, the AutoSys application can be managed across a multi-platform network that includes PCs and UNIX systems. Tivoli/Plus provides different modules for integrating different production control applications with the Tivoli Management Environment. Since all Tivoli/Plus modules have a common interface, a system administrator can implement the system management capabilities of the TME with various production control applications while enjoying the simplicity of a common interface. The addition of Tivoli/CourierTM, Tivoli/SentryTM, and the Tivoli/Enterprise ConsoleTM provides additional management capabilities in the areas of client installation, resource monitoring, and event correlation.
Note:
All references to Sentry in this guide refer to the Tivoli/Sentry product or its components.
iii
Preface
Chapter 1, Getting Started with Tivoli/Plus for AutoSys Contains the installation requirements and procedures for installing Tivoli/Plus for AutoSys. This chapter also contains information about Tivoli/Plus icons, features unique to Tivoli/Plus, and launching the AutoSys application. Chapter 2, Software Distribution for AutoSys Describes how to set up Tivoli/Courier to be used with Tivoli/Plus for AutoSys for distributing and installing the AutoSys application across a network. Chapter 3, Resource Monitoring Describes how Tivoli/Sentry may be used with Tivoli/Plus for AutoSys to monitor AutoSys resources in order to detect and prevent system problems. Chapter 4, Enterprise Event Management Describes how to set up the Tivoli/Enterprise Console to be used with Tivoli/Plus for AutoSys to provide event management. This chapter also contains a description of the events and rules specic to Tivoli/Plus for AutoSys. Chapter 5, Tasks and Jobs for AutoSys Describes how to customize and run AutoSys jobs and reports with Tivoli/Plus for AutoSys.
iv
Version 1.0
Preface
Typeface Conventions
This guide uses several typeface conventions for special terms and actions. These conventions have the following meaning: Bold Commands, keywords, le names, or other information that you must use literally appear in bold. Names of windows, dialogs, and other controls also appear in bold. Variables and values that you must provide appear in italics. New terms appear in bold italic the rst time they are used. Code examples appear in a monospace font.
This guide may include icons in the left margin. These icons provide context for the discussion in the text or for performing a step within a procedure. For example, if you start a procedure by double-clicking on a task icon, that icon appears in the left margin next to the rst step. If the fourth step of the procedure instructs you to open another icon, that icon appears in the left margin next to the fourth step.
Preface
TME Problem Report Name: E-mail: Company: Tivoli Product: Operating System Rel: Previous Call Tracking #: Problem On: Tivoli Server Priority: 1. Critical 3. Minor Short Description (10 - 12 words): Tivoli Client 2. Major 4. No Impact Phone #: Fax #: TMR #: Version: System Type:
Attempted Solutions:
vi
Version 1.0
1
Getting Started with Tivoli/Plus for AutoSys
1
The Tivoli/Plus for AutoSys module provides an integration of the Tivoli Management Environment with the AutoSys Workload Management Applications. This integration allows centralized distribution and management of the AutoSys application across a multi-platform network. This module provides the following features for managing the AutoSys application:
s s s s s
Icons for launching the AutoSys application Subscription lists for clients and servers Tivoli/Courier le packages Tivoli/Sentry monitors Tivoli/Enterprise Console events and rule sets customized for AutoSys AutoSys-specic tasks and jobs The Tivoli/Courier, Tivoli/Sentry, and Tivoli/Enterprise Console applications must be installed and congured before their corresponding Tivoli/Plus feature is operational.
Note:
11
Installation Requirements
Installation Requirements
Before attempting to install Tivoli/Plus for AutoSys into the Tivoli Management Environment, make certain you review the requirements in this section. The following table provides the context and authorization role required to install Tivoli/Plus for AutoSys. Activity
Installing Tivoli/Plus for AutoSys
Context
TME
Required Role
install_product
The Tivoli/Plus for AutoSys module must be installed on the Tivoli server. In order to have full functionality, the Tivoli/Plus for AutoSys module must also be installed on the following machines. These machines must be Tivoli managed nodes.
s s
License Key
You do not need a license key to use the Tivoli/Plus for AutoSys module if your module is installed on Tivoli Management Platform 3.0. However, you must obtain a license key to use the Tivoli/Plus for AutoSys module if your module is installed on TMP 2.5. You must complete and return the license request form that came with this software. Tivoli Customer Support will then provide you with a license key for your module.
Software Requirements
The AutoSys Workload Management Applications should be installed before the Tivoli/Plus for AutoSys module is installed. Note: For information about current TME platform requirements, refer to the release notes.
Tivoli/Plus for AutoSys has features that use Tivoli/Courier, Tivoli/Sentry, and the Tivoli/Enterprise Console. If these applications
12
Version 1.0
Installation Requirements Getting Started with Tivoli/Plus for AutoSys are not installed, then the specic feature requiring these applications will not work. However, the Tivoli/Plus for AutoSys installation allows you to incrementally re-install those features if you buy the missing products at a later date.
Hardware Requirements
The following table provides the client and server disk space requirements for Tivoli/Plus for AutoSys. This space is in addition to the space requirements for the management platform, the Tivoli application, and the AutoSys Workload Management Applications. Tivoli/Plus for AutoSys is installed on the TME server, the Tivoli/Enterprise Console server (if you have the Tivoli/Enterprise Console), and the AutoSys master machines. The space requirements are the same for all of these machines. The Tivoli/Plus for AutoSys module uses platform-independent shell and Perl scripts, which is why the module's requirements do not differ from platform to platform.
Platform
AIX HP-UX OSF-1 Solaris SunOS SVR4
Libraries
0 MB 0 MB 0 MB 0 MB 0 MB 0 MB
Binaries
500 KB 500 KB 500 KB 500 KB 500 KB 500 KB
Database
0 0 0 0 0 0
Man Pages
0 MB 0 MB 0 MB 0 MB 0 MB 0 MB
Message Catalogs
50 KB 50 KB 50 KB 50 KB 50 KB 50 KB
13
14
Version 1.0
Installing from the Desktop Getting Started with Tivoli/Plus for AutoSys to display the Install Product dialog.
If the Tivoli/Plus for AutoSys module is listed in the Select Product to Install scrolling list, skip to step 3. If it is not listed, proceed to step 2.
15
Installing from the Desktop 2. Press the Select Media... button to display the File Browser dialog.
The File Browser dialog enables you to identify or specify the path to the installation media. If you already know the path to the CD-ROM image a. Enter the full path in the Path Name eld. b. Press the Set Path button to change to the specied directory. c. Press the Set Media & Close button to save the new media path and return to the Install Product dialog. The dialog now contains a list of products that are available for installation.
16
Version 1.0
Installing from the Desktop Getting Started with Tivoli/Plus for AutoSys If you do not know the exact path to the CD-ROM image a. From the Hosts scrolling list, choose the host on which the install media is mounted. Choosing a host updates the Directories scrolling list to show the directories of the host you chose. b. From the Directories scrolling list, choose the directory containing the install media. c. Press the Set Media & Close button to save the new media path and return to the Install Product dialog. The dialog now contains a list of products that are available for installation.
17
Installing from the Desktop 3. Select the Tivoli/Plus for AutoSys module from the Select Product to Install list.
After you have selected the Tivoli/Plus module from the Select Product to Install scrolling list, the Install Options dialog is displayed.
18
Version 1.0
Installing from the Desktop Getting Started with Tivoli/Plus for AutoSys 4. Enter the information regarding your AutoSys installation environment in the Install Options dialog. The following describes each of the elds on this dialog: AutoSys Directory. Enter the path to the AutoSys base directory. AutoSys User Directory. Enter the path to the AutoSys user directory. AutoSys Instance Name. Enter the AutoSys instance name. Database Type (sybase/oracle). Enter the database type (Sybase or Oracle). Enter valid Exec User Name. Enter the valid name for the exec user. Event Processor Machine Name. Enter the machine name for the event processor. Note: When you specify the Event Processor Machine Name eld, the Main Machine monitor is added automatically to the Central AutoSys Server Monitors prole during installation.
Shadow Event Processor Machine Name. Enter the machine name for the shadow event processor. Note: When you specify the Shadow Event Processor Machine Name eld, the Shadow Machine monitor is added automatically to the Central AutoSys Server Monitors prole during installation.
TNS Alias. Enter the name of the TNS alias. Is Database Bundled(YES/NO). Enter YES if the database is bundled. Enter NO if the database is not bundled. Sybase or Oracle Distribution Location. Enter the path to the Sybase or Oracle directory or interface le. Sybase Admin Password. Enter the Sybase administrators password. This eld only applies to Sybase database users.
19
Installing from the Desktop Sybase DataServer. Enter the name of the Sybase dataserver. This eld only applies to Sybase database users.
5.
Press the Set and then the Close button on the Install Options dialog when you are ready to continue.
110
Version 1.0
Installing from the Desktop Getting Started with Tivoli/Plus for AutoSys Note: The information you specify on the Install Options dialog can be modied using the Congure AutoSys Environment option on the AutoSys _setup task icons pop-up menu. For more information on using the Tivoli/Plus for AutoSys tasks, refer to page 5-1.
6.
Specify the clients on which the module will be installed, by using the left and right arrow buttons on the Install Product dialog to move the machine names between the Clients to Install On scrolling list and the Available Clients scrolling list. By default, all machines in the current Tivoli Managed Region (TMR) are listed in the Clients to Install On scrolling list. To move a machine name to the Available Clients list, choose one or more clients from the Clients to Install On scrolling list and press the right arrow button. The chosen clients are moved from the Clients to Install On scrolling list to the Available Clients scrolling list.
7. 8.
Enter your license key for the Tivoli/Plus for AutoSys module in the License Key eld. Press the Install & Close button to install the module and close the Install Product dialog. - OR Press the Install button to install the module and keep the Install Product dialog open. You can then install Tivoli/Plus for AutoSys on another set of clients or you can install another product. Note: A Tivoli/Enterprise Console event adapter for AutoSys must be installed in order to set up Event Management. It is recommended that you install this adapter at the same time you are installing the Tivoli/Plus for AutoSys module. For more information see Installing the Event Adapter for AutoSys on page 4-5.
111
Installing from the Desktop The installation process prompts you with a Product Install dialog similar to the following example:
This dialog provides the list of operations that take place when installing the software. This dialog also warns you of any problems that you may want to correct before you install the Tivoli/Plus for AutoSys module.
112
Version 1.0
Installing from the Desktop Getting Started with Tivoli/Plus for AutoSys 9. Press the Continue Install button to begin the installation process. -ORPress the Cancel button to abort the installation process. When the installation is complete, the Product Install dialog displays a completion message similar to the following example.
Completion message
10. Press the Close button when the Product Install status dialog indicates that the installation is complete.
113
where: -c cdrom_path Species the path to the CD-ROM image. -s installation server Species the server on which the product is to be installed. -i index_le Species the index le from which the product is to be installed.
-l license_key Species the license key for the product. This parameter is optional for installations following the rst one. See the winstall command in the Tivoli Management Platform Reference Manual for more information.
Tivoli/Plus Icons
Although the Tivoli/Plus icons look like (traditional) TME icons, their functionality has been altered slightly to provide a faster, more intuitive approach to navigating and deploying the modules features. In some cases, such as a Tivoli/Courier le package prole, menu items have been removed from the icons pop-up menu to create a more point and click environment. The Tivoli/Plus icons can be activated in either of two ways:
s
Opening or executing the icon by double-clicking on it with the left mouse button. In many cases, double-clicking executes an activity (such as a task) without opening another dialog layer. Displaying the icons pull-down menu by pressing and holding the right mouse button.
114
Version 1.0
Tivoli/Plus Unique Features Getting Started with Tivoli/Plus for AutoSys Generally, either method may be used to access a particular function. There are cases, however, where a particular function can only be accessed by one of these methods. The following icon represents the Tivoli/Plus for AutoSys resources:
To prevent confusion between traditional TME and Tivoli/Plus for AutoSys functionality, each Tivoli/Plus icon has been overlaid with the Tivoli/Plus symbol to highlight its special functionality.
115
Use the following steps to see the modules included in your Tivoli/Plus collection: 1. From the main TME desktop, double-click on the TivoliPlus icon
116
Version 1.0
Starting a Tivoli/Plus Module Getting Started with Tivoli/Plus for AutoSys to display the TivoliPlus window.
The TivoliPlus window displays an icon for each Tivoli/Plus module installed. In the case above, only the Tivoli/Plus for AutoSys module is installed. Note: In some cases, icons in the TivoliPlus window may be placeholders for future modules. In the interim, they are used for informational purposes.
2.
Double-click on the TivoliPlus for AutoSys System icon to display the icons representing the tasks and other tools for managing the Autosys Workload Management Systems.
117
118
Version 1.0
Launching the AutoSys Application Getting Started with Tivoli/Plus for AutoSys The AutoSys Workload Management Applications have ve logical entry points:
s s s s s
Main GUI Job Console Time Scape Host Scape GUI calendar
Each logical entry point is pre-congured and appears on the pop-up menu for each AutoSys icon.
119
120
Version 1.0
2
Software Distribution for AutoSys
2
Tivoli/Plus for AutoSys includes hierarchical, pre-congured Tivoli/Courier le packages for distributing and installing the AutoSys applications on clients. Much of the conguration activity normally associated with a Tivoli/Courier le package has been done for you. Using Tivoli/Plus for AutoSys and Tivoli/Courier, you can install the AutoSys applications across a multi-platform network. Installing AutoSys clients is a two-stage process. First, you set up the AutoSys installation by conguring a Tivoli/Courier le package for each type of platform on which you are installing AutoSys. For example, if you are installing AutoSys on both a Solaris and a Sun platform, you need to congure a Tivoli/Courier le package twice, once for each platform. Second, you distribute the congured le packages by running the Install AutoSys Clients task. This task installs AutoSys on the selected subscribers for each platform for which you have congured a Tivoli/Courier le package. You can distribute AutoSys to all congured platforms or choose to distribute to only a single platform.
21
Function
Congures a Tivoli/Courier le package for distributing the AutoSys server applications on a UNIX platform. This le package can be set up to distribute bundled or unbundled software. Congures a Tivoli/Courier le package for distributing and installing the AutoSys client applications on a UNIX platform. This le package can be set up to distribute bundled or unbundled software.
Setup Icon
Use the following procedure to congure Tivoli/Courier le packages for the AutoSys UNIX client and UNIX server applications. Online help is available.
22
Version 1.0
Conguring Tivoli/Courier File Packages The elds on the SetUp AutoSys Client FilePackage and Setup AutoSys Server FilePackage windows are the same except for the Client Installation Information section. Server applications are not installed automatically on a UNIX platform. 1. Double-click on the Setup AutoSys UNIX Client FilePack icon to display the SetUp AutoSys Client FilePackage window.
23
Conguring Tivoli/Courier File Packages The Setup AutoSys Client FilePackage window allows you to congure the client installation parameters for a UNIX platform 2. Select the type of operating system on which you will be running AutoSys from the Tivoli Interpreter Type to Congure pop-up menu. If the operating system is not on the list, select Other from the Tivoli Interpreter Type to Congure pop-up menu, and enter the name of the operating system in the Other eld. Note: You need to complete the Setup AutoSys Client FilePackage window for each UNIX platform on which you will be running the AutoSys application.
3.
a. In the Managed Node Name eld, enter the name of the TME server or the managed node where the AutoSys source binaries are located. b. In the Get Files from eld, select whether the les will come from an existing AutoSys installation or directly from a tar le or device.
24
Version 1.0
Conguring Tivoli/Courier File Packages c. In the Path to Existing AutoSys Directory or tar File eld, enter the directory path where the existing AutoSys installation, tar le or device can be found. d. If you are installing from a tar le or device, the system needs a directory in which to unpack these les before distribution. Enter the path to the directory that you choose for this purpose in the 120 MB Scratch Directory eld. Note: After you have installed AutoSys from a device or tar le, you can use the scratch directory as the source of the AutoSys binaries for subsequent installations. To do this, select Existing AutoSys Installation from the Get Files from eld and then enter the path to the scratch directory in the Path to Existing AutoSys Directory or tar File eld. When you distribute or install AutoSys for the rst time, the system creates subdirectories in the directory that you specied for the AutoSys binaries. These subdirectories are named with the following format:
interpreter_type/AutoSys
where interpreter type refers to the platform on which AutoSys was installed. On subsequent installations, be sure to specify the full path name including the additional directories. For example, if the original path was:
/usr/source_staging
4.
In the AutoSys Destination Directory eld, enter the path to the directory on the target machine to which the AutoSys binaries will be distributed. If you are conguring the Setup AutoSys Server FilePackage window, press the Set and Close button to set all the information you have entered.
25
Conguring Tivoli/Courier File Packages Note: The elds on the Setup AutoSys Server FilePackage and the Setup AutoSys Client FilePackage windows are the same except for the Client Installation Information section. Tivoli/Courier le packages for AutoSys servers distribute server applications to clients, but do not install these applications automatically.
5.
If you are conguring the Setup AutoSys Client FilePackage window, enter the information regarding your client installation environment in the Client Installation Information section. The following describes each of the elds in this section: Client Type. Specify the name of the client type. Select All (all clients) or Jobs (jobs only). AutoUser Location. Enter the path to the AutoSys conguration les and output les. Auto Remote Executable Directory. Enter the path to the auto remote executable directory. Inetd File Location. Enter the path to the directory in which the inetd.conf le resides. Source of System Files. Specify the location of the system network les. Select Local (local machine), NIS, or NIS+. AutoSys Instance. Enter the unique name for the AutoSys instance. Auto Remote Service Name. Enter the service name for Auto Remote Service, which is specied in the inetd.conf le. Installation Log File. Enter the path to the client log le. Monitor. Specify the type of display the client machine uses. Select Color or Black and White.
26
Version 1.0
Conguring Tivoli/Courier File Packages AutoSys Owner. Enter the name of the AutoSys Owner, which is set by the auto_secure command. Auto Remote Service Port. Enter the port number for the Auto Remote Service. Action on Inetd File. Specify the action to take for the inetd le when the service entry is already present. Select Update or No Update. AutoUser Notify. Specify whether to stop distribution if the conguration les already exist in the specied directory. Auto Remote Notify. Specify whether to stop distribution if the specied conguration les already exist in the specied directory. Database Type. Specify the type of database (Sybase or Oracle). Oracle Server Host Name. Enter the name of the Oracle server host. Oracle Distribution Location. Enter the path to the Oracle home directory. Oracle TNS alias for Dataserver. Enter the TNS alias name for the Oracle data server that contains the AutoSys tablespace. Oracle TNS Admin. Enter the name of the TNS administrator. Is Client Bundled. Specify whether the client is bundled. Sybase Server Host Name. Enter the name of the Sybase server host. Sybase Interface File Location. Enter the path to the Sybase interface le. Sybase Dataserver. Enter the name of the Sybase dataserver. Sybase Database. Enter the name of the Sybase database. Software Distribution for AutoSys
27
6.
Press the Set and Close button at the bottom of the Setup AutoSys Client FilePackage window to set all of the information you have entered.
28
Version 1.0
where platform_name refers to the operating system on which AutoSys was installed. You will use the Install AutoSys FilePacks icon to install AutoSys. The AutoSys UNIX server and UNIX client applications use this icon. Note: Tivoli/Courier le packages for AutoSys servers distribute the server applications to clients, but do not install these applications automatically.
If you wish to view the Tivoli/Courier le packages that you have created, select the Open... option from the install icons pop-up menu
29
1.
Select the Open... option from the Install AutoSys FilePacks icon's pop-up menu
210
Version 1.0
Installing AutoSys Applications 2. For each le package, do the following: a. Select the Subscribers... option from the Install AutoSys FilePacks icon's pop-up menu to display the Subscribers window. b. Specify the subscription lists to which you want to install AutoSys by using the left and right arrow buttons to move the desired lists into the Current Subscribers eld. When nished, press the Set Subscriptions & Close button. Software Distribution for AutoSys
3. 4.
Close the Install AutoSys FilePacks window by selecting the Close option from the Collection pull-down menu. Select the Distribute option from the Install AutoSys FilePacks icon's pop-up menu. Selecting this option installs AutoSys onto the machines listed on the subscription lists that you specied for each le package.
211
2.
In the Install AutoSys FilePacks window, select the Subscribers... option from the pop-up menu of the icon representing the le package for the platform on which you wish to install AutoSys.
212
Version 1.0
Installing AutoSys Applications 3. Specify the subscription lists to which you want to install AutoSys on a single platform by using the left and right arrow buttons to move the desired lists into the Current Subscribers eld. When nished, press the Set Subscriptions & Close button.
4.
In the Install AutoSys FilePacks window, select the Distribute... option from the pop-up menu of the icon representing the le package. Selecting this option installs AutoSys onto the client machines listed on the subscription lists that you chose.
213
214
Version 1.0
3
3
Resource Monitoring
Tivoli/Plus for AutoSys provides the ability to monitor critical resources with Tivoli/Sentry. The Tivoli/Sentry monitors are predened to enable you to manage different aspects of the operating system, such as event processor log le size or host status, that are crucial to the continued availability of the AutoSys application. These monitors allow you to quickly identify and respond to potential problems so that system down time is avoided. Resource Monitoring
31
Function These monitors check the status of the AutoSys host systems (main machine, shadow machine, or job execution machine.) These monitors check the status of the event processor log le size.
Monitor Icon
To automatically add the Main Machine and Shadow Machine monitors to the Central AutoSys Server Monitors prole, you must specify the Event Processor Machine Name, and the Shadow Event Processor Machine Name elds in the Install Options window. For more information, seeInstalling from the Desktop on page 1-4. Use the add_jobmc_mon.sh <hostname> shell script to manually add the Job Execution Machines monitor to the Central AutoSys Server Monitors prole. You can copy this script to your home directory and execute it whenever new job execution machines are required.
32
Version 1.0
Using Tivoli/Plus for AutoSys Monitors The following example is the syntax for this script:
add_jobmc_mon.sh <hostname>
where: add_jobmc_mon.sh Species the command to add the Job Execution Machines monitor to the Central AutoSys Server Monitors prole. hostname Species the name of the host to be monitored. This is the host on which the AutoSys job is executed.
This script is shipped with the Tivoli/Plus for AutoSys CD-ROM. Before the Tivoli/Plus for AutoSys monitors are operational, they must be distributed to their subscription lists. To distribute a monitor, simply select the Distribute... option from the monitor's pop-up menu and then click on the Distribute Now button.
Resource Monitoring
33
After installation, the monitors are ready to be distributed to their default subscription list. The Central AutoSys Server Monitors are distributed to the Tivoli server. The Remote AutoSys Server Monitors are distributed to the AutoSys Server List. The AutoSys Client Monitors are distributed to the AutoSys Client List.
34
Version 1.0
Using Tivoli/Plus for AutoSys Monitors The default subscription list can be viewed or changed by using the Subscribers... option from the monitor's pop-up menu. Although the Tivoli/Plus for AutoSys monitors come already dened to monitor resources specic to AutoSys, you can add monitors from the Tivoli/Sentry collection or delete monitors as you wish. You can also edit existing monitors to perform different actions under different conditions. Selecting the options on a AutoSys monitor's pop-up menu displays the usual Tivoli/Sentry windows. Refer to the Tivoli/Sentry documentation for more detailed information on using these windows.
Resource Monitoring
Displays the Sentry Prole Properties window, which includes functions for adding, deleting, and editing monitors.
Displays the Distribute Proles window for distributing monitors to those managed nodes (machines) and profiles included on the monitors subscription list.
Displays the Subscribers window for specifying to which subscription list the monitor is distributed.
35
The thermometer on the AutoSys Sentry Indicators icon rises as the status of a monitored resource becomes more urgent. Open the Central AutoSys Server Monitors, the Remote AutoSys Server Monitors, or the AutoSys Client Monitors icon to view the status of the central AutoSys server or the resources on the remote server and client machines. For each monitored resource, the monitor only reports the most urgent status received within a recent time frame. The monitor reports are organized so that the most urgent status level appears at the top of the report. For more information on viewing the status of a monitored resource and on the Tivoli/Sentry indicator collection, refer to the Tivoli/Sentry documentation.
36
Version 1.0
Monitored Resources
Monitored Resources
The following table indicates the resources that Tivoli/Plus for AutoSys monitors.
Monitored Resource
Host Status
Described on Page
page 3-8
Monitor Icon
page 3-9
Resource Monitoring
37
Monitored Resources
Host Status
The host status monitor checks whether the status of a host is up or down. This monitor veries the status of any host or other resource on the network that can respond to a ping request. This monitor checks specically to see whether the targeted hosts are up or down. This monitor runs every 15 minutes. The following table lists the pre-congured actions for this monitor:
Severity
Critical
Trigger When
Becomes unavailable
Default Actions
Send event to the Tivoli/Enterprise Console. Change icon. None. None. Send event. None. None.
Monitors that are dened with this monitoring source use status operators to evaluate data. You can select the trigger when pop-up menu of the Edit Sentry Monitor window to display a list of the available operators. Refer to the Tivoli/Sentry documentation for more information on displaying the available operators.
38
Version 1.0
Monitored Resources
Severity
Critical
Trigger When
Greater than 8 MB.
Default Actions
Send event to the Tivoli/Enterprise Console. Page administrator. Change icon. Send event. Page administrator. Send event. Send event. None. None.
Greater than 5 MB. Greater than 3 MB. Less than 3 MB. N/A. N/A.
Resource Monitoring
39
Monitored Resources
310
Version 1.0
4
4
41
Conguration Activity
Conguration Activity
The following describes the conguration activity that occurs when setting up the Tivoli/Enterprise Console to be used with Tivoli/Plus for AutoSys. This activity takes place on the Tivoli/Enterprise Console and AutoSys servers.
s
Setting Up the Tivoli/Enterprise Console When you complete the procedure in Setting Up the Tivoli/Enterprise Console on page 4-3, the Tivoli/Enterprise Console is set up to: Recognize and accept AutoSys events. Respond to AutoSys events according to the predened rules. Notify the system administrator of the events received and the action taken.
Installing the Event Adapter for AutoSys When you complete the procedure in Installing the Event Adapter for AutoSys on page 4-5, you install the event adapter for AutoSys on the AutoSys server. You also congure this event adapter to recognize and forward AutoSys events to the Tivoli/Enterprise Console.
Tivoli/Plus for AutoSys performs most of the setup activity automatically. The following icon represents the Setup EventServer for AutoSys task.
42
Version 1.0
2.
Specify the rule base that you want to contain the AutoSys event classes and rules in the New (or existing) Rule Base name eld. You can accept the default rule base (TivoliPlus) or create a new rule base (by entering a new name) or modify an existing rule base (by entering an existing name).
43
Setting Up the Tivoli/Enterprise Console Note: It is not advisable to modify the Default rule base, so do not enter Default in the New (or existing) Rule Base name eld.
New rule bases are created by copying (cloning) and modifying an existing one. If you are creating a new rule base, enter the name of the rule base to be copied in the Rule Base to clone eld:
If you are creating a new rule base, specify the path name to the directory on the Tivoli/Enterprise Console server in which you want to create the new rule base. Only use the Path for new Rule Base eld if you are creating (not modifying) a rule base.
3.
(Optional). Use the Name of Event Console to congure eld to display AutoSys related events on a particular system administrator's event console. To make this assignment, enter the name that appears under the desired system administrator's event console icon. For example, Root_indigo-region.
4.
44
Version 1.0
45
Installing the Event Adapter for AutoSys 2. Select the appropriate event adapter from the Select Product to Install scrolling list. In the following example, the event adapter for the Oracle database is selected.
After you have selected the event adapter from the Select Product to Install scrolling list, the Install Options dialog is displayed. 3. Enter the required information in the Install Options dialog. For more information on specifying the install options parameters,
46
Version 1.0
Installing the Event Adapter for AutoSys refer to the documentation for conguring the Tivoli/Enterprise Console event adapters. EventServer Location (Hostname). Enter the host name on which the Tivoli event server is running. Port Number. Enter the port number that the event adapter will use to communicate with the event server. Max. Size of Tivoli Event. Accept the default value or specify the maximum length of event messages. Enter Type of connection. Specify the connection mode to use to connect to the Tivoli event server. The valid values are connection_oriented and connection_less. AutoSys Server Location (Hostname). Enter the name of the host on which the AutoSys server resides. AutoSys Data Server Name. Enter the data server name of the AutoSys database. AutoSys Database Name. Enter the name of the database used by AutoSys. AutoSys Owner Name. Enter the name of the AutoSys owner as set by the autosecure command. Path for sqlplus executable. Enter the name of the directory where the sqlplus executable is located. This eld only applies to Oracle database users. Enterprise Event Management
47
After closing the Install Options dialog, you can edit the parameters you specied by selecting the Congure T/EC Adapter option on the AutoSys _setup icons pop-up menu. For more information on running AutoSys_setup and other tasks, refer to Chapter 5, Tasks and Jobs for AutoSys. Note: You can further customize the install options by editing the tecad_autosys.cong le located in the directory where you have installed the Tivoli/Enterprise Console event adapter.
4.
Press the Set and then the Close button on the Install Options dialog when you are ready to continue.
48
Version 1.0
Running the Event Adapter for AutoSys 5. Click on the Install or Install & Close button on the Install Product dialog to install the Tivoli/Enterprise Console event adapter for AutoSys. Enterprise Event Management
49
Event Correlation
Tivoli/Plus for AutoSys provides event correlation. Event correlation is the tracking of multiple events whose occurrence may indicate an error condition or abnormal activity. For example, if the DB_PROBLEM event occurs more than once in 24 hours, Tivoli/Plus for AutoSys displays the multiple db problems message on the Tivoli/Enterprise Console. Likewise, Tivoli/Plus for AutoSys can remove obsolete events from the Tivoli/Enterprise Console. If a jobs status changes from running to failure, for example, Tivoli/Plus for AutoSys removes the previous running event from the Tivoli/Enterprise Console. The Tivoli/Plus for AutoSys event correlation rules determine if a number of separate events are related to each other. The event correlation rules determine how the Tivoli/Enterprise Console responds to a specic combination of events and which message the Tivoli/Enterprise Console displays on the event consoles.
410
Version 1.0
411
Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity:
job jobname started Event Description: Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity: The job started if the jobs dened starting conditions permitted and the job was not already running. AutoSys_Action WARNING STARTJOB Action No message is displayed on the Tivoli/Enterprise Console.
412
Version 1.0
job jobname failed Event Description: Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity: An AutoSys job has failed. AutoSys_Alarm CRITICAL JOBFAILURE Alarm Display message on the Tivoli/Enterprise Console.
413
Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity: max restarts tried Event Description:
AutoSys has attempted to restart a job the maximum number of times as specied in the conguration le, using MaxRestartTrys. AutoSys_Alarm CRITICAL MAX_RETRYS Alarm Display message on the Tivoli/Enterprise Console. If this event has occurred more than twice in the last 24 hours, display the multiple maxtrys message on the Tivoli/Enterprise Console.
Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity:
414
Version 1.0
job jobname priority changed Event Description: Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity: A jobs priority has been manually changed. AutoSys_Action HARMLESS CHANGE_PRIORITY Alarm Display message on the Tivoli/Enterprise Console. If this event has occurred more than three times in the last three hours, display the multiple manual interventions message on the Tivoli/Enterprise Console.
415
416
Version 1.0
job jobname taken off hold Event Description: Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity: A job has been manually taken off hold. The job will start as it would have before being placed on hold. AutoSys_Action HARMLESS JOB_OFF_HOLD Status Display message on the Tivoli/Enterprise Console. Remove the jobs previous on hold event from the Tivoli/Enterprise Console.
417
job jobname put on ice Event Description: Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity: This event instructs the event processor to place a job on ice. This event is manually generated. AutoSys_Action HARMLESS JOB_ON_ICE Status Display message on the Tivoli/Enterprise Console. If this event has occurred more than three times in the last three hours, display the multiple manual interventions message on the Tivoli/Enterprise Console.
418
Version 1.0
Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity:
job ended too soon Event Description: A job has nished before its dened processing time. A jobs minimum processing time is specied in the min_run_alarm eld. AutoSys_Alarm CRITICAL MINRUNALARM Alarm Display message on the Tivoli/Enterprise Console. If this event has occurred more than twice in the last 24 hours, display the multiple minruns message on the Tivoli/Enterprise Console.
Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity:
419
420
Version 1.0
Administrator Comments comment sent Event Description: An administrator has issued a comment. Comments are generated at runtime and can be associated with a particular job. AutoSys_ Comment HARMLESS COMMENT Admin Display message on the Tivoli/Enterprise Console.
Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity:
421
fatal DB error Event Description: Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity: A fatal AutoSys database problem has occurred. AutoSys_Alarm CRITICAL DB_PROBLEM Alarm Display message on the Tivoli/Enterprise Console. If this event has occurred more than once in the last 24 hours, display the multiple db problems message on the Tivoli/Enterprise Console.
422
Version 1.0
Event Processor event processor stopped Event Description: Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity: The event processor has been manually shut down. AutoSys_Action WARNING STOP_DEAMON Action Display message on the Tivoli/Enterprise Console.
423
Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity:
event processor failover occurred Event Description: Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity: The shadow event processor is taking over processing. AutoSys_Alarm CRITICAL EP_ROLLOVER Alarm Display message on the Tivoli/Enterprise Console. If this event has occurred more than once in the last 24 hours, display the primary failover to shadow message on the Tivoli/Enterprise Console.
424
Version 1.0
AutoSys event processing error Event Description: Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity: An event processor had an error while processing an event. AutoSys_Alarm CRITICAL EVENT_HDLR_ERROR Alarm Display message on the Tivoli/Enterprise Console.
425
426
Version 1.0
Disk Space insufcient disk space Event Description: Event Class: Event Severity: AutoSys Event: AutoSys Event Type: Correlation Activity: There is an alarm indicating that there is a resource related problem, such as insufcient disk space for a job to start. AutoSys_Alarm CRITICAL RESOURCE Alarm Display message on the Tivoli/Enterprise Console. If this event has occurred more than once in the last hour, display the low on diskspace message on the Tivoli/Enterprise Console.
427
Tivoli/Sentry Events
The following table describes the events and rules that Tivoli/Sentry uses when monitoring AutoSys resources. The table is organized according to the Tivoli/Sentry monitor that sends the event to the Tivoli/Enterprise Console. Since Tivoli/Sentry messages follow a standard format, these messages are not reproduced in the table. The following is an example of a Tivoli/Sentry message:
Sentry AutoSys Remote Monitors/Daemon status on host noonan Mon Oct 02 08:00:00 1995 Status: >>> critical <<< Daemon status (jobman) Changes to down (Previous: up Current: down Effective: down) Daemon: jobman
Tivoli/Sentry Events
Host Status Host is unavailable Event Description: Event Class: Event Severity: Correlation Activity: A host (main machine, shadow machine, or job execution machine) is unavailable. AutoSys_via_Sentry2_0_host CRITICAL Check for previous CRITICAL events of this type. If there are any, increase the events repeat count.
428
Version 1.0
> 5 MB Event Description: Event Class: Event Severity: Correlation Activity: The event processor log le size is greater than 5 MB. AutoSys_via_Sentry2_0_lesize SEVERE Check for any previous SEVERE events of this type. If there are any, increase that events repeat count. Check for any previous WARNING, CRITICAL, OR FATAL events of this type. If there are any, close the event.
429
< 3 MB Event Description: Event Class: Event Severity: Correlation Activity: The event processor log le size has decreased below 3 MB. AutoSys_via_Sentry2_0_lesize HARMLESS Close related CRITICAL, FATAL, SEVERE, or WARNING events in the Tivoli/Enterprise Console.
430
Version 1.0
5
5
51
Stops the main event processor with the option of stopping the shadow event processor.
Starts the primary or any bundled data server in single or dual mode.
Stops the primary or any bundled data server in single or dual mode.
Starts the Tivoli/Enterprise Console event adapter for AutoSys. For information on installing the event adapter, refer to Installing the Event Adapter for AutoSys on page 4-5.
52
Version 1.0
Prints job reports on the AutoSys server. You can specify whether the report be detailed or a summary. You can also specify whether the report is displayed on the screen or sent to a specic printer. Allows you to edit the conguration parameters you specied when installing the Tivoli/Plus for AutoSys module (see Installing from the Desktop on page 1-4) and the Tivoli/Enterprise Console event adapter for Autosys (see Installing the Event Adapter for AutoSys on page 4-5). The name of this jobs icon includes the server on which the Tivoli/Plus for AutoSys module is installed. For example, AutoSys_setup@indigo.
53
OR
54
Version 1.0
Running an AutoSys Job and Saving the Output If Tivoli/Plus for AutoSys requires further information to execute the job, a pop-up window appears prompting you for the information. Online help is available to assist you in completing these windows.
55
Running an AutoSys Job and Saving the Output The jobs output is displayed in an output window. To save the jobs output to a le: 1. 2. 3. 4. Select the Save to File... button to display the Save Job Output dialog box. Enter the name of the machine on which to save the output le in the On Host eld. Enter the name of the output le that will contain the jobs output. Select the Save & Close button to save the output of the job to the le you specied.
You can also use the Modify job... option of the job icons pop-up menu to specify that the output be sent to a le.
56
Version 1.0
Be sure to specify on which managed nodes and profile managers the job will run.
57
Modifying an AutoSys Job 2. Make the necessary changes in the Edit Job window. Online help is available to assist you. Note: 3. Be sure to specify on which managed nodes and prole managers the job will run.
58
Version 1.0
Be sure to specify on which managed nodes and profile managers the job will be run this time.
2. 3.
Make the necessary changes in the Execute Task window. Online help is available to assist you. Click on the Execute button when nished.
59
510
Version 1.0
Index
E
Edit Job Window 5-7 event adapter installing 4-5 running 4-9 event correlation 4-10 event management 4-1 4-30 event messages AutoSys custom 4-11 4-27 Tivoli/Sentry 4-28 4-30 events AutoSys custom administrator comments 4-21 AutoSys version mismatch 4-26 database status 4-22 disk space 4-27 event processor 4-23 event queue 4-26 job duration 4-19 job heartbeats 4-20 job status 4-11 UNIX processes 4-27 correlating 4-10 Tivoli/Sentry event processor log file size 4-29 host status 4-28 Execute Task window 5-9
A
activating Tivoli/Plus icons 1-14 authorization role 1-2 AutoSys installing 2-9 all platforms 2-10 single platform 2-12 starting 1-18 AutoSys custom events 4-11 4-27
C
command line installation 1-14 commands winstall 1-14 wsupport v Configure Tivoli/Enterprise Console AutoSys Events window 4-3 configuring file packages 2-2 2-8 for UNIX platforms 2-2 icons for 2-2 conventions, typeface v correlating events 4-10 customer support, contacting v
for
F
File Browser window 1-6 file packages distributing See installing AutoSys file size 3-9 file system monitor 3-9
D
desktop installation 1-4 dialogs See windows Distribute Profiles window 3-4 documents, related to this guide iv
Index1
G
getting started
1-1 1-19
H
hardware requirements host status 3-8
1-3
L
launching AutoSys license key 1-2
1-18
I
icons activating 1-14 AutoSys application 1-15 for AutoSys jobs 5-2 for configuring file packages 2-2 for installing AutoSys 2-9 for monitored resources 3-7 for monitors 3-2, 3-7 plus symbol 1-15 Sentry indicator 3-6 Install AutoSys FilePacks window 2-10,
M
machine requirements 1-2, 1-3 managing events 4-1 4-30 modifying jobs 5-7 monitored resources file size 3-9 host status 3-8 icons for 3-7 list of 3-7 viewing 3-6 monitoring resources 3-1 3-9 monitors customizing 3-5 distributing 3-3 icons for 3-2 using 3-2 3-5
2-12
Install Options window 1-10, 4-8 Install Product window 1-5, 1-8,
4-6,
4-9
installing AutoSys 2-9 all platforms 2-10 single platform 2-12 installing AutoSys event adapter 4-5 installing Tivoli/Plus for AutoSys from the desktop 1-4 requirements for 1-2 1-3
P
prerequisite documents, to this guide problem report, TME vi procedures configuring file packages for UNIX platforms 2-2 customizing monitors 3-5 distributing monitors 3-3 installing AutoSys 2-9 all platforms 2-10
iv
J
jobs AutoSys 5-2 list of 5-2
Index2
Version 1.0
single platform 2-12 modifying jobs 5-7 saving ouput 5-6 starting a module 1-16 AutoSys 1-18 using monitors 3-2 viewing monitored resources 3-6 Product Install window 1-12, 1-13
T
tasks See jobs 5-2 Tivoli/Courier, configuring file packages
2-2 2-8
for UNIX platforms 2-2 icons for 2-2 Tivoli/Plus plus symbol 1-15 unique features 1-15 Tivoli/Plus for AutoSys module icon 1-15 starting 1-16 Tivoli/Sentry events 4-28 4-30 See also events, Tivoli/Sentry 4-28 Tivoli/Sentry, monitors See monitors 3-2 TivoliPlus for AutoSys System window
R
related documents, to this guide iv requirements for installation See installing Tivoli/Plus for AutoSys, requirements for resource monitoring 3-1 3-9 rules 4-10 4-30 running AutoSys jobs 5-4 the AutoSys event adapter 4-9
1-18, 1-19
TivoliPlus window 1-17 TME desktop window 1-4, 1-16 problem report vi TME Desktop window 4-5 typeface conventions v
S
saving output 5-6 Sentry Indicator Collection window 3-6 Setup AutoSys Client FilePackage window
U
using monitors
3-2 3-5
2-3
software distribution 2-1 2-13 requirements 1-2 starting a module 1-16 AutoSys 1-18 Subscribers window 2-11, 2-13
W
windows Configure Tivoli/Enterprise Console for AutoSys Events 4-5 Distribute Profiles 3-4 Edit Job 5-7 Execute Task 5-9 File Browser 1-6
Index3
Install AutoSys FilePacks 2-10, 2-12 Install Options 1-10, 4-8 Install Product 1-5, 1-8, 4-9 Product Install 1-12, 1-13 Sentry Indicator Collection 3-6 Setup AutoSys UNIX Client FilePack
2-3
Subscribers 2-11, 2-13 Tivoli/Plus for AutoSys System 1-18,
1-19
TivoliPlus 1-17 TME desktop 1-4, 1-16, 4-5 winstall command 1-14 wsupport command v
Index4
Version 1.0