Tivoli/Plus for AutoSys User’s Guidedocshare01.docshare.tips/files/9283/92838535.pdf · Preface iv Version 1.0 Prerequisite and Related Documents The information in the Tivoli/Plus

Tivoli/Plus for AutoSys User’sGuide

Version 1.0

August 23, 1996

Tivoli/Plus for AutoSys User’s Guide (August 23, 1996)Copyright NoticeCopyright © 1991–1996 by Tivoli Systems Inc., including this documentation and all software. All rightsreserved. May only be used pursuant to a Tivoli Systems Incorporated Software License Agreement orAddendum for Tivoli Products to IBM Customer or License Agreement. No part of this publication maybe reproduced, transmitted, transcribed, stored in a retrieval system, or translated into any computerlanguage, in any form or by any means, electronic, mechanical, magnetic, optical, chemical, manual, orotherwise, without prior written permission of Tivoli Systems Inc. This document was prepared by TivoliSystems 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.

Restricted Rights Notice

The Software and its related documentation are provided with "Restricted Rights",unless the Government agrees to other terms. Use, duplication or disclosure by theGovernment is subject to the restrictions set forth in FAR clause 52.227-14 (AlternateIII) or FAR Clause 52.227-19. Unpublished--All Rights Reserved Under the Copy-right Laws of the United States. Manufacturer/Contractor is Tivoli Systems Inc., 9442Capital of Texas Highway, North, Arboretum Plaza One, Suite 500, Austin, Texas78759.

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, TivoliApplication Service, Tivoli/ADE, Tivoli/Admin, Tivoli/AEF, Tivoli/Courier, Tivoli/EIF, Tivoli/EnterpriseConsole, 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 theirrespective manufacturers.

Patent pending.

Tivoli/Plus for AutoSys User’s Guide i

Tivoli/Plus for AutoSysUser’s Guide

Preface................................................................................................................... iii

Who Should Read This Guide...................................................................... iii

Prerequisite and Related Documents............................................................ iv

What This Guide Contains ........................................................................... iv

Typeface Conventions................................................................................... v

Contacting Customer Support ....................................................................... v

Chapter 1—Getting Started with Tivoli/Plus for AutoSysInstallation Requirements ...................................................................................1-2

License Key................................................................................................1-2

Software Requirements ..............................................................................1-2

Hardware Requirements .............................................................................1-3

Installing from the Desktop ................................................................................1-4

Installing from the Command Line...................................................................1-14

Tivoli/Plus Icons ...............................................................................................1-14

Tivoli/Plus Unique Features .............................................................................1-15

Starting a Tivoli/Plus Module...........................................................................1-16

Launching the AutoSys Application.................................................................1-18

Chapter 2—Software Distribution for AutoSysConfiguring Tivoli/Courier File Packages..........................................................2-2

Installing AutoSys Applications .........................................................................2-9

Distributing and Installing AutoSys on All Configured Platforms ..........2-10

Installing AutoSys on a Single Platform ..................................................2-12

Chapter 3—Resource MonitoringUsing Tivoli/Plus for AutoSys Monitors ............................................................3-2

Viewing the Status of Monitored Resources ......................................................3-6

ii Version 1.0

Monitored Resources .......................................................................................... 3-7

Host Status ................................................................................................. 3-8

Event Processor Log File Size ................................................................... 3-9

Chapter 4—Enterprise Event ManagementConfiguration Activity........................................................................................ 4-2

Setting Up the Tivoli/Enterprise Console........................................................... 4-3

Installing the Event Adapter for AutoSys........................................................... 4-5

Running the Event Adapter for AutoSys ............................................................ 4-9

Events and Rules............................................................................................... 4-10

Event Correlation ..................................................................................... 4-10

AutoSys Custom Events........................................................................... 4-11

Tivoli/Sentry Events................................................................................. 4-28

Chapter 5—Tasks and Jobs for AutoSysTivoli/Plus for AutoSys Jobs .............................................................................. 5-2

Running an AutoSys Job and Saving the Output................................................ 5-4

Modifying an AutoSys Job ................................................................................. 5-7

Modifying for All Future Executions of the Job........................................ 5-7

Modifying for a Single Execution of the Job ............................................. 5-9

Preface

Tivoli/Plus for AutoSys User’s Guide iii

PrefaceTheTivoli/Plus for AutoSys User’s Guide describes specific featuresand procedures for using the Tivoli/PlusTM for AutoSys module. Thismodule was jointly developed by Tivoli Systems Inc. and PlatinumTechnology Inc. and provides an integration of the AutoSysTM

workload management application with the Tivoli ManagementEnvironmentTM (TME). Through this integration, the Tivoli/Plus forAutoSys module delivers the system management capabilities of TMEfor specific use with AutoSys. Using Tivoli/Plus for AutoSys, theAutoSys application can be managed across a multi-platform networkthat includes PCs and UNIX systems.

Tivoli/Plus provides different modules for integrating differentproduction control applications with the Tivoli ManagementEnvironment. Since all Tivoli/Plus modules have a common interface,a system administrator can implement the system managementcapabilities of the TME with various production control applicationswhile enjoying the simplicity of a common interface. The addition ofTivoli/CourierTM, Tivoli/SentryTM, and the Tivoli/EnterpriseConsoleTM provides additional management capabilities in the areas ofclient installation, resource monitoring, and event correlation.

Who Should Read This GuideThis guide is for system administrators who use the Tivoli/Plus forAutoSys module to manage the operation of the AutoSys application.Readers of this guide should be familiar with the Tivoli ManagementEnvironment and should have knowledge of the UNIX operatingsystem; concepts such as directories, files, symbolic links; and theoperating systems running on the machines on which they will beusing the Tivoli/Plus module, TME, and the AutoSys application.

Note: All references to “Sentry” in this guide refer tothe Tivoli/Sentry product or its components.

Preface

iv Version 1.0

Prerequisite and Related DocumentsThe information in theTivoli/Plus for AutoSys User’s Guidecomplements information presented in theTivoli ManagementPlatform User’s Guideand the Tivoli/Plus User’s Guide. You must befamiliar with the Tivoli Management Platform and Tivoli/Plus beforeyou can effectively use a specific Tivoli/Plus module. You should befamiliar with the documentation for these products before attemptingto use the information in theTivoli/Plus for AutoSys User’s Guide.Additionally, you should be familiar with the documentation for theAutoSys application.

What This Guide ContainsTheTivoli/Plus for AutoSys User’s Guidecontains the followingchapters:

■ Chapter 1, “Getting Started with Tivoli/Plus for AutoSys”Contains the installation requirements and procedures forinstalling Tivoli/Plus for AutoSys. This chapter also containsinformation about Tivoli/Plus icons, features unique toTivoli/Plus, and launching the AutoSys application.

■ Chapter 2, “Software Distribution for AutoSys”Describes how to set up Tivoli/Courier to be used withTivoli/Plus for AutoSys for distributing and installing theAutoSys application across a network.

■ Chapter 3, “Resource Monitoring”Describes how Tivoli/Sentry may be used with Tivoli/Plus forAutoSys to monitor AutoSys resources in order to detect andprevent system problems.

■ Chapter 4, “Enterprise Event Management”Describes how to set up the Tivoli/Enterprise Console to be usedwith Tivoli/Plus for AutoSys to provide event management. Thischapter also contains a description of the events and rules specificto Tivoli/Plus for AutoSys.

■ Chapter 5, “Tasks and Jobs for AutoSys”Describes how to customize and run AutoSys jobs and reportswith Tivoli/Plus for AutoSys.

Preface

Tivoli/Plus for AutoSys User’s Guide v

Typeface ConventionsThis guide uses several typeface conventions for special terms andactions. These conventions have the following meaning:

Bold Commands, keywords, file names, or otherinformation that you must use literally appear inbold.Names of windows, dialogs, and other controls alsoappear inbold.

Italics Variables and values that you must provide appear initalics.

Bold Italics New terms appear in bold italic the first time they areused.

Monospace Code examples appear in amonospace font.

This guide may include icons in the left margin. These icons providecontext for the discussion in the text or for performing a step within aprocedure. For example, if you start a procedure by double-clicking ona task icon, that icon appears in the left margin next to the first step. Ifthe fourth step of the procedure instructs you to open another icon, thaticon appears in the left margin next to the fourth step.

