atsxugu.pdf

8/9/2019 atsxugu.pdf

1/158

PLATINUM

AutoSys/XpertUser Guide for UNIX

Version 3.4


2/158

Title and Publication NumberPLATINUM Publication Number: ATE-U-342-UG00-00

Printed: December, 1997

Information in this guide is subject to change without notice and does not constitute acommitment on the part of PLATINUM technology, inc. It is supplied on an “as is” basis

without any warranty of any kind, either explicit or implied. Information may be changedor updated in this guide at any time.

Copyright Information

AutoSys/Xpert is ©copyright 1996 - 1997 by PLATINUM technology, inc. and itssubsidiaries. This guide is ©copyright 1996 - 1997 by PLATINUM technology, inc., and itssubsidiaries and may not be reproduced in whole or in part, by any means, without the

written permission of PLATINUM technology, inc. and its subsidiaries.

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

Mailing Address

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


3/158

PLATINUM AutoSys/Xpert User Guide for UNIX iii

Table of Contents

Preface

Philosophy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixContacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Related Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

1 • Product Overview

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2AutoSys/Xpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

The AutoSys/Xpert Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

The Xpert Simulation Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

HostScape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

HostScape Features and Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

JobScape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8

JobScape Features and Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8TimeScape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

TimeScape Features and Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Simulation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18

2 • Xpert BasicsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

Activating AutoSys/Xpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-3

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4

Interface Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4


4/158

iv PLATINUM AutoSys/Xpert User Guide for UNIX

Table of Contents

Window Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6Time Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Monitor Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Xpert Engine Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Freeze Frame Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Job State Color Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Job Console Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Alarm Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10Current Job Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Selecting and Viewing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Set Current Job Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Job Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-14

Conducting a Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Entering Simulation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-21

Setting the Scope of a Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Start Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Time Window Hours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Time Compression Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

Running a Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24

Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

Simulation Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-27

Setting Simulation Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

Removing Simulation Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-30

Reloading Job Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31

Automatically Reloading Job Definitions . . . . . . . . . . . . . . . . . . . . . . . . 2-31

Reloading Job Definitions on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31

Exiting an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32

3 • Using HostScapeIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Displaying Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

The HostScape Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Starting HostScape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4


5/158

Table of Contents

PLATINUM AutoSys/Xpert User Guide for UNIX v

The HostScape Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-6

Control Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-7

View Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-9

HostScape Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-14

Runtime Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17

Selecting and Viewing Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19

Find Machine Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-19Machine Group Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-21

Creating the groups File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-22

Running in Real-Time Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

Running in Simulation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-24

Defining the Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25

Returning to Real-Time Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-25

4 • Using JobScapeIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2

The JobScape Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2

Starting JobScape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3

The JobScape Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4

Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-5

Control Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-6

View Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-7

Customizing Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14

Runtime Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

Running in Real-Time Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18

Running in Simulation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

Defining the Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19Returning to Real-Time Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

5 • Using TimeScapeIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3

The TimeScape Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3

Starting TimeScape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-4


6/158

vi PLATINUM AutoSys/Xpert User Guide for UNIX

Table of Contents

The TimeScape Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6

Control Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-7

Job Name Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

View Region . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9

Customizing Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

Runtime Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15

Running in Real-Time with Projection Mode . . . . . . . . . . . . . . . . . . . . . . . . . 5-17Monitor Control Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

Running in Simulation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

Defining the Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

Returning to Real-Time Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-21

Projection and Simulation Modeling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22

Changing the Completion Status of a Job . . . . . . . . . . . . . . . . . . . . . . . 5-22

Changing the Run Time For a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

A • X ResourcesIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

General X Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Resources for Colors and Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

Resources for Simulations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6

Resources for Real-Time with Projection Mode . . . . . . . . . . . . . . . . . . . . A-7

Resource for Reloading Job Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

Resource for Job Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-8

TimeScape X Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

Resources for Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

Resources for the Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

Resources for Real-Time with Projection Mode . . . . . . . . . . . . . . . . . . .A-10Resources for Icon and Title Bar Text . . . . . . . . . . . . . . . . . . . . . . . . . . . A-10

JobScape X Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-11

Resources for Printing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-11

Resources for Fonts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-11

Resources for the Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12

Resources for Arrow Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-12


7/158

Table of Contents

PLATINUM AutoSys/Xpert User Guide for UNIX vii

Resources for Real-Time Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12Resources for Icon and Title Bar Text . . . . . . . . . . . . . . . . . . . . . . . . . . A-13

HostScape X Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13

Resources for the groups File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-13

Resources for the Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-14

Resources for Color . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-15

Resources for Icon and Title Bar Text . . . . . . . . . . . . . . . . . . . . . . . . . . A-16

Index


8/158

viii PLATINUM AutoSys/Xpert User Guide for UNIX

Table of Contents


9/158

PLATINUM AutoSys/Xpert User Guide for UNIX ix

Preface

AutoSys/Xpert is an advanced add-on interface which, in conjunction

with AutoSys, allows you to graphically monitor and construct AutoSysjobs and/or job simulations. The three different interfaces of Xpert plusan Xpert Simulation Engine provide an intuitive, easy-to-use tool formanaging jobs in your AutoSys environment.

This manual describes each of the Xpert interfaces as well as the XpertSimulation Engine and the AutoSys/Xpert X resources configuration file.

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

open enterprise environment (OEE).By leveraging its expertise in relational technology, PLATINUM offersproducts and services that increase the efficiency of individual computingsystems and databases, as well as the interoperability of these systemsand databases in distributed environments.


10/158

x PLATINUM AutoSys/Xpert User Guide for UNIX

Preface

Contacting Technical Support

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

AutoSys/Xpert .

To send Email to PLATINUM Technical Support, use:

Internet [email protected] MAIL Exchange USRWNPSN

To contact PLATINUM Technical Support, use:

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

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

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

Our Mailing Address is:

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


11/158

PLATINUM AutoSys/Xpert User Guide for UNIX xi

Preface

About This Guide

About This Guide 0 The PLATINUM AutoSys/Xpert User Guide for UNIX explains how to use AutoSys/Xpert to its fullest capabilities.

This guide assumes that the appropriate PLATINUM AutoSys/Xpert components have been installed at your site. The instructions foractivating the product appear at the end of this preface.

Ch.No. Chapter Name Content Description

1 Product Overview Introduces you to the functions andfeatures of AutoSys/Xpert.

2 Xpert Basics Provides important information about

functionality that is common to all AutoSys/Xpert views — HostScape,JobScape, and TimeScape.

3 Using HostScape Provides information about using theHostScape interface.

4 Using JobScape Provides information about using the

JobScape interface.

5 Using TimeScape Provides information about using the TimeScape interface.

A X Resources Provides information aboutconfiguring the Xpert X resources file.

Index Helps you locate information withinthis manual.


12/158

