autosys user guide

8/12/2019 Autosys user guide

1/501

PLATINUM

AutoSysUser Guide for UNIX

Version 3.4


2/501

Title and Publication Number

PLATINUM Publication Number: ATS-U-342-UG00-01

Printed: December, 1997

Information in this guide is subject to change without notice and does not constitute acommitment on the part of PLATINUM technology, inc.It is supplied on an as is basiswithout any warranty of any kind, either explicit or implied. Information may be changedor updated in this guide at any time.

Copyright Information

AutoSys is copyright 1993 - 1997 by PLATINUM technology, inc.and its subsidiaries. Thisguide is copyright 1993 - 1997 by PLATINUM technology, inc., and its subsidiaries and

may not be reproduced in whole or in part, by any means, without the written permissionof PLATINUM technology, inc. and its subsidiaries.

Names marked or and other company and product names may be trademarks orregistered trademarks of their respective vendors or organizations.

Mailing Address

PLATINUM technology, inc.1815 South Meyers RoadOakbrook Terrace, Illinois60181-5235


3/501

PLATINUM AutoSys User Guide for UNIX iii

Table of Contents

Preface

Philosophy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviiContacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xviii

Whats New . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii

Year 2000 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii

PLATINUM ProVision Common Services Integration . . . . . . . . . . . . . . . xxii

Reporting using InfoReports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxii

ServerVision Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiiiAutoSys/Connect Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiii

Bundled Sybase System 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv

Security Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxiv

Event Processor Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .xxiv

Configuration File Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv

Time Zone Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxv

Set Append or Overwrite Behavior for Standard Files . . . . . . . . . . . . . . xxviHewlett-Packard IT/Operations Support . . . . . . . . . . . . . . . . . . . . . . . . .xxvi

User-configurable Title Bar and Icon Text . . . . . . . . . . . . . . . . . . . . . . . xxvii

Expanded Number of Entries in config.EXTERNAL File . . . . . . . . . . . . xxvii

AutoSys Command Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxvii

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxix

Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xxx

1 Introduction to AutoSysAutoSys Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

Defining Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

Event Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

Event Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6


4/501

iv PLATINUM AutoSys User Guide for UNIX

Table of Contents

Remote Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7Example Scenario on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Interface Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

AutoSys Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

AutoSys Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12Basic AutoSys Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Extending AutoSys Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16

2 AutoSys Security Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Security on Events Sent by Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Security on Events Sent by the Event Processor . . . . . . . . . . . . . . . . . . . 2-5

System-Level Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

AutoSys Database Field Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Job Definition Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Remote Agent Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

AutoSys User and Database Administrator Passwords . . . . . . . . . . . . . 2-10

AutoSys Job-Level Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

AutoSys Job Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

AutoSys User Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

AutoSys Permission Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

Job Permissions and Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

AutoSys Superuser Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15

Edit Superuser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-15Exec Superuser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16

Restricting Access to AutoSys Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Remote Agent Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-18


5/501

Table of Contents

PLATINUM AutoSys User Guide for UNIX v

3 AutoSys JobsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3

Job Types and Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-3

Basic Job Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-4

Command Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5

Box Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6

File Watcher Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7

Basic Job Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8Command Job Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-8

File Watcher Job Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9

Box Job Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9

Job States and Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Example State Diagram - Simple Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . 3-12

Example State Diagram - Box Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Starting Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15

Starting Parameters and Boxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-16

Date/Time Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

Job Dependencies Related to Job Status . . . . . . . . . . . . . . . . . . . . . . . . 3-18

Event Processors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22

Event Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22

Job Dependencies Based on Exit Codes . . . . . . . . . . . . . . . . . . . . . . . . 3-25

Job Dependencies Based on Global Variables . . . . . . . . . . . . . . . . . . . 3-28

Job Run Numbers and Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29

Defining Jobs in AutoSys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-30

AutoSys Graphical User Interface Components . . . . . . . . . . . . . . . . . . 3-31

4 Job Attributes

Job Attributes and Job Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3Using JIL to Create a Job Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3

Using the GUI to Create a Job Definition . . . . . . . . . . . . . . . . . . . . . . . . . .4-4

Chapter Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4

Essential Job Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-5

Attributes Common to All Job Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-5

Command Jobs Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-6


6/501

vi PLATINUM AutoSys User Guide for UNIX

Table of Contents

File Watcher Job Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9Box Job Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9

Optional Job Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Common Job Starting Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10

Common General Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Command Job Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

File Watcher Job Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25

Box Job Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26Date and Time Attributes and Time Changes . . . . . . . . . . . . . . . . . . . . . . . . 4-27

The Time Change . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27

AutoSys Behavior During Time Change . . . . . . . . . . . . . . . . . . . . . . . . . 4-29

5 Box Job Logic Basic Box Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Default Box Job Behavior . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3When you Should Not Use a Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

What Happens when a Box Runs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4

Box Job Attributes and Terminators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Attributes in a Box Job Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Attributes in a Job Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Time Conditions in a Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Force Starting Jobs in a Box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

How Job Status Changes Affect Box Status . . . . . . . . . . . . . . . . . . . . . . . 5-9

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Advanced Conditions in Box Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

Default Box Success and Box Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Explicit Box Success and Box Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Using the Box Terminator Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16Using the Job Terminator Attribute . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17

Advanced Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18


7/501


8/501

viii PLATINUM AutoSys User Guide for UNIX

Table of Contents

Deleting a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13Deleting a Box Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

Specifying One-Time Job Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

Setting Job Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15

Example JIL Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-16

8 The Graphical Calendar Facil ity

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3Scheduling Jobs with Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

Starting the Calendar Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Calendar Facility Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Calendar Definition Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6

Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

Calendar Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

Navigation Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12Creating a Simple Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14

Dates Prior to Todays Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-15

Calendar Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16

Term Calendar Rule Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17

Rule Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18

Examples of Date Selection Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20

Rescheduling Rule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22

Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24

Term Calendar Viewer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25

Combining Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27

Printing Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28

Import/Export File Name Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28

Importing Calendar Text Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-28Exporting Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30

Customizing the Calendar Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-30

Font Selection Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32

Object Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-33

Date Range . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34

Window Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34


9/501

Table of Contents

PLATINUM AutoSys User Guide for UNIX ix

Print Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35Calendar Title bar Text and Icon Text . . . . . . . . . . . . . . . . . . . . . . . . . . 8-35

