CA-Scheduler® Online Guide

CA-Scheduler

Online Guide 9.0

SP3

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

This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies.

This right to print copies is limited to the period during which the license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to return to CA the reproduced copies or to certify to CA that same have been destroyed.

To the extent permitted by applicable law, CA provides this documentation “as is” without warranty of any kind, including without limitation, any implied warranties of merchantability, fitness for a particular purpose or noninfringement. In no event will CA be liable to the end user or any third party for any loss or damage, direct or indirect, from the use of this documentation, including without limitation, lost profits, business interruption, goodwill, or lost data, even if CA is expressly advised of such loss or damage.

The use of any product referenced in this documentation and this documentation is governed by the end user’s applicable license agreement.

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

Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.

2003 Computer Associates International, Inc.

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

Contents

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.1 Summary of Revisions in the Fourth Edition . . . . . . . . . . . . . . . . . . 1-21.2 Summary of Revisions in the Third Edition . . . . . . . . . . . . . . . . . . 1-31.3 Summary of Revisions in the Second Edition . . . . . . . . . . . . . . . . . 1-41.4 Summary of Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

1.4.1 Product Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-51.4.2 Documentation Changes . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

1.5 Panel Navigation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-91.6 CA-Scheduler Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-101.7 Sort . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-111.8 Locate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-131.9 PF Keys for ISPF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-151.10 PF Keys for CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-161.11 Tutorial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-171.12 CICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-181.13 CICS Editor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19

1.13.1 Adding Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-211.13.2 Copying a Block of Lines . . . . . . . . . . . . . . . . . . . . . . . . 1-221.13.3 Moving a Block of Lines . . . . . . . . . . . . . . . . . . . . . . . . 1-231.13.4 Deleting a Block of Lines . . . . . . . . . . . . . . . . . . . . . . . . 1-241.13.5 Repeating a Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-25

Chapter 2. Starting CA-Scheduler Online . . . . . . . . . . . . . . . . . . . . 2-12.1 Logging on to CA-Scheduler . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22.2 CA-Scheduler Main Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Chapter 3. Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Chapter 4. Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-14.1 Schedule Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2

4.1.1 Schedule Status Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-54.2 Job Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-16

4.2.1 Job Status Detail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-204.2.2 Predecessor Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-384.2.3 Staged JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-39

4.2.3.1 DEXPAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-404.2.3.2 RECALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-414.2.3.3 DPROMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-42

4.3 Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-43

Contents iii

4.3.1 Add Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-454.3.1.1 Add Job Command . . . . . . . . . . . . . . . . . . . . . . . . . 4-464.3.1.2 Add Pred Command . . . . . . . . . . . . . . . . . . . . . . . . . 4-61

4.3.2 Alloc Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-634.3.3 Cancel Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-65

4.3.3.1 Cancel Job Command . . . . . . . . . . . . . . . . . . . . . . . . 4-664.3.3.2 Cancel Schedule Command . . . . . . . . . . . . . . . . . . . . . 4-684.3.3.3 Cancel All Command . . . . . . . . . . . . . . . . . . . . . . . . 4-70

4.3.4 Complete Job Command . . . . . . . . . . . . . . . . . . . . . . . . . 4-714.3.5 Cancel Post (CP) Commands . . . . . . . . . . . . . . . . . . . . . . 4-73

4.3.5.1 Cancel Post (CP) Job Command . . . . . . . . . . . . . . . . . . 4-744.3.5.2 Cancel Post Schedule Command . . . . . . . . . . . . . . . . . . 4-77

4.3.6 Dealloc Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-804.3.7 Display Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-82

4.3.7.1 Display Alloc Command . . . . . . . . . . . . . . . . . . . . . . 4-834.3.7.2 Display Date Command . . . . . . . . . . . . . . . . . . . . . . . 4-844.3.7.3 Display Dataset Command . . . . . . . . . . . . . . . . . . . . . 4-854.3.7.4 Display MVSJobs Command . . . . . . . . . . . . . . . . . . . . 4-864.3.7.5 Display Network Command . . . . . . . . . . . . . . . . . . . . . 4-874.3.7.6 Display Security Command . . . . . . . . . . . . . . . . . . . . . 4-874.3.7.7 Display XPLAT Command . . . . . . . . . . . . . . . . . . . . . 4-884.3.7.8 Display Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-884.3.7.9 Display Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-884.3.7.10 Display VRM Command . . . . . . . . . . . . . . . . . . . . . 4-89

4.3.8 Force Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-904.3.8.1 Force Job Command . . . . . . . . . . . . . . . . . . . . . . . . . 4-914.3.8.2 Force Schedule Command . . . . . . . . . . . . . . . . . . . . . 4-93

4.3.9 Globals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-954.3.10 Hold Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-96

4.3.10.1 Hold Job Command . . . . . . . . . . . . . . . . . . . . . . . . 4-974.3.10.2 Hold Schedule Command . . . . . . . . . . . . . . . . . . . . . 4-994.3.10.3 Hold All Command . . . . . . . . . . . . . . . . . . . . . . . . 4-1004.3.10.4 Hold Submit Command . . . . . . . . . . . . . . . . . . . . . . 4-101

4.3.11 Messages Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1024.3.11.1 Query Messages . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1024.3.11.2 Send Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-103

4.3.12 Post Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1054.3.12.1 Post Job Command . . . . . . . . . . . . . . . . . . . . . . . . . 4-1064.3.12.2 Post Schedule Command . . . . . . . . . . . . . . . . . . . . . 4-1094.3.12.3 Post Job Start Command . . . . . . . . . . . . . . . . . . . . . . 4-1114.3.12.4 Post Schedule Start Command . . . . . . . . . . . . . . . . . . 4-1144.3.12.5 Post Dataset Command . . . . . . . . . . . . . . . . . . . . . . 4-1164.3.12.6 Post Unscheduled Job Command . . . . . . . . . . . . . . . . . 4-1184.3.12.7 Post Job Step Command . . . . . . . . . . . . . . . . . . . . . . 4-120

4.3.13 Purge Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1244.3.13.1 Purge Job Command . . . . . . . . . . . . . . . . . . . . . . . . 4-1254.3.13.2 Purge Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1274.3.13.3 Purge All . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-128

4.3.14 Release Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1294.3.14.1 Release Job Command . . . . . . . . . . . . . . . . . . . . . . . 4-1304.3.14.2 Release Schedule Command . . . . . . . . . . . . . . . . . . . . 4-132

iv Online Guide

4.3.14.3 Release All Command . . . . . . . . . . . . . . . . . . . . . . . 4-1334.3.14.4 Release Auto Command . . . . . . . . . . . . . . . . . . . . . . 4-1344.3.14.5 Release User Command . . . . . . . . . . . . . . . . . . . . . . 4-1354.3.14.6 Release Userall Command . . . . . . . . . . . . . . . . . . . . . 4-1364.3.14.7 Release Submit Command . . . . . . . . . . . . . . . . . . . . . 4-137

4.3.15 Request Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1384.3.15.1 Request Job Command . . . . . . . . . . . . . . . . . . . . . . . 4-1394.3.15.2 Request Schedule Command . . . . . . . . . . . . . . . . . . . 4-140

4.3.16 Rerun Job Command . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1424.3.17 Restage Job Command . . . . . . . . . . . . . . . . . . . . . . . . . 4-1464.3.18 Run Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-148

4.3.18.1 Run Job Command . . . . . . . . . . . . . . . . . . . . . . . . . 4-1494.3.18.2 Run Schedule Command . . . . . . . . . . . . . . . . . . . . . . 4-151

4.3.19 SREQ Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1534.3.19.1 SREQ Job Command . . . . . . . . . . . . . . . . . . . . . . . 4-1544.3.19.2 SREQ Schedule Command . . . . . . . . . . . . . . . . . . . . 4-156

4.3.20 Start Job Command . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1584.3.21 Submit Job Command . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1604.3.22 Unpost Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-164

4.3.22.1 Unpost Job Command . . . . . . . . . . . . . . . . . . . . . . . 4-1654.3.22.2 Unpost Schedule Command . . . . . . . . . . . . . . . . . . . . 4-1684.3.22.3 Unpost Job Start Command . . . . . . . . . . . . . . . . . . . . 4-1704.3.22.4 Unpost Schedule Start Command . . . . . . . . . . . . . . . . . 4-1734.3.22.5 Unpost Dataset Command . . . . . . . . . . . . . . . . . . . . . 4-1754.3.22.6 Unpost Unscheduled Job . . . . . . . . . . . . . . . . . . . . . . 4-1774.3.22.7 Unpost Job Step Command . . . . . . . . . . . . . . . . . . . . 4-179

4.3.23 Vary Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1834.3.23.1 Vary Active Command . . . . . . . . . . . . . . . . . . . . . . 4-1844.3.23.2 Vary Inactive Command . . . . . . . . . . . . . . . . . . . . . . 4-1854.3.23.3 Vary VRM Command . . . . . . . . . . . . . . . . . . . . . . . 4-186

4.4 FREECMD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-187

Chapter 5. Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15.1 Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3

5.1.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45.1.2 Schedule Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

5.1.2.1 Schedule Definition . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65.1.2.2 Schedule Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24

5.1.3 Batch Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-245.1.3.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-245.1.3.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24

5.1.4 Copying a Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-255.2 Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-26

5.2.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-275.2.2 Job Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28

5.2.2.1 Job Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-295.2.2.2 Job Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-575.2.2.3 Job Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-585.2.2.4 Driver Parms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-625.2.2.5 Virtual Resources . . . . . . . . . . . . . . . . . . . . . . . . . . 5-63

Contents v

5.2.3 Batch Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-645.2.3.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-645.2.3.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-645.2.3.3 Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-645.2.3.4 Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-64

5.2.4 Copying a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-655.3 User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66

5.3.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-675.3.2 User ID Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-685.3.3 Batch Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72

5.3.3.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-725.3.3.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72

5.3.4 Copying a User ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-725.4 Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73

5.4.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-745.4.2 Station Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-755.4.3 Batch Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77

5.4.3.1 Example 1: Define a CPU station . . . . . . . . . . . . . . . . . 5-775.4.3.2 Example 2: Define a JCL setup station (station 39) . . . . . . . . 5-77

5.4.4 Copying a Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-775.5 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78

5.5.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-795.5.2 Resource Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-80

5.5.2.1 Nonshared Resources . . . . . . . . . . . . . . . . . . . . . . . . 5-815.5.2.2 Shared Resources . . . . . . . . . . . . . . . . . . . . . . . . . . 5-89

5.5.3 Batch Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-925.5.3.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-925.5.3.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-92

5.6 Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-935.6.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-945.6.2 Calendar Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-955.6.3 Copying a Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-99

5.7 Datetables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1005.7.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1015.7.2 Date Table Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1025.7.3 Copying a Date Table . . . . . . . . . . . . . . . . . . . . . . . . . . 5-105

5.8 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1065.8.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1085.8.2 Documentation Text . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1085.8.3 Copying a Documentation Member . . . . . . . . . . . . . . . . . . . 5-109

5.9 Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1105.9.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1115.9.2 Flow Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1115.9.3 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-114

5.10 Virtual Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1155.10.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1165.10.2 Virtual Resource Definition . . . . . . . . . . . . . . . . . . . . . . . 5-117

5.10.2.1 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1185.10.3 VRM Job List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1195.10.4 Job/VRM Association . . . . . . . . . . . . . . . . . . . . . . . . . . 5-120

5.10.4.1 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-122

vi Online Guide

5.10.4.2 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1225.10.4.3 ENQ Virtual Resources . . . . . . . . . . . . . . . . . . . . . . 5-1235.10.4.4 Count Virtual Resources . . . . . . . . . . . . . . . . . . . . . . 5-1245.10.4.5 Simple Virtual Resources . . . . . . . . . . . . . . . . . . . . . 5-124

Chapter 6. Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.1 Analyze . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3

6.1.1 Analyze Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-46.1.2 Analyze Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

6.2 Report Abend . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-86.3 Report Audit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-106.4 Report Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-126.5 Report Datetran . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-146.6 Job Average . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-166.7 Job History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-176.8 Report Mailbox . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-186.9 Report Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-206.10 Successors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-21

6.10.1 Jobchain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-226.10.2 Scdchain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-246.10.3 Cjobchan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-266.10.4 Cscdchan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-28

6.11 Predecessors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-306.11.1 Jobrchan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-316.11.2 Scdrchan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-336.11.3 Cjobrchn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-356.11.4 Cscdrchn . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-37

Chapter 7. Criteria Language . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17.1 Criteria Vocabulary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

7.1.1 Reserved Words for Use in Boolean Expressions . . . . . . . . . . . . 7-37.1.2 Reserved Words Used for Selection . . . . . . . . . . . . . . . . . . . . 7-37.1.3 Reserved Words for Use in Predecessors . . . . . . . . . . . . . . . . . 7-57.1.4 Combining Selection and Predecessor Criteria Vocabulary . . . . . . . 7-67.1.5 Using Multiple Conditions with ANDs and ORs . . . . . . . . . . . . . 7-97.1.6 Effect of NOT Condition on Predecessors . . . . . . . . . . . . . . . 7-107.1.7 Recommended Method for Defining Selection Criteria . . . . . . . . 7-11

7.2 Calendar Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-127.2.1 Gregorian Calendar . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-127.2.2 Date Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-15

7.2.2.1 Workday Keywords . . . . . . . . . . . . . . . . . . . . . . . . . 7-157.2.2.2 Accounting-Period Keywords . . . . . . . . . . . . . . . . . . . . 7-167.2.2.3 Summary of Date Tables . . . . . . . . . . . . . . . . . . . . . . 7-197.2.2.4 Date Translation Report . . . . . . . . . . . . . . . . . . . . . . . 7-19

7.2.3 Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-217.2.3.1 Step 1: Define the Prototype Calendar . . . . . . . . . . . . . . . 7-217.2.3.2 Step 2: Define Daily, Weekly and Monthly Calendars . . . . . . 7-23

7.3 Some Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-247.3.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-247.3.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-24

Contents vii

7.3.3 Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-247.3.4 Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-257.3.5 Example 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-257.3.6 Example 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-267.3.7 Example 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-277.3.8 Example 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-277.3.9 Example 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-287.3.10 Example 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-297.3.11 Example 11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-307.3.12 Example 12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-307.3.13 Example 13 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-317.3.14 Example 14 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31

7.4 What Is Wrong with these Examples? . . . . . . . . . . . . . . . . . . . . 7-327.4.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-327.4.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-327.4.3 Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-327.4.4 Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-337.4.5 Example 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-347.4.6 Example 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-347.4.7 Example 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-35

7.5 Review of Tips to Remember . . . . . . . . . . . . . . . . . . . . . . . . . 7-367.5.1 Pitfalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-36

7.6 Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-377.6.1 Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-37

7.7 Summing Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-387.8 Criteria Vocabulary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-39

7.8.1 Reserved Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-397.9 Gregorian Calendar Conditions . . . . . . . . . . . . . . . . . . . . . . . . 7-417.10 Workday Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-447.11 Accounting Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-46

Chapter 8. Using the Autoscan Command File . . . . . . . . . . . . . . . . . 8-1

Chapter 9. Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-19.1 Commonly Asked Questions . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

9.1.1 Startup Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-49.1.1.1 When Should Autoscan be Performed? . . . . . . . . . . . . . . . 9-49.1.1.2 What Is the General Standard for Numbering Stations? . . . . . . 9-49.1.1.3 Should I Use Date Tables or Calendars? . . . . . . . . . . . . . . . 9-59.1.1.4 When Should I Define a New Date Table Versus a New Cycle in

an Existing Date Table? . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-59.1.2 Database Maintenance Questions . . . . . . . . . . . . . . . . . . . . . 9-6

9.1.2.1 How Should I Organize My Schedules? . . . . . . . . . . . . . . . 9-69.1.2.2 When Should a Job be Staged? . . . . . . . . . . . . . . . . . . . . 9-69.1.2.3 When Is a Job Submitted? . . . . . . . . . . . . . . . . . . . . . . 9-79.1.2.4 What Are Global Parameters and When Are They Used? . . . . . 9-89.1.2.5 How Can I Run a Job Like an Edit Check Repeatedly Until its

Output Is Correct? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-109.1.3 Questions About Analyzing the Database . . . . . . . . . . . . . . . . 9-11

9.1.3.1 How Can I Prevent Predecessor Loops (Deadlocks)? . . . . . . . 9-119.1.3.2 When Should I Run Analyze Reports? . . . . . . . . . . . . . . . 9-12

viii Online Guide

9.1.3.3 What Effect Does a Deadlock Have? . . . . . . . . . . . . . . . 9-129.1.3.4 When Should I Run Forecasts? . . . . . . . . . . . . . . . . . . . 9-149.1.3.5 When Should I Run Simulation? . . . . . . . . . . . . . . . . . . 9-149.1.3.6 How Do I Plan When to Run a New Application? . . . . . . . . 9-159.1.3.7 How Do I Verify a New Application? . . . . . . . . . . . . . . . 9-159.1.3.8 How Can I Can Create My Own Reports? . . . . . . . . . . . . 9-18

9.1.4 Daily Processing Questions . . . . . . . . . . . . . . . . . . . . . . . 9-209.1.4.1 From Where Can I Issue CA-Scheduler Control Commands? . . 9-209.1.4.2 What Is the Difference Between FORCE, SUBMIT, RERUN,

RUN, ADD, REQUEST, and SREQ? . . . . . . . . . . . . . . . . . . . 9-209.1.4.3 When Is the PRED Flag Reset? . . . . . . . . . . . . . . . . . . 9-229.1.4.4 What Happens If CA-Scheduler is Shut Down? . . . . . . . . . . 9-239.1.4.5 What Happens If CAIENF is Shut Down? . . . . . . . . . . . . 9-249.1.4.6 What Happens If a System Crash Occurs? . . . . . . . . . . . . 9-24

9.1.5 What Do I Do with Jobs in UNKNOWN Status? . . . . . . . . . . . 9-259.1.6 Pitfalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26

9.1.6.1 Using Control Commands on the Status Panels . . . . . . . . . . 9-269.1.6.2 Canceling and Purging a Job . . . . . . . . . . . . . . . . . . . . 9-269.1.6.3 Changing Criteria on Selected Jobs . . . . . . . . . . . . . . . . 9-279.1.6.4 Backlogging Jobs Over Two Autoscans in $MVS, $DYN and User

Defined Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-279.1.6.5 Resetting Global Parameters . . . . . . . . . . . . . . . . . . . . 9-28

Chapter 10. Techniques . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-110.1 Criteria Language Examples Relating to Criteria Rules . . . . . . . . . . 10-210.2 More Examples of Criteria Language . . . . . . . . . . . . . . . . . . . . 10-4

10.2.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-410.2.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-410.2.3 Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-410.2.4 Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-410.2.5 Example 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-510.2.6 Example 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-510.2.7 Example 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-6

10.3 On-Request Schedules and Jobs . . . . . . . . . . . . . . . . . . . . . . . 10-810.3.1 Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-810.3.2 Criteria Language Subtleties . . . . . . . . . . . . . . . . . . . . . . 10-9

10.3.2.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-910.3.2.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-910.3.2.3 Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-910.3.2.4 Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-910.3.2.5 Example 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1010.3.2.6 Example 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1010.3.2.7 Example 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1110.3.2.8 Example 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1110.3.2.9 Example 9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1210.3.2.10 Example 10 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-12

10.4 Backlogged Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1310.5 Restart/Recovery of Scheduled Jobs . . . . . . . . . . . . . . . . . . . . . 10-15

10.5.1 Restart Through CA-11 . . . . . . . . . . . . . . . . . . . . . . . . . 10-1510.5.2 Inquiring About Jobs to be Recovered . . . . . . . . . . . . . . . . . 10-16

Contents ix

10.5.3 Automatic Recovery Options . . . . . . . . . . . . . . . . . . . . . . 10-1610.5.4 Driver Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 10-17

10.5.4.1 Step-Level Restart . . . . . . . . . . . . . . . . . . . . . . . . . 10-1810.5.4.2 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1910.5.4.3 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20

Chapter 11. Remote Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . 11-111.1 Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-2

11.1.1 Comments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-211.1.2 Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-211.1.3 Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-311.1.4 Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-411.1.5 User . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-411.1.6 Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-5

11.2 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-611.2.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-611.2.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-611.2.3 Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-611.2.4 Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6

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

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

x Online Guide

Chapter 1. Introduction

This guide serves as the primary reference for the online functions of CA-Scheduler.

Chapter 1. Introduction 1-1

1.1 Summary of Revisions in the Fourth Edition

1.1 Summary of Revisions in the Fourth Edition

The fourth edition of this guide includes these changes (see revision marks in themargins):

■ Online Julian dates are seven-digits. For more information, see 4.1.1, “ScheduleStatus Detail” on page 4-5 and 4.2.1, “Job Status Detail” on page 4-20.

■ The SU Flag field is new in 4.2.1, “Job Status Detail” on page 4-20 and 5.2.2.1,“Job Definition” on page 5-29.

■ The panel changed in 5.1.1, “Directory” on page 5-4.

1-2 Online Guide

1.2 Summary of Revisions in the Third Edition

1.2 Summary of Revisions in the Third Edition

The third edition of this guide includes these changes (see revision marks in themargins):

■ We changed the descriptions of the Must Start, Must End, and MaximumExecution fields in 4.3.1.1, “Add Job Command” on page 4-46.

■ We changed the descriptions of the Must Start, Must End, Maximum Execution,and Schedule Skipped fields in 5.1.2.1, “Schedule Definition” on page 5-6.

■ We changed the descriptions of the Must Start, Must End, Maximum Execution,and Schedule Skipped fields in 5.2.2.1, “Job Definition” on page 5-29.

■ We changed the descriptions of option 3 and option 9 in Chapter 6, “Reports” onpage 6-1.

■ We changed several paragraphs of 6.3, “Report Audit” on page 6-10.

■ We changed several paragraphs of 6.8, “Report Mailbox” on page 6-18.

■ We changed the introduction of 9.1.4.5, “What Happens If CAIENF is ShutDown?” on page 9-24.


1.3 Summary of Revisions in the Second Edition

1.3 Summary of Revisions in the Second Edition

The second edition of this guide includes these changes (see revision marks in themargins):

■ 01 the higher priority for both schedule priority in 5.1.2.1, “Schedule Definition”on page 5-6 and internal priority in 5.2.2.1, “Job Definition” on page 5-29.

1-4 Online Guide

1.4 Summary of Revisions


The summary includes changes to CA-Scheduler and to the documentation.

1.4.1 Product Features

CA-Scheduler 9.0 has the following new features:

■ CA-Datacom

CA-Datacom is now used to hold the scheduling database (master file) as well asthe active workload (tracking file). Staged JCL and documentation are also storedin CA-Datacom. CA-Datacom provides many advantages over CATMAN (theprevious access method) such as backup-while-open, forward recovery, and fasteraccess.

CA-Datacom also allows CA-Scheduler to exploit 31-bit storage, relieving virtualstorage shortage problems in many sites.

See the CA-Scheduler Systems Programmer Guide for more information.

■ Virtual Resource Manager

Virtual Resource Management introduces a new way to define resourcedependencies for jobs. Virtual resources can be defined as required for jobprocessing. CA-Scheduler ensures that the defined requirements are met beforesubmitting the job for execution.

See the CA-Scheduler Online Guide for more information.

■ Active Workload

When CA-Scheduler determines that a job or schedule is to be executed, allinformation about that job or schedule is copied to what used to be called thetracking file. The active workload now includes everything needed to submit andtrack the work in the correct order. Changes made to the scheduling database(master file), such as changing a job's criteria, do not impact the current copy ofthe job in the active workload.

Any changes to a schedule or job in the database take effect the next time theschedule or job is added to the active workload.

■ Workload Manager Interface

CA-Scheduler interfaces in two ways with the IBM Workload Manager (WLM).First, a WLM scheduling environment may optionally be inserted into JCL duringsubmission. Second, a WLM scheduling resource may be set ON whenCA-Scheduler starts and OFF when CA-Scheduler shuts down. The WLMscheduling environment and WLM scheduling resource may be used to limitwhich systems jobs execute on, or even what CPU resources are assigned to jobs.

See the CA-Scheduler Interfaces Guide for more information.



■ Online Sort/Locate

In the ISPF online, all scrollable displays, such as status and directory lists, can besorted by any of the displayed columns. The command SORT xxx can be entered,where xxx is one of the column headers. The display can be positioned to aparticular row by using the Locate command. The command L yyy can be entered,where yyy is the value to be found. The most recently sorted column is used tofind the Locate string.

In the CICS online, the Locate command may be used to position the scrollabledisplays. The leftmost column is used to find the Locate string.


■ Hold/Release Submit

A new command, HOLD SUBMIT, prevents all submission without modifying thestatus of any schedules or jobs, as HOLD ALL does. Jobs added to the activeworkload after the HOLD SUBMIT command are also not submitted, unlikeHOLD ALL. The HOLD SUBMIT status is saved across restarts of CA-Scheduler.When the RELEASE SUBMIT command is issued, all jobs that could not besubmitted due to the HOLD SUBMIT are submitted.

See the CA-Scheduler Command Reference Guide for more information.

■ Batch Datetable/Calendar Support

Datetables and calendars may now be maintained and displayed in batch.


■ Backwards JOBCHAIN

New variations of the JOBCHAIN reports are available to display a job orschedule's predecessors instead of their successors.

See the CA-Scheduler Reports Guide for more information.

■ Temporary Predecessors

A new command, ADD PRED, allows the definition of a one-timepredecessor/successor relationship between two jobs in the active workload. Thepredecessor job may not be complete, and the successor job may not have startedwhen the command is issued.


■ Cross-Platform Job Definitions

Jobs may be defined to the scheduling database (master file) with a cross-platformnode, userid, domain, and password. If this information is also specified in thejob's "JCL," the "JCL" copy overrides the database copy.


1-6 Online Guide


■ SKIPPED Messages

A message may be generated when a job or schedule is excluded from the activeworkload due to a nonzero SKIP value. The message may be queued for a specificCA-Scheduler user, issued on the console, or sent to the mailbox.

See the CA-Scheduler Systems Programmer Guide or the CA-Scheduler OnlineGuide for more information.

■ MAILBOX and Audit Trail

The mailbox and audit trail information is now stored in the CA-Schedulerdatabase instead of in CAIENF. Users no longer need to be defined to CAIENF toissue the REPORT AUDIT or REPORT MAILBOX commands. The DELETEAUDIT and DELETE MAILBOX commands should be issued daily to removeaudit trail and mailbox entries more than a given number of days old.


■ Command Response Messages

Messages issued in response to an OS/390 modify command (that is, FCASCHD,xxx) are issued to the originating console. This allows consoleautomation products such as CA-OPS/MVS II to "see" the response to acommand. Modify command output is also captured and displayed by SDSF.Time-out conditions may prevent either console automation products or SDSFfrom seeing the command responses.


■ Exits

All exits are now called AMODE 31 and RMODE ANY. Some client exits mayneed to be reworked to tolerate AMODE 31.


■ Better Handling of OS/390 Modify (F) Commands

When an OS/390 modify command is received (F CASCHD,xxx) while an earliermodify command is being processed, CA-Scheduler automatically retains thecommand and issues it when the command processor is available. Any number ofcommands may be queued waiting for the command processor. Messages areissued when a command is delayed and when it is executed.



1.4.2 Documentation Changes

■ The documentation set has been engineered to take advantage of the latesttechnology for online viewing, keyword searching, book marking, and printing.This set contains a hardcopy CA-Scheduler Getting Started guide and Version 9.0of CA-Scheduler for OS/390 documentation in both IBM BookManager andAdobe Acrobat Reader format on the tape.

■ The CA-Scheduler Getting Started guide replaces the CA-Scheduler InstallationGuide.

■ Reading Syntax Diagrams in the Command Reference Guide explains how to readthe command syntax used in all guides.

1-8 Online Guide

1.5 Panel Navigation

1.5 Panel Navigation

Users may jump to any panel in CA-Scheduler from any other panel by using the jumpcharacter, "=", followed by the menu number. For example, to reach the MonitorCommands menu, enter "=1.3" from any non-scrollable field on any panel inCA-Scheduler.

The CA-Scheduler dialog may be in use concurrently on the same TSO ISPF sessionas many times as needed. Split panel is fully supported.

Note: The CICS interface does not support split panel or the jump character (=). TheEND command (normally PF3/15) returns you to the panel where the functionstarted, which is not necessarily the last menu you saw. Certain scrollablepanels in ISPF will show the total number of rows being displayed. The totalnumber is not displayed for CICS.


1.6 CA-Scheduler Commands

1.6 CA-Scheduler Commands

You can enter CA-Scheduler commands on any panel from the first input field (theCOMMAND or OPTION field). Enter "SCHD" followed by the command, like this:

� � ------------------------- CA-SCHEDULER 9.� xxyy (SCHD) ------------------------

OPTION ===> schd run j n=xxx

� OPTIONS - Specify user preferences

1 MONITOR - Control and monitor the current workload

2 DATABASE - Define and maintain workload definition

3 REPORTS - Execute and view reports

X EXIT - Exit CA-Scheduler

�-------------------------------------------�

� �

� CA-Scheduler copyright 1989, 2��1 �

� Computer Associates International, Inc. �

� �

�-------------------------------------------�

� �

You can enter both database commands (DEFINE, SYNCHK, ANALYZE) andtracking commands (RUN, CANCEL, FORCE). Tracking commands do not require an"SC" before the command, but the "SC" is supported if entered. (Tracking commandsrun in batch using utility CAJUCMD0 still require the SC prefix.)

This interface does not support some commands, such as FORMAT and SIMULATE.Commands that could be interpreted as either tracking commands or simulationcommands (such as RUN) are interpreted as tracking commands.

The output of the command is displayed in a browse panel:

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) COMMAND OUTPUT ----------------

COMMAND ===> SCROLL ===> PAGE

�� TOP OF DATA ��

SC RUN J N=XXX

CACM116I RUN JOB XXX QUEUED

�� BOTTOM OF DATA ��

� �

1-10 Online Guide

1.7 Sort

1.7 Sort

All of the scrollable displays, such as status and directory displays, may be sorted byany of the columns displayed. To sort a display, enter the command "SORT xxx"where xxx is the column title you want sorted. For example:

� �------------------ CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULES Row 1 to 19 of 5�

COMMAND ===> sort date SCROLL ===> CSR

Schedule Sys AutoSel Jobs Date Time Userid

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

_ ABEND NO ��1 1999/�9/23 15:46:45 USER��3

_ ABEND1 NO ��1 2��/�6/22 15:2�:�8 USER��3

_ ABEND2 NO ��1 2��/�6/22 15:2�:2� USER��3

_ AIX NO ��1 2��/�3/15 11:5�:�8 USER��3

_ BADJOB NO ��1 1999/�9/21 11:15:15 USER��3

_ BADPRED NO �� 2��/�7/3� 13:45:59 USER��3

_ BATCH�1 NO ��99 2��1/�1/11 13:47:58 GUEST�2

_ BATCH�2 NO ��99 2��1/�1/11 13:48:19 GUEST�2

_ BATCH�3 NO ��99 2��1/�1/11 13:48:36 GUEST�2

_ CDAY NO ��1 2��/�8/18 13:25:54 USER��3

_ CLEANUP YES ��1 2��1/�1/12 �9:�7:41 USER��3

_ CMD� NO ��98 2��1/�1/18 15:�8:13 GUEST�2

_ DATETAB NO ��1 2��/�6/23 2�:51:39 USER��3

_ DAYOWK YES ��7 1999/�9/�4 �9:44:�1 USER��3

_ DLOCK NO ��3 2��/�7/29 12:41:22 USER��3

_ DLUGG NO 1�� 2��/�2/19 12:�9:�5 USER��3

_ DRIVERS NO ��1 2��/�5/�6 �8:56:28 USER��3

_ DUPS1 YES ��1 1999/1�/2� 12:28:39 USER��3

_ DUPS2 YES ��1 1999/1�/2� 12:28:42 USER��3

� �


1.7 Sort

After the sort command is issued, the following would be displayed:

� �-------------------- CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULES Row 1 to 19 of 14�

COMMAND ===> SCROLL ===> CSR


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

_ QADEMO2A NO ��1 2��1/�2/1� 15:47:35 GUEST�3

_ QADEMO3 YES ��1 2��1/�2/1� 15:47:35 GUEST�3

_ QADEMO4 YES ��12 2��1/�2/1� 15:47:35 GUEST�3

_ QADEMO5 YES ��4 2��1/�2/1� 15:47:35 GUEST�3

_ QADEMO6 YES ��1 2��1/�2/1� 15:47:35 GUEST�3

_ QADEMO1 YES ��4 2��1/�2/1� 15:47:3� GUEST�3

_ QADEMO2 YES ��8 2��1/�2/1� 15:47:3� GUEST�3

_ QADEMO YES ��18 2��1/�2/1� 15:47:24 GUEST�3

_ SAMPSCHD NO ��5 2��1/�2/1� �8:39:51 USER��3

_ Q1427SC1 YES �� 2��1/�2/�3 �9:�2:44 GUEST�3

_ Q1425S61 NO �� 2��1/�2/�3 �8:55:32 GUEST�3

_ Q1425S62 NO �� 2��1/�2/�3 �8:55:32 GUEST�3

_ Q1425S63 NO �� 2��1/�2/�3 �8:55:32 GUEST�3

_ Q1425S64 NO �� 2��1/�2/�3 �8:55:32 GUEST�3

_ Q1425S65 NO �� 2��1/�2/�3 �8:55:32 GUEST�3

_ Q1425S66 NO �� 2��1/�2/�3 �8:55:32 GUEST�3

_ Q1425S67 NO �� 2��1/�2/�3 �8:55:32 GUEST�3

_ Q1425S68 NO �� 2��1/�2/�3 �8:55:32 GUEST�3

_ Q1425S69 NO �� 2��1/�2/�3 �8:55:32 GUEST�3

� �

All rows must be read before the display can be sorted. This may cause a delay beforethe first sort can be completed.

Note: The SORT command is only available on ISPF, not on CICS.

1-12 Online Guide

1.8 Locate

1.8 Locate

All of the scrollable displays, such as status and directory displays, support the Locatecommand to position the display to a particular row. To reposition the display towhere a given value would be, issue "L xxx" where xxx is the value to find. Thecolumn searched is the one most recently sorted with the SORT command. If theSORT command has not been entered, the leftmost column is searched.

For example:

� �-------------------- CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULES Row 1 to 19 of 5�

COMMAND ===> L DUPS SCROLL ===> CSR


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

_ ABEND NO ��1 1999/�9/23 15:46:45 USER��3

_ ABEND1 NO ��1 2��/�6/22 15:2�:�8 USER��3

_ ABEND2 NO ��1 2��/�6/22 15:2�:2� USER��3

_ AIX NO ��1 2��/�3/15 11:5�:�8 USER��3

_ BADJOB NO ��1 1999/�9/21 11:15:15 USER��3

_ BADPRED NO �� 2��/�7/3� 13:45:59 USER��3

_ BATCH�1 NO ��99 2��1/�1/11 13:47:58 GUEST�2

_ BATCH�2 NO ��99 2��1/�1/11 13:48:19 GUEST�2

_ BATCH�3 NO ��99 2��1/�1/11 13:48:36 GUEST�2

_ CDAY NO ��1 2��/�8/18 13:25:54 USER��3

_ CLEANUP YES ��1 2��1/�1/12 �9:�7:41 USER��3

_ CMD� NO ��98 2��1/�1/18 15:�8:13 GUEST�2

_ DATETAB NO ��1 2��/�6/23 2�:51:39 USER��3

_ DAYOWK YES ��7 1999/�9/�4 �9:44:�1 USER��3

_ DLOCK NO ��3 2��/�7/29 12:41:22 USER��3

_ DLUGG NO 1�� 2��/�2/19 12:�9:�5 USER��3

_ DRIVERS NO ��1 2��/�5/�6 �8:56:28 USER��3

_ DUPS1 YES ��1 1999/1�/2� 12:28:39 USER��3

_ DUPS2 YES ��1 1999/1�/2� 12:28:42 USER��3

� �


1.8 Locate

After the Locate command, the display would show:

� �-------------------- CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULE Row 17 to 35 of 14�



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

_ DRIVERS NO ��1 2��/�5/�6 �8:56:28 USER��3

_ DUPS1 YES ��1 1999/1�/2� 12:28:39 USER��3

_ DUPS2 YES ��1 1999/1�/2� 12:28:42 USER��3

_ DUPS3 YES ��1 1999/1�/2� 12:28:5� USER��3

_ DUPS4 YES ��1 1999/1�/2� 12:29:�� USER��3

_ DUPS5 YES ��1 1999/1�/2� 12:29:�3 USER��3

_ FLOW�1 NO ��2 2��/�6/16 �9:3�:48 USER��3

_ GSBACK XE87 NO ��2 2��1/�1/31 �9:52:12 GUEST�1

_ GSCR YES ��1 2��1/�1/11 14:5�:4� GUEST�1

_ GSCRI YES ��3 2��1/�1/26 13:38:2� GUEST�2

_ JCKTEST NO ��1 1999/12/18 12:13:48 USER��3

_ JOBFLOW NO ��5 1999/1�/14 �9:26:39 USER��3

_ NONCPU NO ��3 2��/�8/1� 1�:38:33 USER��3

_ NONCPU2 NO ��1 2��/�8/1� 1�:41:24 USER��3

_ PAIX NO �1�� 2��/�3/15 12:27:12 USER��3

_ PAULNT NO ��1 1999/�8/�3 �8:48:28 USER��3

_ PHINK NO �1�� 2��/�2/25 15:48:�2 USER��3

_ PYRAMID YES ��26 2��/1�/29 14:27:21 USER��3

_ QADEMO YES ��18 2��1/�2/1� 15:47:24 GUEST�3

� �

Note: Because CICS does not support the SORT command, the Locate commandalways searches the leftmost column.

1-14 Online Guide

1.9 PF Keys for ISPF

1.9 PF Keys for ISPF

ISPF allows users to change the settings of the PF keys. This manual assumes that thePF keys are set to the default values, as follows:

CA-Scheduler runs in a new application pool (SCHD). All PF keys are set to thedefault values when users first access it. If a user changes a PF key, it is up to the userto issue the correct command to CA-Scheduler. For example, PF5 is documented asrefreshing a list of schedules or jobs in the status display. Since PF5 is normally set toRfind, CA-Scheduler is really using the Rfind command. If PF5 is set to some othercommand, then pressing PF5 will not refresh the list of jobs or schedules.

Key Value

PF1/13 Help

PF2/14 Split

PF3/15 End

PF4/16 Return

PF5/17 Rfind

PF6/18 Rchange

PF7/19 Up

PF8/20 Down

PF9/21 Swap

PF10/22 Left

PF11/23 Right

PF12/24 Retrieve


1.10 PF Keys for CICS

1.10 PF Keys for CICS

The CICS interface allows users to change the settings of the PF keys. This manualassumes that the PF keys are set to the default values, as follows:

All PF keys are set to the default values when each user first accesses CA-Scheduleron CICS. If a user changes a PF key, it is up to the user to issue the correct commandto CA-Scheduler. For example, PF8 is documented as the DOWN command. If PF8 isset to any other command, then pressing PF8 will not page down.

Key Value

PF1/13 DISPLAY LONG MESSAGE LINE AFTER ERROR

PF3/15 END

PF5/17 REPEAT "FIND" COMMAND (EDITOR ONLY)

PF6/18 REPEAT "CHANGE" COMMAND (EDITOR ONLY)

PF7/19 UP

PF8/20 DOWN

PF10/22 LEFT

PF11/23 RIGHT

1-16 Online Guide

1.11 Tutorial

1.11 Tutorial

You can obtain information about any ISPF panel and the fields on the panel bypressing PF1/13 (HELP). The CICS interface does not currently support tutorial panels.


1.12 CICS

1.12 CICS

The CA-Scheduler CICS interface has been designed to match the ISPF environment,wherever reasonable. ISPF split-panel and the ISPF editor, for example, are notsupported. The base functionality of the product is the same for both ISPF and CICS.

The panel samples in this guide are from ISPF. CICS panels should look similar to theISPF versions but may not look exactly the same.

1-18 Online Guide

1.13 CICS Editor

1.13 CICS Editor

Under ISPF, CA-Scheduler uses the ISPF editor to modify criteria, staged JCL, anddocumentation. Since the ISPF editor is not available under CICS, a nativeCA-Scheduler editor is used.

This section documents how to use the CA-Scheduler native editor in CICS.

You may issue the following commands on the command line:

BOTTOM Position the display to the end of the member.

Syntax: BOTTOMAbbreviation: BOT

CHANGE Replace one string with another. You may optionally specify the columnwhere the strings begin.

Syntax: CHANGE <oldstring> <newstring> column“Abbreviations: CH, C

See also RCHANGE.

COLUMN Display a column scale line.

Syntax: COLUMNAbbreviation: COLS

DELETE (criteria only) Delete the criteria currently displayed from theCA-Scheduler database.

Syntax: DELETE

DEXPAND (staged JCL only) See 4.2.3.1, “DEXPAND” on page 4-40.

Syntax: DEXPAND

DPROMPT (staged JCL only) See 4.2.3.3, “DPROMPT” on page 4-42.

Syntax: DPROMPT

FIND Locate a character string in the member and position the display to it.You may optionally specify a column to search.

Syntax: FIND <string> column“Abbreviations: FI, F

See also RFIND.

LEFT Shift the display of data to the left. Normally set to PF key 10/22.

Syntax: LEFT

RECALL (staged JCL only) See 4.2.3.2, “RECALL” on page 4-41.

Syntax: RECALL


1.13 CICS Editor

RESET Removes the output of the DEXPAND command. See 4.2.3.1,“DEXPAND” on page 4-40.

Syntax: RESET

RIGHT Shift the display of data to the right. Normally set to PF key 11/23.

Syntax: RIGHT

SAVE Write the data being edited to the temporary file. This does NOT save it tothe CA-Scheduler files.

Syntax: SAVE

TOP Position the display to the beginning of the member.

Syntax: TOP

The following commands may be entered in the command area (the numbers to the leftof each line).

AFTER The target of a MOVE or COPY command is after this line.

Syntax: A

BEFORE The target of a MOVE or COPY command is before this line.

Syntax: B

COPY Copy one or more lines to another location in the member. You indicatewhere the lines should be copied with the AFTER or BEFORE commands.

Syntax: C nn“ (where nn is 1 to 18 lines. The default is 1.)CC (block of lines. Enter CC on the first and last linesof the block.)

DELETE Remove one or more lines from the member.

Syntax: D nn“ (where nn is 1 to 18 lines. The default is 1.)DD (block of lines. Enter DD on the first and last linesof the block.)

INSERT Add one or more blank lines to the member. The lines are added after theline on which you enter the command.

Syntax: I nn“ (where nn is 1 to 18 lines. The default is 1.)

MOVE Move one or more lines to another location in the member. You indicatewhere the lines should be moved with the AFTER or BEFORE commands.

Syntax: M nn“ (where nn is 1 to 18 lines. The default is 1.)MM (block of lines. Enter CC on the first and last linesof the block.)

REPEAT Duplicate a line one or more times. The new copies of the line appearimmediately following the original.

Syntax: R nn“ (where nn is 1 to 18 new copies. The default is1.)

1-20 Online Guide

1.13 CICS Editor

1.13.1 Adding Lines

To add 3 lines:

� �------------------------------------------------------------------------

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

��1 WDAY

��2 THIS IS LINE 2.




-> I3 ��6 THIS IS LINE 6.




��1� THIS IS LINE 1�.

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

� �

The result will be:

� �------------------------------------------------------------------------

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

��1 WDAY






-> ��7

-> ��8

-> ��9

��1� THIS IS LINE 7.



��13 THIS IS LINE 1�.

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

� �


1.13 CICS Editor

1.13.2 Copying a Block of Lines

To copy lines 1-3 after line 6:

� �------------------------------------------------------------------------

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

->>CC��1 WDAY


->>CC��3 THIS IS LINE 3.



-> A��6 THIS IS LINE 6.





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

� �

The result will be:

� �------------------------------------------------------------------------

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

��1 WDAY






-> ��7 WDAY

-> ��8 THIS IS LINE 2.






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

� �

1-22 Online Guide

1.13 CICS Editor

1.13.3 Moving a Block of Lines

To move lines 1-3 before line 6:

� �------------------------------------------------------------------------

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

->>MM��1 WDAY


->>MM��3 THIS IS LINE 3.



-> B��6 THIS IS LINE 6.





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

� �

The result will be:

� �------------------------------------------------------------------------

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



-> ��3 WDAY








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

� �


1.13 CICS Editor

1.13.4 Deleting a Block of Lines

To delete lines 4-9:

� �------------------------------------------------------------------------

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

��1 WDAY



->>DD��4 THIS IS LINE 4.





->>DD��9 THIS IS LINE 9.


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

� �

The result will be:

� �------------------------------------------------------------------------

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

��1 WDAY




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

� �

1-24 Online Guide

1.13 CICS Editor

1.13.5 Repeating a Line

To repeat line 4 four times:

� �------------------------------------------------------------------------

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

��1 WDAY



->>R4 ��4 THIS IS LINE 4.







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

� �

The result will be:

� �------------------------------------------------------------------------

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

��1 WDAY



->>��4 THIS IS LINE 4.











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

� �


Chapter 2. Starting CA-Scheduler Online

CA-Scheduler is an ISPF application. Contact the person at your site who installedCA-Scheduler to determine how to access the online dialog.

Chapter 2. Starting CA-Scheduler Online 2-1

2.1 Logging on to CA-Scheduler

2.1 Logging on to CA-Scheduler

Your site may require you to log on to CA-Scheduler. If so, CA-Scheduler displays thefollowing panel:

� � ---------------------- CA-SCHEDULER 9.� xxyy (SCHD) SIGNON --------------------

COMMAND ===>

Signon information:

Userid . . . . . .

Read Password . . .

Write Password . .

�-------------------------------------------�

� �



� �

�-------------------------------------------�

� �

Enter the user ID, read, and write passwords provided by your site's CA-SchedulerAdministrator.

2-2 Online Guide

2.2 CA-Scheduler Main Menu

2.2 CA-Scheduler Main Menu

The CA-Scheduler main menu is the starting point for the online system.

� � ------------------------- CA-SCHEDULER 9.� xxyy (SCHD) ------------------------

OPTION ===>

� OPTIONS - Specify user preferences

1 MONITOR - Control and monitor the current workload

2 DATABASE - Define and maintain workload definition

3 REPORTS - Execute and view reports

X EXIT - Exit CA-Scheduler

�-------------------------------------------�

� �



� �

�-------------------------------------------�

� �

Use option 0, OPTIONS, to tailor the CA-Scheduler online environment to yourpreferences. See Chapter 3, “Options” for more information.

Use option 1, MONITOR, to interact with the current workload. See Chapter 4,“Monitor” for more information.

Use option 2, DATABASE, to define and maintain the workload. See Chapter 5,“Database” for more information.

Use option 3, REPORTS, to issue and view CA-Scheduler reports. See Chapter 6,“Reports” for more information.

Chapter 2. Starting CA-Scheduler Online 2-3

Chapter 3. Options

Option 0 (zero) of the CA-Scheduler main menu displays the options dialog.

The options allow you to tailor the CA-Scheduler online dialog.

� �---------------------- CA-SCHEDULER 9.� xxyy (SCHD) OPTIONS --------------------

COMMAND ===>

Options:

Delete Confirmation . . . . . . . YES (Yes, No)

Default Analyze List Type . . . . ERR (Yes, No, Err, Deadlock)

Command Output from Status . . . . ALL (All, Error)

Command Prompt from Status . . . . YES (Yes, No)

Default Start/Complete Station . . 4� (�1 to 99)

Temporary file secondary size . . ��1 (1 to 1��)

Default JOBCHAIN Levels . . . . . (blank, 1 to 999)

Default JOBCHAIN Repeat . . . . . YES (Yes, No)

Enter END to exit.

� �

The fields are:

Delete ConfirmationIf YES, a confirmation panel is displayed when an object is being deleted fromthe database. If NO, the object is deleted without any confirmation.

Size/Type: YES or NORequired: YesDefault: Yes

Default Analyze List TypeWhen displaying an Analyze panel, this value will be filled in for the List field.Valid values are:

YESAll information about analyzed schedules and jobs is displayed.

NOOnly schedule and job names are displayed.

Chapter 3. Options 3-1

ERROnly error messages are displayed.

DEADLOCKOnly deadlocks and the deadlock path is displayed.

Required: YesDefault: ERR

Command Output from StatusDetermines if the output from commands entered as line commands in the statuslists is displayed or not. Command output that includes a warning or errormessage is always displayed.

AllThe command output always displays.

ErrorThe command output only displays when it contains a warning or errormessage.

Required: YesDefault: All

Command Prompt from StatusDetermines if the command prompt panels are displayed for commands entered asline commands in the status lists.

YesDisplay the prompt panels allowing default options to be changed.

NoIssue the command with all default values.

Required: YesDefault: Yes

Default Start/Complete StationThe Start and Complete commands are normally used for jobs at stations otherthan 40. The value here will be filled in the Station field on the Start andComplete command prompts.

Size/Type: 1 to 2 numeric charactersRequired: YesDefault: 40

Temporary file secondary size (ISPF only)CA-Scheduler allocates a temporary file to hold command output. The file isallocated with one track and a secondary allocation size of the number you specifyhere. Normal OS/390 operations allow fifteen secondary extents of the size youspecify before a data set is considered full. If you get a message that the file isfull when viewing command output, consider increasing this value.

Size/Type: 1 to 3 digits in the range 1 to 100Required: YesDefault: 1

3-2 Online Guide

Default JOBCHAIN LevelsThe value entered here will be automatically filled in whenever a JOBCHAINcommand prompt panel is displayed. These panels are at options 3.11 and 3.12. Ifthe value is blank, then all levels are displayed.

Size/Type: Blank or 1 to 3 digitsRequired: NoDefault: blank

Default JOBCHAIN RepeatThe value entered here will be automatically filled in whenever a JOBCHAINcommand prompt panel is displayed. These panels are at options 3.11 and 3.12.

Size/Type: YES/NORequired: YesDefault: YES

Do you want to change PFkeys (CICS only)Specify YES and press Enter to change the PF key definitions for yourCA-Scheduler CICS session. The following panel is displayed:

� �CAJI�2��--------- CA-SCHEDULER 9.� xxyy (SCHD) PFKEYS ------------------

COMMAND ===>

To change please overtype PFKEY value.

PFK�1/13 : HELP PFK�7/19 : UP

PFK�2/14 : SPLIT PFK�8/2� : DOWN

PFK�3/15 : END PFK�9/21 : SWAP

PFK�4/16 : RETURN PFK1�/22 : LEFT

PFK�5/17 : RFIND PFK11/23 : RIGHT

PFK�6/18 : RCHANGE PFK12/24 : RETRIEVE

Pfkey function ( SPLIT, SWAP, RETRIEVE ) not supported

Enter END to exit.

� �

Chapter 3. Options 3-3

Chapter 4. Monitor

Option 1 of the CA-Scheduler main menu displays the monitor menu.

� � --------------------- CA-SCHEDULER 9.� xxyy (SCHD) MONITOR --------------------

OPTION ===>

1 STATUS - Interact with current workload starting with Schedules

2 STATJOB - Interact with current workload starting with Jobs

3 COMMAND - Build a command for CA-Scheduler

4 FREECMD - Freeform command for CA-Scheduler

5 CA-11 - CA-11 dialogs

Enter END to exit.

� �

Use option 1, STATUS, to view the condition of the current workload from a scheduleperspective. Status for jobs within a specific schedule may also be viewed. See 4.1,“Schedule Status” on page 4-2 for more information.

Use option 2, STATJOB, to view the condition of the current workload from a jobperspective. Jobs from more than one schedule may be viewed at the same time. See4.2, “Job Status” on page 4-16 for more information.

Use option 3, COMMAND, to build and issue monitor commands. See 4.3,“Commands” on page 4-43 for more information.

Use option 4, FREECMD, to issue any CA-Scheduler command. The last tencommands issued are retained and may be recalled. See 4.4, “FREECMD” onpage 4-187 for more information.

Use option 5, CA-11, to display the CA-11 main menu. This option is only available ifyou have CA-11 installed and the CA-11 ISPF data sets are currently allocated to yourISPF session. This option is not available for CICS.

Chapter 4. Monitor 4-1

4.1 Schedule Status

4.1 Schedule Status

Option 1 of the CA-Scheduler monitor menu displays the schedule status selectionpanel. The CA-Scheduler started task does not need to be active.

� �----------------- CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULE STATUS ----------------

COMMAND ===>

Include:

Schedule . . .

Select Status:

/ All (if selected, options below are ignored)

Not Held Not Requested (Inactive)

Held Cancelled

Schedule Not Started Wait Start Time Wait Predecessors

Started Completed

Display Late Only

Display ALL jobs in the schedule, or FILTER . . . ALL

Enter END to exit.

� �

The fields are:

ScheduleA full or partial schedule name to limit the schedules displayed, or blanks to showall schedules.

Size/Type: 1 to 8 alphanumeric charactersRequired: No

Select StatusSelect one or more of the status categories that you want displayed. Select acategory by typing any non-blank character to the left of the category title.Selecting the category All causes any other selections to be ignored. Thecategories you select are saved across CA-Scheduler sessions.

Display all jobs in the schedule, or filter based on above?

When the schedules are displayed, you may display the jobs within the schedulesby typing a J next to the schedule name. You may either have all of the jobs inthe schedule displayed, regardless of the job's status, or only display jobs withselected statuses. To display all of the jobs, enter ALL. To display a panelrequesting which statuses should be shown, enter FILTER.

Press Enter to display the schedule status panel.

4-2 Online Guide

4.1 Schedule Status

� � --------------------- CA-SCHEDULER 9.� xxyy (SCHD) STATUS - ROW 1 TO 11 OF 11


Enter CA-Scheduler command below, or enter a line command:

===>

Command Schedule Node Status Backlog

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

________ DAYOWK Started NO

________ ETEST Waiting Start Time yy�321 ��:�5 NO

________ FLOW1 Waiting Start Time yy�32� �9:�� NO

________ PYRAMID Started YES

________ PYRLONG Waiting Start Time yy�32� 1�:�� NO

________ PYRLONG2 Waiting for Predecessor(s) NO

________ QADEMO Started NO

________ QADEMO1 Waiting for Predecessor(s) NO

________ STEVE Started NO

________ S��1 Started NO

________ Y2��T1 Started NO


� �

Each schedule is displayed on a single row, along with its current status descriptionand backlog condition. The upper right-hand corner of the panel displays the currentrange of rows and the total number of rows. CA-Scheduler only reads the first 50schedules before displaying the list. As you scroll down, more rows are automaticallyadded until the entire list has been built.

Press PF5 to refresh the status of the currently displayed schedules, even if theschedules' status no longer matches the status categories requested. Press PF6 to list allof the schedules that currently match the status categories requested.

Note: Refreshing the display by using PF5 or PF6 is not supported by CICS.

Any CA-Scheduler command may be entered in the space provided.

You may enter the following commands in the command column on one or moreschedules:

Command Use

CAncel Issue a CANCEL SCHEDULE command. See 4.3.3.2, “CancelSchedule Command” on page 4-68.

CP Issue a CP SCHEDULE command. See 4.3.5.2, “Cancel PostSchedule Command” on page 4-77.

Force Issue a FORCE SCHEDULE command. See 4.3.8.2, “ForceSchedule Command” on page 4-93.

Hold Issue a HOLD SCHEDULE command. See 4.3.10.2, “HoldSchedule Command” on page 4-99.

J Display a list of jobs in this schedule. See 4.2, “Job Status” onpage 4-16.


4.1 Schedule Status

If a schedule is selected (command of S), CA-Scheduler displays the following panel:

� � ------------- CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULE STATUS DETAIL -------------

OPTION ===>

Schedule . . . From Node . . .

Status . . . .

1 DETAILS - Detail Information on the Schedule

2 PREDECESSORS - Information on this Schedule's Predecessors

Enter END to exit.

� �

Use option 1, DETAILS, to display and alter information about the schedule in thecurrent workload. See the next topic for more information.

Command Use

P Display the schedule's predecessors, and the predecessor's status.See 4.2.2, “Predecessor Display” on page 4-38.

POst Issue a POST SCD command. See 4.3.12.2, “Post ScheduleCommand” on page 4-109.

PUrge Issue a PURGE SCHEDULE command. See 4.3.13.2, “PurgeSchedule” on page 4-127.

RELease Issue a RELEASE SCHEDULE command. See 4.3.14.2,“Release Schedule Command” on page 4-132.

REQuest Issue a REQUEST SCHEDULE command. See 4.3.15.2,“Request Schedule Command” on page 4-140.

RUn Issue a RUN SCHEDULE command. See 4.3.18.2, “RunSchedule Command” on page 4-151.

S Display detail information about the schedule.

SReq Issue an SREQ SCHEDULE command. See 4.3.19.2, “SREQSchedule Command” on page 4-156.

Unpost Issue an UNPOST SCD command. See 4.3.22.2, “UnpostSchedule Command” on page 4-168.

= Repeat the previous command.

4-4 Online Guide

4.1 Schedule Status

Use option 2, PREDECESSORS, to display a list of the schedule's predecessors. See4.2.2, “Predecessor Display” on page 4-38.

You can bypass this panel by entering a 1 or 2 instead of an S to select the schedule.

4.1.1 Schedule Status Detail

The Schedule Status Detail panels display current information about the schedule inthe workload. Some of the fields may be modified. A command is built and sent to theCA-Scheduler started task for any modifications.

The fields are contained on several panels. Use PF7 and PF8 to scroll up and downthrough the panels. To save any changes and exit, use PF3. To exit without saving anychanges, enter CAN on the command line.

The output of the command is displayed. If an error is detected, the Scheduler StatusDetail panels are redisplayed, allowing you to correct the problem.

The batch utility to use is CAJUCMD0. The batch command is TALTERSCHEDULE.


COMMAND ===>

Schedule . . . From Node . .

Current Status:

Status . . . . . . . . .

Job Count . . . . . . .

Selection Code . . . . .

Backlog Eligible . . . .

Currently Backlogged . .

Waiting on Global . . .

Predecessor Priority . .

Late:

Late due to Must Start Time . Track Must Start Time .

Late due to Must End Time . . Track Must End Time . .

Late due to Maximum Time . . Track Maximum Time . .

Enter END to exit, DOWN for next screen, or UP for previous screen.

� �

You may jump to this panel from other Schedule Status Detail panels by using one ofthe following jump commands:

TOP STATUS LATE


4.1 Schedule Status

The fields are:

ScheduleThe name of the schedule being displayed or altered.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: Name

From NodeThe owning JES NJE node of this schedule. This field is blank if theCA-Scheduler installation option NJE is set to NO.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: FMnodeDefault: Local node name

StatusThe current status of the schedule.

Display only with no batch equivalent.

Job CountThe number of jobs, including Not Requested jobs, that are in the currentworkload.


Selection CodeThe reason why this schedule is part of the current workload.

If RC is This number

01 - 79 Corresponds to the position of the reason on the criteria statement thatwas defined for this job or schedule. A job will inherit the reason codefrom a schedule if no criteria record exists for the job.

80 Indicates that it was selected because today's date corresponds to aworkday on the calendar that was defined for this job or schedule.

84 Indicates that it is selected by default every day because no selectioncriteria were defined or the criteria record is blank (NULL).

88 Indicates that it was added to today's workload by the online RUNcommand.

92 Identifies a schedule that is being run because a job abended. (Thisschedule was defined on the ABEND option as an alternate schedule incase of abend.)

93 Indicates that the job originates from another node (NJE).

94 Indicates a nonscheduled OS/390 job.

95 Indicates that it was added to today's workload by the online ADDcommand.

4-6 Online Guide

4.1 Schedule Status

96 Indicates that this job was a backout job that was submitted for anabended job that specified ABEND=BACKOUT.

Backlog EligibleIndicates if the schedule, and all of its jobs, should be backlogged if the schedulehas not completed at the next autoscan.

Size/Type: YES or NORequired: NoBatch Keyword: Backlog

Currently BackloggedIndicates if the schedule is backlogged now. A Yes value indicates that a newcopy of the schedule and its jobs are brought into the current workload as soon asthis copy finishes.


Waiting on GlobalIndicates if the schedule has an unsatisfied global variable in its criteria.


Predecessor PriorityA number used in ordering schedules on an internal chain of control blocks. Thisvalue is only of use to Computer Associates Technical Support.


Late due to Must Start TimeIf YES, the schedule did not start by its Must Start Time.


Track Must Start TimeIf YES, the schedule has a Must Start Time.


Late due to Must End TimeIf YES, the schedule did not end by its Must End Start Time.


Track Must End TimeIf YES, the schedule has a Must End Time.


Late due to Maximum TimeIf YES, the schedule has been started longer than its Maximum Time.


Track Maximum TimeIf YES, the schedule has a Maximum Time.



4.1 Schedule Status

Press PF8 for the next panel.


COMMAND ===>


Times:

Early Start Time . . . .

Must Start Time . . . .

Must End Time . . . . .

Maximum Execution . . .

User-specified Average .

Historical Average . . .

Scheduled Time . . . . .

Available Time . . . . .

Start Time . . . . . . .

End Time . . . . . . . .


� �

You may jump to this panel from other Scheduler Status Detail panels by using thefollowing jump command:

TIMES

The fields are:

Early Start Time| The earliest date and time that the schedule may start. The values are a seven-digit| Julian date (YYYYDDD) and a four-digit time (HHMM). If the time field is 0000,

the schedule does not have an early start time. The date must be at least the valueof the Scheduled Time date.

| Size/Type: (Online) 7 numeric Julian date and 4 digit time(Batch) 6 numeric in the form ddhhmm

Required: NoBatch Keyword: Erlytime

Must Start TimeThe latest date and time that the schedule may start before being marked late. The

| values are a seven-digit Julian date (YYYYDDD) and a four-digit time (HHMM).If the time field is 0000, the schedule does not have a must start time. The datemust be at least the value of the Scheduled Time date.


Required: NoBatch Keyword: Musttime

4-8 Online Guide

4.1 Schedule Status

Must End TimeThe latest date and time that the schedule may end before being marked late. The

| values are a seven-digit Julian date (YYYYDDD) and a four-digit time (HHMM).If the time field is 0000, the schedule does not have a must end time. The datemust be at least the value of the Scheduled Time date.


Required: NoBatch Keyword: Deadline

Maximum ExecutionThe length of time that the schedule may execute before being marked late. Thevalue is in the form ddhhmm, where dd is the number of autoscans and hhmm isthe time.


User-specified AverageThe length of time entered on the schedule in the database as an averageexecution time. The value is in the form ddhhmm, where dd is the number ofautoscans and hhmm is the time.


Historical AverageThe average amount of time for this schedule to execute, based on the last sevenexecutions of the schedule.


Scheduled TimeThe date and time the schedule was added to the workload.


Available TimeThe date and time the schedule was first available to start.


Start TimeThe date and time of the most recent start of the schedule.


End TimeThe date and time of the most recent end of the schedule.




4.1 Schedule Status


COMMAND ===>


Scheduled At:

Node . . . Sysid . . .

Executing At:


Selection:

Date Table . . .

Calendar . . . .

Auto Select . .

Other:

Continue on bad jobs . . . . .

Date on RUN Command . . . . .

Use Simulate Times . . . . .

User Data . . . . . . . . . .


� �


SCHD EXEC SELECT OTHER

The fields are:

Scheduled At NodeThe JES NJE node name where the schedule is controlled or blanks if theCA-Scheduler installation option NJE is set to NO.

Scheduled At SysidThe system ID of the controlling CA-Scheduler.

Executing At NodeThe JES NJE node name where the schedule is executing or blanks if theCA-Scheduler installation option NJE is set to NO.

Executing At SysidThe system ID of the CA-Scheduler where the schedule is executing.

Date TableThe name of the date table used in bringing the schedule and its jobs into thecurrent workload.

CalendarThe name of the calendar, if any, specified on the schedule's criteria.

Auto SelectIf YES, the schedule is eligible for autoscan to add it to the workload.

4-10 Online Guide

4.1 Schedule Status

Continue on bad jobsIf YES, the schedule's successors are posted if one of the following is true forevery job in this schedule:

1. The job ended successfully.

2. The job was completed with the COMPLETE command.

3. The job failed and has FAILED=CONT.

4. The job abended and has ABEND=CONT.

Date on RUN CommandIf the RUN command with the DATE parameter was used to add the schedule tothe workload, then the DATE value is displayed here. If not, then zeros aredisplayed.

Use Simulate TimesIf YES, the Early Start Time, Must Start, and Must End Times may have beengenerated by the SIMULATE command.

User DataAny user specific data associated with this schedule. The data may be supplied bya user exit (see the Notification Exit in the Systems Programmer Guide) or on theTALTER SCHEDULE command.

Size/Type 1 to 16 alphanumeric charactersRequired: NoBatch Keyword: USERData



COMMAND ===>


Job Defaults:

Library Type . . . Insert Sched Enviro . . .

Stage JCL . . . . Scheduling Environment. .

Insert CA-11 . . .

JCL DDName . . . .

Userids:

User who Issued RUN . . .

User who Held . . . . . .

User who Released . . . .

User who Cancelled . . .

User who Forced . . . . .

Security:

Userids . . . . . . . . .

. . . . . . . . .


� �


4.1 Schedule Status


JOB USERIDS SECURITY

The fields are:

Library TypeThe default access method for jobs in this schedule. A change in this value onlyapplies to jobs added to the workload, not to jobs already in the workload. Validvalues are:

DRIVER CA-Scheduler generates one line of JCL to be expanded by Driver.

JOBDOC CA-Jobdoc

LIBRN CA-Librarian

PANV CA-Panvalet

PDS Partitioned data set

RDRQ Jobs are manually submitted outside of CA-Scheduler with aTYPRUN=HOLD on the job statement. CA-Scheduler releases the joband tracks it as if the job was submitted by CA-Scheduler. See"Performance Considerations" in the Systems Programmer Guide forperformance implications.

USERLIB The access method is provided by a site-written exit program. See"User Exits and APIs" in the Systems Programmer Guide for moreinformation.

TESTLIB CA-Scheduler submits a dummy job (based on the skeleton in memberCAJUTSTB of the PDS allocated to ddname JCLMASTR). Thedummy job may execute for a specified number of seconds, end witha specific return code, or abend, based on parameters defined at thejob level. See the field Test Parm in 5.2.2.1, “Job Definition” onpage 5-29.

ROSCOE CA-Roscoe

Required: NoBatch Keyword: Libtype

Insert Sched EnviroDetermines if a Workload Manager (WLM) scheduling environment should beinserted into this schedule's jobs or not. See also Scheduling Environment.Changing this value only affects jobs that are added to the workload for thisschedule (using the ADD JOB or RUN JOB commands) after the change is made.Jobs already in the active workload are not affected.

Size/Type: YES or NORequired: NoBatch Keyword: INSRSenv

4-12 Online Guide

4.1 Schedule Status

Stage JCLThe default staging option for jobs in this schedule.

Insert CA-11The default CA-11 option for jobs in this schedule. A change in this value onlyapplies to jobs added to the workload, not to jobs already in the workload.

Size/Type: YES or NORequired: NoBatch Keyword: INSrrms

Scheduling EnvironmentThe name of the Workload Manager (WLM) scheduling environment that shouldbe inserted into this schedule's jobs. This field must not be blank, and Insert SchedEnviro must be set to YES before a scheduling environment (SCHENV) isinserted into the job's JCL. Changing this value only affects jobs that are added tothe workload for this schedule (using the ADD JOB or RUN JOB commands)after the change is made. Jobs already in the active workload are not affected.

Size/Type: 1 to 16 alphanumeric charactersRequired: NoBatch Keyword: SCHENV

JCL DDNameThe default ddname for jobs with a library type of PDS. A change in this valueonly applies to jobs added to the workload, not to jobs already in the workload.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: DDname

User who Issued RUNThe user ID responsible for adding the schedule to the workload. A value ofAUTOINIT means the schedule was added by autoscan.


User who HeldThe last user who held the schedule. Blanks mean the schedule has never beenheld.


User who ReleasedThe last user who released the schedule. Blanks mean the schedule has never beenreleased.


User who CancelledThe user who removed the schedule from the workload. Blanks mean the schedulehas not been canceled.



4.1 Schedule Status

User who ForcedThe last user who issued the FORCE SCHEDULE command on this schedule.


UseridsA list of users allowed to manipulate this schedule and its jobs usingCA-Scheduler internal security.



� �-------------- CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULE STATUS DETAIL -------------

COMMAND ===>


Userid to Notify for:

All Events . . . . . . . . . . . . . .

Schedule Start . . . . . . . . . . . .

Schedule End . . . . . . . . . . . . .

Schedule Late . . . . . . . . . . . .

Enter END to Exit, or UP for Previous Screen.

� �


SMR BOTTOM

The fields are:

All EventsA list of zero to four user IDs or OPERxxyy values to which messages will besent when the schedule starts, becomes late, and ends. See below for moreinformation.


Schedule StartA list of zero to four user IDs or OPERxxyy values to which messages will besent when the schedule starts. See below for more information.


4-14 Online Guide

4.1 Schedule Status

Schedule EndA list of zero to four user IDs or OPERxxyy values to which messages will besent when the schedule ends. See below for more information.


Schedule LateA list of zero to four user IDs or OPERxxyy values to which messages will besent if the schedule is marked late. See below for more information.


Messages to users are not TSO SEND messages. They are stored in the CA-Scheduleractive workload and must be retrieved manually by the user. Messages are not keptindefinitely--see the CAIJGEN option MSGHOLD for more information.

Messages are stored in the CA-Scheduler database when the value is MAILBOX, andmay be retrieved by the REPORT MAILBOX command.

A value of OPERxxyy sends a WTO to the OS/390 console. The xx is the route code,and the yy is the descriptor code. Consult your site's systems programmer for a list ofappropriate route codes and descriptor codes for your site.

The CAIJGEN options STRMSG, ENDMSG, and LATMSG specify locations to whichall start, end, and late messages should be sent. Normally these include MAILBOX.


4.2 Job Status

4.2 Job Status

You may start the job status function either by selecting option 2 from theCA-Scheduler Monitor menu or by selecting a schedule with a J from the schedulestatus function. The following panel displays only if started from the CA-SchedulerMonitor menu.

� �------------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB STATUS -------------------

COMMAND ===>

Include:

Job . . . . .

Select Status:

/ All (if selected, options below are ignored)

Not Held Not Requested (Inactive)

Held Cancelled

Schedule Not Started Submit in Progress Failed (rc & JCL err)

Wait Start Time Submitted Abended

Wait Predecessors Submit Failed Interrupted

Wait Resources Rec'd at Remote Node Completed

Unknown Started Purged

Display Late Only Display Staged Only

Enter END to exit.

� �

The fields are:

JobA full or partial job name to limit the jobs displayed, or blanks to show all jobs.


Select StatusSelect one or more of the status categories that you want displayed. Select acategory by typing any non-blank character to the left of the category title.Selecting the category All causes any other selections to be ignored. Thecategories you select are saved across CA-Scheduler sessions.

Press Enter to display the job status panel.

4-16 Online Guide

4.2 Job Status

� �--------------------- CA-SCHEDULER 9.� xxyy (SCHD) STATUS -- Row 1 to 16 of 5�


Enter CA-Scheduler command below, or enter a line command:

===>

Command Job JNO St Node Schedule Status

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

________ BACKOUT �1 4� USI287ME BACKOUT Failed J1�452 RC=��12

________ BACKOUTX �1 4� USI287ME BACKOUT Purged J1�453 RC=��

________ ETEST �1 4� USI287ME ETEST Schedule not Started

________ FL1 �1 4� USI287ME FLOW1 Started J1�484

________ FL2 �1 4� USI287ME FLOW1 Waiting for Predecessors(s)





________ JOBA �1 4� USI287ME PYRAMID Submitted J1�485

________ JOBB �1 4� USI287ME PYRAMID Waiting for Predecessors(s)

________ JOBC �1 4� USI287ME PYRAMID Waiting for Predecessors(s)

________ JOBD �1 4� USI287ME PYRAMID Waiting for Predecessors(s)

________ JOBE �1 4� USI287ME PYRAMID Waiting for Predecessors(s)

________ JOBF �1 4� USI287ME PYRAMID Waiting for Predecessors(s)

________ JOBG �1 4� USI287ME PYRAMID Waiting for Predecessors(s)

� �

Each job is displayed on a single row, along with its current status description andbacklog and late conditions. The upper right-hand corner of the panel displays thecurrent range of rows and the total number of rows. CA-Scheduler only reads the first50 jobs before displaying the list. As you scroll down, more rows are automaticallyadded until the entire list has been built.

Press PF5 to refresh the status of the currently displayed jobs even if the jobs' statusno longer matches the status categories requested. Press PF6 to list all of the jobs thatcurrently match the status categories requested.

Note: Refreshing the display by using PF5 or PF6 is not supported by CICS.

Any CA-Scheduler command may be entered in the space provided.

The following commands may be entered in the command column on one or morejobs:

Command Use

CAncel Issue a CANCEL JOB command. See 4.3.3.1, “Cancel JobCommand” on page 4-66.

CP Issue a CP JOB command. See 4.3.5.1, “Cancel Post (CP) JobCommand” on page 4-74.

COmplete Issue a COMPLETE JOB command. See 4.3.4, “Complete JobCommand” on page 4-71.

Force Issue a FORCE JOB command. See 4.3.8.1, “Force JobCommand” on page 4-91.


4.2 Job Status

If RERUN or SUBMIT is issued and the installation option RERCONF (rerunconfirmation) is set to yes, then the current status of the job is checked. If the job hasalready completed successfully, then the following panel is displayed.

Command Use

Hold Issue a HOLD JOB command. See 4.3.10.1, “Hold JobCommand” on page 4-97.

P Display the job's predecessors, and the predecessor's status. See4.2.2, “Predecessor Display” on page 4-38.

POst Issue a POST SCD command. See 4.3.12.2, “Post ScheduleCommand” on page 4-109.

PUrge Issue a PURGE JOB command. See 4.3.13.1, “Purge JobCommand” on page 4-125.

RELease Issue a RELEASE JOB command. See 4.3.14.1, “Release JobCommand” on page 4-130.

REQuest Issue a REQUEST JOB command. See 4.3.15.1, “Request JobCommand” on page 4-139.

RERun Issue a RERUN JOB command. See 4.3.16, “Rerun JobCommand” on page 4-142.

REStage Issue a RESTAGE JOB command. See 4.3.17, “Restage JobCommand” on page 4-146.

RUn Issue a RUN JOB command. See 4.3.18.1, “Run Job Command”on page 4-149.

S Display detail information about the job.

SReq Issue an SREQ JOB command. See 4.3.19.1, “SREQ JobCommand” on page 4-154.

STart Issue a START JOB command. See 4.3.20, “Start JobCommand” on page 4-158.

SUbmit Issue a SUBMIT JOB command. See 4.3.21, “Submit JobCommand” on page 4-160.

Unpost Issue an UNPOST JOB command. See 4.3.22.1, “Unpost JobCommand” on page 4-165.

= Repeat the previous command.

4-18 Online Guide

4.2 Job Status

� �------------------ CA-SCHEDULER 9.� xxyy (xxxx) CONFIRMATION ------------------

COMMAND ===>

The job xxxxxxxx nn nn nnnnnnnn ssssssss has already COMPLETED successfully.

If you want to have the job submitted again anyway, type a Y in the field

below and press ENTER.

Re-submit job . . .

Enter END to exit.

� �

You must type a Y in the field before the job will be submitted.

If a job is selected (command of S), the following panel is displayed:

� � ---------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB STATUS DETAIL ---------------

OPTION ===>

Job . . . . . TUE Number . . �1 Station . . 4� Schedule . . DAYOWK

From Node . . USI287ME

Status . . . Purged J1�156 RC=��

1 DETAILS - Detail Information on the Job

2 PREDECESSORS - Information on this Job's Predecessors

3 STAGE JCL - Alter Staged JCL

Enter END to exit.

� �

Use option 1, DETAILS, to display and alter information about the job in the currentworkload. See the next topic for more information.

Use option 2, PREDECESSORS, to display a list of the job's predecessors. See 4.2.2,“Predecessor Display” on page 4-38.


4.2 Job Status

Use option 3, STAGE JCL, to display and alter the job's JCL in the CA-Scheduleractive workload. See 4.2.3, “Staged JCL” on page 4-39.

You can bypass this panel by entering a 1, 2, or 3 instead of an S to select the job.

4.2.1 Job Status Detail

Use the Job Status Detail panels to display current information about the job in theworkload. You can modify some of the fields. A command is built and sent to theCA-Scheduler started task for any modifications.

Several panels contain the fields. Use PF7 and PF8 to scroll up and down through thepanels. To save any changes and exit, use PF3. To exit without saving any changes,enter CAN on the command line.

CA-Scheduler displays the output of the command. If an error is detected, the JobStatus Detail panels are redisplayed, allowing you to correct the problem.

The batch utility to use is CAJUCMD0. The batch command is TALTER JOB.


OPTION ===>

Job . . . . . Number . . Station . . Schedule . .

From Node . .

Current Status:

Status . . . . . . . . .

Selection Code . . . . . Original JES Number .

Backlog Eligible . . . .

Currently Backlogged . .

Staged . . . . . . . . . Changed . .

Waiting on Global . . . Waiting on SEPDSN . .

Last Proc Step . . . . . Last Step . . . . . .

Late:

Late due to Must Start Time . Track Must Start Time .

Late due to Must End Time . . Track Must End Time . .

Late due to Maximum Time . . Track Maximum Time . .


� �

You may jump to this panel from other Job Status Detail panels by using one of thefollowing jump commands:

TOP STATus LATE

4-20 Online Guide

4.2 Job Status

The fields are:

JobThe name of the job currently displayed.


NumberThe number of the job currently displayed.

Size/Type: 1 to 2 numeric charactersRequired: NoBatch Keyword: JNoDefault: 01

StationThe station of the job currently displayed.

Size/Type: 1 to 2 numeric charactersRequired: NoBatch Keyword: STationDefault: 40

ScheduleThe schedule to which the currently displayed job belongs.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ScheduleDefault: First schedule that contains this job name

From NodeThe NJE node where the job is controlled, or blanks if the CA-Scheduler NJEoption is set to NO.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: FMnodeDefault: Local node name

StatusThe current status of this job.


Selection CodeThe reason why this job is part of the current workload.

If RC is This number

01 - 79 Corresponds to the position of the reason on the criteria statement thatwas defined for this job or schedule. A job will inherit the reason codefrom a schedule if no criteria record exists for the job.


4.2 Job Status

80 Indicates that it was selected because today's date corresponds to aworkday on the calendar that was defined for this job or schedule.

84 Indicates that it is selected by default every day because no selectioncriteria were defined or the criteria record is blank (NULL).

88 Indicates that it was added to today's workload by the online RUNcommand.

92 Identifies a schedule that is being run because a job abended. (Thisschedule was defined on the ABEND option as an alternate schedule incase of abend.)

93 Indicates that the job originates from another node (NJE).

94 Indicates a nonscheduled OS/390 job.

95 Indicates that it was added to today's workload by the online ADDcommand.

96 Indicates that this job was a backout job that was submitted for anabended job that specified ABEND=BACKOUT.

Original JES NumberIf the job has been transmitted using JES NJE, it may not have the same JES jobnumber it did when it was submitted. The original number is displayed here, orzeros to indicate that the job has not been transmitted.

Backlog EligibleDetermines if CA-Scheduler should keep this copy of the job if it has notcompleted by the next autoscan.

Size/Type: YES or NORequired: NoBatch Keyword: Backlog

Currently BackloggedIndicates whether another copy of this job (or schedule) is waiting to run as soonas this copy completes.


StagedIndicates if a copy of the job's JCL has been written to the CA-Scheduler activeworkload.


ChangedThe date and time that the staged JCL was last modified. If the JCL has not beenstaged, the date and time are blank.


Waiting on GlobalIndicates if the job has an unsatisfied global variable.


4-22 Online Guide

4.2 Job Status

Waiting on SEPDSNIndicates if the job requires an exclusive resource that is currently held by anotherjob.


Last Proc StepThe last step name (outside of a procedure) that executed in this job.


Last StepThe last step name (with an EXEC PGM= on it) that executed in this job.


Late due to Must Start TimeIf YES, the job did not start by its Must Start Time.


Track Must Start TimeIf YES, the job has a Must Start Time.


Late due to Must End TimeIf YES, the job did not end by its Must End Start Time.


Track Must End TimeIf YES, the job has a Must End Time.


Late due to Maximum TimeIf YES, the job has been started longer than its Maximum Time.


Track Maximum TimeIf YES, the job has a Maximum Time.




4.2 Job Status


COMMAND ===>


From Node . .

Times:

Early Start Time . . . .

Must Start Time . . . .

Must End Time . . . . .

Maximum Execution . . .

User-specified Average .

Historical Average . . .

Scheduled Time . . . . .

Available Time . . . . .

Start Time . . . . . . .

End Time . . . . . . . .


� �


TIMes

The fields are:

Early Start Time| The earliest date and time that the job may start. The values are a seven-digit| Julian date (YYYYDDD) and a four-digit time (HHMM). If the time field is 0000,

the job does not have an early start time. The date must be at least the value ofthe Scheduled Time date.


Required: NoBatch Keyword: Erlytime

Must Start TimeThe latest date and time that the job may start before being marked late. The

| values are a seven-digit Julian date (YYYYDDD) and a four-digit time (HHMM).If the time field is 0000, the job does not have a must start time. The date must beat least the value of the Scheduled Time date.


Required: NoBatch Keyword: Musttime

4-24 Online Guide

4.2 Job Status

Must End TimeThe latest date and time that the job may end before being marked late. The

| values are a seven-digit Julian date (YYYYDDD) and a four-digit time (HHMM).If the time field is 0000, the job does not have a must end time. The date must beat least the value of the Scheduled Time date.


Required: NoBatch Keyword: Deadline

Maximum ExecutionThe length of time that the job may execute before being marked late. The valueis in the form ddhhmm, where dd is the number of autoscans and hhmm is thetime.


User-specified AverageThe length of time entered on the job in the database as an average executiontime. The value is in the form ddhhmm, where dd is the number of autoscans andhhmm is the time.


Historical AverageThe average amount of time for this job to execute, based on the last sevenexecutions of the job.


Scheduled TimeThe date and time the job was added to the workload.


Available TimeThe date and time the job was first available to start (submitted).


Start TimeThe date and time of the most recent start of the job.


End TimeThe date and time of the most recent end of the job.


Press PF8 for the next panel. It is displayed only for CPU jobs (station = 40).


4.2 Job Status

� � -------------- CA-SCHEDULER 9.� xxyy (SCHD) CPU JOB STATUS DETAIL -------------

COMMAND ===>


From Node . .

JCL:

Library Type . . . . . .

JCL DDname . . . . . . . Member Subid . . . .

Member Name . . . . . . Insert Sched Enviro .

Insert CA-11 RMS . . . . Sched Enviro . . . .

Memo Text . . . . . . .

Testlib Parm . . . . . .

Failure:

Fail Oper . . . . . . . Fail Code . . . . .

Abend Option . . . . . . Abend Count . . . . .

Fail Option . . . . . .

Job has Step Records . . Job Step Failed . . .


� �


JCL FAILure

The fields are:

Library TypeThe access method to use in retrieving this job's JCL.


JOBDOC CA-Jobdoc

LIBRN CA-Librarian

PANV CA-Panvalet




4-26 Online Guide

4.2 Job Status


ROSCOE CA-Roscoe

Required: NoBatch Keyword: Libtype

JCL DDnameThe ddname that the CA-Scheduler started task should use for reading the job'sJCL when the library type is PDS.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: DDname

Member SubidUsed to prefix the member name to generate the 10-character name used byCA-Panvalet.


Member NameThe member in the library that contains the job's JCL. If blank, the job name isused.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: LIBMemb

Insert Sched EnviroDetermines if a Workload Manager (WLM) scheduling environment should beinserted into this job's JCL. See also Scheduling Environment.

Size/Type: YES or NORequired: NoBatch Keyword: INSRSenv

Insert CA-11 RMSDetermines if the CA-11 Run Manager Step is inserted into the job duringsubmission.

Size/Type: YES or NORequired: NoBatch Keyword: INSrrms


4.2 Job Status

Scheduling EnvironmentThe name of the Workload Manager (WLM) scheduling environment that shouldbe inserted into this job's JCL. This field must not be blank, and Insert SchedEnviro must be set to YES before a scheduling environment (SCHENV) isinserted into the job's JCL.

Size/Type: 1 to 16 alphanumeric charactersRequired: NoBatch Keyword: SCHENV

Memo TextIf specified, this text is issued as a WTOR before the job executes. The operatormust respond OK before the job runs.


Testlib ParmThe PARM to use for library type TESTLIB jobs.

Fail OperThe relational operator used in determining whether a job's condition code shouldbe treated as a FAILED condition. Successors to this job are not posted assatisfied. A value of blank means that any job step ending with a condition codegreater than or equal to the Fail Code value is posted as FAILED. Successors tothis job are not posted as satisfied. Valid relational operators are EQ, NE, GE, LE,GT, and LT.

Size/Type: 2 alphanumeric charactersRequired: NoBatch Keyword: FAILOperDefault: GE

Fail CodeThe condition code threshold which indicates job failure (an integer from1-32767). Any job step ending with a condition code within the range specified bythe fail code operator, Fail Oper, is posted as FAILED. Successors to this job arenot posted as satisfied. A value of zero with Fail Oper equal to blanks means thatCA-Scheduler is not checking the Fail Code.

Size/Type: 1 to 4 numeric charactersRequired: NoBatch Keyword: FailcodeDefault: 0 (zero) No condition code test is done

Abend OptionDetermines what action to take if the job abends. Valid values are:

ABORT (or blank)Do not let successors run.

CONTAllow successors to run as if the job ended successfully.

4-28 Online Guide

4.2 Job Status

BACKOUTSubmit another job, whose name is built based on the CAIJGEN optionBACKOUT.

scheduleRun the specified schedule.

Required: NoBatch Keyword: Abend

Abend CountThe number of times this job has abended while a part of the workload.


Fail OptionDetermines what action to take if the job ends with an unacceptable return code.Valid values are:

ABORT (or blank)Do not let successors run.




Required: NoBatch Keyword: FAILEd

Job has Step RecordsIf YES, the Fail Oper and Fail Code are ignored in favor of the Job Step Recordsin determining if the job ended with an unacceptable return code.


Job Step FailedOne or more steps ended with a return code defined as unacceptable by the JobStep Records.




4.2 Job Status


COMMAND ===>


From Node . .

Scheduled at:


Current location:


Separate Job Execution:

Resource . . . .

Job List . . . . . . . . . .

. . . . . . . . . .

Selection:

Date Table . . . . . .

Calendar . . . . . . .


� �


EXEC RESource SELect

The display-only fields are:

Scheduled At NodeThe NJE node where the job was originally scheduled to run, or blanks if for thelocal node.

Scheduled At SysidThe system ID where the job on which the job was originally scheduled toexecute, or blanks for any system.

Current location NodeIf the CA-Scheduler installation option NJE is NO, this field is blank. If NJE isset to YES and the job has not yet been submitted, the owning (local) node isdisplayed. After the job has been submitted and reached a different node, thevalue is the remote node name.

Current location SysidThe system ID where the job actually ran or blanks if the job has not started yet.

ResourceThe name of a resource internal to CA-Scheduler which this job must haveexclusive control over before it can be submitted.

Job ListFull or partial job names which cannot be submitted or running when this job issubmitted.

4-30 Online Guide

4.2 Job Status

Date TableThe date table used in evaluating the job's criteria.

CalendarThe calendar used in selecting this job.



COMMAND ===>


From Node . .

User ids:

User who Issued RUN . . . Group id . . . . . .

User who Issued SUBMIT. . Group id . . . . . .

User who Defined Job . . Group id . . . . . .

JSI User id . . . . . . . Group id . . . . . .

Staged JCL Changed by . . Group id . . . . . .

User who Held . . . . . .

User who Released . . . .

User who Forced . . . . .

User who Cancelled . . .

User who Started . . . .

User who Completed . . .


� �


USERids SECurity


User who Issued RUN/Group idThe user and group ID of the person who added the job to the current workload.If the user ID is AUTOINIT, the job was added using autoscan.

User who Issued SUBMIT/Group idThe user and group ID of the last person who caused this job to be submitted.

User who Defined Job/Group idThe user and group ID of the last person to modify the job in the database.

JSI User id/Group idThe user and group ID associated with the job, schedule, or CA-Scheduler. If theCA-Scheduler installation option SUBUID includes the value JSI, this user/groupID is used.

Staged JCL Changed by/Group idThe user and group ID who last changed the staged JCL. If the JCL is not stagedor has not yet been modified, these fields are blank.


4.2 Job Status

User who HeldThe last person to hold this job.

User who ReleasedThe last person to release this job.

User who ForcedThe last person to issue the FORCE JOB command on this job.

User who CancelledThe person who removed this job from the workload.

User who StartedThe last person who issued the START JOB command for this job.

User who CompletedThe last person who issued the COMPLETE JOB command for this job.



COMMAND ===>

Job . . . . . CHAS�1 Number . . �1 Station . . 4� Schedule . . CHAS�1

From Node . . USI287ME

Documentation:

Display Key . . . KEY12345

Display Time . . ��

Other:

JES Priority . . . . . . . . . 1�

JES Class . . . . . . . . . . F

Predecessor Priority . . , , , ��1

Internal Priority . . . , , , 1�

Use Simulation Times . . . . . NO

Command Causing Submission . . RELEASE

Date on RUN Command . . . . . ��

User Data . . . . . . . . . .


� �


OTHer SIMulate DOC


Display KeyThe CA-Scheduler workload documentation entry that should be displayed on theOS/390 console for this job.

4-32 Online Guide

4.2 Job Status

Display TimeThe time at which the CA-Scheduler workload documentation entry should bedisplayed on the OS/390 console.

JES PriorityIf modified and the job has been submitted, the job's JES priority is altered to thisvalue. Otherwise, this field is used only for SIMULATE REVISE=YESprocessing.

JES ClassIf modified and the job has been submitted, the job's JES class is altered to thisvalue. Otherwise, this field is only used for SIMULATE REVISE=YESprocessing.

Predecessor PriorityA number used in ordering jobs on an internal chain of control blocks. This valueis only of use to Computer Associates Technical Support.

Internal PriorityA number used in ordering jobs on an internal chain of control blocks. This valueis only of use to Computer Associates Technical Support.

Use Simulation TimesIf YES, the Early Start Time and other time fields may have been generated bySIMULATE reports.

Command Causing SubmissionThe CA-Scheduler command that caused the most recent submission of the job.

Date on RUN CommandThe date on the RUN SCHEDULE command that added this job to the currentworkload.

User DataAny user-specific data associated with this job. The data may be supplied by auser exit (see the Notification Exit in the Systems Programmer Guide) or on theTALTER JOB command.

Size/Type: 1 to 16 alphanumeric charactersRequired: NoBatch Keyword: USERData



4.2 Job Status

� �---------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB STATUS DETAIL ---------------

COMMAND ===>


From Node . .


All Events . . . . . . . . . . . . .

Job Start . . . . . . . . . . . . .

Job Fail . . . . . . . . . . . . . .

Job Abend . . . . . . . . . . . . .

Job Interrupt . . . . . . . . . . .

Job End . . . . . . . . . . . . . .

Job Purge . . . . . . . . . . . . .

Job Late . . . . . . . . . . . . . .


� �


JMR MSG


All EventsA list of zero to four user IDs or OPERxxyy values to which messages will besent when the job starts, fails, abends, is interrupted, becomes late, ends, and isremoved from the active workload. See below for more information.

Job StartA list of zero to four user IDs or OPERxxyy values to which messages will besent when the job starts. See below for more information.

Job FailA list of zero to four user IDs or OPERxxyy values to which messages will besent when the job fails. See below for more information.

Job AbendA list of zero to four user IDs or OPERxxyy values to which messages will besent when the job abends. See below for more information.

Job InterruptA list of zero to four user IDs or OPERxxyy values to which messages will besent when the job is interrupted. See below for more information.

Job EndA list of zero to four user IDs or OPERxxyy values to which messages will besent when the job ends. See below for more information.

4-34 Online Guide

4.2 Job Status

Job PurgeA list of zero to four user IDs or OPERxxyy values to which messages will besent when the job is removed from the active workload. See below for moreinformation.

Job LateA list of zero to four user IDs or OPERxxyy values to which messages will besent when the job is marked late. See below for more information.


Messages are stored in the CA-Scheduler database when the value is MAILBOX, andmay be retrieved by the REPORT MAILBOX command.


The CAIJGEN options STRMSG, ENDMSG, FALMSG, ABNMSG, INTMSG,PURMSG and LATMSG specify locations to which all start, end, fail, abend, interrupt,purge, and late messages should be sent. Normally these include MAILBOX.



COMMAND ===>


From Node . .

Inform JES Nodes:

Node . . . . . . . . .

. . . . . . . . .


� �


JNR NODES


4.2 Job Status


NodeUp to eight JES NJE nodes, defined by the CAIJNET macro, that will be notifiedwhen this job starts and ends. This field does not change where the job executes,only who is told about the job.



COMMAND ===>


From Node . .

Cross-Platform information:

Node . . . .

Domain . . .

User id . .

Password . .

Verify . . .

| SU Flag . .

Enter END to exit, or UP for previous screen.

� �


XPLAT CROSS BOTTOM

The fields on this panel are used when submitting jobs to Unicenter TNG orCA-Scheduler Agent on another platform. The execution node (on a previous panel)must be *REMOTE. The fields are:

NodeThe CCI node where the job should execute.

Size/Type: 1 to 8 alphanumeric charactersRequired: NOBatch Keyword: XPNode

DomainThe Microsoft Windows NT Domain to which the user ID below belongs.

Size/Type: 1 to 15 alphanumeric charactersRequired: NoBatch Keyword: XPDomain

4-36 Online Guide

4.2 Job Status

User idThe user ID with which the job should execute.

Size/Type: 1 to 31 alphanumeric charactersRequired: NoBatch Keyword: XPUser

PasswordThe password for the above user ID.

Size/Type: 1 to 14 alphanumeric charactersRequired: NoBatch Keyword: XPPswd

VerifyA second chance to type the password correctly.

| SU Flag| Determines if the Unix Switch User (su) flag is sent for this job or not. If YES,| then the Unix su command is issued with the dash ("-") option. If NO, the dash| option is not used. If blank, the global default (CAS9 CAIJGEN XPSUTYPE)| value is used. The setting has no impact for jobs not executing on Unix-based| systems.

| Size/Type: YES, NO, or blank| Required: No| Batch Keyword: XPSUtype


4.2 Job Status

4.2.2 Predecessor Display

You can see the predecessor display when you select a schedule or job with a P fromthe status displays or when you select option 2 from the schedule and job status detailmenus.

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) PREDECESSORS ROW 1 TO 1 OF 1


Job . . FL6 Number . . �1 Station . . 4� Schedule . . FLOW1

Command Type Name / Current Status Satisfied

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

________ JOB FL5 �1 4� FLOW1 NO

Waiting for Predecessor(s)


� �

The job or schedule's status is displayed at the top of the panel. Any predecessors,including jobs, schedules, data sets, or globals, are displayed in the scrollable portion,along with the predecessors' current status.

The following command may be entered in the command column of one or morepredecessors:

Command Use

P Displays the predecessors of the predecessor. May only be usedon job and schedule predecessors.

4-38 Online Guide

4.2 Job Status

4.2.3 Staged JCL

You can reach the Staged JCL dialog from option 3 of the Job Status Detail menu.

The following panel displays if the job is not staged.


OPTION ===>


From Node . .

This job is not currently staged. Press Enter to issue the RESTAGE command,

or enter END to exit.

� �

Press Enter to stage the job, or press PF3 to exit.

If the job is staged, the job's JCL is displayed in an edit session, such as this:

� � ------ CA-SCHEDULER 9.� xxyy (SCHD) STAGED JCL--WED-�1 4� DAYOWK --------------



��1 //WED JOB '1','CA-SCHEDULER',CLASS=A,MSGCLASS=�

��2 //TESTSTEP EXEC PGM=CAJUTSTB,PARM='T=1 '

��3 //� ��

��4 //� ��

��5 //� �

��6 //� THIS JCL MEMBER IS USED AS MODEL TO SUBMIT LIBTYPE=TESTLIB JOBS. �

��7 //� IT MUST BE ADDED TO YOUR SITE'S JCL LIBRARY (DDNAME=JCLMASTR) �

��8 //� THE JOB NAME IN THE JOB STATEMENT IS REPLACED BY CA-SCHEDULER �

��9 //� JOB NAME TAKEN FROM THE JBR AT SUBMIT TIME. �

��1� //� IF 'TESTLIB PARMS(TESTPARM=)' WAS DEFINED IN THE JBR THEN �

��11 //� THE //TESTSTEP EXEC... CARD IS REPLACED BY AN INTERNAL CARD WITH �

��12 //� THE PARMS TAKEN FROM THE JBR. �

��13 //� RULES FOR THIS MEMBER: �

��14 //� 1- THE JOB CARD MUST REMAIN THE FIRST CARD IN THIS MEMBER �

��15 //� 2- THE FIRST 15 POSITIONS IN THE JOB CARD MUST NOT BE CHANGED �

��16 //� 3- THE JOB CARD MAY BE CONTINUED IF DESIRED. �

��17 //� 4- THE EXEC CARD MAY BE LOCATED ANYWHERE IN THIS MEMBER �

��18 //� 5- THE EXEC CARD CANNOT BE CONTINUED. �

��19 //� 6- THE FIRST 28 POSITIONS IN THE EXEC CARD MUST NOT BE CHANGED �

��2� //� 7- COMMENTS OR ADDITIONAL JCL MAY BE ADDED AS DESIRED. �

��21 //� �

� �

The editor is ISPF/PDF edit--all functions of ISPF/PDF edit are supported.

Besides the normal ISPF/PDF edit commands, you can issue the following commands:

■ 4.2.3.1, “DEXPAND” on page 4-40,■ 4.2.3.2, “RECALL” on page 4-41, and■ 4.2.3.3, “DPROMPT” on page 4-42.


4.2 Job Status

4.2.3.1 DEXPAND

The DEXPAND expands any Driver procedures in the JCL. Note statements are usedto indicate the beginning and end of Driver expansion. For example, if the JCLcontains the following statements:

� � ------ CA-SCHEDULER 9.� xxyy (SCHD) STAGED JCL--BILLING-�1 4� BILLING ---------



��1 //BILLING JOB '1','CA-SCHEDULER',CLASS=A,MSGCLASS=�

��2 //STEP1 EXEC PGM=BILLING

��3 // EXEC BILLPROC

��4 //


� �

(The BILLPROC Driver procedure is used as an example in the Interfaces Guide.)

After the DEXPAND command is issued, the output might look like this:






=NOTE= EXPANDING PROCUDURE BILLPROC

��3 BILLDAT=�4�2yy PSTART=�3�1yy PEND=�331yy DUEDAT=�423yy

=NOTE= END OF DRIVER EXPANSION


� �

Note: The =NOTE= lines are not part of the data in the edit session. A RESETcommand removes them, if desired.

4-40 Online Guide

4.2 Job Status

4.2.3.2 RECALL

The RECALL command returns the JCL being edited to its original contents (or thecontents of the last SAVE command) after a DEXPAND command. For example, theexample in the previous section showed the following output for the DEXPANDcommand:







��3 BILLDAT=�4�2yy PSTART=�3�1yy PEND=�331yy DUEDAT=�423yy



� �

After the RECALL command is issued, the JCL might look like this:








� �


4.2 Job Status

4.2.3.3 DPROMPT

The DPROMPT command lists all reserved Driver variables used by the job and theircurrent values. The values may be changed for this edit session only, possiblychanging the output of the DEXPAND command.

For example, starting this edit session:








� �

The DPROMPT command displays the following:

� � --------------------- CA-SCHEDULER 9.� xxyy (SCHD) DPROMPT -- ROW 1 TO 1 OF 1


Overtype the values of the variables below.

Enter END to save changes and exit. Enter CAN to exit without saving changes.

Variable Value

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

&C_JOBDT yy�92


� �

Only one reserved variable, &C_JOBDT, is displayed because it is the only reservedvariable used by the procedure BILLPROC.

You may change the value of &C_JOBDT by overtyping it and pressing PF3. Forexample, if the value is changed to yy360, saved, and another DEXPAND commandissued, the following would be displayed:







��3 BILLDAT=1226yy PSTART=11�1yy PEND=113�yy DUEDAT=�116yy



� �

Compare this with the output of the DEXPAND command shown in 4.2.3.1,“DEXPAND” on page 4-40.

Changes to reserved variable values are only used within the edit session.

4-42 Online Guide

4.3 Commands

4.3 Commands

Option 3 of the CA-Scheduler monitor menu displays the commands menu.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) COMMANDS --------------------

OPTION ===>

A1 ADD P1 POST

A2 ALLOC P2 PURGE

C1 CANCEL R1 RELEASE

C2 COMPLETE R2 REQUEST

C3 CAN/POST R3 RERUN

R4 RESTAGE

D1 DEALLOC R5 RUN

D2 DISPLAY

S1 SREQ

F1 FORCE S2 START

S3 SUBMIT

G1 GLOBALS

U1 UNPOST

H1 HOLD

V1 VARY

M1 MESSAGES

Enter END to exit.

� �

Each option displays panels to prompt you for the keywords on that command. All ofthe commands require that the CA-Scheduler started task be active.

Use option A1, ADD, to add a job that is not defined to CA-Scheduler to the activeworkload, or to add a predecessor/successor relationship between two jobs in the activeworkload. See 4.3.1, “Add Commands” on page 4-45.

Use option A2, ALLOC, to allocate one or more data sets with a specified ddname tothe CA-Scheduler started task. See 4.3.2, “Alloc Command” on page 4-63.

Use option C1, CANCEL, to remove a schedule or job from the current workload. See4.3.3, “Cancel Commands” on page 4-65.

Use option C2, COMPLETE, to manually mark a job as successfully ended. See 4.3.4,“Complete Job Command” on page 4-71.

Use option C3, CAN/POST, to remove a schedule or job from the current workloadand to allow any successors to run as if the schedule or job completed normally. See4.3.5, “Cancel Post (CP) Commands” on page 4-73.

Use option D1, DEALLOC, to free a ddname from the CA-Scheduler started task. See4.3.6, “Dealloc Command” on page 4-80.

Use option D2, DISPLAY, to view current information common to all ofCA-Scheduler, such as data sets allocated to the started task, autoscan times, andinstallation options. See 4.3.7, “Display Commands” on page 4-82.


4.3 Commands

Use option F1, FORCE, to allow schedules and jobs to start even though not allpredecessors have been satisfied. See 4.3.8, “Force Command” on page 4-90.

Use option G1, GLOBALS, to view and change CA-Scheduler global variables. See4.3.9, “Globals” on page 4-95.

Use option H1, HOLD, to prevent schedules and jobs from starting. See 4.3.10, “HoldCommands” on page 4-96.

Use option M1, MESSAGES, to send or display messages within CA-Scheduler. See4.3.11, “Messages Menu” on page 4-102.

Use option P1, POST, to allow successors of schedules, jobs, job steps, and data setsto start. See 4.3.12, “Post Menu” on page 4-105.

Use option P2, PURGE, to remove completed and canceled schedules and jobs fromthe status displays. See 4.3.13, “Purge Commands” on page 4-124.

Use option R1, RELEASE, to allow schedules and jobs previously held (option H1) tostart. See 4.3.14, “Release Commands” on page 4-129.

Use option R2, REQUEST, to allow not-requested schedules and jobs and theirsuccessors to start. See 4.3.15, “Request Commands” on page 4-138.

Use option R3, RERUN, to resubmit CPU jobs that had previously failed or abended.See 4.3.16, “Rerun Job Command” on page 4-142.

Use option R4, RESTAGE, to copy a CPU job's JCL into the CA-Scheduler staginglibrary. See 4.3.17, “Restage Job Command” on page 4-146.

Use option R5, RUN, to add defined schedules and jobs to the current workload. See4.3.18, “Run Commands” on page 4-148.

Use option S1, SREQ, to allow not-requested schedules and jobs and selectedsuccessors to start. See 4.3.19, “SREQ Commands” on page 4-153.

Use option S2, START, to manually mark a job as started. See 4.3.20, “Start JobCommand” on page 4-158.

4-44 Online Guide

4.3 Commands

Use option S3, SUBMIT, to resubmit CPU jobs that had previously failed or abended.See 4.3.21, “Submit Job Command” on page 4-160.

Use option U1, UNPOST, to require successors of schedules, jobs, job steps, and datasets to wait, even if the predecessor has already completed. See 4.3.22, “UnpostCommands” on page 4-164.

Use option V1, VARY, to start or stop CA-Scheduler NJE VTAM sessions. See4.3.23, “Vary Commands” on page 4-183.

4.3.1 Add Commands

Use option A1 of the CA-Scheduler Commands menu to display the Add menu.

The Add commands introduce new work or a new relationship to the active workloadwithout having to first define anything to the database. Add commands are temporary,in that their effect is only for the current active workload, not for any future workload.

� �----------------------- CA-SCHEDULER 9.� xxyy (SCHD) ADD ----------------------

OPTION ===>

1 JOB - Add a Job

2 PRED - Add a Predecessor

Enter END to exit.

� �

Use option 1, JOB, to add an undefined job to the active workload. See 4.3.1.1, “AddJob Command” on page 4-46 for more information.

Use option 2, PRED, to add a predecessor/successor relationship between two jobs inthe workload. See 4.3.1.2, “Add Pred Command” on page 4-61 for more information.


4.3 Commands

4.3.1.1 Add Job Command

Use option 1 of the CA-Scheduler Add Commands menu to display the Add Jobdialog. The fields are contained on several panels. Use PF7 and PF8 to scroll up anddown through the panels. To issue the ADD JOB command, use PF3. To exit withoutissuing the ADD JOB command, enter CAN on the command line.

The batch utility to use for adding jobs is CAJUCMD0. The batch command is ADDJOB.

� � --------------------- CA-SCHEDULER 9.� xxyy (SCHD) ADD JOB --------------------

COMMAND ===>

Name . . . Number . . �1 Station . . 4� Schedule . .

Selection:

Backlog . . . . NO

Times:

Early Start . . . . .

Must Start . . . . .

Must End . . . . . .

Maximum Execution . .

Miscellaneous:

Internal Priority . .

Enter END to Exit, or DOWN for Next Screen.

� �

You may jump to this panel from other Add Job panels by using one of the followingjump commands:

TOP BASE TIMes BACKlog

The fields are:

NameThe name of the job being added.


4-46 Online Guide

4.3 Commands

NumberThe number of the job being added. Up to 99 jobs with the same name, station,and schedule may be in the current workload.

Size/Type: 2 numeric charactersRequired: NoBatch Keyword: JNoDefault: 01

StationThe location where the job executes. Station 40 means a CPU job, which executeson the system. Stations less than 40 are for pre-CPU manual tasks, and stationsgreater than 40 are for post-CPU manual tasks.

Size/Type: 2 numeric charactersRequired: NoBatch Keyword: STationDefault: 40

ScheduleThe schedule to which this job belongs.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ScheduleDefault: The four-character value of CAIJGEN installation option $DYNNM

followed by the current SMF ID

BacklogDetermines what action CA-Scheduler should take if the job has not completed bythe next autoscan and the job is scheduled to run again. YES indicates that the jobshould be retained until it (and the rest of its schedule) has completed. NOindicates that the job should be canceled (if not currently executing) and the nextday's copy made available. Blank causes the schedule's Backlog option to be used.

Size/Type: YES/NO/blankRequired: NoBatch Keyword: BacklogDefault: NO

Early StartThe earliest time that this job can start.

The value is in the format of ddhhmm, where dd is the number of autoscans thatthe job should wait, and hhmm is the time to start. Leading zeros do not need tobe entered.

Size/Type: 1 to 6 numeric characters in ddhhmm formatRequired: NoBatch Keyword: ErlytimeDefault: 0 (job may be started immediately)


4.3 Commands

Must Start| If the job has not started by this time, it is considered late. A message may be| sent to the console, the MAILBOX report, and/or a user.


Size/Type: 1 to 6 numeric characters in ddhhmm formatRequired: NoBatch Keyword: MUsttimeDefault: 0 (Never considered late)

Must End| If the job has not ended by this time, it is considered late. A message may be sent| to the console, the MAILBOX report, and/or a user.


Size/Type: 1 to 6 numeric characters in ddhhmm formatRequired: NoBatch Keyword: DeadlineDefault: 0 (Never considered late)

Maximum Execution| If the job takes longer than this time to complete, it is considered late. A message| may be sent to the console, the MAILBOX report, and/or a user.


Size/Type: 1 to 6 numeric characters in ddhhmm formatRequired: NoBatch Keyword: MaxtimeDefault: 0 (Never considered late)

Internal PriorityA number from 0 to 99, where 99 is the higher priority, that controls the order ofinternal control blocks. CA-Scheduler searches these control blocks to find work.

Size/Type: 1 to 2 numeric charactersRequired: NoBatch Keyword: JPrtyDefault: 0

Press PF8 for the next panel. It is only displayed for CPU jobs (station = 40).

4-48 Online Guide

4.3 Commands

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) ADD CPU JOB ------------------

COMMAND ===>

Name . . . A Number . . �1 Station . . 4� Schedule . .

JCL:

Library Type . . . .

JCL DDname . . . . . Member Prefix . . .

Member Name . . . .

Submission:

Local Execution Sysid . .

Remote Execution Node . .

Remote Execution Sysid .

Enter END to Exit, UP for Previous Screen, or DOWN for Next Screen.

� �


JCL SUBmit

The fields are:

Library TypeThe access method to use in retrieving the JCL for this job.

A default access method is specified in the CAIJGEN option LIBTYPE.

Valid values are:


JOBDOC CA-Jobdoc

LIBRN CA-Librarian

PANV CA-Panvalet





4.3 Commands


ROSCOE CA-Roscoe

Required: NoBatch Keyword: LibtypeDefault: Value on CAIJGEN option LIBTYPE

JCL DDnameFor library type of PDS, the ddname of the partitioned data set containing thejob's JCL.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: DDnameDefault: JCLMASTR

Member PrefixA one to eight byte value that will prefix the Member Name field to generate amaximum ten-character name of CA-Panvalet members.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: MBrsubid

Member NameThe member name that contains the job's JCL.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: LIBMembDefault: Job name

Local Execution SysidThe system ID on which this job should execute. The system ID must be part ofthe local multi-CPU environment.

Size/Type: 1 to 4 alphanumeric charactersRequired: NoBatch Keyword: SYsidDefault: Current system ID

Remote Execution NodeThe NJE node at which this job should execute.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: NOdeDefault: Local NJE node

4-50 Online Guide

4.3 Commands

Remote Execution SysidThe system ID at another node on which this job should execute.

Size/Type: 1 to 4 alphanumeric charactersRequired: NoBatch Keyword: NODESys


� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) ADD CPU JOB ------------------

COMMAND ===>

Name . . . Number . . Station . . Schedule . .

Failures:

Fail Oper . . . .

Fail Code . . . .

Abend Option . . .

Fail Option . . .

Options:

Insert CA-11 . NO Interrupt . . . . .

Stage JCL . . NO

Memo . . . . .

Test Parm . .


� �


FAILures OPTions

The fields are:

Fail OperA Boolean operator used in determining if the job ended with an unacceptablereturn code. See Fail Code. Valid values are GE (Greater than or Equal), GT(Greater Than), EQ (EQual), NE (Not Equal), LE (Less than or Equal), and LT(Less Than).


Fail CodeA number that is compared to the job's highest return code using the Fail Oper todetermine if the job ended with an unacceptable return code. The followingequation is evaluated:

job's-high-return-code Fail-Oper Fail-Code


4.3 Commands

If the statement is true, then the job is marked as failed. A typical setting is a FailOper of GE and a Fail Code of 1, making zero the only acceptable return code forthe job.



ABORTDo not let successors run.




Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: AbendDefault: ABORT






Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: FAILEdDefault: ABORT

4-52 Online Guide

4.3 Commands

Insert CA-11Controls the automatic insertion of the CA-11 RMS.

Size/Type: YES or NORequired: NoBatch Keyword: INSrrmsDefault: NO

InterruptIf Interrupt is set to Yes, the job is marked as Interrupted instead of Completewhen it ends normally.

Size/Type: YES or NORequired: NoBatch Keyword: INteruptDefault: NO

Stage JCLIf Stage JCL is set to Yes, the job's JCL is copied into the CA-Scheduler activeworkload and submitted from there.

Size/Type: YES or NORequired: NoBatch Keyword: STAGeDefault: NO

MemoThe value of the Memo field is displayed as a WTOR (Write To Operator withReply) at the beginning of the job. A manual reply by the operator is requiredbefore the job may execute.

Size/Type: 1 to 60 alphanumeric charactersRequired: NoBatch Keyword: MEmo

Test ParmFor library type of TESTLIB, the Test Parm determines how long the job executesand how it ends. One or more of the following may be specified:

T=nnnnNumber of seconds to execute

F=nnnnNormal return code to generate

A=nnnnAbend code to generate (user abend)

If multiple options are specified, separate them with commas.

Size/Type: 1 to 20 alphanumeric charactersRequired: NoBatch Keyword: TEstparmDefault: The values specified on member CAJUTSTB in your JCLMASTR

data set


4.3 Commands

Press PF8 for the next panel. It is only displayed for non-CPU jobs (station not equalto 40).

� � ----------------- CA-SCHEDULER 9.� xxyy (SCHD) ADD NON-CPU JOB ----------------

COMMAND ===>


Non-CPU Options:

Automatic Start . . NO


� �

The fields are:

Automatic StartIf Automatic Start is set to Yes, then the non-CPU job is started as soon as allpredecessors have been satisfied.

If Automatic Start is set to No, then the START command must be used. See4.3.20, “Start Job Command” on page 4-158.

Size/Type: YES or NORequired: NoBatch Keyword: AUtostrtDefault: NO


4-54 Online Guide

4.3 Commands

� � --------------------- CA-SCHEDULER 9.� xxyy (SCHD) ADD JOB --------------------

COMMAND ===>


Simulation:

JES Class . . . . . . .

JES Priority . . . . .

Documentation:

Display Key . . .

Display Time . .


� �


SIM DOC

The fields are:

JES ClassThe value that SIMULATE REVISE=YES should use in determining whichsimulation initiator the job should use. The value is not used outside of simulation.

Size/Type: 1 alphanumeric characterRequired: NoBatch Keyword: ClassDefault: A

JES PriorityThe value that SIMULATE REVISE=YES should use in determining when a jobshould start in the simulation. If multiple jobs are available to start, jobs with highJES Priority values are started first. The value is not used outside of simulation.

Size/Type: 1 to 2 numeric characters from 0 to 15Required: NoBatch Keyword: Prty

Display KeyA one to eight character key of documentation that should be displayed on theOS/390 console for this job.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: Dispkey


4.3 Commands

Display TimeThe time at which the documentation referred to by Display Key should bedisplayed on the OS/390 console.


Size/Type: 1 to 6 numeric characters in ddhhmm formatRequired: NoBatch Keyword: DISPTimeDefault: 0 (Display documentation immediately)


� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) ADD PREDS -------------------

COMMAND ===>


Successors:

Job name JNO St Schedule ProcStep Stepname Oper Code

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

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .


� �


PReds

Up to six job or job step predecessors may be defined that must complete before thejob being added may start.

The columns are:

Job nameThe name of the job that must complete or that contains the job step that mustcomplete.

Size/Type: 1 to 8 alphanumeric charactersRequired: Yes if anything else on same line is enteredBatch Keyword: PJOBn where n is 1 to 6

4-56 Online Guide

4.3 Commands

JNOThe number of the job that must complete or that contains the job step that mustcomplete.

Size/Type: 1 to 2 numeric characters from 1 to 99Required: NoBatch Keyword: PJNOn where n is 1 to 6Default: 01

StThe station of the job that must complete or that contains the job step that mustcomplete.

Size/Type: 1 to 2 numeric characters from 1 to 99Required: NoBatch Keyword: PSTn where n is 1 to 6Default: 40

ScheduleThe schedule of the job that must complete or that contains the job step that mustcomplete.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: PSCHDn where n is 1 to 6Default: Any job that matches the other information on the line satisfies the

requirement.

ProcStepThe procedure step name (outside of the PROC) that must complete.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: PPROCn where n is 1 to 6

StepnameThe step name (with the EXEC PGM=) that must complete.

Size/Type: 1 to 8 alphanumeric charactersRequired: No, unless ProcStep, Oper, or Code is enteredBatch Keyword: PSTEPn where n is 1 to 6

OperA Boolean operator used to determine if the step successfully ended. See Code.Valid values are as follows:

GEGreater than or Equal

GTGreater Than

EQEQual


4.3 Commands

NENot Equal

LTLess Than

LELess than or Equal

Required: NoBatch Keyword: PFOPRn where n is 1 to 6

CodeA number compared to the return code of the specified step to determine if thestep ended successfully. The following statement is evaluated:

step-return-code Oper Code

If the statement is true, the condition is satisfied. Typical values are Oper set toEQ and Code set to 0 (zero) to allow only a return code of zero.

Size/Type: 1 to 5 numeric characters from 0 to 4095Required: No, unless Oper is specifiedBatch Keyword: FAILn where n is 1 to 6Default: If Oper and Code are not entered, then any normal end (not an

abend) of the step is accepted


� � ----------------- CA-SCHEDULER 9.� xxyy (SCHD) ADD SUCCESSORS -----------------

COMMAND ===>


Successors:

Job name JNO St Schedule ProcStep Stepname Oper Code

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

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

. . . . . . .

Enter END to Exit or UP for Previous Screen.

� �


SUccess BOTtom

4-58 Online Guide

4.3 Commands

Up to six jobs may be defined that must wait for the job being added to complete (or astep in job being added) before they may start.

The columns are:

Job nameThe name of the job that must wait for the job being added or one of its steps.

Size/Type: 1 to 8 alphanumeric charactersRequired: Yes if anything else on same line is enteredBatch Keyword: SJOBn where n is 1 to 6

JNOThe number of the job that must wait for the job being added or one of its steps.

Size/Type: 1 to 2 numeric characters from 1 to 99Required: NoBatch Keyword: SJNOn where n is 1 to 6Default: 01

StThe station of the job that must wait for the job being added or one of its steps.

Size/Type: 1 to 2 numeric characters from 1 to 99Required: NoBatch Keyword: SSTn where n is 1 to 6Default: 40

ScheduleThe schedule of the job that must wait for the job being added or one of its steps.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: SSCHDn where n is 1 to 6Default: Any job that matches the other information on the line waits

ProcStepThe procedure step name (outside of the PROC) that must complete.

Note that the procstep is in the job being added.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: SPROCn where n is 1 to 6

StepnameThe step name (with the EXEC PGM=) that must complete.

Note that the step is in the job being added.

Size/Type: 1 to 8 alphanumeric charactersRequired: No, unless ProcStep, Oper, or Code is enteredBatch Keyword: SSTEPn where n is 1 to 6


4.3 Commands

OperA Boolean operator used to determine if the step successfully ended. See Code.Valid values are as follows:

GEGreater than or Equal

GTGreater Than

EQEQual

NENot Equal

LTLess Than

LELess than or Equal


Size/Type: 2 alphanumeric charactersRequired: NoBatch Keyword: SFOPRn where n is 1 to 6

CodeA number compared to the return code of the specified step to determine if thestep ended successfully. The following statement is evaluated:

step-return-code Oper Code

If the statement is true, the condition is satisfied. Typical values are Oper set toEQ and Code set to 0 (zero) to allow only a return code of zero.


Size/Type: 1 to 4 numeric characters from 0 to 4095Required: No, unless Oper is specifiedBatch Keyword: SFAILn where n is 1 to 6Default: If Oper and Code are not entered, then any normal end (not an

abend) of the step is accepted

4-60 Online Guide

4.3 Commands

4.3.1.2 Add Pred Command

Use option 2 of the CA-Scheduler Add Commands menu to display the Add Preddialog.

The Add Pred command defines a predecessor/successor relationship between two jobsin the workload without having to change the successor job's criteria. The change isonly for the current workload. Both jobs must be in the workload. The predecessor jobmay not be complete, and the successor job may not have started.

The batch utility to use is CAJUCMD0. The batch command is ADD PRED.

� �-------------------- CA-SCHEDULER 9.� xxyy (SCHD) ADD PRED --------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

Should wait for job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

Enter END to exit.

� �

The fields are:

Job NameThe name of the successor job. The successor job may not be started yet.


NumberThe JNO of the successor job.

Size/Type: 2 numeric charactersRequired: NoBatch Keyword: JNODefault: 01


4.3 Commands

StationThe station of the successor job.


ScheduleThe schedule of the successor job.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: ScheduleDefault: 40

Should wait for job nameThe name of the predecessor job. The predecessor job may not be completed yet.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: PJOB

NumberThe JNO of the predecessor job.

Size/Type: 2 numeric charactersRequired: NoBatch Keyword: PJNODefault: 01

StationThe station of the predecessor job.

Size/Type: 2 numeric charactersRequired: NoBatch Keyword: PSTatDefault: 40

ScheduleThe schedule of the predecessor job.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: PSChd

4-62 Online Guide

4.3 Commands

4.3.2 Alloc Command

Use option A2 of the CA-Scheduler Commands menu to display the Alloc commanddialog.

The Alloc command allocates one or more data sets to a specified ddname in theCA-Scheduler started task. Typically, you use it to allocate a new (or newlycompressed) JCL library.

See also 4.3.6, “Dealloc Command” on page 4-80 and 4.3.7.1, “Display AllocCommand” on page 4-83.

The batch utility to use is CAJUCMD0. The batch command is ALLOC.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) ALLOCATE ------------------

COMMAND ===>

Allocate:

DDname . . . . .

Dataset 1 . . .

Dataset 2 . . .

Dataset 3 . . .

Dataset 4 . . .

Dataset 5 . . .

Dataset 6 . . .

Dataset 7 . . .

Dataset 8 . . .

Dataset 9 . . .

Dataset 1� . . .

Options:

Auto Submit . . YES

Execute command at:

Sysid . . Route . . Route Sysid . .

Enter END to exit.

� �

The fields are:

DDnameThe ddname to which the data sets is allocated in the CA-Scheduler started task.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: DDname

Dataset 1-10The data sets that should be allocated. The data set names must be fully qualified,without quotes. Your default prefix is NOT added.

Size/Type: 1 to 44 alphanumeric charactersRequired: At least one data set name is requiredBatch Keyword: DSNnn where nn is 01 to 10


4.3 Commands

Auto SubmitIf Auto Submit is set to YES, then after the successful allocation of the data setsCA-Scheduler searches for any jobs currently in Submit Failed status.CA-Scheduler tries to resubmit the jobs.

Size/Type: YES or NORequired: NoBatch Keyword: AUTosubDefault: YES

SysidUse Sysid to execute the command on another CPU in a multiple-CPUenvironment.

Size/Type: 1 to 4 alphanumeric charactersRequired: NoBatch Keyword: SYSidDefault: Current CPU

RouteUse Route to execute the command on another node in an NJE environment.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ROuteDefault: Current node

Route SysidUse Route Sysid to execute the command on a specific CPU at another node in anNJE environment.

Size/Type: 1 to 4 alphanumeric charactersRequired: NoBatch Keyword: ROUTSys

4-64 Online Guide

4.3 Commands

4.3.3 Cancel Commands

Use option C1 of the CA-Scheduler Commands menu to display the Cancel menu.

The Cancel commands remove work from the current workload. Successor jobs andschedules are not allowed to start.

See also 4.3.5, “Cancel Post (CP) Commands” on page 4-73.

� � --------------------- CA-SCHEDULER 9.� xxyy (SCHD) CANCEL ---------------------

OPTION ===>

1 JOB - Cancel a Job

2 SCHEDULE - Cancel a Schedule

3 ALL - Cancel All Jobs and Schedules

Enter END to exit.

� �

Use option 1, JOB, to remove a specific job from the workload. See 4.3.3.1, “CancelJob Command” on page 4-66 for more information.

Use option 2, SCHEDULE, to remove a schedule and all of its jobs from theworkload. See 4.3.3.2, “Cancel Schedule Command” on page 4-68 for moreinformation.

Use option 3, ALL, to remove all schedules and jobs from the workload. See 4.3.3.3,“Cancel All Command” on page 4-70 for more information.


4.3 Commands

4.3.3.1 Cancel Job Command

Option 1 of the Cancel menu displays the Cancel Job dialog.

The Cancel Job command removes a specific job from the workload. If the job hasbeen submitted to OS/390, it is canceled even if it is currently executing.

The batch utility to use is CAJUCMD0. The batch command is CANCEL JOB.

� �-------------------- CA-SCHEDULER 9.� xxyy (SCHD) CANCEL JOB -------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

From Node . . .

Cancel job . . . (if already submitted/started)

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe name of the job to be removed from the workload.


NumberThe number of the job to be removed from the workload.

Size/Type: 1 to 2 numeric characters from 1 to 99Required: NoBatch Keyword: JNoDefault: 01

4-66 Online Guide

4.3 Commands

StationThe station of the job to be removed from the workload.

Size/Type: 1 to 2 numeric characters from 1 to 99Required: NoBatch Keyword: STationDefault: 40

ScheduleThe schedule of the job to be removed from the workload.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ScheduleDefault: First schedule in the current workload that contains this job

From NodeThe name of the node where the job was submitted. Only used in an NJEenvironment.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: FMnodeDefault: Current node

Cancel jobDetermines if the job should be canceled from the operating system if it hasalready been submitted or has already started. If not specified, the CAIJGENCANCJOB value is used.

Size/Type: YES|NORequired: NoBatch Keyword: CANcelDefault: CAIJGEN CANCJOB value




Size/Type: 1 to 4 alphanumeric charactersRequired: NoBatch Keyword: ROUTsys


4.3 Commands

4.3.3.2 Cancel Schedule Command

Option 2 of the Cancel menu displays the Cancel Schedule dialog.

The Cancel Schedule command removes a schedule and all of its jobs from the currentworkload. If any of the jobs have been submitted to OS/390, they are canceled even ifthey are currently executing.

The batch utility to use is CAJUCMD0. The batch command is CANCELSCHEDULE.

� � ----------------- CA-SCHEDULER 9.� xxyy (SCHD) CANCEL SCHEDULE ----------------

COMMAND ===>

Schedule:

Schedule Name . .

From Node . . . .

Cancel jobs . . . (if already submitted/started)

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

ScheduleThe name of the schedule to be removed from the workload.


From NodeThe name of the NJE node where the schedule is controlled. This field is onlyused in an NJE environment.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: FMnode

4-68 Online Guide

4.3 Commands

Cancel jobsDetermines if the jobs should be canceled from the operating system if they havealready been submitted or have already started. If not specified, the CAIJGENCANCJOB value is used.







4.3 Commands

4.3.3.3 Cancel All Command

Option 3 of the Cancel menu displays the Cancel All dialog.

The Cancel All command removes all schedules and jobs from the current workload. Ifany of the jobs have been submitted to OS/390, they are canceled even if they arecurrently executing.

The batch utility to use is CAJUCMD0. The batch command is CANCEL ALL. Thecommand has no keywords.

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) CANCEL ALL -------------------

COMMAND ===>

Press ENTER to cancel all Schedules and Jobs.

Enter END to exit.

� �

The panel has no fields. Press Enter to cancel the entire workload. Press PF3 to exitwithout canceling the workload.

4-70 Online Guide

4.3 Commands

4.3.4 Complete Job Command

Use option C2 of the CA-Scheduler Commands menu to display the Complete Jobdialog.

The Complete Job command manually marks a job as successfully completed.Successor schedules and jobs are allowed to start.

Typically, you use the Complete Job command for non-CPU jobs, but you may alsouse it for CPU jobs in a recovery situation.

The batch utility to use is CAJUCMD0. The command is COMPLETE JOB.

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) COMPLETE JOB ------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 39

Schedule . . . .

From Node . . .

Options:

CPU Job . . . . . . . . . NO

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe name of the job to be completed.


NumberThe number of the job to be completed.



4.3 Commands

StationThe station of the job to be completed.

Size/Type: 1 to 2 numeric characters from 1 to 99Required: NoBatch Keyword: STationDefault: Station number specified in Default Start/Complete Station field in

Chapter 3, “Options” on page 3-1

ScheduleThe schedule of the job to be completed.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ScheduleDefault: First schedule in the current workload that contains the job



CPU JobSpecify YES if this is a CPU job (station 40). CPU Job is used as a safety toprevent a manual completion on a job running in the system.

Size/Type: YES or NORequired: NoBatch Keyword: CPU=Y or CPU=NDefault: NO





4-72 Online Guide

4.3 Commands

4.3.5 Cancel Post (CP) Commands

Use option C3 of the CA-Scheduler Commands menu to display the Cancel Postmenu.

The Cancel Post commands remove work from the current workload. Successor jobsand schedules are allowed to start.

See also 4.3.3, “Cancel Commands” on page 4-65.

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) CANCEL/POST ------------------

OPTION ===>

1 JOB - Cancel a Job and Post its Successors

2 SCHEDULE - Cancel a Schedule and Post its Successors

Enter END to exit.

� �

Use option 1, JOB, to remove a specific job from the workload. See the next topic formore information.

Use option 2, SCHEDULE, to remove a schedule and all of its jobs from theworkload. See 4.3.5.2, “Cancel Post Schedule Command” on page 4-77 for moreinformation.


4.3 Commands

4.3.5.1 Cancel Post (CP) Job Command

Option 1 of the Cancel Post menu displays the Cancel Post Job dialog.

The Cancel Post Job command removes a specific job from the workload. If the jobhas been submitted to OS/390, it is canceled even if it is currently executing.Successor schedules and jobs are allowed to start.

The batch utility to use is CAJUCMD0. The batch command is CP JOB.

� � ----------------- CA-SCHEDULER 9.� xxyy (SCHD) CANCEL/POST JOB ----------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

From Node . . .

Cancel Job . . . (if already submitted/started)

Post only this Successor:

Job Name . . . .

Number . . . . .

Station . . . .

Schedule . . . .

Execute command at:

Route . . . . . Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe name of the job to be removed from the workload.


NumberThe number of the job to be removed from the workload.


4-74 Online Guide

4.3 Commands

StationThe station of the job to be removed from the workload.


ScheduleThe schedule of the job to be removed from the workload.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ScheduleDefault: The first schedule in the current workload that contains this job



Cancel jobDetermines if the job should be canceled from the operating system if it hasalready been submitted or has already started. If not specified, the CAIJGENCANCJOB value is used.


Post only this SuccessorIn allowing successors to start, you may allow all successors or identify a specificjob that may start, leaving all others to continue waiting. By leaving the fieldsunder Post only this Successor blank, all successors may start. By entering a jobname, only that successor may start.

Job Name

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ONLYJob

Number

Size/Type: 1 to 2 numeric characters from 1 to 99Required: NoBatch Keyword: ONLYJNoDefault: 01


4.3 Commands

Station

Size/Type: 1 to 2 numeric characters from 1 to 99Required: NoBatch Keyword: ONLYSTDefault: 40

Schedule

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ONLYScdDefault: The first schedule in the current workload that contains the Post

Only job name





4-76 Online Guide

4.3 Commands

4.3.5.2 Cancel Post Schedule Command

Option 2 of the Cancel Post menu displays the Cancel Post Schedule dialog.

The Cancel Post Schedule command removes a schedule and all of its jobs from thecurrent workload. If any of the jobs have been submitted to OS/390, they are canceledeven if they are currently executing.

The batch utility to use is CAJUCMD0. The batch command is CP SCHEDULE.

� � -------------- CA-SCHEDULER 9.� xxyy (SCHD) CANCEL/POST SCHEDULE --------------

COMMAND ===>

Schedule:

Schedule Name . .

From Node . . . .

Cancel jobs . . . (if already submitted/started)


Job Name . . . .

Number . . . . .

Station . . . .

Schedule . . . .

Execute command at:


Enter END to exit.

� �

The fields are:

Schedule NameThe name of the schedule to be removed from the workload.





4.3 Commands

Cancel jobsDetermines if the jobs should be canceled from the operating system if they havealready been submitted or have already started. If not specified, the CAIJGENCANCJOB value is used.



Job Name


Number

Size/Type: 1 to 2 numeric characters from 1 to 99Required: NoBatch Keyword: ONLYJNODefault: 01

Station


Schedule

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ONLYScdDefault: First schedule in the current workload that contains the Post

Only job name



4-78 Online Guide

4.3 Commands






4.3 Commands

4.3.6 Dealloc Command

Use option D1 of the CA-Scheduler Commands menu to display the DeallocCommand dialog.

The Dealloc Command frees (deallocates) a specified ddname from the CA-Schedulerstarted task. You typically use the command to make a JCL data set available forcompressing.

The batch utility to use is CAJUCMD0. The command is DEALLOC.

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) DEALLOCATE -------------------

COMMAND ===>

Deallocate:

DDname . . . . .

Execute command at:

Sysid . . . . .

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

DDnameThe ddname that should be freed from the CA-Scheduler started task.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: DDname



4-80 Online Guide

4.3 Commands






4.3 Commands

4.3.7 Display Commands

Use option D2 from the CA-Scheduler Commands menu to display the DisplayCommands menu.

� �--------------------- CA-SCHEDULER 9.� xxyy (SCHD) DISPLAY --------------------

OPTION ===>

1 ALLOC - List Datasets Allocated to the CA-Scheduler Started Task

2 DATE - Autoscan Information

3 DATASET - List NJE Dataset Posting Rules

4 MVSJOBS - List Jobs that will be Tracked from outside of CA-Scheduler

5 NETWORK - Status of CA-Scheduler NJE Interface

6 SECURITY - Status of CA-Scheduler External Security Interface

7 XPLAT - Status of cross-platform nodes

8 EVENTS - Cross-platform external events being tracked

9 FLOW - Critical Path Monitoring flows currently loaded

A VRM - Status of virtual resources known to CA-Scheduler

Enter END to exit.

� �

Use option 1, ALLOC, to display data sets allocated to the CA-Scheduler started task.See the next topic for more information.

Use option 2, DATE, to get status on autoscan. See 4.3.7.2, “Display Date Command”on page 4-84 for more information.

Use option 3, DATASET, to list the contents of the CAIJ$DSN macro currently beingused. See 4.3.7.3, “Display Dataset Command” on page 4-85 for more information.

Use option 4, MVSJOBS, to list the contents of the CAIJ$MVS macro currently beingused. See 4.3.7.4, “Display MVSJobs Command” on page 4-86 for more information.

Use option 5, NETWORK, to display the status of the CA-Scheduler NJE VTAMsessions. See 4.3.7.5, “Display Network Command” on page 4-87 for moreinformation.

Use option 6, SECURITY, to list the contents of the CAIJ$SEC macro currently beingused. See 4.3.7.6, “Display Security Command” on page 4-87 for more information.

Use option 7, XPLAT, to display the status of cross-platform nodes with whichCA-Scheduler is communicating. See 4.3.7.7, “Display XPLAT Command” onpage 4-88 for more information.

4-82 Online Guide

4.3 Commands

Use option 8, EVENTS, to display the cross-platform external events that are currentlybeing tracked. See 4.3.7.8, “Display Events” on page 4-88 for more information.

Use option 9, FLOW, to display a list of flows available for the Critical PathMonitoring system. See 4.3.7.9, “Display Flow” on page 4-88 for more information.

Use option A, VRM, to display a list of virtual resources known to CA-Scheduler, andthe jobs currently using or waiting for those resources. See 4.3.7.10, “Display VRMCommand” on page 4-89 for more information.

4.3.7.1 Display Alloc Command

Option 1 of the CA-Scheduler Display Commands menu displays the Display AllocCommand dialog.

The Display Alloc Command lists the data sets allocated to the CA-Scheduler startedtask. The ddname, data set name, and volume serial are displayed.

The batch utility to use is CAJUCMD0. The batch command is DISPLAY ALLOC.

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) DISPLAY ALLOC -----------------

COMMAND ===>

Options:

DDname . . . . (Leave blank for all allocations)

Enter END to exit.

� �

The fields are:

DDnameIf entered, Display Alloc shows only the specified ddname and its data sets.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: DDnameDefault: All ddnames


4.3 Commands

4.3.7.2 Display Date Command

Option 2 of the CA-Scheduler Display Commands menu displays the Display DateCommand dialog.

The Display Date Command provides information about the last autoscan performedand the next autoscan to be performed. It also gives the current system date and time.

The batch utility to use is CAJUCMD0. The batch command is DISPLAY DATE.

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) DISPLAY DATE ------------------

COMMAND ===>

System:

Sysid . . (Leave blank for local system)

Enter END to exit.

� �

The field is:

SysidThe system ID for which you want to see autoscan information.

Size/Type: 1 to 4 alphanumeric charactersRequired: NoBatch Keyword: SYSidDefault: Current system

4-84 Online Guide

4.3 Commands

4.3.7.3 Display Dataset Command

Option 3 of the CA-Scheduler Display Commands menu displays the Display DatasetCommand dialog.

The Display Dataset Command lists the contents of the CAIJ$DSN macro currently inuse. See the CAIJ$DSN Macro in the Systems Programmer Guide.

The batch utility to use is CAJUCMD0. The batch command is DISPLAY $DSN.

� � -------------- CA-SCHEDULER 9.� xxyy (SCHD) DISPLAY NJE DATASETS --------------

COMMAND ===>

Options:

From entry . . . (Leave blank to start at the top)

For entries . . (Leave blank to entire list)

Enter END to exit.

� �

The fields are:

From entryThe output starts at the CAIJ$DSN entry number specified here.

Size/Type: 1 to 6 numeric charactersRequired: NoBatch Keyword: FRomDefault: 1 (The display starts at the first entry)

For entriesThe output stops after this many entries have been displayed.

Size/Type: 1 to 6 numeric charactersRequired: NoBatch Keyword: FOrDefault: All entries


4.3 Commands

4.3.7.4 Display MVSJobs Command

Option 4 of the CA-Scheduler Display Commands menu displays the DisplayMVSJobs Command dialog.

The Display MVSJobs Command lists the contents of the CAIJ$MVS macro currentlyin use. See the CAIJ$MVS Macro in the Systems Programmer Guide.

The batch utility to use is CAJUCMD0. The batch command is DISPLAY $MVS.

� � ---------------- CA-SCHEDULER 9.� xxyy (SCHD) DISPLAY $MVS JOBS ---------------

COMMAND ===>

Options:

From entry . . . (Leave blank to start at the top)

For entries . . (Leave blank to entire list)

Enter END to exit.

� �

The fields are:

From entryThe output starts at the CAIJ$MVS entry number specified here.

Size/Type: 1 to 6 numeric charactersRequired: NoBatch Keyword: FRomDefault: 1 (The display starts at the first entry)

For entriesThe output stops after this many entries have been displayed.

Size/Type: 1 to 6 numeric charactersRequired: NoBatch Keyword: FOrDefault: All entries

4-86 Online Guide

4.3 Commands

4.3.7.5 Display Network Command

Option 5 of the CA-Scheduler Display Commands Menu displays the Display Networkcommand.

The Display Network command lists the status of the CA-Scheduler NJE VTAMsessions.

Since the command has no keywords, it is issued immediately without an interveningpanel.

The batch utility to use is CAJUCMD0. The batch command is DISPLAYNETWORK.

4.3.7.6 Display Security Command

Option 6 of the CA-Scheduler Display Commands menu displays the Display Securitycommand.

The Display Security command lists the CA-Scheduler security options currently inuse.


The batch utility to use is CAJUCMD0. The batch command is DISPLAY $SEC.


4.3 Commands

4.3.7.7 Display XPLAT Command

Option 7 of the CA-Scheduler Display Commands menu displays the Display XPLATcommand.

The Display XPLAT command lists the cross-platform nodes with whichCA-Scheduler is communicating and their status.


The batch utility to use is CAJUCMD0. The batch command is DISPLAY XPLAT.

4.3.7.8 Display Events

Option 8 of the CA-Scheduler Display Commands menu displays the Display Eventscommand.

The Display Events command lists the cross-platform external events that are currentlybeing tracked.


The batch utility to use is CAJUCMD0. The batch command is DISPLAY EVENTS.

4.3.7.9 Display Flow

Option 9 of the CA-Scheduler Display Commands menu displays the Display Flowcommand.

The Display Flow command lists Critical Path Monitoring job streams defined toCA-Scheduler.


The batch utility to use is CAJUCMD0. The batch command is DISPLAY FLOW.

4-88 Online Guide

4.3 Commands

4.3.7.10 Display VRM Command

Option A of the CA-Scheduler Display Commands menu displays the Display VRMcommand dialog.

The Display VRM command lists the virtual resources known to CA-Scheduler, alongwith any jobs that currently have or are waiting for those resources.

The batch utility to use is CAJUCMD0. The batch command is DISPLAY VRM.

� �------------------- CA-SCHEDULER 9.� xxyy (SCHD) DISPLAY VRM ------------------

COMMAND ===>

Resource:

Name . . . . . (Resource name or mask)

Enter END to exit.

� �

The field is:

NameThe name of the virtual resource to be displayed, or a mask to limit the virtualresources being displayed. Wildcard characters * and ? may be used.

Size/Type: 1 to 30 numeric charactersRequired: NoBatch Keyword: ResourceDefault: * (All virtual resources will be displayed)


4.3 Commands

4.3.8 Force Command

Use option F1 of the CA-Scheduler Commands menu to display the Force Commandmenu.

The Force command causes schedules and jobs to start immediately, even ifpredecessors are still outstanding.

� � ---------------------- CA-SCHEDULER 9.� xxyy (SCHD) FORCE ---------------------

OPTION ===>

1 JOB - Force a Job to Start

2 SCHEDULE - Force a Schedule to Start

Enter END to exit.

� �

Use option 1, JOB, to force the start of a job. See the next topic for more information.

Use option 2, SCHEDULE, to force the start of a schedule. See 4.3.8.2, “ForceSchedule Command” on page 4-93 for more information.

4-90 Online Guide

4.3 Commands

4.3.8.1 Force Job Command

Option 1 of the CA-Scheduler Force Commands menu displays the Force JobCommand dialog.

The Force Job command causes a job to start regardless of its status. Any predecessorsor early start time requirements are ignored. If the job is a CPU job, the JCL issubmitted to the operating system.

The batch utility to use is CAJUCMD0. The batch command is FORCE JOB.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) FORCE JOB -------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

From Node . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

Job NameThe name of the job that is to be forced.


NumberThe number of the job that is to be forced.


StationThe station of the job that is to be forced.



4.3 Commands

ScheduleThe schedule of the job that is to be forced.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ScheduleDefault: First schedule in the current workload that contains the job

From NodeThe NJE node where the job was originally submitted.






4-92 Online Guide

4.3 Commands

4.3.8.2 Force Schedule Command

Option 2 of the CA-Scheduler Force Commands menu displays the Force ScheduleCommand dialog.

The Force Schedule command causes a schedule to start regardless of its status. Anypredecessors or early start time requirements are ignored.

The batch utility to use is CAJUCMD0. The batch command is FORCE SCHEDULE.

� � ----------------- CA-SCHEDULER 9.� xxyy (SCHD) FORCE SCHEDULE -----------------

COMMAND ===>

Schedule:

Schedule . . . .

From Node . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

ScheduleThe name of the schedule that is to be forced.


From NodeThe NJE node where the schedule is controlled.





4.3 Commands



4-94 Online Guide

4.3 Commands

4.3.9 Globals

Use option G1 of the CA-Scheduler Commands menu to display the Globals dialog.

You can use global variables in schedule and job criteria to prevent submission untilsome task is complete.

The batch utility to use is CAJUCMD0. The batch command is SET GBLxnn where xis A, B, or C, and nn is 01 to 16.

� � --------------------- CA-SCHEDULER 9.� xxyy (SCHD) GLOBALS --------------------

COMMAND ===>

Numeric Values:

GBLA�1 - �4 . . �� . . �� . . �� . . ��

GBLA�5 - �8 . . �� . . �� . . �� . . ��

GBLA�9 - 12 . . �� . . �� . . �� . . ��

GBLA13 - 16 . . �� . . �� . . �� . . ��

Binary Values:

GBLB�1 - �4 . . . . . . . . . . . . . .

GBLB�5 - �8 . . . . . . . . . . . . . .

GBLB�9 - 12 . . . . . . . . . . . . . .

GBLB13 - 16 . . . . . . . . . . . . . .

Character Values:

GBLC�1 - �4 . . . . . . . .

GBLC�5 - �8 . . . . . . . .

GBLC�9 - 12 . . . . . . . .

GBLC13 - 16 . . . . . . . .

Enter END to exit.

� �

The fields are:

GBLA01 - 16Numbers, each in the range of zero to 99,999,999.

Size/Type: 1 to 8 numeric charactersRequired: YesBatch Keyword: GBLA01 - 16

GBLB01 - 16Yes or No.

Size/Type: YES or NORequired: No, but existing values may not be blanked outBatch Keyword: GBLB01 - 16

GBLC01 - 16Character values.

Size/Type: 1 to 8 alphanumeric charactersRequired: No, but existing values may not be blanked outBatch Keyword: GBLC01 - 16


4.3 Commands

4.3.10 Hold Commands

Use option H1 of the CA-Scheduler Commands menu to display the Hold menu.

The Hold commands prevent work from starting that has not yet started.

� � ---------------------- CA-SCHEDULER 9.� xxyy (SCHD) HOLD ----------------------

OPTION ===>

1 JOB - Hold a Job

2 SCHEDULE - Hold a Schedule

3 ALL - Hold all Jobs and Schedules

4 SUBMIT - Turn off submission

Enter END to exit.

� �

Use option 1, JOB, to hold a specific job. See the next topic for more information.

Use option 2, SCHEDULE, to hold a schedule and all of its jobs. See 4.3.10.2, “HoldSchedule Command” on page 4-99 for more information.

Use option 3, ALL, to hold all schedules and jobs. See 4.3.10.3, “Hold All Command”on page 4-100 for more information.

Use option 4, SUBMIT, to turn off all submission. See 4.3.10.4, “Hold SubmitCommand” on page 4-101 for more information.

4-96 Online Guide

4.3 Commands

4.3.10.1 Hold Job Command

Option 1 of the Hold menu displays the Hold Job dialog.

The Hold Job command prevents a specific job from starting. If the job has beensubmitted to OS/390, but has not yet started, it is held in JES.

The batch utility to use is CAJUCMD0. The batch command is HOLD JOB.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) HOLD JOB --------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

From Node . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe name of the job to be held.


NumberThe number of the job to be held.


StationThe station of the job to be held.



4.3 Commands

ScheduleThe schedule of the job to be held.








4-98 Online Guide

4.3 Commands

4.3.10.2 Hold Schedule Command

Option 2 of the Hold menu displays the Hold Schedule dialog.

The Hold Schedule command prevents a schedule from starting, or if it has alreadystarted, any of its jobs that have not yet started from starting. If any of the jobs havebeen submitted to OS/390 but have not yet started, they are held in JES.

The batch utility to use is CAJUCMD0. The batch command is HOLD SCHEDULE.

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) HOLD SCHEDULE -----------------

COMMAND ===>

Schedule:

Schedule Name . .

From Node . . . .

Execute command at:

Route . . . . . .

Route Sysid . . .

Enter END to exit.

� �

The fields are:

ScheduleThe name of the schedule to be held.







4.3 Commands



4.3.10.3 Hold All Command

Option 3 of the Hold menu displays the Hold All dialog.

The Hold All command prevents all schedules and jobs from starting. If any jobs havebeen submitted to OS/390 but have not yet started, they are held in JES.

The batch utility to use is CAJUCMD0. The batch command is HOLD ALL. Thecommand has no keywords.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) HOLD ALL --------------------

COMMAND ===>

Press ENTER to hold all Schedules and Jobs.

Enter END to exit.

� �

The panel has no fields. Press Enter to hold the entire workload. Press PF3 to exitwithout holding the workload.

4-100 Online Guide

4.3 Commands

4.3.10.4 Hold Submit Command

Option 4 of the Hold menu displays the Hold Submit dialog.

The Hold Submit command prevents any jobs from being submitted. Unlike the HoldAll command, the statuses of jobs and schedules are not changed. Also, the HoldSubmit command applies to all work added to the workload (that is, using the RUNcommand or autoscan) after the command is issued.

When a job is ready to be submitted, it is set in a submit fail status with a reason of"submission is held." Once the Release Submit command is issued, all jobs with thissubmit fail status will be submitted.

The Hold Submit condition is carried over restarts of CA-Scheduler.

The batch utility to use is CAJUCMD0. The batch command is HOLD SUBMIT.

Note: Jobs that are ready to be submitted while submission is held are marked asSubmit Failed. If you have messages issued to the console for failures (CAS9CAIJGEN FAILMSG=(OPERxxyy)), CA-Scheduler will issue messages foreach job that cannot be submitted. The Submit Fail code will be 3C60,indicating that submission is held.

� �------------------- CA-SCHEDULER 9.� xxyy (SCHD) HOLD SUBMIT ------------------

COMMAND ===>

Press ENTER to turn off all submission. Any jobs ready to be submitted will

be marked Submit Fail--submission held.

Enter END to exit.

� �

The panel has no fields. Press Enter to hold all submission. Press PF3 to exit withoutholding all submission.


4.3 Commands

4.3.11 Messages Menu

Use option M1 of the CA-Scheduler Commands menu to display the Messages Menu.

� �-------------------- CA-SCHEDULER 9.� xxyy (SCHD) MESSAGES --------------------

OPTION ===>

1 QUERY - Display messages sent to you

2 SEND - Send a CA-Scheduler message

Enter END to exit.

� �

Use option 1, QUERY, to display any messages queued in CA-Scheduler for you. Seethe next topic for more information.

Use option 2, SEND, to store a message in CA-Scheduler for you or for another user.See 4.3.11.2, “Send Messages” on page 4-103 for more information.

4.3.11.1 Query Messages

Option 1 of the Messages Menu displays the Query Message dialog.

Messages are stored in the CA-Scheduler active workload. Messages are deleted oncethey are displayed. Autoscan deletes any messages that have not been displayed andare at least x minutes old. The CAIJGEN MSGHOLD option sets the number ofminutes.

4-102 Online Guide

4.3 Commands

4.3.11.2 Send Messages

Option 2 of the Messages Menu displays the Send Message dialog.

The SENDMSG command stores a message for a user in the active workload. See theQuery Messages dialog (4.3.11.1, “Query Messages” on page 4-102) for informationon displaying messages.

The batch utility to use is CAJUCMD0. The batch command to use is SENDMSG.

� �--------------------- CA-SCHEDULER 9.� xxyy (SCHD) SENDMSG --------------------

COMMAND ===>

Message:

Text . . .

User . . . (ALL for all users)

Number . . (8�� - 899)

Related Job:

Job Name . . .

Job Number . .

Station . . .

Schedule . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

TextThe text of the message.

Size/Type: 1 to 80 alphanumeric charactersRequired: YesBatch Keyword: Text

UserThe user ID to whom this message is being sent.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: User

NumberA number to be associated with this message.

Size/Type: 1 to 3 numeric characters from 800-899Required: NoBatch Keyword: Mno


4.3 Commands

Related JobA job name, number, station, and schedule to be included in the message.

Size/Type: 1 to 8 alphanumeric characters (job name or schedule)or 2 numeric characters (job number or station)

Required: NoBatch Keyword: Job, JNo, STation, Schedule

RouteThe remote NJE node name where the command should be executed.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ROute

Route SysidThe system at the remote NJE multi-CPU node where the command should beexecuted.

Size/Type: 1 to 4 alphanumeric charactersRequired: NoBatch Keyword: SYsid

4-104 Online Guide

4.3 Commands

4.3.12 Post Menu

Use option P1 of the CA-Scheduler Commands Menu to display the Post Menu.

The Post commands satisfy predecessor conditions for waiting schedules and jobs. ThePost command is issued against the predecessor, not the successor schedule or job.

Optionally, a specific successor may have its predecessor condition satisfied, withoutaffecting other successors.

� � ---------------------- CA-SCHEDULER 9.� xxyy (SCHD) POST ----------------------

OPTION ===>

1 JOB - Post a Job

2 SCHEDULE - Post a Schedule

3 SJOB - Post a Job Start

4 SSCHD - Post a Schedule Start

5 DATASET - Post a Dataset Close

6 MVS - Post an Unscheduled Job

7 STEP - Post a Step within a Job

Enter END to exit.

� �

Use option 1, JOB, to satisfy a predecessor of a CA-Scheduler job completing. See thenext topic for more information.

Use option 2, SCHEDULE, to satisfy a predecessor of a schedule completing. See4.3.12.2, “Post Schedule Command” on page 4-109 for more information.

Use option 3, SJOB, to satisfy a predecessor of a CA-Scheduler job starting. See4.3.12.3, “Post Job Start Command” on page 4-111 for more information.

Use option 4, SSCHD, to satisfy a predecessor of a schedule starting. See 4.3.12.4,“Post Schedule Start Command” on page 4-114 for more information.

Use option 5, DATASET, to satisfy a data set predecessor. See 4.3.12.5, “Post DatasetCommand” on page 4-116 for more information.

Use option 6, MVS, to satisfy a predecessor of a non-CA-Scheduler job completing.See 4.3.12.6, “Post Unscheduled Job Command” on page 4-118 for more information.

Use option 7, STEP, to satisfy a predecessor of a specific step within a CA-Schedulerjob. See 4.3.12.7, “Post Job Step Command” on page 4-120 for more information.


4.3 Commands

4.3.12.1 Post Job Command

Option 1 of the CA-Scheduler Post menu displays the Post Job dialog.

The Post Job command satisfies predecessor conditions for jobs and schedules waitingon a specific CA-Scheduler job to successfully complete. The predecessor conditionsare created by criteria of the form:

┌ ┐─-�1── ┌ ┐─4�──────��──jobname─ ──┼ ┼────── ──┼ ┼───────── ──┬ ┬────────── ───────────────�� └ ┘─-jno─ └ ┘─station─ └ ┘ ─schedule─

Optionally, a specific successor job may have its predecessor satisfied instead of allsuccessors.

The batch utility to use is CAJUCMD0. The batch command is POST JOB.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) POST JOB --------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

From Node . . .


Job Name . . . .

Number . . . . .

Station . . . .

Schedule . . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe job name whose successors are notified that the job has completed normally.


4-106 Online Guide

4.3 Commands

NumberThe number of the job whose successors are notified that the job has completednormally.


StationThe station of the job whose successors are notified that the job has completednormally.


ScheduleThe schedule of the job whose successors are notified that the job has completednormally.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: Schedule

From NodeThe node where the job whose successors are notified was originally submitted.



Job Name


Number



4.3 Commands

Station


Schedule

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ONLYScdDefault: First schedule in the current workload that contains the Post Only job

name





4-108 Online Guide

4.3 Commands

4.3.12.2 Post Schedule Command

Option 2 of the CA-Scheduler Post menu displays the Post Schedule dialog.

The Post Schedule command satisfies predecessor conditions for jobs and scheduleswaiting on a specific schedule to end. The predecessor conditions are created bycriteria of the form:

��──SCD──schedule───────────────────────────────────────────────��


The batch utility to use is CAJUCMD0. The batch command is POST SCD.

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) POST SCHEDULE -----------------

COMMAND ===>

Schedule:

Schedule Name . .

From Node . . . .


Job Name . . . .

Number . . . . .

Station . . . . .

Schedule . . . .

Execute command at:

Route . . . . . .

Route Sysid . . .

Enter END to exit.

� �

The fields are:

ScheduleThe schedule whose successors are notified that it has completed normally.


From NodeThe node where the schedule whose successors are notified is controlled.



4.3 Commands


Job Name


Number


Station


Schedule


name





4-110 Online Guide

4.3 Commands

4.3.12.3 Post Job Start Command

Option 3 of the CA-Scheduler Post menu displays the Post Job Start dialog.

The Post Job start command satisfies predecessor conditions for jobs and scheduleswaiting on a specific CA-Scheduler job to start. The predecessor conditions are createdby criteria of the form:

┌ ┐─-�1── ┌ ┐─4�──────��──START──jobname─ ──┼ ┼────── ──┼ ┼───────── ──┬ ┬────────── ────────�� └ ┘─-jno─ └ ┘─station─ └ ┘ ─schedule─


The batch utility to use is CAJUCMD0. The batch command is POST SJOB.

� � ----------------- CA-SCHEDULER 9.� xxyy (SCHD) POST JOB START -----------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

From Node . . .


Job Name . . . .

Number . . . . .

Station . . . .

Schedule . . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe job name whose successors are notified that the job has started.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: Name


4.3 Commands

NumberThe number of the job whose successors are notified that the job has started.


StationThe station of the job whose successors are notified that the job has started.


ScheduleThe schedule of the job whose successors are notified that the job has started.

Size/Type: 1 to 8 alphanumeric charactersRequired: Yes if CAIJGEN SECURTY=YES or EXTERNALBatch Keyword: Schedule




Job Name


Number


4-112 Online Guide

4.3 Commands

Station


Schedule


name






4.3 Commands

4.3.12.4 Post Schedule Start Command

Option 4 of the CA-Scheduler Post menu displays the Post Schedule Start dialog.

The Post Schedule start command satisfies predecessor conditions for jobs andschedules waiting on a specific schedule to start. The predecessor conditions arecreated by criteria of the form:

��──START SCD──schedule─────────────────────────────────────────��


The batch utility to use is CAJUCMD0. The batch command is POST SSCD.

� � --------------- CA-SCHEDULER 9.� xxyy (SCHD) POST SCHEDULE START --------------

COMMAND ===>

Schedule:

Schedule Name . .

From Node . . . .


Job Name . . . .

Number . . . . .

Station . . . . .

Schedule . . . .

Execute command at:

Route . . . . . .

Route Sysid . . .

Enter END to exit.

� �

The fields are:

ScheduleThe schedule whose successors are notified that it has started.




4-114 Online Guide

4.3 Commands


Job Name


Number


Station


Schedule


name






4.3 Commands

4.3.12.5 Post Dataset Command

Option 5 of the CA-Scheduler Post menu displays the Post Dataset dialog.

The Post Dataset command satisfies predecessor conditions for jobs and scheduleswaiting on a data set to be updated. The predecessor conditions are created by criteriaof the form:

��──DSN datasetname─────────────────────────────────────────────��


The batch utility to use is CAJUCMD0. The batch command is POST DSN.

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) POST DATASET ------------------

COMMAND ===>

Dataset:

Dataset Name . .


Job Name . . . .

Number . . . . .

Station . . . .

Schedule . . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

DatasetThe data set name whose successors are notified that it has been updated.



4-116 Online Guide

4.3 Commands

Job Name


Number


Station


Schedule


name






4.3 Commands

4.3.12.6 Post Unscheduled Job Command

Option 6 of the CA-Scheduler Post menu displays the Post MVS dialog.

The Post MVS command satisfies predecessor conditions for jobs and scheduleswaiting on a non-CA-Scheduler job to successfully complete. The predecessorconditions are created by criteria of the form:

��──MVS jobname─────────────────────────────────────────────────��


The batch utility to use is CAJUCMD0. The batch command is POST MVS.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) POST $MVS -------------------

COMMAND ===>

Unscheduled Job:

Job Name . . . .


Job Name . . . .

Number . . . . .

Station . . . .

Schedule . . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe name of the job not controlled by CA-Scheduler whose successors arenotified that it has completed.



4-118 Online Guide

4.3 Commands

Job Name


Number


Station


Schedule


name






4.3 Commands

4.3.12.7 Post Job Step Command

Option 7 of the CA-Scheduler Post menu displays the Post Job Step dialog.

The Post Job Step command satisfies predecessor conditions for jobs and scheduleswaiting on a specific step within a CA-Scheduler job to successfully complete. Thepredecessor conditions are created by criteria of the form:

��──jobname─ ──┬ ┬─────────── ─.stepname────────────────────────────� └ ┘ ─.procstep─

┌ ┐─-�1── ┌ ┐─4�──────�─ ──┬ ┬───────────────────────── ──┼ ┼────── ──┼ ┼───────── ───────────�

└ ┘ ─.CC.──failoper.failcode─ └ ┘─-jno─ └ ┘─station─

�─ ──┬ ┬────────── ────────────────────────────────────────────────�� └ ┘ ─schedule─


The batch utility to use is CAJUCMD0. The batch command is POST STEP.

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) POST JOB STEP -----------------

COMMAND ===>

Job:

Job Name . . . .

Proc Step . . . Step Name . .

Fail Oper . . . Fail Code . . (�-4�95, 99999)

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

From Node . . .


Job Name . . . .

Number . . . . .

Station . . . .

Schedule . . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe job name with the step whose successors are notified that the job hascompleted normally.


4-120 Online Guide

4.3 Commands

Proc StepThe step name outside of the PROC used to identify the specific step whosesuccessors are notified.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: PROC

Step NameThe step name (with the EXEC PGM= on it) whose successors are notified.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: STEP

Fail OperA Boolean operator that must match the value in the successor schedule's or job'scriteria. Valid values are blank, GE (Greater than or Equal), GT (Greater Than),EQ (EQual), NE (Not Equal), LT (Less Than), and LE (Less than or Equal).

Size/Type: 2 alphanumeric charactersRequired: NoBatch Keyword: FAILOper

Fail CodeA number that must match the value in the successor schedule's or job's criteria.

If 99999 is entered, then all successors of this step, regardless of their criteria'sFail Oper and Fail Code values, are notified.

Size/Type: 1 to 5 numeric characters from 0 to 4095 or 99999Required: NoBatch Keyword: Failcode

NumberThe number of the job with the step whose successors are notified that the job hascompleted normally.


StationThe station of the job with the step whose successors are notified that the job hascompleted normally.



4.3 Commands

ScheduleThe schedule of the job with the step whose successors are notified that the jobhas completed normally.


From NodeThe node where the job with the step whose successors are notified was originallysubmitted.



Job Name


Number


Station


Schedule


name

4-122 Online Guide

4.3 Commands






4.3 Commands

4.3.13 Purge Commands

Use option P2 of the CA-Scheduler Commands menu to display the Purge menu.

The Purge commands remove canceled and completed work from the status displays.

� � ---------------------- CA-SCHEDULER 9.� xxyy (SCHD) PURGE ---------------------

OPTION ===>

1 JOB - Purge a Job

2 SCHEDULE - Purge a Schedule

3 ALL - Purge All Ended Jobs and Schedules

Enter END to exit.

� �

Use option 1, JOB, to purge a specific job. See the next topic for more information.

Use option 2, SCHEDULE, to purge a schedule and all of its jobs. See 4.3.13.2,“Purge Schedule” on page 4-127 for more information.

Use option 3, ALL, to purge all completed and canceled schedules and their jobs. See4.3.13.3, “Purge All” on page 4-128 for more information.

4-124 Online Guide

4.3 Commands

4.3.13.1 Purge Job Command

Option 1 of the Purge menu displays the Purge Job dialog.

The Purge Job command removes a specific job from the status display. The job mustbe either in completed, purged, or canceled status.

The batch utility to use is CAJUCMD0. The batch command is PURGE JOB.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) PURGE JOB -------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

From Node . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe name of the job to purge.


NumberThe number of the job to purge.


StationThe station of the job to purge.



4.3 Commands

ScheduleThe schedule of the job to purge.








4-126 Online Guide

4.3 Commands

4.3.13.2 Purge Schedule

Option 2 of the Purge menu displays the Purge Schedule dialog.

The Purge Schedule command removes a schedule and all of its jobs from the statusdisplays. The schedule must be in an ended or canceled status.

The batch utility to use is CAJUCMD0. The batch command is PURGE SCHEDULE.

� � ----------------- CA-SCHEDULER 9.� xxyy (SCHD) PURGE SCHEDULE -----------------

COMMAND ===>

Schedule:

Schedule Name . .

From Node . . . .

Execute command at:

Route . . . . . .

Route Sysid . . .

Enter END to exit.

� �

The fields are:

ScheduleThe name of the schedule to be purged.







4.3 Commands



4.3.13.3 Purge All

Option 3 of the Purge menu displays the Purge All dialog.

The Purge All command removes all completed and canceled schedules from the statusdisplays, along with all jobs belonging to those schedules. Completed and canceledjobs in schedules that are still active are not removed.

The batch utility to use is CAJUCMD0. The batch command is PURGE ALL. Thecommand has no keywords.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) PURGE ALL -------------------

COMMAND ===>

Press ENTER to purge all ended Schedules.

Enter END to exit.

� �

The panel has no fields. Press Enter to purge all ended and canceled schedules. PressPF3 to exit without purging all ended and canceled schedules.

4-128 Online Guide

4.3 Commands

4.3.14 Release Commands

Use option R1 of the CA-Scheduler Commands menu to display the Release menu.

The Release commands allow work previously held with the Hold commands to start.

� �--------------------- CA-SCHEDULER 9.� xxyy (SCHD) RELEASE --------------------

OPTION ===>

1 JOB - Release a Job

2 SCHEDULE - Release a Schedule

3 ALL - Release all Jobs and Schedules

4 AUTO - Release work held by RHOLD=YES

5 USER - Release all work held by you

6 USERALL - Release all work held by all users

7 SUBMIT - Turn on submission after a HOLD SUBMIT command

Enter END to exit.

� �

Use option 1, JOB, to release a specific job. See the next topic for more information.

Use option 2, SCHEDULE, to release a schedule and all of its jobs. See 4.3.14.2,“Release Schedule Command” on page 4-132 for more information.

Use option 3, ALL, to release all schedules and jobs. See 4.3.14.3, “Release AllCommand” on page 4-133 for more information.

Use option 4, AUTO, to release all schedules and jobs after a restart of theCA-Scheduler started task. This only applies if the RHOLD=YES startup option isused. See 4.3.14.4, “Release Auto Command” on page 4-134 for more information.

Use option 5, USER, to release all jobs held by you. See 4.3.14.5, “Release UserCommand” on page 4-135 for more information.

Use option 6, USERALL, to release all jobs held by all users. See 4.3.14.6, “ReleaseUserall Command” on page 4-136 for more information.

Use option 7, SUBMIT, to turn submission back on (reverse the effect of HOLDSUBMIT). See 4.3.14.7, “Release Submit Command” on page 4-137 for moreinformation.


4.3 Commands

4.3.14.1 Release Job Command

Option 1 of the Release menu displays the Release Job dialog.

The Release Job command allows a specific job that has been held by the Hold Jobcommand to start. If the job is currently held in JES, it is released.

The batch utility to use is CAJUCMD0. The batch command is RELEASE JOB.

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) RELEASE JOB ------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

From Node . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe name of the job to be released.


NumberThe number of the job to be released.


StationThe station of the job to be released.


4-130 Online Guide

4.3 Commands

ScheduleThe schedule of the job to be released.









4.3 Commands

4.3.14.2 Release Schedule Command

Option 2 of the Release menu displays the Release Schedule dialog.

The Release Schedule command allows a schedule that was previously held with theHold Schedule command to start. All held jobs in the schedule are also allowed tostart. If any of the jobs are held in JES, they are released.

The batch utility to use is CAJUCMD0. The batch command is RELEASESCHEDULE.

� � ---------------- CA-SCHEDULER 9.� xxyy (SCHD) RELEASE SCHEDULE ----------------

COMMAND ===>

Schedule:

Schedule Name . .

From Node . . . .

Execute command at:

Route . . . . . .

Route Sysid . . .

Enter END to exit.

� �

The fields are:

ScheduleThe name of the schedule to be released.




4-132 Online Guide

4.3 Commands





4.3.14.3 Release All Command

Option 3 of the Release menu displays the Release All dialog.

The Release All command allows all schedules and jobs held by the Hold commandsto start. Any jobs held in JES are released.

The batch utility to use is CAJUCMD0. The batch command is RELEASE ALL. Thecommand has no keywords.

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) RELEASE ALL ------------------

COMMAND ===>

Press ENTER to release all Schedules and Jobs.

Enter END to exit.

� �

The panel has no fields. Press Enter to release the entire workload. Press PF3 to exitwithout releasing the workload.


4.3 Commands

4.3.14.4 Release Auto Command

Option 4 of the Release menu displays the Release Auto dialog.

The Release Auto command releases all schedules and jobs held by the RHOLD=YESstartup option of CA-Scheduler. You should not issue the command until afterCA-Scheduler issues the message CACM151 (RECOVERY COMPLETED.'RELEASE AUTO' MAY BE ISSUED).

The batch utility to use is CAJUCMD0. The batch command is RELEASE AUTO.The command has no keywords.

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) RELEASE AUTO ------------------

COMMAND ===>

Press ENTER to release all Schedules and Jobs held during CA-Scheduler

start-up.

Enter END to exit.

� �

The panel has no fields. Press Enter to release the entire workload. Press PF3 to exitwithout releasing the entire workload.

4-134 Online Guide

4.3 Commands

4.3.14.5 Release User Command

Option 5 of the Release menu displays the Release User dialog.

The Release User command allows all schedules and jobs previously held by you (bythe same user that issues the Release User command) to start. Jobs that are held in JESare released.

The batch utility to use is CAJUCMD0. The batch command is RELEASE USER.

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) RELEASE USER ------------------

COMMAND ===>

Press ENTER to release all Schedules and Jobs held by you.

Enter END to exit.

� �

The panel has no fields. Press Enter to release all schedules and jobs previously heldby you. Press PF3 to exit without releasing anything.


4.3 Commands

4.3.14.6 Release Userall Command

Option 6 of the Release menu displays the Release Userall.

The Release Userall command allows all schedules and jobs previously held by anyCA-Scheduler user to start. Jobs held in JES are released.

The batch utility to use is CAJUCMD0. The batch command is RELEASE USERALL.The command has no keywords.

� � ----------------- CA-SCHEDULER 9.� xxyy (SCHD) RELEASE USERALL ----------------

COMMAND ===>

Press ENTER to release all Schedules and Jobs held by any user.

Enter END to exit.

� �

The panel has no fields. Press Enter to release all schedules and jobs held byCA-Scheduler users. Press PF3 to exit without releasing anything.

4-136 Online Guide

4.3 Commands

4.3.14.7 Release Submit Command

Use the RELEASE SUBMIT command to allow jobs to be submitted again. All jobswith a submit fail status of "Submission is held" will automatically be submitted.

The batch utility to use is CAJUCMD0. The batch command is RELEASE SUBMIT.The command has no keywords.

� �----------------- CA-SCHEDULER 9.� xxyy (SCHD) RELEASE SUBMIT -----------------

COMMAND ===>

Press ENTER to turn on submission. All jobs with a status of Submit Fail--

submission held will be considered for submission automatically.

Enter END to exit.

� �

The panel has no fields. Press Enter to resume submission. Press PF3 to exit withoutresuming submission.


4.3 Commands

4.3.15 Request Commands

Use option R2 of the CA-Scheduler Commands menu to display the Request menu.

The Request commands activate work in the current workload that has a criteria ofREQUESTED.

� � --------------------- CA-SCHEDULER 9.� xxyy (SCHD) REQUEST --------------------

OPTION ===>

1 JOB - Request a Job and all Successors

2 SCHEDULE - Request a Schedule and all Successors

Enter END to exit.

� �

Use option 1, JOB, to request a job and its successors. See the next topic for moreinformation.

Use option 2, SCHEDULE, to request a schedule, all of its jobs, and all of theirsuccessors. See 4.3.15.2, “Request Schedule Command” on page 4-140 for moreinformation.

4-138 Online Guide

4.3 Commands

4.3.15.1 Request Job Command

Option 1 of the Request menu displays the Request Job dialog.

The Request Job command activates a job in the current workload that has a criteria ofREQUESTED. It also activates all successors of the job.

The batch utility to use is CAJUCMD0. The batch command is REQUEST JOB.

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) REQUEST JOB ------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe name of the job to be requested.


NumberThe number of the job to be requested.


StationThe station of the job to be requested.



4.3 Commands

ScheduleThe schedule of the job to be requested.






4.3.15.2 Request Schedule Command

Option 2 of the Request menu displays the Request Schedule dialog.

The Request Schedule command activates a schedule in the current workload that hasa criteria of REQUESTED. All of the jobs in the schedule, along with all successors ofthe jobs and the schedule, are also activated.

The batch utility to use is CAJUCMD0. The batch command is REQUESTSCHEDULE.

4-140 Online Guide

4.3 Commands

� � ---------------- CA-SCHEDULER 9.� xxyy (SCHD) REQUEST SCHEDULE ----------------

COMMAND ===>

Schedule:

Schedule Name . .

Execute command at:

Route . . . . . .

Route Sysid . . .

Enter END to exit.

� �

The fields are:

ScheduleThe name of the schedule to be requested.







4.3 Commands

4.3.16 Rerun Job Command

Option R3 of the CA-Scheduler Commands menu displays the Rerun Job dialog.

The Rerun Job command causes a job that has previously failed to be submitted again.If the CA-11 interface is installed, a starting and/or ending step may be specified. Ifthe job has a Library Type of DRIVER, restart parameters are used instead of runparameters.

CA-Scheduler fills in the CA-11 Options section of the Rerun Job dialog with thecurrent CA-11 CMT values for this job if ALL of the following are true:

■ CAIJGEN option CA11 is set to YES.

■ The RERUN command was entered from the job status display (see 4.2, “JobStatus” on page 4-16).

■ CA-11 is active.

■ The job is found in the CA-11 CMT.

If the CA-11 Options section is filled in, then the Rerun Job dialog is displayed evenif the option Command Prompt from status is set to No. (See Chapter 3, “Options.”)

The batch utility to use is CAJUCMD0. The batch command is RERUN JOB.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) RERUN JOB ---------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

From Node . . .

CA-11 Options:

Insert CA-11 RMS . . . . Set CMT to . .

Restart Step . . . . . . Bypass GDG . .

Last Step . . . . . . . . Pseudo . . . .

RMS Condition Code . . . Usage . . . .

Reason for Rerun . . . .

Set last code on step . . To . . . . . .

RMS Parm . .

Execute command at:


Enter END to exit.

� �

4-142 Online Guide

4.3 Commands

The fields are:

Job NameThe name of the job to be rerun.


NumberThe number of the job to be rerun.


StationThe station of the job to be rerun.


ScheduleThe schedule of the job to be rerun.




Insert CA-11 RMSIf YES, CA-Scheduler inserts the CA-11 Run Manager Step (RMS) into the job'sJCL during submission.

Size/Type: YES or NORequired: NoBatch Keyword: INSrrmsDefault: The value of the Insert CA-11 RMS field for this job in the

workload


4.3 Commands

Set CMT toIndicates if the CA-11 Catalog Management Table (CMT) for this job should beset to PRODUCTION or RESTART.

Size/Type: PRODUCTION or RESTARTRequired: NoBatch Keyword: CMT=P or CMT=RDefault: The current setting of the CMT is left unchanged

Restart StepThe first step of the job that should execute. The format is "stepname" or"procstep.stepname", where stepname has the EXEC PGM= on it.

Size/Type: 1 to 17 alphanumeric charactersRequired: NoBatch Keyword: REStstepDefault: The step set in the CMT for restart, if the CA-11 AUTOS option is

set to YES

Bypass GDGIf YES, certain CA-11 restrictions on changing JCL are relaxed. See the CA-11documentation for more information.

Size/Type: YES or NORequired: NoBatch Keyword: BYPgdgDefault: NO

Last StepThe last step of the job that should execute. The format is "stepname" or"procstep.stepname", where stepname has the EXEC PGM= on it.

Size/Type: 1 to 17 alphanumeric charactersRequired: NoBatch Keyword: LAStstepDefault: Last step of the job

PseudoIf YES, CA-11 does not perform any processing other than reporting. This optionis useful when first implementing CA-11.

Size/Type: YES or NORequired: NoBatch Keyword: PSEudoDefault: No

RMS Condition CodeThe return code with which the CA-11 RMS should end.

Size/Type: 1 to 4 numeric characters from 0-4095Required: NoBatch Keyword: RMSCcDefault: 0 (zero)

4-144 Online Guide

4.3 Commands

UsageA code that may be used by CA-11 to validate your restart request. Usage maybe required by your CA-11 installation options.

Size/Type: 1 numeric characterRequired: Dependent on CA-11 installation optionsBatch Keyword: USAge

Reason for RerunA text reason for the rerun/restart of this job. It may be required by your CA-11installation options.

Size/Type: 1 to 40 alphanumeric charactersRequired: Dependent on CA-11 installation optionsBatch Keyword: REAson

Set last code on step/ToAllows the previous return code (condition code) on the specified step to bechanged during the restart. See the CA-11 keyword LRTCD for more information.

Size/Type: 1 to 17 alphanumeric characters (stepname or procstep.stepname) and1-4 numeric characters

Required: No. Either both must be specified or both blankBatch Keyword: LRTCDSTP and LRTCDCOD

RMS ParmThe parm field for the RMS. If entered, any values entered for the other CA-11options are ignored, except for the Reason for Rerun field. CA-11 dictates thesyntax.

Size/Type: 1 to 57 alphanumeric charactersRequired: NoBatch Keyword: RMSParms






4.3 Commands

4.3.17 Restage Job Command

Option R4 of the CA-Scheduler Commands menu displays the Restage Job dialog.

The Restage Job command copies the job's JCL into the CA-Scheduler activeworkload. The JCL may then be edited without modifying the original copy. Atsubmission time, the JCL is read from the active workload.

The batch utility to use is CAJUCMD0. The batch command is RESTAGE JOB.

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) RESTAGE JOB ------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe name of the job to be restaged.


NumberThe number of the job to be restaged.


4-146 Online Guide

4.3 Commands

StationThe station of the job to be restaged.


ScheduleThe schedule of the job to be restaged.







4.3 Commands

4.3.18 Run Commands

Use option R5 of the CA-Scheduler Commands menu to display the Run menu.

The Run commands add to the current workload schedules and jobs that are defined toCA-Scheduler.

� � ----------------------- CA-SCHEDULER 9.� xxyy (SCHD) RUN ----------------------

OPTION ===>

1 JOB - Run a Job

2 SCHEDULE - Run a Schedule

Enter END to exit.

� �

Use option 1, JOB, to add a specific job to the workload. See the next topic for moreinformation.

Use option 2, SCHEDULE, to add a schedule and its jobs to the workload. See4.3.18.2, “Run Schedule Command” on page 4-151 for more information.

4-148 Online Guide

4.3 Commands

4.3.18.1 Run Job Command

Option 1 of the Run menu displays the Run Job dialog.

The Run Job command adds a job to the current workload. The job must be defined toCA-Scheduler. If the job's schedule is not in the workload, it is added without anyother jobs.

The batch utility to use is CAJUCMD0. The batch command is RUN JOB.

� � --------------------- CA-SCHEDULER 9.� xxyy (SCHD) RUN JOB --------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

Options:

Hold . . . . . . NO

Execute command at:

Sysid . . . . .

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe name of the job to be run.


NumberThe number of the job to be run.


StationThe station of the job to be run.



4.3 Commands

ScheduleThe schedule of the job to be run.


HoldSpecify YES to add the job to the workload, but prevent it from starting. ARelease command must be issued before the job may start.

Size/Type: YES or NORequired: NoBatch Keyword: HOLDDefault: NO

SysidThe specific CA-Scheduler that should process this command within the localmulti-CPU environment.

Size/Type: 1 to 4 alphanumeric charactersRequired: NoBatch Keyword: SYSidDefault: Current system ID





4-150 Online Guide

4.3 Commands

4.3.18.2 Run Schedule Command

Option 2 of the Run menu displays the Run Schedule dialog.

The Run Schedule command adds a defined schedule to the current workload. Thecriteria for the schedule's jobs are evaluated to determine if the jobs should also beadded to the workload.

The batch utility to use is CAJUCMD0. The batch command is RUN SCHEDULE.

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) RUN SCHEDULE ------------------

COMMAND ===>

Schedule:

Schedule Name . .

Options:

Hold . . . . . . NO

Date . . . . . . (AUTOS, TODAY, mmddyy, ddmmyy)

Execute command at:

Sysid . . . . .

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

ScheduleThe schedule of the job to be run.


HoldSpecify YES to add the schedule to the workload, but prevent it from starting. ARelease command must be issued before the schedule may start.

Size/Type: YES or NORequired: NoBatch Keyword: HOLDDefault: NO


4.3 Commands

DateThe date to use when evaluating the criteria for the schedule's jobs. AUTOSmeans the current autoscan date. TODAY means the current date, which may beone day later than the autoscan date, depending on when autoscan normally runs.

Size/Type: 6 numeric characters, AUTOS, or TODAYRequired: NoBatch Keyword: DateDefault: AUTOS

SysidThe specific CA-Scheduler that should process this command within the localmulti-CPU environment.

Size/Type: 1 to 4 alphanumeric charactersRequired: NoBatch Keyword: SYSidDefault: Current system ID





4-152 Online Guide

4.3 Commands

4.3.19 SREQ Commands

Option S1 of the CA-Scheduler Commands menu displays the SREQ (SelectiveRequest) menu.

The SREQ commands activate schedules and jobs with a criteria of REQUESTED andSOME of their successors.

� � ---------------------- CA-SCHEDULER 9.� xxyy (SCHD) SREQ ----------------------

OPTION ===>

1 JOB - Request a Job and some Successors

2 SCHEDULE - Request a Schedule and some Successors

Enter END to exit.

� �

Use option 1, JOB, to activate a specific job and some of its successors. See the nexttopic for more information.

Use option 2, SCHEDULE, to activate a schedule, its jobs, and some of theirsuccessors. See 4.3.19.2, “SREQ Schedule Command” on page 4-156 for moreinformation.


4.3 Commands

4.3.19.1 SREQ Job Command

Option 1 of the SREQ menu displays the SREQ (Selective Request) Job dialog.

The SREQ Job command activates a job with a criteria of REQUESTED and selectedsuccessors of the job.

Successors are only activated if they do not themselves have criteria of REQUESTEDand do not inherit the REQUESTED attribute from any job other than the one beingSREQed.

The batch utility to use is CAJUCMD0. The batch command is SREQ JOB.

� � -------------- CA-SCHEDULER 9.� xxyy (SCHD) SELECTIVE REQUEST JOB -------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe name of the job to be requested.


NumberThe number of the job to be requested.


4-154 Online Guide

4.3 Commands

StationThe station of the job to be requested.


ScheduleThe schedule of the job to be requested.







4.3 Commands

4.3.19.2 SREQ Schedule Command

Option 2 of the SREQ menu displays the SREQ (Selective Request) Schedule dialog.

The SREQ Schedule command activates a job with a criteria of REQUESTED andselected successors of the schedule.

Successors are only activated if they do not themselves have criteria of REQUESTEDand do not inherit the REQUESTED attribute from any schedule other than the onebeing SREQed.

The batch utility to use is CAJUCMD0. The batch command is SREQ SCHEDULE.

� � ----------- CA-SCHEDULER 9.� xxyy (SCHD) SELECTIVE REQUEST SCHEDULE -----------

COMMAND ===>

Schedule:

Schedule Name . .

Execute command at:

Route . . . . . .

Route Sysid . . .

Enter END to exit.

� �

The fields are:

ScheduleThe name of the schedule to be requested.




4-156 Online Guide

4.3 Commands




4.3 Commands

4.3.20 Start Job Command

Option S2 of the CA-Scheduler Commands menu displays the Start Job dialog.

The Start Job command marks a job as started. It is normally used for non-CPU jobs.

The batch utility to use is CAJUCMD0. The batch command is START JOB.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) START JOB -------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . .

Schedule . . . .

From Node . . .

Options:

CPU Job . . . . NO

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe name of the job to be started.


NumberThe number of the job to be started.


StationThe station of the job to be started.

Size/Type: 1 to 2 numeric characters from 1 to 99Required: NoBatch Keyword: STationDefault: Station number specified in Default Start/Complete Station field in

Chapter 3, “Options”

4-158 Online Guide

4.3 Commands

ScheduleThe schedule of the job to be started.




CPU JobIf a station 40 (CPU) job is being started, then this field must be set to YES.Otherwise, this field must be set to NO.

Size/Type: YES or NORequired: NoBatch Keyword: CPU=Y or CPU=NDefault: NO






4.3 Commands

4.3.21 Submit Job Command

Option S3 of the CA-Scheduler Commands menu displays the Submit Job dialog.

The Submit Job command causes a job that has previously failed to be submittedagain. If the CA-11 interface is installed, a starting and/or ending step may bespecified. If the job has a Library Type of DRIVER, run parameters are used insteadof rerun parameters.

CA-Scheduler fills in the CA-11 Options section of the Submit Job dialog with thecurrent CA-11 CMT values for this job if ALL of the following are true:

■ CAIJGEN option CA11 is set to YES.

■ The SUBMIT command was entered from the job status display (see 4.2, “JobStatus” on page 4-16).

■ CA-11 is active.

■ The job is found in the CA-11 CMT.

If the CA-11 Options section is filled in, the Submit Job dialog displays even if theoption Command Prompt from Status is set to No. (See Chapter 3, “Options.”)

The batch utility to use is CAJUCMD0. The batch command is SUBMIT JOB.

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) SUBMIT JOB ---------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

From Node . . .

CA-11 Options:

Insert CA-11 RMS . . . . Set CMT to . .

Restart Step . . . . . . Bypass GDG . .

Last Step . . . . . . . . Pseudo . . . .

RMS Condition Code . . . Usage . . . .

Reason for Rerun . . . .

Set last code on step . . To . . . . . .

RMS Parm . .

Execute command at:


Enter END to exit.

� �

4-160 Online Guide

4.3 Commands

The fields are:

Job NameThe name of the job to be submitted.


NumberThe number of the job to be submitted.


StationThe station of the job to be submitted.


ScheduleThe schedule of the job to be submitted.




Insert CA-11 RMSIf YES, CA-Scheduler inserts the CA-11 Run Manager Step (RMS) into the job'sJCL during submission.

Size/Type: YES or NORequired: NoBatch Keyword: INSrrmsDefault: The value of the Insert CA-11 RMS field for this job in the

workload


4.3 Commands

Set CMT toIndicates if the CA-11 Catalog Management Table (CMT) for this job should beset to PRODUCTION or RESTART.

Size/Type: PRODUCTION or RESTARTRequired: NoBatch Keyword: CMT=P or CMT=RDefault: The current setting of the CMT is left unchanged

Restart StepThe first step of the job that should execute. The format is "stepname" or"procstep.stepname", where stepname has the EXEC PGM= on it.

Size/Type: 1 to 17 alphanumeric charactersRequired: NoBatch Keyword: REStstepDefault: The step set in the CMT for restart, if the CA-11 AUTOS option is

set to YES

Bypass GDGIf YES, certain CA-11 restrictions on changing JCL are relaxed. See the CA-11documentation for more information.

Size/Type: YES or NORequired: NoBatch Keyword: BYPgdgDefault: NO

Last StepThe last step of the job that should execute. The format is "stepname" or"procstep.stepname", where stepname has the EXEC PGM= on it.

Size/Type: 1 to 17 alphanumeric charactersRequired: NoBatch Keyword: LAStstepDefault: Last step of the job

PseudoIf YES, CA-11 does not perform any processing other than reporting. This optionis useful when first implementing CA-11.

Size/Type: YES or NORequired: NoBatch Keyword: PSEudoDefault: NO

RMS Condition CodeThe return code with which the CA-11 RMS should end.

Size/Type: 1 to 4 numeric characters from 0-4095Required: NoBatch Keyword: RMSCcDefault: 0 (zero)

4-162 Online Guide

4.3 Commands

UsageA code that may be used by CA-11 to validate your restart request. Usage maybe required by your CA-11 installation options.

Size/Type: 1 numeric characterRequired: NoBatch Keyword: USAgeDefault: Dependent on CA-11 installation options

Reason for RerunA text reason for the rerun/restart of this job. It may be required by your CA-11installation options.

Size/Type: 1 to 40 alphanumeric charactersRequired: Dependent on CA-11 installation optionsBatch Keyword: REAson

Set last code on step/ToAllows the previous return code (condition code) on the specified step to bechanged during the restart. See the CA-11 keyword LRTCD for more information.

Size/Type: 1 to 17 alphanumeric characters (stepname or procstep.stepname) and1-4 numeric characters

Required: No. Either both must be specified or both blankBatch Keyword: LRTCDSTP and LRTCDCOD

RMS ParmThe parm field for the RMS. If entered, any values entered for the other CA-11options are ignored, except for the Reason for Rerun field. CA-11 dictates thesyntax.

Size/Type: 1 to 57 alphanumeric charactersRequired: NoBatch Keyword: RMSParms






4.3 Commands

4.3.22 Unpost Commands

Option U1 of the CA-Scheduler Commands menu displays the Unpost menu.

The Unpost commands cause successors to wait on a predecessor job, schedule, step,or data set, even if the predecessor has already completed.

� � --------------------- CA-SCHEDULER 9.� xxyy (SCHD) UNPOST ---------------------

OPTION ===>

1 JOB - Unpost a Job

2 SCHEDULE - Unpost a Schedule

3 SJOB - Unpost a Job Start

4 SSCHD - Unpost a Schedule Start

5 DATASET - Unpost a Dataset Close

6 MVS - Unpost an Unscheduled Job

7 STEP - Unpost a Step within a Job

Enter END to exit.

� �

Use option 1, JOB, to unsatisfy a predecessor of a CA-Scheduler job completing. Seethe next topic for more information.

Use option 2, SCHEDULE, to unsatisfy a predecessor of a schedule completing. See4.3.22.2, “Unpost Schedule Command” on page 4-168 for more information.

Use option 3, SJOB, to unsatisfy a predecessor of a CA-Scheduler job starting. See4.3.22.3, “Unpost Job Start Command” on page 4-170 for more information.

Use option 4, SSCHD, to unsatisfy a predecessor of a schedule starting. See 4.3.22.4,“Unpost Schedule Start Command” on page 4-173 for more information.

Use option 5, DATASET, to unsatisfy a data set predecessor. See 4.3.22.5, “UnpostDataset Command” on page 4-175 for more information.

Use option 6, MVS, to unsatisfy a predecessor of a non-CA-Scheduler job completing.See 4.3.22.6, “Unpost Unscheduled Job” on page 4-177 for more information.

Use option 7, STEP, to unsatisfy a predecessor of a specific step within aCA-Scheduler job. See 4.3.22.7, “Unpost Job Step Command” on page 4-179 for moreinformation.

4-164 Online Guide

4.3 Commands

4.3.22.1 Unpost Job Command

Option 1 of the CA-Scheduler Unpost Menu displays the Unpost Job dialog.

The Unpost Job command unsatisfies predecessor conditions for jobs and scheduleswaiting on a specific CA-Scheduler job to successfully complete. The predecessorconditions are created by criteria of the form:

┌ ┐─-�1── ┌ ┐─4�──────��──jobname─ ──┼ ┼────── ──┼ ┼───────── ──┬ ┬────────── ───────────────�� └ ┘─-jno─ └ ┘─station─ └ ┘ ─schedule─

Optionally, a specific successor job may have its predecessor unsatisfied instead of allsuccessors.

The batch utility to use is CAJUCMD0. The batch command is UNPOST JOB.

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) UNPOST JOB -------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

From Node . . .

Unpost only this Successor:

Job Name . . . .

Number . . . . .

Station . . . .

Schedule . . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

Job NameThe job name whose successors are notified that the job has completed normally.



4.3 Commands

NumberThe number of the job whose successors are notified that the job has completednormally.


StationThe station of the job whose successors are notified that the job has completednormally.


ScheduleThe schedule of the job whose successors are notified that the job has completednormally.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: Schedule



Unpost only this SuccessorIn allowing successors to start, you may allow all successors or identify a specificjob that may start, leaving all others to continue waiting. By leaving the fieldsunder Unpost only this Successor blank, all successors may start. By entering ajob name, only that successor may start.

Job Name


Number


4-166 Online Guide

4.3 Commands

Station


Schedule

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ONLYScdDefault: First schedule in the current workload that contains the Unpost Only

job name






4.3 Commands

4.3.22.2 Unpost Schedule Command

Option 2 of the CA-Scheduler Unpost Menu displays the Unpost Schedule dialog.

The Unpost Schedule command unsatisfies predecessor conditions for jobs andschedules waiting on a specific schedule to end. The predecessor conditions arecreated by criteria of the form:

��──SCD──schedule───────────────────────────────────────────────��


The batch utility to use is CAJUCMD0. The batch command is UNPOST SCD.

� � ----------------- CA-SCHEDULER 9.� xxyy (SCHD) UNPOST SCHEDULE ----------------

COMMAND ===>

Schedule:

Schedule Name . .

From Node . . . .


Job Name . . . .

Number . . . . .

Station . . . . .

Schedule . . . .

Execute command at:

Route . . . . . .

Route Sysid . . .

Enter END to exit.

� �

ScheduleThe schedule whose successors are notified that it has completed normally.




4-168 Online Guide

4.3 Commands


Job Name


Number


Station


Schedule


job name






4.3 Commands

4.3.22.3 Unpost Job Start Command

Option 3 of the CA-Scheduler Unpost Menu displays the Unpost Job Start dialog.

The Unpost Job start command unsatisfies predecessor conditions for jobs andschedules waiting on a specific CA-Scheduler job to start. The predecessor conditionsare created by criteria of the form:

┌ ┐─-�1── ┌ ┐─4�──────��──START──jobname─ ──┼ ┼────── ──┼ ┼───────── ──┬ ┬────────── ────────�� └ ┘─-jno─ └ ┘─station─ └ ┘ ─schedule─


The batch utility to use is CAJUCMD0. The batch command is UNPOST SJOB.

� � ---------------- CA-SCHEDULER 9.� xxyy (SCHD) UNPOST JOB START ----------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

From Node . . .


Job Name . . . .

Number . . . . .

Station . . . .

Schedule . . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:



4-170 Online Guide

4.3 Commands

NumberThe number of the job whose successors are notified that the job has started.


StationThe station of the job whose successors are notified that the job has started.


ScheduleThe schedule of the job whose successors are notified that the job has started.





Job Name


Number



4.3 Commands

Station


Schedule


job name





4-172 Online Guide

4.3 Commands

4.3.22.4 Unpost Schedule Start Command

Option 4 of the CA-Scheduler Unpost Menu displays the Unpost Schedule Start dialog.

The Unpost Schedule start command unsatisfies predecessor conditions for jobs andschedules waiting on a specific schedule to start. The predecessor conditions arecreated by criteria of the form:

��──START SCD──schedule─────────────────────────────────────────��


The batch utility to use is CAJUCMD0. The batch command is UNPOST SSCD.

� � -------------- CA-SCHEDULER 9.� xxyy (SCHD) UNPOST SCHEDULE START -------------

COMMAND ===>

Schedule:

Schedule Name . .

From Node . . . .


Job Name . . . .

Number . . . . .

Station . . . . .

Schedule . . . .

Execute command at:

Route . . . . . .

Route Sysid . . .

Enter END to exit.

� �

The fields are:

ScheduleThe schedule whose successors are notified that it has started.





4.3 Commands


Job Name


Number


Station


Schedule


job name





4-174 Online Guide

4.3 Commands

4.3.22.5 Unpost Dataset Command

Option 5 of the CA-Scheduler Unpost Menu displays the Unpost Dataset dialog.

The Unpost Dataset command unsatisfies predecessor conditions for jobs and scheduleswaiting on a data set to be updated. The predecessor conditions are created by criteriaof the form:

��──DSN datasetname─────────────────────────────────────────────��


The batch utility to use is CAJUCMD0. The batch command is UNPOST DSN.

� � ----------------- CA-SCHEDULER 9.� xxyy (SCHD) UNPOST DATASET -----------------

COMMAND ===>

Dataset:

Dataset Name . .


Job Name . . . .

Number . . . . .

Station . . . .

Schedule . . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �

The fields are:

DatasetThe data set name whose successors are notified that it has been updated.




4.3 Commands

Job Name


Number


Station


Schedule


job name





4-176 Online Guide

4.3 Commands

4.3.22.6 Unpost Unscheduled Job

Option 6 of the CA-Scheduler Unpost menu displays the Unpost MVS dialog.

The Unpost MVS command unsatisfies predecessor conditions for jobs and scheduleswaiting on a non-CA-Scheduler job to successfully complete. The predecessorconditions are created by criteria of the form:

��──MVS jobname─────────────────────────────────────────────────��


The batch utility to use is CAJUCMD0. The batch command is UNPOST MVS.

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) UNPOST $MVS ------------------

COMMAND ===>

Unscheduled Job:

Job Name . . . .


Job Name . . . .

Number . . . . .

Station . . . .

Schedule . . . .

Execute command at:

Route . . . . .

Route Sysid . .

Enter END to exit.

� �





4.3 Commands

Job Name


Number


Station


Schedule


job name





4-178 Online Guide

4.3 Commands

4.3.22.7 Unpost Job Step Command

Option 7 of the CA-Scheduler Unpost Menu displays the Unpost Job Step dialog.

The Unpost Job Step command unsatisfies predecessor conditions for jobs andschedules waiting on a specific step within a CA-Scheduler job to successfullycomplete. The predecessor conditions are created by criteria of the form:

��──jobname─ ──┬ ┬─────────── ─.stepname────────────────────────────� └ ┘ ─.procstep─

┌ ┐─-�1── ┌ ┐─4�──────�─ ──┬ ┬───────────────────────── ──┼ ┼────── ──┼ ┼───────── ───────────�

└ ┘ ─.CC.──failoper.failcode─ └ ┘─-jno─ └ ┘─station─

�─ ──┬ ┬────────── ────────────────────────────────────────────────�� └ ┘ ─schedule─


The batch utility to use is CAJUCMD0. The batch command is UNPOST STEP.

� � ----------------- CA-SCHEDULER 9.� xxyy (SCHD) UNPOST JOB STEP ----------------

COMMAND ===>

Job:

Job Name . . . .

Proc Step . . . Step Name . .

Fail Oper . . . Fail Code . . (�-4�95, 99999)

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

From Node . . .


Job Name . . . .

Number . . . . .

Station . . . .

Schedule . . . .

Execute command at:


Enter END to exit.

� �

The fields are:

Job NameThe job name with the step whose successors are notified that the job hascompleted normally.



4.3 Commands

Proc StepThe step name outside of the PROC used to identify the specific step whosesuccessors are notified.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: PROC

Step NameThe step name (with the EXEC PGM= on it) whose successors are notified.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: STEP

Fail OperA Boolean operator that must match the value in the successor schedule's or job'scriteria. Valid values are blank, GE (Greater than or Equal), GT (Greater Than),EQ (EQual), NE (Not Equal), LT (Less Than), and LE (Less than or Equal).

Size/Type: 2 alphanumeric charactersRequired: NoBatch Keyword: FAILOper

Fail CodeA number that must match the value in the successor schedule's or job's criteria.

If 99999 is entered, then all successors of this step, regardless of their criteria'sFail Oper and Fail Code values, are notified.

Size/Type: 1 to 5 numeric characters from 0 to 4095 or 99999Required: NoBatch Keyword: Failcode

NumberThe number of the job with the step whose successors are notified that the job hascompleted normally.


StationThe station of the job with the step whose successors are notified that the job hascompleted normally.


4-180 Online Guide

4.3 Commands

ScheduleThe schedule of the job with the step whose successors are notified that the jobhas completed normally.


From NodeThe node where the job with the step whose successors are notified was originallysubmitted.



Job Name


Number


Station


Schedule


job name


4.3 Commands





4-182 Online Guide

4.3 Commands

4.3.23 Vary Commands

Option V1 of the CA-Scheduler Commands menu displays the Vary menu.

The Vary Active and Vary Inactive commands start and stop VTAM sessions betweenCA-Scheduler started tasks. These sessions are only used for NJE. The Vary VRMcommand is used to change the state of a virtual resource.

� � ---------------------- CA-SCHEDULER 9.� xxyy (SCHD) VARY ----------------------

OPTION ===>

1 ACTIVE - Start a CA-Scheduler NJE Session

2 INACTIVE - End a CA-Scheduler NJE Session

3 VRM - Make a virtual resource active or inactive

Enter END to exit.

� �

Use option 1, ACTIVE, to start a VTAM session. See the next topic for moreinformation.

Use option 2, INACTIVE, to stop a VTAM session. See 4.3.23.2, “Vary InactiveCommand” on page 4-185 for more information.

Use option 3, VRM, to make a TYPE=SIMPLE virtual resource active or inactive. See4.3.23.3, “Vary VRM Command” on page 4-186 for more information.


4.3 Commands

4.3.23.1 Vary Active Command

Option 1 of the Vary menu displays the Vary Active dialog. The Vary Activecommand starts a VTAM session for NJE.

The batch utility is CAJUCMD0. The batch command is VARY ACT.

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) VARY ACTIVE ------------------

COMMAND ===>

Node:

ID . . . (Leave blank to start all sessions)

Enter END to exit.

� �

The fields are:

IDThe name of the VTAM session to be started. If ID is left blank, all sessions notcurrently active are started.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: IDDefault: All sessions

4-184 Online Guide

4.3 Commands

4.3.23.2 Vary Inactive Command

Option 2 of the Vary menu displays the Vary Inactive dialog.

The Vary Inactive command stops a VTAM session for NJE.

The batch utility is CAJUCMD0. The batch command is VARY INACT.

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) VARY INACTIVE -----------------

COMMAND ===>

Node:

ID . . . (Leave blank to end all sessions)

Options:

Close . .

Enter END to exit.

� �

The fields are:

IDThe name of the VTAM session to be stopped. If ID is left blank, all sessions arestopped.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: IDDefault: All sessions

CloseIf YES, the local VTAM ACB is closed.

Size/Type: YES or NORequired: NoBatch Keyword: CLOSEDefault: NO


4.3 Commands

4.3.23.3 Vary VRM Command

Option 3 of the Vary menu displays the Vary VRM dialog. The Vary VRM commandmakes a virtual resource ACTIVE or INACTIVE. The virtual resource must be definedas TYPE=SIMPLE.

� �-------------------- CA-SCHEDULER 9.� xxyy (SCHD) VARY VRM --------------------

COMMAND ===>

Resource:

Name . . . . (Resource name)

Status . . . (Active or Inactive)

Enter END to exit.

� �

The fields are:

NameThe name of the virtual resource being made active or inactive. The resource mustbe defined as TYPE=SIMPLE.

Size/Type: 1 to 30 alphanumeric charactersRequired: YesBatch Keyword: Resource

StatusThe desired state of the virtual resource. Valid values are ACTIVE andINACTIVE.

Size/Type: ACTIVE or INACTIVERequired: YesBatch Keyword: Status

4-186 Online Guide

4.4 FREECMD

4.4 FREECMD

Option 4 of the CA-Scheduler Monitor menu displays the Freeform Command dialog.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) COMMANDS --------------------

COMMAND ===>

Enter CA-Scheduler command or number �-9:

===>

�:

1:

2:

3:

4:

5:

6:

7:

8:

9:

Enter END to exit.

� �

You may enter most CA-Scheduler commands at the command prompt. Commandsthat you may not enter include:

FORECAST EXCLUDE ONLY OVERRIDE RONLY SHUTDOWN SIMULATE SYNCHK DCF SYNCHK GROUP


4.4 FREECMD

CA-Scheduler interprets the following commands as Monitor commands instead ofSimulate commands:

HOLD RELEASE REQUEST RERUN RUN

The last 10 unique commands are saved in the fields labeled 0 to 9. You may retrievethe commands by typing the number of the field in the command prompt.

The output of the command is browsed using the ISPF/PDF Browse facility. You mayuse all browse functions.

4-188 Online Guide

Chapter 5. Database

Option 2 of the CA-Scheduler main menu displays the database menu.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) DATABASE --------------------

OPTION ===>

1 SCHEDULES - Maintain Schedule Definitions

2 JOBS - Maintain Job Definitions

3 USER IDS - Maintain Users

4 STATION - Maintain Stations

5 RESOURCES - Maintain Resources

6 CALENDARS - Maintain Calendars

7 DATETABLE - Maintain Date Tables

8 DOCUMENTATION - Maintain Documentation

9 FLOWS - Maintain Flows for Critical Path Manager

A VRM - Maintain Virtual Resource Monitor Definitions

Enter END to exit.

� �

Type the appropriate option number and press Enter.

Use option 1, SCHEDULES, to display and maintain schedules.

Schedules are collections of jobs that are in some way related. Schedules aresometimes called job sets. Every job must belong to a schedule. Before a job can beconsidered to be a part of a given day's workload, the schedule must be in that day'sworkload. See 5.1, “Schedules” on page 5-3 for more information.

Use option 2, JOBS, to display and maintain jobs.

Jobs are specific tasks that CA-Scheduler tracks. Jobs may be JCL submitted to theoperating system, tasks processed by a Unicenter TNG on a non-OS/390 platform, ormanual tasks required either before or after a CPU job. See 5.2, “Jobs” on page 5-26for more information.

Use option 3, USER IDS, to display and maintain user ID definitions.

Chapter 5. Database 5-1

User IDs are people defined to CA-Scheduler at a certain authorization level. User IDsmay or may not be required, depending on the CAIJGEN installation optionSECURTY. See 5.3, “User IDs” on page 5-66 for more information.

Use option 4, STATION, to display and maintain station definitions.

A Station is a place where work is done. Stations are two-digit numbers, from 01 to99. Station 40 is the CPU station. Stations less than 40 are called pre-CPU, andstations after 40 are post-CPU. Stations only need to be defined for simulation andforecast reports. See 5.4, “Stations” on page 5-73 for more information.

Use option 5, RESOURCES, to display and maintain resource definitions.

Resources describe the data center and may contain the number of tape drives and jobinitiators. Resources only need to be defined for simulation and forecast reports. See5.5, “Resources” on page 5-78 for more information.

Use option 6, CALENDARS, to display and maintain calendar definitions.

Calendars provide a very simple and inflexible method of determining when a givenschedule or job should be included in a given day's workload. Date tables are muchmore powerful and flexible and should be used instead of calendars whenever possible.See 5.6, “Calendars” on page 5-93 for more information.

Use option 7, DATETABLE, to display and maintain date table definitions.

Date tables define which days are considered workdays against nonworkdays(nonworkdays and holidays are considered the same). Date tables also define whenprocessing periods (months) begin and end, if not on the first and last day of themonth. Multiple periods may be defined, called accounting periods. A minimum ofthree date tables are required: one for the year just past, the current year, and the nextyear. See 5.7, “Datetables” on page 5-100 for more information.

Use option 8, DOCUMENTATION, to display and maintain documentation.

Documentation is text entered by your site that may or may not be associated with ajob. See 5.8, “Documentation” on page 5-106 for more information.

Use option 9, FLOWS, to display and maintain flows.

A flow identifies the starting and ending job of a job stream to be tracked by theCritical Path Monitor (CPM) system. See 5.9, “Flows” on page 5-110 for moreinformation.

Use option A, VRM, to display and maintain virtual resource information.

Virtual resources can be used to restrict when jobs may be submitted. See 5.10,“Virtual Resources” on page 5-115 for more information.

5-2 Online Guide

5.1 Schedules

5.1 Schedules

Every job in CA-Scheduler must belong to a schedule (sometimes called a job set). Aschedule must be included in a given day's workload before any of the jobs in theschedule are considered for that day.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULES -------------------

OPTION ===>

Schedule . . .

1 DIRECTORY - List of Schedules

2 DISPLAY - View an Existing Schedule

3 ALTER - Alter an Existing Schedule

4 DEFINE - Create a New Schedule

5 DELETE - Remove an Existing Schedule

6 COPY - Copy an Existing Schedule

7 ANALYZE - Verify an Existing Schedule

Enter END to Exit.

� �

Use option 1, DIRECTORY, to display a scrollable list of schedules. You may put apartial schedule name in the Schedule field to limit the display, or leave the field blankto list all schedules. From the list you may Select (display), Edit, Delete, and Copyschedules.

Use option 2, DISPLAY, to view a specific schedule. You must enter the schedule todisplay in the Schedule field.

Use option 3, ALTER, to edit a specific schedule. You must enter the schedule to alterin the Schedule field.

Use option 4, DEFINE, to create a new schedule. You must enter the schedule todefine in the Schedule field.

Use option 5, DELETE, to remove a specific schedule. You must enter the schedule todelete in the Schedule field. If you have requested the Delete Confirmation option (seeChapter 3, “Options”) then a panel is displayed asking you to confirm the deletion.Otherwise, the schedule is deleted immediately.

Use option 6, COPY, to copy a schedule. You must enter the schedule to copy in theSchedule field.

Use option 7, ANALYZE, to review the schedule and its jobs for any logical errors.See 6.1, “Analyze” on page 6-3 for more information.


5.1 Schedules

5.1.1 Directory

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULES ROW 1 TO 19 OF 5�


Schedule AutoSel Jobs Date Time Userid

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

_ $ NO �� USER1�3

_ $$ NO �� 2��2/12/19 15:4�:3� USER1�3

_ $GEMDEMO NO ��3 2��3/�1/21 13:5�:29 USER1�3

_ ABNDTEST NO ��2 2��2/12/�6 15:4�:�9 USER1�3

_ ABTEST NO ��1 USER1�3

_ ASCHD NO �� USER1�3

_ BADSCHD NO ��1 USER1�3

_ BIGSCHD NO ��2 2��2/12/�6 15:55:18 USER1�3

_ BUD1 NO �� USER1�3

_ CA#TEST1 NO ��4 USER1�3

_ CAJ7 NO ��8 2��2/12/1� 15:�2:47 USER1�3

_ CHARLIE NO �� 2��3/�1/17 �9:5�:13 USER2�2

_ CHAS1 NO �� 2��3/�1/17 1�:41:35 USER2�2

_ CHRIS NO ��1 USER3�1

_ CIDAY NO ��1� USER2�2

_ CIDUAL1 NO ��1� USER1�3

_ CIDUAL2 NO ��1� USER1�3

_ DALSCHD1 NO ��1 USER1�3

_ DATASCHD NO ��1 USER1�3

� �

Each schedule is displayed on a single row. The upper right-hand corner of the paneldisplays the current range of rows and the total number of rows. CA-Scheduler onlyreads the first 50 schedules before displaying the list. As you scroll down, more rowsare automatically added until the entire list has been built.

If the schedule has been defined or modified in Version 9.0 or higher, then the dateand time of that change is displayed. Schedules that were last updated prior to Version9.0 show blank date and time.

If the schedule was defined and modified only in batch prior to Version 7.4, the userID field may be blank.

Select a schedule by entering a letter to the left of the schedule. Enter:

S to select a schedule for viewingE to edit (alter) a scheduleC to copy this schedule to a new nameD to delete the scheduleA to analyze the schedule and its jobsJ to display a list of jobs in this schedule

5-4 Online Guide

5.1 Schedules

5.1.2 Schedule Options

The same panels are used to display, edit, and define schedules.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULE --------------------

OPTION ===>

Schedule . . .

1 DEFINITION - Schedule Definition

2 CRITERIA - Schedule Selection and Predecessors

Enter END to exit.

� �

Use option 1, DEFINITION, to view or edit the schedule definition. See the next topicfor more information.

Use option 2, CRITERIA, to edit or browse the schedule's criteria. See 5.1.2.2,“Schedule Criteria” on page 5-24 for more information.


5.1 Schedules

5.1.2.1 Schedule Definition

The schedule definition information is contained on several panels. Use PF7 and PF8to scroll up and down through the panels. To save your changes and exit, use PF3. Toexit without saving your changes, enter CAN on the command line.

The batch utility to use for maintaining schedules is CAJUTIL0. The batch commandsfor maintaining schedules are:

The "Sxx" above varies from panel to panel below.

� �------------------ CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULE BASE -----------------

COMMAND ===>

Name . . .

Scheduling:

Auto Selection . . NO Skip . . . . . ��

Backlog . . . . . YES Date Table . .

Execution:

Execution Node . . . .

Execution Sysid . . . .

Job Defaults:

Library Type . . . JCL DDname . . . .

Insert CA-11 . . . JES Class . . . . A

Stage JCL . . . . JES Priority . . .

Ins Sched Enviro . Sched Enviro . . .


� �

The batch command object for this panel is SBR.

You may jump to this panel from other schedule detail panels by using one of thefollowing jump commands:

TOP SBR BASE

Alter (Edit) ALTER Sxx

Copy N/A

Define DEFINE Sxx

Delete DELETE SCHEDULE

Display (view) LIST SCHEDULE

5-6 Online Guide

5.1 Schedules

The fields are:

NameThe name of the schedule being manipulated. This field may not be modified.


Auto SelectionDetermines if the schedule, and all of its jobs, should be considered duringautoscan for inclusion in the current day's workload.

Size/Type: NO or YESRequired: YesBatch Keyword: AUtoselDefault: NO

SkipA number that completes the following sentence: This schedule should beexcluded from the current workload the next n number of times that it would havenormally been selected. Skip is used only if Auto Selection is set to Yes.

Size/Type: 1 to 3 numeric from 0 to 999Required: YesBatch Keyword: SKIPDefault: 0

BacklogBacklog determines what CA-Scheduler should do if the schedule has notcompleted by the next autoscan, and the schedule should be in the next day'sworkload.

YESAllows the old schedule to complete before the new schedule is brought in.

NOCauses the remaining jobs in the schedule to be canceled, and the newschedule is brought in.

Required: YesBatch Keyword: BacklogDefault: YES

Date TableThe name of an alternate date table to use in resolving the schedule's criteria. Thisdate table is also used to resolve all of the criteria for this schedule's jobs. Adefault date table is defined in CAIJGEN.

Size/Type: 1 to 7 alphanumeric charactersRequired: NoBatch Keyword: DAtetablDefault: The value in CAIJGEN DATETAB


5.1 Schedules

Execution NodeIn a JES NJE environment, this is the default JES node where the jobs in thisschedule will execute. If left blank, the default is the local JES node. Individualjobs in this schedule may override this default.

A value of *REMOTE indicates that the jobs in this schedule are not OS/390 jobsbut run on a non-OS/390 platform controlled by Unicenter TNG.

Note: Values other than *REMOTE are ignored if the CAIJGEN option NJE isset to NO or if NJE is set to YES but NJESUB is set to NO.

Size/Type: 1 to 8 alphanumeric characters (value must be defined throughCAIJNET)

Required: NoBatch Keyword: NOdeDefault: Local JES node

Execution SysidIn a JES NJE environment, this is the default JES sysid at the JES node inExecution Node where the jobs in this schedule will run. Individual jobs in thisschedule may override this default.

Size/Type: 1 to 4 alphanumeric charactersRequired: NoBatch Keyword: NODESys

Library TypeThe default access method to use in retrieving JCL for jobs in this schedule.Individual jobs may override this default.

A default access method is specified on the CAIJGEN option LIBTYPE.

Valid values are:

DRIVERCA-Scheduler generates one line of JCL for Driver to expand.

JOBDOCCA-Jobdoc

LIBRNCA-Librarian

PANVCA-Panvalet

PDSPartitioned data set

RDRQJobs are manually submitted outside of CA-Scheduler with aTYPRUN=HOLD on the job statement. CA-Scheduler releases the job andtracks it as if the job was submitted by CA-Scheduler. See "PerformanceConsiderations" in the Systems Programmer Guide for performanceimplications.

5-8 Online Guide

5.1 Schedules

USERLIBThe access method is provided by a site-written exit program. See "User Exitsand APIs" in the Systems Programmer Guide for more information.

TESTLIBCA-Scheduler submits a dummy job (based on the skeleton in memberCAJUTSTB of the PDS allocated to ddname JCLMASTR). The dummy jobmay execute for a specified number of seconds, end with a specific returncode, or abend, based on parameters defined at the job level. See the fieldTest Parm on page 5-38.

ROSCOECA-Roscoe

Required: NoBatch Keyword: LibtypeDefault: Value on CAIJGEN LIBTYPE

JCL DDnameFor Library Type of PDS, the default ddname of the partitioned data setcontaining the JCL of the jobs in this schedule. Individual jobs may override thisvalue.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: DDnameDefault: JCLMASTR

Insert CA-11If Yes, all of the CPU jobs in this schedule are submitted with the CA-11 RMSstep inserted. Individual jobs may override this value.

Note: This option is ignored if the CAIJGEN option CA11 is set to NO.

Size/Type: YES or NORequired: NoBatch Keyword: INSrrmsDefault: Value of CAIJGEN option INSRRMS

JES ClassA default JES class for all of the jobs in this schedule. Individual jobs mayoverride this value.

Note: This value is used only for simulation.



5.1 Schedules

Stage JCLIf YES, CPU jobs in this schedule have their JCL written to the CA-Scheduleractive workload when the schedule starts. When the jobs are submitted to JES, theJCL is read from the active workload. This allows operators to modify the JCLprior to the job being submitted. Individual jobs may override this value.

Note: This value is ignored if CAIJGEN option STAGE is set to NO.

Size/Type: YES or NORequired: NoBatch Keyword: STAGeDefault: NO

JES PriorityA default JES priority for all of the jobs in this schedule. Individual jobs mayoverride this value.

Note: This value is used only for simulation.

Size/Type: 1 to 2 numeric characters from 1 to 15Required: NoBatch Keyword: PRTy

Ins Sched EnviroControls the automatic insertion of a Workload Manager scheduling environmentname in the jobs that belong to this schedule. If not specified, the insert option istaken from the global options (CAS9 CAIJGEN). The scheduling environment tobe inserted into the JCL is taken from the Scheduling Environment field below, orfrom the global options if blank, and may be overridden on the job definition.

Size/Type: YES, NO, or blankRequired: NoBatch Keyword: INSRSenvDefault: Blank (use global option)

Sched EnviroThe name of a Workload Manager scheduling environment that should be insertedinto the JCL of jobs that belong to this schedule. The value is only inserted if theInsert Sched Enviro field above is YES (or defaults to YES). If the SchedulingEnvironment is blank, the global option (CAS9 CAIJGEN) value is used.

Size/Type: 1- to 16-alphanumeric charactersRequired: NoBatch Keyword: SCHENVDefault: Blank (use global option)


5-10 Online Guide

5.1 Schedules

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULE BASE -----------------

COMMAND ===>

Name . . .

Times:

Early Start . . . . . ��

Must Start . . . . . ��

Must End . . . . . . ��

Maximum Execution . . ��

Average Time . . . . ��

Other:

Continue on bad jobs . . NO

Schedule Priority . . . . ��

Use Simulation Time . . . NO

Internal Security:

Userids . . . . . . . . . . . .

Userids . . . . . . . . . . . .


� �

The batch command object for this panel is SBR.


TIMes

The fields are:

Early StartThe earliest time that this schedule can start after being added to the workload.Individual jobs may have a later early start time, but may not start before theschedule starts.

The value is in the format of ddhhmm, where dd is the number of autoscans thatthe schedule should wait, and hhmm is the time to start. You do not need to enterleading zeros.

Note: This is the earliest that the schedule may start. If it has predecessors thatare still unresolved, the schedule may start after this time.

Size/Type: 1 to 6 numeric characters in ddhhmm formatRequired: NoBatch Keyword: ErlytimeDefault: 0 (Start as soon as added to the workload)


5.1 Schedules

Must Start| If the schedule has not started by this time, it is considered late. A message may| be sent to the console, the MAILBOX report, and/or a user.



Must End| If the schedule is not ended by this time it is considered late. A message may be| sent to the console, the MAILBOX report, and/or a user.


Size/Type: 1 to 6 numeric characters in ddhhmm formatRequired: NoBatch Keyword: DEadlineDefault: 0 (Never considered late)

Maximum ExecutionIf the schedule takes longer than this time to complete (once it has started), then it

| is considered late. A message may be sent to the console, the MAILBOX report,| and/or a user.



Average TimeAn estimate of the duration of the schedule. This value is used only in simulationif the schedule has never been executed.


Size/Type: 1 to 6 numeric characters in ddhhmm formatRequired: NoBatch Keyword: AVgtimeDefault: 0

5-12 Online Guide

5.1 Schedules

Continue on bad jobsEnter YES if the schedule's successors should be allowed to run even if theschedule is not complete due to one or more failed or abended jobs. If this field isYES, the schedule's successors will be posted if one of the following is true forevery job in this schedule:

1. The job completed normally

2. The COMPLETE command was issued for the job

3. The job failed and has FAILED=CONT

4. The job abended and has ABEND=CONT

Size/Type: YES|NORequired: NoBatch Keyword: CONTinueDefault: NO

Schedule Priority| A number from 1 to 99, where 01 is the higher priority, that controls the order of

internal control blocks. CA-Scheduler searches these control blocks to find work.A value of zero indicates that the default schedule priority, from the CAIJGENSPRTY value, is to be used. A zero value is displayed on batch reports as blanks.

Size/Type: 1 to 2 numeric characters from 1 to 99Required: NoBatch Keyword: SPrtyDefault: 0 - the value on CAIJGEN option SPRTY

Use Simulation TimeIf YES, the start time as calculated by simulation overrides the early start timeentered above.

Size/Type: NO or YESRequired: NoBatch Keyword: USESimDefault: NO

UseridsUsed by CA-Scheduler internal security. If entered, and a user of type general orsupervisor accesses this schedule, then the user's ID must be in the list. If the listis blank, or the user is type manager, then access is allowed.

Size/Type: 1 to 8 alphanumeric character user ID may be specified from zero toeight times

Required: NoBatch Keyword: Userids=(value,value,..)



5.1 Schedules

� � ---------------- CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULE SECURITY ---------------

COMMAND ===>

Name . . .

External Security:

User id . . .

Group id . .


� �

The batch command object for this panel is SSI.


SSI SECurity

The fields are:

User IDThe user ID to be associated with jobs in this schedule when they are submitted toJES. Individual jobs may override this value.

Note: The user ID in the submitted job is determined by the order of theCAIJGEN option SUBUID. The value JSI corresponds to this field.

The CAIJGEN option SECURTY must be set to YES, and the CAIJ$SECoption for the specific library type (access method) must be YES before auser ID is inserted into the JCL.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: Userid

Group IDThe group ID to be associated with jobs in this schedule when they are submittedto JES. Individual jobs may override this value.

Note: The group ID in the submitted job is determined by the order of theCAIJGEN option SUBUID. The value JSI corresponds to this field.

The CAIJGEN option SECURTY must be set to YES, and the CAIJ$SECoption for the specific library type (access method) must be YES before agroupid is inserted into the JCL.

5-14 Online Guide

5.1 Schedules

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: Groupid


� � ---------------- CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULE MESSAGES ---------------

COMMAND ===>

Name . . .


All Events . . . . . . . . . . . . . .

Schedule Start . . . . . . . . . . . .

Schedule End . . . . . . . . . . . . .

Schedule Late . . . . . . . . . . . .

Schedule Skipped . . . . . . . . . . .


� �

The batch command object for this panel is SMR.


SMR MESsages MSG

The fields are:

All EventsA list of zero to four user IDs or OPERxxyy values to which messages should besent when the schedule starts, becomes late, and ends. See below for moreinformation.

Size/Type: 1 to 8 alphanumeric character value specified from zero to four timesRequired: NoBatch Keyword: Msg=(value,value,..)


5.1 Schedules

Schedule StartA list of zero to four user IDs or OPERxxyy values to which messages should besent when the schedule starts. See below for more information.

Size/Type: 1 to 8 alphanumeric character value specified from zero to four timesRequired: NoBatch Keyword: Startmsg=(value,value,..)

Schedule EndA list of zero to four user IDs or OPERxxyy values to which messages should besent when the schedule ends. See below for more information.

Size/Type: 1 to 8 alphanumeric character value specified from zero to four timesRequired: NoBatch Keyword: Endmsg=(value,value,..)

Schedule LateA list of zero to four user IDs or OPERxxyy values to which messages should besent when the schedule becomes late. See below for more information.

Size/Type: 1 to 8 alphanumeric character value specified from zero to four timesRequired: NoBatch Keyword: Latemsg=(value,value,..)

Schedule SkippedA list of zero to four user IDs or OPERxxyy values to which messages should besent when the schedule is skipped at autoscan. See below for more information.

Size/Type: 1 to 8 alphanumeric character value specified from zero to four timesRequired: NoBatch Keyword: SKIPmsg=(value,value,..)


| Messages are stored in the database when the value is MAILBOX, and may beretrieved by the REPORT MAILBOX command.


The CAIJGEN options STRMSG, ENDMSG, LATMSG, and SKPMSG specifylocations to which all start, end, and late messages should be sent. Normally theseinclude MAILBOX.

All messages are sent both to the CAIJGEN locations and to the locations enteredhere.


5-16 Online Guide

5.1 Schedules

� � -------------- CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULE REASON CODES -------------

COMMAND ===>

Name . . .

Average Times:

Reasons �1 to �4 . . . . . . . . . . .

Reasons �5 to �8 . . . . . . . . . . .

Reasons �9 to 12 . . . . . . . . . . .

Reasons 13 to 16 . . . . . . . . . . .

Early Start Times:

Reasons �1 to �4 . . . . . . . . . . .

Reasons �5 to �8 . . . . . . . . . . .

Reasons �9 to 12 . . . . . . . . . . .

Reasons 13 to 16 . . . . . . . . . . .


� �

The batch command object for this panel is SRC.


SRC AVErage AVG EARLY ERLY

The fields are:

Average Times, Reasons 01 to 16Allows an override of the user-specified average time based on the selectionreason code. See below for more information. The value is specified as ddhhmm,where dd is the number of autoscans and hhmm is hours and minutes.

Size/Type: 1 to 6 numeric character value in ddhhmm format specified fromzero to sixteen times

Required: NoBatch Keyword: AVGxx where xx is 01 to 16

Early Start Times, Reasons 01 to 16Allows an override of the early start time entered earlier based on the selectionreason code. See below for more information. The value is specified as ddhhmm,where dd is the number of autoscans and hhmm is hours and minutes.


Required: NoBatch Keyword: ERLYxx where xx is 01 to 16


5.1 Schedules

The selection reason code reflects what part of the schedule's criteria was used tojustify its inclusion in the workload. For example, if the criteria reads:

MON OR TUE

then the selection reason code on Monday would be 01 and on Tuesday would be 02.If the criteria was:

(MON OR TUE)

then the selection reason code would be 01 on both days. An "OR" outside ofparentheses changes the selection reason code.



COMMAND ===>

Name . . . A

Must Start Times:

Reasons �1 to �4 . . . . . . . . . . .

Reasons �5 to �8 . . . . . . . . . . .

Reasons �9 to 12 . . . . . . . . . . .

Reasons 13 to 16 . . . . . . . . . . .

Must End Times:

Reasons �1 to �4 . . . . . . . . . . .

Reasons �5 to �8 . . . . . . . . . . .

Reasons �9 to 12 . . . . . . . . . . .

Reasons 13 to 16 . . . . . . . . . . .


� �



MUSTStrt MUSTEnd

5-18 Online Guide

5.1 Schedules

The fields are:

Must Start Times, Reasons 01 to 16Allows an override of the must start time entered earlier based on the selectionreason code. See below for more information. The value is specified as ddhhmm,where dd is the number of autoscans and hhmm is hours and minutes.


Required: NoBatch Keyword: MUSTxx where xx is 01 to 16

Must End Times, Reasons 01 to 16Allows an override of the must complete time entered earlier based on theselection reason code. See below for more information. The value is specified asddhhmm, where dd is the number of autoscans and hhmm is hours and minutes.


Required: NoBatch Keyword: DEADxx where xx is 01 to 16


MON OR TUE


(MON OR TUE)




5.1 Schedules


COMMAND ===>

Name . . . A

Maximum Execution Times:

Reasons �1 to �4 . . . . . . . . . . .

Reasons �5 to �8 . . . . . . . . . . .

Reasons �9 to 12 . . . . . . . . . . .

Reasons 13 to 16 . . . . . . . . . . .


� �



MAX

The fields are:

Maximum Execution, Reasons 01 to 16Allows an override of the maximum execution time entered earlier based on theselection reason code. See below for more information. The value is specified asddhhmm, where dd is the number of autoscans and hhmm is hours and minutes.


Required: NoBatch Keyword: MAXxx where xx is 01 to 16


MON OR TUE


(MON OR TUE)



5-20 Online Guide

5.1 Schedules

� � -------------- CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULE INFORMATION --------------

COMMAND ===>

Name . . . A

Information:

Description . . .

Comment . . . . .

Exit Parm . . . .

Form . . . . . .

Quantity . . . .

Notify . . . . .

Responsibility. .

Verify . . . . . NO

Specification . .


� �

The batch command object for this panel is SIR.


SIR INFO

The fields on this panel are only used for documentation or simulation. The fields are:

DescriptionA description of this job.

Size/Type: 1 to 40 alphanumeric charactersRequired: NoBatch Keyword: Desc

CommentA comment that appears next to the schedule name on some reports.

Size/Type: 1 to 30 alphanumeric charactersRequired: NoBatch Keyword: Comment

Exit ParmA string passed to the simulation exit when this schedule is processed.

Size/Type: 1 to 16 alphanumeric charactersRequired: NoBatch Keyword: EXitparm


5.1 Schedules

FormIdentify a form that is associated with the standard jobs in this schedule.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: Form

QuantityIndicate how much input or output is expected for this schedule.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: Quantity

NotifyName a person or group to be notified in connection with this job or schedule.

Size/Type: 1 to 12 alphanumeric charactersRequired: NoBatch Keyword: NOtify

ResponsibilityName the person or group responsible for this schedule.

Size/Type: 1 to 12 alphanumeric charactersRequired: NoBatch Keyword: Resp

VerifyIndicate whether this schedule requires special verification. This is for reportingpurposes only.

Size/Type: YES or NORequired: NoBatch Keyword: VerifyDefault: NO

SpecificationGive specification data associated with this schedule.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: SPec


5-22 Online Guide

5.1 Schedules

� � -------------- CA-SCHEDULER 9.� xxyy (SCHD) SCHEDULE INFORMATION --------------

COMMAND ===>

Name . . . A

Destinations:

�1 to �4 . . . . . . . . .

�5 to �8 . . . . . . . . .

Deliverables:

�1 to �2 . . . . .

�3 to �4 . . . . .

�5 to �6 . . . . .

�7 to �8 . . . . .


� �

The batch command object for this panel is SIR.


BOTtom


DestinationsGive up to eight destinations for the output from the jobs in this schedule.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: DESTx where x is 1 to 8

DeliverablesGive up to eight delivery specifications for the jobs in this schedule.

Size/Type: 1 to 16 alphanumeric characters specified from zero to eight timesRequired: NoBatch Keyword: DELx where x is 1 to 8


5.1 Schedules

5.1.2.2 Schedule Criteria

If you are displaying a schedule, the criteria is browsed using the ISPF/PDF BROWSEservice. The first line of the criteria displays the calendar name in use, if any.

If you are defining or altering a schedule, the criteria is edited using the ISPF/PDFEDIT service. A NOTE line indicates the calendar name in use, if any. If you need tochange the calendar name, enter CAL xxx on the command line, where xxx is the newcalendar name.

Use PF3 to exit and save any changes. Use CAN to exit without saving any changes.

5.1.3 Batch Examples

5.1.3.1 Example 1

Define a schedule that should be considered for autoscan.

//STEP1 EXEC CAJUTIL�

//SYSIN DD �

DEFINE SBR N=ABC,AUTOSEL=YES

//

5.1.3.2 Example 2

This schedule should be selected only on Mondays and Tuesdays.


//SYSIN DD �

DEFINE SCR N=ABC,CRI='MON OR TUE'

//

5-24 Online Guide

5.1 Schedules

5.1.4 Copying a Schedule

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) COPY SCHEDULE -----------------

OPTION ===>

Copy schedule

to schedule

Enter END to exit.

� �

The schedule you selected from the directory is listed in the Copy schedule field. Enterthe new schedule name in the To schedule field.

All of the schedule is copied, including criteria. After you have copied the schedule,you can alter the new schedule to make any desired changes.


5.2 Jobs

5.2 Jobs

A CA-Scheduler job is a unit of work. Jobs may be CPU tasks, pre-CPU tasks, orpost-CPU tasks. A CPU job has JCL and executes on a JES initiator, or may be acommand that executes on a non-OS/390 system. A pre-CPU job is a manual task thatmust be completed before the CPU job executes, such as making temporary changes tothe job's JCL. A post-CPU job is a manual task that cannot be started until after theCPU job completes, such as printing and delivering reports.

Option 2 of the CA-Scheduler Database menu displays the Jobs menu.

� � ---------------------- CA-SCHEDULER 9.� xxyy (SCHD) JOBS ----------------------

OPTION ===>

Job . . . . .

Job Number. .

Station . . .

Schedule. . .

1 DIRECTORY - List of Jobs

2 DISPLAY - View an Existing Job

3 ALTER - Alter an Existing Job

4 DEFINE - Create a New Job

5 DELETE - Remove an Existing Job

6 COPY - Copy an Existing Job

7 ANALYZE - Verify an Existing Job

8 SYNTAX - Syntax Check JCL for an Existing Job

Enter END to Exit.

� �

Use option 1, DIRECTORY, to display a scrollable list of schedules. You may enter apartial job name in the Job field or a partial schedule name in the Schedule field tolimit the display. The Job Number and Station fields are ignored. From the list youmay Select (display), Edit, Delete, Copy, syntax check JCL, and Analyze jobs.

For options 2 to 8, you must enter the Job, Job Number, Station, and Schedule fields.

Use option 2, DISPLAY, to view a specific job.

Use option 3, ALTER, to edit a specific job.

Use option 4, DEFINE, to create a new job.

Use option 5, DELETE, to remove a specific job. If you have requested the DeleteConfirmation option (see Chapter 3, “Options”), then a panel is displayed asking youto confirm the deletion. Otherwise, the job is deleted immediately.

Use option 6, COPY, to copy a job, creating a new job. All information is copied,including criteria.

5-26 Online Guide

5.2 Jobs

Use option 7, ANALYZE, to review the job for any logical errors. See 6.1, “Analyze”on page 6-3 for more information.

Use option 8, SYNTAX, to inspect the job's JCL for syntax errors.

5.2.1 Directory

� � ---------------------- CA-SCHEDULER 9.� xxyy (SCHD) JOBS -- ROW 1 TO 19 OF 5�


Job JNO Station Schedule Sysid Date Time Userid

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

_ $$ �1 4� $$ 2��3/�4/�9 �8:25:47 USER1�3

_ $GEMJOB1 �1 4� $GEMDEMO USER1�3

_ $GEMJOB2 �1 4� $GEMDEMO USER1�3

_ $GEMRMT �1 4� $GEMDEMO USER1�3

_ $GEMXXX1 88 99 $GEMXXX1 2��3/�2/18 1�:37:29 USERB�1

_ ABEND �1 4� BADSCHD USER3�1

_ ABND�1 �1 4� ABNDTEST USER1�3

_ ABND�2 �1 4� ABNDTEST USER1�3

_ ALL �1 4� XE87 USER1�3

_ ASDF �1 4� TONY USER3�1

_ ASDF1 �1 4� ASDF

_ BACKOUT �1 4� BACKOUT 2��3/�2/27 12:19:39 USER1�3

_ BIGJOB �1 4� BIGSCHD 2��3/�1/22 �9:32:�1 USER3�1

_ BIGJOB2 �1 4� BIGSCHD USER1�3

_ BILLING �1 4� BILLING 2��3/�4/�2 13:39:57 USER1�3

_ CAJ7�1 �1 4� CAJ7 USER1�3

_ CAJ7�2 �1 4� CAJ7 USERD�2

_ CAJ7�3 �1 4� CAJ7 USER1�3

_ CAJ7�4 �1 4� CAJ7 USER1�3

� �

Each job is displayed on a single row. The upper right-hand corner of the paneldisplays the current range of rows and the total number of rows. CA-Scheduler onlyreads the first 50 jobs before displaying the list. As you scroll down, more rows areautomatically added until the entire list has been built.

If the job has been defined or modified in Version 9.0 or higher, then the date andtime of that change is displayed. Jobs that were last updated prior to Version 9.0 showblank date and time.

If the job was defined and modified in batch only prior to Version 7.4, the user IDfield may be blank.


5.2 Jobs

Select a job by entering a letter to the left of the job. Enter:

S to select a job for viewingE to edit (alter) a jobC to copy this job to a new nameD to delete the jobA to analyze the jobX to syntax check the job's JCL

5.2.2 Job Options

The same panels are used to display, edit, and define jobs.

� �----------------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB ----------------------

OPTION ===>

Job . . . . .

Job Number. . �1

Station . . . 4�

Schedule. . .

1 DEFINITION - Job Definition

2 CRITERIA - Job Selection Criteria

3 JOB STEPS - Job Step Definitions

4 DRIVER - Parms for Driver Jobs

5 VRM - Virtual Resources

Enter END to Exit.

� �

Use option 1, DEFINITION, to view or edit the job definition. See the next topic formore information.

Use option 2, CRITERIA, to edit or browse the job's criteria. See 5.2.2.2, “JobCriteria” on page 5-57 for more information.

Use option 3, JOB STEPS, to view or edit step level return codes. See 5.2.2.3, “JobSteps” on page 5-58 for more information.

Use option 4, DRIVER, to view or edit Driver parms for jobs with a Library Type ofDRIVER. See 5.2.2.4, “Driver Parms” on page 5-62 for more information.

Use option 5, VRM, to view or edit virtual resources associated with this job. See5.2.2.5, “Virtual Resources” on page 5-63 for more information.

5-28 Online Guide

5.2 Jobs

5.2.2.1 Job Definition

The job definition information is contained on several panels. Use PF7 and PF8 toscroll up and down through the panels. To save your changes and exit, use PF3. Toexit without saving your changes, enter CAN on the command line.

The batch utility to use for maintaining jobs is CAJUTIL0. The batch commands formaintaining jobs are:

The Jxx above varies from panel to panel below.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB BASE --------------------

COMMAND ===>


Selection:

Backlog . . . . Skip . . . . ��

Times:

Early Start . . . . . ��

Must Start . . . . . ��

Must End . . . . . . ��

Maximum Execution . . ��

Average Time . . . . ��

Miscellaneous:

Internal Priority . . ��


� �

The batch command object for this panel is JBR.

You may jump to this panel from other job definition panels by using one of thefollowing jump commands:

TOP JBR BASE TIMes BACKlog

Alter (Edit) ALTER Jxx

Copy N/A

Define DEFINE Jxx

Delete DELETE JOB

Display (View) LIST JOB


5.2 Jobs

The fields are:

NameThe name of the job being manipulated. This field may not be modified after thejob is defined. For CPU jobs, this name must match the name on the JCL JOBstatement.


NumberThe number of the job being manipulated. Up to 99 separate instances of the jobmay be defined by varying the number from 01 to 99. This field may not bemodified after the job has been defined.


StationThe station of the job being manipulated. The station determines if the job isCPU, pre-CPU, or post-CPU. Station 40 jobs are CPU jobs. Jobs with stations lessthan 40 are pre-CPU, and greater than 40 are post-CPU. Station 39 is reserved forstaged JCL setup. Station 60 is reserved for report printing. All pre-CPU jobsmust be complete before the CPU job may start, and the CPU job must becomplete before the post-CPU jobs may start. This field may not be modified afterthe job has been defined.


ScheduleThe schedule of the job being manipulated. All jobs must belong to a schedule.The schedule must be part of a given day's workload before the job may beconsidered for that workload. The same job name, number, and station may bedefined to multiple schedules so that it may run multiple times on the same day.(This can also be done by varying the Number of the job.) The schedule mustexist before the job may be defined. This field may not be modified after the jobhas been defined.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: Schedule

5-30 Online Guide

5.2 Jobs

BacklogDetermines what action CA-Scheduler should take if the job has not completed bythe next autoscan and the job is scheduled to run again. YES indicates that the jobshould be retained until it (and the rest of its schedule) has completed. NOindicates that the job should be canceled (if not currently executing) and the nextday's copy made available. Blank causes the schedule's Backlog option to be used.

Size/Type: YES/NO/blankRequired: NoBatch Keyword: BacklogDefault: Value of schedule's Backlog field

SkipA number that completes the following sentence: This job should be excludedfrom the current workload the next n number of times that it would have normallybeen selected. Skip is used only if the schedule has Auto Select set to Yes.

Size/Type: 1 to 3 numeric charactersRequired: NoBatch Keyword: SKIPDefault: 0

Early StartThe earliest time this job may start after being added to the workload. The jobmay not start before the schedule starts.


Note: This is the earliest that the job may start. If it has predecessors that arestill unresolved, the job may start after this time.

Size/Type: 1 to 6 numeric characters in ddhhmm formatRequired: NoBatch Keyword: ErlytimeDefault: 0 (Start as soon as added to the workload)

Must Start| If the job has not started by this time, it is considered late. A message may be| sent to the console, the MAILBOX report, and/or a user.

The value is in the format of ddhhmm, where dd is the number of autoscans thatthe job should wait, and hhmm is the time. Leading zeros do not need to beentered.



5.2 Jobs

Must End| If the job is not needed by this time it is considered late. A message may be sent| to the console, the MAILBOX report, and/or a user.


Size/Type: 1 to 6 numeric characters in ddhhmm formatRequired: NoBatch Keyword: DEadlineDefault: 0 (Never considered late)

Maximum ExecutionIf the job takes longer than this time to complete (once it has started), then it is

| considered late. A message may be sent to the console, the MAILBOX report,| and/or a user.



Average TimeAn estimate of the duration of the job. This value is used only in simulation if thejob has never been executed.


Size/Type: 1 to 6 numeric characters in ddhhmm formatRequired: NoBatch Keyword: AVgtimeDefault: 0

Internal Priority| A number from 1 to 99, where 01 is the higher priority, that controls the order of

internal control blocks. CA-Scheduler searches these control blocks, within theschedule, to find work.

Size/Type: 1 to 2 numeric charactersRequired: NoBatch Keyword: JPrtyDefault: Value on CAIJGEN option SPRTY

Press PF8 for the next panel. It is displayed only for CPU jobs (station 40).

5-32 Online Guide

5.2 Jobs

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) CPU JOB BASE ------------------

COMMAND ===>


JCL:

Library Type . . . .

JCL DDname . . . . . Member Prefix . . .

Member Name . . . .

Submission:

Local Execution Sysid . .

Remote Execution Node . .

Remote Execution Sysid .

Insert Sched Enviro . . .

Scheduling Environment. .


� �



JCL SUBmit

The fields are:

Library TypeThe access method to use in retrieving the JCL for this job.

Valid values are:

DRIVERCA-Scheduler generates one line of JCL for Driver to expand.

JOBDOCCA-Jobdoc

LIBRNCA-Librarian

PANVCA-Panvalet

PDSPartitioned data set


5.2 Jobs

RDRQJobs are manually submitted outside of CA-Scheduler with aTYPRUN=HOLD on the job statement. CA-Scheduler releases the job andtracks it as if the job was submitted by CA-Scheduler. See "PerformanceConsiderations" in the Systems Programmer Guide for performanceimplications.

USERLIBThe access method is provided by a site-written exit program. See "User Exitsand APIs" in the Systems Programmer Guide for more information.

TESTLIBCA-Scheduler submits a dummy job (based on the skeleton in memberCAJUTSTB of the PDS allocated to ddname JCLMASTR). The dummy jobmay execute for a specified number of seconds, end with a specific returncode, or abend, based on parms defined at the job level. See the field TestParm on page 5-38.

ROSCOECA-Roscoe

Required: NoBatch Keyword: LibtypeDefault: Value on schedule's Library Type field

JCL DDnameFor Library Type of PDS, the ddname of the partitioned data set containing thejob's JCL.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: DDnameDefault: Value on schedule's JCL DDname field

Member PrefixFor Library Type of PANV (CA-Panvalet), the first portion of the member namein the CA-Panvalet library. The Member Prefix and Member Name fields arecombined and the first 10 characters used as the member name.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: MBrsubidDefault: Blanks

5-34 Online Guide

5.2 Jobs

Member NameThe member name in the JCL library that contains the job's JCL.

Note: The job name in the JCL must match the job name as defined toCA-Scheduler.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: LIBMembDefault: Job name

Local Execution SysidThe system ID (SMF ID) on which this job must execute. If the CAIJGENinstallation option INSRSYS is YES, CA-Scheduler modifies the job's JCL duringsubmission to include this system ID.

Size/Type: 1 to 4 alphanumeric charactersRequired: NoBatch Keyword: SYsidDefault: Blanks (Any local system ID)

Remote Execution NodeThe JES NJE node name where the job should execute. If the CAIJGENinstallation option INSROUT is YES, CA-Scheduler modifies the job's JCL duringsubmission to include this node ID.

Alternatively, the value may be *REMOTE to indicate that the job executes on anon-OS/390 system running Unicenter TNG. See Chapter 11, “RemoteScheduling” on page 11-1 for more information.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: NOdeDefault: Blank (Local node)

Remote Execution SysidThe system ID (SMF ID) on which the job must execute at a remote JES NJEnode. If the CAIJGEN installation option INSRSYS is YES, CA-Schedulermodifies the job's JCL during submission to include this system ID.

Size/Type: 1 to 4 alphanumeric charactersRequired: NoBatch Keyword: NODESysDefault: Blank (Any system ID)

Insert Sched EnviroControls the automatic insertion of a Workload Manager scheduling environmentname. If not specified, the insert option is taken from the schedule. The schedulingenvironment to be inserted into the JCL is taken from the Scheduling Environmentfield below, or from the schedule if blank.

Size/Type: YES, NO, or blankRequired: NoBatch Keyword: INSRSenvDefault: Blank (use schedule's value)


5.2 Jobs

Scheduling EnvironmentThe name of a Workload Manager scheduling environment that should be insertedinto this job's JCL during submission. The value is only inserted if the InsertSched Enviro field above is YES (or defaults to YES). If the SchedulingEnvironment is blank, the schedule's value is used.

Size/Type: 1- to 16-alphanumeric charactersRequired: NoBatch Keyword: SCHENVDefault: Blank (use schedule's value)

Press PF8 for the next panel. It is displayed only for CPU jobs (station 40).

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) CPU JOB BASE ------------------

COMMAND ===>


Failures:

Fail Oper . . . .

Fail Code . . . . ��

Abend Option . . .

Fail Option . . .

Options:

Insert CA-11 . Interrupt . . . . . NO

Stage JCL . .

Memo . . . . .

Test Parm . .


� �



FAILures OPTions MEMO

Fail OperA Boolean operator used in determining if the job ended with an unacceptablereturn code. See Fail Code. Valid values are GE (Greater than or Equal), GT(Greater Than), EQ (EQual), NE (Not Equal), LE (Less than or Equal), and LT(Less Than).


5-36 Online Guide

5.2 Jobs

Fail CodeA number that is compared to the job's highest return code using the Fail Oper todetermine if the job ended with an unacceptable return code. The followingequation is evaluated:

job's-high-return-code Fail-Oper Fail-Code

If the statement is true, then the job is marked as failed. A typical setting is a FailOper of GE and a Fail Code of 1, making zero the only acceptable return code forthe job.







Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: AbendDefault: ABORT






Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: FAILEd


5.2 Jobs

Default: ABORT

Insert CA-11Controls the automatic insertion of the CA-11 RMS.

Size/Type: YES|NORequired: NoBatch Keyword: INSrrmsDefault: Value of the schedule's Insert CA-11 field

InterruptIndicates whether a CPU job is to be interrupted for operator intervention before itis posted as complete. Valid options are:

NOThis job is not to be interrupted. It is to be posted as complete as soon as itcompletes successfully. This is the default.

YESThis job is to be interrupted. The job's status is shown as Interrupted insteadof Completed even though it ends successfully. An interrupted job can be runagain if necessary using the RERUN or SUBMIT commands. Successors tothis job are not posted as satisfied until this job is ended manually using theCOMPLETE command.

Size/Type: NO|YESRequired: NOBatch Keyword: INTERUPTDefault: NO

Stage JCLIf Stage JCL is set to YES, the job's JCL is copied into the CA-Scheduler activeworkload and submitted from there.

Size/Type: YES|NORequired: NoBatch Keyword: STAGeDefault: Value of schedule's Stage JCL field

MemoCA-Scheduler displays the value of the Memo field as a WTOR (Write ToOperator with Reply) at the beginning of the job. A manual reply by the operatoris required before the job may execute.

Size/Type: 1 to 60 alphanumeric charactersRequired: NoBatch Keyword: MEmo

Test ParmFor Library Type of TESTLIB, the Test Parm determines how long the jobexecutes and how it ends. One or more of the following may be specified:

T=nnnnNumber of seconds to execute

5-38 Online Guide

5.2 Jobs

F=nnnnNormal return code to generate

A=nnnnAbend code to generate (user abend)

If multiple options are specified, separate them with commas.

Size/Type: 1 to 20 alphanumeric charactersRequired: NoBatch Keyword: TEstparmDefault: The values specified on member CAJUTSTB in your JCLMASTR

data set

Press PF8 for the next panel. It is displayed only for non-CPU jobs (stations other than40).

� � ---------------- CA-SCHEDULER 9.� xxyy (SCHD) NON-CPU JOB BASE ----------------

COMMAND ===>


Non-CPU Options:

Automatic Start . . NO


� �


The field is:

Automatic StartIf set to YES, the non-CPU job starts as soon as any Early Start time andpredecessors are satisfied. Otherwise, the job waits for manual Start Job command.

Size/Type: YES|NORequired: NoBatch Keyword: AUtostrtDefault: NO



5.2 Jobs

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB BASE --------------------

COMMAND ===>


Simulation:

JES Class . . . . . . .

JES Priority . . . . .

Use Simulation Times . . NO

Documentation:

Display Key . . .

Display Time . . ��


� �



SIM DOC

The fields are:

JES ClassThe value SIMULATE should use in determining which simulation initiator thejob should use. The value is not used outside of simulation.


Jes PriorityThe value SIMULATE should use in determining when a job should start in thesimulation. If multiple jobs are available to start, jobs with high JES Priorityvalues are started first. The value is not used outside of simulation.

Size/Type: 1 to 2 numeric characters from 0 to 15Required: NoBatch Keyword: Prty

Display KeyA key of documentation to display on the OS/390 console for this job.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: Dispkey

5-40 Online Guide

5.2 Jobs

Display TimeThe time to display the documentation referred to by Display Key on the OS/390console.


Size/Type: 1 to 6 numeric characters in ddhhmm formatRequired: NoBatch Keyword: DISPTimeDefault: 0 (Display documentation immediately)


� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) JOB SECURITY ------------------

COMMAND ===>


External Security:

User id . . .

Group id . .


� �

The batch command object for this panel is JSI.


JSI SECurity

The fields are:

User IDThe user ID to be associated with this job when it is submitted to JES.

Note: The user ID in the submitted job is determined by the order of theCAIJGEN option SUBUID. The value JSI corresponds to this field.

The CAIJGEN option SECURTY must be set to YES, and the CAIJ$SECoption for the specific library type (access method) must be YES before auser ID is inserted into the JCL.


5.2 Jobs

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: UseridDefault: Value of the schedule's User ID

Group IDThe group ID to be associated with this job when it is submitted to JES.

Note: The group ID in the submitted job is determined by the order of theCAIJGEN option SUBUID. The value JSI corresponds to this field.

The CAIJGEN option SECURTY must be set to YES, and the CAIJ$SECoption for the specific library type (access method) must be YES before agroupid is inserted into the JCL.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: GroupidDefault: Value of the schedule's Groupid


� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) JOB RESOURCE ------------------

COMMAND ===>


Separate Job Execution:

Resource . . .

Job List . . . . . . . . .

. . . . . . . . .


� �

The batch command object for this panel is JRR.


JRR SEPjob SEPdsn

5-42 Online Guide

5.2 Jobs

The fields are:

ResourceThe job must "own" this resource name before CA-Scheduler submits it. If two ormore jobs have the same resource name specified, only one at a time may besubmitted.

Size/Type: 1 to 44 alphanumeric charactersRequired: NoBatch Keyword: SEPDsn

Job ListSpecific job names or job name masks that may not be submitted when this job issubmitted. If any job that matches an entry in the list is submitted whenCA-Scheduler is ready to submit this job, this job is not submitted.

The entries may use masking characters. A question mark ('?') represents anycharacter, but only of length one. An asterisk ('*') represents any character, of anylength (including zero). Question marks and asterisks may be combined.

Note: If the CAIJGEN option MCPU is set to YES, the use of masking in theJob List may cause severe performance problems. See the topicPerformance Considerations for Separate Job List in the SystemsProgrammer Guide.

Size/Type: 1 to 8 alphanumeric characters specified from one to eight timesRequired: NoBatch Keyword: SEPJob=(name,name,...)


Mask Matches Doesn't Match

ABCD ABCD ABCDE

AB?D ABCD, ABXD ABD

AB*D ABCD, ABXXD, ABD ABCDE

ABC* ABC, ABCD, ABCDE ABDC

AB?D* ABCD, ABCDEFG ABDEF


5.2 Jobs

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) JOB RESOURCE ------------------

COMMAND ===>


Simulation Resources:

Disk Type/Count . . . / �� . . . / ��

/ �� . . . / ��

Dasd EXCPs . . . . . ��

Tape Type/Count . . . / �� . . . / ��

/ �� . . . / ��

Tape EXCPs . . . . . ��

Unit Type/Count . . . / �� . . . / ��

/ �� . . . / ��

Unit EXCPs . . . . . ��

Maximum CPU Time . . �� (ddhhmm)

Route Delay . . . . . �� (ddhhmm)


� �

The batch command object for this panel is JRR.

The fields are:

Dasd Type/CountThe number of up to four different types of DASD required by this job. Thisinformation is used only by simulation.

Size/Type: 1 to 8 alphanumeric characters, 1 to 3 numeric charactersRequired: NoBatch Keyword: DASDnn=(type,count) where nn is 01 to 04

Dasd EXCPsThe number of DASD I/Os done by this job. This information is used only bysimulation.

Size/Type: 1 to 8 numeric charactersRequired: NoBatch Keyword: DExcps

Tape Type/CountThe number of up to four different types of tape drives required by this job. Thisinformation is used only by simulation.

Size/Type: 1 to 8 alphanumeric characters, 1 to 3 numeric charactersRequired: NoBatch Keyword: TAPEnn=(type,count) where nn is 01 to 04

Tape EXCPsThe number of tape I/Os done by this job. This information is used only bysimulation.

Size/Type: 1 to 8 numeric charactersRequired: NoBatch Keyword: TExcps

5-44 Online Guide

5.2 Jobs

Unit Type/CountThe number of up to four different types of other units required by this job. Thisinformation is used only by simulation.

Size/Type: 1 to 8 alphanumeric characters, 1 to 3 numeric charactersRequired: NoBatch Keyword: UNITnn=(type,count) where nn is 01 to 04

Unit EXCPsThe number of other unit I/Os done by this job. This information is used only bysimulation.

Size/Type: 1 to 8 numeric charactersRequired: NoBatch Keyword: UExcps

Maximum CPU TimeThe execution duration of the job for simulation reports. This number, in ddhhmmformat, overrides the average execution time. This information is used only bysimulation.

Size/Type: 1 to 6 numeric characters in ddhhmm formatRequired: NoBatch Keyword: Cputime

Route DelayThe amount of time it takes to route a job from one system (or NJE node) toanother and back. Used by simulation to more accurately reflect the time fromsubmission to job completion. This information is used only by simulation.

Size/Type: 1 to 6 numeric characters in ddhhmm formatRequired: NoBatch Keyword: Rdt



5.2 Jobs

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) JOB MESSAGES ------------------

COMMAND ===>



All Events . . . . . . . . . . . . .

Job Start . . . . . . . . . . . . .

Job Fail . . . . . . . . . . . . . .

Job Abend . . . . . . . . . . . . .

Job Interrupt . . . . . . . . . . .

Job End . . . . . . . . . . . . . .

Job Purge . . . . . . . . . . . . .

Job Late . . . . . . . . . . . . . .

Job Skipped . . . . . . . . . . . .


� �

The batch command object for this panel is JMR.


JMR MSG MESsages

The fields are:

All EventsA list of user IDs or OPERxxyy values to which messages should be sent whenthe job starts, fails, abends, completes, is purged, or becomes late. See below formore information.

Size/Type: 1 to 8 alphanumeric characters specified zero to four timesRequired: NoBatch Keyword: Msg=(user,user,...)

Job StartA list of user IDs or OPERxxyy values to which messages should be sent whenthe job starts. See below for more information.

Size/Type: 1 to 8 alphanumeric characters specified zero to four timesRequired: NoBatch Keyword: STARtmsg=(user,user,...)

5-46 Online Guide

5.2 Jobs

Job FailA list of user IDs or OPERxxyy values to which messages should be sent whenthe job fails (bad return code, JCL error, submit fail). See below for moreinformation.

Size/Type: 1 to 8 alphanumeric characters specified zero to four timesRequired: NoBatch Keyword: Failmsg=(user,user,...)

Job AbendA list of user IDs or OPERxxyy values to which messages should be sent whenthe job abends. See below for more information.

Size/Type: 1 to 8 alphanumeric characters specified zero to four timesRequired: NoBatch Keyword: Abendmsg=(user,user,...)

Job InterruptA list of user IDs or OPERxxyy values to which messages should be sent whenthe job completes but has Interrupt set to Yes. See below for more information.

Size/Type: 1 to 8 alphanumeric characters specified zero to four timesRequired: NoBatch Keyword: Intermsg=(user,user,...)

Job EndA list of user IDs or OPERxxyy values to which messages should be sent whenthe job completes. See below for more information.

Size/Type: 1 to 8 alphanumeric characters specified zero to four timesRequired: NoBatch Keyword: Endmsg=(user,user,...)

Job PurgeA list of user IDs or OPERxxyy values to which messages should be sent whenthe job output is removed from JES. See below for more information.

Size/Type: 1 to 8 alphanumeric characters specified zero to four timesRequired: NoBatch Keyword: Purgemsg=(user,user,...)

Job LateA list of user IDs or OPERxxyy values to which messages should be sent whenthe job is marked late. See below for more information.

Size/Type: 1 to 8 alphanumeric characters specified zero to four timesRequired: NoBatch Keyword: Latemsg=(user,user,...)

Job SkippedA list of zero to four user IDs or OPERxxyy values to which messages should besent when the job is skipped at autoscan. See below for more information.

Size/Type: 1 to 8 alphanumeric characters specified zero to four timesRequired: NoBatch Keyword: SKIPmsg=(user,user,...)


5.2 Jobs


| Messages are stored in the database when the value is MAILBOX, and may beretrieved by the REPORT MAILBOX command.


The CAIJGEN options STRMSG, ENDMSG, FALMSG, ABNMSG, INTMSG,PURMSG, LATMSG, and SKPMSG specify locations to which all start, end, fail,abend, interrupt, purge, and late messages should be sent. Normally these includeMAILBOX.

All messages are sent both to the CAIJGEN locations and to the locations enteredhere.


� � ---------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB REASON CODES ----------------

COMMAND ===>


Average Times:

Reasons �1 to �4 . . �� . . . �� . . . �� . . . ��

Reasons �5 to �8 . . �� . . . �� . . . �� . . . ��

Reasons �9 to 12 . . �� . . . �� . . . �� . . . ��

Reasons 13 to 16 . . �� . . . �� . . . �� . . . ��

Early Start Times:

Reasons �1 to �4 . . �� . . . �� . . . �� . . . ��

Reasons �5 to �8 . . �� . . . �� . . . �� . . . ��

Reasons �9 to 12 . . �� . . . �� . . . �� . . . ��

Reasons 13 to 16 . . �� . . . �� . . . �� . . . ��


� �

The batch command object for this panel is JRC.


JRC AVG AVErage EARLY ERLY

5-48 Online Guide

5.2 Jobs

The fields are:

Average Times, Reasons 01 to 16Allows an override of the user-specified average time based on the selectionreason code. See below for more information. The value is specified as ddhhmm,where dd is the number of autoscans and hhmm is hours and minutes.

Size/Type: Zero to sixteen 1 to 6 numeric characters in format ddhhmmRequired: NoBatch Keyword: AVGxx where xx is 01 to 16

Early Start Times, Reasons 01 to 16Allows an override of the early start time based on the selection reason code. Seebelow for more information. The value is specified as ddhhmm, where dd is thenumber of autoscans and hhmm is hours and minutes.

Size/Type: Zero to sixteen 1 to 6 numeric characters in format ddhhmmRequired: NoBatch Keyword: ERLYxx where xx is 01 to 16

The selection reason code reflects what part of the job's criteria was used to justify itsinclusion in the workload. For example, if the criteria reads:

MON OR TUE


(MON OR TUE)




COMMAND ===>


Must Start Times:

Reasons �1 to �4 . . �� . . . �� . . . �� . . . ��

Reasons �5 to �8 . . �� . . . �� . . . �� . . . ��

Reasons �9 to 12 . . �� . . . �� . . . �� . . . ��

Reasons 13 to 16 . . �� . . . �� . . . �� . . . ��

Must End Times:

Reasons �1 to �4 . . �� . . . �� . . . �� . . . ��

Reasons �5 to �8 . . �� . . . �� . . . �� . . . ��

Reasons �9 to 12 . . �� . . . �� . . . �� . . . ��

Reasons 13 to 16 . . �� . . . �� . . . �� . . . ��


� �


5.2 Jobs



MUSTStrt MUSTEnd STARt

The fields are:

Must Start Times, Reasons 01 to 16Allows an override of the must start time based on the selection reason code. Seebelow for more information. The value is specified as ddhhmm, where dd is thenumber of autoscans and hhmm is hours and minutes.

Size/Type: Zero to sixteen 1 to 6 numeric characters in format ddhhmmRequired: NoBatch Keyword: MUSTxx where xx is 01 to 16

Must End Times, Reasons 01 to 16Allows an override of the must end time based on the selection reason code. Seebelow for more information. The value is specified as ddhhmm, where dd is thenumber of autoscans and hhmm is hours and minutes.

Size/Type: Zero to sixteen 1 to 6 numeric characters in format ddhhmmRequired: NoBatch Keyword: DEADxx where xx is 01 to 16


MON OR TUE


(MON OR TUE)



5-50 Online Guide

5.2 Jobs


COMMAND ===>


Maximum Execution Times:

Reasons �1 to �4 . . �� . . . �� . . . �� . . . ��

Reasons �5 to �8 . . �� . . . �� . . . �� . . . ��

Reasons �9 to 12 . . �� . . . �� . . . �� . . . ��

Reasons 13 to 16 . . �� . . . �� . . . �� . . . ��


� �



MAX

The fields are:

Maximum Execution Times, Reasons 01 to 16Allows an override of the maximum execution time based on the selection reasoncode. See below for more information. The value is specified as ddhhmm, wheredd is the number of autoscans and hhmm is hours and minutes.

Size/Type: Zero to sixteen 1 to 6 numeric characters in format ddhhmmRequired: NoBatch Keyword: MAXxx where xx is 01 to 16


MON OR TUE


(MON OR TUE)




5.2 Jobs

� � ----------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB NODE INFORM ----------------

COMMAND ===>


Inform JES Nodes:

Node . . . . . . . . .

. . . . . . . . .


� �

The batch command object for this panel is JNR.


JNR NODEs

The fields are:

NodeUp to eight JES NJE or VSE POWER nodes, defined by the CAIJNET macro,that should be notified when this job starts and ends. This field does not changewhere the job executes, only who is told about the job. Schedules and jobs at thespecified nodes may wait on this job by using criteria with the following syntax:

┌ ┐─-�1── ┌ ┐─4�──────��─ ──┬ ┬─────── ─NJE──,──jobname─ ──┼ ┼────── ──┼ ┼───────── ───────� └ ┘─START─ └ ┘─-jno─ └ ┘─station─

�─ ──┬ ┬────────── ────────────────────────────────────────────�� └ ┘ ─schedule─

Size/Type: 1 to 8 alphanumeric characters specified from zero to eight timesRequired: NoBatch Keyword: Inform=(nodename,nodename,...)


5-52 Online Guide

5.2 Jobs

� � ----------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB INFORMATION ----------------

COMMAND ===>


Information:

Description . . .

Comment . . . . .

Exit Parm . . . .

Form . . . . . .

Quantity . . . .

Notify . . . . .

Responsibility. .

Verify . . . . . NO

Specification . .


� �

The batch command object for this panel is JIR.


JIR INFO


DescriptionA description of the job.


CommentA comment that appears next to the job name on some reports.

Size/Type: 1 to 30 alphanumeric charactersRequired: NoBatch Keyword: Comment

Exit ParmA string passed to the simulation exit when this job is processed.



5.2 Jobs

FormIdentify a form that is associated with the standard jobs in this schedule.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: Form

QuantityIndicate how much input or output is expected for this schedule.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: Quantity

NotifyName a person or group to be notified in connection with this job or schedule.

Size/Type: 1 to 12 alphanumeric charactersRequired: NoBatch Keyword: NOtify

ResponsibilityName the person or group responsible for this schedule.

Size/Type: 1 to 12 alphanumeric charactersRequired: NoBatch Keyword: Resp

VerifyIndicate whether this schedule requires special verification. This is for reportingpurposes only.

Size/Type: YES or NORequired: NoBatch Keyword: VerifyDefault: NO

SpecificationGive specification data associated with this schedule.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: SPec


5-54 Online Guide

5.2 Jobs

� �----------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB INFORMATION ----------------

COMMAND ===>


Destinations:

�1 to �4 . . . . . . . . .

�5 to �8 . . . . . . . . .

Deliverables:

�1 to �2 . . . . .

�3 to �4 . . . . .

�5 to �6 . . . . .

�7 to �8 . . . . .

Simulation Route Stations:

�1 to �8 . . . . . . . . . . . . . . . . .

Enter END to Exit, DOWN for Next Screen, or UP for Previous Screen.

� �

The batch command object for this panel is JIR.


DestinationsGive up to eight destinations for the output from the jobs in this schedule.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: DESTx where x is 1 to 8

DeliverablesGive up to eight delivery specifications for the jobs in this schedule.

Size/Type: 1 to 16 alphanumeric characters specified from zero to eight timesRequired: NoBatch Keyword: DELx where x is 1 to 8

Simulation Route StationsUse this to notify a defined route station when this job is going to be selected forprocessing in simulation. List up to eight route stations that are to receive a reportwhen this job is selected as part of a forecast. Route stations are defined byspecifying two letters in the station record instead of two numbers.

Size/Type: 1 to 2 alphanumeric characters specified from zero to eight timesRequired: NoBatch Keyword: ROut=(id,id,...)



5.2 Jobs

� �--------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB CROSS-PLATFORM ---------------

COMMAND ===>

Name . . . XPLATJ Number . . �1 Station . . 4� Schedule . . XPLATS

Cross-Platform information:

Node . . . .

Domain . . .

User id . .

Password . .

Verify . . .

| SU Flag . .


� �



XPLat CROss BOTtom

The fields on this panel are ignored unless the execution node (on a previous panel) is*REMOTE and the CAIJGEN option XPLAT=YES is used. These fields provideinformation for executing this job on another platform.

The fields are:

NodeThe CCI name of the destination machine for this job.

Size/Type: 0 to 8 alphanumeric charactersRequired: NoBatch Keyword: XPNode

DomainThe Microsoft Windows NT domain in which the user ID is defined. The fieldmay be case-sensitive.

Size/Type: 0 to 15 alphanumeric charactersRequired: NoBatch Keyword: XPDomain

5-56 Online Guide

5.2 Jobs

User idThe user ID with which the job should be initiated. The field may becase-sensitive.

Size/Type: 0 to 32 alphanumeric charactersRequired: NoBatch Keyword: XPUser

| Password| The password for the above user ID.

| Size/Type: 1 to 14 alphanumeric characters| Required: No| Batch Keyword: XPPswd

| Verify| A second chance to type the password correctly.

| SU Flag| Determines if the Unix Switch User (su) flag is sent for this job or not. The| setting has no impact for jobs not executing on Unix-based systems.

| YES| Indicates that the Unix su command is issued with the dash ("-") option.

| NO| Indicates that the dash option is not used.

| blank| Indicates that the global default (CAS9 CAIJGEN XPSUTYPE) value is used.

| Size/Type: YES, NO, or blank| Required: No| Batch Keyword: XPSUtype

5.2.2.2 Job Criteria

If you are displaying a job, the criteria is browsed using the ISPF/PDF BROWSEservice. The first line of the criteria displays the calendar name in use, if any.

If you are defining or altering a job, the criteria is edited using the ISPF/PDF EDITservice. A NOTE line indicates the calendar name in use, if any. If you need to changethe calendar name, enter CAL xxx on the command line, where xxx is the newcalendar name.

Use PF3 to exit and save any changes. Use CAN to exit without saving any changes.


5.2 Jobs

5.2.2.3 Job Steps

Use Job Step entries to determine if step has ended with an unacceptable return code.You can use the Fail Oper and Fail Code fields on the job if the same rules for returncodes apply to all steps in a job. If one or more steps have different rules for "bad"return codes, use Job Step entries.

For example, if a job has 10 steps that all must end with a return code of zero, use aFail Oper of GE and a Fail Code of 1 on the job. If, however, nine steps must endwith zero and one step must end with a 4, use Job Step entries.

Note: If any Job Step entries are specified for a job, CA-Scheduler ignores the job'sFail Oper and Fail Code values. A blank Procstep and a Stepname of *(asterisk) may be defined as a default JSR for the job. Any step that does nothave a specific JSR uses the default JSR.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB STEPS -------------------



Procstep Stepname Type Failoper Failcode More

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


� �

The batch command object for this panel is JSR.

The fields on the panel are:

NameThe name of the job whose Job Step entries are being manipulated.


NumberThe number of the job.


StationThe station of the job. This number is always 40 because only CPU jobs havesteps. It is displayed to be consistent with other job displays.

5-58 Online Guide

5.2 Jobs

ScheduleThe schedule that owns the job.


ProcstepThe step name outside of the proc used to identify the step. If the step does nothave a procedure, then the Procstep is blank. Once a Job Step entry is defined, theProcstep name may not be changed.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: PROCstep

StepnameThe step name (with the EXEC PGM= on it). Once a Job Step entry is defined,the Stepname name may not be changed.

Size/Type: 1 to 8 alphanumeric characters or * (asterisk) for the default JSR forthis job. The Procstep must be blank for the default JSR.

Required: YesBatch Keyword: STEP

TypeDetermines if the Failoper/Failcode pairs indicate good return codes or bad.

Size/Type: BAD or GOODRequired: YesBatch Keyword: TYpe

FailoperA Boolean operator used in determining if the step ended with an unacceptablereturn code. See Failcode. Valid values are GE (Greater than or Equal), GT(Greater Than), EQ (EQual), NE (Not Equal), LE (Less than or Equal), and LT(Less Than). The value may be changed by overtyping it.

Required: YesBatch Keyword: FAILOper

FailcodeA number that is compared to the step's return code using the Failoper todetermine if the step ended with an unacceptable return code. The followingequation is evaluated:

return-code Failoper Failcode

If the statement is true, then the Type is used to determine if the step endedsuccessfully or not. If Type is BAD, the step failed; if Type is GOOD, the stepwas successful.


5.2 Jobs

If the statement is false, then the opposite of Type is used to determine if the stepended successfully or not.

Size/Type: 1 to 4 numeric charactersRequired: YesBatch Keyword: FAILCode

Add Job Step entries by typing an I on the command line or next to an existing entry.The Job Steps panel displays.

Copy entries by typing an R next to the entry. The Job Steps panel displays.

Delete entries by typing a D next to the entry.

Press PF3 to exit and save any changes. To exit without saving changes, type CAN onthe command line.

Job Step Entry: The following panel is displayed when adding or copying a JobStep entry.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB STEPS -------------------

COMMAND ===>


Step Definition:

Procedure step name . . (Outside of the procedure)

Step name . . . . . . . (Step name with PGM=)

If true, step is . . . BAD (Good or Bad)

Fail operator . . . . . Return code . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

. . . . . . . . . . .

Enter END to exit, or press ENTER to save changes.

� �

The batch command object for this panel is JSR.

The fields are:

Procedure step nameThe name of the step outside of a PROC. This field may be blank if the step doesnot use a PROC.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: PROCstep

5-60 Online Guide

5.2 Jobs

Step nameThe name of the step (with the EXEC PGM= on it). This field is required.

Size/Type: 1 to 8 alphanumeric characters or * (asterisk) for the default JSR forthis job. The Procstep must be blank for the default JSR.

Required: YesBatch Keyword: STEP

If true, step isDetermines if the Failoper/Failcode pairs indicate good return codes or bad.

Size/Type: BAD or GOODRequired: YesBatch Keyword: TYpe

Fail operA Boolean operator, used with the Return code, to determine if the step's returncode is unacceptable.

Size/Type: 2 alphanumeric charactersRequired: YesBatch Keyword: FAILOper

Return codeA number compared to the step's return code to determine if the return code isunacceptable. The following equation is evaluated:

step's-return-code Fail-oper Return-code

If the statement is true, then the Type is used to determine whether the step endedsuccessfully. If Type is BAD, then the step failed; if Type is GOOD, the step wassuccessful.

If the statement is false, then the opposite of Type is used to determine whetherthe step ended successfully.

Size/Type: 1 to 4 numeric charactersRequired: YesBatch Keyword: FAILCode


5.2 Jobs

5.2.2.4 Driver Parms

You may specify parameters to be passed to a Driver procedure for jobs with a LibraryType of DRIVER.

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) DRIVER PARMS ------------------


Name . . . DRVTEST Number . . �1 Station . . 4� Schedule . . DRVTEST

Variable Type / Value

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


� �

The fields are:

VariableThe name of the variable parameter to be passed to the Driver PROC. Thevariable name may be one to seven characters long with an optional arraysubscript in parentheses (that is, VARNAME(1) ).

TypeThe value NORMAL or RESTART. Variable parameters with a type of NORMALare passed when jobs are automatically submitted or submitted due to the FORCEor SUBMIT commands. Variable parameters with a type of RESTART are passedwhen jobs are submitted due to the RERUN command.

Value(Under the Type value) The value of the variable parameter.

Variables may be added by typing an I on the command line or to the left of anexisting variable. This adds a blank entry that may be overtyped.

Variables may be deleted by typing a D to the left of the variable.

Press PF3 to exit and save any changes. A batch command is built to process thechanges. If the command is successful, it is not shown. If it fails, the output isdisplayed and the list of variables is presented.

To exit without saving any changes, type CAN on the command line.

5-62 Online Guide

5.2 Jobs

5.2.2.5 Virtual Resources

You may view and maintain virtual resources that are required before this job may besubmitted.

� �----------------------- CA-SCHEDULER 9.� xxyy (SCHD) VRM ----- Row 1 to 3 of 3


Virtual resources required by job RT8�1 JNO �1 Station 4� Schedule RESTEST8

Resource Type Status Free

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

_ XXX SIMPLE ACTIVE NO

_ YYY ENQ SHR NO

_ ZZZ COUNT 2 NO

�� Bottom of data ��

� �

The fields are:

ResourceThe name of the virtual resource associated with this job.

TypeThe type of the virtual resource.

StatusThe state that the virtual resource must have before the job may be submitted.

FreeSpecifies if the virtual resource should be released at job end even if the jobabends or fails.

Select a job/virtual resource association by entering a letter to the left of the virtualresource. Enter:

S to select the association for viewingE to edit (alter) an associationD to delete an associationI (or on the command line) to define a new association for this resource

The dialog to maintain virtual resources is discussed in 5.10.4, “Job/VRM Association”on page 5-120.


5.2 Jobs


5.2.3.1 Example 1

Define a job, ABC, to a schedule XYZ, with an Early Start time of 2:00 PM.


//SYSIN DD �

DEFINE JBR N=ABC,S=XYZ,ERLYTIME=14��

//

5.2.3.2 Example 2

This job should be selected only on Mondays and Tuesdays.


//SYSIN DD �

DEFINE JCR N=ABC,S=XYZ,CRI='MON OR TUE'

//

5.2.3.3 Example 3

Define two steps: Step 1 must end with a zero, step 2 must end with a four.


//SYSIN DD �

DEFINE JSR N=ABC,S=XYZ,STEP=STEP1,FAILOPER=GE,FAILCODE=1

DEFINE JSR N=ABC,S=XYZ,STEP=STEP2,FAILOPER=NE,FAILCODE=4

//

5.2.3.4 Example 4

Define a job with a Library Type of Driver, specifying a normal and restart parm.


//SYSIN DD �

DEFINE JBR N=DRIVJOB,S=XYZ,LIBTYPE=DRIVER,

DRIVPARM='(VAR1=NORMAL)',

RESTPARM='(VAR1=RESTART)'

//

5-64 Online Guide

5.2 Jobs

5.2.4 Copying a Job

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) COPY JOB --------------------

COMMAND ===>

Copy job

number

station

schedule

To job

number

station

schedule

Enter END to exit.

� �

CA-Scheduler lists the job you selected in the Copy Job fields. Enter the new jobinformation in the To job fields.

All of the job is copied, including criteria. After you have copied the job, you mayalter the new job to make any desired changes.


5.3 User IDs

5.3 User IDs

The user ID dialogs maintain information about users who may access theCA-Scheduler online system and the amount of authority they have. Your site may ormay not require user definitions.

If the installation CAIJGEN option SECURTY is set to EXTERNAL, CA-Schedulerdoes not require and ignores user definitions. If CAIJGEN SECURTY is set to NO orYES, CA-Scheduler requires user definitions.

Option 3 of the CA-Scheduler Database menu displays the User IDs menu.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) USER IDS --------------------

OPTION ===>

User ID . . .

1 DIRECTORY - List of User IDs

2 DISPLAY - View an Existing User ID

3 ALTER - Alter an Existing User ID

4 DEFINE - Create a New User ID

5 DELETE - Remove an Existing User ID

6 COPY - Copy an Existing User ID

Enter END to Exit.

� �

Use option 1, DIRECTORY, to display a scrollable list of users defined toCA-Scheduler. You may enter a partial user ID in the User ID field to limit thedisplay. From the list, you may Select (display), Edit, Delete, or Copy user IDs.

For options 2 to 6, you must enter the user ID.

Use option 2, DISPLAY, to view a specific user ID.

Use option 3, ALTER, to edit a specific user ID.

Use option 4, DEFINE, to create a new user ID.

5-66 Online Guide

5.3 User IDs

Use option 5, DELETE, to remove a specific user ID. If you have requested the DeleteConfirmation option (see Chapter 3, “Options”), CA-Scheduler displays a panel askingyou to confirm the deletion. Otherwise, the user ID is deleted immediately.

Use option 6, COPY, to copy a user ID, creating a new user ID.

5.3.1 Directory

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) USER IDS ROW 1 TO 3 OF 3


Userid Type Description

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

_ LEEFR�1 GENERAL FRED LEE

_ PUBJO�1 MANAGER JOHN Q. PUBLIC

_ SMIJA�2 SUPERVISOR JANE SMITH


� �

Each user ID is displayed on a single row. The upper right-hand corner of the paneldisplays the current range of rows and the total number of rows. CA-Scheduler onlyreads the first 50 user IDs before displaying the list. As you scroll down, more rowsare automatically added until the entire list has been built.

Select a user ID by entering a letter to the left of the user ID. Enter:

S to select a user ID for viewingE to edit (alter) a user IDC to copy a user IDD to delete a user ID


5.3 User IDs

5.3.2 User ID Definition

The same panel is used to display, edit, and define user IDs. To save your changes andexit, use PF3. To exit without saving your changes, enter CAN on the command line.

The batch utility to use for maintaining user IDs is CAJUTIL0. The batch commandsfor maintaining user IDs are:

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) USER IDS --------------------

COMMAND ===>

User id . . .

Passwords:

Read . . .

Write . . .

Other:

Type . . . . . . (General, Supervisor, Manager)

Description . .

Stations . . . . . . . . . . . . . . . . . .

Enter END to exit.

� �

The fields are:

User idThe name of the user ID being manipulated. This field may not be modified afterthe user ID is defined.


Alter (Edit) ALTER USERID

Copy N/A

Define DEFINE USERID

Delete DELETE USERID

Display (View) LIST USERID

5-68 Online Guide

5.3 User IDs

ReadA password that the user must specify when accessing CA-Scheduler online onlyif CAIJGEN SECURTY is set to NO. If CAIJGEN SECURTY is set to YES,then this field is not used.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: Readpass

WriteA password that the user must specify when accessing CA-Scheduler online onlyif CAIJGEN SECURTY is set to NO. If CAIJGEN SECURTY is set to NO andthe user does not enter the correct write password, the user is allowed access toCA-Scheduler online in a read-only mode. If CAIJGEN SECURTY is set to YESand the user ID is defined without a write password, then the user is allowedaccess to CA-Scheduler online in a read-only mode.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: Writpass

TypeThe authority level of the user ID. The value may be General, Supervisor, orManager. See Table 5-1 on page 5-70 for more information.

Size/Type: 1 to 10 alphanumeric charactersRequired: YesBatch Keyword: Type=G|S|M

DescriptionA description or the name of the user whose user ID is being defined.


StationsIf one or more stations is specified, General and Supervisor user IDs cannot act onjobs at stations not in the list.

Size/Type: 2 numeric characters specified from zero to eight timesRequired: NoBatch Keyword: Connect=(nn,nn,...)


5.3 User IDs

The authorizations granted at each Type are:

Table 5-1 (Page 1 of 2). Authorization Types

GeneralA user with General authority can:

■ Maintain the passwords for this user ID record

■ Define jobs and schedules

■ Maintain schedule records for which this user ID is authorized

■ Maintain job records, defined for stations at which this user ID isauthorized, within schedules that this user ID is authorized to control

■ Display and alter staged JCL for jobs, while connected to the JCL setupstation (39), within schedules that this user ID is authorized to control

■ Define online documentation

■ Connect only to stations listed on the CONNECT parameter for this userID

■ Display the status of schedules that this user ID is authorized to control

■ Issue tracking commands to control schedules for which this user ID isauthorized

■ Issue tracking commands to control jobs, at stations for which this userID is authorized, within schedules that this user ID is authorized tocontrol

SupervisorA user with Supervisor authority can:

■ Maintain the passwords for this user ID record


■ Maintain all schedule records

■ Maintain all job records defined for stations for which this user ID isauthorized

■ Display and alter staged JCL for jobs while connected to the JCL setupstation (39)


■ Connect only to stations listed on the CONNECT parameter for this userID

■ Display the status of all schedules

■ Issue tracking commands to control all schedules

■ Issue tracking commands to control all jobs at stations for which thisuser ID is authorized

5-70 Online Guide

5.3 User IDs

Table 5-1 (Page 2 of 2). Authorization Types

ManagerA user with Manager authority can:

■ Define new user ID records

■ Define new calendars and date tables


■ Define and maintain all station records

■ Define and maintain resource records for all stations

■ Maintain all schedule records

■ Maintain all job records

■ Maintain all calendars and date tables

■ Maintain all fields within all user ID records

■ Display and alter all staged JCL records (regardless of any editorprotection characters) for all jobs while connected to the JCL setupstation (39)


■ Connect to all stations

■ Display the status of all schedules

■ Issue tracking commands to control all schedules

■ Issue tracking commands to control all jobs

■ Issue CANCEL ALL, HOLD ALL, PURGE ALL, RELEASE ALL,RELEASE AUTO, POST, UNPOST, MOVEOVER, and SETcommands


5.3 User IDs


5.3.3.1 Example 1

Define a user ID as a supervisor.


//SYSIN DD �

DEFINE USERID NAME=PUBJOHN,DESC='JONH Q. PUBLIC',TYPE=S,READPASS=READ,

WRITPASS=WRITE

//

5.3.3.2 Example 2

Change the user ID above to be a manager.


//SYSIN DD �

ALTER USERID NAME=PUBJOHN,TYPE=M

//

5.3.4 Copying a User ID

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) COPY USERID ------------------

OPTION ===>

Copy user USER1�3

to user

Enter END to exit.

� �

CA-Scheduler lists the user ID you selected in the Copy user field. Enter the new userID in the to user field.

5-72 Online Guide

5.4 Stations

5.4 Stations

Note: Station definitions are only used for simulation reports. You do not need todefine stations for any other reason.

A CA-Scheduler station is a place where work is done. Station 40 is called the CPUstation and is used for jobs that execute on a system. Stations less than 40 are manualtasks that must be done prior to a CPU task such as data entry or staging of JCL.Stations greater than 40 are manual tasks that must be done after a CPU task such asdelivery of a printed report.

Option 4 of the CA-Scheduler Database menu displays the Station menu.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) STATIONS --------------------

OPTION ===>

Station . . .

1 DIRECTORY - List of Stations

2 DISPLAY - View an Existing Station

3 ALTER - Alter an Existing Station

4 DEFINE - Create a New Station

5 DELETE - Remove an Existing Station

6 COPY - Copy an Existing Station

Enter END to Exit.

� �

Use option 1, DIRECTORY, to display a scrollable list of stations defined toCA-Scheduler. From the list you may Select (display), Edit, Delete, or Copy stations.

For options 2 to 6, you must enter the Station.

Use option 2, DISPLAY, to view a specific station.

Use option 3, ALTER, to edit a specific station.

Use option 4, DEFINE, to create a new station.


5.4 Stations

Use option 5, DELETE, to remove a specific station. If you have requested the DeleteConfirmation option (See Chapter 3, “Options”), CA-Scheduler displays a panel askingyou to confirm the deletion. Otherwise, CA-Scheduler deletes the station immediately.

Use option 6, COPY, to copy a station, creating a new one.

5.4.1 Directory

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) STATIONS -- ROW 1 TO 3 OF 3


ID Name Description

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

_ 39 STAGE STAGED JCL

_ 4� CPU CPU STATION

_ 6� OUTPUT OUTPUT DESTINATION


� �

Each station is displayed on a single row. The upper right-hand corner of the paneldisplays the current range of rows and the total number of rows. CA-Scheduler onlyreads the first 50 stations before displaying the list. As you scroll down, more rows areautomatically added until the entire list has been built.

Select a station by entering a letter to the left of the station. Enter:

S to select a station for viewingE to edit (alter) a stationC to copy a stationD to delete a station

5-74 Online Guide

5.4 Stations

5.4.2 Station Definition

The same panel is used to display, edit, and define stations. To save your changes andexit, use PF3. To exit without saving your changes, enter CAN on the command line.

The batch utility to use for maintaining stations is CAJUTIL0. The batch commandsfor maintaining stations are:

� � --------------------- CA-SCHEDULER 9.� xxyy (SCHD) STATION --------------------

COMMAND ===>

Station . . .

Details:

Name . . . . .

Title . . . .

Description . .

Time Zone . . . ��

Enter END to exit.

� �

The fields are:

StationThe number of the station being manipulated. This field may not be modified afterthe station is defined.

Size/Type: 2 numeric charactersRequired: YesBatch Keyword: Id

Alter (Edit) ALTER STATION

Copy N/A

Define DEFINE STATION

Delete DELETE STATION

Display (View) LIST STATION


5.4 Stations

NameA short name for the station that is displayed on the simulation Station report.


TitleThe title is displayed on the simulation Station report.

Size/Type: 1 to 60 alphanumeric charactersRequired: NoBatch Keyword: TITLe

DescriptionInformation about the station, displayed only by the List Station command.


5-76 Online Guide

5.4 Stations


5.4.3.1 Example 1: Define a CPU station


//SYSIN DD �

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

//

5.4.3.2 Example 2: Define a JCL setup station (station 39)


//SYSIN DD �

DEFINE STATION ID=39,NAME='STAGE',DESC='STAGED JCL'

//

5.4.4 Copying a Station

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) COPY STATION ------------------

OPTION ===>

Copy station 39

to station

Enter END to exit.

� �

CA-Scheduler lists the station you selected in the Copy station field. Enter the newstation number in the to station field.


5.5 Resources

5.5 Resources

Note: Resource definitions are only used for simulation reports. You do not need todefine resources for any other reason.

Resources map devices such as tape drives and job initiators that must be serializedbetween jobs. By defining each job to CA-Scheduler with the correct number of tapedrives it uses, and defining the total number of tape drives here, the CA-SchedulerSIMULATE command does not show individual jobs running until a sufficient numberof tape drives are available. The same can be done with initiators, DASD devices, andany other unit.

You may define DASD, tape, and units to a specific CPU in a multiple CPUenvironment or define as shared by all CPUs.

Option 5 of the CA-Scheduler Database menu displays the Resource menu.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) RESOURCES ------------------

OPTION ===>

Station . . .

System . . .

1 DIRECTORY - List of Resource Definitions

2 DISPLAY - View an Existing Resource Definition

3 ALTER - Alter an Existing Resource Definition

4 DEFINE - Create a New Resource Definition

5 DELETE - Remove an Existing Resource Definition

Enter END to exit.

� �

Use option 1, DIRECTORY, to display a scrollable list of resource definitions. Fromthe list you may Select (display), Edit, or Delete resource definitions.

For options 2 to 5, you must enter the Station. You may also enter a System ID.

Use option 2, DISPLAY, to view resources defined for a specific Station and System.

Use option 3, ALTER, to edit the resources defined for a specific Station and System.

Use option 4, DEFINE, to create a resource definition for a specific Station andSystem.

5-78 Online Guide

5.5 Resources

Use option 5, DELETE, to remove a resource definition. If you have requested theDelete Confirmation option (See Chapter 3, “Options”), CA-Scheduler displays a panelasking you to confirm the deletion. Otherwise, CA-Scheduler deletes the stationimmediately.

5.5.1 Directory

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) RESOURCES - ROW 1 TO 3 OF 3


Station System Start End Average Route Class

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

_ 3� ��

_ 4� �� A

_ 4� XE87 ��


� �

Each station's resource definition is displayed on a single row. The upper right-handcorner of the panel displays the current range of rows and the total number of rows.

Select a station's resource definition by entering a letter to the left of the stationnumber. Enter:

S to select a resource definition for viewingE to edit (alter) a resource definitionD to delete a resource definition


5.5 Resources

5.5.2 Resource Definition

The same panels are used to display, edit, and define resources.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) RESOURCE -------------------

OPTION ===>

Station . . . Sysid/Substation . .

1 NON-SHARED - Resources dedicated to this Sysid/Substation

2 SHARED - Resources shared across this Station

Enter END to exit.

� �

Use option 1, NON-SHARED, to maintain resources for only the specified system(also called a substation). See the next topic for more information.

Use option 2, SHARED, to maintain resources for all systems at this station. See5.5.2.2, “Shared Resources” on page 5-89 for more information.

5-80 Online Guide

5.5 Resources

5.5.2.1 Nonshared Resources

The batch utility to use for maintaining nonshared resources is CAJUTIL0. The batchcommands for maintaining nonshared resources are:

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) RESOURCE -------------------

OPTION ===>

Station . . . 4� Sysid/Substation . .

1 DEFINITION - Times, Dasd, Tape, Unit Records

2 INIT/UNIT - Initiators or Units

Enter END to exit.

� �

Use option 1, DEFINITION, to maintain information about times, DASD and tapedevices, and other units.

Use option 2, INIT/UNIT, to maintain a list of initiators (for station 40) or units (forother than station 40).

Resource Definition Screens: The resource base information is contained onseveral panels. Use PF7 and PF8 to scroll up and down through the panels. To saveyour changes and exit, use PF3. To exit without saving your changes, enter CAN onthe command line.

Alter (Edit) ALTER RESOURCE

Define DEFINE RESOURCE

Delete DELETE RESOURCE

Display (View) N/A


5.5 Resources

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) RESOURCE --------------------

COMMAND ===>


Times:

Production Start . . . . �� (hhmm)

Production End . . . . . �� (hhmm)

Average Duration . . . . �� (ddhhmm)

Route Delay . . . . . . �� (ddhhmm)

Miscellaneous:

Default Class . . . . .

Simulation Exit Parm . .

Enter END to exit, or DOWN for next screen.

� �

The fields are:

StationThe station for which these resources may be used.

Size/Type: 2 numeric characters from 1-99Required: YesBatch Keyword: STation

Sysid/SubstationThe specific system within this station for which these resources may be used.This field is typically used in a multiple CPU environment on station 40 toidentify which devices are available on each system.

Size/Type: 1 to 4 alphanumeric charactersRequired: NoBatch Keyword: SYsidDefault: Blank

Production StartThe time of day, in hhmm format, that work normally begins for this station. Atypical value would be the autoscan time (CAIJGEN option AUTOTIM).

Size/Type: 4 numeric characters hhmmRequired: NoBatch Keyword: PStDefault: 0000 (midnight)

5-82 Online Guide

5.5 Resources

Production EndThe time of day, in hhmm format, that work normally ends for this station. Atypical value would be one minute before autoscan time.

Size/Type: 4 numeric characters hhmmRequired: NoBatch Keyword: PEtDefault: 0000 (midnight)

Average DurationA length of time to be used for jobs at this station that have never executed (thatis, have no history) and that do not have an Average Time specified on the job.

Size/Type: 6 numeric characters ddhhmmRequired: NoBatch Keyword: AVgtimeDefault: 000000

Route DelayA length of time to be added to the start of jobs that execute at a different node.

Size/Type: 6 numeric characters ddhhmmRequired: NoBatch Keyword: RdtDefault: 000000

Default ClassA class to be used for jobs that do not have a class defined.

Size/Type: 1 alphanumeric characterRequired: NoBatch Keyword: DEFclass

Simulation Exit ParmA character string that is passed to the simulation exit. See the Simulation Exit inthe Systems Programmer Guide for more information.


Press PF8 for the next screen. It is displayed only for CPU station resources (station40).


5.5 Resources

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) CPU RESOURCE ------------------

COMMAND ===>


Dasd: Type Count Type Count

Dasd �1 . . � Dasd �2 . . �

Dasd �3 . . � Dasd �4 . . �

Dasd �5 . . � Dasd �6 . . �

Dasd �7 . . � Dasd �8 . . �

Dasd �9 . . � Dasd 1� . . �

Dasd 11 . . � Dasd 12 . . �

Dasd 13 . . � Dasd 14 . . �

Dasd 15 . . � Dasd 16 . . �

Enter END to exit, UP for previous screen, or DOWN for next screen.

� �

The fields are:

Dasd 01 to Dasd 16Up to 16 different types of DASD may be defined, each with a type and count.The batch syntax for each is: DASDnn=(type,count) where nn is 01 to 16.

TypeThe type of DASD being defined. The type must match the Disk Type on the jobdefinition.

Size/Type: 1 to 8 alphanumeric charactersRequired: No, unless Count entered

CountThe number of the specified type of DASD available.

Size/Type: 1 to 3 numeric characters from 1-255Required: No, unless Type entered

Press PF8 for the next screen. It is displayed only for CPU station resources (station40).

5-84 Online Guide

5.5 Resources

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) CPU RESOURCE ------------------

COMMAND ===>


Tape: Type Count Type Count

Tape �1 . . � Tape �2 . . �

Tape �3 . . � Tape �4 . . �

Tape �5 . . � Tape �6 . . �

Tape �7 . . � Tape �8 . . �

Tape �9 . . � Tape 1� . . �

Tape 11 . . � Tape 12 . . �

Tape 13 . . � Tape 14 . . �

Tape 15 . . � Tape 16 . . �


� �

The fields are:

Tape 01 to Tape 16Up to 16 different types of tape drives may be defined, each with a type andcount. The batch syntax for each is: TAPEnn=(type,count) where nn is 01 to 16.

TypeThe type of tape drive being defined. The type must match the Tape Type on thejob definition.


CountThe number of the specified type of tape drive available.


Press PF8 for the next screen.


5.5 Resources

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) RESOURCE --------------------

COMMAND ===>


Unit Record: Type Count Type Count

Unit �1 . . � Unit �2 . . �

Unit �3 . . � Unit �4 . . �

Unit �5 . . � Unit �6 . . �

Unit �7 . . � Unit �8 . . �

Unit �9 . . � Unit 1� . . �

Unit 11 . . � Unit 12 . . �

Unit 13 . . � Unit 14 . . �

Unit 15 . . � Unit 16 . . �

Enter END to exit,or UP for previous screen.

� �

The fields are:

Unit 01 to Unit 16Up to 16 different types of unit records may be defined, each with a type andcount. The batch syntax for each is: URnn=(type,count) where nn is 01 to 16.

TypeThe type of unit record being defined. The type must match the Unit Type on thejob definition.


CountThe number of the specified type of unit record available.


To exit and save your changes, press PF3. To exit without saving, type CAN on thecommand line.

5-86 Online Guide

5.5 Resources

Resource Initiator

� � ---------------- CA-SCHEDULER 9.� xxyy (SCHD) INITIATORS/UNIT ROW 1 TO 4 OF 4


Station . . . 4� Sysid/Substation . .

Number Header Classes

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

��1 INIT1 AB

��2 INIT2 B

��3 INIT3 B

��5 INIT5 ASDF


� �

The fields are:

StationThe station for which the initiators are defined.

Size/Type: 2 numeric charactersRequired: YesBatch Keyword: STation

Sysid/SubstationThe specific system at this station for which the initiators are defined.

Size/Type: 1 to 4 alphanumeric charactersRequired: NoBatch Keyword: SYsidDefault: Blank

NumberThe number of the initiator. Each initiator must have a unique number from 1 to255.

Size/Type: 1 to 3 numeric charactersRequired: YesBatch Keyword: INITnnn=(classes,header), where nnn is 001 to 255

HeaderA label to use in the simulation reports as a name for this initiator.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: see Number

ClassesThe classes processed by this initiator. Up to 36 classes may be specified.

Size/Type: 1 to 36 alphanumeric charactersRequired: YesBatch Keyword: see Number


5.5 Resources

To change existing Header or Class information, simply overtype the information onthe panel. To add a new initiator, type an I on the command line or next to a number.To delete an initiator, type a D next to the number.

To exit and save your changes, press PF3. To exit without saving, type CAN on thecommand line.

5-88 Online Guide

5.5 Resources

5.5.2.2 Shared Resources

Several panels contain the shared resource definition information. Use PF7 and PF8 toscroll up and down through the panels. To save your changes and exit, use PF3. Toexit without saving your changes, enter CAN on the command line.

The batch utility to use for maintaining shared resources is CAJUTIL0. The batchcommands for maintaining shared resources are:

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) SHARED DASD ------------------

COMMAND ===>

Station . . .

Dasd: Type Count Systems

Dasd �1 . . �

Dasd �2 . . �

Dasd �3 . . �

Dasd �4 . . �

Dasd �5 . . �

Dasd �6 . . �

Dasd �7 . . �

Dasd �8 . . �

Dasd �9 . . �

Dasd 1� . . �

Dasd 11 . . �

Dasd 12 . . �

Dasd 13 . . �

Dasd 14 . . �

Dasd 15 . . �

Dasd 16 . . �

Enter END to exit, or DOWN for next screen.

� �

The fields are:

StationThe station for which the shared resource is defined.

Size/Type: 2 numeric charactersRequired: YesBatch Keyword: STation

Dasd 01 to Dasd 16Up to sixteen different types of DASD may be defined. Each DASD has a type(that is, 3390 or SYSDA), a count, and one to eight system IDs that may use it.The batch syntax is: DASDnn=(type,count,sysid,sysid,...) where nn is 01 to 16.

Alter (Edit) ALTER SHRRSR

Define DEFINE SHRRSR

Delete DELETE SHRRSR

Display (View) N/A


5.5 Resources

TypeThe type of DASD being defined. Typical values are 3390 or SYSDA.

Size/Type: 1 to 8 alphanumeric charactersRequired: No, unless Count enteredBatch Keyword: See Dasd 01 to Dasd 16

CountThe number of the specified type of DASD available.

Size/Type: 1 to 3 numeric characters from 1-255Required: No, unless Type enteredBatch Keyword: See Dasd 01 to Dasd 16

SystemsThe system IDs that may use the DASD device. If Type and Count are entered, atleast one system must be entered.

Size/Type: 1-4 alphanumeric characters specified from one to eight timesRequired: No, unless Type and Count enteredBatch Keyword: See Dasd 01 to Dasd 16


� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) SHARED TAPE ------------------

COMMAND ===>

Station . . .

Tape: Type Count Systems

Tape �1 . . �

Tape �2 . . �

Tape �3 . . �

Tape �4 . . �

Tape �5 . . �

Tape �6 . . �

Tape �7 . . �

Tape �8 . . �

Tape �9 . . �

Tape 1� . . �

Tape 11 . . �

Tape 12 . . �

Tape 13 . . �

Tape 14 . . �

Tape 15 . . �

Tape 16 . . �


� �

The fields are:

Tape 01 to Tape 16Up to sixteen different types of tape drives may be defined. Each tape drive has atype (that is, 3490 or CART), a count, and one to eight system IDs that may useit. The batch syntax is: TAPEnn=(type,count,sysid,sysid,...) where nn is 01 to 16.

5-90 Online Guide

5.5 Resources

TypeThe type of tape drive being defined. Typical values are 3490 or CART.

Size/Type: 1 to 8 alphanumeric charactersRequired: No, unless Count enteredBatch Keyword: See Tape 01 to Tape 16

CountThe number of the specified type of tape drive available.

Size/Type: 1 to 3 numeric characters from 1-255Required: No, unless Type enteredBatch Keyword: See Tape 01 to Tape 16

SystemsThe system IDs that may use the tape drive device. If Type and Count are entered,at least one system must be entered.

Size/Type: 1-4 alphanumeric characters specified from one to eight timesRequired: No, unless Type and Count enteredBatch Keyword: See Tape 01 to Tape 16


� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) SHARED UNITS ------------------

COMMAND ===>

Station . . .

Unit: Type Count Systems

Unit �1 . . �

Unit �2 . . �

Unit �3 . . �

Unit �4 . . �

Unit �5 . . �

Unit �6 . . �

Unit �7 . . �

Unit �8 . . �

Unit �9 . . �

Unit 1� . . �

Unit 11 . . �

Unit 12 . . �

Unit 13 . . �

Unit 14 . . �

Unit 15 . . �

Unit 16 . . �

Enter END to exit, or UP for previous screen.

� �

The fields are:

Unit 01 to Unit 16Up to sixteen different types of other units may be defined. Each other unit has atype, a count, and one to eight system IDs that may use it. The batch syntax is:

URnn=(type,count,sysid,sysid,...)

where nn is 01 to 16.


5.5 Resources

TypeThe type of other unit being defined.

Size/Type: 1 to 8 alphanumeric charactersRequired: No, unless Count enteredBatch Keyword: See Unit 01 to Unit 16

CountThe number of the specified type of other units available.

Size/Type: 1 to 3 numeric characters from 1-255Required: No, unless Type enteredBatch Keyword: See Unit 01 to Unit 16

SystemsThe system IDs that may use the other unit. If Type and Count are entered, atleast one system must be entered.

Size/Type: 1-4 alphanumeric characters specified from one to eight timesRequired: No, unless Type and Count enteredBatch Keyword: See Unit 01 to Unit 16


5.5.3.1 Example 1

Define initiators for a specific CPU.


//SYSIN DD �

DEFINE RESOURCE STATION=4�,SYSID=SYSA,INIT��1=(ABC,INIT1),

INIT��2=(ABC,INIT2),INIT��3=(C,INIT3)

//

5.5.3.2 Example 2

Define tape drives for all CPUs.


//SYSIN DD �

DEFINE SHRRSR STATION=4�,TAPE�1=(CART,15,SYSA,SYSB,SYSC)

//

5-92 Online Guide

5.6 Calendars

5.6 Calendars

You can use calendars to identify the days that a schedule or job is added to theworkload. A job or schedule that specifies a calendar is added to the workload everyworkday in the calendar.

Note: Date tables are much more flexible than calendars. Consider using date tablesinstead of calendars.

Two types of calendars exist: Normal and prototype. Prototype calendars are namedPROTOnn, where nn is the last two digits of the year. Normal calendars have anyother name.

When a normal calendar is created, CA-Scheduler checks for the existence of aprototype calendar for that year. If it is found, the workdays in the prototype calendarmay impact which days in the normal calendar are set as workdays.

Prototype calendars are defined with a flag of Next, Previous, or Drop for bothWeekly and Monthly calendars. When a normal calendar is being defined, and thespecified day in the prototype is not a workday, the prototype flag determines whataction is taken.

For example, a prototype calendar might have Monday, January 1 set as a holiday (nota workday) and have a weekly flag of Next. When a normal, weekly calendar is builtfor Mondays, January 2 would become a workday.

Option 6 of the CA-Scheduler Database menu displays the Calendar menu.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) CALENDARS -------------------

OPTION ===>

Calendar . . . .

Year . . . . . .

1 DIRECTORY - List of Calendars

2 DISPLAY - View an Existing Calendar

3 ALTER - Alter an Existing Calendar

4 DEFINE - Create a New Calendar

5 DELETE - Remove an Existing Calendar

6 COPY - Copy an Existing Calendar

Enter END to Exit.

� �

Use option 1, DIRECTORY, to display a list of calendars defined to CA-Scheduler.From the list you may Select (display), Edit, Delete, or Copy calendars.


5.6 Calendars

For options 2 to 6, you must enter the Calendar and Year.

Use option 2, DISPLAY, to view a specific calendar.

Use option 3, ALTER, to edit a specific calendar.

Use option 4, DEFINE, to create a new calendar.

Use option 5, DELETE, to remove a specific calendar. If you have requested theDelete Confirmation option (See Chapter 3, “Options”), CA-Scheduler displays a panelasking you to confirm the deletion. Otherwise, CA-Scheduler deletes the calendarimmediately.

Use option 6, COPY, to copy a calendar, creating a new one.

5.6.1 Directory

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) CALENDARS ROW 1 TO 19 OF 19


Name Year Description

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

_ CAL1 2��2

_ DAILY 2��3

_ FD 2��3

_ FOUR 2��3

_ FRI 2��3

_ FW 2��3

_ LD 2��3

_ LW 2��3

_ MON 2��3

_ NN 2��3

_ NNW 2��3

_ PROTO�3 2��3

_ SAT 2��3

_ SIX 2��3

_ SUN 2��3

_ THU 2��3

_ TUE 2��3

� �

Each calendar is displayed on a single row. The upper right-hand corner of the paneldisplays the current range of rows and the total number of rows. CA-Scheduler onlyreads the first 50 calendars before displaying the list. As you scroll down, more rowsare automatically added until the entire list has been built.

Select a calendar by entering a letter to the left of the calendar. Enter:

S to select a calendar for viewingE to edit (alter) a calendarC to copy a calendarD to delete a calendar

5-94 Online Guide

5.6 Calendars

5.6.2 Calendar Definition

Calendars may only be maintained online.

The following panel is displayed only when creating a new prototype calendar.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) CALENDAR --------------------

COMMAND ===>

Define Prototype Calendar:

Calendar . . . . . .

Year . . . . . . . .

Workdays per Week . . 5 (5, 6, 7, or �)

Prototype Options:

Weekly Roll Option . . . DROP (NEXT or PREVIOUS workday, or DROP)

Monthly Roll Option . . DROP (NEXT or PREVIOUS workday, or DROP)

Enter END to Exit.

� �

The fields are:

CalendarThe name of the prototype calendar being created. The name of all prototypecalendars is PROTOnn, where nn is the last two digits of the year.

Size/Type: 7, of the form PROTOnnRequired: Yes

YearThe year of the prototype calendar.

Size/Type: 4 numeric charactersRequired: Yes

WorkdaysThe number of days in a "normal" work week. Work weeks are assumed to starton Monday. A value of 5 sets all Mondays to Fridays as workdays; 6 sets allMondays to Saturdays; and 7 makes all days workdays. Individual days may beset to workdays or not after the calendar is defined.

Size/Type: 1 numeric character: 0, 5, 6, or 7Required: Yes


5.6 Calendars

Weekly Roll OptionDetermines what action to take when a normal weekly calendar tries to set aworkday on a day not specified as a workday in the prototype. If Drop isspecified, the day in the normal calendar is not set to a workday. If Next isspecified, the first workday in the prototype after the specified day is used. IfPrevious is specified, the first workday in the prototype before the specified day isused.

Size/Type: DROP, NEXT, or PREVIOUSRequired: Yes

Monthly Roll OptionDetermines what action to take when a normal monthly calendar tries to set aworkday on a day not specified as a workday in the prototype. If Drop isspecified, the day in the normal calendar is not set to a workday. If Next isspecified, the first workday in the prototype after the specified day is used. IfPrevious is specified, the first workday in the prototype before the specified day isused.

Size/Type: DROP, NEXT, or PREVIOUSRequired: Yes

The following panel is displayed only when creating a new normal calendar.


COMMAND ===>

Define Calendar:

Calendar . . . . . .

Year . . . . . . . .


Options:

Type of Calendar . . . DAILY (Daily, Weekly, or Monthly)

Day of Week/Month . . (Blank for Daily,

SUN - SAT or END for Weekly, or

one of the following for Monthly:

FD - first day of month

LD - last day of month

nn - nnth day of month

FW - first workday of month

LW - last workday of month

nnW - nnth workday of month

Enter END to Exit.

� �

The fields are:

CalendarThe name of the normal calendar being created.

Size/Type: 1 to 8 alphanumeric charactersRequired: Yes

5-96 Online Guide

5.6 Calendars

YearThe year of the normal calendar.


WorkdaysThe number of days in a "normal" work week. Work weeks are assumed to starton Monday. A value of 5 sets all Mondays to Fridays as workdays; 6 sets allMondays to Saturdays; and 7 makes all days workdays. Individual days may beset to workdays or not after the calendar is defined.

Size/Type: 1 numeric character: 0, 5, 6, or 7Required: Yes

Type of CalendarA normal calendar is one of three types: daily, weekly, or monthly. A dailycalendar sets every day in the normal work week as a workday (see Workdaysabove). If a prototype calendar exists, it is copied into the daily calendar. Aweekly calendar specifies a single day of each week to be a workday. A monthlycalendar specifies a single day of each month to be a workday. See Day ofWeek/Month below.

Size/Type: DAILY, WEEKLY, or MONTHLYRequired: Yes

Day of Week/MonthFor weekly and monthly calendars, determines the day of the week or month thatshould be set as a workday. Some values cause the prototype roll option to beignored.

For weekly calendars, valid values are:

Value Means Honors prototype roll option

SUN Sunday Yes

MON Monday Yes

TUE Tuesday Yes

WED Wednesday Yes

THU Thursday Yes

FRI Friday Yes

SAT Saturday Yes

END Weekend (both Saturday andSunday)

No


5.6 Calendars

For monthly calendars, valid values are:

Size/Type: FD, LD, 1-31, FW, LW, 1W-31WRequired: Yes

Other than the panels shown above, which are only used when a calendar is defined,the same panel is used to display, alter, and define calendars.


COMMAND ===>

Calendar . . . . .

Description . . . .

JANUARY 2�xx

Sunday Monday Tuesday Wednesday Thursday Friday Saturday

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

1 W 2 W 3 .

4 . 5 W 6 W 7 W 8 W 9 W 1� .

11 . 12 W 13 W 14 W 15 W 16 W 17 .

18 . 19 W 2� W 21 W 22 W 23 W 24 .

25 . 26 W 27 W 28 W 29 W 3� W 31 .

Legend:

W - Workday

Enter END to exit, UP for previous month, or DOWN for next month.

� �

Use PF7 and PF8 to scroll up and down through the months, or enter the first threecharacters of a month on the command line. To exit and save your changes, pressPF3. To exit without saving your changes, type CAN on the command line.

Value Means Honors prototype roll option

FD First day of month No

LD Last day of month No

1 - 31 day of the month No

FW First Workday Yes

LW Last Workday Yes

1W - 31W Workday of the month Yes

5-98 Online Guide

5.6 Calendars

The fields are:

CalendarThe name of the calendar being maintained. This field may not be modified.


DescriptionMay be used to describe the calendar or its purpose.


1 to 31The days of the month, along with their attribute. Days marked with a W areworkdays. Otherwise, they are not workdays.

5.6.3 Copying a Calendar

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) COPY CALENDAR -----------------

COMMAND ===>

Copy calendar

year

To Calendar

Year

Enter END to exit.

� �

The calendar you selected is listed in the Copy calendar fields. Enter the new calendarinformation in the To calendar fields.


5.7 Datetables

5.7 Datetables

CA-Scheduler date tables are used with criteria to determine when schedules and jobsshould be added to the workload. Criteria keywords such as WDAY and HDAY(workday and holiday) are resolved by inspecting the specified day in the date table.

Option 7 of the CA-Scheduler Database menu displays the Date Table menu.

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) DATETABLES -------------------

OPTION ===>

Datetable . . . . .

Accounting Code . .

Year . . . . . . .

1 DIRECTORY - List of Datetables

2 DISPLAY - View an Existing Datetable

3 ALTER - Alter an Existing Datetable

4 DEFINE - Create a New Datetable

5 DELETE - Remove an Existing Datetable

6 COPY - Copy an Existing Datetable

Enter END to Exit.

� �

Use option 1, DIRECTORY, to display a scrollable list of date tables defined toCA-Scheduler. You may enter a partial date table name in the Date Table field to limitthe display. From the list you may Select (display), Edit, Delete, or Copy date tables.

For options 2 to 6, you must enter the Date Table, Accounting Code, and Year.

Use option 2, DISPLAY, to view a specific date table.

Use option 3, ALTER, to edit a specific date table.

Use option 4, DEFINE, to create a new date table.

Use option 5, DELETE, to remove a specific date table. If you have requested theDelete Confirmation option (See Chapter 3, “Options”), CA-Scheduler displays a panelasking you to confirm the deletion. Otherwise, CA-Scheduler deletes the date tableimmediately.

Use option 6, COPY, to copy a date table, creating a new one.

5-100 Online Guide

5.7 Datetables

5.7.1 Directory

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) DATETABLES ROW 1 TO 18 OF 21


Name Code Year Description

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

_ DATETAB A 1994

_ DATETAB A 1995

_ DATETAB A 2��2


_ DATETAB A 1998

_ DATETAB A 1999

_ DATETAB A 2��



_ DATETAB B 1993

_ DATETAB B 1994

_ DATETAB B 1995

_ DATETAB B 2��2

_ DATETAB B 2��3

_ DATETAB B 1998

_ DT A 1993

_ DT A 1994

_ DT A 1995

� �

Each date table is displayed on a single row. The upper right-hand corner of the paneldisplays the current range of rows and the total number of rows. CA-Scheduler onlyreads the first 50 date tables before displaying the list. As you scroll down, more rowsare automatically added until the entire list has been built.

Select a date table by entering a letter to the left of the date table. Enter:

S to select a date table for viewingE to edit (alter) a date tableC to copy a date tableD to delete a date table


5.7 Datetables

5.7.2 Date Table Definition

Date tables may only be maintained online.

The following panel is displayed only when creating a new date table.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) DATETABLE -------------------

COMMAND ===>

Define Datetable:

Datetable . . . . . .

Accounting Code . . .

Year . . . . . . . .

Workdays per Week . . 5 (� to 7)

First Workday . . . . MON (SUN to SAT)

Enter END to Exit.

� �

The fields are:

DatetableThe name of the date table being maintained.


Accounting CodeThe one character prefix used by criteria keywords that should reference this table.The Accounting Code must be a letter.

Size/Type: 1 alphanumeric characterRequired: NoDefault: A

YearThe four-digit year of this date table.


5-102 Online Guide

5.7 Datetables

Workdays per WeekThe number of days in a "normal" work week. Work weeks start with the dayspecified in the First Workday field, which defaults to Monday. A value of zeroin this field does not set any days as work days. Individual days may be set towork days or not after the date table is defined.

Size/Type: 1 numeric character from 0 to 7Required: Yes

First WorkdayThe first day in a "normal" work week. A typical work week starts on Mondayand lasts for five days. To define a work week that starts on Sunday, change thisfield to SUN.

Size/Type: SUN, MON, TUE, WED, THU, FRI, or SATRequired: Yes

Press Enter to continue defining the date table.

Other than the panel shown above, which is used only when a date table is defined,the same panel is used to display, alter, and define date tables.


COMMAND ===>

Datetable . . . . . Accounting Code . .

Description . . . .

JANUARY 2�xx


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

1 WA.. 2 WA.. 3 WA.. 4 ....

5 .... 6 WA.. 7 WA.. 8 WA.. 9 WA.. 1� WA.. 11 ....

12 .... 13 WA.. 14 WA.. 15 WA.. 16 WA.. 17 WA.. 18 ....

19 .... 2� WA.. 21 WA.. 22 WA.. 23 WA.. 24 WA.. 25 ....

26 .... 27 WA.. 28 WA.. 29 WA.. 3� WA.. 31 WAM.

Legend:

W... - Workday

.A.. - Accounting Day

..M. - Month (Period) End

...Y - Year End

Enter END to exit, UP for previous month, or DOWN for next month.

� �

Use PF7 and PF8 to scroll up and down through the months, or enter the first threecharacters of a month on the command line. To exit and save your changes, press PF3.To exit without saving your changes, type CAN on the command line.


5.7 Datetables

The fields are:

DatetableThe name of the date table being manipulated. This field may not be modifiedafter the date table is defined.


Accounting CodeThe one character prefix used by criteria keywords that should reference this table.The Accounting Code must be a letter.

Size/Type: 1 alphanumeric characterRequired: NoDefault: A

DescriptionMay be used to describe the date table or its purpose.


1 to 31The days of the month, along with their attributes. Each day may have up to fourattributes:

WThe day is a workday. Criteria keywords such as WDAY and WDOMx willbe true. If the W attribute is not present, criteria keywords such as HDAY aretrue.

AThe day is an accounting day. Criteria keywords such as xDAY, where x isthe Accounting Code, are true. Note that the attribute for the day is always A,not the value of the Accounting Code.

MThe day is the last day of an accounting period. This is frequently used toindicate the end of the month. Criteria keywords such as ADOMx are countedfrom this day.

YThe day is the last day of the accounting year. Criteria keywords such asADOYx are counted from this day.

5-104 Online Guide

5.7 Datetables

5.7.3 Copying a Date Table

� � ----------------- CA-SCHEDULER 9.� xxyy (SCHD) COPY DATETABLE -----------------

COMMAND ===>

Copy datetable

accounting code

year

To Datetable

Accounting Code

Year

Enter END to exit.

� �

The date table you selected is listed in the Copy date table fields. Enter the new datetable information in the To Datetable fields.


5.8 Documentation

5.8 Documentation

Documentation is text entered by your site that may or may not be associated with ajob. You may enter a full or partial key, job and/or schedule name to limit the display.Text associated with a job is displayed on the OS/390 console at a specific time orwhen the job's schedule starts. See Documentation Display Key and Display Timefields on page 5-39.

Option 8 of the CA-Scheduler Database menu displays the Documentation menu.

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) DOCUMENTATION -----------------

OPTION ===>

Key . . . . .

Job . . . . .

Job Number. .

Station . . .

Schedule. . .

1 DIRECTORY - List of Documentation Members

2 DISPLAY - View an Existing Documentation Member

3 ALTER - Alter an Existing Documentation Member

4 DEFINE - Create a New Documentation Member

5 DELETE - Remove an Existing Documentation Member

6 COPY - Copy an Existing Documentation Member

Enter END to Exit.

� �

Use option 1, DIRECTORY, to display a scrollable list of documentation membersdefined to CA-Scheduler. From the list you may Select (display), Edit, Delete, or Copydocumentation members.

For options 2 to 6, you must enter the Key, Job, Job Number, Station, and Schedule.See below.

Use option 2, DISPLAY, to view a specific documentation member.

Use option 3, ALTER, to edit a specific documentation member.

Use option 4, DEFINE, to create a new documentation member.

Use option 5, DELETE, to remove a specific documentation member. If you haverequested the Delete Confirmation option (See Chapter 3, “Options”), CA-Schedulerdisplays a panel asking you to confirm the deletion. Otherwise, CA-Scheduler deletesthe documentation member immediately.

Use option 6, COPY, to copy a documentation member, creating a new one.

5-106 Online Guide

5.8 Documentation

The fields on the panel are:

KeyThe documentation key. Every documentation member must have a key.


JobIf the documentation member is to be displayed on the OS/390 console, it must bedefined with the name of the job with which it is associated.


Job NumberThe number of the associated job.

Size/Type: 2 numeric charactersRequired: Yes, if Job is used

StationThe station of the associated job.

Size/Type: 2 numeric charactersRequired: Yes, if Job is used

ScheduleThe schedule of the associated job.

Size/Type: 1 to 8 alphanumeric charactersRequired: Yes, if Job is used


5.8 Documentation

5.8.1 Directory

� � ------------------ CA-SCHEDULER 9.� xxyy (SCHD) DOCUMENTATI ROW 1 TO 18 OF 47


Key Job JNO St Schedule Date Time User

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

_ $$ A �1 4� CAJ7 �4/15/�3 �8.47.1� USER1�3

_ $$ B �1 4� CAJ7 �4/16/�3 �8.13.28 USER1�3

_ $$$ A 4� CAJ7 �9/1�/�2 15.12.31 USER1�3

_ A A �1 4� A �8/2�/�2 �9.12.51 USER1�3

_ A C �1 4� B �6/28/�2 �7.49.53 USER1�3

_ AAA AAA �1 4� ABTEST �9/�3/�2 12.39.�1 USER1�3

_ AB A �1 4� B 1�/11/�2 13.49.�9 USER1�3

_ ASDF ASDF �1 4� ASDF �5/�9/�2 14.52.�8 USER1�3

_ CA�7SVCT 4� �6/28/�2 �7.49.19 USER1�3

_ CHERICE 4� �8/22/95 1�.55.18

_ DBT1 4� �8/22/95 1�.55.19

_ DOCKEY CHRIS �1 4� CHRIS �8/19/�2 13.43.28 GEM

_ GAFRSDAY 4� �8/22/95 1�.55.19

_ GAFRSD�1 4� �8/22/95 1�.55.19

_ GAFRSD�2 4� �8/22/95 1�.55.19

_ GLC��1 4� �8/22/95 1�.55.19

_ GLC��3 4� �8/22/95 1�.55.19

_ GLC��4 4� �8/22/95 1�.55.19

� �

Each documentation member is displayed on a single row. The upper right-hand cornerof the panel displays the current range of rows and the total number of rows.CA-Scheduler only reads the first 50 documentation members before displaying thelist. As you scroll down, more rows are automatically added until the entire list hasbeen built.

Select a documentation member by entering a letter to the left of the key. Enter:

S to select a member for viewingE to edit (alter) a memberC to copy a memberD to delete a member

5.8.2 Documentation Text

When defining or editing a documentation member, ISPF Edit is used. Whendisplaying a member, ISPF Browse is used.

5-108 Online Guide

5.8 Documentation

5.8.3 Copying a Documentation Member

� � --------------- CA-SCHEDULER 9.� xxyy (SCHD) COPY DOCUMENTATION ---------------

COMMAND ===>

Copy doc

job

number

station

schedule

To doc

job

number

station

schedule

Enter END to exit.

� �

The documentation member you selected is listed in the Copy doc fields. Enter thenew member information in the To doc fields.


5.9 Flows

5.9 Flows

A flow identifies the starting and ending job of a job stream to be tracked by theCritical Path Monitor (CPM) system.

Option 9 of the CA-Scheduler Database menu displays the Flows menu.

� � ---------------------- CA-SCHEDULER 9.� xxyy (SCHD) FLOWS ---------------------

OPTION ===>

Flow . . . . .

1 DIRECTORY - List of Flows

2 DISPLAY - View an Existing Flow

3 ALTER - Alter an Existing Flow

4 DEFINE - Create a New Flow

5 DELETE - Remove an Existing Flow

6 REFRESH - Update the List of Flows in Storage

Enter END to Exit.

� �

Use option 1, DIRECTORY, to display a scrollable list of flows. You may enter apartial flow name in the Flow field to limit the display. From the list you may Select(display), Edit, and Delete flows.

For options 2 to 5, you must enter the Flow field.

Use option 2, DISPLAY, to view a specific flow.

Use option 3, ALTER, to edit an existing flow.

Use option 4, DEFINE, to create a new flow.

Use option 5, DELETE, to remove a specific flow. If you have requested the DeleteConfirmation option (see Chapter 3, “Options”), then a panel is displayed asking youto confirm the deletion. Otherwise, the flow is deleted immediately.

Use option 6, REFRESH, to issue a REFRESH FLOW command to the CA-Schedulerstarted task. CA-Scheduler must be active for the command to work.

5-110 Online Guide

5.9 Flows

5.9.1 Directory

� � ---------------------- CA-SCHEDULER 9.� xxyy (SCHD) FLOWS ---- Row 1 to 3 of 3


Flow From Job To Job SLA

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

_ FLOW1 FJOB1A �1 4� FLOWSCD1 FJOB1C �1 4� FLOWSCD1 ��18��

_ HOURLY PAY1 �1 4� PAYROLL OVERTIME �1 4� HOURLY ��15��

_ PAYROLL PAY1 �1 4� PAYROLL PAY99 �1 4� PAYCHECK ��5��


� �

Each flow is displayed on a single row. The upper right-hand corner of the paneldisplays the current range of rows and the total number of rows. CA-Scheduler onlyreads the first 50 flows before displaying the list. As you scroll down, more rows areautomatically added until the entire list has been built.

Select a flow by entering a letter to the left of the flow. Enter an:

S to select a flow for viewingE to edit (alter) a flowD to delete a flow

5.9.2 Flow Definition

The same panel is used to display, edit, and define flows. To save your changes andexit, use PF3. To exit without saving your changes, enter CAN on the command line.

The batch utility to use for maintaining flows is CAJUTIL0. The batch commands formaintaining flows are:

Flows are also displayed when either the starting or ending jobs are listed (LIST JOB,LIST SCHEDULE).

Alter (Edit) ALTER FLOW

Define DEFINE FLOW

Delete DELETE FLOW

Display (view) LIST FLOW


5.9 Flows

� � ---------------------- CA-SCHEDULER 9.� xxyy (SCHD) FLOW ----------------------

COMMAND ===>

Flow . . . . .

Beginning of flow:

Job . . . .

JNO . . . .

Station . .

Schedule . .

End of flow:

Job . . . .

JNO . . . .

Station . .

Schedule . .

Service Level Agreement . . . (ddhhmm)

Enter END to exit.

� �

The fields are:

FlowThe name of the flow being manipulated. The field may not be modified after theflow is defined.


Beginning of flow JobThe starting job name for this flow. The job must exist before the flow is defined.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: FJOb

Beginning of flow JNOThe JNO of the starting job for this flow.

Size/Type: 2 numeric charactersRequired: NoDefault: 01Batch Keyword: FJNo

Beginning of flow StationThe station of the starting job for this flow.

Size/Type: 2 numeric charactersRequired: NoDefault: 40Batch Keyword: FSTation

5-112 Online Guide

5.9 Flows

Beginning of flow ScheduleThe schedule to which the starting job for this flow belongs.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: FSChd

End of flow JobThe ending job name for this flow. The job must exist before the flow is defined.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: TJOb

End of flow JNOThe JNO of the ending job for this flow.

Size/Type: 2 numeric charactersRequired: NoDefault: 01Batch Keyword: TJNo

End of flow StationThe station of the ending job for this flow.

Size/Type: 2 numeric charactersRequired: NoDefault: 40Batch Keyword: TSTation

End of flow ScheduleThe schedule to which the ending job for this flow belongs.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: TSChd

Service Level AgreementThe time by which the flow must be complete. If CPM determines that the flowwill not end by this time, it considers the flow late.

The value is in the format of ddhhmm, where dd is the number of autoscans andhhmm is the time. Leading zeros do not need to be entered.

Size/Type: 1 to 6 numeric characters in ddhhmm formatRequired: YesBatch Keyword: SLA


5.9 Flows

5.9.3 Example

Define a flow from PAY1-01 40 PAYROLL to OVERTIME-01 40 HOURLY thatmust complete by 5:00 AM. Autoscan is at 8:00 AM.

//stepname EXEC CAJUTIL�

//SYSIN DD �

DEFINE FLOW NAME=PAYROLL,FJOB=PAY1,FJNO=�1,FST=4�,FSCHD=PAYROLL,

TJOB=OVERTIME,TJNO=�1,TST=4�,TSCHD=HOURLY,

SLA=5��

5-114 Online Guide

5.10 Virtual Resources


A virtual resource may be used to prevent jobs from being submitted unless certainconditions are met. Virtual resources only exist in the CA-Scheduler task. A virtualresource must be defined, then associated with one or more jobs.

Option A of the CA-Scheduler Database menu displays the VRM menu.

� �---------------- CA-SCHEDULER 9.� xxyy (SCHD) VIRTUAL RESOURCES ---------------

OPTION ===>

Virtual Resource . . .

1 DIRECTORY - List of Virtual Resources

2 DISPLAY - View an Existing Virtual Resource

3 ALTER - Alter an Existing Virtual Resource

4 DEFINE - Create a New Virtual Resource

5 DELETE - Remove an Existing Virtual Resource

6 REFRESH - Update the List of Virtual Resources in Storage

Enter END to Exit.

� �

Use option 1, DIRECTORY, to display a scrollable list of virtual resources. You mayenter a partial resource name in the Virtual Resource field to limit the display. Fromthe list you may Select (display), Edit, and Delete virtual resources. You may alsodisplay a list of jobs associated with a virtual resource.

For options 2 to 5, you must enter the Virtual Resource field.

Use option 2, DISPLAY, to view a specific virtual resource.

Use option 3, ALTER, to edit an existing virtual resource.

Use option 4, DEFINE, to create a new virtual resource.

Use option 5, DELETE, to remove a virtual resource. If you have requested the DeleteConfirmation option (see Chapter 3, “Options”), a panel is displayed asking you toconfirm the deletion. Otherwise, the virtual resource is deleted immediately.

Use option 6, REFRESH, to issue a REFRESH VRM command to the CA-Schedulerstarted task. CA-Scheduler must be active for the command to work.



5.10.1 Directory

� �----------------------- CA-SCHEDULER 9.� xxyy (SCHD) VRM ----- Row 1 to 3 of 3


Resource Type Count

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

_ XXX SIMPLE

_ YYY ENQ

_ ZZZ COUNT 5


� �

Each virtual resource is displayed on a single row. The upper right-hand corner of thepanel displays the current range of rows and the total number of rows. CA-Scheduleronly reads the first 50 virtual resources before displaying the list. As you scroll down,more rows are automatically added until the entire list has been built.

Select a virtual resource by entering a letter to the left of the virtual resource. Enter:

S to select the virtual resource for viewingE to edit (alter) a virtual resourceD to delete a virtual resourceJ to display a list of jobs associated with this virtual resource

5-116 Online Guide


5.10.2 Virtual Resource Definition

The same panel is used to display, edit, and define virtual resources. To save yourchanges and exit, use PF3. To exit without saving your changes, enter CAN on thecommand line.

The batch utility to use for maintaining virtual resources is CAJUTIL0. The batchcommands for maintaining virtual resources are:

Virtual resources are also displayed when an associated job is listed (LIST JOB, LISTSCHEDULE).

� �---------------- CA-SCHEDULER 9.� xxyy (SCHD) VIRTUAL RESOURCE ----------------

COMMAND ===>

Resource . . . . .

Resource Type . . . (Enq, Count, or Simple)

Maximum Count . . . (Only if resource type is Count)

Enter END to exit.

� �

The fields are:

ResourceThe name of the virtual resource being manipulated.


Alter (Edit) ALTER VRM

Define DEFINE VRM

DELETE DELETE VRM

Display (view) LIST VRM



Resource TypeThe type of the virtual resource being manipulated. The resource type may not bechanged once the virtual resource has been defined. Valid values are ENQ,COUNT, and SIMPLE. See the usage notes below for more information.

Size/Type: ENQ, COUNT, or SIMPLERequired: YesBatch Keyword: Type

Maximum CountIf Resource Type is set to COUNT, then the Maximum Count field contains thenumber of the virtual resource available.

Size/Type: 1 to 10 numeric charactersRequired: Yes, if Resource Type = COUNTBatch Keyword: Count

5.10.2.1 Example

Define a simple virtual resource to indicate if CICS is up or down:


//SYSIN DD �

DEFINE VRM NAME=CICS,TYPE=SIMPLE

5-118 Online Guide


5.10.3 VRM Job List

The VRM Job List dialog displays all of the jobs associated with a particular virtualresource. To display the list, enter a J next to a virtual resource on the virtual resourcedirectory display. See 5.10.1, “Directory” on page 5-116.

� �-------------------- CA-SCHEDULER 9.� xxyy (SCHD) VRM JOBS - Row 1 to 17 of 17


Jobs that require virtual resource XXX

Name JNO St Schedule Status Free

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

_ RESTEST2 �1 4� RESTEST2 ACTIVE NO

_ RT3�1 �1 4� RESTEST3 INACTIVE NO



_ RT3�4 �1 4� RESTEST3 ACTIVE NO












_ RT81� �1 4� RESTEST8 ACTIVE NO

� �

Each job/virtual resource association is displayed on a single row. The upperright-hand corner of the panel displays the current range of rows and the total numberof rows. CA-Scheduler only reads the first 50 job/virtual resource associations beforedisplaying the list. As you scroll down, more rows are automatically added until theentire list has been built.

Select a job/virtual resource association by entering a letter to the left of the job.Enter:

S to select the association for viewingE to edit (alter) an associationD to delete an associationI (or on the command line) to define a new association for this resource



5.10.4 Job/VRM Association

The same panel is used to display, edit, and define job/virtual resource associations. Tosave your changes and exit, use PF3. To exit without saving your changes, enter CANon the command line.

The batch utility to use for maintaining job/virtual resource associations is CAJUTIL0.The batch commands are:

� �--------------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB VRM --------------------

COMMAND ===>


Virtual Resource:

Resource . . .

Required Status:

Status . . . . . INACTIVE (ACTIVE or INACTIVE)

Termination:

Release on abend/fail . . . NO

Enter END to Exit.

� �

The fields are:

NameThe name of the job being associated with a virtual resource.


Alter (Edit) ALTER JOBRES

Define DEFINE JOBRES

Delete DELETE JOBRES

Display LIST JOB

5-120 Online Guide


JNOThe JNO of the job being associated with a virtual resource.

Size/Type: 2 numeric charactersRequired: NoBatch Keyword: JNoDefault: 01

StationThe station of the job being associated with a virtual resource.


ScheduleThe schedule of the job being associated with a virtual resource.


ResourceThe virtual resource being associated with this job.


Required StatusThe label and meaning of this field varies depending on the type of the virtualresource.

If the virtual resource was defined as TYPE=ENQ, then the label will readEnqueue. Valid values are SHR and EXC, indicating that the job may share thevirtual resource with other jobs, or needs exclusive control of the virtual resource.

Size/Type: SHR or EXCRequired: YesBatch Keyword: Enq

If the virtual resource was defined as TYPE=COUNT, then the label will readCount. Valid values are any number from 1 to 9,999,999,999. No check is madeto ensure that the number entered here is less than or equal to the numberavailable on the virtual resource.

Size/Type: 1 to 10 numeric charactersRequired: YesBatch Keyword: Count



If the virtual resource was defined as TYPE=SIMPLE, then the label reads Status.Valid values are ACTIVE and INACTIVE, indicating that the virtual resourcemust be active or inactive before the job may be submitted.

Size/Type: ACTIVE or INACTIVERequired: YesBatch Keyword: Active=YES|NO

Release on abend/failVirtual resources, once acquired by a job, are usually retained until the jobcompletes successfully. To release the virtual resource at any job end, even if thejob abends or fails, specify YES.

Size/Type: YES or NORequired: NoBatch Keyword: FreeDefault: NO

5.10.4.1 Example

Specify that a job may not be submitted unless a simple virtual resource called CICSis ACTIVE.


//SYSIN DD �

DEFINE JOBRES NAME=JOBA,S=SCHDA,RESOURCE=CICS,STATUS=ACTIVE

5.10.4.2 Usage Notes

Virtual resources may be used to control or limit job submission. The three types ofvirtual resources, ENQ, COUNT, and SIMPLE, are discussed in the following sections.

A job may have any number of virtual resources associated with it. All of the virtualresources must be satisfied before the job is submitted. Virtual resources are resolvedalphabetically. Each virtual resource must be obtained before the next virtual resourceis considered.

Virtual resources are obtained in a first-come, first-served manner.

Use the DISPLAY VRM command to view which jobs currently have or are waitingfor each virtual resource.

The REFRESH VRM command must be used (or wait for an autoscan) to pick up anydefinition changes to the virtual resources.

Note: Virtual resources are known only to CA-Scheduler.

5-122 Online Guide


5.10.4.3 ENQ Virtual Resources

A job may share an ENQ virtual resource with other jobs, or may require exclusivecontrol of the virtual resource.

For example, jobs JOBA, JOBB, JOBC, and JOBD all share the virtual resource X.JOBE requires exclusive control of X. This could be defined like this:


//SYSIN DD �

DEFINE VRM NAME=X,TYPE=ENQ

DEFINE JOBRES NAME=JOBA,S=SCHDA,RESOURCE=X,ENQ=SHR

DEFINE JOBRES NAME=JOBB,S=SCHDB,RESOURCE=X,ENQ=SHR

DEFINE JOBRES NAME=JOBC,S=SCHDC,RESOURCE=X,ENQ=SHR

DEFINE JOBRES NAME=JOBD,S=SCHDD,RESOURCE=X,ENQ=SHR

DEFINE JOBRES NAME=JOBE,S=SCHDE,RESOURCE=X,ENQ=EXC

If jobs JOBA and JOBB are the first jobs ready to be submitted, then they will be ableto obtain the virtual resource.

If job JOBE is the next job ready to be submitted, it must wait, because it can notobtain exclusive control of the virtual resource.

When jobs JOBC and JOBD are ready to be submitted, they must also wait because anexclusive use of the virtual resource is pending.

Once jobs JOBA and JOBB complete, JOBE will be submitted. Once JOBE completes,jobs JOBC and JOBD will be submitted.

Note: An OS/390 ENQ is never issued for ENQ virtual resources.



5.10.4.4 Count Virtual Resources

When virtual resources are defined with a type of COUNT, a number is specifiedindicating how many of the virtual resources are available.

When a job is associated with this virtual resource, a number is specified indicatinghow many of the virtual resources this job requires.

Consider the following example:


//SYSIN DD �

DEFINE VRM NAME=Y,TYPE=COUNT,COUNT=3

DEFINE JOBRES NAME=JOBA,S=SCHDA,RESOURCE=Y,COUNT=1

DEFINE JOBRES NAME=JOBB,S=SCHDB,RESOURCE=Y,COUNT=1

DEFINE JOBRES NAME=JOBC,S=SCHDC,RESOURCE=Y,COUNT=1

DEFINE JOBRES NAME=JOBD,S=SCHDD,RESOURCE=Y,COUNT=1

DEFINE JOBRES NAME=JOBE,S=SCHDE,RESOURCE=Y,COUNT=3

Any three of the jobs JOBA, JOBB, JOBC, and JOBD may be submitted at the sametime. JOBE, however, can only be submitted when no other job has the virtualresource.

Note that the order of requests for a count type virtual resource does not matter. IfJOBE was already waiting for this resource because JOBA already has the resource,and JOBD becomes available to be submitted, the resource will also be given toJOBD.

5.10.4.5 Simple Virtual Resources

A simple virtual resource is either active or inactive. The VARY VRM command isused to switch the state from active to inactive or back.


//SYSIN DD �

DEFINE VRM NAME=Z,TYPE=SIMPLE

DEFINE JOBRES NAME=JOBA,S=SCHDA,RESOURCE=Z,ACTIVE=YES

DEFINE JOBRES NAME=JOBB,S=SCHDB,RESOURCE=Z,ACTIVE=NO

//stepname EXEC CAJUCMD�<tab>

//SYSIN DD �

SC VARY VRM RESOURCE=Z,STATUS=ACTIVE

5-124 Online Guide

Chapter 6. Reports

Option 3 of the CA-Scheduler main menu displays the reports menu.

� �--------------------- CA-SCHEDULER 9.� xxyy (SCHD) REPORTS --------------------

OPTION ===>

1 ANALYZE - Look for logical definition errors

2 ABEND - Historical job abends

3 AUDIT - Audit trail of commands

4 COMPLETE - Historical job completions

5 DATETRAN - Criteria keywords for a given date

7 JOB AVERAGE - Historical job durations

8 JOB HISTORY - Historical information on jobs

9 MAILBOX - Historical information on events

1� OPTIONS - CA-Scheduler installation options

11 SUCCESSOR - Job and Schedule successors

12 PREDECESSOR - Job and Schedule predecessors

Enter END to Exit.

� �

Use option 1, ANALYZE, to inspect schedules and jobs for logical errors, such aspredecessor loops (deadlocks). See 6.1, “Analyze” on page 6-3 for more information.

Use option 2, ABEND, to list jobs from CA-Scheduler's history information thatabended. See 6.2, “Report Abend” on page 6-8 for more information.

| Use option 3, AUDIT, to list CA-Scheduler commands that have been issued and| saved in the audit trail. See 6.3, “Report Audit” on page 6-10 for more information.

Use option 4, COMPLETE, to list jobs from CA-Scheduler's history information thathave completed. See 6.4, “Report Complete” on page 6-12 for more information.

Use option 5, DATETRAN, to generate a list of criteria keywords that are true for aspecified date. See 6.5, “Report Datetran” on page 6-14 for more information.

Use option 7, JOB AVERAGE, to list average execution times for jobs inCA-Scheduler's history. See 6.6, “Job Average” on page 6-16 for more information.

Chapter 6. Reports 6-1

Use option 8, JOB HISTORY, to list up to the last seven executions of jobs inCA-Scheduler's history. See 6.7, “Job History” on page 6-17 for more information.

| Use option 9, MAILBOX, to list events (such as job start and end) that have been| written to the mailbox. See 6.8, “Report Mailbox” on page 6-18 for more information.

Use option 10, OPTIONS, to display all CA-Scheduler installation options. See 6.9,“Report Options” on page 6-20 for more information.

Use option 11, SUCCESSOR, to show successors to a given job or schedule. See 6.10,“Successors” on page 6-21 for more information.

Use option 12, PREDECESSOR, to show predecessors to a given job or schedule. See6.11, “Predecessors” on page 6-30 for more information.

6-2 Online Guide

6.1 Analyze

6.1 Analyze

Option 1 of the CA-Scheduler Reports menu displays the Analyze menu.

The Analyze commands inspect jobs and schedules for logical errors, such aspredecessor loops (deadlocks).

� � --------------------- CA-SCHEDULER 9.� xxyy (SCHD) ANALYZE --------------------

OPTION ===>

1 JOB - Analyze a Job

2 SCHEDULE - Analyze a Schedule

Enter END to exit.

� �

Use option 1, JOB, to inspect a specific job or jobs starting with the same prefix. Seethe next topic for more information.

Use option 2, SCHEDULE, to inspect a specific schedule or schedules with the sameprefix. All jobs in the selected schedules are also analyzed. See 6.1.2, “AnalyzeSchedule” on page 6-6 for more information.


6.1 Analyze

6.1.1 Analyze Job

Option 1 of the CA-Scheduler Analyze menu displays the Analyze Job dialog.

The Analyze Job command inspects one or more jobs for logical errors, such aspredecessor loops (deadlocks).

The batch utility to use is CAJUTIL0. The batch command is ANALYZE JOB.

� �------------------- CA-SCHEDULER 9.� xxyy (SCHD) ANALYZE JOB ------------------

COMMAND ===>

Job:

Job Name . . . .

Schedule . . . .

Options:

List . . . . . . ERR (YES, NO, ERR, DEADLOCK)

Date . . . . . . (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy)

Enter END to exit.

� �

The fields are:

Job NameThe name of the job or job name prefix to be inspected. A job name prefix maybe specified by following the prefix with an asterisk. All job numbers and stationsfor selected jobs will be analyzed.


ScheduleThe schedule or schedule prefix that contains the job(s) to be analyzed.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ScheduleDefault: * (All schedules)

6-4 Online Guide

6.1 Analyze

ListDetermines the amount of information produced by the report. The default valueis determined by the Default Analyze List Type option. See Chapter 3, “Options”on page 3-1. Valid values are:

YESAll information about analyzed jobs is displayed.

NOOnly job names are displayed, along with any errors.

ERROnly jobs with errors are displayed.

DEADLOCKOnly deadlocks and the deadlock path are displayed.

Required: NoBatch Keyword: ListDefault: YES

DateIf a date is entered, ANALYZE will emulate autoscan for that date. Deadlockswill only be reported if autoscan would have detected them. If Date is notspecified, all schedules and jobs are considered selected, regardless of theirindividual criterias.

Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyyRequired: NoBatch Keyword: DateDefault: Blank


6.1 Analyze

6.1.2 Analyze Schedule

Option 2 of the CA-Scheduler Analyze menu displays the Analyze Schedule dialog.

The Analyze Schedule command inspects one or more schedules for logical errors,such as predecessor loops (deadlocks). All jobs in the selected schedules are alsoinspected.

The batch utility to use is CAJUTIL0. The batch command is ANALYZESCHEDULE.

� �---------------- CA-SCHEDULER 9.� xxyy (SCHD) ANALYZE SCHEDULE ----------------

COMMAND ===>

Schedule:

Schedule Name . .

Options:

List . . . . . . ERR (YES, NO, ERR, DEADLOCK)

Date . . . . . . (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy)

Enter END to exit.

� �

The fields are:

ScheduleThe name of the schedule or schedule prefix to be inspected. Specify a scheduleprefix by following the prefix with an asterisk. CA-Scheduler analyzes all jobs inthe selected schedules.


ListDetermines the amount of information produced by the report. The default value isdetermined by the Default Analyze List Type option. See Chapter 3, “Options” onpage 3-1. Valid values are:

YESAll information about analyzed schedules and jobs is displayed.

NOOnly schedule and job names are displayed, along with any errors.

6-6 Online Guide

6.1 Analyze

ERROnly schedules and jobs with errors are displayed.

DEADLOCKOnly deadlocks and the deadlock path are displayed.

Required: NoBatch Keyword: ListDefault: YES

DateIf you enter a date, ANALYZE emulates autoscan for that date. Deadlocks arereported only if autoscan would have detected them. If you do not specify a date,all schedules and jobs are considered selected, regardless of their individualcriterias.

Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyyRequired: NoBatch Keyword: DateDefault: Blank


6.2 Report Abend

6.2 Report Abend

Option 2 of the CA-Scheduler Reports menu displays the Report Abend dialog.

The Report Abend command lists jobs in CA-Scheduler history information that endedabnormally.

Do not confuse the Report Abend command with the Status Abend command, whichlists abended jobs in the current workload.

The batch utility to use is CAJUTIL0. The batch command is REPORT ABEND.

� �------------------ CA-SCHEDULER 9.� xxyy (SCHD) REPORT ABEND ------------------

COMMAND ===>

Job:

Job Name . . . .

Schedule . . . .

Options:

Starting Date . . . (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy)

Starting Time . . . (hhmm)

Duration . . . . . (days)

Scheduled On . . . (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy)

Enter END to exit.

� �

The fields are:

Job NameThe name or name prefix of the job for which historical abends should be listed.Specify a name prefix by following the prefix with an asterisk. CA-Scheduler listsall job numbers of selected jobs.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: JobDefault: * (All jobs)

6-8 Online Guide

6.2 Report Abend

ScheduleThe name or name prefix of the schedule that contains the Job Name. Specify aname prefix by following the prefix with an asterisk.


Starting DateIf entered, lists no abends occurring prior to this date.

Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyyRequired: NoBatch Keyword: FROMDate or FDDefault: Current autoscan date

Starting TimeIf entered, lists no abends occurring prior to this time.

Size/Type: hhmmRequired: NoBatch Keyword: FROMTime or FTDefault: Normal autoscan time

DurationIf entered, lists no abends occurring at least this many days after the Starting Date.

Size/Type: 1 to 3 numeric charactersRequired: NoBatch Keyword: FORDefault: 1

Scheduled onLists only abended jobs selected on this date. If you specify Scheduled on,CA-Scheduler ignores Starting Date.

Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyyRequired: NoBatch Keyword: SDATE


6.3 Report Audit

6.3 Report Audit

Option 3 of the CA-Scheduler Reports menu displays the Report Audit dialog.

| The Report Audit command lists CA-Scheduler commands issued and recorded in the| audit trail.

| CA-Scheduler displays only commands recorded in the audit trail. Typically, only| update (DEFINE, RUN, and so on) commands are saved. Display commands| (REPORT, ANALYZE, and so on) are normally not recorded to the audit trail.

| Information in the audit trail is kept until deleted by the DELETE AUDIT command.

The batch utility to use is CAJUTIL0. The batch command is REPORT AUDIT.

� �------------------ CA-SCHEDULER 9.� xxyy (SCHD) REPORT AUDIT ------------------

COMMAND ===>

Options:



Ending Date . . . . (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy)

Ending Time . . . . (hhmm)

Commands . . . . . . . . . . .

. . . . . .

. . . . . .

. . . . . .

Users . . . . . . . . . . . . .

. . . . . .

. . . . . .

. . . . . .

Enter END to exit.

� �

The fields are:

Starting DateThe earliest date from which commands should be displayed.

Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyyRequired: NoBatch Keyword: FDDefault: Today's date

6-10 Online Guide

6.3 Report Audit

Starting TimeThe earliest time on the Starting Date from which commands should be displayed.

Size/Type: hhmmRequired: NoBatch Keyword: FTDefault: Midnight

Ending DateThe latest date from which commands should be displayed.

Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyyRequired: NoBatch Keyword: TDDefault: Today's date

Ending TimeThe latest time on the Ending Date from which commands should be displayed.

Size/Type: hhmmRequired: NoBatch Keyword: TTDefault: 2359

CommandsIf specified, only commands that match one of the sixteen commands listed aredisplayed.

Size/Type: One to sixteen 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: CMD=(command,command,...)Default: All commands

UsersIf specified, only commands entered by one of the sixteen users listed aredisplayed.

Size/Type: One to sixteen 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: USER=(userid,userid,...)Default: All users


6.4 Report Complete

6.4 Report Complete

Option 4 of the CA-Scheduler Reports menu displays the Report Complete dialog.

The Report Complete command lists jobs in CA-Scheduler history information thatended normally.

Do not confuse the Report Complete command with the Status Comp command, whichlists completed jobs in the current workload.

The batch utility to use is CAJUTIL0. The batch command is REPORT COMPLETE.

� �----------------- CA-SCHEDULER 9.� xxyy (SCHD) REPORT COMPLETE ----------------

COMMAND ===>

Job:

Job Name . . . .

Schedule . . . .

Options:




Scheduled On . . . (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy)

Enter END to exit.

� �

The fields are:

Job NameThe name or name prefix of the job for which historical job completions you wantto list. Specify a name prefix by following the prefix with an asterisk.CA-Scheduler lists all job numbers and stations of selected jobs.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: JobDefault: * (All jobs)

6-12 Online Guide

6.4 Report Complete

ScheduleThe name or name prefix of the schedule that contains the Job Name. Specify aname prefix by following the prefix with an asterisk.


Starting DateIf entered, lists no completions occurring prior to this date.

Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyyRequired: NoBatch Keyword: FROMDate or FDDefault: Current autoscan date

Starting TimeIf entered, lists no completions occurring prior to this time.

Size/Type: hhmmRequired: NoBatch Keyword: FROMTime or FTDefault: Normal autoscan time

DurationIf entered, lists no completions occurring at least this many days after the StartingDate.


Scheduled onLists only completed jobs selected on this date. If you specify Scheduled on,CA-Scheduler ignores Starting Date.

Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyyRequired: NoBatch Keyword: SDATE


6.5 Report Datetran

6.5 Report Datetran

Option 5 of the CA-Scheduler Reports menu displays the Report Datetran dialog.

The Report Datetran command lists criteria keywords that are true for a specified date.

The batch utility to use is CAJUTIL0. The batch command is REPORT DATETRAN.

� �----------------- CA-SCHEDULER 9.� xxyy (SCHD) REPORT DATETRAN ----------------

COMMAND ===>

Date Table:

Date Table . . .

In Schedule . .

In Job . . . . .

Options:



Enter END to exit.

� �

The fields are:

Date TableThe name of the date table to use in generating criteria keywords. If the DateTable, In Schedule, and In Job fields are blank, CA-Scheduler uses the defaultDate Table (CAIJGEN DATETAB option). If you specify Date Table,CA-Scheduler ignores In Schedule and In Job.

Size/Type: 1 to 7 alphanumeric charactersRequired: NoBatch Keyword: TableDefault: CAIJGEN DATETAB value

6-14 Online Guide

6.5 Report Datetran

In ScheduleUse the date table specified in this schedule. If you specify Date Table,CA-Scheduler ignores In Schedule. If you specify In Schedule, CA-Schedulerignores In Job.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ScheduleDefault: Date Table value

In JobUse the date table specified on the schedule that owns this job. If you specifyeither Date Table or In Schedule, CA-Scheduler ignores In Job.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: JobDefault: Date Table or In Schedule value

Starting DateThe date for which criteria keywords should be generated.

Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyyRequired: NoBatch Keyword: FROMDate or FDDefault: Today

DurationThe number of days for which criteria keywords should be listed.



6.6 Job Average

6.6 Job Average

Option 7 of the CA-Scheduler Reports menu displays the Job Average dialog.

The Job Average command displays average execution time for jobs based onCA-Scheduler historical information.

The batch utility to use is CAJUTIL0. The batch command is REPORT JOBAVG.

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB AVERAGE ------------------

COMMAND ===>

Job:

Job Name . . . .

Enter END to exit.

� �

The field is:

Job NameThe name or name prefix of the job for which average execution informationshould be displayed. Specify a name prefix by entering an asterisk after the prefix.The list includes all job numbers and stations for selected jobs.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: NameDefault: * (All jobs)

6-16 Online Guide

6.7 Job History

6.7 Job History

Option 8 of the CA-Scheduler Reports menu displays the Job History dialog.

The Job History command lists information about up to seven previous executions ofjobs.

The batch utility to use is CAJUTIL0. The batch command is REPORT JOBHIST.

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) JOB HISTORY ------------------

COMMAND ===>

Job:

Job Name . . . .

Options:

List . . . JESNUM (Jesnum or Year)

Enter END to exit.

� �

The fields are:

Job NameThe name or name prefix of the jobs for which execution history should bedisplayed. Specify a name prefix by entering an asterisk after the prefix.

Size/Type: 1 to 8 alphanumeric charactersRequired: YesBatch Keyword: NameDefault: * (All jobs)

ListSpecify JESNUM to display the JES job number with which the job executed.Dates are displayed as MM/DD. Specify YEAR to display dates as MM/DD/YY.The JES job number is not displayed.

Size/Type: JESNUM or YEARRequired: NoBatch Keyword: ListDefault: JESNUM


6.8 Report Mailbox

6.8 Report Mailbox

Option 9 of the CA-Scheduler Reports menu displays the Report Mailbox dialog.

| The Report Mailbox command lists events (such as job start and end) that have been| saved for the MAILBOX report.

| Only events that are issued for the MAILBOX report are displayed. Typically, the| following events are available:

| ■ Job and Schedule starts

| ■ Job and Schedule completions

| ■ Jobs and Schedules being marked late

| ■ Job failures (JCL error, submit fail, bad return code)

| ■ Job abends

| ■ Jobs being marked interrupted

| ■ Jobs being purged from JES

| Mailbox information is kept until deleted by the DELETE MAILBOX command.

The batch utility to use is CAJUTIL0. The batch command is REPORT MAILBOX.

� �----------------- CA-SCHEDULER 9.� xxyy (SCHD) REPORT MAILBOX -----------------

COMMAND ===>

Options:



Ending Date . . . . (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy)

Ending Time . . . . (hhmm)

Jobs . . . . . . . . . . . . .

. . . . . .

. . . . . .

. . . . . .

Schedules . . . . . . . . . . .

. . . . . .

. . . . . .

. . . . . .

Enter END to exit.

� �

6-18 Online Guide

6.8 Report Mailbox

The fields are:

Starting DateThe earliest date for which events should be displayed.

Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyyRequired: NoBatch Keyword: FROMDate or FDDefault: Today

Starting TimeThe earliest time on the Starting Date for which events should be displayed.

Size/Type: hhmmRequired: NoBatch Keyword: FTDefault: Midnight

Ending DateThe latest date for which events should be displayed.

Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyyRequired: NoBatch Keyword: TODate or TDDefault: Today

Ending TimeThe latest time on the Ending Date for which events should be displayed.

Size/Type: hhmmRequired: NoBatch Keyword: TTDefault: 2359

JobsIf specified, only events for these sixteen jobs are displayed.

Size/Type: One to sixteen 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: Job=(jobname,jobname,...)Default: All jobs

SchedulesIf specified, only events for these sixteen schedules or for jobs in these schedulesare displayed.

Size/Type: One to sixteen 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: Schedule=(schedule,schedule,...)Default: All schedules


6.9 Report Options

6.9 Report Options

Option 10 of the CA-Scheduler Reports menu issues the Report Options command.

The Report Options command displays all of the CA-Scheduler installation optionscurrently set. Since the command has no keywords, a prompting panel is not displayed.

The batch utility to use is CAJUTIL0. The batch command is REPORT OPTIONS.

6-20 Online Guide

6.10 Successors

6.10 Successors

Option 11 of the CA-Scheduler Reports menu displays the Successor menu.

The Successor menu lists successors of jobs and schedules.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) SUCCESSOR -------------------

OPTION ===>

1 JOBCHAIN - Successors of a Job

2 SCDCHAIN - Successors of a Schedule

3 CJOBCHAN - Successors of a Job in the Current Workload

4 CSCDCHAN - Successors of a Schedule in the Current Workload

Enter END to exit.

� �

Use option 1, JOBCHAIN, to generate a list of successors defined to a specific job inthe database. See the next topic for more information.

Use option 2, SCDCHAIN, to generate a list of successors defined to a specificschedule in the database. See 6.10.2, “Scdchain” on page 6-24 for more information.

Use option 3, CJOBCHAN, to generate a list of successors in the current workload toa specific job. See 6.10.3, “Cjobchan” on page 6-26 for more information.

Use option 4, CSCDCHAN, to generate a list of successors in the current workload toa specific schedule. See 6.10.4, “Cscdchan” on page 6-28 for more information.


6.10 Successors

6.10.1 Jobchain

Option 1 of the CA-Scheduler Successor menu displays the Jobchain dialog.

The Jobchain command lists successors of a specific job as defined in theCA-Scheduler database.

The batch utility to use is CAJUTIL0. The batch command is REPORT JOBCHAIN.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) JOBCHAIN --------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

Options:

Level . . . . .

Repeat . . . . . YES

Date . . . . . .

Enter END to exit.

� �

The fields are:

Job NameThe job from which the successor list should start.


NumberThe job number of the starting job.

Size/Type: 1 to 2 numeric charactersRequired: NoBatch Keyword: JNODefault: 01

StationThe station of the starting job.


6-22 Online Guide

6.10 Successors

ScheduleThe schedule of the starting job.

Size/Type: 1 to 8 alphanumeric charactersRequired: NoBatch Keyword: ScheduleDefault: The first schedule that contains the specified job

LevelHow many levels deep the successor report should go. For example, if JOBA'ssuccessor is JOBB, and JOBB's successor is JOBC, two levels are required toreach JOBC.

Size/Type: 1 to 3 numeric charactersRequired: NoBatch Keyword: LevelDefault: All successors

RepeatSpecify NO to prevent already displayed successors from displaying again whenmultiple successor paths reach the same point. For example, if JOBA's successorsare JOBB and JOBC, and JOBB's and JOBC's successor is JOBD, specifying NOfor REPEAT will only display JOBD's successors once.

Size/Type: Yes or noRequired: NoBatch Keyword: RepeatDefault: YES

DateIf entered, only successors selected on the specified date are shown.

Size/Type: 1 to 6 numeric character date, 1 to 8 numeric character date,TODAY, or AUTOS

Required: NoBatch Keyword: Date


6.10 Successors

6.10.2 Scdchain

Option 2 of the CA-Scheduler Successor menu displays the Scdchain dialog.

The Scdchain command lists successors of a specific schedule as defined in theCA-Scheduler database.

The batch utility to use is CAJUTIL0. The batch command is REPORT SCDCHAIN.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) SCDCHAIN --------------------

COMMAND ===>

Schedule:

Schedule . . . .

Options:

Level . . . . .


Date . . . . . .

Enter END to exit.

� �

The fields are:

ScheduleThe name of the starting schedule.




6-24 Online Guide

6.10 Successors


Size/Type: Yes or noRequired: NoBatch Keyword: RepeatDefault: Yes

DateIf entered, only successors selected on the specified date are shown.




6.10 Successors

6.10.3 Cjobchan

Option 3 of the CA-Scheduler Successor menu displays the Cjobchan dialog.

The Cjobchan command lists successors of a specific job that is in the currentworkload.

The batch utility to use is CAJUTIL0. The batch command is REPORT CJOBCHAN.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) CJOBCHAN --------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

Options:

Level . . . . .


Enter END to exit.

� �

The fields are:

Job NameThe job from which the successor list should start.






6-26 Online Guide

6.10 Successors








6.10 Successors

6.10.4 Cscdchan

Option 4 of the CA-Scheduler Successor menu displays the Cscdchan dialog.

The Cscdchan command lists successors of a specific schedule that is in the currentworkload.

The batch utility to use is CAJUTIL0. The batch command is REPORT CSCDCHAN.

� � -------------------- CA-SCHEDULER 9.� xxyy (SCHD) CSCDCHAN --------------------

COMMAND ===>

Schedule:

Schedule Name . .

Options:

Level . . . . . .


Enter END to exit.

� �

The fields are:





6-28 Online Guide

6.10 Successors




6.11 Predecessors

6.11 Predecessors

Option 12 of the CA-Scheduler Reports menu displays the Predecessor menu.

The Predecessor menu lists predecessors of jobs and schedules.

� �------------------ CA-SCHEDULER 9.� xxyy (SCHD) PREDECESSORS ------------------

OPTION ===>

1 JOBRCHAN - Predecessors of a Job

2 SCDRCHAN - Predecessors of a Schedule

3 CJOBRCHN - Predecessors of a Job in the Current Workload

4 CSCDRCHN - Predecessors of a Schedule in the Current Workload

Enter END to exit.

� �

Use option 1, JOBRCHAN, to generate a list of predecessors defined to a specific jobin the database. See the next topic for more information.

Use option 2, SCDRCHAN, to generate a list of predecessors defined to a specificschedule in the database. See 6.11.2, “Scdrchan” on page 6-33 for more information.

Use option 3, JOBRCHAN, to generate a list of predecessors in the current workloadto a specific job. See 6.11.3, “Cjobrchn” on page 6-35 for more information.

Use option 4, CSCDRCHN, to generate a list of predecessors in the current workloadto a specific schedule. See 6.11.4, “Cscdrchn” on page 6-37 for more information.

6-30 Online Guide

6.11 Predecessors

6.11.1 Jobrchan

Option 1 of the CA-Scheduler Predecessor menu displays the Jobrchan dialog.

The Jobrchan command lists predecessors of a specific job as defined in theCA-Scheduler database.

The batch utility to use is CAJUTIL0. The batch command is REPORT JOBRCHAN.

� � ------------------- CA-SCHEDULER 9.� xxyy (SCHD) JOBRCHAN --------------------

COMMAND ===>

Job:

Job Name . . . .

Number . . . . . �1

Station . . . . 4�

Schedule . . . .

Options:

Level . . . . .


Date . . . . . .

Enter END to exit.

� �

The fields are:

Job NameThe job from which the predecessor list should start.







6.11 Predecessors



LevelHow many levels deep the predecessor report should go. For example, if JOBA'spredecessor is JOBB, and JOBB's predecessor is JOBC, two levels are required toreach JOBC.

Size/Type: 1 to 3 numeric charactersRequired: NoBatch Keyword: LevelDefault: All predecessors

RepeatSpecify NO to prevent already displayed predecessors from displaying again whenmultiple predecessor paths reach the same point. For example, if JOBA'spredecessors are JOBB and JOBC, and JOBB's and JOBC's predecessor is JOBD,specifying NO for REPEAT will only display JOBD's predecessors once.

Size/Type: Yes or noRequired: NoBatch Keyword: RepeatDefault: YES

DateIf entered, only predecessors selected on the specified date are shown.



6-32 Online Guide

6.11 Predecessors

6.11.2 Scdrchan

Option 2 of the CA-Scheduler Predecessor menu displays the Scdrchan dialog.

The Scdrchan command lists predecessors of a specific schedule as defined in theCA-Scheduler database.

The batch utility to use is CAJUTIL0. The batch command is REPORT SCDRCHAN.

� �-------------------- CA-SCHEDULER 9.� xxyy (SCHD) SCDRCHAN --------------------

COMMAND ===>

Schedule:

Schedule . . . .

Options:

Level . . . . .


Date . . . . . .

Enter END to exit.

� �

The fields are:






6.11 Predecessors



DateIf entered, only predecessors selected on the specified date are shown.



6-34 Online Guide

6.11 Predecessors

6.11.3 Cjobrchn

Option 3 of the CA-Scheduler Predecessor menu displays the Cjobrchn dialog.

The Cjobrchn command lists predecessors of a specific job that is in the currentworkload.

The batch utility to use is CAJUTIL0. The batch command is REPORT CJOBRCHN.

� �-------------------- CA-SCHEDULER 9.� xxyy (SCHD) CJOBRCHN --------------------

COMMAND ===>

Schedule:

Schedule . . . .

Options:

Level . . . . .


Enter END to exit.

� �

The fields are:

Job NameThe job from which the predecessor list should start.







6.11 Predecessors







6-36 Online Guide

6.11 Predecessors

6.11.4 Cscdrchn

Option 4 of the CA-Scheduler Predecessor menu displays the Cscdrchn dialog.

The Cscdrchn command lists predecessors of a specific schedule that is in the currentworkload.

The batch utility to use is CAJUTIL0. The batch command is REPORT CSCDRCHN.

� �-------------------- CA-SCHEDULER 9.� xxyy (SCHD) CSCDRCHN --------------------

COMMAND ===>

Schedule:

Schedule Name . .

Options:

Level . . . . . .


Enter END to exit.

� �

The fields are:






6.11 Predecessors



6-38 Online Guide

Chapter 7. 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 a schedule orjob for execution and for establishing its predecessors.

For example, if SCHEDA is to run every Monday and every Thursday, the selectioncriteria associated with this schedule is MON OR THU.

This example uses criteria vocabulary that refers to a processing period when selectinga schedule. Several different types of processing periods can be used:

■ Day of week (as above)

■ 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 be anotherschedule or job being selected. For example, to select JOBB if JOBA was selected, thecriteria associated with JOBB is JOBA.

So far, we have discussed using the criteria vocabulary to select schedules or jobs. Butthe criteria vocabulary is also used for defining predecessors. Predecessors areconditions that have to be met before a schedule or job is allowed to start. Other termsused for predecessor are prerequisite and dependency.

Note: This topic has many examples that use 'JOBA' in criteria for simplicity.All references to JOBA should be translated to 'JOBA SCHDA'.

Chapter 7. Criteria Language 7-1

Predecessors can be the starting or ending of other schedules or jobs, the closing of anoutput data set, a job run on another node, a nonscheduled OS/390 job, and otheritems like these. Any predecessor can be defined as occurring on the day the scheduleor job is selected or as having occurred on a prior day. This will be discussed in moredetail later through the use of examples.

The criteria language uses three types of yearly calendar mechanisms:

■ Absolute Gregorian Calendar which defines specific keywords that haveabsolute dates associated with them. For example, the DAILY keyword causes ajob to be selected every day including weekends and holidays; WEEK-DAYcauses selection on Monday through Friday including holidays; and so on. Thismechanism is determined by the system and you do not have to define anything -only use the keywords.

■ Date Tables which define workdays, holidays, accounting days, and accountingperiods. This is the most flexible calendar mechanism to use and is the onerecommended. It also provides the easiest transition at year end.

■ Calendars which is a different selection methodology where you define daily,weekly, and monthly calendars in order to select schedules and jobs. When usingcalendars, only the calendar name determines selection. For example, you cannotalso select based on a criteria statement: with calendars, criteria statements onlydefine predecessors. To use this mechanism, you must define several differentcalendars.

The following topics explain the criteria vocabulary and calendar mechanisms.

7-2 Online Guide

7.1 Criteria Vocabulary


The criteria vocabulary consists of a set of reserved words broken into the followingcategories:

■ Boolean expressions

■ Selection of schedules and jobs

■ Predecessor conditions on schedules and jobs

This topic discusses these categories in more detail and contains some examples.

7.1.1 Reserved Words for Use in Boolean Expressions

OR and AND expressions are used with selection and predecessor keywords. The NOTexpression is used with selection keywords only. Parentheses can be used to logicallygroup these expressions.

The examples below show how these reserved words can be used to handle realscheduling situations.

7.1.2 Reserved Words Used for Selection

This topic discusses reserved words that cause schedules and jobs to be selected on agiven day.

Gregorian Calendar keywords include such words as DAILY, WEEK-DAY,WEEK-END, SUN, MON, JAN, DEC, 1ST, 31ST, and so on.

Workday keywords include such words as WDAY, HDAY, WDOW1, WDOW7,WDOW-1, WDOM1, HDAY1, HDAY31, HDAY-1, RD01=+nn, RD31=-nn, and soon.

Accounting period keywords include such words as xDAY, xDOM1, xDOM40,xDOM-1, xMOY1, and so on where x is a one-character prefix that you define whenyou set up a date table. Date tables are discussed in more detail later in this chapter.

A schedule or job can be used to determine selection. When it is used, it automaticallybecomes a predecessor as well. Although the schedule or job name itself causesselection to occur, a couple of reserved words can be used with them. One of thesekeywords is SCD which identifies the next name as being a schedule name. Otherwise,it is always assumed to be a job name.

The other keyword is START. Although the schedule or job name causes selection,START means that the predecessor is the starting of the schedule or job. Normally, thepredecessor is the completion. This subject is covered in much more detail later in thischapter.



The following examples demonstrate the use of selection reserved words. Each ofthese examples is called a condition.

Example Interpretation During Selection

JOBA SCHDA Jobname JOBA in schedule SCHDA (Defaults ST=40,JNO=01).

JOBA-02 40 SCHDA Jobname JOBA, Jobnumber 02 at station 40 in scheduleSCHDA.

JOBA.STEP2-02 40 SCHDA Jobname, Jobnumber 02 at station 40 in schedule SCHDA.

JOBA.STEP2.CC.GT.00008-02 40SCHDA

Jobname JOBA, Jobnumber 02 at station 40 in scheduleSCHDA.

JOBA.PROC1.STEP2-02 40 SCHDA Jobname JOBA, Jobnumber 02 at station 40 in scheduleSCHDA.

JOBA.PROC1.STEP2.CC.GT.00008-0240 SCHDA

Jobname JOBA, Jobnumber 02 at station 40 in scheduleSCHDA.

DAILY Daily.

MON Monday.

WDAY Every workday.

HDAY Every nonworkday, meaning holidays and possibly weekends.HDAY can also be expressed as NOT WDAY.

JOB1 Every day JOB1 is selected.

MON AND JOB1 Every Monday as long as JOB1 is also selected.

MON AND START JOB1 This is the same as the prior one. That is, every Monday aslong as JOB1 is also selected.

MON AND NOT HDAY Every Monday as long as it is not a holiday.

WDOW1 First workday of any week.

WED AND SCD SCHD1 Every Wednesday as long as the schedule SCHD1 is alsoselected.

WDOM-1 OR JOB1 Last workday of the month or as long as JOB1 is selected.

WDOW2 OR NOT JOB1 Second workday of the week whether or not JOB1 is selected.Also selected any time JOB1 is not selected.

7TH The seventh day of every month.

RD15 = +01 First workday following the fifteenth of every month.

MAR AND RD14= -01 First workday preceding the fourteenth of March.

7-4 Online Guide


7.1.3 Reserved Words for Use in Predecessors

This topic discusses reserved words that are used to define predecessor conditions.These reserved words ensure predecessor conditions are upheld, but do not cause anyform of selection.

PRED or PRED SCDIndicates the predecessor job or schedule must complete, probably on aprior day. That is, the predecessor must complete some time since thejob or schedule last ran, or was created. If the PRED schedule or jobis also in today's workload, it will always wait for today'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 prefixed withPRED indicating the predecessor was an NJE job that ran on a priorday.

MVS Indicates the predecessor job is a nonscheduled OS/390 job. MVS 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 on aprior 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. These predecessors arecalled global parameters and are described in 9.1, “Commonly AskedQuestions” on page 9-2.

When predecessors are defined this way, they are called explicitpredecessors. That is, the predecessor name is explicitly stated in thecriteria. This particular type can even be further qualified as akeyword-defined explicit predecessor.

The following examples illustrate the use of predecessor reserved words. Each of theseexamples is called a condition.

Example Interpretation of Predecessors

JOBA SCHDA DO NOT RUN UNTIL after JOBA completes.

JOBA.STEP2-02 40 SCHDA After Jobname JOBA, Stepname STEP2, Jobnumber 02 atstation 40 in schedule SCHDA completes.

JOBA.STEP2.CC.GT.00008-02 40SCHDA

After Jobname JOBA, Stepname STEP2 ending with acondition code greater than 8, Jobnumber 02 at station 40 inschedule SCHDA completes.



Example Interpretation of Predecessors

JOBA.PROC1.STEP2-02 40 SCHDA After Jobname JOBA, Procstep name PROC1, StepnameSTEP2, Jobnumber 02 at station 40 in schedule SCHDAcompletes.

JOBA.PROC1.STEP2.CC.GT.00008-0240 SCHDA

After Jobname JOBA, Procstep name PROC1, StepnameSTEP2 ending with a condition code greater than 8,Jobnumber 02 at station 40 in schedule SCHDA completes.

START JOBA After JOBA starts.

PRED JOBA SCHDA JOBA completed at least once since the last time the job youare defining predecessors for ran. If JOBA happens to be intoday's workload, this job will not run until today's JOBAcompletes regardless of when JOBA ran previously.

SCD SCHD1 After all of the jobs in the schedule SCHD1 have completed.

MVS JOBA After the nonscheduled OS/390 job JOBA completes. (The jobJOBA is not under the control of CA-Scheduler.)

PRED DSN PROD.JOB1DSN After the output data set PROD.JOB1DSN has been closed atleast once since this job was last run.

Note: Many other keywords can be found later in this chapter.

7.1.4 Combining Selection and Predecessor Criteria Vocabulary

Until now, we have discussed selection and predecessor processing as separate issues.They really are related, however.

For example, the selection criteria for JOBB is JOBA. That is, JOBB is selected anytime that JOBA is selected. In doing this, JOBA automatically becomes a predecessorto JOBB. Thus, JOBA is an explicit predecessor to JOBB. That is, the predecessorname is explicitly stated in the criteria. This particular type can even be furtherqualified as a selection-defined explicit predecessor.

Selection-defined explicit predecessors are jobs or schedules used in the selectioncriteria. The following is a list of these criteria:

Job nameJob name.Step nameJob name.Procstep name.Step nameJob name.Procstep name.Step name.CC.failoper.failcodeSCD schedule nameSTART job nameSTART SCD schedule name

7-6 Online Guide


Now look at some examples that define selection and predecessor criteria for JOBC.

Example Interpretation of Criteria

JOBA Select every time JOBA is selectedand make the successful completionof JOBA a predecessor of JOBC.

JOBA.STEP2 Select every time JOBA is selectedand make the successful completionof STEP2 in JOBA a predecessor ofJOBC.

JOBA.PROC1.STEP2 Select every time JOBA is selectedand make the successful completionof STEP2 in procstep PROC1 inJOBA a predecessor of JOBC.

JOBA.PROC1.STEP2.CC.GT.00008 Select every time JOBA is selectedand make the completion of STEP2with a condition code greater than 8in procstep PROC1 in JOBA apredecessor of JOBC.

START JOBA Select every time JOBA is selectedand make the start of JOBA apredecessor of JOBC.

MON AND JOBA Select every time JOBA is selectedon a Monday. JOBC will not startuntil JOBA completes successfully.

WED AND START SCD SCHD1 Select every time schedule SCHD1 isselected on a Wednesday. JOBC willnot start until schedule SCHD1 starts.



Some terminology: 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 the criteria.When the same schedule/job/job-number exists for more than one station (01 - 99), thesequential order of the stations defines implicit predecessors. For example, a CPU jobon station 40 will always have an implicit predecessor of its staging job on station 39,if both are in the day's workload. Furthermore, implicit predecessors are automaticallyselected on the same day that the CPU job (station 40) is selected. You can, however,code criteria for them to be selected less frequently than the CPU job. However, youcannot cause implicit predecessors to be selected on a day the CPU job is not selected.

Furthermore, implicit predecessors can only exist for CPU jobs and post-CPU jobs. Forexample, a CPU job is not submitted until all its pre-CPU jobs complete. Likewise,post-CPU jobs are not started until their CPU jobs have ended.

Non-CPU jobs are selected on a combination of their criteria and the status of the jobat the CPU station. If the job at the CPU station is not selected, none of the non-CPUstation jobs will be selected. If the CPU station job is selected, the criteria for thenon-CPU station jobs is evaluated to determine if the non-CPU station job should beselected. For example, assuming that station 40 is the CPU station:

JOB1-�1 3� SCHDA has criteria of 'MON'

JOB1-�1 4� SCHDA has criteria of 'WDAY AND NOT HDAY'

JOB1-�1 7� SCHDA has no criteria

The station 40 job is selected every workday that is not a holiday. The station 30 jobis selected every day that the station 40 job is selected that is also a Monday. Thestation 70 job is selected every day the station 40 job is selected.

If Monday is a holiday, the station 30 job will NOT be selected because the station 40job was not selected. Likewise, even though the station 70 job does not have criteria,which usually implies being selected every day, it is only selected when the station 40job is selected.

If a CPU station job is not defined, the lowest station number defined for the job takesover the role of the station 40 job in determining if other non-CPU station jobs shouldbe selected. For example:

JOB2=�1 7� SCHDA has criteria of 'MON'

JOB2-�1 71 SCHDA has criteria of 'MWF'

The station 70 job is only selected on Mondays. Since there is no station 40 job, andstation 70 is the lowest station number defined for the job, the station 71 job will onlybe eligible for selection when the station 70 job is selected. In this case, the station 71job is only selected on Mondays.

7-8 Online Guide


7.1.5 Using Multiple Conditions with ANDs and ORs

The examples that have been used so far have contained only one reason. That is, thecondition or combination of conditions, individually caused the reason a job orschedule was selected.

The way you separate reasons is with an OR outside of a set of parentheses or with anOR 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 their use more clearly depicts yourintention. All of our examples appear with parentheses.

The reason a job is selected stays with the job for its life in the system. In the exampleabove, the value 01 would be the reason if it was selected because it was (MON ANDJOB1). The value 02 would be the reason if it was (TUE AND JOB2). This value canbe referred to as the reason code.

Understanding the relationships between reasons and predecessors is important. Sincethe criteria language is used to define both selection and predecessor conditions, thereare rules for interpreting this mixture.

Given the example above, this means that no matter what day it is, JOB1 and JOB2will be predecessors 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) willhave to wait for both JOB1 and JOB2 to complete.

Does this mean that CA-Scheduler just makes one list of predecessors for each job?Not at all. Rule #1 just applies to selection-defined predecessors: jobs and schedules.CA-Scheduler observes ORs used with all keyword-defined predecessors.

Rule #1: Every CA-Scheduler-controlled job or schedule listed in a criteriastatement is a predecessor if it is also in the day's production.Whether those jobs or schedules are part of the reason forselection does not matter.



7.1.6 Effect of NOT Condition on Predecessors

The Boolean NOT expression affects selection just as you might expect: selection onlyoccurs when something else does not happen that day. For example, if the criteria forJOBC is:

(MON AND NOT JOB1)

selection will occur only on Mondays when JOB1 is not selected.

How would predecessors be handled in the above example? If JOB1 for some reasonends up in the workload (by a manual override), JOBC will wait for it if JOB1 wasadded while JOBC was waiting for its start time to be reached or other predecessors tobe 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 JOB2 arenot selected. If either JOB1 or JOB2 is present, however, it will be a predecessor ofJOBC. This shows that Rule #1 applies even when using NOT expressions.

The NOT expression is used only for selection purposes within the criteria language.

7-10 Online Guide


7.1.7 Recommended Method for Defining Selection Criteria

Schedules are sets of related jobs grouped together in ways that are easily understoodby your production control area. So if production control thinks of schedules as unitsof work, selection criteria would normally be defined at the schedule level. If all jobsin a schedule run when the schedule is selected, just define when these jobs run once,on the schedule's criteria record. That means you only need to define predecessors atthe job level. If a job does not run every time its schedule runs, define its ownindividual selection criteria on the job criteria record. Keep the following rule in mindwhen coding selection criteria.

For example, if the selection criteria for SCHED1 is MON, and JOB1A in SCHED1has a selection criteria of TUES, JOB1A will never get selected. JOB1A is onlylooked at if its schedule is selected but SCHED1 is not selected on Tuesdays, soJOB1A will never be selected.

Since we are on the subject of schedules and jobs, it is time to suggest another rule forcoding the criteria language.

Up to now, we have not followed this rule for simplicity's sake. After all, schedulenames technically are not required. However, if you omit a schedule name whenreferring to a job, CA-Scheduler looks in its database and defaults to the first scheduleit finds containing a job by that name. That explains why we advise that you followRule #3. From now on, we will, too.

A schedule is eligible for selection even if AUTOSEL=NO is specified.

Rule #2: A job will only be evaluated for selection and eligible for today'sworkload if its schedule is selected or eligible for today'sworkload.

Rule #3: When coding a job in the criteria language, always qualify it withits schedule name.


7.2 Calendar Mechanisms


Most of the examples presented so far have used explicit vocabulary such as MON forMonday or WEEK-DAY for Monday through Friday. But this oversimplifies whathappens in real life. For example, we do have holidays. And your accounting monthmay not begin on the first of every month. Some months have four weeks, whileothers have five. There can be quite a variation not only between different companies,but even different divisions within a company.

CA-Scheduler addresses all variations using three different calendar mechanisms:

■ The Absolute Gregorian Calendar defines specific keywords that have absolutedates associated with them. For example, the DAILY keyword causes a job to beselected every day including weekends and holidays; WEEK-DAY causesselection on Monday through Friday including holidays; and so on. Thismechanism is determined by the system and you do not have to define anything --just use the keywords.

■ Date Tables define workdays, holidays, accounting days, and accounting periods.This is the most flexible calendar mechanism and is the one recommended. It alsoprovides the easiest transition at year end. Each schedule defines which date tableto use for evaluating when to select that schedule and its associated jobs.

■ Calendars define daily, weekly, and monthly calendars for selecting schedulesand jobs. When using calendars, only the calendar name determines selection. Forexample, you cannot also select based on another job being selected. To use thismechanism, you must define individual calendars. This is the mechanism to use ifall else fails.

This topic describes the use of these calendar mechanisms.

7.2.1 Gregorian Calendar

This calendar mechanism is presented first because it is the simplest to understand andcan be used immediately. You do not have to define a calendar or date table first. Allyou do is use the reserved words (keywords) when defining your selection criteria.Most of the preceding examples used keywords from this calendar mechanism.

7-12 Online Guide


This mechanism's reserved words that control selection are based on the standardGregorian calendar, not workdays or accounting days. Some examples of thesekeywords follow:

Many other keywords can be found in 7.9, “Gregorian Calendar Conditions” onpage 7-41.

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 the firstweek of the month)

WOY3 Third week of the year

WOY-2 Second-to-the-last week of the year

I-WOY3 Third week of the year based on the international definitionof a week in ISO 8601, which says that all weeks start onMonday and go to Sunday. The first week of the year is theMonday to Sunday period that contains January 4 (which isthe same as the week that contains the first Thursday). Thismeans that December 29-31 may be in week 1 of thefollowing year, and January 1-3 may be in week 52 of theprevious year.

I-WOY-2 Second-to-the-last week of the year based on theinternational definition of a week in ISO 8601, which saysthat all weeks start on Monday and go to Sunday. The firstweek of the year is the Monday to Sunday period thatcontains January 4 (which is the same as the week thatcontains the first Thursday). This means that December29-31 may be in week 1 of the following year, and January1-3 may be in week 52 of the previous year.



Do not forget that you can also use the Boolean reserved words AND, OR, and NOT:

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

7-14 Online Guide


7.2.2 Date Tables

This calendar mechanism is the most flexible of them all and is the one werecommend you use. It handles holidays (and weekends) as they pertain to your ownenvironment. When defining the selection for a job or schedule, date tables are used toanswer such questions as:

■ Is today a workday?

■ Is tomorrow a holiday?

■ Is this the fourth workday of the month?

In other words, CA-Scheduler is smart enough to know today's date but is not smartenough to automatically know your workdays, holidays, and accounting periods.

With date tables, you can use the reserved words described for Gregorian calendars,but you must define your holidays. This is done with a full panel that actuallydisplays a calendar one month at a time. Before we see how to define holidays onthese panels, we will discuss the reserved words (keywords) used with date tables. Youcan use two types of keywords with date tables: workday keywords andaccounting-period keywords.

7.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 areconsidered holidays (unless you specify otherwise). The following is a sampling ofthese 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-2 Second-to-the-last workday of the month

WWOM2 Second work week of the month (any week with at least oneworkday 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



7.2.2.2 Accounting-Period Keywords

When we discuss how to define a date table, 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 other unit oftime.

When you define a date table, you have to define a prefix (a letter, with the exceptionof E, H, N, P, or W, allowing for 21 different accounting periods) while using thesame date table. Each accounting period has its own prefix. The A prefix or the Aversion of the date table is the default date table. When you use a B prefix, theaccounting resolutions will be taken from the B version of the date table.

In the examples below, x is used instead of a prefix.

Now that we have some of the terminology out of the way, we will see what isinvolved in setting up a date table.

We have to start with a rule. As you might think, we have to consider accountingperiods going over a year-end date. Consequently, a rule for date tables:

To define a date table, select option 2 (Database) from the CA-Scheduler main menu,then option 7 (Datetable). Select option 4 to define a new date table, specifying theone to seven character name of the date table, the prefix character, and the year. Thefollowing panel is displayed.


xDAY All accounting days for prefix x

xDOM1 First accounting day of the period (there can be up to 40accounting days in the period)

xDOM-1 Last accounting day of the period

xWOM2 Second accounting week of the period (there can be up to 10accounting weeks per period)

xWOM-1 Last accounting week of the period

Rule #4: Define three years' worth of date tables for each unique date tablename. Each year being accessed must have a date table for theyear before and after it.

7-16 Online Guide



COMMAND ===>

Define Datetable:

Datetable . . . . . . DATETAB

Accounting Code . . . A

Year . . . . . . . . 2��3


Enter END to Exit.

� �

Press Enter to display the first month of the date table.


COMMAND ===>

Datetable . . . . . DATETAB Accounting Code . . A

Description . . . .

JANUARY 2��3


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

1 WA.. 2 ....

3 .... 4 WA.. 5 WA.. 6 WA.. 7 WA.. 8 WA.. 9 ....

1� .... 11 WA.. 12 WA.. 13 WA.. 14 WA.. 15 WA.. 16 ....

17 .... 18 WA.. 19 WA.. 2� WA.. 21 WA.. 22 WA.. 23 ....

24 .... 25 WA.. 26 WA.. 27 WA.. 28 WA.. 29 WA.. 3� ....

31 ..M.

Legend:

W... - Workday



...Y - Year End

Enter END to exit.

� �

To indicate that January 1 is a holiday and a nonaccounting day, delete the W (toremove the workday attribute) and the A (to remove the accounting day attribute).Note that the accounting day attribute is always an A, even if a different prefix isbeing used.

You can also change the end of the month (or the accounting period) by removing theM from the 31st and putting it on another day (even in another month). If January wasthe end of the accounting year, you could place a Y on the appropriate day.



Press Enter after making the changes. Notice that January 1 is no longer highlighted,since it is no longer a workday.


COMMAND ===>

Datetable . . . . . DATETAB Accounting Code . . A

Description . . . .

JANUARY 2��3


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

1 .... 2 ....

3 .... 4 WA.. 5 WA.. 6 WA.. 7 WA.. 8 WA.. 9 ....

1� .... 11 WA.. 12 WA.. 13 WA.. 14 WA.. 15 WA.. 16 ....

17 .... 18 WA.. 19 WA.. 2� WA.. 21 WA.. 22 WA.. 23 ....

24 .... 25 WA.. 26 WA.. 27 WA.. 28 WA.. 29 WA.. 3� ....

31 ..M.

Legend:

W... - Workday



...Y - Year End

Enter END to exit.

� �

You may use PF8 to scroll to later months and PF7 to scroll to earlier months. Youmay also type the first three letters of any month's name on the command line to jumpdirectly to that month.

When you are finished updating the date table, press PF3 to save your changes. (If youwish to exit without saving your changes, type CAN on the command line.) Don'tforget that you must also define date tables for the prior and next years.

7-18 Online Guide


7.2.2.3 Summary of Date Tables

Date tables are broken into two categories: workday processing and accounting periodprocessing. If you need more than one holiday definition, you will need another datetable.

The reserved words (keywords) for the Gregorian Calendar mechanism and thekeywords for the date table calendar mechanism can be used together. Here are someexamples of Gregorian and/or date table calendar mechanisms:

Example Interpretation

(MON AND WDAY) OR(TUE AND HDAY-1)

Select on Monday when Monday is not a holiday,or select on Tuesday when Monday is a holiday.

WDOW1 Select the first workday of every week. This is thesame as above except if Tuesday is also a holiday,it will be selected on Wednesday.

WDAY AND (MON ORWED OR TT)

Select every Monday through Thursday except onholidays.

WDAY AND NOT FRI This is the same as the above example onlyexpressed more simply.

BDAY AND NOTBDOM-1

Select on every accounting day except for the lastaccounting day of the period. This references thedate table defined with prefix B.

WDAY AND WOY-1 Select every workday of the last week of the year.

MON AND (WWOM2OR WWOM4)

Select every Monday of the second and fourthweeks of the month regardless of whether Mondayis a holiday.

ADAY AND NOT HDAY Select on every accounting day that is not a holiday.An accounting day may be a holiday (this is notnormally the case).

7.2.2.4 Date Translation Report

Now that we have discussed the Gregorian calendar and date tables, we need a way tosee what conditions are met on any given day. The Date Translation report is obtainedby running the CA-Scheduler Utility with the

REPORT DATETRAN

transaction. You can request a specific date and/or date table on this transaction if youdesire. Reviewing this report will help you understand the Gregorian calendar and datetables better.



COMPUTER ASSOCIATES DATE TRANSLATION REPORT DATETRAN PAGE 1

CA-SCHEDULER 9.� xxyyCH9�� 24 APR yyyy 14.27.2�

JULIAN DATE=yyyy114 TABLE NAME=DATETAB

GREGORIAN DATE=�4/24/yy

DAY OF WEEK=FRI WEEK-DAY=YES WEEK-END=NO MWF=YES TT=NO

NTH DAY OF MONTH=FRI4 FRI-1 NEGATIVE DAY OF MONTH=DOM-7 LEAP-YEAR=NO

WEEK OF MONTH=4TH-WEEK WEEK OF YEAR=WOY17 WOY-37 DAYS IN MONTH=3�

DAY1OF2=YES DAY2OF2=NO

DAY1OF3=YES DAY2OF3=NO DAY3OF3=NO

DAY1OF4=NO DAY2OF4=NO DAY3OF4=YES DAY4OF4=NO

DAY1OF5=YES DAY2OF5=NO DAY3OF5=NO DAY4OF5=NO DAY5OF5=NO

DAY1OF6=YES DAY2OF6=NO DAY3OF6=NO DAY4OF6=NO DAY5OF6=NO DAY6OF6=NO

WEEK1OF2=NO WEEK2OF2=YES

WEEK1OF3=NO WEEK2OF3=YES WEEK3OF3=NO

WEEK1OF4=NO WEEK2OF4=NO WEEK3OF4=NO WEEK4OF4=YES

WEEK1OF5=YES WEEK2OF5=NO WEEK3OF5=NO WEEK4OF5=NO WEEK5OF5=NO

WEEK1OF6=NO WEEK2OF6=YES WEEK3OF6=NO WEEK4OF6=NO WEEK5OF6=NO WEEK6OF6=NO

WORK-DAY=YES WORK DAY OF WEEK=WDOW5 WDOW-1

WORK DAY OF MONTH=WDOM18 WDOM-5 WORK DAY OF YEAR=8� -172

WORK WEEK OF MONTH=WWOM4 WWOM-2 WORK WEEK OF YEAR=WWOY17 WWOY-37

RD�1=+17 -�5 RD�2=+16 -�6 RD�3=+15 -�6 RD�4=+15 -�6

RD�5=+15 -�7 RD�6=+14 -�8 RD�7=+13 -�9 RD�8=+12 -1�

RD�9=+11 -11 RD1�=+1� -11 RD11=+1� -11 RD12=+1� -12

RD13=+�9 -13 RD14=+�8 -14 RD15=+�7 -15 RD16=+�6 -16

RD17=+�5 -16 RD18=+�5 -16 RD19=+�5 -17 RD2�=+�4 -18

RD21=+�3 -19 RD22=+�2 -2� RD23=+�1 -21 RD24=+�� -��

RD25=+22 -�1 RD26=+21 -�1 RD27=+2� -�1 RD28=+2� -�2

RD29=+2� -�3 RD3�=+19 -�4 RD31=+18

HOLIDAY=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=YES

A-ACCOUNTING DAY=YES DAY OF MONTH=ADOM18 ADOM-5 DAY OF YEAR=82 -18�

WEEK OF MONTH=AWOM4 AWOM-2 MONTH OF YEAR=AMOY4 AMOY-9

X-ACCOUNTING DAY=YES DAY OF MONTH=XDOM18 XDOM-5 DAY OF YEAR=82 -18�

WEEK OF MONTH=XWOM4 XWOM-2 MONTH OF YEAR=XMOY4 XMOY-9

The Date Translation report is used to show you what selection keywords are TRUEfor a specific date and date table combination. It first displays the Julian andGregorian dates with the date table name that was used to determine workdays,accounting days, and accounting periods. (The date table name is on the right side ofthe report.)

Notice the next set of lines pertain to the Gregorian calendar and include DAY OFWEEK, WEEK OF MONTH, DAYnOFm, and WEEKnOFm. These indicate whether acondition is satisfied. For example, WEEK-DAY=YES means that any time youspecified WEEK-DAY as the criteria, the schedule or job will be selected. The rest ofthe lines pertain to the date table. They include the workday, the workday of the week,the workday of the month, the workday of the year, the work week, the relative daysof the month, and the various accounting days.

After reviewing this report carefully, you should understand how the criteriavocabulary works with the Gregorian calendar and date tables.

7-20 Online Guide


7.2.3 Calendars

To use calendar processing, set aside everything you have learned so far about theGregorian calendar and date tables. Calendars use an entirely different approach toselecting schedules and jobs. Do not try to relate any discussion of calendars to theother calendar mechanisms.

We do not recommend that you use calendars. Instead, try to do all of your definitionswith date tables or the Gregorian calendar or a combination of the two. This feature issupported to assist users converting from the VSE version of CA-Scheduler.Consequently, the description of calendars will be brief. If you do not intend to usecalendars, you can skip this subtopic.

You would use this mechanism if a set of schedules have to run on specific datesduring the year and no relationship exists between the dates. Then you would use acalendar to define just the days of the year on which those schedules run.

When using calendars, a schedule or job is selected on the days that the calendarspecifies as workdays. With calendars, the criteria language is not used for selection,only for defining predecessors. Again, the only thing you specify on a schedule forselection purposes is the calendar name. The same calendar also applies to the jobs inthat schedule.

The following steps describe how to use calendars.

7.2.3.1 Step 1: Define the Prototype Calendar

Before you define any calendars, first define a prototype calendar. This calendardefines your holidays as well as what to do if another calendar is defined with aprocessing day on a holiday. You may shift the day to the previous workday, the nextworkday, or drop the day.

Prototype calendars must have a name of PROTOyy, where yy is the year. For 2003,use PROTO03.

You can have only one prototype calendar for each year. This means that you haveonly one set of holiday definitions. Once the prototype is defined, you can definecalendars specific to your needs.

The panel below defines the prototype calendar for 2003. It specifies a five day workweek. If calendars are defined using a holiday, CA-Scheduler handles reschedulingbased on the calendar's selection frequency:

■ Daily calendars are not rescheduled. Workdays in the prototype calendar becomeworkdays in the daily calendar.

■ Weekly calendars use the Weekly Roll Option. Drop means not to schedule aworkday in the weekly calendar. Next and Previous schedule the next or previousworkday in the prototype as the workday in the weekly calendar.



■ Monthly calendars use the Monthly Roll Option. Drop means not to schedule aworkday in the monthly calendar. Next and Previous schedule the next or previousworkday in the prototype as the workday in the monthly calendar.


COMMAND ===>

Define Prototype Calendar:

Calendar . . . . . . PROTO�3

Year . . . . . . . . 2��3


Prototype Options:

Weekly Roll Option . . . DROP (NEXT or PREVIOUS workday, or DROP)

Monthly Roll Option . . DROP (NEXT or PREVIOUS workday, or DROP)

Enter END to Exit.

� �

When you press Enter, January's dates are displayed. You can change dates from aholiday to a workday by typing a W next to it, or to a holiday by blanking out the W.


COMMAND ===>

Calendar . . . . . PROTO�3

Description . . . .

JANUARY 2��3


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

1 W 2 .

3 . 4 W 5 W 6 W 7 W 8 W 9 .

1� . 11 W 12 W 13 W 14 W 15 W 16 .

17 . 18 W 19 W 2� W 21 W 22 W 23 .

24 . 25 W 26 W 27 W 28 W 29 W 3� .

31 .

Legend:

W - Workday

Enter END to exit.

� �

You may use PF7 and PF8 to scroll through the months, or type the first three lettersof a month's name on the command line to jump to that month.

7-22 Online Guide


When all 12 months are correctly defined, press PF3 and the prototype calendar willbe saved. (You can exit without saving your changes by typing CAN on the commandline.)

7.2.3.2 Step 2: Define Daily, Weekly and Monthly Calendars

Now that we have a prototype calendar, define other types of calendars. When definingcalendars, invent your own names for them such as EVERYDAY, TUESDAYS,ENDOFWK, or ENDOFMO.

When defining a calendar, the following panel is displayed.


COMMAND ===>

Define Calendar:

Calendar . . . . . . MYCAL

Year . . . . . . . . 2��3


Options:

Type of Calendar . . . DAILY (Daily, Weekly, or Monthly)

Day of Week/Month . . (Blank for Daily,

SUN - SAT or END for Weekly, or

one of the following for Monthly:

FD - first day of month

LD - last day of month

nn - nnth day of month

FW - first workday of month

LW - last workday of month

nnW - nnth workday of month

Enter END to Exit.

� �

Specify the type of calendar you are creating: DAILY, WEEKLY, or MONTHLY.

Daily calendars will copy the prototype calendar.

For weekly calendars, you may specify the day of the week that should become aworkday for this calendar.

For monthly calendars, you may specify the day of the month that should become aworkday, using any of the listed options.


7.3 Some Examples

7.3 Some Examples

Now that you are familiar with the criteria language and calendar mechanisms,consider how to apply what you have learned to the following scheduling problems.

7.3.1 Example 1

To run the job named JOBA in the schedule name SCHDA on the first workday of theweek, what criteria statement would you use?

WDOW1

JOBA would be selected on the first working day of the week.

M T W T F S S M T W T F S S M T W T F S S M T W T F S S M T W

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

JOBA X X X X X

7.3.2 Example 2

Now use another variation of WDOW to schedule JOBA to run on the last workday ofthe week.

WDOW-1

JOBA would be selected on the last working day of the week (third Friday=holiday).


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

JOBA X X X H X

7.3.3 Example 3

Then what criteria statement would you use to run JOBA on the first workday of themonth?

WDOM1

JOBA would be selected on the first Monday of the month.


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

JOBA X

7-24 Online Guide

7.3 Some Examples

7.3.4 Example 4

What variation of WDOM will run on JOBA on the last workday of the month?

WDOM-1

JOBA would be selected on the last workday of the month.


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

JOBA X

7.3.5 Example 5

JOBA runs on Friday. If Friday is a holiday, then JOBA runs on the followingMonday. And if the following Monday is also a holiday, then JOBA runs on thefollowing Tuesday. What criteria statement conveys this meaning?

FRI AND NOT HDAY OR

MON AND HDAY-3 OR

TUES AND HDAY-4 AND HDAY-1

Run JOBA on FRI unless FRI is a holiday, then run job on MON unless MON is alsoa holiday, then run job on TUES.


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

JOBA X X H X X


7.3 Some Examples

7.3.6 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 or not Friday is a holiday,and is not dependent on PROD001

■ PROD003 - the weekly summary report that runs on Friday night and must waitfor the other two jobs to finish

What criteria statements apply to this schedule and its jobs?

For selection purposes, the OR expression will be handled as expected. However,predecessors that are jobs are handled as if there is always an AND condition.Consequently, if Friday is a workday, PROD003 will wait for both PROD001 andPROD002.

Criteria for schedule ACCPROD None: All jobs may be selected daily.

Criteria for job PROD001 WDAY

Criteria for job PROD002 FRI

Criteria for job PROD003 FRI AND(PROD001 ACCPROD OR PROD002ACCPROD)

7-26 Online Guide

7.3 Some Examples

7.3.7 Example 7

A payroll schedule (PAY) consists of two jobs:

■ PAY001 - the summary that runs every weekday and needs an input data set,PAY001.INPUT, that is transmitted every weekday from an RJE site. It must alsowait for job PAY002.

■ PAY002 - the summary that only runs on Friday.

This tells CA-Scheduler to schedule job PAY001 every week day, regardless ofwhether job PAY002 is scheduled. Job PAY001 waits for a data set to be createdevery week day and also waits for job PAY002, when it is scheduled on Friday.

Criteria for schedule PAY WEEK-DAY

Criteria for job PAY002 FRI

Criteria for job PAY001 DSN PAY001.INPUT AND(PAY002 PAY OR NOT PAY002PAY)

7.3.8 Example 8

The Manufacturing Quarterly production schedule (MANQTR) contains three jobs thatrun on the last day of the manufacturing quarter. MANQTR runs on a 4-week, 4-week,5-week cycle defined in a date table specified in the schedule definition using a prefixof M.

The example above shows how you can define selection criteria at the schedule leveland predecessors at the job level. Separating selection criteria and predecessorconditions this way makes it easier to evaluate these criteria statements.

Criteria for schedule MANQTR MDOM-1 AND(MMOY3 OR MMOY6 ORMMOY9 OR MMOY12)

Criteria for job JOBA None - Defaults to whenever theschedule is selected.

Criteria for job JOBB JOBA MANQTR

Criteria for job JOBC JOBB MANQTR


7.3 Some Examples

7.3.9 Example 9

For this example, we take something a little more practical and show some of the logicbehind determining criteria. This shows the type of thought process you go through.

The schedule named IH7BKUP backs up some disks and consists of three jobs: a dailybackup, a weekly backup and a monthly backup.

The daily job IH7D02 normally runs Monday through Thursday. Consequently, itscriteria would be something like:

MON OR TUE OR WED OR THU

But what happens on holidays? On holidays, we do not want the job to run. To omitholidays, 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 concise way ofwriting this criteria is as follows:

WDAY AND NOT FRI

Another factor to consider is whether this job has predecessors. In this case, it doesnot, so the daily job's selection criteria is now complete.

Now we can work on the weekly job. We already know to be conscious of holidays. Ifthe weekly job runs on Monday through Thursday, the daily job must finish first. Thecriteria statement that best describes this is shown below.

WDAY AND FRI

OR

(WDAY AND THU AND HDAY1 AND IH7D�2 IH7BKUP)

OR

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, we cansimplify the criteria statement above as follows:

WDOW-1 AND PRED IH7D�2 IH7DBUP

This brings us to the monthly job IH7M02 which runs on the last workday of themonth. Its predecessors vary depending on what day of the week this job runs.

■ If the last workday falls on Monday through Thursday, the monthly job shouldwait for the daily backup to complete.

■ If the last workday of the month is a Friday, the monthly job should wait for theweekly backup to complete.

■ If the last workday of the month falls on a Saturday or Sunday, the monthlybackup job has no predecessors. For our purposes, however, the date table wasdefined for a five-day work week so Saturdays and Sundays are not workdays.

7-28 Online Guide

7.3 Some Examples

The criteria would be:

WDOM-1 AND (IH7D�2 IH7BKUP OR IH7W�2 IH7BKUP)

Now we can look at the finished product:

Criteria for schedule IH7BKUP None - Defaults to having all jobslooked at every day.

Criteria for job IH7D02 WDAY AND NOT FRI

Criteria for job IH7W02 WDOW-1 AND PRED IH7D02IH7BKUP

Criteria for job IH7M02 WDOM-1 AND(IH7D02 IH7BKUP OR IH7W02IH7BKUP)

7.3.10 Example 10

JOBX JNO=�1 CRI=JOBA

JOBX JNO=�2 CRI=JOBB

JOBX JNO=�3 CRI=JOBC

JOBX JNO=�4 CRI=JOBD

Run JOBX once for every time either JOBA, JOBB, JOBC, or JOBD is also selected.For example, if JOBA and JOBB are selected to run today, then JOBX will run twice,once being dependent on JOBA to complete, and once being dependent on JOBC tocomplete.


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

JOBA X X X X

JOBX-�1 X X X X

JOBB X X X

JOBX-�2 X X X

JOBC X X X

JOBX-�3 X X X

JOBD X X

JOBX-�4 X X


7.3 Some Examples

7.3.11 Example 11

JOBA REQUESTED

JOBB JOBA

JOBC JOBB

JOBD JOBC

Because JOBA is a requested job, it will be selected every day, but will not run unlessrequested. And because JOBA is always selected, any other jobs which are a successorto JOBA (in this case, JOBB and JOBC and JOBD are all successors), then all ofthese jobs will also be selected.


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

JOBA X X X X

JOBB X X X X

JOBC X X X X

JOBD X X X X

7.3.12 Example 12

(WEEK-DAY AND JOB1 AND JOB2) OR (WEEK-END AND JOB3)

This particular criteria is not logical if you consider how job selection/dependencyworks under CA-Scheduler. For example, suppose that on any given day, JOB1 andJOB2 and JOB3 are all selected to run. The job dependency would then become 'JOB1and JOB2 and JOB3' since all three jobs were selected. (The 'OR' condition becomesan 'AND' condition for job dependency.)

So, if you have a job (JOBA) that needs to run Monday through Friday when JOB1and JOB2 are selected, and runs on Saturday and Sunday when JOB3 is selected, thenyou could use the following criteria:

JOBA JNO=�1 WEEK-DAY AND JOB1 AND JOB2

JOBA JNO=�2 WEEK-END AND JOB3


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

JOB1 X X X X X X X X X X X X X X X X X X X X X X X

JOB2 X X X X X X X X X X X X X X X X X X X X X X X

JOBA-�1 X X X X X X X X X X X X X X X X X X X X X X X

JOB3 X X X X X X X X

JOBA-�2 X X X X X X X X

7-30 Online Guide

7.3 Some Examples

7.3.13 Example 13

JOB NAME JOB CRITERIA

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

JOBA WDAY ( WORK DAY )

JOBB FRI ( FRIDAY )

JOBC JOBA OR JOBB

ON WDAY, JOBA AND JOBC will run, with JOBA being a predecessor to JOBC.

ON FRI, (if FRIDAY is NOT a WDAY), then JOBB AND JOBC will run, with JOBBbeing a predecessor to JOBC.

However, if FRIDAY is a WORKDAY, then all three jobs will run with JOBC waitingfor both JOBA AND JOBB to finish before being released. Because both JOBA ANDJOBB were SELECTED on FRIDAY, then JOBC's criteria becomes 'JOBA ANDJOBB' rather than 'JOBA OR JOBB'.


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

JOBA X X X X X X X X X H X X X X X X X X X X X X X

JOBB X X X X

JOBC X X X X X X X X X X X X X X X X X X X X X X X

7.3.14 Example 14


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

JOBA DAILY ( DEFAULT )

JOBB MON ( MONDAY )

JOBC WED ( WEDNESDAY)

JOBD (JOBA AND JOBB) OR JOBC

On MON, JOBA JOBB JOBD will run, with JOBD waiting for both JOBA JOBB tocomplete.

ON WED, JOBA AND JOBC AND JOBD will run, with JOBD waiting for bothJOBA AND JOBC to complete.

*REMEMBER that the 'OR' condition becomes an 'AND' condition whenDEPENDENCY is determined, such that on WED, the criteria for JOBD will become'JOBA AND JOBC' (JOBB is disregarded because it was not SELECTED to run onWED).


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

JOBA X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X X

JOBB X X X X X

JOBC X X X X X

JOBD X X X X X X X X X X


7.4 What Is Wrong with these Examples?


Now that you have a basic understanding of the criteria language, try testing yourknowledge by debugging errors in the following criteria statements.

7.4.1 Example 1

Will JOBA run on Mondays? Not likely because MONDAY is not a vocabulary word.Instead, CA-Scheduler interprets MONDAY as a job name. Therefore, this job willonly be selected when the job MONDAY is selected. Since you probably do not havea job named MONDAY, JOBA in SCHD01 would never be selected.

The correct criteria vocabulary word is MON.

Criteria for JOBA SCHD01 MONDAY

7.4.2 Example 2

Will JOBA be selected on Mondays and Tuesdays? No, you cannot have one day as aMonday and a Tuesday.

The correct criteria vocabulary word is MON or TUE.

Criteria for JOBA SCHD01 MON AND TUE MONDAY AND TUESDAY

7.4.3 Example 3

The intent is to select JOBB on the last workday of the week, but that is not whathappens. Evaluate this statement carefully to see what is wrong. It is important toevaluate the selection criteria and the predecessor conditions separately.

What is JOBB's predecessor? The data set JOBA.DATASET must be closed on theday JOBB is selected before JOBB will be submitted. That is straightforward enough.

But 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'

Criteria for job JOBB WDOW-1 OR DSNJOBA.DATASET

7-32 Online Guide


You see, CA-Scheduler cannot translate DSN JOBA.DATASET into a selectioncondition, so the second condition defaults to DAILY. Because of the OR, this job isselected WDOW-1 OR DAILY. How could you rewrite the statement to run JOBBwhen intended? Code the criteria statement with an AND instead of an 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.

7.4.4 Example 4

Here is another problem. Why do JOBA and JOBB in schedule SCHED01 not runwhen expected? Both jobs are supposed to run Mondays and Wednesdays. OnMondays, JOBB should be the predecessor to JOBA, but conversely on Wednesdays.

The meaning of these criteria statements is confusing until you add some parenthesesto show how the system will interpret this:

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 on Mondays.

That seems in order, so look at the predecessor conditions, remembering the rule forevaluating predecessors:

There are no OR relationships with selection-defined explicit predecessors. All ORsbecome ANDs.

That means the explicit predecessor of JOBA is JOBB, and the explicit predecessor ofJOBB is JOBA. When jobs require each other as predecessors, that creates apredecessor loop, which is also called predecessor deadlock. Although thesedeadlocked jobs are selected properly, neither job ever runs because their predecessorsare never satisfied. You can run the Analyze Report at any time to detect deadlocksautomatically.

Criteria for job JOBA MON AND JOBB SCHED01 ORWED

Criteria for job JOBB MON OR WED AND JOBASCHED01

Criteria for job JOBA (MON AND JOBB SCHED01) ORWED

Criteria for job JOBB MON OR (WED AND JOBASCHED01)



7.4.5 Example 5

Suppose you want JOBA to run on any day but Monday or Tuesday. Why does thecriteria statement above not make that happen?

Instead, JOBA is always selected because on Mondays, JOBA is selected because it isnot Tuesday. And on Tuesdays (and every other day), JOBA is selected because it isnot Monday.

Two valid ways to code this criteria are:

Criteria for job JOBA NOT MON OR NOT TUE

Criteria for job JOBA NOT (MON OR TUE)

Another way to express this criteria NOT MON AND NOT TUE

7.4.6 Example 6

Clearly, 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. And 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, the status shows that JOBBwaits for predecessors JOBA, GBLB01, and GBLB01. When GBLB01 is set to YES,JOBB starts regardless of JOBA because of the second GBLB01. We can step throughwhat happens.

After JOBB is selected, these predecessors are left for evaluation:

(JOBA SCHED�1 AND GBLB�1=YES) OR (GBLB�1=YES)

As you can see, JOBB will start as soon as GBLB01 is set to YES.

The correct way of coding this criteria statement is:

Criteria for job JOBB ADAY AND JOBA SCHED01 AND GBLB01=YESORADAY AND GBLB01=YES

Criteria for job JOBB ADAY AND JOBA AND GBLB01=YESORADAY

7-34 Online Guide


After JOBB in SCHED01 is selected, only these predecessors are left for evaluation:

(JOBA AND GBLB�1=YES)

When JOBA is not in the day's workload, CA-Scheduler knows that it cannot be apredecessor.

7.4.7 Example 7

The intent is that JOBB would run Monday through Saturday, but only on Saturday ifJOBA completed sometime since last Saturday (for example, it may be that JOBAonly runs on Fridays). The rule is that keyword-defined explicit predecessors applyacross ALL selection criteria. Consequently, JOBB will wait for JOBA every timeJOBB is selected (even on Monday, Tuesday, and so on).

To accomplish this, we have to set up JOBB as two separate jobs: JOBB-01 andJOBB-02. Notice how we have simplified the criteria for JOBB-01 below.

The correct way of coding this criteria statement is:

Criteria for job JOBB MON OR TUE OR WED OR THU OR FRIOR(SAT AND PRED JOBA)

Criteria for the first job JOBB-01 WEEK-DAY

Criteria for the second job JOBB-02 SAT AND PRED JOBA


7.5 Review of Tips to Remember

7.5 Review of Tips to Remember

7.5.1 Pitfalls

Pitfall #1 A global parameter only gets set. If you want it reset, you must setit to another value. You cannot reset a global parameter.

Pitfall #2 Work can only be backlogged once. If work is eligible to bebacklogged multiple times, only the last occurrence is kept.

Pitfall #3 When keying in a command to the left of a schedule or a job in thestatus displays, be sure you are on the correct line. It is easy tocancel the wrong job.

Pitfall #4 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 active workload by the PURGEcommand.

Pitfall #5 Do not use the CA-Scheduler reserved keywords as job name orschedule names.Example: Jobname: REQUESTED or DAILY

Schedule name: REQUESTED or DAILY

7-36 Online Guide

7.6 Notes

7.6 Notes

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

Note #2 Predecessors in job records are not evaluated until its schedule hasstarted and the job's early start time has been reached.

Note #3 Defining predecessors for jobs does not override a schedule'spredecessors; instead, predecessors are cumulative.

Note #4 Job start times do not override specified schedule start times. Instead,they let you postpone running jobs after a schedule has started.

Note #5 The PRED keyword only waits for the job if it has not run since the lasttime this job has run. If the predecessor job has abended, its criteria hasbeen satisfied.

Note #6 All criteria for JOBNAME should be coded as 'JOBNAMESCHEDULENAME'.

Note #7 Do not use TYPRUN=HOLD in JCL submitted by CA-Scheduler.

Note #8 Autoscan does not reset the global parameters.

Note #9 Formatting the CAIJTRK files sets all global parameters to defaults.

7.6.1 Rules

Rule #1 Every CA-Scheduler-controlled job or schedule listed in a criteriastatement is a predecessor if it is also in the day's production. Whetherthose jobs or schedules are part of the reason for selection does notmatter.

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.

Rule #3 When coding a job in the criteria language, always qualify it with itsschedule name.

Rule #4 CA-Schedule observes ORs used with all keyword-defined predecessors(NJE, MVS, DSN, GDG, GBLxnn, and PRED).


7.7 Summing Up

7.7 Summing Up

Evaluate criteria statements twice: once to determine selection criteria and again toidentify predecessor conditions.

When coding a job in the criteria language, always qualify it with its schedule name.

Use the SCD keyword before a schedule name to identify it as such.

Selection: A job will only be evaluated for selection and eligible for today'sworkload if its schedule is selected or eligible for today's workload. A schedule or jobis eligible for predecessor selection even if AUTOSEL=NO or SKIP=xx is specified.

The NOT keyword only applies to selection.

Predecessors: Every job or schedule listed in a criteria statement is a predecessorif it is also in, or eligible to be in, the day's production. Whether those jobs orschedules are part of the reason for selection does not matter.

CA-Scheduler observes ORs used with all keyword-defined predecessors (NJE, MVS,DSN, GDG, GBLxnn, and PRED).

A criteria statement like NOT JOBA defines JOBA as a predecessor.

If jobs or schedules are predecessors, CA-Scheduler waits for them to complete unlessyou precede their names with the keyword START.

Calendars: Define daily, weekly, and monthly calendars for selecting schedules andjobs. When using calendars, only the calendar name determines selection.

Date Tables: Define three years' worth of date tables for each unique date tablename. Each year being accessed must have a date table for the year before and after it.

7-38 Online Guide



7.8.1 Reserved Words

To show that the predecessor is a schedule that completed on a previous day and thushas no effect on the selection of its successor, precede it with PRED SCD.

To show that the predecessor is a job that completed on a previous day and thus hasno effect on the selection of its successor, precede it with PRED.

Use PRED only to identify predecessors that are NOT selected on the same day astheir successors. (For example, if the predecessor is selected on a Monday and thesuccessor is selected on a Friday. In this case, if both the PRED predecessor and thesuccessor are selected together, the successor will wait for the PRED predecessor eventto occur within this production day.)

In most cases, predecessors and successors are selected together. A job that is selectedwith its successor does not need any reserved word to identify it as a predecessor. Theonly reserved words required for predecessors and successors selected together areSCD and START, as shown in the table at the top of the previous page.

To show that Specify

Criteria consists of two or more selectionreasons, any one of which will cause a job orschedule to be selected.

OR between reasons

A selection reason consists of two or moreconditions, all of which must be met for a job orschedule to be selected.

AND between conditions

Two or more conditions count as one reason. ( ) around the conditions

All conditions must be satisfied except this one(negate the condition).

NOT before the exception

To show that a predecessor condition causesits successor to be selected and is the

Precede it with

Start of a

� Schedule START SCD

� Job START

End of a

� Schedule SCD

� Job



To show that the predecessor is the Precede it with

Start of a job at another node START NJE

End of a

� Job at another node NJE

� Nonscheduled OS/390 job MVS

End on a previous day of a

� Job at another node PRED NJE

� Nonscheduled OS/390 job PRED MVS

Close of a

� Output data set DSN

� Output generation data group GDG

Close on a previous day of a

� Output data set PRED DSN

� Output generation data group PRED GDG

User-defined event which is satisfied when an operatoror authorized user supplies a value on a SETGBLxnn= command which matches the valuespecified by the GBLxnn=value on the CRITERIAkeyword (where nn is a number from 1 to 16).

GBLxnn=

7-40 Online Guide

7.9 Gregorian Calendar Conditions


These conditions are based on the standard Gregorian calendar and not on workdays oraccounting days; therefore, you can use these conditions in criteria statements with orwithout defining a date table. To see what Gregorian conditions are satisfied on anygiven day, consult the Date Translation Report in the Reports Guide.

If you specify Schedules and jobs will be selected on

REQUESTED Request. (They are actually selected every day but must beactivated by the REQUEST or SREQ command in order to bemoved to the active queue for processing. Note, when using theREQUEST/SREQ command with other criteria, that criteria areevaluated from left to right. Therefore, if you listREQUEST/SREQ before another condition, like JOBA, theschedule or job will be selected every day but must be activatedby the REQUEST/SREQ command.)

DAILY Every day, including weekends and holidays

WEEK-DAY Monday through Friday

WEEK-END Saturday and Sunday

SUN Sunday

MON Monday

TUE Tuesday

WED Wednesday

THU Thursday

FRI Friday

SAT Saturday

MWF Monday, Wednesday, and Friday

TT Tuesday and Thursday

JAN January

FEB February

MAR March

APR April

MAY May

JUN June

JUL July

AUG August




SEP September

OCT October

NOV November

DEC December

1ST 1st day of the month

2ND 2nd day of the month

: through the

31ST 31st day of the month

SUN1 1st Sunday of the month

SUN2 2nd Sunday of the month

SUN3 3rd Sunday of the month

SUN4 4th Sunday of the month

SUN5 5th Sunday of the month

: :

SAT5 5th Saturday of the month

SUN-1 Last Sunday of the month

SUN-2 Next to last Sunday of the month

SUN-3 Second to last Sunday of the month

SUN-4 Third to last Sunday of the month

SUN-5 Fourth to last Sunday of the month

: :

SAT-5 Fourth to last Saturday of the month

1ST-WEEK2ND-WEEK3RD-WEEK4TH-WEEK5TH-WEEK6TH-WEEK

First week of the month through the sixth week of the month.(The first week includes those days which precede and includethe first Saturday; the second week includes those days whichfollow the first Saturday and precede and include the secondSaturday; and so on.)

WOY1:WOY53

First week of the year through the 53rd week of the year.

WOY-1:WOY-53

Last week of the year through the 52nd to last week of the year.

7-42 Online Guide



DAY1OF2DAY2OF2DAY1OF3DAY2OF3DAY3OF3:DAY6OF6

According to a cycle lasting from one to six days. The base datefor all cycles is Jan 1, 1900. To determine where a specific datefalls within each cycle, see the Date Translation Table which isgenerated as part of each simulation run. This will tell you, forexample, that May 27, 1984 is the first day in a three-day cycleand the fourth day in a five-day cycle.

WEEK1OF2WEEK2OF2WEEK1OF3WEEK2OF3WEEK3OF3:WEEK6OF6

According to a cycle lasting from one to six weeks. The basedate for all cycles is Jan 1, 1900. To determine where a specificdate falls within each cycle, see the Date Translation Tablewhich is generated as part of each simulation run. This will tellyou, for example, that May 27, 1984 falls in the first week in atwo-week cycle and in the last week in a five-week cycle.

DOM-1:DOM-31

Last day of the month through the 30th to last day of themonth.

Y1994:Y2020

Year 1994 through year 2020.

LEAP-YEAR Leap year.


7.10 Workday Conditions


To use these workday conditions, you must use the Datetable Definition panel todefine workdays and holidays for three years: last year, this year, and next year. Thenyou can consult the Date Translation Report in the Reports Guide to see what workdayconditions are satisfied on any given day. The following criteria keywords can only beused if the schedule or job is selected by a date table.


WDAY All workdays (days shown in high intensity on the date table).

HDAY All holidays (days shown in low intensity on the date table).

WDOW1:WDOW7

First workday of the week through the seventh workday of theweek. (Any day shown in high intensity on the date table iscounted as a workday.)

WDOW-1:WDOW-7

Last workday of the week through the 6th to last workday ofthe week. (Any day shown in high intensity on the date table iscounted as a workday.)

WDOM1:WDOM31

First workday of the month through the 31st workday of themonth. (Any day shown in high intensity on the date table iscounted as a workday.)

WDOM-1:WDOM-31

Last workday of the month through the 30th to last workday ofthe month. (Any day shown in high intensity on the date table iscounted as a workday.)

WWOM1:WWOM6

First work week of the month through the 6th work week of themonth. (Any week with at least one workday is counted as awork week.)

WDOY1:WDOY-1

First workday of the year through the last workday of the year.(Any day shown in high intensity on the date table is counted asa workday.)

WWOM-1:WWOM-6

Last work week of the month through the 5th to last work weekof the month. (Any week with at least one workday is countedas a work week.)

WWOY1:WWOY53

First work week of the year through the 53rd work week of theyear. (Any week with at least one workday is counted as a workweek.)

WWOY-1:WWOY-53

Last work week of the year through the 52nd to last work weekof the year. (Any week with at least one workday is counted asa work week.)

7-44 Online Guide



RD01 = -nn:RD31 = +nn

So many workdays before (-nn) or after (+nn) the first day ofthe month (RD01) or the second day of the month (RD02) orthe third day of the month (RD03) and so on, up to thethirty-first day of the month (RD31). For example, to select ajob on the fifth workday after the 14th of the month, specifyRD14 = +5. To select a job on the third workday before the25th of the month, specify RD25 = -3. (nn may range from -31to +31, a blank must precede and follow the equal sign, and aleading zero is not required with a one-digit number. Also, nnequal to + or -0 causes selection on the specified relative day ofthe month. However, if that day is a holiday, the job will not beselected at all that month.)

HDAY1 If the current date plus 1 day is a holiday

: :

HDAY31 If the current date plus 31 days is a holiday

HDAY-1 If the current date minus 1 day was a holiday

: :

HDAY-7 If the current date minus 7 days was a holiday


7.11 Accounting Conditions


To use these accounting conditions, you must use the Datetable Definition panel todefine which days are accounting days, when each period ends, and when theaccounting year ends. (Periods can be accounting periods, production periods, salescycles, or any other unit of time.) You must do this for three years: last year, this year,and next year. Then you can consult the Date Translation Report in the Reports Guideto see which accounting conditions are satisfied on any given day.

If you have defined a prefix on the Datetable Definition panel, substitute that prefixfor the x in the words below (for example, BDAY or CDOM or DMOY or GWOM).If you have not defined a prefix, substitute A for the x: ADAY, ADOM, AMOY, orAWOM). If you use ADAY in a criteria statement, accounting conditions will betaken from the A version of the date table (the default version). If you use BDAY in acriteria statement, accounting conditions will be taken from the B version of the datetable. Workday and holiday conditions are always taken from the A version. You musthave defined an 'A' date table prefix prior to defining any other prefix for a date table.


xDAY All accounting days (days designated on the date table) by A oranother prefix.

xDOM1:xDOM40

First accounting day of the period through the 40th accountingday of the period. Any day designated by A (or another prefix)on the date table is counted as an accounting day. To use thesecriteria, you must define at least two accounting periods on thedate table. To do this, go through the date table and designatethe end of each period by typing a P on any date. (The end ofthe period defaults to the last day of each month.)

xDOM-1:xDOM-40

Last accounting day of the period through the 39th to lastaccounting day of the period. Any day designated by A (oranother prefix) on the date table is counted as an accountingday. To use these criteria, you must define at least two periodson the date table. To do this, go through the date table anddesignate the end of each period by typing a P on any date.(The end of the period defaults to the last day of each month.)

xMOY1:xMOY53

First period of the accounting year through the 53rd period ofthe accounting year. To use these criteria, you must designatethe ends of two accounting years. To do this, define date tablesfor two years and designate the end of each accounting year bytyping an E on any date. (The end of the accounting yeardefaults to the last day of each year.)

7-46 Online Guide



xMOY-1:xMOY-53

Last period of the accounting year through the 52nd to lastperiod of the accounting year. To use these criteria, you mustdesignate the ends of two accounting years. To do this, definedate tables for two years and designate the end of eachaccounting year by typing an E on any date. (The end of theaccounting year defaults to the last day of each year.)

xWOM1:xWOM10

First accounting week of the period through the 10th accountingweek of the period. (Any week with at least one accounting daycounts as an accounting week.) To use these criteria, you mustdefine at least two periods on the date table. To do this, gothrough the date table and designate the end of each period bytyping a P on any date. (The end of the period defaults to thelast day of each month.) For example, if the period ends onTuesday, October 31, then Wednesday, November 1 throughTuesday, November 7 would be the xWOM1. Therefore,Wednesday, November 8 through Tuesday, November 14 wouldbe xWOM2.

xWOM-1:xWOM-10

Last accounting week of the period through the 9th to lastaccounting week of the period. (Any week with at least oneaccounting day counts as an accounting week.) To use thesecriteria, you must define at least two periods on the date table.To do this, go through the date table and designate the end ofeach period by typing a P on any date. (The end of the perioddefaults to the last day of each month.)


Chapter 8. Using the Autoscan Command File

Autoscan command file processing allows you to make arrangements for futuredatabase updates without affecting today's workload. For example, you are now ableto change a job's predecessors for the next autoscan day without affecting today'sworkload by using the autoscan command file.

■ Job and schedule criteria changes can be implemented without affecting today'sworkload.

■ Database maintenance commands can be set up in advance to define, alter, anddelete job or schedule records, thereby reducing overtime and weekend work.

■ All command can be syntax checked and analyzed ahead of time to ensure that thecommands themselves can be executed without error and that predecessordeadlocks are not inadvertently introduced. This can be done through batch reports(analyze, successor chain, simulation and forecast).

■ Database maintenance commands must be contained within a PDS member orsequential DSN (recfm=FB, lrecl=80) identified by ddname CAIJDCF. You needto specify CAIJDCF in the monitor startup procedure if you need autoscancommand file support.

Example:

//CAIJDCF DD DSN=cai.dcfin(CAIJDCF),disp=shr

■ Commands are executed at autoscan time but before any jobs have been selected.Commands are executed only if today's date falls within the effective andexpiration date, which may be specified as the last two parameters.

Example:

� �DEFINE JBR N=newjob,S=schdule1,LIBTYPE=pds,EFFDATE=�3�3�3,EXPDATE=�3�3�3

DEFINE JCR N=newjob,S=schdule1,CRI='job1 schdule1',EFFDATE=�3�3�3,EXPDATE=�3�3�3

ALTER JBR N=job1,S=schdule1,LIBTYPE=testlib,EFFDATE=�3�5�3,EXPDATE=�3�5�3

ALTER JCR N=job1,S=schdule1,CRI='mon or tue',EFFDATE=�3�5�3,EXPDATE=�3�5�3

� �

■ Commands will be executed at autoscan time but before any jobs have beenselected.

Chapter 8. Using the Autoscan Command File 8-1

■ Each database maintenance command must have as its last two parameters theeffective date and expiration date.

■ All commands will be syntax checked prior to application, if an error occurs amessage will be issued asking the operator to cancel scheduler or proceed with theremaining commands.

■ It is highly recommended to syntax check those autoscan command file commandsbefore submission or autoscan. Otherwise, monitor shutdown may occur if such anerror is detected right before autoscan. DCFERR=CONT can be set in CAIJGENto avoid such shutdown. See the DCFERR parameter in the Systems ProgrammerGuide. You can syntax check the autoscan command file commands at any timeafter you have updated the autoscan command file by using the SYNCHK DCFcommand.

Example:

// EXEC CAJUTIL�


//SYSIN DD �

SYNCHK DCF

/�

■ The batch reports, analyze, successor chain, simulation and forecast may apply thecommand file to the SIMWORK or UTILWORK copy of the database (see theReports Guide) and check possible database update errors. You just need to addthe CAIJDCF ddname with the desired DCF dsname and specify DCF=YES at thefirst CAJUTIL0 command statement.

Example:

// EXEC CAJUTIL�


//SYSIN DD �

ANALYZE SCHEDULE N=caschd1,UTILWORK=sysda,UTILVOL=xxxxxx,DCF=YES

or

REPORT SCDCHAIN N=caschd1,UTILWORK=sysda,UTILVOL=xxxxxx,DCF=YES

or

REPORT JOBCHAIN N=cajob1,S=caschd1,UTILWORK=sysda,UTILVOL=xxxxxx,DCF=YES

or

ONLY S N=schdule1

FORECAST FD=�3�5�3,FOR=2,SIMWORK=sysda,SIMVOL=xxxxxx,DCF=YES

or

ONLY S N=schdule1

SIMULATE ST=(4�),FD=�3�5�3,FOR=2,SIMWORK=sysda,SIMVOL=xxxxxx,DCF=YES

8-2 Online Guide

� �EDIT ----CAI.DCFIN(CAIJDCF) -------------------------------- COLUMNS ��1 ��72



��1 ALTER JCR NAME=JOBA,SCHEDULE=PAYROLL,JNO=�1,STATION=4�,

��2 CRI='MONDAY AND JOBA',EFFDATE=�5�3�3,EXPDATE=�531�3

��3 ALTER JBR NAME=JOBA,SCHEDULE=PAYROLL,JNO=�1,STATION=4�,

��4 EARLYTIME=�715,EFFDATE=�5�3�3,EXPDATE=�531�3

��5 ALTER JBR NAME=JOBC,SCHEDULE=PAYROLL,JNO=�1,STATION=4�,

��6 SKIP=2,EFFDATE=�5�3�3,EXPDATE=�531�3

��7 � DEFINED JOBC'S ABEND MESSAGE

��8 DEFINE JMR NAME=JOBC,SCHEDULE=PAYROLL,JNO=�1,STATION=4�,

��9 ABENDMSG=OPCON5,EFFDATE=�5�3�3,EXPDATE=�531�3


F1=HELP F2=SPLIT F3=END F4=RETURN F5=RFIND F6=RCHANGE

F7=UP F8=DOWN F9=SWAP F1�=LEFT F11=RIGHT F12=RETRIEVE

� �

Note: An * in the first position is treated as a comment.

Supported Commands: The autoscan command file supports the databasemaintenance commands ALTER, DELETE, and DEFINE for schedules and jobs.Control and batch report commands are not allowed. See the Command ReferenceGuide for more information on the ALTER and DEFINE commands.

Chapter 8. Using the Autoscan Command File 8-3

Chapter 9. Tips

This topic is intended to provide you with some helpful hints on using CA-Scheduler.We begin with some of the most commonly asked questions and follow with adiscussion of some pitfalls. The questions are grouped by topics that parallel thestructure of this guide:

■ Startup tasks

■ Maintaining the database

■ Analyzing the database

■ Daily processing

This organization allows each topic to stand on its own so you can jump from subjectto subject. Do not be concerned about reading this chapter in the order that topicsappear.

Chapter 9. Tips 9-1

9.1 Commonly Asked Questions


This topic consists of a series of questions that are commonly asked. The followingtable lists the questions with cross-references to the pages containing their responses.

Topic See

Startup Tasks 9.1.1.1, “When Should Autoscan be Performed?” onpage 9-4

9.1.1.2, “What Is the General Standard for NumberingStations?” on page 9-4

9.1.1.3, “Should I Use Date Tables or Calendars?” onpage 9-5

9.1.1.4, “When Should I Define a New Date Table Versus aNew Cycle in an Existing Date Table?” on page 9-5

Maintaining theDatabase

9.1.2.1, “How Should I Organize My Schedules?” onpage 9-6

9.1.2.2, “When Should a Job be Staged?” on page 9-6

9.1.2.3, “When Is a Job Submitted?” on page 9-7

9.1.2.4, “What Are Global Parameters and When Are TheyUsed?” on page 9-8

9.1.2.5, “How Can I Run a Job Like an Edit CheckRepeatedly Until its Output Is Correct?” on page 9-10

Analyzing theDatabase

9.1.3.1, “How Can I Prevent Predecessor Loops(Deadlocks)?” on page 9-11

9.1.3.2, “When Should I Run Analyze Reports?” onpage 9-12

9.1.3.4, “When Should I Run Forecasts?” on page 9-14

9.1.3.5, “When Should I Run Simulation?” on page 9-14

9.1.3.6, “How Do I Plan When to Run a New Application?”on page 9-15

9.1.3.7, “How Do I Verify a New Application?” onpage 9-15

9.1.3.8, “How Can I Can Create My Own Reports?” onpage 9-18

9-2 Online Guide


Topic See

Daily Processing 9.1.4.1, “From Where Can I Issue CA-Scheduler ControlCommands?” on page 9-20

9.1.4.2, “What Is the Difference Between FORCE,SUBMIT, RERUN, RUN, ADD, REQUEST, and SREQ?”on page 9-20

9.1.4.3, “When Is the PRED Flag Reset?” on page 9-22

9.1.4.4, “What Happens If CA-Scheduler is Shut Down?” onpage 9-23

9.1.4.5, “What Happens If CAIENF is Shut Down?” onpage 9-24

9.1.4.6, “What Happens If a System Crash Occurs?” onpage 9-24

Chapter 9. Tips 9-3


9.1.1 Startup Questions

9.1.1.1 When Should Autoscan be Performed?

Autoscan is the daily process that purges completed jobs from the CA-Scheduler activeworkload, backlogs schedules and jobs, if appropriate, and selects the day's workload.CA-Scheduler scans the database, analyzing the selection criteria and placing theselected schedules and jobs onto the active workload.

Note: If using the autoscan command file, it is used at autoscan time.

If your production normally starts at 16:00 and runs during the night with everythingcompleting by 07:00 or 08:00, then autoscan should be run between 08:00 and 16:00.Run autoscan at a time when your machine load is at a low point.

Running autoscan this way gives the production control area a chance to geteverything ready for the day's workload. This includes JCL changes, control statementchanges, data entry work, last-minute changes, and the like.

9.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 60 Print 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 these dataentry 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 name issubmitted. If you specify that the station 39 job is to beautomatically started (AUTO START=YES), it starts at its earlystart time as long as its predecessors and resources are satisfied.

Station 40 CPU processingJobs start when the early start times are met, all predecessorconditions are fulfilled, and resources are available. CPU jobprocessing is automatic unless you override it.

9-4 Online Guide


Station 60 Print processingJobs are automatically posted as ENDED when thecorresponding CPU job is purged from the system (an SMFtype-26 record is generated). These print station jobsautomatically start when their corresponding CPU jobs completeon station 40 and their predecessors and resources are satisfied.

9.1.1.3 Should I Use Date Tables or Calendars?

Date tables and calendars are two different methods used to select schedules and jobsfor a specific day. Date tables provide significantly more flexibility than calendars andshould be used if at all possible. They are a bit more complicated to understand, butentail less maintenance than calendars when going from year to year. Date tables alsoallow multiple accounting periods as well as different holidays.

One area where you will want to use calendars is when the schedule has to runaccording to a set of dates that follows no pattern. Define these individual days oncein a calendar. Then when any schedule runs on those dates, you just give it thatcalendar name for selection.

For most of your application needs, however, use date tables. A detailed discussion onthis matter appears in the 7.2.2, “Date Tables” on page 7-15.

9.1.1.4 When Should I Define a New Date Table Versus a New Cycle in anExisting Date Table?

Keep in mind that a cycle can be an accounting, production, or sales period. You canhave up to twenty cycles defined with any one date table, and any number of datetables. The date table prefixed by the letter 'A' is your default production date table.The other prefixes are variations upon that date table.

Any time you want to schedule a job based on a combination of two or more cycles,you must use the date table prefix; you cannot use different date table names.

Chapter 9. Tips 9-5


9.1.2 Database Maintenance Questions

9.1.2.1 How Should I Organize My Schedules?

A schedule should consist of a group of logically related jobs. This group of jobsusually belongs to one application, but could also be run at the same frequency. Forexample, you could define a Payroll schedule containing all the payroll jobs and itsselection criteria. If certain jobs in the schedule do not run every time the schedule isselected, just define the selection criteria for the exceptional jobs. Or the dailyAccounts Receivable jobs could be contained in one schedule and the weekly AccountsReceivable jobs could be in another. Possibly, the weekly schedule is dependent on thedaily schedule to complete.

Do not organize schedules just by frequency. For example, do not have a Mondayschedule. There should not be one schedule just for REQUESTED jobs, either, unlessit is easily manageable. Instead, try to keep application-related jobs together. Thismakes interdependencies within applications much clearer.

Keep in mind, most options defined for a schedule apply to all jobs in that schedule.You can, however, override these options at the job level.

9.1.2.2 When Should a Job be Staged?

Staging a job means that at autoscan time or whenever the job is manually run withthe RUN command, the job's JCL is moved from the master JCL file (LIBTYPE field)to the CA-Scheduler active workload. This LIBTYPE defaults to the one that appearsin the LIBTYPE installation option of the CAIJGEN macro, but can be overridden atthe schedule level and again at the job level.

Stage a job only if its JCL needs to be changed before it runs or if it has controlstatements that need to be changed or added. You can code Driver procedures toautomate most of the changes to the JCL and control statement setup. Before youdecide to stage JCL, determine how much of the setup can be handled using Driver.

To have a job's JCL staged, you must make the STAGE JCL field be YES on the JobDefinition panel for station 40 and either:

■ Define an EARLY START TIME that gives users enough time to change the JCLor

■ Define the same job to station 39 (the staging station)

Using this first method does not guarantee that the staged JCL can be ready to runbefore CA-Scheduler submits it. A job's EARLY START TIME may arrive before itsJCL has been modified in preparation for submission.

9-6 Online Guide


To ensure that a user at the JCL setup station has enough time to modify and reviewthe staged JCL, use the second alternative mentioned above. The job defined at station39 will be an implicit predecessor of the CPU job at station 40. That means the CPUjob cannot be submitted until the job at station 39 has been manually marked asENDED using the COMPLETE command.

You could, for example, have a daily job that only needs to have its JCL or a controlstatement changed on Fridays. Therefore, you only want to change the JCL on Fridays.You can accomplish this by allowing the CPU job (the one assigned to station 40) tobe selected DAILY and the staging job (the same job name within the same scheduledefined to station 39) to be selected FRI. The job's JCL will always be staged, eventhough you only change it on Fridays. Remember, the station 39 job has to bemanually started or AUTO START=YES must be specified in its definition.

When the JCL has been changed, you mark the job on station 39 completed with theCOMPLETE command.

A job's JCL can be staged (taken from the master JCL file as specified in theLIBTYPE field and placed in the CA-Scheduler active workload) even if staging is notautomatic. That is, regardless of whether you had STAGE=YES, a fresh copy of thejob's JCL will be restaged. Furthermore, you may want to restage JCL for a job withSTAGE=NO. This would be for purposes of changing it due to a rerun condition. Youuse the RESTAGE command to accomplish this. Keep in mind that it will overlay anyJCL that may already be in the active workload for the respective job.

Once the JCL is staged, you can use a variety of editor commands to prepare it forsubmission. In addition to usual text editing, you can perform some special functionswithin the editor:

■ Expansion of Driver procedures embedded in the JCL

■ Display of current values of all Driver reserved-name variable parameters in theJCL

■ Change of values of any Driver reserved-name variable parameters in the JCL

■ JCL syntax checking using CA-JCLCheck if it is installed on your system

Using these functions together is a convenient way to write and test Driver proceduresto automate JCL setup and minimize the need to stage JCL.

The JCL that is staged is purged from the active workload when its associated job ispurged from the active workload.

9.1.2.3 When Is a Job Submitted?

Once a job's ERLYTIME is met, all of its predecessors have completed normally, andits resources (SEPDSNs, and SEPJOBs) are available, then a job can be submitted.

Chapter 9. Tips 9-7


9.1.2.4 What Are Global Parameters and When Are They Used?

Global parameters are user-defined conditions that are predecessors. You can specifythat a schedule or job must wait for a specific global parameter to be set to a specificvalue before the respective schedule or job can be started or submitted.

The three types of global parameters are: numeric, binary (yes or no), andalphanumeric (up to eight characters). Global parameters follow the format:

GBLxnn=value

Where:

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

For example, suppose a set of jobs cannot start without a particular set of tapesarriving from an off-site location. Suppose this is some accounting data, and we give ita name of HERE-NOW. We have to pick a global variable to be set aside for just thispurpose. We can choose GBLC04 since we know no one else is using it. Any scheduleor job that needs the data before it can run will have as part of its criteria language thefollowing string of data:

GBLC�4=HERE-NOW

9-8 Online Guide


Once the tapes have arrived, an operator sets the value of the global parameterGLBC04 to HERE-NOW. At that point, if any schedule or job is waiting for no otherreason but this variable, then the schedule or job starts. From 4.3.9, “Globals” onpage 4-95, update the value of the global variable:

� � --------------------- CA-SCHEDULER 9.� xxyy (SCHD) GLOBALS --------------------

COMMAND ===>

Numeric Values:

GBLA�1 - �4 . . �� . . �� . . �� . . ��

GBLA�5 - �8 . . �� . . �� . . �� . . ��

GBLA�9 - 12 . . �� . . �� . . �� . . ��

GBLA13 - 16 . . �� . . �� . . �� . . ��

Binary Values:

GBLB�1 - �4 . . NO . . . . NO . . . . NO . . . . NO

GBLB�5 - �8 . . NO . . . . NO . . . . NO . . . . NO

GBLB�9 - 12 . . NO . . . . NO . . . . NO . . . . NO

GBLB13 - 16 . . NO . . . . NO . . . . NO . . . . NO

Character Values:

GBLC�1 - �4 . . . . . . . . here-now

GBLC�5 - �8 . . . . . . . .

GBLC�9 - 12 . . . . . . . .

GBLC13 - 16 . . . . . . . .

Enter END to exit.

� �

It is very important to notice that global parameters are not reset automatically.Someone must cause it to happen. Their values are saved on the active workload andalways remain until they are reset to some other value or the active workload isreinitialized. Autoscan does not reset the global parameters.

When you initialize the active workload, all global parameters are set to zero (forA-type), NO (for B-type), or null (for C-type). For example above set GBLC04=NULLfrom globals panel or batch CAJUCMD0.

When you define the criteria for a schedule or job, you can specify which globalparameters and what values they are to contain for use as predecessor conditions thathave to be met before the schedule can be started or the job can be submitted.

One rule you have to be sure to follow is: a NOT reserved word preceding a GBLxnnpredecessor is NOT recognized. Therefore, NOT GBLC01=CICS-UP will have thesame effect as GBLC01=CICS-UP.

Chapter 9. Tips 9-9


9.1.2.5 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 again until youget an indication that the rest of the application can run. You may not know howmany times it will take each day, since it depends on everything being valid.

Two ways to achieve this type of processing are:

■ Using the INTERRUPT field on the job base record

■ Interfacing with CA-Dispatch and/or CA-Opera

To allow a job to be interrupted, you specify INTERRUPT=YES in its Job Definitionpanel. This means that when the job terminates normally, its status will be set toINTERRUPTED instead of ENDED. You can then run the job by using the RERUNcommand. Successors of this job will not run until the job is ended manually using theCOMPLETE command.

At any time during the day, you can go into the status panels and display all jobs thatare in an INTERRUPTED status. So, you can easily see any jobs that are interrupted.

When a job does get interrupted, you can have a message sent to up to four users.These users can be any user name, the master console (OPERATOR), another console(OPERnn where nn is the route code from 1 - 15), or the CA-Scheduler mailbox(MAILBOX). To do this, use the Job Interrupt field in the job's Job Messages panel.

Remember that when a job is to be interrupted, it must be manually posted to dosomething next such as freeing successors to run. Either mark the job as ENDED, orresubmit the job using the RERUN or SUBMIT command. Successor jobs are thenhandled appropriately.

An alternative method of submitting a job repeatedly is by interfacing withCA-Dispatch, CA-Opera, or both. This method has an added benefit in that it canautomate the resubmission process. CA-Dispatch can interrogate a report or SYSOUTdata produced by a job, and if evidence is found that the job ran without error, aCOMPLETE command can automatically be sent to CA-Scheduler. Otherwise, aRERUN or SUBMIT command could be sent, or a message could be sent to a user toverify the output. CA-Opera can interrogate console messages issued by a job, and aprocedure like that described for CA-Dispatch can be used to handle the job accordingto the contents of those messages.

9-10 Online Guide


9.1.3 Questions About Analyzing the Database

9.1.3.1 How Can I Prevent Predecessor Loops (Deadlocks)?

Predecessor loops are also called predecessor deadlocks. A predecessor deadlock existswhen 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.

As you can see, JOBX is a predecessor of JOBA, but cannot run until JOBB hasended. Since JOBB will not run until after JOBA has ended, we have a deadlock.

You could imagine how complicated this would be to resolve if we had a hundredjobs, each with many predecessors. It is extremely difficult to detect a deadlock unlessyou use the Analyze Report.

To obtain the Analyze Report, run the CA-Scheduler utility program (CAJUTIL0) withthe batch command ANALYZE. You can check specific jobs and/or schedules or youcan give a range of jobs and/or schedules. For example, you can analyze all schedulesthat begin with the first three characters PAY. Any time you make significant changesto jobs, schedules or both, run this report to ensure that your changes have notintroduced deadlocks. You should produce it any time the criteria for a job or scheduleis changed.

Instead of getting the comprehensive Analyze Report, you can use the LIST=NO orLIST=ERR operand to request that just the errors be reported.

The ANALYZE command can also be issued online from any of these panels:

■ Job Maintenance

■ Job Directory

■ Schedule Maintenance

■ Schedule Directory

For details on how to issue ANALYZE online, see 6.1.1, “Analyze Job” on page 6-4and 6.1.2, “Analyze Schedule” on page 6-6.

Another way to detect deadlocks is to generate the Successor Chain List report eitherfrom batch or online in the 6.10, “Successors” on page 6-21. This is especially usefulfor dynamically ADDed jobs to ensure that the added job did not create a deadlock.

Chapter 9. Tips 9-11


One technique for eliminating deadlocks is to use the CA-Scheduler job number (JNO)feature when defining jobs. For example, if JOBA and JOBB in SCHDA both run onMondays and Wednesdays, but on Mondays JOBA must run first and on WednesdaysJOBB must run first, you could define the jobs as:

JOBA-�1 SCHDA has criteria of MON

JOBA-�2 SCHDA has criteria of JOBB-�2 SCHDA

JOBB-�1 SCHDA has criteria of JOBA-�1 SCHDA

JOBB-�2 SCHDA has criteria of WED

This allows the jobs to run without any deadlock.

9.1.3.2 When Should I Run Analyze Reports?

The analyze report allows you to see errors that you might have made while definingSBR, SCR, SIR, SNR, SRR, JBR, JCR, JIR, JMR, JRR, and JSR records.

This report should be run periodically to ensure you have no definition errors to theserecords.

9.1.3.3 What Effect Does a Deadlock Have?

When job predecessors loop, it is called a deadlock. Deadlocks can have some strangeeffects on your workload, and seemingly unrelated changes can have unexpectedresults on how work is selected.

Example 1: When CA-Scheduler is evaluating criteria and detects a deadlock, ittreats the predecessor as being not selected. For example:

JOBA SCHDA has criteria of JOBB SCHDA

JOBB SCHDA has criteria of JOBA SCHDA

When JOBA's criteria is being evaluated, CA-Scheduler realizes that it has to evaluateJOBB first. When it evaluates JOBB, it detects the deadlock with JOBA. Criteria isevaluated as a series of logical TRUE and FALSE conditions, with deadlocks acting asFALSE. Since the criteria of both JOBA and JOBB evaluates to a FALSE, neither jobis selected.

The order that CA-Scheduler evaluates criteria can have an impact on how deadlockedjobs are selected. During autoscan, CA-Scheduler evaluates all schedules first, beforelooking at any jobs. The schedules are evaluated in alphabetical order. After all of theschedules have been evaluated, CA-Scheduler evaluates the jobs in each schedule thatwas selected. Again, the jobs are evaluated in alphabetical order within each schedule.

Example 2: This order changes when predecessors are included in criteria. Apredecessor must be evaluated before its successor. For example:


JOBB SCHDA has criteria of JOBC SCHDA

JOBC SCHDA has criteria of WDAY

9-12 Online Guide


In this case, JOBB must be evaluated before JOBA, since JOBA's criteria references it.JOBC must be evaluated before JOBB. In this example, the jobs are evaluated in theorder JOBC, JOBB, JOBA.

Example 3: Look at an example of how this ordering can affect deadlocks:

Part 1

SCHDA has auto select set to YES, no criteria

JOBA SCHDA has criteria of JOBB SCHDA OR WDAY

JOBB SCHDA has criteria of JOBA SCHDA

CA-Scheduler tries to evaluate JOBA first, but detects that JOBB must be done beforeJOBA. While evaluating JOBB, the deadlock with JOBA is detected, so JOBB is notselected. When CA-Scheduler gets back to finishing JOBA, it treats the "JOBBSCHDA" as a FALSE condition. JOBA's criteria, however, has an OR condition. Iftoday is a workday, JOBA's criteria evaluates as FALSE OR TRUE, which is a TRUE.JOBA is selected. Since JOBB was not selected, JOBA will not wait on it.

We can define another job in schedule PAYROLL as:

Part 2

PAYROLL has auto select set to YES, no criteria

PAYROLL comes before SCHDA, so the jobs in schedule PAYROLL are evaluatedbefore the jobs in schedule SCHDA. JOBC needs JOBB, so JOBB must be evaluatedfirst. But JOBB needs JOBA, so JOBA is done first. JOBA needs JOBB, so thedeadlock is detected. As we saw above, however, the FALSE from the deadlock isORed with the TRUE from WDAY, so JOBA is selected.

CA-Scheduler then backs up to finish JOBB. Since JOBA was selected, JOBB will beselected. And since JOBB was selected, JOBC is selected. Because JOBB wasselected, JOBA must wait for it. But because JOBA was selected, JOBB must wait forit! None of the jobs will run without manual intervention.

If we moved JOBC from schedule PAYROLL to schedule XYZ (which comes afterschedule SCHDA), then only JOBA is selected. This happens because by the timeCA-Scheduler gets to JOBC, JOBA and JOBB have already been evaluated as inExample 3 Part 1.

Example 4: The NOT keyword can also cause some confusion. For example:

JOBA SCHDA has criteria of NOT JOBB SCHDA

JOBB SCHDA has criteria of NOT JOBA SCHDA

Again, CA-Scheduler tries to evaluate JOBA first, but has to move on to JOBB. Whileevaluating JOBB, the deadlock is detected. The criteria for JOBB is then evaluated asNOT FALSE, which is TRUE. JOBB is selected. JOBA's criteria now becomes NOTTRUE, which is FALSE. JOBA is not selected.



Example 5: One last example:


JOBB SCHDA has criteria of NOT JOBA SCHDA

This is the same as example 4 except that JOBA's criteria does not have the NOT.Now both jobs are selected, but neither will run automatically because they are waitingon each other.

9.1.3.4 When Should I Run Forecasts?

The forecast report allows you to predict which schedules and jobs will be selected ona future date as well as providing a comprehensive set of reports detailing such.

When establishing a complex criteria for a schedule or job, run forecasting to verifythe selection. You can do this by only including the schedules and/or jobs that youdesire. This would be the primary reason for running forecasting.

Another reason for running forecasting would be to obtain a hardcopy of run books fora specific day, group of days, or schedules and/or jobs within a set of days. These runbooks contain job information obtained from the database and from workloaddocumentation entries specified by the DISPLAY KEY field.

The skip option on the JBR is not honored on this report.

9.1.3.5 When Should I Run Simulation?

The simulation function simulates the autoscan process and the manner in which jobswould run on the real system. Such things as job concurrency, resources, andpredecessor constraints are taken into consideration. Simulation produces a set ofdetailed reports showing when jobs will run and whether they will complete on time.

Normally, simulation is run to determine the effect of a new application on the rest ofthe workload. This helps you determine in advance whether the requested frequency ofrunning the application is viable. That is, if you find that the new application cannot fiton Wednesdays without making a lot of jobs late, you could try to run it on anotherday. It may turn out that it does not absolutely have to run on Wednesdays. Therequesting department may be able to run it on Thursdays just as easily. You can makethese decisions before establishing policy and before finding that you do not have theresources to handle it. Simulation could also be run to determine the effect of addingnew resources, such as tape drives or a faster CPU. By using the OVERRIDERESOURCE command, you can add the new tape drives, or by using theFACTOR=factor keyword on the same commands, you can cause the simulation tochange the current average time for jobs, to reflect the faster CPU.

You may also want to run simulation as part of normal daily production to determinewhat is going to happen that particular day. It provides you with a plan of what toexpect and when to expect it. When you do this, you can optionally use the simulatedstart times as the early time of the jobs for submission. When you do, it ignores theearly start time that you had on the database.

9-14 Online Guide


Another reason to run simulation is to check the syntax of the JCL before actuallyprocessing the jobs. To do this you must have CA-JCLCheck installed and active onyour system. For details on this function, see the SIMULATE and SYNCHK GROUPcommands in the Command Reference Guide.

The skip option on the JBR record is not honored on this report.

9.1.3.6 How Do I Plan When to Run a New Application?

You first define your application completely. Temporarily set LIBTYPE = TESTLIBin schedule base records. Now run analyze. Then run simulation or forecast (see thediscussion of simulation on 9.1.3.5, “When Should I Run Simulation?” on page 9-14)with an ONLY command just for the schedules in the new application. This willensure that everything is the way you want it.

Once everything looks correct, you can run the application in test mode with thenormal day's production and review its effect on the day's workload.

9.1.3.7 How Do I Verify a New Application?

You should follow these five steps in verifying a new application.

Step #1: Analyze Report: The Analyze Report provides a detailed audit of allinformation pertaining to the schedule(s) being requested. From this report, you have acomplete list of everything that you keyed in for the new application. You also get aset of error messages that identify predecessor/successor deadlocks as well as anyreferences to jobs, predecessors, date tables, and stations that are not on the database.Review this report carefully. Sometimes you may prefer to print just the errors usingthe LIST=NO option.

To obtain this report, use the JCL described in the Reports Guide. You can alsoobtain it by issuing the ANALYZE command online in the schedule maintenance andjob maintenance panels.

This example analyzes all schedules which begin with the characters "APPL1S":

// JOB ...


//SYSIN DD �

ANALYZE SCHEDULE NAME=APPL1S�

//



Step #2: Forecast: Run the forecast component for at least a month of dates andobtain the Job Summary Report (SUMMARY). You do this for the schedules thatwere built for the new application. Through use of the ONLY command, only the newschedule names are supplied causing just the new application to be analyzed. Throughuse of the FORECAST command with the object of SUMMARY, you will obtain justthe Job Summary Report. The following example contains three schedules to beselected over a one month period with only the Job Summary Report being produced.

// JOB ...


//SYSIN DD �

ONLY SCHEDULE N=APPL1S1�



FORECAST SUMMARY MONTHOF=�7�3

//

Step #3: Simulation: Run the Simulation component for each unique day on whichthe new application will run. During a month, this may only be three days: a daily, aweekly, and a monthly.

You would use the ONLY and SIMULATE commands to accomplish this.

You want to verify that the jobs were selected on the days on which you intendedthem to be. Then you want to verify that they were scheduled in the proper sequence:predecessor relationships are properly followed. If you have jobs that are backlogged, agood chance exists that they may have a predecessor deadlock. Also, if jobs arebacklogged, check the accuracy of early start times and run times.

9-16 Online Guide


Step #4: Test: Run the schedule in test mode. Use the online tracking RUN Scommand.

Use the STATUS command to verify that jobs are scheduled correctly, on those dates,and with the correct predecessors. Keep in mind that since LIBTYPE=TESTLIB,CA-Scheduler will submit jobs that execute the CAJUTSTB test program. You can useTESTPARM on individual jobs' base records to cause the test program to abend, topass a nonzero completion code, and to have it wait for a number of seconds. Bydoing that, you can test the effect of abending and failing jobs on the rest of theschedule.

After the jobs in the schedule run to your satisfaction, you can now alterLIBTYPE=TESTLIB, in the SBR, to your production LIBTYPE. Also ensure thatAUTO SELECT is set to YES. Once you do that, the schedule and its jobs will beautomatically selected, starting at the next autoscan.

Step #5: Driver: If jobs in a schedule require frequent JCL changes or controlstatement setup before job submission, you should develop Driver procedures toautomate the JCL changes and the control statement setup.



9.1.3.8 How Can I Can Create My Own Reports?

As part of CA-Scheduler you have a component called CA-Earl. CA-Earl is ageneralized report writing facility for which you are provided a set of sample reports.This sample set of reports includes reporting on:

■ Database

■ History file

■ Active workload

The source code for these CA-Earl reports is provided to you. The following lists thereports and the names of the source members in which the source is contained.

Database CAJINM01 Basic job information by schedule

CAJINM02 Basic job information by station

CAJINM03 Job criteria by schedule

CAJINM04 Job step information by schedule

History file CAJINH04 Abended job profile

CAJINH03 Completed job profile

CAJINH07 Forced and canceled jobs

CAJINH05 Late job profile

CAJINH06 Pending job profile

CAJINH01 Scheduled job status by schedule

CAJINH02 Scheduled job status by station

Active workload CAJINT04 Abended job profile

CAJINT07 Canceled jobs

CAJINT03 Completed job profile

CAJINT06 Pending job profile

CAJINS06 Pending schedules report

CAJINS01 Schedule status

CAJINT01 Scheduled job status by schedule

CAJINT02 Scheduled job status by station

Workloaddocumentation

CAJIND02 Documentation directory and list

CAJIND01 Documentation directory list

CAJINTD1 Documentation with the activeworkload

9-18 Online Guide


Although each of the above reports is written in CA-Earl and provided for you, youhave the ability to tailor any of them to your own needs. See the Reports Guide fordescriptions of each of these samples in detail.

Active workload copyof JCL

CAJING02 Staged JCL directory and list

CAJING01 Staged JCL library directory list



9.1.4 Daily Processing Questions

9.1.4.1 From Where Can I Issue CA-Scheduler Control Commands?

Quite a few control commands are provided within CA-Scheduler. They do everythingfrom displaying status to shutting down CA-Scheduler. For detailed information aboutusing these commands, see 1.6, “CA-Scheduler Commands” on page 1-10, 4.1,“Schedule Status” on page 4-2, 4.2, “Job Status” on page 4-16, 4.3, “Commands” onpage 4-43, and the Command Reference Guide.

However, CA-Scheduler offers a number of different places where you can enter thecontrol commands. This is done to make it practical for you.

Operator Console: Any control command can be issued from the operator consoleby directing it to CA-Scheduler. Prefix the command with "F taskname,". The defaulttaskname is CASCHD.

Batch Program (CAJUCMD0): Control commands can be issued from a batchprogram called CAJUCMD0. This means that you could embed a step calling thisprogram in your production JCL that could take certain actions dependent on, forexample, condition code settings. Since you have the ability to cause anyCA-Scheduler control command to be issued, you could send messages to specificusers or the operator console, start another job, or set global variables.

You can even issue these commands based on conditions coded in an IF statement.You can test against the status of other jobs, any schedule, user-defined globals, andjust about anything else you can think of. The "Tracking Commands" chapter in theCommand Reference Guide describes this in detail.

9.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. Thefollowing describes how each command works.

FORCE Causes a schedule on the active workload to be started regardless ofwhy it is currently waiting. It also can cause a job to be submittedregardless of why it is currently waiting. You can FORCE a job aslong as its status is not STARTED, ENDED, or OS PURGED. Youcannot FORCE a job that has JCL already in the queue if the statusis SUBMITD, SUBMIT IN PROGRESS, or UNKNOWN.

9-20 Online Guide


SUBMIT and RERUNCause a job to be resubmitted. It will not wait for an early time orfor predecessors: the job is submitted immediately. If the schedule inwhich the job exists is not in START status, it will be set to STARTstatus. Use RERUN or SUBMIT instead of FORCE when a job hasabended, failed, ended, canceled, or been interrupted. FORCE isused to make a job start the first time. RERUN substitutes DRIVERrestart parameters if LIBTYPE=DRIVER is defined and the JCL isnot staged or restaged. The only difference between SUBMIT andRERUN is which Driver parameters they use: SUBMIT uses thenormal parameters while RERUN triggers the restart parameters.

RUN Causes a schedule or job that exists on the database to be added tothe active workload. These schedules and jobs are ones that were notselected in today's workload or they may have been canceled orcompleted. This is different than FORCE and RERUN in that a freshcopy is obtained and all times, predecessors, and resources areproperly evaluated.

If the job or schedule is already on the active workload (it would bein a completed or canceled status), then the older one is purged fromthe active workload. If the job is on the active workload and notcompleted or canceled, then the RUN command is in error.

With the RUN command, you can place the schedule or job in aHELD status. This will give you a chance to take any other manualactions you deem appropriate. Further, when you use the RUNcommand to pull in a schedule, you can give it a date so that onlyapplicable jobs in the schedule are selected.

ADD Causes a job to be added to the active workload. The job does nothave to be on the database. If it is on the database, you would usethis command instead of the RUN command if you wanted tochange any keyword values. Normally, you only use ADD forone-time jobs.

You do not have to specify a schedule name. If you do, it will beadded to that schedule. If you do not specify a schedule name, itwill use a schedule name of $DYNxxxx, where xxxx is the SYSIDof the system from which the command was issued.

REQUEST and SREQCause a REQUESTED schedule or job to be activated. This means itis moved from the INACTIVE queue to the ACTIVE queue. Oncein the ACTIVE queue, it is handled normally.

The way that a schedule or job is made 'on-request' is by giving it aselection criteria of REQUESTED. A REQUESTED criteria causesthe schedule or job to be selected every day and placed on the activeworkload.



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 SREQ commandhandles successors differently: SREQ does not activate a successor ifit involves other REQUESTED jobs. A successor of an SREQedschedule or job is not moved to the ACTIVE queue if:

■ The successor's criteria statement contains the keywordREQUESTED or

■ That successor is also the successor of some otherREQUESTED job in the INACTIVE queue.

A separate subtopic devoted to requested jobs is in the next chapter.If you plan to use this facility, you should review it.

Summary: For jobs in the active workload:

■ 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 REQUEST or SREQ for requested jobs.

For jobs not on the active workload:

■ Use ADD to put a job on the active workload if it does not exist on the databaseor 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.

9.1.4.3 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 use thekeyword PRED, the predecessor is to complete within the autoscan day.

When you specify PRED in front of the predecessor, it means the predecessor was tohave completed since the last time this schedule or job was run. However, anexception exists. If the PRED is a schedule or job that is in today's workload, it willwait for that specific one to complete. For example, if a job has a predecessor of PRED

DSN JOBA.MASTER, the output data set JOBA.MASTER must have been closed at leastonce between each running of that job. If the job is run weekly, then it must have beenclosed at least once during the last week.

Normally in the selection process (during autoscan), job names cause selection if thepredecessor job was selected. When PRED precedes a schedule name or job name, it isnot used in determining selection, but is a predecessor condition only. All othercriteria rules still apply.

9-22 Online Guide


9.1.4.4 What Happens If CA-Scheduler is Shut Down?

Every time CA-Scheduler is started, either from a normal shutdown or from a systemcrash, it takes the following steps:

1. Reads the active workload for schedules that belong to the local CA-Scheduler. IfMCPU=NO, this is all schedules. For MCPU=YES, this is schedules with thelocal system's SYSID.

2. If RHOLD=YES was specified, then all jobs that have not yet been submitted(that is, waiting on early start times, waiting on predecessors, or the schedule hasnot yet started) are marked AUTO RCVRY HELD. These jobs are not submittedby CA-Scheduler until a RELEASE AUTO command is issued.

3. If a job was in SUBMIT IN PROGRESS or SUBMITTED status, the job ischanged to UNKNOWN status. CA-Scheduler does not know the current status ofthe job.

4. If a job was in STARTED status, CA-Scheduler queries JES to determine if thejob is still active. If the job is still running, CA-Scheduler leaves the status asSTARTED. Otherwise, the status is changed to UNKNOWN.

5. CA-Scheduler requests any events from CAIENF since the last event received.These events are used to "catch up" with jobs that may have started or endedwhile CA-Scheduler was not active.

If an event is received for a job currently in UNKNOWN status, the job's status isupdated accordingly as long as CA-Scheduler has received a JOBINIT eventfor the job.

If a JOBINIT has not been received for the job, then the job will NOT be tracked.

Example: CA-Scheduler has submitted four jobs: JOB1, JOB2, JOB3, and JOB4.

Time Event

10:05 JOB1 and JOB2 start. CA-Scheduler receives JOBINIT events fromCAIENF

10:06 CA-Scheduler shut down

10:07 JOB1 ends normally

10:08 JOB3 starts and ends normally

10:09 CA-Scheduler started:JOB1 was started, is not currently active, so is marked UNKNOWNJOB2 was started, is still running, so is marked STARTEDJOB3 was submitted, so is marked UNKNOWNJOB4 was submitted, so is marked UNKNOWNENF recovery obtains the following events:

JOBTERM for JOB1--JOB1 marked ENDEDJOBINIT for JOB3--JOB3 marked STARTEDJOBTERM for JOB3--JOB3 marked ENDED



At the end of CAIENF recovery, only JOB4 is still marked UNKNOWN. When itstarts, its status will change to STARTED.

9.1.4.5 What Happens If CAIENF is Shut Down?

| CA-Scheduler takes the following actions when CAIENF is shut down:

1. Any jobs that have not yet been submitted (that is, waiting on early start time orwaiting on predecessors) will be marked ENFDOWN HELD.

2. For jobs that have been submitted but have not yet started, CA-Scheduler willattempt to hold the jobs in JES. CA-Scheduler will show the jobs as ENFDOWNHELD.

3. Any jobs that have already started will be marked UNKNOWN.

When CAIENF is started again, CA-Scheduler will:

1. Release all jobs marked ENFDOWN HELD. Jobs that were submitted and held inJES are released.

2. Jobs that were submitted now have a status of UNKNOWN. CA-Scheduler doesnot know if the job ran while CAIENF was down. If the job subsequently starts,CA-Scheduler changes its status to STARTED.

3. Jobs that were STARTED are checked to see if they are still running. If the jobsare still active, they are marked STARTED. Otherwise, they are left asUNKNOWN.

Note: Any steps that finished while CAIENF was not available are not reportedto CA-Scheduler. CA-Scheduler may mark a job as successful when one ofthese steps received a bad return code.

9.1.4.6 What Happens If a System Crash Occurs?

When CA-Scheduler is started up after a system crash, the same steps are taken as fora normal start of CA-Scheduler. See 9.1.4.4, “What Happens If CA-Scheduler is ShutDown?” on page 9-23.

9-24 Online Guide


9.1.5 What Do I Do with Jobs in UNKNOWN Status?

The STATUS UNKNOWN command displays jobs in UNKNOWN status. Jobs inUNKNOWN status may resolve themselves or may require manual intervention. Anormal restart of CA-Scheduler should automatically resolve all UNKNOWN statusjobs. If CAIENF is restarted or the system crashes, UNKNOWN status jobs willprobably have to be resolved manually.

If an UNKNOWN job has successfully completed, you can use the COMPLETEcommand (with CPU=Y) to inform CA-Scheduler. If the UNKNOWN job needs to bererun, you can use the FORCE command.



9.1.6 Pitfalls

9.1.6.1 Using Control Commands on the Status Panels

You are able to issue control commands from a status display by just keying in thecommand (first four characters) to the left of the schedule or job. You can even issuemore than one command at a time. Therefore, the pitfall:

While on the subject of control commands in status displays, here is a clarification, nota pitfall. Just remember, when using the commands in this manner, that they areprocessed sequentially and stop being processed upon encountering an error. Forexample, there is no reason to cancel a schedule and then the jobs in that schedule.

Pitfall When keying in a command to the left of a schedule or job in theStatus panels, be sure you are on the correct line. It is easy tocancel the wrong job.

9.1.6.2 Canceling and Purging a Job

Suppose you have a schedule that consists of four jobs: JOB1 through JOB4. JOB2requires JOB1 JOB3 requires JOB2 and so on. If you CANCEL JOB3, whether youalso PURGE it, JOB4 always waits for JOB3. You can manually override this with aPOST or FORCE command.

Suppose that JOB3A has JOB3 as a predecessor. If JOB3 is canceled and not purged,the predecessor JOB3 is ignored when you issue a RUN JOB3A command becauseJOB3 has been canceled but is still on the active workload. If you purge JOB3 beforeissuing the RUN JOB3A command, JOB3A waits for JOB3 to complete. You have toRUN JOB3 to put JOB3 back on the active workload.

Do not use the PURGE command unless you plan to put the job back on the activeworkload by issuing a RUN command.

Pitfall Predecessors for jobs added to this day's production using theRUN command are ignored if they have been canceled by theCANCEL command but not deleted from the active workload bythe PURGE command.

9-26 Online Guide


9.1.6.3 Changing Criteria on Selected Jobs

When a schedule or job has been selected, CA-Scheduler reviews its predecessorcriteria as it exists on the database. What this means is that if you have a schedule offour jobs: JOB1, JOB2, JOB3, and JOB5, where JOB2 requires JOB1, JOB3 requiresJOB2, and JOB5 requires JOB3. The schedule has been selected and is on the activeworkload. You then add JOB4 and change the predecessor criteria of JOB5 to nowalso require JOB4. If JOB5 had not yet started, when it is evaluated to start, it willrequire JOB4, but JOB4 was never selected. Therefore, JOB5 will never be submitted.It will always be awaiting JOB4. If this happens, we recommend that you CANCELand PURGE JOB4 and then issue an ADD command for JOB4.

Pitfall When changing predecessor criteria on the database for jobsthat are selected and are already on the active workload, beaware that the jobs on the active workload will be evaluatedbased on the most current data on the database. Do not changethe criteria of active jobs unless the job is canceled and purgedoff the active queue and then rerun.

9.1.6.4 Backlogging Jobs Over Two Autoscans in $MVS, $DYN and UserDefined Schedules

The subject of backlog is covered in a topic called 10.4, “Backlogged Work” onpage 10-13. When a schedule gets backlogged (autoscan occurred before the schedulecompleted) due to the first autoscan occurring, it is handled as you would expect. If,however, it does not finish before the next autoscan (meaning it has been in thesystem for 48 hours), when it does finish, the new schedule that is loaded is evaluatedfor the autoscan day on which it is loaded. This means that if a schedule that isselected on both Monday and Tuesday and has its Monday's version backlogged untilWednesday; Tuesday's version will never be run. That is because the evaluation takesplace when Monday's schedule completes which is Wednesday, but it does not run onWednesday. Always watch backlogged work carefully.

The $MVS and $DYN schedules also get backlogged if these schedules never go toENDed status. There is no cleanup for the jobs that are in ENDed status.

Pitfall Backlogged work that goes beyond a 48-hour period can be lostif not monitored carefully.



9.1.6.5 Resetting Global Parameters

Global parameters are initialized only when the active workload is initialized. They arenot reset at autoscan time. Once a value of a global parameter is set, it is only resetwhen someone actually changes its value to something else. That is, predecessorevaluation of schedules and jobs takes place based upon the current value of the globalparameter regardless of when that value is set.

If the above is not the way in which you desire to operate, you could have a batch jobthat is submitted at a specific time (say immediately following autoscan) that executesthe CA-Scheduler program CAJUCMD0 and supplies transactions that set the globalvariables to the values you want. Therefore, the pitfall:

Once a global parameter is set to a specific value, all unsatisfied predecessors arere-evaluated. If any schedules or jobs are waiting for that global parameter to take onthat value, those global predecessors are marked as satisfied. Satisfaction can only bereversed by changing the GBLxnn parameter and canceling the affected schedule orjob and then issuing a RUN command to reselect that schedule or job.

Note: If the global displays a blank value, it means that global has never been setsince the last format of the active workload.

Formatting of the active workload causes all globals to be reset to their defaultvalues.

Pitfall A global parameter only gets set. If you want it reset, you mustset it to another value. No such thing as resetting a globalparameter exists.

9-28 Online Guide

Chapter 10. Techniques

This chapter is intended to clarify various areas within CA-Scheduler. In someinstances, techniques are discussed while in other cases, the topic resembles a tutorial.Each topic stands on its own so you can jump from subject to subject. Do not beconcerned about reading these topics in the order they are presented.

Chapter 10. Techniques 10-1

10.1 Criteria Language Examples Relating to Criteria Rules


Rule #1: ORs are changed to ANDs if they involve only CA-Scheduler-controlledjobs or schedules only for predecessor relationships, not for selection:

This: JOBA OR JOBA Changes to: JOBA AND JOBA

JOBA OR JOBS JOBA AND JOBS

JOBS OR JOBA JOBS AND JOBA

JOBS OR JOBS JOBS AND JOBS

Rule #2: ORs are respected if the conditions include any kind of keyword (likeMVS, PRED, or GDG):

This stays as is: MVS JOBA OR JOBB

Rule #3: CA-Scheduler-controlled jobs and schedules are always ignored (whentesting predecessors) if they are not eligible for today's workload:

(MVS JOB1 AND JOB1 MONSCHD) or

(MVS JOB1 and JOB1 TUESCHD)

On Monday, will be evaluated as:

(MVS JOB1 AND JOB1 MONSCHD) OR

(MVS JOB1)

On Tuesday:

(MVS JOB1) OR

(MVS JOB1 AND JOB1 TUESCHD)

Any other day:

(MVS JOB1) or (MVS JOB1)

10-2 Online Guide


Rule #4: Reason codes and calendar criteria have no effect on predecessorevaluation at all. If the following criteria is coded:

(WEEK-DAY AND JOB1 SCHD1)

OR (WEEK-END AND DSN DATASET.ONE)

The job will always be selected because it is always either WEEK-DAY orWEEK-END.

However, the predecessor evaluation might not meet expectations. It will be evaluatedas: JOB1 SCHD1 or DSN DATASET.ONE

As soon as one of these two OR's conditions is true, the job runs. Neither reason codenor the calendar criteria have anything to do with predecessor evaluation, they controlonly SELECTION.

Note: Under Rule #2, the following criteria:

(WEEK-DAY AND JOB1 SCHD1)

OR (WEEK-END AND DSN DATASET.ONE)

is evaluated for predecessors as: JOB1 SCHD1 OR DSN DATASET.ONE (theOR stays an OR).

So if JOB1 runs and ends or the DSN DATASET.ONE gets updated, thiscriteria is satisfied.

The recommended way to get the desired results (different predecessors ondifferent days) is to code two different job numbers with different criteria:

JOB1-�1: (WEEK-DAY AND JOB1 SCHD1)

JOB1-�2: (WEEK-END AND DSN DATASET.ONE)


10.2 More Examples of Criteria Language


10.2.1 Example 1

FRI or MON and HDAY-3 OR TUES AND HDAY-4 AND HDAY-1

Run job on FRI unless FRI is a holiday, then run job on MON unless MON is also aholiday, then run job on TUES.

10.2.2 Example 2

JOBX JNO=�1 JOBA

JOBX JNO=�2 JOBB

JOBX JNO=�3 JOBC

JOBX JNO=�4 JOBD

Run JOBX once for every time either JOBA, JOBB, JOBC, or JOBD is also selected.For example, if JOBA and JOBB are selected to run today, then JOBX will run twice,once being dependent on JOBA to complete, and once being dependent on JOBB tocomplete.

10.2.3 Example 3

JOBA REQUESTED

JOBB JOBA

JOBC JOBB

JOBD JOBC

Because JOBA is a requested job, it will be selected every day, but will not run unlessrequested. Because JOBA is always selected, any other jobs which are a successor toJOBA (in this case, JOBB, JOBC, and JOBD are all successors), then all of these jobswill also be selected and put in the inactive queue.

10.2.4 Example 4

(WEEK-DAY AND JOB1 AND JOB2) OR (WEEK-END AND JOB3)

This particular criteria is not logical if you consider how job selection/dependencyworks under CA-Scheduler. For example, suppose that on any given day, JOB1 andJOB2 and JOB3 are all selected to run. The job dependency would then become 'JOB1AND JOB2 AND JOB3' since all three jobs were selected. (The 'OR' conditionbecomes an 'AND' condition for job dependency.)

10-4 Online Guide


If you have a job (JOBA) that needs to run Monday through Friday if JOB1 and JOB2are selected, and runs on Saturday and Sunday when JOB3 is selected, then you coulduse the following criteria:

JOBA JNO=�1 WEEK-DAY AND JOB1 AND JOB2

JOBA JNO=�2 WEEK-END AND JOB3

10.2.5 Example 5


JOBA WDAY ( WORK DAY )

JOBB FRI ( FRIDAY )

JOBC JOBA OR JOBB

On WDAY, JOBA AND JOBC will run, with JOBA being a predecessor to JOBC.

On FRI, (if FRIDAY is not a WDAY), then JOBB and JOBC will run, with JOBBbeing a predecessor to JOBC.

However, if FRIDAY is a WORKDAY, then all three jobs will run with JOBC waitingfor both JOBA AND JOBB to finish before being released. In other words, becauseboth JOBA and JOBB were selected on FRIDAY, then JOBC criteria becomes 'JOBAAND JOBB' rather than 'JOBA OR JOBB'.

10.2.6 Example 6


JOBA DAILY ( DEFAULT )

JOBB MON ( MONDAY )

JOBC WED ( WEDNESDAY )

JOBD (JOBA AND JOBB) OR JOBC

On MON, JOBA AND JOBB AND JOBD will run, with JOBD waiting for bothJOBA AND JOBB to complete.

On WED, JOBA AND JOBC AND JOBD will run, with JOBD waiting for bothJOBA AND JOBC to complete.

Remember that the 'OR' condition becomes an 'AND' condition when dependency isdetermined, such that on WED, the criteria for JOBD will become 'JOBA AND JOBC'(JOBB is disregarded because it was not SELECTED to run on WED).



10.2.7 Example 7

SCHEDULE 'A' CONTAINS JOBA

SCHEDULE 'B' CONTAINS JOBB (WHICH IS TO RUN ONLY WHEN JOBA IS SELECTED)

THE CRITERIA FOR JOBB WOULD BE:

JOBA A (where A is the schedule name)

CA-Scheduler has two kinds of criteria:

SELECTION CRITERIAEvaluated only at autoscan time, these control whether a job is selected fortoday's workload. For example:

SUN

WEEK-DAY

WDAY

JAN

12TH

JOB1 SCHD1 �

PREDECESSOR CRITERIAEvaluated both at autoscan time and continuously during the dailyprocessing, these control when a job runs. For example:

GDG DATA.SET.ONE

PRED JOB2 SCHD1

GBLC�2=TPDWN

JOB1 SCHD1 �

DSN DATA.SET.ONE

MVS JOB1

NJE JOB1

* Some types of criteria, job names and schedule names, function both as selectionand predecessor criteria. If a job's criteria is 'JOBA SCHD1', it means that the jobwill only be selected when JOBA IN SCHD1 is selected, the job will not rununtil JOBA completes.

Selection Criteria are evaluated at autoscan time, since they play a part only indeciding if the job is selected today. When you specify the following criteria recordfor JOBA

(MON AND JOBB AND GBLC�2=TPDWN) OR (TUE AND JOBC)

At autoscan time, the Selection Criteria appears like the following to CA-Scheduler:

(MON AND JOBB) OR (TUE AND JOBC)

The job is selected because it is Monday and JOBB is selected today.

10-6 Online Guide


During predecessor evaluation, the selection-only criteria are ignored since they havealready been evaluated. Assume JOBC is also in Monday's workload. The criteriaappears like this to CA-Scheduler when it is evaluating predecessors:

(JOBB AND GBLC�2=TPDWN) OR JOBC

Since this criteria is continually evaluated, as each job runs it is removed from the'internal criteria' (CA-Scheduler list of what this job is waiting for).

After JOBB runs, the criteria is re-evaluated as:

GBLC�2=TPDWN OR JOBC

After JOBC runs, since the OR is preserved, the job will take off when the ORcondition is true.

The OR in the above criteria is respected because of GBLC02 specification. ORs arechanged to ANDs when their parenthesized criteria statements involve onlyCA-Scheduler controlled jobs or schedules. Any other criteria (like GBLC02 ORPRED OR GDG OR DSN) causes the OR to be preserved.

RESOLUTION:

Change to two different job numbers with two different criteria:

JOBA-�1 : MON AND JOBB AND GBLC�2=TPDWN

JOBA-�2 : TUE AND JOBC


10.3 On-Request Schedules and Jobs


10.3.1 Discussion

On-request schedules and jobs are ones that are selected every day, and placed in anINACTIVE queue, in case they are needed. They remain in an INACTIVE status untilthey are activated by a control command. This means that you cannot determine inadvance whether the schedule or job will be needed on any particular day.

You define an on-request schedule or job using REQUESTED, a Gregorian calendarreserved word, in its selection criteria.

When the autoscan process runs, all REQUESTED schedules and jobs are selectedalong with their successors and placed in the CA-Scheduler active workload in anINACTIVE queue. The only way they can be removed from the INACTIVE queue isusing the control command REQUEST or SREQ. When removed from the INACTIVEqueue, they are placed in the ACTIVE queue and will then be handled as normallyselected jobs.

An important difference between the REQUEST and SREQ commands is thatREQUEST also places the successor schedules and jobs in the ACTIVE queue. TheSREQ command handles successors differently: SREQ does not activate a successor ifit involves other REQUESTED jobs. A successor of an SREQed schedule or job is notto 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 theINACTIVE queue.

All schedules and jobs that have not been requested by the next autoscan are purgedfrom the CA-Scheduler active workload, regardless of what BACKLOG values theyhad defined.

A guideline you should follow when using the REQUESTED keyword is: To ensurethat simulation produces reason codes which match those produced by CA-Scheduler,specify REQUESTED after job and schedule names in selection criteria wheneverpossible.

This explains the basics about how REQUESTED schedules and jobs are handled.However, this topic sometimes causes confusion, so we will discuss it further.

10-8 Online Guide


10.3.2 Criteria Language Subtleties

The best way to explain these subtleties is with examples. Each example assumes thatthe jobs described are all contained in the same schedule. Although you should alwaysspecify schedule names with job names in criteria statements, they are omitted in theexamples below to keep things simple.

10.3.2.1 Example 1

In this example, all three jobs will be placed in the INACTIVE queue every day.

Job Criteria

JOBA REQUESTED

JOBB JOBA

JOBC JOBB

10.3.2.2 Example 2

JOBA will be placed in the INACTIVE queue every Monday.

Job Criteria

JOBA MON AND REQUESTED

10.3.2.3 Example 3

This example follows the same rules as MON when selected on Monday and treated asa normal job (meaning that on Mondays, it is placed in the ACTIVE queue and it doesnot have to be requested). Any other day, it will be treated as a requested job.

Job Criteria

JOBA MON OR REQUESTED

10.3.2.4 Example 4

Job Criteria

JOBA REQUESTED

JOBA1 None

JOBB JOBA OR JOBA1



In this example, all jobs will be selected. JOBA and JOBB will be placed in theINACTIVE queue. JOBB is placed there because JOBA is the first predecessorspecified and it is a REQUESTED job. The ordering of these predecessors is importantas you will see with the next example.

JOBA1 will be run whenever its conditions allow (if none exist, it starts immediately).

JOBB will always wait for JOBA1 (that is, you could request JOBB withoutrequesting JOBA). If JOBA is requested (with the REQUEST or SREQ command),JOBB will automatically be requested and will wait for both JOBA and JOBA1.

If no requests are made, JOBA and JOBB will be purged from the active workload atthe next autoscan.

10.3.2.5 Example 5

This example is the same as the one above except for the order of the predecessors onJOBB. All three jobs will be selected, but only JOBA is placed on the INACTIVEqueue. This is because JOBB got selected because of JOBA1 which is selectedwhenever the schedule is selected.

JOBB will always wait for JOBA1, but will only wait for JOBA if JOBA is requested(using the operator command REQUEST or SREQ) before JOBA1 completes.

If JOBA is not requested, it will be purged from the active workload at the nextautoscan.

Job Criteria

JOBA REQUESTED

JOBA1 None

JOBB JOBA1 OR JOBA

10.3.2.6 Example 6

Both JOBA and JOBB will be placed in the INACTIVE queue at autoscan time.

When the operator command REQ J N=JOBA is issued, both jobs (JOBA and JOBB) willbe moved to the ACTIVE queue.

Job Criteria

JOBA REQUESTED

JOBB JOBA AND REQUESTED

10-10 Online Guide


When the operator command SREQ J N=JOBA is issued, only job JOBA will be movedto the ACTIVE queue. JOBB will not be moved since it has the criteria ANDREQUESTED which must be satisfied. It is not satisfied using the SREQ operatorcommand with its predecessor JOBA. To move JOBB to the ACTIVE queue, in thiscase, use the REQUEST or SREQ command.

10.3.2.7 Example 7

On Mondays, JOBB will be added to the ACTIVE queue and will not wait for JOBAunless it is also in the ACTIVE queue. That is, JOBA will not be considered apredecessor of JOBB unless JOBA is requested with the REQUEST or SREQcommand before JOBB is submitted. Once JOBA and JOBB are both in the ACTIVEqueue, CA-Scheduler will not submit JOBB until JOBA has completed.

Job Criteria

JOBA REQUESTED

JOBB MON OR JOBA

10.3.2.8 Example 8

All four jobs will be placed in the INACTIVE queue at autoscan time.

When the operator command REQ J N=JOBA is issued, JOBA, JOBB and JOBC will bemoved to the ACTIVE queue. This occurs with JOBB and JOBC since neither of themare requested jobs, but rather each of them only require JOBA to be selected. IfJOBA1 were the requested job, then JOBA1 and JOBB would be the ones moved tothe ACTIVE queue.

When the operator command SREQ J N=JOBA is issued, JOBA, JOBB, and JOBC will bemoved to the ACTIVE queue having the same result, in this case, as issuing theREQUEST command. If the operator command SREQ J N=JOBA1 were issued, onlyJOBA1 would be moved to the active queue. This is because JOBB was selected todayfor reason code 01 (the successor to JOBA).

Job Criteria

JOBA REQUESTED

JOBA1 REQUESTED

JOBB JOBA OR JOBA1

JOBC JOBA



10.3.2.9 Example 9

All five jobs will be placed in the INACTIVE queue at autoscan time.

This example closely resembles example 8. We should focus on what happens whenthe SREQ command is used with JOBA. In this case, JOBB is still moved to theACTIVE queue, but JOBC and JOBD are not. That is because JOBC's criteria includesthe REQUESTED keyword, and JOBA1 (JOBD's predecessor) was REQUESTED.Issuing the command SREQ JOBC will move JOBC to the ACTIVE queue. To moveJOBD to the ACTIVE queue, just SREQ both JOBA and JOBA1.

Job Criteria

JOBA REQUESTED

JOBA1 REQUESTED

JOBB JOBA OR JOBA1

JOBC JOBA AND REQUESTED

JOBD JOBA AND JOBA1

10.3.2.10 Example 10

Both of the above jobs are in a schedule called SCHDA which has a criteria ofREQUESTED. At AUTOSCAN time, both JOBA and JOBB are placed in theINACTIVE queue.

When the control command REQ S N=SCHDA is issued, JOBA and JOBB aremoved to the ACTIVE queue. When the control command SREQ S N=SCHDA isissued, only JOBA is moved to the ACTIVE queue.

Job Criteria

JOBA None

JOBB REQUESTED

10-12 Online Guide

10.4 Backlogged Work


Sometimes, schedules, jobs, or both do not complete the day on which they wereselected. This means that they may be candidates for being backlogged. But first, wewill define what a day is.

In terms of your company, a day would be your normal daily business computer cycle.For example, production work starts at 16:00 and is to be completed by 08:00 the nextmorning. This is fairly typical. That means you run autoscan at, or shortly after, 08:00(to select schedules and jobs for the next 16:00 to 08:00 time period). Thus, in termsof CA-Scheduler, a day is the 24-hour period that starts with the time that you runautoscan. We will term this the production day or autoscan day.

Schedules and jobs that do not complete on the production day on which they wereselected can be carried over to the next production day. They are then calledbacklogged schedules or jobs. When you define a schedule or job to the database,specify whether that schedule or job is a candidate for backlog. Normally it is.

We can step through what happens if the work for a production day is not complete.

Job Backlog: The normal situation allows schedules to be backlogged. Whenautoscan is initiated and it is determined that a schedule is still active (it has notfinished running yet), the schedule will be backlogged. Any job in the schedule thathas completed, been canceled, or purged will retain its status. If a job has been definedwith BACKLOG=YES, it will be backlogged if it had not started. That is, it will beallowed to run. If a job in the backlogged schedule has been defined withBACKLOG=NO and still has a status of WAITING, it will be canceled with a statuscalled NO BACKLOG CNCL.

Once all jobs in the backlogged schedule have been completed or canceled, theschedule will be marked as complete. If the same schedule was also selected on thecurrent production day, then it and its associated jobs will be placed on theCA-Scheduler active workload and processed as if it had been selected normally.

If a daily schedule gets backlogged for greater than 24 hours (that is, it is backloggedby two autoscans), then when it completes, the schedule to execute on the completedday is loaded to the active workload. For example, if Monday's schedule getsbacklogged and completes on Wednesday, Tuesday's schedule will never be run.

Schedule Backlog: When BACKLOG=YES or NO is specified on a scheduledefinition, it acts only as a default for jobs in that schedule when BACKLOG is notspecified on a job. Then it is handled as described above.

Requested Jobs And Schedules: Jobs and schedules that are on-request and arestill in the INACTIVE queue at autoscan time will be purged, regardless of theirBACKLOG value.



In Summary: Since the term NO BACKLOG CNCL was used a few times above,we need to define it more clearly. This is a status condition that means the job wascanceled at the end 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 started andwill 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 show up onthe Pending Job Profile CA-EARL report for the current production day.

When a schedule is backlogged and it is also to be selected for the current productionday, the one being selected will not be placed onto the CA-Scheduler active workloaduntil the backlogged one completes. Only one copy of a schedule at a time will bekept on the active workload. Therefore, if for some reason a schedule occurs dailyand is backlogged twice, the schedule for the middle day would never be brought in.Another example is that if a schedule runs Monday and Tuesday only, and Monday'sschedule gets backlogged until Wednesday, Tuesday's schedule will never be run. Thisis because when Monday's schedule finishes and Tuesday's is brought in, it isevaluated for Wednesday. Since there is nothing in this schedule to run on Wednesday,it will never get started.

10-14 Online Guide

10.5 Restart/Recovery of Scheduled Jobs


This topic discusses methods of restarting and recovering scheduled jobs. These arejobs that are defined in the database and were selected as part of the day's productionduring the most recent autoscan process.

Recovery of jobs as they pertain to a multi-CPU environment is discussed in the"Multiple CPU Operations" chapter of the Systems Programmer Guide. That discussiondescribes how jobs can be moved as a group from one CPU to another when one CPUgoes down.

In this topic, we will discuss how you determine which jobs have abended, what typeof manual actions you can take, what type of automatic facilities are available withinthe database, and then discuss how you could use Driver to automate the recoveryprocess. Driver is a component of CA-Scheduler that provides a JCL handling facility.

10.5.1 Restart Through CA-11

Jobs may be restarted using the CA-Scheduler CA-11 interface if you have CA-11installed and active. When the RERUN or SUBMIT commands are used from thestatus display on a job that is known to CA-11, the RERUN or SUBMIT panel isdisplayed with current information from the CA-11 CMT.

The advantages of using CA-11 to restart jobs are:

■ If you originally specify INSERT RMS PROC = YES on the SBR or JBR, theCA-11 RMSPROC is automatically inserted by CA-Scheduler into the job stream(provided that none is already present) at submission time. This allows CA-11 totrack your jobs and maintain restart information in case a job abends. However,since the RMSPROC is inserted automatically by CA-Scheduler, no JCLmaintenance is required to prepare for using the CA-Scheduler CA-11 interface.

■ Jobs that contain the RMSPROC are tracked by CA-11 in its CMT (CatalogManagement Table). The CMT contains information which allows CA-11 torestart jobs from the correct point if they abend. CA-11 also cleans up data setsthat were created or affected by the jobs before they abended. Also, it keeps trackof GDG bias so that restarts of the jobs are performed at the correct version. Allof this tracking permits job restart with no JCL editing.

■ If a job that specifies INSERT RMS PROC = YES abends, it can be restartedthrough CA-11 using one of two CA-Scheduler commands: SUBMIT or RERUN.Alternatively, the job can be completed or canceled. Although CA-Schedulercommands are used to handle the job, the CA-11 CMT is updated accordingly forsubsequent runs of the job. Also, CA-11 restart parameters can be passed throughthe CA-Scheduler commands. This allows you to override CA-11 parameterswhenever necessary.

For details on how to restart a job through the CA-Scheduler CA-11 interface, see4.3.16, “Rerun Job Command” on page 4-142 or 4.3.21, “Submit Job Command” onpage 4-160.



10.5.2 Inquiring About Jobs to be Recovered

From the status panels, you have a set of status queues from which you can displayautomatically. The status conditions that would indicate recovery may be necessaryinclude: jobs that might need recovery if they are not set up to recover automatically.The status conditions that would indicate recovery may be necessary include:

To recover any job, its JCL is either in the active workload or can be placed there bythe RESTAGE command. Once it is in the active workload, you can modify it andresubmit the job.

Status Code Description

ABENDED The job has abended with an abend code such as S0C1. Itcan be rerun by using the RERUN or SUBMIT controlcommand.

OPERATORCANCLD

The job has been canceled by an operator using theCANCEL or CP control command. This job can be runagain by using the RUN, RERUN, or SUBMIT command.

FAILED The job has failed with a condition code that exceeds thevalue specified in the FAIL CODE field when defining thejob or has failed on a JCL error. It can be rerun by using theRERUN or SUBMIT control command.

10.5.3 Automatic Recovery Options

When defining a job to the database, a field called ABEND can be used to aid inautomatic recovery of a job. You can specify four options in this field. They include:

Option Description

ABORT Indicates that successors to this job do not have thispredecessor satisfied. This is the default value.

CONT Indicates that successors to this job are to be handled as ifthe job terminated normally because this predecessor hasbeen satisfied.

BACKOUT Indicates that successors to this job will not be posted assatisfied if this job abends. A backout job will be submittedautomatically if you specified a value for the BACKOUTinstallation option. CA-Scheduler adds a new job trackingrecord for the backout job.

schedule name Indicates that the schedule name provided is to be processed.This is a predefined recovery schedule that will beautomatically processed should the job abend and theabended job will follow the same process as ABORT.

10-16 Online Guide


If a recovery schedule is defined, it could contain a job that executes the CAJUCMD0program that allows you to interrogate various jobs' status through batch commands.Based on the job status, other jobs could be brought in with the RUN, REQUEST, orADD control commands for recovering the abended job. This technique is described inthe preceding topic of this chapter. When you define a recovery schedule, you shouldattempt to use some sort of naming convention so that any recovery schedule can berecognized 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 to use themessage facility. That is, you can specify up to four users to send messages to if thejob abends or fails. These users are defined on the schedule and job message records.The users can be operator consoles or the CA-Scheduler mailbox. (See ScheduleMessages panel on page 5-15 and Job Messages panel on page 5-46.) Keep in mindthat JCL errors for a job are treated as if the job failed.

10.5.4 Driver Considerations

Implementing a job step restart process is inherently complex due to all of thevariations of abend conditions. As with the implementation of any automated system,the 'cure' should not cause more disruption than the problem.

For example, in a multi-step job, Step 5 abends. The determination is made throughthe automated process that exists today, that Step 5 relies on the temporary data setthat was created in Step 2. Therefore, the data sets that were created in Steps 2, 3, and4 must be removed from the OS/390 catalog. What cannot be determined through anyautomated process is that the data set created by Step 1 and used for input by Step 2was created using incorrect input. Herein lies the problem of automating therestart/recovery process.

Many options are available to a data center to effect proper restart/recovery eitherusing native OS/390 JCL, or a more automated method using Driver. Driver is the JCLmanagement facility included in CA-Scheduler.



10.5.4.1 Step-Level Restart

Most actions to restart a program after an abend fall into three categories:

■ Adjustment of generation bias numbers

■ Scratching of a data set from the catalog

■ Executing some type of recovery program

As with other areas in the data center, attempts should be made to keep manualintervention to a minimum. Abend recovery cannot be totally automated, however,because it is impossible to plan for every situation. Realistically, some manualintervention is involved in a program restart. Consideration should be given to keepingthe intervention to a minimum and to making the intervention as error-free as possible.

Of course, facilities exist in OS/390 JCL that ease restart complexities. However,standard JCL does not take care of resetting GDG bias numbers. To reference ageneration data set that was created in a prior step, you must suffix the data set namewith the string (+1). The generation data group's index is updated at job-end and notstep-end. In a restart situation where the restart takes place after the data set has beencreated, all of the (+1) generation pointers must be changed to (0); all the (0) must bechanged to (-1).

Three ways exist to reset relative generation pointers.

First, the values could be explicitly coded in the JCL. This is the most straightforwardmethod and the most error-prone because changes must be made to the execution JCL.

Second, the body of the job could be made into a cataloged procedure with thegeneration members being symbolic values. The symbolics could then be overridden atexecution with values supplied by the starter JCL. The drawback to this approach isthat in a large program, quite a number of overrides could be required to restart theprogram correctly.

The third, and last, method uses the Driver component of CA-Scheduler. The OS/390symbols are made into Driver variables. Driver statements would be used to determinewhether it was production or rerun, and where the restart should begin. This is theleast error-prone because the JCL is automatically changed by Driver.

The first two examples below use standard JCL facilities.

10-18 Online Guide


10.5.4.2 Example 1

In this example, generation members are explicitly coded.

//BACKUP JOB (acctg),'DASD BACKUP',CLASS=A

//STEP1 EXEC PGM=DASDBKUP

//SYSPRINT DD DSN=DASD.BACKUP(+1),// DISP=(NEW,CATLG,DELETE)

//STEP2 EXEC PGM=LISTDASD

//TAPEIN DD DSN=DASD.BACKUP(+1),// DISP=OLD

//SYSPRINT DD SYSOUT=A

This is a two-step job where the first step creates a backup tape of data stored on diskand the second step prints a report using the backup tape as input. The backup data setis a generation data set (DASD.BACKUP) since it is suffixed with (+1), the biaspointer. Thus, when the step ends normally, the data set will be cataloged asDASD.BACKUP.GnnnnV00, where nnnn is the generation number. In the second step,we indicate to use the generation number created in the first step, (+1).

Now, if we want to restart in the second step, we must insert a RESTART parameterand change the GDG bias.

//BACKUP JOB (acctg),'DASD BACKUP',CLASS=A,

// RESTART=STEP2//STEP1 EXEC PGM=DASDBKUP

//SYSPRINT DD DSN=DASD.BACKUP(+1),

// DISP=(NEW,CATLC,DELETE)


//TAPEIN DD DSN=DASD.BACKUP(�),// DISP=OLD


The above would have been the case if the program abended in the second step andwhere the tape was created in the first step properly. A restart must be submitted toprint the report.



10.5.4.3 Example 2

In this example, the body of the JCL is a JCL procedure and uses symbolics instead ofhard-coding the generation bias numbers.

//DASDBKUP PROC GENP1='+1',GENP2='+1'//STEP1 EXEC PGM=DASDBKUP

//SYSPRINT DD DSN=DASD.BACKUP(&GENP1),// DISP=(NEW,CATLC,DELETE)


//TAPEIN DD DSN=DASD.BACKUP(&GENP2),// DISP=OLD


This is a standard OS/390 cataloged procedure. Except for the symbolics, the JCL isthe same as Example 1.

The starter JCL for the normal execution would be:

//BACKUP JOB (acctg),'DASD BACKUP',CLASS=A

//BKUP EXEC PROC=DASDBKUP,GENP1='+1',GENP2='+1'

This would submit the same JCL seen in Example 1 with the symbolics properlyresolved.

Now, if we want to restart in the second step, you would submit the following:

//BACKUP JOB (acctg),'DASD BACKUP',CLASS=A,

// RESTART=(BKUP.STEP2)//BKUP EXEC PROC=DASDBKUP,GENP1='+1',GENP2='�'

This would submit the same JCL as in Example 1 (restart) with the symbolics properlyresolved.

10-20 Online Guide

Chapter 11. Remote Scheduling

Jobs with a node ID of *REMOTE represent work on a remote non-OS/390 platformrunning Unicenter TNG or CA-Scheduler Agent. The work is scheduled byCA-Scheduler, then initiated and tracked by Unicenter TNG or CA-Scheduler Agenton the remote platform. When Unicenter TNG or CA-Scheduler Agent reports that taskcomplete, CA-Scheduler marks the job as ended or failed, based on the return code.

CA-Scheduler needs at least two pieces of information to schedule work on remotesystems: the node name and the command to be executed. You may also specify auser ID, password, and a domain.

CA-Scheduler passes the information to Unicenter TNG or CA-Scheduler Agent usingCAICCI, one of the Unicenter TNG Framework for OS/390 Common Services. Allsystems on which CA-Scheduler is to schedule work must be defined (connected) toCAICCI and must be running either Unicenter TNG or CA-Scheduler Agent.

Work on remote systems is initiated by a command. The command can execute ascript on the remote system, a program, or anything else that can be started with acommand. Parameters can be passed on the command. Uppercase and lowercasecharacters are supported, as well as any special characters needed.

When CA-Scheduler determines that it is time for a remote task to be started, it readsthe CAICCI node name and the command from the data set where the JCL is normallystored. For example, if the job is defined as libtype PDS, the information is read fromJCLMASTR.

Chapter 11. Remote Scheduling 11-1

11.1 Statements

11.1 Statements

The following statement types are supported:

■ Comments

■ Node

■ Command

■ Domain

■ User

■ Password

Statements may be specified in any order.

11.1.1 Comments

Enter comments by typing an asterisk (*) in column 1. CA-Scheduler does not takeany action on these lines.

11.1.2 Node

Specify the CAICCI node name on the node statement:

Node='nodename'

The node statement must begin with the characters "NODE=" in column 1. Useuppercase or lowercase.

The first character after the equal sign is used as a delimiter. In the example above, thedelimiter is a single quote. CA-Scheduler ignores anything after the closing delimiter.The following would all be treated identically:

node=/nodename/

NODE=?NODENAME?

Node="NodeName" comments

CAICCI node names are one to eight characters long and can be entered in uppercaseor lowercase.

Only one node statement is allowed per member.

11-2 Online Guide

11.1 Statements

11.1.3 Command

The command to be executed is specified on one or more command statements:

Command='command'

Command statements must begin with the characters "COMMAND=" in column 1.Use uppercase or lowercase.

The first character after the equal sign is used as a delimiter. In the example above, thedelimiter is a single quote. CA-Scheduler ignores anything after the closing delimiter.The following would all be treated identically:

command=/commandstring/

COMMAND=?commandstring?

Command='commandstring' comments

The case of the command string is preserved. For example, the following are NOTidentical:

command='commandstring'

command='COMMANDSTRING'

Command strings can be up to 255 bytes in length. Use multiple command statementsto build long command strings. The strings are concatenated together without anyintervening spaces or other characters added. For example:

command='command'

command='string'

would produce the command string of "commandstring". If a blank was wantedbetween the two parts, include it in the command statement:

command='command '

command='string'

would produce the command string of "command string".

The command string is split into a command and parameters. Blanks are used todelimit between the command and any parameters. The following command statementwould send two parameters:

command='command parm1 parm2'

If a parameter needs to include a space, use quotes around that parameter. Thefollowing example sends only one parameter:

command=/command "part1 part2"/

If a parameter needs to include a quote, it must be doubled and enclosed in quotes:

command=/command "quote in parentheses ("")"/


11.1 Statements

The previous example will send a single quote between the parentheses, and the entirestring "quote in parentheses (")" will be sent as one parameter.

Note: The interpretation of parameters is platform and command specific. Someplatforms may treat a single parameter as multiple parameters if the parameterincludes blanks.

11.1.4 Domain

On some platforms, such as Microsoft Windows NT, users may be defined withindomains. See the documentation supplied with the target operating system and withUnicenter TNG for that platform to determine if a domain is required and what action,if any, Unicenter TNG takes if a domain is not specified.

Domain='domainname'

The domain statement must begin with the characters "DOMAIN=' in column 1. Useuppercase or lowercase.

The first character after the equal sign is used as a delimiter. In the example above, thedelimiter is a single quote. CA-Scheduler ignores anything after the closing delimiter.

Domain names may be up to 15 characters long. Note, however, that the requirementsof the target system may restrict the length.

The domain name is passed to Unicenter TNG exactly as entered. If the target systemis case-sensitive, enter the domain name in the expected case.

11.1.5 User

Specify a user ID on the user statement. Unicenter TNG executes the command underthis user ID.

If no user ID is specified and the CAIJ$SEC option RMTUSER is set to Y,CA-Scheduler uses the same rules applied to OS/390 jobs to determine a user ID (thatis, CAIJGEN SUBUID order, CAIJ$SEC options).

User='userid'

The user statement must begin with the characters "USER=" in column 1. Useuppercase or lowercase.

The first character after the equal sign is used as a delimiter. In the example above,the delimiter is a single quote. CA-Scheduler ignores anything after the closingdelimiter.

User IDs may be up to 32 characters long. Note, however, that the requirements of thetarget system may restrict the length.

11-4 Online Guide

11.1 Statements

If the user ID specified is ROOT, the CA-Scheduler option CAIJ$SEC SUBROOT ischecked. If SUBROOT is set to YES, the submission is allowed. Otherwise, thesubmission is failed. (ROOT is a powerful user ID on some systems, such as UNIX.)

The user ID is passed to Unicenter TNG exactly as entered. If the target system iscase-sensitive, enter the user ID in the expected case.

Unicenter TNG may need to be configured to support submission of work in otherthan the default user ID. See the Unicenter TNG documentation for the target platformfor more information.

User IDs on the target platform may need special authorization to be used byUnicenter TNG. See the Unicenter TNG documentation for the target platform formore information.

11.1.6 Password

Specify the password to be used to log on the user ID on the target platform.

Password='password'

The password statement must begin with the characters "PASSWORD=" in column 1.Use uppercase or lowercase.

The first character after the equal sign is used as a delimiter. In the example above,the delimiter is a single quote. CA-Scheduler ignores anything after the closingdelimiter.

Passwords may be up to 14 characters long. Note, however, that the requirements ofthe target system may restrict the length.

The password is passed to Unicenter TNG exactly as entered. If the target system iscase-sensitive, enter the password in the expected case.

Unicenter TNG may be configurable to require or not require passwords. See theUnicenter TNG documentation for the target system for more information.


11.2 Examples

11.2 Examples

11.2.1 Example 1

node='uscoiu87'

command='/usr/bin/sleep 1�'

This example runs a program called sleep in the /usr/bin directory of an RS6000machine called USCOIU87. A parm of 10 is passed to the program.

11.2.2 Example 2

command="/usr/bin/sleep"

node=/uscoiu87/

command=' 1�'

This example works identically with the previous example. The statements can be inany order, and different delimiters can be used on each statement.

11.2.3 Example 3

node='win_nt'

command='c:\tngem\bin\cau9test t=15'

user='Administrator'

This example executes a program on a Microsoft Windows NT machine named"win_nt" under the authority granted to the user "Administrator".

11.2.4 Example 4

node='node1'

command='cau9test t=15'

user='user1'

domain='DALLAS'

password='abcd'

This example causes the Microsoft Windows NT user "DALLAS\user1" to be loggedon with a password of "abcd".

11-6 Online Guide

Glossary

This glossary defines terms used in all volumes of theCA-Scheduler documentation. But sometimes one newterm leads to another. To help you grasp these new ideasquickly, we have used italics to highlight related termsworth cross-referencing.

Aabend. Abnormal ending. An early termination of aprogram due to an error.

accounting day. A day designated on a date table aspart of a cyclic production, sales, or accounting period.

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, starttime, or defined resources

■ waiting at a non-CPU station to be started manually■ submitted, held, or started■ completed, interrupted, abended, or failed

The opposite of inactive.

active workload. The CA-Scheduler file that containsthe copy of current production. The default name of thefile is CAIJTRK.

array. A variable parameter with multiple values.

authority level. One of three different types of accessassigned to users using the TYPE field on a user record.Each authority level places different restrictions on whatthose CA-Scheduler users can do. See General,Supervisor, and Manager authority levels.

authorized users. Users with General authority levelwho are allowed to maintain and control a schedule and

its jobs because they are listed in the USERS field on thatschedule's base record. (Users with Supervisor orManager authority level do not require specificauthorization to maintain or control schedules.)

autoscan. The automatic selection of a day's workload.CA-Scheduler scans the database at a set time every dayto determine the workload for the next 24 hours.

autoscan day. The 24-hour period starting withautoscan. Also called the production day.

AUTOTIME. The time when CA-Schedulerautomatically scans its database for workload selection.This defaults to midnight, but may be modified with theAUTOTIM installation option. Also called autoscantime.

available. Ready for processing by CA-Scheduler. Aschedule is available (ready to start) when its early starttime has been reached and all of its predecessors havebeen satisfied. A job is available (ready to be submitted)when its schedule has started, the job's early start timehas been reached, all the job's predecessors have beensatisfied, and the resources defined for that job areavailable (not in use).

Bbacklog. Work that was not completed one day and wascarried over to the next. References to a backloggedschedule or job pertain to a previous day's schedule orjob which is included in today's workload.

backout job. A replacement job that is automaticallysubmitted by CA-Scheduler when a job abends providedthat ABEND=BACKOUT on the abended job's baserecord.

base record. The record which is required to define aschedule 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 CA-Scheduler program through standardOS/390 JCL.

CCA-11. Computer Associates rerun/restart product.

CA-Earl. Computer Associates Easy Access ReportLanguage. A subset of this product that allows you tocustomize reports is provided with CA-Scheduler.

CA-JCLCheck. Computer Associates JCL validationproduct.

CAIRIM. Computer Associates Resource InitializationManager. This component is included with CA-Schedulerand oversees the installation and maintenance ofComputer Associates OS/390 products.

CAISERV. A Computer Associates diagnostic facilitythat allows you to determine the current values ofinstallation options and to produce reports for use introubleshooting problems.

calendar. An alternative method for identifying when aschedule or job should be selected as part of the day'sworkload. With this method, you define severalcalendars, each designating different days when schedulesor jobs should be selected (Mondays, month-ends, paydays, etc.) The database shows which calendar to consultwhen selecting a schedule or job.

calendar mechanism. One of three date referencesCA-Scheduler consults when selecting the day's workload.

■ The Gregorian calendar tells CA-Scheduler what dayof the week it is so, for example, jobs can beselected on Mondays.

■ Calendars explicitly define which days to selectschedules and jobs so you can run jobs on randomdates.

■ Date Tables define workdays, holidays, accountingdays and accounting periods so, for instance,CA-Scheduler can select jobs on the last workday ofthe month.

calling statement. The EXEC statement which retrievesa procedure from the Driver procedure library andsubmits it to JES.

character string. One or more alphabetic, numeric, orspecial characters, usually enclosed in delimiters.

code. A number that explains why a schedule or job wasselected. Numbers from 01 to 79 correspond to theposition of a reason in the criteria statement. Numbersfrom 80 to 99 are special reason codes which indicatethat selection was based on default daily processing,calendars, or manual additions.

code record. The record that assigns time specificationswhich vary according to the reason a schedule or job isselected for processing. There is a schedule reason coderecord (SRC) and job reason code record (JRC).

conditional expansion. Driver retrieves and expandsjust some of the steps in a procedure depending onconditions at the time of expansion.

control command. A command used to monitor orcontrol the workload. Also known as operator command.

criteria record. The record that determines when aschedule or job is to be selected for processing and liststhe predecessors for the schedule or job. There is aschedule criteria record (SCR) and a job criteria record(JCR).

criteria statement. A statement defining:

■ the days schedules or jobs should be selected and

■ what predecessor conditions must be satisfied beforeselected schedules can start or selected jobs can besubmitted

See selection criteria, predecessor criteria, and selection.

criteria vocabulary. Reserved words used inCA-Scheduler's criteria statements.

cross-node dependency. Predecessor events that occurat other nodes in a CA-Scheduler NJE environment.These events can be the close of an output data set orgeneration data group, the start or end of a job underCA-Scheduler's control, or the normal completion of a jobnot under CA-Scheduler's control.

cyclic scheduling. Scheduling a schedule or job atregular intervals regardless of which day or month it is(for example, every six weeks).

X-2 Online Guide

Ddatabase. The CA-Scheduler database that storesrecords containing definitions of user IDs, stations,schedules, jobs, and resources. The default name of thedatabase is CAIJMST.

date table. Identifies workdays, holidays, accountingdays, and accounting periods so you can use workday,holiday, and accounting keywords in criteria statements.

date table prefix. A one letter prefix (excluding E, H,N, P and W) that allows you to define multiple versionsof a date table by applying different prefixes.

Date Translation Table. A report that shows whenworkday, accounting, and Gregorian conditions are true.

deadlock. The stalemate that occurs when jobs arepredecessors to each other. Deadlocked jobs never runbecause their predecessor conditions are never satisfied.Also called a predecessor loop.

default. A value or action that CA-Scheduler suppliesautomatically unless you specify some other alternative.

delimiter. A special character that precedes and followsa character string. In 'this example', the delimiter is asingle quote (') identifying a character string consisting oftwo words: this example.

documentation. Entries in the CA-Scheduler workoaddocumentation (CAIJDCM) that provide information tousers.

documentation batch command. A command issuedthrough batch using the CARUTIL0 program that is usedto maintain members in the workload documentation.

Driver. Computer Associates JCL manipulationcomponent of CA-Scheduler.

Eevents. Occurrences that CA-Scheduler monitors so itknows when predecessor conditions have been satisfied.Some of the events that CA-Scheduler monitors areschedules and jobs starting and ending, the close ofoutput data sets and generation data groups, and whattime it is.

expansion. Driver replaces an EXEC statement with thecontents of a cataloged Driver procedure.

explicit predecessor. A predecessor that is specificallydefined in the criteria statement of a schedule or job.Explicit predecessors can be either of two types:

■ Selection-defined explicit predecessors arepredecessors that also define selection criteria. Theycan be schedule or job names used with or withoutthe keywords SCD and START.

■ Keyword-defined explicit predecessors are ignored inthe selection process and always include one of thefollowing keywords:

DSN GDG GBLxnn MVS NJE PRED

When START or SCD are used with PRED or NJE orMVS, the result is a keyword-defined predecessor that isignored during the selection process.

Fforecasting. Producing reports that show whichschedules and jobs will be selected for processing on anygiven day(s).

GGeneral authority level. The default authority levelassumed for all users unless Supervisor or Manager isspecified. Allow users to:

■ define and maintain certain schedule and job records■ control and display the status of certain schedules

and jobs■ potentially display and alter JCL for certain staged

jobs

Two fields determine the scope of a General user'sauthority:

■ The CONNECT field on each user record defineswhich stations that General user is authorized toaccess.

■ The USERS field on a schedule's base record defineswhich General users can access that schedule and itsjobs.

General users are prohibited from doing anythinginvolving stations or schedules for which they are notauthorized. See authorized users as well as Supervisorand Manager authority levels.

generic list. A group of schedules or jobs whose namesbegin with the same characters. To display, list, oranalyze a generic list, specify the common charactersfollowed by an mask character (*).

Glossary X-3

global parameter. A user-controlled variable thatdefines a predecessor condition in criteria statements andcan assume arithmetic, binary, or character values. Seekeyword-defined explicit predecessors.

Gregorian calendar. The standard 12-month calendarwhich CA-Scheduler references to interpret certainselection keywords (like WEEK-DAY) in criteriastatements. You can use Gregorian calendar keywordswithout defining a date table or calendars.

Gregorian date. A date shown as mm/dd/yy (Americanformat) or dd/mm/yy (European format).

Hhistory file. The CA-Scheduler file that contains historyrecords for schedules and jobs.

history record. The record that contains statistics ofpast runs of schedules and jobs.

Iimplicit predecessor. Predecessors that are not definedon a job's criteria statement. Because CA-Schedulerenforces workstation sequences, pre-CPU jobs (such asdata entry and JCL staging) are implicit predecessors forCPU jobs. Likewise, CPU jobs are implicit predecessorsfor post-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 and jobs

Schedules and jobs in the INACTIVE queue at autoscantime are purged regardless of what values have beendefined for BACKLOG. The opposite of active.

information record. The record that providesdescriptive information of schedules and jobs. There is aschedule information record (SIR) and job informationrecord (JIR).

installation option. A value specified on the CAIJGENinstallation macro when CA-Scheduler is installed. Thisvalue controls scheduling operations throughout the datacenter unless it is overridden by values in theCA-Scheduler database.

JJBR. Job base record. This record is required to define ajob.

JCR. Job criteria record. This record determines whena job is to be selected for processing and lists thepredecessors for the job.

JIR. Job information record. This record providesdescriptive information for a job.

JMR. Job message record. This record determines whoreceives messages when a job begins, ends, starts late,abends, is purged, or is interrupted.

JNR. Job node record. This record is used to specifyother nodes to be notified when a job starts or ends.

job. Usually refers to work submitted to the CPU forprocessing. However, CA-Scheduler expands the scope ofthat definition to encompass all data processing tasksunder CA-Scheduler's control. This can include pre-CPUtasks such as data entry, jobs that run on the CPU, andpost-CPU tasks such as report distribution.

job number. One of four fields used to uniquelyidentify each job definition. When a job needs to runmore than once during a production day, create a jobdefinition for each iteration by giving them different jobnumbers.

job path. All the stations where a job is processed as itmoves through the data center.

JRC. Job reason code record. This record is used toassign time specifications which vary according to thereason a job is selected for processing.

JRR. Job resource record. This record allows you todefine the resources necessary to run a job.

JSR. Job step record. This optional record allows you todefine job step information used to determine a job'sfailed status.

Julian date. A seven-digit number of the form yyyyddd,where yyyy is the year and ddd is the relative day of theyear (from 001 to 366). For example, 2003305 isNovember 1, 2003.

X-4 Online Guide

Kkeyword-defined explicit predecessors. Predecessorsthat are ignored in the selection process and alwaysinclude at least one of the following keywords:

DSN GDG GBLxnn MVS NJE PRED

The keywords START or SCD can also be used withMVS, NJE or PRED.

Llevels of predecessors. In terms of a family tree, thenumber of preceding "generations" (schedules or jobs)with defined predecessors. The number ending each jobname below identifies each job's level of predecessors.

JOBA� JOBB�

│ │

JOBA1 │

│ │

JOBA2 ───┐ │

│ │

JOBA3

│

JOBB4

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 four differentpredecessors, but only three levels of predecessors. Levelsof predecessors is one factor CA-Scheduler uses whenordering the workload. Schedules and jobs with fewerlevels of predecessors are evaluated ahead of those withmore.

Mmailbox. The common area for sending CA-Schedulermessages so that they can be viewed by many userswithout being deleted.

Manager authority level. The highest authority levelwhich allows these users to access all stations, control all

schedules and jobs, define and maintain any databaserecords, and issue all commands. See General andSupervisor authority levels.

mask character. An asterisk (*) or question mark (?)included anywhere in a search string. Used when youwant to display all records with names that share commoncharacters.

? indicates that any character can be substituted at thispoint in the search string, but just one character can besubstituted for each question mark. That makes ? apositional mask character.

* indicates that CA-Scheduler will accept anythingoccurring at this point in the search: an * can signifyany number of characters.

For example:

P? displays all record names of just two charactersstarting with P

P* displays all records that start with the letter P

?ACC?displays record names of just five letters withACC in the middle

*ACC*displays just those records with ACC anywherein their name

See generic list.

message record. The record that determines whoreceives messages when a schedule or job begins, ends,or starts late or when a job abends, is purged, or isinterrupted. There is a schedule message record (SMR)and job message record (JMR).

Nnesting. One procedure calls (retrieves) anotherprocedure which can, in turn, call other procedures.

network. Two or more interconnected systems (nodes)participating in a VTAM network or communicatingusing BSC lines (binary synchronous communication).

node. Each location in a network having one CPU ormultiple CPUs with multi-access spooling facility.

node record. The record that specifies other nodes to benotified when a job starts or ends.

nonscheduled job. An OS/390 job that is neithercontrolled nor submitted by CA-Scheduler.

Glossary X-5

null value. A defined value of nothing which has beenadded to the database using the keyword NULL.

Oon-request. Schedules or jobs having the keywordREQUESTED in their criteria statement. These schedulesand jobs are selected every day in case they are needed,but they remain inactive until activated by the REQUESTor SREQ command.

operator command. A command used to monitor orcontrol the workload. Also known as control command.

Ppath. All the stations where a job is processed as itmoves through the data center.

periods. A year can be divided into accounting periods,production periods, sales cycles, or any other unit of time.The end of each period is identified by a P on the datetable.

post-CPU job. Work scheduled after CPU processing towrap up a job. Examples include output decollation,shipment of backup tapes off-site, and report distribution.See station.

pre-CPU job. Work scheduled to prepare a job for CPUprocessing. Examples include daily shipment of inputforms, data entry, and JCL setup. See station.

predecessor. An event that must happen before the nextjob can begin. CA-Scheduler's criteria statements allowyou to define predecessors for schedules and jobs. Thatmeans schedules and jobs in today's workload do not rununtil their predecessors are satisfied. If JOBA is apredecessor of JOBB, JOBB does not run until JOBAruns to completion.

Predecessors fall into several different categories that aredefined in this glossary:

■ explicit predecessors ■ implicit predecessors■ keyword-defined explicit predecessors■ selection-defined explicit predecessors

predecessor criteria. All of the predecessors defined fora schedule or job in its criteria statement. Thesepredecessor conditions must be satisfied before a schedulecan start or a job can be submitted.

predecessor loop. The stalemate that occurs when jobsare predecessors to each other. These deadlocked jobsnever run because their predecessor conditions are neversatisfied. Also called deadlock.

procedure. One or more statements cataloged under aprocedure name as a member of the CA-Driver procedurelibrary.

procedure library. The library that stores Driverprocedures.

production day. The 24-hour period starting withautoscan. Also called the autoscan day.

prompt. A word on a screen that reminds you to supplya value.

prototype calendar. A master calendar that defines allof the year's holidays and tells when to reschedule jobsthat would normally be selected on holidays. Theseholidays and rescheduling instructions are automaticallyapplied to all calendars 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 are assignedvalues from the prototype definition.

public schedule. A schedule that can be maintained byall users because no value is specified in the USERS fieldof the schedule base record.

Qqueue. One of the various job categories that depend onthe status of the jobs.

Rreason. Why a schedule or job is selected for the day'sworkload. A reason can be:

■ one or more words from the criteria vocabulary or■ the name(s) of jobs or schedules also selected that

day or■ a combination of the two

See selection.

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.

X-6 Online Guide

reserved-name variable parameter. One of a set ofDriver variable parameters which are predefined byComputer 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 data processingtasks.

run book. A report that contains detailed information onthe current day's workload.

SSBR. Schedule base record. This record is required todefine 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 jobs are

organized that way

The payroll department's month-end jobs could make up aschedule. The schedules and jobs selected each daycomprise the workload.

SCR. Schedule criteria record. This record determineswhen a schedule is to be selected for processing and liststhe predecessors for the schedule.

selection. How CA-Scheduler determines the day'sworkload at autoscan time. CA-Scheduler reviews thecriteria statements of every schedule to see which onesqualify for inclusion in the day's workload. Every timeCA-Scheduler selects a schedule that qualifies, it scansthe criteria statements of every job in that schedule. Jobsare selected if:

■ they specify a calendar which defines that day as aworkday or

■ a reason in the criteria statement is true that day or■ no criteria record exists for that job or■ one reason in the criteria statement is the keyword

REQUESTED

Jobs can only be selected when the schedules they belongto are selected. All the important terms used in thisdefinition are also defined in this glossary.

selection criteria. There are two distinct meanings:

■ 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,CA-Scheduler bases selection on the calendar andignores the selection criteria. See selection.

■ The keywords that are used in the maintenancepanels to limit the directory to be displayed.

selection-defined explicit predecessor. A predecessorthat also defines selection criteria. They are schedule orjob names used with or without the keywords SCD andSTART. When START or SCD is used with PRED orNJE or MVS, the result is a keyword-defined explicitpredecessor that is ignored during the selection process.

sequence enforcement. Making sure schedules and jobsare processed in the right order. See implicit predecessor.

shared DASD. A hardware configuration that allowstwo or more operating systems to use the same disk files.This situation allows several operating systems to use thesame set of CA-Scheduler files at the same time.However, when operating systems share CA-Schedulerfiles, it does not imply that they also share spool files.

simulation. Answers the question "what if." It showshow processing is affected by changes in workload orhardware failure. Simulation also totals how long eachjob usually takes to project when the workload is likely tofinish.

SIR. Schedule information record. This record providesdescriptive information for a schedule.

SMF ID. Four characters that identify the SystemManagement Facility running on OS/390. This valueusually corresponds to the JES SID.

SMR. Schedule message record. This record determineswho receives messages when a schedule begins, ends, orstarts late.

spin locks. The method CA-Scheduler uses to protectthe integrity of its files when two or more operatingsystems share them. See shared DASD.

SRC. Schedule reason code record. This record is usedto assign time specifications which vary according to thereason a schedule is selected for processing.

staging. CA-Scheduler's three-step process for tailoringproduction JCL:

Glossary X-7

■ First, CA-Scheduler automatically copies theproduction JCL for jobs that require staging into itsstaging library.

■ Then users modify that copy of the JCL as needed(the original production JCL is not changed).

■ When the JCL has been modified and that pre-CPUjob has been posted as ENDED, CA-Schedulerautomatically submits the modified JCL to theoperating system when that job becomes available forprocessing.

Also called JCL setup.

staging file. The CA-Scheduler file that contains stagedJCL members. The default name of the file is CAIJSTG.

station. Any area where a job is processed as it makesits way through the data center. Examples includeproduction control, data entry, JCL setup, CPUprocessing, and report distribution. Also called aworkstation.

substring. Part of the value given to a variableparameter.

status conditions. The various words (ABENDED,ENDED, FAILED, etc.) that CA-Scheduler applies tojobs to indicate their current state within production.

successor. Any job that cannot start until some eventtriggers it. CA-Scheduler's criteria statements allow youto define conditions that must be met before a job canstart. If JOBA must finish before JOBB can start, JOBBis a successor to JOBA. Conversely, JOBA is apredecessor to JOBB.

Supervisor authority level. The intermediate authoritylevel which allows users to control all schedules and jobsat specified stations, even if they are not authorized onthe schedule base record. However, their scope ofauthority is limited to just those stations specified on theiruser record. See General and Manager authority levels.

syntax checking. Checking JCL for syntax errors anddisplaying those errors. CA-Scheduler uses the standardOS/390 interpreter/convertor or CA-JCLCheck (if it is

installed and the JCLCHK installation option is set toYES) to perform syntax checking.

Ttracking. CA-Scheduler monitors the progress of jobsby collecting and analyzing data on events as they occur.As jobs move from station to station through the datacenter, CA-Scheduler automatically updates their status inits active workload.

Vvariable parameter. A symbolic parameter that isdefined when a procedure is cataloged and referenced inthe body of the procedure. During expansion, eachreference to the symbolic parameter is replaced with adefault or override value.

Wwork flow. The movement of jobs from station tostation through the data center.

workday. Any day that is not designated a weekend ora holiday on a calendar or date table.

workload. The work CA-Scheduler anticipatessubmitting each day. That includes:

■ the schedules and jobs automatically selected byautoscan to run on that production day based on theinformation stored in the CA-Scheduler database and

■ the schedules and jobs manually added by users

See selection.

workload documentation. The CA-Scheduler file thatcontains workload documentation entries. The defaultname of the file is CAIJDCM.

workstation. Every area where a job is scheduled forprocessing as it makes its way through the data center.Examples include production control, data entry, JCLsetup, CPU processing, and report distribution stations.Also called a station.

X-8 Online Guide

Index

Special Characters= (Jump character) 1-9$DYNxxxx schedule 9-21*REMOTE value

and remote scheduling 11-1Execution node field 5-8Remote execution node field 5-35

AAbend option field

Job definition panel 5-37, 10-16ABENDED

statusactivating jobs and schedules 9-21job recovery 10-16reports 9-18

Accountingcode in date tables 5-102cycles

criteria keywords 7-3, 7-16Date Translation report 7-20using date tables 7-2, 7-12, 9-5

periods 7-46ACTIVE

queue 9-21, 10-8active workload

additions 9-21backlogged work 10-13during autoscan 9-4FORCE command 9-20global parameters 9-9INACTIVE queue 10-8initialization 9-9reports 9-18REQUESTED keyword 9-21RESTAGE command 4-146, 10-16user-defined reports 9-18

ADAY keyword 7-3, 7-16, 7-19, 7-46ADD command

automatic recovery 10-17definition 9-21

Add CPU job panel 4-48ADD JOB command 4-46Add Job Command panel 4-46Add Non-CPU job panel 4-54Add panel 4-45ADD PRED command 4-61Add Pred Command panel 4-61Add Preds panel 4-56Add Successors panel 4-58Adding

See also Definingapplications 9-14, 9-15Driver parms 5-62existing jobs to workload 4-149flows 5-110jobs

compared to other commands 9-21panel 4-46, 4-61

predecessors 4-56stations 9-4successors 4-58

ADOM keyword 7-3, 7-16, 7-46ALLOC command 4-63Alloc Command panel 4-63Allocating data sets 4-63ALTER command

JBR 5-29JIR 5-53JMR 5-46JNR 5-52JRC 5-48JRR 5-42JSI 5-41JSR 5-58SBR 5-6

Index X-9

ALTER command (continued)SIR 5-21SMR 5-15SRC 5-17SSI 5-14

ALTER FLOW command 5-111ALTER JCR 5-57ALTER Jxx command 5-29ALTER RESOURCE command 5-81ALTER SHRRSR command 5-89ALTER STATION command 5-75ALTER Sxx command 5-6ALTER USERID command 5-68Altering

calendars 5-93date tables 5-100documentation members 5-106Driver parms 5-62flows 5-111initiators 5-87job criteria record 9-27job sets 5-1jobs 5-29

base record 5-30criteria record 5-57information record 5-53message record 5-46node record 5-52reason code record 5-48resource record 5-42security information record 5-41step code record 5-58

predecessors 9-27resources 5-81schedules

base record 5-6criteria record 5-24message record 5-15reason code record 5-17security information record 5-21

shared resources 5-89staging members 4-39stations 5-75user IDs 5-68

AMOY keyword 7-3, 7-27, 7-46Analysis reports 9-11, 9-15ANALYZE command

issuing 9-11verifying new applications 9-15

ANALYZE JOB command 6-4

Analyze job panel 6-4Analyze menu 6-3ANALYZE SCHEDULE command 6-6Analyze schedule panel 6-6AND keyword

combined selection and predecessor example 7-7date table example 7-19debugging errors 7-33, 7-34inactive queue example 10-12overview 7-39use in Boolean expressions 7-3using multiple conditions 7-9

Applicationsadding 9-15verifying 9-15

Authorization types 5-70AUTO START field

pre-CPU jobs 9-4, 9-7AUTOINIT value 4-13Automatic recovery

ADD command 10-17CAJUCMD0 10-17REQUEST command 10-17RUN command 10-17

AutoscanAUTOINIT value 4-13backlogged work

defined 10-13Job definition panel 5-31performing autoscan 9-4Schedule definition panel 5-7spanning two autoscans 9-27

command file 8-1displaying dates 4-84displaying times 4-43global parameters 9-9process 9-4purges jobs 10-8, 10-10status 4-82time 5-11

AUTOSEL keywordbatch commands for SBR 7-11SBR panel 5-7

AWOF keyword 7-3AWOM keyword 7-16, 7-46

BBacklog

autoscan time 9-4, 9-27, 10-13definition 10-13

X-10 Online Guide

Backlog (continued)symptom of deadlock 9-16

BACKLOG fieldJob definition panel 5-31, 10-13Schedule definition panel 5-7, 10-13

Backout jobsautomatic recovery option 10-17Job definition panel 5-37reason code 4-7, 4-22

Boolean expressions 7-3Build monitor commands 4-1Bypass GDG field

Rerun Job panel 4-144Submit job panel 4-162

CCA-11

ADD CPU Job panel 4-53CPU Job status detail panel 4-27Job definition panel 5-38Rerun job panel 4-142, 4-143restarting jobs 10-15Schedule status panel 4-13Submit job panel 4-161

CA-Dispatch 9-10CA-Earl reporting

creating 9-18list 9-18Pending Job Profile report 10-14

CA-JCLCheckoverview 9-7simulation 9-15

CA-Opera 9-10CA-Roscoe library type

Add CPU job panel 4-50CPU job status detail panel 4-27Job definition panel 5-34Schedule status panel 4-12

CA-Scheduler Agent 11-1initiating and tracking jobs 11-1

CAICCI 11-1CAIENF

shut down 9-24subsystem 9-23, 9-24

CAIJ$DSN macro display 4-85CAIJ$MVS macro display 4-86CAIJDCF member 8-1CAIJGEN SECURTY option

See Installation options

CAIJMVS macro display 4-87CAJUCMD0 utility

automatic recovery 10-17issuing online commands in batch 9-20resetting global parameters 9-28

CAJUTIL0 utilityANALYZE command 9-11, 9-15FORECAST command 9-16ONLY command 9-16SIMULATE command 9-16

CAJUTSTB member 9-17Calendars

definition panel 5-95, 7-22holidays 7-21menu 5-93methodology 7-21, 9-5overview 7-2, 7-12prototype 5-95, 7-21workdays 5-95, 7-21

CANCEL ALL command 4-70CANCEL command

CANCEL ALL 4-70CANCEL JOB 4-66CANCEL SCHEDULE 4-68impacts dependencies 9-26

Cancel Commands panel 4-65CANCEL JOB command 4-66Cancel Post (CP) Commands panel 4-73CANCEL SCHEDULE command 4-68CANCELLED

status 9-21CANCLD status 10-16CASCHD member 9-20Checking JCL syntax 9-15CICS

CICS 1-16Editor 1-19interface 1-18PF key settings (default) 1-16

Cjobchan panel 6-26Cjobrchn panel 6-35Command file, autoscan 8-1Command Output from Status

Options panel 3-2Command Prompt from Status

Options panel 3-2Commands

ADD JOB 4-46ADD PRED 4-61adding to the workload 9-20ALLOC 4-63

Index X-11

Commands (continued)ALTER FLOW 5-111ALTER Jxx 5-29ALTER RESOURCE 5-81ALTER SHRRSR 5-89ALTER STATION 5-75ALTER Sxx 5-6ALTER USERID 5-68ANALYZE JOB 6-4ANALYZE SCHEDULE 6-6CANCEL ALL 4-70CANCEL JOB 4-66CANCEL SCHEDULE 4-68COMPLETE JOB 4-71control

where they can be issued 9-20CP JOB 4-74CP SCHEDULE 4-77DEALLOC 4-80DEFINE FLOW 5-111DEFINE Jxx 5-29DEFINE RESOURCE 5-81DEFINE SHRRSR 5-89DEFINE STATION 5-75DEFINE Sxx 5-6DEFINE USERID 5-68DELETE FLOW 5-111DELETE JOB 5-29DELETE RESOURCE 5-81DELETE SCHEDULE 5-6DELETE SHRRSR 5-89DELETE STATION 5-75DELETE USERID 5-68DEXPAND 4-40DISPLAY $DSN 4-85DISPLAY $MVS 4-86DISPLAY $SEC 4-87DISPLAY ALLOC 4-83DISPLAY DATE 4-84DISPLAY EVENTS 4-88DISPLAY FLOW 4-88DISPLAY NETWORK 4-87DISPLAY VRM 4-89DISPLAY XPLAT 4-88DPROMPT 4-42entering 1-10FORCE JOB 4-91FORCE SCHEDULE 4-93HOLD ALL 4-100HOLD JOB 4-97HOLD SCHEDULE 4-99

Commands (continued)HOLD SUBMIT 4-101in remote scheduling 11-3issuing 4-1LIST FLOW 5-111LIST JOB 5-29LIST SCHEDULE 5-6LIST STATION 5-75LIST USERID 5-68menu 4-43Monitor 4-1POST DSN 4-116POST JOB 4-106POST MVS 4-118POST SCD 4-109POST SJOB 4-111POST SSCD 4-114POST STEP 4-120POST Unscheduled Job 4-118PURGE ALL 4-128PURGE JOB 4-125PURGE SCHEDULE 4-127RECALL 4-41RELEASE ALL 4-133RELEASE AUTO 4-134RELEASE JOB 4-130RELEASE SCHEDULE 4-132RELEASE SUBMIT 4-137RELEASE USER 4-135RELEASE USERALL 4-136REPORT ABEND 6-8REPORT AUDIT 6-10REPORT CJOBCHAN 6-26REPORT CJOBRCHN 6-35REPORT COMPLETE 6-12REPORT CSCDCHAN 6-28REPORT CSCDRCHN 6-37REPORT DATETRAN 6-14REPORT JOBAVG 6-16REPORT JOBCHAIN 6-22REPORT JOBHIST 6-17REPORT JOBRCHAN 6-31REPORT MAILBOX 6-18REPORT OPTIONS 6-20REPORT SCDCHAIN 6-24REPORT SCDRCHAN 6-33REQUEST JOB 4-139REQUEST SCHEDULE 4-140RERUN JOB 4-142RESTAGE JOB 4-146RUN JOB 4-149

X-12 Online Guide

Commands (continued)RUN SCHEDULE 4-151SET GBLxnn 4-95SREQ JOB 4-154SREQ SCHEDULE 4-156START JOB 4-158SUBMIT JOB 4-160TALTER JOB 4-20TALTER SCHEDULE 4-5UNPOST DSN 4-175UNPOST JOB 4-165UNPOST MVS 4-177UNPOST SCD 4-168UNPOST SJOB 4-170UNPOST SSCD 4-173UNPOST STEP 4-179VARY ACT 4-184VARY INACT 4-185VARY VRM 4-186

Commands menu 4-43Comments in remote scheduling 11-2Commonly asked questions 9-2Communicating with CA-Scheduler Agent 11-1Communicating with Unicenter TNG 11-1COMPLETE command

non-CPU stations 9-4, 9-7with

INTERRUPTED status 9-10Complete Job Command panel 4-71Conditions causing selection 7-1, 7-4, 7-6, 7-9Console

commands 9-20messages 9-20

Controlcommands

for recovery 10-16on Status panels 9-26where they can be issued 9-20

Copyingcalendar 5-99date table 5-105documentation member 5-109job 5-65job step entry 5-60schedules 5-25station 5-77User ID 5-72

CP commands 4-73CP JOB command 4-74CP SCHEDULE command 4-77

CPM 5-110CPU resource panel 5-83CPU station 5-73, 9-4Criteria language

job selection 7-3overview 7-1schedule selection 7-3subtleties 10-9vocabulary 7-39

Criteria recordjob 5-57, 9-27schedule 5-24, 7-11

Criteria, predecessors 7-6Critical Path Monitor system

tracking flows 5-110Cross-platform nodes

displaying 4-88Cscdchan panel 6-28Cscdrchn panel 6-37Cyclic scheduling 7-41

DDAILY keyword

calendar mechanism 7-13definition 7-2, 7-12example 7-4Gregorian calendar 7-3Gregorian calendar conditions 7-41staging a job 9-7

DASD definition 5-80Data sets

allocating 4-63displaying those allocated to CA-Scheduler started

task 4-83Database

command entry 1-10menu 5-1reports 9-18

Date tablecycles 9-5definition panel 5-102, 7-16menu 5-100methodology 7-15, 9-5overview 7-2, 7-12prefix 5-102, 5-104, 9-5

Date Translation report 7-19Days-of-the-

month keywordsabbreviations 7-41accounting cycles 7-46workdays 7-41

Index X-13

Days-of-the- (continued)week keywords

abbreviations 7-41accounting cycles 7-46workdays 7-44

DCFERR parameter 8-1Deadlocks

examples 7-33preventing 9-11Report analyze panel 6-3verifying a new application 9-15, 9-16

Dealloc Command panel 4-80Default Analyze List Type field

Options panel 3-1Default PF key settings

CICS 1-16ISPF 1-15

Default Start/Complete StationOptions panel 3-2

DEFINE FLOW command 5-111DEFINE JCR 5-57DEFINE Jxx command 5-29DEFINE RESOURCE command 5-81DEFINE SHRRSR command 5-89DEFINE STATION command 5-75DEFINE Sxx command 5-6DEFINE USERID command 5-68Defining

calendars 5-93DASD 5-80date tables 5-100flows 5-110global parameters 4-95, 7-5, 9-8initiators 5-87job sets 5-1jobs 5-29

base record 5-30criteria record 5-57information record 5-53message record 5-46node record 5-52reason code record 5-48resource record 5-42security information record 5-41

predecessors 4-56, 7-1, 7-6, 9-22resources 5-81schedule criteria record 7-11schedule order 9-6schedules 5-6

base record 5-6criteria record 5-24message record 5-15

Defining (continued)schedules (continued)

reason code record 5-17security information record 5-21

shared resources 5-89staging members 4-39stations 5-75, 9-4successors 4-58user IDs 5-68work schedules

calendars 7-21, 7-23holidays 7-15, 9-5

Delete Confirmation fieldOptions panel 3-1

DELETE FLOW command 5-111DELETE JCR 5-57DELETE JOB command 5-29DELETE RESOURCE command 5-81DELETE SCHEDULE command 5-6DELETE SHRRSR command 5-89DELETE STATION command 5-75DELETE USERID command 5-68Deleting

calendars 5-93date tables 5-100documentation members 5-106Driver parms 5-62flows 5-111initiators 5-87job sets 5-1jobs 5-29resources 5-81schedules 5-6shared resources 5-89stations 5-75user IDs 5-68

Dependencies 7-1DEXPAND command 4-40Directory

calendars 5-94date tables 5-101documentation 5-108job 5-27resources 5-79schedule 5-4station 5-74

DISPLAY $DSN command 4-85DISPLAY $MVS command 4-86DISPLAY $SEC command 4-87DISPLAY ALLOC command 4-83

X-14 Online Guide

Display Commands panel 4-82DISPLAY DATE command 4-84DISPLAY EVENTS command 4-88DISPLAY FLOW command 4-88Display Key field

Job definition panel 5-40, 9-14DISPLAY NETWORK command 4-87Display Time field

Job definition panel 5-41DISPLAY VRM command 4-89DISPLAY XPLAT command 4-88Displaying

autoscan dates 4-84CAIJ$DSN macro contents 4-85CAIJ$MVS macro contents 4-86calendars 5-93cross-platform nodes 4-88current job information 4-20data sets allocated to CA-Scheduler started task 4-83date tables 5-100documentation members 5-106events 4-88flow 4-88global parameters 9-9NJE VTAM session status 4-87predecessors 4-38security 4-87VRM 4-89

Documentationdisplaying members 5-106menu 5-106printing 9-14reports 9-18

DOM keyword 7-27, 7-41, 7-46Domains in remote scheduling 11-4DPROMPT command 4-42Driver

DEXPAND command 4-40expanding Driver procedures 4-40job submission 9-21listing reserved variables 4-42parms panel 5-62recovery 10-15, 10-17, 10-20returning JCL to original contents 4-41

DSN keywordoverview 7-5, 7-39with PRED keyword 9-22

EEARLY START field

Job definition panel 5-31, 9-7Schedule definition panel 5-11

EditingJCL 4-146with CICS 1-19

EFFDATE keyword 8-1ENDED status 9-21ENFDOWN HELD status 9-24Entering

database commands 1-10tracking commands 1-10

Eventsdisplaying 4-88

Expanding Driver procedures 4-40EXPDATE keyword 8-1Explicit predecessors 7-5External security

Display Commands panel 4-82Job security panel 5-41Schedule security panel 5-14setting 5-66

FFail Code field

Add CPU job panel 4-51CPU job status detail panel 4-28Job definition panel 5-37, 10-16Post job step panel 4-121Unpost job step panel 4-180

Fail Oper fieldAdd CPU job panel 4-51CPU job base panel 5-36CPU job status detail panel 4-28Job step panel 5-61Post job step panel 4-121Unpost job step panel 4-180

Fail Option fieldAdd CPU job panel 4-52CPU job base panel 5-37CPU job status detail panel 4-29

FAILEDstatus 9-21, 10-16

Flowdisplaying 4-88

Flows 5-110Force Command

definition 9-20

Index X-15

Force Command (continued)panel 4-90with WAIT status 9-22

FORCE JOB command 4-91FORCE SCHEDULE command 4-93Forecast

overview 9-14verifying applications 9-16

FREECMD panel 4-187Freeform command 4-187Freeing a data set 4-80Frequencies

MONTHLY 7-21, 7-23WEEKLY 7-21, 7-23

GGBLxnn keyword

defined 9-8example 7-34panel 4-95reserved word 7-5resetting 9-28

GDG keyword 7-5, 7-39General authority 5-70Global parameters

defining 7-5, 9-8displaying values 9-9example 7-34panel 4-95setting values 9-28testing values 9-20

Gregorian calendar 7-2, 7-3, 7-12Grouping jobs 9-6

HHDAY keyword

and date tables 7-15date table example 7-19examples 7-25, 7-28holiday scheduling 7-44selection example 7-4selection use 7-3

HELDstatus 9-21

Help 1-17History reports 9-18HOLD ALL command 4-100Hold Commands panel 4-96

HOLD JOB command 4-97HOLD SCHEDULE command 4-99HOLD SUBMIT command 4-101Holiday scheduling 7-44

IIgnoring predecessors 9-20Implicit predecessor 7-8, 9-6INACTIVE queue 9-21, 10-8Initiators 5-87Insert CA-11 field

ADD CPU Job panel 4-53Job definition panel 5-38Schedule definition panel 5-9Schedule status panel 4-13

Insert CA-11 RMS fieldCPU Job status detail panel 4-27Rerun Job panel 4-143Submit job panel 4-161

INSERT RMS PROC fieldJob Definition panel 10-15

Insert Sched EnviroCPU Job status detail panel 4-27Schedule status panel 4-12

Installation options$DYNNM 4-47AUTOTIM 5-82BACKOUT 4-29, 4-52, 5-37CA11 4-142, 4-160, 5-9DATETAB 5-7displaying 6-20ENDMSG 5-16FALMSG 5-48INSROUT 5-35INSRRMS 5-9INSRSenv 5-35INSRSYS 5-35LATMSG 5-16LIBTYPE 4-49, 4-50, 5-8, 9-6MCPU 5-43MSGHOLD 5-16, 5-48NJE

Job status detail panel 4-30Schedule base panel 5-8Schedule status detail panel 4-6, 4-10

SECURTYand JSI 5-41and passwords 5-69and SSI 5-14and user definitions 5-66and user ID requirements 5-2

X-16 Online Guide

Installation options (continued)SECURTY (continued)

Post Job Start panel 4-112Post Job Step panel 4-122Unpost Job Start panel 4-171Unpost Job Step panel 4-181

SKPMSG 5-16SPRTY 5-13, 5-32STAGE 5-10STRMSG 5-16SUBUID 4-31, 5-14, 5-41

Internal securitySchedule base panel 5-13Schedule status detail panel 4-14

Interrupt fieldJob definition panel 5-38, 9-10

Interruptedjobs 9-10

INTERRUPTED status 9-21

JJBR panel 5-29JCL

errors 10-17staging 4-146, 9-4, 9-6, 9-18syntax checking 9-15

JCR panel 5-28, 5-57JES

class 4-33, 4-55, 5-9, 5-40job number 6-17node 5-52Original JES number 4-22priority 4-33, 4-55, 5-10, 5-40

JIR panel 5-53JMR panel 5-46JNR panel 5-52Job

abends 9-21, 10-16average panel 6-16base record (JBR) 5-29canceling 9-26criteria record (JCR) 5-57, 9-27definition panel 5-29, 9-10, 10-16forcing 4-91history panel 6-17holding 4-97information record (JIR) 5-53maintaining 5-29menu 5-26message record (JMR) 5-46, 10-17

Job (continued)node record (JNR) 5-52posting 4-105purging 4-125, 9-26reason code record (JRC) 5-48recovery 10-15releasing

panel 4-130requesting

panel 4-139rerunning 9-10, 10-15

Rerun Job Command panel 4-142Run Job Command panel 4-149Submit Job Command panel 4-160

resource record (JRR) 5-42running 4-149security information record (JSI) 5-41selection

additions 9-21criteria language 7-1, 7-3rule 7-11with REQUESTED 9-21, 10-8

staging 9-6status detail panel 4-20status menu 4-16step panel 5-58step record (JSR) 5-58submission

automatic 9-7manual 9-20

Summary report 9-16job sets 5-1JOBA SCHDA keyword 7-4JOBA-02 40 SCHDA keyword 7-4JOBA.PROC1.STEP2-02 40 SCHDA keyword 7-4JOBA.PROC1.STEP2.CC.GT.00008-02 40 SCHDA

keyword 7-4JOBA.STEP2-02 40 SCHDA keyword 7-4JOBA.STEP2.CC.GT.00008-02 40 SCHDA

keyword 7-4Jobchain panel 6-22Jobrchan panel 6-31JRC panel 5-48JRR panel 5-42JSI panel 5-41JSR panel 5-58Jump character 1-9Jump commands 4-5

Index X-17

KKeywords

ADAY 7-3, 7-16, 7-19, 7-46ADOM 7-3, 7-16, 7-46AMOY 7-3, 7-27, 7-46AND

date table example 7-19debugging errors 7-33, 7-34inactive queue example 10-12overview 7-39use in Boolean expressions 7-3using multiple conditions 7-9

AUTOSELbatch commands for SBR 5-7, 7-11

AWOF 7-3AWOM 7-16, 7-46combined selection and predecessor example 7-7DAILY

calendar mechanism 7-13definition 7-12Gregorian calendar 7-3Gregorian calendar conditions 7-41overview 7-2selection example 7-4

DOM 7-27, 7-41, 7-46DSN

and predecessors 7-39overview 7-5with PRED keyword 9-22

examples 7-25, 7-28GBLxnn

defined 9-8example 7-34reserved word 7-5resetting 9-28

GDG 7-5, 7-39HDAY

and date tables 7-15date table example 7-19examples 7-25, 7-28selection example 7-4selection use 7-3workday conditions 7-44

JOB SCHDA 7-4LEAP-YEAR 7-41LIBTYPE

batch commands for SBR 9-17MVS

predecessor 7-5, 7-39NJE 7-5, 7-39

Keywords (continued)NOT

and GBLXnn predecessors 9-9and predecessors 7-10date table example 7-19debugging errors 7-34examples 7-28overview 7-39use in Boolean expressions 7-3

ORand predecessors 7-9date table example 7-19debugging errors 7-32, 7-34examples 7-25, 7-28overview 7-39predecessors 10-9use in Boolean expressions 7-3using multiple conditions 7-9

PREDresetting PRED flag 9-22usage 7-5, 7-39

RDnn 7-3, 7-4, 7-15, 7-45REQUESTED

daily processing 9-21Gregorian calendar conditions 7-41impact on successors 10-9jobs purged by autoscan 10-8, 10-10purpose 10-8selecting jobs with 10-8selecting schedules with 10-8

SCDcombined selection and predecessor example 7-7defining predecessor conditions 7-5predecessors 7-3, 7-5, 7-39selection example 7-4

staging a job 9-7START

and NJE 7-5predecessor example 7-5, 7-39selection example 7-4selection keyword 7-3

WDAYand date tables 7-15date table example 7-19examples 7-26, 7-28selection example 7-4selection use 7-3workday conditions 7-44

WDOMand date tables 7-15examples 7-24, 7-29selection example 7-4

X-18 Online Guide

Keywords (continued)WDOM (continued)

selection use 7-3workday conditions 7-44

WDOWand date tables 7-15date table example 7-19selection example 7-4, 7-24selection use 7-3workday conditions 7-44

WEEK-DAYcalendar mechanism 7-13Date Translation report 7-20definition 7-2, 7-12example 7-27Gregorian calendar 7-3Gregorian calendar conditions 7-41

WEEK-END 7-3, 7-41WWOM 7-15, 7-19, 7-44WWOY 7-44xDAY 7-3, 7-16, 7-19, 7-46xDOM 7-3, 7-16, 7-19, 7-46xMOY 7-3, 7-27, 7-46xWOF 7-3xWOM 7-16, 7-46xWOY 7-19

LLATE

status 9-18LEAP-YEAR keyword 7-41Library Type field

Job definition panel 5-33, 9-15Schedule definition panel 5-8, 9-17

LIBTYPE installation option 9-6LIBTYPE keyword

batch commands forSBR 9-17

LIST FLOW command 5-111LIST JOB command 5-29List option 3-1, 9-15LIST SCHEDULE command 5-6LIST STATION command 5-75LIST USERID command 5-68Listing

calendars 5-93date tables 5-100documentation members 5-106Driver reserved variables 4-42flows 5-111

Listing (continued)jobs 5-29resources 5-79schedules 5-6stations 5-75user IDs 5-68

Locating command 1-13Logging on 2-2

MMAILBOX value 5-16Main menu 2-3Maintaining

calendars 5-93date tables 5-100documentation members 5-106jobs 5-29schedules 5-6shared resources 5-89stations 5-75user IDs 5-68virtual resources 5-63

Manager authority 5-70Mark job as complete 4-71Message

interrupted jobs 9-10operator 9-10record (JMR) 5-46record (SMR) 5-15routing 9-20

Messagesdefinition panel (JMR) 5-46definition panel (SMR) 5-15

Messages Menu panel 4-102Monitor

commands 4-188menu 4-1

Month keywords 7-46MONTHLY

frequency 7-21, 7-23scheduling 7-41, 7-44

Multiple Schedulers 8-3MVS keyword

overview 7-39predecessor 7-5

NNavigating panels 1-9

Index X-19

NJECAIENF startup 9-24Display NJE datasets panel 4-85displaying network 4-87job node inform panel 5-51keyword 5-52, 7-5, 7-39network 4-87starting and stopping VTAM sessions 4-183VTAM session status 4-87

NO BACKLOG CNCL status 10-13Node name

CPU job base panel 5-35in remote scheduling 11-2Job status detail panel 4-21Schedule status detail 4-6

Node record 5-52Nonshared resources 5-80Normal calendar 5-93NOT keyword 7-10, 9-9

date table example 7-19debugging errors 7-34examples 7-28overview 7-39selection use only 7-3

NOTIFY keyword 5-22, 5-54Numbering stations 9-4

OONLY command

forecast 9-16simulation 9-16

Operatorconsole 9-20messages 9-10

OPERATOR CANCLD status 10-16Options menu panel 3-1OR keyword

and predecessors 7-9, 10-9date table example 7-19debugging errors 7-32, 7-34examples 7-25, 7-28overview 7-39use in Boolean expressions 7-3using multiple conditions 7-9

Organizing schedules 9-6Overriding

Driver parms 5-62predecessors 9-20, 9-21start times 9-20

PPANV library type

Add CPU job panel 4-49CPU job base panel 5-33, 5-34CPU job status detail panel 4-26Schedule base panel 5-8Schedule status detail panel 4-12

Parentheses in criteriadate table example 7-19debugging errors 7-33, 7-34examples 7-25, 7-27, 7-28, 7-29overview 7-39separating reasons 7-9use in Boolean expressions 7-3

Parms panel 5-62Passwords and remote scheduling 11-5Pending Job Profile report 10-14Periods 7-46PF key settings (default)

CICS 1-16ISPF 1-15

POST DSN command 4-116POST JOB command 4-106Post Menu panel 4-105POST MVS command 4-118POST SCD command 4-109POST SJOB command 4-111POST SSCD command 4-114POST STEP command 4-120POST Unscheduled Job command 4-118PRED

flag 9-22keyword 7-5, 9-22

PRED keyword 7-39Predecessor display panel 4-38Predecessors

altering 9-27deadlock 7-33, 9-11, 9-15, 9-16defining 7-1, 7-6, 9-22displaying 4-38explicit 7-5global parameters 9-8implicit 7-8, 9-6listing for

current job 6-35current schedule 6-37specific job 6-31specific schedule 6-33

loop 6-3, 7-33, 9-11, 9-15menu 6-30

X-20 Online Guide

Predecessors (continued)nonscheduled OS/390 job 7-5other jobs or schedules 7-3, 7-5overriding 9-20reserved words 7-5satisfying 4-105tasks starting 7-3user-defined event 9-8with

NOT keyword 7-10OR keyword 7-9, 7-26, 7-32, 10-9

Predicting the workload 9-14Prefixes for date tables 5-102, 5-104Prerequisites 7-1Printing jobs 9-4Production

cycles 7-16, 9-5day 10-13

Prototype calendars 5-93, 7-21PURGE ALL command 4-128Purge Command

impacts dependencies 9-26panel 4-124

PURGE JOB command 4-125PURGE SCHEDULE command 4-127

QQueue

ACTIVE 9-21, 10-8INACTIVE 9-21, 10-8

RRC code

job 4-21schedule 4-6

RDnn keyword 7-3, 7-4, 7-15, 7-45Reason codes

job (JRC) 5-48schedule (SRC) 5-17

Reason(s)code (JRC) 5-48code (SRC) 5-17codes (criteria language) 7-9for selection 7-1job selection code 4-21multiple 7-9schedule selection code 4-6

RECALL command 4-41

RecoveryDriver 10-17scheduled jobs 10-15system crash 9-24

Relative daysand date tables 7-15Date Translation report 7-20scheduling 7-45selection example 7-4selection use 7-3

RELEASE ALL command 4-133RELEASE AUTO command 4-134Release Commands panel 4-129RELEASE JOB command 4-130RELEASE SCHEDULE command 4-132RELEASE SUBMIT command 4-137RELEASE USER command 4-135RELEASE USERALL command 4-136Remote scheduling

command 11-3comments 11-2domains 11-4Execution node field 5-8node name 11-2password 11-5Remote execution node field 5-35user ID 11-4

Removingall schedules and jobs from workload 4-70canceled and completed work 4-124job from current workload 4-66, 4-74job from status display 4-125schedule from current workload 4-68, 4-77schedule from status display 4-127work from current workload 4-65, 4-73

REPORT ABEND command 6-8Report abend panel 6-8REPORT AUDIT command 6-10Report audit panel 6-10REPORT CJOBCHAN command 6-26REPORT CJOBCHAN panel 6-26REPORT CJOBRCHN command 6-35REPORT CJOBRCHN panel 6-35REPORT COMPLETE command 6-12Report complete panel 6-12REPORT CSCDCHAN command 6-28REPORT CSCDCHAN panel 6-28REPORT CSCDRCHN command 6-37REPORT CSCDRCHN panel 6-37REPORT DATETRAN command 6-14

Index X-21

Report datetran panel 6-14REPORT JOBAVG command 6-16REPORT JOBCHAIN command 6-22REPORT JOBCHAIN panel 6-22REPORT JOBHIST command 6-17REPORT JOBRCHAN command 6-31REPORT JOBRCHAN panel 6-31REPORT MAILBOX command 6-18Report mailbox panel 6-18REPORT OPTIONS command 6-20Report options panel 6-20REPORT SCDCHAIN command 6-24REPORT SCDCHAIN panel 6-24REPORT SCDRCHAN command 6-33REPORT SCDRCHAN panel 6-33Reports

abended 6-8analysis 6-3, 9-11, 9-15CA-Earl 9-18database 9-18date translation 6-14, 7-19documentation 9-18forecast 9-14history 6-12, 9-18installation options 6-20job history 6-17Job Summary report 9-16Mailbox 6-18menu 6-1Pending Job Profile report 10-14predecessors 6-3, 6-30simulation 9-14successors 6-21user-defined 9-18

REQUEST commandautomatic recovery 10-17compared to SREQ command 9-21panel 4-138with

INACTIVE queue 10-8predecessors 10-10

REQUEST JOB command 4-139REQUEST SCHEDULE command 4-140REQUESTED keyword

activating work 4-138daily processing 9-21impact on successors 10-9jobs purged by autoscan 10-8, 10-10overview 7-41purpose 10-8selecting jobs with 10-8

REQUESTED keyword (continued)selecting schedules with 10-8

RERUN JOB command 4-142definition 9-20submitting jobs with 9-20with

ABENDED status 10-16CANCLD status 9-22, 10-16FAILED status 10-16INTERRUPTED status 9-10

Rerun Job Command panel 4-142Reserved Driver variables 4-42Reserved words

criteria language 7-39criteria vocabulary 7-3predecessors 7-5

ResettingGDG bias numbers 10-18global parameters 9-28PRED flag 9-22relative generation pointers 10-18

Resourcedefinition panel 5-80menu 5-78Nonshared 5-81panel 5-81requirements 9-7Shared 5-89

RESTAGE JOB command 4-146job recovery 10-16usage 9-7

Restage Job Command panel 4-146Restart

instructions 10-15JCL parameter 10-19

Restarting jobswith CA-11 10-15with Driver 10-17

RHOLD=YES startup option 4-134RMSPROC 10-15Run Book report 9-14Run Command

panel 4-148staging jobs 9-6

RUN JOB commandautomatic recovery 10-17compared to other commands 9-21panel 4-149usage 9-22with

CANCLD status 10-16

X-22 Online Guide

RUN JOB command panel 4-149RUN SCHEDULE command

compared to other commands 9-21panel 4-151

RUN SCHEDULE command panel 4-151

SSales cycles 7-16, 9-5Satisfying predecessor conditions 4-105SBR panel 5-11SC prefix 1-10SCD keyword

and predecessors 7-3combined selection and predecessor example 7-7defining predecessor conditions 7-5predecessors 7-5, 7-39selection example 7-4

Scdchain panel 6-24Scdrchan panel 6-33SCHD prefix 1-10Schedule

base record (SBR) 5-11copying 5-25criteria record (SCR) 5-5, 5-24, 7-11definition panel 5-6directory panel 5-4forcing 4-93holding 4-99information record (SIR) 5-21maintaining 5-6message record (SMR) 5-15options panel 5-5order 9-6panel 5-3posting 4-105purging 4-127reason code record (SRC) 5-17recovery 10-15releasing

panel 4-132requesting

panel 4-140running 4-151security record (SSI) 5-14selection

additions 9-21criteria language 7-1, 7-3rule 7-11with REQUESTED 9-21, 10-8

status detail panel 4-5

Schedule (continued)status panel 4-2

SchedulingSee also Remote Schedulingcyclic 7-41daily 7-41holiday 7-44jobs 7-11, 7-21monthly 7-41, 7-44overview 11-1period 7-46relative day 7-45weekly 7-41, 7-44yearly 7-41

Scheduling EnvironmentCPU Job status detail panel 4-28Schedule status panel 4-13

SCR panel 5-5, 5-24Security

displaying 4-87Job security panel 5-41Schedule security panel 5-14Schedule status detail panel 4-14SSI record 5-14user IDs 5-66

SECURTY option in CAIJGENSee Installation options

Selectingflows 5-111jobs

criteria language 7-3with ADD command 9-21with REQUESTED keyword 9-21, 10-8with RUN command 9-21with schedules 7-11

schedulescriteria language 7-3instead of jobs 7-11methods 9-5with REQUESTED keyword 9-21, 10-8with RUN command 9-21

Selectioncode 4-21criteria 7-11

Sending messagesabended jobs 10-17failed jobs 10-17interrupted jobs 9-10to other users 9-20to the console 9-20

Index X-23

SEPARATE fieldsJob resource panel 5-42, 9-7

SET command 4-95Shared resource definition panel 5-89Shared tape panel 5-90Shared units panel 5-91Shutting down

CA-Scheduler 9-23CAIENF 9-24

SIMULATE command 9-16Simulation

overview 9-14testing applications 9-15verifying applications 9-16

Simulation reportsand resource definitions 5-78and station definitions 5-73

SIR panel 5-21SMR panel 5-15Sorting displays 1-11Specific dates 7-21SRC panel 5-17SREQ command

compared to REQUEST command 9-21with

INACTIVE queue 10-8predecessors 10-10

SREQ Commands panel 4-153SREQ JOB command 4-154SREQ SCHEDULE command 4-156SSI panel 5-14SSI record

panel 5-14Stage JCL field

Job definition panel 5-38, 9-6Schedule base panel 5-10

Staged JCL panel 4-39Staging jobs

Restage job panel 4-146Staged JCL panel 4-39station numbering 9-4when 9-6

START JOB command 4-158Start Job Command panel 4-158START keyword 7-3, 7-4, 7-5, 7-39Starting

jobs 9-20schedules 9-9, 9-20

Station40 5-73adding 5-73, 9-4

Station (continued)definition panel 5-75menu 5-73numbering 5-73, 9-4

StatusABENDED 9-18, 9-21, 10-16autoscan 4-82CANCELLED 9-21CANCLD 10-16ENDED 9-21ENFDOWN HELD 9-24FAILED 9-21, 10-16HELD 9-21INTERRUPTED 9-21LATE 9-18NO BACKLOG CNCL 10-13OPERATOR CANCLD 10-16

Status panelsdisplaying interrupted jobs 9-10issuing control commands 9-26resubmitting jobs 10-16

STATUS UNKNOWN command 9-25Step-level restart 10-18SUBMIT command

definition 9-20jobs 9-20panel 4-160with

ABENDED status 10-16CANCLD status 10-16FAILED status 10-16

SUBMIT JOB command 4-160Submit Job Command panel 4-160Submitting jobs

automatically 9-7, 9-9panel 4-160with

RERUN command 9-20SUBMIT command 9-20

SuccessorsABEND option 10-16Chain List report 9-11listing for

current job 6-26current schedule 6-28specific job 6-22specific schedule 6-24

menu 6-21REQUEST example 10-9REQUEST/SREQ command 9-22, 10-8

X-24 Online Guide

SUMMARY option for forecasts 9-16Supervisor authority level 5-70SYNCHK DCF command 8-2Syntax checking JCL 9-15System crash 9-24

TTALTER JOB command 4-20TALTER SCHEDULE command 4-5Tapes 5-80Testing applications 9-15TESTLIB library type

and testing 9-17planning new application 9-15

Tracking command entry 1-10Tutorial 1-17

UUnicenter TNG

communicating with 11-1initiating and tracking jobs 11-1statements supported 11-2

UNKNOWN status 9-25Unpost Commands panel 4-164UNPOST DSN command 4-175UNPOST JOB command 4-165UNPOST MVS command 4-177UNPOST SCD command 4-168UNPOST SJOB command 4-170UNPOST SSCD command 4-173UNPOST STEP command 4-179UNPOST Unscheduled Job command 4-177User definitions 5-66User IDs

definition panel 5-68in remote scheduling 11-4menu 5-66

User-defined events 7-34Utility program 9-11, 9-15

VVariables (Driver) 4-42VARY ACT command 4-184Vary Commands panel 4-183VARY INACT command 4-185VARY VRM command 4-186Verifying

applications 9-15workload selection 9-14

View current workload 4-1Viewing

virtual resources 5-63Virtual resources 5-115Virtual resources panel 5-63VRM

displaying 4-89VRM panel 5-63

WWDAY keyword

and date tables 7-15date table example 7-19examples 7-25, 7-26, 7-28selection example 7-4selection use 7-3workday conditions 7-44

WDOM keywordand date tables 7-15examples 7-24, 7-29selection example 7-4selection use 7-3workday conditions 7-44

WDOW keywordand date tables 7-15date table example 7-19selection example 7-4, 7-24selection use 7-3workday conditions 7-44

Week keywords 7-46WEEK-DAY keyword

calendar mechanism 7-13Date Translation report 7-20definition 7-2example 7-27Gregorian calendar 7-3Gregorian calendar conditions 7-41

WEEK-END keyword 7-3, 7-41Weekends 7-15Weekly

frequency 7-21, 7-23scheduling 7-43, 7-45

Work schedulescalendars 7-21, 7-23defining 5-100holidays 7-15, 9-5

WORK WEEK fieldDateteble Definition panel 7-16

Workdaysand date tables 7-2, 7-12, 7-15

Index X-25

Workdays (continued)date table example 7-19Date Translation report 7-20keyword table 7-15, 7-44keywords 7-3selection examples 7-4

WWOM keyword 7-15, 7-19, 7-44WWOY keyword 7-44

XxDAY keyword 7-3, 7-16, 7-19, 7-46xDOM keyword 7-3, 7-16, 7-19, 7-46xMOY keyword 7-3, 7-27, 7-46xWOF keyword 7-3xWOM keyword 7-16, 7-46xWOY keyword 7-19

YYearly scheduling 7-41

X-26 Online Guide

CA-Scheduler® Online Guide

Documents

Transcript of CA-Scheduler® Online Guide