xii PLATINUM AutoSys/Xpert User Guide for UNIX

Preface

Conventions

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

Symbol orType Style Represents Example

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

alternatecolor

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

...see Chapter 3, Data Migration.

Italic words that are emphasized ...the entry after thecurrent entry...

the titles of other documents PLATINUM General Applications Guide

syntax variables COPY filename

Monospace directories, file names,command names, computercode

&HIGHLVL.SRCLIB

computer screen text, systemresponses, command linecommands

Copy file? Y/N

Monospacebold

what a user types ...enter RUN APP.EXE in the Application field

< > the name of a key on thekeyboard

Press .


13/158

PLATINUM AutoSys/Xpert User Guide for UNIX xiii

Preface

Related Publications

Related Publications 0 As you use this PLATINUM AutoSys/Xpert User Guide for UNIX , you might

find it helpful to have these additional books available for reference:

PLATINUM AutoSys Installation and Getting Started Guide

PLATINUM AutoSys User Guide

PLATINUM AutoSys Reference Guide

choosing a command from acascading menu

File

Import

Object

hi HighlightMVS character format used tocallout screen text on MVS

screens. (When viewedonline, the screen text will beblue.)

Dataset....Product ....

Parmlib...

Symbol orType Style Represents Example

http://atsigu.pdf/http://atsugu.pdf/http://atsrgu.pdf/http://atsrgu.pdf/http://atsugu.pdf/http://atsigu.pdf/http://atsrgu.pdf/


14/158

xiv PLATINUM AutoSys/Xpert User Guide for UNIX

Preface

Related Publications


15/158

PLATINUM AutoSys/Xpert User Guide for UNIX 1-1

1Product Overview

This chapter provides an overview of AutoSys/Xpert. It containsdescriptions of the product’s primary features.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

AutoSys/Xpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

The AutoSys/Xpert Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

The Xpert Simulation Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

HostScape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

HostScape Features and Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-4

JobScape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

JobScape Features and Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

TimeScape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-12

TimeScape Features and Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-13

Simulation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18


16/158

Product Overview

Introduction

1-2 PLATINUM AutoSys/Xpert User Guide for UNIX

Introduction 1

This chapter introduces you to AutoSys/Xpert and describes its primaryfeatures. The following topics are discussed:

The AutoSys/Xpert product

The HostScape interface

The JobScape interface

The TimeScape interface

Simulation data

AutoSys/Xpert 1 AutoSys/Xpert is an advanced graphical facility for monitoring,analyzing, and forecasting AutoSys implementations. This facility’s threedifferent interfaces and an Xpert Simulation Engine provide an intuitive,easy-to-use approach for managing jobs in your AutoSys environment.

The AutoSys/Xpert Interfaces 1

AutoSys/Xpert consists of three interfaces, each of which is presented ina unique window. These interfaces are called:

HostScape

TimeScape

JobScape


17/158


Product Overview

HostScape

The Xpert Simulation Engine 1

The Xpert Simulation Engine is embedded in each of the three AutoSys/Xpert interfaces. This engine:

Retrieves data from the AutoSys database for conducting simulations

Provides a dialog for specifying simulation parameters and running a

simulation Performs the simulation

You select the Xpert Engine button in any of the AutoSys/Xpert interfacesto access the Xpert Simulation Engine.

HostScape 1HostScape displays jobs on a machine-by-machine basis, showing which

AutoSys client and server machines are up and active. It also shows whichjobs are running or have recently run on each machine. Within eachmachine graphic, Command and File Watcher Jobs are listed. Box Jobsare not shown because boxes are not associated with a particularmachine. You use HostScape to monitor job flow in real-time or to

simulate job progression as it relates to specific machines.

Note • For detailed descriptions of the three job types: CommandJobs, Box Jobs, and File Watcher Jobs, see Chapter 3, AutoSys Jobs, in the AutoSys User Guide for UNIX .

http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/


18/158

Product Overview

HostScape


HostScape Features and Use 1

HostScape provides a number of features that help you monitor andanalyze the machine and job behavior of your AutoSys implementation.

These features are described below.

Monitoring Machines and Jobs

When using HostScape in real-time (or monitor) mode, you arepresented with a graphical view of all AutoSys machines and their currentstate. Machine graphic borders display in a color indicative of themachine’s current state, depicting machine activity as it occurs. Thenames of AutoSys jobs are listed on the machine on which they arecurrently running, or have recently run. These job names display in acolor indicative of the job state, showing actual job execution.


19/158


Product Overview

HostScape

Event Processors and Event Servers are depicted on server machines withunique colors indicating whether the Event Processor or Event Server isup or down. Connectivity between AutoSys server and client machines iscontinually monitored. It is depicted as a function of whether a machinecan run a Remote Agent (and therefore jobs), or be contacted at all.

The graphic for each machine displays the number of jobs in either theRUNNING or STARTING state on the machine. The graphic also contains

an alarm/indicator button, which allows you to display the AutoSys Alarm Manager to immediately respond to an alarm when it is generated.

You can configure a hang time to control how long job names remaindisplayed in a machine graphic once they have completed running. Thisfeature provides a way to filter the past jobs that have run, giving you ahistorical picture of job activity on all machines.

You can at any time reload new or modified job definitions, or thesedefinitions can be automatically reloaded at natural break points.

Hot Link to the Job Console

In real-time mode, you can display an abbreviated version of the JobConsole at any time to simultaneously access all the control features ofthis facility. The currently selected job in HostScape is also the currentlyselected job in the Console. When you select a different job in HostScape,it immediately becomes the currently selected job in the Console as well,giving you complete visual and event-based control over your entire jobenvironment.

Hot Link to the Alarm Manager

In real-time mode, you can display the AutoSys Alarm Manager dialogand simultaneously access all the control features of this facility. Thisprovides you complete control over the disposition and resolution of any

AutoSys alarms that might occur.


20/158

Product Overview

HostScape


Navigating Large ImplementationsHostScape provides an easy-to-use mechanism for selecting the machines

you want to view. Using the Find Machine dialog, you can quickly specifythe currently selected machine, causing it to scroll into view.

To display one or more groups of machines, you use the Machine Groupdialog. Machine groups simplify the selection of a set of machines.

HostScape also provides an easy-to-use mechanism for selecting the jobs you want to view. Using the Set Current Job dialog, you can quicklyspecify the currently selected job, causing the job (and its associatedmachine) to scroll into view. This feature is useful if you want toinvestigate more detailed information using the Job Console;information about the currently selected job is displayed in the JobConsole when it is accessed.

To display one or more groups of jobs (and their associated machines), you use the Job Selection dialog.

Both of the above features are particularly useful when you have a largeinstallation with a large number of machines and jobs.

Specifying the Best View

