Autosys Tut

AutoSys

®

Tutorial

3.5

This documentation and related computer software program (hereinafter referred to as the "Documentation") is for theend user's informational purposes only and is subject to change or withdrawal by Computer Associates International,Inc. ("CA") at any time.

THIS DOCUMENTATION MAY NOT BE COPIED, TRANSFERRED, REPRODUCED, DISCLOSED ORDUPLICATED, IN WHOLE OR IN PART, WITHOUT THE PRIOR WRITTEN CONSENT OF CA. THISDOCUMENTATION IS PROPRIETARY INFORMATION OF CA AND PROTECTED BY THE COPYRIGHT LAWS OFTHE UNITED STATES AND INTERNATIONAL TREATIES.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION "AS IS" WITHOUTWARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILLCA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT,FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESSINTERRUPTION, GOODWILL OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS ORDAMAGE.

THE USE OF ANY PRODUCT REFERENCED IN THIS DOCUMENTATION AND THIS DOCUMENTATION ISGOVERNED BY THE END USER'S APPLICABLE LICENSE AGREEMENT.

The manufacturer of this documentation is Computer Associates International, Inc.

Provided with "Restricted Rights" as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) orDFARS Section 252.227.7013(c)(1)(ii) or applicable successor provisions.

© 1997–2000 Computer Associates International, Inc., One Computer Associates Plaza, Islandia, New York 11788-7000.All rights reserved.

All product names referenced herein belong to their respective companies.

Contents i

Contents

PrefaceRelated Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface-1About the AutoSys Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface-2

Taking the Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface-2

Lesson Summaries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface-3

Conventions Used in the Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Preface-4

Chapter 1: AutoSys EnvironmentAutoSys Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1AutoSys Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Defining Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

AutoSys Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2AutoSys Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

AutoSys Event Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

Event Processor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Working Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6AutoSys Environment Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-6

AutoSys Configuration Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

AutoSys Database Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-7

AutoSys Commands and Monitors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Monitors and Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9See Also . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-9

ii AutoSys Tutorial

Chapter2: AutoSys JobsJob Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Saving Job Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2Starting Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Running Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4Job Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Command Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

File Watcher Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Box Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Job States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10See Also . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Chapter3: Job StreamsJob Streams Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Example Job Streams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Date/Time and Job Dependencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

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

Box Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Advanced Box Job Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10See Also . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10

Chapter4: Defining and Running Jobsusing the GUIAutoSys GUI Dialogs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

Starting the GUI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

GUI Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

AutoSys Job Definition Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3Job Definition Dialog Control Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Job Definition Dialog Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4

Defining a Command Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5Running a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Send Event Dialog and Job Activity Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8

Contents iii

Defining Jobs with Starting Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10Specifying Date and Time Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Date/Time Options Dialog Regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-12

Specifying Job Dependency Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13

Defining a File Watcher Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15Initiating the Job Stream . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Observing the Job Stream’s Progression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Defining a Box Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20Removing Jobs and Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25

Deleting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-25

Deleting Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-26

Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-27See Also . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28

Chapter5: Defining and Running Jobsusing JILJob Information Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

JIL Sub-commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

Basic JIL Attribute Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

JIL Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4Defining a Command Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5Running a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7Defining Jobs with Starting Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Specifying Date and Time Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

Specifying Job Dependency Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-10

Removing Jobs and Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13Deleting Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

Deleting Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14See Also . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

iv AutoSys Tutorial

Chapter6: Monitoring andManaging AutoSysOperator Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Starting the Operator Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Job Activity Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Job List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

Currently Selected Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

Control Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

Action Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

Send Event Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

Control Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

Alarm Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

Exit Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

Job Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11Specifying a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-12

Sorting the Specified Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-13

Setting the Job Selection Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14

AutoSys Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-14Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15

Alarm Manager Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17

Alarm List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-17

Currently Selected Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18

Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-18

Alarm Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19Select by Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-19

Select by State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20

Select by Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-20

Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21See Also . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-22

Contents v

Chapter7: Queuing andLoad BalancingIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Real Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Defining Machines to AutoSys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Specifying Machine Load (max_load) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Specifying Relative Processing Power (factor) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

Using max_load and factor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5

Defining Real Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5Deleting Real Machine Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

Defining Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6Job Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

Load Balancing using Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Load Balancing using a List of Real Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8

Example of Load Balancing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

Review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10See Also . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10

Preface-1

PrefacePrefacePrefacePreface

Welcome to the world of AutoSys, the scheduling and operations automationsoftware for distributed environments. This manual contains a tutorial in sevenlessons to get you started using AutoSys quickly and efficiently.

Related Documents 0

The lessons in this tutorial introduce you to many AutoSys concepts and features.These concepts and features are described in more detail in other AutoSysdocumentation. Therefore, at the end of each lesson there is a “See Also” sectionthat directs you to more in-depth discussions on the topics covered in that specificlesson. These references are to one or more of the manuals listed below.

For UNIX, the following documentation is provided in addition to this AutoSysTutorial:

� AutoSys User Manual for UNIX describes how to use AutoSys, and how tooptimize job management in your distributed computing environment.

� AutoSys Installation Guide for UNIX describes how to install the AutoSys forUNIX software, how to install the AutoSys Database, and how to enter licensemanager keys.

For Windows NT, the following documentation is provided in addition to thisAutoSys Tutorial:

� AutoSys User Manual for Windows NT describes how to use AutoSys, and howto optimize job management in your distributed computing environment.

� The AutoSys Installation Guide for Windows NT describes how to install theAutoSys for Windows NT software, how to install the AutoSys Database, andhow to enter license manager keys.

� AutoSys Help, which you can open from your AutoSys program group. Theon-line help describes how to configure AutoSys, including setting up highavailability options, and how to use the AutoSys Administrator and the JobProfiles Manager.

About the AutoSys Tutorial

Preface-2 AutoSys Tutorial

About the AutoSys Tutorial 0

This tutorial is intended for systems administrators and operations personnel whowill be responsible for defining, monitoring, and managing jobs run by AutoSys.This manual assumes familiarity with the UNIX and/or NT operating systems,and it assumes that AutoSys has been installed and running on the machine thatyou will use when doing the tutorial exercises.

Before beginning this tutorial, you should install, start, and test the AutoSyssoftware.

Note: For information on installing AutoSys on your platform, see the AutoSysInstallation Guide for your platform.

Taking the Tutorial 0

This tutorial is structured into seven lessons that contain the basic information youneed to begin using AutoSys. The seven lessons have been designed so that themore complex topics are built on the understanding of less complicated ones. Also,information is presented in a logical sequence, so you can begin using AutoSys asquickly as possible. As a result, you should take each lesson in the order provided.

Estimated Times

Each lesson in the tutorial has been assigned an “estimated time” to complete.However, you might complete some lessons more quickly, or spend more time ontopics that are of special interest to you. On the average, the tutorial should takeabout five hours to complete, and, after that time, you can be using AutoSysconfidently.

Concepts and Skills

Each lesson in the tutorial presents information either in a conceptual fashion or ina conceptual and hands-on fashion. As you might expect, you will need toconceptually understand some of the basic concepts of AutoSys before youactually begin defining and running jobs on the system. For this reason, the firstthree lessons contain only conceptual information. The next three lessons provideconceptual information as well as hands-on tasks for you to accomplish. The lastlesson has only conceptual information.

Once you read the first three lessons, you will be ready to work on the system andperform the tasks in the next three lessons.

About the AutoSys Tutorial

Preface-3

Lesson Content and Flow

The lessons in this tutorial have been designed and structured with the followingaudiences in mind:

� Lessons 1 through 5 are directed toward individuals responsible for definingand running AutoSys jobs.

� Lessons 6 and 7 are directed toward individuals responsible for configuringand administering AutoSys.

However, all seven lessons can benefit both AutoSys operator and administratorpersonnel.

Lesson Summaries 0

Each lesson is briefly summarized below.

Lesson 1: AutoSys Environment

Provides basic information about the AutoSys environment and how AutoSysfunctions. The following topics are covered: AutoSys Definition, AutoSysMachines, AutoSys Instances, Software Components, Working Environment, andAutoSys Commands.

Lesson 2: AutoSys Jobs

Provides basic information about AutoSys jobs and their fundamentalcharacteristics. The following topics are covered: Job Definitions, Saving JobDefinitions, Starting Parameters, Running Jobs, Job Types, and Job States.

Lesson 3: Job Streams

Provides basic information about job streams and how to develop them. Thefollowing topics are covered: Job Streams Definition and Example Job Streams.

Lesson 4: Defining and Running Jobs using the GUI

Describes how to define and run jobs using the AutoSys Graphical User Interface(GUI). The following topics are covered: GUI Control Panel, Job Definition Dialog,Defining a Command Job, Running a Job, Defining a Dependent Job, Defining aFile Watcher Job, and Defining a Box Job.

Lesson 5: Defining and Running Jobs using JIL

Describes how to define and run jobs using the Job Information Language (JIL).The following topics are covered: Job Information Language, JIL Syntax, Defininga Command Job, Running a Job, and Defining a Dependent Job.

Conventions Used in the Tutorial

Preface-4 AutoSys Tutorial

Lesson 6: Monitoring and Managing AutoSys

Describes how to access the AutoSys features used for monitoring and managingAutoSys jobs and alarms. The following topics are covered: Operator Console, JobActivity Console, Job Selection Dialog, AutoSys Alarms, Alarm Manager, andAlarm Selection Dialog.

Lesson 7: Queuing and Load Balancing

Describes how to define real and virtual machines in order to balance job loadsacross physical machines. The following topics are covered: Real Machines, VirtualMachines, and Load Balancing.

Conventions Used in the Tutorial 0

The conventions used in this guide for syntax statements and instructions are asshown in the following table:

Convention Definition

bold courier Command names, command option and keywordnames, and attribute and value names arein bold courier.

bold italic Non-literal variables, or words that standfor values that you fill in, are in bolditalics.

courier Sample output text and filenames are inregular courier.

{ } Curly braces indicate that you must chooseat least one of the enclosed options. Donot include the braces themselves.

[ ] Square brackets indicate that you maychoose zero, one, or more of the enclosedoptions. Do not include the brackets them-selves.

| A vertical bar indicates that you mayselect only one of the options shown.

, A comma indicates that you may choose asmany of the options shown as you want,separating your choices with commas. Youmust include the commas in the command orattribute you type.

Conventions Used in the Tutorial

Preface-5

For example, the syntax statement for the autorep command is as follows:

autorep {-J job_name | -M machine_name |

-G global_name} [-s | -d | -q | -o over_num]

[ -r run_num] [-L print_level] [-t]

[-D data_server:database | -D TNSname]

The autorep command itself is typed exactly as shown. The three main options,-J job_name, -M machine_name, and -G global_name are enclosed in curlybraces and are separated by vertical bars. Therefore, one and only one of themmust be chosen. The variable job_name must be replaced by an actual job name.The four options -s, -d, -q, and -o are separated by a vertical bar in squarebrackets, indicating that none or one may be specified. The -L and-D options, andtheir arguments, are also optional.

< > Less than/greater than “pointed brackets”indicate a key to be pressed. <Control+C>indicates that both the Control key andthe C key should be pressedsimultaneously.

Convention Definition

Lesson

AutoSys Environment 1-1

1 AutoSys Environment

This first lesson introduces you to AutoSys-specific terminology while providingbasic information about the AutoSys environment.

Estimated Time: 25 Minutes

AutoSys Definition 1

AutoSys is an automated job management system that lets you schedule, monitor,and report on jobs that run on any licensed AutoSys client machines attached toyour network.

AutoSys Jobs 1

In the AutoSys environment, a job is a single action that can be performed on avalid AutoSys client machine. On UNIX, this action can be any single command orshell script, and on NT, this action can be any single command, executable, orbatch file. In addition, job definitions include a set of qualifying attributes.

Topics to be Covered: Topic Approach:

� AutoSys Definition Conceptual

� AutoSys Jobs Conceptual

� AutoSys Machines Conceptual

� AutoSys Instances Conceptual

� Software Components Conceptual

� Working Envirionment Conceptual

� AutoSys Commands and Monitors Conceptual

AutoSys Machines

1-2 AutoSys Tutorial

Defining Jobs 1

Using AutoSys utilities, you can define a job by assigning it a name and specifyingthe attributes that describe its associated behavior. These specifications make upthe AutoSys job definition. Below are the two methods you can use to create jobdefinitions:

� The AutoSys Graphical User Interface (GUI)

� The AutoSys Job Information Language (JIL)

AutoSys Graphical User Interface (GUI)

The AutoSys GUI allows you to interactively set the attributes that describe when,where, and how a job should run. You create job definitions using the GUI ControlPanel and the dialogs you can launch from it. The fields in the GUI dialogscorrespond to the AutoSys JIL sub-commands and attributes.

Job Information Language (JIL)

JIL is a specification language, with its own syntax, that is used to describe when,where, and how a job should run. When you enter the jil command you get thejil command prompt, at which you can enter the job definitions one line at a timeusing this special language. When you exit jil, the job definition is loaded intothe AutoSys database. Alternatively, you can enter the definition as a text file andre-direct the file to the jil command. In this case, the jil command activates thelanguage processor, interprets the information in the text file, and loads thisinformation in the AutoSys database.

AutoSys Machines 1

From a hardware perspective, the AutoSys environment is composed of thefollowing two types of machines attached to a local area network (or LAN):

Server Machine—The AutoSys server is the machine(s) on which the EventProcessor and/or the Event Server (database) reside. In a basic configuration,both the Event Processor and the Event Server reside on the same machine.

Client Machine(s)—The AutoSys client is the machine on which the RemoteAgent software resides, and where AutoSys jobs are to be run. This can be on theAutoSys server and/or on separate physical client (or agent) machine(s).

AutoSys Instance


AutoSys Instance 1

An AutoSys instance is one licensed version of AutoSys software running as anAutoSys server, or as an AutoSys server/agent, on one or more machines. Aninstance uses its own Event Processor and Event Server and operatesindependently of other AutoSys instances. An instance is defined by the following:

� At least one Event Server.

� The instantiation of an Event Processor.

� The value of the AUTOSERV variable, which is the three-letter instance ID.

You might want to install multiple instances of AutoSys to accomplish thefollowing:

� Separate the processing of one department from that of another department.

� Separate test and development environments from production processing.

Software Components 1

From a software perspective, the AutoSys environment is composed these maincomponents (as shown in Figure 1-1):

� Event Server (AutoSys database)

� Event Processor

� Remote Agent

� Console Utilities

The Event Processor and the Event Server constitute the server, and the RemoteAgent(s) constitute the client(s), and they interact with each other based on a trueclient/server model.

The AutoSys Event Server, Event Processor, and Remote Agent(s) can reside on thesame machine. If this is the case, the server machine also acts as a client machine.

The Console Utilities are used for defining and maintaining AutoSys instances andjobs; what is included with these utilities is platform-specific.

Software Components


.

Figure 1-1 AutoSys Software Components

AutoSys Event Server 1

The AutoSys Event Server is a database containing information about AutoSys, aswell as events and job and calendar definitions.

Events

AutoSys is completely event-driven. That is, every action occurring in the AutoSysenvironment is considered a unique event. The Event Server records importantdata about each event, and the Event Processor interprets and processes all theevents it reads from the Event Server.

In the AutoSys environment, an event can be one of the following:

� A command internally generated by the Event Processor which controlsAutoSys job processing.

� A runtime command that is manually sent to the Event Processor using theAutoSys sendevent command or the AutoSys Send Event dialog (part of theOperator Console discussed later in this tutorial). Examples of these types ofevents would be STARTJOB and JOB_ON_HOLD.

� An alarm that notifies operations personnel of situations that require theirattention. An example of this type of event would be JOB_FAILURE.

Server Machine

ClientMachines

Ethernet

AutoSys Event Processor

Remote Agent

Remote Agent

Remote Agent

Database

Software Components


Job and Calendar Definitions

A job definition contains the instructions for a job, including when, where, andhow it should be run.

A calendar definition can be associated with a job to determine what days a jobshould and/or should not be run. To create calendar definitions, use the AutoSysGraphical Calendar Facility (which you can open from the Job Definition dialog,discussed later in this tutorial).

Event Processor 1

The Event Processor interprets and processes all the events it reads from the EventServer. The Event Processor continually scans the database for events to beprocessed. When it finds one, it checks whether the event satisfies the startingconditions for any job in the database.

For each event, it determines whether or not the starting conditions for a particularjob have been satisfied. If they have, it proceeds to do the following (as illustratedin Figure 1-2):

1. Determine what actions are to be taken. The actions to be taken might bethe starting or stopping of a job, checking for resources, monitoringexisting jobs, or initiating corrective procedures.

2. Instructs the appropriate Remote Agent to perform these actions.

High Availability

You can configure AutoSys to run with Dual Event Servers and a Shadow EventProcessor as a means of obtaining high availability and redundancy in the system.

Remote Agent

The Remote Agent is a temporary process started by the Event Processor on aclient, or agent, machine—it is started so a specific action can be taken. The RemoteAgent performs its processing as follows (as illustrated in Figure 1-2):

� Starts the job

� Runs the job

� Returns job status or completion information to the Event Server

� Exits

If the Remote Agent is unable to return information to the Event Server (forexample, if it is down), it waits and tries again later.

Working Environment


Figure 1-2 Running a Job

Working Environment 1

The behavior of the Event Processor, Event Server, and Remote Agent arecontrolled by AutoSys environment variables and the AutoSys configurationparameters. For example, the configuration parameters specify which EventServer the Event Processor and the Remote Agent(s) should connect to for aninstance, and the instance name is specified by the AUTOSERV environmentvariable.

The AutoSys database also has its own associated environment variables andconfiguration file.

Server Machine

Ethernet

Event Server Event Processor

Remote Agent

Remote Agent

polls

Remote Agent

Event Processor

- event found- starting conditions metstart up Remote Agent

- start up- run job- return job status- exit