9 Load Balancing and Queuing JobsReal Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3

Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3

Defining Machines to AutoSys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-3

Specifying Machine Load (max_load) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-5Specifying Relative Processing Power (factor) . . . . . . . . . . . . . . . . . . . . . .9-6

Using max_load and factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-6

Machine Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-7

Defining a Real Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-8

Deleting Real Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9

Defining a Virtual Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9

Deleting Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-10Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11

Force Starting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14

Load Balancing Using ServerVision . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14

Testing the Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-17

ServerVision Monitoring and Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18

Queuing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18

Queuing and Simple Load Limiting . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19

Queuing with Priority . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-20

SubsetsIndividual Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22

Multiple Machine Queues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24

User-Defined Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-25

10 The Operator ConsoleIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4Alarm Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4

InfoReports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5

Operator Console Screens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7

Starting the Operator Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7


10/501

x PLATINUM AutoSys User Guide for UNIX

Table of Contents

Job Activity Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-8Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-9

Job List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-10

Currently Selected Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-11

Starting Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-13

Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-14

Control Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-14

Resizing Regions of the Job Activity Console . . . . . . . . . . . . . . . . . . . . 10-23Job Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23

Specifying a Job by Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-24

Specifying Jobs by Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26

Specifying Jobs by Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-27

Sorting the Specified Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-28

Setting the Job Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-29

Changing the Console Clock Perspective . . . . . . . . . . . . . . . . . . . . . . . . . .10-29Alarm Manager Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29

Alarm Manager Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-31

Alarm List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-31

Currently Selected Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-32

Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33

Alarm Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-35

Select by Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-36

Select by State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-36

Select by Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-37

Customizing the Operator Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-37

Refresh Time Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-38

Alarm Poll Time Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-38

Changing Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-39Freeze Frame at Start Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-39

Font Selection Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-40

Label Font Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-40

List Font Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-40

Object Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-41

Job List Column Widths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-44

Operator Console Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-45


11/501

Table of Contents

PLATINUM AutoSys User Guide for UNIX xi

Default Report Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-45Alarm List Column Width . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-45

Operator Console Title bar Text and Icon Text . . . . . . . . . . . . . . . . . . 10-46

User-Configurable Action Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-46

Console Clock Perspective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-49

11 Monitoring and Reporting Jobs

About Monitors and Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-3Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4

Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4

Defining Monitors and Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-4

Using the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5

Using JIL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5

Chapter Organization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6

Essential Monitor/Report Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7Common Essential AttributesGeneral . . . . . . . . . . . . . . . . . . . . . . . . . 11-7

Common Essential AttributesEvents . . . . . . . . . . . . . . . . . . . . . . . . . . 11-7

Essential Report Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-10

Optional Monitor/Report Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11

Optional Monitor Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-11

Optional Report Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12

Defining Monitors and Reports using the GUI . . . . . . . . . . . . . . . . . . . . . . 11-12

The Monitor/Browser Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-12

Defining an Example Monitor and Report . . . . . . . . . . . . . . . . . . . . . . 11-15

Defining Monitors and Reports using JIL . . . . . . . . . . . . . . . . . . . . . . . . . . 11-19

Running a Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-21

Customizing the Monitor/Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-22

Database Connection Time-out Interval . . . . . . . . . . . . . . . . . . . . . . . 11-22Monitor/Browser Title bar Text and Icon Text . . . . . . . . . . . . . . . . . . 11-23

12 Maintaining AutoSysMaintaining the Event Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3

Starting the Event Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3

Monitoring the Event Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-6


12/501

xii PLATINUM AutoSys User Guide for UNIX

Table of Contents

Stopping the Event Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7Shadow Event Processor Rollover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8

Running AutoSys in Test Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-10

AutoSys Maintenance Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-12

Backing up AutoSys Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-13

Restoring AutoSys Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15

AutoSys Database Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-16

Event Server Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-16Database Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-18

General Database Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-19

Daily Database Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-20

DBMaint Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-20

Event Server Rollover Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-22

Event Server Crash . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-23

Synchronizing the Event Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-23Improving Database Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-24

Improving Sybase Database Performance . . . . . . . . . . . . . . . . . . . . . .12-24

Improving Oracle Database Performance . . . . . . . . . . . . . . . . . . . . . .12-25

Maintaining Bundled Sybase SQL Servers . . . . . . . . . . . . . . . . . . . . . . . . . .12-27

Sybase Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-27

Sybase Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-28

Default Sybase Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-28

Starting Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-30

Stopping Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-31

Accessing Sybase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-32

Identifying Processes Connected to the Database . . . . . . . . . . . . . . .12-33

Displaying the Database Date and Time . . . . . . . . . . . . . . . . . . . . . . .12-34

Bundled Sybase Backup and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . 12-34

13 Configuring AutoSysAutoSys Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

Sample Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-4

Configuration File Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-9

Database Time-out Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-10

Cross-Instance Database Connections . . . . . . . . . . . . . . . . . . . . . . . . .13-11


13/501

Table of Contents

PLATINUM AutoSys User Guide for UNIX xiii

Database Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-11Event Processor Cascading Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12

Machines to Check for Running Event Processors . . . . . . . . . . . . . . . 13-13

Third Machine for Event Processor Contention . . . . . . . . . . . . . . . . . 13-14

Event Processor Log Disk Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15

Internal Database Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15

Event Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-16

Heartbeats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-17Remote Agent Log Files Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18

File Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-18

SNMP Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-21

HP OpenView IT/Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-27

Number of Restart Attempts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-27

Calculating the Wait Time Between Restarts . . . . . . . . . . . . . . . . . . . . 13-28

Method of Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-29KILLJOB Signals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-30

Port Number for Remote Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-31

Z/Team Job Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-31

Instance Wide Append Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-32

Enabling PLATINUM Event Management and Data Exchange . . . . . 13-33

Inetd Job Starting Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-34

The auto.profile File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-35

Sample Default auto.profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-36

Remote Agent Database Connection Settings . . . . . . . . . . . . . . . . . . 13-37

Modifying Remote Agent Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-38

Remote Agent Socket Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-38

Running Two AutoSys Versions of Remote Agents . . . . . . . . . . . . . . 13-39

Configuring Remote Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-40Configuring Event Processor Authentication . . . . . . . . . . . . . . . . . . . . 13-41