To assist you in achieving the best view of machines and jobs, HostScapeprovides a number of ways to refine your graphical viewpoint.

Viewing Machines - Normal View

You view machines in Normal View to get a good overall picture of which AutoSys machines are active (or down) and the jobs, Event Processors,and Event Servers that are running on them.

Viewing Machines - Global View

You view machines in Global View to get a comprehensive picture of AutoSys machines because a greater number of machines are displayedon one screen. In this view, AutoSys jobs, Event Processors, and EventServers are not shown; however, the total number of jobs running oneach machine is shown.


21/158


22/158

Product Overview

JobScape


JobScape 1

JobScape presents a Pert-like view of job processing from a logical (or jobdependency) point of view. This interface depicts all job types:Command Jobs, Box Jobs, and File Watcher Jobs. It also shows thenesting of jobs within boxes and the dependencies between jobs. You usethis interface to monitor job flow in real-time or to simulate jobprogression as it relates to nested jobs and job dependencies.

JobScape Features and Use 1

JobScape provides a number of features that help you monitor, analyze,and refine the logical behavior of your AutoSys job streams. These

features are described below.


23/158


Product Overview

JobScape

Monitoring Jobs When using JobScape in real-time (or monitor) mode, you are presented with a graphical view of all AutoSys jobs and their current state. Jobnames are displayed in colors that represent the current job state. Thesecolors change, depicting actual job execution as it occurs. The jobdependencies between jobs are also shown, letting you view whether adependency was satisfied. To stay as current as possible, you can at any

time reload job definitions that have been added or modified in the AutoSys database.

Hot Link to the Job Console

In real-time mode, you can display an abbreviated version of the JobConsole and simultaneously access all the control features of this facility.

The currently selected job in JobScape is also the currently selected job in

the Console. When you select a different job in JobScape, it becomes thecurrently selected job in the Console as well, giving you complete visualand event-based control over your entire job environment.


In real-time mode, you can display the AutoSys Alarm Manager dialogand simultaneously access all the control features of this facility. This

provides you complete control over the disposition and resolution of any AutoSys alarms that might occur.

Easy Access to the Job Definition Dialog

For any job in JobScape, you can quickly display the Job Definitiondialog from the Job pop-up menu. This dialog remains open until youdismiss it. Every time you change the currently selected job in JobScape,the corresponding job definition is displayed in the Job Definitiondialog.

P d O i


24/158

Product Overview

JobScape


Easy Access to Job Event ExecutionFor any job in JobScape, you can quickly execute any of the followingevents by selecting them from the Job pop-up menu: Start Job, Kill Job,Force Start Job, On Hold, Off Hold, On Ice, or Off Ice.

Navigating Large Implementations

JobScape provides an easy-to-use mechanism for selecting the jobs you

want to view. Using the Set Current Job and the Job Selection dialogs, you can quickly specify the currently selected job or a group of jobs you want to display on the screen. This feature can be particularly useful when you have a large number of dependent jobs and you want totroubleshoot a particular set of dependency conditions.


To assist you in achieving the best view of jobs and their jobdependencies, JobScape provides a number of ways to refine yourgraphical viewpoint.

Viewing Jobs

You can view jobs by name, by job ID, or no text at all. You can alsochoose between normal and small font. This gives you control over how

many jobs can be displayed on the screen at one time.

Viewing Job and Box Arrows

You can selectively turn on and off arrows showing dependenciesbetween jobs and/or boxes. Selected job arrows appear in a differentcolor than the other arrows, to facilitate identification.

Viewing Different Levels of Nested Jobs - Global

You can select the levels of nesting to display for jobs and boxes insideBox Jobs. This feature is useful for achieving the best view of your overallimplementation, especially when you have a large number of AutoSysjobs.

Product Overview


25/158


Product Overview

JobScape

Viewing Different Levels of Nested Jobs - Single Box Job

For a particular Box Job in JobScape, you can view the jobs and boxesinside that box at different levels of nesting. This feature is useful forachieving the best view of the logic for a particular box, especially when

you have a large number of jobs and boxes inside the Box Job. You canshow the children (or immediate descendants) of a box, show all itsdescendants, or hide all its descendants.

Simulating Job Runs

Use JobScape in simulation mode to view jobs and the effect of jobdependencies without actually running any jobs. To enter this mode, youselect the Xpert Engine button. Job runs and job dependencies are basedon existing job definitions from the AutoSys database, giving you arealistic picture of events in a virtual environment. You can specify a

scope of time for the simulation and compress this simulated time toquickly view the progression of a job stream. You can run a continuoussimulation or step through it by either time or event increments.

JobScape provides an intuitive way to visually inspect job dependenciesfor any errors or oversights that might have occurred when designing ajob flow. In simulation mode, you can watch jobs run to completion andinspect the impact they have on their dependent jobs, as well as other

downstream jobs. As a result, JobScape is a very effective tool foranalyzing and testing your job streams before you move them intoproduction.

Product Overview


26/158

Product Overview

TimeScape


Modeling a Simulation To help you create “what if” scenarios during a simulation, JobScape lets you change various job behaviors to determine how job streams mightprogress. You can force a completion status of SUCCESS, TERMINATED,or FAILURE for a particular job. You can also force a pre-determinednumber of failures for a job, alter the duration of a job run, or set a Unixexit code for a job. All these simulation overrides let you examine the

logic of job streams before you implement a job flow. They also let you tryalternative methods of job flow design to resolve any current problemsin job flow logic. As a result, you can address any necessary error recoveryat a single, or at multiple points, of failure.

TimeScape 1

TimeScape presents a Gantt-like view of job processing from a temporal(or time-related) perspective. This view depicts all job types: CommandJobs, Box Jobs, and File Watcher Jobs. It also shows the nesting of jobs

within boxes and the duration of time takes for jobs to complete. You usethis view to monitor job flow in real-time, or to project and simulate jobprogression as it relates to a specified time period.

Product Overview


27/158


Product Overview

TimeScape

TimeScape Features and Use 1

TimeScape provides a number of features that help you monitor, analyze,and refine the time-related behavior of your AutoSys job streams. Thesefeatures are described below.

Product Overview


28/158

Product Overview

TimeScape


Monitoring Jobs When using TimeScape in real-time with projection (or monitor) mode, you are presented with a graphical view of all AutoSys jobs and theircurrent state. Job names are displayed in colors that represent the currentjob state. These colors change, depicting actual job execution as it occurs.Job runs are also depicted in real-time with graphical progress ribbons,letting you view the actual progression of a job. You can witness whether

a job completes when it is expected to or if it is running longer (ascompared to historical job run data). To stay as current as possible, youcan at any time reload job definitions that have been added or modifiedin the AutoSys database.