ClientMachines

AutoSysEvent Server

Working Environment


AutoSys Environment Variables 1

These are the AutoSys environment variables:

� AUTOSYS — Specifies the directory for the AutoSys software.

� AUTOUSER — Specifies the directory containing user files, which, dependingon the platform, can include configuration files, Event Processor output files,archive files, and sound files.

� AUTOSERV — Specifies the unique, three-lettered name of a single instance ofAutoSys running on a single or multiple machines.

AutoSys Configuration Parameters 1

The AutoSys configuration parameters specify the information for and control thebehavior of the AutoSys components. At installation, AutoSys is configured withdefault settings. You can keep the installation defaults or you can modify many ofthe settings.

On UNIX, you can modify these parameters, which are located in the$AUTOUSER/config.$AUTOSERV configuration file. On NT, you can modifythese parameters using the AutoSys Administrator, which is installed in yourAutoSys program group as part of the AutoSys Console Utilities.

AutoSys Database Variables 1

The AutoSys Event Server can be configured for a Sybase, Oracle, or (for NT)Microsoft SQL Server database. Refer to the installation information and releasenotes provided with your platform for details on configuring your database forAutoSys.

Sybase

For bundled and unbundled Sybase, you must define the SYBASE environmentvariable to specify where the Sybase directory is located. The Sybase directorycontains the interfaces file (for UNIX) or the SQL.INI file (for NT), whichspecifies the location of the database. In addition, the DSQUERY environmentvariable defines the name of the Sybase AutoSys database.

Oracle

For Oracle, ensure that the tnsnames.ora file is present and properlyconfigured. This file specifies where the Oracle dataserver is located. On UNIX, thetnsnames.ora file is usually in $TNS_ADMIN/tnsnames.ora. On NT, thisfile is usually in \ORANT\NETWORK\ADMIN\TNSNAMES.ORA.

AutoSys Commands and Monitors


Microsoft SQL Server

For Microsoft SQL Server, you must install the appropriate Microsoft SQL Serverclient utilities on each AutoSys Event Processor and Remote Agent machine, andensure that there is database connectivity between the Event Server, EventProcessor, and Remote Agent machines.

AutoSys Commands and Monitors 1

There are several commands unique to AutoSys that can be used to control,configure, and report on system behavior. In addition, you can monitor AutoSysprocesses and generate reports in various formats using either the AutoSys GUIdialogs or commands.

Commands 1

You enter AutoSys commands with the appropriate arguments at the UNIXprompt or at the AutoSys Instance Command Prompt on NT. You can also usesome of these commands in programs run by AutoSys to programmatically controland monitor AutoSys at runtime.

Below are examples of AutoSys commands:

� chk_auto_up — Inspects the AutoSys environment variables and configurationfiles, then determines if the Event Server and the Event Processor are running.

� autoping — Verifies that the AutoSys client machine(s) are properly configuredand can communicate successfully. It also verifies that the Remote Agent (clientsoftware) is functioning correctly.

� autorep — Reports information about the status of jobs, job runs, machines, andmachine status. It also reports information about job overrides and globalvariables.

Monitors and Reports 1

Monitors provide you with a real-time view of the system. Reports (also calledBrowsers) provide you with the ability to examine historical information about jobruns using a variety of reporting views. Monitors and reports retrieve informationfrom the AutoSys database and allow you to filter and screen only the informationyou are interested in from this vast collection of data.

You can define monitors and reports using the AutoSys GUI (select the Monitor/Browser button from the Control Panel), or by using JIL statements. The monitorsand reports only have to be defined to AutoSys once—they can then be set to runautomatically according to a schedule, or they can be set to wait for “on-demand”execution.

Review


You can monitor job activity using the Job Activity Console of the OperatorConsole; you can monitor the activity of the Event Processor using the autolog -e command.

Operator Console

The Operator Console is a collection of dialogs that provide a sophisticatedmethod of monitoring AutoSys jobs in real-time. This feature lets you view anyjobs that are defined to AutoSys, whether they are currently active or not. You canselect any job and view more detailed information about it.

Review 1

� AutoSys is an automated job management system that lets you schedule,monitor, and report on jobs that run on any licensed AutoSys client machinesattached to a network.

� A job is defined as a single action that can be taken on a valid AutoSys clientmachine.

� From a hardware perspective, AutoSys is composed of two types of machines:server machine and client machine(s).

� From a software perspective, the AutoSys environment is composed of fourmajor components: Event Server (database), Event Processor, Remote Agent(s),and Console Utilities.

� The Event Server stores job definitions and event information.

� The Event Processor is a server process that continually polls the Event Serverfor events that need to be processed.

� The Remote Agent is a temporary process started by the Event Processor on aclient machine to process specific tasks.

� The AutoSys environment is controlled by environment variables andconfiguration parameters. The AutoSys database (Event Server) also has itsown environment variables and configuration files.

� There are several AutoSys commands that can be used to control, configure,and report on operations and system behavior.

� There are GUI dialogs and AutoSys commands that you can use to monitor andreport on AutoSys job activity.

See Also


See Also 1

� For information on configuring your database, see the installation informationprovided with your platform.

� For more information on the AutoSys database (Event Server) refer to theAutoSys User Manual for your platform.

� For information on modifying AutoSys configuration parameters, includingsetting up your AutoSys to use Dual Event Servers and a Shadow EventProcessor, refer to the AutoSys User Manual for your platform.

� For information on AutoSys commands, refer to the AutoSys User Manual foryour platform.

� For information on monitoring jobs and creating reports, refer to the AutoSysUser Manual for your platform.

� For information on using the Operator Console, refer to Lesson 6 in this tutorial,and then refer to the AutoSys User Manual for your platform.

Lesson

AutoSys Jobs 2-1

2 AutoSys Jobs

This lesson provides basic information about AutoSys jobs and their fundamentalcharacteristics.


Job Definitions 2

An AutoSys job is a single action that can be taken on a valid AutoSys clientmachine, by the Remote Agent. A job performs a particular action based on a setof instructions called a job definition. These instructions are essentially attributesof the job that specify when, where, and how the job should be run.

You can create a job definition in one of the following ways (as in Figure 2-1):

� Generated interactively using the AutoSys Graphical User Interface (GUI).

� Entered either into a text file and then redirected using the AutoSys JobInformation Language (JIL), or at the jil prompt.


� Job Definitions Conceptual

� Saving Job Definitions Conceptual

� Starting Conditions Conceptual

� Running Jobs Conceptual

� Job Types Conceptual

� Job States Conceptual

Saving Job Definitions


.

Figure 2-1 Creating Job Definitions

Saving Job Definitions 2

Once a job definition has been created, it must be saved to the Event Server(database). The job definitions are saved to the database in one of the followingways (as illustrated in Figure 2-2):

� If you define a job using the GUI, the job is saved when you click Save in theJob Definition dialog.

� If you define a job by creating a job definition text file, the job is saved when thetext file is re-directed into the AutoSys jil command. Note that if you definea job at the jil prompt, the definition is saved to the database when you exitjil.

JIL Job Definition TextGUI - Job Definition Dialog

Job Definition

JIL sub-commandAttribute statements

...

...

...

Starting Conditions

AutoSys Jobs 2-3

Figure 2-2 Saving Job Definitions

Starting Conditions 2

A job’s starting conditions tell the Event Processor when to run a job. Theseconditions can be based on the following:

� Date and time conditions — Specify certain dates and/or times to run or not torun a job.

� Job dependency conditions — Specify that certain job events occur before thejob can be run.

Starting conditions are defined by attribute statements within a job definition,regardless of whether you use the GUI or JIL to specify them.

If you define a job using the GUI, you specify its date and time conditions in theDate/Time Options dialog. You set its job dependency conditions in the JobDefinition dialog.

JIL Job DefinitionGUI - Job Definition Dialog

Job Definition

JIL sub-commandAttribute statements

...

...

...

Saved to theEvent Server

Save jil < text_file_name

Server MachineAutoSys

Stored in theEvent Server

Event Server

Text File

(database)

Running Jobs


If you define a job using JIL, you specify its date and time conditions, as well as itsjob dependency conditions, using attribute statements.

The following are examples of date and time conditions:

� days_of_week — Specifies days on which to run the job.

� start_times — Specifies times of the day on which to run the job.

� run_window — Specifies a time span in which the job is allowed to start.

The following are examples of job dependency conditions:

� success(job_name) — Specifies to run the job upon the successfulcompletion of the indicated job.

� failure(job_name) — Specifies to run the job if the indicated job fails.

� notrunning(job_name)— Specifies to run the job if the indicated job is notrunning.

� done(job_name) — Specifies to run the job if the indicated job hascompleted running; its status can be SUCCESS, FAILURE, or TERMINATED.

Running Jobs 2

A job is started based on its starting conditions.

� Jobs with starting conditions — If a job has starting conditions, the EventProcessor starts it automatically when the starting conditions have beensatisfied. Figure 2-3 illustrates this process.

� Jobs with no starting conditions — If a job does not have starting conditions,you must start it manually. You must have the correct permissions to start a job.

Figure 2-4 illustrates these two methods of starting a job. Using the GUI, you cansend a STARTJOB event from the Send Event dialog. Using AutoSys commands atthe command prompt, you can issue asendevent -E STARTJOB -J job_name command to start a job. You can useeither of these methods, regardless of how the job definition was entered into theAutoSys database.

Running Jobs

AutoSys Jobs 2-5

.

Figure 2-3 Job Runs Automatically

Figure 2-4 Job Runs Manually

Event Processor- starting conditions met- run job

Server Machine

Event Server Event Processor

polls

Job Runs

Job with Starting Conditions

GUI - Send Event Dialog

STARTJOB eventpress “Execute”

sendevent -E STARTJOB -J job_name

Job Runs

Job with No Starting Conditions

Job Types


Job Types 2

There the three types of AutoSys jobs: Command, File Watcher, and Box.

Command Jobs 2

The Command Job is most commonly thought of as “a job”. When a Command Jobis run, the specified command is executed on a client machine, as illustrated inFigure 2-5. When the command has completed, the executing Remote Agent sendsan AutoSys event (such as SUCCESS or FAILURE) and other completioninformation back to the Event Server.

You can assign to a job a profile that specifies user-defined environment variablesneeded to run the job. If the profile job attribute is assigned to a job, the RemoteAgent will “source” the assigned profile file before executing the job.

Figure 2-5 Running Command Jobs

Server Machine

Client Machine #1

Client Machine #2

Event Processor

- starting conditions met

- start up Remote Agent

- write value of exit code

- Remote Agent exits

- JobA on Client Machine #1

Command Job

- start Command Job

Client Machine #3

- execute command

to AutoSys Event Server

Job Types

AutoSys Jobs 2-7

File Watcher Jobs 2

A File Watcher Job starts a process on a client machine that monitors the creationand size of a specific file. When that file reaches a certain minimum size, and is nolonger growing, the File Watcher Job completes with a SUCCESS status.Figure 2-6 illustrates this process.

File Watcher Jobs provide a means of integrating events external to AutoSys intothe processing of AutoSys jobs. For example, a file needs to be downloaded froma mainframe, and it is expected to arrive after 2:00 a.m. When it arrives, a batch jobis to be run to process it, and this in turn could start a whole sequence of jobs. Thatis, the File Watcher Job could start the processing of several other dependent jobsin a job stream.

.

Figure 2-6 Running File Watcher Jobs

Server Machine

Event Processor


- JobW on Client Machine #2

- start File Watcher Job

File Watcher Job

Client Machine #3

Client Machine #2

Client Machine #1


- monitor file size- watch for file


- file reaches minimum

- Return successfuljob completion status

size and is stable(no longer growing)

Job Types


Box Jobs 2

A box is a container of jobs with like starting conditions, either date/timeconditions or job dependency conditions. Figure 2-7 illustrates the running of jobsin a box.

Use boxes to group jobs with like scheduling parameters, not as means of groupingjobs organizationally. For example, if you have a number of jobs that run daily at1:00 a.m., you could put all these jobs in a box and assigning a daily start conditionto the box. (In contrast, a variety of account processing jobs with diverse startingconditions should not be grouped in the same box.)

Figure 2-7 Running Box Jobs

Note: Jobs in boxes can be started only when their parent box is running.However, once a contained job starts running, it completes, even if the box is laterstopped for some reason.

Server Machine

Client Machine #1

Event Processor


- JobA on Client Machine #1


- run Box Job- Remote Agent exits

Box JobClient Machine #2

- start up Remote Agent- execute shell script from Job

- execute command from JobA

- JobB on Client Machine #2

...


- JobC on Client Machine #3

- execute command from JobC

Client Machine #3

- write value of exit codeto AutoSys Event Server





- complete Box Job and writeexit status when thecontained jobs complete

Job States

AutoSys Jobs 2-9

Job States 2

At every point in processing, a job has what is called its current status or “state.”This status is stored in the Event Server and is kept track of by AutoSys at all times.Figure 2-8 illustrates the states that simple jobs go through.

The value of a job’s status is used to determine when to start other jobs that aredependent on a particular job (or jobs). This value is displayed in the Job Reportgenerated by the AutoSys autorep command, and it is displayed in the AutoSysOperator Console (in the Job Activity Console window’s Status field).

These are the status values a job can have:

� STARTING — The Event Processor is starting up the Remote Agent. The job isin the process of “coming up.”

� RUNNING — The job is running.

� INACTIVE — The job has not been processed; the job has never been run, or itsstatus was intentionally altered to “turn off” its previous completion status.

� SUCCESS — The job exited with an exit code equal to or less than the“maximum exit code for success.”

� FAILURE — The job exited with an exit code greater than the “maximum exitcode for success.”

� TERMINATED — The job terminated while in the RUNNING state.

� RESTART — The job was unable to start (or failed) due to hardware orsoftware problems, and has been scheduled to restart.

� ACTIVATED — The top-level box that this job is in is now in the RUNNINGstate, but the job itself has not yet started.

� QUE_WAIT — The job can logically run (i.e., all the starting conditions havebeen met), but there are not enough machine resources available at the time.

� ON_ICE — This job is removed from all conditions and logic, but is still definedto AutoSys. Operationally, this is like deactivating the job, which will remainon ice until it receives the JOB_OFF_ICE event.

� ON_HOLD — This job is on hold and will not be run until it receives theJOB_OFF_HOLD event. In addition, while this job remains in the ON_HOLDstatus, dependent, downstream jobs will not be run.

Review


Figure 2-8 Basic Job States

Review 2

� An AutoSys job is a single action that can be taken on a valid AutoSys agentmachine, such as executing a command or watching for a file.

� A job performs a particular action based on a set of instructions called a jobdefinition. A job definition can be created using the AutoSys GUI (JobDefinition Dialog) or using JIL.

� Once a job definition has been created, it must be saved to the Event Server.

� A job’s starting parameters tell the Event Processor when to run a job. Theseparameters can be of two types: date and time conditions and/or jobdependency conditions.

� If a job does not have starting conditions, you must start it manually, eitherusing the Send Event dialog or the sendevent command.

� There are three types of AutoSys jobs: Command, Box, and File Watcher.

� When a Command Job is run, the resulting action is the execution of a specifiedcommand by a Remote Agent on a client machine.

Event Generated by Current Job StatePoint in Processing

Event ProcessorReads Event

Starting Conditionsfor a Job Met

Start UpRemote Agent

Run Job

Job is Running

Job Completes

InspectExit Code

Remote AgentExits

Remote AgentStarts Up

Return Statusand Exit Code toAutoSys Database

STARTING

RUNNING

SUCCESS or FAILURE

Event Processor

Remote Agent

Remote Agent

See Also

AutoSys Jobs 2-11

� A File Watcher Job starts a process on an agent machine that monitors thecreation and size of a specific operating system file.

� A Box Job is an abstraction that defines a “container” of other jobs. Thiscontainer provides a way to group jobs based on similar or related startingconditions. The “box” itself performs no actions, although it must be “running”in order for the jobs it contains to run.

� At every point in processing, a job has what is called its current status or“state.” This status is stored in the AutoSys database so that AutoSys can keeptrack of all jobs’ states. The value of a job’s status is used to determine when tostart other jobs that are dependent on a particular job (or jobs).

See Also 2

� For more information on AutoSys jobs, see Chapter 3, “AutoSys Jobs,” andChapter 4, “Job Attributes,” in the AutoSys User Manual for your platform.

� For information on defining jobs using the AutoSys GUI dialogs, see Lesson 4,in this tutorial, and then refer to the AutoSys User Manual for your platform.

� For more information on defining jobs using JIL, see Lesson 5, in this tutorial,and then refer to the AutoSys User Manual for your platform.

� For information on using profiles to set environment variables for jobs, seeChapter 3, “AutoSys Jobs,” in the AutoSys User Manual for your platform.

� For information on running jobs, and job executing permissions, refer toChapter 2, “AutoSys Security,” in the AutoSys User Manual for your platform.

� For information on the sendevent command, refer to its entry in the AutoSysUser Manual for your platform.

Lesson

Job Streams 3-1

3 Job Streams

This lesson provides basic information about job streams and how to developthem.


Job Streams Definition 3

A job stream (or flow) refers to the logic of how related AutoSys jobs are run. Muchof the logic inherent in a job stream is based on the starting conditions of the jobsin the stream. A job’s starting conditions tell the Event Processor when to run a job.These conditions can be the following types:

� Date and time conditions — specifies certain dates and/or times to run or notto run a job.

� Job dependency conditions — specifies that certain job events occur before thejob can be run.

In addition, jobs in a box are controlled by the parent Box Job’s starting conditions,and jobs in a box and only be started when the parent Box Job is running.

The following are examples of ways jobs can be related in a job stream:

� A Command job can be dependent on the successful completion of another jobthat has date and time starting conditions.