Contacting Customer SupportWe are very interested in hearing from you about your experience withthe products in the Tivoli Management Environment. We welcomeyour suggestions for improvements.

If you encounter difficulties with any TME product, please contactyour customer support representative. To assist you, this sectionincludes the TME Problem Report form. You can use this form to faxproblem information to your support provider. Tivoli also includes thewsupport command. This command prompts you for probleminformation, which can be e-mailed to your support provider or savedto a text file. You can then print the saved file, and fax the resultingTME Problem Report form to your support provider.

Preface

vi Version 1.0

TME Problem Report

Name:

E-mail:

Company:

System Type:Operating System Rel:

Tivoli Product:

Problem On:

Priority:

3. Minor

Short Description (10 - 12 words):

Attempted Solutions:

Description / Error Messages:

Phone #:

Fax #:

TMR #:

Version:

Tivoli Server Tivoli Client

2. Major1. Critical

4. No Impact

Previous Call Tracking #:

Tivoli/Plus for AutoSys User’s Guide 1–1

Getting S

tarted with

Tivoli/P

lus for AutoS

ys

1Getting Started with Tivoli/Plusfor AutoSys

The Tivoli/Plus for AutoSys module provides an integration of theTivoli Management Environment with the AutoSys WorkloadManagement Applications. This integration allows centralizeddistribution and management of the AutoSys application across amulti-platform network. This module provides the following featuresfor managing the AutoSys application:

■ Icons for launching the AutoSys application

■ Subscription lists for clients and servers

■ Tivoli/Courier file packages

■ Tivoli/Sentry monitors

■ Tivoli/Enterprise Console events and rule sets customized forAutoSys

■ AutoSys-specific tasks and jobs

Note: The Tivoli/Courier, Tivoli/Sentry, and Tivoli/EnterpriseConsole applications must be installed and configured beforetheir corresponding Tivoli/Plus feature is operational.

1

Installation Requirements

1–2 Version 1.0

Installation RequirementsBefore attempting to install Tivoli/Plus for AutoSys into the TivoliManagement Environment, make certain you review the requirementsin this section.

The following table provides the context and authorization rolerequired to install Tivoli/Plus for AutoSys.

The Tivoli/Plus for AutoSys module must be installed on the Tivoliserver. In order to have full functionality, the Tivoli/Plus for AutoSysmodule must also be installed on the following machines. Thesemachines must be Tivoli managed nodes.

■ The Tivoli/Enterprise Console (if there is one)

■ The AutoSys server

License KeyYou do not need a license key to use the Tivoli/Plus for AutoSysmodule if your module is installed on Tivoli Management Platform3.0. However, you must obtain a license key to use the Tivoli/Plus forAutoSys module if your module is installed on TMP 2.5. You mustcomplete and return the license request form that came with thissoftware. Tivoli Customer Support will then provide you with a licensekey for your module.

Software RequirementsThe AutoSys Workload Management Applications should be installedbefore 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

Activity Context Required Role

Installing Tivoli/Plus forAutoSys

TME install_product

Installation Requirements


Getting S

tarted with

Tivoli/P

lus for AutoS

ys

are not installed, then the specific feature requiring these applicationswill not work. However, the Tivoli/Plus for AutoSys installationallows you to incrementally re-install those features if you buy themissing products at a later date.

Hardware RequirementsThe following table provides the client and server disk spacerequirements for Tivoli/Plus for AutoSys. This space is in addition tothe space requirements for the management platform, the Tivoliapplication, and the AutoSys Workload Management Applications.

Tivoli/Plus for AutoSys is installed on the TME server, theTivoli/Enterprise Console server (if you have the Tivoli/EnterpriseConsole), and the AutoSys master machines. The space requirementsare the same for all of these machines. The Tivoli/Plus for AutoSysmodule uses platform-independent shell and Perl scripts, which is whythe module's requirements do not differ from platform to platform.

Platform Libraries Binaries Database Man PagesMessageCatalogs

0 MB 500 KB † 0 0 MB 50 KB

0 MB 500 KB † 0 0 MB 50 KB

0 MB 500 KB † 0 0 MB 50 KB

0 MB 500 KB † 0 0 MB 50 KB

0 MB 500 KB † 0 0 MB 50 KB

0 MB 500 KB † 0 0 MB 50 KB

AIX

HP-UX

OSF-1

Solaris

SunOS

SVR4

Installing from the Desktop

1–4 Version 1.0

Installing from the DesktopUse the following steps to install Tivoli/Plus for AutoSys from theTivoli desktop:

1. Select theInstall -> Install Product... option from theDesktopmenu



Getting S

tarted with

Tivoli/P

lus for AutoS

ys

to display theInstall Product dialog.

If the Tivoli/Plus for AutoSys module is listed in theSelectProduct to Install scrolling list, skip to step 3. If it is not listed,proceed to step 2.


1–6 Version 1.0

2. Press theSelect Media... button to display theFile Browserdialog.

TheFile Browser dialog enables you to identify or specify thepath to the installation media.

If you already know the path to the CD-ROM image

a. Enter the full path in thePath Name field.

b. Press theSet Path button to change to the specified directory.

c. Press theSet Media & Close button to save the new mediapath and return to theInstall Product dialog. The dialog nowcontains a list of products that are available for installation.



Getting S

tarted with

Tivoli/P

lus for AutoS

ys

If you do not know the exact path to the CD-ROM image

a. From theHosts scrolling list, choose the host on which theinstall media is mounted. Choosing a host updates theDirectories scrolling list to show the directories of the hostyou chose.

b. From theDirectories scrolling list, choose the directorycontaining the install media.

c. Press theSet Media & Close button to save the new mediapath and return to theInstall Product dialog. The dialog nowcontains a list of products that are available for installation.


1–8 Version 1.0

3. Select the Tivoli/Plus for AutoSys module from theSelectProduct to Install list.

After you have selected the Tivoli/Plus module from theSelectProduct to Install scrolling list, theInstall Options dialog isdisplayed.



Getting S

tarted with

Tivoli/P

lus for AutoS

ys

4. Enter the information regarding your AutoSys installationenvironment in theInstall Options dialog. The followingdescribes each of the fields on this dialog:

• AutoSys Directory. Enter the path to the AutoSys basedirectory.

• AutoSys User Directory.Enter the path to the AutoSys userdirectory.

• 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 theexec user.

• Event Processor Machine Name.Enter the machine namefor the event processor.

Note: When you specify theEvent Processor MachineNamefield, the Main Machine monitor is addedautomatically to the Central AutoSys ServerMonitors profile during installation.

• Shadow Event Processor Machine Name.Enter themachine name for the shadow event processor.

Note: When you specify theShadow Event ProcessorMachine Name field, the Shadow Machine monitoris added automatically to the Central AutoSys ServerMonitors profile during installation.

• TNS Alias. Enter the name of the TNS alias.

• Is Database Bundled(YES/NO).Enter YES if the databaseis bundled. Enter NO if the database is not bundled.

• Sybase or Oracle Distribution Location. Enter the path tothe Sybase or Oracle directory or interface file.

• Sybase Admin Password.Enter the Sybase administrator’spassword. This field only applies to Sybase database users.


1–10 Version 1.0

• Sybase DataServer.Enter the name of the Sybasedataserver. This field only applies to Sybase database users.

5. Press theSet and then theClosebutton on theInstall Optionsdialog when you are ready to continue.



Getting S

tarted with

Tivoli/P

lus for AutoS

ys

Note: The information you specify on theInstall Optionsdialog can be modified using theConfigure AutoSysEnvironment option on theAutoSys _setup task icon’spop-up menu. For more information on using theTivoli/Plus for AutoSys tasks, refer to page 5-1.

6. Specify the clients on which the module will be installed, byusing the left and right arrow buttons on theInstall Productdialog to move the machine names between theClients to InstallOn scrolling list and theAvailable Clients scrolling list.

By default, all machines in the current Tivoli Managed Region(TMR) are listed in theClients to Install On scrolling list. Tomove a machine name to theAvailable Clients list, choose oneor more clients from theClients to Install On scrolling list andpress the right arrow button. The chosen clients are moved fromtheClients to Install On scrolling list to theAvailable Clientsscrolling list.