Viewing Historical Job Runs

In real-time with projection mode, you can specify a window of time in

which to view job runs, either relative to the current time or a specifictime period of your choosing. In this way, you can see which jobs haverun in the past and how they performed. The information used for thisdisplay is taken from historical job run data residing in the AutoSysdatabase. As a result, you can evaluate the timeliness of past and presentjob runs, as well as how this pertains to an entire job stream.

Projecting Future Job RunsIn real-time with projection mode, you can specify different windows oftime in which to view job runs, allowing you to see the time it will takefor jobs to run in the future. The information used for this display isbased on historical job run data residing in the AutoSys database.

Using this feature, you can evaluate the timeliness of future jobs,pinpointing where certain jobs might take longer to complete. This canbe particularly useful if you are trying to schedule various jobs within arestricted period of time. This feature can also be handy for personnelstarting a shift. When they arrive, they can see which jobs are remainingfor various production runs.

Product Overview


29/158


TimeScape

Modeling a Projection

To help you create “what if” scenarios during a projection, TimeScape lets you change various job behaviors to determine how job streams mightprogress. You can force a completions status of SUCCESS, TERMINATED,or FAILURE for a particular job. You can also force a pre-determinednumber of failures for a job, alter the duration of a job run, or set a Unixexit code for a job. These overrides let you examine the logic of job

streams before you implement a job flow.In addition to the modeling features above, TimeScape lets you easilychange the completion status of a job using the Status pop-up menu. Youcan also adjust the ending time of a job run using the mouse pointer,overriding any historical job data that is used to estimate the time it takesfor a job to complete.

The advantage of being able to adjust the ending time of a job could bedescribed as follows. Let’s say one of your job streams relies on the arrivalof a mainframe file, and you are notified that the file will be late. Toevaluate how this might affect your job run, you can manually adjust theend time for the job(s) relying on the arriving file and see how it wouldaffect your entire production schedule.

Hot Link to the Job ConsoleIn real-time mode, you can display an abbreviated version of the JobConsole and simultaneously access the control features of this facility.

The currently selected job in the TimeScape view is also the currentlyselected job in the Console. When you select a different job in

TimeScape, it becomes the currently selected job in the Console as well,giving you complete visual and event-based control over your entire job

environment.


In real-time mode, you can display the AutoSys Alarm Manager dialogand simultaneously access all the control features of this facility. Thisprovides you complete control over the disposition and resolution of any

AutoSys alarms that might occur.

Product Overview


30/158

TimeScape


Easy Access to the Job Definition Dialog

For any job in TimeScape, you can quickly display the Job Definitiondialog from the Job pop-up menu. This dialog remains open until youdismiss it. Every time you change the currently selected job in TimeScape,the corresponding job definition is displayed in the Job Definitiondialog.

Easy Access to Job Event ExecutionFor any job in TimeScape, you can quickly execute any of the followingevents by selecting them from the Job pop-up menu: Start Job, Kill Job,Force Start Job, On Hold, Off Hold, On Ice, or Off Ice.

Navigating Large Implementations

TimeScape provides an easy-to-use mechanism for selecting the jobs you want to view. Using the Set Current Job and the Job Selection dialogs, you can quickly specify the currently selected job or a group of jobs you want to display on the screen. This feature can be particularly useful when you have a large number of jobs and you want to troubleshoot aparticular set of time-related conditions.


To assist you in achieving the best view of jobs and their jobdependencies, TimeScape provides a number of ways to refine yourgraphical viewpoint.

Viewing Different Levels of Nested Jobs - Global

In TimeScape, you can control the display to show different levels ofnesting of jobs and boxes inside Box Jobs. This feature is useful for

achieving the best view of your overall implementation, especially when you have a large number of AutoSys jobs.

Product Overview


31/158


TimeScape

Viewing Different Levels of Nested Jobs - Single Box Job

For a particular Box Job in TimeScape, you can view the jobs and boxesinside that box at different levels of nesting. This feature is useful forachieving the best view of the logic for a particular box, especially when

you have a large number of jobs and boxes inside the Box Job. You canshow the children (or immediate descendants) of a box, show all itsdescendants, or hide all its descendants.

Specifying the Time ViewIn TimeScape, you can specify the ratio between an hour of time and thedistance (in inches) used for displaying job progressions. This featurehelps you refine the overall time-related perspective of job runs so youcan visualize an entire job stream.

Simulating Job Runs

Use TimeScape in simulation mode to view job runs across time withoutactually running any jobs. To enter this mode, you select the Xpert Enginebutton. Job runs and starting times are based on existing job definitionsfrom the AutoSys database, giving you a realistic picture of events in a

virtual environment. You can specify a window of time for thesimulation and compress this simulated time to quickly view theprogression of a job stream. You can run a continuous simulation or step

through it by either time or event increments. Simulating job runs in thismanner lets you analyze the timing elements of your current job streamin a safe and expedient way.

Modeling a Simulation

To help you create “what if” scenarios during a simulation, TimeScapelets you change various job behaviors to determine how job streamsmight progress. You can force a completion status of SUCCESS,

TERMINATED, or FAILURE for a particular job. You can also force a pre-determined number of failures for a job, alter the duration of a job run,or set a Unix exit code for a job. These simulation overrides let youexamine the logic of job streams before you implement a job flow. Theyalso let you try alternative methods of job flow design to resolve anyproblems in job flow logic.

Product Overview


32/158

Simulation Data


In addition to the simulation modeling features above, TimeScape lets you easily change the completion status of a job using the Status pop-upmenu. You can also adjust the ending time of a job run using the mousepointer, overriding any historical job data that is used to estimate thetime it takes for a job to complete.

Simulation Data 1 AutoSys/Xpert uses historical data in the AutoSys database whenprojecting job runs. The average time it takes for a job to run is takenfrom the avg_job_runs table. If the job has never run, or if data has beenarchived and removed from the table, then the historical average runtime cannot be determined. In this case, the avg_runtime attribute isused, if it was specified in the job definition. If the avg_runtime attribute

was not specified, a default run time of 300 seconds (5 minutes) is used.

Average run time data is calculated by an AutoSys script called DBMaint,based on historic run times found in the job_runs table. Running thisscript is critical in assuring that AutoSys/Xpert has accurate average runtime data. You set up the AutoSys configuration file to run this scriptdaily as part of its internal database maintenance cycle. For moreinformation on setting up the AutoSys configuration file, see Chapter 13,Configuring AutoSys in the AutoSys User Guide for UNIX .

After calculating average run times, DBMaint removes old events and jobrun information from the database using the archive_events command.By default, it removes data older than 7 days. This can impact the averagejob run calculation for jobs that run less frequently than 7 days, becausethe job run data will no longer be in the database.