� A Command job can be dependent on a particular condition being satisfied foranother job before it will run, such as the other job must have a SUCCESS orFAILURE completion status.


� Job Streams Conceptual

� Example Job Streams Conceptual

Example Job Streams


� A File Watcher Job’s successful completion is dependent on the creation andsize of a particular file. In addition, other jobs can be dependent on the SUCESSof FAILURE of a File Watcher job.

� A Box Job’s successful completion is dependent on the successful completion ofall the jobs inside the box (this is the default behavior for a Box Job). Note thatthe jobs in a box that have no other starting conditions will run as soon as thebox starts.

The above dependencies become more sophisticated when, for example, youimplement one of the following job dependencies:

� A job is dependent on conditions being satisfied for several other jobs, such asSUCCESS for one and the FAILURE of another.

� A job within a Box Job is dependent on conditions being satisfied for one ormore other jobs inside the box.

Example Job Streams 3

This section presents four job streams, with explanations. These examples will helpyou understand how to logically structure job dependencies and job streams usingAutoSys.

Date/Time and Job Dependencies 3

For example, you might create job definitions and a job stream based on thefollowing logic:

� The job_backup Command Job has date and time conditions specified for itsstarting conditions. This job is to be run every day of the week at 1:01 a.m. Forexample, this job might perform regular backups of the system.

� The job_clean Command Job has a job dependency condition specified for itsstarting parameter. It will run only on the successful completion of job_backup.This job might delete certain operating system or log files that have become toolarge, in order to save space on the system.

This logic is illustrated in Figure 3-1.

Example Job Streams

Job Streams 3-3

.

Figure 3-1 Command Job Stream

File Watcher Jobs 3

In this example job stream, a File Watcher Job is used to watch for an incomingmainframe file. Note that this example would run on a UNIX machine. The jobdefinitions and job stream are based on the following logic:

� The job_Fwatch File Watcher Job has date and time conditions specified for itsstarting conditions. This job is to be run every day of the week at 2:00 p.m. Itwatches for a file arriving from a mainframe.

� The job_Fwatch job will check every 15 seconds for the creation of the incomingfile. Once the file has arrived, job_Fwatch will monitor the file’s size to see if ithas “stabilized” (it has maintained a specified size in bytes for at least 15seconds). When both of these conditions are met, job_Fwatch will notify theEvent Server and complete with a SUCCESS status.

� The job_parse Command Job has a job dependency condition specified for itsstarting parameter. It will run only on the successful completion of the jobnamed job_Fwatch. This job parses the newly received file and formats certaindata into a report.

SUCCESS

SUCCESS

Date/TimeMet job_backup

Job Dependencyjob_clean

Job Stream

Conditions

Job Definitions

job_backup job_clean

1:01 a.m. DailyPerform Backup

success(job_backup)Delete Files

Start

Condition MetStart

job_backup

job_clean

Example Job Streams


� The job_print Command Job has a job dependency condition specified for itsstarting parameter. It will run only on the successful completion of thejob_parse job. The job_print job prints the report created by job_parse.


Figure 3-2 File Watcher Job Stream

SUCCESS

SUCCESS

Date/TimeMet

job_Fwatch

Job Dependencyjob_parse

Job Stream

Conditions

Job Definitions

job_Fwatch job_parse

2:00 p.m. DailyWatch for file

success(job_Fwatch)Generate Report

Start

Condition MetStart

job_Fwatch

job_parse

job_print

success(job_parse)Print Report

Job DependencyCondition Met

Start

SUCCESS

job_print

job_print

File fromMainframe

Example Job Streams

Job Streams 3-5

Box Jobs 3

In this example job stream, a Box Job is used to group several jobs that have relatedstarting conditions. The jobs inside the box are often called “nested jobs, or child jobsof the parent Box Job. The job definitions and job stream are based on the followinglogic:

� The bx_daily_update Box Job has date and time conditions specified for itsstarting conditions. This job is to be run every day of the week at 3:00 a.m. Thisbox will serve as a container for three Command Jobs whose overall purpose isto update files and generate a report.

� The job_update Command Job is defined as being inside the bx_daily_updateBox Job. It will run as soon as bx_daily_update starts, since it has no otherstarting conditions. The job_update job will update a set of files.

� The job_run_stats Command Job is defined as being inside thebx_daily_update Box Job. It has a job dependency condition specified for itsstarting parameter. It will run only on the completion of the job_update job. Thejob_run_stats job will run statistics against the updated files.

� The job_report_stats Command Job is defined as being inside thebx_daily_update Box Job. It has a job dependency condition specified for itsstarting parameter. It will run only on the completion of the job_run_stats job.The job_report_stats job will report on the statistics generated the byjob_run_stats job.


Note: In this example, the done starting condition is used for the startingcondition of the job_run_stats and job_report_stats jobs. If these jobs used thesuccess starting condition, and one of the jobs on which they weredependent failed, the dependent job would not start, and thus would notcomplete. This would cause the bx_daily_update Box Job to run indefinitelysince, by default, a Box Job cannot complete until all jobs in the Box Job haverun and completed. You can however configure a Box Job with customcompletion conditions. For information on how to do this, see “AdvancedBox Job Logic” on page 3-7.

Example Job Streams


Figure 3-3 Box Job Stream

Date/TimeMet

bx_daily_update

Box Running job_update

Job Stream

Conditions

Job Definitions

job_update job_run_stats

done(job_update)

Run Statistics

Start

No other Conditions

Start

job_update completes

job_report_stats

done(job_run_stats)

Report Statistics


Start job_run_stats

job_run_stats completes

bx_daily_update

3:00 a.m. Daily


Start job_report_stats

Update Files

DONE bx_daily_update

job_report_stats completes

Box Completes

Example Job Streams

Job Streams 3-7

Advanced Box Job Logic 3

In this example job stream, a Box Job similar to the previous example is used toorganize several jobs. However, more sophisticated logic is applied to the jobstream to address a situation in which jobs depend on the successful completion ofother jobs, and these jobs can fail. The job definitions and job stream are based onthe following logic:

� The bx_daily_update Box Job has date and time conditions specified for itsstarting conditions. This job is to be run every day of the week at 3:00 a.m. Thisjob will serve as a container for three Command Jobs whose overall purpose isto update files and generate a report.

� The job_update Command Job is defined as being inside the bx_daily_updateBox Job. It will run when bx_daily_update has been started, since it has no otherstarting conditions. In addition, this job has a special attribute calledbox_terminator that specifies the following: the bx_daily_update box job(which contains this job_update job) should be terminated if the job_update jobfails. The job_update job will update a set of files.

� The job_run_stats Command Job is defined as being inside thebx_daily_update Box Job. It will run only on the successful completion of thejob_update job named. The job_run_stats job has a special attribute calledbox_terminator that specifies the following: the bx_daily_update box job(which contains this job_run_stats job) should be terminated if thisjob_run_stats job fails. The job_run_stats job will run statistics against theupdated files.

� The job_report_stats Command Job is defined as being inside thebx_daily_update Box Job. It will run only on the successful completion of thejob_run_stats job. The job_report_stats job will report on the statisticsgenerated by job_run_stats.

� The job_trigger_msg Command Job has a job dependency condition specifiedfor its starting parameter. It will run only on the FAILURE status of thebx_daily_update Box Job. The job_trigger_msg job will page an operator toindicate that the problem needs to be investigated.

This logic is illustrated in Figure 3-4 and in Figure 3-5.

Note: Figure 3-4 and Figure 3-5 illustrate the Advanced Box Job job definitionsand job stream example. However, in order to simplify the illustrations, the date/time and job dependency conditions have been omitted in Figure 3-5.

Example Job Streams


Figure 3-4 Advanced Box Job Definitions

Job Definitions

job_trigger_msg

failure(bx_daily_update)

Page Operator

job_update job_run_stats

success(job_update)

Run Statistics

job_report_stats

success(job_run_stats)

Report Statistics

bx_daily_update

3:00 a.m. Daily

Update Files

box_terminator box_terminator

Example Job Streams

Job Streams 3-9

Figure 3-5 Advanced Box Job Stream

bx_daily_update

job_update

Job Stream

SUCCESS job_update

job_run_stats

SUCCESS job_run_stats

job_report_stats

SUCCESS job_report_stats

FAILURE job_update

FAILURE job_run_stats

job_trigger_msg

SUCCESS job_trigger_msg

SUCCESS bx_daily_update

TERMINATED bx_daily_update

FAILURE job_report_stats

FAILURE bx_daily_update

Review


Review 3

� A job stream (or flow) refers to the logic of how related AutoSys jobs are run.AutoSys jobs can be related in a number of ways.

� Much of the logic inherent in a job stream is based on the starting conditions ofthe jobs in the stream.

� There are basic and advanced job stream relationships, or dependencies. Thefollowing are examples of ways jobs can be related in a job stream:

– A Command job can be dependent on the successful completion of anotherjob that has date and time starting conditions.

– A Command job can be dependent on a particular condition being satisfiedfor another job before it will run, such as the other job must have a SUCCESSor FAILURE completion status.

– A File Watcher Job’s successful completion is dependent on the creation andsize of a particular file. In addition, other jobs can be dependent on theSUCESS of FAILURE of a File Watcher job.

– A Box Job’s successful completion is dependent on the successfulcompletion of all the jobs inside the box (this is the default behavior for aBox Job). The jobs in a box that have no other starting conditions will run assoon as the box starts.

See Also 3

� For information on job starting conditions, see the “Starting Parameters”section of Chapter 3, “AutoSys Jobs”, in the AutoSys User Manual for yourplatform.

� For more information on box jobs, job streams, and advanced job streams, referto the AutoSys User Manual for your platform.

� For information on the box_terminator and other box-specific job attributes,refer to the attributes beginning with “box_” in the AutoSys User Manual foryour platform.

Lesson

Defining and Running Jobs using the GUI 4-1

4 Defining and Running Jobsusing the GUI

This lesson describes how to define and run jobs using the AutoSys Graphical UserInterface (GUI).


Note: If you have previously taken this lesson, you must delete the created jobsand files. For instructions on how to do this, see “Removing Jobs and Files” onpage 4-26.


� AutoSys GUI Dialogs Conceptual/Hands-On

� AutoSys Job Definition Dialog Conceptual/Hands-On

� Defining a Command Job Conceptual/Hands-On

� Running a Job Conceptual/Hands-On

� Defining Jobs with StartingConditions

Conceptual/Hands-On

� Defining a File Watcher Job Conceptual/Hands-On

� Defining a Box Job Conceptual/Hands-On

AutoSys GUI Dialogs


AutoSys GUI Dialogs 4

The AutoSys GUI provides several dialogs that you can use to define Command,File Watcher, and Box Jobs. The complexity of the job definition determines howmany dialogs you will use. In addition, there are dialogs that provide the means tosend events and monitor jobs.

Starting the GUI 4

To start the GUI:

UNIX: At the command prompt, enter the autosc & command.

NT: In the AutoSys program group, double-click on the AutoSysGraphicalInterface icon.

The GUI Control Panel appears, as shown in Figure 4-1.

GUI Control Panel 4

Figure 4-1 GUI Control Panel

The Control Panel buttons perform the following actions:

� Ops Console — Displays the Job Activity Console, used for monitoring AutoSysjobs and alarms. From the Job Activity Console, you can open the Job Selection,Alarm Manager, and Alarm Selection dialogs. The Job Activity Console and itsdialogs are referred to as the Operator Console (or Ops Console).

� Job Definition — Displays the Job Definition dialog, used to create jobdefinitions. From the Job Definition dialog, you can open the following dialogs:Advanced Features, Date/Time Options, and Calendar Definition.

� Calendars — Displays the Calendar Definition screen, used for definingAutoSys run and exclude calendars.

� Monitor/Browser — Displays the Monitor/Browser dialog, used to define andrun monitors and reports (or browsers).

� HostScape, JobScape, and TimeScape belong to the AutoSys/Xpert product.These buttons will be greyed out if you have not purchased this product.

� Exit — Exits the GUI

AutoSys Job Definition Dialog


During this lesson, you can use the Operator Console, the Job Activity Console,and its related dialogs to see the progress of jobs in real time. This dialog displaysinformation about AutoSys jobs and shows each job-related event as it occurs.

Note: To view the Operator Console, select the Ops Console button from the GUIControl Panel. The Operator Console is discussed in detail in , “Monitoring andManaging AutoSys”.

AutoSys Job Definition Dialog 4

The Job Definition dialog provides all the fields you need to create a basic jobdefinition.

To access the Job Definition dialog:

1. At the GUI Control Panel, single-click on the Job Definition button. TheJob Definition dialog appears, as shown in Figure 4-2.

Figure 4-2 Job Definition DMialog

AutoSys Job Definition Dialog


Job Definition Dialog Control Buttons 4

The control buttons at the top of the Job Definition dialog perform the followingactions:

� Clear — Clears the dialog without saving any information to the Event Server(database). Use this button to clear all fields before defining a new job.

� Delete — Deletes the currently displayed job from the Event Server.

� Save — Stores the currently displayed job in the Event Server, either modifyinga pre-existing job or creating a new one. When you Save a job definition, thedialog is also cleared in preparation for another job definition.

� Adv Features — Displays the Job Definition Advanced Features dialog, whichis used for all but the simplest of job definitions.

� Exit — Closes the Job Definition dialog. If you click Exit without first clickingSave, your most recent job definition changes are not saved.

The fields displayed in the Job Definition dialog are based on the type of job beingdefined. When you select a Job Type, only the fields appropriate to that type of jobare displayed and activated, other fields are disabled.

Job Definition Dialog Regions 4

The Job Definition dialog is divided into the following three regions:

� Basic Information — The top region of the dialog has fields where you supplybasic information, such as job name and job type.

� Starting Parameters — The middle region of the dialog has the followingcomponents:

– A button for accessing the Date/Time Options dialog to specify date andtime starting conditions. From the Date/Time Options dialog, you can alsoopen the Calendar Definition screen.

– A field for entering job dependency conditions.

� Command and File Watcher Information or Box Completion Conditions —The bottom region of the dialog has fields in which you enter specificCommand, File Watcher, or Box Job information.

Defining a Command Job


Defining a Command Job 4

A Command Job executes a command on an agent machine. The Command Jobyou are about to define will execute a simple echo command. The name of the jobwill be your_name_lesson4.

Note: It is recommended that you use your last name for the your_name valueof the job name—now and throughout this lesson. Job names can be up to 30characters long.

Using the Job Definition Dialog 4

In the Basic Information region:

1. In the Job Name field, enter: your_name_lesson4

2. In the Job Type area, ensure that the Command radio button is selected.

In the Starting Parameters region:

3. Ensure that the Is the Start Date/Time Dependent option is set to No.

In the Command and File Watcher Information region:

4. In the Execute on Machine field, enter the name of a valid AutoSys agentmachine on which the command will run.

5. In the Command to Execute field, enter the following command:UNIX:/bin/echo "AutoSys Lesson 4 test"

NT: echo AutoSys Lesson 4 test

Next, you will specify the name of the standard output file for the above message.You will use Job Definition Advanced Features dialog to do this.



To access the Job Definition Advanced Features Dialog:

6. At the top of the Job Definition dialog, click the Adv Features button. TheJob Definition Advanced Features dialog appears, as shown in Figure 4-3.

Figure 4-3 Job Definition Advanced Features Dialog

For the purposes of this lesson, we will only discuss the File to Redirect to StandardOutput field, which you need to use for your Command Job.

Specify a standard output file for the job in the Command Information region:

7. In the File to Redirect Standard Output field, enter the following:UNIX: /tmp/your_name4.outNT: C:\tmp\your_name4.out



Save the job to the AutoSys Database:

8. At the top of the dialog, click the Save&Dismiss button. This action savesthe new job to the database and closes the Job Definition AdvancedFeatures dialog.

Exit the Job Definition Dialog

9. At the top of the dialog, click the Exit button.Keep the GUI Control Panel on your screen for the next part of thislesson.

Running a Job


Running a Job 4

As stated earlier, a job is started based on its starting conditions. The CommandJob you just created does not have any starting conditions, so the only way this jobwill run is if you start it manually. You can start the job from the Send Event dialog,which is part of the Operator Console (discussed in Lesson 6, “Monitoring andManaging AutoSys”, of this tutorial). In the following sections, you will manuallystart the job and view the real-time events using the Send Event dialog and the JobActivity Console.

Send Event Dialog and Job Activity Console 4

To run the Job Manually and View the Events:

1. In the GUI Control Panel, click the Ops Console button. The Job ActivityConsole window of the Operator Console appears, as shown inFigure 4-4.

Figure 4-4 Job Activity Console

Running a Job


2. In the Control area at the bottom of the dialog, select the Event radiobutton in the Reports area, and deselect Freeze Frame radio button in theShow area. Now, when you manually start the job, you can view theevent activity in the Event Report area.

3. Choose Select Jobs from the View menu. This opens the Job Selectiondialog.

4. The default settings select All Jobs, All Statuses, and All Machines. ClickOK in the Job Selection dialog to accept these defaults. When you returnto the Job Activity Console, the your_name_lesson4 job should bedisplayed in the top field.

5. Click on the your_name_lesson4 job to select it.

6. In the Control area, click the Send Event button. The Send Event dialogappears, as shown in Figure 4-5.

Figure 4-5 Send Event Dialog

You can specify an event using one of the radio buttons at the top of thedialog.

7. Select the Start Job radio button.Just below these buttons is the Job Name field, which by default containsthe name of the currently selected job.

Defining Jobs with Starting Conditions


8. In the Job Name field, make sure that your_name_lesson4 isdisplayed. If it is not, enter the job name.Just below the Job Name is an area to specify when the event shouldoccur.

9. Select the Now button.You do not need to enter any information in the bottom region of thedialog at this time. The Send Priority is Normal by default. If you selectHigh, the event is moved to the top of the unprocessed event queue.