7. Enter your license key for the Tivoli/Plus for AutoSys module intheLicense Key field.

8. Press theInstall & Close button to install the module and closethe Install Product dialog.

- OR -

Press theInstall button to install the module and keep theInstallProduct dialog open. You can then install Tivoli/Plus forAutoSys on another set of clients or you can install anotherproduct.

Note: A Tivoli/Enterprise Console event adapter for AutoSysmust be installed in order to set up Event Management.It is recommended that you install this adapter at thesame time you are installing the Tivoli/Plus for AutoSysmodule. For more information see “Installing the EventAdapter for AutoSys” on page 4-5.


1–12 Version 1.0

The installation process prompts you with aProduct Installdialog similar to the following example:

This dialog provides the list of operations that take place wheninstalling the software. This dialog also warns you of anyproblems that you may want to correct before you install theTivoli/Plus for AutoSys module.



Getting S

tarted with

Tivoli/P

lus for AutoS

ys

9. Press theContinue Install button to begin the installationprocess.

-OR-

Press theCancel button to abort the installation process.

When the installation is complete, theProduct Install dialogdisplays a completion message similar to the following example.

10. Press theClose button when theProduct Install status dialogindicates that the installation is complete.

Completionmessage

Installing from the Command Line

1–14 Version 1.0

Installing from the Command LineUse thewinstall command to install the Tivoli/Plus for AutoSysmodule. The following example is the syntax for thewinstallcommand and its parameters:

winstall -c cdrom_path -s installation_server \-i index_file -l license_key

where:

-c cdrom_path Specifies the path to the CD-ROM image.

-s installation serverSpecifies the server on which the product is to beinstalled.

-i index_file Specifies the index file from which the product is to beinstalled.

-l license_key Specifies the license key for the product. Thisparameter is optional for installations following thefirst one.

See thewinstall command in theTivoli Management PlatformReference Manual for more information.

Tivoli/Plus IconsAlthough the Tivoli/Plus icons look like (traditional) TME icons, theirfunctionality has been altered slightly to provide a faster, moreintuitive approach to navigating and deploying the module’s features.In some cases, such as a Tivoli/Courier file package profile, menuitems have been removed from the icon’s pop-up menu to create amore “point and click” environment.

The 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.

Tivoli/Plus Unique Features


Getting S

tarted with

Tivoli/P

lus for AutoS

ys

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

The following icon represents the Tivoli/Plus for AutoSys resources:

To prevent confusion between traditional TME and Tivoli/Plus forAutoSys functionality, each Tivoli/Plus icon has been overlaid withthe Tivoli/Plus symbol to highlight its special functionality.

Tivoli/Plus Unique FeaturesTivoli/Plus modules use the termprofile manager somewhatdifferently than the other Tivoli products. In a Tivoli/Plus module, aprofile manager's primary function is as asubscription list. Asubscription list identifies the machines that tasks and jobs run onwhen executed. Subscription lists can contain machine names or otherprofile managers. Adding a profile manager to a subscription list issimply a way of subscribing several machines at a time rather thanadding each one individually.

TheTivoli/Plus User's Guide describes the function of profilemanagers in the Tivoli/Plus modules in more detail. For moreinformation, see the section on subscribers and targets in theTivoli/Plus User's Guide.

Starting a Tivoli/Plus Module

1–16 Version 1.0

Starting a Tivoli/Plus ModuleAll Tivoli/Plus modules are kept in a collection under theTivoliPlusicon on the TME desktop. The module’s icon is added to this collectionafter installation. The following icon represents the Tivoli/Pluscollection:

Use the following steps to see the modules included in your Tivoli/Pluscollection:

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

Starting a Tivoli/Plus Module


Getting S

tarted with

Tivoli/P

lus for AutoS

ys

to display theTivoliPlus window.

TheTivoliPlus window displays an icon for each Tivoli/Plusmodule installed. In the case above, only the Tivoli/Plus forAutoSys module is installed.

Note: In some cases, icons in theTivoliPlus window may beplaceholders for future modules. In the interim, they areused for informational purposes.

2. Double-click on theTivoliPlus for AutoSys Systemicon todisplay the icons representing the tasks and other tools formanaging the Autosys Workload Management Systems.

Launching the AutoSys Application

1–18 Version 1.0

Launching the AutoSys ApplicationWhen Tivoli/Plus for AutoSys is installed on an AutoSys server, theinstallation process identifies the location of the AutoSys binarydirectories and creates an icon for launching the AutoSys WorkloadManagement Applications from within the TME.

Each AutoSys server has its own AutoSys icon for launching theAutoSys application from that server site. For example, for a servernamed “bart,” the following icon appears:



Getting S

tarted with

Tivoli/P

lus for AutoS

ys

The AutoSys Workload Management Applications have five logicalentry points:

■ Main GUI

■ Job Console

■ Time Scape

■ Host Scape

■ GUI calendar

Each logical entry point is pre-configured and appears on the pop-upmenu for each AutoSys icon.


1–20 Version 1.0


Softw

are Distribution for

AutoS

ys

2Software Distribution forAutoSys

Tivoli/Plus for AutoSys includes hierarchical, pre-configuredTivoli/Courier file packages for distributing and installing the AutoSysapplications on clients. Much of the configuration activity normallyassociated with a Tivoli/Courier file package has been done for you.Using Tivoli/Plus for AutoSys and Tivoli/Courier, you can install theAutoSys applications across a multi-platform network.

Installing AutoSys clients is a two-stage process. First, you set up theAutoSys installation by configuring a Tivoli/Courier file package foreach type of platform on which you are installing AutoSys. Forexample, if you are installing AutoSys on both a Solaris and a Sunplatform, you need to configure a Tivoli/Courier file package twice,once for each platform.

Second, you distribute the configured file packages by running theInstall AutoSys Clients task. This task installs AutoSys on theselected subscribers for each platform for which you have configureda Tivoli/Courier file package. You can distribute AutoSys to allconfigured platforms or choose to distribute to only a single platform.

2

Configuring Tivoli/Courier File Packages

2–2 Version 1.0

Configuring Tivoli/Courier File PackagesWhen configuring a Tivoli/Courier file package to be used withTivoli/Plus for AutoSys, you establish the location of the AutoSysinstallation directory so that Tivoli/Courier can locate the installationbinaries and files when installing. You also identify the destinationdirectory on the target machines to which the binaries will bedistributed.

Tivoli/Plus for AutoSys has a different setup icon depending onwhether you are configuring a file package for a server or client. Onceconfigured, the Tivoli/Courier file packages are installed with theInstall AutoSys FilePacksicon. (For an illustration of the install icon,see “Installing AutoSys Applications” on page 2-9.)

Note: Tivoli/Courier file packages for AutoSys servers distribute theserver applications to clients, but do not install theseapplications automatically.

Use the following procedure to configure Tivoli/Courier file packagesfor the AutoSys UNIX client and UNIX server applications. Onlinehelp is available.

Function Setup Icon

Configures a Tivoli/Courier filepackage for distributing theAutoSys server applications on aUNIX platform. This file packagecan be set up to distribute bundledor unbundled software.

Configures a Tivoli/Courier filepackage for distributing andinstalling the AutoSys clientapplications on a UNIX platform.This file package can be set up todistribute bundled or unbundledsoftware.



Softw


AutoS

ys

The fields on theSetUp AutoSys Client FilePackageand SetupAutoSys Server FilePackage windows are the same except for theClient Installation Information section. Server applications are notinstalled automatically on a UNIX platform.

1. Double-click on theSetup AutoSys UNIX Client FilePackiconto display theSetUp AutoSys Client FilePackagewindow.


2–4 Version 1.0

TheSetup AutoSys Client FilePackagewindow allows you toconfigure the client installation parameters for a UNIX platform

2. Select the type of operating system on which you will be runningAutoSys from theTivoli Interpreter Type to Configure pop-upmenu.

If the operating system is not on the list, selectOther from theTivoli Interpreter Type to Configure pop-up menu, and enterthe name of the operating system in theOther field.

Note: You need to complete theSetup AutoSys ClientFilePackagewindow for each UNIX platform on whichyou will be running the AutoSys application.