http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/


33/158


2Xpert Basics

This chapter provides important information about basic AutoSys/Xpert

functionality. You should read and understand the material in thischapter before reading the other chapters in this manual.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Activating AutoSys/Xpert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Interface Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Window Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Time Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Monitor Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Xpert Engine Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Freeze Frame Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Job State Color Legend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8

Job Console Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Alarm Button . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Current Job Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Selecting and Viewing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Set Current Job Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Xpert Basics


34/158


Job Selection Dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-14

Conducting a Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-19

Entering Simulation Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-21

Setting the Scope of a Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Start Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-23

Time Window Hours . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-23

Time Compression Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-24

Running a Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-24

Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25

Simulation Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-27

Setting Simulation Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-30

Removing Simulation Overrides . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-30

Reloading Job Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-31

Automatically Reloading Job Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-31

Reloading Job Definitions on Demand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-31

Exiting an Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32

Xpert Basics

Introduction


35/158


Introduction

Introduction 2

This chapter introduces you to AutoSys/Xpert and some of its basicfunctionality. The following topics are discussed:

Activating AutoSys/Xpert

The three Xpert interfaces

Common window controls

Selecting and viewing jobs

Conducting a simulation

Setting simulation overrides

Reloading job definitions Exiting an interface

Activating AutoSys/Xpert 2 When your AutoSys software was installed, AutoSys/Xpert was alsoinstalled. However, to use AutoSys/Xpert you must activate it by updating

the AutoSys License Manager using a special key. This key can be atemporary or a permanent Xpert key, and can be obtained by calling theCustomer Service Department at AutoSystems Development Laboratory.

The Xpert license key activates AutoSys/Xpert for all AutoSys clients andservers. Temporary license keys are set to expire on a certain date; beyondthis date, the Xpert software does not operate. Permanent license keys

allow the Xpert software to operate indefinitely. You can upgrade yourtemporary license to a permanent one by installing a new license key.

For more information about installing license keys using the AutoSysLicense Manager, refer to the AutoSys Installation and Getting Started Guide

for UNIX .

Xpert Basics

Troubleshooting

http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/http://atsigu.pdf/


36/158

Troubleshooting


Troubleshooting 2

If you encounter connectivity problems with Xpert, see TroubleshootingConnectivity Problems in Chapter 3, Using HostScape, for possible solutions.If you encounter any other problems or errors with Xpert, see Chapter 14,Troubleshooting , of the AutoSys User Guide for UNIX . If you are still unableto resolve the problem, see the Contacting Technical Support section at thebeginning of this manual.

Interface Windows 2Each AutoSys/Xpert interface displays in its own window. At the top ofthe windows are pull-down menus containing various options.

The following two regions are common to all windows:

Control region. This region contains display areas, action buttons, andlegends. With only a few exceptions, this region contains the sameelements across all interface types. When differences exist, they aredescribed in the corresponding chapter.

View region. In JobScape and TimeScape, this region displays jobs andjob streams using either real-time or simulated data. In HostScape,

this region displays machines. The appearance of this region variesbetween all three interfaces.

Xpert Basics

Interface Windows

http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/


37/158


Interface Windows

Using JobScape as an example, these two regions are shown in the

following illustration.

Figure 2-1 • Example Control and View Regions

Control region View region


38/158


39/158

Xpert Basics

Window Controls


40/158


Xpert Engine Button 2

You use the Xpert Engine button to:

Set the current mode to simulation. In this mode, the View regionrefreshes according to simulated job data. The Freeze Frame feature isdeactivated in this mode.

Access the Xpert Engine Control dialog. You use this dialog to

configure the scope of time you want applied in simulation mode. You also initiate and control simulations at this dialog.

For more information about using the Xpert Engine button, seeConducting a Simulation on page 2-19.

Freeze Frame Button 2

The Freeze Frame button is a toggle. When it is on in real-time mode, itprevents the current interface from refreshing with live data. When it isoff, the interface is continuously refreshed with the most recent data.

In simulation mode, the Freeze Frame button is deactivated; as a result,data refreshes are under the control of the Xpert Engine.

Job State Color Legend 2

The Job State Color Legend region is static and is used to correlate aunique color with a particular job state. For example, in a JobScape

window a RUNNING job could be depicted with a light green color, andan INACTIVE job could be depicted with a black color. You can configurethese colors by modifying the application’s X resources file, described in

Appendix A, X Resources.

Note • In HostScape only, because it is a machine-based view, thefollowing job states are not shown: ACTIVATED, RESTART,QUE_WAIT, ON_ICE, ON_HOLD, and INACTIVE.

Xpert Basics

Window Controls


41/158


Job Console Button 2

You use the Job Console button to access an abbreviated AutoSys Job Activity Console; only the bottom two-thirds of the standard console isdisplayed. From this console, you can monitor the currently selected jobspecified in the View region of the interface window.

When you click the Job Console button, the Job Console windowappears in the foreground of your screen. While this window is open, itis continually updated with the currently selected job in the View regionof the Xpert interface window. If this window is in the background, youcan bring it to the foreground by clicking the Job Console button again.

In addition to monitoring the currently selected job, the Job Console alsolets you perform actions such as:

Generating reports Starting a job

Killing a job

Forcing a job to start

Placing a job on hold

Taking a job off hold

Accessing the Send Event dialog

Note • The Job Console button is disabled during a simulation.

All Job Console functionality is identical to that found in the standardJob Activity Console, with two exceptions: there is no Job List, and youare not asked to verify an exit when you close the console.

While the Job Console is open, each new job you specify as the currentlyselected job in the AutoSys/Xpert interface becomes the currently selectedjob in the Job Console.

Xpert Basics

Window Controls


42/158


For more information about the Job Activity Console, see Chapter 10, The

Operator Console in the AutoSys User Guide for UNIX .

Alarm Button 2

The Alarm button turns red when an alarm is generated by AutoSys forany job. You reset the button by clicking it. When you do this, the buttonreturns to its default color (gray), and the AutoSys Alarm Manager dialog

appears. This dialog lets you view alarms as they arrive, acknowledgethem, and change their status from Open to Acknowledged or Closed. Inaddition to listing alarms, the Alarm Manager dialog also lets you registera response to an alarm.

Note • The Alarm button is disabled when using the Xpert Engine;that is, when you are conducting a simulation.

For more information about the Alarm Manager dialog, see Chapter 10,The Operator Console, in the AutoSys User Guide for UNIX .

Current Job Name 2

The name of the currently selected job in any of the interfaces is displayedin the Current Job Name area at the bottom of the Control region. Thisarea cannot be edited. If you have a large number of jobs in the Autosysdatabase, this feature reminds you which job is selected; it is the selectedjob that will be acted upon. In all the interfaces, the currently selected jobcan be specified using the Set Current Job dialog (see the next section) or:

In HostScape and JobScape, positioning the mouse pointer over the

job name in its corresponding graphic and clicking the left mousebutton.

In TimeScape, clicking the job’s push button in the Job Name region.

Xpert Basics

Selecting and Viewing Jobs

http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/http://atsugu.pdf/


43/158


If you access the Job Console or the Job Definition dialog, the currently

selected job in the interface becomes the currently selected job in these windows as well. As you select different jobs in the interface, the currentlyselected job in the Job Console or the Job Definition dialog changesaccordingly. Also, if you apply simulation overrides at an interface, theoverrides are applied to the currently selected job.

Because job names can be longer than the allotted space in the Current

Job Name area, you can view any part of the name by placing the cursorin this area and using the Right and Left Arrow keys.

Selecting and Viewing Jobs 2Each AutoSys/Xpert interface provides a way to specify:

The currently selected job. This involves selecting a single job at the Set

Current Job dialog.

A job (or group of jobs) that you want to view. This involves selecting jobsbased on criteria you set at the Job Selection dialog.

Set Current Job Dialog 2

The Set Current Job dialog lets you specify the currently selected job. Thisdialog can be very useful when there are a large number of jobs in the

AutoSys database. When a job is selected, it scrolls into view in the Viewregion of the window.

To access the Set Current Job dialog

Choose View

Set Current Job. The Set Current Job dialog appears, as

shown in the following illustration.

Xpert Basics



44/158


The Set Current Job dialog contains the following elements:

Filter Use this entry field to specify a search pattern; alljobs matching the pattern are retrieved. You canenter a partial job name with a wildcard character.

You can use this wildcard in more than one characterposition within the name specification. Thequestion mark (?) wildcard represents any singlecharacter. The asterisk (*) wildcard represents astring of any number of characters, including anempty (null) string. For example, if you enter the

name “?est*”, all jobs matching this search patternare retrieved, such as testb1 and test_watch. This fieldis case-sensitive.

Jobs Once the filter has been applied, all the jobsmatching the filter appear in this scroll list. You canthen select the job you want from the list.

Xpert Basics



45/158


To apply a filter

1 In the Filter entry field, enter a search pattern.

2 Click the Filter button. Job names matching the search pattern appear

in the Jobs list box.

To specify the currently selected job

1 Select the desired job from the Jobs list box. The job name appears inthe Selected Job field.

2 To accept the selected job and keep the dialog open, click Apply. Thejob is now the currently selected job and the dialog remains open. (InJobScape and TimeScape only, if the job is not currently displayed inthe View region, a Confirm dialog asks you if you want it to display;click Yes or No.)

Or

To accept the selected job and close the dialog, click OK. The job isnow the currently selected job and the dialog closes. (In JobScape and

TimeScape only, if the job is not currently displayed in the Viewregion, a Confirm dialog asks you if you want it to display; click Yesor No.)

Note • You can also specify the currently selected job and close thedialog by double-clicking on the job name in the Jobs list box.

Selected Job The job you select from the Jobs list box displays inthis entry field.

Xpert Basics



46/158


Job Selection Dialog 2

The Job Selection dialog lets you specify the job (or group of jobs) you want to display in the View region of the window. This dialog can be veryuseful when there are a large number of jobs in the AutoSys database.Only the jobs that are selected appear in the View region of the window.

To access the Job Selection dialog

Choose View Select Jobs To Display. The Job Selection dialogappears, as shown in the following illustration.

The Job Selection dialog is divided into three regions:

Select by Name

Select by Status

Select by Machine

DB*

Xpert Basics



47/158


Selecting Jobs by Name

When selecting jobs by name, you can specify the following criteria:

All Jobs All jobs in the AutoSys database are retrieved. Thisselection overrides all other criteria in this region.

Box Hierarchies Jobs within a Box Job that matches the searchpattern are retrieved. (The jobs within the Box Job do

not have to match the search pattern; only the BoxJob itself must match the pattern.)

Show Number ofLevels

Specify how many levels of nested jobs you want to view for a Box Job. You can specify all or enter anumber, such as 1, 2, or 3. The number 0 displays nodescendants.

Name MatchingPatterns Enter one or more search patterns when searchingfor jobs by name; all jobs matching the pattern areretrieved. You can enter:

The entire job name.

A partial job name with a wildcard character. Youcan use this wildcard in more than one characterposition within the name specification. The

question mark (?) wildcard represents any singlecharacter. The asterisk (*) wildcard represents astring of any number of characters, including anempty (null) string. For example, if you enter thename “?est*”, all jobs matching this searchpattern are retrieved, such as testb1 and testb2.

Xpert Basics



48/158


If you enter a partial job name with a wildcard character, all the jobs

matching the pattern can be viewed by choosing the Lookup button nextto the entry field. When this button is pressed, the Lookup Matches

dialog appears, as shown in the following illustration.

The Lookup Matches dialog contains the following elements:

To specify a particular job

1 Select the desired job from the Match List area. The job name appearsin the Selection text box.

Match List This field lists all the jobs matching the search

pattern. Using the mouse, you can then select thedesired job from the list.

Selection This editable field displays the job you selected fromthe Match List.

Xpert Basics



49/158


2 To accept the selected job and keep the dialog open, click Apply. The

job name replaces the original search pattern in the Job Selectiondialog and the dialog remains open.

Or

To accept the selected job and close the dialog, click OK. The job namereplaces the original search pattern in the Job Selection dialog, and thedialog closes.

Note • To select all jobs in the Match list area, do not select any joband click OK or Cancel in the Lookup Matches dialog.

Selecting a Job by Status

The Job Selection dialog lets you select jobs based on their current status,

such as STARTING, RUNNING, or INACTIVE. The default is to select alljobs that are currently RUNNING. You can select any combination ofstatuses, or you can click the All Statuses check box. This setting overridesany specific status settings.

Note • Because HostScape is a machine-based view, the following jobstates are not shown: ACTIVATED, RESTART, QUE_WAIT, ON_ICE,

ON_HOLD, and INACTIVE.

Selecting a Job by Machine

The Job Selection dialog also lets you select jobs based on the machineon which they run. At the right side of the dialog, there is a list of all themachines that are referenced in any job definition or are identified as part

of a virtual machine definition. This list also shows the names ofmachines that have run AutoSys jobs (gleaned from tables in the AutoSysdatabase). From the list, you can select one, several, or all machines (thedefault).


50/158

Xpert Basics

Conducting a Simulation


51/158


Conducting a Simulation 2

You can initiate a simulation from any AutoSys/Xpert interface. Theperspective of the simulation corresponds to the interface from which it

was started.