Client-Side Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-42

Configuring ServerVision Monitoring and Reporting . . . . . . . . . . . . . . . . 13-43

Library Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-43

svload Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-43

ServerVision Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . 13-44


14/501

xiv PLATINUM AutoSys User Guide for UNIX

Table of Contents

ServerVision Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-44Monitoring Job Resource Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-45

User-Defined Alarm Callbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-46

14 TroubleshootingIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

Event Server Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3

Event Server is Down (Sybase) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3Sybase Deadlock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-6

Not Enough User Connections (Bundled Sybase) . . . . . . . . . . . . . . . . . 14-7

archive_events Fails (Bundled Sybase) . . . . . . . . . . . . . . . . . . . . . . . . . . 14-9

Event Server Will Not Start (Bundled Sybase) . . . . . . . . . . . . . . . . . . . . 14-11

Event Processor Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-11

Event Processor is Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-12

Event Processor Will Not Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-12Remote Agent Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-13

Remote Agent Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-13

Remote Agent Will Not Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-14

Remote Agent Will Start - Command Will Not Run . . . . . . . . . . . . . . . 14-17

Remote Agent Starts, Command RunsNo RUNNING Event is Sent .14-20

xql Will Not Start (Sybase Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-23

Remote Agent Not Found . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-24

Jobs Run Twice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-25

Job Failure Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14-26

Jobs Run Only From the Command Line . . . . . . . . . . . . . . . . . . . . . . .14-26

A Integrating AutoSys with Zeke and AutoSys/Team AgentIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Definition of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Related Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

Job Scheduling for the Enterprise . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

Installing and Configuring for Enterprise Job Scheduling . . . . . . . . . . . . . . . A-6

Install the Basic AutoSys Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6

Stop the Event Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

Configure the AutoSys Machine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7


15/501

Table of Contents

PLATINUM AutoSys User Guide for UNIX xv

Initializing the Communication Components . . . . . . . . . . . . . . . . . . . . . . . . A-13License Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14

Restart the Event Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15

About the oasis_broker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15

AutoSys and Zeke Cross-Platform Dependencies . . . . . . . . . . . . . . . . . . . . A-16

Job Scheduler Interdependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-17

Notation for Cross-Platform Job Dependencies . . . . . . . . . . . . . . . . . . A-18

Naming Conventions for AutoSys/Zeke Cross-Platform Jobs . . . . . . . A-19Running AutoSys Jobs on the Team Agent . . . . . . . . . . . . . . . . . . . . . . . . . A-20

Running Jobs on Team Agent Managed Machines . . . . . . . . . . . . . . . A-21

Defining Team Agent Machines to AutoSys . . . . . . . . . . . . . . . . . . . . . A-22

Team Agent Machine in an AutoSys Job Definition . . . . . . . . . . . . . . . A-23

Database Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-23

Logs and Trace Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-23

Zeke and Team Agent Job Statuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-24Unsupported Attributes for Zeke or Team Agent Jobs . . . . . . . . . . . . . . . . A-24

Cross-Platform Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-26

Index


16/501


17/501

PLATINUM AutoSys User Guide for UNIX xvii

Preface

Welcome to the world of AutoSys, the scheduling and operations

automation software for distributed computing environments. Thisguide describes how to use AutoSys to define and run jobs.

This guide is intended for users who will be responsible for defining jobsto AutoSys, and monitoring and managing these jobs. It assumesfamiliarity with the UNIX operating system, as well as the operatingsystem on which the jobs will run. It assumes that you have already

installed AutoSys using theAutoSys Installation and Getting Started Guidefor UNIX.

Philosophy 0PLATINUM technology, inc., is the leading vendor of open enterprisesystems management (OESM) products, which help organizationsmanage all the hardware and software components of the multiplatform,multi-operating system, multivendor environment called the openenterprise environment (OEE).

By leveraging its expertise in relational technology, PLATINUM offersproducts and services that increase the efficiency of individual computingsystems and databases, as well as the interoperability of these systemsand databases in distributed environments.
http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/


18/501

xviii PLATINUM AutoSys User Guide for UNIX

Preface

Contacting Technical Support

Contacting Technical Support 0

You can contact us with any questions or problems you have. You will bedirected to an experienced software engineer familiar with PLATINUM

AutoSys.

To send Email to PLATINUM Technical Support, use:

Internet [email protected]

IBM MAIL Exchange USRWNPSN

To contact PLATINUM Technical Support, use:

USA or Canada, toll free 800-833-PLAT (7528)IBM Software Mall PLATSM4CompuServe GO PLATINUM

For product assistance or information, contact:USA or Canada, toll free 800-442-6861Illinois 630-620-5000FAX 630-691-0708 or 630-691-0406Internet [email protected]

World Wide Web http://www.platinum.com

Our Mailing Address is:

PLATINUM technology, inc.1815 South Meyers RoadOakbrook Terrace, IL 60181-5235

About This Guide 0The PLATINUM AutoSys User Guide for UNIXexplains how to define, run,monitor, manage, and control AutoSys. It has been designed to presentinformation in a natural order so that basic concepts are discussed priorto more advanced topics.


19/501

PLATINUM AutoSys User Guide for UNIX xix

Preface

About This Guide

This guide assumes that the appropriate PLATINUM AutoSyscomponents have been installed at your site. The instructions forinstalling the product are in theAutoSys Installation and Getting StartedGuide for UNIX.

Ch.No. Chapter Name Content Description

1 Introduction to AutoSys Describes AutoSys and its systemarchitecture, system components,events, alarms, and utilities. It alsoincludes descriptions of basic AutoSysconfigurations as well as an overview ofbasic functionality.

2 AutoSys Security Provides information about

permissions, superusers, and security.

3 AutoSys Jobs Describes AutoSys job types andprovides information about basic jobattributes, starting parameters, and jobstates.

4 Job Attributes Describes the various attributes used to

define jobs in AutoSys. It also discussesessential and optional job attributes,which govern what a job does andwhen and where it will run.

5 Box Job Logic Explains how Box Jobs work, includingdefault box behavior and how tooverride the default behavior. It also

explains what types of jobs should andshould not be placed in a box. Toillustrate box logic, numerousexamples of Box Jobs are provided.
http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/


20/501

xx PLATINUM AutoSys User Guide for UNIX

Preface

About This Guide

6 Defining AutoSys JobsUsing the GUI

Describes how to use the AutoSysGraphical User Interface (GUI), andhow to use the Job Definition dialog todefine a simple Command Job, a File

Watcher Job, and a dependent

Command Job. It describes definingAutoSys Box Jobs, as well as changingand deleting a job. It also explains howto set time dependencies.

7 Defining Jobs Using JIL Describes how to use the AutoSys JobInformation Language or JIL to define asimple Command Job, a File Watcher

Job, and a dependent Command Job. Itdescribes defining AutoSys boxes, as

well as changing and deleting a job.Also provides an example JIL script.

8 The Graphical CalendarFacility

Describes the AutoSys GraphicalCalendar Facility and how to use it tocreate, view, and maintain AutoSys

calendars. It also describes how toaccess and use the various features ofthe Calendar Facility, such aspreviewing a calendar before applyingits dates and applying customized rulesto a calendar. Customizing theCalendar Facility is also covered.

9 Load Balancing andQueuing Jobs

Describes the use of real and virtualmachines in the AutoSys environment.It also provides information aboutload balancing jobs across multiplemachines, as well as queueing jobs toreal and virtual machines.



21/501

PLATINUM AutoSys User Guide for UNIX xxi

Preface

About This Guide

10 The Operator Console Describes the AutoSys OperatorConsole and how to monitor andcontrol job activity in real-time. It alsodescribes how to access and use the

various features of the Console, such as

reviewing and reporting on anyAutoSys job, as well as using the AlarmManager. Customizing the OperatorConsole is also covered.

11 Monitoring and ReportingJobs

Describes how to use the GUI or JIL todefine AutoSys monitors and browsers(reports) using essential and optional

monitor and browser attributes.

12 Maintaining AutoSys Describes basic AutoSys maintenanceand how to maintain a bundled Sybasedatabase.

13 Configuring AutoSys Describes the AutoSys configurationfile and how to modify the tunable

parameters in the file to control thebehavior of AutoSys.

14 Troubleshooting Provides useful information abouttroubleshooting the primary AutoSyscomponents.

A Integrating AutoSys with

Zeke and AutoSys/Team Agent

Explains how to set up and implement

these enterprise-wide scheduling withAutoSys, Zeke, and Team Agentcomponents.

Index Helps you locate information withinthis manual.



22/501

xxii PLATINUM AutoSys User Guide for UNIX

Preface

Whats New

Whats New 0

PLATINUM AutoSys Version 3.4 offers all the functions available inVersion 3.3, plus the new features in this section.

Year 2000 Support 0

The AutoSys 3.4.2 GUIs and command-line interfaces now support thespecification and display of four-digit years. If you enter a two-digit year,

AutoSys saves the setting to the database as a four-digit year using a datewindow rule. If you enter 79 or less, AutoSys prepends 20, and if youenter 80 or greater, AutoSys prepends 19. That is, if you enter 79, itbecomes 2079, and if you enter 80, it becomes 1980.

PLATINUM ProVision Common Services Integration 0

You can enable AutoSys to send events to the PLATINUM Event Managerand Data Exchange. If enabled, AutoSys will send events for every

AutoSys job to the Event Manger. If you have installed the PLATINUMProVision common services, you can view these events with thePLATINUM Director. Enabling Data Exchange instructs AutoSys to writejob definition and job history information to the POEMS common

services repository.

Reporting using InfoReports 0

AutoSys bundles an InfoReports Viewer and a number of reports withdetails on AutoSys jobs that you can view using the InfoReports GUI.

Access these reports by defining and clicking on one of theuser-configurable action in the Operator Console.

The following types of reports are available:

Job List

This report allows you to select the list of jobs to be reported on, or

report on all jobs in the database.


23/501

PLATINUM AutoSys User Guide for UNIX xxiii

Preface

Whats New

Job FindThis report allows you to enter a pattern for the job name and reporton all jobs that match the pattern.

Last Run

This report allows you to enter the job name and get informationregarding the last run of the specified job.

Last nRun

This report allows you to enter the job name and get information onthe nth to last run of the job.

You can also configure the InfoReports Viewer to print the reports.

ServerVision Integration 0

You can use the ServerVision GUIs to monitor the real-time resourceusage of AutoSys jobs. This integration allows you to view AutoSys jobsby their job name in the ServerVision GUIs. In addition, AutoSys willarchive job resource usage (CPU utilization, I/O reads and writes, andaverage memory usage) to generate reports for capacity planning and

UNIX processes auditing (charge back).

A new load balancing command, svload, can be specified in the machineattribute of an AutoSys job definition. This enables AutoSys to applymachine performance metrics monitored by ServerVision to select, atruntime, the best machine on which to run a job.

AutoSys/Connect Integration 0

Integration with AutoSys/Connect lets you communicate between manymainframe legacy scheduling products and AutoSys. You can define an

AutoSys job to conditionally start after a legacy mainframe scheduler jobcompletes. And you can use AutoSys to schedule a job on the mainframethrough your legacy scheduler. See the PLATINUM AutoSys/Connect UserGuidefor details on how to set up and use this feature.


24/501

Preface


25/501

PLATINUM AutoSys User Guide for UNIX xxv

Preface

Whats New

Configuration File Enhancements 0

These new parameters were added to the configuration file:

AutoInstWideAppend

FileSystemThreshold

AutoPems

AutoInstWideAppend

This parameter specifies whether to overwrite or append to standard errorand standard output files.

FileSystemThreshold

This parameter specifies the minimum amount of disk space that must beavailable, or the Event Processor will issue a warning. If the disk spacedrops below 8 kilobytes, the Event Processor will shut down.

AutoPems

This parameter enables AutoSys to communicate with PLATINUM EventManagement and Data Exchange.

Time Zone Setting 0

Jobs with time-based starting conditions that do not specify a time zoneare scheduled to start based on the time zone under which the EventProcessor runs. This time zone is also used to report event times with theautorepcommand.

Before you start the Event Processor, ensure that the TZ environmentvariable is set. The Event Processor references this setting to determinethe default time zone.

Preface


26/501

xxvi PLATINUM AutoSys User Guide for UNIX

Preface

Whats New

Set Append or Overwrite Behavior for Standard Files 0

You can now configure AutoSys to either overwrite or append to standarderror and standard output files. You control this behavior for each

AutoSys instance by setting the AutoInstWideAppendparameter in theAutoSys configuration file.

You can override the instance-wide setting for individual client machines

(Remote Agents) by setting the AutoMachWideAppendvariable in the/etc/auto.profilefile. You can also set a behavior for a specific job byplacing special notation as the first character in the standard error orstandard output specification.

Hewlett-Packard IT/Operations Support 0

This release of AutoSys supports HP IT/Operations Center message,application, and monitor capabilities. An AutoSys application group hasbeen provided to support key AutoSys applications from the IT/O userinterface. AutoSys provides its own console GUI which is crucial fordebugging problems that occur with AutoSys. It is recommended thatusers of AutoSys monitor IT/O messages to detect when problems haveoccurred, and then use the AutoSys console GUI to resolve the details ofthe problem. Contact your PLATINUM sales representative for versioncompatibility.

Preface


27/501

PLATINUM AutoSys User Guide for UNIX xxvii

Preface

Whats New

User-configurable Title Bar and Icon Text 0

By modifying X resources, you can customize the icon text and title bartext of the following AutoSys and AutoSys/Xpert GUIs:

Expanded Number of Entries in config.EXTERNAL File 0

The config.EXTERNALfile can contain up to 249 entries. You use this fileto implement cross-instance job dependencies within AutoSys, and toimplement cross-platform dependencies for AutoSys Zeke and Team

Agent integration.

AutoSys Command Changes 0

There are changes to the following AutoSys commands:

archive_events

autobcp

autosyslog

autosys_secure

AutoSys GUI X Resources File Name

Calendar Definition Autocal

AutoSys Operator Console Autocons

AutoSys Launcher, Monitor/Browser, and Job Definition

Autosc

AutoSys/Xpert: HostScape,JobScape, and TimeScape

Xpert

Preface


28/501

xxviii PLATINUM AutoSys User Guide for UNIX

Preface

Whats New

archive_eventsThe archive_eventscommand has the following new argument:

-snum_of_days

This option removes ServerVision audit information older than thespecified number of days from the svarchive table. The DBMaintscriptautomatically archives old data from the svarchive table.

autobcp

The autobcpcommand has two new options which allow you to specifythe source database and the target database. These both default toautosys. This is the new command syntax:

autobcp source_servertarget_serverdump_file\autosys_password[source_db_nametarget_db_name]

autosyslog

The autologcommand has been renamed to autosyslog.

autosys_secure

The autosecurecommand has been renamed to autosys_secure. In

addition, security enhancements (discussed above) were added tofacilitate security administration from both UNIX and Windows NTplatforms.

Preface


29/501

PLATINUM AutoSys User Guide for UNIX xxix

Conventions

Conventions 0

Some or all of the following conventions appear in this guide:

Symbol orType Style Represents Example

Bold a new term ...called a source object.

alternate

color

(online only) hotlinkedcross-references to othersections in this guide; if youare viewing this guide onlinein PDF format, you can clickthe cross-reference to jumpdirectly to its location

...see Chapter 3, DataMigration.

Italic words that are emphasized ...the entry afterthecurrent entry...

the titles of other documents PLATINUM GeneralApplications Guide

syntax variables COPY filename

Monospace directories, file names,command names, computercode

&HIGHLVL.SRCLIB

computer screen text, systemresponses, command linecommands

Copy file? Y/N

Monospacebold what a user types ...enter RUN APP.EXEin theApplication field

< > the name of a key on thekeyboard

Press .

choosing a command from acascading menu

File

Import

Object

Preface


30/501

xxx PLATINUM AutoSys User Guide for UNIX

Related Publications

Related Publications 0

As you use this PLATINUM AutoSys User Guide for UNIX, you might findit helpful to have these additional books available for reference:

Release Notes: AutoSys version 3.4 for UNIX, which provides importantinformation about this release. Please read this before proceeding.

AutoSys Installation and Getting Started Guide for UNIX,which describesthe basic AutoSys configurations, how to install AutoSys, includinghow to configure AutoSys components, databases, and highavailability features. In addition, this guide describes how to enterlicense keys.

AutoSys Reference Guide for UNIX,which lists the AutoSys commandsand job, machine, monitor, and report definition parameters. It also

describes system states, database tables and views, and the API.
http://atsigu.pdf/http://atsigu.pdf/http://atsrgu.pdf/http://atsrgu.pdf/http://atsrgu.pdf/http://atsigu.pdf/


31/501

PLATINUM AutoSys User Guide for UNIX 1-1

1Introduction to AutoSys

AutoSys is an automated job control system for scheduling, monitoring,

and reporting. These jobs can reside on any AutoSys-configured machinethat is attached to a network.

An AutoSys job is any single command, executable, script, or NT batchfile. Each AutoSys job definition contains a variety of qualifyingattributes, including the conditions specifying when and where a jobshould be run.

As with most control systems, there are many ways to correctly define andimplement jobs. It is likely that the way you utilize AutoSys to address

your distributed computing needs will evolve over time. As you becomemore familiar with both the features of AutoSys and the characteristics of

your own jobs, you will also refine your use of AutoSys.

However, before you install and use AutoSys, it is important to

understand the basic AutoSys system, its components, and how thesecomponents work together.

This chapter provides a brief overview of AutoSys, its system architecture,and features.

AutoSys Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Defining Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Introduction to AutoSys


32/501

1-2 PLATINUM AutoSys User Guide for UNIX

System Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Event Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Event Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

Remote Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Example Scenario on UNIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

Interface Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

AutoSys Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10AutoSys Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

Basic AutoSys Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Explanation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Extending AutoSys Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16



33/501


AutoSys Jobs

AutoSys Jobs 1

In the AutoSys environment, a jobis a single action that can beperformed on a valid AutoSys client machine. On UNIX, this action canbe any single command or shell script, and on NT, this action can be anysingle command, executable, or batch file. In addition, job definitionsinclude a set of qualifying attributes.

For information on defining, running, managing, monitoring, andreporting on jobs, see the chapters in this guide.

Defining Jobs 1

Using AutoSys utilities, you can define a job by assigning it a name andspecifying the attributes that describe its associated behavior. These

specifications make up the AutoSys job definition. These are the twomethods you can use to create job definitions:

Using the AutoSys Graphical User Interface (GUI).

Using the AutoSys Job Information Language (JIL) through acommand-line interface.

AutoSys Graphical User InterfaceThe AutoSys GUI allows you to interactively set the attributes thatdescribe when, where, and how a job should run. You create jobdefinitions using the GUI Control Panel and the dialogs you can launchfrom it. The fields in the GUIs correspond to the AutoSys JILsub-commands and attributes. In addition, from the GUI Control Panel,

you can open applications that allow you to define calendars, monitors,

and reports, and that allow you to monitor and manage AutoSys jobs.

Job Information Language

AutoSys JILis a specification language, with its own syntax, that is usedto describe when, where, and how a job should run. When you enter thejilcommand, you get the jilcommand prompt, at which you can enterthe job definitions one line at a time using this special language. When


S t C t


34/501

System Components


you exit JIL, the job definition is loaded into the AutoSys database.Alternatively, you can enter the definition as a text file and re-direct thefile to the jilcommand. In this case, the jilcommand activates thelanguage processor, interprets the information in the text file, and loadsthis information in the AutoSys database.

System Components 1The following are the main AutoSys system components:

Event Server (AutoSys database)

Event Processor

Remote Agent

In addition, AutoSys provides utilities to help you define, run, andmaintain AutoSys instances and jobs. The included utilities are platform-specific; however, all platforms include the AutoSys GUI componentsand JIL. Both the GUI and JIL allow you to define, manage, monitor, andreport on jobs.

Figure 1-1illustrates the AutoSys system components in a basicconfiguration. In addition, this figure illustrates the communication

paths between the components.


35/501


System Components


36/501

System Components


High Availability Option - Dual Event Servers

AutoSys can be configured to run using two databases, or Dual EventServers. This feature provides complete redundancy. Therefore, if youlose one Event Server due to hardware, software, or network problems,

AutoSys operations can continue on the second Event Server without lossof information or functionality.

For various reasons, database users often run multiple instances of

servers that are unaware of the other servers on the network. Whenimplementing AutoSys, the database can run stand-alone for AutoSysonly, or it can be shared with other applications.

For more information on using Dual Event Servers, see Dual Event Serversin Chapter 1, Introduction to AutoSys, of theAutoSys Installation and GettingStarted Guide for UNIX.

Event Processor 1

The Event Processor is the heart of AutoSys; it interprets and processesall the events it reads from the AutoSys database. Sometimes called theevent_demon, the Event Processor is the program, running either as aUNIX process or as a Windows NT service, that actually runs AutoSys. Itschedules and starts jobs.

After you start it, the Event Processor continually scans the database forevents to be processed. When it finds one, it checks whether the eventsatisfies the starting conditions for any job in the database. Based on thisinformation, the Event Processor first determines what actions are to betaken, then instructs the appropriate Remote Agent process to performthe actions. These actions might be the starting or stopping of jobs,

checking for resources, monitoring existing jobs, or initiating correctiveprocedures.

High Availability Option - Shadow Event Processor

AutoSys lets you set up a second Event Processor, called the ShadowEvent Processor. This second processor should run on a separatemachine to avoid a single point of failure.


System Components
http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/


37/501


System Components

The Shadow Event Processor remains in an idle mode, receiving periodic

messages (pings) from the Primary Event Processor. Basically, thesemessages indicate that all is well. However, if the Primary Event Processorfails for some reason, the Shadow Event Processor will take over theresponsibility of interpreting and processing events.

For more information on running a Shadow Event Processor, see ShadowEvent Processorin Chapter 1, Introduction to AutoSys, of theAutoSys

Installation and Getting Started Guide for UNIX.

Remote Agent 1

On a UNIX machine, the Remote Agentis a temporary process started bythe Event Processor to perform a specific task on a remote (client)machine. On a Windows NT machine, the Remote Agent is a

Windows NT service running on a remote (client) machine that isdirected by the Event Processor to perform specific tasks.

The Remote Agent starts the command specified for a given job, sendsrunning and completion information about a task to the Event Server,then exits. If the Remote Agent is unable to transfer the information, it

waits and tries again until it can successfully communicate with thedatabase.

Example Scenario on UNIX 1

The example scenario in Figure 1-2and the numbered explanations thatfollow it illustrate the interactions between the Event Server, the EventProcessor, and Remote Agents.

In the example, the following UNIX command line is to be run onWorkStation_2, at the start date and time specified in the AutoSys jobdefinition:

rm /tmp/mystuff/*


System Components
http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/


38/501

y p


Note Understanding this example will help you answer manyquestions that might arise during your experiences with AutoSys.

Note In the example above, the three primary components areshown running on different machines. Typically, the Event Processorand the Event Server run on the same machine.

ExplanationThe following numbered steps explain the interactions in the examplescenario:

1 From the AutoSys Event Server, the Event Processor reads a new event,which is a start jobevent with a start time condition that has beenmet. Then the Event Processor reads the appropriate job definition

Figure 1-2 Interaction of the Event Server, Event Processor, and Remote Agent

PROCESS

Event ProcessorDetermines Actions

Initiates Action: Startjob on machine com-mand:rm/tmp/mystuff/*

PROCESSEvent Server

Events

Job Definitions

PROCESS

Remote Agent

Receives instructions from EventProcessor

Initiates Action: Starts ChildProcess

Waits for Exit Code (from ChildProcess)

Sends Exit event back to EventServer

Local Area

WorkStation_2 PROCESS

UNIX Command

Runs UNIXCommand:rm /tmp/mystuff/*

Completes execution andexits with status

2 3

4

5

Network

1


System Components


39/501


y p

from the database and, based on that definition, determines what

action to take. In the example, it runs the rm /tmp/mystuff/*command on WorkStation_2.

2 The Event Processor communicates with the Remote Agent onWorkStation_2. As soon as the Remote Agent receives theinstructions from the Event Processor, the connection between thetwo processes is dropped. After the connection is dropped, the job will

run to completion, even if the Event Processor stops running.3 The Remote Agent performs resource checks, such as ensuring that the

minimum specified number of processes are available, then forks achild process that will actually run the specified command.

4 The command completes and exits, and the Remote Agent capturesthe commands exit code.

5 The Remote Agent communicates the event (exit code, status, etc.)directly to the Event Server. If the AutoSys database is unavailable forany reason, the Remote Agent will go into a wait and resend cycle untilit can deliver the message.

Only two AutoSys processes need to be running: the Event Processor andthe Event Server. When these two components are running, AutoSys is

fully operational. The Remote Agent is started on a client machine onceper job. As soon as the job ends and the Remote Agent sends acompletion event to the database, the Remote Agent exits.

Note The Remote Agent is started on the client machine by the EventProcessor talking to the internet daemon (inetd) on the clientmachine. For this to happen, inetdmust also be running. However,

since UNIX is responsible for starting this daemon, it is notconsidered an AutoSys process.


AutoSys Machines


40/501


Interface Components 1

To define, monitor, and report on jobs, you can use either the AutoSysGUI or AutoSys JIL. In addition, the Operator Console and its dialogsprovide a sophisticated method of monitoring AutoSys jobs in real time.

This feature lets you view all jobs that are defined to AutoSys, whether ornot they are currently active. If you purchased AutoSys/Xpert, you can usethe Xpert product to monitor, analyze and forecast (simulate) AutoSys

jobs. For information, see theAutoSys/Xpert User Guide for UNIX.

For information on interface components and defining and monitoringAutoSys jobs, see the chapters in this guide.

AutoSys Machines 1From a hardware perspective, the AutoSys architecture is composed of thefollowing two types of machines attached to a network:

Server Machine

The AutoSys server is the machine on which the Event Processorand/or the Event Server (database) reside. In a basic configuration,both the Event Processor and the Event Server reside on the samemachine.

Client Machine

The AutoSys client is the machine on which the Remote Agentsoftware resides, and where AutoSys jobs are to be run. A Remote

Agent must be installed on the server machine, and it can also beinstalled on separate physical client machines.


AutoSys Instance
http://atsxugu.pdf/http://atsxugu.pdf/http://atsxugu.pdf/http://atsxugu.pdf/


41/501


AutoSys Instance 1

An AutoSys instanceis one licensed version of AutoSys software runningas an AutoSys server with one or more clients, on a single machine or onmultiple machines. An AutoSys instance is defined by the instance ID,

which is a capitalized three-letter identifier defined by the AUTOSERVenvironment variable. An instance uses its own Event Server and EventProcessor and operates independently of other AutoSys instances.

You might want to install multiple AutoSys instances. For example, youmight want to have one instance for production and another fordevelopment. Multiple instances can run on the same machine, and canschedule jobs on the same machines without interfering or affecting theother instances.

Events 1

AutoSys is completely event-driven; that is, for a job to be activated by theEvent Processor, an event must occur on which the job depends. Forexample, a prerequisite job has completed running successfully or arequired file has been received.

Events can come from a number of sources, including the following:

Jobs changing states, such as starting, finishing successfully, etc.

Internal AutoSys verification agents, such as detected errors.

Events sent with the sendeventcommand, sent from the Send Eventdialog, the command line, or user applications.

As each event is processed, the Event Processor scans the database for jobsthat are dependent on that event in some way. If the event satisfiesanother jobs starting condition, that job is either started immediately, orif necessary, queued for the next qualified and available machine. Thecompletion of one job can cause another job to be started, and in this

way, jobs progress in a controlled sequence.


Alarms


42/501


Alarms 1

Alarmsare special events that notify operations personnel of situationsrequiring their attention. Alarms are integral to the automated use of

AutoSys. That is, jobs can be scheduled to run based on a number ofconditions, but some facility is necessary for addressing incidents thatrequire manual intervention. For example, a set of jobs could bedependent on the arrival of a file, and the file is long overdue. It is

important that someone investigate the situation, make a decision, andresolve the problem.

These are some important aspects of alarms:

Alarms are informational only. Any action to be taken due to aproblem is initiated by a separate action event.

Alarms are system messages about a detected problem.

Alarms are sent through the system as an event.

Alarms have special monitoring features to ensure they will be noticed.For more information about these features, see Chapter 10, The OperatorConsole, and Chapter 11, Monitoring and Reporting Jobs.

Utilities 1To help you define, control, and report on jobs, AutoSys has its ownspecification language called Job Information Language, or JIL, fordefining jobs, machines, monitors, and reports. This language isprocessed by the jilcommand, which reads and interprets the JILstatements that you enter and then performs the appropriate actions,

such as adding a new job definition to the database.

AutoSys also provides a set of commands that run essential utilityprograms for defining, controlling, and reporting on jobs. For example,the autorepcommand allows you to generate a variety of reports aboutjob execution, and the sendeventcommand allows you to manuallycontrol job processing.


Basic AutoSys Functionality


43/501


Additional utility programs are provided to assist you in troubleshooting,

running monitors and browsers, and starting and stopping AutoSys andits components. AutoSys also provides a database maintenance utilitythat runs daily by default.

Basic AutoSys Functionality 1The diagram in Figure 1-3and the numbered explanations that follow it

illustrate how AutoSys performs its most basic functionstarting a job(i.e., executing a command) on a client machine.

Working through this example will be very helpful for understandinghow AutoSys processes jobs.

Note In Figure 1-3, the major AutoSys components are shown as

separate entities. Typically, the Event Processor and the AutoSys EventServer are installed on the same server machine (along with a requiredRemote Agent), and other Remote Agents are installed on separateclient machines.




44/501


Explanation 1

1 The Event Processor scans the Event Server for the next event toprocess. If no event is ready, the Event Processor scans again in 5seconds.

2 The Event Processor reads from the Event Server that an event is ready.

If the event is a STARTJOB event, the job definition and attributes areretrieved from the Event Server, including the command and thepointer (full path name on the client machine) to the profile file to beused for the job. In addition, for jobs running on Windows NTmachines, the Event Processor retrieves from the database the userID(s) and password(s) required to run the job on the client machine.

Figure 1-3 Basic AutoSys Functionality

agent

Event Processor

Remote Agent

Client Job

8

5

9

1

7

6

3

4

2

Event Server(Database) connect

AutoSysClient




45/501


3 The Event Processor processes the event. If the event is a STARTJOB,

the Event Processor attempts to establish a connection with theRemote Agent on the client machine, and passes the job attributes tothe client machine.

The Event Processor sends a CHANGE_STATUS event marking in theEvent Server that the job is in STARTING state.

4 On a UNIX machine, the inetdinvokes the Remote Agent. On a

Windows NT machine, the Remote Agent logs onto the machine asthe user defined as the jobs owner, using the user ID(s) andpassword(s) passed to it from the Event Processor.

5 The Remote Agent sends an acknowledgment back to the EventProcessor indicating that it has received the job parameters. The socketconnection is terminated. At this point, the Event Processor resumes

scanning the Event Server database, looking for events to process.6 The Remote Agent starts a process and executes the command in the

job definition.

7 The Remote Agent issues a CHANGE_STATUS event marking in theEvent Server that the job is in RUNNING state.

8 The client job process runs to completion, then returns an exit code tothe Remote Agent and quits.

9 The Remote Agent sends the Event Server a CHANGE_STATUS eventcorresponding to the completion status of the job and passes back anexit code, using the communications facilities of the database.

If the return status is SUCCESS, the Remote Agent deletes the log filein its temporary file directory (usually tmp)on the client machine (ifso specified in the AutoSys configuration file on UNIX or with the

AutoSys Administrator on Windows NT).

The Remote Agent quits.


Extending AutoSys Functionality


46/501


The Event Processor, which is scanning the Event Server, sees the process

completion status, determines if there are dependent jobs, and evaluatesthe rest of the dependent jobs starting conditions. For each job found

whose remaining conditions are satisfied, the Event Processor sends aSTARTJOB command to the Event Server, which it will then process in thenext cycle.

Extending AutoSys Functionality 1

You can extend AutoSys with the AutoSys Zeke/Team Agent Integrationcomponents in order to integrate AutoSys jobs with Zeke and the

AutoSys/Team Agent product from PLATINUMs Altai Development Lab.Using cross-platform job dependency notation, you can define AutoSysjobs to conditionally start based on the status of a Zeke job running on amainframe, and you can define Zeke jobs to conditionally start based on

the status of an AutoSys job. You can also define AutoSys jobs that willrun on a Team Agent machine, if the Team Agent machine is defined to

AutoSys.

In addition, you can install various AutoSys/Adapters. The application-specific Adapters allow you to initiate, control, and report on the statusof jobs related to an application using the sophisticated job schedulingcapabilities of AutoSys. Contact your PLATINUM sales representative for

information on supported Adapters.

Figure 1-4illustrates an extended AutoSys configuration that includes theAutoSys Zeke/Team Agent Integration components and anAutoSys/Adapter installation on a UNIX client.




47/501


For more information, contact your sales representative.

Figure 1-4 AutoSys Components in an Extended Configuration

Remote Agent

Remote AgentUNIX Job

NT Job

UNIX Client NT Client

Application

AutoSys/Adapter

Other OS(e.g., AS/400)

Mainframe(MVS)

Job

Team Agent

OASIS

Zeke

AutoSys Server

(UNIX or NT)

Event Processor

Event Server(database)

oasis-broker

Zeke/Team Agent

Communicator

MVS Job




48/501



49/501


2AutoSys Security

This chapter describes AutoSys security. To set up AutoSys correctly, you

should understand the security features that control where and by whoma job can be edited or executed. If you are installing AutoSys on bothUNIX and NT, you must understand how security is implemented onboth systems.

For information about AutoSys security on NT, see theAutoSys Securitychapter in theAutoSys User Guide for Windows NT.

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Security on Events Sent by Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Security on Events Sent by the Event Processor . . . . . . . . . . . . . . . . . . . . . . . . 2-5

System-Level Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

AutoSys Database Field Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Job Definition Encryption . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Remote Agent Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

AutoSys User and Database Administrator Passwords . . . . . . . . . . . . . . . . . . 2-10

AutoSys Job-Level Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

AutoSys Job Ownership . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

AutoSys User Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

AutoSys Security


50/501


AutoSys Permission Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-12

Job Permissions and Windows NT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

AutoSys Superuser Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-15

Edit Superuser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-15

Exec Superuser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-16

Restricting Access to AutoSys Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-17

Remote Agent Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-18

AutoSys Security

Overview


51/501


Overview 2

AutoSys security includes:

System-level security. See System-Level Security on page 2-7.

Job-level security. SeeAutoSys Job-Level Security on page 2-11.

Superuser privileges. SeeAutoSys Superuser Privileges on page 2-15.

UNIX and NT file permissions. See Restricting Access to AutoSys Jobs onpage 2-17.

AutoSys security is initiated when either a user sends events that affect therunning of a job or the Event Processor sends events that affect a job.

Security on Events Sent by Users 2

By using the sendeventcommand or the Send Event dialog, you can sendexecute events that affect the running of a job. These are the executeevents that you can send, if you have the appropriate permissions:

If you start a job by sending an event, the job permissions are checked asshown in Figure 2-1.

STARTJOB FORCE_STARTJOB

KILLJOB DELETEJOB

CHANGE_STATUS CHANGE_PRIORITY

JOB_ON_HOLD JOB_OFF_HOLD

JOB_ON_ICE JOB_OFF_ICE

SEND_SIGNAL

AutoSys Security

Overview


52/501


Figure 2-1 Security when a user starts a job by sending an event

AutoSys Security

Overview


53/501


Figure 2-1shows how AutoSys checks for the following when a user starts

a job by sending an event:

1 Checks the database to determine if the job definition was tampered

autosys user guide

Documents