Unicenter CA-Scheduler Job Management for VSE … CA-Scheduler Job Management for VSE . This documentation and related computer software program (hereinafter referred to as the “Documentation”)

User Guide r7.3

K01171-1E

Unicenter CA-Scheduler Job Management for VSE

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.

2005 Computer Associates International, Inc.

All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Contents

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.1 Beginning with the Basics . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21.2 How Unicenter CA-Scheduler Works . . . . . . . . . . . . . . . . . . . . 1-71.3 Additional Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-111.4 Summing Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-14

Chapter 2. Startup Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12.1 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

2.1.1 Logging On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22.1.2 Using the Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32.1.3 Getting Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-42.1.4 Logging Off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

2.2 Maintaining Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72.2.1 Defining Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-82.2.2 Updating Station Records . . . . . . . . . . . . . . . . . . . . . . . 2-102.2.3 Deleting Workstations . . . . . . . . . . . . . . . . . . . . . . . . . 2-132.2.4 Displaying Workstations . . . . . . . . . . . . . . . . . . . . . . . . 2-152.2.5 Summary of Station Maintenance . . . . . . . . . . . . . . . . . . 2-18

2.3 Maintaining User Records . . . . . . . . . . . . . . . . . . . . . . . . . 2-202.3.1 User Authority Levels . . . . . . . . . . . . . . . . . . . . . . . . . 2-202.3.2 The Role of Passwords . . . . . . . . . . . . . . . . . . . . . . . . . 2-212.3.3 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-212.3.4 Defining Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-232.3.5 Updating User Records . . . . . . . . . . . . . . . . . . . . . . . . 2-262.3.6 Deleting User Records . . . . . . . . . . . . . . . . . . . . . . . . . 2-292.3.7 Displaying User Records . . . . . . . . . . . . . . . . . . . . . . . . 2-302.3.8 Summary of User Maintenance . . . . . . . . . . . . . . . . . . . . 2-34

Chapter 3. Maintaining the Database . . . . . . . . . . . . . . . . . . . . . 3-13.1 Defining Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

3.1.1 Planning Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23.1.2 Defining a Schedule Base Record . . . . . . . . . . . . . . . . . . . 3-33.1.3 Checking Default Values for Schedule Base Records . . . . . . . . 3-73.1.4 Learning the Basics About a Schedule Record . . . . . . . . . . . . 3-9

3.1.4.1 When Will this Schedule Be Selected? . . . . . . . . . . . . . 3-103.1.4.2 When Will a Schedule's Jobs Actually Run? . . . . . . . . . 3-113.1.4.3 What JCL Does Unicenter CA-Scheduler Submit for These

Jobs? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-143.1.4.4 Which CPU Should Control These Jobs? . . . . . . . . . . . 3-14

Contents iii

3.1.4.5 What Schedule Fields Are Used for Simulation? . . . . . . . 3-153.1.4.6 What General Users Can Update this Schedule Record? . . 3-163.1.4.7 What Happens When Schedules Run Late? . . . . . . . . . . 3-163.1.4.8 Creating Optional Schedule Records? . . . . . . . . . . . . . 3-17

3.2 Defining Optional Schedule Records . . . . . . . . . . . . . . . . . . . 3-193.2.1 Defining a Schedule Criteria Record . . . . . . . . . . . . . . . . . 3-213.2.2 Defining a Schedule Reason Code Record . . . . . . . . . . . . . 3-243.2.3 Defining a Schedule Information Record . . . . . . . . . . . . . . 3-263.2.4 Defining a Schedule Message Record . . . . . . . . . . . . . . . . 3-27

3.3 Copying Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-293.4 Displaying Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-323.5 Deleting Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-363.6 Analyzing Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-403.7 Automatic Console Replies for Schedules . . . . . . . . . . . . . . . . 3-44

3.7.1.1 To ADD a New Reply . . . . . . . . . . . . . . . . . . . . . . 3-453.7.1.2 ALTer or REPlace an Auto-Reply Record . . . . . . . . . . . 3-473.7.1.3 To DELete an Auto-Reply Record . . . . . . . . . . . . . . . 3-49

3.8 Summary of Schedule Maintenance . . . . . . . . . . . . . . . . . . . . 3-513.9 Defining Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-53

3.9.1 Defining a Job Base Record . . . . . . . . . . . . . . . . . . . . . . 3-533.9.2 Checking Default Values for Job Base Records . . . . . . . . . . 3-563.9.3 Learning the Basics About a Job Record . . . . . . . . . . . . . . 3-58

3.9.3.1 Which Users Can Work with Job Records? . . . . . . . . . . 3-583.9.3.2 When Will Jobs Be Selected? . . . . . . . . . . . . . . . . . . . 3-583.9.3.3 When Will Jobs Actually Run? . . . . . . . . . . . . . . . . . 3-593.9.3.4 Does This Job Record Describe a Job Performed on the CPU? 3-643.9.3.5 What JCL Does Unicenter CA-Scheduler Submit for CPU

Jobs? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-653.9.3.6 On Which CPU Should Jobs Be Run? . . . . . . . . . . . . . 3-663.9.3.7 Once a Job Starts, How Can You Intervene? . . . . . . . . . 3-683.9.3.8 What Happens When Jobs Don't End Successfully? . . . . . 3-683.9.3.9 How Do You Phase Unicenter CA-Scheduler into

Production? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-703.9.3.10 What Job Fields are Used for Simulation? . . . . . . . . . . 3-713.9.3.11 How and When Can You Display Documentation

Automatically? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-723.9.3.12 What Happens When Jobs Run Late? . . . . . . . . . . . . . 3-723.9.3.13 How Do You Create Optional Job Records? . . . . . . . . . 3-743.9.3.14 Copying Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-75

3.9.4 Defining Optional Job Records . . . . . . . . . . . . . . . . . . . . 3-773.9.4.1 Defining a Job Criteria Record . . . . . . . . . . . . . . . . . 3-773.9.4.2 Defining a Job's Reason Code Record . . . . . . . . . . . . . 3-793.9.4.3 Defining a Job Information Record . . . . . . . . . . . . . . . 3-823.9.4.4 Creating a Job Message Record . . . . . . . . . . . . . . . . . 3-833.9.4.5 Defining a Job Resource Record . . . . . . . . . . . . . . . . . 3-853.9.4.6 Defining Job Node Records . . . . . . . . . . . . . . . . . . . 3-89

3.10 Displaying and Updating a Job Definition . . . . . . . . . . . . . . . 3-913.11 Deleting Job Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-973.12 Analyzing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1013.13 Automatic Console Replies for Jobs . . . . . . . . . . . . . . . . . . . 3-104

3.13.1.1 To ADD a New Reply . . . . . . . . . . . . . . . . . . . . . . 3-105

iv Unicenter CA-Scheduler User Guide

3.13.1.2 ALTer or REPlace an Auto-Reply Record . . . . . . . . . . 3-1073.13.1.3 To DELete an Auto-Reply Record . . . . . . . . . . . . . . . 3-109

3.14 Summary of Job Maintenance . . . . . . . . . . . . . . . . . . . . . . . 3-111

Chapter 4. Online Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.1 Online Monitoring Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24.2 Displaying Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

4.2.1 Displaying a Specific Queue . . . . . . . . . . . . . . . . . . . . . . 4-54.2.2 Displaying Status for Specific Schedules and Jobs . . . . . . . . . 4-94.2.3 Displaying Status in Sequence . . . . . . . . . . . . . . . . . . . . 4-104.2.4 Different Types of Displays . . . . . . . . . . . . . . . . . . . . . . 4-11

4.2.4.1 Default Status Display . . . . . . . . . . . . . . . . . . . . . . 4-124.2.4.2 Sample Time Status Display . . . . . . . . . . . . . . . . . . . 4-134.2.4.3 Sample History Status Display . . . . . . . . . . . . . . . . . 4-144.2.4.4 Sample Schedule Summary Status Display . . . . . . . . . . 4-15

4.2.5 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-164.2.6 The Meaning of Status . . . . . . . . . . . . . . . . . . . . . . . . . 4-17

4.3 Handling Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-234.3.1 Displaying Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 4-234.3.2 Sending Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-23

4.4 Handling Predecessor Conditions . . . . . . . . . . . . . . . . . . . . . 4-254.4.1 Posting Predecessors . . . . . . . . . . . . . . . . . . . . . . . . . . 4-254.4.2 Unposting Predecessors . . . . . . . . . . . . . . . . . . . . . . . . 4-25

4.5 Handling Global Parameters . . . . . . . . . . . . . . . . . . . . . . . . 4-274.5.1 Displaying Global Parameters . . . . . . . . . . . . . . . . . . . . 4-274.5.2 Setting Global Parameters . . . . . . . . . . . . . . . . . . . . . . . 4-28

4.6 Displaying Date and Autoscan Information . . . . . . . . . . . . . . . 4-294.7 Displaying Data Set Mask Names . . . . . . . . . . . . . . . . . . . . . 4-304.8 Displaying Network Information . . . . . . . . . . . . . . . . . . . . . 4-314.9 Controlling Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-324.10 Controlling Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34

4.10.1 Running Jobs With The ADD Command . . . . . . . . . . . . . 4-364.11 Summing Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39

Chapter 5. Criteria Language . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15.1 Criteria Vocabulary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

5.1.1 Reserved Words for Use in Boolean Expressions . . . . . . . . . . 5-35.1.2 Reserved Words Used for Selection . . . . . . . . . . . . . . . . . . 5-35.1.3 Reserved Words for Use in Predecessors . . . . . . . . . . . . . . . 5-55.1.4 Combining Selection and Predecessor Criteria Vocabulary . . . . 5-65.1.5 Using Multiple Conditions with ANDs and ORs . . . . . . . . . . 5-75.1.6 Affect of NOT Condition on Predecessors . . . . . . . . . . . . . . 5-85.1.7 Recommended Method for Defining Selection Criteria . . . . . . . 5-8

5.2 Calendar Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105.2.1 Gregorian Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105.2.2 Datetables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11

5.2.2.1 Workday Keywords . . . . . . . . . . . . . . . . . . . . . . . . 5-125.2.2.2 Accounting-Period Keywords . . . . . . . . . . . . . . . . . . 5-125.2.2.3 Summary of Datetables . . . . . . . . . . . . . . . . . . . . . . 5-155.2.2.4 Date Translation Table Report . . . . . . . . . . . . . . . . . . 5-15

Contents v

5.2.3 Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-175.2.3.1 Step 1: Define the prototype calendar . . . . . . . . . . . . . 5-175.2.3.2 Step 2: Define daily, weekly and monthly calendars . . . . 5-19

5.3 Some Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-205.4 What Is Wrong with These Examples? . . . . . . . . . . . . . . . . . . 5-255.5 Summing Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29

Chapter 6. Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.1 Commonly Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

6.1.1 Startup Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-26.1.1.1 When Should Autoscan Be Performed? . . . . . . . . . . . . . 6-36.1.1.2 What Is the General Standard for Numbering Stations? . . . 6-36.1.1.3 Should I Use Datetables or Calendars? . . . . . . . . . . . . . 6-46.1.1.4 When Should I Define a New Datetable Versus a New Cycle

in an Existing Datetable? . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.1.2 Maintaining the Database . . . . . . . . . . . . . . . . . . . . . . . . 6-4

6.1.2.1 How Should I Organize My Schedules? . . . . . . . . . . . . . 6-46.1.2.2 Is There a Fast Way to Add Data to the Database? . . . . . . 6-56.1.2.3 When Should a Job Be Staged? . . . . . . . . . . . . . . . . . . 6-56.1.2.4 When Is a Job Submitted? . . . . . . . . . . . . . . . . . . . . . 6-76.1.2.5 What Are Global Parameters and When Are They Used? . . 6-76.1.2.6 How Can I Run a Job Like an Edit Check Repeatedly until Its

Output Is Correct? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86.1.2.7 How and When Can I Display Documentation Automatically? 6-96.1.2.8 What Are My Options When a Job Abends? . . . . . . . . . 6-10

6.1.3 Analyzing the Database . . . . . . . . . . . . . . . . . . . . . . . . 6-106.1.3.1 How Can I Prevent Predecessor Loops? . . . . . . . . . . . . 6-106.1.3.2 When Should I Run Forecasts? . . . . . . . . . . . . . . . . . 6-116.1.3.3 When Should I Run Simulation? . . . . . . . . . . . . . . . . 6-116.1.3.4 How Do I Plan when To Run a New Application? . . . . . 6-126.1.3.5 How Do I Verify a New Application? . . . . . . . . . . . . . 6-126.1.3.6 Is There a Way that I Can Create My Own Reports? . . . . 6-14

6.1.4 Daily Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-156.1.4.1 From Where Can I Issue Unicenter CA-Scheduler Operator

Commands? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-156.1.4.2 What Is the Difference Between FORCE, SUBMIT, RERUN,

RUN, ADD, REQUEST, and SREQ? . . . . . . . . . . . . . . . . . . 6-166.1.4.3 Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-186.1.4.4 When Is the PRED Flag Reset? . . . . . . . . . . . . . . . . . 6-186.1.4.5 What Happens If There Was a System Crash? . . . . . . . . 6-18

6.2 Pitfalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-206.2.1 Using Operator Commands on the Status Display Panel . . . . 6-206.2.2 Cancelling and Purging a Job . . . . . . . . . . . . . . . . . . . . . 6-206.2.3 Changing Criteria on Selected Jobs . . . . . . . . . . . . . . . . . 6-206.2.4 Backlogging Over Two Autoscans . . . . . . . . . . . . . . . . . . 6-216.2.5 Resetting Global Parameters . . . . . . . . . . . . . . . . . . . . . 6-21

Chapter 7. Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17.1 On-Request Schedules and Jobs . . . . . . . . . . . . . . . . . . . . . . . 7-2

7.1.1 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-27.1.2 Criteria Language Subtleties . . . . . . . . . . . . . . . . . . . . . . 7-3

vi Unicenter CA-Scheduler User Guide

7.1.2.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37.1.2.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37.1.2.3 Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37.1.2.4 Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37.1.2.5 Example 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.1.2.6 Example 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47.1.2.7 Example 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57.1.2.8 Example 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-57.1.2.9 Example 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-67.1.2.10 Example 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

7.2 Backlogged Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-87.2.1.1 In Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

7.3 Issuing Online Commands in Batch . . . . . . . . . . . . . . . . . . . . 7-107.3.1 Transaction Format . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-107.3.2 Status Checking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-117.3.3 Some Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13

7.3.3.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-137.3.3.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14

7.4 Restart/Recovery of Scheduled Jobs . . . . . . . . . . . . . . . . . . . 7-167.4.1 Inquiring About Jobs to Be Recovered . . . . . . . . . . . . . . . 7-167.4.2 Automatic Recovery Options . . . . . . . . . . . . . . . . . . . . . 7-177.4.3 Unicenter CA-Driver Considerations . . . . . . . . . . . . . . . . 7-18

7.5 Multiple CPU Considerations . . . . . . . . . . . . . . . . . . . . . . . 7-197.5.1 Installation Considerations . . . . . . . . . . . . . . . . . . . . . . 7-207.5.2 Control Of Jobs in a Multi-CPU Environment . . . . . . . . . . . 7-207.5.3 Recovery Of Jobs in a Multi-CPU Environment . . . . . . . . . . 7-237.5.4 Non-Shared POWER Considerations . . . . . . . . . . . . . . . . 7-25

7.6 NJE Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-267.6.1 Cross-Node Job Submission . . . . . . . . . . . . . . . . . . . . . . 7-267.6.2 Cross-Node Dependencies . . . . . . . . . . . . . . . . . . . . . . . 7-28

7.6.2.1 NJE Job Dependencies . . . . . . . . . . . . . . . . . . . . . . 7-297.6.3 Cross-Node Command Processing . . . . . . . . . . . . . . . . . . 7-297.6.4 Installation Considerations . . . . . . . . . . . . . . . . . . . . . . 7-31

7.6.4.1 CAIJGEN Macro . . . . . . . . . . . . . . . . . . . . . . . . . . 7-317.6.4.2 VTAM Communications . . . . . . . . . . . . . . . . . . . . . 7-31

7.6.5 Control Commands for Checking The NJE Network . . . . . . . 7-327.7 Summing Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-34

7.7.1 On-Request Schedules and Jobs . . . . . . . . . . . . . . . . . . . 7-347.7.2 Backlogged Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-347.7.3 Online Commands in Batch . . . . . . . . . . . . . . . . . . . . . . 7-347.7.4 Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-357.7.5 Multi-CPU Considerations . . . . . . . . . . . . . . . . . . . . . . . 7-357.7.6 NJE Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-9

Contents vii

Chapter 1. Introduction

Unicenter CA-Scheduler Job Management for VSE (UnicenterCA-Scheduler) is designed to automate production control and overseeoperations at VSE sites. To accomplish this, Unicenter CA-Scheduler centralizesall scheduling information into a single database. As you begin implementingUnicenter CA-Scheduler, focus on scheduling CPU processing first. However,this database can ultimately control every production task in the data center,from data preparation through output delivery.

Unicenter CA-Scheduler automates production control by scanning thedatabase to identify each day's workload. It oversees operations by

■ Ensuring that tasks are performed in proper sequence■ Allowing you to monitor the work flow online■ Permitting you to adjust the day's workload as needed

Because Unicenter CA-Scheduler is so versatile, it allows you to choose onlythose features and options appropriate to your site.

This chapter provides a high-level introduction to the terminology, keyconcepts, and basic capabilities of Unicenter CA-Scheduler. Succeeding topicsexpand on these topics in more detail.

Chapter 1. Introduction 1-1

1.1 Beginning with the Basics


Ironically, job scheduling for multi-million-dollar computers is often handledwith an in-box or a chalk board. With Unicenter CA-Scheduler, you can usethe computer you already have to automate production.

Unicenter CA-Scheduler looks at job processing the same way you do: jobsstart and end with the user and a job is not done until the output is delivered.If you trace the path of a job through your data center, it passes throughdifferent areas before and after CPU processing:

Unicenter CA-Scheduler calls each of these areas a workstation and has youassign numbers to them. Since all sites have JCL setup and CPU processing,Unicenter CA-Scheduler assigns those station numbers automatically (stations39 and 40). Notice that pre-CPU station numbers are in ascending order up to39. Post-CPU stations are also numbered sequentially and can range from41-99. This manual will reference the station numbers shown in the diagrampreceding.

Unicenter CA-Scheduler has you number workstations in ascending order for areason: that sequence tells Unicenter CA-Scheduler the logical flow of workthrough your data center. Not all jobs are processed at every workstation:some only run on the CPU, but if a job is scheduled at stations 39 and 40,Unicenter CA-Scheduler knows that JCL setup should finish at station 39before the job can be submitted to the CPU (station 40). To prevent mistakesand reruns, Unicenter CA-Scheduler enforces workstation sequences: all of ajob's pre-CPU work must complete before its CPU processing can begin.

Unicenter CA-Scheduler can also think about work the same way you do. Ifyour production jobs are called AR004 or ARDAILY, use those same names

1-2 Unicenter CA-Scheduler User Guide


when you define jobs to Unicenter CA-Scheduler. Even if ARDAILY is a groupof jobs, you can still retain your familiar names. Because VSE sites run somuch production work, Unicenter CA-Scheduler has you group related jobstogether under one name, a schedule name.

Think of a schedule as a timetable: it tells Unicenter CA-Scheduler whencertain jobs run and which workstations they stop at. All jobs in the databasebelong to some schedule.

Since you are allowed to have multiple schedules, you need to devise anorganized way of grouping jobs into schedules. Many sites group jobs byapplication and frequency. If ARDAILY is one schedule, ARMNTHLY could beanother. When grouping jobs into schedules, keep in mind one thing: optionsdefined for a schedule apply to all jobs in that schedule which means you cansave time by defining options for an entire schedule, but you will always findjobs that are exceptions. Unicenter CA-Scheduler allows you to overrideschedule options by defining different values for the exceptional jobs: mostoptions defined at the job level override options set for a schedule.

Since Unicenter CA-Scheduler does not want to change how you name jobs, itorganizes its database using a method that works for all sites.

Unicenter CA-Scheduler uniquely identifies a task by knowing four values:

■ Job name ■ Job number ■ Workstation number ■ Schedule name

Four values are needed. First, job name alone usually is not enough to singleout every task performed at your site: too many applications have a JOB1 orJOBA, but when job name is linked to schedule name, you come up with aunique job ID. If you omit telling Unicenter CA-Scheduler the other twovalues, workstation defaults to 40 and job number defaults to 01.

Schedule Name When Jobs Run Job Names

ARDAILY

Most options defined for aschedule apply to all thejobs in that schedule.

Every day AR001 . .AR014ADDSTOCKADDSALES

ARMNTHLY

Override schedule optionswith job options.

Each weekend andeach month end.

AR030

ARMNTHLY Only each weekend. ARPAIDARDUE



To show how a job passes through your data center, you define that job ateach workstation. But what if it takes three people to enter the data for JOBA?Just define three workstations for data entry and schedule JOBA at all threeworkstations. That keeps JOBA from running on the CPU until it ends at thosepre-CPU stations.

How does job number fit in? Suppose that you want to run JOBB twice a day,at noon and after 9 p.m. at night. By varying job numbers, you can schedulethe same job several times a day.

That gives you a glimpse of how thoroughly Unicenter CA-Scheduler canmanage your data center, and why you could need all four values to find a



specific job definition in the database. When you are first implementingUnicenter CA-Scheduler, you will start by just defining jobs at station 40 (CPUprocessing). You will have the time to extend Unicenter CA-Scheduler to otherworkstations once it starts automating some of your daily workload.

When defining schedules and jobs to the database, you specify when jobsshould run. Unicenter CA-Scheduler offers two methods for defining whenjobs run: calendars and selection criteria. The calendar method is less versatileand requires more annual maintenance so will not be discussed here.

The preferred method for scheduling jobs uses Unicenter CA-Scheduler criterialanguage. Keywords make it easy to define when to select jobs for the day'sworkload:

DAILY Every day

MON OR WED OR FRI On Monday, Wednesday or Friday

MWF On Monday, Wednesday or Friday

APRIL AND 1ST On April 1st

WEEK-DAY On weekdays (Monday - Friday)

WEEK-END On weekends (Saturday and Sunday)

If you say that a schedule runs daily, Unicenter CA-Scheduler workloadincludes all the jobs in that schedule every day. That is the most efficient wayto schedule daily jobs because you only specify the frequency once for all jobsin the schedule.

Not all jobs run on the same days. Jobs within the same schedule do not haveto run every day the schedule does. For example, a schedule may run dailybut some jobs may only run on Monday and others may only run Friday. Youcontrol when exceptional jobs run by defining a more limited frequency ontheir job records. Remember that a job can only run on days when itsschedule is selected.

Whether Unicenter CA-Scheduler includes a job in the daily workload dependson whether its selection criteria are met. The examples preceding show howself explanatory the criteria language can be. However, its flexibility canaddress every scheduling need.

Defining a job to run on Mondays is easy, but what happens when Monday isa holiday? Unicenter CA-Scheduler knows when holidays occur because theyare defined on a datetable. Therefore, you can ensure that jobs run on the firstwork day of every week by scheduling it on WDOW1 instead of Mondays. Thedatetable tells Unicenter CA-Scheduler:

■ Which days are work days and holidays■ When you need to perform special processing



This last feature allows you to define different accounting, production or salescycles that impact your operations workload. Using other criteria keywords,Unicenter CA-Scheduler allows you to refer to these important days in yourselection criteria. For added flexibility, Unicenter CA-Scheduler allows you todefine up to 20 different kinds of cycles in each datetable, for endless numbersof datetables. Just specify which datetable the criteria statements refer to whenyou define schedules.

The criteria language tells Unicenter CA-Scheduler more than just what daysjobs run: it also shows when jobs must run in a special order. To indicate jobsequences, you define predecessors for jobs. These are events that have to occurbefore that job can begin. Since you define job sequences along with selectioncriteria, both schedules and jobs can have predecessors:

The types of events that can be defined as predecessors include waiting:

■ For a specific job to start or finish■ Until all jobs in a schedule end successfully■ For a specific output data set to close

Before Unicenter CA-Scheduler can begin automating your productionworkload, those jobs need to be defined in the Unicenter CA-Schedulerdatabase. Online, menu-driven panels prompt you for the schedulinginformation that Unicenter CA-Scheduler stores in its database. After thedatabase has been created, Unicenter CA-Scheduler can begin to automateyour production workload.

Schedule's Criteria Job's Criteria When A Job Can Run

JOBA After JOBA on the daysJOBA runs

MON JOBA After JOBA runs onMondays

WEEK-DAY ANDSCHEDA

When schedule SCHEDAfinishes on weekdays


1.2 How Unicenter CA-Scheduler Works


Unicenter CA-Scheduler database contains all of your scheduling informationincluding days, start times and events that impact job processing. UnicenterCA-Scheduler automatically selects, schedules and submits jobs on the rightdays, at the right time, in the right order, based on the information stored inthe database. How that process works is shown following.

Once a day, Unicenter CA-Scheduler scans the database to identify

■ Which schedules qualify for today's workload and■ Which jobs in those schedules should run today

Unicenter CA-Scheduler calls this step autoscan. Authorized users can overridedefined schedules when necessary and run a schedule or job at any time.Schedules and jobs that are not normally selected can be added at the lastminute. Today's workload is copied to the Unicenter CA-Scheduler trackingfile along with any work that has carried over from yesterday as backlog.



Unicenter CA-Scheduler automatically submits jobs to the operating systemwhen they are ready to run. Unicenter CA-Scheduler decides that a job isready to be submitted to the operating system when

■ Its early start time has been reached■ All predecessor conditions have been satisfied■ The job has ended at all pre-CPU workstations■ The job's defined resources are available

Jobs without early start times, without pre-CPU workstations, withoutpredecessors, and without defined resources are submitted when the databaseis scanned. Unicenter CA-Scheduler locates the library in which theappropriate JCL resides, retrieves it and submits it to the operating system.

Customarily, sites store the JCL for each job in a production JCL library.Unicenter CA-Scheduler supports a wide variety of JCL library types:

■ CONDOR■ Unicenter CA-Driver procedure library

■ AllFusion CA-Librarian ■ Allfusion CA-Vollie ■ VM/CMS files ■ AllFusion CA-Panvalet■ User defined library■ VSE PROC library

■ ICCF member ■ SLI member

Different jobs can have their JCL stored in different types of libraries. Anoptional feature of Unicenter CA-Scheduler triggers the display of free-formdocumentation on the operator's console at specified times. Your site mightimplement this feature to display:

■ Job instructions when jobs become available to start, or■ Restart instructions when a job abends

Customarily, sites store the JCL for each job in a production library. Whenselecting the day's workload, Unicenter CA-Scheduler copies the JCL for jobsrequiring setup to the staging library.

Typically, setup means adding something like a date card to the JCL. Foreasier online staging, Unicenter CA-Scheduler can highlight JCL statementsthat require changes and can protect those that do not. The changes you makeaffect the staged JCL without changing your production libraries. UsingUnicenter CA-Scheduler, the setup staff can

■ Display the jobs selected for staging■ Display the staged JCL for each job■ Make the changes online■ Expand Unicenter CA-Driver procedures that are embedded in the JCL



■ Display the current values of Unicenter CA-Driver reserved variableparameters

■ Change the values of any Unicenter CA-Driver reserved variableparameters before each job's staging at workstation 39 is posted ascomplete.

Unicenter CA-Scheduler assists in managing production job rerun/restart inmany different ways:

■ A backout job can be automatically submitted to undo the effect of anabended job.

■ A schedule can be automatically added to the workload when a jobabends. The schedule can include any number of jobs to recover from orrestart the abended job.

■ The Unicenter CA-Scheduler utility program can be embedded in theproduction JCL after strategic job steps, and can trigger different recoveryschedules depending on the abended step.

■ Unicenter CA-Driver procedures can be developed to automaticallygenerate different job streams depending on the abending step when a jobis submitted for a rerun.

False job completion frequently occurs. It is a case in which a job appears tohave run successfully (that is, no abend conditions or fail code returned fromthe job), but in reality the job did NOT run successfully. The evidence is on thejob output (job log), or in the contents of the report produced by the job, or ina message issued to the operator console by the job. False job completioncould be very costly when passed undetected since Unicenter CA-Schedulercould submit numerous successors to a job that appeared to have runsuccessfully. Through the Auto-Reply processing facility false job completioncan be automatically detected and prevented. This is done by checkingconsole output for a job before Unicenter CA-Scheduler posts the job ascomplete.

Users can communicate with Unicenter CA-Scheduler in online or batch mode.All of the Unicenter CA-Scheduler monitoring functions are available from theoperator console as well. Online access is supported for CICS, CMS and ICCF.

Unicenter CA-Scheduler users can be assigned three levels of authority tocontrol what they can and cannot do. Controlling schedules can be limited toauthorized users. Users can also be limited to controlling jobs at certainstations.

Security exits are also available for enhanced protection.

Unicenter CA-Scheduler automatically updates the status of all CPU jobs in thetracking file. Unicenter CA-Scheduler assigns status conditions to jobs toindicate the state of their progress within production. Only authorized userscan issue the commands that alter the status of tasks performed at otherstations.



Using Unicenter CA-Scheduler menu-driven panels, users at differentworkstations can monitor the workload. Status displays allow authorizedusers to monitor the entire day's workload or to selectively view differentcategories of jobs such as

■ Those that are late■ Those that are waiting for predecessors to complete■ Those that have ended, comparing their scheduled start and end times to

actual run times

Now you have an idea of how Unicenter CA-Scheduler automates data centerscheduling, production control management and online tracking. OtherUnicenter CA-Scheduler features that can be implemented in your data centerare shown following.


1.3 Additional Features


Once you have implemented Unicenter CA-Scheduler at station 40, you areready to consider what the next implementation phase will be. Thepossibilities are

■ Extending job definitions to other workstations■ Running forecast, simulation and history reports■ Activating the Unicenter CA-Scheduler progress notification feature■ Expanding scheduling to multiple CPUs

Once Unicenter CA-Scheduler is automating production control for station 40(CPU processing), think about extending that control to pre- and post-CPUworkstations. This would allow you to monitor key applications from start tofinish and alert you to possible production problems before they becomeserious.

The Unicenter CA-Scheduler reporting facility provides a variety of reportsonline or on hardcopy. These reports focus on different facets of productioncontrol to help you address your most pressing concerns.

The Date Translation Table report shows when work day, accounting, andGregorian conditions (like MON) are true.

Production summaries report on various aspects of daily production that youmay want to monitor more closely:

■ Abended jobs ■ Completed jobs■ Closed data sets

■ Job averages

History reports provide statistics on how long it should take to perform everytask and show how long it actually took.

Forecasts show you in advance which schedules and jobs will be selected onany day in the future and what the workload will be like at any station. Asummary report shows at a glance which schedules and jobs will be selectedfor an entire month. Additional forecast reports provide lists of requiredresources, lists of predecessors, and run books for all selected jobs.

Simulation reports answer the question "what if." Unicenter CA-Scheduler canrun simulations without affecting the live scheduling operation and its reportsshow

■ Which jobs would be selected■ What resources would be required■ When and where each job would be processed■ The extent to which each device would be utilized■ Which jobs would be late



■ Which jobs would have to be carried over in backlog to the next day

What if your system goes down? You can run revised simulation reports thatexamine the current status of your workload and project what will happengiven the time remaining.

File Status reports allow you to check the status of the principle UnicenterCA-Scheduler files:

■ Master database ■ Tracking file ■ Staging file ■ Documentation file■ Unicenter CA-Driver procedure library

Use these reports to determine when the files require reorganization (REORGcommand).

The Mailbox report provides a common area to route Unicenter CA-Schedulermessages so that any user can read them.

Successor Chain List reports provide a way of listing a job's or schedule'ssuccessors either globally or up to a specified level. The reports can begenerated online for the current workload or forecasted for a future date.

Analysis reports can be used from batch or online to determine whether aschedule or job has any missing or illogical records.

A variety of Advantage CA-Earl reports provide detailed information on theprinciple Unicenter CA-Scheduler files:

■ Master database ■ History file ■ Tracking file ■ Staging file ■ Documentation file■ Unicenter CA-Driver procedure library

A subset of Advantage CA-Earl is provided with Unicenter CA-Scheduler sothat you can create Advantage CA-Earl reports to suit your data center's needs.In addition, many ready-to-use reports are provided for you to use as is ormodify to your liking.

The CAISERV facility allows you to produce diagnostic reports for checking thecurrent values of product options and assisting in troubleshooting problems.

To better monitor production, you can cause messages to be sent to differentusers when schedules or jobs:

■ Start or end■ Are late starting or ending



■ Abend, fail or are purged■ Run too long

Routing of late messages can be defined globally as an installation option. Youcan specify recipients for other messages using a schedule or job option.Messages can also be logged to the CAICUI data set.

Unicenter CA-Scheduler can run two different ways in a multi-CPUenvironment:

■ All jobs can automatically be scheduled and submitted to one master CPUbefore they are routed by POWER to another CPU for execution.

■ Or each CPU can schedule and submit its own work. In either event,Unicenter CA-Scheduler can cope with system failure by moving control toanother CPU.

You can implement Unicenter CA-Scheduler different ways within networks:

■ To centralize scheduling, design a network following the master/slaveprinciple: do job scheduling at one node of a centralized system and routejobs to other nodes for execution.

■ Or let each node schedule its own work. Even if your network hasdecentralized scheduling, jobs on one network can still be predecessors tojobs scheduled on other networks.

Unicenter CA-Scheduler can handle the production traffic of the busiest datacenters.


1.4 Summing Up

1.4 Summing Up

The first step to implementing Unicenter CA-Scheduler is defining thedatabase. You will begin by defining jobs at station 40 (CPU processing).

Before you begin defining jobs, you need to devise an organized way ofgrouping related jobs into schedules. While grouping jobs, keep in mind thatdefining options for the entire schedule is the most efficient way to implementUnicenter CA-Scheduler. Deal with exceptions by defining options for specificjobs.

An important part of defining jobs is describing their selection criteria andpredecessors. The selection criteria determines which schedules and jobsautoscan includes in the daily workload. Predecessors control the sequence inwhich jobs are submitted to the CPU.

Since jobs are automatically submitted to the CPU, production staff can focusmore on other ways of improving service to their company. Management willappreciate how Unicenter CA-Scheduler reports give an accurate picture of theproduction workload so you can handle special requests more effectively andplan for additional work during peak seasons.

Implementing Unicenter CA-Scheduler reflects a professional commitment toefficient production and will maximize your data processing investment.

The chapter "Startup Tasks" shows new Unicenter CA-Scheduler users how tobegin implementing the product at their site. Its tutorial approach givesstep-by-step instructions in the left column with detailed explanations on theright.

More experienced Unicenter CA-Scheduler users will find the troubleshootinginformation in the chapters "Tips" and "Techniques" most useful.


Chapter 2. Startup Tasks

When Unicenter CA-Scheduler is first installed at your site, its database isempty which means you need to perform some startup tasks before learningabout routine types of maintenance. This chapter is devoted to startupinstructions and introduces you to some of the basics of UnicenterCA-Scheduler. Everyone should read the topic in this chapter called GettingStarted. The other topics in this chapter cover tasks that only concern peoplewith Manager authority level.

If Unicenter CA-Scheduler is new to your site, read this entire chapter.Otherwise, just remember that you can look here to learn how to maintain:

■ Station records ■ Userids

Refer to these topics when you need to perform these tasks.

Chapter 2. Startup Tasks 2-1

2.1 Getting Started

2.1 Getting Started

To get the feel of Unicenter CA-Scheduler, the following tasks will bedescribed:

■ Logging on■ Using the main menu

■ Getting help ■ Logging off

In this topic, logging on will be described first. Follow these instructions topractice using Unicenter CA-Scheduler. Once you are comfortable doing thesetasks, you can start or stop these exercises at your convenience.

2.1.1 Logging OnUnicenter CA-Scheduler can run under CICS, CMS, or ICCF. Once you arelogged on to the appropriate system, how to start Unicenter CA-Scheduler willbe described.

How you start Unicenter CA-Scheduler depends on which system you areusing. Consult the chart following for the appropriate command.

When you type that command and press ENTER, the Unicenter CA-SchedulerLogon panel appears:

� �SCHD-LG �� LOGON �� CA-SCHEDULER

===> - RO

CONNECT : 4�

USERID : master

READ PASSWORD : read

WRITE PASSWORD : write

CONNECT STATION : 4�

PF1=HELP

� �

To Start Unicenter CA-SchedulerFrom

Enter

CICS SCHD

CMS The name of the EXEC defined forUnicenter CA-Scheduler. Write thatname here:

ICCF SCHDICCF


2.1 Getting Started

Now you are ready to log on to Unicenter CA-Scheduler. What you type nextdepends on how long Unicenter CA-Scheduler has been at your site:

■ If Unicenter CA-Scheduler was just installed at your site, type the valuesshown on the preceding panel, tabbing from field to field. Do not pressEnter yet. These passwords are the values defined for the MASTER useridwhen Unicenter CA-Scheduler is first installed.

■ If Unicenter CA-Scheduler has been around your site a while, thosepasswords have probably been changed. Check with the person whoinstalled Unicenter CA-Scheduler to learn what values to use. UnicenterCA-Scheduler userid and passwords do not have to match those you usedto signon to CICS, CMS, or ICCF.

Note: A write password is optional. However, logging on without it meansyou can only display Unicenter CA-Scheduler data. To update data,logon to Unicenter CA-Scheduler with your write password. Alwayslogon with your write password when you begin a practice session.

The last field links you to the workstation of your choice. However, not allusers can connect to all workstations; their choices are limited to those stationsincluded in their user record. When this field is left blank, UnicenterCA-Scheduler automatically connects you to the first station listed in your userrecord.

For now, type 40 as your connect station and press Enter. UnicenterCA-Scheduler responds by displaying its main menu.

2.1.2 Using the Main MenuWhen you have successfully logged on, Unicenter CA-Scheduler displays itsmain menu:


2.1 Getting Started

� � SCHD-MM �� MAIN MENU �� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

-------SELECT FUNCTION-------

==> ONLINE SCHEDULE STATUS

==> ONLINE MONITORING

==> REPORTING FACILITY

==> POWER INTERFACE

==> SCHEDULE MAINTENANCE

==> JOB MAINTENANCE

==> USER ID MAINTENANCE

==> STATION MAINTENANCE

==> RESOURCE MAINTENANCE

==> CALENDAR MAINTENANCE

==> DATETABLE MAINTENANCE

==> STAGED JCL MAINTENANCE

==> DOCUMENTATION MAINTENANCE

==> DRIVER PROC MAINTENANCE

==> AUTO-REPLY MAINTENANCE

==> GENERATION PARM DISPLAY

PF1=HELP

� �

When you logon to Unicenter CA-Scheduler without a write password, thismessage appears on the third line of the main menu:

CACO238I WRITE PASSWORD VERIFICATION FAILED-READ ONLY

Everything you will need to do with Unicenter CA-Scheduler starts here. Toselect a function, tab the cursor to that line and press Enter. Try selecting anyfunction now.

Once you press Enter, Unicenter CA-Scheduler displays the appropriate panel.To return to the Main Menu, press Clear.

No matter how deeply you have gone into Unicenter CA-Scheduler, you canalways return to this panel by pressing Clear repeatedly.

2.1.3 Getting HelpNext the HELP facility will be described. Notice that the bottom line of thatpanel shows PF1=HELP. To display HELP for any panel in UnicenterCA-Scheduler, press PF1 (or PF13). If your terminal does not have PF keys,type HELP in the command area and press Enter.

When you request HELP, Unicenter CA-Scheduler usually shows a panel likethis (some HELP panels will vary depending on the complexity of the panelthat calls them):


2.1 Getting Started

To select the topic you need help with, type a number in the command areaand press Enter.

Some HELP panels contain more text than can be displayed on one physicalpanel. A -- MORE -- prompt at the bottom of the panel tells you that moretext follows. Press PF8 or enter FORW1 to continue to the following text.

While you are exploring HELP, notice the function keys defined on the bottomline. If your terminal does not have function keys, enter the equivalentcommands on the command line instead. The chart following describes whatthese keys and commands do.

PF Key Command Causes Unicenter CA-Scheduler To

PF1/13 HELP Explain how to use the HELP facility

PF3/15 PREVLV Display the last HELP panel

PF4/16 INITIAL Display the initial HELP panel

PF7/19 BACK1 Display previous text in the same HELPpanel

PF8/20 FORW1 Display following text in the same HELPpanel

PF12/24 EXIT Exit from HELP (returns you to UnicenterCA-Scheduler panel). The Clear key doesthe same thing.


2.1 Getting Started

After you have explored HELP a bit, return to the main menu. Remember thatClear always takes you back to the last menu you used.

While you are using Unicenter CA-Scheduler, you are sure to run intomessages that Unicenter CA-Scheduler displays on the third line of your panel.Since that space is limited, you may want a longer explanation of what hashappened. Unicenter CA-Scheduler will give you more details if you type thisin the command area: HELP MSG followed by the message number. (Noticethat message codes start with four letters followed by three numbers andsometimes an additional one-letter action code.)

Now that you know how HELP works, feel free to check what HELP has tosay about the panels you will be working with.

2.1.4 Logging OffThere are two ways to log off of Unicenter CA-Scheduler. Choose a methoddepending on where you are in Unicenter CA-Scheduler.

■ From the Logon panel or main menu, press Clear. If you are at anotherUnicenter CA-Scheduler panel, the other method is more convenient.

■ From any menu or directory panel, enter /LOGOFF in the command area.

Try logging off Unicenter CA-Scheduler now. Then you can log on again inpreparation for the next topic.


2.2 Maintaining Stations


This topic covers the tasks involved in maintaining workstation definitions:

■ Defining stations■ Changing station definitions

■ Deleting stations■ Displaying station records

Since station records rarely require maintenance, most Unicenter CA-Schedulerusers do not need to read this topic. In fact, Unicenter CA-Scheduler onlypermits users with Manager authority to maintain station records. OtherUnicenter CA-Scheduler users can only display existing station records. If andwhen you need to work on your database's station records, consult this topicfor detailed instructions.

Bring up the Unicenter CA-Scheduler main menu as a starting point and tab toSTATION MAINTENANCE.


===> MASTER - WR

CONNECT : 4�





==> POWER INTERFACE


==> JOB MAINTENANCE


_ ==> STATION MAINTENANCE









PF1=HELP

� �

Then tab down to the eighth menu choice, STATION MAINTENANCE, andpress Enter.

That selection brings you to the Station Maintenance menu, which lists thetasks you can choose from:



� � SCHD-WM ��STATION MAINTENANCE�� CA-SCHEDULER

===> _ MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------

DISPLAY FULL DIRECTORY............(PRESS ENTER)

SELECTIVELY DISPLAY DIRECTORY.... 1,SELECT CRITERIA

DISPLAY SPECIFIC STATION......... 2,STATION NUMBER

ALTER STATION RECORD............. 3,STATION NUMBER

DEFINE STATION RECORD............ 4(,STATION NUMBER)

DELETE STATION RECORD............ 5,STATION NUMBER

PF1=HELP

� �

If you logged on without a write password, Unicenter CA-Scheduler onlyshows this menu's first three choices, which allow you to display stationrecords.

The following topics explain how to proceed when:

■ Defining new workstations■ Changing existing station definitions■ Deleting station definitions

2.2.1 Defining StationsIf Unicenter CA-Scheduler is new to your site, you should start building itsdatabase by defining workstations. New Unicenter CA-Scheduler sites beginby defining:

■ Station 40 as CPU processing and possibly■ Station 39 as JCL setup

First, define the CPU station. On the Station Maintenance menu, DEFINESTATION RECORD appears as option 4. Select that option by typing 4 in thecommand area (===>) and pressing Enter.

If you are not assigned Manager authority level, Unicenter CA-Schedulerdisplays the message CACO141E CREATE NOT ALLOWED on the third lineof the Station Maintenance menu. That message indicates that you are notauthorized to work with station records.

If your authority level permits you to define stations, Unicenter CA-Schedulerdisplays the Station Definition panel:



� � SCHD-WU ��STATION DEFINITION�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

STATION ID : 4� PROTOTYPE STATION:

STATION NAME : cpu

TIME ZONE :

STATION TITLE : cpu station

STATION DESCRIPTION : Where the jobs are run

PF1=HELP

� �

The only required field in the station record is STATION ID; the station nameand station title only appear on reports. Press the TAB key to move the cursorfrom field to field. To define station 40 as the CPU station, enter the datadisplayed on the panel preceding.

When defining other workstations, substitute appropriate values for the datashown preceding. Your choice of STATION ID is important: UnicenterCA-Scheduler expects jobs to flow through workstations numbered inascending order. The order in which you number workstations is the basis forsequence enforcement. Therefore, be sure that:

■ Pre-CPU stations range from 01 to 39■ Post-CPU stations use numbers 41-99 and■ Station number sequence shows how work flows through your data center

When you are finished typing values on the Station Definition panel, pressEnter. Unicenter CA-Scheduler then informs you whether that record wassuccessfully added to the database.

If Unicenter CA-Scheduler adds the record to the database, it displays thispanel:

� � SCHD-UTIL ��SCHDUTIL OUTPUT�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

DEFINE STATION ID=4�,NAME=CPU,TITLE='CPU STATION',

DESC='WHERE THE JOBS ARE RUN'

CACU�18I STATION 4� CPU HAS BEEN ADDED

PF1=HELP

� �

If Unicenter CA-Scheduler rejects this record, it displays other messages on thesame panel. For example, if you try to add a station number that is alreadydefined in the database, Unicenter CA-Scheduler displays this message:




===> MASTER - WR

CONNECT : 4�

DEFINE STATION ID=4�,NAME=CPU,TITLE='CPU STATION',

DESC='WHERE THE JOBS ARE RUN'

CACU�15E DEFINE STATION CPU DUPLICATE RECORD

PF1=HELP

� �

Does this mean Unicenter CA-Scheduler created a duplicate record? Wheneveryou are in doubt, display help for that message number. If you try that, youwill see that Unicenter CA-Scheduler detected the duplicate record andrejected it.

If Unicenter CA-Scheduler finds any errors, you can correct them by typingdirectly onto the SCHDUTIL Output panel. Then press Enter again to add thecorrected definition to the database.

Alternatively, you can press Clear to:

■ Exit from the definition panel without entering a record in the database■ Return to the maintenance menu and try the whole definition again or■ Get ready to define another station

Now try defining a station on your own. Pick a number at random and typeyour userid for STATION NAME and STATION TITLE. The examplesfollowing use station 27. Jot down the number you use here so you canpractice changing and deleting your station later.

2.2.2 Updating Station RecordsUnicenter CA-Scheduler gives you two ways of updating records:

■ One requires that you know the station number you want to change.■ The other does not.

The first method follows.

Begin by checking which option on the Station Maintenance menu allows youto update existing records:




===> _ MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------







PF1=HELP

� �

The instructions on this panel tell you to use option 3 to change an existingrecord. Notice, however, that Unicenter CA-Scheduler expects you to enter thestation number when you select option 3. Therefore, when you type 3 in thecommand area, follow it with a comma and the number of the station youwant to update.

Change the name of the workstation you defined. If you defined station 27,enter 3,27 in the command area to retrieve that record.

If you are not assigned Manager authority level, Unicenter CA-Schedulerdisplays the message CACO122E ALTER IS NOT ALLOWED on the third lineof your panel. That message indicates that you are not authorized to workwith station records.

If your authority level permits you to alter station records, UnicenterCA-Scheduler displays the STATION ALTER panel.

� � SCHD-WU ��STATION ALTER�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

STATION ID : 27

STATION NAME : userid

TIME ZONE :

STATION TITLE : your userid

STATION DESCRIPTION :

PF1=HELP

� �

Now you can alter anything but STATION ID in this record by tabbing to itand typing over the old value. Try changing STATION NAME to your initials.



To submit this change to the database, press Enter. Or if you change yourmind about altering the record, press Clear. When you submit a change to thedatabase, Unicenter CA-Scheduler confirms that the station record changed bydisplaying the message following:


===> MASTER - WR

CONNECT : 4�

ALTER STATION ID=27,NAME=INITIALS

CACU�18I STATION 27 INITIALS HAS BEEN ALTERED

PF1=HELP

� �

Compare this approach to the alternate method for making changes. Begin byreturning to the Station Maintenance menu using the Clear key.

The other method for altering station records does not expect you to knowwhich station ID to change. Begin by displaying all station records stored inyour database.


===> _ MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------







PF1=HELP

� �

The first entry on the menu preceding tells you to press Enter to display adirectory of station records.



� � SCHD-WD ��STATION DIRECTORY�� CA-SCHEDULER

===> _ MASTER - WR

CONNECT : 4�

ID STNAME TIME-ZN D E S C R I P T I O N

2� KEYPUNCH �� WHERE INPUT DATA IS KEYPUNCHED

21 KEYPUNCH ��

27 INITIALS ��

39 STAGING �� WHERE JCL CHANGES BEFORE JOBS RUN

4� CPU �� WHERE THE JOBS ARE RUN

6� OUTPUT �� WHERE OUTPUT IS DISTRIBUTED FROM

�� END OF DIRECTORY LIST ��

PF1=HELP

� �

The stations you see listed are different than those shown here. However, youshould be able to spot the station you defined.

Select that station so you can alter its values. Start by tabbing down to thatline. Then type A and press Enter.

If your authority level permits you to alter station records, UnicenterCA-Scheduler displays your station record so you can type in new values. Tryadding a station description such as you see following:

� � SCHD-WU ��STATION ALTER�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

STATION ID : 27

STATION NAME : initials

TIME ZONE :

STATION TITLE : your userid

STATION DESCRIPTION : This is a test record

PF1=HELP

� �

Press Enter to save your changes or press Clear to cancel them. WhenUnicenter CA-Scheduler has changed your station record, it confirms thecorrection by displaying the message:

CACU�18I STATION 27 INITIALS HAS BEEN ALTERED

Then press Clear until you return to the Station Maintenance menu.

2.2.3 Deleting WorkstationsDeleting records is similar to altering them: Unicenter CA-Scheduler gives youtwo methods to choose from. Which method you use depends on whether youknow what station number to delete.

To delete a specific station number, begin by checking which option on theStation Maintenance menu allows you to delete an existing record.




===> _ MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------







PF1=HELP

� �

The preceding panel tells you that option 5 deletes an existing record. Notice,however, that Unicenter CA-Scheduler expects you to enter the station numberwhen you select option 5. Therefore, when you type 5 in the command area,follow it with a comma and the number of the station you want to delete.

Delete the workstation you defined. For example, if you defined station 27,enter 5,27 in the command area to delete that record.

If you are not assigned Manager authority, Unicenter CA-Scheduler displaysthe message CACO148E DELETE IS NOT ALLOWED. But if you haveManager authority, Unicenter CA-Scheduler confirms you deleted that stationrecord with the message shown following:


===> MASTER - WR

CONNECT : 4�

DELETE STATION ID=27

CACU�18I STATION 27 INITIALS HAS BEEN DELETED

PF1=HELP

� �

That's how simple it is to delete a station record. Before the alternate method isdemonstrated, take a moment to recreate the station record you just deleted.Then you will be ready to continue.

If you do not know which station number you want to delete, display adirectory of stations using the Station Maintenance menu. Pressing Enter atthat menu causes the following panel to appear:




===> MASTER - WR

CONNECT : 4�



21 KEYPUNCH ��

27 INITIALS �� THIS IS A TEST RECORD





PF1=HELP

� �

Your entries will differ from those shown preceding, but you should be able topick out your station record. To delete that record, first tab down to it.

Before you typed A to alter the record. Now type L to delete it. Once again, ifyou have Manager authority, Unicenter CA-Scheduler confirms that it deletedthe record by displaying the message:

CACU�18I STATION 27 INITIALS HAS BEEN DELETED

2.2.4 Displaying WorkstationsAll Unicenter CA-Scheduler users can display station records. If you haveManager authority, you saw one way of listing station records while youpracticed maintaining workstations. In all, you have three alternatives fordisplaying station records:

■ Display a specific station number■ List a subset of stations and choose one■ List all stations and pick one

First, the record for station 40 will be displayed. On the Station Maintenancemenu, choices 1 and 2 both display a station record, but in different formats.




===> _ MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------







PF1=HELP

� �

Try option 2 first because it is faster. When you use option 2, UnicenterCA-Scheduler expects you to specify a station number. To display the recordfor station 40, try typing 2,40 in the command area. Unicenter CA-Schedulerresponds by displaying that station record on this panel:

� � SCHD-WU ��STATION DISPLAY�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

STATION ID : 4�

STATION NAME : CPU

TIME ZONE :

STATION TITLE : CPU STATION

STATION DESCRIPTION : WHERE THE JOBS ARE RUN

PF1=HELP

� �

This panel resembles the panel you used when defining station records. Nowcompare that approach to another one that requires two steps. Return to theStation Maintenance menu to try that alternate approach.

Try option 1, which requires you to specify some selection criteria. That criteriacan be the station number. Try typing 1,40 in the command area and pressingENTER. Unicenter CA-Scheduler responds by displaying that station record inanother format:




===> _ MASTER - WR

CONNECT : 4�




PF1=HELP

� �

Option 1 displays that record on the Station Directory panel. You may recallthat this panel allowed you to alter or delete records by typing the appropriatecommand next to a specific record.

This panel also recognizes a third command, D, which causes the StationDisplay panel to appear. Branch to that panel now by tabbing to the station 40record and entering a D.

Then return to the Station Directory panel.

Option 1 on the Station Maintenance menu can be useful if you want to list agroup of related station numbers. To list all defined stations between 20 and29, you can use the asterisk (*) as part of the selection criteria.

For example, if you type 1,*2 in the command area of the Station Maintenancemenu, Unicenter CA-Scheduler displays records for all station numbers thatstart with 2:


===> _ MASTER - WR

CONNECT : 4�



21 KEYPUNCH ��



PF1=HELP

� �

Now return to the Station Maintenance menu to try the last method fordisplaying station records.

The last method causes Unicenter CA-Scheduler to display all station records.The instructions following review how that is done.

The first entry on the Station Maintenance menu tells you to press Enter todisplay a directory of station records. Pressing Enter to view that listing:




===> _ MASTER - WR

CONNECT : 4�



21 KEYPUNCH ��






PF1=HELP

� �

One panel might not hold all the stations defined at your site. If that is thecase, the END OF DIRECTORY LIST message will not appear on your panel.Instead, the list will end with the message:

PRESS ENTER FOR NEXT PAGE

When this message appears, press that key to view the remainder of the list.Remember that Unicenter CA-Scheduler recognizes the following commandswhen they are entered next to a specific station:

Before you start the next topic, return to the main menu by pressing Clear.

To Enter

Alter records A

Display records D

Delete records L

2.2.5 Summary of Station MaintenanceUnicenter CA-Scheduler only permits users with Manager authority to define,alter and delete station records. Any user can display station records. Forquick reference, the steps involved in maintaining station records from theStation Maintenance menu are summarized following. Since there are so manyways to display records, only the fastest ways are shown:

■ A specific station■ An unknown station■ A specific station■ An unknown station■ One station record

■ Some stations ■ All stations



To Enter This In CommandArea

Then

Define records

a specific station

an unknownnumber

3,station number

Press Enter

Enter changes

Tab to a station; enteran A; make changes

Delete records for

a specific station

an unknownstation

5,station number

Press Enter Tab to a station; thenenter an L

Display

one station record

some stations

all stations

2,station number

1,*x where x is the firstcharacter of some stationIDs

Press Enter

Tab to a station; entera D

Press Enter to scrollpanels


2.3 Maintaining User Records


All Unicenter CA-Scheduler users can display userid directories. All userslogged on with write passwords can change their own passwords and useriddescriptions. But only users with Manager authority can maintain all userrecords.

User records control who does what with Unicenter CA-Scheduler. Only userswho are defined in Unicenter CA-Scheduler database can logon to thatproduct. Unicenter CA-Scheduler security goes a step further: user recordslimit what people can do with Unicenter CA-Scheduler.

This topic covers what has involved in maintaining user records in theUnicenter CA-Scheduler database. The topics explored next include:

■ User authority levels■ The role of passwords

■ Defining users■ Altering, deleting, and displaying user records

If you have already become familiar with maintaining stations, you will noticethat Unicenter CA-Scheduler handles these tasks in similar ways.

2.3.1 User Authority LevelsThree levels of authority control what defined users can do with UnicenterCA-Scheduler. The lists following describe the basic capabilities of eachauthority level.

General Authority is intended for end users, restricting:

■ The stations they can connect to■ The database records they can maintain■ The schedules they are authorized to monitor and control

General users are also allowed to display and alter their ownpasswords and define online documentation.

SupervisorAuthority allows its users to:

■ Define, maintain, display, and control All schedules

Jobs defined at stations for which each user is authorized

■ Define online documentation■ Display and alter

Their own passwordsAll staged JCL while connected to station 39

■ Display all other database records■ Connect to just those stations listed on its userid



Manager Authority allows its users to:

■ Connect to all stations■ Maintain all database records■ Control all schedules

People with General or Supervisor authority can display and alter their ownuser records. Only users with Manager authority can define, alter or displayuser records for others. Whether users at any authority level can display orupdate other database records depends on what passwords they have defined.

For a comprehensive list of the specific tasks permitted by each authority level,see the description of the Userid Definition panel in the Unicenter CA-SchedulerReference Guide Part 1.

2.3.2 The Role of PasswordsAuthority levels define what data users can access; but passwords controlwhether users can update or just display that data. People need readpasswords to log on to Unicenter CA-Scheduler. Write passwords control auser's capabilities in two ways:

■ You can prevent users from changing data by not assigning them a writepassword.

■ Users assigned write passwords decide when they want to use that updatecapability. If they logon to Unicenter CA-Scheduler with their writepassword, they can update the database during that logon session, but ifthey signon without specifying their write password, they can only displaydata during that session.

2.3.3 Getting StartedAll the tasks involved with maintaining user records originate from the samemenus. To initiate this kind of maintenance, begin at the UnicenterCA-Scheduler main menu by tabbing to USER ID MAINTENANCE:




===> MASTER - WR

CONNECT : 4�





==> POWER INTERFACE


==> JOB MAINTENANCE

_ ==> USER ID MAINTENANCE










PF1=HELP

� �

Then tab down to the seventh selection, USER ID MAINTENANCE, and pressEnter. That choice displays the UserID Maintenance menu, which listseverything you can do with user records.

� � SCHD-UM ��USERID MAINTENANCE�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------

DISPLAY FULL DIRECTORY........... (PRESS ENTER)


DISPLAY SPECIFIC USERID.......... 2,USERID

ALTER USERID RECORD.............. 3,USERID

DEFINE USERID RECORD............. 4(,USERID)

DELETE USERID RECORD............. 5,USERID,WRITPASS

PF1=HELP

� �

If you logon without a write password, only the first three menu choicesappear on your panel. They allow you to display userid directories.

The following topics explain how to:

■ Define new user records■ Change existing user definitions■ Delete user records■ Display user records



2.3.4 Defining UsersUnicenter CA-Scheduler only allows people with Manager authority to createuser records. To define a new userid, type 4 in the command area of theUserID Maintenance menu and press Enter.

If your authority level does not permit you to create user records, UnicenterCA-Scheduler displays the message CACO147E DEFINE NOT ALLOWED onthe third line of your panel. But if you have Manager authority, UnicenterCA-Scheduler responds by displaying the UserID Definition panel.

� � SCHD-UU ��USERID DEFINITION�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

USER IDENTIFICATION : acctg

USERID READ PASSWORD: receipts

USERID WRITE PASSWORD:

USER ID DESCRIPTION :

CONNECT USERID TO STATIONS: 4�

USERID TYPE (M,S OR G) :

PF1=HELP

� �

The panel preceding shows that Unicenter CA-Scheduler only requires data inthe first two fields. If you press Enter, leaving the remaining fields blank,Unicenter CA-Scheduler creates a user record with the followingcharacteristics:

■ UserID is ACCTG■ Read password is receipts■ User can only display data■ Connect to station 40■ General authority level

ACCTG is limited to displaying data because no write password was assigned.The General authority level limits ACCTG to:

■ Connecting to station 40 and any other stations specified■ Monitoring the status of jobs and schedules for which it is authorized

■ Displaying– Its own user record– Definition records for authorized jobs and schedules– Staged JCL for authorized jobs if authorized for station 39

You can expand upon those capabilities by specifying additional informationon the user record.



The rules following summarize that chart, clarifying the kinds of authority youcan assign to users:

Rule #1: Always assign users a read password.

Rule #2: Assign write passwords to give people update permission andthe ability to issue commands to control schedules and jobs.

Rule #3: Give users extra authority by making USERID TYPE be S or M:

■ Supervisor authority allows people to maintain all scheduleand job records, and issue commands to control all schedulesat just those stations for which they are authorized.

■ Manager authority allows people access all database recordsand control all jobs and schedules at all stations.

Most Unicenter CA-Scheduler sites assign end users General authority with orwithout a write password. To define ACCTG with the minimal permissionsenter the data shown on the preceding panel and press Enter.

If Unicenter CA-Scheduler successfully adds this unique new user record to itsdatabase, the following message panel appears:

To Allow Specify

General users to

■ Update schedules and jobs forwhich they are authorized

■ Issue commands to controlschedules and jobs for whichthey are authorized at stationsfor which they are authorized

■ Maintain schedule and jobdefinitions withoutauthorizing their user IDs onevery schedule

A write password of up to eightalphanumeric characters. Authorize thatuser on the appropriate schedule.

Same as preceding.

Change their authoritylevel to S or M

Users with Supervisor authority to

■ Monitor other workstations

■ Maintain all station and userrecords

Other station IDs separated by commas(list the workstation they will monitormost first).

Change USERID TYPE to M




===> MASTER - WR

CONNECT : 4�

DEFINE USERID NAME=ACCTG,READPASS=RECEIPTS

CACU�18I USERID ACCTG HAS BEEN ADDED

PF1=HELP

� �

However, Unicenter CA-Scheduler may not be able to create that user recordfor some reason. In that case, other messages would appear:

■ If you do not have Manager authority, Unicenter CA-Scheduler respondsby displaying the message

CACO147E DEFINE NOT ALLOWED

on the third line of your panel.■ The same message also appears if you did not logon using your write

password.■ If that userid already exists, Unicenter CA-Scheduler displays the following

panel:


===> MASTER - WR

CONNECT : 4�

DEFINE USERID NAME=ACCTG,READPASS=RECEIPTS

CACU�15E DEFINE USERID ACCTG DUPLICATE RECORD

PF1=HELP

� �

Next, create two other user records with different types of authority:

Define these records now before proceeding to the next topic.

For Define This Record

Operators User ID: OPERATORRead password: CONSOLEWrite password: SYSTEMConnect: 40,39Authority: S

Production control staff User ID: PRODCTRLRead password: INPUTWrite password: OUTPUTConnect: 40,39Authority: M



Unicenter CA-Scheduler allows people who log on as OPERATOR to issueonline commands to control all schedules at stations 39 and 40. If, whenlogging on, they do not specify which station to connect to, UnicenterCA-Scheduler automatically connects them to station 40. That is because 40 isthe first entry in the list of stations that ID is authorized to connect to.

Users logged on as PRODCTRL can do everything OPERATOR can do as wellas:

■ Connect to all stations■ Maintain all database records■ Log other users off after a crash

2.3.5 Updating User RecordsUsers with Manager authority can update any user records. Others with writepasswords can follow these instructions to change their own passwords.

Unicenter CA-Scheduler gives you two ways of updating records. The firstway requires that you know the userid you want to change.

Begin by checking which option on the User Maintenance menu allows you toupdate existing records.


===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------







PF1=HELP

� �

This panel tells you to use option 3 to change an existing record. Notice,however, that Unicenter CA-Scheduler expects you to enter a userid when youselect option 3. Therefore, when you type 3 in the command area, follow itwith a comma and the userid you want to update.

To change ACCTG's user record by adding a write password, enter 3,ACCTGin the command area to retrieve that record. If your authority level permitsyou to alter that user record, Unicenter CA-Scheduler displays the UserIDAlter panel:



� � SCHD-UU ��USERID ALTER�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�



USERID WRITE PASSWORD:

USER ID DESCRIPTION :

CONNECT USERID TO STATIONS:

USERID TYPE (M,S OR G) : G

PF1=HELP

� �

Now you can alter anything in this record but USER IDENTIFICATION bytabbing to the field and typing in a new value. Try extending ACCTG'sauthority by defining a write password of profit which will permit the ACCTGuserid to:

■ Define jobs and schedules■ Define online documentation to display at the console

■ AlterIts read and write passwordsJobs and schedules that specifically authorize that useridStaged JCL if authorized for that station and job

■ Issue commands to control schedules that authorize that userid

To submit this change to the database, press Enter. Or, if you change yourmind about altering the record, press Clear. When you submit a change to thedatabase, Unicenter CA-Scheduler confirms that it is altered that user recordby displaying the message following:


===> MASTER - WR

CONNECT : 4�

ALTER USERID NAME=ACCTG,READPASS=RECEIPTS,WRITPASS=PROFIT

CACU�18I USERID ACCTG HAS BEEN ALTERED

PF1=HELP

� �

Unicenter CA-Scheduler allows people with different authority levels alterdifferent fields in user records:



Compare this editing approach to the alternate method for making changes.Begin by returning to the UserID Maintenance menu using the Clear key.

The other method for altering user records does not expect you to know whichuserid to change. Begin by displaying all user records stored in your database.


===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------







PF1=HELP

� �

The first entry on the menu preceding tells you to press Enter to display adirectory of user records. Press Enter to view that listing:

� � SCHD-UD ��USERID DIRECTORY�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

USERID TYPE STATUS CONNECT STATIONS D E S C R I P T I O N

_ ACCTG G LOGOFF 4�

MASTER M LOGON

OPERATOR S LOGOFF 4�,39

PRODCTRL M LOGOFF


PF1=HELP

� �

The user records you created should appear in the directory list that is sortedalphabetically by userid. The STATUS field on this panel tells you which ofthese users are currently logged on.

Users With Can Change

General and Supervisor authority ■ Their own read password■ Their write password (if one already

exists)

Manager authority Any field in any user's record



Select the userid ACCTG so you can alter its values. Start by tabbing down tothat line. Then type A and press Enter. If you do not have Manager authority,Unicenter CA-Scheduler displays the message ONLY YOUR OWN USERIDCAN BE ALTERED.

If your authority level permits you to alter the ACCTG record, UnicenterCA-Scheduler displays it so you can type in new values. Add a useriddescription such as you see following:

� � SCHD-UU ��USERID ALTER�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�



USERID WRITE PASSWORD: profit

USER ID DESCRIPTION : Accounting Department



PF1=HELP

� �

Press Enter to save your changes or press Clear to cancel them. WhenUnicenter CA-Scheduler has changed that user record, it confirms thecorrection by displaying the message:

CACU�18I USERID ACCTG HAS BEEN ALTERED

Press Clear until you return to the UserID Maintenance menu.

2.3.6 Deleting User RecordsUnicenter CA-Scheduler gives users with Manager authority just one way todelete user records from the database. Begin by checking which option on theUserID Maintenance menu allows you to delete an existing record:




===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------







PF1=HELP

� �

The preceding panel tells you that option 5 deletes an existing record. Notice,however, that Unicenter CA-Scheduler expects you to enter a userid andpassword when you select option 5. The password needed is the writepassword of the userid you are deleting. Therefore, to delete a user record,type 5 in the command area and follow it with a comma, the userid you wantto delete, another comma, and the write password of that userid.

Delete the ACCTG userid you defined by entering 5,ACCTG,PROFIT. If youare assigned Manager authority, Unicenter CA-Scheduler confirms you deletedthat user record with the message shown following:


===> MASTER - WR

CONNECT : 4�

DELETE USERID NAME=ACCTG,WRITPASS=PROFIT

CACU�18I USERID ACCTG HAS BEEN DELETED

PF1=HELP

� �

Before you continue with the next topic, try recreating the userid ACCTG.

Return to the UserID Maintenance menu so you will be ready to start the lasttopic in this chapter.

2.3.7 Displaying User RecordsAll Unicenter CA-Scheduler users can list userids and display their own userrecord. If you have Manager authority, you already saw one way of listinguserids while you practiced maintaining user records.

Basically, Unicenter CA-Scheduler offers you three different ways to displayuser records. You can:



■ Display a specific user record■ List all userids and pick one record to display■ List a subset of user records before picking one■ List userids that are logged on or logged off

Display the user record for ACCTG. On the UserID Maintenance menu,choices 1 and 2 both display a user record, but in different formats.


===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------







PF1=HELP

� �

Try option 2 first because it is faster. When you use option 2, UnicenterCA-Scheduler expects you to specify a userid. To display the record forACCTG, type 2,ACCTG in the command area. Unicenter CA-Schedulerresponds by displaying that user record on this panel:

� � SCHD-UU ��USERID DISPLAY�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�



USERID WRITE PASSWORD: profit

USER ID DESCRIPTION : Accounting Department



PF1=HELP

� �

The preceding panel resembles the one you used when defining useridsbecause all fields in the user record are displayed. Option 1 accomplishes thesame thing in two steps. Return to the UserID Maintenance menu to try thealternate approach.



Option 1 requires you to specify some selection criteria that can be a userid.Type 1,ACCTG in the command area and pressing Enter. UnicenterCA-Scheduler responds by listing that userid in another format:


===> _ MASTER - WR

CONNECT : 4�


ACCTG G LOGOFF 4� ACCOUNTING DEPT


PF1=HELP

� �

Option 1 lists that userid on the UserID Directory panel but omits passwords.If this panel looks familiar, you may recall that you can alter user records byentering the A command next to a specific userid.

This panel also recognizes another command, D, which causes UnicenterCA-Scheduler to display the entire user record on the UserID Display panel.Branch to that panel by tabbing to the ACCTG record and entering a D.

After seeing both ways, you will probably use option 2 to display a userrecord because it is more efficient. To try displaying records using othermethods, first return to the UserID Maintenance menu.

This method causes Unicenter CA-Scheduler to alphabetically list all userids.The instructions following review how that is done.

The first entry on the UserID Maintenance menu tells you to press Enter todisplay a directory of user records. Press Enter now to view that listing:


===> _ MASTER - WR

CONNECT : 4�


ACCTG G LOGOFF 4�

MASTER M LOGON

OPERATOR S LOGOFF 4�,39

PRODCTRL M LOGOFF


PF1=HELP

� �

One panel might not hold all the userids defined at your site. If that is thecase, the END OF DIRECTORY LIST message will not appear on your panel.Instead, the list will end with the message:




When this message appears, press that key to view the remainder of the list.To display a userid's complete record, you would tab to that userid and entera D.

Remember that Unicenter CA-Scheduler recognizes the following commandswhen they are entered next to a specific userid:

Scrolling through several panels full of userids to locate the one that interestsyou could be a bother. That is why Unicenter CA-Scheduler offers yet anotheroption. Before you try the third method, return to the UserID Maintenancemenu by pressing the Clear key.

Option 1 can be useful if your userid directory is long and you want to listuserids that start with the same characters. For example, what if you madeseveral userids for production control that all start with PROD and end withthe user's initials. You could list these several ways using option 1 and theasterisk (*):

For example, typing 1,*P causes Unicenter CA-Scheduler to display records forall userids that start with the letter P:


===> _ MASTER - WR

CONNECT : 4�


PRODCTRL M LOGOFF PRODUCTION CONTROL

PRODLJB M LOGOFF LYNN BROWN

PRODPAS M LOGOFF PAT SMITH

PRODTFA M LOGOFF TERRY ANDERSON


PF1=HELP

� �

Now return to the UserID Maintenance menu to try the last method fordisplaying user records.

To Enter

Alter records A

Display records D

To List Userids Starting With Enter

The letter P 1,*P

The same PROD prefix 1,*PROD



If users are logged on to Unicenter CA-Scheduler when your system goesdown, the MASTER userid needs to force logoffs for those users. The MASTERuserid can force other users off by typing

3,L,userid on the UserID Maintenance menu.

Any user can force a logon by typing

F,userid in the command area of the Logon panel.

You can check to see the status of users individually using the methods shownpreceding, or you can list userids based on their current status. Submit thesecommands to Unicenter CA-Scheduler by entering them in the command areaof the UserID Maintenance menu.

To see who is logged on to Unicenter CA-Scheduler now, type 1,L=ON in thecommand area and press Enter. Unicenter CA-Scheduler responds bydisplaying a directory listing just those users currently running UnicenterCA-Scheduler:


===> _ MASTER - WR

CONNECT : 4�


MASTER M LOGON


PF1=HELP

� �

To List Users Who Are Currently Enter

Logged on to Unicenter CA-Scheduler 1,L=ON

Logged off 1,L=OFF

2.3.8 Summary of User MaintenanceThis list summarizes who can do what with user records:

■ All users can display userid directories.■ Users with write passwords can change their own passwords.■ Only users with Manager authority can maintain all user records.■ Only the MASTER userid can force other users off by typing 3,L,userid on

the UserID Maintenance menu. ■ All userids

The chart following sums up the steps involved in maintaining station recordsfrom the UserID Maintenance menu. Since there are so many ways to displayrecords, only the fastest ways are shown:



To Enter This In CommandArea

Then

Define records

a specific userid

an unknown userid

3,userid

Press Enter

Enter changes

Tab to a userid;enter an A; makechanges

Delete a specific userid 5,userid,writpass

Display

one user record

some userids

all userids

2,userid

1,*x where x is the firstcharacter of some user IDs

Press Enter

Tab to a userid;enter a D

Press Enter to scrollpanels


Chapter 3. Maintaining the Database

The Unicenter CA-Scheduler database contains the information that automatesproduction. Therefore, the maintenance of that database is crucial to your datacenter's operation.

Unicenter CA-Scheduler users find they spend most of their time maintainingschedule and job records. This chapter focuses on how to work with thesetypes of records using the Unicenter CA-Scheduler interactive panels. Whenyou finish this chapter, you will be able to define, display and update:

■ Schedule records ■ Job records

If Unicenter CA-Scheduler is new to your site, perform the startup tasksdescribed in the chapter "Startup Tasks." Then, the next step is defining yourproduction workload to Unicenter CA-Scheduler.

Chapter 3. Maintaining the Database 3-1

3.1 Defining Schedules


A schedule contains one or more jobs that are grouped together because theyshare similarities. Jobs in the same schedule might all:

■ Belong to the same application■ Run on the same day■ Have the same operational dependencies or, most importantly,■ Belong together because that is how your site is organized

Grouping jobs in schedules is easier because jobs can be selected whenevertheir schedules are selected, and many schedule options apply to all jobswithin a schedule. That means you can define jobs faster if you specify theircommon characteristics on a schedule record.

In this chapter, the examples we use do not store much information inschedule records. But as time goes on, you will find it is easy to implementspecial features such as

■ Having Unicenter CA-Scheduler issue messages when work falls behind or■ Defining when to submit jobs

by changing just schedule records instead of every job record.

All users with write passwords can define schedule records. This topic showsyou how by

■ Planning schedules■ Defining a schedule base record■ Checking which defaults apply to schedules■ Learning the basics about a schedule record■ Defining optional schedule records

3.1.1 Planning SchedulesAs you start using Unicenter CA-Scheduler, do not try to automate everythingat once. If you do, you will be overwhelmed with details. Instead, start gettingcomfortable with Unicenter CA-Scheduler by defining just a few simpleschedules first. You will start by outlining a schedule for your site's backupruns. This example shows how easy defining a schedule can be. Laterexamples will show optional features you can implement when definingschedules.

When you are deciding what schedules to define for your site, keep theseguidelines in mind:

■ Group jobs into schedules by application first. If that gives you anunmanageable number of jobs for one schedule, subdivide it based onwhen jobs run.



■ Do not create a schedule for each day of the week. That approach isdifficult to implement and even harder to maintain. Instead, group jobsbelonging to the same application together in one or two schedules. Thatmakes it easier to verify predecessor relationships.

■ Likewise, put jobs that run upon request with the rest of thoseapplications' jobs. The goal here is to limit the number of cross-scheduledependencies, keeping schedule maintenance and verification as simple aspossible.

■ Try to limit the number of jobs you put in schedules to under 50. Again,the rationale is keeping things simple. Big schedules are morecumbersome.

Now apply this advice to defining a schedule for backup jobs.

3.1.2 Defining a Schedule Base RecordSince schedules define the characteristics shared by groups of jobs, schedulerecords primarily consist of optional fields. The simplest schedule definition isstored on a base record. This topic explains how to define a simple schedule.

You begin defining schedules at Unicenter CA-Scheduler's main menu. Tab toSCHEDULE MAINTENANCE.


===> MASTER - WR

CONNECT : 4�





==> POWER INTERFACE

_ ==> SCHEDULE MAINTENANCE

==> JOB MAINTENANCE











PF1=HELP

� �

Defining schedules is one form of schedule maintenance. Therefore, tab downto the fifth selection and press Enter. That choice displays the ScheduleMaintenance menu, which lists everything you can do with schedule records.



� � SCHD-SM ��SCHEDULE MAINTENANCE�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------



DISPLAY SPECIFIC SCHEDULE........ 2,SCHEDULE

ALTER SCHEDULE RECORD............ 3,SCHEDULE

DEFINE SCHEDULE RECORD........... 4(,SCHEDULE)

DELETE SCHEDULE RECORD........... 5,SCHEDULE

ANALYZE SCHEDULE................. 6,SCHEDULE

AUTO-REPLY PROCESSING............ 7,SCHEDULE

PF1=HELP

� �

If you logon without a write password, the read-only functions appear on yourscreen. They only allow you to display schedule directories, analyze aschedule, or view auto-reply records. You need to logon with your writepassword to practice defining schedules.

When the Schedule Maintenance menu appears, type 4 in the command areaand press Enter. Then the Schedule Definition panel appears.

� � SCHD-SU ��SCHEDULE DEFINITION�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

SCHEDULE NAME : _ PROTOTYPE SCHEDULE NAME :

SCHED PRIORITY:

AUTO SELECT : NO

DATETABLE NAME: SKIP :

RUN ON SYSID : BACKLOG : YES

NODE ID : STAGE JCL :

NODE SYSID : USE SIMTIME:

AVERAGE TIME: ��

USERS:

LIBRARY TYPE :

POWER CLASS :

POWER PRIORITY: POWER USER:

AUTO-REPLY MESSAGES: N

EARLIEST START TIME : MAXIMUM EXECUTION TIME :

MUST START BY TIME : COMPLETION DEADLINE TIME :

RECS= SBR: N SCR: N SRC: N SIR: N SMR: N PF1=HELP

� �

This panel displays default values for three of its fields. Check what thosevalues do before deciding whether to change them.



AUTO SELECT controls whether Unicenter CA-Scheduler selects this scheduleautomatically during autoscan. When AUTO SELECT = NO, this schedule isskipped and its jobs are not included in the daily workload. That is exactlywhat you want to happen while you are defining and testing a schedule andits jobs, so do not change that field yet. Once you are satisfied with thosedefinitions, you will activate this schedule for automatic selection by changingthe value of AUTO SELECT to YES.

BACKLOG controls what happens if a schedule's jobs do not run on the daythey were selected. BACKLOG occurs on both schedule and job base records.The value defined for a schedule applies to all jobs in that schedule unless youspecify a different value on a job base record. Since most sites usually wantjobs to carry over, leave BACKLOG = YES.

A complete explanation of how backlog works in Unicenter CA-Schedulerappears later in this chapter.

AUTO-REPLY MESSAGES controls the automatic console replies for jobs. Touse this feature, auto-reply support must be selected in the UnicenterCA-Scheduler generation options (see the CAIJGEN macro in the UnicenterCA-Scheduler Systems Programmer Guide). This optional feature is discussedlater in the chapter. Leave AUTO-REPLY MESSAGES = N.

SCHEDULE NAME is the only field on a schedule record that requires input.To name a schedule, type up to 8 characters (any combination of letters andnumbers). Name this schedule BACKUP. The cursor is already positioned atthe SCHEDULE NAME. Type BACKUP but do not press Enter yet.

The USERS field defines who can control and maintain this schedule. If youleave this field blank, BACKUP becomes a public schedule that any user with awrite password can control or maintain. However, you may want to restrictthat capability to just a few users. With the USERS field, you define whichGeneral users are authorized to control and maintain this schedule. Users withSupervisor or Manager authority do not need to be authorized by the USERSfield because they can access all schedule definitions.

To be sure that you can work with this record later, tab down to the fieldcalled USERS and type in your userid.

When you are defining schedule records, you will tab from field to field untilyou have supplied all the values necessary. The other fields you see on thispanel do not require input. They are discussed later in the chapter. Finishdefining the backup schedule now.

The one distinctive thing about backup jobs is that they usually run at night.Unicenter CA-Scheduler can continue that routine for you. Specify a value forEARLIEST START TIME using 24-hour clock notation. For example, you canhold the backup schedule until 11 p.m. by setting EARLIEST START TIME to2300. Or, type 0100 to keep backup jobs from running before 1 a.m.



To save this schedule record, press Enter. Unicenter CA-Scheduler responds bydisplaying the following panel:


===> MASTER - WR

CONNECT : 4�

DEFINE SBR LASTUSER=userid,NAME=BACKUP,USERIDS=(userid),ERLYTIME=23��

CACU�18I SBR BACKUP HAS BEEN ADDED

PF1=HELP

� �

If a schedule by that name already exists, Unicenter CA-Scheduler displays themessage:

CACU�15E DEFINE SBR BACKUP DUPLICATE RECORD

If that message appears, try giving your schedule another name.

SBR in the messages preceding stands for Schedule Base Record, which is theone required schedule record. Optional schedule records store other processinginformation.

You will see how to define these other types of schedule records later in thischapter. Press the Clear key to return to the Schedule Maintenance menu.

The Schedule Defines

Criteria record (SCR) ■ The days when this schedule isselected

■ Predecessors for this schedule

Reason code record (SRC) Different times pertaining to theschedule (early and late start times,completion of deadlines, time limits)depending on the reason why it wasselected that day (based upon its criteriarecord)

Information record (SIR) Information that will be printed onschedule reports

Message record (SMR) Messages to send users, informing themof the schedule's progress



3.1.3 Checking Default Values for Schedule Base RecordsJust as schedule options simplify the work of defining jobs, installation optionsmake defining schedules easier. Only one field in the schedule record requiresinput: SCHEDULE NAME. All the other fields have defaults. To see whichschedule defaults were selected when Unicenter CA-Scheduler was installed atyour site:

■ Create a schedule record consisting of defaults.■ Then display that record.

Most of the backup schedule you created consists of defaults, so just displaythat schedule base record to see your site's default values.

The first three functions on the Schedule Maintenance menu allow you todisplay a schedule base record:


===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------









PF1=HELP

� �

Use option 2 because it is quicker. When you select option 2, UnicenterCA-Scheduler also expects you to specify the name of an existing schedule inthe command area. To display the base record for your backup schedule, type2 in the command area followed by a comma and the schedule's name,BACKUP. For example, type 2,BACKUP and press Enter.

Unicenter CA-Scheduler responds by displaying that schedule base record:



� � SCHD-SU ��SCHEDULE DISPLAY�� CA-SCHEDULER

===> _ MASTER - WR

CONNECT : 4�

SCHEDULE NAME : BACKUP

SCHED PRIORITY: 5�

AUTO SELECT : NO

DATETABLE NAME: SKIP : ��


NODE ID: : STAGE JCL : NO

NODE SYSID : USE SIMTIME: NO


USERS: userid

LIBRARY TYPE : CMS

POWER CLASS : A

POWER PRIORITY: POWER USER :


EARLIEST START TIME : ��23�� MAXIMUM EXECUTION TIME : ��

MUST START BY TIME : �� COMPLETION DEADLINE TIME : ��

RECS= SBR: Y SCR: N SRC: N SIR: N SMR: N PF1=HELP

� �

Notice that this panel displays more values than you specified for the backupschedule. Many of the fields contain zeros, so skip those now. Instead,concentrate on the fields that have nonzero values. Since your site's optionsare probably different from Computer Associate's, the values you seedisplayed are not the same as those shown preceding. Therefore, take amoment to jot down your site's significant default values for schedules in thealphabetical chart following.

Option Purpose Value

POWER CLASS Identifies the POWER CLASSthat is to appear on jobdefinitions for all jobs in thisschedule.

LIBRARY TYPE Identifies the library specifiedas a generation option. Itcontains the JCL for productionjobs.

RECS Shows which types of schedulerecords have been defined. Sofar, the schedule BACKUP onlyconsists of the schedule baserecord you are looking at (SBR:Y). The other types of schedulerecords have not been definedfor that schedule yet.



Check the values of these defaults to be sure they accurately represent yoursite. Having the appropriate defaults will make defining schedules mucheasier. To change installation options, speak with your systems programmer.

Option Purpose Value

RUN ON SYSID In a multi-CPU environment,identifies the SYSID of the CPUthat automatically selects andsubmits the jobs in thisschedule. Leave this fieldblank when you beginimplementing UnicenterCA-Scheduler at your site.RUN ON SYSID has no defaultin a single CPU environment.

SCHED PRIORITY Determines the order in whichschedules are PRIORITYevaluated when determiningwhich schedules can start. Mostsites ignore this field and useother methods for sequencingtheir workload.

STAGE JCL Controls whether the JCL forthese jobs is copied into thestaging library for editing priorto submission. Since most jobsdo not require staging, STAGEJCL is usually NO.

USE SIMTIME Can affect when this scheduleis started. Most sites ignorethis field and use othermethods for staggering theirworkload. Set USE SIMTIME =NO to ignore this field.

3.1.4 Learning the Basics About a Schedule RecordUnicenter CA-Scheduler provides many optional schedule fields so you candefine any characteristics common to the jobs in this schedule. Following iswhat characteristics schedule records can define. Then how to analyze yourschedules to find out which characteristics the majority of jobs in eachschedule have in common is described.



3.1.4.1 When Will this Schedule Be Selected?

When Unicenter CA-Scheduler runs autoscan, it automatically selects that day'sworkload. The selection process is a loop consisting of two steps:

■ First, Unicenter CA-Scheduler finds a schedule to select. Only scheduleswith AUTO SELECT = YES are eligible for automatic selection. If AUTOSELECT = YES, Unicenter CA-Scheduler checks the selection criteriadefined for that schedule to see whether that schedule should be selectedtoday.

■ Then it scans the selection criteria of every job in that schedule to select thejobs belonging in that day's workload. When Unicenter CA-Schedulerfinishes with that schedule, it is ready to find another it can automaticallyselect today.

Jobs can only run on days when their schedules are selected. Jobs that rundaily must belong to schedules that are selected every day. That is why weadvise you to group an application's daily jobs into one schedule.

Initially, the default for AUTO SELECT prevents schedules from beingautomatically selected. That gives you time to test schedule and job definitionsto be sure jobs run on the appropriate days. When you are satisfied with thosedefinitions, set AUTO SELECT = YES to have Unicenter CA-Scheduler includethat schedule among those it evaluates at autoscan time.

Three more fields control when schedules are selected: DATETABLE NAME,SCR, and SKIP.

■ To select a schedule every day, leave DATETABLE NAME blank and donot define a schedule criteria record (leave SCR: N).

■ To select a schedule only on certain days, you will need to define aschedule criteria record (SCR). That criteria record may contain keywordsthat refer to days defined in a datetable. If that datetable is the default, youcan leave the DATETABLE field blank. Otherwise, specify the appropriatedatetable name. See the chapter "Criteria Language" for detailedinstructions on how that is done.

■ Once you have set AUTO SELECT = YES, you may want to deactivate aschedule for a while. You can use this advanced technique to handle suchexceptional situations, but normally you will not use the SKIP field.

Rather than setting AUTO SELECT = NO again, use the SKIP field to stopselecting this schedule in autoscan for a while. Specify how many times youwant to skip this schedule when it ordinarily would be selected. For example,suppose a schedule that normally runs on Friday instead ran on Tuesday thisweek. Specify SKIP = 1 to prevent that schedule from running this Friday.Every time Unicenter CA-Scheduler skips over a schedule it normally wouldhave selected, it decrements the value in the SKIP field by one until SKIP onceagain is zero.



3.1.4.2 When Will a Schedule's Jobs Actually Run?

As Unicenter CA-Scheduler selects the day's workload, it organizes the work,grouping each schedule's jobs together, but it does not line schedules up in theorder they are selected. Instead, Unicenter CA-Scheduler allows you to controlthe work sequence with several schedule parameters:

■ SCR predecessors ■ USE SIMTIME■ EARLIEST START TIME■ SRC start times■ COMPLETION DEADLINE TIME

■ SCHD PRIORITY

Defining predecessors forces Unicenter CA-Scheduler to witness a specificevent before starting any jobs in that schedule. Predecessors can be a variety ofevents such as

■ The start or end of another schedule or job■ The close of an output data set or generation data group■ A user-defined event that you can control using a global parameter■ An event that occurred sometime in the past

When schedules must run in a certain order, define schedules as predecessorsto one another using the schedule criteria record (SCR). See the chapter"Criteria Language" for instructions on how that is done.

When Unicenter CA-Scheduler lines up the work to be processed during theday, the first factor it considers is each schedule's predecessors. ThenUnicenter CA-Scheduler compares the start times for schedules, putting thosethat can start earliest ahead of ones that start later. Schedules withoutpredecessors and start times go to the top of the list because nothing isdelaying them, so they start right after autoscan. SCHD PRIORITY is the lastfactor Unicenter CA-Scheduler considers when organizing the workload andonly serves to sort schedules that have equivalent values for all the otherfactors.

Unicenter CA-Scheduler gives you three ways of specifying when jobs start.To see which method you chose, Unicenter CA-Scheduler checks the value ofUSE SIMTIME. A value of YES causes Unicenter CA-Scheduler to start thatschedule at the time shown on the Simulated Execution Schedule.

If you set USE SIMTIME=YES, Unicenter CA-Scheduler ignores any other starttimes you may have specified. Unicenter CA-Scheduler sites that have definedtheir resources in great detail and run the vast majority of their productionload under Unicenter CA-Scheduler control could set USE SIMTIME=YES. Theaccuracy of their history data and resource definitions would result insimulations that project optimal start times for schedules. However, mostUnicenter CA-Scheduler sites leave USE SIMTIME=NO.



If USE SIMTIME = NO, Unicenter CA-Scheduler checks to see what start timesyou have specified on the schedule record. You specify the earliest possibletime a schedule can start using a 24-hour clock. For example, an early time of1400 allows a schedule to start no earlier than 2 p.m. in the afternoon. Butwhat if that schedule should not start until some day in the future? UnicenterCA-Scheduler also allows you to specify start times with a prefix showing howmany days to delay the start of those jobs. For example, a start time of 031400delays the start of that schedule until 2 p.m., three days after that schedulewas originally selected.

If USE SIMTIME=NO, Unicenter CA-Scheduler checks to see if a schedule'sreason code record contains start times. Since start time is an important factorin sequencing your workload, Unicenter CA-Scheduler gives you flexibility.For example, a schedule may need to start at different times on different days.This is not a problem because Unicenter CA-Scheduler allows you to definedifferent reasons for selecting a schedule on its criteria record (SCR). Eachreason can cause that schedule to be selected on a different day. Once youhave defined reasons on the SCR, you can specify a different start time foreach reason. A schedule's alternate start times are stored on its reason coderecord (SRC).

The last place Unicenter CA-Scheduler looks for a start time is EARLIESTSTART TIME. If you do not specify a start time anywhere, UnicenterCA-Scheduler only delays starting this schedule until its predecessorconditions are satisfied.

When Unicenter CA-Scheduler organizes the work to be processed each day,first it considers each schedule's predecessors. Then it checks start times. Ifseveral schedules have the same predecessors and start times, UnicenterCA-Scheduler puts those with earlier deadlines ahead of the others. Work thathas to be finished sooner goes first. You define deadlines in fields calledDEADLINE TIME on the reason code record or COMPLETION DEADLINETIME on the schedule base record.

Finally, Unicenter CA-Scheduler checks one last field when it's organizing theworkload. Schedules with the same predecessors, start times, and deadlines aresorted by SCHED PRIORITY: schedules with the highest priority go first.Priorities range from a high of 01 to a low of 99.

If, after checking all these fields, Unicenter CA-Scheduler finds a group ofschedules with equivalent values in all these fields, it lines up those schedulesin alphabetical order. The chart following summarizes how UnicenterCA-Scheduler organizes its workload.

Sequence By Using On The

Predecessors Criteria language Criteria record



What if Unicenter CA-Scheduler does not complete some schedules in theday's workload? Any jobs that are running when the next autoscan occurs arealways automatically backlogged, but what happens to jobs that have notstarted yet?

BACKLOG fields control what happens if a schedule's jobs do not run on theday they were selected. BACKLOG occurs on both schedule and job baserecords. The value defined for a schedule applies to all jobs in that scheduleunless you override it by specifying a different value on a job base record.

Jobs that have BACKLOG=YES on their job base record (or default toBACKLOG=YES on the schedule's base record) will always be backlogged ifthey have not completed or been canceled by the next autoscan.

Jobs with BACKLOG=NO on their job base record (or default toBACKLOG=NO on their schedule's base record) will be removed from theworkload if they are still waiting at the next autoscan.

If that schedule would also be selected tomorrow, the second set of jobs isadded to the workload after the backlogged schedule has completed and beenpurged.

Sequence By Using On The

Start times USE SIMTIME = YESEARLY TIMEsEARLIEST START TIME

Base recordReason code recordBase record

Deadline DEADLINE TIMEsCOMPLETION DEADLINETIME

Reason code recordBase record

Priority SCHED PRIORITY Base record

Alphabetical order SCHEDULE NAME Base record



3.1.4.3 What JCL Does Unicenter CA-Scheduler Submit for These Jobs?

JCL for jobs under Unicenter CA-Scheduler control can be manually submittedto the reader queue, but Unicenter CA-Scheduler can even automate that stepfor you. Unicenter CA-Scheduler can retrieve JCL directly from

■ AllFusion CA-Panvalet, ■ AllFusion CA-Librarian ■ User-defined libraries■ A Unicenter CA-Driver procedure library■ A CMS member■ An ICCF member■ An SLI source member■ A PROC VSE procedure library■ Allfusion CA-Vollie library member

■ CONDOR

However, sometimes production JCL requires editing before it can besubmitted. Two schedule fields tell Unicenter CA-Scheduler where to find theJCL to submit for jobs in that schedule: STAGE JCL and LIBRARY TYPE.

Unicenter CA-Scheduler first determines which library contains the JCL forthese jobs by checking the LIBRARY TYPE. Then Unicenter CA-Schedulerchecks to see if this JCL requires editing. Since you can override a schedule'svalue for STAGE JCL at the job level, Unicenter CA-Scheduler checks bothschedule and job base records. If STAGE JCL = NO, Unicenter CA-Schedulerknows it can submit the production JCL directly to the CPU. However, ifSTAGE JCL = YES, Unicenter CA-Scheduler copies the production JCL into thestaging library as soon as the job is selected. After that JCL has been editedand staging is complete, Unicenter CA-Scheduler submits the edited JCL forprocessing.

In the case where the JCL for a specific job is stored in a CA-Panvalet or OWLlibrary, Unicenter CA-Scheduler will submit a batch job that is a library accessjob. This job will run in a partition and extract the actual job JCL from thelibrary and submit this JCL to POWER to be run.

3.1.4.4 Which CPU Should Control These Jobs?

The RUN ON SYSID field is used only in a multi-CPU environment. Whenspecified within a schedule definition, the RUN ON SYSID field valuedesignates a POWER SYSID that is then associated with the CPU that willcontrol and submit the jobs within that schedule.

Do not specify a RUN ON SYSID within a schedule definition if you have aUnicenter CA-Scheduler Master/Slave, multi-CPU environment. Thisenvironment determines the controlling CPU from the CAIJGEN installationmacro.



If your site has one CPU perform scheduling for all of them, it is called yourMaster CPU. It is the first CPU listed on the SYSID= installation generationmacro parameter. Since that value is the default for a schedule's RUN ONSYSID, you must leave that field blank on the schedule base record if your sitehas a Master CPU.

NODE ID and NODE SYSID are only used at sites that are part of a networkthat uses POWER/VSE at each node and Unicenter CA-Scheduler on eachCPU at every node. Only use NODE SYSIDs if there are multiple CPUs usingshared POWER spool at a NODE ID. Also notice that values for these fieldsmean different things on schedule and job records.

NODE ID on the schedule record indicates the default NODE ID for the jobs inthat schedule. A job's NODE ID identifies which node the job's JCL issubmitted to. If a job runs on the node specified as the schedule's NODE ID,you can leave NODE ID blank on the job record. To submit a job to anothernode, specify its node ID on the job base record.

Suppose there are multiple CPUs at this node. Use NODE SYSID to specify aparticular CPU if the node has multiple CPUs that each run UnicenterCA-Scheduler and share a POWER location. For NODE SYSID, enter thePOWER SYSID of the remote CPU where the job is to run. NODE SYSID isonly valid if NODE ID is also specified on the same record. When NODE IDand NODE SYSID are given, that job base record's value for RUN ON SYSID isignored.

3.1.4.5 What Schedule Fields Are Used for Simulation?

Simulation is one of Unicenter CA-Scheduler's most powerful features. Withoutactually running your workload, Unicenter CA-Scheduler can produce reportsshowing

■ Which jobs would be selected■ What resources would be required■ When and where each job would be processed■ How heavily each device would be utilized■ Which jobs would be late■ Which jobs would carry over to the next day

Such a planning tool gives Unicenter CA-Scheduler users an advantage whendealing with the situations that confront a data center daily. Therefore, it isworth your while to supply the values needed for simulation.

AVERAGE TIME allows you to specify the average processing time in days,hours, and minutes. Leading zeros can be omitted. This optional field is onlyused to prepare simulation reports. Use this field to have simulation reportsproject the overall effect of a change in average processing time for thisschedule. If a time is not specified here, simulation uses the schedule's actualaverage processing time based on historical $JOBACCT data.



Unicenter CA-Scheduler uses POWER CLASS to assign jobs to partitions onthe simulation reports.

3.1.4.6 What General Users Can Update this Schedule Record?

If anyone with General authority can update this schedule, leave the USERSfield blank so this becomes a public schedule. Otherwise, specify up to eightuserids separated by commas.

Example:

USERS: acctlbj,acctpas,accttfa,acctctrl

3.1.4.7 What Happens When Schedules Run Late?

Unicenter CA-Scheduler helps you manage your production workload byalerting you to potential problems as quickly as possible. Therefore, whenUnicenter CA-Scheduler knows jobs are running late, it will warn you byissuing messages. You can control when the messages are issued and whoreceives them using fields on the schedule record.

SBR: schedule base recordSRC: schedule reason code record

You specify times for these fields in different ways:

MAXIMUM EXECUTION TIME tells Unicenter CA-Scheduler how long itshould take to process this schedule. The chart following illustrates thedifferent ways you can specify maximum execution time. Notice that leadingzeros can be omitted.

If You WantNotification

When Schedules Specify A ValueFor

On The

Start late MUST TIMEs orMUST START BY TIME

SRCSBR

Actually miss deadlines DEADLINE TIMEs orCOMPLETION DEADLINETIMER

SRCSBR

Run too long MAXIMUM TIMEs orMAXIMUM EXECUTION TIMER

SRCSBR

A Value Of Uses ThisNotation

And Means The Schedule ShouldFinish

30 mm Thirty minutes after it starts

200 hhmm Two hours after it starts



Use a 24-hour clock to specify MUST START BY TIME and COMPLETIONDEADLINE TIME. The chart following shows that you can omit leading zerosand you can extend the 24-hour clock by days.

Warning messages are sent to the operator if OPERATOR was specified on theMSG installation option. If you want messages sent to other userids, specifythem in the schedule's optional message record (SMR).


And Means The Schedule ShouldFinish

10200 ddhhmm The next day two hours later thanit started (26 hours later)


And Means Late Messages WillBe Issued

930 hhmm After 9:30 a.m. that day

1400 hhmm After 2 p.m. that day

11800 ddhhmm After 6 p.m. the next autoscanday

3.1.4.8 Creating Optional Schedule Records?

The RECS fields at the bottom of schedule panels fulfill two functions:

■ The values displayed show whether each type record already exists for thisschedule. N means that type record has not been defined yet.

■ The fields allow you to input commands that will branch to these records.The chart following shows what these commands can do.

The chart following explains the purpose of each record type.

If The Current Value Is Enter To

N C Create that record

Y AD

Alter that recordDisplay that record



The next topic covers the optional schedule records in detail.

If You Want To Select This Record By TypingC After

Define -the days on which the scheduleis selected -predecessor conditions that mustbe satisfied

shedule

criteria

SCR:

Assign different times to theschedule when it is selected fordifferent reasons

schedulereasoncode

SRC:

Add information that will beprinted on schedule report

scheduleinformation

SIR:

Send messages to users informingthem of the schedule's progress

schedulemessage

SMR:


3.2 Defining Optional Schedule Records


Now that you are familiar with the fields on the schedule base record, theoptional schedule records will be described. Do that by updating the schedulebase record. First check which option on the Schedule Maintenance menuallows you to update existing schedule records.


===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------









PF1=HELP

� �

The preceding panel informs you to use option 3 to change an existing record.Notice, however, that Unicenter CA-Scheduler also expects you to state whichschedule you want to change. Therefore, when you type 3 in the commandarea, follow it with a comma and the name of the schedule you want toupdate.

Next, change the backup schedule you defined. If you defined a schedulenamed BACKUP, enter 3,BACKUP in the command area to retrieve thatrecord.

If you are a user with General authority, Unicenter CA-Scheduler only permitsyou to change that schedule record if:

■ This is a public schedule or■ Your userid is listed as a value in that schedule's USERS field

If an unauthorized user tries to change an existing schedule definition,Unicenter CA-Scheduler displays the message:

CACO229E USER NOT AUTHORIZED FOR THIS SCHEDULE

If your authority level permits you to alter that schedule record, UnicenterCA-Scheduler displays the Schedule Alter panel.



� � SCHD-SU ��SCHEDULE ALTER �� CA-SCHEDULER

===> _ MASTER - WR

CONNECT : 4�



AUTO SELECT : NO



NODE ID : STAGE JCL : NO



USERS: userid

LIBRARY TYPE : CMS

POWER CLASS : A





RECS= SBR: Y SCR: N SRC: N SIR: N SMR: N PF1=HELP

� �

To change any value displayed on this panel, tab to it, type in a new value,and press Enter. If the new value does not completely overwrite the displayedvalue, use the spacebar to blank out the rest of the field.

If desired, you can use this panel to eliminate any value in the SBR withoutsupplying a new one. Depending on the field type, either fill the field withzeros or type NULL and blank out the rest of the field. If applicable, the valuewill revert to the one defined in the CAIJGEN macro.

For example, what if you do not want an EARLIEST START TIME anymore?Or you want to make this a public schedule?

■ To cancel a previously specified start time, fill in the field with six zeros.

■ To delete the value in the USERS field, type NULL and blank out the restof the field. This causes Unicenter CA-Scheduler to eliminate the valuepreviously defined for USERS and makes BACKUP a public schedule.

While you are altering the schedule base record, you can also create optionalschedule records by changing RECS values. Currently, the RECS values showyou which types of records already exist:

■ SBR: Y means the schedule base record has been defined.■ Ns after the other abbreviations mean those record types do not exist.

You can tab to any RECS value and enter codes that allow you to create, alteror display those schedule records.

Enter For Which Is This Type Of Record

C to create SCR Schedule criteria record



The following text explores these optional schedule records by creating one ofeach type. SBR: Y means a schedule base record already exists. To createoptional schedule records, type a C in place of the Ns following SCR, SRC, SIRand SMR. Then press Enter.

When you change the values of RECS fields to A, C or D and press Enter,Unicenter CA-Scheduler immediately branches to panels relating to thoserecords. The order in which they appear corresponds to the order they arelisted on schedule panels which means the Schedule Criteria Record (SCR) willappear first if you have selected it.

Enter For Which Is This Type Of Record

A to alter SRC Schedule reason code record

D to display SIRSMR

Schedule information recordSchedule message record

3.2.1 Defining a Schedule Criteria RecordWhen you select SCR, Unicenter CA-Scheduler displays an editor panel whereyou define the schedule criteria record. This record tells UnicenterCA-Scheduler when to select this schedule for processing and whatpredecessors must be satisfied before this schedule can start.

If you do not define a criteria record for a schedule, that schedule will beselected every day and the schedule will have no predecessors.

To move the cursor into the area where you define criteria, press the TAB keyonce.

� � SCHD-SCRE DEF C= S=BACKUP CA-SCHEDULER

===>

RANGE=�1-72

1...+....1....+....2....+....3....+....4....+....5....+....6....+....7...

��1

��2

��3

��d

��7

��8

��9

��17

� �

There are two methods of defining when jobs are to be run:

■ One method uses calendars. If a datetable was not specified on theschedule's base record, Unicenter CA-Scheduler allows you to enter thename of a calendar after C= on the top line of this panel. Calendarsidentify which days a job should run. If a calendar name appears on this



panel, that alone controls selection. When a calendar name is given, thecriteria statement only defines the schedule's predecessors.

■ The other method uses Unicenter CA-Scheduler's criteria language tocontrol selection and define predecessors. You define criteria statements byentering data anywhere on lines 1 through 19 on this panel.

Most sites run backups daily, so you probably want this schedule to beselected every day. However, on the days your databases are backed up, youwant to run backups after updating our site's databases. Therefore, theDBUPDATE schedule should be a predecessor to the BACKUP schedule. Howthe criteria language would handle this situation follows.

Start by typing SCD DBUPDATE OR on the first line and pressing RETURN.Then type DAILY on the second line.

Although it really does not matter where on this panel you enter your criteria,we recommend you type each reason for selecting a schedule on a separateline because it is easier to see which reasons here correspond with fields on theschedule's reason code record. If there is more than one reason for selecting aschedule, each reason ends with OR (except the last one).

Note: Multiple ORs can be grouped into a single reason code by placingparentheses around this reason. That means (MON OR FRI) is onereason while MON OR FRI defines two reasons.

When you write criteria, you can embed comments anywhere by using /* as abeginning delimiter and */ as an ending delimiter. These delimiters can appearon different lines if the comment is longer than one line.

� � SCHD-SCRE DEF C= S=BACKUP CA-SCHEDULER

===>

RANGE=�1-72

1...+....1....+....2....+....3....+....4....+....5....+....6....+....7...

SCD DBUPDATE OR /� END OF SCHEDULE DBUPDATE OR �/ ��1

DAILY /� EVERY DAY �/ ��2

��3

��4

��5

��6

��7

��8

��9

��1�

��11

��12

��13

��14

��15

��16

��17

��18

��19

1...+....1....+....2....+....3....+....4....+....5....+....6....+....7...

� �



A review of what the criteria statement SCD DBUPDATE OR DAILY doesfollows. The OR without parentheses defines two reasons why this schedulecan be selected. Each reason will be examined independently:

■ This schedule is selected whenever the schedule named DBUPDATE isselected, and on those days, the completion of DBUPDATE is apredecessor to the backup schedule. All DBUPDATE jobs in the workloadmust finish before any backup jobs can begin.

■ OR DAILY causes Unicenter CA-Scheduler to select the backup schedulewhenever DBUPDATE is not selected. On those days, this schedule has nopredecessors.

That means Unicenter CA-Scheduler selects the backup schedule every day.And on days when DBUPDATE is selected, DBUPDATE is a predecessor toBACKUP.

Does the order in that criteria statement matter? Would the statement

DAILY OR SCD DBUPDATE

yield the same result? Both statements cause the backup schedule to run on thesame days with the same predecessor. But there is a subtle differenceinvolving the reasons schedules are selected. Suppose DBUPDATE runs onMondays, Wednesdays and Fridays. Making DAILY the first reason in thecriteria statement means this schedule is always selected for that reason, butputting DAILY last

(SCD DBUPDATE OR DAILY)

means that schedule sometimes is selected for the second reason.

Unicenter CA-Scheduler has an optional record that allows you to controlschedules differently depending on the reason why it was selected. Therefore,make DAILY the second reason to implement different start times ormaximum durations for each reason. The next topic explains how to do thatusing the schedule's optional reason code record.

For complete information on coding criteria statements, see the chapter"Criteria Language."

To save this criteria record and leave this panel, type FILE in the commandinput area. (Otherwise, you could leave the panel without saving this criteriarecord by typing QUIT.)

All of the editor commands are inthe appendix "Editor Commands" in theUnicenter CA-Scheduler Reference Guide, Part 2. The FILE command causesUnicenter CA-Scheduler to immediately create that schedule's criteria record.After you press ENTER, Unicenter CA-Scheduler displays the following panel,which confirms that the record has been created:




===> MASTER - WR

CONNECT : 4�

DEFINE SCR NAME=BACKUP,CRI='

SCD DBUPDATE OR

DAILY'

CACU�18I SCR BACKUP HAS BEEN ADDED

PF1=HELP

� �

To advance to the next panel, press Enter.

3.2.2 Defining a Schedule Reason Code RecordUnicenter CA-Scheduler enables you to modify reasons for selecting a scheduleusing the schedule's reason code record. Unicenter CA-Scheduler can vary thefollowing fields based upon the reason a schedule is selected:

■ AVERAGE TIME■ EARLIEST START TIME■ MUST START BY TIME■ COMPLETION DEADLINE TIME■ MAXIMUM EXECUTION TIME

The Reasons Definition panel allows you to specify up to 16 different valuesfor these five fields found on the schedule's base record. UnicenterCA-Scheduler matches these values with reasons defined on the schedule'scriteria record: the first value here applies to the first reason for selection, andso on. Enter the displayed values under EARLY TIME LIST and MAXIMUMTIME LIST.

� � SCHD-SRC ��REASONS DEFINITION�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

SCHEDULE NAME : BACKUP PROTOTYPE SCHEDULE NAME :

AVG TIME LIST:

�1 �2 �3 �4 �5 �6 �7 �8

�9 1� 11 12 13 14 15 16

EARLY TIME LIST:

�1 22�� 2 23�� 3 �4 �5 �6 �7 �8

�9 1� 11 12 13 14 15 16

MUST TIME LIST:

�1 �2 �3 �4 �5 �6 �7 �8

�9 1� 11 12 13 14 15 16

DEADLINE TIME LIST:

�1 �2 �3 �4 �5 �6 �7 �8

�9 1� 11 12 13 14 15 16

MAXIMUM TIME LIST:

�1 1�� 2 3� �3 �4 �5 �6 �7 �8

�9 1� 11 12 13 14 15 16

RECS= SBR: Y SCR: Y SRC: N SIR: N SMR: N PF1=HELP

� �



The preceding panel shows different values defined for two fields. How doesthis relate to the criteria statement SCD DBUPDATE OR DAILY?

■ On days when DBUPDATE runs, the backup schedule can begin any timeafter 2200 (10 p.m.) and should take no more than one hour to run.

■ On other days, you might run fewer backup jobs, so the schedule can startlater (no earlier than 11 p.m.) and should only take 30 minutes.

Before you actually create this reason code record, examine all five fields onthis panel.

AVG TIME allows you to give simulation more precise average processingtimes for this schedule. The fields here correspond to different reasons why theschedule is selected. If you do not specify AVG TIME for the reason why theschedule was selected, simulation uses AVERAGE TIME on the schedule baserecord. If that field is also blank, simulation uses the actual average processingtime for this schedule derived from historical data.

EARLY TIME allows you to specify different start times for each reason aschedule is selected. If you leave these fields blank, Unicenter CA-Scheduleruses the value on the schedule base record every time the schedule is selected.These values override EARLIEST START TIME on the schedule base record.

MUST TIMEs tell Unicenter CA-Scheduler to issue late messages at differenttimes for each reason schedules are selected. Suppose the backup schedule wasselected today for the second reason: DAILY. Then Unicenter CA-Schedulerwill issue a late message if the backup schedule has not started by the timespecified in the second MUST TIME field. These values override MUSTSTART BY TIME on the schedule base record.

DEADLINE TIMEs tell Unicenter CA-Scheduler to issue late messages if thisschedule is not finished by the deadline specified. Specify values here if youwant to define different deadlines for each reason the schedule was selected.These values override the COMPLETION DEADLINE TIME you may havespecified on the schedule base record.

MAXIMUM TIMEs set limits on how long a schedule should run. If schedulestake longer, Unicenter CA-Scheduler will issue a late message. Specify valueshere if you want to define different durations for each reason the schedule wasselected. These values override the MAXIMUM EXECUTION TIME specifiedon the schedule base record.

Now that you are familiar with these fields, finish creating the reason coderecord. After you have finished filling fields on the panel, press Enter.Unicenter CA-Scheduler immediately sends this information to the databaseand confirms this with the message:




===> MASTER - WR

CONNECT : 4�

DEFINE SRC NAME=BACKUP,ERLY�1=22��,ERLY�2=23��,MAX�1=1��,

MAX�2=3�

CACU�18I SRC BACKUP HAS BEEN ADDED

PF1=HELP

� �

Use of reason codes provides you with tremendous scheduling flexibility. Toadvance to the next panel, press Enter.

3.2.3 Defining a Schedule Information RecordAll the schedule records you have defined so far contain information thataffects how Unicenter CA-Scheduler automates production at your site.Usually, this record does not. A schedule's information record is purely foryour use. It stores descriptive information about this schedule that helps yourstaff wrap up the work Unicenter CA-Scheduler began for you.

A schedule's information record only affects processing if your site hasimplemented an optional simulation user exit. If so, the EXITPARM definedhere is passed to that user exit during simulation.

� � SCHD-SIR ��INFO DEFINITION�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

SCHEDULE NAME : backup PROTOTYPE SCHEDULE NAME :

DESCRIPTION : copies data sets to tape

COMMENT : rerun if this abends

EXITPARM

FORM : QUANTITY :

NOTIFY : j smith RESPONSIBILITY: j smith

VERIFY :

SPECIFICATION :

DESTINATIONS-1: tape 2:library 3: 4:

5: 6: 7: 8:

DELIVERABLES

1: backup tapes 2: 3: 4:

5: 6: 7: 8:

RECS= SBR: Y SCR: Y SRC: Y SIR: N SMR: N PF1=HELP

� �

SCHEDULE NAME The only required value in an information record.The other fields are optional and most allow you toinput anything you feel is appropriate. These fieldnames are intentionally general so you can record theinformation you think will be most useful.



EXITPARM EXITPARM adjusts the default class or defaultaverage processing time of all jobs in this scheduleduring simulation. Unicenter CA-Scheduler passesthis value of up to 16 bytes to a user exit.

VERIFY Requires a specific response. Your choices are toleave the field blank, or type in YES or NO. Use thisfield for anything you want by setting up your ownstandard for this field.

Next, create the information record shown preceding. As you tab from field tofield, type in the data displayed on the panel preceding. After you have inputthat information, you are ready to create the information record.

After you have filled in the panel, press Enter to save the information recordfor that schedule. Unicenter CA-Scheduler confirms that it stored thatinformation by displaying the following panel:


===> MASTER - WR

CONNECT : 4�

DEFINE SIR NAME=BACKUP,DESC='COPIES DATA SETS TO TAPE',

COMMENT='RERUN IF THIS ABENDS',NOTIFY='J SMITH',

RESP='J SMITH',DEST1='TAPE',DEST2='LIBRARY',

DEL1='BACKUP TAPES'

CACU�18I SIR BACKUP HAS BEEN ADDED

PF1=HELP

� �

To view the next panel, press Enter. That displays the panel that defines thelast optional schedule record.

3.2.4 Defining a Schedule Message RecordThe last optional schedule record helps implement Unicenter CA-Scheduler'smessage capability by notifying users of a schedule's progress. UnicenterCA-Scheduler is prepared to notify users of four events concerning schedules:

■ When schedules start■ When they end■ When they are late■ When they run too long



� � SCHD-SMR ��MESSAGE DEFINITION�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

SCHEDULE NAME : backup PROTOTYPE SCHEDULE NAME :

SEND ALL MESSAGES TO : opctrl

SEND START MESSAGES TO :

SEND END MESSAGES TO :

SEND LATE MESSAGES TO : prodctrl,opctrl

RECS= SBR: Y SCR: Y SRC: Y SIR: Y SMR: N PF1=HELP

� �

You can initiate those three kinds of progress reporting by filling in one fieldon the schedule message record. Do this by typing the userid OPCTRL in thefield SEND ALL MESSAGES TO. If that is the only field you fill in on thisrecord, all three kinds of message go to that id.

If you fill in other fields on this record, it affects which messages go toOPCTRL. OPCTRL will get only those messages not routed elsewhere. If youreally want OPCTRL to get all messages, be sure to include that ID in everyuserid list you specify on this panel.

You can list up to four userids separated by commas in any of these fields. Tosend any kind of message to the master console, specify OPERATOR as one ofthe userids.

You can also specify MAILBOX as one of the userids, and the messages will besent to a common mailbox where they can be viewed using the ReportingFacility panel. The following text describes sending late messages to theuserid PRODCTRL. If you only specify PRODCTRL as the recipient of latemessages, OPCTRL will not see the late messages. To guarantee that bothuserids see late messages, list both of them in this field with a commaseparating them.

Then press Enter to save the last optional schedule record. UnicenterCA-Scheduler responds by displaying the following message.


===> MASTER - WR

CONNECT : 4�

DEFINE SMR NAME=BACKUP,MSG=OPCTRL,LATEMSG=(PRODCTRL,OPCTRL)

CACU�18I SMR BACKUP HAS BEEN ADDED

PF1=HELP

� �

To view the next panel, press Enter. Then press Clear to return to the ScheduleMaintenance menu.


3.3 Copying Schedules


Now that you have created one schedule, create another one just like it, onlymuch more quickly. You can do that by copying the new schedule from anexisting schedule.

Begin by using option 1 of the Schedule Maintenance menu. Notice thatUnicenter CA-Scheduler expects you to specify select criteria when you chooseoption 1. We will use the schedule's name. Try typing 1,BACKUP in thecommand area and pressing ENTER.

Unicenter CA-Scheduler responds by displaying the Schedule Directory panel:

� � SCHD-SD ��SCHEDULE DIRECTORY�� CA-SCHEDULER

===> _ MASTER - WR

CONNECT : 4�

B C R I M

SCHEDULE PRTY JOBCT PCLASS PPRTY PSYS AUTOST R R C R R

BACKUP 5� � A NO Y Y Y Y Y


PF1=HELP

� �

The Ys in the five columns at the right indicate that the BACKUP schedule hasa:

■ Schedule base record (BR)■ Schedule criteria record (CR)■ Schedule reason code record (RC)■ Schedule information record (IR)■ Schedule message record (MR)

How to copy the BACKUP schedule's base record is explained next. To createa base record for your new schedule, type C next to BACKUP and pressENTER.

Unicenter CA-Scheduler responds by displaying the Schedule Definition panelfilled in as follows:



� � SCHD-SU ��SCHEDULE DEFINITION�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

SCHEDULE NAME : _ PROTOTYPE SCHEDULE NAME : BACKUP


AUTO SELECT : NO






USERS:

LIBRARY TYPE : CMS

POWER CLASS : A


AUTO REPLY MESSAGES: N



RECS= SBR: Y SCR: Y SRC: Y SIR: Y SMR: Y PF1=HELP

� �

The SCHEDULE DEFINITION panel shows all the information defined onBACKUP's schedule base record and is waiting for you to specify the newschedule's name. You can also tab to any fields on this panel and overrideBACKUP's values by specifying others before you press ENTER. For now,name this new schedule BACKUP1: type BACKUP1 as the SCHEDULE NAMEand press Enter. When you press Enter, Unicenter CA-Scheduler savesBACKUP1's schedule base record.


===> MASTER - WR

CONNECT : 4�

DEFINE SBR LASTUSER=userid,NAME=BACKUP1,ERLYTIME=23��

CACU�18I SBR BACKUP1 HAS BEEN ADDED

PF1=HELP

� �

If you wanted to copy an optional record, you would enter something otherthan C on the Schedule Directory panel. The table following explains what toenter to copy different types of records:

To Copy A Schedule Type This Next To The Schedule Name

Base record C

Criteria record CCR

Reason code record CRC

Information record CIR



Now return to the Schedule Directory panel and try copying BACKUP'smessage record and adding it to the BACKUP1 schedule. Enter CMR insteadof C and press Enter. Then identify which schedule the new message recordbelongs to before pressing Enter again. Press Clear again to return.

Now that you know how to copy schedule records, press the Clear key beforebeginning the next topic.

To Copy A Schedule Type This Next To The Schedule Name

Message record CMR


3.4 Displaying Schedules


Not all Unicenter CA-Scheduler users can display all schedule records. Generalusers are restricted to displaying only those records that specifically grantthem access. In all, you have three alternatives for displaying schedulerecords:

■ Display a specific schedule record■ List a subset of schedules and choose one record type■ List all schedules and pick one record type

To display the record for your backup schedule, on the Schedule Maintenancemenu, option 2 displays a complete schedule base record.


===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------









PF1=HELP

� �

When you use option 2, Unicenter CA-Scheduler expects you to specify aschedule by name. To display the base record for your backup schedule, type2,BACKUP in the command area. Then press Enter. Unicenter CA-Schedulerresponds by displaying that schedule's base record on this panel:



� � SCHD-SU ��SCHEDULE DISPLAY�� CA-SCHEDULER

===> _ MASTER - WR

CONNECT : 4�



AUTO SELECT : NO






USERS:

LIBRARY TYPE : CMS

POWER CLASS : A





RECS= SBR: Y SCR: Y SRC: Y SIR: Y SMR: Y PF1=HELP

� �

This preceding panel resembles the panel you used when defining theschedule base record. To view any optional schedule record, press the TABkey. As you tab to different RECS fields, type Ds where Ys now appear todisplay the optional records. After you press ENTER, the optional records yourequested will appear.

Unicenter CA-Scheduler allows you other RECS options besides D. You canalso type A to alter any schedule record. To move from panel to panel, keeppressing ENTER. To exit from the Schedule Criteria Edit panel, press PF3, ortype FILE and press Enter.

Now you have seen the simplest method of displaying schedule records. Theother two methods for displaying records offer you even more flexibility. Letus return to the Schedule Maintenance menu to try another approach.

Option 1 can be useful if you want to list a subset of schedules. To list allschedules starting with B, you can use the mask character * as part of theselection criteria.

For example, typing 1,*B causes Unicenter CA-Scheduler to display records forall schedules with names that start with B:




===> _ MASTER - WR

CONNECT : 4�

B C R I M


_BACKUP 5� � A NO Y Y Y Y Y

BACKUP1 5� � A NO Y Y


PF1=HELP

� �

If you tabbed down to a particular schedule and typed D, UnicenterCA-Scheduler would show you the Schedule Display panel; the same panelthat appeared when you used the first method.

Now return to the Schedule Maintenance menu to try the last method fordisplaying schedule records.

The last method causes Unicenter CA-Scheduler to display all schedulerecords. The instructions following review how that is done.

The first entry on the Schedule Maintenance menu tells you to press Enter todisplay a directory of schedule records.


===> _ MASTER - WR

CONNECT : 4�

B C R I M


APDAILY 5� 12 A 9 NO Y Y

APMNTHLY 5� 35 B 9 NO Y Y

ARDAILY 5� 27 A 9 NO Y Y

ARMNTHLY 5� 6 B 9 NO Y Y

_BACKUP 5� � A NO Y Y Y Y Y

BACKUP1 5� � A NO Y Y

DBUPDATE 5� 3� A 9 YES Y Y Y

DISASTER �1 1� C 1 YES Y Y Y

INVDAILY 5� 9 A 9 NO Y Y Y

INVWKLY 5� 22 A 9 NO Y Y Y

PERDAILY 5� 6 A 9 YES Y

PERWKLY 5� 1� B 9 YES Y Y

PURDAILY 5� 11 A 9 NO Y

PURWKLY 5� 19 A 9 NO Y Y

RESTART �1 6 A 1 YES Y Y Y

RESTORE 5� 1� A 9 YES Y Y Y

SALES 5� 22 B 9 NO Y Y


PF1=HELP

� �

Your entries will differ from those shown preceding. But you should be ableto find your schedule record. Tab down to your backup schedule. One panelmight not hold all the schedules defined at your site. If that is the case, theEND OF DIRECTORY LIST message will not appear on your panel. Instead,the list will end with the message:




When this message appears, press that key to view the remainder of the list.

A summary of all the commands that the Schedule Directory panel supports isshown in the following table.

Notice that C does more than just create new schedule records: it allows youcopy them. This method of building new records from existing ones is moreefficient than using the PROTOTYPE fields. Therefore they are not discussedhere. The copy feature is illustrated later in this chapter.

The next topic discusses deleting schedule records in more detail. Before youstart the next topic, return to the main menu by pressing Clear.

To Type This Next To The Schedule Name

Display a record base criteriaR information message reason code

DDCRDIRDMRDRC

Alter a record base criteria information message reason code

AACRAIRAMRARC

Define a new record using thisrecord as the model base criteria information message reason code

CCCRCIRCMRCRC

Delete a record all records for a schedule base criteria information message reason code

LLBRLCRLIRLMRLRC


3.5 Deleting Schedules


Because there are different types of schedule records, Unicenter CA-Schedulergives you two methods for deleting them. Which method you use depends onwhat schedule records you want to delete.

If you do not know which schedule you want to delete, or you only want todelete an optional schedule record, begin by displaying a directory ofschedules using the Schedule Maintenance menu:


===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------









PF1=HELP

� �

Pressing Enter at that menu causes the following panel to appear.




===> _ MASTER - WR

CONNECT : 4�

B C R I M


APDAILY 5� 12 A 9 NO Y Y

APMNTHLY 5� 35 B 9 NO Y Y

ARDAILY 5� 27 A 9 NO Y Y

ARMNTHLY 5� 6 B 9 NO Y Y

BACKUP 5� � A 9 NO Y Y Y Y Y

_BACKUP1 5� � A NO Y Y

DBUPDATE 5� 3� A YES Y Y Y

DISASTER �1 1� C 1 YES Y Y Y

INVDAILY 5� 9 A 9 NO Y Y Y

INVWKLY 5� 22 A 9 NO Y Y Y

PERDAILY 5� 6 A 9 YES Y

PERWKLY 5� 1� B 9 YES Y Y

PURDAILY 5� 11 A 9 NO Y

PURWKLY 5� 19 A 9 NO Y Y

RESTART �1 6 A 1 YES Y Y Y

RESTORE 5� 1� A 9 YES Y Y Y

SALES 5� 22 B 9 NO Y Y

SHIPMENT 5� 19 A 9 NO Y Y


PF1=HELP

� �

Your entries will differ from those shown preceding. But you should be ableto find BACKUP1's schedule record. Tab down to your BACKUP1 schedule.The following describes the various deletion options this directory panelsupports are examined.

Use LBR with caution. Optional records for that schedule will not be deletedeven though they do not appear on the directory or Analyze report. Optionalrecords will appear again if a base record with the same name is defined at alater date.

The following describes deleting this schedule's message record. First, checkthat the schedule actually has a message record. The value in the MR columnwill be Y if a message record exists for this schedule. Explanations of theother fields on this panel are provided in the topic called Copying Schedules.Next, delete BACKUP1's schedule message record by typing LMR on that lineand press Enter.

To Delete Enter

All records for that schedule(except the history record)

L

Just the -base record -criteria record -history record -information record -message record -reason code record

LBRLCRLHRLIRLMRLRC



If you have the authority to change this schedule, Unicenter CA-Schedulerconfirms that the message record is deleted by displaying the message:


===> MASTER - WR

CONNECT : 4�

DELETE SMR NAME=BACKUP1

CACU�18I SMR BACKUP1 HAS BEEN DELETED

PF1=HELP

� �

To return to the Schedule Directory panel, press Enter. Then press Clear toreturn to the Schedule Maintenance menu so it can be demonstrated thesecond method for deleting schedule records.

To delete all of a schedule's records with a single command, begin by checkingwhich option on the Schedule Maintenance menu allows you to delete anexisting record:


===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------









PF1=HELP

� �

This panel tells you that option 5 deletes an existing record. Notice, however,that Unicenter CA-Scheduler expects you to enter a schedule name when youselect option 5. Therefore, when you type 5 in the command area, follow itwith a comma and the name of the schedule you want to delete.

The following text describes deleting the backup schedule you defined. Forexample, if you named that schedule BACKUP1, enter 5,BACKUP1 in thecommand area to delete that record.



If you are not authorized to delete this schedule, Unicenter CA-Schedulerdisplays the message CACO229E USER NOT AUTHORIZED FOR THISSCHEDULE. But if you do have that authority, Unicenter CA-Schedulerconfirms it deleted that schedule record with the message shown following:


===> MASTER - WR

CONNECT : 4�

DELETE S NAME=BACKUP1

CACU�18I SBR BACKUP1 HAS BEEN DELETED

PF1=HELP

� �

Since BACKUP1 only had a schedule base record, that is the only record thatwas deleted. This panel will display a message for each type of record thatwas deleted.


3.6 Analyzing Schedules


You should analyze all schedules that you add to the database before you putthem into production. This allows you to fix discrepancies and omissionsbefore you run the schedules. There are two ways to analyze a scheduleonline:

■ Analyze a specific schedule■ List all schedules and pick one to analyze

The first method is quicker, but the second is useful if you do not know theexact spelling of the schedule to be analyzed. The analysis will producemessages about the following:

■ If no jobs are defined for the schedule■ If the schedule records specify an undefined calendar, datetable, userid, or

predecessor■ If a predecessor or successor deadlock exists

To analyze a specific schedule, start at the Schedule Maintenance panel.Suppose you recently defined a schedule (NEWSCHED), but you failed todefine any jobs for it and you defined a nonexistent datetable name in it.


===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------









PF1=HELP

� �

To analyze the schedule, enter 6, followed by the schedule name.

Unicenter CA-Scheduler responds by displaying the SCHDUTIL Output panel:




===> MASTER - WR

CONNECT : 4�

ANALYZE SCHEDULE LIST=ERR,NAME=NEWSCHD

CACU�17E DATETABL ADATETB9 FOR YEAR 2��3 NOT FOUND

CACU�17E DATETABL ADATETB9 FOR YEAR 1994 NOT FOUND

CACU�17E DATETABL ADATETB9 FOR YEAR 2��3 NOT FOUND

CACU�41E SCHEDULE NEWSCHD NO JOBS DEFINED

CACU�18I SCHEDULE NEWSCHD HAS BEEN ANALYZED

PF1=HELP

� �

Notice that the analysis is performed with the LIST=ERR option so that onlyerror messages are displayed. If you need a full analysis report, use the JCLdescribed in the chapter "Reports" of the Unicenter CA-Scheduler Reference GuidePart 2.

Before examining the second method of analyzing schedules, return to theSchedule Maintenance panel by pressing Clear.

To analyze a schedule that has a name you do not know, start at the ScheduleMaintenance panel. You need to display a full directory of schedules so thatyou can find the one you want.


===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------









PF1=HELP

� �



To display a full directory of schedules, press Enter.



===> MASTER - WR

CONNECT : 4�

B C R I M


APDAILY 5� 12 A �9 NO Y Y

APMNTHLY 5� 35 B �9 NO Y Y

ARDAILY 5� 27 A �9 NO Y Y

ARMNTHLY 5� 6 B �9 NO Y Y

BACKUP 5� � A NO Y Y Y Y Y

DBUPDATE 5� 3� A �9 YES Y Y Y

DISASTER �1 1� C �1 YES Y Y Y

INVDAILY 5� 9 A �9 NO Y Y Y

INVWKLY 5� 22 A �9 NO Y Y Y

NEWSCHD 5� � A NO Y

NEWSCHD2 5� 1 A NO Y

PERDAILY 5� 6 A �9 YES Y

PERWKLY 5� 1� B �9 YES Y Y

PURDAILY 5� 11 A �9 NO Y

PURWKLY 5� 19 A �9 NO Y Y

RESTART �1 6 A �1 YES Y Y Y

RESTORE 5� 1� A �9 YES Y Y Y

SALES 5� 22 B �9 NO Y Y

PRESS ENTER FOR NEXT PAGE PF1=HELP

� �

Assume that the schedule that you want to analyze is called NEWSCHD2.You recently defined it, but you defined a userid in the USERS field that is notdefined to Unicenter CA-Scheduler. Tab to it and enter ANA.





===> MASTER - WR

CONNECT : 4�

ANALYZE SCHEDULE LIST=ERR,NAME=NEWSCHD2

CACU�17E USERID AMBMA�3 NOT FOUND

CACU�18I SCHEDULE NEWSCHD2 HAS BEEN ANALYZED

PF1=HELP

� �

Before beginning the next topic, return to the Unicenter CA-Scheduler MainMenu by pressing Clear.


3.7 Automatic Console Replies for Schedules


Console messages issued by Unicenter CA-Scheduler VSE controlled jobs orschedules typically require a response that either issues a command, suppliesdata or requests some kind of operator intervention. These responses can beautomated by using the Unicenter CA-Scheduler Automatic Console Replyfeature. This feature is unavailable with the CMS online component.

You begin by tabbing to the Auto-Reply Maintenance line and pressing Enter.


===> MASTER - WR

CONNECT : 4�





==> POWER INTERFACE


==> JOB MAINTENANCE







==> DOCUMENTATION MAINTENCE




PF1=HELP

� �

This will display the Automatic Reply Maintenance panel. It may also bereached by selecting 7,AUTO-REPLY PROCESSING on the ScheduleMaintenance Menu panel SCHD-SM, or the Job Maintenance Menu panelSCHD-JM. Overwriting the auto-reply messages field on the SBR or JBR panelwith Y or C will also bring you to the Automatic Reply Maintenance panel.



� � SCHD-AR �AUTOMATIC REPLY MAINTENANCE� CA-SCHEDULER

====> MASTER - WR

CONNECT : 4�

Schedule : ________ Job : ________ Jno : __ Msgid : ________

Scantxt :

Reply:

Schedule Job Job Message Scan Reply

Name Name Number Id Text Text

Enter -Browse 2/14 -Add 7/19 -Backward 8/2� -Forward Clear -Quit

� �

3.7.1.1 To ADD a New Reply

Enter the schedule name in the schedule field and press Enter. If the schedulehas already been defined to the database, the panel will show the existing jobnames, job numbers, message ids, scan text for each message (if any), and thereply text.

Enter the job name in the job name field.

Enter the job number in the jno field.

Enter the message ID in the msgid field. The message ID is the first one toeight characters of the message associated with the reply.

Each of the four key fields, Schedule Name, Job Name, JNO (job number) andMSGID (message id), can also have a generic value. For example:

AA� � - any char string may follow

A??B ? - any char in this position

Scan text is a string of one to sixteen characters that occur in the message. Thestring will be checked to verify the message id.

You may enter a reply to the message of up to 72 characters.




====> MASTER - WR

CONNECT : 4�

Schedule : sched1__ Job : JOBD____ Jno : 14 Msgid : cacm�27_

Scantxt : autoscan cannot

Reply: wait for monitor to terminate, then reactivate




� �

To add the record to the database, either enter ADD on the command line orpress the function key.

The message CACO360I AUTO-REPLY RECORD ADDED will be displayed.


====> MASTER - WR

CACO36�I AUTO-REPLY RECORD ADDED CONNECT : 4�

Schedule : SCHED1 Job : JOBD___ Jno : 14 Msgid : CACM�27

Scantxt : AUTOSCAN CANNOT

Reply: WAIT FOR MONITOR TO TERMINATE, THEN REACTIVATE




� �



3.7.1.2 ALTer or REPlace an Auto-Reply Record

Begin with the Auto-Reply Maintenance panel SCHD-AR, described preceding.

To alter or replace an existing reply, enter the schedule name and press Enterto search for the message to be changed. The ENTER-BROWSE functiondisplays the replies that currently exist in the database for that schedule.

Type A or R on the line of the record to be changed, and press Enter.


====> MASTER - WR

CONNECT : 4�

Schedule : SCHED� Job : ________ Jno : __ Msgid : ________

Scantxt :

Reply:



_ SCHED1 JOBA 11 CACM�29 CANNOT RERUN USE RUN

_ SCHED1 JOBB 12 CACM�62 ABENDED

_ SCHED1 JOBB 12 CACM�7� NOT HELD RECHECK STAT

_ SCHED1 JOBC � CACM�97 SCHEDULER REINITIALIZE

a SCHED1 JOBD 14 CACM�27 AUTOSCAN CAN WAIT FOR MON


� �

The messages CACO372I UPDATE FIELDS AND PRESS ENTER and ALTERwill be displayed in the command area.




====> ALTER MASTER - WR

CACO372I UPDATE FIELDS AND PRESS ENTER CONNECT : 4�

Schedule : SCHED1 Job : JOBD____ Jno : 14 Msgid : CACM�27_







_ SCHED1 JOBB 12 CACM�7� NOT HELD RECHECK STATUS


� SCHED1 JOBD 14 CACM�27 AUTOSCAN CAN WAIT FOR MON


� �

Type the changes in the appropriate fields and press Enter.

The database is updated and the message CACO361I AUTO-REPLY RECORDUPDATED is displayed:


====> MASTER - WR

CACO361I AUTO-REPLY RECORD UPDATED CONNECT : 4�

Schedule : SCHED Job : JOBD____ Jno : �_ Msgid : CACM�27_







_ SCHED1 JOBB 12 CACM�7� NOT HELD




� �



3.7.1.3 To DELete an Auto-Reply Record

To delete an existing reply, enter the schedule name on panel SCHD-AR andpress Enter to search for the message to be deleted.

Type L on the line of the record to be deleted and press Enter.


====> MASTER - WR

CONNECT : 4�


Scantxt :

Reply:







l SCHED1 JOBD 14 CACM�27 AUTOSCAN CAN WAIT FOR MON


� �

The message CACO369I PRESS ==> PF5 <== TO CONFIRM DELETE andDELETE will be displayed in the command area.


====> DELETE MASTER - WR

CACO369I PRESS ==> PF5 <== TO CONFIRM DELETE CONNECT : 4�

Schedule : SCHED1 Job : JOBD____ Jno : �_ Msgid : CACM�27_









� SCHED1 JOBD � CACM�27 AUTOSCAN CAN WAIT FOR MON


� �



The database is updated and message CACO362I AUTO-REPLY RECORDDELETED is displayed.


====> MASTER - WR

CACO362I AUTO-REPLY RECORD DELETED CONNECT : 4�

Schedule : SCHED1 Job : JOBD____ Jno : �_ Msgid : CACM�27









_ SCHED1 JOBD � CACM�27 AUTOSCAN CAN WAIT FOR MON


� �


3.8 Summary of Schedule Maintenance


Anyone can create a schedule definition, but Unicenter CA-Scheduler onlyallows authorized users to update or delete existing schedule definitions.General users can change public schedules and schedules that specificallygrant them access in the USERS field.

The chart following sums up the steps involved in maintaining schedulerecords from the Schedule Maintenance menu. Since there are so many waysto display records, only the fastest ways are shown:

To Enter This InCommand Area

Then

Define a schedule 4 Enter data

Copy a schedule 1,schedule name Tab to a schedule; enter C orCxx, where xx is the recordtype. Enter new data

Alter a specific schedule

an unknown schedule

3,schedule name

(Press Enter)

Enter changes in SBR; enter Ain a RECS= field

Tab to a schedule; enter A orAxx, where xx is the recordtype

Delete a specific schedule a specific record 5,schedule name

(Press Enter)

Tab to the schedule; enterLxx, where xx is the recordtype

Display one schedule record

some schedules

all schedules

2,schedule name

1,*x where x isthe first characterin some schedules

(Press Enter)

Tab to a schedule; enter D

Press Enter to scroll panels

Analyze a schedule 6,schedule name

Display, alter ordefine auto-replymessages

7,schedule name



These same functions (except for AUTO-REPLY MAINTENANCE) can also beperformed using the Schedule Directory panel. The chart following lists theappropriate commands.

The Schedule Directory panel supports the following commands:

Note: Deleting the base record will remove the schedule from the Directorypanel. Other schedule records associated with this record, however, willnot be deleted along with it. When you delete a base record, it is yourresponsibility to either replace the base record or delete its associatedrecords using the batch utility.

To Type This Next To The Schedule Name

Display a record base criteria information message reason code

DDCRDIRDMRDRC

Alter a record base criteria information message reason code

AACRAIRAMRARC

Define a new record using thisrecord as the model base criteria information message reason code

CCCRCIRCMRCRC

Delete a record all records for a schedule (exceptthe history record) base criteria history record information message reason code

L

LBR (see Note following)LCRLHRLIRLMRLRC

Analyze a schedule for missing orillogical records

ANA


3.9 Defining Jobs

3.9 Defining Jobs

Unicenter CA-Scheduler uses seven different types of records to storeinformation pertaining to a job, but only the job's base record is required. Thatrecord assigns each job to a specific schedule to make your work easier.Schedules group similar jobs together. If you define those similarities onschedule records, almost all of that data automatically applies to all the jobs inthat schedule which means less work when defining these jobs. Therefore, it isimportant to define schedules first.

All users with write passwords can define jobs for schedules they areauthorized to access. This topic shows you how by:

■ Defining a job base record■ Checking what defaults apply to jobs■ Learning the basics about the job base record■ Defining optional job records

3.9.1 Defining a Job Base RecordJob records primarily consist of optional fields with defaults which means youwill not have to fill in all of the fields on job records. Since a job's base recordis the only one required, you begin by defining a simple job using just thatrecord. You begin defining jobs at Unicenter CA-Scheduler's main menu bytabbing to JOB MAINTENANCE:


===> MASTER - WR

CONNECT : 4�





==> POWER INTERFACE


_ ==> JOB MAINTENANCE











PF1=HELP

� �

Then tab down to the sixth selection, JOB MAINTENANCE, and press Enter.


3.9 Defining Jobs

That choice displays the Job Maintenance menu, that lists everything you cando with job records:

� � SCHD-JM ��JOB MAINTENANCE�� CA-SCHEDULER

===> 4 MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------



DISPLAY SPECIFIC JOB............. 2,JOB(,JNO,STN,SCHEDULE)

ALTER JOB RECORD................. 3,JOB(,JNO,STN,SCHEDULE)

DEFINE JOB RECORD................ 4(,JOB,JNO,STN,SCHEDULE)

DELETE JOB RECORD................ 5,JOB,(JNO,STN,)SCHEDULE

ANALYZE JOB...................... 6,JOB(,JNO,STN,SCHEDULE)

AUTO-REPLY PROCESSING............ 7,JOB(,JNO,STN,SCHEDULE)

PF1=HELP

� �

If you logon without a write password, the read-only functions appear on yourpanel. They allow you to display job directories, analyze a job, or viewauto-reply records. You need to logon with your write password to practicedefining jobs.

Option 4 on the Job Maintenance menu allows you to define a job's baserecord. The information following the 4 (,JOB,JNO,STN,SCHEDULE) identifiesoptions you can specify when selecting menu choice 4. Ignore that whendefining jobs; type 4 in the command area and press Enter. Then the JobDefinition panel appears. Tab to JOB NAME.


3.9 Defining Jobs

� � SCHD-JU � JOB DEFINITION � CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

JOB NAME : _ PROTOTYPE JOB: JNO: STN:

JOB NUMBER : PROTOTYPE JOB IN SCHEDULE :

STATION ID : CPU JOB : SKIP EXECUTION :

SCHEDULE NAME : JOB PRIORTY : USE SIM TIME : NO

STAGE JCL : AUTO START : NO AVERAGE TIME :

MEMO :

DISPLAY KEY : DISPLY TIME : INTERRUPT :

LIBRARY TYPE : MBR SUBID : MEMBER PASSWORD:

MEMBER NAME : SLI SUBLIB : ICCF LIB NUMBER:

POWER CLASS : NODE ID : RUN ON SYSID :


LDEST : PDEST : NODE SYSID :

RECOVERABLE : NO ABEND : ABORT FAIL CODE :

BACKLOG : YES TESTLIB PARM:

MUST START BY TIME : COMMANDS AT JOB START:

COMPLETION DEADLINE TIME : COMMANDS AT JOB END :

MAXIMUM EXECUTION TIME : AUTO-REPLY MESSAGES :

EARLIEST START TIME :

RECS= JBR: N JCR: N JRC: N JIR: N JMR: N JRR: N JNR: N PF1=HELP

� �

Unicenter CA-Scheduler uniquely identifies every job it handles by four values:

■ Job name ■ Job number ■ Station ID ■ Schedule name

Since most work is done at the CPU, workstation ID defaults to station 40.Most jobs are only scheduled once a day, so job number defaults to 01. Thatleaves only two key fields on this panel that always require input.

JOB NAME consists of up to eight characters used to identify this job at yoursite. Define a job called DEFAULTS. Type that value for JOB NAME and thentab down to SCHEDULE.

SCHEDULE identifies which group definition pertains to this job. The valuesin that schedule definition apply to all the jobs belonging to that schedule.Enter the name of an existing schedule (up to eight characters). Assign this jobto your backup schedule.

Unicenter CA-Scheduler needs both job name and schedule name to specify aparticular task in its workload. This job will be known as DEFAULTSBACKUP. If you try to create a job definition without these values, UnicenterCA-Scheduler displays a message like this:


3.9 Defining Jobs


===> MASTER - WR

CONNECT : 4�

DEFINE JBR LASTUSER=userid,NAME=DEFAULTS

CACU�14E DEFINE JBR KEYWORD 'SCHEDULE' MUST BE SPECIFIED

PF1=HELP

� �

The other fields on the Job Definition panel all have default values, some ofwhich appear on the panel. Most job fields default to values specified onschedule records which means you do not have to type in values on the JobDefinition panel if you already entered that data on the schedule's record. Butdefaults based on schedule values do not appear on your panel.

When you are defining job records, tab from field to field until you havesupplied all the values necessary. To further your understanding of UnicenterCA-Scheduler, these fields will be described later in this chapter.

To save this job base record, press Enter. Unicenter CA-Scheduler responds bydisplaying this message:

DEFINE JBR LASTUSER=userid,NAME=DEFAULTS,SCHEDULE=BACKUP

CACU�18I JBR DEFAULTS HAS BEEN ADDED

If a job by that name already exists in that schedule, Unicenter CA-Schedulerdisplays the message:

CACU�15E DEFINE JBR BACKUP DEFAULTS DUPLICATE RECORD

If that message appears, try giving your job another name.

You will see how to define these other types of job records later in thischapter. Now press the Clear key to return to the Job Maintenance menu.

3.9.2 Checking Default Values for Job Base RecordsJust as some schedule options serve as defaults for jobs, installation optionssupply defaults for schedules. It can get confusing because job defaults willvary for different schedules. Clearly, you need a simple way of determiningwhat defaults apply to a job. Instead of worrying about what the install andschedule defaults are, choose an easier way: create a dummy job calledDEFAULTS for every schedule and then glance at the values UnicenterCA-Scheduler supplies. Eventually, you will want to delete these dummyrecords because they take unnecessary space in your database.

The job that you just defined consists of defaults, so display that job's baserecord. The first three functions on the Job Maintenance menu allow you todisplay a job base record:


3.9 Defining Jobs

� � SCHD-JM ��JOB MAINTENANCE�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------









PF1=HELP

� �

Use option 2 because it is quicker. When you select option 2, UnicenterCA-Scheduler also expects you to specify the name of an existing job. Todisplay the base record for the job defaults, type 2 in the command areafollowed by a comma and the job's name, DEFAULTS. For example, type2,DEFAULTS and press Enter.

Unicenter CA-Scheduler responds by displaying that job base record:

� � SCHD-JU � JOB DISPLAY � CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

JOB NAME : DEFAULTS

JOB NUMBER : �1

STATION ID : 4� CPU JOB : YES SKIP EXECUTION : ��

SCHEDULE NAME : BACKUP JOB PRIORTY : 5� USE SIM TIME : NO

STAGE JCL : NO AUTO START : NO AVERAGE TIME : ��

MEMO :

DISPLAY KEY : DISPLY TIME : �� INTERRUPT : NO

LIBRARY TYPE : CMS MBR SUBID : MEMBER PASSWORD:

MEMBER NAME : DEFAULTS SLI SUBLIB : ICCF LIB NUMBER:

POWER CLASS : A NODE ID : RUN ON SYSID :

POWER PRIORITY: � POWER USER :


RECOVERABLE : NO ABEND : ABORT FAIL CODE : ��


MUST START BY TIME : �� COMMANDS AT JOB START: N

COMPLETION DEADLINE TIME : �� COMMANDS AT JOB END : N

MAXIMUM EXECUTION TIME : �� AUTO-REPLY MESSAGES : N

EARLIEST START TIME : ��

RECS= JBR: Y JCR: N JRC: N JIR: N JMR: N JRR: N JNR: N PF1=HELP

� �

Notice that this panel displays more values than you specified for your defaultjob. Many of these fields obtain the defaults from the BACKUP schedule.


3.9 Defining Jobs

3.9.3 Learning the Basics About a Job RecordUnicenter CA-Scheduler provides even more job options than there wereschedule options. The following describes what characteristics job records candefine, and how Unicenter CA-Scheduler works with schedule and job options.

3.9.3.1 Which Users Can Work with Job Records?

Two factors determine who can work with a job record:

■ A user's authority level■ The USERS defined on the corresponding schedule base record

Users with General authority can work with jobs associated with publicschedules and schedules that specifically define them as USERS. Supervisorauthority allows you to access jobs that run at stations your userid recordauthorizes. People with Manager authority can access all jobs. Permission toaccess a job means you can create a job for that schedule or workstation,update records and delete records.

There is no field corresponding to USERS on a job record which means youcannot override the value that appears on the schedule base record at the joblevel.

3.9.3.2 When Will Jobs Be Selected?

When Unicenter CA-Scheduler runs autoscan, it selects that day's workload.The selection process consists of two steps:

■ First, Unicenter CA-Scheduler sees which schedules to select.■ Then it scans only the schedules selected for jobs that belong in the

workload.

That means jobs can only run on days when their schedules are selected. Sojobs that run daily must belong to schedules that are selected every day. Fordetails on the factors controlling when schedules are selected, see the topicWhen Will This Schedule Be Selected?

When Unicenter CA-Scheduler is scanning jobs to select the day's workload, itonly examines two fields on the job base record: the RECS value for JCR andthe value of SKIP EXECUTION.

■ If JCR: N, that job becomes part of the workload whenever its schedule isselected. If you want a job to run less frequently than its schedule, thenset JCR: Y and define a criteria record for that job. You will see how thatis done later in this chapter. Unicenter CA-Scheduler interprets your job'scriteria statement using either the datetable you specified on the schedulebase record, or the calendar shown on the job's criteria record.

■ Someday you may need to stop selecting a job for a while. If so, use theSKIP EXECUTION field. Specify how many times you want to skip this job


3.9 Defining Jobs

when it ordinarily would be selected in autoscan. For example, supposethat only once you want to omit a job that normally runs on Friday.Specify SKIP = 1 and Unicenter CA-Scheduler will "forget" only that jobthis Friday (not its successors). Each autoscan time when UnicenterCA-Scheduler skips over a job it normally would have selected, itdecrements the value in the SKIP field by one until SKIP once again iszero. Then selection for this job resumes normally. This advancedtechnique is only used under exceptional conditions. Usually, SKIP = 0.

3.9.3.3 When Will Jobs Actually Run?

As Unicenter CA-Scheduler selects the day's workload, it organizes the work,grouping each schedule's jobs together. This ordering reflects the sequence inwhich Unicenter CA-Scheduler evaluates jobs for submission. It alsoapproximates the order in which jobs run.

It does not line schedules up in the order they are selected. Instead, UnicenterCA-Scheduler allows you to control that order using schedule options. Thoseoptions are described in the topic When Will A Schedule's Jobs Actually Run?While Unicenter CA-Scheduler is organizing the workload, it also prioritizesthe jobs selected from each schedule. Unicenter CA-Scheduler allows you tocontrol the sequence of jobs within a schedule using the following jobparameters:

■ JCR predecessors ■ USE SIMTIME■ JRC start times■ EARLIEST START TIME■ JRC DEADLINE TIMEs■ COMPLETION DEADLINE TIME

■ JOB PRIORITY


3.9 Defining Jobs

Defining predecessors forces Unicenter CA-Scheduler to witness a specificevent before starting AUTO-STARTed non-CPU jobs or submitting CPU jobs.Predecessors can be a variety of events:

■ The start or end of another schedule or job■ The close of an output data set or output generation data group■ A user-defined event that you can control using a global parameter■ The normal completion of a job that isn't controlled by Unicenter

CA-Scheduler■ An event that occurred sometime in the past

Defining predecessors for schedules forces Unicenter CA-Scheduler to witnessa specific event before evaluating any jobs in that schedule. You can alsodefine predecessors for individual jobs. If both a schedule and its jobs havepredecessors:

■ None of the schedule's jobs will be evaluated until the schedule'spredecessors are satisfied and the schedule starts.

■ Once the schedule's predecessors are met, other factors such as start timesdetermine whether the job is ready to be submitted once its predecessorsare satisfied.

Note: Defining predecessors for jobs does not override a schedule'spredecessors: instead, predecessors are cumulative.

When jobs must run in a certain order, define predecessors for either schedulesor jobs. Be careful deciding what that predecessor should be: check what daysyour predecessor is selected. For example, suppose your job's predecessor isn'teligible to be selected on the same day your job is. If a predecessor is not inthe day's workload, Unicenter CA-Scheduler ignores it: your job runs withoutwaiting for the predecessor. This feature makes writing criteria statementseasier. See the chapter "Criteria Language" for instructions on how that isdone.

When Unicenter CA-Scheduler lines up work to be processed during the day,the first factor it considers is predecessors. Then Unicenter CA-Schedulercompares start times, putting schedules that can start earliest ahead of onesthat start later. Unicenter CA-Scheduler orders jobs within schedules in thesame way: jobs that can start earlier go ahead of jobs from the same schedulethat have later start times.

Schedules without predecessors and start times go to the top of the list becausenothing is delaying them from starting. Likewise, jobs without predecessorsand start times are the first jobs listed for each schedule.


3.9 Defining Jobs

The chart preceding illustrates how Unicenter CA-Scheduler sequences jobs.Schedule A is first because A has no predecessors. Schedule B is ahead of Cbecause B has no start time. Now look at Schedule A's jobs to see why they aresequenced in this order. Job A1 is first because it has no predecessors and nostart time. Since A3 has predecessors, A2 goes ahead of it.

Now look at job start times in Schedule B. B1 has no start time so it goesahead of B2. B2 is next because it can start earlier than B3. B4 is last becauseonly that job has predecessors in addition to the predecessors defined for theschedule. Even though B4 has an earlier start time, its predecessors put it atthe end of Schedule B.

Now look at Schedule C to see how schedule and job start times interact.Schedule C starts at 9 a.m. Job C1 does not have a start time, but its scheduledoes. Therefore, C1 will not start until 9 a.m. What about C2? Its start time is6 a.m., but this schedule does not start until three hours later. Therefore, C2cannot start before 9 a.m. even if you give it an earlier start time.

Note: Job start times do not override specified schedule start times. Instead,they let you postpone running jobs after a schedule has started.

Unicenter CA-Scheduler gives you three ways of specifying when jobs start.To see which method you chose, Unicenter CA-Scheduler checks the values ofUSE SIMTIME. SIMTIME is only used at sites with extensive UnicenterCA-Scheduler experience. Such sites have defined their resources in greatdetail and automated the vast majority of their workload using UnicenterCA-Scheduler. As a result, they have refined simulation to such a degree thatit accurately reflects their daily operation. In fact, their simulation runs are soaccurate that those sites can rely on simulation data to determine whenschedules can start and jobs can be submitted. USE SIMTIME defaults to NO.Only sites using Unicenter CA-Scheduler's most advanced features choose toimplement SIMTIME as their start time.


3.9 Defining Jobs

A value of YES on the schedule base record causes Unicenter CA-Scheduler tostart that schedule no earlier than the time shown on the Simulated ExecutionSchedule. If USE SIM TIME = YES on the job base record, UnicenterCA-Scheduler submits that job at the time indicated on the SimulatedExecution Schedule. Notice the subtle difference here. The SIMTIME fields onschedule and job records do not override one another because they deal withseparate events: when schedules start and when jobs are submitted. Sites thatwant to schedule jobs using SIMTIME get best results when SIMTIME valueson both the schedule and job records are YES.

If you set USE SIMTIME=YES on the schedule base record, UnicenterCA-Scheduler ignores any other start times you may have specified forschedules, either on the reason code record or the schedule's base record.

If USE SIMTIME = NO, Unicenter CA-Scheduler checks to see what start timesyou have specified on the schedule's records. You specify the earliest possibletime a schedule can start using a 24-hour clock. For example, an early time of1400 allows a schedule to start no earlier than 2 p.m., but what if that scheduleshould not start until some day in the future? Unicenter CA-Scheduler alsoallows you to specify start times with a prefix showing how many productiondays to hold those jobs. For example, a start time of 031400 holds that scheduleuntil 2 p.m. three production days after that schedule was originally selected.Notice that production days usually do not start at midnight. Instead, they runfrom one autoscan to the next.

The first place Unicenter CA-Scheduler looks for a start time is on theschedule's reason code record (SRC). If you do not specify a start time therethat corresponds with the reason the schedule was selected today, UnicenterCA-Scheduler looks to see if you defined an EARLIEST START TIME on theschedule base record. Start times defined on job records are not even lookedat until a job's schedule starts. Then Unicenter CA-Scheduler checks to see ifyou have delayed any jobs by defining start times on job records.

Since start time is an important factor in sequencing your workload, UnicenterCA-Scheduler gives you flexibility. For example, a schedule or job may needto start at different times on different days. Unicenter CA-Scheduler allowsyou to define different reasons for selecting a schedule or job on its criteriarecord (SCR or JCR). Each reason can cause work to be selected on a differentday. Once you have defined reasons on a criteria record, you can specify adifferent start time for each reason. A schedule's alternate start times are storedon its reason code record (SRC). Likewise, a job's alternate start times arestored on its reason code record (JRC).

If a job has no criteria record or it only needs one start time, specify that valueas EARLIEST START TIME on the job base record.

When Unicenter CA-Scheduler organizes the work to be processed each day,first it considers predecessors. Then it checks start times. If schedules or jobshave the same predecessors and start times, Unicenter CA-Scheduler puts


3.9 Defining Jobs

those with earlier deadlines ahead of the others. Work that has to be finishedsooner goes first. You define deadlines in the field called COMPLETIONDEADLINE TIME. Schedule deadlines affect how schedules are ordered in theworkload. Job deadlines have no impact on the sequencing of schedules andonly affect how jobs within a schedule are organized. For information on therole deadlines play in progress notification, see the topics What HappensWhen Schedules Run Late and What Happens When Jobs Run Late.

Finally, Unicenter CA-Scheduler checks one last field when it is organizing theworkload. Schedules with the same predecessors, start times, and deadlines aresorted by SCHED PRIORITY: schedules with the highest priority go first.Priorities range from a high of 01 to a low of 99. Likewise, jobs in the sameschedule with the same predecessors, start times, and deadlines are sorted byJOB PRIORTY.

If, after checking all these fields, Unicenter CA-Scheduler finds a group ofschedules with equivalent values in all these fields, it lines up those schedulesin alphabetical order. Unicenter CA-Scheduler handles jobs within schedules inthe same way: jobs with the same values for all these fields are put intoalphabetical order in the work queue.

The factors determining the order of schedules in the workload are listedfollowing in decreasing order of importance.

Factors determining the order of jobs within schedules are listed following indecreasing order of importance.

Sequence By Using On The Schedule


Start times USE SIMTIME = YESEARLY TIMEs orEARLIEST START TIME

Base recordBase code recordBase record

Deadline DEADLINE TIMEs orCOMPLETION DEADLINETIME


Priority SCHED PRIORITY Base record

Alphabeticalorder

SCHEDULE NAME Base record



Start times USE SIMTIME = YESEARLY TIMEs orEARLIEST START TIME

Base recordBase code recordBase record


3.9 Defining Jobs

What if there are so many jobs to run today that Unicenter CA-Schedulernever gets to submit all of them? The values in the BACKLOG fields controlwhat happens. The term backlog identifies jobs that do not run on theproduction day when they were selected and are carried over to the nextproduction day's workload.

If BACKLOG = NO on a schedule base record, that schedule's jobs will neverbe backlogged unless you override this value on job records. IfBACKLOG=NO on the schedule's base record, jobs will only be backlogged ifBACKLOG = YES on their job base records or the job is submitted or started atthe time of the next autoscan.

Suppose a job is carried over into tomorrow's workload. What happens if thatjob is selected again tomorrow? Tomorrow's job is added to the workload aftertoday's backlogged schedule has completed or been canceled.


Deadline DEADLINE TIMEs orCOMPLETION DEADLINETIME


Priority JOB PRIORITY Base record

Alphabeticalorder

JOB NAME Base record

3.9.3.4 Does This Job Record Describe a Job Performed on the CPU?

Job records describe every job defined to Unicenter CA-Scheduler. If a job isperformed at several workstations, a job base record exists for that job at everyworkstation that processes it. So how does Unicenter CA-Scheduler identifyCPU jobs? STATION ID identifies the workstation this record refers to. Station40 usually identifies work performed by your CPU, but what if you want toautomate scheduling of manual jobs your operators do? You can define a jobrecord at station 40 and set CPU JOB = NO. That tells Unicenter CA-Schedulerthat this job does not require CPU processing: no JCL exists for this job.

Can jobs that do not run on the CPU have EARLIEST START TIMEs? Yes,however, the field called AUTO START controls what happens when that timeis reached. If AUTO START = NO, this job has to be started using UnicenterCA-Scheduler's START command. (AUTO START's default is NO.) That meansthat Unicenter CA-Scheduler's statistics for elapsed time are meaningful: theyshow how long it takes for a job to complete once it has started.

If AUTO START = YES, the pre-CPU job automatically starts when its earlystart time is reached and all predecessor conditions have been satisfied whichmeans the pre-CPU job is posted as started even though this work has not yetbegun.


3.9 Defining Jobs

3.9.3.5 What JCL Does Unicenter CA-Scheduler Submit for CPU Jobs?

Several fields on schedule and job base records determine what JCL UnicenterCA-Scheduler submits for your job:

■ CPU JOB ■ LIBRARY TYPE ■ MEMBER NAME ■ MBR SUBID ■ MEMBER PASSWORD

First, Unicenter CA-Scheduler determines if this job executes on the CPU. IfSTATION ID = 40, CPU JOB = YES and LIBTYPE is other than RDRQ, thenUnicenter CA-Scheduler knows this job has JCL it needs to submit.

Unicenter CA-Scheduler identifies the library where a job's JCL is stored usingan installation option or the job's schedule or job base record. If the installationoption is not the LIBTYPE appropriate to this job, override it at the schedule orjob level. If the schedule's value for LIBRARY TYPE is not appropriate to thisjob, then override it using LIBRARY TYPE on the job base record.

Unicenter CA-Scheduler can retrieve JCL directly from:

■ A CMS member■ A Unicenter CA-Driver procedure library

■ AllFusion CA-Panvalet ■ AllFusion CA-Librarian ■ User-defined libraries■ An ICCF member■ An SLI source member■ A PROC VSE procedure library■ A Allfusion CA-Vollie library member

■ CONDOR

Depending on the LIBRARY TYPE you specify, Unicenter CA-Scheduler mayneed additional information to identify where the JCL for your job is stored.

MEMBER NAME Identifies the library member that contains the JCLfor this job. Specify up to 8 characters forMEMBER NAME. If no value is given, UnicenterCA-Scheduler uses the job name as the default. Ifa job's LIBRARY TYPE is RDRQ, do not specify amember name.

MBR SUBID Specifies the prefix or qualifier required to findthe library member (up to 8 characters). For JCLstored in VOLLIE libraries, specify OPERATORhere.

MEMBER PASSWORD Supplies the member's password if one is requiredto access that library member (up to 8 characters).


3.9 Defining Jobs

However, sometimes production JCL requires editing before it can besubmitted. STAGE JCL fields on the schedule and job base records identifywhich jobs have JCL that requires editing before submission. Again, the valueof STAGE JCL on the job record overrides the one defined for the schedule. IfSTAGE JCL = YES, Unicenter CA-Scheduler copies that job's production JCLinto the staging library when the job is selected. You can then define anEARLIEST START TIME that allows plenty of time to edit the staged JCLbefore this job is submitted. Or you can ensure that the JCL has been editedbefore submission by defining another record for this job at station 39 (JCLsetup). Defining a job record for station 39 guarantees that UnicenterCA-Scheduler will not submit this job for processing until that JCL has beenedited and staging is complete.

In the case where the JCL for a specific job is stored in a CA-Panvalet library,Unicenter CA-Scheduler will submit a batch job that is a library access job.This job will run in a partition and extract the actual job JCL from the libraryand submit this JCL to POWER to be run so that this JCL may not be staged.

Once the JCL is staged, you can use a variety of editor commands to prepare itfor submission. In addition to usual text editing, you can perform somespecial functions within the editor:

■ Expansion of Unicenter CA-Driver procedures embedded in the JCL■ Display of current values of all Unicenter CA-Driver reserved-name

variable parameters in the JCL■ Change of values of any Unicenter CA-Driver reserved-name variable

parameters in the JCL

For detailed explanations of the editor commands, see the appendix "EditorCommands" of the Unicenter CA-Scheduler Reference Guide Part 2.

3.9.3.6 On Which CPU Should Jobs Be Run?

Unicenter CA-Scheduler uses three fields on both schedule and job baserecords to record where jobs run:

■ NODE ID ■ NODE SYSID■ RUN ON SYSID

Whether you need to define these fields depends on the CPU configuration atyour site:

If You Do This

Only have one CPU Leave all three fields blank on both schedule andjob records.


3.9 Defining Jobs

How you define these fields on schedule and job records is explainedfollowing.

RUN ON SYSID is only used in a multi-CPU environment with a shared spoolcomplex. Notice that the value on a job record does not override what isspecified on the schedule record. Instead, the SYSID on the schedule recordselects and submits all jobs in that schedule. You specify which CPU the jobsexecute on using RUN ON SYSID on the job record. The schedule recordidentifies which CPU scans this schedule while selecting the day's workload.The same CPU also submits that schedule's jobs, but those jobs do notnecessarily have to execute on that CPU. You can cause a job to execute onanother CPU by specifying the POWER SYSID of that CPU in the RUN ONSYSID field of the job's base record.

If your site has one CPU perform scheduling for all of them, it is called yourMaster CPU. It is the first CPU listed on the SYSID= installation generationmacro parameter. Since that value is the default for a schedule's RUN ONSYSID, you must leave that field blank on the schedule base record if your sitehas a Master CPU.

NODE ID and NODE SYSID are only used at sites that are part of a networkthat uses POWER/VSE at each node and Unicenter CA-Scheduler on eachCPU at every node. Only use NODE SYSIDs if there are multiple CPUs usingshared POWER spool at a NODE ID. Also notice that values for these fieldsmean different things on schedule and job records.

NODE ID on the schedule record indicates the default NODE ID for the jobs inthat schedule. A job's NODE ID identifies which node the job's JCL issubmitted to. If a job runs on the node specified as the schedule's NODE ID,you can leave NODE ID blank on the job record. To submit a job to anothernode, specify its node ID on the job base record.

Suppose there are multiple CPUs at this node. Use NODE SYSID to specify aparticular CPU if the node has multiple CPUs that each run UnicenterCA-Scheduler and share a POWER location. For NODE SYSID, enter thePOWER SYSID of the remote CPU where the job is to run. NODE SYSID isonly valid if NODE ID is also specified on the same record. When NODE IDand NODE SYSID are given, that job base record's value for RUN ON SYSID isignored.

If You Do This

Have multiple CPUs atone site with sharedDASD

Define RUN ON SYSID. See the instructionsfollowing.

Have a network ofCPUs using thePOWER/VSE option

Specify NODE ID and possibly NODE SYSID.


3.9 Defining Jobs

3.9.3.7 Once a Job Starts, How Can You Intervene?

Unicenter CA-Scheduler offers several commands that allow users to control ajob, but a job's definition also allows you to define control points during a job'sprocessing. Ordinarily, you do not want to intervene in job processing.However, Unicenter CA-Scheduler gives you that ability should you need it.

MEMO defines text to display at the system console when this job starts at theCPU. This happens every time that job runs. A MEMO of up to 60 charactersforces the operator to reply OK or TERM. If the reply is OK, the job runs, buta reply of TERM causes Unicenter CA-Scheduler to cancel the job.

Although manual intervention is what Unicenter CA-Scheduler tries toeliminate, there may be times when you need it. For example, UnicenterCA-Scheduler may control a job that needs to have an online database closedto users before it starts. Or another job may need onsite approval before itstarts. These instances show how the MEMO option can be used.

MEMO allows you to control a job when it starts, and INTERRUPT gives youcontrol when a job ends. INTERRUPT = YES prevents a job from automaticallybeing posted COMPLETED even though it ended successfully. Instead, it'sgiven a status of INTRPTD which prevents the job's successors from beingposted as satisfied. That gives you the chance to review the job's output. Forexample, you can check a trial balance to see if it is correct. If so, you canchange the job's status to ENDED so its successors can be reevaluated to see ifthey can run, but if you are not satisfied with the output, you can rerun aninterrupted job using the RERUN or SUBMIT command.

3.9.3.8 What Happens When Jobs Don't End Successfully?

Several fields on the job base record determine what happens when somethinggoes wrong or when unusual circumstances occur:

■ ABEND ■ BACKLOG ■ FAIL CODE ■ RECOVERABLE

What if the system crashes while a job is running? Will UnicenterCA-Scheduler automatically restart the job? RECOVERABLE on the job recordtells Unicenter CA-Scheduler if a job can be restarted after the system isre-IPLed. RECOVERABLE defaults to NO, which causes UnicenterCA-Scheduler to put the job on hold. The job waits to be canceled or released,but if RECOVERABLE = YES, Unicenter CA-Scheduler automatically releasesthe job after you restart the system.

What if a job abends (cancels without going to normal completion)? A job'sABEND field allows a variety of things to happen:


3.9 Defining Jobs

■ Ordinarily, Unicenter CA-Scheduler prevents successors to this job frombeing satisfied. That is what happens when ABEND = ABORT, which isthe default.

■ Alternatively, Unicenter CA-Scheduler can ignore that this job abended. IfABEND = CONT, successors continue to be satisfied as usual even if thisjob abends.

■ If you specify ABEND=BACKOUT, Unicenter CA-Scheduler automaticallysubmits a backout job when the job abends. A value must be specified forthe BACKOUT installation option. Successors to the job will not be postedas satisfied. Unicenter CA-Scheduler adds a new job tracking record forthe backout job. The backout job's name is constructed according to theBACKOUT installation option by altering one character position of theabended job's name. The backout job will be specified as ABEND=ABORTto prevent resubmission if the backout job itself abends. All other jobattributes are copied from the abended job.

■ Unicenter CA-Scheduler's fourth alternative prevents successors from beingsatisfied and begins processing another schedule instead. Specify thatschedule's name (up to eight characters) as the value for ABEND. Thisalternative is a valuable rerun tool.

Suppose that a job runs to normal completion but returns a completion codegreater than zero. What happens then? It depends on the value you define forFAIL CODE on the job base record. FAIL CODE specifies the threshold fordetermining whether a job failed. If any job ends with a return code greaterthan or equal to the value defined for FAIL CODE, Unicenter CA-Schedulergives that job a status of FAILED which means successors to this job will notbe satisfied. Values for FAIL CODE can range from 1 to 4095. If FAIL CODE= 0 on the job base record, Unicenter CA-Scheduler does not check returncodes.

What will happen if a job never runs at all? If the production workload is toogreat, what happens to the selected jobs that do not run? The term backlogidentifies jobs that do not run on the day they are scheduled and are carriedover to the next day's workload.

If BACKLOG=NO on a schedule base record, that schedule's jobs will never bebacklogged unless you override this value on job records. Jobs will only bebacklogged if: 1) BACKLOG = YES on their job base records, or 2) the job issubmitted or started at the time of the next autoscan.

Suppose a job is carried over into tomorrow's workload. What happens if thatjob is selected again tomorrow? Tomorrow's job is added to the workload aftertoday's backlogged schedule has completed or been canceled.


3.9 Defining Jobs

3.9.3.9 How Do You Phase Unicenter CA-Scheduler into Production?

Fields on both the schedule and job base records allow you to implementUnicenter CA-Scheduler in stages:

■ AUTO SELECT on the schedule base record ■ LIBRARY TYPE

AUTO SELECT on the schedule base record controls whether UnicenterCA-Scheduler evaluates this schedule automatically during autoscan. WhenAUTO SELECT = NO, this schedule is skipped and these jobs are not includedin the daily workload. That is exactly what you want to happen while you aredeveloping definitions for a schedule's jobs. Once you have verified thosedefinitions using the Analyze and simulation reports, set AUTO SELECT =YES to include this schedule in the evaluation process that occurs at everyautoscan. Although this schedule may already include production work, youcan let Unicenter CA-Scheduler take control of the selection of this work byspecifying AUTO SELECT = YES.

The next implementation phase permits you to monitor UnicenterCA-Scheduler's operation while it submits dummy JCL for each of your jobs.This gives you three important capabilities:

■ When you are first implementing Unicenter CA-Scheduler, you can run theproduct in parallel with your normal production. Without affecting yourregular operation, you can verify that Unicenter CA-Scheduler isprocessing your workload as planned.

■ Even experienced Unicenter CA-Scheduler sites use this technique toprepare for implementing new applications. TESTLIB enables you to defineand test definitions for applications that are not yet ready to go intoproduction. You can check your selection criteria and verify the order inwhich jobs will run before they have even been handed over toproduction.

■ You can also test the effect of abended and failed jobs by using TESTLIB tocause those conditions for specific jobs.

To initiate this phase, change AUTO SELECT to YES on the schedule baserecord and set LIBRARY TYPE to TESTLIB. Remember that if LIBRARY TYPEis defined at the job level, it overrides the value you specify on that job'sschedule base record. You can quickly verify what library type applies to yourjobs by checking that value on the Job Directory panel.

When Unicenter CA-Scheduler sees that LIBRARY TYPE = TESTLIB, itconstructs the JCL to run a simple Computer Associates utility program:CAJUTSTA.

You can use TESTPARM=testparm on individual jobs to cause the testprogram to abend, to pass a nonzero completion code, and to have it wait fora number of seconds. Thus, you can test the effect of abending and failing jobson the rest of the schedule.


3.9 Defining Jobs

When you are ready to automate the selection process, set AUTO SELECT =YES and identify where the JCL for these jobs is stored using the fieldsdescribed in the topic What JCL Does Unicenter CA-Scheduler Submit ForCPU Jobs.

3.9.3.10 What Job Fields are Used for Simulation?

Without actually executing your jobs, simulation produces reports showing:

■ Which jobs would be selected■ What resources would be required■ When and where each job would be processed■ How heavily each device would be utilized■ Which jobs would be late■ Which jobs would carryover to the next day

Because simulation is such an effective planning tool, take the time to supplythe data needed to run simulation. First, indicate which CPU these jobs runon. See the topic Which CPU Should Jobs Run On for instructions showinghow that is done. Then specify the other data required to run simulations.

AVERAGE TIME allows you to override the computed average run times forthis job derived from historical data. If you specify a value here, UnicenterCA-Scheduler uses that time for simulation. The value reflects how much timeelapsed between when the job starts and ends. If you do not specify a valuehere, Unicenter CA-Scheduler averages the elapsed times for the last sevendays the job ran.

You can change the value for AVERAGE TIME to determine the impact ofproduction changes before they actually happen. First, run simulation withUnicenter CA-Scheduler's computed value for AVERAGE TIME. Then key in adifferent value and rerun simulation. By comparing the reports, you will beable to see the impact of such a change on your production workload.

Unicenter CA-Scheduler uses POWER CLASS to assign jobs to partitions onthe simulation reports. POWER CLASS should correspond to the value of theCLASS parameter on JOB statements submitted to POWER (a single character,0-9 or A-Z). Since that field occurs on both the schedule and job base record,you only need to specify POWER CLASS for a job if the value on its schedulebase record is not appropriate for this job.

To refine the accuracy of your simulation runs, define the resources each jobrequires on the job resource record (JRR). This information is not required torun simulation. However, unless resources have been defined, you will not beable to USE SIMTIME to start schedules and jobs. Instruction on how that isdone are found in the topic Defining A Job's Resource Record.


3.9 Defining Jobs

3.9.3.11 How and When Can You Display Documentation Automatically?

User documentation can be built according to whatever standards you want. Itis done using full-panel editing facilities provided with UnicenterCA-Scheduler. Each documentation member in this documentation file is givenan eight-character key and this along with the schedule name or job name (andjob number and station) comprise the name that is used to uniquely identify it.You can at any time, view this information by using the DocumentationMaintenance panel.

If the job has a documentation key defined, the contents of that documentationlibrary member will be printed as part of the forecast and simulationcomponents, if requested.

When defining a job using the Job Definition panel, you can specify a DISPLYKEY and a DISPLAY TIME. If the job is a CPU job (station 40), then the namein the DISPLY KEY field will have its documentation displayed on the masteroperator console at the time of day specified in the associated DISPLAY TIMEfield. This will happen automatically. If you do not use the DISPLAY TIMEfield, but a DISPLY KEY field is specified, the documentation members willdisplay at autoscan time.

If the job is a non-CPU job, the user starting the job will receive a messagesaying that there is documentation associated with the job and the name of thedocumentation member. The user can then display it. If the non-CPU job isautomatically started (AUTO START=YES), then the message is sent to theusers in the SEND START MESSAGES TO list defined on the job's MessageDefinition panel.

3.9.3.12 What Happens When Jobs Run Late?

Unicenter CA-Scheduler helps you manage your production workload byalerting you to potential problems as quickly as possible. Therefore, whenUnicenter CA-Scheduler knows jobs are running late, it will warn you byissuing messages. You can control when the messages are issued and whoreceives them using fields on both schedule and job records and the MSGgeneration macro parameter.


3.9 Defining Jobs

SBR: Schedule base recordSRC: Schedule reason code recordJBR: Job base recordJRC: Job reason code recordJMR: Job message record

You can specify times in different ways:

MAXIMUM EXECUTION TIME tells Unicenter CA-Scheduler how long itshould take to process this job. The chart following illustrates the differentways you can specify maximum execution time. Notice that leading zeros canbe omitted.

If You WantNotification

Specify This Value On The

When schedules start late

miss their deadlines

run too long

MUST TIMEs orMUST START BY TIME

DEADLINE TIMEs orCOMPLETION DEADLINE TIME

MAXIMUM TIMEs orMAXIMUM EXECUTION TIME

SRCSBR

SRCSBR

SRCSBR

When jobs start late

miss their deadlines

run too long

abend

are interrupted

MUST TIMEs orMUST START BY TIME

DEADLINE TIMEs orCOMPLETION DEADLINE TIME

MAXIMUM TIMEes orMAXIMUM EXECUTION TIME

SEND ABEND MESSAGES TO

INTERRUPT = YES andSEND INTERRUPT MESSAGE TO

JRCJBR

JRCJBR

JRCJBR

JMR

JBRJMR


And Means The Schedule Or JobShould Finish

30 mm Thirty minutes after it starts

200 hhmm Two hours after it starts

10200 ddhhmm The next day two hours after itstarted (26 hours later)


3.9 Defining Jobs

Use a 24-hour clock to specify MUST START BY TIME and COMPLETIONDEADLINE TIME. The chart following shows that you can omit leading zerosand you can extend the 24-hour clock by days.

Warning messages are sent to the operator if OPERATOR was specified on theMSG installation option. However, you can route those messages to any otheruserid by specifying that userid as the value for the MSG installation option. Ifyou want messages sent to other userids, you can specify them in the scheduleand job message records (SMR and JMR).

You can specify MAILBOX as one of the userids, and the messages will be sentto a common mailbox where they can be viewed using the Reporting Facilitypanel.


And Means Late Messages Will BeIssued

930 hhmm After 9:30 a.m. that day

1400 hhmm After 2 p.m. that day

11800 ddhhmm After 6 p.m. the next autoscan day

3.9.3.13 How Do You Create Optional Job Records?

The RECS fields at the bottom of job panels fulfill two functions:

■ The values displayed show whether each type of record already exists forthis job. N means that type of record hasn't been defined yet.

■ The fields allow you to input commands that will branch to these records.The chart following shows what these commands can do.

The chart following explains the purpose of each record type.

If The Current Value Is Enter To

N C Create that record

Y AD

Alter that recordDisplay that record

If You Want To Select This Record By Typing After

Define

■ The days on which thejob is selected

■ Predecessor conditionsthat must be satisfied

job criteria JCR:


3.9 Defining Jobs

These types of records will be discussed in the topic called Defining OptionalJob Records.

If You Want To Select This Record By Typing After

Assign different times to thejob when it is selected fordifferent reasons.

job reason code JRC:

Add information that will beprinted on reports

job information JIR:

Send messages to usersinforming them of the job'sprogress

job message JMR:

Define the resources a jobrequires

job resource JRR:

3.9.3.14 Copying Jobs

The following text describes a much quicker method. You can do this bycopying an existing job.

� � SCHD-JM ��JOB MAINTENANCE�� Scheduler

===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------









PF1=HELP

� �

Begin by using option 1 of the Job Maintenance menu. Notice that Schedulerexpects you to specify select criteria when you choose option 1. Use the job'sname. Type 1,DEFAULTS in the command area and pressing ENTER.

Scheduler responds by displaying the Job Directory panel:


3.9 Defining Jobs

� � SCHD-JD � JOB DIRECTORY � Scheduler

===> _ MASTER - WR

CONNECT : 4�

B C I M R R N C C

JOBNAME ST JNO SCHEDULE LIBTYPE MEMBER SYS R R R R C R R S E

DEFAULTS 4� �1 BACKUP CMS DEFAULTS Y


PF1=HELP

� �

The preceding panel allows you to copy a job definition: to use one jobdefinition as the prototype for another. Type C on the line describing theDEFAULTS job and press Enter. Unicenter CA-Scheduler responds bydisplaying the following panel:

� � SCHD-JU � JOB DEFINITION � Scheduler

===> MASTER - WR

CONNECT : 4�

JOB NAME : _ PROTOTYPE JOB: DEFAULTS JNO: �1 STN: 4�

JOB NUMBER : �1 PROTOTYPE JOB IN SCHEDULE : BACKUP




MEMO :



MEMBER NAME : DEFAULTS SLI SUBLIB : ICCF LIB NUMBER:






MUST START BY TIME : �� COMMANDS AT JOB START: N




RECS= JBR: Y JCR: N JRC: N JIR: N JMR: N JRR: N JNR: N PF1=HELP

� �

Now you can define a job while seeing all the defaults that would apply to it.Next, define a job called IH7D02. Type IH7D02 as the job name. Then tabdown to MEMBER.

MEMBER NAME identifies where the JCL for this job is stored. Most sitesname the members in their production libraries to correspond with job names,so MEMBER NAME defaults to JOB NAME. Notice that DEFAULTS is thecurrent value of MEMBER NAME. Since the JCL for this job is stored in amember named IH7D02, type in that value here.

Next, look at the optional job records Unicenter CA-Scheduler uses toimplement other features. Tab to the bottom of your panel and enter Cs forevery record type except JBR. C indicates that you want to create theserecords.


3.9 Defining Jobs

The next topic discusses the optional job records in detail.

The Job Defines

Criteria record (JCR) - when to select a job less frequently than itsschedule- more or different predecessors for this job

Reason code record (JRC) Different times for running the job dependingon the reason why it was selected that day

Information record (JIR) More information that only applies to this job

Message record (JMR) Messages to send users, informing them ofthe job's progress

Resource record (JRR) Resources required to process the job

Node Record (JNR) Nodes to inform when this job starts andends

3.9.4 Defining Optional Job RecordsAfter the base record is successfully added to the database, pressing Enter willtake you through all of the optional panels that you indicated you want todefine. Now that you are familiar with the fields on the job base record,optional job records will be described.

3.9.4.1 Defining a Job Criteria Record

When you select JCR, Unicenter CA-Scheduler displays an editor panel whereyou define the job criteria record. This record can tell Unicenter CA-Schedulera variety of things:

■ The predecessors you defined for this job.■ That you do not want this job to run every time this schedule is selected

(because a calendar is specified or the criteria statement includes selectionkeywords)

■ That you want to give different reasons for selecting this job so you candefine different start times or keep separate statistics for each reason.

If you do not define a criteria record for a job, that job will be selected everytime the schedule is selected and its only predecessors will be those definedfor its schedule.

The top line of the Criteria Definition panel identifies which job this recordapplies to. If that schedule uses a calendar for selection instead of a datetable,that calendar name appears following C=. To move the cursor into the areawhere you define criteria, press the TAB key once.


3.9 Defining Jobs

� � SCHD-JCRE DEF C= J=IH7D�2 JN=�1 ST=4� S=BACKUP CA-Scheduler

===>

RANGE=�1-72

1...+....1....+....2....+....3....+....4....+....5....+....6....+....7...

MON OR /�EVERY MONDAY OR �/ ��1

TUE OR /�EVERY TUESDAY OR �/ ��2

WED OR /�EVERY WEDNESDAY OR �/ ��3

THU /�EVERY THURSDAY �/ ��4

��5

��6

��7

��8

��9

��1�

��11

��12

��13

��14

��15

��16

��17

��18

��19

1...+....1....+....2....+....3....+....4....+....5....+....6....+....7...

� �

Next, define this job to run Monday through Thursday. Type in the criteriastatement shown preceding to define four reasons for selecting this job.

Although it really does not matter where on this panel you enter your criteria,we recommend you type each reason for selecting a job on a separate line sothat it is easier to see which reasons here correspond with fields on the job'sreason code record. If there is more than one reason for selecting a job, eachreason ends with OR (except the last one, of course).

Note: Multiple ORs can be grouped into a single reason code by placingparentheses around this reason. (See the chapter "Criteria Language" formore details.)

When you write criteria, you can embed comments anywhere by using /* as abeginning delimiter and */ as an ending delimiter. These delimiters can appearon different lines if the comment is longer than one line.

The preceding criteria statement will cause Unicenter CA-Scheduler to selectthis job less frequently than the rest of the schedule. That means UnicenterCA-Scheduler selects the BACKUP schedule every day. On Monday throughThursday, Unicenter CA-Scheduler puts this job in the daily workload.


3.9 Defining Jobs

The criteria statement you just defined contains no predecessors. Therefore,this job will be submitted when:

■ The schedule's early start time is reached■ The schedule's predecessor conditions have been met■ The job's start time is reached and■ The job's defined resources are available

Note: Predecessors in job records are not evaluated until its schedule hasstarted and the job's early start time has been reached.

For complete information on coding criteria statements, see the chapter"Criteria Language."

To save this criteria record and leave this panel, type FILE in the commandinput area. Otherwise, you could leave the panel without saving this criteriarecord by typing QUIT. All of the editor commands are in the appendix"Editor Commands" in the Unicenter CA-Scheduler Reference Guide.

The FILE command causes Unicenter CA-Scheduler to immediately create thatjob's criteria record. After you press Enter, Unicenter CA-Scheduler displaysthe following panel, which confirms that record has been created:

� � SCHD-UTIL ��SCHDUTIL OUTPUT�� Scheduler

===> MASTER - WR

CONNECT : 4�

DEFINE JCR S=BACKUP,NAME=IH7D�2,JNO=�1,ST=4�,CRI='

MON OR

TUE OR

WED OR

THU'

CACU�18I JCR IH7D�2 HAS BEEN ADDED

PF1=HELP

� �

To advance to the next panel, press Enter.

3.9.4.2 Defining a Job's Reason Code Record

If you defined a criteria record for a job, you may also want to use the optionsavailable on a job's reason code record. That record allows you to definedifferent values for the following fields:

■ AVERAGE TIME■ EARLIEST START TIME■ MUST START BY TIME■ COMPLETION DEADLINE TIME■ MAXIMUM EXECUTION TIME

A job reason code record works just like a schedule's reason code record:


3.9 Defining Jobs

■ It is only valid if a criteria record exists for that job and selection is notaccomplished by a calendar.

■ It allows you to define up to 16 different values for certain fields, one foreach reason why this job could be selected.

■ Scheduler checks to see the reason why a job was selected, and thenapplies the corresponding values when processing the job that day.

The only difference is that a job's reason code record applies to a specific jobwhile a schedule's reason code record applies to that schedule. A job's valuesdo not default to its schedule's values. Type the displayed values under MUSTTIME LIST and MAXIMUM TIME LIST.

� � SCHD-JRC ��REASONS DEFINITION�� Scheduler

===> MASTER - WR

CONNECT : 4�

JOB NAME : IH7D�2 PROTOTYPE JOB: JNO: STN:

JOB NUMBER : �1 PROTOTYPE JOB IN SCHEDULE :

STATION ID : 4�


AVG TIME LIST:

�1 �2 �3 �4 �5 �6 �7 �8

�9 1� 11 12 13 14 15 16

EARLY TIME LIST:

�1 �2 �3 �4 �5 �6 �7 �8

�9 1� 11 12 13 14 15 16

MUST TIME LIST:

�1 2215 �2 2315 �3 2315 �4 2315 �5 �6 �7 �8

�9 1� 11 12 13 14 15 16

DEADLINE TIME LIST:

�1 �2 �3 �4 �5 �6 �7 �8

�9 1� 11 12 13 14 15 16

MAXIMUM TIME LIST:

�1 15 �2 1� �3 1� �4 1� �5 �6 �7 �8

�9 1� 11 12 13 14 15 16

RECS= JBR: Y JCR: Y JRC: N JIR: N JMR: N JRR: N JNR: N PF1=HELP

� �

The Reasons Definition panel allows you to specify up to 16 different valuesfor these five fields, which have meanings similar to fields found on the job'sbase record. Unicenter CA-Scheduler matches these values with the reasonsdefined on the job's criteria record: the first values here apply to the firstreason the job was selected, and so on. Our example shows different valuesdefined for two fields. How does this relate to the job's criteria statement andthe schedule's reason code record?

■ On Mondays, Unicenter CA-Scheduler will issue warning messages if thisjob does not start by 10:15 p.m. or runs longer than 15 minutes.

■ On other days, messages are issued if the job hasn't started by 11:15 p.m.or it takes longer than 10 minutes to run.

■ The schedule's reason code record sets the default early start times for allthe jobs in this schedule based upon the reason why the schedule wasselected. None of a schedule's non-CPU jobs can be started and none of itsCPU jobs can be submitted until the schedule's start time has beenreached.


3.9 Defining Jobs

■ MAXIMUM TIMEs have been defined for the schedule as well as this job.The job's record sets limits on how long this one job should run, but theschedule's record limits how long the entire schedule can take.

Descriptions of all five fields on this panel follows.

AVG TIME Tracks how long the job takes for up to 16 reasons whyit might be selected. AVG TIME on the job's record doesnot override the values for AVG TIME on the schedule'srecord because these fields describe two different things:how long an entire schedule or only one job usuallytakes to run. Instead, the AVG TIMEs you specifyoverride the actual average run times derived fromhistorical data.

EARLY TIME Allows you to specify different EARLIEST START TIMEsfor each reason this job is selected. If you leave thesefields blank, Unicenter CA-Scheduler uses the value onthe job's base record every time the job is selected.Notice that a schedule's EARLY TIME must be reachedbefore Unicenter CA-Scheduler considers submitting anyof its jobs.

MUST TIMEs Tell Unicenter CA-Scheduler to issue late messages if thejob hasn't started by the time specified for each reasonjobs can be selected. If you leave these fields blank,Unicenter CA-Scheduler uses the value for MUSTSTART BY TIME on the job's base record instead.

DEADLINE TIMEs Tells Unicenter CA-Scheduler to issue late messages ifthis job isn't finished by the time specified. Specifyvalues here if you want to define different deadlines foreach reason the job was selected. These values overridethe COMPLETION DEADLINE TIME you may havespecified on the job base record. Notice that thesedeadlines apply to a specific job while those on schedulerecords define when all the jobs in that schedule must becompleted.

MAXIMUM TIMEs Sets limits on how long a job should run. If it takeslonger, Unicenter CA-Scheduler will issue a latemessage. Specify values here if you want to definedifferent durations for each reason the job was selected.These values override the MAXIMUM EXECUTIONTIME specified on the job's base record. MAXIMUMTIME on job records define how long a job should taketo run, but on schedule records, MAXIMUM TIMEshows how long all the jobs in that schedule run.

What happens if you define more than 16 reasons in a criteria statement? Thetimes for any reasons beyond the 16th default to the values defined on thejob's base record.


3.9 Defining Jobs

Now that you are familiar with these fields, finish creating this reason coderecord. After you have finished filling in fields on this panel, press Enter.Unicenter CA-Scheduler immediately creates this record and confirms it withthis message.


===> MASTER - WR

CONNECT : 4�

DEFINE JRC NAME=IH7D�2,JNO=�1,STATION=4�,SCHEDULE=BACKUP,MUST�1=2215,

MUST�2=2315,MUST�3=2315,MUST�4=2315,MAX�1=15,MAX�2=1�,MAX�3=1�,

MAX�4=1�

CACU�18I JRC IH7D�2 HAS BEEN ADDED

PF1=HELP

� �

Use of reason codes provides you with scheduling flexibility. To advance tothe next panel, press Enter.

3.9.4.3 Defining a Job Information Record

All the job records you have defined so far contain information that affectshow Unicenter CA-Scheduler automates production at your site. However, ajob's information record is primarily for your use. It stores descriptiveinformation about this job that helps your staff wrap up the work UnicenterCA-Scheduler began for you.

� � SCHD-JIR ��INFO DEFINITION�� Scheduler

===> MASTER - WR

CONNECT : 4�



STATION ID : 4�


DESCRIPTION : JUST WHAT IS CHANGED

COMMENT : MON-THU

EXITPARM:

FORM :

NOTIFY : VERIFY:

QUANTITY :

RESPONSIBILITY:

SPECIFICATION :

DESTINATIONS-1: rm112 2: 3: 4:

5: 6: 7: 8:

DELIVERABLES:

1: backup tapes 2: 3: 4:

5: 6: 7: 8:

RECS= JBR: Y JCR: Y JRC: N JIR: N JMR: N JRR: N JNR: N PF1=HELP

� �

Unicenter CA-Scheduler only reacts to one field on the job information record:EXITPARM. It adjusts the class or average processing time of this job duringsimulation. Unicenter CA-Scheduler passes this optional value of up to 16bytes to an optional user exit.


3.9 Defining Jobs

DESTINATIONS and DELIVERABLES allow you to record where to send theoutput for this job. Notice that the panel preceding shows IH7D02 producesbackup tapes for delivery to room 112. These fields are only used in reports.

Next, create the information record shown preceding. As you tab from field tofield, type in the data displayed on the panel preceding. After you have inputthat information, you are ready to create the information record.

After you have filled in the panel, press Enter to save the information recordfor that job. Unicenter CA-Scheduler confirms that it stored that information bydisplaying the following panel:


===> MASTER - WR

CONNECT : 4�

DEFINE JIR NAME=IH7D�2,JNO-�1,STATION=4�,SCHEDULE=BACKUP,

DESC='JUST WHAT IS CHANGED',COMMENT='MON-THU',DEST1='RM112',

DEL1='BACKUP TAPES'

CACU�18I JIR IH7D�2 HAS BEEN ADDED

PF1=HELP

� �

To view the next panel, press Enter. That displays the panel that defines thejob's message record.

3.9.4.4 Creating a Job Message Record

The job's message record extends Unicenter CA-Scheduler's progressnotification capability beyond schedules to jobs. By defining this record, youcan notify users of the progress made by an individual job:

■ When jobs start or end■ Or only when they end unsuccessfully■ When they are late starting or ending■ When jobs require human intervention■ When jobs run too long

So the schedule's message record identifies who needs to be notified about aschedule's progress while a job's message record specifies who to tell about ajob's progress.


3.9 Defining Jobs

� � SCHD-JMR ��MESSAGE DEFINITION�� Scheduler

===> MASTER - WR

CONNECT : 4�



STATION ID : 4�


SEND ALL MESSAGES TO :

SEND START MESSAGES TO :

SEND END MESSAGES TO :

SEND LATE MESSAGES TO : operator

SEND ABEND MESSAGES TO : operator

SEND FAIL MESSAGES TO : operator

SEND INTERRUPT MESSAGE TO:

RECS= JBR: N JCR: N JRC: N JIR: N JMR: N JRR: N JNR: N PF1=HELP

� �

You can initiate every kind of job progress reporting by filling in one field onthe job message record. If that is the only field you fill in on this record, alljob-related messages will go to that ID. Suppose you entered YOURID as avalue for SEND ALL MESSAGES. If you fill in other fields on this record, itaffects which messages go to YOURID. YOURID will get only those messagesnot routed elsewhere. If you really want YOURID to get all messages, be sureto include YOURID in every userid list you specify on this panel.

You can list up to four userids separated by commas in any of these fields. Tosend any kind of message to the master console, specify OPERATOR as one ofthe userids.

You can also specify MAILBOX as one of the userids, and the messages will besent to a common mailbox where they can be viewed using the ReportingFacility panel.

The panel preceding creates a job message record that sends abend, fail, andlate messages to the master console. Try creating that record on your own bytabbing to these fields and typing the value OPERATOR.

Unicenter CA-Scheduler needs to know more to produce some of thesemessages. The chart following tells you what fields need to be completed toactivate each kind of message.

For These Messages Specify On The

Start messages SEND START MESSAGES JMR

End messages SEND END MESSAGES JMR


3.9 Defining Jobs

You can send a message when this job misses its deadline because you alreadydefined deadlines on the job's reason code record.

Then press Enter to save the job's message record. Unicenter CA-Schedulerresponds by displaying the following message:


===> MASTER - WR

CONNECT : 4�

DEFINE JMR NAME=IH7D�2,JNO=�1,STATION=4�,SCHEDULE=BACKUP,

LATEMSG=(OPERATOR),ABENDMSG=(OPERATOR),FAILMSG=(OPERATOR)

CACU�18I JMR IH7D�2 HAS BEEN ADDED

PF1=HELP

� �

To view the next panel, press Enter.

For These Messages Specify On The

Late messages -SEND LATE MESSAGES and-MUST START BY TIMEMUST TIMEs-COMPLETION DEADLINE TIME orDEADLINE TIMEs-MAXIMUM EXECUTION TIME orMAXIMUM TIMEs

JMRJBRJRCJBRJRCJBRJRC

Abend messages SEND ABEND MESSAGES JMR

Fail messages SEND FAIL MESSAGES JMR

Interrupt messages INTERRUPT and SEND INTERRUPTMESSAGE

JBRJMR

3.9.4.5 Defining a Job Resource Record

The job resource record provides the information needed to run simulations.Most of the fields show what types of devices your job requires. UnicenterCA-Scheduler even maintains several key fields itself using data. To explorethis record in more detail, enter the displayed data in the appropriate fields:


3.9 Defining Jobs

� � SCHD-JRR ��RESOURCE DEFINITION�� Scheduler

===> MASTER - WR

CONNECT : 4�



STATION ID : 4�


MAX CPU TIME : ROUTE DELAY :

SEPARATE DSNAME:

SEPARATE JOBS

LIST:

DASD�1 : 338�,2 DASD�2 :

DASD�3 : DASD�4 :

DASD VOLSERS :

DASD EXCPS :

TAPE�1 : 348�,1 TAPE�2 :

TAPE�3 : TAPE�4 :

TAPE EXCPS:

UNIT�1 : UNIT�2 :

UNIT�3 : UNIT�4 :

UNIT EXCPS:

RECS= JBR: Y JCR: Y JRC: Y JIR: Y JMR: Y JRR: N JNR: N PF1=HELP

� �

First, let us focus on three fields that affect when jobs are actually processed:

SEPARATE DSNAME Identifies a data set that can only be used by onejob at a time. That means while this job isrunning, all other jobs are prevented from usingthat data set. Unicenter CA-Scheduler accepts upto 44 characters for a SEPARATE DSNAME. Forthis option to be effective, you must also definethis data set as a SEPARATE DSNAME for everyjob that uses this data set.

SEPARATE JOBS LIST Accepts up to eight entries that identify jobs thatare submitted or started or that cannot run on thisCPU while this job is running. If JOBA cannotrun with JOBB, then JOBB cannot run with JOBAwhich means every job mentioned here also needsa JRR of its own that names this job in itsSEPARATE JOBS LIST. When specifying morethan one job name, use commas between them, oruse mask characters. Mask characters identify agroup of jobs by defining the characters that thesejob names have in common. The chart followinggives several examples of how to use maskcharacters.

To Separate All Jobs That Specify

Start with PAY PAY*

End with 0100 0100


3.9 Defining Jobs

For more information about mask characters, seethe definition in the Glossary.

DASD VOLSERS Specifies up to eight DASD volumes that must bemounted before this job can be submitted.Specifying them here does not get the devicesmounted. Instead, it causes UnicenterCA-Scheduler to set job status to WAITING FORRESOURCES until all of the DASD VOLSERslisted here are mounted. When UnicenterCA-Scheduler sees that those resources areavailable, it then submits the job. When specifyingmore than one DASD VOLSER, use commasbetween them. To refine the accuracy of yoursimulations, define values where appropriate forthe fields described preceding as well as thefollowing:

■ Identify how many of each type of DASD,tape and unit record devices this job uses. TheDASD types entered here must matchresources listed for the CPU's station record.Unicenter CA-Scheduler has allocated roomfor up to four different entries for each type ofdevice.

■ For example, if this job uses two 3380s, setDASD01 = 3380,2. That tells UnicenterCA-Scheduler that it should not simulateprocessing until:

– Start time has been reached– All predecessor conditions have been

satisfied– Those defined resources are available

If this job is processed at several workstations, you may need to define aROUTE DELAY. Estimate how long it takes this job to get to this station fromthe preceding one. This routing delay could take minutes or even days. Thechart following shows your options for specifying ROUTE DELAY:

To Separate All Jobs That Specify

Somewhere contain the string QUEL *QUEL*

Start with PAY and end with 00 PAY*00

Start with P and the third character is Y P?Y*


3.9 Defining Jobs

JOB NAME, JOB NUMBER, STATION ID and SCHEDULE NAME alwaysrequire the appropriate values. If you create a job's resource record by typingC next to JRR in a RECS field, you do not have to fill in these values becauseUnicenter CA-Scheduler does that for you. If you try copying another job'sresource record by issuing a CRR command on the Job Directory panel, youwill need to enter the appropriate values for these fields.

The remaining fields do not require input:

■ PROTOTYPE JOB, JNO, STN and PROTOTYPE JOB IN SCHEDULE areonly useful if you want to copy another job's resource record. Since there isa more convenient method for copying records, leave these fields blank.

■ Scheduler maintains MAX CPU TIME, DASD EXCPS, TAPE EXCPS andUNIT EXCPS using data. However, these fields also accept input. If youenter values in these fields, they become the new values used in all futuresimulations.

Next, define this job's resources. Enter the values shown on the panelpreceding. DASD01 = 3380,2 shows that this job uses two 3380s. And TAPE01= 3480,1 means this job uses one 3480 tape drive. When UnicenterCA-Scheduler simulates this job, it will know this job cannot run until thoseresources are available.

Be very careful when defining resources: only specify device types that are alsodefined as resources on station records. Unicenter CA-Scheduler does notverify that your job's resources exist at the specified station when you define ajob's resource record. If you specify an undefined station resource, thesimulation report will always show this job as waiting for resources.

To save the job's resource record, press Enter. Unicenter CA-Schedulerresponds by displaying the following message:


===> MASTER - WR

CONNECT : 4�

DEFINE JRR NAME=IH7D�2,JNO=�1,STATION=4�,SCHEDULE=BACKUP

DASD�1=(338�,2),TAPE�1=(348�,1)

CACU�18I JRR IH7D�2 HAS BEEN ADDED

PF1=HELP

� �


And Means The Job Is Delayed

30 mm Thirty minutes because of routing

200 hhmm Two hours

10200 ddhhmm 26 hours due to routing (1 day + 2 hours)


3.9 Defining Jobs

To view the last optional job record, press Enter.

3.9.4.6 Defining Job Node Records

The last type of optional record is only used if you have a CPU network thatuses NJE and Unicenter CA-Scheduler with the NJE option activated at everymember of every node. Job node records contain the information necessary toimplement a specialized feature of the criteria language: NJE. The criterialanguage allows you to define predecessors that reference jobs running at othernodes. For example, suppose that JOBA is defined and runs on the node inNew York. JOBA is a predecessor of JOBB, but JOBB is in a schedule that isdefined at the Phoenix site.

How will the node in Phoenix know the status of JOBA in New York? That isthe purpose of the job node record: to inform other nodes of status of aspecific job. Define a job node record for jobs that are predecessors of jobs thatare defined at different nodes.

� � SCHD-JNR ��INFORM DEFINITION�� Scheduler

===> MASTER - WR

CONNECT : 4�



STATION ID : 4�


INFORM NODES: NEWYORK

RECS= JBR: Y JCR: Y JRC: Y JIR: Y JMR: Y JRR: Y JNR: N JNR: N PF1=HELP

� �

INFORM NODES requires you to specify at least one node ID: the node wherethis job's successor runs. Suppose that after IH7D02 backups up critical files inPhoenix, the national TP network can be started in New York which meansthat IH7D02 runs in Phoenix and has a successor in New York that is waitingfor IH7D02 to complete normally. By specifying NEWYORK in the INFORMNODES field, you ensure that New York is notified when IH7D02 finishessuccessfully.

Scheduler allows you to specify up to eight different node IDs separated bycommas:

INFORM NODES: node1,node2,node3,...,node8


3.9 Defining Jobs

The node IDs you specify here must also be listed in the CAIJNET installationmacro. To avoid undue overhead, only specify the node IDs that havepredecessor jobs waiting on this job's progress. It is not necessary, nor is itadvisable, to list the node ID where the job runs.

Then press Enter to save the job's node record. Unicenter CA-Schedulerresponds by displaying the following message:


===> MASTER - WR

CONNECT : 4�

DEFINE JNR NAME=IH7D�2,JNO=�1,STATION=4�,SCHEDULE=BACKUP

INFORM=(NEWYORK)

CACU�18I JNR IH7D�2 HAS BEEN ADDED

PF1=HELP

� �

Press Clear to return to the Job Maintenance panel before starting the nexttopic.


3.10 Displaying and Updating a Job Definition


To correct errors detected by the ANALYZE command or to make any otherchanges to job definitions, you can retrieve a record from the database, displayit and alter it. There are several ways to do this:

■ Go to the Job Maintenance menu and select the ALTER function by typing3 in the input area. You must also give the name of the job you want toalter. Then press Enter.

■ Display the Job Directory panel by going to the Job Maintenance menu andpressing ENTER. When the directory appears, move the cursor to the jobyou want to alter and type A next to it. This allows you to alter a numberof definitions quickly without having to return to the Job Maintenancemenu each time.

■ Another shortcut uses the RECS= line to edit related job records. If youhave displayed one job record and want to edit another record belongingto the same job, enter A after the appropriate field on the REC= line.

■ The fastest method for editing allows you to go directly to any optional jobrecord from the Job Directory panel. Enter a three-letter code to indicatewhat you want to do and which record to do it to. This method isexplained in detail later in this topic.

The first method parallels what you have learned about editing other types ofrecords, so that will not be repeated here. Other methods of editing are shownfollowing.

Two factors determine who can update a job record:

■ A user's authority level■ The USERS defined on the corresponding schedule base record

Supervisor authority allows users to update all jobs that run at stationsspecified on their userid records. People with Manager authority can updateall job records for every workstation, but users with General authority can onlyupdate jobs belonging to public schedules and schedules that specificallydefine them as USERS.

Begin by checking which option on the Job Maintenance menu allows you toalter existing records:




===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------









PF1=HELP

� �

This panel tells you to press Enter to display a complete directory of jobs. Thatpanel appears following:


===> MASTER - WR

CONNECT : 4�

B C I M R R N C C



IH7D�2 4� �1 BACKUP CMS IH7D�2 Y Y Y Y Y Y Y

�� END OF DATA ��

PF1=HELP

� �

From this panel you can display or alter any type of job record. Enter thefollowing commands next to the job name.

To Type This Next To The Job Name

Display a record base criteria information message node reason code resource

DDCRDIRDMRDNRDRCDRR



Next, change job IH7D02. Other fields occur on the right of this panel, butignore them for now. Instead, press the TAB key twice to move the cursor tothe line that describes the job IH7D02. Then type A and press Enter.

If an unauthorized user tries to change an existing job definition, Schedulerdisplays the message:

CACO226E USER NOT AUTHORIZED FOR THIS JOB

If your authority level permits you to alter that job record, Scheduler displaysthe Job Alter panel.

� � SCHD-JU � JOB ALTER � Scheduler

===> MASTER - WR

CONNECT : 4�

JOB NAME : IH7D�2

JOB NUMBER : �1




MEMO :



MEMBER NAME : IH7D�2 SLI SUBLIB : ICCF LIB NUMBER:






MUST START BY TIME : �� COMMANDS AT JOB START : N




RECS= JBR: Y JCR: Y JRC: Y JIR: Y JMR: Y JRR: Y JNR: Y PF1=HELP

� �

To change any value on this panel, you can tab to it and type in a new value,but what if you do not want a value anymore? How do you eliminate a value?

■ To eliminate TIME values, type all zeros. For example, you can undo apreviously specified start time by filling in the field with six zeros andpressing ENTER.

■ Values for fields like MEMO can be deleted by typing NULL in place ofthe old value. Type NULL and blank out any other characters in the


Alter a record base criteria information message node reason code resource

AACRAIRAMRANRARCARR



MEMO field. That causes Unicenter CA-Scheduler to eliminate the value itpreviously stored for MEMO.

While you are altering the job base record, you can also create or edit optionaljob records by changing RECS values. Currently, the RECS values show youwhich types of records already exist:

■ Y means the record has been defined.■ N means those record types do not exist.

The RECS fields also accept input. You can tab to any RECS value and entercodes that allow you to create, alter or display those job records. In thefollowing fields enter C to create, A to alter, or D to display.

To edit the job's criteria record, type A in the JCR field, and then press Enter.Scheduler first changes the job base record and returns the following message:


===> MASTER - WR

CONNECT : 4�

ALTER JBR LASTUSER=MASTER,NAME=IH7D�2,JNO=�1,STATION=4�,SCHEDULE=BACKUP

CACU�18I JBR IH7D�2 HAS BEEN ALTERED

PF1=HELP

� �

To move on to the job's criteria record, press Enter.

The Criteria Definition panel displays the record you defined for this jobearlier:

Enter C, A, Or D Next To Which Is This Type Of Record

JBR Job base record

JCR Job criteria record

JRC Job reason code record

JIR Job information record

JMR Job message record

JRR Job resource record

JNR Job node record



� � SCHD-JCRE DEF C= J=IH7D�2 JN=� 1 ST=4� S=BACKUP Scheduler

===>

RANGE=�1-72

1...+....1....+....2....+....3....+....4....+....5....+....6....+....7...

MON OR /�EVERY MONDAY OR �/ ��1

TUE OR /�EVERY TUESDAY OR �/ ��2

WED OR /�EVERY WEDNESDAY OR �/ ��3

THU /�EVERY THURSDAY �/ ��4

��5

��6

��7

��8

��9

��1�

��11

��12

��13

��14

��15

��16

��17

��18

��19

1...+....1....+....2....+....3....+....4....+....5....+....6....+....7...

� �

To change the criteria statement, tab to the input area and type the correctstatement. To delete a line, tab to the numbered column at the right, type a Dand press Enter. Other editor commands are documented in the appendix"Editor Commands" in the Unicenter CA-Scheduler Reference Guide, Part 2.

To leave this panel, type one of the following commands in the command area:

■ QUIT cancels the changes you have made to the criteria statement.■ FILE stores this statement as the job's new criteria record.

To leave this panel without saving a new criteria record, type QUIT in thecommand area and press Enter.

Unicenter CA-Scheduler responds by returning you to the Job Directory panel:


===> MASTER - WR

CONNECT : 4�

B C I M R R N C C





PF1=HELP

� �

This panel focuses on the columns at the right. A Y in these columns showswhich types of job records have been created for each job listed in thedirectory:



BR = job base record

CR = job criteria record

IR = job information record

MR = job message record

RC = job reason code record

RR = job resource record

NR = job node record

CS = commands at job start

CE = commands at job end

Next, alter IH7D02's criteria record directly from this panel. Start by tabbing tothat line on the panel. Then type ACR and press Enter. The A means you wantto alter a record and CR indicates which one: the criteria record. (If you onlywanted to display that record, you wouldd type DCR instead of ACR.)

Scheduler responds by displaying IH7D02's criteria record. To save the recordtype FILE on the command line and press Enter. Whenever you alter a jobrecord, Unicenter CA-Scheduler will confirm that it is made that change in itsdatabase by displaying the appropriate message on its utility panel.


===> MASTER - WR

CONNECT : 4�

ALTER JCR NAME=BACKUP,NAME=IH7D�2,JNO=�1,ST=4�,CRI='

MON OR

TUE OR

WED OR

THU'

CACU�18I JCR IH7D�2 HAS BEEN ALTERED

PF1=HELP

� �

Press Enter to return to the Job Directory panel. Then you can continue editingjob definitions or press Clear to return to the Job Maintenance menu.


3.11 Deleting Job Records


Because there are different types of job records, Unicenter CA-Scheduler givesyou two methods for deleting them. Which method you use depends on whatjob records you want to delete. However, be advised that deleting job recordsfrom the database is a serious matter and isn't part of a normal day's activities.

If you do not know which job you want to delete, or you only want to deletean optional job record, begin by displaying a directory of jobs using the JobMaintenance menu.


===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------









PF1=HELP

� �

Pressing Enter at that menu causes the following panel to appear.


===> MASTER - WR

CONNECT : 4�

B C I M R R N C C





PF1=HELP

� �

Your entries will differ from those shown preceding, but you should be able tofind IH7D02's job record. Tab down to it.

The various deletion options this directory panel supports follow.



Next, delete this job's message record. First, check that the job actually has amessage record. The value in the MR column will be Y if a message recordexists for this job. Next, delete the job's message record by typing LMR onthat line and pressing Enter.

If you have the authority to change this job, Scheduler confirms that it deletedthat record by displaying the message:


===> MASTER - WR

CONNECT : 4�

DELETE JMR NAME=IH7D�2,JNO=�1,STATION=4�,SCHEDULE=BACKUP

CACU�18I JMR IH7D�2 HAS BEEN DELETED

PF1=HELP

� �

To return to the Job Directory panel, press Enter. Then press Clear to return tothe Job Maintenance menu so we can demonstrate the second method fordeleting job records.

The following describes how to delete all job records with a single command.Begin by checking which option on the Job Maintenance menu allows you todelete an existing record:

To Delete Enter

All records for that job (except the historyrecord)

L

Just the criteria record history record information record message record reason code record resource record base record commands at job start commands at job end

LCRLHRLIRLMRLRCLRRLBRLCSLCE




===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------









PF1=HELP

� �

The preceding panel tells you that option 5 deletes an existing record. Notice,however, that Unicenter CA-Scheduler expects you to enter a job name andschedule name when you select option 5. Therefore, when you type 5 in thecommand area, follow it with a comma, the name of the job you want todelete, another 3 commas, and the name of the schedule that job belongs to.

Next, delete the job called DEFAULTS. To do that, enter5,DEFAULTS,,,BACKUP in the command area to delete that record.

Scheduler then deletes the record for job number 01 at station 40. To delete arecord at another station or for another job number, specify all the optionalparameters with option 5. For example, entering

5,DEFAULTS,�2,39,BACKUP

deletes the second job record called DEFAULTS belonging to the BACKUPschedule at station 39 (if it was previously defined).



If you are not authorized to delete this job, Unicenter CA-Scheduler displaysthe message DELETE NOT ALLOWED, but if you do have that authority,Unicenter CA-Scheduler confirms it deleted all records (except the historyrecord) for that job with the message shown following:


===> MASTER - WR

CONNECT : 4�

DELETE JOB NAME=DEFAULTS,JNO=�1,STATION=4�,SCHEDULE=BACKUP

CACU�18I JBR DEFAULTS HAS BEEN DELETED

PF1=HELP

� �


3.12 Analyzing Jobs

3.12 Analyzing Jobs

You should analyze all jobs that you add to the database before you put theminto production. This allows you to fix discrepancies and omissions beforeyou run the jobs. There are two ways to analyze a job online:

■ Analyze a specific job■ List all jobs and pick one to analyze

The first method is quicker, but the second is useful if you do not know theexact spelling of the job to be analyzed. The analysis will produce messagesabout the following:

■ If the job records specify an undefined schedule, calendar, datetable,userid, or predecessor

■ If a predecessor or successor deadlock exists

To analyze a specific job, start at the Job Maintenance panel. Suppose there isa job (NEWJOB) you recently defined, but you defined a schedule name ofNEWSCHD7 that isn't defined to Scheduler.


===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------









PF1=HELP

� �

To analyze the schedule, enter 6, followed by the job name.



3.12 Analyzing Jobs


===> MASTER - WR

CONNECT : 4�

ANALYZE JOB LIST=ERR,NAME=NEWJOB

CACU�17E SCHEDULE NEWSCHD7 NOT FOUND

CACU�18I JOB NEWJOB HAS BEEN ANALYZED

PF1=HELP

� �

Notice that the analysis is performed with the LIST=ERR option so that onlyerror messages are displayed. If you need a full analysis report, use the JCLdescribed in the chapter "Reports" in the Unicenter CA-Scheduler Reference GuidePart 2.

Before examining the second method of analyzing jobs, return to the JobMaintenance panel by pressing CLEAR.

To analyze a job that has a name you do not know, start at the JobMaintenance panel. You need to display a full directory of jobs so that youcan find the one you want.


===> MASTER - WR

CONNECT : 4�

FUNCTION ENTER

-------- ------









PF1=HELP

� �


3.12 Analyzing Jobs

To display a full directory of jobs, press Enter.


� � SCHD-JD ��JOB DIRECTORY�� Scheduler

===> MASTER - WR

CONNECT : 4�

B C I M R R N C C


IH7D�2 4� �1 BACKUP CMS IH7D�2 Y Y Y Y Y Y

NEWJOB 4� �1 NEWSCHD7 CMS NEWJOB Y

NEWJOB2 4� �1 NEWSCHD8 CMS NEWJOB2 Y Y


PF1=HELP

� �

Assume that the job that you want to analyze is called NEWJOB2. Yourecently defined it, but on the criteria record you named it as a predecessor ofitself. Thus, a predecessor deadlock exists. Tab to NEWJOB2 and enter ANA.



===> MASTER - WR

CONNECT : 4�

ANALYZE JOB LIST=ERR,NAME=NEWJOB2,SCHEDULE=NEWSCHD8

CACU�4�E NEWJOB2 �1 4� NEWSCHD8 DEADLOCK WITH PRED NEWJOB2 �1 4� NEWSCHD8

CACU�18I JOB NEWJOB2 HAS BEEN ANALYZED

PF1=HELP

� �

Before beginning the next topic, return to the Main Menu by pressing Clearrepeatedly.


3.13 Automatic Console Replies for Jobs


Console messages issued by Unicenter CA-Scheduler VSE controlled jobs orschedules typically require a response that either issues a command, suppliesdata or requests some kind of operator intervention. These responses can beautomated by using Scheduler's Automatic Console Reply feature. This featureis unavailable with the CMS online component.

You begin by tabbing to the Auto-Reply Maintenance line and pressingENTER.

� � SCHD-MM �� MAIN MENU �� Scheduler

===> E - WR

CONNECT : 4�





==> POWER INTERFACE


==> JOB MAINTENANCE







==> DOCUMENTATION MAINTENCE




PF1=HELP

� �

This displays the following Automatic Reply Maintenance panel. It may alsobe reached by selecting 7,AUTO-REPLY PROCESSING on the Job MaintenanceMenu panel SCHD-JM, or the Schedule Maintenance Menu panel SCHD-SM.Overwriting the auto-reply messages field on the JBR or SBR with the letter Yor C will also bring you to the Automatic Reply Maintenance panel.



� � SCHD-AR �AUTOMATIC REPLY MAINTENANCE� Scheduler

====> MASTER - WR

CONNECT : 4�

Schedule : ________ Job : ________ Jno : __ Msgid : ________

Scantxt :

Reply :




� �

3.13.1.1 To ADD a New Reply

To enter a new reply associated with a job, type the job name in the job namefield and press Enter. If the job has already been defined to the database, thepanel will show the existing schedule name, job numbers, message IDs, scantext for each message (if any), and the reply texts. If the job has not beendefined, proceed as follows.

Enter the schedule name in the schedule name field.

Enter the job number in the jno field.

Enter the message ID in the msgid field. The message ID is the first one toeight characters of the message associated with the reply.

Each of the four key fields, Schedule Name, Job Name, JNO (job number) andMSGID (message id), can also have a generic value. For example:

AA� � - any char string may follow

A??B ? - any char in this position

Scan text is a string of one to sixteen characters that occur in the message. Thestring will be checked to verify the message id.

You may enter a reply to the message of up to 72 characters.




====> MASTER - WR

CONNECT : 4�

Schedule : Sched1__ Job : JOBD____ Jno : 14 Msgid : cacm�27_

Scantxt : autoscan cannot

Reply : wait for monitor to terminate, then reactivate




� �

To add the record to the database, either enter ADD on the command line orpress the function key.

The message CACO360I AUTO-REPLY RECORD ADDED will be displayed.


====> MASTER - WR

CACO36�I AUTO-REPLY RECORD ADDED CONNECT : 4�

Schedule : SCHED1 Job : JOBD___ Jno : 14 Msgid : CACM�27


Reply : WAIT FOR MONITOR TO TERMINATE, THEN REACTIVATE




� �



3.13.1.2 ALTer or REPlace an Auto-Reply Record

Begin with the Auto-Reply Maintenance panel SCHD-AR, described preceding.

To alter or replace an existing reply, enter the job name or job number andpress Enter to search for the message to be changed. The ENTER-BROWSEfunction displays the replies that currently exist in the database for thatjobname.

Type A or R on the line of the record to be changed, and press Enter.


====> MASTER - WR

CONNECT : 4�


Scantxt :

Reply :







a SCHED1 JOBD 14 CACM�27 AUTOSCAN CAN WAIT FOR MON


� �

The messages CACO372I UPDATE FIELDS AND PRESS ENTER and ALTERwill be displayed in the command area.




====> ALTER MASTER - WR

CACO372I UPDATE FIELDS AND PRESS ENTER CONNECT : 4�

Schedule : SCHED1 Job : JOBD____ Jno : 14 Msgid : CACM�27_











� �

Type the changes in the appropriate fields and press Enter.

The database is updated and the message CACO361I AUTO-REPLY RECORDUPDATED displayed.


====> MASTER - WR

CACO361I AUTO-REPLY RECORD UPDATED CONNECT : 4�












� �



3.13.1.3 To DELete an Auto-Reply Record

To delete an existing reply, enter the job name on panel SCHD-AR and pressEnter to search for the message to be deleted.

Type L on the line of the record to be deleted and press Enter.


====> MASTER - WR

CONNECT : 4�


Scantxt :

Reply :







l SCHED1 JOBD 14 CACM�27 AUTOSCAN CAN WAIT FOR MON


� �

The message CACO369I PRESS ==> PF5 <== TO CONFIRM DELETE andDELETE will be displayed in the command area.


====> DELETE MASTER - WR

CACO369I PRESS ==> PF5 <== TO CONFIRM DELETE CONNECT : 4�










� SCHED1 JOBD � CACM�27 AUTOSCAN CAN WAIT FOR MON


� �



The database is updated and the message CACO362I AUTO-REPLY RECORDDELETED is displayed.


====> MASTER - WR

CACO362I AUTO-REPLY RECORD DELETED CONNECT : 4�

Schedule : SCHED1 Job : JOBD____ Jno : �_ Msgid : CACM�27









_ SCHED1 JOBD � CACM�27 AUTOSCAN CAN WAIT FOR MON


� �


3.14 Summary of Job Maintenance


Unicenter CA-Scheduler only allows authorized users to create, update ordelete job records. General users can work with jobs belonging to publicschedules or schedules that specifically grant them access in the USERS field.

The chart following sums up the steps involved in maintaining job recordsfrom the Job Maintenance menu. Since there are several ways to do things,only the fastest ways are shown:

The Job Directory panel supports the following commands:

To Enter This InCommand Area

Then

Define a job 4 Enter job data

Copy a job 1,job being copied Tab to a job; enter C or Cxx,where xx is the record type.Enter new data

Alter a specific job

an unknown job

3,job name

(Press Enter)

Enter changes in JBR; enter Ain a RECS= field

Tab to a job; enter A or Axx,where xx is the record type

Delete a specific job a specific record

5,jobname,,,schedname(Press Enter)

Tab to the job; enter Lxx,where xx is the record type

Display one job record

some jobs

all jobs

2,job name

1,*x where x is thefirst character insome job names

(Press Enter)

Tab to a job; enter D

Press Enter to scroll panels

Analyze a job 6,job name

Display, alter ordefine auto-replymessages

7,job name




Display a record base command at job start command at job end criteria information message node reason code resource

DDCSDCEDCRDIRDMRDNRDRCDRR

Alter a record base command at job start command at job end criteria information message node reason code resource

AACSACEACRAIRAMRANRARCARR

Define a new record using thisrecord as the model base command at job start command at job end criteria information message node reason code resource

CCCSCCECCRCIRCMRCNRCRCCRR

Delete a record all records for a job except the history record) base command at job start command at job end criteria history record information message node reason code resource

L

LBR (see following)LCSLCELCRLHRLIRLMRLNRLRCLRR



Notice that C does more than merely create new job records: it allows youcopy them. This method of building new records from existing ones is moreefficient than using the PROTOTYPE fields. The copy feature is illustrated inthe topic Copying Jobs.

Notice that deleting the base record will remove the job from the Directorypanel. Other job records associated with this record, however, will not bedeleted along with it. When you delete a base record, it is your responsibilityto either replace the base record or delete its associated records using the batchutility.


Analyze a job for missing orillogical records

ANA


Chapter 4. Online Monitoring

Once the Unicenter CA-Scheduler database is defined and UnicenterCA-Scheduler is automatically selecting schedules and jobs through theautoscan process, you then use the Online Monitoring component to controlthe daily workload and monitor its progress by performing the followingfunctions:

■ Controlling schedules and jobs using control commands■ Displaying status on Unicenter CA-Scheduler-controlled schedules and

jobs, listing jobs that have been submitted, jobs that are late, abended jobs,and so forth.

■ Displaying other information such asDate and autoscan informationData set mask names defined in the CAIJ$DSN macros

Network information

■ Posting and unposting predecessors■ Sending messages to other users and displaying messages sent by other

users■ Displaying values of global parameters and resetting values■ Setting predecessor conditions manually

This chapter focuses on how you use Unicenter CA-Scheduler to monitor thestatus of the daily work flow and how to use control commands to controldaily production.

Chapter 4. Online Monitoring 4-1

4.1 Online Monitoring Panel


You start monitoring and controlling your production environment at theOnline Monitoring panel. To display that panel, start at UnicenterCA-Scheduler's main menu and tab to ONLINE MONITORING:


===> MASTER - WR

CONNECT : 4�





==> POWER INTERFACE


==> JOB MAINTENANCE











PF1=HELP

� �

Online Monitoring is one of the functions listed on Unicenter CA-Scheduler'smain menu. To make that selection, tab to the second selection and pressEnter.

� � SCHD-OM �� ONLINE MONITORING �� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

Enter no. of selected command, followed by comma and additional parameters.

MISCELLANEOUS COMMANDS

1 ONLINE STATUS 4 POST DEPENDENCY 7 DISPLAY

2 QUERY MESSAGES 5 UNPOST DEPENDENCY

3 SEND MESSAGE 6 SET/DISP GLOBALS

SCHEDULE COMMANDS JOB COMMANDS

2� RUN 3� CANCEL/POST 4� RUN 5� CANCEL/POST

21 REQUEST 31 TALTER 41 REQUEST 51 TALTER

22 RELEASE 32 SREQ 42 RELEASE 52 SREQ

23 HOLD 33 FORCE 43 HOLD 53 FORCE

24 CANCEL 34 PURGE 44 CANCEL 54 PURGE

45 SUBMIT 55 START

46 ADD 56 COMPLETE

47 RESTAGE 57 RERUN

PF1=HELP

� �



The following table describes what you can do with the various fields on thispanel.

For example, you can send messages, post predecessors, and set globalparameters without leaving the Online Monitoring panel. All of these facilitiesare described in detail later in this chapter.

To enter a command, you must enter the number that appears next to it on thecommand line (===>). You may enter optional keywords by separating themfrom the number and from each other with commas. This method of issuingcommands differs from what you have seen elsewhere in UnicenterCA-Scheduler and is discussed in detail (including examples) in the topics thatfollow.

By Selecting You Can

ONLINE STATUS Display schedule status at the stationsyou are authorized to connect to.

QUERY MESSAGES Display messages that have been sent toyour userid.

SEND MESSAGE Cause a message to be sent to otheruserids.

POST DEPENDENCY Satisfy a predecessor condition so that awaiting job or schedule can beprocessed.

UNPOST DEPENDENCY Inhibit a predecessor condition so that awaiting job or schedule cannot beprocessed.

SET/DISP GLOBALS Display global parameters or causepredecessor conditions to be satisfied bysupplying a value for GBLxnn.

DISPLAY Display a variety of informationincluding:

■ Date and autoscan information■ Data set mask names (CAIJ$DSN

macros) ■ Network information

JOB COMMANDS Control jobs by issuing controlcommands.

SCHEDULE COMMANDS Control schedules by issuing controlcommands.



This chapter does not cover control commands in detail. For more information,refer to the chapter "Controlling Schedules and Jobs" in the UnicenterCA-Scheduler Reference Guide Part 1.


4.2 Displaying Status


You will probably be performing this function many times. Throughout theday, you will be reviewing the current status of schedules and jobs. The panelthat controls this process is entered from the Online Monitoring panel but canalso be entered directly from the Main Menu's first selection (ONLINESCHEDULE STATUS). To display the Online Status panel from the OnlineMonitoring panel, enter 1 on the command line.

The following depicts the Online Status panel that is displayed.

� � SCHD-OS �� ONLINE STATUS �� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

OPT PARM=> S=SNAME,J=JNAME,ST=NN,OR=P,D=S|T|H,SYS=SYSID,RO=NODE,FM=NODE

ACTIVE =>

INACTIVE =>

SUBMITTED =>

STARTED =>

COMPLETED =>

LATE =>

WAIT-ANY =>

WAIT, AND REASON =>

WAIT-PREDECESSOR =>

WAIT-RESOURCE =>

WAIT-START TIME =>

HELD =>

HELD, AND WHEN =>

ABENDED =>

CANCELLED =>

FAILED =>

INTERRUPTED =>

RUN IF REQUESTED =>

ALL => PF1-HELP

� �

As soon as the database is scanned and jobs and schedules are selectedthrough the autoscan process, Unicenter CA-Scheduler starts schedules andsubmits jobs that are available for processing. This starts a new daily processthat you can monitor. The day's workload consists of all the new jobs selectedthat day as well as any backlogged work from prior days. Each schedule andjob is placed into a Unicenter CA-Scheduler queue.

4.2.1 Displaying a Specific QueueSchedules and jobs are available for processing when:

■ Their early start time is reached, and■ All predecessor conditions are satisfied, and■ Resources defined on a job resource record are available, and■ They are in the active queue



Schedules and jobs that are available as soon as autoscan is complete areusually those without defined start times, predecessors, or resources. Allschedules and jobs go into one of these primary queues:

■ The active queue contains schedules and jobs waiting until they areavailable for processing. They remain in the active queue during and afterprocessing.

■ The inactive queue contains schedules and jobs that were selected becauseof REQUESTED or that are successors to jobs or schedules that wereselected for the reason REQUESTED, as well as jobs that have been held orcanceled. See the topic On-Request Schedules and Jobs in the chapter"Techniques". REQUESTED schedules and jobs can be activated by theREQUEST or SREQ commands.

All Unicenter CA-Scheduler's queues are listed on the Online Status panel. Todisplay all the schedules and jobs in a queue, place your cursor next to thequeue you want to display and press Enter.

Unicenter CA-Scheduler gives you several methods of tailoring status displaysto your specific needs. You can display:

■ Different kinds of data (full status descriptions, actual versus expected endtimes, past histories of job execution)

■ For certain groups of schedules or jobs

■ Sequenced alphabetically or in order of execution priority

We recommend that you try limiting your displays to:

■ Specific schedules or jobs ■ A station ■ A SYSID■ Schedules or jobs beginning or ending with a certain character string■ A specific node in your network of data centers

or any combination of these. Limiting the display by specifying schedule nameor job name decreases response time in all cases except where a mask characteris used in the first character position.

The next topic explains how to tailor status displays to your specific needs.Before proceeding to that topic, focus first on understanding the different typesof queues you can monitor. The diagram following shows how UnicenterCA-Scheduler classifies jobs into queues.



Jobs in narrowly defined queues also belong to queues covering broadercategories. For example, all jobs in the INTERRUPTED queue are also in theSTARTED queue. The LATE queue isn't depicted on the diagram precedingbecause its members can come from all but one of the other queues; everycategory of job except RUN IF REQUESTED can also be late.



The table following briefly explains each queue type.

This Queue Displays Schedules And Jobs That Are

ABENDED CPU jobs that have abended and their abendcode.

ACTIVE Waiting for processing or were alreadyprocessed.

ALL All jobs (both active and inactive queues).

CANCELLED Cancelled by the CANCEL control command.

COMPLETED Completed normally.

FAILED CPU jobs that failed and their reason forfailure.

HELD Held and the reason why.

HELD, AND WHEN Held and the status as it existed before it washeld.

INACTIVE Waiting to possibly be activated by theREQUEST or SREQ command at which pointthey will be moved to the active queue. Alsoincludes held and canceled jobs.

INTERRUPTED Interrupted by the INTERRUPT=YES field.

LATE Late; they missed their deadline date andtime.

RECEIVED Received at remote nodes.

RUN IF REQUESTED Available to be requested.

STARTED Started. CPU jobs are those currentlyexecuting; non-CPU jobs have been startedwith the START command or startedautomatically because AUTO START=YES.

SUBMIT FAILED Not started because submission failed. Areason code is given.

SUBMIT IN PROGRESS Currently being submitted.



This Queue Displays Schedules And Jobs That Are

SUBMITTED ■ All CPU jobs that have been submitted toPOWER, but have not started yet as wellas

■ All non-CPU jobs waiting for the STARTcommand.

■ CPU jobs currently being submitted■ Jobs received at remote nodes■ UNKNOWN status jobs (were submitted

or were executing when the systemcrashed)

WAIT, AND REASON Waiting for any reason (the reason isdisplayed).

WAIT-ANY Waiting for any reason such as predecessorsto be satisfied, an early start time to bereached, or for resources to be available.

WAIT-PREDECESSOR Waiting for predecessors to be satisfied.

WAIT-RESOURCE Waiting for defined resources to be madeavailable.

WAIT-START TIME Waiting for its associated early start time tobe met.

4.2.2 Displaying Status for Specific Schedules and JobsStatus displays automatically show the status of all schedules you areauthorized to monitor at all the stations you are authorized to connect to. Youcan limit status displays to selected schedules, jobs, stations, and CPUs. Theoptional parameters that limit the scope of status displays are shownfollowing. Use any combination of these parameters to display just those jobsyou are interested in. Type these parameters next to the name of the queueyou want to display and use commas to separate the parameters you haveselected.

To Restrict The Display To Specify Any Combination OfThese

A specific schedule or

all schedules whose names: -start with the same characters or -end with the same characters or -contain the same characters

S=sname

Substitute * or ?s for > following:S=characters-S=-charactersS=-characters-



For example, you could display just those jobs in the ACCTG schedule that arerunning late at station 39. To do that, you would tab down to LATE, enter

S=ACCTG,ST=39

and then press Enter. For more information about * and ?, see the term maskcharacter in the Glossary.

Note: Limiting the display by specifying schedule name or job namedecreases response time in all cases except where a mask character isused in the first character position.

To Restrict The Display To Specify Any Combination OfThese

A specific job or

all jobs whose names:

-start with the same characters or -end with the same characters or -contain the same characters

J=jname

Substitue * or ?s for > following:J=characters-J=-charactersJ=-characters-

One station you can connect to ST=id

One CPU SYS=sysid

Jobs received from another node FM=nodeid

Status at another node RO=nodeid

4.2.3 Displaying Status in SequenceUnicenter CA-Scheduler shows queues in alphabetical order, but you canrequest them in order of priority. Unicenter CA-Scheduler prioritizes work byconsidering several factors, not just the value of the JOB PRIORITY field.Unicenter CA-Scheduler allows you to determine the priority of schedules andjobs within the workload using these factors:

■ Predecessors ■ Start times ■ Deadlines ■ Priority fields

Jobs with the same priority (the same values for all four factors) are sortedalphabetically.

If you want the queue to appear in priority order, type



OR=P next to the queue you want to display. Remember that the priority of aschedule or job is not based solely on the priority defined for it, but on otherfactors.

Some special considerations apply to a multi-CPU environment: the

OR=P

parameter only displays jobs from the CPU at which you are logged on (notfrom other CPUs). When running multi-CPUs, if you issue the STATUScommand with

OR=P and

SYS=sysid other than the SYSID of the CPU you are logged on to, the SYSIDwill be ignored.

Notice that this display is NOT a completely accurate indication of thesequence the jobs will run. Many events may delay or accelerate a given job'sstart time (DSN close, SET GBLxnn, or FORCE, for example). Therefore, theSIMEXEC report with the SIMULATE command is the best way to show a runsequence of jobs.

The next topic contains an example using

OR=P.

4.2.4 Different Types of DisplaysUnicenter CA-Scheduler gives you four different formats for displayingqueues. These formats all display jobs grouped by schedule. You requestdifferent formats by specifying different values for the D parameter. Define theappropriate value next to the queue you want displayed. The chart followingshows which D= values select each queue format. Choose just one of theseformats when displaying a queue.

To Display Specify

Jobs within schedules and their status condition Nothing

Actual start- and end-times versus expected D=T

A history of the execution of jobs within schedules that arecurrently being tracked

D=H

Statistics summarizing the schedules currently being tracked D=S



If you combine options by separating them with a comma, you can list thejobs:

■ That are late■ At station 39■ Showing actual versus expected start- and end-times■ In order of job priority

by tabbing down to LATE, typing

ST=39,D=T,OR=P and pressing ENTER. Looking at these different displayformats will clarify the differences in format.

Notice that using OR=P significantly improves response time for all queuesexcept ACTIVE, ALL, ABENDED, and FAILED.

4.2.4.1 Default Status Display

By not specifying a

D= parameter, you get the default status display. The panel followingillustrates output produced by tabbing to the ACTIVE field on the OnlineStatus panel and pressing Enter:

� �SCHD-CP SCHEDULER COMMAND PROCESSOR CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

��

SCHEDULE JOB NAME JNO ST RC JCNT SYSID S T A T U S

DAILY 84 ��1� 1 ENDED

JDAY1OF2 �1 4� �1 1 ENDED





JWEK1OF2 �1 4� �1 1 ENDED




JWEK4OF5 �1 4� 88 1 OS PURGED

DSNPRED 84 ��2 1 ENDED

DSNPRED1 �1 4� 84 1 SUBMITD

DSNPRED2 �1 4� 84 1 SUBMITD


� �

This display groups jobs by schedule. Both schedules and jobs are listedalphabetically. The status conditions and their meanings are described later inthis topic.

Although this is called a display panel, you can key in control commands tocontrol schedules and jobs by entering an abbreviation of the command to theleft of a schedule or job. The topics on Controlling Schedules and ControllingJobs fully explain this time-saving feature.



The RC field is unique to this display format; no other D= value displays it.RC tells you why the schedule or job appears in today's workload. Some of thenumbers listed there relate back to reasons defined on criteria records. RCcodes have the following meanings:

If RC Is This Number

01 - 79 Corresponds to the position of the reason on the criteriastatement that was defined for this job or schedule.

80 Indicates that it was selected because today's date correspondsto a workday on the calendar that was defined for this job orschedule.

84 Indicates that it is selected by default every day because noselection criteria were defined.

88 Indicates that it was added to today's schedule by the RUNcommand.

92 Identifies a schedule that is being run because a job abended.(This schedule was specified in a job's ABEND option as analternate schedule in case of abend.)

95 Indicates that this job was added to today's schedule using theonline ADD command.

96 Indicates that this job was a backout job that was submittedfor an abended job that specified ABEND=BACKOUT.

4.2.4.2 Sample Time Status Display

By specifying

D=T, you get the Time Status Display. The panel following illustrates outputthat could result from typing just

D=T in the ACTIVE field on the Online Status panel.




===> MASTER - WR

CONNECT : 4�

��

SCHEDULE JOB NAME JNO ST EARLY TIME MUST TIME DEADLINE

AVAIL TIME START TIME END TIME

JWEK3OF3 �1 4� �9/�7 ��.�� 9/�7 ��.�� 9/�7 ��.��

�9/�7 �9.33 ��/�� .�� /�� .��

JWEK3OF4 �1 4� �9/�7 ��.�� 9/�7 ��.�� 9/�7 ��.��

�9/�7 �9.33 ��/�� .�� /�� .��

JWEK3OF6 �1 4� �9/�7 ��.�� 9/�7 ��.�� 9/�7 ��.��

�9/�7 �9.33 ��/�� .�� /�� .��

JWEK4OF5 �1 4� �9/�7 ��.�� 9/�7 ��.�� 9/�7 ��.��

�9/�7 �9.33 ��/�� .�� /�� .��

DSNPRED �9/�7 ��.�� 9/�7 ��.�� 9/�7 ��.��

��/�� .�� /�� .�� /�� .��

DSNPRED1 �1 4� �9/�7 ��.�� 9/�7 ��.�� 9/�7 ��.��

��/�� .�� /�� .�� /�� .��

DSNPRED2 �1 4� �9/�7 ��.�� 9/�7 ��.�� 9/�7 ��.��


� �

Notice that each schedule and job has two lines of data associated with it. Thefirst line of data (the one that contains the schedule or job name) includes thedate and time of its early start time (EARLY TIME), the time it must start by(MUST TIME), and the latest time that it is due out (DEADLINE).

The second line of data contains the date and time when it actually becameavailable (AVAIL TIME), when it actually started (START TIME), and actuallyended (END TIME).

4.2.4.3 Sample History Status Display

By specifying

D=H, you get the History Status Display. The panel following shows outputthat could result from typing just

D=H in the COMPLETED field on the Online Status panel. Average time isshown in hh.mm format.




===> MASTER - WR

CONNECT : 4�

��

SCHEDULE JOB SYS AVG START END COMP

NAME NAME JNO ST ID TIME TIME TIME S T A T U S CODE

ABCXY 1 �.19 16.�5 17.3�

ABC �1 39 1 �. 5 16.�5 16.17 ENDED

�1 39 1 �.�5 16.44 16.45 ENDED

�1 39 1 �.�5 16.55 16.58 ENDED

ABC �1 4� 1 �.�7 16.17 16.2� ABENDED ��14

�1 4� 1 �.�7 16.46 16.5� ABENDED ��18

�1 4� 1 �.�7 17.�� 17.2� ENDED

XYZ �1 4� 1 �.�7 16.21 16.3� FAILED ��8

�1 4� 1 �.�7 16.5� 16.54 FAILED ��16

�1 4� 1 �.�7 17.21 17.3� ENDED


� �

This display also lists jobs within schedules.

The primary difference between this and the default display is that the Historydisplay depicted preceding contains the average run time and the completioncode of the job. The average time of a job is based on its history and you canuse it to immediately determine if something is out of line. The status codeappears, but does not contain the same amount of information as the defaultstatus display.

4.2.4.4 Sample Schedule Summary Status Display

By specifying

D=S, you get the Schedule Summary status display. This panel shows outputthat could result from typing just

D=S in the ACTIVE field on the Online Status panel. Average time is shownin DD/hh.mm format.


===> MASTER - WR

CONNECT : 4�

��

SCHEDULE S T A R T E N D DEADLINE REMAINING AVERAGE RER

NAME DATE TIME DATE TIME DATE TIME TIME RUN TIME UN

CASCHD1 11/�6 11.�2 11/�6 19.22 11/�6 2�.�� 8.12

CASHCD2 11/�6 14.48 11/�6 15.35 11/�6 16.3� ��.44

CASCHD3 11/�6 19.15 11/�6 ��.�� 11/�5 23.15 �3.14 �3.32 Y


� �

This display just summarizes schedules. Along with the date and time atwhich schedules started and finished, you can also see when they were due tofinish.



If the schedule is still waiting to start, the REMAINING TIME field shows theaverage run time of the schedule in hours and minutes followed by a '+' toindicate the amount of time the schedule will probably take to complete. If theschedule has already started, however, this field is calculated by subtractingthe elapsed time from the average time. A '-' indicates that the schedule hastaken longer than average. The AVERAGE RUN TIME shows the schedule'saverage execution time based on Unicenter CA-Scheduler's history data.

Another very important column in this panel is RERUN. It indicates that thisschedule has been carried over as backlog from a previous day and will runagain when this schedule ends.

The panel preceding shows CASCHD3 was supposed to run yesterday (11/5).That schedule started 18 minutes ago (3.32 - 3.14) and still has over three hoursto run (3.14). The RERUN field indicates that when CASCHD3's jobs fromyesterday are done, CASCHD3 will run again with today's jobs.

4.2.5 ExamplesThese examples combine various parameters to illustrate some of the optionsavailable with the Online Status panel.

To Display Move The Cursor To AndType

PAYJ jobs in allschedules that arewaiting forpredecessors

WAIT-PREDECESSOR J=PAYJ*

Start and end times ofall jobs run on thecomputer

COMPLETED D=T,ST=40

Late jobs in order ofpriority

LATE OR=P

All jobs in thePAYROLL schedulethat run on thecomputer

ALL S=PAYROLL,ST=40

All jobs scheduled atthe data entry stationthat are waiting to bestarted in order ofpriority

SUBMITTED ST=20,OR=P



4.2.6 The Meaning of StatusThis list of status conditions explains the various stages that jobs and schedulespass through. Reviewing this information will give you a good understandingof what is going on within Unicenter CA-Scheduler.

ABENDED The job can be rerun using the RERUN or SUBMITcommand.

AUTO RECVRY HELDThe job or schedule was put on hold as part of automaticrecovery following a system crash. It must be releasedusing the RELEASE command. mix INTERRUPT field

AUTO STRTED Is a non-CPU job that was defined with the AUTOSTART=YES option which means that the job wasautomatically started when its early start time was reached,all of its predecessor conditions were satisfied, and itsdefined resources were met. Therefore, you can processthe job without posting START. After processing, use theCOMPLETE command to end the job.

userid CANCLD This job or schedule was canceled by a UnicenterCA-Scheduler CANCEL command issued by a user whoseauthority level allows them to control this schedule or job.It can be purged from the status display via the PURGEcommand or started again using the RUN, SUBMIT, orRERUN command.

ENDED The job or schedule has ended with this completion codeand can be purged from the status display using thePURGE command or started again via the RUN, SUBMIT,or RERUN command. (Formerly COMPLETED status)

FAILED The job can be rerun using the RERUN or SUBMITcommand.

userid HELD The job or schedule was held by a HOLD command issuedby a user whose authority level allows them to control thisschedule or job. It will not be considered for processinguntil it is released using the RELEASE command.

INTRPTD This identifies completed jobs defined withINTERRUPT=YES. The job must be manually ended usingthe COMPLETE command or rerun using the RERUN orSUBMIT command.

NO BACKLOG CNCLThe job was canceled at the end of the day because ithadn't been submitted or started yet and it was defined asBACKLOG=NO. You will only see this if at least oneother job in the same schedule is still running or becamebacklogged at autoscan. If at least one job is still running



or backlogged, the rest of the schedule cannot be purged.Therefore, the rest of the jobs that have not started yet aregiven this status to indicate that they are not really beingcarried over to the next day in backlog; they will bepurged when the schedule ends.

NOT REQUESTEDThis job or schedule has been selected and put in aninactive queue in case it is REQUESTED. It will only beprocessed if it is activated by the online REQUEST orSREQ command.

SHUTDOWN HELDThe SHUTDOWN DELAY command has been issued andshutdown will start as soon as the jobs currently runningat the CPU come to an end.

STARTED A schedule has been started, a CPU job is executing, or anon-CPU job has been started using the START command.For a CPU job, the status display shows the POWER jobnumber and the partition it is running in.

SUBMIT IN PROGRESSUnicenter CA-Scheduler is retrieving a job's JCL from thelibrary where it is stored and submitting it to the operatingsystem. It cannot be held at this point.



SUBMIT FAILED Unicenter CA-Scheduler tried to submit a job and failed.You can resubmit the job using the SUBMIT, RERUN, orFORCE command when the cause of failure is corrected.A four-character code tells you where the job wassubmitted from or how the error was detected and whythe submission failed. The first two characters identify thesource of the error:

Code Source Of Error

04 VSE procedure library

08 ICCF library

0C Unicenter CA-Driver library

10 Unicenter CA-Driver expansion interface

14 SLI library

18 Allfusion CA-Vollie library

1C AllFusion CA-Panvalet library

20 AllFusion CA-Librarian library

24 CMS member

34 Non-standard library (requires user interface)

38 Dummy TESTLIB used during testing

3C Internal to Unicenter CA-Scheduler

40 During staging retrieval

44 During staging add

48 CMS Service Machine

50 CONDOR library

54 JCLMAN library



The last two characters tell you why the submission failed:

Code Reason For Error

04 The member could not be found

10 A file opening failed

18 Support was not generated for this library

1C A READ failed

20 Of an internal CATMAN I/O error

24 Internal to Unicenter CA-Scheduler

28 Job name is invalid

2C Internal to Unicenter CA-Scheduler


34 Class is invalid


3C PRI is invalid

40 SYSID is invalid

44 Unicenter CA-Scheduler ran out of storage

48 POWER communication error - IDENT

4C POWER communication error - CONNECT

50 POWER communication error - SENDR

54 POWER communication error - REQUEST

58 A logic error has occurred

5C Appendage error/CTLSPOOL error

60 An error from the CMS SUBMIT

64 The member is empty (no records)

68 Allfusion CA-Vollie SUBMIT no librarian support

6C Allfusion CA-Vollie INCLUDE not found

70 AllFusion CA-Librarian/CA-Panvalet INCLUDE not found

74 Too many nested INCLUDEs

78 Error on INCLUDE statement

7C LIB link error (bad VCON)

80 The CMS service machine is not logged on

84 The CMS service machine is not receiving



SUBMITD The JCL for CPU jobs has been submitted to the operatingsystem for execution and has not started. The POWER jobnumber also displays with this status.

UNKNOWN This job was either STARTED or SUBMITD when the systemfailed. It was not in a power reader queue when UnicenterCA-Scheduler started up again; therefore it was assigned thisstatus. It can be resubmitted by issuing a SUBMIT, RERUN, orFORCE command. It can also be canceled or posted ascomplete.

WAITING FOR CPU JOBThis job will not start at a post-CPU station until it has endedat the CPU station.

WAITING FOR PREDThe job or schedule has reached its early start time and iswaiting for one or more of its predecessor conditions to besatisfied. These predecessor conditions include the start or endof another job or schedule, the close of an output data set orthe satisfaction of a global variable. (You can use WAIT,AND REASON on the Online Status panel to find out whatthis job or schedule is waiting for.) This job or schedule willnot run until all of its predecessor conditions are satisfiedunless it is forced using the FORCE command.

WAITING FOR RESOURCESThe job has reached its early start time and all of itspredecessor conditions have been satisfied. Now it is waitingfor a DASD volume to be mounted, for a data set (SEPARATEDSNAME), or for jobs from which it is separated to complete(SEPARATE JOBS). (You can use WAIT, AND REASON onthe Online Status panel to find out what this job is waitingfor.) It will not run until these resources are available unless itis forced using the FORCE command.

Code Reason For Error

88 Of a CMS service machine access error

8C Of a CMS service machine punch error

90 The CLOSE failed

94 PFIX failed

98 SCHEDULER/DRIVER variable resolution error

9C Of a CMS service machine invalid record length

A0 Of a CMS service machine error unpacking file

A4 JCLMAN member not found or syntax error

A8 Userid not defined to CA-TOP SECRET



WAITING FOR START TIMEThe job or schedule is waiting for its early start time. It willnot be available for processing until then unless it is forcedusing the FORCE command.

WAITING NON-CPU STARTThis is a non-CPU job that was defined as AUTO START=NO.It is now available and must be manually started using theonline START command.

WAITING PRE-CPU JOBAll of this job's predecessors have been satisfied except thesame job at a pre-CPU station. It will not be submitted at theCPU station until it has ended at all of the pre-CPU stations inits path.

WAITING USER SUBMITUnicenter CA-Scheduler tried to release the JCL for a job andfailed because the JCL has not yet been manually submitted tothe RDR queue. The job must be manually submitted withDISP=H specified on the JECL job card. UnicenterCA-Scheduler will try at regular intervals to release the job.This status will only be seen for jobs defined with LIBTYPE =RDRQ.


4.3 Handling Messages


The following subtopics explain how to display messages when they are sentto you and how you go about sending messages to other users.

4.3.1 Displaying MessagesWhen MSG PENDING appears on the panel, go to the Online Monitoringpanel and enter 2. This will display system and user messages that have beensent to your userid. After you display the messages, they are deleted.Undisplayed messages are deleted at autoscan if they are more than two hoursold (unless the MSGHOLD generation option on the CAIJGEN macro waschanged).

This is a sample display:


===> MASTER - WR

CONNECT : 4�

��

MESSAGE FOR JOB=JOB5 IN SCHEDULE=ARDAILY AT STATION=4�

CACM�4� JCL IS NOT IN READER QUEUE

PF1=HELP

� �

Messages that have been sent to the Unicenter CA-Scheduler mailbox can beviewed through the Reporting Facility panel.

Now that you know how to receive messages, you will learn how you cansend them to others.

4.3.2 Sending MessagesTo send messages to another userid, go to the Online Monitoring panel andenter 3, followed by the following two keywords:

User= Name the user who is to receive the message (1- to 8-characterdefined userid). To send the message to all defined users, specifyUSER=ALL. To send a message to the master console, specifyUSER=OPERATOR.

Text= Give the text of the message (no more than 64 characters). Enclosethe message in single quotes if it contains blanks, commas, or otherdelimiters.

For example, you could send the following valid message:

3,U=JOHN,T='PLEASE MOUNT THAT TAPE NOW'



If your message refers to a specific job, you can use these optional keywords toidentify it:

Job= Name the job (1-8 characters).

Schedule= Name the schedule (1-8 characters).

STation= Name the station (2-character station id).

JNO= Number of the job (1-2 digit number)

If your message refers to a specific schedule, you can use the SCHEDULE=keyword to identify it.

If you want your message routed to another node, use this keyword:

ROute= Give the nodeid.

To assign a number to your message, specify MNO=nnn where nnn is anumber from 800 to 899.

If you need more room to type keywords, end the line with a comma. Whenyou press Enter, a blank panel will be displayed and you can continue thecommand. We recommend that you type a comma after USER=userid andthen press Enter which brings up a continuation panel that leaves you moreroom for specifying TEXT= and any optional keywords.


4.4 Handling Predecessor Conditions


This topic tells you how to post and unpost predecessors.

4.4.1 Posting PredecessorsThe MASTER userid or a userid with Manager authority can post apredecessor condition as satisfied so that a waiting schedule or job can beprocessed. Notice that posting a predecessor satisfies all successors that arewaiting for it. If you only want to release one successor, use ONLYJOB,ONLYST, ONLYJNO or ONLYSCD keywords.

To post a predecessor condition, go to the Online Monitoring panel and enterone of the following:

Type the name of a data set, schedule or job following the predecessorkeywords listed in the chart preceding. If the predecessor is a job, also give theschedule name, job number, and station number. If you cannot fit all of theinformation on the panel, end with a comma. This will give you a continuationpanel. Once you have satisfied a predecessor condition by posting itmanually, Unicenter CA-Scheduler reacts as if the event actually occurred.This affects Unicenter CA-Scheduler totally, so the impact is not limited to justtoday's workload or just this CPU. See the description of the POST commandin the Unicenter CA-Scheduler Reference Guide Part 1.

Enter If The Predecessor You Are Satisfying Is The

4,DSN N=dsname Close of a data set

4,SSCD N=sname4,SJOB N=jname

Start of a -schedule -job

4,SCD N=sname4,JOB N=jname4,VSE N=jname

End of a -schedule -job -nonscheduled DOS job

4.4.2 Unposting PredecessorsThe MASTER userid or a userid with Manager authority can unpost apredecessor condition so that a waiting schedule or job cannot be processed.Notice that unposting a predecessor inhibits all successors that are waiting forit. If you only want to inhibit one successor, use the ONLYJOB, ONLYST,ONLYJNO, or ONLYSCD keywords.



To unpost a predecessor condition, go to the Online Monitoring panel andenter one of the following:

Type the name of a data set, schedule or job following the predecessorkeywords listed in the chart preceding. If the predecessor is a job, also give theschedule name, job number, and station number. If you cannot fit all of theinformation on the panel, end with a comma. This will give you a continuationpanel. Once you have unposted a predecessor condition manually, UnicenterCA-Scheduler reacts as if the event never occurred. This affects UnicenterCA-Scheduler totally, so the impact is not limited to just today's workload orjust this CPU. See the description of the UNPOST command in the UnicenterCA-Scheduler Reference Guide Part 1.

Enter If The Predecessor You Are Unposting Is The

5,DSN N=dsname Close of a data set

5,SSCD N=sname5,SJOB N=jname


-5,SCD N=sname -5,JOB N=jname -5,VSE N=jname



4.5 Handling Global Parameters


This topic describes how you display and set global parameters.

4.5.1 Displaying Global ParametersTo display global parameters, go to the Online Monitoring panel and enter6,D. The following panel is displayed:


===> MASTER - WR

CONNECT : 4�

��

GBLA�1

GBLA�5

GBLA�9

GBLA13

GBLB�1 NO NO YES NO

GBLB�5 NO NO NO NO

GBLB�9 NO NO NO NO

GBLB13 NO NO NO NO

GBLC�1

GBLC�5

GBLC�9

GBLC13


� �

Each row on this panel defines the values of up to four global parameters. Thecolumn on the left identifies the first global parameter defined in each row. Tocheck the value of GBLB03, look in the row that starts with GBLB01. The thirdvalue in that row (YES) corresponds to GBLB03.

Any defined global parameter can be included on a criteria statement as apredecessor condition that must be satisfied before the job or schedule can run.



4.5.2 Setting Global ParametersGlobal parameters can be defined as predecessor conditions that must besatisfied before a schedule or job can be processed. These predecessors arespecified on the Criteria Definition panels or by using the CRITERIA keywordin this format:

GBLxnn=value

These predecessors are satisfied when a global parameter with the same valuesfor x and nn is set to the value defined preceding. To set the value of a globalparameter, go to the Online Monitoring panel and enter:

6,GBLxnn=value

Once GBLxnn is set to a value that satisfies the predecessor conditions ofschedules and jobs, Unicenter CA-Scheduler cannot be "dissatisfied." ResettingGBLxnn will not change the fact that these predecessor conditions havealready been satisfied.

When the nature of your work flow requires manual control, use GBLxnnvariables in the criteria statements of the schedules and jobs that require thattype of manual control.

Where Is

x A if the value is a number from 1 to 99999999B if the value is Y or NC if the value is up to 8 alphanumeric characters

nn A number from 1 to 16 that matches the number on thecriteria statement


4.6 Displaying Date and Autoscan Information

4.6 Displaying Date and Autoscan Information

To display the current system date and time as well as autoscan information,go to the Online Monitoring panel and enter 7,DATE. The following panel isdisplayed:


===> MASTER - WR

CONNECT : 4�

��

CACM�54I LAST AUTOSCAN: JUL=95�99 GREG=�4/�9/95 TIME=11.�9.2� AUTOMATIC

CACM�54I FOR DATE: JUL=95�99 GREG=�4/�9/95 TIME=1�.��.��

CACM�54I NEXT AUTOSCAN: JUL=951�� GREG=�4/1�/95 TIME=1�.��.�� AUTOMATIC

CACM�54I FOR DATE: JUL=951�� GREG=�4/1�/95 TIME=1�.��.��

CACM�54I TODAY'S DATE: JUL=95�99 GREG=�4/�9/95 TIME=2�.16.44


PF1=HELP

� �

It is a good idea to view this display after you temporarily change the nextautoscan time using the AUTOSCAN command with the TIME keyword toensure that the changed time is correct. The display shows whether lastautoscan was MANUAL, TEMPORARY, or AUTOMATIC and whether thenext autoscan will be TEMPORARY or AUTOMATIC.


4.7 Displaying Data Set Mask Names

4.7 Displaying Data Set Mask Names

To display the data set mask table and the node names that will be informedwhen those data sets are closed, go to the Online Monitoring panel and enter7,$DSN. The following panel is displayed:


===> MASTER - WR

CONNECT : 4�

��MILTON ��

��

CACM�54I

CACM�54I

CACM�54I

CACM�54I

CACM�54I

CACM�54I

CACM�54I

CACM�54I

CACM�54I

CACM�54I

CACM�54I

CACM�54I

CACM�54I

CACM�54I

CACM�54I


� �


4.8 Displaying Network Information

4.8 Displaying Network Information

To display the status of each node in a multi-node network, go to the OnlineMonitoring panel and enter 7,NET. The following panel is displayed:


===> MASTER - WR

CONNECT : 4�

��

CACM�54I NAME SYSID TYPE APPLID ZONE S T A T U S STACK-USAGE

CACM�54I USGDNCMD XAD1 JES2 A�1SS�1 � UNCONNECTED � �K

CACM�54I USG2�2ME 3 VSE A�2SS�1 � UNCONNECTED � �K

CACM�54I USG3�2ME 1 VSE A�2SS�1 � UNCONNECTED � �K

CACM�54I USG2�3ME 1 VSE A�3SS�1 1- LOCAL-NODE

CACM�54I USG2�3ME 2 VSE A�3SS�2 1- UNCONNECTED � �K

CACM�54I USG2�4ME XAE1 JES2 A�4SS�1 � UNCONNECTED � �K

CACM�54I USG2�4ME XAE2 JES2 A�4SS�2 � UNCONNECTED � �K

CACM�54I USG212ME XAE3 JES2 A12SS�1 � UNCONNECTED � �K

CACM�54I USG312ME XAE3 JES3 A12SS�1 � ERROR


PF1=HELP

� �

You should keep an eye on the STACK-USAGE value for a connected node.This is the number of requests (and the amount of private storage thoserequests occupy) that the local node is attempting to send to this node. If thosenumbers move up and do not move down, it could indicate a slow down inVTAM communications between the local node and this node and possibly alost VTAM connection. Unicenter CA-Scheduler will send a warning messageto the operator console when the amount of storage used to hold the stackedrequests reaches the threshold defined in the VTAMLIM option of theCAIJNET macro. In this case you should use the Unicenter CA-Scheduler orVTAM VARY INACTIVE command to disconnect communication with thisnode. Unicenter CA-Scheduler will then save any stacked requests for thisnode on the tracking file. When the VTAM problem is resolved, use theUnicenter CA-Scheduler VARY ACTIVE command to reestablishcommunication with this node. Unicenter CA-Scheduler will then resend anyrequests that were saved for this node.


4.9 Controlling Schedules


You can control schedules for which you are authorized. To control schedulesissue one of these online commands:

CANCEL FORCE HOLD PURGE RELEASE

REQUEST RUN SREQ TALTER CP

To enter a command, you must enter the number that appears next to it on thecommand line (===>). You may enter keywords by separating them from thenumber and from each other with commas. The chart following explains whatthese commands do.

When issuing commands from the Online Monitoring panel, you can use anyof the keywords listed under the command name in the chapter "ControllingSchedules and Jobs" in the Uniicenter CA-Scheduler Reference Guide Part 1. Toenter a keyword, enter the number of the command followed by a comma and

To Enter Which Stands For

Add a schedule to the active queue that has:

-not been selected today

-been INACTIVE along with all itssuccessors

-been INACTIVE and leave in the inactivequeue any successors that are alsoREQUESTED or that have other INACTIVEpredecessors that were also REQUESTED

20

21

32

RUN

REQUEST

SREQ

Hold a schedule that is waiting or started 23 HOLD

Release the hold on a schedule 22 RELEASE

Cancel a schedule at any point beforecompletion

24 CANCEL

Cancel a schedule and post its successors asif the schedule completed successfully.

30 CANCEL/POST

Rerun canceled or completed schedules. 20 RUN

Delete canceled or completed schedules 34 PURGE

Temporarily change values defined for anactive schedule for this execution only

31 TALTER

Force a schedule to start, even though it iswaiting for its early start time to be reachedor for predecessor conditions to be satisfied

33 FORCE



then the keyword. If you enter multiple keywords, separate them withcommas. For example, you could enter the following valid TALTER command:

31,NAME=TESTSCHD,DEADLINE=15��

If you run out of room to enter keywords, follow a keyword=valuecombination with a comma and press Enter . Another panel will be displayedthat allows you to continue the command.

You can issue certain control commands that pertain to schedules directly fromany of the status displays (SCHEDULER Command Processor panel). All youhave to do is position your cursor to the left of the schedule and type anabbreviation of the command you want to issue. These abbreviations areshown following:

Optional keywords are not allowed if you use the preceding commandabbreviations. If you need to use optional keywords, issue the commandthrough the Online Monitoring panel.

Enter To Issue This Command

REQU REQUEST SCHEDULE

SREQ SREQ SCHEDULE

HOLD HOLD SCHEDULE

RELE RELEASE SCHEDULE

CANC CANCEL SCHEDULE

CP CANCEL/POST SCHEDULE

PURG PURGE SCHEDULE

FORC FORCE SCHEDULE

RUN RUN SCHEDULE


4.10 Controlling Jobs


You can control jobs that are part of schedules at stations for which you areauthorized. To control jobs, issue one of these online commands:

ADD CANCEL COMPLETE FORCE HOLD PURGE

RELEASE REQUEST RERUN RESTAGE RUN SREQ

START SUBMIT TALTER CP

To enter a command, enter the number that appears next to it on thecommand line (===>). You may enter keywords by separating them from thenumber and from each other with commas. The chart following explains whatthese commands do.


Add jobs to the active queue that: -are not in the database

-are in the database but have not beenselected today

-have been INACTIVE, and add all theirsuccessors

-have been INACTIVE, and add anysuccessors that do not have REQUESTED intheir criteria and that do not have any otherINACTIVE predecessors that were alsoREQUESTED

46

40

41

52

ADD

RUN

REQUEST

SREQ

Submit jobs -that are waiting or SUBMIT FAILED -regardless of their current status

5345

FORCESUBMIT

Rerun jobs that are -canceled or completed -abended, failed, or interrupted

4057

RUNRERUN

PostStart to CPU and non-CPU jobsEnd to INTRPTD jobs or complete non-CPUand CPU jobs

5556

STARTCOMPLETE

Hold a job 43 HOLD

Release the hold on a job 42 RELEASE

Cancel a job 44 CANCEL

Cancel a job and post its successors as if thejob completed successfully

50 CANCEL/POST



When issuing commands from the Online Monitoring panel, you can specifythe schedule name (S=SNAME), the job number (JN=JNO), and the station number(ST=NN), as well as any of the keywords listed under the command name in thechapter "Controlling Schedules and Jobs" in the Unicenter CA-SchedulerReference Guide Part 1.

The following defaults are taken if you do not enter these keywords:

JN=jno Defaults to JN=01

ST=nn Defaults to the connect station (the connect station appears inthe upper right-hand corner of the panel)

To enter a keyword, enter the number of the command followed by a commaand then the keyword. If you enter multiple keywords, separate them withcommas. For example, you could enter the following valid TALTER command:

51,TESTJOB,SCHEDULE=TESTSCHD,ABEND=BACKOUT

If you run out of room to enter keywords, follow a keyword=valuecombination with a comma and press Enter . Another panel will be displayedthat allows you to continue the command.

You can issue certain control commands that pertain to jobs directly from anyof the status displays (SCHEDULER Command Processor panel). All you haveto do is position your cursor to the left of the job and type an abbreviation ofthe command you want to issue. These abbreviations are shown following:


Delete canceled or completed jobs 54 PURGE

Temporarily change the values defined for anactive job for this execution only

51 TALTER

Write a fresh copy of the JCL to the staginglibrary

47 RESTAGE


RER RERUN JOB

REQU REQUEST JOB

SREQ SREQ JOB

FORC FORCE JOB

STAR START JOB

COMP COMPLETE JOB

HOLD HOLD JOB



Optional keywords are not allowed if you use the preceding commandabbreviations. If you need to use optional keywords, issue the commandthrough the Online Monitoring panel.


RELE RELEASE JOB

CANC CANCEL JOB

CP CANCEL/POST JOB

PURG PURGE JOB

REST RESTART JOB

RUN RUN JOB

SUB SUBMIT JOB

4.10.1 Running Jobs With The ADD CommandADD allows you to run a single execution of a job today whether it is definedto the database. You can use this command to add a job to today's workloadif the job:

■ Is not in the database■ Is in the database with different keyword values

and if you only want to run the job on a "one-time" basis.

An ADDed job will only exist on the tracking file for one day (unless itbecomes backlogged); the only trace or record of it in the database will behistory records.

If you are in doubt as to whether the job being added will ever need to be runagain, we recommend that you define the job to the database and define anon-auto-selected schedule for it. Then you can issue a RUN command for theschedule whenever you need this job.



To select this option from the Online Monitoring panel, enter 46. For example,to add a job called JOBC, you would enter the following command in thecommand area of the Online Monitoring panel:

46,NAME=JOBC

Unicenter CA-Scheduler responds by displaying the Dynamic ADD panel:

� � SCHD-DAD �� DYNAMIC ADD �� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

JOB NAME : JOBC

JOB NUMBER : �1

STATION ID : 4�

SCHEDULE NAME : JOB PRIORTY : 5�

STAGE JCL : NO AUTO START : NO

DISPLAY KEY : DISPLY TIME : INTERRUPT : NO

LIBRARY TYPE : DRIVER MBR SUBID : MEMBER PASSWORD:

MEMBER NAME : SLI SUBLIB : ICCF LIB NUMBER:


POWER PRIORITY: 9 POWER USER :


RECOVERABLE : NO ABEND : FAIL CODE :

BACKLOG : YES

MUST START BY TIME :

COMPLETION DEADLINE TIME :

MAXIMUM EXECUTION TIME :

EARLIEST START TIME :

PF1=HELP

� �

This panel closely resembles the Job Definition panel discussed in the chapter"Maintaining the Database." Some fields are already filled in If you do notspecify a schedule name, that field defaults to $DYNxxxx where xxxx is thePOWER SYSID of this CPU. This schedule is dynamically created and added tothe workload for you.

After you key in values appropriate to this job, press Enter to display the nextDynamic ADD panel. Enter any predecessors or successors that you want tospecify on this panel. Specify any predecessors (jobname, job number, station,and schedule) in the PREDECESSOR JOBS fields. Specify any successors(jobname, job number, station, and schedule) in the SUCCESSOR JOBS fields.

For example, if you are adding JOBC to today's schedule and want it to runwhen JOBA completes successfully, specify JOBA's information in thePREDECESSOR JOBS fields as shown following.

If you want to specify that JOB1 and JOB2 should run once JOBC hascompleted successfully, specify JOB1 and JOB2 information in the SUCCESSORJOBS fields as shown following.



� � SCHD-DADP �� DYNAMIC ADD �� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

PREDECESSOR JOBS:

JOBNAME LIST: JOBA

JOB NUMBER LIST: �3

JOB STATION LIST:

JOB SCHEDULE LIST: SCHD1

SUCCESSOR JOBS:

JOBNAME LIST: JOB1,JOB2

JOB NUMBER LIST: �4,�5

JOB STATION LIST:

JOB SCHEDULE LIST: SCHD1,SCHD1

PF1=HELP

� �

When you are done, press Enter to add the job to today's schedule.


4.11 Summing Up

4.11 Summing Up

The Online Monitoring panel is the starting point for monitoring andcontrolling daily production.

To issue a command, you must enter the number that appears next to it on thecommand line (===>). You may enter keywords by separating them from thenumber and from each other with commas.

The Online Status panel allows you to monitor any queue, selecting just theportion that interests you. Queues are explained in the topic Displaying Status.Use the following parameters to tailor the queue display to your needs andseparate parameters with a comma.

For more information about * and ?, see the term mask character in theGlossary.

Use the following keywords to send messages from the Online Monitoringpanel. Enter these keywords after entering 3, and separate them with commas.(The U and T keywords are required.)

To Specify

Select a specific -schedule or job -station -CPU

S=sname or J=jnameST=idSYS=sysid

Select a group of schedules or jobs -starting with the same letters -ending with the same letters -containing the same letters

Use * or ?s where > occurs following:S=characters> or J=characters>S=>characters or J=>charactersS=>characters> or J=>characters>

Just display jobs received fromanother node

FM=nodeid

Display status at another node RO=nodeid

Display specific data -history data or -actual vs. expected times or -schedule summary or -reason codes

D=HD=TD=Somit D parameter

In a certain order (jobs grouped byschedule) -alphabetical order or -job priority order

omit OR= parameterOR=P


4.11 Summing Up

People with Manager authority can post and unpost predecessor conditions.That is done by entering the following values in the Online Monitoring panel.

To display the current values of all global parameters, go to the OnlineMonitoring panel and enter 6,D. To set a value, enter 6,GBLxnn=value. To seta value, you must have Manager authority.

To display the following information, go to the Online Monitoring panel andenter the values displayed following:

To Specify Abbreviation

Identify -who the message goes to

-what your message refers to

USER=ALL orUSER=OPERATOR orUSER=userid

JOB=jnameSCHEDULE=snameSTATION=idJNO=jno

U=

J=S=ST=JN

Define the text of the message TEXT='text' T

Route your message toanother node

ROUTE=nodeid RO=

To Post,Enter

ToUnpost,Enter

Followed by If the Predecessor You AreSatisfying Is The

4, 5, DSN N=dsname Close of a data set

4,4,

5,5,

SSCD N=snameSJOB N=jname


4,4,4,

5,5,5,

SCD N=snameJOB N=jnameVSE N=jname


To Display Enter

The data set name masks defined in the CAIJ$DSN table 7,$DSN

The autoscan information, and the current system date andtime

7,DATE


4.11 Summing Up

To Display Enter

The network information from the CAIJNET table in an NJEenvironment

7,NET

ThisCommand

Affects Jobs/Schedules

This way

ADD J Adds jobs that are not in the database tothe workload.

CANCEL S,J Cancels a job or schedule at any pointbefore completion.

COMPLETE J Ends interrupted jobs and completes allother jobs.

CP S,J Cancels a job or schedule and posts itssuccessors as if the job or schedule hadcompleted successfully.

FORCE S,J -Forces schedules that are waiting tostart. -Submits JCL for jobs that are waiting orSUBMIT FAILED.

HOLD S,J Holds work that is waiting or started.

PURGE S,J Deletes canceled or completed work fromthe status display.

RELEASE S,J Releases held schedules and jobs.

REQUEST S,J Moves requested jobs or schedules andtheir successors to the active queue.

RERUN J Reruns abended, failed or interruptedjobs.

RESTAGE J Writes a fresh copy of a job's JCL to thestaging library.

RUN S,J -Adds work that was not selected to theworkload. -Reruns canceled or completed work.

SREQ S,J Moves a schedule or job to the activequeue as well as any of its successorsthat are not REQUESTED and that donot have other INACTIVE predecessorsthat were also REQUESTED.

START J Posts START status for non-CPU jobs.

SUBMIT J Submits a job's JCL for execution.


4.11 Summing Up

Before using any of these commands, refer to the chapter "ControllingSchedules and Jobs" in the Unicenter CA-Scheduler Reference Guide Part 1 forcomplete command descriptions.

ThisCommand

Affects Jobs/Schedules

This way

TALTER S,J Temporarily changes values defined inthe database for just this execution.


Chapter 5. Criteria Language

The criteria language consists of a criteria vocabulary and a set of calendarmechanisms used to construct a reason, or set of reasons, for selecting aschedule or job for execution and for establishing its predecessors.

For example, if SCHEDA is to run every Monday and every Thursday, theselection criteria associated with this schedule is MON OR THU.

This example uses criteria vocabulary that refers to a processing period whenselecting a schedule. Several different types of processing periods can be used:

■ Day of week (as preceding)■ Week of month■ Day in cycle■ Week in cycle

■ Workday ■ Relative day■ Accounting day of month

■ Holiday■ Negative day of month (nn day from the end of a period)

Another condition that can cause selection of a schedule or job would beanother schedule or job being selected. For example, to select JOBB if JOBAwas selected, the criteria associated with JOBB is JOBA.

Previously, using the criteria vocabulary to select schedules or jobs wasdiscussed, but the criteria vocabulary is also used for defining predecessors.Predecessors are conditions that have to be met before a schedule or job isallowed to start. Other terms used for predecessor are prerequisite anddependency.

Predecessors can be the starting or ending of other schedules or jobs, theclosing of an output data set, a nonscheduled VSE job, and other items likethese. Any predecessor can be defined as occurring on the day the schedule orjob is selected or as having occurred on a prior day. This will be discussed inmore detail later through the use of examples.

Chapter 5. Criteria Language 5-1

The criteria language uses three types of yearly calendar mechanisms:

Absolute Gregorian CalendarDefines specific keywords that have absolute datesassociated with them. For example, the DAILY keywordcauses a job to be selected every day including weekendsand holidays; WEEK-DAY causes selection on Mondaythrough Friday including holidays; and so forth. Thismechanism is determined by the system and you do nothave to define anything; only use the keywords.

Datetables Defines workdays, holidays, accounting days, andaccounting periods. This is the most flexible calendarmechanism to use and is the one recommended. It alsoprovides the easiest transition at year end.

Calendars Define daily, weekly, and monthly calendars to selectschedules and jobs. When using calendars, only thecalendar name determines selection. For example, youcannot also select based on a criteria statement: withcalendars, criteria statements only define predecessors.To use this mechanism, you must define several differentcalendars.

The following topics explain the criteria vocabulary and calendar mechanisms.


5.1 Criteria Vocabulary


The criteria vocabulary consists of a set of reserved words broken into thefollowing categories:

■ Boolean expressions■ Selection of schedules and jobs■ Predecessor conditions on schedules and jobs

The following discusses these categories in more detail and contains someexamples.

5.1.1 Reserved Words for Use in Boolean ExpressionsOR and AND expressions are used with selection and predecessor keywords.The NOT expression is used with selection keywords only. Parentheses can beused to logically group these expressions.

The examples following show how these reserved words can be used to handlereal scheduling situations.

5.1.2 Reserved Words Used for SelectionThe following discusses reserved words that cause schedules and jobs to beselected on a given day.

Gregorian Calendar keywords include such words as DAILY, WEEK-DAY,WEEK-END, SUN, MON, JAN, DEC, 1ST, 31ST, and so forth.

Workday keywords include such words as WDAY, HDAY, WDOW1,WDOW7, WDOW-1, WDOM1, HDAY1, HDAY31, HDAY-1, RD01=+nn,RD31=-nn, and so forth.

Accounting period keywords include such words as xDAY, xDOM1, xDOM40,xDOM-1, xMOY1, xWOF1, and so forth, where x is a one-character prefix thatyou define when you set up a datetable. Datetables are discussed in moredetail later in this chapter.

A schedule or job can be used to determine selection. When it is used, itautomatically becomes a predecessor as well. Although the schedule or jobname itself causes selection to occur, there are a couple of reserved words thatcan be used with them. One of these keywords is SCD, which identifies thenext name as being a schedule name. Otherwise, it is always assumed to be ajob name.

The other keyword is START. Although the schedule or job name causesselection, START means that the predecessor is the starting of the schedule or



job. Normally, the predecessor is the completion. This subject is covered inmuch more detail later in this chapter.

The following examples demonstrate the use of selection reserved words. Eachof these examples is called a condition.

Note: When using relative dating in the criteria record, the relative date mustbe in parentheses or a syntax error will occur. For example,(RDxx=+yy)

Example Interpretation During Selection

DAILY Daily

MON Monday

WDAY Every workday

HDAY Every non-workday, meaning holidaysand possibly weekends. HDAY can alsobe expressed as NOT WDAY.

JOB1 Every day JOB1 is selected.

MON AND JOB1 Every Monday as long as JOB1 is alsoselected.

MON AND START JOB1 This is the same as the prior one. Thatis, every Monday as long as JOB1 is alsoselected.

MON AND NOT HDAY Every Monday as long as it is not aholiday.

WDOW1 First workday of any week.

WED AND SCD SCHD1 Every Wednesday as long as theschedule SCHD1 is also selected.

WDOM-1 OR JOB1 Last workday of the month or as long asJOB1 is selected.

WDOW2 OR NOT JOB1 Second workday of the week whetherJOB1 is selected. Also selected anytimeJOB1 is not selected.

7TH The seventh day of every month.

RD15= +01 First workday following the fifteenth ofevery month.

MAR AND RD14= -01 First workday preceding the fourteenthof March.



5.1.3 Reserved Words for Use in PredecessorsThis topic discusses reserved words that are used to define predecessorconditions. These reserved words ensure predecessor conditions are upheld,but do not cause any form of selection.

PRED Or PRED SCD indicates the predecessor job or schedule mustcomplete, probably on a prior day. That is, the predecessor mustcomplete some time since the job or schedule last ran. If the PREDschedule or job is also in today's workload, it will always wait fortoday's PRED.

NJE Indicates the predecessor job runs on another node. NJE can beprefixed with START indicating that this job will not start until theNJE job that is the predecessor also starts. It can also be prefixedwith PRED indicating the predecessor was an NJE job that ran on aprior day.

DOS Indicates the predecessor job is a nonscheduled VSE job. DOS canbe prefixed with PRED indicating it was run on a prior day.

DSN Indicates the predecessor is the close of an output data set. DSN canbe prefixed with PRED indicating the output data set was closed ona prior day.

GDG Indicates the predecessor is the close of an output generation datagroup. GDG can be prefixed with PRED indicating the outputgeneration data group was closed on a prior day.

GBLxnn Indicates a user-defined event must be satisfied. Thesepredecessors are called global parameters and are described in thetopic Commonly Asked Questions in the chapter "Tips."

When predecessors are defined this way, they are called explicit predecessors.That is, the predecessor name is explicitly stated in the criteria. This particulartype can even be further qualified as a keyword-defined explicit predecessor.

The following examples illustrate the use of predecessor reserved words. Eachof these examples is called a condition.

Example Interpretation Of Predecessors

JOB1 Do not run until after JOB1 completes.

START JOB1 Do not run until after JOB1 starts.

PRED JOB1 Do not run unless JOB1 completed at least oncesince the last time the job you are definingpredecessors for ran. If JOB1 happens to be intoday's workload, this job will not run until today'sJOB1 completes regardless of when JOB1 ranpreviously.



Example Interpretation Of Predecessors

SCD SCHD1 Do not run until all of the jobs in the scheduleSCHD1 have completed.

DOS TSTJOB1 Do not run until after the nonscheduled VSE jobTSTJOB1 completes. (The job TSTJOB1 is not underthe control of Unicenter CA-Scheduler.)

PRED DSNPROD.JOB1DSN

Do not run until after the output data setPROD.JOB1DSN has been closed at least once sincethis job was last run.

5.1.4 Combining Selection and Predecessor Criteria VocabularyPreviously, selection and predecessor processing have been treated as separateissues. They really are related, however.

For example, the selection criteria for JOBB is JOBA. That is, JOBB is selectedany time that JOBA is selected. In doing this, JOBA automatically becomes apredecessor to JOBB. Thus, JOBA is an explicit predecessor to JOBB. That is,the predecessor name is explicitly stated in the criteria. This particular typecan even be further qualified as a selection-defined explicit predecessor.

Selection-defined explicit predecessors are jobs or schedules used in theselection criteria. The following is a list of these criteria:

Job nameSCD schedule nameSTART job nameSTART SCD schedule name

Some examples that define selection and predecessor criteria for JOBC follow.

Example Interpretation Of Criteria

JOBA Select every time JOBA is selected andmake the successful completion of JOBAa predecessor of JOBC.

START JOBA Select every time JOBA is selected andmake the start of JOBA a predecessor ofJOBC.

MON AND JOBA Select every time JOBA is selected on aMonday. JOBC will not start until JOBAcompletes successfully.

WED AND START SCD SCHD1 Select every time schedule SCHD1 isselected on a Wednesday. JOBC will notstart until schedule SCHD1 starts.



Two types of explicit predecessors have been described so far:keyword-defined and selection-defined.

Implicit predecessors are predecessors that do not have to be defined in thecriteria. When the same schedule/job/job-number exists for more than onestation (01 - 99), the sequential order of the stations defines implicitpredecessors. For example, a CPU job on station 40 will always have animplicit predecessor of its staging job on station 39, if both are in the day'sworkload. Further, implicit predecessors are automatically selected on thesame day that the CPU job (station 40) is selected. You can, however, codecriteria for them to be selected less frequently than the CPU job. Note,however, that you cannot cause implicit predecessors to be selected on a daythe CPU job is not selected.

Furthermore, implicit predecessors can only exist for CPU jobs and post-CPUjobs. For example, a CPU job will not be submitted until all its pre-CPU jobscomplete. Likewise, post-CPU jobs will not be started until their CPU jobs haveended.

5.1.5 Using Multiple Conditions with ANDs and ORsThe examples that have been used so far have contained only one reason. Thatis, the condition or combination of conditions, individually caused the reason ajob or schedule was selected.

The way you separate reasons is with an OR outside of a set of parentheses orwith an OR if no parentheses are being used. For example,

MON AND JOB1 OR TUE AND JOB2

is the same as

(MON AND JOB1) OR (TUE AND JOB2)

Use parentheses as a normal convention since it more clearly depicts yourintention. All of our examples will appear with parentheses.

The reason a job is selected stays with the job for its life in the system. In theexample preceding, the value 01 would be the reason if it was selected becauseit was (MON AND JOB1). The value 02 would be the reason if it was (TUEAND JOB2). This value can be referred to as the reason code.

Understanding the relationships between reasons and predecessors isimportant. Since the criteria language is used to define both selection andpredecessor conditions, there are rules for interpreting this mixture.

Rule #1 Every Unicenter CA-Scheduler-controlled job or schedule listed in acriteria statement is a predecessor if it is also in the day'sproduction. Whether those jobs or schedules are part of the reasonfor selection does not matter.



Given the example preceding, no matter what day it is, JOB1 and JOB2 will bepredecessors as long as they are in the day's workload. If it is Monday andJOB2 happens to be in the workload for Monday, JOBC (the job being defined)will have to wait for both JOB1 and JOB2 to complete.

Does this mean that Unicenter CA-Scheduler just makes one list ofpredecessors for each job? Not at all. Rule #1 just applies to selection-definedpredecessors: jobs and schedules. Unicenter CA-Scheduler observes ORs usedwith keyword-defined predecessors.

5.1.6 Affect of NOT Condition on PredecessorsThe Boolean NOT expression affects selection just as you might expect:selection only occurs when something else does not happen that day. Forexample, if the criteria for JOBC is:

(MON AND NOT JOB1)

selection will occur only on Mondays when JOB1 is not selected.

How would predecessors be handled in the preceding example? If JOB1 forsome reason ends up in the workload (by a manual override), JOBC will waitfor it if JOB1 was added while JOBC was waiting for its start time to bereached or other predecessors to be satisfied.

Another example will help reinforce this point. Consider this criteria statementassociated with JOBC:

(MON AND NOT (JOB1 AND JOB2))

This will cause selection to occur only on Mondays when both JOB1 and JOB2are not selected. If either JOB1 or JOB2 is present, however, it will be apredecessor of JOBC. This shows that Rule #1 applies even when using NOTexpressions.

The NOT expression is used only for selection purposes within the criterialanguage.

5.1.7 Recommended Method for Defining Selection CriteriaSchedules are sets of related jobs grouped together in ways that are easilyunderstood by your production control area. So if production control thinks ofschedules as units of work, selection criteria would normally be defined at theschedule level. If all jobs in a schedule run when the schedule is selected,define when these jobs run once, on the schedule's criteria record which meansyou only need to define predecessors at the job level. If a job does not runevery time its schedule runs, define its own individual selection criteria on thejob criteria record. Keep the following rule in mind when coding selectioncriteria.



Rule #2 A job will only be evaluated for selection and eligible for today'sworkload if its schedule is selected or eligible for today's workload.

For example, if the selection criteria for SCHED1 is MON, and JOB1A inSCHED1 has a selection criteria of TUES, JOB1A will never get selected. JOB1Ais only looked at if its schedule is selected but SCHED1 is not selected onTuesdays, so JOB1A will never be selected.

Rule #3 When coding a job in the criteria language, always qualify it withits schedule name.

Previously we have not followed the preceding rule for simplicity's sakebecause schedule names technically are not required. However, if you omit aschedule name when referring to a job, Unicenter CA-Scheduler looks in itsdatabase and defaults to the first schedule it finds containing a job by thatname.

To specify a unique job, use this format:

jobname[-jobnumber] [station] [schedule]

Any or all of the three optional parameters (job number, station, and schedule)may be omitted, but the order in which they are specified is significant. Noticethat the job number must be connected to the job name with a hyphen (-) andno intervening blanks. For example, this is how to specify JOBA in SCHDAwith a job number of 02 at station 39:

JOBA-�2 39 SCHDA

This format can be used with any of the reserved words that are valid fordefining predecessor jobs (PRED, VSE, or START).

If you run simulation, be careful how you use the REQUESTED keyword. Toensure that simulation reports return reason codes that match those producedby Unicenter CA-Scheduler on the online status displays (SCHEDULERCommand Processor panel), specify REQUESTED after job and schedule namesin selection criteria whenever possible.

A schedule is eligible for selection even if AUTO SELECT=NO is specified.


5.2 Calendar Mechanisms


Most of the examples presented so far have used explicit vocabulary such asMON for Monday or WEEK-DAY for Monday through Friday, but thisoversimplifies what happens in real life. For example, we do have holidays.Your accounting month may not begin on the first of every month. Somemonths have four weeks, while others have five. There can be quite a variationnot only between different companies, but even different divisions within acompany.

Unicenter CA-Scheduler addresses all variations using three different calendarmechanisms:

The Absolute Gregorian CalendarDefines specific keywords that have absolute dates associatedwith them. For example, the DAILY keyword causes a job tobe selected every day including weekends and holidays;WEEK-DAY causes selection on Monday through Fridayincluding holidays; and so forth. This mechanism isdetermined by the system and you do not have to defineanything; just use the keywords.

Datetables Define workdays, holidays, accounting days, and accountingperiods. This is the most flexible calendar mechanism and isthe one recommended. It also provides the easiest transition atyear end. Each schedule defines which datetable to use forevaluating when to select that schedule and its associated jobs.

Calendars Define daily, weekly, and monthly calendars for selectingschedules and jobs. When using calendars, only the calendarname determines selection. For example, you cannot alsoselect based on another job being selected. To use thismechanism, you must define individual calendars. This is themechanism to use if all else fails.

5.2.1 Gregorian CalendarThe Gregorian calendar mechanism is the simplest to understand and can beused immediately. You do not have to define a calendar or datetable first. Allyou do is use the reserved words (keywords) when defining your selectioncriteria. Most of the preceding examples used keywords from the Gregoriancalendar mechanism.

This mechanism's reserved words that control selection are based on thestandard Gregorian calendar, not workdays or accounting days. Someexamples of these keywords follow:



There are many other keywords that can be found in the appendix "CriteriaVocablulary" in the Unicenter CA-Scheduler Reference Guide Part 2.

Do not forget that you can also use the Boolean reserved words AND, OR, andNOT:

Keyword When Selected

DAILY Every day including weekends and holidays

WEEK-DAY Monday through Friday

SUN Sunday

FRI Friday

MWF Monday or Wednesday or Friday

TT Tuesday or Thursday

JAN January

1ST First day of the month

SUN1 First Sunday of the month

WED-1 Last Wednesday of the month

2ND-WEEK Second week of the month (first Saturday starts thefirst week of the month)

WOY3 Third week of the year

WOY-2 Second-to-the-last week of the year

Example Always Selected

JAN AND 15TH On January 15

(JAN AND 1ST) OR(APR AND 1ST) OR(JUL AND 1ST) OR(OCT AND 1ST)

On the first day of each quarter

DEC AND THU-1 On the last Thursday in December

5.2.2 DatetablesThis calendar mechanism is the most flexible of them all and is the one werecommend you use. It handles holidays (and weekends) as they pertain toyour own environment. When defining the selection for a job or schedule,datetables are used to answer such questions as:

■ Is today a workday?■ Is tomorrow a holiday?■ Is this the fourth workday of the month?



In other words, Unicenter CA-Scheduler is smart enough to know today's date,but is not smart enough to automatically know your unique workdays,holidays, and accounting periods.

With datetables, you can use the reserved words described for Gregoriancalendars, but you must define your holidays. This is done with a full panelthat actually displays a calendar one month at a time. You can use two typesof keywords with datetables: workday keywords and accounting-periodkeywords.

5.2.2.1 Workday Keywords

Workday keywords are just what they say: keywords that relate to workdays.Workdays are days that are not defined as holidays. For our purposes,weekends are considered holidays (unless you specify otherwise). Thefollowing is a sampling of these keywords:


WDAY All workdays

HDAY All holidays

WDOW2 Second workday of the week

WDOW-1 Last workday of the week

WDOM-1 Last workday of the month

WDOM-3 Second-to-the-last workday of the month

WWOM2 Second work week of the month (any week with at leastone workday is counted as a work week)

RD01 = +1 First workday after the first day of any month

RD17 = -2 Two workdays prior to the 17th of any month

HDAY1 Current date plus one is a holiday

HDAY-3 Current date minus three days was a holiday

5.2.2.2 Accounting-Period Keywords

Later, when how to define a datetable is described, you will see how to define:

■ Accounting days■ When an accounting period starts■ When the accounting year ends

These accounting periods can be production cycles, sales cycles, or any otherunit of time. When you define a datetable, you have to define a prefix (anyletter, except E, H, N, P, or W, allowing for 21 different accounting periods)while using the same datetable. Each accounting period has its own prefix. The



A prefix or the A version of the datetable is the default datetable. When youuse a B prefix, the accounting resolutions will be taken from the B version ofthe datetable.

In the examples following, x is used instead of a prefix.

The following describes what is involved in setting up a datetable.

You have to start with a rule. You have to consider accounting periods goingover a year-end date. Consequently, a rule for datetables:

Rule #4 Define three year's worth of datetables for each unique datetablename. Each year being accessed must have a datetable for the yearbefore and after it.

The best way to describe the concept of datetables is to use an example.Suppose that production jobs run Monday through Saturday. That is a six-daywork week (so type a 6 over the 5 for the WORK WEEK field). After youpress the ENTER key, the datetable display shows January, 2003:

� � SCHD-DTC �DATETABLE DEFINITION� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

DATETABLE NAME: DATETAB

DATETAB PREFIX: A

DESCRIPTION : THIS IS AN EXAMPLE

DESIRED MONTH : JANUARY

DESIRED YEAR : 2��3

WORK WEEK : 6

SUNDAY MONDAY TUESDAY WEDNESDAY THURSDAY FRIDAY SATURDAY

��

�1A �2A �3A �4A �5A �6A

�7 �8A �9A 1�A 11A 12A 13A

14 15A 16A 17A 18A 19A 2�A

21 22A 23A 24A 25A 26A 27A

28 29A 3�A 31AP

PF1=HELP

� �


xDAY All accounting days for prefix x

xDOM1 First accounting day of the period (there canbe up to 40 accounting days in the period)

xDOM-1 Last accounting day of the period

xWOM2 Second accounting week of the period (therecan be up to 10 accounting weeks per period)

xWOM-1 Last accounting week of the period



Suppose you now want to indicate that January 1 is a holiday and anonaccounting day (by typing an H for holiday and an N for nonaccountingday on top of the 01A field). You could also change the end of the accountingperiod by removing the P from the 31st and putting it where ever you wantedit, say on the 30th. If January was the end of the accounting year, youwouldput an E on the 30th. After typing this data on the panel, the following wouldbe displayed before pressing the Enter key.


===> MASTER - WR

CONNECT : 4�


DATETAB PREFIX: A




WORK WEEK : 6


��

HN �2A �3A �4A �5A �6A

�7 �8A �9A 1�A 11A 12A 13A

14 15A 16A 17A 18A 19A 2�A

21 22A 23A 24A 25A 26A 27A

28 29A 3�APE 31A

PF1=HELP

� �

Now, press the ENTER key.

The panel following shows what happens. Notice that 01 is now displayed inlow intensity and there is no A following it.


===> MASTER - WR

CONNECT : 4�


DATETAB PREFIX: A




WORK WEEK : 6


��

�1 �2A �3A �4A �5A �6A

�7 �8A �9A 1�A 11A 12A 13A

14 15A 16A 17A 18A 19A 2�A

21 22A 23A 24A 25A 26A 27A

28 29A 3�APE 31A

PF1=HELP

� �

Once January's definition is complete, press Enter to go to February. When all12 months are defined, press Enter to store the datetable for this year on the



database. Also, define the corresponding datetables for the prior and nextyears.

5.2.2.3 Summary of Datetables

Datetables are broken into two categories: workday processing and accountingperiod processing. If you need more than one holiday definition, you willneed another datetable.

The reserved words (keywords) for the Gregorian Calendar mechanism andthe keywords for the Datetable calendar mechanism can be used together.Here are some examples of Gregorian or Datetable calendar mechanisms:

Example Interpretation

(MON AND WDAY) OR(TUE AND HDAY-1)

Select on Monday when Monday is not aholiday, or select on Tuesday when Mondayis a holiday.

WDOW1 Select the first workday of every week. Thisis the same as preceding except if Tuesday isalso a holiday, it will be selected onWednesday.

WDAY AND (MON ORWED OR TT)

Select every Monday through Thursdayexcept on holidays.

WDAY AND NOT FRI This is the same as the preceding example,only expressed more .

BDAY AND NOT BDOM-1 Select on every accounting day except for thelast accounting day of the period. Thisreferences the datetable defined with prefix B.

WDAY AND WOY-1 Select every workday of the last week of theyear.

MON AND (WWOM2 ORWWOM4)

Select every Monday of the second and fourthweeks of the month regardless of whetherMonday is a holiday.

ADAY AND NOT HDAY Select on every accounting day that is not aholiday. Notice that an accounting day maybe a holiday (this is not normally the case).

5.2.2.4 Date Translation Table Report

Previously discussed were the Gregorian calendar and datetables. A way isneeded to see what conditions are met on any given day. The Date TranslationTable report is obtained by running the Unicenter CA-Scheduler Utility withthe REPORT DATETRAN transaction. You can request a specific date or



datetable on this transaction if you desire. Reviewing this report will help youunderstand the Gregorian calendar and datetables better.

COMPUTER ASSOCIATES DATE TRANSLATION TABLE

DATETRAN PAGE 1

Unicenter CA-Scheduler 7.3 96�5SHESA

�4 APR 2��3 15.53.49

SIMULATION DATE �8 SEP 2��3

JULIAN DATE=95251

TABLE NAME=DATETAB

GREGORIAN DATE=�9/�8/95

DAY OF WEEK=FRI WEEK-DAY=YES WEEK-END=NO MWF=YES TT=NO NTH DAY OF MONTH=FRI2

FRI-4 NEGATIVE DAY OF MONTH=DOM-23

WEEK OF MONTH=2ND-WEEK WEEK OF YEAR=WOY36 WOY-18 DAYS IN MONTH=3� LEAP-YEAR=NO

DAY1OF2=NO DAY2OF2=YES

DAY1OF3=NO DAY2OF3=NO DAY3OF3=YES

DAY1OF4=NO DAY2OF4=YES DAY3OF4=NO DAY4OF4=NO

DAY1OF5=NO DAY2OF5=NO DAY3OF5=NO DAY4OF5=NO DAY5OF5=YES

DAY1OF6=NO DAY2OF6=NO DAY3OF6=NO DAY4OF6=NO DAY5OF6=NO DAY6OF6=YES

WEEK1OF2=YES WEEK2OF2=NO

WEEK1OF3=YES WEEK2OF3=NO WEEK3OF3=NO

WEEK1OF4=YES WEEK2OF4=NO WEEK3OF4=NO WEEK4OF4=NO

WEEK1OF5=NO WEEK2OF5=NO WEEK3OF5=YES WEEK4OF5=NO WEEK5OF5=NO

WEEK1OF6=YES WEEK2OF6=NO WEEK3OF6=NO WEEK4OF6=NO WEEK5OF6=NO WEEK6OF6=NO

WORK-DAY=YES WORK DAY OF WEEK=WDOW5 WDOW-1 WORK DAY OF MONTH=WDOM6 WDOM-16 WORK

DAY OF YEAR=18� -81

WORK WEEK OF MONTH=WWOM2 WWOM-4 WORK WEEK OF YEAR=WWOY36 WWOY-17

RD�1=+�5 -16 RD�2=+�5 -16 RD�3=+�5 -17 RD�4=+�4 -18 RD�5=+�3 -19

RD�6=+�2 -2� RD�7=+�1 -21 RD�8=+�� -��

RD�9=+22 -�1 RD1�=+21 -�1 RD11=+2� -�1 RD12=+2� -�2 RD13=+2� -�3

RD14=+19 -�4 RD15=+18 -�5 RD16=+17 -�6

RD17=+16 -�6 RD18=+15 -�6 RD19=+15 -�7 RD2�=+15 -�8 RD21=+14 -�9

RD22=+13 -1� RD23=+12 -11 RD24=+11 -11

RD25=+1� -11 RD26=+1� -12 RD27=+1� -13 RD28=+�9 -14 RD29=+�8 -15

RD3�=+�7 -16 RD31=+�6

HDAY=NO

HDAY-1=NO HDAY-2=NO HDAY-3=NO HDAY-4=NO HDAY-5=YES HDAY-6=YES HDAY-7=NO

HDAY1 =YES HDAY2 =YES HDAY3 =NO HDAY4 =NO HDAY5 =NO HDAY6 =NO HDAY7 =NO

HDAY8 =YES HDAY9 =YES HDAY1�=NO

HDAY11=NO HDAY12=NO HDAY13=NO HDAY14=NO HDAY15=YES HDAY16=YES HDAY17=NO

HDAY18=NO HDAY19=NO HDAY2�=NO

HDAY21=NO HDAY22=YES HDAY23=YES HDAY24=NO HDAY25=NO HDAY26=NO HDAY27=NO

HDAY28=NO HDAY29=YES HDAY3�=YES

HDAY31=NO

A-ACCOUNTING DAY=YES DAY OF MONTH=ADOM6 ADOM-16 DAY OF YEAR=18� -81 WEEK OF

MONTH=AWOM2 AWOM-4 MONTH OF YEAR=AMOY9 AMOY-4

X-ACCOUNTING DAY=YES DAY OF MONTH=XDOM6 XDOM-16 DAY OF YEAR=18� -81 WEEK OF

MONTH=XWOM2 XWOM-4 MONTH OF YEAR=XMOY9 XMOY-4

The Date Translation Table Report is used to show you what selectionkeywords are TRUE for a specific date and datetable combination. It firstdisplays the Julian and Gregorian dates with the datetable name that was usedto determine workdays, accounting days, and accounting periods. (Thedatetable name is on the right side of the report).

Notice the next set of lines pertain to the Gregorian calendar and include DAYOF WEEK, WEEK OF MONTH, DAYnOFm, and WEEKnOFm. These indicatewhether a condition is satisfied. For example, WEEK-DAY=YES means that



any time you specified WEEK-DAY as the criteria, the schedule or job will beselected. The rest of the lines pertain to the datetable. They include theworkday, the workday of the week, the workday of the month, the workday ofthe year, the work week, the relative days of the month, and the variousaccounting days.

After reviewing this report carefully, you should understand how the criteriavocabulary works with the Gregorian calendar and datetables.

5.2.3 CalendarsTo use calendar processing, set aside everything you have learned so far aboutthe Gregorian calendar and datetables. Calendars use an entirely differentapproach to selecting schedules and jobs. Do not try to relate any discussion ofcalendars to the other calendar mechanisms.

We do not recommend that you use calendars. Instead, try to do all of yourdefinitions with datetables or the Gregorian calendar or a combination of thetwo. Consequently, the description of calendars will be brief. If you do notintend to use calendars, you can skip this subtopic.

You would use this mechanism if a set of schedules have to run on specificdates during the year and there is no relationship between the dates. Then youwould use a calendar to define just the days of the year on which thoseschedules run.

When using calendars, a schedule or job is selected on the days that thecalendar specifies as workdays. With calendars, the criteria language is notused for selection, only for defining predecessors. Again, the only thing youspecify on a schedule for selection purposes is the calendar name. The samecalendar also applies to the jobs in that schedule.

The following steps describe how to use calendars.

5.2.3.1 Step 1: Define the prototype calendar

Before you define any calendars, first define a prototype calendar. Thiscalendar defines your holidays and what to do if jobs are selected on holidays.In case of holidays, should jobs run on the prior workday, the next workday,or not at all? The prototype calendar must have a name PROTOyy, where yyis the year (for example, PROTO87).

You can only have one prototype calendar for each year which means thatthere is only one set of holiday definitions. Once the prototype is defined, youcan define calendars specific to your needs. Defining a prototype calendarfollows.



The panel following defines the prototype calendar for 2003. It specifies afive-day work week. If jobs are selected on holidays, Unicenter CA-Schedulerhandles rescheduling differently depending on the selection frequency:

■ With a WEEKLY frequency, jobs will be selected on the workday after theholiday (nw: next workday).

■ MONTHLY selection reschedules jobs the workday before the holiday (pw:prior workday).

■ Unicenter CA-Scheduler will not reschedule jobs selected from dailycalendars when holidays occur because we have not specified anything inthe DAILY field.

� � SCHD-CU ��CALENDAR DEFINITION�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

CALENDAR NAME : PROTO96

DESCRIPTION : 2��3 prototype calendar



WORK WEEK : 5

DAILY (Y): WEEKLY (DOW): nw MONTHLY : pw

PF1=HELP

� �

When you press Enter, January's dates are displayed in calendar format. Sincedefault work week value of 5 was accepted, the five weekdays are shown inhigh intensity and the two weekend days are shown in low intensity. You canchange January 01 to a holiday by overtyping 01 with H and pressing Enter.This changes the high intensity to low intensity.



� � SCHD-CU ��CALENDAR DEFINITION�� CA-SCHEDULER

===> MASTER - WR

CONNECT : 4�

CALENDAR NAME : PROTO96

DESCRIPTION : 2��3 PROTOTYPE CALENDAR



WORK WEEK : 5

DAILY (Y): Y WEEKLY (DOW): NW MONTHLY : PW


��

H1 �2 �3 �4 �5 �6

�7 �8 �9 1� 11 12 13

14 15 16 17 18 19 2�

21 22 23 24 25 26 27

28 29 3� 31

PF1=HELP

� �

Now pressing Enter causes FEBRUARY to be displayed. When all 12 monthsare defined, press Enter and the prototype calendar is entered in the database.You can now schedule jobs for selection according to the prototype calendar.You can also use the prototype calendar as the basis for other calendars.

5.2.3.2 Step 2: Define daily, weekly and monthly calendars

Now that we have a prototype calendar, define other types of calendars.When defining calendars, invent your own names for them such as DAILY,TUESDAYS, PAYSEMI, ENDOFWK, or ENDOFMO.

To define a daily calendar, just specify a Y in the DAILY field.

To define a weekly calendar, specify a day of the week in the WEEKLY(DOW) field. It can be SUN, MON, ..., SAT, or WE (Saturday and Sunday). Ifthis day corresponds with a holiday on the prototype calendar, the jobautomatically moves to the next day (NW on the prototype) or the previousday (PW on the prototype).

To define a monthly calendar, use the MONTHLY field to specify the day onwhich schedules or jobs that reference this calendar are to be selected. It canbe FD (first day of month), LD (last day of month), or nn (nnth day of month)to identify absolute days of the month. If any of these fall on a holiday, theselection is based on the manner in which you defined the prototype. There isa corresponding set of days used for workdays. These are FW, LW and nnW.Since these are workdays, holidays are automatically considered.


5.3 Some Examples

5.3 Some Examples

Now that you are familiar with the criteria language and calendarmechanisms, consider how to apply what you have learned to the followingscheduling problems.

Example 1

To run the Weekend Summary Report on the first workday of the week, whichcriteria statement would you use?

Criteria:

WDOW1

Example 2

Now use another variation of WDOW to schedule the Weekly SummaryReport to run on the last workday of the week.

Criteria:

WDOW-1

Example 3

Which criteria statement would you use to run the Monthly Summary Reporton the first workday of the month?

Criteria:

WDOM1

Example 4

Which variation of WDOM will run the Monthly Summary Report on the lastworkday of the month?

Criteria:

WDOM-1


5.3 Some Examples

Example 5

The weekly accounting report runs on Friday. If Friday is a holiday, the reportruns on the following Monday. If the following Monday is also a holiday, thereport runs on the following Tuesday. Which criteria statement conveys thismeaning?

Criteria:

(FRI AND WDAY) OR

(MON AND WDAY AND HDAY-3) OR

(TUE AND WDAY AND HDAY-4 AND

HDAY-1)

Example 6

An Accounting schedule (ACCPROD) consists of three jobs:

■ PROD001 - the daily summary that runs each workday■ PROD002 - the summary that runs on Friday whether Friday is a holiday,

and is not dependent on PROD001■ PROD003 - the weekly summary report that runs on Friday night and

must wait for the other two jobs to finish

Which criteria statements apply to this schedule and its jobs?

Criteria for schedule ACCPROD&COLON.

None: All jobs may be selected daily.

Criteria for job PROD001:

WDAY


FRI


FRI AND

(PROD��1 ACCPROD OR PROD��2

ACCPROD)

For selection purposes, the OR expression will be handled as expected.However, predecessors that are jobs are handled as if there is always an ANDcondition. Consequently, if Friday is a workday, PROD003 will wait for bothPROD001 and PROD002.


5.3 Some Examples

Example 7

A payroll schedule (PAY) consists of two jobs:

■ PAY001 - the summary that runs every weekday and needs an input dataset, PAY001.INPUT, that is transmitted every weekday from an RJE site. Itmust also wait for job PAY002.

■ PAY002 - the summary that only runs on Friday.

Criteria for schedule PAY:

WEEK-DAY

Criteria for job PAY002:

FRI

Criteria for job PAY001:

DSN PAY��1.INPUT AND

(PAY��2 PAY OR NOT PAY��2 PAY)

This tells Unicenter CA-Scheduler to schedule job PAY001 every week day,whether job PAY002 is scheduled or not. Job PAY001 will wait for a data set tobe created every week day, and will also wait for job PAY002, when it isscheduled on Friday.

Example 8

The Manufacturing Quarterly production schedule (MANQTR) contains threejobs that run on the last day of the manufacturing quarter. MANQTR runs ona 4-week, 4-week, 5-week cycle defined in a datetable specified in the scheduledefinition using a prefix of M.

Criteria for schedule MANQTR:

MDOM-1 AND

(MMOY3 OR MMOY6 OR MMOY9 OR

MMOY12)

Criteria for job JOBA:

None - Defaults to whenever the schedule is selected.

Criteria for job JOBB:

JOBA MANQTR

Criteria for job JOBC:

JOBB MANQTR

The example preceding shows how you can define selection criteria at theschedule level and predecessors at the job level. Separating selection criteria


5.3 Some Examples

and predecessor conditions this way makes it easier to evaluate these criteriastatements.

Example 9

In this example, something a little more practical will be shown to show someof the logic behind determining criteria, which shows the type of thoughtprocess you may go through.

The schedule named IH7BKUP backs up some disks and consists of three jobs:a daily backup, a weekly backup and a monthly backup.

The daily job IH7D02 normally runs Monday through Thursday.Consequently, its criteria would be something like:

MON OR TUE OR WED OR THU

What happens on holidays? On holidays, you do not want the job to run. Toomit holidays, revise the criteria as follows:

WDAY AND (MON OR TUE OR WED OR THU)

Now Monday through Thursday also have to be workdays. A more conciseway of writing this criteria statement is as follows:

WDAY AND NOT FRI

Another factor to consider is whether this job has predecessors. In this case, itdoes not, so the daily job's selection criteria is now complete.

Next, work on the weekly job. You already know to be conscience of holidays.If the weekly job runs on Monday through Thursday, the daily job must finishfirst. The criteria statement that best describes this is shown following.

WDAY AND FRI

OR

(WDAY AND THU AND HDAY1 AND IH7D�2 IH7BKUP)

OR

(WDAY AND WED AND HDAY1 AND HDAY2 AND IH7D�2 IH7BKUP)

Since the weekly job will always run on the last workday of the week, you cansimplify the criteria statement preceding as follows:

WDOW-1 AND PRED IH7D�2 IH7DBUP

The monthly job IH7M02 runs on the last workday of the month. Itspredecessors vary depending on what day of the week this job runs.

■ If the last workday falls on Monday through Thursday, the monthly jobshould wait for the daily backup to complete.


5.3 Some Examples

■ If the last workday of the month is a Friday, the monthly job should waitfor the weekly backup to complete.

■ If the last workday of the month falls on a Saturday or Sunday, themonthly backup job has no predecessors. However, the datetable wasdefined for a five-day work week so Saturdays and Sundays are notworkdays.

The criteria would be:

WDOM-1 AND (IH7D�2 IH7BKUP OR IH7W�2 IH7BKUP)

Shown following is the finished product:

Criteria for schedule IH7BKUP:

None - Defaults to looking at all jobs each day.

Criteria for job IH7D02:

WDAY AND NOT FRI

Criteria for job IH7W02:

WDOW-1 AND PRED IH7D�2 IH7BKUP

Criteria for job IH7M02:

WDOM-1 AND

(IH7D�2 IH7BKUP OR IH7W�2 IH7BKUP)


5.4 What Is Wrong with These Examples?


Now that you have a basic understanding of the criteria language, try testingyour knowledge by debugging errors in the following criteria statements.

Example 1

Criteria for schedule SCHD01:

MONDAY

Will this job run on Mondays? Not likely because MONDAY is not avocabulary word. Instead, Unicenter CA-Scheduler interprets MONDAY as ajob name. Therefore, this job will only be selected when the job MONDAY isselected. Since you probably do not have a job named MONDAY, the scheduleSCHD01 would never be selected.

The correct criteria vocabulary word is MON.

Example 2


WDOW-1 OR DSN JOBA.DATASET

The intent is to select JOBB on the last workday of the week, but that is notwhat happens. Evaluate this statement carefully to see what is wrong. It isimportant to evaluate the selection criteria and the predecessor conditionsseparately.

What is JOBB's predecessor? The data set JOBA.DATASET must be closed onthe day JOBB is selected before JOBB will be submitted.

When is JOBB selected? Not just on WDOM-1 (the last workday of the month).Why? Because of the OR. The days on which JOBB is selected will be:

WDOW-1 OR 'keyword-defined parameter'

Unicenter CA-Scheduler cannot translate DSN JOBA.DATASET into a selectioncondition, so the second condition defaults to DAILY. Because of the OR, thisjob is selected WDOW-1 OR DAILY. How could you rewrite the statement torun JOBB when intended? Code the criteria statement with an AND instead ofan OR:

WDOW-1 AND DSN JOBA.DATASET

This selects JOBB on the last workday of the month and waits for the data setJOBA.DATASET to close before submitting JOBB.



Example 3


MON AND JOBB SCHED�1 OR WED


MON OR WED AND JOBA SCHED�1

Here is another problem. Why do not JOBA and JOBB in schedule SCHED01run when expected? Both jobs are supposed to run Mondays andWednesdays. On Mondays, JOBB should be the predecessor to JOBA, butconversely on Wednesdays.

The meaning of these criteria statements is confusing until you add someparentheses to show how the system will interpret this:


(MON AND JOBB SCHED�1) OR WED


MON OR (WED AND JOBA SCHED�1)

Now it is a bit clearer. First, look at the selection criteria. Both jobs are alwaysselected on Mondays and Wednesdays:

■ JOBA is always selected on Wednesdays, so JOBB is, too.

■ JOBB is always selected on Mondays, so JOBA is also selected onMondays.

That seems in order, so look at the predecessor conditions, remembering therule for evaluating predecessors:

There are no OR relationships with selection-defined explicit predecessors. AllORs become ANDs.

The preceding means the explicit predecessor of JOBA is JOBB, and the explicitpredecessor of JOBB is JOBA. When jobs require each other as predecessors,that creates a predecessor loop, which is also called predecessor deadlock.Although these deadlocked jobs are selected properly, neither job ever runsbecause their predecessors are never satisfied. You can run the AnalyzeReport at any time to detect deadlocks automatically.

Example 4


NOT MON OR NOT TUE



Suppose you want JOBA to run on any day but Monday or Tuesday. Whydoes the criteria statement preceding not make that happen?

Instead, JOBA is always selected because on Mondays, JOBA is selectedbecause it is not Tuesday. And on Tuesdays (and every other day), JOBA isselected because it is not Monday.

There are two valid ways to code this criteria:


NOT (MON OR TUE)

Another way to express this criteria:

NOT MON AND NOT TUE

Example 5


ADAY AND JOBA SCHED�1 AND

GBLB�1=YES

OR

ADAY AND GBLB�1=YES

JOBB in SCHED01 will always be selected on ADAY. The confusion ariseswhen evaluating predecessors. JOBB is always supposed to wait for the globalGBLB01 to be set to YES. If JOBA is in the day's workload, it is supposed to bea predecessor to JOBB.

That is not what happens. Instead, when JOBA is present, status shows thatJOBB waits for predecessors JOBA, GBLB01, and GBLB01. When GBLB01 is setto YES, JOBB starts regardless of JOBA because of the second GBLB01. Thefollowing is what happens.

After JOBB is selected, these predecessors are left for evaluation:

(JOBA SCHED01 AND GBLB01=YES) OR (GBLB01=YES)

JOBB will start as soon as GBLB01 is set to YES.

The correct way of coding this criteria statement is:


ADAY AND JOBA AND GBLB�1=YES

OR

ADAY



After JOBB in SCHED01 is selected, only these predecessors are left forevaluation:

(JOBA AND GBLB01=YES)

When JOBA is not in the day's workload, Unicenter CA-Scheduler knows thatit cannot be a predecessor.

Example 6


MON OR TUE OR WED OR THU OR FRI

OR

(SAT AND PRED JOBA)

The intent is that JOBB would run Monday through Saturday, but only onSaturday if JOBA completed sometime since last Saturday (for example, it maybe that JOBA only runs on Fridays). The rule is that keyword-defined explicitpredecessors apply across all selection criteria. Consequently, JOBB will waitfor JOBA every time JOBB is selected (even on Monday, Tuesday, and soforth).

To accomplish this, you have to set up JOBB as two separate jobs: JOBB-01 andJOBB-02. Notice how the criteria for JOBB-01 has been simplified following.

The correct way of coding this criteria statement is:

Criteria for the first job JOBB-01:

WEEK-DAY

Criteria for the second job JOBB-02:

SAT AND PRED JOBA


5.5 Summing Up

5.5 Summing Up

Evaluate criteria statements twice: once to determine selection criteria andagain to identify predecessor conditions. When coding a job in the criterialanguage, always qualify it with its schedule name. Use the SCD keywordbefore a schedule name to identify it as such.

Selection A job will only be evaluated for selection and eligible fortoday's workload if its schedule is selected or eligible fortoday's workload. A schedule is considered eligible forselection if the only reason it was not selected is because itwas defined with AUTO SELECT=NO.

The NOT keyword only applies to selection.

Predecessors Every job or schedule listed in a criteria statement is apredecessor if it is also in or eligible to be in the day'sproduction. Whether those jobs or schedules are part of thereason for selection does not matter.

Unicenter CA-Scheduler observes ORs used with allkeyword-defined predecessors except PRED, meaningNJE,VSE, DSN, GDG, and GBLxnn.

A criteria statement like NOT JOBA defines JOBA as apredecessor.

If jobs or schedules are predecessors, Unicenter CA-Schedulerwaits for them to complete unless you precede their nameswith the keyword START.

Calendars Define daily, weekly, and monthly calendars for selectingschedules and jobs. When using calendars, only the calendarname determines selection.

Datetables Define three years' worth of datetables for each uniquedatetable name. Each year being accessed must have adatetable for the year before and after it.


Chapter 6. Tips

This topic of the manual is intended to provide you with some helpful hintson using Scheduler. Some of the most commonly asked questions are followedwith a discussion of some pitfalls. The questions are grouped by topics thatparallel the structure of this manual:

■ Startup tasks■ Maintaining the database■ Analyzing the database

■ Daily processing

This organization allows each topic to stand on its own so you can jump fromtopic to topic. Do not be concerned about reading this chapter in the order thattopics appear.

Chapter 6. Tips 6-1

6.1 Commonly Asked Questions


This topic consists of a series of questions that are commonly asked.

The following table lists the topic category with associated questions which areanswered following the table.

Topic Question

Startup Tasks When should autoscan be performed?What is the general standard for numberingstations?Should I use datetables or calendars?When should I define a new datetable versus anew cycle in an existing datetable?

Maintaining TheDatabase

How should I organize my schedules?Is there a fast way to add data to the database?When should a job be staged?When is a job submitted?What are global parameters and when are theyused?How can I run a job like an edit check repeatedlyuntil its output is correct?How and when can I display documentationautomatically?What are my options when a job abends?

Analyzing TheDatabase

How can I prevent predecessor loops?When should I run forecasts?When should I run simulation?How do I plan when to run a new application?How do I verify a new application?Is there a way that I can create my own reports?

Daily Processing From where can I issue Unicenter CA-Scheduleroperator commands?What is the difference between FORCE, SUBMIT,RERUN, RUN, ADD, REQUEST, and SREQ?When is the PRED flag reset?What happens if there was a system crash?

6.1.1 Startup TasksCommonly asked questions concerning startup tasks follow.



6.1.1.1 When Should Autoscan Be Performed?

Autoscan is the daily process that purges completed jobs from the Schedulertracking file, backlogs schedules and jobs, if appropriate, and selects the day'sworkload. Scheduler scans the database, analyzing the selection criteria andplacing the selected schedules and jobs onto the tracking file.

If your production normally starts at 16:00 and runs during the night witheverything completing by 07:00 or 08:00, then autoscan should be run at 08:00or shortly after that. Run autoscan at a time when your machine load is at alow point.

Notice the VSE jobs that are running will not go to the end of job untilautoscan completes. This ensures that the Unicenter CA-Scheduler monitor willnot miss events such as database close, VSE job ends, scheduler job ends, andso forth.

Running autoscan this way gives the production control area a chance to geteverything ready for the day's workload, which includes JCL changes, controlstatement changes, data entry work, last-minute changes, and the like.

6.1.1.2 What Is the General Standard for Numbering Stations?

Normally, stations are set up as follows:

20 Data entry 39 JCL staging 40 CPU processing

Station 20 Data entryJobs start at their early start time if you specify AUTOSTART=YES (as long as their predecessors and resources aresatisfied). However, you always have to manually post thesedata entry jobs when they have ended.

Station 39 JCL stagingJobs must be manually posted as ENDED (using theCOMPLETE command) before a CPU job with the same namewill be submitted. If you specify that the station 39 job is to beautomatically started (AUTO START=YES), it will be startedat its early start time as long as its predecessors and resourcesare satisfied.

Station 40 CPU processingJobs will be started when the early start times are met, allpredecessor conditions are fulfilled, and resources areavailable. CPU job processing is automatic unless you overrideit.

Chapter 6. Tips 6-3


6.1.1.3 Should I Use Datetables or Calendars?

Datetables and calendars are two different methods used to select schedulesand jobs for a specific day. Datetables provide significantly more flexibilitythan calendars and should be used if at all possible. They are a bit morecomplicated to understand, but entail less maintenance than calendars whengoing from year to year. Datetables also allow multiple accounting periods aswell as different holidays.

One area where you will want to use Calendars is when the schedule has torun according to a set of dates that follows no pattern. Define these individualdays once in a calendar. Then when any schedule runs on those dates, yougive it that calendar name for selection.

For most of your application needs, however, use datetables. A detaileddiscussion on this matter appears in the chapter "Criteria Language."

6.1.1.4 When Should I Define a New Datetable Versus a New Cycle in anExisting Datetable?

Keep in mind that a cycle can be an accounting, production, or sales period.You can have up to twenty cycles defined with any one datetable, and anynumber of datetables. The datetable prefixed by the letter A is your defaultproduction datetable. The other prefixes are variations upon that datetable.

Any time you want to schedule a job based on a combination of two or morecycles, you must use the datetable prefix; you cannot use different datetablenames.

6.1.2 Maintaining the DatabaseCommonly asked questions concerning maintaining the database follow.

6.1.2.1 How Should I Organize My Schedules?

A schedule should consist of a group of logically related jobs. This group ofjobs usually belongs to one application, but could also be run at the samefrequency. For example, you could define a Payroll schedule containing all thepayroll jobs and its selection criteria. If certain jobs in the schedule do not runevery time the schedule is selected, define the selection criteria for theexceptional jobs. Or the daily Accounts Receivable jobs could be contained inone schedule and the weekly Accounts Receivable jobs could be in another.Possibly, the weekly schedule is dependent on the daily schedule to complete.

Do not organize schedules just by frequency. For example, do not have aMonday schedule. There should not be one schedule just for requested jobs,either, unless it is easily manageable. Instead, try to keep application-relatedjobs together. This makes interdependencies within applications much clearer.



Keep in mind, most options defined for a schedule apply to all jobs in thatschedule. You can, however, override these options at the job level.

Try to keep schedules small (around 50 jobs) so they are easily managed. Thisis particularly important when a schedule gets backlogged or when scrollingthrough jobs displayed on Online Status panels.

6.1.2.2 Is There a Fast Way to Add Data to the Database?

If you have a lot of information to add, you should always analyze whether itwould be best to do it in a batch mode. You would use a full-panel editor toformat the data and then run it through the Unicenter CA-Scheduler batchutility (CAJUTIL0).

You can take a shortcut when using the Online Database Maintenance facility.Each time you enter a panel of data, Unicenter CA-Scheduler translates thisinto a batch command with appropriate keywords, which invokes the batchutility program and processes the command. Once the command is processed,it is redisplayed in its batch format at the top of the panel in an inputcommand area. The panel on which this is displayed is called the SCHDUTILOutput panel.

The SCHDUTIL Output panel will also contain any messages associated withthe command just processed and currently displayed. Messages can confirmthat the database has been updated or that a command contains specific errors.The shortcut allows you to overtype any part of the batch command displayedon the SCHUTIL Output panel. Once the batch command is displayed, youcan change part of the command, press Enter, and the new command will beprocessed.

You can use this technique to:

■ Correct errors■ Add a similar job or schedule to the database

To reduce the possibility of destructive errors, this feature does not permit youto alter or delete multiple records.

6.1.2.3 When Should a Job Be Staged?

Staging a job means that at autoscan time or whenever the job is manually runwith the RUN command, the job's JCL is moved from the master JCL file(LIBTYPE field) to the Unicenter CA-Scheduler staging library. This LIBTYPEwill default to the one that appears in the LIBTYPE installation option of theCAIJGEN macro, but can be overridden at the schedule level and again at thejob level.

A job should only be staged if its JCL needs to be changed before it runs or ifit has control statements that need to be changed or added.

Chapter 6. Tips 6-5


To have a job's JCL staged, you must make the STAGE JCL field be YES on theJob Definition panel for station 40 and either:

■ Define an EARLIEST START TIME that gives users enough time to changethe JCL or

■ Define the same job to station 39 (the staging station)

Using the first method does not guarantee that the staged JCL will be ready torun before Unicenter CA-Scheduler submits it. A job's EARLIEST STARTTIME may arrive before its JCL has been modified in preparation forsubmission.

To ensure that a user at the JCL setup station has enough time to modify andreview the staged JCL, use the second alternative mentioned preceding. Thejob defined at station 39 will be an implicit predecessor of the CPU job atstation 40 which means the CPU job cannot be submitted until the job atstation 39 has been manually marked as ENDED using the COMPLETEcommand.

You could, for example, have a daily job that only needs to have its JCL or acontrol statement changed on Fridays. Therefore, you only want to change theJCL on Fridays. You can accomplish this by allowing the CPU job (the oneassigned to station 40) to be selected DAILY and the staging job (the same jobname within the same schedule defined to station 39) to be selected FRI.Notice that the job's JCL will always be staged, even though you only changeit on Fridays. Remember, the station 39 job has to be manually started orAUTO START=YES must be specified in its definition. When the JCL has beenchanged, you mark the job on station 39 completed with the COMPLETEcommand.

A job's JCL can be staged (taken from the master JCL file as specified in theLIBTYPE field and placed in the Unicenter CA-Scheduler staging file) even ifstaging is not automatic. That is, regardless of whether you had STAGE=YESor not, a fresh copy of the job's JCL will be restaged. Furthermore, you maywant to restage JCL for a job with STAGE=NO. This would be for purposes ofchanging it due to a rerun condition. You use the RESTAGE operatorcommand to accomplish this. Keep in mind that it will overlay any JCL thatmay already be in the staging file for the respective job.

Once the JCL is staged, you can use a variety of editor commands to prepare itfor submission. In addition to usual text editing, you can perform somespecial functions within the editor:

■ Expansion of Unicenter CA-Driver procedures embedded in the JCL■ Display of current values of all Unicenter CA-Driver reserved-name

variable parameters in the JCL■ Change of values of any Unicenter CA-Driver reserved-name variable

parameters in the JCL



Using these functions together is a convenient way to write and test UnicenterCA-Driver procedures to automate JCL setup and minimize the need to stageJCL. For detailed explanations of these functions and all of the editorcommands, see the appendix "Editor Commands" in the Unicenter CA-SchedulerReference Guide Part 2.

The JCL that is staged is purged from the staging library when its associatedjob is purged from the tracking file. JCL that is stored in either a DOS sourcestatement library, a DOS procedure library, or Unicenter CA-Driver procedurelibrary is not fully expanded in the staging file. The staged version of thesejobs will contain the JECL and *$$SLI, // EXEC PROC, or // PROC,respectively.

Do not use STAGE=YES for jobs that have their JCL stored in an AllFusionCA-Panvalet library.

6.1.2.4 When Is a Job Submitted?

Once a job's EARLIEST START TIME is met, all of its predecessors havecompleted normally, and its resources (volumes, SEPARATE DSNAMEs, andSEPARATE JOBS) are available, then a job can be submitted.

6.1.2.5 What Are Global Parameters and When Are They Used?

Global parameters are user-defined conditions that are predecessors. You canspecify that a schedule or job must wait for a specific global parameter to beset to a specific value before the respective schedule or job can be started orsubmitted.

There are three types of global parameters: numeric, binary (yes or no), andalphanumeric (up to eight characters). Global parameters follow the format:

GBLxnn=value

x= A if the value is a number from 1 to 99999999B if the value is Y or NC if the value is up to 8 alphanumeric characters

nn = a number from 1 through 16

An example follows. Suppose there is a set of jobs that cannot start without aparticular set of tapes arriving from an off-site location. Suppose this is someaccounting data and you give it a name of HERE-NOW. You have to pick aglobal variable to be set aside for just this purpose. Suppose you chooseGBLC4 because you know no one else is using it. Any schedule or job thatneeds the data before it can run will have as part of its criteria language thefollowing string of data:

GBLC4=HERE-NOW

Chapter 6. Tips 6-7


Once the tapes have arrived, an operator sets the value of the global parameterGBLC4 to HERE-NOW. At that point, if any schedule or job is waiting for noother reason but this variable, then the schedule will be started or the job willbe submitted.

It is very important to notice that global parameters are not resetautomatically. Someone must cause it to happen. Their values are saved on thetracking file and always remain until they are reset to some other value or thetracking file is reinitialized. Autoscan does not reset the global parameters.

A review of all the ways you can set, reset, and define global parametersfollows.

When you initialize the tracking file, all global parameters are set to zero (forA-type), NO (for B-type), or null (for C-type).

If you want to see the current values of the global parameters, go into theOnline Monitoring panel and enter 6,D. The general Unicenter CA-SchedulerCommand Processor panel will be displayed with all of the global parametervalues. Another way to see the current values is to issue an operator commandGBL to display all defined global parameters, or GBLA for the numeric ones,or GBLB or the YES/NO ones, or GBLC for the character ones.

To assign a value to a global parameter, you also go to the Online Monitoringpanel. Once there, enter 6,GBLxnn=value. You never really reset a value; youtype a new value each time. Another way to set global parameters is to usethe operator command SET GBLxnn=value. For example, SET GBLC1=SHIFT1to mark the start of a specific shift. Another example, SET GBLC16=TP1HEREto mark the arrival of a tape.

When you define the criteria for a schedule or job, you can specify whichglobal parameters and what values they are to contain for use as predecessorconditions that have to be met before the schedule can be started or the job canbe submitted.

There is one rule you have to be sure to follow: a NOT reserved wordpreceding a GBLxnn predecessor is NOT recognized. Therefore, NOTGBLC01=CICS-UP will have the same affect as GBLC01=CICS-UP.

6.1.2.6 How Can I Run a Job Like an Edit Check Repeatedly until Its Output IsCorrect?

This is a situation where you want to keep running a job over and over againuntil you get an indication that the rest of the application can run. You maynot know how many times it will take each day, since it depends oneverything being valid. There are two ways to achieve this type of processing:

■ Using the INTERRUPT field on the job base record■ Using Auto-Reply processing.



To allow a job to be interrupted, you specify INTERRUPT=YES in its JobDefinition panel which means that when the job terminates normally, its statuswill be set to INTRPTD instead of ENDED. You can then run the job by usingthe RERUN command. Successors of this job will not run until the job is endedmanually using the COMPLETE command.

At any time during the day, you can go into the Online Status panel (eitherfrom the Main Menu or from the Online Monitoring panel) and display all jobsthat are in an INTRPTD status so you can see any jobs that are interrupted.

When a job does get interrupted, you can have a message sent to up to fourusers. These users can be any user name, the master console ('OPERATOR'),or the Unicenter CA-Scheduler mailbox (MAILBOX). To do this, use the SENDINTERRUPT MESSAGE TO field in the job's Message Definition panel.

Remember that when a job is to be interrupted, it must be manually posted todo something next such as freeing successors to run. Either mark the job asENDED, or resubmit the job using the RERUN or SUBMIT command.Successor jobs are then handled appropriately.

AUTO-REPLY processing takes a predefined action in reply to a consolemessage associated with a job or schedule.

6.1.2.7 How and When Can I Display Documentation Automatically?

User documentation can be built according to whichever standards you want.It is done using full-panel editing facilities provided with UnicenterCA-Scheduler. Each documentation member in this documentation file isgiven an eight-character key and this along with the schedule name or jobname (and job number and station) comprise the name that is used to uniquelyidentify it. You can at any time, view this information by using theDocumentation Maintenance panel.

If the job has a documentation key defined, the contents of that documentationlibrary member will be printed as part of the forecast and simulationcomponents, if requested.

When defining a job using the Job Definition panel, you can specify a DISPLYKEY and a DISPLAY TIME. If the job is a CPU job (station 40), then the namein the DISPLY KEY field will have its documentation displayed on the masteroperator console at the time of day specified in the associated DISPLAY TIMEfield. This will happen automatically. If you do not use the DISPLAY TIMEfield, but a DISPLY KEY field is specified, the documentation members willdisplay at autoscan time.

If the job is a non-CPU job, the user starting the job will receive a messagetelling him that there is documentation associated with the job and the nameof the documentation member. The user can then display it. If the non-CPUjob is automatically started (AUTO START=YES), the message is sent to the

Chapter 6. Tips 6-9


users in the SEND START MESSAGES TO list defined on the job's MessageDefinition panel.

6.1.2.8 What Are My Options When a Job Abends?

In the next chapter, the separate topic Restart/Recovery Of Scheduled Jobs isdevoted to this topic.

6.1.3 Analyzing the DatabaseThis topic presents several questions you may have regarding analyzing thedatabase and gives you difinitive answers.

6.1.3.1 How Can I Prevent Predecessor Loops?

Predecessor loops are also called predecessor deadlocks. A predecessordeadlock exists when two jobs end up requiring that the other execute first.

For example:

JOBA requires JOBX to run first.JOBB requires JOBA to run first.JOBX requires JOBB to run first.

JOBX is a predecessor of JOBA, but cannot run until JOBB has ended. SinceJOBB will not run until after JOBA has ended, there is a deadlock.

Imagine how complicated this would be to resolve if there were a hundredjobs, each with many predecessors. It is difficult to detect a deadlock unlessyou use the Analyze Report.

To obtain the Analyze Report, run the Unicenter CA-Scheduler Utility program(CAJUTIL0) with the batch command ANALYZE. You can check specific jobsor schedules or you can give a range of jobs or schedules. For example, youcan analyze all schedules that begin with the first three characters PAY.Anytime you make significant changes to jobs or schedules, run this report toensure that your changes have not introduced deadlocks. You should produceit any time the criteria for a job or schedule is changed.

Instead of getting the comprehensive Analyze Report, you can use theLIST=NO operand to request that just the errors be reported.

The ANALYZE command can also be issued online from any of these panels:

■ Job Maintenance (SCHD-JM)■ Job Directory (SCHD-JD)■ Schedule Maintenance (SCHD-SM)■ Schedule Directory (SCHD-SD)



For details on how to issue ANALYZE online, see the topics AnalyzingSchedules and Analyzing Jobs in the chapter "Maintaining The Database."

Another way to detect deadlocks is to generate the Successor Chain List reporteither from batch or online in the Reporting Facility panel. This is especiallyuseful for dynamically ADDed jobs to make sure that the added job did notcreate a deadlock.

6.1.3.2 When Should I Run Forecasts?

The forecast function allows you to predict which schedules and jobs will beselected on a future date as well as providing a comprehensive set of reportsdetailing such.

When establishing a complex criteria for a schedule or job, run forecasting toverify the selection. You can do this by only including the schedules or jobsthat you desire. This would be the primary reason for running forecasting.

Another reason for running forecasting would be to obtain a hard copy of runbooks for a specific day, group of days, or schedules or jobs within a set ofdays. These run books contain job information obtained from the database andfrom documentation library members specified by the DISPLY KEY field.

6.1.3.3 When Should I Run Simulation?

The simulation function simulates the autoscan process and the manner inwhich jobs would run on the real system. Such things as job concurrency,resources, and predecessor constraints are taken into consideration. Simulationproduces a set of detailed reports showing when jobs will run and whetherthey will complete on time.

Normally, simulation is run to determine the affect of a new application on therest of the workload. This helps you determine in advance whether therequested frequency of running the application is viable. That is, if you findthat the new application cannot fit on Wednesdays without making a lot ofjobs late, you could try to run it on another day. It may turn out that it doesnot absolutely have to run on Wednesdays. The requesting department may beable to run it on Thursdays just as easily. You can make these decisions beforeestablishing policy and before finding that you do not have the resources tohandle it.

Simulation could also be run to determine the effect of adding new resourcessuch as tape drives or a faster CPU. By using the OVERRIDE RESOURCEcommand, you can add the new tape drives. Or by using the FACTOR=factorkeyword on the same commands, you can cause the simulation to change thecurrent average time for jobs to reflect the faster CPU.

You may also want to run simulation as part of normal daily production todetermine what is going to happen that particular day. It provides you with a

Chapter 6. Tips 6-11


plan of what to expect and when to expect it. When you do this, you canoptionally use the simulated start times as the early time of the jobs forsubmission. When you do, it ignores the early start time that you had on thedatabase.

6.1.3.4 How Do I Plan when To Run a New Application?

You first define your application completely. Temporarily set LIBTYPE =TESTLIB in schedule base records. Now run simulation (see the discussion ofsimulation preceding) with a ONLY command just for the schedules in thenew application. This will ensure that everything is the way you want it.

If you have backlogged jobs in the simulation, you may want to run theAnalyze Report to check for predecessor deadlocks.

Once everything looks correct, you can run the application in test mode withthe normal day's production and review its affect on the day's workload.

6.1.3.5 How Do I Verify a New Application?

There are four steps you should follow in verifying a new application.

Step #1 Analyze ReportThe Analyze Report provides a detailed audit of all informationpertaining to the schedules being requested. From this report,you have a complete list of everything that you keyed in for thenew application. You also get a set of error messages thatidentify predecessor/successor deadlocks as well as anyreferences to jobs, predecessors, datetables, and stations that arenot on the database. Review this report carefully. Sometimesyou may prefer to print just the errors using the LIST=NOoption.

To obtain this report, use the JCL described in the the topicReports in the Unicenter CA-Scheduler Reference Guide Part 2.

You can also obtain it by issuing the ANALYZE commandonline in the Job Maintenance (SCHD-JM) or ScheduleMaintenance (SCHD-SM) panel.

This example analyzes all schedules that begin with thecharacters "APPLIS."

// JOB ANALYZE

// EXEC CAJUTIL�,SIZE=48K

ANALYZE SCHEDULE NAME=APPLIS�

/�

/&

Step #2 ForecastRun the forecast component for at least a month of dates andobtain the Job Summary Report (SUMMARY). You do this forthe schedules that were built for the new application. Through



use of the ONLY command, only the new schedule names aresupplied causing just the new application to be analyzed.Through use of the FORECAST command with the object ofSUMMARY, you will obtain just the Job Summary Report. Thefollowing example contains three schedules to be selected over aone month period with only the Job Summary Report beingproduced.

// JOB FORCAST

// EXEC CAJUTIL�,SIZE=48K

ONLY SCHEDULE N=APPL1S1�



FORECAST SUMMARY MONTHOF=�795

/�

/&

Step #3 SimulationRun the Simulation component for each unique day on whichthe new application will run. During a month, this may only bethree days: a daily, a weekly, and a monthly.

You would use the ONLY and SIMULATE commands toaccomplish this.

You want to verify that the jobs were selected on the days onwhich you intended them to be. Then you want to verify thatthey were scheduled in the proper sequence: predecessorrelationships are properly followed. If you have jobs that arebacklogged, there is a good chance they may have a predecessordeadlock. Also, if jobs are backlogged, check the accuracy ofearly start times and run times.

Step #4 Test Run the schedule in test mode. Use the online tracking RUN Scommand with the DATE=date keyword for each unique day onwhich the new application will run.

Use the STATUS command to verify that jobs are scheduledcorrectly, on those dates, and with the correct predecessors.Keep in mind that since LIBTYPE=TESTLIB, UnicenterCA-Scheduler will submit jobs that execute the CAJUTSTA testprogram. You can use TESTPARM=testparm on individual jobsto cause the test program to abend, to pass a nonzero returncode, and to have it wait for a number of seconds. By doingthat, you can test the effect of abending and failing jobs on therest of the schedule.

After the jobs in the schedule run to your satisfaction, you cannow alter LIBTYPE=TESTLIB, in the SBR, to your productionLIBTYPE. Also make sure that AUTO SELECT is set to YES.Once you do that, the schedule and its jobs will be automaticallyselected, starting at the next AUTOSCAN.



6.1.3.6 Is There a Way that I Can Create My Own Reports?

As part of Unicenter CA-Scheduler you have a component called AdvantageCA-Earl. Advantage CA-Earl is a generalized report writing facility for whichyou are provided a set of sample reports. This sample set of reports includesreporting on:

Database History file Tracking file Documentation file

JCL Staging library

The source code for these Advantage CA-Earl reports is provided to you. Thefollowing lists the reports and the names of the source members in which thesource is contained.

Although each of the preceding reports is written in Advantage CA-Earl andprovided for you, you have the ability to tailor any of them to your ownneeds. The topic Reports in the Unicenter CA-Scheduler Reference Guide Part 2describes each of these samples in detail. Also, the appendix "AdvantageCA-Earl Reports in the Unicenter CA-Scheduler Reference Guide Part 2 describes

Database CAJINM01 Basic job information by scheduleCAJINM02 Basic job information by stationCAJINM03 Job criteria by schedule

History file CAJINH04 Abended job profileCAJINH03 Completed job profileCAJINH07 Forced and canceled jobsCAJINH05 Late job profileCAJINH06 Pending job profileCAJINH01 Scheduled job status by scheduleCAJINH02 Scheduled job status by station

Tracking file CAJINT04 Abended job profileCAJINT07 Cancelled jobsCAJINT03 Completed job profileCAJINT06 Pending job profileCAJINS06 Pending schedules reportCAJINS01 Schedule statusCAJINT01 Scheduled job status by scheduleCAJINT02 Scheduled job status by station

Documentation CAJIND02 Documentation directory and list libraryCAJIND01 Documentation directory listCAJINTD1 Documentation with the tracking file

Staging library CAJING02 Staged JCL directory and listCAJING01 Staged JCL library directory list



other Advantage CA-Earl members that are used in producing the precedingreports and that you may need for any reports that you build.

6.1.4 Daily ProcessingCommonly asked questions concerning daily processing follow.

6.1.4.1 From Where Can I Issue Unicenter CA-Scheduler Operator Commands?

There are quite a few operator commands provided within UnicenterCA-Scheduler. They do everything from displaying status to shutting downScheduler. For detailed information about using these commands, see thechapter "Controlling Schedules and Jobs" in the Unicenter CA-SchedulerReference Guide Part 1.

There are, however, a number of different places where you can enter theoperator commands. This is done to make it practical for you.

Online Monitoring panelWhen you are on the Online Monitoring panel, the operatorcommands that can be used for schedules and jobs are listedunder the headings SCHEDULE COMMANDS and JOBCOMMANDS, respectively. If you want to issue one of thecommands you must enter the number that appears next to iton the command line (===>). You may enter keywords byseparating them from the number and from each other withcommas. If you run out of room to enter keywords, follow akeyword=value combination with a comma and press Enter.Another panel will then be displayed to allow the entirecommand to be entered.

Online Status panelWhen you display status using the Online Status panel, asubsequent panel is displayed with the data requested. It iscalled the Schedule Command Processor panel. It is on thispanel that you can issue operator commands that pertain toschedules and jobs.

Issue the commands by moving your cursor to the left of aschedule or job and enter an abbreviation of the command.For example, enter CANC for CANCEL. You can enter asmany commands on one panel as you need. See the chapter"Online Monitoring" for a list of the command abbreviations.

When you use this method, you cannot use optionalkeywords, only the command.

Be careful when you position your cursor. It is easy to put iton the wrong line. You could end up cancelling a scheduleinstead of a job, or cancelling the wrong job.



Operator ConsoleAny operator command can be issued from the operatorconsole by directing it to Scheduler. Prefix the command withSC followed by a blank space.

Batch Program (CAJUCMD0)Operator commands can be issued from a batch programcalled CAJUCMD0 which means that you could embed a stepcalling this program in your production JCL that could takecertain actions dependent on, for example, condition codesettings. Since you have the ability to cause any Scheduleroperator command to be issued, you could send messages tospecific users or the operator console, you could start anotherjob, or you could set global variables.

You can even issue these commands based on conditionscoded in an IF statement. You can test against the status ofother jobs, any schedule, user-defined globals, and manyothers. The subtopic Issuing Online Operator Commands InBatch Mode in the chapter "Techniques" describes this indetail.

6.1.4.2 What Is the Difference Between FORCE, SUBMIT, RERUN, RUN, ADD,REQUEST, and SREQ?

Each of these commands causes a job or schedule to be activated in some form.The following describes how each command works.

FORCE Causes a schedule on the tracking file to be started regardlessof why it is currently waiting. It also can cause a job to besubmitted regardless of why it is currently waiting.

SUBMIT and RERUNCause a job to be resubmitted. It will not wait for an earlytime or for predecessors: it is submitted immediately. If theschedule that owns the job is not in START status, it will beset to START status. Use RERUN or SUBMIT instead ofFORCE when a job has abended, failed, ended, canceled, orbeen interrupted. FORCE is used to make a job start the firsttime. RERUN substitutes Unicenter CA-Driver restartparameters if LIBTYPE=DRIVER is defined and the JCL is notstaged or restaged. The only difference between SUBMIT andRERUN is the Unicenter CA-Driver parameters they use:SUBMIT uses the normal parameters while RERUN triggersthe restart parameters.

RUN Causes a schedule or job that exists on the database to beadded to the tracking file. These schedules and jobs are onesthat were not selected in today's workload or they may havebeen canceled or completed. This is different than FORCE andRERUN in that a fresh copy is obtained and all times,predecessors, and resources are properly evaluated.



If the job or schedule is already on the tracking file (it wouldbe in a completed or canceled status), the older one is purgedfrom the tracking file. If the job is on the tracking file and notcompleted or canceled, then the RUN command is in error.With the RUN command, you can place the schedule or job ina HELD status. This will give you a chance to take any othermanual actions you deem appropriate. Further, when you usethe RUN command to pull in a schedule, you can give it adate so that only applicable jobs in the schedule are selected.

ADD Causes a job to be added to the tracking file. The job does nothave to be on the database. If it is on the database, you woulduse this command instead of the RUN command if youwanted to change any keyword values. Normally, you onlyuse ADD for one-time jobs.

You do not have to specify a schedule name. If you do, it willbe added to that schedule. If you do not specify a schedulename, it will use a schedule name of $DYNx, where x is thePOWER SYSID of the system from which the command wasissued.

REQUEST and SREQCause a REQUESTED schedule or job to be activated whichmeans it is moved from the inactive queue to the activequeue. Once in the active queue, it is handled normally.

The way that a schedule or job is made 'on-request' is bygiving it a selection criteria of REQUESTED. A REQUESTEDcriteria causes the schedule or job to be selected every dayand placed on the tracking file.

The difference between REQUEST and SREQ is that, withREQUEST, the REQUESTED schedule or job is moved to theactive queue along with all its successors. The SREQcommand handles successors differently: SREQ will notactivate a successor if it involves other requested jobs. Asuccessor of an SREQed schedule or job will not be moved tothe active queue if:

The successor's criteria statement contains the keywordREQUESTED orThat successor is also the successor of some otherrequested job in the inactive queue

There is a separate subtopic devoted to requested jobs in thenext chapter. If you plan to use this facility, you shouldreview the subtopic on REQUESTED work.



6.1.4.3 Summary

For jobs in the tracking file:

■ Use RERUN or SUBMIT for jobs that ended abnormally or were canceled.■ Use FORCE to submit jobs if you are willing to violate their reasons for

waiting.■ Use requested or SREQ for requested jobs.

For jobs not on the tracking file:

■ Use ADD to put a job on the tracking file if it does not exist on thedatabase or if it is on the database, but you need to change its keywords.

■ Use RUN to submit jobs in the database if you do not need to change theirkeywords.

6.1.4.4 When Is the PRED Flag Reset?

When you use the PRED keyword in the criteria language, it indicates that theschedule or job is to wait for a predecessor to complete. When you do not usethe keyword PRED, the predecessor is to complete within the autoscan day.

When you specify PRED in front of the predecessor, it means the predecessorwas to have completed since the last time this schedule or job was run. Thereis an exception, however. If the PRED is a schedule or job that is in today'sworkload, it will wait for that specific one to complete. For example, if a jobhas a predecessor of PRED DSN JOBA.MASTER, the output data setJOBA.MASTER must have been closed at least once between each running ofthat job. If the job is run weekly, then it must have been closed at least onceduring the last week.

Normally in the selection process (during autoscan), job names cause selectionif the predecessor job was selected. When PRED precedes a schedule name orjob name, it is not used in determining selection, but is a predecessor conditiononly. All other criteria rules still apply.

6.1.4.5 What Happens If There Was a System Crash?

The following discussion is appropriate to a system crash or if UnicenterCA-Scheduler does not complete normally.

Unicenter CA-Scheduler is able to recognize whether a clean shutdownoccurred. When a clean shutdown did not occur, upon starting back up,Unicenter CA-Scheduler does the following based on the status of the job atthe point Unicenter CA-Scheduler was last active:

Status At Failure Sets New Status To

STARTED UNKNOWN - The job may have to be rerun, butrequires investigation by a troubleshooter.



Once Unicenter CA-Scheduler has set all of the preceding status codes, it is upto you to review the jobs and rerun appropriate jobs, mark current status onothers, and ensure the current status of each is correct. To see the status of thejob prior to the outage, use the HELD, AND WHEN option on the OnlineStatus panel. A lot of jobs will be left with a status of AUTO RECVRY HELD.To restore their status to what it was at the time of the system crash, issue thecommand:

RELEASE AUTO

These remaining jobs will be handled as if they had RECOVERABLE=YESspecified on their Job Definition panel.

Everything should now be back to normal.

Status At Failure Sets New Status To

SUBMITD Unicenter CA-Scheduler issues the POWER command todetermine if the job is in the POWER queue. If the job isnot in the POWER queue, it is placed in a status ofUNKNOWN. If the job is in the POWER queue,Unicenter CA-Scheduler issues the POWER command toplace the job on POWER HOLD and then places the jobin a status of AUTO RECVRY HELD ifRECOVERABLE=NO on the Job Definition panel. IfRECOVERABLE=YES was specified and the job is in thePOWER RDR queue, the job is released and ready torun.

WAITINGanything

As long as a job was waiting for any reason, it is placedin a status of AUTO RECVRY HELD if the job wasdefined with RECOVERABLE=NO. If it was definedwith RECOVERABLE=YES, it will take on the lastknown status and be reevaluated (for example, it maynow meet its early start time). This ensures that youhave time to review it.


6.2 Pitfalls

6.2 Pitfalls

This topic discusses some of the pitfalls you may encounter.

6.2.1 Using Operator Commands on the Status Display PanelYou are able to issue operator commands from a status display by just keyingin the command (first four characters) to the left of the schedule or job. Youcan even issue more than one command at a time.

Pitfall: When keying in a command to the left of a schedule or job in theOnline Status Display, be sure you are on the correct line. It is easyto cancel the wrong job.

While on the subject of operator commands in status displays, here is aclarification, not a pitfall. Remember, when using the commands in thismanner, that they are processed sequentially and stop being processed uponencountering an error. For example, there is no reason to cancel a schedule andthen the jobs in that schedule.

6.2.2 Cancelling and Purging a JobSuppose you have a schedule that consists of four jobs: JOB1 through JOB4.JOB2 requires JOB1; JOB3 requires JOB2; and so on. If you CANCEL JOB3,whether you also PURGE it, JOB4 will always wait for JOB3. You canmanually override this with a POST or FORCE command.

Suppose that JOB3A has JOB3 as a predecessor. If JOB3 is canceled and notpurged, the predecessor JOB3 is ignored when you issue a RUN JOB3Acommand because JOB3 has been canceled but is still on the tracking file. Ifyou purge JOB3 before issuing the RUN JOB3A command, JOB3A waits forJOB3 to complete. You have to RUN JOB3 to put JOB3 back on the trackingfile.

Do not use the PURGE command unless you plan to put the job back on thetracking file by issuing a RUN command.

Pitfall: Predecessors for jobs added to this day's production using the RUNcommand are ignored if they have been canceled by the CANCELcommand but not deleted from the tracking file by the PURGEcommand.

6.2.3 Changing Criteria on Selected JobsWhen a schedule or job has been selected, Unicenter CA-Scheduler reviews itspredecessor criteria as it exists on the database. What this means is that if youhave a schedule of four jobs: JOB1, JOB2, JOB3, and JOB5, where JOB2 requiresJOB1, JOB3 requires JOB2, and JOB5 requires JOB3. The schedule has beenselected and is on the tracking file. You then add JOB4 and change the


6.2 Pitfalls

predecessor criteria of JOB5 to now also require JOB4. If JOB5 had not yetstarted, when it is evaluated to start, it will require JOB4, but JOB4 was neverselected. Therefore, JOB5 will never be submitted. It will always be awaitingJOB4. If this happens, we recommend that you CANCEL and PURGE JOB4and then issue an ADD command for JOB4.

Pitfall: When changing predecessor criteria on the database for jobsthat are selected and are already on the tracking file, be awarethat the jobs on the tracking file will be evaluated based onthe most current data on the database. Do not change thecriteria of active jobs.

6.2.4 Backlogging Over Two AutoscansThe subject of backlog is covered in the topic Backlogged Work in the chapter"Techniques." When a schedule gets backlogged (autoscan occurred before theschedule completed) due to the first autoscan occurring, it is handled as youwould expect. If, however, it does not finish before the next autoscan (meaningit has been in the system for 48 hours), when it does finish, the new schedulethat is loaded is evaluated for the autoscan day on which it is loaded whichmeans that if a schedule that is selected on both Monday and Tuesday and hasits Monday's version backlogged until Wednesday; Tuesday's version willnever be run. That is because the evaluation takes place when Monday'sschedule completes, which is Wednesday, but it does not run on Wednesday.Always watch backlogged work carefully.

Pitfall: Backlogged work that goes beyond a 48-hour period can belost if not monitored carefully.

6.2.5 Resetting Global ParametersGlobal parameters are initialized only when the tracking file is initialized. Theyare not reset at autoscan time. Once a value of a global parameter is set, it isonly reset when someone actually changes its value to something else. That is,predecessor evaluation of schedules and jobs takes place based upon thecurrent value of the global parameter regardless of when that value is set.

If the preceding is not the way in which you desire to operate, you could havea batch job that is submitted at a specific time (say immediately followingautoscan) that executes the Unicenter CA-Scheduler program CAJUCMD0 andsupplies transactions that set the global variables to the values you want.Therefore, the pitfall:

Pitfall: A global parameter only gets set. If you want it reset, youmust set it to another value. There is no such thing asresetting a global parameter.

Once a global parameter is set to a specific value, all unsatisfied predecessorsare reevaluated. If any schedules or jobs are waiting for that global parameterto take on that value, those global predecessors are marked as satisfied.


6.2 Pitfalls

Satisfaction can only be reversed by changing the GBLxnn parameter andcancelling the affected schedule or job and then issuing a RUN command toreselect that schedule or job.


Chapter 7. Techniques

This chapter of the manual is intended to clarify various topics withinUnicenter CA-Scheduler. In some instances, techniques are discussed while inother cases, the topic resembles a tutorial. Each topic stands on its own so youcan jump from topic to topic. Do not be concerned about reading these topicsin the order they are presented.

Chapter 7. Techniques 7-1

7.1 On-Request Schedules and Jobs


This topic discusses on-request schedules and jobs and gives you manyexamples of criteria language.

7.1.1 DiscussionOn-request schedules and jobs are ones that are selected every day, and placedin an inactive queue, in case they are needed. They remain in an INACTIVEstatus until they are activated by an operator command which means that youcannot determine in advance whether the schedule or job will be needed onany particular day.

You define an on-request schedule or job using REQUESTED, a Gregoriancalendar reserved word, in its selection criteria.

When the autoscan process runs, all REQUESTED schedules and jobs areselected along with their successors and placed in Unicenter CA-Scheduler'stracking file in an inactive queue. The only way they can be removed from theinactive queue is using the operator command REQUEST or SREQ. Whenremoved from the inactive queue, they are placed in the active queue and willthen be handled as normally selected jobs.

An important difference between the REQUEST and SREQ commands is thatREQUEST also places the successor schedules and jobs in the active queue.The SREQ command handles successors differently: SREQ will not activate asuccessor if it involves other requested jobs. A successor of an SREQedschedule or job will not be moved to the active queue if:

■ The successor's criteria statement contains the keyword REQUESTED or■ That successor is also the successor of some other requested job in the

inactive queue

All schedules and jobs that have not been requested by the next autoscan arepurged from Unicenter CA-Scheduler's tracking file, regardless of whichBACKLOG values they had defined.

There is a guideline you should follow when using the REQUESTED keyword:To ensure that simulation produces reason codes that match those producedby Unicenter CA-Scheduler, specify REQUESTED after job and schedule namesin selection criteria whenever possible.



7.1.2 Criteria Language SubtletiesThe best way to explain these subtleties is with examples. Each exampleassumes that the jobs described are all contained in the same schedule.

Although you should always specify schedule names with job names in criteriastatements, they are omitted in the examples following to keep things simple.

7.1.2.1 Example 1

In the preceding example, all three jobs will be placed in the inactive queueevery day.

Job Criteria

JOBA REQUESTED

JOBB JOBA

JOBC JOBB

7.1.2.2 Example 2

JOBA will be placed in the inactive queue every Monday.

Job Criteria

JOBA MON AND REQUESTED

7.1.2.3 Example 3

The preceding example follows the same rules as MON when selected onMonday and treated as a normal job (meaning that on Mondays, it is placed inthe active queue and it does not have to be requested). Any other day, it willbe treated as a requested job.

Job Criteria

JOBA MON OR REQUESTED

7.1.2.4 Example 4

Job Criteria

JOBA REQUESTED

JOBA1 None

JOBB JOBA OR JOBA1



In the preceding example, all jobs will be selected. JOBA and JOBB will beplaced in the inactive queue. JOBB is placed there because JOBA is the firstpredecessor specified and it is a requested job. The ordering of thesepredecessors is important as you will see with the next example.

JOBA1 will be run whenever its conditions allow (if there are none, it will startimmediately).

JOBB will always wait for JOBA1 (that is, you could request JOBB withoutrequesting JOBA). If JOBA is requested (with the REQUEST or SREQcommand), JOBB will automatically be requested and will wait for both JOBAand JOBA1.

If no requests are made, JOBA and JOBB will be purged from the tracking fileat the next autoscan.

7.1.2.5 Example 5

The preceding example is the same as the one previous except for the order ofthe predecessors on JOBB. All three jobs will be selected, but only JOBA isplaced on the inactive queue. This is because JOBB got selected because ofJOBA1, which is selected whenever the schedule is selected.

JOBB will always wait for JOBA1, but will only wait for JOBA if JOBA isrequested (using the operator command REQUEST or SREQ) before JOBA1completes.

If JOBA is not requested, it will be purged from the tracking file at the nextautoscan.

Job Criteria

JOBA REQUESTED

JOBA1 None

JOBB JOBA1 OR JOBA

7.1.2.6 Example 6

Both JOBA and JOBB will be placed in the inactive queue at autoscan time.

Job Criteria

JOBA REQUESTED

JOBB JOBA AND REQUESTED



When the operator command REQ J N=JOBA is issued, both jobs (JOBA andJOBB) will be moved to the active queue.

When the operator command SREQ J N=JOBA is issued, only job JOBA will bemoved to the active queue. JOBB will not be moved since it has the criteriaAND REQUESTED that must be satisfied. It is not satisfied using the SREQoperator command with its predecessor JOBA. To move JOBB to the activequeue, in this case, use the REQUEST or SREQ command.

7.1.2.7 Example 7

On Mondays, JOBB will be added to the active queue and will not wait forJOBA unless it is also in the active queue. That is, JOBA will not be considereda predecessor of JOBB unless JOBA is requested with the REQUEST or SREQcommand before JOBB is submitted. Once JOBA and JOBB are both in theactive queue, Unicenter CA-Scheduler will not submit JOBB until JOBA hascompleted.

Job Criteria

JOBA REQUESTED

JOBB MON OR JOBA

7.1.2.8 Example 8

All four jobs will be placed in the inactive queue at autoscan time.

Job Criteria

JOBA REQUESTED

JOBA1 REQUESTED

JOBB JOBA OR JOBA1

JOBC JOBA



When the operator command REQ J N=JOBA is issued, JOBA, JOBB and JOBCwill be moved to the active queue. This occurs with JOBB and JOBC sinceneither of them are requested jobs, but rather each of them only require JOBAto be selected. If JOBA1 were the requested job, then JOBA1 and JOBB wouldbe the ones moved to the active queue.

When the operator command SREQ J N=JOBA is issued, JOBA, JOBB, andJOBC will be moved to the active queue having the same result, in this case, asissuing the REQUEST command.

7.1.2.9 Example 9

All five jobs will be placed in the inactive queue at autoscan time.

This example closely resembles Example 8. Following is what happens whenthe SREQ command is used with JOBA. In this case, JOBB will still be movedto the active queue, but JOBC and JOBD will not. That is because JOBC'scriteria includes the REQUESTED keyword, and JOBA1 (JOBD's predecessor)was REQUESTED. Issuing the command SREQ JOBC will move JOBC to theactive queue. To move JOBD to the active queue, SREQ both JOBA andJOBA1.

Job Criteria

JOBA REQUESTED

JOBA1 REQUESTED

JOBB JOBA OR JOBA1

JOBC JOBA AND REQUESTED

JOBD JOBA AND JOBA1

7.1.2.10 Example 10

Both these jobs are in a schedule called SCHDA. SCHDA has a criteria ofREQUESTED. At autoscan time both JOBA and JOBB will be placed in theinactive queue.

Job Criteria

JOBA NONE

JOBB REQUESTED



When the operator command REQ S N=SCHDA is issued, JOBA and JOBB willbe moved to the active queue.

When the operator command SREQ S N=SCHDA is issued, only JOBA will bemoved to the active queue.


7.2 Backlogged Work

7.2 Backlogged Work

There will be times when schedules or jobs will not complete the day on whichthey were selected which means that they may be candidates for beingbacklogged, but first, define what a day is.

In terms of your company, a day would be your normal daily businesscomputer cycle. For example, production work starts at 16:00 and is to becompleted by 08:00 the next morning. This is fairly typical which means yourun autoscan at, or shortly after, 08:00 (to select schedules and jobs for the next16:00 to 08:00 time period). Thus, in terms of Unicenter CA-Scheduler, a day isthe 24-hour period that starts with the time that you run autoscan. This istermed the production day or autoscan day.

Schedules and jobs that do not complete on the production day on which theywere selected can be carried over to the next production day. They are thencalled backlogged schedules or jobs. When you define a schedule or job to thedatabase, specify whether that schedule or job is a candidate for backlog.Normally it is.

What happens if the work for a production day is not complete is nextdescribed.

Job Backlog The normal situation allows schedules to be backlogged.When autoscan is initiated and it is determined that aschedule is still active (it has not finished running yet),the schedule will be backlogged. Any job in the schedulethat has completed, been canceled, or purged will retainits status. If a job has been defined withBACKLOG=YES, it will be backlogged if it had notstarted. That is, it will be allowed to run. If a job in thebacklogged schedule has been defined withBACKLOG=NO and still has a status of WAITING, itwill be canceled with a status called NO BACKLOGCNCL.

Once all jobs in the backlogged schedule have beencompleted or canceled, the schedule will be marked ascomplete. If the same schedule was also selected on thecurrent production day, then it and its associated jobswill be placed on the Unicenter CA-Scheduler trackingfile and processed as if it had been selected normally.

If a daily schedule gets backlogged for greater than 24hours (that is, it is backlogged by two autoscans), thenwhen it completes, the schedule to execute on thecompleted day is loaded to the tracking file. Forexample, if Monday's schedule gets backlogged and


7.2 Backlogged Work

completes on Wednesday, Tuesday's schedule will neverbe run.

Schedule Backlog When BACKLOG=YES or NO is specified on a scheduledefinition, it acts only as a default for jobs in thatschedule when BACKLOG is not specified on a job.Then it is handled as described in the previousparagraph under the caption Job Backlog.

Requested Jobs

And Schedules Jobs and schedules that are ON-REQUEST and are stillin the inactive queue at autoscan time will be purged,regardless of their BACKLOG value.

7.2.1.1 In Summary

NO BACKLOG CNCL is a status code that means the job was canceled at theend of the day because it had not yet started and it was defined as, ordefaulted to, BACKLOG=NO. The jobs carrying this status have not yet startedand will not be run. As soon as the schedule ends, they will be purged.

When history is generated for these NO BACKLOG CNCL jobs, they will showup on the Pending Job Profile Advantage CA-Earl report for the currentproduction day.

When a schedule is backlogged and it is also to be selected for the currentproduction day, the one being selected will not be placed onto the UnicenterCA-Scheduler tracking file until the backlogged one completes. Only one copyof a schedule at a time will be kept on the tracking file. Therefore, if for somereason a schedule occurs daily and is backlogged twice, the schedule for themiddle day would never be brought in. Another example is that if a scheduleruns Monday and Tuesday only, and Monday's schedule gets backlogged untilWednesday, Tuesday's schedule will never be run. This is because whenMonday's schedule finishes and Tuesday's is brought in, it is evaluated forWednesday. Since there is nothing in this schedule to run on Wednesday, itwill never get started.


7.3 Issuing Online Commands in Batch


A utility program (CAJUCMD0) is provided with Unicenter CA-Scheduler thatallows you to:

■ Send operator messages to system console■ Issue Unicenter CA-Scheduler operator commands■ Issue VM commands (if you are running under VM)■ Issue POWER commands■ Issue CICS CEMT commands or start user transactions

When you combine the facility with some language flexibility, you haveconsiderable power. For example, you could test the condition code of a stepin the middle of a job and based on its setting cause some other job orschedule to be released to run. Or if a particular job was submitted before thisjob, you could place some other job on hold. There are a whole set of statusconditions that you can check. These are described later.

A more detailed discussion on the format and use of this facility exists in thechapter "Unicenter CA-Scheduler Commands in Batch Mode" in the UnicenterCA-Scheduler Reference Guide Part 1.

7.3.1 Transaction FormatThere are six types of transactions, you have to tell the CAJUCMD0 programwhich type you are describing which you do by prefixing each transactionwith a two-digit code as follows:

Prefix Transaction Type

MO Send the following text to the operator console.

SC Issue the following Unicenter CA-Scheduler operatorcommand, which can include the conditional batch IFstatement.

CP Issue the following VM command.

PW Issue POWER commands.

CI Issue CICS Transactions.

DM Issue commands stored in the documentation library.



The preceding commands can be executed conditionally based upon the settingof a global parameter or the status of a schedule or job. This introduces the SCtransaction that is used with the IF statement. The IF statement can even haveAND, OR, and NOT keywords. For example:

Transaction:

SC IF JOBA INTRPTD SC STATUS S=PAYSCHD

Read as:

The job that is executing CAJUCMD0 right now wants to determine if the jobJOBA is in an interrupted status. If it is, Unicenter CA-Scheduler will print thestatus of the schedule PAYSCHD and all its jobs.

The following describes using the NOT keyword.

Transaction:

SC IF JOBA NOT COMPLETE SC HOLD J N=JOBB

Read as:

The job that is executing CAJUCMD0 right now wants to determine whetheror not JOBA completed. If it has not, Unicenter CA-Scheduler will place JOBBin HELD status.

7.3.2 Status CheckingIn the previous examples, the portion of the IF statement that reads JOBAINTRPTD and JOBA NOT COMPLETE is called a condition. There can bemore than one condition in an IF statement. In this case, they would beseparated by an AND or an OR keyword. If the condition pertains to aschedule or job, the right-hand part of the condition is the status to checkagainst. If you are looking at a global, the right-hand part is the value of theglobal you want to check.

There are two levels of status codes. The major level is a code such asINTRPTD or COMPLETE (as in the previous examples). This is termed themajor status code. There are some major status codes that can be optionallyqualified with a minor status code. An example of a major status code with aminor status code would be WAIT PRED. WAIT is the major status code andPRED is the minor status code. One example is asking if a schedule or job is ina WAIT status for predecessors. Another example is WAIT START, which isasking if a schedule or job is waiting for its early start time to be met.



To have an appreciation for the flexibility of this capability, all of the differentstatus codes are listed in the following tables.

Major Minor Description

ABENDED

CC=dd

The job abended.

The job abended with a completion code ofX'dd' (for example, X'FF').

ACTIVE The schedule or job is active in the system.It is not necessarily running, but it is noton HOLD.

CANCEL

BACKLOG

OPER

The schedule or job was canceled:

It carried over to the next production dayas backlog

By an operator

COMPLETE The schedule or job ran to completion. Thisincludes abended, failed, and canceled jobs.(The status display indicates ENDED.)

FAILED CC=nnnn The job failed with a FAILCODE of nnnn

HELD

AUTO

OPER

The schedule or job was held:

Due to automatic recovery

By the Unicenter CA-Scheduler HOLDcommand

LATE

DEAD

MAX

MUST

The schedule or job caused a late messageto be issued because it:

Did not finish by the COMPLETIONDEADLINE time

Exceeded the MAXIMUM EXECUTIONtime

Did not start by the MUST START BY time.

INTRPTD The job was interrupted.

NOTREQ The schedule or job is in the inactivequeue.

STARTED The schedule or job is executing.

SUBMITD The job has been submitted.



Major Minor Description

SUBMFAIL The job was submitted, but failed.

WAIT

OPSUB

PRED

RESC

START

The schedule or job is waiting for:

Operator submission (jobs only)

A predecessor to be satisfied

Defined resources (jobs only)

Its early start time.

7.3.3 Some ExamplesThe following examples show how you might issue some commands in batch.

7.3.3.1 Example 1

Suppose you have an online application called NETSCD and when it is shutdown, you want to set an indicator that allows a set of backup jobs to beginprocessing. You can assign a global parameter to this function. Assume aglobal parameter GLBC4 and assign it a value of NETSCDUP when the systemis running, and the value NETSCDWN when the system is not running andbackups can be taken.

You would use the following transaction in one of the first steps when startingup the NETSCD task. This step would execute the CAJUCMD0 program.

SC SET GLBC4=NETSCDUP

This means that whenever the NETSCD task is running, the global parameterGLBC4 is set to a value other than NETSCDWN.

Now, when the system is shut down, one of the last steps is to set GLBC4 tothe value NETSCDWN, which will allow the backup jobs to be started. Thetransaction for the step that executes the CAJUCMD0 program will be:

SC SET GLBC4=NETSCDWN



7.3.3.2 Example 2

This example is a series of transactions and how they can be coded:

Transaction:

SC IF SCD PAYSCHD STARTED SC S S=NEXTSCHD

Read as:

The job that is executing CAJUCMD0 right now wants to determine if theschedule PAYSCHD has started. If it has a status of STARTED, the status ofthe schedule NEXTSCHD and all its jobs will be printed.

Transaction:

SC IF JOBA COMPLETE CC=10SC TALT S N=NEXTSCHD ERLYTIME=0900

Read as:

The job that is executing CAJUCMD0 right now wants to determine if the jobJOBA completed normally. If it did, the early start time of the scheduleNEXTSCHD will be altered to 9:00 a.m. in the morning.

Transaction:

SC IF GBLA01 NOT 5 SC GBL

Read as:

The job that is executing CAJUCMD0 right now wants to determine if thenumeric global parameter number 1 (GBLA01) contains a value other than five.If it does, a list of all current global values will be printed.



Transaction:

SC IF GBLC02 NULLMO REVIEW THE CURRENT GLOBAL

Read as:

The job that is executing CAJUCMD0 right now wants to determine if thealphanumeric global parameter number 2 (GBLC02) does not contain anyvalue. If there is no value, the console operator is notified to review the valuesof all of the globals.

Transaction:

SC IF JOBA-2 40 PAYSCHD WAIT START ANDGBLB16 YES SC S

Read as:

The job that is executing CAJUCMD0 right now wants to determine if the CPUjob JOBA with job number 02 (JNO) contained in schedule PAYSCHD iswaiting for its early start time and the 16th binary global parameter is set toYES. If so, a complete status of all schedules and jobs will be printed.


7.4 Restart/Recovery of Scheduled Jobs


This topic discusses methods of restarting and recovering scheduled jobs thatare defined in Unicenter CA-Scheduler's database and were selected as part ofthe day's production during the most recent autoscan process.

Recovery of jobs after a system crash is discussed in the chapter "Tips" withthe question What happens if there was a system crash? This includes thevarious Unicenter CA-Scheduler status settings.

Recovery of jobs as they pertain to a multi-CPU environment is discussed inthe topic Multi-CPU Considerations later in this chapter. That discussiondescribes how jobs can be moved as a group from one CPU to another whenone CPU goes down.

In this topic, it will be discussed how you determine which jobs have abended,what type of manual actions you can take, what type of automatic facilities areavailable within the Unicenter CA-Scheduler database, and then discuss howyou could use Unicenter CA-Driver to automate the recovery process.Unicenter CA-Driver is a component of Unicenter CA-Scheduler that providesa JCL handling facility.

7.4.1 Inquiring About Jobs to Be RecoveredFrom the Online Status panel (which you can get to from the Main Menu orthe Online Monitoring panel), you have a set of status codes from which youcan display jobs that might need recovery if they are not set up to recoverautomatically. The status codes that would indicate recovery may be necessaryinclude:

Status Code Description

ABENDED The job has abended with an abend code such asX'1A'. It can be rerun by using the RERUN orSUBMIT operator command.

OPERATOR CANCLD The job has been canceled by an operator using theCANCEL operator command. This job can be runagain by using the RUN, RERUN, or SUBMITcommand.

FAILED The job has failed with a condition code thatexceeds the value specified in the FAIL CODE fieldwhen defining the job or has failed on a JCL error.It can be rerun by using the RERUN or SUBMIToperator command.



To recover any job, its JCL is either in the staging library or can be placedthere by the RESTAGE operator command. Once it is in the staging library,you can modify it and resubmit the job.

7.4.2 Automatic Recovery OptionsWhen defining a job to the database, there is a field called ABEND, which canbe used to aid in automatic recovery of a job. There are four options you canspecify in this field. They include:

If a recovery schedule is defined, it could contain a job that executes theCAJUCMD0 program that allows you to interrogate various job's statusthrough batch commands. Based on the job status, other jobs could be broughtin with the RUN, REQUEST, or ADD operator commands for recovering theabended job. This technique is described in the preceding topic of this chapter.When you define a recovery schedule, you should attempt to use some sort ofnaming convention so that any recovery schedule can be recognized quickly.For example, begin all recovery schedule names with RR.

Another way to be sure that jobs that need recovery do not go unnoticed is touse the message facility. That is, you can specify up to four users to sendmessages to if the job abends or fails. Users are defined on the schedule andjob message records and can be operator consoles or the UnicenterCA-Scheduler mailbox. (See the topics Defining A Schedule Message Recordand Creating A Job Message Record in the chapter "Maintaining the Database"for more information.) Keep in mind that JCL errors for a job are treated as ifthe job failed.

Option Description

ABORT Indicates that successors to this job will not havethis predecessor satisfied. This is the default value.

CONT Indicates that successors to this job are to behandled as if the job terminated normally becausethis predecessor has been satisfied.

BACKOUT Indicates that successors to this job will not beposted as satisfied if this job abends. A backout jobwill be submitted automatically if you specified avalue for the BACKOUT installation option.Unicenter CA-Scheduler adds a new job trackingrecord for the backout job.

Schedule name Indicates that the schedule name provided is to beprocessed. This is a predefined recovery schedulethat will be automatically processed should the jobabend and the abended job will follow the sameprocess as ABORT.



7.4.3 Unicenter CA-Driver ConsiderationsImplementing a job step restart process is inherently complex due to all of thevariations of abend conditions. As with the implementation of any automatedsystem, the 'cure' should not cause more disruption than the problem.

For example, in a multi-step job, Step 5 abends. The determination is madethrough the automated process that exists today, that Step 5 relies on thetemporary data set that was created in Step 2. Therefore, the data sets thatwere created in Steps 2, 3 and 4 must be removed from the VSAM USERCAT.What cannot be determined through any automated process is that the data setcreated by Step 1 and used for input by Step 2 was created using incorrectinput. Herein lies the problem of automating the restart/recovery process.

There are many options available to a data center to effect properrestart/recovery. A more automated method can be achieved by usingUnicenter CA-Driver, an optional component of Unicenter CA-Scheduler/VSE.Unicenter CA-Driver is a powerful JCL and runtime management facility thatcan work hand-in-hand with Unicenter CA-Scheduler. You can define jobs toUnicenter CA-Scheduler that store their JCL with UnicenterCA-Driver-managed procedures. Unicenter CA-Driver controls the expansionof these 'procs' based upon values that you supply.

When defining jobs to Unicenter CA-Scheduler that find their JCL in Driverprocs, Unicenter CA-Scheduler will also ask you to define normal runtimeparameters and rerun runtime parameters. The normal runtime parameterswill be passed from Unicenter CA-Scheduler to Unicenter CA-Driver when it istime to submit the job. The panel (Unicenter CA-Driver restart parms)parameters will be passed from Unicenter CA-Scheduler to UnicenterCA-Driver whenever the job is being rerun using the Unicenter CA-SchedulerRERUN command. Thus, this facility gives you the flexibility to have yourUnicenter CA-Driver procs expanded differently depending on thecircumstances at the time.

Unicenter CA-Driver also provides you with the ability to test VSE completioncodes and return codes between steps of a job. The results of these tests can beused to execute steps of a job conditionally.

Unicenter CA-Driver is a very useful tool. To really get to know all of thefacilities of Unicenter CA-Driver and how they can be used, refer to yourUnicenter CA-Driver Reference Guide.


7.5 Multiple CPU Considerations


Unicenter CA-Scheduler, as you have seen throughout this manual, has a greatdeal of flexibility. When it comes to scheduling and controlling production onmore than one CPU, this flexibility continues to exist. In this topic, however,we are going to discuss the manner in which most shops use UnicenterCA-Scheduler in a multi-CPU environment.

First, you must get some basic IBM terminology out of the way. The termSYSID will be used throughout this chapter.

SYSID is the system identifier that uniquely identifies each of the VSEoperating systems that execute in your environment. This is established by thesystems programmer when generating each of the VSE operating systems. Attimes, the SYSID is referred to as the POWER SYSID.

You can allow POWER with shared spool to determine which CPU jobs runon. You do this through control of the CLASS designations. That is, if a job isto run in CLASS T, and there is a CLASS T on each CPU, then POWER willdetermine which CPU on which to run the job. There will be times, however,where you want a job to execute on a specific CPU (maybe it is the only placewhere a program can get to a specific database). In this case, you can directPOWER to execute the job on a specific CPU by specifying a RUN ON SYSIDvalue in the job base record.

If Unicenter CA-Scheduler is submitting your JCL from LIBTYPE=CMS, it maynot be necessary to generate POWER with shared spool. In this case, theUnicenter CA-Scheduler CMS service machine will do what non-shared powerspool cannot—route the JCL to the correct POWER SYSID. This can beaccomplished by creating a file that contains the POWER SYSID and the VSEguest machine name. The file has a filename of SCDSYSID and a filetype ofUSERID and must reside on a CMS disk that is accessible to the UnicenterCA-Scheduler CMS service machine. The Unicenter CA-Scheduler CMSservice machine will match the SYSID in this file with the RUN ON SYSIDvalue (SYSID=) in the job base record and submit the job to the correspondingVSE guest machine. There must be at least one blank between the POWERSYSID and the VSE guest machine name as follows:

1 VSEPROD1 2 VSEPROD2 3 VSEPROD3

Unicenter CA-Scheduler will generate the appropriate POWER JECL JOBstatement with the SYSID= parameter whenever a RUN ON SYSID is specifiedon the job base record.



7.5.1 Installation ConsiderationsWhen installing Unicenter CA-Scheduler, you have to indicate that it is goingto run in a multi-CPU environment which means that five things have to bedone.

1. You must code the parameter MCPU=YES in the CAIJGEN macro, whichindicates that you have a multi-CPU environment.

2. You must code the parameter SHARE=YES in the CAIJGEN macro. Thisspecifies that you are to share the Unicenter CA-Scheduler database andassociated files, which includes the database, the tracking file, the staginglibrary, and the documentation file and optionally the Unicenter CA-Driverprocedure library. This must always match the SHARE field on theFORMAT and RESTORE commands (see number 4, following). By usingthe SHARE database facility, you ensure the integrity of accessing thedatabases and libraries from different CPUs at the same time, which isdone with software (spin) locks and not with IBM LOCKs.

3. You must code the parameter SYSID=(sysid1,sysid2,...) in the CAIJGENmacro, which specifies the valid SYSIDs in your multi-CPU environment.The first SYSID in the list is the default SYSID that governs which CPUtracks schedules, which will be explained later. The list is also used tovalidate any SYSID defined with a schedule or job.

4. You must specify INSRSYS=YES in the CAIJGEN macro to cause UnicenterCA-Scheduler to insert the SYSID on the POWER job statementautomatically for designated jobs (jobs defined with a value for the SYSIDkeyword on their job base records).

5. You must code the parameter SHARE=YES in the FORMAT statementwhen initializing the Unicenter CA-Scheduler database (CAIJMST), thetracking file (CAIJTRK), the staging library (CAIJSTG), and thedocumentation file (CAIJDCM). It must also be performed whenformatting the the Unicenter CA-Driver procedure library. See theUnicenter CA-Driver Systems Programmer Guide. This is done by executingthe program CAJUTIL0.

These steps are discussed further in the Unicenter CA-Scheduler SystemsProgrammer Guide.

7.5.2 Control Of Jobs in a Multi-CPU EnvironmentDiscussion in this topic pertains to multi-CPUs in a POWER shared spoolenvironment. This can be depicted as:



Normally you would not specify a specific CPU on which a job is to execute.That is, you would let POWER determine which CPU is available to handlethe job and then let POWER start it on that CPU. This is called centralizedcontrol. If you direct a schedule to a specific CPU by defining the SYSID fromwhich it will be controlled (by defining the SYSID on the schedule baserecord), you will have a degree of decentralized control. The more schedulesyou do this to, the more decentralized control you have.

In the case of decentralized control, be aware that the RUN ON SYSID fields(and the equivalent SYSID batch keywords) on the schedule base record andjob base record perform different functions. RUN ON SYSID on the schedulebase record defines the CPU on which Unicenter CA-Scheduler controls theschedule (that is, the CPU from which the schedule's jobs are submitted.) Onthe other hand, RUN ON SYSID on the job base record specifies the CPU onwhich the job actually executes.

The following steps through what happens in the control of a multi-CPUenvironment on a daily basis.

Autoscan During the autoscan process, all schedules that have a SYSIDthat matches the one for the CPU on which autoscan is beingrun, will be selected for control on that CPU. That is, all jobswill be submitted from the controlling CPU and internally



tracked there. Do not forget, the default SYSID is the first onein your SYSID list specified when generating UnicenterCA-Scheduler (CAIJGEN macro) and will be used for anyschedule defined without a SYSID.

If the job is actually executed on a CPU other than thecontrolling one the other CPU will notify the controlling CPUof any information it would have picked up itself, such as jobstarted and job completed, along with the termination code.This is done by writing information on the tracking file to bepassed along as internal events. If any job is defined withouta SYSID, the default SYSID is the one specified (or defaulted)at the schedule definition.

Operator CommandsWhen you issue operator commands, there are times that youshould be aware of which CPU is in control of the schedule orjob. That is, if you issue a CANCEL operator command for ajob that is not controlled on the CPU on which you are on, itis written to the tracking file and within seconds (could be upto 30 seconds), processed by the CPU controlling that job. If,for some reason, the CPU is not able to handle it right away(suppose it is down), as soon as it can, it will process thecommand; even if it is hours later. The area on the trackingfile that passes these operator commands and statusinformation back and forth between CPUs is called theInter-Communication Records area (ICR).

The only operator command that cannot work in a multi-CPUenvironment is the STATUS command using the prioritysequence. Since the priority order happens to be an in-coremechanism, for performance reasons, each CPU has its ownlist. Thus, when you request a display of jobs on anotherCPU, the priority option cannot be used.

Do keep in mind that any operator commands that are issuedthat have to execute on a CPU other than the one they wereissued from, will be sent across the ICR on the tracking file.They will remain there until actually processed or purged.When the down CPU becomes operational again andUnicenter CA-Scheduler is subsequently started, UnicenterCA-Scheduler determines if it missed an autoscan. If it missedan autoscan, Unicenter CA-Scheduler immediately performsan autoscan. If, during this autoscan, Unicenter CA-Schedulerfinds ICRs that are more than 24 hours old, it purges thoseold ICRs without executing them.

Another consideration for multiple CPU environments is themethod for executing jobs at a CPU other than the controllingCPU. To do this on a permanent basis, specify the SYSID ofthe CPU at which the job will execute in the RUN ON SYSIDfield of the job's base record. To alter the CPU for one



execution only, use the TALTER command with the SYSIDkeyword.

Submission of JobsJobs are always submitted from the CPU where theirschedules are controlled from. The proper POWER JECL JOBparameters are generated if a RUN ON SYSID (SYSIDkeyword) is specified on the job base record.

7.5.3 Recovery Of Jobs in a Multi-CPU EnvironmentThe recovery process that is described here is when one of the CPUs in amulti-CPU environment has an outage. Just because a CPU is down, it doesnot mean the jobs set to execute there do not have to run; the work still has toget done.

In the discussions that follow, there are two items that apply to practically allrecovery methods.

First, there is an operator command that is used to, essentially, move UnicenterCA-Scheduler control of schedules from one CPU to another. You do this withthe operator command called MOVEOVER. This command should be usedonly when there is a CPU outage.

Second, you are able to run the autoscan process for a down CPU with anoperator command called AUTOSCAN, on the CPU that is up. You do this byspecifying the CPU SYSID whose schedules and jobs you want to run on theup CPU. This ensures that all work, even for the down CPU, is in theproduction workload.

The following describes the various environments, as recovery is slightlydifferent if you are in a decentralized versus a centralized environment.

Decentralized In a decentralized environment, there are some schedules thathave a specific SYSID from which they are controlled. Thismeans that you have filled in the controlling SYSID in theRUN ON SYSID field on the Schedule Definition panel.Consequently, schedules will be controlled from theirrespective SYSIDs which means that the environment containsmultiple Master CPUs.

Now, what happens if one of the Master CPUs goes down?Move the schedules and jobs onto a Master CPU that is up.You do this by issuing the MOVEOVER operator command onthe Master CPU that is to take control of the downed MasterCPU's jobs. Here is an example. If the downed Master CPUhas a SYSID of 1 and the new one has a SYSID of 2, then theMOVEOVER operator command would look like:

SC MOVEOVER SYS=1,TARGET=2



If you knew the outage was going to be short, you couldMOVEOVER specific schedules by issuing this command foreach schedule you want moved over. The TARGET field isoptional and defaults to the CPU on which the MOVEOVERcommand is being issued. It gives you the flexibility to issuethe command and cause it to be executed on another CPU.

At some point, the original Master CPU is available. It mustbe given back control of Unicenter CA-Scheduler. Thus, youuse the operator command (from SYSID 1):

SC MOVEOVER RESTORE=Y

which will cause all schedules (even those currently executing)that were controlled originally by the CPU that was down, tobe moved back.

Centralized In a centralized environment, there are no schedules that havea user-specified SYSID from which they are controlled. Thismeans that you have never filled in the RUN ON SYSID fieldwhen using the Schedule Definition panel. Consequently, alljobs will be controlled on the first SYSID in the list of SYSIDsdefined in the CAIJGEN macro which is the the Master CPU.All other CPUs in the list are Slave CPUs.

The simplest case is that if a Slave CPU is down, nothing hasto be done with Unicenter CA-Scheduler as POWER will havebeen changed in a manner to handle this situation.

Now consider what must be done if the Master CPU goesdown. One of the Slave CPUs must be made the Master sothat Unicenter CA-Scheduler can continue controlling theschedules and jobs. The workload from the Master CPU mustbe moved over to the Slave CPU and the Slave CPU made tosimulate the Master CPU. You may do this by executing abatch program, CAJMMOV0, but first you must use theSHUTDOWN operator command to shutdown UnicenterCA-Scheduler, then run the following job on the slave CPU.

// JOB CAJMMOV�

// EXEC CAJMMOV�

/�

/&

After the job completes, bring up Unicenter CA-Scheduler onthat CPU again. It will now perform as the Master CPU.

Executing the CAJMMOV0 program on a CPU has a "permanent" effect, in thatthe CPU will become the Master (control all schedules and jobs, and performAUTOSCAN) until the program is executed on a different CPU. If for anyreason a format of the tracking file becomes necessary, you must run



CAJMMOV0 again to designate the master CPU. Thus, when your "real"Master CPU is back, execute the CAJMMOV0 program on the "real" Master,before you bring up Unicenter CA-Scheduler, and things should be back tonormal.

7.5.4 Non-Shared POWER ConsiderationsThis topic pertains to multi-CPUs in a POWER environment that is not shared.This can be depicted as:

In this environment, you must specify a SYSID for each schedule you defineon the database, unless it is to be controlled from the first SYSID in the SYSIDlist generated with the CAIJGEN macro.

Recovery in this environment is handled in the same way as the sharedPOWER (multi-access) environment.

Do keep in mind that, in this environment, it is not possible to have a schedulecontrolled at CPU1 and have that schedule's jobs be submitted to any otherCPU (CPU2 or CPU3) for execution.


7.6 NJE Processing

7.6 NJE Processing

NJE processing provides the ability to go beyond one data center complex.That is, you can schedule and control production at different locations (even indifferent cities). The different locations can have just one CPU or they mayhave a multi-CPU environment, though each CPU must be a node on theVTAM network.

In some cases, you may want to have just interdependencies across locationsproperly handled. In other cases, you may want to go beyond this and havejobs at one location submitted to execute at another location. These locationsare called nodes in the network of computer sites (or systems). The networkconsists of two or more of these interconnected systems (nodes) thatparticipate in a VTAM communications network.

Using more common terminology, a job at one node can have a predecessor atanother node and Unicenter CA-Scheduler will know to wait for it. Each nodewill be able to schedule its own work as if it were autonomous, but when ithas interrelationships with other nodes, they will be upheld properly. This is adecentralized (Master/Master) environment. Each of these Masterenvironments (nodes) can have its own Master/Master or Master/Slaveenvironment and may be one or more CPUs themselves that utilize sharedspool.

Following are some samples that describe:

■ Cross-node job submission ■ Cross-node dependencies ■ Cross-node communications.

7.6.1 Cross-Node Job SubmissionIn a NJE environment, it is possible to have Unicenter CA-Scheduler causework to be submitted to run on other nodes. The appropriate VSE/POWERJECL parameters (if omitted from the submitted JCL) are generated to handlethis, but what you want to accomplish here is to have you understand howUnicenter CA-Sheduler operates in this environment.

The following depicts the general environment that the samples will reference.


7.6 NJE Processing

In the preceding diagram, the NODEA site is a single CPU using VSE\POWERwith NJE, and CA†SCHEDULER with the NJE option activated. Each CPU is anode on a VTAM Network.

Sample 1 Schedule SCHDA is defined at node NODEA with no NODEID specified.

This is the normal case and it will always be controlled byNODEA.

Sample 2 Schedule SCHDB is defined at node NODEB with no NODEID specified.

This is also the normal case and it will be controlled byNODEB.

Sample 3 Schedule SCHDX is defined at node NODEA with a NODE IDof NODEB. JOB1 is defined as part of schedule SCHDX andhas no NODE ID specified.

In this case, NODEA controls and submits JOB1. JOB1 will berouted to NODEB where it will run and NODEB will know tosend its status back to NODEA for posting and control. Noticethat since the NODE ID for the job was not defined, it usesthe one defined for the schedule.

Sample 4 Schedule SCHDX is defined at node NODEA. JOB1 is definedas part of schedule SCHDX and has a NODE ID of NODEB,which means that JOB1 is to execute on the CPU defined asNODEB.

In this case, NODEA controls the schedule SCHDX. JOB1within SCHDX, however, has a NODE ID defined whichmeans that JOB1 will have its JCL routed to NODEB throughNJE.


7.6 NJE Processing

Sample 5 Schedule SCHDY is defined at NODEB with a NODE ID ofNODEA and RUN ON SYSID of 2. JOB1 is defined as part ofschedule SCHDY and does not have a NODE ID specified, butdoes have RUN ON SYSID of 3.

In this case, NODEB controls the schedule SCHDY at the CPUwith SYSID 2. JOB1 within SCHDY will be routed to NODEAto run since its NODE ID is not defined and it picks up theone from its schedule which is NODEA. Since there is noNODE SYSID on the job or its schedule, it will run accordingto the definitions at NODEA that, in this sample, would be 1.The RUN ON SYSID of 3 at the job level, in this case, will beignored.

Sample 6 Schedule SCHDY is defined at node NODEB with no NODEID or NODE SYSID. JOB1 is defined as part of scheduleSCHDY and has a NODE ID of NODEA and a RUN ONSYSID of 3.

In this case, NODEB controls the schedule SCHDY at the CPUthat is defined as the controlling CPU with the UnicenterCA-Scheduler SYSGEN definitions (described in the priortopic on Multiple CPU Considerations). JOB1 within SCHDYwill be routed to NODEA to run since its NODE ID ofNODEA overrides anything defined at the schedule level.Since there is no NODE SYSID on the job or its schedule, itwill run according to the definitions at NODEA that, in thissample, would be 1. The RUN ON SYSID of 3 at the job levelwill, again, be ignored.

In summary This gives you some insight into how jobs can be defined onone node and submitted to run on another node.

7.6.2 Cross-Node DependenciesThe only predecessor events that can be fed back and forth between nodes areNJE start or completion of job events.

In the case of job predecessors across nodes, you must define a job node recordif Unicenter CA-Scheduler is to inform another node or nodes (up to eight)that this job started or completed. You do this with the INFORM Definitionpanel.

The following discusses each of these types of predecessors and how to definethem.


7.6 NJE Processing

7.6.2.1 NJE Job Dependencies

When a predecessor of a schedule or job is a job controlled by another node,then you use the NJE keyword. The NJE keyword only pertains to jobs, notschedules. NJE can take any one of the following forms:

To mark an NJE predecessor job as satisfied, its definition must includeinstructions for Unicenter CA-Scheduler to notify the relevant node or nodes.You do this using the INFORM Record Definition panel. That is, if a jobcontrolled from NODEA has NJE JOBA as a predecessor and you neverdefined a job INFORM Definition panel for JOBA and JOBA runs at a nodeother than NODEA, then NODEA will never be notified that JOBA completed.Consequently, the job on NODEA will never be submitted.

Remember two things when dealing with predecessor jobs across nodes. First,use the NJE keyword, and second, use the INFORM Definition panel. Thus,you close the loop.

NJE Form Predecessor Type Is

NJE jobname The completion of a job at another node.

START NJE jobname The start of a job at another node.

PRED NJE jobname The completion of a job at another node on aprevious day.

7.6.3 Cross-Node Command ProcessingControl commands can be issued on one node and processed on another node.You do this by using the RO (ROute=nodeid) keyword in the correspondingcontrol command. The node to which you are directing the command must beactive. Practically all of the commands offer this keyword. An example ofcross-node communications follows.

The environment used in the preceding example consists of three nodesrunning NJE using the Unicenter CA-Scheduler NJE option. Each nodeconsists of a single CPU.


7.6 NJE Processing

The following jobs are defined at the Cherry Hill node:

SCD: SH��1

JOB: SHJ�1,NODE=blank

JOB: SHJ�2,NODE=NEWYORK

JOB: SHJ�3,NODE=PHOENIX

JOB: SHJ�4,NODE=NEWYORK

All of the preceding jobs are within the schedule SH001. The schedule runsevery day and so does each job.

Shown below are different cases of cross-node communications given thefollowing situation with these nodes.

The operator at the Phoenix node can issue the CANCEL command withdifferent optional keywords with different results in each case.

CASE 1: CANCEL S NAME=SH��1,FM=CHERRYHL

The preceding will cancel the part of SH001 submitted from Cherry Hill andrunning at Phoenix. Thus, only job SHJ03 is canceled. The other jobs in theschedule at Cherry Hill and New York remain intact.

CASE 2: CANCEL S NAME=SH��1,FM=CHERRYHL,ROUTE=NEWYORK

This preceding will cancel the part of SH001 submitted from Cherry Hill andrunning at New York. Thus, only jobs SHJ02 and SHJ04 are canceled (that is,they are deleted from the POWER input queue since they have a status ofSUBMITD). The other jobs in the schedule at Cherry Hill and Phoenix remainintact.

CASE 3: CANCEL S NAME=SH��1,ROUTE=CHERRYHL

The preceding will cause all jobs in schedule SH001 to be canceled regardlessof where they are running. All of them are canceled because the ROUTE=keyword directs the command to be issued at the Cherry Hill node. This isthe node where the schedule SH001 is defined and controlled.

A summary follows.


7.6 NJE Processing

1. When specifying the optional keyword FM= on commands, you areidentifying which node originally submitted the schedule or job to yourlocal node. This optional keyword allows you to distinguish betweenremotely submitted schedules and jobs from locally defined and controlledschedules and jobs of the same name (that is, schedule SH001 from CherryHill as opposed to schedule SH001 originating in Phoenix).

2. When specifying the optional keyword ROUTE= on commands you areidentifying the remote node that will actually process the command youare issuing.

3. When executing a command directed at a schedule at the node where thatschedule is defined, all jobs within that schedule are affected.

7.6.4 Installation ConsiderationsWhen installing Unicenter CA-Scheduler, you have to designate that you aregoing to be in an NJE environment.

There are a set of steps you must take in establishing your communicationenvironment. First, you must code a certain set of operands in the CAIJGENmacro for each of the data centers. Next, you must establish your VTAMnetwork. Each of these is described separately.

7.6.4.1 CAIJGEN Macro

There are a set of operands on the CAIJGEN macro that you must considerwhen installing the cross-node communication facility in UnicenterCA-Scheduler. They include the following.

1. You must establish each of the individual locations with their ownUnicenter CA-Scheduler system. Each of them must have UnicenterCA-Scheduler installed and be defined to handle a Unicenter CA-SchedulerNJE environment.

2. You must code the parameter NJE=YES in the CAIJGEN macro. Thisspecifies that you are going to have cross-node communications usingUnicenter CA-Scheduler.

3. You can override the VTAM retry interval, which means that if the VTAMconnection that is suppose to exist is, for some reason, not up, thenUnicenter CA-Scheduler will keep trying to make the connection every nminutes. You define n in the operand VRETRY=N in the CAIJGEN macro.

7.6.4.2 VTAM Communications

You will be using VTAM as your mechanism for cross-node communications.You are going to have to do two things to implement the VTAM mechanism.

1. You will have to code the CAIJNET macro as described in the UnicenterCA-Scheduler Systems Programmer Guide. You must use this macro for eachof the nodes in the network. Its primary purpose is to list the nodes that


7.6 NJE Processing

Unicenter CA-Scheduler will communicate with. The node name(NNAME) is related back to the NODE ID on the Schedule and JobDefinition panels.

2. You are going to have to define the VTAM application to your variousdata centers. This is described in the Unicenter CA-Scheduler InstallationGuide. It relates your VTAM environment back to the VTAM applicationname defined in the CAIJNET macro described preceding. You mustdefine a VTAM APPLID for each system in the network where UnicenterCA-Scheduler is installed.

7.6.5 Control Commands for Checking The NJE NetworkThere are three commands that can be used to control and interrogate thenetwork under which Unicenter CA-Scheduler operates. These commands aredescribed in the chapter "Controlling Schedules and Jobs" in the UnicenterCA-Scheduler Reference Guide Part 1. The commands are described brieflyfollowing.

The network can be displayed with the Display Network control command (orD NET). The status of each node in the network will be displayed. The displayincludes the following information for each node:

NAME The node name.

SYSID This node's NJE/POWER SYSID.

TYPE This node's type.

APPLID This node's VTAM applid if VTAM is used for communicationbetween this node and the local node, or

ZONE Time adjustment factor between this node and the local node.

STATUS The current status of this node. The STATUS may be any of thefollowing:

Status Meaning

LOCAL-NODE This is the local node.

CONNECTED This node is currently connected to the local node.

UNCONNECTED This node is not connected to the local node at thistime. Either Unicenter CA-Scheduler is down onthis node, or VTAM communication is interruptedfor some reason.

CONCT-BND This node is in the process of establishingconnection to the local node.

ERROR This node was not defined to POWER. Make sureNNAME in the CAIJNET macro correctly specifiesthe name of the node as defined to POWER.


7.6 NJE Processing

STACK USAGE The number of requests currently stacked to be sent to thisnode from the local node, and the amount of private storagethat those requests occupy.

All Unicenter CA-Scheduler sessions can be activated or deactivated with theVARY operator command. You can vary one VTAM session at a time or dothem all at once. VARY A activates VTAM sessions and VARY I deactivatesthem.

Status Meaning

BUSY The local node is currently sending requests to thisnode. This is a normal situation as long as thenumber of stacked requests is moving up anddown. If the number of stacked requests onlymoves up, it may indicate a slowdown in VTAMcommunications between the local node and thisnode and possibly a lost VTAM connection.

Unicenter CA-Scheduler will send a warningmessage to the operator console when the amountof storage used to hold the stacked requestsreaches the threshold defined in the VTAMLIMoption of the CAIJNET option. In this case youshould use the Unicenter CA-Scheduler or VTAMVARY INACT command to disconnectcommunication with this node.

Unicenter CA-Scheduler will then save any stackedrequests for this node on the tracking file. Whenthe VTAM problem is resolved, use the UnicenterCA-Scheduler VARY ACT command to reestablishcommunication with this node. UnicenterCA-Scheduler will then resend any requests thatwere saved for this node.


7.7 Summing Up

7.7 Summing Up

The following is a review of the important principles outlined previously.

7.7.1 On-Request Schedules and JobsRemember these subtleties when defining a criteria statement containing thekeyword REQUESTED:

■ A criteria statement of REQUESTED causes Unicenter CA-Scheduler to putthat schedule or job and its successors in the inactive queue at autoscan.

■ When OR REQUESTED occurs in a criteria statement, UnicenterCA-Scheduler will select that schedule or job daily. However, whether it isput in the inactive queue depends on the reason for selection. If selectionoccurs because of REQUESTED, that schedule or job is placed in theinactive queue. Therefore, the order of reasons in a criteria statement reallymatters a lot if one of the reasons is requested.

When a schedule or job is selected because of REQUESTED, all its successorsare put in the inactive queue. Issuing a REQUEST command moves a scheduleor job and all its successors to the active queue. The SREQ command handlessuccessors differently: SREQ will not activate a successor if it involves otherrequested jobs. A successor of an SREQed schedule or job will not be movedto the active queue if:

■ The successor's criteria statement contains the keyword REQUESTED or■ That successor is also the successor of some other requested job in the

inactive queue

7.7.2 Backlogged WorkIf work is backlogged for more than 48 hours, it is likely that the second day'sschedule will never run. Monitor your backlogged work carefully.

7.7.3 Online Commands in BatchThe CAJUCMD0 program can process six types of batch transactions:


CP Issue the following VM command.

MO Send the following text to the operator console.

SC Issue the following Unicenter CA-Scheduler operatorcommand, which can include the conditional batch IFstatement.

CI CICS Transactions


7.7 Summing Up

IF statements can include AND, OR and NOT keywords, test for major andminor status codes test the value of a global parameter


PW POWER commands

DM Commands stored in the documentation library

7.7.4 RecoveryJobs that may need recovery have a status of ABENDED, OPERATORCANCLD, or FAILED. The ABEND field on a job base record controls whathappens automatically if a job abends. If ABEND specifies a recovery schedule,that schedule could include a job that executes the program CAJUCMD0.Unicenter CA-Driver can automatically restart a job at different stepsdepending on the type of abend that occurred.

7.7.5 Multi-CPU ConsiderationsBe sure to specify these values in the CAIJGEN macro when installingUnicenter CA-Scheduler:

MCPU=YES SHARE=YES SYSID=(sysid1,2,...) INSRSYS=YES

Run the program CAJUTIL0 with the keyword SHARE=YES in the FORMATstatements for the following files:

CAIJMST CAIJTRK CAIJSTG CAIJDCM

If Unicenter CA-Driver is installed at your site, run the program CARUINTAor CAJUTIL0 with the keyword SHARE=YES in the FORMAT statement forthe Unicenter CA-Driver procedure library (CAIJDRV).

If you have multiple CPUs in a POWER environment that is not shared spool,you must specify a SYSID for each schedule you define unless it is controlledfrom first SYSID in the list generated with the CAIJGEN macro. In thisenvironment, it is not possible to have a schedule controlled by one CPU andhave its jobs executed on another CPU.


7.7 Summing Up

7.7.6 NJE ProcessingThe node where a schedule is defined is the node that controls that scheduleand submits its jobs.

A job's NODE ID identifies where that job will run. A schedule's NODE IDidentifies the CPU that will track and control that schedule and its jobs, andwill submit those jobs to the appropriate CPUs.

NODE SYSID identifies which CPU a job will run on at the specified NODEID.

Predecessor events can be fed between nodes if:

■ Jobs are preceded by the keyword NJE in the successors' criteria statementsand the predecessor's job node record is defined to notify every successor'snode of the predecessor's status

■ Output data set names are preceded by the keyword DSN in thesuccessors' criteria statements and have been specified to the CAIJ$DSNmacro with the successors' nodes that require notification andDSNINFM=YES in the CAIJGEN macro


Glossary

This glossary defines terms used in all volumes ofUnicenter CA-Scheduler's documentation, butsometimes one new term leads to another. To helpyou grasp these new ideas quickly, we have useditalics to highlight related terms worthcross-referencing.

abend. Abnormal ending. An early termination ofa program due to an error.

accounting day. A day designated on a datetable aspart of a cyclic production, sales, or accountingperiod.

accounting period. One or more accounting days.

accounting week. A week containing at least oneaccounting day.

active. Schedules and jobs that are:

■ Waiting at any workstation for predecessors,start time, or defined resources

■ Waiting at a non-CPU station to be startedmanually

■ Submitted, held, or started

■ Completed, interrupted, abended, or failed

The opposite of inactive.

array. A variable parameter with multiple values.

authority level. One of three different types ofaccess assigned to users using the TYPE field on auser record. Each authority level places differentrestrictions on what those Unicenter CA-Schedulerusers can do. See General, Supervisor, and Managerauthority levels.

authorized users. Users with General authority levelwho are allowed to maintain and control a scheduleand its jobs because they are listed in the USERSfield on that schedule's base record. (Users with

Supervisor or Manager authority level do notrequire specific authorization to maintain or controlschedules.)

autoscan. The automatic selection of a day'sworkload. Unicenter CA-Scheduler scans thedatabase at a set time every day to determine theworkload for the next 24 hours.

autoscan day. The 24-hour period starting withautoscan. Also called the production day.

AUTOTIME. The time when UnicenterCA-Scheduler automatically scans its database forworkload selection. This defaults to midnight, butmay be modified with the AUTOTIM installationoption. Also called autoscan time.

available. Ready for processing by UnicenterCA-Scheduler. A schedule is available (ready tostart) when its early start time has been reached andall of its predecessors have been satisfied. A job isavailable (ready to be submitted) when its schedulehas started, the job's early start time has beenreached, all the job's predecessors have beensatisfied, and the resources defined for that job areavailable (not in use).

backlog. Work that was not completed one dayand was carried over to the next. References to abacklogged schedule or job pertain to a previousday's schedule or job which is included in today'sworkload.

backout job. A replacement job that isautomatically submitted by Unicenter CA-Schedulerwhen a job abends provided thatABEND=BACKOUT on the abended job's baserecord.

base record. The record which is required to definea schedule or job. There is a schedule base record(SBR) and a job base record (JBR).

Glossary X-1

batch command. Any command that is issued byexecuting a Unicenter CA-Scheduler programthrough standard DOS JCL.

Unicenter CA-Driver. Computer Associates JCLmanipulation product.

Advantage CA-Earl. Computer Associates EasyAccess Report Language. A subset of this productthat allows you to customize reports is providedwith Unicenter CA-Scheduler.

CAISERV. A Computer Associates diagnosticfacility that allows you to determine the currentvalues of installation options and to produce reportsfor use in troubleshooting problems.

calendar. An alternative method for identifyingwhen a schedule or job should be selected as part ofthe day's workload. With this method, you defineseveral calendars, each designating different dayswhen schedules or jobs should be selected(Mondays, month-ends, pay days, and so forth).The database shows which calendar to consult whenselecting a schedule or job.

calendar mechanism. One of three date referencesUnicenter CA-Scheduler consults when selecting theday's workload.

■ The Gregorian calendar tells UnicenterCA-Scheduler what day of the week it is so, forexample, jobs can be selected on Mondays.

■ Calendars explicitly define which days to selectschedules and jobs so you can run jobs onrandom dates.

■ Datetables define workdays, holidays,accounting days and accounting periods so, forinstance, Unicenter CA-Scheduler can select jobson the last workday of the month.

character string. One or more alphabetic, numeric,or special characters, usually enclosed in delimiters.

control command. A command used to monitor orcontrol the workload. Also known as operatorcommand.

criteria record. The record that determines when aschedule or job is to be selected for processing andlists the predecessors for the schedule or job. There isa schedule criteria record (SCR) and a job criteriarecord (JCR).

criteria statement. A statement defining:

■ The days schedules or jobs should be selectedand

■ What predecessor conditions must be satisfiedbefore selected schedules can start or selectedjobs can be submitted

See selection criteria, predecessor criteria, and selection.

criteria vocabulary. Reserved words used inUnicenter CA-Scheduler's criteria statements.

cyclic scheduling. Scheduling a schedule or job atregular intervals regardless of which day or monthit is (for example, every six weeks).

database. The Unicenter CA-Scheduler masterdatabase that stores records containing definitions ofuserids, stations, schedules, jobs, and resources. Thedefault name of the database is CAIJMST.

datetable. Identifies workdays, holidays,accounting days, and accounting periods so you canuse workday, holiday, and accounting keywords incriteria statements.

datetable prefix. A one letter prefix (excluding E,H, N, P and W) that allows you to define multipleversions of a datetable by applying differentprefixes.

Date Translation Table. A report that shows whenworkday, accounting, and Gregorian conditions aretrue.

deadlock. The stalemate that occurs when jobs arepredecessors to each other. Deadlocked jobs neverrun because their predecessor conditions are neversatisfied. Also called a predecessor loop.

default. A value or action that UnicenterCA-Scheduler supplies automatically unless youspecify some other alternative.

delimiter. A special character that precedes andfollows a character string. In 'this example', thedelimiter is a single quote (') identifying a characterstring consisting of two words: this example.

documentation. Members in the UnicenterCA-Scheduler documentation file (CAIJDCM) thatprovide information to users.

X-2 Unicenter CA-Scheduler User Guide

documentation batch command. A commandissued through batch using the CARUTIL0 programthat is used to maintain members in thedocumentation file.

documentation file. The Unicenter CA-Schedulerfile that contains documentation members. Thedefault name of the file is CAIJDCM.

events. Occurrences that Unicenter CA-Schedulermonitors so it knows when predecessor conditionshave been satisfied. Some of the events thatUnicenter CA-Scheduler monitors are schedules andjobs starting and ending, the close of output datasets and generation data groups, and what time it is.

explicit predecessor. A predecessor that isspecifically defined in the criteria statement of aschedule or job. Explicit predecessors can be eitherof two types:

■ Selection-defined explicit predecessors arepredecessors that also define selection criteria.They can be schedule or job names used with orwithout the keywords SCD and START.

■ Keyword-defined explicit predecessors areignored in the selection process and alwaysinclude one of the following keywords:

DSN GDG GBLxnn DOS PRED

When START or SCD are used with PRED or DOS,the result is a keyword-defined predecessor that isignored during the selection process.

forecasting. .* previously FORECAST Producingreports that show which schedules and jobs will beselected for processing on any given days.

General authority level. The default authority levelassumed for all users unless Supervisor or Manageris specified. Allow users to:

■ Define and maintain certain schedule and jobrecords

■ Control and display the status of certainschedules and jobs

■ Potentially display and alter JCL for certainstaged jobs

Two fields determine the scope of a General user'sauthority:

1. The CONNECT field on each user recorddefines which stations that General user isauthorized to access.

2. The USERS field on a schedule's base recorddefines which General users can access thatschedule and its jobs.

General users are prohibited from doing anythinginvolving stations or schedules for which they arenot authorized. See authorized users as well asSupervisor and Manager authority levels.

generic list. A group of schedules or jobs whosenames begin with the same characters. To display,list, or analyze a generic list, specify the commoncharacters followed by an mask character (*).

global parameter. A user-controlled variable thatdefines a predecessor condition in criteria statementsand can assume arithmetic, binary, or charactervalues. See keyword-defined explicit predecessors.

Gregorian calendar. The standard 12-monthcalendar which Unicenter CA-Scheduler referencesto interpret certain selection keywords (likeWEEK-DAY) in criteria statements. You can useGregorian calendar keywords without defining adatetable or calendars.

Gregorian date. A date shown as mm/dd/yy(American format) or dd/mm/yy (European format).

history file. The Unicenter CA-Scheduler file thatcontains history records for schedules and jobs.

history record. The record that contains statistics ofpast runs of schedules and jobs.

implicit predecessor. Predecessors that are notdefined on a job's criteria statement. BecauseUnicenter CA-Scheduler enforces workstationsequences, pre-CPU jobs (such as data entry and JCLstaging) are implicit predecessors for CPU jobs.Likewise, CPU jobs are implicit predecessors forpost-CPU jobs (such as report distribution). Seesequence enforcement.

inactive. Schedules and jobs that are:

■ Defined as REQUESTED but not activated by aREQUEST or SREQ command, and

■ The successors of REQUESTED schedules andjobs

Schedules and jobs in the inactive queue at autoscantime are purged regardless of what values havebeen defined for BACKLOG. The opposite of active.

Glossary X-3

information record. The record that providesdescriptive information of schedules and jobs. Thereis a schedule information record (SIR) and jobinformation record (JIR).

installation option. A value specified on theCAIJGEN installation macro when UnicenterCA-Scheduler is installed. This value controlsscheduling operations throughout the data centerunless it is overridden by values in UnicenterCA-Scheduler's database.

JBR. Job base record. This record is required todefine a job.

JCR. Job criteria record. This record determineswhen a job is to be selected for processing and liststhe predecessors for the job.

JIR. Job information record. This record providesdescriptive information for a job.

JMR. Job message record. This record determineswho receives messages when a job begins, ends,starts late, abends, is purged, or is interrupted.

JNR. Job node record. This record is used tospecify other nodes to be notified when a job startsor ends.

job. Usually refers to work submitted to the CPUfor processing. However, Unicenter CA-Schedulerexpands the scope of that definition to encompassall data processing tasks under UnicenterCA-Scheduler's control. This can include pre-CPUtasks such as data entry, jobs that run on the CPU,and post-CPU tasks such as report distribution.

job number. One of four fields used to uniquelyidentify each job definition. When a job needs torun more than once during a production day, createa job definition for each iteration by giving themdifferent job numbers.

job path. All the stations where a job is processedas it moves through the data center.

JRC. Job reason code record. This record is usedassign time specifications which vary according tothe reason a job is selected for processing.

JRR. Job resource record. This record allows you todefine the resources necessary to run a job.

Julian date. A five-digit number of the formyyddd, where yy is the year and ddd is the relativeday of the year (from 001 to 366). For example,87305 is November 1, 1987.

keyword-defined explicit predecessors. Predecessorsthat are ignored in the selection process and alwaysinclude at least one of the following keywords:

DSN GDG GBLxnn DOS PRED

The keywords START or SCD can also be used withDOS or PRED.

levels of predecessors. In terms of a family tree,the number of preceding "generations" (schedules orjobs) with defined predecessors. The number endingeach job name following identifies each job's level ofpredecessors.

JOBA0 and JOBB0 have no predecessors.(Their levels of predecessors = 0)

JOBA0 is JOBA1's predecessor.(JOBA1's level of predecessors = 1)

JOBA1 is JOBA2's predecessor.(JOBA2's level of predecessors = 2)

JOBA2 and JOBB0 are JOBA3's predecessors.(JOBA3's level of predecessors = 3)

JOBA3 is JOBB4's predecessor.(JOBB4's level of predecessors = 4)

The key word here is level. JOBA3 has fourdifferent predecessors, but only three levels ofpredecessors. Levels of predecessors is one factor


Unicenter CA-Scheduler uses when ordering theworkload. Schedules and jobs with fewer levels ofpredecessors are evaluated ahead of those withmore.

mailbox. The common area for sending UnicenterCA-Scheduler messages so that they can be viewedby many users without being deleted.

Manager authority level. The highest authoritylevel which allows these users to access all stations,control all schedules and jobs, define and maintainany database records, and issue all commands. SeeGeneral and Supervisor authority levels.

MASTER userid. The userid reserved for theUnicenter CA-Scheduler administrator.

mask character. An asterisk (*) or question mark (?)included anywhere in a search string. Used whenyou want to display all records with names thatshare common characters.

? indicates that any character can besubstituted at this point in the search string,but just one character can be substituted foreach question mark. That makes ? apositional mask character.

* indicates that Unicenter CA-Scheduler willaccept anything occurring at this point in thesearch: an * can signify any number ofcharacters. For example:

P? displays all record names of just 2characters starting with P

P* displays all records that start with theletter P

?ACC?displays record names of just fiveletters with ACC in the middle

*ACC*displays just those records with ACCanywhere in their name

See generic list.

master database. The Unicenter CA-Schedulerdatabase that stores records containing definitions ofuserids, stations, schedules, jobs, and resources. Thedefault name of the database is CAIJMST.

message record. The record that determines whoreceives messages when a schedule or job begins,ends, or starts late or when a job abends, or is

interrupted. There is a schedule message record(SMR) and job message record (JMR).

nesting. One procedure calls (retrieves) anotherprocedure which can, in turn, call anotherprocedure.

node. Each location in a network having one CPUor multiple CPUs with multi-access spooling facility.

node record. The record that specifies other nodesto be notified when a job starts or ends.

null value. A defined value of nothing which hasbeen added to the database using the keywordNULL.

on-request. Schedules or jobs having the keywordREQUESTED in their criteria statement. Theseschedules and jobs are selected every day in casethey are needed, but they remain inactive untilactivated by the REQUEST or SREQ command.

operator command. A command used to monitoror control the workload. Also known as controlcommand.

path. All the stations where a job is processed as itmoves through the data center.

periods. A year can be divided into accountingperiods, production periods, sales cycles, or anyother unit of time. The end of each period isidentified by a P on the datetable.

post-CPU job. Work scheduled after CPUprocessing to wrap up a job. Examples includeoutput decollation, shipment of backup tapes offsite,and report distribution. See station.

pre-CPU job. Work scheduled to prepare a job forCPU processing. Examples include daily shipment ofinput forms, data entry, and JCL setup. See station.

predecessor. An event that must happen before thenext job can begin. Unicenter CA-Scheduler'scriteria statements allow you to define predecessorsfor schedules and jobs which means schedules andjobs in today's workload will not run until theirpredecessors are satisfied. If JOBA is a predecessorof JOBB, JOBB will not run until JOBA runs tocompletion.

Predecessors fall into several different categories thatare defined in this glossary:

Glossary X-5

■ Explicit predecessors

■ Implicit predecessors

■ Keyword-defined explicit predecessors

■ Selection-defined explicit predecessors

predecessor criteria. All of the predecessors definedfor a schedule or job in its criteria statement. Thesepredecessor conditions must be satisfied before aschedule can start or a job can be submitted.

predecessor loop. The stalemate that occurs whenjobs are predecessors to each other. These deadlockedjobs never run because their predecessor conditionsare never satisfied. Also called deadlock.

procedure. One or more statements catalogedunder a procedure name as a member of theCA-Driver procedure library.

procedure library. The library that stores UnicenterCA-Driver procedures.

production day. The 24-hour period starting withautoscan. Also called the autoscan day.

prompt. A word on a screen that reminds you tosupply a value.

prototype calendar. A master calendar that definesall of the year's holidays and tells when toreschedule jobs that would normally be selected onholidays. These holidays and reschedulinginstructions are automatically applied to allcalendars defined for that year.

prototype definition. An existing definition whosevalues are used as defaults for a new definition. Anyfields left blank while defining a new record areassigned values from the prototype definition.

public schedule. A schedule that can bemaintained by all users because no value is specifiedin the USERS field of the schedule base record.

queue. One of the various job categories thatdepend on the status of the jobs.

reason. Why a schedule or job is selected for theday's workload. A reason can be:

■ One or more words from the criteria vocabularyor

■ The names of jobs or schedules also selected thatday or

■ A combination of the two

See selection.

reason code. A number that explains why aschedule or job was selected. Numbers from 01 to 79correspond to the position of a reason in the criteriastatement. Numbers from 80 to 99 are special reasoncodes which indicate that selection was based ondefault daily processing, calendars, or manualadditions.

reason code record. The record that assigns timespecifications which vary according to the reason aschedule or job is selected for processing. There is aschedule reason code record (SRC) and job reasoncode record (JRC).

RECS line. The line on the bottom of the ScheduleDefinition (SCHD-SU) panel and Job Definition(SCHD-JU) panel that provides access to panels foroptional schedule and job records.

reserved-name variable parameter. One of a set ofUnicenter CA-Driver variable parameters which arepredefined by Computer Associates.

resource record. The record which specifies theresources that are used to run a job.

route delay time. The delay between the time a jobends at one station and starts at the next station.

route station. A workstation defined for purposes ofreceiving reports rather than performing dataprocessing tasks.

run book. A report that contains detailedinformation on the current day's workload.

SBR. Schedule base record. This record is requiredto define a schedule.

schedule. A group of related jobs that:

■ Run on the same days or

■ Belong to the same application or

■ Have the same operational dependencies or

■ Belong together because your production jobsare organized that way


The payroll department's month-end jobs couldmake up a schedule. The schedules and jobsselected each day comprise the workload.

SCR. Schedule criteria record. This recorddetermines when a schedule is to be selected forprocessing and lists the predecessors for the schedule.

selection. How Unicenter CA-Scheduler determinesthe day's workload at autoscan time. UnicenterCA-Scheduler reviews the criteria statements ofevery schedule to see which ones qualify forinclusion in the day's workload. Every timeUnicenter CA-Scheduler selects a schedule thatqualifies, it scans the criteria statements of every jobin that schedule. Jobs are selected if:

■ They specify a calendar which defines that dayas a workday or

■ A reason in the criteria statement is true thatday or

■ No criteria record exists for that job or

■ One reason in the criteria statement is thekeyword REQUESTED

Jobs can only be selected when the schedules theybelong to are selected. All the important terms usedin this definition are also defined in this glossary.

selection criteria. There are two distinct meanings:

1. All the reasons why a job or schedule can beselected as defined in its criteria statement. If acalendar is also defined for a schedule or job,Unicenter CA-Scheduler bases selection on thecalendar and ignores the selection criteria. Seeselection.

2. The keywords that are used in the maintenancepanels to limit the directory to be displayed.

selection-defined explicit predecessor. Apredecessor that also defines selection criteria. Theyare schedule or job names used with or without thekeywords SCD and START. When START or SCD isused with PRED or DOS, the result is akeyword-defined explicit predecessor that is ignoredduring the selection process.

selection criteria. All the reasons why a job orschedule can be selected as defined in its criteriastatement. If a calendar is also defined for a scheduleor job, Unicenter CA-Scheduler bases selection on

the calendar and ignores the selection criteria. Seeselection.

sequence enforcement. Making sure schedules andjobs are processed in the right order. See implicitpredecessor.

shared DASD. A hardware configuration thatallows two or more operating systems to use thesame disk files. This situation allows severaloperating systems to use the same set of UnicenterCA-Scheduler files at the same time. However,when operating systems share UnicenterCA-Scheduler files, it does not imply that they alsoshare spool files.

simulation. Answers the question "what if." Itshows how processing is affected by changes inworkload or hardware failure. Simulation also totalshow long each job usually takes to project when theworkload is likely to finish.

SIR. Schedule information record. This recordprovides descriptive information for a schedule.

SMR. Schedule message record. This recorddetermines who receives messages when a schedulebegins, ends, or starts late.

spin locks. The method Unicenter CA-Scheduleruses to protect the integrity of its files when two ormore operating systems share them. See sharedDASD.

SRC. Schedule reason code record. This record isused assign time specifications which vary accordingto the reason a schedule is selected for processing.

staging. Unicenter CA-Scheduler's three-stepprocess for tailoring production JCL:

1. First, Unicenter CA-Scheduler automaticallycopies the production JCL for jobs that requirestaging into its staging library.

2. Then users modify that copy of the JCL asneeded (the original production JCL is notchanged).

3. When the JCL has been modified and thatpre-CPU job has been posted as ENDED,Unicenter CA-Scheduler automatically submitsthe modified JCL to the operating system whenthat job becomes available for processing.

Also called JCL setup.

Glossary X-7

staging file. The Unicenter CA-Scheduler file thatcontains staged JCL members. The default name ofthe file is CAIJSTG.

station. Any area where a job is processed as itmakes its way through the data center. Examplesinclude production control, data entry, JCL setup,CPU processing, and report distribution. Also calleda workstation.

substring. Part of the value given to a variableparameter.

status conditions. The various words (ABENDED,ENDED, and so forth) that Unicenter CA-Schedulerapplies to jobs to indicate their current state withinproduction.

successor. Any job that cannot start until someevent triggers it. Unicenter CA-Scheduler's criteriastatements allow you to define conditions that mustbe met before a job can start. If JOBA must finishbefore JOBB can start, JOBB is a successor to JOBA.Conversely, JOBA is a predecessor to JOBB.

Supervisor authority level. The intermediateauthority level which allows users to control allschedules and jobs at specified stations, even if theyare not authorized on the schedule base record.However, their scope of authority is limited to justthose stations specified on their user record. SeeGeneral and Manager authority levels.

SYSID. The 1-character POWER identifier thatdefines the CPU on which Unicenter CA-Scheduleris running.

tracking. Unicenter CA-Scheduler monitors theprogress of jobs by collecting and analyzing data on

events as they occur. As jobs move from station tostation through the data center, UnicenterCA-Scheduler automatically updates their status inits tracking file.

tracking file. The Unicenter CA-Scheduler file thatcontains the copy of current production. Thedefault name of the file is CAIJTRK.

variable parameter. A symbolic parameter that isdefined when a procedure is cataloged and referencedin the body of the procedure. During expansion, eachreference to the symbolic parameter is replaced witha default or override value.

work flow. The movement of jobs from station tostation through the data center.

workday. Any day that is not designated aweekend or a holiday on a calendar or datetable.

workload. The work Unicenter CA-Scheduleranticipates submitting each day. That includes:

1. The schedules and jobs automatically selected byautoscan to run on that production day based onthe information stored in UnicenterCA-Scheduler's database and

2. The schedules and jobs manually added byusers

See selection.

workstation. Every area where a job is scheduledfor processing as it makes its way through the datacenter. Examples include production control, dataentry, JCL setup, CPU processing, and reportdistribution stations. Also called a station.


Index

Special Characters"Who

islogged on" 2-34

$DYNx schedule 6-17* 2-33

AABEND

field 3-68, 4-13, 7-17ABENDED

queue 4-8status 4-17, 6-14, 6-16, 7-12, 7-16

ABORT option 7-17Accounting periods

criteria keywords 5-3, 5-12Date Translation Table report 5-17using datetables 1-6, 5-2, 5-10, 6-3

Activating VTAM sessions 7-33ACTIVE

field 4-12, 4-13, 4-15queue 4-6, 4-8, 6-17, 7-2status 7-12

AddAuto-Reply Record 3-105command 4-36

ADD command 4-13, 4-36, 6-17, 7-17ADD command definition 4-34Adding

applications 6-11, 6-12fast 6-5jobs 3-53, 3-74, 3-94, 6-5schedules 3-1, 3-3, 3-17, 3-20, 6-5stations 1-11, 2-8, 6-3, 6-5users 2-22, 6-5

Adding an Auto-Reply Record 3-45Advantage CA-Earl reports 1-12, 6-13, 7-9

ALLqueue 4-8value for USER= parameter 4-23

Alter Or Replace An Auto-Reply Record 3-47,3-107

AlteringCPUs jobs run at 7-23job optional records 3-94jobs 3-91predecessors 6-20schedules 3-18, 3-20station

records 2-10user records 2-26

Analysis reports 1-12Analyze

jobs 3-101schedules 3-40

ANALYZE command 1-12, 6-10, 6-12Analyze report 6-10, 6-12AND keyword

DSN keyword 5-25examples 5-4, 5-6IF statement 7-11NOT keyword 5-4, 5-27OR keyword 5-7, 5-11, 5-15purpose 5-3REQUESTED 7-6

Applications 6-12APPLID parameter, CAIJNET macro 7-32Authority levels 1-9, 2-20AUTO

option of RELEASE command 6-19RECVRY HELD status 4-17, 6-18SELECT field 3-5, 3-10, 3-70, 6-12START field

NO value 3-64, 4-22YES value 3-64, 3-72, 4-8, 4-17, 6-3, 6-6, 6-9

status 7-12

Index X-9

AUTO (continued)STRTED status 4-17

Auto-Replydefault values 3-5processing 1-9

Automaticjob submission 4-17, 7-23recovery 4-17, 7-17

AUTOMATIC CONSOLE REPLY 3-44, 3-45, 3-47,3-49, 3-104, 3-105, 3-107, 3-109

Maintenance Panel 3-44Autoscan

backlogged work 6-20, 7-8definition 6-2displaying information 4-3, 4-29global parameters 6-8multi-CPU environment 7-21process 1-7, 3-5, 4-5purges jobs 7-2, 7-4REQUESTED schedules 7-2time 3-72, 6-9, 7-8

AUTOSCAN command 4-29, 7-23AVAIL TIME field 4-14AVERAGE TIME on

job panels 3-71, 3-79schedule panels 3-15, 3-24summary status panel 4-16

AVG TIME onhistory status panel 4-15job panels 3-81schedule panels 3-25

BBacklog

autoscan time 6-2, 6-20definition 1-7, 7-8rerun schedule 4-16status 4-17, 7-12symptom of deadlock 6-12, 6-13

BACKLOG fieldon schedule panels 3-5

BACKLOG field onjob panels 3-69, 7-7, 7-8schedule panels 3-13, 3-64, 7-8, 7-9

Backout jobs 1-9, 3-69, 4-13, 7-17Batch mode 6-5Boolean expressions 5-3

CCAIJ$DSN 4-3, 4-30CAIJGEN 7-31CAIJNET 3-90, 4-31, 7-31CAISERV 1-12CAJUCMD0 program

automatic recovery 7-17issuing online commands in batch 6-16, 7-10resetting global parameters 6-21, 7-13

CAJUTIL0 program 7-20Calendar

Definition panel 5-18holidays 5-18mechanisms 5-1method 3-21, 5-2, 5-10, 5-17, 6-3reason code 4-13workdays 5-18

CANCELcommand

abbreviation 6-15impacts dependencies 6-20recovery 7-16with UNKNOWN status 4-21

status 6-14, 6-16, 7-12CANCEL command

definition 4-32CANCELLED queue 4-8CANCLD status 4-17Carrying over backlog 1-7CC=Uxxxx status 7-12CC=x"00" status 7-12CC=xxxx status 7-12Centralized control 7-20, 7-24Changing

jobs 3-91predecessors 6-20schedules 3-18, 3-20station records 2-10user records 2-26

Checkingjob completion codes 7-12status 7-11, 7-14

Commandsabbreviations 6-15adding to the workload 6-16control online 4-3cross-node processing 7-29, 7-32operator

for recovery 7-16issued in batch 7-10multiple CPUs 7-22


Commands (continued)operator (continued)

online monitoring 4-1where they work 6-15

options 6-15Processor panel 6-8VM 7-10

COMPLETEstatus 7-12, 7-14

COMPLETE commandAUTO STRTED status 4-17definition 4-34INTERRUPTED status 6-9INTRPTD status 4-17non-CPU stations 6-3UNKNOWN status 4-21

COMPLETED queue 4-6, 4-8, 4-14Completion codes 4-15, 4-17, 7-12COMPLETION DEADLINE TIME on

job panels 3-62, 3-73, 3-79schedule panels 3-12, 3-24, 3-73

CONCT-END status 7-32Conditions

causing selection 5-1, 5-4, 5-6, 5-7in IF statements 7-11

CONNECT STATION fieldlogon panel 2-3

CONNECTED status 7-32Console

commands 6-15messages 6-16, 7-10, 7-15

CONT option 7-17Control

centralized 7-20, 7-24commands

checking NJE network 7-32online 4-3online monitoring 4-1

daily production 4-1, 4-3, 7-25decentralized 7-20, 7-23, 7-26NJE network 7-32schedules 4-31

Copying schedule records 3-29CP command 4-32CP transaction 7-10CPU

JOB field 3-64, 3-65master/slave relationship 7-24, 7-26outage 7-23selection 3-66, 7-18station 1-2, 6-3

Creatingjobs 3-53, 3-74schedules 3-1, 3-3, 3-17, 3-20station records 1-11, 2-8, 6-3user records 2-23

CriteriaDefinition panel 3-21, 3-22, 3-77, 3-94language 1-5, 3-58, 5-1, 7-2

CRITERIA keyword 4-28Cross-node

communications 7-29dependencies 7-28job submission 7-26

DD NET command 7-32DAILY keyword 5-2, 5-3, 5-4, 5-10, 6-6Daily processing 4-5Data

Setsmask names 4-30

Data entry 6-3Database

maintenance 3-1, 6-5organization 1-3reports 6-13

Date Translation Table report 5-15Date, displaying 4-3, 4-29Datetable

cycles 6-4Definition panel 5-13method 1-5, 5-2, 5-10, 5-11, 6-3prefix 6-4

DATETABLE field 3-10, 3-21DAY keyword 5-3, 5-13, 5-15Days-of-the-

month keywordsabbreviations 5-3, 5-10accounting cycles 5-3, 5-13workdays 5-3, 5-22

week keywordsabbreviations 5-3, 5-4, 5-10, 5-15, 5-25accounting cycles 5-3workdays 5-3, 5-4

Deactivating VTAM sessions 7-33DEAD status 7-12DEADLINE TIME field 3-25, 3-81Deadlock 5-26, 6-10, 6-12, 6-13Decentralized control 7-20, 7-23, 7-26

Index X-11

Defaults forjob base records 3-56schedule base records 3-6status displays 4-12

Definingdatabase records

authority levels 2-20jobs 3-53, 3-74, 6-5, 6-9optional schedules 3-18passwords 2-21predecessors 3-60, 5-1, 5-6, 6-18schedules 3-1, 3-3, 3-17, 3-20, 6-3, 6-4, 6-5scheduling criteria 1-5, 5-8stations 1-2, 1-11, 2-8, 6-3, 6-5users 2-22, 6-5

global parameters 6-7job

node record 3-89options 1-3, 1-5, 3-18predecessors 3-89work schedules

accounting cycles 1-6calendars 5-17, 5-19holidays 1-5, 5-12production cycles 1-6sales cycles 1-6

DeletingAuto-Reply Record 3-49, 3-109job 3-97schedules 3-36stations 2-13user records 2-29values 3-93

Dependencies 5-1, 7-28Directory of

jobs 3-75schedules 3-29, 3-33, 3-34, 3-37stations 2-12, 2-14, 2-16, 2-17users 2-28, 2-32

DISPLAY $DSN command 4-3, 4-30DISPLAY Alloc command 4-3DISPLAY Date command 4-3, 4-29DISPLAY Network command 4-3, 4-31, 7-32DISPLAY TIME field 3-72, 6-9Displaying

"statusinformation" "who is logged on" 2-34

autoscan information 4-3, 4-29CAIJ$DSN table 4-3data set mask names 4-30database records

jobs 3-56, 3-91

Displaying (continued)database records (continued)

schedules 3-6, 3-20, 3-32stations 2-15userids 2-30

date 4-3, 4-29documentation on operator console 1-8execution history 4-11global parameters 4-3HELP 2-4job

optional records 3-94messages

from other users 4-1sent to your userid 4-3, 4-23when jobs are late 3-72when schedules are late 3-16

network information 4-31status information

global parameters 4-1, 4-27, 6-8network nodes 7-32workload 1-10, 4-1, 4-4

DISPLY KEY field 3-72, 6-9, 6-11Documentation

library 1-8, 3-71, 6-9, 6-11Maintenance panel 3-72, 6-9reports 6-13

DOM keyword 5-3, 5-13, 5-15, 5-22DOS keyword 5-5Down, CPU 7-23DSN keyword

OR keyword 5-25PRED keyword 5-5, 6-18

Dynamic ADD panels 4-37

EEARLIEST START TIME

onjob panels 3-62, 3-65, 3-79, 6-7schedule panels 3-5, 3-20, 3-24

EARLY TIME field 3-25, 3-81END TIME field 4-14End-times 4-11ENDED status 4-17, 6-16Ending Unicenter CA-Scheduler 2-6Erasing values 3-93ERROR status 7-32EXITPARM field 3-27, 3-82Explicit predecessors 5-5


FFAIL CODE field 7-16FAILED

queue 4-8status 4-17, 6-16, 7-12, 7-16

False job completion 1-9File Status report 1-12FORCE command

abbreviation 6-15definition 4-32, 4-34, 6-16FAILED status 4-19UNKNOWN status 4-21WAIT status 4-21, 4-25, 6-17

Forcing logons and logoffs 2-34FORECAST command 6-12Forecasting 1-11, 3-72, 6-9, 6-11, 6-12FORMAT statement 7-20Forms control 1-2

GGBL command 4-3, 6-8, 7-14GBLxnn keyword 4-3, 4-26, 5-5, 5-27, 6-7GDG keyword 5-5General authority level 2-20Getting help 2-4Global parameters

definition 6-7displaying values 4-1, 4-3, 4-27, 6-8in IF statements 7-11setting values 4-1, 4-3, 4-28, 6-21starting transactions 7-11testing values 6-16when backups can run 7-13

Gregorian calendar 5-2, 5-3, 5-10Grouping jobs 1-2, 6-4

HHandling messages 4-22HDAY keyword 5-3, 5-4, 5-12, 5-15, 5-21, 5-23HELD

AND WHENfield 6-18queue 4-8

queue 4-8status 4-17, 6-17, 7-12

HELP 2-4History

displays 4-11, 4-14reports 1-11, 6-13

HOLDcommand 4-17, 7-12JCL parameter 4-22

HOLD command 4-32Holidays 5-4, 5-12, 5-15, 5-18, 5-21, 5-23, 6-3

IICR 7-22IF statement 7-10Ignoring predecessors 6-16Implementation 1-1Implicit predecessors 5-7, 6-6inactive queue

contents 4-6, 4-8, 7-2, 7-12operator commands 6-17

Inform Definition panel 3-89, 7-28, 7-29INFORM NODES field, Inform Definition

panel 3-89Information Definition panel 3-26, 3-82INSRSYS installation option 7-20Installation

NJE considerations 7-31Installation considerations 7-19Inter-Communication Records area 7-22INTERRUPT field 4-17, 6-9INTERRUPTED queue 4-8INTRPTD status 4-17, 6-16, 7-12

JJBR 3-53JCL

errors 7-17libraries 1-8setup 1-2, 1-8, 6-5staging 6-3, 6-13

JCR 3-58, 3-60, 3-77, 4-13JES

CLASS field 3-71shared 7-20, 7-27

JIR 3-77, 3-82JMR 3-74, 3-77, 7-17JNR 3-89Job

altering 3-94analyzing 3-101Auto-Reply Maintenance 3-104commands 6-15defaults 3-56defining 3-94

Index X-13

Job (continued)displaying 3-94maintenance

changes 3-91defining 3-53, 3-74, 6-5, 6-9deleting 3-97displaying 3-56resources 6-7sequencing 1-2, 1-6

messages 3-83name 1-2, 3-55numbers 1-4, 7-15panels

Alter panel 3-93Definition panel 3-54, 3-76, 6-9Directory panel 3-70, 3-75, 3-92Display panel 3-57Maintenance menu 3-54, 3-91

path 1-2, 1-4processing

abends 6-10, 6-16, 7-16cancelling 6-20purging 6-20recovery 7-15reruns 6-8staging 1-8, 3-9, 3-65, 6-5submission 1-7, 6-7, 6-8, 6-16, 7-23

queues 4-8records

base record 3-53criteria record 3-58, 3-60, 3-77, 4-13information 3-77information record 3-82message 3-74, 3-77, 7-17node record 3-89reason code 3-62, 3-77, 3-79

resource recorddefining 3-77, 3-85for simulation 3-71

routing 7-27selection

additions 6-16, 6-17criteria language 5-1, 5-3process 3-58rule 5-8with REQUESTED 6-17, 7-2

status 7-14submission 7-26Summary report 6-12

JOB NUMBER field 3-55

JOB PRIORITY field 3-63JRC 3-62, 3-77, 3-79JRR 3-71, 3-77, 3-85

LLate

messages 3-16, 3-72, 7-12queue 4-6, 4-8status 6-14, 7-12

LIBRARY TYPEon

job panels 3-65, 3-70schedule panels 3-8

Limiting scope of status displays 4-9LIST

option 6-12Listing

"whois logged on" 2-34

jobs 3-56, 3-91schedules 3-32stations 2-15userids 2-30

LOCAL-NODE status 7-32Logoff procedure 2-6, 2-34Logon

panel 2-2, 2-34procedure 2-2, 2-34status 2-28

MMailbox report 1-12, 3-74, 3-84Main menu panel 2-3Maintaining

database records 3-1, 6-5job records 3-52schedule records 3-2stations 2-7user records 2-20

Manager authority level 2-21Mask character 2-33, 3-86, 4-9Master CPU 7-24, 7-26MAX status 7-12MAXIMUM EXECUTION TIME

onjob panels 3-73, 3-79schedule panels 3-16, 3-24, 3-73

MAXIMUM TIME field 3-16, 3-25, 3-81


MBR SUBID field 3-65MCPU installation option 7-20MEMBER

NAME field 3-65PASSWORD field 3-65

MEMOfield 3-68

MessageDefinition panel 3-27, 3-72, 3-83, 6-9displaying 4-3, 4-23HELP 2-6operator 7-10, 7-15record definition 3-27, 3-83routing 6-16sending 4-3status 7-12to other users 1-12, 4-1, 4-23when

jobs are interrupted 6-9jobs run late 3-72jobs start 3-72, 6-9schedules run late 3-16

MO transaction 7-10, 7-15Monitoring workflow 1-10Month keywords

abbreviations 5-3accounting cycles 5-3month names 5-10workdays 5-3, 5-20, 5-22, 5-24

MONTHLY frequency 5-18, 5-19MOVEOVER command 7-23, 7-24MOY keyword 5-3, 5-22MSG installation option 3-17, 3-74MSGHOLD generation option 4-23Multiple

CPUs 1-13, 3-66, 4-11, 7-18, 7-26reasons 5-7

MUSTSTART BY TIME on

job panels 3-73, 3-79schedule panels 3-16, 3-24, 3-73

status 7-12TIME field 3-16, 3-25, 3-81

NNaming

conventions 7-17jobs 1-2schedules 1-3workstations 1-2

Networkdisplaying 4-3, 4-31implementation 1-13, 3-89, 7-25simulation 3-66

NJEdefinition 7-31installation option 7-31job 5-5keyword 5-5, 7-28

PRED keyword 5-5START keyword 5-5

processing 7-25support 1-13

NJE keyword 7-28NNAME parameter, CAIJNET macro 7-32NO BACKLOG CNCL status 4-17, 7-9Node

definition 7-26displaying status 4-31, 7-32notification 7-28record 3-77, 3-89status 7-32

NODE ID fieldJob

Definition panel 7-27, 7-32Definition screen 3-15, 3-67

ScheduleDefinition screen 3-15, 3-67

NODE SYSID fieldJob

Definition panel 7-27, 7-32Definition screen 3-15, 3-67

ScheduleDefinition screen 3-15, 3-67

Non-scheduled MVS job 4-13Non-shared POWER 7-25NORMAL job completion 7-14NOT

keywordAND keyword 5-4, 5-15, 5-23, 5-27IF statement 7-11, 7-14parentheses 5-27purpose 5-3rule 6-8selection 5-8, 5-11

REQUSTED status 4-18Notifying nodes 7-28NOTREQ status 7-12NSYSID parameter, CAIJNET macro 7-32NULL value 3-93, 7-15

Index X-15

Numberingjobs 1-4stations 1-2

OOnline

commands in batch 7-9monitoring 4-1Monitoring panel

displaying global parameters 6-8getting there 4-1issuing control commands 4-33issuing operator commands 6-15

Status paneldisplaying interrupted jobs 6-9issuing operator commands 6-15recovering from system crash 6-18resubmitting jobs 7-16

transactions 7-10Online Monitoring panel 4-35ONLY command 6-12, 6-13OPER status 7-12Operator

commandsdisplaying global parameters 6-8for recovery 7-16issued in batch 7-10multiple CPUs 7-22on Status Display panel 6-20where they work 6-15

messages 7-10, 7-15OPERATOR CANCLD status 7-16OPERATOR on

job panels 3-84, 6-9schedule panels 3-28, 6-9USER= parameter 4-23

OPSUB status 7-12Optional

job records 3-74schedule records 3-17

Options 1-3, 3-18defining 3-18

OR keywordDSN keyword 5-25IF statement 7-11NOT keyword 5-27parentheses 5-7, 5-11, 5-15, 5-21, 5-23predecessors 5-8, 5-21purpose 5-3REQUESTED 7-3

Ordering queues 4-10Organizing schedules 6-4Outage, CPU 7-23Overriding

predecessors 6-16schedule options 1-3start times 6-16

Overviewsystem 1-7

PParentheses in expressions

AND and OR keywords 5-7, 5-11, 5-15, 5-21,5-22, 5-23, 5-24, 5-26

NOT keyword 5-27purpose 5-3

Passwords 2-21Pending Job Profile report 7-9Pitfalls 6-19POST command 4-3POST DEPENDENCY field 4-25Post-CPU stations 1-2POWER

CLASS field 3-8, 3-16HOLD status 6-18non-shared 7-25

Pre-CPU stations 1-2PRED

flag 6-18keyword 5-5, 6-18status 7-12

PRED keyword 7-29PREDECESSOR JOBS field 4-37Predecessors

AND keyword 5-4deadlock 5-26, 6-10, 6-12, 6-13definition 1-6, 3-11, 3-60loop 5-26, 6-10, 6-12maintenance

changing 6-20defining 5-1, 5-6, 6-18overriding 6-16posting 4-38set manually 4-1

multiple nodes 7-28NOT keyword 5-8OR keyword 5-7, 5-21, 5-25, 7-4reserved words 5-4, 5-5satisfying 4-3types

at different nodes 3-89


Predecessors (continued)types (continued)

explicit 5-5from prior days 5-5, 6-18generation data group 5-5implicit 5-7, 6-6non-scheduled DOS job 5-5other jobs or schedules 5-3, 5-4, 5-5, 5-6, 5-9,

5-21, 5-22, 5-23, 5-24, 5-25, 5-26, 5-27, 7-3, 7-4output data set 5-5, 5-25tasks starting 5-3, 5-4, 5-5, 5-6user-defined event 5-5, 5-27, 6-7

unposting 4-3, 4-25waiting 4-21

Predicting the workload 6-11Prerequisites 5-1Printing

jobs 4-17, 6-3run books 6-11

Priority-ordered queues 4-10Production

control 1-2cycles 1-6, 5-12, 6-4day 4-5, 7-8library 1-8tasks 1-1

Progress notification 1-12Prototype

calendars 5-17schedules 3-30

Public schedules 3-5PURGE command

definition 4-32impacts dependencies 6-20with CANCLD status 4-17with ENDED status 4-17

QQUERY MESSAGES field 4-23Questions 6-2Queue

definitions 4-6formats 4-11sequence 4-10

Quick data entry 6-5

RRC field 4-13

RDnn keyword 5-3, 5-12Reasons

codes 4-13, 5-7, 7-4Definition Panel 3-24, 3-80for selection 5-1multiple 5-7

RECOVERABLEfield 3-68, 6-18

Recovering scheduled jobs 7-15Recovery

AUTO status 7-12system crash 6-18

RECSfield


Relative days 5-3, 5-12, 5-17RELEASE command

automatic recovery 4-17, 6-18definition 4-32HELD status 4-17

REMAINING TIME field 4-16REORG command 1-12Reports

Advantage CA-Earl Databaseuser-defined 6-13

Analyze 6-10, 6-12Date Translation Table 5-15distribution 1-2forecasts 6-11Job Summary 6-12Pending Job Profile 7-9simulation 6-11types 1-11user-defined 6-13

REQUESTcommand

abbreviation 6-17automatic recovery 7-17definition 4-32, 4-34inactive queue 4-6, 4-8, 4-18, 7-2predecessors 7-4

REQUESTED keyworddaily processing 4-6, 6-17impact on successors 7-3jobs purged by autoscan 7-2, 7-4purpose 7-1

RERUNcommand

ABENDED status 7-16CANCLD status 4-17, 6-17, 7-16definition 4-34, 6-16

Index X-17

RERUN (continued)command (continued)

edit checks 6-8ENDED status 4-17FAILED status 4-17, 7-16INTRPTD status 4-17, 6-9

field 4-16RESC status 7-12Reserved words 5-3, 5-4, 5-5Resetting

global parameters 6-21PRED flag 6-18

ResourceDefinition panel 3-85requirements 4-21, 6-7

RESTAGE command 6-6, 7-17Restart

instructions 1-8, 7-15job steps 7-18

RESTORE option 7-24Revising

jobs 3-91schedules 3-18, 3-20

ROUTE keyword 7-29, 7-32Routing

jobs 7-27messages 1-12, 3-72, 6-9

Rules governingcriteria language 5-29datetables 5-13predecessors 5-7, 5-8, 5-9selection 5-8, 5-9, 5-10

RUNcommand

automatic recovery 7-17CANCLD status 4-17, 7-16definition 4-32, 4-34, 6-16, 6-17ENDED status 4-17reason code 4-13staging jobs 6-5

IF REQUESTED queue 4-8ON SYSID field on


RUNBOOK 3-72, 6-9, 6-11Running backups 7-13

SSales cycles 1-6, 5-12, 6-4

Satisfy predecessor conditions 4-3, 4-38SBR 3-6SC transaction 7-10, 7-13SCD keyword 5-3, 5-4, 5-5, 5-6SCHD command 2-2SCHDUTIL Output Panel 2-9, 6-5SCHED PRIORITY field, schedule display 3-8, 3-12Schedule

analyzing 3-40Auto-Reply Maintenance 3-44maintenance

changing 3-18, 3-20copying 3-29defaults 3-6defining 3-1, 3-3, 3-17, 3-20, 6-3, 6-4, 6-5deleting 3-36displaying 3-6, 3-20listing 3-32messages 3-27priorities 3-12

name 1-3, 3-55panels

Command Processor panel 6-15Definition panel 3-4, 3-29Directory panel 3-29, 3-33, 3-34, 3-37Display panel 3-7, 3-32Maintenance menu 3-4, 3-19Schedule Directory panel 3-35Summary Status Display 4-11, 4-15

processingbacklog 4-16commands 6-15controlling 4-31recovery 7-15

recordsbase 3-6criteria record 3-6, 3-10, 3-11, 3-21, 4-13information 3-6message 3-6, 3-17, 3-74reason code 3-6, 3-12, 3-62

selectionadditions 6-16criteria language 5-1, 5-3rule 5-8with REQUESTED 6-17, 7-2

SCHEDULE NAME field 3-4SCHEDULER Command Processor

panel 4-12panel, issuing control commands 4-33, 4-35

SchedulingCPU networks 1-13


Scheduling (continued)jobs 1-5, 5-8, 5-18multiple CPUs 1-13techniques 7-1

SCR 3-6, 3-10, 3-11, 3-21, 4-13Security 1-9Selecting

jobsADD command 6-17criteria language 5-3process 1-7, 3-58REQUESTED keyword 6-17, 7-2RUN command 6-16with schedules 5-8

reports 1-11schedules

criteria language 5-3instead of jobs 5-8methods 6-3process 3-10REQUESTED keyword 6-17, 7-2RUN command 6-16

SEND MESSAGE field 4-23Sending messages

abended jobs 7-17failed jobs 7-17interrupted jobs 6-9late jobs 3-16, 3-72to

console 6-16, 7-10, 7-15other users 3-27, 3-83, 4-1, 4-3, 4-23, 6-16

when non-CPU jobs start 3-72, 6-9SENDMSG command 4-3SEPARATE

DSNAME field 4-21, 6-7JOBS field 4-21, 6-7

Sequencingenforcement 1-2, 1-6jobs 1-6queues 4-10workstations 1-2

SET command 4-3, 6-8, 7-13SET/DSPLY GLOBALS field 4-27Setting global parameters 4-1, 4-3, 4-28SHARE installation option 7-20Shared

JES 7-20, 7-27SHUTDOWN

DELAY command 4-18HELD status 4-18

SID 7-19SIMTIME 6-11SIMULATE command 6-13Simulation 1-11, 3-72, 6-9, 6-11, 6-12, 6-13SIR 3-6SKIP field 3-10, 3-58Slave CPU 7-24, 7-26SMR 3-6, 3-17, 3-74Sorting queues 4-10Specific dates 5-17, 6-4SRC 3-6, 3-12, 3-62SREQ

commandinactive queue 7-2

SREQ commandabbreviation 6-17definition 4-32, 4-34inactive queue 4-6, 4-8, 4-18predecessors 7-4

STAGE JCL field 3-9, 3-65, 6-6Staging

filereports 6-13

jobs 1-8, 3-9, 3-65, 6-3, 6-5START

command 4-18, 4-22, 4-34, 7-14keyword 5-3, 5-4, 5-5, 7-29status 7-12TIME field 4-14with WAIT status 7-15

STARTEDqueue 4-6, 4-8status 4-18, 6-18, 7-12, 7-14

Startingjobs 6-16schedules 6-8, 6-16transactions 7-11Unicenter CA-Scheduler 2-2

StationID 2-9, 3-55, 3-64maintenance

adding 1-11, 2-8, 6-3, 6-5deleting 2-13listing 2-15

numbers 1-2panels

Alter panel 2-11, 2-13Definition panel 2-8Directory panel 2-12, 2-14, 2-16, 2-17Display panel 2-16Maintenance menu 2-7

Index X-19

Station (continued)records 2-8standards 6-3

Statuschecking 7-11, 7-14codes 4-16, 6-18, 7-11command 7-22displays

content 4-1default (D= omitted) 4-12for specific schedules and jobs 4-9getting there 4-4History (D=H) 4-14issuing operator commands 6-20monitoring workload 1-10multiple CPUs 4-11Time (D=T) 4-13

field 2-28, 2-34nodes 7-32values 7-11

status displaying, schedule status 4-3Stopping Unicenter CA-Scheduler 2-6SUBMFAIL status 7-12SUBMIT

commandABENDED status 4-17, 7-16CANCLD status 4-17, 7-16definition 4-34, 6-16ENDED status 4-17FAILED status 4-17, 4-19, 7-16INTRPTD status 4-17UNKNOWN status 4-21

FAILED status 4-19, 4-34IN PROGRESS status 4-18

SUBMITD status 4-21, 6-18, 7-12SUBMITTED queue 4-6, 4-8Submitting jobs

across nodes 7-26automatically 1-7, 6-7, 6-8manually 4-22multiple CPUs 7-23RERUN command 6-16SUBMIT command 6-16

Successor Chain List report 1-12, 6-11SUCCESSOR JOBS field 4-37Successors 6-17, 7-2, 7-3, 7-17Summary

option for forecasts 6-12schedules 4-11status display 4-15

Supervisor authority level 2-20SYSID

definition 7-19installation option 7-20status 7-32

Systemcrash 3-68, 4-17, 6-18, 7-16overview 1-7

TTALTER command 4-32, 7-14TARGET option 7-24Techniques 7-1TEXT= parameter 4-23TIME

keyword, AUTOSCAN command 4-29status displays 4-13

Tips 6-1Tracking file

additions 6-16, 6-17backlogged work 7-8during autoscan 1-7, 6-2FORCE command 6-16global parameters 6-8inactive queue 7-2initialization 6-8multiple CPUs 7-22REQUESTED keyword 6-17user-defined reports 6-13

Transactions 7-10, 7-13

UUNCONNECTED status 7-32Unicenter CA-Driver

recovery 7-16, 7-18restart parameters 6-16

UNKNOWN status 4-21, 6-18UNPOST command 4-3, 4-26Unposting predecessors 4-3, 4-25Updating

database information 3-1jobs 3-91, 3-94schedules 3-20station records 2-10status 1-9user records 2-26

USE SIMTIME field 3-9, 3-11, 3-61, 3-71User

-defined events 5-27


User (continued)authority levels 2-20defining 2-22, 6-5deleting 2-29documentation 3-71, 6-9listing 2-30logon status 2-28maintaining 2-20

USER= parameter 4-23Userid

Alter panel 2-26, 2-29CANCLD status 4-17Definition panel 2-23Directory panel 2-28, 2-32, 2-33Display panel 2-31HELD status 4-17Maintenance menu 2-22, 2-34

USERS fieldcontent 3-16controls job records 3-58, 3-91NULL value 3-20purpose 3-5, 3-19

UsingHELP 2-4menus 2-3

Utility program 6-5, 6-10, 6-12

VVARY command 4-31, 7-33VERIFY field 3-27Verifying

applications 6-12workload selection 6-11

VIA parameter, CAIJNET macro 7-32VM commands 7-10VRETRY installation option 7-31VTAM communications 4-31, 7-26, 7-31VTAMLIM option, CAIJNET macro 7-33

WWAIT

queue 4-8, 4-21status 4-21, 4-22, 4-34, 6-18, 7-12, 7-15

WDAY keyword 5-3, 5-4, 5-12, 5-15, 5-21, 5-23WDOM keyword 5-3, 5-12, 5-20, 5-24WDOW keyword 5-3, 5-12, 5-15, 5-20Week keywords 5-3, 5-10, 5-12, 5-13, 5-15, 5-20WEEK-DAY keyword 5-3, 5-10, 5-16

WEEK-END keyword 5-3Weekends 5-12WEEKLY frequency 5-18, 5-19WOF keyword 5-3WOM keywords 5-13WORK WEEK field 5-13Workdays 5-2, 5-3, 5-4, 5-10, 5-12, 5-15, 5-17Workstations 1-2WOY keyword 5-15WWOM keyword 5-12, 5-15

ZZONE parameter, CAIJNET macro 7-32

Index X-21

Documents

Unicenter CA-Scheduler Job Management for VSE … CA-Scheduler Job Management for VSE . This documentation and related computer software program (hereinafter referred to as the “Documentation”)