3. Identify the location of the AutoSys source binaries as follows:

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

b. In theGet Files from field, select whether the files will comefrom an existing AutoSys installation or directly from a tarfile or device.



Softw


AutoS

ys

c. In thePath to Existing AutoSys Directory or tar File field,enter the directory path where the existing AutoSysinstallation, tar file or device can be found.

d. If you are installing from a tar file or device, the system needsa directory in which to unpack these files before distribution.Enter the path to the directory that you choose for thispurpose in the120 MB Scratch Directory field.

Note: After you have installed AutoSys from a device or tarfile, you can use the scratch directory as the source ofthe AutoSys binaries for subsequent installations. Todo this, selectExisting AutoSys Installation fromtheGet Files from field and then enter the path to thescratch directory in thePath to Existing AutoSysDirectory or tar File field. When you distribute orinstall AutoSys for the first time, the system createssubdirectories in the directory that you specified forthe AutoSys binaries. These subdirectories arenamed with the following format:

interpreter_type/AutoSys

where interpreter type refers to the platform onwhich AutoSys was installed.

On subsequent installations, be sure to specify thefull path name including the additional directories.For example, if the original path was:

/usr/source_staging

and you installed on a solaris2 platform, you wouldspecify:

/usr/source_staging/solaris2/AutoSys

4. In theAutoSys Destination Directory field, enter the path to thedirectory on the target machine to which the AutoSys binarieswill be distributed.

If you are configuring theSetup AutoSys Server FilePackagewindow, press theSet and Closebutton to set all the informationyou have entered.


2–6 Version 1.0

Note: The fields on theSetup AutoSys Server FilePackageand theSetup AutoSys Client FilePackage windowsare the same except for theClient InstallationInformation section. Tivoli/Courier file packages forAutoSys servers distribute server applications to clients,but do not install these applications automatically.

5. If you are configuring theSetup AutoSys Client FilePackagewindow, enter the information regarding your client installationenvironment in the Client Installation Information section. Thefollowing describes each of the fields in this section:

• Client Type. Specify the name of the client type. SelectAll(all clients) orJobs (jobs only).

• AutoUser Location. Enter the path to the AutoSysconfiguration files and output files.

• Auto Remote Executable Directory. Enter the path to theauto remote executable directory.

• Inetd File Location. Enter the path to the directory in whichthe inetd.conf file resides.

• Source of System Files. Specify the location of the systemnetwork files. SelectLocal (local machine),NIS, or NIS+.

• AutoSys Instance. Enter the unique name for the AutoSysinstance.

• Auto Remote Service Name. Enter the service name forAuto Remote Service, which is specified in theinetd.conffile.

• Installation Log File. Enter the path to the client log file.

• Monitor . Specify the type of display the client machine uses.SelectColor or Black and White.



Softw


AutoS

ys

• AutoSys Owner. Enter the name of the AutoSys Owner,which is set by theauto_secure command.

• Auto Remote Service Port. Enter the port number for theAuto Remote Service.

• Action on Inetd File. Specify the action to take for theinetdfile when the service entry is already present. SelectUpdateor No Update.

• AutoUser Notify. Specify whether to stop distribution if theconfiguration files already exist in the specified directory.

• Auto Remote Notify. Specify whether to stop distribution ifthe specified configuration files already exist in the specifieddirectory.

• Database Type. Specify the type of database (SybaseorOracle).

• Oracle Server Host Name. Enter the name of the Oracleserver host.

• Oracle Distribution Location . Enter the path to the Oraclehome directory.

• Oracle TNS alias for Dataserver. Enter the TNS alias namefor the Oracle data server that contains the AutoSystablespace.

• Oracle TNS Admin. Enter the name of the TNSadministrator.

• Is Client Bundled. Specify whether the client is bundled.

• Sybase Server Host Name. Enter the name of the Sybaseserver host.

• Sybase Interface File Location. Enter the path to the Sybaseinterface file.

• Sybase Dataserver. Enter the name of the Sybase dataserver.

• Sybase Database. Enter the name of the Sybase database.


2–8 Version 1.0

6. Press theSet and Close button at the bottom of theSetupAutoSys Client FilePackage window to set all of theinformation you have entered.

Installing AutoSys Applications


Softw


AutoS

ys

Installing AutoSys ApplicationsAfter you have configured a Tivoli/Courier file package for eachplatform on which you wish to install a AutoSys application, you areready to install AutoSys on these platforms. You can distribute to allplatforms for which you have configured a Tivoli/Courier file packageor to a single platform. Tivoli/Plus for AutoSys performspre-installation checks, such as verifying available disk space andmemory. Output for each platform is sent to the source machine in thefollowing files:

/tmp/AutoSys_client_install.platform_name

where platform_name refers to the operating system on whichAutoSys was installed.

You will use theInstall AutoSys FilePacks icon to install AutoSys.The AutoSys UNIX server and UNIX client applications use this icon.


If you wish to view the Tivoli/Courier file packages that you havecreated, select theOpen... option from the install icon’s pop-up menu


2–10 Version 1.0

Distributing and Installing AutoSys on All ConfiguredPlatforms

Use the following procedure to install a particular AutoSys applicationon all platforms for which you have configured a Tivoli/Courier filepackage.


1. Select theOpen... option from theInstall AutoSys FilePacksicon's pop-up menu



Softw


AutoS

ys

2. For each file package, do the following:

a. Select theSubscribers... option from theInstall AutoSysFilePacksicon's pop-up menu to display theSubscriberswindow.

b. Specify the subscription lists to which you want to installAutoSys by using the left and right arrow buttons to move thedesired lists into theCurrent Subscribers field. Whenfinished, press theSet Subscriptions & Close button.

3. Close theInstall AutoSys FilePackswindow by selecting theClose option from theCollection pull-down menu.

4. Select theDistribute option from theInstall AutoSys FilePacksicon's pop-up menu. Selecting this option installs AutoSys ontothe machines listed on the subscription lists that you specified foreach file package.


2–12 Version 1.0

Installing AutoSys on a Single PlatformIf you want to install AutoSys on only one type of platform, you candistribute only the Tivoli/Courier file package that applies to thatplatform.

Use the following steps to install AutoSys on a single platform:

1. Select theOpen... option from theInstall AutoSys FilePacksicon's pop-up menu to display theInstall AutoSys FilePackswindow.

2. In theInstall AutoSys FilePackswindow, select theSubscribers... option from the pop-up menu of the iconrepresenting the file package for the platform on which you wishto install AutoSys.



Softw


AutoS

ys

3. Specify the subscription lists to which you want to installAutoSys on a single platform by using the left and right arrowbuttons to move the desired lists into theCurrent Subscribersfield. When finished, press theSet Subscriptions & Closebutton.

4. In theInstall AutoSys FilePackswindow, select theDistribute... option from the pop-up menu of the iconrepresenting the file package. Selecting this option installsAutoSys onto the client machines listed on the subscription liststhat you chose.


2–14 Version 1.0


Resource M

onitoring

3Resource Monitoring

Tivoli/Plus for AutoSys provides the ability to monitor criticalresources with Tivoli/Sentry. The Tivoli/Sentry monitors arepredefined to enable you to manage different aspects of the operatingsystem, such as event processor log file size or host status, that arecrucial to the continued availability of the AutoSys application. Thesemonitors allow you to quickly identify and respond to potentialproblems so that system down time is avoided.

3

Using Tivoli/Plus for AutoSys Monitors

3–2 Version 1.0

Using Tivoli/Plus for AutoSys MonitorsTivoli/Plus for AutoSys comes with three types of monitors:CentralAutoSys Server Monitors, Remote AutoSys Server Monitors,AutoSys Client Monitors.

To automatically add the Main Machine and Shadow Machinemonitors to the Central AutoSys Server Monitors profile, you mustspecify theEvent Processor Machine Name, and theShadow EventProcessor Machine Name fields in theInstall Options window. Formore information, see“Installing from the Desktop” on page 1-4.

Use the add_jobmc_mon.sh <hostname>shell script to manuallyadd the Job Execution Machines monitor to the Central AutoSysServer Monitors profile. You can copy this script to your homedirectory and execute it whenever new job execution machines arerequired.