10. To send the event and dismiss the dialog, click the Execute button. At thistime, you can view the events in the Event Report area of the Job ActivityConsole. When the job runs and completes successfully, the AutoSysLesson 4 test message should be redirected to theyour_name4.out file.

Note: You can keep the Job Activity Console open to view the events for the restof the exercises in this lesson.

To view the standard output file:

11. At the command prompt, enter the following command:UNIX: cat /tmp/your_name4.out

NT: type C:\tmp\your_name4.out

You should see the following message:

AutoSys Lesson 4 test

Defining Jobs with Starting Conditions 4

If an AutoSys job definition contains starting conditions, it is run when thosestarting conditions are met. That is, a job’s starting conditions tell the EventProcessor when to run a job. These conditions can be of the following two types:

� Date and time conditions — Specifies certain dates and/or times to run or notto run a job.

� Job dependency conditions — Specifies that certain job events must occurbefore the job can be run.

In the next part of this lesson, you will set date and time conditions for theCommand Job you just created, then you will specify a date/time dependency, orstarting, condition for the job.

To prepare for this module:

Delete the standard output file created in the previous exercise. To do this, enterthe following command at the command prompt:



UNIX: rm /tmp/your_name4.out

NT: del C:\tmp\your_name4.out

Specifying Date and Time Conditions 4

To add date and time conditions to the your_name_lesson4 job, you need to accessthe Date/Time Options dialog.

To specify date and time conditions for a job:

1. At the GUI Control Panel, click the Job Definition button. The JobDefinition dialog appears.

2. In the Job Name field, enter your_name_lesson4, and click Search.This action displays the entire job definition.Instead of typing the entire job name, you can enter the first three or fourletters of your_name, and click Search. The entire job definition shoulddisplay.


3. Ensure that there are date and time dependencies by selecting the Yesradio button.

To access the Date/Time Options dialog:

4. Click the Date/Time Options button. The Date/Time Options dialogappears, as shown in Figure 4-6.



Figure 4-6 Date/Time Options Dialog

Date/Time Options Dialog Regions 4

The Date/Time Options dialog has the following regions:

� Date — The left region of the dialog has fields where you specify the dateconditions for a job.

� Time — The right region of the dialog has fields where you specify the timeconditions for a job.

� Control area — The control area at the bottom of the dialog contains theCalendars and Dismiss buttons. The Calendars button accesses the AutoSysCalendar Definition dialog. The Dismiss button closes the Date/Time Optionsdialog. When you Dismiss this dialog, all entries are maintained in memory sothat the subsequent Save process in the Job Definition dialog will also save theDate/Time Options settings.

In the Date region of the Date/Time Options dialog:

5. Select the radio button for today. For example, if today is Thursday, selectthe Thursday radio button.



In the Time region:

6. In the Time(s) of Day field, enter a time that is only a few minutes awayfrom the current time.You must enter the time in 24 hour format, using the HH:MM formatshown in the dialog. For example, to specify 2:35 p.m., you enter 14:35.

To exit the Date/Time Options dialog:

7. At the bottom of the dialog, click the Dismiss button.

To save the date and time conditions you just specified:

8. At the top of the Job Definition dialog, click the Save button. This actionthe saves to the database the changed job definition foryour_name_lesson4, with its new date and time conditions.Keep the Job Definition dialog open to define jobs later in this lesson.

Now that the your_name_lesson4 Command Job has starting parameters, you donot have to run it manually. As soon as the starting parameters have been satisfied,the Event Processor will start the job.

Before continuing with the lesson, wait until the Time(s) of Day field value youspecified has arrived, so that the job runs and completes. You can view the actionsin the Job Activity Console’s Event Report area. Once the job runs, the specifiedmessage should be redirected to the standard output file.

To view the standard output file:





Specifying Job Dependency Conditions 4

Now you will use the Job Definition dialog to specify a job dependency conditionfor your Command Job. The scenario is as follows:

� First, you will define a new Command Job named your_name_depjob4 that willredirect a message to a file. You will specify that this job to be run only whenyour_name_lesson4 has completed successfully.

� Next, you will save your_name_depjob4 to the AutoSys database.

� Then you will change the date/time conditions for your_name_lesson4 and re-save the job to the AutoSys database.



� When your_name_lesson4 completes successfully, the Event Processor checksif any jobs are dependent on the completion of this job. As a result, it will startyour_name_depjob4.


You must delete the your_name4.out file. To do this, enter the followingcommand at the command prompt:



To define a dependent job in the Basic Information region of the Job Definitiondialog:

1. In the Job Name field, enter the following: your_name_depjob4




4. In the Starting Condition field, enter the following:success(your_name_lesson4)



6. In the Command to Execute field, enter the following command:UNIX: date

NT: ntgetdate

Next, you will specify the name of the standard output file for the results of thiscommand. You do this at the Job Definition Advanced Features dialog.

To specify standard output file for the job:

1. At the top of the Job Definition dialog, click the Adv Features button. TheJob Definition Advanced Features dialog appears.

2. In the Command Information region, find the File to Redirect StandardOutput field and enter:UNIX: /tmp/your_name_depjob4.outNT: C:\tmp\your_name_depjob4.out

To save your_name_depjob4 to the AutoSys database:

At the top of the dialog, click the Save&Dismiss button. This action savesthe new job to the AutoSys database and closes the dialog.



To change the date/time conditions for your_name_lesson4 in the BasicInformation region of the Job Definition dialog:

1. In the Job Name field, enter the following: your_name_lesson4

2. Click the Search button. This action retrieves the complete job definitionfrom the AutoSys database and displays it in the dialog.


3. Ensure that the Is the Start Date/Time Dependent option is set to Yes.


4. Click the Date/Time Options button, and the Date/Time Options dialogappears.

In the Time region of the Date/Time Options dialog:

5. In the Time(s) of Day field, enter a time that is only a few minutes awayfrom the current time.You must enter the time in 24 hour format, using the HH:MM formatshown in the dialog. For example, to specify 2:35 p.m., you enter 14:35.




7. At the top of the Job Definition dialog, click the Save button. This actionre-saves to the database the job definition for your_name_lesson4, with itsnew date and time conditions.

8. Before continuing with the lesson, wait until the Time(s) of Day fieldvalue you specified has arrived. You can view the event Activity in theJob Activity Console’s Event Report field.After your_name_lesson4 has completed successfully, theyour_name_depjob4 job will start and redirect the current system dateinto the file your_name_depjob4.out. This process takes only a fewseconds.

To view the files created with this job stream:


NT: type \tmp\your_name4.out



10. At the command prompt, enter the following command:UNIX: cat /tmp/your_name_depjob4.out

NT: type \tmp\your_name_depjob4.out

Defining a File Watcher Job


You should see the system date displayed.

Defining a File Watcher Job 4

The next job you will define is a File Watcher Job, as illustrated in Figure 4-7. A FileWatcher Job starts a process on an agent machine that monitors the creation andsize of a specific operating system file. When that file reaches a certain minimumsize, and is no longer growing, the File Watcher Job sends an event to the AutoSysEvent Server indicating that the job has succeeded and the file has “arrived.”

The scenario is as follows:

� First you will define the File Watcher Job named your_name_watcher and saveit to the database. This job will have date/time conditions for its startingparameters.

� The job your_name_watcher will check every 15 seconds for a file you will becreating named your_name_file.txt. Only after this file is saved to thetmp directory and has “stabilized” will your_name_watcher completesuccessfully.



� Then you will define a Command Job named your_name_wdone and save it tothe database. This job will have a job dependency condition specified for itsstarting condition. It will run only when the job your_name_watchersuccessfully completes. When run, this job will redirect a message to a filenamed your_name_wdone.out indicating that the job stream hascompleted successfully:

.

Figure 4-7 File Watcher Job Stream

To define the File Watcher Job in the Basic Information region of the Job Definitiondialog:

1. In the Job Name field, enter the following: your_name_watcher

2. In the Job Type area, ensure that the File Watcher radio button is selected.



4. In the File To Watch For field, enter:UNIX: /tmp/your_name_file.txtNT: C:\tmp\your_name_file.txt

SUCCESS

SUCCESS

Date/TimeMet

Job Dependency

ConditionsStart

Condition Met

your_name_watcher

your_name_wdone

Creation andStabilization ofyour_name_file.txt

Job Definitions

your_name_watcher your_name_wdone

Specified Date/TimeWatch for File

success(your_name_watcher)Create File

Creation ofyour_name_wdone.out

Start

your_name_watcher

your_name_wdone

Job Stream




5. Ensure that the Is the Start Date/Time Dependent option is set to Yes.


6. Click the Date/Time Options button. The Date/Time Options dialogappears.

In the Date region of the Date/Time Options dialog:

7. Select the radio button for today.

In the Time region:

8. In the Time(s) of Day field, enter a time that is about 10 minutes later thanthe current time.You must enter the time in 24 hour format, using the HH:MM formatshown in the dialog.



Next, you will specify file watching criteria for the your_name_watcher job, as wellas the name of the standard output file for the results of this command. You do thisat the Job Definition Advanced Features dialog.

To access the Job Definition Advanced Features dialog:


To specify file watching criteria for the File Watcher Job:

11. At the File Watching Criteria region at the top of the Advanced Featuresdialog, in the Time Interval (secs) to Determine Steady State field, enterthe following: 15

This value specifies that if the file named your_name_file.txtdoes not grow in size for a duration of 15 seconds, it will be consideredstabilized. Note that the default value is 60.

12. At the File Watching Criteria region at the top of the dialog, in theMinimum File Size (in BYTES) field, ensure that the entry is this: 0

A specification of 0 bytes indicates that there is no minimum file size.Note that this is the default setting.

To save the date/time and file watcher settings:




Now you will create a Command Job named your_name_wdone. This job is adependent job, and it will be started once your_name_watcher has completedsuccessfully.

To define the your_name_wdone job in the Basic Information region of the JobDefinition dialog:

1. In the Job Name field, enter the following: your_name_wdone




4. In the Starting Condition field, enter the following:

success (your_name_watcher)



6. In the Command to Execute field, enter the following command:UNIX:/bin/echo "The job your_name_watcher has completed."NT:echo The job your_name_watcher has completed.After your_name_wdone has completed successfully, this message will beredirected to the your_name_wdone.out file.

Next, you will specify the name of the standard output file. You do this in the JobDefinition Advanced Features dialog.



To specify standard output file for the job in the Command Information region ofthe Advance Features dialog:

8. In the File to Redirect Standard Output field, enter:UNIX: /tmp/your_name_wdone.outNT: C:\tmp\your_name_wdone.out

To save the job:




Initiating the Job Stream 4

Now you are ready to initiate the job stream and see how everything works.

To initiate the job stream:

1. Start up a text editor, such as vi for UNIX or Notepad for NT, and createa file named your_name_file.txt.

2. Enter any short string of text in the file.

3. Save and exit the file.

Observing the Job Stream’s Progression 4

Assuming everything has been done properly, the following is occurring while thejob stream progresses:

� Once you saved and exited the file your_name_file.txt, it was only amatter of seconds before your_name_watcher started checking the file’s sizeand stability.

� Once the file your_name_file.txt has remained at the same size for 15seconds, the Remote Agent that started your_name_watcher will send aSUCCESS event to the Event Server and exit.

� The successful completion of the your_name_watcher job will trigger the EventProcessor to start the job named your_name_wdone.

� The your_name_watcher job creates the following message that will beredirected to the file your_name_wdone.out:

The job your_name_watcher has completed.

You can view the stream of events in the Job Activity Console.

To view the file created by this job stream:

At the command prompt, enter the following command:UNIX: cat /tmp/your_name_wdone.outNT: type C:\tmp\your_name_wdone.out

You should see the following message:The job your_name_watcher has completed.

Defining a Box Job


Defining a Box Job 4

The last job you will define is a Box Job. Figure 4-8 illustrates the job definitionsand the job stream for this example Box Job exercise.

A Box Job is an abstraction that defines a “container” of other jobs. A Box Jobprovides an organizational or grouping function of jobs with like or relatedstarting conditions. The box itself performs no actions, although it can trigger otherjobs to run.

In this final exercise, you will do the following:

� Define a Box Job named your_name_box.

� Define two simple Command Jobs named your_name_job1 andyour_name_job2, and specify that they be put in your_name_box. Theyour_name_job2 job will be dependent on the completion of theyour_name_job1 job.

� Manually start the your_name_box job, and, as a result, both theyour_name_job1 and your_name_job2 jobs will be run.

Defining a Box Job


Figure 4-8 Box Job Definitions and Stream

To define the your_name_box Box Job in the Basic Information region of the JobDefinition dialog:

1. In the Job Name field, enter the following: your_name_box

2. In the Job Type area, ensure that the Box radio button is selected.Notice that because of this action the Command and File Watcher regionchanges to Box Completion Conditions.



To save the your_name_box job:

4. At the top of the Job Definition dialog, click the Save button. This actionsaves the new job definition to the database.

your_name_box

your_name_job1

SUCCESS your_name_box

Start Box Job from the

your_name_job1 completes

Send Event dialog

Job Stream

Job Definitions

your_name_job1 your_name_job2

done (your_name_job1)

echo command

your_name_box

No starting conditions

echo command

your_name_job2

your_name_job2 completes

Start

Box Job running, no Start

Job dependency Start

Box Job completes

other start conditions

condition met

Defining a Box Job


To define your_name_job1 in the Basic Information region of the Job Definitiondialog:

1. In the Job Name field, enter the following: your_name_job1


3. In the Name of Box this Job is IN field, enter the following:your_name_box


4. Ensure that the Is the Start Date/Time Dependent option is set to No.Note that since this job has no starting conditions, it will be started whenthe your_name_box job is started.



6. In the Command to Execute field, enter the following command:UNIX:/bin/echo "your_name_job1 has successfully completed."

NT:echo your_name_job1 has successfully completed.After your_name_job1 completes successfully, this message will beredirected to the your_name_job1.out file.

Next, you will specify the name of this standard output file. You do this at the JobDefinition Advanced Features dialog.



To specify standard output file for the job in the Command Information region ofthe Advanced Features dialog:

8. In the File to Redirect Standard Output field, enter the following:UNIX: /tmp/your_name_job1.outNT: C:\tmp\your_name_job1.out

To save the job:


Defining a Box Job


To define your_name_job2 in the Basic Information region of the Job Definitiondialog:

1. In the Job Name field, enter the following: your_name_job2


3. In the Name of Box this Job is IN field, enter the following:your_name_box



5. In the Starting Conditions field, enter the following:done(your_name_job1)

Notice that you are giving this job the done starting parameter. You dothis to ensure that all jobs in the box will complete, and thus, theyour_name_box Box Job will complete. If you were to use the success orfailure starting conditions in this example, there is a possibility that theyour_name_job2 job would never start, and thus never complete. Thiswould cause the Box Job to continue running indefinitely. Note that youcan set up Box Jobs and their contained jobs to use any startingconditions, using advanced logic.



7. In the Command to Execute field, enter the following command:UNIX:/bin/echo "your_name_job2 has successfully completed."

NT:

echo your_name_job2 has successfully completed.

After your_name_job2 has completed successfully, this message will beredirected to the your_name_job2.out file.

Next, you will specify the name of this standard output file. You do this at the JobDefinition Advanced Features dialog.



To specify standard output file for the job in the Command Information region:

9. In the File to Redirect Standard Output field, enter the following:UNIX:/tmp/your_name_job2.outNT: C:\tmp\your_name_job2.out

Defining a Box Job


To save the job:


To exit the Job Definition dialog:

11. At the top of the dialog, click the Exit button.

To initiate the job stream and test your job definition for the new Box Job:

1. In the GUI Control Panel, click the Ops Console button. The Job ActivityConsole window of the Operator Console appears.If you have been viewing the AutoSys Event Report while you wererunning the jobs in this lesson, this window will be open already.

2. If jobs are not already displayed in the Job Activity Console, choose SelectJobs from the View menu to open the Job Selection dialog. Accept thedefault settings and click OK to close the dialog.

3. In the Job Activity Console Job List, select the job your_name_box. Thismakes this job the currently selected job

4. In the Control area at the bottom of the console, click the Send Eventbutton. The Send Event dialog appears.

5. In the Send Event dialog, select the Start Job radio button.Just below these buttons is the Job Name field, which by default containsthe name of the currently selected job. It should display the jobyour_name_box

Just below the Job Name is an area to specify when the event shouldoccur.

6. Select the Now radio button.

7. To send the event and dismiss the dialog, click the Execute button.The your_name_box job should run and the specified message should beredirected to the file named your_name_job2.out.In the Job Activity Console, you can view the events as they occur.


8. At the command prompt, enter the following command:UNIX: cat /tmp/your_name_job1.outNT: type C:\tmp\your_name_job1.out


your_name_job1 has successfully completed.

9. At the command prompt, enter the following command:UNIX: cat /tmp/your_name_job2.outNT: type C:\tmp\your_name_job2.out


your_name_job2 has successfully completed.

Removing Jobs and Files


To exit the AutoSys GUI and complete this lesson:

Exit all open AutoSys dialogs and windows, and, in the GUI ControlPanel, click the Exit button.

Removing Jobs and Files 4

If you are moving on to the next lesson, keep the job definitions and files youcreated. You will use them later in this tutorial.

If you are repeating this lesson, you must first remove from the database the jobdefinitions that you created previously. You must also delete the files created bythese jobs when you ran them during this lesson.

Deleting Jobs 4

These are the job definitions that you must delete from the database:

� your_name_lesson4

� your_name_depjob4

� your_name_watcher

� your_name_wdone

� your_name_box

� your_name_job1

� your_name_job2

To delete these jobs:

1. Display the AutoSys GUI Control Panel:UNIX: At the command prompt, enter the autosc & command.NT: In the AutoSys program group, double click on the AutoSys

