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 users 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 users 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 users 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.1 Summary of Revisions in the Fourth Edition 1.2 Summary of Revisions in the Third Edition 1.3 Summary of Revisions in the Second Edition 1.4 Summary of Revisions . . . . . . . . . . . . . . . . . . . . . . . . 1.4.1 Product Features 1.4.2 Documentation Changes . . . . . . . . 1.5 Panel Navigation . . . . . . . . . . . . . . . 1.6 CA-Scheduler Commands . . . . . . . . . . 1.7 Sort . . . . . . . . . . . . . . . . . . . . . . 1.8 Locate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1.9 PF Keys for ISPF 1.10 PF Keys for CICS . . . . . . . . . . . . . 1.11 Tutorial . . . . . . . . . . . . . . . . . . . 1.12 CICS . . . . . . . . . . . . . . . . . . . . . 1.13 CICS Editor . . . . . . . . . . . . . . . . . 1.13.1 Adding Lines . . . . . . . . . . . . . . 1.13.2 Copying a Block of Lines . . . . . . . 1.13.3 Moving a Block of Lines . . . . . . . 1.13.4 Deleting a Block of Lines . . . . . . . 1.13.5 Repeating a Line . . . . . . . . . . . . Chapter 2. Starting CA-Scheduler Online 2.1 Logging on to CA-Scheduler . . . . . 2.2 CA-Scheduler Main Menu . . . . . . . Chapter 3. Options
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1-1 1-2 1-3 1-4 1-5 1-5 1-8 1-9 1-10 1-11 1-13 1-15 1-16 1-17 1-18 1-19 1-21 1-22 1-23 1-24 1-25 2-1 2-2 2-3 3-1 4-1 4-2 4-5 4-16 4-20 4-38 4-39 4-40 4-41 4-42 4-43
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 4. Monitor . . . . . 4.1 Schedule Status . . . . . . 4.1.1 Schedule Status Detail 4.2 Job Status . . . . . . . . . 4.2.1 Job Status Detail . . 4.2.2 Predecessor Display . 4.2.3 Staged JCL . . . . . 4.2.3.1 DEXPAND . . . 4.2.3.2 RECALL . . . . 4.2.3.3 DPROMPT . . . 4.3 Commands . . . . . . . .
Contents iii
4.3.1 Add Commands . . . . . . . . . . . . 4.3.1.1 Add Job Command . . . . . . . 4.3.1.2 Add Pred Command . . . . . . . 4.3.2 Alloc Command . . . . . . . . . . . . 4.3.3 Cancel Commands . . . . . . . . . . 4.3.3.1 Cancel Job Command . . . . . . 4.3.3.2 Cancel Schedule Command . . . 4.3.3.3 Cancel All Command . . . . . . 4.3.4 Complete Job Command . . . . . . . . . . . 4.3.5 Cancel Post (CP) Commands 4.3.5.1 Cancel Post (CP) Job Command 4.3.5.2 Cancel Post Schedule Command 4.3.6 Dealloc Command . . . . . . . . . . 4.3.7 Display Commands . . . . . . . . . . 4.3.7.1 Display Alloc Command . . . . 4.3.7.2 Display Date Command . . . . . 4.3.7.3 Display Dataset Command . . . 4.3.7.4 Display MVSJobs Command . . 4.3.7.5 Display Network Command . . . 4.3.7.6 Display Security Command . . . 4.3.7.7 Display XPLAT Command . . . 4.3.7.8 Display Events . . . . . . . . . . 4.3.7.9 Display Flow . . . . . . . . . . . 4.3.7.10 Display VRM Command . . . 4.3.8 Force Command . . . . . . . . . . . . 4.3.8.1 Force Job Command . . . . . . . 4.3.8.2 Force Schedule Command . . . 4.3.9 Globals . . . . . . . . . . . . . . . . . 4.3.10 Hold Commands . . . . . . . . . . . 4.3.10.1 Hold Job Command . . . . . . 4.3.10.2 Hold Schedule Command . . . 4.3.10.3 Hold All Command . . . . . . 4.3.10.4 Hold Submit Command . . . . 4.3.11 Messages Menu . . . . . . . . . . . 4.3.11.1 Query Messages . . . . . . . . 4.3.11.2 Send Messages . . . . . . . . . 4.3.12 Post Menu . . . . . . . . . . . . . . 4.3.12.1 Post Job Command . . . . . . . 4.3.12.2 Post Schedule Command . . . 4.3.12.3 Post Job Start Command . . . . 4.3.12.4 Post Schedule Start Command 4.3.12.5 Post Dataset Command . . . . 4.3.12.6 Post Unscheduled Job Command 4.3.12.7 Post Job Step Command . . . . 4.3.13 Purge Commands . . . . . . . . . . 4.3.13.1 Purge Job Command . . . . . . 4.3.13.2 Purge Schedule . . . . . . . . . 4.3.13.3 Purge All . . . . . . . . . . . . 4.3.14 Release Commands . . . . . . . . . 4.3.14.1 Release Job Command . . . . . 4.3.14.2 Release Schedule Command . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-45 4-46 4-61 4-63 4-65 4-66 4-68 4-70 4-71 4-73 4-74 4-77 4-80 4-82 4-83 4-84 4-85 4-86 4-87 4-87 4-88 4-88 4-88 4-89 4-90 4-91 4-93 4-95 4-96 4-97 4-99 4-100 4-101 4-102 4-102 4-103 4-105 4-106 4-109 4-111 4-114 4-116 4-118 4-120 4-124 4-125 4-127 4-128 4-129 4-130 4-132
iv Online Guide
4.3.14.3 Release All Command . . . . . 4.3.14.4 Release Auto Command . . . . 4.3.14.5 Release User Command . . . . 4.3.14.6 Release Userall Command . . . 4.3.14.7 Release Submit Command . . . 4.3.15 Request Commands . . . . . . . . . 4.3.15.1 Request Job Command . . . . . 4.3.15.2 Request Schedule Command . 4.3.16 Rerun Job Command . . . . . . . . 4.3.17 Restage Job Command . . . . . . . 4.3.18 Run Commands . . . . . . . . . . . 4.3.18.1 Run Job Command . . . . . . . 4.3.18.2 Run Schedule Command . . . . 4.3.19 SREQ Commands . . . . . . . . . . 4.3.19.1 SREQ Job Command . . . . . 4.3.19.2 SREQ Schedule Command . . 4.3.20 Start Job Command . . . . . . . . . 4.3.21 Submit Job Command . . . . . . . . . . . . . . . . . 4.3.22 Unpost Commands 4.3.22.1 Unpost Job Command . . . . . 4.3.22.2 Unpost Schedule Command . . 4.3.22.3 Unpost Job Start Command . . 4.3.22.4 Unpost Schedule Start Command 4.3.22.5 Unpost Dataset Command . . . 4.3.22.6 Unpost Unscheduled Job . . . . 4.3.22.7 Unpost Job Step Command . . 4.3.23 Vary Commands . . . . . . . . . . . 4.3.23.1 Vary Active Command . . . . 4.3.23.2 Vary Inactive Command . . . . 4.3.23.3 Vary VRM Command . . . . . 4.4 FREECMD . . . . . . . . . . . . . . . . . Chapter 5. Database . . . . . 5.1 Schedules . . . . . . . . . . 5.1.1 Directory . . . . . . . . 5.1.2 Schedule Options . . . 5.1.2.1 Schedule Definition 5.1.2.2 Schedule Criteria 5.1.3 Batch Examples . . . . 5.1.3.1 Example 1 . . . . 5.1.3.2 Example 2 . . . . 5.1.4 Copying a Schedule . . 5.2 Jobs . . . . . . . . . . . . . 5.2.1 Directory . . . . . . . . 5.2.2 Job Options . . . . . . 5.2.2.1 Job Definition . . 5.2.2.2 Job Criteria . . . . 5.2.2.3 Job Steps . . . . . 5.2.2.4 Driver Parms . . . 5.2.2.5 Virtual Resources
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4-133 4-134 4-135 4-136 4-137 4-138 4-139 4-140 4-142 4-146 4-148 4-149 4-151 4-153 4-154 4-156 4-158 4-160 4-164 4-165 4-168 4-170 4-173 4-175 4-177 4-179 4-183 4-184 4-185 4-186 4-187 5-1 5-3 5-4 5-5 5-6 5-24 5-24 5-24 5-24 5-25 5-26 5-27 5-28 5-29 5-57 5-58 5-62 5-63
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents v
5.2.3 Batch Examples . . . . . . . . . . . . . . . . . . . . . . 5.2.3.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . 5.2.3.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . 5.2.3.3 Example 3 . . . . . . . . . . . . . . . . . . . . . . 5.2.3.4 Example 4 . . . . . . . . . . . . . . . . . . . . . . 5.2.4 Copying a Job . . . . . . . . . . . . . . . . . . . . . . . 5.3 User IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . 5.3.2 User ID Definition . . . . . . . . . . . . . . . . . . . . 5.3.3 Batch Examples . . . . . . . . . . . . . . . . . . . . . . 5.3.3.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . 5.3.3.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . 5.3.4 Copying a User ID . . . . . . . . . . . . . . . . . . . . 5.4 Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . 5.4.2 Station Definition . . . . . . . . . . . . . . . . . . . . . 5.4.3 Batch Examples . . . . . . . . . . . . . . . . . . . . . . 5.4.3.1 Example 1: Define a CPU station . . . . . . . . . 5.4.3.2 Example 2: Define a JCL setup station (station 39) 5.4.4 Copying a Station . . . . . . . . . . . . . . . . . . . . . 5.5 Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . 5.5.2 Resource Definition . . . . . . . . . . . . . . . . . . . . 5.5.2.1 Nonshared Resources . . . . . . . . . . . . . . . . 5.5.2.2 Shared Resources . . . . . . . . . . . . . . . . . . 5.5.3 Batch Examples . . . . . . . . . . . . . . . . . . . . . . 5.5.3.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . 5.5.3.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . 5.6 Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . 5.6.2 Calendar Definition . . . . . . . . . . . . . . . . . . . . 5.6.3 Copying a Calendar . . . . . . . . . . . . . . . . . . . . 5.7 Datetables . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.7.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . 5.7.2 Date Table Definition . . . . . . . . . . . . . . . . . . . 5.7.3 Copying a Date Table . . . . . . . . . . . . . . . . . . 5.8 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . 5.8.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . 5.8.2 Documentation Text . . . . . . . . . . . . . . . . . . . 5.8.3 Copying a Documentation Member . . . . . . . . . . . 5.9 Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5.9.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . . 5.9.2 Flow Definition . . . . . . . . . . . . . . . . . . . . . . 5.9.3 Example . . . . . . . . . . . . . . . . . . . . . . . . . 5.10 Virtual Resources . . . . . . . . . . . . . . . . . . . . . . . 5.10.1 Directory . . . . . . . . . . . . . . . . . . . . . . . . . 5.10.2 Virtual Resource Definition . . . . . . . . . . . . . . . 5.10.2.1 Example . . . . . . . . . . . . . . . . . . . . . . . 5.10.3 VRM Job List . . . . . . . . . . . . . . . . . . . . . . 5.10.4 Job/VRM Association . . . . . . . . . . . . . . . . . . 5.10.4.1 Example . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-64 5-64 5-64 5-64 5-64 5-65 5-66 5-67 5-68 5-72 5-72 5-72 5-72 5-73 5-74 5-75 5-77 5-77 5-77 5-77 5-78 5-79 5-80 5-81 5-89 5-92 5-92 5-92 5-93 5-94 5-95 5-99 5-100 5-101 5-102 5-105 5-106 5-108 5-108 5-109 5-110 5-111 5-111 5-114 5-115 5-116 5-117 5-118 5-119 5-120 5-122
vi Online Guide
5.10.4.2 5.10.4.3 5.10.4.4 5.10.4.5
Usage Notes . . . . . . ENQ Virtual Resources Count Virtual Resources Simple Virtual Resources
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5-122 5-123 5-124 5-124 6-1 6-3 6-4 6-6 6-8 6-10 6-12 6-14 6-16 6-17 6-18 6-20 6-21 6-22 6-24 6-26 6-28 6-30 6-31 6-33 6-35 6-37 7-1 7-3 7-3 7-3 7-5 7-6 7-9 7-10 7-11 7-12 7-12 7-15 7-15 7-16 7-19 7-19 7-21 7-21 7-23 7-24 7-24 7-24
Chapter 6. Reports . . 6.1 Analyze . . . . . . . 6.1.1 Analyze Job . . 6.1.2 Analyze Schedule 6.2 Report Abend . . . . 6.3 Report Audit . . . . 6.4 Report Complete . . 6.5 Report Datetran . . . . . . . 6.6 Job Average 6.7 Job History . . . . . 6.8 Report Mailbox . . . 6.9 Report Options . . . 6.10 Successors . . . . . 6.10.1 Jobchain . . . 6.10.2 Scdchain . . . 6.10.3 Cjobchan . . . 6.10.4 Cscdchan . . . 6.11 Predecessors . . . . 6.11.1 Jobrchan . . . 6.11.2 Scdrchan . . . 6.11.3 Cjobrchn . . . 6.11.4 Cscdrchn . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 7. Criteria Language . . . . . . . . . . . . . . . . . . . 7.1 Criteria Vocabulary . . . . . . . . . . . . . . . . . . . . . . . 7.1.1 Reserved Words for Use in Boolean Expressions . . . . 7.1.2 Reserved Words Used for Selection . . . . . . . . . . . . 7.1.3 Reserved Words for Use in Predecessors . . . . . . . . . 7.1.4 Combining Selection and Predecessor Criteria Vocabulary 7.1.5 Using Multiple Conditions with ANDs and ORs . . . . . 7.1.6 Effect of NOT Condition on Predecessors . . . . . . . . 7.1.7 Recommended Method for Defining Selection Criteria . 7.2 Calendar Mechanisms . . . . . . . . . . . . . . . . . . . . . . 7.2.1 Gregorian Calendar . . . . . . . . . . . . . . . . . . . . . 7.2.2 Date Tables . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.2.1 Workday Keywords . . . . . . . . . . . . . . . . . . 7.2.2.2 Accounting-Period Keywords . . . . . . . . . . . . . 7.2.2.3 Summary of Date Tables . . . . . . . . . . . . . . . 7.2.2.4 Date Translation Report . . . . . . . . . . . . . . . . 7.2.3 Calendars . . . . . . . . . . . . . . . . . . . . . . . . . . 7.2.3.1 Step 1: Define the Prototype Calendar . . . . . . . . 7.2.3.2 Step 2: Define Daily, Weekly and Monthly Calendars 7.3 Some Examples . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . 7.3.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents vii
7.3.3 Example 3 . . . . . . . . . . . . 7.3.4 Example 4 . . . . . . . . . . . . 7.3.5 Example 5 . . . . . . . . . . . . 7.3.6 Example 6 . . . . . . . . . . . . 7.3.7 Example 7 . . . . . . . . . . . . 7.3.8 Example 8 . . . . . . . . . . . . 7.3.9 Example 9 . . . . . . . . . . . . 7.3.10 Example 10 . . . . . . . . . . 7.3.11 Example 11 . . . . . . . . . . . . . . . . . . . . 7.3.12 Example 12 7.3.13 Example 13 . . . . . . . . . . 7.3.14 Example 14 . . . . . . . . . . 7.4 What Is Wrong with these Examples? 7.4.1 Example 1 . . . . . . . . . . . . 7.4.2 Example 2 . . . . . . . . . . . . 7.4.3 Example 3 . . . . . . . . . . . . 7.4.4 Example 4 . . . . . . . . . . . . 7.4.5 Example 5 . . . . . . . . . . . . 7.4.6 Example 6 . . . . . . . . . . . . 7.4.7 Example 7 . . . . . . . . . . . . 7.5 Review of Tips to Remember . . . . 7.5.1 Pitfalls . . . . . . . . . . . . . . 7.6 Notes . . . . . . . . . . . . . . . . . 7.6.1 Rules . . . . . . . . . . . . . . . 7.7 Summing Up . . . . . . . . . . . . . 7.8 Criteria Vocabulary . . . . . . . . . 7.8.1 Reserved Words . . . . . . . . . 7.9 Gregorian Calendar Conditions . . . 7.10 Workday Conditions . . . . . . . . 7.11 Accounting Conditions . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7-24 7-25 7-25 7-26 7-27 7-27 7-28 7-29 7-30 7-30 7-31 7-31 7-32 7-32 7-32 7-32 7-33 7-34 7-34 7-35 7-36 7-36 7-37 7-37 7-38 7-39 7-39 7-41 7-44 7-46 8-1 9-1 9-2 9-4 9-4 9-4 9-5 9-5 9-6 9-6 9-6 9-7 9-8 9-10 9-11 9-11 9-12
Chapter 8. Using the Autoscan Command File
Chapter 9. Tips . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1 Commonly Asked Questions 9.1.1 Startup Questions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.1.1 When Should Autoscan be Performed? . . . . . . . . . . . . . . 9.1.1.2 What Is the General Standard for Numbering Stations? . . . . . 9.1.1.3 Should I Use Date Tables or Calendars? . . . . . . . . . . . . . . 9.1.1.4 When Should I Define a New Date Table Versus a New Cycle in an Existing Date Table? . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.2 Database Maintenance Questions . . . . . . . . . . . . . . . . . . . . 9.1.2.1 How Should I Organize My Schedules? . . . . . . . . . . . . . . 9.1.2.2 When Should a Job be Staged? . . . . . . . . . . . . . . . . . . . 9.1.2.3 When Is a Job Submitted? . . . . . . . . . . . . . . . . . . . . . 9.1.2.4 What Are Global Parameters and When Are They Used? . . . . 9.1.2.5 How Can I Run a Job Like an Edit Check Repeatedly Until its Output Is Correct? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.3 Questions About Analyzing the Database . . . . . . . . . . . . . . . . 9.1.3.1 How Can I Prevent Predecessor Loops (Deadlocks)? . . . . . . . 9.1.3.2 When Should I Run Analyze Reports? . . . . . . . . . . . . . . .
viii Online Guide
9.1.3.3 What Effect Does a Deadlock Have? . . . . . . . . . . . . . . . 9.1.3.4 When Should I Run Forecasts? . . . . . . . . . . . . . . . . . . . 9.1.3.5 When Should I Run Simulation? . . . . . . . . . . . . . . . . . . 9.1.3.6 How Do I Plan When to Run a New Application? . . . . . . . . 9.1.3.7 How Do I Verify a New Application? . . . . . . . . . . . . . . . 9.1.3.8 How Can I Can Create My Own Reports? . . . . . . . . . . . . 9.1.4 Daily Processing Questions . . . . . . . . . . . . . . . . . . . . . . . 9.1.4.1 From Where Can I Issue CA-Scheduler Control Commands? . . 9.1.4.2 What Is the Difference Between FORCE, SUBMIT, RERUN, RUN, ADD, REQUEST, and SREQ? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.4.3 When Is the PRED Flag Reset? 9.1.4.4 What Happens If CA-Scheduler is Shut Down? . . . . . . . . . . 9.1.4.5 What Happens If CAIENF is Shut Down? . . . . . . . . . . . . . . . . . . . . . . . . 9.1.4.6 What Happens If a System Crash Occurs? 9.1.5 What Do I Do with Jobs in UNKNOWN Status? . . . . . . . . . . . 9.1.6 Pitfalls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.6.1 Using Control Commands on the Status Panels . . . . . . . . . . 9.1.6.2 Canceling and Purging a Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.6.3 Changing Criteria on Selected Jobs 9.1.6.4 Backlogging Jobs Over Two Autoscans in $MVS, $DYN and User Defined Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.1.6.5 Resetting Global Parameters . . . . . . . . . . . . . . . . . . . . Chapter 10. Techniques . . . . . . . . . . . . . . . . . . 10.1 Criteria Language Examples Relating to Criteria Rules 10.2 More Examples of Criteria Language . . . . . . . . . 10.2.1 Example 1 . . . . . . . . . . . . . . . . . . . . . 10.2.2 Example 2 . . . . . . . . . . . . . . . . . . . . . 10.2.3 Example 3 . . . . . . . . . . . . . . . . . . . . . 10.2.4 Example 4 . . . . . . . . . . . . . . . . . . . . . 10.2.5 Example 5 . . . . . . . . . . . . . . . . . . . . . 10.2.6 Example 6 . . . . . . . . . . . . . . . . . . . . . 10.2.7 Example 7 . . . . . . . . . . . . . . . . . . . . . 10.3 On-Request Schedules and Jobs . . . . . . . . . . . . 10.3.1 Discussion . . . . . . . . . . . . . . . . . . . . . 10.3.2 Criteria Language Subtleties . . . . . . . . . . . 10.3.2.1 Example 1 . . . . . . . . . . . . . . . . . . 10.3.2.2 Example 2 . . . . . . . . . . . . . . . . . . 10.3.2.3 Example 3 . . . . . . . . . . . . . . . . . . 10.3.2.4 Example 4 . . . . . . . . . . . . . . . . . . 10.3.2.5 Example 5 . . . . . . . . . . . . . . . . . . 10.3.2.6 Example 6 . . . . . . . . . . . . . . . . . . 10.3.2.7 Example 7 . . . . . . . . . . . . . . . . . . 10.3.2.8 Example 8 . . . . . . . . . . . . . . . . . . 10.3.2.9 Example 9 . . . . . . . . . . . . . . . . . . 10.3.2.10 Example 10 . . . . . . . . . . . . . . . . . 10.4 Backlogged Work . . . . . . . . . . . . . . . . . . . . 10.5 Restart/Recovery of Scheduled Jobs . . . . . . . . . . 10.5.1 Restart Through CA-11 . . . . . . . . . . . . . . 10.5.2 Inquiring About Jobs to be Recovered . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9-12 9-14 9-14 9-15 9-15 9-18 9-20 9-20 9-20 9-22 9-23 9-24 9-24 9-25 9-26 9-26 9-26 9-27 9-27 9-28 10-1 10-2 10-4 10-4 10-4 10-4 10-4 10-5 10-5 10-6 10-8 10-8 10-9 10-9 10-9 10-9 10-9 10-10 10-10 10-11 10-11 10-12 10-12 10-13 10-15 10-15 10-16
Contents ix
10.5.3 Automatic Recovery Options 10.5.4 Driver Considerations . . . 10.5.4.1 Step-Level Restart . . 10.5.4.2 Example 1 . . . . . . . . . . . . 10.5.4.3 Example 2 Chapter 11. Remote Scheduling 11.1 Statements . . . . . . . . . 11.1.1 Comments . . . . . . 11.1.2 Node . . . . . . . . . 11.1.3 Command . . . . . . 11.1.4 Domain . . . . . . . . 11.1.5 User . . . . . . . . . . 11.1.6 Password . . . . . . . 11.2 Examples . . . . . . . . . 11.2.1 Example 1 . . . . . . 11.2.2 Example 2 . . . . . . 11.2.3 Example 3 . . . . . . 11.2.4 Example 4 . . . . . . Glossary Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10-16 10-17 10-18 10-19 10-20 11-1 11-2 11-2 11-2 11-3 11-4 11-4 11-5 11-6 11-6 11-6 11-6 11-6 X-1 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 the margins): Online Julian dates are seven-digits. For more information, see 4.1.1, Schedule Status 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 the margins): We changed the descriptions of the Must Start, Must End, and Maximum Execution 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 on page 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 Shut Down? 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 the margins): 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 as the active workload (tracking file). Staged JCL and documentation are also stored in CA-Datacom. CA-Datacom provides many advantages over CATMAN (the previous access method) such as backup-while-open, forward recovery, and faster access. CA-Datacom also allows CA-Scheduler to exploit 31-bit storage, relieving virtual storage 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 resource dependencies for jobs. Virtual resources can be defined as required for job processing. CA-Scheduler ensures that the defined requirements are met before submitting 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, all information about that job or schedule is copied to what used to be called the tracking file. The active workload now includes everything needed to submit and track 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 of the job in the active workload. Any changes to a schedule or job in the database take effect the next time the schedule 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 during submission. Second, a WLM scheduling resource may be set ON when CA-Scheduler starts and OFF when CA-Scheduler shuts down. The WLM scheduling environment and WLM scheduling resource may be used to limit which 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 be sorted 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 a particular 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 to find the Locate string. In the CICS online, the Locate command may be used to position the scrollable displays. The leftmost column is used to find the Locate string. See the CA-Scheduler Online Guide for more information. Hold/Release Submit A new command, HOLD SUBMIT, prevents all submission without modifying the status of any schedules or jobs, as HOLD ALL does. Jobs added to the active workload after the HOLD SUBMIT command are also not submitted, unlike HOLD ALL. The HOLD SUBMIT status is saved across restarts of CA-Scheduler. When the RELEASE SUBMIT command is issued, all jobs that could not be submitted 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. See the CA-Scheduler Command Reference Guide for more information. Backwards JOBCHAIN New variations of the JOBCHAIN reports are available to display a job or schedule'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-time predecessor/successor relationship between two jobs in the active workload. The predecessor job may not be complete, and the successor job may not have started when the command is issued. See the CA-Scheduler Command Reference Guide for more information. Cross-Platform Job Definitions Jobs may be defined to the scheduling database (master file) with a cross-platform node, userid, domain, and password. If this information is also specified in the job's "JCL," the "JCL" copy overrides the database copy. See the CA-Scheduler Online Guide for more information.
1-6 Online Guide
SKIPPED Messages A message may be generated when a job or schedule is excluded from the active workload due to a nonzero SKIP value. The message may be queued for a specific CA-Scheduler user, issued on the console, or sent to the mailbox. See the CA-Scheduler Systems Programmer Guide or the CA-Scheduler Online Guide for more information. MAILBOX and Audit Trail The mailbox and audit trail information is now stored in the CA-Scheduler database instead of in CAIENF. Users no longer need to be defined to CAIENF to issue the REPORT AUDIT or REPORT MAILBOX commands. The DELETE AUDIT and DELETE MAILBOX commands should be issued daily to remove audit trail and mailbox entries more than a given number of days old. See the CA-Scheduler Command Reference Guide for more information. Command Response Messages Messages issued in response to an OS/390 modify command (that is, F CASCHD,xxx) are issued to the originating console. This allows console automation products such as CA-OPS/MVS II to "see" the response to a command. Modify command output is also captured and displayed by SDSF. Time-out conditions may prevent either console automation products or SDSF from seeing the command responses. See the CA-Scheduler Systems Programmer Guide for more information. Exits All exits are now called AMODE 31 and RMODE ANY. Some client exits may need to be reworked to tolerate AMODE 31. See the CA-Scheduler Systems Programmer Guide for more information. Better Handling of OS/390 Modify (F) Commands When an OS/390 modify command is received (F CASCHD,xxx) while an earlier modify command is being processed, CA-Scheduler automatically retains the command and issues it when the command processor is available. Any number of commands may be queued waiting for the command processor. Messages are issued 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 latest technology for online viewing, keyword searching, book marking, and printing. This set contains a hardcopy CA-Scheduler Getting Started guide and Version 9.0 of CA-Scheduler for OS/390 documentation in both IBM BookManager and Adobe Acrobat Reader format on the tape. The CA-Scheduler Getting Started guide replaces the CA-Scheduler Installation Guide. Reading Syntax Diagrams in the Command Reference Guide explains how to read the 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 jump character, "=", followed by the menu number. For example, to reach the Monitor Commands menu, enter "=1.3" from any non-scrollable field on any panel in CA-Scheduler. The CA-Scheduler dialog may be in use concurrently on the same TSO ISPF session as many times as needed. Split panel is fully supported. Note: The CICS interface does not support split panel or the jump character (=). The END command (normally PF3/15) returns you to the panel where the function started, which is not necessarily the last menu you saw. Certain scrollable panels in ISPF will show the total number of rows being displayed. The total number 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 (the COMMAND or OPTION field). Enter "SCHD" followed by the command, like this:
------------------------- CA-SCHEDULER 9. OPTION ===> schd run j n=xxx 1 2 3 X OPTIONS MONITOR DATABASE REPORTS EXIT -
xxyy (SCHD) ------------------------
Specify user preferences Control and monitor the current workload Define and maintain workload definition Execute and view reports Exit CA-Scheduler ------------------------------------------CA-Scheduler copyright 1989, 2 1 Computer Associates International, Inc. -------------------------------------------
You can enter both database commands (DEFINE, SYNCHK, ANALYZE) and tracking commands (RUN, CANCEL, FORCE). Tracking commands do not require an "SC" before the command, but the "SC" is supported if entered. (Tracking commands run 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 simulation commands (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 by any 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. COMMAND ===> sort date Schedule -------ABEND ABEND1 ABEND2 AIX BADJOB BADPRED BATCH 1 BATCH 2 BATCH 3 CDAY CLEANUP CMD DATETAB DAYOWK DLOCK DLUGG DRIVERS DUPS1 DUPS2 Sys ---AutoSel ------NO NO NO NO NO NO NO NO NO NO YES NO NO YES NO NO NO YES YES Jobs ---1 1 1 1 1 99 99 99 1 1 98 1 7 3 1 1 1 1
xxyy (SCHD) SCHEDULES Date ---------1999/ 9/23 2 / 6/22 2 / 6/22 2 / 3/15 1999/ 9/21 2 / 7/3 2 1/ 1/11 2 1/ 1/11 2 1/ 1/11 2 / 8/18 2 1/ 1/12 2 1/ 1/18 2 / 6/23 1999/ 9/ 4 2 / 7/29 2 / 2/19 2 / 5/ 6 1999/1 /2 1999/1 /2 Time -------15:46:45 15:2 : 8 15:2 :2 11:5 : 8 11:15:15 13:45:59 13:47:58 13:48:19 13:48:36 13:25:54 9: 7:41 15: 8:13 2 :51:39 9:44: 1 12:41:22 12: 9: 5 8:56:28 12:28:39 12:28:42
Row 1 to 19 of 5 SCROLL ===> CSR Userid -------USER 3 USER 3 USER 3 USER 3 USER 3 USER 3 GUEST 2 GUEST 2 GUEST 2 USER 3 USER 3 GUEST 2 USER 3 USER 3 USER 3 USER 3 USER 3 USER 3 USER 3
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
1.7 Sort
After the sort command is issued, the following would be displayed:
-------------------- CA-SCHEDULER 9. COMMAND ===> Schedule -------QADEMO2A QADEMO3 QADEMO4 QADEMO5 QADEMO6 QADEMO1 QADEMO2 QADEMO SAMPSCHD Q1427SC1 Q1425S61 Q1425S62 Q1425S63 Q1425S64 Q1425S65 Q1425S66 Q1425S67 Q1425S68 Q1425S69 Sys ---AutoSel ------NO YES YES YES YES YES YES YES NO YES NO NO NO NO NO NO NO NO NO Jobs ---1 1 12 4 1 4 8 18 5
xxyy (SCHD) SCHEDULES Row 1 to 19 of 14 SCROLL ===> CSR Date ---------2 1/ 2/1 2 1/ 2/1 2 1/ 2/1 2 1/ 2/1 2 1/ 2/1 2 1/ 2/1 2 1/ 2/1 2 1/ 2/1 2 1/ 2/1 2 1/ 2/ 3 2 1/ 2/ 3 2 1/ 2/ 3 2 1/ 2/ 3 2 1/ 2/ 3 2 1/ 2/ 3 2 1/ 2/ 3 2 1/ 2/ 3 2 1/ 2/ 3 2 1/ 2/ 3 Time -------15:47:35 15:47:35 15:47:35 15:47:35 15:47:35 15:47:3 15:47:3 15:47:24 8:39:51 9: 2:44 8:55:32 8:55:32 8:55:32 8:55:32 8:55:32 8:55:32 8:55:32 8:55:32 8:55:32 Userid -------GUEST 3 GUEST 3 GUEST 3 GUEST 3 GUEST 3 GUEST 3 GUEST 3 GUEST 3 USER 3 GUEST 3 GUEST 3 GUEST 3 GUEST 3 GUEST 3 GUEST 3 GUEST 3 GUEST 3 GUEST 3 GUEST 3
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
All rows must be read before the display can be sorted. This may cause a delay before the 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 Locate command to position the display to a particular row. To reposition the display to where a given value would be, issue "L xxx" where xxx is the value to find. The column searched is the one most recently sorted with the SORT command. If the SORT command has not been entered, the leftmost column is searched. For example:
-------------------- CA-SCHEDULER 9. COMMAND ===> L DUPS Schedule -------ABEND ABEND1 ABEND2 AIX BADJOB BADPRED BATCH 1 BATCH 2 BATCH 3 CDAY CLEANUP CMD DATETAB DAYOWK DLOCK DLUGG DRIVERS DUPS1 DUPS2 Sys ---AutoSel ------NO NO NO NO NO NO NO NO NO NO YES NO NO YES NO NO NO YES YES Jobs ---1 1 1 1 1 99 99 99 1 1 98 1 7 3 1 1 1 1
xxyy (SCHD) SCHEDULES Date ---------1999/ 9/23 2 / 6/22 2 / 6/22 2 / 3/15 1999/ 9/21 2 / 7/3 2 1/ 1/11 2 1/ 1/11 2 1/ 1/11 2 / 8/18 2 1/ 1/12 2 1/ 1/18 2 / 6/23 1999/ 9/ 4 2 / 7/29 2 / 2/19 2 / 5/ 6 1999/1 /2 1999/1 /2 Time -------15:46:45 15:2 : 8 15:2 :2 11:5 : 8 11:15:15 13:45:59 13:47:58 13:48:19 13:48:36 13:25:54 9: 7:41 15: 8:13 2 :51:39 9:44: 1 12:41:22 12: 9: 5 8:56:28 12:28:39 12:28:42
Row 1 to 19 of 5 SCROLL ===> CSR
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Userid -------USER 3 USER 3 USER 3 USER 3 USER 3 USER 3 GUEST 2 GUEST 2 GUEST 2 USER 3 USER 3 GUEST 2 USER 3 USER 3 USER 3 USER 3 USER 3 USER 3 USER 3
1.8 Locate
After the Locate command, the display would show:
-------------------- CA-SCHEDULER 9. COMMAND ===> Schedule -------DRIVERS DUPS1 DUPS2 DUPS3 DUPS4 DUPS5 FLOW 1 GSBACK GSCR GSCRI JCKTEST JOBFLOW NONCPU NONCPU2 PAIX PAULNT PHINK PYRAMID QADEMO Sys ---AutoSel ------NO YES YES YES YES YES NO NO YES YES NO NO NO NO NO NO NO YES YES Jobs ---1 1 1 1 1 1 2 2 1 3 1 5 3 1 1 1 1 26 18
xxyy (SCHD) SCHEDULE Row 17 to 35 of 14 SCROLL ===> CSR Date ---------2 / 5/ 6 1999/1 /2 1999/1 /2 1999/1 /2 1999/1 /2 1999/1 /2 2 / 6/16 2 1/ 1/31 2 1/ 1/11 2 1/ 1/26 1999/12/18 1999/1 /14 2 / 8/1 2 / 8/1 2 / 3/15 1999/ 8/ 3 2 / 2/25 2 /1 /29 2 1/ 2/1 Time -------8:56:28 12:28:39 12:28:42 12:28:5 12:29: 12:29: 3 9:3 :48 9:52:12 14:5 :4 13:38:2 12:13:48 9:26:39 1 :38:33 1 :41:24 12:27:12 8:48:28 15:48: 2 14:27:21 15:47:24 Userid -------USER 3 USER 3 USER 3 USER 3 USER 3 USER 3 USER 3 GUEST 1 GUEST 1 GUEST 2 USER 3 USER 3 USER 3 USER 3 USER 3 USER 3 USER 3 USER 3 GUEST 3
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
XE87
Note: Because CICS does not support the SORT command, the Locate command always 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 the PF keys are set to the default values, as follows: Key PF1/13 PF2/14 PF3/15 PF4/16 PF5/17 PF6/18 PF7/19 PF8/20 PF9/21 PF10/22 PF11/23 PF12/24 Value Help Split End Return Rfind Rchange Up Down Swap Left Right Retrieve
CA-Scheduler runs in a new application pool (SCHD). All PF keys are set to the default values when users first access it. If a user changes a PF key, it is up to the user to issue the correct command to CA-Scheduler. For example, PF5 is documented as refreshing a list of schedules or jobs in the status display. Since PF5 is normally set to Rfind, CA-Scheduler is really using the Rfind command. If PF5 is set to some other command, then pressing PF5 will not refresh the list of jobs or schedules.
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 manual assumes that the PF keys are set to the default values, as follows: Key PF1/13 PF3/15 PF5/17 PF6/18 PF7/19 PF8/20 PF10/22 PF11/23 Value DISPLAY LONG MESSAGE LINE AFTER ERROR END REPEAT "FIND" COMMAND (EDITOR ONLY) REPEAT "CHANGE" COMMAND (EDITOR ONLY) UP DOWN LEFT RIGHT
All PF keys are set to the default values when each user first accesses CA-Scheduler on CICS. If a user changes a PF key, it is up to the user to issue the correct command to CA-Scheduler. For example, PF8 is documented as the DOWN command. If PF8 is set to any other command, then pressing PF8 will not page down.
1-16 Online Guide
1.11 Tutorial
1.11 Tutorial
You can obtain information about any ISPF panel and the fields on the panel by pressing 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 not supported. 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 the ISPF 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, and documentation. Since the ISPF editor is not available under CICS, a native CA-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: Abbreviation: BOTTOM BOT
CHANGE Replace one string with another. You may optionally specify the column where the strings begin. Syntax: Abbreviations: CHANGE <oldstring> <newstring> column CH, C
See also RCHANGE. COLUMN Display a column scale line. Syntax: Abbreviation: COLUMN COLS
DELETE (criteria only) Delete the criteria currently displayed from the CA-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: FIND DPROMPT
Locate a character string in the member and position the display to it. You may optionally specify a column to search. Syntax: Abbreviations: See also RFIND. FIND <string> column FI, F
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 to the 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 left of 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: COPY B
Copy one or more lines to another location in the member. You indicate where 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 lines of 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 lines of the block.)
INSERT
Add one or more blank lines to the member. The lines are added after the line 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 indicate where 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 lines of the block.)
REPEAT Duplicate a line one or more times. The new copies of the line appear immediately following the original. Syntax: R nn (where nn is 1 to 18 new copies. The default is 1.)
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. 3 THIS IS LINE 3. 4 THIS IS LINE 4. 5 THIS IS LINE 5. -> I3 6 THIS IS LINE 6. 7 THIS IS LINE 7. 8 THIS IS LINE 8. 9 THIS IS LINE 9. 1 THIS IS LINE 1 . ------------------------------------------------------------------------
The result will be:
-----------------------------------------------------------------------1...+....1....+....2....+....3....+....4....+....5....+....6.. 1 WDAY 2 THIS IS LINE 2. 3 THIS IS LINE 3. 4 THIS IS LINE 4. 5 THIS IS LINE 5. 6 THIS IS LINE 6. -> 7 -> 8 -> 9 1 THIS IS LINE 7. 11 THIS IS LINE 8. 12 THIS IS LINE 9. 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 2 THIS IS LINE 2. ->>CC 3 THIS IS LINE 3. 4 THIS IS LINE 4. 5 THIS IS LINE 5. -> A 6 THIS IS LINE 6. 7 THIS IS LINE 7. 8 THIS IS LINE 8. 9 THIS IS LINE 9. 1 THIS IS LINE 1 . ------------------------------------------------------------------------
The result will be:
-----------------------------------------------------------------------1...+....1....+....2....+....3....+....4....+....5....+....6.. 1 WDAY 2 THIS IS LINE 2. 3 THIS IS LINE 3. 4 THIS IS LINE 4. 5 THIS IS LINE 5. 6 THIS IS LINE 6. -> 7 WDAY -> 8 THIS IS LINE 2. -> 9 THIS IS LINE 3. 1 THIS IS LINE 7. 11 THIS IS LINE 8. 12 THIS IS LINE 9. 13 THIS IS LINE 1 . ------------------------------------------------------------------------
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 2 THIS IS LINE 2. ->>MM 3 THIS IS LINE 3. 4 THIS IS LINE 4. 5 THIS IS LINE 5. -> B 6 THIS IS LINE 6. 7 THIS IS LINE 7. 8 THIS IS LINE 8. 9 THIS IS LINE 9. 1 THIS IS LINE 1 . ------------------------------------------------------------------------
The result will be:
-----------------------------------------------------------------------1...+....1....+....2....+....3....+....4....+....5....+....6.. 1 THIS IS LINE 4. 2 THIS IS LINE 5. -> 3 WDAY -> 4 THIS IS LINE 2. -> 5 THIS IS LINE 3. 6 THIS IS LINE 6. 7 THIS IS LINE 7. 8 THIS IS LINE 8. 9 THIS IS LINE 9. 1 THIS IS LINE 1 . ------------------------------------------------------------------------
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 2 THIS IS LINE 2. 3 THIS IS LINE 3. ->>DD 4 THIS IS LINE 4. 5 THIS IS LINE 5. 6 THIS IS LINE 6. 7 THIS IS LINE 7. 8 THIS IS LINE 8. ->>DD 9 THIS IS LINE 9. 1 THIS IS LINE 1 . ------------------------------------------------------------------------
The result will be:
-----------------------------------------------------------------------1...+....1....+....2....+....3....+....4....+....5....+....6.. 1 WDAY 2 THIS IS LINE 2. 3 THIS IS LINE 3. 1 THIS IS LINE 1 . ------------------------------------------------------------------------
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 2 THIS IS LINE 2. 3 THIS IS LINE 3. ->>R4 4 THIS IS LINE 4. 5 THIS IS LINE 5. 6 THIS IS LINE 6. 7 THIS IS LINE 7. 8 THIS IS LINE 8. 9 THIS IS LINE 9. 1 THIS IS LINE 1 . ------------------------------------------------------------------------
The result will be:
-----------------------------------------------------------------------1...+....1....+....2....+....3....+....4....+....5....+....6.. 1 WDAY 2 THIS IS LINE 2. 3 THIS IS LINE 3. ->> 4 THIS IS LINE 4. ->> 5 THIS IS LINE 4. ->> 6 THIS IS LINE 4. ->> 7 THIS IS LINE 4. ->> 8 THIS IS LINE 4. 9 THIS IS LINE 5. 1 THIS IS LINE 6. 11 THIS IS LINE 7. 12 THIS IS LINE 8. 13 THIS IS LINE 9. 14 THIS IS LINE 1 . ------------------------------------------------------------------------
Chapter 2. Starting CA-Scheduler Online

CA-Scheduler is an ISPF application. Contact the person at your site who installed CA-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 the following panel:
---------------------- CA-SCHEDULER 9. COMMAND ===> Signon information: Userid . . . . . . Read Password . . . Write Password . .
xxyy (SCHD) SIGNON --------------------
------------------------------------------CA-Scheduler copyright 1989, 2 1 Computer Associates International, Inc. -------------------------------------------
Enter the user ID, read, and write passwords provided by your site's CA-Scheduler Administrator.
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. OPTION ===> 1 2 3 X OPTIONS MONITOR DATABASE REPORTS EXIT -
xxyy (SCHD) ------------------------
Specify user preferences Control and monitor the current workload Define and maintain workload definition Execute and view reports Exit CA-Scheduler ------------------------------------------CA-Scheduler copyright 1989, 2 3 Computer Associates International, Inc. -------------------------------------------
Use option 0, OPTIONS, to tailor the CA-Scheduler online environment to your preferences. 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. COMMAND ===> Options: Delete Confirmation . . . . . Default Analyze List Type . . Command Output from Status . . Command Prompt from Status . . Default Start/Complete Station Temporary file secondary size Default JOBCHAIN Levels . . . Default JOBCHAIN Repeat . . . . . . . . . . . . . . . . . . .
xxyy (SCHD) OPTIONS --------------------
YES ERR ALL YES 4 1 YES
(Yes, No) (Yes, No, Err, Deadlock) (All, Error) (Yes, No) ( 1 to 99) (1 to 1 ) (blank, 1 to 999) (Yes, No)
Enter END to exit.
The fields are: Delete Confirmation If YES, a confirmation panel is displayed when an object is being deleted from the database. If NO, the object is deleted without any confirmation. Size/Type: Required: Default: YES or NO Yes Yes
Default Analyze List Type When displaying an Analyze panel, this value will be filled in for the List field. Valid values are: YES All information about analyzed schedules and jobs is displayed. NO Only schedule and job names are displayed.
Chapter 3. Options 3-1
ERR Only error messages are displayed. DEADLOCK Only deadlocks and the deadlock path is displayed. Required: Default: Yes ERR
Command Output from Status Determines if the output from commands entered as line commands in the status lists is displayed or not. Command output that includes a warning or error message is always displayed. All The command output always displays. Error The command output only displays when it contains a warning or error message. Required: Default: Yes All
Command Prompt from Status Determines if the command prompt panels are displayed for commands entered as line commands in the status lists. Yes Display the prompt panels allowing default options to be changed. No Issue the command with all default values. Required: Default: Yes Yes
Default Start/Complete Station The Start and Complete commands are normally used for jobs at stations other than 40. The value here will be filled in the Station field on the Start and Complete command prompts. Size/Type: Required: Default: 1 to 2 numeric characters Yes 40
Temporary file secondary size (ISPF only) CA-Scheduler allocates a temporary file to hold command output. The file is allocated with one track and a secondary allocation size of the number you specify here. Normal OS/390 operations allow fifteen secondary extents of the size you specify before a data set is considered full. If you get a message that the file is full when viewing command output, consider increasing this value. Size/Type: Required: Default: 1 to 3 digits in the range 1 to 100 Yes 1
3-2 Online Guide
Default JOBCHAIN Levels The value entered here will be automatically filled in whenever a JOBCHAIN command prompt panel is displayed. These panels are at options 3.11 and 3.12. If the value is blank, then all levels are displayed. Size/Type: Required: Default: Blank or 1 to 3 digits No blank
Default JOBCHAIN Repeat The value entered here will be automatically filled in whenever a JOBCHAIN command prompt panel is displayed. These panels are at options 3.11 and 3.12. Size/Type: Required: Default: YES/NO Yes YES
Do you want to change PFkeys (CICS only) Specify YES and press Enter to change the PF key definitions for your CA-Scheduler CICS session. The following panel is displayed:
CAJI 2 --------COMMAND ===>
CA-SCHEDULER
9.
xxyy
(SCHD)
PFKEYS ------------------
To change please overtype PFKEY value. PFK PFK PFK PFK PFK PFK 1/13 2/14 3/15 4/16 5/17 6/18 : : : : : : HELP SPLIT END RETURN RFIND RCHANGE PFK 7/19 PFK 8/2 PFK 9/21 PFK1 /22 PFK11/23 PFK12/24 : : : : : : UP DOWN SWAP LEFT RIGHT RETRIEVE
Pfkey function ( SPLIT, SWAP, Enter END to exit.
RETRIEVE ) not supported
Chapter 3. Options 3-3
Chapter 4. Monitor
Option 1 of the CA-Scheduler main menu displays the monitor menu.
--------------------- CA-SCHEDULER 9. OPTION ===> 1 2 3 4 5 STATUS STATJOB COMMAND FREECMD CA-11 -
xxyy (SCHD) MONITOR --------------------
Interact with current workload starting with Schedules Interact with current workload starting with Jobs Build a command for CA-Scheduler Freeform command for CA-Scheduler CA-11 dialogs
Enter END to exit.
Use option 1, STATUS, to view the condition of the current workload from a schedule perspective. 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 job perspective. Jobs from more than one schedule may be viewed at the same time. See 4.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 ten commands issued are retained and may be recalled. See 4.4, FREECMD on page 4-187 for more information. Use option 5, CA-11, to display the CA-11 main menu. This option is only available if you have CA-11 installed and the CA-11 ISPF data sets are currently allocated to your ISPF 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 selection panel. The CA-Scheduler started task does not need to be active.
----------------- CA-SCHEDULER 9. COMMAND ===> Include: Schedule . . .
xxyy (SCHD) SCHEDULE STATUS ----------------
Select Status: / All (if selected, options below are ignored) Not Held Held Schedule Not Started Started Display Late Only Not Requested (Inactive) Cancelled Wait Start Time Completed Wait Predecessors
Display ALL jobs in the schedule, or FILTER . . . ALL Enter END to exit.
The fields are: Schedule A full or partial schedule name to limit the schedules displayed, or blanks to show all schedules. Size/Type: Required: 1 to 8 alphanumeric characters No
Select Status Select one or more of the status categories that you want displayed. Select a category by typing any non-blank character to the left of the category title. Selecting the category All causes any other selections to be ignored. The categories 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 schedules by typing a J next to the schedule name. You may either have all of the jobs in the schedule displayed, regardless of the job's status, or only display jobs with selected statuses. To display all of the jobs, enter ALL. To display a panel requesting 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. COMMAND ===>
xxyy (SCHD) STATUS -
ROW 1 TO 11 OF 11 SCROLL ===> CSR
Enter CA-Scheduler command below, or enter a line command: ===> Command -------________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ Schedule -------DAYOWK ETEST FLOW1 PYRAMID PYRLONG PYRLONG2 QADEMO QADEMO1 STEVE S 1 Y2 T1 Node -------Status -------------------------------------Started Waiting Start Time yy 321 : 5 Waiting Start Time yy 32 9: Started Waiting Start Time yy 32 1 : Waiting for Predecessor(s) Started Waiting for Predecessor(s) Started Started Started BOTTOM OF DATA Backlog ------NO NO NO YES NO NO NO NO NO NO NO
Each schedule is displayed on a single row, along with its current status description and backlog condition. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. CA-Scheduler only reads the first 50 schedules before displaying the list. As you scroll down, more rows are automatically added until the entire list has been built. Press PF5 to refresh the status of the currently displayed schedules, even if the schedules' status no longer matches the status categories requested. Press PF6 to list all of 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 more schedules: Command CAncel CP Force Hold J Use Issue a CANCEL SCHEDULE command. See 4.3.3.2, Cancel Schedule Command on page 4-68. Issue a CP SCHEDULE command. See 4.3.5.2, Cancel Post Schedule Command on page 4-77. Issue a FORCE SCHEDULE command. See 4.3.8.2, Force Schedule Command on page 4-93. Issue a HOLD SCHEDULE command. See 4.3.10.2, Hold Schedule Command on page 4-99. Display a list of jobs in this schedule. See 4.2, Job Status on page 4-16.
4.1 Schedule Status
Command P POst PUrge RELease REQuest RUn S SReq Unpost =
Use Display the schedule's predecessors, and the predecessor's status. See 4.2.2, Predecessor Display on page 4-38. Issue a POST SCD command. See 4.3.12.2, Post Schedule Command on page 4-109. Issue a PURGE SCHEDULE command. See 4.3.13.2, Purge Schedule on page 4-127. Issue a RELEASE SCHEDULE command. See 4.3.14.2, Release Schedule Command on page 4-132. Issue a REQUEST SCHEDULE command. See 4.3.15.2, Request Schedule Command on page 4-140. Issue a RUN SCHEDULE command. See 4.3.18.2, Run Schedule Command on page 4-151. Display detail information about the schedule. Issue an SREQ SCHEDULE command. See 4.3.19.2, SREQ Schedule Command on page 4-156. Issue an UNPOST SCD command. See 4.3.22.2, Unpost Schedule Command on page 4-168. Repeat the previous command.
If a schedule is selected (command of S), CA-Scheduler displays the following panel:
------------- CA-SCHEDULER 9. OPTION ===> Schedule . . . Status . . . . 1 2
xxyy (SCHD) SCHEDULE STATUS DETAIL -------------
From Node . . .
DETAILS - Detail Information on the Schedule PREDECESSORS - Information on this Schedule's Predecessors
Enter END to exit.
Use option 1, DETAILS, to display and alter information about the schedule in the current workload. See the next topic for more information.
4-4 Online Guide
4.1 Schedule Status
Use option 2, PREDECESSORS, to display a list of the schedule's predecessors. See 4.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 in the workload. Some of the fields may be modified. A command is built and sent to the CA-Scheduler started task for any modifications. The fields are contained on several panels. Use PF7 and PF8 to scroll up and down through the panels. To save any changes and exit, use PF3. To exit without saving any changes, enter CAN on the command line. The output of the command is displayed. If an error is detected, the Scheduler Status Detail panels are redisplayed, allowing you to correct the problem. The batch utility to use is CAJUCMD0. The batch command is TALTER SCHEDULE.
------------- CA-SCHEDULER 9. COMMAND ===> Schedule . . . Current Status: Status . . . . . . . Job Count . . . . . Selection Code . . . Backlog Eligible . . Currently Backlogged Waiting on Global . Predecessor Priority . . . . . . .
From Node . . . . . . . . . Track Must Start Time . Track Must End Time . . Track Maximum Time . .
Late: Late due to Must Start Time . Late due to Must End Time . . Late due to 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 of the following jump commands: TOP STATUS LATE
4.1 Schedule Status
The fields are: Schedule The name of the schedule being displayed or altered. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name From Node The owning JES NJE node of this schedule. This field is blank if the CA-Scheduler installation option NJE is set to NO. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Local node name Status The current status of the schedule. Display only with no batch equivalent. Job Count The number of jobs, including Not Requested jobs, that are in the current workload. Display only with no batch equivalent. Selection Code The reason why this schedule is part of the current workload. If RC is 01 - 79 This number Corresponds to the position of the reason on the criteria statement that was defined for this job or schedule. A job will inherit the reason code from a schedule if no criteria record exists for the job. Indicates that it was selected because today's date corresponds to a workday on the calendar that was defined for this job or schedule. Indicates that it is selected by default every day because no selection criteria were defined or the criteria record is blank (NULL). Indicates that it was added to today's workload by the online RUN command. Identifies a schedule that is being run because a job abended. (This schedule was defined on the ABEND option as an alternate schedule in case of abend.) Indicates that the job originates from another node (NJE). Indicates a nonscheduled OS/390 job. Indicates that it was added to today's workload by the online ADD command.
80 84 88 92
93 94 95
4-6 Online Guide
4.1 Schedule Status
96
Indicates that this job was a backout job that was submitted for an abended job that specified ABEND=BACKOUT.
Backlog Eligible Indicates if the schedule, and all of its jobs, should be backlogged if the schedule has not completed at the next autoscan. Size/Type: YES or NO Required: No Batch Keyword: Backlog Currently Backlogged Indicates if the schedule is backlogged now. A Yes value indicates that a new copy of the schedule and its jobs are brought into the current workload as soon as this copy finishes. Display only with no batch equivalent. Waiting on Global Indicates if the schedule has an unsatisfied global variable in its criteria. Display only with no batch equivalent. Predecessor Priority A number used in ordering schedules on an internal chain of control blocks. This value is only of use to Computer Associates Technical Support. Display only with no batch equivalent. Late due to Must Start Time If YES, the schedule did not start by its Must Start Time. Display only with no batch equivalent. Track Must Start Time If YES, the schedule has a Must Start Time. Display only with no batch equivalent. Late due to Must End Time If YES, the schedule did not end by its Must End Start Time. Display only with no batch equivalent. Track Must End Time If YES, the schedule has a Must End Time. Display only with no batch equivalent. Late due to Maximum Time If YES, the schedule has been started longer than its Maximum Time. Display only with no batch equivalent. Track Maximum Time If YES, the schedule has a Maximum Time. Display only with no batch equivalent.
4.1 Schedule Status
Press PF8 for the next panel.
------------- CA-SCHEDULER 9. COMMAND ===> Schedule . . . 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 . . . . . . . . . . . . . . . . . . .
From Node . . . . . . . . . . . .
You may jump to this panel from other Scheduler Status Detail panels by using the following 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 value of the Scheduled Time date. Size/Type: (Online) 7 numeric Julian date and 4 digit time (Batch) 6 numeric in the form ddhhmm Required: No Batch Keyword: Erlytime Must Start Time The 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 date must be at least the value of the Scheduled Time date. Size/Type: (Online) 7 numeric Julian date and 4 digit time (Batch) 6 numeric in the form ddhhmm Required: No Batch Keyword: Musttime
4-8 Online Guide
4.1 Schedule Status
Must End Time The 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 date must be at least the value of the Scheduled Time date. Size/Type: (Online) 7 numeric Julian date and 4 digit time (Batch) 6 numeric in the form ddhhmm Required: No Batch Keyword: Deadline Maximum Execution The length of time that the schedule may execute before being marked late. The value is in the form ddhhmm, where dd is the number of autoscans and hhmm is the time. Display only with no batch equivalent. User-specified Average The length of time entered on the schedule in the database as an average execution time. The value is in the form ddhhmm, where dd is the number of autoscans and hhmm is the time. Display only with no batch equivalent. Historical Average The average amount of time for this schedule to execute, based on the last seven executions of the schedule. Display only with no batch equivalent. Scheduled Time The date and time the schedule was added to the workload. Display only with no batch equivalent. Available Time The date and time the schedule was first available to start. Display only with no batch equivalent. Start Time The date and time of the most recent start of the schedule. Display only with no batch equivalent. End Time The date and time of the most recent end of the schedule. Display only with no batch equivalent. Press PF8 for the next panel.
4.1 Schedule Status
------------- CA-SCHEDULER 9. COMMAND ===> Schedule . . . Scheduled At: Node . . . Executing At: Node . . . Selection: Date Table . . . Calendar . . . . Auto Select . . Other: Continue on bad jobs Date on RUN Command Use Simulate Times User Data . . . . . . . . . . . . . . . . . . . . .
From Node . . Sysid . . . Sysid . . .
. . . .
You may jump to this panel from other Schedule Status Detail panels by using one of the following jump commands: SCHD EXEC SELECT OTHER The fields are: Scheduled At Node The JES NJE node name where the schedule is controlled or blanks if the CA-Scheduler installation option NJE is set to NO. Scheduled At Sysid The system ID of the controlling CA-Scheduler. Executing At Node The JES NJE node name where the schedule is executing or blanks if the CA-Scheduler installation option NJE is set to NO. Executing At Sysid The system ID of the CA-Scheduler where the schedule is executing. Date Table The name of the date table used in bringing the schedule and its jobs into the current workload. Calendar The name of the calendar, if any, specified on the schedule's criteria. Auto Select If YES, the schedule is eligible for autoscan to add it to the workload.
4-10 Online Guide
4.1 Schedule Status
Continue on bad jobs If YES, the schedule's successors are posted if one of the following is true for every 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 Command If the RUN command with the DATE parameter was used to add the schedule to the workload, then the DATE value is displayed here. If not, then zeros are displayed. Use Simulate Times If YES, the Early Start Time, Must Start, and Must End Times may have been generated by the SIMULATE command. User Data Any user specific data associated with this schedule. The data may be supplied by a user exit (see the Notification Exit in the Systems Programmer Guide) or on the TALTER SCHEDULE command. Size/Type 1 to 16 alphanumeric characters Required: No Batch Keyword: USERData Press PF8 for the next panel.
------------- CA-SCHEDULER 9. COMMAND ===> Schedule . . . Job Defaults: Library Type Stage JCL . Insert CA-11 JCL DDName . Userids: User who User who User who User who User who . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
From Node . . Insert Sched Enviro . . . Scheduling Environment. .
Issued RUN Held . . . Released . Cancelled Forced . .
Security: Userids . . . . . .
. . . .
. . . .
4.1 Schedule Status
You may jump to this panel from other Schedule Status Detail panels by using one of the following jump commands: JOB USERIDS SECURITY The fields are: Library Type The default access method for jobs in this schedule. A change in this value only applies to jobs added to the workload, not to jobs already in the workload. Valid values are: DRIVER CA-Scheduler generates one line of JCL to be expanded by Driver.
JOBDOC CA-Jobdoc LIBRN PANV PDS RDRQ CA-Librarian CA-Panvalet Partitioned data set Jobs are manually submitted outside of CA-Scheduler with a TYPRUN=HOLD on the job statement. CA-Scheduler releases the job and tracks it as if the job was submitted by CA-Scheduler. See "Performance Considerations" in the Systems Programmer Guide for performance implications.
USERLIB The access method is provided by a site-written exit program. See "User Exits and APIs" in the Systems Programmer Guide for more information. TESTLIB CA-Scheduler submits a dummy job (based on the skeleton in member CAJUTSTB of the PDS allocated to ddname JCLMASTR). The dummy job may execute for a specified number of seconds, end with a specific return code, or abend, based on parameters defined at the job level. See the field Test Parm in 5.2.2.1, Job Definition on page 5-29. ROSCOE CA-Roscoe Required: No Batch Keyword: Libtype Insert Sched Enviro Determines if a Workload Manager (WLM) scheduling environment should be inserted into this schedule's jobs or not. See also Scheduling Environment. Changing this value only affects jobs that are added to the 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: YES or NO Required: No Batch Keyword: INSRSenv
4-12 Online Guide
4.1 Schedule Status
Stage JCL The default staging option for jobs in this schedule. Insert CA-11 The default CA-11 option for jobs in this schedule. A change in this value only applies to jobs added to the workload, not to jobs already in the workload. Size/Type: YES or NO Required: No Batch Keyword: INSrrms Scheduling Environment The name of the Workload Manager (WLM) scheduling environment that should be inserted into this schedule's jobs. This field must not be blank, and Insert Sched Enviro must be set to YES before a scheduling environment (SCHENV) is inserted into the job's JCL. Changing this value only affects jobs that are added to the 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 characters Required: No Batch Keyword: SCHENV JCL DDName The default ddname for jobs with a library type of PDS. A change in this value only applies to jobs added to the workload, not to jobs already in the workload. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: DDname User who Issued RUN The user ID responsible for adding the schedule to the workload. A value of AUTOINIT means the schedule was added by autoscan. Display only with no batch equivalent. User who Held The last user who held the schedule. Blanks mean the schedule has never been held. Display only with no batch equivalent. User who Released The last user who released the schedule. Blanks mean the schedule has never been released. Display only with no batch equivalent. User who Cancelled The user who removed the schedule from the workload. Blanks mean the schedule has not been canceled. Display only with no batch equivalent.
4.1 Schedule Status
User who Forced The last user who issued the FORCE SCHEDULE command on this schedule. Display only with no batch equivalent. Userids A list of users allowed to manipulate this schedule and its jobs using CA-Scheduler internal security. Display only with no batch equivalent. Press PF8 for the next panel.
-------------- CA-SCHEDULER 9. COMMAND ===> Schedule . . . Userid to Notify All Events . . Schedule Start Schedule End . Schedule Late for: . . . . . . . . . . . .
From Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enter END to Exit, or UP for Previous Screen.
You may jump to this panel from other Schedule Status Detail panels by using one of the following jump commands: SMR BOTTOM The fields are: All Events A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the schedule starts, becomes late, and ends. See below for more information. Display only with no batch equivalent. Schedule Start A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the schedule starts. See below for more information. Display only with no batch equivalent.
4-14 Online Guide
4.1 Schedule Status
Schedule End A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the schedule ends. See below for more information. Display only with no batch equivalent. Schedule Late A list of zero to four user IDs or OPERxxyy values to which messages will be sent if the schedule is marked late. See below for more information. Display only with no batch equivalent. Messages to users are not TSO SEND messages. They are stored in the CA-Scheduler active workload and must be retrieved manually by the user. Messages are not kept indefinitely--see the CAIJGEN option MSGHOLD for more information. Messages are stored in the CA-Scheduler database when the value is MAILBOX, and may 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 of appropriate route codes and descriptor codes for your site. The CAIJGEN options STRMSG, ENDMSG, and LATMSG specify locations to which all 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 the CA-Scheduler Monitor menu or by selecting a schedule with a J from the schedule status function. The following panel displays only if started from the CA-Scheduler Monitor menu.
------------------- CA-SCHEDULER 9. COMMAND ===> Include: Job . . . . .
xxyy (SCHD) JOB STATUS -------------------
Select Status: / All (if selected, options below are ignored) Not Held Held Schedule Not Started Wait Start Time Wait Predecessors Wait Resources Unknown Display Late Only Enter END to exit. Not Requested (Inactive) Cancelled Submit in Progress Submitted Submit Failed Rec'd at Remote Node Started Display Staged Only Failed (rc & JCL err) Abended Interrupted Completed Purged
The fields are: Job A full or partial job name to limit the jobs displayed, or blanks to show all jobs. Size/Type: Required: 1 to 8 alphanumeric characters No
Select Status Select one or more of the status categories that you want displayed. Select a category by typing any non-blank character to the left of the category title. Selecting the category All causes any other selections to be ignored. The categories you select are saved across CA-Scheduler sessions. Press Enter to display the job status panel.
4-16 Online Guide
4.2 Job Status
xxyy (SCHD) STATUS -- Row 1 to 16 of 5 SCROLL ===> CSR
Enter CA-Scheduler command below, or enter a line command: ===> Command -------________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ ________ Job JNO St Node Schedule -------- --- -- -------- -------BACKOUT 1 4 USI287ME BACKOUT BACKOUTX 1 4 USI287ME BACKOUT ETEST 1 4 USI287ME ETEST FL1 1 4 USI287ME FLOW1 FL2 1 4 USI287ME FLOW1 FL3 1 4 USI287ME FLOW1 FL4 1 4 USI287ME FLOW1 FL5 1 4 USI287ME FLOW1 FL6 1 4 USI287ME FLOW1 JOBA 1 4 USI287ME PYRAMID JOBB 1 4 USI287ME PYRAMID JOBC 1 4 USI287ME PYRAMID JOBD 1 4 USI287ME PYRAMID JOBE 1 4 USI287ME PYRAMID JOBF 1 4 USI287ME PYRAMID JOBG 1 4 USI287ME PYRAMID Status -------------------------------Failed J1 452 RC= 12 Purged J1 453 RC= Schedule not Started Started J1 484 Waiting for Predecessors(s) Waiting for Predecessors(s) Waiting for Predecessors(s) Waiting for Predecessors(s) Waiting for Predecessors(s) Submitted J1 485 Waiting for Predecessors(s) Waiting for Predecessors(s) Waiting for Predecessors(s) Waiting for Predecessors(s) Waiting for Predecessors(s) Waiting for Predecessors(s)
Each job is displayed on a single row, along with its current status description and backlog and late conditions. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. CA-Scheduler only reads the first 50 jobs before displaying the list. As you scroll down, more rows are automatically added until the entire list has been built. Press PF5 to refresh the status of the currently displayed jobs even if the jobs' status no longer matches the status categories requested. Press PF6 to list all of the jobs 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. The following commands may be entered in the command column on one or more jobs: Command CAncel CP COmplete Force Use Issue a CANCEL JOB command. See 4.3.3.1, Cancel Job Command on page 4-66. Issue a CP JOB command. See 4.3.5.1, Cancel Post (CP) Job Command on page 4-74. Issue a COMPLETE JOB command. See 4.3.4, Complete Job Command on page 4-71. Issue a FORCE JOB command. See 4.3.8.1, Force Job Command on page 4-91.
4.2 Job Status
Command Hold P POst PUrge RELease REQuest RERun REStage RUn S SReq STart SUbmit Unpost =
Use Issue a HOLD JOB command. See 4.3.10.1, Hold Job Command on page 4-97. Display the job's predecessors, and the predecessor's status. See 4.2.2, Predecessor Display on page 4-38. Issue a POST SCD command. See 4.3.12.2, Post Schedule Command on page 4-109. Issue a PURGE JOB command. See 4.3.13.1, Purge Job Command on page 4-125. Issue a RELEASE JOB command. See 4.3.14.1, Release Job Command on page 4-130. Issue a REQUEST JOB command. See 4.3.15.1, Request Job Command on page 4-139. Issue a RERUN JOB command. See 4.3.16, Rerun Job Command on page 4-142. Issue a RESTAGE JOB command. See 4.3.17, Restage Job Command on page 4-146. Issue a RUN JOB command. See 4.3.18.1, Run Job Command on page 4-149. Display detail information about the job. Issue an SREQ JOB command. See 4.3.19.1, SREQ Job Command on page 4-154. Issue a START JOB command. See 4.3.20, Start Job Command on page 4-158. Issue a SUBMIT JOB command. See 4.3.21, Submit Job Command on page 4-160. Issue an UNPOST JOB command. See 4.3.22.1, Unpost Job Command on page 4-165. Repeat the previous command.
If RERUN or SUBMIT is issued and the installation option RERCONF (rerun confirmation) is set to yes, then the current status of the job is checked. If the job has already completed successfully, then the following panel is displayed.
4-18 Online Guide
4.2 Job Status
------------------ CA-SCHEDULER 9. COMMAND ===>
xxyy (xxxx) CONFIRMATION ------------------
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. OPTION ===> Job . . . . . TUE From Node . . USI287ME Status . . . Purged 1 2 3 Number . .
xxyy (SCHD) JOB STATUS DETAIL --------------1 Station . . 4 RC= Schedule . . DAYOWK
J1 156
DETAILS - Detail Information on the Job PREDECESSORS - Information on this Job's Predecessors STAGE JCL - Alter Staged JCL
Enter END to exit.
Use option 1, DETAILS, to display and alter information about the job in the current workload. 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-Scheduler active 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 the workload. You can modify some of the fields. A command is built and sent to the CA-Scheduler started task for any modifications. Several panels contain the fields. Use PF7 and PF8 to scroll up and down through the panels. 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 Job Status Detail panels are redisplayed, allowing you to correct the problem. The batch utility to use is CAJUCMD0. The batch command is TALTER JOB.
---------------- CA-SCHEDULER 9. OPTION ===> Job . . . . . From Node . . Current Status: Status . . . . . . . Selection Code . . . Backlog Eligible . . Currently Backlogged Staged . . . . . . . Waiting on Global . Last Proc Step . . . . . . . . . . Number . .
xxyy (SCHD) JOB STATUS DETAIL --------------Station . . Schedule . .
. . . . . . .
Original JES Number . Changed . . Waiting on SEPDSN . . Last Step . . . . . . Track Must Start Time . Track Must End Time . . Track Maximum Time . .
Late: Late due to Must Start Time . Late due to Must End Time . . Late due to Maximum Time . .
You may jump to this panel from other Job Status Detail panels by using one of the following jump commands: TOP STATus LATE
4-20 Online Guide
4.2 Job Status
The fields are: Job The name of the job currently displayed. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job currently displayed. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JNo Default: 01 Station The station of the job currently displayed. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: STation Default: 40 Schedule The schedule to which the currently displayed job belongs. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: First schedule that contains this job name From Node The NJE node where the job is controlled, or blanks if the CA-Scheduler NJE option is set to NO. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Local node name Status The current status of this job. Display only with no batch equivalent. Selection Code The reason why this job is part of the current workload. If RC is 01 - 79 This number Corresponds to the position of the reason on the criteria statement that was defined for this job or schedule. A job will inherit the reason code from a schedule if no criteria record exists for the job.
4.2 Job Status
80 84 88 92
Indicates that it was selected because today's date corresponds to a workday on the calendar that was defined for this job or schedule. Indicates that it is selected by default every day because no selection criteria were defined or the criteria record is blank (NULL). Indicates that it was added to today's workload by the online RUN command. Identifies a schedule that is being run because a job abended. (This schedule was defined on the ABEND option as an alternate schedule in case of abend.) Indicates that the job originates from another node (NJE). Indicates a nonscheduled OS/390 job. Indicates that it was added to today's workload by the online ADD command. Indicates that this job was a backout job that was submitted for an abended job that specified ABEND=BACKOUT.
93 94 95 96
Original JES Number If the job has been transmitted using JES NJE, it may not have the same JES job number it did when it was submitted. The original number is displayed here, or zeros to indicate that the job has not been transmitted. Backlog Eligible Determines if CA-Scheduler should keep this copy of the job if it has not completed by the next autoscan. Size/Type: YES or NO Required: No Batch Keyword: Backlog Currently Backlogged Indicates whether another copy of this job (or schedule) is waiting to run as soon as this copy completes. Display only with no batch equivalent. Staged Indicates if a copy of the job's JCL has been written to the CA-Scheduler active workload. Display only with no batch equivalent. Changed The date and time that the staged JCL was last modified. If the JCL has not been staged, the date and time are blank. Display only with no batch equivalent. Waiting on Global Indicates if the job has an unsatisfied global variable. Display only with no batch equivalent.
4-22 Online Guide
4.2 Job Status
Waiting on SEPDSN Indicates if the job requires an exclusive resource that is currently held by another job. Display only with no batch equivalent. Last Proc Step The last step name (outside of a procedure) that executed in this job. Display only with no batch equivalent. Last Step The last step name (with an EXEC PGM= on it) that executed in this job. Display only with no batch equivalent. Late due to Must Start Time If YES, the job did not start by its Must Start Time. Display only with no batch equivalent. Track Must Start Time If YES, the job has a Must Start Time. Display only with no batch equivalent. Late due to Must End Time If YES, the job did not end by its Must End Start Time. Display only with no batch equivalent. Track Must End Time If YES, the job has a Must End Time. Display only with no batch equivalent. Late due to Maximum Time If YES, the job has been started longer than its Maximum Time. Display only with no batch equivalent. Track Maximum Time If YES, the job has a Maximum Time. Display only with no batch equivalent. Press PF8 for the next panel.
4.2 Job Status
---------------- CA-SCHEDULER 9. COMMAND ===> Job . . . . . 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 . . . . . . . . . . . . . . . . . . . Number . .
. . . . . . . . . .
You may jump to this panel from other Job Status Detail panels by using one of the following jump commands: 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 of the Scheduled Time date. Size/Type: (Online) 7 numeric Julian date and 4 digit time (Batch) 6 numeric in the form ddhhmm Required: No Batch Keyword: Erlytime Must Start Time The 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 be at least the value of the Scheduled Time date. Size/Type: (Online) 7 numeric Julian date and 4 digit time (Batch) 6 numeric in the form ddhhmm Required: No Batch Keyword: Musttime
4-24 Online Guide
4.2 Job Status
Must End Time The 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 be at least the value of the Scheduled Time date. Size/Type: (Online) 7 numeric Julian date and 4 digit time (Batch) 6 numeric in the form ddhhmm Required: No Batch Keyword: Deadline Maximum Execution The length of time that the job may execute before being marked late. The value is in the form ddhhmm, where dd is the number of autoscans and hhmm is the time. Display only with no batch equivalent. User-specified Average The length of time entered on the job in the database as an average execution time. The value is in the form ddhhmm, where dd is the number of autoscans and hhmm is the time. Display only with no batch equivalent. Historical Average The average amount of time for this job to execute, based on the last seven executions of the job. Display only with no batch equivalent. Scheduled Time The date and time the job was added to the workload. Display only with no batch equivalent. Available Time The date and time the job was first available to start (submitted). Display only with no batch equivalent. Start Time The date and time of the most recent start of the job. Display only with no batch equivalent. End Time The date and time of the most recent end of the job. Display only with no batch equivalent. Press PF8 for the next panel. It is displayed only for CPU jobs (station = 40).
4.2 Job Status
-------------- CA-SCHEDULER 9. COMMAND ===> Job . . . . . From Node . . JCL: Library Type JCL DDname . Member Name Insert CA-11 Memo Text . Testlib Parm Failure: Fail Oper . Abend Option Fail Option Job has Step . . . . . . RMS . . . . . . . . . . . . . . . . . . . . . . . . . .
xxyy (SCHD) CPU JOB STATUS DETAIL ------------Station . . Schedule . .
Number . .
. . . . . . . . . .
Member Subid . . . . Insert Sched Enviro . Sched Enviro . . . .
. . . . . . . . . . . . Records
Fail Code . . . . . Abend Count . . . . . Job Step Failed . . .
You may jump to this panel from other Job Status Detail panels by using one of the following jump commands: JCL FAILure The fields are: Library Type The access method to use in retrieving this job's JCL. DRIVER CA-Scheduler generates one line of JCL to be expanded by Driver.
USERLIB The access method is provided by a site-written exit program. See "User Exits and APIs" in the Systems Programmer Guide for more information.
4-26 Online Guide
4.2 Job Status
TESTLIB CA-Scheduler submits a dummy job (based on the skeleton in member CAJUTSTB of the PDS allocated to ddname JCLMASTR). The dummy job may execute for a specified number of seconds, end with a specific return code, or abend, based on parameters defined at the job level. See the field Test Parm in 5.2.2.1, Job Definition on page 5-29. ROSCOE CA-Roscoe Required: No Batch Keyword: Libtype JCL DDname The ddname that the CA-Scheduler started task should use for reading the job's JCL when the library type is PDS. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: DDname Member Subid Used to prefix the member name to generate the 10-character name used by CA-Panvalet. Display only with no batch equivalent. Member Name The member in the library that contains the job's JCL. If blank, the job name is used. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: LIBMemb Insert Sched Enviro Determines if a Workload Manager (WLM) scheduling environment should be inserted into this job's JCL. See also Scheduling Environment. Size/Type: YES or NO Required: No Batch Keyword: INSRSenv Insert CA-11 RMS Determines if the CA-11 Run Manager Step is inserted into the job during submission. Size/Type: YES or NO Required: No Batch Keyword: INSrrms
4.2 Job Status
Scheduling Environment The name of the Workload Manager (WLM) scheduling environment that should be inserted into this job's JCL. This field must not be blank, and Insert Sched Enviro must be set to YES before a scheduling environment (SCHENV) is inserted into the job's JCL. Size/Type: 1 to 16 alphanumeric characters Required: No Batch Keyword: SCHENV Memo Text If specified, this text is issued as a WTOR before the job executes. The operator must respond OK before the job runs. Display only with no batch equivalent. Testlib Parm The PARM to use for library type TESTLIB jobs. Fail Oper The relational operator used in determining whether a job's condition code should be treated as a FAILED condition. Successors to this job are not posted as satisfied. A value of blank means that any job step ending with a condition code greater than or equal to the Fail Code value is posted as FAILED. Successors to this job are not posted as satisfied. Valid relational operators are EQ, NE, GE, LE, GT, and LT. Size/Type: 2 alphanumeric characters Required: No Batch Keyword: FAILOper Default: GE Fail Code The condition code threshold which indicates job failure (an integer from 1-32767). Any job step ending with a condition code within the range specified by the fail code operator, Fail Oper, is posted as FAILED. Successors to this job are not posted as satisfied. A value of zero with Fail Oper equal to blanks means that CA-Scheduler is not checking the Fail Code. Size/Type: 1 to 4 numeric characters Required: No Batch Keyword: Failcode Default: 0 (zero) No condition code test is done Abend Option Determines what action to take if the job abends. Valid values are: ABORT (or blank) Do not let successors run. CONT Allow successors to run as if the job ended successfully.
4-28 Online Guide
4.2 Job Status
BACKOUT Submit another job, whose name is built based on the CAIJGEN option BACKOUT. schedule Run the specified schedule. Required: No Batch Keyword: Abend Abend Count The number of times this job has abended while a part of the workload. Display only with no batch equivalent. Fail Option Determines what action to take if the job ends with an unacceptable return code. Valid values are: ABORT (or blank) Do not let successors run. CONT Allow successors to run as if the job ended successfully. BACKOUT Submit another job, whose name is built based on the CAIJGEN option BACKOUT. schedule Run the specified schedule. Required: No Batch Keyword: FAILEd Job has Step Records If YES, the Fail Oper and Fail Code are ignored in favor of the Job Step Records in determining if the job ended with an unacceptable return code. Display only with no batch equivalent. Job Step Failed One or more steps ended with a return code defined as unacceptable by the Job Step Records. Display only with no batch equivalent. Press PF8 for the next panel.
4.2 Job Status
---------------- CA-SCHEDULER 9. COMMAND ===> Job . . . . . From Node . . Scheduled at: Node . . . Current location: Node . . . Separate Job Resource . Job List . . Execution: . . . . . . . . . Number . .
Sysid . . . Sysid . . .
. . . .
. . . .
. . . .
Selection: Date Table . . . . . . Calendar . . . . . . . Enter END to exit, DOWN for next screen, or UP for previous screen.
You may jump to this panel from other Job Status Detail panels by using one of the following jump commands: EXEC RESource SELect The display-only fields are: Scheduled At Node The NJE node where the job was originally scheduled to run, or blanks if for the local node. Scheduled At Sysid The system ID where the job on which the job was originally scheduled to execute, or blanks for any system. Current location Node If the CA-Scheduler installation option NJE is NO, this field is blank. If NJE is set to YES and the job has not yet been submitted, the owning (local) node is displayed. After the job has been submitted and reached a different node, the value is the remote node name. Current location Sysid The system ID where the job actually ran or blanks if the job has not started yet. Resource The name of a resource internal to CA-Scheduler which this job must have exclusive control over before it can be submitted. Job List Full or partial job names which cannot be submitted or running when this job is submitted.
4-30 Online Guide
4.2 Job Status
Date Table The date table used in evaluating the job's criteria. Calendar The calendar used in selecting this job. Press PF8 for the next panel.
---------------- CA-SCHEDULER 9. COMMAND ===> Job . . . . . From Node . . Number . .
User ids: User who Issued RUN . . User who Issued SUBMIT. User who Defined Job . JSI User id . . . . . . Staged JCL Changed by . User User User User User User who who who who who who Held . . . Released . Forced . . Cancelled Started . Completed . . . . . . . . . . . .
. . . . . . . . . . .
Group Group Group Group Group
id id id id id
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
You may jump to this panel from other Job Status Detail panels by using one of the following jump commands: USERids SECurity The display-only fields are: User who Issued RUN/Group id The 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 id The user and group ID of the last person who caused this job to be submitted. User who Defined Job/Group id The user and group ID of the last person to modify the job in the database. JSI User id/Group id The user and group ID associated with the job, schedule, or CA-Scheduler. If the CA-Scheduler installation option SUBUID includes the value JSI, this user/group ID is used. Staged JCL Changed by/Group id The user and group ID who last changed the staged JCL. If the JCL is not staged or has not yet been modified, these fields are blank.
4.2 Job Status
User who Held The last person to hold this job. User who Released The last person to release this job. User who Forced The last person to issue the FORCE JOB command on this job. User who Cancelled The person who removed this job from the workload. User who Started The last person who issued the START JOB command for this job. User who Completed The last person who issued the COMPLETE JOB command for this job. Press PF8 for the next panel.
---------------- CA-SCHEDULER 9. COMMAND ===> Job . . . . . CHAS 1 From Node . . USI287ME Number . .
xxyy (SCHD) JOB STATUS DETAIL --------------1 Station . . 4 Schedule . . CHAS 1
Documentation: Display Key . . . KEY12345 Display Time . . Other: JES Priority . . . . . . . JES Class . . . . . . . . Predecessor Priority . . , Internal Priority . . . , Use Simulation Times . . . Command Causing Submission Date on RUN Command . . . User Data . . . . . . . . . . , , . . . . . . , , . . . . 1 F 1 1 NO RELEASE
You may jump to this panel from other Job Status Detail panels by using one of the following jump commands: OTHer SIMulate DOC The display-only fields are: Display Key The CA-Scheduler workload documentation entry that should be displayed on the OS/390 console for this job.
4-32 Online Guide
4.2 Job Status
Display Time The time at which the CA-Scheduler workload documentation entry should be displayed on the OS/390 console. JES Priority If modified and the job has been submitted, the job's JES priority is altered to this value. Otherwise, this field is used only for SIMULATE REVISE=YES processing. JES Class If modified and the job has been submitted, the job's JES class is altered to this value. Otherwise, this field is only used for SIMULATE REVISE=YES processing. Predecessor Priority A number used in ordering jobs on an internal chain of control blocks. This value is only of use to Computer Associates Technical Support. Internal Priority A number used in ordering jobs on an internal chain of control blocks. This value is only of use to Computer Associates Technical Support. Use Simulation Times If YES, the Early Start Time and other time fields may have been generated by SIMULATE reports. Command Causing Submission The CA-Scheduler command that caused the most recent submission of the job. Date on RUN Command The date on the RUN SCHEDULE command that added this job to the current workload. User Data Any user-specific data associated with this job. The data may be supplied by a user exit (see the Notification Exit in the Systems Programmer Guide) or on the TALTER JOB command. Size/Type: 1 to 16 alphanumeric characters Required: No Batch Keyword: USERData Press PF8 for the next panel.
4.2 Job Status
---------------- CA-SCHEDULER 9. COMMAND ===> Job . . . . . From Node . . Userid to Notify All Events . . Job Start . . Job Fail . . . Job Abend . . Job Interrupt Job End . . . Job Purge . . Job Late . . . for: . . . . . . . . . . . . . . . . Number . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
You may jump to this panel from other Job Status Detail panels by using one of the following jump commands: JMR MSG The display-only fields are: All Events A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the job starts, fails, abends, is interrupted, becomes late, ends, and is removed from the active workload. See below for more information. Job Start A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the job starts. See below for more information. Job Fail A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the job fails. See below for more information. Job Abend A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the job abends. See below for more information. Job Interrupt A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the job is interrupted. See below for more information. Job End A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the job ends. See below for more information.
4-34 Online Guide
4.2 Job Status
Job Purge A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the job is removed from the active workload. See below for more information. Job Late A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the job is marked late. See below for more information. Messages to users are not TSO SEND messages. They are stored in the CA-Scheduler active workload and must be retrieved manually by the user. Messages are not kept indefinitely--see the CAIJGEN option MSGHOLD for more information. Messages are stored in the CA-Scheduler database when the value is MAILBOX, and may 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 of appropriate route codes and descriptor codes for your site. 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. Press PF8 for the next panel.
---------------- CA-SCHEDULER 9. COMMAND ===> Job . . . . . From Node . . Inform JES Nodes: Node . . . . . . Number . .
. . . .
. . . .
. . . .
You may jump to this panel from other Job Status Detail panels by using one of the following jump commands: JNR NODES
4.2 Job Status
The display-only fields are: Node Up to eight JES NJE nodes, defined by the CAIJNET macro, that will be notified when this job starts and ends. This field does not change where the job executes, only who is told about the job. Press PF8 for the next panel.
---------------- CA-SCHEDULER 9. COMMAND ===> Job . . . . . From Node . . Number . .
Cross-Platform information: Node . . . . Domain . . . User id . . Password . . Verify . . . SU Flag . .
Enter END to exit, or UP for previous screen.
You may jump to this panel from other Job Status Detail panels by using one of the following jump commands: XPLAT CROSS BOTTOM The fields on this panel are used when submitting jobs to Unicenter TNG or CA-Scheduler Agent on another platform. The execution node (on a previous panel) must be *REMOTE. The fields are: Node The CCI node where the job should execute. Size/Type: 1 to 8 alphanumeric characters Required: NO Batch Keyword: XPNode Domain The Microsoft Windows NT Domain to which the user ID below belongs. Size/Type: 1 to 15 alphanumeric characters Required: No Batch Keyword: XPDomain
4-36 Online Guide
4.2 Job Status
User id The user ID with which the job should execute. Size/Type: 1 to 31 alphanumeric characters Required: No Batch 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. 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 from the status displays or when you select option 2 from the schedule and job status detail menus.
------------------ CA-SCHEDULER 9. COMMAND ===> Job . . FL6 Number . . 1
xxyy (SCHD) PREDECESSORS Station . . 4
Schedule . . FLOW1
Command Type Name / Current Status Satisfied -------- -------- -------------------------------------------------- --------________ JOB FL5 1 4 FLOW1 NO Waiting for Predecessor(s) BOTTOM OF DATA
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 more predecessors: Command P Use Displays the predecessors of the predecessor. May only be used on 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.
---------------- CA-SCHEDULER 9. OPTION ===> Job . . . . . From Node . . Number . .
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. COMMAND ===> 1 2 3 4 5 6 7 8 9 1 11 12 13 14 15 16 17 18 19 2 21
xxyy (SCHD) STAGED JCL--WED- 1 4
DAYOWK -------------SCROLL ===> CSR
TOP OF DATA //WED JOB '1','CA-SCHEDULER',CLASS=A,MSGCLASS= //TESTSTEP EXEC PGM=CAJUTSTB,PARM='T=1 ' // // // // THIS JCL MEMBER IS USED AS MODEL TO SUBMIT LIBTYPE=TESTLIB JOBS. // IT MUST BE ADDED TO YOUR SITE'S JCL LIBRARY (DDNAME=JCLMASTR) // THE JOB NAME IN THE JOB STATEMENT IS REPLACED BY CA-SCHEDULER // JOB NAME TAKEN FROM THE JBR AT SUBMIT TIME. // IF 'TESTLIB PARMS(TESTPARM=)' WAS DEFINED IN THE JBR THEN // THE //TESTSTEP EXEC... CARD IS REPLACED BY AN INTERNAL CARD WITH // THE PARMS TAKEN FROM THE JBR. // RULES FOR THIS MEMBER: // 1- THE JOB CARD MUST REMAIN THE FIRST CARD IN THIS MEMBER // 2- THE FIRST 15 POSITIONS IN THE JOB CARD MUST NOT BE CHANGED // 3- THE JOB CARD MAY BE CONTINUED IF DESIRED. // 4- THE EXEC CARD MAY BE LOCATED ANYWHERE IN THIS MEMBER // 5- THE EXEC CARD CANNOT BE CONTINUED. // 6- THE FIRST 28 POSITIONS IN THE EXEC CARD MUST NOT BE CHANGED // 7- COMMENTS OR ADDITIONAL JCL MAY BE ADDED AS DESIRED. //
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 used to indicate the beginning and end of Driver expansion. For example, if the JCL contains the following statements:
------ CA-SCHEDULER 9. COMMAND ===> 1 2 3 4 //BILLING //STEP1 // //
xxyy (SCHD) STAGED JCL--BILLING- 1 4
BILLING --------SCROLL ===> CSR
TOP OF DATA JOB '1','CA-SCHEDULER',CLASS=A,MSGCLASS= EXEC PGM=BILLING EXEC BILLPROC BOTTOM OF DATA
(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:
------ CA-SCHEDULER 9. COMMAND ===> 1 2 =NOTE= 3 =NOTE=
TOP OF DATA //BILLING JOB '1','CA-SCHEDULER',CLASS=A,MSGCLASS= //STEP1 EXEC PGM=BILLING EXPANDING PROCUDURE BILLPROC BILLDAT= 4 2yy PSTART= 3 1yy PEND= 331yy DUEDAT= 423yy END OF DRIVER EXPANSION BOTTOM OF DATA
Note: The =NOTE= lines are not part of the data in the edit session. A RESET command 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 the contents of the last SAVE command) after a DEXPAND command. For example, the example in the previous section showed the following output for the DEXPAND command:
TOP OF DATA //BILLING JOB '1','CA-SCHEDULER',CLASS=A,MSGCLASS= //STEP1 EXEC PGM=BILLING EXPANDING PROCUDURE BILLPROC BILLDAT= 4 2yy PSTART= 3 1yy PEND= 331yy DUEDAT= 423yy END OF DRIVER EXPANSION BOTTOM OF DATA
After the RECALL command is issued, the JCL might look like this:
------ CA-SCHEDULER 9. COMMAND ===> 1 //BILLING 2 //STEP1 3 //
4.2 Job Status
4.2.3.3 DPROMPT
The DPROMPT command lists all reserved Driver variables used by the job and their current values. The values may be changed for this edit session only, possibly changing the output of the DEXPAND command. For example, starting this edit session:
------ CA-SCHEDULER 9. COMMAND ===> 1 //BILLING 2 //STEP1 3 //
The DPROMPT command displays the following:
xxyy (SCHD) DPROMPT --
ROW 1 TO 1 OF 1 SCROLL ===> PAGE
Overtype the values of the variables below. Enter END to save changes and exit. Enter CAN to exit without saving changes. Variable ---------&C_JOBDT Value ------------------------------yy 92 BOTTOM OF DATA
Only one reserved variable, &C_JOBDT, is displayed because it is the only reserved variable used by the procedure BILLPROC. You may change the value of &C_JOBDT by overtyping it and pressing PF3. For example, if the value is changed to yy360, saved, and another DEXPAND command issued, the following would be displayed:
TOP OF DATA //BILLING JOB '1','CA-SCHEDULER',CLASS=A,MSGCLASS= //STEP1 EXEC PGM=BILLING EXPANDING PROCUDURE BILLPROC BILLDAT=1226yy PSTART=11 1yy PEND=113 yy DUEDAT= 116yy END OF DRIVER EXPANSION BOTTOM OF DATA
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. OPTION ===> A1 ADD A2 ALLOC C1 CANCEL C2 COMPLETE C3 CAN/POST D1 DEALLOC D2 DISPLAY F1 FORCE G1 GLOBALS
xxyy (SCHD) COMMANDS -------------------P1 POST P2 PURGE R1 R2 R3 R4 R5 RELEASE REQUEST RERUN RESTAGE RUN
S1 SREQ S2 START S3 SUBMIT 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 of the 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 active workload, or to add a predecessor/successor relationship between two jobs in the active workload. 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 to the 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. See 4.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 workload and to allow any successors to run as if the schedule or job completed normally. See 4.3.5, Cancel Post (CP) Commands on page 4-73. Use option D1, DEALLOC, to free a ddname from the CA-Scheduler started task. See 4.3.6, Dealloc Command on page 4-80. Use option D2, DISPLAY, to view current information common to all of CA-Scheduler, such as data sets allocated to the started task, autoscan times, and installation 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 all predecessors 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. See 4.3.9, Globals on page 4-95. Use option H1, HOLD, to prevent schedules and jobs from starting. See 4.3.10, Hold Commands on page 4-96. Use option M1, MESSAGES, to send or display messages within CA-Scheduler. See 4.3.11, Messages Menu on page 4-102. Use option P1, POST, to allow successors of schedules, jobs, job steps, and data sets to start. See 4.3.12, Post Menu on page 4-105. Use option P2, PURGE, to remove completed and canceled schedules and jobs from the 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) to start. See 4.3.14, Release Commands on page 4-129. Use option R2, REQUEST, to allow not-requested schedules and jobs and their successors 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 staging library. 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. See 4.3.18, Run Commands on page 4-148. Use option S1, SREQ, to allow not-requested schedules and jobs and selected successors 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 Job Command 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 data sets to wait, even if the predecessor has already completed. See 4.3.22, Unpost Commands on page 4-164. Use option V1, VARY, to start or stop CA-Scheduler NJE VTAM sessions. See 4.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 workload without 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. OPTION ===> 1 2 JOB PRED - Add a Job - Add a Predecessor
xxyy (SCHD) ADD ----------------------
Enter END to exit.
Use option 1, JOB, to add an undefined job to the active workload. See 4.3.1.1, Add Job Command on page 4-46 for more information. Use option 2, PRED, to add a predecessor/successor relationship between two jobs in the 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 Job dialog. The fields are contained on several panels. Use PF7 and PF8 to scroll up and down through the panels. To issue the ADD JOB command, use PF3. To exit without issuing the ADD JOB command, enter CAN on the command line. The batch utility to use for adding jobs is CAJUCMD0. The batch command is ADD JOB.
--------------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Selection: Backlog . . . . NO Times: Early Start . . . Must Start . . . Must End . . . . Maximum Execution . . . . . . . . Number . . 1
xxyy (SCHD) ADD JOB -------------------Schedule . .
Station . . 4
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 following jump commands: TOP BASE TIMes BACKlog The fields are: Name The name of the job being added. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name
4-46 Online Guide
4.3 Commands
Number The 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 characters Required: No Batch Keyword: JNo Default: 01 Station The location where the job executes. Station 40 means a CPU job, which executes on the system. Stations less than 40 are for pre-CPU manual tasks, and stations greater than 40 are for post-CPU manual tasks. Size/Type: 2 numeric characters Required: No Batch Keyword: STation Default: 40 Schedule The schedule to which this job belongs. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: The four-character value of CAIJGEN installation option $DYNNM followed by the current SMF ID Backlog Determines what action CA-Scheduler should take if the job has not completed by the next autoscan and the job is scheduled to run again. YES indicates that the job should be retained until it (and the rest of its schedule) has completed. NO indicates that the job should be canceled (if not currently executing) and the next day's copy made available. Blank causes the schedule's Backlog option to be used. Size/Type: YES/NO/blank Required: No Batch Keyword: Backlog Default: NO Early Start The earliest time that this job can start. The value is in the format of ddhhmm, where dd is the number of autoscans that the job should wait, and hhmm is the time to start. Leading zeros do not need to be entered. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: Erlytime Default: 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. The value is in the format of ddhhmm, where dd is the number of autoscans that the job should wait, and hhmm is the time to start. Leading zeros do not need to be entered. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: MUsttime Default: 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. The value is in the format of ddhhmm, where dd is the number of autoscans that the job should wait, and hhmm is the time to start. Leading zeros do not need to be entered. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: Deadline Default: 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. The value is in the format of ddhhmm, where dd is the number of autoscans that the job should wait, and hhmm is the time to start. Leading zeros do not need to be entered. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: Maxtime Default: 0 (Never considered late) Internal Priority A number from 0 to 99, where 99 is the higher priority, that controls the order of internal control blocks. CA-Scheduler searches these control blocks to find work. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JPrty Default: 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. COMMAND ===> Name . . . A Number . . 1
xxyy (SCHD) ADD CPU JOB -----------------Station . . 4 Schedule . .
JCL: Library Type . . . . JCL DDname . . . . . Member Name . . . . Submission: Local Execution Sysid . . Remote Execution Node . . Remote Execution Sysid .
Member Prefix . . .
Enter END to Exit, UP for Previous Screen, or DOWN for Next Screen.
You may jump to this panel from other Add Job panels by using one of the following jump commands: JCL SUBmit The fields are: Library Type The 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: DRIVER CA-Scheduler generates one line of JCL to be expanded by Driver.
USERLIB The access method is provided by a site-written exit program. See "User Exits and APIs" in the Systems Programmer Guide for more information.
4.3 Commands
TESTLIB CA-Scheduler submits a dummy job (based on the skeleton in member CAJUTSTB of the PDS allocated to ddname JCLMASTR). The dummy job may execute for a specified number of seconds, end with a specific return code, or abend, based on parameters defined at the job level. See the field Test Parm in 5.2.2.1, Job Definition on page 5-29. ROSCOE CA-Roscoe Required: No Batch Keyword: Libtype Default: Value on CAIJGEN option LIBTYPE JCL DDname For library type of PDS, the ddname of the partitioned data set containing the job's JCL. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: DDname Default: JCLMASTR Member Prefix A one to eight byte value that will prefix the Member Name field to generate a maximum ten-character name of CA-Panvalet members. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: MBrsubid Member Name The member name that contains the job's JCL. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: LIBMemb Default: Job name Local Execution Sysid The system ID on which this job should execute. The system ID must be part of the local multi-CPU environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: SYsid Default: Current system ID Remote Execution Node The NJE node at which this job should execute. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: NOde Default: Local NJE node
4-50 Online Guide
4.3 Commands
Remote Execution Sysid The system ID at another node on which this job should execute. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: NODESys Press PF8 for the next panel. It is only displayed for CPU jobs (station = 40).
------------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Failures: Fail Oper . Fail Code . Abend Option Fail Option Options: Insert CA-11 Stage JCL . Memo . . . . Test Parm . . . . . . . . . . . . . Number . .
xxyy (SCHD) ADD CPU JOB -----------------Station . . Schedule . .
. NO . NO . .
Interrupt . . . . .
You may jump to this panel from other Add Job panels by using one of the following jump commands: FAILures OPTions The fields are: Fail Oper A Boolean operator used in determining if the job ended with an unacceptable return 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). Size/Type: 2 alphanumeric characters Required: No Batch Keyword: FAILOper Default: GE Fail Code A number that is compared to the job's highest return code using the Fail Oper to determine if the job ended with an unacceptable return code. The following equation 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 Fail Oper of GE and a Fail Code of 1, making zero the only acceptable return code for the job. Size/Type: 1 to 4 numeric characters Required: No Batch Keyword: Failcode Default: 0 (zero) No condition code test is done Abend Option Determines what action to take if the job abends. Valid values are: ABORT Do not let successors run. CONT Allow successors to run as if the job ended successfully. BACKOUT Submit another job, whose name is built based on the CAIJGEN option BACKOUT. schedule Run the specified schedule. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Abend Default: ABORT Fail Option Determines what action to take if the job ends with an unacceptable return code. Valid values are: ABORT Do not let successors run. CONT Allow successors to run as if the job ended successfully. BACKOUT Submit another job, whose name is built based on the CAIJGEN option BACKOUT. schedule Run the specified schedule. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FAILEd Default: ABORT
4-52 Online Guide
4.3 Commands
Insert CA-11 Controls the automatic insertion of the CA-11 RMS. Size/Type: YES or NO Required: No Batch Keyword: INSrrms Default: NO Interrupt If Interrupt is set to Yes, the job is marked as Interrupted instead of Complete when it ends normally. Size/Type: YES or NO Required: No Batch Keyword: INterupt Default: NO Stage JCL If Stage JCL is set to Yes, the job's JCL is copied into the CA-Scheduler active workload and submitted from there. Size/Type: YES or NO Required: No Batch Keyword: STAGe Default: NO Memo The value of the Memo field is displayed as a WTOR (Write To Operator with Reply) at the beginning of the job. A manual reply by the operator is required before the job may execute. Size/Type: 1 to 60 alphanumeric characters Required: No Batch Keyword: MEmo Test Parm For library type of TESTLIB, the Test Parm determines how long the job executes and how it ends. One or more of the following may be specified: T=nnnn Number of seconds to execute F=nnnn Normal return code to generate A=nnnn Abend code to generate (user abend) If multiple options are specified, separate them with commas. Size/Type: 1 to 20 alphanumeric characters Required: No Batch Keyword: TEstparm Default: 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 equal to 40).
----------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Number . .
xxyy (SCHD) ADD NON-CPU JOB ---------------Station . . Schedule . .
Non-CPU Options: Automatic Start . . NO
The fields are: Automatic Start If Automatic Start is set to Yes, then the non-CPU job is started as soon as all predecessors have been satisfied. If Automatic Start is set to No, then the START command must be used. See 4.3.20, Start Job Command on page 4-158. Size/Type: YES or NO Required: No Batch Keyword: AUtostrt Default: NO Press PF8 for the next panel. It is only displayed for CPU jobs (station = 40).
4-54 Online Guide
4.3 Commands
--------------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Number . .
xxyy (SCHD) ADD JOB -------------------Schedule . .
Station . .
Simulation: JES Class . . . . . . . JES Priority . . . . . Documentation: Display Key . . . Display Time . .
You may jump to this panel from other Add Job panels by using one of the following jump commands: SIM DOC The fields are: JES Class The value that SIMULATE REVISE=YES should use in determining which simulation initiator the job should use. The value is not used outside of simulation. Size/Type: 1 alphanumeric character Required: No Batch Keyword: Class Default: A JES Priority The value that SIMULATE REVISE=YES should use in determining when a job should start in the simulation. If multiple jobs are available to start, jobs with high JES Priority values are started first. The value is not used outside of simulation. Size/Type: 1 to 2 numeric characters from 0 to 15 Required: No Batch Keyword: Prty Display Key A one to eight character key of documentation that should be displayed on the OS/390 console for this job. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Dispkey
4.3 Commands
Display Time The time at which the documentation referred to by Display Key should be displayed on the OS/390 console. The value is in the format of ddhhmm, where dd is the number of autoscans that the job should wait, and hhmm is the time to start. Leading zeros do not need to be entered. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: DISPTime Default: 0 (Display documentation immediately) Press PF8 for the next panel.
-------------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Successors: Job name JNO -------- --. . . . . . St -. . . . . . . . . . . . Number . . Schedule -------. . . . . .
xxyy (SCHD) ADD PREDS ------------------Station . . Schedule . . Oper ---. . . . . . . . . . . . Code ----
ProcStep -------. . . . . .
Stepname --------
You may jump to this panel from other Add Job panels by using one of the following jump commands: PReds Up to six job or job step predecessors may be defined that must complete before the job being added may start. The columns are: Job name The name of the job that must complete or that contains the job step that must complete. Size/Type: 1 to 8 alphanumeric characters Required: Yes if anything else on same line is entered Batch Keyword: PJOBn where n is 1 to 6
4-56 Online Guide
4.3 Commands
JNO The number of the job that must complete or that contains the job step that must complete. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: PJNOn where n is 1 to 6 Default: 01 St The station of the job that must complete or that contains the job step that must complete. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: PSTn where n is 1 to 6 Default: 40 Schedule The schedule of the job that must complete or that contains the job step that must complete. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: PSCHDn where n is 1 to 6 Default: Any job that matches the other information on the line satisfies the requirement. ProcStep The procedure step name (outside of the PROC) that must complete. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: PPROCn where n is 1 to 6 Stepname The step name (with the EXEC PGM=) that must complete. Size/Type: 1 to 8 alphanumeric characters Required: No, unless ProcStep, Oper, or Code is entered Batch Keyword: PSTEPn where n is 1 to 6 Oper A Boolean operator used to determine if the step successfully ended. See Code. Valid values are as follows: GE Greater than or Equal GT Greater Than EQ EQual
4.3 Commands
NE Not Equal LT Less Than LE Less than or Equal Required: No Batch Keyword: PFOPRn where n is 1 to 6 Code A number compared to the return code of the specified step to determine if the step 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 to EQ and Code set to 0 (zero) to allow only a return code of zero. Size/Type: 1 to 5 numeric characters from 0 to 4095 Required: No, unless Oper is specified Batch Keyword: FAILn where n is 1 to 6 Default: If Oper and Code are not entered, then any normal end (not an abend) of the step is accepted Press PF8 for the next panel.
----------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Successors: Job name JNO -------- --. . . . . . St -. . . . . . . . . . . . Number . . Schedule -------. . . . . .
xxyy (SCHD) ADD SUCCESSORS ----------------Station . . ProcStep -------. . . . . . Schedule . . Oper ---. . . . . . . . . . . . Code ----
Stepname --------
Enter END to Exit or
UP for Previous Screen.
You may jump to this panel from other Add Job panels by using one of the following jump commands: 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 a step in job being added) before they may start. The columns are: Job name The name of the job that must wait for the job being added or one of its steps. Size/Type: 1 to 8 alphanumeric characters Required: Yes if anything else on same line is entered Batch Keyword: SJOBn where n is 1 to 6 JNO The 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 99 Required: No Batch Keyword: SJNOn where n is 1 to 6 Default: 01 St The 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 99 Required: No Batch Keyword: SSTn where n is 1 to 6 Default: 40 Schedule The schedule of the job that must wait for the job being added or one of its steps. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: SSCHDn where n is 1 to 6 Default: Any job that matches the other information on the line waits ProcStep The 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 characters Required: No Batch Keyword: SPROCn where n is 1 to 6 Stepname The 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 characters Required: No, unless ProcStep, Oper, or Code is entered Batch Keyword: SSTEPn where n is 1 to 6
4.3 Commands
Oper A Boolean operator used to determine if the step successfully ended. See Code. Valid values are as follows: GE Greater than or Equal GT Greater Than EQ EQual NE Not Equal LT Less Than LE Less than or Equal Note that the step is in the job being added. Size/Type: 2 alphanumeric characters Required: No Batch Keyword: SFOPRn where n is 1 to 6 Code A number compared to the return code of the specified step to determine if the step 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 to EQ and Code set to 0 (zero) to allow only a return code of zero. Note that the step is in the job being added. Size/Type: 1 to 4 numeric characters from 0 to 4095 Required: No, unless Oper is specified Batch Keyword: SFAILn where n is 1 to 6 Default: 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 Pred dialog. The Add Pred command defines a predecessor/successor relationship between two jobs in the workload without having to change the successor job's criteria. The change is only for the current workload. Both jobs must be in the workload. The predecessor job may 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. COMMAND ===> Job: Job Name Number . Station Schedule . . . . . . . . . . . . . . 1 . 4 .
xxyy (SCHD) ADD PRED --------------------
Should wait for job: Job Name . . . . Number . . . . . 1 Station . . . . 4 Schedule . . . .
Enter END to exit.
The fields are: Job Name The name of the successor job. The successor job may not be started yet. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The JNO of the successor job. Size/Type: 2 numeric characters Required: No Batch Keyword: JNO Default: 01
4.3 Commands
Station The station of the successor job. Size/Type: 2 numeric characters Required: No Batch Keyword: STation Default: 40 Schedule The schedule of the successor job. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Schedule Default: 40 Should wait for job name The name of the predecessor job. The predecessor job may not be completed yet. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: PJOB Number The JNO of the predecessor job. Size/Type: 2 numeric characters Required: No Batch Keyword: PJNO Default: 01 Station The station of the predecessor job. Size/Type: 2 numeric characters Required: No Batch Keyword: PSTat Default: 40 Schedule The schedule of the predecessor job. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch 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 command dialog. The Alloc command allocates one or more data sets to a specified ddname in the CA-Scheduler started task. Typically, you use it to allocate a new (or newly compressed) JCL library. See also 4.3.6, Dealloc Command on page 4-80 and 4.3.7.1, Display Alloc Command on page 4-83. The batch utility to use is CAJUCMD0. The batch command is ALLOC.
-------------------- CA-SCHEDULER 9. 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxyy (SCHD) ALLOCATE ------------------
. . YES Route Sysid . .
Execute command at: Sysid . . Route . . Enter END to exit.
The fields are: DDname The ddname to which the data sets is allocated in the CA-Scheduler started task. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: DDname Dataset 1-10 The 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 characters Required: At least one data set name is required Batch Keyword: DSNnn where nn is 01 to 10
4.3 Commands
Auto Submit If Auto Submit is set to YES, then after the successful allocation of the data sets CA-Scheduler searches for any jobs currently in Submit Failed status. CA-Scheduler tries to resubmit the jobs. Size/Type: YES or NO Required: No Batch Keyword: AUTosub Default: YES Sysid Use Sysid to execute the command on another CPU in a multiple-CPU environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: SYSid Default: Current CPU Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch 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 and schedules are not allowed to start. See also 4.3.5, Cancel Post (CP) Commands on page 4-73.
--------------------- CA-SCHEDULER 9. OPTION ===> 1 2 3
xxyy (SCHD) CANCEL ---------------------
JOB - Cancel a Job SCHEDULE - Cancel a Schedule 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, Cancel Job Command on page 4-66 for more information. Use option 2, SCHEDULE, to remove a schedule and all of its jobs from the workload. See 4.3.3.2, Cancel Schedule Command on page 4-68 for more information. 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 has been 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. COMMAND ===> Job: Job Name . Number . . Station . Schedule . From Node . . . . . . . . . . . . 1 . 4 . .
xxyy (SCHD) CANCEL JOB -------------------
Cancel job . . . Execute command at: Route . . . . . Route Sysid . .
(if already submitted/started)
Enter END to exit.
The fields are: Job Name The name of the job to be removed from the workload. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be removed from the workload. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01
4-66 Online Guide
4.3 Commands
Station The station of the job to be removed from the workload. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 Schedule The schedule of the job to be removed from the workload. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: First schedule in the current workload that contains this job From Node The name of the node where the job was submitted. Only used in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Cancel job Determines if the job should be canceled from the operating system if it has already been submitted or has already started. If not specified, the CAIJGEN CANCJOB value is used. Size/Type: YES|NO Required: No Batch Keyword: CANcel Default: CAIJGEN CANCJOB value Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch 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 current workload. If any of the jobs have been submitted to OS/390, they are canceled even if they are currently executing. The batch utility to use is CAJUCMD0. The batch command is CANCEL SCHEDULE.
----------------- CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule Name . . From Node . . . . Cancel jobs . . . Execute command at: Route . . . . . Route Sysid . .
xxyy (SCHD) CANCEL SCHEDULE ----------------
Enter END to exit.
The fields are: Schedule The name of the schedule to be removed from the workload. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name From Node The name of the NJE node where the schedule is controlled. This field is only used in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode
4-68 Online Guide
4.3 Commands
Cancel jobs Determines if the jobs should be canceled from the operating system if they have already been submitted or have already started. If not specified, the CAIJGEN CANCJOB value is used. Size/Type: YES|NO Required: No Batch Keyword: CANcel Default: CAIJGEN CANCJOB value Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTsys
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. If any of the jobs have been submitted to OS/390, they are canceled even if they are currently executing. The batch utility to use is CAJUCMD0. The batch command is CANCEL ALL. The command has no keywords.
------------------- CA-SCHEDULER 9. COMMAND ===>
xxyy (SCHD) CANCEL ALL -------------------
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 exit without 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 Job dialog. 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 also use it for CPU jobs in a recovery situation. The batch utility to use is CAJUCMD0. The command is COMPLETE JOB.
------------------ CA-SCHEDULER 9. COMMAND ===> Job: Job Name . Number . . Station . Schedule . From Node . . . . . . . . . . . . 1 . 39 . .
xxyy (SCHD) COMPLETE JOB ------------------
Options: CPU Job . . . . . . . . . NO Execute command at: Route . . . . . Route Sysid . .
Enter END to exit.
The fields are: Job Name The name of the job to be completed. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be completed. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01
4.3 Commands
Station The station of the job to be completed. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: Station number specified in Default Start/Complete Station field in Chapter 3, Options on page 3-1 Schedule The schedule of the job to be completed. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: First schedule in the current workload that contains the job From Node The name of the node where the job was submitted. Only used in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node CPU Job Specify YES if this is a CPU job (station 40). CPU Job is used as a safety to prevent a manual completion on a job running in the system. Size/Type: YES or NO Required: No Batch Keyword: CPU=Y or CPU=N Default: NO Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 Post menu. The Cancel Post commands remove work from the current workload. Successor jobs and schedules are allowed to start. See also 4.3.3, Cancel Commands on page 4-65.
------------------- CA-SCHEDULER 9. OPTION ===> 1 2
xxyy (SCHD) CANCEL/POST ------------------
JOB - Cancel a Job and Post its Successors 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 for more information. Use option 2, SCHEDULE, to remove a schedule and all of its jobs from the workload. See 4.3.5.2, Cancel Post Schedule Command on page 4-77 for more information.
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 job has 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. COMMAND ===> Job: Job Name . Number . . Station . Schedule . From Node . . . . . . . . . . . . 1 . 4 . .
xxyy (SCHD) CANCEL/POST JOB ----------------
Cancel Job . . . Post only this Job Name . . Number . . . Station . . Schedule . . Successor: . . . . . . . .
Execute command at: Route . . . . . Enter END to exit.
Route Sysid
. .
The fields are: Job Name The name of the job to be removed from the workload. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be removed from the workload. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01
4-74 Online Guide
4.3 Commands
Station The station of the job to be removed from the workload. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 Schedule The schedule of the job to be removed from the workload. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: The first schedule in the current workload that contains this job From Node The name of the node where the job was submitted. Only used in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Cancel job Determines if the job should be canceled from the operating system if it has already been submitted or has already started. If not specified, the CAIJGEN CANCJOB value is used. Size/Type: YES|NO Required: No Batch Keyword: CANcel Default: CAIJGEN CANCJOB value Post only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Post only this Successor blank, all successors may start. By entering a job name, only that successor may start. Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNo Default: 01
4.3 Commands
Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: The first schedule in the current workload that contains the Post Only job name Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 the current workload. If any of the jobs have been submitted to OS/390, they are canceled even if they are currently executing. The batch utility to use is CAJUCMD0. The batch command is CP SCHEDULE.
-------------- CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule Name . . From Node . . . . Cancel jobs Post only this Job Name . . Number . . . Station . . Schedule . . . . . Successor: . . . . . . . .
xxyy (SCHD) CANCEL/POST SCHEDULE --------------
Execute command at: Route . . . . .
Route Sysid
. .
Enter END to exit.
The fields are: Schedule Name The name of the schedule to be removed from the workload. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name From Node The name of the NJE node where the schedule is controlled. This field is only used in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode
4.3 Commands
Cancel jobs Determines if the jobs should be canceled from the operating system if they have already been submitted or have already started. If not specified, the CAIJGEN CANCJOB value is used. Size/Type: YES|NO Required: No Batch Keyword: CANcel Default: CAIJGEN CANCJOB value Post only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Post only this Successor blank, all successors may start. By entering a job name, only that successor may start. Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNO Default: 01 Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: First schedule in the current workload that contains the Post Only job name Sysid Use Sysid to execute the command on another CPU in a multiple-CPU environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: SYSid Default: Current CPU
4-78 Online Guide
4.3 Commands
Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
4.3 Commands
4.3.6 Dealloc Command

Use option D1 of the CA-Scheduler Commands menu to display the Dealloc Command dialog. The Dealloc Command frees (deallocates) a specified ddname from the CA-Scheduler started task. You typically use the command to make a JCL data set available for compressing. The batch utility to use is CAJUCMD0. The command is DEALLOC.
------------------- CA-SCHEDULER 9. COMMAND ===> Deallocate: DDname . . . . . Execute command at: Sysid . . . . . Route . . . . . Route Sysid . .
xxyy (SCHD) DEALLOCATE -------------------
Enter END to exit.
The fields are: DDname The ddname that should be freed from the CA-Scheduler started task. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: DDname Sysid Use Sysid to execute the command on another CPU in a multiple-CPU environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: SYSid Default: Current CPU
4-80 Online Guide
4.3 Commands
Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTsys
4.3 Commands
4.3.7 Display Commands

Use option D2 from the CA-Scheduler Commands menu to display the Display Commands menu.
--------------------- CA-SCHEDULER 9. OPTION ===> 1 2 3 4 5 6 7 8 9 A ALLOC DATE DATASET MVSJOBS NETWORK SECURITY XPLAT EVENTS FLOW VRM -
xxyy (SCHD) DISPLAY --------------------
List Datasets Allocated to the CA-Scheduler Started Task Autoscan Information List NJE Dataset Posting Rules List Jobs that will be Tracked from outside of CA-Scheduler Status of CA-Scheduler NJE Interface Status of CA-Scheduler External Security Interface Status of cross-platform nodes Cross-platform external events being tracked Critical Path Monitoring flows currently loaded 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 being used. 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 being used. 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 VTAM sessions. See 4.3.7.5, Display Network Command on page 4-87 for more information. Use option 6, SECURITY, to list the contents of the CAIJ$SEC macro currently being used. 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 which CA-Scheduler is communicating. See 4.3.7.7, Display XPLAT Command on page 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 currently being 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 Path Monitoring 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, and the jobs currently using or waiting for those resources. See 4.3.7.10, Display VRM Command 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 Alloc Command dialog. The Display Alloc Command lists the data sets allocated to the CA-Scheduler started task. 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. COMMAND ===> Options: DDname . . . .
xxyy (SCHD) DISPLAY ALLOC -----------------
(Leave blank for all allocations)
Enter END to exit.
The fields are: DDname If entered, Display Alloc shows only the specified ddname and its data sets. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: DDname Default: All ddnames
4.3 Commands
4.3.7.2 Display Date Command

Option 2 of the CA-Scheduler Display Commands menu displays the Display Date Command dialog. The Display Date Command provides information about the last autoscan performed and 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. COMMAND ===> System: Sysid . .
xxyy (SCHD) DISPLAY DATE ------------------
(Leave blank for local system)
Enter END to exit.
The field is: Sysid The system ID for which you want to see autoscan information. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: SYSid Default: 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 Dataset Command dialog. The Display Dataset Command lists the contents of the CAIJ$DSN macro currently in use. 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. COMMAND ===> Options: From entry . . . For entries . .
xxyy (SCHD) DISPLAY NJE DATASETS --------------
(Leave blank to start at the top) (Leave blank to entire list)
Enter END to exit.
The fields are: From entry The output starts at the CAIJ$DSN entry number specified here. Size/Type: 1 to 6 numeric characters Required: No Batch Keyword: FRom Default: 1 (The display starts at the first entry) For entries The output stops after this many entries have been displayed. Size/Type: 1 to 6 numeric characters Required: No Batch Keyword: FOr Default: All entries
4.3 Commands
4.3.7.4 Display MVSJobs Command

Option 4 of the CA-Scheduler Display Commands menu displays the Display MVSJobs Command dialog. The Display MVSJobs Command lists the contents of the CAIJ$MVS macro currently in 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. COMMAND ===> Options: From entry . . . For entries . .
xxyy (SCHD) DISPLAY $MVS JOBS ---------------
(Leave blank to start at the top) (Leave blank to entire list)
Enter END to exit.
The fields are: From entry The output starts at the CAIJ$MVS entry number specified here. Size/Type: 1 to 6 numeric characters Required: No Batch Keyword: FRom Default: 1 (The display starts at the first entry) For entries The output stops after this many entries have been displayed. Size/Type: 1 to 6 numeric characters Required: No Batch Keyword: FOr Default: 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 Network command. The Display Network command lists the status of the CA-Scheduler NJE VTAM sessions. Since the command has no keywords, it is issued immediately without an intervening panel. The batch utility to use is CAJUCMD0. The batch command is DISPLAY NETWORK.
4.3.7.6 Display Security Command

Option 6 of the CA-Scheduler Display Commands menu displays the Display Security command. The Display Security command lists the CA-Scheduler security options currently in use. Since the command has no keywords, it is issued immediately without an intervening panel. 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 XPLAT command. The Display XPLAT command lists the cross-platform nodes with which CA-Scheduler is communicating and their status. Since the command has no keywords, it is issued immediately without an intervening panel. 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 Events command. The Display Events command lists the cross-platform external events that are currently being tracked. Since the command has no keywords, it is issued immediately without an intervening panel. 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 Flow command. The Display Flow command lists Critical Path Monitoring job streams defined to CA-Scheduler. Since the command has no keywords, it is issued immediately without an intervening panel. 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 VRM command dialog. The Display VRM command lists the virtual resources known to CA-Scheduler, along with 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. COMMAND ===> Resource: Name . . . . .
xxyy (SCHD) DISPLAY VRM ------------------
(Resource name or mask)
Enter END to exit.
The field is: Name The name of the virtual resource to be displayed, or a mask to limit the virtual resources being displayed. Wildcard characters * and ? may be used. Size/Type: 1 to 30 numeric characters Required: No Batch Keyword: Resource Default: * (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 Command menu. The Force command causes schedules and jobs to start immediately, even if predecessors are still outstanding.
---------------------- CA-SCHEDULER 9. OPTION ===> 1 2
xxyy (SCHD) FORCE ---------------------
JOB - Force a Job to Start 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, Force Schedule 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 Job Command dialog. The Force Job command causes a job to start regardless of its status. Any predecessors or early start time requirements are ignored. If the job is a CPU job, the JCL is submitted to the operating system. The batch utility to use is CAJUCMD0. The batch command is FORCE JOB.
xxyy (SCHD) FORCE JOB -------------------
Execute command at: Route . . . . . Route Sysid . .
Enter END to exit.
Job Name The name of the job that is to be forced. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job that is to be forced. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 Station The station of the job that is to be forced. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40
4.3 Commands
Schedule The schedule of the job that is to be forced. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: First schedule in the current workload that contains the job From Node The NJE node where the job was originally submitted. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 Schedule Command dialog. The Force Schedule command causes a schedule to start regardless of its status. Any predecessors or early start time requirements are ignored. The batch utility to use is CAJUCMD0. The batch command is FORCE SCHEDULE.
----------------- CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule . . . . From Node . . . Execute command at: Route . . . . . Route Sysid . .
xxyy (SCHD) FORCE SCHEDULE -----------------
Enter END to exit.
The fields are: Schedule The name of the schedule that is to be forced. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name From Node The NJE node where the schedule is controlled. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node
4.3 Commands
Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 until some task is complete. The batch utility to use is CAJUCMD0. The batch command is SET GBLxnn where x is A, B, or C, and nn is 01 to 16.
--------------------- CA-SCHEDULER 9. 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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxyy (SCHD) GLOBALS --------------------
. . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
Character Values: GBLC 1 - 4 . . GBLC 5 - 8 . . GBLC 9 - 12 . . GBLC13 - 16 . . Enter END to exit.
The fields are: GBLA01 - 16 Numbers, each in the range of zero to 99,999,999. Size/Type: 1 to 8 numeric characters Required: Yes Batch Keyword: GBLA01 - 16 GBLB01 - 16 Yes or No. Size/Type: YES or NO Required: No, but existing values may not be blanked out Batch Keyword: GBLB01 - 16 GBLC01 - 16 Character values. Size/Type: 1 to 8 alphanumeric characters Required: No, but existing values may not be blanked out Batch 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. OPTION ===> 1 2 3 4 JOB SCHEDULE ALL SUBMIT Hold Hold Hold Turn
xxyy (SCHD) HOLD ----------------------
a Job a Schedule all Jobs and Schedules 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, Hold Schedule 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 Submit Command 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 been submitted 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.
xxyy (SCHD) HOLD JOB --------------------
Enter END to exit.
The fields are: Job Name The name of the job to be held. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be held. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 Station The station of the job to be held. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40
4.3 Commands
Schedule The schedule of the job to be held. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: First schedule in the current workload that contains this job From Node The name of the node where the job was submitted. Only used in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 already started, any of its jobs that have not yet started from starting. If any of the jobs have been 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. COMMAND ===> Schedule: Schedule Name . . From Node . . . . Execute command at: Route . . . . . . Route Sysid . . .
xxyy (SCHD) HOLD SCHEDULE -----------------
Enter END to exit.
The fields are: Schedule The name of the schedule to be held. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name From Node The name of the NJE node where the schedule is controlled. This field is only used in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node
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 have been 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. The command has no keywords.
-------------------- CA-SCHEDULER 9. COMMAND ===>
xxyy (SCHD) HOLD ALL --------------------
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 exit without 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 Hold All command, the statuses of jobs and schedules are not changed. Also, the Hold Submit command applies to all work added to the workload (that is, using the RUN command 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 this submit 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 as Submit Failed. If you have messages issued to the console for failures (CAS9 CAIJGEN FAILMSG=(OPERxxyy)), CA-Scheduler will issue messages for each job that cannot be submitted. The Submit Fail code will be 3C60, indicating that submission is held.
xxyy (SCHD) HOLD SUBMIT ------------------
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 without holding 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. OPTION ===> 1 2 QUERY SEND
xxyy (SCHD) MESSAGES --------------------
- Display messages sent to you - Send a CA-Scheduler message
Enter END to exit.
Use option 1, QUERY, to display any messages queued in CA-Scheduler for you. See the 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 once they are displayed. Autoscan deletes any messages that have not been displayed and are at least x minutes old. The CAIJGEN MSGHOLD option sets the number of minutes.
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 the Query Messages dialog (4.3.11.1, Query Messages on page 4-102) for information on displaying messages. The batch utility to use is CAJUCMD0. The batch command to use is SENDMSG.
--------------------- CA-SCHEDULER 9. COMMAND ===> Message: Text . . . User . . . Number . . Related Job: Job Name . Job Number Station . Schedule . . . . . . . . .
xxyy (SCHD) SENDMSG --------------------
(ALL for all users) (8 - 899)
Enter END to exit.
The fields are: Text The text of the message. Size/Type: 1 to 80 alphanumeric characters Required: Yes Batch Keyword: Text User The user ID to whom this message is being sent. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: User Number A number to be associated with this message. Size/Type: 1 to 3 numeric characters from 800-899 Required: No Batch Keyword: Mno
4.3 Commands
Related Job A 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: No Batch Keyword: Job, JNo, STation, Schedule Route The remote NJE node name where the command should be executed. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Route Sysid The system at the remote NJE multi-CPU node where the command should be executed. Size/Type: 1 to 4 alphanumeric characters Required: No Batch 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. The Post command is issued against the predecessor, not the successor schedule or job. Optionally, a specific successor may have its predecessor condition satisfied, without affecting other successors.
---------------------- CA-SCHEDULER 9. OPTION ===> 1 2 3 4 5 6 7 JOB SCHEDULE SJOB SSCHD DATASET MVS STEP Post Post Post Post Post Post Post
xxyy (SCHD) POST ----------------------
a Job a Schedule a Job Start a Schedule Start a Dataset Close an Unscheduled Job a Step within a Job
Enter END to exit.
Use option 1, JOB, to satisfy a predecessor of a CA-Scheduler job completing. See the next topic for more information. Use option 2, SCHEDULE, to satisfy a predecessor of a schedule completing. See 4.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. See 4.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 Dataset Command 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-Scheduler job. 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 waiting on a specific CA-Scheduler job to successfully complete. The predecessor conditions are created by criteria of the form:
- 1 4 jobname -jno station schedule
Optionally, a specific successor job may have its predecessor satisfied instead of all successors. The batch utility to use is CAJUCMD0. The batch command is POST JOB.
xxyy (SCHD) POST JOB --------------------
Post only this Job Name . . Number . . . Station . . Schedule . .
Successor: . . . . . . . .
Execute command at: Route . . . . . Route Sysid . . Enter END to exit.
The fields are: Job Name The job name whose successors are notified that the job has completed normally. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name
4-106 Online Guide
4.3 Commands
Number The number of the job whose successors are notified that the job has completed normally. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 Station The station of the job whose successors are notified that the job has completed normally. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 Schedule The schedule of the job whose successors are notified that the job has completed normally. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule From Node The node where the job whose successors are notified was originally submitted. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Post only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Post only this Successor blank, all successors may start. By entering a job name, only that successor may start. Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNo Default: 01
4.3 Commands
Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: First schedule in the current workload that contains the Post Only job name Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 schedules waiting on a specific schedule to end. The predecessor conditions are created by criteria of the form:
SCDschedule
Optionally, a specific successor job may have its predecessor satisfied instead of all successors. The batch utility to use is CAJUCMD0. The batch command is POST SCD.
------------------ CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule Name . . From Node . . . . Post only this Successor: Job Name . . . . Number . . . . . Station . . . . . Schedule . . . . Execute command at: Route . . . . . . Route Sysid . . .
xxyy (SCHD) POST SCHEDULE -----------------
Enter END to exit.
The fields are: Schedule The schedule whose successors are notified that it has completed normally. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name From Node The node where the schedule whose successors are notified is controlled. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node
4.3 Commands
Post only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Post only this Successor blank, all successors may start. By entering a job name, only that successor may start. Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNo Default: 01 Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: First schedule in the current workload that contains the Post Only job name Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 schedules waiting on a specific CA-Scheduler job to start. The predecessor conditions are created by criteria of the form:
- 1 4 STARTjobname -jno station schedule
Optionally, a specific successor job may have its predecessor satisfied instead of all successors. The batch utility to use is CAJUCMD0. The batch command is POST SJOB.
----------------- CA-SCHEDULER 9. COMMAND ===> Job: Job Name . Number . . Station . Schedule . From Node . . . . . . . . . . . . 1 . 4 . .
xxyy (SCHD) POST JOB START -----------------
Successor: . . . . . . . .
The fields are: Job Name The job name whose successors are notified that the job has started. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Name
4.3 Commands
Number The number of the job whose successors are notified that the job has started. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 Station The station of the job whose successors are notified that the job has started. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 Schedule The schedule of the job whose successors are notified that the job has started. Size/Type: 1 to 8 alphanumeric characters Required: Yes if CAIJGEN SECURTY=YES or EXTERNAL Batch Keyword: Schedule From Node The node where the job whose successors are notified was originally submitted. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Post only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Post only this Successor blank, all successors may start. By entering a job name, only that successor may start. Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNo Default: 01
4-112 Online Guide
4.3 Commands
Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: First schedule in the current workload that contains the Post Only job name Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 and schedules waiting on a specific schedule to start. The predecessor conditions are created by criteria of the form:
START SCDschedule
Optionally, a specific successor job may have its predecessor satisfied instead of all successors. The batch utility to use is CAJUCMD0. The batch command is POST SSCD.
--------------- CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule Name . . From Node . . . . Post only this Successor: Job Name . . . . Number . . . . . Station . . . . . Schedule . . . . Execute command at: Route . . . . . . Route Sysid . . .
xxyy (SCHD) POST SCHEDULE START --------------
Enter END to exit.
The fields are: Schedule The schedule whose successors are notified that it has started. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name From Node The node where the schedule whose successors are notified is controlled. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node
4-114 Online Guide
4.3 Commands
Post only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Post only this Successor blank, all successors may start. By entering a job name, only that successor may start. Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNo Default: 01 Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: First schedule in the current workload that contains the Post Only job name Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 schedules waiting on a data set to be updated. The predecessor conditions are created by criteria of the form:
DSN datasetname
Optionally, a specific successor job may have its predecessor satisfied instead of all successors. The batch utility to use is CAJUCMD0. The batch command is POST DSN.
------------------ CA-SCHEDULER 9. COMMAND ===> Dataset: Dataset Name . . Post only this Job Name . . Number . . . Station . . Schedule . . Successor: . . . . . . . .
xxyy (SCHD) POST DATASET ------------------
Enter END to exit.
The fields are: Dataset The data set name whose successors are notified that it has been updated. Size/Type: 1 to 44 alphanumeric characters Required: Yes Batch Keyword: Name Post only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Post only this Successor blank, all successors may start. By entering a job name, only that successor may start.
4-116 Online Guide
4.3 Commands
Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNo Default: 01 Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: First schedule in the current workload that contains the Post Only job name Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 schedules waiting on a non-CA-Scheduler job to successfully complete. The predecessor conditions are created by criteria of the form:
MVS jobname
Optionally, a specific successor job may have its predecessor satisfied instead of all successors. The batch utility to use is CAJUCMD0. The batch command is POST MVS.
-------------------- CA-SCHEDULER 9. COMMAND ===> Unscheduled Job: Job Name . . . . Post only this Job Name . . Number . . . Station . . Schedule . . Successor: . . . . . . . .
xxyy (SCHD) POST $MVS -------------------
Enter END to exit.
The fields are: Job Name The name of the job not controlled by CA-Scheduler whose successors are notified that it has completed. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Post only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Post only this Successor blank, all successors may start. By entering a job name, only that successor may start.
4-118 Online Guide
4.3 Commands
Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNo Default: 01 Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: First schedule in the current workload that contains the Post Only job name Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 schedules waiting on a specific step within a CA-Scheduler job to successfully complete. The predecessor conditions are created by criteria of the form:
jobname.stepname .procstep - 1 4 .CC.failoper.failcode -jno station schedule
Optionally, a specific successor job may have its predecessor satisfied instead of all successors. The batch utility to use is CAJUCMD0. The batch command is POST STEP.
------------------ CA-SCHEDULER 9. COMMAND ===> Job: Job Name . Proc Step Fail Oper Number . . Station . Schedule . From Node . . . . . . . . . . . . . . . . . . 1 . 4 . .
xxyy (SCHD) POST JOB STEP -----------------
Step Name . . Fail Code . .
( -4 95, 99999)
Successor: . . . . . . . .
The fields are: Job Name The job name with the step whose successors are notified that the job has completed normally. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Name
4-120 Online Guide
4.3 Commands
Proc Step The step name outside of the PROC used to identify the specific step whose successors are notified. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: PROC Step Name The step name (with the EXEC PGM= on it) whose successors are notified. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: STEP Fail Oper A Boolean operator that must match the value in the successor schedule's or job's criteria. 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 characters Required: No Batch Keyword: FAILOper Fail Code A 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's Fail Oper and Fail Code values, are notified. Size/Type: 1 to 5 numeric characters from 0 to 4095 or 99999 Required: No Batch Keyword: Failcode Number The number of the job with the step whose successors are notified that the job has completed normally. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 Station The station of the job with the step whose successors are notified that the job has completed normally. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40
4.3 Commands
Schedule The schedule of the job with the step whose successors are notified that the job has completed normally. Size/Type: 1 to 8 alphanumeric characters Required: Yes if CAIJGEN SECURTY=YES or EXTERNAL Batch Keyword: Schedule From Node The node where the job with the step whose successors are notified was originally submitted. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Post only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Post only this Successor blank, all successors may start. By entering a job name, only that successor may start. Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNo Default: 01 Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: First schedule in the current workload that contains the Post Only job 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. OPTION ===> 1 2 3
xxyy (SCHD) PURGE ---------------------
JOB - Purge a Job SCHEDULE - Purge a Schedule 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. See 4.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 must be either in completed, purged, or canceled status. The batch utility to use is CAJUCMD0. The batch command is PURGE JOB.
xxyy (SCHD) PURGE JOB -------------------
Enter END to exit.
The fields are: Job Name The name of the job to purge. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to purge. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JNo Default: 01 Station The station of the job to purge. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: STation Default: 40
4.3 Commands
Schedule The schedule of the job to purge. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: First schedule in the current workload that contains this job From Node The name of the node where the job was submitted. Only used in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 status displays. 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. COMMAND ===> Schedule: Schedule Name . . From Node . . . . Execute command at: Route . . . . . . Route Sysid . . .
xxyy (SCHD) PURGE SCHEDULE -----------------
Enter END to exit.
The fields are: Schedule The name of the schedule to be purged. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name From Node The name of the node where the job was submitted. Only used in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node
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 status displays, along with all jobs belonging to those schedules. Completed and canceled jobs in schedules that are still active are not removed. The batch utility to use is CAJUCMD0. The batch command is PURGE ALL. The command has no keywords.
xxyy (SCHD) PURGE ALL -------------------
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. Press PF3 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. OPTION ===> 1 2 3 4 5 6 7 JOB SCHEDULE ALL AUTO USER USERALL SUBMIT Release Release Release Release Release Release Turn on
xxyy (SCHD) RELEASE --------------------
a Job a Schedule all Jobs and Schedules work held by RHOLD=YES all work held by you all work held by all users 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 All Command on page 4-133 for more information. Use option 4, AUTO, to release all schedules and jobs after a restart of the CA-Scheduler started task. This only applies if the RHOLD=YES startup option is used. 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 User Command on page 4-135 for more information. Use option 6, USERALL, to release all jobs held by all users. See 4.3.14.6, Release Userall Command on page 4-136 for more information. Use option 7, SUBMIT, to turn submission back on (reverse the effect of HOLD SUBMIT). See 4.3.14.7, Release Submit Command on page 4-137 for more information.
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 Job command 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. COMMAND ===> Job: Job Name . Number . . Station . Schedule . From Node . . . . . . . . . . . . 1 . 4 . .
xxyy (SCHD) RELEASE JOB ------------------
Enter END to exit.
The fields are: Job Name The name of the job to be released. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be released. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 Station The station of the job to be released. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40
4-130 Online Guide
4.3 Commands
Schedule The schedule of the job to be released. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: First schedule in the current workload that contains this job From Node The name of the node where the job was submitted. Only used in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 the Hold Schedule command to start. All held jobs in the schedule are also allowed to start. If any of the jobs are held in JES, they are released. The batch utility to use is CAJUCMD0. The batch command is RELEASE SCHEDULE.
---------------- CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule Name . . From Node . . . . Execute command at: Route . . . . . . Route Sysid . . .
xxyy (SCHD) RELEASE SCHEDULE ----------------
Enter END to exit.
The fields are: Schedule The name of the schedule to be released. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name From Node The name of the NJE node where the schedule is controlled. This field is only used in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode
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 commands to start. Any jobs held in JES are released. The batch utility to use is CAJUCMD0. The batch command is RELEASE ALL. The command has no keywords.
xxyy (SCHD) RELEASE ALL ------------------
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 exit without 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=YES startup option of CA-Scheduler. You should not issue the command until after CA-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.
xxyy (SCHD) RELEASE AUTO ------------------
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 exit without 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 (by the same user that issues the Release User command) to start. Jobs that are held in JES are released. The batch utility to use is CAJUCMD0. The batch command is RELEASE USER.
xxyy (SCHD) RELEASE USER ------------------
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 held by 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 any CA-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. COMMAND ===>
xxyy (SCHD) RELEASE USERALL ----------------
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 by CA-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 jobs with 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. COMMAND ===>
xxyy (SCHD) RELEASE SUBMIT -----------------
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 without resuming 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 of REQUESTED.
--------------------- CA-SCHEDULER 9. OPTION ===> 1 2
xxyy (SCHD) REQUEST --------------------
JOB - Request a Job and all Successors 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 more information. Use option 2, SCHEDULE, to request a schedule, all of its jobs, and all of their successors. See 4.3.15.2, Request Schedule Command on page 4-140 for more information.
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 of REQUESTED. It also activates all successors of the job. The batch utility to use is CAJUCMD0. The batch command is REQUEST JOB.
------------------- CA-SCHEDULER 9. COMMAND ===> Job: Job Name Number . Station Schedule . . . . . . . . . . . . . . 1 . 4 .
xxyy (SCHD) REQUEST JOB ------------------
Enter END to exit.
The fields are: Job Name The name of the job to be requested. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be requested. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 Station The station of the job to be requested. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40
4.3 Commands
Schedule The schedule of the job to be requested. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: First schedule in the current workload that contains this job Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 has a criteria of REQUESTED. All of the jobs in the schedule, along with all successors of the jobs and the schedule, are also activated. The batch utility to use is CAJUCMD0. The batch command is REQUEST SCHEDULE.
4-140 Online Guide
4.3 Commands
---------------- CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule Name . . Execute command at: Route . . . . . . Route Sysid . . .
xxyy (SCHD) REQUEST SCHEDULE ----------------
Enter END to exit.
The fields are: Schedule The name of the schedule to be requested. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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. If the job has a Library Type of DRIVER, restart parameters are used instead of run parameters. CA-Scheduler fills in the CA-11 Options section of the Rerun Job dialog with the current 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, Job Status 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 even if 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. COMMAND ===> Job: Job Name . Number . . Station . Schedule . From Node . . . . . . . . . . . . 1 . 4 . . . . . . . . . . . . . .
xxyy (SCHD) RERUN JOB ---------
CA-11 Options: Insert CA-11 RMS . . Restart Step . . . . Last Step . . . . . . RMS Condition Code . Reason for Rerun . . Set last code on step RMS Parm . . Execute command at: Route . . . . . Enter END to exit.
Set CMT to Bypass GDG Pseudo . . Usage . .
. . . .
. . . .
To . . . . . .
Route Sysid
. .
4-142 Online Guide
4.3 Commands
The fields are: Job Name The name of the job to be rerun. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be rerun. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 Station The station of the job to be rerun. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 Schedule The schedule of the job to be rerun. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: First schedule in the current workload that contains this job From Node The name of the node where the job was submitted. Only used in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Insert CA-11 RMS If YES, CA-Scheduler inserts the CA-11 Run Manager Step (RMS) into the job's JCL during submission. Size/Type: YES or NO Required: No Batch Keyword: INSrrms Default: The value of the Insert CA-11 RMS field for this job in the workload
4.3 Commands
Set CMT to Indicates if the CA-11 Catalog Management Table (CMT) for this job should be set to PRODUCTION or RESTART. Size/Type: PRODUCTION or RESTART Required: No Batch Keyword: CMT=P or CMT=R Default: The current setting of the CMT is left unchanged Restart Step The 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 characters Required: No Batch Keyword: REStstep Default: The step set in the CMT for restart, if the CA-11 AUTOS option is set to YES Bypass GDG If YES, certain CA-11 restrictions on changing JCL are relaxed. See the CA-11 documentation for more information. Size/Type: YES or NO Required: No Batch Keyword: BYPgdg Default: NO Last Step The 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 characters Required: No Batch Keyword: LAStstep Default: Last step of the job Pseudo If YES, CA-11 does not perform any processing other than reporting. This option is useful when first implementing CA-11. Size/Type: YES or NO Required: No Batch Keyword: PSEudo Default: No RMS Condition Code The return code with which the CA-11 RMS should end. Size/Type: 1 to 4 numeric characters from 0-4095 Required: No Batch Keyword: RMSCc Default: 0 (zero)
4-144 Online Guide
4.3 Commands
Usage A code that may be used by CA-11 to validate your restart request. Usage may be required by your CA-11 installation options. Size/Type: 1 numeric character Required: Dependent on CA-11 installation options Batch Keyword: USAge Reason for Rerun A text reason for the rerun/restart of this job. It may be required by your CA-11 installation options. Size/Type: 1 to 40 alphanumeric characters Required: Dependent on CA-11 installation options Batch Keyword: REAson Set last code on step/To Allows the previous return code (condition code) on the specified step to be changed during the restart. See the CA-11 keyword LRTCD for more information. Size/Type: 1 to 17 alphanumeric characters (stepname or procstep.stepname) and 1-4 numeric characters Required: No. Either both must be specified or both blank Batch Keyword: LRTCDSTP and LRTCDCOD RMS Parm The parm field for the RMS. If entered, any values entered for the other CA-11 options are ignored, except for the Reason for Rerun field. CA-11 dictates the syntax. Size/Type: 1 to 57 alphanumeric characters Required: No Batch Keyword: RMSParms Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 active workload. The JCL may then be edited without modifying the original copy. At submission time, the JCL is read from the active workload. The batch utility to use is CAJUCMD0. The batch command is RESTAGE JOB.
xxyy (SCHD) RESTAGE JOB ------------------
Enter END to exit.
The fields are: Job Name The name of the job to be restaged. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be restaged. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01
4-146 Online Guide
4.3 Commands
Station The station of the job to be restaged. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 Schedule The schedule of the job to be restaged. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: First schedule in the current workload that contains this job Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 to CA-Scheduler.
----------------------- CA-SCHEDULER 9. OPTION ===> 1 2 JOB - Run a Job SCHEDULE - Run a Schedule
xxyy (SCHD) RUN ----------------------
Enter END to exit.
Use option 1, JOB, to add a specific job to the workload. See the next topic for more information. Use option 2, SCHEDULE, to add a schedule and its jobs to the workload. See 4.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 to CA-Scheduler. If the job's schedule is not in the workload, it is added without any other jobs. The batch utility to use is CAJUCMD0. The batch command is RUN JOB.
--------------------- CA-SCHEDULER 9. COMMAND ===> Job: Job Name Number . Station Schedule . . . . . . . . . . . . . . 1 . 4 .
xxyy (SCHD) RUN JOB --------------------
Options: Hold . . . . . . NO Execute command at: Sysid . . . . . Route . . . . . Route Sysid . .
Enter END to exit.
The fields are: Job Name The name of the job to be run. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be run. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 Station The station of the job to be run. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40
4.3 Commands
Schedule The schedule of the job to be run. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: First schedule in the current workload that contains this job Hold Specify YES to add the job to the workload, but prevent it from starting. A Release command must be issued before the job may start. Size/Type: YES or NO Required: No Batch Keyword: HOLD Default: NO Sysid The specific CA-Scheduler that should process this command within the local multi-CPU environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: SYSid Default: Current system ID Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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. The criteria for the schedule's jobs are evaluated to determine if the jobs should also be added to the workload. The batch utility to use is CAJUCMD0. The batch command is RUN SCHEDULE.
------------------ CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule Name . . Options: Hold . . . . . . NO Date . . . . . . Execute command at: Sysid . . . . . Route . . . . . Route Sysid . .
xxyy (SCHD) RUN SCHEDULE ------------------
(AUTOS, TODAY, mmddyy, ddmmyy)
Enter END to exit.
The fields are: Schedule The schedule of the job to be run. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: First schedule in the current workload that contains this job Hold Specify YES to add the schedule to the workload, but prevent it from starting. A Release command must be issued before the schedule may start. Size/Type: YES or NO Required: No Batch Keyword: HOLD Default: NO
4.3 Commands
Date The date to use when evaluating the criteria for the schedule's jobs. AUTOS means the current autoscan date. TODAY means the current date, which may be one day later than the autoscan date, depending on when autoscan normally runs. Size/Type: 6 numeric characters, AUTOS, or TODAY Required: No Batch Keyword: Date Default: AUTOS Sysid The specific CA-Scheduler that should process this command within the local multi-CPU environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: SYSid Default: Current system ID Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
4-152 Online Guide
4.3 Commands
4.3.19 SREQ Commands

Option S1 of the CA-Scheduler Commands menu displays the SREQ (Selective Request) menu. The SREQ commands activate schedules and jobs with a criteria of REQUESTED and SOME of their successors.
---------------------- CA-SCHEDULER 9. OPTION ===> 1 2
xxyy (SCHD) SREQ ----------------------
JOB - Request a Job and some Successors 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 next topic for more information. Use option 2, SCHEDULE, to activate a schedule, its jobs, and some of their successors. See 4.3.19.2, SREQ Schedule Command on page 4-156 for more information.
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 selected successors of the job. Successors are only activated if they do not themselves have criteria of REQUESTED and do not inherit the REQUESTED attribute from any job other than the one being SREQed. The batch utility to use is CAJUCMD0. The batch command is SREQ JOB.
-------------- CA-SCHEDULER 9. COMMAND ===> Job: Job Name Number . Station Schedule . . . . . . . . . . . . . . 1 . 4 .
xxyy (SCHD) SELECTIVE REQUEST JOB -------------
Enter END to exit.
The fields are: Job Name The name of the job to be requested. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be requested. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01
4-154 Online Guide
4.3 Commands
Station The station of the job to be requested. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 Schedule The schedule of the job to be requested. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: First schedule in the current workload that contains this job Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 and selected successors of the schedule. Successors are only activated if they do not themselves have criteria of REQUESTED and do not inherit the REQUESTED attribute from any schedule other than the one being SREQed. The batch utility to use is CAJUCMD0. The batch command is SREQ SCHEDULE.
----------- CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule Name . . Execute command at: Route . . . . . . Route Sysid . . .
xxyy (SCHD) SELECTIVE REQUEST SCHEDULE -----------
Enter END to exit.
The fields are: Schedule The name of the schedule to be requested. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node
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. COMMAND ===> Job: Job Name . Number . . Station . Schedule . From Node Options: CPU Job . . . . . . . . . . . . . . .
xxyy (SCHD) START JOB -------------------
. . . . NO
Enter END to exit.
The fields are: Job Name The name of the job to be started. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be started. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 Station The station of the job to be started. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: Station number specified in Default Start/Complete Station field in Chapter 3, Options
4-158 Online Guide
4.3 Commands
Schedule The schedule of the job to be started. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: First schedule in the current workload that contains this job From Node The name of the node where the job was submitted. Only used in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node CPU Job If 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 NO Required: No Batch Keyword: CPU=Y or CPU=N Default: NO Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 submitted again. If the CA-11 interface is installed, a starting and/or ending step may be specified. If the job has a Library Type of DRIVER, run parameters are used instead of rerun parameters. CA-Scheduler fills in the CA-11 Options section of the Submit Job dialog with the current 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, Job Status 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 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 SUBMIT JOB.
------------------- CA-SCHEDULER 9. COMMAND ===> Job: Job Name . Number . . Station . Schedule . From Node . . . . . . . . . . . . 1 . 4 . . . . . . . . . . . . . .
xxyy (SCHD) SUBMIT JOB ---------
CA-11 Options: Insert CA-11 RMS . . Restart Step . . . . Last Step . . . . . . RMS Condition Code . Reason for Rerun . . Set last code on step RMS Parm . . Execute command at: Route . . . . . Enter END to exit.
Set CMT to Bypass GDG Pseudo . . Usage . .
. . . .
. . . .
To . . . . . .
Route Sysid
. .
4-160 Online Guide
4.3 Commands
The fields are: Job Name The name of the job to be submitted. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be submitted. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 Station The station of the job to be submitted. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 Schedule The schedule of the job to be submitted. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: First schedule in the current workload that contains this job From Node The name of the node where the job was submitted. Only used in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Insert CA-11 RMS If YES, CA-Scheduler inserts the CA-11 Run Manager Step (RMS) into the job's JCL during submission. Size/Type: YES or NO Required: No Batch Keyword: INSrrms Default: The value of the Insert CA-11 RMS field for this job in the workload
4.3 Commands
Set CMT to Indicates if the CA-11 Catalog Management Table (CMT) for this job should be set to PRODUCTION or RESTART. Size/Type: PRODUCTION or RESTART Required: No Batch Keyword: CMT=P or CMT=R Default: The current setting of the CMT is left unchanged Restart Step The 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 characters Required: No Batch Keyword: REStstep Default: The step set in the CMT for restart, if the CA-11 AUTOS option is set to YES Bypass GDG If YES, certain CA-11 restrictions on changing JCL are relaxed. See the CA-11 documentation for more information. Size/Type: YES or NO Required: No Batch Keyword: BYPgdg Default: NO Last Step The 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 characters Required: No Batch Keyword: LAStstep Default: Last step of the job Pseudo If YES, CA-11 does not perform any processing other than reporting. This option is useful when first implementing CA-11. Size/Type: YES or NO Required: No Batch Keyword: PSEudo Default: NO RMS Condition Code The return code with which the CA-11 RMS should end. Size/Type: 1 to 4 numeric characters from 0-4095 Required: No Batch Keyword: RMSCc Default: 0 (zero)
4-162 Online Guide
4.3 Commands
Usage A code that may be used by CA-11 to validate your restart request. Usage may be required by your CA-11 installation options. Size/Type: 1 numeric character Required: No Batch Keyword: USAge Default: Dependent on CA-11 installation options Reason for Rerun A text reason for the rerun/restart of this job. It may be required by your CA-11 installation options. Size/Type: 1 to 40 alphanumeric characters Required: Dependent on CA-11 installation options Batch Keyword: REAson Set last code on step/To Allows the previous return code (condition code) on the specified step to be changed during the restart. See the CA-11 keyword LRTCD for more information. Size/Type: 1 to 17 alphanumeric characters (stepname or procstep.stepname) and 1-4 numeric characters Required: No. Either both must be specified or both blank Batch Keyword: LRTCDSTP and LRTCDCOD RMS Parm The parm field for the RMS. If entered, any values entered for the other CA-11 options are ignored, except for the Reason for Rerun field. CA-11 dictates the syntax. Size/Type: 1 to 57 alphanumeric characters Required: No Batch Keyword: RMSParms Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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. OPTION ===> 1 2 3 4 5 6 7 JOB SCHEDULE SJOB SSCHD DATASET MVS STEP Unpost Unpost Unpost Unpost Unpost Unpost Unpost
xxyy (SCHD) UNPOST ---------------------
a Job a Schedule a Job Start a Schedule Start a Dataset Close an Unscheduled Job a Step within a Job
Enter END to exit.
Use option 1, JOB, to unsatisfy a predecessor of a CA-Scheduler job completing. See the next topic for more information. Use option 2, SCHEDULE, to unsatisfy a predecessor of a schedule completing. See 4.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. See 4.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, Unpost Dataset 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 a CA-Scheduler job. See 4.3.22.7, Unpost Job Step Command on page 4-179 for more information.
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 schedules waiting on a specific CA-Scheduler job to successfully complete. The predecessor conditions 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 all successors. The batch utility to use is CAJUCMD0. The batch command is UNPOST JOB.
------------------- CA-SCHEDULER 9. COMMAND ===> Job: Job Name . Number . . Station . Schedule . From Node . . . . . . . . . . . . 1 . 4 . . Successor: . . . .
xxyy (SCHD) UNPOST JOB -------------------
Unpost only this Job Name . . . Number . . . . Station . . . Schedule . . .
The fields are: Job Name The job name whose successors are notified that the job has completed normally. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name
4.3 Commands
Number The number of the job whose successors are notified that the job has completed normally. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 Station The station of the job whose successors are notified that the job has completed normally. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 Schedule The schedule of the job whose successors are notified that the job has completed normally. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule From Node The node where the job whose successors are notified was originally submitted. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Unpost only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Unpost only this Successor blank, all successors may start. By entering a job name, only that successor may start. Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNo Default: 01
4-166 Online Guide
4.3 Commands
Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: First schedule in the current workload that contains the Unpost Only job name Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 and schedules waiting on a specific schedule to end. The predecessor conditions are created by criteria of the form:
SCDschedule
Optionally, a specific successor job may have its predecessor unsatisfied instead of all successors. The batch utility to use is CAJUCMD0. The batch command is UNPOST SCD.
----------------- CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule Name . . From Node . . . . Unpost only Job Name Number . Station . Schedule this Successor: . . . . . . . . . . . . . . . .
xxyy (SCHD) UNPOST SCHEDULE ----------------
Execute command at: Route . . . . . . Route Sysid . . .
Enter END to exit.
Schedule The schedule whose successors are notified that it has completed normally. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name From Node The node where the schedule whose successors are notified is controlled. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node
4-168 Online Guide
4.3 Commands
Unpost only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Unpost only this Successor blank, all successors may start. By entering a job name, only that successor may start. Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNo Default: 01 Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: First schedule in the current workload that contains the Unpost Only job name Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 and schedules waiting on a specific CA-Scheduler job to start. The predecessor conditions are created by criteria of the form:
- 1 4 STARTjobname -jno station schedule
Optionally, a specific successor job may have its predecessor unsatisfied instead of all successors. The batch utility to use is CAJUCMD0. The batch command is UNPOST SJOB.
---------------- CA-SCHEDULER 9. COMMAND ===> Job: Job Name . Number . . Station . Schedule . From Node . . . . . . . . . . . . 1 . 4 . . Successor: . . . .
xxyy (SCHD) UNPOST JOB START ----------------
The fields are: Job Name The job name whose successors are notified that the job has started. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Name
4-170 Online Guide
4.3 Commands
Number The number of the job whose successors are notified that the job has started. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 Station The station of the job whose successors are notified that the job has started. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 Schedule The schedule of the job whose successors are notified that the job has started. Size/Type: 1 to 8 alphanumeric characters Required: Yes if CAIJGEN SECURTY=YES or EXTERNAL Batch Keyword: Schedule From Node The node where the job whose successors are notified was originally submitted. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Unpost only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Unpost only this Successor blank, all successors may start. By entering a job name, only that successor may start. Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNo Default: 01
4.3 Commands
Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: First schedule in the current workload that contains the Unpost Only job name Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 and schedules waiting on a specific schedule to start. The predecessor conditions are created by criteria of the form:
START SCDschedule
Optionally, a specific successor job may have its predecessor unsatisfied instead of all successors. The batch utility to use is CAJUCMD0. The batch command is UNPOST SSCD.
-------------- CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule Name . . From Node . . . . Unpost only Job Name Number . Station . Schedule this Successor: . . . . . . . . . . . . . . . .
xxyy (SCHD) UNPOST SCHEDULE START -------------
Execute command at: Route . . . . . . Route Sysid . . .
Enter END to exit.
The fields are: Schedule The schedule whose successors are notified that it has started. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name From Node The node where the schedule whose successors are notified is controlled. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node
4.3 Commands
Unpost only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Unpost only this Successor blank, all successors may start. By entering a job name, only that successor may start. Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNo Default: 01 Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: First schedule in the current workload that contains the Unpost Only job name Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 schedules waiting on a data set to be updated. The predecessor conditions are created by criteria of the form:
DSN datasetname
Optionally, a specific successor job may have its predecessor unsatisfied instead of all successors. The batch utility to use is CAJUCMD0. The batch command is UNPOST DSN.
----------------- CA-SCHEDULER 9. COMMAND ===> Dataset: Dataset Name . . Unpost only this Job Name . . . Number . . . . Station . . . Schedule . . . Successor: . . . .
xxyy (SCHD) UNPOST DATASET -----------------
Enter END to exit.
The fields are: Dataset The data set name whose successors are notified that it has been updated. Size/Type: 1 to 44 alphanumeric characters Required: Yes Batch Keyword: Name Unpost only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Unpost only this Successor blank, all successors may start. By entering a job name, only that successor may start.
4.3 Commands
Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNo Default: 01 Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: First schedule in the current workload that contains the Unpost Only job name Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 schedules waiting on a non-CA-Scheduler job to successfully complete. The predecessor conditions are created by criteria of the form:
MVS jobname
Optionally, a specific successor job may have its predecessor unsatisfied instead of all successors. The batch utility to use is CAJUCMD0. The batch command is UNPOST MVS.
------------------- CA-SCHEDULER 9. COMMAND ===> Unscheduled Job: Job Name . . . . Unpost only this Job Name . . . Number . . . . Station . . . Schedule . . . Successor: . . . .
xxyy (SCHD) UNPOST $MVS ------------------
Enter END to exit.
Job Name The job name whose successors are notified that the job has started. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Name Unpost only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Unpost only this Successor blank, all successors may start. By entering a job name, only that successor may start.
4.3 Commands
Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNo Default: 01 Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: First schedule in the current workload that contains the Unpost Only job name Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys
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 and schedules waiting on a specific step within a CA-Scheduler job to successfully complete. The predecessor conditions are created by criteria of the form:
jobname.stepname .procstep - 1 4 .CC.failoper.failcode -jno station schedule
Optionally, a specific successor job may have its predecessor unsatisfied instead of all successors. The batch utility to use is CAJUCMD0. The batch command is UNPOST STEP.
----------------- CA-SCHEDULER 9. COMMAND ===> Job: Job Name . Proc Step Fail Oper Number . . Station . Schedule . From Node . . . . . . . . . . . . . . . . . . 1 . 4 . . Successor: . . . .
xxyy (SCHD) UNPOST JOB STEP ----------------
Step Name . . Fail Code . .
( -4 95, 99999)
Execute command at: Route . . . . . Enter END to exit.
Route Sysid
. .
The fields are: Job Name The job name with the step whose successors are notified that the job has completed normally. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Name
4.3 Commands
Proc Step The step name outside of the PROC used to identify the specific step whose successors are notified. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: PROC Step Name The step name (with the EXEC PGM= on it) whose successors are notified. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: STEP Fail Oper A Boolean operator that must match the value in the successor schedule's or job's criteria. 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 characters Required: No Batch Keyword: FAILOper Fail Code A 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's Fail Oper and Fail Code values, are notified. Size/Type: 1 to 5 numeric characters from 0 to 4095 or 99999 Required: No Batch Keyword: Failcode Number The number of the job with the step whose successors are notified that the job has completed normally. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 Station The station of the job with the step whose successors are notified that the job has completed normally. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40
4-180 Online Guide
4.3 Commands
Schedule The schedule of the job with the step whose successors are notified that the job has completed normally. Size/Type: 1 to 8 alphanumeric characters Required: Yes if CAIJGEN SECURTY=YES or EXTERNAL Batch Keyword: Schedule From Node The node where the job with the step whose successors are notified was originally submitted. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Unpost only this Successor In allowing successors to start, you may allow all successors or identify a specific job that may start, leaving all others to continue waiting. By leaving the fields under Unpost only this Successor blank, all successors may start. By entering a job name, only that successor may start. Job Name Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYJob Number Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYJNo Default: 01 Station Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: ONLYST Default: 40 Schedule Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ONLYScd Default: First schedule in the current workload that contains the Unpost Only 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 between CA-Scheduler started tasks. These sessions are only used for NJE. The Vary VRM command is used to change the state of a virtual resource.
---------------------- CA-SCHEDULER 9. OPTION ===> 1 2 3
xxyy (SCHD) VARY ----------------------
ACTIVE - Start a CA-Scheduler NJE Session INACTIVE - End a CA-Scheduler NJE Session 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 more information. Use option 2, INACTIVE, to stop a VTAM session. See 4.3.23.2, Vary Inactive Command on page 4-185 for more information. Use option 3, VRM, to make a TYPE=SIMPLE virtual resource active or inactive. See 4.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 Active command starts a VTAM session for NJE. The batch utility is CAJUCMD0. The batch command is VARY ACT.
------------------- CA-SCHEDULER 9. COMMAND ===> Node: ID . . .
xxyy (SCHD) VARY ACTIVE ------------------
(Leave blank to start all sessions)
Enter END to exit.
The fields are: ID The name of the VTAM session to be started. If ID is left blank, all sessions not currently active are started. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ID Default: 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. COMMAND ===> Node: ID . . . Options: Close . .
xxyy (SCHD) VARY INACTIVE -----------------
(Leave blank to end all sessions)
Enter END to exit.
The fields are: ID The name of the VTAM session to be stopped. If ID is left blank, all sessions are stopped. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ID Default: All sessions Close If YES, the local VTAM ACB is closed. Size/Type: YES or NO Required: No Batch Keyword: CLOSE Default: 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 command makes a virtual resource ACTIVE or INACTIVE. The virtual resource must be defined as TYPE=SIMPLE.
-------------------- CA-SCHEDULER 9. COMMAND ===> Resource: Name . . . . Status . . .
xxyy (SCHD) VARY VRM --------------------
(Resource name) (Active or Inactive)
Enter END to exit.
The fields are: Name The name of the virtual resource being made active or inactive. The resource must be defined as TYPE=SIMPLE. Size/Type: 1 to 30 alphanumeric characters Required: Yes Batch Keyword: Resource Status The desired state of the virtual resource. Valid values are ACTIVE and INACTIVE. Size/Type: ACTIVE or INACTIVE Required: Yes Batch 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. COMMAND ===> Enter CA-Scheduler command or number ===>
xxyy (SCHD) COMMANDS --------------------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. Commands that 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 of Simulate commands: HOLD RELEASE REQUEST RERUN RUN The last 10 unique commands are saved in the fields labeled 0 to 9. You may retrieve the 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 may use 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. OPTION ===> 1 2 3 4 5 6 7 8 9 A SCHEDULES JOBS USER IDS STATION RESOURCES CALENDARS DATETABLE DOCUMENTATION FLOWS VRM Maintain Maintain Maintain Maintain Maintain Maintain Maintain Maintain Maintain Maintain
xxyy (SCHD) DATABASE --------------------
Schedule Definitions Job Definitions Users Stations Resources Calendars Date Tables Documentation Flows for Critical Path Manager 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 are sometimes called job sets. Every job must belong to a schedule. Before a job can be considered to be a part of a given day's workload, the schedule must be in that day's workload. 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 the operating system, tasks processed by a Unicenter TNG on a non-OS/390 platform, or manual tasks required either before or after a CPU job. See 5.2, Jobs on page 5-26 for 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 IDs may or may not be required, depending on the CAIJGEN installation option SECURTY. 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 to 99. Station 40 is the CPU station. Stations less than 40 are called pre-CPU, and stations after 40 are post-CPU. Stations only need to be defined for simulation and forecast 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 job initiators. Resources only need to be defined for simulation and forecast reports. See 5.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 given schedule or job should be included in a given day's workload. Date tables are much more 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 when processing periods (months) begin and end, if not on the first and last day of the month. Multiple periods may be defined, called accounting periods. A minimum of three date tables are required: one for the year just past, the current year, and the next year. 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 a job. 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 the Critical Path Monitor (CPM) system. See 5.9, Flows on page 5-110 for more information. 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). A schedule must be included in a given day's workload before any of the jobs in the schedule are considered for that day.
-------------------- CA-SCHEDULER 9. OPTION ===> Schedule . . . 1 2 3 4 5 6 7 DIRECTORY DISPLAY ALTER DEFINE DELETE COPY ANALYZE -
xxyy (SCHD) SCHEDULES -------------------
List of Schedules View an Existing Schedule Alter an Existing Schedule Create a New Schedule Remove an Existing Schedule Copy an Existing Schedule Verify an Existing Schedule
Enter END to Exit.
Use option 1, DIRECTORY, to display a scrollable list of schedules. You may put a partial schedule name in the Schedule field to limit the display, or leave the field blank to list all schedules. From the list you may Select (display), Edit, Delete, and Copy schedules. Use option 2, DISPLAY, to view a specific schedule. You must enter the schedule to display in the Schedule field. Use option 3, ALTER, to edit a specific schedule. You must enter the schedule to alter in the Schedule field. Use option 4, DEFINE, to create a new schedule. You must enter the schedule to define in the Schedule field. Use option 5, DELETE, to remove a specific schedule. You must enter the schedule to delete in the Schedule field. If you have requested the Delete Confirmation option (see Chapter 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 the Schedule 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. COMMAND ===> Schedule -------$ $$ $GEMDEMO ABNDTEST ABTEST ASCHD BADSCHD BIGSCHD BUD1 CA#TEST1 CAJ7 CHARLIE CHAS1 CHRIS CIDAY CIDUAL1 CIDUAL2 DALSCHD1 DATASCHD AutoSel ------NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO Jobs ---3 2 1 1 2 4 8 1 1 1 1 1 1 xxyy (SCHD) SCHEDULES Time -------15:4 :3 13:5 :29 15:4 : 9 Userid -------USER1 3 USER1 3 USER1 3 USER1 3 USER1 3 USER1 3 USER1 3 USER1 3 USER1 3 USER1 3 USER1 3 USER2 2 USER2 2 USER3 1 USER2 2 USER1 3 USER1 3 USER1 3 USER1 3 ROW 1 TO 19 OF 5 SCROLL ===> CSR
Date ---------2 2 2 2/12/19 3/ 1/21 2/12/ 6
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
2 2 2 2
2/12/ 6 2/12/1 3/ 1/17 3/ 1/17
15:55:18 15: 2:47 9:5 :13 1 :41:35
Each schedule is displayed on a single row. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. CA-Scheduler only reads the first 50 schedules before displaying the list. As you scroll down, more rows are 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 date and time of that change is displayed. Schedules that were last updated prior to Version 9.0 show blank date and time. If the schedule was defined and modified only in batch prior to Version 7.4, the user ID field may be blank. Select a schedule by entering a letter to the left of the schedule. Enter: S to select a schedule for viewing E to edit (alter) a schedule C to copy this schedule to a new name D to delete the schedule A to analyze the schedule and its jobs J 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. OPTION ===> Schedule . . . 1 2
xxyy (SCHD) SCHEDULE --------------------
DEFINITION - Schedule Definition CRITERIA - Schedule Selection and Predecessors
Enter END to exit.
Use option 1, DEFINITION, to view or edit the schedule definition. See the next topic for 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 PF8 to scroll up and down through the panels. To save your changes and exit, use PF3. To exit without saving your changes, enter CAN on the command line. The batch utility to use for maintaining schedules is CAJUTIL0. The batch commands for maintaining schedules are: Alter (Edit) Copy Define Delete Display (view) ALTER Sxx N/A DEFINE Sxx DELETE SCHEDULE LIST SCHEDULE
The "Sxx" above varies from panel to panel below.
------------------ CA-SCHEDULER 9. COMMAND ===> Name . . . Scheduling: Auto Selection . . NO Backlog . . . . . YES Execution: Execution Node . . . . Execution Sysid . . . . Job Defaults: Library Type . . Insert CA-11 . . Stage JCL . . . Ins Sched Enviro . . . .
xxyy (SCHD) SCHEDULE BASE -----------------
Skip . . . . . Date Table . .
JCL DDname . JES Class . JES Priority Sched Enviro
. . . .
. . . .
. . A . .
The batch command object for this panel is SBR. You may jump to this panel from other schedule detail panels by using one of the following jump commands: TOP SBR BASE
5-6 Online Guide
5.1 Schedules
The fields are: Name The name of the schedule being manipulated. This field may not be modified. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Auto Selection Determines if the schedule, and all of its jobs, should be considered during autoscan for inclusion in the current day's workload. Size/Type: NO or YES Required: Yes Batch Keyword: AUtosel Default: NO Skip A number that completes the following sentence: This schedule should be excluded from the current workload the next n number of times that it would have normally been selected. Skip is used only if Auto Selection is set to Yes. Size/Type: 1 to 3 numeric from 0 to 999 Required: Yes Batch Keyword: SKIP Default: 0 Backlog Backlog determines what CA-Scheduler should do if the schedule has not completed by the next autoscan, and the schedule should be in the next day's workload. YES Allows the old schedule to complete before the new schedule is brought in. NO Causes the remaining jobs in the schedule to be canceled, and the new schedule is brought in. Required: Yes Batch Keyword: Backlog Default: YES Date Table The name of an alternate date table to use in resolving the schedule's criteria. This date table is also used to resolve all of the criteria for this schedule's jobs. A default date table is defined in CAIJGEN. Size/Type: 1 to 7 alphanumeric characters Required: No Batch Keyword: DAtetabl Default: The value in CAIJGEN DATETAB
5.1 Schedules
Execution Node In a JES NJE environment, this is the default JES node where the jobs in this schedule will execute. If left blank, the default is the local JES node. Individual jobs in this schedule may override this default. A value of *REMOTE indicates that the jobs in this schedule are not OS/390 jobs but run on a non-OS/390 platform controlled by Unicenter TNG. Note: Values other than *REMOTE are ignored if the CAIJGEN option NJE is set 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 through CAIJNET) Required: No Batch Keyword: NOde Default: Local JES node Execution Sysid In a JES NJE environment, this is the default JES sysid at the JES node in Execution Node where the jobs in this schedule will run. Individual jobs in this schedule may override this default. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: NODESys Library Type The 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: DRIVER CA-Scheduler generates one line of JCL for Driver to expand. JOBDOC CA-Jobdoc LIBRN CA-Librarian PANV CA-Panvalet PDS Partitioned data set RDRQ Jobs are manually submitted outside of CA-Scheduler with a TYPRUN=HOLD on the job statement. CA-Scheduler releases the job and tracks it as if the job was submitted by CA-Scheduler. See "Performance Considerations" in the Systems Programmer Guide for performance implications.
5-8 Online Guide
5.1 Schedules
USERLIB The access method is provided by a site-written exit program. See "User Exits and APIs" in the Systems Programmer Guide for more information. TESTLIB CA-Scheduler submits a dummy job (based on the skeleton in member CAJUTSTB of the PDS allocated to ddname JCLMASTR). The dummy job may execute for a specified number of seconds, end with a specific return code, or abend, based on parameters defined at the job level. See the field Test Parm on page 5-38. ROSCOE CA-Roscoe Required: No Batch Keyword: Libtype Default: Value on CAIJGEN LIBTYPE JCL DDname For Library Type of PDS, the default ddname of the partitioned data set containing the JCL of the jobs in this schedule. Individual jobs may override this value. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: DDname Default: JCLMASTR Insert CA-11 If Yes, all of the CPU jobs in this schedule are submitted with the CA-11 RMS step 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 NO Required: No Batch Keyword: INSrrms Default: Value of CAIJGEN option INSRRMS JES Class A default JES class for all of the jobs in this schedule. Individual jobs may override this value. Note: This value is used only for simulation. Size/Type: 1 alphanumeric character Required: No Batch Keyword: Class Default: A
5.1 Schedules
Stage JCL If YES, CPU jobs in this schedule have their JCL written to the CA-Scheduler active workload when the schedule starts. When the jobs are submitted to JES, the JCL is read from the active workload. This allows operators to modify the JCL prior 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 NO Required: No Batch Keyword: STAGe Default: NO JES Priority A default JES priority for all of the jobs in this schedule. Individual jobs may override this value. Note: This value is used only for simulation. Size/Type: 1 to 2 numeric characters from 1 to 15 Required: No Batch Keyword: PRTy Ins Sched Enviro Controls the automatic insertion of a Workload Manager scheduling environment name in the jobs that belong to this schedule. If not specified, the insert option is taken from the global options (CAS9 CAIJGEN). The scheduling environment to be inserted into the JCL is taken from the Scheduling Environment field below, or from the global options if blank, and may be overridden on the job definition. Size/Type: YES, NO, or blank Required: No Batch Keyword: INSRSenv Default: Blank (use global option) Sched Enviro The name of a Workload Manager scheduling environment that should be inserted into the JCL of jobs that belong to this schedule. The value is only inserted if the Insert Sched Enviro field above is YES (or defaults to YES). If the Scheduling Environment is blank, the global option (CAS9 CAIJGEN) value is used. Size/Type: 1- to 16-alphanumeric characters Required: No Batch Keyword: SCHENV Default: Blank (use global option) Press PF8 for the next panel.
5-10 Online Guide
5.1 Schedules
------------------ CA-SCHEDULER 9. COMMAND ===> Name . . . Times: Early Start . . . Must Start . . . Must End . . . . Maximum Execution Average Time . . . . . . . . . . . .
xxyy (SCHD) SCHEDULE BASE -----------------
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. You may jump to this panel from other schedule detail panels by using one of the following jump commands: TIMes The fields are: Early Start The 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 the schedule starts. The value is in the format of ddhhmm, where dd is the number of autoscans that the schedule should wait, and hhmm is the time to start. You do not need to enter leading zeros. Note: This is the earliest that the schedule may start. If it has predecessors that are still unresolved, the schedule may start after this time. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: Erlytime Default: 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. The value is in the format of ddhhmm, where dd is the number of autoscans that the schedule should wait, and hhmm is the time to start. You do not need to enter leading zeros. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: MUsttime Default: 0 (Never considered late)
| |
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. The value is in the format of ddhhmm, where dd is the number of autoscans that the schedule should wait, and hhmm is the time to start. You do not need to enter leading zeros. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: DEadline Default: 0 (Never considered late) Maximum Execution If 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. The value is in the format of ddhhmm, where dd is the number of autoscans that the schedule should wait, and hhmm is the time to start. You do not need to enter leading zeros. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: Maxtime Default: 0 (Never considered late) Average Time An estimate of the duration of the schedule. This value is used only in simulation if the schedule has never been executed. The value is in the format of ddhhmm, where dd is the number of autoscans that the schedule should wait, and hhmm is the time to start. You do not need to enter leading zeros. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: AVgtime Default: 0
| |
5-12 Online Guide
5.1 Schedules
Continue on bad jobs Enter YES if the schedule's successors should be allowed to run even if the schedule is not complete due to one or more failed or abended jobs. If this field is YES, the schedule's successors will be posted if one of the following is true for every 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|NO Required: No Batch Keyword: CONTinue Default: 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 CAIJGEN SPRTY 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 99 Required: No Batch Keyword: SPrty Default: 0 - the value on CAIJGEN option SPRTY Use Simulation Time If YES, the start time as calculated by simulation overrides the early start time entered above. Size/Type: NO or YES Required: No Batch Keyword: USESim Default: NO Userids Used by CA-Scheduler internal security. If entered, and a user of type general or supervisor accesses this schedule, then the user's ID must be in the list. If the list is 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 to eight times Required: No Batch Keyword: Userids=(value,value,..) Press PF8 for the next panel.
5.1 Schedules
---------------- CA-SCHEDULER 9. COMMAND ===> Name . . . External Security: User id . . . Group id . .
xxyy (SCHD) SCHEDULE SECURITY ---------------
The batch command object for this panel is SSI. You may jump to this panel from other schedule detail panels by using one of the following jump commands: SSI SECurity The fields are: User ID The user ID to be associated with jobs in this schedule when they are submitted to JES. Individual jobs may override this value. Note: The user ID in the submitted job is determined by the order of the CAIJGEN option SUBUID. The value JSI corresponds to this field. The CAIJGEN option SECURTY must be set to YES, and the CAIJ$SEC option for the specific library type (access method) must be YES before a user ID is inserted into the JCL. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Userid Group ID The group ID to be associated with jobs in this schedule when they are submitted to JES. Individual jobs may override this value. Note: The group ID in the submitted job is determined by the order of the CAIJGEN option SUBUID. The value JSI corresponds to this field. The CAIJGEN option SECURTY must be set to YES, and the CAIJ$SEC option for the specific library type (access method) must be YES before a groupid is inserted into the JCL.
5-14 Online Guide
5.1 Schedules
Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Groupid Press PF8 for the next panel.
---------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Userid to Notify for: All Events . . . . . Schedule Start . . . Schedule End . . . . Schedule Late . . . Schedule Skipped . . . . . . .
xxyy (SCHD) SCHEDULE MESSAGES ---------------
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
The batch command object for this panel is SMR. You may jump to this panel from other schedule detail panels by using one of the following jump commands: SMR MESsages MSG The fields are: All Events A list of zero to four user IDs or OPERxxyy values to which messages should be sent when the schedule starts, becomes late, and ends. See below for more information. Size/Type: 1 to 8 alphanumeric character value specified from zero to four times Required: No Batch Keyword: Msg=(value,value,..)
5.1 Schedules
Schedule Start A list of zero to four user IDs or OPERxxyy values to which messages should be sent when the schedule starts. See below for more information. Size/Type: 1 to 8 alphanumeric character value specified from zero to four times Required: No Batch Keyword: Startmsg=(value,value,..) Schedule End A list of zero to four user IDs or OPERxxyy values to which messages should be sent when the schedule ends. See below for more information. Size/Type: 1 to 8 alphanumeric character value specified from zero to four times Required: No Batch Keyword: Endmsg=(value,value,..) Schedule Late A list of zero to four user IDs or OPERxxyy values to which messages should be sent when the schedule becomes late. See below for more information. Size/Type: 1 to 8 alphanumeric character value specified from zero to four times Required: No Batch Keyword: Latemsg=(value,value,..) Schedule Skipped A list of zero to four user IDs or OPERxxyy values to which messages should be sent 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 times Required: No Batch Keyword: SKIPmsg=(value,value,..) Messages to users are not TSO SEND messages. They are stored in the CA-Scheduler active workload and must be retrieved manually by the user. Messages are not kept indefinitely--see the CAIJGEN option MSGHOLD for more information. | Messages are stored in the database when the value is MAILBOX, and may 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 of appropriate route codes and descriptor codes for your site. The CAIJGEN options STRMSG, ENDMSG, LATMSG, and SKPMSG specify locations to which all start, end, and late messages should be sent. Normally these include MAILBOX. All messages are sent both to the CAIJGEN locations and to the locations entered here. Press PF8 for the next panel.
5-16 Online Guide
5.1 Schedules
-------------- CA-SCHEDULER 9. 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 . . . . . . . . . . . . . . . . . . . .
xxyy (SCHD) SCHEDULE REASON CODES -------------
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
. . . . . . . .
The batch command object for this panel is SRC. You may jump to this panel from other schedule detail panels by using one of the following jump commands: SRC AVErage AVG EARLY ERLY The fields are: Average Times, Reasons 01 to 16 Allows an override of the user-specified average time based on the selection reason 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 from zero to sixteen times Required: No Batch Keyword: AVGxx where xx is 01 to 16 Early Start Times, Reasons 01 to 16 Allows an override of the early start time entered earlier based on the selection reason 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 from zero to sixteen times Required: No Batch 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 to justify 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 of parentheses changes the selection reason code. Press PF8 for the next panel.
-------------- CA-SCHEDULER 9. 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 .
The batch command object for this panel is SRC. You may jump to this panel from other schedule detail panels by using one of the following jump commands: MUSTStrt MUSTEnd
5-18 Online Guide
5.1 Schedules
The fields are: Must Start Times, Reasons 01 to 16 Allows an override of the must start time entered earlier based on the selection reason 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 from zero to sixteen times Required: No Batch Keyword: MUSTxx where xx is 01 to 16 Must End Times, Reasons 01 to 16 Allows an override of the must complete time entered earlier based on the selection reason 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 from zero to sixteen times Required: No Batch Keyword: DEADxx where xx is 01 to 16 The selection reason code reflects what part of the schedule's criteria was used to justify 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 of parentheses changes the selection reason code. Press PF8 for the next panel.
5.1 Schedules
-------------- CA-SCHEDULER 9. COMMAND ===> Name . . . A Maximum Execution 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. You may jump to this panel from other schedule detail panels by using one of the following jump commands: MAX The fields are: Maximum Execution, Reasons 01 to 16 Allows an override of the maximum execution time entered earlier based on the selection reason 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 from zero to sixteen times Required: No Batch Keyword: MAXxx where xx is 01 to 16 The selection reason code reflects what part of the schedule's criteria was used to justify 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 of parentheses changes the selection reason code. Press PF8 for the next panel.
5-20 Online Guide
5.1 Schedules
-------------- CA-SCHEDULER 9. COMMAND ===> Name . . . A Information: Description . . . Comment . . . . . Exit Parm . . . . Form . . . . . . Quantity . . . . Notify . . . . . Responsibility. . Verify . . . . . NO Specification . .
xxyy (SCHD) SCHEDULE INFORMATION --------------
The batch command object for this panel is SIR. You may jump to this panel from other schedule detail panels by using one of the following jump commands: SIR INFO The fields on this panel are only used for documentation or simulation. The fields are: Description A description of this job. Size/Type: 1 to 40 alphanumeric characters Required: No Batch Keyword: Desc Comment A comment that appears next to the schedule name on some reports. Size/Type: 1 to 30 alphanumeric characters Required: No Batch Keyword: Comment Exit Parm A string passed to the simulation exit when this schedule is processed. Size/Type: 1 to 16 alphanumeric characters Required: No Batch Keyword: EXitparm
5.1 Schedules
Form Identify a form that is associated with the standard jobs in this schedule. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Form Quantity Indicate how much input or output is expected for this schedule. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Quantity Notify Name a person or group to be notified in connection with this job or schedule. Size/Type: 1 to 12 alphanumeric characters Required: No Batch Keyword: NOtify Responsibility Name the person or group responsible for this schedule. Size/Type: 1 to 12 alphanumeric characters Required: No Batch Keyword: Resp Verify Indicate whether this schedule requires special verification. This is for reporting purposes only. Size/Type: YES or NO Required: No Batch Keyword: Verify Default: NO Specification Give specification data associated with this schedule. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: SPec Press PF8 for the next panel.
5-22 Online Guide
5.1 Schedules
-------------- CA-SCHEDULER 9. COMMAND ===> Name . . . A Destinations: 1 to 4 . . . 5 to 8 . . . Deliverables: 1 to 2 . . 3 to 4 . . 5 to 6 . . 7 to 8 . . . . . . . . . .
xxyy (SCHD) SCHEDULE INFORMATION --------------
. . . . . . . . . . . .
. . . .
The batch command object for this panel is SIR. You may jump to this panel from other schedule detail panels by using one of the following jump commands: BOTtom The fields on this panel are only used for documentation or simulation. The fields are: Destinations Give up to eight destinations for the output from the jobs in this schedule. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: DESTx where x is 1 to 8 Deliverables Give up to eight delivery specifications for the jobs in this schedule. Size/Type: 1 to 16 alphanumeric characters specified from zero to eight times Required: No Batch 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 BROWSE service. 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/PDF EDIT service. A NOTE line indicates the calendar name in use, if any. If you need to change the calendar name, enter CAL xxx on the command line, where xxx is the new calendar 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.
//STEP1 EXEC CAJUTIL //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. OPTION ===> Copy schedule to schedule xxyy (SCHD) COPY SCHEDULE -----------------
Enter END to exit.
The schedule you selected from the directory is listed in the Copy schedule field. Enter the 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, or post-CPU tasks. A CPU job has JCL and executes on a JES initiator, or may be a command that executes on a non-OS/390 system. A pre-CPU job is a manual task that must be completed before the CPU job executes, such as making temporary changes to the job's JCL. A post-CPU job is a manual task that cannot be started until after the CPU job completes, such as printing and delivering reports. Option 2 of the CA-Scheduler Database menu displays the Jobs menu.
---------------------- CA-SCHEDULER 9. OPTION ===> Job . . . . Job Number. Station . . Schedule. . 1 2 3 4 5 6 7 8 . . . . -
xxyy (SCHD) JOBS ----------------------
DIRECTORY DISPLAY ALTER DEFINE DELETE COPY ANALYZE SYNTAX
List of Jobs View an Existing Job Alter an Existing Job Create a New Job Remove an Existing Job Copy an Existing Job Verify an Existing Job 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 a partial job name in the Job field or a partial schedule name in the Schedule field to limit the display. The Job Number and Station fields are ignored. From the list you may 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 Delete Confirmation option (see Chapter 3, Options), then a panel is displayed asking you to 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. COMMAND ===> Job -------$$ $GEMJOB1 $GEMJOB2 $GEMRMT $GEMXXX1 ABEND ABND 1 ABND 2 ALL ASDF ASDF1 BACKOUT BIGJOB BIGJOB2 BILLING CAJ7 1 CAJ7 2 CAJ7 3 CAJ7 4 JNO --1 1 1 1 88 1 1 1 1 1 1 1 1 1 1 1 1 1 1 Station ------4 4 4 4 99 4 4 4 4 4 4 4 4 4 4 4 4 4 4 Schedule -------$$ $GEMDEMO $GEMDEMO $GEMDEMO $GEMXXX1 BADSCHD ABNDTEST ABNDTEST XE87 TONY ASDF BACKOUT BIGSCHD BIGSCHD BILLING CAJ7 CAJ7 CAJ7 CAJ7 xxyy (SCHD) JOBS -Sysid ----Date ---------2 3/ 4/ 9 ROW 1 TO 19 OF 5 SCROLL ===> CSR Userid -------USER1 3 USER1 3 USER1 3 USER1 3 USERB 1 USER3 1 USER1 3 USER1 3 USER1 3 USER3 1 USER1 USER3 USER1 USER1 USER1 USERD USER1 USER1 3 1 3 3 3 2 3 3
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Time -------8:25:47
3/ 2/18
1 :37:29
2 2 2
3/ 2/27 3/ 1/22 3/ 4/ 2
12:19:39 9:32: 1 13:39:57
Each job is displayed on a single row. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. CA-Scheduler only reads the first 50 jobs before displaying the list. As you scroll down, more rows are automatically 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 and time of that change is displayed. Jobs that were last updated prior to Version 9.0 show blank date and time. If the job was defined and modified in batch only prior to Version 7.4, the user ID field 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 viewing E to edit (alter) a job C to copy this job to a new name D to delete the job A to analyze the job X 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. OPTION ===> Job . . . . Job Number. Station . . Schedule. . 1 2 3 4 5 . . 1 . 4 . -
xxyy (SCHD) JOB ----------------------
DEFINITION CRITERIA JOB STEPS DRIVER VRM
Job Definition Job Selection Criteria Job Step Definitions Parms for Driver Jobs Virtual Resources
Enter END to Exit.
Use option 1, DEFINITION, to view or edit the job definition. See the next topic for more information. Use option 2, CRITERIA, to edit or browse the job's criteria. See 5.2.2.2, Job Criteria 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, Job Steps on page 5-58 for more information. Use option 4, DRIVER, to view or edit Driver parms for jobs with a Library Type of DRIVER. 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. See 5.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 to scroll up and down through the panels. To save your changes and exit, use PF3. To exit without saving your changes, enter CAN on the command line. The batch utility to use for maintaining jobs is CAJUTIL0. The batch commands for maintaining jobs are: Alter (Edit) Copy Define Delete Display (View) ALTER Jxx N/A DEFINE Jxx DELETE JOB LIST JOB
The Jxx above varies from panel to panel below.
-------------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Selection: Backlog . . . . Times: Early Start . . . Must Start . . . Must End . . . . Maximum Execution Average Time . . . . . . . . . . . . Number . .
xxyy (SCHD) JOB BASE -------------------Station . . Skip . . . . Schedule . .
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 the following jump commands: TOP JBR BASE TIMes BACKlog
5.2 Jobs
The fields are: Name The name of the job being manipulated. This field may not be modified after the job is defined. For CPU jobs, this name must match the name on the JCL JOB statement. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job being manipulated. Up to 99 separate instances of the job may be defined by varying the number from 01 to 99. This field may not be modified after the job has been defined. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JNo Default: 01 Station The station of the job being manipulated. The station determines if the job is CPU, pre-CPU, or post-CPU. Station 40 jobs are CPU jobs. Jobs with stations less than 40 are pre-CPU, and greater than 40 are post-CPU. Station 39 is reserved for staged JCL setup. Station 60 is reserved for report printing. All pre-CPU jobs must be complete before the CPU job may start, and the CPU job must be complete before the post-CPU jobs may start. This field may not be modified after the job has been defined. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: STation Default: 40 Schedule The 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 be considered for that workload. The same job name, number, and station may be defined 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 must exist before the job may be defined. This field may not be modified after the job has been defined. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Schedule
5-30 Online Guide
5.2 Jobs
Backlog Determines what action CA-Scheduler should take if the job has not completed by the next autoscan and the job is scheduled to run again. YES indicates that the job should be retained until it (and the rest of its schedule) has completed. NO indicates that the job should be canceled (if not currently executing) and the next day's copy made available. Blank causes the schedule's Backlog option to be used. Size/Type: YES/NO/blank Required: No Batch Keyword: Backlog Default: Value of schedule's Backlog field Skip A number that completes the following sentence: This job should be excluded from the current workload the next n number of times that it would have normally been selected. Skip is used only if the schedule has Auto Select set to Yes. Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: SKIP Default: 0 Early Start The earliest time this job may start after being added to the workload. The job may not start before the schedule starts. The value is in the format of ddhhmm, where dd is the number of autoscans that the job should wait, and hhmm is the time to start. Leading zeros do not need to be entered. Note: This is the earliest that the job may start. If it has predecessors that are still unresolved, the job may start after this time. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: Erlytime Default: 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 that the job should wait, and hhmm is the time. Leading zeros do not need to be entered. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: MUsttime Default: 0 (Never considered late)
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. The value is in the format of ddhhmm, where dd is the number of autoscans that the job should wait, and hhmm is the time. Leading zeros do not need to be entered. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: DEadline Default: 0 (Never considered late) Maximum Execution If 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. The value is in the format of ddhhmm, where dd is the number of autoscans that the job should wait, and hhmm is the time. Leading zeros do not need to be entered. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: Maxtime Default: 0 (Never considered late) Average Time An estimate of the duration of the job. This value is used only in simulation if the job has never been executed. The value is in the format of ddhhmm, where dd is the number of autoscans that the job should wait, and hhmm is the time. Leading zeros do not need to be entered. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: AVgtime Default: 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 the schedule, to find work. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JPrty Default: 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. COMMAND ===> Name . . . Number . .
xxyy (SCHD) CPU JOB BASE -----------------Station . . Schedule . .
JCL: Library Type . . . . JCL DDname . . . . . Member Name . . . . Submission: Local Execution Sysid . Remote Execution Node . Remote Execution Sysid Insert Sched Enviro . . Scheduling Environment. . . . . .
Member Prefix . . .
The batch command object for this panel is JBR. You may jump to this panel from other job definition panels by using one of the following jump commands: JCL SUBmit The fields are: Library Type The access method to use in retrieving the JCL for this job. Valid values are: DRIVER CA-Scheduler generates one line of JCL for Driver to expand. JOBDOC CA-Jobdoc LIBRN CA-Librarian PANV CA-Panvalet PDS Partitioned data set
5.2 Jobs
RDRQ Jobs are manually submitted outside of CA-Scheduler with a TYPRUN=HOLD on the job statement. CA-Scheduler releases the job and tracks it as if the job was submitted by CA-Scheduler. See "Performance Considerations" in the Systems Programmer Guide for performance implications. USERLIB The access method is provided by a site-written exit program. See "User Exits and APIs" in the Systems Programmer Guide for more information. TESTLIB CA-Scheduler submits a dummy job (based on the skeleton in member CAJUTSTB of the PDS allocated to ddname JCLMASTR). The dummy job may execute for a specified number of seconds, end with a specific return code, or abend, based on parms defined at the job level. See the field Test Parm on page 5-38. ROSCOE CA-Roscoe Required: No Batch Keyword: Libtype Default: Value on schedule's Library Type field JCL DDname For Library Type of PDS, the ddname of the partitioned data set containing the job's JCL. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: DDname Default: Value on schedule's JCL DDname field Member Prefix For Library Type of PANV (CA-Panvalet), the first portion of the member name in the CA-Panvalet library. The Member Prefix and Member Name fields are combined and the first 10 characters used as the member name. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: MBrsubid Default: Blanks
5-34 Online Guide
5.2 Jobs
Member Name The 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 to CA-Scheduler. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: LIBMemb Default: Job name Local Execution Sysid The system ID (SMF ID) on which this job must execute. If the CAIJGEN installation option INSRSYS is YES, CA-Scheduler modifies the job's JCL during submission to include this system ID. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: SYsid Default: Blanks (Any local system ID) Remote Execution Node The JES NJE node name where the job should execute. If the CAIJGEN installation option INSROUT is YES, CA-Scheduler modifies the job's JCL during submission to include this node ID. Alternatively, the value may be *REMOTE to indicate that the job executes on a non-OS/390 system running Unicenter TNG. See Chapter 11, Remote Scheduling on page 11-1 for more information. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: NOde Default: Blank (Local node) Remote Execution Sysid The system ID (SMF ID) on which the job must execute at a remote JES NJE node. If the CAIJGEN installation option INSRSYS is YES, CA-Scheduler modifies the job's JCL during submission to include this system ID. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: NODESys Default: Blank (Any system ID) Insert Sched Enviro Controls the automatic insertion of a Workload Manager scheduling environment name. If not specified, the insert option is taken from the schedule. The scheduling environment to be inserted into the JCL is taken from the Scheduling Environment field below, or from the schedule if blank. Size/Type: YES, NO, or blank Required: No Batch Keyword: INSRSenv Default: Blank (use schedule's value)
5.2 Jobs
Scheduling Environment The name of a Workload Manager scheduling environment that should be inserted into this job's JCL during submission. The value is only inserted if the Insert Sched Enviro field above is YES (or defaults to YES). If the Scheduling Environment is blank, the schedule's value is used. Size/Type: 1- to 16-alphanumeric characters Required: No Batch Keyword: SCHENV Default: Blank (use schedule's value) Press PF8 for the next panel. It is displayed only for CPU jobs (station 40).
------------------ CA-SCHEDULER 9. COMMAND ===> Name . . . Failures: Fail Oper . Fail Code . Abend Option Fail Option Options: Insert CA-11 Stage JCL . Memo . . . . Test Parm . . . . . . . . . . . . . . . . . Number . .
xxyy (SCHD) CPU JOB BASE -----------------Station . . Schedule . .
Interrupt . . . . . NO
The batch command object for this panel is JBR. You may jump to this panel from other job definition panels by using one of the following jump commands: FAILures OPTions MEMO Fail Oper A Boolean operator used in determining if the job ended with an unacceptable return 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). Size/Type: 2 alphanumeric characters Required: No Batch Keyword: FAILOper Default: GE
5-36 Online Guide
5.2 Jobs
Fail Code A number that is compared to the job's highest return code using the Fail Oper to determine if the job ended with an unacceptable return code. The following equation 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 Fail Oper of GE and a Fail Code of 1, making zero the only acceptable return code for the job. Size/Type: 1 to 4 numeric characters Required: No Batch Keyword: Failcode Default: 0 (zero) No condition code test is done Abend Option Determines what action to take if the job abends. Valid values are: ABORT Do not let successors run. CONT Allow successors to run as if the job ended successfully. BACKOUT Submit another job, whose name is built based on the CAIJGEN option BACKOUT. schedule Run the specified schedule. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Abend Default: ABORT Fail Option Determines what action to take if the job ends with an unacceptable return code. Valid values are: ABORT Do not let successors run. CONT Allow successors to run as if the job ended successfully. BACKOUT Submit another job, whose name is built based on the CAIJGEN option BACKOUT. schedule Run the specified schedule. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FAILEd
5.2 Jobs
Default:
ABORT
Insert CA-11 Controls the automatic insertion of the CA-11 RMS. Size/Type: YES|NO Required: No Batch Keyword: INSrrms Default: Value of the schedule's Insert CA-11 field Interrupt Indicates whether a CPU job is to be interrupted for operator intervention before it is posted as complete. Valid options are: NO This job is not to be interrupted. It is to be posted as complete as soon as it completes successfully. This is the default. YES This job is to be interrupted. The job's status is shown as Interrupted instead of Completed even though it ends successfully. An interrupted job can be run again if necessary using the RERUN or SUBMIT commands. Successors to this job are not posted as satisfied until this job is ended manually using the COMPLETE command. Size/Type: NO|YES Required: NO Batch Keyword: INTERUPT Default: NO Stage JCL If Stage JCL is set to YES, the job's JCL is copied into the CA-Scheduler active workload and submitted from there. Size/Type: YES|NO Required: No Batch Keyword: STAGe Default: Value of schedule's Stage JCL field Memo CA-Scheduler displays the value of the Memo field as a WTOR (Write To Operator with Reply) at the beginning of the job. A manual reply by the operator is required before the job may execute. Size/Type: 1 to 60 alphanumeric characters Required: No Batch Keyword: MEmo Test Parm For Library Type of TESTLIB, the Test Parm determines how long the job executes and how it ends. One or more of the following may be specified: T=nnnn Number of seconds to execute
5-38 Online Guide
5.2 Jobs
F=nnnn Normal return code to generate A=nnnn Abend code to generate (user abend) If multiple options are specified, separate them with commas. Size/Type: 1 to 20 alphanumeric characters Required: No Batch Keyword: TEstparm Default: 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 than 40).
---------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Number . .
xxyy (SCHD) NON-CPU JOB BASE ---------------Station . . Schedule . .
Non-CPU Options: Automatic Start . . NO
The batch command object for this panel is JBR. The field is: Automatic Start If set to YES, the non-CPU job starts as soon as any Early Start time and predecessors are satisfied. Otherwise, the job waits for manual Start Job command. Size/Type: YES|NO Required: No Batch Keyword: AUtostrt Default: NO Press PF8 for the next panel.
5.2 Jobs
-------------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Number . .
xxyy (SCHD) JOB BASE -------------------Station . . Schedule . .
Simulation: JES Class . . . . . . . JES Priority . . . . . Use Simulation Times . . NO Documentation: Display Key . . . Display Time . .
The batch command object for this panel is JBR. You may jump to this panel from other job definition panels by using one of the following jump commands: SIM DOC The fields are: JES Class The value SIMULATE should use in determining which simulation initiator the job should use. The value is not used outside of simulation. Size/Type: 1 alphanumeric character Required: No Batch Keyword: Class Default: A Jes Priority The value SIMULATE should use in determining when a job should start in the simulation. If multiple jobs are available to start, jobs with high JES Priority values are started first. The value is not used outside of simulation. Size/Type: 1 to 2 numeric characters from 0 to 15 Required: No Batch Keyword: Prty Display Key A key of documentation to display on the OS/390 console for this job. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Dispkey
5-40 Online Guide
5.2 Jobs
Display Time The time to display the documentation referred to by Display Key on the OS/390 console. The value is in the format of ddhhmm, where dd is the number of autoscans that the job should wait, and hhmm is the time to start. Leading zeros do not need to be entered. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: DISPTime Default: 0 (Display documentation immediately) Press PF8 for the next panel.
------------------ CA-SCHEDULER 9. COMMAND ===> Name . . . External Security: User id . . . Group id . . Number . .
xxyy (SCHD) JOB SECURITY -----------------Station . . Schedule . .
The batch command object for this panel is JSI. You may jump to this panel from other job definition panels by using one of the following jump commands: JSI SECurity The fields are: User ID The 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 the CAIJGEN option SUBUID. The value JSI corresponds to this field. The CAIJGEN option SECURTY must be set to YES, and the CAIJ$SEC option for the specific library type (access method) must be YES before a user ID is inserted into the JCL.
5.2 Jobs
Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Userid Default: Value of the schedule's User ID Group ID The 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 the CAIJGEN option SUBUID. The value JSI corresponds to this field. The CAIJGEN option SECURTY must be set to YES, and the CAIJ$SEC option for the specific library type (access method) must be YES before a groupid is inserted into the JCL. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Groupid Default: Value of the schedule's Groupid Press PF8 for the next panel.
------------------ CA-SCHEDULER 9. COMMAND ===> Name . . . Separate Job Resource . Job List . . Number . . Execution: . . . . . .
xxyy (SCHD) JOB RESOURCE -----------------Station . . Schedule . .
. . . .
. . . .
. . . .
The batch command object for this panel is JRR. You may jump to this panel from other job definition panels by using one of the following jump commands: JRR SEPjob SEPdsn
5-42 Online Guide
5.2 Jobs
The fields are: Resource The job must "own" this resource name before CA-Scheduler submits it. If two or more jobs have the same resource name specified, only one at a time may be submitted. Size/Type: 1 to 44 alphanumeric characters Required: No Batch Keyword: SEPDsn Job List Specific job names or job name masks that may not be submitted when this job is submitted. If any job that matches an entry in the list is submitted when CA-Scheduler is ready to submit this job, this job is not submitted. The entries may use masking characters. A question mark ('?') represents any character, but only of length one. An asterisk ('*') represents any character, of any length (including zero). Question marks and asterisks may be combined. Mask ABCD AB?D AB*D ABC* AB?D* Matches ABCD ABCD, ABXD ABCD, ABXXD, ABD ABC, ABCD, ABCDE ABCD, ABCDEFG Doesn't Match ABCDE ABD ABCDE ABDC ABDEF
Note: If the CAIJGEN option MCPU is set to YES, the use of masking in the Job List may cause severe performance problems. See the topic Performance Considerations for Separate Job List in the Systems Programmer Guide. Size/Type: 1 to 8 alphanumeric characters specified from one to eight times Required: No Batch Keyword: SEPJob=(name,name,...) Press PF8 for the next panel.
5.2 Jobs
------------------ CA-SCHEDULER 9. COMMAND ===> Name . . . Number . . / / / / / /
xxyy (SCHD) JOB RESOURCE -----------------Station . . . . . . . . . . . . . . . . . . . . (ddhhmm) (ddhhmm) Schedule . . / / / / / /
Simulation Resources: Disk Type/Count . . . Dasd EXCPs . . . . . Tape Type/Count . . . Tape EXCPs . . . . . Unit Type/Count . . . Unit EXCPs . . . . . Maximum CPU Time . . Route Delay . . . . .
The batch command object for this panel is JRR. The fields are: Dasd Type/Count The number of up to four different types of DASD required by this job. This information is used only by simulation. Size/Type: 1 to 8 alphanumeric characters, 1 to 3 numeric characters Required: No Batch Keyword: DASDnn=(type,count) where nn is 01 to 04 Dasd EXCPs The number of DASD I/Os done by this job. This information is used only by simulation. Size/Type: 1 to 8 numeric characters Required: No Batch Keyword: DExcps Tape Type/Count The number of up to four different types of tape drives required by this job. This information is used only by simulation. Size/Type: 1 to 8 alphanumeric characters, 1 to 3 numeric characters Required: No Batch Keyword: TAPEnn=(type,count) where nn is 01 to 04 Tape EXCPs The number of tape I/Os done by this job. This information is used only by simulation. Size/Type: 1 to 8 numeric characters Required: No Batch Keyword: TExcps
5-44 Online Guide
5.2 Jobs
Unit Type/Count The number of up to four different types of other units required by this job. This information is used only by simulation. Size/Type: 1 to 8 alphanumeric characters, 1 to 3 numeric characters Required: No Batch Keyword: UNITnn=(type,count) where nn is 01 to 04 Unit EXCPs The number of other unit I/Os done by this job. This information is used only by simulation. Size/Type: 1 to 8 numeric characters Required: No Batch Keyword: UExcps Maximum CPU Time The execution duration of the job for simulation reports. This number, in ddhhmm format, overrides the average execution time. This information is used only by simulation. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: Cputime Route Delay The amount of time it takes to route a job from one system (or NJE node) to another and back. Used by simulation to more accurately reflect the time from submission to job completion. This information is used only by simulation. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: Rdt Press PF8 for the next panel.
5.2 Jobs
------------------ CA-SCHEDULER 9. COMMAND ===> Name . . . Userid to Notify All Events . . Job Start . . Job Fail . . . Job Abend . . Job Interrupt Job End . . . Job Purge . . Job Late . . . Job Skipped . for: . . . . . . . . . . . . . . . . . . Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xxyy (SCHD) JOB MESSAGES -----------------Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
The batch command object for this panel is JMR. You may jump to this panel from other job definition panels by using one of the following jump commands: JMR MSG MESsages The fields are: All Events A list of user IDs or OPERxxyy values to which messages should be sent when the job starts, fails, abends, completes, is purged, or becomes late. See below for more information. Size/Type: 1 to 8 alphanumeric characters specified zero to four times Required: No Batch Keyword: Msg=(user,user,...) Job Start A list of user IDs or OPERxxyy values to which messages should be sent when the job starts. See below for more information. Size/Type: 1 to 8 alphanumeric characters specified zero to four times Required: No Batch Keyword: STARtmsg=(user,user,...)
5-46 Online Guide
5.2 Jobs
Job Fail A list of user IDs or OPERxxyy values to which messages should be sent when the job fails (bad return code, JCL error, submit fail). See below for more information. Size/Type: 1 to 8 alphanumeric characters specified zero to four times Required: No Batch Keyword: Failmsg=(user,user,...) Job Abend A list of user IDs or OPERxxyy values to which messages should be sent when the job abends. See below for more information. Size/Type: 1 to 8 alphanumeric characters specified zero to four times Required: No Batch Keyword: Abendmsg=(user,user,...) Job Interrupt A list of user IDs or OPERxxyy values to which messages should be sent when the job completes but has Interrupt set to Yes. See below for more information. Size/Type: 1 to 8 alphanumeric characters specified zero to four times Required: No Batch Keyword: Intermsg=(user,user,...) Job End A list of user IDs or OPERxxyy values to which messages should be sent when the job completes. See below for more information. Size/Type: 1 to 8 alphanumeric characters specified zero to four times Required: No Batch Keyword: Endmsg=(user,user,...) Job Purge A list of user IDs or OPERxxyy values to which messages should be sent when the job output is removed from JES. See below for more information. Size/Type: 1 to 8 alphanumeric characters specified zero to four times Required: No Batch Keyword: Purgemsg=(user,user,...) Job Late A list of user IDs or OPERxxyy values to which messages should be sent when the job is marked late. See below for more information. Size/Type: 1 to 8 alphanumeric characters specified zero to four times Required: No Batch Keyword: Latemsg=(user,user,...) Job Skipped A list of zero to four user IDs or OPERxxyy values to which messages should be sent when the job is skipped at autoscan. See below for more information. Size/Type: 1 to 8 alphanumeric characters specified zero to four times Required: No Batch Keyword: SKIPmsg=(user,user,...)
5.2 Jobs
Messages to users are not TSO SEND messages. They are stored in the CA-Scheduler active workload and must be retrieved manually by the user. Messages are not kept indefinitely--see the CAIJGEN option MSGHOLD for more information. | Messages are stored in the database when the value is MAILBOX, and may 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 of appropriate route codes and descriptor codes for your site. 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 include MAILBOX. All messages are sent both to the CAIJGEN locations and to the locations entered here. Press PF8 for the next panel.
---------------- CA-SCHEDULER 9. 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 . . . . Number . . . . . . . . . . . . . . . . . . . . . . . . . .
xxyy (SCHD) JOB REASON CODES ---------------Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule . . . . . . . . . . . . . . . . . . . . . . . . . .
The batch command object for this panel is JRC. You may jump to this panel from other job definition panels by using one of the following jump commands: JRC AVG AVErage EARLY ERLY
5-48 Online Guide
5.2 Jobs
The fields are: Average Times, Reasons 01 to 16 Allows an override of the user-specified average time based on the selection reason 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 ddhhmm Required: No Batch Keyword: AVGxx where xx is 01 to 16 Early Start Times, Reasons 01 to 16 Allows an override of the early start time based on the selection reason 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 ddhhmm Required: No Batch Keyword: ERLYxx where xx is 01 to 16 The selection reason code reflects what part of the job's criteria was used to justify 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 of parentheses changes the selection reason code. Press PF8 for the next panel.
---------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Must Start Times: Reasons 1 to 4 Reasons 5 to 8 Reasons 9 to 12 Reasons 13 to 16 . . . . Number . . . . . . . . . . . . . . . . . . . . . . . . . .
xxyy (SCHD) JOB REASON CODES ---------------Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Schedule . . . . . . . . . . . . . . . . . . . . . . . . . .
Must End Times: Reasons 1 to 4 . Reasons 5 to 8 . Reasons 9 to 12 . Reasons 13 to 16 .
5.2 Jobs
The batch command object for this panel is JRC. You may jump to this panel from other job definition panels by using one of the following jump commands: MUSTStrt MUSTEnd STARt The fields are: Must Start Times, Reasons 01 to 16 Allows an override of the must start time based on the selection reason 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 ddhhmm Required: No Batch Keyword: MUSTxx where xx is 01 to 16 Must End Times, Reasons 01 to 16 Allows an override of the must end time based on the selection reason 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 ddhhmm Required: No Batch Keyword: DEADxx where xx is 01 to 16 The selection reason code reflects what part of the job's criteria was used to justify 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 of parentheses changes the selection reason code. Press PF8 for the next panel.
5-50 Online Guide
5.2 Jobs
---------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Number . . . . . . . . . .
xxyy (SCHD) JOB REASON CODES ---------------Station . . . . . . . . . . . . . . . . . . Schedule . . . . . . . . . . . . . .
Maximum Execution 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. You may jump to this panel from other job definition panels by using one of the following jump commands: MAX The fields are: Maximum Execution Times, Reasons 01 to 16 Allows an override of the maximum execution time based on the selection reason 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 ddhhmm Required: No Batch Keyword: MAXxx where xx is 01 to 16 The selection reason code reflects what part of the job's criteria was used to justify 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 of parentheses changes the selection reason code. Press PF8 for the next panel.
5.2 Jobs
----------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Inform JES Nodes: Node . . . . . . Number . . . . . .
xxyy (SCHD) JOB NODE INFORM ---------------Station . . . . . . . . . . Schedule . .
The batch command object for this panel is JNR. You may jump to this panel from other job definition panels by using one of the following jump commands: JNR NODEs The fields are: Node Up 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 change where the job executes, only who is told about the job. Schedules and jobs at the specified 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 times Required: No Batch Keyword: Inform=(nodename,nodename,...) Press PF8 for the next panel.
5-52 Online Guide
5.2 Jobs
----------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Information: Description . . . Comment . . . . . Exit Parm . . . . Form . . . . . . Quantity . . . . Notify . . . . . Responsibility. . Verify . . . . . NO Specification . . Number . .
xxyy (SCHD) JOB INFORMATION ---------------Station . . Schedule . .
The batch command object for this panel is JIR. You may jump to this panel from other job definition panels by using one of the following jump commands: JIR INFO The fields on this panel are only used for documentation or simulation. The fields are: Description A description of the job. Size/Type: 1 to 40 alphanumeric characters Required: No Batch Keyword: Desc Comment A comment that appears next to the job name on some reports. Size/Type: 1 to 30 alphanumeric characters Required: No Batch Keyword: Comment Exit Parm A string passed to the simulation exit when this job is processed. Size/Type: 1 to 16 alphanumeric characters Required: No Batch Keyword: EXitparm
5.2 Jobs
Form Identify a form that is associated with the standard jobs in this schedule. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Form Quantity Indicate how much input or output is expected for this schedule. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Quantity Notify Name a person or group to be notified in connection with this job or schedule. Size/Type: 1 to 12 alphanumeric characters Required: No Batch Keyword: NOtify Responsibility Name the person or group responsible for this schedule. Size/Type: 1 to 12 alphanumeric characters Required: No Batch Keyword: Resp Verify Indicate whether this schedule requires special verification. This is for reporting purposes only. Size/Type: YES or NO Required: No Batch Keyword: Verify Default: NO Specification Give specification data associated with this schedule. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: SPec Press PF8 for the next panel.
5-54 Online Guide
5.2 Jobs
----------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Destinations: 1 to 4 . . . 5 to 8 . . . Deliverables: 1 to 2 . . 3 to 4 . . 5 to 6 . . 7 to 8 . . . . . . Number . . . . . .
xxyy (SCHD) JOB INFORMATION ---------------Station . . . . . . . . . . . . . . . . . . . . . . Schedule . . . . . .
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. The fields on this panel are only used for documentation or simulation. The fields are: Destinations Give up to eight destinations for the output from the jobs in this schedule. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: DESTx where x is 1 to 8 Deliverables Give up to eight delivery specifications for the jobs in this schedule. Size/Type: 1 to 16 alphanumeric characters specified from zero to eight times Required: No Batch Keyword: DELx where x is 1 to 8 Simulation Route Stations Use this to notify a defined route station when this job is going to be selected for processing in simulation. List up to eight route stations that are to receive a report when this job is selected as part of a forecast. Route stations are defined by specifying two letters in the station record instead of two numbers. Size/Type: 1 to 2 alphanumeric characters specified from zero to eight times Required: No Batch Keyword: ROut=(id,id,...) Press PF8 for the next panel.
5.2 Jobs
--------------- CA-SCHEDULER 9. COMMAND ===> Name . . . XPLATJ Number . .
xxyy (SCHD) JOB CROSS-PLATFORM --------------1 Station . . 4 Schedule . . XPLATS
Cross-Platform information: Node . . . . Domain . . . User id . . Password . . Verify . . . SU Flag . .
The batch command object for this panel is JBR. You may jump to this panel from other job definition panels by using one of the following jump commands: 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 provide information for executing this job on another platform. The fields are: Node The CCI name of the destination machine for this job. Size/Type: 0 to 8 alphanumeric characters Required: No Batch Keyword: XPNode Domain The Microsoft Windows NT domain in which the user ID is defined. The field may be case-sensitive. Size/Type: 0 to 15 alphanumeric characters Required: No Batch Keyword: XPDomain
5-56 Online Guide
5.2 Jobs
User id The user ID with which the job should be initiated. The field may be case-sensitive. Size/Type: 0 to 32 alphanumeric characters Required: No Batch 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 BROWSE service. 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 EDIT service. A NOTE line indicates the calendar name in use, if any. If you need to change the calendar name, enter CAL xxx on the command line, where xxx is the new calendar 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 return codes 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 a Fail Oper of GE and a Fail Code of 1 on the job. If, however, nine steps must end with 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's Fail 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 not have a specific JSR uses the default JSR.
-------------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Procstep -------Number . . Stepname -------Type ----
xxyy (SCHD) JOB STEPS ------------------SCROLL ===> PAGE Station . . Schedule . . More ----
Failoper Failcode -------- -------BOTTOM OF DATA
The batch command object for this panel is JSR. The fields on the panel are: Name The name of the job whose Job Step entries are being manipulated. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JNo Default: 01 Station The station of the job. This number is always 40 because only CPU jobs have steps. It is displayed to be consistent with other job displays.
5-58 Online Guide
5.2 Jobs
Schedule The schedule that owns the job. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Schedule Procstep The step name outside of the proc used to identify the step. If the step does not have a procedure, then the Procstep is blank. Once a Job Step entry is defined, the Procstep name may not be changed. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: PROCstep Stepname The 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 for this job. The Procstep must be blank for the default JSR. Required: Yes Batch Keyword: STEP Type Determines if the Failoper/Failcode pairs indicate good return codes or bad. Size/Type: BAD or GOOD Required: Yes Batch Keyword: TYpe Failoper A Boolean operator used in determining if the step ended with an unacceptable return 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: Yes Batch Keyword: FAILOper Failcode A number that is compared to the step's return code using the Failoper to determine if the step ended with an unacceptable return code. The following equation is evaluated: return-code Failoper Failcode If the statement is true, then the Type is used to determine if the step ended successfully or not. If Type is BAD, the step failed; if Type is GOOD, the step was successful.
5.2 Jobs
If the statement is false, then the opposite of Type is used to determine if the step ended successfully or not. Size/Type: 1 to 4 numeric characters Required: Yes Batch 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 on the command line. Job Step Entry: The following panel is displayed when adding or copying a Job Step entry.
-------------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Step Definition: Procedure step name Step name . . . . . If true, step is . Fail operator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Number . . . . . . . . . . . . . . . . . . BAD . . . . . . . . . .
xxyy (SCHD) JOB STEPS ------------------Station . . Schedule . . procedure) PGM=) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
(Outside of the (Step name with (Good or Bad) 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 name The name of the step outside of a PROC. This field may be blank if the step does not use a PROC. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: PROCstep
5-60 Online Guide
5.2 Jobs
Step name The 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 for this job. The Procstep must be blank for the default JSR. Required: Yes Batch Keyword: STEP If true, step is Determines if the Failoper/Failcode pairs indicate good return codes or bad. Size/Type: BAD or GOOD Required: Yes Batch Keyword: TYpe Fail oper A Boolean operator, used with the Return code, to determine if the step's return code is unacceptable. Size/Type: 2 alphanumeric characters Required: Yes Batch Keyword: FAILOper Return code A number compared to the step's return code to determine if the return code is unacceptable. 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 ended successfully. If Type is BAD, then the step failed; if Type is GOOD, the step was successful. If the statement is false, then the opposite of Type is used to determine whether the step ended successfully. Size/Type: 1 to 4 numeric characters Required: Yes Batch 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 Library Type of DRIVER.
------------------ CA-SCHEDULER 9. COMMAND ===> Name . . . DRVTEST Number . . 1
xxyy (SCHD) DRIVER PARMS -----------------SCROLL ===> PAGE Station . . 4 Schedule . . DRVTEST
Variable Type / Value ----------- ---------------------------------------------------------------BOTTOM OF DATA
The fields are: Variable The name of the variable parameter to be passed to the Driver PROC. The variable name may be one to seven characters long with an optional array subscript in parentheses (that is, VARNAME(1) ). Type The value NORMAL or RESTART. Variable parameters with a type of NORMAL are passed when jobs are automatically submitted or submitted due to the FORCE or SUBMIT commands. Variable parameters with a type of RESTART are passed when 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 an existing 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 the changes. If the command is successful, it is not shown. If it fails, the output is displayed 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 be submitted.
----------------------- CA-SCHEDULER 9. COMMAND ===> Virtual resources required by job RT8 1
xxyy (SCHD) VRM ----- Row 1 to 3 of 3 SCROLL ===> CSR 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: Resource The name of the virtual resource associated with this job. Type The type of the virtual resource. Status The state that the virtual resource must have before the job may be submitted. Free Specifies if the virtual resource should be released at job end even if the job abends or fails. Select a job/virtual resource association by entering a letter to the left of the virtual resource. Enter: S to select the association for viewing E to edit (alter) an association D to delete an association I (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.
//STEP1 EXEC CAJUTIL //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.
//STEP1 EXEC CAJUTIL //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.
//STEP1 //SYSIN DEFINE JSR DEFINE JSR //
EXEC CAJUTIL DD N=ABC,S=XYZ,STEP=STEP1,FAILOPER=GE,FAILCODE=1 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.
//STEP1 EXEC CAJUTIL //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. COMMAND ===> Copy job number station schedule To job number station schedule xxyy (SCHD) COPY JOB --------------------
Enter END to exit.
CA-Scheduler lists the job you selected in the Copy Job fields. Enter the new job information in the To job fields. All of the job is copied, including criteria. After you have copied the job, you may alter 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 the CA-Scheduler online system and the amount of authority they have. Your site may or may not require user definitions. If the installation CAIJGEN option SECURTY is set to EXTERNAL, CA-Scheduler does not require and ignores user definitions. If CAIJGEN SECURTY is set to NO or YES, CA-Scheduler requires user definitions. Option 3 of the CA-Scheduler Database menu displays the User IDs menu.
-------------------- CA-SCHEDULER 9. OPTION ===> User ID . . . 1 2 3 4 5 6 DIRECTORY DISPLAY ALTER DEFINE DELETE COPY -
xxyy (SCHD) USER IDS --------------------
List of User IDs View an Existing User ID Alter an Existing User ID Create a New User ID Remove an Existing User ID Copy an Existing User ID
Enter END to Exit.
Use option 1, DIRECTORY, to display a scrollable list of users defined to CA-Scheduler. You may enter a partial user ID in the User ID field to limit the display. 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 Delete Confirmation option (see Chapter 3, Options), CA-Scheduler displays a panel asking you 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. COMMAND ===> Userid -------LEEFR 1 PUBJO 1 SMIJA 2 Type ---------GENERAL MANAGER SUPERVISOR xxyy (SCHD) USER IDS ROW 1 TO 3 OF 3 SCROLL ===> CSR
_ _ _
Description ---------------------------------------FRED LEE JOHN Q. PUBLIC JANE SMITH BOTTOM OF DATA
Each user ID is displayed on a single row. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. CA-Scheduler only reads the first 50 user IDs before displaying the list. As you scroll down, more rows are 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 viewing E to edit (alter) a user ID C to copy a user ID D 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 and exit, 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 commands for maintaining user IDs are: Alter (Edit) Copy Define Delete Display (View) ALTER USERID N/A DEFINE USERID DELETE USERID LIST USERID
-------------------- CA-SCHEDULER 9. COMMAND ===> User id . . . Passwords: Read . . . Write . . . Other: Type . . . . . . Description . . Stations . . . .
xxyy (SCHD) USER IDS --------------------
(General, Supervisor, Manager) . . . . . . . . . . . . . .
Enter END to exit.
The fields are: User id The name of the user ID being manipulated. This field may not be modified after the user ID is defined. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name
5-68 Online Guide
5.3 User IDs
Read A password that the user must specify when accessing CA-Scheduler online only if 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 characters Required: Yes Batch Keyword: Readpass Write A password that the user must specify when accessing CA-Scheduler online only if CAIJGEN SECURTY is set to NO. If CAIJGEN SECURTY is set to NO and the user does not enter the correct write password, the user is allowed access to CA-Scheduler online in a read-only mode. If CAIJGEN SECURTY is set to YES and the user ID is defined without a write password, then the user is allowed access to CA-Scheduler online in a read-only mode. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Writpass Type The authority level of the user ID. The value may be General, Supervisor, or Manager. See Table 5-1 on page 5-70 for more information. Size/Type: 1 to 10 alphanumeric characters Required: Yes Batch Keyword: Type=G|S|M Description A description or the name of the user whose user ID is being defined. Size/Type: 1 to 40 alphanumeric characters Required: No Batch Keyword: Desc Stations If one or more stations is specified, General and Supervisor user IDs cannot act on jobs at stations not in the list. Size/Type: 2 numeric characters specified from zero to eight times Required: No Batch Keyword: Connect=(nn,nn,...)
5.3 User IDs
The authorizations granted at each Type are:

Table 5-1 (Page 1 of 2). Authorization Types
General A 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 is authorized, within schedules that this user ID is authorized to control Display and alter staged JCL for jobs, while connected to the JCL setup station (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 user ID Display the status of schedules that this user ID is authorized to control Issue tracking commands to control schedules for which this user ID is authorized Issue tracking commands to control jobs, at stations for which this user ID is authorized, within schedules that this user ID is authorized to control Supervisor A user with Supervisor authority can: Maintain the passwords for this user ID record Define jobs and schedules Maintain all schedule records Maintain all job records defined for stations for which this user ID is authorized Display and alter staged JCL for jobs while connected to the JCL setup station (39) Define online documentation Connect only to stations listed on the CONNECT parameter for this user ID Display the status of all schedules Issue tracking commands to control all schedules Issue tracking commands to control all jobs at stations for which this user ID is authorized
5-70 Online Guide
5.3 User IDs
Table
5-1 (Page 2 of 2). Authorization Types
Manager A user with Manager authority can: Define new user ID records Define new calendars and date tables Define jobs and schedules 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 editor protection characters) for all jobs while connected to the JCL setup station (39) Define online documentation 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 SET commands
5.3 User IDs

5.3.3.1 Example 1
Define a user ID as a supervisor.
//STEP1 EXEC CAJUTIL //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.
//STEP1 EXEC CAJUTIL //SYSIN DD ALTER USERID NAME=PUBJOHN,TYPE=M //
5.3.4 Copying a User ID

------------------- CA-SCHEDULER 9. OPTION ===> Copy user USER1 3 to user xxyy (SCHD) COPY USERID ------------------
Enter END to exit.
CA-Scheduler lists the user ID you selected in the Copy user field. Enter the new user ID 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 to define stations for any other reason. A CA-Scheduler station is a place where work is done. Station 40 is called the CPU station and is used for jobs that execute on a system. Stations less than 40 are manual tasks 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 as delivery of a printed report. Option 4 of the CA-Scheduler Database menu displays the Station menu.
-------------------- CA-SCHEDULER 9. OPTION ===> Station . . . 1 2 3 4 5 6 DIRECTORY DISPLAY ALTER DEFINE DELETE COPY -
xxyy (SCHD) STATIONS --------------------
List of Stations View an Existing Station Alter an Existing Station Create a New Station Remove an Existing Station Copy an Existing Station
Enter END to Exit.
Use option 1, DIRECTORY, to display a scrollable list of stations defined to CA-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 Delete Confirmation option (See Chapter 3, Options), CA-Scheduler displays a panel asking you 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. COMMAND ===> ID -39 4 6 Name -------STAGE CPU OUTPUT xxyy (SCHD) STATIONS -ROW 1 TO 3 OF 3 SCROLL ===> CSR
_ _ _
Description ---------------------------------------STAGED JCL CPU STATION OUTPUT DESTINATION BOTTOM OF DATA
Each station is displayed on a single row. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. CA-Scheduler only reads the first 50 stations before displaying the list. As you scroll down, more rows are automatically 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 viewing E to edit (alter) a station C to copy a station D 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 and exit, 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 commands for maintaining stations are: Alter (Edit) Copy Define Delete Display (View) ALTER STATION N/A DEFINE STATION DELETE STATION LIST STATION
--------------------- CA-SCHEDULER 9. COMMAND ===> Station . . . Details: Name . . . Title . . Description Time Zone . . . . . . . . .
xxyy (SCHD) STATION --------------------
Enter END to exit.
The fields are: Station The number of the station being manipulated. This field may not be modified after the station is defined. Size/Type: 2 numeric characters Required: Yes Batch Keyword: Id
5.4 Stations
Name A short name for the station that is displayed on the simulation Station report. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Name Title The title is displayed on the simulation Station report. Size/Type: 1 to 60 alphanumeric characters Required: No Batch Keyword: TITLe Description Information about the station, displayed only by the List Station command. Size/Type: 1 to 40 alphanumeric characters Required: No Batch Keyword: Desc
5-76 Online Guide
5.4 Stations

5.4.3.1 Example 1: Define a CPU station
//STEP1 EXEC CAJUTIL //SYSIN DD DEFINE STATION ID=4 ,NAME='CPU',DESC='CPU STATION' //
5.4.3.2 Example 2: Define a JCL setup station (station 39)
//STEP1 EXEC CAJUTIL //SYSIN DD DEFINE STATION ID=39,NAME='STAGE',DESC='STAGED JCL' //
5.4.4 Copying a Station

------------------ CA-SCHEDULER 9. OPTION ===> Copy station 39 to station xxyy (SCHD) COPY STATION ------------------
Enter END to exit.
CA-Scheduler lists the station you selected in the Copy station field. Enter the new station 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 to define resources for any other reason. Resources map devices such as tape drives and job initiators that must be serialized between jobs. By defining each job to CA-Scheduler with the correct number of tape drives it uses, and defining the total number of tape drives here, the CA-Scheduler SIMULATE command does not show individual jobs running until a sufficient number of tape drives are available. The same can be done with initiators, DASD devices, and any other unit. You may define DASD, tape, and units to a specific CPU in a multiple CPU environment or define as shared by all CPUs. Option 5 of the CA-Scheduler Database menu displays the Resource menu.
-------------------- CA-SCHEDULER 9. OPTION ===> Station . . . System . . . 1 2 3 4 5 DIRECTORY DISPLAY ALTER DEFINE DELETE -
xxyy (SCHD) RESOURCES ------------------
List of Resource Definitions View an Existing Resource Definition Alter an Existing Resource Definition Create a New Resource Definition Remove an Existing Resource Definition
Enter END to exit.
Use option 1, DIRECTORY, to display a scrollable list of resource definitions. From the 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 and System.
5-78 Online Guide
5.5 Resources
Use option 5, DELETE, to remove a resource definition. If you have requested the Delete Confirmation option (See Chapter 3, Options), CA-Scheduler displays a panel asking you to confirm the deletion. Otherwise, CA-Scheduler deletes the station immediately.
5.5.1 Directory
-------------------- CA-SCHEDULER 9. COMMAND ===> Station ------_ 3 _ 4 _ 4 System -----XE87 BOTTOM OF DATA Start ----End ---xxyy (SCHD) RESOURCES Route ----Class ----A ROW 1 TO 3 OF 3 SCROLL ===> CSR
Average -------
Each station's resource definition is displayed on a single row. The upper right-hand corner 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 station number. Enter: S to select a resource definition for viewing E to edit (alter) a resource definition D 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. OPTION ===> Station . . . 1 2
xxyy (SCHD) RESOURCE -------------------
Sysid/Substation . .
NON-SHARED - Resources dedicated to this Sysid/Substation 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. See 5.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 batch commands for maintaining nonshared resources are: Alter (Edit) Define Delete Display (View) ALTER RESOURCE DEFINE RESOURCE DELETE RESOURCE N/A
-------------------- CA-SCHEDULER 9. OPTION ===> Station . . . 4 1 2
xxyy (SCHD) RESOURCE -------------------
Sysid/Substation . .
DEFINITION - Times, Dasd, Tape, Unit Records INIT/UNIT - Initiators or Units
Enter END to exit.
Use option 1, DEFINITION, to maintain information about times, DASD and tape devices, and other units. Use option 2, INIT/UNIT, to maintain a list of initiators (for station 40) or units (for other than station 40). Resource Definition Screens: The resource base information is contained on several panels. Use PF7 and PF8 to scroll up and down through the panels. To save your changes and exit, use PF3. To exit without saving your changes, enter CAN on the command line.
5.5 Resources
-------------------- CA-SCHEDULER 9. COMMAND ===> Station . . . Times: Production Start Production End . Average Duration Route Delay . . . . . . . . . . . . . . . . . .
xxyy (SCHD) RESOURCE --------------------
Sysid/Substation . . (hhmm) (hhmm) (ddhhmm) (ddhhmm)
Miscellaneous: Default Class . . . . . Simulation Exit Parm . .
Enter END to exit, or DOWN for next screen.
The fields are: Station The station for which these resources may be used. Size/Type: 2 numeric characters from 1-99 Required: Yes Batch Keyword: STation Sysid/Substation The 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 to identify which devices are available on each system. Size/Type: Required: Batch Keyword: Default: 1 to 4 alphanumeric characters No SYsid Blank
Production Start The time of day, in hhmm format, that work normally begins for this station. A typical value would be the autoscan time (CAIJGEN option AUTOTIM). Size/Type: Required: Batch Keyword: Default: 4 numeric characters hhmm No PSt 0000 (midnight)
5-82 Online Guide
5.5 Resources
Production End The time of day, in hhmm format, that work normally ends for this station. A typical value would be one minute before autoscan time. Size/Type: Required: Batch Keyword: Default: 4 numeric characters hhmm No PEt 0000 (midnight)
Average Duration A length of time to be used for jobs at this station that have never executed (that is, have no history) and that do not have an Average Time specified on the job. Size/Type: Required: Batch Keyword: Default: 6 numeric characters ddhhmm No AVgtime 000000
Route Delay A length of time to be added to the start of jobs that execute at a different node. Size/Type: Required: Batch Keyword: Default: 6 numeric characters ddhhmm No Rdt 000000
Default Class A class to be used for jobs that do not have a class defined. Size/Type: 1 alphanumeric character Required: No Batch Keyword: DEFclass Simulation Exit Parm A character string that is passed to the simulation exit. See the Simulation Exit in the Systems Programmer Guide for more information. Size/Type: 1 to 16 alphanumeric characters Required: No Batch Keyword: EXitparm Press PF8 for the next screen. It is displayed only for CPU station resources (station 40).
5.5 Resources
------------------ CA-SCHEDULER 9. COMMAND ===> Station . . . Dasd: Type Dasd 1 . . Dasd 3 . . Dasd 5 . . Dasd 7 . . Dasd 9 . . Dasd 11 . . Dasd 13 . . Dasd 15 . .
xxyy (SCHD) CPU RESOURCE ------------------
Sysid/Substation . . Count Dasd Dasd Dasd Dasd Dasd Dasd Dasd Dasd . . . . 1 . 12 . 14 . 16 . 2 4 6 8 . . . . . . . . Type Count
Enter END to exit, UP for previous screen, or DOWN for next screen.
The fields are: Dasd 01 to Dasd 16 Up 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. Type The type of DASD being defined. The type must match the Disk Type on the job definition. Size/Type: Required: 1 to 8 alphanumeric characters No, unless Count entered
Count The number of the specified type of DASD available. Size/Type: Required: 1 to 3 numeric characters from 1-255 No, unless Type entered
Press PF8 for the next screen. It is displayed only for CPU station resources (station 40).
5-84 Online Guide
5.5 Resources
------------------ CA-SCHEDULER 9. COMMAND ===> Station . . . Tape: Type Tape 1 . . Tape 3 . . Tape 5 . . Tape 7 . . Tape 9 . . Tape 11 . . Tape 13 . . Tape 15 . .
xxyy (SCHD) CPU RESOURCE ------------------
Sysid/Substation . . Count Tape Tape Tape Tape Tape Tape Tape Tape . . . . 1 . 12 . 14 . 16 . 2 4 6 8 . . . . . . . . Type Count
Enter END to exit, UP for previous screen, or DOWN for next screen.
The fields are: Tape 01 to Tape 16 Up to 16 different types of tape drives may be defined, each with a type and count. The batch syntax for each is: TAPEnn=(type,count) where nn is 01 to 16. Type The type of tape drive being defined. The type must match the Tape Type on the job definition. Size/Type: Required: 1 to 8 alphanumeric characters No, unless Count entered
Count The number of the specified type of tape drive available. Size/Type: Required: 1 to 3 numeric characters from 1-255 No, unless Type entered
Press PF8 for the next screen.
5.5 Resources
-------------------- CA-SCHEDULER 9. COMMAND ===> Station . . . Unit Record: Type Unit 1 . . Unit 3 . . Unit 5 . . Unit 7 . . Unit 9 . . Unit 11 . . Unit 13 . . Unit 15 . .
xxyy (SCHD) RESOURCE --------------------
Sysid/Substation . . Count Unit Unit Unit Unit Unit Unit Unit Unit . . . . 1 . 12 . 14 . 16 . 2 4 6 8 . . . . . . . . Type Count
Enter END to exit,or UP for previous screen.
The fields are: Unit 01 to Unit 16 Up to 16 different types of unit records may be defined, each with a type and count. The batch syntax for each is: URnn=(type,count) where nn is 01 to 16. Type The type of unit record being defined. The type must match the Unit Type on the job definition. Size/Type: Required: 1 to 8 alphanumeric characters No, unless Count entered
Count The number of the specified type of unit record available. Size/Type: Required: 1 to 3 numeric characters from 1-255 No, unless Type entered
To exit and save your changes, press PF3. To exit without saving, type CAN on the command line.
5-86 Online Guide
5.5 Resources
Resource Initiator
---------------- CA-SCHEDULER 9. COMMAND ===> Station . . . 4 Number -----1 2 3 5 Header -------INIT1 INIT2 INIT3 INIT5
xxyy (SCHD) INITIATORS/UNIT
Sysid/Substation . . Classes -----------------------------------AB B B ASDF BOTTOM OF DATA
The fields are: Station The station for which the initiators are defined. Size/Type: 2 numeric characters Required: Yes Batch Keyword: STation Sysid/Substation The specific system at this station for which the initiators are defined. Size/Type: Required: Batch Keyword: Default: 1 to 4 alphanumeric characters No SYsid Blank
Number The number of the initiator. Each initiator must have a unique number from 1 to 255. Size/Type: 1 to 3 numeric characters Required: Yes Batch Keyword: INITnnn=(classes,header), where nnn is 001 to 255 Header A label to use in the simulation reports as a name for this initiator. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: see Number Classes The classes processed by this initiator. Up to 36 classes may be specified. Size/Type: 1 to 36 alphanumeric characters Required: Yes Batch Keyword: see Number
5.5 Resources
To change existing Header or Class information, simply overtype the information on the 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 the command 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 to scroll up and down through the panels. To save your changes and exit, use PF3. To exit without saving your changes, enter CAN on the command line. The batch utility to use for maintaining shared resources is CAJUTIL0. The batch commands for maintaining shared resources are: Alter (Edit) Define Delete Display (View) ALTER SHRRSR DEFINE SHRRSR DELETE SHRRSR N/A
------------------- CA-SCHEDULER 9. COMMAND ===> Station . Dasd: 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 . .
xxyy (SCHD) SHARED DASD ------------------
Type Count Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . to exit, or DOWN for next screen.
The fields are: Station The station for which the shared resource is defined. Size/Type: 2 numeric characters Required: Yes Batch Keyword: STation Dasd 01 to Dasd 16 Up 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.
5.5 Resources
Type The type of DASD being defined. Typical values are 3390 or SYSDA. Size/Type: 1 to 8 alphanumeric characters Required: No, unless Count entered Batch Keyword: See Dasd 01 to Dasd 16 Count The number of the specified type of DASD available. Size/Type: 1 to 3 numeric characters from 1-255 Required: No, unless Type entered Batch Keyword: See Dasd 01 to Dasd 16 Systems The system IDs that may use the DASD 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 times Required: No, unless Type and Count entered Batch Keyword: See Dasd 01 to Dasd 16 Press PF8 for the next panel.
------------------- CA-SCHEDULER 9. COMMAND ===> Station . Tape: 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 Enter END . .
xxyy (SCHD) SHARED TAPE ------------------
Type Count Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . to exit, UP for previous screen, or DOWN for next screen.
The fields are: Tape 01 to Tape 16 Up to sixteen different types of tape drives may be defined. Each tape drive has a type (that is, 3490 or CART), a count, and one to eight system IDs that may use it. The batch syntax is: TAPEnn=(type,count,sysid,sysid,...) where nn is 01 to 16.
5-90 Online Guide
5.5 Resources
Type The type of tape drive being defined. Typical values are 3490 or CART. Size/Type: 1 to 8 alphanumeric characters Required: No, unless Count entered Batch Keyword: See Tape 01 to Tape 16 Count The number of the specified type of tape drive available. Size/Type: 1 to 3 numeric characters from 1-255 Required: No, unless Type entered Batch Keyword: See Tape 01 to Tape 16 Systems The 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 times Required: No, unless Type and Count entered Batch Keyword: See Tape 01 to Tape 16 Press PF8 for the next panel.
------------------ CA-SCHEDULER 9. COMMAND ===> Station . Unit: 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 . .
xxyy (SCHD) SHARED UNITS ------------------
Type Count Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . to exit, or UP for previous screen.
The fields are: Unit 01 to Unit 16 Up to sixteen different types of other units may be defined. Each other unit has a type, 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
Type The type of other unit being defined. Size/Type: 1 to 8 alphanumeric characters Required: No, unless Count entered Batch Keyword: See Unit 01 to Unit 16 Count The number of the specified type of other units available. Size/Type: 1 to 3 numeric characters from 1-255 Required: No, unless Type entered Batch Keyword: See Unit 01 to Unit 16 Systems The system IDs that may use the other unit. If Type and Count are entered, at least one system must be entered. Size/Type: 1-4 alphanumeric characters specified from one to eight times Required: No, unless Type and Count entered Batch Keyword: See Unit 01 to Unit 16

5.5.3.1 Example 1
Define initiators for a specific CPU.
//STEP1 EXEC CAJUTIL //SYSIN DD DEFINE RESOURCE STATION=4 ,SYSID=SYSA,INIT INIT 2=(ABC,INIT2),INIT 3=(C,INIT3) //
1=(ABC,INIT1),
5.5.3.2 Example 2
Define tape drives for all CPUs.
//STEP1 EXEC CAJUTIL //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 the workload. A job or schedule that specifies a calendar is added to the workload every workday in the calendar. Note: Date tables are much more flexible than calendars. Consider using date tables instead of calendars. Two types of calendars exist: Normal and prototype. Prototype calendars are named PROTOnn, where nn is the last two digits of the year. Normal calendars have any other name. When a normal calendar is created, CA-Scheduler checks for the existence of a prototype calendar for that year. If it is found, the workdays in the prototype calendar may impact which days in the normal calendar are set as workdays. Prototype calendars are defined with a flag of Next, Previous, or Drop for both Weekly and Monthly calendars. When a normal calendar is being defined, and the specified day in the prototype is not a workday, the prototype flag determines what action is taken. For example, a prototype calendar might have Monday, January 1 set as a holiday (not a workday) and have a weekly flag of Next. When a normal, weekly calendar is built for Mondays, January 2 would become a workday. Option 6 of the CA-Scheduler Database menu displays the Calendar menu.
-------------------- CA-SCHEDULER 9. OPTION ===> Calendar . . . . Year . . . . . . 1 2 3 4 5 6 DIRECTORY DISPLAY ALTER DEFINE DELETE COPY -
xxyy (SCHD) CALENDARS -------------------
List of Calendars View an Existing Calendar Alter an Existing Calendar Create a New Calendar Remove an Existing Calendar 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 the Delete Confirmation option (See Chapter 3, Options), CA-Scheduler displays a panel asking you to confirm the deletion. Otherwise, CA-Scheduler deletes the calendar immediately. Use option 6, COPY, to copy a calendar, creating a new one.
5.6.1 Directory
-------------------- CA-SCHEDULER 9. COMMAND ===> Name -------CAL1 DAILY FD FOUR FRI FW LD LW MON NN NNW PROTO 3 SAT SIX SUN THU TUE Year ---2 2 2 3 2 3 2 3 2 3 2 3 2 3 2 3 2 3 2 3 2 3 2 3 2 3 2 3 2 3 2 3 2 3 xxyy (SCHD) CALENDARS ROW 1 TO 19 OF 19 SCROLL ===> CSR
Description ----------------------------------------
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Each calendar is displayed on a single row. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. CA-Scheduler only reads the first 50 calendars before displaying the list. As you scroll down, more rows are 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 viewing E to edit (alter) a calendar C to copy a calendar D 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. COMMAND ===> Define Prototype Calendar: Calendar . . . . . . Year . . . . . . . . Workdays per Week . . 5
xxyy (SCHD) CALENDAR --------------------
(5, 6, 7, or
Prototype Options: Weekly Roll Option . . . DROP Monthly Roll Option . . DROP
(NEXT or PREVIOUS workday, or DROP) (NEXT or PREVIOUS workday, or DROP)
Enter END to Exit.
The fields are: Calendar The name of the prototype calendar being created. The name of all prototype calendars is PROTOnn, where nn is the last two digits of the year. Size/Type: Required: 7, of the form PROTOnn Yes
Year The year of the prototype calendar. Size/Type: Required: 4 numeric characters Yes
Workdays The number of days in a "normal" work week. Work weeks are assumed to start on Monday. A value of 5 sets all Mondays to Fridays as workdays; 6 sets all Mondays to Saturdays; and 7 makes all days workdays. Individual days may be set to workdays or not after the calendar is defined. Size/Type: Required: 1 numeric character: 0, 5, 6, or 7 Yes
5.6 Calendars
Weekly Roll Option Determines what action to take when a normal weekly calendar tries to set a workday on a day not specified as a workday in the prototype. If Drop is specified, the day in the normal calendar is not set to a workday. If Next is specified, the first workday in the prototype after the specified day is used. If Previous is specified, the first workday in the prototype before the specified day is used. Size/Type: Required: DROP, NEXT, or PREVIOUS Yes
Monthly Roll Option Determines what action to take when a normal monthly calendar tries to set a workday on a day not specified as a workday in the prototype. If Drop is specified, the day in the normal calendar is not set to a workday. If Next is specified, the first workday in the prototype after the specified day is used. If Previous is specified, the first workday in the prototype before the specified day is used. Size/Type: Required: DROP, NEXT, or PREVIOUS Yes
The following panel is displayed only when creating a new normal calendar.
-------------------- CA-SCHEDULER 9. COMMAND ===> Define Calendar: Calendar . . . . . . Year . . . . . . . . Workdays per Week . . 5
(5, 6, 7, or
Options: Type of Calendar . . . DAILY Day of Week/Month . .
(Daily, Weekly, or Monthly) (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: Calendar The name of the normal calendar being created. Size/Type: Required: 1 to 8 alphanumeric characters Yes
5-96 Online Guide
5.6 Calendars
Year The year of the normal calendar. Size/Type: Required: 4 numeric characters Yes
Workdays The number of days in a "normal" work week. Work weeks are assumed to start on Monday. A value of 5 sets all Mondays to Fridays as workdays; 6 sets all Mondays to Saturdays; and 7 makes all days workdays. Individual days may be set to workdays or not after the calendar is defined. Size/Type: Required: 1 numeric character: 0, 5, 6, or 7 Yes
Type of Calendar A normal calendar is one of three types: daily, weekly, or monthly. A daily calendar sets every day in the normal work week as a workday (see Workdays above). If a prototype calendar exists, it is copied into the daily calendar. A weekly calendar specifies a single day of each week to be a workday. A monthly calendar specifies a single day of each month to be a workday. See Day of Week/Month below. Size/Type: Required: DAILY, WEEKLY, or MONTHLY Yes
Day of Week/Month For weekly and monthly calendars, determines the day of the week or month that should be set as a workday. Some values cause the prototype roll option to be ignored. For weekly calendars, valid values are: Value SUN MON TUE WED THU FRI SAT END Means Sunday Monday Tuesday Wednesday Thursday Friday Saturday Weekend (both Saturday and Sunday) Honors prototype roll option Yes Yes Yes Yes Yes Yes Yes No
5.6 Calendars
For monthly calendars, valid values are: Value FD LD 1 - 31 FW LW 1W - 31W Size/Type: Required: Means First day of month Last day of month day of the month First Workday Last Workday Workday of the month Honors prototype roll option No No No Yes Yes Yes
FD, LD, 1-31, FW, LW, 1W-31W 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.
-------------------- CA-SCHEDULER 9. COMMAND ===> Calendar . . . . . Description . . . .
JANUARY Sunday --------4 11 18 25 . . . . Monday --------5 12 19 26 W W W W Tuesday --------6 13 2 27 W W W W
2 xx Thursday --------1 W 8 W 15 W 22 W 29 W Friday --------2 W 9 W 16 W 23 W 3 W Saturday --------3 . 1 . 17 . 24 . 31 .
Wednesday --------7 14 21 28 W W W W
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 three characters 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-98 Online Guide
5.6 Calendars
The fields are: Calendar The name of the calendar being maintained. This field may not be modified. Size/Type: Required: 1 to 8 alphanumeric characters Yes
Description May be used to describe the calendar or its purpose. Size/Type: Required: 1 to 40 alphanumeric characters No
1 to 31 The days of the month, along with their attribute. Days marked with a W are workdays. Otherwise, they are not workdays.
5.6.3 Copying a Calendar

------------------ CA-SCHEDULER 9. COMMAND ===> Copy calendar year To Calendar Year xxyy (SCHD) COPY CALENDAR -----------------
Enter END to exit.
The calendar you selected is listed in the Copy calendar fields. Enter the new calendar information in the To calendar fields.
5.7 Datetables
5.7 Datetables
CA-Scheduler date tables are used with criteria to determine when schedules and jobs should 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. OPTION ===> Datetable . . . . . Accounting Code . . Year . . . . . . . 1 2 3 4 5 6 DIRECTORY DISPLAY ALTER DEFINE DELETE COPY -
xxyy (SCHD) DATETABLES -------------------
List of Datetables View an Existing Datetable Alter an Existing Datetable Create a New Datetable Remove an Existing Datetable Copy an Existing Datetable
Enter END to Exit.
Use option 1, DIRECTORY, to display a scrollable list of date tables defined to CA-Scheduler. You may enter a partial date table name in the Date Table field to limit the 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 the Delete Confirmation option (See Chapter 3, Options), CA-Scheduler displays a panel asking you to confirm the deletion. Otherwise, CA-Scheduler deletes the date table immediately. 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. COMMAND ===> Name Code -------- ---DATETAB A DATETAB A DATETAB A DATETAB A DATETAB A DATETAB A DATETAB A DATETAB A DATETAB A DATETAB B DATETAB B DATETAB B DATETAB B DATETAB B DATETAB B DT A DT A DT A Year ---1994 1995 2 2 2 3 1998 1999 2 2 1 2 2 1993 1994 1995 2 2 2 3 1998 1993 1994 1995 xxyy (SCHD) DATETABLES ROW 1 TO 18 OF 21 SCROLL ===> CSR
Description ----------------------------------------
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Each date table is displayed on a single row. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. CA-Scheduler only reads the first 50 date tables before displaying the list. As you scroll down, more rows are 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 viewing E to edit (alter) a date table C to copy a date table D 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. COMMAND ===> Define Datetable: Datetable . . . . Accounting Code . Year . . . . . . Workdays per Week First Workday . . . . . . .
xxyy (SCHD) DATETABLE -------------------
. . . . 5 ( to 7) . MON (SUN to SAT)
Enter END to Exit.
The fields are: Datetable The name of the date table being maintained. Size/Type: Required: 1 to 7 alphanumeric characters Yes
Accounting Code The one character prefix used by criteria keywords that should reference this table. The Accounting Code must be a letter. Size/Type: Required: Default: 1 alphanumeric character No A
Year The four-digit year of this date table. Size/Type: Required: 4 numeric characters Yes
5-102 Online Guide
5.7 Datetables
Workdays per Week The number of days in a "normal" work week. Work weeks start with the day specified in the First Workday field, which defaults to Monday. A value of zero in this field does not set any days as work days. Individual days may be set to work days or not after the date table is defined. Size/Type: Required: 1 numeric character from 0 to 7 Yes
First Workday The first day in a "normal" work week. A typical work week starts on Monday and lasts for five days. To define a work week that starts on Sunday, change this field to SUN. Size/Type: Required: SUN, MON, TUE, WED, THU, FRI, or SAT 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.
-------------------- CA-SCHEDULER 9. COMMAND ===> Datetable . . . . . Description . . . . Sunday --------5 12 19 26 .... .... .... .... Monday --------6 13 2 27 WA.. WA.. WA.. WA.. Tuesday --------7 14 21 28 WA.. WA.. WA.. WA..
Accounting Code . . JANUARY 2 xx Thursday --------2 WA.. 9 WA.. 16 WA.. 23 WA.. 3 WA.. Friday --------3 WA.. 1 WA.. 17 WA.. 24 WA.. 31 WAM. Saturday --------4 .... 11 .... 18 .... 25 ....
Wednesday --------1 WA.. 8 WA.. 15 WA.. 22 WA.. 29 WA..
Legend: W... .A.. ..M. ...Y -
Workday Accounting Day Month (Period) End 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 three characters 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: Datetable The name of the date table being manipulated. This field may not be modified after the date table is defined. Size/Type: Required: 1 to 7 alphanumeric characters Yes
Accounting Code The one character prefix used by criteria keywords that should reference this table. The Accounting Code must be a letter. Size/Type: Required: Default: 1 alphanumeric character No A
Description May be used to describe the date table or its purpose. Size/Type: Required: 1 to 40 alphanumeric characters No
1 to 31 The days of the month, along with their attributes. Each day may have up to four attributes: W The day is a workday. Criteria keywords such as WDAY and WDOMx will be true. If the W attribute is not present, criteria keywords such as HDAY are true. A The day is an accounting day. Criteria keywords such as xDAY, where x is the Accounting Code, are true. Note that the attribute for the day is always A, not the value of the Accounting Code. M The day is the last day of an accounting period. This is frequently used to indicate the end of the month. Criteria keywords such as ADOMx are counted from this day. Y The day is the last day of the accounting year. Criteria keywords such as ADOYx are counted from this day.
5-104 Online Guide
5.7 Datetables
5.7.3 Copying a Date Table

----------------- CA-SCHEDULER 9. COMMAND ===> Copy datetable accounting code year To Datetable Accounting Code Year xxyy (SCHD) COPY DATETABLE -----------------
Enter END to exit.
The date table you selected is listed in the Copy date table fields. Enter the new date table 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 a job. 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 or when the job's schedule starts. See Documentation Display Key and Display Time fields on page 5-39. Option 8 of the CA-Scheduler Database menu displays the Documentation menu.
------------------ CA-SCHEDULER 9. OPTION ===> Key . . . . Job . . . . Job Number. Station . . Schedule. . 1 2 3 4 5 6 . . . . . -
xxyy (SCHD) DOCUMENTATION -----------------
DIRECTORY DISPLAY ALTER DEFINE DELETE COPY
List of Documentation Members View an Existing Documentation Member Alter an Existing Documentation Member Create a New Documentation Member Remove an Existing Documentation Member Copy an Existing Documentation Member
Enter END to Exit.
Use option 1, DIRECTORY, to display a scrollable list of documentation members defined to CA-Scheduler. From the list you may Select (display), Edit, Delete, or Copy documentation 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 have requested the Delete Confirmation option (See Chapter 3, Options), CA-Scheduler displays a panel asking you to confirm the deletion. Otherwise, CA-Scheduler deletes the 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: Key The documentation key. Every documentation member must have a key. Size/Type: Required: Job If the documentation member is to be displayed on the OS/390 console, it must be defined with the name of the job with which it is associated. Size/Type: Required: 1 to 8 alphanumeric characters No 1 to 8 alphanumeric characters Yes
Job Number The number of the associated job. Size/Type: Required: 2 numeric characters Yes, if Job is used
Station The station of the associated job. Size/Type: Required: 2 numeric characters Yes, if Job is used
Schedule The schedule of the associated job. Size/Type: Required: 1 to 8 alphanumeric characters Yes, if Job is used
5.8 Documentation
5.8.1 Directory
------------------ CA-SCHEDULER 9. COMMAND ===> Key -------$$ $$ $$$ A A AAA AB ASDF CA 7SVCT CHERICE DBT1 DOCKEY GAFRSDAY GAFRSD 1 GAFRSD 2 GLC 1 GLC 3 GLC 4 Job -------A B A A C AAA A ASDF JNO --1 1 1 1 1 1 1 St -4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 xxyy (SCHD) DOCUMENTATI Date ---------4/15/ 3 4/16/ 3 9/1 / 2 8/2 / 2 6/28/ 2 9/ 3/ 2 1 /11/ 2 5/ 9/ 2 6/28/ 2 8/22/95 8/22/95 8/19/ 2 8/22/95 8/22/95 8/22/95 8/22/95 8/22/95 8/22/95 ROW 1 TO 18 OF 47 SCROLL ===> CSR User -------USER1 3 USER1 3 USER1 3 USER1 3 USER1 3 USER1 3 USER1 3 USER1 3 USER1 3 GEM
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Schedule -------CAJ7 CAJ7 CAJ7 A B ABTEST B ASDF
CHRIS
CHRIS
Time -------8.47.1 8.13.28 15.12.31 9.12.51 7.49.53 12.39. 1 13.49. 9 14.52. 8 7.49.19 1 .55.18 1 .55.19 13.43.28 1 .55.19 1 .55.19 1 .55.19 1 .55.19 1 .55.19 1 .55.19
Each documentation member is displayed on a single row. The upper right-hand corner of 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 the list. As you scroll down, more rows are automatically added until the entire list has been built. Select a documentation member by entering a letter to the left of the key. Enter: S to select a member for viewing E to edit (alter) a member C to copy a member D to delete a member
5.8.2 Documentation Text

When defining or editing a documentation member, ISPF Edit is used. When displaying a member, ISPF Browse is used.
5-108 Online Guide
5.8 Documentation
5.8.3 Copying a Documentation Member

--------------- CA-SCHEDULER 9. COMMAND ===> Copy doc job number station schedule To doc job number station schedule xxyy (SCHD) COPY DOCUMENTATION ---------------
Enter END to exit.
The documentation member you selected is listed in the Copy doc fields. Enter the new 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 the Critical Path Monitor (CPM) system. Option 9 of the CA-Scheduler Database menu displays the Flows menu.
---------------------- CA-SCHEDULER 9. OPTION ===> Flow . . . . . 1 2 3 4 5 6 DIRECTORY DISPLAY ALTER DEFINE DELETE REFRESH -
xxyy (SCHD) FLOWS ---------------------
List of Flows View an Existing Flow Alter an Existing Flow Create a New Flow Remove an Existing Flow 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 a partial 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 Delete Confirmation option (see Chapter 3, Options), then a panel is displayed asking you to confirm the deletion. Otherwise, the flow is deleted immediately. Use option 6, REFRESH, to issue a REFRESH FLOW command to the CA-Scheduler started 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. COMMAND ===> Flow -------FLOW1 HOURLY PAYROLL From Job ----------------------FJOB1A 1 4 FLOWSCD1 PAY1 1 4 PAYROLL PAY1 1 4 PAYROLL Bottom xxyy (SCHD) FLOWS ---- Row 1 to 3 of 3 SCROLL ===> CSR To Job ----------------------FJOB1C 1 4 FLOWSCD1 OVERTIME 1 4 HOURLY PAY99 1 4 PAYCHECK of data SLA -----18 15 5
_ _ _
Each flow is displayed on a single row. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. CA-Scheduler only reads the first 50 flows before displaying the list. As you scroll down, more rows are automatically 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 viewing E to edit (alter) a flow D to delete a flow
5.9.2 Flow Definition

The same panel is used to display, edit, and define flows. To save your changes and exit, 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 for maintaining flows are: Alter (Edit) Define Delete Display (view) ALTER FLOW DEFINE FLOW DELETE FLOW LIST FLOW
Flows are also displayed when either the starting or ending jobs are listed (LIST JOB, LIST SCHEDULE).
5.9 Flows
---------------------- CA-SCHEDULER 9. COMMAND ===> Flow . . . . . Beginning of Job . . . JNO . . . Station . Schedule . End of flow: Job . . . JNO . . . Station . Schedule . flow: . . . . . . . .
xxyy (SCHD) FLOW ----------------------
Service Level Agreement . . .
(ddhhmm)
Enter END to exit.
The fields are: Flow The name of the flow being manipulated. The field may not be modified after the flow is defined. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Beginning of flow Job The starting job name for this flow. The job must exist before the flow is defined. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: FJOb Beginning of flow JNO The JNO of the starting job for this flow. Size/Type: 2 numeric characters Required: No Default: 01 Batch Keyword: FJNo Beginning of flow Station The station of the starting job for this flow. Size/Type: 2 numeric characters Required: No Default: 40 Batch Keyword: FSTation
5-112 Online Guide
5.9 Flows
Beginning of flow Schedule The schedule to which the starting job for this flow belongs. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: FSChd End of flow Job The ending job name for this flow. The job must exist before the flow is defined. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: TJOb End of flow JNO The JNO of the ending job for this flow. Size/Type: 2 numeric characters Required: No Default: 01 Batch Keyword: TJNo End of flow Station The station of the ending job for this flow. Size/Type: 2 numeric characters Required: No Default: 40 Batch Keyword: TSTation End of flow Schedule The schedule to which the ending job for this flow belongs. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: TSChd Service Level Agreement The time by which the flow must be complete. If CPM determines that the flow will 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 and hhmm is the time. Leading zeros do not need to be entered. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: Yes Batch Keyword: SLA
5.9 Flows
5.9.3 Example
Define a flow from PAY1-01 40 PAYROLL to OVERTIME-01 40 HOURLY that must 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 certain conditions are met. Virtual resources only exist in the CA-Scheduler task. A virtual resource 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. OPTION ===> Virtual Resource . . . 1 2 3 4 5 6 DIRECTORY DISPLAY ALTER DEFINE DELETE REFRESH -
xxyy (SCHD) VIRTUAL RESOURCES ---------------
List of Virtual Resources View an Existing Virtual Resource Alter an Existing Virtual Resource Create a New Virtual Resource Remove an Existing Virtual Resource 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 may enter a partial resource name in the Virtual Resource field to limit the display. From the list you may Select (display), Edit, and Delete virtual resources. You may also display 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 Delete Confirmation option (see Chapter 3, Options), a panel is displayed asking you to confirm the deletion. Otherwise, the virtual resource is deleted immediately. Use option 6, REFRESH, to issue a REFRESH VRM command to the CA-Scheduler started task. CA-Scheduler must be active for the command to work.
5.10.1 Directory
----------------------- CA-SCHEDULER 9. COMMAND ===> xxyy (SCHD) VRM ----- Row 1 to 3 of 3 SCROLL ===> CSR
_ _ _
Resource Type Count ------------------------------ ------ -----------XXX SIMPLE YYY ENQ ZZZ COUNT 5 Bottom of data
Each virtual resource is displayed on a single row. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. CA-Scheduler only 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 viewing E to edit (alter) a virtual resource D to delete a virtual resource J 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 your changes and exit, use PF3. To exit without saving your changes, enter CAN on the command line. The batch utility to use for maintaining virtual resources is CAJUTIL0. The batch commands for maintaining virtual resources are: Alter (Edit) Define DELETE Display (view) ALTER VRM DEFINE VRM DELETE VRM LIST VRM
Virtual resources are also displayed when an associated job is listed (LIST JOB, LIST SCHEDULE).
---------------- CA-SCHEDULER 9. COMMAND ===> Resource . . . . .
xxyy (SCHD) VIRTUAL RESOURCE ----------------
Resource Type . . . Maximum Count . . .
(Enq, Count, or Simple) (Only if resource type is Count)
Enter END to exit.
The fields are: Resource The name of the virtual resource being manipulated. Size/Type: 1 to 30 alphanumeric characters Required: Yes Batch Keyword: Resource
Resource Type The type of the virtual resource being manipulated. The resource type may not be changed 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 SIMPLE Required: Yes Batch Keyword: Type Maximum Count If Resource Type is set to COUNT, then the Maximum Count field contains the number of the virtual resource available. Size/Type: 1 to 10 numeric characters Required: Yes, if Resource Type = COUNT Batch Keyword: Count
5.10.2.1 Example
Define a simple virtual resource to indicate if CICS is up or down:
//stepname EXEC CAJUTIL //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 virtual resource. To display the list, enter a J next to a virtual resource on the virtual resource directory display. See 5.10.1, Directory on page 5-116.
xxyy (SCHD) VRM JOBS - Row 1 to 17 of 17 SCROLL ===> CSR
Jobs that require virtual resource XXX Name -------RESTEST2 RT3 1 RT3 2 RT3 3 RT3 4 RT3 5 RT3 6 RT8 1 RT8 2 RT8 3 RT8 4 RT8 5 RT8 6 RT8 7 RT8 8 RT8 9 RT81 JNO --1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 St -4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 4 Schedule -------RESTEST2 RESTEST3 RESTEST3 RESTEST3 RESTEST3 RESTEST3 RESTEST3 RESTEST8 RESTEST8 RESTEST8 RESTEST8 RESTEST8 RESTEST8 RESTEST8 RESTEST8 RESTEST8 RESTEST8 Status -----------ACTIVE INACTIVE INACTIVE INACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE ACTIVE Free ---NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO NO
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Each job/virtual resource association is displayed on a single row. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. CA-Scheduler only reads the first 50 job/virtual resource associations before displaying the list. As you scroll down, more rows are automatically added until the entire 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 viewing E to edit (alter) an association D to delete an association I (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. To save your changes and exit, use PF3. To exit without saving your changes, enter CAN on the command line. The batch utility to use for maintaining job/virtual resource associations is CAJUTIL0. The batch commands are: Alter (Edit) Define Delete Display ALTER JOBRES DEFINE JOBRES DELETE JOBRES LIST JOB
--------------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Virtual Resource: Resource . . . Required Status: Status . . . . . INACTIVE Termination: Release on abend/fail . . . NO Number . .
xxyy (SCHD) JOB VRM -------------------Station . . Schedule . .
(ACTIVE or INACTIVE)
Enter END to Exit.
The fields are: Name The name of the job being associated with a virtual resource. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name
5-120 Online Guide
JNO The JNO of the job being associated with a virtual resource. Size/Type: 2 numeric characters Required: No Batch Keyword: JNo Default: 01 Station The station of the job being associated with a virtual resource. Size/Type: 2 numeric characters Required: No Batch Keyword: STation Default: 40 Schedule The schedule of the job being associated with a virtual resource. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Schedule Resource The virtual resource being associated with this job. Size/Type: 1 to 30 alphanumeric characters Required: Yes Batch Keyword: Resource Required Status The label and meaning of this field varies depending on the type of the virtual resource. If the virtual resource was defined as TYPE=ENQ, then the label will read Enqueue. Valid values are SHR and EXC, indicating that the job may share the virtual resource with other jobs, or needs exclusive control of the virtual resource. Size/Type: SHR or EXC Required: Yes Batch Keyword: Enq If the virtual resource was defined as TYPE=COUNT, then the label will read Count. Valid values are any number from 1 to 9,999,999,999. No check is made to ensure that the number entered here is less than or equal to the number available on the virtual resource. Size/Type: 1 to 10 numeric characters Required: Yes Batch 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 resource must be active or inactive before the job may be submitted. Size/Type: ACTIVE or INACTIVE Required: Yes Batch Keyword: Active=YES|NO Release on abend/fail Virtual resources, once acquired by a job, are usually retained until the job completes successfully. To release the virtual resource at any job end, even if the job abends or fails, specify YES. Size/Type: YES or NO Required: No Batch Keyword: Free Default: NO
5.10.4.1 Example
Specify that a job may not be submitted unless a simple virtual resource called CICS is ACTIVE.
//stepname EXEC CAJUTIL //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 of virtual 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 virtual resources must be satisfied before the job is submitted. Virtual resources are resolved alphabetically. Each virtual resource must be obtained before the next virtual resource is 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 waiting for each virtual resource. The REFRESH VRM command must be used (or wait for an autoscan) to pick up any definition 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 exclusive control 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:
//stepname EXEC CAJUTIL //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 able to obtain the virtual resource. If job JOBE is the next job ready to be submitted, it must wait, because it can not obtain exclusive control of the virtual resource. When jobs JOBC and JOBD are ready to be submitted, they must also wait because an exclusive 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 specified indicating how many of the virtual resources are available. When a job is associated with this virtual resource, a number is specified indicating how many of the virtual resources this job requires. Consider the following example:
//stepname EXEC CAJUTIL //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 same time. JOBE, however, can only be submitted when no other job has the virtual resource. Note that the order of requests for a count type virtual resource does not matter. If JOBE 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 to JOBD.
5.10.4.5 Simple Virtual Resources

A simple virtual resource is either active or inactive. The VARY VRM command is used to switch the state from active to inactive or back.
//stepname EXEC CAJUTIL //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. OPTION ===> 1 2 3 4 5 7 8 9 1 11 12 ANALYZE ABEND AUDIT COMPLETE DATETRAN JOB AVERAGE JOB HISTORY MAILBOX OPTIONS SUCCESSOR PREDECESSOR -
xxyy (SCHD) REPORTS --------------------
Look for logical definition errors Historical job abends Audit trail of commands Historical job completions Criteria keywords for a given date Historical job durations Historical information on jobs Historical information on events CA-Scheduler installation options Job and Schedule successors Job and Schedule predecessors
Enter END to Exit.
Use option 1, ANALYZE, to inspect schedules and jobs for logical errors, such as predecessor 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 that abended. 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 that have 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 a specified 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 in CA-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 in CA-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. See 6.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 as predecessor loops (deadlocks).
--------------------- CA-SCHEDULER 9. OPTION ===> 1 2 JOB - Analyze a Job SCHEDULE - Analyze a Schedule
xxyy (SCHD) ANALYZE --------------------
Enter END to exit.
Use option 1, JOB, to inspect a specific job or jobs starting with the same prefix. See the next topic for more information. Use option 2, SCHEDULE, to inspect a specific schedule or schedules with the same prefix. All jobs in the selected schedules are also analyzed. See 6.1.2, Analyze Schedule 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 as predecessor loops (deadlocks). The batch utility to use is CAJUTIL0. The batch command is ANALYZE JOB.
------------------- CA-SCHEDULER 9. COMMAND ===> Job: Job Name . . . . Schedule . . . . Options: List . . . . . . ERR Date . . . . . .
xxyy (SCHD) ANALYZE JOB ------------------
(YES, NO, ERR, DEADLOCK) (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy)
Enter END to exit.
The fields are: Job Name The name of the job or job name prefix to be inspected. A job name prefix may be specified by following the prefix with an asterisk. All job numbers and stations for selected jobs will be analyzed. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Schedule The schedule or schedule prefix that contains the job(s) to be analyzed. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: * (All schedules)
6-4 Online Guide
6.1 Analyze
List Determines the amount of information produced by the report. The default value is determined by the Default Analyze List Type option. See Chapter 3, Options on page 3-1. Valid values are: YES All information about analyzed jobs is displayed. NO Only job names are displayed, along with any errors. ERR Only jobs with errors are displayed. DEADLOCK Only deadlocks and the deadlock path are displayed. Required: No Batch Keyword: List Default: YES Date If a date is entered, ANALYZE will emulate autoscan for that date. Deadlocks will only be reported if autoscan would have detected them. If Date is not specified, all schedules and jobs are considered selected, regardless of their individual criterias. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: Date Default: 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 also inspected. The batch utility to use is CAJUTIL0. The batch command is ANALYZE SCHEDULE.
---------------- CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule Name . . Options: List . . . . . . ERR Date . . . . . .
xxyy (SCHD) ANALYZE SCHEDULE ----------------
(YES, NO, ERR, DEADLOCK) (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy)
Enter END to exit.
The fields are: Schedule The name of the schedule or schedule prefix to be inspected. Specify a schedule prefix by following the prefix with an asterisk. CA-Scheduler analyzes all jobs in the selected schedules. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name List Determines the amount of information produced by the report. The default value is determined by the Default Analyze List Type option. See Chapter 3, Options on page 3-1. Valid values are: YES All information about analyzed schedules and jobs is displayed. NO Only schedule and job names are displayed, along with any errors.
6-6 Online Guide
6.1 Analyze
ERR Only schedules and jobs with errors are displayed. DEADLOCK Only deadlocks and the deadlock path are displayed. Required: No Batch Keyword: List Default: YES Date If you enter a date, ANALYZE emulates autoscan for that date. Deadlocks are reported only if autoscan would have detected them. If you do not specify a date, all schedules and jobs are considered selected, regardless of their individual criterias. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: Date Default: 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 ended abnormally. Do not confuse the Report Abend command with the Status Abend command, which lists abended jobs in the current workload. The batch utility to use is CAJUTIL0. The batch command is REPORT ABEND.
------------------ CA-SCHEDULER 9. COMMAND ===> Job: Job Name . . . . Schedule . . . . Options: Starting Date Starting Time Duration . . Scheduled On . . . . . . . . . . . .
xxyy (SCHD) REPORT ABEND ------------------
(mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) (hhmm) (days) (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy)
Enter END to exit.
The fields are: Job Name The 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 lists all job numbers of selected jobs. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Job Default: * (All jobs)
6-8 Online Guide
6.2 Report Abend
Schedule The name or name prefix of the schedule that contains the Job Name. Specify a name prefix by following the prefix with an asterisk. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: * (All schedules) Starting Date If entered, lists no abends occurring prior to this date. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: FROMDate or FD Default: Current autoscan date Starting Time If entered, lists no abends occurring prior to this time. Size/Type: hhmm Required: No Batch Keyword: FROMTime or FT Default: Normal autoscan time Duration If entered, lists no abends occurring at least this many days after the Starting Date. Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: FOR Default: 1 Scheduled on Lists only abended jobs selected on this date. If you specify Scheduled on, CA-Scheduler ignores Starting Date. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch 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. COMMAND ===> Options: Starting Date Starting Time Ending Date . Ending Time . Commands . . . . . . . . . . . . . . . . .
xxyy (SCHD) REPORT AUDIT ------------------
Users . . . . . . .
. . . . . . . .
(mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) (hhmm) (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) (hhmm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enter END to exit.
The fields are: Starting Date The earliest date from which commands should be displayed. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: FD Default: Today's date
6-10 Online Guide
6.3 Report Audit
Starting Time The earliest time on the Starting Date from which commands should be displayed. Size/Type: hhmm Required: No Batch Keyword: FT Default: Midnight Ending Date The latest date from which commands should be displayed. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: TD Default: Today's date Ending Time The latest time on the Ending Date from which commands should be displayed. Size/Type: hhmm Required: No Batch Keyword: TT Default: 2359 Commands If specified, only commands that match one of the sixteen commands listed are displayed. Size/Type: One to sixteen 1 to 8 alphanumeric characters Required: No Batch Keyword: CMD=(command,command,...) Default: All commands Users If specified, only commands entered by one of the sixteen users listed are displayed. Size/Type: One to sixteen 1 to 8 alphanumeric characters Required: No Batch 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 that ended normally. Do not confuse the Report Complete command with the Status Comp command, which lists completed jobs in the current workload. The batch utility to use is CAJUTIL0. The batch command is REPORT COMPLETE.
----------------- CA-SCHEDULER 9. COMMAND ===> Job: Job Name . . . . Schedule . . . . Options: Starting Date Starting Time Duration . . Scheduled On . . . . . . . . . . . .
xxyy (SCHD) REPORT COMPLETE ----------------
(mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) (hhmm) (days) (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy)
Enter END to exit.
The fields are: Job Name The name or name prefix of the job for which historical job completions you want to 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 characters Required: No Batch Keyword: Job Default: * (All jobs)
6-12 Online Guide
6.4 Report Complete
Schedule The name or name prefix of the schedule that contains the Job Name. Specify a name prefix by following the prefix with an asterisk. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: * (All schedules) Starting Date If entered, lists no completions occurring prior to this date. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: FROMDate or FD Default: Current autoscan date Starting Time If entered, lists no completions occurring prior to this time. Size/Type: hhmm Required: No Batch Keyword: FROMTime or FT Default: Normal autoscan time Duration If entered, lists no completions occurring at least this many days after the Starting Date. Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: FOR Default: 1 Scheduled on Lists only completed jobs selected on this date. If you specify Scheduled on, CA-Scheduler ignores Starting Date. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch 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. COMMAND ===> Date Table: Date Table . . . In Schedule . . In Job . . . . . Options: Starting Date . . . Duration . . . . .
xxyy (SCHD) REPORT DATETRAN ----------------
(mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) (days)
Enter END to exit.
The fields are: Date Table The name of the date table to use in generating criteria keywords. If the Date Table, In Schedule, and In Job fields are blank, CA-Scheduler uses the default Date Table (CAIJGEN DATETAB option). If you specify Date Table, CA-Scheduler ignores In Schedule and In Job. Size/Type: 1 to 7 alphanumeric characters Required: No Batch Keyword: Table Default: CAIJGEN DATETAB value
6-14 Online Guide
6.5 Report Datetran
In Schedule Use the date table specified in this schedule. If you specify Date Table, CA-Scheduler ignores In Schedule. If you specify In Schedule, CA-Scheduler ignores In Job. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: Date Table value In Job Use the date table specified on the schedule that owns this job. If you specify either Date Table or In Schedule, CA-Scheduler ignores In Job. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Job Default: Date Table or In Schedule value Starting Date The date for which criteria keywords should be generated. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: FROMDate or FD Default: Today Duration The number of days for which criteria keywords should be listed. Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: FOR Default: 1
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 on CA-Scheduler historical information. The batch utility to use is CAJUTIL0. The batch command is REPORT JOBAVG.
------------------- CA-SCHEDULER 9. COMMAND ===> Job: Job Name . . . .
xxyy (SCHD) JOB AVERAGE ------------------
Enter END to exit.
The field is: Job Name The name or name prefix of the job for which average execution information should 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 characters Required: Yes Batch Keyword: Name Default: * (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 of jobs. The batch utility to use is CAJUTIL0. The batch command is REPORT JOBHIST.
------------------- CA-SCHEDULER 9. COMMAND ===> Job: Job Name . . . . Options: List . . . JESNUM
xxyy (SCHD) JOB HISTORY ------------------
(Jesnum or Year)
Enter END to exit.
The fields are: Job Name The name or name prefix of the jobs for which execution history should be displayed. Specify a name prefix by entering an asterisk after the prefix. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Default: * (All jobs) List Specify 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 YEAR Required: No Batch Keyword: List Default: 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. COMMAND ===> Options: Starting Date Starting Time Ending Date . Ending Time . Jobs . . . . . . . . . . . . . . . . . . .
xxyy (SCHD) REPORT MAILBOX -----------------
Schedules . . . . .
. . . . . . . .
(mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) (hhmm) (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) (hhmm) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Enter END to exit.
6-18 Online Guide
6.8 Report Mailbox
The fields are: Starting Date The earliest date for which events should be displayed. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: FROMDate or FD Default: Today Starting Time The earliest time on the Starting Date for which events should be displayed. Size/Type: hhmm Required: No Batch Keyword: FT Default: Midnight Ending Date The latest date for which events should be displayed. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: TODate or TD Default: Today Ending Time The latest time on the Ending Date for which events should be displayed. Size/Type: hhmm Required: No Batch Keyword: TT Default: 2359 Jobs If specified, only events for these sixteen jobs are displayed. Size/Type: One to sixteen 1 to 8 alphanumeric characters Required: No Batch Keyword: Job=(jobname,jobname,...) Default: All jobs Schedules If specified, only events for these sixteen schedules or for jobs in these schedules are displayed. Size/Type: One to sixteen 1 to 8 alphanumeric characters Required: No Batch 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 options currently 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. OPTION ===> 1 2 3 4 JOBCHAIN SCDCHAIN CJOBCHAN CSCDCHAN Successors Successors Successors Successors of of of of a a a a
xxyy (SCHD) SUCCESSOR -------------------
Job Schedule Job in the Current Workload Schedule in the Current Workload
Enter END to exit.
Use option 1, JOBCHAIN, to generate a list of successors defined to a specific job in the database. See the next topic for more information. Use option 2, SCDCHAIN, to generate a list of successors defined to a specific schedule 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 to a 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 to a 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 the CA-Scheduler database. The batch utility to use is CAJUTIL0. The batch command is REPORT JOBCHAIN.
xxyy (SCHD) JOBCHAIN --------------------
Options: Level . . . . . Repeat . . . . . YES Date . . . . . .
Enter END to exit.
The fields are: Job Name The job from which the successor list should start. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The job number of the starting job. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JNO Default: 01 Station The station of the starting job. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: STation Default: 40
6-22 Online Guide
6.10 Successors
Schedule The schedule of the starting job. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: The first schedule that contains the specified job Level How many levels deep the successor report should go. For example, if JOBA's successor is JOBB, and JOBB's successor is JOBC, two levels are required to reach JOBC. Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: Level Default: All successors Repeat Specify NO to prevent already displayed successors from displaying again when multiple successor paths reach the same point. For example, if JOBA's successors are JOBB and JOBC, and JOBB's and JOBC's successor is JOBD, specifying NO for REPEAT will only display JOBD's successors once. Size/Type: Yes or no Required: No Batch Keyword: Repeat Default: YES Date If 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: No Batch 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 the CA-Scheduler database. The batch utility to use is CAJUTIL0. The batch command is REPORT SCDCHAIN.
-------------------- CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule . . . . Options: Level . . . . . Repeat . . . . . YES Date . . . . . .
xxyy (SCHD) SCDCHAIN --------------------
Enter END to exit.
The fields are: Schedule The name of the starting schedule. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Schedule Level How many levels deep the successor report should go. For example, if JOBA's successor is JOBB, and JOBB's successor is JOBC, two levels are required to reach JOBC. Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: Level Default: All successors
6-24 Online Guide
6.10 Successors
Repeat Specify NO to prevent already displayed successors from displaying again when multiple successor paths reach the same point. For example, if JOBA's successors are JOBB and JOBC, and JOBB's and JOBC's successor is JOBD, specifying NO for REPEAT will only display JOBD's successors once. Size/Type: Yes or no Required: No Batch Keyword: Repeat Default: Yes Date If 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: No Batch Keyword: Date
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 current workload. The batch utility to use is CAJUTIL0. The batch command is REPORT CJOBCHAN.
xxyy (SCHD) CJOBCHAN --------------------
Options: Level . . . . . Repeat . . . . . YES
Enter END to exit.
The fields are: Job Name The job from which the successor list should start. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The job number of the starting job. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JNO Default: 01 Station The station of the starting job. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: STation Default: 40
6-26 Online Guide
6.10 Successors
Schedule The schedule of the starting job. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: The first schedule that contains the specified job Level How many levels deep the successor report should go. For example, if JOBA's successor is JOBB, and JOBB's successor is JOBC, two levels are required to reach JOBC. Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: Level Default: All successors Repeat Specify NO to prevent already displayed successors from displaying again when multiple successor paths reach the same point. For example, if JOBA's successors are JOBB and JOBC, and JOBB's and JOBC's successor is JOBD, specifying NO for REPEAT will only display JOBD's successors once. Size/Type: Yes or no Required: No Batch Keyword: Repeat Default: Yes
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 current workload. The batch utility to use is CAJUTIL0. The batch command is REPORT CSCDCHAN.
-------------------- CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule Name . . Options: Level . . . . . . Repeat . . . . . YES
xxyy (SCHD) CSCDCHAN --------------------
Enter END to exit.
The fields are: Schedule The name of the starting schedule. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Schedule Level How many levels deep the successor report should go. For example, if JOBA's successor is JOBB, and JOBB's successor is JOBC, two levels are required to reach JOBC. Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: Level Default: All successors
6-28 Online Guide
6.10 Successors
Repeat Specify NO to prevent already displayed successors from displaying again when multiple successor paths reach the same point. For example, if JOBA's successors are JOBB and JOBC, and JOBB's and JOBC's successor is JOBD, specifying NO for REPEAT will only display JOBD's successors once. Size/Type: Yes or no Required: No Batch Keyword: Repeat Default: Yes
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. OPTION ===> 1 2 3 4 JOBRCHAN SCDRCHAN CJOBRCHN CSCDRCHN Predecessors Predecessors Predecessors Predecessors of of of of a a a a
xxyy (SCHD) PREDECESSORS -----------------Job Schedule Job in the Current Workload Schedule in the Current Workload
Enter END to exit.
Use option 1, JOBRCHAN, to generate a list of predecessors defined to a specific job in the database. See the next topic for more information. Use option 2, SCDRCHAN, to generate a list of predecessors defined to a specific schedule 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 workload to 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 workload to 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 the CA-Scheduler database. The batch utility to use is CAJUTIL0. The batch command is REPORT JOBRCHAN.
xxyy (SCHD) JOBRCHAN --------------------
Options: Level . . . . . Repeat . . . . . YES Date . . . . . .
Enter END to exit.
The fields are: Job Name The job from which the predecessor list should start. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The job number of the starting job. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JNO Default: 01 Station The station of the starting job. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: STation Default: 40
6.11 Predecessors
Schedule The schedule of the starting job. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: The first schedule that contains the specified job Level How many levels deep the predecessor report should go. For example, if JOBA's predecessor is JOBB, and JOBB's predecessor is JOBC, two levels are required to reach JOBC. Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: Level Default: All predecessors Repeat Specify NO to prevent already displayed predecessors from displaying again when multiple predecessor paths reach the same point. For example, if JOBA's predecessors 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 no Required: No Batch Keyword: Repeat Default: YES Date If entered, only predecessors 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: No Batch Keyword: Date
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 the CA-Scheduler database. The batch utility to use is CAJUTIL0. The batch command is REPORT SCDRCHAN.
-------------------- CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule . . . . Options: Level . . . . . Repeat . . . . . YES Date . . . . . .
xxyy (SCHD) SCDRCHAN --------------------
Enter END to exit.
The fields are: Schedule The name of the starting schedule. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Schedule Level How many levels deep the predecessor report should go. For example, if JOBA's predecessor is JOBB, and JOBB's predecessor is JOBC, two levels are required to reach JOBC. Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: Level Default: All predecessors
6.11 Predecessors
Repeat Specify NO to prevent already displayed predecessors from displaying again when multiple predecessor paths reach the same point. For example, if JOBA's predecessors 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 no Required: No Batch Keyword: Repeat Default: Yes Date If entered, only predecessors 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: No Batch Keyword: Date
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 current workload. The batch utility to use is CAJUTIL0. The batch command is REPORT CJOBRCHN.
-------------------- CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule . . . . Options: Level . . . . . Repeat . . . . . YES
xxyy (SCHD) CJOBRCHN --------------------
Enter END to exit.
The fields are: Job Name The job from which the predecessor list should start. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The job number of the starting job. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JNO Default: 01 Station The station of the starting job. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: STation Default: 40
6.11 Predecessors
Schedule The schedule of the starting job. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: The first schedule that contains the specified job Level How many levels deep the predecessor report should go. For example, if JOBA's predecessor is JOBB, and JOBB's predecessor is JOBC, two levels are required to reach JOBC. Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: Level Default: All predecessors Repeat Specify NO to prevent already displayed predecessors from displaying again when multiple predecessor paths reach the same point. For example, if JOBA's predecessors 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 no Required: No Batch Keyword: Repeat Default: Yes
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 current workload. The batch utility to use is CAJUTIL0. The batch command is REPORT CSCDRCHN.
-------------------- CA-SCHEDULER 9. COMMAND ===> Schedule: Schedule Name . . Options: Level . . . . . . Repeat . . . . . YES
xxyy (SCHD) CSCDRCHN --------------------
Enter END to exit.
The fields are: Schedule The name of the starting schedule. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Schedule Level How many levels deep the predecessor report should go. For example, if JOBA's predecessor is JOBB, and JOBB's predecessor is JOBC, two levels are required to reach JOBC. Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: Level Default: All predecessors
6.11 Predecessors
Repeat Specify NO to prevent already displayed predecessors from displaying again when multiple predecessor paths reach the same point. For example, if JOBA's predecessors 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 no Required: No Batch Keyword: Repeat Default: Yes
6-38 Online Guide
Chapter 7. Criteria Language

The criteria language consists of a criteria vocabulary and a set of calendar mechanisms used to construct a reason, or set of reasons, for selecting a schedule or job for execution and for establishing its predecessors. For example, if SCHEDA is to run every Monday and every Thursday, the selection criteria associated with this schedule is MON OR THU. This example uses criteria vocabulary that refers to a processing period when selecting a 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 another schedule or job being selected. For example, to select JOBB if JOBA was selected, the criteria associated with JOBB is JOBA. So far, we have discussed using the criteria vocabulary to select schedules or jobs. But the criteria vocabulary is also used for defining predecessors. Predecessors are conditions that have to be met before a schedule or job is allowed to start. Other terms used 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 an output data set, a job run on another node, a nonscheduled OS/390 job, and other items like these. Any predecessor can be defined as occurring on the day the schedule or job is selected or as having occurred on a prior day. This will be discussed in more detail later through the use of examples. The criteria language uses three types of yearly calendar mechanisms: Absolute Gregorian Calendar which defines specific keywords that have absolute dates associated with them. For example, the DAILY keyword causes a job to be selected every day including weekends and holidays; WEEK-DAY causes selection on Monday through Friday including holidays; and so on. This mechanism 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 accounting periods. This is the most flexible calendar mechanism to use and is the one recommended. 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 using calendars, only the calendar name determines selection. For example, you cannot also select based on a criteria statement: with calendars, criteria statements only define predecessors. To use this mechanism, you must define several different calendars. 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 following categories: 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 NOT expression is used with selection keywords only. Parentheses can be used to logically group these expressions. The examples below show how these reserved words can be used to handle real scheduling situations.
7.1.2 Reserved Words Used for Selection

This topic discusses reserved words that cause schedules and jobs to be selected on a given 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 so on. 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 when you 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 automatically becomes a predecessor as well. Although the schedule or job name itself causes selection to occur, a couple of reserved words can be used with them. One of these keywords 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, the predecessor is the completion. This subject is covered in much more detail later in this chapter.
The following examples demonstrate the use of selection reserved words. Each of these examples is called a condition. Example JOBA SCHDA JOBA-02 40 SCHDA JOBA.STEP2-02 40 SCHDA JOBA.STEP2.CC.GT.00008-02 40 SCHDA JOBA.PROC1.STEP2-02 40 SCHDA JOBA.PROC1.STEP2.CC.GT.00008-02 40 SCHDA DAILY MON WDAY HDAY JOB1 MON AND JOB1 MON AND START JOB1 MON AND NOT HDAY WDOW1 WED AND SCD SCHD1 WDOM-1 OR JOB1 WDOW2 OR NOT JOB1 7TH RD15 = +01 MAR AND RD14= -01 Interpretation During Selection Jobname JOBA in schedule SCHDA (Defaults ST=40, JNO=01). Jobname JOBA, Jobnumber 02 at station 40 in schedule SCHDA. Jobname, Jobnumber 02 at station 40 in schedule SCHDA. Jobname JOBA, Jobnumber 02 at station 40 in schedule SCHDA. Jobname JOBA, Jobnumber 02 at station 40 in schedule SCHDA. Jobname JOBA, Jobnumber 02 at station 40 in schedule SCHDA. Daily. Monday. Every workday. Every nonworkday, meaning holidays and possibly weekends. HDAY can also be expressed as NOT WDAY. Every day JOB1 is selected. Every Monday as long as JOB1 is also selected. This is the same as the prior one. That is, every Monday as long as JOB1 is also selected. Every Monday as long as it is not a holiday. First workday of any week. Every Wednesday as long as the schedule SCHD1 is also selected. Last workday of the month or as long as JOB1 is selected. Second workday of the week whether or not JOB1 is selected. Also selected any time JOB1 is not selected. The seventh day of every month. First workday following the fifteenth of every month. 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 any form of selection. PRED or PRED SCD Indicates the predecessor job or schedule must complete, probably on a prior day. That is, the predecessor must complete some time since the job or schedule last ran, or was created. If the PRED schedule or job is also in today's workload, it will always wait for today's PRED. NJE Indicates the predecessor job runs on another node. NJE can be prefixed with START indicating that this job will not start until the NJE job that is the predecessor also starts. It can also be prefixed with PRED indicating the predecessor was an NJE job that ran on a prior day. Indicates the predecessor job is a nonscheduled OS/390 job. MVS can be prefixed with PRED indicating it was run on a prior day. Indicates the predecessor is the close of an output data set. DSN can be prefixed with PRED indicating the output data set was closed on a prior day. Indicates the predecessor is the close of an output generation data group. GDG can be prefixed with PRED indicating the output generation data group was closed on a prior day. Indicates a user-defined event must be satisfied. These predecessors are called global parameters and are described in 9.1, Commonly Asked Questions on page 9-2. When predecessors are defined this way, they are called explicit predecessors. That is, the predecessor name is explicitly stated in the criteria. This particular type can even be further qualified as a keyword-defined explicit predecessor. The following examples illustrate the use of predecessor reserved words. Each of these examples is called a condition. Example JOBA SCHDA JOBA.STEP2-02 40 SCHDA JOBA.STEP2.CC.GT.00008-02 40 SCHDA Interpretation of Predecessors DO NOT RUN UNTIL after JOBA completes. After Jobname JOBA, Stepname STEP2, Jobnumber 02 at station 40 in schedule SCHDA completes. After Jobname JOBA, Stepname STEP2 ending with a condition code greater than 8, Jobnumber 02 at station 40 in schedule SCHDA completes.
MVS DSN
GDG
GBLxnn
Example JOBA.PROC1.STEP2-02 40 SCHDA
Interpretation of Predecessors After Jobname JOBA, Procstep name PROC1, Stepname STEP2, Jobnumber 02 at station 40 in schedule SCHDA completes. After Jobname JOBA, Procstep name PROC1, Stepname STEP2 ending with a condition code greater than 8, Jobnumber 02 at station 40 in schedule SCHDA completes. After JOBA starts. JOBA completed at least once since the last time the job you are defining predecessors for ran. If JOBA happens to be in today's workload, this job will not run until today's JOBA completes regardless of when JOBA ran previously. After all of the jobs in the schedule SCHD1 have completed. After the nonscheduled OS/390 job JOBA completes. (The job JOBA is not under the control of CA-Scheduler.) After the output data set PROD.JOB1DSN has been closed at least once since this job was last run.
JOBA.PROC1.STEP2.CC.GT.00008-02 40 SCHDA START JOBA PRED JOBA SCHDA
SCD SCHD1 MVS JOBA PRED DSN PROD.JOB1DSN
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 any time that JOBA is selected. In doing this, JOBA automatically becomes a predecessor to JOBB. Thus, JOBA is an explicit predecessor to JOBB. That is, the predecessor name is explicitly stated in the criteria. This particular type can even be further qualified as a selection-defined explicit predecessor. Selection-defined explicit predecessors are jobs or schedules used in the selection criteria. The following is a list of these criteria: Job name Job name.Step name Job name.Procstep name.Step name Job name.Procstep name.Step name.CC.failoper.failcode SCD schedule name START job name START SCD schedule name
7-6 Online Guide
Example JOBA
Interpretation of Criteria Select every time JOBA is selected and make the successful completion of JOBA a predecessor of JOBC. Select every time JOBA is selected and make the successful completion of STEP2 in JOBA a predecessor of JOBC. Select every time JOBA is selected and make the successful completion of STEP2 in procstep PROC1 in JOBA a predecessor of JOBC. Select every time JOBA is selected and make the completion of STEP2 with a condition code greater than 8 in procstep PROC1 in JOBA a predecessor of JOBC. Select every time JOBA is selected and make the start of JOBA a predecessor of JOBC. Select every time JOBA is selected on a Monday. JOBC will not start until JOBA completes successfully. Select every time schedule SCHD1 is selected on a Wednesday. JOBC will not start until schedule SCHD1 starts.
JOBA.STEP2
JOBA.PROC1.STEP2
JOBA.PROC1.STEP2.CC.GT.00008
START JOBA
MON AND JOBA
WED AND START SCD SCHD1
Now look at some examples that define selection and predecessor criteria for JOBC.
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), the sequential order of the stations defines implicit predecessors. For example, a CPU job on 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 automatically selected 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, you cannot 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. For example, 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 job at the CPU station. If the job at the CPU station is not selected, none of the non-CPU station jobs will be selected. If the CPU station job is selected, the criteria for the non-CPU station jobs is evaluated to determine if the non-CPU station job should be selected. For example, assuming that station 40 is the CPU station: JOB1- 1 3 JOB1- 1 4 JOB1- 1 7 SCHDA has criteria of 'MON' SCHDA has criteria of 'WDAY AND NOT HDAY' SCHDA has no criteria
The station 40 job is selected every workday that is not a holiday. The station 30 job is selected every day that the station 40 job is selected that is also a Monday. The station 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 40 job 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 40 job is selected. If a CPU station job is not defined, the lowest station number defined for the job takes over the role of the station 40 job in determining if other non-CPU station jobs should be 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, and station 70 is the lowest station number defined for the job, the station 71 job will only be eligible for selection when the station 70 job is selected. In this case, the station 71 job 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, the condition or combination of conditions, individually caused the reason a job or schedule was selected. The way you separate reasons is with an OR outside of a set of parentheses or with an OR if no parentheses are being used. For example, MON AND JOB1 OR TUE AND JOB2 is the same as (MON AND JOB1) OR (TUE AND JOB2) Use parentheses as a normal convention since their use more clearly depicts your intention. 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 example above, the value 01 would be the reason if it was selected because it was (MON AND JOB1). The value 02 would be the reason if it was (TUE AND JOB2). This value can be referred to as the reason code. Understanding the relationships between reasons and predecessors is important. Since the criteria language is used to define both selection and predecessor conditions, there are rules for interpreting this mixture. Rule #1: Every CA-Scheduler-controlled job or schedule listed in a criteria statement is a predecessor if it is also in the day's production. Whether those jobs or schedules are part of the reason for selection does not matter.
Given the example above, this means that no matter what day it is, JOB1 and JOB2 will be predecessors as long as they are in the day's workload. If it is Monday and JOB2 happens to be in the workload for Monday, JOBC (the job being defined) will have to wait for both JOB1 and JOB2 to complete. Does this mean that 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.
7.1.6 Effect of NOT Condition on Predecessors

The Boolean NOT expression affects selection just as you might expect: selection only occurs when something else does not happen that day. For example, if the criteria for JOBC is: (MON AND NOT JOB1) selection will occur only on Mondays when JOB1 is not selected. How would predecessors be handled in the above example? If JOB1 for some reason ends up in the workload (by a manual override), JOBC will wait for it if JOB1 was added while JOBC was waiting for its start time to be reached or other predecessors to be satisfied. Another example will help reinforce this point. Consider this criteria statement associated with JOBC: (MON AND NOT (JOB1 AND JOB2)) This will cause selection to occur only on Mondays when both JOB1 and JOB2 are not selected. If either JOB1 or JOB2 is present, however, it will be a predecessor of JOBC. 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 understood by your production control area. So if production control thinks of schedules as units of work, selection criteria would normally be defined at the schedule level. If all jobs in 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 at the job level. If a job does not run every time its schedule runs, define its own individual selection criteria on the job criteria record. Keep the following rule in mind when coding selection criteria. Rule #2: A job will only be evaluated for selection and eligible for today's workload if its schedule is selected or eligible for today's workload.
For example, if the selection criteria for SCHED1 is MON, and JOB1A in SCHED1 has a selection criteria of TUES, JOB1A will never get selected. JOB1A is only looked at if its schedule is selected but SCHED1 is not selected on Tuesdays, so JOB1A will never be selected. Since we are on the subject of schedules and jobs, it is time to suggest another rule for coding the criteria language. Rule #3: When coding a job in the criteria language, always qualify it with its schedule name.
Up to now, we have not followed this rule for simplicity's sake. After all, schedule names technically are not required. However, if you omit a schedule name when referring to a job, CA-Scheduler looks in its database and defaults to the first schedule it finds containing a job by that name. That explains why we advise that you follow Rule #3. From now on, we will, too. A schedule is eligible for selection even if AUTOSEL=NO is specified.
7.2 Calendar Mechanisms

Most of the examples presented so far have used explicit vocabulary such as MON for Monday or WEEK-DAY for Monday through Friday. But this oversimplifies what happens in real life. For example, we do have holidays. And your accounting month may not begin on the first of every month. Some months have four weeks, while others 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 absolute dates associated with them. For example, the DAILY keyword causes a job to be selected every day including weekends and holidays; WEEK-DAY causes selection on Monday through Friday including holidays; and so on. This mechanism 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 also provides the easiest transition at year end. Each schedule defines which date table to use for evaluating when to select that schedule and its associated jobs. Calendars define daily, weekly, and monthly calendars for selecting schedules and jobs. When using calendars, only the calendar name determines selection. For example, you cannot also select based on another job being selected. To use this mechanism, you must define individual calendars. This is the mechanism to use if all 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 and can be used immediately. You do not have to define a calendar or date table first. All you 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 standard Gregorian calendar, not workdays or accounting days. Some examples of these keywords follow: Keyword DAILY WEEK-DAY SUN FRI MWF TT JAN 1ST SUN1 WED-1 2ND-WEEK WOY3 WOY-2 I-WOY3 When Selected Every day including weekends and holidays Monday through Friday Sunday Friday Monday or Wednesday or Friday Tuesday or Thursday January First day of the month First Sunday of the month Last Wednesday of the month Second week of the month (first Saturday starts the first week of the month) Third week of the year Second-to-the-last week of the year Third week of the year based on the international definition of a week in ISO 8601, which says that all weeks start on Monday and go to Sunday. The first week of the year is the Monday to Sunday period that contains January 4 (which is the same as the week that contains the first Thursday). This means that December 29-31 may be in week 1 of the following year, and January 1-3 may be in week 52 of the previous year. Second-to-the-last week of the year based on the international definition of a week in ISO 8601, which says that all weeks start on Monday and go to Sunday. The first week of the year is the Monday to Sunday period that contains January 4 (which is the same as the week that contains the first Thursday). This means that December 29-31 may be in week 1 of the following year, and January 1-3 may be in week 52 of the previous year.
I-WOY-2
Many other keywords can be found in 7.9, Gregorian Calendar Conditions on page 7-41.
Do not forget that you can also use the Boolean reserved words AND, OR, and NOT: Example JAN AND 15TH (JAN AND 1ST) OR (APR AND 1ST) OR (JUL AND 1ST) OR (OCT AND 1ST) DEC AND THU-1 Always Selected On January 15 On the first day of each quarter
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 we recommend you use. It handles holidays (and weekends) as they pertain to your own environment. When defining the selection for a job or schedule, date tables are used to answer such questions as: Is today a workday? Is tomorrow a holiday? Is this the fourth workday of the month? In other words, CA-Scheduler is smart enough to know today's date but is not smart enough 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 actually displays a calendar one month at a time. Before we see how to define holidays on these panels, we will discuss the reserved words (keywords) used with date tables. You can use two types of keywords with date tables: workday keywords and accounting-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 are considered holidays (unless you specify otherwise). The following is a sampling of these keywords: Keyword WDAY HDAY WDOW2 WDOW-1 WDOM-1 WDOM-2 WWOM2 RD01 = +1 RD17 = -2 HDAY1 HDAY-3 When Selected All workdays All holidays Second workday of the week Last workday of the week Last workday of the month Second-to-the-last workday of the month Second work week of the month (any week with at least one workday is counted as a work week) First workday after the first day of any month Two workdays prior to the 17th of any month Current date plus one is a holiday 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 of time. When you define a date table, you have to define a prefix (a letter, with the exception of E, H, N, P, or W, allowing for 21 different accounting periods) while using the same date table. Each accounting period has its own prefix. The A prefix or the A version of the date table is the default date table. When you use a B prefix, the accounting resolutions will be taken from the B version of the date table. In the examples below, x is used instead of a prefix. Keyword xDAY xDOM1 xDOM-1 xWOM2 xWOM-1 When Selected All accounting days for prefix x First accounting day of the period (there can be up to 40 accounting days in the period) Last accounting day of the period Second accounting week of the period (there can be up to 10 accounting weeks per period) Last accounting week of the period
Now that we have some of the terminology out of the way, we will see what is involved in setting up a date table. We have to start with a rule. As you might think, we have to consider accounting periods going over a year-end date. Consequently, a rule for date tables: Rule #4: Define three years' worth of date tables for each unique date table name. Each year being accessed must have a date table for the year before and after it.
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 the one to seven character name of the date table, the prefix character, and the year. The following panel is displayed.
7-16 Online Guide
-------------------- CA-SCHEDULER 9. COMMAND ===> Define Datetable: Datetable . . . . Accounting Code . Year . . . . . . Workdays per Week . . . . . . . .
DATETAB A 2 3 5 (5, 6, 7, or
Enter END to Exit.
Press Enter to display the first month of the date table.
-------------------- CA-SCHEDULER 9. COMMAND ===> Datetable . . . . . DATETAB Description . . . . Sunday --------3 1 17 24 31 .... .... .... .... ..M. Monday --------4 11 18 25 WA.. WA.. WA.. WA.. Tuesday --------5 12 19 26 WA.. WA.. WA.. WA..
Accounting Code . . A JANUARY 2 3 Thursday --------7 14 21 28 WA.. WA.. WA.. WA.. Friday --------1 WA.. 8 WA.. 15 WA.. 22 WA.. 29 WA.. Saturday --------2 .... 9 .... 16 .... 23 .... 3 ....
Wednesday --------6 13 2 27 WA.. WA.. WA.. WA..
Legend: W... .A.. ..M. ...Y -
Enter END to exit.
To indicate that January 1 is a holiday and a nonaccounting day, delete the W (to remove 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 is being used. You can also change the end of the month (or the accounting period) by removing the M from the 31st and putting it on another day (even in another month). If January was the 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.
-------------------- CA-SCHEDULER 9. COMMAND ===> Datetable . . . . . DATETAB Description . . . . Sunday --------3 1 17 24 31 .... .... .... .... ..M. Monday --------4 11 18 25 WA.. WA.. WA.. WA.. Tuesday --------5 12 19 26 WA.. WA.. WA.. WA..
Accounting Code . . A JANUARY 2 3 Thursday --------7 14 21 28 WA.. WA.. WA.. WA.. Friday --------1 .... 8 WA.. 15 WA.. 22 WA.. 29 WA.. Saturday --------2 .... 9 .... 16 .... 23 .... 3 ....
Wednesday --------6 13 2 27 WA.. WA.. WA.. WA..
Legend: W... .A.. ..M. ...Y -
Enter END to exit.
You may use PF8 to scroll to later months and PF7 to scroll to earlier months. You may also type the first three letters of any month's name on the command line to jump directly to that month. When you are finished updating the date table, press PF3 to save your changes. (If you wish to exit without saving your changes, type CAN on the command line.) Don't forget 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 period processing. If you need more than one holiday definition, you will need another date table. The reserved words (keywords) for the Gregorian Calendar mechanism and the keywords for the date table calendar mechanism can be used together. Here are some examples of Gregorian and/or date table calendar mechanisms: Example (MON AND WDAY) OR (TUE AND HDAY-1) WDOW1 Interpretation Select on Monday when Monday is not a holiday, or select on Tuesday when Monday is a holiday. Select the first workday of every week. This is the same as above except if Tuesday is also a holiday, it will be selected on Wednesday. Select every Monday through Thursday except on holidays. This is the same as the above example only expressed more simply. Select on every accounting day except for the last accounting day of the period. This references the date table defined with prefix B. Select every workday of the last week of the year. Select every Monday of the second and fourth weeks of the month regardless of whether Monday is a holiday. Select on every accounting day that is not a holiday. An accounting day may be a holiday (this is not normally the case).
WDAY AND (MON OR WED OR TT) WDAY AND NOT FRI BDAY AND NOT BDOM-1 WDAY AND WOY-1 MON AND (WWOM2 OR WWOM4) ADAY AND NOT HDAY
7.2.2.4 Date Translation Report

Now that we have discussed the Gregorian calendar and date tables, we need a way to see what conditions are met on any given day. The Date Translation report is obtained by running the CA-Scheduler Utility with the REPORT DATETRAN transaction. You can request a specific date and/or date table on this transaction if you desire. Reviewing this report will help you understand the Gregorian calendar and date tables better.
COMPUTER ASSOCIATES CA-SCHEDULER 9. xxyyCH9
DATE TRANSLATION REPORT
DATETRAN PAGE 1 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 TRUE for a specific date and date table combination. It first displays the Julian and Gregorian 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 of the report.) Notice the next set of lines pertain to the Gregorian calendar and include DAY OF WEEK, WEEK OF MONTH, DAYnOFm, and WEEKnOFm. These indicate whether a condition is satisfied. For example, WEEK-DAY=YES means that any time you specified WEEK-DAY as the criteria, the schedule or job will be selected. The rest of the 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 days of the month, and the various accounting days. After reviewing this report carefully, you should understand how the criteria vocabulary 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 the Gregorian calendar and date tables. Calendars use an entirely different approach to selecting schedules and jobs. Do not try to relate any discussion of calendars to the other calendar mechanisms. We do not recommend that you use calendars. Instead, try to do all of your definitions with date tables or the Gregorian calendar or a combination of the two. This feature is supported 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 use calendars, you can skip this subtopic. You would use this mechanism if a set of schedules have to run on specific dates during the year and no relationship exists between the dates. Then you would use a calendar 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 calendar specifies 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 for selection purposes is the calendar name. The same calendar also applies to the jobs in that 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 calendar defines your holidays as well as what to do if another calendar is defined with a processing day on a holiday. You may shift the day to the previous workday, the next workday, 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 have only one set of holiday definitions. Once the prototype is defined, you can define calendars specific to your needs. The panel below defines the prototype calendar for 2003. It specifies a five day work week. If calendars are defined using a holiday, CA-Scheduler handles rescheduling based on the calendar's selection frequency: Daily calendars are not rescheduled. Workdays in the prototype calendar become workdays in the daily calendar. Weekly calendars use the Weekly Roll Option. Drop means not to schedule a workday in the weekly calendar. Next and Previous schedule the next or previous workday in the prototype as the workday in the weekly calendar.
Monthly calendars use the Monthly Roll Option. Drop means not to schedule a workday in the monthly calendar. Next and Previous schedule the next or previous workday in the prototype as the workday in the monthly calendar.
Define Prototype Calendar: Calendar . . . . . . PROTO 3 Year . . . . . . . . 2 3 Workdays per Week . . 5 (5, 6, 7, or Prototype Options: Weekly Roll Option . . . DROP Monthly Roll Option . . DROP
(NEXT or PREVIOUS workday, or 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 a holiday to a workday by typing a W next to it, or to a holiday by blanking out the W.
-------------------- CA-SCHEDULER 9. COMMAND ===> Calendar . . . . . PROTO 3 Description . . . .
JANUARY Sunday --------3 1 17 24 31 . . . . . Monday --------4 11 18 25 W W W W Tuesday --------5 12 19 26 W W W W
3 Thursday --------7 14 21 28 W W W W Friday --------1 W 8 W 15 W 22 W 29 W Saturday --------2 . 9 . 16 . 23 . 3 .
Wednesday --------6 13 2 27 W W W W
Legend: W - Workday
Enter END to exit.
You may use PF7 and PF8 to scroll through the months, or type the first three letters of 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 will be saved. (You can exit without saving your changes by typing CAN on the command line.)
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 defining calendars, invent your own names for them such as EVERYDAY, TUESDAYS, ENDOFWK, or ENDOFMO. When defining a calendar, the following panel is displayed.
Define Calendar: Calendar . . . . . . MYCAL Year . . . . . . . . 2 3 Workdays per Week . . 5 (5, 6, 7, or Options: Type of Calendar . . . DAILY Day of Week/Month . .
(Daily, Weekly, or Monthly) (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 a workday for this calendar. For monthly calendars, you may specify the day of the month that should become a workday, 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 the week, 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - X X X X X
JOBA
7.3.2 Example 2
Now use another variation of WDOW to schedule JOBA to run on the last workday of the week. WDOW-1 JOBA would be selected on the last working day of the week (third Friday=holiday). 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - X X X H X
JOBA
7.3.3 Example 3
Then what criteria statement would you use to run JOBA on the first workday of the month? WDOM1 JOBA would be selected on the first Monday of the month. 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - X
JOBA
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. 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - X
JOBA
7.3.5 Example 5
JOBA runs on Friday. If Friday is a holiday, then JOBA runs on the following Monday. And if the following Monday is also a holiday, then JOBA runs on the following 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 also a holiday, then run job on TUES. 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - X X H X X
JOBA
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 wait for the other two jobs to finish What criteria statements apply to this schedule and its jobs? Criteria for schedule ACCPROD Criteria for job PROD001 Criteria for job PROD002 Criteria for job PROD003 None: All jobs may be selected daily. WDAY FRI FRI AND (PROD001 ACCPROD OR PROD002 ACCPROD)
For selection purposes, the OR expression will be handled as expected. However, predecessors that are jobs are handled as if there is always an AND condition. Consequently, if Friday is a workday, PROD003 will wait for both PROD001 and PROD002.
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 also wait for job PAY002. PAY002 - the summary that only runs on Friday. Criteria for schedule PAY Criteria for job PAY002 Criteria for job PAY001 WEEK-DAY FRI DSN PAY001.INPUT AND (PAY002 PAY OR NOT PAY002 PAY)
This tells CA-Scheduler to schedule job PAY001 every week day, regardless of whether job PAY002 is scheduled. Job PAY001 waits for a data set to be created every week day and also waits for job PAY002, when it is scheduled on Friday.
7.3.8 Example 8
The Manufacturing Quarterly production schedule (MANQTR) contains three jobs that run 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 prefix of M. Criteria for schedule MANQTR MDOM-1 AND (MMOY3 OR MMOY6 OR MMOY9 OR MMOY12) None - Defaults to whenever the schedule is selected. JOBA MANQTR JOBB MANQTR
Criteria for job JOBA Criteria for job JOBB Criteria for job JOBC
The example above shows how you can define selection criteria at the schedule level and predecessors at the job level. Separating selection criteria and predecessor conditions this way makes it easier to evaluate these criteria statements.
7.3 Some Examples
7.3.9 Example 9
For this example, we take something a little more practical and show some of the logic behind 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 daily backup, a weekly backup and a monthly backup. The daily job IH7D02 normally runs Monday through Thursday. Consequently, its criteria would be something like: MON OR TUE OR WED OR THU But what happens on holidays? On holidays, we do not want the job to run. To omit holidays, revise the criteria as follows: WDAY AND (MON OR TUE OR WED OR THU) Now Monday through Thursday also have to be workdays. A more concise way of writing this criteria is as follows: WDAY AND NOT FRI Another factor to consider is whether this job has predecessors. In this case, it does not, 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. If the weekly job runs on Monday through Thursday, the daily job must finish first. The criteria 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 can simplify 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 the month. 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 should wait for the daily backup to complete. If the last workday of the month is a Friday, the monthly job should wait for the weekly backup to complete. If the last workday of the month falls on a Saturday or Sunday, the monthly backup job has no predecessors. For our purposes, however, the date table was defined 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 Criteria for job IH7D02 Criteria for job IH7W02 Criteria for job IH7M02 None - Defaults to having all jobs looked at every day. WDAY AND NOT FRI WDOW-1 AND PRED IH7D02 IH7BKUP WDOM-1 AND (IH7D02 IH7BKUP OR IH7W02 IH7BKUP)
7.3.10 Example 10
JOBX JOBX JOBX JOBX JNO= JNO= JNO= JNO= 1 2 3 4 CRI=JOBA CRI=JOBB CRI=JOBC 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 to complete. 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - X X X X X X X X X X X X X X X X X X X X X X X X
JOBA JOBXJOBB JOBXJOBC JOBXJOBD JOBX-
1 2 3 4
7.3 Some Examples
7.3.11 Example 11
JOBA JOBB JOBC JOBD REQUESTED JOBA JOBB JOBC
Because JOBA is a requested job, it will be selected every day, but will not run unless requested. And because JOBA is always selected, any other jobs which are a successor to JOBA (in this case, JOBB and JOBC and JOBD are all successors), then all of these jobs will also be selected. 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - X X X X X X X X X X X X X X X X
JOBA JOBB JOBC JOBD
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/dependency works under CA-Scheduler. For example, suppose that on any given day, JOB1 and JOB2 and JOB3 are all selected to run. The job dependency would then become 'JOB1 and JOB2 and JOB3' since all three jobs were selected. (The 'OR' condition becomes an 'AND' condition for job dependency.) So, if you have a job (JOBA) that needs to run Monday through Friday when JOB1 and JOB2 are selected, and runs on Saturday and Sunday when JOB3 is selected, then you could use the following criteria: JOBA JNO= 1 JOBA JNO= 2 M JOB1 X JOB2 X JOBA- 1 X JOB3 JOBA- 2 T X X X W X X X T X X X WEEK-DAY AND JOB1 AND JOB2 WEEK-END AND JOB3 F S S M T W - - - - - X X X X X X X X X X X X X X X X T X X X F S S M T W - - - - - X X X X X X X X X X X X X X X X T X X X F S S M T W - - - - - X X X X X X X X X X X X X X X X T X X X F S S M T W - - - - - X X X X X X X X X X X X X X X X
7-30 Online Guide
7.3 Some Examples
7.3.13 Example 13
JOB NAME -------JOBA JOBB JOBC JOB CRITERIA -----------WDAY ( WORK DAY ) FRI ( FRIDAY ) 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 JOBB being a predecessor to JOBC. However, if FRIDAY is a WORKDAY, then all three jobs will run with JOBC waiting for both JOBA AND JOBB to finish before being released. Because both JOBA AND JOBB were SELECTED on FRIDAY, then JOBC's criteria becomes 'JOBA AND JOBB' rather than 'JOBA OR JOBB'. M T W T F S S M T W - - - - - - - - - X X X X X X X X X X X X X X X X X T F S S M T W - - - - - - X H X X X X X X X X X T F S S M T W - - - - - - X X X X X X X X X X X T F S S M T W - - - - - - X X X X X X X X X X X
JOBA JOBB JOBC
7.3.14 Example 14
JOB NAME -------JOBA JOBB JOBC JOBD JOB CRITERIA -----------DAILY ( DEFAULT ) MON ( MONDAY ) WED ( WEDNESDAY) (JOBA AND JOBB) OR JOBC
On MON, JOBA JOBB JOBD will run, with JOBD waiting for both JOBA JOBB to complete. ON WED, JOBA AND JOBC AND JOBD will run, with JOBD waiting for both JOBA AND JOBC to complete. *REMEMBER that the 'OR' condition becomes an 'AND' condition when DEPENDENCY 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 on WED). 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 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 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 X X X X X X X X X X X X X X X X X X X X
JOBA JOBB JOBC JOBD
7.4 What Is Wrong with these Examples?

Now that you have a basic understanding of the criteria language, try testing your knowledge by debugging errors in the following criteria statements.
7.4.1 Example 1
Criteria for JOBA SCHD01 MONDAY
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 will only be selected when the job MONDAY is selected. Since you probably do not have a job named MONDAY, JOBA in SCHD01 would never be selected. The correct criteria vocabulary word is MON.
7.4.2 Example 2
Criteria for JOBA SCHD01 MON AND TUE MONDAY AND TUESDAY
Will JOBA be selected on Mondays and Tuesdays? No, you cannot have one day as a Monday and a Tuesday. The correct criteria vocabulary word is MON or TUE.
7.4.3 Example 3
Criteria for job JOBB WDOW-1 OR DSN JOBA.DATASET
The intent is to select JOBB on the last workday of the week, but that is not what happens. Evaluate this statement carefully to see what is wrong. It is important to evaluate the selection criteria and the predecessor conditions separately. What is JOBB's predecessor? The data set JOBA.DATASET must be closed on the day 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'
7-32 Online Guide
You see, CA-Scheduler cannot translate DSN JOBA.DATASET into a selection condition, so the second condition defaults to DAILY. Because of the OR, this job is selected WDOW-1 OR DAILY. How could you rewrite the statement to run JOBB when 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 set JOBA.DATASET to close before submitting JOBB.
7.4.4 Example 4
Criteria for job JOBA Criteria for job JOBB MON AND JOBB SCHED01 OR WED MON OR WED AND JOBA SCHED01
Here is another problem. Why do JOBA and JOBB in schedule SCHED01 not run when expected? Both jobs are supposed to run Mondays and Wednesdays. On Mondays, JOBB should be the predecessor to JOBA, but conversely on Wednesdays. The meaning of these criteria statements is confusing until you add some parentheses to show how the system will interpret this: Criteria for job JOBA Criteria for job JOBB (MON AND JOBB SCHED01) OR WED MON OR (WED AND JOBA SCHED01)
Now it is a bit clearer. First, look at the selection criteria. Both jobs are always selected 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 for evaluating predecessors: There are no OR relationships with selection-defined explicit predecessors. All ORs become ANDs. That means the explicit predecessor of JOBA is JOBB, and the explicit predecessor of JOBB is JOBA. When jobs require each other as predecessors, that creates a predecessor loop, which is also called predecessor deadlock. Although these deadlocked jobs are selected properly, neither job ever runs because their predecessors are never satisfied. You can run the Analyze Report at any time to detect deadlocks automatically.
7.4.5 Example 5
Criteria for job JOBA NOT MON OR NOT TUE
Suppose you want JOBA to run on any day but Monday or Tuesday. Why does the criteria statement above not make that happen? Instead, JOBA is always selected because on Mondays, JOBA is selected because it is not Tuesday. And on Tuesdays (and every other day), JOBA is selected because it is not Monday. Two valid ways to code this criteria are: Criteria for job JOBA Another way to express this criteria NOT (MON OR TUE) NOT MON AND NOT TUE
7.4.6 Example 6
Criteria for job JOBB ADAY AND JOBA SCHED01 AND GBLB01=YES OR ADAY AND GBLB01=YES
Clearly, JOBB in SCHED01 will always be selected on ADAY. The confusion arises when evaluating predecessors. JOBB is always supposed to wait for the global GBLB01 to be set to YES. And if JOBA is in the day's workload, it is supposed to be a predecessor to JOBB. That is not what happens. Instead, when JOBA is present, the status shows that JOBB waits 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 through what 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 AND GBLB01=YES OR ADAY
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 a predecessor.
7.4.7 Example 7
Criteria for job JOBB MON OR TUE OR WED OR THU OR FRI OR (SAT AND PRED JOBA)
The intent is that JOBB would run Monday through Saturday, but only on Saturday if JOBA completed sometime since last Saturday (for example, it may be that JOBA only runs on Fridays). The rule is that keyword-defined explicit predecessors apply across ALL selection criteria. Consequently, JOBB will wait for JOBA every time JOBB is selected (even on Monday, Tuesday, and so on). To accomplish this, we have to set up JOBB as two separate jobs: JOBB-01 and JOBB-02. Notice how we have simplified the criteria for JOBB-01 below. The correct way of coding this criteria statement is: Criteria for the first job JOBB-01 Criteria for the second job JOBB-02 WEEK-DAY SAT AND PRED JOBA
7.5 Review of Tips to Remember
7.5 Review of Tips to Remember

7.5.1 Pitfalls
Pitfall #1 Pitfall #2 Pitfall #3 A global parameter only gets set. If you want it reset, you must set it to another value. You cannot reset a global parameter. Work can only be backlogged once. If work is eligible to be backlogged multiple times, only the last occurrence is kept. When keying in a command to the left of a schedule or a job in the status displays, be sure you are on the correct line. It is easy to cancel the wrong job. Predecessors for jobs added to this day's production using the RUN command are ignored if they have been canceled by the CANCEL command but not deleted from the active workload by the PURGE command. Do not use the CA-Scheduler reserved keywords as job name or schedule names. Example: Jobname: REQUESTED or DAILY Schedule name: REQUESTED or DAILY
Pitfall #4
Pitfall #5
7-36 Online Guide
7.6 Notes
7.6 Notes
Note #1 Multiple ORs can be grouped into a single reason code by placing parameters around this reason. That means (MON OR FRI) is one reason while MON OR FRI defines two reasons. Predecessors in job records are not evaluated until its schedule has started and the job's early start time has been reached. Defining predecessors for jobs does not override a schedule's predecessors; instead, predecessors are cumulative. Job start times do not override specified schedule start times. Instead, they let you postpone running jobs after a schedule has started. The PRED keyword only waits for the job if it has not run since the last time this job has run. If the predecessor job has abended, its criteria has been satisfied. All criteria for JOBNAME should be coded as 'JOBNAME SCHEDULENAME'. Do not use TYPRUN=HOLD in JCL submitted by CA-Scheduler. Autoscan does not reset the global parameters. Formatting the CAIJTRK files sets all global parameters to defaults.
Note #2 Note #3 Note #4 Note #5
Note #6 Note #7 Note #8 Note #9
7.6.1 Rules
Rule #1 Every CA-Scheduler-controlled job or schedule listed in a criteria statement is a predecessor if it is also in the day's production. Whether those jobs or schedules are part of the reason for selection does not matter. A job will only be evaluated for selection and eligible for today's workload if its schedule is selected or eligible for today's workload. When coding a job in the criteria language, always qualify it with its schedule name. CA-Schedule observes ORs used with all keyword-defined predecessors (NJE, MVS, DSN, GDG, GBLxnn, and PRED).
Rule #2 Rule #3 Rule #4
7.7 Summing Up
7.7 Summing Up
Evaluate criteria statements twice: once to determine selection criteria and again to identify 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's workload if its schedule is selected or eligible for today's workload. A schedule or job is 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 predecessor if it is also in, or eligible to be in, the day's production. Whether those jobs or schedules 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 unless you precede their names with the keyword START. Calendars: Define daily, weekly, and monthly calendars for selecting schedules and jobs. When using calendars, only the calendar name determines selection. Date Tables: Define three years' worth of date tables for each unique date table name. 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 Criteria consists of two or more selection reasons, any one of which will cause a job or schedule to be selected. A selection reason consists of two or more conditions, all of which must be met for a job or schedule to be selected. Two or more conditions count as one reason. All conditions must be satisfied except this one (negate the condition). Specify OR between reasons
AND between conditions
( ) around the conditions NOT before the exception
To show that a predecessor condition causes its successor to be selected and is the Start of a Schedule Job End of a Schedule Job
Precede it with
START SCD START
SCD
To show that the predecessor is a schedule that completed on a previous day and thus has 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 has no 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 as their successors. (For example, if the predecessor is selected on a Monday and the successor is selected on a Friday. In this case, if both the PRED predecessor and the successor are selected together, the successor will wait for the PRED predecessor event to occur within this production day.) In most cases, predecessors and successors are selected together. A job that is selected with its successor does not need any reserved word to identify it as a predecessor. The only reserved words required for predecessors and successors selected together are SCD and START, as shown in the table at the top of the previous page.
To show that the predecessor is the Start of a job at another node End of a Job at another node Nonscheduled OS/390 job End on a previous day of a Job at another node Nonscheduled OS/390 job Close of a Output data set Output generation data group Close on a previous day of a Output data set Output generation data group User-defined event which is satisfied when an operator or authorized user supplies a value on a SET GBLxnn= command which matches the value specified by the GBLxnn=value on the CRITERIA keyword (where nn is a number from 1 to 16).
Precede it with START NJE
NJE MVS
PRED NJE PRED MVS
DSN GDG
PRED DSN PRED GDG GBLxnn=
7-40 Online Guide
7.9 Gregorian Calendar Conditions

These conditions are based on the standard Gregorian calendar and not on workdays or accounting days; therefore, you can use these conditions in criteria statements with or without defining a date table. To see what Gregorian conditions are satisfied on any given day, consult the Date Translation Report in the Reports Guide. If you specify REQUESTED Schedules and jobs will be selected on Request. (They are actually selected every day but must be activated by the REQUEST or SREQ command in order to be moved to the active queue for processing. Note, when using the REQUEST/SREQ command with other criteria, that criteria are evaluated from left to right. Therefore, if you list REQUEST/SREQ before another condition, like JOBA, the schedule or job will be selected every day but must be activated by the REQUEST/SREQ command.) Every day, including weekends and holidays Monday through Friday Saturday and Sunday Sunday Monday Tuesday Wednesday Thursday Friday Saturday Monday, Wednesday, and Friday Tuesday and Thursday January February March April May June July August
DAILY WEEK-DAY WEEK-END SUN MON TUE WED THU FRI SAT MWF TT JAN FEB MAR APR MAY JUN JUL AUG
If you specify SEP OCT NOV DEC 1ST 2ND : 31ST SUN1 SUN2 SUN3 SUN4 SUN5 : SAT5 SUN-1 SUN-2 SUN-3 SUN-4 SUN-5 : SAT-5 1ST-WEEK 2ND-WEEK 3RD-WEEK 4TH-WEEK 5TH-WEEK 6TH-WEEK WOY1 : WOY53 WOY-1 : WOY-53
Schedules and jobs will be selected on September October November December 1st day of the month 2nd day of the month through the 31st day of the month 1st Sunday of the month 2nd Sunday of the month 3rd Sunday of the month 4th Sunday of the month 5th Sunday of the month : 5th Saturday of the month Last Sunday of the month Next to last Sunday of the month Second to last Sunday of the month Third to last Sunday of the month Fourth to last Sunday of the month : Fourth to last Saturday of the month First week of the month through the sixth week of the month. (The first week includes those days which precede and include the first Saturday; the second week includes those days which follow the first Saturday and precede and include the second Saturday; and so on.) First week of the year through the 53rd week of the year.
Last week of the year through the 52nd to last week of the year.
7-42 Online Guide
If you specify DAY1OF2 DAY2OF2 DAY1OF3 DAY2OF3 DAY3OF3 : DAY6OF6 WEEK1OF2 WEEK2OF2 WEEK1OF3 WEEK2OF3 WEEK3OF3 : WEEK6OF6 DOM-1 : DOM-31 Y1994 : Y2020 LEAP-YEAR
Schedules and jobs will be selected on According to a cycle lasting from one to six days. The base date for all cycles is Jan 1, 1900. To determine where a specific date falls within each cycle, see the Date Translation Table which is generated as part of each simulation run. This will tell you, for example, that May 27, 1984 is the first day in a three-day cycle and the fourth day in a five-day cycle. According to a cycle lasting from one to six weeks. The base date for all cycles is Jan 1, 1900. To determine where a specific date falls within each cycle, see the Date Translation Table which is generated as part of each simulation run. This will tell you, for example, that May 27, 1984 falls in the first week in a two-week cycle and in the last week in a five-week cycle. Last day of the month through the 30th to last day of the month. Year 1994 through year 2020.
Leap year.
7.10 Workday Conditions

To use these workday conditions, you must use the Datetable Definition panel to define workdays and holidays for three years: last year, this year, and next year. Then you can consult the Date Translation Report in the Reports Guide to see what workday conditions are satisfied on any given day. The following criteria keywords can only be used if the schedule or job is selected by a date table. If you specify WDAY HDAY WDOW1 : WDOW7 WDOW-1 : WDOW-7 WDOM1 : WDOM31 WDOM-1 : WDOM-31 WWOM1 : WWOM6 WDOY1 : WDOY-1 WWOM-1 : WWOM-6 WWOY1 : WWOY53 WWOY-1 : WWOY-53 Schedules and jobs will be selected on All workdays (days shown in high intensity on the date table). All holidays (days shown in low intensity on the date table). First workday of the week through the seventh workday of the week. (Any day shown in high intensity on the date table is counted as a workday.) Last workday of the week through the 6th to last workday of the week. (Any day shown in high intensity on the date table is counted as a workday.) First workday of the month through the 31st workday of the month. (Any day shown in high intensity on the date table is counted as a workday.) Last workday of the month through the 30th to last workday of the month. (Any day shown in high intensity on the date table is counted as a workday.) First work week of the month through the 6th work week of the month. (Any week with at least one workday is counted as a work week.) First workday of the year through the last workday of the year. (Any day shown in high intensity on the date table is counted as a workday.) Last work week of the month through the 5th to last work week of the month. (Any week with at least one workday is counted as a work week.) First work week of the year through the 53rd work week of the year. (Any week with at least one workday is counted as a work week.) Last work week of the year through the 52nd to last work week of the year. (Any week with at least one workday is counted as a work week.)
7-44 Online Guide
If you specify RD01 = -nn : RD31 = +nn
Schedules and jobs will be selected on So many workdays before (-nn) or after (+nn) the first day of the month (RD01) or the second day of the month (RD02) or the third day of the month (RD03) and so on, up to the thirty-first day of the month (RD31). For example, to select a job on the fifth workday after the 14th of the month, specify RD14 = +5. To select a job on the third workday before the 25th of the month, specify RD25 = -3. (nn may range from -31 to +31, a blank must precede and follow the equal sign, and a leading zero is not required with a one-digit number. Also, nn equal to + or -0 causes selection on the specified relative day of the month. However, if that day is a holiday, the job will not be selected at all that month.) If the current date plus 1 day is a holiday : If the current date plus 31 days is a holiday If the current date minus 1 day was a holiday : If the current date minus 7 days was a holiday
HDAY1 : HDAY31 HDAY-1 : HDAY-7
7.11 Accounting Conditions

To use these accounting conditions, you must use the Datetable Definition panel to define which days are accounting days, when each period ends, and when the accounting year ends. (Periods can be accounting periods, production periods, sales cycles, 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 Guide to see which accounting conditions are satisfied on any given day. If you have defined a prefix on the Datetable Definition panel, substitute that prefix for 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, or AWOM). If you use ADAY in a criteria statement, accounting conditions will be taken from the A version of the date table (the default version). If you use BDAY in a criteria statement, accounting conditions will be taken from the B version of the date table. Workday and holiday conditions are always taken from the A version. You must have defined an 'A' date table prefix prior to defining any other prefix for a date table. If you specify xDAY xDOM1 : xDOM40 Schedules and jobs will be selected on All accounting days (days designated on the date table) by A or another prefix. First accounting day of the period through the 40th accounting day of the period. Any day designated by A (or another prefix) on the date table is counted as an accounting day. To use these criteria, you must define at least two accounting periods on the date table. To do this, go through the date table and designate 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.) Last accounting day of the period through the 39th to last accounting day of the period. Any day designated by A (or another prefix) on the date table is counted as an accounting day. To use these criteria, you must define at least two periods on the date table. To do this, go through the date table and designate 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.) First period of the accounting year through the 53rd period of the accounting year. To use these criteria, you must designate the ends of two accounting years. To do this, define date tables for two years and designate the end of each accounting year by typing an E on any date. (The end of the accounting year defaults to the last day of each year.)
xDOM-1 : xDOM-40
xMOY1 : xMOY53
7-46 Online Guide
If you specify xMOY-1 : xMOY-53
Schedules and jobs will be selected on Last period of the accounting year through the 52nd to last period of the accounting year. To use these criteria, you must designate the ends of two accounting years. To do this, define date tables for two years and designate the end of each accounting year by typing an E on any date. (The end of the accounting year defaults to the last day of each year.) First accounting week of the period through the 10th accounting week of the period. (Any week with at least one accounting day counts as an accounting week.) To use these criteria, you must define at least two periods on the date table. To do this, go through the date table and designate 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.) For example, if the period ends on Tuesday, October 31, then Wednesday, November 1 through Tuesday, November 7 would be the xWOM1. Therefore, Wednesday, November 8 through Tuesday, November 14 would be xWOM2. Last accounting week of the period through the 9th to last accounting week of the period. (Any week with at least one accounting day counts as an accounting week.) To use these criteria, you must define at least two periods on the date table. To do this, go through the date table and designate 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.)
xWOM1 : xWOM10
xWOM-1 : xWOM-10
Chapter 8. Using the Autoscan Command File

Autoscan command file processing allows you to make arrangements for future database updates without affecting today's workload. For example, you are now able to change a job's predecessors for the next autoscan day without affecting today's workload by using the autoscan command file. Job and schedule criteria changes can be implemented without affecting today's workload. Database maintenance commands can be set up in advance to define, alter, and delete job or schedule records, thereby reducing overtime and weekend work. All command can be syntax checked and analyzed ahead of time to ensure that the commands themselves can be executed without error and that predecessor deadlocks 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 or sequential DSN (recfm=FB, lrecl=80) identified by ddname CAIJDCF. You need to specify CAIJDCF in the monitor startup procedure if you need autoscan command 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 and expiration 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 been selected.
Chapter 8. Using the Autoscan Command File 8-1
Each database maintenance command must have as its last two parameters the effective date and expiration date. All commands will be syntax checked prior to application, if an error occurs a message will be issued asking the operator to cancel scheduler or proceed with the remaining commands. It is highly recommended to syntax check those autoscan command file commands before submission or autoscan. Otherwise, monitor shutdown may occur if such an error is detected right before autoscan. DCFERR=CONT can be set in CAIJGEN to avoid such shutdown. See the DCFERR parameter in the Systems Programmer Guide. You can syntax check the autoscan command file commands at any time after you have updated the autoscan command file by using the SYNCHK DCF command. Example:
// EXEC CAJUTIL //CAIJDCF DD DSN=cai.dcfin(CAIJDCF),disp=shr //SYSIN DD SYNCHK DCF /
The batch reports, analyze, successor chain, simulation and forecast may apply the command file to the SIMWORK or UTILWORK copy of the database (see the Reports Guide) and check possible database update errors. You just need to add the CAIJDCF ddname with the desired DCF dsname and specify DCF=YES at the first CAJUTIL0 command statement. Example:
// EXEC CAJUTIL //CAIJDCF DD DSN=cai.dcfin(CAIJDCF),disp=shr //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 COMMAND ===> SCROLL ===> PAGE TOP OF DATA 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 BOTTOM OF DATA F1=HELP F7=UP F2=SPLIT F8=DOWN F3=END F9=SWAP F4=RETURN F1 =LEFT F5=RFIND F11=RIGHT F6=RCHANGE F12=RETRIEVE
Note: An * in the first position is treated as a comment. Supported Commands: The autoscan command file supports the database maintenance commands ALTER, DELETE, and DEFINE for schedules and jobs. Control and batch report commands are not allowed. See the Command Reference Guide 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 a discussion of some pitfalls. The questions are grouped by topics that parallel the structure 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 subject to subject. Do not be concerned about reading this chapter in the order that topics appear.
Chapter 9. Tips 9-1
9.1 Commonly Asked Questions

This topic consists of a series of questions that are commonly asked. The following table lists the questions with cross-references to the pages containing their responses. Topic Startup Tasks See 9.1.1.1, When Should Autoscan be Performed? on page 9-4 9.1.1.2, What Is the General Standard for Numbering Stations? on page 9-4 9.1.1.3, Should I Use Date Tables or Calendars? on page 9-5 9.1.1.4, When Should I Define a New Date Table Versus a New Cycle in an Existing Date Table? on page 9-5 Maintaining the Database 9.1.2.1, How Should I Organize My Schedules? on page 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 They Used? on page 9-8 9.1.2.5, How Can I Run a Job Like an Edit Check Repeatedly Until its Output Is Correct? on page 9-10 Analyzing the Database 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? on page 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? on page 9-15 9.1.3.8, How Can I Can Create My Own Reports? on page 9-18
9-2 Online Guide
Topic Daily Processing
See 9.1.4.1, From Where Can I Issue CA-Scheduler Control Commands? 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? on page 9-23 9.1.4.5, What Happens If CAIENF is Shut Down? on page 9-24 9.1.4.6, What Happens If a System Crash Occurs? on page 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 active workload, backlogs schedules and jobs, if appropriate, and selects the day's workload. CA-Scheduler scans the database, analyzing the selection criteria and placing the selected 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 everything completing 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 get everything ready for the day's workload. This includes JCL changes, control statement changes, 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 39 40 60 Data entry JCL staging CPU processing Print processing
Station 20 Data entry Jobs start at their early start time if you specify AUTO START=YES (as long as their predecessors and resources are satisfied). However, you always have to manually post these data entry jobs when they have ended. Station 39 JCL staging Jobs must be manually posted as ENDED (using the COMPLETE command) before a CPU job with the same name is submitted. If you specify that the station 39 job is to be automatically started (AUTO START=YES), it starts at its early start time as long as its predecessors and resources are satisfied. Station 40 CPU processing Jobs start when the early start times are met, all predecessor conditions are fulfilled, and resources are available. CPU job processing is automatic unless you override it.
9-4 Online Guide
Station 60 Print processing Jobs are automatically posted as ENDED when the corresponding CPU job is purged from the system (an SMF type-26 record is generated). These print station jobs automatically start when their corresponding CPU jobs complete on 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 jobs for a specific day. Date tables provide significantly more flexibility than calendars and should be used if at all possible. They are a bit more complicated to understand, but entail less maintenance than calendars when going from year to year. Date tables also allow multiple accounting periods as well as different holidays. One area where you will want to use calendars is when the schedule has to run according to a set of dates that follows no pattern. Define these individual days once in a calendar. Then when any schedule runs on those dates, you just give it that calendar name for selection. For most of your application needs, however, use date tables. A detailed discussion on this 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 an Existing Date Table?
Keep in mind that a cycle can be an accounting, production, or sales period. You can have up to twenty cycles defined with any one date table, and any number of date tables. 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 jobs usually belongs to one application, but could also be run at the same frequency. For example, you could define a Payroll schedule containing all the payroll jobs and its selection criteria. If certain jobs in the schedule do not run every time the schedule is selected, just define the selection criteria for the exceptional jobs. Or the daily Accounts Receivable jobs could be contained in one schedule and the weekly Accounts Receivable jobs could be in another. Possibly, the weekly schedule is dependent on the daily schedule to complete. Do not organize schedules just by frequency. For example, do not have a Monday schedule. There should not be one schedule just for REQUESTED jobs, either, unless it is easily manageable. Instead, try to keep application-related jobs together. This makes 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 with the 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 appears in the LIBTYPE installation option of the CAIJGEN macro, but can be overridden at the 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 control statements that need to be changed or added. You can code Driver procedures to automate most of the changes to the JCL and control statement setup. Before you decide 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 Job Definition panel for station 40 and either: Define an EARLY START TIME that gives users enough time to change the JCL or 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 run before CA-Scheduler submits it. A job's EARLY START TIME may arrive before its JCL 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 review the staged JCL, use the second alternative mentioned above. The job defined at station 39 will be an implicit predecessor of the CPU job at station 40. That means the CPU job cannot be submitted until the job at station 39 has been manually marked as ENDED using the COMPLETE command. You could, for example, have a daily job that only needs to have its JCL or a control statement 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) to be selected DAILY and the staging job (the same job name within the same schedule defined to station 39) to be selected FRI. The job's JCL will always be staged, even though you only change it on Fridays. Remember, the station 39 job has to be manually 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 the COMPLETE command. A job's JCL can be staged (taken from the master JCL file as specified in the LIBTYPE field and placed in the CA-Scheduler active workload) even if staging is not automatic. That is, regardless of whether you had STAGE=YES, a fresh copy of the job's JCL will be restaged. Furthermore, you may want to restage JCL for a job with STAGE=NO. This would be for purposes of changing it due to a rerun condition. You use the RESTAGE command to accomplish this. Keep in mind that it will overlay any JCL 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 for submission. In addition to usual text editing, you can perform some special functions within the editor: Expansion of Driver procedures embedded in the JCL Display of current values of all Driver reserved-name variable parameters in the JCL 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 procedures to 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 is purged 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, and its 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 specify that a schedule or job must wait for a specific global parameter to be set to a specific value before the respective schedule or job can be started or submitted. The three types of global parameters are: numeric, binary (yes or no), and alphanumeric (up to eight characters). Global parameters follow the format:
GBLxnn=value
Where: x= A if the value is a number from 1 to 99999999 B if the value is Y or N C 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 tapes arriving from an off-site location. Suppose this is some accounting data, and we give it a name of HERE-NOW. We have to pick a global variable to be set aside for just this purpose. We can choose GBLC04 since we know no one else is using it. Any schedule or job that needs the data before it can run will have as part of its criteria language the following string of data: GBLC 4=HERE-NOW
9-8 Online Guide
Once the tapes have arrived, an operator sets the value of the global parameter GLBC04 to HERE-NOW. At that point, if any schedule or job is waiting for no other reason but this variable, then the schedule or job starts. From 4.3.9, Globals on page 4-95, update the value of the global variable:
--------------------- CA-SCHEDULER 9. 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 . . . . . . . . . NO NO NO NO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NO NO NO NO . . . . . . . .
xxyy (SCHD) GLOBALS --------------------
. . . . . . . . . . . .
. . . . . . . . . . . . NO NO NO NO . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . NO NO NO NO
Character Values: GBLC 1 - 4 . . GBLC 5 - 8 . . GBLC 9 - 12 . . GBLC13 - 16 . . Enter END to exit.
. here-now . . .
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 and always remain until they are reset to some other value or the active workload is reinitialized. Autoscan does not reset the global parameters. When you initialize the active workload, all global parameters are set to zero (for A-type), NO (for B-type), or null (for C-type). For example above set GBLC04=NULL from globals panel or batch CAJUCMD0. When you define the criteria for a schedule or job, you can specify which global parameters and what values they are to contain for use as predecessor conditions that have 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 GBLxnn predecessor is NOT recognized. Therefore, NOT GBLC01=CICS-UP will have the same 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 Is Correct?
This is a situation where you want to keep running a job over and over again until you get an indication that the rest of the application can run. You may not know how many 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 Definition panel. This means that when the job terminates normally, its status will be set to INTERRUPTED instead of ENDED. You can then run the job by using the RERUN command. Successors of this job will not run until the job is ended manually using the COMPLETE command. At any time during the day, you can go into the status panels and display all jobs that are 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 do something next such as freeing successors to run. Either mark the job as ENDED, or resubmit the job using the RERUN or SUBMIT command. Successor jobs are then handled appropriately. An alternative method of submitting a job repeatedly is by interfacing with CA-Dispatch, CA-Opera, or both. This method has an added benefit in that it can automate the resubmission process. CA-Dispatch can interrogate a report or SYSOUT data produced by a job, and if evidence is found that the job ran without error, a COMPLETE command can automatically be sent to CA-Scheduler. Otherwise, a RERUN or SUBMIT command could be sent, or a message could be sent to a user to verify the output. CA-Opera can interrogate console messages issued by a job, and a procedure like that described for CA-Dispatch can be used to handle the job according to 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 exists when two jobs end up requiring that the other execute first. For example: JOBA requires JOBX to run first. JOBB requires JOBA to run first. JOBX requires JOBB to run first. As you can see, JOBX is a predecessor of JOBA, but cannot run until JOBB has ended. 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 hundred jobs, each with many predecessors. It is extremely difficult to detect a deadlock unless you use the Analyze Report. To obtain the Analyze Report, run the CA-Scheduler utility program (CAJUTIL0) with the batch command ANALYZE. You can check specific jobs and/or schedules or you can give a range of jobs and/or schedules. For example, you can analyze all schedules that begin with the first three characters PAY. Any time you make significant changes to jobs, schedules or both, run this report to ensure that your changes have not introduced deadlocks. You should produce it any time the criteria for a job or schedule is changed. Instead of getting the comprehensive Analyze Report, you can use the LIST=NO or LIST=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-4 and 6.1.2, Analyze Schedule on page 6-6. Another way to detect deadlocks is to generate the Successor Chain List report either from batch or online in the 6.10, Successors on page 6-21. This is especially useful for 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 on Mondays and Wednesdays, but on Mondays JOBA must run first and on Wednesdays JOBB must run first, you could define the jobs as: JOBAJOBAJOBBJOBB1 2 1 2 SCHDA SCHDA SCHDA SCHDA has has has has criteria criteria criteria criteria of of of of MON JOBB- 2 SCHDA JOBA- 1 SCHDA 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 defining SBR, 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 these records.
9.1.3.3 What Effect Does a Deadlock Have?

When job predecessors loop, it is called a deadlock. Deadlocks can have some strange effects on your workload, and seemingly unrelated changes can have unexpected results on how work is selected. Example 1: When CA-Scheduler is evaluating criteria and detects a deadlock, it treats 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 evaluate JOBB first. When it evaluates JOBB, it detects the deadlock with JOBA. Criteria is evaluated as a series of logical TRUE and FALSE conditions, with deadlocks acting as FALSE. Since the criteria of both JOBA and JOBB evaluates to a FALSE, neither job is selected. The order that CA-Scheduler evaluates criteria can have an impact on how deadlocked jobs are selected. During autoscan, CA-Scheduler evaluates all schedules first, before looking at any jobs. The schedules are evaluated in alphabetical order. After all of the schedules have been evaluated, CA-Scheduler evaluates the jobs in each schedule that was selected. Again, the jobs are evaluated in alphabetical order within each schedule. Example 2: This order changes when predecessors are included in criteria. A predecessor must be evaluated before its successor. For example: JOBA SCHDA has criteria of JOBB SCHDA 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 the order 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 before JOBA. While evaluating JOBB, the deadlock with JOBA is detected, so JOBB is not selected. When CA-Scheduler gets back to finishing JOBA, it treats the "JOBB SCHDA" as a FALSE condition. JOBA's criteria, however, has an OR condition. If today 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 evaluated before the jobs in schedule SCHDA. JOBC needs JOBB, so JOBB must be evaluated first. But JOBB needs JOBA, so JOBA is done first. JOBA needs JOBB, so the deadlock is detected. As we saw above, however, the FALSE from the deadlock is ORed with the TRUE from WDAY, so JOBA is selected. CA-Scheduler then backs up to finish JOBB. Since JOBA was selected, JOBB will be selected. And since JOBB was selected, JOBC is selected. Because JOBB was selected, JOBA must wait for it. But because JOBA was selected, JOBB must wait for it! None of the jobs will run without manual intervention. If we moved JOBC from schedule PAYROLL to schedule XYZ (which comes after schedule SCHDA), then only JOBA is selected. This happens because by the time CA-Scheduler gets to JOBC, JOBA and JOBB have already been evaluated as in Example 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. While evaluating JOBB, the deadlock is detected. The criteria for JOBB is then evaluated as NOT FALSE, which is TRUE. JOBB is selected. JOBA's criteria now becomes NOT TRUE, which is FALSE. JOBA is not selected.
Example 5: One last example: JOBA SCHDA has criteria of JOBB SCHDA 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 waiting on 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 on a 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 verify the selection. You can do this by only including the schedules and/or jobs that you desire. This would be the primary reason for running forecasting. Another reason for running forecasting would be to obtain a hardcopy of run books for a specific day, group of days, or schedules and/or jobs within a set of days. These run books contain job information obtained from the database and from workload documentation 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 jobs would run on the real system. Such things as job concurrency, resources, and predecessor constraints are taken into consideration. Simulation produces a set of detailed 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 of the workload. This helps you determine in advance whether the requested frequency of running the application is viable. That is, if you find that the new application cannot fit on Wednesdays without making a lot of jobs late, you could try to run it on another day. It may turn out that it does not absolutely have to run on Wednesdays. The requesting department may be able to run it on Thursdays just as easily. You can make these decisions before establishing policy and before finding that you do not have the resources to handle it. Simulation could also be run to determine the effect of adding new resources, such as tape drives or a faster CPU. By using the OVERRIDE RESOURCE command, you can add the new tape drives, or by using the FACTOR=factor keyword on the same commands, you can cause the simulation to change 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 determine what is going to happen that particular day. It provides you with a plan of what to expect and when to expect it. When you do this, you can optionally use the simulated start times as the early time of the jobs for submission. When you do, it ignores the early 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 actually processing the jobs. To do this you must have CA-JCLCheck installed and active on your system. For details on this function, see the SIMULATE and SYNCHK GROUP commands 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 = TESTLIB in schedule base records. Now run analyze. Then run simulation or forecast (see the discussion 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 will ensure that everything is the way you want it. Once everything looks correct, you can run the application in test mode with the normal 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 all information pertaining to the schedule(s) being requested. From this report, you have a complete list of everything that you keyed in for the new application. You also get a set of error messages that identify predecessor/successor deadlocks as well as any references 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 using the LIST=NO option. To obtain this report, use the JCL described in the Reports Guide. You can also obtain it by issuing the ANALYZE command online in the schedule maintenance and job maintenance panels. This example analyzes all schedules which begin with the characters "APPL1S":
// JOB ... //STEP1 EXEC CAJUTIL //SYSIN DD ANALYZE SCHEDULE NAME=APPL1S //
Step #2: Forecast: Run the forecast component for at least a month of dates and obtain the Job Summary Report (SUMMARY). You do this for the schedules that were built for the new application. Through use of the ONLY command, only the new schedule names are supplied causing just the new application to be analyzed. Through use of the FORECAST command with the object of SUMMARY, you will obtain just the Job Summary Report. The following example contains three schedules to be selected over a one month period with only the Job Summary Report being produced.
// JOB ... //STEP1 EXEC CAJUTIL //SYSIN DD ONLY SCHEDULE N=APPL1S1 ONLY SCHEDULE N=APPL1S2 ONLY SCHEDULE N=APPL1S3 FORECAST SUMMARY MONTHOF= 7 3 //
Step #3: Simulation: Run the Simulation component for each unique day on which the new application will run. During a month, this may only be three days: a daily, a weekly, 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 intended them 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, a good chance exists that they may have a predecessor deadlock. Also, if jobs are backlogged, 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 S command. 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 use TESTPARM on individual jobs' base records to cause the test program to abend, to pass a nonzero completion code, and to have it wait for a number of seconds. By doing that, you can test the effect of abending and failing jobs on the rest of the schedule. After the jobs in the schedule run to your satisfaction, you can now alter LIBTYPE=TESTLIB, in the SBR, to your production LIBTYPE. Also ensure that AUTO SELECT is set to YES. Once you do that, the schedule and its jobs will be automatically selected, starting at the next autoscan. Step #5: Driver: If jobs in a schedule require frequent JCL changes or control statement setup before job submission, you should develop Driver procedures to automate 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 a generalized 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 the reports and the names of the source members in which the source is contained. Database CAJINM01 CAJINM02 CAJINM03 CAJINM04 History file CAJINH04 CAJINH03 CAJINH07 CAJINH05 CAJINH06 CAJINH01 CAJINH02 Active workload CAJINT04 CAJINT07 CAJINT03 CAJINT06 CAJINS06 CAJINS01 CAJINT01 CAJINT02 Workload documentation CAJIND02 CAJIND01 CAJINTD1 Basic job information by schedule Basic job information by station Job criteria by schedule Job step information by schedule Abended job profile Completed job profile Forced and canceled jobs Late job profile Pending job profile Scheduled job status by schedule Scheduled job status by station Abended job profile Canceled jobs Completed job profile Pending job profile Pending schedules report Schedule status Scheduled job status by schedule Scheduled job status by station Documentation directory and list Documentation directory list Documentation with the active workload
9-18 Online Guide
Active workload copy of JCL
CAJING02 CAJING01
Staged JCL directory and list Staged JCL library directory list
Although each of the above reports is written in CA-Earl and provided for you, you have the ability to tailor any of them to your own needs. See the Reports Guide for descriptions of each of these samples in detail.
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 everything from displaying status to shutting down CA-Scheduler. For detailed information about using 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 on page 4-43, and the Command Reference Guide. However, CA-Scheduler offers a number of different places where you can enter the control commands. This is done to make it practical for you. Operator Console: Any control command can be issued from the operator console by directing it to CA-Scheduler. Prefix the command with "F taskname,". The default taskname is CASCHD. Batch Program (CAJUCMD0): Control commands can be issued from a batch program called CAJUCMD0. This means that you could embed a step calling this program in your production JCL that could take certain actions dependent on, for example, condition code settings. Since you have the ability to cause any CA-Scheduler control command to be issued, you could send messages to specific users 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, and just about anything else you can think of. The "Tracking Commands" chapter in the Command 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. The following describes how each command works. FORCE Causes a schedule on the active workload to be started regardless of why it is currently waiting. It also can cause a job to be submitted regardless of why it is currently waiting. You can FORCE a job as long as its status is not STARTED, ENDED, or OS PURGED. You cannot FORCE a job that has JCL already in the queue if the status is SUBMITD, SUBMIT IN PROGRESS, or UNKNOWN.
9-20 Online Guide
SUBMIT and RERUN Cause a job to be resubmitted. It will not wait for an early time or for predecessors: the job is submitted immediately. If the schedule in which the job exists is not in START status, it will be set to START status. Use RERUN or SUBMIT instead of FORCE when a job has abended, failed, ended, canceled, or been interrupted. FORCE is used to make a job start the first time. RERUN substitutes DRIVER restart parameters if LIBTYPE=DRIVER is defined and the JCL is not staged or restaged. The only difference between SUBMIT and RERUN is which Driver parameters they use: SUBMIT uses the normal parameters while RERUN triggers the restart parameters. RUN Causes a schedule or job that exists on the database to be added to the active workload. These schedules and jobs are ones that were not selected in today's workload or they may have been canceled or completed. This is different than FORCE and RERUN in that a fresh copy is obtained and all times, predecessors, and resources are properly evaluated. If the job or schedule is already on the active workload (it would be in a completed or canceled status), then the older one is purged from the active workload. If the job is on the active workload and not completed or canceled, then the RUN command is in error. With the RUN command, you can place the schedule or job in a HELD status. This will give you a chance to take any other manual actions you deem appropriate. Further, when you use the RUN command to pull in a schedule, you can give it a date so that only applicable jobs in the schedule are selected. ADD Causes a job to be added to the active workload. The job does not have to be on the database. If it is on the database, you would use this command instead of the RUN command if you wanted to change any keyword values. Normally, you only use ADD for one-time jobs. You do not have to specify a schedule name. If you do, it will be added to that schedule. If you do not specify a schedule name, it will use a schedule name of $DYNxxxx, where xxxx is the SYSID of the system from which the command was issued. REQUEST and SREQ Cause a REQUESTED schedule or job to be activated. This means it is moved from the INACTIVE queue to the ACTIVE queue. Once in the ACTIVE queue, it is handled normally. The way that a schedule or job is made 'on-request' is by giving it a selection criteria of REQUESTED. A REQUESTED criteria causes the schedule or job to be selected every day and placed on the active workload.
The difference between REQUEST and SREQ is that, with REQUEST, the REQUESTED schedule or job is moved to the ACTIVE queue along with all its successors. The SREQ command handles successors differently: SREQ does not activate a successor if it involves other REQUESTED jobs. A successor of an SREQed schedule or job is not moved to the ACTIVE queue if: The successor's criteria statement contains the keyword REQUESTED or That successor is also the successor of some other REQUESTED job in the INACTIVE queue. 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 database or if it is on the database, but you need to change its keywords. Use RUN to submit jobs in the database if you do not need to change their keywords.
9.1.4.3 When Is the PRED Flag Reset?

When you use the PRED keyword in the criteria language, it indicates that the schedule or job is to wait for a predecessor to complete. When you do not use the keyword PRED, the predecessor is to complete within the autoscan day. When you specify PRED in front of the predecessor, it means the predecessor was to have completed since the last time this schedule or job was run. However, an exception exists. If the PRED is a schedule or job that is in today's workload, it will wait 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 least once between each running of that job. If the job is run weekly, then it must have been closed at least once during the last week. Normally in the selection process (during autoscan), job names cause selection if the predecessor job was selected. When PRED precedes a schedule name or job name, it is not used in determining selection, but is a predecessor condition only. All other criteria 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 system crash, it takes the following steps: 1. Reads the active workload for schedules that belong to the local CA-Scheduler. If MCPU=NO, this is all schedules. For MCPU=YES, this is schedules with the local 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 has not yet started) are marked AUTO RCVRY HELD. These jobs are not submitted by CA-Scheduler until a RELEASE AUTO command is issued. 3. If a job was in SUBMIT IN PROGRESS or SUBMITTED status, the job is changed to UNKNOWN status. CA-Scheduler does not know the current status of the job. 4. If a job was in STARTED status, CA-Scheduler queries JES to determine if the job is still active. If the job is still running, CA-Scheduler leaves the status as STARTED. 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 ended while CA-Scheduler was not active. If an event is received for a job currently in UNKNOWN status, the job's status is updated accordingly as long as CA-Scheduler has received a JOBINIT event for 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 10:05 10:06 10:07 10:08 10:09 Event JOB1 and JOB2 start. CA-Scheduler receives JOBINIT events from CAIENF CA-Scheduler shut down JOB1 ends normally JOB3 starts and ends normally CA-Scheduler started: JOB1 was started, is not currently active, so is marked UNKNOWN JOB2 was started, is still running, so is marked STARTED JOB3 was submitted, so is marked UNKNOWN JOB4 was submitted, so is marked UNKNOWN ENF recovery obtains the following events: JOBTERM for JOB1--JOB1 marked ENDED JOBINIT for JOB3--JOB3 marked STARTED JOBTERM for JOB3--JOB3 marked ENDED
At the end of CAIENF recovery, only JOB4 is still marked UNKNOWN. When it starts, 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 or waiting on predecessors) will be marked ENFDOWN HELD. 2. For jobs that have been submitted but have not yet started, CA-Scheduler will attempt to hold the jobs in JES. CA-Scheduler will show the jobs as ENFDOWN HELD. 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 in JES are released. 2. Jobs that were submitted now have a status of UNKNOWN. CA-Scheduler does not 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 jobs are still active, they are marked STARTED. Otherwise, they are left as UNKNOWN. Note: Any steps that finished while CAIENF was not available are not reported to CA-Scheduler. CA-Scheduler may mark a job as successful when one of these 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 for a normal start of CA-Scheduler. See 9.1.4.4, What Happens If CA-Scheduler is Shut Down? 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 in UNKNOWN status may resolve themselves or may require manual intervention. A normal restart of CA-Scheduler should automatically resolve all UNKNOWN status jobs. If CAIENF is restarted or the system crashes, UNKNOWN status jobs will probably have to be resolved manually. If an UNKNOWN job has successfully completed, you can use the COMPLETE command (with CPU=Y) to inform CA-Scheduler. If the UNKNOWN job needs to be rerun, 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 the command (first four characters) to the left of the schedule or job. You can even issue more than one command at a time. Therefore, the pitfall: Pitfall When keying in a command to the left of a schedule or job in the Status panels, be sure you are on the correct line. It is easy to cancel the wrong job.
While on the subject of control commands in status displays, here is a clarification, not a pitfall. Just remember, when using the commands in this manner, that they are processed sequentially and stop being processed upon encountering an error. For example, there is no reason to cancel a schedule and then the jobs in that schedule.
9.1.6.2 Canceling and Purging a Job

Suppose you have a schedule that consists of four jobs: JOB1 through JOB4. JOB2 requires JOB1 JOB3 requires JOB2 and so on. If you CANCEL JOB3, whether you also PURGE it, JOB4 always waits for JOB3. You can manually override this with a POST 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 because JOB3 has been canceled but is still on the active workload. If you purge JOB3 before issuing the RUN JOB3A command, JOB3A waits for JOB3 to complete. You have to RUN 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 active workload by issuing a RUN command. Pitfall Predecessors for jobs added to this day's production using the RUN command are ignored if they have been canceled by the CANCEL command but not deleted from the active workload by the 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 predecessor criteria as it exists on the database. What this means is that if you have a schedule of four jobs: JOB1, JOB2, JOB3, and JOB5, where JOB2 requires JOB1, JOB3 requires JOB2, and JOB5 requires JOB3. The schedule has been selected and is on the active workload. You then add JOB4 and change the predecessor criteria of JOB5 to now also require JOB4. If JOB5 had not yet started, when it is evaluated to start, it will require 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 CANCEL and PURGE JOB4 and then issue an ADD command for JOB4. Pitfall When changing predecessor criteria on the database for jobs that are selected and are already on the active workload, be aware that the jobs on the active workload will be evaluated based on the most current data on the database. Do not change the criteria of active jobs unless the job is canceled and purged off the active queue and then rerun.
9.1.6.4 Backlogging Jobs Over Two Autoscans in $MVS, $DYN and User Defined Schedules
The subject of backlog is covered in a topic called 10.4, Backlogged Work on page 10-13. When a schedule gets backlogged (autoscan occurred before the schedule completed) 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 the system for 48 hours), when it does finish, the new schedule that is loaded is evaluated for the autoscan day on which it is loaded. This means that if a schedule that is selected on both Monday and Tuesday and has its Monday's version backlogged until Wednesday; Tuesday's version will never be run. That is because the evaluation takes place when Monday's schedule completes which is Wednesday, but it does not run on Wednesday. Always watch backlogged work carefully. Pitfall Backlogged work that goes beyond a 48-hour period can be lost if not monitored carefully.
The $MVS and $DYN schedules also get backlogged if these schedules never go to ENDed status. There is no cleanup for the jobs that are in ENDed status.
9.1.6.5 Resetting Global Parameters

Global parameters are initialized only when the active workload is initialized. They are not reset at autoscan time. Once a value of a global parameter is set, it is only reset when someone actually changes its value to something else. That is, predecessor evaluation of schedules and jobs takes place based upon the current value of the global parameter 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 job that is submitted at a specific time (say immediately following autoscan) that executes the CA-Scheduler program CAJUCMD0 and supplies transactions that set the global variables to the values you want. Therefore, the pitfall: Pitfall A global parameter only gets set. If you want it reset, you must set it to another value. No such thing as resetting a global parameter exists.
Once a global parameter is set to a specific value, all unsatisfied predecessors are re-evaluated. If any schedules or jobs are waiting for that global parameter to take on that value, those global predecessors are marked as satisfied. Satisfaction can only be reversed by changing the GBLxnn parameter and canceling the affected schedule or job 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 set since the last format of the active workload. Formatting of the active workload causes all globals to be reset to their default values.
9-28 Online Guide
Chapter 10. Techniques

This chapter is intended to clarify various areas within CA-Scheduler. In some instances, 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 be concerned 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-controlled jobs or schedules only for predecessor relationships, not for selection: This: JOBA JOBA JOBS JOBS OR OR OR OR JOBA JOBS JOBA JOBS Changes to: JOBA JOBA JOBS JOBS AND AND AND AND JOBA JOBS JOBA JOBS
Rule #2: ORs are respected if the conditions include any kind of keyword (like MVS, PRED, or GDG): This stays as is: MVS JOBA OR JOBB
Rule #3: CA-Scheduler-controlled jobs and schedules are always ignored (when testing predecessors) if they are not eligible for today's workload: (MVS JOB1 AND JOB1 MONSCHD) (MVS JOB1 and JOB1 TUESCHD) or
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 predecessor evaluation at all. If the following criteria is coded: OR (WEEK-DAY AND JOB1 SCHD1) (WEEK-END AND DSN DATASET.ONE)
The job will always be selected because it is always either WEEK-DAY or WEEK-END. However, the predecessor evaluation might not meet expectations. It will be evaluated as: JOB1 SCHD1 or DSN DATASET.ONE As soon as one of these two OR's conditions is true, the job runs. Neither reason code nor the calendar criteria have anything to do with predecessor evaluation, they control only SELECTION. Note: Under Rule #2, the following criteria: OR (WEEK-DAY AND JOB1 SCHD1) (WEEK-END AND DSN DATASET.ONE)
is evaluated for predecessors as: JOB1 SCHD1 OR DSN DATASET.ONE (the OR stays an OR). So if JOB1 runs and ends or the DSN DATASET.ONE gets updated, this criteria is satisfied. The recommended way to get the desired results (different predecessors on different 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 a holiday, then run job on TUES.
10.2.2 Example 2
JOBX JOBX JOBX JOBX JNO= JNO= JNO= JNO= 1 2 3 4 JOBA JOBB JOBC 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 to complete.
10.2.3 Example 3
JOBA JOBB JOBC JOBD REQUESTED JOBA JOBB JOBC
Because JOBA is a requested job, it will be selected every day, but will not run unless requested. Because JOBA is always selected, any other jobs which are a successor to JOBA (in this case, JOBB, JOBC, and JOBD are all successors), then all of these jobs will 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/dependency works under CA-Scheduler. For example, suppose that on any given day, JOB1 and JOB2 and JOB3 are all selected to run. The job dependency would then become 'JOB1 AND JOB2 AND JOB3' since all three jobs were selected. (The 'OR' condition becomes 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 JOB2 are selected, and runs on Saturday and Sunday when JOB3 is selected, then you could use the following criteria: JOBA JNO= 1 JOBA JNO= 2 WEEK-DAY AND JOB1 AND JOB2 WEEK-END AND JOB3
10.2.5 Example 5
JOB NAME JOBA JOBB JOBC JOB CRITERIA WDAY ( WORK DAY ) FRI ( FRIDAY ) 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 JOBB being a predecessor to JOBC. However, if FRIDAY is a WORKDAY, then all three jobs will run with JOBC waiting for both JOBA AND JOBB to finish before being released. In other words, because both JOBA and JOBB were selected on FRIDAY, then JOBC criteria becomes 'JOBA AND JOBB' rather than 'JOBA OR JOBB'.
10.2.6 Example 6
JOB NAME JOBA JOBB JOBC JOBD JOB CRITERIA DAILY ( DEFAULT ) MON ( MONDAY ) WED ( WEDNESDAY ) (JOBA AND JOBB) OR JOBC
On MON, JOBA AND JOBB AND JOBD will run, with JOBD waiting for both JOBA AND JOBB to complete. On WED, JOBA AND JOBC AND JOBD will run, with JOBD waiting for both JOBA AND JOBC to complete. Remember that the 'OR' condition becomes an 'AND' condition when dependency 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 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 CRITERIA Evaluated only at autoscan time, these control whether a job is selected for today's workload. For example: SUN WEEK-DAY WDAY JAN 12TH JOB1 SCHD1 PREDECESSOR CRITERIA Evaluated both at autoscan time and continuously during the daily processing, 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 selection and predecessor criteria. If a job's criteria is 'JOBA SCHD1', it means that the job will only be selected when JOBA IN SCHD1 is selected, the job will not run until JOBA completes.
Selection Criteria are evaluated at autoscan time, since they play a part only in deciding if the job is selected today. When you specify the following criteria record for 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 have already been evaluated. Assume JOBC is also in Monday's workload. The criteria appears 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 OR condition is true. The OR in the above criteria is respected because of GBLC02 specification. ORs are changed to ANDs when their parenthesized criteria statements involve only CA-Scheduler controlled jobs or schedules. Any other criteria (like GBLC02 OR PRED 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 an INACTIVE queue, in case they are needed. They remain in an INACTIVE status until they are activated by a control command. This means that you cannot determine in advance whether the schedule or job will be needed on any particular day. You define an on-request schedule or job using REQUESTED, a Gregorian calendar reserved word, in its selection criteria. When the autoscan process runs, all REQUESTED schedules and jobs are selected along with their successors and placed in the CA-Scheduler active workload in an INACTIVE queue. The only way they can be removed from the INACTIVE queue is using the control command REQUEST or SREQ. When removed from the INACTIVE queue, they are placed in the ACTIVE queue and will then be handled as normally selected jobs. An important difference between the REQUEST and SREQ commands is that REQUEST also places the successor schedules and jobs in the ACTIVE queue. The SREQ command handles successors differently: SREQ does not activate a successor if it involves other REQUESTED jobs. A successor of an SREQed schedule or job is not to be moved to the ACTIVE queue if: The successor's criteria statement contains the keyword REQUESTED or That successor is also the successor of some other REQUESTED job in the INACTIVE queue. All schedules and jobs that have not been requested by the next autoscan are purged from the CA-Scheduler active workload, regardless of what BACKLOG values they had defined. A guideline you should follow when using the REQUESTED keyword is: To ensure that simulation produces reason codes which match those produced by CA-Scheduler, specify REQUESTED after job and schedule names in selection criteria whenever possible. 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 that the jobs described are all contained in the same schedule. Although you should always specify schedule names with job names in criteria statements, they are omitted in the examples below to keep things simple.
10.3.2.1 Example 1
Job JOBA JOBB JOBC Criteria REQUESTED JOBA JOBB
In this example, all three jobs will be placed in the INACTIVE queue every day.
10.3.2.2 Example 2
Job JOBA Criteria MON AND REQUESTED
JOBA will be placed in the INACTIVE queue every Monday.
10.3.2.3 Example 3
Job JOBA Criteria MON OR REQUESTED
This example follows the same rules as MON when selected on Monday and treated as a normal job (meaning that on Mondays, it is placed in the ACTIVE queue and it does not have to be requested). Any other day, it will be treated as a requested job.
10.3.2.4 Example 4
Job JOBA JOBA1 JOBB Criteria REQUESTED None JOBA OR JOBA1
In this example, all jobs will be selected. JOBA and JOBB will be placed in the INACTIVE queue. JOBB is placed there because JOBA is the first predecessor specified and it is a REQUESTED job. The ordering of these predecessors is important as 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 without requesting 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 at the next autoscan.
10.3.2.5 Example 5
Job JOBA JOBA1 JOBB Criteria REQUESTED None JOBA1 OR JOBA
This example is the same as the one above except for the order of the predecessors on JOBB. All three jobs will be selected, but only JOBA is placed on the INACTIVE queue. This is because JOBB got selected because of JOBA1 which is selected whenever 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 next autoscan.
10.3.2.6 Example 6
Job JOBA JOBB Criteria REQUESTED JOBA AND REQUESTED
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) will be moved to the ACTIVE queue.
10-10 Online Guide
When the operator command SREQ J N=JOBA is issued, only job JOBA will be moved to the ACTIVE queue. JOBB will not be moved since it has the criteria AND REQUESTED which must be satisfied. It is not satisfied using the SREQ operator command with its predecessor JOBA. To move JOBB to the ACTIVE queue, in this case, use the REQUEST or SREQ command.
10.3.2.7 Example 7
Job JOBA JOBB Criteria REQUESTED MON OR JOBA
On Mondays, JOBB will be added to the ACTIVE queue and will not wait for JOBA unless it is also in the ACTIVE queue. That is, JOBA will not be considered a predecessor of JOBB unless JOBA is requested with the REQUEST or SREQ command before JOBB is submitted. Once JOBA and JOBB are both in the ACTIVE queue, CA-Scheduler will not submit JOBB until JOBA has completed.
10.3.2.8 Example 8
Job JOBA JOBA1 JOBB JOBC Criteria REQUESTED REQUESTED JOBA OR JOBA1 JOBA
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 be moved to the ACTIVE queue. This occurs with JOBB and JOBC since neither of them are requested jobs, but rather each of them only require JOBA to be selected. If JOBA1 were the requested job, then JOBA1 and JOBB would be the ones moved to the ACTIVE queue. When the operator command SREQ J N=JOBA is issued, JOBA, JOBB, and JOBC will be moved to the ACTIVE queue having the same result, in this case, as issuing the REQUEST command. If the operator command SREQ J N=JOBA1 were issued, only JOBA1 would be moved to the active queue. This is because JOBB was selected today for reason code 01 (the successor to JOBA).
10.3.2.9 Example 9
Job JOBA JOBA1 JOBB JOBC JOBD Criteria REQUESTED REQUESTED JOBA OR JOBA1 JOBA AND REQUESTED JOBA AND JOBA1
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 when the SREQ command is used with JOBA. In this case, JOBB is still moved to the ACTIVE queue, but JOBC and JOBD are not. That is because JOBC's criteria includes the REQUESTED keyword, and JOBA1 (JOBD's predecessor) was REQUESTED. Issuing the command SREQ JOBC will move JOBC to the ACTIVE queue. To move JOBD to the ACTIVE queue, just SREQ both JOBA and JOBA1.
10.3.2.10 Example 10
Job JOBA JOBB Criteria None REQUESTED
Both of the above jobs are in a schedule called SCHDA which has a criteria of REQUESTED. At AUTOSCAN time, both JOBA and JOBB are placed in the INACTIVE queue. When the control command REQ S N=SCHDA is issued, JOBA and JOBB are moved to the ACTIVE queue. When the control command SREQ S N=SCHDA is issued, only JOBA is moved to the ACTIVE queue.
10-12 Online Guide
10.4 Backlogged Work

Sometimes, schedules, jobs, or both do not complete the day on which they were selected. This means that they may be candidates for being backlogged. But first, we will 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 next morning. 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 terms of CA-Scheduler, a day is the 24-hour period that starts with the time that you run autoscan. We will term this the production day or autoscan day. Schedules and jobs that do not complete on the production day on which they were selected can be carried over to the next production day. They are then called backlogged 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. When autoscan is initiated and it is determined that a schedule is still active (it has not finished running yet), the schedule will be backlogged. Any job in the schedule that has completed, been canceled, or purged will retain its status. If a job has been defined with BACKLOG=YES, it will be backlogged if it had not started. That is, it will be allowed to run. If a job in the backlogged schedule has been defined with BACKLOG=NO and still has a status of WAITING, it will be canceled with a status called NO BACKLOG CNCL. Once all jobs in the backlogged schedule have been completed or canceled, the schedule will be marked as complete. If the same schedule was also selected on the current production day, then it and its associated jobs will be placed on the CA-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 backlogged by two autoscans), then when it completes, the schedule to execute on the completed day is loaded to the active workload. For example, if Monday's schedule gets backlogged and completes on Wednesday, Tuesday's schedule will never be run. Schedule Backlog: When BACKLOG=YES or NO is specified on a schedule definition, it acts only as a default for jobs in that schedule when BACKLOG is not specified on a job. Then it is handled as described above. Requested Jobs And Schedules: Jobs and schedules that are on-request and are still in the INACTIVE queue at autoscan time will be purged, regardless of their BACKLOG 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 was canceled at the end of the day because it had not yet started and it was defined as, or defaulted to, BACKLOG=NO. The jobs carrying this status have not yet started and will not be run. As soon as the schedule ends, they will be purged. When history is generated for these NO BACKLOG CNCL jobs, they will show up on the 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 production day, the one being selected will not be placed onto the CA-Scheduler active workload until the backlogged one completes. Only one copy of a schedule at a time will be kept on the active workload. Therefore, if for some reason a schedule occurs daily and 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's schedule gets backlogged until Wednesday, Tuesday's schedule will never be run. This is because when Monday's schedule finishes and Tuesday's is brought in, it is evaluated 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 are jobs that are defined in the database and were selected as part of the day's production during 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 discussion describes how jobs can be moved as a group from one CPU to another when one CPU goes down. In this topic, we will discuss how you determine which jobs have abended, what type of manual actions you can take, what type of automatic facilities are available within the database, and then discuss how you could use Driver to automate the recovery process. 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-11 installed and active. When the RERUN or SUBMIT commands are used from the status display on a job that is known to CA-11, the RERUN or SUBMIT panel is displayed 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, the CA-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 to track your jobs and maintain restart information in case a job abends. However, since the RMSPROC is inserted automatically by CA-Scheduler, no JCL maintenance 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 (Catalog Management Table). The CMT contains information which allows CA-11 to restart jobs from the correct point if they abend. CA-11 also cleans up data sets that were created or affected by the jobs before they abended. Also, it keeps track of GDG bias so that restarts of the jobs are performed at the correct version. All of this tracking permits job restart with no JCL editing. If a job that specifies INSERT RMS PROC = YES abends, it can be restarted through CA-11 using one of two CA-Scheduler commands: SUBMIT or RERUN. Alternatively, the job can be completed or canceled. Although CA-Scheduler commands are used to handle the job, the CA-11 CMT is updated accordingly for subsequent runs of the job. Also, CA-11 restart parameters can be passed through the CA-Scheduler commands. This allows you to override CA-11 parameters whenever necessary. For details on how to restart a job through the CA-Scheduler CA-11 interface, see 4.3.16, Rerun Job Command on page 4-142 or 4.3.21, Submit Job Command on page 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 display automatically. The status conditions that would indicate recovery may be necessary include: 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: Status Code ABENDED Description The job has abended with an abend code such as S0C1. It can be rerun by using the RERUN or SUBMIT control command. The job has been canceled by an operator using the CANCEL or CP control command. This job can be run again by using the RUN, RERUN, or SUBMIT command. The job has failed with a condition code that exceeds the value specified in the FAIL CODE field when defining the job or has failed on a JCL error. It can be rerun by using the RERUN or SUBMIT control command.
OPERATOR CANCLD FAILED
To recover any job, its JCL is either in the active workload or can be placed there by the RESTAGE command. Once it is in the active workload, you can modify it and resubmit the job.
10.5.3 Automatic Recovery Options

When defining a job to the database, a field called ABEND can be used to aid in automatic recovery of a job. You can specify four options in this field. They include: Option ABORT CONT Description Indicates that successors to this job do not have this predecessor satisfied. This is the default value. Indicates that successors to this job are to be handled as if the job terminated normally because this predecessor has been satisfied. Indicates that successors to this job will not be posted as satisfied if this job abends. A backout job will be submitted automatically if you specified a value for the BACKOUT installation option. CA-Scheduler adds a new job tracking record for the backout job. Indicates that the schedule name provided is to be processed. This is a predefined recovery schedule that will be automatically processed should the job abend and the abended job will follow the same process as ABORT.
BACKOUT
schedule name
10-16 Online Guide
If a recovery schedule is defined, it could contain a job that executes the CAJUCMD0 program 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, or ADD control commands for recovering the abended job. This technique is described in the preceding topic of this chapter. When you define a recovery schedule, you should attempt to use some sort of naming convention so that any recovery schedule can be recognized quickly. For example, begin all recovery schedule names with RR. Another way to be sure that jobs that need recovery do not go unnoticed is to use the message facility. That is, you can specify up to four users to send messages to if the job 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 Schedule Messages panel on page 5-15 and Job Messages panel on page 5-46.) Keep in mind that 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 the variations 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 through the automated process that exists today, that Step 5 relies on the temporary data set that was created in Step 2. Therefore, the data sets that were created in Steps 2, 3, and 4 must be removed from the OS/390 catalog. What cannot be determined through any automated process is that the data set created by Step 1 and used for input by Step 2 was created using incorrect input. Herein lies the problem of automating the restart/recovery process. Many options are available to a data center to effect proper restart/recovery either using native OS/390 JCL, or a more automated method using Driver. Driver is the JCL management 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 manual intervention to a minimum. Abend recovery cannot be totally automated, however, because it is impossible to plan for every situation. Realistically, some manual intervention is involved in a program restart. Consideration should be given to keeping the 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 a generation data set that was created in a prior step, you must suffix the data set name with the string (+1). The generation data group's index is updated at job-end and not step-end. In a restart situation where the restart takes place after the data set has been created, all of the (+1) generation pointers must be changed to (0); all the (0) must be changed to (-1). Three ways exist to reset relative generation pointers. First, the values could be explicitly coded in the JCL. This is the most straightforward method 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 the generation members being symbolic values. The symbolics could then be overridden at execution with values supplied by the starter JCL. The drawback to this approach is that in a large program, quite a number of overrides could be required to restart the program correctly. The third, and last, method uses the Driver component of CA-Scheduler. The OS/390 symbols are made into Driver variables. Driver statements would be used to determine whether it was production or rerun, and where the restart should begin. This is the least 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 //STEP1 //SYSPRINT // //STEP2 //TAPEIN // //SYSPRINT
JOB (acctg),'DASD BACKUP',CLASS=A EXEC PGM=DASDBKUP DD DSN=DASD.BACKUP(+1), DISP=(NEW,CATLG,DELETE) EXEC PGM=LISTDASD DD DSN=DASD.BACKUP(+1), DISP=OLD DD SYSOUT=A
This is a two-step job where the first step creates a backup tape of data stored on disk and the second step prints a report using the backup tape as input. The backup data set is a generation data set (DASD.BACKUP) since it is suffixed with (+1), the bias pointer. Thus, when the step ends normally, the data set will be cataloged as DASD.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 parameter and 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) //STEP2 EXEC PGM=LISTDASD //TAPEIN DD DSN=DASD.BACKUP( ), // DISP=OLD //SYSPRINT DD SYSOUT=A
The above would have been the case if the program abended in the second step and where the tape was created in the first step properly. A restart must be submitted to print the report.
10.5.4.3 Example 2
In this example, the body of the JCL is a JCL procedure and uses symbolics instead of hard-coding the generation bias numbers.
//DASDBKUP //STEP1 //SYSPRINT // //STEP2 //TAPEIN // //SYSPRINT
PROC GENP1='+1',GENP2='+1' EXEC PGM=DASDBKUP DD DSN=DASD.BACKUP(&GENP1), DISP=(NEW,CATLC,DELETE) EXEC PGM=LISTDASD DD DSN=DASD.BACKUP(&GENP2), DISP=OLD DD SYSOUT=A
This is a standard OS/390 cataloged procedure. Except for the symbolics, the JCL is the same as Example 1. The starter JCL for the normal execution would be:
//BACKUP //BKUP
JOB (acctg),'DASD BACKUP',CLASS=A EXEC PROC=DASDBKUP,GENP1='+1',GENP2='+1'
This would submit the same JCL seen in Example 1 with the symbolics properly resolved. 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 properly resolved.
10-20 Online Guide
Chapter 11. Remote Scheduling

Jobs with a node ID of *REMOTE represent work on a remote non-OS/390 platform running Unicenter TNG or CA-Scheduler Agent. The work is scheduled by CA-Scheduler, then initiated and tracked by Unicenter TNG or CA-Scheduler Agent on the remote platform. When Unicenter TNG or CA-Scheduler Agent reports that task complete, 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 remote systems: the node name and the command to be executed. You may also specify a user ID, password, and a domain. CA-Scheduler passes the information to Unicenter TNG or CA-Scheduler Agent using CAICCI, one of the Unicenter TNG Framework for OS/390 Common Services. All systems on which CA-Scheduler is to schedule work must be defined (connected) to CAICCI and must be running either Unicenter TNG or CA-Scheduler Agent. Work on remote systems is initiated by a command. The command can execute a script on the remote system, a program, or anything else that can be started with a command. Parameters can be passed on the command. Uppercase and lowercase characters 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 reads the CAICCI node name and the command from the data set where the JCL is normally stored. For example, if the job is defined as libtype PDS, the information is read from JCLMASTR.
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 take any 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. 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 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 uppercase or 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, the delimiter 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 NOT identical: command='commandstring' command='COMMANDSTRING' Command strings can be up to 255 bytes in length. Use multiple command statements to build long command strings. The strings are concatenated together without any intervening spaces or other characters added. For example: command='command' command='string' would produce the command string of "commandstring". If a blank was wanted between 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 to delimit between the command and any parameters. The following command statement would send two parameters: command='command parm1 parm2' If a parameter needs to include a space, use quotes around that parameter. The following 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 entire string "quote in parentheses (")" will be sent as one parameter. Note: The interpretation of parameters is platform and command specific. Some platforms may treat a single parameter as multiple parameters if the parameter includes blanks.
11.1.4 Domain
On some platforms, such as Microsoft Windows NT, users may be defined within domains. See the documentation supplied with the target operating system and with Unicenter 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. 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 closing delimiter. Domain names may be up to 15 characters long. Note, however, that the requirements of the target system may restrict the length. The domain name is passed to Unicenter TNG exactly as entered. If the target system is 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 under this 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 (that is, CAIJGEN SUBUID order, CAIJ$SEC options). User='userid' The user statement must begin with the characters "USER=" 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 closing delimiter. User IDs may be up to 32 characters long. Note, however, that the requirements of the target 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 is checked. If SUBROOT is set to YES, the submission is allowed. Otherwise, the submission 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 is case-sensitive, enter the user ID in the expected case. Unicenter TNG may need to be configured to support submission of work in other than the default user ID. See the Unicenter TNG documentation for the target platform for more information. User IDs on the target platform may need special authorization to be used by Unicenter TNG. See the Unicenter TNG documentation for the target platform for more 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 closing delimiter. Passwords may be up to 14 characters long. Note, however, that the requirements of the target system may restrict the length. The password is passed to Unicenter TNG exactly as entered. If the target system is case-sensitive, enter the password in the expected case. Unicenter TNG may be configurable to require or not require passwords. See the Unicenter 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 RS6000 machine 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 in any 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 logged on with a password of "abcd".
11-6 Online Guide
Glossary
This glossary defines terms used in all volumes of the CA-Scheduler documentation. But sometimes one new term leads to another. To help you grasp these new ideas quickly, we have used italics to highlight related terms worth cross-referencing. its jobs because they are listed in the USERS field on that schedule's base record. (Users with Supervisor or Manager authority level do not require specific authorization to maintain or control schedules.) autoscan. The automatic selection of a day's workload. CA-Scheduler scans the database at a set time every day to determine the workload for the next 24 hours. autoscan day. The 24-hour period starting with autoscan. Also called the production day. AUTOTIME. The time when CA-Scheduler automatically scans its database for workload selection. This defaults to midnight, but may be modified with the AUTOTIM installation option. Also called autoscan time. available. Ready for processing by CA-Scheduler. A schedule is available (ready to start) when its early start time has been reached and all of its predecessors have been satisfied. A job is available (ready to be submitted) when its schedule has started, the job's early start time has been reached, all the job's predecessors have been satisfied, and the resources defined for that job are available (not in use).
A
abend. Abnormal ending. An early termination of a program due to an error. accounting day. A day designated on a date table as part of a cyclic production, sales, or accounting period. accounting period. One or more accounting days. accounting week. A week containing at least one accounting day. active. Schedules and jobs that are: waiting at any workstation for predecessors, start time, or defined resources waiting at a non-CPU station to be started manually submitted, held, or started completed, interrupted, abended, or failed The opposite of inactive. active workload. The CA-Scheduler file that contains the copy of current production. The default name of the file is CAIJTRK. array. A variable parameter with multiple values. authority level. One of three different types of access assigned to users using the TYPE field on a user record. Each authority level places different restrictions on what those CA-Scheduler users can do. See General, Supervisor, and Manager authority levels. authorized users. Users with General authority level who are allowed to maintain and control a schedule and
B
backlog. Work that was not completed one day and was carried over to the next. References to a backlogged schedule or job pertain to a previous day's schedule or job which is included in today's workload. backout job. A replacement job that is automatically submitted by CA-Scheduler when a job abends provided that ABEND=BACKOUT on the abended job's base record. base record. The record which is required to define a schedule or job. There is a schedule base record (SBR) and a job base record (JBR).
Glossary X-1
batch command. Any command that is issued by executing a CA-Scheduler program through standard OS/390 JCL.
character string. One or more alphabetic, numeric, or special characters, usually enclosed in delimiters. code. A number that explains why a schedule or job was selected. Numbers from 01 to 79 correspond to the position of a reason in the criteria statement. Numbers from 80 to 99 are special reason codes which indicate that selection was based on default daily processing, calendars, or manual additions. code record. The record that assigns time specifications which vary according to the reason a schedule or job is selected for processing. There is a schedule reason code record (SRC) and job reason code record (JRC). conditional expansion. Driver retrieves and expands just some of the steps in a procedure depending on conditions at the time of expansion. control command. A command used to monitor or control the workload. Also known as operator command. criteria record. The record that determines when a schedule or job is to be selected for processing and lists the predecessors for the schedule or job. There is a schedule 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 before selected schedules can start or selected jobs can be submitted See selection criteria, predecessor criteria, and selection. criteria vocabulary. Reserved words used in CA-Scheduler's criteria statements. cross-node dependency. Predecessor events that occur at other nodes in a CA-Scheduler NJE environment. These events can be the close of an output data set or generation data group, the start or end of a job under CA-Scheduler's control, or the normal completion of a job not under CA-Scheduler's control. cyclic scheduling. Scheduling a schedule or job at regular intervals regardless of which day or month it is (for example, every six weeks).
C
CA-11. Computer Associates rerun/restart product. CA-Earl. Computer Associates Easy Access Report Language. A subset of this product that allows you to customize reports is provided with CA-Scheduler. CA-JCLCheck. Computer Associates JCL validation product. CAIRIM. Computer Associates Resource Initialization Manager. This component is included with CA-Scheduler and oversees the installation and maintenance of Computer Associates OS/390 products. CAISERV. A Computer Associates diagnostic facility that allows you to determine the current values of installation options and to produce reports for use in troubleshooting problems. calendar. An alternative method for identifying when a schedule or job should be selected as part of the day's workload. With this method, you define several calendars, each designating different days when schedules or jobs should be selected (Mondays, month-ends, pay days, etc.) The database shows which calendar to consult when selecting a schedule or job. calendar mechanism. One of three date references CA-Scheduler consults when selecting the day's workload. The Gregorian calendar tells CA-Scheduler what day of the week it is so, for example, jobs can be selected on Mondays. Calendars explicitly define which days to select schedules and jobs so you can run jobs on random dates. Date Tables define workdays, holidays, accounting days and accounting periods so, for instance, CA-Scheduler can select jobs on the last workday of the month.
calling statement. The EXEC statement which retrieves a procedure from the Driver procedure library and submits it to JES.
X-2 Online Guide
D
database. The CA-Scheduler database that stores records containing definitions of user IDs, stations, schedules, jobs, and resources. The default name of the database is CAIJMST. date table. Identifies workdays, holidays, accounting days, 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 versions of a date table by applying different prefixes. Date Translation Table. A report that shows when workday, accounting, and Gregorian conditions are true. deadlock. The stalemate that occurs when jobs are predecessors to each other. Deadlocked jobs never run because their predecessor conditions are never satisfied. Also called a predecessor loop. default. A value or action that CA-Scheduler supplies automatically unless you specify some other alternative. delimiter. A special character that precedes and follows a character string. In 'this example', the delimiter is a single quote (') identifying a character string consisting of two words: this example. documentation. Entries in the CA-Scheduler workoad documentation (CAIJDCM) that provide information to users. documentation batch command. A command issued through batch using the CARUTIL0 program that is used to maintain members in the workload documentation. Driver. Computer Associates JCL manipulation component of CA-Scheduler.
explicit predecessor. A predecessor that is specifically defined in the criteria statement of a schedule or job. Explicit predecessors can be either of two types: Selection-defined explicit predecessors are predecessors that also define selection criteria. They can be schedule or job names used with or without the keywords SCD and START. Keyword-defined explicit predecessors are ignored in the selection process and always include one of the following keywords: DSN GDG GBLxnn MVS NJE PRED When START or SCD are used with PRED or NJE or MVS, the result is a keyword-defined predecessor that is ignored during the selection process.
F
forecasting. Producing reports that show which schedules and jobs will be selected for processing on any given day(s).
G
General authority level. The default authority level assumed for all users unless Supervisor or Manager is specified. 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's authority: The CONNECT field on each user record defines which stations that General user is authorized to access. The USERS field on a schedule's base record defines which General users can access that schedule and its jobs. General users are prohibited from doing anything involving stations or schedules for which they are not authorized. See authorized users as well as Supervisor and Manager authority levels. generic list. A group of schedules or jobs whose names begin with the same characters. To display, list, or analyze a generic list, specify the common characters followed by an mask character (*).
E
events. Occurrences that CA-Scheduler monitors so it knows when predecessor conditions have been satisfied. Some of the events that CA-Scheduler monitors are schedules and jobs starting and ending, the close of output data sets and generation data groups, and what time it is. expansion. Driver replaces an EXEC statement with the contents of a cataloged Driver procedure.
Glossary X-3
global parameter. A user-controlled variable that defines a predecessor condition in criteria statements and can assume arithmetic, binary, or character values. See keyword-defined explicit predecessors. Gregorian calendar. The standard 12-month calendar which CA-Scheduler references to interpret certain selection keywords (like WEEK-DAY) in criteria statements. You can use Gregorian calendar keywords without defining a date table or calendars. Gregorian date. A date shown as mm/dd/yy (American format) or dd/mm/yy (European format).
J
JBR. Job base record. This record is required to define a job. JCR. Job criteria record. This record determines when a job is to be selected for processing and lists the predecessors for the job. JIR. Job information record. This record provides descriptive information for a job. JMR. Job message record. This record determines who receives messages when a job begins, ends, starts late, abends, is purged, or is interrupted. JNR. Job node record. This record is used to specify other nodes to be notified when a job starts or ends. job. Usually refers to work submitted to the CPU for processing. However, CA-Scheduler expands the scope of that definition to encompass all data processing tasks under CA-Scheduler's control. This can include pre-CPU tasks such as data entry, jobs that run on the CPU, and post-CPU tasks such as report distribution. job number. One of four fields used to uniquely identify each job definition. When a job needs to run more than once during a production day, create a job definition for each iteration by giving them different job numbers. job path. All the stations where a job is processed as it moves through the data center. JRC. Job reason code record. This record is used to assign time specifications which vary according to the reason a job is selected for processing. JRR. Job resource record. This record allows you to define the resources necessary to run a job. JSR. Job step record. This optional record allows you to define job step information used to determine a job's failed status. Julian date. A seven-digit number of the form yyyyddd, where yyyy is the year and ddd is the relative day of the year (from 001 to 366). For example, 2003305 is November 1, 2003.
H
history file. The CA-Scheduler file that contains history records for schedules and jobs. history record. The record that contains statistics of past runs of schedules and jobs.
I
implicit predecessor. Predecessors that are not defined on a job's criteria statement. Because CA-Scheduler enforces workstation sequences, pre-CPU jobs (such as data entry and JCL staging) are implicit predecessors for CPU jobs. Likewise, CPU jobs are implicit predecessors for post-CPU jobs (such as report distribution). See sequence enforcement. inactive. Schedules and jobs that are: defined as REQUESTED but not activated by a REQUEST or SREQ command and the successors of REQUESTED schedules and jobs Schedules and jobs in the INACTIVE queue at autoscan time are purged regardless of what values have been defined for BACKLOG. The opposite of active. information record. The record that provides descriptive information of schedules and jobs. There is a schedule information record (SIR) and job information record (JIR). installation option. A value specified on the CAIJGEN installation macro when CA-Scheduler is installed. This value controls scheduling operations throughout the data center unless it is overridden by values in the CA-Scheduler database.
X-4 Online Guide
K
keyword-defined explicit predecessors. Predecessors that are ignored in the selection process and always include at least one of the following keywords: DSN GDG GBLxnn MVS NJE PRED
schedules and jobs, define and maintain any database records, and issue all commands. See General and Supervisor authority levels. mask character. An asterisk (*) or question mark (?) included anywhere in a search string. Used when you want to display all records with names that share common characters. ? indicates that any character can be substituted at this point in the search string, but just one character can be substituted for each question mark. That makes ? a positional mask character. * indicates that CA-Scheduler will accept anything occurring at this point in the search: an * can signify any number of characters. For example: P? P* ?ACC? displays record names of just five letters with ACC in the middle *ACC* displays just those records with ACC anywhere in their name See generic list. message record. The record that determines who receives messages when a schedule or job begins, ends, or starts late or when a job abends, is purged, or is interrupted. There is a schedule message record (SMR) and job message record (JMR). displays all record names of just two characters starting with P displays all records that start with the letter P
The keywords START or SCD can also be used with MVS, NJE or PRED.
L
levels of predecessors. In terms of a family tree, the number of preceding "generations" (schedules or jobs) with defined predecessors. The number ending each job name 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 different predecessors, but only three levels of predecessors. Levels of predecessors is one factor CA-Scheduler uses when ordering the workload. Schedules and jobs with fewer levels of predecessors are evaluated ahead of those with more.
N
nesting. One procedure calls (retrieves) another procedure which can, in turn, call other procedures. network. Two or more interconnected systems (nodes) participating in a VTAM network or communicating using BSC lines (binary synchronous communication). node. Each location in a network having one CPU or multiple CPUs with multi-access spooling facility. node record. The record that specifies other nodes to be notified when a job starts or ends. nonscheduled job. An OS/390 job that is neither controlled nor submitted by CA-Scheduler.
M
mailbox. The common area for sending CA-Scheduler messages so that they can be viewed by many users without being deleted. Manager authority level. The highest authority level which allows these users to access all stations, control all
Glossary X-5
null value. A defined value of nothing which has been added to the database using the keyword NULL.
O
on-request. Schedules or jobs having the keyword REQUESTED in their criteria statement. These schedules and jobs are selected every day in case they are needed, but they remain inactive until activated by the REQUEST or SREQ command. operator command. A command used to monitor or control the workload. Also known as control command.
predecessor loop. The stalemate that occurs when jobs are predecessors to each other. These deadlocked jobs never run because their predecessor conditions are never satisfied. Also called deadlock. procedure. One or more statements cataloged under a procedure name as a member of the CA-Driver procedure library. procedure library. The library that stores Driver procedures. production day. The 24-hour period starting with autoscan. Also called the autoscan day. prompt. A word on a screen that reminds you to supply a value. prototype calendar. A master calendar that defines all of the year's holidays and tells when to reschedule jobs that would normally be selected on holidays. These holidays and rescheduling instructions are automatically applied to all calendars defined for that year. prototype definition. An existing definition whose values are used as defaults for a new definition. Any fields left blank while defining a new record are assigned values from the prototype definition. public schedule. A schedule that can be maintained by all users because no value is specified in the USERS field of the schedule base record.
P
path. All the stations where a job is processed as it moves 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 date table. post-CPU job. Work scheduled after CPU processing to wrap 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 CPU processing. Examples include daily shipment of input forms, data entry, and JCL setup. See station. predecessor. An event that must happen before the next job can begin. CA-Scheduler's criteria statements allow you to define predecessors for schedules and jobs. That means schedules and jobs in today's workload do not run until their predecessors are satisfied. If JOBA is a predecessor of JOBB, JOBB does not run until JOBA runs to completion. Predecessors fall into several different categories that are defined in this glossary: explicit predecessors implicit predecessors keyword-defined explicit predecessors selection-defined explicit predecessors
Q
queue. One of the various job categories that depend on the status of the jobs.
R
reason. Why a schedule or job is selected for the day's workload. 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.
predecessor criteria. All of the predecessors defined for a schedule or job in its criteria statement. These predecessor conditions must be satisfied before a schedule can start or a job can be submitted.
RECS line. The line on the bottom of the Schedule Definition (SCHD-SU) panel and Job Definition (SCHD-JU) panel that provides access to panels for optional schedule and job records.
X-6 Online Guide
reserved-name variable parameter. One of a set of Driver variable parameters which are predefined by Computer Associates. resource record. The record which specifies the resources that are used to run a job. route delay time. The delay between the time a job ends at one station and starts at the next station. route station. A workstation defined for purposes of receiving reports rather than performing data processing tasks. run book. A report that contains detailed information on the current day's workload.
selection criteria. There are two distinct meanings: All the reasons why a job or schedule can be selected as defined in its criteria statement. If a calendar is also defined for a schedule or job, CA-Scheduler bases selection on the calendar and ignores the selection criteria. See selection. The keywords that are used in the maintenance panels to limit the directory to be displayed. selection-defined explicit predecessor. A predecessor that also defines selection criteria. They are schedule or job names used with or without the keywords SCD and START. When START or SCD is used with PRED or NJE or MVS, the result is a keyword-defined explicit predecessor that is ignored during the selection process. sequence enforcement. Making sure schedules and jobs are processed in the right order. See implicit predecessor. shared DASD. A hardware configuration that allows two or more operating systems to use the same disk files. This situation allows several operating systems to use the same set of CA-Scheduler files at the same time. However, when operating systems share CA-Scheduler files, it does not imply that they also share spool files. simulation. Answers the question "what if." It shows how processing is affected by changes in workload or hardware failure. Simulation also totals how long each job usually takes to project when the workload is likely to finish. SIR. Schedule information record. This record provides descriptive information for a schedule. SMF ID. Four characters that identify the System Management Facility running on OS/390. This value usually corresponds to the JES SID. SMR. Schedule message record. This record determines who receives messages when a schedule begins, ends, or starts late. spin locks. The method CA-Scheduler uses to protect the integrity of its files when two or more operating systems share them. See shared DASD. SRC. Schedule reason code record. This record is used to assign time specifications which vary according to the reason a schedule is selected for processing. staging. CA-Scheduler's three-step process for tailoring production JCL:
S
SBR. Schedule base record. This record is required to define a schedule. schedule. A group of related jobs that: run on the same days or belong to the same application or have the same operational dependencies or belong together because your production jobs are organized that way
The payroll department's month-end jobs could make up a schedule. The schedules and jobs selected each day comprise the workload. SCR. Schedule criteria record. This record determines when a schedule is to be selected for processing and lists the predecessors for the schedule. selection. How CA-Scheduler determines the day's workload at autoscan time. CA-Scheduler reviews the criteria statements of every schedule to see which ones qualify for inclusion in the day's workload. Every time CA-Scheduler selects a schedule that qualifies, it scans the criteria statements of every job in that schedule. Jobs are selected if: they specify a calendar which defines that day as a workday 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 belong to are selected. All the important terms used in this definition are also defined in this glossary.
Glossary X-7
First, CA-Scheduler automatically copies the production JCL for jobs that require staging into its staging 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-CPU job has been posted as ENDED, CA-Scheduler automatically submits the modified JCL to the operating system when that job becomes available for processing. Also called JCL setup. staging file. The CA-Scheduler file that contains staged JCL members. The default name of the file is CAIJSTG. station. Any area where a job is processed as it makes its way through the data center. Examples include production control, data entry, JCL setup, CPU processing, and report distribution. Also called a workstation. substring. Part of the value given to a variable parameter. status conditions. The various words (ABENDED, ENDED, FAILED, etc.) that CA-Scheduler applies to jobs to indicate their current state within production. successor. Any job that cannot start until some event triggers it. CA-Scheduler's criteria statements allow you to define conditions that must be met before a job can start. If JOBA must finish before JOBB can start, JOBB is a successor to JOBA. Conversely, JOBA is a predecessor to JOBB. Supervisor authority level. The intermediate authority level which allows users to control all schedules and jobs at specified stations, even if they are not authorized on the schedule base record. However, their scope of authority is limited to just those stations specified on their user record. See General and Manager authority levels. syntax checking. Checking JCL for syntax errors and displaying those errors. CA-Scheduler uses the standard OS/390 interpreter/convertor or CA-JCLCheck (if it is
installed and the JCLCHK installation option is set to YES) to perform syntax checking.
T
tracking. CA-Scheduler monitors the progress of jobs by collecting and analyzing data on events as they occur. As jobs move from station to station through the data center, CA-Scheduler automatically updates their status in its active workload.
V
variable parameter. A symbolic parameter that is defined when a procedure is cataloged and referenced in the body of the procedure. During expansion, each reference to the symbolic parameter is replaced with a default or override value.
W
work flow. The movement of jobs from station to station through the data center. workday. Any day that is not designated a weekend or a holiday on a calendar or date table. workload. The work CA-Scheduler anticipates submitting each day. That includes: the schedules and jobs automatically selected by autoscan to run on that production day based on the information stored in the CA-Scheduler database and the schedules and jobs manually added by users See selection. workload documentation. The CA-Scheduler file that contains workload documentation entries. The default name of the file is CAIJDCM. workstation. Every area where a job is scheduled for processing as it makes its way through the data center. Examples include production control, data entry, JCL setup, 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-1 Execution node field 5-8 Remote execution node field 5-35 ADAY keyword 7-3, 7-16, 7-19, 7-46 ADD command automatic recovery 10-17 definition 9-21 Add CPU job panel 4-48 ADD JOB command 4-46 Add Job Command panel 4-46 Add Non-CPU job panel 4-54 Add panel 4-45 ADD PRED command 4-61 Add Pred Command panel 4-61 Add Preds panel 4-56 Add Successors panel 4-58 Adding See also Defining applications 9-14, 9-15 Driver parms 5-62 existing jobs to workload 4-149 flows 5-110 jobs compared to other commands 9-21 panel 4-46, 4-61 predecessors 4-56 stations 9-4 successors 4-58 ADOM keyword 7-3, 7-16, 7-46 ALLOC command 4-63 Alloc Command panel 4-63 Allocating data sets 4-63 ALTER command JBR 5-29 JIR 5-53 JMR 5-46 JNR 5-52 JRC 5-48 JRR 5-42 JSI 5-41 JSR 5-58 SBR 5-6
A
Abend option field Job definition panel 5-37, 10-16 ABENDED status activating jobs and schedules 9-21 job recovery 10-16 reports 9-18 Accounting code in date tables 5-102 cycles criteria keywords 7-3, 7-16 Date Translation report 7-20 using date tables 7-2, 7-12, 9-5 periods 7-46 ACTIVE queue 9-21, 10-8 active workload additions 9-21 backlogged work 10-13 during autoscan 9-4 FORCE command 9-20 global parameters 9-9 INACTIVE queue 10-8 initialization 9-9 reports 9-18 REQUESTED keyword 9-21 RESTAGE command 4-146, 10-16 user-defined reports 9-18
Index X-9
ALTER command (continued) SIR 5-21 SMR 5-15 SRC 5-17 SSI 5-14 ALTER FLOW command 5-111 ALTER JCR 5-57 ALTER Jxx command 5-29 ALTER RESOURCE command 5-81 ALTER SHRRSR command 5-89 ALTER STATION command 5-75 ALTER Sxx command 5-6 ALTER USERID command 5-68 Altering calendars 5-93 date tables 5-100 documentation members 5-106 Driver parms 5-62 flows 5-111 initiators 5-87 job criteria record 9-27 job sets 5-1 jobs 5-29 base record 5-30 criteria record 5-57 information record 5-53 message record 5-46 node record 5-52 reason code record 5-48 resource record 5-42 security information record 5-41 step code record 5-58 predecessors 9-27 resources 5-81 schedules base record 5-6 criteria record 5-24 message record 5-15 reason code record 5-17 security information record 5-21 shared resources 5-89 staging members 4-39 stations 5-75 user IDs 5-68 AMOY keyword 7-3, 7-27, 7-46 Analysis reports 9-11, 9-15 ANALYZE command issuing 9-11 verifying new applications 9-15 ANALYZE JOB command 6-4
Analyze job panel 6-4 Analyze menu 6-3 ANALYZE SCHEDULE command 6-6 Analyze schedule panel 6-6 AND keyword combined selection and predecessor example date table example 7-19 debugging errors 7-33, 7-34 inactive queue example 10-12 overview 7-39 use in Boolean expressions 7-3 using multiple conditions 7-9 Applications adding 9-15 verifying 9-15 Authorization types 5-70 AUTO START field pre-CPU jobs 9-4, 9-7 AUTOINIT value 4-13 Automatic recovery ADD command 10-17 CAJUCMD0 10-17 REQUEST command 10-17 RUN command 10-17 Autoscan AUTOINIT value 4-13 backlogged work defined 10-13 Job definition panel 5-31 performing autoscan 9-4 Schedule definition panel 5-7 spanning two autoscans 9-27 command file 8-1 displaying dates 4-84 displaying times 4-43 global parameters 9-9 process 9-4 purges jobs 10-8, 10-10 status 4-82 time 5-11 AUTOSEL keyword batch commands for SBR 7-11 SBR panel 5-7 AWOF keyword 7-3 AWOM keyword 7-16, 7-46
7-7
B
Backlog autoscan time 9-4, 9-27, 10-13 definition 10-13
X-10 Online Guide
Backlog (continued) symptom of deadlock 9-16 BACKLOG field Job definition panel 5-31, 10-13 Schedule definition panel 5-7, 10-13 Backout jobs automatic recovery option 10-17 Job definition panel 5-37 reason code 4-7, 4-22 Boolean expressions 7-3 Build monitor commands 4-1 Bypass GDG field Rerun Job panel 4-144 Submit job panel 4-162
C
CA-11 ADD CPU Job panel 4-53 CPU Job status detail panel 4-27 Job definition panel 5-38 Rerun job panel 4-142, 4-143 restarting jobs 10-15 Schedule status panel 4-13 Submit job panel 4-161 CA-Dispatch 9-10 CA-Earl reporting creating 9-18 list 9-18 Pending Job Profile report 10-14 CA-JCLCheck overview 9-7 simulation 9-15 CA-Opera 9-10 CA-Roscoe library type Add CPU job panel 4-50 CPU job status detail panel 4-27 Job definition panel 5-34 Schedule status panel 4-12 CA-Scheduler Agent 11-1 initiating and tracking jobs 11-1 CAICCI 11-1 CAIENF shut down 9-24 subsystem 9-23, 9-24 CAIJ$DSN macro display 4-85 CAIJ$MVS macro display 4-86 CAIJDCF member 8-1 CAIJGEN SECURTY option See Installation options
CAIJMVS macro display 4-87 CAJUCMD0 utility automatic recovery 10-17 issuing online commands in batch 9-20 resetting global parameters 9-28 CAJUTIL0 utility ANALYZE command 9-11, 9-15 FORECAST command 9-16 ONLY command 9-16 SIMULATE command 9-16 CAJUTSTB member 9-17 Calendars definition panel 5-95, 7-22 holidays 7-21 menu 5-93 methodology 7-21, 9-5 overview 7-2, 7-12 prototype 5-95, 7-21 workdays 5-95, 7-21 CANCEL ALL command 4-70 CANCEL command CANCEL ALL 4-70 CANCEL JOB 4-66 CANCEL SCHEDULE 4-68 impacts dependencies 9-26 Cancel Commands panel 4-65 CANCEL JOB command 4-66 Cancel Post (CP) Commands panel 4-73 CANCEL SCHEDULE command 4-68 CANCELLED status 9-21 CANCLD status 10-16 CASCHD member 9-20 Checking JCL syntax 9-15 CICS CICS 1-16 Editor 1-19 interface 1-18 PF key settings (default) 1-16 Cjobchan panel 6-26 Cjobrchn panel 6-35 Command file, autoscan 8-1 Command Output from Status Options panel 3-2 Command Prompt from Status Options panel 3-2 Commands ADD JOB 4-46 ADD PRED 4-61 adding to the workload 9-20 ALLOC 4-63
Index X-11
Commands (continued) ALTER FLOW 5-111 ALTER Jxx 5-29 ALTER RESOURCE 5-81 ALTER SHRRSR 5-89 ALTER STATION 5-75 ALTER Sxx 5-6 ALTER USERID 5-68 ANALYZE JOB 6-4 ANALYZE SCHEDULE 6-6 CANCEL ALL 4-70 CANCEL JOB 4-66 CANCEL SCHEDULE 4-68 COMPLETE JOB 4-71 control where they can be issued 9-20 CP JOB 4-74 CP SCHEDULE 4-77 DEALLOC 4-80 DEFINE FLOW 5-111 DEFINE Jxx 5-29 DEFINE RESOURCE 5-81 DEFINE SHRRSR 5-89 DEFINE STATION 5-75 DEFINE Sxx 5-6 DEFINE USERID 5-68 DELETE FLOW 5-111 DELETE JOB 5-29 DELETE RESOURCE 5-81 DELETE SCHEDULE 5-6 DELETE SHRRSR 5-89 DELETE STATION 5-75 DELETE USERID 5-68 DEXPAND 4-40 DISPLAY $DSN 4-85 DISPLAY $MVS 4-86 DISPLAY $SEC 4-87 DISPLAY ALLOC 4-83 DISPLAY DATE 4-84 DISPLAY EVENTS 4-88 DISPLAY FLOW 4-88 DISPLAY NETWORK 4-87 DISPLAY VRM 4-89 DISPLAY XPLAT 4-88 DPROMPT 4-42 entering 1-10 FORCE JOB 4-91 FORCE SCHEDULE 4-93 HOLD ALL 4-100 HOLD JOB 4-97 HOLD SCHEDULE 4-99
Commands (continued) HOLD SUBMIT 4-101 in remote scheduling 11-3 issuing 4-1 LIST FLOW 5-111 LIST JOB 5-29 LIST SCHEDULE 5-6 LIST STATION 5-75 LIST USERID 5-68 menu 4-43 Monitor 4-1 POST DSN 4-116 POST JOB 4-106 POST MVS 4-118 POST SCD 4-109 POST SJOB 4-111 POST SSCD 4-114 POST STEP 4-120 POST Unscheduled Job 4-118 PURGE ALL 4-128 PURGE JOB 4-125 PURGE SCHEDULE 4-127 RECALL 4-41 RELEASE ALL 4-133 RELEASE AUTO 4-134 RELEASE JOB 4-130 RELEASE SCHEDULE 4-132 RELEASE SUBMIT 4-137 RELEASE USER 4-135 RELEASE USERALL 4-136 REPORT ABEND 6-8 REPORT AUDIT 6-10 REPORT CJOBCHAN 6-26 REPORT CJOBRCHN 6-35 REPORT COMPLETE 6-12 REPORT CSCDCHAN 6-28 REPORT CSCDRCHN 6-37 REPORT DATETRAN 6-14 REPORT JOBAVG 6-16 REPORT JOBCHAIN 6-22 REPORT JOBHIST 6-17 REPORT JOBRCHAN 6-31 REPORT MAILBOX 6-18 REPORT OPTIONS 6-20 REPORT SCDCHAIN 6-24 REPORT SCDRCHAN 6-33 REQUEST JOB 4-139 REQUEST SCHEDULE 4-140 RERUN JOB 4-142 RESTAGE JOB 4-146 RUN JOB 4-149
X-12 Online Guide
Commands (continued) RUN SCHEDULE 4-151 SET GBLxnn 4-95 SREQ JOB 4-154 SREQ SCHEDULE 4-156 START JOB 4-158 SUBMIT JOB 4-160 TALTER JOB 4-20 TALTER SCHEDULE 4-5 UNPOST DSN 4-175 UNPOST JOB 4-165 UNPOST MVS 4-177 UNPOST SCD 4-168 UNPOST SJOB 4-170 UNPOST SSCD 4-173 UNPOST STEP 4-179 VARY ACT 4-184 VARY INACT 4-185 VARY VRM 4-186 Commands menu 4-43 Comments in remote scheduling 11-2 Commonly asked questions 9-2 Communicating with CA-Scheduler Agent 11-1 Communicating with Unicenter TNG 11-1 COMPLETE command non-CPU stations 9-4, 9-7 with INTERRUPTED status 9-10 Complete Job Command panel 4-71 Conditions causing selection 7-1, 7-4, 7-6, 7-9 Console commands 9-20 messages 9-20 Control commands for recovery 10-16 on Status panels 9-26 where they can be issued 9-20 Copying calendar 5-99 date table 5-105 documentation member 5-109 job 5-65 job step entry 5-60 schedules 5-25 station 5-77 User ID 5-72 CP commands 4-73 CP JOB command 4-74 CP SCHEDULE command 4-77
CPM 5-110 CPU resource panel 5-83 CPU station 5-73, 9-4 Criteria language job selection 7-3 overview 7-1 schedule selection 7-3 subtleties 10-9 vocabulary 7-39 Criteria record job 5-57, 9-27 schedule 5-24, 7-11 Criteria, predecessors 7-6 Critical Path Monitor system tracking flows 5-110 Cross-platform nodes displaying 4-88 Cscdchan panel 6-28 Cscdrchn panel 6-37 Cyclic scheduling 7-41
D
DAILY keyword calendar mechanism 7-13 definition 7-2, 7-12 example 7-4 Gregorian calendar 7-3 Gregorian calendar conditions 7-41 staging a job 9-7 DASD definition 5-80 Data sets allocating 4-63 displaying those allocated to CA-Scheduler started task 4-83 Database command entry 1-10 menu 5-1 reports 9-18 Date table cycles 9-5 definition panel 5-102, 7-16 menu 5-100 methodology 7-15, 9-5 overview 7-2, 7-12 prefix 5-102, 5-104, 9-5 Date Translation report 7-19 Days-of-themonth keywords abbreviations 7-41 accounting cycles 7-46 workdays 7-41
Index X-13
Days-of-the- (continued) week keywords abbreviations 7-41 accounting cycles 7-46 workdays 7-44 DCFERR parameter 8-1 Deadlocks examples 7-33 preventing 9-11 Report analyze panel 6-3 verifying a new application 9-15, 9-16 Dealloc Command panel 4-80 Default Analyze List Type field Options panel 3-1 Default PF key settings CICS 1-16 ISPF 1-15 Default Start/Complete Station Options panel 3-2 DEFINE FLOW command 5-111 DEFINE JCR 5-57 DEFINE Jxx command 5-29 DEFINE RESOURCE command 5-81 DEFINE SHRRSR command 5-89 DEFINE STATION command 5-75 DEFINE Sxx command 5-6 DEFINE USERID command 5-68 Defining calendars 5-93 DASD 5-80 date tables 5-100 flows 5-110 global parameters 4-95, 7-5, 9-8 initiators 5-87 job sets 5-1 jobs 5-29 base record 5-30 criteria record 5-57 information record 5-53 message record 5-46 node record 5-52 reason code record 5-48 resource record 5-42 security information record 5-41 predecessors 4-56, 7-1, 7-6, 9-22 resources 5-81 schedule criteria record 7-11 schedule order 9-6 schedules 5-6 base record 5-6 criteria record 5-24 message record 5-15
Defining (continued) schedules (continued) reason code record 5-17 security information record 5-21 shared resources 5-89 staging members 4-39 stations 5-75, 9-4 successors 4-58 user IDs 5-68 work schedules calendars 7-21, 7-23 holidays 7-15, 9-5 Delete Confirmation field Options panel 3-1 DELETE FLOW command 5-111 DELETE JCR 5-57 DELETE JOB command 5-29 DELETE RESOURCE command 5-81 DELETE SCHEDULE command 5-6 DELETE SHRRSR command 5-89 DELETE STATION command 5-75 DELETE USERID command 5-68 Deleting calendars 5-93 date tables 5-100 documentation members 5-106 Driver parms 5-62 flows 5-111 initiators 5-87 job sets 5-1 jobs 5-29 resources 5-81 schedules 5-6 shared resources 5-89 stations 5-75 user IDs 5-68 Dependencies 7-1 DEXPAND command 4-40 Directory calendars 5-94 date tables 5-101 documentation 5-108 job 5-27 resources 5-79 schedule 5-4 station 5-74 DISPLAY $DSN command 4-85 DISPLAY $MVS command 4-86 DISPLAY $SEC command 4-87 DISPLAY ALLOC command 4-83
X-14 Online Guide
Display Commands panel 4-82 DISPLAY DATE command 4-84 DISPLAY EVENTS command 4-88 DISPLAY FLOW command 4-88 Display Key field Job definition panel 5-40, 9-14 DISPLAY NETWORK command 4-87 Display Time field Job definition panel 5-41 DISPLAY VRM command 4-89 DISPLAY XPLAT command 4-88 Displaying autoscan dates 4-84 CAIJ$DSN macro contents 4-85 CAIJ$MVS macro contents 4-86 calendars 5-93 cross-platform nodes 4-88 current job information 4-20 data sets allocated to CA-Scheduler started task date tables 5-100 documentation members 5-106 events 4-88 flow 4-88 global parameters 9-9 NJE VTAM session status 4-87 predecessors 4-38 security 4-87 VRM 4-89 Documentation displaying members 5-106 menu 5-106 printing 9-14 reports 9-18 DOM keyword 7-27, 7-41, 7-46 Domains in remote scheduling 11-4 DPROMPT command 4-42 Driver DEXPAND command 4-40 expanding Driver procedures 4-40 job submission 9-21 listing reserved variables 4-42 parms panel 5-62 recovery 10-15, 10-17, 10-20 returning JCL to original contents 4-41 DSN keyword overview 7-5, 7-39 with PRED keyword 9-22
E
EARLY START field Job definition panel 5-31, 9-7 Schedule definition panel 5-11 Editing JCL 4-146 with CICS 1-19 EFFDATE keyword 8-1 ENDED status 9-21 ENFDOWN HELD status 9-24 Entering database commands 1-10 tracking commands 1-10 Events displaying 4-88 Expanding Driver procedures 4-40 EXPDATE keyword 8-1 Explicit predecessors 7-5 External security Display Commands panel 4-82 Job security panel 5-41 Schedule security panel 5-14 setting 5-66
4-83
F
Fail Code field Add CPU job panel 4-51 CPU job status detail panel 4-28 Job definition panel 5-37, 10-16 Post job step panel 4-121 Unpost job step panel 4-180 Fail Oper field Add CPU job panel 4-51 CPU job base panel 5-36 CPU job status detail panel 4-28 Job step panel 5-61 Post job step panel 4-121 Unpost job step panel 4-180 Fail Option field Add CPU job panel 4-52 CPU job base panel 5-37 CPU job status detail panel 4-29 FAILED status 9-21, 10-16 Flow displaying 4-88 Flows 5-110 Force Command definition 9-20
Index X-15
Force Command (continued) panel 4-90 with WAIT status 9-22 FORCE JOB command 4-91 FORCE SCHEDULE command Forecast overview 9-14 verifying applications 9-16 FREECMD panel 4-187 Freeform command 4-187 Freeing a data set 4-80 Frequencies MONTHLY 7-21, 7-23 WEEKLY 7-21, 7-23
HOLD JOB command 4-97 HOLD SCHEDULE command 4-99 HOLD SUBMIT command 4-101 Holiday scheduling 7-44 4-93
I
Ignoring predecessors 9-20 Implicit predecessor 7-8, 9-6 INACTIVE queue 9-21, 10-8 Initiators 5-87 Insert CA-11 field ADD CPU Job panel 4-53 Job definition panel 5-38 Schedule definition panel 5-9 Schedule status panel 4-13 Insert CA-11 RMS field CPU Job status detail panel 4-27 Rerun Job panel 4-143 Submit job panel 4-161 INSERT RMS PROC field Job Definition panel 10-15 Insert Sched Enviro CPU Job status detail panel 4-27 Schedule status panel 4-12 Installation options $DYNNM 4-47 AUTOTIM 5-82 BACKOUT 4-29, 4-52, 5-37 CA11 4-142, 4-160, 5-9 DATETAB 5-7 displaying 6-20 ENDMSG 5-16 FALMSG 5-48 INSROUT 5-35 INSRRMS 5-9 INSRSenv 5-35 INSRSYS 5-35 LATMSG 5-16 LIBTYPE 4-49, 4-50, 5-8, 9-6 MCPU 5-43 MSGHOLD 5-16, 5-48 NJE Job status detail panel 4-30 Schedule base panel 5-8 Schedule status detail panel 4-6, 4-10 SECURTY and JSI 5-41 and passwords 5-69 and SSI 5-14 and user definitions 5-66 and user ID requirements 5-2
G
GBLxnn keyword defined 9-8 example 7-34 panel 4-95 reserved word 7-5 resetting 9-28 GDG keyword 7-5, 7-39 General authority 5-70 Global parameters defining 7-5, 9-8 displaying values 9-9 example 7-34 panel 4-95 setting values 9-28 testing values 9-20 Gregorian calendar 7-2, 7-3, 7-12 Grouping jobs 9-6
H
HDAY keyword and date tables 7-15 date table example 7-19 examples 7-25, 7-28 holiday scheduling 7-44 selection example 7-4 selection use 7-3 HELD status 9-21 Help 1-17 History reports 9-18 HOLD ALL command 4-100 Hold Commands panel 4-96
X-16 Online Guide
Installation options (continued) SECURTY (continued) Post Job Start panel 4-112 Post Job Step panel 4-122 Unpost Job Start panel 4-171 Unpost Job Step panel 4-181 SKPMSG 5-16 SPRTY 5-13, 5-32 STAGE 5-10 STRMSG 5-16 SUBUID 4-31, 5-14, 5-41 Internal security Schedule base panel 5-13 Schedule status detail panel 4-14 Interrupt field Job definition panel 5-38, 9-10 Interrupted jobs 9-10 INTERRUPTED status 9-21
J
JBR panel 5-29 JCL errors 10-17 staging 4-146, 9-4, 9-6, 9-18 syntax checking 9-15 JCR panel 5-28, 5-57 JES class 4-33, 4-55, 5-9, 5-40 job number 6-17 node 5-52 Original JES number 4-22 priority 4-33, 4-55, 5-10, 5-40 JIR panel 5-53 JMR panel 5-46 JNR panel 5-52 Job abends 9-21, 10-16 average panel 6-16 base record (JBR) 5-29 canceling 9-26 criteria record (JCR) 5-57, 9-27 definition panel 5-29, 9-10, 10-16 forcing 4-91 history panel 6-17 holding 4-97 information record (JIR) 5-53 maintaining 5-29 menu 5-26 message record (JMR) 5-46, 10-17
Job (continued) node record (JNR) 5-52 posting 4-105 purging 4-125, 9-26 reason code record (JRC) 5-48 recovery 10-15 releasing panel 4-130 requesting panel 4-139 rerunning 9-10, 10-15 Rerun Job Command panel 4-142 Run Job Command panel 4-149 Submit Job Command panel 4-160 resource record (JRR) 5-42 running 4-149 security information record (JSI) 5-41 selection additions 9-21 criteria language 7-1, 7-3 rule 7-11 with REQUESTED 9-21, 10-8 staging 9-6 status detail panel 4-20 status menu 4-16 step panel 5-58 step record (JSR) 5-58 submission automatic 9-7 manual 9-20 Summary report 9-16 job sets 5-1 JOBA SCHDA keyword 7-4 JOBA-02 40 SCHDA keyword 7-4 JOBA.PROC1.STEP2-02 40 SCHDA keyword 7-4 JOBA.PROC1.STEP2.CC.GT.00008-02 40 SCHDA keyword 7-4 JOBA.STEP2-02 40 SCHDA keyword 7-4 JOBA.STEP2.CC.GT.00008-02 40 SCHDA keyword 7-4 Jobchain panel 6-22 Jobrchan panel 6-31 JRC panel 5-48 JRR panel 5-42 JSI panel 5-41 JSR panel 5-58 Jump character 1-9 Jump commands 4-5
Index X-17
K
Keywords ADAY 7-3, 7-16, 7-19, 7-46 ADOM 7-3, 7-16, 7-46 AMOY 7-3, 7-27, 7-46 AND date table example 7-19 debugging errors 7-33, 7-34 inactive queue example 10-12 overview 7-39 use in Boolean expressions 7-3 using multiple conditions 7-9 AUTOSEL batch commands for SBR 5-7, 7-11 AWOF 7-3 AWOM 7-16, 7-46 combined selection and predecessor example DAILY calendar mechanism 7-13 definition 7-12 Gregorian calendar 7-3 Gregorian calendar conditions 7-41 overview 7-2 selection example 7-4 DOM 7-27, 7-41, 7-46 DSN and predecessors 7-39 overview 7-5 with PRED keyword 9-22 examples 7-25, 7-28 GBLxnn defined 9-8 example 7-34 reserved word 7-5 resetting 9-28 GDG 7-5, 7-39 HDAY and date tables 7-15 date table example 7-19 examples 7-25, 7-28 selection example 7-4 selection use 7-3 workday conditions 7-44 JOB SCHDA 7-4 LEAP-YEAR 7-41 LIBTYPE batch commands for SBR 9-17 MVS predecessor 7-5, 7-39 NJE 7-5, 7-39
7-7
Keywords (continued) NOT and GBLXnn predecessors 9-9 and predecessors 7-10 date table example 7-19 debugging errors 7-34 examples 7-28 overview 7-39 use in Boolean expressions 7-3 OR and predecessors 7-9 date table example 7-19 debugging errors 7-32, 7-34 examples 7-25, 7-28 overview 7-39 predecessors 10-9 use in Boolean expressions 7-3 using multiple conditions 7-9 PRED resetting PRED flag 9-22 usage 7-5, 7-39 RDnn 7-3, 7-4, 7-15, 7-45 REQUESTED daily processing 9-21 Gregorian calendar conditions 7-41 impact on successors 10-9 jobs purged by autoscan 10-8, 10-10 purpose 10-8 selecting jobs with 10-8 selecting schedules with 10-8 SCD combined selection and predecessor example defining predecessor conditions 7-5 predecessors 7-3, 7-5, 7-39 selection example 7-4 staging a job 9-7 START and NJE 7-5 predecessor example 7-5, 7-39 selection example 7-4 selection keyword 7-3 WDAY and date tables 7-15 date table example 7-19 examples 7-26, 7-28 selection example 7-4 selection use 7-3 workday conditions 7-44 WDOM and date tables 7-15 examples 7-24, 7-29 selection example 7-4
7-7
X-18 Online Guide
Keywords (continued) WDOM (continued) selection use 7-3 workday conditions 7-44 WDOW and date tables 7-15 date table example 7-19 selection example 7-4, 7-24 selection use 7-3 workday conditions 7-44 WEEK-DAY calendar mechanism 7-13 Date Translation report 7-20 definition 7-2, 7-12 example 7-27 Gregorian calendar 7-3 Gregorian calendar conditions 7-41 WEEK-END 7-3, 7-41 WWOM 7-15, 7-19, 7-44 WWOY 7-44 xDAY 7-3, 7-16, 7-19, 7-46 xDOM 7-3, 7-16, 7-19, 7-46 xMOY 7-3, 7-27, 7-46 xWOF 7-3 xWOM 7-16, 7-46 xWOY 7-19
Listing (continued) jobs 5-29 resources 5-79 schedules 5-6 stations 5-75 user IDs 5-68 Locating command 1-13 Logging on 2-2
M
MAILBOX value 5-16 Main menu 2-3 Maintaining calendars 5-93 date tables 5-100 documentation members 5-106 jobs 5-29 schedules 5-6 shared resources 5-89 stations 5-75 user IDs 5-68 virtual resources 5-63 Manager authority 5-70 Mark job as complete 4-71 Message interrupted jobs 9-10 operator 9-10 record (JMR) 5-46 record (SMR) 5-15 routing 9-20 Messages definition panel (JMR) 5-46 definition panel (SMR) 5-15 Messages Menu panel 4-102 Monitor commands 4-188 menu 4-1 Month keywords 7-46 MONTHLY frequency 7-21, 7-23 scheduling 7-41, 7-44 Multiple Schedulers 8-3 MVS keyword overview 7-39 predecessor 7-5
L
LATE status 9-18 LEAP-YEAR keyword 7-41 Library Type field Job definition panel 5-33, 9-15 Schedule definition panel 5-8, 9-17 LIBTYPE installation option 9-6 LIBTYPE keyword batch commands for SBR 9-17 LIST FLOW command 5-111 LIST JOB command 5-29 List option 3-1, 9-15 LIST SCHEDULE command 5-6 LIST STATION command 5-75 LIST USERID command 5-68 Listing calendars 5-93 date tables 5-100 documentation members 5-106 Driver reserved variables 4-42 flows 5-111
N
Navigating panels 1-9
Index X-19
NJE CAIENF startup 9-24 Display NJE datasets panel 4-85 displaying network 4-87 job node inform panel 5-51 keyword 5-52, 7-5, 7-39 network 4-87 starting and stopping VTAM sessions VTAM session status 4-87 NO BACKLOG CNCL status 10-13 Node name CPU job base panel 5-35 in remote scheduling 11-2 Job status detail panel 4-21 Schedule status detail 4-6 Node record 5-52 Nonshared resources 5-80 Normal calendar 5-93 NOT keyword 7-10, 9-9 date table example 7-19 debugging errors 7-34 examples 7-28 overview 7-39 selection use only 7-3 NOTIFY keyword 5-22, 5-54 Numbering stations 9-4
P
PANV library type Add CPU job panel 4-49 CPU job base panel 5-33, 5-34 CPU job status detail panel 4-26 Schedule base panel 5-8 Schedule status detail panel 4-12 Parentheses in criteria date table example 7-19 debugging errors 7-33, 7-34 examples 7-25, 7-27, 7-28, 7-29 overview 7-39 separating reasons 7-9 use in Boolean expressions 7-3 Parms panel 5-62 Passwords and remote scheduling 11-5 Pending Job Profile report 10-14 Periods 7-46 PF key settings (default) CICS 1-16 ISPF 1-15 POST DSN command 4-116 POST JOB command 4-106 Post Menu panel 4-105 POST MVS command 4-118 POST SCD command 4-109 POST SJOB command 4-111 POST SSCD command 4-114 POST STEP command 4-120 POST Unscheduled Job command 4-118 PRED flag 9-22 keyword 7-5, 9-22 PRED keyword 7-39 Predecessor display panel 4-38 Predecessors altering 9-27 deadlock 7-33, 9-11, 9-15, 9-16 defining 7-1, 7-6, 9-22 displaying 4-38 explicit 7-5 global parameters 9-8 implicit 7-8, 9-6 listing for current job 6-35 current schedule 6-37 specific job 6-31 specific schedule 6-33 loop 6-3, 7-33, 9-11, 9-15 menu 6-30
4-183
O
ONLY command forecast 9-16 simulation 9-16 Operator console 9-20 messages 9-10 OPERATOR CANCLD status 10-16 Options menu panel 3-1 OR keyword and predecessors 7-9, 10-9 date table example 7-19 debugging errors 7-32, 7-34 examples 7-25, 7-28 overview 7-39 use in Boolean expressions 7-3 using multiple conditions 7-9 Organizing schedules 9-6 Overriding Driver parms 5-62 predecessors 9-20, 9-21 start times 9-20
X-20 Online Guide
Predecessors (continued) nonscheduled OS/390 job 7-5 other jobs or schedules 7-3, 7-5 overriding 9-20 reserved words 7-5 satisfying 4-105 tasks starting 7-3 user-defined event 9-8 with NOT keyword 7-10 OR keyword 7-9, 7-26, 7-32, 10-9 Predicting the workload 9-14 Prefixes for date tables 5-102, 5-104 Prerequisites 7-1 Printing jobs 9-4 Production cycles 7-16, 9-5 day 10-13 Prototype calendars 5-93, 7-21 PURGE ALL command 4-128 Purge Command impacts dependencies 9-26 panel 4-124 PURGE JOB command 4-125 PURGE SCHEDULE command 4-127
Q
Queue ACTIVE 9-21, 10-8 INACTIVE 9-21, 10-8
R
RC code job 4-21 schedule 4-6 RDnn keyword 7-3, 7-4, 7-15, 7-45 Reason codes job (JRC) 5-48 schedule (SRC) 5-17 Reason(s) code (JRC) 5-48 code (SRC) 5-17 codes (criteria language) 7-9 for selection 7-1 job selection code 4-21 multiple 7-9 schedule selection code 4-6 RECALL command 4-41
Recovery Driver 10-17 scheduled jobs 10-15 system crash 9-24 Relative days and date tables 7-15 Date Translation report 7-20 scheduling 7-45 selection example 7-4 selection use 7-3 RELEASE ALL command 4-133 RELEASE AUTO command 4-134 Release Commands panel 4-129 RELEASE JOB command 4-130 RELEASE SCHEDULE command 4-132 RELEASE SUBMIT command 4-137 RELEASE USER command 4-135 RELEASE USERALL command 4-136 Remote scheduling command 11-3 comments 11-2 domains 11-4 Execution node field 5-8 node name 11-2 password 11-5 Remote execution node field 5-35 user ID 11-4 Removing all schedules and jobs from workload 4-70 canceled and completed work 4-124 job from current workload 4-66, 4-74 job from status display 4-125 schedule from current workload 4-68, 4-77 schedule from status display 4-127 work from current workload 4-65, 4-73 REPORT ABEND command 6-8 Report abend panel 6-8 REPORT AUDIT command 6-10 Report audit panel 6-10 REPORT CJOBCHAN command 6-26 REPORT CJOBCHAN panel 6-26 REPORT CJOBRCHN command 6-35 REPORT CJOBRCHN panel 6-35 REPORT COMPLETE command 6-12 Report complete panel 6-12 REPORT CSCDCHAN command 6-28 REPORT CSCDCHAN panel 6-28 REPORT CSCDRCHN command 6-37 REPORT CSCDRCHN panel 6-37 REPORT DATETRAN command 6-14
Index X-21
Report datetran panel 6-14 REPORT JOBAVG command 6-16 REPORT JOBCHAIN command 6-22 REPORT JOBCHAIN panel 6-22 REPORT JOBHIST command 6-17 REPORT JOBRCHAN command 6-31 REPORT JOBRCHAN panel 6-31 REPORT MAILBOX command 6-18 Report mailbox panel 6-18 REPORT OPTIONS command 6-20 Report options panel 6-20 REPORT SCDCHAIN command 6-24 REPORT SCDCHAIN panel 6-24 REPORT SCDRCHAN command 6-33 REPORT SCDRCHAN panel 6-33 Reports abended 6-8 analysis 6-3, 9-11, 9-15 CA-Earl 9-18 database 9-18 date translation 6-14, 7-19 documentation 9-18 forecast 9-14 history 6-12, 9-18 installation options 6-20 job history 6-17 Job Summary report 9-16 Mailbox 6-18 menu 6-1 Pending Job Profile report 10-14 predecessors 6-3, 6-30 simulation 9-14 successors 6-21 user-defined 9-18 REQUEST command automatic recovery 10-17 compared to SREQ command 9-21 panel 4-138 with INACTIVE queue 10-8 predecessors 10-10 REQUEST JOB command 4-139 REQUEST SCHEDULE command 4-140 REQUESTED keyword activating work 4-138 daily processing 9-21 impact on successors 10-9 jobs purged by autoscan 10-8, 10-10 overview 7-41 purpose 10-8 selecting jobs with 10-8
REQUESTED keyword (continued) selecting schedules with 10-8 RERUN JOB command 4-142 definition 9-20 submitting jobs with 9-20 with ABENDED status 10-16 CANCLD status 9-22, 10-16 FAILED status 10-16 INTERRUPTED status 9-10 Rerun Job Command panel 4-142 Reserved Driver variables 4-42 Reserved words criteria language 7-39 criteria vocabulary 7-3 predecessors 7-5 Resetting GDG bias numbers 10-18 global parameters 9-28 PRED flag 9-22 relative generation pointers 10-18 Resource definition panel 5-80 menu 5-78 Nonshared 5-81 panel 5-81 requirements 9-7 Shared 5-89 RESTAGE JOB command 4-146 job recovery 10-16 usage 9-7 Restage Job Command panel 4-146 Restart instructions 10-15 JCL parameter 10-19 Restarting jobs with CA-11 10-15 with Driver 10-17 RHOLD=YES startup option 4-134 RMSPROC 10-15 Run Book report 9-14 Run Command panel 4-148 staging jobs 9-6 RUN JOB command automatic recovery 10-17 compared to other commands 9-21 panel 4-149 usage 9-22 with CANCLD status 10-16
X-22 Online Guide
RUN JOB command panel 4-149 RUN SCHEDULE command compared to other commands 9-21 panel 4-151 RUN SCHEDULE command panel 4-151
S
Sales cycles 7-16, 9-5 Satisfying predecessor conditions 4-105 SBR panel 5-11 SC prefix 1-10 SCD keyword and predecessors 7-3 combined selection and predecessor example defining predecessor conditions 7-5 predecessors 7-5, 7-39 selection example 7-4 Scdchain panel 6-24 Scdrchan panel 6-33 SCHD prefix 1-10 Schedule base record (SBR) 5-11 copying 5-25 criteria record (SCR) 5-5, 5-24, 7-11 definition panel 5-6 directory panel 5-4 forcing 4-93 holding 4-99 information record (SIR) 5-21 maintaining 5-6 message record (SMR) 5-15 options panel 5-5 order 9-6 panel 5-3 posting 4-105 purging 4-127 reason code record (SRC) 5-17 recovery 10-15 releasing panel 4-132 requesting panel 4-140 running 4-151 security record (SSI) 5-14 selection additions 9-21 criteria language 7-1, 7-3 rule 7-11 with REQUESTED 9-21, 10-8 status detail panel 4-5
7-7
Schedule (continued) status panel 4-2 Scheduling See also Remote Scheduling cyclic 7-41 daily 7-41 holiday 7-44 jobs 7-11, 7-21 monthly 7-41, 7-44 overview 11-1 period 7-46 relative day 7-45 weekly 7-41, 7-44 yearly 7-41 Scheduling Environment CPU Job status detail panel 4-28 Schedule status panel 4-13 SCR panel 5-5, 5-24 Security displaying 4-87 Job security panel 5-41 Schedule security panel 5-14 Schedule status detail panel 4-14 SSI record 5-14 user IDs 5-66 SECURTY option in CAIJGEN See Installation options Selecting flows 5-111 jobs criteria language 7-3 with ADD command 9-21 with REQUESTED keyword 9-21, 10-8 with RUN command 9-21 with schedules 7-11 schedules criteria language 7-3 instead of jobs 7-11 methods 9-5 with REQUESTED keyword 9-21, 10-8 with RUN command 9-21 Selection code 4-21 criteria 7-11 Sending messages abended jobs 10-17 failed jobs 10-17 interrupted jobs 9-10 to other users 9-20 to the console 9-20
Index X-23
SEPARATE fields Job resource panel 5-42, 9-7 SET command 4-95 Shared resource definition panel 5-89 Shared tape panel 5-90 Shared units panel 5-91 Shutting down CA-Scheduler 9-23 CAIENF 9-24 SIMULATE command 9-16 Simulation overview 9-14 testing applications 9-15 verifying applications 9-16 Simulation reports and resource definitions 5-78 and station definitions 5-73 SIR panel 5-21 SMR panel 5-15 Sorting displays 1-11 Specific dates 7-21 SRC panel 5-17 SREQ command compared to REQUEST command 9-21 with INACTIVE queue 10-8 predecessors 10-10 SREQ Commands panel 4-153 SREQ JOB command 4-154 SREQ SCHEDULE command 4-156 SSI panel 5-14 SSI record panel 5-14 Stage JCL field Job definition panel 5-38, 9-6 Schedule base panel 5-10 Staged JCL panel 4-39 Staging jobs Restage job panel 4-146 Staged JCL panel 4-39 station numbering 9-4 when 9-6 START JOB command 4-158 Start Job Command panel 4-158 START keyword 7-3, 7-4, 7-5, 7-39 Starting jobs 9-20 schedules 9-9, 9-20 Station 40 5-73 adding 5-73, 9-4
Station (continued) definition panel 5-75 menu 5-73 numbering 5-73, 9-4 Status ABENDED 9-18, 9-21, 10-16 autoscan 4-82 CANCELLED 9-21 CANCLD 10-16 ENDED 9-21 ENFDOWN HELD 9-24 FAILED 9-21, 10-16 HELD 9-21 INTERRUPTED 9-21 LATE 9-18 NO BACKLOG CNCL 10-13 OPERATOR CANCLD 10-16 Status panels displaying interrupted jobs 9-10 issuing control commands 9-26 resubmitting jobs 10-16 STATUS UNKNOWN command 9-25 Step-level restart 10-18 SUBMIT command definition 9-20 jobs 9-20 panel 4-160 with ABENDED status 10-16 CANCLD status 10-16 FAILED status 10-16 SUBMIT JOB command 4-160 Submit Job Command panel 4-160 Submitting jobs automatically 9-7, 9-9 panel 4-160 with RERUN command 9-20 SUBMIT command 9-20 Successors ABEND option 10-16 Chain List report 9-11 listing for current job 6-26 current schedule 6-28 specific job 6-22 specific schedule 6-24 menu 6-21 REQUEST example 10-9 REQUEST/SREQ command 9-22, 10-8
X-24 Online Guide
SUMMARY option for forecasts Supervisor authority level 5-70 SYNCHK DCF command 8-2 Syntax checking JCL 9-15 System crash 9-24
9-16
T
TALTER JOB command 4-20 TALTER SCHEDULE command 4-5 Tapes 5-80 Testing applications 9-15 TESTLIB library type and testing 9-17 planning new application 9-15 Tracking command entry 1-10 Tutorial 1-17
View current workload 4-1 Viewing virtual resources 5-63 Virtual resources 5-115 Virtual resources panel 5-63 VRM displaying 4-89 VRM panel 5-63
W
WDAY keyword and date tables 7-15 date table example 7-19 examples 7-25, 7-26, 7-28 selection example 7-4 selection use 7-3 workday conditions 7-44 WDOM keyword and date tables 7-15 examples 7-24, 7-29 selection example 7-4 selection use 7-3 workday conditions 7-44 WDOW keyword and date tables 7-15 date table example 7-19 selection example 7-4, 7-24 selection use 7-3 workday conditions 7-44 Week keywords 7-46 WEEK-DAY keyword calendar mechanism 7-13 Date Translation report 7-20 definition 7-2 example 7-27 Gregorian calendar 7-3 Gregorian calendar conditions 7-41 WEEK-END keyword 7-3, 7-41 Weekends 7-15 Weekly frequency 7-21, 7-23 scheduling 7-43, 7-45 Work schedules calendars 7-21, 7-23 defining 5-100 holidays 7-15, 9-5 WORK WEEK field Dateteble Definition panel 7-16 Workdays and date tables 7-2, 7-12, 7-15
U
Unicenter TNG communicating with 11-1 initiating and tracking jobs 11-1 statements supported 11-2 UNKNOWN status 9-25 Unpost Commands panel 4-164 UNPOST DSN command 4-175 UNPOST JOB command 4-165 UNPOST MVS command 4-177 UNPOST SCD command 4-168 UNPOST SJOB command 4-170 UNPOST SSCD command 4-173 UNPOST STEP command 4-179 UNPOST Unscheduled Job command User definitions 5-66 User IDs definition panel 5-68 in remote scheduling 11-4 menu 5-66 User-defined events 7-34 Utility program 9-11, 9-15
4-177
V
Variables (Driver) 4-42 VARY ACT command 4-184 Vary Commands panel 4-183 VARY INACT command 4-185 VARY VRM command 4-186 Verifying applications 9-15 workload selection 9-14
Index X-25
Workdays (continued) date table example 7-19 Date Translation report 7-20 keyword table 7-15, 7-44 keywords 7-3 selection examples 7-4 WWOM keyword 7-15, 7-19, 7-44 WWOY keyword 7-44
X
xDAY keyword xDOM keyword xMOY keyword xWOF keyword xWOM keyword xWOY keyword 7-3, 7-16, 7-19, 7-46 7-3, 7-16, 7-19, 7-46 7-3, 7-27, 7-46 7-3 7-16, 7-46 7-19
Y
Yearly scheduling 7-41
X-26 Online Guide

CA-Scheduler® Online Guide

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CA-Scheduler® Online Guide

Uploaded by

Copyright:

Available Formats

CA-Scheduler

2003 Computer Associates International, Inc.

5.10.4.2 5.10.4.3 5.10.4.4 5.10.4.5

Chapter 8. Using the Autoscan Command File

viii Online Guide

Chapter 1. Introduction 1-1

1.1 Summary of Revisions in the Fourth Edition

1.1 Summary of Revisions in the Fourth Edition

1-2 Online Guide

1.2 Summary of Revisions in the Third Edition

1.2 Summary of Revisions in the Third Edition

Chapter 1. Introduction 1-3

1.3 Summary of Revisions in the Second Edition

1.3 Summary of Revisions in the Second Edition

1-4 Online Guide

1.4 Summary of Revisions

1.4 Summary of Revisions

1.4.1 Product Features

Chapter 1. Introduction 1-5

1.4 Summary of Revisions

1-6 Online Guide

1.4 Summary of Revisions

Chapter 1. Introduction 1-7

1.4 Summary of Revisions

1.4.2 Documentation Changes

1-8 Online Guide

1.5 Panel Navigation

1.5 Panel Navigation

Chapter 1. Introduction 1-9

1.6 CA-Scheduler Commands

1.6 CA-Scheduler Commands

xxyy (SCHD) ------------------------

1-10 Online Guide

Chapter 1. Introduction 1-11

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

1-12 Online Guide

Row 1 to 19 of 5 SCROLL ===> CSR

Chapter 1. Introduction 1-13

After the Locate command, the display would show:

1-14 Online Guide

1.9 PF Keys for ISPF

1.9 PF Keys for ISPF

Chapter 1. Introduction 1-15

1.10 PF Keys for CICS

1.10 PF Keys for CICS

1-16 Online Guide

Chapter 1. Introduction 1-17

1-18 Online Guide

1.13 CICS Editor

1.13 CICS Editor

Chapter 1. Introduction 1-19

1.13 CICS Editor

Position the display to the beginning of the member. Syntax: TOP

1-20 Online Guide

1.13 CICS Editor

1.13.1 Adding Lines

The result will be:

Chapter 1. Introduction 1-21

1.13 CICS Editor

1.13.2 Copying a Block of Lines

The result will be:

1-22 Online Guide

1.13 CICS Editor