Function Monitor Icon

These monitors check the status of theAutoSys host systems (main machine,shadow machine, or job executionmachine.)

These monitors check the status of theevent processor log file size.

These monitors check the status of theAutoSys client machines.



Resource M

onitoring

The following example is the syntax for this script:

add_jobmc_mon.sh <hostname>

where:

add_jobmc_mon.shSpecifies the command to add the Job ExecutionMachines monitor to the Central AutoSys ServerMonitors profile.

hostname Specifies the name of the host to be monitored. This isthe 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 mustbe distributed to their subscription lists. To distribute a monitor,simply select theDistribute... option from the monitor's pop-up menuand then click on theDistribute Now button.


3–4 Version 1.0

After installation, the monitors are ready to be distributed to theirdefault subscription list. TheCentral AutoSys Server Monitors aredistributed to the Tivoli server. TheRemote AutoSys ServerMonitors are distributed to theAutoSys Server List. TheAutoSysClient Monitors are distributed to theAutoSys Client List.



Resource M

onitoring

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

Although the Tivoli/Plus for AutoSys monitors come already definedto monitor resources specific to AutoSys, you can add monitors fromthe Tivoli/Sentry collection or delete monitors as you wish. You canalso edit existing monitors to perform different actions under differentconditions.

Selecting the options on a AutoSys monitor's pop-up menu displaysthe usual Tivoli/Sentry windows. Refer to the Tivoli/Sentrydocumentation for more detailed information on using these windows.

Displays the Sentry Profile Properties win-dow, which includes functions for adding,deleting, and editing monitors.

Displays the Distribute Profiles windowfor distributing monitors to those managednodes (machines) and profiles included onthe monitor’s subscription list.

Displays the Subscribers window for spec-ifying to which subscription list the moni-tor is distributed.

Viewing the Status of Monitored Resources

3–6 Version 1.0

Viewing the Status of Monitored ResourcesUse theAutoSys Sentry Indicators icon to view the status of themonitored resources.

The thermometer on theAutoSys Sentry Indicators icon rises as thestatus of a monitored resource becomes more urgent.

Open theCentral AutoSys Server Monitors, theRemote AutoSysServer Monitors, or theAutoSys Client Monitors icon to view thestatus of the central AutoSys server or the resources on the remoteserver and client machines. For each monitored resource, the monitoronly reports the most urgent status received within a recent time frame.The monitor reports are organized so that the most urgent status levelappears at the top of the report.

For more information on viewing the status of a monitored resourceand on the Tivoli/Sentry indicator collection, refer to the Tivoli/Sentrydocumentation.

Monitored Resources


Resource M

onitoring

Monitored ResourcesThe following table indicates the resources that Tivoli/Plus forAutoSys monitors.

Monitored ResourceDescribed on Page

Monitor Icon

Host Status page 3-8

Event Processor Log File Size page 3-9

Monitored Resources

3–8 Version 1.0

Host StatusThe host status monitor checks whether the status of a host is up ordown. This monitor verifies the status of any host or other resource onthe network that can respond to aping request. This monitor checksspecifically to see whether the targeted hosts are up or down.

This monitor runs every 15 minutes.

The following table lists the pre-configured actions for this monitor:

Monitors that are defined with this monitoring source use statusoperators to evaluate data. You can select thetrigger when pop-upmenu of theEdit Sentry Monitor window to display a list of theavailable operators. Refer to the Tivoli/Sentry documentation for moreinformation on displaying the available operators.

Severity Trigger When Default Actions

Critical Becomes unavailable Send event to theTivoli/Enterprise Console.Change icon.

Severe Never. None.

Warning Never. None.

Reset Becomes available. Send event.

Normal N/A. None.

Always N/A. None.

Monitored Resources


Resource M

onitoring

Event Processor Log File SizeThe event processor log file size monitor checks the size of the eventprocessor log files.

This monitor runs every 15 minutes.

The following table lists the pre-configured actions for this monitor:

Severity Trigger When Default Actions

Critical Greater than 8 MB. Send event to theTivoli/Enterprise Console.Page administrator. Change icon.

Severe Greater than 5 MB. Send event. Page administrator.

Warning Greater than 3 MB. Send event.

Reset Less than 3 MB. Send event.

Normal N/A. None.

Always N/A. None.

Monitored Resources

3–10 Version 1.0


Enterprise E

ventM

anagement

4Enterprise Event Management

With the Tivoli/Enterprise Console, Tivoli/Plus for AutoSys providesa set of filters for identifying events and a set of predefined correlationrules to automate the task of responding to specific events. An event isany significant change in the state of system resources or anapplication. In the case of Tivoli/Plus for AutoSys, an event is achange in a monitored resource that affects AutoSys or the system onwhich AutoSys is running. Examples of events are the starting andstopping of a process or a host going down. Event managementprovides a predefined or automated response to specific events, so thatpotential problems are identified and responded to before causingsystem down time. For example, if a process fails, theTivoli/Enterprise Console can automatically rerun the process. TheTivoli/Enterprise Console can also notify the system administrator ofrepeated process failures that may indicate a more severe problem withan application or the network. For some events, there is no automatedresponse except to display a message in the Tivoli/Enterprise Console.

4

Configuration Activity

4–2 Version 1.0

Configuration ActivityThe following describes the configuration activity that occurs whensetting up the Tivoli/Enterprise Console to be used with Tivoli/Plus forAutoSys. This activity takes place on the Tivoli/Enterprise Consoleand AutoSys servers.

■ Setting Up the Tivoli/Enterprise Console

When you complete the procedure in “Setting Up theTivoli/Enterprise Console” on page 4-3, the Tivoli/EnterpriseConsole is set up to:

• Recognize and accept AutoSys events.

• Respond to AutoSys events according to the predefined rules.

• Notify the system administrator of the events received andthe action taken.

■ Installing the Event Adapter for AutoSys

When you complete the procedure in “Installing the EventAdapter for AutoSys” on page 4-5, you install the event adapterfor AutoSys on the AutoSys server. You also configure this eventadapter to recognize and forward AutoSys events to theTivoli/Enterprise Console.

Tivoli/Plus for AutoSys performs most of the setup activityautomatically. The following icon represents theSetup EventServerfor AutoSys task.

Setting Up the Tivoli/Enterprise Console


Enterprise E

ventM

anagement

Setting Up the Tivoli/Enterprise ConsoleTo set up the Tivoli/Enterprise Console:

1. Select theRun job... option from theSetup EventServer forAutoSys icon's pop-up menu.

2. Specify the rule base that you want to contain the AutoSys eventclasses and rules in theNew (or existing) Rule Base namefield.You can accept the default rule base (TivoliPlus) or create a newrule base (by entering a new name) or modify an existing rulebase (by entering an existing name).

Setting Up the Tivoli/Enterprise Console

4–4 Version 1.0

Note: It is not advisable to modify theDefault rule base, so donot enterDefault in theNew (or existing) Rule Basenamefield.

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 theRule Base to clone field:

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 thePath for new RuleBase field if you are creating (not modifying) a rule base.

3. (Optional). Use theName of Event Console to configure fieldto display AutoSys related events on a particular systemadministrator's event console. To make this assignment, enter thename that appears under the desired system administrator's eventconsole icon. For example,Root_indigo-region.

4. Press theSet and Closebutton when finished.

Installing the Event Adapter for AutoSys


Enterprise E

ventM

anagement

Installing the Event Adapter for AutoSysIn order for the Tivoli event server to be able to recognize and respondto AutoSys custom events, you need to install and run theTivoli/Enterprise Console event adapter for Autosys. This eventadapter forwards AutoSys event information to the event server in aform recognizable by the event server. You need to install the eventadapter that suits your database type. For example, if you have anORACLE database, you would install the Tivoli/Enterprise Consoleevent adapter for Autosys that is appropriate for the Oracle database.

To install the Tivoli/Enterprise Console event adapter:

1. Select theInstall -> Install Product... option from the TMEDesktop menu

to display theInstall Product dialog.


4–6 Version 1.0

2. Select the appropriate event adapter from theSelect Product toInstall scrolling list. In the following example, the event adapterfor the Oracle database is selected.