Graphical Interface icon.The GUI Control Panel appears.

2. At the GUI Control Panel, click the Job Definition button.The JobDefinition dialog appears.

In the Basic Information region:


4. Click the Search button. This action retrieves the job definition from thedatabase and displays it in the dialog.

5. Make absolutely sure this is the job definition for the job named

Review


your_name_lesson4.

6. At the top of the dialog, click the Delete button. This action deletes the jobfrom the database.

7. Repeat Steps 3 through 6 for all the jobs listed above.

Deleting Files 4

When the jobs in Lesson 4 are run, they create some fileson your system in the following directory:

UNIX: /tmpNT: C:\tmp

These are the files in that directory that you must delete:

� your_name4.out

� your_name_depjob4.out

� your_name_file.txt

� your_name_wdone.out

� your_name_job1.out

� your_name_job2.out

To delete these files:

Enter the following command:UNIX: rm /tmp/your_name*

NT: del C:\tmp\your_name*

Review 4

� AutoSys provides a complete GUI for defining Command, File Watcher, andBox jobs. The complexity of the job you are defining dictates how manyAutoSys GUI dialogs you will need to use.

� The GUI dialogs also provide the means to send events (Send Event dialog) andmonitor jobs (Operator Console dialogs).

� To access the GUI Control Panel:

UNIX: Use the AutoSys autosc command.NT:Double-click on the AutoSys Graphical Interface icon in the

AutoSys program group.� The GUI Control Panel has eight buttons: Ops Console, Job Definition,

Calendars, Monitor/Browser, HostScape, JobScape, TimeScape, and Exit.

See Also


� To access the Job Definition dialog, you click the Job Definition button in theGUI Control Panel. This dialog provides all the fields you need to create a basicjob definition.

� When using the GUI, you specify the type of job (Command, File Watcher, orBox) by selecting the appropriate radio button in the Job Definition Dialog.

� A job’s starting conditions tell the Event Processor when to start the job.Starting conditions can be of two types: date and time conditions and/or jobdependency conditions. Jobs with starting conditions are started automaticallyby the Event Processor when the starting conditions have been satisfied.

� You specify date and time conditions at the Date/Time Options dialog,accessed from the Job Definition dialog.

� You specify job dependency conditions in the Starting Parameters region of theJob Definition dialog.

� When defining a File Watcher Job, you must enter the name of the file to watchfor in the Job Definition dialog. You can access the Job Definition AdvancedFeatures dialog and specify the time interval to determine a steady state and aminimum file size for the “watched for” job.

� When defining a job inside a Box Job, you use the Job Definition Dialog tospecify the name of the Box the job is in.

� If a job does not have starting conditions, you must start it manually. You canuse the Send Event dialog (accessed from the Job Activity Console) to start a jobmanually.

See Also 4

� For more information on defining jobs using the AutoSys GUI dialogs, refer tothe AutoSys User Manual for your platform.

� For information on using the Operator Console to monitor and manage jobs,see Lesson 6, in this tutorial, and then refer to the AutoSys User Manual for yourplatform.

� For information on how to set up calendars using the Calendar Definitionwindow, refer to the AutoSys User Manual for your platform.

� For information on using the Monitor/Browser dialog, refer to the AutoSys UserManual for your platform.

� For information on advance Box Job logic, refer to the AutoSys User Manual foryour platform.

� For information on how to assign the machine job attribute, as well as otherjob attributes, to implement job load balancing and queuing, refer to Lesson 7in this tutorial, then refer to the AutoSys User Manual for your platform.

Lesson

Defining and Running Jobs using JIL 5-1

5 Defining and Running Jobsusing JIL

This lesson describes how to define and run jobs using the AutoSys JobInformation Language (JIL).


Note: If you have previously taken this lesson, you must delete the created jobsand files. For instructions on how to do this, see “Removing Jobs and Files” onpage 5-14.


� Job Information Language Conceptual

� JIL Syntax Conceptual

� Defining a Command Job Conceptual/Hands-On

� Running a Job Conceptual/Hands-On

� Defining Jobs with StartingConditions

Conceptual/Hands-On

Before You Begin


Before You Begin 5

During this lesson, you can see a real-time report of the status of jobs once they arestarted using theautolog command. This command displays the Event Processorlog file and shows each job-related event as it occurs. This log can be very helpfulbecause it shows you what is happening as you proceed with each part of thelesson. You should run this process in its own window, separate from the windowin which you are running JIL. On UNIX, you should run the command in its ownshell, and on NT, you should run the command in its own AutoSys InstanceCommand Prompt window.

At the command prompt, enter the following:

autolog -e

This displays the Event Processor log file and shows each job-related event as itoccurs. You can terminate this reporting at any time by pressing <Control+C>.

Note: On NT, you must use an AutoSys Instance Command Prompt window toexecute all AutoSys commands and processes. You can open an AutoSys InstanceCommand prompt by double-clicking on the icon in the AutoSys program group.This command prompt window sets several necessary AutoSys environmentvariables.

Job Information Language 5

As an alternative to the GUI, you can also use the AutoSys proprietary scriptinglanguage—Job Information Language (or JIL) to create job definitions. This jobdefinition must be submitted to the AutoSys database before the job can be run. Todefine a job using JIL, you can do one of the following:

� Submit the full job definition by redirecting a JIL script file to the jilcommand. (This is the process you will use in this lesson.)

� Interactively submit the job definition by issuing the jil command first, andthen entering JIL statements at the jil>> command prompt.

Both of these methods are analogous to “saving” a job definition in the AutoSysGUI at the Job Definition dialog.

When you enter a job definition using JIL, it contains the following information:

� One or more JIL job definition sub-commands, which you can use to create,modify, and delete job definitions.

� One or more attribute statements, which define when, where, and how a jobshould be run.

Job Information Language


JIL Sub-Commands 5

There are the five JIL sub-commands that you can use to create, modify, and deletejob definitions. These sub-commands are described in the following table:

Basic JIL Attribute Types 5

Even though AutoSys has a number of job, monitor/report, and machineattributes, there are basic attribute types you almost always use when definingwhen, where, and how a job should be run. These attribute types are described inthe following table:

Table 1:

Sub-command Action

insert_job Adds a new job to AutoSys.

update_job Edits fields on an existing job.

delete_job Deletes this job from AutoSys.

delete_box Deletes the specified Box Job, and recursivelydeletes all the jobs that are contained in thebox.

override_job Applies overrides on indicated job attributesfor only the next run of this job.

Table 2:

Attribute Type Job Type Job Characteristic

Job Name All(Required)

Identifies the job. This is an argument to oneof the JIL sub-commands, like this:insert_job: install_test

Job Type All(Required)

Identifies the type of job: either c for Com-mand, f for File Watcher, or b for Box.For example, you would specify a box likethis: job_type: b

Machine Name Command,File Watcher(Required)

Identifies the agent machine on which the jobshould run, like this:machine: machine_name

StartingConditions

All(Optional)

Specifies the date and time, or the job depen-dency conditions for a job, like this:days_of_week: mo, we, frcondition: success(my_job)

JIL Syntax


JIL Syntax 5

When writing a JIL script, you must follow the syntax rules listed below.

Rule 1

Each sub-command uses the following form:

sub_command: job_name

where

� sub_command is one of the sub-commands listed in the above table.

� job_name is the user-specified name of the job to be acted on.

Rule 2

Each sub-command can be followed by one or more attribute statements. Thesestatements can occur in any order, and are applied to the job specified in thepreceding sub-command. A subsequent sub-command begins a new set ofattributes for a different job. The attribute statements have the following form:

attribute_keyword: value

where

� attribute_keyword is one of the legal JIL attributes.

� value is the setting to be applied to the attribute.

Rule 3

Multiple attribute statements can be entered on the same line. However, they mustbe separated by at least one space.

Rule 4

A box that contains jobs must be defined before the jobs can be placed in it.

Rule 5

File toWatch For

File Watcher(Required)

Specifies a file for which to watch. For exam-ple, on UNIX you might specify this:watch_file: /tmp/mainframe_file

Table 2:

Attribute Type Job Type Job Characteristic



Legal value settings can include any of the following characters: upper- andlower-case letters, hyphens, underscores, numbers, colons (if the colon is escapedwith quotes or a preceding backslash; see “Rule 6”), and the special character “@”.

Rule 6

Any colons used in an attribute statement’s value setting must be escapedbecause JIL parses on the combination of keyword followed by a colon. Forexample, to specify the time to start a job, specify “10:00”, or escape the colonwith a preceding backslash “\”, as in 10\:00.

Rule 7

Comments are indicated using one of the following two methods:

� You can comment out an entire line by placing a pound sign “#” in the firstcolumn.

� You can use the C programming syntax by beginning a comment with “/*”and ending it with “*/”. This approach allows comments to span multiplelines. The following is an example comment:

/* this is a comment */

Defining a Command Job 5

The first job you will define is a Command Job. It will be identical to the firstCommand Job you defined in Lesson 4. However, the name of this job isyour_name_lesson5. As in the last lesson, this Command Job will execute a simpleecho command on a valid AutoSys agent machine.

Note: It is recommended that you use your last name for the your_name valueof the job name—now and throughout this lesson. Job names can be up to 30characters long.

To define a Command Job using JIL:

1. Start your favorite text editor, and create the following file in the tmpdirectory:

your_name_lesson5.jil



2. Using the editor, enter the following JIL script:UNIX:

NT:

The Event Processor on the system interprets the above JIL scripts in thefollowing way:

Line Summary1-3 Comments about the script.4 Blank — Not read.5 JIL Sub-Command — The name of the job is

your_name_lesson5.6 Machine Attribute — The agent machine on which the job

should run. The machine_name value must be a validAutoSys agent machine at your site.

7 Command Attribute — The command the job should run onthe agent machine is: echo theAutoSys Lesson 5 testmessage.

8 File Redirection Attribute — The file to which standardoutput should be redirected is the following:UNIX: /tmp/your_name5.outNT: C:\tmp\your_name5.out

3. Save (write) and exit the file.

# JIL script to test the AutoSys installation.

# This script will re-direct a message to the

# file named /tmp/your_name5.out.

insert_job: your_name_lesson5machine: machine_name

command: /bin/echo "AutoSys Lesson 5 test"std_out_file: /tmp/your_name5.out

# JIL script to test the AutoSys installation.

# This script will re-direct a message to the

# file named C:\tmp\your_name5.out.

insert_job: your_name_lesson5machine: machine_name

command: echo AutoSys Lesson 5 teststd_out_file: "C:\tmp\your_name5.out"

Running a Job


To save the job to the AutoSys Event Server:

4. At the command prompt, enter the following command:jil < your_name_lesson5.jil

This re-direction of the text file containing your JIL script saves theyour_name_lesson5 job to the Event Server (database). The followingmessage should display to standard output, indicating that the job hasbeen successfully submitted to the database:

_______________________________________

Insert/Updating Job: your_name_lesson5Database Change WAS Successful!_______________________________________

Exit Code = 0_______________________________________

Running a Job 5

A job is started based on its starting conditions. However, the Command Job youjust created does not have any starting conditions. Therefore, to run this job, youmust start it manually.

To run the job manually:

At the command prompt, enter the following:

sendevent -E STARTJOB -J your_name_lesson5

The STARTJOB option should be in all upper-case letters.

These are the options to the sendevent command:

� -E STARTJOB — Indicates the event you want to send.

� -J your_name_lesson5 — Indicates the job you want to run.



When the job runs, the specified message should be re-directed to the file namedyour_name5.out.

To view the your_name5.out file:

At the command prompt, enter the following command:

UNIX:cat /tmp/your_name5.outNT:type C:\tmp\your_name5.out



Defining Jobs with Starting Conditions 5

Jobs can be defined that are dependent on certain starting conditions. A job’sstarting conditions tell the Event Processor when to run the job. These conditionscan be of the following two types:

� Date and time conditions — Specifies certain dates and/or times to run or notto run a job.

� Job dependency conditions — Specifies that certain job events occur before thejob can be run.

In this next part of the lesson, you will first set date and time conditions for theCommand Job you just created, then you will specify a job dependency conditionfor the job.

To prepare for this module, delete the standard output file created in the previousexercise. At the command prompt, enter the following:





Specifying Date and Time Conditions 5

To add date and time conditions to the your_name_lesson5 job, edit the JIL scriptdefining this job.

To specify date and time conditions for a job:

1. Open the following file in your favorite text editor:your_name_lesson5.jil

Using an editor, modify the JIL script as shown in the example scriptsbelow (revised/added lines are shown in bold).When adding these lines, you should indicate today’s day of the week forthe days_of_week attribute, using the mo, tu, we, th, fr, sa, or suvalues. In addition, you should indicate for the start_times attribute atime value that is only a few minutes away from the current time, using a24-hour format enclosed in quotes. For example, 2:00 p.m. is written as"14:00".UNIX:

NT:

# JIL script to test the AutoSys installation.# This script will re-direct a message to the# file named /tmp/your_name5.out.

update_job: your_name_lesson5

machine: machine_namecommand: /bin/echo "AutoSys Lesson 5 test"std_out_file: /tmp/your_name5.outdate_conditions: y

days_of_week: fr

start_times: "9:05"

# JIL script to test the AutoSys installation.# This script will re-direct a message to the# file named C:\tmp\your_name5.out.

update_job: your_name_lesson5

machine: machine_namecommand: echo AutoSys Lesson 5 teststd_out_file: "C:\tmp\your_name5.out"date_conditions: y

days_of_week: fr

start_times: "9:05"



The Event Processor interprets the new lines in the script in the followingway:

Line Summary5 JIL Sub-Command — Update the existing job in the database.

The your_name_lesson5 job is already exists in the database,but you are modifying it. Therefore, the Event Processormust know to update the job definition in the database.

9 Date Conditions Attribute — Indicates that there are dateand/or time conditions specified for this job (i.e., y meansthat there are date/time conditions).

10 Days Attribute — Run the job on this day of the week (i.e., frmeans run the job on Friday). For this attribute, you can usethese values: mo, tu, we, th, fr, sa, or su.

11 Start Time Attribute — Run the job at this time of day (i.e.,"9:05" means run the job at five minutes after nine o’clockin the morning). Note that the start_times value uses a24-hour format, and it is enclosed in quotes. The quotesprevent the Event Processor from interpreting the colonincorrectly.


To save to the database these new date and time conditions:

3. At the command prompt, enter the following command:jil < your_name_lesson5.jil

The following message should display to standard output, indicating thatthe job has been successfully re-submitted to the AutoSys Event Server:

______________________________________

Insert/Updating Job: your_name_lesson5Database Change WAS Successful!_______________________________________

Exit Code = 0_______________________________________

Now the Command Job named your_name_lesson5 does have starting parameters.And as a result, you do not have to run it manually. As soon as the startingparameters have been satisfied, the Event Processor will run the job.

Before continuing with the lesson, wait until the start_times value youspecified has arrived. If you are running an autolog -e process in a commandprompt window, you can view the Event Processor event activity in that window,and you will know when the job runs and completes. Once the job runs, thespecified message should be re-directed to the your_name5.out file.



To view the your_name5.out file:

At the command prompt, enter the following command:

UNIX:cat /tmp/your_name5.out




Specifying Job Dependency Conditions 5

Now you will specify a job dependency condition for your Command Job. Thescenario is as follows:

� You will define a new Command Job your_name_depjob5 and specify that itrun only when your_name_lesson5 has completed successfully.

� You will save your_name_depjob5 to the AutoSys Event Server.

� You will change the date/time conditions for your_name_lesson5 and re-savethe job to the Event Server (database).

When your_name_lesson5 runs and completes successfully, the Event Processorwill determine that the your_name_depjob5 job should be run, and, as a result, runthe job. Then, the your_name_depjob5 job will re-direct a message to theyour_name_depjob5.out standard output file.


Delete the standard output file created in the previous exercise. To do this, enterthe following at the command prompt:



To define a dependent job:

1. Start up your favorite editor, and create the following file in the tmpdirectory:

your_name_depjob5.jil

2. Using the editor, enter the following JIL script:



UNIX:

NT:

The Event Processor interprets the lines in the script in the following way:Line Meaning1-3 Comments about the script.4 Blank — Not read.5 JIL Sub-Command — The name of the new job to insert into

the database is your_name_depjob5.6 Machine Attribute — The agent machine on which the job

should run. The machine_name value must be a validAutoSys agent machine at your site.

7 Condition Attribute — This job should not run until theyour_name_lesson5 job has run successfully.

8 Command Attribute — The command the job should run onthe agent machine. In this case, this attribute value is thedate or ntgetdate command.

9 File Redirection Attribute — The file to which standardoutput should be redirected.


# JIL script to demonstrate a job dependency.# This job will run only when the job named# your_name_lesson5 has completed successfully.

insert_job: your_name_depjob5

machine: machine_name

condition: success(your_name_lesson5)command: datestd_out_file: /tmp/your_name_depjob5.out

# JIL script to demonstrate a job dependency.# This job will run only when the job named# your_name_lesson5 has completed successfully.

insert_job: your_name_depjob5

machine: machine_name

condition: success(your_name_lesson5)command: ntgetdatestd_out_file: "C:\tmp\your_name_depjob5.out"



To save your_name_depjob5 to the AutoSys database:

4. At the command prompt, enter the following:jil < your_name_depjob5.jil

The “Insert/Updating Job:...” message should display tostandard output.

To change the date/time conditions for your_name_lesson5:

1. Start your favorite editor and open the following file:your_name_lesson5.jil

2. Using the editor, modify the JIL script to indicate a time that is a fewminutes away from the current time for the start_times attribute.



4. At the command prompt, enter the following:jil < your_name_lesson5.jil

This re-submits the job definition for your_name_lesson5, with its newdate and time conditions, to the Event Server (database).The “Insert/Updating Job:...” message should display.

