CA-Scheduler

Online Guide
9.0

SP3

This documentation and related computer software program (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by Computer Associates International, Inc. (“CA”) at any time. This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties. Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies. This right to print copies is limited to the period during which the license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to return to CA the reproduced copies or to certify to CA that same have been destroyed. To the extent permitted by applicable law, CA provides this documentation “as is” without warranty of any kind, including without limitation, any implied warranties of merchantability, fitness for a particular purpose or noninfringement. In no event will CA be liable to the end user or any third party for any loss or damage, direct or indirect, from the use of this documentation, including without limitation, lost profits, business interruption, goodwill, or lost data, even if CA is expressly advised of such loss or damage. The use of any product referenced in this documentation and this documentation is governed by the end user’s applicable license agreement. The manufacturer of this documentation is Computer Associates International, Inc. Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.

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

Contents
Chapter 1. Introduction . . . . . . . . . . . . 1.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

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

2.1.1 Summary of Revisions in the Fourth Edition 1. see 4. For more information. “Schedule Status Detail” on page 4-5 and 4. “Job Definition” on page 5-29.2.1.1.1. 1-2 Online Guide .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. ■ The SU Flag field is new in 4.1. “Directory” on page 5-4.1. “Job Status Detail” on page 4-20 and 5.2. “Job Status Detail” on page 4-20.2. ■ The panel changed in 5.1.

“Add Job Command” on page 4-46.2 Summary of Revisions in the Third Edition 1.1.2. “Report Mailbox” on page 6-18.2.1.1. “Job Definition” on page 5-29. ■ We changed the introduction of 9. Must End. Introduction 1-3 .1.1.2.1. Must End.5. ■ We changed the descriptions of the Must Start.8. ■ We changed several paragraphs of 6.3. and Schedule Skipped fields in 5.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. Maximum Execution. ■ We changed several paragraphs of 6. “What Happens If CAIENF is Shut Down?” on page 9-24. “Schedule Definition” on page 5-6.4. ■ We changed the descriptions of option 3 and option 9 in Chapter 6. “Report Audit” on page 6-10.1. Must End.3. Chapter 1. “Reports” on page 6-1. ■ We changed the descriptions of the Must Start. and Schedule Skipped fields in 5. Maximum Execution. and Maximum Execution fields in 4.

“Job Definition” on page 5-29.2.1.2.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.3 Summary of Revisions in the Second Edition 1. 1-4 Online Guide .1. “Schedule Definition” on page 5-6 and internal priority in 5.

such as changing a job's criteria. ■ Active Workload When CA-Scheduler determines that a job or schedule is to be executed. CA-Datacom provides many advantages over CATMAN (the previous access method) such as backup-while-open. See the CA-Scheduler Interfaces Guide for more information. relieving virtual storage shortage problems in many sites. a WLM scheduling environment may optionally be inserted into JCL during submission. all information about that job or schedule is copied to what used to be called the tracking file. Second. See the CA-Scheduler Online Guide for more information. forward recovery.4 Summary of Revisions 1. a WLM scheduling resource may be set ON when CA-Scheduler starts and OFF when CA-Scheduler shuts down. ■ Virtual Resource Manager Virtual Resource Management introduces a new way to define resource dependencies for jobs. Staged JCL and documentation are also stored in CA-Datacom. See the CA-Scheduler Systems Programmer Guide for more information. First. CA-Scheduler ensures that the defined requirements are met before submitting the job for execution.4. do not impact the current copy of the job in the active workload. Changes made to the scheduling database (master file). and faster access. Chapter 1. The WLM scheduling environment and WLM scheduling resource may be used to limit which systems jobs execute on. 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. or even what CPU resources are assigned to jobs. 1.1 Product Features CA-Scheduler 9. CA-Datacom also allows CA-Scheduler to exploit 31-bit storage. ■ Workload Manager Interface CA-Scheduler interfaces in two ways with the IBM Workload Manager (WLM). The active workload now includes everything needed to submit and track the work in the correct order. Introduction 1-5 .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).1. Virtual resources can be defined as required for job processing.4 Summary of Revisions The summary includes changes to CA-Scheduler and to the documentation.

■ Temporary Predecessors A new command. all scrollable displays. In the CICS online.1. See the CA-Scheduler Reports Guide for more information. can be sorted by any of the displayed columns. such as status and directory lists. Jobs added to the active workload after the HOLD SUBMIT command are also not submitted. See the CA-Scheduler Online Guide for more information. The command L yyy can be entered. as HOLD ALL does. unlike HOLD ALL. The HOLD SUBMIT status is saved across restarts of CA-Scheduler. userid. ■ Cross-Platform Job Definitions Jobs may be defined to the scheduling database (master file) with a cross-platform node. See the CA-Scheduler Command Reference Guide for more information. See the CA-Scheduler Online Guide for more information. If this information is also specified in the job's "JCL. ADD PRED. where yyy is the value to be found. prevents all submission without modifying the status of any schedules or jobs. ■ Hold/Release Submit A new command." the "JCL" copy overrides the database copy. See the CA-Scheduler Command Reference Guide for more information. The display can be positioned to a particular row by using the Locate command. and password. 1-6 Online Guide . all jobs that could not be submitted due to the HOLD SUBMIT are submitted. where xxx is one of the column headers. ■ Batch Datetable/Calendar Support Datetables and calendars may now be maintained and displayed in batch. domain. The predecessor job may not be complete. The most recently sorted column is used to find the Locate string.4 Summary of Revisions ■ Online Sort/Locate In the ISPF online. ■ Backwards JOBCHAIN New variations of the JOBCHAIN reports are available to display a job or schedule's predecessors instead of their successors. HOLD SUBMIT. allows the definition of a one-time predecessor/successor relationship between two jobs in the active workload. The command SORT xxx can be entered. See the CA-Scheduler Command Reference Guide for more information. The leftmost column is used to find the Locate string. When the RELEASE SUBMIT command is issued. and the successor job may not have started when the command is issued. the Locate command may be used to position the scrollable displays.

xxx) are issued to the originating console.xxx) while an earlier modify command is being processed. ■ MAILBOX and Audit Trail The mailbox and audit trail information is now stored in the CA-Scheduler database instead of in CAIENF. This allows console automation products such as CA-OPS/MVS II to "see" the response to a command. ■ Exits All exits are now called AMODE 31 and RMODE ANY. See the CA-Scheduler Systems Programmer Guide for more information. See the CA-Scheduler Systems Programmer Guide or the CA-Scheduler Online Guide for more information. or sent to the mailbox. Chapter 1.4 Summary of Revisions ■ SKIPPED Messages A message may be generated when a job or schedule is excluded from the active workload due to a nonzero SKIP value. issued on the console. Introduction 1-7 . ■ Command Response Messages Messages issued in response to an OS/390 modify command (that is. See the CA-Scheduler Systems Programmer Guide for more information. See the CA-Scheduler Command Reference Guide for more information. Any number of commands may be queued waiting for the command processor. CA-Scheduler automatically retains the command and issues it when the command processor is available. Users no longer need to be defined to CAIENF to issue the REPORT AUDIT or REPORT MAILBOX commands.1. F CASCHD. The message may be queued for a specific CA-Scheduler user. ■ Better Handling of OS/390 Modify (F) Commands When an OS/390 modify command is received (F CASCHD. 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. Modify command output is also captured and displayed by SDSF. Messages are issued when a command is delayed and when it is executed. Some client exits may need to be reworked to tolerate AMODE 31. Time-out conditions may prevent either console automation products or SDSF from seeing the command responses.

book marking.2 Documentation Changes ■ The documentation set has been engineered to take advantage of the latest technology for online viewing. ■ Reading Syntax Diagrams in the Command Reference Guide explains how to read the command syntax used in all guides.4 Summary of Revisions 1.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.1. keyword searching. and printing. 1-8 Online Guide .4. This set contains a hardcopy CA-Scheduler Getting Started guide and Version 9.

5 Panel Navigation 1. Chapter 1. For example.3" from any non-scrollable field on any panel in CA-Scheduler.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. Note: The CICS interface does not support split panel or the jump character (=). Split panel is fully supported. The CA-Scheduler dialog may be in use concurrently on the same TSO ISPF session as many times as needed. The total number is not displayed for CICS.1. which is not necessarily the last menu you saw. "=". The END command (normally PF3/15) returns you to the panel where the function started. enter "=1. Introduction 1-9 . Certain scrollable panels in ISPF will show the total number of rows being displayed. to reach the Monitor Commands menu.

Tracking commands do not require an "SC" before the command. Commands that could be interpreted as either tracking commands or simulation commands (such as RUN) are interpreted as tracking commands.6 CA-Scheduler Commands 1. The output of the command is displayed in a browse panel: -----------------. Enter "SCHD" followed by the command. Inc. FORCE). ------------------------------------------- You can enter both database commands (DEFINE. SYNCHK.CA-SCHEDULER 9. ANALYZE) and tracking commands (RUN. 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 .) This interface does not support some commands.1.CA-SCHEDULER 9. but the "SC" is supported if entered.6 CA-Scheduler Commands You can enter CA-Scheduler commands on any panel from the first input field (the COMMAND or OPTION field). like this: ------------------------. (Tracking commands run in batch using utility CAJUCMD0 still require the SC prefix. CANCEL. 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. such as FORMAT and SIMULATE. 2 1 Computer Associates International.

enter the command "SORT xxx" where xxx is the column title you want sorted.7 Sort 1. For example: -----------------. may be sorted by any of the columns displayed. such as status and directory displays.1.CA-SCHEDULER 9.7 Sort All of the scrollable displays. To sort a display. 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 _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ Chapter 1. Introduction 1-11 .

1.7 Sort After the sort command is issued. the following would be displayed: -------------------. not on CICS. 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.CA-SCHEDULER 9. This may cause a delay before the first sort can be completed. 1-12 Online Guide . Note: The SORT command is only available on ISPF.

8 Locate 1. The column searched is the one most recently sorted with the SORT command.CA-SCHEDULER 9. For example: -------------------. Introduction 1-13 . 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 Chapter 1.1. If the SORT command has not been entered. the leftmost column is searched. issue "L xxx" where xxx is the value to find. 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.8 Locate All of the scrollable displays.

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.8 Locate After the Locate command. the display would show: -------------------.1. the Locate command always searches the leftmost column. 1-14 Online Guide .CA-SCHEDULER 9.

then pressing PF5 will not refresh the list of jobs or schedules. 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).9 PF Keys for ISPF 1. Since PF5 is normally set to Rfind. Chapter 1. This manual assumes that the PF keys are set to the default values. Introduction 1-15 . If PF5 is set to some other command. All PF keys are set to the default values when users first access it. it is up to the user to issue the correct command to CA-Scheduler.9 PF Keys for ISPF ISPF allows users to change the settings of the PF keys. CA-Scheduler is really using the Rfind command.1. If a user changes a PF key. PF5 is documented as refreshing a list of schedules or jobs in the status display. For example.

10 PF Keys for CICS 1. For example. 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. PF8 is documented as the DOWN command. If PF8 is set to any other command.1. This manual assumes that the PF keys are set to the default values. If a user changes a PF key. it is up to the user to issue the correct command to CA-Scheduler.10 PF Keys for CICS The CICS interface allows users to change the settings of the PF keys. then pressing PF8 will not page down. 1-16 Online Guide .

11 Tutorial You can obtain information about any ISPF panel and the fields on the panel by pressing PF1/13 (HELP). Introduction 1-17 . Chapter 1.1. The CICS interface does not currently support tutorial panels.11 Tutorial 1.

The base functionality of the product is the same for both ISPF and CICS. wherever reasonable.12 CICS 1.1. are not supported.12 CICS The CA-Scheduler CICS interface has been designed to match the ISPF environment. 1-18 Online Guide . The panel samples in this guide are from ISPF. for example. ISPF split-panel and the ISPF editor. CICS panels should look similar to the ISPF versions but may not look exactly the same.

Syntax: LEFT RECALL (staged JCL only) See 4. You may optionally specify a column to search.13 CICS Editor Under ISPF.13 CICS Editor 1. staged JCL. C See also RCHANGE. FIND <string> column“ FI.2. Syntax: FIND DPROMPT Locate a character string in the member and position the display to it. Syntax: RECALL Chapter 1.1. Normally set to PF key 10/22.3.2. Syntax: DEXPAND DPROMPT (staged JCL only) See 4.2. Syntax: DELETE DEXPAND (staged JCL only) See 4. COLUMN Display a column scale line. a native CA-Scheduler editor is used. Syntax: Abbreviations: CHANGE <oldstring> <newstring> column“ CH. F LEFT Shift the display of data to the left. Syntax: Abbreviations: See also RFIND. This section documents how to use the CA-Scheduler native editor in CICS. “RECALL” on page 4-41. Syntax: Abbreviation: COLUMN COLS DELETE (criteria only) Delete the criteria currently displayed from the CA-Scheduler database. CA-Scheduler uses the ISPF editor to modify criteria. and documentation.2. You may optionally specify the column where the strings begin. “DEXPAND” on page 4-40.1. “DPROMPT” on page 4-42. Syntax: Abbreviation: BOTTOM BOT CHANGE Replace one string with another.3.3. Since the ISPF editor is not available under CICS. Introduction 1-19 .3. You may issue the following commands on the command line: BOTTOM Position the display to the end of the member.

) MM (block of lines. Enter DD on the first and last lines of the block.13 CICS Editor RESET Removes the output of the DEXPAND command. The new copies of the line appear immediately following the original. Syntax: C nn“ (where nn is 1 to 18 lines.) REPEAT Duplicate a line one or more times. Enter CC on the first and last lines of the block. Syntax: COPY B Copy one or more lines to another location in the member.) INSERT Add one or more blank lines to the member. The default is 1. The default is 1. The default is 1. AFTER The target of a MOVE or COPY command is after this line. Syntax: R nn“ (where nn is 1 to 18 new copies. Syntax: A BEFORE The target of a MOVE or COPY command is before this line.2. You indicate where the lines should be moved with the AFTER or BEFORE commands. Syntax: RIGHT SAVE Write the data being edited to the temporary file. Syntax: RESET RIGHT Shift the display of data to the right. Enter CC on the first and last lines of the block. The default is 1. Syntax: SAVE TOP Position the display to the beginning of the member.) CC (block of lines. Syntax: TOP The following commands may be entered in the command area (the numbers to the left of each line).) DD (block of lines.1.) DELETE Remove one or more lines from the member. Syntax: M nn“ (where nn is 1 to 18 lines. You indicate where the lines should be copied with the AFTER or BEFORE commands. “DEXPAND” on page 4-40. See 4. The default is 1.) MOVE Move one or more lines to another location in the member. Syntax: D nn“ (where nn is 1 to 18 lines.3.1.) 1-20 Online Guide . Syntax: I nn“ (where nn is 1 to 18 lines. This does NOT save it to the CA-Scheduler files. Normally set to PF key 11/23. The lines are added after the line on which you enter the command.

. 11 THIS IS LINE 8.......2... 3 THIS IS LINE 3. 5 THIS IS LINE 5. 1 WDAY 2 THIS IS LINE 2.. 1 WDAY 2 THIS IS LINE 2.5..6.2....1. 8 THIS IS LINE 8. 5 THIS IS LINE 5.+.... 6 THIS IS LINE 6.3...... ------------------------------------------------------------------------ The result will be: -----------------------------------------------------------------------1.. 3 THIS IS LINE 3.1.... 1 THIS IS LINE 1 .5.6..... -> I3 6 THIS IS LINE 6.+..+.+....13 CICS Editor 1...3.+..+.+....4. ------------------------------------------------------------------------ Chapter 1.........1 Adding Lines To add 3 lines: -----------------------------------------------------------------------1.+...... 13 THIS IS LINE 1 .. -> 7 -> 8 -> 9 1 THIS IS LINE 7. Introduction 1-21 . 12 THIS IS LINE 9... 7 THIS IS LINE 7.........+.+..13...4.+. 4 THIS IS LINE 4.. 9 THIS IS LINE 9. 4 THIS IS LINE 4....1..+.

6 THIS IS LINE 6..13..+. -> 7 WDAY -> 8 THIS IS LINE 2..+...... 9 THIS IS LINE 9......2. 13 THIS IS LINE 1 .1...+. 7 THIS IS LINE 7. ->>CC 3 THIS IS LINE 3...5...3.+... 8 THIS IS LINE 8...... ->>CC 1 WDAY 2 THIS IS LINE 2.+......6.13 CICS Editor 1... ------------------------------------------------------------------------ The result will be: -----------------------------------------------------------------------1... 1 WDAY 2 THIS IS LINE 2... 12 THIS IS LINE 9.3.1.6. 1 THIS IS LINE 1 .2 Copying a Block of Lines To copy lines 1-3 after line 6: -----------------------------------------------------------------------1...1. 11 THIS IS LINE 8..... 3 THIS IS LINE 3.... 5 THIS IS LINE 5... 4 THIS IS LINE 4.5.+.... -> A 6 THIS IS LINE 6..+.4. 5 THIS IS LINE 5.+. 1 THIS IS LINE 7..... ------------------------------------------------------------------------ 1-22 Online Guide .+...4....+........2. -> 9 THIS IS LINE 3..+..+. 4 THIS IS LINE 4...

.. 7 THIS IS LINE 7. 2 THIS IS LINE 5.+. 4 THIS IS LINE 4.3...1.+....... 1 THIS IS LINE 4.... -> 3 WDAY -> 4 THIS IS LINE 2.+. 1 THIS IS LINE 1 ... 5 THIS IS LINE 5...+...........6... 6 THIS IS LINE 6... 8 THIS IS LINE 8.2..+...5.. ->>MM 1 WDAY 2 THIS IS LINE 2.... 8 THIS IS LINE 8. 9 THIS IS LINE 9.13.3 Moving a Block of Lines To move lines 1-3 before line 6: -----------------------------------------------------------------------1... Introduction 1-23 .+..+.+.4.+.+. -> B 6 THIS IS LINE 6.......+....4. ->>MM 3 THIS IS LINE 3. 7 THIS IS LINE 7..... ------------------------------------------------------------------------ The result will be: -----------------------------------------------------------------------1... 1 THIS IS LINE 1 ...1... -> 5 THIS IS LINE 3..13 CICS Editor 1.. ------------------------------------------------------------------------ Chapter 1.+...1...5.. 9 THIS IS LINE 9..6...2...3.

+....2....... 7 THIS IS LINE 7....6....... ->>DD 4 THIS IS LINE 4..13 CICS Editor 1....4.. ->>DD 9 THIS IS LINE 9..+...6.3. 5 THIS IS LINE 5.1.+..+...4.+.....5.1....2.+........... 6 THIS IS LINE 6.+. 3 THIS IS LINE 3..+.+. 1 THIS IS LINE 1 ......... ------------------------------------------------------------------------ The result will be: -----------------------------------------------------------------------1. 1 WDAY 2 THIS IS LINE 2.. 3 THIS IS LINE 3.3.+...5....1. 8 THIS IS LINE 8..4 Deleting a Block of Lines To delete lines 4-9: -----------------------------------------------------------------------1.+. 1 WDAY 2 THIS IS LINE 2. ------------------------------------------------------------------------ 1-24 Online Guide ..13.....+.... 1 THIS IS LINE 1 ...

.. 13 THIS IS LINE 9.. 3 THIS IS LINE 3. 1 THIS IS LINE 1 ... 9 THIS IS LINE 5..+. Introduction 1-25 ....5....+...+.13...1.. 8 THIS IS LINE 8....5... 1 WDAY 2 THIS IS LINE 2. 1 WDAY 2 THIS IS LINE 2.. ->> 6 THIS IS LINE 4.+......13 CICS Editor 1.. 3 THIS IS LINE 3.3.. 14 THIS IS LINE 1 .2.6. ->> 7 THIS IS LINE 4.. ->> 5 THIS IS LINE 4. 5 THIS IS LINE 5....+.. ->>R4 4 THIS IS LINE 4....4. 11 THIS IS LINE 7.+.+.... ------------------------------------------------------------------------ The result will be: -----------------------------------------------------------------------1..+...3. ->> 4 THIS IS LINE 4.. 12 THIS IS LINE 8.. ------------------------------------------------------------------------ Chapter 1..2.. 9 THIS IS LINE 9.. 7 THIS IS LINE 7.......1.+..+.......5 Repeating a Line To repeat line 4 four times: -----------------------------------------------------------------------1...+. 6 THIS IS LINE 6..1....6.4. ->> 8 THIS IS LINE 4. 1 THIS IS LINE 6....+..

.

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 . Starting CA-Scheduler Online CA-Scheduler is an ISPF application.Chapter 2.

2 1 Computer Associates International.CA-SCHEDULER 9. .1 Logging on to CA-Scheduler Your site may require you to log on to CA-Scheduler. Inc. ------------------------------------------- Enter the user ID.2. . . If so. Read Password . . xxyy (SCHD) SIGNON -------------------- ------------------------------------------CA-Scheduler copyright 1989. Write Password . and write passwords provided by your site's CA-Scheduler Administrator. . read. CA-Scheduler displays the following panel: ---------------------. . COMMAND ===> Signon information: Userid . . 2-2 Online Guide .1 Logging on to CA-Scheduler 2. .

Starting CA-Scheduler Online 2-3 . DATABASE. Inc.2. to define and maintain the workload. 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. ------------------------------------------- Use option 0. “Reports” for more information. Chapter 2. Use option 2. to interact with the current workload. See Chapter 3. to issue and view CA-Scheduler reports.2 CA-Scheduler Main Menu 2. Use option 3.2 CA-Scheduler Main Menu The CA-Scheduler main menu is the starting point for the online system. “Monitor” for more information. ------------------------.CA-SCHEDULER 9. See Chapter 5. Use option 1. See Chapter 6. REPORTS. “Options” for more information. “Database” for more information. See Chapter 4. MONITOR. OPTIONS. 2 3 Computer Associates International. to tailor the CA-Scheduler online environment to your preferences.

.

a confirmation panel is displayed when an object is being deleted from the database. Error) (Yes. Default JOBCHAIN Repeat . If NO. Deadlock) (All. Err. . ---------------------. . . No) (Yes. No. . Default Analyze List Type . Command Output from Status . . . NO Only schedule and job names are displayed. The options allow you to tailor the CA-Scheduler online dialog. . The fields are: Delete Confirmation If YES. . . COMMAND ===> Options: Delete Confirmation . Size/Type: Required: Default: YES or NO Yes Yes Default Analyze List Type When displaying an Analyze panel. 1 to 999) (Yes. . . . . . . Chapter 3. . . . No) Enter END to exit.CA-SCHEDULER 9. . this value will be filled in for the List field. xxyy (SCHD) OPTIONS -------------------- YES ERR ALL YES 4 1 YES (Yes. .Chapter 3. No) ( 1 to 99) (1 to 1 ) (blank. Command Prompt from Status . . Options 3-1 . Default Start/Complete Station Temporary file secondary size Default JOBCHAIN Levels . . Valid values are: YES All information about analyzed schedules and jobs is displayed. . Options Option 0 (zero) of the CA-Scheduler main menu displays the options dialog. . . the object is deleted without any confirmation. . .

Command output that includes a warning or error message is always displayed. The file is allocated with one track and a secondary allocation size of the number you specify here. 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. If you get a message that the file is full when viewing command output. 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. All The command output always displays. Size/Type: Required: Default: 1 to 3 digits in the range 1 to 100 Yes 1 3-2 Online Guide . 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.ERR Only error messages are displayed. consider increasing this value. DEADLOCK Only deadlocks and the deadlock path is displayed. 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. Normal OS/390 operations allow fifteen secondary extents of the size you specify before a data set is considered full. Yes Display the prompt panels allowing default options to be changed. No Issue the command with all default values.

12. 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. 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. RETRIEVE ) not supported Chapter 3. These panels are at options 3. These panels are at options 3. Enter END to exit.Default JOBCHAIN Levels The value entered here will be automatically filled in whenever a JOBCHAIN command prompt panel is displayed. If the value is blank.11 and 3. then all levels are displayed. 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. Options 3-3 .11 and 3. xxyy (SCHD) PFKEYS ------------------ To change please overtype PFKEY value. SWAP.12. The following panel is displayed: CAJI 2 --------COMMAND ===> CA-SCHEDULER 9.

.

See 4.CA-SCHEDULER 9. Status for jobs within a specific schedule may also be viewed. The last ten commands issued are retained and may be recalled. See 4. to display the CA-11 main menu. See 4. Use option 3.4. to view the condition of the current workload from a schedule perspective. COMMAND. to issue any CA-Scheduler command. “Job Status” on page 4-16 for more information. Use option 5. This option is not available for CICS. to build and issue monitor commands. STATJOB. Use option 4.2. to view the condition of the current workload from a job perspective. 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. --------------------. Jobs from more than one schedule may be viewed at the same time.3. “Commands” on page 4-43 for more information. STATUS. “Schedule Status” on page 4-2 for more information. Use option 2. FREECMD. Use option 1. “FREECMD” on page 4-187 for more information. Monitor 4-1 .Chapter 4. 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. See 4.1. Monitor Option 1 of the CA-Scheduler main menu displays the monitor menu. Chapter 4. CA-11.

The CA-Scheduler started task does not need to be active.4. The categories you select are saved across CA-Scheduler sessions. 4-2 Online Guide . To display all of the jobs. .1 Schedule Status 4. . The fields are: Schedule A full or partial schedule name to limit the schedules displayed. Size/Type: Required: 1 to 8 alphanumeric characters No Select Status Select one or more of the status categories that you want displayed. 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. You may either have all of the jobs in the schedule displayed. xxyy (SCHD) SCHEDULE STATUS ---------------- Select Status: / All (if selected. ----------------. To display a panel requesting which statuses should be shown. or only display jobs with selected statuses. enter FILTER. ALL Enter END to exit.CA-SCHEDULER 9. or filter based on above? When the schedules are displayed. Select a category by typing any non-blank character to the left of the category title.1 Schedule Status Option 1 of the CA-Scheduler monitor menu displays the schedule status selection panel. Selecting the category All causes any other selections to be ignored. . enter ALL. Display all jobs in the schedule. COMMAND ===> Include: Schedule . or blanks to show all schedules. regardless of the job's status. Press Enter to display the schedule status panel. . or FILTER . you may display the jobs within the schedules by typing a J next to the schedule name.

2.2. Press PF5 to refresh the status of the currently displayed schedules.3. Monitor 4-3 .3.1 Schedule Status --------------------. 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.CA-SCHEDULER 9. along with its current status description and backlog condition.4. even if the schedules' status no longer matches the status categories requested. As you scroll down. Any CA-Scheduler command may be entered in the space provided.3. The upper right-hand corner of the panel displays the current range of rows and the total number of rows.2. “Force Schedule Command” on page 4-93. See 4.10. Display a list of jobs in this schedule. “Cancel Schedule Command” on page 4-68. CA-Scheduler only reads the first 50 schedules before displaying the list. Issue a HOLD SCHEDULE command. COMMAND ===> xxyy (SCHD) STATUS - ROW 1 TO 11 OF 11 SCROLL ===> CSR Enter CA-Scheduler command below. “Cancel Post Schedule Command” on page 4-77. Chapter 4. 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. Issue a FORCE SCHEDULE command.2.3. See 4. See 4.5. Note: Refreshing the display by using PF5 or PF6 is not supported by CICS. “Hold Schedule Command” on page 4-99.2. more rows are automatically added until the entire list has been built. See 4. See 4. Press PF6 to list all of the schedules that currently match the status categories requested. Issue a CP SCHEDULE command. “Job Status” on page 4-16.8.3.

See 4. See 4. See 4. “Release Schedule Command” on page 4-132. Issue a RUN SCHEDULE command. “Run Schedule Command” on page 4-151. 4-4 Online Guide . Use option 1. Status .2. Display detail information about the schedule. Issue a POST SCD command. Issue an SREQ SCHEDULE command. .12. DETAILS.Detail Information on the Schedule PREDECESSORS .22. . Repeat the previous command.19.3.14. DETAILS . If a schedule is selected (command of S).3. CA-Scheduler displays the following panel: ------------.3. 1 2 xxyy (SCHD) SCHEDULE STATUS DETAIL ------------- From Node . “Unpost Schedule Command” on page 4-168.2.2.Information on this Schedule's Predecessors Enter END to exit.2. “Predecessor Display” on page 4-38.4. .15. . .2.3.2.2. “Request Schedule Command” on page 4-140.18. See 4. Issue an UNPOST SCD command. Issue a REQUEST SCHEDULE command.3. See 4. to display and alter information about the schedule in the current workload. See 4. . “SREQ Schedule Command” on page 4-156. See 4.2.13. See 4. Issue a RELEASE SCHEDULE command.2. “Purge Schedule” on page 4-127. .1 Schedule Status Command P POst PUrge RELease REQuest RUn S SReq Unpost = Use Display the schedule's predecessors. OPTION ===> Schedule . See the next topic for more information. and the predecessor's status. Issue a PURGE SCHEDULE command. “Post Schedule Command” on page 4-109.3.3.CA-SCHEDULER 9.

To exit without saving any changes. . . . PREDECESSORS. Track Must End Time . Current Status: Status . enter CAN on the command line.1 Schedule Status Detail The Schedule Status Detail panels display current information about the schedule in the workload. . . . .2. . “Predecessor Display” on page 4-38. . See 4. . Track Maximum Time . Late due to Must End Time . The output of the command is displayed.4. . Selection Code . . .1 Schedule Status Use option 2. ------------. DOWN for next screen. . 4. Predecessor Priority . You can bypass this panel by entering a 1 or 2 instead of an S to select the schedule. allowing you to correct the problem. Late: Late due to Must Start Time . The batch utility to use is CAJUCMD0. .2. Track Must Start Time . Backlog Eligible . or UP for previous screen. . . . If an error is detected. the Scheduler Status Detail panels are redisplayed. . .CA-SCHEDULER 9. Monitor 4-5 . To save any changes and exit. use PF3. The fields are contained on several panels. Late due to Maximum Time . . . . .1. . A command is built and sent to the CA-Scheduler started task for any modifications. Job Count . xxyy (SCHD) SCHEDULE STATUS DETAIL ------------- From Node . Some of the fields may be modified. Use PF7 and PF8 to scroll up and down through the panels. . Currently Backlogged Waiting on Global . to display a list of the schedule's predecessors. COMMAND ===> Schedule . . . . . You may jump to this panel from other Schedule Status Detail panels by using one of the following jump commands: TOP STATUS LATE Chapter 4. . . The batch command is TALTER SCHEDULE. Enter END to exit. .

Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name From Node The owning JES NJE node of this schedule.4. Selection Code The reason why this schedule is part of the current workload. Indicates that it is selected by default every day because no selection criteria were defined or the criteria record is blank (NULL). (This schedule was defined on the ABEND option as an alternate schedule in case of abend. Display only with no batch equivalent. Indicates that it was added to today's workload by the online ADD command. Indicates that it was added to today's workload by the online RUN command. 80 84 88 92 93 94 95 4-6 Online Guide .79 This number Corresponds to the position of the reason on the criteria statement that was defined for this job or schedule. If RC is 01 . This field is blank if the CA-Scheduler installation option NJE is set to NO. including Not Requested jobs. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Local node name Status The current status of the schedule. A job will inherit the reason code from a schedule if no criteria record exists for the job. Job Count The number of jobs. Display only with no batch equivalent.1 Schedule Status The fields are: Schedule The name of the schedule being displayed or altered.) Indicates that the job originates from another node (NJE). that are in the current workload. Indicates that it was selected because today's date corresponds to a workday on the calendar that was defined for this job or schedule. Identifies a schedule that is being run because a job abended. Indicates a nonscheduled OS/390 job.

the schedule has a Must Start Time. Display only with no batch equivalent. Monitor 4-7 . the schedule has a Must End Time. Track Must End Time If YES. Display only with no batch equivalent. 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. Backlog Eligible Indicates if the schedule. This value is only of use to Computer Associates Technical Support. the schedule did not end by its Must End Start Time. should be backlogged if the schedule has not completed at the next autoscan. Display only with no batch equivalent. Late due to Must End Time If YES.1 Schedule Status 96 Indicates that this job was a backout job that was submitted for an abended job that specified ABEND=BACKOUT. Display only with no batch equivalent. Display only with no batch equivalent. the schedule did not start by its Must Start Time. Size/Type: YES or NO Required: No Batch Keyword: Backlog Currently Backlogged Indicates if the schedule is backlogged now. Track Maximum Time If YES. the schedule has a Maximum Time. Display only with no batch equivalent. Display only with no batch equivalent. Late due to Maximum Time If YES.4. Display only with no batch equivalent. Late due to Must Start Time If YES. Waiting on Global Indicates if the schedule has an unsatisfied global variable in its criteria. and all of its jobs. Chapter 4. Track Must Start Time If YES. Display only with no batch equivalent. Predecessor Priority A number used in ordering schedules on an internal chain of control blocks. the schedule has been started longer than its Maximum Time.

the schedule does not have an early start time. . . . . . . . . . Maximum Execution .1 Schedule Status Press PF8 for the next panel. If the time field is 0000. 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 . . 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. .4. . . 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. . DOWN for next screen. The date must be at least the value of the Scheduled Time date. . . Scheduled Time Available Time Start Time . . The date must be at least the value of the Scheduled Time date. . . . End Time . . . ------------. . xxyy (SCHD) SCHEDULE STATUS DETAIL ------------- From Node . . . The values are a seven-digit Julian date (YYYYDDD) and a four-digit time (HHMM). or UP for previous screen. . .CA-SCHEDULER 9. . . . . . Times: Early Start Time . . . . Must End Time . . . COMMAND ===> Schedule . the schedule does not have a must start time. Must Start Time . If the time field is 0000. The values are a seven-digit Julian date (YYYYDDD) and a four-digit time (HHMM). . . Enter END to exit. User-specified Average Historical Average . . .

where dd is the number of autoscans and hhmm is the time. Press PF8 for the next panel. 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. Available Time The date and time the schedule was first available to start. Scheduled Time The date and time the schedule was added to the workload. If the time field is 0000. | Chapter 4. The value is in the form ddhhmm. 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.1 Schedule Status | Must End Time The latest date and time that the schedule may end before being marked late. User-specified Average The length of time entered on the schedule in the database as an average execution time. Monitor 4-9 . 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. The values are a seven-digit Julian date (YYYYDDD) and a four-digit time (HHMM). Display only with no batch equivalent. the schedule does not have a must end time. based on the last seven executions of the schedule.4. Display only with no batch equivalent. Historical Average The average amount of time for this schedule to execute. Display only with no batch equivalent. Display only with no batch equivalent. End Time The date and time of the most recent end of the schedule. The date must be at least the value of the Scheduled Time date.

. Sysid . . Auto Select . Sysid . . . . . . . if any. . Executing At Sysid The system ID of the CA-Scheduler where the schedule is executing. 4-10 Online Guide . . . 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. . . . DOWN for next screen. Other: Continue on bad jobs Date on RUN Command Use Simulate Times User Data . .4. Scheduled At: Node . Calendar The name of the calendar. .CA-SCHEDULER 9. . . the schedule is eligible for autoscan to add it to the workload. . or UP for previous screen. Scheduled At Sysid The system ID of the controlling CA-Scheduler. .1 Schedule Status ------------. . . . . specified on the schedule's criteria. Calendar . . Executing At: Node . . . . COMMAND ===> Schedule . Date Table The name of the date table used in bringing the schedule and its jobs into the current workload. . . . . . . Enter END to exit. . Auto Select If YES. . . 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. . xxyy (SCHD) SCHEDULE STATUS DETAIL ------------- From Node . . . . Selection: Date Table .

. . . . The job abended and has ABEND=CONT. .1 Schedule Status Continue on bad jobs If YES. Userids: User who User who User who User who User who . . . . Use Simulate Times If YES. and Must End Times may have been generated by the SIMULATE command. . . The job ended successfully. . Cancelled Forced . COMMAND ===> Schedule . . . . . . . 3. User Data Any user specific data associated with this schedule. The job was completed with the COMPLETE command. . the Early Start Time. or UP for previous screen. ------------. .4. 4. Scheduling Environment. . . . Released . . . the schedule's successors are posted if one of the following is true for every job in this schedule: 1. . Must Start. If not. . then the DATE value is displayed here. . . Insert CA-11 JCL DDName . Enter END to exit. Date on RUN Command If the RUN command with the DATE parameter was used to add the schedule to the workload. . Issued RUN Held . DOWN for next screen. . Monitor 4-11 . Job Defaults: Library Type Stage JCL . . . . Size/Type 1 to 16 alphanumeric characters Required: No Batch Keyword: USERData Press PF8 for the next panel. .CA-SCHEDULER 9. . xxyy (SCHD) SCHEDULE STATUS DETAIL ------------- From Node . then zeros are displayed. . . . Security: Userids . . . . The data may be supplied by a user exit (see the Notification Exit in the Systems Programmer Guide) or on the TALTER SCHEDULE command. . . . . . . . . . Insert Sched Enviro . . 2. Chapter 4. . The job failed and has FAILED=CONT.

CA-Scheduler releases the job and tracks it as if the job was submitted by CA-Scheduler. See also Scheduling Environment. USERLIB The access method is provided by a site-written exit program.4. A change in this value only applies to jobs added to the workload. or abend. Size/Type: YES or NO Required: No Batch Keyword: INSRSenv 4-12 Online Guide . See "User Exits and APIs" in the Systems Programmer Guide for more information.1. See "Performance Considerations" in the Systems Programmer Guide for performance implications. The dummy job may execute for a specified number of seconds. Jobs already in the active workload are not affected. “Job Definition” on page 5-29. 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. 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.2.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. See the field Test Parm in 5. end with a specific return code. not to jobs already in the workload. based on parameters defined at the job level. Valid values are: DRIVER CA-Scheduler generates one line of JCL to be expanded by Driver. 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. TESTLIB CA-Scheduler submits a dummy job (based on the skeleton in member CAJUTSTB of the PDS allocated to ddname JCLMASTR).2.

A change in this value only applies to jobs added to the workload. Display only with no batch equivalent.4. Blanks mean the schedule has not been canceled. Blanks mean the schedule has never been released. This field must not be blank.1 Schedule Status Stage JCL The default staging option for jobs in this schedule. Blanks mean the schedule has never been held. User who Released The last user who released the schedule. Monitor 4-13 . and Insert Sched Enviro must be set to YES before a scheduling environment (SCHENV) is inserted into the job's JCL. 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. User who Cancelled The user who removed the schedule from the workload. User who Held The last user who held the schedule. Chapter 4. Display only with no batch equivalent. 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. Insert CA-11 The default CA-11 option for jobs in this schedule. 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. Jobs already in the active workload are not affected. 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. A change in this value only applies to jobs added to the workload. A value of AUTOINIT means the schedule was added by autoscan. not to jobs already in the workload. Display only with no batch equivalent. Display only with no batch equivalent.

. . . . . 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. Display only with no batch equivalent. . . . Display only with no batch equivalent. . . . . 4-14 Online Guide . . . . Schedule Late for: . . COMMAND ===> Schedule . . . . becomes late. Press PF8 for the next panel. Enter END to Exit. . . Display only with no batch equivalent. . See below for more information. . . . . . . . Userid to Notify All Events . xxyy (SCHD) SCHEDULE STATUS DETAIL ------------- From Node . . . See below for more information. . . . . and ends. . Userids A list of users allowed to manipulate this schedule and its jobs using CA-Scheduler internal security. Schedule Start Schedule End . . . . or UP for Previous Screen. . . .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.CA-SCHEDULER 9. . . . . . Schedule Start A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the schedule starts. . . . .

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.

Chapter 4. Monitor 4-15

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

--------------------- CA-SCHEDULER 9. COMMAND ===>

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.

Chapter 4. Monitor 4-17

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.

Chapter 4. Monitor 4-19

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 . .

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: 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.

Chapter 4. Monitor 4-21

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.

Chapter 4. Monitor 4-23

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 . .

xxyy (SCHD) JOB STATUS DETAIL --------------Station . . Schedule . .

. . . . . . . . . .

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: 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

The date must be at least the value of the Scheduled Time date. Monitor 4-25 . Display only with no batch equivalent. Display only with no batch equivalent. Historical Average The average amount of time for this job to execute.4. Display only with no batch equivalent. 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. Press PF8 for the next panel. Display only with no batch equivalent. Display only with no batch equivalent. Start Time The date and time of the most recent start of the job. Scheduled Time The date and time the job was added to the workload. Display only with no batch equivalent. If the time field is 0000. where dd is the number of autoscans and hhmm is the time. | Chapter 4. Display only with no batch equivalent. Available Time The date and time the job was first available to start (submitted). based on the last seven executions of the job.2 Job Status | Must End Time The latest date and time that the job may end before being marked late. The value is in the form ddhhmm. 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. the job does not have a must end time. End Time The date and time of the most recent end of the job. The values are a seven-digit Julian date (YYYYDDD) and a four-digit time (HHMM). It is displayed only for CPU jobs (station = 40). where dd is the number of autoscans and hhmm is the time.

.4. . . 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. . . See "Performance Considerations" in the Systems Programmer Guide for performance implications. Abend Option Fail Option Job has Step . . . . . . . Abend Count . . . RMS . Member Name Insert CA-11 Memo Text . . . Sched Enviro . 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. . . JCL: Library Type JCL DDname . . . . Records Fail Code . . . xxyy (SCHD) CPU JOB STATUS DETAIL ------------Station . . . See "User Exits and APIs" in the Systems Programmer Guide for more information.CA-SCHEDULER 9. or UP for previous screen. . . . . USERLIB The access method is provided by a site-written exit program. . Schedule . . Job Step Failed . . . .2 Job Status -------------. Enter END to exit. Number . . DOWN for next screen. . COMMAND ===> Job . . . . DRIVER CA-Scheduler generates one line of JCL to be expanded by Driver. 4-26 Online Guide . . . . . . . . . . . Member Subid . . . . . . . . . . . . . . . . . From Node . . . . . CA-Scheduler releases the job and tracks it as if the job was submitted by CA-Scheduler. . . Testlib Parm Failure: Fail Oper . . . . Insert Sched Enviro . . . .

Monitor 4-27 . “Job Definition” on page 5-29. end with a specific return code. 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. The dummy job may execute for a specified number of seconds. 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.2 Job Status TESTLIB CA-Scheduler submits a dummy job (based on the skeleton in member CAJUTSTB of the PDS allocated to ddname JCLMASTR). If blank.2. 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. See the field Test Parm in 5. Display only with no batch equivalent. See also Scheduling Environment. 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.1. the job name is used. Size/Type: YES or NO Required: No Batch Keyword: INSrrms Chapter 4. or abend. Member Name The member in the library that contains the job's JCL. based on parameters defined at the job level.4.2.

This field must not be blank. CONT Allow successors to run as if the job ended successfully. The operator must respond OK before the job runs. Successors to this job are not posted as satisfied. GE. and Insert Sched Enviro must be set to YES before a scheduling environment (SCHENV) is inserted into the job's JCL. is posted as FAILED. Successors to this job are not posted as satisfied. Valid relational operators are EQ.4. 4-28 Online Guide . and LT. Valid values are: ABORT (or blank) Do not let successors run. 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). GT. Size/Type: 1 to 16 alphanumeric characters Required: No Batch Keyword: SCHENV Memo Text If specified. LE. 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. Display only with no batch equivalent. A value of zero with Fail Oper equal to blanks means that CA-Scheduler is not checking the Fail Code. Fail Oper. NE. Any job step ending with a condition code within the range specified by the fail code operator. this text is issued as a WTOR before the job executes.2 Job Status Scheduling Environment The name of the Workload Manager (WLM) scheduling environment that should be inserted into this job's JCL. 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. 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.

Press PF8 for the next panel. 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. whose name is built based on the CAIJGEN option BACKOUT.2 Job Status BACKOUT Submit another job. 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. CONT Allow successors to run as if the job ended successfully. Display only with no batch equivalent. Monitor 4-29 . schedule Run the specified schedule. BACKOUT Submit another job. 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. Valid values are: ABORT (or blank) Do not let successors run. Fail Option Determines what action to take if the job ends with an unacceptable return code.4. Chapter 4. Required: No Batch Keyword: FAILEd Job has Step Records If YES. whose name is built based on the CAIJGEN option BACKOUT.

. . Current location: Node . or blanks if for the local node. Calendar . . . the value is the remote node name. . Current location Node If the CA-Scheduler installation option NJE is NO. Current location Sysid The system ID where the job actually ran or blanks if the job has not started yet. Selection: Date Table . .CA-SCHEDULER 9. Number . . . Scheduled At Sysid The system ID where the job on which the job was originally scheduled to execute. . 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. Job List Full or partial job names which cannot be submitted or running when this job is submitted. . Scheduled at: Node . . After the job has been submitted and reached a different node. . . . or UP for previous screen. . . . . Resource The name of a resource internal to CA-Scheduler which this job must have exclusive control over before it can be submitted. . . . . From Node . .2 Job Status ---------------. Schedule . . . . Sysid . Enter END to exit. . . . or blanks for any system. . . .4. . . . 4-30 Online Guide . Execution: . . . . If NJE is set to YES and the job has not yet been submitted. Sysid . . DOWN for next screen. . this field is blank. . the owning (local) node is displayed. Job List . . . . xxyy (SCHD) JOB STATUS DETAIL --------------Station . . Separate Job Resource . . COMMAND ===> Job . . .

. If the CA-Scheduler installation option SUBUID includes the value JSI. . Cancelled Started . . . . . . JSI User id . Monitor 4-31 . User who Defined Job . or UP for previous screen. User User User User User User who who who who who who Held . . . Staged JCL Changed by/Group id The user and group ID who last changed the staged JCL. . . . . xxyy (SCHD) JOB STATUS DETAIL --------------Station . 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. Completed . COMMAND ===> Job . . . Forced . . DOWN for next screen. From Node . . . . . . . . . .CA-SCHEDULER 9. . . . . . User ids: User who Issued RUN . Enter END to exit. .4. . . . . Number . . . . Schedule . Released . . User who Issued SUBMIT. . Chapter 4. . . . or CA-Scheduler. these fields are blank. ---------------. . Staged JCL Changed by . If the user ID is AUTOINIT. . . . . schedule. . . . . . . . User who Defined Job/Group id The user and group ID of the last person to modify the job in the database. Press PF8 for the next panel. . .2 Job Status Date Table The date table used in evaluating the job's criteria. User who Issued SUBMIT/Group id The user and group ID of the last person who caused this job to be submitted. . . Group Group Group Group Group id id id id id . . If the JCL is not staged or has not yet been modified. . . Calendar The calendar used in selecting this job. the job was added using autoscan. . . JSI User id/Group id The user and group ID associated with the job. . . . . this user/group ID is used.

.CA-SCHEDULER 9. Use Simulation Times . . . . . . ---------------. . DOWN for next screen. CHAS 1 Documentation: Display Key . . . Internal Priority . . . . JES Class . . 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. . User who Released The last person to release this job. User who Completed The last person who issued the COMPLETE JOB command for this job. . User who Started The last person who issued the START JOB command for this job. . . . . COMMAND ===> Job . .2 Job Status User who Held The last person to hold this job. . . . . . . 4-32 Online Guide . Press PF8 for the next panel. . . . . . . . USI287ME Number . . . . 4 Schedule . Predecessor Priority . User who Cancelled The person who removed this job from the workload. . . . . 1 F 1 1 NO RELEASE Enter END to exit. KEY12345 Display Time . Command Causing Submission Date on RUN Command . . . Other: JES Priority . . User who Forced The last person to issue the FORCE JOB command on this job. . . . . . . . . . CHAS 1 From Node . User Data . . . or UP for previous screen.4. . . xxyy (SCHD) JOB STATUS DETAIL --------------1 Station .

User Data Any user-specific data associated with this job. This value is only of use to Computer Associates Technical Support. JES Priority If modified and the job has been submitted. Size/Type: 1 to 16 alphanumeric characters Required: No Batch Keyword: USERData Press PF8 for the next panel. Internal Priority A number used in ordering jobs on an internal chain of control blocks. Otherwise. the job's JES class is altered to this value. The data may be supplied by a user exit (see the Notification Exit in the Systems Programmer Guide) or on the TALTER JOB command. the Early Start Time and other time fields may have been generated by SIMULATE reports. this field is only used for SIMULATE REVISE=YES processing. Chapter 4. Monitor 4-33 . Command Causing Submission The CA-Scheduler command that caused the most recent submission of the job. Otherwise. the job's JES priority is altered to this value.2 Job Status Display Time The time at which the CA-Scheduler workload documentation entry should be displayed on the OS/390 console. This value is only of use to Computer Associates Technical Support. JES Class If modified and the job has been submitted. Use Simulation Times If YES. Predecessor Priority A number used in ordering jobs on an internal chain of control blocks. this field is used only for SIMULATE REVISE=YES processing. Date on RUN Command The date on the RUN SCHEDULE command that added this job to the current workload.4.

. . . . . . Job Abend . . . .2 Job Status ---------------. . Job Late . . . . . or UP for previous screen. Job Fail A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the job fails. Job Start A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the job starts. Job Abend A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the job abends. From Node . . . . . . . . . . . ends. . . Number . Job End A list of zero to four user IDs or OPERxxyy values to which messages will be sent when the job ends. . . . . . . Job Interrupt Job End . . . . . for: . . 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. . . See below for more information. . .4. . . . xxyy (SCHD) JOB STATUS DETAIL --------------Station . COMMAND ===> Job . . . . Job Fail . becomes late. . Schedule . . . . . . . . See below for more information. . . . . fails. See below for more information. . . . . . . . .CA-SCHEDULER 9. . . and is removed from the active workload. . . 4-34 Online Guide . . See below for more information. Enter END to exit. abends. . . . . . . . DOWN for next screen. . . . Job Purge . . . . . . . . . See below for more information. . . . Userid to Notify All Events . 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. . . . is interrupted. . . . Job Start .

.CA-SCHEDULER 9. purge.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. . . INTMSG. Number . and late messages should be sent. . COMMAND ===> Job . abend. See below for more information. . . . ABNMSG. . DOWN for next screen. Normally these include MAILBOX. end. They are stored in the CA-Scheduler active workload and must be retrieved manually by the user. Consult your site's systems programmer for a list of appropriate route codes and descriptor codes for your site. . Messages are not kept indefinitely--see the CAIJGEN option MSGHOLD for more information. ---------------. . A value of OPERxxyy sends a WTO to the OS/390 console. You may jump to this panel from other Job Status Detail panels by using one of the following jump commands: JNR NODES Chapter 4. interrupt. The xx is the route code. and the yy is the descriptor code. . . See below for more information. Inform JES Nodes: Node . . . FALMSG. ENDMSG. . . . . 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. . Schedule . Press PF8 for the next panel. PURMSG and LATMSG specify locations to which all start. Enter END to exit. and may be retrieved by the REPORT MAILBOX command. fail. The CAIJGEN options STRMSG. Messages are stored in the CA-Scheduler database when the value is MAILBOX. xxyy (SCHD) JOB STATUS DETAIL --------------Station . Monitor 4-35 . Messages to users are not TSO SEND messages. . . From Node . 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. . Password .4. xxyy (SCHD) JOB STATUS DETAIL --------------Station . COMMAND ===> Job . This field does not change where the job executes.2 Job Status The display-only fields are: Node Up to eight JES NJE nodes. . only who is told about the job. The fields are: Node The CCI node where the job should execute. . . . or UP for previous screen. User id . Enter END to exit. . ---------------. Number . The execution node (on a previous panel) must be *REMOTE. 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. . . . . . Domain . . defined by the CAIJNET macro. . Verify . | Cross-Platform information: Node . Press PF8 for the next panel. Size/Type: 1 to 15 alphanumeric characters Required: No Batch Keyword: XPDomain 4-36 Online Guide . . . . that will be notified when this job starts and ends. From Node .CA-SCHEDULER 9. . Schedule . SU Flag .

Size/Type: YES. then the Unix su command is issued with the dash ("-") option. the dash option is not used. NO. Monitor 4-37 . the global default (CAS9 CAIJGEN XPSUTYPE) value is used. Size/Type: 1 to 31 alphanumeric characters Required: No Batch Keyword: XPUser Password The password for the above user ID. If YES. or blank Required: No Batch Keyword: XPSUtype Chapter 4.4. If blank. | | | | | | | | | SU Flag Determines if the Unix Switch User (su) flag is sent for this job or not. Size/Type: 1 to 14 alphanumeric characters Required: No Batch Keyword: XPPswd Verify A second chance to type the password correctly. If NO. The setting has no impact for jobs not executing on Unix-based systems.2 Job Status User id The user ID with which the job should execute.

schedules. The following command may be entered in the command column of one or more predecessors: Command P Use Displays the predecessors of the predecessor.4. Any predecessors.-------.-------------------------------------------------. are displayed in the scrollable portion. or globals. COMMAND ===> Job . . . including jobs. 4-38 Online Guide .CA-SCHEDULER 9. May only be used on job and schedule predecessors.2 Job Status 4. 4 ROW 1 TO 1 OF 1 SCROLL ===> CSR Schedule .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. -----------------. . data sets. FLOW1 Command Type Name / Current Status Satisfied -------. 1 xxyy (SCHD) PREDECESSORS Station . along with the predecessors' current status.--------________ 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. . FL6 Number .

CARD IS REPLACED BY AN INTERNAL CARD WITH // THE PARMS TAKEN FROM THE JBR. . “DPROMPT” on page 4-42.THE EXEC CARD MAY BE LOCATED ANYWHERE IN THIS MEMBER // 5.3.'CA-SCHEDULER'.2.MSGCLASS= //TESTSTEP EXEC PGM=CAJUTSTB. .2.THE FIRST 28 POSITIONS IN THE EXEC CARD MUST NOT BE CHANGED // 7.THE EXEC CARD CANNOT BE CONTINUED.3.2.. Schedule . Besides the normal ISPF/PDF edit commands. 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'. or press PF3 to exit.THE JOB CARD MUST REMAIN THE FIRST CARD IN THIS MEMBER // 2.2 Job Status 4.3. // The editor is ISPF/PDF edit--all functions of ISPF/PDF edit are supported. // 4. and ■ 4.3 Staged JCL You can reach the Staged JCL dialog from option 3 of the Job Status Detail menu. .THE FIRST 15 POSITIONS IN THE JOB CARD MUST NOT BE CHANGED // 3. Monitor 4-39 . .2.. .CA-SCHEDULER 9. Press Enter to issue the RESTAGE command. . // IF 'TESTLIB PARMS(TESTPARM=)' WAS DEFINED IN THE JBR THEN // THE //TESTSTEP EXEC. From Node .1.2. “RECALL” on page 4-41.THE JOB CARD MAY BE CONTINUED IF DESIRED. Press Enter to stage the job. // 6. This job is not currently staged. OPTION ===> Job . xxyy (SCHD) JOB STATUS DETAIL --------------Station . “DEXPAND” on page 4-40. ---------------. the job's JCL is displayed in an edit session. The following panel displays if the job is not staged.CA-SCHEDULER 9. // 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.COMMENTS OR ADDITIONAL JCL MAY BE ADDED AS DESIRED. such as this: -----.PARM='T=1 ' // // // // THIS JCL MEMBER IS USED AS MODEL TO SUBMIT LIBTYPE=TESTLIB JOBS. // RULES FOR THIS MEMBER: // 1.3.CLASS=A. you can issue the following commands: ■ 4. ■ 4. Number . . or enter END to exit. Chapter 4. . If the job is staged.4.

3. COMMAND ===> 1 2 =NOTE= 3 =NOTE= xxyy (SCHD) STAGED JCL--BILLING. Note statements are used to indicate the beginning and end of Driver expansion.CA-SCHEDULER 9.CLASS=A. For example.'CA-SCHEDULER'. A RESET command removes them. the output might look like this: -----.1 4 BILLING --------SCROLL ===> CSR TOP OF DATA //BILLING JOB '1'.1 4 BILLING --------SCROLL ===> CSR TOP OF DATA JOB '1'.4.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.2 Job Status 4.MSGCLASS= EXEC PGM=BILLING EXEC BILLPROC BOTTOM OF DATA (The BILLPROC Driver procedure is used as an example in the Interfaces Guide. if the JCL contains the following statements: -----.1 DEXPAND The DEXPAND expands any Driver procedures in the JCL. 4-40 Online Guide . COMMAND ===> 1 2 3 4 //BILLING //STEP1 // // xxyy (SCHD) STAGED JCL--BILLING.CA-SCHEDULER 9.2. if desired.'CA-SCHEDULER'.) After the DEXPAND command is issued.CLASS=A.

COMMAND ===> 1 //BILLING 2 //STEP1 3 // xxyy (SCHD) STAGED JCL--BILLING.CLASS=A.2 Job Status 4. the example in the previous section showed the following output for the DEXPAND command: -----.4.1 4 BILLING --------SCROLL ===> CSR TOP OF DATA JOB '1'.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.2.MSGCLASS= EXEC PGM=BILLING EXEC BILLPROC BOTTOM OF DATA Chapter 4. COMMAND ===> 1 2 =NOTE= 3 =NOTE= xxyy (SCHD) STAGED JCL--BILLING.'CA-SCHEDULER'. the JCL might look like this: -----.CLASS=A.'CA-SCHEDULER'. For example.CA-SCHEDULER 9. Monitor 4-41 .3.1 4 BILLING --------SCROLL ===> CSR TOP OF DATA //BILLING JOB '1'.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.CA-SCHEDULER 9.

'CA-SCHEDULER'. Enter END to save changes and exit.'CA-SCHEDULER'. Changes to reserved variable values are only used within the edit session.CA-SCHEDULER 9. saved. “DEXPAND” on page 4-40.2 Job Status 4. COMMAND ===> xxyy (SCHD) DPROMPT -- ROW 1 TO 1 OF 1 SCROLL ===> PAGE Overtype the values of the variables below. Variable ---------&C_JOBDT Value ------------------------------yy 92 BOTTOM OF DATA Only one reserved variable. the following would be displayed: -----.3 DPROMPT The DPROMPT command lists all reserved Driver variables used by the job and their current values.CA-SCHEDULER 9.1 4 BILLING --------SCROLL ===> CSR TOP OF DATA //BILLING JOB '1'. You may change the value of &C_JOBDT by overtyping it and pressing PF3. &C_JOBDT. Enter CAN to exit without saving changes.3. For example.1 4 BILLING --------SCROLL ===> CSR TOP OF DATA JOB '1'. COMMAND ===> 1 2 =NOTE= 3 =NOTE= xxyy (SCHD) STAGED JCL--BILLING.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.1. 4-42 Online Guide .2.4. starting this edit session: -----.CLASS=A. For example.CA-SCHEDULER 9. if the value is changed to yy360. is displayed because it is the only reserved variable used by the procedure BILLPROC. The values may be changed for this edit session only.MSGCLASS= EXEC PGM=BILLING EXEC BILLPROC BOTTOM OF DATA The DPROMPT command displays the following: --------------------.CLASS=A. possibly changing the output of the DEXPAND command. COMMAND ===> 1 //BILLING 2 //STEP1 3 // xxyy (SCHD) STAGED JCL--BILLING. and another DEXPAND command issued.3.

3 Commands 4.3. Use option C3. Each option displays panels to prompt you for the keywords on that command. Use option A2.5. See 4.3.1. Use option D1.6. See 4. CAN/POST. DISPLAY. to remove a schedule or job from the current workload. Use option A1. to manually mark a job as successfully ended. 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. See 4. See 4.3 Commands Option 3 of the CA-Scheduler monitor menu displays the commands menu. ALLOC.4. “Display Commands” on page 4-82. “Cancel Commands” on page 4-65. COMPLETE. ADD. autoscan times. “Alloc Command” on page 4-63. -------------------. “Add Commands” on page 4-45. “Cancel Post (CP) Commands” on page 4-73. Use option C2.CA-SCHEDULER 9. to free a ddname from the CA-Scheduler started task. and installation options. “Dealloc Command” on page 4-80.2.3.3.4. Use option C1. All of the commands require that the CA-Scheduler started task be active. See 4. to allocate one or more data sets with a specified ddname to the CA-Scheduler started task.3. Chapter 4.3. Use option D2.3. such as data sets allocated to the started task. or to add a predecessor/successor relationship between two jobs in the active workload.3. 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. CANCEL. See 4. See 4. to view current information common to all of CA-Scheduler. to add a job that is not defined to CA-Scheduler to the active workload.7. Monitor 4-43 . “Complete Job Command” on page 4-71. DEALLOC.

“Globals” on page 4-95.15.11. “Hold Commands” on page 4-96.3. See 4.3. See 4.3. “Request Commands” on page 4-138. and data sets to start.18. HOLD.12. to copy a CPU job's JCL into the CA-Scheduler staging library.3.3. Use option R4. “Messages Menu” on page 4-102. Use option G1. “Purge Commands” on page 4-124.8. Use option R2. RUN.3. to allow schedules and jobs to start even though not all predecessors have been satisfied. REQUEST. to allow not-requested schedules and jobs and their successors to start. RERUN. Use option P1. to remove completed and canceled schedules and jobs from the status displays. See 4. Use option P2. to manually mark a job as started. PURGE. Use option S1. Use option M1. to resubmit CPU jobs that had previously failed or abended.16. “Start Job Command” on page 4-158. Use option R3. Use option R5. GLOBALS. “Release Commands” on page 4-129. to add defined schedules and jobs to the current workload.19.17. “SREQ Commands” on page 4-153. FORCE. See 4.9. RESTAGE. See 4.3. See 4. to allow schedules and jobs previously held (option H1) to start.3. See 4. “Rerun Job Command” on page 4-142.3.3. START. to prevent schedules and jobs from starting. See 4. “Post Menu” on page 4-105. POST. “Force Command” on page 4-90.3.14.10. 4-44 Online Guide . RELEASE.20. to allow not-requested schedules and jobs and selected successors to start. to allow successors of schedules. SREQ. jobs. “Run Commands” on page 4-148. Use option S2. job steps. See 4. to send or display messages within CA-Scheduler. Use option R1.13. MESSAGES. to view and change CA-Scheduler global variables. See 4. See 4.3 Commands Use option F1. Use option H1.3.3.4. See 4. See 4. “Restage Job Command” on page 4-146.

“Vary Commands” on page 4-183.3. VARY. SUBMIT. Chapter 4. to require successors of schedules. “Add Pred Command” on page 4-61 for more information.3. to start or stop CA-Scheduler NJE VTAM sessions.2. and data sets to wait. See 4.4. “Unpost Commands” on page 4-164. UNPOST.1. 4.3.22. even if the predecessor has already completed. OPTION ===> 1 2 JOB PRED .CA-SCHEDULER 9. See 4. See 4. jobs.21. job steps.3. Use option 1. PRED. Use option V1. Monitor 4-45 . Use option U1.23.3. The Add commands introduce new work or a new relationship to the active workload without having to first define anything to the database. to add a predecessor/successor relationship between two jobs in the workload. ----------------------. to add an undefined job to the active workload.3. in that their effect is only for the current active workload. Add commands are temporary.Add a Job . “Submit Job Command” on page 4-160.1 Add Commands Use option A1 of the CA-Scheduler Commands menu to display the Add menu. See 4. not for any future workload. to resubmit CPU jobs that had previously failed or abended. See 4. Use option 2. “Add Job Command” on page 4-46 for more information.Add a Predecessor xxyy (SCHD) ADD ---------------------- Enter END to exit.3 Commands Use option S3.1.1. JOB.

To issue the ADD JOB command. .3 Commands 4. 1 xxyy (SCHD) ADD JOB -------------------Schedule . 4 Miscellaneous: Internal Priority . COMMAND ===> Name . Selection: Backlog . . . 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. --------------------. .3. . . Maximum Execution . Must End . Number . use PF3. or DOWN for Next Screen. .CA-SCHEDULER 9. Must Start .1 Add Job Command Use option 1 of the CA-Scheduler Add Commands menu to display the Add Job dialog. . To exit without issuing the ADD JOB command. . The batch utility to use for adding jobs is CAJUCMD0. .4. NO Times: Early Start . . The batch command is ADD JOB. . Enter END to Exit. . The fields are contained on several panels. . . . . Station . . . Use PF7 and PF8 to scroll up and down through the panels. enter CAN on the command line. . .1. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name 4-46 Online Guide . . .

where dd is the number of autoscans that the job should wait. which executes on the system. The value is in the format of ddhhmm. and stations greater than 40 are for post-CPU manual tasks. YES indicates that the job should be retained until it (and the rest of its schedule) has completed. Up to 99 jobs with the same name. Blank causes the schedule's Backlog option to be used. Monitor 4-47 . Size/Type: 2 numeric characters Required: No Batch Keyword: STation Default: 40 Schedule The schedule to which this job belongs.4. station. Leading zeros do not need to be entered.3 Commands Number The number of the job being added. 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. and hhmm is the time to start. 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. Size/Type: YES/NO/blank Required: No Batch Keyword: Backlog Default: NO Early Start The earliest time that this job can start. NO indicates that the job should be canceled (if not currently executing) and the next day's copy made available. and schedule may be in the current workload. Stations less than 40 are for pre-CPU manual tasks. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: Erlytime Default: 0 (job may be started immediately) Chapter 4.

where dd is the number of autoscans that the job should wait. Leading zeros do not need to be entered. 4-48 Online Guide . and/or a user. The value is in the format of ddhhmm. and hhmm is the time to start. and hhmm is the time to start. A message may be sent to the console. Leading zeros do not need to be entered. CA-Scheduler searches these control blocks to find work. where 99 is the higher priority.4. 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. and hhmm is the time to start.3 Commands | | Must Start If the job has not started by this time. Leading zeros do not need to be entered. A message may be sent to the console. the MAILBOX report. it is considered late. it is considered late. the MAILBOX report. It is only displayed for CPU jobs (station = 40). 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. 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. and/or a user. the MAILBOX report. and/or a user. A message may be sent to the console. where dd is the number of autoscans that the job should wait. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JPrty Default: 0 Press PF8 for the next panel. where dd is the number of autoscans that the job should wait. it is considered late. The value is in the format of ddhhmm. The value is in the format of ddhhmm. that controls the order of internal control blocks.

4 Schedule . Chapter 4. . USERLIB The access method is provided by a site-written exit program. Valid values are: DRIVER CA-Scheduler generates one line of JCL to be expanded by Driver. . . JCL DDname . See "Performance Considerations" in the Systems Programmer Guide for performance implications. . or DOWN for Next Screen. Remote Execution Node . .4. . . Member Prefix . JCL: Library Type . 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.3 Commands ------------------. . . Remote Execution Sysid . . COMMAND ===> Name . UP for Previous Screen. . . CA-Scheduler releases the job and tracks it as if the job was submitted by CA-Scheduler. . . . Member Name .CA-SCHEDULER 9. . See "User Exits and APIs" in the Systems Programmer Guide for more information. A default access method is specified in the CAIJGEN option LIBTYPE. Enter END to Exit. 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. . 1 xxyy (SCHD) ADD CPU JOB -----------------Station . A Number . Monitor 4-49 . . . Submission: Local Execution Sysid .

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.4. The dummy job may execute for a specified number of seconds. ROSCOE CA-Roscoe Required: No Batch Keyword: Libtype Default: Value on CAIJGEN option LIBTYPE JCL DDname For library type of PDS. 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. end with a specific return code. “Job Definition” on page 5-29. the ddname of the partitioned data set containing the job's JCL. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: MBrsubid Member Name The member name that contains the job's JCL.2.2. See the field Test Parm in 5. The system ID must be part of the local multi-CPU environment.3 Commands TESTLIB CA-Scheduler submits a dummy job (based on the skeleton in member CAJUTSTB of the PDS allocated to ddname JCLMASTR). Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: NOde Default: Local NJE node 4-50 Online Guide . 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.1. based on parameters defined at the job level. or abend.

.3 Commands Remote Execution Sysid The system ID at another node on which this job should execute. Abend Option Fail Option Options: Insert CA-11 Stage JCL . 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. ------------------. . Fail Code . . GT (Greater Than). Enter END to Exit. . NO . . . The following equation is evaluated: job's-high-return-code Fail-Oper Fail-Code Chapter 4. COMMAND ===> Name . . . . . . NE (Not Equal). Failures: Fail Oper . 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. Schedule . Number . Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: NODESys Press PF8 for the next panel. . . or DOWN for Next Screen. NO . Test Parm . . . EQ (EQual). . . It is only displayed for CPU jobs (station = 40). See Fail Code. . . and LT (Less Than). . UP for Previous Screen.4. . Memo . . . . xxyy (SCHD) ADD CPU JOB -----------------Station .CA-SCHEDULER 9. Valid values are GE (Greater than or Equal). . . Monitor 4-51 . Interrupt . LE (Less than or Equal).

schedule Run the specified schedule. then the job is marked as failed. whose name is built based on the CAIJGEN option BACKOUT. making zero the only acceptable return code for the job. BACKOUT Submit another 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. CONT Allow successors to run as if the job ended successfully. whose name is built based on the CAIJGEN option BACKOUT. Valid values are: ABORT Do not let successors run. Valid values are: ABORT Do not let successors run.4. A typical setting is a Fail Oper of GE and a Fail Code of 1. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FAILEd Default: ABORT 4-52 Online Guide . BACKOUT Submit another job. schedule Run the specified schedule. CONT Allow successors to run as if the job ended successfully.3 Commands If the statement is true. 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.

A manual reply by the operator is required before the job may execute. the Test Parm determines how long the job executes and how it ends.4. Size/Type: YES or NO Required: No Batch Keyword: INterupt Default: NO Stage JCL If Stage JCL is set to Yes. separate them with commas. Size/Type: 1 to 60 alphanumeric characters Required: No Batch Keyword: MEmo Test Parm For library type of TESTLIB. Size/Type: 1 to 20 alphanumeric characters Required: No Batch Keyword: TEstparm Default: The values specified on member CAJUTSTB in your JCLMASTR data set Chapter 4. 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. Size/Type: YES or NO Required: No Batch Keyword: INSrrms Default: NO Interrupt If Interrupt is set to Yes. 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. Monitor 4-53 . the job's JCL is copied into the CA-Scheduler active workload and submitted from there.3 Commands Insert CA-11 Controls the automatic insertion of the CA-11 RMS. the job is marked as Interrupted instead of Complete when it ends normally.

It is only displayed for non-CPU jobs (station not equal to 40). . NO Enter END to Exit. The fields are: Automatic Start If Automatic Start is set to Yes. It is only displayed for CPU jobs (station = 40). then the START command must be used. See 4.4. .20. 4-54 Online Guide . then the non-CPU job is started as soon as all predecessors have been satisfied. UP for Previous Screen.3. .3 Commands Press PF8 for the next panel. Number . Non-CPU Options: Automatic Start . If Automatic Start is set to No. “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. xxyy (SCHD) ADD NON-CPU JOB ---------------Station . Schedule . . or DOWN for Next Screen. COMMAND ===> Name .CA-SCHEDULER 9. .

jobs with high JES Priority values are started first. . . The value is not used outside of simulation. JES Priority . Station . . . .4. . . . 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. Enter END to Exit. or DOWN for Next Screen. If multiple jobs are available to start. xxyy (SCHD) ADD JOB -------------------Schedule . . .3 Commands --------------------. Number . . Simulation: JES Class . . UP for Previous Screen. . . 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. . Monitor 4-55 .CA-SCHEDULER 9. Display Time . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Dispkey Chapter 4. . Documentation: Display Key . . COMMAND ===> Name . 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.

. . . . . Stepname -------- Enter END to Exit. . .3 Commands Display Time The time at which the documentation referred to by Display Key should be displayed on the OS/390 console. . . . Successors: Job name JNO -------. xxyy (SCHD) ADD PREDS ------------------Station . -------------------. . . . . . . . . . . Number . . . . . . Leading zeros do not need to be entered. . The value is in the format of ddhhmm. . . . . . COMMAND ===> Name . Schedule . . St -.CA-SCHEDULER 9. where dd is the number of autoscans that the job should wait. and hhmm is the time to start. .--. or DOWN for Next Screen. Code ---- ProcStep -------. . . Oper ---. . 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 . . . . 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. 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. The columns are: Job name The name of the job that must complete or that contains the job step that must complete. . . UP for Previous Screen. . Schedule -------.4.

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. Oper. 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. See Code. unless ProcStep.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 8 alphanumeric characters Required: No.4. 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. 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. Valid values are as follows: GE Greater than or Equal GT Greater Than EQ EQual Chapter 4. Monitor 4-57 .

Schedule -------. . . . . . . Oper ---. . . . 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 . . Typical values are Oper set to EQ and Code set to 0 (zero) to allow only a return code of zero. . . Successors: Job name JNO -------. . . ProcStep -------. . xxyy (SCHD) ADD SUCCESSORS ----------------Station . . . . The following statement is evaluated: step-return-code Oper Code If the statement is true. the condition is satisfied. . . . Code ---- Stepname -------- Enter END to Exit or UP for Previous Screen.4.CA-SCHEDULER 9. ----------------.--. .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. . . . COMMAND ===> Name . . unless Oper is specified Batch Keyword: FAILn where n is 1 to 6 Default: If Oper and Code are not entered. St -. Number . . . . Size/Type: 1 to 5 numeric characters from 0 to 4095 Required: No. . then any normal end (not an abend) of the step is accepted Press PF8 for the next panel. Schedule . . . . . . . . . . . . .

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. Monitor 4-59 . Oper. Note that the procstep is in the job being added.4. Note that the step 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. Size/Type: 1 to 8 alphanumeric characters Required: No. 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 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: 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. or Code is entered Batch Keyword: SSTEPn where n is 1 to 6 Chapter 4. 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. unless ProcStep.

4. See Code. 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. 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 . Size/Type: 1 to 4 numeric characters from 0 to 4095 Required: No. Typical values are Oper set to EQ and Code set to 0 (zero) to allow only a return code of zero. 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. The following statement is evaluated: step-return-code Oper Code If the statement is true. the condition is satisfied. Note that the step is in the job being added.3 Commands Oper A Boolean operator used to determine if the step successfully ended.

4 . . . Number . . The batch command is ADD PRED. . .2 Add Pred Command Use option 2 of the CA-Scheduler Add Commands menu to display the Add Pred dialog. . and the successor job may not have started. 1 Station . . The fields are: Job Name The name of the successor job. . . . 1 . . . The predecessor job may not be complete.3 Commands 4. Enter END to exit. .3. . . . The batch utility to use is CAJUCMD0. Both jobs must be in the workload. . . .1. Station Schedule . xxyy (SCHD) ADD PRED -------------------- Should wait for job: Job Name . 4 Schedule . COMMAND ===> Job: Job Name Number . . The Add Pred command defines a predecessor/successor relationship between two jobs in the workload without having to change the successor job's criteria. . Monitor 4-61 . . . Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The JNO of the successor job. -------------------. The successor job may not be started yet. The change is only for the current workload.CA-SCHEDULER 9.4. . . Size/Type: 2 numeric characters Required: No Batch Keyword: JNO Default: 01 Chapter 4. .

Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: PSChd 4-62 Online Guide . 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: Schedule Default: 40 Should wait for job name The name of the predecessor job.3 Commands Station The station of the successor job. Size/Type: 2 numeric characters Required: No Batch Keyword: PJNO Default: 01 Station The station of the predecessor job. 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: STation Default: 40 Schedule The schedule of the successor job.4. The predecessor job may not be completed yet.

. . YES Route Sysid . Dataset 1 Dataset 2 Dataset 3 Dataset 4 Dataset 5 Dataset 6 Dataset 7 Dataset 8 Dataset 9 Dataset 1 Options: Auto Submit . 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 Chapter 4. See also 4. “Display Alloc Command” on page 4-83. xxyy (SCHD) ALLOCATE ------------------ . “Dealloc Command” on page 4-80 and 4.3. The data set names must be fully qualified. . . . . . COMMAND ===> Allocate: DDname .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.6. . . . . . . . . . .1. you use it to allocate a new (or newly compressed) JCL library. without quotes. . . . The batch command is ALLOC. . -------------------. Your default prefix is NOT added. Monitor 4-63 .CA-SCHEDULER 9. .3.4. . Typically. .3. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: DDname Dataset 1-10 The data sets that should be allocated. The batch utility to use is CAJUCMD0. .3 Commands 4. . . . Enter END to exit. . The fields are: DDname The ddname to which the data sets is allocated in the CA-Scheduler started task. . Route . Execute command at: Sysid . . . . . .7. .

3 Commands Auto Submit If Auto Submit is set to YES. 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. 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: ROUTSys 4-64 Online Guide .4. 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. then after the successful allocation of the data sets CA-Scheduler searches for any jobs currently in Submit Failed status.

3. to remove a specific job from the workload. “Cancel Job Command” on page 4-66 for more information.5.2. Successor jobs and schedules are not allowed to start.1.4. See also 4.3. SCHEDULE.3.CA-SCHEDULER 9.Cancel a Job SCHEDULE .3. Use option 1. ALL. to remove all schedules and jobs from the workload.3. See 4. Chapter 4. See 4.3. JOB.3. “Cancel Post (CP) Commands” on page 4-73. OPTION ===> 1 2 3 xxyy (SCHD) CANCEL --------------------- JOB . Monitor 4-65 . “Cancel All Command” on page 4-70 for more information.3.3. --------------------. See 4.Cancel a Schedule ALL . “Cancel Schedule Command” on page 4-68 for more information. The Cancel commands remove work from the current workload. Use option 2.3 Commands 4. to remove a schedule and all of its jobs from the workload.Cancel All Jobs and Schedules Enter END to exit.3 Cancel Commands Use option C1 of the CA-Scheduler Commands menu to display the Cancel menu. Use option 3.

COMMAND ===> Job: Job Name . . . . -------------------. The Cancel Job command removes a specific job from the workload. 4 .3. Execute command at: Route . The batch command is CANCEL JOB. xxyy (SCHD) CANCEL JOB ------------------- Cancel job . . 1 . The fields are: Job Name The name of the job to be removed from the workload. . .4. Number . . From Node . If the job has been submitted to OS/390. . . (if already submitted/started) Enter END to exit. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 4-66 Online Guide . Route Sysid . it is canceled even if it is currently executing.3 Commands 4. . . . . . The batch utility to use is CAJUCMD0. Schedule . .3. Station . . .CA-SCHEDULER 9. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be removed from the workload. . . .1 Cancel Job Command Option 1 of the Cancel menu displays the Cancel Job dialog.

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. the CAIJGEN CANCJOB value is used. If not specified. Monitor 4-67 . 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. 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 Chapter 4. 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: FMnode 4-68 Online Guide . From Node . COMMAND ===> Schedule: Schedule Name . .3.CA-SCHEDULER 9. . Cancel jobs . ----------------. . If any of the jobs have been submitted to OS/390. This field is only used in an NJE environment. xxyy (SCHD) CANCEL SCHEDULE ---------------- (if already submitted/started) Enter END to exit. Execute command at: Route . Route Sysid . . 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. . The Cancel Schedule command removes a schedule and all of its jobs from the current workload. The fields are: Schedule The name of the schedule to be removed from the workload.3 Commands 4. . The batch utility to use is CAJUCMD0.2 Cancel Schedule Command Option 2 of the Cancel menu displays the Cancel Schedule dialog. . . . they are canceled even if they are currently executing. The batch command is CANCEL SCHEDULE.3. .4.

If not specified.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. 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. the CAIJGEN CANCJOB value is used. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTsys Chapter 4. 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. Monitor 4-69 .

4.3. The Cancel All command removes all schedules and jobs from the current workload.3.3 Cancel All Command Option 3 of the Cancel menu displays the Cancel All dialog. The batch utility to use is CAJUCMD0. The command has no keywords. If any of the jobs have been submitted to OS/390. The batch command is CANCEL ALL.3 Commands 4. The panel has no fields.CA-SCHEDULER 9. they are canceled even if they are currently executing. Press PF3 to exit without canceling the workload. 4-70 Online Guide . ------------------. Press Enter to cancel the entire workload. COMMAND ===> xxyy (SCHD) CANCEL ALL ------------------- Press ENTER to cancel all Schedules and Jobs. Enter END to exit.

. you use the Complete Job command for non-CPU jobs. xxyy (SCHD) COMPLETE JOB ------------------ Options: CPU Job . NO Execute command at: Route . The fields are: Job Name The name of the job to be completed. . .CA-SCHEDULER 9. . . Enter END to exit. Route Sysid .3 Commands 4. . . From Node . . . 39 . . . . Station .4.4 Complete Job Command Use option C2 of the CA-Scheduler Commands menu to display the Complete Job dialog. COMMAND ===> Job: Job Name . Successor schedules and jobs are allowed to start. . Schedule . 1 . Typically. Monitor 4-71 . .3. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 Chapter 4. . Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be completed. . The command is COMPLETE JOB. . The Complete Job command manually marks a job as successfully completed. . . . . . . Number . -----------------. but you may also use it for CPU jobs in a recovery situation. The batch utility to use is CAJUCMD0. . . .

4. CPU Job is used as a safety to prevent a manual completion on a job running in the system. 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.3 Commands Station The station of the job to be completed. Only used in an NJE environment. “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: FMnode Default: Current node CPU Job Specify YES if this is a CPU job (station 40). 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. 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 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4-72 Online Guide . 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.

The Cancel Post commands remove work from the current workload. See also 4.5 Cancel Post (CP) Commands Use option C3 of the CA-Scheduler Commands menu to display the Cancel Post menu. Use option 1. Monitor 4-73 . to remove a specific job from the workload.3. Successor jobs and schedules are allowed to start. “Cancel Post Schedule Command” on page 4-77 for more information. SCHEDULE.3 Commands 4. “Cancel Commands” on page 4-65. JOB.2. See the next topic for more information.4. See 4. ------------------. Use option 2. to remove a schedule and all of its jobs from the workload.Cancel a Schedule and Post its Successors Enter END to exit.3. Chapter 4.5. OPTION ===> 1 2 xxyy (SCHD) CANCEL/POST ------------------ JOB .Cancel a Job and Post its Successors SCHEDULE .CA-SCHEDULER 9.3.3.

. . . . From Node . . . . Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be removed from the workload. . it is canceled even if it is currently executing. . .1 Cancel Post (CP) Job Command Option 1 of the Cancel Post menu displays the Cancel Post Job dialog.CA-SCHEDULER 9. . . Number . (if already submitted/started) Execute command at: Route . . . COMMAND ===> Job: Job Name . .4. Number . The batch command is CP JOB. Successor: . . . The Cancel Post Job command removes a specific job from the workload. If the job has been submitted to OS/390. xxyy (SCHD) CANCEL/POST JOB ---------------- Cancel Job . . Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 4-74 Online Guide . . Station . Successor schedules and jobs are allowed to start. .5. . . Post only this Job Name . The batch utility to use is CAJUCMD0. . . Route Sysid . . Enter END to exit. 1 . Station . . .3. ----------------. 4 . .3 Commands 4. . The fields are: Job Name The name of the job to be removed from the workload. . Schedule . . Schedule . .

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.4. If not specified. only that successor may start. By leaving the fields under Post only this Successor blank. all successors may start.3 Commands Station The station of the job to be removed from the workload. the CAIJGEN CANCJOB value is used. Only used in an NJE environment. 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: YES|NO Required: No Batch Keyword: CANcel Default: CAIJGEN CANCJOB value Post only this Successor In allowing successors to start. Monitor 4-75 . 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. By entering a job name. leaving all others to continue waiting. 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 Chapter 4. you may allow all successors or identify a specific job that may start.

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.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.4. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4-76 Online Guide .

5. . Number . xxyy (SCHD) CANCEL/POST SCHEDULE -------------- (if already submitted/started) Execute command at: Route . Enter END to exit. COMMAND ===> Schedule: Schedule Name .3 Commands 4. From Node . Monitor 4-77 . . . -------------. . If any of the jobs have been submitted to OS/390. . The batch utility to use is CAJUCMD0. Route Sysid . Schedule . . . The Cancel Post Schedule command removes a schedule and all of its jobs from the current workload. they are canceled even if they are currently executing. The batch command is CP SCHEDULE. . Cancel jobs Post only this Job Name .3. . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Chapter 4.2 Cancel Post Schedule Command Option 2 of the Cancel Post menu displays the Cancel Post Schedule dialog. . . Successor: . . . . . . Station . . The fields are: Schedule Name The name of the schedule to be removed from the workload. . .CA-SCHEDULER 9. 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.4. . . . . This field is only used in an NJE environment. .

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 . If not specified.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. By leaving the fields under Post only this Successor blank. the CAIJGEN CANCJOB value is used. leaving all others to continue waiting. Size/Type: YES|NO Required: No Batch Keyword: CANcel Default: CAIJGEN CANCJOB value Post only this Successor In allowing successors to start. only that successor may start. By entering a job name.4. all successors may start. you may allow all successors or identify a specific job that may start.

4. Monitor 4-79 .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 Chapter 4.

. Execute command at: Sysid . . Route Sysid . COMMAND ===> Deallocate: DDname . .3. 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. xxyy (SCHD) DEALLOCATE ------------------- Enter END to exit.CA-SCHEDULER 9.3 Commands 4. . The fields are: DDname The ddname that should be freed from the CA-Scheduler started task. Route .4. . The Dealloc Command frees (deallocates) a specified ddname from the CA-Scheduler started task. . The batch utility to use is CAJUCMD0. . . You typically use the command to make a JCL data set available for compressing. . . . The command is DEALLOC. . Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: SYSid Default: Current CPU 4-80 Online Guide .6 Dealloc Command Use option D1 of the CA-Scheduler Commands menu to display the Dealloc Command dialog. ------------------. .

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. Monitor 4-81 .4. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTsys Chapter 4.

7.7.6.4. to display the status of cross-platform nodes with which CA-Scheduler is communicating. XPLAT. Use option 4. See 4. ALLOC. Use option 6.3. DATE. to display the status of the CA-Scheduler NJE VTAM sessions. Use option 3.5. See 4. 4-82 Online Guide .3. “Display Dataset Command” on page 4-85 for more information. 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 2. “Display Network Command” on page 4-87 for more information. Use option 5. MVSJOBS. DATASET.7. See 4. to list the contents of the CAIJ$DSN macro currently being used. “Display Security Command” on page 4-87 for more information. See 4.7 Display Commands Use option D2 from the CA-Scheduler Commands menu to display the Display Commands menu. See 4. Use option 1.3 Commands 4. NETWORK.3. “Display MVSJobs Command” on page 4-86 for more information. Use option 7.7. See 4. “Display XPLAT Command” on page 4-88 for more information.3.3.3. to list the contents of the CAIJ$SEC macro currently being used.CA-SCHEDULER 9.3.3. “Display Date Command” on page 4-84 for more information. to get status on autoscan.2. SECURITY.7.7. to list the contents of the CAIJ$MVS macro currently being used. See the next topic for more information. --------------------.7.4. to display data sets allocated to the CA-Scheduler started task.

.CA-SCHEDULER 9. The batch utility to use is CAJUCMD0. Use option 9. “Display Flow” on page 4-88 for more information. Use option A.3.3 Commands Use option 8.3.7. The fields are: DDname If entered. 4.7. See 4. to display a list of virtual resources known to CA-Scheduler. data set name. VRM. Monitor 4-83 . . See 4. and volume serial are displayed.1 Display Alloc Command Option 1 of the CA-Scheduler Display Commands menu displays the Display Alloc Command dialog. EVENTS.3. COMMAND ===> Options: DDname .7. to display a list of flows available for the Critical Path Monitoring system. .4.9. xxyy (SCHD) DISPLAY ALLOC ----------------- (Leave blank for all allocations) Enter END to exit. “Display Events” on page 4-88 for more information. -----------------. Display Alloc shows only the specified ddname and its data sets. and the jobs currently using or waiting for those resources.3. The Display Alloc Command lists the data sets allocated to the CA-Scheduler started task. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: DDname Default: All ddnames Chapter 4. to display the cross-platform external events that are currently being tracked. The ddname. “Display VRM Command” on page 4-89 for more information. The batch command is DISPLAY ALLOC. See 4.7.10. FLOW.8.

COMMAND ===> System: Sysid . xxyy (SCHD) DISPLAY DATE ------------------ (Leave blank for local system) Enter END to exit. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: SYSid Default: Current system 4-84 Online Guide . -----------------.3 Commands 4.4.7. The Display Date Command provides information about the last autoscan performed and the next autoscan to be performed.2 Display Date Command Option 2 of the CA-Scheduler Display Commands menu displays the Display Date Command dialog.CA-SCHEDULER 9. It also gives the current system date and time. . The field is: Sysid The system ID for which you want to see autoscan information.3. The batch utility to use is CAJUCMD0. The batch command is DISPLAY DATE.

Size/Type: 1 to 6 numeric characters Required: No Batch Keyword: FOr Default: All entries Chapter 4. See the CAIJ$DSN Macro in the Systems Programmer Guide. . The Display Dataset Command lists the contents of the CAIJ$DSN macro currently in use. xxyy (SCHD) DISPLAY NJE DATASETS -------------- (Leave blank to start at the top) (Leave blank to entire list) Enter END to exit. COMMAND ===> Options: From entry . . . The batch command is DISPLAY $DSN.CA-SCHEDULER 9.4. Monitor 4-85 . 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.3. The batch utility to use is CAJUCMD0.3 Display Dataset Command Option 3 of the CA-Scheduler Display Commands menu displays the Display Dataset Command dialog.7. For entries .3 Commands 4. -------------. The fields are: From entry The output starts at the CAIJ$DSN entry number specified here.

The batch command is DISPLAY $MVS. The batch utility to use is CAJUCMD0. xxyy (SCHD) DISPLAY $MVS JOBS --------------- (Leave blank to start at the top) (Leave blank to entire list) Enter END to exit. 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. See the CAIJ$MVS Macro in the Systems Programmer Guide.4.3 Commands 4.4 Display MVSJobs Command Option 4 of the CA-Scheduler Display Commands menu displays the Display MVSJobs Command dialog. COMMAND ===> Options: From entry . ---------------. . .7. For entries . .3. Size/Type: 1 to 6 numeric characters Required: No Batch Keyword: FOr Default: All entries 4-86 Online Guide . The Display MVSJobs Command lists the contents of the CAIJ$MVS macro currently in use. The fields are: From entry The output starts at the CAIJ$MVS entry number specified here.CA-SCHEDULER 9.

it is issued immediately without an intervening panel. The batch command is DISPLAY NETWORK.3. Since the command has no keywords.5 Display Network Command Option 5 of the CA-Scheduler Display Commands Menu displays the Display Network command.3. The batch utility to use is CAJUCMD0. The Display Network command lists the status of the CA-Scheduler NJE VTAM sessions.7.7.3 Commands 4.6 Display Security Command Option 6 of the CA-Scheduler Display Commands menu displays the Display Security command. Monitor 4-87 . The batch command is DISPLAY $SEC. Chapter 4.4. 4. it is issued immediately without an intervening panel. The batch utility to use is CAJUCMD0. The Display Security command lists the CA-Scheduler security options currently in use. Since the command has no keywords.

4-88 Online Guide .7 Display XPLAT Command Option 7 of the CA-Scheduler Display Commands menu displays the Display XPLAT command.3. The batch command is DISPLAY FLOW. The batch utility to use is CAJUCMD0.3. The Display XPLAT command lists the cross-platform nodes with which CA-Scheduler is communicating and their status. 4. it is issued immediately without an intervening panel. Since the command has no keywords. The Display Events command lists the cross-platform external events that are currently being tracked.7.4.9 Display Flow Option 9 of the CA-Scheduler Display Commands menu displays the Display Flow command. Since the command has no keywords.3 Commands 4. The batch utility to use is CAJUCMD0. The batch command is DISPLAY XPLAT. 4. it is issued immediately without an intervening panel.3.8 Display Events Option 8 of the CA-Scheduler Display Commands menu displays the Display Events command. Since the command has no keywords.7. The batch command is DISPLAY EVENTS.7. it is issued immediately without an intervening panel. The batch utility to use is CAJUCMD0. The Display Flow command lists Critical Path Monitoring job streams defined to CA-Scheduler.

or a mask to limit the virtual resources being displayed.3. 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. The batch utility to use is CAJUCMD0.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. ------------------.7. Monitor 4-89 . The batch command is DISPLAY VRM. .3 Commands 4. Size/Type: 1 to 30 numeric characters Required: No Batch Keyword: Resource Default: * (All virtual resources will be displayed) Chapter 4. . along with any jobs that currently have or are waiting for those resources. Wildcard characters * and ? may be used. . COMMAND ===> Resource: Name . .CA-SCHEDULER 9.4.

to force the start of a schedule.8 Force Command Use option F1 of the CA-Scheduler Commands menu to display the Force Command menu.3. SCHEDULE.Force a Job to Start SCHEDULE .Force a Schedule to Start Enter END to exit.2. See the next topic for more information. The Force command causes schedules and jobs to start immediately. 4-90 Online Guide .8. ---------------------. to force the start of a job. JOB.3 Commands 4. even if predecessors are still outstanding.4. OPTION ===> 1 2 xxyy (SCHD) FORCE --------------------- JOB . Use option 2. “Force Schedule Command” on page 4-93 for more information. See 4.3. Use option 1.CA-SCHEDULER 9.

. . . Monitor 4-91 .4. xxyy (SCHD) FORCE JOB ------------------- Execute command at: Route . . If the job is a CPU job. the JCL is submitted to the operating system. Any predecessors or early start time requirements are ignored. . Number . . . Enter END to exit. 1 . . Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job that is to be forced.8. Schedule . Route Sysid . The batch utility to use is CAJUCMD0. The batch command is FORCE JOB. 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. 4 .3 Commands 4. Job Name The name of the job that is to be forced. . . .3. . .1 Force Job Command Option 1 of the CA-Scheduler Force Commands menu displays the Force Job Command dialog. From Node . . . Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 Chapter 4. Station . -------------------. . .CA-SCHEDULER 9. . The Force Job command causes a job to start regardless of its status. COMMAND ===> Job: Job Name .

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 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4-92 Online Guide . 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 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.4.3 Commands Schedule The schedule of the job 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. .4. The batch command is FORCE SCHEDULE. . COMMAND ===> Schedule: Schedule .CA-SCHEDULER 9.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. .3. . . Route Sysid . . Monitor 4-93 . .3 Commands 4. xxyy (SCHD) FORCE SCHEDULE ----------------- Enter END to exit. . Execute command at: Route . The fields are: Schedule The name of the schedule that is to be forced. The batch utility to use is CAJUCMD0. . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Chapter 4. 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. Any predecessors or early start time requirements are ignored.8. From Node . ----------------.

3 Commands Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment.4. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4-94 Online Guide .

.CA-SCHEDULER 9.8 . . . . . . Monitor 4-95 . . --------------------. GBLB 9 . . GBLC 5 . .3. .12 . .8 . . but existing values may not be blanked out Batch Keyword: GBLB01 .999. . . . . GBLA 9 . or C. . .12 . . . .9 Globals Use option G1 of the CA-Scheduler Commands menu to display the Globals dialog. . . . . . . .8 . . . . . Size/Type: 1 to 8 numeric characters Required: Yes Batch Keyword: GBLA01 . . The batch command is SET GBLxnn where x is A. The fields are: GBLA01 . .16 . . and nn is 01 to 16. . . . GBLA13 . . GBLB 5 . . The batch utility to use is CAJUCMD0.16 Character values. . . . Size/Type: 1 to 8 alphanumeric characters Required: No. . . xxyy (SCHD) GLOBALS -------------------- .4. but existing values may not be blanked out Batch Keyword: GBLC01 . . Character Values: GBLC 1 . . . .16 GBLB01 . . . . . . . . . Size/Type: YES or NO Required: No.999. . . . . . . GBLA 5 . . . . .12 . Binary Values: GBLB 1 . COMMAND ===> Numeric Values: GBLA 1 . . You can use global variables in schedule and job criteria to prevent submission until some task is complete.4 . . . . . . . B.16 Yes or No. . GBLC13 .16 Numbers. . . .4 . .4 . . .16 . . GBLB13 . . .16 Chapter 4. . . . . . each in the range of zero to 99. GBLC 9 .16 . . . . . . .3 Commands 4. . . . . . . . . . . Enter END to exit. . .16 GBLC01 .

SCHEDULE. 4-96 Online Guide . Use option 2.4.3.10.3 Commands 4. ---------------------.2.4. ALL. “Hold Submit Command” on page 4-101 for more information.CA-SCHEDULER 9. “Hold All Command” on page 4-100 for more information. to hold all schedules and jobs.10. See the next topic for more information. “Hold Schedule Command” on page 4-99 for more information. Use option 4. 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. to hold a schedule and all of its jobs. Use option 1. Use option 3.3. See 4.3. See 4. See 4. to turn off all submission.3. The Hold commands prevent work from starting that has not yet started. JOB.10. SUBMIT. to hold a specific job.3.10 Hold Commands Use option H1 of the CA-Scheduler Commands menu to display the Hold menu.

. Station . Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be held. . . . The Hold Job command prevents a specific job from starting.10.3 Commands 4. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 Chapter 4. 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. Enter END to exit. but has not yet started. . From Node . 4 . Schedule .4. . 1 . If the job has been submitted to OS/390. . The batch command is HOLD JOB. . -------------------. . Monitor 4-97 .3. . . . . The fields are: Job Name The name of the job to be held. . xxyy (SCHD) HOLD JOB -------------------- Execute command at: Route . Route Sysid . . .CA-SCHEDULER 9. it is held in JES. The batch utility to use is CAJUCMD0. Number . COMMAND ===> Job: Job Name .1 Hold Job Command Option 1 of the Hold menu displays the Hold Job dialog. . .

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. Only used in an NJE environment.4. 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.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. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4-98 Online Guide .

. xxyy (SCHD) HOLD SCHEDULE ----------------- Enter END to exit. any of its jobs that have not yet started from starting.CA-SCHEDULER 9. .2 Hold Schedule Command Option 2 of the Hold menu displays the Hold Schedule dialog. COMMAND ===> Schedule: Schedule Name . -----------------. . or if it has already started. they are held in JES. Execute command at: Route . Monitor 4-99 . . The batch command is HOLD SCHEDULE. . . . 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.3 Commands 4. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Chapter 4. The batch utility to use is CAJUCMD0. This field is only used in an NJE environment. Route Sysid . The Hold Schedule command prevents a schedule from starting.10. From Node . 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. . .3. . If any of the jobs have been submitted to OS/390 but have not yet started. The fields are: Schedule The name of the schedule to be held.4. .

3. The Hold All command prevents all schedules and jobs from starting. The command has no keywords.10. 4-100 Online Guide .4. The panel has no fields.3 Hold All Command Option 3 of the Hold menu displays the Hold All dialog. Enter END to exit. -------------------. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4. they are held in JES.CA-SCHEDULER 9. The batch command is HOLD ALL. If any jobs have been submitted to OS/390 but have not yet started. Press Enter to hold the entire workload. The batch utility to use is CAJUCMD0. Press PF3 to exit without holding the workload. COMMAND ===> xxyy (SCHD) HOLD ALL -------------------- Press ENTER to hold all Schedules and Jobs.3 Commands Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment.

If you have messages issued to the console for failures (CAS9 CAIJGEN FAILMSG=(OPERxxyy)). The panel has no fields. Any jobs ready to be submitted will be marked Submit Fail--submission held. Press Enter to hold all submission.3 Commands 4. COMMAND ===> xxyy (SCHD) HOLD SUBMIT ------------------ Press ENTER to turn off all submission. Note: Jobs that are ready to be submitted while submission is held are marked as Submit Failed. the Hold Submit command applies to all work added to the workload (that is. Chapter 4. ------------------." Once the Release Submit command is issued. Also. The batch utility to use is CAJUCMD0.3. CA-Scheduler will issue messages for each job that cannot be submitted. When a job is ready to be submitted.4 Hold Submit Command Option 4 of the Hold menu displays the Hold Submit dialog. Unlike the Hold All command.CA-SCHEDULER 9. Press PF3 to exit without holding all submission. Monitor 4-101 . The Hold Submit command prevents any jobs from being submitted. The batch command is HOLD SUBMIT.10. all jobs with this submit fail status will be submitted. Enter END to exit. indicating that submission is held. The Hold Submit condition is carried over restarts of CA-Scheduler. the statuses of jobs and schedules are not changed. it is set in a submit fail status with a reason of "submission is held.4. The Submit Fail code will be 3C60. using the RUN command or autoscan) after the command is issued.

See the next topic for more information. The CAIJGEN MSGHOLD option sets the number of minutes. -------------------. QUERY. Use option 2. SEND.3. 4-102 Online Guide . Use option 1. See 4.11.Display messages sent to you . Messages are stored in the CA-Scheduler active workload.CA-SCHEDULER 9.Send a CA-Scheduler message Enter END to exit. 4. Autoscan deletes any messages that have not been displayed and are at least x minutes old.4.3.3 Commands 4.11 Messages Menu Use option M1 of the CA-Scheduler Commands menu to display the Messages Menu.2. “Send Messages” on page 4-103 for more information. to display any messages queued in CA-Scheduler for you. Messages are deleted once they are displayed.1 Query Messages Option 1 of the Messages Menu displays the Query Message dialog. to store a message in CA-Scheduler for you or for another user.3. OPTION ===> 1 2 QUERY SEND xxyy (SCHD) MESSAGES -------------------- .11.

. Size/Type: 1 to 80 alphanumeric characters Required: Yes Batch Keyword: Text User The user ID to whom this message is being sent. . See the Query Messages dialog (4. .2 Send Messages Option 2 of the Messages Menu displays the Send Message dialog. Size/Type: 1 to 3 numeric characters from 800-899 Required: No Batch Keyword: Mno Chapter 4. --------------------. Schedule . “Query Messages” on page 4-102) for information on displaying messages. The SENDMSG command stores a message for a user in the active workload. The batch utility to use is CAJUCMD0. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: User Number A number to be associated with this message. . Related Job: Job Name . . COMMAND ===> Message: Text . Job Number Station . .3 Commands 4.4. . . .1. . .CA-SCHEDULER 9. Enter END to exit. Route Sysid .3. User . . . The batch command to use is SENDMSG.11.899) Execute command at: Route .3. . Number . Monitor 4-103 . . . The fields are: Text The text of the message. xxyy (SCHD) SENDMSG -------------------- (ALL for all users) (8 .11. . .

JNo. 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. STation. number. Size/Type: 1 to 8 alphanumeric characters (job name or schedule) or 2 numeric characters (job number or station) Required: No Batch Keyword: Job. station. Schedule Route The remote NJE node name where the command should be executed. and schedule to be included in the message.4. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: SYsid 4-104 Online Guide .3 Commands Related Job A job name.

12. See the next topic for more information. STEP.3. Use option 2. “Post Schedule Start Command” on page 4-114 for more information. to satisfy a predecessor of a schedule completing. “Post Schedule Command” on page 4-109 for more information. to satisfy a predecessor of a schedule starting. The Post command is issued against the predecessor. to satisfy a predecessor of a CA-Scheduler job completing.3.4.3.3 Commands 4. not the successor schedule or job.5. to satisfy a predecessor of a CA-Scheduler job starting.12. to satisfy a predecessor of a specific step within a CA-Scheduler job. “Post Dataset Command” on page 4-116 for more information. Use option 4. Optionally. See 4.12.3. See 4.3.2. Use option 5. SSCHD. ---------------------. to satisfy a data set predecessor.12 Post Menu Use option P1 of the CA-Scheduler Commands Menu to display the Post Menu. SJOB.6.12. See 4. Monitor 4-105 . a specific successor may have its predecessor condition satisfied. Use option 7. MVS. See 4.12. Use option 6. “Post Job Start Command” on page 4-111 for more information.3. 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. without affecting other successors.3. SCHEDULE. Chapter 4. See 4.7. Use option 3. “Post Unscheduled Job Command” on page 4-118 for more information. DATASET. JOB.4. to satisfy a predecessor of a non-CA-Scheduler job completing.12. See 4. The Post commands satisfy predecessor conditions for waiting schedules and jobs. Use option 1.3.CA-SCHEDULER 9. “Post Job Step Command” on page 4-120 for more information.

. . The fields are: Job Name The job name whose successors are notified that the job has completed normally. Station . . COMMAND ===> Job: Job Name . . a specific successor job may have its predecessor satisfied instead of all successors. Schedule . Enter END to exit. .CA-SCHEDULER 9. . The batch command is POST JOB. . Number . . The batch utility to use is CAJUCMD0. Execute command at: Route . Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name 4-106 Online Guide .3 Commands 4. . . . .12. . . . The predecessor conditions are created by criteria of the form: ┌─. . . . The Post Job command satisfies predecessor conditions for jobs and schedules waiting on a specific CA-Scheduler job to successfully complete. . . . . 4 . Station . .3. Number . Schedule . Successor: . . xxyy (SCHD) POST JOB -------------------- Post only this Job Name . . -------------------. From Node . . . 1 . . .1 Post Job Command Option 1 of the CA-Scheduler Post menu displays the Post Job dialog.4. Route Sysid .1──┐ ┌─4 ──────┐ ──jobname──┼──────┼──┼─────────┼──┬──────────┬──────────────── └─-jno─┘ └─station─┘ └─schedule─┘ Optionally. .

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. 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 Chapter 4. only that successor may start.4. 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. By entering a job name. leaving all others to continue waiting. you may allow all successors or identify a specific job that may start. all successors may start. By leaving the fields under Post only this Successor blank. 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.3 Commands Number The number of the job whose successors are notified that the job has completed normally. Monitor 4-107 . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Post only this Successor In allowing successors to start.

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.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 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4-108 Online Guide .4.

. . . . . Route Sysid . . Monitor 4-109 . .2 Post Schedule Command Option 2 of the CA-Scheduler Post menu displays the Post Schedule dialog. . . . The batch command is POST SCD. Post only this Successor: Job Name . a specific successor job may have its predecessor satisfied instead of all successors. The fields are: Schedule The schedule whose successors are notified that it has completed normally. . Number .3 Commands 4. Station . . Schedule . . . The predecessor conditions are created by criteria of the form: ──SCD──schedule─────────────────────────────────────────────── Optionally. . -----------------. xxyy (SCHD) POST SCHEDULE ----------------- Enter END to exit. . COMMAND ===> Schedule: Schedule Name . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Chapter 4. .3. . .4. The Post Schedule command satisfies predecessor conditions for jobs and schedules waiting on a specific schedule to end. . . . . . 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.CA-SCHEDULER 9. The batch utility to use is CAJUCMD0. From Node . Execute command at: Route .12. .

you may allow all successors or identify a specific job that may start. 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. all successors may start. only that successor may start. leaving all others to continue waiting.3 Commands Post only this Successor In allowing successors to 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. By entering a job name.4. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4-110 Online Guide . By leaving the fields under Post only this Successor blank.

CA-SCHEDULER 9. . a specific successor job may have its predecessor satisfied instead of all successors. . The batch utility to use is CAJUCMD0. The Post Job start command satisfies predecessor conditions for jobs and schedules waiting on a specific CA-Scheduler job to start.3 Commands 4. Station . . . . Successor: . . Number .3 Post Job Start Command Option 3 of the CA-Scheduler Post menu displays the Post Job Start dialog. . . From Node . Schedule . Enter END to exit. . . . . . . Station . Route Sysid . . . The batch command is POST SJOB. Monitor 4-111 . The fields are: Job Name The job name whose successors are notified that the job has started. . . 4 . . ----------------. . . Number .12. . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Name Chapter 4. . . Schedule . .3. The predecessor conditions are created by criteria of the form: ┌─.1──┐ ┌─4 ──────┐ ──START──jobname──┼──────┼──┼─────────┼──┬──────────┬───────── └─-jno─┘ └─station─┘ └─schedule─┘ Optionally. . COMMAND ===> Job: Job Name . 1 . . . . xxyy (SCHD) POST JOB START ----------------- Post only this Job Name .4. Execute command at: Route . .

Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Post only this Successor In allowing successors to start. 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 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. only that successor may start. you may allow all successors or identify a specific job that may start. By entering a job name. leaving all others to continue waiting. 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. all successors 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 .3 Commands Number The number of the job whose successors are notified that the job has started.4. By leaving the fields under Post only this Successor blank.

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.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. Monitor 4-113 . Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys Chapter 4.

Number . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node 4-114 Online Guide . . . . .4 Post Schedule Start Command Option 4 of the CA-Scheduler Post menu displays the Post Schedule Start dialog.12. --------------. Execute command at: Route . . . .3 Commands 4. . . The batch command is POST SSCD. . . . .3. . . Route Sysid . COMMAND ===> Schedule: Schedule Name . . The batch utility to use is CAJUCMD0. . a specific successor job may have its predecessor satisfied instead of all successors.4. xxyy (SCHD) POST SCHEDULE START -------------- Enter END to exit. . The predecessor conditions are created by criteria of the form: ──START SCD──schedule───────────────────────────────────────── Optionally. . . . The fields are: Schedule The schedule whose successors are notified that it has started. . Schedule . From Node . 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. .CA-SCHEDULER 9. The Post Schedule start command satisfies predecessor conditions for jobs and schedules waiting on a specific schedule to start. Post only this Successor: Job Name . Station . . .

By entering a job name. only that successor may start. Monitor 4-115 . all successors may start. By leaving the fields under Post only this Successor blank. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys Chapter 4.3 Commands Post only this Successor In allowing successors to start. leaving all others to continue waiting. 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.4. you may allow all successors or identify a specific job that may start.

. -----------------.5 Post Dataset Command Option 5 of the CA-Scheduler Post menu displays the Post Dataset dialog. By entering a job name. . Number . COMMAND ===> Dataset: Dataset Name . . . . Enter END to exit. By leaving the fields under Post only this Successor blank. . .3 Commands 4.CA-SCHEDULER 9. . The batch utility to use is CAJUCMD0. . leaving all others to continue waiting. The Post Dataset command satisfies predecessor conditions for jobs and schedules waiting on a data set to be updated. . Route Sysid . a specific successor job may have its predecessor satisfied instead of all successors. you may allow all successors or identify a specific job that may start. The batch command is POST DSN. Successor: . Size/Type: 1 to 44 alphanumeric characters Required: Yes Batch Keyword: Name Post only this Successor In allowing successors to start. . .4. . The fields are: Dataset The data set name whose successors are notified that it has been updated. Schedule .12. . . . . only that successor may start.3. all successors may start. The predecessor conditions are created by criteria of the form: ──DSN datasetname───────────────────────────────────────────── Optionally. . Post only this Job Name . xxyy (SCHD) POST DATASET ------------------ Execute command at: Route . Station . 4-116 Online Guide .

Monitor 4-117 . Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys Chapter 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.4. 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.

Route Sysid . The batch utility to use is CAJUCMD0.6 Post Unscheduled Job Command Option 6 of the CA-Scheduler Post menu displays the Post MVS dialog. Successor: . . Enter END to exit. . all successors may start. . . .12. . Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Post only this Successor In allowing successors to start. . . The Post MVS command satisfies predecessor conditions for jobs and schedules waiting on a non-CA-Scheduler job to successfully complete. . By leaving the fields under Post only this Successor blank. Schedule .4. only that successor may start. . By entering a job name. . xxyy (SCHD) POST $MVS ------------------- Execute command at: Route . . . . .3. leaving all others to continue waiting. . . The predecessor conditions are created by criteria of the form: ──MVS jobname───────────────────────────────────────────────── Optionally. -------------------. 4-118 Online Guide . Station .3 Commands 4. The fields are: Job Name The name of the job not controlled by CA-Scheduler whose successors are notified that it has completed. . Post only this Job Name . The batch command is POST MVS. Number . COMMAND ===> Unscheduled Job: Job Name . you may allow all successors or identify a specific job that may start. a specific successor job may have its predecessor satisfied instead of all successors. .CA-SCHEDULER 9. .

Monitor 4-119 . 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.4. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys Chapter 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.

. . . Schedule . . 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 batch command is POST STEP. . The batch utility to use is CAJUCMD0. . . . . .stepname──────────────────────────── └─. Fail Code . . Schedule . Station . . . Successor: . a specific successor job may have its predecessor satisfied instead of all successors. . Route Sysid . . . . COMMAND ===> Job: Job Name . Enter END to exit. .3 Commands 4. . . 4 . Station . From Node .failcode─┘ └─-jno─┘ └─station─┘ ──┬──────────┬───────────────────────────────────────────────── └─schedule─┘ Optionally. . Execute command at: Route . .CA-SCHEDULER 9. The predecessor conditions are created by criteria of the form: ──jobname──┬───────────┬──. . .7 Post Job Step Command Option 7 of the CA-Scheduler Post menu displays the Post Job Step dialog. .──failoper. Proc Step Fail Oper Number . .3.12. . 99999) Post only this Job Name . The fields are: Job Name The job name with the step whose successors are notified that the job has completed normally. . . .1──┐ ┌─4 ──────┐ ──┬─────────────────────────┬──┼──────┼──┼─────────┼──────────── └─.CC.4. xxyy (SCHD) POST JOB STEP ----------------- Step Name . . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Name 4-120 Online Guide . . Number . ( -4 95. .procstep─┘ ┌─. 1 . . . . . -----------------.

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.4. then all successors of this step. NE (Not Equal). and LE (Less than or Equal). GE (Greater than or Equal). Valid values are blank. 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.3 Commands Proc Step The step name outside of the PROC used to identify the specific step whose successors are notified. If 99999 is entered. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 Chapter 4. LT (Less Than). 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. Monitor 4-121 . regardless of their criteria's Fail Oper and Fail Code values. GT (Greater Than). 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. EQ (EQual). 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.

leaving all others to continue waiting. 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 . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Post only this Successor In allowing successors to start. all successors may start.4. By leaving the fields under Post only this Successor blank. you may allow all successors or identify a specific job that may start.3 Commands Schedule The schedule of the job with the step whose successors are notified that the job has completed normally. only that successor may start. 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. By entering a job name.

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.3 Commands Route Use Route to execute the command on another node in an NJE environment. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys Chapter 4. Monitor 4-123 .4.

JOB. “Purge All” on page 4-128 for more information.13. ---------------------. Use option 2.2.3. OPTION ===> 1 2 3 xxyy (SCHD) PURGE --------------------- JOB . to purge all completed and canceled schedules and their jobs.3 Commands 4. Use option 3.13. ALL. “Purge Schedule” on page 4-127 for more information. See 4. See 4.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. SCHEDULE.4.3. 4-124 Online Guide . to purge a schedule and all of its jobs.CA-SCHEDULER 9.Purge a Job SCHEDULE .3.3.Purge a Schedule ALL .Purge All Ended Jobs and Schedules Enter END to exit. to purge a specific job. See the next topic for more information. Use option 1.

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 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to purge. 4 . Number . Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: STation Default: 40 Chapter 4. COMMAND ===> Job: Job Name . Enter END to exit. The Purge Job command removes a specific job from the status display. . From Node . The batch utility to use is CAJUCMD0. 1 . -------------------. . . . The job must be either in completed. Schedule . . The batch command is PURGE JOB. Monitor 4-125 . . . .4.3. Route Sysid . or canceled status. . . Station . .1 Purge Job Command Option 1 of the Purge menu displays the Purge Job dialog.CA-SCHEDULER 9. . . xxyy (SCHD) PURGE JOB ------------------- Execute command at: Route .13. The fields are: Job Name The name of the job to purge.3 Commands 4. . purged. . . . .

Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4-126 Online Guide . Only used in an NJE environment. 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.3 Commands Schedule The schedule of the job to purge. 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.4.

The batch utility to use is CAJUCMD0. The schedule must be in an ended or canceled status.4. . COMMAND ===> Schedule: Schedule Name . . The fields are: Schedule The name of the schedule to be purged. . The batch command is PURGE SCHEDULE. . ----------------. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name From Node The name of the node where the job was submitted. The Purge Schedule command removes a schedule and all of its jobs from the status displays.13. . 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.3 Commands 4. . xxyy (SCHD) PURGE SCHEDULE ----------------- Enter END to exit. Execute command at: Route .3.CA-SCHEDULER 9. . . Only used in an NJE environment.2 Purge Schedule Option 2 of the Purge menu displays the Purge Schedule dialog. Monitor 4-127 . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node Chapter 4. . . . Route Sysid . From Node .

Press Enter to purge all ended and canceled schedules.4.13. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4. The batch utility to use is CAJUCMD0.CA-SCHEDULER 9. The panel has no fields. -------------------. The command has no keywords. along with all jobs belonging to those schedules. 4-128 Online Guide . COMMAND ===> xxyy (SCHD) PURGE ALL ------------------- Press ENTER to purge all ended Schedules.3. The batch command is PURGE ALL. Press PF3 to exit without purging all ended and canceled schedules.3 Purge All Option 3 of the Purge menu displays the Purge All dialog.3 Commands Route Sysid Use Route Sysid to execute the command on a specific CPU at another node in an NJE environment. The Purge All command removes all completed and canceled schedules from the status displays. Completed and canceled jobs in schedules that are still active are not removed. Enter END to exit.

USERALL.4.3.14 Release Commands Use option R1 of the CA-Scheduler Commands menu to display the Release menu. See 4.3.2. to release all jobs held by all users.14. “Release Auto Command” on page 4-134 for more information.14. This only applies if the RHOLD=YES startup option is used. Use option 5. AUTO. Use option 7.3. SUBMIT.CA-SCHEDULER 9.14.5. Use option 1. to release a schedule and all of its jobs. Monitor 4-129 . “Release User Command” on page 4-135 for more information.14. SCHEDULE. to release all jobs held by you.3. “Release Submit Command” on page 4-137 for more information. to release all schedules and jobs. to turn submission back on (reverse the effect of HOLD SUBMIT). --------------------. JOB. “Release All Command” on page 4-133 for more information. Use option 2. See 4. ALL.3. See the next topic for more information. Use option 4. Use option 6. “Release Userall Command” on page 4-136 for more information. See 4.14. to release all schedules and jobs after a restart of the CA-Scheduler started task. USER. The Release commands allow work previously held with the Hold commands to start. 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.3.3 Commands 4.3.3.7. See 4. See 4. “Release Schedule Command” on page 4-132 for more information. Chapter 4. See 4.14.6. Use option 3.4. to release a specific job.

. Number .3. 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. 1 . Enter END to exit. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be released. . .3 Commands 4.1 Release Job Command Option 1 of the Release menu displays the Release Job dialog. . If the job is currently held in JES. ------------------. . From Node . . xxyy (SCHD) RELEASE JOB ------------------ Execute command at: Route . The batch utility to use is CAJUCMD0. . . . . The batch command is RELEASE JOB. Route Sysid .CA-SCHEDULER 9. . . Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 4-130 Online Guide . 4 . . Station . . .4.14. Schedule . it is released. . . . The fields are: Job Name The name of the job to be released. The Release Job command allows a specific job that has been held by the Hold Job command to start. COMMAND ===> Job: Job Name .

Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys Chapter 4. Monitor 4-131 .3 Commands Schedule The schedule of the job to be released. 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. Only used in an NJE environment. 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. 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.4.

The Release Schedule command allows a schedule that was previously held with the Hold Schedule command to start. . . . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode 4-132 Online Guide . ---------------. .3 Commands 4.14. . All held jobs in the schedule are also allowed to start. Route Sysid . . they are released. If any of the jobs are held in JES. This field is only used in an NJE environment. 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. The batch command is RELEASE SCHEDULE. xxyy (SCHD) RELEASE SCHEDULE ---------------- Enter END to exit. COMMAND ===> Schedule: Schedule Name . Execute command at: Route . .4. The fields are: Schedule The name of the schedule to be released. . . .CA-SCHEDULER 9. .3. From Node .2 Release Schedule Command Option 2 of the Release menu displays the Release Schedule dialog. The batch utility to use is CAJUCMD0.

Chapter 4. Any jobs held in JES are released. COMMAND ===> xxyy (SCHD) RELEASE ALL ------------------ Press ENTER to release all Schedules and Jobs.4. 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.3 Release All Command Option 3 of the Release menu displays the Release All dialog. ------------------. The batch utility to use is CAJUCMD0.CA-SCHEDULER 9.3 Commands Route Use Route to execute the command on another node in an NJE environment. The command has no keywords. The batch command is RELEASE ALL. Press PF3 to exit without releasing the workload.3. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4. Monitor 4-133 .14. Press Enter to release the entire workload. The Release All command allows all schedules and jobs held by the Hold commands to start. Enter END to exit. The panel has no fields.

Press PF3 to exit without releasing the entire workload. The command has no keywords. The panel has no fields. -----------------.4. You should not issue the command until after CA-Scheduler issues the message CACM151 (RECOVERY COMPLETED.3.CA-SCHEDULER 9.3 Commands 4. The Release Auto command releases all schedules and jobs held by the RHOLD=YES startup option of CA-Scheduler. Enter END to exit. 4-134 Online Guide . COMMAND ===> xxyy (SCHD) RELEASE AUTO ------------------ Press ENTER to release all Schedules and Jobs held during CA-Scheduler start-up. The batch command is RELEASE AUTO.4 Release Auto Command Option 4 of the Release menu displays the Release Auto dialog.14. 'RELEASE AUTO' MAY BE ISSUED). The batch utility to use is CAJUCMD0. Press Enter to release the entire workload.

4.3 Commands 4. -----------------.CA-SCHEDULER 9. Jobs that are held in JES are released.14. Press Enter to release all schedules and jobs previously held by you. Enter END to exit. Chapter 4. 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. The batch command is RELEASE USER.3. Monitor 4-135 . The batch utility to use is CAJUCMD0. COMMAND ===> xxyy (SCHD) RELEASE USER ------------------ Press ENTER to release all Schedules and Jobs held by you. Press PF3 to exit without releasing anything. The panel has no fields.5 Release User Command Option 5 of the Release menu displays the Release User dialog.

3. 4-136 Online Guide .14. The batch utility to use is CAJUCMD0. Jobs held in JES are released.CA-SCHEDULER 9. ----------------. The command has no keywords. Press Enter to release all schedules and jobs held by CA-Scheduler users.4.6 Release Userall Command Option 6 of the Release menu displays the Release Userall. COMMAND ===> xxyy (SCHD) RELEASE USERALL ---------------- Press ENTER to release all Schedules and Jobs held by any user. The panel has no fields. The batch command is RELEASE USERALL. Enter END to exit. The Release Userall command allows all schedules and jobs previously held by any CA-Scheduler user to start. Press PF3 to exit without releasing anything.3 Commands 4.

The panel has no fields.CA-SCHEDULER 9. Press Enter to resume submission.3. Chapter 4. Monitor 4-137 .7 Release Submit Command Use the RELEASE SUBMIT command to allow jobs to be submitted again.4. COMMAND ===> xxyy (SCHD) RELEASE SUBMIT ----------------- Press ENTER to turn on submission.3 Commands 4. All jobs with a submit fail status of "Submission is held" will automatically be submitted. The batch utility to use is CAJUCMD0. ----------------. All jobs with a status of Submit Fail-submission held will be considered for submission automatically. Enter END to exit.14. Press PF3 to exit without resuming submission. The command has no keywords. The batch command is RELEASE SUBMIT.

to request a schedule. --------------------.CA-SCHEDULER 9. and all of their successors. OPTION ===> 1 2 xxyy (SCHD) REQUEST -------------------- JOB . Use option 2.3 Commands 4.Request a Job and all Successors SCHEDULE .15.Request a Schedule and all Successors Enter END to exit. The Request commands activate work in the current workload that has a criteria of REQUESTED. SCHEDULE.3. 4-138 Online Guide . See 4. JOB. all of its jobs.4. “Request Schedule Command” on page 4-140 for more information. to request a job and its successors. See the next topic for more information.3.15 Request Commands Use option R2 of the CA-Scheduler Commands menu to display the Request menu. Use option 1.2.

Monitor 4-139 . The fields are: Job Name The name of the job to be requested. . . . COMMAND ===> Job: Job Name Number . Station Schedule .CA-SCHEDULER 9. Enter END to exit. .15. . 4 . . The batch command is REQUEST JOB. . .3. .1 Request Job Command Option 1 of the Request menu displays the Request Job dialog. ------------------. . . The batch utility to use is CAJUCMD0. 1 . . xxyy (SCHD) REQUEST JOB ------------------ Execute command at: Route . .4. Route Sysid . The Request Job command activates a job in the current workload that has a criteria of REQUESTED. . . Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 Chapter 4. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be requested. .3 Commands 4. . It also activates all successors of the job. 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. .

along with all successors of the jobs and the schedule. are also activated. 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. The batch command is REQUEST SCHEDULE.3 Commands Schedule The schedule of the job to be requested. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4.15. The batch utility to use is CAJUCMD0. The Request Schedule command activates a schedule in the current workload that has a criteria of REQUESTED.2 Request Schedule Command Option 2 of the Request menu displays the Request Schedule dialog.3. 4-140 Online Guide .4. All of the jobs in the schedule. 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.

. . . . . xxyy (SCHD) REQUEST SCHEDULE ---------------- Enter END to exit.3 Commands ---------------. Execute command at: Route . COMMAND ===> Schedule: Schedule Name . . Route Sysid . . The fields are: Schedule The name of the schedule to be requested. . Monitor 4-141 . 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.4.CA-SCHEDULER 9. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys Chapter 4. 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.

. . . . . . . . “Job Status” on page 4-16). . Restart Step . then the Rerun Job dialog is displayed even if the option Command Prompt from status is set to No. . . ■ The job is found in the CA-11 CMT. . . 4-142 Online Guide . . If the CA-11 Options section is filled in. . . Usage . . Reason for Rerun . . . . . . . The Rerun Job command causes a job that has previously failed to be submitted again. . . RMS Condition Code . . ■ The RERUN command was entered from the job status display (see 4. . . From Node . -------------------.16 Rerun Job Command Option R3 of the CA-Scheduler Commands menu displays the Rerun Job dialog. Execute command at: Route .3. . ■ CA-11 is active. To . Station . xxyy (SCHD) RERUN JOB --------- CA-11 Options: Insert CA-11 RMS . . . . . . . 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. Number .”) The batch utility to use is CAJUCMD0. . . . . Enter END to exit. . restart parameters are used instead of run parameters. . Set CMT to Bypass GDG Pseudo .CA-SCHEDULER 9. .2.4. . 4 . Set last code on step RMS Parm . (See Chapter 3. a starting and/or ending step may be specified. The batch command is RERUN JOB. If the CA-11 interface is installed. .3 Commands 4. 1 . . COMMAND ===> Job: Job Name . . Last Step . Route Sysid . . . . . . If the job has a Library Type of DRIVER. “Options. Schedule . . . . . .

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

Chapter 4. Monitor 4-143

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

Chapter 4. Monitor 4-145

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.

------------------- CA-SCHEDULER 9. COMMAND ===> Job: Job Name Number . Station Schedule . . . . . . . . . . . . . . 1 . 4 .

xxyy (SCHD) RESTAGE JOB ------------------

Execute command at: Route . . . . . Route Sysid . .

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

Chapter 4. Monitor 4-147

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

Chapter 4. Monitor 4-149

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

Chapter 4. Monitor 4-151

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

Chapter 4.Request a Job and some Successors SCHEDULE . See the next topic for more information.CA-SCHEDULER 9. and some of their successors. to activate a specific job and some of its successors.2.3. Use option 1.3 Commands 4. OPTION ===> 1 2 xxyy (SCHD) SREQ ---------------------- JOB .19 SREQ Commands Option S1 of the CA-Scheduler Commands menu displays the SREQ (Selective Request) menu.3. SCHEDULE. See 4. The SREQ commands activate schedules and jobs with a criteria of REQUESTED and SOME of their successors. Use option 2.4. “SREQ Schedule Command” on page 4-156 for more information. Monitor 4-153 .Request a Schedule and some Successors Enter END to exit.19. JOB. ---------------------. its jobs. to activate a schedule.

-------------. . Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: JNo Default: 01 4-154 Online Guide . Route Sysid . . 1 . Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be requested.1 SREQ Job Command Option 1 of the SREQ menu displays the SREQ (Selective Request) Job dialog.19. The batch command is SREQ JOB. Station Schedule . .3 Commands 4. . . Enter END to exit. The batch utility to use is CAJUCMD0. . The fields are: Job Name The name of the job to be requested.4. 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. . COMMAND ===> Job: Job Name Number . xxyy (SCHD) SELECTIVE REQUEST JOB ------------- Execute command at: Route . 4 . . . .CA-SCHEDULER 9.3. . . . . The SREQ Job command activates a job with a criteria of REQUESTED and selected successors of the job. . . . .

3 Commands Station The station of the job to be requested.4. 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. Monitor 4-155 . Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys Chapter 4. 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 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 Schedule The schedule of the job to be requested.

. .4. xxyy (SCHD) SELECTIVE REQUEST SCHEDULE ----------- Enter END to exit. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ROute Default: Current node 4-156 Online Guide . Execute command at: Route . 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. The SREQ Schedule command activates a job with a criteria of REQUESTED and selected successors of the schedule. The batch command is SREQ SCHEDULE. ----------.3.2 SREQ Schedule Command Option 2 of the SREQ menu displays the SREQ (Selective Request) Schedule dialog. The batch utility to use is CAJUCMD0. 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. . . COMMAND ===> Schedule: Schedule Name . . . The fields are: Schedule The name of the schedule to be requested.3 Commands 4. Route Sysid . .CA-SCHEDULER 9. .19.

Monitor 4-157 .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 Chapter 4.

. COMMAND ===> Job: Job Name . . . . From Node Options: CPU Job . Route Sysid . . Station . . . . .CA-SCHEDULER 9. . The fields are: Job Name The name of the job to be started. It is normally used for non-CPU jobs. . Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job to be started.3. . “Options” 4-158 Online Guide . The batch utility to use is CAJUCMD0. . Number . 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.20 Start Job Command Option S2 of the CA-Scheduler Commands menu displays the Start Job dialog. . xxyy (SCHD) START JOB ------------------- 1 . The batch command is START JOB.3 Commands 4. -------------------. . 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. . The Start Job command marks a job as started.4. . . . Enter END to exit. . . NO Execute command at: Route . Schedule . . .

4. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys Chapter 4. Monitor 4-159 . 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. Otherwise. Only used in an NJE environment. this field must be set to NO. 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. 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. 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.3 Commands Schedule The schedule of the job to be started.

. Station . . . 4 . 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. . . . To . . . Route Sysid . Enter END to exit. .”) The batch utility to use is CAJUCMD0. ■ CA-11 is active. “Job Status” on page 4-16). . . . From Node . . . . run parameters are used instead of rerun parameters. . Set CMT to Bypass GDG Pseudo . . . . Restart Step . RMS Condition Code . If the CA-11 Options section is filled in. . a starting and/or ending step may be specified. . . Schedule . . . (See Chapter 3. . . The batch command is SUBMIT JOB. . The Submit Job command causes a job that has previously failed to be submitted again. Set last code on step RMS Parm . xxyy (SCHD) SUBMIT JOB --------- CA-11 Options: Insert CA-11 RMS . . “Options. . . . COMMAND ===> Job: Job Name . Reason for Rerun . . . ■ The SUBMIT command was entered from the job status display (see 4. . 1 . . . . .3. ------------------. .2. Last Step . . If the CA-11 interface is installed. . . Usage .CA-SCHEDULER 9. . 4-160 Online Guide . . . . . If the job has a Library Type of DRIVER. . . Number . Execute command at: Route .3 Commands 4. . ■ The job is found in the CA-11 CMT. . . . the Submit Job dialog displays even if the option Command Prompt from Status is set to No. .4. .21 Submit Job Command Option S3 of the CA-Scheduler Commands menu displays the Submit Job dialog. .

Monitor 4-161 .3 Commands The fields are: Job Name The name of the job to be submitted. 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 Chapter 4.4. 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 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. CA-Scheduler inserts the CA-11 Run Manager Step (RMS) into the job's JCL during submission. Only used in an NJE environment. 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 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 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Insert CA-11 RMS If YES.

Size/Type: YES or NO Required: No Batch Keyword: BYPgdg Default: NO Last Step The last step of the job that should execute. if the CA-11 AUTOS option is set to YES Bypass GDG If YES. 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. where stepname has the EXEC PGM= on it. The format is "stepname" or "procstep. Size/Type: 1 to 17 alphanumeric characters Required: No Batch Keyword: LAStstep Default: Last step of the job Pseudo If YES. Size/Type: 1 to 17 alphanumeric characters Required: No Batch Keyword: REStstep Default: The step set in the CMT for restart. where stepname has the EXEC PGM= on it.stepname". certain CA-11 restrictions on changing JCL are relaxed. Size/Type: 1 to 4 numeric characters from 0-4095 Required: No Batch Keyword: RMSCc Default: 0 (zero) 4-162 Online Guide . CA-11 does not perform any processing other than reporting.3 Commands Set CMT to Indicates if the CA-11 Catalog Management Table (CMT) for this job should be set to PRODUCTION or RESTART. See the CA-11 documentation for more information.stepname". The format is "stepname" or "procstep. 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.4. This option is useful when first implementing CA-11.

Usage may be required by your CA-11 installation options. Either both must be specified or both blank Batch Keyword: LRTCDSTP and LRTCDCOD RMS Parm The parm field for the RMS. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys Chapter 4.4. CA-11 dictates the syntax. Size/Type: 1 to 17 alphanumeric characters (stepname or procstep. 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. Monitor 4-163 . It may be required by your CA-11 installation options. 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. If entered.3 Commands Usage A code that may be used by CA-11 to validate your restart request. any values entered for the other CA-11 options are ignored. 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. except for the Reason for Rerun field. 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.stepname) and 1-4 numeric characters Required: No.

22 Unpost Commands Option U1 of the CA-Scheduler Commands menu displays the Unpost menu. “Unpost Dataset Command” on page 4-175 for more information. “Unpost Schedule Command” on page 4-168 for more information. See 4. to unsatisfy a predecessor of a schedule starting. 4-164 Online Guide . STEP. to unsatisfy a predecessor of a CA-Scheduler job starting.4.6. See the next topic for more information. to unsatisfy a predecessor of a CA-Scheduler job completing. Use option 6. See 4. “Unpost Job Start Command” on page 4-170 for more information. step. 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. See 4.22. or data set. Use option 3. Use option 5. “Unpost Schedule Start Command” on page 4-173 for more information.22.5.3.3.22. --------------------.CA-SCHEDULER 9.7. JOB.3. Use option 1. even if the predecessor has already completed. The Unpost commands cause successors to wait on a predecessor job. MVS. See 4.3. See 4. DATASET. Use option 7.3. to unsatisfy a data set predecessor. schedule.22.3 Commands 4.2.3.4.22. Use option 4. “Unpost Unscheduled Job” on page 4-177 for more information. to unsatisfy a predecessor of a schedule completing. SSCHD.3. to unsatisfy a predecessor of a specific step within a CA-Scheduler job. to unsatisfy a predecessor of a non-CA-Scheduler job completing.3. “Unpost Job Step Command” on page 4-179 for more information. See 4. Use option 2.22. SCHEDULE. SJOB.

. Successor: . . . The batch utility to use is CAJUCMD0. Execute command at: Route . . Station . Route Sysid . . Enter END to exit. The batch command is UNPOST JOB. . . The predecessor conditions are created by criteria of the form: ┌─. . From Node . Schedule . . . . . . .1 Unpost Job Command Option 1 of the CA-Scheduler Unpost Menu displays the Unpost Job dialog. a specific successor job may have its predecessor unsatisfied instead of all successors. . . . Monitor 4-165 . . .4. ------------------. . . Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Chapter 4. 1 . . . The fields are: Job Name The job name whose successors are notified that the job has completed normally. Schedule . xxyy (SCHD) UNPOST JOB ------------------- Unpost only this Job Name . . Station . . 4 . .CA-SCHEDULER 9. .3 Commands 4. Number . The Unpost Job command unsatisfies predecessor conditions for jobs and schedules waiting on a specific CA-Scheduler job to successfully complete. . COMMAND ===> Job: Job Name .1──┐ ┌─4 ──────┐ ──jobname──┼──────┼──┼─────────┼──┬──────────┬──────────────── └─-jno─┘ └─station─┘ └─schedule─┘ Optionally. .22. .3. Number .

By entering a job name.3 Commands Number The number of the job whose successors are notified that the job has completed normally. 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 . leaving all others to continue waiting. 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. By leaving the fields under Unpost only this Successor blank. all successors may start. only that successor may start. 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. 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. you may allow all successors or identify a specific job that may start.4.

Monitor 4-167 .4. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys Chapter 4. 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.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.

. . .3 Commands 4. . . .22. . xxyy (SCHD) UNPOST SCHEDULE ---------------- Execute command at: Route . . . The predecessor conditions are created by criteria of the form: ──SCD──schedule─────────────────────────────────────────────── Optionally. ----------------. . . . . . a specific successor job may have its predecessor unsatisfied instead of all successors. . . . . .2 Unpost Schedule Command Option 2 of the CA-Scheduler Unpost Menu displays the Unpost Schedule dialog. Unpost only Job Name Number . The Unpost Schedule command unsatisfies predecessor conditions for jobs and schedules waiting on a specific schedule to end. . . .CA-SCHEDULER 9. From Node . 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 . The batch command is UNPOST SCD. Station . .4. Schedule The schedule whose successors are notified that it has completed normally. Enter END to exit. . . Schedule this Successor: .3. . The batch utility to use is CAJUCMD0. COMMAND ===> Schedule: Schedule Name . Route Sysid .

4. you may allow all successors or identify a specific job that may start. leaving all others to continue waiting. 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. By entering a job name. Monitor 4-169 . By leaving the fields under Unpost only this Successor blank. all successors may start. 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 Chapter 4.3 Commands Unpost only this Successor In allowing successors to start. only that successor may start.

. . . Enter END to exit. 1 . . The fields are: Job Name The job name whose successors are notified that the job has started. . xxyy (SCHD) UNPOST JOB START ---------------- Unpost only this Job Name . Execute command at: Route . . Number .1──┐ ┌─4 ──────┐ ──START──jobname──┼──────┼──┼─────────┼──┬──────────┬───────── └─-jno─┘ └─station─┘ └─schedule─┘ Optionally. . Station . From Node . . The predecessor conditions are created by criteria of the form: ┌─. .4. . . . . . 4 . . . The Unpost Job start command unsatisfies predecessor conditions for jobs and schedules waiting on a specific CA-Scheduler job to start. .22. ---------------. . The batch utility to use is CAJUCMD0. . . . . COMMAND ===> Job: Job Name . Successor: .3. Schedule . The batch command is UNPOST SJOB.3 Commands 4. . . . . . Route Sysid . . Station . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Name 4-170 Online Guide . Number .CA-SCHEDULER 9. . Schedule .3 Unpost Job Start Command Option 3 of the CA-Scheduler Unpost Menu displays the Unpost Job Start dialog. . a specific successor job may have its predecessor unsatisfied instead of all successors.

you may allow all successors or identify a specific job that may start. only that successor may start. 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 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. By leaving the fields under Unpost only this Successor blank.3 Commands Number The number of the job whose successors are notified that the job has started. By entering a job name. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Unpost only this Successor In allowing successors to start. leaving all others to continue waiting.4. 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. 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 Chapter 4. all successors may start. Monitor 4-171 .

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 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4-172 Online Guide .4. 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.

. . . The Unpost Schedule start command unsatisfies predecessor conditions for jobs and schedules waiting on a specific schedule to start. xxyy (SCHD) UNPOST SCHEDULE START ------------- Execute command at: Route . .22. 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. Enter END to exit.4. . . . . .3 Commands 4. . . . . . From Node . . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Chapter 4. Monitor 4-173 . The batch utility to use is CAJUCMD0. .CA-SCHEDULER 9. . . Station . . The fields are: Schedule The schedule whose successors are notified that it has started. Schedule this Successor: . -------------. Unpost only Job Name Number . . The batch command is UNPOST SSCD. . . COMMAND ===> Schedule: Schedule Name . .3. .4 Unpost Schedule Start Command Option 4 of the CA-Scheduler Unpost Menu displays the Unpost Schedule Start dialog. . . Route Sysid . a specific successor job may have its predecessor unsatisfied instead of all successors. The predecessor conditions are created by criteria of the form: ──START SCD──schedule───────────────────────────────────────── Optionally.

By leaving the fields under Unpost only this Successor blank. only that successor may start. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4-174 Online Guide .3 Commands Unpost only this Successor In allowing successors to 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. leaving all others to continue waiting. 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. all successors may start. you may allow all successors or identify a specific job that may start. By entering a job name.4.

5 Unpost Dataset Command Option 5 of the CA-Scheduler Unpost Menu displays the Unpost Dataset dialog. Chapter 4. Number . The batch command is UNPOST DSN. Monitor 4-175 . The fields are: Dataset The data set name whose successors are notified that it has been updated. By entering a job name. Schedule . .22. Successor: .4. . . .3. xxyy (SCHD) UNPOST DATASET ----------------- Execute command at: Route . . you may allow all successors or identify a specific job that may start. ----------------. only that successor may start.3 Commands 4. all successors may start. . . By leaving the fields under Unpost only this Successor blank.CA-SCHEDULER 9. Station . leaving all others to continue waiting. Unpost only this Job Name . Size/Type: 1 to 44 alphanumeric characters Required: Yes Batch Keyword: Name Unpost only this Successor In allowing successors to start. . Route Sysid . . COMMAND ===> Dataset: Dataset Name . . . . 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 Unpost Dataset command unsatisfies predecessor conditions for jobs and schedules waiting on a data set to be updated. Enter END to exit. .

Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4-176 Online Guide .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.4. 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.

xxyy (SCHD) UNPOST $MVS ------------------ Execute command at: Route . Station .3 Commands 4. The batch command is UNPOST MVS. Monitor 4-177 . . only that successor may start. . . . By leaving the fields under Unpost only this Successor blank. Number . . Job Name The job name whose successors are notified that the job has started. By entering a job name. Enter END to exit. Schedule .22. . .6 Unpost Unscheduled Job Option 6 of the CA-Scheduler Unpost menu displays the Unpost MVS dialog. ------------------. . The predecessor conditions are created by criteria of the form: ──MVS jobname───────────────────────────────────────────────── Optionally. Route Sysid .4.CA-SCHEDULER 9. . . a specific successor job may have its predecessor unsatisfied instead of all successors. Chapter 4. . Unpost only this Job Name . leaving all others to continue waiting. all successors may start. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Name Unpost only this Successor In allowing successors to start. The batch utility to use is CAJUCMD0. Successor: . . .3. you may allow all successors or identify a specific job that may start. . . . The Unpost MVS command unsatisfies predecessor conditions for jobs and schedules waiting on a non-CA-Scheduler job to successfully complete. COMMAND ===> Unscheduled Job: Job Name . . . . .

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.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.4. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4-178 Online Guide .

COMMAND ===> Job: Job Name . . .22. . Route Sysid . . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Name Chapter 4.4. Schedule . . a specific successor job may have its predecessor unsatisfied instead of all successors. . . . . . . The batch command is UNPOST STEP. . Station .3 Commands 4. Enter END to exit. The fields are: Job Name The job name with the step whose successors are notified that the job has completed normally. 4 . .7 Unpost Job Step Command Option 7 of the CA-Scheduler Unpost Menu displays the Unpost Job Step dialog.CA-SCHEDULER 9. . . 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. 99999) Unpost only this Job Name .stepname──────────────────────────── └─. . . From Node . . Station . 1 . Successor: .CC.3. .1──┐ ┌─4 ──────┐ ──┬─────────────────────────┬──┼──────┼──┼─────────┼──────────── └─. . . . . ( -4 95. . . ----------------. Proc Step Fail Oper Number . . Schedule . Execute command at: Route . .──failoper. . . Fail Code . The predecessor conditions are created by criteria of the form: ──jobname──┬───────────┬──.procstep─┘ ┌─. The batch utility to use is CAJUCMD0. . . Number . . . Monitor 4-179 .failcode─┘ └─-jno─┘ └─station─┘ ──┬──────────┬───────────────────────────────────────────────── └─schedule─┘ Optionally. . . xxyy (SCHD) UNPOST JOB STEP ---------------- Step Name . . . .

then all successors of this step. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: STation Default: 40 4-180 Online Guide . GE (Greater than or Equal). Valid values are blank. GT (Greater Than). regardless of their criteria's Fail Oper and Fail Code values.4. 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. If 99999 is entered. are notified. NE (Not 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.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: Yes Batch Keyword: STEP Fail Oper A Boolean operator that must match the value in the successor schedule's or job's criteria. 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. LT (Less Than). and LE (Less than or Equal). EQ (EQual). 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.

By entering a job name.3 Commands Schedule The schedule of the job with the step whose successors are notified that the job has completed normally. 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 Chapter 4. Monitor 4-181 . leaving all others to continue waiting. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FMnode Default: Current node Unpost only this Successor In allowing successors to start. 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. By leaving the fields under Unpost only this Successor blank. you may allow all successors or identify a specific job that may start. all successors may start.4.

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.4. Size/Type: 1 to 4 alphanumeric characters Required: No Batch Keyword: ROUTSys 4-182 Online Guide .3 Commands Route Use Route to execute the command on another node in an NJE environment.

Chapter 4. Use option 2.23.2.End a CA-Scheduler NJE Session VRM .3.3.3. See 4.23. Use option 1. to start a VTAM session.CA-SCHEDULER 9. OPTION ===> 1 2 3 xxyy (SCHD) VARY ---------------------- ACTIVE . The Vary VRM command is used to change the state of a virtual resource.Make a virtual resource active or inactive Enter END to exit. Use option 3. See the next topic for more information. Monitor 4-183 .3 Commands 4. “Vary Inactive Command” on page 4-185 for more information. ---------------------. VRM.Start a CA-Scheduler NJE Session INACTIVE . See 4. The Vary Active and Vary Inactive commands start and stop VTAM sessions between CA-Scheduler started tasks. to make a TYPE=SIMPLE virtual resource active or inactive.4. ACTIVE.23 Vary Commands Option V1 of the CA-Scheduler Commands menu displays the Vary menu. INACTIVE.3. “Vary VRM Command” on page 4-186 for more information. to stop a VTAM session. These sessions are only used for NJE.

3. The batch utility is CAJUCMD0. The fields are: ID The name of the VTAM session to be started. The batch command is VARY ACT. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ID Default: All sessions 4-184 Online Guide . If ID is left blank. . .4. ------------------. COMMAND ===> Node: ID .23. xxyy (SCHD) VARY ACTIVE ------------------ (Leave blank to start all sessions) Enter END to exit.CA-SCHEDULER 9.3 Commands 4.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. all sessions not currently active are started.

Size/Type: YES or NO Required: No Batch Keyword: CLOSE Default: NO Chapter 4. The batch command is VARY INACT. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: ID Default: All sessions Close If YES. The batch utility is CAJUCMD0. Options: Close . xxyy (SCHD) VARY INACTIVE ----------------- (Leave blank to end all sessions) Enter END to exit.CA-SCHEDULER 9.2 Vary Inactive Command Option 2 of the Vary menu displays the Vary Inactive dialog. -----------------.23. COMMAND ===> Node: ID . .3. . all sessions are stopped.4. The Vary Inactive command stops a VTAM session for NJE. Monitor 4-185 . If ID is left blank. . The fields are: ID The name of the VTAM session to be stopped. the local VTAM ACB is closed.3 Commands 4.

The Vary VRM command makes a virtual resource ACTIVE or INACTIVE. . Size/Type: ACTIVE or INACTIVE Required: Yes Batch Keyword: Status 4-186 Online Guide . 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. The virtual resource must be defined as TYPE=SIMPLE. -------------------.3 Commands 4.CA-SCHEDULER 9. xxyy (SCHD) VARY VRM -------------------- (Resource name) (Active or Inactive) Enter END to exit.4.23.3. . . . The fields are: Name The name of the virtual resource being made active or inactive. The resource must be defined as TYPE=SIMPLE. Status .3 Vary VRM Command Option 3 of the Vary menu displays the Vary VRM dialog. COMMAND ===> Resource: Name .

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 Chapter 4.4 FREECMD Option 4 of the CA-Scheduler Monitor menu displays the Freeform Command dialog.CA-SCHEDULER 9.4 FREECMD 4. COMMAND ===> Enter CA-Scheduler command or number ===> xxyy (SCHD) COMMANDS --------------------9: : 1: 2: 3: 4: 5: 6: 7: 8: 9: Enter END to exit.4. -------------------. Monitor 4-187 .

You may retrieve the commands by typing the number of the field in the command prompt. 4-188 Online Guide .4. You may use all browse functions. The output of the command is browsed using the ISPF/PDF Browse facility.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.

Schedules are sometimes called job sets. See 5.2. Schedules are collections of jobs that are in some way related. Database 5-1 . 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. Jobs are specific tasks that CA-Scheduler tracks. to display and maintain user ID definitions. Jobs may be JCL submitted to the operating system. “Schedules” on page 5-3 for more information.1. to display and maintain jobs. the schedule must be in that day's workload. USER IDS. Chapter 5. to display and maintain schedules. -------------------. tasks processed by a Unicenter TNG on a non-OS/390 platform. Before a job can be considered to be a part of a given day's workload. Type the appropriate option number and press Enter. JOBS.Chapter 5. Database Option 2 of the CA-Scheduler main menu displays the database menu. “Jobs” on page 5-26 for more information. or manual tasks required either before or after a CPU job. Use option 3. Every job must belong to a schedule.CA-SCHEDULER 9. See 5. Use option 1. SCHEDULES. Use option 2.

See 5. Multiple periods may be defined. “Stations” on page 5-73 for more information. to display and maintain calendar definitions. Resources describe the data center and may contain the number of tape drives and job initiators. Station 40 is the CPU station. See 5. See 5. See 5. See 5. Date tables define which days are considered workdays against nonworkdays (nonworkdays and holidays are considered the same). Use option 8. A minimum of three date tables are required: one for the year just past. Stations only need to be defined for simulation and forecast reports. Stations are two-digit numbers. Use option 4. to display and maintain virtual resource information. called accounting periods. to display and maintain flows. Use option 7. Stations less than 40 are called pre-CPU. See 5.User IDs are people defined to CA-Scheduler at a certain authorization level. FLOWS. the current year.7. and the next year. to display and maintain station definitions. “Virtual Resources” on page 5-115 for more information.4. RESOURCES. Date tables are much more powerful and flexible and should be used instead of calendars whenever possible. to display and maintain documentation. depending on the CAIJGEN installation option SECURTY.9. “Flows” on page 5-110 for more information. 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. to display and maintain date table definitions. Virtual resources can be used to restrict when jobs may be submitted. “Datetables” on page 5-100 for more information. Use option A.6. VRM. Documentation is text entered by your site that may or may not be associated with a job. and stations after 40 are post-CPU.3. “Calendars” on page 5-93 for more information. Use option 9. DATETABLE.10. DOCUMENTATION. See 5. User IDs may or may not be required. “Resources” on page 5-78 for more information.8. Date tables also define when processing periods (months) begin and end. to display and maintain resource definitions. “User IDs” on page 5-66 for more information. if not on the first and last day of the month. Resources only need to be defined for simulation and forecast reports. “Documentation” on page 5-106 for more information. 5-2 Online Guide . Use option 5. A Station is a place where work is done. CALENDARS. Use option 6.5. STATION. from 01 to 99. See 5. A flow identifies the starting and ending job of a job stream to be tracked by the Critical Path Monitor (CPM) system.

Use option 5. You must enter the schedule to define in the Schedule field. You must enter the schedule to copy in the Schedule field. A schedule must be included in a given day's workload before any of the jobs in the schedule are considered for that day. to remove a specific schedule. to view a specific schedule. OPTION ===> Schedule . DIRECTORY. If you have requested the Delete Confirmation option (see Chapter 3. “Analyze” on page 6-3 for more information. DEFINE. -------------------. Database 5-3 . Use option 7. Use option 4.5. to review the schedule and its jobs for any logical errors. You must enter the schedule to alter in the Schedule field. Delete. to edit a specific schedule. Otherwise. or leave the field blank to list all schedules.CA-SCHEDULER 9. You may put a partial schedule name in the Schedule field to limit the display. See 6. and Copy schedules. From the list you may Select (display).1. 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 6. Use option 2.1 Schedules 5. to copy a schedule. to create a new schedule. You must enter the schedule to delete in the Schedule field. . Edit. to display a scrollable list of schedules. ALTER. DELETE. ANALYZE. Chapter 5. Use option 3. You must enter the schedule to display in the Schedule field. “Options”) then a panel is displayed asking you to confirm the deletion. DISPLAY. COPY. Use option 1. the schedule is deleted immediately.1 Schedules Every job in CA-Scheduler must belong to a schedule (sometimes called a job set).

CA-Scheduler only reads the first 50 schedules before displaying the list. the user ID field may be blank. Schedules that were last updated prior to Version 9.0 show blank date and time.0 or higher.1. 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. As you scroll down. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. If the schedule was defined and modified only in batch prior to Version 7. then the date and time of that change is displayed.1 Directory -------------------. If the schedule has been defined or modified in Version 9.1 Schedules 5.CA-SCHEDULER 9. 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 . more rows are automatically added until the entire list has been built.4.5. Select a schedule by entering a letter to the left of the schedule.

DEFINITION. to view or edit the schedule definition.2.2 Schedule Options The same panels are used to display. 1 2 xxyy (SCHD) SCHEDULE -------------------- DEFINITION .CA-SCHEDULER 9. “Schedule Criteria” on page 5-24 for more information.Schedule Selection and Predecessors Enter END to exit. -------------------. and define schedules. Use option 1.2. See the next topic for more information. .1 Schedules 5. CRITERIA.5.1. OPTION ===> Schedule . edit. to edit or browse the schedule's criteria.Schedule Definition CRITERIA . See 5. .1. Use option 2. Chapter 5. Database 5-5 .

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. . . . Use PF7 and PF8 to scroll up and down through the panels. . . . use PF3. Job Defaults: Library Type . Ins Sched Enviro . . . . . . . . . Stage JCL .1 Schedules 5.2.5. . . YES Execution: Execution Node . xxyy (SCHD) SCHEDULE BASE ----------------- Skip . -----------------. . The batch command object for this panel is SBR. . or DOWN for Next Screen. . . . Date Table . Enter END to Exit. . . NO Backlog . To save your changes and exit. enter CAN on the command line. Scheduling: Auto Selection . To exit without saving your changes. . COMMAND ===> Name . . . JES Priority Sched Enviro . . A .CA-SCHEDULER 9.1 Schedule Definition The schedule definition information is contained on several panels. . The batch utility to use for maintaining schedules is CAJUTIL0. JES Class .1. . . 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 . . . . Execution Sysid . . Insert CA-11 . JCL DDname . .

This field may not be modified. Skip is used only if Auto Selection is set to Yes. A default date table is defined in CAIJGEN. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Auto Selection Determines if the schedule. Required: Yes Batch Keyword: Backlog Default: YES Date Table The name of an alternate date table to use in resolving the schedule's criteria. YES Allows the old schedule to complete before the new schedule is brought in. and the new schedule is brought in. and the schedule should be in the next day's workload. This date table is also used to resolve all of the criteria for this schedule's jobs. Size/Type: 1 to 7 alphanumeric characters Required: No Batch Keyword: DAtetabl Default: The value in CAIJGEN DATETAB Chapter 5.5. 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. 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. and all of its jobs. should be considered during autoscan for inclusion in the current day's workload. NO Causes the remaining jobs in the schedule to be canceled.1 Schedules The fields are: Name The name of the schedule being manipulated. Database 5-7 .

Individual jobs may override this default.5. See "Performance Considerations" in the Systems Programmer Guide for performance implications. 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. this is the default JES node where the jobs in this schedule will execute. 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. 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. Valid values are: DRIVER CA-Scheduler generates one line of JCL for Driver to expand. CA-Scheduler releases the job and tracks it as if the job was submitted by CA-Scheduler. If left blank. 5-8 Online Guide . 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. 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.1 Schedules Execution Node In a JES NJE environment. Individual jobs in this schedule may override this default. the default is the local JES node. 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. A default access method is specified on the CAIJGEN option LIBTYPE.

Individual jobs may override this value. Database 5-9 . See "User Exits and APIs" in the Systems Programmer Guide for more information. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: DDname Default: JCLMASTR Insert CA-11 If Yes. Note: This value is used only for simulation. based on parameters defined at the job level. Size/Type: 1 alphanumeric character Required: No Batch Keyword: Class Default: A Chapter 5. See the field Test Parm on page 5-38. TESTLIB CA-Scheduler submits a dummy job (based on the skeleton in member CAJUTSTB of the PDS allocated to ddname JCLMASTR). 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. the default ddname of the partitioned data set containing the JCL of the jobs in this schedule.5. end with a specific return code. Note: This option is ignored if the CAIJGEN option CA11 is set to NO. all of the CPU jobs in this schedule are submitted with the CA-11 RMS step inserted. The dummy job may execute for a specified number of seconds. Individual jobs may override this value. or abend. ROSCOE CA-Roscoe Required: No Batch Keyword: Libtype Default: Value on CAIJGEN LIBTYPE JCL DDname For Library Type of PDS. Individual jobs may override this value.1 Schedules USERLIB The access method is provided by a site-written exit program.

Note: This value is used only for simulation.to 16-alphanumeric characters Required: No Batch Keyword: SCHENV Default: Blank (use global option) Press PF8 for the next panel. If the Scheduling Environment is blank. the JCL is read from the active workload. 5-10 Online Guide . or from the global options if blank. Size/Type: 1. The scheduling environment to be inserted into the JCL is taken from the Scheduling Environment field below. When the jobs are submitted to JES. 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. NO. and may be overridden on the job definition. Size/Type: YES. Note: This value is ignored if CAIJGEN option STAGE is set to NO. The value is only inserted if the Insert Sched Enviro field above is YES (or defaults to YES). the insert option is taken from the global options (CAS9 CAIJGEN). 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.5. Individual jobs may override this value.1 Schedules Stage JCL If YES. Individual jobs may override this value. the global option (CAS9 CAIJGEN) value is used. CPU jobs in this schedule have their JCL written to the CA-Scheduler active workload when the schedule starts. 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. This allows operators to modify the JCL prior to the job being submitted.

Note: This is the earliest that the schedule may start. 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) Chapter 5. . . Database 5-11 . the schedule may start after this time. . . . . where dd is the number of autoscans that the schedule should wait. Userids . and hhmm is the time to start. The value is in the format of ddhhmm. . . . . . If it has predecessors that are still unresolved. . Maximum Execution Average Time . . Must End .1 Schedules -----------------.CA-SCHEDULER 9. . . . NO Schedule Priority . . . . . . .5. . . . Use Simulation Time . COMMAND ===> Name . . . . . but may not start before the schedule starts. . You do not need to enter leading zeros. xxyy (SCHD) SCHEDULE BASE ----------------- Other: Continue on bad jobs . . . . . Times: Early Start . . . Must Start . UP for Previous Screen. . . . . . Individual jobs may have a later early start time. Enter END to Exit. . . or DOWN for Next Screen. 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. . . . NO Internal Security: Userids . .

and/or a user. where dd is the number of autoscans that the schedule should wait. the MAILBOX report. the MAILBOX report. The value is in the format of ddhhmm. it is considered late. where dd is the number of autoscans that the schedule should wait. The value is in the format of ddhhmm. 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). You do not need to enter leading zeros. and hhmm is the time to start. You do not need to enter leading zeros. The value is in the format of ddhhmm. where dd is the number of autoscans that the schedule should wait. A message may be sent to the console. The value is in the format of ddhhmm. and/or a user.1 Schedules | | Must Start If the schedule has not started by this time. then it is considered late. You do not need to enter leading zeros. and hhmm is the time to start. and hhmm is the time to start. This value is used only in simulation if the schedule has never been executed. 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. 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.5. You do not need to enter leading zeros. where dd is the number of autoscans that the schedule should wait. A message may be sent to the console. the MAILBOX report. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: AVgtime Default: 0 | | 5-12 Online Guide . and hhmm is the time to start. and/or a user.

that controls the order of internal control blocks. 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 job failed and has FAILED=CONT 4. is to be used. Size/Type: 1 to 8 alphanumeric character user ID may be specified from zero to eight times Required: No Batch Keyword: Userids=(value. from the CAIJGEN SPRTY value. then access is allowed. If entered.) Press PF8 for the next panel.the value on CAIJGEN option SPRTY Use Simulation Time If YES. A value of zero indicates that the default schedule priority. 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. Size/Type: NO or YES Required: No Batch Keyword: USESim Default: NO Userids Used by CA-Scheduler internal security. If this field is YES..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. CA-Scheduler searches these control blocks to find work. Size/Type: 1 to 2 numeric characters from 1 to 99 Required: No Batch Keyword: SPrty Default: 0 .value. If the list is blank. A zero value is displayed on batch reports as blanks. Chapter 5. where 01 is the higher priority. The COMPLETE command was issued for the job 3. and a user of type general or supervisor accesses this schedule. Database 5-13 . or the user is type manager. then the user's ID must be in the list. the start time as calculated by simulation overrides the early start time entered above.

CA-SCHEDULER 9. Group id . . . External Security: User id . The value JSI corresponds to this field.5. UP for Previous Screen. The CAIJGEN option SECURTY must be set to YES. . 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.1 Schedules ---------------. . and the CAIJ$SEC option for the specific library type (access method) must be YES before a user ID is inserted into the JCL. 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. . COMMAND ===> Name . The CAIJGEN option SECURTY must be set to YES. The batch command object for this panel is SSI. or DOWN for Next Screen. Note: The group ID in the submitted job is determined by the order of the CAIJGEN option SUBUID. Note: The user ID in the submitted job is determined by the order of the CAIJGEN option SUBUID. 5-14 Online Guide . Individual jobs may override this value. The value JSI corresponds to this field. and the CAIJ$SEC option for the specific library type (access method) must be YES before a groupid is inserted into the JCL. xxyy (SCHD) SCHEDULE SECURITY --------------- Enter END to Exit. Individual jobs may override this value.

. . Enter END to Exit. . . . . Schedule End . . . and ends.) Chapter 5. . . becomes late. . . . . . Schedule Start . . . .. . . . ---------------. . Schedule Skipped . . 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. Schedule Late . See below for more information. . . . . . xxyy (SCHD) SCHEDULE MESSAGES --------------- . . . .. . or DOWN for Next Screen. COMMAND ===> Name . . . . Size/Type: 1 to 8 alphanumeric character value specified from zero to four times Required: No Batch Keyword: Msg=(value. UP for Previous Screen. . .1 Schedules Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Groupid Press PF8 for the next panel. . . . . . . .5. . . . . . The batch command object for this panel is SMR. .CA-SCHEDULER 9. . .value. . . . . Userid to Notify for: All Events . . . Database 5-15 .

) 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. 5-16 Online Guide . See below for more information.. A value of OPERxxyy sends a WTO to the OS/390 console. Size/Type: 1 to 8 alphanumeric character value specified from zero to four times Required: No Batch Keyword: SKIPmsg=(value. The CAIJGEN options STRMSG. Consult your site's systems programmer for a list of appropriate route codes and descriptor codes for your site.) Schedule End A list of zero to four user IDs or OPERxxyy values to which messages should be sent when the schedule ends.) 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. See below for more information.value.. They are stored in the CA-Scheduler active workload and must be retrieved manually by the user.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. The xx is the route code. Size/Type: 1 to 8 alphanumeric character value specified from zero to four times Required: No Batch Keyword: Startmsg=(value.5. and SKPMSG specify locations to which all start.. Size/Type: 1 to 8 alphanumeric character value specified from zero to four times Required: No Batch Keyword: Latemsg=(value. and late messages should be sent. Normally these include MAILBOX. Size/Type: 1 to 8 alphanumeric character value specified from zero to four times Required: No Batch Keyword: Endmsg=(value. Messages are not kept indefinitely--see the CAIJGEN option MSGHOLD for more information... and the yy is the descriptor code. See below for more information. LATMSG. | Messages are stored in the database when the value is MAILBOX. end.. All messages are sent both to the CAIJGEN locations and to the locations entered here. ENDMSG.value.value... Press PF8 for the next panel.value. and may be retrieved by the REPORT MAILBOX command.) Messages to users are not TSO SEND messages.

Reasons 01 to 16 Allows an override of the user-specified average time based on the selection reason code. Average Times: Reasons 1 to 4 . . . . . . . . . . . . . . . . . . . . . . . . where dd is the number of autoscans and hhmm is hours and minutes. . . . . . Reasons 01 to 16 Allows an override of the early start time entered earlier based on the selection reason code. .1 Schedules -------------. Reasons 5 to 8 . Database 5-17 . . . . . xxyy (SCHD) SCHEDULE REASON CODES ------------- . where dd is the number of autoscans and hhmm is hours and minutes. . . . . See below for more information. . . .CA-SCHEDULER 9. . .5. 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 Chapter 5. . . . 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. . . 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 9 to 12 . . . . The value is specified as ddhhmm. . . COMMAND ===> Name . . . Reasons 13 to 16 . . . Enter END to Exit. . . . See below for more information. . . . . . . . . Early Start Times: Reasons 1 to 4 Reasons 5 to 8 Reasons 9 to 12 Reasons 13 to 16 . . . . . . . . UP for Previous Screen. . . . or DOWN for Next Screen. . The value is specified as ddhhmm. . . . The batch command object for this panel is SRC.

The batch command object for this panel is SRC. . Press PF8 for the next panel. An "OR" outside of parentheses changes the selection reason code.1 Schedules The selection reason code reflects what part of the schedule's criteria was used to justify its inclusion in the workload. If the criteria was: (MON OR TUE) then the selection reason code would be 01 on both days. . UP for Previous Screen. . . . . . . . . . . . . . Reasons 9 to 12 . . Enter END to Exit. if the criteria reads: MON OR TUE then the selection reason code on Monday would be 01 and on Tuesday would be 02. . . . . . . . . . . . . . . Reasons 13 to 16 . . . . . . . . . . . . . . . . . . . or DOWN for Next Screen. . . . . . . . . . . . . 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 . . . Must End Times: Reasons 1 to 4 . -------------. . . . . . . . . . .CA-SCHEDULER 9. . xxyy (SCHD) SCHEDULE REASON CODES ------------- . . For example. . COMMAND ===> Name . . . . . Reasons 5 to 8 . . A Must Start Times: Reasons 1 to 4 Reasons 5 to 8 Reasons 9 to 12 Reasons 13 to 16 .5. . . . .

if the criteria reads: MON OR TUE then the selection reason code on Monday would be 01 and on Tuesday would be 02. See below for more information. Database 5-19 .1 Schedules The fields are: Must Start Times. See below for more information. The value is specified as ddhhmm. If the criteria was: (MON OR TUE) then the selection reason code would be 01 on both days. 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. An "OR" outside of parentheses changes the selection reason code.5. Chapter 5. Reasons 01 to 16 Allows an override of the must complete time entered earlier based on the selection reason code. 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. Press PF8 for the next panel. where dd is the number of autoscans and hhmm is hours and minutes. The value is specified as ddhhmm. Reasons 01 to 16 Allows an override of the must start time entered earlier based on the selection reason code.

.CA-SCHEDULER 9. . Reasons 9 to 12 . . . . . . .1 Schedules -------------. The batch command object for this panel is SRC. . . Press PF8 for the next panel. . . if the criteria reads: MON OR TUE then the selection reason code on Monday would be 01 and on Tuesday would be 02. . xxyy (SCHD) SCHEDULE REASON CODES ------------- . . Reasons 13 to 16 . . 5-20 Online Guide . . Enter END to Exit. . . 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. . . Reasons 01 to 16 Allows an override of the maximum execution time entered earlier based on the selection reason code. . . . COMMAND ===> Name . 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. . . . An "OR" outside of parentheses changes the selection reason code. . . . . . . . or DOWN for Next Screen. UP for Previous Screen. . . The value is specified as ddhhmm. . See below for more information. where dd is the number of autoscans and hhmm is hours and minutes. . . . If the criteria was: (MON OR TUE) then the selection reason code would be 01 on both days. Reasons 5 to 8 . For example. . .5. A Maximum Execution Times: Reasons 1 to 4 .

COMMAND ===> Name . . . . The fields are: Description A description of this job. . . . 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. . Database 5-21 . . Form . . . . Responsibility. . . . The batch command object for this panel is SIR. 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. . . Exit Parm . Size/Type: 1 to 16 alphanumeric characters Required: No Batch Keyword: EXitparm Chapter 5.1 Schedules -------------. . . Verify . Notify . .5. UP for Previous Screen. . xxyy (SCHD) SCHEDULE INFORMATION -------------- Enter END to Exit.CA-SCHEDULER 9. . . Quantity . or DOWN for Next Screen. . . . Comment . . . . 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. A Information: Description . NO Specification . .

Size/Type: 1 to 12 alphanumeric characters Required: No Batch Keyword: NOtify Responsibility Name the person or group responsible for this schedule.1 Schedules Form Identify a form that is associated with the standard jobs in this schedule. Size/Type: YES or NO Required: No Batch Keyword: Verify Default: NO Specification Give specification data associated with this schedule.5. Size/Type: 1 to 12 alphanumeric characters Required: No Batch Keyword: Resp Verify Indicate whether this schedule requires special verification. 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 8 alphanumeric characters Required: No Batch Keyword: Form Quantity Indicate how much input or output is expected for this schedule. 5-22 Online Guide . This is for reporting purposes only. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: SPec Press PF8 for the next panel.

. . . . . 5 to 8 .1 Schedules -------------. . . . Deliverables: 1 to 2 . 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. or UP for Previous Screen. . . COMMAND ===> Name . Size/Type: 1 to 16 alphanumeric characters specified from zero to eight times Required: No Batch Keyword: DELx where x is 1 to 8 Chapter 5. 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. . . . . . . . . . . .5. The batch command object for this panel is SIR.CA-SCHEDULER 9. . 3 to 4 . xxyy (SCHD) SCHEDULE INFORMATION -------------- . The fields are: Destinations Give up to eight destinations for the output from the jobs in this schedule. . . . . . Enter END to Exit. A Destinations: 1 to 4 . 7 to 8 . . . . . 5 to 6 . . Database 5-23 . .

1.2 Example 2 This schedule should be selected only on Mondays and Tuesdays. Use PF3 to exit and save any changes.1 Example 1 Define a schedule that should be considered for autoscan. The first line of the criteria displays the calendar name in use. the criteria is browsed using the ISPF/PDF BROWSE service.3.2.3 Batch Examples 5.2 Schedule Criteria If you are displaying a schedule. the criteria is edited using the ISPF/PDF EDIT service.CRI='MON OR TUE' // 5-24 Online Guide .AUTOSEL=YES // 5. //STEP1 EXEC CAJUTIL //SYSIN DD DEFINE SBR N=ABC.3.5. if any. A NOTE line indicates the calendar name in use. 5. Use CAN to exit without saving any changes.1. where xxx is the new calendar name. If you need to change the calendar name. enter CAL xxx on the command line. If you are defining or altering a schedule.1.1 Schedules 5. if any.1. //STEP1 EXEC CAJUTIL //SYSIN DD DEFINE SCR N=ABC.

Enter the new schedule name in the To schedule field.5. Chapter 5.1 Schedules 5. After you have copied the schedule. The schedule you selected from the directory is listed in the Copy schedule field. Database 5-25 . OPTION ===> Copy schedule to schedule xxyy (SCHD) COPY SCHEDULE ----------------- Enter END to exit.1.4 Copying a Schedule -----------------.CA-SCHEDULER 9. All of the schedule is copied. you can alter the new schedule to make any desired changes. including criteria.

and Analyze jobs. All information is copied. Delete. syntax check JCL. to view a specific job. Schedule. A CPU job has JCL and executes on a JES initiator. . such as printing and delivering reports. or may be a command that executes on a non-OS/390 system. DISPLAY. to edit a specific job. Use option 4. If you have requested the Delete Confirmation option (see Chapter 3. Edit. the job is deleted immediately. creating a new job. . and Schedule fields.2 Jobs A CA-Scheduler job is a unit of work. DEFINE. . to remove a specific job. - 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.5. Use option 5. You may enter a partial job name in the Job field or a partial schedule name in the Schedule field to limit the display. to create a new job. to display a scrollable list of schedules. including criteria. Job Number. or post-CPU tasks. . ALTER. Station . Use option 2. “Options”). then a panel is displayed asking you to confirm the deletion. Use option 1. DELETE. ---------------------. Use option 3. . A pre-CPU job is a manual task that must be completed before the CPU job executes. OPTION ===> Job . Jobs may be CPU tasks. pre-CPU tasks. . Otherwise. COPY.CA-SCHEDULER 9. 1 2 3 4 5 6 7 8 .2 Jobs 5. 5-26 Online Guide . From the list you may Select (display). Use option 6. For options 2 to 8. A post-CPU job is a manual task that cannot be started until after the CPU job completes. you must enter the Job. The Job Number and Station fields are ignored. such as making temporary changes to the job's JCL. . to copy a job. Station. Job Number. Option 2 of the CA-Scheduler Database menu displays the Jobs menu. DIRECTORY. Copy. .

4. then the date and time of that change is displayed. CA-Scheduler only reads the first 50 jobs before displaying the list. 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 2 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. Database 5-27 . If the job has been defined or modified in Version 9. more rows are automatically added until the entire list has been built. SYNTAX.1 Directory ---------------------. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. As you scroll down. Jobs that were last updated prior to Version 9.CA-SCHEDULER 9.2 Jobs Use option 7. the user ID field may be blank. Use option 8. 5. Chapter 5.5. If the job was defined and modified in batch only prior to Version 7.2. See 6. ANALYZE.0 show blank date and time. to review the job for any logical errors.0 or higher. to inspect the job's JCL for syntax errors. “Analyze” on page 6-3 for more information.1.

Use option 1. Use option 3. “Job Criteria” on page 5-57 for more information. 4 .2 Jobs Select a job by entering a letter to the left of the job.4.2 Job Options The same panels are used to display. Schedule. 1 .5. . See the next topic for more information. DRIVER. Job Number. 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. and define jobs. OPTION ===> Job . See 5. VRM.2. to view or edit step level return codes. See 5. . to edit or browse the job's criteria. See 5. . Use option 4. “Virtual Resources” on page 5-63 for more information.2. DEFINITION.2. . to view or edit Driver parms for jobs with a Library Type of DRIVER. See 5.5.2.CA-SCHEDULER 9.2. CRITERIA. . - 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. edit. Use option 5. ----------------------.2.2. Station . to view or edit virtual resources associated with this job. “Job Steps” on page 5-58 for more information.3. JOB STEPS. 5-28 Online Guide .2. to view or edit the job definition.2. Use option 2.2. . 1 2 3 4 5 . “Driver Parms” on page 5-62 for more information.

. . xxyy (SCHD) JOB BASE -------------------Station .CA-SCHEDULER 9. Use PF7 and PF8 to scroll up and down through the panels. . or DOWN for Next Screen. To save your changes and exit. . .2. . . .1 Job Definition The job definition information is contained on several panels. Times: Early Start . . Must Start . .2. . enter CAN on the command line. . COMMAND ===> Name .5. . . . You may jump to this panel from other job definition panels by using one of the following jump commands: TOP JBR BASE TIMes BACKlog Chapter 5. . Enter END to Exit. Miscellaneous: Internal Priority . The batch utility to use for maintaining jobs is CAJUTIL0. . To exit without saving your changes. 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. . . Schedule . . Database 5-29 . Skip . . . -------------------. Maximum Execution Average Time . Selection: Backlog . . . . .2 Jobs 5. Number . Must End . . . use PF3. . . The batch command object for this panel is JBR.

or post-CPU. For CPU jobs. number. The station determines if the job is CPU. Up to 99 separate instances of the job may be defined by varying the number from 01 to 99. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JNo Default: 01 Station The station of the job being manipulated. Station 39 is reserved for staged JCL setup. (This can also be done by varying the Number of the job. This field may not be modified after the job has been defined. and station may be defined to multiple schedules so that it may run multiple times on the same day. Station 60 is reserved for report printing. All jobs must belong to a schedule.5. and the CPU job must be complete before the post-CPU jobs may start. and greater than 40 are post-CPU. The same job name. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job being manipulated. This field may not be modified after the job has been defined.2 Jobs The fields are: Name The name of the job being manipulated. All pre-CPU jobs must be complete before the CPU job may start. The schedule must be part of a given day's workload before the job may be considered for that workload. This field may not be modified after the job is defined.) The schedule must exist before the job may be defined. Jobs with stations less than 40 are pre-CPU. Station 40 jobs are CPU jobs. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Schedule 5-30 Online Guide . this name must match the name on the JCL JOB statement. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: STation Default: 40 Schedule The schedule of the job being manipulated. pre-CPU. This field may not be modified after the job has been defined.

Note: This is the earliest that the job may start. NO indicates that the job should be canceled (if not currently executing) and the next day's copy made available. the MAILBOX report.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. Leading zeros do not need to be entered. the job may start after this time. and hhmm is the time. If it has predecessors that are still unresolved. Database 5-31 . 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. YES indicates that the job should be retained until it (and the rest of its schedule) has completed. 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. Skip is used only if the schedule has Auto Select set to Yes.5. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: No Batch Keyword: MUsttime Default: 0 (Never considered late) Chapter 5. 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. Blank causes the schedule's Backlog option to be used. The value is in the format of ddhhmm. The job may not start before the schedule starts. and hhmm is the time to start. and/or a user. where dd is the number of autoscans that the job should wait. where dd is the number of autoscans that the job should wait. Leading zeros do not need to be entered. A message may be sent to the console. The value is in the format of ddhhmm. it is considered late.

The value is in the format of ddhhmm.2 Jobs | | Must End If the job is not needed by this time it is considered late. 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. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JPrty Default: Value on CAIJGEN option SPRTY Press PF8 for the next panel. 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). Leading zeros do not need to be entered. to find work. 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. where dd is the number of autoscans that the job should wait. 5-32 Online Guide . It is displayed only for CPU jobs (station 40). within the schedule. and/or a user. and/or a user.5. Leading zeros do not need to be entered. and hhmm is the time. and hhmm is the time. CA-Scheduler searches these control blocks. The value is in the format of ddhhmm. where dd is the number of autoscans that the job should wait. 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. A message may be sent to the console. This value is used only in simulation if the job has never been executed. The value is in the format of ddhhmm. the MAILBOX report. where 01 is the higher priority. that controls the order of internal control blocks. A message may be sent to the console. then it is considered late. the MAILBOX report.

. Member Prefix . The batch command object for this panel is JBR. UP for Previous Screen. . . .2 Jobs -----------------. Submission: Local Execution Sysid . 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. . Remote Execution Sysid Insert Sched Enviro . . . Number . JOBDOC CA-Jobdoc LIBRN CA-Librarian PANV CA-Panvalet PDS Partitioned data set Chapter 5. JCL: Library Type . . Enter END to Exit.CA-SCHEDULER 9. . Scheduling Environment. or DOWN for Next Screen. Remote Execution Node . Member Name . . JCL DDname . Valid values are: DRIVER CA-Scheduler generates one line of JCL for Driver to expand. . Database 5-33 . xxyy (SCHD) CPU JOB BASE -----------------Station . . . . . . . Schedule . .5. . . . COMMAND ===> Name . . .

or abend. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: MBrsubid Default: Blanks 5-34 Online Guide . 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). ROSCOE CA-Roscoe Required: No Batch Keyword: Libtype Default: Value on schedule's Library Type field JCL DDname For Library Type of PDS. See the field Test Parm on page 5-38. the first portion of the member name in the CA-Panvalet library. TESTLIB CA-Scheduler submits a dummy job (based on the skeleton in member CAJUTSTB of the PDS allocated to ddname JCLMASTR). See "Performance Considerations" in the Systems Programmer Guide for performance implications.2 Jobs RDRQ Jobs are manually submitted outside of CA-Scheduler with a TYPRUN=HOLD on the job statement. The dummy job may execute for a specified number of seconds. The Member Prefix and Member Name fields are combined and the first 10 characters used as the member name. based on parms defined at the job level. USERLIB The access method is provided by a site-written exit program. end with a specific return code. CA-Scheduler releases the job and tracks it as if the job was submitted by CA-Scheduler. the ddname of the partitioned data set containing the job's JCL. See "User Exits and APIs" in the Systems Programmer Guide for more information.5.

“Remote Scheduling” on page 11-1 for more information. CA-Scheduler modifies the job's JCL during submission to include this system ID. the value may be *REMOTE to indicate that the job executes on a non-OS/390 system running Unicenter TNG. If the CAIJGEN installation option INSROUT is YES. Database 5-35 . the insert option is taken from the schedule. Alternatively.2 Jobs Member Name The member name in the JCL library that contains the job's JCL.5. If the CAIJGEN installation option INSRSYS is YES. 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. See Chapter 11. 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. Note: The job name in the JCL must match the job name as defined to CA-Scheduler. NO. The scheduling environment to be inserted into the JCL is taken from the Scheduling Environment field below. or blank Required: No Batch Keyword: INSRSenv Default: Blank (use schedule's value) Chapter 5. CA-Scheduler modifies the job's JCL during submission to include this system ID. CA-Scheduler modifies the job's JCL during submission to include this node 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. or from the schedule if blank. Size/Type: YES. If not specified. If the CAIJGEN installation option INSRSYS is YES. 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.

or DOWN for Next Screen. Interrupt . Number . . NO Enter END to Exit. Fail Code . GT (Greater Than). . The value is only inserted if the Insert Sched Enviro field above is YES (or defaults to YES). . . . .2 Jobs Scheduling Environment The name of a Workload Manager scheduling environment that should be inserted into this job's JCL during submission. 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. The batch command object for this panel is JBR. .CA-SCHEDULER 9. . xxyy (SCHD) CPU JOB BASE -----------------Station . EQ (EQual). . Memo . . . Size/Type: 1. . . COMMAND ===> Name . Test Parm . . . . LE (Less than or Equal). . Size/Type: 2 alphanumeric characters Required: No Batch Keyword: FAILOper Default: GE 5-36 Online Guide . and LT (Less Than). the schedule's value is used. It is displayed only for CPU jobs (station 40). If the Scheduling Environment is blank. NE (Not Equal). Schedule . Valid values are GE (Greater than or Equal). . Abend Option Fail Option Options: Insert CA-11 Stage JCL . . See Fail Code. . UP for Previous Screen.5. . . . Failures: Fail Oper . . . . -----------------. . .to 16-alphanumeric characters Required: No Batch Keyword: SCHENV Default: Blank (use schedule's value) Press PF8 for the next panel.

schedule Run the specified schedule. BACKOUT Submit another job. Database 5-37 .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. A typical setting is a Fail Oper of GE and a Fail Code of 1. 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. then the job is marked as failed. Valid values are: ABORT Do not let successors run. CONT Allow successors to run as if the job ended successfully. whose name is built based on the CAIJGEN option BACKOUT. schedule Run the specified schedule.5. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: FAILEd Chapter 5. 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. CONT Allow successors to run as if the job ended successfully. BACKOUT Submit another job. The following equation is evaluated: job's-high-return-code Fail-Oper Fail-Code If the statement is true. making zero the only acceptable return code for the job. Valid values are: ABORT Do not let successors run. whose name is built based on the CAIJGEN option BACKOUT.

An interrupted job can be run again if necessary using the RERUN or SUBMIT commands. It is to be posted as complete as soon as it completes successfully. The job's status is shown as Interrupted instead of Completed even though it ends successfully. A manual reply by the operator is required before the job may execute.5.2 Jobs Default: ABORT Insert CA-11 Controls the automatic insertion of the CA-11 RMS. the Test Parm determines how long the job executes and how it ends. 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. Successors to this job are not posted as satisfied until this job is ended manually using the COMPLETE command. 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. Size/Type: NO|YES Required: NO Batch Keyword: INTERUPT Default: NO Stage JCL If Stage JCL is set to YES. YES This job is to be interrupted. This is the default. Valid options are: NO This job is not to be interrupted. Size/Type: 1 to 60 alphanumeric characters Required: No Batch Keyword: MEmo Test Parm For Library Type of TESTLIB. One or more of the following may be specified: T=nnnn Number of seconds to execute 5-38 Online Guide . the job's JCL is copied into the CA-Scheduler active workload and submitted from there.

Number . Schedule . . Database 5-39 . Otherwise. or DOWN for Next Screen. ---------------. 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. Non-CPU Options: Automatic Start . . Size/Type: YES|NO Required: No Batch Keyword: AUtostrt Default: NO Press PF8 for the next panel. xxyy (SCHD) NON-CPU JOB BASE ---------------Station . Chapter 5. . . The batch command object for this panel is JBR. . separate them with commas. the non-CPU job starts as soon as any Early Start time and predecessors are satisfied. . NO Enter END to Exit. UP for Previous Screen.2 Jobs F=nnnn Normal return code to generate A=nnnn Abend code to generate (user abend) If multiple options are specified. the job waits for manual Start Job command.CA-SCHEDULER 9. COMMAND ===> Name . It is displayed only for non-CPU jobs (stations other than 40). The field is: Automatic Start If set to YES.5.

If multiple jobs are available to start. NO Documentation: Display Key . . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Dispkey 5-40 Online Guide . 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.CA-SCHEDULER 9. Display Time . Schedule . 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. . . . . UP for Previous Screen. . .2 Jobs -------------------. . . The value is not used outside of simulation. Use Simulation Times . . . JES Priority . . 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. Enter END to Exit. . . . Simulation: JES Class . . jobs with high JES Priority values are started first.5. . The value is not used outside of simulation. Number . . The batch command object for this panel is JBR. COMMAND ===> Name . xxyy (SCHD) JOB BASE -------------------Station . or DOWN for Next Screen. .

or DOWN for Next Screen. UP for Previous Screen. . . .2 Jobs Display Time The time to display the documentation referred to by Display Key on the OS/390 console. . Leading zeros do not need to be entered. The CAIJGEN option SECURTY must be set to YES. Chapter 5. Database 5-41 . Group id . Schedule . The value is in the format of ddhhmm. and the CAIJ$SEC option for the specific library type (access method) must be YES before a user ID is inserted into the JCL. and hhmm is the time to start. The batch command object for this panel is JSI.5. The value JSI corresponds to this field. COMMAND ===> Name . Enter END to Exit. .CA-SCHEDULER 9. Note: The user ID in the submitted job is determined by the order of the CAIJGEN option SUBUID. 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. . xxyy (SCHD) JOB SECURITY -----------------Station . External Security: User id . . -----------------. where dd is the number of autoscans that the job should wait. 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. . Number .

. . . . . 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. . 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 . . . . . . Note: The group ID in the submitted job is determined by the order of the CAIJGEN option SUBUID. . . Enter END to Exit. . The batch command object for this panel is JRR. xxyy (SCHD) JOB RESOURCE -----------------Station . Separate Job Resource . . Execution: . COMMAND ===> Name . -----------------. Schedule . . UP for Previous Screen. The value JSI corresponds to this field. The CAIJGEN option SECURTY must be set to YES. Job List . . . .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. . or DOWN for Next Screen. Number . .5. and the CAIJ$SEC option for the specific library type (access method) must be YES before a groupid is inserted into the JCL.CA-SCHEDULER 9. . .

of any length (including zero). Size/Type: 1 to 8 alphanumeric characters specified from one to eight times Required: No Batch Keyword: SEPJob=(name. Chapter 5..2 Jobs The fields are: Resource The job must "own" this resource name before CA-Scheduler submits it. The entries may use masking characters.. 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. ABXXD.) Press PF8 for the next panel. the use of masking in the Job List may cause severe performance problems. A question mark ('?') represents any character. An asterisk ('*') represents any character. If two or more jobs have the same resource name specified. this job is not submitted.name.5.. ABCD. ABCDEFG Doesn't Match ABCDE ABD ABCDE ABDC ABDEF Note: If the CAIJGEN option MCPU is set to YES. ABD ABC. Mask ABCD AB?D AB*D ABC* AB?D* Matches ABCD ABCD. Database 5-43 . ABCDE ABCD. If any job that matches an entry in the list is submitted when CA-Scheduler is ready to submit this job. only one at a time may be submitted. See the topic Performance Considerations for Separate Job List in the Systems Programmer Guide. Question marks and asterisks may be combined. ABXD ABCD. but only of length one.

. . This information is used only by simulation. . .2 Jobs -----------------. .CA-SCHEDULER 9.count) where nn is 01 to 04 Tape EXCPs The number of tape I/Os done by this job. . . 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. . . Size/Type: 1 to 8 numeric characters Required: No Batch Keyword: TExcps 5-44 Online Guide . . Number . . . Unit Type/Count . Enter END to Exit. 1 to 3 numeric characters Required: No Batch Keyword: TAPEnn=(type. . Route Delay . . / / / / / / Simulation Resources: Disk Type/Count . Maximum CPU Time . . . . Tape EXCPs . 1 to 3 numeric characters Required: No Batch Keyword: DASDnn=(type. / / / / / / xxyy (SCHD) JOB RESOURCE -----------------Station . or DOWN for Next Screen. (ddhhmm) (ddhhmm) Schedule . . COMMAND ===> Name .5. . . . . . . . . Size/Type: 1 to 8 alphanumeric characters. . The batch command object for this panel is JRR. . . This information is used only by simulation.count) where nn is 01 to 04 Dasd EXCPs The number of DASD I/Os done by this job. . . . . Unit EXCPs . Tape Type/Count . . . . . Dasd EXCPs . . . . 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. . . This information is used only by simulation. Size/Type: 1 to 8 alphanumeric characters. . . . UP for Previous Screen. .

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. Database 5-45 .5. 1 to 3 numeric characters Required: No Batch Keyword: UNITnn=(type. Chapter 5. This information is used only by simulation.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. This information is used only by simulation. overrides the average execution time. Size/Type: 1 to 8 numeric characters Required: No Batch Keyword: UExcps Maximum CPU Time The execution duration of the job for simulation reports. Size/Type: 1 to 8 alphanumeric characters.count) where nn is 01 to 04 Unit EXCPs The number of other unit I/Os done by this job. in ddhhmm format. Used by simulation to more accurately reflect the time from submission to job completion. 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. This number.

. . .. abends. COMMAND ===> Name . . . . . . . .) Job Start A list of user IDs or OPERxxyy values to which messages should be sent when the job starts. . . . . . . for: . See below for more information. . . . . . . .2 Jobs -----------------. .5. . The batch command object for this panel is JMR. or DOWN for Next Screen. . . . . . . . UP for Previous Screen.. . See below for more information. . . . . . . . . . . . ... .CA-SCHEDULER 9. completes. . . . Number .user. . . . Job Abend . . Size/Type: 1 to 8 alphanumeric characters specified zero to four times Required: No Batch Keyword: STARtmsg=(user. . . . or becomes late.user. . . . . . . Job Skipped . . . . . . . fails. . . Job Fail . . . . . . . . .. . . Job Interrupt Job End . . . . . . . . xxyy (SCHD) JOB MESSAGES -----------------Station . . . . . Userid to Notify All Events . Schedule . . . . Job Start . Job Purge . . . . . Job Late . . . . . . . is purged. . Enter END to Exit. . . . Size/Type: 1 to 8 alphanumeric characters specified zero to four times Required: No Batch Keyword: Msg=(user. 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. . . . .. .) 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,...)

Chapter 5. Database 5-47

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 . . . . . . . . . . . . . . . . . . . . . . . . . .

Enter END to Exit, UP for Previous Screen, or DOWN for Next Screen.

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 .

Enter END to Exit, UP for Previous Screen, or DOWN for Next Screen.

Chapter 5. Database 5-49

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 . .

Enter END to Exit, UP for Previous Screen, or DOWN for Next Screen.

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.

Chapter 5. Database 5-51

5.2 Jobs

----------------- CA-SCHEDULER 9. COMMAND ===> Name . . . Inform JES Nodes: Node . . . . . . Number . . . . . .

xxyy (SCHD) JOB NODE INFORM ---------------Station . . . . . . . . . . Schedule . .

Enter END to Exit, UP for Previous Screen, or DOWN for Next Screen.

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 . .

Enter END to Exit, UP for Previous Screen, or DOWN for Next Screen.

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

Chapter 5. Database 5-53

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.

Chapter 5. Database 5-55

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 . .

Enter END to Exit, or UP for Previous Screen.

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

2. Use CAN to exit without saving any changes. Database 5-57 . NO Indicates that the dash option is not used.2. If you need to change the calendar name. the criteria is edited using the ISPF/PDF EDIT service. Size/Type: 1 to 14 alphanumeric characters Required: No Batch Keyword: XPPswd Verify A second chance to type the password correctly. or blank Required: No Batch Keyword: XPSUtype 5. If you are defining or altering a job. Use PF3 to exit and save any changes. if any. blank Indicates that the global default (CAS9 CAIJGEN XPSUTYPE) value is used. the criteria is browsed using the ISPF/PDF BROWSE service. The field may be case-sensitive.2 Jobs User id The user ID with which the job should be initiated. where xxx is the new calendar name. enter CAL xxx on the command line. if any.5. SU Flag Determines if the Unix Switch User (su) flag is sent for this job or not. Size/Type: YES. A NOTE line indicates the calendar name in use. Chapter 5.2 Job Criteria If you are displaying a job. Size/Type: 0 to 32 alphanumeric characters Required: No Batch Keyword: XPUser | | | | | | | | | | | | | | | | | | | Password The password for the above user ID. NO. YES Indicates that the Unix su command is issued with the dash ("-") option. The setting has no impact for jobs not executing on Unix-based systems. The first line of the criteria displays the calendar name in use.

3 Job Steps Use Job Step entries to determine if step has ended with an unacceptable return code. -------------------. Any step that does not have a specific JSR uses the default JSR. use Job Step entries. Note: If any Job Step entries are specified for a job. COMMAND ===> Name . nine steps must end with zero and one step must end with a 4. The fields on the panel are: Name The name of the job whose Job Step entries are being manipulated. If.-------BOTTOM OF DATA The batch command object for this panel is JSR. .CA-SCHEDULER 9. More ---- Failoper Failcode -------. A blank Procstep and a Stepname of * (asterisk) may be defined as a default JSR for the job. It is displayed to be consistent with other job displays. Procstep -------Number . . CA-Scheduler ignores the job's Fail Oper and Fail Code values. For example.2. if a job has 10 steps that all must end with a return code of zero. 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. Stepname -------Type ---- xxyy (SCHD) JOB STEPS ------------------SCROLL ===> PAGE Station . If one or more steps have different rules for "bad" return codes. . 5-58 Online Guide . Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JNo Default: 01 Station The station of the job. use Job Step entries. use a Fail Oper of GE and a Fail Code of 1 on the job. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The number of the job. however. .5. .2. Schedule . This number is always 40 because only CPU jobs have steps.2 Jobs 5.

the step failed. Database 5-59 . If Type is BAD. the Procstep name may not be changed. LE (Less than or Equal). then the Procstep is blank. The Procstep must be blank for the default JSR. See Failcode. the step was successful. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: PROCstep Stepname The step name (with the EXEC PGM= on it). The value may be changed by overtyping it. Valid values are GE (Greater than or Equal). then the Type is used to determine if the step ended successfully or not.2 Jobs Schedule The schedule that owns the job. 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. 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.5. GT (Greater Than). 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. The following equation is evaluated: return-code Failoper Failcode If the statement is true. NE (Not Equal). Size/Type: 1 to 8 alphanumeric characters or * (asterisk) for the default JSR for this job. if Type is GOOD. and LT (Less Than). EQ (EQual). the Stepname name may not be changed. Once a Job Step entry is defined. Required: Yes Batch Keyword: STEP Type Determines if the Failoper/Failcode pairs indicate good return codes or bad. Chapter 5. Once a Job Step entry is defined.

. . . . . . . . . . type CAN on the command line. . procedure) PGM=) . . . . . Enter END to exit. . . . Number . then the opposite of Type is used to determine if the step ended successfully or not. Schedule .CA-SCHEDULER 9. . . . . . . Fail operator . . . . . . -------------------. or press ENTER to save changes. . . . xxyy (SCHD) JOB STEPS ------------------Station . . . . Copy entries by typing an R next to the entry. . . . . . . . . . . (Outside of the (Step name with (Good or Bad) Return code . . Job Step Entry: The following panel is displayed when adding or copying a Job Step entry. . .2 Jobs If the statement is false. . BAD . . . . The Job Steps panel displays. . . . . . .5. . . . . . To exit without saving changes. . . . . . . . . . . . . . Step Definition: Procedure step name Step name . . . 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. . . . . . . . . Press PF3 to exit and save any changes. . . . . . . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: PROCstep 5-60 Online Guide . . . . . The Job Steps panel displays. . . . . . Delete entries by typing a D next to the entry. . . . . The batch command object for this panel is JSR. . . . COMMAND ===> Name . . . . This field may be blank if the step does not use a PROC. The fields are: Procedure step name The name of the step outside of a PROC. . . . If true. . . . . . step is . . .

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 Chapter 5. The Procstep must be blank for the default JSR. This field is required. If Type is BAD. then the Type is used to determine whether the step ended successfully. Size/Type: BAD or GOOD Required: Yes Batch Keyword: TYpe Fail oper A Boolean operator. if Type is GOOD.2 Jobs Step name The name of the step (with the EXEC PGM= on it).5. Required: Yes Batch Keyword: STEP If true. then the step failed. Size/Type: 1 to 8 alphanumeric characters or * (asterisk) for the default JSR for this job. used with the Return code. to determine if the step's return code is unacceptable. step is Determines if the Failoper/Failcode pairs indicate good return codes or bad. The following equation is evaluated: step's-return-code Fail-oper Return-code If the statement is true. the step was successful. 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. Database 5-61 . If the statement is false.

---------------------------------------------------------------BOTTOM OF DATA The fields are: Variable The name of the variable parameter to be passed to the Driver PROC. To exit without saving any changes. Type The value NORMAL or RESTART. 1 xxyy (SCHD) DRIVER PARMS -----------------SCROLL ===> PAGE Station . This adds a blank entry that may be overtyped. VARNAME(1) ). type CAN on the command line.CA-SCHEDULER 9. Variable parameters with a type of NORMAL are passed when jobs are automatically submitted or submitted due to the FORCE or SUBMIT commands. Variables may be added by typing an I on the command line or to the left of an existing variable.4 Driver Parms You may specify parameters to be passed to a Driver procedure for jobs with a Library Type of DRIVER. .2.2. COMMAND ===> Name . . the output is displayed and the list of variables is presented. The variable name may be one to seven characters long with an optional array subscript in parentheses (that is. . DRVTEST Number . it is not shown. If the command is successful.5. . Variable parameters with a type of RESTART are passed when jobs are submitted due to the RERUN command. Variables may be deleted by typing a D to the left of the variable. -----------------. 5-62 Online Guide .2 Jobs 5. If it fails. . DRVTEST Variable Type / Value ----------. 4 Schedule . A batch command is built to process the changes. Press PF3 to exit and save any changes. Value (Under the Type value) The value of the variable parameter.

Chapter 5.5 Virtual Resources You may view and maintain virtual resources that are required before this job may be submitted. COMMAND ===> Virtual resources required by job RT8 1 xxyy (SCHD) VRM ----.CA-SCHEDULER 9. Status The state that the virtual resource must have before the job may be submitted.2. Database 5-63 . Free Specifies if the virtual resource should be released at job end even if the job abends or fails.---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.5.---------.4. 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.-----. ----------------------. Select a job/virtual resource association by entering a letter to the left of the virtual resource.2 Jobs 5.10.Row 1 to 3 of 3 SCROLL ===> CSR JNO 1 Station 4 Schedule RESTEST8 _ _ _ Resource Type Status Free -----------------------------. “Job/VRM Association” on page 5-120.2.

specifying a normal and restart parm.S=XYZ.CRI='MON OR TUE' // 5.3.3.2 Jobs 5.4 Example 4 Define a job with a Library Type of Driver.2. step 2 must end with a four.2.S=XYZ. with an Early Start time of 2:00 PM. //STEP1 EXEC CAJUTIL //SYSIN DD DEFINE JBR N=DRIVJOB.3.2.1 Example 1 Define a job.3 Batch Examples 5.ERLYTIME=14 // 5.S=XYZ. //STEP1 //SYSIN DEFINE JSR DEFINE JSR // EXEC CAJUTIL DD N=ABC.3 Example 3 Define two steps: Step 1 must end with a zero.STEP=STEP2.S=XYZ. ABC.2.2 Example 2 This job should be selected only on Mondays and Tuesdays.5. RESTPARM='(VAR1=RESTART)' // 5-64 Online Guide . DRIVPARM='(VAR1=NORMAL)'.FAILOPER=NE. //STEP1 EXEC CAJUTIL //SYSIN DD DEFINE JCR N=ABC.3.STEP=STEP1.2.LIBTYPE=DRIVER.FAILCODE=1 N=ABC.S=XYZ.FAILCODE=4 5.FAILOPER=GE. to a schedule XYZ. //STEP1 EXEC CAJUTIL //SYSIN DD DEFINE JBR N=ABC.

5. you may alter the new job to make any desired changes.2. After you have copied the job. Database 5-65 . Chapter 5. Enter the new job information in the To job fields.CA-SCHEDULER 9. CA-Scheduler lists the job you selected in the Copy Job fields. All of the job is copied.2 Jobs 5. COMMAND ===> Copy job number station schedule To job number station schedule xxyy (SCHD) COPY JOB -------------------- Enter END to exit. including criteria.4 Copying a Job -------------------.

to create a new user ID.5. Edit. If the installation CAIJGEN option SECURTY is set to EXTERNAL. ALTER. If CAIJGEN SECURTY is set to NO or YES. Option 3 of the CA-Scheduler Database menu displays the User IDs menu. Use option 2. . you must enter the user ID. Use option 1. DEFINE. -------------------. DISPLAY. DIRECTORY.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. For options 2 to 6. 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. to view a specific user ID. OPTION ===> User ID . or Copy user IDs.CA-SCHEDULER 9. Your site may or may not require user definitions.3 User IDs 5. You may enter a partial user ID in the User ID field to limit the display. Use option 4. CA-Scheduler does not require and ignores user definitions. you may Select (display). . 5-66 Online Guide . to edit a specific user ID. Delete. From the list. Use option 3. CA-Scheduler requires user definitions. to display a scrollable list of users defined to CA-Scheduler.

COPY. Select a user ID by entering a letter to the left of the user ID. “Options”).1 Directory -------------------. 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. the user ID is deleted immediately.3. 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 Chapter 5. to remove a specific user ID. Database 5-67 . If you have requested the Delete Confirmation option (see Chapter 3. CA-Scheduler displays a panel asking you to confirm the deletion. DELETE. CA-Scheduler only reads the first 50 user IDs before displaying the list. PUBLIC JANE SMITH BOTTOM OF DATA Each user ID is displayed on a single row.3 User IDs Use option 5. 5.5. Use option 6. Otherwise. more rows are automatically added until the entire list has been built.CA-SCHEDULER 9. creating a new user ID. As you scroll down. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. to copy a user ID.

5. 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.2 User ID Definition The same panel is used to display. . Write . . . . To save your changes and exit. . . . . Stations .CA-SCHEDULER 9. Passwords: Read . Description . . . . COMMAND ===> User id . . and define user IDs.3. . .3 User IDs 5. . use PF3. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name 5-68 Online Guide . . . . . Enter END to exit. xxyy (SCHD) USER IDS -------------------- (General. enter CAN on the command line. . . To exit without saving your changes. Other: Type . . Manager) . . Supervisor. edit. . . . 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 -------------------. The batch utility to use for maintaining user IDs is CAJUTIL0. . .

If CAIJGEN SECURTY is set to YES..3 User IDs Read A password that the user must specify when accessing CA-Scheduler online only if CAIJGEN SECURTY is set to NO. 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. See Table 5-1 on page 5-70 for more information. Size/Type: 2 numeric characters specified from zero to eight times Required: No Batch Keyword: Connect=(nn. General and Supervisor user IDs cannot act on jobs at stations not in the list. or Manager.5.. 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. If CAIJGEN SECURTY is set to NO and the user does not enter the correct write password. Database 5-69 .) Chapter 5. Supervisor. Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Writpass Type The authority level of the user ID.nn. 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. The value may be General. Size/Type: 1 to 40 alphanumeric characters Required: No Batch Keyword: Desc Stations If one or more stations is specified. then this field is not used.

defined for stations at which this user ID is authorized. while connected to the JCL setup station (39).3 User IDs The authorizations granted at each Type are: Table 5-1 (Page 1 of 2). 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 . within schedules that this user ID is authorized to control ■ Display and alter staged JCL for jobs. 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.5. at stations for which this user ID is authorized. 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.

3 User IDs Table 5-1 (Page 2 of 2). HOLD ALL. PURGE ALL. MOVEOVER. UNPOST. Database 5-71 . and SET commands Chapter 5. 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. RELEASE AUTO.5. RELEASE ALL. POST.

5.3 User IDs 5.CA-SCHEDULER 9. WRITPASS=WRITE // 5.4 Copying a User ID ------------------.2 Example 2 Change the user ID above to be a manager. OPTION ===> Copy user USER1 3 to user xxyy (SCHD) COPY USERID ------------------ Enter END to exit. //STEP1 EXEC CAJUTIL //SYSIN DD DEFINE USERID NAME=PUBJOHN.3.3 Batch Examples 5. //STEP1 EXEC CAJUTIL //SYSIN DD ALTER USERID NAME=PUBJOHN. CA-Scheduler lists the user ID you selected in the Copy user field.READPASS=READ.TYPE=M // 5.3.3.DESC='JONH Q. PUBLIC'. 5-72 Online Guide . Enter the new user ID in the to user field.1 Example 1 Define a user ID as a supervisor.3.TYPE=S.3.3.

to create a new station. Option 4 of the CA-Scheduler Database menu displays the Station menu. DIRECTORY. Use option 1. or Copy stations.4 Stations Note: Station definitions are only used for simulation reports. ALTER. . You do not need to define stations for any other reason. Delete. Use option 4. Database 5-73 . . Use option 2. Use option 3. Stations less than 40 are manual tasks that must be done prior to a CPU task such as data entry or staging of JCL. Chapter 5.5. DEFINE. 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.4 Stations 5. -------------------. Station 40 is called the CPU station and is used for jobs that execute on a system.CA-SCHEDULER 9. A CA-Scheduler station is a place where work is done. you must enter the Station. to edit a specific station. OPTION ===> Station . For options 2 to 6. to display a scrollable list of stations defined to CA-Scheduler. DISPLAY. Stations greater than 40 are manual tasks that must be done after a CPU task such as delivery of a printed report. Edit. From the list you may Select (display). to view a specific station.

5. Select a station by entering a letter to the left of the station. COPY. 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.1 Directory -------------------. Otherwise. If you have requested the Delete Confirmation option (See Chapter 3. 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 . CA-Scheduler deletes the station immediately. CA-Scheduler displays a panel asking you to confirm the deletion. DELETE.4. CA-Scheduler only reads the first 50 stations before displaying the list.CA-SCHEDULER 9. Use option 6. to remove a specific station. creating a new one.4 Stations Use option 5. 5. to copy a station. As you scroll down. more rows are automatically added until the entire list has been built. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. “Options”).

The batch commands for maintaining stations are: Alter (Edit) Copy Define Delete Display (View) ALTER STATION N/A DEFINE STATION DELETE STATION LIST STATION --------------------. edit. . .4. The fields are: Station The number of the station being manipulated.CA-SCHEDULER 9. use PF3. To save your changes and exit. Database 5-75 . . Title . . . To exit without saving your changes.5. . This field may not be modified after the station is defined. . The batch utility to use for maintaining stations is CAJUTIL0. .2 Station Definition The same panel is used to display. Size/Type: 2 numeric characters Required: Yes Batch Keyword: Id Chapter 5. . . enter CAN on the command line. Description Time Zone . and define stations. . xxyy (SCHD) STATION -------------------- Enter END to exit. . COMMAND ===> Station . Details: Name .4 Stations 5. .

5. displayed only by the List Station command. Size/Type: 1 to 60 alphanumeric characters Required: No Batch Keyword: TITLe Description Information about the station.4 Stations Name A short name for the station that is displayed on the simulation Station report. Size/Type: 1 to 40 alphanumeric characters Required: No Batch Keyword: Desc 5-76 Online Guide . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Name Title The title is displayed on the simulation Station report.

Enter the new station number in the to station field.3.DESC='STAGED JCL' // 5.4 Copying a Station -----------------.2 Example 2: Define a JCL setup station (station 39) //STEP1 EXEC CAJUTIL //SYSIN DD DEFINE STATION ID=39. Chapter 5. OPTION ===> Copy station 39 to station xxyy (SCHD) COPY STATION ------------------ Enter END to exit.DESC='CPU STATION' // 5.4.4.1 Example 1: Define a CPU station //STEP1 EXEC CAJUTIL //SYSIN DD DEFINE STATION ID=4 .3 Batch Examples 5.4. CA-Scheduler lists the station you selected in the Copy station field.NAME='CPU'.NAME='STAGE'.3. Database 5-77 .5.4 Stations 5.4.CA-SCHEDULER 9.

. Use option 4. DISPLAY. ALTER. or Delete resource definitions. DEFINE. You do not need to define resources for any other reason.CA-SCHEDULER 9. you must enter the Station. Resources map devices such as tape drives and job initiators that must be serialized between jobs. DIRECTORY.5 Resources 5. tape. OPTION ===> Station .5. For options 2 to 5. . and defining the total number of tape drives here. DASD devices.5 Resources Note: Resource definitions are only used for simulation reports. . Use option 3. to display a scrollable list of resource definitions. and units to a specific CPU in a multiple CPU environment or define as shared by all CPUs. System . to edit the resources defined for a specific Station and System. 5-78 Online Guide . The same can be done with initiators. By defining each job to CA-Scheduler with the correct number of tape drives it uses. and any other unit. You may also enter a System ID. Option 5 of the CA-Scheduler Database menu displays the Resource menu. Edit. to create a resource definition for a specific Station and System. the CA-Scheduler SIMULATE command does not show individual jobs running until a sufficient number of tape drives are available. 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. From the list you may Select (display). -------------------. You may define DASD. to view resources defined for a specific Station and System. . Use option 2.

“Options”). DELETE.CA-SCHEDULER 9. to remove a resource definition. Database 5-79 . If you have requested the Delete Confirmation option (See Chapter 3.5.5 Resources Use option 5. Otherwise. CA-Scheduler deletes the station immediately.1 Directory -------------------.5. Enter: S to select a resource definition for viewing E to edit (alter) a resource definition D to delete a resource definition Chapter 5. CA-Scheduler displays a panel asking you to confirm the deletion. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. 5. Select a station's resource definition by entering a letter to the left of the station number. 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.

. NON-SHARED .5.5 Resources 5.2 Resource Definition The same panels are used to display.Resources shared across this Station Enter END to exit. . to maintain resources for all systems at this station. edit. See 5. and define resources.5. . “Shared Resources” on page 5-89 for more information.CA-SCHEDULER 9. to maintain resources for only the specified system (also called a substation). 5-80 Online Guide . Use option 1.2.5. See the next topic for more information. 1 2 xxyy (SCHD) RESOURCE ------------------- Sysid/Substation .Resources dedicated to this Sysid/Substation SHARED . -------------------. NON-SHARED. Use option 2. SHARED.2. OPTION ===> Station .

.5. DEFINITION. enter CAN on the command line.CA-SCHEDULER 9. to maintain a list of initiators (for station 40) or units (for other than station 40). Database 5-81 . INIT/UNIT. DASD and tape devices. and other units. Use PF7 and PF8 to scroll up and down through the panels. Tape.Times. . To save your changes and exit. 4 1 2 xxyy (SCHD) RESOURCE ------------------- Sysid/Substation .5 Resources 5. Unit Records INIT/UNIT .Initiators or Units Enter END to exit. To exit without saving your changes. Resource Definition Screens: The resource base information is contained on several panels.1 Nonshared Resources The batch utility to use for maintaining nonshared resources is CAJUTIL0. Dasd. Chapter 5. Use option 1. OPTION ===> Station .2. The batch commands for maintaining nonshared resources are: Alter (Edit) Define Delete Display (View) ALTER RESOURCE DEFINE RESOURCE DELETE RESOURCE N/A -------------------. DEFINITION . . to maintain information about times. use PF3.5. Use option 2.

.CA-SCHEDULER 9. Simulation Exit Parm . that work normally begins for this station. COMMAND ===> Station . . . . . xxyy (SCHD) RESOURCE -------------------- Sysid/Substation . . . . in hhmm format. (hhmm) (hhmm) (ddhhmm) (ddhhmm) Miscellaneous: Default Class . . . or DOWN for next screen. 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. . Enter END to exit. Times: Production Start Production End . . . Average Duration Route Delay . . . Size/Type: Required: Batch Keyword: Default: 1 to 4 alphanumeric characters No SYsid Blank Production Start The time of day. .5 Resources -------------------. . . . . The fields are: Station The station for which these resources may be used. Size/Type: Required: Batch Keyword: Default: 4 numeric characters hhmm No PSt 0000 (midnight) 5-82 Online Guide . .5. . . . . A typical value would be the autoscan time (CAIJGEN option AUTOTIM).

in hhmm format. 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). 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. Database 5-83 . have no history) and that do not have an Average Time specified on the job.5 Resources Production End The time of day. 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. that work normally ends for this station. See the Simulation Exit in the Systems Programmer Guide for more information.5. 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. Chapter 5. Size/Type: 1 alphanumeric character Required: No Batch Keyword: DEFclass Simulation Exit Parm A character string that is passed to the simulation exit.

Dasd 7 . Type Count Enter END to exit.count) where nn is 01 to 16. Count Dasd Dasd Dasd Dasd Dasd Dasd Dasd Dasd . Dasd: Type Dasd 1 . . . xxyy (SCHD) CPU RESOURCE ------------------ Sysid/Substation . . . . 16 . Dasd 11 . The fields are: Dasd 01 to Dasd 16 Up to 16 different types of DASD may be defined. 12 . UP for previous screen.5. Dasd 9 .5 Resources -----------------. Size/Type: Required: 1 to 8 alphanumeric characters No. . or DOWN for next screen. each with a type and count. . . The type must match the Disk Type on the job definition. . Dasd 5 . unless Count entered Count The number of the specified type of DASD available. . 2 4 6 8 . Dasd 3 . 14 . Size/Type: Required: 1 to 3 numeric characters from 1-255 No. . . unless Type entered Press PF8 for the next screen. Dasd 13 . The batch syntax for each is: DASDnn=(type. . COMMAND ===> Station .CA-SCHEDULER 9. . Dasd 15 . . . 5-84 Online Guide . Type The type of DASD being defined. . It is displayed only for CPU station resources (station 40). . . 1 . . .

Chapter 5. . . Tape 7 . 12 . COMMAND ===> Station . The batch syntax for each is: TAPEnn=(type. unless Type entered Press PF8 for the next screen. . . . UP for previous screen. The type must match the Tape Type on the job definition. . . Type Count Enter END to exit. . Database 5-85 . unless Count entered Count The number of the specified type of tape drive available. . Size/Type: Required: 1 to 8 alphanumeric characters No.5. Tape 3 . or DOWN for next screen.count) where nn is 01 to 16. . . Tape 15 . . . . . 16 .5 Resources -----------------. . Tape 11 . Tape 5 . . . The fields are: Tape 01 to Tape 16 Up to 16 different types of tape drives may be defined. 14 . each with a type and count. Tape 13 . Tape: Type Tape 1 . . Size/Type: Required: 1 to 3 numeric characters from 1-255 No. xxyy (SCHD) CPU RESOURCE ------------------ Sysid/Substation . . . 2 4 6 8 . 1 . Type The type of tape drive being defined. Tape 9 . Count Tape Tape Tape Tape Tape Tape Tape Tape .CA-SCHEDULER 9.

xxyy (SCHD) RESOURCE -------------------- Sysid/Substation . . 2 4 6 8 . . unless Count entered Count The number of the specified type of unit record available. Count Unit Unit Unit Unit Unit Unit Unit Unit . Unit 11 . . .count) where nn is 01 to 16. . . . . Unit 9 . . . . Size/Type: Required: 1 to 3 numeric characters from 1-255 No. Unit 3 . Unit Record: Type Unit 1 . . . The fields are: Unit 01 to Unit 16 Up to 16 different types of unit records may be defined.5. unless Type entered To exit and save your changes. Type The type of unit record being defined. . . . Type Count Enter END to exit. . Unit 13 . . each with a type and count. 16 . Unit 7 . press PF3.CA-SCHEDULER 9. 12 . . . Size/Type: Required: 1 to 8 alphanumeric characters No. Unit 5 . COMMAND ===> Station . .5 Resources -------------------. The batch syntax for each is: URnn=(type.or UP for previous screen. Unit 15 . 1 . 5-86 Online Guide . type CAN on the command line. The type must match the Unit Type on the job definition. To exit without saving. 14 .

5 Resources Resource Initiator ---------------. Size/Type: 2 numeric characters Required: Yes Batch Keyword: STation Sysid/Substation The specific system at this station for which the initiators are defined.5. Size/Type: 1 to 36 alphanumeric characters Required: Yes Batch Keyword: see Number Chapter 5. . Database 5-87 . COMMAND ===> Station . where nnn is 001 to 255 Header A label to use in the simulation reports as a name for this initiator. Each initiator must have a unique number from 1 to 255. Size/Type: Required: Batch Keyword: Default: 1 to 4 alphanumeric characters No SYsid Blank Number The number of the initiator. . Classes -----------------------------------AB B B ASDF BOTTOM OF DATA The fields are: Station The station for which the initiators are defined. 4 Number -----1 2 3 5 Header -------INIT1 INIT2 INIT3 INIT5 xxyy (SCHD) INITIATORS/UNIT ROW 1 TO 4 OF 4 SCROLL ===> CSR Sysid/Substation . Up to 36 classes may be specified. . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: see Number Classes The classes processed by this initiator.header).CA-SCHEDULER 9. Size/Type: 1 to 3 numeric characters Required: Yes Batch Keyword: INITnnn=(classes.

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.

Chapter 5. Database 5-89

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.

Chapter 5. Database 5-91

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 Batch Examples
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.

Chapter 5. Database 5-93

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

Chapter 5. Database 5-95

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

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

(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

Chapter 5. Database 5-97

1W-31W Yes Other than the panels shown above. 1 . valid values are: Value FD LD 1 . . . xxyy (SCHD) CALENDAR -------------------- JANUARY Sunday --------4 11 18 25 . Description . 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 . UP for previous month. or enter the first three characters of a month on the command line. . COMMAND ===> Calendar . type CAN on the command line. 5-98 Online Guide . . -------------------. 17 . which are only used when a calendar is defined. Wednesday --------7 14 21 28 W W W W Legend: W . LD.CA-SCHEDULER 9. . . . To exit without saving your changes.5.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. FW. To exit and save your changes. . 1-31. . and define calendars. alter. the same panel is used to display. LW. 24 . Use PF7 and PF8 to scroll up and down through the months.31 FW LW 1W . 31 . .Workday Enter END to exit.6 Calendars For monthly calendars. or DOWN for next month. press PF3.

Size/Type: Required: 1 to 40 alphanumeric characters No 1 to 31 The days of the month. they are not workdays. Chapter 5. Enter the new calendar information in the To calendar fields. COMMAND ===> Copy calendar year To Calendar Year xxyy (SCHD) COPY CALENDAR ----------------- Enter END to exit. Database 5-99 . The calendar you selected is listed in the Copy calendar fields.6. 5. This field may not be modified.5. Days marked with a W are workdays.CA-SCHEDULER 9.3 Copying a Calendar -----------------. along with their attribute. Otherwise.6 Calendars The fields are: Calendar The name of the calendar being maintained. Size/Type: Required: 1 to 8 alphanumeric characters Yes Description May be used to describe the calendar or its purpose.

CA-Scheduler deletes the date table immediately. DELETE. .5. to view a specific date table. DEFINE.CA-SCHEDULER 9. .7 Datetables CA-Scheduler date tables are used with criteria to determine when schedules and jobs should be added to the workload. Delete. . Option 7 of the CA-Scheduler Database menu displays the Date Table menu. Use option 2. to remove a specific date table. . Use option 4. You may enter a partial date table name in the Date Table field to limit the display. and Year. to display a scrollable list of date tables defined to CA-Scheduler. ALTER. DIRECTORY. . or Copy date tables. OPTION ===> Datetable . Use option 5. Use option 6. COPY. Criteria keywords such as WDAY and HDAY (workday and holiday) are resolved by inspecting the specified day in the date table.7 Datetables 5. From the list you may Select (display). ------------------. to copy a date table. you must enter the Date Table. to create a new date table. . CA-Scheduler displays a panel asking you to confirm the deletion. “Options”). . If you have requested the Delete Confirmation option (See Chapter 3. Otherwise. 5-100 Online Guide . DISPLAY. Use option 3. Accounting Code . 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. For options 2 to 6. . Use option 1. . to edit a specific date table. creating a new one. . Edit. Year . . Accounting Code.

7. CA-Scheduler only reads the first 50 date tables before displaying the list. more rows are automatically added until the entire list has been built. 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 Chapter 5.1 Directory ------------------.CA-SCHEDULER 9. Database 5-101 . Select a date table by entering a letter to the left of the date table. COMMAND ===> Name Code -------. The upper right-hand corner of the panel displays the current range of rows and the total number of rows.7 Datetables 5. As you scroll down.---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.5.

COMMAND ===> Define Datetable: Datetable . . . The following panel is displayed only when creating a new date table. . . . . . . . MON (SUN to SAT) Enter END to Exit.7 Datetables 5. . Workdays per Week First Workday . xxyy (SCHD) DATETABLE ------------------- . . . Size/Type: Required: 4 numeric characters Yes 5-102 Online Guide . Size/Type: Required: Default: 1 alphanumeric character No A Year The four-digit year of this date table. .2 Date Table Definition Date tables may only be maintained online. . Year .CA-SCHEDULER 9. -------------------. 5 ( to 7) . . . . The Accounting Code must be a letter.7. Size/Type: Required: 1 to 7 alphanumeric characters Yes Accounting Code The one character prefix used by criteria keywords that should reference this table.5. The fields are: Datetable The name of the date table being maintained. Accounting Code .

CA-SCHEDULER 9. To exit and save your changes.. Other than the panel shown above. Legend: W. 3 WA.. Description . JANUARY 2 xx Thursday --------2 WA. . -------------------.. WA. 15 WA. . change this field to SUN. 16 WA. 24 WA.... THU... Size/Type: Required: 1 numeric character from 0 to 7 Yes First Workday The first day in a "normal" work week. 31 WAM. 23 WA.. which defaults to Monday.... WA.. Saturday --------4 .5.. . To exit without saving your changes. 8 WA. WA... 17 WA. Friday --------3 WA.. UP for previous month. 18 ..M. . To define a work week that starts on Sunday.7 Datetables Workdays per Week The number of days in a "normal" work week. 9 WA. which is used only when a date table is defined.. . 22 WA. type CAN on the command line.... Wednesday --------1 WA. 29 WA. 11 ... WA. A typical work week starts on Monday and lasts for five days.. . . Tuesday --------7 14 21 28 WA. press PF3.. WA. or SAT Yes Press Enter to continue defining the date table. WED.. the same panel is used to display. Work weeks start with the day specified in the First Workday field.. Size/Type: Required: SUN.. or DOWN for next month. Monday --------6 13 2 27 WA. 25 . MON.. . 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... ... alter. Use PF7 and PF8 to scroll up and down through the months. FRI..... . 1 WA.. Database 5-103 .... xxyy (SCHD) DATETABLE ------------------- Accounting Code ..Y - Workday Accounting Day Month (Period) End Year End Enter END to exit. or enter the first three characters of a month on the command line...A.. .. . TUE. WA. Chapter 5. .. Sunday --------5 12 19 26 .... and define date tables. . COMMAND ===> Datetable ..

M The day is the last day of an accounting period. This field may not be modified after the date table is defined. along with their attributes. Criteria keywords such as ADOYx are counted from this day. Criteria keywords such as WDAY and WDOMx will be true. The Accounting Code must be a letter. Criteria keywords such as xDAY.7 Datetables The fields are: Datetable The name of the date table being manipulated. 5-104 Online Guide .5. Y The day is the last day of the accounting year. Size/Type: Required: Default: 1 alphanumeric character No A Description May be used to describe the date table or its purpose. are true. criteria keywords such as HDAY are true. where x is the Accounting Code. Each day may have up to four attributes: W The day is a workday. If the W attribute is not present. Size/Type: Required: 1 to 40 alphanumeric characters No 1 to 31 The days of the month. not the value of the Accounting Code. A The day is an accounting day. Note that the attribute for the day is always A. Criteria keywords such as ADOMx are counted from this day. Size/Type: Required: 1 to 7 alphanumeric characters Yes Accounting Code The one character prefix used by criteria keywords that should reference this table. This is frequently used to indicate the end of the month.

3 Copying a Date Table ----------------. COMMAND ===> Copy datetable accounting code year To Datetable Accounting Code Year xxyy (SCHD) COPY DATETABLE ----------------- Enter END to exit.7.CA-SCHEDULER 9. Chapter 5.5.7 Datetables 5. The date table you selected is listed in the Copy date table fields. Database 5-105 . Enter the new date table information in the To Datetable fields.

Otherwise. 1 2 3 4 5 6 . DIRECTORY. -----------------. Use option 3. DEFINE. . DELETE. You may enter a full or partial key. “Options”). Job. See below. OPTION ===> Key . CA-Scheduler displays a panel asking you to confirm the deletion. . Use option 4. From the list you may Select (display). Job . . If you have requested the Delete Confirmation option (See Chapter 3. Schedule.8 Documentation Documentation is text entered by your site that may or may not be associated with a job. . CA-Scheduler deletes the documentation member immediately. to view a specific documentation member. job and/or schedule name to limit the display. Use option 6. . . Job Number.8 Documentation 5. Use option 2. to copy a documentation member. Edit.5. . 5-106 Online Guide . - 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. Delete. . and Schedule. Text associated with a job is displayed on the OS/390 console at a specific time or when the job's schedule starts. to remove a specific documentation member. Use option 5.CA-SCHEDULER 9. DISPLAY. For options 2 to 6. . . Option 8 of the CA-Scheduler Database menu displays the Documentation menu. ALTER. Station. . to create a new documentation member. Job Number. creating a new one. to display a scrollable list of documentation members defined to CA-Scheduler. . COPY. to edit a specific documentation member. or Copy documentation members. Station . See Documentation Display Key and Display Time fields on page 5-39. Use option 1. you must enter the Key.

Size/Type: Required: 2 numeric characters Yes. Size/Type: Required: Job If the documentation member is to be displayed on the OS/390 console. Size/Type: Required: 1 to 8 alphanumeric characters No 1 to 8 alphanumeric characters Yes Job Number The number of the associated job.5. if Job is used Station The station of the associated job. Size/Type: Required: 2 numeric characters Yes. Size/Type: Required: 1 to 8 alphanumeric characters Yes. Database 5-107 . it must be defined with the name of the job with which it is associated. if Job is used Chapter 5.8 Documentation The fields on the panel are: Key The documentation key. Every documentation member must have a key. if Job is used Schedule The schedule of the associated job.

53 12.49. When displaying a member. Select a documentation member by entering a letter to the left of the key.19 1 .55.55.19 13.55.8 Documentation 5. 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 1 CHRIS Time -------8. ISPF Browse is used.1 8. 5-108 Online Guide . 8 7. 9 14.19 1 .18 1 . As you scroll down.47.19 1 .1 Directory -----------------.28 1 .13.43.19 1 . The upper right-hand corner of the panel displays the current range of rows and the total number of rows.49.19 1 . CA-Scheduler only reads the first 50 documentation members before displaying the list.12.19 Each documentation member is displayed on a single row.55.CA-SCHEDULER 9.12.55.28 15.5.2 Documentation Text When defining or editing a documentation member.39. ISPF Edit is used.8.55.52.49.19 1 . 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.31 9. more rows are automatically added until the entire list has been built. 1 13.55.51 7.55.8.

COMMAND ===> Copy doc job number station schedule To doc job number station schedule xxyy (SCHD) COPY DOCUMENTATION --------------- Enter END to exit. Chapter 5. The documentation member you selected is listed in the Copy doc fields.5.8 Documentation 5.8.3 Copying a Documentation Member --------------. Database 5-109 .CA-SCHEDULER 9. Enter the new member information in the To doc fields.

to display a scrollable list of flows. Edit. DELETE. to remove a specific flow. “Options”).9 Flows A flow identifies the starting and ending job of a job stream to be tracked by the Critical Path Monitor (CPM) system. Use option 5. you must enter the Flow field. the flow is deleted immediately. If you have requested the Delete Confirmation option (see Chapter 3. Use option 3. 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. OPTION ===> Flow . From the list you may Select (display). Use option 4. . REFRESH. CA-Scheduler must be active for the command to work. Option 9 of the CA-Scheduler Database menu displays the Flows menu. Use option 6. . You may enter a partial flow name in the Flow field to limit the display. to edit an existing flow. Otherwise. to create a new flow. to issue a REFRESH FLOW command to the CA-Scheduler started task. ALTER. ---------------------. .9 Flows 5. 5-110 Online Guide .5. and Delete flows.CA-SCHEDULER 9. Use option 1. DEFINE. Use option 2. For options 2 to 5. DIRECTORY. . then a panel is displayed asking you to confirm the deletion. DISPLAY. to view a specific flow.

To exit without saving your changes.CA-SCHEDULER 9. Database 5-111 . To save your changes and exit. more rows are automatically added until the entire list has been built. 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. use PF3. LIST SCHEDULE). edit.1 Directory ---------------------. CA-Scheduler only reads the first 50 flows before displaying the list. Chapter 5.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.9. The batch utility to use for maintaining flows is CAJUTIL0.9.9 Flows 5. Enter an: S to select a flow for viewing E to edit (alter) a flow D to delete a flow 5. As you scroll down. enter CAN on the command line.2 Flow Definition The same panel is used to display. Select a flow by entering a letter to the left of the flow. The upper right-hand corner of the panel displays the current range of rows and the total number of rows.5. COMMAND ===> Flow -------FLOW1 HOURLY PAYROLL From Job ----------------------FJOB1A 1 4 FLOWSCD1 PAY1 1 4 PAYROLL PAY1 1 4 PAYROLL Bottom xxyy (SCHD) FLOWS ---. and define flows.

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: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Beginning of flow Job The starting job name for this flow. Beginning of Job . . Schedule . xxyy (SCHD) FLOW ---------------------- Service Level Agreement .9 Flows ---------------------. Schedule . flow: . .5. . Station .CA-SCHEDULER 9. 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: 40 Batch Keyword: FSTation 5-112 Online Guide . JNO . (ddhhmm) Enter END to exit. . . COMMAND ===> Flow . . . . . . JNO . . . Station . . . End of flow: Job . The fields are: Flow The name of the flow being manipulated. . . The job must exist before the flow is defined. The field may not be modified after the flow is defined.

If CPM determines that the flow will not end by this time. it considers the flow late. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: FSChd End of flow Job The ending job name 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. Database 5-113 .5. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: TSChd Service Level Agreement The time by which the flow must be complete. The value is in the format of ddhhmm. where dd is the number of autoscans and hhmm is the time. The job must exist before the flow is defined. 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.9 Flows Beginning of flow Schedule The schedule to which the starting job for this flow belongs. Size/Type: 1 to 6 numeric characters in ddhhmm format Required: Yes Batch Keyword: SLA Chapter 5. Leading zeros do not need to be entered. 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.

FST=4 . Autoscan is at 8:00 AM.5.9. SLA=5 5-114 Online Guide .9 Flows 5. TJOB=OVERTIME.TST=4 .3 Example Define a flow from PAY1-01 40 PAYROLL to OVERTIME-01 40 HOURLY that must complete by 5:00 AM.FSCHD=PAYROLL.FJNO= 1.TSCHD=HOURLY.TJNO= 1. //stepname EXEC CAJUTIL //SYSIN DD DEFINE FLOW NAME=PAYROLL.FJOB=PAY1.

a panel is displayed asking you to confirm the deletion. Use option 3. If you have requested the Delete Confirmation option (see Chapter 3. OPTION ===> Virtual Resource . to issue a REFRESH VRM command to the CA-Scheduler started task. to edit an existing virtual resource. to remove a virtual resource. to view a specific virtual resource.5. DELETE. ALTER. the virtual resource is deleted immediately. A virtual resource must be defined. For options 2 to 5. then associated with one or more jobs. . and Delete virtual resources. Chapter 5. to display a scrollable list of virtual resources. From the list you may Select (display). 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. Otherwise. CA-Scheduler must be active for the command to work. to create a new virtual resource. Use option 2. REFRESH. Use option 6. Virtual resources only exist in the CA-Scheduler task.10 Virtual Resources A virtual resource may be used to prevent jobs from being submitted unless certain conditions are met. DEFINE. you must enter the Virtual Resource field. DIRECTORY. . Edit. DISPLAY. Database 5-115 . Use option 4. ---------------. Use option 5. You may also display a list of jobs associated with a virtual resource.10 Virtual Resources 5.CA-SCHEDULER 9. You may enter a partial resource name in the Virtual Resource field to limit the display. Use option 1. Option A of the CA-Scheduler Database menu displays the VRM menu. “Options”).

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. 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 .-----------XXX SIMPLE YYY ENQ ZZZ COUNT 5 Bottom of data Each virtual resource is displayed on a single row. COMMAND ===> xxyy (SCHD) VRM ----.CA-SCHEDULER 9.Row 1 to 3 of 3 SCROLL ===> CSR _ _ _ Resource Type Count -----------------------------.5. more rows are automatically added until the entire list has been built. As you scroll down.10.1 Directory ----------------------.-----.10 Virtual Resources 5. Select a virtual resource by entering a letter to the left of the virtual resource.

10 Virtual Resources 5. Count.2 Virtual Resource Definition The same panel is used to display. edit. . enter CAN on the command line. .5. ---------------. 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. . Size/Type: 1 to 30 alphanumeric characters Required: Yes Batch Keyword: Resource Chapter 5. LIST SCHEDULE). xxyy (SCHD) VIRTUAL RESOURCE ---------------- Resource Type . .CA-SCHEDULER 9. (Enq. The fields are: Resource The name of the virtual resource being manipulated. To save your changes and exit.10. or Simple) (Only if resource type is Count) Enter END to exit. . To exit without saving your changes. and define virtual resources. . COMMAND ===> Resource . . Database 5-117 . The batch utility to use for maintaining virtual resources is CAJUTIL0. Maximum Count . use PF3. .

2.10.5.TYPE=SIMPLE 5-118 Online Guide . Valid values are ENQ.1 Example Define a simple virtual resource to indicate if CICS is up or down: //stepname EXEC CAJUTIL //SYSIN DD DEFINE VRM NAME=CICS. then the Maximum Count field contains the number of the virtual resource available. COUNT. Size/Type: ENQ.10 Virtual Resources Resource Type The type of the virtual resource being manipulated. COUNT. See the usage notes below for more information. if Resource Type = COUNT Batch Keyword: Count 5. or SIMPLE Required: Yes Batch Keyword: Type Maximum Count If Resource Type is set to COUNT. and SIMPLE. The resource type may not be changed once the virtual resource has been defined. Size/Type: 1 to 10 numeric characters Required: Yes.

-------------------.10. more rows are automatically added until the entire list has been built. As you scroll down.1.CA-SCHEDULER 9.5. See 5.3 VRM Job List The VRM Job List dialog displays all of the jobs associated with a particular virtual resource.10. Database 5-119 . CA-Scheduler only reads the first 50 job/virtual resource associations before displaying the list. COMMAND ===> xxyy (SCHD) VRM JOBS . Select a job/virtual resource association by entering a letter to the left of the job. To display the list. The upper right-hand corner of the panel displays the current range of rows and the total number of rows. enter a J next to a virtual resource on the virtual resource directory display. “Directory” on page 5-116.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.10 Virtual Resources 5. 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 Chapter 5.

Schedule . . . The batch commands are: Alter (Edit) Define Delete Display ALTER JOBRES DEFINE JOBRES DELETE JOBRES LIST JOB --------------------. use PF3.10 Virtual Resources 5. To exit without saving your changes.5. (ACTIVE or INACTIVE) Enter END to Exit.4 Job/VRM Association The same panel is used to display. . . INACTIVE Termination: Release on abend/fail . . .10. . The fields are: Name The name of the job being associated with a virtual resource. COMMAND ===> Name . NO Number . Required Status: Status . . and define job/virtual resource associations. . . To save your changes and exit.CA-SCHEDULER 9. xxyy (SCHD) JOB VRM -------------------Station . edit. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name 5-120 Online Guide . The batch utility to use for maintaining job/virtual resource associations is CAJUTIL0. . enter CAN on the command line. . Virtual Resource: Resource . .

10 Virtual Resources JNO The JNO of the job being associated with a virtual resource.999. 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. No check is made to ensure that the number entered here is less than or equal to the number available on the virtual resource. Database 5-121 .999. or needs exclusive control of the 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. then the label will read Count. Valid values are any number from 1 to 9.5. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Schedule Resource The virtual resource being associated with this job. Valid values are SHR and EXC. Size/Type: 1 to 10 numeric characters Required: Yes Batch Keyword: Count Chapter 5. Size/Type: SHR or EXC Required: Yes Batch Keyword: Enq If the virtual resource was defined as TYPE=COUNT. Size/Type: 2 numeric characters Required: No Batch Keyword: STation Default: 40 Schedule The schedule of the job being associated with a virtual resource.999. If the virtual resource was defined as TYPE=ENQ. then the label will read Enqueue. indicating that the job may share the virtual resource with other jobs.

2 Usage Notes Virtual resources may be used to control or limit job submission.S=SCHDA. even if the job abends or fails.5.4. Use the DISPLAY VRM command to view which jobs currently have or are waiting for each virtual resource. Each virtual resource must be obtained before the next virtual resource is considered. //stepname EXEC CAJUTIL //SYSIN DD DEFINE JOBRES NAME=JOBA. Note: Virtual resources are known only to CA-Scheduler.4.RESOURCE=CICS. Virtual resources are resolved alphabetically.1 Example Specify that a job may not be submitted unless a simple virtual resource called CICS is ACTIVE. then the label reads Status. Size/Type: ACTIVE or INACTIVE Required: Yes Batch Keyword: Active=YES|NO Release on abend/fail Virtual resources.10. ENQ. The REFRESH VRM command must be used (or wait for an autoscan) to pick up any definition changes to the virtual resources. All of the virtual resources must be satisfied before the job is submitted. are usually retained until the job completes successfully.STATUS=ACTIVE 5. The three types of virtual resources. A job may have any number of virtual resources associated with it. once acquired by a job. and SIMPLE. Virtual resources are obtained in a first-come. 5-122 Online Guide . Size/Type: YES or NO Required: No Batch Keyword: Free Default: NO 5. are discussed in the following sections. indicating that the virtual resource must be active or inactive before the job may be submitted. COUNT. first-served manner.10. specify YES.10 Virtual Resources If the virtual resource was defined as TYPE=SIMPLE. Valid values are ACTIVE and INACTIVE. To release the virtual resource at any job end.

RESOURCE=X. JOBE will be submitted. jobs JOBA.5.3 ENQ Virtual Resources A job may share an ENQ virtual resource with other jobs.RESOURCE=X. Once jobs JOBA and JOBB complete.RESOURCE=X. Database 5-123 .TYPE=ENQ DEFINE JOBRES NAME=JOBA.ENQ=SHR DEFINE JOBRES NAME=JOBC. then they will be able to obtain the virtual resource.10. it must wait.S=SCHDB. because it can not obtain exclusive control of the virtual resource.ENQ=SHR DEFINE JOBRES NAME=JOBD.RESOURCE=X. Chapter 5. This could be defined like this: //stepname EXEC CAJUTIL //SYSIN DD DEFINE VRM NAME=X. JOBB.ENQ=EXC If jobs JOBA and JOBB are the first jobs ready to be submitted.RESOURCE=X.10 Virtual Resources 5. JOBC. For example. Note: An OS/390 ENQ is never issued for ENQ virtual resources.4. Once JOBE completes.S=SCHDC.S=SCHDD. or may require exclusive control of the virtual resource. JOBE requires exclusive control of X.S=SCHDE. If job JOBE is the next job ready to be submitted.S=SCHDA.ENQ=SHR DEFINE JOBRES NAME=JOBE. and JOBD all share the virtual resource X.ENQ=SHR DEFINE JOBRES NAME=JOBB. they must also wait because an exclusive use of the virtual resource is pending. jobs JOBC and JOBD will be submitted. When jobs JOBC and JOBD are ready to be submitted.

TYPE=SIMPLE DEFINE JOBRES NAME=JOBA.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.COUNT=1 DEFINE JOBRES NAME=JOBC. and JOBD may be submitted at the same time. however.RESOURCE=Y.S=SCHDA. JOBB.4 Count Virtual Resources When virtual resources are defined with a type of COUNT.COUNT=3 Any three of the jobs JOBA. can only be submitted when no other job has the virtual resource. a number is specified indicating how many of the virtual resources this job requires. the resource will also be given to JOBD.RESOURCE=Y. and JOBD becomes available to be submitted.S=SCHDA.S=SCHDE.COUNT=1 DEFINE JOBRES NAME=JOBD.S=SCHDB. //stepname EXEC CAJUTIL //SYSIN DD DEFINE VRM NAME=Z. JOBC.4.STATUS=ACTIVE 5-124 Online Guide . Consider the following example: //stepname EXEC CAJUTIL //SYSIN DD DEFINE VRM NAME=Y.4. When a job is associated with this virtual resource.10.RESOURCE=Z.COUNT=1 DEFINE JOBRES NAME=JOBE.TYPE=COUNT.RESOURCE=Z. a number is specified indicating how many of the virtual resources are available.10.RESOURCE=Y. JOBE. Note that the order of requests for a count type virtual resource does not matter.COUNT=1 DEFINE JOBRES NAME=JOBB.COUNT=3 DEFINE JOBRES NAME=JOBA.ACTIVE=YES DEFINE JOBRES NAME=JOBB.RESOURCE=Y.ACTIVE=NO //stepname EXEC CAJUCMD <tab> //SYSIN DD SC VARY VRM RESOURCE=Z. 5.5.RESOURCE=Y.10 Virtual Resources 5. If JOBE was already waiting for this resource because JOBA already has the resource.S=SCHDD.S=SCHDC.S=SCHDB.

DATETRAN. AUDIT. to list jobs from CA-Scheduler's history information that abended.6. Use option 1.Chapter 6. “Report Audit” on page 6-10 for more information. See 6. | | Use option 3. See 6. “Report Abend” on page 6-8 for more information. ANALYZE. to list CA-Scheduler commands that have been issued and saved in the audit trail. Use option 7. See 6. Chapter 6. JOB AVERAGE.CA-SCHEDULER 9. Reports 6-1 . to inspect schedules and jobs for logical errors. Use option 4. such as predecessor loops (deadlocks). to generate a list of criteria keywords that are true for a specified date.5. COMPLETE. See 6.2. to list jobs from CA-Scheduler's history information that have completed. Use option 2. “Analyze” on page 6-3 for more information.3. “Report Datetran” on page 6-14 for more information. to list average execution times for jobs in CA-Scheduler's history. “Job Average” on page 6-16 for more information.1. See 6. ABEND. Reports Option 3 of the CA-Scheduler main menu displays the reports menu.4. 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 5. See 6. “Report Complete” on page 6-12 for more information.

“Predecessors” on page 6-30 for more information.Use option 8. “Successors” on page 6-21 for more information. Use option 12.11. See 6. PREDECESSOR. “Job History” on page 6-17 for more information.7. SUCCESSOR. to show predecessors to a given job or schedule. “Report Options” on page 6-20 for more information. to list events (such as job start and end) that have been written to the mailbox. 6-2 Online Guide .9. See 6. Use option 11. to show successors to a given job or schedule. | | Use option 9. MAILBOX. Use option 10. OPTIONS. to display all CA-Scheduler installation options.8. See 6.10. See 6. JOB HISTORY. “Report Mailbox” on page 6-18 for more information. to list up to the last seven executions of jobs in CA-Scheduler's history. See 6.

--------------------. “Analyze Schedule” on page 6-6 for more information.6.2.Analyze a Schedule xxyy (SCHD) ANALYZE -------------------- Enter END to exit. JOB. SCHEDULE. All jobs in the selected schedules are also analyzed. Use option 2.1 Analyze Option 1 of the CA-Scheduler Reports menu displays the Analyze menu. The Analyze commands inspect jobs and schedules for logical errors. See the next topic for more information. Reports 6-3 . to inspect a specific job or jobs starting with the same prefix. OPTION ===> 1 2 JOB . to inspect a specific schedule or schedules with the same prefix.Analyze a Job SCHEDULE . See 6.1.1 Analyze 6.CA-SCHEDULER 9. such as predecessor loops (deadlocks). Chapter 6. Use option 1.

Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: * (All schedules) 6-4 Online Guide . . NO. ERR Date . . .1 Analyze 6. Options: List . ------------------. The batch command is ANALYZE JOB.6. 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. . COMMAND ===> Job: Job Name . Schedule . . . .1. . . All job numbers and stations for selected jobs will be analyzed. The Analyze Job command inspects one or more jobs for logical errors.1 Analyze Job Option 1 of the CA-Scheduler Analyze menu displays the Analyze Job dialog. DEADLOCK) (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) Enter END to exit. . The batch utility to use is CAJUTIL0. such as predecessor loops (deadlocks). xxyy (SCHD) ANALYZE JOB ------------------ (YES. . .CA-SCHEDULER 9. The fields are: Job Name The name of the job or job name prefix to be inspected. . . ERR. . A job name prefix may be specified by following the prefix with an asterisk. .

1 Analyze List Determines the amount of information produced by the report. See Chapter 3. ERR Only jobs with errors are displayed. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: Date Default: Blank Chapter 6. The default value is determined by the Default Analyze List Type option. “Options” on page 3-1. If Date is not specified.6. along with any errors. Deadlocks will only be reported if autoscan would have detected them. Required: No Batch Keyword: List Default: YES Date If a date is entered. regardless of their individual criterias. Valid values are: YES All information about analyzed jobs is displayed. all schedules and jobs are considered selected. NO Only job names are displayed. DEADLOCK Only deadlocks and the deadlock path are displayed. ANALYZE will emulate autoscan for that date. Reports 6-5 .

COMMAND ===> Schedule: Schedule Name . . . xxyy (SCHD) ANALYZE SCHEDULE ---------------- (YES. 6-6 Online Guide . 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. “Options” on page 3-1. .1 Analyze 6. NO Only schedule and job names are displayed. ERR Date . ---------------. Specify a schedule prefix by following the prefix with an asterisk. . . . DEADLOCK) (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) Enter END to exit. . . along with any errors. The default value is determined by the Default Analyze List Type option. Options: List . . The batch utility to use is CAJUTIL0.CA-SCHEDULER 9. All jobs in the selected schedules are also inspected. Valid values are: YES All information about analyzed schedules and jobs is displayed.2 Analyze Schedule Option 2 of the CA-Scheduler Analyze menu displays the Analyze Schedule dialog. .1. . See Chapter 3. The fields are: Schedule The name of the schedule or schedule prefix to be inspected. such as predecessor loops (deadlocks). The batch command is ANALYZE SCHEDULE. The Analyze Schedule command inspects one or more schedules for logical errors. ERR.6. NO.

all schedules and jobs are considered selected.1 Analyze ERR Only schedules and jobs with errors are displayed.6. Reports 6-7 . DEADLOCK Only deadlocks and the deadlock path are displayed. If you do not specify a date. ANALYZE emulates autoscan for that date. Required: No Batch Keyword: List Default: YES Date If you enter a date. Deadlocks are reported only if autoscan would have detected them. regardless of their individual criterias. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: Date Default: Blank Chapter 6.

Schedule . . . Scheduled On . . . Specify a name prefix by following the prefix with an asterisk. .2 Report Abend Option 2 of the CA-Scheduler Reports menu displays the Report Abend dialog. The batch utility to use is CAJUTIL0. . . .6. . Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Job Default: * (All jobs) 6-8 Online Guide . . . CA-Scheduler lists all job numbers of selected jobs. COMMAND ===> Job: Job Name . . . The batch command is REPORT ABEND. Options: Starting Date Starting Time Duration .CA-SCHEDULER 9. . . which lists abended jobs in the current workload. The fields are: Job Name The name or name prefix of the job for which historical abends should be listed. . .2 Report Abend 6. . Do not confuse the Report Abend command with the Status Abend command. -----------------. The Report Abend command lists jobs in CA-Scheduler history information that ended abnormally. xxyy (SCHD) REPORT ABEND ------------------ (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) (hhmm) (days) (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) Enter END to exit.

Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule Default: * (All schedules) Starting Date If entered. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: FROMDate or FD Default: Current autoscan date Starting Time If entered. CA-Scheduler ignores 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.6. lists no abends occurring prior to this time. If you specify Scheduled on. Reports 6-9 . Specify a name prefix by following the prefix with an asterisk. Size/Type: hhmm Required: No Batch Keyword: FROMTime or FT Default: Normal autoscan time Duration If entered. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: SDATE Chapter 6. lists no abends occurring prior to this date.2 Report Abend Schedule The name or name prefix of the schedule that contains the Job Name. lists no abends occurring at least this many days after the Starting Date.

. RUN. . . xxyy (SCHD) REPORT AUDIT ------------------ Users . . . . . . . . . The batch command is REPORT AUDIT. -----------------. . . . . . . . . . . . . . . . . . . . . .CA-SCHEDULER 9. . . COMMAND ===> Options: Starting Date Starting Time Ending Date . . The batch utility to use is CAJUTIL0. . CA-Scheduler displays only commands recorded in the audit trail. . . (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) (hhmm) (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) (hhmm) .3 Report Audit 6. and so on) are normally not recorded to the audit trail. | | | | | | The Report Audit command lists CA-Scheduler commands issued and recorded in the audit trail. . .3 Report Audit Option 3 of the CA-Scheduler Reports menu displays the Report Audit dialog. . Information in the audit trail is kept until deleted by the DELETE AUDIT command. . . Typically. . . . ANALYZE. and so on) commands are saved. . The fields are: Starting Date The earliest date from which commands should be displayed. .6. . . . . only update (DEFINE. . . Display commands (REPORT. . . . Ending Time . . Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: FD Default: Today's date 6-10 Online Guide . . . . . . . Enter END to exit. . . . Commands . . .

. 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: USER=(userid.. Size/Type: hhmm Required: No Batch Keyword: TT Default: 2359 Commands If specified. Size/Type: One to sixteen 1 to 8 alphanumeric characters Required: No Batch Keyword: CMD=(command. Reports 6-11 . 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. only commands entered by one of the sixteen users listed are displayed...3 Report Audit Starting Time The earliest time on the Starting Date from which commands should be displayed.) Default: All commands Users If specified. Size/Type: hhmm Required: No Batch Keyword: FT Default: Midnight Ending Date The latest date from which commands should be displayed.command.userid..6.) Default: All users Chapter 6.

. COMMAND ===> Job: Job Name .4 Report Complete Option 4 of the CA-Scheduler Reports menu displays the Report Complete dialog. 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. The batch utility to use is CAJUTIL0. ----------------. . Scheduled On . . . . . The Report Complete command lists jobs in CA-Scheduler history information that ended normally. . xxyy (SCHD) REPORT COMPLETE ---------------- (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) (hhmm) (days) (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) Enter END to exit. . . . . .6. . . Size/Type: 1 to 8 alphanumeric characters Required: No Batch Keyword: Job Default: * (All jobs) 6-12 Online Guide . Options: Starting Date Starting Time Duration .4 Report Complete 6.CA-SCHEDULER 9. CA-Scheduler lists all job numbers and stations of selected jobs. which lists completed jobs in the current workload. . The batch command is REPORT COMPLETE. . Schedule . Do not confuse the Report Complete command with the Status Comp command.

lists no completions occurring at least this many days after the Starting Date.6. 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. Size/Type: hhmm Required: No Batch Keyword: FROMTime or FT Default: Normal autoscan time Duration If entered. Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: FOR Default: 1 Scheduled on Lists only completed jobs selected on this date. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: SDATE Chapter 6. lists no completions occurring prior to this date. Reports 6-13 .4 Report Complete Schedule The name or name prefix of the schedule that contains the Job Name. lists no completions occurring prior to this time. If you specify Scheduled on. CA-Scheduler ignores Starting Date. Size/Type: mmddyy ddmmyy mmddyyyy ddmmyyyy Required: No Batch Keyword: FROMDate or FD Default: Current autoscan date Starting Time If entered.

COMMAND ===> Date Table: Date Table . . Size/Type: 1 to 7 alphanumeric characters Required: No Batch Keyword: Table Default: CAIJGEN DATETAB value 6-14 Online Guide . . ----------------. . .5 Report Datetran Option 5 of the CA-Scheduler Reports menu displays the Report Datetran dialog. . Options: Starting Date . The batch utility to use is CAJUTIL0. xxyy (SCHD) REPORT DATETRAN ---------------- (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) (days) Enter END to exit. . CA-Scheduler ignores In Schedule and In Job.CA-SCHEDULER 9. The Report Datetran command lists criteria keywords that are true for a specified date. If you specify Date Table. CA-Scheduler uses the default Date Table (CAIJGEN DATETAB option). If the Date Table. The batch command is REPORT DATETRAN. In Schedule. . .5 Report Datetran 6. The fields are: Date Table The name of the date table to use in generating criteria keywords. In Schedule . In Job . . . .6. and In Job fields are blank. . Duration . .

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. 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. CA-Scheduler ignores In Job. CA-Scheduler ignores In Schedule. Reports 6-15 . Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: FOR Default: 1 Chapter 6.5 Report Datetran In Schedule Use the date table specified in this schedule. If you specify either Date Table or In Schedule. If you specify In Schedule.6. 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. If you specify Date Table.

. ------------------. The field is: Job Name The name or name prefix of the job for which average execution information should be displayed.6 Job Average 6. . Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Default: * (All jobs) 6-16 Online Guide . Specify a name prefix by entering an asterisk after the prefix. The list includes all job numbers and stations for selected jobs. xxyy (SCHD) JOB AVERAGE ------------------ Enter END to exit. .CA-SCHEDULER 9. The Job Average command displays average execution time for jobs based on CA-Scheduler historical information.6. The batch command is REPORT JOBAVG. The batch utility to use is CAJUTIL0. COMMAND ===> Job: Job Name .6 Job Average Option 7 of the CA-Scheduler Reports menu displays the Job Average dialog.

. JESNUM xxyy (SCHD) JOB HISTORY ------------------ (Jesnum or Year) Enter END to exit. . . Size/Type: JESNUM or YEAR Required: No Batch Keyword: List Default: JESNUM Chapter 6. . The JES job number is not displayed. Dates are displayed as MM/DD. The Job History command lists information about up to seven previous executions of jobs. Reports 6-17 .7 Job History Option 8 of the CA-Scheduler Reports menu displays the Job History dialog. The batch command is REPORT JOBHIST. COMMAND ===> Job: Job Name . Specify a name prefix by entering an asterisk after the prefix.6.CA-SCHEDULER 9. Options: List . 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. Specify YEAR to display dates as MM/DD/YY. ------------------. The fields are: Job Name The name or name prefix of the jobs for which execution history should be displayed. The batch utility to use is CAJUTIL0.7 Job History 6. .

. 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. COMMAND ===> Options: Starting Date Starting Time Ending Date . . . Jobs . . .8 Report Mailbox 6. . . . . . . . Enter END to exit. . .6. . . submit fail. . . . . . . 6-18 Online Guide . . . . . . . . . . . . . Only events that are issued for the MAILBOX report are displayed. . .CA-SCHEDULER 9. . . the following events are available: ■ Job and Schedule starts ■ Job and Schedule completions ■ Jobs and Schedules being marked late ■ Job failures (JCL error. . . . . The batch command is REPORT MAILBOX. . . . . Ending Time . . . (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) (hhmm) (mmddyy/mmddyyyy/ddmmyy/ddmmyyyy) (hhmm) . . . . . . Typically. . . . . . .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. ----------------. The batch utility to use is CAJUTIL0. . . . . xxyy (SCHD) REPORT MAILBOX ----------------- Schedules . . . . . . .

.6. Size/Type: One to sixteen 1 to 8 alphanumeric characters Required: No Batch Keyword: Schedule=(schedule. 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.8 Report Mailbox The fields are: Starting Date The earliest date for which events should be displayed. only events for these sixteen jobs are displayed. Reports 6-19 .) Default: All schedules Chapter 6. Size/Type: hhmm Required: No Batch Keyword: FT Default: Midnight Ending Date The latest date for which events should be displayed. Size/Type: hhmm Required: No Batch Keyword: TT Default: 2359 Jobs If specified.jobname.....) Default: All jobs Schedules If specified. Size/Type: One to sixteen 1 to 8 alphanumeric characters Required: No Batch Keyword: Job=(jobname. 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..schedule. only events for these sixteen schedules or for jobs in these schedules are displayed.

The batch command is REPORT OPTIONS. Since the command has no keywords. The batch utility to use is CAJUTIL0. The Report Options command displays all of the CA-Scheduler installation options currently set.9 Report Options Option 10 of the CA-Scheduler Reports menu issues the Report Options command.9 Report Options 6.6. 6-20 Online Guide . a prompting panel is not displayed.

10. Reports 6-21 .2. See 6.10 Successors 6. The Successor menu lists successors of jobs and schedules. See the next topic for more information. SCDCHAIN. JOBCHAIN. to generate a list of successors defined to a specific schedule in the database. Use option 3. “Cscdchan” on page 6-28 for more information. “Scdchain” on page 6-24 for more information. Use option 1. -------------------. to generate a list of successors in the current workload to a specific schedule.6.10. 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. to generate a list of successors in the current workload to a specific job. See 6.3. CJOBCHAN. to generate a list of successors defined to a specific job in the database.10. “Cjobchan” on page 6-26 for more information. Chapter 6. Use option 2.4.10 Successors Option 11 of the CA-Scheduler Reports menu displays the Successor menu. Use option 4. CSCDCHAN.CA-SCHEDULER 9. See 6.

. The batch command is REPORT JOBCHAIN. . .6. . Enter END to exit.10 Successors 6. . . . . 4 . -------------------. xxyy (SCHD) JOBCHAIN -------------------- Options: Level . . . YES Date . The fields are: Job Name The job from which the successor list should start. . . . . . Station Schedule . COMMAND ===> Job: Job Name Number . . The batch utility to use is CAJUTIL0. 1 . Repeat .10. . . The Jobchain command lists successors of a specific job as defined in the CA-Scheduler database. .1 Jobchain Option 1 of the CA-Scheduler Successor menu displays the Jobchain dialog. . . . .CA-SCHEDULER 9. 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 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: STation Default: 40 6-22 Online Guide . . .

or AUTOS Required: No Batch Keyword: Date Chapter 6.6. Size/Type: 1 to 6 numeric character date. For example. specifying NO for REPEAT will only display JOBD's successors once. For example. 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. and JOBB's successor is JOBC. and JOBB's and JOBC's successor is JOBD.10 Successors Schedule The schedule of the starting job. TODAY. Size/Type: Yes or no Required: No Batch Keyword: Repeat Default: YES Date If entered. if JOBA's successors are JOBB and JOBC. Reports 6-23 . if JOBA's successor is JOBB. 1 to 8 numeric character date. only successors selected on the specified date are shown. two levels are required to reach JOBC. 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.

10 Successors 6. Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: Level Default: All successors 6-24 Online Guide . . For example. . . . . The Scdchain command lists successors of a specific schedule as defined in the CA-Scheduler database. Options: Level . .10. . COMMAND ===> Schedule: Schedule .2 Scdchain Option 2 of the CA-Scheduler Successor menu displays the Scdchain dialog. The fields are: Schedule The name of the starting schedule.CA-SCHEDULER 9. . . xxyy (SCHD) SCDCHAIN -------------------- Enter END to exit. .6. The batch utility to use is CAJUTIL0. if JOBA's successor is JOBB. The batch command is REPORT SCDCHAIN. . two levels are required to reach JOBC. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Schedule Level How many levels deep the successor report should go. and JOBB's successor is JOBC. -------------------. . . YES Date . . . Repeat . .

and JOBB's and JOBC's successor is JOBD.6. specifying NO for REPEAT will only display JOBD's successors once. 1 to 8 numeric character date. Reports 6-25 . only successors selected on the specified date are shown. For example. if JOBA's successors are JOBB and JOBC. or AUTOS Required: No Batch Keyword: Date Chapter 6. Size/Type: 1 to 6 numeric character date. Size/Type: Yes or no Required: No Batch Keyword: Repeat Default: Yes Date If entered. TODAY.10 Successors Repeat Specify NO to prevent already displayed successors from displaying again when multiple successor paths reach the same point.

Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JNO Default: 01 Station The station of the starting job. . . . xxyy (SCHD) CJOBCHAN -------------------- Options: Level . COMMAND ===> Job: Job Name Number . Station Schedule . .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 fields are: Job Name The job from which the successor list should start. YES Enter END to exit. . . . . . 4 . .6. . The batch command is REPORT CJOBCHAN. . . . Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The job number of the starting job. . The batch utility to use is CAJUTIL0. -------------------.CA-SCHEDULER 9.10. . Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: STation Default: 40 6-26 Online Guide . Repeat . .10 Successors 6. . . 1 . .

if JOBA's successor is JOBB.6.10 Successors Schedule The schedule of the starting job. 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. and JOBB's and JOBC's successor is JOBD. For example. 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 successors are JOBB and JOBC. specifying NO for REPEAT will only display JOBD's successors once. two levels are required to reach JOBC. Reports 6-27 . Size/Type: Yes or no Required: No Batch Keyword: Repeat Default: Yes Chapter 6. and JOBB's successor is JOBC.

CA-SCHEDULER 9.6. two levels are required to reach JOBC. The batch command is REPORT CSCDCHAN. if JOBA's successor is JOBB. . Repeat . . The batch utility to use is CAJUTIL0. For example. -------------------.4 Cscdchan Option 4 of the CA-Scheduler Successor menu displays the Cscdchan dialog. . . and JOBB's successor is JOBC. The fields are: Schedule The name of the starting schedule.10. Options: Level . . Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: Level Default: All successors 6-28 Online Guide . Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Schedule Level How many levels deep the successor report should go.10 Successors 6. . . . The Cscdchan command lists successors of a specific schedule that is in the current workload. COMMAND ===> Schedule: Schedule Name . . YES xxyy (SCHD) CSCDCHAN -------------------- Enter END to exit. .

For example. Size/Type: Yes or no Required: No Batch Keyword: Repeat Default: Yes Chapter 6.6. specifying NO for REPEAT will only display JOBD's successors once. and JOBB's and JOBC's successor is JOBD. Reports 6-29 .10 Successors Repeat Specify NO to prevent already displayed successors from displaying again when multiple successor paths reach the same point. if JOBA's successors are JOBB and JOBC.

11. JOBRCHAN.2. 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.CA-SCHEDULER 9. to generate a list of predecessors defined to a specific job in the database.6. Use option 3. to generate a list of predecessors defined to a specific schedule in the database. JOBRCHAN. to generate a list of predecessors in the current workload to a specific job.11 Predecessors Option 12 of the CA-Scheduler Reports menu displays the Predecessor menu. The Predecessor menu lists predecessors of jobs and schedules. CSCDRCHN. Use option 4. “Cscdrchn” on page 6-37 for more information.11. 6-30 Online Guide .11 Predecessors 6. See the next topic for more information. “Scdrchan” on page 6-33 for more information.11. See 6. Use option 2. “Cjobrchn” on page 6-35 for more information. Use option 1. See 6.4.3. SCDRCHAN. See 6. to generate a list of predecessors in the current workload to a specific schedule. -----------------.

.1 Jobrchan Option 1 of the CA-Scheduler Predecessor menu displays the Jobrchan dialog. . YES Date . The batch utility to use is CAJUTIL0. . The batch command is REPORT JOBRCHAN.11 Predecessors 6. . . . ------------------. . .CA-SCHEDULER 9. Station Schedule . Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: STation Default: 40 Chapter 6. . . . . Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The job number of the starting job. xxyy (SCHD) JOBRCHAN -------------------- Options: Level . 1 . . . . . Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JNO Default: 01 Station The station of the starting job. The fields are: Job Name The job from which the predecessor list should start. The Jobrchan command lists predecessors of a specific job as defined in the CA-Scheduler database. . 4 . Enter END to exit. . . COMMAND ===> Job: Job Name Number . . Reports 6-31 . .11. . . . . . Repeat .6.

For example. if JOBA's predecessors are JOBB and JOBC. if JOBA's predecessor is JOBB. only predecessors selected on the specified date are shown. 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. 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.6.11 Predecessors Schedule The schedule of the starting job. two levels are required to reach JOBC. and JOBB's and JOBC's predecessor is JOBD. and JOBB's predecessor is JOBC. 1 to 8 numeric character date. Size/Type: Yes or no Required: No Batch Keyword: Repeat Default: YES Date If entered. or AUTOS Required: No Batch Keyword: Date 6-32 Online Guide . TODAY. For example. specifying NO for REPEAT will only display JOBD's predecessors once. Size/Type: 1 to 6 numeric character date.

The batch utility to use is CAJUTIL0.2 Scdrchan Option 2 of the CA-Scheduler Predecessor menu displays the Scdrchan dialog. -------------------. . . Repeat . . two levels are required to reach JOBC. .11. . . . . For example. Reports 6-33 . xxyy (SCHD) SCDRCHAN -------------------- Enter END to exit.11 Predecessors 6. The fields are: Schedule The name of the starting schedule.6. YES Date . . The batch command is REPORT SCDRCHAN. . . Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: Level Default: All predecessors Chapter 6. . and JOBB's predecessor is JOBC. . .CA-SCHEDULER 9. . The Scdrchan command lists predecessors of a specific schedule as defined in the CA-Scheduler database. if JOBA's predecessor is JOBB. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Schedule Level How many levels deep the predecessor report should go. . Options: Level . COMMAND ===> Schedule: Schedule .

For example. specifying NO for REPEAT will only display JOBD's predecessors once. TODAY. or AUTOS Required: No Batch Keyword: Date 6-34 Online Guide . if JOBA's predecessors are JOBB and JOBC.6. Size/Type: 1 to 6 numeric character date.11 Predecessors Repeat Specify NO to prevent already displayed predecessors from displaying again when multiple predecessor paths reach the same point. and JOBB's and JOBC's predecessor is JOBD. only predecessors selected on the specified date are shown. 1 to 8 numeric character date. Size/Type: Yes or no Required: No Batch Keyword: Repeat Default: Yes Date If entered.

Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Name Number The job number of the starting job. The Cjobrchn command lists predecessors of a specific job that is in the current workload. Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: STation Default: 40 Chapter 6. The batch utility to use is CAJUTIL0. . . . . The fields are: Job Name The job from which the predecessor list should start. Options: Level . Reports 6-35 . . The batch command is REPORT CJOBRCHN. . . Size/Type: 1 to 2 numeric characters Required: No Batch Keyword: JNO Default: 01 Station The station of the starting job.11.11 Predecessors 6. . . . YES xxyy (SCHD) CJOBRCHN -------------------- Enter END to exit. -------------------. . COMMAND ===> Schedule: Schedule . Repeat .6.CA-SCHEDULER 9.3 Cjobrchn Option 3 of the CA-Scheduler Predecessor menu displays the Cjobrchn dialog.

specifying NO for REPEAT will only display JOBD's predecessors once. and JOBB's and JOBC's predecessor is JOBD. 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. two levels are required to reach JOBC.11 Predecessors Schedule The schedule of the starting job. if JOBA's predecessor is JOBB. Size/Type: Yes or no Required: No Batch Keyword: Repeat Default: Yes 6-36 Online Guide . if JOBA's predecessors are JOBB and JOBC. and JOBB's predecessor is JOBC. For example. For example. 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.6.

. . . . Repeat . The batch command is REPORT CSCDRCHN. .6. and JOBB's predecessor is JOBC. . Reports 6-37 . . YES xxyy (SCHD) CSCDRCHN -------------------- Enter END to exit. Size/Type: 1 to 3 numeric characters Required: No Batch Keyword: Level Default: All predecessors Chapter 6. For example. . The fields are: Schedule The name of the starting schedule. . if JOBA's predecessor is JOBB.4 Cscdrchn Option 4 of the CA-Scheduler Predecessor menu displays the Cscdrchn dialog. Size/Type: 1 to 8 alphanumeric characters Required: Yes Batch Keyword: Schedule Level How many levels deep the predecessor report should go. The batch utility to use is CAJUTIL0. Options: Level . COMMAND ===> Schedule: Schedule Name . -------------------. two levels are required to reach JOBC.11 Predecessors 6.11. .CA-SCHEDULER 9. The Cscdrchn command lists predecessors of a specific schedule that is in the current workload.

if JOBA's predecessors are JOBB and JOBC. specifying NO for REPEAT will only display JOBD's predecessors once.11 Predecessors Repeat Specify NO to prevent already displayed predecessors from displaying again when multiple predecessor paths reach the same point. For example.6. Size/Type: Yes or no Required: No Batch Keyword: Repeat Default: Yes 6-38 Online Guide . and JOBB's and JOBC's predecessor is JOBD.

or set of reasons. For example. Criteria Language The criteria language consists of a criteria vocabulary and a set of calendar mechanisms used to construct a reason. the selection criteria associated with this schedule is MON OR THU. for selecting a schedule or job for execution and for establishing its predecessors. All references to JOBA should be translated to 'JOBA SCHDA'. Note: This topic has many examples that use 'JOBA' in criteria for simplicity. 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. Predecessors are conditions that have to be met before a schedule or job is allowed to start. So far. For example. we have discussed using the criteria vocabulary to select schedules or jobs. the criteria associated with JOBB is JOBA. Chapter 7. if SCHEDA is to run every Monday and every Thursday. This example uses criteria vocabulary that refers to a processing period when selecting a schedule. Other terms used for predecessor are prerequisite and dependency. to select JOBB if JOBA was selected. Criteria Language 7-1 . But the criteria vocabulary is also used for defining predecessors.Chapter 7.

you must define several different calendars. This will be discussed in more detail later through the use of examples. Any predecessor can be defined as occurring on the day the schedule or job is selected or as having occurred on a prior day. For example. weekly. you cannot also select based on a criteria statement: with calendars. 7-2 Online Guide . the DAILY keyword causes a job to be selected every day including weekends and holidays. ■ Calendars which is a different selection methodology where you define daily. When using calendars. accounting days. a nonscheduled OS/390 job. a job run on another node. It also provides the easiest transition at year end. and other items like these. and so on. only the calendar name determines selection. and monthly calendars in order to select schedules and jobs. criteria statements only define predecessors. WEEK-DAY causes selection on Monday through Friday including holidays. the closing of an output data set. To use this mechanism. The following topics explain the criteria vocabulary and calendar mechanisms. and accounting periods. This mechanism is determined by the system and you do not have to define anything only use the keywords. The criteria language uses three types of yearly calendar mechanisms: ■ Absolute Gregorian Calendar which defines specific keywords that have absolute dates associated with them.Predecessors can be the starting or ending of other schedules or jobs. ■ Date Tables which define workdays. This is the most flexible calendar mechanism to use and is the one recommended. holidays. For example.

Workday keywords include such words as WDAY.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. xDOM-1. Normally. WDOW-1. HDAY1. Date tables are discussed in more detail later in this chapter. The examples below show how these reserved words can be used to handle real scheduling situations. and so on. 1ST. Although the schedule or job name itself causes selection to occur.1 Criteria Vocabulary 7. Otherwise.1. The other keyword is START. Although the schedule or job name causes selection. 31ST. HDAY. WDOW7.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. 7. 7. it is always assumed to be a job name. and so on. One of these keywords is SCD which identifies the next name as being a schedule name. Chapter 7.2 Reserved Words Used for Selection This topic discusses reserved words that cause schedules and jobs to be selected on a given day. DEC. and so on where x is a one-character prefix that you define when you set up a date table. WEEK-END. Gregorian Calendar keywords include such words as DAILY.1. START means that the predecessor is the starting of the schedule or job. HDAY-1. xDOM1. WDOW1. When it is used. xDOM40. HDAY31. WEEK-DAY. SUN. RD31=-nn. Accounting period keywords include such words as xDAY. This subject is covered in much more detail later in this chapter. JAN.7. the predecessor is the completion. MON. WDOM1. Criteria Language 7-3 . RD01=+nn. A schedule or job can be used to determine selection. xMOY1. it automatically becomes a predecessor as well. a couple of reserved words can be used with them.

PROC1. This is the same as the prior one. Second workday of the week whether or not JOB1 is selected. Daily.STEP2. Jobname JOBA. HDAY can also be expressed as NOT WDAY.GT. Every workday. meaning holidays and possibly weekends. Last workday of the month or as long as JOB1 is selected. Every Monday as long as it is not a holiday. Jobnumber 02 at station 40 in schedule SCHDA.CC. Jobnumber 02 at station 40 in schedule SCHDA.GT.PROC1.STEP2-02 40 SCHDA JOBA.7. The seventh day of every month. Jobname JOBA. Every nonworkday. 7-4 Online Guide .STEP2. Monday. Every Monday as long as JOB1 is also selected. First workday preceding the fourteenth of March. Jobnumber 02 at station 40 in schedule SCHDA. JNO=01). That is.STEP2-02 40 SCHDA JOBA. Jobname JOBA. Example JOBA SCHDA JOBA-02 40 SCHDA JOBA. Jobnumber 02 at station 40 in schedule SCHDA. Jobname JOBA. Every Wednesday as long as the schedule SCHD1 is also selected. First workday of any week. Jobnumber 02 at station 40 in schedule SCHDA.CC. First workday following the fifteenth of every month. Also selected any time JOB1 is not selected.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. Each of these examples is called a condition.1 Criteria Vocabulary The following examples demonstrate the use of selection reserved words. Jobname.00008-02 40 SCHDA JOBA. every Monday as long as JOB1 is also selected. Every day JOB1 is selected.

1 Criteria Vocabulary 7. Example JOBA SCHDA JOBA. DSN can be prefixed with PRED indicating the output data set was closed on a prior day. That is. the predecessor name is explicitly stated in the criteria. Stepname STEP2.7.3 Reserved Words for Use in Predecessors This topic discusses reserved words that are used to define predecessor conditions. “Commonly Asked Questions” on page 9-2. MVS DSN GDG GBLxnn Chapter 7. These predecessors are called global parameters and are described in 9.GT. Indicates the predecessor is the close of an output generation data group. Stepname STEP2 ending with a condition code greater than 8. NJE can be prefixed with START indicating that this job will not start until the NJE job that is the predecessor also starts. Each of these examples is called a condition. but do not cause any form of selection. Indicates the predecessor is the close of an output data set.1.STEP2. they are called explicit predecessors. probably on a prior day.CC. After Jobname JOBA.STEP2-02 40 SCHDA JOBA. it will always wait for today's PRED. the predecessor must complete some time since the job or schedule last ran. NJE Indicates the predecessor job runs on another node. If the PRED schedule or job is also in today's workload. Criteria Language 7-5 . After Jobname JOBA. Indicates a user-defined event must be satisfied. It can also be prefixed with PRED indicating the predecessor was an NJE job that ran on a prior day. Jobnumber 02 at station 40 in schedule SCHDA completes.00008-02 40 SCHDA Interpretation of Predecessors DO NOT RUN UNTIL after JOBA completes. PRED or PRED SCD Indicates the predecessor job or schedule must complete. These reserved words ensure predecessor conditions are upheld. Jobnumber 02 at station 40 in schedule SCHDA completes. The following examples illustrate the use of predecessor reserved words. Indicates the predecessor job is a nonscheduled OS/390 job. That is. MVS can be prefixed with PRED indicating it was run on a prior day.1. When predecessors are defined this way. or was created. GDG can be prefixed with PRED indicating the output generation data group was closed on a prior day. This particular type can even be further qualified as a keyword-defined explicit predecessor.

failoper. Procstep name PROC1.GT.PROC1.00008-02 40 SCHDA START JOBA PRED JOBA SCHDA SCD SCHD1 MVS JOBA PRED DSN PROD. Jobnumber 02 at station 40 in schedule SCHDA completes. JOBB is selected any time that JOBA is selected.STEP2-02 40 SCHDA Interpretation of Predecessors After Jobname JOBA. The following is a list of these criteria: Job name Job name. After all of the jobs in the schedule SCHD1 have completed. In doing this. After Jobname JOBA. Stepname STEP2. For example. That is. JOBA completed at least once since the last time the job you are defining predecessors for ran.1. however. If JOBA happens to be in today's workload. the predecessor name is explicitly stated in the criteria. (The job JOBA is not under the control of CA-Scheduler. Stepname STEP2 ending with a condition code greater than 8. This particular type can even be further qualified as a selection-defined explicit predecessor.JOB1DSN has been closed at least once since this job was last run. the selection criteria for JOBB is JOBA. JOBA. They really are related. That is.1 Criteria Vocabulary Example JOBA. Thus. Selection-defined explicit predecessors are jobs or schedules used in the selection criteria.failcode SCD schedule name START job name START SCD schedule name 7-6 Online Guide .Step name. After the nonscheduled OS/390 job JOBA completes. we have discussed selection and predecessor processing as separate issues.Step name Job name.4 Combining Selection and Predecessor Criteria Vocabulary Until now. this job will not run until today's JOBA completes regardless of when JOBA ran previously.CC. JOBA is an explicit predecessor to JOBB.7.Step name Job name.JOB1DSN Note: Many other keywords can be found later in this chapter.) After the output data set PROD.CC.PROC1. After JOBA starts.STEP2.Procstep name.Procstep name. JOBA automatically becomes a predecessor to JOBB. 7. Jobnumber 02 at station 40 in schedule SCHDA completes. Procstep name PROC1.

00008 START JOBA MON AND JOBA WED AND START SCD SCHD1 Now look at some examples that define selection and predecessor criteria for JOBC.PROC1. Criteria Language 7-7 . Select every time schedule SCHD1 is selected on a Wednesday.STEP2 JOBA. Select every time JOBA is selected and make the successful completion of STEP2 in procstep PROC1 in JOBA a predecessor of JOBC. JOBC will not start until schedule SCHD1 starts.CC. Select every time JOBA is selected on a Monday.1 Criteria Vocabulary Example JOBA Interpretation of Criteria Select every time JOBA is selected and make the successful completion of JOBA a predecessor of JOBC.STEP2. 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. Chapter 7. Select every time JOBA is selected and make the successful completion of STEP2 in JOBA a predecessor of JOBC.STEP2 JOBA. JOBC will not start until JOBA completes successfully. JOBA.GT. Select every time JOBA is selected and make the start of JOBA a predecessor of JOBC.7.PROC1.

If a CPU station job is not defined.1 Criteria Vocabulary Some terminology: Two types of explicit predecessors have been described so far: keyword-defined and selection-defined. if both are in the day's workload. The station 70 job is selected every day the station 40 job is selected. If Monday is a holiday. Likewise. the criteria for the non-CPU station jobs is evaluated to determine if the non-CPU station job should be selected. implicit predecessors are automatically selected on the same day that the CPU job (station 40) is selected. post-CPU jobs are not started until their CPU jobs have ended. a CPU job on station 40 will always have an implicit predecessor of its staging job on station 39. it is only selected when the station 40 job is selected. For example: JOB2= 1 7 SCHDA has criteria of 'MON' JOB2. For example. In this case.99). Non-CPU jobs are selected on a combination of their criteria and the status of the job at the CPU station. For example. Likewise. none of the non-CPU station jobs will be selected.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. which usually implies being selected every day.1 3 JOB1. For example. however. Implicit predecessors are predecessors that do not have to be defined in the criteria. and station 70 is the lowest station number defined for the job. implicit predecessors can only exist for CPU jobs and post-CPU jobs. Since there is no station 40 job. If the job at the CPU station is not selected. When the same schedule/job/job-number exists for more than one station (01 . code criteria for them to be selected less frequently than the CPU job. You can. 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. However. you cannot cause implicit predecessors to be selected on a day the CPU job is not selected.1 71 SCHDA has criteria of 'MWF' The station 70 job is only selected on Mondays. the station 71 job will only be eligible for selection when the station 70 job is selected. a CPU job is not submitted until all its pre-CPU jobs complete.7. the station 30 job will NOT be selected because the station 40 job was not selected.1 4 JOB1. If the CPU station job is selected. Furthermore. the station 71 job is only selected on Mondays. the sequential order of the stations defines implicit predecessors. even though the station 70 job does not have criteria. The station 30 job is selected every day that the station 40 job is selected that is also a Monday. Furthermore. assuming that station 40 is the CPU station: JOB1. 7-8 Online Guide .

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). there are rules for interpreting this mixture. Since the criteria language is used to define both selection and predecessor conditions. individually caused the reason a job or schedule was selected.1. 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. That is. For example. The reason a job is selected stays with the job for its life in the system. the condition or combination of conditions.7. If it is Monday and JOB2 happens to be in the workload for Monday. 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. Does this mean that CA-Scheduler just makes one list of predecessors for each job? Not at all. In the example above. Criteria Language 7-9 . All of our examples appear with parentheses. 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. this means that no matter what day it is. Given the example above. JOB1 and JOB2 will be predecessors as long as they are in the day's workload. Chapter 7. Rule #1 just applies to selection-defined predecessors: jobs and schedules. JOBC (the job being defined) will have to wait for both JOB1 and JOB2 to complete. Understanding the relationships between reasons and predecessors is important.1 Criteria Vocabulary 7. Whether those jobs or schedules are part of the reason for selection does not matter.5 Using Multiple Conditions with ANDs and ORs The examples that have been used so far have contained only one reason. CA-Scheduler observes ORs used with all keyword-defined predecessors. This value can be referred to as the reason code.

1.7. 7-10 Online Guide . however. The NOT expression is used only for selection purposes within the criteria language. 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.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. it will be a predecessor of JOBC. Another example will help reinforce this point. if the criteria for JOBC is: (MON AND NOT JOB1) selection will occur only on Mondays when JOB1 is not selected. This shows that Rule #1 applies even when using NOT expressions.1 Criteria Vocabulary 7. For example. 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. If either JOB1 or JOB2 is present. How would predecessors be handled in the above example? If JOB1 for some reason ends up in the workload (by a manual override).

define its own individual selection criteria on the job criteria record. Since we are on the subject of schedules and jobs. Chapter 7. selection criteria would normally be defined at the schedule level.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. That explains why we advise that you follow Rule #3. A schedule is eligible for selection even if AUTOSEL=NO is specified. JOB1A is only looked at if its schedule is selected but SCHED1 is not selected on Tuesdays. if the selection criteria for SCHED1 is MON. However. just define when these jobs run once. For example. Up to now. 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. we have not followed this rule for simplicity's sake. JOB1A will never get selected. So if production control thinks of schedules as units of work. on the schedule's criteria record.1. From now on. If all jobs in a schedule run when the schedule is selected. CA-Scheduler looks in its database and defaults to the first schedule it finds containing a job by that name. Criteria Language 7-11 . it is time to suggest another rule for coding the criteria language. if you omit a schedule name when referring to a job. and JOB1A in SCHED1 has a selection criteria of TUES. we will. schedule names technically are not required. Keep the following rule in mind when coding selection criteria. so JOB1A will never be selected. too.1 Criteria Vocabulary 7. Rule #3: When coding a job in the criteria language. That means you only need to define predecessors at the job level. always qualify it with its schedule name. After all. If a job does not run every time its schedule runs.7.

It also provides the easiest transition at year end. you cannot also select based on another job being selected. Most of the preceding examples used keywords from this calendar mechanism. weekly.1 Gregorian Calendar This calendar mechanism is presented first because it is the simplest to understand and can be used immediately. and accounting periods. For example.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. ■ Calendars define daily. ■ Date Tables define workdays. but even different divisions within a company.2. All you do is use the reserved words (keywords) when defining your selection criteria. the DAILY keyword causes a job to be selected every day including weekends and holidays. Each schedule defines which date table to use for evaluating when to select that schedule and its associated jobs. accounting days. For example. and so on. This is the mechanism to use if all else fails.2 Calendar Mechanisms 7.7. and monthly calendars for selecting schedules and jobs. When using calendars. 7. This is the most flexible calendar mechanism and is the one recommended. This mechanism is determined by the system and you do not have to define anything -just use the keywords. You do not have to define a calendar or date table first. This topic describes the use of these calendar mechanisms. you must define individual calendars. For example. And your accounting month may not begin on the first of every month. holidays. we do have holidays. CA-Scheduler addresses all variations using three different calendar mechanisms: ■ The Absolute Gregorian Calendar defines specific keywords that have absolute dates associated with them. Some months have four weeks. To use this mechanism. There can be quite a variation not only between different companies. while others have five. WEEK-DAY causes selection on Monday through Friday including holidays. 7-12 Online Guide . only the calendar name determines selection.

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).2 Calendar Mechanisms This mechanism's reserved words that control selection are based on the standard Gregorian calendar. This means that December 29-31 may be in week 1 of the following year. Second-to-the-last week of the year based on the international definition of a week in ISO 8601. 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. “Gregorian Calendar Conditions” on page 7-41. and January 1-3 may be in week 52 of the previous year.7.9. This means that December 29-31 may be in week 1 of the following year. not workdays or accounting days. Criteria Language 7-13 . Chapter 7. and January 1-3 may be in week 52 of the previous year. which says that all weeks start on Monday and go to Sunday. which says that all weeks start on Monday and go to Sunday. I-WOY-2 Many other keywords can be found in 7. 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).

2 Calendar Mechanisms Do not forget that you can also use the Boolean reserved words AND. 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. OR.

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 Chapter 7. You can use two types of keywords with date tables: workday keywords and accounting-period keywords. Workdays are days that are not defined as holidays. When defining the selection for a job or schedule. For our purposes.2. Criteria Language 7-15 .7. With date tables. This is done with a full panel that actually displays a calendar one month at a time.2 Calendar Mechanisms 7.2 Date Tables This calendar mechanism is the most flexible of them all and is the one we recommend you use.2. but you must define your holidays. 7. CA-Scheduler is smart enough to know today's date but is not smart enough to automatically know your workdays. we will discuss the reserved words (keywords) used with date tables.2. you can use the reserved words described for Gregorian calendars. It handles holidays (and weekends) as they pertain to your own environment. 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. holidays.1 Workday Keywords Workday keywords are just what they say: keywords that relate to workdays. weekends are considered holidays (unless you specify otherwise). and accounting periods. Before we see how to define holidays on these panels.

N. specifying the one to seven character name of the date table. Consequently. 7-16 Online Guide .2 Calendar Mechanisms 7. x is used instead of a prefix. The A prefix or the A version of the date table is the default date table. allowing for 21 different accounting periods) while using the same date table. In the examples below. When you use a B prefix. To define a date table.2 Accounting-Period Keywords When we discuss how to define a date table. then option 7 (Datetable). or W. 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.2. Each accounting period has its own prefix. you have to define a prefix (a letter.2. a rule for date tables: Rule #4: Define three years' worth of date tables for each unique date table name. select option 2 (Database) from the CA-Scheduler main menu. sales cycles. the accounting resolutions will be taken from the B version of the date table. We have to start with a rule.7. or any other unit of time. Each year being accessed must have a date table for the year before and after it. H. As you might think. we have to consider accounting periods going over a year-end date. and the year. Select option 4 to define a new date table. we will see what is involved in setting up a date table. 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. the prefix character. with the exception of E. When you define a date table. P. The following panel is displayed.

15 WA..CA-SCHEDULER 9.. WA.. 3 . WA. .. ..M.. Saturday --------2 . DATETAB Description .. WA.M. Workdays per Week . or ) Enter END to Exit.. Chapter 7. .... WA. you could place a Y on the appropriate day.. . .. Sunday --------3 1 17 24 31 .. delete the W (to remove the workday attribute) and the A (to remove the accounting day attribute). .. ...Y - Workday Accounting Day Month (Period) End Year End Enter END to exit. To indicate that January 1 is a holiday and a nonaccounting day. . . xxyy (SCHD) DATETABLE ------------------- DATETAB A 2 3 5 (5.. . . WA... .. COMMAND ===> Datetable .. . 7... Legend: W.. WA. 22 WA. WA..CA-SCHEDULER 9. -------------------.. Monday --------4 11 18 25 WA..7. . WA. Friday --------1 WA.. WA. . Accounting Code .. . Note that the accounting day attribute is always an A. . ... Criteria Language 7-17 . WA.. COMMAND ===> Define Datetable: Datetable . 8 WA.... 16 .. Wednesday --------6 13 2 27 WA... .. . .... A JANUARY 2 3 Thursday --------7 14 21 28 WA.. ... 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). Press Enter to display the first month of the date table. even if a different prefix is being used.2 Calendar Mechanisms -------------------. .. WA. WA. 23 .. 6. Tuesday --------5 12 19 26 WA... . If January was the end of the accounting year. . . .A.... 29 WA. 9 .. xxyy (SCHD) DATETABLE ------------------- Accounting Code . . . Year .. .

.. xxyy (SCHD) DATETABLE ------------------- Accounting Code .... Sunday --------3 1 17 24 31 ... type CAN on the command line... since it is no longer a workday.. .... 9 . 23 .....7..CA-SCHEDULER 9. When you are finished updating the date table. 22 WA. Monday --------4 11 18 25 WA. WA. COMMAND ===> Datetable .... You may also type the first three letters of any month's name on the command line to jump directly to that month.2 Calendar Mechanisms Press Enter after making the changes..... ..A. 7-18 Online Guide ... WA. WA.... WA..M.... . press PF3 to save your changes. 15 WA. Tuesday --------5 12 19 26 WA. Notice that January 1 is no longer highlighted. . WA. . 16 . Wednesday --------6 13 2 27 WA. (If you wish to exit without saving your changes. 3 ... DATETAB Description . WA...M. . Friday --------1 ... WA. WA.... Saturday --------2 . WA. . Legend: W.. 29 WA.. A JANUARY 2 3 Thursday --------7 14 21 28 WA. WA.. You may use PF8 to scroll to later months and PF7 to scroll to earlier months. ... .) Don't forget that you must also define date tables for the prior and next years.... ..Y - Workday Accounting Day Month (Period) End Year End Enter END to exit. . . -------------------. 8 WA... .. WA.. .. WA.

2 Calendar Mechanisms 7.2. it will be selected on Wednesday. Select every workday of the last week of the year.2. 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. You can request a specific date and/or date table on this transaction if you desire. Chapter 7. you will need another date table. Select the first workday of every week. This references the date table defined with prefix B.2. An accounting day may be a holiday (this is not normally the case). Select every Monday through Thursday except on holidays.2.7. 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. Reviewing this report will help you understand the Gregorian calendar and date tables better. Select every Monday of the second and fourth weeks of the month regardless of whether Monday is a holiday. Select on every accounting day except for the last accounting day of the period. If you need more than one holiday definition. This is the same as above except if Tuesday is also a holiday. or select on Tuesday when Monday is a holiday.4 Date Translation Report Now that we have discussed the Gregorian calendar and date tables. Criteria Language 7-19 .3 Summary of Date Tables Date tables are broken into two categories: workday processing and accounting period processing. The Date Translation report is obtained by running the CA-Scheduler Utility with the REPORT DATETRAN transaction. Select on every accounting day that is not a holiday. The reserved words (keywords) for the Gregorian Calendar mechanism and the keywords for the date table calendar mechanism can be used together. we need a way to see what conditions are met on any given day. This is the same as the above example only expressed more simply.

the work week.) Notice the next set of lines pertain to the Gregorian calendar and include DAY OF WEEK.1 RD28=+2 .7.6 RD 3=+15 . 7-20 Online Guide .6 RD 5=+15 .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 . The rest of the lines pertain to the date table. and accounting periods. the workday of the week. They include the workday.8 RD 7=+13 .27.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.7 RD 6=+14 .3 RD3 =+19 . the workday of the year.1 RD27=+2 . accounting days.6 RD 4=+15 . These indicate whether a condition is satisfied. WEEK-DAY=YES means that any time you specified WEEK-DAY as the criteria.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 . you should understand how the criteria vocabulary works with the Gregorian calendar and date tables. the workday of the month. (The date table name is on the right side of the report.5 RD 2=+16 . WEEK OF MONTH.2 Calendar Mechanisms COMPUTER ASSOCIATES CA-SCHEDULER 9. the relative days of the month.2 RD29=+2 . DAYnOFm. For example. It first displays the Julian and Gregorian dates with the date table name that was used to determine workdays. xxyyCH9 DATE TRANSLATION REPORT DATETRAN PAGE 1 24 APR yyyy 14. and the various accounting days. the schedule or job will be selected. and WEEKnOFm.1 RD26=+21 . After reviewing this report carefully.

If calendars are defined using a holiday.7. or drop the day. We do not recommend that you use calendars. Criteria Language 7-21 . Again. ■ Weekly calendars use the Weekly Roll Option. you can skip this subtopic. Chapter 7. first define a prototype calendar. The panel below defines the prototype calendar for 2003. the next workday. Next and Previous schedule the next or previous workday in the prototype as the workday in the weekly calendar.3 Calendars To use calendar processing. You can have only one prototype calendar for each year.2. where yy is the year. Consequently.2 Calendar Mechanisms 7. Workdays in the prototype calendar become workdays in the daily calendar. use PROTO03. Drop means not to schedule a workday in the weekly calendar. This calendar defines your holidays as well as what to do if another calendar is defined with a processing day on a holiday. Instead. You may shift the day to the previous workday. Calendars use an entirely different approach to selecting schedules and jobs. The following steps describe how to use calendars. 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. Once the prototype is defined. This means that you have only one set of holiday definitions.1 Step 1: Define the Prototype Calendar Before you define any calendars. CA-Scheduler handles rescheduling based on the calendar's selection frequency: ■ Daily calendars are not rescheduled. It specifies a five day work week. This feature is supported to assist users converting from the VSE version of CA-Scheduler. Prototype calendars must have a name of PROTOyy. a schedule or job is selected on the days that the calendar specifies as workdays. set aside everything you have learned so far about the Gregorian calendar and date tables. When using calendars. With calendars. only for defining predecessors. For 2003. 7. If you do not intend to use calendars. the description of calendars will be brief. Then you would use a calendar to define just the days of the year on which those schedules run.3.2. the criteria language is not used for selection. you can define calendars specific to your needs. try to do all of your definitions with date tables or the Gregorian calendar or a combination of the two. The same calendar also applies to the jobs in that schedule. the only thing you specify on a schedule for selection purposes is the calendar name. Do not try to relate any discussion of calendars to the other calendar mechanisms.

. . PROTO 3 Year . 16 . . Monday --------4 11 18 25 W W W W Tuesday --------5 12 19 26 W W W W 2 3 Thursday --------7 14 21 28 W W W W Friday --------1 W 8 W 15 W 22 W 29 W Saturday --------2 . . . 7-22 Online Guide . 6. -------------------. You may use PF7 and PF8 to scroll through the months. . . 2 3 Workdays per Week . Next and Previous schedule the next or previous workday in the prototype as the workday in the monthly calendar. . DROP Monthly Roll Option . . COMMAND ===> Calendar . . 7. or to a holiday by blanking out the W. or Prototype Options: Weekly Roll Option . 23 .7. . or type the first three letters of a month's name on the command line to jump to that month. . 9 . PROTO 3 Description . . xxyy (SCHD) CALENDAR -------------------- JANUARY Sunday --------3 1 17 24 31 . or DROP) (NEXT or PREVIOUS workday. When you press Enter. Drop means not to schedule a workday in the monthly calendar. 3 . 5 (5. . . . . . .CA-SCHEDULER 9.Workday Enter END to exit. . You can change dates from a holiday to a workday by typing a W next to it.CA-SCHEDULER 9. Wednesday --------6 13 2 27 W W W W Legend: W .2 Calendar Mechanisms ■ Monthly calendars use the Monthly Roll Option. . January's dates are displayed. . -------------------. . . COMMAND ===> xxyy (SCHD) CALENDAR -------------------- Define Prototype Calendar: Calendar . or DROP) Enter END to Exit. . . . DROP ) (NEXT or PREVIOUS workday.

. 2 3 Workdays per Week . . (You can exit without saving your changes by typing CAN on the command line. . or one of the following for Monthly: FD .first workday of month LW . TUESDAYS. press PF3 and the prototype calendar will be saved.) 7. . MYCAL Year . For weekly calendars. . . . Specify the type of calendar you are creating: DAILY.2 Calendar Mechanisms When all 12 months are correctly defined.3. . .last workday of month nnW . or Monthly) (Blank for Daily. When defining calendars. or Options: Type of Calendar . ENDOFWK. . . ) (Daily. . WEEKLY. For monthly calendars. .SAT or END for Weekly. define other types of calendars.2. 5 (5.nnth workday of month Enter END to Exit. SUN . invent your own names for them such as EVERYDAY. COMMAND ===> xxyy (SCHD) CALENDAR -------------------- Define Calendar: Calendar . . Weekly and Monthly Calendars Now that we have a prototype calendar.7. you may specify the day of the week that should become a workday for this calendar. or MONTHLY. Daily calendars will copy the prototype calendar.first day of month LD . 6. Weekly. Chapter 7. 7.nnth day of month FW . or ENDOFMO. using any of the listed options. -------------------. the following panel is displayed. DAILY Day of Week/Month . . Criteria Language 7-23 . When defining a calendar. you may specify the day of the month that should become a workday.2 Step 2: Define Daily.last day of month nn .CA-SCHEDULER 9. .

..X JOBA 7-24 Online Guide ...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.............3.......1 Example 1 To run the job named JOBA in the schedule name SCHDA on the first workday of the week....X X X X X JOBA 7.2 Example 2 Now use another variation of WDOW to schedule JOBA to run on the last workday 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 ..3 Some Examples 7.... 7..................3 Some Examples Now that you are familiar with the criteria language and calendar mechanisms.......X X X H X JOBA 7. consider how to apply what you have learned to the following scheduling problems.... WDOW-1 JOBA would be selected on the last working day of the week (third Friday=holiday)....3..3.....7.... 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 ...... 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 ................

.....3.. then JOBA runs on the following Monday..... If Friday is a holiday..3 Some Examples 7.. then run job on MON unless MON is also a holiday. then JOBA runs on the following Tuesday... And if the following Monday is also a holiday........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........... 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...X X H X X JOBA Chapter 7... Criteria Language 7-25 ......5 Example 5 JOBA runs on Friday.. 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 ..3. 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 .7.........X JOBA 7.

the daily summary that runs each workday ■ PROD002 .the summary that runs on Friday whether or not Friday is a holiday.3.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. and is not dependent on PROD001 ■ PROD003 .7. WDAY FRI FRI AND (PROD001 ACCPROD OR PROD002 ACCPROD) For selection purposes. Consequently.6 Example 6 An accounting schedule (ACCPROD) consists of three jobs: ■ PROD001 . predecessors that are jobs are handled as if there is always an AND condition.3 Some Examples 7. However. PROD003 will wait for both PROD001 and PROD002. the OR expression will be handled as expected. 7-26 Online Guide . if Friday is a workday.

Chapter 7. MANQTR runs on a 4-week.Defaults to whenever the schedule is selected.INPUT AND (PAY002 PAY OR NOT PAY002 PAY) This tells CA-Scheduler to schedule job PAY001 every week day. It must also wait for job PAY002.7. PAY001.3.the summary that only runs on Friday. 7.8 Example 8 The Manufacturing Quarterly production schedule (MANQTR) contains three jobs that run on the last day of the manufacturing quarter. 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. ■ PAY002 . 5-week cycle defined in a date table specified in the schedule definition using a prefix of M.3 Some Examples 7. Criteria for schedule MANQTR MDOM-1 AND (MMOY3 OR MMOY6 OR MMOY9 OR MMOY12) None .3. Criteria Language 7-27 .7 Example 7 A payroll schedule (PAY) consists of two jobs: ■ PAY001 . Criteria for schedule PAY Criteria for job PAY002 Criteria for job PAY001 WEEK-DAY FRI DSN PAY001. Separating selection criteria and predecessor conditions this way makes it easier to evaluate these criteria statements. 4-week.INPUT. when it is scheduled on Friday. regardless of whether job PAY002 is scheduled.the summary that runs every weekday and needs an input data set. that is transmitted every weekday from an RJE site. Job PAY001 waits for a data set to be created every week day and also waits for job PAY002.

9 Example 9 For this example. we take something a little more practical and show some of the logic behind determining criteria. ■ If the last workday falls on Monday through Thursday. the monthly job should wait for the weekly backup to complete.3. so the daily job's selection criteria is now complete. ■ If the last workday of the month is a Friday. The daily job IH7D02 normally runs Monday through Thursday. We already know to be conscious of holidays. This shows the type of thought process you go through. In this case. If the weekly job runs on Monday through Thursday. The criteria statement that best describes this is shown below. we do not want the job to run. the monthly job should wait for the daily backup to complete. 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. Now we can work on the weekly job. 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. 7-28 Online Guide . however. the date table was defined for a five-day work week so Saturdays and Sundays are not workdays. For our purposes. The schedule named IH7BKUP backs up some disks and consists of three jobs: a daily backup. the daily job must finish first. Its predecessors vary depending on what day of the week this job runs. ■ If the last workday of the month falls on a Saturday or Sunday. a weekly backup and a monthly backup. Consequently. the monthly backup job has no predecessors. revise the criteria as follows: WDAY AND (MON OR TUE OR WED OR THU) Now Monday through Thursday also have to be workdays. 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.7.3 Some Examples 7. it does not. To omit holidays. its criteria would be something like: MON OR TUE OR WED OR THU But what happens on holidays? On holidays.

... or JOBD is also 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 .. WDAY AND NOT FRI WDOW-1 AND PRED IH7D02 IH7BKUP WDOM-1 AND (IH7D02 IH7BKUP OR IH7W02 IH7BKUP) 7... then JOBX will run twice. and once being dependent on JOBC to complete.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 .. JOBB.7.....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 Chapter 7... JOBC...Defaults to having all jobs looked at every day...... Criteria Language 7-29 .... For example.. once being dependent on JOBA to complete.3... if JOBA and JOBB are selected to run today.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..

but will not run unless requested...) So.. And because JOBA is always selected. JOB1 and JOB2 and JOB3 are all selected to run.7.. 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 .11 Example 11 JOBA JOBB JOBC JOBD REQUESTED JOBA JOBB JOBC Because JOBA is a requested job..............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 ..1 X JOB3 JOBA..3. (The 'OR' condition becomes an 'AND' condition for job dependency.. and runs on Saturday and Sunday when JOB3 is selected. if you have a job (JOBA) that needs to run Monday through Friday when JOB1 and JOB2 are selected... any other jobs which are a successor to JOBA (in this case.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...... then you could use the following criteria: JOBA JNO= 1 JOBA JNO= 2 M JOB1 X JOB2 X JOBA... JOBB and JOBC and JOBD are all successors)...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 ..... For example..X X X X X X X X X X X X X X X X JOBA JOBB JOBC JOBD 7.3 Some Examples 7.X X X X X X X X X X X X X X X X 7-30 Online Guide .... suppose that on any given day. The job dependency would then become 'JOB1 and JOB2 and JOB3' since all three jobs were selected. then all of these jobs will also be selected..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 .. it will be selected every day...3...

. However.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 Chapter 7.14 Example 14 JOB NAME -------JOBA JOBB JOBC JOBD JOB CRITERIA -----------DAILY ( DEFAULT ) MON ( MONDAY ) WED ( WEDNESDAY) (JOBA AND JOBB) OR JOBC On MON. the criteria for JOBD will become 'JOBA AND JOBC' (JOBB is disregarded because it was not SELECTED to run on WED).. with JOBD waiting for both JOBA JOBB to complete... Criteria Language 7-31 ..X X X X X X X X X X X X X X X X X T F S S M T W ..... JOBA AND JOBC AND JOBD will run. with JOBA being a predecessor to JOBC....X X X X X X X X X X X JOBA JOBB JOBC 7.. JOBA AND JOBC will run. 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 T F S S M T W ..3 Some Examples 7. Because both JOBA AND JOBB were SELECTED on FRIDAY.. M T W T F S S M T W . with JOBB being a predecessor to JOBC.... with JOBD waiting for both JOBA AND JOBC to complete.. (if FRIDAY is NOT a WDAY)......3........ *REMEMBER that the 'OR' condition becomes an 'AND' condition when DEPENDENCY is determined..... then JOBB AND JOBC will run.......X H X X X X X X X X X T F S S M T W .7.13 Example 13 JOB NAME -------JOBA JOBB JOBC JOB CRITERIA -----------WDAY ( WORK DAY ) FRI ( FRIDAY ) JOBA OR JOBB ON WDAY... then JOBC's criteria becomes 'JOBA AND JOBB' rather than 'JOBA OR JOBB'. JOBA JOBB JOBD will run.. ON WED..... if FRIDAY is a WORKDAY. ON FRI.. then all three jobs will run with JOBC waiting for both JOBA AND JOBB to finish before being released.3.. such that on WED..

Instead. Therefore. this job will only be selected when the job MONDAY is selected. you cannot have one day as a Monday and a Tuesday.4.4. The correct criteria vocabulary word is MON or TUE. but that is not what happens.4. What is JOBB's predecessor? The data set JOBA.2 Example 2 Criteria for JOBA SCHD01 MON AND TUE MONDAY AND TUESDAY Will JOBA be selected on Mondays and Tuesdays? No. 7. That is straightforward enough.4 What Is Wrong with these Examples? 7. 7. The correct criteria vocabulary word is MON. Evaluate this statement carefully to see what is wrong. Why? Because of the OR. JOBA in SCHD01 would never be selected.DATASET The intent is to select JOBB on the last workday of the week. The days on which JOBB is selected will be: WDOW-1 OR 'keyword-defined parameter' 7-32 Online Guide . 7.4 What Is Wrong with these Examples? Now that you have a basic understanding of the criteria language.DATASET must be closed on the day JOBB is selected before JOBB will be submitted.7. It is important to evaluate the selection criteria and the predecessor conditions separately. try testing your knowledge by debugging errors in the following criteria statements. Since you probably do not have a job named MONDAY. But when is JOBB selected? Not just on WDOM-1 (the last workday of the month).1 Example 1 Criteria for JOBA SCHD01 MONDAY Will JOBA run on Mondays? Not likely because MONDAY is not a vocabulary word.3 Example 3 Criteria for job JOBB WDOW-1 OR DSN JOBA. CA-Scheduler interprets MONDAY as a job name.

so the second condition defaults to 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. Why do JOBA and JOBB in schedule SCHED01 not run when expected? Both jobs are supposed to run Mondays and Wednesdays. 7. too.DATASET to close before submitting JOBB. so look at the predecessor conditions.4 What Is Wrong with these Examples? You see. CA-Scheduler cannot translate DSN JOBA. remembering the rule for evaluating predecessors: There are no OR relationships with selection-defined explicit predecessors. 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. that creates a predecessor loop.DATASET This selects JOBB on the last workday of the month and waits for the data set JOBA. You can run the Analyze Report at any time to detect deadlocks automatically. When jobs require each other as predecessors. That seems in order. JOBB should be the predecessor to JOBA. this job is selected WDOW-1 OR DAILY. First. All ORs become ANDs. and the explicit predecessor of JOBB is JOBA. Chapter 7.7. ■ JOBB is always selected on Mondays.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. That means the explicit predecessor of JOBA is JOBB.DATASET into a selection condition. look at the selection criteria. On Mondays. Both jobs are always selected on Mondays and Wednesdays: ■ JOBA is always selected on Wednesdays. neither job ever runs because their predecessors are never satisfied. which is also called predecessor deadlock.4. so JOBB is. Criteria Language 7-33 . Although these deadlocked jobs are selected properly. Because of the OR. but conversely on Wednesdays. so JOBA is also selected on Mondays.

JOBB in SCHED01 will always be selected on ADAY.7. After JOBB is selected. The confusion arises when evaluating predecessors. Why does the criteria statement above not make that happen? Instead. Instead. it is supposed to be a predecessor to JOBB. JOBB will start as soon as GBLB01 is set to YES.4 What Is Wrong with these Examples? 7.6 Example 6 Criteria for job JOBB ADAY AND JOBA SCHED01 AND GBLB01=YES OR ADAY AND GBLB01=YES Clearly. That is not what happens. and GBLB01. when JOBA is present. these predecessors are left for evaluation: (JOBA SCHED 1 AND GBLB 1=YES) OR (GBLB 1=YES) As you can see. 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 . JOBA is selected because it is not Monday. We can step through what happens.4. When GBLB01 is set to YES.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. And if JOBA is in the day's workload. GBLB01. JOBA is selected because it is not Tuesday. JOBA is always selected because on Mondays. 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. the status shows that JOBB waits for predecessors JOBA. JOBB starts regardless of JOBA because of the second GBLB01. And on Tuesdays (and every other day). JOBB is always supposed to wait for the global GBLB01 to be set to YES.

we have to set up JOBB as two separate jobs: JOBB-01 and JOBB-02. 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 Chapter 7.4 What Is Wrong with these Examples? After JOBB in SCHED01 is selected. it may be that JOBA only runs on Fridays). Tuesday. 7. only these predecessors are left for evaluation: (JOBA AND GBLB 1=YES) When JOBA is not in the day's workload. To accomplish this. The rule is that keyword-defined explicit predecessors apply across ALL selection criteria. but only on Saturday if JOBA completed sometime since last Saturday (for example.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.7. and so on). CA-Scheduler knows that it cannot be a predecessor. JOBB will wait for JOBA every time JOBB is selected (even on Monday. Criteria Language 7-35 . Consequently.4. Notice how we have simplified the criteria for JOBB-01 below.

Work can only be backlogged once. Example: Jobname: REQUESTED or DAILY Schedule name: REQUESTED or DAILY Pitfall #4 Pitfall #5 7-36 Online Guide . Do not use the CA-Scheduler reserved keywords as job name or schedule names.5. It is easy to cancel the wrong job.7.5 Review of Tips to Remember 7. If work is eligible to be backlogged multiple times. be sure you are on the correct line. If you want it reset. only the last occurrence is kept. You cannot reset a global parameter. When keying in a command to the left of a schedule or a job in the status displays. 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.1 Pitfalls Pitfall #1 Pitfall #2 Pitfall #3 A global parameter only gets set. you must set it to another value.5 Review of Tips to Remember 7.

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.7. If the predecessor job has abended. Whether those jobs or schedules are part of the reason for selection does not matter. CA-Schedule observes ORs used with all keyword-defined predecessors (NJE. The PRED keyword only waits for the job if it has not run since the last time this job has run. Note #2 Note #3 Note #4 Note #5 Note #6 Note #7 Note #8 Note #9 7. Criteria Language 7-37 . Autoscan does not reset the global parameters. DSN. All criteria for JOBNAME should be coded as 'JOBNAME SCHEDULENAME'. predecessors are cumulative. Job start times do not override specified schedule start times. That means (MON OR FRI) is one reason while MON OR FRI defines two reasons. its criteria has been satisfied. they let you postpone running jobs after a schedule has started. Formatting the CAIJTRK files sets all global parameters to defaults. 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. and PRED). always qualify it with its schedule name.6. Instead.6 Notes Note #1 Multiple ORs can be grouped into a single reason code by placing parameters around this reason. instead. MVS. Predecessors in job records are not evaluated until its schedule has started and the job's early start time has been reached. Rule #2 Rule #3 Rule #4 Chapter 7.6 Notes 7. GBLxnn. Defining predecessors for jobs does not override a schedule's predecessors. Do not use TYPRUN=HOLD in JCL submitted by CA-Scheduler. When coding a job in the criteria language. GDG.

CA-Scheduler waits for them to complete unless you precede their names with the keyword START. the day's production. A schedule or job is eligible for predecessor selection even if AUTOSEL=NO or SKIP=xx is specified. Use the SCD keyword before a schedule name to identify it as such. weekly. and PRED). Calendars: Define daily. Predecessors: Every job or schedule listed in a criteria statement is a predecessor if it is also in.7. 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. MVS. A criteria statement like NOT JOBA defines JOBA as a predecessor. When using calendars. only the calendar name determines selection. Each year being accessed must have a date table for the year before and after it. Date Tables: Define three years' worth of date tables for each unique date table name. always qualify it with its schedule name.7 Summing Up 7. The NOT keyword only applies to selection. GDG. and monthly calendars for selecting schedules and jobs. or eligible to be in. 7-38 Online Guide . DSN. When coding a job in the criteria language. 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.7 Summing Up Evaluate criteria statements twice: once to determine selection criteria and again to identify predecessor conditions. If jobs or schedules are predecessors. GBLxnn.

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. the successor will wait for the PRED predecessor event to occur within this production day. 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. all of which must be met for a job or schedule to be selected. Chapter 7.8 Criteria Vocabulary 7. A selection reason consists of two or more conditions.8. if the predecessor is selected on a Monday and the successor is selected on a Friday. if both the PRED predecessor and the successor are selected together.8 Criteria Vocabulary 7.1 Reserved Words To show that Criteria consists of two or more selection reasons. Two or more conditions count as one reason. precede it with PRED SCD. Use PRED only to identify predecessors that are NOT selected on the same day as their successors. predecessors and successors are selected together. precede it with PRED.7. The only reserved words required for predecessors and successors selected together are SCD and START. In this case. as shown in the table at the top of the previous page. A job that is selected with its successor does not need any reserved word to identify it as a predecessor. All conditions must be satisfied except this one (negate the condition). Criteria Language 7-39 . (For example.) In most cases. any one of which will cause a job or schedule to be selected.

8 Criteria Vocabulary 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.

therefore. To see what Gregorian conditions are satisfied on any given day.9 Gregorian Calendar Conditions 7. consult the Date Translation Report in the Reports Guide. including weekends and holidays Monday through Friday Saturday and Sunday Sunday Monday Tuesday Wednesday Thursday Friday Saturday Monday. (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. If you specify REQUESTED Schedules and jobs will be selected on Request. 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 Chapter 7. Note.7. the schedule or job will be selected every day but must be activated by the REQUEST/SREQ command. Wednesday.9 Gregorian Calendar Conditions These conditions are based on the standard Gregorian calendar and not on workdays or accounting days. Therefore. Criteria Language 7-41 . you can use these conditions in criteria statements with or without defining a date table. if you list REQUEST/SREQ before another condition.) Every day. that criteria are evaluated from left to right. when using the REQUEST/SREQ command with other criteria. like JOBA.

7-42 Online Guide .7.) First week of the year through the 53rd week of the year. and so on. (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. Last week of the year through the 52nd to last week of the year.9 Gregorian Calendar Conditions 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.

To determine where a specific date falls within each cycle. 1900.9 Gregorian Calendar Conditions 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. see the Date Translation Table which is generated as part of each simulation run. Criteria Language 7-43 . This will tell you. To determine where a specific date falls within each cycle. The base date for all cycles is Jan 1. see the Date Translation Table which is generated as part of each simulation run. Last day of the month through the 30th to last day of the month. 1984 falls in the first week in a two-week cycle and in the last week in a five-week cycle. 1984 is the first day in a three-day cycle and the fourth day in a five-day cycle. This will tell you. The base date for all cycles is Jan 1. Leap year. According to a cycle lasting from one to six weeks. for example. for example. Year 1994 through year 2020. Chapter 7. that May 27. that May 27.7. 1900.

) First workday of the year through the last workday of the year.) Last workday of the month through the 30th to last workday of the month.) 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. Then you can consult the Date Translation Report in the Reports Guide to see what workday conditions are satisfied on any given day. (Any week with at least one workday is counted as a work week. (Any day shown in high intensity on the date table is counted as a workday. (Any week with at least one workday is counted as a work week. 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. (Any day shown in high intensity on the date table is counted as a workday. this year.7.) First work week of the month through the 6th work week of the month. (Any day shown in high intensity on the date table is counted as a workday.) Last work week of the year through the 52nd to last work week of the year.) First workday of the month through the 31st workday of the month. (Any week with at least one workday is counted as a work week. The following criteria keywords can only be used if the schedule or job is selected by a date table.10 Workday Conditions 7.) Last workday of the week through the 6th to last workday of the week. All holidays (days shown in low intensity on the date table). you must use the Datetable Definition panel to define workdays and holidays for three years: last year. 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). and next year.) Last work week of the month through the 5th to last work week of the month.) 7-44 Online Guide . (Any day shown in high intensity on the date table is counted as a workday.10 Workday Conditions To use these workday conditions.

10 Workday Conditions 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. To select a job on the third workday before the 25th of the month. (nn may range from -31 to +31. Criteria Language 7-45 . a blank must precede and follow the equal sign.7. However. Also. specify RD25 = -3. specify RD14 = +5. the job will not be selected at all that month. nn equal to + or -0 causes selection on the specified relative day of the month. For example.) 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 Chapter 7. up to the thirty-first day of the month (RD31). if that day is a holiday. to select a job on the fifth workday after the 14th of the month. and a leading zero is not required with a one-digit number.

11 Accounting Conditions 7.7. To do this. To use these criteria.) You must do this for three years: last year. Any day designated by A (or another prefix) on the date table is counted as an accounting day. substitute A for the x: ADAY. define date tables for two years and designate the end of each accounting year by typing an E on any date. and when the accounting year ends. 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.) xDOM-1 : xDOM-40 xMOY1 : xMOY53 7-46 Online Guide . accounting conditions will be taken from the A version of the date table (the default version). BDAY or CDOM or DMOY or GWOM). (The end of the period defaults to the last day of each month. To do this. go through the date table and designate the end of each period by typing a P on any date. go through the date table and designate the end of each period by typing a P on any date. you must define at least two accounting periods on the date table. To use these criteria. sales cycles. you must designate the ends of two accounting years. when each period ends. or AWOM).) Last accounting day of the period through the 39th to last accounting day of the period. AMOY. and next year. (Periods can be accounting periods. or any other unit of time.) First period of the accounting year through the 53rd period of the accounting year. If you use ADAY in a criteria statement. If you have defined a prefix on the Datetable Definition panel. you must use the Datetable Definition panel to define which days are accounting days. ADOM. accounting conditions will be taken from the B version of the date table.11 Accounting Conditions To use these accounting conditions. Then you can consult the Date Translation Report in the Reports Guide to see which accounting conditions are satisfied on any given day. you must define at least two periods on the date table. Any day designated by A (or another prefix) on the date table is counted as an accounting day. substitute that prefix for the x in the words below (for example. this year. If you use BDAY in a criteria statement. If you have not defined a prefix. (The end of the accounting year defaults to the last day of each year. First accounting day of the period through the 40th accounting day of the period. production periods. To do this. You must have defined an 'A' date table prefix prior to defining any other prefix for a date table. (The end of the period defaults to the last day of each month. Workday and holiday conditions are always taken from the A version. To use these criteria.

define date tables for two years and designate the end of each accounting year by typing an E on any date.) xWOM1 : xWOM10 xWOM-1 : xWOM-10 Chapter 7. Wednesday. you must designate the ends of two accounting years. Criteria Language 7-47 .11 Accounting Conditions 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. November 14 would be xWOM2. November 7 would be the xWOM1. (The end of the period defaults to the last day of each month. To use these criteria. then Wednesday. (The end of the period defaults to the last day of each month. November 1 through Tuesday.) To use these criteria.) For example. To do this. (Any week with at least one accounting day counts as an accounting week. go through the date table and designate the end of each period by typing a P on any date. if the period ends on Tuesday. you must define at least two periods on the date table. To do this. you must define at least two periods on the date table.) To use these criteria. Last accounting week of the period through the 9th to last accounting week of the period. Therefore.7. (Any week with at least one accounting day counts as an accounting week.) First accounting week of the period through the 10th accounting week of the period. (The end of the accounting year defaults to the last day of each year. November 8 through Tuesday. October 31. go through the date table and designate the end of each period by typing a P on any date. To do this.

.

Chapter 8.EFFDATE= 3 5 3.S=schdule1. ■ Job and schedule criteria changes can be implemented without affecting today's workload.S=schdule1. successor chain. which may be specified as the last two parameters.EXPDATE= 3 3 3 DEFINE JCR N=newjob.EFFDATE= 3 3 3. and delete job or schedule records.EXPDATE= 3 5 3 ALTER JCR N=job1. Using the Autoscan Command File Autoscan command file processing allows you to make arrangements for future database updates without affecting today's workload.EFFDATE= 3 3 3.dcfin(CAIJDCF).CRI='mon or tue'. Using the Autoscan Command File 8-1 . lrecl=80) identified by ddname CAIJDCF. ■ 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.Chapter 8.LIBTYPE=testlib. Example: DEFINE JBR N=newjob. For example.S=schdule1.disp=shr ■ Commands are executed at autoscan time but before any jobs have been selected.LIBTYPE=pds.EXPDATE= 3 5 3 ■ Commands will be executed at autoscan time but before any jobs have been selected. thereby reducing overtime and weekend work.CRI='job1 schdule1'.EFFDATE= 3 5 3. This can be done through batch reports (analyze. 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. Example: //CAIJDCF DD DSN=cai. ■ Database maintenance commands must be contained within a PDS member or sequential DSN (recfm=FB. alter. Commands are executed only if today's date falls within the effective and expiration date.S=schdule1. ■ Database maintenance commands can be set up in advance to define. simulation and forecast).EXPDATE= 3 3 3 ALTER JBR N=job1. You need to specify CAIJDCF in the monitor startup procedure if you need autoscan command file support.

DCF=YES 8-2 Online Guide .SIMWORK=sysda. DCFERR=CONT can be set in CAIJGEN to avoid such shutdown.DCF=YES or REPORT SCDCHAIN N=caschd1.UTILVOL=xxxxxx. ■ It is highly recommended to syntax check those autoscan command file commands before submission or autoscan.SIMVOL=xxxxxx. Example: // EXEC CAJUTIL //CAIJDCF DD DSN=cai.UTILWORK=sysda. 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.DCF=YES or ONLY S N=schdule1 SIMULATE ST=(4 ).dcfin(CAIJDCF). successor chain. ■ All commands will be syntax checked prior to application.UTILWORK=sysda.SIMWORK=sysda.S=caschd1. monitor shutdown may occur if such an error is detected right before autoscan. 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).SIMVOL=xxxxxx.FOR=2.UTILVOL=xxxxxx.UTILVOL=xxxxxx. Otherwise. See the DCFERR parameter in the Systems Programmer Guide.■ Each database maintenance command must have as its last two parameters the effective date and expiration date.UTILWORK=sysda.DCF=YES or ONLY S N=schdule1 FORECAST FD= 3 5 3. analyze. You just need to add the CAIJDCF ddname with the desired DCF dsname and specify DCF=YES at the first CAJUTIL0 command statement.FD= 3 5 3.disp=shr //SYSIN DD ANALYZE SCHEDULE N=caschd1. if an error occurs a message will be issued asking the operator to cancel scheduler or proceed with the remaining commands.FOR=2.disp=shr //SYSIN DD SYNCHK DCF / ■ The batch reports.DCF=YES or REPORT JOBCHAIN N=cajob1.

STATION=4 .EFFDATE= 5 3 3.EFFDATE= 5 3 3. Using the Autoscan Command File 8-3 . 6 SKIP=2. Control and batch report commands are not allowed. DELETE.COLUMNS 1 72 COMMAND ===> SCROLL ===> PAGE TOP OF DATA 1 ALTER JCR NAME=JOBA.STATION=4 . See the Command Reference Guide for more information on the ALTER and DEFINE commands.EXPDATE= 531 3 3 ALTER JBR NAME=JOBA. Chapter 8.JNO= 1.SCHEDULE=PAYROLL.EFFDATE= 5 3 3.EXPDATE= 531 3 7 DEFINED JOBC'S ABEND MESSAGE 8 DEFINE JMR NAME=JOBC.STATION=4 .EFFDATE= 5 3 3.JNO= 1.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.STATION=4 .EDIT ----CAI.SCHEDULE=PAYROLL. Supported Commands: The autoscan command file supports the database maintenance commands ALTER.JNO= 1. 2 CRI='MONDAY AND JOBA'.JNO= 1.EXPDATE= 531 3 5 ALTER JBR NAME=JOBC. and DEFINE for schedules and jobs.DCFIN(CAIJDCF) -------------------------------. 4 EARLYTIME= 715.SCHEDULE=PAYROLL.SCHEDULE=PAYROLL. 9 ABENDMSG=OPCON5.

.

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. Tips This topic is intended to provide you with some helpful hints on using CA-Scheduler.Chapter 9. Chapter 9. We begin with some of the most commonly asked questions and follow with a discussion of some pitfalls. Do not be concerned about reading this chapter in the order that topics appear. Tips 9-1 .

“When Should Autoscan be Performed?” on page 9-4 9.1.2.3. “How Can I Can Create My Own Reports?” on page 9-18 9-2 Online Guide .2. “When Should I Run Forecasts?” on page 9-14 9.1.1.7.1.3.1. “How Can I Prevent Predecessor Loops (Deadlocks)?” on page 9-11 9. Topic Startup Tasks See 9.3.4.1.1.5.6.1.1.1. “How Should I Organize My Schedules?” on page 9-6 9.5.1. “When Should I Run Analyze Reports?” on page 9-12 9.1.3.2.8. “What Is the General Standard for Numbering Stations?” on page 9-4 9.2.1. “How Do I Plan When to Run a New Application?” on page 9-15 9. “What Are Global Parameters and When Are They Used?” on page 9-8 9.3. “When Should I Run Simulation?” on page 9-14 9.2.3.1 Commonly Asked Questions 9.4.3.3. “When Should a Job be Staged?” on page 9-6 9.3.1 Commonly Asked Questions This topic consists of a series of questions that are commonly asked.4.1.9. “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.1.1.1.2. “How Do I Verify a New Application?” on page 9-15 9.2.1. The following table lists the questions with cross-references to the pages containing their responses. “When Is a Job Submitted?” on page 9-7 9.1.1. “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.1. “Should I Use Date Tables or Calendars?” on page 9-5 9.2.

4.4.4.1. “What Happens If a System Crash Occurs?” on page 9-24 Chapter 9. “What Is the Difference Between FORCE. REQUEST.1. and SREQ?” on page 9-20 9. “When Is the PRED Flag Reset?” on page 9-22 9.4.1.1.1 Commonly Asked Questions Topic Daily Processing See 9. “From Where Can I Issue CA-Scheduler Control Commands?” on page 9-20 9.4.1. RERUN.1.1. Tips 9-3 . “What Happens If CAIENF is Shut Down?” on page 9-24 9.6.4.5. SUBMIT. RUN. “What Happens If CA-Scheduler is Shut Down?” on page 9-23 9.2.9. ADD.3.4.

If you specify that the station 39 job is to be automatically started (AUTO START=YES). control statement changes. you always have to manually post these data entry jobs when they have ended. 9.1 Startup Questions 9.1. last-minute changes. backlogs schedules and jobs. 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. then autoscan should be run between 08:00 and 16:00.1 Commonly Asked Questions 9. analyzing the selection criteria and placing the selected schedules and jobs onto the active workload. This includes JCL changes. Run autoscan at a time when your machine load is at a low point. Note: If using the autoscan command file. However. 9-4 Online Guide .1. it starts at its early start time as long as its predecessors and resources are satisfied.1. If your production normally starts at 16:00 and runs during the night with everything completing by 07:00 or 08:00. all predecessor conditions are fulfilled. data entry work. Station 40 CPU processing Jobs start when the early start times are met.1. CPU job processing is automatic unless you override it. and selects the day's workload. it is used at autoscan time. and resources are available.1 When Should Autoscan be Performed? Autoscan is the daily process that purges completed jobs from the CA-Scheduler active workload.2 What Is the General Standard for Numbering Stations? Normally. CA-Scheduler scans the database. 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).9. if appropriate.1. and the like. Running autoscan this way gives the production control area a chance to get everything ready for the day's workload.

“Date Tables” on page 7-15.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. Then when any schedule runs on those dates. A detailed discussion on this matter appears in the 7. The date table prefixed by the letter 'A' is your default production date table. and any number of date tables. 9. use date tables. production. Any time you want to schedule a job based on a combination of two or more cycles.1. They are a bit more complicated to understand. 9. Date tables provide significantly more flexibility than calendars and should be used if at all possible.1.2. or sales period. For most of your application needs.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.1. you just give it that calendar name for selection.1. 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. These print station jobs automatically start when their corresponding CPU jobs complete on station 40 and their predecessors and resources are satisfied. but entail less maintenance than calendars when going from year to year. you must use the date table prefix. You can have up to twenty cycles defined with any one date table. Tips 9-5 . Define these individual days once in a calendar. you cannot use different date table names. however.1 Commonly Asked Questions 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). Date tables also allow multiple accounting periods as well as different holidays.9. Chapter 9.2. The other prefixes are variations upon that date table.

unless it is easily manageable. Before you decide to stage JCL. You can code Driver procedures to automate most of the changes to the JCL and control statement setup.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. Instead. determine how much of the setup can be handled using Driver. the job's JCL is moved from the master JCL file (LIBTYPE field) to the CA-Scheduler active workload.2. This LIBTYPE defaults to the one that appears in the LIBTYPE installation option of the CAIJGEN macro.2 Database Maintenance Questions 9.1 Commonly Asked Questions 9.1 How Should I Organize My Schedules? A schedule should consist of a group of logically related jobs. 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. 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. the weekly schedule is dependent on the daily schedule to complete. For example.2. To have a job's JCL staged. If certain jobs in the schedule do not run every time the schedule is selected. Keep in mind.1. 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. This group of jobs usually belongs to one application.9.1. 9-6 Online Guide . There should not be one schedule just for REQUESTED jobs. A job's EARLY START TIME may arrive before its JCL has been modified in preparation for submission. either. you could define a Payroll schedule containing all the payroll jobs and its selection criteria. This makes interdependencies within applications much clearer. however. 9. do not have a Monday schedule. try to keep application-related jobs together. You can. Do not organize schedules just by frequency. For example.1. but could also be run at the same frequency. most options defined for a schedule apply to all jobs in that schedule. override these options at the job level. but can be overridden at the schedule level and again at the job level. Possibly.

and its resources (SEPDSNs. The job defined at station 39 will be an implicit predecessor of the CPU job at station 40. That is. That means the CPU job cannot be submitted until the job at station 39 has been manually marked as ENDED using the COMPLETE command. Chapter 9. The JCL that is staged is purged from the active workload when its associated job is purged from the active workload.3 When Is a Job Submitted? Once a job's ERLYTIME is met. for example.2. you can use a variety of editor commands to prepare it for submission. Once the JCL is staged. Tips 9-7 . and SEPJOBs) are available. Furthermore. Keep in mind that it will overlay any JCL that may already be in the active workload for the respective job. a fresh copy of the job's JCL will be restaged. This would be for purposes of changing it due to a rerun condition. even though you only change it on Fridays. When the JCL has been changed. In addition to usual text editing. You use the RESTAGE command to accomplish this. have a daily job that only needs to have its JCL or a control statement changed on Fridays. 9. 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. Remember. 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. use the second alternative mentioned above. You could.1 Commonly Asked Questions To ensure that a user at the JCL setup station has enough time to modify and review the staged JCL. all of its predecessors have completed normally.1. you only want to change the JCL on Fridays. you mark the job on station 39 completed with the COMPLETE command. 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. Therefore. then a job can be submitted. you may want to restage JCL for a job with STAGE=NO.9. The job's JCL will always be staged. regardless of whether you had STAGE=YES. the station 39 job has to be manually started or AUTO START=YES must be specified in its definition.

9. suppose a set of jobs cannot start without a particular set of tapes arriving from an off-site location. 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. binary (yes or no). Suppose this is some accounting data. We can choose GBLC04 since we know no one else is using it.1.2. and alphanumeric (up to eight characters). We have to pick a global variable to be set aside for just this purpose. 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. and we give it a name of HERE-NOW. The three types of global parameters are: numeric. 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 .1 Commonly Asked Questions 9.4 What Are Global Parameters and When Are They Used? Global parameters are user-defined conditions that are predecessors.

. .8 . NO NO NO NO . Tips 9-9 . . .12 . . . . . .9. . . . For example above set GBLC04=NULL from globals panel or batch CAJUCMD0. . . NO NO NO NO Character Values: GBLC 1 . . Someone must cause it to happen. . . . . . 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. here-now . . . .3. . . .8 . . . if any schedule or job is waiting for no other reason but this variable. GBLA 5 . It is very important to notice that global parameters are not reset automatically. Autoscan does not reset the global parameters.8 . . . . . . . . NO (for B-type). . . “Globals” on page 4-95. . . . GBLB13 . .4 . . . . 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. . .12 . . GBLA13 .9. . .16 . . . . . . update the value of the global variable: --------------------.CA-SCHEDULER 9.16 . . . At that point. all global parameters are set to zero (for A-type). . .1 Commonly Asked Questions Once the tapes have arrived. .12 . . When you define the criteria for a schedule or job. . . . When you initialize the active workload. NO NO NO NO . . . Chapter 9. . . .4 . . . One rule you have to be sure to follow is: a NOT reserved word preceding a GBLxnn predecessor is NOT recognized. an operator sets the value of the global parameter GLBC04 to HERE-NOW. . . . . then the schedule or job starts. .4 . . . . . . . GBLB 9 . . . . . . From 4. . or null (for C-type). . . GBLC 9 . COMMAND ===> Numeric Values: GBLA 1 . . . . GBLC13 . . . NO NO NO NO . . GBLC 5 . . . . GBLA 9 . . Enter END to exit. . . GBLB 5 . NOT GBLC01=CICS-UP will have the same effect as GBLC01=CICS-UP.16 . Binary Values: GBLB 1 . . xxyy (SCHD) GLOBALS -------------------- . . Therefore.

Remember that when a job is to be interrupted. This method has an added benefit in that it can automate the resubmission process.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. since it depends on everything being valid.2. Either mark the job as ENDED. you can easily see any jobs that are interrupted. This means that when the job terminates normally.1 Commonly Asked Questions 9. the master console (OPERATOR). or both. An alternative method of submitting a job repeatedly is by interfacing with CA-Dispatch. it must be manually posted to do something next such as freeing successors to run. Otherwise. These users can be any user name. Successor jobs are then handled appropriately. another console (OPERnn where nn is the route code from 1 .1. and if evidence is found that the job ran without error. CA-Dispatch can interrogate a report or SYSOUT data produced by a job. or the CA-Scheduler mailbox (MAILBOX). and a procedure like that described for CA-Dispatch can be used to handle the job according to the contents of those messages. CA-Opera can interrogate console messages issued by a job. a COMPLETE command can automatically be sent to CA-Scheduler. You may not know how many times it will take each day. use the Job Interrupt field in the job's Job Messages panel. CA-Opera. a RERUN or SUBMIT command could be sent. Successors of this job will not run until the job is ended manually using the COMPLETE command. At any time during the day. To do this. When a job does get interrupted. you can go into the status panels and display all jobs that are in an INTERRUPTED status.15). or resubmit the job using the RERUN or SUBMIT command. you specify INTERRUPT=YES in its Job Definition panel. or a message could be sent to a user to verify the output. 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 can then run the job by using the RERUN command. 9-10 Online Guide .9. So. its status will be set to INTERRUPTED instead of ENDED. you can have a message sent to up to four users.

9. JOBX is a predecessor of JOBA. It is extremely difficult to detect a deadlock unless you use the Analyze Report.1.1. you can use the LIST=NO or LIST=ERR operand to request that just the errors be reported. each with many predecessors. This is especially useful for dynamically ADDed jobs to ensure that the added job did not create a deadlock. run the CA-Scheduler utility program (CAJUTIL0) with the batch command ANALYZE. Chapter 9. but cannot run until JOBB has ended.1. Tips 9-11 . JOBX requires JOBB to run first. You can check specific jobs and/or schedules or you can give a range of jobs and/or schedules. Since JOBB will not run until after JOBA has ended. As you can see. You should produce it any time the criteria for a job or schedule is changed.1. “Analyze Job” on page 6-4 and 6. JOBB requires JOBA to run first.1 How Can I Prevent Predecessor Loops (Deadlocks)? Predecessor loops are also called predecessor deadlocks. Another way to detect deadlocks is to generate the Successor Chain List report either from batch or online in the 6.2.1 Commonly Asked Questions 9. You could imagine how complicated this would be to resolve if we had a hundred jobs.3 Questions About Analyzing the Database 9. 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. Any time you make significant changes to jobs. you can analyze all schedules that begin with the first three characters PAY.10. we have a deadlock. see 6. For example. Instead of getting the comprehensive Analyze Report.1. run this report to ensure that your changes have not introduced deadlocks. schedules or both.3. A predecessor deadlock exists when two jobs end up requiring that the other execute first. To obtain the Analyze Report. “Analyze Schedule” on page 6-6. “Successors” on page 6-21. For example: JOBA requires JOBX to run first.

1. if JOBA and JOBB in SCHDA both run on Mondays and Wednesdays. Criteria is evaluated as a series of logical TRUE and FALSE conditions. When it evaluates JOBB. 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 . CA-Scheduler realizes that it has to evaluate JOBB first. the jobs are evaluated in alphabetical order within each schedule. 9. neither job is selected.3 What Effect Does a Deadlock Have? When job predecessors loop.1. SRR.2 When Should I Run Analyze Reports? The analyze report allows you to see errors that you might have made while defining SBR. it detects the deadlock with JOBA. before looking at any jobs.2 SCHDA JOBA. CA-Scheduler evaluates all schedules first. Deadlocks can have some strange effects on your workload. it treats the predecessor as being not selected.9. The order that CA-Scheduler evaluates criteria can have an impact on how deadlocked jobs are selected. 9. 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. Since the criteria of both JOBA and JOBB evaluates to a FALSE. Example 1: When CA-Scheduler is evaluating criteria and detects a deadlock. and JSR records.1 Commonly Asked Questions One technique for eliminating deadlocks is to use the CA-Scheduler job number (JNO) feature when defining jobs. JMR. SCR.3. The schedules are evaluated in alphabetical order. This report should be run periodically to ensure you have no definition errors to these records. Again. Example 2: This order changes when predecessors are included in criteria. and seemingly unrelated changes can have unexpected results on how work is selected. For example: JOBA SCHDA has criteria of JOBB SCHDA JOBB SCHDA has criteria of JOBA SCHDA When JOBA's criteria is being evaluated.1 SCHDA WED This allows the jobs to run without any deadlock. JCR. A predecessor must be evaluated before its successor. JIR. During autoscan. SNR. with deadlocks acting as FALSE. JBR. it is called a deadlock. After all of the schedules have been evaluated. SIR. For example. CA-Scheduler evaluates the jobs in each schedule that was selected. JRR.3. but on Mondays JOBA must run first and on Wednesdays JOBB must run first.

then only JOBA is selected. If today is a workday.9.1 Commonly Asked Questions In this case. If we moved JOBC from schedule PAYROLL to schedule XYZ (which comes after schedule SCHDA). Example 4: The NOT keyword can also cause some confusion. which is FALSE. For example: JOBA SCHDA has criteria of NOT JOBB SCHDA JOBB SCHDA has criteria of NOT JOBA SCHDA Again. As we saw above. Tips 9-13 . JOBB. which is a TRUE. but has to move on to JOBB. Chapter 9. JOBA must wait for it. JOBA is not selected. however. has an OR condition. In this example. Because JOBB was selected. JOBB must be evaluated before JOBA. While evaluating JOBB. JOBA's criteria now becomes NOT TRUE. JOBC is selected. the jobs are evaluated in the order JOBC. since JOBA's criteria references it. however. JOBA. no criteria PAYROLL comes before SCHDA. When CA-Scheduler gets back to finishing JOBA. JOBA and JOBB have already been evaluated as in Example 3 Part 1. the deadlock with JOBA is detected. so JOBA is done first. Example 3: Look at an example of how this ordering can affect deadlocks: Part 1 SCHDA has auto select set to YES. but detects that JOBB must be done before JOBA. JOBA's criteria. it treats the "JOBB SCHDA" as a FALSE condition. The criteria for JOBB is then evaluated as NOT FALSE. JOBC must be evaluated before JOBB. CA-Scheduler tries to evaluate JOBA first. so JOBB must be evaluated first. JOBA's criteria evaluates as FALSE OR TRUE. And since JOBB was selected. so JOBB is not selected. so the deadlock is detected. CA-Scheduler then backs up to finish JOBB. Since JOBB was not selected. JOBC needs JOBB. This happens because by the time CA-Scheduler gets to JOBC. But because JOBA was selected. We can define another job in schedule PAYROLL as: Part 2 PAYROLL has auto select set to YES. JOBA is selected. which is TRUE. the deadlock is detected. 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. JOBB will be selected. JOBA needs JOBB. JOBA will not wait on it. so the jobs in schedule PAYROLL are evaluated before the jobs in schedule SCHDA. While evaluating JOBB. JOBB must wait for it! None of the jobs will run without manual intervention. so JOBA is selected. Since JOBA was selected. JOBB is selected. But JOBB needs JOBA. the FALSE from the deadlock is ORed with the TRUE from WDAY.

It may turn out that it does not absolutely have to run on Wednesdays.1.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. Another reason for running forecasting would be to obtain a hardcopy of run books for a specific day. It provides you with a plan of what to expect and when to expect it. You can make these decisions before establishing policy and before finding that you do not have the resources to handle it. 9.1 Commonly Asked Questions 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. you can cause the simulation to change the current average time for jobs. if you find that the new application cannot fit on Wednesdays without making a lot of jobs late. You can do this by only including the schedules and/or jobs that you desire. simulation is run to determine the effect of a new application on the rest of the workload. run forecasting to verify the selection. This helps you determine in advance whether the requested frequency of running the application is viable. you could try to run it on another day. resources. you can add the new tape drives. or schedules and/or jobs within a set of days. When establishing a complex criteria for a schedule or job. Normally. but neither will run automatically because they are waiting on each other. you can optionally use the simulated start times as the early time of the jobs for submission. Simulation produces a set of detailed reports showing when jobs will run and whether they will complete on time. When you do.3. 9-14 Online Guide . group of days. When you do this.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. it ignores the early start time that you had on the database.3. 9. or by using the FACTOR=factor keyword on the same commands. You may also want to run simulation as part of normal daily production to determine what is going to happen that particular day. The requesting department may be able to run it on Thursdays just as easily.9.1. and predecessor constraints are taken into consideration. Simulation could also be run to determine the effect of adding new resources. The skip option on the JBR is not honored on this report. to reflect the faster CPU. This would be the primary reason for running forecasting. These run books contain job information obtained from the database and from workload documentation entries specified by the DISPLAY KEY field. By using the OVERRIDE RESOURCE command. That is. Such things as job concurrency. such as tape drives or a faster CPU.

1. you can run the application in test mode with the normal day's production and review its effect on the day's workload.1. To obtain this report.9. From this report. Now run analyze. date tables.1. and stations that are not on the database. you have a complete list of everything that you keyed in for the new application. Step #1: Analyze Report: The Analyze Report provides a detailed audit of all information pertaining to the schedule(s) being requested. You can also obtain it by issuing the ANALYZE command online in the schedule maintenance and job maintenance panels. Sometimes you may prefer to print just the errors using the LIST=NO option.3. predecessors.3. use the JCL described in the Reports Guide. You also get a set of error messages that identify predecessor/successor deadlocks as well as any references to jobs.7 How Do I Verify a New Application? You should follow these five steps in verifying a new application. Review this report carefully.6 How Do I Plan When to Run a New Application? You first define your application completely. 9. “When Should I Run Simulation?” on page 9-14) with an ONLY command just for the schedules in the new application.3. see the SIMULATE and SYNCHK GROUP commands in the Command Reference Guide. This will ensure that everything is the way you want it. Tips 9-15 . For details on this function. 9. Temporarily set LIBTYPE = TESTLIB in schedule base records.. Then run simulation or forecast (see the discussion of simulation on 9.5. Once everything looks correct. This example analyzes all schedules which begin with the characters "APPL1S": // JOB . To do this you must have CA-JCLCheck installed and active on your system.. //STEP1 EXEC CAJUTIL //SYSIN DD ANALYZE SCHEDULE NAME=APPL1S // Chapter 9.1 Commonly Asked Questions Another reason to run simulation is to check the syntax of the JCL before actually processing the jobs. The skip option on the JBR record is not honored on this report.

// JOB . If you have jobs that are backlogged. a good chance exists that they may have a predecessor deadlock..1 Commonly Asked Questions Step #2: Forecast: Run the forecast component for at least a month of dates and obtain the Job Summary Report (SUMMARY). The following example contains three schedules to be selected over a one month period with only the Job Summary Report being produced. 9-16 Online Guide . and a monthly. Also. check the accuracy of early start times and run times. this may only be three days: a daily. Through use of the ONLY command. if jobs are backlogged. you will obtain just the Job Summary Report. Through use of the FORECAST command with the object of SUMMARY. During a month. a weekly. only the new schedule names are supplied causing just the new application to be analyzed. You would use the ONLY and SIMULATE commands to accomplish this. //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.9.. Then you want to verify that they were scheduled in the proper sequence: predecessor relationships are properly followed. You want to verify that the jobs were selected on the days on which you intended them to be. You do this for the schedules that were built for the new application.

9. CA-Scheduler will submit jobs that execute the CAJUTSTB test program. Use the STATUS command to verify that jobs are scheduled correctly. you should develop Driver procedures to automate the JCL changes and the control statement setup. By doing that.1 Commonly Asked Questions Step #4: Test: Run the schedule in test mode. starting at the next autoscan. to pass a nonzero completion code. Keep in mind that since LIBTYPE=TESTLIB. Chapter 9. Use the online tracking RUN S command. You can use TESTPARM on individual jobs' base records to cause the test program to abend. and with the correct predecessors. to your production LIBTYPE. the schedule and its jobs will be automatically selected. Also ensure that AUTO SELECT is set to YES. in the SBR. on those dates. Step #5: Driver: If jobs in a schedule require frequent JCL changes or control statement setup before job submission. After the jobs in the schedule run to your satisfaction. and to have it wait for a number of seconds. Once you do that. you can test the effect of abending and failing jobs on the rest of the schedule. you can now alter LIBTYPE=TESTLIB. Tips 9-17 .

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.8 How Can I Can Create My Own Reports? As part of CA-Scheduler you have a component called CA-Earl.3. The following lists the reports and the names of the source members in which the source is contained.1 Commonly Asked Questions 9.1. 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 . CA-Earl is a generalized report writing facility for which you are provided a set of sample reports.9.

1 Commonly Asked Questions 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. Tips 9-19 .9. Chapter 9. See the Reports Guide for descriptions of each of these samples in detail.

4. ADD. and the Command Reference Guide.3. RERUN. or OS PURGED. For detailed information about using these commands.4. Since you have the ability to cause any CA-Scheduler control command to be issued.2 What Is the Difference Between FORCE. Prefix the command with "F taskname.1 From Where Can I Issue CA-Scheduler Control Commands? Quite a few control commands are provided within CA-Scheduler.1. You can test against the status of other jobs. You can even issue these commands based on conditions coded in an IF statement. 4.1 Commonly Asked Questions 9.6. ENDED. “Job Status” on page 4-16. You cannot FORCE a job that has JCL already in the queue if the status is SUBMITD. user-defined globals. “Schedule Status” on page 4-2. any schedule.1. see 1. Batch Program (CAJUCMD0): Control commands can be issued from a batch program called CAJUCMD0. The default taskname is CASCHD.". Operator Console: Any control command can be issued from the operator console by directing it to CA-Scheduler. SUBMIT IN PROGRESS. RUN. and just about anything else you can think of.4 Daily Processing Questions 9. for example. REQUEST. This means that you could embed a step calling this program in your production JCL that could take certain actions dependent on.1. 9-20 Online Guide . It also can cause a job to be submitted regardless of why it is currently waiting. CA-Scheduler offers a number of different places where you can enter the control commands. or set global variables. or UNKNOWN. 4. start another job.2. 9. “CA-Scheduler Commands” on page 1-10. FORCE Causes a schedule on the active workload to be started regardless of why it is currently waiting. The following describes how each command works.9. However. you could send messages to specific users or the operator console. SUBMIT. and SREQ? Each of these commands causes a job or schedule to be activated in some form. 4. You can FORCE a job as long as its status is not STARTED. They do everything from displaying status to shutting down CA-Scheduler.1. This is done to make it practical for you. “Commands” on page 4-43. condition code settings. The "Tracking Commands" chapter in the Command Reference Guide describes this in detail.

With the RUN command. predecessors. ended. then the older one is purged from the active workload. you only use ADD for one-time jobs.1 Commonly Asked Questions SUBMIT and RERUN Cause a job to be resubmitted.9. Use RERUN or SUBMIT instead of FORCE when a job has abended. you can place the schedule or job in a HELD status. If the job or schedule is already on the active workload (it would be in a completed or canceled status). it will be set to START status. If you do not specify a schedule name. and resources are properly evaluated. If it is on the database. RUN Causes a schedule or job that exists on the database to be added to the active workload. The only difference between SUBMIT and RERUN is which Driver parameters they use: SUBMIT uses the normal parameters while RERUN triggers the restart parameters. where xxxx is the SYSID of the system from which the command was issued. you can give it a date so that only applicable jobs in the schedule are selected. when you use the RUN command to pull in a schedule. or been interrupted. canceled. This is different than FORCE and RERUN in that a fresh copy is obtained and all times. A REQUESTED criteria causes the schedule or job to be selected every day and placed on the active workload. This means it is moved from the INACTIVE queue to the ACTIVE queue. you would use this command instead of the RUN command if you wanted to change any keyword values. failed. Once in the ACTIVE queue. These schedules and jobs are ones that were not selected in today's workload or they may have been canceled or completed. RERUN substitutes DRIVER restart parameters if LIBTYPE=DRIVER is defined and the JCL is not staged or restaged. Further. You do not have to specify a schedule name. The job does not have to be on the database. The way that a schedule or job is made 'on-request' is by giving it a selection criteria of REQUESTED. It will not wait for an early time or for predecessors: the job is submitted immediately. ADD Causes a job to be added to the active workload. it is handled normally. This will give you a chance to take any other manual actions you deem appropriate. Tips 9-21 . If the job is on the active workload and not completed or canceled. Chapter 9. If you do. it will be added to that schedule. REQUEST and SREQ Cause a REQUESTED schedule or job to be activated. it will use a schedule name of $DYNxxxx. Normally. then the RUN command is in error. FORCE is used to make a job start the first time. If the schedule in which the job exists is not in START status.

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. For example. 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. When PRED precedes a schedule name or job name.9. ■ Use FORCE to submit jobs if you are willing to violate their reasons for waiting. A separate subtopic devoted to requested jobs is in the next chapter.MASTER. the REQUESTED schedule or job is moved to the ACTIVE queue along with all its successors. 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. ■ Use RUN to submit jobs in the database if you do not need to change their keywords. but is a predecessor condition only. the predecessor is to complete within the autoscan day. 9.1 Commonly Asked Questions The difference between REQUEST and SREQ is that. When you do not use the keyword PRED. ■ Use REQUEST or SREQ for requested jobs. but you need to change its keywords. then it must have been closed at least once during the last week.MASTER must have been closed at least once between each running of that job. If you plan to use this facility. you should review it. 9-22 Online Guide . with REQUEST. the output data set JOBA. an exception exists. If the job is run weekly. If the PRED is a schedule or job that is in today's workload. job names cause selection if the predecessor job was selected. it will wait for that specific one to complete. it indicates that the schedule or job is to wait for a predecessor to complete. Normally in the selection process (during autoscan). The SREQ command handles successors differently: SREQ does not activate a successor if it involves other REQUESTED jobs. it is not used in determining selection.4. All other criteria rules still apply.3 When Is the PRED Flag Reset? When you use the PRED keyword in the criteria language. However. Summary: For jobs in the active workload: ■ Use RERUN or SUBMIT for jobs that ended abnormally or were canceled.1. if a job has a predecessor of PRED DSN JOBA.

so is marked UNKNOWN JOB2 was started. 3. Example: CA-Scheduler has submitted four jobs: JOB1. Tips 9-23 . If RHOLD=YES was specified.9. These jobs are not submitted by CA-Scheduler until a RELEASE AUTO command is issued. so is marked STARTED JOB3 was submitted. is not currently active. For MCPU=YES. CA-Scheduler leaves the status as STARTED.4 What Happens If CA-Scheduler is Shut Down? Every time CA-Scheduler is started. If a job was in STARTED status. CA-Scheduler queries JES to determine if the job is still active. either from a normal shutdown or from a system crash. JOB2. 4. this is schedules with the local system's SYSID. the status is changed to UNKNOWN. then the job will NOT be tracked. Reads the active workload for schedules that belong to the local CA-Scheduler. and JOB4. 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. If the job is still running. CA-Scheduler does not know the current status of the job. If a job was in SUBMIT IN PROGRESS or SUBMITTED status. If MCPU=NO. or the schedule has not yet started) are marked AUTO RCVRY HELD.4. then all jobs that have not yet been submitted (that is. 5. so is marked UNKNOWN JOB4 was submitted. 2. this is all schedules.1 Commonly Asked Questions 9. JOB3. These events are used to "catch up" with jobs that may have started or ended while CA-Scheduler was not active. is still running. 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 Chapter 9. waiting on predecessors. If an event is received for a job currently in UNKNOWN status. Otherwise. the job is changed to UNKNOWN status. If a JOBINIT has not been received for the job. it takes the following steps: 1. waiting on early start times. the job's status is updated accordingly as long as CA-Scheduler has received a JOBINIT event for the job. Time 10:05 10:06 10:07 10:08 10:09 Event JOB1 and JOB2 start.1. CA-Scheduler requests any events from CAIENF since the last event received.

they are left as UNKNOWN.4. waiting on early start time or waiting on predecessors) will be marked ENFDOWN HELD. Jobs that were submitted now have a status of UNKNOWN.1 Commonly Asked Questions At the end of CAIENF recovery. CA-Scheduler will attempt to hold the jobs in JES. CA-Scheduler will show the jobs as ENFDOWN HELD.4. For jobs that have been submitted but have not yet started. 3.1. Any jobs that have not yet been submitted (that is. CA-Scheduler may mark a job as successful when one of these steps received a bad return code. Release all jobs marked ENFDOWN HELD. 9. CA-Scheduler changes its status to STARTED. they are marked STARTED. Otherwise. CA-Scheduler will: 1.4. Jobs that were STARTED are checked to see if they are still running. 2. When it starts. Any jobs that have already started will be marked UNKNOWN. 9. 9-24 Online Guide . See 9. the same steps are taken as for a normal start of CA-Scheduler.1. Jobs that were submitted and held in JES are released. “What Happens If CA-Scheduler is Shut Down?” on page 9-23.4. When CAIENF is started again.5 What Happens If CAIENF is Shut Down? | CA-Scheduler takes the following actions when CAIENF is shut down: 1. 2. If the jobs are still active.6 What Happens If a System Crash Occurs? When CA-Scheduler is started up after a system crash.1. Note: Any steps that finished while CAIENF was not available are not reported to CA-Scheduler. only JOB4 is still marked UNKNOWN. its status will change to STARTED. 3. If the job subsequently starts. CA-Scheduler does not know if the job ran while CAIENF was down.9.

If the UNKNOWN job needs to be rerun. UNKNOWN status jobs will probably have to be resolved manually.1 Commonly Asked Questions 9.9. If an UNKNOWN job has successfully completed. Jobs in UNKNOWN status may resolve themselves or may require manual intervention. you can use the FORCE command. If CAIENF is restarted or the system crashes.5 What Do I Do with Jobs in UNKNOWN Status? The STATUS UNKNOWN command displays jobs in UNKNOWN status. Chapter 9.1. Tips 9-25 . A normal restart of CA-Scheduler should automatically resolve all UNKNOWN status jobs. you can use the COMPLETE command (with CPU=Y) to inform CA-Scheduler.

not a pitfall. the predecessor JOB3 is ignored when you issue a RUN JOB3A command because JOB3 has been canceled but is still on the active workload. Suppose that JOB3A has JOB3 as a predecessor.6 Pitfalls 9.6.1. be sure you are on the correct line. If you purge JOB3 before issuing the RUN JOB3A command. there is no reason to cancel a schedule and then the jobs in that schedule. the pitfall: Pitfall When keying in a command to the left of a schedule or job in the Status panels. here is a clarification. JOB4 always waits for JOB3. JOB2 requires JOB1 JOB3 requires JOB2 and so on. that they are processed sequentially and stop being processed upon encountering an error. 9. JOB3A waits for JOB3 to complete. For example.6. You can manually override this with a POST or FORCE command. It is easy to cancel the wrong job.1. whether you also PURGE it.1.2 Canceling and Purging a Job Suppose you have a schedule that consists of four jobs: JOB1 through JOB4.1 Commonly Asked Questions 9. Therefore. You have to RUN JOB3 to put JOB3 back on the active workload. You can even issue more than one command at a time. Do not use the PURGE command unless you plan to put the job back on the active workload by issuing a RUN command. While on the subject of control commands in status displays.9. If you CANCEL JOB3. If JOB3 is canceled and not purged.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. Just remember. 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. when using the commands in this manner. 9-26 Online Guide .

1. Tuesday's version will never be run. JOB5 will never be submitted.6. it does not finish before the next autoscan (meaning it has been in the system for 48 hours). however. When a schedule gets backlogged (autoscan occurred before the schedule completed) due to the first autoscan occurring. be aware that the jobs on the active workload will be evaluated based on the most current data on the database. If. Pitfall When changing predecessor criteria on the database for jobs that are selected and are already on the active workload. JOB3. where JOB2 requires JOB1. the new schedule that is loaded is evaluated for the autoscan day on which it is loaded. JOB2.4 Backlogging Jobs Over Two Autoscans in $MVS. Therefore. it will require JOB4. but it does not run on Wednesday. You then add JOB4 and change the predecessor criteria of JOB5 to now also require JOB4. CA-Scheduler reviews its predecessor criteria as it exists on the database. It will always be awaiting JOB4. JOB3 requires JOB2.1 Commonly Asked Questions 9. Always watch backlogged work carefully.3 Changing Criteria on Selected Jobs When a schedule or job has been selected. $DYN and User Defined Schedules The subject of backlog is covered in a topic called 10. The schedule has been selected and is on the active workload. Tips 9-27 . What this means is that if you have a schedule of four jobs: JOB1. There is no cleanup for the jobs that are in ENDed status. Chapter 9. This means that if a schedule that is selected on both Monday and Tuesday and has its Monday's version backlogged until Wednesday.4. That is because the evaluation takes place when Monday's schedule completes which is Wednesday.6. “Backlogged Work” on page 10-13. If this happens. but JOB4 was never selected. Pitfall Backlogged work that goes beyond a 48-hour period can be lost if not monitored carefully. If JOB5 had not yet started. when it is evaluated to start.1. when it does finish. and JOB5. Do not change the criteria of active jobs unless the job is canceled and purged off the active queue and then rerun. and JOB5 requires JOB3. we recommend that you CANCEL and PURGE JOB4 and then issue an ADD command for JOB4. it is handled as you would expect.9. 9. The $MVS and $DYN schedules also get backlogged if these schedules never go to ENDed status.

predecessor evaluation of schedules and jobs takes place based upon the current value of the global parameter regardless of when that value is set.6. 9-28 Online Guide . all unsatisfied predecessors are re-evaluated. Therefore. those global predecessors are marked as satisfied. They are not reset at autoscan time. you must set it to another value. the pitfall: Pitfall A global parameter only gets set.9. That is. If any schedules or jobs are waiting for that global parameter to take on that value. Once a value of a global parameter is set.5 Resetting Global Parameters Global parameters are initialized only when the active workload is initialized. it is only reset when someone actually changes its value to something else. No such thing as resetting a global parameter exists. it means that global has never been set since the last format of the active workload. Once a global parameter is set to a specific value.1 Commonly Asked Questions 9. 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. If you want it reset. 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.1. Formatting of the active workload causes all globals to be reset to their default values.

Each topic stands on its own so you can jump from subject to subject. Techniques 10-1 . Chapter 10.Chapter 10. the topic resembles a tutorial. techniques are discussed while in other cases. Techniques This chapter is intended to clarify various areas within CA-Scheduler. In some instances. Do not be concerned about reading these topics in the order they are presented.

PRED. 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 . 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. 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.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.1 Criteria Language Examples Relating to Criteria Rules 10.

Neither reason code nor the calendar criteria have anything to do with predecessor evaluation. the predecessor evaluation might not meet expectations. this criteria is satisfied. However.ONE As soon as one of these two OR's conditions is true. the following criteria: OR (WEEK-DAY AND JOB1 SCHD1) (WEEK-END AND DSN DATASET. they control only SELECTION. Note: Under Rule #2.1 Criteria Language Examples Relating to Criteria Rules Rule #4: Reason codes and calendar criteria have no effect on predecessor evaluation at all. Techniques 10-3 .1: (WEEK-DAY AND JOB1 SCHD1) JOB1. The recommended way to get the desired results (different predecessors on different days) is to code two different job numbers with different criteria: JOB1. So if JOB1 runs and ends or the DSN DATASET. It will be evaluated as: JOB1 SCHD1 or DSN DATASET.ONE gets updated.ONE (the OR stays an OR).2: (WEEK-END AND DSN DATASET.10.ONE) The job will always be selected because it is always either WEEK-DAY or WEEK-END.ONE) is evaluated for predecessors as: JOB1 SCHD1 OR DSN DATASET. the job runs.ONE) Chapter 10. If the following criteria is coded: OR (WEEK-DAY AND JOB1 SCHD1) (WEEK-END AND DSN DATASET.

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. The job dependency would then become 'JOB1 AND JOB2 AND JOB3' since all three jobs were selected. if JOBA and JOBB are selected to run today. it will be selected every day. but will not run unless requested. or JOBD is also selected.10.2 More Examples of Criteria Language 10. JOBB. For example. JOBC.2. then JOBX will run twice. then run job on TUES. JOBC. any other jobs which are a successor to JOBA (in this case.2. 10.2. For example. JOB1 and JOB2 and JOB3 are all selected to run.2 More Examples of Criteria Language 10. once being dependent on JOBA to complete. JOBB. (The 'OR' condition becomes an 'AND' condition for job dependency. and JOBD are all successors).3 Example 3 JOBA JOBB JOBC JOBD REQUESTED JOBA JOBB JOBC Because JOBA is a requested job. 10. then all of these jobs will also be selected and put in the inactive queue. then run job on MON unless MON is also a holiday.2.) 10-4 Online Guide . suppose that on any given day. and once being dependent on JOBB to complete.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. Because JOBA is always selected.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. 10.

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. In other words.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 JOBC AND JOBD will run. However. with JOBB being a predecessor to JOBC. because both JOBA and JOBB were selected on FRIDAY. the criteria for JOBD will become 'JOBA AND JOBC' (JOBB is disregarded because it was not SELECTED to run on WED).2 More Examples of Criteria Language If you have a job (JOBA) that needs to run Monday through Friday if JOB1 and JOB2 are selected. (if FRIDAY is not a WDAY).10.5 Example 5 JOB NAME JOBA JOBB JOBC JOB CRITERIA WDAY ( WORK DAY ) FRI ( FRIDAY ) JOBA OR JOBB On WDAY. then all three jobs will run with JOBC waiting for both JOBA AND JOBB to finish before being released. JOBA AND JOBC will run. Remember that the 'OR' condition becomes an 'AND' condition when dependency is determined. with JOBA being a predecessor to JOBC. JOBA AND JOBB AND JOBD will run. and runs on Saturday and Sunday when JOB3 is selected. with JOBD waiting for both JOBA AND JOBB to complete. On WED. Techniques 10-5 . Chapter 10. then JOBB and JOBC will run. 10. On FRI. then JOBC criteria becomes 'JOBA AND JOBB' rather than 'JOBA OR JOBB'. such that on WED. if FRIDAY is a WORKDAY.2. with JOBD waiting for both JOBA AND JOBC to complete.

the job will not run until JOBA completes.2 More Examples of Criteria Language 10. If a job's criteria is 'JOBA SCHD1'.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. it means that the job will only be selected when JOBA IN SCHD1 is selected. 10-6 Online Guide . For example: GDG DATA. job names and schedule names.10. When you specify the following criteria record for JOBA (MON AND JOBB AND GBLC 2=TPDWN) OR (TUE AND JOBC) At autoscan time. Selection Criteria are evaluated at autoscan time. these control whether a job is selected for today's workload.2.SET.ONE PRED JOB2 SCHD1 GBLC 2=TPDWN JOB1 SCHD1 DSN DATA. since they play a part only in deciding if the job is selected today.ONE MVS JOB1 NJE JOB1 * Some types of criteria. 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.SET. function both as selection and predecessor criteria. these control when a job runs. For example: SUN WEEK-DAY WDAY JAN 12TH JOB1 SCHD1 PREDECESSOR CRITERIA Evaluated both at autoscan time and continuously during the daily processing.

Assume JOBC is also in Monday's workload. as each job runs it is removed from the 'internal criteria' (CA-Scheduler list of what this job is waiting for). RESOLUTION: Change to two different job numbers with two different criteria: JOBA. the criteria is re-evaluated as: GBLC 2=TPDWN OR JOBC After JOBC runs.1 : MON AND JOBB AND GBLC 2=TPDWN JOBA. the selection-only criteria are ignored since they have already been evaluated.2 : TUE AND JOBC Chapter 10. The OR in the above criteria is respected because of GBLC02 specification. After JOBB runs.10. Any other criteria (like GBLC02 OR PRED OR GDG OR DSN) causes the OR to be preserved. Techniques 10-7 . ORs are changed to ANDs when their parenthesized criteria statements involve only CA-Scheduler controlled jobs or schedules. the job will take off when the OR condition is true. since the OR is preserved. 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.2 More Examples of Criteria Language During predecessor evaluation.

The only way they can be removed from the INACTIVE queue is using the control command REQUEST or SREQ.1 Discussion On-request schedules and jobs are ones that are selected every day.3 On-Request Schedules and Jobs 10. The SREQ command handles successors differently: SREQ does not activate a successor if it involves other REQUESTED jobs. 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. in case they are needed. All schedules and jobs that have not been requested by the next autoscan are purged from the CA-Scheduler active workload. When the autoscan process runs. this topic sometimes causes confusion.3. This means that you cannot determine in advance whether the schedule or job will be needed on any particular day. specify REQUESTED after job and schedule names in selection criteria whenever possible. They remain in an INACTIVE status until they are activated by a control command. all REQUESTED schedules and jobs are selected along with their successors and placed in the CA-Scheduler active workload in an INACTIVE queue. a Gregorian calendar reserved word. they are placed in the ACTIVE queue and will then be handled as normally selected jobs. 10-8 Online Guide . so we will discuss it further.10. 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. However. An important difference between the REQUEST and SREQ commands is that REQUEST also places the successor schedules and jobs in the ACTIVE queue.3 On-Request Schedules and Jobs 10. You define an on-request schedule or job using REQUESTED. This explains the basics about how REQUESTED schedules and jobs are handled. and placed in an INACTIVE queue. When removed from the INACTIVE queue. in its selection criteria. regardless of what BACKLOG values they had defined.

3.10. 10. 10.2 Criteria Language Subtleties The best way to explain these subtleties is with examples.2.2. Techniques 10-9 . all three jobs will be placed in the INACTIVE queue every day.3. 10.1 Example 1 Job JOBA JOBB JOBC Criteria REQUESTED JOBA JOBB In this example.3. Although you should always specify schedule names with job names in criteria statements. 10.4 Example 4 Job JOBA JOBA1 JOBB Criteria REQUESTED None JOBA OR JOBA1 Chapter 10. Any other day.2. it will be treated as a requested job. it is placed in the ACTIVE queue and it does not have to be requested).3 On-Request Schedules and Jobs 10.2.2 Example 2 Job JOBA Criteria MON AND REQUESTED JOBA will be placed in the INACTIVE queue every Monday. they are omitted in the examples below to keep things simple.3.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. Each example assumes that the jobs described are all contained in the same schedule.3.

If no requests are made. 10. JOBA and JOBB will be placed in the INACTIVE queue. 10-10 Online Guide . JOBA1 will be run whenever its conditions allow (if none exist. you could request JOBB without requesting JOBA). 10. If JOBA is not requested. JOBB will always wait for JOBA1 (that is.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.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.3. all jobs will be selected. it will be purged from the active workload at the next autoscan. This is because JOBB got selected because of JOBA1 which is selected whenever the schedule is selected.2.2. JOBB will always wait for JOBA1. The ordering of these predecessors is important as you will see with the next example.3. If JOBA is requested (with the REQUEST or SREQ command). JOBB is placed there because JOBA is the first predecessor specified and it is a REQUESTED job. JOBA and JOBB will be purged from the active workload at the next autoscan.3 On-Request Schedules and Jobs In this example. JOBB will automatically be requested and will wait for both JOBA and JOBA1.10. both jobs (JOBA and JOBB) will be moved to the ACTIVE queue. When the operator command REQ J N=JOBA is issued. but only JOBA is placed on the INACTIVE queue. but will only wait for JOBA if JOBA is requested (using the operator command REQUEST or SREQ) before JOBA1 completes. it starts immediately). All three jobs will be selected.

JOBA will not be considered a predecessor of JOBB unless JOBA is requested with the REQUEST or SREQ command before JOBB is submitted. in this case. only JOBA1 would be moved to the active queue.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.3 On-Request Schedules and Jobs When the operator command SREQ J N=JOBA is issued. CA-Scheduler will not submit JOBB until JOBA has completed. 10. but rather each of them only require JOBA to be selected. When the operator command SREQ J N=JOBA is issued. Once JOBA and JOBB are both in the ACTIVE queue. and JOBC will be moved to the ACTIVE queue having the same result.3.3.2.2. 10. Chapter 10. That is. JOBB.7 Example 7 Job JOBA JOBB Criteria REQUESTED MON OR JOBA On Mondays. When the operator command REQ J N=JOBA is issued.10. This occurs with JOBB and JOBC since neither of them are requested jobs. JOBB will be added to the ACTIVE queue and will not wait for JOBA unless it is also in the ACTIVE queue. If JOBA1 were the requested job. JOBB will not be moved since it has the criteria AND REQUESTED which must be satisfied. JOBB and JOBC will be moved to the ACTIVE queue. then JOBA1 and JOBB would be the ones moved to the ACTIVE queue. It is not satisfied using the SREQ operator command with its predecessor JOBA. To move JOBB to the ACTIVE queue. as issuing the REQUEST command. If the operator command SREQ J N=JOBA1 were issued. This is because JOBB was selected today for reason code 01 (the successor to JOBA). JOBA. in this case. JOBA. use the REQUEST or SREQ command. Techniques 10-11 . only job JOBA will be moved to the ACTIVE queue.

10.10. but JOBC and JOBD are not. just SREQ both JOBA and JOBA1. That is because JOBC's criteria includes the REQUESTED keyword. We should focus on what happens when the SREQ command is used with JOBA.3.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. only JOBA is moved to the ACTIVE queue. and JOBA1 (JOBD's predecessor) was REQUESTED. To move JOBD to the ACTIVE queue. 10-12 Online Guide . At AUTOSCAN time. JOBA and JOBB are moved to the ACTIVE queue.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. When the control command REQ S N=SCHDA is issued.2. In this case. Issuing the command SREQ JOBC will move JOBC to the ACTIVE queue. JOBB is still moved to the ACTIVE queue.3 On-Request Schedules and Jobs 10. When the control command SREQ S N=SCHDA is issued.3.2. This example closely resembles example 8. both JOBA and JOBB are placed in the INACTIVE queue.

When autoscan is initiated and it is determined that a schedule is still active (it has not finished running yet). jobs. Tuesday's schedule will never be run. Chapter 10. we will define what a day is. Techniques 10-13 . production work starts at 16:00 and is to be completed by 08:00 the next morning.4 Backlogged Work 10. They are then called backlogged schedules or jobs. if Monday's schedule gets backlogged and completes on Wednesday. then it and its associated jobs will be placed on the CA-Scheduler active workload and processed as if it had been selected normally. Once all jobs in the backlogged schedule have been completed or canceled. Job Backlog: The normal situation allows schedules to be backlogged.4 Backlogged Work Sometimes. When you define a schedule or job to the database. Any job in the schedule that has completed. If a daily schedule gets backlogged for greater than 24 hours (that is. That means you run autoscan at. That is. This means that they may be candidates for being backlogged. If a job in the backlogged schedule has been defined with BACKLOG=NO and still has a status of WAITING.10. Requested Jobs And Schedules: Jobs and schedules that are on-request and are still in the INACTIVE queue at autoscan time will be purged. then when it completes. or shortly after. it is backlogged by two autoscans). in terms of CA-Scheduler. For example. a day is the 24-hour period that starts with the time that you run autoscan. In terms of your company. This is fairly typical. it will be backlogged if it had not started. 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. If the same schedule was also selected on the current production day. But first. Schedule Backlog: When BACKLOG=YES or NO is specified on a schedule definition. the schedule will be marked as complete. For example. or both do not complete the day on which they were selected. it will be canceled with a status called NO BACKLOG CNCL. regardless of their BACKLOG value. Thus. the schedule to execute on the completed day is loaded to the active workload. a day would be your normal daily business computer cycle. Then it is handled as described above. We will term this the production day or autoscan day. or purged will retain its status. schedules. the schedule will be backlogged. it acts only as a default for jobs in that schedule when BACKLOG is not specified on a job. it will be allowed to run. We can step through what happens if the work for a production day is not complete. been canceled. specify whether that schedule or job is a candidate for backlog. If a job has been defined with BACKLOG=YES. Normally it is. 08:00 (to select schedules and jobs for the next 16:00 to 08:00 time period).

10. Tuesday's schedule will never be run. if for some reason a schedule occurs daily and is backlogged twice. they will show up on the Pending Job Profile CA-EARL report for the current production day. Since there is nothing in this schedule to run on Wednesday. When history is generated for these NO BACKLOG CNCL jobs. Another example is that if a schedule runs Monday and Tuesday only. As soon as the schedule ends. it will never get started. BACKLOG=NO. the schedule for the middle day would never be brought in. This is because when Monday's schedule finishes and Tuesday's is brought in. we need to define it more clearly. they will be purged. or defaulted to. When a schedule is backlogged and it is also to be selected for the current production day. 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. it is evaluated for Wednesday. The jobs carrying this status have not yet started and will not be run. 10-14 Online Guide . Only one copy of a schedule at a time will be kept on the active workload. Therefore.4 Backlogged Work In Summary: Since the term NO BACKLOG CNCL was used a few times above. and Monday's schedule gets backlogged until Wednesday. the one being selected will not be placed onto the CA-Scheduler active workload until the backlogged one completes.

CA-11 also cleans up data sets that were created or affected by the jobs before they abended. That discussion describes how jobs can be moved as a group from one CPU to another when one CPU goes down. 10.1 Restart Through CA-11 Jobs may be restarted using the CA-Scheduler CA-11 interface if you have CA-11 installed and active. The CMT contains information which allows CA-11 to restart jobs from the correct point if they abend. ■ Jobs that contain the RMSPROC are tracked by CA-11 in its CMT (Catalog Management Table). “Rerun Job Command” on page 4-142 or 4.5. Techniques 10-15 . 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. the RERUN or SUBMIT panel is displayed with current information from the CA-11 CMT. see 4. Recovery of jobs as they pertain to a multi-CPU environment is discussed in the "Multiple CPU Operations" chapter of the Systems Programmer Guide.3. Driver is a component of CA-Scheduler that provides a JCL handling facility. However. ■ If a job that specifies INSERT RMS PROC = YES abends. what type of automatic facilities are available within the database. The advantages of using CA-11 to restart jobs are: ■ If you originally specify INSERT RMS PROC = YES on the SBR or JBR. Alternatively. what type of manual actions you can take.5 Restart/Recovery of Scheduled Jobs This topic discusses methods of restarting and recovering scheduled jobs.16. the job can be completed or canceled. CA-11 restart parameters can be passed through the CA-Scheduler commands. This allows CA-11 to track your jobs and maintain restart information in case a job abends. the CA-11 RMSPROC is automatically inserted by CA-Scheduler into the job stream (provided that none is already present) at submission time. 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.5 Restart/Recovery of Scheduled Jobs 10. since the RMSPROC is inserted automatically by CA-Scheduler. For details on how to restart a job through the CA-Scheduler CA-11 interface. This allows you to override CA-11 parameters whenever necessary. and then discuss how you could use Driver to automate the recovery process.3. When the RERUN or SUBMIT commands are used from the status display on a job that is known to CA-11. “Submit Job Command” on page 4-160.10. Although CA-Scheduler commands are used to handle the job. Also.21. it can be restarted through CA-11 using one of two CA-Scheduler commands: SUBMIT or RERUN. Also. we will discuss how you determine which jobs have abended. In this topic. no JCL maintenance is required to prepare for using the CA-Scheduler CA-11 interface. the CA-11 CMT is updated accordingly for subsequent runs of the job. Chapter 10.

Indicates that the schedule name provided is to be processed. It can be rerun by using the RERUN or SUBMIT control command.5. RERUN.10. you have a set of status queues from which you can display automatically. BACKOUT schedule name 10-16 Online Guide . OPERATOR CANCLD FAILED To recover any job. They include: Option ABORT CONT Description Indicates that successors to this job do not have this predecessor satisfied. you can modify it and resubmit the job. You can specify four options in this field. or SUBMIT command. This job can be run again by using the RUN. 10. The job has been canceled by an operator using the CANCEL or CP control command. 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. 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.2 Inquiring About Jobs to be Recovered From the status panels. 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.5. Indicates that successors to this job are to be handled as if the job terminated normally because this predecessor has been satisfied. a field called ABEND can be used to aid in automatic recovery of a job. This is the default value. It can be rerun by using the RERUN or SUBMIT control command. 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. its JCL is either in the active workload or can be placed there by the RESTAGE command. Once it is in the active workload.5 Restart/Recovery of Scheduled Jobs 10. CA-Scheduler adds a new job tracking record for the backout job.3 Automatic Recovery Options When defining a job to the database. 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.

or ADD control commands for recovering the abended job. The determination is made through the automated process that exists today. Chapter 10. For example. Techniques 10-17 . Therefore. Driver is the JCL management facility included in CA-Scheduler.5.5 Restart/Recovery of Scheduled Jobs If a recovery schedule is defined. 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. the 'cure' should not cause more disruption than the problem. That is. or a more automated method using Driver. Step 5 abends. 10. you should attempt to use some sort of naming convention so that any recovery schedule can be recognized quickly.10. REQUEST. These users are defined on the schedule and job message records. other jobs could be brought in with the RUN. 3. For example. in a multi-step job.) Keep in mind that JCL errors for a job are treated as if the job failed. it could contain a job that executes the CAJUCMD0 program that allows you to interrogate various jobs' status through batch commands. and 4 must be removed from the OS/390 catalog. Another way to be sure that jobs that need recovery do not go unnoticed is to use the message facility. Based on the job status. When you define a recovery schedule. Herein lies the problem of automating the restart/recovery process. As with the implementation of any automated system. the data sets that were created in Steps 2. begin all recovery schedule names with RR. Many options are available to a data center to effect proper restart/recovery either using native OS/390 JCL. you can specify up to four users to send messages to if the job abends or fails. The users can be operator consoles or the CA-Scheduler mailbox. that Step 5 relies on the temporary data set that was created in Step 2.4 Driver Considerations Implementing a job step restart process is inherently complex due to all of the variations of abend conditions. (See Schedule Messages panel on page 5-15 and Job Messages panel on page 5-46. This technique is described in the preceding topic of this chapter.

the values could be explicitly coded in the JCL. the body of the job could be made into a cataloged procedure with the generation members being symbolic values. standard JCL does not take care of resetting GDG bias numbers.5 Restart/Recovery of Scheduled Jobs 10. Abend recovery cannot be totally automated. The OS/390 symbols are made into Driver variables. because it is impossible to plan for every situation. The generation data group's index is updated at job-end and not step-end.10. The first two examples below use standard JCL facilities. This is the most straightforward method and the most error-prone because changes must be made to the execution JCL. However. method uses the Driver component of CA-Scheduler.5. however. and last. Realistically. Three ways exist to reset relative generation pointers. First. This is the least error-prone because the JCL is automatically changed by Driver.4. facilities exist in OS/390 JCL that ease restart complexities. Driver statements would be used to determine whether it was production or rerun. all the (0) must be changed to (-1). some manual intervention is involved in a program restart. To reference a generation data set that was created in a prior step. In a restart situation where the restart takes place after the data set has been created. 10-18 Online Guide . all of the (+1) generation pointers must be changed to (0). you must suffix the data set name with the string (+1). Of course. Consideration should be given to keeping the intervention to a minimum and to making the intervention as error-free as possible. and where the restart should begin. The third. Second. The drawback to this approach is that in a large program. The symbolics could then be overridden at execution with values supplied by the starter JCL. quite a number of overrides could be required to restart the program correctly.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.

// RESTART=STEP2 //STEP1 EXEC PGM=DASDBKUP //SYSPRINT DD DSN=DASD.DELETE) EXEC PGM=LISTDASD DD DSN=DASD.CLASS=A EXEC PGM=DASDBKUP DD DSN=DASD. The backup data set is a generation data set (DASD.BACKUP(+1).CATLG. generation members are explicitly coded.'DASD BACKUP'. the bias pointer.5. // DISP=(NEW.10. Now. //BACKUP //STEP1 //SYSPRINT // //STEP2 //TAPEIN // //SYSPRINT JOB (acctg). Techniques 10-19 .BACKUP) since it is suffixed with (+1). Thus. //BACKUP JOB (acctg). we must insert a RESTART parameter and change the GDG bias.BACKUP(+1). where nnnn is the generation number. // 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. we indicate to use the generation number created in the first step. In the second step.GnnnnV00. Chapter 10.DELETE) //STEP2 EXEC PGM=LISTDASD //TAPEIN DD DSN=DASD.5 Restart/Recovery of Scheduled Jobs 10.2 Example 1 In this example.BACKUP.'DASD BACKUP'.CATLC.BACKUP(+1). DISP=(NEW.BACKUP( ).4. (+1).CLASS=A. A restart must be submitted to print the report. when the step ends normally. 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. if we want to restart in the second step. the data set will be cataloged as DASD.

DELETE) EXEC PGM=LISTDASD DD DSN=DASD. Except for the symbolics. the body of the JCL is a JCL procedure and uses symbolics instead of hard-coding the generation bias numbers. // RESTART=(BKUP. 10-20 Online Guide .GENP2=' ' This would submit the same JCL as in Example 1 (restart) with the symbolics properly resolved.STEP2) //BKUP EXEC PROC=DASDBKUP.CATLC.'DASD BACKUP'. DISP=OLD DD SYSOUT=A This is a standard OS/390 cataloged procedure.BACKUP(&GENP1).BACKUP(&GENP2).5. you would submit the following: //BACKUP JOB (acctg). if we want to restart in the second step. The starter JCL for the normal execution would be: //BACKUP //BKUP JOB (acctg).GENP2='+1' EXEC PGM=DASDBKUP DD DSN=DASD.CLASS=A EXEC PROC=DASDBKUP.10. DISP=(NEW. Now.GENP2='+1' This would submit the same JCL seen in Example 1 with the symbolics properly resolved.5 Restart/Recovery of Scheduled Jobs 10. the JCL is the same as Example 1.3 Example 2 In this example.4. //DASDBKUP //STEP1 //SYSPRINT // //STEP2 //TAPEIN // //SYSPRINT PROC GENP1='+1'.GENP1='+1'.GENP1='+1'.'DASD BACKUP'.CLASS=A.

You may also specify a user ID. For example. one of the Unicenter TNG Framework for OS/390 Common Services. When Unicenter TNG or CA-Scheduler Agent reports that task complete. and a domain. 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. CA-Scheduler needs at least two pieces of information to schedule work on remote systems: the node name and the command to be executed. then initiated and tracked by Unicenter TNG or CA-Scheduler Agent on the remote platform. CA-Scheduler marks the job as ended or failed. 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. Work on remote systems is initiated by a command. as well as any special characters needed. if the job is defined as libtype PDS. a program. password. Parameters can be passed on the command. 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. the information is read from JCLMASTR. The command can execute a script on the remote system. CA-Scheduler passes the information to Unicenter TNG or CA-Scheduler Agent using CAICCI. based on the return code. or anything else that can be started with a command. Uppercase and lowercase characters are supported. Chapter 11. Remote Scheduling 11-1 . The work is scheduled by CA-Scheduler.Chapter 11.

1 Statements The following statement types are supported: ■ Comments ■ Node ■ Command ■ Domain ■ User ■ Password Statements may be specified in any order.1 Statements 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. The first character after the equal sign is used as a delimiter. CA-Scheduler ignores anything after the closing delimiter.1. the delimiter is a single quote. 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.1 Comments Enter comments by typing an asterisk (*) in column 1. 11. In the example above. Only one node statement is allowed per member. 11.11. CA-Scheduler does not take any action on these lines. 11-2 Online Guide . Use uppercase or lowercase.

it must be doubled and enclosed in quotes: command=/command "quote in parentheses ("")"/ Chapter 11. Use multiple command statements to build long command strings. Use uppercase or lowercase. For example. If a blank was wanted between the two parts. Blanks are used to delimit between the command and any parameters.1. The command string is split into a command and parameters.11. include it in the command statement: command='command ' command='string' would produce the command string of "command string". the delimiter is a single quote. The first character after the equal sign is used as a delimiter. The following command statement would send two parameters: command='command parm1 parm2' If a parameter needs to include a space. CA-Scheduler ignores anything after the closing delimiter. use quotes around that parameter. The following example sends only one parameter: command=/command "part1 part2"/ If a parameter needs to include a quote.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. The following would all be treated identically: command=/commandstring/ COMMAND=?commandstring? Command='commandstring' comments The case of the command string is preserved. the following are NOT identical: command='commandstring' command='COMMANDSTRING' Command strings can be up to 255 bytes in length. For example: command='command' command='string' would produce the command string of "commandstring". The strings are concatenated together without any intervening spaces or other characters added. Remote Scheduling 11-3 . In the example above.1 Statements 11.

that the requirements of the target system may restrict the length. however. the delimiter is a single quote. CAIJGEN SUBUID order. Domain='domainname' The domain statement must begin with the characters "DOMAIN=' in column 1. If the target system is case-sensitive. Some platforms may treat a single parameter as multiple parameters if the parameter includes blanks. CAIJ$SEC options). Note: The interpretation of parameters is platform and command specific. User='userid' The user statement must begin with the characters "USER=" in column 1.1. The first character after the equal sign is used as a delimiter. If no user ID is specified and the CAIJ$SEC option RMTUSER is set to Y. The domain name is passed to Unicenter TNG exactly as entered. The first character after the equal sign is used as a delimiter.5 User Specify a user ID on the user statement. enter the domain name in the expected case. In the example above. 11. the delimiter is a single quote.1 Statements The previous example will send a single quote between the parentheses. Use uppercase or lowercase. Unicenter TNG executes the command under this user ID. 11. Note. CA-Scheduler ignores anything after the closing delimiter. CA-Scheduler ignores anything after the closing delimiter. In the example above. Note. 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. users may be defined within domains. 11-4 Online Guide . such as Microsoft Windows NT.1.11. Domain names may be up to 15 characters long. if any. however. that the requirements of the target system may restrict the length. Use uppercase or lowercase. CA-Scheduler uses the same rules applied to OS/390 jobs to determine a user ID (that is. and the entire string "quote in parentheses (")" will be sent as one parameter. User IDs may be up to 32 characters long. Unicenter TNG takes if a domain is not specified.4 Domain On some platforms.

Remote Scheduling 11-5 . Unicenter TNG may be configurable to require or not require passwords. the CA-Scheduler option CAIJ$SEC SUBROOT is checked.11. In the example above. CA-Scheduler ignores anything after the closing delimiter. however. enter the password in the expected case.) The user ID is passed to Unicenter TNG exactly as entered. the delimiter is a single quote. 11. User IDs on the target platform may need special authorization to be used by Unicenter TNG. Otherwise. (ROOT is a powerful user ID on some systems. Password='password' The password statement must begin with the characters "PASSWORD=" in column 1. See the Unicenter TNG documentation for the target platform for more information.1 Statements If the user ID specified is ROOT. such as UNIX.1. the submission is failed. If the target system is case-sensitive. The password is passed to Unicenter TNG exactly as entered. Note. If SUBROOT is set to YES. that the requirements of the target system may restrict the length. Unicenter TNG may need to be configured to support submission of work in other than the default user ID. The first character after the equal sign is used as a delimiter. the submission is allowed. If the target system is case-sensitive. See the Unicenter TNG documentation for the target platform for more information. enter the user ID in the expected case. Passwords may be up to 14 characters long. See the Unicenter TNG documentation for the target system for more information. Chapter 11.6 Password Specify the password to be used to log on the user ID on the target platform. Use uppercase or lowercase.

2. 11. 11.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".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".2. 11-6 Online Guide .2.2 Examples 11.2.2 Example 2 command="/usr/bin/sleep" node=/uscoiu87/ command=' 1 ' This example works identically with the previous example.2 Examples 11. A parm of 10 is passed to the program. The statements can be in any order. 11.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.11. and different delimiters can be used on each statement.

The automatic selection of a day's workload. An early termination of a program due to an error. all the job's predecessors have been satisfied. active workload. Each authority level places different restrictions on what those CA-Scheduler users can do. One of three different types of access assigned to users using the TYPE field on a user record. To help you grasp these new ideas quickly. start time. One or more accounting days. CA-Scheduler scans the database at a set time every day to determine the workload for the next 24 hours. accounting week. The time when CA-Scheduler automatically scans its database for workload selection. The CA-Scheduler file that contains the copy of current production. abended. Also called autoscan time. held. or accounting period. There is a schedule base record (SBR) and a job base record (JBR). AUTOTIME. References to a backlogged schedule or job pertain to a previous day's schedule or job which is included in today's workload. A job is available (ready to be submitted) when its schedule has started. but may be modified with the AUTOTIM installation option. Also called the production day. interrupted. Abnormal ending. Schedules and jobs that are: ■ waiting at any workstation for predecessors.Glossary This glossary defines terms used in all volumes of the CA-Scheduler documentation. Supervisor. authority level. sales. or defined resources ■ waiting at a non-CPU station to be started manually ■ submitted. we have used italics to highlight related terms worth cross-referencing. and Manager authority levels. A week containing at least one accounting day. accounting day. autoscan day. Work that was not completed one day and was carried over to the next. (Users with Supervisor or Manager authority level do not require specific authorization to maintain or control schedules. Ready for processing by CA-Scheduler. A abend. array. base record. active. or failed The opposite of inactive. backout job.) autoscan. The record which is required to define a schedule or 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. A schedule is available (ready to start) when its early start time has been reached and all of its predecessors have been satisfied. the job's early start time has been reached. its jobs because they are listed in the USERS field on that schedule's base record. authorized users. and the resources defined for that job are available (not in use). The default name of the file is CAIJTRK. A variable parameter with multiple values. A day designated on a date table as part of a cyclic production. Glossary X-1 . See General. But sometimes one new term leads to another. available. The 24-hour period starting with autoscan. accounting period. Users with General authority level who are allowed to maintain and control a schedule and B backlog. This defaults to midnight. or started ■ completed.

calendar. There is a schedule criteria record (SCR) and a job criteria record (JCR). jobs can be selected on Mondays. or special characters. Computer Associates JCL validation product. cross-node dependency. conditional expansion. 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. Computer Associates rerun/restart product. you define several calendars. or the normal completion of a job not under CA-Scheduler's control. A subset of this product that allows you to customize reports is provided with CA-Scheduler. and selection. CA-JCLCheck. A number that explains why a schedule or job was selected. etc. cyclic scheduling. usually enclosed in delimiters. CA-Earl. accounting days and accounting periods so. code record. Driver retrieves and expands just some of the steps in a procedure depending on conditions at the time of expansion. One of three date references CA-Scheduler consults when selecting the day's workload. An alternative method for identifying when a schedule or job should be selected as part of the day's workload. X-2 Online Guide . Computer Associates Easy Access Report Language. the start or end of a job under CA-Scheduler's control. ■ The Gregorian calendar tells CA-Scheduler what day of the week it is so. 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. criteria statement. Numbers from 80 to 99 are special reason codes which indicate that selection was based on default daily processing. predecessor criteria. This component is included with CA-Scheduler and oversees the installation and maintenance of Computer Associates OS/390 products. numeric. These events can be the close of an output data set or generation data group. or manual additions. CAIRIM. calendar mechanism. ■ calling statement. 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 reason code record (SRC) and job reason code record (JRC). each designating different days when schedules or jobs should be selected (Mondays. Date Tables define workdays. Reserved words used in CA-Scheduler's criteria statements. criteria record. holidays. One or more alphabetic. A command used to monitor or control the workload. pay days. character string. C CA-11. Computer Associates Resource Initialization Manager. Also known as operator command. for example. Predecessor events that occur at other nodes in a CA-Scheduler NJE environment.) The database shows which calendar to consult when selecting a schedule or job. CA-Scheduler can select jobs on the last workday of the month. Scheduling a schedule or job at regular intervals regardless of which day or month it is (for example. With this method. Numbers from 01 to 79 correspond to the position of a reason in the criteria statement. The record that assigns time specifications which vary according to the reason a schedule or job is selected for processing. every six weeks). Any command that is issued by executing a CA-Scheduler program through standard OS/390 JCL. criteria vocabulary. control command. CAISERV. ■ Calendars explicitly define which days to select schedules and jobs so you can run jobs on random dates. month-ends.batch command. calendars. for instance. code. The EXEC statement which retrieves a procedure from the Driver procedure library and submits it to JES.

A predecessor that is specifically defined in the criteria statement of a schedule or job. Also called a predecessor loop. To display. documentation batch command. accounting days. holidays. In 'this example'. Identifies workdays. delimiter. P and W) that allows you to define multiple versions of a date table by applying different prefixes. A report that shows when workday. The default name of the database is CAIJMST. holiday. the close of output data sets and generation data groups. the result is a keyword-defined predecessor that is ignored during the selection process. date table prefix. ■ F forecasting. ■ The USERS field on a schedule's base record defines which General users can access that schedule and its jobs. The stalemate that occurs when jobs are predecessors to each other. and what time it is. and accounting keywords in criteria statements. default. Explicit predecessors can be either of two types: ■ Selection-defined explicit predecessors are predecessors that also define selection criteria. expansion. specify the common characters followed by an mask character (*). The CA-Scheduler database that stores records containing definitions of user IDs. the delimiter is a single quote (') identifying a character string consisting of two words: this example. Producing reports that show which schedules and jobs will be selected for processing on any given day(s). A special character that precedes and follows a character string. G General authority level. schedules. and resources. General users are prohibited from doing anything involving stations or schedules for which they are not authorized. A command issued through batch using the CARUTIL0 program that is used to maintain members in the workload documentation. stations. Some of the events that CA-Scheduler monitors are schedules and jobs starting and ending. H. and Gregorian conditions are true. The default authority level assumed for all users unless Supervisor or Manager is specified. generic list. Driver replaces an EXEC statement with the contents of a cataloged Driver procedure. and accounting periods so you can use workday. 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. deadlock. See authorized users as well as Supervisor and Manager authority levels. jobs. list. date table. accounting. A one letter prefix (excluding E. Glossary X-3 . explicit predecessor.D database. A value or action that CA-Scheduler supplies automatically unless you specify some other alternative. N. Occurrences that CA-Scheduler monitors so it knows when predecessor conditions have been satisfied. A group of schedules or jobs whose names begin with the same characters. Date Translation Table. They can be schedule or job names used with or without the keywords SCD and START. documentation. E events. Driver. 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. Computer Associates JCL manipulation component of CA-Scheduler. or analyze a generic list. Entries in the CA-Scheduler workoad documentation (CAIJDCM) that provide information to users. Deadlocked jobs never run because their predecessor conditions are never satisfied.

JSR. Julian date. is purged.global parameter. JNR. where yyyy is the year and ddd is the relative day of the year (from 001 to 366). Job message record. The opposite of active. ends. CA-Scheduler expands the scope of that definition to encompass all data processing tasks under CA-Scheduler's control. job number. binary. See sequence enforcement. job path. inactive. A seven-digit number of the form yyyyddd. Predecessors that are not defined on a job's criteria statement. Because CA-Scheduler enforces workstation sequences. This record is used to specify other nodes to be notified when a job starts or ends. JRR. There is a schedule information record (SIR) and job information record (JIR). See keyword-defined explicit predecessors. The record that contains statistics of past runs of schedules and jobs. Gregorian date. Job information record. history record. Gregorian calendar. A user-controlled variable that defines a predecessor condition in criteria statements and can assume arithmetic. or character values. job. This record determines when a job is to be selected for processing and lists the predecessors for the job. The record that provides descriptive information of schedules and jobs. JRC. You can use Gregorian calendar keywords without defining a date table or calendars. Usually refers to work submitted to the CPU for processing. JIR. installation option. or is interrupted. Job base record. jobs that run on the CPU. X-4 Online Guide . abends. This record allows you to define the resources necessary to run a job. and post-CPU tasks such as report distribution. 2003305 is November 1. The CA-Scheduler file that contains history records for schedules and jobs. JCR. However. create a job definition for each iteration by giving them different job numbers. J JBR. This can include pre-CPU tasks such as data entry. 2003. I implicit predecessor. Job step record. Likewise. 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. When a job needs to run more than once during a production day. The standard 12-month calendar which CA-Scheduler references to interpret certain selection keywords (like WEEK-DAY) in criteria statements. This record is required to define a job. This record determines who receives messages when a job begins. pre-CPU jobs (such as data entry and JCL staging) are implicit predecessors for CPU jobs. Job criteria record. This value controls scheduling operations throughout the data center unless it is overridden by values in the CA-Scheduler database. JMR. For example. A value specified on the CAIJGEN installation macro when CA-Scheduler is installed. This record provides descriptive information for a job. CPU jobs are implicit predecessors for post-CPU jobs (such as report distribution). This record is used to assign time specifications which vary according to the reason a job is selected for processing. One of four fields used to uniquely identify each job definition. starts late. H history file. This optional record allows you to define job step information used to determine a job's failed status. Job node record. All the stations where a job is processed as it moves through the data center. Job resource record. A date shown as mm/dd/yy (American format) or dd/mm/yy (European format). information record. Job reason code record.

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. M mailbox. See General and Supervisor authority levels. L levels of predecessors. or is interrupted. node. but only three levels of predecessors. (Their levels of predecessors = 0) JOBA0 is JOBA1's predecessor. nonscheduled job. In terms of a family tree. The common area for sending CA-Scheduler messages so that they can be viewed by many users without being deleted. the number of preceding "generations" (schedules or jobs) with defined predecessors. node record. The number ending each job name below identifies each job's level of predecessors. or starts late or when a job abends. (JOBA1's level of predecessors = 1) JOBA1 is JOBA2's predecessor. 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. (JOBB4's level of predecessors = 4) The key word here is level. Each location in a network having one CPU or multiple CPUs with multi-access spooling facility. in turn. ends. network. The record that determines who receives messages when a schedule or job begins. and issue all commands. An OS/390 job that is neither controlled nor submitted by CA-Scheduler. define and maintain any database records. ? indicates that any character can be substituted at this point in the search string. 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. mask character. One procedure calls (retrieves) another procedure which can. but just one character can be substituted for each question mark. The record that specifies other nodes to be notified when a job starts or ends. call other procedures. is purged. (JOBA2's level of predecessors = 2) JOBA2 and JOBB0 are JOBA3's predecessors. Two or more interconnected systems (nodes) participating in a VTAM network or communicating using BSC lines (binary synchronous communication). The highest authority level which allows these users to access all stations. N nesting. JOBA JOBB │ │ JOBA1 │ │ │ JOBA2 ───┐ │ │ │ JOBA3 │ JOBB4 JOBA0 and JOBB0 have no predecessors. control all Glossary X-5 . Levels of predecessors is one factor CA-Scheduler uses when ordering the workload. (JOBA3's level of predecessors = 3) JOBA3 is JOBB4's predecessor. message record. NJE or PRED. Manager authority level. 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.K keyword-defined explicit predecessors. JOBA3 has four different predecessors. 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. Schedules and jobs with fewer levels of predecessors are evaluated ahead of those with more. There is a schedule message record (SMR) and job message record (JMR).

One of the various job categories that depend on the status of the jobs. These holidays and rescheduling instructions are automatically applied to all calendars defined for that year. O on-request. See station. periods. Schedules or jobs having the keyword REQUESTED in their criteria statement. procedure library. The stalemate that occurs when jobs are predecessors to each other. and report distribution. A word on a screen that reminds you to supply a value. sales cycles. shipment of backup tapes off-site. or any other unit of time. JOBB does not run until JOBA runs to completion. A year can be divided into accounting periods. See station. A schedule that can be maintained by all users because no value is specified in the USERS field of the schedule base record. A master calendar that defines all of the year's holidays and tells when to reschedule jobs that would normally be selected on holidays. prompt. production day. A command used to monitor or control the workload. Work scheduled to prepare a job for CPU processing. The end of each period is identified by a P on the date table. These deadlocked jobs never run because their predecessor conditions are never satisfied.null value. production periods. X-6 Online Guide . predecessor. 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. post-CPU job. prototype calendar. predecessor criteria. 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. Also called deadlock. All the stations where a job is processed as it moves through the data center. 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 loop. Why a schedule or job is selected for the day's workload. Also known as control command. The library that stores Driver procedures. If JOBA is a predecessor of JOBB. An existing definition whose values are used as defaults for a new definition. Work scheduled after CPU processing to wrap up a job. R reason. Also called the autoscan day. and JCL setup. An event that must happen before the next job can begin. One or more statements cataloged under a procedure name as a member of the CA-Driver procedure library. CA-Scheduler's criteria statements allow you to define predecessors for schedules and jobs. All of the predecessors defined for a schedule or job in its criteria statement. A defined value of nothing which has been added to the database using the keyword NULL. Any fields left blank while defining a new record are assigned values from the prototype definition. The 24-hour period starting with autoscan. 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. Examples include daily shipment of input forms. These predecessor conditions must be satisfied before a schedule can start or a job can be submitted. That means schedules and jobs in today's workload do not run until their predecessors are satisfied. P path. prototype definition. operator command. data entry. RECS line. Examples include output decollation. procedure. pre-CPU job. public schedule.

selection. selection-defined explicit predecessor. How CA-Scheduler determines the day's workload at autoscan time. 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. CA-Scheduler reviews the criteria statements of every schedule to see which ones qualify for inclusion in the day's workload. when operating systems share CA-Scheduler files. All the important terms used in this definition are also defined in this glossary. SMR. resource record. selection criteria. A hardware configuration that allows two or more operating systems to use the same disk files. A report that contains detailed information on the current day's workload. Glossary X-7 . See selection. it does not imply that they also share spool files. The schedules and jobs selected each day comprise the workload. See implicit predecessor. ends. A predecessor that also defines selection criteria. SMF ID. Schedule criteria record. Making sure schedules and jobs are processed in the right order. it scans the criteria statements of every job in that schedule. route delay time. This situation allows several operating systems to use the same set of CA-Scheduler files at the same time. ■ The keywords that are used in the maintenance panels to limit the directory to be displayed. the result is a keyword-defined explicit predecessor that is ignored during the selection process. shared DASD. This record determines who receives messages when a schedule begins.reserved-name variable parameter. There are two distinct meanings: ■ All the reasons why a job or schedule can be selected as defined in its criteria statement. staging. See shared DASD. sequence enforcement. One of a set of Driver variable parameters which are predefined by Computer Associates. SCR. The record which specifies the resources that are used to run a job. Answers the question "what if. Schedule information record. Four characters that identify the System Management Facility running on OS/390." It shows how processing is affected by changes in workload or hardware failure. SIR. This value usually corresponds to the JES SID. simulation. route station. This record is required to define a schedule. run book. Simulation also totals how long each job usually takes to project when the workload is likely to finish. spin locks. Every time CA-Scheduler selects a schedule that qualifies. CA-Scheduler's three-step process for tailoring production JCL: S SBR. schedule. The method CA-Scheduler uses to protect the integrity of its files when two or more operating systems share them. Schedule reason code record. or starts late. A workstation defined for purposes of receiving reports rather than performing data processing tasks. They are schedule or job names used with or without the keywords SCD and START. However. If a calendar is also defined for a schedule or job. This record provides descriptive information for a schedule. When START or SCD is used with PRED or NJE or MVS. This record is used to assign time specifications which vary according to the reason a schedule is selected for processing. 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. The delay between the time a job ends at one station and starts at the next station. CA-Scheduler bases selection on the calendar and ignores the selection criteria. Schedule message record. SRC. Schedule base record. This record determines when a schedule is to be selected for processing and lists the predecessors for the schedule.

The work CA-Scheduler anticipates submitting each day. Every area where a job is scheduled for processing as it makes its way through the data center. data entry. The CA-Scheduler file that contains staged JCL members. even if they are not authorized on the schedule base record. Conversely. The intermediate authority level which allows users to control all schedules and jobs at specified stations. 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. The CA-Scheduler file that contains workload documentation entries. FAILED. substring. Supervisor authority level. However. If JOBA must finish before JOBB can start. etc. status conditions.■ First. CPU processing. CA-Scheduler automatically copies the production JCL for jobs that require staging into its staging library. syntax checking. their scope of authority is limited to just those stations specified on their user record. Also called a workstation. CPU processing. During expansion. successor. W work flow. Also called a station. workload. staging file. ■ When the JCL has been modified and that pre-CPU job has been posted as ENDED. 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. each reference to the symbolic parameter is replaced with a default or override value. Any area where a job is processed as it makes its way through the data center. Examples include production control. and report distribution stations. See General and Manager authority levels. CA-Scheduler monitors the progress of jobs by collecting and analyzing data on events as they occur. CA-Scheduler automatically submits the modified JCL to the operating system when that job becomes available for processing. CA-Scheduler's criteria statements allow you to define conditions that must be met before a job can start. workload documentation. Examples include production control. workstation. Also called JCL setup. The default name of the file is CAIJSTG. ■ Then users modify that copy of the JCL as needed (the original production JCL is not changed). The default name of the file is CAIJDCM. Any day that is not designated a weekend or a holiday on a calendar or date table. The movement of jobs from station to station through the data center. data entry. JCL setup.) that CA-Scheduler applies to jobs to indicate their current state within production. Any job that cannot start until some event triggers it. and report distribution. T tracking. JOBA is a predecessor to JOBB. V variable parameter. The various words (ABENDED. station. Checking JCL for syntax errors and displaying those errors. A symbolic parameter that is defined when a procedure is cataloged and referenced in the body of the procedure. JCL setup. X-8 Online Guide . workday. Part of the value given to a variable parameter. ENDED. CA-Scheduler automatically updates their status in its active workload. As jobs move from station to station through the data center. JOBB is a successor to JOBA.

4-61 predecessors 4-56 stations 9-4 successors 4-58 ADOM keyword 7-3. 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. 7-19. 7-16. 7-16. 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. 7-12. 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.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. 9-5 periods 7-46 ACTIVE queue 9-21. 10-16 user-defined reports 9-18 Index X-9 . 7-16 Date Translation report 7-20 using date tables 7-2. 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. 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.

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. 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-27. 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.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. 10-13 definition 10-13 X-10 Online Guide . 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.

7-12 prototype 5-95. 7-21 workdays 5-95. 9-15 FORECAST command 9-16 ONLY command 9-16 SIMULATE command 9-16 CAJUTSTB member 9-17 Calendars definition panel 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.Backlog (continued) symptom of deadlock 9-16 BACKLOG field Job definition panel 5-31. 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. 10-13 Schedule definition panel 5-7. 7-22 holidays 7-21 menu 5-93 methodology 7-21. 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 . 9-5 overview 7-2. 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. 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. 10-13 Backout jobs automatic recovery option 10-17 Job definition panel 5-37 reason code 4-7.

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 .

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-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. 7-4. 7-6.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. 7-16 menu 5-100 methodology 7-15. 9-5 overview 7-2. 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. 9-7 with INTERRUPTED status 9-10 Complete Job Command panel 4-71 Conditions causing selection 7-1. 9-5 Date Translation report 7-19 Days-of-themonth keywords abbreviations 7-41 accounting cycles 7-46 workdays 7-41 Index X-13 . 5-104. 7-12 prefix 5-102. 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. 7-11 Criteria. 9-27 schedule 5-24.

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 . 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-5. 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.(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. 7-23 holidays 7-15.Days-of-the. 7-6. 9-4 successors 4-58 user IDs 5-68 work schedules calendars 7-21. 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. 7-1.

7-39 with PRED keyword 9-22 E EARLY START field Job definition panel 5-31. 10-16 Flow displaying 4-88 Flows 5-110 Force Command definition 9-20 Index X-15 . 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. 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-20 returning JCL to original contents 4-41 DSN keyword overview 7-5.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. 10-17. 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. 7-41.

4-160. 7-39 General authority 5-70 Global parameters defining 7-5.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. 4-50. 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 . 5-48 NJE Job status detail panel 4-30 Schedule base panel 5-8 Schedule status detail panel 4-6. 7-3. 5-8. 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. 5-37 CA11 4-142. 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. 9-6 INACTIVE queue 9-21. 4-52. 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-8 displaying values 9-9 example 7-34 panel 4-95 setting values 9-28 testing values 9-20 Gregorian calendar 7-2. 7-23 WEEKLY 7-21. 7-12 Grouping jobs 9-6 H HDAY keyword and date tables 7-15 date table example 7-19 examples 7-25. 9-6 MCPU 5-43 MSGHOLD 5-16. 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.

GT. 9-18 syntax checking 9-15 JCR panel 5-28. 5-57 JES class 4-33. 4-55. 9-27 definition panel 5-29.PROC1.STEP2. 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. 5-14. 9-26 reason code record (JRC) 5-48 recovery 10-15 releasing panel 4-130 requesting panel 4-139 rerunning 9-10.PROC1. 9-10 Interrupted jobs 9-10 INTERRUPTED status 9-21 J JBR panel 5-29 JCL errors 10-17 staging 4-146. 5-32 STAGE 5-10 STRMSG 5-16 SUBUID 4-31.STEP2-02 40 SCHDA keyword 7-4 JOBA.STEP2. 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.STEP2-02 40 SCHDA keyword 7-4 JOBA. 5-10. 10-17 Job (continued) node record (JNR) 5-52 posting 4-105 purging 4-125. 5-40 job number 6-17 node 5-52 Original JES number 4-22 priority 4-33.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 . 5-41 Internal security Schedule base panel 5-13 Schedule status detail panel 4-14 Interrupt field Job definition panel 5-38.00008-02 40 SCHDA keyword 7-4 JOBA. 5-9. 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. 9-4.CC. 9-10.CC. 4-55.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. 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. 9-6.GT.

7-15. 7-46 DSN and predecessors 7-39 overview 7-5 with PRED keyword 9-22 examples 7-25. 7-46 AMOY 7-3. 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-39 NJE 7-5. 7-4. 7-16.K Keywords ADAY 7-3. 7-46 ADOM 7-3. 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-45 REQUESTED daily processing 9-21 Gregorian calendar conditions 7-41 impact on successors 10-9 jobs purged by autoscan 10-8. 7-41. 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-39 selection example 7-4 staging a job 9-7 START and NJE 7-5 predecessor example 7-5. 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 HDAY and date tables 7-15 date table example 7-19 examples 7-25. 7-5. 7-28 selection example 7-4 selection use 7-3 workday conditions 7-44 WDOM and date tables 7-15 examples 7-24. 7-16. 7-29 selection example 7-4 7-7 X-18 Online Guide . 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-19. 7-11 AWOF 7-3 AWOM 7-16. 7-28 GBLxnn defined 9-8 example 7-34 reserved word 7-5 resetting 9-28 GDG 7-5. 7-39 RDnn 7-3. 7-46 AND date table example 7-19 debugging errors 7-33. 7-34 examples 7-25. 7-27. 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-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-24 selection use 7-3 workday conditions 7-44 WEEK-DAY calendar mechanism 7-13 Date Translation report 7-20 definition 7-2. 7-19. 7-19. 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. 7-23 scheduling 7-41. 9-15 Schedule definition panel 5-8. 7-19. 7-16. 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.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-46 xDOM 7-3. 7-44 WWOY 7-44 xDAY 7-3. 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-27. 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 . 7-46 xMOY 7-3. 7-46 xWOF 7-3 xWOM 7-16. 7-41 WWOM 7-15. 7-16. 7-12 example 7-27 Gregorian calendar 7-3 Gregorian calendar conditions 7-41 WEEK-END 7-3.

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. 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-15. 9-22 displaying 4-38 explicit 7-5 global parameters 9-8 implicit 7-8. 7-34 examples 7-25. 7-28. 9-22 PRED keyword 7-39 Predecessor display panel 4-38 Predecessors altering 9-27 deadlock 7-33. 9-11. 7-34 examples 7-25. 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-5. 7-33. 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. 9-16 defining 7-1. 10-9 date table example 7-19 debugging errors 7-32. 9-6 listing for current job 6-35 current schedule 6-37 specific job 6-31 specific schedule 6-33 loop 6-3. 7-27. 9-21 start times 9-20 X-20 Online Guide .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-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. 7-6. 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-11.

4-74 job from status display 4-125 schedule from current workload 4-68. 10-9 Predicting the workload 9-14 Prefixes for date tables 5-102. 4-77 schedule from status display 4-127 work from current workload 4-65. 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. 10-8 INACTIVE 9-21. 10-8 R RC code job 4-21 schedule 4-6 RDnn keyword 7-3. 7-32. 7-26. 9-5 day 10-13 Prototype calendars 5-93. 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. 7-15. 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. 5-104 Prerequisites 7-1 Printing jobs 9-4 Production cycles 7-16.Predecessors (continued) nonscheduled OS/390 job 7-5 other jobs or schedules 7-3. 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 . 7-4.

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.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. 7-19 documentation 9-18 forecast 9-14 history 6-12. 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 . 9-11. 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. 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. 9-15 CA-Earl 9-18 database 9-18 date translation 6-14.

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. 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. 7-44 overview 11-1 period 7-46 relative day 7-45 weekly 7-41. 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-3 rule 7-11 with REQUESTED 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 . 7-44 yearly 7-41 Scheduling Environment CPU Job status detail panel 4-28 Schedule status panel 4-13 SCR panel 5-5. 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.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. 5-24. 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. 7-21 monthly 7-41. 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.

7-5. 10-16 autoscan 4-82 CANCELLED 9-21 CANCLD 10-16 ENDED 9-21 ENFDOWN HELD 9-24 FAILED 9-21. 7-4.SEPARATE fields Job resource panel 5-42. 9-4 Status ABENDED 9-18. 9-20 Station 40 5-73 adding 5-73. 9-4 Station (continued) definition panel 5-75 menu 5-73 numbering 5-73. 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. 7-39 Starting jobs 9-20 schedules 9-9. 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 . 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-21. 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-12. 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 . 7-23 scheduling 7-43. 7-26. 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.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-41 Weekends 7-15 Weekly frequency 7-21. 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-23 defining 5-100 holidays 7-15. 9-5 WORK WEEK field Dateteble Definition panel 7-16 Workdays and date tables 7-2. 7-45 Work schedules calendars 7-21. 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-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.

7-16. 7-44 WWOY keyword 7-44 X xDAY keyword xDOM keyword xMOY keyword xWOF keyword xWOM keyword xWOY keyword 7-3. 7-19. 7-44 keywords 7-3 selection examples 7-4 WWOM keyword 7-15. 7-46 7-3.Workdays (continued) date table example 7-19 Date Translation report 7-20 keyword table 7-15. 7-46 7-3. 7-46 7-3 7-16. 7-19. 7-16. 7-19. 7-27. 7-46 7-19 Y Yearly scheduling 7-41 X-26 Online Guide .

Sign up to vote on this title
UsefulNot useful

Master Your Semester with Scribd & The New York Times

Special offer: Get 4 months of Scribd and The New York Times for just $1.87 per week!

Master Your Semester with a Special Offer from Scribd & The New York Times