After you have selected the event adapter from theSelectProduct to Install scrolling list, theInstall Options dialog isdisplayed.

3. Enter the required information in theInstall Options dialog. Formore information on specifying the install options parameters,



Enterprise E

ventM

anagement

refer to the documentation for configuring the Tivoli/EnterpriseConsole event adapters.

• EventServer Location (Hostname). Enter the host name onwhich the Tivoli event server is running.

• Port Number. Enter the port number that the event adapterwill use to communicate with the event server.

• Max. Size of Tivoli Event. Accept the default value orspecify the maximum length of event messages.

• Enter Type of connection. Specify the connection mode touse to connect to the Tivoli event server. The valid values areconnection_oriented andconnection_less .

• AutoSys Server Location (Hostname). Enter the name ofthe host on which the AutoSys server resides.

• AutoSys Data Server Name. Enter the data server name ofthe AutoSys database.

• AutoSys Database Name. Enter the name of the databaseused by AutoSys.

• AutoSys Owner Name. Enter the name of the AutoSysowner as set by theautosecure command.

• Path for ‘sqlplus’ executable. Enter the name of thedirectory where the‘sqlplus’ executable is located. This fieldonly applies to Oracle database users.


4–8 Version 1.0

After closing theInstall Options dialog, you can edit theparameters you specified by selecting theConfigure T/ECAdapter option on theAutoSys _setup icon’s pop-up menu. Formore information on runningAutoSys_setup and other tasks,refer to Chapter 5, “Tasks and Jobs for AutoSys.”

Note: You can further customize the install options by editingthe tecad_autosys.config file located in the directorywhere you have installed the Tivoli/Enterprise Consoleevent adapter.

4. Press theSet and then theClose button on theInstall Optionsdialog when you are ready to continue.

Running the Event Adapter for AutoSys


Enterprise E

ventM

anagement

5. Click on theInstall or Install & Close button on theInstallProduct dialog to install the Tivoli/Enterprise Console eventadapter for AutoSys.

Running the Event Adapter for AutoSysThe Tivoli/Plus for AutoSys module provides tasks for starting andstopping the Tivoli/Enterprise Console event adapter for AutoSys. Tostart the event adapter, double-click on theStart Event Adapter icon.Likewise, to stop the event adapter, double-click on theStop EventAdapter icon.

For more information on these tasks, refer to Chapter 5, “Tasks andJobs for AutoSys.”

Events and Rules

4–10 Version 1.0

Events and RulesTivoli/Plus for AutoSys configures the Tivoli/Enterprise Console toreceive events from AutoSys and Tivoli/Sentry. The Tivoli/EnterpriseConsole classifies the events and then matches them against the rulebase to see if the event has a predefined rule (automated response).

Event CorrelationTivoli/Plus for AutoSys provides event correlation. Event correlationis the tracking of multiple events whose occurrence may indicate anerror 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” messageon the Tivoli/Enterprise Console. Likewise, Tivoli/Plus for AutoSyscan remove obsolete events from the Tivoli/Enterprise Console. If ajob’s status changes from “running” to “failure,” for example,Tivoli/Plus for AutoSys removes the previous “running” event fromthe Tivoli/Enterprise Console.

The Tivoli/Plus for AutoSys event correlation rules determine if anumber of separate events are related to each other. The eventcorrelation rules determine how the Tivoli/Enterprise Consoleresponds to a specific combination of events and which message theTivoli/Enterprise Console displays on the event consoles.

Events and Rules


Enterprise E

ventM

anagement

AutoSys Custom EventsThe following events are sent to the Tivoli/Enterprise Console by theTivoli/Enterprise Console event adapter for AutoSys.

AutoSys Custom Events

Job Status

“job jobname deleted”

Event Description: The job or box definition has been removed from the database .

Event Class: AutoSys_Action

Event Severity: WARNING

AutoSys Event: DELETEJOB

AutoSys Event Type: Action

Correlation Activity: Display message on the Tivoli/Enterprise Console.

“job jobname force started”

Event Description: The job has been force started regardless of the job’s presentstatus definition.



AutoSys Event: FORCE_STARTJOB


Correlation Activity: Display message on the Tivoli/Enterprise Console.If this event has occurred more than three times in the last threehours, display the “multiple manual interventions” message onthe Tivoli/Enterprise Console.

Events and Rules

4–12 Version 1.0

“job jobname killed”

Event Description: This manually generated event instructs the event processor toterminate a specific job. If the marked job is in a BOX, the boxstatus changes to terminated.



AutoSys Event: KILLJOB


Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than three times in the last three hours, dis-play the “multiple manual interventions” message on theTivoli/Enterprise Console.

“job jobname started”

Event Description: The job started if the job’s defined starting conditions permit-ted and the job was not already running.



AutoSys Event: STARTJOB


Correlation Activity: No message is displayed on the Tivoli/Enterprise Console.


Events and Rules


Enterprise E

ventM

anagement

“job status out of synch”

Event Description: Thechase command has found a problem with a job that issupposed to be running.

Event Class: AutoSys_Alarm

Event Severity: CRITICAL

AutoSys Event: CHASE

AutoSys Event Type: Alarm

Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than once in the last 24 hours, display the“multiple chase alarms” message on the Tivoli/Enterprise Con-sole.

“job jobname failed”

Event Description: An AutoSys job has failed.



AutoSys Event: JOBFAILURE




Events and Rules

4–14 Version 1.0

“Job_Not_On_Ice _Hold”

Event Description: This event indicates that a job for which a JOB_ON_ICE or aJOB_ON__HOLD event was generated was not put on hold oron ice. A job cannot be put on hold or on ice under certainconditions. For example, a job that is already running cannotbe put on hold or on ice.



AutoSys Event: JOB_OFF_HOLD



“max restarts tried”

Event Description: AutoSys has attempted to restart a job the maximum number oftimes as specified in the configuration file, usingMaxRestartTrys.



AutoSys Event: MAX_RETRYS


Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than twice in the last 24 hours, display the“multiple maxtrys” message on the Tivoli/Enterprise Console.


Events and Rules


Enterprise E

ventM

anagement

“job jobname didn't start”

Event Description: AutoSys was unable to start a job.



AutoSys Event: STARTJOBFAIL


Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than once in the last hour, display the “mul-tiple startjobfails” message on the Tivoli/Enterprise Console.

“job jobname priority changed”

Event Description: A job’s priority has been manually changed.


Event Severity: HARMLESS

AutoSys Event: CHANGE_PRIORITY




Events and Rules

4–16 Version 1.0

“job jobname status changed”

Event Description: A job’s status has been changed (manually or automatically).

Event Class: AutoSys_Transition


AutoSys Event: CHANGE_STATUS



If the job’s status is “STARTING,” remove any previousFORCE_STARTJOB” events for the same job name and jobstatus from the Tivoli/Enterprise Console.

If the job’s status is “RUNNING,” remove any previous“STARTING,” “RESTART,” or “FORCE_STARTJOB” eventsfor the same job name and job status from the Tivoli/EnterpriseConsole.

If the job’s status is “FAILURE,” remove any previous“RUNNING,” or “FAILURE” events for the same job nameand job status from the Tivoli/Enterprise Console.

If the job’s status is “SUCCESS,” set the current event status to“CLOSED” and remove any previous “RUNNING” events forthe same job name and job status from the Tivoli/EnterpriseConsole.


Events and Rules


Enterprise E

ventM

anagement

“job jobname put on hold”

Event Description: This event instructs the event process to put a job on hold. Thisevent is manually generated.



AutoSys Event: JOB_ON_HOLD

AutoSys Event Type: Status


“job jobname taken off hold”

Event Description: A job has been manually taken off hold. The job will start as itwould have before being placed on hold.



AutoSys Event: JOB_OFF_HOLD


Correlation Activity: Display message on the Tivoli/Enterprise Console. Remove thejob’s previous “on hold” event from the Tivoli/Enterprise Con-sole.


Events and Rules

4–18 Version 1.0

“job jobname taken off ice”

Event Description: This event instates the event processor to take a job off ice.This event is manually generated.



AutoSys Event: JOB_OFF_ICE


Correlation Activity: Display message on the Tivoli/Enterprise Console. Remove thejob’s previous “on ice” event from the Tivoli/Enterprise Con-sole.