Before continuing with the lesson, wait until the start_times value youspecified has passed. You can view the Event Processor activity in the commandprompt window that is running the autolog -e command.

After the your_name_lesson5 job has completed successfully, theyour_name_depjob5 job will start and re-direct the current system date into theyour_name_depjob5.out file. As a result, you will be able to view the filescreated by this job stream.






2. At the command prompt, enter the following:UNIX: cat /tmp/your_namedepjob5.out

NT: type C:\tmp\your_namedepjob5.out

You should see the system date displayed.

Removing Jobs and Files


Removing Jobs and Files 5

If you are moving on to the next lesson, keep the job definitions and files youcreated. You will use them later in this tutorial.

If you are repeating this lesson, you must first remove from the AutoSys databasethe job definitions that you created the first time. You must also delete the filescreated by these jobs when you ran them during the lesson.

Deleting Jobs 5

These are the job definitions that you must delete from the database:

� your_name_lesson5

� your_name_depjob5

To delete these jobs:

1. At the command prompt, enter the following command:jil

2. At the jil prompt, enter the following command:delete_job: your_name_depjob5

3. Enter the following command:delete_job: your_name_lesson5

4. Enter the following command:exit

This exits the jil command mode. The standard output message will tellyou whether the job definitions were successfully deleted.

Deleting Files 5

When the jobs in Lesson 5 are run, they create some files on your system in thefollowing directory:

UNIX:/tmpNT:C:\tmp

These are the files in this directory that you must delete:

� your_name5.out

� your_name_lesson5.jil

� your_name_depjob5.out

� your_name_depjob.jil

Review


To delete these files:

Enter the following command:UNIX: rm /tmp/your_name*

NT: del C:\tmp\your_name*

Review 5

� The AutoSys Job Information Language (JIL) is a proprietary scriptinglanguage that can be used to create job definitions.

� You can use JIL sub-commands to create, modify, and delete job definitions.

� These are the five JIL sub-commands used to create, modify, and delete jobdefinitions: insert_job, update_job, delete_job, delete_box, andoverride_job.

� You can use JIL attribute statements to define when, where, and how a jobshould run.

� Even though JIL has a number of JIL job attribute statements, you will use thefollowing basic attribute types most often: Job Name, Job Type, Machine Name,Starting Conditions, and File to Watch For.

� You can create or modify a job definition by redirecting a JIL script file usingthe jil command, or by using JIL sub-commands and attribute statements atthe jil>> prompt.

� When writing a JIL script and entering sub-commands and attributestatements, there are seven syntax rules you must follow.

� When using AutoSys commands on NT, you must use the AutoSys InstanceCommand Prompt window.

See Also


See Also 5

� For a list of AutoSys job attributes, refer to Chapter 4, “Job Attributes,” in theAutoSys User Manual for your platform.

� For more information on using JIL to define jobs, refer to the AutoSys UserManual for your platform.

� For a complete listing of JIL sub-commands and job definition attributes, referto the AutoSys User Manual for your platform.

� For information on how to use AutoSys commands, refer to the AutoSys UserManual for your platform.

� For a complete listing of AutoSys commands, refer to the AutoSys User Manualfor your platform.

� For information on how to assign the machine job attribute, as well as otherjob attributes, to implement job load balancing and queuing, see 7 in thistutorial, then refer to the AutoSys User Manual for your platform.

Lesson

Monitoring and Managing AutoSys 6-1

6 Monitoring andManaging AutoSys

This lesson describes how to access the AutoSys features used for monitoring andmanaging AutoSys jobs and alarms.


Operator Console 6

The Operator Console refers to a collection of dialogs used for monitoring andmanaging AutoSys jobs in real-time. When you first access the Operator Console,the Job Activity Console is displayed. From this console you can view all the jobsdefined to AutoSys, along with a brief description and the current status. Inaddition, you can access dialogs to view the job definition and job dependencies.Also available from the Job Activity console are the Job Selection, Alarm Manager,and Alarm Selection dialogs.

You can use the Job Selection dialog to determine, at any time, which jobs you wantto view, based on various parameters such as current job states, job names, and thespecific machines on which jobs are defined to run.


� Operator Console Conceptual/Hands-On

� Job Activity Console Conceptual/Hands-On

� Job Selection Dialog Conceptual/Hands-On

� AutoSys Alarms Conceptual/Hands-On

� Alarm Manager Dialog Conceptual/Hands-On

� Alarm Selection Dialog Conceptual/Hands-On

Operator Console


You can select any job and view more detailed information about it, including itsstarting conditions, its dependent jobs, and various types of reports that describethe progression of the job run. You can even display the job definition and, if youhave the required permissions, make changes to the job.

The Operator Console consists of the following elements:

� Job Activity Console — The primary interface to the Operator Console, and it isused for monitoring jobs.

� Job Selection dialog — Used to specify which jobs you want to view.

� Alarm Manager dialog — Allows you to browse any alarms that have occurred,and to acknowledge (and log a response to) those alarms.

� Alarm Selection dialog — Provides a way for you to specify which alarms youwant to view at any given time.

Starting the Operator Console 6

To start the Operator Console:

At the GUI Control Panel, single-click on the Ops Console button.

You can also start the Operator Console by typing the following at the commandprompt: autocons &

The Job Activity Console appears, as shown in Figure 6-1.

Note: The Job Activity Console is blank when it initially displays. In order forjobs to be displayed, as they are in Figure 6-1, you must first use the Job Selectiondialog, as explained on page 6-11.

Job Activity Console


Figure 6-1 Job Activity Console

By default, the information displayed in the Job Activity Console is updated every5 seconds with information retrieved from the database. To prevent the screenfrom being updated constantly, the console starts up in Freeze Frame mode. For anexplanation of how to toggle Freeze Frame mode, see “Freeze Frame” onpage 6-10.

Job Activity Console 6

The Job Activity Console contains a menu bar and the following three regions:

� Job List — Displays a list of all jobs stored in the database, or displays the jobsyou specified in the Job Selection dialog.

� Currently Selected Job — Displays more detailed information about thecurrently selected job.



� Control Area — The left side of this area contains buttons that act on thecurrently selected job; the middle of this area contains buttons that providecontrol functions for the Console screen; the right side contains the Alarmbutton, which displays the Alarm Dialog, and the Exit button to exit the JobActivity Console.

Menu Bar 6

At the top of the Job Activity Console is the menu bar, containing three menus:File, View, and Options.

File menu—Contains the Exit option, which functions exactly like the Exit buttonin the Control area. Before exiting, a verification dialog displays asking you toconfirm. If you confirm, the Job Activity Console is closed. If the Alarm Manageris open, it is closed as well.

View menu—Contains the Select Jobs option, which displays the Job Selectiondialog.

Options menu—Contains the Console Clock Perspective option, which controlsthe time perspective of the display. This option gives you three choices: ServerTime, Current Job Time, or Local Machine Time.

Job List 6

The Job List region displays a list of all the jobs defined to AutoSys, and thisdisplay is subject to the job selection criteria currently in effect. Each entry in theJob List contains the following information about a single job:

� Job name.

� Description.

� Current status.

� Command defined for this job, if it is a Command Job; the file to watch for, if itis a File Watcher Job; and nothing, if it is a Box Job.

� Machine on which the job is defined to run.

The entries in the Job List provide a snapshot of the entire instance, across multiplemachines.

To inspect the jobs you defined in Lessons 4 and 5:

1. In the View menu, select the Select Jobs option. This displays the JobSelection dialog.

2. In the Job Selection dialog, locate the Job Name field and enteryour_name*. Ensure the All Statuses and All Machines options areselected (these are the default settings). Then, to begin the search anddismiss the dialog, click OK.



3. A list of jobs beginning with your_name should appear in the Job List inthe Job Activity Console. Look for the following jobs (you can use thescroll bar to view the entire list if needed):

– your_name_lesson4, defined in Lesson 4

– your_name_depjob4, defined in Lesson 4

– your_name_watcher, defined in Lesson 4

– your_name_wdone, defined in Lesson 4

– your_name_box, defined in Lesson 4

– your_name_job1, defined in Lesson 4

– your_name_job2, defined in Lesson 4

– your_name_lesson5, defined in Lesson 5

– your_name_depjob5, defined in Lesson 5

You can select any job in the Job List by single-clicking on the line on which thejob’s information displays. The job you click on becomes the currently selected job,and detailed information about the job appears in the Currently Selected Jobregion.

To inspect more detailed information about a job you have defined:

In the Job List, single-click on a job, and the job description appears in theCurrently Selected Job region.

Currently Selected Job 6

The Currently Selected Job region of the window displays more detailedinformation about the most recent execution of the currently selected job, such asits start time and exit code. This information is updated with each execution of thejob.

This area also displays the job’s entire starting condition, as specified in the jobdefinition, as well as the atomic conditions—which are the basic components of anoverall condition.

To view more detailed information for a job you have defined:



1. In the Job List, single-click on the your_name_lesson4 job. This job thusbecomes the currently selected job.

2. In the Currently Selected Job region, check the following fields:

To view the starting conditions for a job you have defined:

1. In the Job List, single-click on the your_name_depjob4 job. This jobbecomes the currently selected job.

2. In the Currently Selected Job region, verify that the Starting Conditionsfield shows the following:

success(your_name_lesson4)

Control Area 6

The Control area at the bottom of the Job Activity Console contains the following:

� Action buttons, which act on the currently selected job.

� Control buttons, which provide control functions for the console.

� The Alarm button, which indicates an alarm has occurred and accesses theAlarm Manager dialog.

� The Exit button, which dismisses the Job Activity Console.

Action Buttons 6

The left side of the Control area is the Actions area containing a group of buttonsthat can be clicked to initiate certain actions on the currently selected job or jobs.By clicking the appropriate button, you can issue an event that will do one of thefollowing:

� Start a job

Table 3:

Field Display

Command UNIX: /bin/echo “AutoSys Lesson 4 test”NT: echo AutoSys Lesson 4 test”

Start Time The date and time the job started.

End Time The date and time the job ended.

Run Time The amount of time it took for the job to run.

Status Success

Exit Code 0

Machine The machine on which the job ran.



� Kill a job

� Force a job to start

� Place a job on hold

� Take a job off hold

In each of these cases, a dialog asks you to confirm the action. If you confirm, theevent is processed immediately.

In addition, there is the Send Event button, which if clicked displays the SendEvent dialog that allows you to send any type of event.

The last column of buttons are user-configurable. You can associate any commandwith these buttons, and specify your own button labels.

You can use any of these action buttons to issue events on multiple AutoSys jobs.To do this, you select multiple jobs from the job list area, and then click theappropriate button, or open the Send Even dialog to issue the event.

To select multiple jobs from the Job List area of the Job Activity Console:

To select a contiguous group of jobs:

Single-click on the first job then press <Shift>, and single-click on the lastjob to be selected.

To select a noncontiguous group of jobs:

Single-click on the first job, then press <Control>, and single-click onadditional jobs in any order.

To deselect a job:

Press <Control> and single-click on the job.

Send Event Dialog 6

The Send Event dialog allows you to do the following:

� Send any event that can be sent manually in AutoSys.

� Select the various event parameters you want to specify when sending theevent.

� Cancel an event that has been scheduled to occur in the future.

To display the Send Event dialog:

1. In the Control area, click the Send Event button.The Send Event dialog appears, as shown in Figure 6-2.



Figure 6-2 Send Event Dialog

Choose an event type using the radio buttons at the top of the dialog. Just belowthese buttons is the Job Name field, which displays the name of the currentlyselected job. If desired, you can enter a different job name in this field.

You can specify when the event is to take effect: either immediately (the default)or at some future date and time. Note that the current time and date are providedas defaults for your convenience. Use the A.M. and P.M. radio buttons if you wantto specify the time using a 12-hour format. By default, a time with less than 13 inthe hours is considered a.m., while any larger value is considered p.m.

The Comment field lets you enter text to be associated with this event in thedatabase. This field is for documentation purposes only. For example, if you forcea job to start, you can provide an explanation about why this was necessary.

The Execute button of the dialog executes, or sends, the event. The Cancel buttoncancels the event that was about to be sent. When either button is clicked, the SendEvent dialog is dismissed.

Note: The other fields in this dialog are not used for this exercise. For moreinformation on the fields, refer to the AutoSys User Manual for your platform.

To send an event for a job you have defined:

1. In the Event Type region, select the Force Start Job radio button.Use this event to force start a job, overriding the starting parametersdefined for it.


3. Be sure the Now radio button is selected (this is the default setting).



4. At the bottom of the dialog, click the Execute button, then click OK in theconfirmation dialog. This action starts the your_name_lesson4 job.

The event buttons at the bottom of the Job Activity Console can also be used tosend events without accessing the Send Event dialog. However, all of the eventtypes are not available in this group of Action buttons, but they are available in theSend Event dialog.

To view information about the job you just started:

1. In the Job List, single-click on the your_name_lesson4 job. This jobbecomes the currently selected job.

2. In the Currently Selected Job region, note when the job started, ended,and its completion status. This status should be SUCCESS.

3. In the Control area, locate the Reports region and select the Summarybutton to view the Summary report. Then select the Event button to viewthe more detailed Event report. (The Reports control area is described in“Reports” on page 6-10.)

Control Buttons 6

In the middle of the Control area, there are several push buttons that providecontrol functions for the Console screen.

Job Definition

The Job Definition button displays the Job Definition dialog, with the currentlyselected job already displayed. This allows you to quickly review the job’sdefinition, and change it if necessary (and if permissions allow).

Dependent Jobs

The Dependent Jobs button displays the Dependent Jobs dialog which contains alist of all the jobs that are directly dependent on the currently selected job. Thisallows you to quickly see which jobs are dependent upon the current job. Inparticular, it shows which jobs will not run until the current job completes. This isuseful if the currently selected job is running late and you need to determine theimpact of the situation.

To display the Dependent Jobs dialog:

1. In the Control area, locate the Show area, and click the Dependent Jobsbutton.The Dependent Jobs dialog appears, as shown in Figure 6-3. Becauseyour_name_lesson4 is the currently selected job, this dialog displays theone job dependent on it, your_name_depjob4.



Figure 6-3 Dependent Jobs Dialog

2. To dismiss the dialog, click Close.

Freeze Frame

Initially, the Job Activity Console displays in Freeze Frame mode. This mode“freezes” the console display, which otherwise is regularly updated. By default,the display is updated every 5 seconds (directions to change this setting are in theAutoSys User Manual for your platform). In Freeze Frame mode, all processingcontinues normally, but the screen is not refreshed. When Freeze Frame mode isoff, the console displays job progressions in real-time. To activate and deactivateFreeze Frame mode, select or deselect the Freeze Frame radio button.

Reports

You can choose a type of report from the Reports area options, and the report willappear on the right side of the Currently Selected Job region in the Reports area.This area displays a real-time report that presents job run information in the sameformat as that produced by the autorep command. You can choose one of thefollowing report types:

� Summary — Displays a one-line synopsis of the last or current execution of thejob. This shows the job name, timestamp of the last start and last end of the job,status, job run number and number of tries (separated by a slash), and priority(if the job is in QUE_WAIT status) or exit code (if the job completed).

� Event — Displays a detailed report listing all the events and statuses from thelast or current execution of the job. Figure 6-1 on page 6-3 shows an EventReport.

� None— Displays no report.

Summary and Event reports are run automatically each time the dialog isrefreshed (by default, the refresh interval is every 5 seconds). If the Event report ischosen, you can watch the real-time progression of a job, observing, as they occur,the arrival of the various events, such as the job starting, running, and completing.

Job Selection Dialog


To view a Summary Report for a job you have defined:

1. In the Job List, single-click on the your_name_lesson4 job. This jobbecomes the currently selected job.

2. In the Control area at the bottom of the window, locate the Reports area,and select the Summary radio button. This action displays the SummaryReport.

To view an Event Report for a job you have defined:

1. In the Job List, single-click on the your_name_depjob4 job. This jobbecomes the currently selected job.

2. In the Control area at the bottom of the window, locate the Reports area,and select the Event radio button. This action displays the Event Report.

Alarm Button 6

The Alarm button serves both as an indicator that a new alarm has been detectedand as a way to display the Alarm Manager dialog. When a new alarm occurs(either operator- or system-generated), the Alarm button turns red. When youclick the button, its color returns to green and the Alarm Manager dialog isdisplayed. Note that you can invoke the Alarm Manager by clicking the button,even when the Alarm button is green.

Exit Button 6

The Exit button is used to terminate the Job Activity Console, including the AlarmManager, if it is displayed. When you click this button, a verification dialog asksyou to confirm the exit before closing the console.

Job Selection Dialog 6

The Job Selection dialog provides a way for you to specify which jobs you want toview, filtering out all other jobs. It lets you specify the jobs you want to view byname, job status, and machine.

To display the Job Selection dialog:

From the Job Activity Console, choose the Select Jobs option from the View menu.The Job Selection dialog appears, as shown in Figure 6-4.



Figure 6-4 Job Selection Dialog

Specifying a Job 6

Selecting All Jobs will display in the Job Activity Console all the jobs defined toAutoSys for that instance. You can filter which jobs to display by specifying a jobname, job status, or the machine on which the job is to run.

When specifying a job name in the Job Name field, you can either enter the entirename or you can enter a partial name with the asterisk * wildcard character. Youcan use this wildcard in more than one character position. For example, the *a*string would match all job names that have an a in them.

In a similar fashion, you can specify a Box Job name in the Box Name field to selecta box and all the jobs in the box. When boxes and their contained jobs are displayedin the Job List, each nested level is indented two spaces. When specifying a Box Jobname, you can also include the wildcard character.