In HostScape, a simulation simulates the progression of jobs runningon the various AutoSys machines. In addition, it displays the actualcurrent state of the AutoSys server(s) and the ability of Remote Agentsto run jobs. Virtual machines and load balancing cannot besimulated. If a virtual machine was specified, the first real machine inthe virtual machine definition is used.

In JobScape, you can simulate job runs and analyze the impact theyhave on dependent jobs. This provides the opportunity to inspect jobstreams before you move them into production.

In TimeScape, you can simulate job runs across time so you cananalyze the timing elements of job streams.

Simulated job runs are based on existing job definitions and historicaljob run data from the AutoSys database. All simulations are conducted inmemory; actual jobs are not run. Simulated job runs default to acompletion status of SUCCESS. Simulation overrides (discussed on

page 2-27) let you control various job behaviors to determine how jobstreams might progress. For any job, you can force a completion status,force a pre-determined number of FAILUREs, alter the duration, or set anexit code. Simulation overrides are the only way to influence a simulatedjob; you cannot send events manually using the sendevent command orthe GUI.

Jobs are handled in the following way when conducting a simulation:

To simplify the simulation, job permissions checking andauthentication are not performed.

The default duration of the job is the average run time for the job. (SeeSimulation Data on page 1-18 for details on how this time iscalculated.)

Xpert Basics



52/158


Job dependencies based on global variables always evaluate to true,

regardless of the value of the global variable it is referencing.

Cross-instance job dependencies always evaluate to true. In other words, if a starting condition references a job in another AutoSysinstance, the status of the cross-instance job is SUCCESS.

The following AutoSys events and job attributes are ignored by theSimulation Engine because they do not apply to jobs that are being

simulated:

Events

ALARM HEARTBEAT

CHANGE_PRIORITY JOB_OFF_HOLD

CHECK_HEARBEAT JOB_OFF_ICE

COMMENT JOB_ON_HOLD

DELETEJOB JOB_ON_ICE

EXTERNAL_DEPENDENCY SEND_SIGNAL

FORCE_STARTJOB SET_GLOBAL

Job Attributes

alarm_if_fail owner

auto_delete permission

auto_hold priority

chk_files profile

command std_err_file

heartbeat_interval std_in_file

Xpert Basics



53/158


Entering Simulation Mode 2

From any AutoSys/Xpert interface you can change from real-time(monitor) mode to simulation mode by accessing the Xpert EngineControl dialog.

To access the Xpert Engine Control dialog

Click the Xpert Engine button in the Control region. You are now insimulation mode.

The Xpert Engine Control dialog appears, as shown in the following

illustration.

job_load std_out_file

max_run_alarm watch_file

min_run_alarm watch_file_min_size

override_job watch_interval

Job Attributes

Xpert Basics



54/158


The Xpert Engine Control dialog is divided into five regions used to setthe scope of and run a simulation. From top to bottom, these regions are:

Start Time

Time Window Hours

Time Compression Rate

Step By Time/Step By Event

Control

Xpert Basics



55/158


Setting the Scope of a Simulation 2

Before you start a simulation, you must first specify the scope of thesimulation using the Xpert Engine Control dialog.

To set the scope of a simulation

From the Xpert Engine Control dialog, specify the following:

• Start Time (date and time)

• Time Window Hours

• Time Compression Rate

Start Time 2

Use the Start Time region to specify the date and time for the beginningof the simulation. You can enter the start date and time directly in theentry field, or you can use the provided arrow buttons. The single-arrowbuttons move the time forward or backwards in ten-minute increments;the double-arrow buttons move the date forward or backwards in one-day increments. You can configure the single-arrow and double-arrowbuttons, as described in the Resources for Simulations section of

Appendix A, X Resources.

Note • Times are displayed in 24-hour format. For example, 11:00a.m. is designated as 11:00, and 11:00 p.m. is 23:00.

Time Window Hours 2

Use the Time Window Hours region to specify the duration of time (afterthe Start Time) over which you want to view the simulation. For example,if you set the Start Time at 03:00 and the Time Window Hours at 4.0, thesimulation displays job activity for 4 hours, from 3:00 a.m. to 7:00 a.m.

You specify the Time Window Hours by using the mouse pointer to movethe slider bar found in this region. The slider moves in increments of one-tenth of an hour.

Xpert Basics



56/158


Time Compression Rate 2

Use the Time Compression Rate region to specify the ratio of actual timeto simulated time. This setting lets you view the progression of jobs overa large period of simulated time in a very short period of actual time. Forexample, a Time Compression Rate of 60 means that for each second ofactual time, the simulation displays 60 seconds worth of events. Putanother way, if you specify a Time Compression Rate of 60, you see fourhours of events in a four minute time span. You specify the TimeCompression Rate by using the mouse pointer to move the slider barfound in this region. The maximum setting is 180, which means that 3minutes of simulation activity is displayed in one second of actual time.

Running a Simulation 2

You can let the simulation run continuously to completion or you can view the progression of the simulation in pre-defined time or eventincrements.

To run a continuous simulation

Click the Run/Continue button. A continuous simulation begins, andthe time display refreshes, showing the current simulated time.

To step through the simulation

To conduct a time-related simulation, use the Step By Time arrowbuttons. The single-arrow button steps through the simulation inincrements of ten simulated seconds; the double-arrow button stepsthrough the simulation in increments of sixty simulated seconds.

Or

To conduct an event-related simulation, use the Step By Event arrowbuttons. (An event is a change of status of a job.) The single-arrowbutton steps through the simulation in increments of one simulated event; the double-arrow button steps through the simulation inincrements of five simulated events.

Xpert Basics


f h ld h b d hil li ki b h


57/158


If you hold the mouse button down while clicking an arrow button, the

Xpert Engine continues to step through the simulation.

Note • You can configure the default time and step increments for thebuttons in this region by modifying the application’s X resource file.See the Resources for Simulations section of Appendix A, X Resources.

To skip to the end of the simulation

Click the Skip to End button to advance to the end result of thesimulation and stop the simulation.

Control 2

Use the Control region of the Xpert Engine Control dialog to initiate and

control the run of a simulation. The following options are available:

Run/Continue Starts or resumes a simulation.

Pause Stops a simulation after it has started. The screenstops refreshing and the time display is idle.

Reset To Start Sets the simulation back to the Start Time and

pauses the simulation. To initiate the simulationagain, either click the Run/Continue button or clickone of the Step By Time or Step By Event arrowbuttons.

Skip To End Advances the simulation to the end of the Time Window and stops the simulation after displayingall simulation data.

Dismiss Closes the Xpert Engine Control dialog.

Xpert Basics


Whil th i l ti i i f f th f ll i


58/158


While the simulation is running, you can perform any of the following

actions:

To temporarily stop the simulation, click the Pause button. Thesimulation stops and the time display is frozen.

To restart the simulation, click the Run/Continue button. Thesimulation starts again and the time display shows the currentsimulated time.

To step through the simulation in time increments, click the Pausebutton, then click one of the Step by Time arrow buttons. To resumea continuous simulation, click the Pause button, then click theRun/Continue button.

To step through the simulation in event increments, click the Pausebutton, then click one of the Step by Event arrow buttons. To resume

a continuous simulation, click the Pause button, then click theRun/Continue button.

To set the simulation back to the Start Time, click the Reset To Startbutton. This sets the simulation back to the Start Time and pauses. Torestart the simulation, click the Run/Continue button or one of theStep by Time or Step by Event arrow buttons.

To advance the simulation to the end of the time window specified forthe simulation, click the Skip To End button. The simulation advancesto the end of the time window and stops.

To close the Xpert Engine Control dialog, click the Dismiss button. The dialog closes; if a simulation is in progress, it continues runningto completion.


59/158

Xpert Basics

Simulation Overrides

To access the Simulation Overrides dialog


60/158


To access the Simulation Overrides dialog

At any interface window, choose Edit Set Simulation Overrides.

Or

From JobScape or TimeScape, place the mouse pointer over the jobgraphic or job name and click the right mouse button to display theJob pop-up menu, then choose Simulation Overrides.

Note • In the Job Name region of TimeScape, Box Jobs display with ahanging indent above their descendant jobs. If the descendants of aBox Job have been hidden, the name of the Box Job appears with anasterisk (*) next to it.

The Simulation Overrides dialog appears, as shown in the following

illustration.

The Simulation Overrides dialog is divided into the following four

regions.

Job Name The Job Name region displays the currently selectedjob; you cannot edit this field.

Completion Status Use the Completion Status region to specify whichcompletion status you want the currently selectedjob to have: Success, Terminated, or Failure.

Xpert Basics


O id C it i E it C d U h E i C d fi ld if i


61/158


Override Criteria Exit Code—Use the Exit Code field to specify an exit

code for the currently selected job. You can enter anumber directly in the text box, or you can use theprovided arrow buttons. The right arrow buttonincreases the number; the left arrow buttondecreases the number. Valid values are 0 to 120.

Number Of Failures—When you specify a failurecondition in the Completion Status region, you use

the Override Criteria region to specify the number offailures you want to occur during the simulation. Tospecify the number of failures, you can enter anumber directly in the text box, or you can use theprovided arrow buttons. The right arrow buttonincreases the number; the left arrow buttondecreases the number. Valid values are 0 to 9.

Duration (HH:MM:SS)—You can specify the runtimeduration for the currently selected job. To specifythis duration, you can enter the time directly in thetext box, or you can use the provided arrow buttons.

The right arrow button increases the time in one-minute increments; the left arrow button decreasesthe time in one-minute increments.

Control Use the Control region to apply simulationoverrides. The following options are available:

OK —Sets the simulation overrides and closes thedialog.

Apply —Sets the simulation overrides and keeps thedialog open.

Cancel—Cancels the operation and closes the dialog.

Xpert Basics


Setting Simulation Overrides 2


62/158


Setting Simulation Overrides 2

To set simulation overrides

1 In the Completion Status region, specify the completion status byclicking one of the radio buttons.

2 If you selected a failure condition, you must specify the number offailures in the Override Criteria region.

Or

If you selected a Success or Terminated condition, you must specifythe duration of the run time for the job in the Override Criteria region;use HH:MM:SS format.

3 Optionally, specify an exit code in the Override Criteria region.

4 To apply the settings and keep the dialog open, click Apply.

Or

To apply the settings and close the dialog, click OK . The overrides areset and the dialog closes.

Removing Simulation Overrides 2

To remove simulation overrides

1 At any interface window, choose Edit Remove All SimulationOverrides. A Confirm dialog appears asking you if you want to removethe overrides.

2 To remove the overrides, click Yes. The overrides are removed and the

dialog closes.

Xpert Basics

Reloading Job Definitions

Reloading Job Definitions


63/158


Reloading Job Definitions 2 When you start any of the three AutoSys/Xpert interfaces, all the jobdefinitions currently in the AutoSys database are used for real-timemonitoring and simulations. Any job definitions that are modified,added to the database, or deleted from the database after you start

AutoSys/Xpert (and while the application is running) can be:

Automatically reloaded

Reloaded on demand

Automatically Reloading Job Definitions 2

By default, job definitions are automatically reloaded. This means that when job definitions change, they are reloaded into AutoSys/Xpert at

appropriate breakpoints. In real-time mode, they are reloaded at the nextautomatic refresh; in simulation mode, they are reloaded at thebeginning of the next simulation.

To turn on/off automatic job definition reloading for current session

At an interface window, select Options

Auto Reload Job Defs. Thisoption is a toggle; an indicator appears when the option is on.

To turn on/off automatic job definition reloading for all sessions

Change the default behavior by modifying the autoReloadJobDefs resource in the application’s X resources file. See Appendix A, XResources for more information.

Reloading Job Definitions on Demand 2

If you want to control when job definitions are reloaded, follow the stepsbelow.

Xpert Basics

Exiting an Interface

To set job definitions to be reloaded on demand


64/158


1 At an interface window, turn off the Options Auto Reload Job Defsoption. (The absence of an indicator box signifies that the option isoff.)

Or

Set the autoReloadJobDefs resource in the application’s X resourcesfile to 0 to turn off automatic reloading for all AutoSys/Xpert sessions.

2 Choose File Reload Job Defs.

You can choose Reload Job Defs as often as you want. The Reload JobDefs option displays with black type face if any job definitions havebeen added, modified, or deleted since you started AutoSys/Xpert, orsince the last reload. Otherwise, the option is grayed out, indicatingthat no job definition changes have occurred. This option cannot be

chosen if it is grayed-out.

Note • You cannot reload job definitions during a simulation. If youchoose the Auto Reload Job Defs or Reload Job Defs options during asimulation, a dialog appears stating that if you continue, thesimulation will be paused in order to reload job definitions. If youcontinue with the reload, you must restart the simulation manually.

Exiting an Interface 2 When you exit any of the AutoSys/Xpert interfaces, all other windowsthat are open (such as the Job Console or Alarm Manager) close.

To exit an AutoSys/Xpert interface

1 At an interface window, choose File Exit. A Confirm dialog appearsasking you to verify that you want to exit.

2 To exit the interface, click OK. The interface window closes.


65/158


3Using HostScape

This chapter provides information about using the HostScape interface.Before reading this chapter, be sure you have read Chapter 2, Xpert Basics.

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Displaying Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

atsxugu.pdf

Documents