“job jobname put on ice”

Event Description: This event instructs the event processor to place a job on ice.This event is manually generated.



AutoSys Event: JOB_ON_ICE




Events and Rules


Enterprise E

ventM

anagement

Job Duration

“job running too long”

Event Description: A job is running longer than its defined processing time. Ajob’s maximum processing time is specified in themax_run_alarm field.



AutoSys Event: MAXRUNALARM


Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than twice in the last 24 hours, display the“multiple maxruns” message on the Tivoli/Enterprise Console.

“job ended too soon”

Event Description: A job has finished before its defined processing time. A job’sminimum processing time is specified in the min_run_alarmfield.



AutoSys Event: MINRUNALARM


Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than twice in the last 24 hours, display the“multiple minruns” message on the Tivoli/Enterprise Console.


Events and Rules

4–20 Version 1.0

Job Heartbeats

“heartbeat checked”

Event Description: The event processor has checked all jobs to see if any are miss-ing. If so, a MISSING_HEARTBEAT alarm will be sent.

Event Class: AutoSys_Admin


AutoSys Event: CHECK_HEARTBEAT

AutoSys Event Type: Admin


“heartbeat sent”

Event Description: This event is sent by the remote agent to post a heartbeat for aparticular job.

Event Class: AutoSys_Admin


AutoSys Event: HEARTBEAT




Events and Rules


Enterprise E

ventM

anagement

“job missed heartbeat”

Event Description: A job has not sent a heartbeat within the interval specified forthat job.



AutoSys Event: MISSING_HEARTBEAT


Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than once in the last 10 minutes, display the“multiple missing heartbeats” message on the Tivoli/EnterpriseConsole.

AdministratorComments

“comment sent”

Event Description: An administrator has issued a comment. Comments aregenerated at runtime and can be associated with a particularjob.

Event Class: AutoSys_ Comment


AutoSys Event: COMMENT




Events and Rules

4–22 Version 1.0

Database Status

“lost DB connection”

Event Description: A database connection problem occurred when a remote agentwas trying to send an event to the database.



AutoSys Event: DATABASE_COMM


Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than once in the last 24 hours, display the“multiple db comm failures” message on the Tivoli/EnterpriseConsole.

“fatal DB error”

Event Description: A fatal AutoSys database problem has occurred.



AutoSys Event: DB_PROBLEM


Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than once in the last 24 hours, display the“multiple db problems” message on the Tivoli/Enterprise Con-sole.


Events and Rules


Enterprise E

ventM

anagement

“DB failover occurred”

Event Description: AutoSys has rolled over from dual-server to single-servermode.



AutoSys Event: DB_ROLLOVER


Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than once in the last 24 hours, display the“multiple db rollovers” message on the Tivoli/EnterpriseConsole.

Event Processor

“event processor stopped”

Event Description: The event processor has been manually shut down.



AutoSys Event: STOP_DEAMON




Events and Rules

4–24 Version 1.0

“shadow event processor failed”

Event Description: A shadow event processor has failed. This may mean that thethird machine for resolving contentions between two eventprocessors cannot be reached and the event processor isshutting down or that there are other event processor take overproblems.



AutoSys Event: EP_HIGH_AVAIL


Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than once in the last 24 hours, display the“multiple shadow EP failure” message on the Tivoli/EnterpriseConsole.

“event processor failover occurred”

Event Description: The shadow event processor is taking over processing.



AutoSys Event: EP_ROLLOVER


Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than once in the last 24 hours, display the“primary failover to shadow” message on the Tivoli/EnterpriseConsole.


Events and Rules


Enterprise E

ventM

anagement

“event processor terminated”

Event Description: The primary event processor has shut down.



AutoSys Event: EP_SHUTDOWN


Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than once in the last 24 hours, display the“sole event processor failure” message on the Tivoli/EnterpriseConsole.

“AutoSys event processing error”

Event Description: An event processor had an error while processing an event.



AutoSys Event: EVENT_HDLR_ERROR




Events and Rules

4–26 Version 1.0

AutoSys VersionMismatch

“AutoSys version mismatch”

Event Description: There is an AutoSys version mismatch between the event pro-cessor and a remote agent.



AutoSys Event: VERSION_MISMATCH



Event Queue

“AutoSys event queue error”

Event Description: An event was not able to be marked as processed.



AutoSys Event: EVENT_QUE_ERROR


Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than once in the last hour, display the “jobstuck in queue” message on the Tivoli/Enterprise Console.


Events and Rules


Enterprise E

ventM

anagement

UNIX Processes

“Unix process fork failed”

Event Description: The remote agent was unable to start the user commandbecause it was unable to get a process slot on the machine.



AutoSys Event: FORKFAIL


Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than once in the last hour, display the “mul-tiple fork failures” message on the Tivoli/Enterprise Console.

Disk Space

“insufficient disk space”

Event Description: There is an alarm indicating that there is a resource relatedproblem, such as insufficient disk space for a job to start.



AutoSys Event: RESOURCE


Correlation Activity: Display message on the Tivoli/Enterprise Console. If this eventhas occurred more than once in the last hour, display the “lowon diskspace” message on the Tivoli/Enterprise Console.


Events and Rules

4–28 Version 1.0

Tivoli/Sentry EventsThe following table describes the events and rules that Tivoli/Sentryuses when monitoring AutoSys resources. The table is organizedaccording to the Tivoli/Sentry monitor that sends the event to theTivoli/Enterprise Console.

Since Tivoli/Sentry messages follow a standard format, thesemessages are not reproduced in the table. The following is an exampleof a Tivoli/Sentry message:

Sentry AutoSys Remote Monitors/Daemon status on host noonanMon 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: A host (main machine, shadow machine, or job executionmachine) is unavailable.

Event Class: AutoSys_via_Sentry2_0_host


Correlation Activity: Check for previous CRITICAL events of this type. If there areany, increase the event’s repeat count.

Events and Rules


Enterprise E

ventM

anagement

Host is available

Event Description: A previously unavailable host (main machine, shadowmachine or job execution machine) is now available.

Event Class: AutoSys_via_Sentry2_0_host


Correlation Activity: Close related AutoSys_via_Sentry2_0_host events in theTivoli/Enterprise Console.

Event Processor LogFile Size

> 8 MB

Event Description: The event processor log file size is greater than 8 MB.

Event Class: AutoSys_via_Sentry2_0_filesize


Correlation Activity: Check for any previous CRITICAL or FATAL events of thistype. If there are any, increase that event’s repeat count. Checkfor any previous WARNING events of this type. If there areany, close the event.

> 5 MB



Event Severity: SEVERE

Correlation Activity: Check for any previous SEVERE events of this type. If thereare any, increase that event’s repeat count. Check for any previ-ous WARNING, CRITICAL, OR FATAL events of this type. Ifthere are any, close the event.


Events and Rules

4–30 Version 1.0

> 3 MB




Correlation Activity: Check for any previous WARNING events of this type. If thereare any, increase that event’s repeat count. Check for any previ-ous SEVERE, CRITICAL, OR FATAL events of this type. Ifthere are any, close the event.

< 3 MB

Event Description: The event processor log file size has decreased below 3 MB.



Correlation Activity: Close related CRITICAL, FATAL, SEVERE, or WARNINGevents in the Tivoli/Enterprise Console.



Tasks and Jobs forA

utoSys

5Tasks and Jobs for AutoSys

Tivoli/Plus for AutoSys provides several tasks that allow you to runAutoSys jobs on multiple machines and operating systems. Thesetasks are ready to be executed as soon as you have installed yourTivoli/Plus for AutoSys module. Simply double-click on the task iconto execute the AutoSys job. You can modify the default executioncharacteristics of a particular job, such as where the output of a job isdisplayed and on which machines the job will run. You may alsospecify whether a job runs serially on each machine, in parallel on allmachines, or staged in groups of machines.

5

Tivoli/Plus for AutoSys Jobs

5–2 Version 1.0

Tivoli/Plus for AutoSys JobsThe following table lists the AutoSys jobs and reports that can becustomized and executed with Tivoli/Plus for AutoSys. Double-clickon the task icon to run the AutoSys job.


Job Description Icon

Starts the main event processor with theoption of starting with or without theshadow event processor.