The Box Levels field governs how many levels of nesting is displayed for eachmatched box. The default setting of All displays all jobs, and all levels of nestinginside each job. If you want to view only the Box Jobs themselves, enter 0 in theBox Levels field. If you want to view the top-level boxes and only the first-levelnesting of jobs and boxes inside each box, enter 1 in the Box Levels field.



To Display the jobs that you have already defined:

1. In the Job Name field, enter the following: your_name_*

2. Click the Apply button.

3. In the Job Activity Console (behind the dialog), check the Job List andnotice that all the jobs beginning with your_name are listed.

To Display the Box Job that you have already defined:

1. In the Box Name field, enter the following: your_name_boxLeave the default setting of All Box Levels.

2. Click the Apply button.

3. In the Job List (behind the dialog), notice that the job namedyour_name_box is listed, as well as the names of the jobs you placedinside this box.If you are using AutoSys on NT, this Job List would look similar to thatshown in Figure 6-5.

Figure 6-5 Displaying a Box Job

Specifying Jobs by Status

From the Job Selection dialog, you can select jobs based on their current status,such as STARTING, RUNNING, or INACTIVE. You can select any combination ofstatuses. The default behavior is to display all statuses.

Specifying Jobs by Machine

From the Job Selection dialog, you can select jobs based on the name of the machineon which they are defined to run. On the right side of this dialog is a list of all themachines that are known to AutoSys for that instance. That is, all machines that arereferenced in a job or virtual machine definition, or which have run an AutoSysjob. From this list, you can choose one, several, or all machines (all machines is thedefault setting).



Sorting the Specified Jobs 6

The Job Selection dialog lets you specify the order in which the jobs should belisted. You can select one of the following sort criteria:

� Start Time — Sort jobs by the start time for the last (most recent) execution ofthe job.

� End Time — Sort jobs by the ending time for the last (most recent) execution ofthe job.

� Job Name — Sort jobs by name in ascending alphanumeric order.

� Job Status — Sort jobs by their current status in ascending alphabetical order.

� Machine Name — Sort jobs by the name of the machine on which they aredefined to run, in ascending alphabetical order.

� Unsorted — Display jobs in the order in which they were created, whichcorresponds to the order in which they exist in the database. This is the defaultsetting.

Note: You should choose the Unsorted option when selecting jobs by Box Name,because the creation order can control the order in which they are started. If a BoxJob’s contained jobs do not have a specified starting condition, the Event Processorwill start the Box Job based on its starting condition, and then start the containedjobs in their creation order. Therefore, in this situation, the Unsorted criteria canprovide the starting order information for jobs in a box.

Setting the Job Selection Criteria 6

To make the job selection criteria take effect:

1. Select the desired selection criteria.

2. To apply the sorting and dismiss the dialog, click OK.

Note: If you click the Apply button, the sorting criteria is changed, but the JobSelection dialog stays open. If you click Cancel, the changes to the sorting criteriaare not made, and the Job Selection dialog closes.

AutoSys Alarms


AutoSys Alarms 6

Alarms are special events that notify you about important situations that requireyour attention. For example, if a set of jobs are dependent on the arrival of a file,and the file is long overdue, someone should investigate the situation and resolvethe problem.

These are some important aspects of alarms:

� Alarms are informational only. Any action taken due to a problem is initiated bya separate action event.

� Alarms are system messages about a detected problem.

� Alarms are sent through the AutoSys system as an event.

Preparation 6

In order to view an alarm, you will modify an existing job definition to force it togenerate an alarm. To do this, you need to perform the steps described in thefollowing sections.

In the Job Activity Console:

1. In the Job List, select the your_name_lesson4 job.

2. Access the Job Definition dialog by clicking the Job Definition button inthe Control area at the bottom of the window. This action displays the JobDefinition dialog with your_name_lesson4 as the selected job.

At the Job Definition Dialog:

3. In the Command to Execute field, replace the current entry with thefollowing:

bad_command

This will cause the job your_name_lesson4 to fail. As a result, an alarmcalled JOBFAILURE will be generated.

4. At the top of the Job Definition dialog, click the Save button to save thechanged job definition to the AutoSys database.

5. At the top of the dialog, click the Exit button.

At the Job Activity Console:

6. In the Job List, ensure that the job your_name_lesson4 is still the currentlyselected job.

7. If you wan to view an Event Report while this job runs, select the Eventradio button in the Reports area. Also ensure the Freeze Frame button isdeselected. Then, when the job runs, the events are displayed in the EventReport area.

AutoSys Alarms


8. In the Control area at the bottom of the window, click the Force Start Jobbutton, and confirm the action. This process overrides all startingconditions and starts the your_name_lesson4 job immediately.

This job will not be able to run the bad_command, and thus it will fail and generatean alarm. The Alarm button at the lower-right of the console should change fromgreen to red indicating that an alarm has been received. You can view the alarmusing the Alarm Manager dialog.

Alarm Manager Dialog


Alarm Manager Dialog 6

The Alarm Manager allows you to do the following:

� View alarms as they arrive

� Acknowledge alarms

� Change the alarm status from Open to Acknowledged or Closed

This dialog’s features provide a useful tracking mechanism for all the alarmsissued on your system.

To display the Alarm Manager dialog:

In the lower-right corner of the Job Activity Console, click the Alarm button. TheAlarm Manager dialog appears, as shown in Figure 6-6.

Figure 6-6 Alarm Manager Dialog



Menu Bar and Regions 6

The Alarm Manager dialog has a menu bar and the following three regions:

� Alarm List — Displays a list of alarms. By default, all Open and Acknowledgedalarms are shown. The alarms in the Closed State can be displayed also, ifindicated in the Alarm Selection dialog.

� Currently Selected Alarm — Displays the currently selected alarm, the responseto the alarm (if one was entered) and the alarm state.

� Control — Provides control functions for the Alarm Manager screen.

Menu Bar 6

The Alarm Manager menu bar, at the top of the dialog, contains the View andOptions menus.

View—Provides two options. The Select Alarms option displays the AlarmSelection dialog (discussed on page 6-20). The Reset to Defaults option resets thealarm selection criteria to their default settings and updates the Alarm Managerdialog accordingly.

Options—Contains the Sound On option, which you can toggle on or off byselecting the option. When on, this feature plays sound clips associated withalarms whenever a new alarm is generated.

Alarm List 6

The Alarm List region of the dialog displays a list of all the alarms that arecurrently in the system, subject to your selection criteria. The default behavior is todisplay all Open and Acknowledged alarms of any type, regardless of the timethey were generated.

Each entry in the Alarm List corresponds to a single alarm and shows thefollowing information:

� Alarm type.

� Name of the job for which the alarm was generated.

� Date and time the alarm was generated.

� Current state of the alarm.

� Any comment associated with the alarm at the time it was generated. Thesecomments can be system-generated (by the Event Processor) or user-generated(a comment attached to a sendevent command).

The Alarm List is chronological; the newest alarms appear at the top of the list,older ones appear below.



You can select any alarm in the Alarm List by single-clicking on it. This actioncauses the alarm to become the currently selected alarm, and the window displaysmore detailed information about it in the Currently Selected Alarm region.

To inspect the alarm for the failure of your_name_lesson4:

1. Check the Alarm List for the JOBFAILURE alarm that was just generatedfor your_name_lesson4. It should be at or near the top of the Job List.

2. In the Alarm List, single-click on the JOBFAILURE alarm foryour_name_lesson4.

Currently Selected Alarm 6

The Currently Selected Alarm region of the dialog displays the currently selectedalarm, and lets you enter a response in the Response edit box.

The Response edit box accepts multiple lines of text. The entered text isautomatically word-wrapped, with lines breaking at appropriate spaces. You canuse the mouse to edit text. In addition, you can use the arrow and backspace keysas well as the <Tab> and <Enter> keys.

The User field, beneath the Response edit box, shows the user who invoked theAlarm Manager. This read-only field shows which user responded to the alarmfield.

The Alarm State region lets you change the alarm state to Acknowledged orClosed. Once an alarm is changed from the Open state, you cannot put it back inthe Open state.

To register a response and change the state of the alarm generated foryour_name_lesson4:

1. In the Response edit box, enter the following comment:

Alarm generated intentionally for tutorial.

2. In the Alarm State area, single-click on the Acknowledged radio button.

3. At the bottom-center of the dialog, click Apply. This action saves thealarm to the database, but the dialog remains open.Note that typically the Apply button is used to register changes. Thisapproach allows you to keep the Alarm Manager open to continuemonitoring alarms.

Alarm Selection Dialog


Control 6

The Control region at the bottom of the of the Alarm Manager dialog contains thefollowing buttons:

� Freeze Frame — Suspends or resumes, when toggled, the automatic refreshingof the Alarm Manager dialog.

� Select Job — Makes the job associated with the currently selected alarm thecurrently selected job in the Job Activity Console.

� New Alarm — Turns red to alert you when a new alarm arrives.

Alarm Selection Dialog 6

The Alarm Selection dialog lets you control which alarms are displayed. Alarmscan be selected by type of alarm, state of alarm (Open, Acknowledged, or Closed),and by the date and time the alarm occurred.

To display the Alarm Selection dialog select the Select Alarms option from theView menu at the top of the Alarm Manager dialog. The Alarm Selection dialogappears with the default settings, as shown in Figure 6-7.

Figure 6-7 Alarm Selection Dialog

The Alarm Selection dialog is divided into the following three regions:

� Alarm Selection Area — Allows you to specify what types of alarms to displaybased on alarm types, alarm states, or the times the alarms were generated.

� Control Area — Provides buttons to initiate the alarm selection, and to close thedialog.

Alarm Selection Dialog


Select by Type 6

In the Select by Type region of the dialog, a list of all possible alarm types isdisplayed. From this list, you can select one, several, or all types of alarms. Thedefault is to select all alarm types.

To select a contiguous group of alarms:

Single-click on the first alarm then press <Shift>, and single-click on thelast alarm to be selected.

To select a noncontiguous group of alarms:

Single-click on the first alarm then press <Control>, and single-click onadditional alarms in any order.

To deselect an alarm:

Press <Control> and single-click on the alarm.

To select only the alarms that are of the type JOBFAILURE:

1. In the Select by Type region, in the list box, single-click on JOBFAILURE.

2. At the bottom-left of the dialog, click OK. This action closes the AlarmSelection dialog, and all jobs with a JOBFAILURE alarm appear in theAlarm Manager Alarm List. The alarm for the job your_name_lesson4should be listed.

Select by State 6

You can also select alarms by the state of the alarm. You can select one or morestates by toggling on the Open, Acknowledged, or Closed buttons. You can selectthe All States button to select all states. The default is to display all Open andAcknowledged alarms.

Select by Time 6

By default, alarms are shown regardless of the time they were generated. You canchoose to display only alarms that were generated during a specific date and timewindow. Fields are provided to specify a From Date, From Time, To Date, and ToTime. You can specify dates without times. However, you cannot specify timeswithout dates.

As shown in Figure 6-7 on page 6-20, the current system date and time areautomatically filled in for your convenience.

Review


To exit the Operator Console and complete this lesson:

1. At the Alarm Manager dialog, at the bottom-left corner, click OK.

2. At the Job Activity Console, at the bottom-right corner, click Exit.

3. In the dialog that appears asking your to confirm the exit, click Yes.

Review 6

� The Operator Console refers to a collection of dialogs for monitoring andmanaging AutoSys jobs in real-time. You can view AutoSys jobs, whether theyare currently active or not.

� You start the Operator Console by clicking the Ops Console button in the GUIControl Panel (or by entering autocons at the command prompt).

� When you first access the Operator Console, the Job Activity Console isdisplayed. From this console you can view AutoSys jobs along with a briefdescription and the current status. In addition, you can access dialogs to viewthe job definition and job dependencies.

� The Job Selection dialog lets you specify which jobs you want to view, filteringout all other jobs. You can select jobs by name, job status, and machine on whichthe job is defined to run.

� You can use job selection criteria at any time to control which jobs you want toview based on various parameters such as current job state, job name, and themachine on which the job is defined to run.

� You can select any job in the Job Activity Console to make it the currentlyselected job. The console displays more detailed information about the job inthe Currently Selected Job region. You can initiate events on the currentlyselected job. In addition, you can access the Job Definition dialog directly fromthis console, allowing you to view the entire job definition and even edit it (ifthe required permissions are set).

� The Report region in the Job Activity Console displays a real-time report of thecurrent (or most recently completed) run of the currently selected job.

� The Send Event dialog is accessed from the Job Activity Console. It provides themeans to send events that can be sent manually with AutoSys.

� The Alarm Manager is accessed from the Job Activity Console. It allows you toview alarms as they arrive, acknowledge them, and change their status fromOpen to Acknowledged or Closed.

� The Alarm Selection dialog lets you control which alarms are displayed in theAlarm Manager dialog. Alarms can be displayed by type of alarm, state ofalarm, and by the date and time the alarm occurred.

See Also


See Also 6

� For more information on the Operator Console, refer to the AutoSys UserManual for your platform.

� For information on how to associate commands with the buttons on the JobActivity Console, refer to the AutoSys User Manual for your platform.

� For information on customizing other aspects of the Operator Console, refer tothe AutoSys User Manual for your platform.

� For information on job executing permissions, refer to Chapter 2 in the AutoSysUser Manual for your platform.

Lesson

Queuing and Load Balancing 7-1

7 Queuing andLoad Balancing

This lesson describes how to define real and virtual machines in order to balancejob loads across physical machines.


Introduction 7

AutoSys provides both queuing and load balancing as a way to distribute jobs tomachines with sufficient processing power to run them. This is done by definingto AutoSys both real and virtual machines on which you will be running jobs. Thislesson explains how to accomplish this.


� Real Machines Conceptual

� Virtual Machines Conceptual

� Defining Real Machines Conceptual

� Defining Virtual Machines Conceptual

� Job Load Balancing Conceptual

Real Machines


Real Machines 7

In the AutoSys environment, a real machine is any machine that has:

� Been identified in the appropriate network database so that AutoSys can accessit. For UNIX, this is a physical CPU that has identified in /etc/hosts; forNT, this is a network host that is accessible over the network using the TCP/IPprotocol.

� Undergone a Remote Agent software installation, and a client license keyinstallation, so that AutoSys can run jobs on it.

The above two conditions are all that is required for a real machine to run AutoSysjobs. However, for AutoSys to perform intelligent load balancing and queuingwhile executing jobs, it needs to know the relative processing power of the variousreal machines. You can define the real machines to AutoSys and specify thesevalues. In addition, AutoSys provides both load balancing and queuing by way ofthe logical construct called virtual machines.

Virtual Machines 7

A virtual machine is comprised of two or more real machines, in whole or in part(or a combination of both). All real machines within a virtual machine must be ofthe same type, either NT or UNIX—not a mix of the two types.

By defining virtual machines to AutoSys, and then submitting jobs to run on thosemachines, you can implement runtime resource policies that AutoSys can executein a multi-machine environment.

Defining Machines to AutoSys 7

You define both real and virtual machines to AutoSys by using machine attributestatements within a JIL script. The following JIL sub-command defines a real orvirtual machine to AutoSys:

insert_machine: machine_name

The following JIL machine attributes are used when defining machines:

� type — Can be either r for UNIX real, v for UNIX virtual, or n for NT (real orvirtual).

� machine — Specifies a real machine name to be inserted in a virtual machine.

� max_load — For real machines only, used for load balancing.

� factor — For real machines only, used for load balancing.

Defining Machines to AutoSys


You need to define real machines to AutoSys only if they fit into one of thefollowing categories:

� Require a max_load or factor attribute to be set for them. (These attributesare discussed in the next sections.)

� Are to be included in a virtual machine.

Conversely, virtual machines must be defined before they can be used.

Load balancing and queuing can be done only if real and virtual machines havebeen defined to AutoSys using the JIL machine attribute statements mentionedabove. The max_load and factor attributes are used when defining realmachines, and they are required if you want to implement load balancing andqueuing.

Specifying Machine Load (max_load) 7

The max_load attribute can be defined only for real machines. It describes howmuch of a load can be placed on a real machine, and it is specified with an arbitraryunit called a load unit. Any weighting scheme desired by the user can be used. Forexample, a load unit with a range of 10-100 would specify that machines withlimited processing power are expected to carry a load of only 10, while machineswith ample processing power can carry a load of 100. There is no directrelationship between the load unit value and any of the machine’s physicalresources. Therefore, you should develop conventions that are meaningful to you.The max_load machine attribute is illustrated in Figure 7-1.

Job Attributes and Load Balancing and Queuing

For load balancing to work, every defined job that will impact the load on amachine must be assigned a job_load job attribute, which defines the relativeload the job will place on a machine. Thus, a machine’s current load can be tracked,and overloading of a machine can be prevented. For example, if the max_load ona machine is “100” and the job_load for one job is “10”, then that job will use 10percent of the machine’s resources.

In addition, for job queueing to take place, the priority job attribute must alsobe assigned in the job definition. The priority attribute specifies the relativepriority of all jobs queued for a given machine. Without this attribute set, a job willrun immediately on a machine, and it will not be placed in the queue.

Defining Machines to AutoSys


Figure 7-1 Load Balancing using max_load

Specifying Relative Processing Power (factor) 7

The factor attribute can be defined only for real machines. It is another arbitraryvalue, but it describes the relative processing power of a machine. This attribute’svalue is a real number that can contain a decimal. It is used to weigh availablecycles on one machine against that of another. In fact, when AutoSys checks theavailable cycles on each machine, it multiplies the percent of free CPU cycles by thefactor in order to determine which machine has more relative processing poweravailable, as shown in Figure 7-2. Therefore, the factor value is typically anumber between 0.0 and 1.0.

Figure 7-2 Load Balancing using factor

Using max_load and factor 7

