Unicenter AutoSys Job Management for Windows

£

£

User Guide
4.5

This documentation and related computer software program (hereinafter referred to as the “Documentation”) is for the end 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 or duplicated, in whole or in part, without the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties. Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies. This right to print copies is limited to the period during which the license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to return to CA the reproduced copies or to certify to CA that same have been destroyed. To the extent permitted by applicable law, CA provides this documentation “as is” without warranty of any kind, including without limitation, any implied warranties of merchantability, fitness for a particular purpose or noninfringement. In no event will CA 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, business interruption, goodwill, or lost data, even if CA is expressly advised of such loss or damage. The use of any product referenced in this documentation and this documentation is governed 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) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.

” 2003 Computer Associates International, Inc.
All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Contents

Chapter 1: Introduction
Related Publications Jobs
..........................................................................

1–2 1–2 1–3 1–3 1–4 1–5

.........................................................................................

Defining Jobs ............................................................................. 1–2 Graphical User Interface System Components
............................................................... .............................................................

Job Information Language

..........................................................................

Event Server .............................................................................. 1–5 High-Availability Option: Dual-Event Servers
...........................................

Event processor ........................................................................... 1–6 High-availability Option: Shadow Event Processor ....................................... 1–6 Remote Agent
............................................................................

1–7

Example Scenario on Windows ............................................................. 1–8 Explanation ........................................................................... 1–9 Interface Components .................................................................... 1–10 Machines
................................................................................... 1–10

Instance ..................................................................................... 1–10 Events ...................................................................................... 1–11 Alarms
..................................................................................... 1–11

Utilities ..................................................................................... 1–12 Basic Functionality ........................................................................... 1–12 Explanation
............................................................................. 1–13

Extending Functionality ...................................................................... 1–15 Contacting Technical Support ................................................................. 1–16

Contents

iii

Chapter 2: Security
Overview .....................................................................................2–1 Native Security
...............................................................................2–2

Security On Events Sent By Users ...........................................................2–2 Security On Events Sent By the Event Processor System-Level Security
..............................................2–4 .........................................................................2–7

Database Field Verification .................................................................2–7 Job Definition Encryption
..................................................................2–7 ..............................................................2–8

Remote Agent Authentication

User Authentication....................................................................2–8 Event processor Authentication .........................................................2–9 User and Database Administrator Passwords
................................................2–9

Job-Level Security ........................................................................... 2–10 Job Ownership .......................................................................... 2–10 User Types.............................................................................. 2–11 Permission Types ........................................................................ 2–11 Granting Permissions
................................................................

2–12

Job Permissions and Windows ............................................................ 2–13 Security Control ......................................................................... 2–13 Superuser Privileges ......................................................................... 2–14 Edit Superuser
..........................................................................

2–14 2–16 2–17 2–19 2–20

Exec Superuser .......................................................................... 2–15 Restricting Access to Jobs eTrust Access Control Policy Manager
....................................................................

Remote Agent Security ................................................................... 2–17
....................................................................... .........................................................................

Security Access .......................................................................... 2–19 Disable Security
.....................................................................

Controlling the Event Processor ........................................................... 2–20 Asset-Level Security ..................................................................... 2–21 eTrust Resource Classes .............................................................. 2–22 eTrust Access Modes ................................................................. 2–23 Security Enabled Applications ............................................................ 2–33 Security Call Logic....................................................................... 2–34

iv

User Guide

Chapter 3: Jobs
Job Types and Structure ....................................................................... 3–2 Basic Job Information ...................................................................... 3–2 Command Jobs
...........................................................................

3–3

Box Jobs .................................................................................. 3–3 Starting Conditions for Box Jobs ........................................................ 3–4 File Watcher Jobs
.........................................................................

3–5

Job Profiles ................................................................................... 3–6 Using the Job Profiles Manager ............................................................. 3–8 Basic Job Attributes .......................................................................... 3–11 Command Job Attributes
................................................................. 3–11 ............................................................... 3–11

File Watcher Job Attributes

Box Job Attributes ........................................................................ 3–12 Job States and Status ......................................................................... 3–13 Example State Diagram: Simple Jobs ....................................................... 3–15 Example State Diagram: Box Jobs .......................................................... 3–17 Starting Parameters .......................................................................... 3–19 Starting Parameters and Boxes
............................................................ 3–19

Date/Time Dependencies ................................................................. 3–20 TZ Environment Variable ............................................................. 3–20 Custom Calendars.................................................................... 3–21 Job Dependencies Related to Job Status Cross-Instance Job Dependencies
.................................................... 3–21 ...................................................... 3–23

Event processors ......................................................................... 3–25 Event Servers ............................................................................ 3–25 Example Job Dependencies ............................................................ 3–26 Managing Job Status .................................................................. 3–27 Job Dependencies Based on Exit Codes ..................................................... 3–28 Using Exit Codes and Batch Files with Jobs Running on Windows Job Dependencies Based on Global Variables
........................ 3–29 ............................................... 3–30

Job Run Numbers and Names................................................................. 3–31 Defining Jobs ................................................................................ 3–32 Graphical User Interface Components...................................................... 3–32

Contents

v

Chapter 4: Job Attributes
Job Attributes and Job Definitions
..............................................................4–1 .........................................................4–2 ...............................................4–2

Using JIL to Create a Job Definition

Using the Job Editor to Create a Job Definition

Organization ..............................................................................4–3 Essential Job Attributes ........................................................................4–4 Attributes Common to All Job Types ........................................................4–4 Job Name .............................................................................4–4 Job Type ..............................................................................4–4 Job Owner Command
............................................................................4–4

Command Jobs Attributes ..................................................................4–5
............................................................................4–5 ....................................................................4–7

Machine to Run On Machine to Run On File to Watch For Optional Job Attributes

File Watcher Job Attributes .................................................................4–8
....................................................................4–8 ......................................................................4–8

Box Job Attributes .........................................................................4–8
........................................................................4–9

Common Job Starting Attributes ............................................................4–9 Start Date /Time Dependence...........................................................4–9 Days of the Week ......................................................................4–9 Days to Run on —Using a Custom Calendar
.............................................4–9

Days to NOT Run on—Using a Custom Calendar ....................................... 4–10 Specific Times of Day to Run.......................................................... 4–10 Time of Day Not to Run .............................................................. 4–10 Specific Times Every Hour to Run ..................................................... 4–11 Job Dependencies .................................................................... 4–11 Common General Attributes .............................................................. 4–12 Description.......................................................................... 4–12 Box Name ........................................................................... 4–12 Minimum Run Time Alarm ........................................................... 4–12 Maximum Run Time Alarm Terminate Due to Run Time
.......................................................... ..........................................................

4–13 4–13

Send Alarm if the Job Fails ............................................................ 4–13 Terminate the Box if the Job Fails ...................................................... 4–14

vi

User Guide

Terminate the Job if the Box Fails

...................................................... 4–14

Number of Times to Restart a Job ...................................................... 4–15 Time Zone for Job .................................................................... 4–15 Delete Job After Completion........................................................... 4–16 Autohold ............................................................................ 4–16 Permissions .......................................................................... 4–17 Command Job Attributes
................................................................. 4–18

Profile ............................................................................... 4–18 Redirection of the Standard Input File .................................................. 4–19 Redirection of the Standard Output File ................................................ 4–19 Redirection of the Standard Error File .................................................. 4–20 Job Load............................................................................. 4–21 Queue Priority ....................................................................... 4–21 Job Overrides ........................................................................ 4–22 Maximum Exit Code for Success ....................................................... 4–22 Average Runtimes.................................................................... 4–23 Heartbeat-Interval .................................................................... 4–23 Resource Check - File Space ........................................................... 4–24 File Watcher Job Attributes
............................................................... 4–25

Watch File Minimum Size ............................................................. 4–25 Watch Interval ....................................................................... 4–25 Resource Check - File Space ........................................................... 4–25 Box Job Attributes ........................................................................ 4–26 Box Successful Completion ............................................................ 4–26 Box Failure
.......................................................................... 4–26

Date and Time Attributes and Time Changes ................................................... 4–27 The Time Change ........................................................................ 4–27 Behavior During Time Change ............................................................ 4–28 Spring Time Change .................................................................. 4–29 Fall Time Change
.................................................................... 4–31

Testing the Fall Time Change .......................................................... 4–32

Contents

vii

Chapter 5: Box Job Logic
Basic Box Concepts ............................................................................5–1 Default Box Job Behavior ...................................................................5–1 When You Should Not Use a Box What Happens When a Box Runs Simple Box Job
...........................................................5–2 ...........................................................5–3

........................................................................5–4

Box Job Attributes and Terminators .............................................................5–5 Attributes in a Box Job Definition Attributes in a Job Definition
...........................................................5–5

Example of a Non-Default Success Condition .............................................5–5
...............................................................5–6

Time Conditions in a Box...................................................................5–6 Force Starting Jobs in a Box .................................................................5–8 How Job Status Changes Affect Box Status ...................................................5–9 Examples ................................................................................... 5–10 Advanced Conditions in Box Jobs ......................................................... 5–10 Default Box Success and Box Failure Explicit Box Success and Box Failure
...................................................... ......................................................

5–12 5–13

Using the Box Terminator Attribute ....................................................... 5–14 Using the Job Terminator Attribute ........................................................ 5–15 Advanced Job Streams ................................................................... 5–16 Scenario On the First of the Month Scenario On the Second of Month
....................................................

5–16 5–17

.....................................................

Scenario I On First of the Month ....................................................... 5–18 Scenario II On First of the Month ...................................................... 5–19 Scenario III On First of the Month
.....................................................

5–20

viii

User Guide

Chapter 6: Introduction to the Graphical User Interface
Starting the GUI Control Panel ................................................................. 6–1 Using the GUI Control Panel ................................................................... 6–2 GUI Control Panel Menu Bar ............................................................... 6–2 File Menu
............................................................................

6–2 6–3 6–4

Tools Menu ........................................................................... 6–3 Preferences Menu Help Menu
..................................................................... ...........................................................................

GUI Control Panel Buttons ................................................................. 6–4

Chapter 7: Defining Jobs Using the Job Editor
Starting the Job Editor ......................................................................... 7–1 Using the Job Editor Interface .................................................................. 7–3 Job Editor Menu Bar....................................................................... 7–3 File Menu
............................................................................

7–3 7–5 7–5 7–5 7–6

Edit Menu ............................................................................ 7–4 Options Menu Help Menu Job Editor Tabs
........................................................................ ........................................................................... ...........................................................................

Job Editor Status Area ..................................................................... 7–6 Required Values for Command Jobs
....................................................

Required Values for Box Jobs ........................................................... 7–7 Required Values for File Watcher Jobs................................................... 7–7 Creating a Simple Command Job ............................................................... 7–8 Creating a File Watcher Job ................................................................... 7–10 Creating a Dependent Command Job .......................................................... 7–12 Creating a Box Job
........................................................................... 7–14

Creating the EOD_box Box Job ............................................................ 7–14 Modifying the EOD_post Command Job
................................................... 7–16

Setting Date and Time Dependencies .......................................................... 7–18 Setting Days of the Week Starting Conditions ............................................... 7–19 Setting the Run Days Option Setting Time Starting Conditions
.......................................................... 7–19

Setting Run Calendar and Exclude Calendar Options .................................... 7–20
.......................................................... 7–20

Contents

ix

Setting Time Zones Deleting Jobs

.................................................................. ..........................................

7–21 7–22 7–24 7–25 7–26 7–27

Example on Setting Date and Time Dependencies Notes on Deleting a Box Job Setting Job Overrides

............................................................................... ..............................................................

Specifying One-Time Job Overrides ........................................................... 7–26
.................................................................... ........................................................

Notes on One-Time Overrides

Deleting One-Time Overrides............................................................. 7–28 Enabled Job Editor Fields for One-Time Overrides .......................................... 7–28

Chapter 8: Defining Jobs Using JIL
Job Information Language (JIL) .................................................................8–1 JIL Syntax Rules ...........................................................................8–2 Rule 1 Rule 2 Rule 3 Rule 4 Rule 5 Rule 6 Rule 7
................................................................................8–2 ................................................................................8–2 ................................................................................8–2 ................................................................................8–2 ................................................................................8–3 ................................................................................8–3 ................................................................................8–3 ........................................................................8–4 .................................................................8–4

JIL Sub-commands

Submitting Job Definitions

Running JIL ...............................................................................8–5 Creating a Simple Command Job Creating a File Watcher Job Creating a Box
...............................................................8–5 ....................................................................8–6

Creating a Dependent Command Job............................................................8–7
................................................................................8–9

x

User Guide

................................ 9–4 9–5 9–5 9–7 9–7 9–9 9–9 Using the Calendar Editor Interface File Menu Using the Menu Bar .................................................... ........................................................................ 8–13 Setting Job Overrides ..... 9–10 Calendars Area ............................................................................................................ 8–11 Additional Time Setting Features ............................................................................................. 8–11 Deleting a Job .......................................................................................... 9–13 Setting Dates Prior to Today’s Date Applying Rules to Calendars .......................................................................... 9–9 ........................... 9–15 ........................................................................................................................................... ............................................................................................. 8–15 Chapter 9: Calendar Editor Using Defined Calendars ................................................................ ...... 9–13 Creating a Calendar .... 9–18 Using the Rule Specification Area Action Area............................. 9–11 Date States.................... 8–10 Setting Time Dependencies ........ 9–2 Starting the Calendar Editor ............................................................................................................................................................................. 9–2 Scheduling Jobs with Calendars ................................................................................... Preferences Menu .......... 9–17 ........ 9–7 Utilities Menu Help Menu ....... 8–14 Example JIL Script ....................................................................................................................... 9–5 ................................................................ 9–10 Using the Calendar Display .............. 8–12 Specifying One-Time Job Overrides ....................................................................................................................................................................................................... 9–14 Opening an Existing Calendar................................. 9–18 Contents xi . 8–12 Deleting a Box Job ................................... Edit Menu .............................................................Changing a Job ........................................................................................................................................................................................................................................................................................................... 9–11 Creating and Modifying Calendars ................................................................... 9–10 Instance Area ................................................................... Using the Navigation Controls Conflicts Area Selections Area .................

............................ Specifying Machine Load (max_load) Job Attributes and Load Balancing and Queuing Specifying Relative Processing Power (factor) ................ 10–7 Deleting Real Machines Defining a Virtual Machine Load Balancing .................. 10–10 ......................... 10–1 10–2 10–3 10–4 Virtual Machines ............................................................................... 9–27 Exporting Calendars ..............................................................Date Range Area...................... Move Direction Area ........................................................................................................................... 10–5 Machine Definitions ................................................................. 9–28 Chapter 10: Load Balancing and Queing Jobs Real Machines .............................................................................................................................................................................................. Combining Calendars Example .............. ................................................................ ........... 9–24 Using the Job Definition Reference List ............................................................................. 9–19 9–22 9–23 9–23 9–24 Date Selection Rule Examples .......................................................... 9–22 ...... ........................................................................................................ Rescheduling Rule Example Combining Existing Calendars ................................................................................................... 9–26 Importing and Exporting Calendars ....... ............................................................................ 10–11 xii User Guide ................................................................................................................. 10–7 10–8 Deleting Virtual Machines . 9–27 Importing Calendar Text Files ....................................................................................................................................... 9–20 Using the Rescheduling Rule Area To Day Area ............................................ 10–6 Defining a Real Machine .................................. 10–4 Using max_load and factor ................................................................................................................................... 10–2 Defining Machines ............................................... 9–19 Date Selection Rule Area ......

........................... 11–8 Using the Summary Area ............................ 11–3 Actions Menu ....................................................................................... 11–9 Defining Scheduler Console Filters ................................. 11–16 Using Scheduler Console Tools Using the Run Status Tool .............................................................................................................................. 11–3 Tools Menu .................................................................................... 11–17 Using the Job Dependencies Dialog .. 10–17 Load Units and Virtual Machines ........................................................................ 11–7 Using the Control Area ...................................................................................................................... 11–12 ....................................................................................................................................................................................................Force Starting Jobs ............................................................................................................................... 11–3 ......................................... 11–6 ............ 11–14 Machines/Instances Tab ................... 11–6 Preferences Menu Help Menu ..................................................... 11–13 Names Tab Status Tab ............... 10–15 Subsets—Individual Queues ............................................... 10–18 User-Defined Load Balancing ................................................................................................................... 11–11 Filters Editor Dialog ............................. 10–13 Queuing Jobs ......................................................................................................................... 11–20 Contents xiii .............. 11–18 ............................................................................................................................................................................................................. 11–5 Reports Menu ............................................................ 11–5 Applications Menu ..................................... 11–15 Using the Filter Editor .... 11–9 Selecting Jobs ........................................................................................... 10–18 Multiple Machine Queues ............................................................................................................................................................................................................................. 11–3 Filters Menu .......... 11–8 Summary Area Information ...................... 11–1 Using the Scheduler Console Menu Bar File Menu ............. 10–14 Queuing with Priority ................ 11–12 File Menu ........................... 10–13 Queuing and Simple Load Limiting............... 10–19 Chapter 11: Scheduler Console Using the Scheduler Console ...............................................

Run Status Tool Menu Bar ........................................................... 11–21 Run Status Tool Display Fields ....................................................... 11–22 Using the Send Event Tool
..............................................................

11–23 11–25

Opening the Send Event Tool ........................................................ 11–24 Send Event Tool Menu Bar
..........................................................

Send Event Tool Fields .............................................................. 11–26 Sending an Event ................................................................... 11–29 Canceling a Sent Event .............................................................. 11–30 Using Scheduler Console Reports ............................................................ 11–32 Using the Job Detail Report Tool ......................................................... 11–32 Job Detail Report Menu Bar .......................................................... 11–33 Setting Scheduler Console Preferences
.......................................................

11–34

Using the General Dialog ................................................................ 11–35 Using the User-Defined Buttons Dialog ................................................... 11–36 Creating Command Buttons
......................................................... ..................................................

11–36 11–37

Using AutoSys-Specific Commands

Using the User Defined Reports Dialog ................................................... 11–38 Creating Reports Menu Items ........................................................ 11–38 Using the Summary Area Layout Dialog .................................................. 11–39 Customizing the Summary Area in the Scheduler Console .............................. 11–39 Customizing the Display with the Summary Area Layout Dialog ........................ 11–40 Sort Key Settings
...................................................................

11–41

Using the Action Area Layout Dialog..................................................... 11–42 Action Area Layout Tool and Action Buttons .......................................... 11–43 Setting the Time Perspective ............................................................. 11–44

Chapter 12: Managing Alarms
Using the Alarm Sentry ...................................................................... 12–1 Using the Alarm Sentry Menu Bar
........................................................

12–2

File Menu ........................................................................... 12–2 Preferences Menu .................................................................... 12–2 Help Menu .......................................................................... 12–2 Using the Alarm Manager .................................................................... 12–3 Using the Alarm Manager Menu Bar
......................................................

12–4

xiv

User Guide

File Menu

........................................................................... 12–4

Filters Menu ......................................................................... 12–4 Tools Menu .......................................................................... 12–5 Preferences Menu Help Menu
.................................................................... 12–5 .......................................................................... 12–6

Using the Alarm Manager Alarm List ...................................................... 12–6 Viewing the Currently Selected Alarm ..................................................... 12–7 Registering Responses and Changing Alarm States ...................................... 12–8 Setting the Refresh Behavior
.............................................................. 12–8

Filtering Alarms ............................................................................. 12–9 Selecting Alarms by Type ................................................................ 12–10 Selecting Alarms by State ................................................................ 12–11 Selecting Alarms by Instance ............................................................. 12–11 Selecting Alarms by Time ................................................................ 12–11

Chapter 13: Monitoring and Reporting on Jobs
Using AutoSys Monitors and Browsers Using Reports
........................................................ 13–1

Using Monitors .......................................................................... 13–2
........................................................................... 13–3

Using the Monitor/Browser Editor ............................................................ 13–4 Using the Monitor/Browser Editor Menu Bar............................................... 13–5 File Menu
........................................................................... 13–5

Edit Menu ........................................................................... 13–6 Help Menu
.......................................................................... 13–6

Defining Monitors and Reports with the Editor ................................................. 13–7 Defining a Monitor ....................................................................... 13–7 Defining a Report ........................................................................ 13–9 Closing the Monitor/Browser Editor ...................................................... 13–10

Contents

xv

Setting Monitor and Report Attributes Setting the Job Selection Criteria

.......................................................

13–11 13–13

Setting Event Types ..................................................................... 13–11
.........................................................

Setting Monitor Options................................................................. 13–14 Setting the Browser Time Criteria ........................................................ 13–15 Running a Monitor or Generating a Report
...................................................

13–16

Defining Monitors and Reports Using JIL ..................................................... 13–17 Defining Monitors Using JIL ............................................................. 13–18

Chapter 14: Maintaining
Maintaining the Event Processor .............................................................. 14–1 Starting the Event Processor .............................................................. 14–1 Event Processor Starting Processes
....................................................

14–2 14–4 14–4 14–5

Monitoring the Event Processor ........................................................... 14–3 Location of the Event Processor Log File Event Processor Log File Size
............................................... ......................................................... ........................................

Starting the Event Processor in Global Auto Hold Mode

Stopping the Event Processor ............................................................. 14–7 Shadow Event Processor Rollover ......................................................... 14–8 Restoring the Primary Event Processor................................................. 14–9 Maintaining the Remote Agent Stopping a Remote Agent
..............................................................

14–10 14–11

Starting the Remote Agent............................................................... 14–10
...............................................................

Running in Test Mode ...................................................................... 14–12 %AUTOTESTMODE% = 1............................................................... 14–13 %AUTOTESTMODE% = 2............................................................... 14–13 Maintenance Commands .................................................................... 14–14 chase .................................................................................. 14–14 clean_files
.............................................................................

14–15

Backing up Definitions...................................................................... 14–16 Restoring Definitions ....................................................................... 14–18 Database Overview ......................................................................... 14–19 Event Server Overview
..................................................................... ..........................................................

14–20 14–20

Using Dual Event Server Mode

xvi

User Guide

Database Storage Requirements

.......................................................... 14–21

Database Architecture ....................................................................... 14–22 General Database Maintenance............................................................... 14–23 Daily Database Maintenance ............................................................. 14–23 DBMaint.bat Batch File .................................................................. 14–24 Modifying the DBMaint.bat File .......................................................... 14–25 Data Locking ........................................................................... 14–25 Event Server Rollover Recovery .............................................................. 14–26 Returning to Dual Server Mode After a Rollover ........................................... 14–27 Synchronizing the Databases ............................................................. 14–28 To synchronize the databases ......................................................... 14–29 Synchronizing Sybase Databases...................................................... 14–30 Synchronizing Oracle Databases ...................................................... 14–31 Synchronizing Microsoft SQL Server Databases ........................................ 14–31 Handling Errors ..................................................................... 14–32 Improving Database Performance ............................................................ 14–33 Improving Sybase Database Performance
................................................. 14–33

Improving Oracle Database Performance .................................................. 14–33 Maintaining Bundled Sybase SQL Servers ..................................................... 14–35 Sybase Architecture ..................................................................... 14–35 Sybase Environment
.................................................................... 14–35

Default Sybase Users .................................................................... 14–36 Database Users...................................................................... 14–36 Changing the System Administrator Password ......................................... 14–37 Starting Sybase
......................................................................... 14–37 ........................................................................ 14–38 ....................................................................... 14–39

Stopping Sybase

Accessing Sybase

Identifying Processes Connected to the Database ........................................... 14–40 Displaying the Database Date and Time ................................................... 14–41

Contents

xvii

Bundled Sybase Backup and Recovery.................................................... 14–41 Configuring a Backup Server
........................................................

14–42

Backing up the Database to a File ..................................................... 14–43 Recovering a Bundled Sybase Database ............................................... 14–43 Stopping the Event Processor
........................................................ ....................................................

14–44 14–44 14–45

Dropping the Damaged Database Reloading the Database

Re-Creating the Database ............................................................ 14–44
.............................................................

Restarting the Event Processor ....................................................... 14–45

Chapter 15: Administrator
About the Administrator ..................................................................... 15–1 Starting the Administrator
................................................................... .....................................................

15–3 15–3 15–4 15–6

Administrator Menu Bar and Toolbar Administrator Menu Bar Instances

.............................................................

...................................................................................

Administrator Instance Screen ............................................................ 15–7 Remote Agents .............................................................................. 15–9 Administrator Remote Agent Screen
......................................................

15–9

Defining Remote Agent Configuration Parameters ..................................... 15–10 Event Servers .............................................................................. 15–12 Dual-Event Servers ..................................................................... 15–12 Administrator Event Server Screen ....................................................... 15–13 Defining Event Server Configuration Parameters
......................................

15–14

Event Processors ........................................................................... 15–18 Administrator Event Processor Screen .................................................... 15–19 Defining Event Processor Configuration Parameters
...................................

15–20

Event Processor Options ............................................................. 15–31 Broker Options ..................................................................... 15–34 Notification Mechanism
....................................................................

15–35

Administrator Notifications Screen ....................................................... 15–36 Notification Example................................................................ 15–37 Defining Notifications Configuration Parameters ...................................... 15–37 System Information
........................................................................

15–38

xviii

User Guide

Administrator System Information Screen ................................................. 15–39 Using the System Information Screen Sounds
................................................. 15–40

System Information Configuration Parameters ......................................... 15–40
.................................................................................... 15–43 ............................................................ 15–43

Administrator Sounds Screen

Defining Sounds Configuration Parameters ............................................ 15–44 Security .................................................................................... 15–46 User Remote Authentication Example..................................................... 15–47 Administrator Security Screen ............................................................ 15–48 Defining Security Configuration Parameters ........................................... 15–49 Services .................................................................................... 15–50 Administrator Services Screen ............................................................ 15–50 Services Screen Components Using the Services Screen
......................................................... 15–52 ............................................................ 15–53

Chapter 16: Troubleshooting
Introduction ................................................................................. 16–2 Windows Services Troubleshooting
........................................................... 16–3

Event Server Troubleshooting ................................................................. 16–4 Event Server Is Down (Sybase) ............................................................ 16–4 Sybase Deadlock ......................................................................... 16–5 Not Enough User Connections (Bundled Sybase) ............................................ 16–6 archive_events Fails (Bundled Sybase)
..................................................... 16–8 ......................................... 16–9

Event Server Unable to Extend Tablespace (Oracle) Event Processor Is Down

Event Processor Troubleshooting .............................................................. 16–9
................................................................ 16–10 ........................................................... 16–10

Event Processor Will Not Start

Contents

xix

Remote Agent Troubleshooting .............................................................. 16–15 Remote Agent Verification Database Verification
..............................................................

16–15 16–15 16–16 16–17 16–20

autoping ........................................................................... 16–15
............................................................... ............................................................ ........................

Remote Agent Will Not Start

Remote Agent Starts, Command Runs: No RUNNING Event Is Sent xql Will Not Start (Sybase Only)

.........................................................

Job Failure Troubleshooting ................................................................. 16–21 Remote Agent Will Start: Command Will Not Run ......................................... 16–21

Appendix A: Integrating with the Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS
Definition of Terms ........................................................................... A–2 Related Documentation ................................................................... A–3 Job Scheduling for the Enterprise
.............................................................. A–4

Prerequisites ............................................................................. A–4 Configuring for Enterprise Job Scheduling ...................................................... A–5 Stop the Event Processor
.................................................................. A–5

Configure the Machine .................................................................... A–5 Set the AutoSysAgentSupport Parameter
............................................... A–5 ...................................... A–5

Set the Receive Remote Job Submissions Parameter

Create the config.EXTERNAL File ...................................................... A–6 config.EXTERNAL Examples: .......................................................... A–7 Ensure Consistent Integration Settings .................................................. A–7 Configure the Communication Components ............................................. A–8 Restart the Event Processor ................................................................ A–8 About asbIII
................................................................................. A–9

Environment Variable for asbIII ........................................................... A–10 PRIMARYCCISYSID ................................................................. A–10 Bi-Directional Scheduling
................................................................ A–11

Running Jobs on Behalf of a Workload Manager ........................................ A–11 Unicenter AutoSys JM Connect Cross-Platform Dependencies ................................... A–12 Job Scheduler Interdependencies .......................................................... A–13 Notation for Cross-Platform Job Dependencies ............................................. A–14

xx

User Guide

Unicenter AutoSys JM Connect Cross-Platform Dependency Example .................... A–15 Naming Conventions for Unicenter AutoSys JM Connect Cross-Platform Jobs
................

A–15

Running Jobs on Agents ..................................................................... A–16 Agent Job Names and User IDs ........................................................... A–17 Running Jobs On Agent Managed Machines ............................................... A–17 Defining Agent Machines ................................................................ A–18 Job Definition Examples Log and Trace Information
.............................................................

A–19 A–20 A–22 A–23

Unicenter AutoSys Agent Machine In an Job Definition ..................................... A–20
..................................................................

Unicenter AutoSys JM Connect and Unicenter AutoSys Agent Job Statuses ....................... A–21 Unsupported Attributes for Unicenter AutoSys JM Connect or Unicenter AutoSys Agent Jobs Cross-Platform Limitations
..... ..................................................................

Appendix B: Troubleshooting CCI
Troubleshooting Tools for Remote CCI Connections netstat ping
............................................. B–1 ................................................................................... B–1

..................................................................................... B–2

nslookup ............................................................................. B–2 traceroute and tracert .................................................................. B–3 ccinet
................................................................................ B–3 .................................................................. B–4

CCI Command Line Controls

ccicntrl ................................................................................... B–4 ccicntrl [start | stop] [tpd, nrs, nrc, rmt]
................................................. B–4

ccicntrl install [tpd | nrs | nrc | rmt ] PATH ............................................. B–4 ccicntrl status ......................................................................... B–4 rmtcntrl .................................................................................. B–5 rmtcntrl status
........................................................................ B–5 ................................................ B–5

rmtcntrl debugon and rmtcntrl debugoff rmtcntrl rrt

rmtcntrl hats .......................................................................... B–5
........................................................................... B–5

rmtcntrl ping sysid .................................................................... B–6 rmtcntrl reconnect [All] sysid ........................................................... B–6 rmtcntrl disconnect sysid rmtcntrl release
.............................................................. B–6 ....................................................................... B–6

Contents

xxi

Appendix C: General Debugging
Values
......................................................................................

C–1

Appendix D: Unicenter Integration
Running Unicenter AutoSys JM 4.5/Unicenter NSM Framework Integration Utility
............ D–1

Modifying Admin Configuration to Publish Events to the Unicenter Console................... D–4 After the Integration Process ........................................................... D–5 Removing Icons from WorldView ...................................................... D–6

xxii

User Guide

Chapter

1

Introduction

This guide is for users responsible for defining jobs to Unicenter AutoSys Job Management (Unicenter AutoSys JM) and monitoring and managing these jobs. It assumes familiarity with the operating system on which jobs will be run, and it assumes that you have already installed and are running Unicenter AutoSys JM using the procedures described in the Unicenter AutoSys Job Management for

Windows Installation Guide.
Unicenter AutoSys JM is an automated job control system for scheduling, monitoring, and reporting. These jobs can reside on any configured machine that is attached to a network. Note: In this guide, the term Windows refers to Microsoft Windows operating systems, Windows NT and higher. Unless specifically designated, Windows refers to any Microsoft Windows operating system supported by AutoSys. A job is any single command, executable, script, or Windows batch file. Each job definition contains a variety of qualifying attributes, including the conditions specifying when and where a job should be run. As with most control systems, there are many ways to correctly define and implement jobs. It is likely that the way you utilize Unicenter AutoSys JM to address your distributed computing needs will evolve over time. As you become more familiar with both the features of Unicenter AutoSys JM and the characteristics of your own jobs, you will also refine your use of Unicenter AutoSys JM. However, before you install and use Unicenter AutoSys JM, it is important to understand the basic system, its components, and how these components work together. This chapter provides a brief overview of Unicenter AutoSys JM, its system architecture, and features.

Introduction

1–1

and the API. and report definition parameters. In addition. job definitions include a set of qualifying attributes. and on Windows. These specifications make up the job definition. Defining Jobs Using utilities. which provides important information about this release. including how to configure components. managing. monitoring. database tables and views. executable. On UNIX. running. or batch file. ■ Unicenter AutoSys Job Management for Windows Installation Guide. and high-availability features. You can use the following methods to create job definitions: ■ ■ Using the graphical user interface (GUI). machine. monitor. you may find it helpful to have these additional books available for reference: ■ Unicenter AutoSys Job Management Release Summary. 1–2 User Guide . Jobs In the Unicenter AutoSys JM environment. databases. which lists the commands and job. see the chapters in this guide. In addition. this action can be any single command. and reporting on jobs. ■ Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. you can define a job by assigning it a name and specifying the attributes that describe its associated behavior. For information on defining. a job is a single action that can be performed on a valid client machine. Please read this before proceeding. how to install Unicenter AutoSys JM. this action can be any single command or shell script.Related Publications Related Publications As you use this Unicenter AutoSys Job Management for Windows User Guide. this guide describes how to enter license keys. It also describes system states. which describes the basic configurations. Using the Job Information Language (JIL) through a command-line interface.

from the GUI Control Panel. The fields in the GUIs correspond to the JIL subcommands and attributes. that is used to describe when. and how a job should run. you get the jil command prompt. When you enter the jil command. and how a job should run. Job Information Language JIL is a specification language. When you exit JIL. where. Alternatively. monitors. you can enter the definition as a text file and re-direct the file to the jil command. the jil command activates the language processor. In addition. with its own syntax. where. interprets the information in the text file.Jobs Graphical User Interface The GUI allows you to interactively set the attributes that describe when. Introduction 1–3 . and reports. you can open applications that allow you to define calendars. and loads this information in the database. at which you can enter the job definitions one line at a time using this special language. the job definition is loaded into the database. and that allow you to monitor and manage jobs. You create job definitions using the GUI Control Panel and the dialogs you can launch from it. In this case.

however. The following illistration shows the system components in a basic configuration. this displays the communication paths between the components. and maintain instances and jobs. all platforms include the GUI components and JIL. monitor. In addition. run. 1–4 User Guide . Unicenter AutoSys JM provides utilities to help you define. manage. The included utilities are platform-specific. and report on jobs. Both the GUI and JIL allow you to define.System Components System Components The following are the main system components: ■ ■ ■ Event server (database) Event processor Remote agent In addition.

This feature provides complete redundancy. Introduction 1–5 . the database is called a data server. which can include multiple databases or tablespaces. Therefore. see Dual-event Servers in the chapter “Introduction” in the Unicenter AutoSys Job Management for Windows Installation Guide. and it is associated data space (or raw disk storage). For various reasons. monitor. operations can continue on the second event server without loss of information or functionality. Event server refers to the database where all the information. That is. When implementing Unicenter AutoSys JM. the database can run stand-alone for Unicenter AutoSys JM only. allow you to specify a particular server and database. and report definitions. High-Availability Option: Dual-Event Servers Unicenter AutoSys JM can be configured to run using two databases. or network problems. software. or dualevent servers. Occasionally. which actually describes a server instance. For more information about using dual-event servers. Note: The database refers to the specific server instance and the “autosys” database for that instance. it is either a UNIX or Windows process. events.System Components Event Server The event server or database (the RDBMS) is the data repository for all system information and events as well as all job. such as isql (Sybase) and ISQL/w (Microsoft SQL Server). and job definitions are stored. or it can be shared with other applications. Some utilities. database users often run multiple instances of servers that are unaware of the other servers on the network. if you lose one event server due to hardware.

called the shadow event processor. the event processor first determines what actions are to be taken. if the primary event processor fails for some reason. Basically. it checks whether the event satisfies the starting conditions for any job in the database. After you start it. the event processor is the program.System Components Event processor The event processor is the heart of Unicenter AutoSys JM. It schedules and starts jobs. For more information about running a shadow event processor. running either as a UNIX process or as a Windows service that actually runs Unicenter AutoSys JM. checking for resources. see Shadow Event processor in the chapter “Introduction. 1–6 User Guide . However. monitoring existing jobs. These actions may be the starting or stopping of jobs. then instructs the appropriate remote agent process to perform the actions. it interprets and processes all the events it reads from the database. or initiating corrective procedures. The shadow event processor remains in an idle mode. Based on this information. When it finds one.” in the Unicenter AutoSys Job Management for Windows Installation Guide. High-availability Option: Shadow Event Processor Unicenter AutoSys JM lets you set up a second event processor. these messages indicate that all is well. This second processor should run on a separate machine to avoid a single point of failure. the shadow event processor will take over the responsibility of interpreting and processing events. Sometimes called the event_demon. the event processor continually scans the database for events to be processed. receiving periodic messages (pings) from the primary event processor.

the remote agent is a temporary process started by the event processor to perform a specific task on a remote (client) machine. the remote agent is a Windows service running on a remote (client) machine that is directed by the event processor to perform specific tasks.System Components Remote Agent On a UNIX machine. The remote agent starts the command specified for a given job. sends running and completion information about a task to the event server. If the remote agent is unable to transfer the information. On a Windows machine. Introduction 1–7 . and then exits. it waits and tries again until it can successfully communicate with the database.

and remote agents. PROCESS Remote Agent • Receives instructions from Event Processor • Initiates Action: Starts Child Process • Waits for Exit Code (From Child Process) • Sends Exit event back to Event Server PROCESS PROCESS 1 Event Processor • Determines Actions • Initiates Action: Start job on machine command: 'del C:\tmp\*. In the example. the event processor.* Note: Understanding this example will help you answer many questions that may arise during your experiences with Unicenter AutoSys JM. the three primary components are shown running on different machines.*' 2 3 5 PROCESS Event Server • Events • Job Definitions WorkStation_2 PROCESS Windows NT/2000 Command 4 • Runs NT/2000 command: 'del C:\tmp\*. the event processor and the event server run on the same machine. 1–8 User Guide . Typically.System Components Example Scenario on Windows The following example scenario and the numbered explanations illustrate the interactions between the event server.*' • Completes execution and exits with status Local Area Network Note: In this illistration. the following Windows command line is to be run on “WorkStation_2.” at the start date and time specified in the job definition: del C:\tmp\*.

As soon as the job ends and the remote agent process sends a completion event to the database. even if the event processor stops running. 3. status. Only two processes need to be running: the event processor and the event server. Then the event processor reads the appropriate job definition from the database and.* 2. For this to happen. From the event server. When these two components are running. The command completes and exits. the event processor reads a new event. which is a start job event with a start time condition that has been met. determines what action to take. Unicenter AutoSys JM is fully operational. The remote agent performs resource checks. the job will run to completion. If the database is unavailable for any reason. based on that definition.System Components Explanation The following numbered steps explain the interactions in the example scenario: 1. The remote agent process is started on a client machine once per job. then “forks” a child process that will actually run the specified command. the connection between the two processes is dropped. the remote agent will go into a wait and resend cycle until it can deliver the message. and so forth) directly to the event server. Note: The remote agent is started on the client machine by the event processor talking to the Remote Agent Service on the client machine. As soon as the remote agent receives the instructions from the event processor. the remote agent exits. 5. After the connection is dropped. In the example. Introduction 1–9 . Remote Agent Service must also be running on the client machine. The remote agent communicates the event (exit code. it runs the following command on “WorkStation_2”: del C:\tmp\*. The event processor communicates with the remote agent on “WorkStation_2”. 4. and the remote agent captures the command’s exit code. such as ensuring that the minimum specified number of processes are available.

which allows you to set configuration parameters. A remote agent must be installed on the server machine and can also be installed on separate physical client machines. both the event processor and the event server reside on the same machine. An instance is defined by the instance ID. and report on jobs.” to associate with jobs within their definitions. Instance An instance is one licensed version of software running as an server with one or more clients. which allows you to set up job environment variables. on a single machine or on multiple machines. In addition. and where jobs are to run. the architecture is composed of the following two types of machines attached to a network: ■ Server Machine The server is the machine on which the event processor or the event server (database) reside. This feature lets you view all jobs that are defined. Unicenter AutoSys JM also provides the Unicenter AutoSys Administrator. ■ Client Machine The client is the machine on which the remote agent software resides. An instance uses its own event server and event processor and operates independently of other instances. 1–10 User Guide . which is a capitalized three-letter identifier defined by the AUTOSERV environment variable.Machines Interface Components To define. For information on interface components and defining and monitoring jobs. whether or not they are currently active. see the chapters in this guide. Machines From a hardware perspective. and the Job Profiles Manager. you can use either the GUI or JIL. In a basic configuration. monitor. or “profiles. the Scheduler Console and its dialogs provide a sophisticated method of monitoring jobs in real time.

jobs can be scheduled to run based on a number of conditions. that job is either started immediately. or user applications. It is important that someone investigate the situation. Multiple instances can run on the same machine. The completion of one job can cause another job to be started. the command line. you may want to have one instance for production and another for development. sent from the Send Event Tool. queued for the next qualified and available machine. and can schedule jobs on the same machines without interfering or affecting the other instances. including the following: ■ ■ ■ Jobs changing states. As each event is processed. but some facility is necessary for addressing incidents that require manual intervention.Events You may want to install multiple instances. and resolve the problem. or if necessary. For example. For example. for a job to be activated by the event processor. and the file is long overdue. Events can come from a number of sources. If the event satisfies another job’s starting condition. a set of jobs could be dependent on the arrival of a file. such as starting. Events sent with the sendevent command. and so forth Internal verification agents. the event processor scans the database for jobs that are dependent on that event in some way. that is. finishing successfully. make a decision. For example. Alarms Alarms are special events that notify operations personnel of situations requiring their attention. Events Unicenter AutoSys JM is completely event-driven. That is. such as detected errors. These are some important aspects of alarms: Introduction 1–11 . jobs progress in a controlled sequence. and in this way. a prerequisite job has completed running successfully or a required file has been received. an event must occur on which the job depends. Alarms are integral to the automated use of Unicenter AutoSys JM.

see the chapters “Scheduler Console. Unicenter AutoSys JM also provides a set of commands that run essential utility programs for defining. or JIL. and report on jobs. running monitors and browsers. the autorep command allows you to generate a variety of reports about job execution. Any action to be taken due to a problem is initiated by a separate action event. ■ ■ Alarms have special monitoring features to ensure they will be noticed. controlling. such as adding a new job definition to the database.” “Managing Alarms. Unicenter AutoSys JM also provides a database maintenance utility that runs daily by default. and reporting on jobs. control. and reports. for defining jobs. and the sendevent command allows you to manually control job processing.” in this guide. 1–12 User Guide . This language is processed by the jil command. For more information about these features. Alarms are sent through the system as an event. and starting and stopping Unicenter AutoSys JM and its components. Utilities To help you define. Alarms are system messages about a detected problem. machines. which reads and interprets the JIL statements that you enter and then performs the appropriate actions. Working through this example will be very helpful for understanding how Unicenter AutoSys JM processes jobs. Additional utility programs are provided to assist you in troubleshooting. Basic Functionality The following figure and the numbered explanations that follow it illustrate how Unicenter AutoSys JM performs its most basic function—starting a job (that is.” and “Monitoring and Reporting on Jobs. monitors.Utilities ■ Alarms are informational only. For example. Unicenter AutoSys JM has its own specification language called Job Information Language. executing a command) on a client machine.

the job definition and attributes are retrieved from the event server. the event processor scans again in 5 seconds. Event Processor 5 Unicenter AutoSys JM Client agent connect 4 7 Remote Agent 9 6 Client Job 8 3 1 2 Event Server (Database) Explanation 1. for jobs running on Windows machines. The event processor scans the event server for the next event to process. The event processor reads from the event server that an event is ready. The event processor processes the event. and passes the job attributes to the client machine. In addition. and other remote agents are installed on separate client machines. the major components are shown as separate entities. If no event is ready. the event processor retrieves from the database the user IDs and passwords required to run the job on the client machine. Introduction 1–13 . The event processor sends a CHANGE_STATUS event marking in the event server that the job is in STARTING state. 2. If the event is a STARTJOB event. the event processor and the event server are installed on the same server machine (along with a required remote agent). If the event is a STARTJOB. including the command and the pointer (full path name on the client machine) to the profile file to be used for the job. Typically.Basic Functionality Note: In the following illistration. 3. the event processor attempts to establish a connection with the remote agent on the client machine.

9. then returns an exit code to the remote agent and quits.Basic Functionality 4. If the return status is SUCCESS. On a UNIX machine. The remote agent sends an acknowledgment back to the event processor indicating that it has received the job parameters. At this point. the inetd invokes the remote agent. The remote agent issues a CHANGE_STATUS event marking in the event server that the job is in RUNNING state. sees the process completion status. the event processor sends a STARTJOB command to the event server. 5. the remote agent deletes the log file in its temporary file directory (usually tmp) on the client machine (if so specified in the configuration file on UNIX or with the Unicenter AutoSys Administrator on Windows). the remote agent logs onto the machine as the user defined as the job’s owner. The remote agent starts a process and executes the command in the job definition. 1–14 User Guide . which it will then process in the next cycle. and evaluates the rest of the dependent jobs’ starting conditions. The remote agent sends the event server a CHANGE_STATUS event corresponding to the completion status of the job and passes back an exit code. using the communications facilities of the database. 8. On a Windows machine. looking for events to process. The client job process runs to completion. For each job found whose remaining conditions are satisfied. 7. determines if there are dependent jobs. The event processor. 6. the event processor resumes scanning the event server database. which is scanning the event server. The socket connection is terminated. using the user IDs and passwords passed to it from the event processor. The remote agent quits.

if the Unicenter AutoSys Agent machine is defined to Unicenter AutoSys JM. Using cross-platform job dependency notation. and you can define Unicenter AutoSys JM Connect jobs to conditionally start based on the status of an job. You can also define jobs that will run on an Unicenter AutoSys Agent machine. Unicenter AutoSys JM Server (UNIX or Windows) UNIX Client UNIX Job Windows Client Remote Agent Event Server (Database) Remote Agent Event Processor Adapter asbIII Application NT Job Other OS (for example: AS/400) CCI CCI Mainframe (OS/390) CCI AutoSys Agent AutoSys Connect AS/400 Job AS/390 Job Introduction 1–15 . you can define jobs to conditionally start based on the status of an Unicenter AutoSys JM Connect job running on a mainframe. and report on the status of jobs related to an application using the sophisticated job scheduling capabilities of Unicenter AutoSys JM. you can install various AutoSys/Adapters. control.Extending Functionality Extending Functionality You can extend jobs with the Unicenter AutoSys JM Connect and Unicenter AutoSys Agent integration components. The application-specific Adapters allow you to initiate. The following illistration shows an extended configuration that includes the Unicenter AutoSys JM Connect and Unicenter AutoSys Agent integration components and an Unicenter AutoSys JM/Adapter installation on a UNIX client. In addition.

ca. You will be directed to an experienced software engineer familiar with Unicenter AutoSys JM.Contacting Technical Support Contacting Technical Support You can contact us with any questions or problems you have. You can contact Computer Associates Technical Support at esupport. 1–16 User Guide .com.

native security is not enforced. or later on by an authorized EXEC superuser. see autosys_secure in the Unicenter AutoSys Job Management for UNIX and Windows Reference Guide.Chapter 2 Security To set up Unicenter AutoSys JM correctly. you must understand how security is implemented on both systems. Security 2–1 . in this chapter. the eTrust security package will be called to authorize the user. External security (eTrust) can be enabled during the installation of the product. For more information on controlling the security setting with the Unicenter AutoSys Secure utility. Overview Unicenter AutoSys JM is able to run in either eTrust™ secured mode or native security mode. see Security Control. If you are installing on both UNIX and Windows. For more information on enabling eTrust security. and to determine if they can turn off security in the product. For information about security on UNIX. Once external security is enabled. you should understand the security features that control where and by whom certain secured activities can be edited or executed. Note: While external security is enabled. see the chapter “Security” in the Unicenter AutoSys Job Management for UNIX User Guide.

Native Security Native Security Unicenter AutoSys JM native security includes the following: ■ ■ ■ ■ Job-level security Superuser privileges System-level security UNIX and Windows file permissions (See Restricting Access to Jobs in this chapter.) Security is initiated when either a user sends events that affect the running of a job or the event processor sends events that affect a job. you can send execute events that affect the running of a job. Security On Events Sent By Users By using the sendevent command or the Send Event dialog. if you have the appropriate permissions: Security Events CHANGE_PRIORITY CHANGE_STATUS DELETEJOB FORCE_STARTJOB JOB_OFF_HOLD JOB_OFF_ICE JOB_ON_HOLD JOB_ON_ICE KILLJOB SEND_SIGNAL STARTJOB 2–2 User Guide . These are the execute events that you can send.

Does the user match the owner as indicated in the job definition? Is the user the exec superuser as defined with autosys_secure? 2. The previous figure shows how Unicenter AutoSys JM checks for the following when a user starts a job by sending an event: 1. Security 2–3 . and the job is not run. the job permissions are checked as shown in the following figure. If so. the job definition is invalid. Checks the database to determine if the job definition was tampered with.Native Security If you start a job by sending an event. 3.

permissions are checked on the remote agent machine on which the job is to run. Security On Events Sent By the Event Processor In addition to sending execute events on jobs. The event processor scans the event server for any jobs with starting conditions that have been met. 7. you can schedule jobs to start at certain times or under certain conditions. When a job is scheduled to start automatically. 5. the event processor sends a STARTJOB event to the designated remote agent machine. Does the machine portion of the user logon match the job owner machine portion? Does the job have machine permission as indicated by the job definition? 6. When the starting conditions for a job are met. Does the user have job execute permissions as indicated in the job definition? Is there a machine name in the owner value of the job definition? The edit superuser can remove this portion of the owner.Native Security 4. 2–4 User Guide .

Native Security The following figure shows the permissions and security checks that occur on a UNIX machine before a job is allowed to start on the machine. Note: In the figure. Security 2–5 . an asterisk indicates checks that are made only if the specific method of remote authentication is enabled (see Remote Agent Authentication in this chapter).

If so. Checks the DES encrypted job definition to determine if the event processor can connect to the remote agent machine. 4. is the user a trusted user (as defined in the /etc/hosts. and the job is not run. Does the user who is defined as the job owner (user@machine) have a logon account on the remote agent machine? If user authentication is enabled. 3. the job definition is invalid. 5. Note: The edit superuser can enable remote authentication by using the autosys_secure utility.rhosts files)? If event processor authentication is enabled. does the requesting event processor have permission to run jobs on this remote agent machine? 2. Checks the database to determine if the job definition was tampered with.equiv and $HOME/.Native Security The previous figure shows how Unicenter AutoSys JM checks for the following when the event processor sends a STARTJOB event to a remote agent machine: 1. 2–6 User Guide .

which in turn prevents unauthorized access to jobs. but also generates a checksum from fields in the job definition. Whenever a job is accessed. In this case. Unicenter AutoSys JM not only encrypts some fields specified in a job definition. If the checksums are different. Security 2–7 . this indicates that someone tampered with the job definition in the database. the owner or the edit superuser must access the definition and re-save it. Job Definition Encryption To secure the remote agent from unauthorized access.System-Level Security System-Level Security The security scheme prevents unauthorized access to facilities. If the remote agent receives any job information from the event processor that it does not recognize. the database field and control string encryption features provide a level of security comparable to the security provided in the native UNIX environment. The following features handle system security: ■ ■ ■ ■ Database field verification Job definition encryption Remote agent authentication User and database administrator passwords Note: On UNIX. probably by using an SQL command. its checksum is regenerated and compared to the one in the database. Database Field Verification To secure the database. To re-enable a disabled job. the job is disabled and cannot be executed. by using either the JIL update_job sub-command or the Job Definition dialog. the event processor encrypts the information in a job definition sent over the socket to the remote agent. and stores the checksum in the database. The remote agent then decrypts the job information and continues to process the job. it issues an error message and will not process the job.

com. To activate this type of remote authentication.” Similarly. The edit superuser must enable them by using the autosys_secure command.” If they do not match. It accomplishes this by telling the client’s remote agent to make the ruserok() UNIX system call to check the client machine’s /etc/hosts.rhosts file must contain “jungle. User Authentication This remote authentication method uses UNIX ruserok() authentication to verify that a user has permission to start a job on an client machine.System-Level Security Remote Agent Authentication Unicenter AutoSys JM provides two remote agent authentication methods: ■ ■ User authentication Event processor authentication By default.rhosts file entries must match the job owner and machine name field exactly.rhosts file must contain “jungle. the hosts. both user authentication and event processor authentication are disabled.com. The hosts. For information on enabling this type of remote authentication.equiv or . This function call performs a “local” verification. if the owner is tarzan@jungle.equiv or . the hosts.equiv and the user’s .equiv or .vine. and it is not related in any way to rshd or rlogind. For example.vine.rhosts file to validate that the requesting user is registered in that environment. see autosys_secure in the chapter “Commands” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. jobs will fail to run on that machine when ruserok() remote authentication is in use. use the autosys_secure command. 2–8 User Guide . if the owner is tarzan@jungle.

autostuff file on every client machine that will participate in this authentication method. as described in Configuring Remote Authentication in the chapter “Configuring. the database system administrator ID is “sa. It does this by reading the /etc/. For example. see xql in the chapter “Commands” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. an “autosys” user is added to the database with a password set to “autosys. and for information on changing the “sa” password and querying the database. when using the xql utility to query the database. see autosys_secure in the chapter “Commands” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide.” in this guide. User and Database Administrator Passwords When you install Unicenter AutoSys JM and configure your database. we recommend that you change the system administrator password by using the xql utility. Note: Before enabling event processor authentication. we recommend that you change the “autosys” user password with the autosys_secure command. You must supply the “autosys” and “sa” user IDs and passwords when you use several utilities. To enhance system security.” The “autosys” user is the owner of the database and can make changes to specific information in the database.autostuff file on the machine on which the remote agent is running. For information on changing the “autosys” user password see autosys_secure. Security 2–9 . you must know both the “autosys” user password and the “sa” system administrator password.System-Level Security Event processor Authentication When event processor authentication is enabled. you must set up and properly configure the /etc/.” and the password is “sysadmin.” To enhance security. When you install with bundled Sybase. the remote agent verifies that it has permission to process requests from the requesting event processor before starting each job. For information on enabling event processor authentication.

For jobs running on Windows. For this process to work. If a job is run on a Windows client machine. the user ID is retrieved from the UNIX environment and attached to the job in the form of user@machine. The owner can extend permissions to other users and other machines. group. the owner of an job is the user who defines that job on a particular machine.Job-Level Security Job-Level Security The security scheme provides individuals and groups of users with edit and execute permissions on a job-by-job basis. and so forth that the command needs to access. the job owner must have the appropriate system permissions. The owner’s umask “write” permission is used as the default “edit” permission of the job. The user@machine combination must have execute permission for any command specified in a job on the machine where the job command is to run. Job Ownership By default. as described in the following sections. By default. the edit superuser must have entered the valid Windows user ID and password for the owner into the database. For more information about the edit superuser. only the owner can edit and execute the job. and the umask “execute” permission is used as the default “execute” permission of the job. 2–10 User Guide . resource. When a user defines a job on UNIX. Unicenter AutoSys JM supports owner and world edit and execute permissions. see Edit Superuser in this chapter. For jobs running on UNIX. and world edit and execute permissions. The job owner must also have permission to access any device. only the user logged on as the owner of a job can edit or execute a job. Unicenter AutoSys JM supports owner. By default. The owner is defined by the owner job attribute.

override. the owner can grant different types of permissions when defining a job. or delete a job definition. see Security On Events Sent By Users in this chapter. Execute Users can send an execute event that affects the running of a job by using the sendevent command or the Send Event dialog. Permission Types By default. Who can execute the UNIX command specified in a job. and all edit and execute permissions are valid only on the machine on which the job was defined. Unicenter AutoSys JM uses the notion of these three types of users for any job: Owner The user who created the job. or delete a job definition. For a list of the execute events that users can send. Similar to UNIX. Unicenter AutoSys JM uses the UNIX user ID (uid) and group ID (gid) of a job’s owner to control the following: ■ ■ Who can edit. Unicenter AutoSys JM associates different types of permissions with each job. Security 2–11 . Every job has the following permission types: Edit Users can edit. override.Job-Level Security User Types Like UNIX. only the owner has edit and execute permissions on a job. The owner of a job can allow other users to edit and execute the job by setting the permissions in the job definition (discussed in the following section). However. World Every user. Group Any user who is in the same primary group as the owner.

the user must be logged onto the machine specified in the owner attribute. can edit the job (otherwise. that is. that is. user@machine). The following table shows the permissions that you can set by using JIL or the Permission toggle buttons on the Job Definitions Advanced Features dialog. user@machine). Users can execute the job if logged onto the machine where the job was created (the machine specified in the owner attribute.Job-Level Security Machine Users logged onto a machine other than the one on which a job was created can edit or execute the job. user@machine). user@machine). regardless of the machine logged onto. Note: In order for a job to run on a machine other than the one on which the job was defined. Users. that is. that is. GUI Group Execute JIL gx Meaning Users assigned to the job owner’s primary group can execute the job if logged onto the machine where the job was created (the machine specified in the owner attribute. Group Edit ge All Hosts Execute m x All Hosts Edit m e World Execute w x 2–12 User Guide . can execute the job (otherwise. that is. regardless of the machine logged onto. user@machine). the owner of that job must have an account on that machine. Granting Permissions The owner of a job cannot override his or her ownership designation. Users. the user must be logged onto the machine specified in the owner attribute. Users assigned to the job owner’s primary group can edit the job if logged onto the machine where the job was created (the machine specified in the owner attribute. only the edit superuser has the authority to change the owner job attribute. However. the owner can grant other users edit and execute permissions for a job by using the GUI or JIL to set the permission job attribute in the job definition.

but not who the job runs as. the user executing the job must be the owner of the job. the user editing the job must be the owner of the job. In this case. the job will still run as the user. but they will be ignored. In this case. Job Permissions and Windows If you are defining jobs and running them on different operating systems. When executing a job from a Windows machine. Execute permissions determine who can execute events against the job. user@machine). You can turn external security on or off by using the autosys_secure binary. ■ ■ Security Control External security is controlled by a setting in the Unicenter AutoSys JM database. keep the following in mind: ■ When defining a job to run on a Windows machine. Security 2–13 . the group execute permission is ignored. Even if World Execute permissions are granted. that is. or World Edit permissions must be specified for the job. When editing a job from a Windows machine. the group edit permission is ignored. you can set group permissions. Note: A job and the command it executes will always run as the user specified in the owner attribute of the job definition. or World Execute permissions must be specified for the job.Job-Level Security GUI World Edit JIL we Meaning Users can edit the job if logged onto the machine where the job was created (the machine specified in the owner attribute. Group permissions will be used if a job is edited or executed on a UNIX machine.

and add and change Windows user IDs and passwords by using the autosys_secure command. change the remote authentication method. For example.Superuser Privileges Superuser Privileges Unicenter AutoSys JM provides you the ability to create more than one EDIT or EXEC Super User. For more information about changing the job owner. For information about defining the edit and exec superusers. Change the database password. 2–14 User Guide . The edit superuser can override user authentication (if enabled) on a job-by-job basis by changing the owner of the job from the form user@machine to the form user. see the chapters “Server Installation for Sybase” or “Server Installation for Oracle” in the Unicenter AutoSys Job Management for UNIX Installation Guide. Edit Superuser Only the edit superuser has permission to: ■ ■ ■ Edit or delete any job regardless of its owner or its permissions. Note: The purpose of the user@machine form is to prevent users from running jobs on machines where they do not have the appropriate permission. User authentication of the job at execution time is not performed on the client machine. Change the owner attribute of a job. You can define these superusers by using the autosys_secure command. see owner attribute in the chapter “JIL/GUI Job Definitions” in the Unicenter AutoSys Job Management Reference Guide. root@machine prevents root on any machine from running root jobs on all machines.

either using the sendevent command or the Send Event dialog. These user IDs and passwords are required to log onto and run jobs on Windows client machines. For information about entering and changing Windows user IDs and passwords. Exec Superuser Only the exec superuser has permission to: ■ Issue commands that affect the running or the state of any job.Superuser Privileges The edit superuser must enter valid Windows user IDs and passwords into the database. see autosys_secure in the chapter “Commands” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. it logs on as the user defined in the owner attribute for the job. the event processor retrieves encrypted versions of the IDs and passwords for the user@host_or_domain and the user@machine from the event server and passes them to the remote agent. When a remote agent runs a job on a machine. Note: Any user who knows an existing user ID and password can change that password or delete that user and password. Security 2–15 . To do this. Enable eTrust Access Control Set the Subscriber Authentication Security Word Stop the event processor by issuing the following command: sendevent -E STOP_DEMON ■ ■ ■ Note: Exec superuser privileges are usually granted to the night operator.

and change calendars. edit jobs. Then. you must ensure that only authorized users can change permissions on the files and directories in the directory structure. This allows users to use the GUI to view job states. you can change permissions on many files to control which users can view jobs. First. execute jobs. Any user can view jobs and reports about jobs. 2–16 User Guide . This will also prevent unauthorized users from making changes to the configuration. Secure the following files: File Names archive_events autocal autocal_asc autocons* autotimezone clean_files DBMaint dbspace dbstatistics Hostscape* jil jobscape* sendevent timescape* xql zappls zql Note: An asterisk (*) indicates files that can be executable by all users as long as sendevent and jil are not executable. If you want all users to view reports about jobs. If you want only authorized users to access Unicenter AutoSys JM. but only authorized users to create and edit jobs and calendars. for example: ■ ■ Only authorized users can use Unicenter AutoSys JM. but does not allow them to add new jobs or calendars or start jobs (even if the job has world execute permissions). such as using autorep to see the status of a job. but only authorized users can create jobs and calendars or make changes to them.Restricting Access to Jobs Restricting Access to Jobs Using the UNIX chmod command. ensure that the following files in the %AUTOSYS%/bin directory are executable only by the authorized users. you should determine what level of security you want. ensure that only those users have execute permissions on the files in the bin directory.

All GUI applications and all Command Line Interfaces will have call outs to security. This is accomplished through integration with eTrust Access Control (eTrust AC). eTrust Access Control Unicenter AutoSys JM provides you with Asset Level Security. This database will subscribe to the machine where the eTrust PMDB was created to ensure that security policies are pushed out to each machine. If you turn on eTrust AC security. Security 2–17 . policy changes will not affect resources which were entered into the database. Since the event processor and remote agent will not enforce security. Note: Wherever Unicenter AutoSys JM binaries are installed. you can specify a list of users whose jobs are prohibited from running on that machine. a local eTrust database will be created called seosdb. if selected during installation. For example. Remote Agent Security In the auto. For information on this. Any security calls made by these binaries will go against the local seosdb.profile file for the remote agent machine. Read permission is necessary to source the environment files. the job-level security and superuser security supported in native mode will no longer be adhered to. rather than a remote security database. User defined classes within eTrust AC will be used to govern what types of resources can be controlled by which users.” in this guide. if the security administrator withdraws a users permission to create jobs. to avoid unnecessary network traffic.eTrust Access Control You should also protect the files in the %AUTOUSER% directory from modification by ensuring that only users authorized to change the configuration have write permission on the files. Unicenter AutoSys JM will continue to run jobs created by the user before the change. see Client-Side Security in the chapter “Configuring.

The only time you will ever be prompted for this word again is if you decide to change your security word. You will be prompted for your security word. Before establishing your security word is a good opportunity to define your enterprise security policy since Unicenter AutoSys JM is effectively locked down until you establish the security word. Before checking security. When you are ready to establish your security word. With that information it would be possible for a malicious user to setup a local eTrust policy and circumvent Unicenter AutoSys JM security. It will only be present in eTrust if the local installation is a valid subscriber to the enterprise security policy. Note: To provide cross-platform compatibility. If you have reason to believe that your security word has been compromised. you can do one of two things. ■ You can create a filter that will not include these entries. access to secured assets will be denied. you could successfully enter 'My_Word' or 'my_WORD'. If there are problems verifying the security word. all secured Unicenter AutoSys JM executables will read the security word from the Unicenter AutoSys JM database and compare it to the security word in the eTrust database. For more information see the section Audit Filters in the eTrust Access Control Administrator Guide. This renders the security word case-insensitive. you should change it using autosys_secure. 2–18 User Guide . when you are prompted for the existing security word.eTrust Access Control If eTrust security is enabled. and Unicenter AutoSys JM will see them as the same. Note: The eTrust AC audit log may have failed to check the security word resource each time you run a secured binary. if you create the security word 'my_word' and then decide to change it. The security word you provide is stored in the Unicenter AutoSys JM database and the eTrust database. This is expected behavior. Choose menu item 7 followed by item 2. For example. the security word is stored in the eTrust database and the Unicenter AutoSys JM database in upper case. you must establish a subscriber authentication security word before any secured executables will work properly. If you would rather not see these failures. run autosys_secure as a user and from a host that are authorized to administer the eTrust pmdb.

you must be granted execute access to the SECADM resource. Enter the hostname where the autosys PMDB was installed. Start. However.eTrust Access Control ■ You can change your user resources so that these failures will not be logged. Check the Connect to PMDB check-box and enter autosys as the PMDB name. Connect Click Add (Insert) in the Host Selection dialog. Policy Manager. To modify security do the following: 1. eTrust. 5. You can change the audit rules using either selang or the Policy Manager GUI. Security Access The Policy Manager is used to modify security. You can globally enable or disable eTrust using autosys_secure. the security word resource has been created to not cause log entries to be generated on failure (since that is expected behavior in this case). You can also modify security access using the selang command line utility. 3. Click. Programs. Policy Manager All modifications to security access of any Unicenter AutoSys resource can easily be done through the eTrust Policy Manager on Windows. 4. all users are configured to cause log entries to be generated on access failures (regardless of which resource the failure occurred with). By default. see the eTrust Access Control for UNIX Reference Guide. This leaves it up to the individual resources to create failure entries in the audit log (the default behavior for resources). For more information on configuring audit rules see the eTrust Access Control Administrator Guide. In order to disable eTrust. Select File. For more information on selang. The eTrust Policy Manager opens 2. Security 2–19 . You can change (or create) your users to not create an audit log entry when a failure occurs. Computer Associates. Access Control. The eTrust Policy Manager allows you to modify and set security levels for all user-defined classes provided by Unicenter AutoSys JM.

click Resources in the left program bar Access Control. Controlling the Event Processor If eTrust security has been enabled through autosys_secure. 8. To view Unicenter AutoSys JM security classes. if control of the Event Processor Service through the Service Control Manager is desired. or the Administrator tool to stop the event demon.eTrust Access Control A new entry appears in the Host Selection dialog 6. Select the new entry. Disable Security To access Disable Security use the autosys_secure command. The sendevent command or the Administrator Tool should be used to shutdown the event demon. For more information about autosys_secure. then the service must be configured to log on as a certain user. Alternatively. Selecting a class will list the available policies governing access to a specific resource. the user will be prevented from using the Windows Service Control Manager to stop the Event Processor Service by default. an eTrust security call will be issued to see if the user in question has been given as-control/STOP_DEMON execute rights to shut down the Event Processor Service. and click OK. 2–20 User Guide . Access to shutting down the event demon can be restricted through the eTrust Policy Manager by setting access to the STOP_DEMON resource in the as-control class. Once connected. see the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. The user must use the AutoSys Administrator tool or the “sendevent –e STOP_DEMON” command to stop the Event Processor Service. expand the User-Defined classes folder. 7. Doing this will prevent users from using the sendevent command. In all cases.

on what will be considered the master security server. Security 2–21 . For example. For more information on eTrust Access Control see the eTrust Access Control for UNIX User guide. Once security is enabled. you must be vigilant as to how resources are added to an eTrust Access Control database. On the master security server. All Unicenter AutoSys JM GUI applications and Command Line Interfaces will call out to the security engine bundled with the installation program if eTrust AC is currently enabled. or later on by an authorized EXEC super user. The install will ask for the users that will be defined as administrators to the eTrust database. Since the event processor and remote agent will not enforce security. if the security administrator withdraws a user’s permission to create jobs. it is easy to enter a name with the wrong case which will then not be correctly recognized.eTrust Access Control Asset-Level Security If selected during installation. Windows) and using eTrust AC security only. Important! When working in a mixed environment (UNIX. Since UNIX is case-sensitive and Windows is case-preserving. During the installation of eTrust AC.2. External security can be enabled during the installation of the product. Unicenter AutoSys JM will continue to run jobs the user created before the change. User defined classes within eTrust will be used to govern what types of resources can be controlled by which users. eTrust AC will subscribe a client subscriber to the autosys PMDB. the external security package will be called to authorize the user to determine if they can turn off security in the product. but will not import existing OS users into the eTrust AC database. policy changes will not affect resources which were entered into the database under the previous policy. Unicenter AutoSys JM will be able to run in either eTrust secured mode or regular mode. Unicenter AutoSys JM provides you asset-level security through integration with eTrust AC release 5. a Local Policy Model Database (PMDB) was created called autosys.

For more information on enabling security see Security control. eTrust Resource Classes To secure the product. There are also classes to prevent unauthorized users from starting or shutting down Unicenter AutoSys JM. and to prevent unauthorized users from accessing Unicenter AutoSys JM Web Interface. If you create the user as 'administrator' (lowercase 'a') and then try to run the policy manager from a Windows box where you are logged in as 'Administrator' you will be denied access. Note: The security administrator must use the object. These classes are used to control access to jobs. The classes are eTrust enabled and will make security call outs prior to performing an action on a specified object. you might want to create a user 'Administrator' that you will allow to administer the 'autosys' PMDB from a Windows machine. and the owner field of a job. instance convention when creating policies. Unicenter AutoSys JM will use the following eTrust User Defined Classes. machines. For example. a set of classes will be defined that pertain to Unicenter AutoSys JM. disabling security.ACE when a user tries to update job payroll in instance ACE. calendars. This can be confusing because Windows will let you login to the 'Administrator' account as 'administrator'. cycles. a period. in this chapter.eTrust Access Control For example. as-job as-gvar as-view as-calendar as-owner as-list as-machine as-control The name of each eTrust resource will be the name of the corresponding AutoSys object. 2–22 User Guide . global variables. and the name of the instance. The key is that the user in the PMDB must follow the case as it is preserved on the Windows machine. Unicenter AutoSys JM will query eTrust about as-job payroll. You may use wild cards to create policies which apply to multiple objects among different instances. These classes will be created in the eTrust database and the PMDB autosys.

exe jobdef. eTrust Access Modes Unicenter AutoSys JM will utilize the following access modes on each of the various resource classes. ■ ■ ■ ■ ■ READ CREATE DELETE EXECUTE WRITE as-job Class The as-job class will control access to job objects. READ Prevents users from being able to view jobs or their contents. All of the eTrust access modes will be applied to this object. -q If as-list\AUTOSTAT denied.exe autostatus. The use of these access modes is explained in more detail with the description of each class.exe autorep.exe jobdetails. otherwise -J job. change tabs If as-list\JOBDEP denied.exe eventreport. otherwise –J job -J job Launch from autocons Launch form autocons If as-list\JOBDEF denied. otherwise –J job autostatad.exe Security Checkpoints If as-list\AUTOCONS denied If as-list\AUTOREP denied. see the eTrust Access Control for UNIX Reference Guide.exe job_depends Security 2–23 . Binary autocons.eTrust Access Control For more information on Resource Classes. otherwise file-open.

delete -e DELETEJOB EXECUTE Controls whether a user is allowed to issue a sendevent against the job object.save DELETE Prevents users from deleting jobs. Binary sendevent Security Checkpoints -e STARTJOB -e KILLJOB -e FORCE_STARTJOB -e JOB_ON_ICE -e JOB_OFF_ICE -e JOB_ON_HOLD -e JOB_OFF_HOLD -e COMMENT (not global) WRITE Prevents unauthorized users from updating an existing job object.exe sendevent Security Checkpoints insert_job File .exe jobdef.eTrust Access Control Binary monbro. Binary jil.save as -e CHANGE_PRIORITY 2–24 User Guide .exe jobdef.exe jobdef.exe sendevent. Binary jil.exe Security Checkpoints delete_job File .exe Security Checkpoints update_job File . including deleting the job using the sendevent command. Binary jil.exe Security Checkpoints If as-list\MONBRO denied CREATE Prevents users from creating a job object.

open PRINT autocal_asc.exe Security Checkpoints If as-list\AUTOCAL denied. READ Prevents users from being able to view calendars or their contents.exe Security Checkpoints File – save as ADD (existing) Security 2–25 . Binary autocal. Binary autocal.exe autocal_asc. Binary autocal.exe autocal_asc. Binary autocal.eTrust Access Control as-calendar Class The as-calendar class will control access to calendar objects.save ADD (new) DELETE Prevents users from deleting a calendar.exe Security Checkpoints File – delete DELETE EXECUTE Controls whether a user is allowed to specify the given calendar to run or to exclude within a job object. otherwise File.exe autocal_asc.exe Security Checkpoints run_calendar.exe Security Checkpoints File . Binary jil. exclude_calendar WRITE Prevents unauthorized users from updating existing calendar objects.exe CREATE Prevents users from creating a calendar object.

Binary jil.eTrust Access Control as-machine Class The as-machine class will control access to machine objects. READ Prevents users from being able to view machines or their contents.exe Security Checkpoints delete_machine 2–26 User Guide . change tabs jobdef. otherwise –m machine File – open.exe CREATE Prevents users from creating machine objects.exe Security Checkpoints insert_machine DELETE Prevents users from deleting machine objects. Binary jil. This will control who can do what to the machine object including whether or not it can be used by a user in a job definition.exe Security Checkpoints If as-list\AUTOREP denied. Binary autorep. All of the eTrust access modes will be applied to this object.

Binary jil. Security 2–27 .exe jobdef.eTrust Access Control EXECUTE Unless authorized.exe sendevent Security Checkpoints machine File – save as -e STARTJOB -e KILLJOB -e FORCE_STARTJOB -e JOB_ON_ICE -e JOB_OFF_ICE -e JOB_ON_HOLD -e JOB_OFF_HOLD -e COMMENT (not global) WRITE Prevents unauthorized users from updating existing machine objects. EXEC controls whether a user is allowed to specify that machine inside a job object.

Binary sendevent. Binary sendevent Security Checkpoints -g (existing variable) 2–28 User Guide .exe autostatus. Binary sendevent Security Checkpoints -g variable=DELETE EXECUTE Prevents users from using sendevent all together against global variables. All of the eTrust access modes will be applied to this object. the access modes will be checked during sendevent execution.eTrust Access Control as-gvar Class The as-gvar class will control access to global variable objects. Since this object is only controlled through the sendevent binary.exe Security Checkpoints -g (new variable) DELETE Prevents users from deleting specific global variable objects. Binary sendevent Security Checkpoints -e SET_GLOBAL. READ Prevents users from being able to view specific global variable objects. Binary autorep. all-g options WRITE Prevents unauthorized users from updating an existing specific global variable objects.exe Security Checkpoints -g variable -g variable CREATE Prevents users from creating specific global variable objects.

EXECUTE Prevents users from using unauthorized user-id’s.exe Security Checkpoints owner File – save as Security 2–29 .exe jobdef. For example. when a new job is created.eTrust Access Control as-owner Class The as-owner class will control access to the job owner field in the job object. Binary jil. However. when a different user is to be used. This will be used to control what owner can be specified in a job definition. by default the user-id of the job creator is automatically used. security will be called to determine if the owner specified is allowed to be used by the current user.

Security Checkpoints Services screen. WEBLOG For Internal Use only.exe SECADM For Internal Use only.exe Security Checkpoints -e STOP_DEMON STOP_DEMON Controls who can stop the event processor. Event Processor. EXECUTE Control critical resources through the following: Binary sendevent. Applies to both the sendevent command. and the service control manager on Windows. Note: If eTrust security has been enabled then by default.eTrust Access Control as-control Class The as-control class will control access to critical services within Unicenter AutoSys JM. Stop Button Service Control Manager Stop 2–30 User Guide . Binary autosysadmin. the user will be prevented from stopping the event processor from the Service Control Manager and can only use sendevent. WEBADM For Internal Use only.exe eventsysd.

eTrust Access Control as-view Class The as-view class will control access to the various views defined in the Unicenter AutoSys JM Web Interface GUIs. In an environment where there are thousands of jobs. Security 2–31 . DELETE Prevents users from deleting views defined and maintained by Unicenter AutoSys JM Web Interface. issuing a security call against each individual job. it is not feasible to call security for each individual object that is to be displayed on the web browser. where the information displayed does not constitute a security violation. CREATE Prevents users from creating views defined and maintained by Unicenter AutoSys JM Web Interface. as in autocons or autorep. may cause unnecessary security overhead. preventing access to jobs they are not authorized to see. Notes: By using the default of this class Unicenter AutoSys JM will not incur the tremendous overhead of issuing a security call for each individual line item displayed. just to see status type or summary. WRITE Prevents unauthorized users from updating views defined and maintained by Unicenter AutoSys JM Web Interface. READ Prevents users from being able to bring up a particular view. including preventing graphical representations of certain jobs. Note: For performance reasons. as-list Class The as-list class will control telling programs to bypass security for read only operation. This class is provided for those users that do not believe that status or report type functions that do not display the detail of the asset warrant a security call on each object.

exe Security Checkpoints -m ALL -J ALL -J box -g ALL AUTOCONS Controls read access to the console type programs including the Unicenter AutoSys JM Web Interface GUI.exe Security Checkpoints on refresh.exe Security Checkpoints -J % MONBRO Controls read access to the monitor/browser GUI. Binary autocal. Binary autorep. Binary autocons. This value will ignored for any autorep report that specifies the –q option.exe Security Checkpoints File – open search File – delete search cal dropdown listbox AUTOSTAT Controls read access to ???? Binary autostatad. Binary Security Checkpoints 2–32 User Guide . select filter from dropdown list AUTOCAL Controls read access within the Calendar Definition GUI. JOBDEP Controls read access to the job_depends GUI.eTrust Access Control READ Control security bypass through the following: AUTOREP Controls read access for the autorep program.

Before re-launching autocons. -d] % [-t. All access has been disabled for these jobs. read access to the job ‘goodtest’ will be disabled. then the individual read access checks for each job is ignored and the entire list of jobs is displayed.exe Security Checkpoints -c –J ALL -c –J % [-t. -d] box File – open search File – delete . Since read access was denied for all jobs beginning with good. autocons will update the display accordingly during the refresh cycle. Now when autocons starts up. From the Policy Manager a resource has now been created for any job beginning with good. and a read access check will be performed for each job before displaying it.eTrust Access Control Binary jobdep.exe Security Enabled Applications Example 1 If read access to the autocons resource belonging to the as-list class has been granted to the Unicenter AutoSys JM instance. This is necessary as all security checks will automatically pass if called by the owner. Security 2–33 . and select AUTOCONS*. Note: The resource that Unicenter AutoSys JM used to check for read access is AUTOCONS. open the eTrust Policy Manager to the as-list class. As eTrust access rights are changed.INSTANCE. To disable list access for autocons.search jobdef. -d] ALL [-t. Note: The owner of the AUTOCONS* resource has been set to nobody. a warning message will be displayed indicating that as-list access failed. the job goodtest no longer appears in the display list.

4. Call security to validate user has authority to assign the object in the specified security group by calling security with execute permission on the security group. For Job objects only — call security again and validate the owner field using an asset of as-owner and a permission of execute. First list access will be checked for the AUTOREP resource in the as-list class. Call security to validate user can create the object by passing in the security group name and specifying create authority. Notes: If a job in a box fails read access. 2. 2–34 User Guide . 3. If access is granted the requested jobs will be reported without performing read access checks. then read access checks will be performed for each job before displaying job information. For Job only — call security passing in the security group of the machine with an execute permission if that machine can be used. If a box job fails read access none of the jobs within the box. the failed job will not be displayed. if list access has been denied. Security Call Logic This section walks through the logical flow of creating. Creating an Object The following represents a logical flow for the creation of any object: 1. and the box will not be displayed.eTrust Access Control Example 2 A similar behavior is exhibited when running autorep from the command prompt. but the box passes read access. However. and deleting an object. updating.

For Jobs only — Call security on the owner field and machine field as if on a create object. Call security to validate user has authority to update objects in the security group using the original security group of the object. call security to ensure that the user has update authority to objects in the security group. If the security group is being modified. Call security to validate user authority to delete objects from the specified security group. Deleting an Object The following represents a logical flow for deleting any object. 2. Security 2–35 .eTrust Access Control Updating an Object The following represents a logical flow for updating any object: 1. 3.

.

Browsers (Reports). such as Monitors. you will also refine your use of Unicenter AutoSys JM. As you become more familiar with both the features of and the characteristics of your own jobs. A job is the basic building block upon which the entire operations cycle is built. or Windows batch file.Chapter 3 Jobs All activity controlled by Unicenter AutoSys JM is based on jobs.” for details on starting the event processor. Note: Before continuing with this chapter. UNIX shell script. and the Operator Console. serve to track job progress. It is likely that the way you utilize Unicenter AutoSys JM to address your distributed computing needs will evolve over time. As with most control systems. including the conditions specifying when and where a job should be run. there are many ways to correctly define and implement jobs. which must be running before you start any processes. Other objects. Each job definition contains a variety of qualifying attributes. A job is any single command or executable. Jobs 3–1 . read the chapter “Maintaining .

and Unicenter AutoSys JM treats them all similarly.Job Types and Structure Job Types and Structure The following illistration shows the structure of a job. box jobs are containers. the job is in). and box. the attributes listed inside the Job region comprise what is called the basic job information and are common to all jobs regardless of type. any specified alarms. Basic Job Information In the previous figure. if any. command jobs execute commands. and file watcher jobs watch for the arrival of a specified file. These attributes include the identifier name. These job types have a majority of job attributes in common. There are three types of jobs: command. Job Definition Basic Job Information Current State Name Starting Conditions Alarm Restart Conditions Depends On Current Status Start time End Time Exit code Job Types File Watcher Command Command to execute File to source Machine to run on Standard output files Standard input file File Name Minimum File size Watch Interval Box Container Watch for File Action Run Command on Machine As their names imply. which hold other jobs (including other boxes). file watcher. the restart conditions. the starting conditions. and a variety of other settings not shown (such as the box. 3–2 User Guide . The primary differences between them are the actions that are taken when the job is run.

a file transfer. and so forth. Jobs 3–3 . A box job can be used to organize and control process flow. an executable program.Job Types and Structure Notice that a job’s starting conditions can be contingent on the date. you can specify a script to be sourced before the execution of the command that defines the environment in which the command is to be run.” The command can be a shell script. although it can trigger other jobs to run. ■ Profile Script For each job. you can specify the standard input. When this type of job is run. The exit event (either SUCCESS or FAILURE) and the exit code value are stored in the database. When this is done. Therefore. standard output. The box itself performs no actions. Unicenter AutoSys JM runs this command and captures its exit code upon completion. a command job has the following supporting features: ■ Resource Criteria Unicenter AutoSys JM will check that a certain amount of free file space is available before starting a process. Command Jobs The command job is commonly thought of (and referred to) as “a job. ■ I/O Standard Files For each job. the box job (or box) is a container of other jobs. or use the Job Definition Advanced Features dialog. use the JIL std_* commands. If it is not available. time. and the status of any other job. To do this. and standard error files. an alarm is sent and the job is rescheduled to start after a suitable delay. all statements in the profile must use /bin/sh syntax. the result is the execution of a specified command on a client machine. Box Jobs In the environment. In addition to the primary functionality described previously. An important feature of this type of job is that boxes can be put inside of other boxes. When all the starting conditions are met. All commands are run under the Bourne shell (/bin/sh). jobs related by like starting conditions (not by similar application types) can be grouped and operated on in a logical way.

another future start job is issued for 15 minutes past the hour. the job runs at 15 minutes past the hour. Starting Conditions for Box Jobs If no other starting conditions are specified at the job level. In addition to explicit starting conditions. the box completes. if a job inside a box starts and the box job is stopped. and the cycle repeats itself. However. Note: Some caution must be exercised when placing a job with more than one time-related starting condition in a box. Unicenter AutoSys JM starts a job if the current time matches. jobs inside of boxes have the following implicit condition: the box job itself is running. At that time. only the first start time will be used. For example. a job that runs at 15 and 45 minutes past the hour is placed in a box that runs every hour. Jobs inside of boxes will be run only once per box execution. by which time the box has completed. and administering large numbers of jobs that have similar starting conditions or have complex logic flows. or is later than. they will all run in parallel. This prevents jobs in boxes from inadvertently running multiple times. the job will not run until the box is running again at the top of the next hour. a job within a box will run as soon as the starting conditions for the box are satisfied. highest to lowest. As a result. If several jobs in a box do not have job-level starting conditions. the other jobs are checked to see if they are eligible to start running. the job runs as soon as the box starts because it is past the start time. Knowing how and when to use boxes is often the result of some experimentation. This means that jobs inside of a box will start only if the box job itself is running. they will be processed in order of priority. managing. 3–4 User Guide . If you do specify multiple start times for a job during one box processing cycle. If jobs in a box have a priority attribute setting. the start time. The job runs.Job Types and Structure Note: Box jobs are very powerful tools for organizing. the started job runs to completion. The first time the box starts. Each time any job in a box changes state. A future start is then issued for 45 minutes past the hour.

Jobs 3–5 . a batch job is to be run to process it. and it is expected to arrive after 2:00 a. indicating that the file has arrived. it starts a process that monitors for the existence and size of a specific operating system file. After it arrives. For example. possibly even starting a whole sequence of jobs. a file needs to be downloaded from a mainframe.Job Types and Structure File Watcher Jobs A file watcher job is similar to a command job. You could set up a file watcher job to start at 2:00 a.m. You could also set up the batch job so that the completion of the file watcher job is its only starting condition. Using file watcher jobs provides a means of integrating events that are external to Unicenter AutoSys JM into the processing conditions of jobs. the file watcher job completes successfully. instead of starting a user-specified command on a client machine. and then exit. However. wait for the arrival of the specified file.m. and is no longer growing in size. When that file reaches a certain minimum size.

After setting the environment variables. you must define all of the environment variables needed to run a job in its assigned profile. the remote agent searches for the assigned profile. By default. the remote agent searches for the profile on the machine on which the command is to run. or to multiple jobs. and the environment variables are set before the profile variables. However. Since only one profile is sourced before a command job is run. and then it sets the specified job profile variables. However. Therefore. You must define your own DEFAULT profile using the Job Profiles Manager. A job profile defines the appropriate non-system environment variables for the job. when assigning the job profile. you can reference system environment variables in job profiles. If you do not assign a profile job attribute in the job definition. the last one read is the one used. The remote agent on a machine first sets the environment variables for the job’s execution. you cannot assign a profile that is defined in one instance to a job that is defined in another. While AutoSys supplies a DEFAULT job profile.Job Profiles Job Profiles Before running a command job. Only one job profile can be sourced for a job. which allows you to run the job on one machine while using a job profile defined on another machine. you can specify both the machine name and profile name. the remote agent sets the assigned Job Profile on the job’s target machine. 3–6 User Guide . if a variable is set more than once. you can assign that profile to a job. using the profile attribute or the Job Environment Profile field (in the Job Editor Resource/Profile tab). These profiles are however instance-specific. it does not define any environment variables in it. Then. You can use the Job Profiles Manager to define a profile that contains the environment variables that must be set for a specific job to run. the remote agent uses the DEFAULT job profile.

either in the DEFAULT (which on Windows is initially empty) or in a user-defined job profile. in which case. Therefore. variables set from the job profile can be used in the path name specification. if “Path” is a variable in the specified profile. the environment variables in a profile are expanded. when the remote agent reads the profile. Note: Although environment variables will be set automatically in the command’s environment. Jobs 3–7 . the variables must be defined so that they are in the appropriate order when read alphabetically. if you plan on expanding variables within the profile itself. Unicenter AutoSys JM will expand any environment variables specified as the value of Path. All other required environment variables must be defined in the job’s profile. and set the new value for the %Path% variable before executing the command.” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. user environment variables will not be set. For more information about the profile attribute. use this path to search for the command. see profile in the chapter “JIL/GUI Job Definitions. For example. You can specify the full path name. Note however that the profile variables are read in alphabetical order.Job Profiles In addition.

delete. To define a new profile. Therefore. Note: Profiles are instance-specific. To view all existing profiles on this current host. and if you have “Administrator” group privileges and Registry edit privileges. if you have installed multiple instances. delete. do the following: Open the AutoSys Instance Job Profile Management icon from the program group. At the top of the Job Profiles Manager is the Host Name field. type in a new name into this field. you can create. and edit job profiles. The Profiles Manager appears.Job Profiles Using the Job Profiles Manager The Job Profiles manager allows you to create. 3–8 User Guide . To display the Job Profiles manager. You can also connect to any host machine and view the profiles defined there. The Profile Name field lets you specify a profile. By default. and edit the profiles on the specified host machine. click the down arrow to the right of this field. make sure that you launch the Job Profiles Manager for the appropriate instance. the Job Profiles Manager uses the machine that you are logged on to as the Host Name.

the new or changed variable appears in the Environment Variable display area. Repeat these steps for additional variable definitions. 6. its current settings appear in the Environment Variables display area. Jobs 3–9 . you can make the following changes to the settings in these fields. by the following: 1. 3. and it will be placed in the Variable and Value fields at the bottom of the Profiles Manager. 5. Note: When adding new profiles.” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. Note: The capitalization of the variable definitions does not matter on Windows. you can double-click on a variable setting. Click Set to enter the variable definition. by selecting the new profile in the Profile Name field. the capitalization that you enter in the Variable and Value fields. Then. In the Variable field. To accept the new or changed definitions. click OK in the upper-right corner of the Job Profiles Manager. enter a variable name. When you do this. you must either define the profile on the machine where the command will run or specify the computer name (on which the profile is defined) with the profile name when you are defining the Job Environment Profile or the profile attribute. Tab to or click the mouse button in the Value field and enter a value for the variable. For more information about specifying the profile attribute. 2. If you do not use one of these approaches. However. the Job Profiles Manager does replicate. see profile in the chapter “JIL/GUI Job Definitions. This writes the definitions to the specified Profile Name and exits the manager. you will get a “Profile not found” error when starting the job. Edit or create a variable definition. You can enter a new variable or an existing one. 4. To cancel the changes.Job Profiles When you select a profile. You cannot edit a variable directly in this display area. click Cancel in the upper-right corner of the Job Profiles Manager. This action exits the Job Profiles Manager without updating the current profile. However. in the Job Profile itself. Note: Variable settings are also saved when you change to a new profile.

In the confirmation dialog. Delete a Profile: 1. or click Cancel to cancel the deletion. you can delete the variables in the DEFAULT profile. 2. 3–10 User Guide . However. and no confirmation is required. Note: You cannot delete the DEFAULT profile. Double-click on a variable from the Environment Variables display area. 2. Click Delete Profile. This action immediately deletes the variable from the profile. 3.Job Profiles Delete a variable definition: 1. This action brings up a confirmation dialog box. Click Delete. Select the profile in the Profile Name field. click OK to delete the profile.

Starting Conditions The date/time or job dependency conditions necessary for the job to be run. such as in cases where a job will always be started manually. some job attributes are required. Command Job Attributes The basic command job definition has the following required attributes: Job Name The unique job identifier by which a job is referenced. Machine Name The name of the machine on which the command is to be run. Starting Conditions The date/time or job status conditions necessary for the job to be run. such as in cases where a job will always be started manually. Note: The owner attribute is required for all job types. Machine Name The name of the machine on which the command is to be run.) Jobs 3–11 . There are additional optional attributes that you can use for more advanced job definitions. or application program to be executed. Command The UNIX shell script. File Name to Watch For The name of the file for which to watch. (Strictly speaking.) File Watcher Job Attributes The basic file watcher job definition has the following required attributes: Job Name The unique job identifier by which a job is referenced. but is automatically assigned. command. (Strictly speaking. this is not required.Basic Job Attributes Basic Job Attributes For each of the three job types. this is not required.

this is not required.) 3–12 User Guide . This name is used by other jobs as the name of their parent box.Basic Job Attributes Box Job Attributes The basic box job definition has the following required attributes: Box Name The unique job identifier by which the box is referenced. Starting Conditions The date/time or job status conditions necessary for the job to be run. (Strictly speaking. such as in cases where a job will always be started manually.

The value of a job’s status is used to determine when to start other jobs that are dependent on the job. ■ STARTING The event processor has initiated the start job procedure with the remote agent. ■ SUCCESS The job exited with an exit code equal to or less than the “maximum exit code for success. The job status is displayed in the job report generated by the autorep command. If the job is a box job. A job can have one of the following statuses: ■ INACTIVE The job has not yet been processed. ■ RUNNING The job is running. and in the job report you can view in the Job Activity Console. this value simply means that the jobs within the box might be started (other conditions permitting).” By default. If it is a command or file watcher job. or the “Exit Condition for Box Success” evaluated to true. or status. a range of values up to the “maximum exit code for success” can be reserved for each job to be interpreted as success. of every job. If the job is a box job.Job States and Status Job States and Status Unicenter AutoSys JM keeps track of the current state. (These exit conditions are discussed further in later sections. but the job itself has not started yet. this value means that all the jobs within the box have finished with the status SUCCESS (the default). Either the job has never been run.) Jobs 3–13 . only the exit code “0” is interpreted as “success. the value means that the process is actually running on the remote machine.” However. or its status was intentionally altered to “turn off” its previous completion status. ■ ACTIVATED The top-level box that this job is in is now in the RUNNING state.

3–14 User Guide . or that the “Exit Condition for Box Failure” evaluated to true. ■ ON_HOLD This job is on hold and will not be run until it receives the JOB_OFF_HOLD event. ■ TERMINATED The job terminated while in the RUNNING state. it has a FAILURE status. A job might also be terminated if it has exceeded the maximum run time (term_run_time attribute. If the job itself fails. any number greater than zero is interpreted as “failure. A job can be terminated if a user sends a KILLJOB event or if it was defined to terminate if the box it is in failed. not a TERMINATED status. ■ RESTART The job was unable to start due to hardware or application problems. and has been scheduled to restart.” If the job is a box job. all the starting conditions have been met). if one was specified for the job). but there are not enough machine resources available.” By default. Unicenter AutoSys JM issues an alarm if a job is terminated. or if it was killed from the command line through a UNIX kill command.Job States and Status ■ FAILURE The job exited with an exit code greater than the “maximum exit code for success. AutoSys issues an alarm if a job fails. ■ QUE_WAIT The job can logically run (that is. a FAILURE status means either that at least one job within the box exited with the status FAILURE (the default).

” in this guide. the event processor log will contain the following entry: EVENT: CHANGE_STATUS STATUS: RUNNING JOB: test_job Note: In the following diagrams. all dependent jobs do not run when a job is on “on hold”—nothing downstream from this job will run. For example. This job will not run until its starting conditions re-occur.” it will not start. but is still defined. Whereas. For details on how “on ice” affects boxes. if its starting conditions are already satisfied. when the job “test_job” changes from the STARTING state to the RUNNING state. Operationally. Example State Diagram: Simple Jobs When a change in job status occurs. it will be scheduled to run. see the chapter “Box Job Logic. this condition is like deactivating the job. The difference between “on hold” and “on ice” is that when an “on hold” job is taken off hold. On the other hand. even if its starting conditions are already satisfied. if an “on ice” job is taken “off ice. a status is depicted using the following box drawing: Jobs 3–15 . it is reported as a CHANGE_STATUS event. The other major distinction is that jobs downstream from the job that is “on ice” will run as though the job succeeded. It will remain on ice until it receives the JOB_OFF_ICE event. and the event processor records it in its log when this status is processed. and it will run.Job States and Status ■ ON_ICE This job is removed from all conditions and logic.

Check Conditions Event generated by Event Processor. and completes with either a failure or success exit code. in which an event satisfies the starting conditions for the job. The job starts.OR - FAILURE 3–16 User Guide . STARTING Event generated by Remote Agent indicating the job has actually been started andis now running. indicating attempt to start job on Remote Machine. Event Processor Event is read by Event Processor EVENT Finds jobs dependent on this event.Job States and Status The following illistration depicts the simplest state transition for a job. Remote Agent RUNNING Inspects Exit Code of the process Event generated by Remote Agent SUCCESS . processes.

it goes into the STARTING state. This RUNNING event usually triggers jobs within the box to also start. the job first goes into the ACTIVATED state when the toplevel box it is in goes into the RUNNING state. this EVENT may trigger Jobs within the box to run. After the job starts. SUCCESS .OR - FAILURE In the case of a box.Job States and Status Example State Diagram: Box Jobs For a job in a box. Event Procesor EVENT Finds jobs dependent on this event. Jobs 3–17 . RUNNING Inspects Exit Status of jobs within it to determine if box is done. and then runs. If the job has a priority associated with it. and there are not enough machine resources available. the box always goes into the RUNNING state as soon as all its starting conditions are met. Once the resources become available. However. as shown in the following illistration. Check Conditions Event sent by Event Processor indicating tht the box is "Running. and if so what the Exit Status is." Nothing actually RUNS. all its starting conditions have been met. it goes into the QUE_WAIT state. the remainder of the scenario is the same as for simple jobs.

By displaying the detail of the job (either in the Job Activity Console. As a result. If it ended successfully. or in the output of the autorep command). Therefore. In addition. all jobs within the box change state to ACTIVATED before they run. If a box completes before a job is run. 3–18 User Guide . the status will remain as it is on completion. after a job has completed. Jobs will then run immediately. Therefore. the status always reflects the most recent event that was processed. including those that have not processed yet. a job might have actually completed on a machine and if the event processor has not processed that event yet. the status will remain as SUCCESS until the job is run again. Unicenter AutoSys JM will still show the job’s status as RUNNING.Job States and Status The value of status reflects the event processing. jobs do not retain their statuses from previous box processing cycles once a new box cycle has begun. unless other conditions apply. you can see all the events for a job. Note: When a box job starts. the job is set to INACTIVE at the time of box completion.

then “Job1” and “Job3” would start simultaneously as soon as the box they are in started running. (Jobs that are dependent on a job that is ON_ICE run as if that starting condition has been satisfied.Starting Parameters Starting Parameters Unicenter AutoSys JM determines whether or not it should start a job based on the evaluation of the starting conditions (or starting parameters) defined for the job. To implement a sequence within a box. Note: It is very important to keep in mind the above four conditions. if there are three jobs inside a box. “Job1” may have no starting conditions. It also means that if there are no additional conditions on the job. Placing a job in a box means that the job inherits all the starting conditions of the box job. it will be started as soon as the box is started. The current status of the job is not ON_HOLD or ON_ICE. you must specify additional starting conditions for each job. a job runs only once per box execution. then when the box is started. and none of them has any additional conditions. all three jobs will be started. ■ ■ ■ Every time an event changes any of the above conditions. For example. Also. For jobs in a box. and determines whether or not to start them. These conditions can be one or more of the following: ■ Date and time scheduling parameters are met (it is or has passed the specified date and time). Unicenter AutoSys JM finds all the jobs that might be affected by this change.) Jobs 3–19 . the box job must be running. while “Job2” is dependent on the completion of “Job1.” Be aware that if this scenario were implemented and “Job2” were placed ON_ICE. there is no concept of sequential job processing in a box. Starting Parameters and Boxes Be aware that for a job in a box to start. the box must be in the RUNNING state. Starting Conditions specified in the job definition evaluate to true. all defined starting conditions must be true. In order for a job to start. For example. By default.” and “Job3” is dependent on the completion of “Job2.

if you define a job to be started on Monday.m. and 5:00 p.m. The 3. which you can define using the Graphical Calendar Facility. and 5:00 p.m. Before you start the event processor. For example. ensure that the TZ environment variable is set. denoted in minutes past the hour. You can also specify a time zone to apply to your starting times. jobs with time-based starting conditions that do not specify a time zone are scheduled to start based on the time zone of the TZ environment variable (the same time zone under which the event processor runs).m. autosc.4 event processor must be started once after you upgrade your database to insert the value of the TZ environment variable into the database. or hourly.m. You can specify either form using JIL or the GUI (you do not have to create custom calendars). A time range cannot span more than 24 hours. and Friday at 8:00 a.4. based on the information you supply using JIL statements or the GUI. but you can only specify actual dates through the use of custom calendars. Wednesday. and 5:00 p. Do this before executing jil.m. You can specify days of the week using JIL or the GUI.m.. or autorep. Wednesday at 8:00 a. You can specify times as certain times of the day. autocons. Unicenter AutoSys JM then calculates a matrix of these values and starts jobs at those times.m. However. You define these dependencies by specifying the days or dates and times for time-based job starts. and Friday at 8:00 a. Again. and 5:00 p. you cannot specify both.Starting Parameters Date/Time Dependencies Unicenter AutoSys JM jobs can be automatically scheduled to start at a certain date and time. 3–20 User Guide . the two formats are mutually exclusive. it will be started 6 times a week: Monday at 8:00 a. TZ Environment Variable By default. You can specify days of the week or actual dates...

and the equation is evaluated from left to right. Starting conditions can be as simple as specifying “JobB” to start when “JobA” achieves a SUCCESS status. In this way. Job Dependencies Related to Job Status You can start jobs based on the current status of one or more jobs. These jobs must exist in the database. You may use the pipe symbol (|) instead of the word “OR. batch queuelike logic. you can define any number of custom calendars. You can configure more complex conditions by combining a series of conditions with the AND or the OR logical operators. you can use chk_cond. they are referenced by jobs through job definitions. Note: If a condition is specified for an undefined job. Spaces between conditions and delimiters are optional. You can use these calendars in one of two ways: as days on which to run the jobs with which they are associated. Calendars exist independently of any jobs that may be associated with them. and any jobs dependent on this condition will not run. To check for this type of invalid condition statement. The parentheses force precedence. Given the sample script of: (success(JobA) and success(JobB)) or (done(JobD) AND done(Job E)) would be evaluated. the condition will be evaluated as FALSE.Starting Parameters Custom Calendars Using the Graphical Calendar Facility or the autocal_asc utility. the stored procedure.” and the ampersand symbol (&) instead of the word AND. and “JobC” to start when “JobB” achieves a SUCCESS status. and the results would be A and B or D and E. or as days on which to not run the jobs with which they are associated. You can specify even more complex conditions by grouping the expressions in parentheses. each with a unique name and containing any number of dates or date/time combinations. Jobs 3–21 . These starting conditions enable you to program simple or complex prerequisites that must be met in order to initiate a job. reading from left to right. you can implement a single-threaded.

while the GUI field will only contain the language for the dependency itself. You can also abbreviate the dependency specification exit code with the letter e and VALUE (of a global variable) with the letter v.Starting Parameters The syntax for defining job dependencies is the same whether the job is being defined using JIL or the GUI. Indicates that the status condition for job_name is anything except RUNNING. The only difference is the JIL statement will begin with the JIL condition keyword. The dependency specification can take one of the following three forms: ■ ■ ■ Based on the current status of other jobs Based on the UNIX exit codes of other jobs Based on global variables This is the syntax for conditions based on job status: status(job_name) where: status success failure done Is one of the following: Indicates that the status condition for job_name is SUCCESS. using s. and n. You can abbreviate the status condition identifiers with the first letter. Indicates that the status condition for job_name is SUCCESS. Indicates that the status condition for job_name is TERMINATED. d. FAILURE or TERMINATED.or lowercase. f. Indicates that the status condition for job_name is FAILURE. Is the job on which the new job is dependent. These abbreviations can be upper. terminated notrunning job_name 3–22 User Guide . t.

However. Cross-Instance Job Dependencies Cross-instance job dependencies can be implemented among different instances. Note: Either uppercase or lowercase can be used to specify a status. the case cannot be mixed in either of the forms described. any job that exits with an exit code less than or equal to the specified value will be treated as a success. You can define jobs to have cross-instance dependencies. A FAILURE status means the job exited with an exit code higher than this value. and as an server/client. Multiple instances are not inherently connected. An instance is one licensed version of Unicenter AutoSys JM software running as an server. It uses its own event server and event processor and operates independently of other instances. If you specify this attribute. Jobs 3–23 .Starting Parameters You can control the value of the SUCCESS status by using the “Maximum Exit Code for Success” attribute. which is the instance’s unique. and multiple instances can send events to each other. For example. capitalized three-character identifier. on a single machine or on multiple machines. The convention (and the default) for normal job completion is “0”. which can be set for a job. but they can communicate with each other. multiple instances can send events to each other by way of a sendevent command line like: sendevent -E STARTJOB -J job_name -S autoserv The job_name argument is a job defined for the instance indicated by the autoserv argument. A TERMINATED status means the job was killed.

If the target instance cannot be reached.Starting Parameters In addition. The specification for such a job dependency might look like: condition: success(jobA) AND success(jobB^PRD) The success(jobB^PRD) condition specifies the successful completion of a job named “jobB” running on a different instance specified with the three-letter ID of “PRD. 3–24 User Guide . One Instance of AutoSys ACE One Instance of AutoSys PRD Event Server config. However.ACE config. an EXTERNAL_DEPENDENCY event is sent from the requesting instance.EXTERNAL Event Processor Event Server config. Each time a cross-instance dependency is encountered. each with a single event server. see Running Cross-Instance Job Dependencies in the chapter “Introduction. by default. jobs can be associated with more than one instance.” If the dependency specification does not include a caret (^) and a different instance ID.PRD File config. The following illistration shows two instances. they must have a different value for %AUTOSERV%. an INSTANCE_UNAVAILABLE alarm is issued. both on the event processor machine and on machines running remote agents. a job defined to run on one instance could have as a starting condition the successful completion of a job running on a different instance. For example. the current instance will be used. exchanging cross-instance job dependencies.EXTERNAL Event Processor condition: success (jobB^PRD) jobE jobB condition: success (jobE^ACE) Different instances can run from the same executables and can have the same values for %AUTOSYS% and %AUTOUSER%.” in the Unicenter AutoSys Job Management for UNIX Installation Guide. For information on configuring for cross-instance job dependencies.

instances with Sybase data servers can only connect with other instances having Sybase data servers. ■ In both tables above. An entry to the req_job table of the receiving instance. different event processors can do the following: ■ ■ ■ Be run on different server machines or on the same server machine.Starting Parameters Event processors When cross-instance dependencies are implemented. as shown following: jobB^PRD The use of multiple databases is completely independent of instances using cross-instance dependencies. That is. Each time a job definition with a cross-instance job dependency is submitted to the database. Note: When communicating with event servers. each using dualevent servers. the event processor will try to resend an event (or events) every five minutes until the other instance’s event server can be reached. a caret symbol (^). Access the same client machines to start jobs. The entries in this table specify the status of jobs in other instances in which this instance has an interest. event processors can only connect to those instances with “like” event servers. The entries in this table specify the jobs that have been specified as a job dependency in a job definition on the source instance. the following entries are made: ■ An entry to the ext_job table of the issuing instance. Send events to other AutoSys instances. Note: If the event server of a target instance is down. Event Servers Event servers keep track of the cross-instance job dependencies. Jobs 3–25 . The same holds true for instances with Oracle databases. You can have multiple instances. jobs are entered using the job name. and the instance name.

” Spaces between conditions and delimiters are optional. With this latitude. you can program branching paths that must be taken and that will provide alternate actions for error conditions. you might want to call a routine titled “Backout” that backs out of the changes that were made. You can enter these operators in uppercase or lowercase.Starting Parameters Example Job Dependencies For a job that runs only if the job named “DB_BACKUP” succeeds. You can specify more complex conditions by grouping the expressions in parentheses. but not in mixed case. the job dependency specification would be written as follows: success(DB_BACKUP) or: s(DB_BACKUP) You can configure more complex conditions by combining a series of conditions with the AND or the OR logical operators. if “JobB” fails after processing only partially. you can use the symbol | instead of the word “OR. In addition. or terminated. You would specify the following job dependency in the job definition for “Backout”: failure(JobB) or: f(JobB) 3–26 User Guide . you would specify the following dependency in the job definition for “JobC”: (success(JobA) AND success(JobB)) OR (done(JobD) AND done(JobE)) or: (s(JobA)&s(JobB))|(d(JobD)&d(JobE)) As indicated in this example. For example. The parentheses do not imply any sort of precedence. regardless of whether they failed.” and the symbol & instead of the word “AND. For example. succeeded. you can use any job status as part of the specification for a specific job’s starting conditions. if “JobC” should only be started when both “JobA” and “JobB” complete successfully or when both “JobD” and “JobE” complete. they are simply used for grouping.

For example. running one job is exclusive of any others). Placing the jobs in one processing cycle inside a top-level box and setting the box to start at the beginning of the processing cycle will prevent time-critical jobs from being affected by invalid information. regardless of when it last ran. Managing Job Status Starting conditions that are based on job status use the current (or most recent) completion status of the job. However. where the completion status of a job for some previous time period should not affect the processing of this time cycle. However.Starting Parameters You use the notrunning operator to keep multiple jobs from running simultaneously (that is. you might have a smaller job that can run as long as both of these resource-intensive jobs aren’t running. use the virtual machine and job queuing feature described in the chapter “Load Balancing and Queuing Jobs. You would specify the smaller job’s dependency like this: notrunning(DB_DUMP) AND notrunning(BACKUP) Note: If you have jobs that you want to run exclusively. This would cause the hard disk to be accessed very frequently. all the jobs within the box have their status changed to ACTIVATED. Jobs 3–27 . When a box job is started. there are several options you can use to control statuses. it might be best not to run a database dump (“DB_DUMP”) and a file backup (“BACKUP”) at the same time. if you wish to enforce the concept of time-based processing cycles. downstream jobs in the box that depend on the completion of jobs upstream in the same box will use only the completion statuses from this run of the box.” in this guide. Therefore. The current completion status is defined by the last execution of the job.

or >= Is any numeric value. and prior to its being run for the first time. its status is set to INACTIVE. you can base job dependencies on exit codes that indicate completed tasks. value 3–28 User Guide . >. If you change the status of a top-level box to INACTIVE. Is one of the following exitcode comparison operators: =. <=. In this way. you can implement even more specific branching logic for recovering from job failures. <.) Job Dependencies Based on Exit Codes In addition to job status. the completion status from the last run will no longer be the current status. and it will not be used. != (not equal). To change a job status to INACTIVE. By changing to INACTIVE the status of jobs that have completed. However.Starting Parameters When a job is first entered into the database. but whose completion status should no longer be used in dependent job conditions. you can create an AutoSys job to accomplish this as well. (Updating a job using JIL does not change the status of the job. Of course. Deleting and reinserting the job using JIL will accomplish the same thing. For example. when this code is encountered. use the GUI (Send Event dialog). all the jobs in the box are recursively set to INACTIVE. This is the syntax you would use to specify this type of job dependency: exitcode (job_name) operator value where: job_name operator Is the name of the job upon which the “new” job is dependent. if a broken communication line results in “JobA” failing with an exit code of “4”. or use the sendevent command. you want the system to execute a shell script (“JobB”) which redials the line. the past reporting history on the job will no longer be available.

This exit value is the last thing returned to Windows when the program terminates. Windows programs return any exit values that are programmed within the executable code. but some programs can return unexpected exit codes. With this latitude. After the job has been created. The expected error values should be documented with each individual program. and account for. Generally. you would enter the following for the job dependency specification for the “JobB” redial job: e (JobA) = 4 You can use any job status or exit codes as part of the specification for starting conditions. Use these values when specifying exit code dependencies. a zero exit code indicates success. For the previous example. Jobs are created using standard Windows process creation techniques. you should be aware of. Using Exit Codes and Batch Files with Jobs Running on Windows When you are defining jobs that will run batch files on Windows. Jobs 3–29 . You should modify these programs so that they return expected values. the remote agent waits for the job to complete.Starting Parameters You can abbreviate the dependency specification exit code with the letter e (uppercase or lowercase). Unicenter AutoSys JM gets the program exit code from Windows and stores it in the database for later use. the Windows-specific behavior. while a non-zero exit code indicates an error. you can program branching paths that will provide alternative actions for all types of error conditions. When the job completes.

When using global variables in this way.EXE. the value of the expression must evaluate to TRUE for the job dependency to be satisfied. Job Dependencies Based on Global Variables Job dependencies can also be based on global variables you set using the Send Event dialog or the sendevent command. In this case.tmp does not exist.Starting Parameters When launching programs directly.tmp false 1 When test fails with errorlevel 1.” and make the top-level box job dependent on this global variable. Consider the following example: REM test batch file test if errorlevel 1 goto bad goto good :bad del test. If test. which is the exit code you want false to return on completion.tmp exists. this batch file will return an exit code of 1 from false. However. whether the test. You can use false in the above example batch file. such as only on your manager’s approval. This program is located in the Windows %AUTOSYS%\bin directory and takes only one parameter. like: REM test batch file test if errorlevel 1 goto bad exit :bad del test. Unicenter AutoSys JM supplies a program called FALSE. the return code is from the del line and not from the line that executes test.tmp file exists or not. To help handle situations like this.BAT batch files. this batch file will return a 0 (successful) exit code. Global variables are referenced using the following expression: 3–30 User Guide . Therefore.tmp :good exit This example batch file will return a 0 exit code as long as test. the exit codes are returned and put in the database. The exit code returned from a batch file is the return code from the last operation executed from within that particular batch file. even if test failed to execute as intended. For example. you have a set of jobs in a box that are only supposed to run on special occasions. there are some exit code behaviors that you must take into consideration when using to start *. you would set the global variable named “manager-ok” to “OK.

When using JIL. <=. enter the above expression in the Starting Condition field. >. Jobs 3–31 . This design permits runs of nested jobs to be associated together within the same run. != (not equal). Consecutive run numbers are assigned every time a top-level job starts. and these run numbers are inherited by every job that is in a box. When using the Job Definition dialog to define a job. In the example cited above. Is one of the following: =. Is the name of the global variable upon which the job is dependent. The run number is a unique integer associated with every run of a job. You can abbreviate the dependency specification VALUE with the letter v (uppercase or lowercase).or lowercase.Job Run Numbers and Names VALUE(global_name) operator value where: VALUE global_name operator value Can be upper. This means that all jobs within a top-level box have the same run number as the number used for the run of the box. A top-level job is a job that is not contained in a box. The global_name and the value can each be a maximum of 30 characters. enter the above expression in the appropriate JIL script using the condition attribute. you would enter the following for the job’s condition statement: VALUE(manager-ok) = OK or: v (manager-ok) = OK Job Run Numbers and Names Unicenter AutoSys JM employs the notion of run numbers for jobs. or >= Is any numeric value or text string (no quotes or spaces). <.

In the standard reports (see the autorep command in the chapter “Commands. run. this value is accessible to those shell scripts or executables executed as the job’s UNIX command. you can input them interactively to the jil command. you can open the GUI by using the autosc command. the run number remains the same. Unicenter AutoSys JM also maintains a value for each job’s name. The value is contained in the variable $AUTO_JOB_NAME. so you can have a file to restore from in case of system failure. Graphical User Interface Components You can use the GUI to interactively define. The value of run_num/ntry is defined in the runtime environment for the job. This value is contained in the variable $AUTORUN. which you can redirect into the jil command. or you can store them in text files.” in this guide. and you can enter the job definition by filling in the appropriate fields of the Job Definition dialog and its associated dialogs. You should back up your job definitions periodically. Unicenter AutoSys JM provides the following top-level Windows and dialogs. Defining Jobs You can define jobs using one of two methods: JIL statements or the GUI (in the Job Definition dialog). When you use JIL statements. monitor. and report on jobs. manage. these two values are displayed in the “Run” column as run_num/ntry. which you can launch from the GUI Control Panel: 3–32 User Guide . As with $AUTORUN. and the ntrys field is incremented. and it is accessible to those shell scripts or executables executed as the job’s command.” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide).Defining Jobs If there are restarts of a job. Alternatively. This process is explained in Backing up Definitions in the chapter “Maintaining. which is defined in the runtime environment for the job.

The Graphical Calendar Facility and its related dialogs allow you to create calendars in order to simplify job scheduling. and delete job definitions for command jobs. setup conflict resolution. ■ Operator Console Used to monitor and manage jobs. box jobs. block certain dates. using the Job Definition dialog. Jobs 3–33 . Then. Alarm Manager dialog. The Operator Console consists of the following components: Job Activity Console. Job Selection dialog. The Monitor/Browser allows you to define filters by which you can screen AutoSys system information. and preview calendar definitions before assigning them to jobs. build calendars based on combinations of other calendars. you can use the Alarm Selection dialog. you can use the Job Selection dialog. view. you can assign them to a certain job. Monitors provide real time views of the system. edit. and file watcher jobs. Monitor/Browser Used to define monitors and reports.Defining Jobs ■ Job Definition dialog Used to define jobs. The Alarm Manager allows you to browse and handle alarms. It allows you to create custom rules. Browsers (reports) provide historical views of system information. The Job Definition dialog and its related dialogs allow you to create. The Job Activity Console allows you to monitor jobs. and Alarm Selection dialog. ■ Graphical Calendar Facility Used to define calendar definitions. and to filter the alarms that it displays. and to filter the jobs that it displays.

You should back up your job definitions periodically so you can have a file to restore from in case of system failure. and the job definition is always stored in the database. Job Attributes and Job Definitions You define a new job by assigning it a name and specifying any number of attributes that describe its intended behavior.Before modifying or deleting an existing job.Regardless of method. These attributes determine what a job does. There are two methods of creating a job definition: using JIL and using the Job Editor. Job Attributes 4–1 . including when and where it will run.Chapter 4 Job Attributes This chapter describes the essential and optional job attributes used to define jobs. make sure the job is not running. This specification of a job’s behavior is called a job definition. For more information see the chapter “Maintaining.” in this guide. the specified set of attributes is the same.

you enter the jil command to display the jil prompt. Is the setting to be applied to the attribute. Your JIL commands will look like this: insert_job: job_name attribute:value . where: job_name attribute_keyword value Is a unique job name. and set the various attributes and their values using the text fields and push-buttons in the Job Editor. Using the Job Editor to Create a Job Definition When using the Job Editor to create a job definition. Is one of the legal JIL attributes. click on the Job Editor button in the GUI Control Panel. 4–2 User Guide . At this prompt.Job Attributes and Job Definitions Using JIL to Create a Job Definition When using JIL to create a job definition. You can also use JIL sub-commands to modify or delete an existing job definition. open the GUI Control Panel from the Graphical Interface icon in your program group... you define a job using the insert_job subcommand followed by any desired attribute:value statements which specify an action to be performed.

For each attribute described in this chapter. of the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. Essential attributes are those that must be specified in order for the job definition to be accepted. As the name implies. or GUI Field Name. job attributes are organized into two categories: Essential and Optional. optional attributes are not necessarily required for a job definition to be accepted. Job Attributes 4–3 . and a description of its use. we indicate its name. as in the following illustration.Job Attributes and Job Definitions Organization In this chapter. its corresponding Job Editor object. For more information see the chapter JIL/GUI Job Definitions. its JIL attribute keyword.

File Watcher (f). and Box Jobs cannot use the same name. and is terminated with white space. Commands. or Box (b). 4–4 User Guide . Job Name insert_job New Job and Save dialogs: Job Name The job name is used to identify the job to.Essential Job Attributes Essential Job Attributes Attributes Common to All Job Types The following attributes are common to all job types: Command. Although defaults may be available. Job Owner owner Basic Tab: Owner The job owner specifies whose user ID the command will be run under on the client machine. It can be from 1 to 30 alphanumeric characters. and Box. and cannot be changed except by the Edit Superuser. Job Type job_type New Job dialog: Job Type The job type specifies the type of job: Command (c). File Watchers. the attributes in this section are still essential due to the fact that every job definition must include them. whether by default or by explicit specification. and must be unique. File Watcher. This attribute is automatically set to the user who invoked jil or the Job Editor to define the job. Embedded blanks and tabs are illegal.

or as part of the command’s runtime arguments. the following attributes must be specified in addition to those listed in the Attributes Common to All Job Types section previously shown. all resources and files referenced by the command’s execution must also be accessible to the job’s owner. NTFS). the specific variables are set correctly): initautosys -i Instance -r “command_line” where: Instance command_line Specifies the instance name. Job Attributes 4–5 . Command command Basic tab: Command The command attribute can be the name of any command. When issuing commands that are to be run on a different operating system. and its arguments. Specifies the full command line. for more information see Profile in this chapter.) User-defined environment variables necessary for the command to be executed are defined by a job profile. use the sendevent command. this profile is sourced before a job is executed. If the command resides on a file system that supports NT security mechanisms (for example. If you want to use an command in the Command field or for the command attribute. Global variables can be used as part of the command name itself. which you can launch from several places in the GUI. then the job’s owner must have read and execute permission on that command. Input and output redirection cannot be part of the command. The job’s owner must have execute permission for this command on the client machine. UNIX shell script or batch file.Essential Job Attributes Command Jobs Attributes For Command jobs. (By extension. Redirection is specified by other job attributes. To set a global variable. you must use the syntax appropriate to the operating system of the client machine. This command line must be in quotes. you must use the following syntax (when you use this syntax. or use the Send Event Tool. executable.

Job attributes. if you are including a drive letter with the pathname. \TAURUS\C$\tmp. output. Command line arguments can be passed using global variables. jobs are started in the foreground to allow Windows applications to interact with the desktop. If you do not specify a profile specifically. You must use a fully qualified network name instead. do not use escape characters. either in the default one (which on Windows is initially empty) or in a user-defined job profile. When using the GUI applications and dialogs. can be used to provide the necessary functionality. such as std_in_file for standard input. described in the section Job Profiles in the chapter “Jobs. the userdefined environment variables and the variables defined in the job profile are probably different. Redirection of standard input.Essential Job Attributes You cannot use a network drive letter in a command definition. the colon must be escaped (for example "C:\tmp" and C\:\tmp are valid. the default profile is used. C:\tmp is not). enter an ampersand (&) as the first character in the job command attribute.” in this guide. Although system environment variables will be set automatically into the command’s environment. but it fails to run or run properly when specified as a command attribute. and error files is not allowed in the command attribute. When using JIL. For example. All other required environment variables must be defined in the job’s profile. 4–6 User Guide . To define profiles. Note: That \TAURUS\C$ must be shared so that no password is needed to access it. To launch a job in the background. These are additional points to keep in mind with regard to the command attribute: ■ By default. If this is the case. user environment variables will not be. ■ ■ ■ If a command works properly when issued at an MS-DOS command prompt. make sure that all required user environment variables are defined correctly in the job’s profile. use the Profiles Manager.

or a virtual machine. and how Unicenter AutoSys JM chooses a machine to run on when you specify multiple machines or a load balancing program.Essential Job Attributes Machine to Run On machine Basic tab: Send to Machine This attribute specifies the client machine on which the command should be run. Localhost implies: “run on the machine on which the Event Processor is currently running.” The job might run normally on the Primary Event Processor machine. a set of real machines. Real machines must be accessible over the network using the TCP/IP protocol. and yet fail on the Shadow Event Processor machine. The job’s owner must have permission to access this machine and to execute the specified command at this machine.” in this guide. you should never set the machine attribute to localhost. Note: If you have implemented the Shadow Event Processor feature. Job Attributes 4–7 . see the chapter. The machine can be a specific real machine. “Load Balancing and Queuing Jobs. For more information about virtual machines.

When using the GUI. When using JIL. Wildcards cannot be used in the file name. C:\tmp is not). 4–8 User Guide . the following attributes must be specified in addition to those listed in the section Attributes Common to All Job Types. For a File Watcher. do not use escape characters. the colon must be escaped (for example "C:\tmp"and C\:\tmp are valid. Machine to Run On machine Basic tab: Send to Machine This attribute specifies the client machine on which the File Watcher should run. to determine when a file is considered to have arrived. but the file itself does not have to exist at the time the job is defined. For more information on how to use wildcards. File to Watch For watch_file File to watch The name of the file to watch for must be a legal file name and must include the full path to the file. as well as global variables. in this chapter. Box Job Attributes For more information on Box Job Attributes. if you are including a drive letter with the pathname. Environment variables defined and exported in the profile file (the specified or default). this field only appears when the File Watcher type has been selected.Essential Job Attributes File Watcher Job Attributes For File Watcher jobs. All directories in the path must exist. This attribute is used in combination with the Watch File Minimum File Size and Watch Interval attributes. see the section Attributes Common to All Job Types. in this chapter. this attribute must specify a single real machine. When using the Job Editor. see the Unicenter AutoSys Job Management for UNIX and Windows Reference Guide in the watch_file section. can be used in the path. accessible over the network using TCP/IP.

File Watcher. or all for every day. Days of the Week days_of_week Date/Time tab: Run Days The days of the week attribute specifies the days on which the job should be run. Start Date /Time Dependence date_conditions Date/Time tab: Date/Time Conditions The start date/time dependencies attribute is a toggle. which specifies whether or not there are date or time conditions required for starting the job. Each calendar is stored in the database as a separate object with a unique name. and typically default to “inactive” or NULL if not specified. Days to Run on —Using a Custom Calendar run_calendar Date/Time tab: Run Days The days on which a job should be run can be specified by way of a custom calendar. Custom calendars. the remainder of the related date/time attributes described below will be ignored. and Box. Job Attributes 4–9 . specified through the Calendar Editor. see the section Date and Time Attributes and Time Changes. You can specify one or more days. If set to no. and a calendar can be associated with one or more jobs. using this attribute or the exclude_calendar attribute. These attributes are used to specify when a job should start. For information on how date and time attributes are affected by the Spring and Fall time adjustments. rather than through a list of days of the week. or the autocal_asc command. can include any number of dates on which the job should be run.Optional Job Attributes Optional Job Attributes Common Job Starting Attributes The following optional attributes are common to all Job Types: Command. in this chapter.

Time of Day Not to Run run_window Date/Time tab: Run Window This attribute specifies a time range (or time window) during which a job can be started. specified through the Calendar Editor. This setting can prevent a latearriving file from causing a job to run at an inopportune time. and there are certain times when jobs dependent on that file should not run. The sendevent command can be used to accomplish this. or from within a shell script or batch file in another job. or the autocal_asc command. it is not known when a watched-for file will arrive. and the “Anytime After Midnight” attributes are mutually exclusive. The run window range cannot span more than 24 hours. This attribute controls only when the job will start. This attribute is particularly useful when. Specific Times of Day to Run start_times Date/Time tab: Times of Day This attribute specifies one or more specific times of day when the job should be started. can include any number of dates on which the job should not be run. 4–10 User Guide . Note: You can also block out times of day when you do not want a job to start by putting the job on hold. When the starting conditions for a job have been met. then taking it off hold later. for example. on every day specified in the associated date attributes. and a calendar can be associated with one or more jobs. Each calendar is stored in the database as a separate object with a unique name. The job will not start outside of the specified window. This attribute.Optional Job Attributes Days to NOT Run on—Using a Custom Calendar exclude_calendar Date/Time: Exclude Calendar The days on which a job should not be run can be specified by way of a custom calendar. executed either from the command line. Unicenter AutoSys JM checks if the current time is within the specified run window. The job will be started at each specified time of day. Custom calendars. jobs that are not in a box must have starting conditions in addition to the run_window attribute in order for the job to be automatically started. using this attribute or the run_calendar attribute. through the Send Event Tool. not when it will stop running. the “Minutes after Each Hour” (start_mins).

every dependency must evaluate to true before the dependent job will be run. The job will be started at each specified time every hour of the day. Job dependencies can reference jobs residing on different instances. and the value of a global variable. failure of a job. This attribute. however.Optional Job Attributes Specific Times Every Hour to Run start_mins Date/Time tab: Minutes after Each Hour One or more specific times per hour when the job should be started can be specified. Each time is specified in minutes past the hour. If a condition is specified for an undefined job. Examples of job dependencies include successful completion of a job. Various combinations of conditions may also be specified. a job’s exit code. on every day specified in the associated date attributes. and the “Anytime After Midnight” attributes are mutually exclusive. the “Minutes after Each Hour” (start_times). and any jobs dependent on this condition will not run. the condition will be evaluated as FALSE. Job Dependencies condition Basic tab: Dependencies Any number of job dependencies can be specified. Job Attributes 4–11 .

and Box. to “gate” the jobs inside the box.” and the chapter “Defining Jobs Using JIL. used for documentation purposes only. Minimum Run Time Alarm min_run_alarm Alarms/Terminators tab: Minimum Run Time 4–12 User Guide . then specifying their starting conditions relative to each other individually. This feature is particularly useful for setting starting conditions at the box level. The functionality listed in these locations will help you when creating your own job definitions. Description description Basic tab: Description This attribute provides a comment field. you can use the chk_cond stored procedure. These attributes are used to specify a variety of features.” in this guide. and typically default to “inactive” or NULL if not specified. Box Name box_name Basic tab: Box Boxes allow a set of jobs to be manipulated as a group.” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. File Watcher. When entering a description using JIL. you should enclose the string in double quotes to ensure JIL properly interprets it. The Job Editor adds quotes for you automatically. if necessary. The specified box must already exist before you can place jobs in it. For more information see the section Starting Parameters in the chapter “Jobs.Optional Job Attributes To check for this type of invalid condition statement. For more informatin see the chapter “Commands. This attribute specifies the name of the box in which the job is to be placed. Common General Attributes The following optional attributes are common to all job types: Command.

the Alarm Sentry. or it completes by itself. The attribute “Terminate this job n mins after starting” (term_run_time) can be used to automatically terminate a job that has been running for too long. such as the application being stuck in a loop. and they do nothing on their own. If the job runs longer than this time. the job should not take longer than the specified time to finish. This reasonability test may catch an error. A monitor. Maximum Run Time Alarm max_run_alarm Alarms/Terminators tab: Maximum Run Time A maximum runtime can be specified for a job. Terminate Due to Run Time term_run_time Alarms/Terminators tab: Terminiate this job n mins after starting A maximum run time (in minutes) can be specified for a job. the job should not take longer than the specified time to finish. the job will continue running until manually interrupted. or the Alarm Manager must be running and tracking alarms in order for them to be seen and acted upon in real-time. This feature allows the job to be automatically terminated if it runs longer than the allotted time. Alarms are informational.Optional Job Attributes A minimum run time (in minutes) can be specified for a job. or the application waiting for additional data which may never arrive. the job should not end in less than the specified time. Alarms are informational. Send Alarm if the Job Fails alarm_if_fail Alarms/Terminators tab: Send Alarm if this job fails Job Attributes 4–13 . an alarm is generated to alert someone to investigate the situation and take corrective action. or the Alarm Manager must be running and tracking alarms in order for them to be seen and acted upon in real-time. an alarm is generated to alert someone to investigate the situation and take corrective action. If term_run_time is not set. If the job does end prior to this time. This may prevent an inadvertent truncation of the file being processed before it is complete. and they do nothing on their own. the Alarm Sentry. A monitor.

or the Alarm Manager must be running and tracking alarms in order for them to be seen and acted upon in real-time. KILLJOB will kill the process specified in the command definition. you can control how nested jobs react when a job fails. or TERMINATED. you can control how nested jobs react when a job fails.bat) files will not be killed. (The Maximum Exit Code for SUCCESS attribute determines what codes are interpreted as FAILURE for a job. The Job Status will be set according to the return code of the killed CMD. FAILURE. KILLJOB will kill only the CMD.exe.bat. terminate the box it is in This attribute specifies whether or not the box containing this job should be terminated if the job fails or terminates. and the Failure Condition attribute for Box Jobs determines what constitutes a box failure. *. terminate this job attribute.EXE to launch the job. *. terminate the box it is in attribute. Unicenter AutoSys JM uses CMD. terminate this job This attribute specifies whether or not the job should be terminated if the box it is in fails or terminates. This attribute only applies if the job is being placed in a box.) Alarms are informational.exe (for example. A monitor.EXE process. If the job that was launched was a *.cmd. Any processes that were launched by user applications or batch (*. the Alarm Sentry.EXE process.com).Optional Job Attributes This attribute specifies whether or not an alarm should be generated when the job fails. By using this attribute in combination with the If this box fails. This status can be any one of the following: SUCCESS. Failure is defined as the job completing with a FAILURE or TERMINATED status. This attribute only applies if the job is being placed in a box. 4–14 User Guide . Terminate the Box if the Job Fails box_terminator Alarms/Terminators tab: If this Job fails. or *. By using this attribute in combination with the If this job fails. If the job being run is not a *. Note: Windows does not support the concept of process groups. and they do nothing on their own. Terminate the Job if the Box Fails job_terminator Alarms/Terminators tab: If the box fails.

the time settings in the job are based on the specified time zone. or permissions are not properly set). the fork in the Remote Agent failed. Time Zone for Job timezone Date/Time tab: Time Zone This attribute allows you to schedule a job based on a chosen time zone. When this attribute is used.” in this guide. the socket connect timed out. For example. if any.For more information on Max Restart see the chapter “Administrator. or the file system space resource check failed). For example: timezone: "IST-5:30" If you do not quote a time zone specification that contains a colon. it does not apply to system or network failures (for example. JIL will interpret the colon as a delimiter.m.Optional Job Attributes Number of Times to Restart a Job n_retrys Misc tab: Number of times to restart this job after a failure This attribute specifies how many times. in Denver. Pacific time. which means the job will not be automatically restarted after an application failure. the job will start at 1:00 a. if you define a start time of 01:00 for a job running on a machine in Denver. which is 2:00 a. Jobs with timebased starting conditions that do not specify a time zone will have their start event scheduled based on the time zone under which the Event Processor is running. and enter SanFrancisco in the Time Zone field. This attribute applies to application failures (for example. If you specify a time zone that includes a colon.m. machine unavailability. producing unexpected results. The default is “0”. Unicenter AutoSys JM is unable to find a file or a command. the job should be restarted after exiting with a FAILURE status. you must quote the time zone name if you are using JIL. Job Attributes 4–15 . The number of restarts after system or network failures is specified using the Max Restart Trys field on the Administrator Event Processor screen.

you might want to place a job in a box. which is the default. it inherits the box’s starting conditions. At this point.Optional Job Attributes Delete Job After Completion auto_delete Misc tab: Delete Job after completion This attribute indicates whether or not the job definition should be automatically deleted after successful completion. To start the job. however. If the job did not complete successfully. or the attribute can be turned “off” by specifying a negative value (for example “-1”). This attribute is useful for letting Unicenter AutoSys JM schedule and run a one-time batch job. When a job is in a box. This is typically the desired behavior. Unicenter AutoSys JM will keep the job definition for 7 days before automatically deleting it. the Box job will start all the jobs within it (unless other conditions are not satisfied). the job is in exactly the same state as if it were manually placed on hold. AutoSys automatically changes the job state to ON_HOLD when the box it is in begins RUNNING. 4–16 User Guide . For example. there are occasions when it is not. Autohold auto_hold Misc tab: AutoHold on for jobs in boxes This feature is only for jobs in a box. If auto_delete is set to 0. This means that when a box goes into the RUNNING state. but not start the job until a non-job (for example. operating system level) event arrives. Unicenter AutoSys JM will immediately delete job definitions only if the job completed successfully. A number of hours can be specified (including “0” for immediately). take the job off hold by sending the JOB_OFF_HOLD event via the Send Event Tool or the sendevent command. By specifying “yes” to Autohold On.

For more information about setting permissions. KILLJOB and so forth. see the section overview of the chapter “Security.” in this guide.Optional Job Attributes Permissions permissions Misc tab: Permissions The permission scheme provides users with Edit and Execute permissions on a per job basis. Permission attributes can allow a user or the world to edit or execute a job from a different machine. Edit The user or the world can edit the job definition itself. all Edit and Execute permissions are valid only on the machine on which the job was defined (using either jil or the Job Editor). For Windows by default. including deleting the job. The following levels of permissions are supported: Exec The user or the world can issue events that affect the running of the job as in STARTJOB. Unicenter AutoSys JM associates different types of permissions with a job. Machine By default. only a job’s owner has Edit and Execute permission on a job. Job Attributes 4–17 .

On Windows. in this chapter. but. verify that all required user defined environment variables are defined in the job’s associated profile. you can specify a machine name in the path to the profile using the following syntax: \computer_name\profile_name. 4–18 User Guide . If a profile attribute is specified. in the attribute or in the Job Environment Profile field. in addition to those listed in the section Attributes Common to All Job Type. in the chapter “Jobs.” in this guide. it is usually due to the incomplete specification of the required environment for the command in the job’s profile. If a command that normally executes when entered at the command line fails when run as a job. the default profile is initially empty. These attributes typically default to “inactive” if not specified. but you can add variables to it using the Profiles Manager.Optional Job Attributes Command Job Attributes For Command jobs. Since only system environment variables are defined by default when a job runs. that profile_name is searched for on the machine on which the command is to run. You can add and delete job profiles using the Profiles Manager. which you can open from the program group. the following optional attributes can be specified. If no profile attribute is specified. the profile named “default” is used. For more information on the Profiles Manager aee the section Job Profiles. Profile profile Resource Profile: Job Environment Profile The profile attribute specifies the name of the defined job profile that contains the environment variables that should be set for the command’s execution.

The full pathname must be specified. the default is to append this file. as well as global variables. Job Attributes 4–19 . When using the Job Editor. By default. as well as global variables. C:\tmp is not). which you can set on the Administrator System Information screen. you must escape the colon (for example "C:\tmp" and C\:\tmp are valid. If the issuing instance is UNIX. although variables defined in the command’s environment. The default is NUL:. For information on using the Unicenter AutoSys Administrator.” in this guide. Redirection of the Standard Output File std_out_file Command Info tab: File to redirect standard output The standard output file can be redirected to any file on the client machine to which the job owner has write permission. realize that the Event Processor of the issuing instance controls the default behavior. By placing the following notation as the first characters in the std_out_file specification. the colon must be escaped (for example "C:\tmp" and C\:\tmp are valid. C:\tmp is not). do not use escape characters. see the chapter “Administrator. The default is NUL:. When using JIL. the file will be overwritten with new information. When using JIL and including a drive letter with the pathname. if you are including a drive letter with the pathname. When using the Job Editor. Note: If you are running jobs across platforms. although variables defined in the command’s environment. do not use escape characters. you can specify if the error file should be appended to or overwritten: > Overwrite file >> Append file This setting overrides the instance-wide setting for the Append stdout/stderr setting on the Administrator Event Processor screen. can be used in the pathname specification.Optional Job Attributes Redirection of the Standard Input File std_in_file Command Info tab: File to redirect standard input The standard input file can be redirected to any file to which the job owner has read permission on the client machine. The full pathname must be specified. can be used in the pathname specification. It also overrides the machine-specific setting for the AutoMachWideAppend variable.

Optional Job Attributes Redirection of the Standard Error File std_err_file Command Info tab: File to redirect standard error The standard error file can be redirected to any file on the client machine to which the job owner has write permission. do not use escape characters. When using JIL. By default. realize that the Event Processor of the issuing instance controls the default behavior. the default is to append this file. 4–20 User Guide . can be used in the pathname specification. you can specify if the error file should be appended to or overwritten: > Overwrite file >> Append file This setting overrides the instance-wide setting for the Append stdout/stderr setting on the Administrator Event Processor screen. The full pathname must be specified. as well as global variables. the colon must be escaped (for example "C:\tmp" and C\:\tmp are valid. It also overrides the machine-specific setting for the AutoMachWideAppend variable. see the chapter “Administrator. By placing the following notation as the first characters in the std_err_file specification. The default is NUL:. which you can set on the Administrator System Information screen. although variables defined in the command’s environment. the file will be overwritten with new information. When using the Job Editor. if you are including a drive letter with the pathname. For information on using the Unicenter AutoSys Administrator. C:\tmp is not). If the issuing instance is UNIX. Note: If you are running jobs across platforms.” in this guide.

Optional Job Attributes

Job Load job_load Command Info tab: Job Load

Machines can be assigned “maximum job loads,” which is a measure of the CPU load that is desirable for a machine at any given time. Similarly, jobs can be assigned loads, indicating the relative amount of processing power they consume. This scheme allows for machine loading to be controlled, and prevents a machine from being overloaded. If a job is ready to run on a designated machine, but the current load on that machine is too large to accept the new job’s load, the job will be “queued” for that machine, to be run when sufficient resources are available. For load balancing to function properly, all jobs to be run on a controlled machine must have job loads specified; otherwise, their impact on a machine cannot be measured. If you force a job to start, it will run even if its load exceeds the machine’s max_load. Also, if job_load is specified for a job and no priority attribute is set, AutoSys uses the default priority of 0, which means ignore the job_load and run the job immediately. For information about load balancing on machines, see the chapter “Load Balancing and Queuing Jobs,” in this guide.

Queue Priority priority Command Info tab: Que priority

The queue priority establishes the relative priority of all jobs queued for a given machine, with the lower number indicating higher priority. If a job is ready to run on a designated machine, but the current load on that machine is too large to accept the new job’s load, the job will be “queued” for that machine. Priority only influences the starting of jobs that are queued, unless the jobs are in a box. If jobs in a box have a priority attribute setting, they will be processed in order of priority, highest to lowest.

Job Attributes

4–21

Optional Job Attributes

Job Overrides override_job File menu and Basic tab: Add One Time Override

You can specify a one-time job override for the next run of a particular job. An override lets you change the behavior of a job the next time the job runs. The following attributes can be modified in a job override: For a description of how to use the Job Editor to specify job overrides, see the chapter “Defining Jobs using the Job Editor,” in this guide.

override_job menu auto_hold command condition date_conditions days_of_week exclude_calendar machine max_run_alarm min_run_alarm n_retrys profile run_calendar run_window start_mins start_times std_err_file std_in_file std_out_file term_run_time watch_file watch_file_min_size watch_interval

Maximum Exit Code for Success max_exit_success Command Info tab: Maximum Exit Code for SUCESS

The maximum exit code for success attribute indicates what exit codes will be considered as a success. It is used when a command can exit with more than just a single exit code, indicating either “degrees of success,” or other conditions that may not indicate a failure. This attribute lets you define complex branching logic based on specific exit code values. Unicenter AutoSys JM reserves exit codes greater than 120 for internal use, so do not use exit codes of 120 or greater.

4–22

User Guide

Optional Job Attributes

Average Runtimes avg_runtime (JIL only)

The avg_runtime attribute is used to provide an average runtime (in minutes) for a job that is newly submitted to the database; it establishes this value in the absence of the job having been run multiple times. This attribute is used solely to establish an average runtime for the new job in the avg_job_runs table.

Heartbeat-Interval heartbeat_interval Command Info tab: Heartbeat interval (mins)

Heartbeats are a means of monitoring a job’s progress. It automates the common practice of outputting characters, similar to displaying “progress” asterisks across the screen as a process runs. If a job does not send a heartbeat within this specified interval, a HEARTBEAT alarm is generated. The heartbeat interval is specified in minutes. To send a heartbeat from a C program, you call the routine found in the following source file:
%AUTOSYS%\code\testheart.c

The Event Processor must be configured to check for heartbeats. To do this, use the HeartBeat Interval field in the Administrator Event Processor screen. For information on configuring Unicenter AutoSys JM and the Unicenter AutoSys Administrator, see the chapter “Administrator,” in this guide. For information on sending heartbeats, see the section Sending Heartbeats in the chapter “API,”in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide.

Job Attributes

4–23

Optional Job Attributes

Resource Check - File Space chk_files Resource/Profile tab: Resource Check – File System Space

This attribute specifies a minimum amount of file space that must be available on the designated drives for the job to be started. One or more drives, specified with drive letters, and their corresponding sizes, can be specified. If multiple drives are specified, separate them with a single space. Only drives are checked; directories, if specified, are ignored. When the Remote Agent is preparing to start the job on the client machine, it checks whether or not the required space is available before starting the job. If the requirements are not met, an alarm is generated and automatically reschedules the job to start again after a delay. It will perform the same resource check the next time it attempts to start. This feature is intended to prevent a job that is known to require large amounts of file space from failing due to a shortage of space during processing time.

4–24

User Guide

Optional Job Attributes

File Watcher Job Attributes
For File Watcher jobs, the following attributes can be specified in addition to those listed in the section File Watcher Job Attributes, in this guide. These attributes typically default to inactive if not specified.

Watch File Minimum Size watch_file_min_size Basic tab: Minimum file size (in bytes)

The watch file minimum size determines when enough data has been written to the file to consider it complete. This attribute is specified in bytes. You should specify a reasonable file size to ensure that a nearly empty file isn’t assumed to be complete. Use caution with this attribute. If you specify a large file size Unicenter AutoSys JM will wait for the file to reach that size, even if the file has reached a steady state and is no longer growing.

Watch Interval watch_interval Basic tab: Time Interval (secs) to determine steady state

The watch interval specifies (in seconds) how often the File Watcher should check the current file size to ascertain whether data is still being written to the file. The default is every 60 seconds.

Resource Check - File Space chk_files Resource/Profile tab: Resource Check – File System Space

This attribute specifies a minimum amount of file space that must be available on designated file systems for a Command job to be started. One or more file systems, specified with drive letters, and their corresponding sizes can be specified. When the Remote Agent is preparing to start the job on the client machine, it checks whether the required space is available before starting the job. If the requirements are not met, an alarm is generated. File Watcher jobs will still be started.

Job Attributes

4–25

Optional Job Attributes

Box Job Attributes
For Box jobs, the following optional attributes can be specified, in addition to those listed in the section Attributes Common to All Job Types, in this chapter. These attributes typically default to inactive or NULL if not specified.

Box Successful Completion box_success Basic Tab: Success Conditions

The default condition required for a box to be considered successful is that every job in the box must have completed with a success condition. A box can contain complex branching logic, which can take a number of different paths, all of which constitute a success. In this case, some jobs in the box may never need to run, but if the default box behavior is applied, the jobs that had not run would prevent the box from ever completing. This attribute can be used to specify what is considered a success of a single job, or as complex as necessary. This attribute is only displayed in the Job Editor when you select a Box Job Type, and then it is located on the Basic tab.

Box Failure box_failure Basic tab: Failure Conditions

The default condition required for a box to complete with a FAILURE status is that all jobs in the box have completed and one or more jobs in the box completed with a failure condition. A box can contain complex branching logic, which may take a number of different paths, one of which may include recovery from a failed job. In this case, you might want the box to be considered successful, even though a job within it failed. This attribute can be used to specify what will be considered as a failure, which could be as simple as the failure of a single job, or as complex as necessary. This attribute is only displayed in the Job Editor when you select a Box Job Type, and then it is located on the Basic tab.

4–26

User Guide

Date and Time Attributes and Time Changes

Date and Time Attributes and Time Changes
Date and Time attributes can be affected by the Spring and Fall time adjustments. The following sections describe the job run behavior you should expect, and thus can plan for.

The Time Change
During the changes to and from daylight saving time, your operating system automatically changes the system clock to reflect the switch to either Standard Time (ST) or Daylight Time (DT). In the spring, at 2 a.m., the clocks spring forward to 3 a.m. In most of the United States, this happens on the first Sunday in April. The following illustration shows this time change.

When this change occurs, time runs 1:58 ST, 1:59 ST, 3:00 DT, 3:01 DT, and the 2:00 to 2:59 hour is lost.

Job Attributes

4–27

Date and Time Attributes and Time Changes

In the fall, at 2 a.m., the clocks fall back to 1 a.m. In most of the United States, this happens on the fourth Sunday in October. The following illustration shows this time change

When this change occurs, time runs 1:58 DT, 1:59 DT, 1:00 ST, 1:01 ST,..., 2:00 ST, 2:01 ST, and the 1:00 to 1:59 hour is repeated.

Behavior During Time Change
Jobs that are time dependent may have their scheduling shifted to adjust for the time change. Jobs that are not time dependent, but have other starting conditions, will run as normal. There are two types of time dependencies: absolute, and relative. Absolute times are defined to occur at a particular time of day, for example 9:30 on Thursday, or 12:00 on December 25. Absolute time dependent job attributes include:
■ ■ ■ ■ ■

days_of_week exclude_calendar run_calendar run_window start_times

Relative times are specified with respect to either the current time, or relative to the start of the hour. For example, start a job at 10 and 20 minutes after the hour, or terminate a job after it has run for 90 minutes. Relative time dependent job attributes include:

auto_delete

4–28

User Guide

Date and Time Attributes and Time Changes

■ ■ ■ ■ ■

max_run_alarm min_run_alarm start_mins term_run_time watch_interval

During the time change, absolute time attributes will behave differently than relative time attributes, as described below.

Spring Time Change During the change to daylight saving time in the spring, the “2:00-2:59” hour is lost, therefore Unicenter AutoSys JM cannot schedule any jobs during that nonexistent hour. The solution is to schedule jobs with absolute time dependencies for the missing hour to start within the first minute of the 3:00 DT hour. For example, a job scheduled to run on Sundays at 2:05, will run at 3:00:05 that day; a job scheduled to run everyday at 2:45 will run at 3:00:45. Although it might not be possible to start a large number of jobs within the first minute of the hour, this feature does somewhat preserve the scheduling order. If you scheduled a job to run more than once during the missing hour, for example, 2:05 and 2:25, only the first scheduled job would run. Any additional start times for the same job in the missing hour will be ignored. Relative time dependencies, such as start_mins, will run as you would expect. For example, a job specified to run at 0, 20, and 40 minutes after the hour will be scheduled for 1:00 ST, 1:20 ST, 1:40 ST, 3:00 DT, 3:20 DT, and 3:40 DT. Relative interval calculations, such as max_run_alarm, min_run_alarm, term_run_time, and watch_interval are still calculated in minutes out from when the job started. For example, if our Sunday at 2:05 job has a term_run_time of 90 minutes, the job will start shortly after 3:00, the term_run_time will be at 4:30. Therefore, the behavior between two jobs that appear to have the same times specified, but use start_times versus start_mins, will not be the same. For example, job “Jrel” has start minutes of 10 and 20 minutes after the hour, and job “Jabs” has start times of 1:10, 1:20, 2:10, 2:20, 3:10, and 3:20. “Jrel” will run at 1:10, 1:20, 3:10, and 3:20. “Jabs” will run at 1:10, 1:20, 3:00, 3:10, and 3:20.

Job Attributes

4–29

Date and Time Attributes and Time Changes

Run Windows Run windows are treated a bit differently. If the specified closing of the run window falls within the missing hour, its recalculated closing time will be bumped up an hour, so that the effective duration of the run window remains the same. For example, a run window of 1:00 - 2:30 will have the closing time move to 3:30, so that the run window still remains open for an hour and a half. If the specified opening of the run window falls within the missing hour, its opening time is moved to 3:00. The closing time does not get altered, therefore the run window is foreshortened. For example, a run window of 2:45 - 3:45 will become 3:00 - 3:45, and the actual run window elapsed time will be 15 minutes shorter. If both the specified opening and closing of the run window is within the missing hour, its opening time is moved to the first minute after 3:00, and its closing time is pushed forward one hour. Therefore, the resultant run window may be lengthened. For example, a run window of 2:15 - 2:45 will become 3:00 3:45, or 15 minutes longer.

4–30

User Guide

but have other dependencies. For example.Date and Time Attributes and Time Changes Fall Time Change During the change from daylight saving to standard time in the fall. the job would normally be terminated at 2:30. and watch_interval are still calculated in minutes out from when the job started. and so on (as shown in the following illistration). Relative interval calculations. or Standard Time hour. a job scheduled to run on Sundays at 1:05. will run only at the second 1:05. such as max_run_alarm. then again at 1:00 ST and 1:30 ST. A job scheduled to run every 30 minutes will run at 1:00 DT and 1:30 DT. Jobs with start_mins settings will run in both hours. and has a term_run_time of 120 minutes. Job Attributes 4–31 . there are two “1:00-1:59” hours. it will terminate at 1:30 Standard Time. Jobs with start_times set between 1:00 and 1:59 will run only in the second. if a job is scheduled to run on Sunday at 0:30. term_run_time. min_run_alarm. On the day of the fall time change. For example. Standard Time 1:00 2:00 3:00 4:00 start_time attribute runs in second hour start_mins attribute runs in both hours 0:00 1:00 Daylight Savings Time 1:59 Jobs that are not time-based. which is 120 minutes after the job started. will still run during the first hour.

if the job also had a start time of 1:15.m to 2 a. or first hour. and the job would not run on the day of the time change.Date and Time Attributes and Time Changes Testing the Fall Time Change During the fall time change from Daylight Savings time to Standard Time. a run window of 11:30 . it will close during the daylight saving. If the specified opening of a run window is before the time change. This may be a problem if there are also associated start times on the job which occur during the repeated hour.1:30 will have the closing time of 1:30 DT. the start time would be calculated for 1:15 ST. you must set the clock to a time before 1 a.m. The closing time does not get altered. For example. window. your operating system automatically falls back one hour from 2 a. therefore the length of the run window will remain the same. which means that the run window remains open for its specified two hours. a run window of 1:45 . For example. In the example above. Standard Time hour. or the same hour in length. 4–32 User Guide .m. the run window will be open during the second. When testing this time change. the system will assume that the time change has already occurred and will not reset at 2 a.m. and its specified closing falls within the repeated hour. not 1:30 ST. causing the hour from 1 a.m. and allow the entire hour to pass before you can observe the time change.m. to 2 a.2:45 will become 1:45 ST to 2:45. If both the specified opening and closing of the run window is within the repeated hour. Standard Time hour. If the specified opening of the run window falls within the repeated hour. If you manually set the time to a period within the 1 a. its opening time is moved to the second. Run Windows Run windows are treated a bit differently.m to be repeated. to 1 a.m..

Jobs in a box will start only if the box itself is running. a box will return a status of SUCCESS only when all the jobs in the box have run and the status of all the jobs is “success.Chapter 5 Box Job Logic This chapter explains how box jobs work.m. you could put all these jobs in a box and assigning a daily start condition to the box. several examples of box job definitions and job streams are provided in Examples.. the box remains in RUNNING state. For example. Use boxes to group jobs with like scheduling parameters.” Default SUCCESS is described in Default Box Success and Box Failure. not as means of grouping jobs organizationally. However. Default Box Job Behavior Some important rules to remember about boxes are: ■ ■ ■ Jobs run only once per box execution. To illustrate box logic. Basic Box Concepts A box is a container of jobs with like starting conditions (either date/time conditions or job dependency conditions). Boxes should be used primarily for jobs with the same starting conditions. It also explains what types of jobs should and should not be placed in a box. By default. including default box behavior and how to override the default behavior. if you have a number of jobs that run daily at 1:00 a. ■ ■ Box Job Logic 5–1 . A box used to group sequential jobs is limited to 1. a variety of account processing jobs with diverse starting conditions should not be grouped in the same box. the box cannot complete until all jobs have run. As long as any job in a box is running.000 jobs.

Be aware that placing jobs in a box to achieve this end may bring undesired behavior due to the nature of boxes. Avoid the temptation to put jobs in a box as a short cut for performing events (such as ON_ICE or ON_HOLD) on a large number of jobs at once.” Default FAILURE is described in Default Box Success and Box Failure. Changing the state of a box to INACTIVE (the sendevent command) changes the state of all the jobs in the box to INACTIVE.Basic Box Concepts ■ By default. see Box Job Attributes and Terminators. a box will run indefinitely until it reaches a status of SUCCESS or FAILURE. For a description of how to override this behavior. ■ Unless otherwise specified. 5–2 User Guide . ■ When You Should Not Use a Box The fact that all jobs in a box change status when a box starts running has lead some to use boxes to implement “job cycle” behavior. a box will return a status of FAILURE only when all jobs in the box have run and the status of one or more of the jobs is “failure. You will most likely find that the default behavior of boxes inhibits the expected execution of the jobs you placed in the box.

you should not place jobs in a box solely because you want to run reports on all of them. (Some exceptions to this are explained in How Job Status Changes Affect Box Status. discussed later in this chapter. For example. The box remains in the RUNNING state as long as there are activated or running jobs in the box. you could get duplicate entries in your report. Note: Jobs in a box cannot start unless the box is running.) If a box changes to TERMINATED state. will list “acnt_job1” and “acnt_job2” a second time. the box completes with a status of SUCCESS. Box Job Logic 5–3 . you will get a report on the box and all the jobs in the box (unless you use the -L0 option). the status of that job will change directly from ACTIVATED to INACTIVE. What Happens When a Box Runs As soon as a box starts running. All jobs with no additional starting conditions are started. (Because of this. if you use wildcarding when specifying a job name. once the job starts running. jobs in boxes do not retain their statuses from previous box cycles. for example. The status of the box and the jobs in the box remain unchanged until the next time the box runs. thus. without any implied ordering or prioritizing.” If you specify acnt% as the job name for the autorep report. all the jobs in the box (including sub-boxes) change to status ACTIVATED. suppose you have a box named “acnt_box” containing three jobs named “acnt_job1. However.) Then each job is analyzed for additional starting conditions. if a user sends a KILLJOB event.” and “daily_rep. In addition.Basic Box Concepts Likewise. When you run autorep on a box. regardless of any later state changes of jobs within the box. the report will have an entry for the box “acnt_box” and an entry for each job in the box. Jobs with additional starting conditions remain in the ACTIVATED state until those additional dependencies have been met. Then autorep will continue searching for all job names matching the wildcard characters and. If a box is terminated before a job in it was able to start. meaning they are eligible to run. Once all the jobs in a box have completed successfully. it will continue to run even if the box is later stopped for some reason. it will stay in TERMINATED state until the next time it is started.” “acnt_job2.

a box named “simple_box” contains three jobs: “job_a. Because no contingency conditions have been defined. namely that all jobs in the box ran.” “job_b. After “job_b” completes successfully. 5–4 User Guide . they will start running. all jobs change to state ACTIVATED. Because “job_a” and “job_b” have no additional starting conditions. If “job_b” fails. the box completes with status of SUCCESS. “job_c” will not start. it will remain in ACTIVATED state. “simple_box” will continue running indefinitely. When “job_c” completes successfully. “job_c” will start.Basic Box Concepts Simple Box Job In this example. the starting condition for “job_c” is the success of “job_b.” and “job_c.” job_a simple_box job_b SUCCESS job_b job_c When “simple_box” starts running. waiting for the default completion criteria to be met.” “job_a” and “job_b” have no starting conditions.

otherwise the default failure conditions are applied.Box Job Attributes and Terminators Box Job Attributes and Terminators The following sections describe how to use various job attributes to control the behavior of box jobs and their contained jobs. be careful that you do not define conflicting success and failure conditions. they determine what conditions must be met to put the box in a state of SUCCESS or FAILURE. assume you defined the following success condition for “simple_box”: box_success: success(job_a) If “job_a” runs successfully. When overriding default box terminators. and “job_b” is still running. Attributes in a Box Job Definition Two box job attributes override the default success or failure of a box. Box Job Logic 5–5 . If you specify conditions for success of a box you should also specify failure conditions. “job_c” would pass from ACTIVATED state directly to INACTIVE state without ever running because the box it is in would no longer be running. Example of a Non-Default Success Condition Using the above simple box example. If included in a box job definition. They are box_success and box_failure.

If you use this attribute. you should not define more than one time attribute for any job in a box because the job will only run the first time. see the figure in Using the Job Terminator Attribute in this chapter. 5–6 User Guide . see the figure in Using the Box Terminator Attribute in this chapter. For more information. They are box_terminator and job_terminator. you must assign multiple start time conditions to the box itself. If you want every job in a box to terminate upon box failure. Time Conditions in a Box Each job in a box will run only once per box execution. Therefore. and define no time conditions for the job. but you also want it to run more than once. The job_terminator: y attribute specifies that if the box the job is in fails. The box_terminator: y attribute specifies that if the job fails.Box Job Attributes and Terminators Attributes in a Job Definition There are two attributes you can add to the definition of a job within a box to force either the job or the box to stop running. this job will terminate. the next time the box starts the job will start immediately. Do not assign a start time for a job in a box if the box will not be running at that time. the box the job is in should terminate. For more information. If you want to put a job in a box. If you do. you must add this attribute to every job definition. Remember also that the box must be running before the job can start. be sure you have defined conditions for the other jobs in the box in the event that the box is terminated.

” and the status of the box will be RUNNING. which causes “job_a” to start running. “job_report” will still be ACTIVATED waiting for the success of “job_a.m. Box Job Logic 5–7 . if “job_a” fails. “job_a” is defined to run repeatedly until it succeeds. Daily job_a run until succeed job_report success(job_a) Report success of job_a At 3:00 a. because jobs run only once per box execution.. it will not be able to run again until the next time the box starts. The box will remain in this state indefinitely. “job_report” has one starting condition—the success of “job_a. However. “bx_stat” starts running. If “job_a” is successful.” bx_stat 3:00 a.m.Box Job Attributes and Terminators The following illistration shows a scenario that would not work properly if placed in a box. “job_report” runs and all goes as expected.

5–8 User Guide . as shown in the following example. “report_stats” would still not start because the box it is in is not running. The command has the form: sendevent -E FORCE_STARTJOB -J job_name You can also execute this by selecting the Force Start Job button in the Job Activity Console. the state of the box influences whether or not other jobs in the box will run as expected. bx_report 3:00 a. the “bx_report” box job will terminate because “run_stats” has a box_terminator attribute.” and it completes successfully.m.Box Job Attributes and Terminators Force Starting Jobs in a Box The FORCE_STARTJOB command forces a job to start even if its starting conditions have not been met. If you force start “run_stats. The next section discusses how job status changes influence the status of the container box. if the job “run_stats” fails. Daily job_Fwatch run_stats success (job_Fwatch) box_terminator: y Run Statistics report_stats success (run_stats) Watch for file Report Statistics In the previous figure. If you force start a job in a box.

Box Job Logic 5–9 . consider an INACTIVE box that contains four jobs. the status of the box will be evaluated again according to the success or failure conditions assigned to the box (either the default or user-assigned). Any jobs in the box with a status of INACTIVE are ignored when the status of the box is being reevaluated. If one of the jobs is force started and completes successfully. dependent jobs are not affected. If a box contained only one job. the status change could trigger the job to start.Box Job Attributes and Terminators How Job Status Changes Affect Box Status If a box that is not running contains a job that changes status. as a result of a FORCE_STARTJOB or CHANGE_STATUS event. and the job changed status. all with a status of INACTIVE (this is typical of a newly created box). A change of status of the box could trigger the start of downstream jobs that are dependent on the box. the new job status could change the status of its container box. the box status would change as shown in the following table: Current Box Status SUCCESS SUCCESS FAILURE FAILURE INACTIVE INACTIVE TERMINATED New Job Status TERMINATED or FAILURE SUCCESS SUCCESS FAILURE SUCCESS TERMINATED or FAILURE any change New Box Status FAILURE Box status does not change SUCCESS Box status does not change SUCCESS FAILURE Box status does not change If another job is dependent on the status of the box. the status of the box will change to SUCCESS even though none of the other jobs ran. If the box status does not change. For example. If the box contains other jobs in addition to the job that changed status.

” This job has a box_terminator attribute.Examples Examples Spend some time studying the examples in this section. The logic of this job flow is as follows: ■ The box job named “bx_daily_update” has date and time conditions specified for its starting conditions. It is defined as being inside “bx_daily_update. The command job named “job_run_stats” runs statistics on the updated files. ■ ■ 5–10 User Guide . if this job fails. it runs every day of the week at 3:00 a.m. therefore.” It will run only on the successful completion of the job named “job_update. the box containing this job will be terminated. This job has a box_terminator attribute.” It will run as soon as “bx_daily_update” starts because it has no other starting conditions. The command job named “job_update” updates a set of files. They will help explain the logic of job flow in a box and reduce your chances of creating unexpected box behavior. conditions are defined to address different situations where the box might complete with a FAILURE status. It is defined as being inside “bx_daily_update. the box containing this job will be terminated. Advanced Conditions in Box Jobs In the following example. therefore. if this job fails. This box contains three command jobs whose overall purpose is to update files and generate a report.

Examples ■ The command job named “job_report_stats” reports on the statistics generated by “job_run_stats.” It is defined as being inside “bx_daily_update. ■ The following illistration shows this job stream: bx_daily_update 3:00 a. daily job_update box_terminator: y Update files SUCCESS job_update FAILURE job_update job_run_stats success (job_update) box_terminator: y Run statistics SUCCESS job_run_stats FAILURE job_run_stats job_report_stats success(job_run_stats) Report Statistics SUCCESS job_report_stats FAILURE job_report_stats SUCCESS bx_daily_update FAILURE bx_daily_update job_trigger_msg failure (bx_daily_update) Page operator SUCCESS job_trigger_msg Box Job Logic 5–11 .” The command job named “job_trigger_msg” has a job dependency condition specified for its starting parameter.m. It will run only on the FAILURE of the box job named “bx_daily_update.” This job will page an operator in order that the problem is investigated.” It has a job dependency condition specified for its starting parameter. It will run only on the successful completion of the job named “job_run_stats.

its only starting condition is the success of “run_stats. it has no other starting conditions so it starts as soon as the box starts running.” No conditions for success or failure of the box have been defined. That is. “run_stats” runs statistics. its only starting condition is the success of “update_accounts. It contains three jobs. “update_accounts” updates files.Examples Default Box Success and Box Failure The box job “do_statistics” runs every day at 3:00 a. box failure is when all jobs in the box have run and at least one has failed. The following illistration shows this job stream logic: Job Stream Job status update_accounts FAILURE SUCCESS run_stats success(update_accounts) FAILURE ACTIVATED SUCCESS report_stats success(run_stats) FAILURE ACTIVATED ACTIVATED SUCCESS Box SUCCESS Box FAILURE Box Still RUNNING Box Still RUNNING 5–12 User Guide .” “report_stats” reports statistics. The box will remain in the RUNNING state until all jobs in the box have run.m. therefore the default conditions are applied. box success is when all jobs in the box have run and successfully completed.

Examples Explicit Box Success and Box Failure The following illistration showsm a box success and failure: Job Definitions do_statistics 3:00 a.m. Daily box_success: success(update_accountes) AND success(run_stats) AND success (report_stats) box_failure: failure(update_accounts) OR failure(run_stats) OR failure(report_stats) update_accounts Update Files run_stats success(update_acco unts) Run Statistics report_stats success(run_stats) Report Statistics Job Stream do_statistics Job status update_accounts FAILURE SUCCESS run_stats FAILURE INACTIVE SUCCESS report_stats FAILURE INACTIVIE INACTIVE SUCCESS Box SUCCESS FAILURE FAILURE FAILURE Box Job Logic 5–13 .

m. Daily daily_receipts box_terminator: y Process Receipts daily_payables box_terminator: y Process Payables daily_balance success(daily receipts) AND success(daily_payables) Calculate Balance Job Stream daily_accounts daily_receipts daily_payables SUCCESS FAILURE SUCCESS FAILURE Box TERMINATED SUCCESS TERMINATED daily_balance 5–14 User Guide .Examples Using the Box Terminator Attribute The following illistration uses box_terminator: Job Definitions daily_accounts 3:00 a.

m. Daily daily_receipts Process Receipts daily_payables job_terminator: y Process Payables daily_balance success(daily receipts) AND success(daily_payables) Calculate Balance Job Stream daily_accounts daily_receipts daily_payables TERMINATE SUCCESS SUCCESS FAILURE FAILURE FAILURE Box FAILURE daily_balance Box Job Logic 5–15 .Examples Using the Job Terminator Attribute The following illistration uses job_terminator: Job Definitions daily_accounts 3:00 a.

January 1). First Day of Month success(job_Fwatch) Re-index. First Day of month term_run_time:90 Watch for File job_monthly 2:00 a.m.m. Organize. statuses behave as expected.Examples Advanced Job Streams Scenario On the First of the Month The first time cycle is run (for example. Purge job_daily 3:00 a. Job Definitions job_Fwatch 1:00 a. Daily success(job_monthly) Generate Report Job Stream Date/Time Conditions Met Job Dependency Condition Met Start job_monthly Event Status in AutoSys Database= SUCCESS Start job_Fwatch File from Mainframe SUCCESS Date/Time Conditions Met SUCCESS Job Dependency Condition Met job_daily Date/Time Conditions Met SUCCESS 5–16 User Guide .m.

As a result. They still have a status of SUCCESS in the database from the previous run on the first of the month.m. First Day of Month success(job_Fwatch) Re-index. Organize. Job Definitions job_Fwatch 1:00 a. First Day of month term_run_time:90 Watch for File job_monthly 2:00 a.m.m.Examples Scenario On the Second of Month On days of the month other than the 1st. “job_daily” will still run. “job_Fwatch” and “job_monthly” do not run. Daily success(job_monthly) Generate Report Job Stream NOT RUN Date/Time NOT Conditions Met Job Dependency Condition NOT Met NOT RUN Date/Time NOT Conditions Met job_Fwatch File from Mainframe job_monthly X Start job_daily SUCCESS Event Status in AutoSys Database= SUCCESS (from Jan 1) Job Dependency Condition Met Date/Time Conditions Met Box Job Logic 5–17 . Purge job_daily 3:00 a.

and as a result. However.m. Purge job_daily 3:00 a. “job_monthly” does not run for the month. Organize. Daily success(job_monthly) Generate Report Job Stream Date/Time Conditions Met Job Dependency Condition NOT Met Start job_Fwatch term_run_time: 90 TERMINATED NOT RUN job_monthly File from Mainframe Date/Time Conditions X job_daily SUCCESS Event Status in AutoSys Database= SUCCESS (from Jan 1) Job Dependency Condition Met Start Date/Time Conditions Met Undesirable Result 5–18 User Guide . “job_daily” runs in error. February 1). Job Definitions job_Fwatch 1:00 a. its event status in the database is still SUCCESS from the previous month. the file from the mainframe fails to arrive.m. therefore. First Day of Month success(job_Fwatch) Re-index.m. First Day of month term_run_time:90 Watch for File job_monthly 2:00 a.Examples Scenario I On First of the Month On the first of the next month (for example.

m. First Day of Month success(job_Fwatch) Re-index. Daily success(job_monthly) Generate Report At 1:00 a. Organize. Job Definitions job_Fwatch 1:00 a. You can create another job to do this automatically. you can use a sendevent command to change them to INACTIVE at the end of their valid time period. issue a CHANGE_STATUS on "job_monthly" using GUI Send Event dialog or by issuing the following command: sendevent -E CHANGE_STATUS -S INACTIVE -J job_monthly Job Stream Date/Time Conditions Met Start job_Fwatch File from Mainframe Job Dependency term_run_time: 90 Condition NOT Met TERMINATED NOT RUN Date/Time Conditions job_monthly X job_daily Event Status in AutoSys Database= INACTIVE Job Dependency Condition NOT Met NOT RUN Date/Time Conditions Met Desirable Result Box Job Logic 5–19 . First Day of month term_run_time:90 Watch for File job_monthly 2:00 a.m. Purge job_daily 3:00 a. on first day of month.m.m.Examples Scenario II On First of the Month To fix statuses that are time-related.

and set box_failure or box_terminator appropriately.Examples Scenario III On First of the Month Instead of issuing a sendevent command to change the status of the jobs. Purge job_daily 3:00 a.m. Organize.m. you could put the monthly process in a box. First Day of Month box_terminator: y Watch for File job_monthly success(job_Fwatch) job_terminator: y Re-index. box_monthly job_Fwatch 1:00 a. Daily success(box_monthly) Generate Report box_monthly Date/Time Conditions Met Start job_Fwatch File from Mainframe SUCCESS job_monthly SUCCESS TERMINATED Job Dependency Condition Met Job Dependency Condition NOT Met job_daily NOT RUN Date/Time Conditions Met Start Date/Time Conditions Met job_daily SUCCESS 5–20 User Guide .

You can access these components from the GUI Control Panel. Starting the GUI Control Panel To start the GUI Control Panel: Open the graphical interface from its icon in the program group. and manage jobs. This action opens the GUI Control Panel: Introduction to the Graphical User Interface 6–1 . monitor.Chapter 6 Introduction to the Graphical User Interface The GUI refers to a set of windows and dialogs that you can use to define. This chapter provides an introduction to the Graphical User Interface (GUI) components. which is also described in this chapter.

Exit Closes all of the Graphical User Interface windows and dialogs. 6–2 User Guide . GUI Control Panel Menu Bar The GUI Control Panel has the following menus: ■ ■ ■ ■ File Tools Preferences Help File Menu The File menu contains the following options: Iconize All Minimizes all the open Graphical User Interface windows and dialogs.Using the GUI Control Panel Using the GUI Control Panel The GUI Control Panel has a menu bar and several buttons. as well as the GUI Control Panel.

which you can use to send events. For more information. The No Alarm Color is used in the Alarm Sentry to indicate there are no alarms for the instance. then select this option. as well as cancel those previously sent events.Using the GUI Control Panel Tools Menu The Tools menu contains the following options: Send Event Opens the Send Event Tool. After the specified number of tries. In the DB Retry Count field. and you must close and restart the GUI component to restart the retry count. Event Report Opens the Job Detail Report tool. which displays an event or summary report for a job. or Alarm Manager windows. and Alarm Manager. you must first close all GUI windows and dialogs. the GUI stops trying to connect. you can specify the number of times each GUI component tries to connect to the database.” in this guide. If you want to remove all user settings and return to the default settings. see the topic Using the Job Detail Report Tool in the chapter “Scheduler Console. which you can use to set the DB Retry Count and the Alarm Color.” in this guide. Opened from the GUI Control Panel. Preferences Menu The Preferences menu contains the following options: General Opens the General dialog. The Alarm Color setting is used to indicate alarms in the Scheduler Console. Introduction to the Graphical User Interface 6–3 . Remove All User Settings Removes all user settings for closed windows and dialogs. For more information about the Job Detail Report tool. which you can use to view comprehensive information about the most recent run (or the current run) of a job.” in this guide. and Alarm Manager. see the topic Using the Run Status Tool in the chapter “Scheduler Console. the Run Status Tool displays the job selected in the Scheduler Console. Run Status Tool Opens the Run Status Tool. see the topic Using the Send Event Tool in the chapter “Scheduler Console. For more information about the Run Status Tool. Alarm Sentry. the Job Detail Report tool displays the job selected in the Scheduler Console. Opened from the GUI Control Panel.

Calendar Editor Displays the Calendar Editor window. 6–4 User Guide . For information. see the chapter “Scheduler Console. which indicates if there is an alarm for any instance you are monitoring.” in this guide. For information. see the chapter “Monitoring and Reporting on Jobs. Job Editor Displays the Job Editor. For information. which lets you define jobs.” in this guide. see the chapter “Managing Alarms. which lets you monitor jobs and alarms across multiple instances. see the chapter “Calendar Editor.” in this guide. see the chapter “Managing Alarms.” in this guide. Monitor/Browser Editor Displays the Monitor/Browser Editor.” in this guide. For information. GUI Control Panel Buttons These are the Control Panel buttons and the actions they perform: Scheduler Console Displays the Scheduler Console. which lets you define run and exclude calendars. For information. For information.Using the GUI Control Panel Help Menu The Help menu contains the following options: About Displays GUI Control Panel version number. which lets you define and run monitors and reports (or browsers). which lets you view and respond to alarms across multiple instances. Alarm Manager Displays the Alarm Manager application. see the chapter “Defining Jobs Using the Job Editor. Alarm Sentry Displays the Alarm Sentry dialog.” in this guide.

Exit Exits the GUI Control Panel. For more information on the Admin GUI. and shadow event processors. which lets you implement several advanced configurations.Using the GUI Control Panel Admin GUI Displays the administration dialog. dualevent servers. see the chapter “Administrator” in this guide. Introduction to the Graphical User Interface 6–5 . including cross-instance job dependencies.

.

are discussed in detail in the chapter “JIL/GUI Job Definitions. Note: Not all of the Job Editor fields are described in this chapter.Chapter 7 Defining Jobs Using the Job Editor This chapter provides a description of the Job Editor interface and its use. along with the Name and Instance. the Job Editor opens in command job format. but the fields. If you want to define a file watcher or box job. file watcher. modify. To open the Job Editor: Click Job Editor in the GUI Control Panel. choose New from the File menu. and delete job definitions for command. Starting the Job Editor Use the Job Editor to create. based on their corresponding job attributes. Defining Jobs Using the Job Editor 7–1 . By default. in the New Job dialog.” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. and indicate the Job Type. and box jobs.

7–2 User Guide . as the following illistration shows.Starting the Job Editor The Job Editor opens for a command job.

Save Stores the currently displayed job in the database. and it is terminated with white space (embedded white space is invalid). Defining Jobs Using the Job Editor 7–3 . a tabbed area. click OK to open the appropriate Job Editor display for the new job. which you can use to search for existing job definitions. this option displays the Save As dialog. wildcard character. Job names cannot have the same names within an instance. File Menu The File menu includes the following options: New—Displays the New Job dialog in which you enter the name of the job. file watcher job. either modifying a preexisting job or creating a new definition. The Job Editor displays different tabs and fields based on whether you are defining a command job. or box job. and a status area.Using the Job Editor Interface Using the Job Editor Interface The Job Editor has a menu bar. The default % filter displays a list of all job names. The Job Editor shown in the previous figure is based on a command job. Box. After you indicate the required information in the New Job dialog. When you save a new job definition. It must be from 1 to 64 alphanumeric characters. and Help. ■ Open Displays the Open dialog. Job Type can be a Command. In the Pattern field of this dialog. You can also enter Job Name and click OK. Edit. and then click Search to display a list of those jobs with names that include the string. the instance to which you are defining it and the job type as follows: ■ Name must be unique to the instance. The number of and type of tabs that are displayed are based on the type of job you are defining. Options. but they can have the same name as a calendar definition in the instance. you can specify any string. including the percent (%). Job Editor Menu Bar The Job Editor menu bar includes the following menus: File. or File Watcher job.

Delete Displays a Delete dialog. you can keep the same job definition name. You can also access this option from the Add One-time Override button on the Basic Scheduling tab. and they are for the next run only. empty Job Editor window. New Job Editor Displays a new. if desired. It disables all other fields. Exit Closes the Job Editor. but maintains the current job name.Using the Job Editor Interface Save As Displays the Save As dialog in which you can enter the Instance to which you want the definition saved and the new name for the job definition. 7–4 User Guide . This option is enabled only if there are one-time overrides defined for the job. which you can use to search the database for all job definitions. Edit Menu The Edit menu contains the following option: Clear Clears the Job Editor without affecting the database. If you are saving the definition to another instance. Delete Overrides Deletes overrides defined for the current job. and then select the definitions that you want to delete. You can apply one-time overrides to a job. You can also access this option from the Delete Override button on the Basic Scheduling tab. and when you use any of the dialogs to connect to another instance. Note: When you first open a Job Editor. AutoSys establishes a connection to that instance’s database and maintains that connection until you close the Job Editor. Add Overrides Enables the fields in the Job Editor that you can modify for onetime overrides.

Defining Jobs Using the Job Editor 7–5 . Job Editor Tabs The Job Editor displays all or part of the following tabs. alarm behavior. Misc Contains the settings for job restart. If you toggle this option to off. and it contains job-specific execute and edit permissions. When you select a job from the Scheduler Console or Alarm Manager. Date/Time Contains the date and time start-job condition and contains the time zone setting. delete job after completion. depending on what job type you are defining: Basic Contains the job description and basic job attribute fields. you can specify any run or exclude calendars for the job. Instead of setting specific date and time starting conditions. and the box terminator settings. and automatic hold for jobs in a box job. the open Job Editor updates to reflect the selected job. About Displays the Job Editor version number. the open Job Editor does not update.Using the Job Editor Interface Options Menu The Options menu contains the following option: Adopt Session Context Toggles the session context feature on and off. Alarms/Terminators Contains the minimum and maximum runtime. Help Menu The Help menu contains the following option: Contents Displays the Contents of the Unicenter AutoSys JM Help. The default setting is to have Adopt Session Context on (checked).

Required Values for Command Jobs In addition to the Name. each job type requires that you set specific attributes. of the Job Editor lists the fields that require values for the job type you are defining. That is. Job Type. You indicate the Name and Job Type when you open a new Job Editor. or when you save a job definition. Machine Indicates the client machine on which to run the job. The job Owner must have permission to access this machine and to execute the specified command at this machine. each Job Type requires a set of values. you must use the syntax appropriate to the operating system of the client machine on which the job will run. Resource/Profile Contains the resource check and the path to the job profile settings. 7–6 User Guide . and Owner. All jobs require a Name. or status area. heartbeat interval.Using the Job Editor Interface Command Info Contains the queuing and load balancing. and Owner. The job Owner must be able to log on to the specified client Machine and have operating system permissions to execute the specified command. and file redirect settings. In addition. exit code. and those attributes are listed in the status area of the window. the status area indicates syntax errors and other problems with the job definition. Job Editor Status Area The bottom portion. When issuing commands that are to run on a different operating system. The Owner of the job is defined as the logged-on user who started the AutoSys GUI. you must supply the following values for command jobs on the Job Editor Basic tab: Command Indicates the command to run. Job Type. In addition.

the owner must have a user account on the machine. and Owner are the only required values for box jobs. Job Type. and Owner. File to watch Indicates the name of the file to watch for. For jobs running on Windows machines. and the associated logon ID and password must be entered into the database (using the autosys_secure command). which indicate when a file has arrived. The job Owner must have permission to access this machine and to execute the specified command at this machine. This must be a legal filename and full path to the file. you must supply the following values for file watcher jobs on the Job Editor Basic tab: Machine Indicates the client machine on which to run the job.Using the Job Editor Interface Required Values for Box Jobs Name. Required Values for File Watcher Jobs In addition to the Name. Defining Jobs Using the Job Editor 7–7 . Job Type. Note: You can use the File to watch setting in combination with the optional values Time Interval (in seconds) to determine steady state and Minimum file size (in bytes).

Note: In the Send to Machine field. if you are running with a shadow event processor. licensed client machine. In the Send to Machine field. In the GUI Control Panel. However. These are the steps to define a job named “test_run. Select localhost from the drop-down list. enter a machine name. and click OK. click Job Editor. In the Command field. In addition.Creating a Simple Command Job Creating a Simple Command Job This section describes how to define a basic command job. you should not use the localhost machine setting. Create the test_run example command job from the following: 1. for Windows. you must enter a valid. If you add a machine at this time. The Save As dialog opens. you should add your own machine name. when manually started. by doing one of the following: ■ ■ Click Add. it echoes a message to standard output. choose Save. enter the following command to be executed: echo AUTOSYS install test run 3. 7–8 User Guide . enter the machine on which the command will be executed. you must have a Windows user ID and password in the database for user@localhost (entered using the autosys_secure command). which specifies to run the job on the event processor machine. The Job Editor dialog opens for a command job. 4.” This job has no starting parameters. 2. From the File menu. If you use localhost. you must have already entered into the database a valid Windows user ID and password for the Owner’s user account on the machine.

Note: The Owner field for the job defaults to the currently logged-on user. Your entries in the Job Editor should look similar to those in the following illistration. 6. Click OK to dismiss the dialog.Creating a Simple Command Job 5. WARNING! For the host portion of the Owner field. select an Instance and enter the new job name: test_run Click OK. it does not use the Computer Name on the Identification tab of the Windows Control Panel Network dialog. Leave the Job Editor open and use it for the next example. The Instance is the instance that you chose in the Save As dialog. When the definition is written to the database. Defining Jobs Using the Job Editor 7–9 . In the Save As dialog. Unicenter AutoSys JM uses the Host Name on the DNS tab of the TCP/IP Protocol dialog. a confirmation dialog is displayed.

Instance. You must use a valid. enter the following time interval: 60 7–10 User Guide . This job will watch for an end-of-day transaction file called EOD_trans_file. event processor machine) or the machine you entered for the previous example. In the New Job dialog: a. enter this file name: c:\users\default\EOD_trans_file 4. Select the appropriate Instance.Creating a File Watcher Job Creating a File Watcher Job File watcher jobs do not actually execute commands. A New Job dialog opens. Select File Watcher from the Job Type drop-down list. In the File to watch field. 3. In the Time Interval (secs) to determine steady state field. in which you can enter the Name. Enter the following in the Name field: EOD_watch b. 5. 2. This section describes how to create a basic file watcher job. and it will have specific file watching criteria. Typically. To define a file watcher job: Follow these steps using the open Job Editor: 1. Click OK. New. A Job Editor opens for this file watcher job. and you must have already entered into the AutoSys database a valid Windows user ID and password for the Owner’s user account on the machine. c. d. In the Machine field. they signal the arrival of files. licensed client machine. select either localhost (that is. Choose File. file watcher jobs are used to initiate the execution of command jobs. and Job Type.

8. the file must reach 50000 bytes and be in a “steady state” before the file watcher job will complete with a SUCCESS status. a confirmation dialog is displayed. Note: The Owner field for the job defaults to the currently logged-on user.” 6. it is considered to be in a “steady state. which opens the Save As dialog. Save. When the definition is written to the database. Click OK to dismiss the dialog. The Instance is the instance that you chose in the New Job dialog. If the file has not changed in size. 7. To save the job. Leave the Job Editor open to use in the next example. Defining Jobs Using the Job Editor 7–11 . choose File. Your entries in the Job Editor should look similar to those in the following illistration. and it will check if the file has grown between checks. In the Minimum file size (in bytes) field. and click OK. Therefore.Creating a File Watcher Job This setting indicates that Unicenter AutoSys JM will check for the file’s existence every 60 seconds. enter the following: 50000 This setting indicates the minimum file size that should be reached before the file can be considered complete.

3. enter the starting condition. 4. In the New Job dialog: a. A New Job dialog opens. 5. Unlike the simple command job you created earlier. Enter the following in the Name field: EOD_post b. in which you can enter the Name. assume that the environment variable %HOMEPATH% means that the post executable is located in the job owner’s home directory. You must use a valid. select either localhost (that is. and you must have already entered into the database a valid Windows user ID and password for the Owner’s user account on the machine. this command job is dependent on another job. In the Machine field. licensed client machine. New. d.exe In this example. Leave the default Command setting for the Job Type. In the Dependencies field. In the Command field. in this case the successful completion of the file watcher job: S(EOD-watch) Note: If you want to add a list of Dependencies. To create a command job with dependencies: Follow these steps using the open Job Editor: 1. Choose File. Click OK. c. for example: %HOMEPATH%\post. Select the appropriate Instance. you can click the button to the right of the field and enter the job dependencies in the Conditions dialog. and Job Type. event processor machine) or the machine you entered for the first example. A Job Editor opens for this command job. enter the command that runs when the file watcher completes. Instance.Creating a Dependent Command Job Creating a Dependent Command Job This section describes how to create a command job that is dependent on the successful completion of the file watcher job you just created. 2. 7–12 User Guide .

which opens the Save As dialog. Note: The Owner field for the job defaults to the currently logged-on user. When the definition is written to the database. and click OK. Choose File. Leave the Job Editor open to use for the next example. Note: On Windows.Creating a Dependent Command Job 6. The profile you indicate is used to set the variables immediately before the job is started. The Instance is the instance that you chose in the New Job dialog. If you want to set the User Variables or any other variables for the job. Save. The Job Editor should look similar to the following illistration. but it does not include the Windows User Variables. a confirmation dialog is displayed. Click OK to dismiss the dialog. Then you must indicate the appropriate profile on the Job Editor Resource/Profile tab in the Job Environment Profile field. 7. the job’s execution environment automatically includes Windows System Variables and specific environment variables. you must define them in an job profile using the Job Profiles Manager. Defining Jobs Using the Job Editor 7–13 .

In the Dependencies field. enter the following starting condition.” in this guide. see the chapter “Box Job Logic. For detailed information on box jobs. c. Select the appropriate Instance. if you wanted to schedule a group of jobs to start running after a file watcher job completes successfully. This section describes how to do the following: ■ ■ Create the EOD_box job Modify the EOD_post job that you just created to put it in the box and make it no longer individually dependent on the file watcher job. New. Choose File. The New Job dialog opens. and place all of the jobs in the box. From the Job Type drop-down list.Creating a Box Job Creating a Box Job A box job contains jobs with like starting conditions. select Box. Creating the EOD_box Box Job To define a box job: Follow these steps using the open Job Editor: 1. Enter the following in the Name field: EOD_box b. Click OK. d. For example. 2. Instead of making each individual job dependent on the file watcher job. In the New Job dialog: a. A Job Editor opens in which you can define this box job. 3. you could create a box job to contain those jobs. you create a box job that is dependent on the file watcher. which is the successful completion of the file watcher job: S(EOD-watch) 7–14 User Guide .

5. Note: The Owner field for the job defaults to the currently logged-on user. Defining Jobs Using the Job Editor 7–15 . The Job Editor should look similar to the following illistration. and then click OK. Choose File. a confirmation dialog displays. Save. Click OK to dismiss the confirmation dialog.Creating a Box Job 4. Leave the Job Editor open. which opens the Save As dialog. The Instance is the instance that you chose in the New Job dialog. When the definition is written to the database.

you must ensure that the job is not running. enter the following in the Pattern field.Creating a Box Job Modifying the EOD_post Command Job This section describes how to modify the existing EOD_post job to remove its dependencies and place it in the EOD_box job you just created. to open an existing job. Typing just the % wildcard character will display all the jobs defined in the database. which you can use to search for and select existing job names. To modify the EOD_post job: Follow these steps using the open Job Editor: 1. you can enter some portion of the job name. In the Open Dialog. 7–16 User Guide . The names of the jobs you defined in this chapter should be displayed. as shown in the following illistration: Note: In the Pattern field. In addition. Click Search. The percent (%) character will match any string of one or more characters in the job name. followed by the percent (%) wildcard character. Note: Before you modify any job. Open. The Open dialog opens. EOD% 3. Choose File. 2. you can enter the full job name directly into the Job Name field and click OK.

Click OK to dismiss the confirmation dialog. select EOD_post and click OK. it will inherit the Dependencies (starting conditions) of that box. A Job Editor opens for this job. When you place this job in a box job.Creating a Box Job 4. 5. 8. The Box Selection dialog opens. Choose File. 6. enter EOD_box in the Box Name field and click OK. In the Job Editor. a confirmation dialog displays. Click the Search button next to the Box field. as shown following. Note: You can also enter the box job name directly into the Box field of the Job Editor. 9. Leave the Job Editor open. From the list of job names in the Open dialog. delete the Dependencies setting. placing the EOD_post command job in the box job. 7. When the job definition is written to the database. In the Box Selection dialog. Save. This box job is entered in the Job Editor Box field. Defining Jobs Using the Job Editor 7–17 .

days of the week. and times of the day. You can also assign a specific “run window. and it indicates the span of time during which the job will be allowed to start. click the tab. and the Time settings are on the right side.” The Run Window setting is in a 24hour format. you must select both a Day setting and a Time setting. To enable the fields. The Time Zone indicates that the selected time settings should be based on that particular “zone” setting. Unicenter AutoSys JM uses the time zone of the event server. you can set the Time Zone for the job. If you do not set a Time Zone for the job. In addition. To bring the Job Editor Date/Time tab to the front. The Day settings are on the left side of the dialog. as shown in the following illistration: After you enable the tab.Setting Date and Time Dependencies Setting Date and Time Dependencies You can use the Job Editor Date/Time tab to set starting conditions based on calendars. click the Date/Time Conditions check box. 7–18 User Guide .

you can set an Exclude Calendar in combination with either of these Date options. ■ To clear the selected days: Click None. or that it should not run on the days indicated in the calendar. you can indicate that a job should run on specific days of the week or on all days of the week. When you set Date conditions. you must also set Time conditions to indicate the time of day the job should run. Setting the Run Days Option You can define a job to run one or more days a week. They are exclusive settings. You can also use a custom calendar to indicate that a job should run on the days defined in the calendar.Setting Date and Time Dependencies Setting Days of the Week Starting Conditions When setting Date conditions. ■ To define your job to run on one or more days of the week: Select Run Days radio. and then click All. ■ To define your job to run on all the days of the week: Select Run Days radio. Note: You can set only one of the Run Days or Run Calendar Date options. However. Defining Jobs Using the Job Editor 7–19 . and then click the check boxes next to the days of the week on which you want the job to run.

The times you indicate in this field must be in a 24-hour format. and then select a calendar name from the Run Calendar drop-down list. ■ To define a job to run at a specific time of day: Select the Times of Day radio button and indicate the time of day in the field below it. Alternatively. you can specify a calendar that defines days on which the job must not run.Setting Date and Time Dependencies Setting Run Calendar and Exclude Calendar Options You can define jobs to run on specific dates. you must define a calendar by using the Calendar Editor. 7–20 User Guide . Separate multiple time settings with commas. on the days or dates on which the job is defined to run. ■ To define a job to use an existing calendar to not run on specific dates: Click Exclude Calendar radio. you must define a calendar. ■ To define a job to use an existing calendar and run on specific dates: Click Run Calendar radio. and then you set that calendar as the Exclude Calendar. To do this. or times. and then you set that calendar as the Run Calendar. For information on using the Calendar Editor. To do this. see the chapter “Calendar Editor. you must set a time starting condition. and then select a calendar name from the Exclude Calendar drop-down list. The time starting condition indicates that Unicenter AutoSys JM should run the job at that time. Setting Time Starting Conditions After you set the date condition. ■ To define a job to run at specific times past every hour: Select the Minutes after Each Hour radio button and indicate the number of minutes past that time in the field below. by using the Calendar Editor. ■ To modify an existing calendar or create a new calendar : Click Edit Calendars.” in this guide. rather than specific days of the week. This action opens the Calendar Editor.

the job will not run today but will run tomorrow at (12:00). When a start time job definition is written to the database within “one minute” of the current run time. To do this.Setting Date and Time Dependencies The minute values you indicate in this field must be a number between 1 and 59. Setting Time Zones You can base the time settings for a job on a specific time zone.” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. and click Apply. Note: If a job runs daily at the same time (example: 12:00) and you EDIT this job definition and save this job at (11:59). the start time will be placed in the future. The Every Minutes settings must be a number between 1 and 59. see timezone in the chapter “JIL/GUI Job Definitions. However. enter a minute setting in the Every Minutes field. meaning tomorrow. Defining Jobs Using the Job Editor 7–21 . This sets the minutes interval in the Minutes after Each Hour field. if the start time is two minutes or greater from the current save time the job will run today. enter a valid time zone in the Time Zone field (above the time settings on this tab). ■ To define a job to run at regular intervals past every hour: Select the Minutes after Each Hour radio button. You can use a comma-separated list to indicate more than one setting. For information on specifying a time zone in a job definition.

Select the Run Days radio button and single-click the Monday.m. Note: The times do not have to be enclosed in quotes when they are entered in the Job Editor. by using the Send Event Tool or the sendevent command. 7–22 User Guide . Click the Date/Time tab to bring it to the front. 5. Open. then enter the following times (in a 24 hour format) in the enabled field: 10:00. Select the Times of Day radio button. A Job Editor opens with the test_run job definition. 14:00 6. However. Wednesday. To modify the test_run job to add time and date dependencies: Follow these steps using the open Job Editor. Click the Date/Time Conditions checkbox to enable the fields on this tab. This section describes how to modify the job to run at 10:00 a. on Mondays. The Open dialog opens.Setting Date and Time Dependencies Example on Setting Date and Time Dependencies The “test_run” job you created at the beginning of the chapter can only be executed if it is started manually. and then click OK. 4.m. Choose File. 1. In the Open dialog. Save. Wednesdays. and Friday checkboxes. and 2:00 p. and Fridays. Choose File. 7. 2. they are not mutually exclusive. 3. unlike jobs entered using the Job Information Language (JIL). enter test_run in the Job Name field. you could define this job to run on certain days at certain times. A confirmation dialog is displayed to indicate the next start time. You can toggle the day check boxes on and off.

The Job Editor Time/Date tab should look similar to the following illistration. another confirmation dialog displays.Setting Date and Time Dependencies 8. After the definition is written to the database. Defining Jobs Using the Job Editor 7–23 . 9. Click OK to dismiss the second confirmation dialog. Leave the Job Editor open to use in the next example. Click OK to dismiss the confirmation dialog.

enter a name. You must select at least one job. 3. you must be either the owner of the job or the edit superuser. Delete. To select a continuous section of jobs. press Ctrl and click each job. Then. To delete a job definition. click a job. click it. Choose File. You can delete any jobs. To delete a job. A list of job names based on your search is displayed. Ensure that you are operating on the correct Instance. To select one job. 7–24 User Guide . press Shift and click the ending of the list. in the same way. 2. select one or more jobs to delete. or the “%” wildcard character. Click Search. To select several jobs in the list. From the list of job names. however. follow these steps using the open Job Editor: 1. regardless of type. in the Pattern field. The Delete Jobs dialog opens.Deleting Jobs Deleting Jobs You can use the Job Editor to delete job definitions from the database. It should look similar to the following illistration. partial name with the percent (%) wildcard character.

the job definition is written to the database (as if it is a new definition). For information on deleting box jobs with JIL. it will still be in the Job Editor. If you choose to save it. Currently. If you change any setting and try to open another definition. Note: If you have a job open. Defining Jobs Using the Job Editor 7–25 . Click OK to close the dialog and delete the jobs. and you delete it using the Delete Jobs dialog. Notes on Deleting a Box Job When using the Job Editor to delete a box job.” in this guide. 5. there is no way to delete just the box itself and not its contents when using the Job Editor. Unicenter AutoSys JM will delete the box and all jobs within that box. Click OK. A confirmation dialog displays. you are asked if you want to save the current (deleted) definition.Deleting Jobs 4. see Deleting a Job in the chapter “Defining Jobs Using JIL.

On the Basic Tab. The Job Editor fields that you can use in a job override definition are listed in tables in Enabled Job Editor Fields for One-time Overrides in this chapter. you can specify a onetime job override for the next run of a particular job. 7–26 User Guide . bring the Date/Time tab to the front and select one of the choices from the drop-down list. Enter new values into the fields. Setting Job Overrides To enter a onetime override: 1. 4. or enter NULL to turn off the set value. When the modified definition is written to the database. 5. Note: To specify a date or time override.Specifying One-Time Job Overrides Specifying One-Time Job Overrides Using the Job Editor. This action will enable the appropriate fields. Click OK to dismiss the dialog. if you specify an override. Use the Job Editor to specify overrides. Choose File. a confirmation dialog is displayed. the job definition and the job run behavior are changed only for the next time a job runs. click the Add One Time Override button. Open a job in the Job Editor. 3. That is. Turn on the override mode by doing one of the following: ■ ■ Choose File. Add Override. Both of these actions disable the fields that you cannot modify for one-time overrides. Save. 2.

Defining Jobs Using the Job Editor 7–27 . You cannot submit an override if it results in an invalid job definition. Note: The maximum number of job restarts after system or network failures is specified in the Max Restart Trys field on the Administrator event processor screen. The Job Editor fields that you can use in a job override definition are listed in tables in Enabled Job Editor Fields for Onetime Overrides in this chapter. If a RESTART event is generated because of system problems. the override is deleted.Specifying One-Time Job Overrides Notes on One-Time Overrides Job overrides are applied for the next run of the job only. Application failures include inability to read or write a file. System problems include machine unavailability. After this. and insufficient disk space. media failures. Onetime job overrides are applied to jobs that are restarted due to system problems. and not in the specified Time setting. and various syntax errors. but are not applied to jobs restarted because of application failures. For example. command not found. exit status greater than the defined maximum exit status for success. because removing only one of the Date/Time start condition makes the job definition invalid. or until the maximum number of retries limit is met. Unicenter AutoSys JM will re-issue a job override until the job actually runs once. the definition becomes invalid. if you enter NULL in the Times of Day field only.

Click Yes in this dialog to delete the defined overrides. 3. open the job for which you want to delete the overrides. Choose File. you must save it before you can delete the defined overrides.Specifying One-Time Job Overrides Deleting One-Time Overrides To delete the onetime job overrides: 1. Do one of the following: ■ ■ Click the Delete Override button on the Basic tab. Choose File. 2. In the Job Editor. Delete Overrides. Enabled Job Editor Fields for One-Time Overrides The tables in this section list the fields that are enabled for one-time overrides. When the job definition is written to the database. The following table lists the Job Editor fields for command job overrides: Tab Basic Fields ■ ■ ■ Command Dependencies Send To Machine All conditions. Both of these actions display a confirmation dialog. a confirmation dialog is displayed. Click OK to dismiss the dialog. except the Time Zone setting Minimum Run Time (Alarms) Maximum Run Time (Alarms) Terminate this job minutes after starting (Terminators) Date/Time Alarms/Terminators ■ ■ ■ ■ 7–28 User Guide . Save. Note: If the job is already open in the Job Editor.

Specifying One-Time Job Overrides Tab Misc Fields ■ ■ ■ Number of times to restart this job after failure Delete Job after completion AutoHold for jobs in boxes File to redirect standard input File to redirect standard output File to redirect standard error Job Environment Profile Command Info ■ ■ ■ Resource/Profile ■ The following table lists the Job Editor fields for box job overrides: Tab Basic Date/Time Alarms/Terminators Fields ■ ■ ■ ■ ■ Dependencies All conditions. except the Time Zone setting Minimum Run Time (Alarms) Maximum Run Time (Alarms) Terminate this job minutes after starting (Terminators) Number of times to restart this job after failure Delete Job after completion AutoHold for jobs in boxes Misc ■ ■ ■ Defining Jobs Using the Job Editor 7–29 .

Specifying One-Time Job Overrides The following table lists the Job Editor fields for file watcher jobs: Tab Basic Fields ■ ■ ■ ■ ■ File to watch Dependencies Send To Machine Time interval (secs) to determine steady state Minimum file size (in bytes) All conditions. except the Time Zone setting Minimum Run Time (Alarms) Maximum Run Time (Alarms) Terminate this job minutes after starting (Terminators) Number of times to restart this job after failure Delete Job after completion AutoHold for jobs in boxes Job Environment Profile Date/Time Alarms/Terminators ■ ■ ■ ■ Misc ■ ■ ■ Resource/Profile ■ 7–30 User Guide .

Job Information Language (JIL) Job Information Language JIL) is a scripting language which provides a way to specify how jobs should behave. It discusses changing and deleting a job. Defining Jobs Using JIL 8–1 . and how to set time dependencies. When you are using JIL commands you must use the Instance Command Prompt window. An example JIL script is provided. It also provides information about creating various types of jobs. JIL scripts contain one or more JIL subcommands and one or more attribute statements. which is located in the instance’s program group. these elements constitute a job definition. This window sets several environment variables that are needed to run the commands.Chapter 8 Defining Jobs Using JIL This chapter describes how to define jobs using the Job Information Language or JIL.

These statements may occur in any order. 8–2 User Guide . Rule 4 A box must be defined before the jobs can be placed in it.Job Information Language (JIL) JIL Syntax Rules When writing a JIL script. The attribute statements have the following form: attribute_keyword: value where: attribute_keyword value Is one of the legal JIL attributes. Rule 3 Multiple attribute statements can be entered on the same line. Is the user-specified name of the job to be acted upon. A subsequent sub-command begins a new set of attributes for a different job. you must follow the syntax rules listed below. but the lines must be separated by at least one space. Rule 1 Each sub-command uses the following form: sub_command: job_name where: sub_command job_name Is a sub-command. Is the setting to be applied to the attribute. in this chapter. For more information on JIL Sub-commands see the section JIL Sub-commands. and are applied to the job specified in the preceding sub-command. Rule 2 Each sub-command may be followed by one or more attribute statements.

C:\tmp is not. The following is an example: /* this is a comment */ Defining Jobs Using JIL 8–3 . numbers. the colon ( : ) must be escaped. and the at character (@). or: ■ The C programming syntax used for beginning a comment with a forward slash and astrisk (/*) and ending it with a astrisk and a forward slash (*/) may be used. because JIL parses on the combination of keyword followed by a colon. specify 10:00. to specify the time to start a job. Rule 7 Comments are indicated using one of the following two methods: ■ An entire line can be commented by placing a pound sign. colons (if the colon is escaped with quotes or a preceding backslash). underscores. Note: When specifying drive letters in commands. "C:\tmp" and C\:\tmp are valid. That is. this allows comments to span multiple lines. (#) in the first column. The colon may also be escaped with a preceding backslash (\).Job Information Language (JIL) Rule 5 Legal value settings can include any of the following characters: uppercase and lowercase letters. as in 10\:00. For example. Rule 6 Any colons used in an attribute statement’s value setting must be escaped. hyphens.

Delete an existing Box job. a completed JIL script is called a job definition. Apply overrides on indicated job attributes for the next run of this job. or delete a job definition. This job definition must be submitted to the database before the job it defines can be run. Edit fields on an existing job. override. You can submit a job to the database using one of the following methods (at the Instance Command Prompt window that is associated with the instance for which you are defining this job): ■ Submit the job by redirecting a JIL script file to the jil command. Primary JIL Sub-command Definition insert_job update_job delete_job delete_box Add a new job.Job Information Language (JIL) JIL Sub-commands JIL sub-commands are used to create. Delete an existing job from the database. using the Job Editor. Both of these methods are analogous to saving a job definition in the GUI. or press Ctrl+d. Then entering JIL statements at the provided Command Prompts jil>> To exit interactive mode. and recursively delete all the jobs which are contained in the box. enter exit at the prompt. override_job Submitting Job Definitions As stated earlier. 8–4 User Guide . for example: jil < my_jil_script ■ Interactively submit it by issuing the jil command and pressing Return. modify. These sub-commands are listed in the following table.

Creating a Simple Command Job To create the most basic Command Job. you only need to specify a few attributes. If a JIL script does not specify any starting parameters for a job. it will run the job.BAT" This JIL script instructs Unicenter AutoSys JM: ■ ■ ■ ■ To add a new job named “test_run. For example. The only way to start it would be to issue the following command: sendevent -E STARTJOB -J test_install This command tells the Event Processor to start the job named test_install. it is the default) */ machine: tibet command: "C:\MYAPPS\DOREPORTS. For example. For more information about the sendevent command. it will start only if you issue the sendevent command. the job will not be started automatically by the Event Processor.” To execute the C:\MYAPPS\DOREPORTS.” That the new job is a Command Job. the JIL script required to define a simple Command Job named “test_run” is given following: insert_job: test_run job_type: c /*(optional. To run the job on the client machine named “tibet.BAT batch file. it will be started according to the starting parameters specified in its JIL script. assume a job named “test_install” has no starting parameters specified in its JIL script. see the chapter “Commands.Creating a Simple Command Job Running JIL After a job definition has been submitted to the database.” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. That is. the Event Processor will continually poll the database and when it determines that the starting parameters have been met. Defining Jobs Using JIL 8–5 .

■ ■ Until the minimum file size of 50. To run the job on the client machine named “tibet”.Creating a File Watcher Job Creating a File Watcher Job File Watcher Jobs do not execute commands themselves. Check the file every 60 seconds. For example. 8–6 User Guide . That the new job will be a File Watcher Job. the File Watcher Job will end with a SUCCESS condition. they are used to signal the arrival of files.000 bytes has been reached. Determine if the file has reached the minimum file size of 50. the file will not be considered as complete. When this occurs. the JIL script required to define a File Watcher Job named “EOD_watch” is given following: insert_job: EOD_watch job_type: f machine: tibet watch_file: "C:\tmp\EodTransFile" watch_interval: 60 watch_file_min_size: 50000 This JIL script instructs Unicenter AutoSys JM: ■ ■ ■ ■ To add a new job named “EOD_watch”.000 bytes. and typically set off the execution of a Command Job. To watch for a file named “EodTransFile” in the C:\tmp directory (this file will contain end of day transactions). When the file reaches this minimum size and does not change between check intervals (60 seconds in this example) it is considered complete.

And. “EOD_post” will be specified to run on the same machine as the File Watcher Job created in the previous section. To run the job on the client machine named “tibet”. That the new job will be a Command Job. the JIL script required to define a dependent Command Job named “EOD_post” is given below.Creating a Dependent Command Job Creating a Dependent Command Job Command Jobs can be dependent on the successful completion of other jobs. it will be dependent on the success of the File Watcher Job. Defining Jobs Using JIL 8–7 . insert_job: EOD_post job_type: c machine: tibet condition: success(EOD_watch) command: %HOMEPATH%\POST. For example. since it presumably will need the watched-for file to process. The only difference between a dependent Command Job and a simple Command Job is its dependency on another job.EXE This JIL script instructs Unicenter AutoSys JM: ■ ■ ■ To add a new job named “EOD_post”. such as the File Watcher Job created in the previous section.

you must define the default profile. the default is initially blank. All other variables must be defined by a job profile. the default profile is sourced. which you can open from the program group. use the profile attribute. on the Resource/Profile tab. which resides in the owner’s home directory. However. see the section Job Profiles in the chapter “Jobs. see the chapter “JIL/GUI Job Definitions.Creating a Dependent Command Job ■ To run the job only if the File Watcher Job named “EOD_watch” completes with a SUCCESS status. the job’s execution environment is determined by the profile. or use the Job Environment Profile field in the Job Editor. which contains the user defined environment variables that are necessary to run the job. set all environment variables in the default job profile. For more information on defining job profiles.) Note: The job’s execution environment automatically includes NT system environment variables.EXE. (%HOMEPATH% and Windows system variables are the only variables that are automatically set. ■ 8–8 User Guide . For information on the profile job attribute. other than the default. but Windows user defined environment variables are not set automatically. which is in the program group. By default. To set the %HOMEPATH% variable. To associate a profile. You can define these profiles using the Profiles Manager.” in this guide. with a job.” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. then execute POST. All other non-system variables must be set in the default or user-defined job profile. on Windows. The profile is sourced immediately before the job is started. You can define the default profile and other profiles using the Profiles Manager.

then change the job you just created to put it in the box. Rather than make each job dependent on the File Watcher. For information on Box Jobs. Defining Jobs Using JIL 8–9 . and place all of the jobs in the box. Assume you want to schedule a group of jobs to all start running once the File Watcher completes successfully. Now you will create a box.” in this guide. see the chapter “Box Job Logic. you can create a box that is dependent on the File Watcher.Creating a Box Creating a Box Box Jobs are a convenient way to start multiple jobs. and then make it no longer individually dependent on the File Watcher. To run the job only if the File Watcher Job named “EOD_watch” completes with a SUCCESS status. you only have to start a single job (the box) in order for all the jobs in the box to start running. When you put jobs in a box. The JIL script required to define a Box Job named “EOD_box” is given following: insert_job: EOD_box job_type: b condition: success(EOD_watch) This JIL script instructs Unicenter AutoSys JM: ■ ■ ■ To add a new job named “EOD_box”. That the new job will be a Box Job.

and has inherited the box’s starting parameters. The “EOD_post” Command Job is now in the “EOD_box” Box Job. The latter scenario is particularly useful when many non-default attributes have been specified. then redefine the job using the insert_job sub-command. you want to de-activate them. To change a job. in other words. since the job will inherit the starting condition of the box in which it is placed. you’ll have to respecify any of the attributes that need to remain the same. using the delete_job sub-command. The JIL script required to change the “EOD-post” job and to put it in the “EOD_box” is given following: update_job: EOD_post condition: NULL box_name: EOD_box This JIL script instructs Unicenter AutoSys JM: To update the job named “EOD_post”. However. You will place the “EOD_post” job in the newlycreated box. you can either use the update_job sub-command. 1. 8–10 User Guide . So. or you can delete the job definition. in the example below. 2. Remove the starting condition from the job definition. you need to change the “EOD_post” Command Job that was created previously. and you want to “unset” them rather than “reset” them.Changing a Job Changing a Job To place an existing job in a box. You should make sure a job is not running before you modify or delete it. Put the job named “EOD_post” in the box named “EOD_box”. you’ll use the update method.

14:00" This JIL script instructs Unicenter AutoSys JM: 1. Set the job to run on Mondays. and Fridays.m. you would use the timezone attribute.Setting Time Dependencies Setting Time Dependencies The “test_run” job you specified at the beginning of the chapter has no starting conditions. using the Calendar Editor. start the job at 10:00 a. instead of listing the individual day values. Then. Wednesdays. on Mondays. 14\:00 Additional Time Setting Features If you wanted the time settings for the job to be based on a specific time zone. Activate the conditions based on date. “weekday_cal”. the colon will be interpreted as a delimiter. First. you could have specified the all value. 2. and 2:00 p. it will only run if it is started using the sendevent command. or the autocal_asc command. Therefore. Or.m. If you specify a time zone that includes a colon. using the following JIL statement: run_calendar: weekday_cal Defining Jobs Using JIL 8–11 . Wednesdays. you would have had to define the calendar. since they contain a colon. producing unexpected results. you must quote the time zone name like: timezone: "IST-5:30" If you do not quote a time zone that contains a colon. you could have specified a custom calendar. and Fridays. you would specify the calendar name. rather than specific days of the week. and 2:00 p. such as 10:00 a. They could also have been escaped by using backslashes (\). 3. if you had wanted to schedule the job for specific dates. The times shown in the script above are quoted. On each of these three days. If you had wanted to run the job every day. To update the job named “test_run”. rather than only on specific days. we.m. as shown following: start_times: 10\:00. fr start_times: "10:00. 4.m. To set the job to run automatically on certain days at a certain time. you would modify the job using this JIL script: update_job: test_run date_conditions: y days_of_week: mo.

Deleting a Box Job To delete a box.”in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. and recursively delete every job in that box use the delete_box sub-command. These attributes are described in detail in the chapter “JIL/GUI Job Definitions. This functionality only works when JIL is in the job verification mode. as opposed to specific times of day. “holiday_cal”.Deleting a Job Alternatively. To delete the “test_run” job. like: delete_job: EOD_box Using JIL. but leave its contents intact use the delete_job sub-command on the box. which you specified at the beginning of this chapter. This reference chapter provides complete information on all job attributes specified using JIL. which is the default. use the following JIL statement: start_mins: 15. enter the following JIL sub-command: delete_job: test_run The delete_job sub-command checks the job_cond table and notifies you if dependent conditions for the deleted job exist. to run a job at a quarter after and a quarter before each hour. the minutes past every hour could have been specified. like: delete_box: EOD_box To delete a box. there are a number of other attributes which you can configure. you could have specified a custom calendar specifying the days on which the job was not to be run. 45 Deleting a Job Now you will delete the “test_run” job. 8–12 User Guide . using the following JIL statement: exclude_calendar: holiday_cal If you wanted the job to run at specific times every hour. For example.

Specifying One-Time Job Overrides

Specifying One-Time Job Overrides
Using JIL, you can specify a job override for the next run of a particular job. In other words, the next time a job runs, you can change its behavior. Job overrides are applied only once. If a RESTART event is generated because of system problems, Unicenter AutoSys JM will re-issue a job override until the job actually runs once, or until the maximum number of retries limit is met. After this, the override is discarded. Note: The maximum number of job restarts after system or network failures is specified in the Max Restart Trys field on the Administrator Event Processor screen. One-time job overrides will be applied to jobs restarted due to system problems, but will not be applied to jobs restarted because of application failures. System problems include such things as machine unavailability, media failures, or insufficient disk space. Application failures include such things as inability to read or write a file, command not found, exit status greater than the defined maximum exit status for success, or various syntax errors. The following attributes can be modified in a job override:

auto_hold command condition date_conditions days_of_week exclude_calendar Machine max_run_alarm

min_run_alarm n_retrys profile run_calendar run_window start_mins start_times std_err_file

std_in_file std_out_file term_run_time watch_file watch_file_min_size watch_interval

JIL will not accept an override if it results in an invalid job definition. For example, if a job definition has only one starting condition, start_times, JIL will not allow you to set the start_times attribute to NULL because removing the start condition makes the job definition invalid (no start time could be calculated).

Defining Jobs Using JIL

8–13

Specifying One-Time Job Overrides

Setting Job Overrides
To set job overrides, you use the override_job sub-command; you only need to specify those attributes that you want to override. Using this command, you can also temporarily delete a job attribute. For example, if you wanted to run a job named “RunData” with no conditions (where some had been previously specified) and you wanted to output the results to a different output file, you would enter a JIL script like:
override_job: RunData condition: NULL std_out_file: "C:\tmp\SpecialRun.out"

To cancel the job overrides specified in the script above, you would enter the following JIL script:
override_job: RunData delete

Note: Once you have submitted a JIL script to the database, you cannot view the JIL script and edit a job override. If you want to change the override values, you must submit another JIL script with new values, or use the Job Editor. However, the original override (for example, the first over_num) remains stored in the “overjob” table in the database.

8–14

User Guide

Example JIL Script

Example JIL Script
The following is a full example of an JIL script. It incorporates the creation and use of a Command Job, a File Watcher Job, and a Box Job. The following is a processing “scenario”:

A file named C:\DOWNLOAD\MAINFRAME\SALE.RAW is expected to arrive from the mainframe sometime after 2:00 a.m. When the file arrives, it is processed by the command file named filter_mainframe_info, and the results are placed in the file named C:\DOWNLOAD\MAINFRAME\SALES.SQL. When the above functions are completed, the file named C:\DOWNLOAD\MAINFRAME\SALES.SQL (containing SQL statements) is executed.
# Example of Jobs insert_job: Nightly_Download job_type: b date_conditions: yes days_of_week: all start_times: "02:00" insert_job: Watch_4_file job_type: f box_name: Nightly_Download watch_file: "C:\DOWNLOAD\MAINFRAME\SALES.RAW" machine: gateway insert_job: filter_data job_type: c box_name: Nightly_Download condition: success(Watch_4_file) command: filter_mainframe_info machine: gateway std_in_file: "C:\DOWNLOAD\MAINFRAME\SALES.RAW" std_out_file: "C:\DOWNLOAD\MAINFRAME\SALES.SQL" std_err_file: "C:\LOG\FilterMFLog.err" insert_job: update_DBMS job_type: c box_name: Nightly_Download condition: success(filter_data) machine: gateway command: isql -U mutt -P jeff std_in_file: "C:\DOWNLOAD\MAINFRAME\SALES.SQL"

An example of the output generated by the autorep command for the previously shown job definition is provided in the Examples section for the autorep command in the chapter “Commands,” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide.

Defining Jobs Using JIL

8–15

Chapter

9

Calendar Editor

This chapter describes how to create calendars by using the Calendar Editor and how to use the calendars you create with jobs. The Calendar Editor provides a method of defining and maintaining calendars using a point and click approach on a graphical display of a conventional calendar. After defining a calendar, you can apply it to jobs through the job definition, either using JIL or the Job Editor. The Calendar Editor allows you to do the following:
■ ■ ■

Define simple calendars. Set, unset, or block certain dates, such as holidays, when editing calendars. Apply custom rules to a calendar, such as the “first weekday of every month,” rather than selecting the individual dates by hand. Select options that will automatically reschedule conflicting dates when applying a rule. “Conflicting” dates are those that are blocked out but also meet the qualifications of the rule being applied. A number of alternatives for rescheduling are provided. Build a new calendar by overlaying multiple, preexisting calendars, and allowing you to further customize the new calendar manually. Preview a calendar before applying it to another calendar. Import and export text definitions for calendars.

■ ■

Calendar Editor

9–1

Using Defined Calendars

Using Defined Calendars
After you define a calendar using the Calendar Editor, you can use it to schedule jobs. Using defined calendars simplifies job scheduling by letting you group any collection of dates into a single entity.

Scheduling Jobs with Calendars
In the job definition, use one of the following methods to apply a calendar:

With the GUI, go to the Job Editor Date/Time tab, select either Run Calendar or Exclude Calendar, and select a calendar from the drop-down list. With JIL, use a single attribute in the job definition: either run_calendar or exclude_calendar.

You can set the calendar in conjunction with other time attributes to precisely control when a job will or will not start. For example, you could create a calendar called “holidays” containing the dates of all corporate holidays, and then you could define the job with the Job Editor, you would do the following: 1. On the Date/Time tab, click the Date/Time Conditions check box. This action checks the box and enables the fields on the Date/Time tab. 2. Do one of the following:

For a job that you want to start on holidays, click the Run Calendar radio button. For a job that you do not want to start on holidays, click the Exclude Calendar check box.

3.

Select the defined holiday calendar from the calendar drop-down list that is to the right of the option you selected. Define the other attributes for the job appropriately. Choose File, Save to save the new job definition.

4. 5.

9–2

User Guide

Using Defined Calendars

When using these attributes, or their Job Editor field equivalents, keep the following in mind.

Jobs scheduled with a Run Calendar are scheduled to start on every day specified in the calendar, at the times specified in the calendar or in the Times of Day or Minutes after Each Hour attribute. If present in the job definition, both of these attributes override the times specified for the defined Run Calendar. By default, if no start time is specified, calendarscheduled jobs start at midnight. Note: You can only assign times to calendars when using the command-line calendar definition tool, autocal_asc. For information, see autocal_asc in the chapter “Commands,” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide.

Jobs scheduled with the Run Calendar are scheduled to run on the next available date in that calendar. Dates previous to the current date are ignored. Jobs scheduled with an Exclude Calendar can make use of other starting conditions in the job definition. In this case, Unicenter AutoSys JM evaluates the start conditions and, if they are true, checks if the date is set in the Exclude Calendar. If the date is in the defined calendar, the job will not be started, and its status will be changed to INACTIVE.

For information on using the Job Editor, see the chapter “Defining Jobs Using the Job Editor,” in this guide. For information about these attributes, see their reference pages in the chapter “JIL/GUI Job Definitions,” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide.

Calendar Editor

9–3

Starting the Calendar Editor

Starting the Calendar Editor
To start the Calendar Editor: 1. Open the GUI Control Panel from the Graphical Interface icon in the AutoSys program group. Click the Calendar Editor button in the GUI control panel. This opens the Calendar Editor:

2.

9–4

User Guide

Using the Calendar Editor Interface

Using the Calendar Editor Interface
The Calendar Editor is divided into the following regions:
■ ■ ■

Menu Bar Navigation Controls Calendar Display

Using the Menu Bar
At the top of the Calendar Editor is the menu bar that contains the following menus: File, Edit, Utilities, Preferences, and Help.

File Menu The File menu contains the following options: New Displays the New Calendar dialog in which you enter the Instance and new Calendar Name, then click OK. The new Calendar Name must be a unique job name for the specific instance. The name must be from 1 to 30 alphanumeric characters, and white space indicates the end of the name. Embedded spaces and tabs are illegal. When you click OK, an empty Calendar Editor displays. Open Displays the Calendar Selection dialog that you can use to open an existing calendar. Save Saves the calendar currently being edited and writes it to the database, using its current name. The first time you save a calendar, this option displays the Save As dialog. Save As Displays the Save As dialog in which you can enter both the name of the Instance to which you want the calendar saved and the new calendar name for the calendar. If you want to save a definition to another instance and keep the definition for the current instance, you can use this option to do so, and you can keep the same calendar name for the new instance.

Calendar Editor

9–5

Using the Calendar Editor Interface

Delete Displays the Delete Calendar dialog in which you can search for and select the calendar or calendars to delete. Rename Displays the Rename dialog in which you can enter a different instance and/or a new name for the calendar you are saving. Before you can use this option, the calendar definition must be saved to the defining instance. When you rename a calendar, it is saved to the new name, and the old calendar definition is deleted from the database. If you want to keep the current definition in the database, use the Save As option. Import Displays the Open dialog that allows you to select the directory and filename of a text file that contains calendar definitions that you want to import into the database. Export All Displays the Save As dialog that permits you to select the directory and name of the file to which you want to save all the calendars in the database, in text form. You can export all definitions at once only. Print Prints the current calendar in text format. Graphical Print Prints the current calendar in a graphical format, as it appears on the screen. New Calendar Editor Opens another Calendar Editor window. When you open more Calendar Editors, each window is numbered sequentially. Exit Exits the application. Note: When you first select an instance in any dialogs of the Calendar Editor, Unicenter AutoSys JM establishes a connection to that instance’s database. It maintains that connection until you close the Calendar Editor.

9–6

User Guide

Nine. Unicenter AutoSys JM recomputes the starting times for all jobs that use that calendar. Clear Clears the calendar settings. Revert Resets the state of all the dates in the current calendar to those last saved to the database. Six. which contains a list of all the jobs that reference the calendar you are currently editing. For more information. and it indicates which jobs will be affected by any changes you make to the current calendar. You can choose one of the following options: One. either as their Run Calendar or Exclude Calendar. Calendar Editor 9–7 . see Using the Job Definition Reference List in this chapter. Four. or Twelve.Using the Calendar Editor Interface Edit Menu The Edit menu contains the following options: Apply Rule Displays the Term Calendar Rule dialog in which you can set multiple dates using a variety of rule options. Note: When you update a calendar. This list is read only. For more information. all dates are returned to the unset state. Preferences Menu The Preferences menu contains the following options: Months in View Displays a submenu that allows you to choose how many months are displayed on one calendar screen. see Applying Rules to Calendars in this chapter. Utilities Menu The Utilities menu contains the following option: Job Definition Reference List Displays the Job Definition Reference List dialog.

Five—Indicates to include five years. Ten—Indicates to include ten years. or Conflicting. a Selected Color dialog displays. Blocked. whichever is greater. Three—Indicates to include three years. two years. The following colors are used by default: ■ ■ ■ ■ Unset dates use the background color of the Calendar Editor application Selected dates use green Conflicting dates use red Blocked dates use black Years Displays a submenu that allows you to select the number of years that the current calendar should include and that the Calendar Editor should display. if you do so. 9–8 User Guide . You can increase and decrease the date range of a calendar. and you can use this dialog to set the color for the date selection type.Using the Calendar Editor Interface Colors Displays a submenu that allows you to choose one of the following date selection types: Selected. however. or the default setting. when you open an existing calendar. becomes the new date range for the current Calendar Editor session. Unicenter AutoSys JM ignores these dates. The Years option limits how far into the future you can set dates in the current calendar. its date range. Two—Indicates to include through the next year. Note: The Calendar Editor allows you to set dates in the current year that have already past. Also. Four—Indicates to include four years. or the current date range. You can extend the calendar to include additional years by selecting one of the following options: ■ ■ ■ ■ ■ ■ One—Indicates one year. The default range is the current year. When you choose one of these options.

Using the Navigation Controls The Navigation controls area of the window contains the following: Selections area Allows you to navigate through and select dates. Calendar Editor 9–9 . Note: A darkened box surrounds the date with focus. Move focus to the next date in the calendar that has been set relative to the date that currently has the focus.Using the Calendar Editor Interface Help Menu The Help menu contains the following options: Contents Displays the table of contents for the Unicenter AutoSys JM Help. You can use the arrow buttons to do the following: ■ ■ Move focus to the first date in the calendar that has been set. Conflicts area Allows you to view the number of Conflicts and navigate through them. About Displays the Calendar Editor version number. ■ ■ When you use the Selections buttons and the focus changes to a date that is not currently displayed. the calendar display shifts to bring that date into view. Move focus to the last date in the calendar that has been set. Selections Area You can use the buttons in the Selections area to move to a particular date whose state has been set. Calendar drop-down list Allows you to select a defined calendar to be displayed in the Calendar Editor. Instance drop-down list Allows you to select the instance to which you want to connect. Move focus to the previous date in the calendar that has been set relative to the date that currently has the focus.

Instance Area To the right of the Conflicts area is the Instance drop-down list. Note: When you save a calendar containing unresolved conflicts to the database.” the navigation buttons are disabled.Using the Calendar Editor Interface Conflicts Area The Conflicts area displays the number of conflicts and allows you to navigate among those conflicts. The Conflicts field is updated each time you apply a rule or manually change a Conflicting date to another state. the Calendars drop-down list contains the appropriate defined calendars. When you select an instance. You can move to the First. they are not written to the database. and the navigation buttons are enabled. When there are “0 Conflicts. If there are Conflicts. Previous. the number of conflicts is displayed. All other date states are saved. Next. you are prompted that conflicts exist. If you choose to ignore the prompt and save anyway. 9–10 User Guide . the Conflicting dates are lost. or Last conflict. Calendars Area The Calendars drop-down list contains all of the defined calendars for the selected instance (in the Instance drop-down list).

If you click. When you open a new calendar. The current state of each date is indicated by its color. if you click again. and if you click the date a third time. Colors submenu. ■ To move to the previous six months (if it is part of the calendar): Click in the upper portion of the scroll bar. the date’s state is Unset. the date’s state is Selected. ■ To scroll to the next six months: Click in the lower portion of the scroll bar. You can change the display from the Preferences. Blocked Indicates the date is ineligible for setting when applying a rule. Calendar Editor 9–11 . Months in View menu. ■ To move back a month: Click the up arrow on the scroll bar. Selected Indicates the date is set for that calendar. all of the dates are unset. the date’s state is Blocked. The title bar of the window displays the name of the current calendar. as indicated from the Preferences. Date States You can set the dates on the calendar to one of the following states: Unset Indicates the date is not set. ■ To advance a month at a time: Click the down arrow on the scroll bar. You can cycle through these three states by clicking a date multiple times.Using the Calendar Editor Interface Using the Calendar Display The Calendar Editor by default displays six months of the calendar currently being edited.

which results in “falling off” the calendar. the Blocked state is only useful while applying rules. (Rescheduling may not have occurred if either a rescheduling rule has not been applied. a Conflicting state is generated. you want to apply a rule to set the “first day of each month.” The rule would conflict with the January 1st Blocked date.) For example. Blocked dates and rules are not stored in the database. see Applying Rules to Calendars in this chapter. there is a fourth. you must manually correct the situation before attempting to save the calendar to the database. This state occurs when both of the following are true: ■ ■ A rule is applied to a calendar. Note: Calendars created with the Calendar Editor are stored in the database. Only the Selected dates are stored. That is. you marked all holidays as Blocked. such as “move to the next weekday. but if you do so.” or if the rescheduling rule specifies to move backwards. all Conflicting dates are lost—they are not written to the database.Using the Calendar Editor Interface In addition to these three user-selectable states. 9–12 User Guide . including January 1st. or an applied rescheduling rule cannot find a nonconflicting date to move to. systemgenerated state called the “Conflicting” state. You can ignore the Conflicting state when you save. If there is no rescheduling rule in effect. Dates designated as Blocked are only in effect while editing a calendar. and rescheduling has not occurred. A date that qualifies for setting by the rule was previously set to the Blocked state. and. For more information about rules. In this case.

Save. you can define calendars and open existing calendars to create and modify calendars. From the Preferences menu.S. In the Calendar Editor. 2. select Years.Creating and Modifying Calendars Creating and Modifying Calendars Using the basic features of the Calendar Editor. select the holiday dates by clicking each date. 3. A New Calendar dialog is displayed. holidays. Then. To create a simple calendar containing all 2003 holidays: 1. select the Instance. and select Two. In the New Calendar dialog. using the scroll bar. 4. Enter us_hol_03 then click OK in the Save As dialog. scroll down to 2003 in the calendar display area. so that jobs do not run on holidays. If the desired dates are not displayed. New. 5. This type of calendar might be useful as an exclude calendar. Choose File. use the scroll bar to bring them into view. Calendar Editor 9–13 . Choose File. Creating a Calendar This example demonstrates how to create a calendar containing 2003 U.

they are ignored. Moreover. therefore.Creating and Modifying Calendars Your calendar will resemble the following illistration: Setting Dates Prior to Today’s Date Calendars exist to simplify the scheduling of job runs. any dates prior to today are dropped from the new calendar. 9–14 User Guide . only current and future dates are applicable. when you merge calendars to create a new calendar. While the Calendar Editor allows you to set dates in the past.

Open. The Calendar Selection dialog appears: The Calendar Selection dialog allows you to select which calendar to open. The list displays only the matching calendar names. “%. Choose File. Click Search. For example. and click Search to list those calendars whose names include the string. do the following: 1.” you specify the filter “holiday%.” such as “holiday_all” and “holiday_company. In the Pattern field of the Calendar Selection dialog. you can specify any string.” lists all of the calendar names.” and click the Search button. including the percent (%) wildcard character. 2. Calendar Editor 9–15 . to list only those calendar names starting with the string “holiday.Creating and Modifying Calendars Opening an Existing Calendar To open a saved calendar. The default filter. The Calendar Selection dialog contains a list of all the calendars that currently exist in the database for this instance.

■ 9–16 User Guide .Creating and Modifying Calendars 3. Click Cancel to exit the Calendar Selection dialog without opening a calendar. This action opens the calendar and exits the Calendar Selection dialog. Do one of the following: ■ Select a calendar in the list. and click OK.

you can apply a rule to set the state for multiple dates. Apply Rescheduling Rule The lower portion of the dialog. From the Edit menu. Instead of selecting each date individually to set a state.Applying Rules to Calendars Applying Rules to Calendars Using the Term Calendar Rule dialog. Calendar Editor 9–17 . This action opens the Term Calendar Rule dialog: The Term Calendar Rule dialog is divided into the following regions: Rule Specification The top portion of the dialog. To open the Term Calendar Rule dialog from the Calendar Editor: 1. you can apply rules to calendars. choose the Apply Rule option.

Using the Rule Specification Area The Rule Specification region provides a wide variety of options to specify the dates in the selected calendar that you want to affect and to what states those dates should be set. You can only select only one of these actions: Set Dates Changes the state of the selected dates to Selected. and Period. Apply. so that this date will not be set during any subsequent rule applications. This region consists of the following three areas: Action Allows you to set the action the rule will initiate. To specify and apply a rule for a calendar: Select the appropriate Action. The Apply button applies the rule and does not dismiss the dialog. The OK button applies the current rule and dismisses the dialog. you can select an action. The Cancel button dismisses the dialog without applying the rule.Applying Rules to Calendars Control The bottom portion of the dialog containing the OK. Day. Unset Dates Changes the state of the selected dates to Unset. Date Range. Block Dates Changes the state of the selected dates to Blocked. 9–18 User Guide . Date Range Allows you to set the range of dates the rule will include. and Period for the rule. Occurrences. and click Apply. and Cancel buttons. Action Area In the Action Area. Day. or OK. which is one of the following states to which the selected dates will be set. Date Selection Rule Allows you to set the Occurrences.

Period Allows you to specify the period during which the rule should be applied. starting with the current date. For usage examples. First. Select one or more options by clicking the corresponding check box. see Date Selection Rule Examples. When you enter a date range.Applying Rules to Calendars Date Range Area In the Date Range area. the dates must fall within the display range set in the Years option of the Preferences menu. The settings you select in these three areas must make sense together. You could choose the First/Monday Quarterly to indicate the first Monday of each quarter. The Range Starting date must be on or after the current date. Note: Rules are not applied to any date prior to today’s date. The No Period option is used for nonrepeating periods. you can specify the date range over which the rule should apply. or by specifying an actual date range in the All Days in Range Starting and Ending edit fields. Date Selection Rule Area The Date Selection Rule area contains the following three sub areas: Occurrences. Every nth). Day. Last. Monthly. If you select Specific Days. Calendar Editor 9–19 . the entire date range of the selected calendar is listed. Weekday. Occurrences Allows you to specify the occurrence of a day for which the rule should be applied (for example. and Period. or the days in a specified Calendar. Day Allows you to specify on what days of the week the rule should be applied. however. Quarterly. or Specific Days. Usually. Every n weeks. Select only one of the following options: No Period. you must also select one or more of the specific days of the week. By default. you can limit the date range by selecting an option from either the All Year pull-down menu. Select one of the following three options: Day (Any). you would use the No Period option with the Every or Every nth option in the Occurrences sub area.

only the dates specified in the indicated calendar are used when applying the rule. Click OK to apply the rule to the calendar you are currently editing. 3. Example One Set the 3rd Tuesday of every month throughout the entire currently selected calendar: 1. or you can clear everything using the Clear option from the Edit menu. 2. select Block Dates. which automatically selects the Specific Days option. 2. You can enter the calendar name directly. do not change the default All Days in Range setting. 3. or you can click the Calendar drop-down list button to display a list of existing calendars from which you can choose a calendar for the period. In the Period sub area. In the Date Range area. In the Occurrences sub area. Remember. 5. Date Selection Rule Examples The examples in this section illustrate the use of the Date Selection Rule options. and to close the dialog. which indicates the calendar’s entire range. Apply Rule. In the Action area of the Term Calendar Rule dialog. 6. Example Two Block every holiday date and prevent those days from being scheduled: Using the calendar named us_hol_03. Open the Term Calendar Rule dialog by choosing Edit. In the Date Range area. select Tuesday. 7. we recommend that you experiment a little bit. In the Day sub area. you can always revert to the last saved version of a calendar by using the Revert option from the Edit menu. do not change the default All Days in Range setting. follow these steps: 1. 4. do not change the default Set Dates selection.Applying Rules to Calendars If you select the Calendar Period option. or type “3” in the nth option field. Note: When you first start applying rules to your calendars. Apply Rule. select Monthly. Open the Term Calendar Rule dialog by choosing Edit. In the Action area of the Term Calendar Rule dialog. select either the Third option. which you defined. 9–20 User Guide . which indicates the calendar’s entire range.

In the Period sub area. In the Action area. follow these steps. you want to change the state of every Thursday to Selected. select the us_hol_03 calendar. 5. the Conflicting state is assigned to the Thursdays that were previously Blocked. In the Occurrences sub area. by clicking them until they are Unset. select Set Dates. In the Day sub area. 4. In the Period sub area. Use the open Term Calendar Rule dialog in the next example. The calendar name should appear in the Calendar field. In the Date Range area. Example Three Continuing with the above example. using the drop-down list. Selected. When you apply this rule. 5. In the current calendar. you could reset these conflicting dates manually. 2. Rescheduling Rules are described in Using the Rescheduling Rule Area. select Thursday. 7. leave the default selection of Day. do not change the default All Day in Range setting. select Calendar and. using the open Term Calendar Rule dialog: 1. leave Every selected. which also selects the Specific Days radio button. or you could specify a rescheduling rule to accommodate this type of conflict (as described in Rescheduling Rule Example in this chapter). all the holidays that were selected in your us_hol_03 calendar are set to Blocked. select No Period. Calendar Editor 9–21 . In the Day sub area. As a result.Applying Rules to Calendars 4. because they were selected using the us_hol_03 calendar. or Blocked. Click Apply to apply the rule to the current calendar (in the Calendar Editor). 6. Click OK to apply the rule to the current calendar. select Every. 6. 3. In the Occurrences sub area. To do this.

2. To Following Moves the Selected state forward in the calendar. Move Direction Area You can select one of the following Move Direction options: To Previous Moves the Selected state backward in the calendar. Note: Conflicts can also occur if a date is both Selected and Blocked. rather than wait for conflicts to occur.Applying Rules to Calendars Using the Rescheduling Rule Area The Rescheduling Rule region allows you to specify how date conflicts should be resolved when applying a rule. Date Range. If you intend to apply a Rescheduling Rule. 9–22 User Guide . and the Blocked date is maintained. Select the Apply Rescheduling Rule check box. 3. you should set it up at the same time you set up the Date Selection Rule. Select the appropriate Move Direction and To Day options. These settings indicate how the Conflicting dates should be rescheduled. 4. Day. the selected state is moved when rescheduling. This action enables the Move Direction and To Day options. Occurrences. and Period. Click OK. Create the rule in the Date Selection Rule area by selecting the Action. To specify a rescheduling rule using the Term Calendar Rule dialog: 1. When a conflict occurs.

Use the dropdown list to select an existing calendar. In Calendar Indicates the next available date in the specified calendar. In the Occurrences sub area. Click the Apply Rescheduling Rule check box. 7. you must specify one of the following To Day options: Any Day Indicates the next available date. which also selects the Specific Days radio button. select To Following. you apply a Rescheduling Rule that specifies “any day following the date in conflict that is not also a holiday. Use the drop-down list to select an existing calendar. 3. Conflicting states will be assigned to Thursdays that were blocked because they were selected in the us_hol_98 calendar). select Thursday. This selection will reschedule Conflicting dates to the appropriate following date. In the Action area. select Set Dates. 4. 6. select No Period. In the Period sub area. follow these steps (as opposed to those given in “Example Three” previously discussed): 1.Applying Rules to Calendars To Day Area In addition to specifying the Move Direction. In the Day sub area. In this example. Weekday Indicates the next available weekday date.” To do this. In the Move Direction area. Rescheduling Rule Example This example describes how to remedy the conflict situation in the last example (when you applied the rule. Not in Calendar Indicates to use the next available date not Selected in the specified calendar. 5. leave Every selected. This action enables the other fields. 2. In the Date Range area. do not change the default All Days in Range setting. Calendar Editor 9–23 .

then apply a rule to set every day. along with the To Following selection. From the Edit menu. Likewise. select Weekday. Note: Many conflict dates can be rescheduled to the same new date. 4. Combining Calendars Example For example. In the To Day area. select the holiday dates. if you block all weekend dates. choose the New option. 2. will reschedule the Conflicting dates to the following weekday. To do this you must first create a calendar named co_hol_03. 9. In the Calendar Editor. scroll down to the 2003 calendar. and the Selected dates should be rescheduled to the following weekday. Then. you can combine any number of calendars in these ways. For example. 9–24 User Guide . and save the calendar. you can combine the two calendars following these steps by using the Calendar Editor: 1. For example. you can create a calendar that includes all the dates that are in either one calendar or another. choose the Apply Rule option. select the Instance. both the Saturday and Sunday conflicts will be resolved to the preceding Friday. In the New Calendar dialog. In fact. you can create a calendar that includes all the dates that are in one calendar but not in another. turn off the Rescheduling Rule and resolve the conflicts manually. 3. the Conflicting dates should be set to Blocked. you should set it up at the same time you set up the Date Selection Rule. This action opens the New Calendar dialog. Combining Existing Calendars You can combine calendars in a number of ways. If you want separate runs for Saturday and Sunday. From the File menu. From the Preferences menu. If you intend to apply a Rescheduling Rule. rather than wait for conflicts to occur. choose Years. If necessary. you could combine your existing us_hol_03 calendar with your company holiday calendar. This selection. Click OK to apply the rule to the current calendar and to close the dialog. then choose Two from the submenu.Combining Existing Calendars 8. with rescheduling to the previous weekday.

any dates prior to the current date are dropped from the new calendar. and select us_hol_03 from drop-down list. Then. From the File menu. 7. select Set Dates in the Action area. holidays and click OK in the Save As dialog.Combining Existing Calendars 5. except select the co_hol_03 calendar from the dropdown list. Every in the Occurrences area. Enter the calendar name. 10. select the Save option. click the Calendar radio button. click OK to dismiss the Term Calendar Rule dialog. click Apply. In the Period sub area. This new calendar will include and combine the dates that are the two previously defined calendars. 6. This process of combining calendars can be repeated for any number of calendars. Note: When combining calendars. 8. Calendar Editor 9–25 . Repeat steps 5 and 6. 9. In the Term Calendar Rule dialog. and Day in the Day area. In the Term Calendar Rule dialog.

it displays a list of jobs that reference the current calendar either as a “run calendar” or an “exclude calendar. When you save the current calendar.” These are the jobs that will be affected by any changes that you make to the current calendar. To open the Job Definition Reference List dialog: 1. Job Definition List. Choose Utilities. This action opens the Job Definition Reference List dialog: When you open the Job Definition Reference List. you can open the Job Definition Reference List. 9–26 User Guide . You can use the Job Definition List to see what jobs will be affected by any changes you make to the current calendar. the start dates for the job will be recomputed.Using the Job Definition Reference List Using the Job Definition Reference List From the Calendar Editor Utilities menu.

This is a sample calendar text file: calendar: Q1paydays 01/01/2003 01/15/2003 02/01/2003 02/15/2003 03/01/2003 calendar: Q1holidays 01/01/2003 You can include comments following a space after the calendar name or after each date. and export them to text files. Note: Unicenter AutoSys JM will not automatically overwrite the existing calendar definitions. You perform calendar imports and exports by using the standard Open or Save dialogs.Importing and Exporting Calendars Importing and Exporting Calendars Using the Calendar Editor. These text files may contain multiple calendars. each of which must be delimited with the calendar:calendar_name attribute. To import a file: Choose File. The standard Open dialog opens. after the import has completed. a warning dialog will notify you that a calendar name is duplicated and that the import of this calendar will not occur. Calendar Editor 9–27 . This is the same format that is written by the Export function. In addition. which you use to select the file to import. Import. If you have calendars within a text file that have names identical to calendars existing in the database. Importing Calendar Text Files You can import calendars contained in ASCII text files into the database. an information dialog will tell you how many calendars were imported. you can import calendars from.

The standard Save As dialog opens. which you can use to select a location and file name to which the calendar definition should be saved. Export All. 9–28 User Guide . Export All. To export the calendars: Select File. When you use the Export All option. Note: There is no way to export individual calendar definitions. all the calendars in the database are exported to a single ASCII text file. however. you can edit the text file created by File.Importing and Exporting Calendars Exporting Calendars You can export all calendars defined in the database to an ASCII text file.

a real machine is any network host that has: ■ Been identified in the appropriate network database and is accessible over the network using the TCP/IP protocol so that Unicenter AutoSys JM can access it. Undergone a client software installation (and is licensed) so that Unicenter AutoSys JM can run jobs on it. ■ Load Balancing and Queing Jobs 10–1 . Real Machines In the environment. as well as queueing jobs to real and virtual machines.Chapter 10 Load Balancing and Queing Jobs This chapter describes the use of real and virtual machines in the environment to provide load balancing and queueing functionality. It provides information about load balancing jobs across multiple machines.

The following JIL sub-command defines a real or virtual machine: insert_machine: machine_name The following JIL machine attributes are used when defining machines: Machine Attribute type Description Specifies a machine type. Virtual Machines A virtual machine is comprised of one or more real machines. Defining Machines Define both real and virtual machines by using machine attribute statements within a JIL script. All real machines within a virtual machine must be of the same type. By defining virtual machines to Unicenter AutoSys JM . either Windows or UNIX. Unicenter AutoSys JM provides both load balancing and queuing by way of the logical construct called virtual machines. in whole or in part (or a combination of both).Virtual Machines The above two conditions are required for a real machine to run jobs. Virtual machines cannot be a mix of both UNIX and Windows machines. for Unicenter AutoSys JM to perform intelligent load balancing and queuing while executing jobs. it needs to know the relative processing power of the various real machines. That Unicenter AutoSys JM automatically execute those policies in a multimachine environment. and then submitting jobs to run on those machines. you can specify: ■ ■ Runtime resource policies (or constraints) at a high level. which can be one of the following: ■ ■ ■ r for UNIX real v for UNIX virtual n for Windows (Real or Virtual) 10–2 User Guide . However.

For more information about the JIL sub-commands and attributes pertaining to machines. It describes how much of a load can be placed on a real machine.Specifying Machine Load (max_load) Machine Attribute machine Description Specifies a real machine name to be inserted in a virtual machine. Are to be included in a virtual machine. Specifying Machine Load (max_load) The max_load attribute can be defined only for real machines. For real machines only. and used for load balancing. Note: Real and virtual machines can be defined only using JIL. Load balancing and queuing can be done only if real and virtual machines have been defined to Unicenter AutoSys JM using these machine attribute statements. Virtual machines must be defined before you can use them. are key for load balancing and queuing: max_load and factor. a load unit with a range of 10-100 would specify that machines with limited processing power are expected to carry a load of only 10. max_load factor Real machines only need to be defined if they meet one of the following criteria: ■ ■ Require a max_load or factor attribute to be set for them. and used for load balancing. For real machines only. see the chapter “JIL Machine Definitions. The following two attributes. Any weighting scheme desired by the user can be used. For example. used when defining real machines.” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. There is no GUI interface for defining machines. and it is specified with an arbitrary unit called a “load unit”. Zero and negative numbers cannot be used. while machines with ample processing power can carry a load of 100. There is no direct relationship between the load unit value and any of the machine’s physical resources. you should develop conventions that are meaningful to you. Load Balancing and Queing Jobs 10–3 . Therefore.

Thus. It is used to weigh available cycles on one machine against that of another machine. a machine’s current load can be tracked. For example. every defined job that will impact the load on a machine must be assigned a job_load job attribute. if the max_load on a machine is “100” and the job_load for one job is “10”. it multiplies the percent of free CPU cycles by the factor in order to determine which machine has more relative processing power available. Specifying Relative Processing Power (factor) The factor machine attribute can be defined only for real machines. When AutoSys checks the available cycles on each machine.0 and 1. and overloading of a machine can be prevented.Specifying Machine Load (max_load) Job Attributes and Load Balancing and Queuing For load balancing to work. the priority job attribute must also be assigned in the job definition. This attribute’s value is a real number that can contain a decimal. which defines the relative load the job will place on a machine. the factor value is typically a number between 0. for job queueing to take place. Without this attribute set. In addition. The priority attribute specifies the relative priority of all jobs queued for a given machine. Therefore. a job will run immediately on a machine. It is another arbitrary value that describes the relative processing power of a machine. then that job will use ten percent of the machine’s resources. 10–4 User Guide .0. and it will not be placed in the queue.

If these attributes are not specified in a real machine definition. They are specified in the definitions of the real machines that make up the virtual machine.0 Note: A virtual machine is comprised of real machines. Conversely. the factor attribute is primarily intended to be used when deciding between machines for running a job.Specifying Machine Load (max_load) Using max_load and factor The max_load attribute is primarily used to limit the loading of a machine. Load Balancing and Queing Jobs 10–5 . the max_load attribute does not influence the decision of on which machine a job should be run. they default to the values shown following: max_load: none/* no limit */ factor: 1. As long as a job’s load will not cause a machine’s max_load to be exceeded. Therefore you do not specify max_load and factor attributes explicitly in a virtual machine definition. if more than one machine is available.

because only real machines can have these attributes. These examples include the JIL statements used to define these machines. Compare the following definitions.Machine Definitions Machine Definitions Unicenter AutoSys JM can infer whether a machine being defined is a real or a virtual machine based solely on the attributes in the definition. you can omit the type attribute when defining a UNIX machine. Any machine definition containing a list of machine attributes is a virtual machine definition. Any machine definition containing a max_load or factor attribute must be a real machine definition. For Windows. 10–6 User Guide . Because of this. however. the following sections provide a series of examples that demonstrate the different combinations of real machines that can constitute a virtual machine.8 Virtual UNIX insert_machine: pond machine: toad machine: frog Virtual Windows insert_machine: jungle type: n machine: tiger machine: monkey To help you understand virtual machines and their capabilities. the type attribute is required.8 Real Windows insert_machine: tiger type: n max_load: 100 factor: . Real UNIX insert_machine: toad max_load: 100 factor: .

this must be its hostname. Assign a machine name.0 Deleting Real Machines The following JIL statement deletes the real machine definition for the machine named “jaguar”: delete_machine: jaguar Load Balancing and Queing Jobs 10–7 . assign a max_load and a factor attribute value. The following illustration defines a real UNIX machine named “jaguar” with a max_load of 100 and a factor of 1. enter the following JIL statements: insert_machine: jaguar type: r max_load: 100 factor: 1.0 100 1. insert_machine: jaguar type: r max_load: 100 factor: 1. Assign a machine type: r for real UNIX or n for Windows. Optionally.Defining a Real Machine Defining a Real Machine To define a real machine 1.0. 3. 2.0 jaguar max_load factor To define a real Windows machine named “jaguar”.

Defining a Virtual Machine Defining a Virtual Machine To define a virtual machine 1. 3. they will have the default values for these attributes: a factor of 1. insert_machine: modena type: v machine: ferrari machine: lambo modena ferrari lambo The following JIL statements define two real UNIX machines named “fiat” and “lotus”. Assign a machine name. the virtual machine will use the max_load and factor attributes specified for them.) insert_machine: fiat type: r max_load: 100 factor: 1 insert_machine: lotus type: r max_load: 80 factor: . Specify the real machines that will make up the virtual machine. and a virtual machine named “capri”.0 and unlimited load units. The virtual machine is a superset of the two previously defined real machines. The following defines a virtual UNIX machine named “modena”. 2. which is composed of the two real machines. Assign a machine type: v for virtual UNIX or n for virtual Windows. Because the real machines do not specify a max_load and factor. (Because the real machines are defined first. which is composed of two real UNIX machines named “ferrari” and “lambo”.9 insert_machine: capri type: v machine: fiat machine: lotus 10–8 User Guide .

insert_machine: rose type: n max_load: 100 factor: 1 insert_machine: lily type: n max_load: 80 factor: . only the reduced load portion (or slices) will be used in the virtual machine “mustang.9 The following JIL statements define a virtual machine named “mustang” which is composed of slices.” insert_machine: mustang type: v machine: fiat max_load: 10 machine: lotus max_load: 9 mustang fiat 10 lotus 9 Load Balancing and Queing Jobs 10–9 .Defining a Virtual Machine The following illustration defines a virtual NT machine named “garden” comprised of two real Windows machines named “rose” and “lily”. or subsets.” Even though the real machines have been previously defined. of the real machines named “fiat” and “lotus. Insert machine: garden type: n machine: rose machine: lily The following JIL statements define the two real NT machines.

10–10 User Guide . To delete the entire virtual machine. its individual definition still remains in effect. you specify the virtual machine and the desired component. their individual definitions remain in effect. you don’t have to specify any of the component real machines. The following JIL statement deletes the virtual machine named “mustang”: delete_machine: mustang Because the real machines “fiat” and “lotus” had been individually defined outside of the virtual machine.Defining a Virtual Machine Deleting Virtual Machines To delete a real machine component of a virtual machine. The following JIL statements delete only the real machine named “lambo” found within the virtual machine named “modena”: delete_machine: modena machine: lambo If the machine “lambo” had been individually defined outside of the virtual machine. The real machines are still defined—only the virtual machine they were in is deleted.

the factor attribute is not specified for either machine. When a job is ready to start.Load Balancing Load Balancing By specifying a virtual machine or a list of real machines in a job’s machine attribute.0. Determines the percentage of CPU cycles available on each real machine in the specified virtual machine. To accomplish this. Chooses the machine with the largest result (for example. The following JIL example shows the job definition statements for such a job: insert_job: test_load machine: modena command: echo "Test Load Balancing" job_load: 50 priority: 1 where: modena Is a virtual machine. Load Balancing and Queing Jobs 10–11 . Unicenter AutoSys JM would choose the machine to run on based solely on available processing power. That is. In addition to load balancing. rather than a single real machine. Alternatively. including available CPU cycles. In the example machine list previously shown. if all machines are Windows or UNIX — not a combination of the two. you can specify a list of real machines in the job’s machine attribute. 3. This is accomplished by opening a special key named HKEY_PERFORMANCE_DATA in the NT Registry. For example. load balancing will run the job on another machine. 2. if one of the machines is down. Unicenter AutoSys JM does the following: 1. you can implement simple load balancing. based on each machine’s capabilities. the machine with the most relative processing cycles available). Unicenter AutoSys JM will determine which of the specified machines is best suited to run the job. this feature is useful way to ensure reliable job processing. which provides a variety of system performance data. and thus the default factor value for each machine is 1. lambo If the max_load attribute was not defined for either real machine (as in our example). or both machines had ample load units available. you can cause the work load to be spread across multiple machines. Multiplies it by the machine’s factor value. as shown below: machine: ferrari.

italia ferrari alfa_romeo lambo 1.3 factors The following JIL statements can be used to define this machine: insert_machine: italia machine: ferrari factor: 1 machine: alfa_romeo factor: . the values can vary between machines. and the new construct is immediately applied globally. it is equivalent to defining a job and specifying the following in the machine field: machine: ferrari. In all likelihood. simply specify “italia” as the machine attribute for the job.8 0.80]=64> <lambo=2*[. and reflect these calculations in its output log.0 0. lambo The advantages of building a virtual machine are that it can be changed.00]=78> <alfa_romeo=80*[. Also. Even when a set of real machines that have not been explicitly defined to Unicenter AutoSys JM are specified in a job’s machine attribute.8 machine: lambo factor: . The following illustration shows three machines having different capabilities.30]=06> [ferrari connected] EVENT: CHANGE_STATUS STATUS: STARTING JOB: test_mach 10–12 User Guide . The output is similar to: EVENT: STARTJOB JOB: test_mach Checking Machine usages using NT Performance Method :<ferrari=78*[1. The Event Processor will perform the necessary calculations to determine on which machine to run the job. so you will need to specify the factor attribute value for each real machine. your system configuration will include machines of varying processing power.Load Balancing If the machines have equal max_load and factor values.3 To start a job on this virtual machine. the available CPU cycles are used to determine which machine will run the job. which are grouped into a virtual machine.

You can also issue a “change priority” event to change the priority of a job in the queue. Unicenter AutoSys JM will start the job right away on the machine specified in the job definition. Instead. Job-1 will run to completion (either success or failure). Thus. on Sunday you placed this job ON_HOLD. and subsequent interaction. The following sections discuss queuing jobs and give examples of how load balancing and queuing are used to optimize job processing in your environment. If the job was defined to run on a virtual machine. the status/condition does not change back to the previous condition.8).M.Force Starting Jobs Note that even though the “ferrari” usage was less than “alfa_romeo”. “ferrari” was picked because of the factors (78 * 1. upon completion (either success or failure).. If you FORCE_START Job-1 on Wednesday at 2:00 P. Note: If you FORCE_START a job that has a status of ON_ICE or ON_HOLD. the factors weigh each machine to account for variations in processing power. however. of the two job attributes job_load and priority. Load Balancing and Queing Jobs 10–13 . and then run again as scheduled on Monday at 3:00 A. even if the job_load of the job exceeds the max_load defined for the machine. Queuing policies are established through the use. or a list of real machines. regardless of the current load on the machine or the job_load specified for the job. Unicenter AutoSys JM will determine which machine has the most processing power available and will run the job on that machine. Queuing Jobs Queuing jobs in Unicenter AutoSys JM is a mechanism for ordering jobs that are unable to be run immediately. jobs are chosen based on queuing policies. and the two machine attributes max_load and factor. Force Starting Jobs If you force start a job. For example: You scheduled Job-1 to run every Monday at 3:00 A. There is no actual “queue” entity.M.M.0 > 80 * 0.

If any of the starting conditions are no longer true. and removed from all other queues. the job will be placed “on queue” for both (or all) machines. if only one of the machines has sufficient load units.Queuing Jobs Queuing and Simple Load Limiting If a job has been assigned a job_load value (the load limiting feature). Unicenter AutoSys JM will first determine whether each machine has sufficient available load units before running the job. “jobB” would be in a QUE_WAIT state until “jobA” completed and “jobB” could run. If no machines have sufficient load units. job loads will still be tracked on each machine. again checks all the job’s starting conditions to ensure it is still okay to run the job. However. the job is run on that machine. However. The words “in the queue” refer to an actual QUE_WAIT job status. all jobs must have their priority attribute set. This is done so that jobs that do have non-zero priorities will still be queued. By default. it is important to note that even when jobs have a priority of 0. a simple queuing example would be as follows: insert_job: jobA machine: fiat job_load: 80 priority: 1 insert_job: jobB machine: fiat job_load: 90 priority: 1 If “jobA” was running when “jobB” started. 10–14 User Guide . but be run immediately. and the job will stay in this state until the necessary load units become available. Note: In order for any queuing to take place. Unicenter AutoSys JM employs the load balancing and “factor” algorithms to determine on which machine it should start. the priority attribute is set to 0 indicating that the job should not be queued. the job will be run on that machine. the following message is generated: Job: job_name Starting Conditions are no longer TRUE. When one machine becomes available. When the necessary load units become available. When this is the case. If each real machine has sufficient load units. and a max_load attribute is assigned to every real machine comprising a virtual machine. Using a previously defined machine named “fiat” with a max_load of “100”. even jobs whose job load would push the machine over its load limit will be run. De-Queuing this Job and setting to ACTIVATED.

Note: The constructs of job loads and machine loads are merely conventions that you set up. the priority attribute should always be set. which does inspect the CPU to determine its usage. and that are enforced. Obviously. so when load limiting is in use. When there is no priority value assigned to a job (default is 0). To change the job queue priority. Therefore. It is important to note that if there is no job_load value set for a job. If you do not indicate what the load of a job is. the priority value is considered first when deciding which job to run next. Load Balancing and Queing Jobs 10–15 . there is no queuing and AutoSys starts the job immediately. it will not figure it into its queuing calculations. In the case where a job has its job_load attribute set. it will not be figured into the total load units running on a machine. the job will never go into the QUE_WAIT state. the job would run regardless of the current load on the machine. and lower priority jobs will be considered subsequently. the load value will be reflected in the total load running on a machine. do not force start the job. If the job’s priority was set to run immediately. If there are insufficient load units (job_load value) available to run the highest priority job. it will remain in the queue.Queuing Jobs Note: If a job is in the QUE_WAIT state and you want to run it immediately. this interferes with the load limiting feature. This is different from the load balancing feature. Queuing with Priority When more than one job is queued. use the sendevent command with the -E CHANGE_PRIORITY option.

and the max_load of the machine. The numbers in the figure indicate the job_load assigned to each job. so either “JobA” or “JobD” could be run. Since “JobA” has a higher priority (lower value = higher priority). “JobB” and “JobC” are already running because their starting conditions were satisfied first. In this example. so only “JobD” could be run. If “JobB” finishes first. if “JobC” finishes first. waiting for available load units. The resulting scenario will differ. “JobA” or “JobD”. QUE_WAIT EXECUTE JobA 50 JobD 30 JobB 50 JobC 30 80 max_load insert_machine: ferrari max_load: 80 insert_job: JobA machine: ferrari job_load: 50 priority: 60 insert_job: JobB machine: ferrari job_load: 50 priority: 50 insert_job: JobC machine: ferrari job_load: 30 priority: 80 insert_job: JobD machine: ferrari job_load: 30 priority: 70 In the previously shown illustration. it will run first. Which job will start. only 30 load units become available. 10–16 User Guide . The JIL statements provided below define the machine and the jobs. “JobA” or “JobD” will start. and the max_load machine attribute. After “JobB” or “JobC” are completed. is determined by a combination of the priority and job_load attributes of each job. “JobB” and “JobC” are executing while “JobA” and “JobD” are “queued” (in the QUE_WAIT state). 50 load units become available. However. and multiple jobs are waiting to start. based on which job finishes first.Queuing Jobs The following illustration shows a situation where a machine has 80 load units.

Queuing Jobs Subsets—Individual Queues One variety of virtual machine can be considered a subset of a real machine. this type of virtual machine is used to construct an individual queue on a given machine. One use for this construct might be to limit the number of jobs. For example. you would first create the virtual machine named “ferrari_printQ”. but you want only one job to run on a machine at a time. since each job requires all of the load units available on the specified machine. you would define the three print jobs. like: insert_job: Print1 machine: ferrari_printQ job_load: 15 priority: 1 insert_job: Print2 machine: ferrari_printQ job_load: 15 priority: 1 insert_job: Print3 machine: ferrari_printQ job_load: 15 priority: 2 Using this definition. Load Balancing and Queing Jobs 10–17 . The JIL statements to define the queue. You can accomplish this by using a combination of the max_load attribute for the virtual machine and the job_load attribute for the jobs themselves. like: insert_machine: ferrari_printQ machine: ferrari max_load: 15 Next. you have created three different print jobs. The following illustration shows a virtual machine functioning as a queue. called “ferrari_printQ” follow the graphic. only one of the jobs would run on “ferrari” at one time. Typically. that will run on a machine at any given time. of a certain type. ferrari_printQ ferrari 80 15 To implement the schema. Note that “ferrari” is a real machine.

In the above example. 10–18 User Guide . In the case that there are enough available load units on both machines. A possible need for this would be if there were two machines that were print servers. you would first create the virtual machine named “printQ”. “ferrari” and “lambo” as shown in the following example: insert_machine: printQ type: v machine: ferrari max_load: 15 machine: lambo max_load: 15 As a job is logically ready to start on printQ. printQ ferrari 80 lambo 15 120 15 To implement the above illustration. and start it when there are enough load units. it will place the job in the QUE_WAIT state. then you would specify two real machines. Multiple Machine Queues Virtual machines can also be constructed to allow subsets (or slices) of real machines to be combined into one virtual machine. The following illustration shows this situation. this means that the virtual load of 15 does not subtract from the load units of 80 for the real machine. and start the job on the machine with the most available CPU resources.Queuing Jobs Load Units and Virtual Machines It is important to note that the load units associated with a virtual machine have no interaction with the load units for the real machine. on each of which only one print job was to run at a time. If there are not. Load units are simply a convention which allows the user to constrict concurrent jobs running on any one machine. If there are enough units on only one machine. it will start it on that machine. Unicenter AutoSys JM will determine the usage on each. Unicenter AutoSys JM will determine if there are enough load units available on either machine.

you cannot use the priority or job_load job attributes. and the job will be run on that machine. For example. and it will substitute its output for the machine name.User-Defined Load Balancing User-Defined Load Balancing As an alternative to using the provided load balancing methods described in this chapter.BAT" command: %HOME%\DEL_STUFF. the "C:\USERS\DEFAULT\PICK_MACHINE. the Event Processor will execute the batch file at job runtime. The standard output will be substituted for the name of the machine.BAT" batch file is run on the Event Processor machine. you might supply the following: insert_job: run_free machine: "C:\USERS\DEFAULT\PICK_MACHINE.BAT At runtime. Load Balancing and Queing Jobs 10–19 . you can write your own programs or batch files to determine which machine to use at runtime. Note: If you specify a user-defined load balancing script in the machine attribute. If you specify the name of a program or batch file as the machine name in the job’s machine specification.

.

and you can define a filter to use in the Scheduler Console. In addition. the Filter Editor is opened. from the Scheduler Console you can select any job and view more detailed information about it. and autorep reports. You can also open several utilities and tools from the Scheduler Console. dependent jobs. To open the Scheduler Console: Click Scheduler Console on the GUI Control Panel. For information on using the Filter Editor. Using the Scheduler Console The Scheduler Console provides a sophisticated method of monitoring jobs from multiple instances in real time. If you choose No. These filters are based on various parameters. and the machine on which the job runs. whether or not they are currently active. such as the current job state. You can create filters that allow you to control the jobs displayed in the Scheduler Console. You can change the current filter to change the jobs displayed in the console. you will be prompted to choose whether you want to open the Scheduler Console using the Default Filter.Chapter 11 Scheduler Console This chapter describes how to use the Scheduler Console to monitor and control job runs in real-time. the job name. including its starting conditions. If you are opening the Scheduler Console for the first time. Scheduler Console 11–1 . The Scheduler Console lets you view any jobs that are defined. This action opens a window similar to the illistration following. The Scheduler Console allows you to access job information from multiple instances. see Defining Scheduler Console Filters in this chapter.

For information on setting the interval for Auto Refresh. Note: By default. Control area The area below the menu bar that contains the drop-down list of defined filters and the action buttons you have selected to display. and the job list is updated every 60 seconds. Summary area or job list The area at the center of the window which displays a list of all jobs stored in the database. 11–2 User Guide . see Using the General Dialog. You can populate this “action area” with action buttons and user-defined action buttons. subject to the filter currently in effect. the Scheduler Console starts up with Auto Refresh on.Using the Scheduler Console The following image is the Schedule Console: The Scheduler Console has the following three areas: Menu bar The area that is at the top of the window.

Actions Menu The Actions menu contains a list of actions that you can perform on the selected jobs in the job list area. Applications. Filters Menu The Filters menu has the following option: Filter Editor Opens the Filter Editor dialog. see Filters Editor Dialog in this chapter. Exit Exits the Scheduler Console and closes all database connections that it has established. Note: The first time you connect to an instance in a session. do not use it on jobs in boxes. Tools. Use this dialog to define. Preferences. This action ignores Date/Time starting conditions. Reports. File Menu The File menu has the following options: New Unicenter AutoSys Scheduler Console Opens another Scheduler Console window.Using the Scheduler Console Using the Scheduler Console Menu Bar At the top of the Scheduler Console is the menu bar. For information on defining filters. Scheduler Console 11–3 . and Help. and delete filters. a database connection is established. Filters. You can only use this option to start toplevel jobs. which contains the following menus: File. Actions. but it does not ignore job dependency starting conditions. These are the Actions menu options: Start Job Starts the selected jobs if the Dependencies starting conditions are met. and it is maintained until you close the Scheduler Console. Filters define the jobs you want to appear in the job list area. Choosing this option is equal to sending a STARTJOB event. modify.

You cannot place a job on hold if it is in STARTING or RUNNING state. 11–4 User Guide . and its action depends on the job type and the type of machine (UNIX or Windows) on which the job is running. On Hold Places the selected jobs on hold. When you take a job off ice. which is the functional equivalent of reactivating the job definition. Off Ice Takes the selected jobs off ice. which is the functional equivalent of deactivating the job definition. Choosing this option is equal to sending a JOB_OFF_ICE event. You cannot place a job on ice if it has a STARTING or RUNNING status. Choosing this option is equal to sending a KILLJOB event. see sendevent in the chapter “Commands” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. the jobs will be started. Choosing this option is equal to sending a FORCE_STARTJOB event. On Ice Places the selected jobs on ice. Choosing this option is equal to sending a JOB_ON_HOLD event. For more information about any of these events.Using the Scheduler Console Kill Job Kills the selected jobs. which means they cannot be started. Force Start Job Starts the selected jobs regardless of whether the starting conditions have been met. it will start the next time the starting conditions are met. Off Hold Takes the selected jobs off hold. If you choose this option and the selected jobs’ starting conditions have been met. Choosing this option is equal to sending a JOB_ON_ICE event. Choosing this option is equal to sending a JOB_OFF_HOLD event.

including information about the most recent. For information on the Job Editor. the starting Condition also displays.” in this guide. it contains the alarms for all instances it can access. You can also open a Run Status Tool for a specific Job by doubleclicking on the job in the summary area. Applications Menu The Applications menu has the following option: Alarm Manager Opens the Alarm Manager. see the chapter “Managing Alarms.Using the Scheduler Console Tools Menu The Tools menu allows you to open windows and dialogs that give you more information on a job. For information. Run Status Tool Opens the Run Status Tool for the selected job. The Run Status Tool displays a job summary. Job Editor Opens a Job Editor for the selected job. or allow you to modify a job. see Using the Job Dependencies Dialog in this chapter. which you can use to view alarms and change their status from Open to Acknowledged or Closed. or current. The menu has the following options: Dependent Jobs Opens the Job Dependencies dialog for the selected job. see Using the Send Event Tool in this chapter. This dialog shows the Current Job Name and the Predecessor Jobs and Successor Jobs. For information. see the chapter “Defining Jobs Using the Job Editor. Scheduler Console 11–5 . Using this dialog. When you select a job in this dialog. When you open the Alarm Manager from the Scheduler Console. see Using the Run Status Tool in this chapter. Send Event Opens the Send Event Tool for the selected job. run of the job.” in this guide. and you can cancel events that have been scheduled for a later time. you can send events. For information. For information on the Alarm Manager.

see Using the User Defined Buttons Dialog in this chapter. User Defined Commands Opens the User Defined Buttons dialog. 11–6 User Guide . see Using the General Dialog in this chapter. For information.Using the Scheduler Console Reports Menu The Reports menu allows you to run and view various job reports. The menu has the following options: Job Detail Report Opens the Job Detail Report tool for the selected job. and the button display. the button is placed in the control area at the top of the Scheduler Console window. see Using the Summary Area Layout Dialog in this chapter. in which you can set column length. For information. For information. Summary Area Layout Opens the Summary Area Layout dialog. the confirm action behavior. For information. column order. These buttons are shortcuts to sending events and opening tools. User Defined Reports Opens the User Defined Reports dialog. in which you can select the buttons that you want in the control area at the top of the Scheduler Console. This dialog displays a realtime report of the job run information (in the format of the autorep command output). For information. in which you can enter Report menu items and the command that they execute. see Using the Action Area Layout Dialog in this chapter. For information. The menu has the following options: General Opens the General dialog in which you can set the refresh interval (the default setting is 60 seconds). Preferences Menu The Preferences menu allows you to set user preferences and customize the Scheduler Console display. see Using the User Defined Reports Dialog in this chapter. and sort order for the summary area. Action Area Layout Opens the Action Area Layout dialog. in which you can enter button names and the commands they execute. see Using the Job Detail Report Tool in this chapter. When you enter a button Name and Command.

AutoRefresh Indicates whether or not the Scheduler Console summary area should be updated automatically. This setting indicates that the Scheduler Console should be updated based on the Refresh Interval setting in the General dialog. For more information. Help Menu The Help menu contains the following options: Contents Displays the table of contents for the Unicenter AutoSys JM Help. you can check the AutoRefresh option. which controls the time zone used in the display: Local Time. To update the display. Currently Selected Job. About Displays the Scheduler Console version number. If you uncheck the AutoRefresh option. or you can click the Refresh button (if you indicated to have the button in the action area). By default. Scheduler Console 11–7 . Note: The Time Perspective affects the Start Time and Last Change display in the summary area. AutoRefresh is selected (set to on). see Setting the Time Perspective in this chapter.Using the Scheduler Console Time Perspective Allows you to select one of the following time perspectives. or Currently Selected Instance. the Console display is not updated automatically. setting it to off.

■ ■ – Using the Summary Area The summary area displays a list of all the jobs that are defined. For information. User-Defined Commands. all buttons are displayed the first time you open the Scheduler Console. User-defined buttons that execute assigned commands. by using the User Defined Button dialog. click on the filter name in the filter list. The control area contains the following items: ■ The drop-down list of defined filters.Using the Scheduler Console Using the Control Area The control area is located below the Scheduler Console menu bar. 11–8 User Guide . The action area. You define the set of buttons that appear in the area using the Action Area Layout dialog. subject to the currently selected filter. To define or modify a filter. The default color for alarms is red. use the Filter Editor (described in Defining Scheduler Console Filters in this chapter). across multiple machines and multiple instances. The Refresh button. see Using the Action Area Layout Dialog in this chapter. which you can open from Preferences. which you can open from the Control Panel Preferences. see Using the User-Defined Buttons Dialog in this chapter. An alarm is generated when a job completes with FAILURE or TERMINATED status. its line turns the color specified in the Control Panel Colors dialog. Colors menu item. To change the summary display. basing it on a different filter. You define the set of buttons that appear in the area and the commands that they execute. which you can populate with the following: – Buttons that open tools or send events on the selected jobs. For information. The list of jobs in the summary area provides a snapshot of the system. which you can click to update the display with the most current database information. When a job generates an alarm. By default.

You can double-click on a job to open the Run Status Tool to view the job information (see Using the Run Status Tool in this chapter). see Setting the Time Perspective in this chapter. In addition. based on the Time Perspective. For more information. or any buttons you have added to the action area at the top of the Scheduler Console. the highlighted job becomes the currently selected job. This menu will also contain a list of your userdefined buttons that allow you to execute the command from this menu. When the Scheduler Console is reading the database (refreshing or changing filters) an asterisk appears at the end of the date time statement. You can right-click on any job to get a menu of actions you can perform on that job and tools you can open. Scheduler Console 11–9 . and you can open the dialogs and applications located on the Tools and Applications menus to get more information on the selected job. see Using the User-Defined Buttons Dialog in this chapter. the status bar of the Scheduler Console shows the appropriate time. by using the Actions menu options. you can select multiple jobs from the list and perform actions on them. Note: When you select a job from the list. or Box) Start Time (based on the Time Perspective) Job ID Selecting Jobs When you select a job from the list. the Send Event Tool.Using the Scheduler Console Summary Area Information Each entry in the summary area contains the following job-specific information: ■ ■ ■ ■ ■ ■ ■ ■ Job Name Instance (to which the job is defined) Status (Current) Last Change (based on the Time Perspective) Machine (on which it last ran or is currently running) Type (Job. FW. For information on user-defined buttons.

■ To select noncontiguous multiple jobs: Press the Control key and click each job you want to select. 11–10 User Guide . you can resize the columns and change the sort order. click on the jobs at the end of a desired range to select a group of jobs. see Using the Summary Area Layout Dialog in this chapter. For more information. on the Preferences menu. Note: The summary area has a scroll bar along the right side for scrolling through the job list. you can resize the titles by dragging the edges. In addition. Using the Summary Area Layout dialog. ■ To deselect all the currently selected jobs: Click anywhere in the job list. ■ To select contiguous multiple jobs: Press and hold the shift key. Pressing the Control key and clicking a selected job deselects that job.Using the Scheduler Console ■ To select a job: Click the job in the summary area job list display.

you use the Filter Editor. Filter Editor. and modify filter definitions. To do this. on all defined machines. and for all locally defined (installed) instances. with all statuses. You can define any number of filters to control the jobs that are displayed in the Scheduler Console summary area. The Default Filter includes all jobs. delete. This action opens a dialog similar to the following: Scheduler Console 11–11 . which allows you to filter by the following criteria: ■ ■ ■ ■ Names of jobs Status of jobs Machine on which jobs are to run Instances to which jobs belong You can use the Filter Editor to create.Defining Scheduler Console Filters Defining Scheduler Console Filters If you are opening the Scheduler Console for the first time. To open the Filter Editor: Choose Filters. you will be prompted to choose whether you want to open the Scheduler Console using the Default Filter.

which lists the defined filters. this option opens the Save As dialog. This deletes the Filter definition. displaying a dialog asking you if you want to save your last modifications when necessary. When you save for the first time. Save Saves the filter definition. You can select a filter to open. To delete a filter. but they are user-specific. Open Opens the Open Filter Criteria dialog. select it from the list.Defining Scheduler Console Filters Filters Editor Dialog The Filter Editor has a File menu and the following tabs: ■ ■ ■ Names Status Machine/Instance File Menu The File menu has the following options: New Opens a new Filter Editor. and click OK. so they are saved. which displays a list of defined filters. Exit Closes the Filter Editor. Delete Opens the Deleting Filters dialog. and click OK. 11–12 User Guide . These filters apply to all installed instances. in which you can enter a new filter name and save it. Save As Opens the Save As dialog.

In addition. When selecting jobs based on box name. 0—Indicates that only the top-level box specified in the scrollable text box is to be displayed. If you use the wildcard character to specify all box names. the name of the nested box job will be listed multiple times in the summary area. Scheduler Console 11–13 . You can click one of the following radio buttons: All Jobs Selects all jobs that meet the other filtering criteria. press Enter. the indentation will display. you can enter the asterisk ( * ) wildcard character.” “Bat. Jobs in Boxes named Selects the jobs with the name or names you enter in the scrollable text box to the right of the button.Defining Scheduler Console Filters Names Tab Using the Filter Editor Names tab. and a box has other boxes inside of it. ■ ■ When specifying a job name in the scrollable text box. You can select one of the following settings: ■ All—Indicates that the box specified in the scrollable text box and all of its direct descendents (including nested boxes and the jobs in those boxes) are to be displayed. each contained level will be indented two spaces to indicate the nesting. press Enter. the levels of box jobs will not display indentation correctly. Jobs named Selects the jobs with the name or names you enter in the scrollable text box to the right of the button. the entire job name. but the order will not be based on the jobs relationship to the containing box job. specifying the job name “*a*” would match the jobs “Dad. At the end of each entry. Note: If you have selected a Sort Key for the Summary Area Layout that is different from the default order (which is no sort order). For example. you can select the jobs you want to view by name.” “Bad. After entering each name. this selection enables the Maximum Depth field.” and so forth. or a partial name with the asterisk ( * ) wildcard character representing one or more characters. which allows you to indicate how many levels of nesting you want to view for all selected box jobs. 1 through 20—Indicates that the box specified in the scrollable text box and the selected number of levels of nesting are to be displayed. This is the default. You can use this wildcard in more than one character position.

you can select the jobs that you want displayed based on their current status. or you can select individual statuses. such as STARTING. You can select All Statuses. The All Statuses selection is the default setting. RUNNING. You can select any combination of the statuses.Defining Scheduler Console Filters Status Tab From the Filter Editor Status Tab (shown in the following illistration). and it is automatically deselected when you deselect any of the statuses listed below it (when all statuses are no longer selected). 11–14 User Guide . or INACTIVE.

is a list of instances to which this Scheduler Console can connect. you can select jobs based on the name of the machine on which they ran (or they are currently running). and then select the machines you want to include in the filter. you can select the instance or instances you want included in this filter. but you cannot use them to select jobs. because jobs can run only on real machines. you can choose one or several names to include in the filter. On the left side of this tab is a list of all the machines that are referenced in any job or machine definition for the instance. or which have run an AutoSys job. ■ To specify Machines from the list: Click the All Machines check box to uncheck it. Selecting Machines or Instances From the Machine or Instance list. Note: Virtual machines appear on the Machine list.Defining Scheduler Console Filters Machines/Instances Tab From the Filter Editor Machine/Instance tab (shown in the following illistration). All Instances is selected. On the right side of this tab. Scheduler Console 11–15 . By default. In addition. but you can uncheck the check box and select specific instances from the list of instances.

Defining Scheduler Console Filters ■ To specify Instances from the list: Click the All Instances check box to uncheck it. and then select the instances you want to include in the filter. the behavior is the same. Status. Choose Filters. and Machine/Instance tabs to specify the filter definition. ■ To choose multiple names. Filter Editor. or more names after your initial selection: Press the Ctrl key and click each name. or multiple names. 3. ■ To choose a single name: Click that name. and then drag the cursor to the last name and release the mouse button. Using the Filter Editor ■ To define a filter: 1. Note: Sorting order of the jobs listed in the summary area is controlled by the settings in the Summary Area Layout dialog. Save. 2. Choose File. When you are selecting machines or instances. 11–16 User Guide . see Using the Summary Area Layout Dialog in this chapter. This action opens a dialog similar to the one shown in Defining Scheduler Console Filters in this chapter. This action saves the filter definition. a range of names. For information about changing the settings. ■ To select a defined filter on which to base the summary area display: Select the name from the filter drop-down list at the top left of the Scheduler Console. ■ To choose a range of names: Press the mouse button and hold on the first name. In the Filter Editor. You can select a single name. This opens a Save As dialog in which you can enter the name of the filter. then click OK. use the Names.

with the exception of the Job Editor.” in this guide.Using Scheduler Console Tools Using Scheduler Console Tools The Tools menu contains the following options: ■ ■ ■ ■ Dependent Jobs (opens the Job Dependencies dialog) Job Editor Run Status Tool Send Event The following sections describe these tools. which is described in the chapter “Defining Jobs Using the Job Editor. Scheduler Console 11–17 .

Dependent Jobs. double-click on the job name in the list. the defined Dependencies for the selected job are listed in the Condition area. and to move between the displayed dependent jobs to see their defined Dependencies.Using Scheduler Console Tools Using the Job Dependencies Dialog The Job Dependencies dialog allows you to view the defined Dependencies of the selected job. To move to one of these jobs and see its Conditions and dependent jobs. In the Job Dependencies dialog. which include their status. In the area below that. and choose Tools. ■ To open the Job Dependencies dialog: Select a job. ■ To close the Job Dependencies dialog: Click OK. and that newly selected job and its dependencies will be displayed in the dialog. This action opens a dialog like the one shown in the following illistration. you can view lists of the Predecessor Jobs and the Successor Jobs. but you can select other jobs from the summary area. it stays on top. When you open this dialog. 11–18 User Guide .

For example. if a job has not run within the time frame it was expected to. or to see what effect a problem might have. you could select the job from the job list and check its starting conditions to quickly determine what predecessor jobs might be preventing it from running.Using Scheduler Console Tools This dialog allows you to move quickly up and down the flow of dependent jobs in order to locate the problem in a job run. Scheduler Console 11–19 .

Run Status Tool. the first job you selected will be the currently selected job. These actions open a dialog similar to the one shown in the Run Status Tool. In addition. Note: If you selected multiple jobs. 11–20 User Guide .Using Scheduler Console Tools Using the Run Status Tool You can use the Run Status Tool to view comprehensive information about the most recent run (or the current run) of the selected job. Double-click a job. and choose Tools. To open the Run Status Tool: ■ ■ Select a job. Auto Refresh must be on in order for the information in the Run Status Tool to update in real time.

see Using the Send Event Tool in this chapter. For more information. File Menu The File menu has the following options: New Run Status Tool Opens a new Run Status Tool. Options. you can send events. For information. see the chapter “Defining Jobs Using the Job Editor. Scheduler Console 11–21 . The default setting is on.” in this guide. Using this dialog. the Run Status Tool does not update with new selections. Help Menu The Help menu has the following options: Contents Displays the table of contents for the Help. If you toggle this option to off (unchecked). Tools Menu The Tools menu has the following option: Send Event Tool Opens the Send Event Tool for the selected job. About Displays the Run Status Tool version number. This new Run Status Tool will update when you select a job. Applications Menu The Applications menu contains the following option: Job Editor Opens a Job Editor for the current job. Tools. Applications. Options Menu The Options menu has the following option: Adopt Session Context Toggles the session context feature on or off.Using Scheduler Console Tools Run Status Tool Menu Bar The Run Status Tool has the following menus: File. and when this is the case and you select a job from the Scheduler Console or the Alarm Manager. and you can cancel events that you have scheduled for a later time. Exit Closes the Run Status Tool. the open Run Status Tool updates to reflect the selected job. and Help.

If the job is currently running. If the job is a file watcher job. Start Time The start time of the current. Instance The name of the instance for which this job is defined.Using Scheduler Console Tools Run Status Tool Display Fields The following sections describe the fields in this dialog: Job Name The name of the selected job. Run Machine The name of the machine on which the job ran or is currently running. End Time The end time of the most recent run of the job. the number of times it was started appears here. Run Time How much time elapsed between the start and end of the most recent run of the job. This information is very useful when troubleshooting a job. Starting Conditions The job’s entire starting condition. this field is blank. Command The command to be executed for command jobs. the name of the real machine component on which it actually ran will appear here. Exit Code The exit code from the most recent run of the job. this field is blank. as specified in its job definition as well as the “atomic” conditions. 11–22 User Guide . Try Count If the job had to be restarted. which are the most basic components of an overall condition. If a job is defined to run on a virtual machine. Description The description text entered in the Job Editor Description field or with the description job attribute with JIL. If the job is a box job. the file it is watching for appears here. or the most recent run of the job. this field will be blank. If the job is currently running.

Scheduler Console 11–23 . Queue Name If the job is queued to start on a machine. Cancel an event that has been scheduled to occur in the future. Select the various event parameters you want to specify when sending the event. Using the Send Event Tool Using the Send Event Tool. For more job flow information. Next Start If the job has date and time starting conditions. This information is in addition to the Starting Conditions information (previously discussed). its priority in the queue appears here. you must have execute permission on the selected job. the name of that machine appears here.Using Scheduler Console Tools Status The current status of the job. Priority If the job is queued to start on a machine. Predecessor and Successor Jobs A list of predecessor jobs and successor jobs and their conditions and status. you can do the following: ■ ■ Send any event that can be sent manually. use the Job Dependencies dialog (described in Using the Job Dependencies Dialog in this chapter). ■ Note: To send an event on a job. this field shows when the next run of the job is scheduled to start.

The Send Event Tool has a menu bar and several fields. For basic Send Event Tool usage information. Send Event. if the Send Event Tool is set to Adopt Session Context (on its Options menu). you can click on a job in the Scheduler Console to associate a job with the tool. Note: If you do not select a job before you open choose Send Event. This action opens a dialog like the one shown in this chapter. 11–24 User Guide . a Send Event Tool opens that does not have an associated job. see Sending an Event and Canceling a Send Event. or.Using Scheduler Console Tools Opening the Send Event Tool To open the Send Event Tool: Select a job and choose Tools. You can enter a Job Name in the Send Event Tool.

File Menu The File menu contains the following options: New Send Event Tool Opens a new Send Event Tool that is not associated with a job. Scheduler Console 11–25 .Using Scheduler Console Tools Send Event Tool Menu Bar The menu bar contains the following menus: File. Help Menu The Help menu contains the following options: Contents Displays the table of contents for the Unicenter AutoSys JM Help. the Send Event Tool updates to reflect the selected job. and you must manually change the name or open a new tool for other jobs. the Send Event Tool does not update. If the option is off (unchecked). If this option is selected (checked). Options. About Displays the Send Event Tool version number. and Help. Options Menu The Options menu contains the following option: Adopt Session Context Determines if the Send Event Tool will associate with the selected job in any open Scheduler Console or Alarm Manager window. Exit Closes the tool.

regardless of its starting conditions. Job On Hold Places the selected jobs on hold. or you can select another job from the Scheduler Console summary area. This does not stop the database service. selecting the event from the list in the Event Type area. Choosing this option is equal to sending a COMMENT event. If you have selected multiple jobs. the jobs will be started. You cannot place a job on hold if it has a STARTED or RUNNING status. or with the condition JIL attribute). If desired. You can send the event now. Choosing this option is equal to sending a STOP_DEMON event. That is. the name of the first one you selected appears in the Job Name field. If you want to start a job immediately. but it does not ignore dependencies on other jobs (set in the Job Editor Dependencies field. Job Off Hold Takes the selected jobs off hold. These are the Event Types you can send: Start Job Starts the selected jobs if their Dependencies are satisfied. Stop Demon Stops the event processor for the selected instance. you can enter the name of a different job in this field. Comment Attaches the message in the Comment field of the Send Event Tool to the specified job for its next run.Using Scheduler Console Tools Send Event Tool Fields Using the Send Event Tool. the Job Name field at the top of the tool contains the name of the currently selected job. you can send one event at a time. but all selected jobs will be affected by the event sent. which is the job on which you will send the event. which means they cannot be started. this event ignores time and date conditions. By default. Choosing this option is equal to sending a STARTJOB event. 11–26 User Guide . use the Force Start Job option. If you choose this option and the selected jobs have starting conditions that have been met. or you can determine a future date to send it. Choosing this option is equal to sending a JOB_OFF_HOLD event. Choosing this option is equal to sending a JOB_ON_HOLD event.

you must also select the status to change to from the Send Event Tool Status drop-down list. If a job has not been started. Choosing this option is equal to sending a FORCE_STARTJOB event. Choosing this option is equal to sending a JOB_OFF_ICE event. which is the functional equivalent of reactivating the job definitions. You cannot place a job on ice if it has a STARTED or RUNNING status. Choosing this option is equal to sending a CHANGE_STATUS event. Kill Job Kills the selected jobs. Choosing this option is equal to sending a KILLJOB event. In addition. Job On Ice Places the selected jobs on ice. and is in a queue. Choosing this option is equal to sending a CHANGE_PRIORITY event. which is the functional equivalent of deactivating the job definitions. The lower the number. and its action depends on the type of the job on which you are sending the event.Using Scheduler Console Tools Force Start Job Starts the selected jobs regardless of whether any of the starting conditions have been met. the priority is changed immediately. If a job has been started. the priority is changed for the next run only. Job Off Ice Takes the selected jobs off ice. Change Status Forces a change in the status of the selected jobs. if you use this option. Change Priority Changes the priority of the selected jobs to the one specified in the Send Event Tool Queue Priority field. If you do select this option. Choosing this option is equal to sending a JOB_ON_ICE event. Scheduler Console 11–27 . zero means to run the job right away. the higher the priority. it will start the next time the starting conditions are met. Ordinarily this option should not be used because Unicenter AutoSys JM manages job state changes internally. Queue priority is the relative priority of all jobs in the queue. you will need to send another Change Status event to change the status back to what it was. When you take a job off ice.

Send Signal Sends the UNIX signal specified in the Send Event Tool Signal field to the selected jobs that are running on UNIX machines. then indicating a time). if you force a job to start. Choosing this options is equal to sending a SET_GLOBAL event. For information. see Canceling a Sent Event in this chapter. Comment A free-form field in which you can enter any text you want to associate with this event in the database. Match On Time Indicates that the event or events you are canceling are based on the Time you indicate in the Future field area. The Time entry must be in 24-hour format. or cancel a specific event (or events) by scheduled time (by selecting an Event Type and the Match On Time check box. see the section sendevent in the chapter “Commands” in the Unicenter AutoSys Job Management Reference Guide. see Canceling a Sent Event in this chapter. or at some Future time and date. Now or Future You can specify when the event is to take effect. either Now (the default). For information. This field is for documentation purposes only. You can either cancel a specific event (by choosing an event from the Event Types list). For more information about any of these events. These are the other Send Event Tool fields: Cancel Previously Sent Event Cancel one or more events scheduled to occur sometime in the future. you might provide an explanation about why this was necessary.Using Scheduler Console Tools Set Global Sets an global variable to the variable indicated in the Send Event Tool Global Name and Global Value fields. For example. The Global Name and Global Value can each be a maximum of 30 characters. 11–28 User Guide . Choosing this option is equal to sending a SEND_SIGNAL event. The current time and date are provided as examples of the required format. This event is ignored if the job is running on a Windows machine. You can do this in one of two ways. This event is sent with a high priority so that the event processor will process the variable before it is referenced by any jobs at runtime.

Click Send. Enter a Comment if desired. 2. This action sends the event type you selected at the date and time you indicated. the event. Choose Send Priority from the drop-down list. either the Normal or High. the Send Event Tool is closed. the Send Event Tool will send the chosen event on all of the selected jobs. The Time entry should be in a 24-hour format. 7. 4. Choose an Event Type. Scheduler Console 11–29 . The Close button closes the dialog without sending the event. Send Priority Indicates whether the selected event should be sent with a Normal or High priority. 6. 5. 3. there are two buttons: Send and Close. When events need to be sent to a different instance.Using Scheduler Console Tools Instance The AUTOSERV instance name for the currently selected job. The Send button of the dialog executes. Make sure that you have the appropriate Instance selected. Choose Now or Future. enter a Date and Time. If you click on either button. If you do so. choose another instance from the drop-down list. This event is sent to the database for the selected job. Sending an Event To send an event using the Send Event Tool: 1. Make sure you have the appropriate job in the Job Name field. If you choose Future. At the bottom of the Send Event Tool. or sends. Note: You can select multiple jobs in the Scheduler Console before you open the Send Event Tool.

If you want to override a scheduled starting condition for a job. Select an Event Type radio button. 4. You can do this in one of two ways: by canceling a specific event or by canceling a specific event by its scheduled time. ■ To cancel an event by its scheduled time: 1. Note: You can select multiple jobs in the Scheduler Console before you open the Send Event Tool. ■ To cancel a specific event: 1. Note: You can select multiple jobs in the Scheduler Console before you open the Send Event Tool. Click Send.Using Scheduler Console Tools Canceling a Sent Event From the Send Event Tool. In the Event Type region. the Send Event Tool will send this cancel event on all of the selected jobs that meet the Event Type and Time criteria. Select the Cancel Previously Sent Event check box. If you do so. Note: You should use this feature to cancel events that you have sent from the Send Event Tool. 3. Make sure you have the appropriate job in the Job Name field. the Send Event Tool will send this cancel event on all of the selected jobs that meet the Event Type criteria. Make sure you have the appropriate job in the Job Name field. 2. 2. This process cancels all pending events of the specified Event Type for the selected jobs. either from the Job Editor or from JIL. If you do so. indicating the type of event to be cancelled. you can cancel one or more events scheduled to occur sometime in the future. you should use the one time override job attribute. specify an event type by selecting one of the radio buttons. 11–30 User Guide . Select the Cancel Previously Sent Event check box. 3.

Click Send. 6. you cancel the 11:00 Start Job event. In the Time field. For example. If you cancel a future Start Job event for a time-dependent job with no other starting conditions. jobA starts at 11:00 on Monday and completes at 11:30. The job not only does not run at 11:00 on Tuesday. Select the Match on Time check box.Using Scheduler Console Tools 4. but it will not be scheduled to run again. at which time the next future Start Job event is set for 11:00 Tuesday. you should use the one time override job attribute. At 9:00 on Tuesday. The Time entry must be in 24-hour format. If you want to override a scheduled starting condition for a job. the job may never run again without manually starting it with a Send Event command. 5. Scheduler Console 11–31 . either from the Job Editor or from JIL. you can either update its job definition or manually issue a Start Job Send Event. This process cancels all pending events of the specified Event Type at the specified Time for the selected jobs. Notes on Canceling a Send Event The Cancel Previously Sent Event feature is designed to be used primarily on events that you have sent from the Send Event Tool. To restart the job. indicate the scheduled event time you want to match. jobA is scheduled to run daily at 11:00.

The Job Detail Report tool has a menu bar and a display area. ■ To open the Job Detail Report tool: Choose Reports. It presents the following two types of reports. Event Displays a detailed report listing all the events and statuses from the last or current execution of the selected job. ■ To dismiss the tool: Click OK. which you can select from the drop-down list on the bottom right of the tool: Summary Displays a one-line synopsis of the last or current execution of the job.Using Scheduler Console Reports Using Scheduler Console Reports The Reports menu contains the following options: Job Detail Report Opens the Job Detail Report tool. Using the Job Detail Report Tool The Job Detail Report tool displays a realtime report for one currently selected job. Job Detail Report. This action opens a dialog similar to the one shown in the following figure. 11–32 User Guide . This report presents job run information in the same format produced by the autorep command.

Help Menu The Help menu has the following options: Contents Displays the table of contents for the Unicenter AutoSys JM Help. Applications Menu The Applications menu has the following option: Job Editor Opens a Job Editor for the selected job. and Help. see Using the Run Status Tool in this chapter. For information. see Using the Send Event Tool in this chapter. Applications. For information. For information. If this option is selected (checked). the Job Detail Report tool updates to reflect the selected job’s Job Name. see the chapter “Defining AutoSys Jobs Using the Job Editor.” in this guide. About Displays the version for the Job Detail Report. Options. Tools Menu The Tools menu has the following options: Send Event Opens a Send Event Tool for the selected job. the Job Detail Report tool does not update. Exit Closes the Job Detail Report tool. Options Menu The Options menu has the following option: Adopt Session Context Determines if the Job Detail Report tool will associate with the selected job in any open Scheduler Console or Alarm Manager windows. Scheduler Console 11–33 . Run Status Tool Opens a Run Status Tool for the selected job. Tools. If the option is off (unchecked).Using Scheduler Console Reports Job Detail Report Menu Bar The Job Detail Report tool has the following menus: File. and you must open a new tool to view other job information. File Menu The File menu has the following options: New Job Detail Report Opens another Job Detail Report tool for the selected job.

you can check the AutoRefresh option. AutoRefresh is selected (set to on). setting it to off. This setting indicates that the Scheduler Console should be updated based on the Refresh Interval setting in the General dialog. the Console display is not updated automatically. By default. If you uncheck the AutoRefresh option. User-Defined Commands Opens the User-Defined Buttons dialog (see Using the User-Defined Buttons Dialog in this chapter). 11–34 User Guide . Action Area Layout Opens the Action Area Layout dialog (see Using the Action Area Layout Dialog in this chapter). AutoRefresh You can toggle the AutoRefresh setting to determine if the Scheduler Console updates automatically.Setting Scheduler Console Preferences Setting Scheduler Console Preferences The Scheduler Console Preferences menu contains the following options: General Opens the General dialog (see Using the General Dialog in this chapter). Time Perspective Presents three submenu options (see Setting the Time Perspective in this chapter). or you can click the Refresh button. To update the display. Summary Area Layout Opens the Summary Area Layout dialog (see Using the Summary Area Layout Dialog in this chapter). User-Defined Reports Opens the User-Defined Reports dialog (see Using the User-Defined Reports Dialog in this chapter).

■ ■ ■ ■ To close the General dialog: Do one of the following: ■ Click OK to set the modified settings and dismiss the dialog. The Button Appearance. or Both. This setting indicates whether or not you want confirmation dialogs displayed when you click on any Action Area Layout buttons. The default setting is every 60 seconds. The Confirm action function. Icon Only. This action opens a dialog like the one shown in the following illistration.” which indicates that a confirmation dialog should be displayed before the execution of the actions. This setting indicates how often the Scheduler Console should refresh. To refresh.Setting Scheduler Console Preferences Using the General Dialog Using the General dialog. or choose any Action menu options. The default setting is “on. in seconds. To open the General dialog: Choose Preferences. Scheduler Console 11–35 . and the tool tip will contain the name of the button. or: ■ Click Cancel to make no changes and dismiss the dialog. You can set the action area and user-defined buttons to display Text Only. General. If you choose Icon Only. it reads the databases and updates the summary area job list. you can set the following for the Scheduler Console: ■ The Refresh interval. the user-defined buttons will all have the same icon.

and enter the command line. Click in the Command field. This action opens a dialog like the one shown in the following figure. 4. Use the $JOB variable for arguments that take a job name. In the dialog. and the selected job will be used when you click the button. and enter the name you want to appear on the button. Note: The button text can be 15 characters or less. 11–36 User Guide . and it can contain $JOB and $INST. This action puts a button with the specified name in the action area. Click OK. Choose Preferences. click in the Name field. Creating Command Buttons To create buttons: 1.Setting Scheduler Console Preferences Using the User-Defined Buttons Dialog You can use the User-Defined Buttons dialog to implement shortcuts to commands you use often. 2. Use the $INST variable for arguments that take the instance name. Note: You can create up to 20 user-defined buttons. Note: The command line can contain environment variables. and the selected instance will be used when you click the button. 3. User-Defined Commands.

Note: When you choose commands to execute from a user-defined button. Using AutoSys-Specific Commands If you want to use an command in the Command field of this dialog. you should use only persistent commands. you must use the following syntax: initautosys -i $INST -r "command_line" where : “command_line” Specifies the full command line. Use the $JOB variable for arguments that take a job name. and the selected instance will be used when you click the button.Setting Scheduler Console Preferences When you click the new button in the action area. Scheduler Console 11–37 . and it can contain $JOB and $INST. The command line can contain environment variables. and the selected job will be used when you click the button. it executes the specified command. Use the $INST variable for arguments that take the instance name. This command line must be in quotes.

and it can contain $JOB and $INST. 11–38 User Guide . 2. Note: The text can be 15 characters or less. 3. click in the Name field. and the selected instance will be used when you click the button. This action puts the option with the specified name on the Reports menu. User-Defined Reports. Choose Preferences. and enter the command line. Creating Reports Menu Items To create report menu items: 1. Use the $INST variable for arguments that take the instance name. In the dialog.Setting Scheduler Console Preferences Using the User Defined Reports Dialog You can use the User-Defined Reports dialog to implement a menu item on the Reports menu. and enter the name you want to appear on the Reports menu. Use the $JOB variable for arguments that take a job name. Click OK. Note: The command line can contain environment variables. Click in the Command field. This action opens a dialog like the one in the following illistration. 4. and the selected job will be used when you click the button.

you can modify the layout area in the window. (You can choose only the first. By default. Customizing the Summary Area in the Scheduler Console ■ To resize the summary area columns in the Scheduler Console: Drag the edges of the titles. or primary. ■ To select the primary sorting order: Click the title name by which you want the job list sorted.Setting Scheduler Console Preferences When you choose the new Reports menu item. Using the Summary Area Layout Dialog Using the Summary Area Layout dialog. and Sort Order. In addition to using the Summary Area Layout dialog to customize the display of the Scheduler Console. jobs appear in the summary area in the order they are pulled from the database. Scheduler Console 11–39 . category by which the list is sorted. You can set the Column Size. it executes the specified command. Column Order. customize the summary area further by using the Summary Area Layout dialog.) You can. you can customize the summary area display.

and the Column Order and Sort Key settings are relative to the other settings. and Sort Key. the indentation will display. The Column Length setting corresponds to the size of the column. Column Order. Each setting is based on the Column Name. This action opens a dialog like the following illistration: Using this dialog. ■ To close the dialog without saving the settings: Click Cancel. but the order will not be based on the jobs relationship to the containing box job. 11–40 User Guide .Setting Scheduler Console Preferences Customizing the Display with the Summary Area Layout Dialog ■ To open the Summary Area Layout dialog: Choose Preferences. ■ To save the settings you make in the Summary Area Layout dialog: Click OK. ■ To return to the default settings: Click Default. Summary Area Layout. you can set the Column Length. the levels of box jobs will not display indentation correctly. indicated on the left side of the dialog. Note: If you select a Sort Key for the Summary Area Layout that is different from the default order (which is no sort order).

and you can choose other levels of priority that will be used when appropriate: Job Name Jobs will be sorted by name in ascending alphanumeric order.Setting Scheduler Console Preferences Sort Key Settings The Summary Area Layout dialog allows you to specify the sort order in which the jobs should be listed. Start Time Jobs will be sorted by the starting time for the most recent execution of the job. or if there is no recent run data. Note: If you want to view levels of box jobs. you can choose one of the following as primary sort criteria. in ascending alphabetical order. in ascending alphabetical order. Last Change Jobs will be sorted by the date of their last change. and there is no indication of which jobs are in which box job. Machine Jobs will be sorted by the machine on which they run or have run. the time that it is scheduled to run. you should use the default sort order. in ascending alphabetical order. If you choose a sort order. Status Jobs will be sorted by their current status. the jobs are displayed in the order they are returned from the database. Scheduler Console 11–41 . Type Jobs will be sorted by the type of job. Instance Jobs will be sorted by their instance name. there is no sort order. To modify the sort order. you can modify this order. However. By default. which is no sort order. in ascending alphabetical order. the indenting of the various nesting levels for box jobs has no meaning. Job ID Jobs will be sorted in the order in which they were created.

By default. and after you click OK. If you have initiated an action on multiple jobs. This opens a dialog like the following illistration: Buttons in the action area for any of these tools or actions: Select the tools or actions. Action Area Layout. 11–42 User Guide . This puts the appropriate buttons in the action area. the confirmation dialog will display the list of jobs you have selected. the related dialog opens.Setting Scheduler Console Preferences Using the Action Area Layout Dialog The Action Area Layout dialog allows you to select the specific buttons you want to appear in the control area at the top of the Scheduler Console. When you click an action button. all of the buttons are selected to be displayed. the associated event is sent. a confirmation dialog displays. ■ To open the Action Area Layout dialog: Choose Preferences. and click OK. When you click a tool button in the action area.

For information.Setting Scheduler Console Preferences Action Area Layout Tool and Action Buttons From the Action Area Layout dialog. see the chapter “Defining Jobs Using the Job Editor. see Using the Send Event Tool in this chapter.” in this guide.. do not use it on jobs in boxes. Kill Job Kills the selected jobs... which allows you to send any type of event. You can only use this option to start top-level jobs. see Using the Job Dependencies Dialog in this chapter. but it does not ignore defined Dependencies. This action ignores Date/Time starting conditions. Opens the Send Event Tool. Choosing this option is equal to sending a STARTJOB event.... Job Editor. Job Detail Report. This dialog displays a realtime report of the job run information (in the format of the autorep command output). Opens the Job Dependencies dialog for the selected jobs. Scheduler Console 11–43 . Opens the Job Detail Report tool for the selected jobs. Force Start Job Starts the selected jobs regardless of whether the starting conditions have been met.. Dependent Jobs. see Using the Job Detail Report Tool in this chapter. Choosing this option is equal to sending a KILLJOB event. Start Job Starts the selected jobs if the defined Dependencies are met. For information on the Job Editor. you can select from the following tool and action buttons: Send Event. the starting Condition also displays. This dialog shows the Current Job Name and the Predecessor Jobs and Successor Jobs. For information. You can also double-click on the displayed jobs. When you select a job in this dialog. Opens a Job Editor with the selected jobs. to see their dependencies.. Choosing this option is equal to sending a FORCE_STARTJOB event. For information.

Choosing this option is equal to sending a JOB_ON_ICE event. Currently Selected Instance Displays the time based on the time zone of the database. 11–44 User Guide . On Ice Places the selected jobs on ice. Local Machine Time is used. it will start the next time the starting conditions are met. If you choose this option and the selected jobs have starting conditions that have been met. You cannot place a job on ice if it has a STARTED or RUNNING status. Choosing this option is equal to sending a JOB_OFF_HOLD event. If no time zone is set for the job. You cannot place a job on hold if it has a STARTED or RUNNING status. which means they cannot be started. Setting the Time Perspective The Time Perspective option has the following submenu options that control the time perspective of the summary area display: Local Time Displays the time in the time zone of the machine on which your Scheduler Console is running. Off Hold Takes the selected jobs off hold. Choosing this option is equal to sending a JOB_OFF_ICE event. the jobs will be started. Off Ice Takes the selected jobs off ice. which is the functional equivalent of deactivating the job definitions.Setting Scheduler Console Preferences On Hold Places the selected jobs on hold. Choosing this option is equal to sending a JOB_ON_HOLD event. When you take a job off ice. which is the functional equivalent of reactivating the job definitions. Currently Selected Job Displays the time using the time zone specified in the job definition (the timezone attribute). see Using the User Defined Buttons Dialog. Note: If you want to add your own buttons.

Setting Scheduler Console Preferences The Time Perspective that you choose appears in the status bar at the bottom of the Scheduler Console. Scheduler Console 11–45 . the Local Machine Time is used: ■ ■ Do not select a job. If it is based on a job. Select multiple jobs with different or no time zone settings. If you do either of the following. If it is based on an instance. the job name appears before the time in the display. the instance name appears before the time.

.

and they invoke no action on their own. To open the Alarm Sentry: Click Alarm Sentry in the GUI Control Panel. The following illistration shows the Alarm Sentry for one instances: Managing Alarms 12–1 . the button for an appropriate instance changes color. Your Alarm Sentry will have a button for each instance it can access. Using the Alarm Sentry The Alarm Sentry window displays a button for each instance that it can access. This action opens a window similar to the following figure. Alarms are information events.Chapter 12 Managing Alarms This chapter describes how to use the Alarm Sentry and the Alarm Manager to manage alarms. You can then click the button to open an Alarm Manager for that instance. These buttons serve both as alarm indicators and as a way to open the Alarm Manager for the specific instance. When an alarm event occurs.

About Displays the Alarm Sentry version number. 12–2 User Guide . Preferences Menu The Preferences menu contains the following option: General Opens the Refresh Interval dialog that you can use to set the time in seconds between refresh (updating the buttons based on the database information). the Alarm Sentry has a menu bar. In the button display area. You set the interval in seconds. and the default setting is every 60 seconds. File Menu The File menu contains the following option: Exit Closes the Alarm Sentry. and Help. Preferences. Using the Alarm Sentry Menu Bar The Alarm Sentry has the following menus: File. The number that follows the instance name specifies the number of open alarms that instance has.Using the Alarm Sentry In addition to the button area display. Help Menu The Help menu contains the following options: Contents Displays the table of contents for the Unicenter AutoSys JM Help. The status area at the bottom of the window indicates whether the Alarm sentry is updating or “done” updating. there is a button for each instance to which the Alarm Sentry can connect.

This feature provides a useful tracking mechanism for all the alarms issued on your system. and change their status from Open to Acknowledged or Closed.Using the Alarm Manager Using the Alarm Manager The Alarm Manager lets you view alarms as they arrive. acknowledge them. This action opens an instance-specific Alarm Manager. To display the Alarm Manager dialog do one of the following: ■ Click an instance-specific button in the Alarm Sentry. one that displays alarms for the invoking instance only. This action opens an Alarm Manager that displays the alarms for all instances to which it can connect. Managing Alarms 12–3 . Note: In addition. you can open the Alarm Manager from the Scheduler Console by choosing Alarm Manager from the Applications menu. Either of these actions opens an Alarm Manager dialog similar to the following illistration. or: ■ Click the Alarm Manager button in the GUI Control Panel.

Exit Closes the Alarm Manager. Use this dialog to define the filter by which you want to view alarms. Filters Menu The Filters menu contains the following options: Default Alarm Criteria Resets the filter criteria to the default and updates the Alarm Manager Alarm List to reflect this. Tools.Using the Alarm Manager The Alarm Manager dialog has a menu bar and the following three regions. 12–4 User Guide . Filters. Select Alarms Displays the Alarm Selection dialog (described in Filtering Alarms in this chapter). Preferences. and Help. which are described in the sections following: ■ ■ ■ Alarm List at the top of the dialog Currently Selected Alarm in the middle of the dialog Refresh area at the bottom of the dialog Using the Alarm Manager Menu Bar The Alarm Manager menu bar contains the following menus: File. File Menu The File menu contains the following options: New Alarm Manager Opens a New Alarm Manager.

For information.” in this guide. and you can enable Sound. Send Event Opens the Send Event Tool for the selected job (the job for which the alarm was generated). If you select the Sound check box in the Preferences dialog. and for refresh to work.” in this guide. see Using the Job Detail Report Tool in the chapter “Scheduler Console. This Sound setting overrides the Enable Sound setting on the Unicenter AutoSys Administrator Sounds screen. The default refresh interval time is 60 seconds. This dialog displays a realtime report of the job run information (in the format of the autorep command output). including information about the most recent.” in this guide. you must select the Auto Refresh check box (which is the default setting). Managing Alarms 12–5 . you can send events. For information. see Using the Send Event Tool in the chapter “Scheduler Console. For information. see Using the Run Status Tool in the chapter “Scheduler Console. Using this dialog.Using the Alarm Manager Tools Menu The Tools menu contains the following options: Run Status Tool Opens the Run Status Tool for the Currently Selected Job. Preferences Menu The Preferences menu contains the following option: General Opens the Preferences dialog in which you can set the Time between refreshes in seconds. run of the job for which the alarm was generated. the running Alarm Manager plays sound clips associated with alarms each time a new alarm is generated. and you can cancel events that have been scheduled for a later time. The Run Status Tool displays a job summary. or current. Job Detail Report Opens the Job Detail Report tool for the selected job (the job for which the alarm was generated).

Using the Alarm Manager

Help Menu The Help menu contains the following option: Contents Displays the table of contents for the Unicenter AutoSys JM Help. About Displays the Alarm Manager version number.

Using the Alarm Manager Alarm List
The Alarm List region of the dialog displays a list of all the alarms that are currently in the system and that meet the specified viewing criteria, either the default or the one specified in the Alarm Selection dialog. The default is to display all Open and Acknowledged alarms of any type, regardless of the time they were generated. Each entry in the Alarm List contains the following information about a single alarm:
■ ■ ■

Alarm Type, or the type of Alarm generated. Job Name, which is the job for which the alarm was generated. Time, which is composed of the date and time at which the alarm was generated. State, which is the alarm’s current state. Comment, which is any comment associated with the alarm at the time it was generated. Instance, which is the name of the instance for which the job is defined.

■ ■

Alarms are displayed in reverse order of occurrence; the newest alarms appear at the top of the list and older ones appear farther down.

To make an alarm the Currently Selected Alarm: Click on its line in the alarm list. When you do this, you can view more information about the alarm. You can also select multiple alarms, which allows you to perform actions on all of the selected alarms multiple alarms at the same time.

12–6

User Guide

Using the Alarm Manager

To select multiple alarms: Do one of the following:

Press the Ctrl key and click on each alarm that you want to select. Pressing the Ctrl key and clicking on a selected alarm will deselect the alarm.

or:

Click on one alarm, press the Shift key, and click on another alarm. This will select the two alarms and all the alarms in the list between them.

Clicking anywhere in the alarm list will deselect the currently selected alarms.

Viewing the Currently Selected Alarm
The Currently Selected Alarm region of the dialog displays more information about the currently selected alarm and allows you to enter a response in the Response scrollable text box. The Response scrollable text box accepts multiple lines of text. The entered text is automatically word wrapped, with lines breaking at appropriate spaces. You can use the mouse to edit text. In addition, you can use the arrow and backspace keys as well as the Tab and Enter keys. Once you enter your Response, click Apply to write it to the database. The User field, beneath the Response scrollable text box, shows the user who invoked the Alarm Manager. This read-only field shows which user responded to the alarm field. The Alarm State region lets you change the alarm state to Acknowledged or Closed. Once an alarm is changed from the Open state, you cannot return it to the Open state. To change the Currently Selected Alarm to Acknowledged or Closed: Select the appropriate radio button, and click Apply. If you change the alarm to Acknowledged, it remains on the list. If you change the alarm to Closed, it is removed from the list.

Managing Alarms

12–7

Using the Alarm Manager

Registering Responses and Changing Alarm States To register a response or change the state of an alarm in the database, you must explicitly save the alarm. Because the Alarm Manager will probably run on a continual basis, use the Apply button to register changes that you make to any alarms. That is, when you enter a response or change alarm states, you must click Apply to save the change to the database.

Setting the Refresh Behavior
At the bottom of the Alarm manager is the Refresh area, and it contains the Auto Refresh setting, which you can turn off or on, and the Refresh button. By default Auto Refresh is selected (set to on). The on setting indicates that the Alarm Manager should be updated based on the setting in the General dialog, which you can open from the Preferences menu. The default refresh interval is 60 seconds. With this setting, the Alarm Manager reads from the database to update the alarm list every 60 seconds. If you uncheck the Auto Refresh check box, setting it to off, the Console display is not updated. To update the display: Do one of the following:

Check the Auto Refresh checkbox.

or:

Click Refresh.

12–8

User Guide

Filtering Alarms

Filtering Alarms
Alarms and their responses are stored in the database, from which you can retrieve them for viewing or for adding additional responses. To control dynamically which alarms are displayed in the Alarm Manager, use the Alarm Selection dialog. Using the Alarm Selection dialog, you can select alarms by the following:
■ ■ ■ ■

Type of alarm State of alarm (Open, Acknowledged, or Closed) Date and time of the alarm’s occurrence Instance name

Note: Alarms that have been archived cannot be displayed. To display the Alarm Selection dialog: Choose Filters, Select Alarms. The Alarm Selection dialog appears with the defaults set, as shown in the following illistration:

Managing Alarms

12–9

Filtering Alarms

The Alarm Selection dialog is divided into the following regions, described in the sections following:
■ ■ ■ ■

Select by Type Select by State Select by Instance Select by Time

After you define your filter, you can view it in the Alarm Manager.

To view the selection criteria in the Alarm Manager: Click OK. This action sets your selections and dismisses the Alarm Selection dialog.

To dismiss the dialog without applying the selections: Click Cancel.

Selecting Alarms by Type
In the Select by Type region of the dialog, a list of all possible alarm types is displayed. From this list, you can select one, several, or all types of alarms. The default is All Types of alarms.

To choose a single alarm from the list: Click the alarm name.

To choose a range of alarms: Click and hold the mouse button on the first alarm name, drag the cursor to the last alarm in the range, and release the mouse button.

To choose noncontiguous alarms: Press the Ctrl key and click the desired alarms. To deselect an alarm, press the Ctrl key and click the selected alarm.

To choose all alarm types: Select the All Types option, which overrides any specific or individual selections.

For information on the Alarm Types, see the section Alarms in the chapter “System States, “ of the Unicenter AutoSys Job Management Reference Guide.

12–10

User Guide

Filtering Alarms

Selecting Alarms by State
You can also select alarms by the state of the alarm. You can select All States, or you can select individual states. To do so, you click on, and check, the appropriate check boxes. The default setting is to display all Open and Acknowledged alarms.

Selecting Alarms by Instance
You can select which instances you want included in this filter. The instances on this list are the ones to which this Alarm Manager can connect.

Selecting Alarms by Time
By default, alarms are shown regardless of the time they were generated. You can choose to display only alarms that were generated during a specific date and time window. To indicate a specific date and time window: Uncheck the All Times check box, and fill in the From Date, From Time, To Date, and To Time fields. You can specify dates without times, but you cannot specify times without dates. You must use a 24-hour format when specifying times. For your convenience, the current system date and time are filled in automatically.

Managing Alarms

12–11

Chapter

13

Monitoring and Reporting on Jobs

Using AutoSys Monitors and Browsers
You can define and create monitors and browsers to view the state of the system. Monitors provide a realtime view of the system. Browsers are reports that provide historical information about job executions. Monitors and reports enable you to filter and screen only the information you are interested in from a vast collection of data. That is, they are tools that can give you the information you want. Because browsers are reports, and because “report” is a common term, this document uses the term report, except when talking about the Monitor/Browser interface components. Monitors and reports are simply applications that retrieve data from the database. Because all information is in the database, monitors and reports that retrieve information from the database provide a complete picture of the state of the entire system. Monitors and reports can run with any database, and they work with dual-event servers. Also, you can run monitors and reports on any client machine. You can define monitors and reports to display events by using the following:
■ ■ ■

Event type Job type Job name

In addition, you can define reports to display events based on the time the events occurred. You cannot define monitors to display based on event time because they provide realtime information.

Monitoring and Reporting on Jobs

13–1

Using AutoSys Monitors and Browsers

You can define monitors and reports by using the Monitor/Browser Editor, which you open from the GUI Control Panel. In the Monitor/Browser Editor, you can define a new monitor or report by assigning a name and specifying a number of attributes that define its behavior. In addition, you can define monitors and reports by passing Job Information Language (JIL) statements to the jil command. For information, see Defining Monitors and Reports Using JIL in this chapter. In either case, the monitor or report definitions are stored in the database. Because the definitions are stored in the database, you can run defined monitors or reports at any time without redefining the criteria.

Using Monitors
Monitors provide a realtime view of the system. These are the two steps necessary to use a monitor: 1. 2. Define the events to monitor. Run the defined monitor.

A running monitor is an application that polls the database for new events that meet the selection criteria. Monitors are strictly informational. They provide an up-to-the-minute window to events as they occur. For box jobs, you can specify to track all job levels. Note: Monitors provide a picture of the system’s state in real time. If the event processor is down, monitors will not provide any information.

13–2

User Guide

Using AutoSys Monitors and Browsers

Using Reports
A report (or browser) provides historical information about job executions. A report is a customized query run against the database, and it is based on the selection criteria you define for the specific report. Its primary function is to enable you to get very specific information quickly. Reports can display only the events still in the database; archived events are inaccessible and cannot be displayed. For example, you could create a report based on the finish time of the database backup for the last two weeks, or one based on all jobs that have an alarm associated with them. You can also create reports that contain all the job levels in box jobs. Report definitions are also stored in the database, enabling you to run defined reports at any time, without redefining the criteria.

Monitoring and Reporting on Jobs

13–3

Open the GUI Control Panel from the Graphical Interface icon in the program group. 4. 13–4 User Guide .Using the Monitor/Browser Editor Using the Monitor/Browser Editor To define a monitor or report using the Monitor/Browser Editor: 1. and can specify the name of the monitor or report. Unicenter AutoSys JM establishes a connection to that instance’s database. Select Monitor or Browser from the drop-down list at the top of the editor window. click Monitor/Browser Editor. 2. and maintains that connection until you close the Monitor/Browser Editor. 3. Note: When you first select an instance in any of the Monitor/Browser Editor dialogs. Set the various attributes and their values using the fields and checkboxes. When you do this you can select the instance to save the definition to. In the GUI Control Panel. 5. Save the monitor or report definition to the database. which displays the Monitor/Browser Editor shown in the following illistration.

Open Opens the Open dialog. which allows you to select an instance and enter a unique name for the new monitor or report you are going to define. then click Search to display a list of those monitors and reports whose names include the string. File Menu The File menu contains the following options: New Opens the New Monitor/Browser dialog. this option opens the Save As dialog. The default filter. including the percent (%) wildcard character. you can specify any string. The monitor or report name identifies the monitor or report. Monitoring and Reporting on Jobs 13–5 . see Setting Monitor and Report Attributes in this chapter. Save Stores the currently displayed monitor or report in the database. In the Pattern field of this dialog. A monitor or report name can be from 1-30 alphanumeric characters. which allows you to search for and select an existing monitor or report. Embedded spaces are illegal. A monitor and report cannot have the same name.Using the Monitor/Browser Editor The Monitor/Browser Editor contains fields that represent all the information needed to define a monitor or report. Edit. Using the Monitor/Browser Editor Menu Bar At the top of the Monitor/Browser Editor is a menu bar that contains the following menus: File. When you Save a definition for the first time. which allows you to select an instance and enter a new name for the monitor or report. and must be unique within an instance. For more information about these fields. You can use this option to save a definition to a different instance or a different name. and Help.” displays a list of all monitor and report names. “%. but a monitor or report can have the same name as a job. Save As Opens the Save As dialog.

Help Menu The Help menu contains the following options: Contents Displays the table of contents for the Unicenter AutoSys JM Help. you are prompted to choose whether or not to save it before the editor is closed. Exit Closes the Monitor/Browser Editor. Note: When you first open a Monitor/Browser Editor. Unicenter AutoSys JM establishes a connection to that instance’s database. New Monitor/Browser Editor Opens a new Monitor/Browser Editor. and it maintains that connection until you close the Monitor/Browser Editor. Monitor and report definitions must be saved in the database before they can be run. Edit Menu The Edit menu contains the following option: Clear Clears the Monitor/Browser Editor without affecting the database. and click OK. About Displays the Monitor/Browser Editor version number. This action deletes the selected definitions from the database. and when you select a new instance in any of the Monitor/Browser dialogs. Run Monitor/Browser Runs the current monitor or report and displays output in an AutoSys Instance Command Prompt window. Use this button to clear all fields before you begin defining a new monitor or report. In this dialog. you can select one or more monitors or reports. If you have unsaved work. which allows you to search for existing monitors and reports.Using the Monitor/Browser Editor Delete Displays the Delete Monitor/Browser dialog. 13–6 User Guide .

7. select the All Jobs radio button. 5. To define the example monitor: Follow these steps using the open Monitor/Browser Editor: 1. and enter the following name for the new monitor: Regular 4. In the Save As dialog. There are corresponding examples that demonstrate using JIL statements to create monitors and reports in Defining Monitors and Reports Using JIL in this chapter. 2. 6. A message is displayed when the monitor definition is successfully written to the database. Your entries in the Monitor/Browser Editor should look like those shown in the following illistration. In the Job Selection Criteria area. leave the Monitor setting. select an Instance. To follow the steps in these exercises. select the Running. Choose File. In the Event Types area select the Alarm check box. Save. you must first open a Monitor/Browser Editor by opening the GUI Control Panel and clicking the Monitor/Browser Editor button. success. In the Job Change Status Events sub area. Monitoring and Reporting on Jobs 13–7 . which opens the Save As dialog. 3. In the Save As dialog. In the drop-down list at the top. Failure. Defining a Monitor This example describes how to define a monitor with the name “Regular. click OK.” This monitor will monitor all alarms. Success. and Terminated check boxes.Defining Monitors and Reports with the Editor Defining Monitors and Reports with the Editor This section contains examples of creating a monitor and a report. plus job status events when a job changes state to running. failure. or terminated. Note: The examples in this section demonstrate how to use the Monitor/Browser Editor.

Run Monitor/Browser. you must save it first. For information on running a monitor. and then choose File.Defining Monitors and Reports with the Editor You can leave the Monitor/Browser Editor open to do the next example. When you run a monitor or a report from the Monitor/Browser Editor. see Running a Monitor or Generating a Report in this chapter. Note: If you want to run the monitor. 13–8 User Guide . an Instance Command Prompt window opens to display the monitor or report output.

Defining Monitors and Reports with the Editor Defining a Report This example describes how to define a report with the name “Alarm_Rep. Save. Choose File. Monitoring and Reporting on Jobs 13–9 . 2. select an Instance. This action opens a New Monitor/Browser dialog. In the dialog. In the Browser Time Criteria area. A message is displayed when the report definition is successfully written to the database. This action returns you to the Monitor/Browser Editor. at 2:00 a. Click OK in the New Monitor/Browser dialog. to the present.” This definition will create a report that contains all alarms on any job. time): 05/22/1997 2:00 4. In the Event Types area select the Alarm check box. enter the date and time in the Events After Date/Time text field as follows (or you can enter a different. 8. and click OK in the Save As dialog. From the drop-down list at the top of the window. In the Job Selection Criteria area. 1997. select Browser. select the All Jobs radio button.m. and enter the following report name: Alarm_Rep 3. more appropriate. 7. New. To define the example report: 1. Choose File. 5. 6. from May 22.

Exit. 13–10 User Guide .Defining Monitors and Reports with the Editor Your entries in the Monitor/Browser Editor should look like those shown in the following illistration: Closing the Monitor/Browser Editor To close the Monitor/Browser Editor: Choose File.

Any other Event Types filtering settings are ignored. by using the following command at an AutoSys instance command prompt: autosyslog –e Monitoring and Reporting on Jobs 13–11 . such as alarms Manually generated events. If you want to monitor all the events for all jobs. you should not run a monitor. Setting Event Types The Event Types you specify determine which events will be monitored or reported. placing a job on hold. The Monitor/Browser Editor is divided into the following areas: ■ ■ ■ ■ Event Types Job Selection Criteria Monitor Options Browser Time Criteria You can define several different filters by which monitors and reports will track events. If you do not select this check box. All Events include job status events and alarms. When you complete a definition.Setting Monitor and Report Attributes Setting Monitor and Report Attributes To set the monitor or report attributes. the other Event Types settings are used. such as starting a job. Instead. or killing a job all_events All Events JIL Keyword: Selecting the All Events check box specifies that all events will be tracked for the selected jobs. Events include the following: ■ ■ ■ Changes in the state of jobs Generated occurrences. you should display the event processor log in real time. the events that are tracked are determined by the combination of the Event Types and the Job Selection Criteria settings. use the fields on the Monitor/Browser Editor.

you can select the following Job Change Status Events (JIL attribute values are in parentheses): ■ ■ ■ ■ ■ ■ Running (running) Success (success) Failure (failure) Terminated (terminated) Starting (starting) Restart (restart) Note: If you select All Change Status Events. 13–12 User Guide . any Job Change Status Events that you select are ignored. You can select both All Change Status Events and Alarms as filters. or choose specific Job Change Status Events as filters (described below). All Change Status Events JIL Keyword: all_status Selecting the All Change Status Events check box specifies that all job status events should be tracked. however. so they do not have the same impact on system performance as monitors do. because they are already included in the All Change Status Events filter. Job status events occur whenever a job’s status changes. Job Change Status Events Instead of selecting All Change Status Events. change status events are automatically tracked. If this attribute is checked all of the Job Change Status Events shown below as well as a few internal job status events are tracked. Reports connect to the database only once to get the information. If you select the All Events check box. This has a significant impact on system performance. the information logged by the event processor contains more diagnostic information than the monitor does. alarms are already tracked.Setting Monitor and Report Attributes Running a monitor adds another connection to the database and establishes another process that is continually polling the database. To limit the events that are tracked. you can select both Alarm and All Change Status Events. Alarm JIL Keyword: alarm Selecting the Alarm check box specifies that generated alarms should be tracked. Moreover. If you select the All Events check box.

you must enter the job name in the field to the right of these choices. The events to be tracked are determined by the combination of the Event Types that you set as filters and the Job Selection Criteria you set in this area. or a single job with a specified name. If you select either the Jobs in Box named or Single Job named radio buttons. all jobs in a box job with a specified name. Job Filter JIL Keyword: job_filter You can set the Job Filter to one of three settings: All jobs (no job filtering). Monitoring and Reporting on Jobs 13–13 .Setting Monitor and Report Attributes Setting the Job Selection Criteria In the Job Selection Criteria area you can indicate the jobs to track.

along with the alarm event. the monitor must be running.Setting Monitor and Report Attributes Setting Monitor Options The monitor attributes in the Monitor Options area are optional. The announcement is from prerecorded sound clips. it keeps playing the sound clip until someone responds. see the section Sounds in the Chapter “Administrator. 13–14 User Guide .” in this guide. Execute SQL against the msg_ack table to view the account of the alarms responded to and at what time. Unicenter AutoSys JM uses sound to announce the events as they occur. especially alarms. This verification feature prompts users (in the window running the monitor) for their initials and a comment. Therefore. It frees you from needing to look through output files to see if there were any problems. Alarm Verification Required JIL Keyword: alarm_verif Selecting the Alarm Verification Required check box specifies that personnel must respond to alarms to turn the alarms off. for the sound attribute to work. However. For more information about enabling AutoSys sounds. An important feature of this attribute is the alarm sound is repeated every 20 seconds until there is a response. if you momentarily step out of the room and there is an alarm. Sound JIL Keyword: sound Selecting the Sound check box specifies that the sound facility should be used. Note: We strongly recommend that you use the sound attribute for monitoring AutoSys. This information is timestamped and logged in the msg_ack database table. If the Windows machine running the monitor has sound capabilities and you have enabled sound using the Unicenter AutoSys Administrator.

you must first deselect the Current Run Only checkbox.Setting Monitor and Report Attributes Setting the Browser Time Criteria When defining reports. Monitoring and Reporting on Jobs 13–15 . Note: These settings are disabled for monitors because time is not used in monitors. Note: If your local setting uses a two-digit year. monitors only show events as they occur. Reports are based on all events in the database. Unicenter AutoSys JM prepends 19. This option allows you to get a report on what happened most recently. For example. Unicenter AutoSys JM prepends 20. The setting is typically the mm/dd/[yy]yy hh:mm format. select All Jobs in the Job Selection Criteria area. Events After Date/Time JIL Keyword: after_time Entering a date and time in the Events After Date/Time field specifies that only the events occurring after that date and time for the specified jobs. The two choices are mutually exclusive. and select this check box. Unicenter AutoSys JM however saves the setting to the database using a four-digit year. to get a report on all the jobs that restarted in its last run. and the Browser Time Criteria allows you to select events that occurred within a particular span of time. and. This is the default selection. To use this option. Current Run Only JIL Keyword: currun Selecting the Current Run Only check box specifies that only events in the current or most recent execution of the specified jobs will be reported. This entry must be in the date time format set locally. you must enter the year in that format. are in the report. which is displayed under the field. If you enter 79 or less. select Restart in the Job Change Status Events area. you must specify one of the Browser Time Criteria options. if you enter 80 or greater.

open a monitor or report and choose File. To close a monitor or report: Press Ctrl+C. From an instance command prompt. execute the following AutoSys command: monbro -N monbro_name ■ where monbro_name ■ Is the defined monitor or report name.Running a Monitor or Generating a Report Running a Monitor or Generating a Report ■ To run a monitor or report: Do one of the following: ■ In the Monitor/Browser Editor. and the current monitor or report will run. 13–16 User Guide . Run Monitor/Browser.

Open an instance command prompt window. insert_monbro: name_value ■ To define a monitor or report using JIL by redirecting a file containing jil definitions: At the Instance Command Prompt. however you use different subcommands. At the instance command prompt. At the jil prompt. see the chapter “JIL/GUI Monitor/Report Definitions” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. like: jil < jil_script where: jil_script Is the name of the file containing the jil monitor and report definitions. 2. The examples in the following sections include the JIL versions of the monitor and report examples in Defining Monitor and Reports with the Editor in this chapter. use these JIL subcommands: ■ ■ ■ ■ insert_monbro update_monbro delete_monbro To define a monitor or report using JIL interactively: 1. you use the same syntax as you do to define a job. Note: For a complete listing and description of the JIL commands and subcommands that you can use to define monitors and reports. issue the following command: jil 3. For defining monitors or reports.Defining Monitors and Reports Using JIL Defining Monitors and Reports Using JIL In addition to using the Monitor/Browser Editor. Monitoring and Reporting on Jobs 13–17 . you can use the Job Information Language (JIL) to define monitors and reports. submit the JIL script file. To define a monitor or report with JIL. enter the JIL subcommand followed by a set of attribute: value pairs.

failure.” in this guide. see Sounds in the chapter “Administrator. Archived events are inaccessible and cannot be displayed.jil contains example JIL statements. and terminated: /* Monitor for all ALARMS. and repeats the sound until someone responds: /* Monitor for JUST ALARMS! * Verification Required is ON so someone must * type in a response.FAILURE & TERMINATED */ insert_monbro: Regular mode: m alarm: y running: y success: y failure: y terminated: y The following JIL statements define a monitor that catches alarms.m. This example defines a report with the name “Alarm_Rep. at 2:00 a. insert_monbro: Alarm_Rep mode: b alarm: y after_time: "05/22/1997 2:00" In this example. plus job status events when a job changes state to running. the colon.” This monitor will track all alarms.Defining Monitors and Reports Using JIL Defining Monitors Using JIL The first example in this section defines a monitor with the name “Regular.SUCCESS. generates a sound.” This report will report all alarms on any job from April 1. For more information about enabling sound. 1997. success. quotes are required because the time contains a special character. 13–18 User Guide . to the present. and * Job EVENTS: RUNNING. Note: Reports can display only events that are still in the database. * Sound is ON! */ insert_monbro: Alarm mode: m sound: y alarm: y alarm_verif: y Note: The file named %AUTOSYS%\install\data\monbro.

Open the Unicenter AutoSys Administrator from the program group. On the Services screen.Chapter 14 Maintaining This chapter describes the procedures for maintaining Unicenter AutoSys JM and the database. Maintaining the Event Processor The Event Processor is the engine of Unicenter AutoSys JM. select the AutoSys Event Processor from the Service drop-down menu. When the Event Processor is not running. and the actions that have already started will run to completion. 4. To start the Event Processor 1. and properly identified before you can start the Event Processor. On the Instance screen. Do one of the following to display the Services screen: Choose AutoSys. Starting the Event Processor The database that is designated as the Event Server must be available. running. Maintaining 14–1 . specify the Computer and Instance you are modifying and click OK. Click the Start Service button. 2. You can stop the Event Processor. or: Click the Services button on the toolbar. however. 3. Event Processor. The Computer should be the machine on which the Event Processor is installed. you cannot initiate new actions. 5.

WARNING! Do not log onto the Shadow Event Processor machine and start the Shadow Event Processor manually. Note: Most services. including the Remote Agent and the Event Server (database service). Note: If you want it to also check that no other Event Processors are running on other machines. it performs the following tasks: ■ Verifies that no other Event Processor is running on that machine. Event Processor Starting Processes After you start the Event Processor. but before it begins processing. and on which machine.Maintaining the Event Processor If you set up a Shadow Event Processor. If a job is not running as expected. it sends an alarm. add the machine names to the Network Machine List field in the AutoSys Administrator Event Processor screen. If chase locates anomalies. We recommend that you start the Event Processor manually after booting your system. it starts automatically when you start the Primary Event Processor. if the job definition allows this. If you lose several systems at once due to power failure. The chase utility determines from the database which jobs are in the STARTING or RUNNING state. chase passes the Remote Agent a list of jobs that are supposed to be running there and instructs the Remote Agent to verify that the processes actually are running. which will cause a failure. For each client machine. chase also verifies that the Remote Agent is running. 14–2 User Guide . the Event Processor sends the necessary corrective event for the job. start automatically at boot time. ■ Invokes the chase -A -E command. Doing this will cause the Shadow Event Processor to act as the Primary Event Processor. this approach allows the Remote Agents to start on their respective machines before you start the Event Processor.

Maintaining 14–3 . Monitoring the Event Processor The output of the Event Processor (event_demon. the last ten lines of the log file are displayed. the Event Processor will not start it again. Note: You can turn off this Event Processor startup behavior by deselecting the Chase On Startup check box located on the Unicenter AutoSys Administrator Event Processor screen.” in this guide. and then all additions to the log are automatically displayed as they occur. including startup and shutdown information. For more information on using the Unicenter AutoSys Administrator.%AUTOSERV% This log file contains a record of all the actions taken by the Event Processor. It displays the log file. To terminate the autosyslog process: Press Ctrl+c. This method is similar to database check pointing and rolling forward or backward upon recovery. see the section Administrator Event Processor in the chapter “Administrator. Note: We recommend that you use the autosyslog -e command to follow the behavior of the Event Processor.Maintaining the Event Processor ■ If the event being processed is a STARTJOB event. Problems are detected upon Event Processor startup. and the job it started is still alive. To view the log file Execute the autosyslog utility like: autosyslog -e When you execute this command. which generates information on all Event Processor activity.exe executable) is written to the following log file: %AUTOUSER%\out\event_demon. The purpose of running the chase utility is to guarantee that the Event Processor starts with all processes in a known state.

If the file is the indicated maximum size. in: event_demon. the error is written to the designated Enterprise Wide Directory. if the amount of available disk space falls below that specified by the FileSystem Threshold setting in the Administrator Event Processor screen. The Event Processor reads this setting on startup and checks the file size. the error is written to the Windows Event Log. For information on the FileSystem Threshold setting. the error is written to: %AUTOUSER%\out\event_demon. However.%AUTOSERV% Event Processor Log File Size The Maximum Log Size setting on the Administrator Event Processor screen specifies the maximum size of the Event Processor log file. You can locate the error description in one of the following locations: ■ If the Event Processor fails early in startup.Maintaining the Event Processor Location of the Event Processor Log File When the Event Processor has problems starting.out ■ ■ If the Event Processor has problems while running. If the Event Processor fails during the startup procedure. which is dependent upon when the starting process fails. The Event Processor shuts down if there is less than 8 kilobytes of disk space available. the Event Processor issues warnings in the Event Processor log file.” in this guide. 14–4 User Guide . see the section Unicenter AutoSys Administrator Event Processor in the chapter “Administrator. the Event Processor deletes it. the error log is written to different place.%AUTOSERV%. The Event Processor log has a file system threshold setting.

and File Watcher Jobs). but instead of starting the jobs.Starting the Event Processor in Global Auto Hold Mode Starting the Event Processor in Global Auto Hold Mode If you restart an Event Processor after a period of downtime. Click the Global Auto Hold checkbox to select it. To start the Event Processor in Global Auto Hold mode 1. the Event Processor starts without simultaneously starting all the jobs whose starting conditions are met. The only way to start a job when Global Auto Hold is on is to send the FORCE_STARTJOB event. The Computer should be the machine on which the Event Processor is installed. specify the Computer and Instance you are modifying and click OK. Services. you might want to start it in Global Auto Hold mode. On the Instance screen. or: Click the Event Processor button on the toolbar. the Event Processor puts them ON_HOLD. Do one of the following to display the Services screen: Choose AutoSys. Maintaining 14–5 . When you select Global Auto Hold. and click OK. select the Event Processor from the Service dropdown menu. or: Click the Services button on the toolbar. Command. Do one of the following to display the Event Processor screen: Choose AutoSys. Event Processor. 4. It does this for all types of jobs (Box. This approach allows you to decide which jobs should run by selectively starting them with the Force Start Job event. Click the Start Service button. 3. 2. Open the Unicenter AutoSys Administrator from the program group. the Event Processor evaluates all jobs whose starting conditions have passed and are eligible to run. Starting the Event Processor in Global Auto Hold mode prevents the system from being flooded with jobs that were scheduled to run during the downtime. 6. In Global AutoHold mode. 5. On the Services screen. 7.

On the Instance screen. and click OK. Do one of the following to display the Services screen: Choose AutoSys. 4. 14–6 User Guide . 6. 8. The Computer should be the machine on which the Event Processor is installed. or: Click the Services button on the toolbar. Do one of the following to display the Event Processor screen: Choose AutoSys. select the Event Processor from the Service dropdown menu. Shut down the Event Processor. Services. Note: If you have AutoSys configured with a Shadow Event Processor. 7. Click the Start Service button. On the Services screen. Click the Global Auto Hold check box to deselect it. 5. the Shadow Event Processor will also be in Global Auto Hold mode. Open the Unicenter AutoSys Administrator from the program group. 3. specify the Computer and Instance you are modifying and click OK.Starting the Event Processor in Global Auto Hold Mode To send a Force Start Job event Use the Scheduler Console. or: Click the Event Processor button on the toolbar. or: Execute the following command: sendevent -E FORCE_STARTJOB -J job_name To turn off Global Auto Hold mode 1. Event Processor. or: Use the Send Event Tool. and you start the Event Processor in Global Auto Hold mode. using the following command: sendevent -E STOP_DEMON 2.

see sendevent in the chapter Commands. Note: Stopping the Event Processor does not affect jobs that are already running. 2. Only the Exec Superuser can stop the Event Processor. do not send another STOP_DEMON event. These methods stop the Event Processor no matter what it is doing. the STOP_DEMON event is sent to the database. in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. if you are using Dual Event Servers and use these methods. and it will promptly shut down. Issue the following command at an Instance Command Prompt: sendevent -E STOP_DEMON This method allows the Event Processor to complete gracefully any processing it is performing.Starting the Event Processor in Global Auto Hold Mode Stopping the Event Processor It is safe to stop the Event Processor at any time. Log onto any AutoSys configured machine as the Exec Superuser. because the event Processor will process that event the next time it starts. at which time the exit events are sent directly to the database. it might be in the middle of processing an event. They continue to run to completion. WARNING! Do not attempt to stop the Event Processor by using a utility such as pview or by using the Control Panel Services dialog. Maintaining 14–7 . The effect of stopping the Event Processor is that actions triggered by incoming events sent from the Remote Agents are not initiated until you start the Event Processor again. If the Event Processor does not shut down immediately. The Event Processor then reads the STOP_DEMON event. Also. the databases can lose synchronization. For more information about the sendevent command. if it is stopped properly. There might be a delay between when you send the STOP_DEMON event and when the Event Processor reads it and shuts down. goes into an orderly shutdown cycle. When you issue the sendevent command. and exits. You can assign a high priority to the sendevent -E STOP_DEMON command by including the -P 1 argument. To stop the Event Processor properly 1.

In this situation.dibs file already exists. attempts to signal the Primary Event Processor to stop. If the Primary Event Processor and an Event Server are on the same machine. and follows the same procedure as the Shadow Event Processor. see the chapter “Administrator. However. Unicenter AutoSys JM uses the Third Machine and the existence of the . it listens for the periodic signals (every 90 seconds) from the Primary Event Processor that indicate the Primary processor is still functioning. or: ■ If it can connect but cannot locate the .Starting the Event Processor in Global Auto Hold Mode Shadow Event Processor Rollover You can configure a Shadow Event Processor to act as a backup Event Processor. ■ Checks the Third Machine for the . Does one of the following: If it cannot connect to the Third Machine. if the Primary Event Processor cannot locate and signal the Shadow Event Processor. the Event Processor failure could also mean an Event Server failure. For more information. and it will shut down both processors. For example. The Shadow Event Processor is normally idle. Unicenter AutoSys JM might not be able to determine which Event Processor is the “healthy” one. You can specify the Shadow Event Processor and the Third Machine using the Unicenter AutoSys Administrator Event Processor screen (accessed from the program group).dibs file. and takes over processing the events. it does the following: 1. the Primary processor checks the Third Machine for the .dibs file. or: ■ If it can connect and the . Unicenter AutoSys JM will roll over to the Shadow Event Processor and to Single Server mode. the Shadow Event Processor is not guaranteed to take over in 100% of the cases. the Shadow Event Processor shuts down. Similarly. If the Shadow Event Processor does not receive the signal. 2.dibs file. the Shadow Event Processor shuts down.” in this guide. if Dual Event Servers are configured. in the case of network problems. 14–8 User Guide .dibs file to resolve contentions and to eliminate the case where one processor takes over because its own network is down. the Shadow Event Processor creates the file.

Maintaining 14–9 . 4. Go to the Services screen by clicking Services on the toolbar.Starting the Event Processor in Global Auto Hold Mode Restoring the Primary Event Processor To restore the Event Processor service following a rollover 1. On the Services screen. 5. open the Unicenter AutoSys Administrator from the program group. and click OK. Stop the Shadow Event Processor by logging on as the Exec Superuser. 6. Specify the Computer and the Instance you are modifying. The Shadow Event Processor starts automatically when you start the Primary Event Processor. and issuing the following command: sendevent -E STOP_DEMON 2. Click Start Service. Note: If you attempt to start the Primary and Shadow Event Processors without having a Third Machine specified in the Unicenter AutoSys Administrator. the Shadow Event Processor will not start. 3. On the Primary Event Processor machine. select the Event Processor from the Service dropdown menu.

so under normal circumstances you should not need to start the Remote Agent manually. Open the Unicenter AutoSys Administrator from the program group. It will continue to try to connect to the database until it can successfully transfer the information. 2. If for some reason the Remote Agent service is stopped. and then exits. Go to the Services screen by doing one of the following: ■ 3. 14–10 User Guide . Click the Services (traffic light) toolbar button. Services.Maintaining the Remote Agent Maintaining the Remote Agent A Remote Agent is a Windows service that runs on a remote machine. and click OK. If the Remote Agent is unable to transfer the information. specify the Computer and Instance of the Remote Agent you want to start. The Remote Agent starts the command specified for a given job. Starting the Remote Agent The Remote Agent service should start automatically when the machine is started (this is set in the Control Panel Services dialog). or: ■ Choose AutoSys. any user with Administrators group privileges can restart it. On the Instance screen. sends running and completion information about a task as an event to the database. it waits and tries again. The Event Processor directs the Remote Agent to perform specific tasks. To restart the Remote Agent 1.

In addition. if the Remote Agent is not running. Click Start Service. 5. yellow. Stop Services is enabled and Start Services is disabled). or green light of the traffic light icon and the field under it indicate the status of the Remote Agent. Start Service is enabled (if it is running. The red. For information on using the Administrator. select the Remote Agent service from the Service drop-down list.Maintaining the Remote Agent 4. On the Services screen. Stopping a Remote Agent You should not stop the Remote Agent service. If it is inadvertently stopped. Maintaining 14–11 . If the Remote Agent does not start.” in this guide. see the previous section for directions on how to restart it. see the chapter “Administrator. see the section Remote Agent Troubleshooting in the chapter “Troubleshooting.” in this guide.

When running in test mode. without having to run the defined jobs. If the conditional logic for jobs. The levels of test mode are determined by the value of the %AUTOTESTMODE% variable. 14–12 User Guide . you can run in test mode. which are discussed in the following sections: ■ ■ %AUTOTESTMODE%= 1 %AUTOTESTMODE% = 2 Note: The event processor cannot run partially in test mode. These are the values.Running in Test Mode Running in Test Mode If you want to check your configuration. You do this by setting the %AUTOTESTMODE% environment variable before starting the event processor. you should exercise extreme caution when you run in test mode on a live production system. Unicenter AutoSys JM does not provide a test mode for the database. This process is helpful for troubleshooting problems. Running in test mode uses the same mechanisms of starting jobs and sending events that Unicenter AutoSys JM uses in its normal mode. A simple job is run in place of the defined job. ■ You can run the event processor at two levels of test mode. including nested boxes. Running the event processor in test mode allows you to test the set up as well as the execution of logic by the jil command. Therefore. you can determine the following: ■ If the event processor and the remote agents are installed and configured properly. is functioning correctly.

Output from the ntgetdate command goes to the user defined standard output and standard error files. where %AUTO_JOB_NAME% is the job name as defined to AutoSys. If the job being run in test mode is a file watcher job. otherwise. ■ ■ The following functions are disabled: ■ ■ ■ Minimum and Maximum Run Alarms Sourcing a user-specified job profile file All resource checks %AUTOTESTMODE% = 2 The second level of test mode runs with the same behaviors as the first level with the addition of the following procedures: ■ ■ ■ Resource checks are performed.%AUTO_JOB_NAME% Maintaining 14–13 . Standard output and standard errors for the command are redirected to the \tmp\autotest %AUTO_JOB_NAME% file.Running in Test Mode %AUTOTESTMODE% = 1 At the first level of test mode. each job that you specify runs with the following test mode variations: ■ The command ntgetdate is executed on the remote machine instead of the command specified in the job definition. if they are defined. it runs as it would in real mode. it is not disabled. output goes to the file named \tmp\autotest. A user defined job profile is sourced.

see the chapter “Commands. For more information about the chase command. 14–14 User Guide . The job is running. it can automatically restart jobs that are “missing in action” and that are defined to be restartable (by using the -E option). or are running on the machine with the failed network connection might be restarted if the network connection is re-established. The options used with chase further determine what actions are taken when error conditions are detected. It goes to every machine that should be running a job and verifies that the following are true: ■ ■ The Remote Agent is running. chase can send alarms to alert you to the problems it finds (by using the -A option).” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. therefore. Errors detected by chase are sent to standard output. chase The chase command verifies that the expected jobs are running. or if the network connection to the machine is down.Maintenance Commands Maintenance Commands The maintenance commands described below are located in the %AUTOSYS%\bin directory. If you run chase with the -E option. jobs that have already run. Note: There is no way for chase to tell if a machine is down. In addition. it cannot tell if jobs on that machine are running. You can execute these commands from the Instance Command Prompt window or as an job.

use the following command: clean_files -d days where: days Specifies that files older than this number of days should be deleted. To remove only the log files older than a specific number of days.” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. It performs this task by searching the database for all machines that have had jobs started on them. For more information about the clean_files command.Maintenance Commands clean_files The clean_files command deletes old remote agent log files. and then sending a command to the database on that machine to purge all remaining log files from the machine’s remote agent log directory (specified by AutoRemoteDir in the configuration file). see the chapter “Commands. Maintaining 14–15 .

Note: The calendar definitions are saved as text. The Save As dialog is displayed. d. Export All. b. This command saves your job definitions to a file named autosys. Open a Calendar Editor window. 14–16 User Guide .jil. Save your calendar definitions: a. Click Save. execute the following command: autorep -J ALL -q > c:\directory\autosys. To back up definitions: 1. Save your job definitions. In the Save As dialog.jil where: directory Is a directory outside of the Unicenter AutoSys JM directory structure. We also recommend that you keep a copy of your license keys in case you need to reinstall them. c. Choose File. We recommend that you save this directory to the same directory where you saved your calendar definitions.Backing up Definitions Backing up Definitions We recommend that you back up the following definitions periodically to ensure that you have files to restore from in case of a system failure: ■ ■ ■ ■ ■ calendar definitions job definitions machine definitions monitor and browser definitions global variables For information about restoring the backed up definitions. 2. see the section Restoring Definitions in this chapter. select a directory that is outside of the directory structure and select or enter a file name. from a Instance command prompt.

you enter >> instead of >. from the Instance command prompt. We recommend that you save this directory to the same directory where you saved your other definitions. execute the following command: autorep -M ALL -q >> c:\directory\autosys. Then you have only one file to restore following a system failure.Backing up Definitions 3. from the Instance command prompt. Note: You can create a job that runs periodically to back up your definitions automatically. This command saves your global variables to a file named globals. execute the following command: autorep -G ALL > c:\directory\globals. 5.jil where: directory Is a directory outside of the Unicenter AutoSys JM directory structure. Save your global variables to their own file. 6. run the gatekeeper command to print your current license keys to a file. Append your machine definitions to the same file that contains your job definitions. machine. We recommend that you append your job. Save your license keys. execute the following command: monbro -N ALL -q >> c:\directory\autosys.jil where: directory Is the same directory where you saved your job definitions. This file is simply a record of what you must redefine following a system failure. and monitor and browser definitions to the same file. Note: To append definitions to an existing file.jil. a directory outside of the Unicenter AutoSys JM directory structure.jil where: directory Is the same directory where you saved your job definitions. Maintaining 14–17 . a directory outside of the Unicenter AutoSys JM directory structure. 4. from the Instance command prompt. Append your monitor and browser definitions to the same file that contains your job and machine definitions.

Choose File. and monitor and browser definitions. 14–18 User Guide . In the Open dialog. reference your backup file. Restore your calendar definitions: a. Open a Calendar Editor window. select the directory and file name of the text file that contains your calendar definitions.jil where: directory Is the directory where you saved your definitions. from a AutoSys Instance command prompt. Import. c. 2. Click Open. Restore your global variables. The Open dialog is displayed. d. 3. redefine any global variables and reset the necessary Administrator settings. machine. execute the following command: jil < c:\directory\autosys. b. Restore your job. To restore definitions: 1.Restoring Definitions Restoring Definitions The procedure in this section assumes that you backed up your definitions by following the procedure in Backing Up Definitions in this chapter.

Due to the critical nature of the information stored in the database. you can use a Sybase. running. The Event Processor reads from the Event Server to determine what actions to take. Note: While Unicenter AutoSys JM uses the database solely as an SQL engine. it does use Sybase Open Client C Library communications protocol. Maintaining 14–19 . and Microsoft SQL Server Multi-Protocol Net-Library to send events around the system. an Oracle. or a Microsoft SQL Server database. you can configure to run with Dual Event Servers (two databases). For this database. The Remote Agents send starting. Dual databases provide redundancy in the event of an Event Server crash.Database Overview Database Overview All information is stored in a relational database known as the Event Server or database. Oracle SQL*Net V2. and completion information about jobs to the Event Server. An Event Server contains all of the information about a particular instance.

In Dual Server mode both servers are peers. “ in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. The Event Processor continually reads from both databases as it processes events. and the Event Processor is responsible for keeping the databases synchronized. Using Dual Event Server Mode When you configure with Dual Event Servers. For information about installing a second Event Server. An Event Server contains the following objects: ■ ■ ■ ■ ■ Job definitions Events Monitor and report (browser) definitions Calendar information Machine definitions For a list of the database tables and views as well as the event and alarm codes used in the database. see the chapter “Database Tables and Codes.Event Server Overview Event Server Overview An Event Server can be associated with only one instance and one running Event Processor. 14–20 User Guide . all of the data is duplicated on two Event Servers. see the section Installing Dual Event Servers in the chapter “Advanced Configurations.” in the Unicenter AutoSys Job Management for Windows Installation Guide.

The size requirements for your database depend on the following: ■ ■ ■ ■ The number of jobs you define. How many of the jobs have dependencies.) Maintaining 14–21 .Event Server Overview Database Storage Requirements The standard sizes for databases are 64 MB (Sybase and Microsoft SQL Server) and 128 MB (Oracle). it generates at least three events and an entry in the job_runs table. you should create a larger database. If your job load is large. The standard sizes for databases are the recommended sizes. How often the jobs are run. How often the database is cleaned. (Every time a job runs.

This information is stored in the Registry. Event Server 2 Event Processor Remote Agent databases Processes The previous illustration shows one instance that is configured with Dual Event Servers. OS File AutoSys Administrator setting Instructs Remote Machine: Command to execute and databases to send events to. The controlling variable in the architecture is the environment variable named AUTOSERV. the database. 14–22 User Guide . which are used only by this one instance. see the chapter “Administrator. and how the three primary components (the Event Processor. you must execute commands in these windows. For more information on configuring instances. You define the configuration for an instance at installation and by using the Unicenter AutoSys Administrator. Both the Event Processor and the Remote Agent ensure that events are written to the appropriate databases. It depicts how Unicenter AutoSys JM determines which database to use.Database Architecture Database Architecture The following illustration shows the layout of databases in an Unicenter AutoSys JM environment. One Instance of AutoSys — %AUTOSERV% Event Server 1 Define Jobs Read Registry to determine which databases to use.” in this guide. All commands access it. and thus. and it will help you understand configuration options. In the Unicenter AutoSys Administrator. which is the instance name. This variable along with other specific variables are set in the Instance Command Prompt window. you can specify which databases to use. and the Remote Agent) interact.

it does not process any events. You can customize the settings by using the Unicenter AutoSys Administrator. If these events are not “pruned” from the database periodically. this maintenance cycle starts at 3:30 a. By default. there are defaults in place that provide frequent. Therefore. see the section Administrator Event Server in the chapter “Administrator. Periodic maintenance is essential to keeping Unicenter AutoSys JM working correctly. Daily Database Maintenance Once a day. You can specify the Database Maintenance Command and Database Maintenance Time in their fields on the Unicenter AutoSys Administrator Event Processor screen. automatic maintenance. Use a 24-hour format for the time entry. In fact. During this time.General Database Maintenance General Database Maintenance You can configure Unicenter AutoSys JM to maintain it self as it runs. we recommend that you use the suggested periodic maintenance practices described in this section. the database will eventually fill up. In addition to this regularly scheduled maintenance.” in this guide. If it is necessary to change the start time. the Event Processor performs internal database maintenance.m. Several events are generated for each run of each job. For information on setting the database maintenance time and using the Unicenter AutoSys Administrator. you can issue general and database maintenance commands from the Instance Command Prompt. Maintaining 14–23 . it waits for the maintenance activities to complete before resuming normal operations. bringing Unicenter AutoSys JM and its jobs to a halt. reset it to a time of minimal activity.

but DBMaint reports the whole extent as used space. old data is overwritten with the new data. ■ Note: If you use an Oracle database. DBMaint runs the archive_events command to remove old information from the various database tables. job_status. Specifically. it computes statistics for all of the tables. Run the dbspace command to check the available space in the database. it issues warning messages and generates a DB_PROBLEM alarm. it updates statistics for the event. and job_cond tables.bat batch file during its daily maintenance cycle.bat Batch File By default. job. When dbstatistics is run.General Database Maintenance DBMaint. Unicenter AutoSys JM executes the %AUTOSYS%\bin\DBMaint. The extents may be nearly empty. For Oracle. This can occur because DBMaint calculates how much space is not allocated for extents. This batch file runs the dbstatistics and archive_events commands. ■ Calculate and update the average job run statistics in the avg_job_run table. DBMaint runs the dbstatistics command to perform the following tasks: ■ Update statistics in the database for optimal performance. For Sybase and Microsoft SQL Server databases. autotrack log information from the audit_info and audit_msg tables 14–24 User Guide . running DBMaint may report that your database is close to full when this is not the case. If the amount of free space is insufficient. archive_events removes the following: ■ ■ ■ Events and any alarms associated with them from the event table Job run information from the job_runs table.

bat File You can modify the %AUTOSYS%\bin\DBMaint.” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. tells you how much space is left in your database. then. you will not lose your changes. you may see many Sybase deadlock messages in the event_processor log.bat batch file. This is a good way to calculate how many events in a single day can be maintained safely in the database before they should be archived.out. you can turn on row-level locking. as well as the event and alarm codes used in the tables. you should keep a backup copy of it. when you upgrade. see the section Bundled Sybase Backup and Recovery.General Database Maintenance The output from DBMaint. For more information on backing up bundled Sybase. and then add your enhancements to the copied version. For a list of the database tables and views. Maintaining 14–25 . you might want to modify the batch file to perform database backups also. see the chapter “Database Tables and Codes. in this chapter. When you modify the script. %AUTOUSER%\out\DBMaint. 0. For example. You can use your enhanced batch file to modify the newly installed file. To turn on row-level locking for the entire database. If you modify the script. type the following at an xql prompt: sp_configure "lock scheme". datarows. The batch file name is specified in the Database Maintenance Command field on the Unicenter AutoSys Administrator Event Processor screen. Data Locking Depending on your environment. it can affect performance.” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide Modifying the DBMaint. see the chapter “Commands. For more information on the dbstatistics and archive_events commands. copy it first. so that you can check (and monitor) if the event tables are filling up. To reduce the number of deadlocks. While this has no adverse effect on the integrity of your system.

If there was a rollover and a switch to Single Server mode. corrupt database or media failure). and the Event Processor detects an unrecoverable error condition on one of the Event Servers. it automatically rolls over to Single Server mode. and so that client processes will not try to write to the down Event Server. Based on usage. we recommend the following tables: Tables event job2 job_runs proc_event job_cond last_Eoid_counter job job_status next_oid Event Server Rollover Recovery When Unicenter AutoSys JM runs in Dual Server mode. 14–26 User Guide . Where <table> indicates the name of the table on which to configure row-level locking. Unicenter AutoSys JM automatically rolls over to the functioning server and continues to run in Single Server mode. Unicenter AutoSys JM makes these changes so that you and the utilities trying to access the database will know that it is now running in Single Server mode. A database had an unrecoverable error (for example. the Administrator Event Server screen indicates this in two ways: the Status field shows which Event Server is DOWN. with the following command from an xql prompt: alter table <table> lock datarows. An unrecoverable error is defined as one of the following: ■ The connection to the database is lost. ■ If one Event Server is lost. you can lock tables individually. and after the configured number of reconnect attempts.Event Server Rollover Recovery Or. the database remains unconnected. and the Database Rollover Has Occurred check box is checked.

You will use this script both when you install a second Event Server after running in single mode and when you want to re-enable Dual Server mode after rolling over to Single Server mode. Before you can start with both Event Servers however. Services. After you recover the crashed server. Start the Event Processor: a. Maintaining 14–27 . Exit the Unicenter AutoSys Administrator. you can reconfigure Unicenter AutoSys JM to run with Dual Event Servers. b.NT Perl script. Choose AutoSys. c. Note: The Event Processor marks both Event Servers as being in Dual Server mode.Event Server Rollover Recovery Returning to Dual Server Mode After a Rollover When an Event Server is down. To restore a down Event Server and Dual Server Mode 1. b. Note: AutoSys provides the autobcp. 5. you must make sure that they are synchronized. Specify the appropriate Computer and Instance. choose AutoSys. Open the Unicenter AutoSys Administrator from the program group. Click Enable to start the disabled server. In the open Unicenter AutoSys Administrator. therefore. D. Select the Event Processor service from the drop-down list. Synchronize the Event Servers by using the autobcp. 3. Unicenter AutoSys JM client processes and commands check the flags in both Event Servers for consistency. under any circumstances. simply bring that Event Server back on-line and run in Dual Server mode. Event Server to go to the Event Server screen. Enable the second database: a. you must start the Event Processor before running any other commands. c. 4. Stop the Event Processor by entering the following command in an Instance Command Prompt window (which you open from the program group): sendevent -E STOP_DEMON 2. and click OK. do not. Click Start Services.NT Perl script to synchronize the databases.

Ensure that no clients (for example. (For Oracle. you will need more disk space for the temporary file. If one Event Server missed an event due to recovery or network problems. 14–28 User Guide .NT Perl script identifies one database as the “source” and the other database as the “destination” for the synchronization process.Event Server Rollover Recovery Synchronizing the Databases The autobcp.NT script. Before you run the autobcp.NT script while jobs are running on remote machines. Therefore. GUI) are running. If you have made your database larger. It deletes all of the data in the destination database and replaces it with the data in the source database. You can run the autobcp. archive it before you run this Perl script. ■ ■ ■ Note: When you stop the Event Processor. you are asked to supply the path to the Oracle software before the script runs. and the standard sizes for AutoSys databases are 64 MB (Sybase and Microsoft SQL Server) and 100 MB (Oracle). it copies that event to the database that is missing it. this feature also dynamically synchronizes both servers.) Ensure that both Event Servers are running. The script deletes this temporary file after the synchronization is complete. This is not a problem. because the Event Processor always reads from both Event Servers. however. If it finds an event on one server that is not on the other. In the worst case scenario. The temporary file will be the size of your database. there might be events on the source Event Server that are not stored on the destination Event Server. the jobs that are running will run to completion.NT. if you want to save the data in the destination database. Event Processor. check the following: ■ Ensure that you have enough disk space for the temporary file created by autobcp. Ensure that the AUTOSYS variable and either the SYBASE or ORACLE_HOME variables are set correctly.

NT source_server source_db destination_server destination_db autosys_password dump_file ■ For Oracle databases: perl autobcp. enter the following command: ■ For Sybase databases: perl autobcp. Specifies the temporary file used in the transfer of data from one database to the other. see the Microsoft SQL Enterprise Manager. For Microsoft SQL Server. For Sybase this is defined in the SQL. source_db Specifies the source Sybase or Microsoft SQL Server database (for example.NT source_server source_db destination_server destination_db autosys_password dump_file MSSQL_path where: source_server Specifies the name of the source Sybase or Microsoft SQL Server (for example. AUTOSYSDB2). Specifies the destination Sybase or Microsoft SQL Server database (for example. Then. Specifies the destination Oracle instance (for example. enter the following: cd %AUTOSYS%\DBOBJ 2. Specifies the password for the “autosys” user (by default. AUTOSYSDB). In an Instance Command Prompt window. autosys). the “autosys” user password is “autosys”).Event Server Rollover Recovery To synchronize the databases 1.INI file. destination_server destination_db source_instance destination_instance autosys_password Specifies the destination Sybase or Microsoft SQL Server database Specifies the source Oracle instance (for example. dump_file Maintaining 14–29 .INI file. AUTOSYSDB2).NT source_instance destination_instance autosys_password dump_file oracle_path ■ For Microsoft SQL Server databases: perl autobcp. For Sybase this is defined in the SQL. AUTOSYSDB).

EXE program. you see messages on your screen. If the script completes successfully. MSSQL_path Synchronizing Sybase Databases If you are synchronizing two Sybase databases. in this chapter. as described in the following database-specific sections. autobcp.NT: Dump file name [dump. in this chapter.NT: Source server [SourceServer]? > source_server AUTOBCP.NT: Destination server [DestinationServer]? > destination_server AUTOBCP. If the script is not successful.Event Server Rollover Recovery oracle_path Specifies the path to the Oracle import and export executables set in ORACLE_HOME. the script prompts you with questions and requests confirmation. 14–30 User Guide . Specifies the local path to the Microsoft SQL Server directory. in this chapter. in this chapter.fil]? > dump.. you are prompted to answer the following questions. you see descriptive messages on your screen. If you enter any information incorrectly. continue with the steps described in the section Returning to Dual Server Mode After a Rollover. it checks for the existence of both databases before it begins moving the data. If the script is not successful. If you enter the information correctly.NT: Are you sure? ([y]|n)> y . When it completes. After the script starts. the script runs. autobcp: complete If the script runs successfully. and then the script runs: AUTOBCP. continue with the steps described in the section Returning to Dual Server Mode After a Rollover.NT: Source database [autosys]? > autosys AUTOBCP. see the section Handling Errors.NT: Autosys password [password]? > autosys_password AUTOBCP.NT: Destination database [autosys]? autosys AUTOBCP.NT: Moving data from source_server:autosys to destination_server:autosys AUTOBCP.file AUTOBCP. When it completes.NT must be able to locate the Microsoft binn\BCP.. see the section Handling Errors.

NT: Path for MicroSoft SQL [c:\mssql]? > c:\path AUTOBCP.fil]? > dump. you are prompted to answer the following questions.NT: Dump file name [dump. you see messages on your screen..NT: Are you sure? ([y]|n)> y . in this chapter. in this chapter.NT: Source server [SourceServer]? >source_server AUTOBCP. continue with the steps described in the section Returning to Dual Server Mode After a Rollover. you are prompted to answer the following questions.NT: Destination database [autosys]? > autosys AUTOBCP.. autobcp: complete If the script runs successfully. autobcp: Source instance [SourceInst]? > source_path Destination instance [DestinationInst]? > destination_path Autosys password [password]? > autosys_password Dump file name [dump.Event Server Rollover Recovery Synchronizing Oracle Databases If you are synchronizing two Oracle databases. When it completes.. continue with the steps described in the section Returning to Dual Server Mode After a Rollover. see the section Handling Errors. you see messages on your screen. in this chapter. Maintaining 14–31 . If the script is not successful. When it completes.NT: Autosys password [password]? > autosys_password AUTOBCP..NT: Destination server [DestinationServer]? > destination_server AUTOBCP. and then the script runs: autobcp: autobcp: autobcp: autobcp: autobcp: autobcp: autobcp: .file AUTOBCP. Synchronizing Microsoft SQL Server Databases If you are synchronizing two Microsoft SQL Server databases. in this chapter.NT: Source database [autosys]? > autosys AUTOBCP.fil]? > dump. ORACLE_HOME) [c:\orant]? > c:\path Moving data from source_path to destination_path Are you sure? ([y]|n)> y complete If the script runs successfully.NT: Moving data from source_server:autosys to destination_server:autosys AUTOBCP. see the section Handling Errors. and then the script runs: AUTOBCP.file Path for Oracle (ie. If the script is not successful.

this setting is in the SQL.ORA file. For bundled Sybase. and for Oracle it is in the TNSNAMES.” If you run unbundled Sybase.Event Server Rollover Recovery Handling Errors If the autobcp. check the following: ■ Did you correctly specify the source and the destination databases in the Perl script command? Do you have the correct Event Server ports set for the databases? For Sybase. and OracleTNSListener. For Microsoft SQL Server. ■ ■ 14–32 User Guide . For a Microsoft SQL Server. the service name is MSSQLServer. If this happens.INI file. the port is specified at installation time with the Microsoft SQL Server Setup program. verify that the status of SYBSQL_LOCAL is “started. look at the NT Control Panel Services dialog. the service has a different name. OracleStart*.NT process detects an error. If you run an Oracle database. verify the status of the following services (substitute your Oracle SID for the asterisk): OracleService*. it exits and displays an error message. Are both Event Servers started? To verify this.

This improves access time. Improving Oracle Database Performance Tuning Oracle to improve its performance is complicated. The Ratio of Misses should be less than 1%. Improving Sybase Database Performance These are ways to improve your Sybase database performance: ■ Increase the amount of memory that Sybase can use. (The Ratio of Misses number is displayed as a percentage. ■ ■ Upgrade your processor.) If it is higher than 1%. ■ ■ WARNING! Only the database administrator should put your data on a raw partition. memory. The following are some suggestions for the database administrator: ■ Tune the shared pool size. Install the Sybase server and the Event Processor on a dedicated machine or machines.ora value of DB_BLOCK_BUFFERS. Make changes to the shared pool size by altering the init. and/or hard disks. Use the Sybase server for Unicenter AutoSys JM only. For unbundled Sybase only.Improving Database Performance Improving Database Performance This section contains information about improving your database performance. Maintaining 14–33 . To determine if you need to increase the shared pool size. Do not share machine resources with other processes. sum(reloads) “Cache Misses while Executing”. ■ Tune the buffer cache. put your data on a raw partition. WARNING! Only the database administrator should increase Sybase memory.ora value of SHARED_POOL_SIZE. Make changes to the buffer cache by altering the init. enter the following query in SQL*Plus: select sum(pins) “Executions”. you should increase the value of SHARED_POOL_SIZE incrementally until the value of Executions approaches zero. ((sum(reloads)/sum(pins))*100) “Ratio of Misses” from v$librarycache.

increase the value of DB_BLOCK_BUFFERS. value from v$sysstat where name in (‘db block gets’. different drive controllers. ‘sorts (disk)’).(physical reads/(db block gets + consistent gets)) The closer the hit ratio approaches 1. Make sure you have at least five percent free memory. ‘physical reads’). Tune the sort area. A sort area in memory sorts records before they are written to disk.95. Increasing the size of the sort area by increasing the init. enter the following query as the “sys” user in SQL*Plus: select name. ■ Maximize disk I/O by separating the data files. value from v$sysstat where name in (‘sorts (memory)’. If you have disk contention. place the autodata and autoindexes data files on separate disk drives. then increase the value of SORT_AREA_SIZE. Calculate the hit ratio for the buffer cache by using this formula: hit ratio = 1 . the better your system performs. and if possible. monitor the sorting disk activity in your system by entering the following query in SQL*Plus: select name. If you have free memory and the hit ratio is below . 14–34 User Guide .00. ■ To determine if sorting is affecting the performance of your system. Monitor the statistics from the query while running.ora value of SORT_AREA_SIZE improves sort efficiency.Improving Database Performance To determine if you need to allocate more memory. ‘consistent gets’. If disk sorts are greater than one percent of memory sorts.

and then returns the information to the client. you can execute those commands from any machine that has access to the Event Server and is a licensed client. Sybase Architecture The Sybase database is based on a client/server architecture. The client communicates with the server using a C library known as Open Client. This library handles the communications between the client application and the Sybase SQL Server as well as sending requests and parsing results for the use of the application. It listens on a specific port for a request from a client. or the DB Library. stopping. It is through this mechanism that the Dual Event Servers are maintained. Maintaining 14–35 . single process that runs on one machine. this section is specific to Sybase Event Server maintenance. If you are using an existing Sybase. with the communications between clients and server built into the product. the Remote Agent. fulfills that request. Note: The following sections are specifically for bundled Sybase users. and monitors. It contains information to help you query the database as well as to perform basic maintenance procedures on Sybase SQL Server databases. or Microsoft SQL Server database. Note: The DB Library allows a client to maintain multiple connections to the same server or multiple servers. This means that all AutoSys commands and processes. including the Event Processor. Oracle. the following environment variables are used: DSQUERY Defines the name of the Sybase dataserver. This server is a multithreaded. Sybase Environment If you are using a Sybase. consult your database administrator for details on starting. and configuring your database. The server portion is called the Sybase SQL Server. Because all commands are merely Sybase clients.Maintaining Bundled Sybase SQL Servers Maintaining Bundled Sybase SQL Servers Because you can purchase Unicenter AutoSys JM with a bundled Sybase database. are DB Library applications that connect to the databases.

there are two users defined by default in the database: the system administrator and the user. in this guide. or you can log onto Sybase as “sa. or the appropriate password.INI file. Unicenter AutoSys JM uses the Sybase configuration file to look up database information. For more information on changing the “autosys” password. see the section autosys_secure in the chapter “Commands. which is an supplied utility that can access the Sybase dataserver from any properly configured client machine. which on UNIX is the interfaces file and on Windows is the SQL. Database Users When using the bundled Sybase version. Changing the System Administrator Password. you must log onto Sybase as “sa” using the “sysadmin” password.” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. see the chapter “Commands” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. User System Administrator User User Name sa autosys Default Password sysadmin autosys For information on changing the “sa” password. you use the xql utility. You do most of the Sybase administration through system-stored procedures. For more information on using xql. The Sybase software directory contains the Sybase configuration file. Default Sybase Users To perform many administrative tasks on your bundled Sybase database. All system-stored procedures start with the sp_ prefix. In most cases. Each of these users has a default user name and password. 14–36 User Guide . It is the means by which the network is navigated to find the Sybase dataserver. see the section.” then operate interactively at the xql prompt.Maintaining Bundled Sybase SQL Servers SYBASE Specifies the complete path to the Sybase software directory. You can log onto Sybase within a command line.

Execute the following xql command in an Instance Command Prompt window: xql -Usa -Psysadmin The following prompt appears: xql>>[AUTOSYSDB][master] 1> Note: If you are not using the default settings. and “autosys” is the user password): xql -Uautosys -Pautosys -c "select getdate()" If this command returns the date. Make sure that the new password is recorded. newPassword. the database is running. Starting Sybase When you reboot the machine after installation. To change the system administrator password 1. enter the following command at the Instance Command Prompt (assuming “autosys” is the Unicenter AutoSys JM user. The new password must be at least six characters. Maintaining 14–37 . the name of the Service is SYBSQL_LOCAL. the bundled Sybase database is started. the old password is unrecoverable. otherwise. It is a service that is started automatically with subsequent startups. Enter the following command sequence (replacing newPassword with the new password): xql>>[AUTOSYSDB][master] 1> sp_password xql>>[AUTOSYSDB][master] 2> sysadmin. the name of your dataserver is substituted for AUTOSYSDB.Maintaining Bundled Sybase SQL Servers Changing the System Administrator Password You can change the system administrator password from its initial value of “sysadmin” to a new value. If the database is not running. the entire database will have to be re-installed. it has a different name. If you are using bundled Sybase. To verify that the database is up and accessible. you can start it from the Control Panel Services dialog on the machine where the database is installed. and your database administrator can start it. WARNING! After you change the “sa” password. If you are using a pre-existing dataserver at your site.

Before you attempt to stop the Event Processor. it has a different name. For information on changing the “sa” password. 14–38 User Guide . the Sybase service is shut down correctly as part of that process. stop it. 2. or by checking its status on the Unicenter AutoSys Administrator Services screen. you can stop the Sybase service from the Control Panel Services dialog.Maintaining Bundled Sybase SQL Servers Stopping Sybase If you perform a Windows Shutdown. If the Event Processor is not running and you send the event. If you are using a pre-existing dataserver at your site. use this command: xql -Usa -Psa_password -c "shutdown with no_wait" Note: In addition. Stop the Sybase service by entering the following command (the sa_password is initially installed as “sysadmin”): xql -Usa -Psa_password -c "shutdown" This command allows any database processes to complete. If the Event Processor is running. and then shuts the database down. If you are using bundled Sybase. see the section Changing the System Administrator Password. you must stop the Event Processor first. log on as the Exec Superuser and enter the following command at the Instance Command Prompt: sendevent -E STOP_DEMON ■ If you are not sure whether the Event Processor is running. do not sent the STOP_DEMON event. it will be queued and sent when the Event Processor is started again. and your database administrator can stop it. the name of the Service is SYBSQL_LOCAL. If you need to stop the Sybase service. and it is restarted automatically with the Restart process. ensure that it is running by using the chk_auto_up command. If you must shut down the database immediately. To do this. To stop Sybase 1. in this guide.

For a detailed description of how to use xql. Maintaining 14–39 . use the ISQL/w graphical query interface. Note: The xql utility functions only with the Sybase database. use the SQL*Plus command language interface. Use this utility for interactive database queries. If you use an Oracle database. see its entry in the chapter “Commands. which resides in the %AUTOSYS%\bin directory. If you use a Microsoft SQL Server.Maintaining Bundled Sybase SQL Servers Accessing Sybase Unicenter AutoSys JM comes with a utility named xql.” in the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide.

Maintaining Bundled Sybase SQL Servers Identifying Processes Connected to the Database These are reasons you might want to identify the processes that are connected to the database: ■ Before you change the “autosys” user password or shut down Unicenter AutoSys JM . The list of processes connected to the database is displayed. hostname. then shut them down. Many GUI processes connected to the database can slow it down. autocal autocons autosc auto_remote event_demon hostscape jil jobscape sendevent timescape xql 14–40 User Guide . xql>>[AUTOSYSDB][master] 2> hostprocess. ■ To see what processes are connected to the database and their status At the xql prompt. The processes without names are internal Sybase processes. you should ensure that no processes are connected to the database. You can see how many and what type of processes are connected to the database. You can identify the active processes. enter the following: xql>>[AUTOSYSDB][master] 1> select program_name. like: program_name ------------xql hostname --------Joe hostprocess ----------14050 status -----running sleeping sleeping sleeping sleeping sleeping recv sleep recv sleep event_demon jil Michelle Erik 13448 12272 status 0. xql>>[AUTOSYSDB][master] 3> status from sysprocesses. which you can ignore. The following are the most common process you will see. and event_demon is the Event Processor. and then ask users to shut down the GUIs they are not currently using. xql is the process running your query to display the processes. rows affected 8 In the example list of processes.

If your jobs do not run when you expect them to. Before dumping a database to a file. You should decide on a routine for backing up the database so that you will have no trouble recovering a lost database. using the backup database dump. and then you must identify a dump file to the database by running the Sybase system sp_addumpdevice procedure. you can check the database clock.Maintaining Bundled Sybase SQL Servers Displaying the Database Date and Time Jobs are scheduled and run based on the date and time for the machine on which the database is running. This section describes how to dump the database to a file. Maintaining 14–41 . enter the following: xql>>[AUTOSYSDB][master] 1> select getdate(). which you can then back up to tape along with the rest of your production system. so that you can recover it in the event of catastrophic system or media failure. To display the database date and time At the xql prompt. The sp_addumpdevice procedure requires a logical name for the dump file (the dump and load database commands use this name) as well as a physical name (the file’s full pathname). you must configure a backup server by using the Sybase Configure Sybase SQL Server dialog. Bundled Sybase Backup and Recovery You must back up the database periodically.

9. then use DATABASENAME_BS). The backup service that you named should be “Started. In the Enter Connection dialog. 10. and you can click Continue. and click Configure New Backup Server under Backup Server. which should be AUTOSYSDB_BS (if you are not using the default Event Server name. This action opens the Enter Connection dialog. the process to create the backup server runs. To ensure that the backup server service was created and is running. 8. do not use your Event Server port number for this value. In the Network Connections dialog. the Sybase BCKServer_AUTOSYSDB_BS service should appear as a Service with a Status of “Started. check the Control Panel Services dialog. In the Network Connection dialog. In the dialog. Note: The port number must be one not already in use at your site. click Network Addresses. click Continue. click Exit. select Backup Server under Products. At this time. Then. the New Backup Server Complete prompt appears. click OK.Maintaining Bundled Sybase SQL Servers Configuring a Backup Server To configure a Sybase backup server 1. Then. and if it is correct. if you supplied the AUTOSYSDB_BS name as the Default Name of Backup Server. enter the Name of the Backup Server. click OK.” After this process is done. check the information that you just entered. 5. In the Configure Backup Server dialog. change the Protocol to “NLWNSCK WinSock TCP/IP Driver. In the Backup Server Name dialog. When it completes. 14–42 User Guide . 3. This action opens the Network Connections dialog. and enter any unused port number in the Connection Info field. This action opens the Backup Server Name dialog. 6.” That is. In the Configure Sybase SQL Server dialog.” which is located on the drop-down list. click Add. In the Configure Backup Server dialog. click Continue. 4. 2. Enter the following command at an Instance Command Prompt: syconfig This command runs the Sybase Configure Sybase SQL Server dialog. you can back up the database to a file anytime. 7.

check the C:\tmp directory for the new autodump file. Re-create the database. or dump. when necessary.Maintaining Bundled Sybase SQL Servers Backing up the Database to a File To backup. autodump. To back up the database. the database to a file 1. Recovering a Bundled Sybase Database To recover a damaged database using the backup file 1. 3. 3. Execute the following xql command at the Instance Command Prompt: xql -Usa -Psysadmin 2. This should return the following message: 'Disk' device added. enter the following: xql>>[AUTOSYSDB][master] 1> dump database autosys to autodump. Note: For this example to work. enter the following at the xql prompt: xql>>[AUTOSYSDB][master] 1> sp_addumpdevice 'disk'. Your system administrator can now archive the autodump file. Restart the Event Processor. 4. 2. xql>>[AUTOSYSDB][master] 2> 'C:\tmp\autodump'. Drop the damaged database. Stop the Event Processor. When the process completes. To define the dump device to Sybase. and you can use the file for restoring the database. 5. Before using this process to recover a damaged database. Maintaining 14–43 . Reload the database. the C:\tmp directory must already exist on the database machine. investigate all other options. WARNING! You should drop the database and re-create it only in extreme situations. 2.

replacing the Sybase “go”. To create the new database. If the database is so damaged that drop database does not work. 3. enter the following: xql>>[AUTOSYSDB][master] 1> drop database autosys. Use the create database command to create the new database.Maintaining Bundled Sybase SQL Servers Stopping the Event Processor To stop the Event Processor Log on as the Exec Superuser and issue the following command at an Instance Command Prompt: sendevent -E STOP_DEMON Dropping the Damaged Database You can drop the damaged database by using the drop database command. the autodump file) that you are recovering. This new database is used to load the database dump file (for example. contact your Technical Support representative. at the xql prompt. At the xql prompt. enter the following: xql>>[AUTOSYSDB][master] 1> create database xql>>[AUTOSYSDB][master] 2> autosys on default xql>>[AUTOSYSDB][master] 3> = 50. Re-Creating the Database After dropping the damaged database. To drop the damaged database 1. you must recreate a new database. Before you drop the damaged database. you should ensure that you have a database dump file to use to restore the database. To re-create the database 1. Enter the following xql command at the Instance Command Prompt: xql -Usa -Psysadmin 2. The output generated by this command will look similar to: 14–44 User Guide . however. Note: The above size of 50 MB is only an example. The semicolon at the end of the command line is an end-of-statement delimiter in xql.

a message similar to the following should be returned: Database owner changed. Reloading the Database You are now ready to execute the load database command to restore the database you originally dumped to autodump. When you complete this process. To reload the database and put it online Enter the following at the xql prompt: xql>>[AUTOSYSDB][master] 1> load database autosys xql>>[AUTOSYSDB][master] 2> from autodump. you can restart the Event Processor using the Unicenter AutoSys Administrator Services screen. Unicenter AutoSys JM will be in the state it was in when you dumped the database to the backup file. xql>>[AUTOSYSDB][master] 1> online database autosys. Level 0. xql>>[AUTOSYSDB][autosys] 1> sp_changedbowner xql>>[AUTOSYSDB][autosys] 2> autosys. To exit xql Enter the following at the xql prompt: xql>>[AUTOSYSDB][master] 1> exit Restarting the Event Processor Then. To change the owner of the new database to “autosys. The database is now restored and online. When the procedure has completed successfully. Line 1 CREATE DATABASE: allocating 15360 pages on disk ‘default’ 2. Maintaining 14–45 . you must put the database online.Maintaining Bundled Sybase SQL Servers Msg 1805.” enter the following at the xql prompt: xql>>[AUTOSYSDB][master] 1> use autosys. State 1. Note: For Sybase System 11. Previous versions of Sybase did not require this.

dual-event servers.Chapter 15 Administrator This chapter describes the Unicenter AutoSys Administrator and how to use its various screens to configure Unicenter AutoSys JM instances. Once set. the event processor bases much of its runtime behavior on the parameters that are defined in the Unicenter AutoSys Administrator. including cross-instance job dependencies. Unicenter AutoSys JM reads this configuration information to determine the databases to which to connect. and you can use it to view and modify the configuration parameters for each instance you install. The Administrator has the following screens. this chapter describes how to use the Unicenter AutoSys Administrator to implement several advanced configurations. and shadow event processors. Unicenter AutoSys JM reads this information to determine runtime behavior. which contain the associated configuration parameters: ■ ■ ■ ■ ■ Instance Remote Agent Event Server Event Processor Notifications Administrator 15–1 . On startup. About the Administrator The Unicenter AutoSys Administrator is installed as part of the Console Utilities. as well as how to react to certain error conditions. In addition. these configuration parameters are loaded into the Windows Registry. In particular.

About the Administrator ■ ■ ■ ■ System Information Sounds Security Services To modify many of these settings. For information on the configuration file on UNIX platforms. Therefore. If you do not have these privileges. if you make a change to an Administrator setting that you want implemented immediately. see the chapter “Configuring . However. Sounds screen Which allows you specify the sounds associated with certain alarms and events. Services screen Which allows you to view the status of remote agent and event processor services (but you cannot change the status without the correct permissions). 15–2 User Guide . Security screen Which allows you to set up your own trusted users for remote authentication. this chapter provides both the Administrator field name and its UNIX configuration file parameter equivalent. Note: Many of the configuration parameters that you set on Windows using the Unicenter AutoSys Administrator have a corresponding configuration parameter on UNIX. ■ ■ ■ WARNING! The event processor reads the settings in the Unicenter AutoSys Administrator on startup only.” in the Unicenter AutoSys Job Management for UNIX User Guide.$AUTOSERV configuration file. and then restart it using the Administrator Services screen (which is described in the topic Using the Services Screen). When appropriate. you must have Windows Administrators group privileges. but you do have Windows Power User or User group privileges. you have access to only the following screens and actions: ■ Instance screen Which allows you to specify the computer and instance to which the settings belong. you must stop the event processor using the sendevent -E STOP_DEMON command. on UNIX you set these parameters in the $AUTOUSER/config.

see Administrator Instance Screen. press Shift+F1 while that screen has focus. Open the Unicenter AutoSys JM Help from the Unicenter AutoSys JM Help icon in the program group. see the Unicenter AutoSys JM Help. Event Server Event Processor System Informat ion Security Instance Past e Cut Export S ervices Remote Agent Sounds Notif ication Copy Abo ut Administrator Administrator 15–3 . Once you have started the Unicenter AutoSys Administrator. To open help for the Administrator. press F1 while the Administrator has focus.Starting the Administrator For information while using the Unicenter AutoSys Administrator. or open help from the Administrator. To open help on a specific Administrator screen. you must select an instance before you can use the various Administrator screens. Administrator Menu Bar and Toolbar The Unicenter AutoSys Administrator has a basic menu bar and toolbar that is available with all Administrator screens. Starting the Administrator To start the Unicenter AutoSys Administrator: Select the Unicenter AutoSys Administrator icon in the program group. For information on selecting an instance. The toolbar buttons are menu item accelerators.

Cut Removes the selected text and places it on the clipboard. Edit Menu The Edit menu contains the following options: Undo Undoes the last operation. View. Status Bar Toggles to show or hide the status bar. Paste Pastes the contents of the clipboard at the location of the cursor.Starting the Administrator Administrator Menu Bar The Administrator menu bar contains the File. Copy Copies the selected text to the clipboard. AutoSys. Edit. File Menu The File menu contains the following options: Export Exports the configuration settings to a text file. View Menu The View menu contains the following options: Toolbar Toggles to show or hide the toolbar. Exit Exits the AutoSys Administrator. and Help menus. 15–4 User Guide . Export As Writes the configuration settings to a text file that you specify.

which you can use to set the Trusted Hosts and Trusted Users for remote authentication. Event Processor Displays the Event Processor screen. This information is helpful when troubleshooting. Help Menu The Help menu contains the following options: Administrator 15–5 . Notifications Displays the Notifications screen. which you can use to specify user-defined alarm callbacks for certain types of system alarms. Once you select a computer and instance. Security Displays the Security screen. which you can use to view and set the sounds that are associated with certain events. Sounds Displays the Sounds screen.Starting the Administrator AutoSys Menu The AutoSys menu contains the following options: Instance Displays the Instance screen. which you can use to define the event processor behavior. which you can use to set the Remote Agent port number and its list of authorized event processors (used in remote authentication). Services Displays the Services screen. either for single-server or dual-server mode. as well as the information needed to run a shadow event processor. you can view and modify instance settings using the other Administrator screens. which you can use to view the settings for certain variables. but you should do so with caution. which you can use to specify event servers. which you can use to view and alter the status of Remote Agent and Event Processor services. Event Server Displays the Event Server screen. You can modify the settings on this screen. System Displays the System Information screen. which you can use to select the computer and installed instance. Remote Agent Displays the Remote Agent screen. You can also use this screen to enable and disable sound.

You can have multiple instances.Instances Help Topics Displays the Help Index and Find utility. which is prefixed by the three-letter instance ID that is specified by the %AUTOSERV% variable. They have a unique ID. which you can view or modify using the other screens of the Administrator. An instance is one licensed version of Unicenter AutoSys JM software running as a server and as one or more clients. you can configure Unicenter AutoSys JM to run with cross-instance job dependencies. (The %AUTOSERV% value is indicated on the Administrator System Information screen. The use of multiple databases is completely independent of multiple instances. called an eoid. An instance uses its own event processor and event server and operates independently of other instances. This naming convention ensures an event’s uniqueness and traceability across multiple instances. An event processor. each using dual-event servers. An instance is defined by the following: ■ ■ ■ A definition in the Unicenter AutoSys Administrator. The value of the %AUTOSERV% variable defined in the environment in which the event processor is running.) At least one event server (specified in the Administrator Event Server screen). In addition. 15–6 User Guide . on one or multiple machines. About AutoSysAdmin Displays release information on Unicenter AutoSys Administrator. Administrator Instance Screen in this chapter). Instances When you start the Unicenter AutoSys Administrator. ■ Events are associated with a specific instance. This screen lets you select a computer and instance. Note: You can set the instance ID only during the installation process. the Instance screen is displayed (see the figure in the section.

For information on running multiple instances and running cross-instance job dependencies. Administrator 15–7 .Instances For information on installing multiple instances. By default.” in the Unicenter AutoSys Job Management for Windows Installation Guide. To view the various Unicenter AutoSys Administrator screens. Computer The Computer setting specifies the host name of the computer on which Unicenter AutoSys JM is installed and to which you are connected. see the Installing Multiple Instances section in the chapter “Advanced Configurations. The Instance screen allows you to select a computer and AutoSys instance. this field contains the name of the machine that you are logged on to. see the chapter “Introduction. To connect to a remote machine: Enter the host name in the Computer field and click Connect. but you can connect to a remote machine to administer the instance information. you must first select a computer and installed instance on which to operate. the Instance screen is displayed. so you can view or modify that instance’s configuration settings.” in the Unicenter AutoSys Job Management for Windows Installation Guide. Administrator Instance Screen When you start the Unicenter AutoSys Administrator.

If necessary. The host name of the computer that you are logged on to is already selected when you open the window. which allows you to move from screen to screen. The instance that appears in the Instance field is selected. 3. You can have multiple instances running on the same machine. The Instance ID is referenced by the %AUTOSERV% environment variable. If necessary. After you select an instance. 15–8 User Guide . select a computer by typing in the Computer name and clicking Connect. Date Format The date format is where you can specify the format for the date in your area.Instances Instance The capitalized three-letter name that identifies a specific server installation. Click OK. the Instance ID is ACE. To select an instance: 1. but you can specify another name during the installation process. By default. the menu items and their corresponding toolbar buttons are enabled. as long as they have different instance IDs. The default is MM/DD/YYYY. select an instance from the Instance drop-down list. 2.

or: ■ Click the Remote Agent button on the toolbar. sends running and completion information about a task as events to the database. the remote agent logs on to the machine. Note: To modify the settings on this screen. Administrator 15–9 . it waits and tries again until it successfully communicates with the database.Remote Agents Remote Agents The remote agent is a Windows service running on a remote machine. starts the command specified for a given job. and then exits. When the event processor starts a job. If the remote agent is unable to transfer the information. and event processors that have permission to start processes on this remote agent (when remote authentication is turned on). To move to the Remote Agent screen do one of the following: ■ Select Remote Agent from the AutoSys menu. you must have Windows Administrators group privileges. and the event processor directs the remote agent to perform specific tasks. local logging directory. Administrator Remote Agent Screen The Administrator Remote Agent screen allows you to set the remote agent port number.

and it should be the same number for all remote agents associated with an instance. and all remote agents for an instance must use the same port number. 15–10 User Guide . This number must be different from the event server port number. in which Unicenter AutoSys JM should write that remote agent log files for jobs. You set the TCP/IP Port number at installation time. each instance must have a unique remote agent port number. in this chapter.Remote Agents Defining Remote Agent Configuration Parameters Note: This section lists and describes the configuration parameters located on the Remote Agent screen. The default number is 5280. on the remote agent machine. see Defining Event Server Configuration Parameters. The internet service on the client machine uses the port number to point to the name of the service in the following file: %SYSTEMROOT%\system32\drivers\etc\SERVICES On Windows. Local Agent Logging Directory The Local Agent Logging Directory field specifies the local directory. see its description in “Enterprise Wide Logging Directory.” in this guide. but you can change this number using the Unicenter AutoSys Administrator. TCP/IP Port UNIX parameter: #AutoRemPort The remote agent TCP/IP port number specifies the port number for the remote agent. if you are running an ACE and a PRD instance. This setting overrides the enterprise-wide logging directory. That is. you must supply unique remote agent port numbers for each instance that you install. For information on the Enterprise Wide Logging Directory. For information on the event server port number. The event processor communicates to the remote agent by way of this TCP/IP socket connection.

If you turn on the event processor remote authentication. however. Administrator 15–11 . the remote agent verifies that the requesting event processor is on this list before it will process job requests. For information on turning on remote authentication. and when it appears in the top field. therefore. the machine host name is all that is required in this field. and click the Add EP button. each remote agent installation is associated with an instance.autostuff file. this list is located in the /etc/. Note: On Windows. When setting up event processor remote authentication on a UNIX machine.” in the Unicenter AutoSys Job Management Reference Guide. click the Remove EP button. see autosys_secure in the chapter “Commands. Unicenter AutoSys JM uses this list only if remote authentication is turned on. To delete an event processor from this list: Select the event processor. which you can do using the autosys_secure command. To add an event processor to this list: Type the event processor machine host name.Remote Agents Authorized Event Processor Host Names The Authorized Event Processor Host Names list specifies the host names of the event processors from which this remote agent can accept job-processing requests. and the entries are in the Instance:Machine_hostname format.

In addition. The Event Server Screen (see the figure in Administrator Event Server Screen in this chapter) allows you to view and modify database-specific configuration parameters. including job definitions and events. it will copy the missing event to the other server. see Dual-Event Servers in the chapter “Introduction. If it detects an event on one server and not the other. by defining and enabling the second event server. Unicenter AutoSys JM keeps these two servers synchronized. In this way. you can enable dual-server mode. Dual-Event Servers Unicenter AutoSys JM can run with two event servers. you can use this screen to determine if there has been a database rollover.” in the Unicenter AutoSys Job Management for Windows Installation Guide. When processing events. the remote agent sends events and writes to both event servers. the two event servers should reside on two different data servers. These two event servers contain identical information. As a safeguard. and you can use it to restart the down event server and reenable dual-server mode. which can include multiple databases. For information on installing and configuring dualevent servers. Unicenter AutoSys JM reads and writes to both servers simultaneously. 15–12 User Guide . see Installing Dual-event Servers in the chapter “Advanced Configurations.Event Servers Event Servers The event server is the database that contains all of the events and job definitions that are used by the event processor. Note: To avoid a single point of failure. In addition. a temporary problem in getting events to one of the servers will not interrupt processing. you can configure Unicenter AutoSys JM to run with two event servers. running on different machines. in dual-server mode. the event processor reads from both event servers. For more information about using dual-event servers. The event server is a Windows process and its associated data space (or raw disk storage). Using this screen.” in the Unicenter AutoSys Job Management for Windows Installation Guide. and this configuration provides complete recovery when a disaster occurs on one of the two servers.

or: ■ Click the Event Server button on the toolbar. you must have Windows Administrators group privileges. and dual-server mode.Event Servers Administrator Event Server Screen Using the Event Server screen. you can use this screen to determine if there has been a database rollover. you can view and modify the database-specific settings. To move to the Event Server screen: Do one of the following: ■ Select Event Server from the AutoSys menu. In addition. Note: To modify the settings on this screen. and to enable the down event server. Administrator 15–13 . The following illustration shows the Event Server screen for Sybase and Microsoft SQL Server installations. and you can configure Unicenter AutoSys JM for dual-event servers.

it must be exactly as it is defined for the database. the event servers should have different values in the Name field. For Oracle.ORA file. You can also define a second event server (using the “Event Server B” area) and enable dualserver mode. either when enabling a down server or when implementing dual-server mode. Note: You can enable and define either Event Server A or Event Server B to be in single-server mode. 15–14 User Guide . For Microsoft SQL Server.Event Servers Defining Event Server Configuration Parameters This section lists and describes configuration parameters located on the Event Server screen. Unicenter AutoSys JM uses this name to locate the event servers. and you can check the database settings using the Microsoft SQL Enterprise Manager. the logical names are stored in the SQL.INI Sybase interface file. Name or Alias UNIX parameter: EventServer The Name parameter specifies a logical name used to locate the database. the “Alias. Note: In the UNIX configuration file. the EventServer parameter is defined by the Name: Database combination.” or logical name. For dual-server mode. Enable Use the Enable button to enable the associated event server. For Sybase. WARNING! When you enter the event server information. is stored in the Oracle TNSNAMES. The largest single reason for “things not working” is that Unicenter AutoSys JM cannot determine which RDBMS to connect to or where to find the executables or configuration files. the logical name is the same as the host machine name. including case. Therefore. The “Event Server A” area defines a server for single-server mode. it is very important to make sure that all of the database information is set up correctly on every machine. When performing database queries.

For Oracle installations. running on different host machines. the EventServer parameter is defined by the Event Server Name: Database combination. see the topic “Defining Remote Agent Configuration Parameters.Event Servers Disable Use the Disable button to stop an event server and return to single server mode. Host Port The Port parameter specifies the port number for the TCP/IP socket connection between the event server and the remote agent. this name is autosys. Database UNIX parameter: EventServer The Database parameter specifies the particular database for the associated event server instance. this can be the same value for both event servers. you must stop and restart the event processor. This is a readonly field. and for dual server mode. Note that this number should be different than the value in the TCP/IP Port field in the Remote Agent screen. If you click this button. this field is disabled. For dual server mode. If you disable a server. For Oracle installations.” in this chapter. see Event Server Rollover Recovery in the chapter “Maintaining . Note: In the UNIX configuration file. For information on the remote agent port number. Administrator 15–15 . Database Provider Specifies the provider (manufacturer) of the Relational Database Manager System (RDBMS) that is being used for the AutoSys database. this field is disabled. we recommend that the two event servers reside on two different databases. The Host parameter specifies the name of the machine on which the associated event server runs.” in this guide. to avoid a single point of failure. it sets the associated event server status to DOWN. it is for informational purposes only. so that it is restarted in single server mode. For information on dual server mode and how to re-enable a DOWN event server. Typically. Status The Status field indicates whether the associated database is UP or DOWN. This is the port number on which the event server “listens” when waiting for requests.

If the event processor is unable to connect to both databases. DB Event Reconnect UNIX parameter: DBEventReconnect The Reconnect parameter specifies the number of times that an event processor should attempt to connect to the event server before shutting down. Upon startup. 5 values specifies that the event processor should attempt to connect to the event servers 5 times before rolling over to single server mode. If you add a second server after completing the installation process. 5 (which is set only if you initially install dual severs). such as the default setting of 50. 15–16 User Guide . the event processor attempts to connect to the event servers 5 times. or before rolling over to single server mode. DB Event Reconnect contains two values. it assumes there is a connection or configuration problem. see Event Server Rollover Recovery in the chapter “Maintaining. the event processor will attempt to reconnect to the remaining event server 50 times before shutting down. In dual server mode.Event Servers Database Rollover Has Occurred The Database Rollover Has Occurred check box is checked when there has been a rollover from dual server mode to single server mode. This setting specifies that the event processor should attempt to connect to the event server 50 times before shutting down. and will gracefully shutdown. The 50. In single server mode. That is. the DB Event Reconnect value is a number. For information on how to re-enable dual server mode. the event processor attempts to reconnect 50 times both on startup and when there is a connection problem.” in this guide. with a default setting of 50. and using only the remaining event server. you must set the DB Event Reconnect value appropriately. Once Unicenter AutoSys JM is in single server mode.

and if an event server is in an unknown state.Event Servers Database Wait Time UNIX parameter: DBLibWaitTime The Database Wait Time parameter indicates the amount of time the event processor waits before it breaks a connection with an event server that is in an unknown state. Administrator 15–17 . That is. Because it can cause the event processor to hang. Unicenter AutoSys JM will attempt to reconnect to the database a specified number of times. it probably indicates some kind of machine or event server contention problem. Typically. the event processor breaks the connection after the indicated time. the database should never time out. In other words. it means that no time-out value is to be applied. the event processor maintains and checks its connections with the databases. Database Alarm Reconnect UNIX parameter: DBAlarmReconnect Specifies the number of times that the event server should try to reconnect to the alarm server (if installed). However. Note: If you set this value to 0. If you see the database connections timing out at a frequent rate. using the value of 0 is not recommended. if it does. there are infinite connections.

see Shadow Event Processor in the chapter “Introduction. These actions include starting or stopping jobs. This second processor must run on a separate machine. see Installing a Shadow Event Processor in the chapter “Advanced Configurations. running as a Windows service. As a safeguard. the event processor first determines what actions are to be taken. checking for resources. Note: Shadow event processors and dual-event servers are independent features. and it will take over if the primary event processor fails. it checks whether the event satisfies the starting conditions for any job in the database. you can configure Unicenter AutoSys JM with a second event processor.” in the Unicenter AutoSys Job Management for Windows Installation Guide. The event processor is a Windows service you must start that continually scans the database for events to be processed. The event processor is the program.Event Processors Event Processors The event processor interprets and processes all the events it reads from the database. but they do not have to.” in the Unicenter AutoSys Job Management for Windows Installation Guide. 15–18 User Guide . called the shadow event processor. For information on installing dual-event servers. Usually they run together. Based on this information. which actually controls Unicenter AutoSys JM—it schedules and starts jobs. then instructs the appropriate remote agent process to perform the actions. For information on running a shadow event processor. monitoring existing jobs. When it finds one. and initiating corrective procedures.

or: ■ Click on the Event Processor button on the toolbar. Administrator 15–19 .Event Processors Administrator Event Processor Screen The Event Processor screen (see the following illustration) contains the event processor-specific configuration parameters. including the parameters necessary for setting up a shadow event processor and the values used in calculating the wait time between job restart attempts To move to the Event Processor screen: Do one of the following: ■ Select Event Processor from the AutoSys menu. you must have Windows Administrators group privileges. Note: To modify the settings on this screen.

Event Processors Defining Event Processor Configuration Parameters This section lists and describes the configuration parameters located on the Event Processor screen. For Example: Running a dual CPU machine would give you an EP Count of 2. either Windows or UNIX. Note: Both the primary and the shadow event processor machines require valid server licenses. Note: The number of Event Processors you elect should be equal to the number of processors available on the hardware Unicenter AutoSys JM is installed on. it must be run on a different machine than the one on which the event processor is running. both the shadow machine and the primary event processor must be installed on the same type of machine. EP Count The EP Count parameter specifies the number of concurrent Event Processors the user is able to run at one time (default is set to 1. However. WARNING! The event processor reads the settings in the Unicenter AutoSys Administrator on startup only. Shadow Machine The Shadow Machine parameter specifies the host name of the machine on which a shadow event processor runs. Therefore. if you make a change that you want implemented immediately. 15–20 User Guide . If the primary event processor fails. the shadow event processor takes over. you must stop the event processor using the sendevent -E STOP_DEMON command. The maximum number of Event Processors the can run at one time is 256.) Each Event Processor is able to retrieve an event out of the database and process it independently. If used. You must install an event processor and a remote agent on the shadow machine. then restart it using the Administrator Services screen (as described in the topic Using the Services Screen in this chapter). The shadow event processor is optional.

the third machine must be defined by the same AutoSys instance and installed on the same type of machine as the primary and shadow event processors are installed on. and it must have a valid client license. so that a new event processor is not started on a different machine. This list should contain all the possible machines on which an event processor may be started. Note: The third machine must have a remote agent installed on it. the third machine is used to resolve possible contentions between the two event processors. and to ensure that only one of the processors is running at any given time. the processor that is taking over connects to this third machine and creates a “dibs” file that will lock the other processor out. In addition. The machines in this list are checked both when the chk_auto_up command is run and when a new event processor is started. Before the shadow event processor takes over. Having a complete list of network machines is especially critical when a shadow event processor takeover occurs and your primary server is configured to automatically restart the event processor. either Windows or UNIX. The machines are checked to see if there are existing event processors running on them.Event Processors Third Machine UNIX parameter: ThirdMachine When running a shadow event processor. Administrator 15–21 . or if the primary event processor cannot signal the shadow event processor. Network Machine List UNIX parameter: EDMachines The Network Machine List parameter contains a comma-separated list of valid server machines on the network where event processors may have been started. or may be running.

bat batch file. The DBMaint. and replace all / characters with \ characters. the path to the log files directory is translated into the format expected by the recipient platform.bat batch file. it must exist and be “writable” on every machine running a remote agent. see the chapter “Maintaining. If you are using the Enterprise Wide Logging Directory. A UNIX remote agent removes the drive letter. In a cross-platform environment where a UNIX event processor starts a Windows remote agent (or vice versa).Event Processors Enterprise Wide Logging Directory UNIX parameter: AutoRemoteDir The Enterprise Wide Logging Directory parameter specifies the path and directory to which enterprise-wide event processor log output files should be written. the remote agent writes log files to its Local Agent Logging Directory instead. Upon installation.bat process cleans out old events and job_runs information using the archive_events command. For information on the Local Logging Directory. You can specify the time of day for this maintenance cycle in the Database Maintenance Time field of the Event Processor screen. A Windows remote agent will prepend the system drive letter and colon. /tmp becomes C:\tmp. Database Maintenance Command UNIX parameter: DBMaintCmd The Database Maintenance Command parameter specifies the location of the provided DBMaint. if present. For more information about the DBMaint. and send a DB_PROBLEM alarm if the amount of free space is insufficient. This command is run once a day.bat directory.” in this guide. and replace \ characters with / characters. For example. If specified. check for available free space. 15–22 User Guide . see the topic “Defining Remote Agent Configuration Parameters.” in this chapter. the DBMaint. It also uses the dbstatistics command to update statistics for the optimizer. For example.bat file is located in the %AUTOSYS%\bin\DBMaint. C:\tmp becomes /tmp. if no drive letter is present. However. you can override this setting at the remote agent level by setting the Local Agent Logging Directory on the Remote Agent screen.

Note: The default setting of the DB Poll Interval is set to . During this time.) If the Primary Event Processor detects one of the other Event Processors are down. You should schedule the maintenance command to run during a time of minimal activity. DB Poll Interval The DB poll Interval parameter specifies the time interval (in seconds) the Event Processor should retrieve events from the database. Each day at the time you specify. you do not need to set this parameter. EP Heartbeat Interval The EP Heartbeat Interval parameter specifies the time interval (in seconds) the Primary Event Processor (EP [1]) should use when checking the status of the other Event Processors (default is set to 10.5 seconds. Note: If you are not running multiple Event Processors. it will attempt to restart it. Shadow Ping Delay The Shadow Ping Delay parameter specifies how often the Shadow machine should ping the Primary Event Server Machine (in seconds. Administrator 15–23 .) Note: The default setting of the Shadow Ping Delay is set to 60 seconds. and we highly recommend that you configure your system to backup the database during this maintenance cycle. and it waits for the maintenance activities to complete before resuming normal operations. the event processor goes into a database maintenance cycle. it does not process any events.Event Processors Database Maintenance Time UNIX parameter: DBMaintTime The Database Maintenance Time parameter specifies the time of day that the database maintenance command is run.

When you change this number the new size does not affect until you start the event processor again. This -1 setting indicates that the remote agent should use the size set for the event processor (set in the Unicenter AutoSys Administrator for the event processor machine). The event processor reads this setting on startup and checks the file size. the event processor issues a warning in the event processor log file similar to the following: WARNING: The disk partition containing the EP log file is too full! WARNING: EP will shutdown if partition has less than 8192 bytes available! If the amount of disk space falls below 8 KB. If the file is the indicated maximum size. issuing messages similar to the following: ERROR: No disk space left to write Event Processor log EVENT: STOP_DEMON The Event STOP_DEMON has just been received. the event processor issues an EP_SHUTDOWN alarm and shuts down. File System Threshold UNIX parameter: FileSystemThreshold If the amount of available disk space falls below that specified by the File System Threshold setting. start the event processor. 15–24 User Guide . If you set the File System Threshold setting on a remote agent machine. We are going down! The default File System Threshold setting is 32 KB. Note: If you have an autosyslog process running on the file. the event processor will not start because it cannot delete the log file (because it has a lock on it). Valid settings must be less than 10 MB and greater than 8192 bytes. The default File System Threshold setting on remote agent machines is -1. the setting applies to the space available for the remote agent log file. the event processor deletes it. The event processor will read the new number only on the subsequent startup processes. and the file is its maximum size.Event Processors Maximum Log Size The Maximum Log Size parameter specifies the maximum size of the event processor log file.

when in dual-server mode. Valid settings must be less than 10 MB and greater than 8192 bytes. an event that is missing from one event server is copied over to the second server after this time-out delay. and the Number of Errors is 20. These two settings together guard against cascading event processor errors. By default. the Error Time Interval is 60 seconds. the remote agent issues a warning and stops writing to the remote agent log file. and change the setting to a number greater than -1. The primary reason for setting these parameters. To do this. Event Transfer Wait Time UNIX parameter: EvtTransferWaitTime The Event Transfer Wait Time parameter specifies the time-out delay for transferring events while in dual-server mode. Administrator 15–25 . Error Time Interval UNIX parameter: EDErrTimeInt The Error Time Interval parameter specifies the time interval that is used with the Number of Errors setting (see following) to determine if Unicenter AutoSys JM should shut down the event processor. That is. Unicenter AutoSys JM shuts down the event processor. These settings specify to shut the processor down if more than 20 errors occur within 60 seconds. and shutting the event processor down. the remote agent writes dots to the remote agent log file. If the specified number of errors occurs within the error time interval.Event Processors You can change the File System Threshold setting on any remote agent machine to override the event processor setting. This is implemented as a safety measure. If the amount of available disk space falls below that specified by the File System Threshold setting. but the remote agent service keeps running. You can set this to a different value on each remote agent machine. If the available space drops below 8 KB. which are caused by the event processor automatically reissuing failed directives. connect to the appropriate instance and machine. is to avoid starting any new processes while there are serious problems in the system. move to the event processor screen.

If you are not using this feature. the HEARTBEAT will be absent. the HEARTBEAT is a good indicator of the stability of the network. Therefore. Note: The reason that the event processor (not the remote agent) performs the checking is that if there is a problem between the remote agent and the event servers. Job HeartBeat Interval UNIX parameter: Check_Heartbeat The Job HeartBeat Interval parameter specifies the time interval (in minutes) that the event processor should use when checking for heartbeats. Heartbeats offer a method by which the continued progress of an application can be automatically monitored. Finally. and the Number of Errors is 20. Unicenter AutoSys JM shuts down the event processor as a safety measure. If the specified number of errors occurs within the error time interval. These settings specify to shut the processor down if more than 20 errors occur within 60 seconds. you do not need to set this parameter. A heartbeat is a signal sent from the application to the remote agent that started the application. User applications can be programmed to send heartbeats that are monitored by Unicenter AutoSys JM . the event processor checks that the HEARTBEAT event has occurred within the heartbeat interval specified for the instance.Event Processors Number Errors UNIX parameter: EDNumErrors The Number Errors parameter specifies the maximum number of errors that can happen within the Error Time Interval (see previous) when determining if Unicenter AutoSys JM should shut down the event processor. 15–26 User Guide . By default. the Error Time Interval is 60 seconds. That remote agent then sends a HEARTBEAT event to the Event Servers. and thus an alarm will be sent.

In addition.Event Processors Startjob Poll Interval The Startjob Poll Interval parameter controls how long the inetd waits between job starts on the same Remote Agent machine. the connection will be dropped. The default setting. If the value of this parameter is equal to one. then the event processor will connect to the other instance before every new event is sent. and only choice on Windows is vmstat (on UNIX. after the event has been sent. rstatd is also supported). you must ensure your machines processor is fast enough to handle starting jobs at a faster interval. This option is preferable when you use crossinstance job dependencies infrequently. The default setting is set to . then the event processor will connect to the other instance before the first event is sent and maintain the connection indefinitely.05 seconds. This method is used to achieve load balancing.” in the Unicenter AutoSys Job Management for UNIX User Guide. Administrator 15–27 . Note: Setting the Startjob Poll interval too low for your specific hardware could adversely affect performance. there will be frequent socket connection failures. If this parameter is set to zero. For information about rstatd. This option is preferable when you use cross-instance job dependencies intensively. XInstance DB Drop Time UNIX parameter: XInstanceDBDropTime The XInstance DB Drop Time parameter specifies how an instance will connect with a different instance when it has a job defined with a cross-instance job dependency. Machine Method UNIX parameter: MachineMethod The Machine Method parameter specifies the method Unicenter AutoSys JM will use to determine the percentage of CPU cycles available on a real machine belonging to a virtual machine. which will cause numerous job restarts. see the chapter “Configuring. Otherwise.

If the calculated Wait Time is greater than the specified value for the Max Restart Wait parameter. or failure of the file system space resource check. then WaitTime = MaxRestartWait The Num_of_Trys value is the value specified by the counter. The Restart Factor and Restart Constant parameters are described in this chapter. which is the interval in seconds that Unicenter AutoSys JM will wait before attempting to start a job again. which controls restarts when a job fails due to application failure (for example. then the Wait Time is set to the value of the Max Restart Wait parameter. It is different from the n_retrys job definition attribute. see n_retrys in the chapter “JIL/GUI Job Definitions. Max Restart Trys UNIX parameter: MaxRestartTrys The MaxRestartTrys parameter specifies the maximum number of times that Unicenter AutoSys JM will try to start a job. Note: This parameter governs retries that result because of system or network problems.Event Processors Max Restart Wait UNIX parameter: MaxRestartWait The MaxRestartWait parameter specifies the maximum amount of time (in seconds) Unicenter AutoSys JM will wait before it attempts to restart a job. or permissions are not properly set). Unicenter AutoSys JM is unable to find a file or a command. The following is the formula used for calculating the Wait Time: WaitTime=RestartConstant+(Num_of_Trys*RestartFactor) if WaitTime > MaxRestartWait. This value is used in calculating the Wait Time. For information on the n_retrys job definition attribute. Unicenter AutoSys JM may be unable to start a job due to system problems including machine unavailability. a timed-out socket connect. which indicates the number of times Unicenter AutoSys JM has already tried to start the job. 15–28 User Guide . an inability to create new processes.” in the Unicenter AutoSys Job Management Reference Guide.

By default Unicenter Events is set to 0. The formula used for calculating the Wait Time is described in the Max Restart Wait parameter. This value is used in calculating the Wait Time. If a list of signals is specified. this list is ignored and the job is simply terminated. with five-second sleeps between each call. If the job is running on a UNIX machine. Administrator 15–29 . 3–To log all events that are generated to the Event Console. previously discussed. Use of this option requires the Unicenter NSM Event Management component be installed locally on the machine where AutoSys is installed. 2–To log all Alarms and job completions. The Restart Constant parameter is described in this chapter. which is the interval in seconds that Unicenter AutoSys JM will wait before attempting to start a job again. The parameter values for Unicenter Events are as follows: ■ ■ ■ ■ 0–Reports no events to Unicenter (default setting) 1–To log all Alarms to the Event Console. Kill Signals UNIX parameter: KillSignals The Kill Signals parameter specifies a comma-separated list of signals to send to a job whenever the KILLJOB event is sent. Note: Any other value in the Unicenter Events field will be ignored. Restart Factor UNIX parameter: RestartFactor The Restart Factor parameter specifies a factor. the signals are sent in the order listed. the parameter specifies a single or commadelimited list of UNIX signals to be sent to the job. If the job to be killed is running on a Windows machine. and no messages will be sent to the Unicenter Event Management Console.Event Processors Unicenter Events The Unicenter Events parameter specifies what messages should be sent to the Unicenter Event Management Console.

and then. *. KILLJOB kills the process specified in the command definition.EXE process. Any processes that were launched by user applications or batch (*. Restart Constant UNIX parameter: RestartConstant The Restart Constant parameter specifies a constant value. The Job Status is then set according to the return code of the killed CMD.EXE to launch the job.cmd. If the job being run is not a *. FAILURE. The formula used for calculating the Wait Time is described in the Max Restart Wait parameter. KILLJOB kills only the CMD. Note: The KillSignals listed in the configuration file are overridden when issuing the sendevent command with the -k option.exe (for example. or *.bat. *. on “MaxRestartWait” MaxRestartWait.Event Processors Microsoft Windows does not support the concept of process groups.bat) files cannot be killed.com). 15–30 User Guide . AutoSys uses CMD.EXE process. or TERMINATED. and this status can be any one of the following: SUCCESS. which is the interval in seconds that Unicenter AutoSys JM will wait before attempting to start a job again. If the launched job is a *. This value is used in calculating the Wait Time.exe.

Then. Unicenter AutoSys JM removes the temporary log file upon the successful running a job. Clean Temporary Files UNIX parameter: CleanTmpFiles The Clean Temporary Files setting indicates whether the remote agent should remove its temporary log file upon successfully completing a job. when you start the event processor. the files remain in the directories until you run the clean_files process. This option allows you to manually start jobs in a controlled manner so that the system is not overloaded with job start events.” in this guide.” in the Unicenter AutoSys Job Management Reference Guide. see chase in the chapter “Commands. You can use the Scheduler Console screens to help you decide which jobs to start. If you check the Clean Temporary Files box. For every job that runs.Event Processors Event Processor Options Chase On Startup The Chase On Startup setting indicates whether the chase utility program should run when the event processor is started.” in this guide. the files remain in the directory for diagnostic purposes regardless of the setting. the remote agent. it is in global auto hold mode. see the chapter “Scheduler Console. For information on using the Scheduler Console. upon the successful completion of its tasks. You should turn on global auto hold when you are going to restart an event processor after a shutdown period. with either setting. Therefore. removes the C:\tmp\auto_rem* file (assuming the default C:\tmp Local Logging Directory is being used). you should run the clean_files process periodically to remove files from unsuccessful job completions. and to then start them. Administrator 15–31 . For information on the chase utility. The chase utility checks to see if jobs and remote agents are actually running. For more information about Global Auto Hold. By doing this. Global Auto Hold The Global Auto Hold setting indicates whether global auto hold mode is on or off. If a job is not successful. see Starting the Event Processor in the chapter “Maintaining . a file is created in the remote agent log directory. If you deselect the Clean Temporary Files box. and you have time to evaluate all jobs whose starting conditions have passed and are thus eligible to run.

Since job profiles are defined differently on Windows. Unicenter AutoSys JM checks the following (in this order): 1. and does not check other settings.” in the Unicenter AutoSys Job Management for UNIX User Guide. If there is a notation.profile file is sourced. see RemoteProFiles in the chapter “Configuring. To set the behavior at the job definition level. then the files are overwritten. or in the File to redirect standard output and File to redirect standard error fields on the Job Editor Command Info tab. Checks the AutoSys job definition for append or overwrite notation. Unicenter AutoSys JM uses the indicated behavior. Append stdout/stderr UNIX parameter: AutoInstWideAppend The Append stdout/stderr setting specifies whether the instance will overwrite or append information to the standard output and standard error files. the new output and error information is appended to the files When determining its behavior. If this check box is selected. no profile related standard error and output information is generated. which is the default behavior. place the appropriate notation as the first characters in the std_err_file or std_out_file specification in JIL. If this check box is not selected. Therefore.Event Processors Remote Profile Logging UNIX parameter: RemoteProFiles The Remote Profile Logging setting indicates whether the event processor should redirect to the auto. this parameter applies only to jobs that the event processor is sending to run on a UNIX machine.rem* log file all standard error and standard output information that is generated when the UNIX /etc/auto. Use the following notation to specify whether the files should be appended to or overwritten: > >> Overwrite file Append file 15–32 User Guide . For information on how remote profile logging is handled on UNIX machines.

the primary event processor will try to automatically restart any of the secondary event processors should it go down. Administrator 15–33 . Note: This option is only available when running multiple event processors. and does not check other settings. Checks the Append stdout/stderr setting. If the Event Serialization option is not selected. It is possible to experience database deadlocks without running the event serialization option. which you can set in the Unicenter AutoSys Administrator System Information screen (see the topic. The primary event processor will not be restarted. Multiple EP Restart When the Multiple EP Restart option is checked. Checks the AutoMachWideAppend variable setting. the process that received the deadlock condition will retry.)” If this variable is set for the specific machine. For UNIX. Unicenter AutoSys JM uses the indicated behavior. the default event processor behavior is to append this file. Note: This option is only available when running multiple event processors. “AutoMachWideAppend. and uses this setting. preventing deadlock conditions between multiple event processors. multiple Event Processors will be able to retrieve events from the database without serialization. Note: If you are running jobs across platforms. 3. If this condition occurs. the event processor of the issuing instance controls the default behavior. should it go down.Event Processors 2. Event Serialization This Event Serialization setting only allows one event processor to retrieve an event from the database at a given time.

the event processor will not send jobs to Unicenter AutoSys Agents. the event processor can send jobs to Unicenter AutoSys Agent machines. For information on Unicenter AutoSys JM Connect and Unicenter AutoSys Agent support. “Integrating with the Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS. If the check box is not checked (the default setting. Receive Remote Job Submissions The Remote Job Submissions setting specifies whether or not an instance can receive job submissions from a mainframe or a Unicenter Manager. When this option is selected. 15–34 User Guide . see Appendix a. that Broker will start the asbIIIsr1 process. which is responsible for processing remote job submissions.) the Instance will not be able to receive jobs. Note: This option is only effective upon the initialization of the Event Processor/Broker.Event Processors Broker Options AutoSys Agent Support UNIX parameter: AutoSysAgentSupport The Unicenter AutoSys Agent Support setting indicates whether an instance can start jobs on Unicenter AutoSys Agent machines. If the Unicenter AutoSys Agent Support check box is checked on. If the check box is not checked (the default setting).” in this guide.

Administrator 15–35 . That is. You can configure Unicenter AutoSys JM to call user-defined routines for the following types of system alarms: ■ ■ ■ ■ ■ Database Rollover Database Problem Event Processor Rollover Event Processor Shutdown Event Processor High Availability To specify that Unicenter AutoSys JM should invoke a user-defined callback for one of these alarms. For example. your administrator can be notified as soon as certain events occur. you can configure Unicenter AutoSys JM to call userdefined routines that communicate the problem to specific members of your company.Notification Mechanism Notification Mechanism The notification mechanism provides a method for communicating problems to administrators in a manner that is external to the event system. for certain types of alarms. enter the path and executable name in the appropriate field on the Unicenter AutoSys Administrator Notifications screen. by using electronic mail or a command line pager utility.

or: ■ Click the Notifications button on the toolbar. Note: To modify the settings on this screen. 15–36 User Guide . For the Notification mechanism to work. you can enter the path and executable name to the userdefined routines that you want associated with the events. the specified executable file must exist in the specified path.Notification Mechanism Administrator Notifications Screen Using the Unicenter AutoSys Administrator Notifications screen (see the following illustration). you must have Windows Administrators group privileges. To move to the Notifications screen: Do one of the following: ■ Select Notifications from the AutoSys menu.

Database Rollover UNIX parameter: DB_ROLLOVER The Database Rollover parameter specifies the user-defined routine that Unicenter AutoSys JM should call when it has rolled over from dual server mode to single server mode. Administrator 15–37 .Notification Mechanism Notification Example If you want Unicenter AutoSys JM to call the program C:\utils\pager. You must code pager to accept these parameters. if the event processor shuts down. Defining Notifications Configuration Parameters This section lists and describes the configuration parameters located on the Notifications screen. Database Problem UNIX parameter: DB_PROBLEM The Database Problem parameter specifies the user-defined routine that Unicenter AutoSys JM should call when there is a problem with one of the AutoSys databases. you must enter the complete path and executable name in the appropriate field. Event Processor Shutdown UNIX parameter: EP_SHUTDOW The Event Processor Shutdown parameter specifies the user-defined routine that Unicenter AutoSys JM should call when the event processor is shutting down.bat Then. either as a result of a normal shutdown process or as a result of an error condition. Unicenter AutoSys JM will pass pager a numeric code and a text message. you would enter the following in the Event Processor Shutdown field: C:\utils\pager.bat when the event processor shuts down. When specifying a user-defined routine. Event Processor Rollover UNIX parameter: EP_ROLLOVER The Event Processor Rollover parameter specifies the user-defined routine that Unicenter AutoSys JM should call when the shadow event processor is taking over processing.

the database often has associated environment variables and configuration files. In addition. System Information Access to Unicenter AutoSys JM software is controlled by three environment variables and the Windows Registry settings that you enter through the Unicenter AutoSys Administrator. these variables are set when you run the Unicenter AutoSys JM software. For Unicenter AutoSys JM to work properly. variables are set both at the Windows system level and at the Unicenter AutoSys JM level.System Information Event Processor High Availability UNIX parameter: EP_HIGH_AVAIL The Event Processor High Availability parameter specifies the user-defined routine that AutoSys should call when the event processor is shutting down. This occurs when the shadow event processor cannot reach the third machine to determine the availability of the primary event processor. Note: The environment variables for the AutoSys database are set at the Windows system level. or when there are other types of event processor takeover problems. all of these variables and files must be present in each working environment. The Unicenter AutoSys Administrator System Information screen displays the variables that are set at the Unicenter AutoSys JM level. 15–38 User Guide . During the installation procedures. You can modify and add to these standard environment variables.

you should be very careful if you decide to do so. the System Information screen provides Version and Build information on the Unicenter AutoSys JM that you are running.System Information Administrator System Information Screen Using the Unicenter AutoSys Administrator System Information screen you can view and modify the settings of environment variables that are necessary. To move to the System Information screen: Do one of the following: ■ Select System Information from the AutoSys menu. In addition. while you can modify these standard System settings. or: ■ Click the System Information button on the toolbar. That is. This information is supplied primarily for informational purposes. The Administrator System Information screen reflects the information that Unicenter AutoSys JM is using. Administrator 15–39 .

AUTOSYS UNIX parameter: $AUTOSYS The %AUTOSYS% environment variable specifies the full path to the software directory. Then. 2. 3. For information on ISDBGACTIV see the Appendix “General Debugging” in this guide. 2. In addition to the default environment variable settings. Note: The variables that appear on this screen are set when you open an AutoSys instance command prompt window. You can set this to control output and error writing behavior on a machine-specific basis.System Information Using the System Information Screen ■ To add an environment variable: Enter a Variable and Value. ■ To modify an existing environment variable: 1. Modify the Variable or Value. These are the environment variables that are set in the instance command prompt windows. System Information Configuration Parameters This section lists and describes the specific variable settings that are located on the System Information screen by default. or both. ■ To delete an environment variable: 1. Double-click on the Environment Variable in the list that you want to delete. and click Set. Click Delete. Double-click on the Environment Variable in the list that you want to modify. you must have Windows Administrators group privileges. and click Apply or OK. the System Information screen includes the AutoMachWideAppend variable. AUTOROOT UNIX parameter: $AUTOROOT 15–40 User Guide . Click Set. and click Apply or OK. click Apply or OK. Note: To modify the settings on this screen.

the instance ID is ACE. which holds the user external configurations file (the config.” in the Unicenter AutoSys Job Management for Windows Installation Guide.EXTERNAL file).System Information The %AUTOROOT% environment variable specifies the top-level directory. but you can specify another name during the installation process.EXTERNAL file. By default. see the Configuring Cross-instance Job Dependencies section in the chapter “Advanced Configurations. For more information about AutoSys instances. If you are using an Oracle or Microsoft SQL Server database. Administrator 15–41 . the event processor output files. You cannot change this variable using the Unicenter AutoSys Administrator. AUTOUSER UNIX parameter: $AUTOUSER The %AUTOUSER% environment variable specifies the full path to the directory containing the user’s directory. this field is not displayed. and the archive output files generated during database maintenance. For more information about the config. DSQUERY The %DSQUERY% environment variable specifies the name of the Sybase event server. The default setting is AUTOSYSDB.” in this chapter. AUTOSERV UNIX parameter: $AUTOSERV The %AUTOSERV% environment variable specifies the instance ID. To change the instance ID. The instance ID is the capitalized three-letter name that identifies a specific server installation on a particular machine. you must uninstall Unicenter AutoSys JM. and reinstall it using the new ID. see the topic “Instances.

Version The Version field indicates the Unicenter AutoSys JM for Windows version number (for information purposes only). the behavior set by the “Append stdout/stderr” global configuration parameter is used. at the machine level. the log files are appended. The Build field indicates the Unicenter AutoSys JM for Windows build number. it is for informational purposes only.profile file. which is set in the Unicenter AutoSys Administrator Event Processor screen (see “Append stdout/stderr” AutoInstWideAppend). Using this variable. the “Append stdout/stderr” configuration parameter. If you set this variable to yes. Build 15–42 User Guide . If you do not set this variable.System Information AutoMachWide Append You can set the %AutoMachWideAppend% variable to override. the log files are replaced. This field is read-only. you can set up each client machine to override global behavior. Note: On UNIX. If you set it to no. the AutoMachWideAppend parameter is located in the /etc/auto.

Unicenter AutoSys JM uses the defined sounds to announce the events as they occur. you can associate sounds with specific events. you can turn sound on and off as well as specify the sounds you want played for specific events. In addition. see the chapter “Monitoring and Reporting on Jobs. you can record new sounds with the Windows Sound Recorder in the Accessories program group. Administrator Sounds Screen Using the Unicenter AutoSys Administrator Sounds screen (see the following illustration).Sounds Sounds If you have a Monitor/Browser Editor running on a Windows system that supports sound. You can use the Administrator Sounds screen to turn sound on and off as well as specify the sounds you want played for specific events.” in this guide.wav file that you want played for that event. Then. see your Windows documentation. In each Sounds field. once you have enabled and defined these sounds. Administrator 15–43 . For instructions on how to record sounds. or: ■ Click on the Sounds button on the toolbar. such as alarms or job success and failure. For information on the Monitor/Browser Editor. you can specify the *. To move to the Sounds screen: Do one of the following: ■ Select Sounds from the AutoSys menu. Note: All sounds also can be managed using the Sound option of the Windows Control Panel.

Big Alarm. AutoSys Default 15–44 User Guide . Alarm. If you log on as a different user. An AutoSys Big Alarm announces an event that is not a job CHANGE_STATUS event.Sounds Note: Changes you make to the sound settings are saved for the current. logged on Windows user. Defining Sounds Configuration Parameters This section lists and describes the configuration parameters located on the Sounds screen. but still returns a FAILURE or TERMINATED status. see the Alarms section in the chapter “System States. AutoSys Alarm The AutoSys Alarm setting specifies the location of the *. these modified settings will not be in effect.wav file that is played for AutoSys Alarm events. Success. The AutoSys Default setting specifies the location of the *. For a list of Alarms. and Failure).wav file that is played for the AutoSys Big Alarm.” in the Unicenter AutoSys Job Management Reference Guide. AutoSys Big Alarm The AutoSys Big Alarm setting specifies the location of the *.wav file that is played for all events that do not fit in the other Sounds categories (that is.

or when the failure conditions for a box job evaluated to TRUE. based on the exit code for a command job or the success conditions for a box job. The AutoSys Failure setting specifies the location of the *. A FAILURE event occurs when a job exits and AutoSys considers it a failure.Sounds AutoSys Success The AutoSys Success setting specifies the location of the *.wav file that is played for an AutoSys job SUCCESS event. A SUCCESS event occurs when a job exits and AutoSys considers it successful. AutoSys Failure Administrator 15–45 .wav file that is played for an AutoSys job FAILURE status event. A job is considered a failure when the exit code for a command job is greater than the maximum success value specified for the job.

” For information on using autosys_secure to turn on remote authentication. The Unicenter AutoSys Administrator Security screen allows you to define the Trusted Hosts and Trusted Users for User remote authentication. By default. The Security screen allows you specify Trusted Hosts and Users. For information about specifying authorized event processors. which are used when remote authentication is turned on. the remote agent will check the Trusted Hosts and Trusted Users lists to see if the job request is coming from an authorized host or user. If user remote authentication is turned on. the remote agent will verify that the requesting event processor is on the list of authorized event processor host names. For information on other types of security features.Security Security Unicenter AutoSys JM supplies you with several security features. but you can turn them on using the autosys_secure command.” in the Unicenter AutoSys Job Management Reference Guide. and you can turn it on using the autosys_secure utility. both types of remote authentication are turned off. There are two types of remote authentication: ■ ■ Event processor authentication user authentication You can configure your remote agents so they verify access permission for event processors and for users. see the chapter “Security. 15–46 User Guide . see Defining Remote Agent Configuration Parameters in this chapter. One of these features is remote authentication. If event processor remote authentication is on. Remote authentication supplies additional security measures. see autosys_secure in the chapter “Commands. which is specified on the Unicenter AutoSys Administrator Remote Agent screen.

remote agent user authentication is required. Therefore. If the first log on does not work. However. If this logon is successful. ■ 3. To log on to a machine to run a job: 1. the job is started. The event processor tries to log on as the user@host_or_domain specified by the owner job attribute. The edit superuser can enter and modify passwords using the autosys_secure command. Note: In addition to checking the permissions of these various users. If the host_or_domain specified in the owner attribute is on the Trusted Hosts list. the remote agent does not start the job and issues an error. the remote agent tries to log on as the user owner at the machine on which the job is to be run (the host name specified by the machine job attribute). the remote agent attempts to log on as this user (user@host) by using the database password entered for that user. the remote agent checks for one of the following two things (in this order. since the job owner is now different from the user that is trying to log on. If this logon succeeds. Otherwise. using the password that the event processor has passed with that owner value. the job is started. The remote agent uses the password that the event processor has passed to it for this user. using the user@host format. If the user@host_or_domain specified by the owner attribute is on the Trusted Users list. If one of these conditions is met. the remote agent makes sure that the Windows user has a valid ID and password entered in the database.Security User Remote Authentication Example With user remote authentication turned on. the remote agent follows this procedure when trying to log on to a machine to run a job. Administrator 15–47 . and only one condition must be met): ■ 2. and any user that knows an existing user ID and password can change the password or delete the user and password using the autosys_secure command.

Administrator Security Screen Using the Unicenter AutoSys Administrator Security screen (see the following illustration). and you must have Windows Administrators group privileges. see Examples of Security on Windows in the chapter “Security. or: ■ Click on the Security button on the toolbar.” For information on entering your Windows user IDs and passwords. Note: To modify the Trusted Host setting. you can specify the Trusted Hosts and Trusted Users lists (which are only used when remote authentication is turned on. see autosys_secure in the chapter “Commands. see the chapter “Adding the Superusers and the Windows User IDs and Passwords. For information on autosys_secure and turning on remote authentication. To move to the Security screen: Do one of the following: ■ Select Security from the AutoSys menu. 15–48 User Guide . you must be the edit superuser.Security For more examples of security on Windows. using the autosys_secure utility).” of the Unicenter AutoSys Job Management Reference Guide.” in the Unicenter AutoSys Job Management for Windows Installation Guide.

As the current. logged on Windows user. Exercise caution when modifying this list. Administrator 15–49 . Trusted Users permissions are owned and administered by individual users on client machines. Trusted Hosts The Trusted Hosts list defines the machine host names or domain names that are allowed to log on to the client machine to run jobs. and they are saved under your specific user ID only. since any user on a designated Trusted Host host_or_domain is granted logon access. Trusted Users The Trusted Users list is a group of user@host_or_domain entries that define who can log on and run jobs on the defining client machine.Security Defining Security Configuration Parameters This section lists and describes the configuration parameters located on the Security screen. You must be the edit superuser to modify the Trusted Hosts settings. Use the Add Host and Remove Host buttons to enter or remove the host name in the top field of the Trusted Hosts list. and thus can run jobs on the client machine. Use the Add User and Remove User buttons to enter or remove the user names in the top field of the Trusted Users list. all users listed as Trusted Users are allowed to log on to the defining client machine. Then. as long as they have a valid user ID and password in the database. you can make changes to the Trusted Users settings. All users can define their own set of Trusted Users on their own machines.

Other users can only view the status of these services. When you are ready to start the event processor again. users with Windows Administrators group privileges can start and stop the Remote Agent service. you can do so from the Services screen. and start the Event Processor service. you must be the exec superuser. 15–50 User Guide . Administrator Services Screen Using the Unicenter AutoSys Administrator Services screen (see the following illustration). or services: ■ ■ Remote Agent Event Processor The Services screen allows to you check the statuses of Services associated with the instance that you selected in the Instance screen.Services Services Unicenter AutoSys JM has the following primary components. To stop the event processor. Note: You cannot stop the Event Processor service from this screen. and you must execute the sendevent -E STOP_DEMON command at an instance command prompt.

you must have Windows Administrators group privileges. Administrator 15–51 . or: ■ Click on the Services button on the toolbar.Services To move to the Services screen: Do one of the following: ■ Select Services from the AutoSys menu. Note: To modify the settings on this screen.

Services Services Screen Components This section lists and describes the components of the Services screen. You can select a Service from the drop-down list. and then you can view and change the Status of the Service. “Updating. This value can be “Stopped”. A red light indicates that the service is Stopped. a yellow light indicates that the service is Updating or Pausing. The field below the traffic light also indicates the status of the selected Service— it corresponds to the traffic light. you can click it to start the selected Service. and a green light indicates that the service is Running. See the note in the next section.) Stop Service 15–52 User Guide .” or “Running.” Status Start Service If the Start Service button is enabled. you can click it to stop the selected Remote Agent service. The Status traffic light and the field below indicate the status of the selected Service. Service The Service drop-down list shows the Services that are installed on the selected instance. If the Stop Service button is enabled. (The Event Processor service cannot be stopped from this screen. The traffic light indicates the status of the selected Service.

■ To stop the Remote Agent: Select the Remote Agent service from the Service drop-down list and click Stop Service.Services Using the Services Screen Using the Unicenter AutoSys Administrator Services screen. and you must execute the sendevent -E STOP_DEMON command at an instance command prompt. To stop the event processor. and start the Event Processor service ■ To start the Remote Agent: Select the Remote Agent service from the Service drop-down list and click Start Service. Administrator 15–53 . you must be the exec superuser. Note: You cannot stop the Event Processor Service from this screen. users with Windows Administrators group privileges can start and stop the Remote Agent service. When you are ready to start the event processor again. you can do so from the Services screen. ■ To start the Event Processor: Select the Event Processor service from the Service drop-down list and click Start Service.

rather than with the individual components themselves. and how to resolve them. Troubleshooting 16–1 .Chapter 16 Troubleshooting Problems with Unicenter AutoSys JM usually involve the interactions between the major components. This chapter presents a number of common problems. their symptoms. It provides very useful information about troubleshooting the primary components.

After the job completes. the event processor initiates a remote agent on the client machine to execute the job. and remote agent machines.2 or higher) or Microsoft SQL Server client utilities on each event processor and remote agent machine. event server. and the following occurs: ■ When its starting conditions are met. you must install the appropriate.Introduction Introduction To troubleshoot Unicenter AutoSys JM more effectively. the order in which they occur. 16–2 User Guide . event processor. it is not run again until its starting conditions are met. database-specific Oracle Client Products (specifically SQL*Net Release 2. ■ ■ This is the basic cycle for all jobs. event processor. The remote agent runs the job and sends the exit status of the job back to the event server. its starting conditions are saved to the event server (database). When a job is defined. and remote agent). it is essential that you understand the stages in the life of a job. and the roles played by the three major components (that is. and you must ensure that you have database connectivity between the event server. Note: If you are using an Oracle or a Microsoft SQL Server database as your event server.

verify the status of the MSSQLServer service. follow the instructions in the appendix “Removing Unicenter AutoSys JM 3. verify that the status of SYBSQL_LOCAL is “started. If you are running a Microsoft SQL Server. often the best approach. In these cases.” If you are running unbundled Sybase. Troubleshooting 16–3 . To verify that the Event Server service (the database service) is started. to remove the existing AutoSys installation and reinstall it. and OracleTNSListener.” in this guide. indicate that the software was not successfully installed. You can find details as to why the service did not start in the Windows Event Viewer in the Administrative Tools program group. look at the Windows Control Panel’s Services dialog. For information on starting services with the Administrator. the service will have a different name. or Microsoft SQL Server service) from the Windows Control Panel’s Services dialog. OracleStart*. Oracle.4. using the Administrator Services screen. Typically. Note: To remove AutoSys. For bundled Sybase. and you can start the event server (the Sybase.” in the Unicenter AutoSys Job Management for Windows Installation Guide. see Services in the chapter “Administrator.Windows Services Troubleshooting Windows Services Troubleshooting You can start the event processor and remote agents from the Administrator Services screen. If you are running an Oracle database. verify the status of the following services (substitute your Oracle SID for the asterisk): OracleService*. problems with starting services.

verify that the database services have been started. If you are running with an unbundled Sybase database. Or. In addition. you can check the status of the database using the Services dialog in the Windows Control Panel on that machine. If you have installed the bundled Sybase database on a Windows machine. you can use the Windows Services dialog to start the Sybase Service. Resolution You are unable to insert keys with gatekeeper. 16–4 User Guide . then xql will fail. When trying to start xql.Event Server Troubleshooting Event Server Troubleshooting Event Server Is Down (Sybase) Symptoms 1. if your database resides on a UNIX platform. When running programs like autorep or autosc. or the process in question is unable to access it. The system DSQUERY environment variable points to the name of the data server (typically AUTOSYSDB). When you run chk_auto_up. you get a message like: DB-Library error: dbproc NULL Error in SybInit: dbopen failed 2. This indicates that either the data server is down. If it is not set properly and you are not specifying a data server name to xql (using the -S server option). If the database service is running. you receive a message similar to the following: Couldn’t connect with Server: AUTOSYS:autosys 4. verify that the processes for your database are running. The name of the bundled Sybase Service is SYBSQL_LOCAL. log onto the server machine and run the chk_auto_up utility. the problem could be that you are pointing to the wrong data server. you get a message like: Client ERROR: Net-Lib protocol driver call to connect to two end points failed. 3. To confirm that the data server is down.

INI file might not have the proper form. For information on using the Unicenter AutoSys Administrator. The data server detects the situation and chooses the user whose process has accumulated the least amount of CPU time as the “victim. and allows the other user’s processes to move forward. but the second user will not let go until the lock on the first user’s object is freed. see the chapter “Introduction. notifies the application with the above error message. This file is located in %SYBASE%\INI. Resolution A deadlock is a Sybase condition that occurs when two users have a lock on separate objects. or be in the proper location. This typically occurs on servers if the environment has been changed.log): Your server command (process id #11) was deadlocked with another process and has been chosen as deadlock victim. The DSQUERY field is located on the Administrator System Information screen.INI file has not been correctly installed. then the Sybase SQL.Event Server Troubleshooting You can view and modify the setting of the DSQUERY environment variable using the Unicenter AutoSys Administrator. Re-run your command. If the database service is up.INI file and connecting to databases.” in this guide. Troubleshooting 16–5 . sendevent will try to rerun the command until it is successful or until it reaches the maximum number of tries specified by the -M option. on clients. and they each want to acquire an additional lock on the other user’s object. if the SQL. and the environment variable is set properly.” in the Unicenter AutoSys Job Management for Windows Installation Guide.” The data server rolls back the victim’s transaction. see the chapter “Administrator.instance\sql10\log\sqlsrvr. The first user is waiting for the second user to let go of the lock. For more information about the Sybase SQL. Sybase Deadlock Symptom A message similar to the following appears in the event processor log when viewed with the autosyslog -e command or in the Sybase error log (Autosys. which you can open from the program group. or.

rows affected 1 4. rows affected 1 3. Results similar to the following are displayed: -------------3 return status 0. Results similar to the following are displayed: ------------253 return status 0. they cannot start the GUI or send events.Event Server Troubleshooting Not Enough User Connections (Bundled Sybase) Symptoms Users cannot make connections to the database. Results similar to the following are displayed: -------------0 return status 0. 2. Enter: 1> select count(*) from master. To determine the maximum number of user connections you can set for your system: 1. rows affected 1 16–6 User Guide . Log into the database as the “sa.sysdevices where cntrltype = 0.instance\sql10\log\sqlsrvr.” At the isql or xql prompt. By default. but first you must determine the maximum number of user connections your system can support. Enter: 1> select count(*) from master.log) you see one or both of the following errors: Not enough User Connections (Sybase error 1601) No Pss structures available for new process Resolution These messages occur because there are more users who want to run jobs simultaneously than there are user connections. there are not enough connections available to the database.sysdevices where mirrorname is not NULL. When you check the Sybase error log (Autosys.. the bundled Sybase installation of Unicenter AutoSys JM has a limit of 25 user connections.. You can increase the number of user connections. enter: 1> select @@max_connections.

To increase the number of user connections:: 1.sysservers where srvname != @@servername. Results similar to the following are displayed: -------------1 return status 0. number. the database will be unusable. To return the database to working order. you might not be able to rerun sp_configure to lower the number of user connections. Stop and restart the event server. rows affected 1 The maximum number of user connections that you can set is @@max_connections minus the sum of the results of the last three queries. Troubleshooting 16–7 . Changes will not take effect until you stop and restart the event server. the maximum number of user connections is 249.. Enter: 1> select count(*) from master. WARNING! If you set the number of user connections too high. where: number Is the number of user connections you want. At this point. At the isql or xql prompt.Event Server Troubleshooting 5. 2. In the example results to the above queries. you must run buildmaster or recover the database from backups. enter the following command to specify the number of user connections you want: 1> sp_configure “user connections”.

archive_events fails. ideally as part of the daily database maintenance cycle by using DBMaint or as a regularly scheduled job. 1> exit Resolution To resolve the full transaction log problem: 1.log on chkpt is not set. use that one instead of sysadmin): xql -Usa -Psysadmin 2. This usually occurs because archive_events is not run regularly. To have Sybase truncate the transaction log: 1. Log into the database server as the “sa” by entering the following command (if you changed the “sa” password. 16–8 User Guide . enter the following commands: 1> sp_helpdb. To check if the truncate option is set. use that one instead of sysadmin): xql -Usa -Psysadmin 2. If trunc. 4. log on chkpt. Use the autosys database by entering the following command: 1> use autosys. You can usually avoid a full transaction log by having Sybase truncate the transaction log during regular checkpoints. 3. Dump the transaction log by entering the following command: 1> dump transaction autosys with no_log. true. “trunc log on chkpt”. We highly recommend that you run archive_events frequently. or: 1> sp_dboption autosys. enter one of the following commands depending on your version of Sybase: 1> sp_dboption autosys. “trunc. 3. Log into the database server as the “sa” by entering the following command (if you changed the “sa” password. true.Event Server Troubleshooting archive_events Fails (Bundled Sybase) Symptom When the transaction log is full.”. Enter the following commands: 1> checkpoint.

Troubleshooting 16–9 . OEXN (34) event: GRO0000mct02 Could NOT be marked as processed. Repeat Step 4 and each time increase the row count incrementally. If this fails at any time.%AUTOSERV% To view this file. restart your event processor. For example: archive_events -n 30 archive_events -n 10 Event Server Unable to Extend Tablespace (Oracle) Symptom While running.EVENT_STATE".. 5. Event Processor Troubleshooting Output from the event processor is redirected into the following log file: %AUTOUSER%\out\event_demon. and then run archive_events. issue the autosyslog -e command in an instance command prompt (which you open from the program group). . When the row count is large. 1> dump transaction autosys with no_log.EVENT_GET1 by 512 in tablespace AUTOIN-06512: at "AUTOSYS. Resolution Ask your database administrator to increase the size of the tablespace in your Oracle database.ORACLE error -01654: unable to extend index AUTOSYS. and then the event processor shuts down: -. line 34-06512: at line 1 OCI function OEXEC. decrease the row count and try again. To begin with try doubling the number. Begin with a large number of days and work down until you reach your target number of days. log out of the data server. You can terminate this reporting at any time by pressing Control+C.. Log out of the data server. reports an error similar to the following. This command displays the event processor’s log file and shows each job-related event as it occurs. Then.Event Processor Troubleshooting 4. If this fails. This error indicates that the Oracle tablespace it too small. enter the following commands: 1> set rowcount 1.

Resolution Confirm that the event processor is down by performing one of the following actions: ■ ■ ■ Run the chk_auto_up utility. select the Event Processor from the Service drop-down list. on the Services screen. Look at the Unicenter AutoSys Administrator Services screen. use the Unicenter AutoSys Administrator Services screen to start the event processor. it returns a message similar to this (assuming your event processor was installed on the machine “EPhost”:) Checking machine: EPhost No Event Processor is running on machine: EPhost. Jobs do not start. Event Processor Will Not Start Symptom 16–10 User Guide . Event Processor Is Down Symptoms 1.) For information on the Unicenter AutoSys Administrator. and the traffic light icon should turn green. in the order it was done. To do so. Network problems are usually reflected in this file as well. 8. The event processor log should register date and timestamps every minute. On the screen. and then click the Start Service button. When chk_auto_up is run. The event processor log viewed with the autosyslog -e command has not registered a date and timestamp for a period of time. Execute an autosyslog -e command and check for date stamps.” in this guide. and check the Status “traffic light” icon and field. (The Status field should change to Running.Event Processor Troubleshooting Everything that the event processor does. This file is very useful for reconstructing what happened when a problem occurs. 2. see the chapter “Administrator. select the event processor from the Service drop-down list. If the event processor is indeed down. is in this file.

The event processor service does not remain running or never starts. 2.” in the Unicenter AutoSys Job Management for Windows Installation Guide. and restart the event processor. view it by entering the following command: type EVENT_DEMON. Symptom The autosyslog -e command displays messages indicating that it cannot connect to the database. Note: This file is appended to each time the event processor is started. or that no entries were made when the event processor service was started. Resolution The database service is down or there are problems with the Sybase installation.%AUTOSERV% | more Correct the problems identified at the end of this file. If the file exists. After you have done this. and the database service is accessible. Resolution Install your Time Key as described in the chapter “Entering License Keys. follow the steps in the Resolution section of Event Server is Down in this chapter. this directory is C:\tmp). Symptom Troubleshooting 16–11 . the event processor should be able to connect.%AUTOSERV% in the directory specified in the Enterprise-Wide Logging Directory field on the AutoSys Administrator Event Processor screen (by default. Resolution Check for a file named event_demon.Event Processor Troubleshooting The autosyslog -e command displays a message indicating that the Time Key is not valid. The autosyslog -e command displays messages indicating that the event processor log file does not exist. To fix the problem. Symptom 1.

%AUTOSERV% file or to the event_demon. the resolution depends on the Windows event log message. Uninstall Unicenter AutoSys JM. Event Log Message Incorrect options have been set to event_demon.%AUTOSERV% is missing! Resolution The event processor on the machine must have been started at least once or this message appears.%AUTOSERV%.) Event Log Message The environment variable AUTOSYS is too long. Resolution This occurs if you have modified the Windows Registry so that the -A option is not used when starting the Event Processor service. you must uninstall AutoSys. Resolution The %AUTOSYS% system environment variable is not available to the event processor. Event Log Message The log file %AUTOUSER%\out\event_demon. If the event processor has been started. Resolution The %AUTOSYS% environment variable value is set to a path that is longer than 80 characters. To fix this problem with the Windows Registry settings. It must not have been set properly.out file that is located in the directory specified in the Enterprise-Wide Logging Directory field on the Unicenter AutoSys Administrator Event Processor screen (by default. and then reinstall Unicenter AutoSys JM. ensure that permissions are set on the log file that will allow a system program to read and write to the file. Event Log Message The environment variable AUTOSYS is not set. The Event Log Viewer is located in the Administrative Tools program group. click on the System icon and ensure that the %AUTOSYS% environment variable is set properly in the System Environment Variables region. In the Windows Control Panel. Resolution This symptom could be attributed to a number of causes. (You can also check the setting of this variable on the UnicenterAutoSys Administrator System Information screen. this directory is C:\tmp). therefore. and reinstall it into a directory path that is fewer than 80 characters. 16–12 User Guide .Event Processor Troubleshooting The event processor will not remain started and does not write log output to the %AUTOUSER%\out\event_demon.

However. That process has terminated without proper notification to the event processor. Event Log Message An event processor is already running. Event Log Message chk_auto_up is taking a while to complete. To test for this problem. If this is successful. Uninstall and reinstall the software. When this occurs. This might occur on large or slow networks where chk_auto_up has to query every machine in the Authorized Event Processor Host Names list (which is located on the AutoSys Administrator Remote Agent screen). Resolution The event processor launches chk_auto_up upon initialization. Verify that chk_auto_up. it is recommended that you consider uninstalling and reinstalling the software. This event is only a warning.. it detected another event processor running with the same instance ID. you can run the event processor. That process reported that the setup is incorrect. Only one event processor can run in an instance. Event Log Message The AutoSys environment has not been installed correctly.. <NT Error Code> Resolution The event processor launches chk_auto_up upon initialization. Resolution The event processor launches chk_auto_up upon initialization. Resolution The event processor launches chk_auto_up upon initialization.exe is located in the %AUTOSYS%\bin directory and has the proper permissions for system programs to execute. That process is taking longer than 5 minutes to complete. run chk_auto_up in an instance command prompt window. Try setting the event processor to log on as the administrator. Resolution When the event processor was started. or do not attempt to start this event processor. Troubleshooting 16–13 . Event Log Message Wait for chk_auto_up process failed. Either stop the other event processor. EP not operational. something is seriously wrong with your local system account. and the event processor will wait for this to complete before starting. We will not start another one. Call Tech support. That process terminated prematurely with a Windows error code.Event Processor Troubleshooting Event Log Message chk_auto_up process is missing. and check how long it takes to complete.

If this file is greater than 256 KB. Also. check if the disk drive has run out of space. Ensure that the log file has permissions that will allow a system program to read and write to the file. Resolution The event processor was unable to create the normal log file named in the message. Resolution When the event processor starts it looks at the size of the EPFILENAME log file. If the event processor is unable to do this.Event Processor Troubleshooting Event Log Message Event processor cannot open its log file <EP logfile name>. Fix file and directory permissions so accessible by SYSTEM. Event Log Message Could not rename the LARGE event processor file: <EPFILENAME> to backup archive file:<EPBACKUPFILENAME>. or remove the files. check that EPFILENAME has permissions that will allow a system program to read and write the file. 16–14 User Guide . Also check if the disk drive has run out of space. the event processor will attempt to rename it to EPBACKUPFILENAME and create a new EPFILENAME log file. Some directory in the path is not accessible to the SYSTEM.

the remote agent should start properly. enter: autoping -m machine -D Instead of a single machine. and it does not return an error. Database Verification Use autoping to verify the remote agent database connection. autoping -m venice -D AutoPinging Machine [venice] AND checking the Remote Agent's DB Access. This command captures the output from the attempted database connection. displays it.Remote Agent Troubleshooting Remote Agent Troubleshooting Remote Agent Verification If you suspect problems with the remote agent. To check the database connections on machine. you can use autoping to verify your suspicions. if one is generated (use the -A argument to generate an alarm if problems are found). you can enter autoping -m ALL to check all machines. AutoPing WAS SUCCESSFUL! Troubleshooting 16–15 . The remote agent writes RUNNING and completion statuses directly to the event server. If you use the autoping -m client_hostname command. autoping The autoping command is used to test the connections between the event processor and the remote agent. and includes it in the alarm.

4. This action enables the menu items. 16–16 User Guide .Remote Agent Troubleshooting Remote Agent Will Not Start The symptoms in this section are similar and result from network problems. Select set Computer and Instance. To do this. 3. open the Unicenter AutoSys Administrator from the AutoSys program group. Resolution Either the Remote Agent service is not started. Symptom The autosyslog -e command displays a message like: Attempting to connect to AutoSys Remote Agent Service on socket=5280: Connection Refused Could NOT connect to machine: spartacus. verify that the Remote Agent service is started. Move to the Services screen by selecting Services from the menu or clicking the Services button (traffic light) on the toolbar. and their corresponding toolbar buttons. The remote agent may not be installed properly. click the Start Service button. 2. and follow these steps: 1. First. or the client machine is down. or Unicenter AutoSys JM was not installed or configured properly so that the remote agent and event processor use different port numbers. Select the Remote Agent from the Service drop-down list. You must resolve the network or machine problems before jobs can run on that machine. If the status is Stopped. Symptom The autosyslog -e command displays a message like: Attempting to connect to AutoSys Remote Agent Service on socket=5280: Interrupted function. Could NOT connect to machine: spartacus Resolution Either there is a network communication problem. and click OK. Check the Status using the traffic light icon and the Status field.

To do so. Remote Agent Starts. then check the following database-specific solutions. With Sybase and Microsoft SQL Server databases. SUCCESS. when the following event appears. 2. check the Remote Agent Port Number in the same fashion.” in this guide. Troubleshooting 16–17 . Command Runs: No RUNNING Event Is Sent Symptoms 1. First. or TERMINATED status events. FAILURE. The remote agent must be able to connect to the event server in order to send the RUNNING. For information on the Unicenter AutoSys Administrator. see the chapter “Administrator. yet the job does run to completion on the client machine: CHANGE_STATUS Status: STARTING Job: test_install Resolution This is a common problem and is nearly always the result of the remote agent being unable to contact the event server. Job is stuck in STARTING state. If the port number settings are different. follow these steps: 1. verify that the port numbers are synchronized using the Unicenter AutoSys Administrator. 2. start the Unicenter AutoSys Administrator and check the Remote Agent Port Number. On the event processor machine. On the machine where the Remote Agent service is located. this problem usually occurs because the SQL*Net V2 connections are not set up properly. synchronize the numbers by modifying the incorrect one. With Oracle. the usual cause of this connection problem is that the specified database settings are different from those used by the AutoSys event processor. then nothing else. If this is not the problem.Remote Agent Troubleshooting After the Remote Agent service is started. This problem is detected either in the Event Processor window (or log) or in the results of running the autorep command on the job. which is located on the Remote Agent screen. ensure that network problems are not preventing communication between the remote agent and the event server machines. 3.

plus run some diagnostics. check the database settings against the settings on the AutoSys Administrator Event Server screen. specified in the Unicenter AutoSys Administrator Remote Agent screen).Remote Agent Troubleshooting To verify the problem. and port number settings are the same as those on the event processor machine settings. For Sybase. check the Microsoft SQL Server database settings using the SQL Enterprise Manager. look at the Control Panel System dialog. 16–18 User Guide . Oracle.INI file exists. look in the AutoRemoteDir\auto_rem* file for this job (the AutoRemoteDir value is the Local Agent Logging Directory value. or Microsoft SQL Server) are the same as the settings Unicenter AutoSys JM is using. For Microsoft SQL Server databases.) To determine that all the database settings are correct. In addition. User accounts have been added on the database machines for all users. If the remote agent cannot send the event back to the database. check the settings on the Unicenter AutoSys Administrator Event Server screen for both the remote agent and the event processor machines. (The output from the autosyslog command could provide a helpful DBMS error number from the connect attempt. To determine the setting Unicenter AutoSys JM is using for the %SYBASE% variable. first make sure that the Sybase SQL. database. Verify that the remote agent’s event server name. into this file. In addition. then make sure that the settings are the same as the settings AutoSys is using. That is. This file is located in the %SYBASE%\INI directory. it will write a message to that effect. You can accomplish this by issuing the following command on the machine where the job is supposed to have run (using an Instance Command Prompt window): autosyslog -J job_name where: job_name Is the name of the job in question. make sure that the database settings (as determined by Sybase. you must make sure that one of the following is true: ■ ■ All AutoSys machines are on the same Windows domain. for Microsoft SQL Server database.

ORA. or the ISQL/w graphical query interface (for Microsoft SQL Server). and contains the correct information for the event server. TNSNAMES. Testing the Setup To test that everything is set up properly. When you log onto the event server. By default. For information on using the Unicenter AutoSys Administrator. using the xql utility (for Sybase). your jobs will go into Starting state. Check that the Oracle TNS names file. is readable. because the owner of the job does not have proper permissions on that database machine. exists.” in this guide. see the chapter “Administrator. and will seem to remain in this condition. If you are using Oracle. the TNS names file is in the following location: \ORANT\NETWORK\ADMIN\TNSNAMES. This behavior results from the fact that the remote agent cannot write the status back to the Microsoft SQL Server databases. try to log onto the event server from the client machine.ORA 2. use the “autosys” user and password. check for the following: 1. the SQL*Plus command language interface (for Oracle). Troubleshooting 16–19 . Check that the Oracle TNS names file has a SQL*Net V2 formatted entry for the event server.Remote Agent Troubleshooting If you do not configure your Microsoft SQL Servers in one of these ways.

xql returns the following message: DB-Library error: dbproc NULL Error in SybInit: dbopen failed Resolution Check the following: 1. then it is a problem with the interfaces file. 16–20 User Guide . Verify that the DSQUERY environment is set to the proper data server. see the resolution in Remote Agent Starts. Command Runs: No RUNNING Event is Sent in this chapter. Determine if the data server is started and running. 3. For more information about dealing with this file. and start it if it is not running. Run xql with the -S and -D options to specify the correct data server and database.Remote Agent Troubleshooting xql Will Not Start (Sybase Only) Symptom From the remote machine. If a fully-qualified xql statement still fails. Do one of the following: ■ ■ 2.

run_num.Job Failure Troubleshooting Job Failure Troubleshooting Remote Agent Will Start: Command Will Not Run Each time the remote agent is started on a machine. this directory is the C:\AUTOSYS. Any problems experienced by the remote agent are reported here.ntry auto_rem.pid where: AutoRemoteDir Is the Remote Agent Local Agent Logging Directory specified in the Unicenter AutoSys Administrator Remote Agent screen. which is the most common problem. or C:\AUTOSYS\INSTANCE.pid where: joid run_num ntry Is the job object ID. This is the form of the new file name: AutoRemoteDir\auto_rem. This file contains all the instructions passed to the remote agent by the event processor. By default.INSTANCE\tmp for single instance installations. Troubleshooting 16–21 . it renames this file to give it a unique name. or at installation time. including the inability to send events to the databases.joid. After the remote agent receives its instructions from the event processor. Is the number of tries or restarts. Is the process ID of the remote agent. Is the run job run number. it creates the following log file: AutoRemoteDir\auto_rem. and a record of all actions it took.tmp for multiple instance installations. the results of any resource checks.

Message: Couldn’t find valid entry in security key. regardless of the setting. 16–22 User Guide .> In addition. If the job fails for some reason. To turn off automatic deletion of the remote agent log files. the remote agent log as viewed with the autorep -J job_name command might display the following message: Remote Authentication has FAILED for User:USER@HOST on machine:RAHOST.” in this guide.Job Failure Troubleshooting To find the most recent instance of the remote agent Log for a given job. see the chapter “Administrator. the log file is not deleted. If this setting is on (the default setting). For information on the Unicenter AutoSys Administrator. you issue the following command on the machine where the job last ran: autosyslog -J job_name Note: The Clean Temporary Files setting in the Unicenter AutoSys Administrator Event Processor screen specifies whether the remote agent log files are to be cleaned up at the completion of a job. Symptoms The event processor log as viewed with the autosyslog -e command displays a message like: Agent remote authentication! Error:<Remote Authentication has FAILED for User: USER@HOST on machine:RAHOST. the file is removed when a job completes normally. deselect the Clean Temporary Files box on the Unicenter AutoSys Administrator Event Processor screen.

Cannot run job for user USER! Run "autosys_secure" to enter the user password. For this example. Symptoms Troubleshooting 16–23 . the password for the user@host_or_domain either does not exist or is not valid. Or a message similar to: No valid password was found for USER@HOST or USER@DOMAIN.Job Failure Troubleshooting Resolution The job is trying to run on a host that is different than the host or domain on which the job was defined. the job was defined on the HOST host. run the autosys_secure command to enter or change the user ID and password. Cannot run job for user USER! Run "autosys_secure" to enter the user password. Resolution In this example. Or a message similar to: Owner UserId/Password error! ERROR: No valid password was found for USER@HOST or USER@DOMAIN. ■ Symptoms The Event Processor log as viewed with the autosyslog -e command displays a message similar to one of the following: Owner UserId/Password error! ERROR: The password specified for USER@HOSR_OR_DOMAIN is invalid! Run "autosys_secure" to enter the correct password. USER can log on to the RAHOST machine and add a Trusted User entry for the USER@HOST user to the Trusted Users list on the Unicenter AutoSys Administrator Security screen.” of the Unicenter AutoSys Job Management for Windows and UNIX Reference Guide. and security (remote agent user authentication) has denied access for the host or domain on which the job was defined. For more information. In addition. see autosys_secure in the chapter “Commands. To fix this problem. In this case. you can resolve the problem in one of the following ways: ■ The edit superuser can log on to the RAHOST machine and add a Trusted Host entry for HOST to the Trusted Hosts list on the Unicenter AutoSys Administrator Security screen. and is trying to run on the RAHOST host. the remote agent log as viewed with the autorep -J job_name command could display a message similar to one of the following: The password specified for USER@DOMAIN is invalid! Run "autosys_secure" to enter the correct password.

most error messages will be in that file.” in this guide. see Job Profiles in the chapter “Jobs. 16–24 User Guide . The permissions are correct on any standard input and output files specified for re-direction. You should also verify the following items: ■ The default profile or the job’s specified user-defined profile has defined the proper job environment. look for error messages by running the autosyslog -e command on the event processor machine. For example. is correct. To determine what is wrong. if defined in a job profile. Symptoms When a job starts. It is always a good idea to include %PATH% in any job profile that defines a path variable. the event processor log as viewed with the autosyslog -e command displays a message similar to the following: Read Stream Socket Failed You can also see this message with the Event Report tool (which you can open from the Scheduler Console or Alarm Manager). a message indicating this would appear in the event processor log. ■ ■ ■ Note: A valuable debugging technique is to specify a file to be used for standard output and standard error for a job that is having run problems. For information on defining job profiles. The system permissions are correct for the job command to be executed. If there are any command problems. if the job’s standard out file was Read-only. In particular.Job Failure Troubleshooting The event processor log as viewed with the autosyslog -e command indicates that the job immediately returned as FAILURE. ensure that the path variable. and the autorep -J job_name command on the machine where the job was supposed to have run. The file system where the job command resides is accessible from this machine. This will ensure that all system path directories are accessible. Resolution A variety of things could be wrong.

Unicenter AutoSys JM can receive work from other agents. You can also create jobs that will run on any of the agent machines (if the agent machine is defined). Unicenter AutoSys JM can schedule jobs on any of those machines as well.Appendix A Integrating with the Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS Unicenter AutoSys JM enterprise-wide scheduling lets you integrate jobs with Unicenter AutoSys Agents for AS/400. and with various scheduling products on the mainframe. and OpenVMS. jobs can be defined to conditionally start based on the status of a job running on the included set of agent machines. AS/400. The following types of integration are supported: ■ Jobs can be defined to conditionally start based on the status of jobs running on OS/390. OpenVMS. Integrating with the Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS A–1 . The term “agent machine” is defined in the next paragraph. ■ ■ Using cross-platform job dependency notation.

AS/400. such as Unicenter Workload Server and Unicenter AutoSys JM Server. Common Communication Interface Any remote agent in the set of agents supported by AutoSys 4. script. a job running on a UNIX or Windows machine can be dependent on a job running on a mainframe.Definition of Terms Definition of Terms The following terms are used in this appendix: Term Unicenter AutoSys JM Unicenter AutoSys JM Connect CCI Unicenter AutoSys Agent Definition A job scheduler that runs on UNIX and Windows. JCL or other unit of work. Collects status information about job execution and file creations. Any machine which supports an agent. The agent performs the following functions: ■ Agent Machines Unicenter Workload Agent Receives job requests from one or more managers. These are Unicenter AutoSys JM. A dependency between jobs running on different platforms. and any Unicenter NSM Job Management Agent. Cross-instance job dependency Cross-platform job dependency A dependency between jobs running on different instances of AutoSys. Unicenter AutoSys JM Connect. A–2 User Guide . For example. scheduling agents for VMS. A small set of programs that execute on each target machine where jobs are processed. Software that lets AutoSys communicate with legacy OS/390 schedulers. ■ Sends status information to the requesting workload manager.0. and initiates the requested program.

Definition of Terms Related Documentation The information presented in this appendix supplements the following documents: ■ ■ Unicenter AutoSys Job Management for Windows Installation Guide Unicenter AutoSys Job Management Connect Option User Guide Note: Unicenter AutoSys JM can also drive your legacy mainframe scheduler by way of the Unicenter AutoSys JM Connect product. Integrating with the Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS A–3 . See the Unicenter AutoSys Job Management Connect Option User Guide for instructions on how to install and use this product.

5 for Windows NT/2000 CCI Version 16123032000 (minimum) TCP/IP One or more of the following: ■ To determine your version of CCI. DGI. and Windows) ■ ■ The following elements must be present on the machine: ■ asbIII An Unicenter AutoSys JM process that communicates with Unicenter AutoSys JM Connect or any supported Unicenter AutoSys Agent. and so forth. The required software and version levels are listed in the following table: Unicenter AutoSys JM ■ CCI ■ Unicenter AutoSys Agent ■ Unicenter AutoSys JM version 4. as instructed in the documentation for these components. You must also install and configure Unicenter AutoSys JM Connect or Unicenter AutoSys Agents. or both. OSF.5 lets you schedule or reroute jobs from multiple sources throughout the enterprise. you must install and configure the basic software as instructed in the Unicenter AutoSys Job Management for Windows Installation Guide. HP. Prerequisites Before you can implement enterprise job scheduling.Job Scheduling for the Enterprise Job Scheduling for the Enterprise Unicenter AutoSys JM 4. A–4 User Guide . NCR. enter the following command: rmtcntrl release Unicenter AutoSys JM Connect (OS/390) Unicenter AutoSys Agent for AS/400 or OpenVMS Unicenter NSM Job Management Agent (for UNIX versions such as AIX. SCO.

See the appendix “Introducing CCI” in the Unicenter AutoSys Job Management for Windows Installation Guide. After enabling AutoSysAgentSupport.Configuring for Enterprise Job Scheduling ■ CCI The Common Communication Interface. an instance can dispatch jobs to an Unicenter AutoSys Agent. Stop the Event Processor Before you proceed with the configuration and initialization procedures discussed in the following sections. select the Receive Remote Job Submissions check box on the Event Processor Maintenance tab of the Unicenter AutoSys Administrator. you need to configure the machine. Configuring for Enterprise Job Scheduling After installing and configuring the basic software and Unicenter AutoSys JM Connect or Unicenter AutoSys Agents. Integrating with the Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS A–5 . Set the Receive Remote Job Submissions Parameter To enable bi-directional support. enable Unicenter AutoSys JM Agent job support. shut down the event processor as shown following (you must be the exec superuser to do this): sendevent -E STOP_DEMON Configure the Machine Set the AutoSysAgentSupport Parameter To run jobs directly on a Unicenter AutoSys Agent. or both. To enable Unicenter AutoSys JM Agent job support. select the AutoSysAgentSupport check box on the Event Processor Maintenance tab of the Unicenter AutoSys Administrator.

Represents a Unicenter Job Management Agent Mmchine. Is one of the following: – – CNCT TNG Represents a Unicenter AutoSys JM Connect machine. For more information see the section Bi-Directional Scheduling in this appendix.EXTERNAL.EXTERNAL in the $AUTOUSER directory. CA7.EXTERNAL File To enable cross-platform dependencies. Create the config. AGT REMOTE_HOST The name of the agent machine. This is the name by which the Unicenter AutoSys JM Connect application will be known to AutoSys. create a file named config. add an entry similar to the following for each agent for which cross-platform dependencies will be exchanged: INS:AGT=REMOTE_HOST where: INS Is the three-letter uppercase identifier for the Unicenter AutoSys JM Connect instance.Configuring for Enterprise Job Scheduling After enabling this parameter. A–6 User Guide . In config. for example. the asbIIIsr1 process is started.

That is. CA-7.Configuring for Enterprise Job Scheduling config. VMS. Therefore. or INS.EXTERNAL file can contain a maximum of 249 entries.EXTERNAL file (if you want to communicate with Unicenter AutoSys JM Connect).EXTERNAL Examples: The following are examples of the config. ■ FRU:CNCT=fruit where: FRU CNCT fruit Is a three-character instance name. or INS. it is important to ensure the settings are consistent. Is the agent type. Note: The config. or AGT. the following must be true: ■ AutoSysAgentSupport check box is selected on the Event Processor Maintenance tab of the Unicenter AutoSys Administrator. or AGT. Is the agent type. Is a REMOTE_HOST that is a Unicenter NSM Job Management Agent machine on AS/400.EXTERNAL file: ■ FLO:TNG=flower where: FLO TNG flower Is a three-character instance name. CA-Jobtrac. UNIX. Ensure Consistent Integration Settings When the event processor starts up. or CA-Scheduler. If the parameter setting is inconsistent with the other integration settings. Is a REMOTE_HOST that is an AutoSys Connect machine on OS/390. Unicenter AutoSys JM Connect instances are defined in the config. it checks the setting of the AutoSysAgentSupport check box on the Event Processor Maintenance tab of the Unicenter AutoSys Administrator. or Windows. ■ Integrating with the Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS A–7 . the event processor will detect this disparity and shut down. to enable communication with any Unicenter AutoSys Agent.

EXTERNAL file. A–8 User Guide . you must: ■ Comment out any Unicenter AutoSys JM Connect instances in the config. If you want to disable both Unicenter AutoSys Agent and Unicenter AutoSys JM Connect communication. you must do the following: ■ Clear the AutoSysAgentSupport check box in the Event Processor Maintenance tab of the Unicenter AutoSys Administrator. Restart the Event Processor Now you can start the event processor using the Unicenter AutoSys Administrator Services screen. Introducing CCI in the Unicenter AutoSys Job Management for Windows Installation Guide. For information about starting the event processor.Configuring for Enterprise Job Scheduling If you want to disable only Unicenter AutoSys JM Connect communication. ■ Configure the Communication Components See the Appendix A.EXTERNAL file. see the chapter “Administrator.” in this guide. Comment out any Unicenter AutoSys JM Connect instances in the config.

When the event processor is started. It is a necessary component for cross-platform communication. as in the following example. the event processor starts asbIII automatically. asbIII will also stop running. or goes down for any reason. Letting asbIII handle that exchange frees the event processor to handle other events. If the event processor is stopped. The only way to bring up asbIII is to restart the event processor. use the sendevent command. the only way to change the status of the job is to change it manually. If the event processor and asbIII go down while an Unicenter AutoSys JM Connect job finishes. the completion event will be lost.About asbIII About asbIII Communication between Unicenter AutoSys JM and Unicenter AutoSys JM Connect or a Unicenter AutoSys Agent is facilitated by asbIII. it checks if the AutoSysAgentSupport check box in the event processor tab of the Unicenter AutoSys Administrator is enabled. If it is. (This does not happen to an Unicenter AutoSys Agent job because missed events are resent during a checkpoint restart at asbIII startup. Integrating with the Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS A–9 . This dialog is accessed from the Scheduler Console.) That information is sent only once and is not saved. (You must have execute permission on a job in order to change its status. If this happens. as shown in the following example: sendevent -E CHANGE_STATUS -J job_name -s status You can also use the Send Event dialog to change the status of a job.) To change the status of a job.

PRIMARYCCISYSID PRIMARYCCISYSID = cci_system_id This environment variable defines the CCI system ID used by the Broker running under the Primary Event Processor when communicating with remote nodes (mainframe or Unicenter Workload Agents. Any statuses currently residing on the remote agent machines (mainframe or Unicenter Workload Agents) will now be dispatched to the Shadow EP machine as opposed to the primary for processing. Through the Unicenter AutoSys Administrator “System” selection. all Broker communication under the Shadow EP will take place as normal. ■ A–10 User Guide . Should the Primary EP failover.About asbIII Environment Variable for asbIII You can customize asbIII by setting the environment variable from the Environment tab of the System Properties dialog. The value of this environment variable is passed by the Primary EP to the Shadow EP on startup.) This environment variable is key to providing Broker failover support within the Unicenter AutoSys JM environment should the Primary EP shutdown or become unreachable. To set this environment variable on Windows: ■ Automatically configured at installation time should the Event Processor component of Unicenter AutoSys JM be installed.

these instances can share the same database. You can define a job in the database. see the section Configure the Machine. It is also possible for a later instance to run jobs defined by an earlier instance. You can start jobs in other instances running on other nodes through out their respective asbIII’s. since multiple instances can be thought of as full peers of one another. In order to enable this feature. Any instance can initiate or be a recipient of any other instance. Integrating with the Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS A–11 . in this appendix. destined to run on any agent supported by Unicenter AutoSys JM. and include the agents defined in this appendix with a full-fledged job definition. or an NT MSSQL instance can initiate jobs in a Linux Sybase. and the scheduling load can be distributed across the network. Although. a Solaris Sybase and an AIX Oracle or HP environment can be added. Note: There is no restriction on platforms.5. For example. provided the instances run on distinct servers. In either case.About asbIII Bi-Directional Scheduling Running Jobs on Behalf of a Workload Manager With Unicenter AutoSys JM 4. The statuses of these jobs will be reported back to the Workload Manager as if Unicenter AutoSys JM was the Workload Agent. in the configuration file. For more information on AutoSysAgentSupport. you must have the AutoSysAgentSupportReceiveSubmit parameter set to 1. regardless of platform or database. a Linux Sybase instance can initiate jobs in an NT MSSQL environment. so that job can be initiated by a Workload Manager. databases or number of instances when running this broker-to-broker mode. it is possible to extend the Workload Manager’s capabilities into Unicenter AutoSys JM. The broker-to-broker function can be combined with the Workload function described previously.

Unicenter AutoSys JM Connect Cross-Platform Dependencies Unicenter AutoSys JM Connect Cross-Platform Dependencies Jobs can have dependencies on jobs managed by the Unicenter AutoSys JM Connect scheduling software running in the OS/390 environment. a job defined to run on a UNIX or Windows machine could have as a starting condition the successful completion of an Unicenter AutoSys JM Connect job running on a mainframe system. The event processor communicates with Unicenter AutoSys JM Connect through a process called asbIII. as described in Create the config. a file named config. communication between Unicenter AutoSys JM and Unicenter AutoSys JM Connect is handled by asbIII and the communication components.EXTERNAL is present on the machine on which the event processor was installed. which communicates with any supported agent through CCI. In addition.EXTERNAL File in this chapter. AutoSys Windows REMOTE_HOST: MYMACHIN Instance: ACE C O N N E C T OS/390 REMOTE_HOST: CA7 Event Server CCI CCI Job Event Processor asbIII Note: CCI components are listed in the appendix “Introducing CCI” in the Unicenter AutoSys Job Management for Windows Installation Guide. the mainframe has been identified with a three-letter uppercase instance name. For example. A–12 User Guide . In the previous figure. In this file.

asbIII communicates the status to the database. 6. asbIII passes the request to Unicenter AutoSys JM Connect. The event processor starts the job that is dependent on the completion of the remote job. For jobs. Unicenter AutoSys JM sends a request to asbIII for the status of an Unicenter AutoSys JM Connect job running on a mainframe. see your Unicenter AutoSys JM Connect documentation. 5. The completion status of the job is passed to asbIII. Integrating with the Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS A–13 . 4. 7. and Unicenter AutoSys JM Connect jobs can be dependent on the status of jobs. Unicenter AutoSys JM Connect registers the request. 2. 3. For details on how to implement this with the Unicenter AutoSys JM Connect job scheduler.Unicenter AutoSys JM Connect Cross-Platform Dependencies Job Scheduler Interdependencies Jobs can be dependent on the status of Unicenter AutoSys JM Connect jobs. To create job scheduler interdependencies: 1. the following describes this type of cross-platform dependency. The job runs as scheduled by Unicenter AutoSys JM Connect that can run the job on the mainframe.

use the following notation: JOB_NAME^INS where: JOB_NAME INS ^ Is the name of the job. you enter this in the condition job attribute. Is a three-letter uppercase identifier of the instance on which the job is running. From JIL.Unicenter AutoSys JM Connect Cross-Platform Dependencies Notation for Cross-Platform Job Dependencies To define a cross-platform job dependency. (Caret symbol before the instance name)—Indicates that the job resides on a different instance of AutoSys. enter this information in the Dependencies field of the Job Editor. Use the following statuses in the condition attribute of an job definition dependent on an Unicenter AutoSys JM Connect job: ■ ■ ■ ■ SUCCESS TERMINATED DONE NOTRUNNING A–14 User Guide . as shown in the following example: condition: success(JOB_NAME^INS) From the GUIs. Note: Job names for cross-platform dependencies must be all uppercase. The caret symbol (^) before the instance name indicates that the job resides on a different instance of AutoSys.

” an OS/390 scheduler defined job that runs on a mainframe: condition: success(JOBA^CA7) where: success(JOBA^CA7) Specifies the successful completion of an OS/390 defined job named “JOBA” running on a mainframe specified with the three-letter ID of “CA7. numbers. ■ ■ Note: These limitations do not apply to all jobs. the names of jobs specified as job dependencies between Unicenter AutoSys JM and Unicenter AutoSys JM Connect must follow these guidelines: ■ The first character of a job name must be an uppercase alpha character or one of the following characters: pound sign (#). Integrating with the Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS A–15 .” in this guide. only to jobs that will be referenced to Unicenter AutoSys JM Connect.) Job names can be no longer than eight characters. For more information about cross-instance job dependencies. or a pound sign (#). see Cross-Instance Job Dependencies in the chapter “Jobs. an at symbol (@). or a dollar sign ($). or a dollar sign ($.Unicenter AutoSys JM Connect Cross-Platform Dependencies Unicenter AutoSys JM Connect Cross-Platform Dependency Example Following is an example of an job that will start only upon the successful completion of “JOBA. The remaining characters in the job name can be any combination of uppercase alphabetic characters. All alphabetic characters must be in uppercase. an at symbol (@).” Naming Conventions for Unicenter AutoSys JM Connect Cross-Platform Jobs Because of naming limitations in the OS/390 environment.

communication between Unicenter AutoSys JM and all agents is handled by asbIII and CCI. ■ ■ A–16 User Guide .Running Jobs on Agents Running Jobs on Agents Unicenter AutoSys JM can directly schedule jobs on a machine that is running a supported agent. In the previous figure. The agent (which in this example is running on the AS/400 platform) is analogous to an remote agent. The communication components running on the machine receive information from the agent and pass it to asbIII. assuming the machine running the agent has been defined to Unicenter AutoSys JM. In the following example configuration. Unicenter AutoSys JM and agent integration is supported on other operating platforms as well. AutoSys Windows REMOTE_HOST: MYMACHIN Instance: ACE AS/400 REMOTE_HOST: ZASYS400 Event Server CCI CCI Job Event Processor asbIII AGENT Note: CCI components are listed in the appendix “Introducing CCI” in the Unicenter AutoSys Job Management for Windows Installation Guide. the agent is running on an AS/400 machine. ■ The event processor communicates with an agent through a process called asbIII.

3. 2. These job names and user IDs can be both uppercase and lowercase (when the operating system allows mixed case). the job changes to RUNNING status. agent job names can contain up to 64 alphanumeric characters and agent user IDs can contain up to 30 alphanumeric characters. 4. the agent client traps the return code and passes the information that the job is finished to asbIII.Running Jobs on Agents Agent Job Names and User IDs Agent job names and user IDs have the same naming restrictions as Unicenter AutoSys JM. 6. Blank spaces and tabs are illegal characters. AEOJ). asbIII writes to the database. To run jobs on agent managed machine: 1. the job changes to a status of either SUCCESS (if the job exited with a normal end of job code. which starts the job. 5. Running Jobs On Agent Managed Machines The process by which Unicenter AutoSys JM can run jobs directly on an agent managed machine is described following. asbIII writes to the database. EOJ) or TERMINATED (if the job exited with an abnormal end of job code. The event processor sends the job information to asbIII and the job changes to STARTING status. asbIII passes the information to the agent. Integrating with the Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS A–17 . The agent passes the information that the job is running (BOJ event) to CCI on the AutoSys machine that writes it to the proper broker instance. Where the operating system allows. When the job exits.

It is described in detail in the chapter “Load Balancing and Queuing Jobs. and factor attributes are not supported for agent-managed machines. This command adds a new machine definition to the database. ■ c Indicates a machine running Unicenter AutoSys JM Connect. which has a REMOTE_HOST of “ZASYS400. Note: Agent managed machines cannot be part of a virtual machine. you must first define the agent machine to Unicenter AutoSys JM using the insert_machine subcommand. CA-JobTrac. For example. To define an agent machine. max_load. use JIL and follow this example: insert_machine: REMOTE_HOST type: MACHINE_TYPE where: REMOTE_HOST MACHINE_TYPE Is the name of the agent machine. CA-7. to define the machine shown in the previous figure in this chapter. or CA-JobTrac. or any OS/390 scheduling system.” in this guide. This section pertains specifically to defining an agent machine. If Unicenter AutoSys JM Connect is running on the same machine as CA-7. job_load. the machine type should be c.Running Jobs on Agents Defining Agent Machines Before you can run jobs on an agent machine.” you would specify the following: insert_machine: ZASYS400 type: t A–18 User Guide . Is one of the following: ■ t Indicates a machine running Unicenter NSM Job Management.

COM” machine:VMSNODE owner:system@VMSNODE max_exit_success:1 Note: A job that executes successfully on an OpenVMS machine returns an exit code of 1.wx date_conditions: 1 days_of_week: all start_mins: 45 The following job definition example is for OpenVMS: insert_job: vmsjob1 command:”@SYS$LOGIN:SCHEDULE_WAIT. by default.Running Jobs on Agents Job Definition Examples The following job definition example is for an AS/400: insert_job: as400_a1 job_type: c command: DLYJOB DLY(15) machine: usprncax owner: user1@usprncax permission: gx. Integrating with the Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS A–19 . Unicenter AutoSys JM .wx date_conditions: 1 days_of_week: all start_mins: 30 The following job definition example is for Unicenter AutoSys JM Connect: insert_job: cas1 job_type: c command: auto_cnct -a A87SOENF -j RYAKEJ01 -c RUN -p SCHEDULE=RYAKE01 -s CAS machine: A87SOENF owner: user1@A87SOENF permission: gx. will interpret an exit code of 1 as a failure unless the max_exit_success attribute is used in the job definition.

[7] Disable E-Trust Access Control [8[ Exit autosys_secure. ZASYS400 Log and Trace Information If AutoSys is unable to start a job on an agent. an entry will be inserted into the event processor log located in the %AUTOUSER%\out directory. For example: insert_job: as400ji owner: bob@ZASYS400 machine: ZASYS400 command: DLYJOB DLY(16) The owner identified in the owner attribute of the job definition must have an account on the target agent machine. The owner of the job definition must be specified as “user@machine. Start the Security Utility: $ autosys_secure 2. A–20 User Guide . The account must match the owner name exactly in order for the job to run.” The edit superuser must use the autosys_secure binary to add valid userids and passwords using option 4 as follows: 1. [4] Create AutoSys User@Host or Domain password. [3] Change AutoSys remote authentication method. and password information when prompted: Enter user name : bob Enter user Host or Domain : Enter new password: Enter new password again: User Create successful.Log and Trace Information Unicenter AutoSys Agent Machine In an Job Definition Once you have defined an Unicenter AutoSys Agent machine to Unicenter AutoSys JM you can specify that machine in an job definition. user host or domain. using the machine job attribute. Select option 4 from the menu: AutoSys Security Utility Please select an action to perform: [1] Administer EDIT/EXEC superusers [2] Change AutoSys database password. Enter the user name. [6] Delete AutoSys User@Host or Domain password. [5] Change AutoSys User@Host or Domain password. > 4 3.

Unicenter AutoSys JM Connect and Unicenter AutoSys Agent Job Statuses Unicenter AutoSys JM Connect and Unicenter AutoSys Agent Job Statuses The valid statuses that Unicenter AutoSys JM can get for Unicenter AutoSys JM Connect and Unicenter AutoSys Agent managed jobs are: ■ STARTING The job has been passed from the event processor to asbIII. SUCCESS The job has ended and an EOJ (End Of Job) event has been passed back to asbIII. Integrating with the Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS A–21 . TERMINATED The job has ended and an AEOJ (Abnormal End Of Job) event has been sent back to asbIII. RUNNING The job has started and a BOJ (Beginning Of Job) event has been sent back to asbIII. ■ ■ ■ Any Unicenter AutoSys JM Connect or Unicenter AutoSys Agent managed job without a return code of zero will be considered TERMINATED.

they will be ignored. The JIL attribute is listed on the left and the corresponding GUI field is shown on the right.. Heartbeat Interval (mins) Job Load If the Box fails should this Job be Terminated? Job Type (File Watcher) Number of Times to Restart this Job after a FAILURE Que Priority Job Environment Profile File to Redirect to Standard Error File to Redirect to Standard Input File to Redirect to Standard Output Terminate this Job Mins after starting File To Watch For Minimum File Size (in Bytes) Time Interval (secs) to Determine Steady State priority profile std_err_file std_in_file std_out_file term_run_time watch_file watch_file_min_size watch_interval A–22 User Guide . JIL Attribute chk_files heartbeat_interval job_load job_terminator job_type:f n_retrys GUI Field Resource Check . If specified.Unsupported Attributes for Unicenter AutoSys JM Connect or Unicenter AutoSys Agent Jobs Unsupported Attributes for Unicenter AutoSys JM Connect or Unicenter AutoSys Agent Jobs The following attributes are not supported for Unicenter AutoSys JM Connect or Unicenter AutoSys Agent managed jobs..File System Space.

The chase and autoping commands cannot return any information on Unicenter AutoSys JM Connect or Unicenter AutoSys Agent jobs and machines. keep the following in mind: ■ If you are running a shadow event processor. cross-platform dependencies will be lost if the shadow event processor takes over. The following events cannot be executed on an Unicenter AutoSys JM Connect or Unicenter AutoSys Agent job: ■ ■ ■  CHANGE_PRIORITY  SEND_SIGNAL Integrating with the Mainframe and Unicenter AutoSys Agents for AS/400 and OpenVMS A–23 . Remote authentication is not supported for Unicenter AutoSys JM Connect or Unicenter AutoSys Agent jobs.Cross-Platform Limitations Cross-Platform Limitations When you are running across platforms.

.

Troubleshooting CCI B–1 . you know that the kernel accepts connections on behalf of the ccirmtd process. which can be resolved to caic(ci). Troubleshooting Tools for Remote CCI Connections The following are troubleshooting tools: netstat The netstat command allows you to check TCP/IP statistics: ■ netstat –a | grep caic Shows all connections to the local host involving a port. This means that a remote host attempting to connect to this host should get the TCP/IP connected state. If the latter is present. Established connections are important because we know that CCI transactions may not transpire between the hosts in question if a TCP/IP Established connection does not exist.Appendix B Troubleshooting CCI This appendix describes troubleshooting CCI for AutoSys. The important connections are ESTABLISHED and LISTEN.

B–2 User Guide . as well as the IP address. This is usually indicative of name resolution problems. Verify the IP address and host name for both hosts. If there is a question as to the integrity of the DNS environment. You can issue: netstat –an | grep 1721 netstat skips the name resolution and displays information about connections. nslookup The nslookup command allows you to be sure that the name of the host to which you wish to connect.Troubleshooting Tools for Remote CCI Connections It is important to understand that netstat output is of the form: ip-address:port where the local host listed to the left of the remote host. You then enter the IP address back into nslookup and verify that the same host name is returned. If you cannot ping a host. The netstat –i command also provides valuable statistics about network collisions. ping The ping command allows you to establish that a remote host can be reached. Sometimes netstat –a does not return or may take a long time to return with very little information. You can use the netstat –i command to determine if the host has more than one network card and determine the host names or IP addresses of these cards. is resolvable. CCI cannot establish a connection to that host. The latter side is that which initiated the connection. One side will always have a port that resolves to caicci and the other side will have a numeric port. The important thing to look for is high ratio of outgoing or incoming packets to collisions. ■ netstat –i Shows information about the network interfaces on the local hosts. It is important to ping by IP address as well as host name. A collision occurs when two hosts simultaneously attempt to send on an ethernet. you can use nslookup to verify the IP address of the host to which you need to communicate.

■ ccinet status Allows you to determine the status of the CCI connections. (ccinet ping tests remote-process-to-remote-process communication) Troubleshooting CCI B–3 . this is the rmtcntrl binary. this command may show where the network path is failing. This does not use the native ping command nor does it operate in quite the same way. ccinet ccinet may be used to pass commands to the ccirmtd demon on UNIX. If a client cannot ping a host. This may be used as follows: ■ ccinet ping Can be used to send a special CCI test packet across the CCI connection.Troubleshooting Tools for Remote CCI Connections traceroute and tracert The traceroute command on UNIX and the tracert command on Windows allow you to determine the route taken between two hosts. ■ ccir/ccis/ccic/ccii Provides you a suite of test binaries to test application-to-application CCI communication. On Windows.

nrs. The valid states are: ■ ■ ■ ■ ■ STOPPED STARTED START PENDING STOP PENDING NOT INSTALLED and RUNNING B–4 User Guide . ccicntrl status Displays the status of the CCI services. the process is no longer available as a service. Path is the directory in which the executable resides. The specific services are: ■ ■ ■ ■ ■ tpd: Transport nrs: NR-Server nrc: NR-Client rmt: Remote ccicntrl remove [ tpd | nrs | nrc | rmt ] This removes the specified service. rmt] This is used to stop or start the CCI services. rather.CCI Command Line Controls CCI Command Line Controls The command binaries on Windows are the following: ccicntrl rmtcntrl ccicntrl The main command binary is ccicntrl. nrc. This does not imply that the binary is affected in any way. ccicntrl install [tpd | nrs | nrc | rmt ] PATH This command installs the specified service. ccicntrl [start | stop] [tpd.

Troubleshooting CCI B–5 . rmtcntrl debugon and rmtcntrl debugoff Starts and stops remote service tracing. A unitrace window should have been open prior to issuing this command.CCI Command Line Controls rmtcntrl The remote service is contacted in a manner similar to the remote demon on UNIX. rmtcntrl rrt Displays detailed information to stdout about the remote receivers. The command executable is rmtcntrl. Note: rmtcntrl hats and rmtcntrl rrt are equivalent to ccinet show. rmtcntrl status Displays information about the state of connections to remote hosts. rmtcntrl hats Displays detailed information to stdout about the connections to other hosts.

Neither side will attempt to reconnect. rmtcntrl release Displays the release of the remote service. rmtcntrl disconnect sysid The remote service will disconnect from the remote host specified. rmtcntrl reconnect [All] sysid The remote service disconnects and reconnects to all of the remote hosts to which it is connected or to the specified host.CCI Command Line Controls rmtcntrl ping sysid Sends a CCI test packet to the remote host specified and displays the round trip time. B–6 User Guide .

the ISDBGACTIV environment variable can be set as any other environment variable using either the setenv or export command depending on the UNIX operating system used. ISDBGACTIV is an OS environment variable. a Unicenter AutoSys JM environment variable has been introduced called ISDBGACTIV. In UNIX. the traceable applications will look for the set value of the ISDBGACTIV environment variable and will output certain trace messages given the value assigned. In Windows. (For UNIX. For Windows it is a registry key). the ISDBGACTIV environment variable must be set using the Administrator Tool through the System Environment Variable screen.Appendix C General Debugging To better monitor the behavior of the Unicenter AutoSys JM product and to facilitate in identifying problems while troubleshooting. message queues) OPX Internal Communications Status Information EDB EDB Event Processor Debug Messages 8 16 32 DDB DDB Database General Debugging C–1 . Upon startup. The environment variable must be set prior to initiating the product. Values The following is a description of how the products interpret the ISDBGACTIV values: ISDBGACTIV Value ID 1 2 4 Description DBG Generic Debug Status Information CDB CCI Memory Output MDB Internal Communications Data Information (sockets.

To view all traces. DBG. Each of these products generate their own log files under normal circumstances located in the $AUTOSERV/autouser/out directory. C–2 User Guide . The products that generate trace messages are the Event Processor. and DDB generate large amounts of trace statements whereas OPX and EDB provide light traces. Any trace messages will be added to these log files at various places as the products encounter them. MDB. ISDBGACTIV should be set to 32 + 1 = 33.Values ISDBGACTIV Value ID 64 Description RDB Event Processor to Remote Agent Communications Information SDB Sendevent Status Information JDB Job Start Status Information 128 256 The individual values can be combined to control the number of traces generated. For example. and the Remote Agent. In general. to view Event Processor Debug Messages and Generic Debug Status. ISDBGACTIV should be set to 63 (32+16+8+4+2+1). the AutoSys Broker. the AutoSys Broker CCI Send and Receive Objects.

Select option 1. ■ Running Unicenter AutoSys JM 4. Unicenter Integration D–1 . From the autosys\bin directory. Modifying your Unicenter AutoSys JM Admin configuration to publish events on the Unicenter Event Manager console. The integration process consists of the following steps: ■ ■ Running the integration utility on Framework. enter: autosys_wv The utility displays the following menu: [1] Add Instance [2] Delete Instance [3] List Autosys Instances [4] Exit 2.5/Unicenter NSM Framework Integration Utility 1.Appendix D Unicenter Integration Important! The information contained in this appendix pertains to Window users only. Starting the 2D map on Framework and launch the Unicenter AutoSys JM applications.

you are connected to the repository to perform operations. Enter the three-character instance name. D–2 User Guide . Type 1 at the prompt: AutoSys WorldView Utility [1] Add Instance [2] Delete Instance [3] List AutoSys Instances [4] Exit > 1 3. The following messages are displayed: Checking if Instance ACE exits in the repository. Start the WorldView Utility from the autosys\bin directory.5/Unicenter NSM Framework Integration Utility 3.” After the repository is selected. When the autosys_wv utility is started the repository selection box appears. Select the “hostname_TNGDB. The new object is created only if the instance is installed and the object does not exist in the repository.. 4. AutoSys Instance ACE does not exist! New object ACE created successfully. enter: autosys_wv 2. 5. Type AutoSys Instance: ACE.. The default user ID is “sa” with no password.. Sign on. Example: 1. Once you sign on. it creates the AutoSys class and a Unicenter AutoSys JM instance.. The instance is created as an object of the Unicenter AutoSys JM class.Running Unicenter AutoSys JM 4. When the autosys_wv utility is first executed. the repository sign on box appears.

5/Unicenter NSM Framework Integration Utility 4.. 6. [4] Exit. from the AutoSys WorldView Utility menu: AutoSys WorldView Utility [1] Add Instance. from the AutoSys WorldView Utility menu: AutoSys WorldView Utility [1] Add Instance [2] Delete Instance [3] List AutoSys Instances [4] Exit > 1 5.. Start the 2D map to view these two Unicenter AutoSys JM instances and will launch the AutoSys applications... ACE 2. Type AutoSys Instance: CHA The following messages are displayed: Checking if Instance CHA exits in the repository. Type 1. Type 3. [3] List AutoSys Instances. CHA 7. AutoSys Instance CHA does not exist! New object CHA created successfully. > 3 The following message appears: There were 2 AutoSys objects found 1. [2] Delete Instance.Running Unicenter AutoSys JM 4. Unicenter Integration D–3 .

Modifying Admin Configuration to Publish Events to the Unicenter Console Modifying Admin Configuration to Publish Events to the Unicenter Console 1. Note: To modify the settings on this screen. Therefore. 2—Alarms and Job Completion status are sent. if you make a change that you want to implement immediately. then Click OK. 1—Only the Alarms are sent. whose events you want to publish to the Unicenter Console. Click OK. Events are sent to the Event Management Console based on the value set in the “Unicenter Events” edit box. 3—All the events are sent. in the event processor screen. you must stop the event processor using the sendevent -E STOP_DEMON command. Click Apply. Enter the integer value (0–3) that corresponds to the desired message level in the Unicenter Events edit box. D–4 User Guide . The valid values for the Unicenter Events edit box are: 0—No events are sent. you must have privileges in the Windows Administrators group. 3. from the drop-down list. 2. Select event processor from the drop-down menu. This field is located in the lower-right corner of the event processor screen. 5. Select the instance. then restart the event processor using the Administrator Services screen (as described in the chapter “Administrator” of the Unicenter AutoSys Job Management for Windows User Guide). Important! The event processor only reads the settings in the Unicenter AutoSys JM Administrator on startup. Open the Unicenter AutoSys JM Admin GUI. 4.

Right-click the Unicenter AutoSys JM icon to display the Unicenter AutoSys JM menu. Select Programs.Modifying Admin Configuration to Publish Events to the Unicenter Console After the Integration Process For detailed information about using Unicenter. 2. based on the level set in the Unicenter AutoSys JM Administrator. 1. Unicenter Integration D–5 . Unicenter AutoSys JM events will now display on the console. you can launch all Unicenter AutoSys JM GUIs. Click Windows. c. Enterprise Managers. see the WorldView Help. In the Framework Managed Objects program window. Restart Framework 2D Map. b. From here. you will see the new icon for the Unicenter AutoSys JM instance. Click Console Logs. Unicenter Events edit box. To view Unicenter AutoSys JM events on the Unicenter console: a. Click Events. 4. 3. d. event processor. Unicenter.

If this is the last instance in the repository being deleted when you select option 2. 2.Removing Icons from WorldView Removing Icons from WorldView 1. D–6 User Guide . [2] Delete Instance. Type 4 to exit the integration utility menu: 1] Add Instance [2] Delete Instance [3] List AutoSys Instances [4] Exit > 4 The Unicenter NSM Console continues to display Unicenter AutoSys JM messages even though the WorldView icon has been removed. Select 2 to delete an instance from the CORe and enter the name of the instance you want to delete. [3] List AutoSys Instances. [4] Exit. 3. enter: autosys_wv The AutoSys WorldView Utility displays the following menu: [1] Add Instance. From the autosys\bin directory. the AutoSys class is deleted.

A–10 asset level security. 12–7 menu bar. 1–11 /tmp/autotest. 15–20 after_time report attribute. 12–4 Alarm Selection dialog. 6–4. 13–14 sound. 15–32 asbIII. 12–3 Currently Selected Alarm acknowledging. 13–13 Index–1 .Index acknowledging alarms. 14–13 all_events monitor/report attribute. environment variables.$JobName. 12–3 Alarm List. 13–14 monitor/report alarm monitor/report attribute. 12–7 closing. about. 3–13 Administrator Services. 13–12 all_status. 13–12 $ $AUTORUN. 12–7 closing alarms. 13–11 all_status monitor/report attribute. 14–13 Alarm Sentry. 13–15 agent machines defining to AutoSys. 12–8 alarm monitor/report attribute. 14–13 / /bin/date command. 11–42 ACTIVATED status. 12–4 registering responses. 6–4 about. 12–3 Append stdout/stderr. 3–21 monitor alarm_verif. 13–12 A Action Area Layout dialog. 2–21 attributes job dependencies. 12–7 Response edit box. 12–9 Select by State region. 12–11 Select by Type region. 12–11 Select by Time region. 14–13 % %AUTOSERV% variable. 12–10 changing alarm states. 15–6 %autotestmode%. 13–14 alarms. 12–1 alarm_verif monitor attribute. 13–12 job_filter. A–18 in a job definition. A–20 Alarm Manager. 3–32 $AUTOTESTMODE.

A–4 support. 15–3 modifying configuration parameters. A–5 autosyslog. 13–15 currun. 15–9 AutoSys Services. 3–17 examples. 5–1 diagram. 15–38 AutoSys Administrator defined. monitoring Remote Agent log. 1–3 instances defined. 1–10 machines. 5–1 basic job definition. 1–4 database defined. 15–50. A–1 AutoSys Connect and AutoSys Agent support. 15–12 AutoSys instance defined. A–22 Attributes Date and Time. 14–16 backups calendar definitions. 14–17 monitor and browser definitions (using monbro). 15–48 Services. 15–52 Sounds Screen. 15–8 screen. 2–1 System Information. 1–5 graphical user interface see GUI. 15–3 System Information screen. 15–13 Instance screen. 16–15 AutoSys components. 15–50 AutoSys Sounds. A–1 AutoSys Console Utilities. 15–39 AutoSys Administrator Security Screen. 3–12 default behavior. 15–2 Notifications screen. 15–36 screens. 16–10 Services Screen. A–17 machines. 14–17 batch files and exit codes. 1–10 Notification Mechanism. A–18 running jobs. 15–1 Event Processor Screen. 3–3. 3–21 unsupported. AutoSys Administrator. 4–27 Authorized Event Processor Host Names. 15–6 ID. 8–9 Box Jobs. 15–6. 15–38. 14–17 job definitions (using autorep). 15–1 AutoSys Event Servers. 3–29 Bi-Directional Scheduling. 5–10 Index–2 User Guide . 15–43 AutoSysAgentSupport parameter. 15–18 B backing up definitions. 13–15 starting conditions. 15–11 autoping. 15–46 AutoSys Agent job names and user IDs. 14–16 machine definitions (using autorep). 15–43 starting. 15–1 Security Screen. 16–22 AytoSys Event Processor. 14–16 global variables (using autorep). 15–6 AutoSys Remote Agent screen. 15–7 menu bar and toolbar. A–16 software requirements. 15–19 Event Server screen.report after_time. A–11 Box Creating. 15–35 security.

14–18 reverting to last saved. 14–14 Chase On Startup. B–1 ccicntrl. 9–22 rule specification. 5–5 placing job in GUI. 9–5 selecting. 9–24 navigation controls. 9–7 backing up definitions. 9–1 applying rules. 11–27 CHANGE_STATUS. 15–31 clean_files. 9–4 Utilities menu. 9–15 date states. 9–17 unsetting dates. 9–19 printing. 3–11 COMMENT. 9–18 combining. B–4 CHANGE_PRIORITY. 9–24 navigation controls. 5–9 browsers backing up definitions. 9–7 rule specification. 3–4.force starting jobs in a box. 9–6 importing. 3–3. 9–6 rescheduling rules. 9–7 exporting definitions. 9–22. 9–6. 5–2 non-default terminators. 7–14 starting conditions. 9–5 saving to other instances. 15–31 Clean Temporary Files. 9–7 calendars. B–4 troubleshooting tools. 9–11 deleting. 9–11 Edit menu. 9–11 blocking dates. 9–18 Term Calendar Rule. 9–7 rescheduling rules. 9–10. 14–16 blocked dates. 9–19 date states. 9–5 Help menu. 14–18 Job Definition Reference List. 9–5 periods. 9–28 File menu. 9–6 exiting. 9–27 merging calendars. 9–28 exporting definitions to file. 9–9 Preferences menu. 9–18 saving. 9–18 See also calendars. 9–7 merging. 9–9 importing text files. 9–23 restoring definitions. 6–4. 11–26 components Index–3 . 9–15 setting dates. 4–3 chase. 9–24 conflicting dates. 9–27 importing definitions from file. 9–12 custom. 9–9 opening. 9–6 renaming. 14–17 defined. 9–5 opening new. 1–10 command jobs. 5–8 guidelines. 13–1 restoring definitions from backup file. 14–18 C Calendar Editor. 14–15 client machine. 9–18 CCI command line controls. 9–4 starting. 9–6 exporting. 3–19 status changes. 9–1 applying rules. 9–17 Calendar Selection dialog. 3–21 date range. 11–27 Chapter Organization. 14–16 exporting to text.

14–44 reloading. 10–2 delete job GUI. 14–25 database architecture. 14–23 identifying connected processes. 3–21 Database Mainteneance Command. 1–5 remote agent. 13–15 custom calendars. 14–31 synchronizing sybase. 14–41 dropping. 15–22 database overview. 14–44 general maintenance. A–12 currun report attribute. 1–5 Date and Time Attributes and Time Changes. 4–27 Date Changes. 7–24 Deleting a Job. 7–22 DB Poll Interval. setting GUI. A–15 notation. 10–7 deleting virtual machines. A–6 configure the AutoSys Machine. 3–21 config. 16–9 verifying connection. 8–12 deleting a real machine. 14–24 modifying. 14–31 synchronizing oracle. 14–25 default owner of job. 10–8 defining machines to AutoSys. 3–20 date range in calendars. 14–33 passwords. A–23 naming conventions. 14–23 data locking. GUI. 15–23 dbmaint. 15–10 defining a real machine. A–12 job scheduler interdepencies. 6–1 cross-platform limitations. 1–6 event server. 14–32 synchronizing. 14–22 connection to Monitor/Browser Editor. A–14 cross-platform dependencies. 14–25 displaying date and time. 10–7 defining a virtual machines. defined.event processor. 14–19 databases handling errors. 14–45 storage requirements. 14–21 tablespace error. 2–10 default port number. A–14 D data locking. 16–15 Database Maintenance Time.EXTERNAL. 4–27 date dependency. 1–16 Control Panel. 8–12 Deleting a Job Box. starting. 14–28 synchronizing Microsoft SQL. Oracle. 3–20 days to run job. A–5 contacting technical support. 14–40 improving oracle performance. creating the file.bat batch file. 1–7 conditions. A–13 notation. 13–18 daily maintenance. 9–19 date/time job dependencies. 14–33 improving sybase performance. overview. 10–10 dependencies cross-platform. 15–23 Index–4 User Guide . 14–30 dataserver. 2–9 re-creating. 14–33 improving performance.

2–19 Security Administration. 15–34 configuration parameters. 15–26 Restart Constant. 2–30 as-gvar class. 14–4 maintaining. 15–27 defined. 3–30 job status. 15–21 Number Errors. 7–12 example. 15–20 Shadow Ping Delay. 15–24 Network Machine List. 15–23 Start Poll Interval. 15–23 Enterprise Wide Logging Directory. 15–25 Essential Job Attributes. 2–23 as-list class. 15–20 EP Heartbeat Interval. 15–26 Kill Signals. 15–22 eoid. 15–22 EP Count. 15–28 Maximum Log Size. 2–21 as-view class. 2–31 Index–5 . 2–14 enterprise job scheduling. 15–28 Max Restart Wait. 3–26 disable security. 15–25 Event Transfer Wait Time. 15–30 Restart Factor. 2–29 asset level security. 15–29 Machine Method. 3–21 dependent jobs creating GUI. 4–4 eTrust access control. 15–6 EP Count. 2–18 security call logic. 15–22 Database Maintenance Time. A–5 Enterprise Wide Logging Directory. 14–1 E eAC. 2–20 policy manager. job date/time. 15–21 Unicenter Events. 3–20 exit code. 2–11 Edit Superuser. 2–31 as-machine class. 3–28 global variables. 15–23 DB Poll Interval. 2–22 security access. 2–19 resource classes. 2–26 as-owner class. 15–29 configuration parametersXInstance DB Drop Time. A–20 log file location. 2–17 access modes. 14–4 log file size. 15–34 Receive Remote Job Submissions. 15–23 Error Time Interval. 2–28 as-job class. 2–20 disable security. 15–20 EP Heartbeat Interval. 2–33 event processor AutoSys Broker Options. 15–27 Third Machine.dependency. 15–25 File System Threshold. 15–20 Database Maintenance Command. 15–27 Max Restart Trys. 2–23 as-calendar class. 15–23 Error Time Interval. 15–29 Shadow Machine. 15–12 controlling the event processor. 2–34 security enabled applications. 2–17 edit permissions. 2–20 dual event servers defined. 1–5 Dual-Event Server. 15–24 Job Heartbeat Interval. 15–34 AutoSys Agent Support. 2–25 as-control class. 1–6 log.

11–12 Machine/Instance tab. 14–12 See also event_demon. 15–14 Event Server screen. 15–31 Clean Temporary Files. 8–6 File Watcher Jobs. 15–33 event server defined. 14–26 See also database. 15–31 Event Serialization. 15–33 Options. 3–23 exporting calendars. 3–5 basic job definition. 1–5 overview. 16–4 Sybase Deadlock. 9–28. A–5 troubleshooting. 15–32 restarting. 15–13 Event Transfer Wait Time. 15–31 Remote Profile Logging. 14–20 returning after rollback. 1–11 cancelling. A–8 global mode. 3–26 monitor/report definition. 16–9 Event Processor Defined. 2–15 execute permissions. 14–20 Event Server Configuration Parameters. 14–16 Event Processor Screen. with. 1–6 shadow rollover. 1–8 exclusive condition. 16–5 using dual server mode. 1–5 See also dual event servers. 13–18 reports. defining in JIL. 11–16 force starting jobs. 14–1. 3–29 FALSE. 11–27. 15–19 Event Serialization. 15–47 examples calendar rescheduling rule. defining in JIL. 15–24 File Watcher Creating Job. 3–28 maximum for success. 11–15 Names tab. 1–5 Server is Down. 10–13 FORCE_STARTJOB. 14–45 restoring primary. 1–6 events about. 13–7 monitors. 14–7 stopping. 14–5 status. 15–31 Append stdout/stderr. 14–8 starting. 3–30 File System Threshold. 11–13 Status tab.monitoring. 9–23 job dependencies. 15–32 Chase On Startup. 15–33 Global Auto Hold. 3–11 creating. 11–30 F FAILURE status. 11–14 using. 14–9 running in test mode. 14–27 rollover recovery. 11–4. 15–25 event_demon See also event processor. 14–44. 16–10 stoping. 3–14 FALSE. 11–43 Index–6 User Guide . 2–15 Exec Superuser. 15–18 Example Remote Authentication.EXE. 14–3 Multiple EP Restart. 3–27 exec superuser.EXE. 7–10 Filter Editor. 13–18 system architecture. 2–11 exit codes batch files. 3–30 job dependencies.

G General Dialog. 1–3 defining monitor. 6–1 Job Editor. 1–3 introduction. 6–4 Calendar Editor. 8–7 JIL Index–7 . 3–30 restoring definitions. 6–1 defined. 6–3 Alarm Manager. 11–37 Instance screen. 13–18 JIL Create a Job Definition. 14–18 setting in the Send Event Tool. 8–4 JIL Running. 6–3 Control Panel. 7–26 removing user preferences. 4–2 JIL Syntax Rules. 1–6 Command Job Creating. 1–10 J JIL. 6–1 See also GUI. 3–13 inherit. 8–6 JIL Command Job Dependent Command Job. 13–18 defining report. setting. 3–19 initautosys command. job’s starting conditions. 15–31 global variables backing up definitions. 15–8 instances of AutoSys. 11–28 Graphical User Interface introduction. 8–5 JIL H JIL high availability dual event servers. 8–4 JIL Submitting Job Definitions. 6–4 time dependencies. 6–4 Alarm Sentry. 2–11 Global Auto Hold. 11–35 gid. 8–5 Command Job File Watcher. 6–3 Scheduler Console. 6–4 Job Editor menu bar. 9–27. 7–18 I importing calendars. ID. 2–11 GUI alarm color setting. 6–1 group ID. 14–17 job dependencies. 14–18 INACTIVE status. 8–2 JIL Sub-commands. 8–1 defined. 6–4 one-time job overrides. 7–3 Monitor/Browser Editor. 1–5 shadow event processor. 15–6 Instance. 6–4 connect to database.

7–10 creating jobs with dependencies. 7–18 Job Editor Using Create a Job Definition. 4–1 Job Attributes and Load Balancing and Queuing. 8–12 Deleting Box. 8–9 Changing. 7–1 creating Box Jobs. 4–12 Job Attributes Optional Command. 7–4 saving jobs. 1–12 See also JIL. 4–4 Job Attributes Common to All Job Types. 7–26 opening definitions. 8–9 JIL Changing a Job. 8–7 File Watcher. 8–13 Running JIL. 4–8 Job Attributes Optional. 4–2 Job Heartbeat Interval. 11–18 Job Detail Report. 8–12 Dependent Command. 4–4 Job Attributes Common. 8–1 Index–8 User Guide . 6–4. 1–12 Job Information Language (JIL). 7–4 deleting jobs. 7–9 saving job as. 8–6 Overrides. 8–13 JIL Example Script. 7–12 deleting definition. 8–4 Time Dependencies. 7–16 one-time overrides. 8–14 Submitting Defenitions. 4–5 Job Attributes File Watcher. 4–8 Job Attributes Box. 7–22 setting time dependencies. 15–26 Job Information Language. 8–5 Setting Overrides. 4–1. 4–18 Job Attributes Optional File Watcher. 8–10 JIL Deleting a Job. 10– 4 Job Definition Reference List. 4–9 Job Attributes Optional Common Job Starting. 8–12 JIL Job Overrides. 7–24 menu bar. 7–3 opening new job. 8–5 Deleting. 7–3 Owner field. 7–14 creating Command Jobs. 7–8 creating File Watcher Jobs. 11–32 Job Editor. 9–7 Job Dependencies dialog. 4–26 Job Attributes and Definitions. 8–15 Job Box. 8–11 Job Attributes. 7–3 modifying job definitions. 4–25 Job Attributes Optional Box Job. 4–9 Job Attributes Optional Common General. 7–3 setting days to run. 8–10 Creating Simple Command.Creating a Box.

7–22 defined. 11–4. 3–30 job status.GUI. 3–21 job_filter monitor/report attribute. 7–14 Command Jobs . 14–18 run number. 7–10 custom calendars. 11–4. 11–4. 7–14 defined. 16–2 date/time dependencies setting in GUI. 7–16 command jobs defined. 2–10 permissions on NT.GUI. 3–11 deleting GUI. 11–26.GUI. 3–20 types. 7–8 File Watcher Jobs . 3–12 command. 2–11 exit code. 14–16 basic job information. 7–26 owner default.GUI. 2–11 execute permssions. 3–15 QUE_WAIT. 3–11 File Watcher. 3–21 cycles of processing. 7–18 days to run. as job dependency. 11–13 Job Name field. 11–27. 3–2 Box Jobs. 11–8 names and user IDs. 11–44 JOB_ON_ICE. 3–31 saving definitions to backup file. 7–16 starting conditions. 3–3 calendar reference list. 3–32 definition Box. 3–14 RESTART. 11–44 jobs backing up definitions. 7–10 defined. 11–27. 11–4. 3–13 time/date dependencies. 3–13 status ACTIVATED. 3–3 Command Jobs creating . 3–5 list in Scheduler Console. 3–13 TERMINATED. 3–28 global variables. 3–13 FAILURE. 3–14 ON_ICE. 3–27 ON_HOLD. 11–13 job status. 7–12 exit codes. 11–26. A–17 overrides GUI.job level security. 7–8 creating Box Jobs . 9–7 changing . 3–28 File Watcher creating . 7–24 dependencies creating with GUI. 3–13 managing. 3–14 INACTIVE. setting. 14–16 selection list. A–17 on agent managed machines. 1–2 defining in AutoSys. 2–10 Job Selection dialog Box Levels field. 3–19 states. 13–13 JOB_OFF_HOLD. 2–13 restoring definitions from backup file. 3–2 Index–9 . 3–13 SUCCESS.GUI. 11–44 JOB_ON_HOLD.GUI. 5–1 creating . 3–14 STARTING. 3–14 status codes. 3–21 time GUI.GUI. 7–18 edit permissions. 11–44 JOB_OFF_ICE.

15–28 maximum exit code for success. 15–21 Notification Mechanism. remote agent. A–15 Network Machine List. 14–18 saving definitions to backup file. 14–14 maintenance backing up definitions calendar definitions. 15–33 Multiple Machine Queues. 14–17 client. 11–27. 13–1 Alarm field. 14–17 clean_files. 14–17 monitor and browser definitions. 14–17 defined. 13–15 Events After Date/Time field. 13–14 monitors. 11–4. 16–2. 13–1 about. 15–29 KILLJOB. 15–28 Max Restart Wait. 14–17 job definitions. A–20 log files. cross-platform. 1–10 Machine Definitions. 16–17 Monitor/Browser Editor. 14–18 managing job status. 15–27 maintenace chase. 13–14 backing up definitions. 14–17 server. 10–18 M machine backing up definitions. 13–18 restoring definitions from backup file. A–17 naming conventions. 3–27 Max Restart Trys. 2–12 restoring definitions from backup file. 14–14 commands. 15–10 log. 13–2 alarm_verif. 10–11 Load Units and Virtual machines. 14–31 Microsoft SQL Server. 13–11 Current Run Only field. 13–13 naming. A–23 load balancing. 13–12 All Events field. 13–17. 3–23 L limitations. 13–14 Multiple EP Restart. 14–18 sound. 16–21 Maximum Log Size. 15–35 Index–10 User Guide . 13–14 All Change Status Events field. 13–15 Job Filter field. 14–16 machine definitions. 13–5 Sound field. 13–12 Alarm Verification Required field. 1–10 permissions edit and execute.K Kill Signals. 14–16 global variables. 13–7. 10–6 Machine Method. 11–43 restoring definitions. 13–1 defining. 15–24 Microsoft SQL synchronizing databases. 14–15 N names. 6–4. 10–18 Local Agent Logging Directory.

3–15 one-time job overrides. 16–17 Event Processor authentication. 2–9 security. 2–12 types. 2–11 user. 10–1 remote agent defined. 15–37 Event Processor High Availability. 2–11 Index–11 . 14–10 stopping. 15–36 ntrys. 15–37 defined. 2–10 using umask.Notifications screen Configuration Parameters. 10–15 R real machines. 16–9 troubleshooting. 6–3 profile script. 2–13 policy manager. 2–17 P passwords autosys user. 2–12 machine. 2–9 database. 1–7 Local Agent Logging Directory. 16–21 maintaining. 14–33 synchronizing databases. 3–15 ON_ICE. 2–19 port number. 15–37 Database Problem. 15–10 preferences alarm color. 10–13 Queuing with Priority. 6–3 retry count. 3–3 O ON_HOLD. 16–3 overrides job GUI. 14–11 TCP/IP. ON_ICE. 14–31 Oracle. 3–14 ON_HOLD vs. 2–11 execute. 15–37 Event processor Shutdown. 15–10 Remote Agent database connectivity. 6–3 removing user. 15–26 granting. 3–14 queuing and simple load limiting. 16–2 tablespace error. 15–38 Event Processor Rollover. 15–10 log name assigning. 10–14 queuing jobs. 15–37 Database Rolloever. 2–10 Q QUE_WAIT status. 2–10 Windows NT. 7–26 owner default. default. 7–26 oracle improving database performance. 14–10 port number. 2–9 permissions edit. 15–10 starting. 3–31 Number Errors.

11–18 Job Detail Report. 14–18 global variables (using autorep). 11–23 Queue Name field. 13–5 reports. 2–8 S Scheduler Console. 14–18 machine definitions (using autorep). 11–23 Try Count field. 2–9 user. 13–9 reports all_status. 2–16 Rule Specification region. 14–18 monitor and browser definitions. 11–23 Run Machine field. 13–6 run number. 3–32 RUNNING status. 11–22 Instance field. 11–22 Next Start field. 15–10 remote authentication Event Processor. 11–43 cancelling a sent event. 3–14 restoring calendar definitions. 11–30 Control Area. 11–14 filters. 11–22 Starting Conditions field. 15–32 reports naming. 13–1 about. 11–23 Priority field. 13–12 reports defining. 14–18 restoring definitions. 11–13 Names Tab. 11–22 Job Name field. 11–22 End Time field. 3–13 ruserok. 11–22 Description field. 15–30 Restart Factor. 11–23 Predecessor and Successor Jobs fields. 2–8 Remote Agent screen defining configuration parameters. 13–18 rescheduling rules. 2–8 Remote Authentication. 11–8 Filter Editor. 6–4. 11–13 Status tab. 9–22 resource classes. 11–22 Status field. 11–22 Run Time field. 13–17 reports defining. 11–11 Job Dependencies dialog. 14–18 restricting access to jobs. 9–18 Run MonBro button. 11–22 Start Time field. 16–15 user authentication. 11–12 Machine/Instance tab. 11–20 Command field. 3–31 Run Status Tool. 11–22 run_num/ntry defined. 2–22 Restart Constant.troubleshooting. 15–29 RESTART status. 14–18 job definitions (using autorep). 15–46 Remote Profile Logging. 13–1 reports defining. 13–3 defined. 11–15 Names tab. 11–1 buttons. 11–32 Index–12 User Guide . 11–11. 13–7 reports defining. 11–22 Exit Code field.

2–13 security enabled applications. 2–11 security access. 11–8 menu bar. 11–8 time perspective. 11–24 Send button. 11–26 SEND_SIGNAL. 2–10 user and database administrator passwords. 11–27 Job On Hold. 2–9 user authentication. 11–28 Set Global. 2–7 umask. 2–8 restricting access to jobs. 11–26 AUTOSERV instance. 2–1 permission types. 2–14 superusers AutoSys. 2–13 native. 2–34 database field verification. 2–10 user types. 11–28 opening. 11–28 Force Start Job. 15–48 Configuration Parameters. 11–24 Send button. 2–14 system level. 11–29 Comment. 11–26 Stop Demon. 11–27 Change Status. 2–4 events sent by users. 11–28 Start Job. 11–36 viewing job dependencies. 2–17 remote agent authentication. 11–18 Run Status Tool. 11–18 security. 2–12 job definition encryption. 2–7 Remote Agent. 2–10 job ownership. 11–27 Close button. 11–23 Tools menu. 2–2 overview. 2–7 event processor authentication. 11–27 opening. 11–38 refresh interval setting for. 2–16 security control. 11–29 Send Signal. 11–44 Tools Dependent Jobs. 11–17 user defined commands. 2–7 job level. 11–36 User Defined Reports. 11–34 General. 2–9 events sent by the event processor. 2–13 superuser privileges. 11–41 summary area. 11–26 Job On Ice. 11–27 Job Off Hold. 2–19 security control. 11–44 User Defined Commands. 11–42 AutoRefresh. 11–26 AUTOSERV instance. 11–35 Reports Job Detail Report. 11–23. 2–33 Security Screen. 2–10 job permissions and windows.job list. 11–35 Summary Area Layout. 11–26 Comment field. 2–1 call logic. 11–39 Time Perspective. 2–11 preventing unauthorized access. 11–29 sorting specified jobs. 11–28 Index–13 . 2–8 user permissions. 11–3 Preferences Action Area Layout. 11–29 Comment field. 11–29 cancelling an event. 11–20 Send Event Tool. 11–23. 11–27 Kill Job. 11–30 Change Priority. 11–32 Send Event Tool. 15–46 Send Event Tool. 15–49 Defined. 11–26 Job Off Ice. 2–2 granting permissions. 11–29 Close button.

2–15 server instance. 13–12 starting. 15–23 Subsets—Individual queues. 11–39 Specifying Relative Process Power. 14–44 reloading the database. 14–37 configuring a backup server. 14–36 dropping a damaged database. 3–14 ON_ICE. 14–43 re-creating the database. 14–33 maintaining bundled SQL servers. 3–13 status job ACTIVATED. 3–13 STARTING. 3–14 RUNNING. 13–12 restart. 10–17 sound monitor attribute. 3–21 STOP_DEMON. 14–42 default user. 3–22 FAILURE. 15–27 states job. 3–21 STARTING status. 3–13 as job dependency. 15–52 Defined. 13–12 success. 3–14 RESTART. 1–5 server machine. 1–6 Shadow Machine. 14–35 recovering a bundled database. 15–50 SET_GLOBAL. 14–45 starting. 3–14 INACTIVE. 15–43 Configuration Parameters. 13–14 Sounds Screen. 14–39 architecture. 4–31 starting conditions. 3–23 SUCCESS status. 2–15 sybase accessing. unprocessed. 3–13 superusers. 11–26 Shadow Ping Delay. 3–13 Index–14 User Guide . 4–29. 3–13 STARTJOB. 3–19. 14–36 changing system administrator password. 3–15 QUE_WAIT. 1–10 Services Screen Components. 10–3 Summary Area Layout Dialog. 13–12 running. 3–13 ON_HOLD. 14–44 environment. 14–41 bundeled recovery. 13–12 terminated. 14–37 success maximum exit code.sendevent command. 15–44 specifying machine load. 13–12 processed vs. 10–4 Spring Time Change. 14–35 improving database performance. 3–13 See also status. 2–14 Edit Superuser defined. 11–26. 15–20 SUCCESS. 14–35 backing up to a file. 14–41 bundled database users. 11–3. 14–43 bundeled backup. 3–18 using in job dependencies. 11–28 shadow event processor defined. 13–12 monitor/report failure. 11–43 Startjob Poll Interval. 3–13 TERMINATED. 2–14 exec superuser defined. 3–14 tracking changes.

16–3 troubleshooting tools CCI. 16–3 Remote Agent. A–20 troubleshooting. 3–14 test mode output file. 14–38 stopping event processor. 15–10 AutoInstWideAppend.stopping. 14–28 Syntax Rules. B–2 troubleshooting tools nslookup. 15–21 Time Changes. 16–3. 8–11 troubleshooting tools netstat. 15–23 Index–15 . 15–38 using. 15–32 AutoRemoteDir. 15–34 Check_Heartbeat. 15–17 DBMaintCmd. B–3 troubleshooting tools ccinet. 15–37 DBAlarmReconnect. 16–1 Event Processor. 3–20 setting GUI. 15–31 DB_PROBLEMt. 15–10 technical support. 15–22 DBMaintTime. 14–44 synchronizing databases. 11–44 trace information. 16–9 Event Servers. 14–12 The Time Change. 4–29 The Time Change Fall Time Change. 8–11 Setting Additional Features. B–2 troubleshooting tools traceroute and tracert. 4–31 Third Machine. 15–26 CleanTmpFiles. B–3 U uid. 16–15 Sybase. 16–18 Oracle. 8–2 System Information screen Configuration Parameters. 15–29 UNIX Parameter #AutoRemPort. 2–11 Unicenter Events. 15–17 DBEventReconnect. 16–4 Microsoft SQL Server. 4–27 The Time Change AutoSys Behavior. 7–18 Time Dependencies Setting. 1–16 Term Calendar Rule dialog. 15–16 DBLibWaitTime. B–1 T TCP/IP. 14–30 synchronizing databases. 15–22 AutoSysAgentSupport. 4–27 time dependencies overview. remote agent. B–1 troubleshooting tools ping. 4–28 The Time Change Spring Time Change. 15–40 defined. 15–39 time perspective in the Scheduler Console. 14–13 running in. 9–17 TERMINATED status.

2–11 user IDs. 11–36 User Defined Load Balancing. 10–5 utilities provided with AutoSys. 11–38 user ID. 10–19 User Defined Reports dialog. 15–21 EDNumErrors. A–22 User Defined Buttons dialog.DB-ROLLOVER. 15–14 EvtTransferWaitTime. 2–11 Using Services Screen. 15–25 EDMachine. 15–28 RemoteProFiles. 15–53 using max_load and factor. 1–12 V virtual machines. 15–26 EP_HIGH_AVAIL. 15–37 EventServer. 15–37 EDErrTimeInt. 15–37 EP_SHUTDOWN. 15–29 MachineMethod. 15–25 FileSystemThreshold. 15–38 EP_ROLLOVER. 15–21 XInstanceDBDropTimer. 2–13 X Xinstance DB Drop Time. 2–11 owner. 15–27 MaxRestartTrys. 10–2 W Windows NT job permissions on. 15–24 KillSignals. A–17 user types group. 15–32 RestartConstant. 2–11 world. 15–30 RestartFactor. 15–28 MaxRestartWait. 15–27 unsupported attributes. 15–27 Index–16 User Guide . 15–29 ThirdMachine.