Stops the main event processor with theoption of stopping the shadow eventprocessor.

Starts the primary or any bundled dataserver in single or dual mode.

Stops the primary or any bundled dataserver in single or dual mode.

Starts the Tivoli/Enterprise Console eventadapter for AutoSys.

For information on installing the eventadapter, refer to “Installing the EventAdapter for AutoSys” on page 4-5.



Tasks and Jobs forA

utoSys

Stops the Tivoli/Enterprise Consoleevent adapter for AutoSys.

Prints job reports on the AutoSys server.You can specify whether the report bedetailed or a summary. You can alsospecify whether the report is displayed onthe screen or sent to a specific printer.

Allows you to edit the configurationparameters you specified when installingthe Tivoli/Plus for AutoSys module (see“Installing from the Desktop” onpage 1-4) and the Tivoli/EnterpriseConsole event adapter for Autosys (see“Installing the Event Adapter forAutoSys” on page 4-5).

The name of this job’s icon includes theserver on which the Tivoli/Plus forAutoSys module is installed. Forexample,AutoSys_setup@indigo.


Running an AutoSys Job and Saving the Output

5–4 Version 1.0

Running an AutoSys Job and Saving the OutputAll Tivoli/Plus for AutoSys jobs can be run immediately afterinstallation. You can run these jobs from the desktop only.

To run an AutoSys job with the default execution characteristics:

—OR—Double-click onthe icon.

Use the icon’s pop-up menu.



Tasks and Jobs forA

utoSys

If Tivoli/Plus for AutoSys requires further information to execute thejob, a pop-up window appears prompting you for the information.Online help is available to assist you in completing these windows.

Where appropriate, apop-up window assists youin supplying additional in-formation.

Output is displayed in anoutput window.


5–6 Version 1.0

The job’s output is displayed in an output window. To save the job’soutput to a file:

1. Select theSave to File... button to display theSave Job Outputdialog box.

2. Enter the name of the machine on which to save the output file intheOn Host field.

3. Enter the name of the output file that will contain the job’s output.

4. Select theSave & Close button to save the output of the job tothe file you specified.

You can also use theModify job... option of the job icon’s pop-upmenu to specify that the output be sent to a file.

Modifying an AutoSys Job


Tasks and Jobs forA

utoSys

Modifying an AutoSys JobYou can modify the execution characteristics of a job for each time thejob is run or for one particular job only.

Modifying for All Future Executions of the JobUse the following steps to modify a job for each time it is run:

1. Select theModify job... option from the task's pop-up menu.

Be sure to specifyon which man-aged nodes andprofile managersthe job will run.


5–8 Version 1.0

2. Make the necessary changes in theEdit Job window. Online helpis available to assist you.

Note: Be sure to specify on which managed nodes and profilemanagers the job will run.

3. Click on theChange & Close button when finished.



Tasks and Jobs forA

utoSys

Modifying for a Single Execution of the JobUse the following steps to modify a job for only a single execution ofthe job. The next time you run the same job, it will return to the defaultexecution characteristics.

1. Select theRun on selected subscribers... option from the jobicon’s pop-up menu.

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

3. Click on theExecute button when finished.

Be sure to specifyon which managednodes and profilemanagers the jobwill be run thistime.


5–10 Version 1.0

Tivoli/Plus for AutoSys User’s Guide Index–1

Index

Aactivating Tivoli/Plus icons 1-14authorization role 1-2AutoSys

installing 2-9all platforms 2-10single platform 2-12

starting 1-18AutoSys custom events 4-11– 4-27

Ccommand line installation 1-14commands

winstall 1-14wsupport v

Configure Tivoli/Enterprise Console forAutoSys Events window 4-3

configuring file packages 2-2– 2-8for UNIX platforms 2-2icons for 2-2

conventions, typeface vcorrelating events 4-10customer support, contacting v

Ddesktop installation 1-4dialogs

SeewindowsDistribute Profiles window 3-4documents, related to this guide iv

EEdit Job Window 5-7event adapter

installing 4-5running 4-9

event correlation 4-10event management 4-1– 4-30event messages

AutoSys custom 4-11– 4-27Tivoli/Sentry 4-28– 4-30

eventsAutoSys custom

administrator comments 4-21AutoSys version mismatch 4-26database status 4-22disk space 4-27event processor 4-23event queue 4-26job duration 4-19job heartbeats 4-20job status 4-11UNIX processes 4-27

correlating 4-10Tivoli/Sentry

event processor log file size 4-29host status 4-28

Execute Task window 5-9

FFile Browser window 1-6file packages

distributingSeeinstalling AutoSysfile size 3-9file system

monitor 3-9

Index–2 Version 1.0

Ggetting started 1-1– 1-19

Hhardware requirements 1-3host status 3-8

Iicons

activating 1-14AutoSys application 1-15for AutoSys jobs 5-2for configuring file packages 2-2for installing AutoSys 2-9for monitored resources 3-7for monitors 3-2, 3-7plus symbol 1-15Sentry indicator 3-6

Install AutoSys FilePacks window 2-10,2-12

Install Options window 1-10, 4-8Install Product window 1-5, 1-8, 4-6,

4-9installing AutoSys 2-9

all platforms 2-10single platform 2-12

installing AutoSys event adapter 4-5installing Tivoli/Plus for AutoSys

from the desktop 1-4requirements for 1-2– 1-3

Jjobs

AutoSys 5-2list of 5-2

modifying 5-7running 5-4saving output 5-4, 5-6

Llaunching AutoSys 1-18license key 1-2

Mmachine requirements 1-2, 1-3managing events 4-1– 4-30modifying jobs 5-7monitored resources

file size 3-9host status 3-8icons for 3-7list of 3-7viewing 3-6

monitoring resources 3-1– 3-9monitors

customizing 3-5distributing 3-3icons for 3-2using 3-2– 3-5

Pprerequisite documents, to this guide ivproblem report, TME viprocedures

configuring file packagesfor UNIX platforms 2-2

customizing monitors 3-5distributing monitors 3-3installing AutoSys 2-9

all platforms 2-10

Tivoli/Plus for AutoSys User’s Guide Index–3

single platform 2-12modifying

jobs 5-7saving ouput 5-6starting

a module 1-16AutoSys 1-18

using monitors 3-2viewing monitored resources 3-6

Product Install window 1-12, 1-13

Rrelated documents, to this guide ivrequirements for installation

Seeinstalling Tivoli/Plus for AutoSys,requirements for

resource monitoring 3-1– 3-9rules 4-10– 4-30running

AutoSys jobs 5-4the AutoSys event adapter 4-9

Ssaving output 5-6Sentry Indicator Collection window 3-6Setup AutoSys Client FilePackage window

2-3software

distribution 2-1– 2-13requirements 1-2

startinga module 1-16AutoSys 1-18

Subscribers window 2-11, 2-13

Ttasks

See jobs 5-2Tivoli/Courier, configuring file packages

2-2– 2-8for UNIX platforms 2-2icons for 2-2

Tivoli/Plusplus symbol 1-15unique features 1-15

Tivoli/Plus for AutoSysmodule icon 1-15starting 1-16

Tivoli/Sentry events 4-28– 4-30See also events, Tivoli/Sentry 4-28

Tivoli/Sentry, monitorsSee monitors 3-2

TivoliPlus for AutoSys System window1-18, 1-19

TivoliPlus window 1-17TME

desktop window 1-4, 1-16problem report vi

TME Desktop window 4-5typeface conventions v

Uusing monitors 3-2– 3-5

Wwindows

Configure Tivoli/Enterprise Console forAutoSys Events 4-5

Distribute Profiles 3-4Edit Job 5-7Execute Task 5-9File Browser 1-6

Index–4 Version 1.0

Install AutoSys FilePacks 2-10, 2-12Install Options 1-10, 4-8Install Product 1-5, 1-8, 4-9Product Install 1-12, 1-13Sentry Indicator Collection 3-6Setup AutoSys UNIX Client FilePack

2-3Subscribers 2-11, 2-13Tivoli/Plus for AutoSys System 1-18,

1-19TivoliPlus 1-17TME desktop 1-4, 1-16, 4-5

winstall command 1-14wsupport command v