The max_load attribute is primarily intended to limit the loading of a machine. Aslong as a job’s load will not cause a machine’s max_load to be exceeded, thisattribute does not enter into the decision of where to run the job. Conversely, thefactor attribute is primarily intended to decide between machines for running ajob (when more than one machine is available).

Real Machine #2Real Machine #1 Real Machine #3

5010 80max_load

Will carry lessof a load

Will carry moreof a load

50MIPS

15MIPS

25MIPS

actualvalue

arbitraryvalue

Real Machine #2 Real Machine #1Real Machine #3

1 42

factor

availablefree cycles

.50 .25.15

relativeprocessingpower

.5 1

Can carrygreatest load

Can carryleast load

50MIPS

25MIPS

15MIPS

.3

Defining Real Machines


If these attributes are not specified in a real machine definition, they will default tothe values shown here:

max_load: none /* no limit */

factor: 1.0

Note: A virtual machine is comprised of real machines. Therefore, you do notspecify max_load and factor attributes explicitly in a virtual machinedefinition. They are specified in the definitions of the real machines that make upthe virtual machine.

Defining Real Machines 7

To define real machines to AutoSys, follow these basic steps:

1. Assign a machine name. This value must be the machine’s validhostname.

2. Assign a machine type, either r for real UNIX, or n for NT.

3. If you want to implement load balancing, assign a max_load and afactor attribute value.

For example, to define a UNIX machine named “ferrari”, with a max_load of100and a factor of .9, you would submit the following JIL statements at a jilprompt:

insert_machine: ferrari

type:r

max_load: 100

factor: .9

Deleting Real Machine Definitions 7

To delete a real machine definition, use the following JIL sub-command at the jilprompt:

delete_machine: ferrari

This example deletes the real machine definition for the machine named “ferrari”.

Defining Virtual Machines


Defining Virtual Machines 7

To define a virtual machine to AutoSys, you must follow these basic steps:

1. Assign a machine name.

2. Assign a machine type, either v for virtual UNIX or n for virtual NT.

3. Specify the real machines that will make up the virtual machine.

A virtual machine is the combination of two or more real machines. It can be agroup of machines, a subset of a machine, or both. Do not assign the max_loadand factor attributes to a virtual machine. You assign these attribute values toreal machines only.

The following example JIL statements define an NT virtual machine named“modena”, which is comprised of three real machines named “ferrari”, “lambo”,and “cobra”. This virtual machine is illustrated in Figure 7-3.

insert_machine: modena

type: n

machine: ferrari

machine: lambo

machine: cobra

Figure 7-3 Virtual Machine modena

Deleting Virtual Machines

You can delete real machines from a virtual machine definition, and you can deletethe virtual machine definition itself. To remove a real machine component from avirtual machine, you specify the virtual machine and the component you want toremove.

The following JIL statements remove the real machine named “lambo” from thevirtual machine named “modena”:

delete_machine: modena

machine: lambo


hostname ferrari lambo cobra

modena

Job Load Balancing


The definition for the real machine “lambo” remains intact; it is simply removedfrom the virtual machine “modena”.

To delete a virtual machine, you do not specify any of the component realmachines.

The following JIL statement deletes the virtual machine named “modena,” and allof its components:

delete_machine: modena

Job Load Balancing 7

When you define a Command Job, you use the job’s machine attribute to specifythe machine on which the job will run. By specifying a virtual machine, or a list ofreal machines, rather than a single real machine, you can implement simple loadbalancing. When load balancing is implemented, AutoSys checks the current workload of the real machines defined in the virtual machine (or of the real machines inthe specified list) and chooses the machine with the most available processingpower to run a given job.

In addition to load balancing, this feature is a useful way to ensure reliable jobprocessing. For example, if one of the machines is down, AutoSys will simply runthe job on another machine.

Load Balancing using Virtual Machines 7

The following example JIL script shows a job defined to run on an NT virtualmachine named “modena”:

insert_job: test_load

machine: modena

command: echo “Test Load Balancing”

job_load: 50

priority: 1

When a job is ready to start running, AutoSys will determine which of the realmachines specified in the virtual machine will be used to run the job. To determinethis, AutoSys will consider two things:

� The max_load defined for each real machine.

� The factor defined for each real machine.

Job Load Balancing


max_load

In this example, AutoSys will not use any of virtual “modena’s” componentmachines that have a max_load of less than 50, because the test_load job has ajob_load of 50. In addition, AutoSys would eliminate all machines that cannotcarry that load. That is, if a machine has a max_load of 80, but is currently runninga job with a job_load of 60, AutoSys would not use it to run the job at this time.

factor

Once it determines which machines do have ample load units available, AutoSyswould choose the machine to run on based solely on available processing power.To accomplish this, AutoSys determines the percentage of CPU cycles availableand multiplies it by the machine’s factor value. The machine with the largestresult is selected as the machine with the most relative processing cycles available.

Load Balancing using a List of Real Machines 7

Instead of specifying a virtual machine, you can specify a list of real machines inthe job’s machine attribute, as shown below:

machine: ferrari, lambo, cobra

When specifying a list of real machines, all machines must be NT or UNIX, not acombination of the two.

Example of Load Balancing 7

Figure 7-4 shows how AutoSys determines which machine will be used to run ajob. For simplicity, each machine in this example has enough load units availableto run the job, so AutoSys calculates the percentage of CPU cycles available andmultiplies it by the machine’s factor value. AutoSys selects the machine with thelargest result as the machine with the most relative processing cycles available.

Review


Figure 7-4 Determining Relative Processing Power

Review 7

� AutoSys provides ways to define both real machines and virtual machines inorder to handle load balancing and queuing.

� A virtual machine is the combination of one or more real (physical) machines,in whole or in part.

� For AutoSys to perform intelligent load balancing, it needs to know the relativeprocessing power of the various real machines. Two machine attributes areused to characterize real machines: max_load and factor.

� The max_load attribute describes how much of a load should be placed on amachine, and is specified with an arbitrary value called a “load unit.”

� The factor attribute describes the relative processing power of a machine,with an arbitrary value. This attribute’s value is a real number that can containa decimal. The factor attribute is used to weigh available cycles on onemachine against that of another machine.

� You use JIL to define both real and virtual machines to AutoSys. There are twomain JIL sub-commands for defining machines: insert_machine anddelete_machine.


hostname ferrari lambo cobra

Virtual Machine: modena

64 2

factor

availablefree cycles

.5.5 1

relativeprocessingpower 32

Chosen torun the job

2

See Also


� In order to implement simple load balancing, you must specify the followingattributes in the job definition:

� job_load — Specifies the relative load that a job will put on a machine.

� priority — Specifies the relative priority that a job has, relative to the otherjobs in the queue for a given machine.

� machine — Specifies a virtual machine or list of real machines.

See Also 7

� For more information on job load balancing and queues, refer tp the AutoSysUser Manual for your platform.

� For more information about the JIL sub-commands and attributes pertaining tomachines, refer to the AutoSys User Manual for your platform.

� For more information about the JIL sub-commands and attributes for definingjobs, refer to the AutoSys User Manual for your platform.

Index 1

IndexIndexIndexIndex

SymbolsSymbolsSymbolsSymbols

$AUTOUSER/config.$AUTOSERV 1-7

AAAA

ACTIVATED status 2-9

Advanced Features dialog 4-6

Alarm Manager dialog 6-15Alarm List region 6-17Control region 6-18Currently Selected Alarm region 6-18Freeze Frame button 6-18menu bar 6-17New Alarm button 6-18Select Job button 6-18

Alarm Selection dialog 6-19Select by State region 6-20Select by Time region 6-20Select by Type region 6-19

alarms 6-14Alarm Manager dialog 6-15Job Activity Console 6-11managing 6-15selecting 6-18viewing all 6-17viewing by state 6-20viewing by time 6-20viewing by type 6-19

attributes, jobdays_of_week 5-8file to watch for 5-4JIL types 5-3job_load 7-3machine to run on 5-3name 5-3priority 7-3start_times 5-8starting conditions 5-3type 5-3

attributes, machinefactor 7-2, 7-4max_load 7-2, 7-3type 7-2

autocons 6-2

autoping 1-8

autorep 1-8, 2-9

autosc 4-2

AUTOSERV 1-7

AUTOSYS 1-6

AutoSysAdministrator 1-7alarms 6-14commands 1-8Console Utilities 1-3database 1-3defined 1-1documentation Preface-1environment variables 1-6Event Processor 1-3, 1-5

2 AutoSys Tutorial

Event Server 1-3Graphical User Interface, see GUIinstance, defined 1-3machines 1-2Remote Agent 1-3, 1-5software components 1-3

AUTOUSER 1-7

BBBB

Box Jobs 3-5defined 2-8defining with GUI 4-20job stream, advanced example 3-7job stream, examples 3-5

CCCC

Calendar Manager dialog 4-2

chk_auto_up 1-8

client machine 1-2

Command Jobsdefined 2-6defining with GUI 4-5defining with JIL 5-5

commands 1-8autocons 6-2autoping 1-8autorep 1-8, 2-9autosc 4-2chk_auto_up 1-8delete_box 5-3delete_job 5-3delete_machine 7-6, 7-7insert_job 5-3insert_machine 7-2JIL 5-3JIL, sub-commands 2-2override_job 5-3sendevent 2-4update_job 5-3

concepts and skills Preface-2

conditionsdate/time

defining with GUI 4-11defining with JIL 5-8

dependencydefining with GUI 4-13defining with JIL 5-10

startingdefining with GUI 4-10defining with JIL 5-3, 5-8

configuration fileAutoSys 1-7

Console Utilities 1-3

Control Panel, GUI 4-2

conventions, used in manual Preface-4

DDDD

databaseAutoSys, see Event Serverenvironment variables 1-7

date/time conditions 2-3defining with GUI 4-11specifying with JIL 5-8

Date/Time Options dialog 2-3, 4-11

days_of_week job attribute 5-8

definingBox Jobs with GUI 4-20Command Jobs with GUI 4-5Command Jobs with JIL 5-5date/time conditions with GUI 4-11date/time conditions with JIL 5-8dependent jobs with GUI 4-13dependent jobs with JIL 5-10File Watcher Jobs with GUI 4-15jobs with GUI 4-3jobs with JIL 5-1machines 7-2starting conditions with GUI 4-10starting conditions with JIL 5-8

Index 3

delete_box 5-3

delete_job 5-3

delete_machine 7-6, 7-7

deletingjobs with GUI 4-25jobs with JIL 5-13real machines 7-6virtual machines 7-7

Dependent Jobs dialog 6-9

dependent jobs, viewing 6-9

documentation, AutoSys Preface-1

DSQUERY 1-7

EEEE

environment variablesAUTOSERV 1-7AUTOSYS 1-6AUTOUSER 1-7database 1-7DSQUERY 1-7Oracle 1-7Sybase 1-7

environment, AutoSys 1-6

Event Processor 1-3, 1-5

Event Server 1-3, 1-4

events 4-8defined 1-4reports, viewing 6-10Send Event dialog 6-7sending with JIL 5-7sending with Job Activity Console 6-6

FFFF

factor machine attribute 7-2, 7-4, 7-5, 7-6

FAILURE status 2-9

File Watcher Jobsdefined 2-7defining with GUI 4-15file to watch for 5-4job stream example 3-3

filesconfiguration, AutoSys 1-7interfaces, Sybase 1-7

Freeze FrameAlarm Manager dialog 6-18Job Activity Console 6-10

GGGG

GUI 2-1, 4-1Control Panel 4-2, 6-2Date/Time Options dialog 4-11defined 1-2defining date/time conditions with 4-11defining dependent jobs with 4-13defining jobs with 4-1defining starting conditions with 4-10Job Definition dialog 4-2Monitor/Browser dialog 4-2Operator Console 4-2, 6-1Send Event dialog 4-8starting 4-2

IIII

INACTIVE status 2-9

insert_job 5-3

insert_machine 7-2

instance, AutoSys 1-3

interfaces file (for Sybase) 1-7

4 AutoSys Tutorial

JJJJ

JILcommands 2-2defined 1-2defining date/time conditions with 5-8defining dependent jobs with 5-10defining jobs with 2-1, 5-1defining machines with 7-2defining starting conditions with 5-8deleting jobs with 5-13job attribute types 5-3sub-commands 5-3syntax rules 5-4

Job Activity Console 6-3Action Area 6-6Alarm button 6-11Alarm Manager dialog 6-15Control Area 6-6control buttons 6-9Currently Selected Job region 6-5Dependent Jobs button 6-9Exit button 6-11Freeze Frame button 6-10Job Definition button 6-9Job List region 6-4Job Selection dialog 6-11menu bar 6-4Reports, Event 6-10Reports, None 6-10Reports, Summary 6-10Send Event dialog 6-7

Job Definition dialog 4-2, 4-3, 6-9Advanced Features dialog 4-6Basic Information region 4-4Box Completion Conditions region 4-4Command and File Watcher Information region

4-4File to Redirect to Standard Output field 4-7Starting Parameters region 4-4

Job Information Language, see JIL

Job Selection dialog 6-11Job Name field 6-12sorting jobs 6-13

specifying job selection criteria 6-14specifying jobs by machine 6-13specifying jobs by status 6-13

job streamsdefined 3-1examples

box job 3-5date/time 3-2file watcher 3-3

job_load job attribute 7-3

jobsACTIVATED status 2-9box 3-5

advanced job stream example 3-7defined 2-8defining with GUI 4-20job stream example 3-5

commanddefined 2-6defining with GUI 4-5defining with JIL 5-5

conditions, dependency 4-10date/time conditions


date/time dependencies 3-2date/time running options 2-3defined 1-1defining with GUI 2-1, 4-1defining with JIL 2-1, 5-1definition dialog 4-2, 4-3definitions 1-5, 2-1deleting with GUI 4-25deleting with JIL 5-13dependent


dependent, viewing 6-9event reports, viewing 6-10FAILURE status 2-9file to watch for attribute 5-4file watcher

defining with GUI 4-15file watcher stream example 3-3file watcher, defined 2-7

Index 5

INACTIVE status 2-9JIL attribute types 5-3JIL sub-commands 2-2Job Activity Console, listed in 6-4Job Definition dialog 4-3machine attribute 5-3name attribute 5-3nested 3-5ON_HOLD status 2-9ON_ICE status 2-9QUE_WAIT status 2-9queuing 7-3RESTART status 2-9running 2-4, 4-7, 5-7RUNNING status 2-9saving definitions with JIL and GUI 2-2sorting order for viewing 6-13starting attribute 5-3starting conditions 2-3


STARTING status 2-9states 2-9status 2-9

in Job Activity Console 6-10streams

defined 3-1examples 3-2

SUCCESS status 2-9summary reports, viewing 6-10TERMINATED status 2-9type attribute 5-3types 2-6viewing by machine 6-13viewing by name 6-12viewing by sorting order 6-13viewing by status 6-13viewing selection 6-14with starting conditions 2-4without starting conditions 2-4

LLLL

lesson content and flow Preface-3

lesson summaries Preface-3

load balancing 7-1, 7-7job attributes required for 7-3machine attributes required for 7-3machine factor 7-4maximum load on machine 7-3

MMMM

machinesclient 1-2defining using insert_machine 7-2deleting real 7-6deleting virtual 7-7distributing jobs among 7-1factor attribute 7-2, 7-4job attribute 5-3job_load job attribute 7-3load balancing 7-7max_load attribute 7-2, 7-3priority job attribute 7-3real 7-2real, defining 7-5real, deleting definition 7-6server 1-2type 7-2viewing jobs by 6-13virtual 7-2virtual, defining 7-6virtual, deleting definitions 7-7virtual, example 7-6

manual, conventions used in Preface-4

max_load machine attribute 7-2, 7-3, 7-5, 7-6

maximum system load 7-3

Monitor/Browser dialog 4-2

NNNN

nested jobs 3-5

6 AutoSys Tutorial

OOOO

ON_HOLD status 2-9

ON_ICE status 2-9

Operator Console 4-2, 6-1defined 1-9starting 6-2

Operator Console. See also Job Activity Console

Oracleenvironment variables 1-7tnsnames.ora file 1-7

override_job 5-3

PPPP

priority job attribute 7-3

QQQQ

QUE_WAIT status 2-9

queuing jobs 7-3

RRRR

real machines 7-2defining 7-2, 7-5deleting 7-6type 7-2

Remote Agent 1-3, 1-5

reportsevents, viewing 6-10job summary, viewing 6-10

RESTART status 2-9

rules, JIL syntax 5-4

running jobs 2-4, 4-7, 5-7

RUNNING status 2-9

SSSS

Send Event dialog 4-8, 6-7illustration 4-9

sendevent 2-4

server machine 1-2

software components of AutoSys 1-3

SQL.INI file (for Sybase) 1-7

start_times job attribute 5-8

starting conditions 5-3jobs 2-3

STARTING status 2-9

starting the GUI 4-2

states, job 2-9

statusjob, in Job Activity Console 6-10sorting jobs by 6-13

status, jobACTIVATED 2-9FAILURE 2-9INACTIVE 2-9ON_HOLD 2-9ON_ICE 2-9QUE_WAIT 2-9RESTART 2-9RUNNING 2-9STARTING 2-9SUCCESS 2-9TERMINATED 2-9

SUCCESS status 2-9

SybaseDSQUERY environment variable 1-7environment variables 1-7interfaces file 1-7SQL.INI file 1-7

system load, maximum 7-3

Index 7

TTTT

TERMINATED status 2-9

tnsnames.ora file (for Oracle) 1-7

tutorialconcepts and skills Preface-2estimated times Preface-2lesson content and flow Preface-3lesson summaries Preface-3process Preface-2

type machine attribute 7-2

UUUU

update_job 5-3

VVVV

variables, environment 1-6

virtual machines 7-2defining 7-2, 7-6deleting 7-7example 7-6type 7-2

WWWW

working environment 1-6