Unicenter CA-Scheduler Job Management for VSE Reference Guide ...

Unicenter ® CA-Scheduler ®
Job Management for VSE
Reference Guide Part 2
r7.3
K01169-1E

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

Contents
Chapter 5. Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
5.1 Report Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.2 Coding Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
5.3 Display and Analysis Reports . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.3.1 Analyze Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6
5.3.1.1 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.3.1.2 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8
5.3.2 Analyze Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-9
5.3.2.1 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.3.2.2 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-11
5.3.3 List Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12
5.3.3.1 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
5.3.3.2 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
5.3.3.3 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
5.3.4 List Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-14
5.3.4.1 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
5.3.4.2 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
5.3.4.3 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
5.3.5 List Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-16
5.3.5.1 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
5.3.5.2 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17
5.3.6 List Userid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19
5.3.6.1 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
5.3.6.2 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
5.3.6.3 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-20
5.4 Batch Versions of Online Reports . . . . . . . . . . . . . . . . . . . . . 5-21
5.4.1 Abended Job Schedule . . . . . . . . . . . . . . . . . . . . . . . . . 5-21
5.4.1.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22
5.4.1.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23
5.4.2 Closed Data Set Report . . . . . . . . . . . . . . . . . . . . . . . . 5-23
5.4.3 Completed Job Schedule . . . . . . . . . . . . . . . . . . . . . . . . 5-25
5.4.3.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-27
5.4.3.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
5.4.3.3 Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
5.4.3.4 Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
5.4.3.5 Example 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28
5.4.3.6 Example 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-29
5.4.4 Date Translation Report . . . . . . . . . . . . . . . . . . . . . . . . 5-29
5.4.5 File Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31
Contents iii

5.4.6 Job Average Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34
5.4.6.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
5.4.6.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
5.4.7 Job History Report . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-35
5.4.7.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-37
5.4.7.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
5.4.8 Successor Chain List . . . . . . . . . . . . . . . . . . . . . . . . . . 5-38
5.4.8.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
5.4.8.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
5.4.8.3 Example 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
5.4.8.4 Example 4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
5.4.8.5 Example 5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-40
5.4.8.6 Example 6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
5.4.8.7 Example 7 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
5.4.8.8 Example 8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41
5.5 Tapepull Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
5.5.1 TAPEPULL GROUP . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
5.5.1.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42
5.5.1.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-42
5.5.1.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
5.5.1.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-43
5.5.2 TAPEPULL JOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
5.5.2.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44
5.5.2.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-44
5.5.2.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
5.5.2.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45
5.6 Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46
5.6.1 Summary of the Simulation Reports . . . . . . . . . . . . . . . . . 5-47
5.6.2 Summary of the SIMULATE Command Keywords . . . . . . . . 5-49
5.6.3 Summary of the Simulation Commands . . . . . . . . . . . . . . 5-50
5.6.4 Virtual Storage Requirements for Simulation . . . . . . . . . . . 5-51
5.6.4.1 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52
5.6.5 Selection Criteria's Impact on Simulation . . . . . . . . . . . . . . 5-52
5.7 Simulation Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53
5.7.1 EXCLUDE Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53
5.7.1.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53
5.7.1.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-53
5.7.1.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
5.7.1.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
5.7.2 EXCLUDE Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
5.7.2.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54
5.7.2.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-55
5.7.2.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
5.7.2.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55
5.7.3 HOLD Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
5.7.3.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56
5.7.3.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-56
5.7.3.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57
5.7.3.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57
5.7.4 HOLD Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57
5.7.4.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57
iv Unicenter CA-Scheduler Reference Guide, Part 2

5.7.4.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-57
5.7.4.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58
5.7.4.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58
5.7.5 ONLY Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59
5.7.5.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59
5.7.5.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-59
5.7.5.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59
5.7.5.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60
5.7.6 OVERRIDE Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60
5.7.6.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60
5.7.6.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-60
5.7.6.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61
5.7.6.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61
5.7.7 OVERRIDE Resource . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62
5.7.7.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62
5.7.7.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-62
5.7.7.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66
5.7.7.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66
5.7.8 OVERRIDE Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67
5.7.8.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67
5.7.8.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-67
5.7.8.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68
5.7.8.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68
5.7.9 OVERRIDE SHRRSR . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68
5.7.9.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68
5.7.9.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-69
5.7.9.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
5.7.9.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
5.7.10 OVERRIDE Station . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
5.7.10.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71
5.7.10.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-72
5.7.10.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72
5.7.10.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73
5.7.11 RELEASE JOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73
5.7.11.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73
5.7.11.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-73
5.7.11.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74
5.7.11.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-74
5.7.12 RELEASE SCHEDULE . . . . . . . . . . . . . . . . . . . . . . . . 5-75
5.7.12.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75
5.7.12.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-75
5.7.12.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75
5.7.12.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76
5.7.13 REQUEST Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76
5.7.13.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76
5.7.13.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-76
5.7.13.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77
5.7.13.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77
5.7.14 REQUEST Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78
5.7.14.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78
Contents v

5.7.14.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-78
5.7.14.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78
5.7.14.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-79
5.7.15 RERUN Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-79
5.7.15.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-79
5.7.15.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-79
5.7.15.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-80
5.7.15.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-80
5.7.16 RONLY Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-81
5.7.16.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-81
5.7.16.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-81
5.7.16.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-81
5.7.16.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-82
5.7.17 RUN Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-82
5.7.17.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-82
5.7.17.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-82
5.7.17.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-83
5.7.17.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-83
5.7.18 RUN Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-84
5.7.18.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-84
5.7.18.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-84
5.7.18.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-84
5.7.18.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85
5.7.19 SIMULATE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85
5.7.19.1 Optional Object . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85
5.7.19.2 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85
5.7.19.3 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-86
5.7.19.4 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-90
5.7.19.5 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-91
5.8 Simulation Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-93
5.8.1 Backlogged Schedules/Jobs (BACKLOG) . . . . . . . . . . . . . . 5-93
5.8.2 Date Translation Report (DATETRAN) . . . . . . . . . . . . . . . 5-95
5.8.3 Late Job Profile (LATEJOBS) . . . . . . . . . . . . . . . . . . . . . 5-103
5.8.4 Resources Required for All Selected Jobs (RESALL) . . . . . . . 5-105
5.8.5 Schedules/Jobs Selected for DD MM YY (SELECTED) . . . . . . 5-107
5.8.6 Simulated Device Utilization (DEVUTIL) . . . . . . . . . . . . . . 5-110
5.8.7 Simulated Execution Schedule (SIMEXEC) . . . . . . . . . . . . . 5-111
5.8.8 Simulated Shared Device Utilization (DEVUTIL) . . . . . . . . . 5-112
5.8.9 Simulated Unit Utilization (UNITUTIL) . . . . . . . . . . . . . . . 5-112
5.8.10 Tracking File Job Start Errors (EXPERROR) . . . . . . . . . . . . 5-114
5.9 Forecasting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-115
5.9.1 Summary of the Forecast Commands . . . . . . . . . . . . . . . . 5-116
5.9.2 Virtual Storage Requirements for Forecasting . . . . . . . . . . . 5-116
5.9.2.1 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-117
5.10 Forecast Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-118
5.10.1 EXCLUDE JOB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-118
5.10.1.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-118
5.10.1.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-118
5.10.1.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-119
5.10.1.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-119
5.10.2 EXCLUDE SCHEDULE . . . . . . . . . . . . . . . . . . . . . . . . 5-120
vi Unicenter CA-Scheduler Reference Guide, Part 2

5.10.2.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-120
5.10.2.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-120
5.10.2.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-120
5.10.2.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-120
5.10.3 ONLY Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-121
5.10.3.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-121
5.10.3.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-121
5.10.3.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-121
5.10.3.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-122
5.10.4 REQUEST Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-122
5.10.4.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-122
5.10.4.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-122
5.10.4.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-123
5.10.4.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-123
5.10.5 REQUEST Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . 5-123
5.10.5.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-124
5.10.5.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-124
5.10.5.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-124
5.10.5.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-124
5.10.6 RUN Job . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-125
5.10.6.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-125
5.10.6.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-125
5.10.6.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-126
5.10.6.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-126
5.10.7 RUN Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-126
5.10.7.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-126
5.10.7.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-127
5.10.7.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-127
5.10.7.4 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-127
5.10.8 FORECAST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-128
5.10.8.1 Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-128
5.10.8.2 Keyword Descriptions . . . . . . . . . . . . . . . . . . . . . . 5-128
5.10.8.3 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-130
5.10.8.4 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-131
5.10.8.5 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-131
5.11 Forecast Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-132
5.11.1 Job Summary (SUMMARY) . . . . . . . . . . . . . . . . . . . . . 5-132
5.11.2 Predecessors Required for Jobs at Station X (PREDS) . . . . . . 5-133
5.11.3 Resources Required for All Selected Jobs (RESALL) . . . . . . . 5-135
5.11.4 Resources Required for Jobs at Station X (RESSTN) . . . . . . . 5-137
5.11.5 Run Book (RUNBOOK) . . . . . . . . . . . . . . . . . . . . . . . . 5-138
5.11.6 Schedules/Jobs Selected for DD MM YY (SELECTED) . . . . . 5-144
5.11.7 Schedules/Jobs Selected for Station X (STATION) . . . . . . . . 5-147
5.12 Advantage CA-Earl Automatic Console Reply Reports . . . . . . . 5-151
5.12.1 Automatic Console Reply (by Job) . . . . . . . . . . . . . . . . . 5-151
5.12.2 Automatic Console Reply (by Schedule) . . . . . . . . . . . . . . 5-153
5.12.3 Automatic Console Reply (by Message Number) . . . . . . . . 5-155
5.12.3.1 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-157
5.13 Advantage CA-Earl Database Reports . . . . . . . . . . . . . . . . . . 5-158
5.13.1 Basic Job Information (by Schedule) . . . . . . . . . . . . . . . . 5-158
Contents vii

5.13.2 Basic Job Information (by Station) . . . . . . . . . . . . . . . . . 5-160
5.13.3 Job Criteria (by Schedule) . . . . . . . . . . . . . . . . . . . . . . 5-162
5.14 Advantage CA-Earl History File Reports . . . . . . . . . . . . . . . . 5-165
5.14.1 Abended Job Profile . . . . . . . . . . . . . . . . . . . . . . . . . . 5-165
5.14.2 Completed Job Profile . . . . . . . . . . . . . . . . . . . . . . . . . 5-167
5.14.3 Forced and Canceled Jobs . . . . . . . . . . . . . . . . . . . . . . 5-169
5.14.4 Late Job Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-171
5.14.5 Pending Job Profile . . . . . . . . . . . . . . . . . . . . . . . . . . 5-173
5.14.6 Scheduled Job Status (by Schedule) . . . . . . . . . . . . . . . . 5-175
5.14.7 Scheduled Job Status (by Station) . . . . . . . . . . . . . . . . . . 5-178
5.15 Advantage CA-Earl Tracking File Reports . . . . . . . . . . . . . . . 5-181
5.15.1 Abended Job Profile . . . . . . . . . . . . . . . . . . . . . . . . . . 5-181
5.15.2 Canceled Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-183
5.15.3 Completed Job Profile . . . . . . . . . . . . . . . . . . . . . . . . . 5-186
5.15.4 Pending Job Profile . . . . . . . . . . . . . . . . . . . . . . . . . . 5-188
5.15.5 Pending Schedules Report . . . . . . . . . . . . . . . . . . . . . . 5-191
5.15.6 Schedule Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-194
5.15.7 Scheduled Job Status (by Schedule) . . . . . . . . . . . . . . . . 5-197
5.15.8 Scheduled Job Status (by Station) . . . . . . . . . . . . . . . . . . 5-200
5.16 Advantage CA-Earl Documentation File Reports . . . . . . . . . . . 5-204
5.16.1 Documentation Directory And Member List . . . . . . . . . . . 5-204
5.16.2 Documentation Directory List . . . . . . . . . . . . . . . . . . . . 5-208
5.16.3 Documentation Selected By The Tracking File . . . . . . . . . . 5-210
5.17 Advantage CA-Earl Staging File Reports . . . . . . . . . . . . . . . . 5-218
5.17.1 Staged JCL Directory And Member List . . . . . . . . . . . . . . 5-218
5.17.2 Staged JCL Library Directory List . . . . . . . . . . . . . . . . . 5-222
5.18 Batch Reporting for CAIAUDIT . . . . . . . . . . . . . . . . . . . . . 5-225
5.18.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-225
5.18.2 UPSI Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-225
5.18.3 Audited Events Report . . . . . . . . . . . . . . . . . . . . . . . . 5-225
5.18.4 Audited Commands/Text Report . . . . . . . . . . . . . . . . . . 5-227
5.18.5 Audited Messages Report . . . . . . . . . . . . . . . . . . . . . . 5-229
5.18.6 Audited Commands/Response Report . . . . . . . . . . . . . . 5-231
Appendix A. Criteria Vocabulary . . . . . . . . . . . . . . . . . . . . . . . A-1
A.1 Reserved Words . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
A.2 Gregorian Calendar Conditions . . . . . . . . . . . . . . . . . . . . . . A-4
A.3 Workday Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
A.4 Accounting Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
Appendix B. Batch Command Examples . . . . . . . . . . . . . . . . . . . B-1
B.1 Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
B.1.1 Example 1: Define STation . . . . . . . . . . . . . . . . . . . . . . . B-2
B.1.2 Example 2: ALter STation . . . . . . . . . . . . . . . . . . . . . . . . B-2
B.1.3 Example 3: DELete STation . . . . . . . . . . . . . . . . . . . . . . . B-3
B.2 Userids . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
B.2.1 Example 1: Define USerid . . . . . . . . . . . . . . . . . . . . . . . . B-4
B.2.2 Example 2: ALter USerid . . . . . . . . . . . . . . . . . . . . . . . . B-4
B.2.3 Example 3: DELete USerid . . . . . . . . . . . . . . . . . . . . . . . B-5
B.3 Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
B.3.1 Example 1: Define SBR . . . . . . . . . . . . . . . . . . . . . . . . . B-6
viii Unicenter CA-Scheduler Reference Guide, Part 2

B.3.2 Example 2: Define SBR . . . . . . . . . . . . . . . . . . . . . . . . . B-7
B.3.2.1 Example 3: ALter SBR . . . . . . . . . . . . . . . . . . . . . . . B-7
B.3.2.2 Example 4: DELete SBR . . . . . . . . . . . . . . . . . . . . . . B-8
B.3.2.3 Example 5: DELete SCHEDULE . . . . . . . . . . . . . . . . . B-8
B.3.3 Define Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-8
B.3.3.1 Example 1: Define SCR . . . . . . . . . . . . . . . . . . . . . . . B-8
B.3.3.2 Example 2: Define SCR . . . . . . . . . . . . . . . . . . . . . . . B-9
B.3.3.3 Example 3: ALter SCR . . . . . . . . . . . . . . . . . . . . . . . B-9
B.3.3.4 Example 4: DELete SCR . . . . . . . . . . . . . . . . . . . . . B-10
B.3.4 Reasons Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10
B.3.4.1 Example 1: Define SRC . . . . . . . . . . . . . . . . . . . . . . B-10
B.3.4.2 Example 2: ALter SRC . . . . . . . . . . . . . . . . . . . . . . B-11
B.3.4.3 Example 3: DELete SRC . . . . . . . . . . . . . . . . . . . . . B-11
B.3.5 Message Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . B-12
B.3.5.1 Example 1: Define SMR . . . . . . . . . . . . . . . . . . . . . B-12
B.3.5.2 Example 2: ALter SMR . . . . . . . . . . . . . . . . . . . . . . B-12
B.3.5.3 Example 3: DELete SMR . . . . . . . . . . . . . . . . . . . . . B-12
B.3.6 Info Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-13
B.3.6.1 Example 1: Define SIR . . . . . . . . . . . . . . . . . . . . . . B-13
B.3.6.2 Example 2: ALter SIR . . . . . . . . . . . . . . . . . . . . . . . B-13
B.3.6.3 Example 3: DELete SIR . . . . . . . . . . . . . . . . . . . . . . B-14
B.4 Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15
B.4.1 Define JBR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15
B.4.1.1 Example 1: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-15
B.4.1.2 Example 2: Define JBR . . . . . . . . . . . . . . . . . . . . . . B-16
B.4.1.3 Example 3: Define JBR . . . . . . . . . . . . . . . . . . . . . . B-17
B.4.1.4 Example 4: ALter JBR . . . . . . . . . . . . . . . . . . . . . . . B-17
B.4.1.5 Example 5: DELete JBR . . . . . . . . . . . . . . . . . . . . . . B-18
B.4.1.6 Example 6: DELete JOB . . . . . . . . . . . . . . . . . . . . . B-18
B.4.2 Define Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-19
B.4.2.1 Example 1: Define JCR . . . . . . . . . . . . . . . . . . . . . . B-19
B.4.2.2 Example 2: Define JCR . . . . . . . . . . . . . . . . . . . . . . B-19
B.4.2.3 Example 3: Define JCR . . . . . . . . . . . . . . . . . . . . . . B-20
B.4.2.4 Example 4: ALter JCR . . . . . . . . . . . . . . . . . . . . . . B-20
B.4.2.5 Example 5: DELete JCR . . . . . . . . . . . . . . . . . . . . . B-21
B.4.3 Reasons Definition (Jobs) . . . . . . . . . . . . . . . . . . . . . . . B-21
B.4.3.1 Example 1: Define JRC . . . . . . . . . . . . . . . . . . . . . . B-21
B.4.3.2 Example 2: ALter JRC . . . . . . . . . . . . . . . . . . . . . . B-22
B.4.3.3 Example 3: DELete JRC . . . . . . . . . . . . . . . . . . . . . B-22
B.4.4 Message Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . B-22
B.4.4.1 Example 1: Define JMR . . . . . . . . . . . . . . . . . . . . . . B-22
B.4.4.2 Example 2: ALter JMR . . . . . . . . . . . . . . . . . . . . . . B-23
B.4.4.3 Example 3: DELete JMR . . . . . . . . . . . . . . . . . . . . . B-24
B.4.5 Info Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-24
B.4.5.1 Example 1: Define JIR . . . . . . . . . . . . . . . . . . . . . . B-24
B.4.5.2 Example 2: ALter JIR . . . . . . . . . . . . . . . . . . . . . . . B-24
B.4.5.3 Example 3: DELete JIR . . . . . . . . . . . . . . . . . . . . . . B-25
B.4.6 Resource Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . B-25
B.4.6.1 Example 1: Define JRR . . . . . . . . . . . . . . . . . . . . . . B-25
B.4.6.2 Example 2: ALter JRR . . . . . . . . . . . . . . . . . . . . . . B-26
Contents ix

B.4.6.3 Example 3: DELete JRR . . . . . . . . . . . . . . . . . . . . . . B-26
B.4.7 Defining Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . B-27
B.4.7.1 Example 1: Define RESource . . . . . . . . . . . . . . . . . . B-27
B.4.7.2 Example 2: Define RESource . . . . . . . . . . . . . . . . . . B-28
B.4.7.3 Example 3: ALter RESource . . . . . . . . . . . . . . . . . . . B-29
B.4.7.4 Example 4: DELete RESource . . . . . . . . . . . . . . . . . . B-29
Appendix C. Editor Commands . . . . . . . . . . . . . . . . . . . . . . . . . C-1
C.1 Line Protection and Highlighting . . . . . . . . . . . . . . . . . . . . . . C-2
C.2 Input Area Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-3
C.3 Prefix Area Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
C.3.1 Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
C.3.1.1 Changing the Current Line . . . . . . . . . . . . . . . . . . . . C-6
C.3.1.2 Adding Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-7
C.3.1.3 Deleting Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-8
C.3.1.4 Copying Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9
C.3.1.5 Moving Lines . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10
C.3.1.6 Duplicating Lines . . . . . . . . . . . . . . . . . . . . . . . . . C-11
C.4 Staging Editor Commands . . . . . . . . . . . . . . . . . . . . . . . . . C-12
C.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-12
C.4.2 DEXPAND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
C.4.2.1 Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
C.4.2.2 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-13
C.4.2.3 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-14
C.4.3 DPROMPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-16
C.4.3.1 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-16
C.4.3.2 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-16
C.4.4 DSET . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-19
C.4.4.1 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-19
C.4.5 RECALL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20
C.4.5.1 Usage Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20
C.4.5.2 Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-20
C.5 PF Key Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-23
Appendix D. Advantage CA-Earl Reports . . . . . . . . . . . . . . . . . D-1
D.1 All Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-2
D.1.1 CAJEPM Source Member . . . . . . . . . . . . . . . . . . . . . . . D-2
D.1.2 CAISTMD Source Member . . . . . . . . . . . . . . . . . . . . . . D-2
D.2 Database Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4
D.2.1 CAJECRI Source Member . . . . . . . . . . . . . . . . . . . . . . . D-4
D.2.2 CAJEGLBL Source Member . . . . . . . . . . . . . . . . . . . . . D-5
D.2.3 CAJESETM Source Member . . . . . . . . . . . . . . . . . . . . . D-8
D.2.3.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-8
D.2.3.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-8
D.2.4 Job Information from Database . . . . . . . . . . . . . . . . . . . D-9
D.2.5 Schedule Information from Database . . . . . . . . . . . . . . . . D-17
D.3 History File Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-22
D.3.1 CAJESETH Source Member . . . . . . . . . . . . . . . . . . . . . D-22
D.3.2 CAJECNVS Source Member . . . . . . . . . . . . . . . . . . . . . D-22
D.3.3 CAIDEFD Source Member . . . . . . . . . . . . . . . . . . . . . . D-22
D.3.4 Job Information from History File . . . . . . . . . . . . . . . . . . D-24
x Unicenter CA-Scheduler Reference Guide, Part 2

D.3.5 Schedule Information from History File . . . . . . . . . . . . . . D-26
D.4 Tracking File Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-28
D.4.1 CAJESETT Source Member . . . . . . . . . . . . . . . . . . . . . . D-28
D.4.2 CAJESETS Source Member . . . . . . . . . . . . . . . . . . . . . . D-28
D.4.3 CAJECNV0 Source Member . . . . . . . . . . . . . . . . . . . . . D-29
D.4.4 Job Information from Tracking File . . . . . . . . . . . . . . . . . D-32
D.4.5 Schedule Information from Tracking File . . . . . . . . . . . . . D-36
D.5 Documentation or Staging Library Reports . . . . . . . . . . . . . . . D-39
D.5.1 CAJESETD Source Member . . . . . . . . . . . . . . . . . . . . . . D-39
D.5.2 CAJDDIR Source Member . . . . . . . . . . . . . . . . . . . . . . D-39
D.5.3 CAJESETG Source Member . . . . . . . . . . . . . . . . . . . . . . D-40
D.5.4 CAJSDIR Source Member . . . . . . . . . . . . . . . . . . . . . . . D-40
D.5.5 CAJMBR Source Member . . . . . . . . . . . . . . . . . . . . . . . D-40
D.5.6 Information from Documentation or Staging Library . . . . . . D-41
D.6 Information from CAIAUDIT . . . . . . . . . . . . . . . . . . . . . . . D-42
Appendix E. Event Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-1
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1
Contents xi

Chapter 5. Reports
This chapter contains all the information you will need to produce any or all of
the reports available with Unicenter® CA-Scheduler® Job Management for
VSE (Unicenter CA-Scheduler).
Chapter 5. Reports 5-1

5.1 Report Categories
5.1 Report Categories
The reports fall into five general categories and are presented in the following
order:
1. Database Analysis And Display
These reports list all the records and values that have been defined for
jobs, schedules, stations, and userids. The analysis reports, in addition,
print messages informing you of conflicts that must be resolved before jobs
or schedules can be selected for processing. These reports are:
Analyze Job
Analyze Schedule
List Job
List Schedule
List Station
List Userid
2. Batch Versions Of Online Reports
These reports provide information on jobs and schedules that have run
today or have been selected to run today. (See the topic Reporting Facility
in the chapter "Online Panels and Batch Maintenance" in the Unicenter
CA-Scheduler Reference Guide Part 1 to display these reports online.) These
reports are:
Abended Job Schedule
Closed Data Set Report
Completed Job Schedule
Date Translation Report
File Status Report
Job Average Report
Job History Report
Successor Chain List
3. Simulation Reports
These reports are produced while Unicenter CA-Scheduler is being run in
simulation mode, where no jobs are actually run. The reports show what
schedules and jobs would be selected today, and when and where the jobs
would be processed. By using the simulation commands, you can see the
effects of changing values for each simulation run. The reports are:
Backlogged Schedules/Jobs
Date Translation Report
Late Job Profile
Resources Required For All Selected Jobs
5-2 Unicenter CA-Scheduler Reference Guide, Part 2

5.1 Report Categories
Schedules/Jobs Selected For DD MM YY
Simulated Device Utilization
Simulated Execution Schedule
Simulated Shared Device Utilization
Simulated Unit Utilization
Tracking File Job Start Errors
4. Forecast Reports
These reports provide information on jobs and schedules that will be
selected for processing on a future date or range of dates. They are
predictions of what would occur under a predefined set of conditions. By
using the forecast commands, you can see the effects of changing values
for each forecast period. The reports are:
Job Summary
Predecessors Required For Jobs At Station X
Resourced Required For All Selected Jobs
Resources Required For Jobs At Station X
Route Station Report For Station X
Run Book
Schedules/Jobs Selected For DD MM YY
Schedules/Jobs Selected For Station X
5. Advantage CA-Earl Reports
These are user-defined reports produced by using Advantage CA-Earl.
The information for these reports can be taken from the Unicenter
CA-Scheduler database, the history file, the tracking file, the
documentation library, or the JCL staging library. Samples of each of these
reports are provided, but they may be modified to give any information
you want to include.
■
The sample reports from the database are:
Basic Job Information By Schedule
Basic Job Information By Station
Job Criteria By Schedule
Chapter 5. Reports 5-3

5.1 Report Categories
■
■
■
■
■
The sample reports from the history file are:
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
The sample reports from the tracking file are:
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
The sample reports from the documentation library are:
Documentation Directory And Member List
Documentation Directory List
Documentation Selected By The Tracking File
The sample reports from the staging library are:
Staged JCL Directory And Member List
Staged JCL Library Directory List
The sample reports from the CAIAUDIT file are:
Audited Events Report
Audited Commands/Text Report
Audited Messages Report
Audited Commands/Response Report
All of the reports are illustrated and explained in the above order in this
chapter.
5-4 Unicenter CA-Scheduler Reference Guide, Part 2

5.2 Coding Requirements
5.2 Coding Requirements
Commands consists of a verb, an object, keywords, and their values:
■
■
■
■
■
■
■
■
■
■
Code one or more blank characters before and after the object.
Keywords may be required or optional (as specified for each command).
Objects may be required or optional.
The default value of a keyword is assumed. To select it, do not code the
keyword.
Separate the keyword and its value with an EQUAL sign.
Separate keywords with commas.
Enclose multiple keyword values in parentheses and separate them with
commas.
Enclose keyword values in single quotes as indicated. If the text of a
comment, description, memo, or criteria statement contains a single quote,
precede it with an extra quote. The extra quote will be removed when the
text prints.
To delete a keyword, specify the value as NULL. (Example:
CLASS=NULL)
Keywords may not begin with a blank.
Commands from batch may begin in any column and must end by column 72:
.
■
■
A command may be continued on additional lines. Divide commands
between keywords or between multiple keyword values, ending one line
with a comma and beginning the continuation in any column on the next
line. Keyword values enclosed in quotes, such as criteria statements, may
be divided between any two words.
Use an asterisk in column one to indicate a comment line. Comments may
follow keywords if they are separated by one or more blanks:
ANALYZE JOB NAME=jname,SCHEDULE=sname
Chapter 5. Reports 5-5

5.3 Display and Analysis Reports
5.3 Display and Analysis Reports
5.3.1 Analyze Job
This topic shows each of the Display and Analysis reports, gives usage notes,
and shows examples of JCL to produce each report.
This Analyze Job report analyzes a defined job to identify conflicts that must
be resolved before the job is selected for processing. It shows each record that
has been defined for the job and all the values defined in each record. The
sample report following analyzes a job named JOB11 in the SCHD01 schedule.
The error message indicates that a predecessor deadlock has occurred. This is
because JOB11 and JOB12 have been defined as predecessors to each other,
causing neither to be selected for processing.
5-6 Unicenter CA-Scheduler Reference Guide, Part 2

5.3 Display and Analysis Reports
COMPUTER ASSOCIATES JOB SCHEDULING SYSTEM UTILITY LOG CAJUTIL PAGE 1
CA-SCHEDULER 7.3 39SH73
3 SEP 23 16.26.5
ANALYZE JOB N=JOB11,S=SCHD1
JOB BASE RECORD
------------------------------
JOB: JOB11 EARLY TIME = /. DOC DISP KEY = CLASS = AUTO START = INTERRUPT =
JOB# 1 MUST TIME = /. NODEID = PRTY = RECOVER = USE SIMTIM=
STATION 4 DEADLINE TIME = /. LIBTYPE = DRIVER SUBLIB = JMR REC = YES
SCHEDULE SCHD1 MAX TIME = /. LIBMEMB = JOB11 SYSID = DRIVER PARMS = YES JIR REC = YES
SIM ST TIME = /11.15 LIBMPASS = PRIORITY = STAGING = YES JRR REC = YES
AVG ELAP TIME = /. LIBMBR SUBID = CPU JOB = BACKLOG = YES JRC REC = YES
DOC DISP TIME = /. ABEND = ABORT FAIL CODE = JCR REC = YES
LAST USER = CALENDAR = SKIP = JNR REC =
MEMO = NODE SYSID=
TESTLIB PARMS = USER INFO =
CRITERIA: JOB12-1 4 SCHD1
JOB MESSAGE RECORD
------------------------------
JOB: JOB11 JOB#= 1 STATION ID= 4 SCHEDULE= SCHD1
ALL MSG USERID LIST=
END MSG USERID LIST= MARK
FAIL MSG USERID LIST=
ABEND MSG USERID LIST= MARK
INTERRUPT MSG USERID LIST= MARK
LATE MSG USERID LIST= MARK
PURGE MSG USERID LIST=
START MSG USERID LIST= MARK
CACU4E SCHD1 JOB12 14 DEADLOCK WITH PREDECESSOR SCHD1 JOB11 14
JOB BASE RECORD
------------------------------
JOB: JOB11 EARLY TIME = /. DOC DISP KEY = CLASS = AUTO START = YES INTERRUPT =
JOB# 1 MUST TIME = /. NODEID = PRTY = RECOVER = USE SIMTIM=
STATION 2 DEADLINE TIME = /. LIBTYPE = SUBLIB = JMR REC =
SCHEDULE SCHD1 MAX TIME = /. LIBMEMB = SYSID = DRIVER PARMS = JIR REC =
SIM ST TIME = /11. LIBMPASS = PRIORITY = STAGING = JRR REC = YES
AVG ELAP TIME = /.5 LIBMBR SUBID = CPU JOB = NO BACKLOG = JRC REC =
DOC DISP TIME = /. ABEND = FAIL CODE = JCR REC =
LAST USER = CALENDAR = SKIP = JNR REC =
MEMO = NODE SYSID=
TESTLIB PARMS = USER INFO =
CACU18I JOB JOB11 HAS BEEN ANALYZED
To produce the basic report, submit the following JCL with your job statement:
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
ANALYZE JOB NAME=jname,SCHEDULE=sname job name and schedule name
/
/&
Chapter 5. Reports 5-7

5.3 Display and Analysis Reports
5.3.1.1 Usage Notes
Use the Analyze Job report to analyze jobs that have been added or changed
since their schedules were analyzed. We recommend that you run this report
for the entire database after adding schedules and jobs. Correct all errors
before allowing Unicenter CA-Scheduler to select the schedule that the job is
assigned to.
Any schedule or job parameters that were not specified at schedule or job
definition time (that is, left to default values), will NOT be displayed when the
schedule or job is analyzed.
Error messages identify the following types of conflicts:
■
■
■
Jobs assigned to schedules that are not defined in the database.
Calendars, datetables, userids, stations, and predecessors that are
referenced but not defined or found.
Predecessor/successor deadlocks.
A deadlock situation arises when two or more jobs have been defined as
predecessors or successors to each other. For example, if JOBA has been
defined as a predecessor to JOBB, and JOBB has been defined as a predecessor
to JOBA, neither job will run because their predecessors cannot start and
complete.
To analyze a group of jobs that begin with the same characters, specify the
jobname as a generic. To do this, code the common characters followed by an
asterisk.
To suppress the printing of all the job records with all their defined values,
specify LIST=NO. Only the four fields that uniquely identify the job (job name,
job number, station, and schedule name) will be printed, followed by any error
messages.
To limit the report to jobs with errors, specify LIST=ERR.
5.3.1.2 Example
The following example shows what will be printed if the LIST=NO option is
used. It analyzes the job as before, but only prints the job's key fields,
followed by the error messages.
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
ANALYZE JOB NAME=JOB11,
jobname
SCHEDULE=SCHD1,
schedule name
/
/&
LIST=NO
5-8 Unicenter CA-Scheduler Reference Guide, Part 2

5.3 Display and Analysis Reports
COMPUTER ASSOCIATES JOB SCHEDULING SYSTEM UTILITY LOG CAJUTIL PAGE 1
CA-SCHEDULER 7.3 39SH73
3 SEP 23 16.9.55
ANALYZE JOB N=JOB11,S=SCHD1,LIST=NO
JOB: JOB11 JOB#= 1 STATION ID= 4 SCHEDULE= SCHD1
CACU4E SCHD1 JOB12 14 DEADLOCK WITH PREDECESSOR SCHD1 JOB11 14
JOB: JOB11 JOB#= 1 STATION ID= 2 SCHEDULE= SCHD1
JOB: JOB11 JOB#= 1 STATION ID= 39 SCHEDULE= SCHD1
JOB: JOB11 JOB#= 1 STATION ID= 6 SCHEDULE= SCHD1
CACU18I JOB JOB11 HAS BEEN ANALYZED
5.3.2 Analyze Schedule
The Analyze Schedule report analyzes a defined schedule to identify conflicts
that must be resolved before the schedule is selected for processing. It shows
each record that has been defined for this schedule and all of the values
defined in each record. It also shows the records and values defined for each
job assigned to the schedule. The sample report following analyzes the
schedule named SCHD01.
Chapter 5. Reports 5-9

5.3 Display and Analysis Reports
COMPUTER ASSOCIATES JOB SCHEDULING SYSTEM UTILITY LOG CAJUTIL PAGE 1
CA-SCHEDULER 7.3 39SH73 3 SEP 23 16.39.25
ANALYZE SCHEDULE NAME=SCHD1
SCHEDULE BASE RECORD
------------------------------
SCHEDULE= SCHD1 SCHD PRTY = EARLY TIME = /. STAGE JCL = NO SIR REC = YES
AUTO SELECT = YES MUST TIME = /. USE SIM TIME= NO SMR REC = YES
SYSID = DEADLINE TIME = /. CLASS = SRC REC = YES
DATE TABLE = DATETAB MAX TIME = /. PRTY = SCR REC = YES
NODE ID = AVG ELAP TIME = /. USER INFO =
SIM ST TIME = /11. LIBTYPE = DRIVER NO OF JOBS = 12 BACKLOG = YES
USERID LIST =
LAST USER = CALENDAR = SKIP = NODE SYS=
CRITERIA: DAILY
SCHEDULE REASON CODE RECORD
------------------------------
SCHEDULE: SCHD1
EARLY TIME LIST 1= /11. 2= /12. 3= /13. 4= /14. 5= 6= 7= 8=
9= 1= 11= 12= 13= 14= 15= 16=
MUST TIME LIST 1= /11.3 2= /12.3 3= /13.3 4= /14.3 5= 6= 7= 8=
9= 1= 11= 12= 13= 14= 15= 16=
DEADLINE TIME LIST 1= 2= 3= 4= 5= 6= 7= 8=
9= 1= 11= 12= 13= 14= 15= 16=
MAXIMUM TIME LIST 1= 2= 3= 4= 5= 6= 7= 8=
9= 1= 11= 12= 13= 14= 15= 16=
JOB BASE RECORD
------------------------------
JOB: JOB11 EARLY TIME = /. DOC DISP KEY = CLASS = AUTO START = INTERRUPT =
JOB# 1 MUST TIME = /. NODEID = PRTY = RECOVER = USE SIMTIM=
STATION 4 DEADLINE TIME = /. LIBTYPE = DRIVER SUBLIB = JMR REC = YES
SCHEDULE SCHD1 MAX TIME = /. LIBMEMB = JOB11 SYSID = DRIVER PARMS = YES JIR REC = YES
SIM ST TIME = /11.15 LIBMPASS = PRIORITY = STAGING = YES JRR REC = YES
AVG ELAP TIME = /. LIBMBR SUBID = CPU JOB = BACKLOG = YES JRC REC = YES
DOC DISP TIME = /. ABEND = ABORT FAIL CODE = JCR REC = YES
LAST USER = CALENDAR = SKIP = JNR REC =
MEMO = NODE SYSID=
TESTLIB PARMS = USER INFO =
CRITERIA: JOB12-1 4 SCHD1
CACU4E SCHD1 JOB12 14 DEADLOCK WITH PREDECESSOR SCHD1 JOB11 14
CACU18I SCHEDULE SCHD1 HAS BEEN ANALYZED
To produce the basic report, submit the following JCL with your job statement:
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
ANALYZE SCHEDULE NAME=sname
schedule name
/
/&
5-10 Unicenter CA-Scheduler Reference Guide, Part 2

5.3 Display and Analysis Reports
5.3.2.1 Usage Notes
Use the Analyze Schedule report after adding schedules and jobs to your
database. We strongly recommend that you run it for the entire database. Any
schedules or job parameters that were not specified at schedule or job
definition time (that is, left to default values), will not be displayed when the
schedule or job is analyzed.
Analyze all schedules and correct all errors before allowing Unicenter
CA-Scheduler to start automatic selection.
Error messages identify the following types of conflicts:
■
■
■
Schedules with no defined jobs.
Calendars, datetables, userids, stations, and predecessors that are
referenced but not defined.
Predecessor/successor deadlocks.
A deadlock situation arises when two or more jobs have been defined as
predecessors or successors to each other. For example, if JOBA has been
defined as a predecessor to JOBB, and JOBB has been defined as a predecessor
to JOBA, neither job will run because their predecessors cannot start and
complete.
To analyze a group of schedules that begin with the same characters, specify
the schedule name as a generic. To do this, code the common characters
followed by an asterisk. To analyze all schedules, specify NAME=*
To print only the schedule name and errors, specify LIST=NO.
To limit the report to schedules and jobs with errors, specify LIST=ERR.
5.3.2.2 Example
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
ANALYZE SCHEDULE NAME=
/
/&
generic schedule name
The preceding example will analyze all schedules for conflicts before turning
them over to Unicenter CA-Scheduler for automatic selection.
Chapter 5. Reports 5-11

5.3 Display and Analysis Reports
5.3.3 List Job
The List Job report lists all of the records and values that have been defined
for one job or a group of jobs.
COMPUTER ASSOCIATES JOB SCHEDULING SYSTEM UTILITY LOG CAJUTIL PAGE 1
CA-SCHEDULER 7.3 39SH73
3 SEP 23 18.11.4
LIST
JOB N=JOB11
JOB BASE RECORD
------------------------------
JOB: JOB11 EARLY TIME = /. DOC DISP KEY = CLASS = AUTO START = INTERRUPT =
JOB# 1 MUST TIME = /. NODEID = PRTY = RECOVER = USE SIMTIM=
STATION 4 DEADLINE TIME = /. LIBTYPE = DRIVER SUBLIB = JMR REC = YES
SCHEDULE SCHD1 MAX TIME = /. LIBMEMB = JOB11 SYSID = DRIVER PARMS = YES JIR REC = YES
SIM ST TIME = /. LIBMPASS = PRIORITY = STAGING = YES JRR REC = YES
AVG ELAP TIME = /. LIBMBR SUBID = CPU JOB = BACKLOG = YES JRC REC = YES
DOC DISP TIME = /. ABEND = ABORT FAIL CODE = JCR REC = YES
LAST USER = MARK CALENDAR = SKIP = JNR REC =
MEMO = NODE SYSID=
TESTLIB PARMS = USER INFO =
CRITERIA: DAILY
DRIVPARM NAME = DRIVPARM VALUE:
NUMBER
DSDSPC1
DSDSPC2
TAPVER1
TAPVER2
= (PRIMEIRO,SEGUNDO,TERCEIRO)
= 35
= 8
=
=
RESTPARM NAME = RESTPARM VALUE:
NUMBER
= (QUARTO,QUINTO,SEXTO)
TAPVER1
TAPVER2
= '-1'
= '-1'
JOB REASON CODE RECORD
------------------------------
JOB: JOB11 JOB#= 1 STATION ID= 4 SCHEDULE= SCHD1
EARLY TIME LIST 1= /11.15 2= /12.3 3= /13.3 4= /14.3 5= 6= 7= 8=
9= 1= 11= 12= 13= 14= 15= 16=
MUST TIME LIST 1= /12.3 2= /13.3 3= /14.3 4= /15.3 5= 6= 7= 8=
9= 1= 11= 12= 13= 14= 15= 16=
DEADLINE TIME LIST 1= 2= 3= 4= 5= 6= 7= 8=
9= 1= 11= 12= 13= 14= 15= 16=
MAXIMUM TIME LIST 1= 2= 3= 4= 5= 6= 7= 8=
9= 1= 11= 12= 13= 14= 15= 16=
JOB INFORMATION RECORD
------------------------------
JOB: JOB11 JOB#= 1 STATION ID = 4 SCHEDULE= SCHD1 FORM =JOB11
DESCRIPTION= DESCRIPTION JOB JOB11 QUANTITY = NOTIFY= MARK
EXIT PARM = RESPONSIBILITY=
COMMENT = SPECIFICATION =
ROUTE STATION CODES = VERIFY = NO
DESTINATION LIST 1.=JOB111 2.=JOB112 3.=JOB113 4.= 5.= 6.= 7.= 8.=
5-12 Unicenter CA-Scheduler Reference Guide, Part 2

5.3 Display and Analysis Reports
COMPUTER ASSOCIATES JOB SCHEDULING SYSTEM UTILITY LOG CAJUTIL PAGE 2
CA-SCHEDULER 7.3 39SH73
3 SEP 23 18.11.4
DELIVERY LIST 1.= 2.= 3.= 4.=
5.= 6.= 7.= 8.=
JOB RESOURCE RECORD
------------------------------
JOB: JOB11 JOB#= 1 STATION ID= 4 SCHEDULE= SCHD1 ROUTE DELAY TIME = /. CPU TIME= /.
VOLSERS THAT MUST BE MOUNTED=
DASD= DASD1 3 DISK EXCPS= 111111
TAPE= TAPE1 2 TAPE EXCPS= 111111
U/R =
OTHER EXCPS=
EXCLUSIVE JOB LIST= JOB21 JOB31
SEPARATE DSNAME = EXCLUSIVE.DATASET1
5.3.3.1 Usage Notes
5.3.3.2 Example 1
To produce the basic report, submit the following JCL with your job statement:
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
LIST JOB NAME=jname
jobname
/
/&
Use the List Job report by specifying the keyword Schedule= (schedule name)
whenever the same job name appears in two or more schedules. Otherwise, all
schedules that include the specified job name are listed.
To list a group of jobs that begin with the same characters, specify the jobname
generically. To do this, code the common characters followed by an asterisk.
If any parameters were left to default values when the job was defined, those
default parameters will not be printed.
To identify conflicts in job records, run the ANALYZE JOB report.
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
LIST JOB NAME=CUST1,
/
/&
SCHEDULE=CUSTMAST
jobname
schedule name
The preceding example will list all of the job records that have been defined
for the job named CUST1 as part of the CUSTMAST schedule.
Chapter 5. Reports 5-13

5.3 Display and Analysis Reports
5.3.3.3 Example 2
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
LIST JOB NAME=PAYJ,
/
/&
5.3.4 List Schedule
SCHEDULE=PAY
generic jobname
generic schedule name
The preceding example will list all the records defined for all jobs beginning
with PAYJ in all schedules beginning with PAY.
The List Schedule report lists all of the records and values that have been
defined for one schedule or a group of schedules. In addition, the records and
values defined for each job in each schedule are listed.
5-14 Unicenter CA-Scheduler Reference Guide, Part 2

5.3 Display and Analysis Reports
COMPUTER ASSOCIATES JOB SCHEDULING SYSTEM UTILITY LOG CAJUTIL PAGE 1
CA-SCHEDULER 7.3 39SH73 3 SEP 23 15.29.22
LIST
SCHEDULE N=SCHD1
SCHEDULE BASE RECORD
------------------------------
SCHEDULE= SCHD1 SCHD PRTY = EARLY TIME = /. STAGE JCL = NO SIR REC = YES
AUTO SELECT = YES MUST TIME = /. USE SIM TIME= NO SMR REC = YES
SYSID = DEADLINE TIME = /. CLASS = SRC REC = YES
DATE TABLE = DATETAB MAX TIME = /. PRTY = SCR REC = YES
NODE ID = AVG ELAP TIME = /. USER INFO =
SIM ST TIME = /. LIBTYPE = DRIVER NO OF JOBS = 12 BACKLOG = YES
USERID LIST =
LAST USER = CALENDAR = SKIP = NODE SYS=
CRITERIA: DAILY
SCHEDULE MESSAGE RECORD
------------------------------
SCHEDULE: SCHD1 ALL MESSAGE USERID LIST=
END MESSAGE USERID LIST= MARK
LATE MESSAGE USERID LIST= MARK
START MESSAGE USERID LIST= MARK
SCHEDULE REASON CODE RECORD
------------------------------
SCHEDULE: SCHD1
EARLY TIME LIST 1= /11. 2= /12. 3= /13. 4= /14. 5= 6= 7= 8=
9= 1= 11= 12= 13= 14= 15= 16=
MUST TIME LIST 1= /11.3 2= /12.3 3= /13.3 4= /14.3 5= 6= 7= 8=
9= 1= 11= 12= 13= 14= 15= 16=
DEADLINE TIME LIST 1= 2= 3= 4= 5= 6= 7= 8=
9= 1= 11= 12= 13= 14= 15= 16=
MAXIMUM TIME LIST 1= 2= 3= 4= 5= 6= 7= 8=
9= 1= 11= 12= 13= 14= 15= 16=
SCHEDULE INFORMATION RECORD
------------------------------
SCHEDULE: SCHD1
FORM= SCHD1
DESCRIPTION= DESCRIPTION SCH SCHD1 QUANTITY= NOTIFY= MARK
RESPONSIBILITY=
COMMENT = SPECIFICATION=
EXIT PARM = VERIFY= NO
DESTINATION LIST 1.=SCHD11 2.=SCHD12 3.=SCHD13 4.= 5.= 6.= 7.= 8.=
DELIVERY LIST 1.= 2.= 3.= 4.=
5.= 6.= 7.= 8.=
JOB BASE RECORD
------------------------------
JOB: JOB11 EARLY TIME = /. DOC DISP KEY = CLASS = AUTO START = INTERRUPT =
JOB# 1 MUST TIME = /. NODEID = PRTY = RECOVER = USE SIMTIM=
STATION 4 DEADLINE TIME = /. LIBTYPE = DRIVER SUBLIB = JMR REC = YES
SCHEDULE SCHD1 MAX TIME = /. LIBMEMB = JOB11 SYSID = DRIVER PARMS = YES JIR REC = YES
SIM ST TIME = /. LIBMPASS = PRIORITY = STAGING = YES JRR REC = YES
AVG ELAP TIME = /. LIBMBR SUBID = CPU JOB = BACKLOG = YES JRC REC = YES
DOC DISP TIME = /. ABEND = ABORT FAIL CODE = JCR REC = YES
LAST USER = CALENDAR = SKIP = JNR REC =
MEMO = NODE SYSID=
TESTLIB PARMS = USER INFO =
CRITERIA: DAILY
Chapter 5. Reports 5-15

5.3 Display and Analysis Reports
5.3.4.1 Usage Notes
5.3.4.2 Example 1
5.3.4.3 Example 2
5.3.5 List Station
To produce the basic report, submit the following JCL with your job statement:
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
LIST SCHEDULE NAME=sname
schedule name
/
/&
Use the List Schedule report to list a group of schedules that begin with the
same characters by specifying the schedule name generically. To do this, code
the common characters followed by an asterisk. To list all schedules, code
NAME=*.
If any parameters were left to default values when the schedule was defined,
those default parameters will not be printed.
To identify conflicts in records, use the ANALYZE SCHEDULE command.
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
LIST SCHEDULE NAME=CUSTMAST
/
/&
schedule name
The preceding example lists all of the schedule records that have been defined
for the CUSTMAST schedule and all of the job records for jobs that have been
assigned to the CUSTMAST schedule.
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
LIST SCHEDULE NAME=
/
/&
generic schedule name
The preceding example lists all schedule and job records in the database.
This List Station report lists either one station record, a generic group of
station records, or all station records. The sample report following shows the
record that was defined for station 20, the reception of documents station.
5-16 Unicenter CA-Scheduler Reference Guide, Part 2

5.3 Display and Analysis Reports
COMPUTER ASSOCIATES JOB SCHEDULING SYSTEM UTILITY LOG CAJUTIL PAGE 1
CA-SCHEDULER 7.3 39SH73 3 SEP 23 18.24.59
LIST
STATION ID=2
STATION RECORD
------------------------------
STATION: RECPTION STATION ID= 2 START TIME = /. END TIME= /. ROUTE STATION ID= TIMEZONE ADJUST=
DESCRIPTION= RECEPTION OF DOCUMENTS STATION
TITLE = RECEPTION OF DOCUMENTS STATION
5.3.5.1 Usage Notes
5.3.5.2 Example
To produce the basic report, submit the following JCL with your job statement:
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
LIST STATION ID=nn
station ID
/
/&
Use the List Station report to list a group of stations that begin with the same
number, by specifying the number followed by an asterisk. To list all stations,
specify ID=*.
If any parameters were left to default values when the station was defined,
those default parameters will not be printed.
The following example lists all station records defined in the database in
alphabetical order by station ID.
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
LIST STATION ID=
all stations
/
/&
Chapter 5. Reports 5-17

5.3 Display and Analysis Reports
COMPUTER ASSOCIATES JOB SCHEDULING SYSTEM UTILITY LOG CAJUTIL PAGE 1
CA-SCHEDULER 7.3 39SH73 3 SEP 23 18.24.59
LIST
STATION ID=
STATION RECORD
------------------------------
STATION: RECPTION STATION ID= 2 START TIME = /. END TIME= /. ROUTE STATION ID= TIMEZONE ADJUST=
DESCRIPTION= RECEPTION OF DOCUMENTS STATION
TITLE = RECEPTION OF DOCUMENTS STATION
STATION RECORD
------------------------------
STATION: DATENTRY STATION ID= 25 START TIME = /. END TIME= /. ROUTE STATION ID= TIMEZONE ADJUST=
DESCRIPTION= DATA ENTRY OF DOCUMENTS STATION
TITLE = DATA ENTRY OF DOCUMENTS STATION
STATION RECORD
------------------------------
STATION: VERFCATN STATION ID= 3 START TIME = /. END TIME= /. ROUTE STATION ID= TIMEZONE ADJUST=
DESCRIPTION= DATA ENTRY VERIFICATION STATION
TITLE = DATA ENTRY VERIFICATION STATION
STATION RECORD
------------------------------
STATION: JCLSETUP STATION ID= 39 START TIME = /. END TIME= /. ROUTE STATION ID= TIMEZONE ADJUST=
DESCRIPTION= SETUP OF JCL STATION
TITLE = SETUP OF JCL STATION
STATION RECORD
------------------------------
STATION: CPU STATION ID= 4 START TIME = /. END TIME= /. ROUTE STATION ID= TIMEZONE ADJUST=
DESCRIPTION= CPU STATION
TITLE = CPU STATION
STATION RECORD
------------------------------
STATION: PRINTING STATION ID= 6 START TIME = /. END TIME= /. ROUTE STATION ID= TIMEZONE ADJUST=
DESCRIPTION= PRINTING STATION
TITLE = PRINTING STATION
STATION RECORD
------------------------------
STATION: OUTPTVER STATION ID= 65 START TIME = /. END TIME= /. ROUTE STATION ID= TIMEZONE ADJUST=
DESCRIPTION= OUTPUT VERIFICATION STATION
TITLE = OUTPUT VERIFICATION STATION
STATION RECORD
------------------------------
STATION: OUTPTDIS STATION ID= 7 START TIME = /. END TIME= /. ROUTE STATION ID= TIMEZONE ADJUST=
DESCRIPTION= OUTPUT DISTRIBUTION STATION
TITLE = OUTPUT DISTRIBUTION STATION
5-18 Unicenter CA-Scheduler Reference Guide, Part 2

5.3 Display and Analysis Reports
5.3.6 List Userid
The List Userid report lists the records and values that have been defined for
one userid, a group of userids, or all userids. The sample following shows the
userids specified.
COMPUTER ASSOCIATES JOB SCHEDULING SYSTEM UTILITY LOG CAJUTIL PAGE 1
CA-SCHEDULER 7.3 39SH73 3 SEP 23 18.24.59
LIST
USERID NAME=ANNE
USERID RECORD
------------------------------
USERID: ANNE READ PASSWORD= WRITE PASSWORD= CLASS= M
DESCRIPTION = SHIFT PRODUCTION ANALIST
LIST
USERID NAME=MARK
USERID RECORD
------------------------------
USERID: MARK READ PASSWORD= WRITE PASSWORD= CLASS= M
DESCRIPTION = SHIFT PRODUCTION ANALIST
LIST
USERID NAME=RON
USERID RECORD
------------------------------
USERID: RON READ PASSWORD= WRITE PASSWORD= CLASS= M
DESCRIPTION = PRODUCTION SUPERVISOR
LIST
USERID NAME=JEFF
USERID RECORD
------------------------------
USERID: JEFF READ PASSWORD= WRITE PASSWORD= CLASS= M
DESCRIPTION = PRODUCTION MANAGER
To produce the basic report, submit the following JCL with your job statement:
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
LIST USERID NAME=userid
userid
/
/&
Chapter 5. Reports 5-19

5.3 Display and Analysis Reports
5.3.6.1 Usage Notes
5.3.6.2 Example 1
5.3.6.3 Example 2
Use the List Userid report to list the records and values that have been defined
for userids. If any parameters were left to default values when the userid was
defined, those default parameters will not be printed.
To list a group of userids that begin with the same characters, specify the
userid name generically. To do this, code the common characters followed by
an asterisk.
Optionally, you can list the userid read or write passwords. To list the userids
read passwords, code the master userid read password. To list the write
passwords, code the master userid write password.
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
LIST USERID NAME=ACCTG,
/
/&
READPASS=RMASTER
userid
master read password
The preceding example lists the userid record that was defined as ACCTG. The
master read password is included so that the output will show the ACCTG
userid's read password.
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
LIST USERID NAME=,
READPASS=RMASTER,
/
/&
WRITPASS=WMASTER
generic userid
master read password
master write password
The preceding example will list all userid records in the database in
alphabetical order. The master read password and master write password are
specified so that the output will show both the read and write passwords
defined for each userid.
5-20 Unicenter CA-Scheduler Reference Guide, Part 2

5.4 Batch Versions of Online Reports
5.4 Batch Versions of Online Reports
5.4.1 Abended Job Schedule
This topic gives samples of each batch version of an online report and gives
sample JCL to produce the report. In addition, each of the report fields are
explained.
The Abended Job Schedule report lists all Unicenter CA-Scheduler-controlled
jobs that abended on the current AUTOSCAN DATE starting at AUTOTIM,
unless you use the optional keywords described following. Up to the last seven
executions of a job that abended will be reported on. For each job that
abended, the date on which the job and schedule were planned to run is
shown, along with the actual date, actual start time, and abnormal end time of
the job. Jobs on a report for a day other than today will be listed up to
AUTOTIM.
COMPUTER ASSOCIATES ABENDED JOB SCHEDULE ABENDED PAGE 1
CA-SCHEDULER 7.3 39SH73 3 SEP 23 15.32.11
PLANNED START DATE: 3 SEP 23
-------P L A N N E D------ --------A C T U A L-------
SCHEDULE ----JOB---- START END ELAPSED START END ELAPSED TERM
NAME NAME ST TIME TIME TIME TIME TIME TIME CODE
-------- -------- -- -------- -------- -------- -------- -------- -------- -----
DEMO CAJDEM3 4 /. /. /. /12.43 /12.43 /. X'2'
DEMOTRCK CAJINT4 4 /. /. /. /22.54 /22.59 /.5 X'23'
SCHD1 JOB11 4 /. /. /. /16.25 /17.37 /1.2 X'FF'
SCHD1 JOB13 4 /. /. /. /9.1 /9.14 /.4 X'24'
SCHD2 JOB21 4 /. /. /. /13.1 /13.8 /.7 X'2'
SCHD2 JOB22 4 /. /. /. /13.8 /13.1 /.2 X'2'
SCHD2 JOB23 4 /. /. /. /13.11 /13.15 /.4 X'2'
SCHD3 JOB33 4 /. /. /. /14.45 /14.48 /.3 X'2'
To
Limit the report to one
job or a group of jobs whose names
begin with the same characters
schedule or a group of schedules whose
names begin with the same characters
Report on
a date other than today
more than one day
jobs that were scheduled for a given
date regardless of when they abended
Start the report at a time other than
AUTOTIM
Specify
JOB=jname|jname*
SCHEDULE=sname|sname*
FROMDATE=mmddyy|ddmmyy
FOR=nn
SDATE=mmddyy|ddmmyy
FROMTIME=hhmm
Chapter 5. Reports 5-21

5.4 Batch Versions of Online Reports
5.4.1.1 Example 1
JCL that produces the Abended Job Schedule report requires the inclusion of a
work file. A generic version of this work file is contained on the installation
tape. The file's name is Z.CAWORK1. Tailor this file to your installation's
needs and ensure that it is accessible before running the JCL that produces the
report. To produce this report, submit the following JCL with your job
statement:
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT ABEND
/
/&
The following information is included on the Abended Job Schedule report:
PLANNED START DATE
SCHEDULE NAME
JOB NAME
JOB ST
PLANNED START TIME
PLANNED END TIME
PLANNED ELAPSED TIME
ACTUAL START TIME
ACTUAL END TIME
ACTUAL ELAPSED TIME
TERM CODE
The date the job was selected to run.
The schedule the abended job was assigned
to.
The jobs that abended during the period
reported on.
The stations where these jobs were scheduled.
EARLIEST START TIME, if one was defined
for the job.
COMPLETION DEADLINE TIME, if one was
defined for the job.
AVERAGE TIME, if one was defined for the
job.
The time the job actually started.
The time the job actually ended.
The time it actually took to process the job.
The completion code.
Note: The time fields are of the format dd/hh.mm where dd is the number of
days from the planned start date, hh is the hour, and mm is the
minute.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT ABEND FROMDATE=1153
/
/&
5-22 Unicenter CA-Scheduler Reference Guide, Part 2

5.4 Batch Versions of Online Reports
5.4.1.2 Example 2
The preceding JCL will produce a report for any job that abended on
10/15/03.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT ABEND SDATE=1153
/
/&
5.4.2 Closed Data Set Report
The preceding JCL will produce a report for any job that was scheduled to run
on 10/15/03 and abended on the same day or later.
The Closed Data Set report lists the output data sets used by all Unicenter
CA-Scheduler-controlled jobs that ran today, starting at AUTOTIM.
Chapter 5. Reports 5-23

5.4 Batch Versions of Online Reports
COMPUTER ASSOCIATES CLOSED DATA SET REPORT DATASET PAGE 1
CA-SCHEDULER 7.3 39SH73 14 SEP 23 15.35.45
CLOSED DATA SET DATE: 14 SEP 23
SCHEDULE JOB LAST TIME BLOCK RECORD RECORD DEVICE
NAME NAME DATA SET NAME CLOSED CLOSED SIZE SIZE FORMAT TYPE
-------- -------- -------------------------------------------- -------- -------- ------- ------- ------ ------
SCHD1 JOB13 JOB13.FILE 9/14/3 12.36.4 72 72 F DISK
SCHD2 JOB23 JOB23.FILE 9/14/3 12.38.1 72 72 F DISK
DEMO CAJDEM4 CAI.SCHD.HISTORY 9/14/3 14.3.42 TAPE
DEMOHIST CAJINH1 EARLOBJ.FILE 9/14/3 14.5.28 3,2 8 F DISK
DEMOHIST CAJINH1 WORK1.FILE 9/14/3 14.5.39 DISK
DEMOHIST CAJINM1 IJSYS1.FILE 9/14/3 14.6.25 248 248 F DISK
DEMOHIST CAJINM1 IJSYS5.FILE 9/14/3 14.6.28 3,224 248 F DISK
DEMOHIST CAJINM1 EARLOBJ.FILE 9/14/3 14.6.4 3,2 8 F DISK
DEMOHIST CAJINM1 WORK1.FILE 9/14/3 14.9.49 DISK
DEMOHIST CAJINM2 IJSYS1.FILE 9/14/3 14.11.38 248 248 F DISK
DEMOHIST CAJINM2 IJSYS5.FILE 9/14/3 14.11.42 3,224 248 F DISK
DEMOHIST CAJINM2 EARLOBJ.FILE 9/14/3 14.12. 3,2 8 F DISK
DEMOHIST CAJINM2 WORK1.FILE 9/14/3 14.14.54 DISK
DEMOHIST CAJINM3 EARLOBJ.FILE 9/14/3 14.15.21 3,2 8 F DISK
DEMOHIST CAJINM3 WORK1.FILE 9/14/3 14.19.16 DISK
DEMOHIST CAJINH2 EARLOBJ.FILE 9/14/3 14.22.19 3,2 8 F DISK
DEMOHIST CAJINH2 WORK1.FILE 9/14/3 14.22.28 DISK
DEMOHIST CAJINH3 EARLOBJ.FILE 9/14/3 14.23.3 3,2 8 F DISK
DEMOHIST CAJINH3 WORK1.FILE 9/14/3 14.23.13 DISK
DEMOHIST CAJINH4 EARLOBJ.FILE 9/14/3 14.23.53 3,2 8 F DISK
DEMOHIST CAJINH4 WORK1.FILE 9/14/3 14.24.1 DISK
DEMOHIST CAJINH5 EARLOBJ.FILE 9/14/3 14.24.48 3,2 8 F DISK
DEMOHIST CAJINH5 WORK1.FILE 9/14/3 14.24.58 DISK
DEMOHIST CAJINH6 EARLOBJ.FILE 9/14/3 14.25.58 3,2 8 F DISK
DEMOHIST CAJINH6 WORK1.FILE 9/14/3 14.26.15 DISK
DEMOHIST CAJINH7 EARLOBJ.FILE 9/14/3 14.28. 3,2 8 F DISK
DEMOHIST CAJINH7 WORK1.FILE 9/14/3 14.28.36 DISK
DEMOTRCK CAJIND1 EARLOBJ.FILE 9/14/3 14.29.21 3,2 8 F DISK
DEMOTRCK CAJIND1 WORK1.FILE 9/14/3 14.29.29 DISK
DEMOTRCK CAJIND2 EARLOBJ.FILE 9/14/3 14.31.21 3,2 8 F DISK
DEMOTRCK CAJIND2 WORK1.FILE 9/14/3 14.31.27 DISK
DEMOTRCK CAJING1 EARLOBJ.FILE 9/14/3 14.34.42 3,2 8 F DISK
DEMOTRCK CAJING1 WORK1.FILE 9/14/3 14.34.53 DISK
DEMOTRCK CAJING2 EARLOBJ.FILE 9/14/3 14.35.36 3,2 8 F DISK
DEMOTRCK CAJING2 WORK1.FILE 9/14/3 14.35.45 DISK
DEMOTRCK CAJINS1 EARLOBJ.FILE 9/14/3 14.37.51 3,2 8 F DISK
DEMOTRCK CAJINS1 WORK1.FILE 9/14/3 14.37.58 DISK
DEMOTRCK CAJINS6 EARLOBJ.FILE 9/14/3 14.42.19 3,2 8 F DISK
DEMOTRCK CAJINTD1 IJSYS1.FILE 9/14/3 14.44.41 248 248 F DISK
DEMOTRCK CAJINTD1 IJSYS4.FILE 9/14/3 14.44.44 248 248 F DISK
DEMOTRCK CAJINTD1 IJSYS5.FILE 9/14/3 14.44.48 3,224 248 F DISK
DEMOTRCK CAJINTD1 EARLOBJ.FILE 9/14/3 14.45.13 3,2 8 F DISK
DEMOTRCK CAJINTD1 WORK1.FILE 9/14/3 14.45.55 DISK
DEMOTRCK CAJINT1 EARLOBJ.FILE 9/14/3 14.48.23 3,2 8 F DISK
Use these optional keywords to limit the report to selected information:
To
Limit the report to one
job or a group of jobs whose names begin
with the same characters
schedule or a group of schedules whose
names begin with the same characters
Report on
a date other than today
more than one day
Specify
JOB=jname]jname*
SCHEDULE=sname]sname*
FROMDATE=mmddyy|ddmmyy
FOR=nn
5-24 Unicenter CA-Scheduler Reference Guide, Part 2

5.4 Batch Versions of Online Reports
To
Start the report at a time other than AUTOTIM
Specify
FROMTIME=hhmm
JCL that produces this report requires the inclusion of a work file. A generic
version of this work file is contained on the installation tape. The file's name is
Z.CAWORK1. Tailor this file to your installation's needs and ensure that it is
accessible before running the JCL that produces the report. To produce this
report, submit the following JCL with your job statement:
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT DATASET
/
/&
The following information is included on the Closed Data Set report:
CLOSED DATA SET DATE
SCHEDULE NAME
JOB NAME
DATA SET NAME
LAST CLOSED
TIME CLOSED
BLOCK SIZE
RECORD SIZE
RECORD FORMAT
DEVICE TYPE
5.4.3 Completed Job Schedule
FROMDATE, if specified, or else today's date.
The schedules processed during the period
reported on.
The jobs processed during the period reported
on.
The data sets used by these jobs.
The date the data set was closed.
The time the data set was closed.
The data set's block size.
The data set's logical record size.
The data set's record format.
DISK or TAPE.
Note: Data set information collection is determined by the DSN= option in
the CAIJGEN macro.
The Completed Job Schedule report lists all Unicenter CA-Scheduler-controlled
jobs that completed on the current AUTOSCAN DATE starting at AUTOTIM,
unless you use the optional keywords described following. Up to the last seven
executions of a job that completed will be reported on. For each job that
completed, the date on which the job and schedule were planned to run is
shown, along with the actual date, actual start time, and end time of the job.
Jobs on a report for a day other than today will be listed up to AUTOTIM.
Chapter 5. Reports 5-25

5.4 Batch Versions of Online Reports
COMPUTER ASSOCIATES COMPLETED JOB SCHEDULE COMPLETE PAGE 1
CA-SCHEDULER 7.3 39SH73
3 SEP 23 15.37.6
PLANNED START DATE: 2 SEP 23
-------P L A N N E D------ --------A C T U A L-------
SCHEDULE ----JOB---- START END ELAPSED START END ELAPSED COMP
NAME NAME ST TIME TIME TIME TIME TIME TIME CODE
-------- -------- -- -------- -------- -------- -------- -------- -------- -----
SCHD1 JOB13 4 1/9. /. /. 1/12.36 1/12.36 /. X'1'
SCHD2 JOB23 4 1/9.15 /. /. 1/12.36 1/12.38 /.1 X'1'
DEMO
DEMO
DEMO
DEMO
DEMO
CAJDEM1 4 /. /. /. /12.42 /12.42 /. X'1'
CAJDEM2 4 /. /. /. /12.42 /12.42 /. X'1'
CAJDEM3 39 /. /. /. /12.43 /12.43 /.
CAJDEM3 4 /. /. /. /14.2 /14.2 /. X'1'
CAJDEM4 4 /. /. /. /14.2 /14.3 /. X'1'
DEMOHIST CAJINH1 4 /. /. /. /14.5 /14.5 /. X'1'
DEMOHIST CAJINM1 4 /. /. /. /14.5 /14.1 /.4 X'1'
DEMOHIST CAJINM2 4 /. /. /. /14.1 /14.15 /.4 X'1'
DEMOHIST CAJINM3 4 /. /. /. /14.15 /14.19 /.4 X'1'
DEMOHIST CAJINH2 4 /. /. /. /14.2 /14.22 /.2 X'1'
DEMOHIST CAJINH3 4 /. /. /. /14.22 /14.23 /. X'1'
DEMOHIST CAJINH4 4 /. /. /. /14.23 /14.24 /. X'1'
DEMOHIST CAJINH5 4 /. /. /. /14.24 /14.25 /. X'1'
DEMOHIST CAJINH6 4 /. /. /. /14.25 /14.27 /.2 X'1'
DEMOHIST CAJINH7 4 /. /. /. /14.27 /14.28 /.1 X'1'
DEMOTRCK CAJIND1 4 /. /. /. /14.28 /14.29 /. X'1'
DEMOTRCK CAJIND2 4 /. /. /. /14.29 /14.31 /.1 X'1'
DEMOTRCK CAJING1 4 /. /. /. /14.32 /14.35 /.2 X'1'
DEMOTRCK CAJING2 4 /. /. /. /14.35 /14.37 /.2 X'1'
DEMOTRCK CAJINS1 4 /. /. /. /14.37 /14.39 /.2 X'1'
DEMOTRCK CAJINS6 4 /. /. /. /14.39 /14.42 /.2 X'1'
DEMOTRCK CAJINTD1 4 /. /. /. /14.42 /14.47 /.4 X'1'
DEMOTRCK CAJINT1 4 /. /. /. /14.47 /14.49 /.1 X'1'
DEMOTRCK CAJINT2 4 /. /. /. /14.49 /14.54 /.5 X'1'
DEMOTRCK CAJINT3 4 /. /. /. /14.54 /14.59 /.4 X'1'
DEMOTRCK CAJINT4 4 /. /. /. /14.59 /15.1 /.2 X'1'
DEMOTRCK CAJINT6 4 /. /. /. /15.1 /15.4 /.2 X'1'
DEMOTRCK CAJINT7 4 /. /. /. /15.5 /15.8 /.3 X'1'
Use the following optional keywords to limit the report to selected
information:
To
Limit the report to one
job or a group of jobs whose names
begin with the same characters
schedule or a group of schedules whose
names begin with the same characters
Specify
JOB=jname]jname*
SCHEDULE=sname]sname*
station
Report on
a date other than today
more than one day
jobs that were scheduled for a given
date regardless of when they abended
STATION=nn
FROMDATE=mmddyy|ddmmyy
FOR=nn
SDATE=mmddyy|ddmmyy
5-26 Unicenter CA-Scheduler Reference Guide, Part 2

5.4 Batch Versions of Online Reports
To
Start the report later than AUTOTIM
Specify
FROMTIME=hhmm
JCL that produces this report requires the inclusion of a work file. A generic
version of this work file is contained on the installation tape. The file's name is
Z.CAWORK1. Tailor this file to your installation's needs and ensure that it is
accessible before running the JCL that produces the report. To produce the
Completed Job Schedule report, submit the following JCL with your job
statement:
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT COMPLETE
/
/&
The following information is included on the Completed Job Schedule report:
PLANNED START DATE
SCHEDULE NAME
JOB NAME
JOB ST
PLANNED START TIME
PLANNED END TIME
PLANNED ELAPSED TIME
ACTUAL START TIME
ACTUAL END TIME
ACTUAL ELAPSED TIME
TERM CODE
The date the job was selected to run.
The schedule the completed job was assigned
to.
The jobs that completed during the period
reported on.
The station where these jobs were scheduled.
The EARLIEST START TIME, if one was
defined for the job.
The COMPLETION DEADLINE TIME, if one
was defined.
The AVERAGE TIME, if one was defined for
the job.
The time the job actually started.
The time the job actually ended.
The time it actually took to process the job.
The completion code.
5.4.3.1 Example 1
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT COMPLETE,FROMDATE=213,FOR=28
/
/&
Chapter 5. Reports 5-27

5.4 Batch Versions of Online Reports
5.4.3.2 Example 2
5.4.3.3 Example 3
5.4.3.4 Example 4
5.4.3.5 Example 5
The preceding JCL will list all the jobs that completed during the month of
February.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT COMPLETE,FROMTIME=1,JOB=PROD
/
/&
The preceding JCL will list the jobs starting with 'PROD' that completed today
from 1:00 a.m.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT COMPLETE,SCHEDULE=DAILY1
/
/&
The preceding JCL will list all the jobs in schedule 'DAILY1' that completed
today.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT COMPLETE,STATION=36
/
/&
The preceding JCL will list all the jobs for station 36 that completed today. In
this example, station 36 is a pre-CPU station.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT COMPLETE FROMDATE=1153
/
/&
The preceding JCL will produce a report for any job that completed on
10/15/03.
5-28 Unicenter CA-Scheduler Reference Guide, Part 2

5.4 Batch Versions of Online Reports
5.4.3.6 Example 6
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT COMPLETE SDATE=1153
/
/&
5.4.4 Date Translation Report
The preceding JCL will produce a report for any job that was scheduled to run
on 10/15/03 and completed on the same date or later.
The Date Translation report shows which Gregorian calendar dates, workdays,
holidays, and accounting periods are true for a specific date and datetable
combination. We recommend that you run this report to verify that the
selection criteria keywords you use in your schedule and job criteria
definitions are correct. In some cases, this report can be interpreted as showing
which selection criteria keywords are false. In either case, the values on this
report are always calculated based upon the combination of Gregorian
calendar conditions, a specific datetable definition, and the actual date the
report is run. When schedules and jobs do not use calendars for selection, this
report will show which selection criteria keywords they can use on a specific
day to be selected.
Chapter 5. Reports 5-29

5.4 Batch Versions of Online Reports
COMPUTER ASSOCIATES DATE TRANSLATION REPORT DATETRAN PAGE 1
CA-SCHEDULER 7.3 39SHESA
4 SEP 23
15.53.49
SIMULATION DATE 8 SEP 23
JULIAN DATE=3251
GREGORIAN DATE=9/8/3
TABLE NAME=DATETAB
DAY OF WEEK=FRI WEEK-DAY=YES WEEK-END=NO MWF=YES TT=NO NTH DAY OF MONTH=FRI2 FRI-4 NEGATIVE DAY OF MONTH=DOM-23
WEEK OF MONTH=2ND-WEEK WEEK OF YEAR=WOY36 WOY-18 DAYS IN MONTH=3 LEAP-YEAR=NO
DAY1OF2=NO DAY2OF2=YES
DAY1OF3=NO DAY2OF3=NO DAY3OF3=YES
DAY1OF4=NO DAY2OF4=YES DAY3OF4=NO DAY4OF4=NO
DAY1OF5=NO DAY2OF5=NO DAY3OF5=NO DAY4OF5=NO DAY5OF5=YES
DAY1OF6=NO DAY2OF6=NO DAY3OF6=NO DAY4OF6=NO DAY5OF6=NO DAY6OF6=YES
WEEK1OF2=YES WEEK2OF2=NO
WEEK1OF3=YES WEEK2OF3=NO WEEK3OF3=NO
WEEK1OF4=YES WEEK2OF4=NO WEEK3OF4=NO WEEK4OF4=NO
WEEK1OF5=NO WEEK2OF5=NO WEEK3OF5=YES WEEK4OF5=NO WEEK5OF5=NO
WEEK1OF6=YES WEEK2OF6=NO WEEK3OF6=NO WEEK4OF6=NO WEEK5OF6=NO WEEK6OF6=NO
WORK-DAY=YES WORK DAY OF WEEK=WDOW5 WDOW-1 WORK DAY OF MONTH=WDOM6 WDOM-16 WORK DAY OF YEAR=18 -81
WORK WEEK OF MONTH=WWOM2 WWOM-4
WORK WEEK OF YEAR=WWOY36 WWOY-17
RD1=+5 -16 RD2=+5 -16 RD3=+5 -17 RD4=+4 -18 RD5=+3 -19 RD6=+2 -2 RD7=+1 -21 RD8=+ -
RD9=+22 -1 RD1=+21 -1 RD11=+2 -1 RD12=+2 -2 RD13=+2 -3 RD14=+19 -4 RD15=+18 -5 RD16=+17 -6
RD17=+16 -6 RD18=+15 -6 RD19=+15 -7 RD2=+15 -8 RD21=+14 -9 RD22=+13 -1 RD23=+12 -11 RD24=+11 -11
RD25=+1 -11 RD26=+1 -12 RD27=+1 -13 RD28=+9 -14 RD29=+8 -15 RD3=+7 -16 RD31=+6
HDAY=NO
HDAY-1=NO HDAY-2=NO HDAY-3=NO HDAY-4=NO HDAY-5=YES HDAY-6=YES HDAY-7=NO
HDAY1 =YES HDAY2 =YES HDAY3 =NO HDAY4 =NO HDAY5 =NO HDAY6 =NO HDAY7 =NO HDAY8 =YES HDAY9 =YES HDAY1=NO
HDAY11=NO HDAY12=NO HDAY13=NO HDAY14=NO HDAY15=YES HDAY16=YES HDAY17=NO HDAY18=NO HDAY19=NO HDAY2=NO
HDAY21=NO HDAY22=YES HDAY23=YES HDAY24=NO HDAY25=NO HDAY26=NO HDAY27=NO HDAY28=NO HDAY29=YES HDAY3=YES
HDAY31=NO
A-ACCOUNTING DAY=YES DAY OF MONTH=ADOM6 ADOM-16 DAY OF YEAR=18 -81 WEEK OF MONTH=AWOM2 AWOM-4 MONTH OF YEAR=AMOY9 AMOY-4
X-ACCOUNTING DAY=YES DAY OF MONTH=XDOM6 XDOM-16 DAY OF YEAR=18 -81 WEEK OF MONTH=XWOM2 XWOM-4 MONTH OF YEAR=XMOY9 XMOY-4
The Date Translation report will also display valid accounting day conditions
based upon the seven-byte datetable name. This means that all defined
variations (prefixes) of the named datetable will be analyzed at the end of the
report.
JCL that produces this report requires the inclusion of a work file. A generic
version of this work file is contained on the installation tape. The file's name is
Z.CAWORK1. Tailor this file to your installation's needs and ensure that it is
accessible before running the JCL that produces the report. To produce the
report, submit the following JCL with your job statement :
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT DATETRAN
/
/&
All datetables are translated for today only unless you use these optional
keywords to limit the report to selected information:
5-30 Unicenter CA-Scheduler Reference Guide, Part 2

5.4 Batch Versions of Online Reports
To
Limit the report to
one specific datetable
the datetable referenced by this schedule
the datetable referenced by the schedule
this job is assigned to
Report on
a date other than today
more than one day
Start the report at a time other than AUTOTIM
Specify
TABLE-tablename
SCHEDULE=sname
JOB=jname
FROMDATE=mmddyy|ddmmyy
FOR=nn
FROMTIME=hhmm
5.4.5 File Status Report
A Date Translation Report may also be produced while running Unicenter
CA-Scheduler in simulation mode. See the topic Simulation Reports in this
chapter for explanations of the information found on this report.
The File Status report shows the physical DASD status for the named file. The
information on the left side of the report is static and does not change unless
the file is reformatted. You can request information pertaining to the job
master database, tracking file, staging library, documentation library, or
Unicenter CA-Driver procedure library.
F I L E S T A T U S R E P O R T
DDNAME :CAIJMST FILE ID :SCHEDULER.MASTER
VOLUME SERIAL :VOL12C SPACE ALLOCATED :7512 JOBS
DASD TYPE :338 SPACE AVAILABLE :3512 JOBS
CISIZE :6144 REORG RECOMENDED:NO
LOWER EXTENT LIMIT:185 SHARED FILE :YES
UPPER EXTENT LIMIT:23 14
CROSS-CPU ENQUED:NO
FORMATTED BY : LAST ACCESSED BY:
JOB NAME :RESTORE JOB NAME :S71E
STEP NAME :FORM STEP NAME :S71E
PROC NAME : PROC NAME :
PHYSICAL CPUID :FF22389381 PHYSICAL CPUID:FF22389381
DATE :4 OCT 23 DATE :6 NOV 23
TIME : 6.41.12 TIME :11.53.44
There are no keywords associated with this report.
To produce a file status report for the job master database, submit the
following JCL with your job statement:
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT CAIJMST
/
/&
To produce a file status report for the tracking file, submit the following JCL
with your job statement:
Chapter 5. Reports 5-31

5.4 Batch Versions of Online Reports
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT CAIJTRK
/
/&
To produce a file status report for the staging library, submit the following JCL
with your job statement:
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT CAIJSTG
/
/&
To produce a file status report for the documentation library, submit the
following JCL with your job statement:
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT CAIJDCM
/
/&
To produce a file status report for the Unicenter CA-Driver procedure library,
submit the following JCL with your job statement:
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT CAIJDRV
/
/&
The following information is included on the File Status Report:
DDNAME
VOLUME SERIAL
DASD TYPE
CISIZE
LOWER EXTENT LIMIT
UPPER EXTENT LIMIT
FORMATTED BY
JOB NAME
STEP NAME
PROC NAME
PHYSICAL CPUID
DATE
TIME
The ddname used to allocate the file as specified in
the CAIJGEN macro generation options.
The volume serial where the file actually resides.
The actual DASD type where the file resides.
The control interval size used to format the file.
The starting disk address for the file in cchhr
format.
The ending disk address for the file in cchhr
format.
Information about the job that initially formatted
the file.
The job name used to format the file.
The program used to format data set.
The PROC name used to format the file.
The physical CPU ID used to format the file.
The date that the file was formatted.
The time that the file was formatted.
5-32 Unicenter CA-Scheduler Reference Guide, Part 2

5.4 Batch Versions of Online Reports
Most of the information on the right side of the report is dynamic and shows
the current status of the file:
FILE ID
SPACE ALLOCATED
SPACE AVAILABLE
REORG RECOMENDED
SHARED FILE
CROSS-CPU ENQUED
The name used on the ID=id keyword of the
FORMAT command.
The amount of DASD space allocated to the file in
terms of the number of jobs; that is, the total
number of jobs that can be defined on the space
allocated. If you expect to have more jobs, you
should increase the amount of disk space allocated
to the file.
The amount of contiguous DASD space available in
terms of the number of jobs. As more jobs are
added, this number will decrease. If jobs are
deleted, it may not accurately reflect the available
space. When this number approaches zero, a
REORG will be recommended.
Recommends whether to perform a REORG on the
file. If after a REORG, the amount of space
available does not increase, you should probably
allocate more space to the file.
Indicates whether the file is shared among multiple
CPUs.
Indicates whether the file is currently enqueued by
one CPU in a multi-CPU environment. If so, the
LAST ACCESSED BY information shows the CPU
and the job or user that is currently holding the
enqueue. If that job or user no longer exists on that
CPU, (such as might happen after a system crash)
you should perform a FORCEDEQ on the file to
clear the enqueue.
LAST ACCESSED BY
JOB NAME
STEP NAME
PROC NAME
PHYSICAL CPUID
DATE
TIME
The job or user that last
accessed the file.
The job name used.
The program or CICS
TASKID
The PROC name used.
The physical CPU ID
where the job is running.
The date that the job
accessed the file.
The time that the job
accessed the file.
Chapter 5. Reports 5-33

5.4 Batch Versions of Online Reports
5.4.6 Job Average Report
The Job Average report lists the average time and I/O information for the last
seven successful executions of all Unicenter CA-Scheduler controlled jobs. It is
a high performance report since no sorting is performed. Jobs are listed in
alphabetical order. You may limit the report to one job or a group of jobs.
COMPUTER ASSOCIATES JOB AVERAGE REPORT PAGE 1
JOB AVG AVG AVG AVG AVG
NAME JNO ST ELAPSED CPU TIME DISK I/O TAPE I/O OTHER I/O
CICSACC 1 39 /.7 /. 13 44
CICSACC 1 4 /9.14 /.5 2763
CICSASAP 1 4 /.5 /.4 16
CICSASAP 2 4 /.4 /.4 13
CICSASAP 3 4 /.5 /.4 16
CICSASAP 4 4 /.4 /.4 13
CICSBAX 1 39 /.1 /. 47
CICSBAX 1 4 /14.4 /.34 3278
CICSBAX 2 4 /6.59 /.6 31783
CICSBAXA 1 39 /.54 /.
CICSBAXA 1 4 /. /. 67
CICSBAXB 1 4 /.19 /. 679 433
To
Limit the report to one job or a group of jobs
Specify
Name=jname|generic jname
JCL that produces this report requires the inclusion of a work file. A generic
version of this work file is contained on the installation tape. The file's name is
Z.CAWORK1. Tailor this file to your installation's needs and ensure that it is
accessible before running the JCL that produces the report. To produce a
report listing the average time and I/O information for all Unicenter
CA-Scheduler controlled jobs, submit the following JCL with your job
statement:
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT JOBAVG
/
/&
The following information is included on the Job Average Report:
JOB NAME
JNO
ST
AVG ELAPSED
The job name.
The Unicenter CA-Scheduler job number.
The station ID.
The average elapsed time in DD/hh.mm format.
AVG CPU TIME The average CPU time in DD/hh.mm format.
5-34 Unicenter CA-Scheduler Reference Guide, Part 2

5.4 Batch Versions of Online Reports
AVG DISK I/O The average number of EXCPs on DASD devices.
AVG TAPE I/O The average number of EXCPs on TAPE devices.
AVG OTHER I/O The average number of EXCPs on other devices.
5.4.6.1 Example 1
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT JOBAVG NAME=JOB1
/
/&
5.4.6.2 Example 2
The preceding JCL will list the average time and I/O information for JOB1.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT JOBAVG NAME=JOB
/
/&
5.4.7 Job History Report
The preceding JCL will list the average time and I/O information for all jobs
that begin with the letters JOB.
The Job History report lists the last seven executions for all Unicenter
CA-Scheduler-controlled jobs. It is a high performance report since no sorting
is performed. Jobs are listed in alphabetical order. You may limit the report to
one job or a group of jobs.
Chapter 5. Reports 5-35

5.4 Batch Versions of Online Reports
COMPUTER ASSOCIATES JOB HISTORY REPORT PAGE 1
JOB SCHEDULE SCHEDULED START START END END POWER COMP.
NAME JNO ST NAME RC DATE TIME DATE TIME DATE TIME JOBNO CODE
CAJDEM1 1 4 DEMO 84 2/24 1.23 2/24 1.23 2/24 1.23 1 X'1'
DEMO 88 3/3 12.41 3/3 12.42 3/3 12.42 742 X'1'
CAJDEM2 1 4 DEMO 1 2/22 13.42 PENDING
DEMO 1 2/24 1.23 2/24 1.24 2/24 1.24 11 X'1'
DEMO 1 3/3 12.41 3/3 12.42 3/3 12.42 745 X'1'
CAJDEM3 1 39 DEMO 84 2/22 13.42 PENDING
DEMO 88 3/3 12.41 3/3 12.43 3/3 12.43
CAJDEM3 1 4 DEMO 1 2/22 13.42 PENDING
DEMO 1 3/3 12.41 3/3 12.43 3/3 12.43 747 X'2'
DEMO 1 3/3 12.41 3/3 14.2 3/3 14.2 826 X'1'
CAJDEM4 1 4 DEMO 1 2/22 13.42 PENDING
DEMO 1 3/3 12.41 3/3 14.2 3/3 14.3 827 X'1'
CAJIND1 1 4 DEMOTRCK 1 2/22 13.42
PENDING
DEMOTRCK 1 2/24 1.23 2/24 11.22 2/24 11.23 33 X'1'
CAJIND2 1 4 DEMOTRCK 1 2/22 13.42
PENDING
DEMOTRCK 1 2/24 1.23 2/24 11.23 2/24 11.25 34 X'1'
CAJING1 1 4 DEMOTRCK 1 2/22 13.42
PENDING
DEMOTRCK 1 2/24 1.23 2/24 11.25 2/24 11.27 35 X'1'
CAJING2 1 4 DEMOTRCK 1 2/22 13.42
PENDING
DEMOTRCK 1 2/24 1.23 2/24 11.27 2/24 11.29 36 X'1'
CAJINH1 1 4 DEMOHIST 1 2/22 13.42
PENDING
DEMOHIST 1 2/24 1.23 2/24 1.47 2/24 1.5 21 X'1'
CAJINH2 1 4 DEMOHIST 1 2/22 13.42
PENDING
DEMOHIST 1 2/24 1.23 2/24 11.1 2/24 11.13 27 X'1'
CAJUCMD1 1 4 CAJUCMD 1 3/1 17.34
CAJUCMD 1 3/1 17.44
118
CAJUCMD 1 3/2 15.56 3/2 15.57 3/2 15.58 51 X'1'
CAJUCMD2 1 4 CAJUCMD 1 3/1 17.34
PENDING
CAJUCMD 1 3/1 17.44
PENDING
JOB11 1 39 SCHD1 1 3/1 17.34 3/1 17.34
SCHD1 1 3/2 14.25 3/2 14.25 3/2 14.26
SCHD1 1 3/2 15.56 3/2 15.56 3/2 15.58
JOB11 1 4 SCHD1 1 3/1 17.47 PENDING
SCHD1 1 3/2 14.25 3/2 14.27 3/2 14.27 37 X'FF'
SCHD1 1 3/2 15.56 3/2 15.58 3/2 15.59 52 X'1'
JOB12 1 2 SCHD1 1 3/1 17.34 3/1 17.34
SCHD1 1 3/2 14.25 3/2 14.25 3/2 14.26
SCHD1 1 3/2 15.56 3/2 15.56 3/2 15.58
JOB12 1 4 SCHD1 1 3/1 17.34 PENDING
SCHD1 1 3/2 15.56 3/2 16.3 3/2 16.5 59 X'1'
JOB12 1 6 SCHD1 1 3/1 17.34 PENDING
SCHD1 1 3/2 15.56 3/2 16.5
JOB13 1 4 SCHD1 1 3/1 17.44 PENDING
SCHD1 1 3/2 15.56 3/3 12.36 3/3 12.36 735 X'1'
JOB13 1 6 SCHD1 1 3/1 17.34 PENDING
JOB21 1 4 SCHD2 1 3/1 17.44 PENDING
SCHD2 1 3/2 14.25
SCHD2 1 3/2 15.56 3/2 15.59 3/2 16.1 54 X'1'
JOB22 1 4 SCHD2 1 2/24 16.28 PENDING
SCHD2 1 2/24 16.44 PENDING
SCHD2 1 2/24 16.52 2/24 16.55 2/24 16.56 136 X'1'
SCHD2 1 3/2 14.25 PENDING
SCHD2 1 3/2 15.56 3/2 16.5 3/2 16.7 61 X'1'
JOB23 1 4 SCHD2 1 3/1 17.44 PENDING
SCHD2 1 3/1 17.47 PENDING
SCHD2 1 3/2 15.56 3/3 12.36 3/3 12.38 736 X'1'
JOB33 1 4 SCHD3 1 3/1 17.34 PENDING
SCHD3 1 3/1 17.44 PENDING
SCHD3 1 3/1 17.47 PENDING
SCHD3 1 3/1 17.47 PENDING
To
Limit the report to one job or a group of jobs
Specify
Name=jname|generic jname
JCL that produces this report requires the inclusion of a work file. A generic
version of this work file is contained on the installation tape. The file's name is
Z.CAWORK1. Tailor this file to your installation's needs and ensure that it is
accessible before running the JCL that produces the report. To list the last
5-36 Unicenter CA-Scheduler Reference Guide, Part 2

5.4 Batch Versions of Online Reports
seven executions of all Unicenter CA-Scheduler-controlled jobs, submit the
following JCL with your job statement:
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT JOBHIST
/
/&
The following information is included on the Job History Report:
JOB NAME
JNO
ST
SCHEDULE NAME
RC
SCHEDULED DATE
SCHEDULED TIME
START DATE
START TIME
END DATE
END TIME
POWER JOBNO
COMP. CODE
The job name.
The Unicenter CA-Scheduler job number.
The station ID.
The schedule to which the job was assigned.
The selection criteria reason code.
The date that the job was scheduled to run.
The time that the job was scheduled to run.
The date that the job actually started.
The time that the job actually started.
The date that the job actually completed.
The time that the job actually completed.
The POWER assigned job number
The job completion code or submit fail code
(PENDING) indicates that the job did not complete
on the day it was scheduled to run (backlogged).
5.4.7.1 Example 1
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT JOBHIST NAME=JOB1
/
/&
The preceding JCL lists the last seven executions of JOB1.
Chapter 5. Reports 5-37

5.4 Batch Versions of Online Reports
5.4.7.2 Example 2
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REPORT JOBHIST NAME=JOB
/
/&
5.4.8 Successor Chain List
This report lists the last seven executions of all jobs that begins with the letters
JOB.
The Successor Chain List report may be produced for a job or a schedule. It
includes the job (or schedule) and its immediate and global successors. Four
REPORT command objects may be used to produce the list.
COMPUTER ASSOCIATES SUCCESSOR CHAIN PAGE 1
1 PBC7A 1 4 BCBDACC
2 PBC1A 1 4 BCBDACC
3 PBC12A 1 4 BCBDACC
4 PBC11A 1 4 BCBDACC
5 PBC12A 1 4 BCBDACC
6 PBC7A 2 4 BCBDACC
7 PBC122A 1 4 BCBDACC
8 PBC124A 1 4 BCBDACC
9 PBC128A 1 4 BCBDACC
1 PBC14A 1 4 BCBDACC
11 PBC142A 1 4 BCBDACC
12 PBC7A 3 4 BCBDACC
13 PBC998A 2 4 BCBDACC
7 PBC128A 1 4 BCBDACC DEADLOCK
To produce the successor chain list for a job out of the job master database,
submit the following JCL with your job statement:
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT JOBCHAIN NAME=jname
/
/&
To produce the successor chain list for a schedule out of the job master
database, submit the following JCL with your job statement:
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT SCDCHAIN NAME=sname
/
/&
To produce the successor chain list for a job out of the tracking file, submit the
following JCL with your job statement:
5-38 Unicenter CA-Scheduler Reference Guide, Part 2

5.4 Batch Versions of Online Reports
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT CJOBCHAN NAME=jname
/
/&
To produce the successor chain list for a schedule out of the tracking file,
submit the following JCL with your job statement:
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT CSCDCHAN NAME=sname
/
/&
A job name or schedule name is always required. A job name may be qualified
by JNO=nn, STation=nn, or Schedule=sname.
REPORT JOBCHAIN and REPORT SCDCHAIN accept the DATE=date
keyword.
■
■
if the DATE=date keyword is specified, the list is produced for the job (or
schedule) and for only those global successors that would be scheduled on
that date.
If DATE=date keyword is NOT specified, the list is produced for the job
(or schedule) and for all global successors defined on the job master
database.
REPORT CJOBCHAN and REPORT CSCDCHAN produce the list for the job
(or schedule) and for the global successors that are currently on the tracking
file. The current status is also included on the list.
The list is indented left to right, according to the successor level (indicated by
the number in positions 1-3). The indentation is limited by the panel (page)
size and repeats every 20 levels. The rightmost area of the panel may display
the status of the job (or schedule). If a successor loop occurs, the list will stop
there and display an error message: ** DEADLOCK **. A job is identified by its
name, job number, station ID, and schedule name, while a schedule is
identified by its name preceded by dashes.
Subchains for a job or schedule are repeated every time it is referenced on a
criteria record for the named job or schedule or any of its successors. Use the
REPEAT=NO keyword to produce the report without repeated subchains. The
subchain is listed once, and any subsequent references to a subchain are
indicated by '** REPEAT **' on the right side of the report.
Use the LEVEL=nnn keyword to limit the report to 'nnn' levels.
Chapter 5. Reports 5-39

5.4 Batch Versions of Online Reports
5.4.8.1 Example 1
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT JOBCHAIN NAME=JOB1
/
/&
5.4.8.2 Example 2
The preceding JCL produces the global successor chain list for job JOB1.
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT JOBCHAIN NAME=JOB1,DATE=1153
/
/&
5.4.8.3 Example 3
The preceding JCL produces the global successor chain list for job JOB1 and
only those successors that would be scheduled for 10/15/03.
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT SCDCHAIN NAME=SCD1
/
/&
5.4.8.4 Example 4
The preceding JCL produces the global successor chain list for schedule SCD1.
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT SCDCHAIN NAME=SCD1,DATE=1153
/
/&
5.4.8.5 Example 5
The preceding JCL produces the global successor chain list for schedule SCD1
and only those successors that would be scheduled for 10/15/03.
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT CJOBCHAN NAME=JOB1
/
/&
5-40 Unicenter CA-Scheduler Reference Guide, Part 2

5.4 Batch Versions of Online Reports
5.4.8.6 Example 6
The preceding JCL produces the global successor chain list for job JOB1, only if
it is currently on the tracking file.
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT CSCDCHAN NAME=SCD1
/
/&
5.4.8.7 Example 7
The preceding JCL produces the global successor chain list for schedule SCD1,
only if it is currently on the tracking file.
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT JOBCHAIN NAME=JOB1,REPEAT=NO
/
/&
5.4.8.8 Example 8
The preceding JCL produces the global successor chain list for job JOB1
without repeating subchains.
// JOB CAJUTIL
// EXEC CAJUTIL,SIZE=24K
REPORT CSCDCHAN NAME=SCD1,LEVEL=2
/
/&
The preceding JCL produces a list of immediate successors to schedule SCD1
that are currently on the tracking file.
Chapter 5. Reports 5-41

5.5 Tapepull Commands
5.5 Tapepull Commands
5.5.1 TAPEPULL GROUP
This topic describes the keywords and gives usage notes and examples for the
TAPEPULL GROUP and TAPEPULL job.
TAPEPULL GROUP
Punch a job that will produce a list of tapes needed
for a group of simulated jobs.
5.5.1.1 Keywords
Class=x
LDest=userid
POwerjnm=name
PRTy=n
RERun=YES/NO
STAGe=YES|NO
5.5.1.2 Keyword Descriptions
Class=x
Supply the CLASS parameter for the TAPEPULL LIST JOB statement that is
submitted to POWER (a value from 0-9 or A-Z). If the parameter is omitted it
will default to the POWER default value.
LDest=userid
Use this parameter to route the list output of TAPEPULL LIST JOB to the
intended VM user ID. Use this field only for VM spooling.
POwerjnm=name
Use the TAPEPULL LIST JOB name you intend the job to be punched with. If
no job name is supplied, the name is defaulted to TAPEPULL.
PRTy=n
Supply the PRI parameter for the TAPEPULL LIST JOB statement that is
submitted to POWER (a value from 0-9). If the parameter is omitted it will
default to the POWER default value.
RERun=YES/NO
Specify YES to have Unicenter CA-Driver jobs expanded with restart
parameters defined on the Restart Parm Definition panel. No is the default.
5-42 Unicenter CA-Scheduler Reference Guide, Part 2

5.5 Tapepull Commands
5.5.1.3 Usage Notes
STAGe=YES|NO
Specify YES to cause an attempt to retrieve the job's JCL from the Unicenter
CA-Scheduler staging file. Specify NO to retrieve the jobs' JCL from the
master JCL library depending on the job submission information defined for
the job even when there are copies of the JCL on the staging file. NO is the
default and does not need be specified.
Use the TAPEPULL command only after a SIMULATE TAPEPULL command.
You must have either BrightStor CA-Dynam/T or CA-Tape Manager installed
and active at your installation to use this command.
When this command is issued, the JNI file produced by the SIMULATE
TAPEPULL command is read (see the SIMULATE command's Usage Notes)
and each job's JCL is retrieved according to the job submission information
defined for the job and simulated on the JNI file.
Note: See copybook CAJNIWRK.Z for information on the JNI file.
The following LIBTYPES are not supported:
■
■
VSE/POWER Reader Queue
CMS
5.5.1.4 Example
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
SIMULATE TAPEPULL,FD=9183,FOR=3
TAPEPULL GROUP
/
/&
The preceding example illustrates how the TAPEPULL keyword in the
simulation is used together with the command TAPEPULL to punch the job
that will print all the necessary tapes for the jobs that appear on the SIMEXEC
report.
Chapter 5. Reports 5-43

5.5 Tapepull Commands
5.5.2 TAPEPULL JOB
TAPEPULL JOB
Punch a job that will produce a list of tapes needed for
that specific job.
5.5.2.1 Keywords
Name=jname
Class=x
JNo=nn
LDest=userid
POwerjnm=name
PRTy=n
Rerun=YES|NO
Schedule=sname
STAGe=YES|NO
5.5.2.2 Keyword Descriptions
Name=jname
Specify the job (1- to 8-character job name) you want to include.
Class=x
Supply the CLASS parameter for the TAPEPULL LIST JOB statement that is
submitted to POWER (a value from 0-9 or A-Z). If the parameter is omitted it
will default to the POWER default value.
JNo=nn
Specify the job number (an integer from 1-99) if you want to include a
particular occurrence of a job.
LDest=userid
Use this parameter to route the list output of TAPEPULL LIST JOB to the
intended VM user ID. Use this field for VM spooling only.
POwerjnm=name
Use the TAPEPULL LIST JOB name you intend the job to be punched with. If
no job name is supplied, the name is defaulted to TAPEPULL.
PRTy=n
Supply the PRI parameter for the TAPEPULL LIST JOB statement that is
submitted to POWER (a value from 0-9). If the parameter is omitted it will
default to the POWER default value.
5-44 Unicenter CA-Scheduler Reference Guide, Part 2

5.5 Tapepull Commands
5.5.2.3 Usage Notes
5.5.2.4 Example
Rerun=YES|NO
Specify YES to have Unicenter CA-Driver jobs expanded with restart
parameters specified on the DRIVER Restart Parm Definition panel.
Schedule=sname
Specify the schedule name (1-8 characters) if the job has been defined in more
than one schedule. If this is not specified, Unicenter CA-Scheduler will include
the first job it finds with the specified job name.
STAGe=YES|NO
Specify YES to cause an attempt to retrieve the jobs' JCL from the Unicenter
CA-Scheduler staging file. Specify NO to retrieve the jobs' JCL from the
master JCL library depending on the job submission information defined for
the job even when there are copies of the JCL on the staging file. NO is the
default and need not be specified.
Use the TAPEPULL JOB command to produce a list of tapes needed for a
specific job. You must have either BrightStor CA-Dynam/T or CA-Tape
Manager installed and active at your installation to use this command.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
TAPEPULL JOB N=JOB111,S=SCD11,RERUN=YES
/
/&
The preceding example illustrates how the TAPEPULL command can be used
to determine which tapes are required to rerun a job.
Chapter 5. Reports 5-45

5.6 Simulation
5.6 Simulation
Unicenter CA-Scheduler can be run in simulation mode. This means that jobs
and schedules are selected for processing, but no jobs are actually run. Instead,
simulation reports are produced showing what schedules and jobs would be
selected and when and where each job would be processed. Jobs are
scheduled for processing on the simulation reports depending on their
requirements and the availability of resources, in addition to the start times,
deadlines, and predecessors that determine scheduling in a live run. More
specifically, simulation scheduling is based on:
These Values
Defined By These
Fields
In These Records
Job class and priority CLASS, PRIORITY Job base record
Schedule base record
Station resource record
Start time EARLY TIME Job base record
Schedule base record
Job reason code record
Schedule reason code record
Average run time AVERAGE TIME Job base record
Job reason code record
Job history record
Station resource record
Maximum execution time MAXTIME Job base record
Schedule base record
Job reason code record
Schedule reason code record
Routing delay time
between stations
Job requirements:
devices
EXCPs
CPU time
Production start time and
end time at each station
Availability of shared and
dedicated devices
ROUTE DELAY
DASDnn, TAPEnn,
UNITnn
DASD, TAPE, and
UNIT
EXCPS MAX CPU
TIME
PST and PET TIME
DASDnn,TAPENN,
UNIT RECORDnn
Job resource record
Station resource record
Job resource record
Job history record
Station resource record
Station resource record
5-46 Unicenter CA-Scheduler Reference Guide, Part 2

5.6 Simulation
These Values
Availability of units or
partitions of the right
class
Defined By These
Fields
UNITnn, PARTnn
In These Records
Station resource record
The panels and commands that define these records are described in the
"Online Panels and Batch Maintenance" chapter.
Note: The SKIP option, in the JBR, is not reflected in these reports.
5.6.1 Summary of the Simulation Reports
The following reports are generated for each day in the simulation period:
Use This Report Report ID For Information On
Date Translation Report DATETRAN What calendar, workday, and accounting
criteria are true on any given date
Schedules/Jobs Selected For DDMMYY SELECTED Which schedules and jobs wi ll be selected
for processing
Resources Required For All Jobs RESALL What resources are required
Simulated Execution Schedule SIMEXEC When each job should be processed and on
which unit
Simulated
Unit/Partition Utilization
Device Utilization
UNITUTIL
DEVUTIL
The extent to which each:
unit/partition will be used
dedicated device will be used
shared device will be used
Shared Device Utilization
DEVUTIL
Backlogged Schedules/Jobs BACKLOG Which schedules and jobs will have to be
carried over in backlog to the next day
Late Job Profile LATEJOBS Which jobs will start and end late each day
and at the end of the entire simulation
period
Tracking File Job Start Errors (generated
only if you specify REVISE=YES)
EXPERROR
When jobs in the tracking file have not
started yet or did not start on time
Chapter 5. Reports 5-47

5.6 Simulation
Sample reports are at the end of this topic. If you do not want to print some
of these reports, you can specify the ones you want to exclude on the
EXCREPT keyword on the SIMULATE command.
5-48 Unicenter CA-Scheduler Reference Guide, Part 2

5.6 Simulation
5.6.2 Summary of the SIMULATE Command Keywords
To run simulation, execute CAJUTIL0 with the SIMULATE command. The
following keywords are available with the SIMULATE command:
To Produce A Simulated Schedule
For all defined stations
For up to 8 stations
For today
For a date in the past, present or future
For one day
For a number of days
On the Simulated Execution Schedule (SIMEXEC) report
(only) for the first day of simulation
On the Simulated Execution Schedule (SIMEXEC) report
(only) for every day of simulation
On the Simulated Execution Schedule (SIMEXEC) report
(only) starting at FROMDATE or FROMTIME (if
specified) or otherwise AUTOSCAN time
On the Simulated Execution Schedule (SIMEXEC) report
(only) starting at a specific time
On the Simulated Execution Schedule (SIMEXEC) report
(only) ending at the end of the simulation period
may optionally be specified by FOR)
On the Simulated Execution Schedule (SIMEXEC) report
only) ending at a specific time
That starts at AUTOTIM
That starts at a specific time
That lets CPU jobs end if running at production
end time (PET)
That stops CPU jobs at production end time and
restarts at production start time (PST)
That allows the full 24 hours each day
That allows a different amount of time
That shows use at 15-minute intervals
That shows use at a different interval
That selects jobs from the database
That shows current status of tracking file
Ignore Or Use This Keyword
(default)
STATION=(nn,...)
(default)
FROMDATE=mmddyy
(default)
FOR=nnn
(default)
EVERYDAY=YES
(default)
RFT=hhmmm]ddhhmm
(default)
RTT=hhmmm]ddhhmm
(default)
FROMTIME=hhmm
(default)
Cpushut=yes
(default)
MAXTIME=ddhhmm
(default)
INTERVAL=mm
(default)
REVISE=yes
Chapter 5. Reports 5-49

5.6 Simulation
To Produce A Simulated Schedule
That updates the database with the simulated start time
That does not update the database
With all of the simulation reports
Without some of the simulation reports
With some of the Forecast reports
Without diagnostic dumps
With diagnostic dumps (only upon Computer Associates
request)
With the Job Summary report showing
the current month
a different month
Ignore Or Use This Keyword
(default)
UPDATE=NO
(default)
EXCREPT=
(reportid1,...)
INCREPT=
(reportid1...)
(default)
TRACEOPT=
(dump1,...)
(default)
MONthof=mmyy
Valid only if INCREPT=SUMMARY is used. In addition,
this parameter does not affect simulation, only the Job
Summary report.
5.6.3 Summary of the Simulation Commands
The following options are available using commands that must precede the
SIMULATE command. Changed values are in effect for that simulation run
only.
To Change
Jobs and schedules that will be selected by
excluding
- schedules
- jobs
singling out one or more schedules
Use This Command
EXCLUDE S
EXCLUDE J
ONLY S
5-50 Unicenter CA-Scheduler Reference Guide, Part 2

5.6 Simulation
To Change
Jobs and schedules that will be processed by
activating REQUESTED
- schedules
- jobs
adding
- schedules
- jobs
holding
- schedules
- jobs
releasing from HOLD
- schedules
- jobs
rerunning jobs (valid only with REVISE=YES)
Schedules that are included in the Simulated
Execution
Schedule (SIMEXEC) report
Normal execution time for
one or more schedules
one or more jobs
a station
Automatic selection of one or more schedules
Values defined for
dedicated resources
shared resources
Use This Command
REQUEST S
REQUEST J
RUN S
RUN J
HOLD S
HOLD J
RELEASE S
RELEASE J
RERUN J
RONLY S
OVERRIDE SCHEDULE
OVERRIDE JOB
OVERRIDE STATION
OVERRIDE SCHEDULE
OVERRIDE RESOURCE
OVERRIDE SHRRSR
The preceding commands are described in alphabetical order on the following
pages.
Note: The function of the INCLUDE command has been incorporated into the
OVERRIDE and RUN commands. For compatibility with Version 7.0,
however, the INCLUDE command will still be accepted.
5.6.4 Virtual Storage Requirements for Simulation
Executing simulation requires 200K in virtual storage for the program. A
certain amount of additional virtual storage is necessary based upon the
following variables.
Allocate
For Each
72 bytes Partition
120 bytes Defined station
Chapter 5. Reports 5-51

5.6 Simulation
Allocate
For Each
80 bytes Defined and selected schedule
152 bytes Defined and selected job
268 bytes Selected job with a resource record
5.6.4.1 Example
Given the following values, 290K of virtual storage is necessary to run
simulation.
Program storage
248 bytes
Partitions BG,F1,F2,F3,F4
36 bytes
Stations 2,3,39,4,6,9
72 bytes
6 schedules
48 bytes
3 jobs
456 bytes
15 jobs with resource records
42 bytes
--------------------------------------------------------------------
Total
29648 bytes
or 29K
5.6.5 Selection Criteria's Impact on Simulation
Follow these guidelines to produce accurate simulation results.
1. Specify REQUESTED after job and schedule names when writing selection
criteria. Otherwise, simulation may return different reason codes than those
Unicenter CA-Scheduler returns during actual production.
2. Remember that DSN, DOS, and PRED predecessors may affect simulation
accuracy. Simulation assumes that these types of predecessors complete
successfully. In actual production, they may not. Therefore, do not assume
that simulation involving these types of predecessors is always accurate.
5-52 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7 Simulation Commands
5.7.1 EXCLUDE Job
This topic describes each of the commands that must precede the SIMULATE
command. Usage notes on when to use the command are given, descriptions
are given for each keyword, and an example is provided for each command.
EXCLUDE Job Name=jname
Exclude one or more jobs for this
simulation run only.
5.7.1.1 Keywords
Name=jname
JNo=nn
Schedule=sname
SImday=nn
STation=nn
5.7.1.2 Keyword Descriptions
Name=jname
Specify the job (1- to 8-character job name) you want to exclude from the
simulation run. To exclude a group of jobs, use the asterisk (*) or question
mark (?) mask characters.
JNo=nn
Specify the job number (an integer from 1-99) if you want to exclude a
particular occurrence of the job from the simulation run.
Schedule=sname
Specify the schedule name (1-8 characters) if the job has been defined in more
than one schedule. If this is not specified, Unicenter CA-Scheduler will exclude
the first job it finds with the specified job name.
SImday=nn
Indicate what day to exclude the job. Give the number of that day relative to
the beginning of the simulation period, where the first day is day 0. Therefore,
to exclude a job only on the second day of simulation, specify SIMDAY=1. If
you do not use this keyword, the job will be excluded every day during the
simulation period.
STation=nn
Chapter 5. Reports 5-53

5.7 Simulation Commands
5.7.1.3 Usage Notes
5.7.1.4 Example
5.7.2 EXCLUDE Schedule
Specify the station ID (integer from 1-99) for non-CPU stations.
Use the EXCLUDE Job command to exclude a job that is normally selected
today but is not needed for this simulation run. The effect is to treat the job as
if it can not be selected today. All successors are excluded too.
Specify JNO for job numbers other than 01. Specify the schedule name if the
job has been defined in more than one schedule. Specify STATION for
non-CPU stations.
The EXCLUDE Job command must precede the SIMULATE command. Code a
separate EXCLUDE command for each job that you want to exclude.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
EXCLUDE J N=MONTHLY,
S=ANNUAL
SIMULATE
/
/&
exclude a job
job is in this schedule
produce simulation reports
The preceding example excludes from this simulation run a job named
MONTHLY that is in the schedule named ANNUAL. If MONTHLY has any
successors, they will be excluded too.
EXCLUDE Schedule Name=sname
Exclude one or more schedules for this
simulation run only.
5.7.2.1 Keywords
Name=sname
SImday=nn
5-54 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7.2.2 Keyword Descriptions
5.7.2.3 Usage Notes
5.7.2.4 Example
Name=sname
Use this required keyword to specify the schedule (1- to 8-character schedule
name) you want to exclude from the simulation run. To exclude a group of
jobs, use the asterisk (*) or question mark (?) mask characters.
SImday=nn
Indicate what day to exclude the schedule. Give the number of that day
relative to the beginning of the simulation period, where the first day is day 0.
Therefore, to exclude a schedule only on the second day of simulation, specify
SIMDAY=1. If you do not use this keyword, the schedule will be excluded
every day during the simulation period.
Use the EXCLUDE Schedule command to exclude a schedule that is normally
selected today but is not needed for this simulation run. All jobs within this
schedule, as well as their successors, are excluded. The effect of this command
is to treat this schedule as if it can not be selected today.
The EXCLUDE Schedule command must precede the SIMULATE command.
Code a separate EXCLUDE command for each schedule that you want to
exclude.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
EXCLUDE S N=USUALLY
SIMULATE
/
/&
exclude a schedule
produce simulation reports
The preceding example excludes a schedule named USUALLY from this
simulation run. If this schedule has any successors, they will be excluded too.
Chapter 5. Reports 5-55

5.7 Simulation Commands
5.7.3 HOLD Job
HOLD Job Name=jname
Place one or more jobs in HELD status.
5.7.3.1 Keywords
Name=jname
AT=hhmm|ddhhmm
JNo=nn
Schedule=sname
SImday=nn
STation=nn
5.7.3.2 Keyword Descriptions
Name=jname
Specify the job (1- to 8-character job name) you want to put on hold. To hold
a group of jobs, use the asterisk (*) or question mark (?) mask characters.
AT=hhmm|ddhhmm
Specify the time that the job is to be held. Specify hhmm in terms of a 24-hour
clock. Use dd to indicate the number of autoscan days in the future when the
job is to be held. Do not use dd if the job will be held today.
JNo=nn
Specify the job number (an integer from 1-99) if you want to hold a particular
occurrence of a job. If not specified, the first occurrence is assumed.
Schedule=sname
Specify the schedule name (1-8 characters) if the job has been defined in more
than one schedule. If this is not specified, Unicenter CA-Scheduler will hold
the first job it finds with the specified job name.
SImday=nn
Indicate what day of the simulation period to put the job on hold. Give the
number of that day relative to the beginning of the simulation period, where
the first day is day 0. Therefore, to place a job in HELD status on the second
day of simulation, specify SIMDAY=1. If you do not use this keyword, the job
is placed in HELD status every day during the simulation period.
STation=nn
Specify the station ID (integer from 1-99) for non-CPU stations.
5-56 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7.3.3 Usage Notes
5.7.3.4 Example
5.7.4 HOLD Schedule
Use the HOLD Job command to prevent simulation from starting a job until
the RELEASE command is issued.
This command must precede the SIMULATE command.
Jobs that are held are not placed in a partition to simulate their processing
until the RELEASE simulation command is issued against them.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
HOLD J N=CUST1,
S=SALES,
SIMDAY=2
SIMULATE
/
/&
hold a job
job is in this schedule
hold it only on 3rd day
produce simulation reports
The preceding example places the job CUST1 in HELD status on the third day
of the simulation period.
HOLD Schedule Name=sname
Place one or more schedules in HELD status.
5.7.4.1 Keywords
Name=sname
AT=hhmm|ddhhmm
SImday=nn
5.7.4.2 Keyword Descriptions
Name=sname
Specify the schedule (1- to 8-character schedule name) you want to put on
hold. To hold a group of schedules, use the asterisk (*) or question mark (?)
mask characters.
AT=hhmm|ddhhmm
Chapter 5. Reports 5-57

5.7 Simulation Commands
5.7.4.3 Usage Notes
5.7.4.4 Example
Specify the time that the schedule is to be held. Specify hhmm in terms of a
24-hour clock. Use dd to indicate the number of autoscan days in the future
when the schedule is to be held. Do not use dd if the schedule will be held
today.
SImday=nn
Indicate what day of the simulation period to put the schedule on hold. Give
the number of that day relative to the beginning of the simulation period,
where the first day is day 0. Therefore, to place a schedule in HELD status on
the second day of simulation, specify SIMDAY=1. If you do not use this
keyword, the schedule is placed in HELD status every day during the
simulation period.
Use the HOLD Schedule command to prevent simulation from starting a
schedule until the RELEASE command is issued. It must precede the
SIMULATE command.
The HOLD Schedule command holds a schedule and all jobs in the schedule
that have not started, completed, interrupted, abended, or failed by the time
the HOLD command is processed.
Jobs in a held schedule are not placed in a partition to simulate their
processing until the RELEASE simulation command is issued against them.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
HOLD S N=PAYROLL,
AT=1
SIMULATE
/
/&
hold a schedule
at 1:
produce simulation reports
The preceding example holds an entire schedule at 10:00 a.m. every day
during the simulation period. All jobs in the schedule that have not started,
ended, interrupted, abended, or failed by 10:00 a.m. will be placed in HELD
status until they are released.
5-58 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7.5 ONLY Schedule
ONLY Schedule Name=sname
Limit the eligible workload for
simulation to one or more schedules.
5.7.5.1 Keywords
Name=sname
SImday=nn
5.7.5.2 Keyword Descriptions
5.7.5.3 Usage Notes
Name=sname
Specify the schedule (1- to 8-character schedule name) for which simulation
reports are to be produced. To include a group of schedules, use the asterisk
(*) or question mark (?) mask characters.
SImday=nn
Indicate what day of the simulation period to process this command. Give the
number of that day relative to the beginning of the simulation period, where
the first day is day 0. Therefore, to process the command only on the second
day of simulation, specify SIMDAY=1. If you do not use this keyword, the
command will be processed every day during the simulation period.
The ONLY Schedule command must precede the SIMULATE command.
Use the ONLY Schedule command to limit the eligible workload for simulation
to one or more schedules. A schedule is eligible for simulation if
AUTOSEL=YES is specified on its SBR and its calendar or criteria indicates
that the schedule is to be selected on a given day within the simulation period.
Use the RUN Schedule command to include a schedule that is not normally
selected for a simulation day. Use the OVERRIDE SCHEDULE command to
change the AUTOSEL value.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
Chapter 5. Reports 5-59

5.7 Simulation Commands
5.7.5.4 Example
5.7.6 OVERRIDE Job
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
ONLY S N=ACCT
ONLY S N=MANU
SIMULATE
/
/&
simulate the accounting schedules only
simulate the manufacturing schedules only
perform the simulation
The preceding example limits the simulation processing to schedules beginning
with ACCT and MANU.
OVERRIDE Job Name=jname
Increase or decrease the amount of time
it takes to process one or more jobs.
5.7.6.1 Keywords
Name=jname
FACtor=nnn
JNo=nn
Schedule=sname
STation=nn
5.7.6.2 Keyword Descriptions
Name=jname
Specify the job name (1-8 characters) of the job whose processing time is to be
modified for the simulation reports. To modify processing time for a group of
jobs, use the asterisk (*) or question mark (?) mask characters.
FACtor=nnn
Increase or decrease the amount of time it normally takes to process the job.
The simulation reports will show the effect of this change and allow you to see
what would happen if execution time were actually increased or decreased.
Specify nnn as the percentage by which you want the normal processing time
to be multiplied (100 is normal processing time). For example, to test the effect
of increasing processing time for a job by 50%, specify FACTOR=150; that is, a
job that normally takes an hour to process will be given an hour and a half.
The simulation reports will reflect this change. To test the effect of a job
running more quickly, you can specify FACTOR=50. This will temporarily
decrease processing time by 50%; that is, a job that normally takes an hour to
process will be given a half hour. The simulation reports will reflect this
change.
JNo=nn
5-60 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7.6.3 Usage Notes
5.7.6.4 Example
Specify the job number (an integer from 1-99) if you want to modify the
processing time for a particular occurrence of a job.
Schedule=sname
Specify the schedule name (1-8 characters) if the job has been defined in more
than one schedule. If this is not specified, Unicenter CA-Scheduler will take the
first job it finds with the specified job name.
STation=nn
Specify the station ID (integer from 1-99) for non-CPU stations.
Use the OVERRIDE Job command only if you want the simulation reports to
reflect a change in the amount of time it normally takes to execute one job.
Specify the schedule name if the job has been defined in more than one
schedule. Specify STATION for non-CPU stations. Specify JNO for job numbers
other than 01.
This command must precede the SIMULATE command.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
OVERRIDE JOB NAME=CUST1,
SCHEDULE=SALES,
JNO=1,
FACTOR=5
SIMULATE
/
/&
change execution time for this job
schedule from base record
job number from base record
cut processing time in half
produce simulation reports
The preceding example shows how the simulation reports would look if this
job could be processed 50% faster.
Chapter 5. Reports 5-61

5.7 Simulation Commands
5.7.7 OVERRIDE Resource
OVERRIDE RESOURCE STation=nn
Change dedicated resources for all or
part of one simulation run.
5.7.7.1 Keywords
5.7.7.2 Keyword Descriptions
STation=nn
SUBID=nnnn
SYSID=sysid
AVGtime=mm|hhmm|ddhhmm
DASDnn=(type,number)
DEFclass=x
EVeryday=NO|YES
EXITPARM=xxxxxxxxxxxxxxxx
FACtor=nnn
OET=hhmm|ddhhmm
OST=hhmm|ddhhmm
PARTnn=(classes,header)
PET=hhmm
PST=hhmm
RDT=mm|hhmm|ddhhmm
TAPEnn=(type,number)
UNITnn=(classes,header)
URnn=(type,number)
STation=nn
Identify the workstation for which overrides are being submitted.
SUBID=nnnn
Identify each unit at a non-CPU station by a 1-4 digit number. (This is the
substation for which dedicated resources were defined with the DEFINE
RESOURCE command.) This value is in effect during this simulation run only.
SYSID=sysid
Specify the CPU for which resources are being overridden.
AVGtime=mm|hhmm|ddhhmm
Change the number of days, hours, and minutes it will take to process a job at
this station. Leading zeros are not required. This value will be used during
this simulation run for any job without an AVGTIME in its job base record, or
if no history exists. DOS accounting does not update the AVGtime field in the
5-62 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
JBR record. Instead, the AVGtime field in the JHR (job history) record is
updated. When simulation is performed, the order for selection of AVGtime is:
1. AVGtime from the job base record
2. AVGtime (updated by DOS accounting) from the job history record
3. station defaults
DASDnn=(type,number)
Change the direct access devices that are exclusively dedicated to one
substation. (A substation is one CPU at the CPU station or one unit at a
non-CPU station.) This value is in effect during this simulation run only.
Describe each type on a separate DASDnn keyword, where nn is a number
from 01 to 16. Specify the device type and the number of devices of that type
(up to 255). For example, to define eight 3380s and ten 3390s, specify
DASD01=(3380,8) and DASD02=(3390,10).
DEFclass=x
Change the default class for all jobs processed at this station that do not have a
defined class. This value is in effect during this simulation run only.
EVeryday=NO|YES
Indicate whether you want the override conditions to be in effect every day
starting at Override Start Time (OST), and ending at Override End Time
(OET). Valid options are:
No
Yes
The override conditions will be in effect only on the days specified by
OST=ddhhmm and OET=ddhhmm. This is the default and need not be
specified.
OST and OET will apply to every day in the simulation period. For
example, to put the override conditions into effect during the noon hour
every day during the simulation period, code OST=1200, OET=1300 and
EVERYDAY=YES on the OVERRIDE command.
EXITPARM=xxxxxxxxxxxxxxxx
Use this 16-byte field to pass information to an optional user exit that you can
use to adjust a job's class or average process time for this simulation run. See
the chapter "User Exits and Interfaces" in the Unicenter CA-Scheduler Systems
Programmer Guide for more information on coding this exit.
FACtor=nnn
Increase or decrease the amount of time it normally takes to process all of the
jobs run on one CPU. The simulation reports will show the effect of this
change and allow you to see what would happen if the execution time were
actually increased or decreased. Specify nnn as the percentage by which you
want the normal processing time to be multiplied (100 is normal processing
Chapter 5. Reports 5-63

5.7 Simulation Commands
time). For example, to test the effect of a disaster that slows down all
processing on one CPU, specify FACTOR=150 with this CPU's SYSID. This
will temporarily increase processing time on this CPU by 50%; that is, a job
that normally takes an hour to process will be given an hour and a half. The
simulation reports will show how all of the work will be processed assuming
that each job run on this CPU takes 50% longer than normal. To test the effect
of a new processor that runs jobs more quickly, you can specify FACTOR=50.
This will temporarily decrease processing time by 50%; that is, a job that
normally takes an hour to process will be given a half hour. The simulation
reports will show how all of the work will be processed assuming that each
job takes half its normal time.
OET=hhmm|ddhhmm
Specify when you want the override conditions to end (Override End Time).
Specify hhmm in terms of a 24-hour clock. Specify dd as the relative number
of days after simulation begins, where the first simulated day is 00, the second
day is 01, the third day is 02, and so on. For example, if you specify
OET=0801, the override conditions will end at 8:01 A.M. on the first day of
simulation. If you specify OET=012001, the override conditions will end at
8:01 P.M. on the second day of simulation. If OET is not specified, the
override conditions will be in effect until the end of the simulation run.
OST=hhmm|ddhhmm
Specify when you want the override conditions to go into effect (Override Start
Time). Specify hhmm in terms of a 24-hour clock. Specify dd as the relative
number of days after simulation begins, where the first simulated day is 00,
the second day is 01, the third day is 02, and so on. For example, if you
specify OST=0801, the override conditions will go into effect at 8:01 A.M. on
the first day of simulation. If you specify OST=012001, the override conditions
will go into effect at 8:01 P.M. on the second day of simulation. If OST is not
specified, the override conditions will go into effect at the beginning of the
simulation run.
PARTnn=(classes,header)
Temporarily change the classes of jobs that can run in a partition. To do this,
specify PARTnn=classes, where nn is a number from 1 to 12. You can only
specify a header on an OVERRIDE if
■
■
OST and OET are not specified
You are defining a new partition that will only be used during this
simulation run
The classes defined here are each one character in length, and correspond to
the classes defined for jobs (or default classes for schedules).
5-64 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
PET=hhmm
Change the production end time at this station. Specify the time of day in
terms of a 24-hour clock, where 0800 is 8:00 a.m. and 2000 is 8:00 p.m. This
value is in effect during this simulation run only. Note that you cannot
change the PET and specify OST/OET on the same OVERRIDE command.
PST=hhmm
Change the production start time at this station. Specify the time of day in
terms of a 24-hour clock, where 0800 is 8:00 a.m. and 2000 is 8:00 p.m. This
value is in effect during this simulation run only. Note that you cannot
change the PST and specify OST/OET on the same OVERRIDE command.
RDT=mm|hhmm|ddhhmm
Change the number of days, hours, and minutes it will take for a job to get to
this station from the preceding station (Routing Delay Time). Leading zeros
are not required. This value is in effect during this simulation run only and
will be used for any job without an RDT in its job record.
TAPEnn=(type,number)
Change the tape devices that are exclusively dedicated to one substation. (A
substation is one CPU at the CPU station or one unit at a non-CPU station.)
This value is in effect during this simulation run only. Describe each type on a
separate TAPEnn keyword, where nn is a number from 01 to 16. Specify the
device type and the number of devices of that type (up to 255). For example,
to define six 3420s and eight 3480s, specify TAPE01=(3420,6) and
TAPE02=(3480,8).
UNITnn=(classes,header)
Temporarily change the classes of jobs that can be processed at a unit. To do
this, specify UNITnn=classes, where nn is a number from 1 to 16. You can
only specify a header on an OVERRIDE if
■
■
OST and OET are not specified
You are defining a new unit that will only be used during this simulation
run
The classes defined here are each one character in length, and correspond to
the classes defined for jobs (or default classes for schedules).
URnn=(type,number)
Change the unit record devices that are exclusively dedicated to one
substation. (A substation is one CPU at the CPU station or one unit at a
non-CPU station.) This value is in effect during this simulation run only.
Describe each type on a separate URnn keyword, where nn is a number from
Chapter 5. Reports 5-65

5.7 Simulation Commands
5.7.7.3 Usage Notes
5.7.7.4 Example
01 to 16. Specify the device type and the number of devices of that type (up to
255). For example, to define twenty 2540s and twelve 1403s, specify
UR01=(2540,20) and UR02=(1403,12).
Use the OVERRIDE Resource command to change the values specified on the
DEFINE Resource command on the master database for device types or job
classes. This allows you to test the effect of a change in resources available at
one station or dedicated to one substation.
You can also use FACTOR to test the effect of increased or decreased execution
time on one CPU.
The OVERRIDE Resource command must precede the SIMULATE command.
Changes are in effect for this simulation run only, beginning with OST and
ending with OET. If no time parameters are given, changes are in effect
throughout the simulation run.
You can only change PST or PET on this command if OST/OET are not
specified.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
OVERRIDE RESOURCE SYSID=1,
DASD1=(338,2),
TAPE1=(342,1),
FACTOR=5
SIMULATE
/
/&
change CPU 1 resources
increase the number of 338s
decrease the number of 342s
cut processing time in half
produce simulation reports
The preceding example changes the number of 3380s and 3420s available for
the exclusive use of the first CPU. It also multiplies all processing times by
50%. These changes allow you to test the effect of a faster processor with more
direct access devices and fewer tape drives. The results will be reflected on the
simulation reports that are produced for this simulation run only.
5-66 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7.8 OVERRIDE Schedule
5.7.8.1 Keywords
OVERRIDE Schedule Name=sname Increase or decrease the time it takes to
process one or more schedules, or
change AUTO SELECT to YES.
Name=sname
AUtosel=YES
FACtor=nnn
STation=nn
5.7.8.2 Keyword Descriptions
Name=sname
Specify the schedule (1- to 8-character schedule name) whose processing time
you want to modify. To modify processing time for a group of schedules, use
the asterisk (*) or question mark (?) mask characters.
AUtosel=YES
Change the AUTOSEL parameter on the schedule base record.
FACtor=nnn
Increase or decrease the amount of time it normally takes to process the jobs in
this schedule. The simulation reports will show the effect of this change and
allow you to see what would happen if execution time were actually increased
or decreased. Specify nnn as the percentage by which you want the normal
processing time to be multiplied. For example, to test the effect of increasing
processing time for all jobs in this schedule by 50%, specify FACTOR=150; that
is, this schedule that normally takes an hour to process will be given an hour
and a half. The simulation reports will reflect this change. To test the effect of
the jobs running more quickly, you can specify FACTOR=50. This will
temporarily decrease processing time by 50%; that is, a schedule that normally
takes an hour to process will be given a half hour. The simulation reports will
reflect this change.
STation=nn
Identify the workstation for which this override is being submitted. If not
specified, station 40 (CPU) is assumed.
Chapter 5. Reports 5-67

5.7 Simulation Commands
5.7.8.3 Usage Notes
5.7.8.4 Example
Use the OVERRIDE Schedule command if you want the simulation reports to
reflect a change in the amount of time it normally takes to execute all of the
jobs in one schedule or if you want to change the AUTO SELECT value from
NO to YES.
If no STATION is specified, the override is in effect at the CPU.
This command must precede the SIMULATE command.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
OVERRIDE SCHEDULE NAME=CUSTMAST,
FACTOR=15,
AUTOSEL=YES
SIMULATE
/
/&
change execution time for schedule
increase processing time by half
change AUTO SELECT to YES
produce simulation reports
5.7.9 OVERRIDE SHRRSR
The preceding example shows how the simulation reports would look if it took
50% longer to process all of the jobs in this schedule. It also changes the
AUTO SELECT option on the schedule definition from NO to YES so that the
schedule will be automatically selected. See the example on page % to decrease
processing time.
OVERRIDE SHRRSR STation=nn
Change shared resources for all or part
of one simulation run.
5.7.9.1 Keywords
STation=nn
DASDnn=(type,number,substation,substation,...)
EVeryday=NO|YES
OET=hhmm|ddhhmm
OST=hhmm|ddhhmm
TAPEnn=(type,number,substation,substation,...)
URnn=(type,number,substation,substation,...)
5-68 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7.9.2 Keyword Descriptions
STation=nn
Identify the workstation for which overrides are being submitted.
DASDnn=(type,number,substation,substation,...)
Change the direct access devices that can be shared by two or more
substations. This value is in effect during this simulation run only. Describe
each device type on a separate DASDnn keyword, where nn is a number from
01 to 16. Specify the device type and the number of devices of that type (up to
255). Then list up to eight substations that can share those devices. If this is a
CPU station, identify each CPU by the SYSID number assigned it on the
DEFINE RESOURCE command. If this is a non-CPU station, identify each unit
by the SUBID number assigned to it on the DEFINE RESOURCE command.
For example, to define four 3380s that can be shared by the three CPUs
defined as SYSID=1, SYSID=2, and SYSID=3, specify DASD01=(3380,4,1,2,3).
EVeryday=NO|YES
Indicate whether you want the override conditions to be in effect every day
starting at Override Start Time (OST), and ending at Override End Time
(OET). Valid options are:
No
Yes
The override conditions will be in effect only on the days specified by
OST=ddhhmm and OET=ddhhmm. This is the default and need not be
specified.
OST and OET will apply to every day in the simulation period. For
example, to put the override conditions into effect during the noon hour
every day during the simulation period, code OST=1200, OET=1300 and
EVERYDAY=YES on the OVERRIDE command.
Chapter 5. Reports 5-69

5.7 Simulation Commands
OET=hhmm|ddhhmm
Specify when you want the override conditions to end (Override End Time).
Specify hhmm in terms of a 24-hour clock. Specify dd as the relative number
of days after simulation begins, where the first simulated day is 00, the second
day is 01, the third day is 02, and so on. For example, if you specify
OET=0801, the override conditions will end at 8:01 a.m. on the first day of
simulation. If you specify OET=012001, the override conditions will end at
8:01 p.m. on the second day of simulation. If OET is not specified, the
override conditions will be in effect until the end of the simulation run.
OST=hhmm|ddhhmm
Specify when you want the override conditions to go into effect (Override Start
Time). Specify hhmm in terms of a 24-hour clock. Specify dd as the relative
number of days after simulation begins, where the first simulated day is 00,
the second day is 01, the third day is 02, and so on. For example, if you
specify OST=0801, the override conditions will go into effect at 8:01 a.m. on the
first day of simulation. If you specify OST=012001, the override conditions
will go into effect at 8:01 p.m. on the second day of simulation. If OST is not
specified, the override conditions will go into effect at the beginning of the
simulation run.
TAPEnn=(type,number,substation,substation,...)
Change the tape devices that can be shared by two or more substations. This
value is in effect during this simulation run only. Describe each device type
on a separate TAPEnn keyword, where nn is a number from 01 to 16. Specify
the device type and the number of devices of that type (up to 255). Then list
up to eight substations that can share those devices. If this is a CPU station,
identify each CPU by the SYSID number assigned it on the DEFINE
RESOURCE command. If this is a non-CPU station, identify each unit by the
SUBID number assigned it on the DEFINE RESOURCE command. For
example, to define four 3420s that can be shared by the two CPUs defined as
SYSID=1 and SYSID=2, specify TAPE01=(3420,4,1,2).
URnn=(type,number,substation,substation,...)
Change the unit record devices that can be shared by two or more substations.
This value is in effect during this simulation run only. Describe each unit
record type on a separate URnn keyword, where nn is a number from 01 to 16.
Specify the device type and the number of devices of that type (up to 255).
Then list up to eight substations that can share those devices. If this is a CPU
station, identify each CPU by the SYSID number assigned it on the DEFINE
RESOURCE command. If this is a non-CPU station, identify each unit by the
SUBID number assigned to it on the DEFINE RESOURCE command. For
example, to define six 2540s that can be shared by the four keypunch units
defined as SUBID=1, SUBID=2, SUBID=3, and SUBID=4, specify
UR01=(2540,6,1,2,3,4).
5-70 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7.9.3 Usage Notes
5.7.9.4 Example
5.7.10 OVERRIDE Station
Use the OVERRIDE SHRRSR command to change the values specified on the
DEFINE SHRRSR command in the master database for device types. This
allows you to test the effect of a change in resources shared by two or more
substations.
This command must precede the SIMULATE command. Changes are in effect
for this simulation run only, beginning with OST and ending with OET. If no
time parameters are given, changes are in effect throughout the simulation run.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
OVERRIDE SHRRSR DASD1=(338,,1,2),
DASD2=(339,2,3,4)
SIMULATE
/
/&
decrease the number of 338s
decrease the number of 339s
produce simulation reports
The preceding example decreases the number of 3380s and 3390s that can be
shared by the CPUs listed on the DEFINE SHRRSR command.
OVERRIDE STATION Id=nn
Stop work from being scheduled at a
station at a specific time, then restart it
at a later time.
5.7.10.1 Keywords
Id=nn
Halt=hhmm|ddhhmm
Restart=hhmm|ddhhmm
Subid=nnn
SYsid=nn
Chapter 5. Reports 5-71

5.7 Simulation Commands
5.7.10.2 Keyword Descriptions
Id=nn
5.7.10.3 Usage Notes
Specify the workstation where scheduling will be temporarily suspended (an
integer from 1-99).
Halt=hhmm|ddhhmm
Tell what time to stop work at a station. This keyword, along with the
RESTART keyword, allows you to stop and restart processing during the
simulation period, for example during the lunch hour or over the weekend.
Specify hhmm in terms of a 24-hour clock. Specify dd as the relative number
of days after simulation begins, where the first simulated day is 00, the second
day is 01, the third day is 02, and so on.
Restart=hhmm|ddhhmm
Tell what time to resume work at a station after it has been halted. This
keyword, along with the HALT keyword, allows you to stop and restart
processing during the simulation period, for example during the lunch hour or
over the weekend. Specify hhmm in terms of a 24-hour clock. Specify dd as
the relative number of days after simulation begins, where the first simulated
day is 00, the second day is 01, the third day is 02, and so on.
Subid=nnn
Identify each unit at a non-CPU station by a 1-3 digit number.
SYsid=nn
Specify the SYSID for which resources are being overridden.
Use the OVERRIDE Station command to stop work for any amount of time at
any time during the simulation period.
The OVERRIDE Station command must precede the SIMULATE command.
The value that you supply for the SUBID or SYSID option will be in effect
during the simulation period.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
5-72 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7.10.4 Example
5.7.11 RELEASE JOB
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
OVERRIDE STATION ID=1,
HALT=12,
RESTART=13
OVERRIDE STATION ID=4,
HALT=3,
RESTART=32359
SIMULATE
/
/&
stop production at noon
resume production at 1 p.m.
stop production on Sunday
resume production on Monday
produce simulation reports
The preceding example stops work from being scheduled during the lunch
hour at station 10 on the first day of simulation. It stops work all day Sunday
at station 40 on the fourth day of simulation.
RELEASE Job Name=jname
Release one or more jobs from HELD status.
5.7.11.1 Keywords
Name=jname
AT=hhmm|ddhhmm
JNo=nn
Schedule=sname
SImday=nn
STation=nn
5.7.11.2 Keyword Descriptions
Name=jname
Specify the job (1- to 8-character job name) you want to release from HELD
status. To release a group of jobs, use the asterisk (*) or question mark (?)
mask characters.
AT=hhmm|ddhhmm
Specify the time that the job is to be released from HELD status. Specify
hhmm in terms of a 24-hour clock. Use dd to indicate the number of autoscan
days in the future when the job is to be released. Do not use dd if the job will
be released today.
Chapter 5. Reports 5-73

5.7 Simulation Commands
5.7.11.3 Usage Notes
5.7.11.4 Example
JNo=nn
Specify the job number (an integer from 1-99) if you want to release a
particular occurrence of a job.
Schedule=sname
Specify the schedule name (1-8 characters) if the job has been defined in more
than one schedule. If this is not specified, Unicenter CA-Scheduler will release
the first job it finds with the specified job name.
SImday=nn
Indicate what day of the simulation period to release the job from hold. Give
the number of that day relative to the beginning of the simulation period,
where the first day is day 0. Therefore, to release a job from HELD status on
the second day of simulation, specify SIMDAY=1. If you do not use this
keyword, the job will be released from HELD status every day during the
simulation period.
STation=nn
Specify the station ID (integer from 1-99) for non-CPU stations.
Use the RELEASE Job command to release jobs placed in HELD status.
The RELEASE Job command must precede the SIMULATE command.
Jobs that are held are not placed in a partition to simulate their processing
until the RELEASE simulation command is issued against them.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
RELEASE J N=CUST1,
S=SALES,
SIMDAY=3
SIMULATE
/
/&
release a job
job is in this schedule
release it on 4th day
produce simulation reports
5-74 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7.12 RELEASE SCHEDULE
5.7.12.1 Keywords
The preceding example releases a job on the fourth day of the simulation
period.
RELEASE Schedule Name=sname Release one or more schedules from HELD
status.
Name=sname
AT=hhmm|ddhhmm
SImday=nn
5.7.12.2 Keyword Descriptions
5.7.12.3 Usage Notes
Name=sname
Specify the schedule (1- to 8-character schedule name) you want to release
from HELD status.
AT=hhmm|ddhhmm
Specify the time that the schedule is to be released from HELD status. Specify
hhmm in terms of a 24-hour clock. Use dd to indicate the number of autoscan
days in the future when the schedule is to be released. Do not use dd if the
schedule will be released today.
SImday=nn
Indicate what day of the simulation period to release the schedule from hold.
Give the number of that day relative to the beginning of the simulation period,
where the first day is day 0. Therefore, to release a schedule from HELD status
on the second day of simulation, specify SIMDAY=1. If you do not use this
keyword, the schedule will be released from HELD status every day during
the simulation period.
Use the RELEASE Schedule command to release one or more schedules from
HELD status. It must precede the SIMULATE command.
Jobs in a held schedule are not placed in a partition to simulate their
processing until the RELEASE simulation command is issued against them.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
Chapter 5. Reports 5-75

5.7 Simulation Commands
5.7.12.4 Example
5.7.13 REQUEST Job
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
RELEASE S N=PAYROLL,
AT=17,
SIMDAY=3
SIMULATE
/
/&
release a schedule
at 5: p.m.
release it on 4th day
produce simulation reports
The preceding example releases a schedule from HELD status at 5:00 p.m. on
the fourth day of the simulation period.
REQUEST Job Name=jname
Request one or more jobs and their respective
successors.
5.7.13.1 Keywords
Name=jname
AT=hhmm|ddhhmm
JNo=nn
Schedule=sname
SImday=nn
STation=nn
5.7.13.2 Keyword Descriptions
Name=jname
Specify the job (1- to 8-character job name) you want to move to the ACTIVE
queue. To request a group of jobs, use the asterisk (*) or question mark (?)
mask characters.
AT=hhmm|ddhhmm
Specify the time that the job is to be moved to the ACTIVE queue. Specify
hhmm in terms of a 24-hour clock. Use dd to indicate the number of autoscan
days in the future when this is to occur. Do not use dd if the job will be
moved to the ACTIVE queue today.
JNo=nn
Specify the job number (an integer from 1-99) if you want to activate a
particular occurrence of a job.
5-76 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7.13.3 Usage Notes
5.7.13.4 Example
Schedule=sname
Specify the schedule name (1-8 characters) if the job has been defined in more
than one schedule. If this is not specified, Unicenter CA-Scheduler will activate
the first job it finds with the specified job name (if the schedule that the job
belongs to is active).
SImday=nn
Indicate what day of the simulation period to activate the job. Give the
number of that day relative to the beginning of the simulation period, where
the first day is day 0. Therefore, to activate a job on the second day of
simulation, specify SIMDAY=1. If you do not use this keyword, the job will be
activated every day during the simulation period.
STation=nn
Specify the station ID (integer from 1-99) for non-CPU stations.
Use the REQUEST Job command to request one or more jobs and their
respective successors. Use this command only if the schedule that contains the
job is active.
The REQUEST Job command must precede the SIMULATE command.
Specify the schedule name if the job is assigned to more than one schedule.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REQUEST J N=NOTTODAY,
S=SALES,
SIMDAY=1
SIMULATE
/
/&
activate a job
job is in this schedule
activate it on 2nd day
produce simulation reports
The preceding example activates a job in the SALES schedule on the second
day of the simulation period. Note that the SALES schedule must be scheduled
that day for one of its jobs to be activated.
Chapter 5. Reports 5-77

5.7 Simulation Commands
5.7.14 REQUEST Schedule
5.7.14.1 Keywords
REQUEST Schedule Name=sname Request one or more schedules and their
respective successors.
Name=sname
AT=hhmm|ddhhmm
SImday=nn
5.7.14.2 Keyword Descriptions
5.7.14.3 Usage Notes
Name=sname
Specify the schedule (1- to 8-character schedule name) you want to move to
the ACTIVE queue. To request a group of schedules, use the asterisk (*) or
question mark (?) mask characters.
AT=hhmm|ddhhmm
Specify the time that the job or schedule is to be moved to the ACTIVE queue.
Specify hhmm in terms of a 24-hour clock. Use dd to indicate the number of
autoscan days in the future when this is to occur. Do not use dd if the job or
schedule will be moved to the ACTIVE queue today.
SImday=nn
Indicate what day of the simulation period to activate the job or schedule.
Give the number of that day relative to the beginning of the simulation period,
where the first day is day 0. Therefore, to activate a job on the second day of
simulation, specify SIMDAY=1. If you do not use this keyword, the job or
schedule will be activated every day during the simulation period.
Use the REQUEST Schedule command to request one or more schedules and
their succesors. The REQUEST Schedule command must precede the
SIMULATE command.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
5-78 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7.14.4 Example
5.7.15 RERUN Job
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REQUEST S N=RUNONREQ,
AT=12
SIMULATE
/
/&
activate a schedule
at noon
produce simulation reports
The preceding example activates a schedule that has been defined with the
REQUESTED criteria. These schedules are selected every day but are kept in
the INACTIVE queue until a REQUEST command moves them to the ACTIVE
queue.
RERUN Job Name=jname
Rerun one or more abended, failed, or
interrupted jobs during a revised simulation.
5.7.15.1 Keywords
Name=jname
AT=hhmm|ddhhmm
JNo=nn
Schedule=sname
SImday=nn
5.7.15.2 Keyword Descriptions
Name=jname
Specify the job (1- to 8-character job name) you want to rerun. To rerun a
group of jobs, use the asterisk(*) or question mark (?) to mask characters.
AT=hhmm|ddhhmm
Specify the time that the job is to be rerun. Specify hhmm in terms of a
24-hour clock. Use dd to indicate the number of autoscan days in the future
when the job is to be rerun. Do not use dd if the job will be rerun today.
JNo=nn
Specify the job number (an integer from 1-99) if you want to rerun a particular
occurrence of a job. To rerun a group of jobs, use the asterisk (*) or question
mark (?) mask characters.
Chapter 5. Reports 5-79

5.7 Simulation Commands
5.7.15.3 Usage Notes
5.7.15.4 Example
Schedule=sname
Specify the schedule name (1-8 characters) if the job has been defined in more
than one schedule. If this is not specified, Unicenter CA-Scheduler will rerun
the first job it finds with the specified job name.
SImday=nn
Indicate what day of the simulation period to rerun the job. Give the number
of that day relative to the beginning of the simulation period, where the first
day is day 0. Therefore, to rerun a job on the second day of simulation, specify
SIMDAY=1. If you do not use this keyword, the job will be rerun every day
during the simulation period.
Use the RERUN command to rerun a job during a revised simulation. This job
has either currently abended, failed, or been interrupted by the Unicenter
CA-Scheduler Monitor.
This RERUN Job command must precede the SIMULATE command with the
REVISE keyword.
Abended, failed, and interrupted jobs are not placed in a partition to simulate
their processing until a RERUN simulation command is issued against them.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
RERUN J N=CUST1,
S=SALES
SIMULATE REVISE=YES
/
/&
rerun a job
job is in this schedule
produce revised simulation reports
The preceding example simulates the rerun of a job that abended when it was
run during the original simulation. The job will be rerun as soon as the revised
simulation command is issued.
5-80 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7.16 RONLY Schedule
5.7.16.1 Keywords
RONLY Schedule Name=sname Limit the Simulated Execution Schedule
(SIMEXEC) report to one or more schedules.
Name=sname
SImday=nn
5.7.16.2 Keyword Descriptions
5.7.16.3 Usage Notes
Name=sname
Specify the schedule (1- to 8-character schedule name) to be included in the
Simulated Execution Schedule (SIMEXEC) report. To include a group of
schedules, use the asterisk (*) or question mark (?) mask characters.
SImday=nn
Indicate what day of the simulation period to process this command. Give the
number of that day relative to the beginning of the simulation period, where
the first day is day 0. Therefore, to process the command only on the second
day of simulation, specify SIMDAY=1. If you do not use this keyword, the
command will be processed every day during the simulation period.
Use the RONLY Schedule command to limit the Simulated Execution Schedule
report to one or more schedules. This command must precede the SIMULATE
command.
Use the RONLY Schedule command to limit the schedules that are included in
the Simulated Execution Schedule (SIMEXEC) report. Although the report is
limited, the entire workload is still used during simulation processing. This
command is useful when the workload is closely interdependent across
schedules (for example, when many schedules or jobs are predecessors for
other schedules). In that case, you would ordinarily need to simulate more
schedules than you were interested in to obtain accurate simulation results.
Instead, however, you can use the RONLY Schedule command to list only
those schedules you want to see.
Other simulation reports are not affected by this command.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
Chapter 5. Reports 5-81

5.7 Simulation Commands
5.7.16.4 Example
5.7.17 RUN Job
// job CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
RONLY S N=ACCT
RONLY S N=MANU
SIMULATE
/
/&
list the accounting schedules only
list the manufacturing schedules only
perform the simulation
The preceding example limits the Simulated Execution Schedule (SIMEXEC)
report to schedules beginning with ACCT and MANU.
RUN Job Name=jname
Include one or more jobs that are not
normally selected today.
5.7.17.1 Keywords
Name=jname
AT=hhmm|ddhhmm
Jno=nn
Schedule=sname
SImday=nn
STation=nn
5.7.17.2 Keyword Descriptions
Name=jname
Specify the job (1- to 8-character job name) you want to include. If you want
to include more than one job, use the asterisk (*) or question mark (?) mask
characters.
AT=hhmm|ddhhmm
Specify the time that the job is to start. Specify hhmm in terms of a 24-hour
clock. Use dd to indicate the number of autoscan days in the future when the
job is to be included. Do not use dd if the job will be included today.
JNo=nn
Specify the job number (an integer from 1-99) if you want to include a
particular occurrence of a job.
Schedule=sname
Specify the schedule name (1-8 characters) if the job has been defined in more
than one schedule. If this is not specified, Unicenter CA-Scheduler will include
5-82 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7.17.3 Usage Notes
5.7.17.4 Example
the first job it finds with the specified job name (if the schedule that the job
belongs to is active).
SImday=nn
Indicate what day of the simulation period to include the job. Give the
number of that day relative to the beginning of the simulation period, where
the first day is day 0. Therefore, to include a job on the second day of
simulation, specify SIMDAY=1. If you do not use this keyword, the job will be
included every day during the simulation period.
STation=nn
Specify the station ID (integer from 1-99) for non-CPU stations.
Use the RUN Job command to include one or more jobs that are not normally
selected today. Use this command only if the schedule that contains the job is
active: it must either be selected today or added using a RUN Schedule
command.
The RUN Schedule command must precede the SIMULATE command.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
RUN J N=CUST1,
S=SALES,
SIMDAY=1
SIMULATE
/
/&
add a job
job is in this schedule
add it only on 2nd day
produce simulation reports
The preceding example adds a job that is not normally selected today,
although it is part of a schedule that is normally selected. The job is to be
added to the schedule only on the second day of the simulation period.
Chapter 5. Reports 5-83

5.7 Simulation Commands
5.7.18 RUN Schedule
RUN Schedule Name=sname
Include one or more schedules that are not
normally selected today.
5.7.18.1 Keywords
Name=sname
AT=hhmm|ddhhmm
SImday=nn
5.7.18.2 Keyword Descriptions
5.7.18.3 Usage Notes
Name=sname
Specify the schedule (1- to 8-character schedule name) you want to include. If
you want to include more than one schedule, use the asterisk (*) or question
mark (?) mask characters.
AT=hhmm|ddhhmm
Specify the time that the schedule is to start. Specify hhmm in terms of a
24-hour clock. Use dd to indicate the number of autoscan days in the future
when the schedule is to be included. Do not use dd if the schedule will be
included today.
SImday=nn
Indicate what day of the simulation period to include the schedule. Give the
number of that day relative to the beginning of the simulation period, where
the first day is day 0. Therefore, to include a schedule on the second day of
simulation, specify SIMDAY=1. If you do not use this keyword, the schedule
will be included every day during the simulation period.
Use the RUN Schedule command to include one or more schedules that are
not normally selected today. This command must precede the SIMULATE
command.
JCL that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
5-84 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7.18.4 Example
5.7.19 SIMULATE
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
RUN S N=PAYROLL,
AT=12
SIMULATE
/
/&
add a schedule
start it at noon
produce simulation reports
The preceding example adds a schedule that is not normally selected today.
The schedule is to start at noon.
SIMULATE
Select jobs and schedules in simulation mode, and produce
reports showing where and when they would be processed.
5.7.19.1 Optional Object
5.7.19.2 Keywords
TAPEPULL
You can specify this optional object to produce a sequential file (the JNI file)
that will be accessed later to provide a list of tapes needed for the simulated
jobs if you have either BrightStor CA-Dynam/T or CA-Tape Manager installed.
See the topic Usage Notes that follows for more information.
Cpushut=yes
EVeryday=NO|YES
EXCrept=(reportid1,reportid2,...)
FOR=nn
FromDate=AUTOS|TODAY|mmddyy|ddmmyy
FromTime=hhmm
INCrept=(reportid1,reportid2,...)
INTerval=hhmm|mm
MAXtime=hhmm|ddhhmm
MONthof=mmyy
Revise=yes
RFT=hhmm|ddhhmm
RTT=hhmm|ddhhmm
STation=(nn,...)
Traceopt=(dump1,...dump5)
UPDATE=YES|NO
Chapter 5. Reports 5-85

5.7 Simulation Commands
5.7.19.3 Keyword Descriptions
Cpushut=yes
Use this keyword if you want the CPU station to stop jobs at Production End
Time (PET), and restart them at Production Start Time (PST).
EVeryday=NO|YES
Use this keyword only in conjunction with the RFT and RTT keywords.
Specify YES to cause the RFT (report from time) and RTT (report to time)
keywords to be applied to every day of the simulation period. Specify NO to
cause the RFT and RTT keyword to be applied to only the first day of the
simulation period. NO is the default.
EXCrept=(reportid1,reportid2,...)
List the reports that you do not want printed as part of this simulation run. If
you do not use this keyword, all reports are printed except the Tracking File
Job Errors report that is only generated when you specify REVISE=YES.
To Exclude This Report
Date Translation Report
Schedules/Job Selected For All Jobs
Simulated
Execution Schedule
Unit Utilization
Device Utilization
Shared Device Utilization
Backlogged Schedules/Jobs
Late Job Profile
Tracking File Job Start Errors
Specify
DATETRAN
SELECTED
SIMEXEC
UNITUTIL
DEVUTIL
DEVUTIL
BACKLOG
LATEJOBS
EXPERROR
FOR=nn
Specify the number of days that you want simulated selecting and scheduling.
Unicenter CA-Scheduler will begin selecting jobs and schedules that are
supposed to be processed on the date specified by FROMDATE and will
continue selecting jobs and schedules that are to be processed on the next day,
and the day after that, and so on, until it covers the number of days specified
here. If FOR is not specified, Unicenter CA-Scheduler will select jobs and
schedules only for one day.
5-86 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
FromDate=AUTOS|TODAY|mmddyy|ddmmyy
Give the date when you want simulation to begin:
AUTOS
TODAY
mmddyy|
FromTime=hhmm
Start simulation on the date the database was scanned. This
ignores the actual system date, which changes at midnight. This
is the default and need not be specified.
Start simulation today, according to the system date. If it is after
midnight, this may be a day later than the autoscan date, which
does not change at midnight. (If autoscan takes place at
midnight, FD=AUTOS and FD=TODAY are the same.)
Start simulation on this date. For example, if you specify
FD=120103, ddmmyy Unicenter CA-Scheduler selects jobs and
schedules that are to be processed on December 1, 2003. Specify
the date as mmddyy or ddmmyy, whichever is the standard date
format used at your installation. The simulation will start at
AUTOTIM on this date, unless overridden by FROMTIME.
Give the time that you want simulation to begin. If no time is specified,
simulation will begin when the database is scanned at AUTOTIM on the date
specified by FD. However, if you specify FT=1200 Unicenter CA-Scheduler
will begin selecting schedules and jobs at noon instead of at AUTOTIM when
selection is normally done, and the simulation reports will begin at noon.
INCrept=(reportid1,reportid2...)
Print one or more forecast reports in addition to the simulation reports.
To Include This Report
Job Summary
Schedules/Jobs Selected For Station X
Resources Required For Jobs At Station X
Run Book
Predecessors Required For Jobs At Station X
Route Station Report
Specify
SUMMARY
STATION
RESSTN
RUNBOOK
PREDS
ROUTESTN
INTerval=hhmm|mm
Specify the time interval on the DEVUTIL and UNITUTIL reports. For
example, if you specify INTERVAL=30, Unicenter CA-Scheduler will sample
device and unit utilization every 30 minutes, and the reports will the
utilization at this interval. The default interval is set at 15 minutes.
Chapter 5. Reports 5-87

5.7 Simulation Commands
MAXtime=hhmm|ddhhmm
Specify when to stop simulation. If you do not specify MAXTIME, simulation
will stop at the end of the last day in the simulation period. Specifying
MAXTIME allows you to stop simulation before the end of the day or let it
continue for additional days. Use hhmm to tell what time to stop simulation
on the first day of the simulation period. Use ddhhmm to tell what time to
stop simulation on the second day, third day, and so on. For example, to stop
simulation at 10:00 p.m. on the first day, specify MAXTIME=2200. To stop
simulation at 5:00 p.m. on the fifth day, specify MAXTIME=041700. Unicenter
CA-Scheduler will stop the simulated scheduling of jobs at his time on this day
even if all of the selected schedules and jobs have not been processed. Those
that have started but have not completed will show on the Late Job Profile At
End Of Simulation report as RUNNING or INCOMPLETE.
MONthof=mmyy
Specify a month (mm) or year(yy) other than the current month/year on the
Job Summary report. This option is valid only if INCREPT=SUMMARY is
specified, and does not affect simulation, only the Job Summary report. If not
specified, the current month and year will appear on the report.
Revise=yes
Get an up-to-date picture of how the real production is going and what work
remains to be done. This is useful if you are having system problems and
want to see how they affect the schedule. The Tracking File Job Start Errors
report is generated in addition to all of the regular simulation reports, which
will start at the time the SIMULATE command is issued. The information for
all of these reports is taken from the tracking file instead of form the database;
therefore it includes backlogged jobs from previous days and jobs that have
been added to the schedule using online commands. Completed jobs are
eliminated from the schedule. Start and end times on the Late Job Profile
report are revised. The Tracking File Job Errors report shows all of the jobs in
the tracking file that have either not started or started late. We recommend
that this report be run only when the Unicenter CA-Scheduler Monitor is shut
down.
RFT=hhmm|ddhhmm
Specify RFT=hhmm (report from time) in conjunction with RTT=hhmm (report
to time) to limit the reporting period for the Simulated Execution Schedule
(SIMEXEC) report. Specifying EVERYDAY=YES produces the Simulated
Execution Schedule report for every day of the simulation period. Specifying
EVERYDAY = NO limits the report to the first day of the simulation period.
Use the RFT=ddhhmm format to limit the report to a day other than the first
day of the simulation period. Other simulation reports are not affected by this
keyword.
5-88 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
RTT=hhmm|ddhhmm
Specify RTT=hhmm (report to time) in conjunction with RFT=hhmm (report
from time) to limit the reporting period for the Simulated Execution Schedule
(SIMEXEC) report. Specifying EVERYDAY=YES produces the Simulated
Execution Schedule report for every day of the simulation period. Specifying
EVERYDAY = NO limits the report to the first day of the simulation period.
Use the RTT=ddhhmm format to limit the report to a day other than the first
day of the simulation period. Other simulation reports are not affected by this
keyword.
STation=(nn,...)
Identify up to eight workstations for which simulation reports are to be
produced. If no STATION is specified, reports are produced for all defined
stations.
Traceopt=(dump1,...dump5)
Used only at the request of Computer Associates support personnel to
generate diagnostic dumps during a simulation run. List the names of the
dumps that you need:
To Trace
Events
Jobs as scheduled
Catalog I/O
Sort I/O
Internal tables on every update
Specify
EVENT
EXEC
CAMIO
SORTIO
TABLES
UPDATE=YES|NO
Turns the SIMTIME update on or off in Schedule/Job base records. Yes is the
default. To prevent the update, specify NO.
Chapter 5. Reports 5-89

5.7 Simulation Commands
5.7.19.4 Usage Notes
Use the SIMULATE command to select jobs and schedules in simulation mode,
and produce reports showing where and when they would be processed JCL
that produces simulation reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
In addition to all simulation reports, the SIMULATE command with the
TAPEPULL object produces a JNI file ( Job Network Information file). The JNI
file is a sequential data set that will be later accessed to produce a list of tapes
needed for the simulated jobs. (See also TAPEPULL GROUP command) The
JNI file contains a record for every job in the simulated execution order. These
records contain (among other things) information about the jobs' JCL and
where it resides. They also contain simulated values for variable parameters
that can be resolved by Unicenter CA-Driver at JCL validation time. (See the
chapter "Unicenter CA-Driver Procedures, Variable Parameters, and
Functions".) Only those jobs that appear on the Simulated Execution Schedule
(SIMEXEC) report will have matching records in the JNI file.
In addition to all other simulation reports, using the FROMDATE keyword
with the TAPEPULL object produces the JNI file for a future day, thus
providing a list of tapes for future work.
Using the REVISE=YES keyword value with the TAPEPULL object produces
the JNI file for the portion of the current workload not yet completed.
Held jobs in the current workload require a RELEASE JOB command run
against them in order for those jobs to be simulated and recorded in the JNI
file. Jobs that are currently in ABENDED, FAILED or INTRPTD status require
a RERUN Job command run against them in order for those jobs to be
simulated and recorded in the JNI file.
You can use the RFT=hhmm and RTT=hhmm keywords to limit the Simulated
Execution Schedule (SIMEXEC) report and the JNI file to those jobs that would
run in the specified period.
5-90 Unicenter CA-Scheduler Reference Guide, Part 2

5.7 Simulation Commands
5.7.19.5 Example
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
OVERRIDE RESOURCE SYSID=1,
change CPU 1 resources
DASD3=(339,1)
OVERRIDE RESOURCE SYSID=2,
change CPU 2 resources
DASD1=(338,1)
OVERRIDE RESOURCE ST=2,
change station 2 resources
UR1=(PCHKEYS,2)
OVERRIDE RESOURCE ST=2,
add keypunch operator SALLY
UNIT3=(ABC,SALLY)
to the keypunch station
OVERRIDE SHRRSR ST=4,EVERYDAY=YES, change resources shared by
OST=81,OET=1, CPU 1 and CPU 2 from 8:1
DASD1=(338,2,1,2)
to 1: every day
OVERRIDE SCHEDULE N=DAILY4,FACTOR=75 decrease processing time
OVERRIDE JOB N=SUNJOB1,SC=SUNDAY1, increase processing time
ST=4,FACTOR=125
EXCLUDE SCHEDULE N=EXCSCHD1
exclude a schedule
RUN Schedule N=SCHDA
add a schedule
RUN JOB N=JOBA,S=SCHDB
add a job
HOLD JOB N=JOBB
hold a job
RELEASE JOB N=JOBC
release a job
REQUEST SCHEDULE N=SCHDC
activate an "on-request" schedule
SIMULATE FD=9143,FT=1,FOR=2, begin selection on this date at
MAX=215,INTERV=2,
this time for 2 days and report
/
/&
STA=(2,3,4,5,6)
on these stations
Chapter 5. Reports 5-91

5.7 Simulation Commands
The preceding example illustrates how to run simulation with the OVERRIDE,
EXCLUDE, RUN, HOLD, RELEASE, and REQUEST commands. Note that
these commands are all coded before SIMULATE. The OVERRIDE
RESOURCE commands change the number of DASD devices dedicated to each
of the two CPUs, as well as the number of keypunch devices at station 20. In
addition, the new keypunch operator 'SALLY' has been added to the staff. The
OVERRIDE SHRRSR command changes the number of DASD devices shared
by the two CPUs for a two-hour period every day. The OVERRIDE
SCHEDULE command decreases one schedule's overall processing time while
the OVERRIDE JOB command increases one job's processing time at the CPU.
The SIMULATE command directs Unicenter CA-Scheduler to select all jobs
and schedules that would normally be processed on September 14th and 15th,
except for the EXCSCHD1 schedule. It also:
■
■
■
■
■
Adds a schedule that would not normally be selected
Adds a job that would not normally be selected, although the rest of its
schedule is selected
Holds a job that normally would be run
Releases a job that is in HELD status
Activates a schedule that was defined with REQUESTED criteria and is
selected every day in case it is needed
The simulation period is to start at 1:00 a.m. instead of at AUTOTIM and is to
continue until 3:00 p.m. on the third day instead of ending after two days of
processing. The SIMULATE command also directs Unicenter CA-Scheduler to
produce simulation reports for stations 20, 30, 40, 50, and 60, showing a
20-minute time interval on the utilization reports.
The reports generated from this command are shown in the section on
Simulation Reports.
5-92 Unicenter CA-Scheduler Reference Guide, Part 2

5.8 Simulation Reports
5.8 Simulation Reports
The reports generated by the SIMULATE command are illustrated on the
following pages, organized alphabetically by report title for easy reference. The
three-part report heading is illustrated following:
COMPUTER ASSOCIATES
CA-SCHEDULER 7.3 yymmSHvvn
The left-hand part of the heading identifies the product by vendor, name,
release number, and generation level. The generation level consists of the last
two digits of the year (yy), the month (mm), the product code (SH), the release
number (vv), and a number for internal use (n).
SIMULATED EXECUTION SCHEDULE FOR STATION 3
PRE-CPU STATION (VERIFY
The middle of the heading gives the report title. If the report is for a specific
station, the station ID or name is inserted on the first line, and the station title
is printed on the second line (id, name, and title are all taken from the station
definition).
SIMEXEC PAGE 1
14 SEP 23 11.13.5
SIMULATION DATE 14 SEP 23
The right-hand part of the heading begins with the report id. (Each report has
a 1- to 8-character report ID that can be specified on the EXCREPT keyword to
exclude the report from a simulation run or on the INCREPT keyword to
include the report in a forecast run.) The second line gives the date and time
the report is generated. The bottom line gives the date for which the events are
being simulated.
5.8.1 Backlogged Schedules/Jobs (BACKLOG)
The Backlogged Schedules/Jobs report lists all jobs that will probably not be
processed on the day they are selected and will have to be carried over to the
next day as backlog.
COMPUTER ASSOCIATES BACKLOGGED SCHEDULES/JOBS AT END OF SIMULATION BACKLOG PAGE 1
CA-SCHEDULER 7.3 39SH73
14 SEP 23 11.13.5
SIMULATION DATE 14 SEP 23
SCHEDULE ------JOB-----
NAME NAME NO ST EARLY TIME MUST TIME DEADLINE PREDECESSORS NOT SATISFIED WAITING FOR
-------- -------- -- -- -------------- -------------- -------------- ----------------------------- -------------
SCD3 JOB3B 1 4 JOB3A -1 4
SCD4 JOB4C 1 4 JOB4B -1 4
SCD4 JOB4B 1 4 9/15/3 8. START TIME
Chapter 5. Reports 5-93

5.8 Simulation Reports
The following information is given:
SCHEDULE NAME
JOB NAME
JOB NO
JOB ST
EARLY TIME
MUSTTIME
DEADLINE
The schedules that these jobs are assigned to.
These jobs will not have been started by production
end time on September 14, and therefore will be
carried over to the next day automatically.
Any number higher than 01 indicates that the backlog
job is the second or third time (or more) the job is
scheduled that day.
The stations where the job is scheduled for processing.
The job's EARLIEST START TIME will be taken from
the following records in the following order:
1. Job reason code record (JRC) if defined and there
is a matching nonzero early start time for the
selection reason.
2. Job base record (JBR) if early time is defined.
3. The job will start when the schedule it is in starts.
The job's MUST START BY TIME will be taken from
the following records in the following order:
1. Job reason code record (JRC) if defined and there
is a matching nonzero must time for the selection
reason.
2. Job base record (JBR) if must time is defined.
3. No must start by time is used.
The job's COMPLETION DEADLINE TIME is taken
from the following records in the following order:
1. Job reason code record (JRC) if defined and there
is a matching nonzero DEADLINE for the selection
reason.
2. Job base record (JBR) if DEADLINE is defined.
3. No deadline time is used.
PREDECESSORS NOT SATISFIED
The job cannot be processed today because these
predecessor conditions have not yet been satisfied.
WAITING FOR
The job cannot be processed today for one of these
reasons:
START TIME
The EARLY TIME has not yet been
reached.
5-94 Unicenter CA-Scheduler Reference Guide, Part 2

5.8 Simulation Reports
PREV-STN
RESOURCE
All of the predecessor conditions
have been satisfied except the
completion of this job at a previous
station.
All of the predecessor conditions
have been satisfied, but the job is
waiting for either a DASD volume to
be mounted, exclusive use of a data
set, mutually exclusive jobs to end,
or a partition/unit to have the
correct class availability. In a
multi-CPU environment, there must
be a resource record defined for the
CPU station for each SYSID.
In addition, if the job has BACKLOG=NO, the word PURGED will appear
following the WAITING FOR column. This indicates that the job has been
purged from the schedule.
5.8.2 Date Translation Report (DATETRAN)
The Date Translation report shows which Gregorian calendar dates, workdays,
holidays, and accounting periods are true for a specific date and datetable
combination. We recommend that you run this report to verify that the
selection criteria keywords you use in your schedule and job criteria
definitions are correct. In some cases, this report can be interpreted as showing
which selection criteria keywords are false. In either case, the values on this
report are always calculated based upon the combination of Gregorian
calendar conditions, a specific datetable definition, and the actual date the
report is run. When schedules and jobs do not use calendars for selection, this
report will show which selection criteria keywords they can use on a specific
day to be selected.
Chapter 5. Reports 5-95

5.8 Simulation Reports
COMPUTER ASSOCIATES DATE TRANSLATION REPORT DATETRAN PAGE 1
CA-SCHEDULER 7.3 39SHESA 4 SEP 23 15.53.49
SIMULATION DATE 8 SEP 23
JULIAN DATE=3251
GREGORIAN DATE=9/8/3
TABLE NAME=DATETAB
DAY OF WEEK=FRI WEEK-DAY=YES WEEK-END=NO MWF=YES TT=NO NTH DAY OF MONTH=FRI2 FRI-4 NEGATIVE DAY OF MONTH=DOM-23
WEEK OF MONTH=2ND-WEEK WEEK OF YEAR=WOY36 WOY-18 DAYS IN MONTH=3 LEAP-YEAR=NO
DAY1OF2=NO DAY2OF2=YES
DAY1OF3=NO DAY2OF3=NO DAY3OF3=YES
DAY1OF4=NO DAY2OF4=YES DAY3OF4=NO DAY4OF4=NO
DAY1OF5=NO DAY2OF5=NO DAY3OF5=NO DAY4OF5=NO DAY5OF5=YES
DAY1OF6=NO DAY2OF6=NO DAY3OF6=NO DAY4OF6=NO DAY5OF6=NO DAY6OF6=YES
WEEK1OF2=YES WEEK2OF2=NO
WEEK1OF3=YES WEEK2OF3=NO WEEK3OF3=NO
WEEK1OF4=YES WEEK2OF4=NO WEEK3OF4=NO WEEK4OF4=NO
WEEK1OF5=NO WEEK2OF5=NO WEEK3OF5=YES WEEK4OF5=NO WEEK5OF5=NO
WEEK1OF6=YES WEEK2OF6=NO WEEK3OF6=NO WEEK4OF6=NO WEEK5OF6=NO WEEK6OF6=NO
WORK-DAY=YES WORK DAY OF WEEK=WDOW5 WDOW-1 WORK DAY OF MONTH=WDOM6 WDOM-16 WORK DAY OF YEAR=18 -81
WORK WEEK OF MONTH=WWOM2 WWOM-4
WORK WEEK OF YEAR=WWOY36 WWOY-17
RD1=+5 -16 RD2=+5 -16 RD3=+5 -17 RD4=+4 -18 RD5=+3 -19 RD6=+2 -2 RD7=+1 -21 RD8=+ -
RD9=+22 -1 RD1=+21 -1 RD11=+2 -1 RD12=+2 -2 RD13=+2 -3 RD14=+19 -4 RD15=+18 -5 RD16=+17 -6
RD17=+16 -6 RD18=+15 -6 RD19=+15 -7 RD2=+15 -8 RD21=+14 -9 RD22=+13 -1 RD23=+12 -11 RD24=+11 -11
RD25=+1 -11 RD26=+1 -12 RD27=+1 -13 RD28=+9 -14 RD29=+8 -15 RD3=+7 -16 RD31=+6
HDAY=NO
HDAY-1=NO HDAY-2=NO HDAY-3=NO HDAY-4=NO HDAY-5=YES HDAY-6=YES HDAY-7=NO
HDAY1 =YES HDAY2 =YES HDAY3 =NO HDAY4 =NO HDAY5 =NO HDAY6 =NO HDAY7 =NO HDAY8 =YES HDAY9 =YES HDAY1=NO
HDAY11=NO HDAY12=NO HDAY13=NO HDAY14=NO HDAY15=YES HDAY16=YES HDAY17=NO HDAY18=NO HDAY19=NO HDAY2=NO
HDAY21=NO HDAY22=YES HDAY23=YES HDAY24=NO HDAY25=NO HDAY26=NO HDAY27=NO HDAY28=NO HDAY29=YES HDAY3=YES
HDAY31=NO
A-ACCOUNTING DAY=YES DAY OF MONTH=ADOM6 ADOM-16 DAY OF YEAR=18 -81 WEEK OF MONTH=AWOM2 AWOM-4 MONTH OF YEAR=AMOY9 AMOY-4
X-ACCOUNTING DAY=YES DAY OF MONTH=XDOM6 XDOM-16 DAY OF YEAR=18 -81 WEEK OF MONTH=XWOM2 XWOM-4 MONTH OF YEAR=XMOY9 XMOY-4
The Date Translation report will also display valid accounting day conditions
based upon the seven-byte datetable name. This means that all defined
variations (prefixes) of the named datetable will be analyzed at the end of the
report.
The following information is included on the Date Translation Report:
JULIAN DATE
TABLE NAME
The first two digits are the year. The last three digits
are the day of year, from 001 to 366.
The name of the datetable that was used to determine
which days are workdays, which days are accounting
days, when the periods end, and when the accounting
year ends. (Calendar conditions, like the fifth week of
the year, remain the same regardless of which
datetable is referenced.) The datetable name was
either specified on the schedule definition or taken
from the DATETABL option in the CAIJGEN macro,
which specifies a default datetable for schedules that
do not define one.
5-96 Unicenter CA-Scheduler Reference Guide, Part 2

5.8 Simulation Reports
GREGORIAN DATE
DAY OF WEEK...
The date in American format mm/dd/yy or European
format dd/mm/yy. The format depends on the
DATETYPE installation option.
The next three lines indicate whether a number of
calendar conditions from the criteria vocabulary are
true on this date: (Refer to the sample report.)
Schedules And Jobs Whose Selection Criteria Is Will Be True Will Be False
FRI (Friday) x
WEEK-DAY (a weekday) x
WEEK-END (a weekend day) x
MWF (Monday, Wednesday, or Friday) x
TT (Tuesday or Thursday) x
FRI2 (2nd Friday of the month) x
FRI-4 (3rd from last Friday of the month) x
DOM-23 (22nd to last day of the month) x
LEAP-YEAR (is it a leap year) x
2ND-WEEK (2nd week of the month) x
WOY36 (37th week of the year) x
WOY-18 (17th-to-last week of the year) x
Chapter 5. Reports 5-97

5.8 Simulation Reports
DAY1OF2...
The next five lines indicate which 1- to 6-day cyclic
conditions are true for the report date.
Schedules And Jobs Whose Selection Criteria Is
Will Be
True
Will Be
False
DAY1OF2 (day 1 in a 2-day cycle) x
DAY2OF2 (day 2 in a 2-day cycle) x
DAY1OF3 (day 1 in a 3-day cycle) x
DAY2OF3 (day 2 in a 3-day cycle) x
DAY3OF3 (day 3 in a 3-day cycle) x
DAY1OF4 (day 1 in a 4-day cycle) x
DAY2OF4 (day 2 in a 4-day cycle) x
DAY3OF4 (day 3 in a 4-day cycle) x
DAY4OF4 (day 4 in a 4-day cycle) x
DAY1OF5 (day 1 in a 5-day cycle) x
DAY2OF5 (day 2 in a 5-day cycle) x
DAY3OF5 (day 3 in a 5-day cycle) x
DAY4OF5 (day 4 in a 5-day cycle) x
DAY5OF5 (day 5 in a 5-day cycle) x
DAY1OF6 (day 1 in a 6-day cycle) x
DAY2OF6 (day 2 in a 6-day cycle) x
DAY3OF6 (day 3 in a 6-day cycle) x
DAY4OF6 (day 4 in a 6-day cycle) x
DAY5OF6 (day 5 in a 6-day cycle) x
DAY6OF6 (day 6 in a 6-day cycle) x
5-98 Unicenter CA-Scheduler Reference Guide, Part 2

5.8 Simulation Reports
WEEK1OF2...
The next five lines indicate which 1- to 6-week cyclic
conditions are true for the report date.
Schedules And Jobs Whose Selection Criteria
Is
Will Be
True
WEEK1OF2 (week 1 in a 2-week cycle) x
Will Be
False
WEEK2OF2 (week 2 in a 2-week cycle) x
WEEK1OF3 (week 1 in a 3-week cycle) x
WEEK2OF3 (week 2 in a 3-week cycle) x
WEEK3OF3 (week 3 in a 3-week cycle) x
WEEK1OF4 (week 1 in a 4-week cycle) x
WEEK2OF4 (week 2 in a 4-week cycle) x
WEEK3OF4 (week 3 in a 4-week cycle) x
WEEK4OF4 (week 4 in a 4-week cycle) x
WEEK1OF5 (week 1 in a 5-week cycle) x
WEEK2OF5 (week 2 in a 5-week cycle) x
WEEK3OF5 (week 3 in a 5-week cycle) x
WEEK4OF5 (week 4 in a 5-week cycle) x
WEEK5OF5 (week 5 in a 5-week cycle) x
WEEK1OF6 (week 1 in a 6-week cycle) x
WEEK2OF6 (week 2 in a 6-week cycle) x
WEEK3OF6 (week 3 in a 6-week cycle) x
WEEK4OF6 (week 4 in a 6-week cycle) x
WEEK5OF6 (week 5 in a 6-week cycle) x
WEEK6OF6 (week 6 in a 6-week cycle) x
Chapter 5. Reports 5-99

5.8 Simulation Reports
WORK-DAY=...
The next three lines indicate that workday conditions are
satisfied on this date:
This Field
WORK-DAY=YES
WDOW5
WDOW-1
WDOM6
WDOM-16
WWOM2
WWOM-4
WWOY36
WWOY-17
Means Today Is
A workday
The 5th workday of the week
The last workday of the week
The 6th workday of the month
The 15th-to-last workday of the month
The 2nd work week of the month
The 3rd-to-last work week of the month
The 36th work week of the year
The 16th-to-last work week of the year
Any schedules defined with one of these criteria: WDOW5,
WDOW-1, WDOM6, WDOM-16, etc., would be selected
today.
RD01=...
The next four lines indicate relative workday conditions
that are satisfied on this date:
This Field
RD01=+05 -16
RD11=+20 -01
RD21=+14 -09
Means Today Is
5 workdays after and 16 workdays before the 1st of
the month
20 workdays after and 1 workday before the 11th
of the month
14 workdays after and 9 workdays before the 21st
of the month
Any schedules or jobs defined with one of these criteria:
RD01=+05, RD01=-16, RD11=+20, RD11=-01, etc., would be
selected today if this were the only selection criteria. For
example, the relative workday criteria allows you to
schedule your payroll jobs 2 workdays before the 28th of
the month (RD28=-13). These jobs or schedules will be
selected (if this is the only selection criteria) on a workday
every month even if the 25th, 26th, and 27th are all
holidays or weekend days.
HOLIDAY=...
The next six lines indicate nonworkday conditions
(holidays and weekends) that are satisfied on this date:
5-100 Unicenter CA-Scheduler Reference Guide, Part 2

5.8 Simulation Reports
Schedules And Jobs Whose Selection
Criteria Is
Will Be True
Will Be False
HDAY (nonworkday) x
HDAY-1 (1 day after a nonworkday) x
HDAY-2 (2 days after a nonworkday) x
HDAY-3 (3 days after a nonworkday) x
HDAY-4 (4 days after a nonworkday) x
HDAY-5 (5 days after a nonworkday) x
HDAY-6 (6 days after a nonworkday) x
HDAY-7 (7 days after a nonworkday) x
HDAY1 (1 day before a nonworkday) x
HDAY2 (2 days before a nonworkday) x
HDAY3 (3 days before a nonworkday) x
HDAY4 (4 days before a nonworkday) x
HDAY5 (5 days before a nonworkday) x
HDAY6 (6 days before a nonworkday) x
HDAY7 (7 days before a nonworkday) x
HDAY8 (8 days before a nonworkday) x
HDAY9 (9 days before a nonworkday) x
HDAY10 (10 days before a nonworkday) x
HDAY11 (11 days before a nonworkday) x
HDAY12 (12 days before a nonworkday) x
HDAY13 (13 days before a nonworkday) x
HDAY14 (14 days before a nonworkday) x
HDAY15 (15 days before a nonworkday) x
HDAY16 (16 days before a nonworkday) x
HDAY17 (17 days before a nonworkday) x
HDAY18 (18 days before a nonworkday) x
HDAY19 (19 days before a nonworkday) x
HDAY20 (20 days before a nonworkday) x
HDAY21 (21 days before a nonworkday) x
HDAY22 (22 days before a nonworkday) x
HDAY23 (23 days before a nonworkday) x
Chapter 5. Reports 5-101

5.8 Simulation Reports
Schedules And Jobs Whose Selection
Criteria Is
Will Be True
Will Be False
HDAY24 (24 days before a nonworkday) x
HDAY25 (25 days before a nonworkday) x
HDAY26 (26 days before a nonworkday) x
HDAY27 (27 days before a nonworkday) x
HDAY28 (28 days before a nonworkday) x
HDAY29 (29 days before a nonworkday) x
HDAY30 (30 days before a nonworkday) x
HDAY31 (31 days before a nonworkday) x
ACCOUNTING
DAY...
The last two lines indicate which accounting conditions are
true on this date.
This Field
ADAY
ADOM6
ADOM-16
AWOM2
AWOM-4
AMOY9
AMOY-4
XDOM5
XDOM-16
XWOM2
XWOM-4
XMOY9
XMOY-4
Means Today Is
An accounting day
The 6th accounting day of the month
The 15th-to-last accounting day of the month
The 2nd accounting week of the month
The 3rd-to-last accounting week of the month
The 9th accounting month of the year
The 3rd-to-last accounting month of the year.
The 5th accounting day of the month
The 15th-to-last accounting day of the month
The 2nd accounting week of the month
The 3rd-to-last accounting week of the month
The 9th accounting month of the year
The 3rd-to-last accounting month of the year.
The values for ADOM6, ADOM-16, AWOM2, AWOM-4, AMOY9, AMOY-4,
and ADAY are determined from the datetable defined with the 'A' prefix.
The values for XDOM5, XDOM-16, XWOM2, XWOM-4, XMOY9, XMOY-4, and
XDAY are determined from the datetable defined with the 'X' prefix.
5-102 Unicenter CA-Scheduler Reference Guide, Part 2

5.8 Simulation Reports
5.8.3 Late Job Profile (LATEJOBS)
The Late Job Profile report lists all jobs that will start or end late.
COMPUTER ASSOCIATES LATE JOB PROFILE AT END OF SIMULATION LATEJOBS PAGE 1
CA-SCHEDULER 7.3 39SH73
14 SEP 23 11.13.5
SIMULATION DATE 14 SEP 23
SCHEDULE ------JOB----- LATE LATE AVAILABLE
NAME NAME NO ST START END STATUS EARLY TIME TIME MUST TIME START TIME DEADLINE END TIME WAITING FOR
-------- -------- -- -- ----- ---- ---------- ----------- ----------- ----------- ----------- ----------- ----------- ---------
SCD2 JOB2A 1 4 YES YES COMPLETE 9/14 8. 9/14 9.15 9/14 8. 9/14 9.15 9/14 1. 9/14 1.3
The following information is given:
SCHEDULE NAME
JOB NAME
JOB NO
JOB ST
LATE START
LATE END
STATUS
The schedules that these jobs are assigned to.
The jobs that will either start or end late.
Any number higher than 01 indicates that the job is
scheduled more than once.
The stations where the job is scheduled for processing.
YES in this column means the job will start after its
MUST START BY TIME.
YES in this column means the job will end after its
COMPLETION DEADLINE TIME.
The job's status at the end of the day will be:
COMPLETE
INCOMPLETE
RUNNING
NOT STARTED
Even though the job was late, it
completed today and will not have
to be carried over to tomorrow in
backlog. Since it is complete, its
record will be purged at the end of
day.
The job will not be completed at a
non-CPU station by the end of the
day. It will have to be completed
tomorrow. It will not be carried
over in backlog along with the
unprocessed jobs because it
already started.
The job will still be running on the
CPU at the end of the day. It will
continue running to completion.
This job has not started yet. It will
be carried over to tomorrow if
BACKLOG=YES was specified in
its job definition.
Chapter 5. Reports 5-103

5.8 Simulation Reports
EARLY TIME
AVAILABLE TIME
MUSTTIME
START TIME
DEADLINE
END TIME
WAITING FOR
The job's EARLIEST START TIME will be taken from the
following records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero early start time for the selection
reason.
2. Job base record (JBR) if early time is defined.
3. The job will start when the schedule it is in starts.
The time the job will be available to start, which means
that its early start time is reached and all predecessor
conditions are satisfied. The reasons in the last column
indicate that most of these jobs will not become available
until after their MUST START BY TIMES, because they
are waiting to complete at a previous station.
The job's MUST START BY TIME will be taken from the
following records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero must time for the selection
reason.
2. Job base record (JBR) if must time is defined.
3. No must start by time is used.
The time the job will actually start. If this time is after
the MUST TIME in the previous column, the job will
start late.
The job's COMPLETION DEADLINE TIME is taken from
the following records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero DEADLINE for the selection
reason.
2. Job base record (JBR) if DEADLINE is defined.
3. No deadline time is used.
The time the job will actually end. If this time is after the
DEADLINE value in the previous column, the job will
end late.
The reason the job will start or end late:
PRED
PREV-STN
One of the predecessor conditions will
not be satisfied.
All of the predecessor conditions will be
satisfied except the completion of this
job at a previous station.
5-104 Unicenter CA-Scheduler Reference Guide, Part 2

5.8 Simulation Reports
RESOURCE
SCD-START
All of the predecessor conditions will be
satisfied, but the job is waiting for a
DASD volume to be mounted, a data set
to be closed, or mutually exclusive jobs
to end.
The job is waiting for the Schedule Start
time to be reached.
If no status was specified for this field,
it indicates that the job was waiting for
an initiator/unit to be free. This can be
caused by incorrect PST/PET or class
definition, or insufficient partitions or
units defined with the correct classes.
5.8.4 Resources Required for All Selected Jobs (RESALL)
The Resources Required for All Selected Jobs (RESALL) report lists the
resources required to process the jobs that will be selected on a given date.
Only jobs with defined job resource records are listed.
COMPUTER ASSOCIATES RESOURCES REQUIRED FOR ALL SELECTED JOBS RESALL PAGE 1
CA-SCHEDULER 7.3 39SH73 29 SEP 23 13.35.39
FORECAST DATE 29 SEP 23
SCHEDULE ------JOB-----
----DASD--- ----TAPE--- -----UR----
NAME NAME NO ST DISK EXCP TAPE EXCP OTHER EXCP SEPARATE JOBS TYPE NO TYPE NO TYPE NO
-------- -------- -- -- ----------- ----------- ----------- ------------------------------- ----------- ----------- -----------
DSNABC DSNABC 1 4 1,111 2,222 3,333 CAJDEM3 338 2 348 2 143 4
9345 2
ABATCH AB 1 4 3,333 4,444 5,555 IEBDG 339 78 349 3 254 3
Chapter 5. Reports 5-105

5.8 Simulation Reports
The following information is given:
SCHEDULE NAME
JOB NAME
JOB NO
JOB ST
DISK EXCP
TAPE EXCP
OTHER EXCP
The schedules that the jobs are assigned to.
The jobs with defined resource records that will be
selected.
The selected job number.
The stations where the job will be processed.
The number of disk device I/Os required by each job,
as defined by DASD EXCPS on the job resource record.
(See Note.)
The number of tape device I/Os required by each job,
as defined by TAPE EXCPS on the job resource record.
(See Note.)
The number of unit device I/Os required by each job,
as defined by UNIT EXCPS on the job resource record.
(See Note.)
SEPARATE JOBS/DSNS
The list of jobs that cannot run at the same time as this
job, as defined by SEPARATE JOBS LIST on the job
resource record; or, a DSN that cannot be used by more
than one job at a time, as defined by SEPARATE DSN
on the job resource record.
DASD TYPE
DASD NO
TAPE TYPE
TAPE NO
UR TYPE
UR NO
The types of direct access devices each job requires, as
defined by DASD01 through DASD04 on the job
resource record.
How many of each type of direct access device each job
requires, as defined by DASD01 through DASD04 on
the job resource record.
The types of tape devices each job requires, as defined
by TAPE01 through TAPE04 on the job resource record.
How many of each type of tape device each job
requires, as defined by TAPE01 through TAPE04 on the
job resource record.
The types of unit record devices each job requires, as
defined by UNIT01 through UNIT04 on the job resource
record.
How many of each type of unit record device each job
requires, as defined by UNIT01 through UNIT04 on the
job resource record.
Note: If EXCPs are not defined on the job resource record, the information is
obtained from the job history records, which are updated by
$JOBAACT data.
5-106 Unicenter CA-Scheduler Reference Guide, Part 2

5.8 Simulation Reports
5.8.5 Schedules/Jobs Selected for DD MM YY (SELECTED)
The Schedules/Jobs Selected for DD MM YY (SELECTED) report lists all
schedules and jobs that will be selected on a given date.
COMPUTER ASSOCIATES SCHEDULES/JOBS SELECTED FOR 14 SEP 23 SELECTED PAGE 1
CA-SCHEDULER 7.3 39SH73 14 SEP 23 13.35.39
FORECAST DATE 14 SEP 23
SCHEDULE ------JOB----- SYSID/ REASON AVERAGE ROUTING TRACK
NAME NAME NO ST SUBID CODE EARLY TIME MUST TIME DEADLINE MAXTIME TIME DELAY TIME CLASS FILE STUS
-------- -------- -- -- ------ ------ -------------- -------------- -------------- -------- -------- ---------- ----- ----- ---
DSNABC 88 9/14/3 8. 9/14/3 9. 9/14/3 1. .1
DJKBR14 1 4 9/14/3 9.15 9/14/3 1.15 9/14/3 11.15 .3 .1 B
DSNABC 1 4 1 9/14/3 1. 9/14/3 11. 9/14/3 12. 1. .35 .3 B
ABATCH 1 88 9/14/3 8.1 9/14/3 1.1 1.1
ABATCH 2 39 1 9/14/3 21.21 9/14/3 22.25 9/14/3 23.23 .3 12.34 X
DSNABC 1 4 .1 C
AB 1 4 2 8 9/14/3 21.21 9/14/3 22.25 9/14/3 23.23 .3 12.34 .13 X
The following information is given:
SCHEDULE NAME
JOB NAME
JOB NO
The schedules that will be selected for processing on
this date.
The individual jobs that will be selected as part of
these schedules. (A job with its own criteria record
may be selected less frequently than the rest of the
schedule.)
Any number higher than 01 indicates that the job is
supposed to run more than once as part of this
schedule. (A separate job base record has been
defined for each occurrence.)
JOB ST The stations where the job will be processed. (A
separate job base record has been defined for the job
at each of these stations.)
SYSID/SUBID
REASON CODE
The SYSID or SUBID if one was defined.
This tells why each schedule or job will be selected:
01 - 79 Corresponds to the position of the reason on
the CRITERIA statement that was defined for
this job or schedule.
80 Means it will be selected because the date
corresponds to a workday on the
CALENDAR that was defined for this job or
schedule.
84 Means it is selected by default every day
because no selection criteria were defined.
88 Means that it was added to the simulation
run by the RUN command.
Chapter 5. Reports 5-107

5.8 Simulation Reports
EARLY TIME
MUST TIME
DEADLINE
The schedule's or job's EARLIEST START TIME. The
schedule's earliest start time is taken from the
following records in the following order:
1. Schedule reason code record (SRC), if defined and
there is a matching nonzero EARLYTIME defined
for the selection reason.
2. Schedule base record (SBR), if there is a nonzero
EARLYTIME defined
3. The schedule will be able to start just after
autoscan.
The job's earliest start time is taken from the following
records in the following order:
1. Job reason code record (JRC), if defined and there
is a matching nonzero EARLY START TIME for
the selection reason.
2. Job base record (JBR) if EARLYTIME is defined.
3. The job will start when the schedule that it is in
starts.
The schedule's or job's must start time, if one was
defined. The schedule's must start time is taken from
the following records in the following order:
1. Schedule reason code record (SRC), if defined and
there is a matching nonzero MUSTTIME defined
for the selection reason.
2. Schedule base record (SBR), if there is a nonzero
MUSTTIME defined.
3. No must start time is used.
The job's must start time is taken from the following
records in the following order:
1. Job reason code record (JRC), if defined and there
is a matching nonzero MUSTTIME for the
selection reason.
2. Job base record (JBR) if MUSTTIME is defined.
3. No must start time is used.
The schedule's or job's COMPLETION DEADLINE
TIME, if one was defined. The schedule's deadline
time is taken from the following records in the
following order:
1. Schedule reason code record (SRC), if defined and
there is a matching nonzero DEADLINE for the
selection reason.
5-108 Unicenter CA-Scheduler Reference Guide, Part 2

5.8 Simulation Reports
2. Schedule base record (SBR), if a nonzero
DEADLINE was defined.
3. No deadline time is used.
The job's deadline time is taken from the following
records in the following order:
1. Job reason code record (JRC), if defined and there
is a matching nonzero DEADLINE for the selection
reason.
2. Job base record (JBR) if DEADLINE is defined.
3. No deadline time is used.
MAXTIME
AVERAGE TIME
The schedule's or job's MAXIMUM EXECUTION
TIME, if one was defined. The schedule's maximum
execution time is taken from the following records in
the following order:
1. Schedule reason code record (SRC), if defined and
there is a matching nonzero MAXTIME for the
selection reason.
2. Schedule base record (SBR), if a nonzero
MAXTIME has been defined.
3. No maximum execution time is used.
The job's maximum execution time is taken from the
following records in the following order:
1. Job reason code record (JRC), if defined and there
is a matching nonzero MAXTIME for the selection
reason.
2. Job base record (JBR) if there is a nonzero
MAXTIME defined.
3. No maximum execution time is used.
The job's average processing time is taken from the
following records in the following order:
1. Job reason code record (JRC) if defined and there
is a matching nonzero average time for the
selection reason.
2. Job base record (JBR) if there is a nonzero average
time defined.
3. Job history record (JHR) average time is calculated
and based upon $JOBACCT data. If the job has not
run at your installation yet, this field is not used.
4. Station resource record (RSR) average time is used.
Chapter 5. Reports 5-109

5.8 Simulation Reports
ROUTING DELAY TIME
The ROUTE DELAY time as defined on the job
resource record or the RTE DELAY defined on the
station resource record and assigned by default to all
jobs processed at this station. This is how long it takes
the job to get to this station from the preceding
station.
CLASS
TRACK FILE
STATUS
The class the job is to be run in.
Whether the schedule or job was selected from the
tracking file.
The current status of the schedule or job. This is
shown only if simulation was run with the
REVISE=YES keyword.
5.8.6 Simulated Device Utilization (DEVUTIL)
The Simulated Device Utilization (DEVUTIL) report shows the extent to which
each device dedicated to one station or substation will be utilized.
COMPUTER ASSOCIATES SIMULATED SHARED DEVICE UTILIZATION FOR STATION 4 DEVUTIL PAGE 1
CA-SCHEDULER 7.3 39SH73 CPU 14 SEP 23 11.13.5
SIMULATION DATE 14 SEP 23
338 339 342 143
TIME USE AVAL USE AVAL USE AVAL USE AVAL
-------------- -------- -------- -------- --------
9/14/3 9. 8 4 2 1
9/14/3 9.15 8 4 2 1
9/14/3 9.3 8 4 2 1
9/14/3 9.45 8 4 2 1
9/14/3 1. 8 4 2 1
9/14/3 1.15 8 4 2 1
9/14/3 1.3 8 4 2 1
9/14/3 1.45 8 4 2 1
9/14/3 11. 8 4 2 1
9/14/3 11.15 8 4 2 1
9/14/3 11.3 8 4 2 1
9/14/3 11.45 8 4 2 1
9/14/3 12. 8 4 2 1
The following information is given:
TIME
USE AVAL
The date for which these events are being simulated and the
times throughout that day. (The time interval is defined by the
INTERVAL keyword on the SIMULATE COMMAND. If
INTERVAL is not specified, a 15-minute interval is used.)
Each heading is a different DASD, tape, or unit record device
type. These are the device types defined on the station resource
record for dedicated use at this station or substation (or changed
for this simulation run only using the OVERRIDE RESOURCE
command). Additional device types are shown on additional
pages. The two columns shown are:
5-110 Unicenter CA-Scheduler Reference Guide, Part 2

5.8 Simulation Reports
■
■
The USE column, which shows how many of each type of
device will actually be in use during the time interval shown
at the left.
The AVAL column, which shows how many of each type of
device will not be in use. This is the number defined minus
the number in use.
5.8.7 Simulated Execution Schedule (SIMEXEC)
The Simulated Execution Schedule (SIMEXEC) report shows when and where
each job will be processed based on the job's requirements and the availability
of resources. It allows you to see at a glance exactly what will happen at each
partition or unit throughout the day.
COMPUTER ASSOCIATES SIMULATED EXECUTION SCHEDULE FOR STATION 4 SYSID 1 SIMEXEC PAGE 1
CA-SCHEDULER 7.3 39SH73 CPU 14 SEP 23 11.13.5
SIMULATION DATE 14 SEP 23
TIME PART1 PART2 PART3 PART4 PART5
-------------- -------------------- -------------------- -------------------- -------------------- --------------------
9/14/3 8. JOB6A -1 SCD6 JOB4A -1 SCD4 IDLE IDLE IDLE
9/14/3 9. JOB7A -1 SCD7 JOB7B -1 SCD7
9/14/3 1. JOB7D -1 SCD7 JOB7E -1 SCD7
9/14/3 11. IDLE IDLE
The following information is given:
TIME
PART01, etc.
The date for which these events are being simulated and the
times when a job starts or a unit becomes idle.
The headers that identify each partition at the CPU station or
each unit at a non-CPU station. (These headers are defined on
the station resource record and may be overridden for this
simulation run only using the OVERRIDE RESOURCE
command.) Under each header are listed the jobs that will run
in this partition or be processed at this unit. The job will start
at the time shown under TIME and last until another job starts
or until the unit is idle. Jobs are assigned to units based on
their class and the classes of jobs defined for each unit. (Unit
classes are also defined on the station resource record and may
be overridden using the OVERRIDE RESOURCE command.)
Jobs are scheduled according to their priorities, start times,
deadlines, availability, and the availability of any resources
defined for them. Additional partitions or units are shown on
additional pages.
Jobs listed on this report can be limited to:
■
■
Jobs assigned to certain schedules using the RONLY Schedule command
Jobs simulated within a specific time period using the RFT and RTT
keywords with the SIMULATE command
Chapter 5. Reports 5-111

5.8 Simulation Reports
5.8.8 Simulated Shared Device Utilization (DEVUTIL)
The Simulated Shared Device Utilization (DEVUTIL) report shows the extent to
which each defined device at a station will be utilized. The devices shown here
are those that are shared by all substations at this station and are in addition
to the dedicated devices shown on the previous Simulated Device Utilization
report.
COMPUTER ASSOCIATES SIMULATED SHARED DEVICE UTILIZATION FOR STATION 4 DEVUTIL PAGE 1
CA-SCHEDULER 7.3 39SH73 CPU 14 SEP 23 11.13.5
SIMULATION DATE 14 SEP 23
338 339 342 143
TIME USE AVAL USE AVAL USE AVAL USE AVAL
-------------- -------- -------- -------- --------
9/14/3 9. 8 4 2 1
9/14/3 9.15 8 4 2 1
9/14/3 9.3 8 4 2 1
9/14/3 9.45 8 4 2 1
9/14/3 1. 8 4 2 1
9/14/3 1.15 8 4 2 1
9/14/3 1.3 8 4 2 1
9/14/3 1.45 8 4 2 1
9/14/3 11. 8 4 2 1
9/14/3 11.15 8 4 2 1
9/14/3 11.3 8 4 2 1
9/14/3 11.45 8 4 2 1
9/14/3 12. 8 4 2 1
The following information is given:
TIME
The date for which these events are being simulated and the times
throughout that day. (The time interval is defined by the
INTERVAL keyword on the SIMULATE command. If not
specified, a 15-minute interval is used.)
USE AVAL Each heading is a different DASD, tape, or unit record device
type. These are the device types defined on the station resource
record for shared use at this station (or changed for this simulation
run only using the OVERRIDE SHRRSR command). The two
columns shown are:
5.8.9 Simulated Unit Utilization (UNITUTIL)
■
■
The USE column, which shows how many of each type of
device will actually be in use during the time interval shown
at the left.
The AVAL column, which shows how many of each type of
device will not be in use. This is the number defined minus
the number in use.
The Simulated Unit Utilization report shows the extent to which each unit at a
defined station will be utilized.
5-112 Unicenter CA-Scheduler Reference Guide, Part 2

5.8 Simulation Reports
COMPUTER ASSOCIATES SIMULATED UNIT UTILIZATION FOR STATION 4 SYSID 1 UNITUTIL PAGE 1
CA-SCHEDULER 7.3 39SH73 CPU 14 SEP 23 11.13.5
SIMULATION DATE 14 SEP 23
TIME 1 2 3 4 5 6 7
-------------- --- --- --- --- --- --- ---
9/14/3 9.
9/14/3 9.15
9/14/3 9.3
9/14/3 9.45
9/14/3 1.
9/14/3 1.15
9/14/3 1.3
9/14/3 1.45
9/14/3 11.
9/14/3 11.15
9/14/3 11.3
9/14/3 11.45
9/14/3 12.
9/14/3 12.15
9/14/3 12.3
9/14/3 12.45
9/14/3 13.
9/14/3 13.15
9/14/3 13.3
9/14/3 13.45
9/14/3 14.
9/14/3 14.15
9/14/3 14.3
9/14/3 14.45
9/14/3 15.
9/14/3 15.15
9/14/3 15.3
9/14/3 15.45
9/14/3 16.
9/14/3 16.15
9/14/3 16.3
9/14/3 16.45
9/14/3 17.
9/14/3 17.15
9/14/3 17.3
9/14/3 17.45
9/14/3 18.
9/14/3 18.15
9/14/3 18.3
9/14/3 18.45
9/14/3 19.
9/14/3 19.15
9/14/3 19.3
9/14/3 19.45
9/14/3 2.
1=PART1 2=PART2 3=PART3 4=PART4 5=PART5 6=PART6 7=PART7
The following information is given:
TIME
The date for which these events are being simulated and the times
throughout that day. (The time interval is defined by the
INTERVAL keyword on the SIMULATE COMMAND. If INTERVAL
is not specified, a 15-minute interval is used.)
Asterisks appear in time intervals where the job starts in the time
interval, or if there is activity in the preceding interval.
001, etc. Each number represents a different unit. The units that have been
defined for this station are shown at the bottom of the report. For
example, the first unit at this station is partition PART01. The first
unit at the keypunch station could be KEYPCH01, one of the
keypunch devices. The asterisks below each number indicate that the
unit is being utilized during the time interval shown at the left. That
is, the asterisks will appear if the job starts at the time interval or
Chapter 5. Reports 5-113

5.8 Simulation Reports
there is activity in the preceding time interval. This allows you to
see at a glance which units are in use throughout the day and which
times are the busiest.
For example, a job running at partition 001, starting at 9:45 and
ending at 10:19 would have asterisks at times 9:45, 10:00, 10:15, and
10:30 - the default 15 minute interval time. 9:45 appears because that
is the time the job starts. 10:30 appears because there was activity
from 10:16 to 10:19 that is in the preceding time interval of (10:16 to
10:30) or 10:30.
5.8.10 Tracking File Job Start Errors (EXPERROR)
The Tracking File Job Start Errors (EXPERROR) report lists the jobs in the
tracking file that have not started yet or did not start on time.
COMPUTER ASSOCIATES TRACKING FILE JOB START ERRORS EXPERROR PAGE 1
CA-SCHEDULER 7.3 39SH73
23 SEP 23 1.42.46
SIMULATION DATE 23 SEP 23
CACU62W JOB SHSIG1 1 IN SCHEDULE SHSI AT STATION 4 STARTED AT 9/23/3 . INSTEAD OF 9/23/3 1.42
This report has no column headings. The lines on the report are produced by
using two Unicenter CA-Scheduler messages: CACU620W and CACU621W.
Message CACU620W indicates that the job was not able to be started by
simulation at the time specified in the tracking file. It is displayed as:
JOB xxxxxxxx IN SCHEDULE yyyyyyyy AT STATION nn STARTED AT mm/dd/yy hh.mm
INSTEAD OF mm/dd/yy hh.mm
The job name, schedule name and station number are given, followed by the
actual starting date and time, and the date and time specified in the tracking
file.
Message CACU621W indicates that a job was supposed to start at a specified
date and time, but did not start by the current time of day in simulation. It is
displayed as:
JOB xxxxxxxx IN SCHEDULE yyyyyyyy AT STATION nn DID NOT START AT mm/dd/yy hh.mm
The job name, schedule name and station number are given, followed by the
date and time the job was supposed to start (it hasn't started yet).
Note: For installations using the European date format, the date will appear
as dd/mm/yy.
5-114 Unicenter CA-Scheduler Reference Guide, Part 2

5.9 Forecasting
5.9 Forecasting
Forecasting allows you to predict which schedules and jobs will be selected on
a future date. We highly recommend that you run forecast reports after you
run the database Analyze report and review its output. The Analyze report
will confirm or deny the validity of the selection criteria you have used to
define schedules and jobs. After correcting any errors or resolving any
conflicts, you can then run one or more of the following forecast reports:
Use This Report Report ID For This Information
Job Summary SUMMARY An overview of jobs that will
be selected on a given date
(usually a range of dates)
Schedules/Jobs Selected For
DDMMYY
Schedules/Jobs Selected For
Station X
Resources Required
For all selected jobs
For jobs at station X
SELECTED
STATION
RESALL
RESSTN
A detailed list of schedules
and jobs that will be selected
on a given date
The workload at each station
The resources defined on the
job resource record
for all selected jobs
for jobs at each station
Route Station Report ROUTESTN The jobs that will be selected
that are of interest to a route
station (jobs must be
identified by ROUTE on
their job information records)
Run Book RUNBOOK Database and documentation
library values
Predecessors Required For
Jobs At Station X
PREDS
List of predecessors that
must be satisfied
Revised forecasting allows you to see the current status of every schedule and
job in the tracking file. This appears on both Schedules/Jobs Selected reports
when the FORECAST command is issued with the REVISE=YES keyword.
Chapter 5. Reports 5-115

5.9 Forecasting
5.9.1 Summary of the Forecast Commands
These commands allow you to limit the forecast reports to only one schedule
or to change the schedules and jobs that would normally be selected:
To
Exclude
schedules
jobs
Report on only one schedule
Activate REQUESTED
schedules
jobs
Add
schedules
jobs
Use This Command
EXCLUDE S
EXCLUDE J
ONLY S
REQUEST S
REQUEST J
RUN S
RUN J
These commands, which must be submitted before the FORECAST command,
are described in the above order on the following pages. The FORECAST
command is described last, followed by samples of the forecast reports.
5.9.2 Virtual Storage Requirements for Forecasting
Forecasting requires 200K in virtual storage for the program. A certain
amount of additional virtual storage is necessary based upon the following
variables.
Allocate
For Each
72 bytes Partition
120 bytes Defined station
80 bytes Defined and selected schedule
152 bytes Defined and selected job
268 bytes Selected job with a resource record
5-116 Unicenter CA-Scheduler Reference Guide, Part 2

5.9 Forecasting
5.9.2.1 Example
Given the following values, 290K of virtual storage is necessary to run a
forecast report.
Program storage
248 bytes
Partitions BG,F1,F2,F3,F4
36 bytes
Stations 2,3,39,4,6,9
72 bytes
6 schedules
48 bytes
3 jobs
456 bytes
15 jobs with resource records
42 bytes
--------------------------------------------------------------------
Total
29648 bytes
or 29K
Chapter 5. Reports 5-117

5.10 Forecast Commands
5.10 Forecast Commands
5.10.1 EXCLUDE JOB
This topic describes each of the commands used with forecasting. Descriptions
of each keyword are given along with notes on when to use the command and
an example of how to use it.
EXCLUDE Job Name=jname
Exclude a specific schedule or job that would
normally be selected.
5.10.1.1 Keywords
Name=jname
JNo=nn
Schedule=sname
SImday=nn
STation=nn
5.10.1.2 Keyword Descriptions
Name=jname
Use this required keyword to specify the job (1- to 8-character job name) you
want to exclude from the forecast run.
JNo=nn
Specify the job number (an integer from 1-99) if you want to exclude a
particular occurrence of the job from the forecast run.
Schedule=sname
Specify the schedule name (1-8 characters) if the job has been defined in more
than one schedule. If this is not specified, Unicenter CA-Scheduler will exclude
the first job it finds with the specified job name.
5-118 Unicenter CA-Scheduler Reference Guide, Part 2

5.10 Forecast Commands
5.10.1.3 Usage Notes
5.10.1.4 Example
SImday=nn
Indicate what day to exclude the job. Give the number of that day relative to
the beginning of the forecast period, where the first day is day 0. Therefore, to
exclude a job only on the second day of the forecast period, specify
SIMDAY=1. If you do not use this keyword, the job will be excluded every
day during the forecast period.
STation=nn
Specify the station ID (integer from 1-99) for non-CPU stations.
Use the EXCLUDE Job command to exclude a job that is normally selected
today but is not needed for this forecast run. All successors will also be
excluded, as if this job can not be selected today.
Specify JNO for job numbers other than 01. Specify the schedule name if the
job has been defined in more than one schedule. Specify STATION for
non-CPU stations.
This command must precede the FORECAST command. Code a separate
EXCLUDE command for each job that you want to exclude.
JCL that produces forecast reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
EXCLUDE J N=MONTHLY,
S=ANNUAL
FORECAST SUMMARY
/
/&
exclude a job
job is in this schedule
produce summary report
The preceding example uses the EXCLUDE command to exclude the job
named 'MONTHLY' in the schedule named 'ANNUAL' from the summary
report. If this job has any successors, they will be excluded too.
Chapter 5. Reports 5-119

5.10 Forecast Commands
5.10.2 EXCLUDE SCHEDULE
5.10.2.1 Keywords
EXCLUDE Schedule Name=sname Exclude a specific schedule that would
normally be selected.
Name=sname
SImday=nn
5.10.2.2 Keyword Descriptions
5.10.2.3 Usage Notes
5.10.2.4 Example
Name=sname
Use this required keyword to specify the schedule (1- to 8-character schedule
name) you want to exclude from the forecast run.
SImday=nn
Indicate what day to exclude the job or schedule. Give the number of that day
relative to the beginning of the forecast period, where the first day is day 0.
Therefore, to exclude a job only on the second day of the forecast period,
specify SIMDAY=1. If you do not use this keyword, the job or schedule will
be excluded every day during the forecast period.
Use the EXCLUDE Schedule command to exclude a schedule that is normally
selected today but is not needed for this forecast run. All successors will also
be excluded, as if this schedule and its jobs can not be selected today.
This command must precede the FORECAST command. Code a separate
EXCLUDE command for each job or schedule that you want to exclude.
JCL that produces forecast reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
EXCLUDE S N=USUALLY
FORECAST SUMMARY
/
/&
exclude a schedule
produce summary report
5-120 Unicenter CA-Scheduler Reference Guide, Part 2

5.10 Forecast Commands
5.10.3 ONLY Schedule
The preceding example uses the EXCLUDE command to exclude a schedule
named 'USUALLY' from the summary report. If this schedule has any
successors, they will be excluded too.
ONLY Schedule Name=sname
Produce forecast reports for only on schedule.
5.10.3.1 Keywords
Name=sname
SImday=nn
5.10.3.2 Keyword Descriptions
5.10.3.3 Usage Notes
Name=sname
Specify the schedule (1- to 8-character schedule name) for which the forecast
reports will be produced.
SImday=nn
Indicate what day to produce the reports. Give the number of that day
relative to the beginning of the forecast period, where the first day is day 0.
Therefore, to produce reports for the selected schedule on the second day of
the forecast period, specify SIMDAY=1. If you do not use this keyword, the
reports will be produced every day during the forecast period.
Use the ONLY Schedule command to produce forecast reports for only on
schedule. This command must precede the FORECAST command.
The ONLY Schedule command only reports on a schedule that is normally
selected on the day you are forecasting. To report on a schedule that is not
normally selected, use either the RUN Schedule command or the OVERRIDE
SCHEDULE command with AUTOSEL=YES.
JCL that produces forecast reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
Chapter 5. Reports 5-121

5.10 Forecast Commands
5.10.3.4 Example
5.10.4 REQUEST Job
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
ONLY S N=JUSTONE report on only one schedule
FORECAST
produce all forecast reports
/
/&
The preceding example produces all of the forecast reports for only one
schedule.
REQUEST Job Name=jname
Request a job and its respective successors.
5.10.4.1 Keywords
Name=jname
AT=hhmm|ddhhmm
Jno=nn
Schedule=sname
SImday=nn
STation=nn
5.10.4.2 Keyword Descriptions
Name=jname
Specify the job (1- to 8-character job name) you want to move to the ACTIVE
queue.
AT=hhmm|ddhhmm
Specify the time that the job is to be moved to the ACTIVE queue. Specify
hhmm in terms of a 24-hour clock. Use dd to indicate the number of autoscan
days in the future when this is to occur. Do not use dd if the job will be
moved to the ACTIVE queue today.
JNo=nn
Specify the job number (an integer from 1-99) if you want to request a
particular occurrence of a job.
Schedule=sname
Specify the schedule name (1-8 characters) if the job has been defined in more
than one schedule. If this is not specified, Unicenter CA-Scheduler will move
to the ACTIVE queue the first job it finds with the specified job name (if the
schedule that the job belongs to is active).
5-122 Unicenter CA-Scheduler Reference Guide, Part 2

5.10 Forecast Commands
5.10.4.3 Usage Notes
5.10.4.4 Example
SImday=nn
Indicate what day of the forecast period to move the job to the ACTIVE queue.
Give the number of that day relative to the beginning of the forecast period,
where the first day is day 0. Therefore, to request a job on the second day of
forecasting, specify SIMDAY=1. If you do not use this keyword, the job will be
moved to the ACTIVE queue every day during the forecast period.
STation=nn
Specify the station ID (integer from 1-99) for non-CPU stations.
Use the REQUEST Job command to request a job and its respective succesors.
Use this command only if the schedule that contains the job is active.
The REQUEST Job command must precede the FORECAST command.
JCL that produces forecast reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REQUEST J N=NOTTODAY,
S=SALES,
SIMDAY=1
FORECAST
/
/&
5.10.5 REQUEST Schedule
activate a job
job is in this schedule
activate it on 2nd day
produce forecast reports
The preceding example activates a job in the SALES schedule on the second
day of the forecast period. Note that the SALES schedule must be scheduled
that day for one of its jobs to be activated.
REQUEST Schedule Name=sname
Request a schedule and its respective
successors.
Chapter 5. Reports 5-123

5.10 Forecast Commands
5.10.5.1 Keywords
Name=sname
AT=hhmm|ddhhmm
SImday=nn
5.10.5.2 Keyword Descriptions
5.10.5.3 Usage Notes
5.10.5.4 Example
Name=sname
Specify the schedule (1- to 8-character schedule name) you want to move to
the ACTIVE queue.
AT=hhmm|ddhhmm
Specify the time that the schedule is to be moved to the ACTIVE queue.
Specify hhmm in terms of a 24-hour clock. Use dd to indicate the number of
autoscan days in the future when this is to occur. Do not use dd if the
schedule will be moved to the ACTIVE queue today.
SImday=nn
Indicate what day of the forecast period to move the job or schedule to the
ACTIVE queue. Give the number of that day relative to the beginning of the
forecast period, where the first day is day 0. Therefore, to request a job on the
second day of forecasting, specify SIMDAY=1. If you do not use this keyword,
the job or schedule will be moved to the ACTIVE queue every day during the
forecast period.
Use the REQUEST Schedule command to request a schedule and its respective
successors. This command must precede the FORECAST command.
JCL that produces forecast reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
REQUEST S N=RUNONREQ,
AT=12
FORECAST
/
/&
activate a schedule
at noon
produce forecast reports
5-124 Unicenter CA-Scheduler Reference Guide, Part 2

5.10 Forecast Commands
The preceding example activates a schedule that has been defined with
REQUESTED criteria. These schedules are selected every day but are kept in
the INACTIVE queue until a REQUEST command moves them to the ACTIVE
queue.
5.10.6 RUN Job
RUN Job Name=jname
Include a job that is not normally selected
today.
5.10.6.1 Keywords
Name=jname
AT=hhmm|ddhhmm
Jno=nn
Schedule=sname
SImday=nn
STation=nn
5.10.6.2 Keyword Descriptions
Name=jname
Specify the job (1- to 8-character job name) you want to include.
AT=hhmm|ddhhmm
Specify the time that the job is to start. Specify hhmm in terms of a 24-hour
clock. Use dd to indicate the number of autoscan days in the future when the
job is to be included. Do not use dd if the job will be included today.
JNo=nn
Specify the job number (an integer from 1-99) if you want to include a
particular occurrence of a job.
Schedule=sname
Specify the schedule name (1-8 characters) if the job has been defined in more
than one schedule. If this is not specified, Unicenter CA-Scheduler will include
the first job it finds with the specified job name (if the schedule that the job
belongs to is active).
SImday=nn
Indicate what day of the forecast period to include the job. Give the number
of that day relative to the beginning of the forecast period, where the first day
is day 0. Therefore, to include a job on the second day, specify SIMDAY=1. If
Chapter 5. Reports 5-125

5.10 Forecast Commands
5.10.6.3 Usage Notes
5.10.6.4 Example
you do not use this keyword, the job will be included every day during the
forecast period.
STation=nn
5.10.7 RUN Schedule
Specify the station ID (integer from 1-99) for non-CPU stations.
User the RUN Job command to include a job that is not normally selected
today. Use this command only if the schedule that contains the job is active. It
must either be selected today or added using a RUN Schedule command.
This command must precede the FORECAST command.
JCL that produces forecast reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
RUN J N=CUST1,
S=SALES,
SIMDAY=1
FORECAST
/
/&
add a job
job is in this schedule
add it only on 2nd day
produce forecast reports
The preceding example adds a job that is not normally selected today,
although it is part of a schedule that is normally selected. The job is to be
added to the schedule only on the second day of the forecast period.
RUN Schedule Name=sname
Include a schedule that is not normally
selected today.
5.10.7.1 Keywords
Name=sname
AT=hhmm|ddhhmm
SImday=nn
5-126 Unicenter CA-Scheduler Reference Guide, Part 2

5.10 Forecast Commands
5.10.7.2 Keyword Descriptions
5.10.7.3 Usage Notes
5.10.7.4 Example
Name=sname
Specify the schedule (1- to 8-character schedule name) you want to include.
AT=hhmm|ddhhmm
Specify the time that the schedule is to start. Specify hhmm in terms of a
24-hour clock. Use dd to indicate the number of autoscan days in the future
when the schedule is to be included. Do not use dd if the schedule will be
included today.
SImday=nn
Indicate what day of the forecast period to include the schedule. Give the
number of that day relative to the beginning of the forecast period, where the
first day is day 0. Therefore, to include a schedule on the second day, specify
SIMDAY=1. If you do not use this keyword, the schedule will be included
every day during the forecast period.
Use the RUN Schedule command to include a schedule that is not normally
selected today. This command must precede the FORECAST command.
JCL that produces forecast reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
RUN S N=PAYROLL,
AT=12
RUN J N=CUST1,
S=SALES,
SIMDAY=1
FORECAST
/
/&
add a schedule
start it at noon
add a job
job is in this schedule
add it only on 2nd day
produce forecast reports
The preceding example adds a schedule that is not normally selected today.
The schedule is to start at noon.
Chapter 5. Reports 5-127

5.10 Forecast Commands
5.10.8 FORECAST
FORECAST
Produce one or more of the forecast reports.
5.10.8.1 Keywords
Optional object: reportid
5.10.8.2 Keyword Descriptions
EXCrept=(reportid1,reportid2,...)
For=nn
FromDate=AUTOS|TODAY|mmddyy|ddmmyy
INCrept=(reportid1,reportid2,...)
MONthof=mmyy
Revise=YES
STation=(nn,...)
EXCrept=(reportid1,reportid2,...)
Use this keyword to list the reports that you do not want printed. If you do
not use this keyword, all reports are printed except the Job Summary Report.
To Exclude This Report
Schedules/Jobs Selected For DDMMYY
Schedules/Jobs Selected For Station X
Resources Required For All Jobs
Resources Required For Jobs At Station X
Run Book
Predecessors Required For Jobs At Station X
Specify
SELECTED
STATION
RESALL
RESSTN
RUNBOOK
PREDS
5-128 Unicenter CA-Scheduler Reference Guide, Part 2

5.10 Forecast Commands
For=nn
Specify the number of days you want included in the forecast. Unicenter
CA-Scheduler will begin selecting jobs and schedules that are supposed to be
processed on the date specified by FROMDATE and will continue selecting
jobs and schedules that are supposed to be processed on the next day, and the
day after that, and so on, until it covers the number of days specified here. If
FOR is not specified, Unicenter CA-Scheduler will select jobs and schedules
only for one day.
FromDate=AUTOS|TODAY|mmddyy|ddmmyy
Give the date when you want the forecast to begin:
AUTOS
TODAY
Start the forecast on the date the database was scanned.
This ignores the actual system date, which changes at
midnight. This is the default and need not be specified.
Start the forecast today, according to the system date. If it
is after midnight, this may be a day later than the
AUTOSCAN date which does not change at midnight. (If
AUTOSCAN takes place at midnight, FD=AUTOS and
FD=TODAY are the same.)
mmddyy|ddmmyy Start the forecast on this date. For example, if you specify
FD=120103, Unicenter CA-Scheduler selects jobs and
schedules that are to be processed on December 1, 2003.
Specify the date as ddmmyy if this is the standard date
format used at your installation.
INCrept=(reportid1,reportid2,...)
Print the Job Summary Report or some of the simulation reports in addition to
the forecast reports.
To Include This Report
Job Summary
Date Translation Report
Specify
SUMMARY
DATETRAN
MONthof=mmyy
Use this keyword if you want the Job Summary report to show a specific
month. If you do not specify a month, the report is for the current month.
This keyword only affects the Job Summary Report. It is to be used in
conjunction with the FromDate and FOR keywords to produce the Forecast
Reports.
Revise=YES
Chapter 5. Reports 5-129

5.10 Forecast Commands
5.10.8.3 Usage Notes
Get an up-to-date picture of how the schedule is going and what work remains
to be done. This is useful if you are having system problems and want to see
how they affect the schedule. All of the regular forecast reports are generated,
starting at the time the FORECAST command is issued. The Schedules/Jobs
Selected reports show the current status of every schedule and job in the
tracking file. The information for all of these reports is taken from the tracking
file instead of from the database; therefore it includes backlogged jobs from
previous days and jobs that have been added to the schedule using online
commands. Completed jobs are eliminated from the schedule. Start and end
times on the Late Job Profile are revised. We suggest that you use this option
when the Unicenter CA-Scheduler Monitor is not operational; for example,
after a system recovery before you bring up Monitor.
STation=(nn,...)
Identify up to eight workstations for which forecast reports are to be
produced. If no STATION is specified, reports are produced for all defined
stations.
Use the FORECAST command to produce one or more of the forecast reports.
Submit EXCLUDE, ONLY, REQUEST or RUN commands before this
command.
All of the forecast reports except the Job Summary Report are produced unless
you specify an object, EXCREPT, or INCREPT. The object can be any of these
report ids:
To Print Only This Report
Job Summary
Schedules/Jobs Selected For DDMMYY
Schedules/Jobs Selected For Station X
Resources Required For Jobs At Station X
Resources Required For All Jobs
Run Book
Predecessors Required For Jobs At Station X
Specify
SUMMARY
SELECTED
STATION
RESSTN
RESALL
RUNBOOK
PREDS
JCL that produces forecast reports requires the inclusion of a work file. A
generic version of this work file is contained on the installation tape. The file's
name is Z.CAWORK1. Tailor this file to your installation's needs and ensure
that it is accessible before running the JCL that produces the reports.
5-130 Unicenter CA-Scheduler Reference Guide, Part 2

5.10 Forecast Commands
5.10.8.4 Example 1
5.10.8.5 Example 2
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
ONLY SCHEDULE N=BIGSCHD
FORECAST station MONTHOF=93
/
/&
report on only one schedule
produce station reports for one month
The preceding example prints station reports for all defined stations showing
which jobs in BIGSCHD will be selected each day during the month of
September, 2003.
// JOB CAJUTIL
work file
// EXEC CAJUTIL,SIZE=24K
EXCLUDE SCHEDULE N=EXCSCHD1
RUN Schedule N=REQJOB1
FORECAST FD=9143,FOR=2,
/
/&
STA=(2,3,4,5,6),
EXC=RUNBOOK,
INC=SUMMARY
exclude a schedule
add a schedule
produce all forecast reports except the
runbook for these stations for 2 days
The preceding example forecasts which schedules and jobs will be selected on
September 14th and 15th, excluding one schedule that would normally be
selected, but adding a schedule that would not normally be selected. All
forecast reports, except runbooks, will be printed. Only five stations will be
reported on.
Chapter 5. Reports 5-131

5.11 Forecast Reports
5.11 Forecast Reports
The reports generated by the FORECAST command are illustrated on the
following pages, organized alphabetically by report title for easy reference. The
three-part report heading is illustrated following:
COMPUTER ASSOCIATES
CA-SCHEDULER 7.3 yymmSHvvn
The left-hand part of the heading identifies the product by vendor, name,
release number and generation level. The generation level consists of the last
two digits of the year (yy), the month (mm), the product code (SH), the release
number (vv), and a number for internal use (n).
SCHEDULES/JOBS SELECTED FOR STATION CPUSTN
THIS IS THE CPU STATION
The middle of the heading gives the report title. If the report is for a specific
station, the station ID or name is inserted on the first line, and the station title
is printed on the second line. (id, name, and title are all taken from the station
definition.)
STATION PAGE 6
14 SEP 23 11.14.17
FORECAST DATE 14 SEP 23
The right-hand part of the heading begins with the report id. (Each report has
a 1- to 8-character report ID which can be specified on the EXCREPT keyword
to exclude the report from a forecast run or on the INCREPT keyword to
include the report in a simulation run.) The second line gives the date and
time the report is generated. The bottom line gives the date for which the
events are being forecasted.
5.11.1 Job Summary (SUMMARY)
The Job Summary (SUMMARY) report is produced only if you specify
SUMMARY or include it using the INCREPT keyword when you issue the
FORECAST command. It gives an overview of jobs that will be selected on
one date or a range of dates. The default report shows an entire month, but
fewer days can be specified using the FROMDATE and FOR keywords.
This report indicates job path selection on a given date by reason code. It does
NOT indicate which stations are selected within a given job path.
5-132 Unicenter CA-Scheduler Reference Guide, Part 2

5.11 Forecast Reports
COMPUTER ASSOCIATES JOB SUMMARY SUMMARY PAGE 1
CA-SCHEDULER 7.3 39SH73 SEP 1, 23 TO SEP 3, 23 1 SEP 23 16.9.12
SCHEDULE ----JOB----
NAME NAME NO RC 1 2 3 4 5 6 7 8 9 1 11 12 13 14 15 16 17 18 19 2 21 22 23 24 25 26 27 28 29 3
-------- -------- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
SCHD1 JOBA 1 1 S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S
SCHD1 JOBB 2 1 S S S S S S S S S S S S S S S S S S S S S S
SCHD1 JOBC 3 1 S S S S S S S S S S S S S S S S S S S S S S
SCHD1 JOBD 4 1 S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S
SCHD1 JOBE 5 1 S S S S S S S S S S S S S S S S S S S S S S
SCHD1 JOBF 1 1 S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S
SCHD1 JOBG 11 1 S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S
SCHD1 JOBH 13 1 S S S S S S S S S S S S S S S S S S S S S S S S S S S S S S
SCHD2 JOBA 1 1 S S S S S S S S S S S S S S S S S S S S S S
JOBNAME=FORCAST PARTITION=BG DATE=9/1/3 TIME=16:12:49 CPUID=FF23 39 COMP=5686326DB6 PAGE 1
The following information is given:
SCHEDULE NAME
JOB NAME
JOB NO
REASON CODE
The schedules that the selected jobs are assigned to.
The jobs that will be selected during this period.
Any number higher than 01 indicates that the job is
supposed to run more than once as part of this schedule.
This tells why each job will be selected:
01 - 79 Corresponds to the position of the reason on
the CRITERIA statement that was defined for
this job or schedule.
80 Means it will be selected because the date
corresponds to a workday on the CALENDAR
that was defined for this job or schedule.
84 Means it is selected by default every day
because no selection criteria were defined.
88 Means that it was added to the forecast by the
RUN command.
1, 2, etc. The dates that are being reported on are listed across the
top of the report. An S under the date means that that
job will be selected on that date.
5.11.2 Predecessors Required for Jobs at Station X (PREDS)
The Predecessors Required for Jobs at Station X (PREDS) report lists the
predecessors that must be satisfied before these jobs can be processed at this
station.
Chapter 5. Reports 5-133

5.11 Forecast Reports
COMPUTER ASSOCIATES PREDECESSORS REQUIRED FOR JOBS AT STATION 4 CPUSTN PREDS PAGE 1
CA-SCHEDULER 7.3 39SH73 CPU 14 SEP 23 11.14.17
FORECAST DATE 14 SEP 23
PREDECESSORS FOR JOBS SELECTED on 14 SEP 23
SCHEDULE ------JOB-----
AVERAGE
NAME NAME NO ST PREDECESSOR SYSID EARLY TIME MUSTTIME DEADLINE TIME
-------- -------- -- -- ----------------------------------------------------- ----- ---------- -------- -------- --------
SCD2 JOB2A 1 4 JOB1A -1 4 8. 8. 1. 1.15
SCD3 JOB3B 1 4 JOB3A -1 4 4.
SCD4 JOB4B 1 4 JOB4A -1 4 1/8.
SCD4 JOB4C 1 4 JOB4B -1 4
The following information is given:
SCHEDULE NAME
JOB NAME
JOB NO
JOB ST
PREDECESSOR
The schedules the selected jobs are assigned to.
The jobs that will be selected on this date.
Any number higher than 01 indicates that the job is
supposed to run more than once as part of this schedule.
The station being reported on.
The predecessor conditions that were defined on the
schedule or job criteria record that need to be satisfied
prior to the job being run. Each predecessor condition is
the end of a job, unless it is preceded by one of the
following reserved words:
This Word
DOS
DSN
GBLxnn=
PRED
SCD
START
Indicates That The Predecessor Is
A DOS job
The close of a data set
A user-defined event
A predecessor only and does not cause selection
A schedule
The start of a job or schedule
SYSID
EARLY TIME
The SYSID, if defined.
The job's EARLIEST START TIME will be taken from the
following records in the following order:
1. Job reason code record (JRC) if defined and there is a
matching nonzero early start time for the selection
reason.
2. Job base record (JBR) if early time is defined.
3. The job will start when the schedule it is in starts.
5-134 Unicenter CA-Scheduler Reference Guide, Part 2

5.11 Forecast Reports
MUSTTIME
DEADLINE
AVERAGE TIME
The job's MUST START BY TIME will be taken from the
following records in the following order:
1. Job reason code record (JRC) if defined and there is a
matching nonzero must time for the selection reason.
2. Job base record (JBR) if must time is defined.
3. No must start by time will be used.
The job's COMPLETION DEADLINE TIME is taken from
the following records in the following order:
1. Job reason code record (JRC) if defined and there is a
matching nonzero DEADLINE for the selection
reason.
2. Job base record (JBR) if DEADLINE is defined.
3. No deadline is used.
The job's average processing time is taken from the
following records in the following order:
1. Job reason code record (JRC) if defined and there is a
matching nonzero average time for the selection
reason.
2. Job base record (JBR) if there is a nonzero average
time defined.
3. Job history record (JHR). The average time in this
record is calculated and based upon $JOBACCT
data. If the job has not been run at your installation
yet, this field is not used.
4. Station resource record (RSR) average time is used.
5.11.3 Resources Required for All Selected Jobs (RESALL)
The Resources Required for All Selected Jobs report lists the resources required
to process jobs that will be selected on a given date. Only jobs with defined job
resource records are listed.
COMPUTER ASSOCIATES RESOURCES REQUIRED FOR ALL SELECTED JOBS RESALL PAGE 1
CA-SCHEDULER 7.3 39SH73 14 SEP 23 13.35.39
FORECAST DATE 14 SEP 23
SCHEDULE ------JOB-----
----DASD--- ----TAPE--- -----UR----
NAME NAME NO ST DISK EXCP TAPE EXCP OTHER EXCP SEPARATE JOBS TYPE NO TYPE NO TYPE NO
-------- -------- -- -- ----------- ----------- ----------- ------------------------------- ----------- ----------- -----------
DSNABC DSNABC 1 4 1,111 2,222 3,333 CAJDEM3 338 2 349 2 143 4
9345 2
ABATCH AB 1 4 3,333 4,444 5,555 IEBDG 339 78 342 3 254 3
The following information is given:
Chapter 5. Reports 5-135

5.11 Forecast Reports
SCHEDULE NAME
The schedules that the jobs are assigned to.
JOB NAME
JOB NO
JOB ST
DISK EXCP
TAPE EXCP
OTHER EXCP
The jobs with defined resource records that will be selected.
The selected job number.
The stations where the job will be scheduled for processing.
To see a separate resource report for each station, use
Resources Required For Jobs At Station X, the RESSTN
report.
The number of disk device I/Os required by each job, as
defined by DASD EXCPS on the job resource record. (See
Note.)
The number of tape device I/Os required by each job, as
defined by TAPE EXCPS on the job resource record. (See
Note.)
The number of unit device I/Os required by each job, as
defined by UNIT EXCPS on the job resource record. (See
Note.)
SEPARATE JOBS/DSNS
The list of jobs that cannot run at the same time as this job,
as defined by SEPARATE JOBS LIST on the job resource
record; or, a DSN that cannot be used by more than one job
at a time, as defined by SEPARATE DSN on the job resource
record.
DASD TYPE
DASD NO
TAPE TYPE
TAPE NO
UR TYPE
UR NO
The types of direct access devices each job requires, as
defined by DASD01 through DASD16 on the job resource
record.
How many of each type of direct access device each job
requires, as defined by DASD01 through DASD16 on the job
resource record.
The types of tape devices each job requires, as defined by
TAPE01 through TAPE16 on the job resource record.
How many of each type of tape device each job requires, as
defined by TAPE01 through TAPE16 on the job resource
record.
The types of unit record devices each job requires, as defined
by UR01 through UR16 on the job resource record.
How many of each type of unit record device each job
requires, as defined by UR01 through UR16 on the job
resource record.
Note: If EXCPs are not defined on the job resource record, the information is
obtained from the job history records, which are updated by
$JOBACCT data.
5-136 Unicenter CA-Scheduler Reference Guide, Part 2

5.11 Forecast Reports
5.11.4 Resources Required for Jobs at Station X (RESSTN)
The Resources Required for Jobs at Station X report lists the resources required
to process jobs at one station. Only jobs with defined job resource records are
listed.
COMPUTER ASSOCIATES RESOURCES REQUIRED FOR JOBS AT STATION CPU RESSTN PAGE 1
CA-SCHEDULER 7.3 39SH73 CPU 14 SEP 23 13.35.39
FORECAST DATE 14 SEP 23
SCHEDULE ------JOB-----
----DASD--- ----TAPE--- -----UR----
NAME NAME NO ST DISK EXCP TAPE EXCP OTHER EXCP SEPARATE JOBS TYPE NO TYPE NO TYPE NO
-------- -------- -- -- ----------- ----------- ----------- ------------------------------- ----------- ----------- -----------
DSNABC DSNABC 1 4 1,111 2,222 3,333 CAJDEM3 338 2 342 2 143 4
339 2
ABATCH AB 1 4 3,333 4,444 5,555 IEBDG 9345 78 349 3 254 3
The following information is given:
SCHEDULE NAME The schedules that the jobs are assigned to.
JOB NAME
JOB NO
JOB ST
DISK EXCP
TAPE EXCP
OTHER EXCP
SEPARATE JOBS
DASD TYPE
DASD NO
TAPE TYPE
The jobs with defined resource records that will be
scheduled for processing at this station.
The selected job number.
All of the jobs listed here will be scheduled for processing
at the same station.
The number of disk device I/Os required by each job, as
defined by DASD EXCPS on the job resource record. (See
Note.)
The number of tape device I/Os required by each job, as
defined by TAPE EXCPS on the job resource record. (See
Note.)
The number of unit device I/Os required by each job, as
defined by UNIT EXCPS on the job resource record. (See
Note.)
The list of jobs that cannot run at the same time as this job,
as defined by SEPARATE JOBS LIST on the job resource
record.
The types of direct access devices each job requires, as
defined by DASD01 through DASD16 on the job resource
record.
How many of each type of direct access device each job
requires, as defined by DASD01 through DASD16 on the
job resource record.
The types of tape devices each job requires, as defined by
TAPE01 through TAPE16 on the job resource record.
Chapter 5. Reports 5-137

5.11 Forecast Reports
TAPE NO
UR TYPE
UR NO
5.11.5 Run Book (RUNBOOK)
How many of each type of tape device each job requires,
as defined by TAPE01 through TAPE16 on the job resource
record.
The types of unit record devices each job requires, as
defined by UR01 through UR16 on the job resource record.
How many of each type of unit record device each job
requires, as defined by UR01 through UR16 on the job
resource record.
Note: If EXCPs are not defined on the job resource record, the information is
obtained from the job history records, which are updated by
$JOBACCT data.
The Run Book report lists all database and documentation library values
defined for each job that will be selected on the given date.
5-138 Unicenter CA-Scheduler Reference Guide, Part 2

5.11 Forecast Reports
COMPUTER ASSOCIATES RUN BOOK RUNBOOK PAGE 1
CA-SCHEDULER 7.3 39SH73 14 SEP 23 13.35.39
FORECAST DATE 14 SEP 23
JOB - DSNABC -1
SCHEDULE - DSNABC
STATION - 4
DATE - 14 SEP 23
JOB CMNT:JOB INFO COMMENT AREA
SCD CMNT:THIS IS SCD COMMENT AREA
DATE TABLE:DATETAB
CALENDAR:
DOC DISP TIME - 9. DOC DISP KEY - DSNABC SYSID -
EARLY TIME - 1. CLASS - B CPUJOB - YES
MUST TIME - 11. PRTY - 12 AUTOSTART - NO
DEADLINE TIME - 12. PRIORTY - RECOVER - NO
SIM START TIME - USE SIM TIME - NO STAGING - NO
MAX TIME - 1. LIBTYPE - PDS INTERRUPT - NO
AVG ELASP TIME - .35 LIBMEMBER - DSNABC ABEND - ABORT
MEMBER SUB ID - BACKLOG - NO FAILCODE - 3
MEMO
- THIS IS THE MEMO FOR JOB DSNABC IN SCHEDULE DSNABC
FORM - JIR FORM QUANTITY - 87654321 SPEC NUMBR - JIR SPEC
USER RESP - DEB KOLOMICK NOTIFY - JIR NOTIFY
MEMO DESCRIPTION - JOB INFO DESCRIPTION AREA
DESTINATION: DEST1
DEST5
DELIVERY SPECS: DELIVERABLE2
JIRDELIVERABLE3
ROUTE CODES: PP,OO
SEND ALL MESSAGES: DEB
SEND START MESSAGES: JEFF
SEND END MESSAGES: BOB
SEND LATE MESSAGES: FRAN
SEND PURGE MESSAGES: LINDA
SEND FAIL MESSAGES: HOWIE
SEND ABEND MESSAGES: BOB
SEND INTERRUPT MESSAGES: DEB
DATA SET NAME: MOHAMED.ABC
DASD VOLSERS : CAI8
SEPARATE JOBS: CAJDEM3
OUTPUT DSN
DATA SET NAME DEVTYPE BLKSIZE LRECL
------------- ------- ------- -----
DEBK.ABC DISK 6 5
RUNBOOK DOCUMENTATION SPECIFIED BUT RECORD NOT FOUND
Chapter 5. Reports 5-139

5.11 Forecast Reports
COMPUTER ASSOCIATES RUN BOOK RUNBOOK PAGE 2
CA-SCHEDULER 7.3 39SH73 14 SEP 23 13.35.39
FORECAST DATE 14 SEP 23
JOB - DSNABC -1
SCHEDULE - DSNABC
STATION - 4
DATE - 14 SEP 23
NOTEPAD AREA
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
The following information is given:
JOB
SCHEDULE
STATION
DATE
JOB CMNT
SCD CMNT
DATE TABLE
CALENDAR
DOC DISP TIME
DOC DISP KEY
SYSID
EARLY TIME
One of the jobs selected as part of this forecast.
The schedule the job is assigned to.
The station defined for this job.
The date being forecasted.
The COMMENT field on the job information record
(JIR).
The COMMENT field on the schedule information
record (SIR) where this job is defined.
The DATETABLE NAME field on the schedule base
record (SBR) where this job is defined.
The CALENDAR field on the job criteria record (JCR) if
a calendar is used for selection.
The DOC DISP TIME value is taken from the job base
record (JBR).
The documentation member key value is taken from the
job base record (JBR).
The RUN on SYSID value taken from the job base record
(JBR).
The job's EARLIEST START TIME will be taken from the
following records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero early start time for the selection
reason.
5-140 Unicenter CA-Scheduler Reference Guide, Part 2

5.11 Forecast Reports
2. Job base record (JBR) if early time is defined.
3. The job will start when the schedule it is in starts.
CLASS
CPUJOB
MUST TIME
PRTY
AUTOSTART
DEADLINE TIME
PRIORTY
RECOVER
SIM START TIME
USE SIM TIME
STAGING
The POWER class taken from the job base record (JBR)
or the default value from the schedule base record (SBR)
for this job.
Indicates whether this job runs as a computer job.
The job's MUST START BY TIME will be taken from the
following records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero must time for the selection
reason.
2. Job base record (JBR) if must time is defined.
3. No must start time is used.
The POWER priority from the job base record (JBR), or
the default value from the schedule base record (SBR) for
this job.
This is for pre-CPU jobs only. This value is taken from
the job base record (JBR).
The job's COMPLETION DEADLINE TIME is taken from
the following records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero DEADLINE for the selection
reason.
2. Job base record (JBR) if DEADLINE is defined.
3. No deadline is used.
The schedule's evaluation priority for this job, taken
from the job base record (JBR).
The RECOVERY option from the job base record (JBR).
The start time as calculated by a simulation run for this
job.
This option, taken from the job base record (JBR),
indicates whether the job is to start at the simulated start
time.
Value taken from the job base record (JBR) or the default
value from the schedule base record (SBR) for this job.
Chapter 5. Reports 5-141

5.11 Forecast Reports
MAX TIME
LIBTYPE
INTERRUPT
AVG ELASP TIME
LIBMEMBER
ABEND
MEMBER SUB ID
BACKLOG
FAILCODE
The job's MAXIMUM EXECUTION TIME is taken from
the following records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero MAXTIME for the selection
reason.
2. Job base record (JBR) if there is a nonzero MAXTIME
defined.
3. No maximum execution time is used.
This value is taken from the following in this order:
1. Job base record (JBR).
2. The default value from the schedule base record
(SBR) for the job.
3. The system default value as defined in the
generation macro.
This option is taken from the job base record (JBR).
The job's average processing time is taken from the
following records in the following order:
1. Job reason code record (JRC) if defined and there is a
matching nonzero average time for the selection
reason.
2. Job base record (JBR) if there is a nonzero average
time defined.
3. Job history record (JHR). The average time in this
record is calculated and based upon $JOBACCT
data. If the job has not been run at your installation
yet, this field is not used.
4. Finally, the station resource record (RSR) average
time is used.
The library member where the job's JCL is found is taken
from the job base record (JBR).
The abend action as defined on the job base record (JBR).
The library member SUB ID as defined on the job base
record (JBR).
The backlog option as defined on the job base record
(JBR) or the default value found on the schedule base
record (SBR) for the jobs.
The condition code threshold that indicates job failure.
Any job step ending with a return code greater than or
equal to this value will be posted as having FAILED.
5-142 Unicenter CA-Scheduler Reference Guide, Part 2

5.11 Forecast Reports
MEMO
FORM
QUANTITY
SPEC NUMBR
USER RESP
NOTIFY
The memo text as specified on the job base record (JBR).
The form's name is taken from the job information
record (JIR).
The quantity of output as defined on the job information
record (JIR).
The specification value as defined on the job information
record (JIR).
The person or group responsible for this job, as defined
on the job information record (JIR).
The name of the person or group that was specified on
the job information record (JIR).
MEMO DESCRIPTION
The job's description, as entered on the job information
record (JIR).
DESTINATION
DELIVERY SPECS
ROUTE CODES
The destination or destinations (up to eight) as were
defined on the job information record (JIR).
The delivery specifications defined for the job on the job
information record (JIR).
The route stations that will be notified when this job will
be selected for processing. This is taken from the job
information record (JIR).
SEND ALL MESSAGES
The userids that will receive all the messages for this job,
as defined on the job message record (JMR).
SEND START MESSAGES
The userids that will receive the start messages for this
job, as defined on the job message record (JMR).
SEND END MESSAGES
The userids that will receive the job end message for this
job, as defined on the job message record (JMR).
SEND LATE MESSAGES
The userids that will receive the late messages for this
job, as defined on the job message record (JMR).
SEND FAIL MESSAGES
The userids that will receive the job failure message, as
defined on the job message record (JMR).
SEND ABEND MESSAGES
The userids that will receive the job abend message, as
defined on the job message record (JMR).
Chapter 5. Reports 5-143

5.11 Forecast Reports
SEND INTERRUPT MESSAGES
The userids that will receive the job interrupt message,
as defined on the job message record (JMR).
DATA SET NAME
DASD VOLSERS
SEPARATE JOBS
OUTPUT DSN
The SEPDSN value as defined on the job resource record
(JRR).
The required DASD volsers as defined on the job
resource record (JRR).
The separate jobs (SEPJOBS) as defined on the job
resource record (JRR).
Shows the data sets that were closed by the programs
within this job. This was the last time the data sets were
closed for output.
RUNBOOK DOCUMENTATION
Documentation on the job that has been defined and
stored in the documentation library.
NOTEPAD AREA
Area provided for handwritten comments about the job.
5.11.6 Schedules/Jobs Selected for DD MM YY (SELECTED)
The Schedules/Jobs Selected For DD MM YY report lists all schedules and jobs
that will be selected on a given date.
COMPUTER ASSOCIATES SCHEDULES/JOBS SELECTED FOR 29 SEP 23 SELECTED PAGE 1
CA-SCHEDULER 7.3 39SH73 14 SEP 23 13.35.39
FORECAST DATE 14 SEP 23
SCHEDULE ------JOB----- SYSID/ REASON AVERAGE ROUTING TRACK
NAME NAME NO ST SUBID CODE EARLY TIME MUST TIME DEADLINE MAXTIME TIME DELAY TIME CLASS FILE STS
-------- -------- -- -- ------ ------ -------------- -------------- -------------- -------- -------- ---------- ----- ----- ---
DSNABC 88 9/14/3 8. 9/14/3 9. 9/14/3 1. .1
DJKBR14 1 4 9/14/3 9.15 9/14/3 1.15 9/14/3 11.15 .3 .1 B
DSNABC 1 4 1 9/14/3 1. 9/14/3 11. 9/14/3 12. 1. .35 .3 B
ABATCH 1 88 9/14/3 8.1 9/14/3 1.1 1.1
ABATCH 2 39 1 9/14/3 21.21 9/14/3 22.25 9/14/3 23.23 .3 12.34 X
DSNABC 1 4 .1 C
AB 1 4 2 8 9/14/3 21.21 9/14/3 22.25 9/14/3 23.23 .3 12.34 .13 X
The following information is given:
SCHEDULE NAME
JOB NAME
JOB NO
The schedules that will be selected for processing on this
date.
The individual jobs that will be selected as part of these
schedules. (A job with its own criteria record may be
selected less frequently than the rest of the schedule.)
The selected job number.
JOB ST The stations where the job will be processed. (A
separate job base record has been defined for the job at
each of these stations.) To see a separate schedule for
each station, use Selected Schedules/Jobs For Station X,
the STATION report.
5-144 Unicenter CA-Scheduler Reference Guide, Part 2

5.11 Forecast Reports
SYSID/SUBID
REASON CODE
EARLY TIME
MUST TIME
The SYSID or SUBID, if defined.
Specifies why each schedule or job will be selected:
01 - 79 Corresponds to the position of the reason on
the CRITERIA statement that was defined for
this job or schedule
80 Means it will be selected because the date
corresponds to a workday on the CALENDAR
that was defined for this job or schedule.
84 Means it is selected by default every day
because no selection criteria were defined.
88 Means that it was added to the forecast by the
RUN command.
The schedule's or job's EARLIEST START TIME. The
schedule's earliest start time is taken from the following
records in the following order:
1. Schedule reason code record (SRC) if defined, and
there is a matching nonzero EARLYTIME defined for
the selection reason.
2. Schedule base record (SBR) if there is a nonzero
EARLYTIME defined
3. The schedule will be able to start just after autoscan.
The job's earliest start time is taken from the following
records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero EARLY START TIME for the
selection reason.
2. Job base record (JBR) if EARLYTIME is defined.
3. The job will start when the schedule that it is in
starts.
The schedule's or job's MUST START BY TIME, if one
was defined. The schedule's must start time is taken
from the following records in the following order:
1. Schedule reason code record (SRC) if defined, and
there is a matching nonzero MUSTTIME defined for
the selection reason.
2. Schedule base record (SBR) if there is a nonzero
MUSTTIME defined.
3. No must start time is used.
The job's must start time is taken from the following
records in the following order:
Chapter 5. Reports 5-145

5.11 Forecast Reports
1. Job reason code record (JRC) if defined, and there is
a matching nonzero MUSTTIME for the selection
reason.
2. Job base record (JBR) if MUSTTIME is defined.
3. No must start time is used.
DEADLINE
MAXTIME
The schedule's or job's COMPLETION DEADLINE
TIME, if one was defined. The schedule's deadline time
is taken from the following records in the following
order:
1. Schedule reason code record (SRC) if defined, and
there is a matching nonzero DEADLINE for the
selection reason.
2. Schedule base record (SBR), if a nonzero DEADLINE
was defined.
3. No deadline is used.
The job's deadline time is taken from the following
records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero DEADLINE for the selection
reason.
2. Job base record (JBR) if DEADLINE is defined.
3. No deadline is used.
The schedule's or job's MAXIMUM EXECUTION TIME,
if one was defined. The schedule's maximum execution
time is taken from the following records in the following
order:
1. Schedule reason code record (SRC) if defined, and
there is a matching nonzero MAXTIME for the
selection reason.
2. Schedule base record (SBR) if a nonzero MAXTIME
has been defined.
3. No maximum execution time is used.
The job's maximum execution time is taken from the
following records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero MAXTIME for the selection
reason.
2. Job base record (JBR) if there is a nonzero MAXTIME
defined.
3. No maximum execution time is used.
5-146 Unicenter CA-Scheduler Reference Guide, Part 2

5.11 Forecast Reports
AVERAGE TIME
The job's average processing time is taken from the
following records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero average time for the selection
reason.
2. Job base record (JBR) if there is a nonzero average
time defined.
3. Job history record (JHR) average time is calculated
and based upon $JOBACCT data. If the job has not
run at your installation yet, this field is not used.
4. Station resource record (RSR) average time is used.
ROUTING DELAY TIME
The ROUTE DELAY time as defined on the job resource
record, or RTE DELAY, defined on the station resource
record and assigned by default to all jobs processed at
this station, which indicates how long it takes the job to
get to this station from the preceding station.
CLASS
TRACK FILE
STATUS
The class the job is to be run in.
Whether the schedule or job was selected from the
tracking file.
The current status of the schedule or job. This is shown
only if FORECAST was executed with the REVISE=YES
keyword.
5.11.7 Schedules/Jobs Selected for Station X (STATION)
The Schedules/Jobs Selected For Station X report lists all jobs that will be
scheduled for processing at one station on a given date.
COMPUTER ASSOCIATES SCHEDULES/JOBS SELECTED FOR STATION CPU STATION PAGE 1
CA-SCHEDULER 7.3 39SH73 CPU 14 SEP 23 13.35.39
FORECAST DATE 14 SEP 23
SCHEDULE ------JOB----- SYSID/ REASON AVERAGE ROUTING TRACK
NAME NAME NO ST SUBID CODE EARLY TIME MUST TIME DEADLINE MAXTIME TIME DELAY TIME CLASS FILE STS
-------- -------- -- -- ------ ------ -------------- -------------- -------------- -------- -------- ---------- ----- ----- ---
DSNABC 88 9/14/3 8. 9/14/3 9. 9/14/3 1. .1
DJKBR14 1 4 9/14/3 9.15 9/14/3 1.15 9/14/3 11.15 .3 .1 B
DSNABC 1 4 1 9/14/3 1. 9/14/3 11. 9/14/3 12. 1. .35 .3 B
ABATCH 1 88 9/14/3 8.1 9/14/3 1.1 1.1
DSNABC 1 4 .1 C
AB 1 4 2 8 9/14/3 21.21 9/14/3 22.25 9/14/3 23.23 .3 12.34 .13 X
The following information is given:
SCHEDULE NAME
The schedules that the jobs are assigned to.
Chapter 5. Reports 5-147

5.11 Forecast Reports
JOB NAME
JOB NO
JOB ST
SYSID/SUBID
REASON CODE
EARLY TIME
MUST TIME
The jobs that are scheduled for processing at this station.
To appear here, a job must be selected for processing on
this date and must also be defined for processing at this
station.
Any number higher than 01 indicates that the job is
scheduled more than once.
All of the jobs listed here are scheduled for processing at
the same station.
The SYSID or SUBID, if defined.
Specifies why each schedule or job will be selected:
01 - 79 Corresponds to the position of the reason on
the CRITERIA statement that was defined for
this job or schedule.
80 Means it will be selected because the date
corresponds to a workday on the CALENDAR
that was defined for this job or schedule.
84 Means it is selected by default every day
because no selection criteria were defined.
88 Means that it was added to the forecast by the
RUN command.
The schedule's or job's EARLIEST START TIME. The
schedule's earliest start time is taken from the following
records in the following order:
1. Schedule reason code record (SRC) if defined, and
there is a matching nonzero EARLYTIME defined for
the selection reason.
2. Schedule base record (SBR) if there is a nonzero
EARLYTIME defined
3. The schedule will be able to start just after autoscan.
The job's earliest start time is taken from the following
records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero EARLY START TIME for the
selection reason.
2. Job base record (JBR) if EARLYTIME is defined.
3. The job will start when the schedule that it is in
starts.
The schedule's or job's MUST START BY TIME, if one
was defined. The schedule's must start time is taken
from the following records in the following order:
5-148 Unicenter CA-Scheduler Reference Guide, Part 2

5.11 Forecast Reports
1. Schedule reason code record (SRC) if defined, and
there is a matching nonzero MUSTTIME defined for
the selection reason.
2. Schedule base record (SBR) if there is a nonzero
MUSTTIME defined.
3. No must start time is used.
The job's must start time is taken from the following
records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero MUSTTIME for the selection
reason.
2. Job base record (JBR) if MUSTTIME is defined.
3. No must start time is used.
DEADLINE
MAXTIME
The schedule's or job's COMPLETION DEADLINE
TIME, if one was defined. The schedule's deadline time
is taken from the following records in the following
order:
1. Schedule reason code record (SRC) if defined, and
there is a matching nonzero DEADLINE for the
selection reason.
2. Schedule base record (SBR) if a nonzero DEADLINE
was defined.
3. No deadline is used.
The job's deadline time is taken from the following
records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero DEADLINE for the selection
reason.
2. Job base record (JBR) if DEADLINE is defined.
3. No deadline is used.
The schedule's or job's MAXIMUM EXECUTION TIME,
if one was defined. The schedule's maximum execution
time is taken from the following records in the following
order:
1. Schedule reason code record (SRC) if defined, and
there is a matching nonzero MAXTIME for the
selection reason.
2. Schedule base record (SBR) if a nonzero MAXTIME
has been defined.
3. No maximum execution time is used.
Chapter 5. Reports 5-149

5.11 Forecast Reports
The job's maximum execution time is taken from the
following records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero MAXTIME for the selection
reason.
2. Job base record (JBR) if there is a nonzero MAXTIME
defined.
3. No maximum execution time is used.
AVERAGE TIME
ROUTING
DELAY TIME
CLASS
TRACK FILE
STATUS
The job's average processing time is taken from the
following records in the following order:
1. Job reason code record (JRC) if defined, and there is
a matching nonzero average time for the selection
reason.
2. Job base record (JBR) if there is a nonzero average
time defined.
3. Job history record (JHR) average time is calculated
and based upon $JOBACCT data. If the job has not
run at your installation yet, this field is not used.
4. Station resource record (RSR) average time is used.
The ROUTE DELAY time as defined on the job resource
record, or
The RTE DELAY defined on the station resource record
and assigned by default to all jobs processed at this
station. This is how long it takes the job to get to this
station from the preceding station.
The class the job is to be run in.
Whether the schedule or job was selected from the
tracking file.
The current status of the schedule or job. This is shown
only if FORECAST was executed with the REVISE=YES
keyword.
5-150 Unicenter CA-Scheduler Reference Guide, Part 2

5.12 Advantage CA-Earl Automatic Console Reply Reports
5.12 Advantage CA-Earl Automatic Console Reply Reports
This topic gives examples of each of the Advantage CA-Earl reports available
and explains how to produce them.
5.12.1 Automatic Console Reply (by Job)
The report lists job information from the ACR database, sorted by job.
9/14/3 AUTOMATIC CONSOLE REPLY REPORT PAGE 1
SORTED BY JOB
-------------------------------------------------------------------------------------------------------------
JOB JOB SCHEDULE MESSAGE MESSAGE MESSAGE
NAME NO NAME NUMBER SCAN TEXT REPLY TEXT
-------------------------------------------------------------------------------------------------------------
CACM73
DUMP 1,-FFFFFF,E
CACM213
RETRY
CACU4
OK
CADD21
MAX
CADD36
CANCEL
CADD566
BYPASS
CADT5
MSGID1
MSGID2
REPLY2 MSGID2
MSGID3 SCAN3 MSGID3 REPLY3 MSGID3 SCAN3
1S1D
4333D
DELETE
4433D
DELETE
4444D
DELETE
DRV13 MSGID3 SCAN3 MSGID3 REPLY3 MSGID3 DRV13 SCAN3
LIB11 MSGID1
VOL21 MSGID2 REPLY2 MSGID2 VOL21
DRV121 DRV21 ENTER NUMBER OF FILES 3
DRV21 ENTER NUMBER OF TAPES 17
2 DRV21 ENTER NUMBER OF TAPES 13
DRV123 DRV11 4333D CANCEL
DRV131 MSGID3 SCAN3 MSGID3 REPLY3 MSGID3 DRV131 SCAN3
3 MSGID3 SCAN3 MSGID3 REPLY3 MSGID3 DRV131-3 SCAN3
3 DRV13 MSGID3 SCAN3 MSGID3 REPLY3 MSGID3 DRV131-3 DRV13 SCAN3
LIB111
MSGID1
1
MSGID1
1 LIB11 MSGID1
VOL111 VOL11 ENTER NUMBER OF FILES 3
VOL11 ENTER NUMBER OF TAPES 7
VOL122 MSGID2 REPLY2 MSGID2 VOL122
2 MSGID2 REPLY2 MSGID2 VOL122-2
2 VOL21 MSGID2 REPLY2 MSGID2 VOL122-2
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERA1
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
Chapter 5. Reports 5-151

5.12 Advantage CA-Earl Automatic Console Reply Reports
The SYSIPT control statements for the Automatic Console Reply (by job) report
are contained in the CAJINA01.0 source member (shown following). You may
modify the OPTION statement values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
OPTION LIST off
OPTION NODUMP
CAIXVDB:FILE CAJCACRA RECORD=234
COPY CAJEACRP
COPY CAJEACRO
!
DEF GSAJNAME = ' ' 'JOB' 'NAME'
!
SET PRMFUNC = 'GETG'
SET PRMMSGID = ' '
SET PRMJNAME = ' '
SET PRMJNO = ' '
SET PRMSNAME = ' '
!
COPY CAJERA1
END
The control statements that print this report are contained in the CAJERA01.0
source member (shown following). You may modify these statements to
produce your own reports. If you modify any of the source members
provided, be sure to copy them with a different name so a reinstallation of the
product will not replace the modified members.
GET CAIXVDB
GOTO EOJ CAIXVDB = 'E' OR CAIXVDB = 'N'
!
REPORT 'AUTOMATIC CONSOLE REPLY REPORT'
TITLE 'SORTED BY JOB'
!
CONTROL
!
IF(D)
ENDIF
!
PRINT
(ACRJNAME) ACRJNO ACRSNAME ACRMSGID
BREAKQSEQ = 1 SET(D) GSAJNAME = ACRJNAME
ELSE SET(D) GSAJNAME = ' '
GSAJNAME ACRJNO ACRSNAME ACRMSGID ACRSCAN ACRREPLY
The preceding PRINT statement produces a report with the following fields:
5-152 Unicenter CA-Scheduler Reference Guide, Part 2

5.12 Advantage CA-Earl Automatic Console Reply Reports
Field on Report Panel Prompt Batch Operand
JOB NAME JOB JOB
JOB NO JNO JNO
SCHEDULE NAME SCHEDULE SCHEDULE
MESSAGE NUMBER MSGID MSGID
MESSAGE SCAN TEST SCANTXT SCANTXT
MESSAGE REPLY TEXT REPLY REPLY
5.12.2 Automatic Console Reply (by Schedule)
The Advantage CA-Earl Automatic Console Reply (by schedule) report lists job
information from the ACR database, sorted by schedule.
9/14/3 AUTOMATIC CONSOLE REPLY REPORT PAGE 1
SORTED BY SCHEDULE
-------------------------------------------------------------------------------------------------------------------------------
SCHEDULE JOB JOB MESSAGE MESSAGE MESSAGE
NAME NAME NO NUMBER SCAN TEXT REPLY TEXT
-------------------------------------------------------------------------------------------------------------------------------
CACM73
DUMP 1,-FFFFFF,E
CACM213
RETRY
CACU4
OK
CADD21
MAX
CADD36
CANCEL
CADD566
BYPASS
CADT5
MSGID1
MSGID2
REPLY2 MSGID2
MSGID3 SCAN3 MSGID3 REPLY3 MSGID3 SCAN3
1S1D
4333D
DELETE
4433D
DELETE
4444D
DELETE
DRV131 MSGID3 SCAN3 MSGID3 REPLY3 MSGID3 DRV131 SCAN3
DRV131 3 MSGID3 SCAN3 MSGID3 REPLY3 MSGID3 DRV131-3 SCAN3
LIB111 MSGID1
LIB111 1 MSGID1
VOL122 MSGID2 REPLY2 MSGID2 VOL122
VOL122 2 MSGID2 REPLY2 MSGID2 VOL122-2
DRV11 DRV123 4333D CANCEL
DRV13 MSGID3 SCAN3 MSGID3 REPLY3 MSGID3 DRV13 SCAN3
DRV131 3 MSGID3 SCAN3 MSGID3 REPLY3 MSGID3 DRV131-3 DRV13 SCAN3
DRV21 DRV121 ENTER NUMBER OF FILES 3
DRV121 ENTER NUMBER OF TAPES 17
DRV121 2 ENTER NUMBER OF TAPES 13
LIB11
MSGID1
LIB111 1 MSGID1
VOL11 VOL111 ENTER NUMBER OF FILES 3
VOL111 ENTER NUMBER OF TAPES 7
VOL21 MSGID2 REPLY2 MSGID2 VOL21
VOL122 2 MSGID2 REPLY2 MSGID2 VOL122-2
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce the report, submit the following JCL with your job
statement :
Chapter 5. Reports 5-153

5.12 Advantage CA-Earl Automatic Console Reply Reports
// JOB CAJERA2
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The SYSIPT control statements for this report are contained in the CAJINA02.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
OPTION LIST off
OPTION NODUMP
CAIXVDB:FILE CAJCACRA RECORD=234
COPY CAJEACRP
COPY CAJEACRO
!
DEF GSASNAME = ' ' 'SCHEDULE' 'NAME'
!
SET PRMFUNC = 'GETG'
SET PRMMSGID = ' '
SET PRMJNAME = ' '
SET PRMJNO = ' '
SET PRMSNAME = ' '
!
COPY CAJERA2
END
The control statements that print this report are contained in the CAJERA02.0
source member (shown following). You may modify these statements to
produce your own reports. If you modify any of the source members
provided, be sure to copy them with a different name so a reinstallation of the
product will not replace the modified members.
GET CAIXVDB
GOTO EOJ CAIXVDB = 'E' OR CAIXVDB = 'N'
!
REPORT 'AUTOMATIC CONSOLE REPLY REPORT'
TITLE 'SORTED BY SCHEDULE'
!
CONTROL
!
IF(D)
ENDIF
!
PRINT
(ACRSNAME) ACRJNAME ACRJNO ACRMSGID
BREAKQSEQ = 1 SET(D) GSASNAME = ACRSNAME
ELSE SET(D) GSASNAME = ' '
GSASNAME ACRJNAME ACRJNO ACRMSGID ACRSCAN ACRREPLY
The preceding PRINT statement produces a report with the following fields:
Field on Report Panel Prompt Batch Operand
SCHEDULE NAME SCHEDULE SCHEDULE
5-154 Unicenter CA-Scheduler Reference Guide, Part 2

5.12 Advantage CA-Earl Automatic Console Reply Reports
Field on Report Panel Prompt Batch Operand
JOB NAME JOB JOB
JOB NO JNO JNO
MESSAGE NUMBER MSGID MSGID
MESSAGE SCAN TEXT SCANTXT SCANTXT
MESSAGE REPLY TEXT REPLY REPLY
5.12.3 Automatic Console Reply (by Message Number)
The Advantage CA-Earl Automatic Console Reply (by message number) report
lists job information from the ACR database, sorted by message number.
9/14/3 AUTOMATIC CONSOLE REPLY REPORT PAGE 1
SORTED BY MESSAGE NUMBER
-------------------------------------------------------------------------------------------------------------------------------
MESSAGE JOB JOB SCHEDULE MESSAGE MESSAGE
NUMBER NAME NO NAME SCAN TEXT REPLY TEXT
-------------------------------------------------------------------------------------------------------------------------------
CACM73
DUMP 1,-FFFFFF,E
CACM213
RETRY
CACU4
OK
CADD21
MAX
CADD36
CANCEL
CADD566
BYPASS
CADT5
ENTER DRV121 DRV21 NUMBER OF FILES 3
DRV121 DRV21 NUMBER OF TAPES 17
DRV121 2 DRV21 NUMBER OF TAPES 13
VOL111 VOL11 NUMBER OF FILES 3
VOL111 VOL11 NUMBER OF TAPES 7
MSGID1
LIB11
LIB111
LIB111 1
LIB111 1 LIB11
MSGID2
REPLY2 MSGID2
VOL21
REPLY2 MSGID2 VOL21
VOL122
REPLY2 MSGID2 VOL122
VOL122 2 REPLY2 MSGID2 VOL122-2
VOL122 2 VOL21 REPLY2 MSGID2 VOL122-2
MSGID3 SCAN3 MSGID3 REPLY3 MSGID3 SCAN3
DRV13 SCAN3 MSGID3 REPLY3 MSGID3 DRV13 SCAN3
DRV131 SCAN3 MSGID3 REPLY3 MSGID3 DRV131 SCAN3
DRV131 3 SCAN3 MSGID3 REPLY3 MSGID3 DRV131-3 SCAN3
DRV131 3 DRV13 SCAN3 MSGID3 REPLY3 MSGID3 DRV131-3 DRV13 SCAN3
1S1D
4333D
4433D
4444D
END OF REPORT
DELETE
DRV123 DRV11 CANCEL
DELETE
DELETE
REPORT RECORDS READ LINES PRINTED
1 32 47
REPORT PHASE ENDED .6 SECONDS.
1S55I LAST RETURN CODE WAS
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
Chapter 5. Reports 5-155

5.12 Advantage CA-Earl Automatic Console Reply Reports
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERA3
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The SYSIPT control statements for the report are contained in the CAJINA03.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
OPTION LIST off
OPTION NODUMP
CAIXVDB:FILE CAJCACRA RECORD=234
COPY CAJEACRP
COPY CAJEACRO
!
DEF GSAMSGID = ' ' 'MESSAGE' 'NUMBER'
!
SET PRMFUNC = 'GETG'
SET PRMMSGID = ' '
SET PRMJNAME = ' '
SET PRMJNO = ' '
SET PRMSNAME = ' '
!
COPY CAJERA3
END
The control statements that print this report are contained in the CAJERA03.0
source member (shown following). You may modify these statements to
produce your own reports. If you modify any of the source members
provided, be sure to copy them with a different name so a reinstallation of the
product will not replace the modified members.
GET CAIXVDB
GOTO EOJ CAIXVDB = 'E' OR CAIXVDB = 'N'
!
REPORT 'AUTOMATIC CONSOLE REPLY REPORT'
TITLE 'SORTED BY MESSAGE NUMBER'
!
CONTROL
!
IF(D)
ENDIF
!
PRINT
(ACRMSGID) ACRJNAME ACRJNO ACRSNAME
BREAKQSEQ = 1 SET(D) GSAMSGID = ACRMSGID
ELSE SET(D) GSAMSGID = ' '
GSAMSGID ACRJNAME ACRJNO ACRSNAME ACRSCAN ACRREPLY
The preceding PRINT statement produces a report with the following fields:
5-156 Unicenter CA-Scheduler Reference Guide, Part 2

5.12 Advantage CA-Earl Automatic Console Reply Reports
Field On Report Panel Prompt Batch Operand
MESSAGE NUMBER MSGID MSGID
JOB NAME JOB JOB
JOB NO JNO JNO
SCHEDULE NAME SCHEDULE SCHEDULE
MESSAGE SCAN TEXT MSGID MSGID
MESSAGE REPLY TEXT REPLY REPLY
5.12.3.1 Usage Notes
Use the Automatic Console Reply report to list job information from the ACR
database, sorted by message numbers. You may modify members CAJINA01,
CAJINA02 and CAJINA03 to produce your own selective reports.
Example
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
OPTION LIST off
OPTION NODUMP
CAIXVDB:FILE CAJCACRA RECORD=234
COPY CAJEACRP
COPY CAJEACRO
!
DEF GSAJNAME = ' ' 'JOB' 'NAME'
!
SET PRMFUNC = 'GETG'
SET PRMMSGID = 'msg1??1 '
SET PRMJNAME = 'job12 '
SET PRMJNO = ' '
SET PRMSNAME = ' '
!
COPY CAJERA1
END
GET CAIXVDB
GOTO EOJ CAIXVDB = 'E' OR CAIXVDB = 'N'
!
REPORT 'AUTOMATIC CONSOLE REPLY REPORT'
TITLE 'SORTED BY JOB'
!
CONTROL (ACRJNAME) ACRJNO ACRSNAME ACRMSGID
!
IF(D)
ENDIF
!
PRINT
BREAKQSEQ = 1 SET(D) GSAJNAME = ACRJNAME
ELSE SET(D) GSAJNAME = ' '
GSAJNAME ACRJNO ACRSNAME ACRMSGID ACRSCAN ACRREPLY
Chapter 5. Reports 5-157

5.13 Advantage CA-Earl Database Reports
5.13 Advantage CA-Earl Database Reports
This topic gives examples of each of the Advantage CA-Earl Database reports
and how to produce them.
5.13.1 Basic Job Information (by Schedule)
The Advantage CA-Earl Basic Job Information report lists the job information
from the Unicenter CA-Scheduler database, sorted by schedule.
9/14/3 BASIC JOB INFORMATION (BY SCHEDULE) PAGE 1
-------------------------------------------------------------------------------------------------------------------------------
SCHEDULE NAME NUMBER STATION DISPLAY-TIME EARLY-TIME MUST-TIME DEAD-TIME MAXIMUM-TIME
NAME DD.HH.MM DD.HH.MM DD.HH.MM DD.HH.MM DD.HH.MM
-------------------------------------------------------------------------------------------------------------------------------
BNSPE1 BNPAY1 1 39 9. 9. 22. 1.
BNSPE1 BNPAY1 1 4 9. 9. 1. 22. 1.
BNSPE1 BNPAY1 1 2 9. 9. 22. 1.
BNSPE1 BNPAY1 1 4 9. 1. 22. 1.
BNSPE1 BNPAY1 1 4 9. 1. 22. 1.
BNSPE1 BNPAY1 1 6
BNSPE1 BNPAY1 1 4 1. 22. 1.
BNSPE1 BNPAY1 1 4 9. 1. 22. 1.
BNSPE1 BNPAY1 1 4 9. 1. 22. 1.
BNSPE1
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERM1
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The SYSIN control statements for this report are contained in the CAJINM01
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJMST:FILE CAJCACC2 RECORD = 248
COPY CAJEJM
COPY CAJEPM
COPY CAJESETM
COPY CAJERM1
END
5-158 Unicenter CA-Scheduler Reference Guide, Part 2

5.13 Advantage CA-Earl Database Reports
The control statements that print the report are contained in the CAJERM01.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports." You can also modify the report to
select schedule fields; change CAJESETM from JOB to SCH. The schedule
fields you can print are also listed in the appendix "Advantage CA-Earl
Reports." You can also modify the report to select schedule fields; Change
CAJESETM from JOB to SCH. (If you modify any of the source members
provided, be sure to copy them with a different name so a reinstallation of the
product will not replace the modified members.
GET CAIJMST
GOTO EOJ CAIJMST = 'E' OR CAIJMST = 'N'
REPORT 'BASIC JOB INFORMATION (BY SCHEDULE)'
SELECT JOBRECID = 'J'
CONTROL (JOBSCHNAME) SKIP JOBNAME
PRINT JOBSCHNAME JOBNAME JOBNUMBER JOBSTATION
JOBDISPTIME JOBERLYTIME JOBMUSTTIME JOBDEADTIME JOBMAXTIME
The preceding PRINT statement produces a report with the following fields:
Field on Report Batch Operand Panel Prompt
SCHEDULE NAME SCHEDULE SCHEDULE
NAME JOB NAME NAME
NUMBER JOB NUMBER JNO
STATION STATION ID STATION
DISPLAY-TIME DISPLAY TIME DISPTIME
EARLY-TIME
MUST-TIME
DEAD-TIME
MAXIMUM-TIME
EARLIEST START
TIME
MUST START BY
TIME
COMPLETION
DEADLINE TIME
MAXIMUM
EXECUTION TIME
ERLYTIME
MUSTTIME
DEADLINE
MAXTIME
Chapter 5. Reports 5-159

5.13 Advantage CA-Earl Database Reports
5.13.2 Basic Job Information (by Station)
The report lists the job information from the Unicenter CA-Scheduler database,
sorted by station.
9/14/3 BASIC JOB INFORMATION (BY SCHEDULE) PAGE 1
-------------------------------------------------------------------------------------------------------------------------------
STATION SCHEDULE NAME NUMBER DISPLAY-TIME EARLY-TIME MUST-TIME DEAD-TIME MAXIMUM-TIME
NAME DD.HH.MM DD.HH.MM DD.HH.MM DD.HH.MM
-------------------------------------------------------------------------------------------------------------------------------
4 BNRCVR BNPAY1 1 8. 1. 14. 5
4 BNRCVR BNPAY2 2 8. 1. 14. 5
4 BNSPE1 BNPAY1 1 9. 9. 22. 1.
4 BNSPE1 BNPAY1 1 9. 9. 1. 22. 1.
4 BNSPE1 BNPAY1 1 9. 9. 22. 1.
4 BNSPE1 BNPAY1 1 9. 1. 22. 1.
4 BNSPE1 BNPAY1 1 9. 1. 22. 1.
4 BNSPE1 BNPAY1 1
4 BNSPE1 BNPAY1 1 1. 22. 1.
4 BNSPE1 BNPAY2 1 9. 1. 22. 1.
4 BNSPE1 BNPAY3 1 9. 1. 22. 1.
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERM2
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The SYSIN control statements for this report are contained in the CAJINM02.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJMST:FILE CAJCACC2 RECORD = 248
COPY CAJEJM
COPY CAJEPM
COPY CAJESETM
COPY CAJERM2
END
The control statements that print this report are contained in the CAJERM02.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports." You can also modify this report to
select schedule fields; change CAJESETM from JOB to SCH. The schedule
fields you can print are also listed. (If you modify any of the source members
5-160 Unicenter CA-Scheduler Reference Guide, Part 2

5.13 Advantage CA-Earl Database Reports
provided, be sure to copy them with a different name so a reinstallation of the
product will not replace the modified members.
GET CAIJMST
GOTO EOJ CAIJMST = 'E' OR CAIJMST = 'N'
REPORT 'BASIC JOB INFORMATION (BY STATION)'
SELECT JOBRECID = 'J'
CONTROL (JOBSTATION) SKIP JOBSCHNAME
PRINT JOBSTATION JOBSCHNAME JOBNAME JOBNUMBER
JOBDISPTIME JOBERLYTIME JOBMUSTTIME JOBDEADTIME JOBMAXTIME
The preceding PRINT statement produces a report with the following fields:
Field on Report Batch Operand Panel Prompt
STATION STATION ID STATION
SCHEDULE NAME SCHEDULE SCHEDULE
NAME JOB NAME NAME
NUMBER JOB NUMBER JNO
DISPLAY-TIME DISPLAY TIME DISPTIME
EARLY-TIME
MUST-TIME
DEAD-TIME
MAXIMUM-TIME
EARLIEST START
TIME
MUST START BY
TIME
COMPLETION
DEADLINE TIME
MAXIMUM
EXECUTION TIME
ERLYTIME
MUSTTIME
DEADLINE
MAXTIME
Chapter 5. Reports 5-161

5.13 Advantage CA-Earl Database Reports
5.13.3 Job Criteria (by Schedule)
The report lists the criteria from the job criteria record in the Unicenter
CA-Scheduler database.
9/14/3 JOB CRITERIA (BY SCHEDULE) PAGE 1
-------------------------------------------------------------------------------------------------------------------------------
SCHEDULE JOB JNO STATION DATETABLE CALENDAR CRITERIA
NAME NAME
-------------------------------------------------------------------------------------------------------------------------------
BNSCHD2 BNPAY2 1 4
BNSCHD2 BNPAY1 1 4 BNPAY1-1
BNSCHD2 BNPAY2 2 4 BNPAY1-1
BNSCHD2 BNPAY2 1 39
BNSCHD3 BNPAY1 1 4 1.
BNSCHD3 BNPAY1 3 4 BNPAY1-2
BNSCHD3 BNPAY1 2 4 BNPAY1-1
BNSCHD3 BNPAY1 1 39
BNSCHD4 BNPAY2 1 4
BNSCHD4 BNPAY2 1 39
BNSCHD4 BNPAY2 2 4 BNPAY1-1
BNSCHD4 BNPAY2 3 4 BNPAY1-2
BNSCHD5 BNPAY2 1 4 BNPAY1-1
BNSCHD5 BNPAY1 1 39
BNSCHD5 BNPAY1 2 4 BNPAY1-2
BNSCHD5 BNPAY1 1 4
BNSCHD6 BNPAY1 1 4 BNPAY1-2
BNSCHD6 BNPAY2 1 4
BNSCHD6 BNPAY2 2 4 BNPAY1-1
BNSCHD6 BNPAY2 1 39
BNSPE1
BNPAY1 OR BNPAY1 AND BNPAY2
BNSPE1
MON OR TUE OR THU OR FRI OR BNPAY4 AND WED
BNSPE1
BNPAY2
BNSPE1
BNPAY3
BNSPE1
BNSPE1
BNPAY1
BNSPE1
BNSPE1
BNSPE1
BNXAD1
BNXAD1
BNXAD1
BNXAD1
BNPAY1
BNXAD1
BNXAD1
BNPAY3
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERM3
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The SYSIN control statements for this report are contained in the CAJINM03.0
source member (shown following). You may modify the OPTION statement
values. You must also change the number of lines specified in the last SET
statement if any of the criteria statements are longer than 20 lines. If you add
5-162 Unicenter CA-Scheduler Reference Guide, Part 2

5.13 Advantage CA-Earl Database Reports
lines, you must also change the first line in the CAJECRI source member
shown in the appendix "Advantage CA-Earl Reports" to reflect this increase.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
OPTION OMIT DETAIL BLANK LINES
CAIJMST:FILE CAJCACC2 RECORD = 248
COPY CAJECRI
COPY CAJEPM
SET PRMFUNC = 'GETS'
SET PRMID = 'JCR '
SET PRMNME = ' '
SET PRMNUM = ' '
SET PRMSTA = ' '
SET PRMSCH = ' '
! CHANGE THE NEXT LINE IF YOU CHANGE NO OF LINES IN CAJECRI
SET PRMCRIN = 2
COPY CAJERM3
END
The PRINT statement shown following produces a report with the fields
below:
Field on Report Panel Prompt Batch Operand
SCHEDULE NAME S= SCHEDULE
JOB NAME J= NAME
JNO JNO= JNO
STATION ST= STATION
DATETABLE
DATETABLE NAME
(on SBR)
DISPTIME
CALENDAR C= CALENDAR
CRITERIA Lines 1-20 CRITERIA
The control statements that print this report are contained in the CAJERM03.0
source member (shown following). If any of the criteria is longer than 20 lines,
you will have to add additional PRINT statements, in addition to modifying
the SET statement above. (If you modify any of the source members provided,
be sure to copy them with a different name so so a reinstallation of the
product will not replace the modified members.)
Chapter 5. Reports 5-163

5.13 Advantage CA-Earl Database Reports
GET CAIJMST
GOTO EOJ CAIJMST = 'E' OR CAIJMST = 'N'
REPORT 'JOB CRITERIA (BY SCHEDULE)'
CONTROL CRISCHNAME
PRINT CRISCHNAME CRIJNAME CRIJNO CRISTATION CRIDATETAB CRICAL CRILINE1
PRINT @ CRILINE1 CRILINE2
PRINT @ CRILINE1 CRILINE3
PRINT @ CRILINE1 CRILINE4
PRINT @ CRILINE1 CRILINE5
PRINT @ CRILINE1 CRILINE6
PRINT @ CRILINE1 CRILINE7
PRINT @ CRILINE1 CRILINE8
PRINT @ CRILINE1 CRILINE9
PRINT @ CRILINE1 CRILINE1
PRINT @ CRILINE1 CRILINE11
PRINT @ CRILINE1 CRILINE12
PRINT @ CRILINE1 CRILINE13
PRINT @ CRILINE1 CRILINE14
PRINT @ CRILINE1 CRILINE15
PRINT @ CRILINE1 CRILINE16
PRINT @ CRILINE1 CRILINE17
PRINT @ CRILINE1 CRILINE18
PRINT @ CRILINE1 CRILINE19
PRINT @ CRILINE1 CRILINE2
5-164 Unicenter CA-Scheduler Reference Guide, Part 2

5.14 Advantage CA-Earl History File Reports
5.14 Advantage CA-Earl History File Reports
5.14.1 Abended Job Profile
To obtain reports from the history file, the history file backup tape must be
created using the BACKUP HISTORY command, which copies history records
from the database to a sequential file. The ddname for this file is CAIJHST.
See the Unicanter CA-Scheduler Systems Programmer Guide for more information
on this command.
The Abended Job Profile report lists jobs that were terminated abnormally.
9/14/3 ABENDED JOB PROFILE PAGE 1
-------------------------------------------------------------------------------------------------------------------------------
SCHEDULE JOB JNO STATION REASON POWER SCHEDULED SCHEDULED AVAILABLE ACTUAL ACTUAL ELAPSED CPU COMPLETION
NAME NAME ID CODE JOBNO DATE TIME TIME ST-TIME END-TIME TIME TIME CODE
-------------------------------------------------------------------------------------------------------------------------------
DEMO CAJDEM3 1 4 1 747 9/14/3 12.41.59 12.43.4 12.43.41 12.43.42 1 X'2'
DEMO
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERH4
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The PRINT statement shown following produces a report with the fields
below:
Field on Report
SCHEDULE NAME
JOB NAME
JNO
STATION ID
REASON CODE
POWER JOBNO
SCHEDULED DATE
Meaning
Schedules jobs were assigned to.
Jobs selected for this report.
Number defined for job.
Stations where jobs were processed.
Reason job was selected.
The job number assigned by POWER.
The date the job was supposed to be selected.
Chapter 5. Reports 5-165

5.14 Advantage CA-Earl History File Reports
Field on Report
SCHEDULED TIME
AVAILABLE TIME
ACTUAL ST-TIME
ACTUAL END-TIME
ELAPSED TIME
CPU TIME
COMPLETION CODE
Meaning
The time the job was supposed to be selected
(usually AUTOTIM).
The time the job was available for processing:
start time was reached, predecessors were
satisfied, and resources were available.
The time the job actually started.
The time the job actually ended.
The time it took to process the job from start to
end.
The CPU processing time.
The DOS completion code.
The SYSIPT control statements for the report are contained in the CAJINH04.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJHST:FILE CAJCACC2 RECORD = 248
COPY CAJEJHR
COPY CAJEPM
COPY CAJERH4
END
The control statements that print this report are contained in the CAJERH04.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Job Information From
History File. You can also modify this report to select schedule fields; change
CAJESETH HHR to THR. The schedule fields that you can print are also listed.
(If you modify any of the source members provided, be sure to copy them
with a different name so a reinstallation of the product will not replace the
modified members.)
5-166 Unicenter CA-Scheduler Reference Guide, Part 2

5.14 Advantage CA-Earl History File Reports
5.14.2 Completed Job Profile
DEF SCHD_DATE (8) = ' ' 'SCHEDULED' 'DATE'
COPY CAIJDEFD
COPY CAJESETH
GET CAIJHST
GOTO EOJ CAIJHST = 'E' OR CAIJHST = 'N'
GOTO START JHRRECID NOT = 'H'
GOTO START JHRSTATUS NOT = 'A'
SET CAI_DATE = JHRSDATE
PERFORM CAI_DATE_CONVERSION
SET SCHD_DATE = CAI_OUTDATE
COPY CAIJSTMD
REPORT 'ABENDED JOB PROFILE'
CONTROL (JHRSCHNAME) SKIP JHRJNAME
PRINT JHRSCHNAME JHRJNAME JHRJNUMBER JHRSTATID JHRRCODE
JHRJOBNO SCHD_DATE JHRSCHTME JHRAVTME JHRACSTME
JHRACETME JHRELAPTME JHRCPUTME JHRCCODE
The Completed Job Profile report lists jobs that completed successfully.
9/14/3 COMPLETED JOB PROFILE PAGE 1
-------------------------------------------------------------------------------------------------------------------------------
SCHEDULE JOB JNO STATION REASON POWER SCHEDULED SCHEDULED AVAILABLE ACTUAL ACTUAL ELAPSED CPU COMPLETION
NAME NAME ID CODE JOBNO DATE TIME TIME ST-TIME END-TIME TIME TIME CODE
-------------------------------------------------------------------------------------------------------------------------------
CAJUCMD CAJUCMD1 1 4 1 51 9/14/3 15.56.56 15.57.42 15.57.48 15.58.51 1.3 X'1'
CAJUCMD CAJUCMD1 1 4 1 36 9/14/3 14.25.18 14.26.1 14.26.14 14.27.1 56 X'1'
CAJUCMD CAJUCMD1 1 4 1 9 9/14/3 12.33.12 12.34.32 12.34.48 12.36.9 1.21 X'1'
CAJUCMD
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERH3
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The PRINT statement following produces a report with the fields below:
Field on Report
SCHEDULE NAME
JOB NAME
JNO
Meaning
Schedules jobs were assigned to.
Jobs selected for this report.
Number defined for job.
Chapter 5. Reports 5-167

5.14 Advantage CA-Earl History File Reports
Field on Report
STATION ID
REASON CODE
POWER JOBNO
SCHEDULED DATE
SCHEDULED TIME
AVAILABLE TIME
ACTUAL ST-TIME
ACTUAL END-TIME
ELAPSED TIME
CPU TIME
COMPLETION CODE
Meaning
Stations where jobs were processed.
Reason the job was selected.
Job number assigned by POWER.
The date the job was supposed to be selected.
The time the job was supposed to be selected
(usually AUTOTIM).
The time the job was available for processing:
start time was reached, predecessors were
satisfied, and resources were available.
The time the job actually started.
The time the job actually ended.
The time it took to process the job from start to
end.
The CPU processing time.
The DOS completion code.
The SYSIN control statements for this report are contained in the CAJINH03.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJHST:FILE CAJCACC2 RECORD = 248
COPY CAJEJHR
COPY CAJEPM
COPY CAJERH3
END
The control statements that print this report are contained in the CAJERH03.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Job Information From
History File. You can also modify this report to select schedule fields; change
CAJESETH HHR to THR. The schedule fields you can print are also listed. (If
you modify any of the source members provided, be sure to copy them with a
different name so a reinstallation of the product will not replace the modified
members.)
5-168 Unicenter CA-Scheduler Reference Guide, Part 2

5.14 Advantage CA-Earl History File Reports
DEF SCHD_DATE (8) = ' ' 'SCHEDULED' 'DATE'
COPY CAIJDEFD
COPY CAJESETH
GET CAIJHST
GOTO EOJ CAIJHST = 'E' OR CAIJHST = 'N'
GOTO START JHRRECID NOT = 'H'
GOTO START JHRSTATUS NOT = 'C'
SET CAI_DATE = JHRSDATE
PERFORM CAI_DATE_CONVERSION
SET SCHD_DATE = CAI_OUTDATE
COPY CAIJSTMD
REPORT 'COMPLETED JOB PROFILE'
CONTROL (JHRSCHNAME) SKIP JHRJNAME
PRINT JHRSCHNAME JHRJNAME JHRJNUMBER JHRSTATID JHRRCODE
JHRJOBNO SCHD_DATE JHRSCHTME JHRAVTME JHRACSTME
JHRACETME JHRELAPTME JHRCPUTME JHRCCODE
5.14.3 Forced and Canceled Jobs
The Forced and Canceled Jobs report lists jobs that were forced or canceled by
online commands.
9/14/3 FORCED AND CANCELLED JOBS PAGE 1
-------------------------------------------------------------------------------------------------------------------------------
SCHEDULE JOB JNO STATION REASON POWER SCHEDULED SCHEDULED USERID USERID
NAME NAME ID CODE JOBNO DATE TIME FORCED CANCEL
-------------------------------------------------------------------------------------------------------------------------------
CAJUCMD CAJUCMD1 1 4 1 9/14/3 17.44.43 OPERATOR
CAJUCMD CAJUCMD1 1 4 1 9/14/3 17.47.2 OPERATOR
CAJUCMD CAJUCMD2 1 4 1 9/14/3 17.44.43 OPERATOR
CAJUCMD CAJUCMD2 1 4 1 9/14/3 12.33.12 OPERATOR
CAJUCMD CAJUCMD2 1 4 1 9/14/3 17.47.2 OPERATOR
CAJUCMD
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERH7
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The SYSIPT control statements for this report are contained in the CAJINH07.0
source member (shown following). You may modify the OPTION statement
values.
Chapter 5. Reports 5-169

5.14 Advantage CA-Earl History File Reports
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJHST:FILE CAJCACC2 RECORD = 248
COPY CAJEJHR
COPY CAJEPM
COPY CAJERH7
END
The control statements that print this report are contained in the CAJERH07.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Job Information From
History File. You can also modify this report to select schedule fields; change
CAJESETH from HHR to THR. The schedule fields you can print are also
listed. (If you modify any of the source members provided, be sure to copy
them with a different name so a reinstallation of the product will not replace
the modified members.)
DEF SCHD_DATE (8) = ' ' 'SCHEDULED' 'DATE'
COPY CAIJDEFD
COPY CAJESETH
GET CAIJHST
GOTO EOJ CAIJHST = 'E' OR CAIJHST = 'N'
GOTO START JHRRECID NOT = 'H'
GOTO START JHRUFRCE = ' ' AND JHRUCNCL = ' '
SET CAI_DATE = JHRSDATE
PERFORM CAI_DATE_CONVERSION
SET SCHD_DATE = CAI_OUTDATE
COPY CAIJSTMD
REPORT 'FORCED AND CACNCELLED JOBS'
CONTROL (JHRSCHNAME) SKIP JHRJNAME
PRINT JHRSCHNAME JHRJNAME JHRJNUMBER JHRSTATID JHRRCODE
JHRJOBNO SCHD_DATE JHRSCHTME JHRUFRCE JHRUCNCL
The preceding PRINT statement produces a report with the following fields:
Field on Report
SCHEDULE NAME
JOB NAME
JNO
STATION ID
REASON CODE
POWER JOBNO
SCHEDULED DATE
SCHEDULED TIME
USERID FORCED
Meaning
Schedules jobs were assigned to.
Jobs selected for this report.
Number defined for job.
Stations where jobs were processed.
Reason job was selected.
Job number assigned by POWER.
The date the job was supposed to be selected.
The time the job was supposed to be selected
(usually AUTOTIM)
The user that issued the FORCE command.
5-170 Unicenter CA-Scheduler Reference Guide, Part 2

5.14 Advantage CA-Earl History File Reports
Field on Report
USERID CANCEL
Meaning
The user that issued the CANCEL command.
5.14.4 Late Job Profile
The report lists jobs that were late.
9/14/3 LATE JOB PROFILE PAGE 1
------------------------------------------------------------------------------------------------------------------------------
SCHEDULE JOB JOB STATION REASON MUST MUST ACTUAL ACTUAL DEDLINE DEADLINE ACTUAL ACTUAL
NAME NAME NUMBER ID CODE ST-DATE TIME ST-DATE ST-TIME DATE TIME END-DATE END-TIME
------------------------------------------------------------------------------------------------------------------------------
SCD1 JOB1A 1 4 84 9/14/3 9. 9/14/3 11.43.56 9/15/3 1. 9/14/3 11.44.3
SCD1 JOB1A 1 4 84 9/14/3 9. 9/14/3 11.43.56 9/15/3 1. 9/14/3 11.44.3
SCD2 JOB2A 1 4 1 9/14/3 8. 9/15/3 1.
TBIL33 DOPBIL29 1 4 1 9/14/3 23. 9/15/3 1.
TBIL33 DOPBI5 1 4 1 9/14/3 23.3 9/15/3 1.3
TBIL33 DOPBI5 1 4 1 9/14/3 23.3 9/15/3 1.3
TBIL33 DOPFB11 1 4 3 9/14/3 2. 9/15/3 2.3
TBIL33 DOPFB11 1 4 3 9/14/3 2. 9/15/3 2.3
TBIL33 DOPFB11 1 4 3 9/14/3 2. 9/15/3 2.3
TBIL33 DOPFB11 1 4 3 9/14/3 2. 9/15/3 2.3
TBIL33 DOPFB11 1 4 3 9/14/3 2. 9/15/3 2.3
TBIL33 DOPFB11 1 4 3 9/14/3 2. 9/15/3 2.3
TBIL33 DOPFB11 1 4 3 9/14/3 2. 9/15/3 2.3
END OF REPORT
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERH5
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The SYSIPT control statements for this report are contained in the CAJINH05.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJHST:FILE CAJCACC2 RECORD = 248
COPY CAJEJHR
COPY CAJEPM
COPY CAJERH5
END
Chapter 5. Reports 5-171

5.14 Advantage CA-Earl History File Reports
The PRINT statement following produces a report with the fields below:
Field on Report
SCHEDULE NAME
JOB NAME
JOB NUMBER
STATION ID
REASON CODE
MUST ST-DATE
MUST TIME
ACTUAL ST-DATE
ACTUAL ST-TIME
DEDLINE DATE
DEADLINE TIME
ACTUAL END-DATE
ACTUAL END-TIME
Meaning
Schedules jobs were assigned to.
Jobs selected for this report.
Number defined for job.
Stations where jobs were processed.
Reason job was selected.
MUST START BY date, if defined. (This is the dd
value defined for MUST START BY TIME.)
MUST START BY TIME, if defined.
The date the job actually started.
The time the job actually started.
COMPLETION DEADLINE date, if defined. (This
is the dd value defined for COMPLETION
DEADLINE TIME.)
COMPLETION DEADLINE TIME, if defined.
The date the job actually ended.
The time the job actually ended.
The control statements that print this report are contained in the CAJERH05.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Job Information From
History File. You can also modify this report to select schedule fields; change
CAJESETH in the appendix "Advantage CA-Earl Reports" from HHR to THR.
The schedule fields you can print are also listed in the appendix "Advantage
CA-Earl Reports." (If you modify any of the source members provided, be
sure to copy them with a different name so a reinstallation of the product will
not replace the modified members.)
5-172 Unicenter CA-Scheduler Reference Guide, Part 2

5.14 Advantage CA-Earl History File Reports
5.14.5 Pending Job Profile
DEF MUST_DATE (8) = ' ' 'MUST ' 'ST-DATE'
DEF ACTS_DATE (8) = ' ' 'ACTUAL' 'ST-DATE'
DEF DEAD_DATE (8) = ' ' 'DEDLINE' 'DATE'
DEF ACTE_DATE (8) = ' ' 'ACTUAL' 'END-DATE'
COPY CAIJDEFD
COPY CAJESETH
GET CAIJHST
GOTO EOJ CAIJHST = 'E' OR CAIJHST = 'N'
GOTO START JHRRECID NOT = 'H'
GOTO START JHRLATE NOT = 'L'
SET CAI_DATE = JHRMDATE
PERFORM CAI_DATE_CONVERSION
SET MUST_DATE = CAI_OUTDATE
SET CAI_DATE = JHRACTSD
PERFORM CAI_DATE_CONVERSION
SET ACTS_DATE = CAI_OUTDATE
SET CAI_DATE = JHRDDATE
PERFORM CAI_DATE_CONVERSION
SET DEAD_DATE = CAI_OUTDATE
SET CAI_DATE = JHRACTED
PERFORM CAI_DATE_CONVERSION
SET ACTE_DATE = CAI_OUTDATE
COPY CAIJSTMD
REPORT 'LATE JOB PROFILE'
CONTROL JHRSCHNAME JHRJNAME JHRSTATID
PRINT JHRSCHNAME JHRJNAME JHRJNUMBER JHRSTATID JHRRCODE
MUST_DATE JHRMTIME ACTS_DATE JHRACSTME
DEAD_DATE JHRDTIME ACTE_DATE JHRACETME
The Pending Job Profile report lists jobs that had not completed by the end of
the day and tells why they had not completed.
9/14/3 PENDING JOB PROFILE PAGE 1
-------------------------------------------------------------------------------------------------------------------------------
SCHEDULE JOB JOB STATION REASON MUST MUST DEDLINE DEADLINE STATUS JOB
NAME NAME NUMBER ID CODE ST-DATE TIME DATE TIME STATUS
-------------------------------------------------------------------------------------------------------------------------------
SCD4 JOB4B 1 4 1 9/14/3 9/14/3 P WAITING PREDS
SCD4 JOB4B 1 4 1 9/14/3 9/14/3 P WAITING PREDS
SCD4 JOB4B 1 4 1 9/14/3 9/14/3 P WAITING PREDS
SCD4 JOB4B 1 4 1 9/14/3 9/14/3 P WAITING PREDS
SCD4 JOB4C 1 4 1 9/14/3 9/14/3 P WAITING PREDS
SCD4 JOB4C 1 4 1 9/14/3 9/14/3 P WAITING PREDS
SCD4 JOB4C 1 4 1 9/14/3 9/14/3 P WAITING PREDS
SCD4 JOB4C 1 4 1 9/14/3 9/14/3 P WAITING PREDS
SCD4
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
Chapter 5. Reports 5-173

5.14 Advantage CA-Earl History File Reports
// JOB CAJERH6
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The SYSIPT control statements for this report are contained in the CAJINH06.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJHST:FILE CAJCACC2 RECORD = 248
COPY CAJEJHR
COPY CAJEPM
COPY CAJERH6
END
The PRINT statement following produces a report with the fields below:
Field on Report
SCHEDULE NAME
JOB NAME
JOB NUMBER
STATION ID
REASON CODE
MUST ST-DATE
MUST TIME
DEDLINE DATE
DEADLINE TIME
STATUS
JOB STATUS
Meaning
Schedules jobs were assigned to.
Jobs selected for this report.
Number defined for job.
Stations where jobs were processed.
Reason job was selected.
MUST START BY date, if defined. (This is the dd
value defined for MUST START BY TIME.)
MUST START BY TIME, if defined.
COMPLETION DEADLINE date, if defined. (This
is the dd value defined for COMPLETION
DEADLINE TIME.)
COMPLETION DEADLINE TIME, if defined.
Final status code from history record.
Final status as shown on status display. This tells
why the job was not available for processing.
The control statements that print this report are contained in the CAJERH06.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Job Information From
History File. You can also modify this report to select schedule fields; change
CAJESETH in the appendix "Advantage CA-Earl Reports" from HHR to THR.
The schedule fields you can print are also listed in the appendix "Advantage
5-174 Unicenter CA-Scheduler Reference Guide, Part 2

5.14 Advantage CA-Earl History File Reports
CA-Earl Reports." (If you modify any of the source members provided, be
sure to copy them with a different name so a reinstallation of the product will
not replace the modified members.)
DEF IN_STATUS (1) = ' '
DEF OUT_STATUS (2) = ' ' 'JOB' 'STATUS'
DEF MUST_DATE (8) = ' ' 'MUST ' 'ST-DATE'
DEF DEAD_DATE (8) = ' ' 'DEDLINE' 'DATE'
COPY CAIJDEFD
COPY CAJESETH
GET CAIJHST
GOTO EOJ CAIJHST = 'E' OR CAIJHST = 'N'
GOTO START JHRRECID NOT = 'H'
GOTO START JHRSTATUS NOT = 'T' AND JHRSTATUS NOT = 'P' AND
JHRSTATUS NOT = 'R' AND JHRSTATUS NOT = 'O'
SET CAI_DATE = JHRMDATE
PERFORM CAI_DATE_CONVERSION
SET MUST_DATE = CAI_OUTDATE
SET CAI_DATE = JHRDDATE
PERFORM CAI_DATE_CONVERSION
SET DEAD_DATE = CAI_OUTDATE
SET IN_STATUS = JHRSTATUS
PERFORM DECODE_STATUS
COPY CAJECNVS
COPY CAIJSTMD
REPORT 'PENDING JOB PROFILE'
CONTROL (JHRSCHNAME) SKIP JHRJNAME
PRINT JHRSCHNAME JHRJNAME JHRJNUMBER JHRSTATID JHRRCODE
MUST_DATE JHRMTIME DEAD_DATE JHRDTIME
JHRSTATUS OUT_STATUS
5.14.6 Scheduled Job Status (by Schedule)
The Scheduled Job Status report lists job status information from the Unicenter
CA-Scheduler history file, sorted by schedule.
9/14/3 SCHEDULED JOB STATUS (BY SCHEDULE) PAGE 1
-------------------------------------------------------------------------------------------------------------------------------
SCHEDULE JOB JOB STATION REASON SCHEDULED SCHEDULED ACTUAL ACTUAL AVAILABLE ELAPSED STATUS JOB
NAME NAME NUMBER ID CODE DATE TIME ST-TIME END-TIME TIME TIME STATUS
-------------------------------------------------------------------------------------------------------------------------------
BNSPE1 BNPAY1 1 4 84 9/14/3 19.13.23 19.13.23 P WAITING PREDS
BNSPE1 BNPAY1 1 39 3 9/14/3 19.13.23 19.13.23 19.13.23 S STARTED
BNSPE1 BNPAY1 1 2 3 9/14/3 19.13.23 19.13.23 19.13.23 S STARTED
BNSPE1 BNPAY1 1 2 3 9/14/3 9.25.28 9.25.28 9.25.28 S STARTED
BNSPE1 BNPAY1 1 2 3 9/14/3 9.25.28 9.25.28 9.25.28 S STARTED
BNSPE1 BNPAY1 1 2 3 9/14/3 9.25.28 9.25.28 9.25.28 N OPERATOR CANCELD
BNSPE1 BNPAY2 1 4 1 9/14/3 19.13.23 19.13.23 Q SUBMITTED
BNSPE1 BNPAY3 1 4 1 9/14/3 9.25.28 N OPERATOR CANCELD
BNSPE1 BNPAY3 1 4 1 9/14/3 19.13.23 19.14.17 19.14.17 19.13.23 C COMPLETED
BNSPE1 BNPAY4 1 4 1 9/14/3 9.25.28 N OPERATOR CANCELD
BNSPE1 BNPAY4 1 4 1 9/14/3 19.13.23 B NO BACKLOG CANCLED
BNSPE1 BNPAY5 1 4 5 9/14/3 19.13.23 B NO BACKLOG CANCLED
BNSPE1 BNPAY6 1 4 1 9/14/3 9.25.28 P WAITING PREDS
BNSPE1 BNPAY6 1 4 1 9/14/3 9.25.28 P WAITING PREDS
BNSPE1 BNPAY6 1 4 1 9/14/3 9.25.28 N OPERATOR CANCELD
BNSPE1 BNPAY6 1 4 1 9/14/3 19.13.23 19.14.18 19.14.19 19.13.23 1 A ABENDED
BNSPE1
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
Chapter 5. Reports 5-175

5.14 Advantage CA-Earl History File Reports
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERH1
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The SYSIPT control statements for this report are contained in the CAJINH01.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJHST:FILE CAJCACC2 RECORD = 248
COPY CAJEJHR
COPY CAJEPM
COPY CAJERH1
END
The PRINT statement following produces a report with the fields below:
Field on Report
SCHEDULE NAME
JOB NAME
JOB NUMBER
STATION ID
REASON CODE
SCHEDULED DATE
SCHEDULED TIME
ACTUAL ST-TIME
ACTUAL END-TIME
AVAILABLE TIME
ELAPSED TIME
STATUS
JOB STATUS
Meaning
Schedules jobs were assigned to.
Jobs selected for this report.
Number defined for job.
Stations where jobs were processed.
Reason job was selected.
Date job was selected.
Time job was selected (usually AUTOTIM).
Time job actually started.
Time job actually ended.
Time job was available for processing: start time
was reached, predecessors were satisfied, and
resources were available.
Time it took to process the job from start to end.
Final status code from history record.
Final status as shown on status display.
5-176 Unicenter CA-Scheduler Reference Guide, Part 2

5.14 Advantage CA-Earl History File Reports
The control statements that print this report are contained in the CAJERH01.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Job Information From
History File. You can also modify this report to select schedule fields; change
CAJESETH in the appendix "Advantage CA-Earl Reports" from HHR to THR.
The schedule fields you can print are also listed in the appendix "Advantage
CA-Earl Reports." (If you modify any of the source members provided, be
sure to copy them with a different name so a reinstallation of the product will
not replace the modified members.)
DEF SCHD_DATE (8) = ' ' 'SCHEDULED' 'DATE'
DEF IN_STATUS (1) = ' '
DEF OUT_STATUS (2) = ' ' 'JOB' 'STATUS'
COPY CAIJDEFD
COPY CAJESETH
GET CAIJHST
GOTO EOJ CAIJHST = 'E' OR CAIJHST = 'N'
GOTO START JHRRECID NOT = 'H'
SET CAI_DATE = JHRSDATE
PERFORM CAI_DATE_CONVERSION
SET SCHD_DATE = CAI_OUTDATE
SET IN_STATUS = JHRSTATUS
PERFORM DECODE_STATUS
COPY CAIJSTMD
COPY CAJECNVS
REPORT 'SCHEDULED JOB STATUS (BY SCHEDULE)'
CONTROL (JHRSCHNAME) SKIP JHRJNAME
PRINT JHRSCHNAME JHRJNAME JHRJNUMBER JHRSTATID JHRRCODE
SCHD_DATE JHRSCHTME JHRACSTME JHRACETME JHRAVTME
JHRELAPTME JHRSTATUS OUT_STATUS
Chapter 5. Reports 5-177

5.14 Advantage CA-Earl History File Reports
5.14.7 Scheduled Job Status (by Station)
The Scheduled Job Status (by Station) report lists job status information from
the Unicenter CA-Scheduler history file, sorted by station.
9/14/3 SCHEDULED JOB STATUS (BY STATION) PAGE 1
-------------------------------------------------------------------------------------------------------------------------------
STATION SCHEDULE JOB JOB REASON SCHEDULED SCHEDULED ACTUAL ACTUAL AVAILABLE ELAPSED STATUS JOB
ID NAME NAME NUMBER CODE DATE TIME ST-TIME END-TIME TIME TIME STATUS
-------------------------------------------------------------------------------------------------------------------------------
4 SCD6 JOB6A 1 84 9/14/3 9.27.2 11.18.54 11.18.58 11.18.49 4 A ABENDED
4 SCD6 JOB6A 1 84 9/14/3 9.27.2 11.18.54 11.18.58 11.18.49 4 N OPERATOR CANCELLED
4 SCD6 JOB6A 1 88 9/14/3 11.32.6 11.35.37 11.35.4 11.35.14 3 C COMPLETED
4 SCD6 JOB6A 1 88 9/14/3 11.42.36 11.43.58 11.44. 11.43.52 2 A ABENDED
4 SCD6 JOB6A 1 88 9/14/3 11.42.36 11.43.58 11.44. 11.43.52 2 N OPERATOR CANCELLED
4 SCD7 JOB7A 1 88 9/14/3 11.42.37 11.44.1 11.44.13 11.43.52 3 A ABENDED
4 SCD7 JOB7A 1 88 9/14/3 11.42.37 11.44.1 11.44.13 11.43.52 3 N OPERATOR CANCELLED
4 SCD7 JOB7B 1 88 9/14/3 11.42.37 11.44.44 11.44.44 11.44.43 F FAILED
4 SCD7 JOB7B 1 88 9/14/3 11.42.37 11.47.4 11.47.42 11.47.37 2 A ABENDED
4 SCD7 JOB7B 1 88 9/14/3 11.42.37 11.47.4 11.47.42 11.47.37 2 N OPERATOR CANCELLED
4 SCD7 JOB7C 1 88 9/14/3 11.32.1 11.36. 11.36.5 11.35.14 5 C COMPLETED
4 SCD7 JOB7C 1 88 9/14/3 11.42.37 11.47.41 11.47.49 11.47.37 8 A ABENDED
4 SCD7 JOB7C 1 88 9/14/3 11.42.37 11.47.41 11.47.49 11.47.37 8 N OPERATOR CANCELLED
4 SCD7 JOB7D 1 88 9/14/3 11.42.37 11.47.44 11.47.46 11.47.37 2 A ABENDED
4 SCD7 JOB7D 1 88 9/14/3 11.42.37 11.47.44 11.47.46 11.47.37 2 N OPERATOR CANCELLED
4 SCD7 JOB7E 1 88 9/14/3 11.42.37 11.47.51 11.47.55 11.47.37 4 A ABENDED
4 SCD7 JOB7E 1 88 9/14/3 11.42.37 11.47.51 11.47.55 11.47.37 4 N OPERATOR CANCELLED
4 SCOTTA DYNDA$7 1 88 9/14/3 11.18.45 B NO BACKLOG CANCELLED
4 SCOTTA DYNDA$7 2 1 9/14/3 11.18.45 B NO BACKLOG CANCELLED
4 SCOTTA DYNDB$7 1 1 9/14/3 11.18.45 B NO BACKLOG CANCELLED
4 SCOTTA VMFGN$7 1 1 9/14/3 11.18.45 B NO BACKLOG CANCELLED
4 SCOTTF SCOTTF 1 84 9/14/3 8..17 8..27 8..28 8..17 1 C COMPLETED
4 TBIL33 DOPFB11 1 3 9/14/3 9.27.2 1.45.1 Q SUBMITTED
4 TBIL33 DOPFB11 1 3 9/14/3 9.27.2 1.45.1 Q SUBMITTED
4 TBIL33 DOPFB11 1 3 9/14/3 9.27.2 1.45.1 Q SUBMITTED
4 TBIL33 DOPFB11 1 3 9/14/3 9.27.2 1.45.1 Q SUBMITTED
4 TBIL33 DOPFB11 1 3 9/14/3 9.27.2 1.45.1 Q SUBMITTED
4 TBIL33 DOPFB11 1 3 9/14/3 9.27.2 1.45.1 Q SUBMITTED
4 TBIL33 DOPFB11 1 3 9/14/3 9.27.2 1.45.1 Q SUBMITTED
4 TBIL33 DOPBIL29 1 1 9/14/3 9.27.2 22.5. Q SUBMITTED
4 TBIL33 DOPBI5 1 1 9/14/3 9.27.2 22.5. P WAITING PREDS
4 TBIL33 DOPBI5 1 1 9/14/3 9.27.2 22.5. P WAITING PREDS
4
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERH2
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The PRINT statement following produces a report with the fields below:
Field on Report
SCHEDULE NAME
Meaning
Schedules jobs were assigned to.
5-178 Unicenter CA-Scheduler Reference Guide, Part 2

5.14 Advantage CA-Earl History File Reports
Field on Report
JOB NAME
JOB NUMBER
REASON CODE
SCHEDULED DATE
SCHEDULED TIME
ACTUAL ST-TIME
ACTUAL END-TIME
AVAILABLE TIME
ELAPSED TIME
STATUS
JOB STATUS
Meaning
Jobs selected for this report.
Number defined for job.
Reason job was selected.
Date job was selected.
Time job was selected (usually AUTOTIM).
Time job actually started.
Time job actually ended.
Time job was available for processing: start time
was reached, predecessors were satisfied, and
resources were available.
Time it took to process job from start to end.
Final status code from history record.
Final status as shown on status display.
The SYSIPT control statements for this report are contained in the CAJINH02.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJHST:FILE CAJCACC2 RECORD = 248
COPY CAJEJHR
COPY CAJEPM
COPY CAJERH2
END
The control statements that print this report are contained in the CAJERH02.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Job Information From
History File. You can also modify this report to select schedule fields; change
CAJESETH in the appendix "Advantage CA-Earl Reports" from HHR to THR.
The schedule fields you can print are also listed in the appendix "Advantage
CA-Earl Reports." (If you modify any of the source members provided, be
sure to copy them with a different name so a reinstallation of the product will
not replace the modified members.)
Chapter 5. Reports 5-179

5.14 Advantage CA-Earl History File Reports
DEF SCHD_DATE (8) = ' ' 'SCHEDULED' 'DATE'
DEF IN_STATUS (1) = ' '
DEF OUT_STATUS (2) = ' ' 'JOB' 'STATUS'
COPY CAIJDEFD
COPY CAJESETH
GET CAIJHST
GOTO EOJ CAIJHST = 'E' OR CAIJHST = 'N'
GOTO START JHRRECID NOT = 'H'
SET CAI_DATE = JHRSDATE
PERFORM CAI_DATE_CONVERSION
SET SCHD_DATE = CAI_OUTDATE
SET IN_STATUS = JHRSTATUS
PERFORM DECODE_STATUS
COPY CAIJSTMD
COPY CAJECNVS
REPORT 'SCHEDULED JOB STATUS (BY STATION)'
CONTROL (JHRSTATID) SKIP JHRSCHNAME
PRINT JHRSTATID JHRSCHNAME JHRJNAME JHRJNUMBER JHRRCODE
SCHD_DATE JHRSCHTME JHRACSTME JHRACETME JHRAVTME
JHRELAPTME JHRSTATUS OUT_STATUS
5-180 Unicenter CA-Scheduler Reference Guide, Part 2

5.15 Advantage CA-Earl Tracking File Reports
5.15 Advantage CA-Earl Tracking File Reports
5.15.1 Abended Job Profile
When reports are generated using the tracking file for input, the data reflected
will be from the current day's work (autoscan+23.59).
The Abended Job Profile report lists abended job information from the
Unicenter CA-Scheduler tracking file. Information is sorted by schedule.
9/14/3 ABENDED JOB PROFILE PAGE 1
AT 16.11.4
-------------------------------------------------------------------------------------------------------------------------------
SCHEDULE JOB JNO ST. REASON POWER SCHEDULED ACTUAL ACTUAL ACTUAL ACTUAL CPU COMPLETION
NAME NAME ID CODE JOBNO DATE SCHDTIME AVLTIME STRTTIME END-TIME TIME CODE
-------------------------------------------------------------------------------------------------------------------------------
ABBRV ABBRV 1 4 88 179 9/14/3 16.5.58 16.5.58 16.6.34 16.6.4 X'2'
ABBRV
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERT4
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The PRINT statement following produces a report with the fields below:
Field on Report
SCHEDULE NAME
JOB NAME
JNO
ST ID
REASON CODE
POWER JOBNO
SCHEDULED DATE
ACTUAL SCHDTIME
Meaning
Schedules jobs were assigned to.
Jobs that abended.
Number defined for job.
Stations where jobs were processed.
The reason the job was selected.
Job number assigned by POWER.
The date the job was supposed to be selected.
The time the job was actually selected.
Chapter 5. Reports 5-181

5.15 Advantage CA-Earl Tracking File Reports
Field on Report
ACTUAL AVLTIME
ACTUAL STRTTIME
ACTUAL END-TIME
CPU TIME
COMPLETION CODE
Meaning
The time the job was available for processing:
start time was reached, predecessors were
satisfied, and resources were available.
The time the job actually started.
The time the job actually ended.
The CPU processing time.
The job's completion code.
The SYSIPT control statements for this report are contained in the CAJINT04.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJTRK:FILE CAJCACC2 RECORD = 248
COPY CAJEJTR
COPY CAJEPM
COPY CAJERT4
END
The control statements that print this report are contained in the CAJERT04.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Job Information From
Tracking File. (If you modify any of the source members provided, be sure to
copy them with a different name so a reinstall of the product will not replace
the modified members.)
5-182 Unicenter CA-Scheduler Reference Guide, Part 2

5.15 Advantage CA-Earl Tracking File Reports
5.15.2 Canceled Jobs
! REDEFINE FOR PRMONODE (ORIGIN NODE-ID IN JTR KEY)
!
DEF PRMONODE = PRMWRK 1-8 X
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
DEF SCHD_DATE (8) = ' ' 'SCHEDULED' 'DATE'
DEF GETUNIQ (8) = 'GETUNIQ '
COPY CAIJDEFD
!
IF PRMNME = GETUNIQ THEN GOTO EOJ
ENDIF
!
COPY CAJESETT
!
GET CAIJTRK
GOTO EOJ CAIJTRK = 'E' OR CAIJTRK = 'N'
GOTO START JTRRECID NOT = 'J'
GOTO START JTRRSTAT NOT = M'111'
!
SET CAI_DATE = JTRSDATE
PERFORM CAI_DATE_CONVERSION
SET SCHD_DATE = CAI_OUTDATE
COPY CAIJSTMD
REPORT 'ABENDED JOB PROFILE'
TITLE 'AT' 4 TIMEOFREPORT
CONTROL (JTRSCHNAME) SKIP JTRJNAME
PRINT JTRSCHNAME JTRJNAME JTRJNUMBER JTRSTATID JTRRC
JTRPWSEQ SCHD_DATE JTRATIME JTRVTIME JTRSTIME
JTRETIME JTRCPUT JTRCC
The Canceled Jobs report lists canceled job information from the Unicenter
CA-Scheduler tracking file.
9/14/3 CANCELLED JOBS PAGE 1
AT 11.5.52
-------------------------------------------------------------------------------------------------------------------------------
SCHEDULE JOB JOB STATN REASON SCHEDULED ACTUAL HOLD
NAME NAME NMBR ID CODE DATE SCHDTIME STATUS
-------------------------------------------------------------------------------------------------------------------------------
DEMO CAJDEM3 1 39 84 11.1.29 CANCELED BY DEBK
DEMO CAJDEM5 1 4 84 11.1.29 CANCELED BY DEBK
DEMO
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
Chapter 5. Reports 5-183

5.15 Advantage CA-Earl Tracking File Reports
// JOB CAJERT7
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The PRINT statement following produces a report with the fields below:
Field on Report
SCHEDULE NAME
JOB NAME
JOB NMBR
STATN ID
REASON CODE
SCHEDULED DATE
ACTUAL SCHDTIME
HOLD STATUS
Meaning
Schedules jobs were assigned to.
Jobs that completed.
Number defined for job.
Stations where jobs were processed.
The reason the job was selected.
The date the job was supposed to be selected.
The time the job was actually selected.
Whether the job was in HELD status.
The SYSIPT control statements for this report are contained in the CAJINT07.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJTRK:FILE CAJCACC2 RECORD = 248
COPY CAJEJTR
COPY CAJEPM
COPY CAJERT7
END
The control statements that print this report are contained in the CAJERT07.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are listed in the appendix
"Advantage CA-Earl Reports" in the topic Job Information From Tracking File.
(If you modify any of the source members provided, be sure to copy them
with a different name so a reinstall of the product will not replace the
modified members.)
5-184 Unicenter CA-Scheduler Reference Guide, Part 2

5.15 Advantage CA-Earl Tracking File Reports
! REDEFINE FOR PRMONODE (ORIGIN NODE-ID IN JTR KEY)
DEF PRMONODE = PRMWRK 1-8 X
!
DEF SCHD_DATE (8) = ' ' 'SCHEDULED' 'DATE'
!
DEF IN_RSTAT (B 3.) =
DEF IN_HSTAT (B 3.) =
DEF IN_FLG1 (B 3.) =
DEF IN_FLG4 (B 3.) =
!
DEF OUT_HSTAT (2) = ' ' 'HOLD' 'STATUS'
DEF OUT_HSTAT_MSG = OUT_HSTAT 1-12 X
DEF OUT_HSTAT_USERID = OUT_HSTAT 13-2 X
!
DEF OUT_RSTAT (2) = ' ' 'RUN' 'STATUS'
DEF GETUNIQ (8) = 'GETUNIQ '
!
COPY CAIJDEFD
!
IF PRMNME = GETUNIQ THEN GOTO EOJ
ENDIF
!
COPY CAJESETT
GET CAIJTRK
!
GOTO EOJ CAIJTRK = 'E' OR CAIJTRK = 'N'
GOTO START JTRRECID NOT = 'J'
GOTO START JTRHSTAT NOT = M'11' M'11'
!
SET IN_HSTAT = JTRHSTAT
SET IN_RSTAT = JTRRSTAT
SET IN_FLG1 = JTRFLG1
SET IN_FLG4 = JTRFLG4
PERFORM DECODE_STATUS
!
! IF JOB HELD OR CANCELED BY USER CHANGE OUTPUT STATUS MESSAGE
SET COMPL_CODE = JTRCC
IF IN_HSTAT = M'1' THEN SET OUT_HSTAT_USERID = JTRCMHLD
ENDIF
IF IN_HSTAT = M'11' THEN SET OUT_HSTAT_USERID = JTRCMCNC
ENDIF
!
SET CAI_DATE = JTRSDATE
PERFORM CAI_DATE_CONVERSION
SET SCHD_DATE = CAI_OUTDATE
COPY CAIJSTMD
COPY CAJECNV
REPORT 'CANCELLED JOBS'
TITLE 'AT' 4 TIMEOFREPORT
CONTROL (JTRSCHNAME) SKIP JTRJNAME
PRINT JTRSCHNAME JTRJNAME JTRJNUMBER JTRSTATID JTRRC
SCHD_DATE JTRATIME OUT_HSTAT
Chapter 5. Reports 5-185

5.15 Advantage CA-Earl Tracking File Reports
5.15.3 Completed Job Profile
The Completed Job Profile report lists completed job information from the
Unicenter CA-Scheduler tracking file.
9/14/3 COMPLETED JOB PROFILE PAGE 1
AT 14.1.5
-------------------------------------------------------------------------------------------------------------------------------
SCHEDULE JOB JOB STATN REASON SCHEDULED ACTUAL ACTUAL ACTUAL ACTUAL CPU COMPLETION
NAME NAME NMBR ID CODE DATE SCHDTIME AVLTIME STRTTIME END-TIME TIME CODE
-------------------------------------------------------------------------------------------------------------------------------
DJKS1 DJKS1CA 1 4 3 9/14/3 8..36 9.54.7 9.55.6 9.55.15 x'1'
DJKS1 DJKS1IBM 1 4 3 9/14/3 8..36 9.54.7 9.55.6 9.55.16 1 x'1'
DJKS1 IEBCOMPR 1 4 1 9/14/3 8..36 9.55.5 9.55.26 9.55.29 x'1'
DJKS1
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERT3
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The PRINT statement following produces a report with the fields below:
Field on Report
SCHEDULE NAME
JOB NAME
JOB NMBR
STATN ID
REASON CODE
SCHEDULED DATE
ACTUAL SCHDTIME
ACTUAL AVLTIME
ACTUAL STRTTIME
ACTUAL END-TIME
CPU TIME
Meaning
Schedules jobs were assigned to.
Jobs that completed.
Number defined for job.
Stations where jobs were processed.
The reason the job was selected.
The date the job was supposed to be selected.
The time the job was actually selected.
The time the job was available for processing:
start time was reached, predecessors were
satisfied, and resources were available.
The time the job actually started.
The time the job actually ended.
The CPU processing time.
5-186 Unicenter CA-Scheduler Reference Guide, Part 2

5.15 Advantage CA-Earl Tracking File Reports
Field on Report
COMPLETION CODE
Meaning
The job's completion code.
The SYSIPT control statements for this report are contained in the CAJINT03.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJTRK:FILE CAJCACC2 RECORD = 248
COPY CAJEJTR
COPY CAJEPM
COPY CAJERT3
END
The control statements that print this report are contained in the CAJERT03.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Job Information From
Tracking File. (If you modify any of the source members provided, be sure to
copy them with a different name so a reinstall of the product will not replace
the modified members.)
! REDEFINE FOR PRMONODE (ORIGIN NODE-ID IN JTR KEY)
!
DEF PRMONODE = PRMWRK 1-8 X
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
DEF SCHD_DATE (8) = ' ' 'SCHEDULED' 'DATE'
DEF GETUNIQ (8) = 'GETUNIQ '
COPY CAIJDEFD
!
IF PRMNME = GETUNIQ THEN GOTO EOJ
ENDIF
!
COPY CAJESETT
GET CAIJTRK
GOTO EOJ CAIJTRK = 'E' OR CAIJTRK = 'N'
GOTO START JTRRECID NOT = 'J'
GOTO START JTRRSTAT NOT = M'111' M'111'
! M'111' = COMPLETED
! M'111' = OS PURGED
SET CAI_DATE = JTRSDATE
PERFORM CAI_DATE_CONVERSION
SET SCHD_DATE = CAI_OUTDATE
COPY CAIJSTMD
REPORT 'COMPLETED JOB PROFILE'
TITLE 'AT' 4 TIMEOFREPORT
CONTROL (JTRSCHNAME) SKIP JTRJNAME
PRINT JTRSCHNAME JTRJNAME JTRJNUMBER JTRSTATID JTRRC
SCHD_DATE JTRATIME JTRVTIME JTRSTIME JTRETIME
JTRCPUT JTRCC
Chapter 5. Reports 5-187

5.15 Advantage CA-Earl Tracking File Reports
5.15.4 Pending Job Profile
The Pending Job Profile report lists pending job information from the
Unicenter CA-Scheduler tracking file. The information is sorted by schedule.
9/14/3 PENDING JOB PROFILE PAGE 1
AT 14.1.22
-------------------------------------------------------------------------------------------------------------------------------
SCHEDULE JOB JOB STATN REASON MUST MUST-STRT DEDLINE DEADLINE JOB JOB
NAME NAME NMBR ID CODE ST-DATE TIME DATE TIME HOLD-STATUS RUN-STATUS
-------------------------------------------------------------------------------------------------------------------------------
DEMO CAJDEM3 1 39 84 9/14/3 9/14/3 CANCELED BY DEBK WAIT NON-CPU START
DEMO CAJDEM3 1 4 1 9/14/3 9/14/3 AUTO RECOVERY HELD WAITING PREDS
DEMO CAJDEM5 1 4 84 9/14/3 9/14/3 CANCELED BY DEBK WAITING USER SUBMIT
DEMO
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERT6
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The PRINT statement following produces a report with the fields below:
Field on Report
SCHEDULE NAME
JOB NAME
JOB NMBR
STATN ID
REASON CODE
MUST ST-DATE
MUST-STRT TIME
DEDLINE DATE
DEADLINE TIME
Meaning
Schedules jobs were assigned to.
Jobs that have not yet completed and were not
canceled.
Number defined for job.
Stations where jobs were processed.
The reason the job was selected.
MUST START BY date if one was defined.
(This is the dd value defined for MUST START
BY TIME.)
MUST START BY TIME, if defined.
COMPLETION DEADLINE date, if defined.
(This is the dd value defined for
COMPLETION DEADLINE TIME.)
COMPLETION DEADLINE TIME, if defined.
5-188 Unicenter CA-Scheduler Reference Guide, Part 2

5.15 Advantage CA-Earl Tracking File Reports
Field on Report
HOLD-STATUS
RUN-STATUS
Meaning
Whether the job was on hold.
The current status of the job.
The SYSIPT control statements for this report are contained in the CAJINT06.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJTRK:FILE CAJCACC2 RECORD = 248
COPY CAJEJTR
COPY CAJEPM
COPY CAJERT6
END
The control statements that print this report are contained in the CAJERT06.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Job Information From
Tracking File. (If you modify any of the source members provided, be sure to
copy them with a different name so a reinstall of the product will not replace
the modified members.)
Chapter 5. Reports 5-189

5.15 Advantage CA-Earl Tracking File Reports
! REDEFINE FOR PRMONODE (ORIGIN NODE-ID IN JTR KEY)
!
DEF PRMONODE = PRMWRK 1-8 X
DEF SCHD_DATE (8) = ' ' 'SCHEDULED' 'DATE'
!
DEF IN_HSTAT (B 3.) =
DEF IN_RSTAT (B 3.) =
DEF IN_FLG1 (B 3.) =
DEF IN_FLG4 (B 3.) =
!
DEF OUT_HSTAT (2) = ' ' 'JOB' 'HOLD-STATUS'
DEF OUT_HSTAT_MSG = OUT_HSTAT 1-12 X
DEF OUT_HSTAT_USERID = OUT_HSTAT 13-2 X
!
DEF OUT_RSTAT (2) = ' ' 'JOB' 'RUN-STATUS'
DEF MUST_DATE (8) = ' ' 'MUST ' 'ST-DATE'
DEF DEAD_DATE (8) = ' ' 'DEDLINE' 'DATE'
DEF COMPL_CODE (5) = ' ' 'COMPLETION' 'CODE'
DEF COMPL_CODE_SW (B 3.) =
DEF REJECT_SW (B 3.) =
DEF GETUNIQ (8) = 'GETUNIQ '
COPY CAIJDEFD
IF PRMNME = GETUNIQ THEN GOTO EOJ
ENDIF
COPY CAJESETT
GET CAIJTRK
!
SET REJECT_SW =
!
GOTO EOJ CAIJTRK = 'E' OR CAIJTRK = 'N'
GOTO START JTRRECID NOT = 'J'
GOTO START JTRRSTAT NOT = M'1' M'1'
M'11' M'11'
M'111'
!
IF (JTRRSTAT = M'11' AND JTRFLG1 NOT = M'XX1XXXXX') THEN
SET REJECT_SW = 1
ENDIF
IF (JTRRSTAT = M'111' AND JTRFLG4 NOT = M'X1XXXXXX') THEN
SET REJECT_SW = 1
ENDIF
!
GOTO START REJECT_SW = 1
!
SET CAI_DATE = JTRMUDT
PERFORM CAI_DATE_CONVERSION
SET MUST_DATE = CAI_OUTDATE
!
SET CAI_DATE = JTRDEDT
PERFORM CAI_DATE_CONVERSION
SET DEAD_DATE = CAI_OUTDATE
5-190 Unicenter CA-Scheduler Reference Guide, Part 2

5.15 Advantage CA-Earl Tracking File Reports
!
SET IN_HSTAT = JTRHSTAT
SET IN_RSTAT = JTRRSTAT
SET IN_FLG1 = JTRFLG1
SET IN_FLG4 = JTRFLG4
!
PERFORM DECODE_STATUS
!
! IF JOB HELD OR CANCELED BY USER CHANGE OUTPUT STATUS MESSAGE
!
IF IN_HSTAT = M'1' THEN SET OUT_HSTAT_USERID = JTRCMHLD
ENDIF
IF IN_HSTAT = M'11' THEN SET OUT_HSTAT_USERID = JTRCMCNC
ENDIF
!
COPY CAJECNV
COPY CAIJSTMD
REPORT 'PENDING JOB PROFILE'
TITLE 'AT' 4 TIMEOFREPORT
CONTROL (JTRSCHNAME) SKIP JTRJNAME
PRINT JTRSCHNAME JTRJNAME JTRJNUMBER JTRSTATID JTRRC
MUST_DATE JTRMUST DEAD_DATE JTRDEDLN
OUT_HSTAT OUT_RSTAT
5.15.5 Pending Schedules Report
The Pending Schedules report lists pending schedule information from the
Unicenter CA-Scheduler tracking file.
9/14/3 PENDING SCHEDULES REPORT PAGE 1
------------------------------------------------------------------------------------------------------------------------------
SCHEDULE SCHEDULING MUST MUST-STRT DEDLINE DEADLINE HOLD RUN
NAME REASON-CODE ST-DATE TIME DATE TIME STATUS STATUS
------------------------------------------------------------------------------------------------------------------------------
ARUN 1 9/14/3 9/14/3 ACTIVE WAITING PREDS
PRIORA 84 9/14/3 9/14/3 ACTIVE WAITING PREDS
PRIORB 84 9/14/3 9/14/3 ACTIVE WAITING PREDS
PRIORC 84 9/14/3 9/14/3 ACTIVE WAITING PREDS
PRIORD 84 9/14/3 9/14/3 ACTIVE WAITING PREDS
6DAYWK 84 9/14/3 9/14/3 ACTIVE WAITING START TIME
7DAYWK 84 9/14/3 9/14/3 ACTIVE WAITING START TIME
END OF REPORT
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERS6
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
Chapter 5. Reports 5-191

5.15 Advantage CA-Earl Tracking File Reports
The PRINT statement following produces a report with the fields below:
Field on Report
SCHEDULE NAME
SCHEDULING
REASON-CODE
MUST ST-DATE
MUST-STRT TIME
DEDLINE DATE
DEADLINE TIME
HOLD STATUS
RUN STATUS
Meaning
Schedules that have not yet completed and
were not canceled.
The reason the schedule was selected.
MUST START BY date if one was defined.
(This is the dd value defined for MUST START
BY TIME.)
MUST START BY TIME if one was defined.
COMPLETION DEADLINE date, if defined.
(This is the dd value defined for
COMPLETION DEADLINE TIME.)
COMPLETION DEADLINE TIME, if defined.
Whether this schedule was on hold
The current status of this schedule.
The SYSIPT control statements for this report are contained in the CAJINS06.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJTRK:FILE CAJCACC2 RECORD = 248
COPY CAJESTR
COPY CAJEPM
COPY CAJERS6
END
The control statements that print this report are contained in the CAJERS06.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Schedule Information
From Tracking File. (If you modify any of the source members provided, be
sure to copy them with a different name so a reinstall of the product will not
replace the modified members.)
5-192 Unicenter CA-Scheduler Reference Guide, Part 2

5.15 Advantage CA-Earl Tracking File Reports
! REDEFINE FOR PRMONODE (STRONODE IN RECORD KEY)
!
DEF PRMONODE = PRMWRK 1-8 X
DEF SCHD_DATE (8) = ' ' 'SCHEDULED' 'DATE'
DEF IN_HSTAT (B 3.) =
DEF IN_RSTAT (B 3.) =
DEF IN_FLG1 (B 3.) =
DEF IN_FLG4 (B 3.) =
DEF OUT_HSTAT (2) = ' ' 'JOB' 'HOLD-STATUS'
DEF OUT_RSTAT (2) = ' ' 'JOB' 'RUN-STATUS'
DEF MUST_DATE (8) = ' ' 'MUST ' 'ST-DATE'
DEF DEAD_DATE (8) = ' ' 'DEDLINE' 'DATE'
DEF COMPL_CODE (5) = ' ' 'COMPLETION' 'CODE'
DEF COMPL_CODE_SW (B 3.) =
DEF GETUNIQ (8) = 'GETUNIQ '
COPY CAIJDEFD
IF PRMSCH = GETUNIQ THEN GOTO EOJ
ENDIF
COPY CAJESETS
GET CAIJTRK
!
GOTO EOJ CAIJTRK = 'E' OR CAIJTRK = 'N'
GOTO START STRRECID NOT = 'S'
SET IN_HSTAT = STRHSTAT
SET IN_RSTAT = STRRSTAT
PERFORM DECODE_STATUS
!
IF (OUT_RSTAT = 'WAITING START TIME ' OR
OUT_RSTAT = 'WAITING PREDS ' OR
OUT_RSTAT = 'WAITING RESOURCES ' OR
OUT_RSTAT = 'WAITING PRE-CPU END ' OR
OUT_RSTAT = 'WAITING CPU JOB END ')
THEN GOTO ACCEPT
ELSE GOTO START
ENDIF
!
ACCEPT:
SET CAI_DATE = STRMUDT
PERFORM CAI_DATE_CONVERSION
SET MUST_DATE = CAI_OUTDATE
SET CAI_DATE = STRDEDT
PERFORM CAI_DATE_CONVERSION
SET DEAD_DATE = CAI_OUTDATE
COPY CAJECNV
COPY CAIJSTMD
REPORT 'PENDING SCHEDULES REPORT'
PRINT DOUBLE SPACING STRNAME STRRC
MUST_DATE STRMUST DEAD_DATE STRDEDLN
OUT_HSTAT OUT_RSTAT
Chapter 5. Reports 5-193

5.15 Advantage CA-Earl Tracking File Reports
5.15.6 Schedule Status
The Schedule Status report lists schedule status information from the Unicenter
CA-Scheduler tracking file.
5-194 Unicenter CA-Scheduler Reference Guide, Part 2

5.15 Advantage CA-Earl Tracking File Reports
on.
9/24/3 SCHEDULE STATUS PAGE 2
AT 11.1.59
-------------------------------------------------------------------------------------------------------------------------------
SCHEDULE SCHEDULING SCHEDULED ACTUAL ACTUAL ACTUAL HOLD RUN COMPLETION
NAME REASON-CODE DATE STRTTIME END-TIME AVLTIME STATUS STATUS CODE
-------------------------------------------------------------------------------------------------------------------------------
DEPENDBK 84 9/16/3 16.2.25 16.2.25 ACTIVE STARTED
DEPENDJB 84 9/16/3 16.2.25 16.2.25 ACTIVE STARTED
DJKBR14R 1 NOT REQUESTED SCHEDULED TO RUN
DJKNRQ 1 NOT REQUESTED SCHEDULED TO RUN
DJKS1 3 9/18/3 9.54.7 9.54.7 ACTIVE STARTED
NONMVS 84 9/16/3 16.2.25 16.2.25 ACTIVE STARTED
PRIORA 84 ACTIVE WAITING PREDS
PRIORB 84 ACTIVE WAITING PREDS
PRIORC 84 ACTIVE WAITING PREDS
PRIORD 84 ACTIVE WAITING PREDS
P24 84 9/2/3 12.35. 12.35. ACTIVE STARTED
P247 84 9/17/3 7.3. 7.3. ACTIVE STARTED
P6611379 88 9/18/3 12.59.54 12.59.54 ACTIVE STARTED
P6611383 84 9/19/3 9.54.34 9.54.34 ACTIVE STARTED
P72379 84 9/19/3 8.51.55 8.51.55 ACTIVE STARTED
ST 84 9/16/3 16.2.25 16.2.25 ACTIVE STARTED
TAMIR 88 9/23/3 6.46.3 6.46.3 ACTIVE STARTED
TSTA 1 NOT REQUESTED SCHEDULED TO RUN
6DAYWK 84 ACTIVE WAITING START TIME
7DAYWK 84 ACTIVE WAITING START TIME
END OF REPORT
off.
JCL that produces Advantage CA-Earl reports requires the inclusion
of certain work files.
Generic versions of these work files are contained in the installation
tape file Z.CAWRKLAB. Tailor these files to your installation's needs
and ensure that they are accessible before running the JCL that
produces the reports.
To produce this report, submit the following JCL with your job statement:
// JOB CAJERS1
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The PRINT statement following
produces a report with the fields below:
Field on Report
SCHEDULE NAME
SCHEDULING REASON CODE
SCHEDULED DATE
ACTUAL STRTTIME
ACTUAL END-TIME
ACTUAL AVLTIME
HOLD STATUS
RUN STATUS
COMPLETION CODE
Meaning
Schedules selected for this report.
The reason the schedule was selected.
The date the schedule was supposed to be selected.
The time the schedule actually started.
The time the schedule actually ended.
The time the schedule was available for processing: start time was reached, predecessors were
satisfied, and resources were available.
Whether the schedule was on hold.
The current status of the schedule.
The completion code (jobs only).
The SYSIPT control statements for this report are contained in the
CAJINS01.0 source member (shown following).
You may modify the OPTION statement values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJTRK:FILE CAJCACC2 RECORD = 248
COPY CAJESTR
COPY CAJEPM
COPY CAJERS1
END
The control statements that print this report are contained in the
Chapter 5. Reports 5-195

5.15 Advantage CA-Earl Tracking File Reports
CAJERS01.0 source member (shown following).
You may modify these statements to produce your own reports. The fields you can print are all listed in the appendix "Advantage CA-Earl
Reports" in the topic Schedule Information From Tracking File. (If you modify any of the source members provided, be sure to copy them with a
different name so a reinstall of the product will not replace the modified members.)
! REDEFINE FOR PRMONODE (STRONODE IN RECORD KEY)
!
DEF PRMONODE = PRMWRK 1-8 X
DEF SCHD_DATE (8) = ' ' 'SCHEDULED' 'DATE'
!
DEF IN_HSTAT (B 3.) =
DEF IN_RSTAT (B 3.) =
DEF IN_FLG1 (B 3.) =
DEF IN_FLG4 (B 3.) =
!
DEF OUT_HSTAT (2) = ' ' 'HOLD' 'STATUS'
DEF OUT_HSTAT_MSG = OUT_HSTAT 1-12 X
DEF OUT_HSTAT_USERID = OUT_HSTAT 13-2 X
!
DEF OUT_RSTAT (2) = ' ' 'RUN' 'STATUS'
!
DEF COMPL_CODE (5) = ' ' 'COMPLETION' 'CODE'
DEF COMPL_CODE_SW (B 3.) =
DEF GETUNIQ (8) = 'GETUNIQ '
COPY CAIJDEFD
IF PRMSCH = GETUNIQ THEN GOTO EOJ
ENDIF
COPY CAJESETS
GET CAIJTRK
!
GOTO EOJ CAIJTRK = 'E' OR CAIJTRK = 'N'
GOTO START STRRECID NOT = 'S'
!
SET CAI_DATE = STRSDATE
PERFORM CAI_DATE_CONVERSION
SET SCHD_DATE = CAI_OUTDATE
SET IN_HSTAT = STRHSTAT
SET IN_RSTAT = STRRSTAT
SET IN_FLG1 = STRFLG1
SET IN_FLG4 = STRFLG4
!
PERFORM DECODE_STATUS
!
! IF JOB HELD OR CANCELED BY USER CHANGE OUTPUT STATUS MESSAGE
!
IF IN_HSTAT = M'1' THEN SET OUT_HSTAT_USERID = STRCMHLD
ENDIF
IF IN_HSTAT = M'11' THEN SET OUT_HSTAT_USERID = STRCMCNC
ENDIF
!
COPY CAIJSTMD
COPY CAJECNV
!
SET COMPL_CODE = STRCC
5-196 Unicenter CA-Scheduler Reference Guide, Part 2

5.15 Advantage CA-Earl Tracking File Reports
!
REPORT 'SCHEDULE STATUS'
TITLE 'AT' 4 TIMEOFREPORT
PRINT DOUBLE SPACING STRNAME STRRC SCHD_DATE
STRSTIME STRETIME STRVTIME
OUT_HSTAT OUT_RSTAT COMPL_CODE
5.15.7 Scheduled Job Status (by Schedule)
The Scheduled Job Status (by Schedule) report lists job status information from
the Unicenter CA-Scheduler tracking file, sorted by schedule.
9/24/3 SCHEDULED JOB STATUS (BY SCHEDULE) PAGE 1
AT 11.11.49
-------------------------------------------------------------------------------------------------------------------------------
SCHEDULE JOB JOB STATN REASON SCHEDULED ACTUAL ACTUAL ACTUAL JOB JOB COMPLETION
NAME NAME NMBR ID CODE DATE STRTTIME END-TIME AVLTIME HOLD-STATUS RUN-STATUS CODE
-------------------------------------------------------------------------------------------------------------------------------
DEPENDBK D1 1 39 84 9/16/3 16.2.25 16.2.25 ACTIVE AUTO STARTED
DEPENDBK D1 1 4 84 ACTIVE WAITING PREDS
DEPENDBK D2 1 39 84 9/16/3 16.2.25 16.2.25 ACTIVE AUTO STARTED
DEPENDBK D2 1 4 84 ACTIVE WAITING PREDS
DEPENDBK D3 1 39 84 9/16/3 16.2.25 16.2.25 ACTIVE AUTO STARTED
DEPENDBK D3 1 4 84 ACTIVE WAITING PREDS
DEPENDBK D4 1 4 84 6.11.38 ACTIVE UNKNOWN
DEPENDBK D5 1 4 84 16.2.25 ACTIVE ABENDED x'FF'
DEPENDBK
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERT1
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The PRINT statement following produces a report with the fields below:
Field on Report
SCHEDULE NAME
JOB NAME
JOB NMBR
STATN ID
REASON CODE
Meaning
Schedules jobs were assigned to.
Jobs selected for this report.
Number defined for job.
Stations where jobs were processed.
Reason job was selected.
Chapter 5. Reports 5-197

5.15 Advantage CA-Earl Tracking File Reports
Field on Report
SCHEDULED DATE
ACTUAL STRTTIME
ACTUAL END-TIME
ACTUAL AVLTIME
JOB HOLD-STATUS
JOB RUN-STATUS
COMPLETION CODE
Meaning
The date the schedule was supposed to be
selected.
The time the job actually started.
The time the job actually ended.
The time the job was available for processing:
start time was reached, predecessors were
satisfied, and resources were available.
Whether the job was on hold.
The current status of the job.
The job's completion code.
The SYSIPT control statements for this report are contained in the CAJINT01.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJTRK:FILE CAJCACC2 RECORD = 248
COPY CAJEJTR
COPY CAJEPM
COPY CAJERT1
END
The control statements that print this report are contained in the CAJERT01.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Job Information From
Tracking File. (If you modify any of the source members provided, be sure to
copy them with a different name so a reinstall of the product will not replace
the modified members.)
5-198 Unicenter CA-Scheduler Reference Guide, Part 2

5.15 Advantage CA-Earl Tracking File Reports
! REDEFINE FOR PRMONODE (ORIGIN NODE-ID IN JTR KEY)
!
DEF PRMONODE = PRMWRK 1-8 X
DEF SCHD_DATE (8) = ' ' 'SCHEDULED' 'DATE'
!
DEF IN_HSTAT (B 3.) =
DEF IN_RSTAT (B 3.) =
DEF IN_FLG1 (B 3.) =
DEF IN_FLG4 (B 3.) =
!
DEF OUT_HSTAT (2) = ' ' 'JOB' 'HOLD-STATUS'
DEF OUT_HSTAT_MSG = OUT_HSTAT 1-12 X
DEF OUT_HSTAT_USERID = OUT_HSTAT 13-2 X
!
DEF OUT_RSTAT (2) = ' ' 'JOB' 'RUN-STATUS'
DEF COMPL_CODE (5) = ' ' 'COMPLETION' 'CODE'
DEF COMPL_CODE_SW (B 3.) =
DEF GETUNIQ (8) = 'GETUNIQ '
!
COPY CAIJDEFD
IF PRMNME = GETUNIQ THEN GOTO EOJ
ENDIF
COPY CAJESETT
GET CAIJTRK
GOTO EOJ CAIJTRK = 'E' OR CAIJTRK = 'N'
GOTO START JTRRECID NOT = 'J'
!
SET CAI_DATE = JTRSDATE
PERFORM CAI_DATE_CONVERSION
!
SET SCHD_DATE = CAI_OUTDATE
SET IN_HSTAT = JTRHSTAT
SET IN_RSTAT = JTRRSTAT
SET IN_FLG1 = JTRFLG1
SET IN_FLG4 = JTRFLG4
!
PERFORM DECODE_STATUS
!
! IF JOB HELD OR CANCELED BY USER CHANGE OUTPUT STATUS MESSAGE
!
SET COMPL_CODE = JTRCC
IF IN_HSTAT = M'1' THEN SET OUT_HSTAT_USERID = JTRCMHLD
ENDIF
IF IN_HSTAT = M'11' THEN SET OUT_HSTAT_USERID = JTRCMCNC
ENDIF
!
COPY CAIJSTMD
COPY CAJECNV
Chapter 5. Reports 5-199

5.15 Advantage CA-Earl Tracking File Reports
!
!
REPORT 'SCHEDULED JOB STATUS (BY SCHEDULE)'
TITLE 'AT' 4 TIMEOFREPORT
CONTROL (JTRSCHNAME) SKIP JTRJNAME
PRINT JTRSCHNAME JTRJNAME JTRJNUMBER JTRSTATID JTRRC
SCHD_DATE JTRSTIME JTRETIME JTRVTIME
OUT_HSTAT OUT_RSTAT COMPL_CODE
5.15.8 Scheduled Job Status (by Station)
The Scheduled Job Status (by Station) report lists job status information from
the Unicenter CA-Scheduler tracking file, sorted by station.
9/24/3 SCHEDULED JOB STATUS (BY STATION) PAGE 1
AT 11.11.52
-------------------------------------------------------------------------------------------------------------------------------
STATN SCHEDULE JOB JOB REASON SCHEDULED ACTUAL ACTUAL ACTUAL JOB JOB COMPLETION
ID NAME NAME NMBR CODE DATE STRTTIME END-TIME AVLTIME HOLD-STATUS RUN-STATUS CODE
-------------------------------------------------------------------------------------------------------------------------------
39 AADD AADD 1 84 9/24/3 1.5.1 1.5.1 ACTIVE AUTO STARTED
39 ABC DJKBR14 1 84 9/16/3 16.2.25 16.2.25 ACTIVE AUTO STARTED
39 BACKUP71 BKMSTDOC 1 1 9/18/3 9.13.42 1.52.46 9.13.42 ACTIVE COMPLETED
39 BACKUP71 IEHINIT 1 1 9/18/3 9.13.42 1.52.51 9.13.42 ACTIVE COMPLETED
39 DEMO CAJDEM3 1 84 11.1.29 CANCELED BY DEBK WAIT NON-CPU START
39 DEPENDBK D3 1 84 9/16/3 16.2.25 16.2.25 ACTIVE AUTO STARTED
39 DEPENDBK D1 1 84 9/16/3 16.2.25 16.2.25 ACTIVE AUTO STARTED
39 DEPENDBK D2 1 84 9/16/3 16.2.25 16.2.25 ACTIVE AUTO STARTED
39 ST DJKBR14 1 84 9/16/3 16.2.25 16.2.25 ACTIVE AUTO STARTED
39
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. Generic versions of these work files are contained in the
installation tape file Z.CAWRKLAB. Tailor these files to your installation's
needs and ensure that they are accessible before running the JCL that produces
the reports. To produce this report, submit the following JCL with your job
statement:
// JOB CAJERT2
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The PRINT statement following produces a report with the fields below:
Field on Report
STATN ID
SCHEDULE NAME
JOB NAME
JOB NMBR
REASON CODE
Meaning
Stations where jobs were processed.
Schedules jobs were assigned to.
Jobs selected for this report.
Number defined for job.
Reason the job was selected.
5-200 Unicenter CA-Scheduler Reference Guide, Part 2

5.15 Advantage CA-Earl Tracking File Reports
Field on Report
SCHEDULED DATE
ACTUAL STRTTIME
ACTUAL END-TIME
ACTUAL AVLTIME
JOB HOLD-STATUS
JOB RUN-STATUS
COMPLETION CODE
Meaning
The date the schedule was supposed to be
selected.
The time the job actually started.
The time the job actually ended.
The time the job was available for processing:
start time was reached, predecessors were
satisfied, and resources were available.
Whether the job was on hold.
The current status of the job.
The job's completion code.
The SYSIPT control statements for this report are contained in the CAJINT02.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJTRK:FILE CAJCACC2 RECORD = 248
COPY CAJEJTR
COPY CAJEPM
COPY CAJERT2
END
The control statements that print this report are contained in the CAJERT02.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Job Information From
Tracking File. (If you modify any of the source members provided, be sure to
copy them with a different name so a reinstall of the product will not replace
the modified members.)
Chapter 5. Reports 5-201

5.15 Advantage CA-Earl Tracking File Reports
! REDEFINE FOR PRMONODE (ORIGIN NODE-ID IN JTR KEY)
!
DEF PRMONODE = PRMWRK 1-8 X
DEF SCHD_DATE (8) = ' ' 'SCHEDULED' 'DATE'
!
DEF IN_HSTAT (B 3.) =
DEF IN_RSTAT (B 3.) =
DEF IN_FLG1 (B 3.) =
DEF IN_FLG4 (B 3.) =
!
DEF OUT_HSTAT (2) = ' ' 'JOB' 'HOLD-STATUS'
DEF OUT_HSTAT_MSG = OUT_HSTAT 1-12 X
DEF OUT_HSTAT_USERID = OUT_HSTAT 13-2 X
!
DEF OUT_RSTAT (2) = ' ' 'JOB' 'RUN-STATUS'
DEF COMPL_CODE (5) = ' ' 'COMPLETION' 'CODE'
DEF GETUNIQ (8) = 'GETUNIQ '
!
COPY CAIJDEFD
IF PRMNME = GETUNIQ THEN GOTO EOJ
ENDIF
COPY CAJESETT
!
GET CAIJTRK
GOTO EOJ CAIJTRK = 'E' OR CAIJTRK = 'N'
GOTO START JTRRECID NOT = 'J'
!
SET CAI_DATE = JTRSDATE
PERFORM CAI_DATE_CONVERSION
SET SCHD_DATE = CAI_OUTDATE
SET IN_HSTAT = JTRHSTAT
SET IN_RSTAT = JTRRSTAT
SET IN_FLG1 = JTRFLG1
SET IN_FLG4 = JTRFLG4
!
PERFORM DECODE_STATUS
!
! IF JOB HELD OR CANCELED BY USER CHANGE OUTPUT STATUS MESSAGE
!
IF IN_HSTAT = M'1' THEN SET OUT_HSTAT_USERID = JTRCMHLD
ENDIF
IF IN_HSTAT = M'11' THEN SET OUT_HSTAT_USERID = JTRCMCNC
ENDIF
!
COPY CAIJSTMD
COPY CAJECNV
!
SET COMPL_CODE = JTRCC
5-202 Unicenter CA-Scheduler Reference Guide, Part 2

5.15 Advantage CA-Earl Tracking File Reports
!
REPORT 'SCHEDULED JOB STATUS (BY STATION)'
TITLE 'AT' 4 TIMEOFREPORT
CONTROL (JTRSTATID) SKIP JTRSCHNAME
PRINT JTRSTATID JTRSCHNAME JTRJNAME JTRJNUMBER JTRRC
SCHD_DATE JTRSTIME JTRETIME JTRVTIME
OUT_HSTAT OUT_RSTAT COMPL_CODE
Chapter 5. Reports 5-203

5.16 Advantage CA-Earl Documentation File Reports
5.16 Advantage CA-Earl Documentation File Reports
This topic shows examples of each of the Documentation File reports and
shows you how to produce each report.
5.16.1 Documentation Directory And Member List
The Documentation Directory And Member List report lists directory records
and members from the Unicenter CA-Scheduler documentation library.
9/14/3 DOCUMENTATION DIRECTORY AND MEMBER LIST PAGE 1
-------------------------------------------------------------------------------------------------------------------------------
DISPL-KEY SCHEDULE JOB JOB STATION CREATION CREATION LAST-UPDATE LAST-UPDATE LAST-UPDATE OUTRECN OUTUPDT
MEMBR-NAME NUMBER ID DATE TIME DATE TIME USERID
-------------------------------------------------------------------------------------------------------------------------------
RUNBOOK SCHD1 JOB1 1 4 9/14/3 11.58.2 9/14/3 15.31.11 DANA 11 2
1
2 THIS JOB CANNOT BE STARTED UNTIL THE DAILY SALES TAPE HAS BEEN
3 RECEIVED FROM THE MANHATTAN OFFICE. ONCE THIS TAPE IS LOGGED
4 INTO THE TAPE LIBRARY... THE JCL FOR THIS JOB NEEDS TO BE UPDATED
5 WITH TODAYS TAPE VOLSERS FOR BOTH THE LONG ISLAND OFFICE AND THE
6 MANHATTAN OFFICE.
7
8 PLEASE RETURN ALL TAPES TO PRODUCTION CONTROL AT EOJ.
9
1 T H A N K Y O U !!
11
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. A generic version of these work files was cataloged into the
Unicenter CA-Scheduler library during installation as CAWRKLAB.Z. Tailor
these files to your installation's needs and ensure that they are accessible
before running the JCL that produces the reports. To produce this report,
submit the following JCL with your job statement:
// JOB CAJERD2
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The PRINT statement following produces a report with the fields below:
Field on Report
DISPL-KEY
MEMBR-NAME
SCHEDULE
JOB
JOB NUMBER
STATION ID
Meaning
The member name under which the
documentation is stored in the documentation
library.
Schedule name, if defined for this member.
Job name, if defined for this member.
Job number, if defined for this member.
Station id, if defined for this member.
5-204 Unicenter CA-Scheduler Reference Guide, Part 2

5.16 Advantage CA-Earl Documentation File Reports
Field on Report
CREATION DATE
CREATION TIME
LAST-UPDATE DATE
LAST-UPDATE TIME
LAST-UPDATE USERID
OUTRECN
OUTUPDT
Meaning
The date the documentation was created.
The time the documentation was created.
The date the documentation member was last
updated.
The time the documentation member was last
updated.
ID of the user who last updated the
documentation member.
The number of records in the documentation
member.
The number of updates to those records.
The SYSIPT control statements for this report are contained in the CAJIND02.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJDCM:FILE CAJCACC2 RECORD = 248
COPY CAJEDIR
COPY CAJEPM
COPY CAJERD2
END
The control statements that print this report are contained in the CAJERD02.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Information From
Documentation and Staging Libraries. (If you modify any of the source
members provided, be sure to copy them with a different name so a reinstall
of the product will not replace the modified members.)
Chapter 5. Reports 5-205

5.16 Advantage CA-Earl Documentation File Reports
!
! REDEFINES FOR JCLECORD -- DOCUMENTATION MEMBER RECORD
!
DEF RECORDJC = RECDIR 1-144 X
!
DEF JCLRECID = RECORDJC 5-5 X
DEF JCLTIME = RECORDJC 49-56 X
DEF JCLSEQN = RECORDJC 57-59 P
DEF JCLDATA = RECORDJC 6-139 X
!
! REDEFINE FOR RECORD IDENTIFICATION (DIR,JCL)
!
DEF RECIDENT = RECDIR 5-7 X
!
! REDEFINE FOR DOCUMENTATION DISPLAY KEY AND MEMBER NAME
!
DEF PRMDSPN = PRMWRK 1-8 X
DEF PRMSEQN = PRMWRK 9-11 P
!
! HOLD AREAS FOR PREVIOUS DIRECORD AND JCLECORD
!
DEF HOLD_PREVDIR (248) = ' '
DEF HOLD_PREVMBR (144) = ' '
!
DEF FIRST_TIME_SW (B 3.) =
DEF DIRCNTR (B 5.) =
DEF TOT_MEMBRS (P 5.) =
DEF TIME_STAMP (8) = ' '
DEF OUTRECN (P 5.) = PIC 'ZZZZ9'
DEF OUTUPDT (P 3.) = PIC 'ZZ9'
DEF HOLD_PRMNME (8) = ' '
DEF HOLD_PRMNUM (2) = ' '
DEF HOLD_PRMSTA (2) = ' '
DEF HOLD_PRMSCH (8) = ' '
DEF HOLD_PRMDSPN (8) = ' '
DEF EDITSEQ (3.) = PIC 'ZZ9'
DEF GETUNIQ (8) = 'GETUNIQ '
DEF ENDUNIQ (8) = 'ENDUNIQ '
!
IF FIRST_TIME_SW > THEN GOTO NOT_FIRST_TIME
ENDIF
SET FIRST_TIME_SW = FIRST_TIME_SW + 1
!
! SET INITIAL PARM VALUES AND HOLD FOR RESETTING
!
COPY CAJESETD
SET HOLD_PRMNME = PRMNME
SET HOLD_PRMNUM = PRMNUM
SET HOLD_PRMSTA = PRMSTA
SET HOLD_PRMSCH = PRMSCH
SET HOLD_PRMDSPN = PRMDSPN
5-206 Unicenter CA-Scheduler Reference Guide, Part 2

5.16 Advantage CA-Earl Documentation File Reports
!
NOT_FIRST_TIME:
IF PRMNME = ENDUNIQ
THEN GOTO EOJ
ENDIF
IF PRMID = 'DDIR' THEN SET RECDIR = HOLD_PREVDIR
GOTO GETREC
ENDIF
IF PRMID = 'DMBR' THEN SET RECORDJC = HOLD_PREVMBR
SET JCLTIME = TIME_STAMP
ELSE GOTO START
ENDIF
GETREC:
GET CAIJDCM
GOTO EOJ CAIJDCM = 'E'
GOTO EOJ (CAIJDCM = 'N' AND RECIDENT = 'DIR')
GOTO RESET_DIR (CAIJDCM = 'N' AND RECIDENT = 'JCL')
!
IF (RECIDENT = 'DIR' AND PRMNME = GETUNIQ)
THEN SET HOLD_PRMNME = GETUNIQ
ENDIF
IF RECIDENT = 'DIR' THEN SET HOLD_PREVDIR = RECDIR
PERFORM REC_IS_DDIR
SET DIRCNTR = DIRCNTR + 1
ELSE
SET HOLD_PREVMBR = RECORDJC
PERFORM REC_IS_MBR
ENDIF
!
! IF LAST MEMBER-REC AND IS A GETUNIQ -- DONOT RESET PRMFIELDS
!
IF (RECIDENT = 'JCL' AND JCLSEQN = TOT_MEMBRS AND
HOLD_PRMNME = GETUNIQ)
THEN SET PRMNME = ENDUNIQ
GOTO TEST
ENDIF
IF (RECIDENT = 'JCL' AND JCLSEQN = TOT_MEMBRS)
THEN GOTO RESET_DIR
ELSE GOTO TEST
ENDIF
!
RESET_DIR:
SET PRMID = 'DDIR'
SET PRMNME = HOLD_PRMNME
SET PRMNUM = HOLD_PRMNUM
SET PRMSTA = HOLD_PRMSTA
SET PRMSCH = HOLD_PRMSCH
SET PRMDSPN = HOLD_PRMDSPN
IF CAIJDCM = 'N' THEN GOTO START
ELSE GOTO TEST
ENDIF
Chapter 5. Reports 5-207

5.16 Advantage CA-Earl Documentation File Reports
!
COPY CAJDDIR
COPY CAJMBR
!
REPORT 'DOCUMENTATION DIRECTORY AND MEMBER LIST'
SELECT 'A' RECIDENT = 'DIR'
SELECT 'B' RECIDENT = 'JCL'
CONTROL QSEQ (DIRCNTR) SKIP
IFTAG A; PRINT DIRDSPN DIRSCDN
DIRJOBN DIRJNUM DIRJSTN DIRCDATE
DIRCTIME DIRUDATE DIRUTIME DIRUUSER OUTRECN OUTUPDT
IFTAG B; PRINT EDITSEQ JCLDATA
5.16.2 Documentation Directory List
The Documentation Directory List report lists directory records from the
Unicenter CA-Scheduler documentation library.
9/14/3 DOCUMENTATION DIRECTORY LIST PAGE 1
--------------------------------------------------------------------------------------------------------------------------------
DISPL-KEY SCHEDULE JOB JOB STATION CREATION CREATION LAST-UPDATE LAST-UPDATE LAST-UPDATE OUTRECN OUTUPDT
MEMBR-NAME NUMBER ID DATE TIME DATE TIME USERID
--------------------------------------------------------------------------------------------------------------------------------
RUNBOOK SCHD1 JOB1 1 4 9/14/3 11.58.2 9/14/3 15.31.11 DANA 11 2
SETUP SCHD1 JOB1 1 39 9/14/3 12..45 9/14/3 12..45 DANA 3 1
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. A generic version of these work files was cataloged into the
Unicenter CA-Scheduler library during installation as CAWRKLAB.Z. Tailor
these files to your installation's needs and ensure that they are accessible
before running the JCL that produces the reports. To produce this report,
submit the following JCL with your job statement:
// JOB CAJERD1
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The PRINT statement following produces a report with the fields below:
Field on Report
DISPL-KEY
MEMBR-NAME
SCHEDULE
JOB
JOB NUMBER
Meaning
The member name under which the
documentation is stored in the documentation
library.
Schedule name, if defined for this member.
Job name, if defined for this member.
Job number, if defined for this member.
5-208 Unicenter CA-Scheduler Reference Guide, Part 2

5.16 Advantage CA-Earl Documentation File Reports
Field on Report
STATION ID
CREATION DATE
CREATION TIME
LAST-UPDATE DATE
LAST-UPDATE TIME
LAST-UPDATE USERID
OUTRECN
OUTUPDT
Meaning
Station id, if defined for this member.
The date the documentation was created.
The time the documentation was created.
The date the documentation member was last
updated.
The time the documentation member was last
updated.
ID of the user who last updated the
documentation member.
The number of records in the documentation
member.
The number of updates to those records.
The SYSIPT control statements for this report are contained in the CAJIND01.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJDCM:FILE CAJCACC2 RECORD = 248
COPY CAJEDIR
COPY CAJEPM
COPY CAJERD1
END
The control statements that print this report are contained in the CAJERD01.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Information From
Documentation and Staging Libraries. (If you modify any of the source
members provided, be sure to copy them with a different name so a reinstall
of the product will not replace the modified members.)
Chapter 5. Reports 5-209

5.16 Advantage CA-Earl Documentation File Reports
!
! REDEFINE FOR DOCUMENTATION DISPLAY KEY AND MEMBER NAME
!
DEF PRMDSPN = PRMWRK 1-8 X
DEF PRMSEQN = PRMWRK 9-11 P
!
DEF OUTRECN (P 5.) = PIC 'ZZZZ9'
DEF OUTUPDT (P 3.) = PIC 'ZZ9'
DEF GETUNIQ (8) = 'GETUNIQ '
!
IF PRMNME = GETUNIQ THEN GOTO EOJ
ENDIF
!
COPY CAJESETD
!
GET CAIJDCM
GOTO EOJ CAIJDCM = 'E' OR CAIJDCM = 'N'
GOTO START DIRRECID NOT = 'D'
!
SET OUTRECN = DIRRECN
SET OUTUPDT = DIRUPDT
!
REPORT 'DOCUMENTATION DIRECTORY LIST'
PRINT DOUBLE SPACING DIRDSPN DIRSCDN DIRJOBN
DIRJNUM DIRJSTN DIRCDATE
DIRCTIME DIRUDATE DIRUTIME DIRUUSER OUTRECN OUTUPDT
5.16.3 Documentation Selected By The Tracking File
The Documentation Selected By The Tracking File report lists job information
from the Unicenter CA-Scheduler tracking file and the corresponding members
of the Unicenter CA-Scheduler documentation library.
9/14/3 DOCUMENTATION SELECTED BY THE TRACKING FILE PAGE 1
AT 16.27.16
-------------------------------------------------------------------------------------------------------------------------------
SCHEDULE JOB JNO ST. REASON SCHEDULED ACTUAL ACTUAL ACTUAL JOB JOB COMPLETION
NAME NAME ID CODE DATE STRTTIME END-TIME AVLTIME HOLD-STATUS RUN-STATUS CODE
-------------------------------------------------------------------------------------------------------------------------------
SCHD1 JOB1 1 39 84 9/14/3 14.55.4 14.55.4 ACTIVE AUTO STARTED
1
2 P L E A S E N O T E
3 COMPLETING THIS JOB WILL AUTOMATICALLY START THE DAILY UPDATES!!
4 DO NOT COMPLETE THIS JOB UNTIL THE DAILY SALES TAPES HAVE BEEN
5 RECEIVED FROM BOTH THE MANHATTAN OFFICE AND THE LONG ISLAND OFFICE
6 AND THE STAGED JCL FOR JOB1 HAS BEEN UPDATED WITH BOTH VOLSERS.
7 T H A N K Y O U
8
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. A generic version of these work files was cataloged into the
Unicenter CA-Scheduler library during installation as CAWRKLAB.Z. Tailor
these files to your installation's needs and ensure that they are accessible
before running the JCL that produces the reports. To produce this report,
submit the following JCL with your job statement:
5-210 Unicenter CA-Scheduler Reference Guide, Part 2

5.16 Advantage CA-Earl Documentation File Reports
// JOB CAJERTD1
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The SYSIPT control statements for this report are contained in the CAJINTD1.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJTRK:FILE CAJCACC2 RECORD = 248
COPY CAJEJTR
COPY CAJEPM
COPY CAJERTD1
END
The PRINT statement following produces a report with the fields below:
Field on Report
SCHEDULE NAME
JOB NAME
JNO
ST. ID
CODE
SCHEDULED DATE
ACTUAL STRTTIME
ACTUAL END-TIME
ACTUAL AVLTIME
JOB HOLD-STATUS
JOB RUN-STATUS
COMPLETION CODE
Meaning
Schedules jobs were assigned to.
Jobs selected for this report.
Number defined for job.
Stations where jobs were processed.
the job was selected.
The date the schedule was supposed to be
selected.
The time the job actually started.
The time the job actually ended.
The time the job was available for processing:
start time was reached, predecessors were
satisfied, and resources were available.
Whether the job was on hold.
The current status of the job.
The job's completion code.
Chapter 5. Reports 5-211

5.16 Advantage CA-Earl Documentation File Reports
If the documentation member exists, it will be printed after the last line of field
values described above. If the documentation member does not exist, the
message 'DOCUMENTATION MEMBER DOES NOT EXIST' is printed after
the last line of field values.
The control statements that print this report are contained in the CAJERTD1.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Information From
Documentation and Staging Libraries. (If you modify any of the source
members provided, be sure to copy them with a different name so a reinstall
of the product will not replace the modified members.)
5-212 Unicenter CA-Scheduler Reference Guide, Part 2

5.16 Advantage CA-Earl Documentation File Reports
!
! REDEFINES FOR DIRECORD -- DOCUMENTATION DIRECTORY RECORD
!
DEF RECORDD = RECORDJT 1-248 X
!
DEF DIRRECID = RECORDD 5-5 X
DEF DIRDSPN = RECORDD 13-2 X
DEF DIRSCDN = RECORDD 21-28 X
DEF DIRJOBN = RECORDD 29-36 X
DEF DIRJNUM = RECORDD 37-38 X
DEF DIRJSTN = RECORDD 39-4 X
DEF DIRTIME = RECORDD 49-56 X
DEF DIRRECN = RECORDD 66-68 P
DEF DIRUPDT = RECORDD 69-7 P
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! REDIFINES FOR JCLECORD -- DOCUMENTATION MEMBER RECORD
!
DEF RECORDJC = RECORDD 1-144 X
!
DEF JCLRECID = RECORDJC 5-5 X
DEF JCLTIME = RECORDJC 49-56 X
DEF JCLSEQN = RECORDJC 57-59 P
DEF JCLDATA = RECORDJC 6-139 X
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! REDEFINES FOR DOCUMENTATION DISPLAY KEY AND MEMBER NAME
!
DEF PRMDSPN = PRMWRK 1-8 X
DEF PRMSEQN = PRMWRK 9-11 P
!
! REDEFINE FOR RECORD IDENTIFICATION (JTR ,DIR,JCL)
!
DEF RECIDENT = RECORDJT 5-7 X
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
!
! HOLD AREAS FOR PREVIOUS JTRECORD,DIRECORD,JCLECORD
! HOLD AREAS FOR PARM FIELDS
!
DEF HOLD_PREVJTR (9) = ' '
DEF HOLD_PREVDIR (248) = ' '
DEF HOLD_PREVMBR (144) = ' '
DEF HOLD_PRMNME (8) = ' '
DEF HOLD_PRMNUM (2) = ' '
DEF HOLD_PRMSTA (2) = ' '
DEF HOLD_PRMSCH (8) = ' '
DEF HOLD_PRMONODE (8) = ' '
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Chapter 5. Reports 5-213

5.16 Advantage CA-Earl Documentation File Reports
!
DEF SCHD_DATE (8) = ' ' 'SCHEDULED' 'DATE'
DEF EDITSEQ (3.) = PIC 'ZZ9'
DEF FIRST_TIME_SW (B 3.) =
DEF TOT_MEMBRS (P 5.) =
DEF TIME_STAMP (8) = ' '
!
DEF IN_RSTAT (B 3.) =
DEF IN_HSTAT (B 3.) =
DEF IN_FLG1 (B 3.) =
DEF IN_FLG4 (B 3.) =
!
DEF OUT_RSTAT (2) = ' ' 'JOB' 'RUN-STATUS'
DEF OUT_HSTAT (2) = ' ' 'JOB' 'HOLD-STATUS'
DEF OUT_HSTAT_MSG = OUT_HSTAT 1-12 X
DEF OUT_HSTAT_USERID = OUT_HSTAT 13-2 X
!
DEF COMPL_CODE (5) = ' ' 'COMPLETION' 'CODE'
DEF COMPL_CODE_SW (B 3.) =
DEF JTRCNTR (B 5.) =
DEF GETUNIQ (8) = 'GETUNIQ '
DEF ENDUNIQ (8) = 'ENDUNIQ '
!
COPY CAIJDEFD
!
!
!
IF FIRST_TIME_SW > THEN GOTO NOT_FIRST_TIME
ENDIF
SET FIRST_TIME_SW = FIRST_TIME_SW + 1
!
! SET INITIAL PARM VALUES AND HOLD FOR RESETTING
!
COPY CAJESETT
!
SET HOLD_PRMNME = PRMNME
SET HOLD_PRMNUM = PRMNUM
SET HOLD_PRMSTA = PRMSTA
SET HOLD_PRMSCH = PRMSCH
SET HOLD_PRMONODE = PRMONODE
!
NOT_FIRST_TIME:
GOTO EOJ PRMNME = ENDUNIQ
GOTO TRACK_GET PRMID = 'JTR '
GOTO DOC_GET PRMID = 'DDIR'
GOTO DOC_GET PRMID = 'DMBR'
5-214 Unicenter CA-Scheduler Reference Guide, Part 2

5.16 Advantage CA-Earl Documentation File Reports
!
TRACK_GET:
SET RECORDJT = HOLD_PREVJTR
GET CAIJTRK
GOTO EOJ CAIJTRK = 'E' OR CAIJTRK = 'N'
GOTO START RECIDENT NOT = 'JTR'
!
IF PRMNME = GETUNIQ
THEN SET HOLD_PRMNME = GETUNIQ
ENDIF
!
SET JTRCNTR = JTRCNTR +1
SET HOLD_PREVJTR = RECORDJT
!
SET CAI_DATE = JTRSDATE
PERFORM CAI_DATE_CONVERSION
SET SCHD_DATE = CAI_OUTDATE
!
SET IN_HSTAT = JTRHSTAT
SET IN_RSTAT = JTRRSTAT
SET IN_FLG1 = JTRFLG1
SET IN_FLG4 = JTRFLG4
PERFORM DECODE_STATUS
SET COMPL_CODE = JTRCC
!
! IF JOB HELD OR CANCELED BY USER CHANGE OUTPUT STATUS MESSAGE
!
IF IN_HSTAT = M'1' THEN SET OUT_HSTAT_USERID = JTRCMHLD
ENDIF
IF IN_HSTAT = M'11' THEN SET OUT_HSTAT_USERID = JTRCMCNC
ENDIF
!
!
! SETUP PARMS FOR DIR GET
!
SET PRMFUNC = 'GETS'
SET PRMID = 'DDIR'
SET PRMNME = JTRJNAME
SET PRMNUM = JTRJNUMBER
SET PRMSTA = JTRSTATID
SET PRMSCH = JTRSCHNAME
SET PRMDSPN = JTRDISPK
GOTO TEST
!
!
Chapter 5. Reports 5-215

5.16 Advantage CA-Earl Documentation File Reports
!
DOC_GET:
IF PRMID = 'DDIR' THEN SET RECORDD = HOLD_PREVDIR
ELSE SET RECORDJC = HOLD_PREVMBR
SET JCLTIME = TIME_STAMP
ENDIF
GET CAIJTRK
GOTO RESET_JTR CAIJTRK = 'E'
GOTO RESET_JTR CAIJTRK = 'N'
!
IF RECIDENT = 'DIR' THEN SET HOLD_PREVDIR = RECORDD
PERFORM REC_IS_DDIR
GOTO START
ELSE SET HOLD_PREVMBR = RECORDJC
PERFORM REC_IS_MBR
ENDIF
IF (RECIDENT = 'JCL' AND JCLSEQN = TOT_MEMBRS AND
HOLD_PRMNME = GETUNIQ)
THEN SET PRMNME = ENDUNIQ
GOTO TEST
ENDIF
IF (RECIDENT = 'JCL' AND JCLSEQN = TOT_MEMBRS)
THEN GOTO RESET_JTR
ELSE GOTO TEST
ENDIF
!
RESET_JTR:
SET PRMID = 'JTR '
SET PRMNME = HOLD_PRMNME
SET PRMNUM = HOLD_PRMNUM
SET PRMSTA = HOLD_PRMSTA
SET PRMSCH = HOLD_PRMSCH
SET PRMONODE = HOLD_PRMONODE
GOTO TEST
!
COPY CAIJSTMD
!
COPY CAJECNV
!
COPY CAJDDIR
!
COPY CAJMBR
5-216 Unicenter CA-Scheduler Reference Guide, Part 2

5.16 Advantage CA-Earl Documentation File Reports
!
REPORT 'DOCUMENTATION SELECTED BY THE TRACKING FILE'
TITLE 'AT' 4 TIMEOFREPORT
SELECT 'A' RECIDENT = 'JTR'
SELECT 'B' RECIDENT = 'JCL'
SELECT 'C' (RECIDENT = 'DIR' AND (CAIJTRK = 'N' OR CAIJTRK = 'E'))
CONTROL QSEQ (JTRCNTR) SKIP
IFTAG A; PRINT JTRSCHNAME JTRJNAME
JTRJNUMBER JTRSTATID JTRRC
SCHD_DATE JTRSTIME JTRETIME JTRVTIME
OUT_HSTAT OUT_RSTAT COMPL_CODE
IFTAG B; PRINT EDITSEQ JCLDATA
IFTAG C; PRINT 'DOCUMENTATION MEMBER DOES NOT EXIST'
Chapter 5. Reports 5-217

5.17 Advantage CA-Earl Staging File Reports
5.17 Advantage CA-Earl Staging File Reports
When reports are generated using the staging file for input, the data reflected
will be from the current day's work (autoscan+23.59).
5.17.1 Staged JCL Directory And Member List
The Staged JCL Directory And Member List report lists directory records from
the Unicenter CA-Scheduler staging library.
9/14/3 STAGED JCL DIRECTORY AND MEMBER LIST PAGE 1
-------------------------------------------------------------------------------------------------------------------------------
JOB JOB STAGED STATION CREATION CREATION LAST-UPDATE LAST-UPDATE LAST-UPDATE OUTRECN OUTUPDT
NUMBER SCHEDULE ID DATE TIME DATE TIME USERID
-------------------------------------------------------------------------------------------------------------------------------
JOB1 1 SCHD1 4 9/14/3 14.55.5 9/14/3 15.42.1 DANA 13 3
1 $$ JOB JNM=JOB1,DISP=D,CLASS=A, X
2 $$ USER='DANA',LDEST=(,CEGDA1),PDEST=(,CEGDA1)
3 CARCTL off SCHEDULER P
4 SCSTART S=SCHD1 JNO=1 J=JOB1 P
5 // JOB JOB1 UPDATE DAILY SALES TOTALS
6 =====> UPDATE TLBLS WITH TODAYS DAILY SALES VOLSERS
7 // TLBL DAILYM,'MANHATTAN.DAILY.SALES',,VOLSER
8 // TLBL DAILYL,'LONG.ISLAND.DAILY.SALES',,VOLSER
9 // EXEC DAILY
1 /
11 /&
12 SCEND S=SCHD1 P
13 $$ EOJ P
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. A generic version of these work files was cataloged into the
Unicenter CA-Scheduler library during installation as CAWRKLAB.Z. Tailor
these files to your installation's needs and ensure that they are accessible
before running the JCL that produces the reports. To produce this report,
submit the following JCL with your job statement:
// JOB CAJERG2
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The PRINT statement following produces a report with the fields below:
Field on Report
JOB
JOB NUMBER
STAGED SCHEDULE
STATION ID
Meaning
JCL that was written to the staging library for
setup.
Number defined for job.
Schedules jobs were assigned to.
Stations where jobs were processed.
5-218 Unicenter CA-Scheduler Reference Guide, Part 2

5.17 Advantage CA-Earl Staging File Reports
Field on Report
CREATION DATE
CREATION TIME
LAST-UPDATE DATE
LAST-UPDATE TIME
LAST-UPDATE USERID
OUTRECN
OUTUPDT
Meaning
The date the JCL was staged.
The time the JCL was staged.
The date the staged JCL was last updated.
The time the staged JCL was last updated.
ID of the user who last updated the
documentation member.
The number of records in the library.
The number of updates to those records.
The SYSIPT control statements for this report are contained in the CAJING02.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJSTG:FILE CAJCACC2 RECORD = 248
COPY CAJEDIR
COPY CAJEPM
COPY CAJERG2
END
The control statements that print this report are contained in the CAJERG02.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" in the topic Information From
Documentation and Staging Libraries. (If you modify any of the source
members provided, be sure to copy them with a different name so a reinstall
of the product will not replace the modified members.)
Chapter 5. Reports 5-219

5.17 Advantage CA-Earl Staging File Reports
!
! REDEFINES FOR JCLECORD -- STAGING MEMBER RECORD
!
DEF RECORDJC = RECDIR 1-144 X
!
DEF JCLRECID = RECORDJC 5-5 X
DEF JCLTIME = RECORDJC 49-56 X
DEF JCLSEQN = RECORDJC 57-59 P
DEF JCLDATA = RECORDJC 6-139 X
!
! REDEFINE FOR RECORD IDENTIFICATION (DIR,JCL)
!
DEF RECIDENT = RECDIR 5-7 X
!
! REDEFINE : RECORD SEQUENCE NUMBER FOR JCL MEMBER
!
DEF PRMSEQN = PRMWRK 9-11 P
!
! HOLD AREAS FOR PREVIOUS DIRECORD AND JCLECORD
!
DEF HOLD_PREVDIR (248) = ' '
DEF HOLD_PREVMBR (144) = ' '
!
DEF FIRST_TIME_SW (B 3.) =
DEF DIRCNTR (B 5.) =
DEF TOT_MEMBRS (P 5.) =
DEF TIME_STAMP (8) = ' '
DEF OUTRECN (P 5.) = PIC 'ZZZZ9'
DEF OUTUPDT (P 3.) = PIC 'ZZ9'
DEF HOLD_PRMNME (8) = ' '
DEF HOLD_PRMNUM (2) = ' '
DEF HOLD_PRMSTA (2) = ' '
DEF HOLD_PRMSCH (8) = ' '
DEF EDITSEQ (3.) = PIC 'ZZ9'
DEF GETUNIQ (8) = 'GETUNIQ '
DEF ENDUNIQ (8) = 'ENDUNIQ '
!
IF FIRST_TIME_SW > THEN GOTO NOT_FIRST_TIME
ENDIF
SET FIRST_TIME_SW = FIRST_TIME_SW + 1
!
! SET INITIAL PARM VALUES AND HOLD FOR RESETTING
!
COPY CAJESETG
SET HOLD_PRMNME = PRMNME
SET HOLD_PRMNUM = PRMNUM
SET HOLD_PRMSTA = PRMSTA
SET HOLD_PRMSCH = PRMSCH
5-220 Unicenter CA-Scheduler Reference Guide, Part 2

5.17 Advantage CA-Earl Staging File Reports
!
NOT_FIRST_TIME:
IF PRMNME = ENDUNIQ
THEN GOTO EOJ
ENDIF
IF PRMID = 'SDIR' THEN SET RECDIR = HOLD_PREVDIR
GOTO GETREC
ENDIF
IF PRMID = 'SMBR' THEN SET RECORDJC = HOLD_PREVMBR
SET JCLTIME = TIME_STAMP
ELSE GOTO START
ENDIF
GETREC:
GET CAIJSTG
GOTO EOJ CAIJSTG = 'E'
GOTO EOJ (CAIJSTG = 'N' AND RECIDENT = 'DIR')
GOTO RESET_DIR (CAIJSTG = 'N' AND RECIDENT = 'JCL')
!
IF (RECIDENT = 'DIR' AND PRMNME = GETUNIQ)
THEN SET HOLD_PRMNME = GETUNIQ
ENDIF
IF RECIDENT = 'DIR' THEN SET HOLD_PREVDIR = RECDIR
PERFORM REC_IS_SDIR
SET DIRCNTR = DIRCNTR + 1
ELSE
SET HOLD_PREVMBR = RECORDJC
PERFORM REC_IS_MBR
ENDIF
!
! IF LAST MEMBER-REC AND IS A GETUNIQ -- DONOT RESET PRMFIELDS
!
IF (RECIDENT = 'JCL' AND JCLSEQN = TOT_MEMBRS AND
HOLD_PRMNME = GETUNIQ)
THEN SET PRMNME = ENDUNIQ
GOTO TEST
ENDIF
IF (RECIDENT = 'JCL' AND JCLSEQN = TOT_MEMBRS)
THEN GOTO RESET_DIR
ELSE GOTO TEST
ENDIF
!
RESET_DIR:
SET PRMID = 'SDIR'
SET PRMNME = HOLD_PRMNME
SET PRMNUM = HOLD_PRMNUM
SET PRMSTA = HOLD_PRMSTA
SET PRMSCH = HOLD_PRMSCH
IF CAIJSTG = 'N' THEN GOTO START
ELSE GOTO TEST
ENDIF
Chapter 5. Reports 5-221

5.17 Advantage CA-Earl Staging File Reports
!
COPY CAJSDIR
COPY CAJMBR
!
REPORT 'STAGED JCL DIRECTORY AND MEMBER LIST'
SELECT 'A' RECIDENT = 'DIR'
SELECT 'B' RECIDENT = 'JCL'
CONTROL QSEQ (DIRCNTR) SKIP
IFTAG A; PRINT DIRJOBN DIRJNUM DIRSCDX DIRJSTN DIRCDATE
DIRCTIME DIRUDATE DIRUTIME DIRUUSER OUTRECN OUTUPDT
IFTAG B; PRINT EDITSEQ JCLDATA
5.17.2 Staged JCL Library Directory List
The Staged JCL Library Directory List report lists directory records from the
Unicenter CA-Scheduler staging library.
9/14/3 STAGED JCL LIBRARY DIRECTORY LIST PAGE 1
-------------------------------------------------------------------------------------------------------------------------------
JOB JOB STAGED STATION CREATION CREATION LAST-UPDATE LAST-UPDATE LAST-UPDATE OUTRECN OUTUPDT
NUMBER SCHEDULE ID DATE TIME DATE TIME USERID
-------------------------------------------------------------------------------------------------------------------------------
JOB1 1 SCHD1 4 9/14/3 14.55.5 9/14/3 15.37.41 DANA 13 2
JOB2 2 SCHD1 4 9/14/3 14.55.6 9/14/3 14.55.6 7 1
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. A generic version of these work files was cataloged into the
Unicenter CA-Scheduler library during installation as CAWRKLAB.Z. Tailor
these files to your installation's needs and ensure that they are accessible
before running the JCL that produces the reports. To produce this report,
submit the following JCL with your job statement:
// JOB CAJERG1
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
The PRINT statement following produces a report with the fields below:
Field on Report
JOB
JOB NUMBER
STAGED SCHEDULE
STATION ID
CREATION DATE
CREATION TIME
Meaning
JCL that was written to the staging library for
setup.
Number defined for job.
Schedules jobs were assigned to.
Stations where jobs were processed.
The date the JCL was staged.
The time the JCL was staged.
5-222 Unicenter CA-Scheduler Reference Guide, Part 2

5.17 Advantage CA-Earl Staging File Reports
Field on Report
LAST-UPDATE DATE
LAST-UPDATE TIME
LAST-UPDATE USERID
OUTRECN
OUTUPDT
Meaning
The date the staged JCL was last updated.
The time the staged JCL was last updated.
ID of the user who last updated the
documentation member.
The number of records in the library.
The number of updates to those records.
The SYSIPT control statements for this report are contained in the CAJING01.0
source member (shown following). You may modify the OPTION statement
values.
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
CAIJSTG:FILE CAJCACC2 RECORD = 248
COPY CAJEDIR
COPY CAJEPM
COPY CAJERG1
END
The control statements that print this report are contained in the CAJERG01.0
source member (shown following). You may modify these statements to
produce your own reports. The fields you can print are all listed in the
appendix "Advantage CA-Earl Reports" under 'Information From
Documentation and Staging Libraries.' (If you modify any of the source
members provided, be sure to copy them with a different name so a reinstall
of the product will not replace the modified members.)
Chapter 5. Reports 5-223

5.17 Advantage CA-Earl Staging File Reports
!
! REDEFINE FOR RECORD SEQUENCE NEMBER
!
DEF PRMSEQN = PRMWRK 9-11 P
!
DEF OUTRECN (P 5.) = PIC 'ZZZZ9'
DEF OUTUPDT (P 3.) = PIC 'ZZ9'
DEF GETUNIQ (8) = 'GETUNIQ '
!
! PRMNME FIELD BLANKED OUT AFTER A GET UNIQUE (IN ACCESS MODULE)
! TO AVOID REPEATED OUTPUT OF SAME RECORD
!
IF PRMNME = GETUNIQ THEN GOTO EOJ
ENDIF
COPY CAJESETG
!
GET CAIJSTG
GOTO EOJ CAIJSTG = 'E' OR CAIJSTG = 'N'
GOTO START DIRRECID NOT = 'D'
!
SET OUTRECN = DIRRECN
SET OUTUPDT = DIRUPDT
!
REPORT 'STAGED JCL LIBRARY DIRECTORY LIST'
PRINT DOUBLE SPACING DIRJOBN DIRJNUM DIRSCDX
DIRJSTN DIRCDATE DIRCTIME
DIRUDATE DIRUTIME DIRUUSER OUTRECN OUTUPDT
5-224 Unicenter CA-Scheduler Reference Guide, Part 2

5.18 Batch Reporting for CAIAUDIT
5.18 Batch Reporting for CAIAUDIT
5.18.1 Overview
This topic gives examples of each of the batch reports and gives you
information on how to produce them.
CAIAUDIT's extensive reporting capabilities are facilitated by Advantage
CA-Earl, a utility that generates reports for all CA products that use
CAIAUDIT. In addition to the standard reports provided with CAIAUDIT,
customized reports can also be created using Advantage CA-Earl.
The copybooks needed to generate Unicenter CA-Scheduler reports of
CAIAUDIT events were cataloged into the Unicenter CA-Scheduler library as 0
(zero) books during installation. They may be found in the library with the
prefix CAAU.
■
■
The Unicenter CA-Scheduler copybooks are CAAUE06 through CAAUE09.
Copybooks CAAUDCOD and CAAUEF, cataloged into the CA90s
installation library, are also required for report generation.
5.18.2 UPSI Settings
The following pages display sample Advantage CA-Earl reports.
The following UPSI settings apply to the Advantage CA-Earl JCL.
UPSI bits 5 and 8 are used for processing CA AUDIT EARL reports.
UPSI bit 5
UPSI bit 8
Set this bit to 1 to process CAIAUDIT records from tape, or
set it to 0 to process CAIAUDIT records from a VSAM data
set.
Set this bit to 1 to process CAIAUDIT records from the
CAUDPC2 data set, or set it to 0 to process CAIAUDIT
records from the CAUDPC1 data set.
Note: UPSI bit 5 overrides UPSI bit 8.
5.18.3 Audited Events Report
The report lists all events audited for Unicenter CA-Scheduler, sorted by time.
Chapter 5. Reports 5-225

5.18 Batch Reporting for CAIAUDIT
CA AUDIT/VSE
SEP 7 3 CA AUDIT RECORD LISTING PAGE 1
PRODUCT: SCHEDULER
------------------------------------------------------------------------------------------------------------------------------
EVENT DATE TIME USER SYS-ID COMMAND/ OBJECT/ MISCELLANEOUS
CODE SCHD NAME JOB NAME
------------------------------------------------------------------------------------------------------------------------------
CTD 9/7/3 9:38:41 OPERATOR 1 DISPLAY DATE
CTU 9/7/3 9:58:2 OPERATOR 1 SHUTDOWN DELAYED
CBU 9/7/3 1:7:59 1 DEFINE USERID JNM=CAJUTIL#19
CBU 9/7/3 1:7:59 1 DEFINE USERID JNM=CAJUTIL#19
CBU 9/7/3 1:7:59 1 DEFINE USERID JNM=CAJUTIL#19
CBU 9/7/3 1:7:59 1 DEFINE USERID JNM=CAJUTIL#19
CTU 9/7/3 1:19:31 OPERATOR 1 SHUTDOWN DELAYED
CBU 9/7/3 1:48:8 STEVE 1 DEFINE USERID JNM=STRTCICS#7
CBU 9/7/3 1:48:8 STEVE 1 DEFINE USERID JNM=STRTCICS#7
CBU 9/7/3 1:49:31 STE 1 ALTER USERID JNM=STRTCICS#7
CBU 9/7/3 1:49:53 STE 1 ALTER USERID JNM=STRTCICS#7
CTU 9/6/3 16:35:51 OPERATOR 1 SHUTDOWN DELAYED
CTU 9/6/3 15:9:52 OPERATOR 1 RUN JOB
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. A generic version of these work files was cataloged into the
Unicenter CA-Scheduler library during installation as CAWRKLAB.Z. Tailor
these files to your installation's needs and ensure that they are accessible
before running the JCL that produces the reports. To produce this report,
submit the following JCL with your job statement:
// JOB CAAUE6
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
COPY CAAUEF
COPY CAAUDCOD
COPY CAAUE6
/
The control statements that print this report are contained in the CAAUE06
source member (shown following). You may modify these statements to
produce your own reports. Printable fields are listed in the appendix
"Advantage CA-Earl Reports." (If you modify any of the source members
provided, be sure to copy them with a different name so that a reinstallation of
the product will not replace the modified members.)
5-226 Unicenter CA-Scheduler Reference Guide, Part 2

5.18 Batch Reporting for CAIAUDIT
! SCHEDULER RECORD LISTING
REPORT 'CA AUDIT RECORD LISTING'
TITLE'PRODUCT: SCHEDULER'
TITLE ' '
SELECT 'A' CAAUDPRD = 'CASH' AND CAAUDPE1 = 'C'
CONTROL CAAUDDTE DOWN CAAUDTME
IFTAG A;PRINT DOUBLE SPACING CAAUDPEC CAAUDDTE CAAUDTME CAAUDUID
CAAUDSID CAUSHCMD CAUSHOBJ CAAUDINF
!
REPORT 'CA AUDIT RECORD LISTING'
TITLE'PRODUCT: SCHEDULER'
TITLE ' '
SELECT 'A' CAAUDPRD = 'CASH' AND CAAUDPE1 = 'M'
CONTROL CAAUDDTE DOWN CAAUDTME
IFTAG A;PRINT DOUBLE SPACING CAAUDPEC CAAUDDTE CAAUDTME CAAUDUID
CAAUDSID CAUSHSNM CAUSHJNM CAAUDINF
The preceding PRINT statement produces a report with the following fields:
Field On Report
EVENT CODE
DATE
TIME
USER
SYSID
COMMAND/SCHD NAME
OBJECT/JOB NAME
MISCELLANEOUS
Meaning
Audit event code
Date event occurred
Time event occurred
User ID associated with the event
ID of the system where the event occurred
Unicenter CA-Scheduler command or
schedule name
Object or job name
Any miscellaneous event information
5.18.4 Audited Commands/Text Report
The Audited Commands/Text Report report lists all commands and
corresponding text audited for Unicenter CA-Scheduler.
CA AUDIT/VSE
SEP 7 3 CA AUDIT RECORD LISTING PAGE 1
PRODUCT: SCHEDULER
COMMAND RECORDS
-------------------------------------------------------------------------------------------------------------------------------
EVENT DATE TIME USER COMMAND/ OBJECT/ TYPE CLASS INDICATOR COMMAND TEXT
CODE SCHD NAME JOB NAME
-------------------------------------------------------------------------------------------------------------------------------
CBU 9/7/3 1:7:59 DEFINE USERID B U WRITPASS=,C
9/7/3 1:7:59 DEFINE USERID B U DEFINE USERID NAME=STEVE,D
9/7/3 1:7:59 DEFINE USERID B U WRITPASS=,C
9/7/3 1:7:59 DEFINE USERID B U DEFINE USERID NAME=MASTER,
9/7/3 1:48:8 STEVE DEFINE USERID B U CONNECT=(39,4),TYPE=M
9/7/3 1:48:8 STEVE DEFINE USERID B U DEFINE USERID NAME=STE,REA
9/7/3 1:49:31 STE ALTER USERID B U ALTER USERID NAME=STE,CONN
9/7/3 1:49:53 STE ALTER USERID B U ALTER USERID NAME=STE,DESC
Chapter 5. Reports 5-227

5.18 Batch Reporting for CAIAUDIT
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. A generic version of these work files was cataloged into the
Unicenter CA-Scheduler library during installation as CAWRKLAB.Z. Tailor
these files to your installation's needs and ensure that they are accessible
before running the JCL that produces the reports. To produce this report,
submit the following JCL with your job statement:
// JOB CAAUE7
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
COPY CAAUEF
COPY CAAUDCOD
COPY CAAUE7
/
The control statements that print this report are contained in the CAAUE07
source member (shown following). You may modify these statements to
produce your own reports. Printable fields are listed in the appendix
"Advantage CA-Earl Reports." (If you modify any of the source members
provided, be sure to copy them with a different name so that a reinstallation of
the product will not replace the modified members.)
! SCHEDULER COMMAND REPORTS
REPORT 'CA AUDIT RECORD LISTING'
TITLE'PRODUCT: SCHEDULER'
TITLE 'COMMAND RECORDS'
SELECT 'A' CAAUDPRD = 'CASH' AND CAAUDPE1 = 'C'
CONTROL (CAAUDPEC) SKIP BREAK CAAUDDTE DOWN CAAUDTME
IFTAG A;PRINT DOUBLE SPACING CAAUDPEC CAAUDDTE CAAUDTME CAAUDUID
CAUSHCMD CAUSHOBJ CAUSHTYP CAUSHCLS CAUSHIND
CAUSHCTX
!
REPORT 'CA AUDIT RECORD LISTING'
TITLE'PRODUCT: SCHEDULER'
TITLE 'FULL COMMAND TEXT'
SELECT 'A' CAAUDPRD = 'CASH' AND CAAUDPE1 = 'C'
CONTROL (CAAUDPEC) SKIP BREAK CAAUDDTE DOWN CAAUDTME
IFTAG A;PRINT DOUBLE SPACING CAAUDDTE CAAUDTME CAAUDUID CAUSHCMD
CAUSHOBJ CAUSHDAT
The preceding PRINT statement produces two reports. The first report lists the
command records, with the following fields:
Field On Report
EVENT CODE
DATE
Meaning
Audit event code
Date event occurred
5-228 Unicenter CA-Scheduler Reference Guide, Part 2

5.18 Batch Reporting for CAIAUDIT
Field On Report
TIME
USER
COMMAND/SCHD NAME
OBJECT/JOB NAME
TYPE
CLASS
INDICATOR
COMMAND TEXT
Meaning
Time event occurred
User ID associated with the event
Command issued
Object of command
Command type (B-Database, T-Tracking,
D-Documentation, S-Staging)
Command class (D-Display, I-Invalid
commands, M-Maintenance commands,
U-Update commands)
Reserved field
Text of the command.
5.18.5 Audited Messages Report
The Audited Messages Report report lists all message records audited for
Unicenter CA-Scheduler.
CA AUDIT/VSE
SEP 22 3 CA AUDIT RECORD LISTING PAGE 1
PRODUCT: SCHEDULER
MESSAGE RECORDS
-------------------------------------------------------------------------------------------------------------------------------
DATE TIME USER COMMAND/ OBJECT/ JOB NUMBER WS MSG NUMBER MSG ID/ SCHD USER SCHD NODE MSG TEXT
SCHD NAME JOB NAME
SEV CODE
-------------------------------------------------------------------------------------------------------------------------------
22/9/3 8:18:21 STEVE4 52 SCHEDULE STARTED AT 8.18.
22/9/3 8:18:35 STEVE4 JOB1 1 4 69 JOB STARTED AT 8.18.34
22/9/3 8:18:4 STEVE4 JOB1 1 4 6 COMPLETED AT 8.18.4 COD
22/9/3 8:18:49 STEVE4 JOB2 1 4 69 JOB STARTED AT 8.18.48
22/9/3 8:18:56 STEVE4 6 COMPLETED AT 8.18.56 COD
22/9/3 8:18:56 STEVE4 JOB2 1 4 6 COMPLETED AT 8.18.56 COD
21/9/3 14:25:22 STEVE4 72 SCHEDULE STARTED AT 14.27.
21/9/3 14:25:43 STEVE4 JOB1 1 4 69 JOB STARTED AT 14.27.43
21/9/3 14:25:56 STEVE4 JOB1 1 4 6 COMPLETED AT 14.27.55 COD
21/9/3 14:28:6 STEVE4 JOB2 1 4 69 JOB STARTED AT 14.28.6
21/9/3 14:28:38 STEVE4 6 COMPLETED AT 14.28.38 COD
21/9/3 14:28:38 STEVE4 JOB2 1 4 6 COMPLETED AT 14.28.38 COD
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. A generic version of these work files was cataloged into the
Unicenter CA-Scheduler library during installation as CAWRKLAB.Z. Tailor
these files to your installation's needs and ensure that they are accessible
before running the JCL that produces the reports. To produce this report,
submit the following JCL with your job statement:
Chapter 5. Reports 5-229

5.18 Batch Reporting for CAIAUDIT
// JOB CAAUE8
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
COPY CAAUEF
COPY CAAUDCOD
COPY CAAUE8
/
The control statements that print this report are contained in the CAAUE08
source member (shown following). You may modify these statements to
produce your own reports. Printable fields are listed in the appendix
"Advantage CA-Earl Reports." (If you modify any of the source members
provided, be sure to copy them with a different name so a reinstallation of the
product will not replace the modified members.)
! SCHEDULER MESSAGE REPORTS
REPORT 'CA AUDIT RECORD LISTING'
TITLE'PRODUCT: SCHEDULER'
TITLE 'MESSAGE RECORDS'
SELECT 'A' CAAUDPRD = 'CASH' AND CAAUDPE1 = 'M'
CONTROL CAAUDDTE DOWN CAAUDTME
IFTAG A;PRINT DOUBLE SPACING CAAUDDTE CAAUDTME CAAUDUID
CAUSHSNM CAUSHJNM CAUSHJNO CAUSHWS CAUSHMNO
CAUSHMSV CAUSHSND CAUSHNOD CAUSHMTX
!
REPORT 'CA AUDIT RECORD LISTING'
TITLE'PRODUCT: SCHEDULER'
TITLE 'FULL MESSAGE TEXT'
SELECT 'A' CAAUDPRD = 'CASH' AND CAAUDPE1 = 'M'
CONTROL CAAUDDTE DOWN CAAUDTME
IFTAG A;PRINT DOUBLE SPACING CAAUDDTE CAAUDTME CAUSHMNO CAUSHMSV
CAUSHTXT
The preceding PRINT statement produces two reports. The first report lists the
message records, with the following fields:
Field On Report
DATE
TIME
USER
COMMAND/SCHD NAME
OBJECT/JOB NAME
JOB NUMBER
Meaning
Date when event occurred
Time event occurred
User ID associated with the event
Command or schedule name
Object or job name
Job's number
5-230 Unicenter CA-Scheduler Reference Guide, Part 2

5.18 Batch Reporting for CAIAUDIT
Field On Report
WS
MSG NUMBER
MSG ID/SEV CODE
SCHD USER
SCHD NODE
MSG TEXT
Meaning
Job's workstation
Message number
Message code (W-Warning, I-Information,
E-Error, A-Abend)
Unicenter CA-Scheduler user ID associated
with message.
Unicenter CA-Scheduler node from which the
message was sent
Text of the message
5.18.6 Audited Commands/Response Report
The Audited Commands/Response Report report lists all commands and
corresponding responses audited for Unicenter CA-Scheduler.
CA AUDIT/VSE
SEP 7 3 CA AUDIT RECORD LISTING PAGE 1
PRODUCT: SCHEDULER
-------------------------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------------------------
6/9/3 16:35:51 SHUT
CACM26I SCHEDULER MONITOR IS IN THE SHUTDOWN PERIOD
6/9/3 17:9:52 RUN J N=STEVE1
CACM116I RUN JOB STEVE1 DONE
7/9/3 9:38:41 D D
CACM54I LAST AUTOSCAN: JUL=325 GREG=9/5/3 TIME= 8..38 AUT
CACM54I FOR DATE: JUL=325 GREG=9/5/3 TIME= 8..
CACM54I NEXT AUTOSCAN: JUL=3251 GREG=9/8/3 TIME= 8.. AUT
CACM54I FOR DATE: JUL=3251 GREG=9/8/3 TIME= 8..
CACM54I TODAY'S DATE: JUL=325 GREG=9/5/3 TIME= 9.38.41
7/9/3 9:58:2 SHUT
CACM26I SCHEDULER MONITOR IS IN THE SHUTDOWN PERIOD
7/9/3 1:7:59 DEFINE USERID NAME=MASTER,DESC='MASTER ID',READPASS=, X
WRITPASS=,CONNECT=(4,39),TYPE=M
CACU15E DEFINE USERID MASTER DUPLICATE RECORD
JCL that produces Advantage CA-Earl reports requires the inclusion of certain
work files. A generic version of these work files was cataloged into the
Unicenter CA-Scheduler library during installation as CAWRKLAB.Z. Tailor
these files to your installation's needs and ensure that they are accessible
before running the JCL that produces the reports. To produce this report,
submit the following JCL with your job statement:
Chapter 5. Reports 5-231

5.18 Batch Reporting for CAIAUDIT
// JOB CAAUE9
: :
: :
work files
: :
: :
// EXEC EARL,SIZE=3K
OPTION SORT=SRAM
OPTION PRINTER=132
OPTION CPAGE=56
COPY CAAUEF
COPY CAAUDCOD
COPY CAAUE9
/
The control statements that print this report are contained in the CAAUE09
source member (shown following). You may modify these statements to
produce your own reports. Printable fields are listed in the appendix
"Advantage CA-Earl Reports." (If you modify any of the source members
provided, be sure to copy them with a different name so a reinstallation of the
product will not replace the modified members.)
! SCHEDULER RECORD LISTING
REPORT 'CA AUDIT RECORD LISTING'
TITLE'PRODUCT: SCHEDULER'
TITLE ' '
SELECT 'A' CAAUDPRD = 'CASH' AND CAAUDPE1 = 'C' AND
(CAAUDCFL2 = '' OR CAAUDCFL2 = '1')
SELECT 'B' CAAUDPRD = 'CASH' AND CAAUDPE1 = 'C' AND
(CAAUDCFL2 = '2' OR CAAUDCFL2 = '4')
SELECT 'C' CAAUDPRD = 'CASH' AND CAAUDPE1 = 'R'
IFTAG A;PRINT ''
''
''
IFTAG A;PRINT ' '
IFTAG A;PRINT CAAUDDTE CAAUDTME CAUSHDAT
IFTAG B;PRINT @CAUSHDAT CAUSHDAT
IFTAG C;PRINT @CAUSHDAT CAUSHRSP
The preceding PRINT statement produces a report with the following fields:
Field On Report
DATE
TIME
TEXT
Meaning
Date when event occurred
Time the event occurred
Command and response to the command
5-232 Unicenter CA-Scheduler Reference Guide, Part 2

Appendix A. Criteria Vocabulary
This appendix describes the following topics:
■
■
■
■
Reserved Words
Gregorian Calendar Conditions
Workday Conditions
Accounting Conditions
Appendix A. Criteria Vocabulary A-1

A.1 Reserved Words
A.1 Reserved Words
To Show That
Criteria consists of two or more selection
reasons, any one of which will cause a job or
schedule to be selected. (See the Unicenter
CA-Scheduler User Guide for details on the
specific uses of this keyword.)
A selection reason consists of two or more
conditions, all of which must be met for a job
or schedule to be selected
Two or more conditions count as one reason
All conditions must be satisfied except this
one negate the condition)
Specify
OR between reasons
AND between conditions
( ) around the conditions
NOT before the exception
To Show That A Predecessor Condition Causes Its
Successor To Be Selected And Is The
Start of a
schedule
job
End of a
schedule
job
Precede It With
START SCD
START
SCD
To show that the predecessor is a schedule that completed on a previous day
and thus has no effect on the selection of its successor, precede it with PRED
SCD.
To show that the predecessor is a job that completed on a previous day and
thus has no effect on the selection of its successor, precede it with PRED.
Use PRED only to identify predecessors that are NOT selected on the same
day as their successors. (For example, if the predecessor is selected on a
Monday and the successor is selected on a Friday. In this case, if both the
PRED predecessor and the successor are selected together, the successor will
wait for the PRED predecessor event to occur within this production day.)
In most cases, predecessors and successors are selected together. A job that is
selected with its successor does not need any reserved word to identify it as a
predecessor. The only reserved words required for predecessors and successors
selected together are SCD and START, as shown in the chart at the top of the
page.
A-2 Unicenter CA-Scheduler Reference Guide, Part 2

A.1 Reserved Words
To Show That The Predecessor Is The
End of a nonscheduled DOS job
End on a previous day of a nonscheduled DOS 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
GDG
User-defined event that is satisfied when an operator
or authorized user supplies a value on a SET
GBLXnn= command that matches the value specified
by the GBLxnn=value on the CRITERIA keyword
(where nn is a number from 1 to 16.)
Job running on another node of the NJE network
Precede It With
DOS
PRED DOS
DSN
GDG
PRED DSN
PRED GDG
GBLxnn=
NJE
Appendix A. Criteria Vocabulary A-3

A.2 Gregorian Calendar Conditions
A.2 Gregorian Calendar Conditions
These conditions are based on the standard Gregorian calendar and not on
workdays or accounting days; therefore, you can use these conditions in
criteria statements whether you have defined a datetable. To see what
Gregorian conditions are satisfied on any given day, consult the Date
Translation Table.
If You Specify
REQUESTED
DAILY
WEEK-DAY
WEEK-END
SUN
MON
TUE
WED
THU
FRI
SAT
MWF
TT
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
NOV
DEC
Schedules And Jobs Will Be Selected On
Request (They are actually selected every day but
must be activated by the REQUEST or SREQ
command to be moved to the active queue for
processing. Note, when using the REQUEST/SREQ
command with other criteria, that criteria are
evaluated from left to right. Therefore, if you list
REQUEST/SREQ before another condition, like JOBA,
the schedule or job will be selected every day but
must be activated by the REQUEST/SREQ
command.)
Monday through Friday
Every day, including weekends and holidays
Saturday and Sunday
Sunday
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Monday, Wednesday, and Friday
Tuesday and Thursday
January
February
March
April
May
June
July
August
September
October
November
December
A-4 Unicenter CA-Scheduler Reference Guide, Part 2

A.2 Gregorian Calendar Conditions
If You Specify
1ST
.
.
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
DAY1OF2
DAY2OF2
DAY1OF3
DAY2OF3
DAY3OF3
.
.
DAY6OF6
Schedules And Jobs Will Be Selected On
1st day of the month
through the
31st day of the month
1st Sunday of the month
2nd Sunday of the month
3rd Sunday of the month
4th Sunday of the month
5th Sunday of the month
5th Saturday of the month
Last Sunday of the month
Next to last Sunday of the month
Second to last Sunday of the month
Third to last Sunday of the month
Fourth to last Sunday of the month
.
.
Fourth to last Saturday of the month
First week of the month through the sixth week of
the month. (The first week includes those days that
precede and include the first Saturday; the second
week includes those days that follow the first
Saturday and precede and include the second
Saturday; and so on.)
First week of the year through the 53rd week of the
year.
Last week of the year through the 52nd to last week
of the year.
According to a cycle lasting from one to six days. The
base date for all cycles is Jan 1, 1900. To determine
where a specific date falls within each cycle, see the
Date Translation Table that is generated as part of
each simulation run. This will tell you, for example,
that Sept 17, 1994 is the first day in a three-day cycle
and the fourth day in a five-day cycle.
Appendix A. Criteria Vocabulary A-5

A.2 Gregorian Calendar Conditions
If You Specify
WEEK1OF2
WEEK2OF2
WEEK1OF3
WEEK2OF3
WEEK3OF3
.
.
WEEK6OF6
DOM-1
.
.
DOM-31
Y1994
.
.
Y2000
LEAP-YEAR
Schedules And Jobs Will Be Selected On
According to a cycle lasting from one to six weeks.
The base date for all cycles is Jan 1, 1900. To
determine where a specific day falls within each
cycle, see the Date Translation Table that is generated
as part of each simulation run. This will tell you, for
example, that Sept 17, 1994 falls in the first week in a
three-week cycle and in the last week in a two-week
cycle.
Last day of the month through the 30th to last day of
the month.
Year 1994 through year 2000.
Leap year.
A-6 Unicenter CA-Scheduler Reference Guide, Part 2

A.3 Workday Conditions
A.3 Workday Conditions
To use these workday conditions, you must use the Datetable Definition panel
to define workdays and holidays for three years: last year, this year, and next
year. Then you can consult the Date Translation Table to see what workday
conditions are satisfied on any given day. The following criteria keywords can
only be used if the schedule or job is selected by a datetable.
If You Specify
WDAY
HDAY
WDOW1
.
.
WDOW7
WDOW-1
.
.
WDOW-7
WDOM1
.
.
WDOM31
WDOM1
.
.
WDOM31
WWOM1
.
.
WWOM6
WWOM-1
.
.
WWOM-6
WWOY1
.
.
WWOY53
Schedules And Jobs Will Be Selected On
All workdays (days shown in high intensity on the
datetable)
All holidays (days shown in low intensity on the
datetable)
First workday of the week through the seventh workday
of the week. (Any day shown in high intensity on the
datetable is counted as a workday.)
Last workday of the week through the 6th to last
workday of the week. (Any day shown in high intensity
on the datetable is counted as a workday.)
First workday of the month through the 31st workday of
the month. (Any day shown in high intensity on the
datetable is counted as a workday.)
Last workday of the month through the 30th to last
workday of the month. (Any day shown in high
intensity on the datetable is counted as a workday.)
First work week of the month through the 6th work
week of the month. (Any week with at least one
workday is counted as a work week.)
Last work week of the month through the 5th to last
work week of the month. (Any week with at least one
workday is counted as a work week.)
First work week of the year through the 53rd work week
of the year. (Any week with at least one workday is
counted as a work week.)
Appendix A. Criteria Vocabulary A-7

A.3 Workday Conditions
If You Specify
WWOY-1
.
.
WWOY-53
RD01 = -nn
.
.
RD31 = +nn
HDAY1
.
.
HDAY31
HDAY-1
.
.
HDAY-7
Schedules And Jobs Will Be Selected On
Last work week of the year through the 52nd to last
work week of the year. (Any week with at least one
workday is counted as a work week.)
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 RD31 = +nn month
(RD03) and so on, up to the thirty-first day of the month
(RD31). For example, to select a job on the fifth
workday after the 14th of the month, specify RD14 = +5.
To select a job on the third workday before the 25th of
the month, specify RD25 = -3. (Note that nn may range
from -31 to +31, a blank must precede and follow the
equal sign, and a leading zero is not required with a
one-digit number.)
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
A-8 Unicenter CA-Scheduler Reference Guide, Part 2

A.4 Accounting Conditions
A.4 Accounting Conditions
To use these accounting conditions, you must use the Datetable Definition
panel to define which days are accounting days, when each period ends, and
when the accounting year ends. (Note that periods can be accounting periods,
production periods, sales cycles, or any other unit of time.) You must do this
for three years: last year, this year, and next year. Then you can consult the
Date Translation Table to see which accounting conditions are satisfied on any
given day.
If you have defined a prefix on the Datetable Definition panel, substitute that
prefix for the x in the words following (for example, BDAY or CDOM or
DMOY or GWOM). If you have not defined a prefix, substitute A for the x:
ADAY, ADOM, AMOY, or AWOM). If you use ADAY in a criteria statement,
accounting conditions will be taken from the A version of the datetable (the
default version). If you use BDAY in a criteria statement, accounting
conditions will be taken from the B version of the datetable. Workday and
holiday conditions are always taken from the A version. You must have
defined an 'A' datetable prefix prior to defining any other prefix for a
datetable.
If You Specify
xDAY
xDOM1
.
.
xDOM40
xDOM-1
.
.
xDOM-40
Schedules And Jobs Will Be Selected On
All accounting days (days designated on the datetable) by
A or another prefix).
First accounting day of the period through the 40th
accounting day of the period. Any day designated by A
(or another prefix) on the datetable is counted as an
accounting day. Note that to use these criteria, you must
define at least two accounting periods on the datetable.
To do this, go through the datetable and designate the
end of each period by typing a P on any date. (The end of
the period defaults to the last day of each month.)
Last accounting day of the period through the 39th to last
accounting day of the period. Any day designated by A
(or another prefix) on the datetable is counted as an
accounting day Note that to use these criteria, you must
define at least two periods on the datetable. To do this, go
through the datetable and designate the end of each
period by typing a P on any date.
Appendix A. Criteria Vocabulary A-9

A.4 Accounting Conditions
If You Specify
xMOY1
.
.
xMOY53
xMOY-1
.
.
xMOY-53
xWOM1
.
.
xWOM10
xWOM-1
.
.
xWOM-10
Schedules And Jobs Will Be Selected On
First period of the accounting year through the 53rd
period of the accounting year. Note that to use these
criteria, you must designate the ends of two accounting
years. To do this, define datetables for two years and
designate the end of each accounting year by typing an E
on any date. (The end of the accounting year defaults to
the last day of each year.)
Last period of the accounting year through the 52nd to
last period of the accounting year. Note that to use these
criteria, you must designate the ends of two accounting
years. To do this, define datetables for two years and
designate the end of each accounting year by typing an E
on any date. The end of the accounting year defaults to
the last day of each year.)
First accounting week of the period through the 10th
accounting week of the period. (Any week with at least
one accounting day counts as an accounting week.) Note
that to use these criteria, you must define at least two
periods on the datetable. To do this, go through the
datetable and designate the end of each period by typing
a P on any date. (The end of the period defaults to the
last day of each month.)
Last accounting week of the period through the 9th to last
accounting week week of the period. (Any week with at
least one accounting days count as an accounting week.)
Note that in order to use these criteria, you must define at
least two periods on the datetable. To do this, go
through the datetable and designate the end of each
period by typing a P on any date. (The end of the period
defaults to the last day of each month.)
A-10 Unicenter CA-Scheduler Reference Guide, Part 2

Appendix B. Batch Command Examples
This appendix includes Batch Command examples that illustrate the batch
commands described in the "Online Panels and Batch Maintenance" chapter.
For more information on these batch commands, refer to the corresponding
section of that chapter.
Appendix B. Batch Command Examples B-1

B.1 Stations
B.1 Stations
Following are examples of Stations batch commands.
B.1.1 Example 1: Define STation
// JOB DEFINE STATION RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE STATION ID=2,
NAME=entry,
DESC='data entry station',
/
/&
B.1.2 Example 2: ALter STation
TITLE='Data Entry Schedule'
unique station ID
station name
description
report title
The preceding example adds a data entry workstation to the database. Since
data entry tasks must be performed before jobs are processed at the CPU, the
data entry station is assigned a number lower than 40, which is the number of
the CPU station. A job that is scheduled at a pre-CPU station (numbers 01
through 39) is automatically considered to be a predecessor to the same job at
the CPU. This means that the job must have ended (using the COMPLETE
online command) at the pre-CPU station before it is available for submission at
the CPU. Thus, by defining job base records for a job at both stations 20 and
40, you ensure that the data entry task is completed before the job runs at the
CPU because Unicenter CA-Scheduler automatically enforces the processing
sequence between pre-CPU stations and the CPU. (The same sequence
enforcement is provided between the CPU and stations assigned a number
higher than 40 to ensure than a job ends successfully at the CPU before it can
be started at a post-CPU station.) The title 'Data Entry Schedule' will appear
on any simulation reports that are produced to show which jobs will be
scheduled for processing at this station on any given day.
// JOB ALTER STATION RECORD
// EXEC CAJUTIL,SIZE=24K
ALTER STATION ID=2,
/
/&
station ID from define command
TITLE='pre-cpu station (data entry)'
new title
The preceding example changes the title that will appear on all reports
produced for this workstation.
B-2 Unicenter CA-Scheduler Reference Guide, Part 2

B.1 Stations
B.1.3 Example 3: DELete STation
// JOB DELETE STATION RECORD
// EXEC CAJUTIL,SIZE=24K
DELETE STATION ID=2
/
/&
station ID from define command
The preceding example removes station 20 from the database. When a station
is deleted, you must check all userid records and job information records in
the database to see if they list this station ID on the CONNECT or ROUT
keyword. If so, you must use the ALTER command to remove this ID from the
list of stations. If you do not do this, your userid and job information records
will refer to an undefined station. (The ANALYZE command can help you
identify these undefined references.)
Appendix B. Batch Command Examples B-3

B.2 Userids
B.2 Userids
B.2.1 Example 1: Define USerid
Following are examples of Userids batch commands.
// JOB DEFINE USERID RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE USERID NAME=acctg,
logon ID
DESC='accounting dept logon id', description
READPASS=money,
read password
WRITPASS=taxes,
write password
/
/&
B.2.2 Example 2: ALter USerid
CONNECT=(4,2,39)
connect to these stations
The preceding example defines a userid for the accounting department. No
TYPE is specified; therefore, this userid has a general authority level. This
means that the userid acctg can only access stations listed after CONNECT,
and can only control schedules that authorize it on their schedule base records.
The users in this department must give the password MONEY to log on to
Unicenter CA-Scheduler to display schedules. They must also give the
password TAXES to maintain or control schedules that specify ACCTG as an
authorized USERID. When they log on, they may specify that they want to be
connected to station 40, 20 or 39. If they do not specify, they will automatically
be connected to the first station listed, which in this case is the CPU station. If
they later need to be connected to station 20 or 39, they can type in the station
ID preceded by a slash in the command input area of any panel.
// JOB ALTER USERID RECORD
// EXEC CAJUTIL,SIZE=24K
ALTER USERID NAME=acctg,
/
/&
CONNECT=(4,2,39,7)
userid from define command
add a station
The preceding example adds station 70 to the list of stations that the ACCTG
userid can connect to. Note that CONNECT on the ALTER USERID command
overlays CONNECT on the DEFINE USERID command. Therefore, the three
stations originally defined for this userid must be listed here along with the
additional station to be retained in the database. Now when users log on with
the ACCTG userid, they can connect to station 70 as well as to stations 20, 39,
and 40.
B-4 Unicenter CA-Scheduler Reference Guide, Part 2

B.2 Userids
B.2.3 Example 3: DELete USerid
// JOB DELETE USERID RECORD
// EXEC CAJUTIL,SIZE=24K
DELETE USERID NAME=acctg,
/
/&
WRITPASS=writpass
userid from define command
userid's write password
The preceding example removes the ACCTG userid from the database. When
a userid is deleted, you must check all keywords on the schedule message and
job message records and the USERID keyword on the schedule base record to
see if they list this userid. If so, you must use the ALTER command to remove
this userid from the list. If you do not do this, these records will refer to an
undefined userid. (The ANALYZE command can help you identify undefined
references.)
Appendix B. Batch Command Examples B-5

B.3 Schedules
B.3 Schedules
B.3.1 Example 1: Define SBR
Following are examples of Schedules batch commands.
// JOB DEFINE SCHEDULE BASE RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE SBR NAME=custmast,
AUTOSEL=yes,
USERIDS=(acctg,sales),
SPRTY=25,
SYSID=2,
CLASS=s,
PRTY=1,
ERLYTIME=1,
DEADLINE=17,
/
/&
MAXTIME=4
unique schedule name
automatic selection at AUTOSCAN
authorized users
schedule priority
controlling CPU
class default
priority default
earliest start time
deadline
maximum processing time
The preceding example defines a schedule named CUSTMAST that will be
automatically selected on the days specified on its criteria record. If it is not
processed on those days, it will be carried over to the next day as backlog.
The schedule can be controlled by users logging on with the ACCTG userid or
the SALES userid. This means that these users can issue online commands to
run, force, cancel, hold or release this schedule and the jobs in this schedule.
The schedule priority of 25 is high, so this schedule will be started before
many other schedules. All of the jobs in this schedule will be controlled by
CPU 2 with a class of S and a priority of 1, unless CLASS or PRTY are
overridden by different values at the job level.
The schedule cannot start until 10:00 a.m. and must end by 5:00 p.m. If it does
not complete by its deadline, a late message is issued to the userid specified on
the MSG installation option on the CAIJGEN macro. (If you want this late
message sent to users other than the one specified on the MSG installation
option, use the LATEMSG keyword on the schedule message record to specify
different users.) The schedule is also monitored in terms of its elapsed time; if
it takes longer to process than four hours, a late message is also issued.
No message is sent when the schedule starts unless the STARTMSG keyword
is specified on a schedule message record.
B-6 Unicenter CA-Scheduler Reference Guide, Part 2

B.3 Schedules
B.3.2 Example 2: Define SBR
// JOB DEFINE SCHEDULE BASE RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE SBR NAME=invntory,
PROTOTYP=custmast,
USERIDS=(dept1,boss3),
/
/&
B.3.2.1 Example 3: ALter SBR
DEADLINE=18
unique schedule name
model record
authorized users
deadline
The preceding example defines a schedule named INVNTORY. It references
CUSTMAST as its prototype so all of the information in the CUSTMAST
schedule base record is copied to the INVNTORY schedule base record. Any
keywords that need to be changed for INVNTORY can be included on this
command. Most of the values defined for CUSTMAST are also valid for
INVNTORY, except that different users are authorized to control this schedule
and the deadline is changed to 6:00 p.m.
// JOB ALTER SCHEDULE BASE RECORD
// EXEC CAJUTIL,SIZE=24K
ALTER SBR NAME=custmast,
USERIDS=acctg,
SPRTY=5,
CLASS=x,
DEADLINE=18,
/
/&
MAXTIME=43
schedule name from define command
delete one authorized user
change schedule priority
change class default
change deadline
change maximum processing time
The preceding example changes some of the values defined for the
CUSTMAST schedule. Originally, both the ACCTG and SALES userids were
authorized to control this schedule. Then it is decided to restrict this
authorization to ACCTG only. To remove SALES as an authorized userid,
specify only ACCTG on the USERIDS keyword when we submit the ALTER
SBR command. This new value will overlay USERIDS=(ACCTG,SALES) in the
database so that from now on the only authorized userid listed in the database
(for schedule CUSTMAST) is ACCTG.
It is also decided to lower this schedule's relative priority from 25 to 50. At the
same time you can extend its deadline, lengthen its maximum processing time,
and change the class that will be assigned to all of the jobs in the schedule.
Note that only the values specified here are changed in the CUSTMAST
schedule base record; the rest of the values that were defined for this record
remain the same.
Appendix B. Batch Command Examples B-7

B.3 Schedules
B.3.2.2 Example 4: DELete SBR
// JOB DELETE SCHEDULE BASE RECORD
// EXEC CAJUTIL,SIZE=24K
DELETE SBR NAME=custmast
/
/&
schedule name
The preceding example deletes the CUSTMAST schedule base record from the
database.
B.3.2.3 Example 5: DELete SCHEDULE
B.3.3 Define Criteria
B.3.3.1 Example 1: Define SCR
// JOB DELETE SCHEDULE
// EXEC CAJUTIL,SIZE=24K
DELETE SCHEDULE NAME=custmast
/
/&
schedule name
The preceding example removes the CUSTMAST schedule from the database.
It deletes the schedule base record and all other schedule records that have
been defined for CUSTMAST. Any jobs that have been assigned to this
schedule remain in the database, but they can never be selected since they are
no longer part of a schedule. Therefore, you must either delete all the jobs
within this schedule, or define a schedule with the same name.
Following are Define Criteria examples.
// JOB DEFINE SCHEDULE CRITERIA RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE SCR NAME=custmast,
/
/&
CALENDAR=tuesdays,
CRITERIA='custup1 or
pred joba or
gblc1=tp1here or
dsn ''acc.sales.totals''
schedule name from base record
calendar to be referenced
predecessor conditions
This sample criteria record directs Unicenter CA-Scheduler to select the
CUSTMAST schedule every Tuesday. (The TUESDAYS calendar was defined
online, and Tuesday was specified as the day to process any schedules and
jobs that reference this calendar.) If Tuesday is a holiday, the schedule will be
selected on Monday since PW on the prototype calendar directs Unicenter
CA-Scheduler to select schedules on the previous workday in case of a
holiday.
The CRITERIA keyword defines four predecessor conditions that must be
satisfied before this schedule starts: the CUSTUP1 job must complete if it is
also selected today; JOBA, which was selected on a previous day, must have
B-8 Unicenter CA-Scheduler Reference Guide, Part 2

B.3 Schedules
B.3.3.2 Example 2: Define SCR
B.3.3.3 Example 3: ALter SCR
been completed; the ACC.SALES.TOTALS data set must close; and the global
variable TP1HERE must be supplied. This global variable is defined so that the
schedule cannot start until a tape is delivered from another site. The variable
can be supplied by the SET GBLC1=TP1HERE online command issued by the
operator.
In summary, this schedule will be selected every Tuesday according to the
calendar workdays, and all the jobs in this schedule will run when any of the
four predecessor conditions have been satisfied (unless the individual job
criteria records specify different workdays or predecessors). Note that a
criteria record like this must be defined for every schedule unless you want it
selected for processing every workday with no predecessors.
// JOB DEFINE SCHEDULE CRITERIA RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE SCR NAME=invntory,
CRITERIA='(amoy3 and awom-1 and wdow-1 and scd qrtrly) or
(amoy6 and awom-1 and wdow-1 and scd qrtrly) or
(amoy9 and awom-1 and wdow-1 and scd qrtrly) or
(amoy12 and awom-1 and wdow-1 and scd qrtrly)'
/
/&
This sample criteria record directs Unicenter CA-Scheduler to select the
INVNTORY schedule on the last workday of the last week of the accounting
month that ends every quarter. (Workdays and accounting periods referenced
on the CRITERIA keyword are defined to Unicenter CA-Scheduler on the date
table specified on the CAIJGEN macro or on an alternate date table specified
on the DATETABL keyword in the schedule base record.) It also establishes
the QRTRLY schedule as the predecessor to the INVNTORY schedule so that
the jobs in the INVNTORY schedule cannot run until the QRTRLY schedule
jobs have ended. Since these criteria are expressed as four different reasons,
you can define a reason code record for this schedule and assign different
processing times to the schedule when it is selected for different reasons.
// JOB ALTER SCHEDULE CRITERIA RECORD
// EXEC CAJUTIL,SIZE=24K
ALTER SCR NAME=custmast,
/
/&
CRITERIA='custup1 or
pred joba or
glbl1=tp1here or
dsn ''acc.sales.totals''
or joba-2 7 custlist'
schedule name from define command
old and new predecessors
The preceding example adds a fifth predecessor condition to the four that were
originally defined for the CUSTMAST schedule. Since the CRITERIA keyword
submitted on an ALTER SCR command overlays the CRITERIA keyword
Appendix B. Batch Command Examples B-9

B.3 Schedules
B.3.3.4 Example 4: DELete SCR
B.3.4 Reasons Definition
B.3.4.1 Example 1: Define SRC
submitted on the DEFINE SCR command, you must repeat the four
predecessors previously defined to keep them in the database. If only the new
predecessor is specified here, it will replace the first four instead of joining
them. Therefore, the CRITERIA keyword above lists the four predecessors the
same way they were listed on the DEFINE command and adds the new one,
which is the completion of a job at the report distribution station, which we
are assuming is station 70. Since this job runs twice a day, the -2 qualifier is
added to the jobname to specify that the predecessor is the second occurrence
of JOBA. Since JOBA is assigned to two different schedules, the schedule
name is also given here to ensure that CUSTMAST waits for the right job to
end.
// JOB DELETE SCHEDULE CRITERIA RECORD
// EXEC CAJUTIL,SIZE=24K
DELETE SCR NAME=custmast
schedule name
/
/&
The preceding example deletes the CUSTMAST schedule criteria record.
Without a criteria record, the schedule is automatically selected for processing
every workday, which is the default selection criteria for schedules without
criteria records.
Following are Reasons Definition (Jobs) examples.
// JOB DEFINE SCHEDULE REASON CODE RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE SRC NAME=invntory,
schedule name from base record
MAX1=1,
first reason's maximum run time
MAX2=2,
second reason's maximum run time
MAX3=3,
third reason's maximum run time
MAX4=4,
fourth reason's maximum run time
DEAD1=18,
first reason's deadline
DEAD2=2,
second reason's deadline
DEAD3=23,
third reason's deadline
DEAD4=11
fourth reason's deadline
/
/&
The preceding example illustrates how you can define a schedule reason code
record for schedules that are selected for more than one reason. The
CRITERIA keyword on the schedule criteria record for the INVNTORY
schedule listed four reasons for this schedule to be selected. Since these
reasons occur later and later in the accounting year, it can be assumed that it
will take longer and longer to process this schedule each time it is selected.
Therefore, you can allow an hour to process the schedule at the end of the first
quarter and expect it to be done by 6:00 p.m.; you can allow two hours to
B-10 Unicenter CA-Scheduler Reference Guide, Part 2

B.3 Schedules
B.3.4.2 Example 2: ALter SRC
B.3.4.3 Example 3: DELete SRC
process the schedule at the end of the second quarter and expect it to be done
by 8:00 p.m.; you can allow three hours to process the schedule at the end of
the third quarter and expect it to be done by 11:00 p.m. at night. Note that the
deadline for the last quarter is set at 1:00 a.m. This is done by adding one day
to the time so that the deadline extends past midnight on the day the schedule
is selected.
// JOB ALTER SCHEDULE REASON CODE RECORD
// EXEC CAJUTIL,SIZE=24K
ALTER SRC NAME=invntory, schedule name from define command
MAX4=5,
change fourth reason's maximum run time
DEAD4=12
change fourth reason's deadline
/
/&
The preceding example changes the values defined for the INVNTORY
schedule when it is selected for the fourth reason only. Remember that the
INVNTORY schedule is selected four times a year, at the end of each
accounting quarter, and that the original reason code record defined for this
schedule increased its processing time as the year went on. At the end of the
year, you find out that the schedule takes an hour longer to process than the
four hours originally allowed. Therefore, this command increases the
maximum run time and deadline for this schedule when it is selected for the
fourth reason only. Times defined for the other three reasons remain
unchanged. Note that a one is added to the 2:00 a.m. deadline to set the
deadline at 2:00 a.m. the next day.
// JOB DELETE SCHEDULE REASON CODE RECORD
// EXEC CAJUTIL,SIZE=24K
DELETE SRC NAME=invntory
schedule name
/
/&
The preceding example deletes the schedule reason code record that was
defined and altered for the INVNTORY schedule. Deleting this record means
that the MAX and DEAD times listed on the DEFINE SRC and ALTER SRC
commands for this schedule are no longer in effect. If MAXTIME or
DEADLINE was defined on the INVNTORY schedule base record, these times
will now be assigned to the schedule when it is selected for each of its four
reason codes. If MAXTIME and DEADLINE were not defined on the schedule
base record, the schedule will still be selected for the same four reasons but
will be processed without a deadline or maximum processing time.
Appendix B. Batch Command Examples B-11

B.3 Schedules
B.3.5 Message Definition
B.3.5.1 Example 1: Define SMR
Following are Message Definition examples.
// JOB DEFINE SCHEDULE MESSAGE RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE SMR NAME=custmast,
STARTMSG=(acctg,sales),
/
/&
B.3.5.2 Example 2: ALter SMR
ENDMSG=(acctg,sales)
schedule name from base record
message when schedule starts
message when schedule ends
The preceding example defines a message record for the CUSTMAST schedule.
Messages will be sent to both the ACCTG and SALES userids when this
schedule starts and ends, regardless of which station it starts and ends at. If
this schedule misses its deadline or exceeds its MAXTIME (both defined on the
base record), late messages will be sent to the operator as specified on the
MSG installation option. Note that it is not necessary to specify LATEMSG on
this message record as long as the userid specified on the MSG installation
option is acceptable for this schedule.
// JOB ALTER SCHEDULE MESSAGE RECORD
// EXEC CAJUTIL,SIZE=24K
ALTER SMR NAME=custmast,
/
/&
B.3.5.3 Example 3: DELete SMR
LATEMSG=acctg
schedule name from define command
add userid for late messages
The preceding example adds LATEMSG to the CUSTMAST schedule message
record. When the message record was originally defined for this schedule,
userids were designated to receive start and end messages. LATEMSG was not
coded because late messages are automatically sent to the userid specified on
the MSG installation option, which is assumed to be OPERATOR. Now you
decide that you want late messages sent to the ACCTG userid instead of to the
operator. Therefore, you use this command to add LATEMSG to the message
record. Note that the values defined for STARTMSG and ENDMSG will not be
overlaid or affected by this ALTER SMR command.
// JOB DELETE SCHEDULE MESSAGE RECORD
// EXEC CAJUTIL,SIZE=24K
DELETE SMR NAME=custmast
/
/&
schedule name
The preceding example deletes the schedule message record that was defined
and altered for the CUSTMAST schedule. Deleting this record means that start,
end, late and miscellaneous messages will no longer be sent to the userids
B-12 Unicenter CA-Scheduler Reference Guide, Part 2

B.3 Schedules
B.3.6 Info Definition
B.3.6.1 Example 1: Define SIR
listed on the DEFINE SMR and ALTER SMR commands for this schedule.
However, in the absence of this message record, late messages and
miscellaneous messages will go to the userid defined on the MSG installation
option as the default message receiver for late and miscellaneous messages.
Messages about individual jobs in this schedule will still go to the userids
specified on the job message records.
Following are Info Definition examples.
// JOB DEFINE SCHEDULE INFORMATION RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE SIR NAME=custmast,
COMMENT='check output',
DEL1=reporta,
DEL2=reportb,
DEL3=reportc,
DESC='customer master file',
DEST1=jones,
DEST2=smith,
DEST3=clark,
FORM=123456,
NOTIFY=accounting,
QUANTITY=3,
/
/&
B.3.6.2 Example 2: ALter SIR
RESP=johnsmith
schedule name from base record
comment
deliverable
deliverable
deliverable
description
destination
destination
destination
form number
department to notify
amount of output
person reponsible
The preceding example defines an information record for the CUSTMAST
schedule.
// JOB ALTER SCHEDULE INFORMATION RECORD
// EXEC CAJUTIL,SIZE=24K
ALTER SIR NAME=custmast,
schedule name from define command
DEL4=reportd,
add fourth deliverable
DEST4=wilson,
add fourth destination
FORM=null,
delete form number
QUANTITY=4
change amount of output
/
/&
The preceding example changes some of the values that were defined for the
CUSTMAST schedule information record. The output quantity is changed from
three reports to four, and delivery information is added for the fourth report.
Note that both DEL and DEST are coded with a suffix from one to eight so
that you can define up to eight different deliverables and destinations. It is
therefore possible to add a fourth deliverable using the keyword DEL4 without
overlaying the values already defined for DEL1, DEL2, and DEL3; they will
remain in the database as originally defined and do not have to be repeated
Appendix B. Batch Command Examples B-13

B.3 Schedules
B.3.6.3 Example 3: DELete SIR
here. In the same way, we can add DEST4 without repeating DEST1, DEST2,
and DEST3.
It is decided to delete the form number originally defined for this schedule. To
delete a keyword from a record without deleting the whole record, you submit
the keyword with the value NULL. The null value overlays the 123456 value
specified for FORM and has the effect of deleting the form number from the
information record.
// JOB DELETE SCHEDULE INFORMATION RECORD
// EXEC CAJUTIL,SIZE=24K
DELETE SIR NAME=payschd
/
/&
The preceding example deletes the schedule information record for the
PAYSCHD schedule. Deleting the information record does not affect the
schedule's selection or processing.
B-14 Unicenter CA-Scheduler Reference Guide, Part 2

B.4 Jobs
B.4 Jobs
B.4.1 Define JBR
B.4.1.1 Example 1:
This topic discusses the various Job Definition batch jobs and gives examples
for each of the definitions.
Following are examples of the Define JBR.
// JOB DEFINE JOB BASE RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE JBR NAME=cust1,
JNO=2,
SCHEDULE=custmast,
ERLYTIME=11,
MAXTIME=59,
JPRTY=5,
LIBT=driver,
LIBM=jcl1,
ABEND=abndschd,
STAGE=yes,
MEMO='is tape mounted?',
/
/&
INTERUPT=yes
jobname
second occurrence within schedule
schedule name
early start time
maximum execution time
priority within schedule
library
member name
abend action
staging required
request operator reply
post job as INTERRUPTED
The preceding example defines a job that must be run twice as part of the
CUSTMAST schedule. The first occurrence was defined in a separate job base
record with JNO=01. (If no JNO is specified, 01 is assumed.) Since no station
ID is specified, the CPU is assumed so this job will be scheduled twice at the
CPU whenever it is selected for processing.
This occurrence of the job will have the same CLASS, PRTY, and SYSID values
as the rest of the CUSTMAST schedule. ERLYTIME for this job is defined as
11:00 a.m. and a maximum execution time of 59 minutes is defined. (Note that
an individual job can start later than the rest of the schedule, but not earlier.)
This job will have a priority of 50 relative to the other jobs in this schedule.
Since this is a computer job, information that identifies the alternative schedule
is provided in the JCL and an alternative schedule, ABNDSCHD, is specified
to run if this job abends. This job requires JCL changes so the JCL is
submitted to the staging library when the job is selected; this is indicated by
the STAGE=yes specification. This job also requires that a tape be mounted so
the MEMO keyword is used to issue a message to the operator when the job is
initiated. The operator must reply OK or TERM. If he replies OK, the job can
run; if he replies TERM, the job is flushed.
The INTERUPT keyword is used so that the job's status will be shown as
INTERRUPTED instead of COMPLETED when the job ends successfully. This
Appendix B. Batch Command Examples B-15

B.4 Jobs
B.4.1.2 Example 2: Define JBR
interruption allows the operator to check the output and manually end the job
if the output is satisfactory or rerun the job if the output is unsatisfactory.
Successors to the job cannot run until the operator issues the COMPLETE
command that changes the job's status to COMPLETE. Note that the
INTERMSG keyword is used on a message record for this job to notify the
operator when the job is interrupted.
// JOB DEFINE JOB BASE RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE JBR NAME=cust1,
JNO=2,
SCHEDULE=custmast,
STATION=39,
DISPKEY=setupcu1,
/
/&
DEADLINE=15
jobname
second occurrence within schedule
schedule name
JCL setup station
documentation member name
deadline
The preceding example defines a job base record for CUST1 at station 39. This
schedules the job at the JCL setup station whenever it is selected, so JCL
changes can be made before the job continues on its path to the computer.
(Note that STAGE=Yes is specified on the job base record of the CPU station
so that the JCL is written to the staging library when the job is selected.) Note
that it is the second occurrence of CUST1 that is being scheduled at station 39.
If the first occurrence requires JCL changes, a separate job base record at
station 39 has to be defined for it.
Documentation on the setup procedure has been stored in the documentation
library under the member name SETUPCU1. Including DISPKEY on this job's
record will send a message to whoever starts this job at station 39 telling that
person what display key to use to find the setup instructions. This ensures
that the correct JCL changes are made.
A deadline of 10:50 a.m. is assigned to the job at the setup station so that it
will be ready to meet its ERLYTIME of 11:00 a.m. at the CPU. If the job starts
too late to meet its deadline or has not completed by its deadline, a late
message is sent to the userid specified on the MSG keyword on the CAIJGEN
macro. (If a job message record is defined for this job at this station, the
LATEMSG keyword can be used to specify up to four users who will receive
this message instead of the userid specified on the CAIJGEN macro.)
B-16 Unicenter CA-Scheduler Reference Guide, Part 2

B.4 Jobs
B.4.1.3 Example 3: Define JBR
// JOB DEFINE JOB BASE RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE JBR NAME=cust1,
JNO=1,
SCHEDULE=sales,
PROTOTYP=cust1,
PROTOSCD=custmast,
PROTOJNO=2,
DEADLINE=null,
ERLYTIME=8,
JPRTY=9,
DISPKEY=tapes,
/
/&
B.4.1.4 Example 4: ALter JBR
DISPTIME=8
jobname
first occurrence within schedule
schedule name
model jobname
model schedule name
model job number
delete deadline from new record
modified early start time
modified priority
documentation member name
documentation display time
The preceding example defines a job base record for CUST1 as part of the
SALES schedule. This means that the CUST1 job will be selected as part of the
CUSTMAST schedule (as previously defined) and also as part of the SALES
schedule. Since CUST1 has the same library information regardless of which
schedule it belongs to, the easiest way to create another job base record for it is
to copy the record that was previously defined. To do this, specify CUST1 as
the prototype jobname and CUSTMAST as the prototype schedule name. All
of the information previously defined is copied to the new record, except
DEADLINE. Any keywords that need to be modified to fit the requirements
of the SALES schedule can be specified here. Note that the prototype job
number must also be specified to copy the second occurrence of CUST1 in the
CUSTMAST schedule. But since it will run only once as part of the SALES
schedule, JNO is changed to 01 on the new record.
In addition to the ERLYTIME and JPRTY keywords that are modified to fit the
requirements of the SALES schedule, DISPKEY AND DISPTIME are added.
These direct Unicenter CA-Scheduler to display the documentation stored
under TAPES in the documentation library at 8:00 a.m. The operator can then
follow these instructions when this job is submitted.
// JOB ALTER JOB BASE RECORD
// EXEC CAJUTIL,SIZE=24K
ALTER JBR NAME=cust1,
JNO=2,
SCHEDULE=custmast,
ERLYTIME=1,
ABEND=CONT,
/
/&
INTERUPT=no
jobname from define command
job number from define command
schedule name from define command
new early start time
change abend action
stop interrupting job
The preceding example changes some of the values defined for the CUST1 job
when it is selected for the second time as part of the CUSTMAST schedule. To
make sure the right record is changed, you specify both the schedule name
Appendix B. Batch Command Examples B-17

B.4 Jobs
B.4.1.5 Example 5: DELete JBR
and job number. (You do not have to specify STATIO because the CPU station
is assumed.) The ERLYTIME on this record is changed from 11:00 a.m. to
10:00 a.m., which is the early start time of the rest of the schedule. (A time
earlier than 10:00 a.m. would create a conflict since an individual job cannot
start earlier than its schedule.) The action to be taken if this job abends is
changed to CONT, which tells Unicenter CA-Scheduler to continue to post
successors even if this job abends. And, last, INTERUPT is changed from Yes
to No because this job need no longer be interrupted for operator intervention
before it ends successfully. Note that INTERUPT=NO is a default value, which
need not be specified on a define command, but is required on an ALTER
command to overlay INTERUPT=Yes which was originally defined for this job.
// JOB DELETE JOB BASE RECORD
// EXEC CAJUTIL,SIZE=24K
DELETE JBR NAME=cust1,
SCHEDULE=custmast,
/
/&
B.4.1.6 Example 6: DELete JOB
STATION=39
jobname
schedule name
station number
The preceding example deletes the job base record that schedules the first
occurrence of the CUST1 job at the JCL setup station when it is selected as part
of the CUSTMAST schedule. Note that this command does not affect the job at
the CPU. It will still be scheduled at the CPU when CUSTMAST is selected,
but it will no longer be scheduled for JCL setup. Therefore, the job can be
submitted at the CPU without waiting for it to be completed at station 39.
We highly recommend that you always use DELETE Job instead of DELETE
JBR. The DELETE JBR does not delete any other associated job records (that is,
job message record); those records need to be deleted specifically.
// JOB DELETE JOB
// EXEC CAJUTIL,SIZE=24K
DELETE JOB NAME=cust1,
SCHEDULE=custmast,
/
/&
JNO=2
jobname
schedule name
job number
The preceding example deletes all of the job records defined for the CUST1 job
when it runs at the CPU for the second time as part of the CUSTMAST
schedule. Note that it does not delete job records that have been defined for
the first occurrence of CUST1, for CUST1 at peripheral stations, or for CUST1
as part of any schedule other than CUSTMAST.
B-18 Unicenter CA-Scheduler Reference Guide, Part 2

B.4 Jobs
B.4.2 Define Criteria
B.4.2.1 Example 1: Define JCR
Following are examples of Define Criteria.
// JOB DEFINE JOB CRITERIA RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE JCR NAME=custeom,
SCHEDULE=custmast,
CALENDAR=firtue,
/
/&
B.4.2.2 Example 2: Define JCR
CRITERIA='pred eominput'
jobname from base record
schedule name from base record
first Tuesday of month calendar
predecessor from previous day
This sample criteria record controls when the CUSTEOM job is selected and
scheduled at the CPU and any other stations in its path. (Its path is made up
of all of the stations at which it is scheduled for processing. See DEFINE JBR.)
This schedule needs to be selected on the middle Tuesday of each month.
Therefore, its job criteria record references a different calendar, one named
FIRTUE, which defines the first Tuesday of each month as its work days.
(Remember that an individual job can be selected less frequently than the rest
of the schedule, but not more frequently.)
In addition, it needs input from the EOMINPUT job, so EOMINPUT is defined
as a predecessor to CUSTEOM. The EOMINPUT job runs on Monday, so it is
preceded by the reserved word PRED. This tells Unicenter CA-Scheduler that
this predecessor is selected on a different day from its successor. When the
EOMINPUT job completes on Monday, this information is posted to the
database and stored until it is needed on Tuesday to satisfy the CUSTEOM
predecessor condition. Then this information is cleared from the database.
Note that if no job criteria record were defined for this job, it would be run
every day with the rest of the CUSTMAST schedule.
// JOB DEFINE JOB CRITERIA RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE JCR NAME=joba,
SCHEDULE=everyday,
CRITERIA=mon,
/
/&
STATION=39
jobname from base record
schedule name from base record
select on Monday
only at one station
This sample criteria record controls the selection of a job that requires JCL
setup only when it runs on Monday. It is assumed that this job is part of a
schedule that has no schedule criteria record and therefore is selected every
workday by default. It is further assumed that each of the jobs in the schedule
has been defined in a job base record and an additional job base record was
defined for JOBA at station 39. Without this job criteria record, JOBA will be
Appendix B. Batch Command Examples B-19

B.4 Jobs
B.4.2.3 Example 3: Define JCR
scheduled for processing at station 39 every workday when it is selected as
part of its schedule. Since JCL setup is required only on Monday, this job
criteria record tells Unicenter CA-Scheduler to schedule JOBA at station 39
only on Monday even though it is scheduled at the CPU every day of the
week.
// JOB DEFINE JOB CRITERIA RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE JCR NAME=custeow,
SCHEDULE=custmast,
/
/&
B.4.2.4 Example 4: ALter JCR
CRITERIA='start scd sales'
jobname from base record
sched name from base record
additional predecessor
This sample criteria record adds a predecessor condition to a job called
CUSTEOW, which is selected every Tuesday as part of the CUSTMAST
schedule. Note that the CUSTMAST schedule cannot start until any of the four
predecessors defined on its schedule criteria record are satisfied. In addition,
this particular job cannot start until the SALES schedule starts. This additional
predecessor is described by the use of the reserved words SCD and START,
which indicate to Unicenter CA-Scheduler that this predecessor is a schedule
rather than a job and that the schedule must start rather than end before its
successor can run.
// JOB ALTER JOB CRITERIA RECORD
// EXEC CAJUTIL,SIZE=24K
ALTER JCR NAME=custeom, jobname from define command
SCHEDULE=custmast, schedule name from define command
CRITERIA='start jobx custlist or
pred scd abc or
pred dos jd1' new predecessors
/
/&
The preceding example changes the criteria defined for the CUSTEOM job
when it is selected as part of the CUSTMAST schedule. The criteria that was
previously defined for this job, the completion of the EOMINPUT job, is no
longer valid, so that jobname is not repeated on this command. Instead, three
new predecessor conditions are substituted: the start of JOBX when it runs as
part of the CUSTLIST schedule, the end of the ABC schedule, and the end of a
DOS job that is not defined in the Unicenter CA-Scheduler database. Note that
the ABC schedule and the DOS job are preceded by the PRED reserved word,
which means that they are only predecessors to CUSTEOM; they do not
control its selection. In fact, they were probably selected and processed on a
previous day.
Since there is no change to the calendar defined for this job, CALENDAR is
not coded here.
B-20 Unicenter CA-Scheduler Reference Guide, Part 2

B.4 Jobs
B.4.2.5 Example 5: DELete JCR
// JOB DELETE JOB CRITERIA RECORD
// EXEC CAJUTIL,SIZE=24K
DELETE JCR NAME=custeom,
/
/&
SCHEDULE=custmast
B.4.3 Reasons Definition (Jobs)
B.4.3.1 Example 1: Define JRC
jobname
schedule name
The preceding example deletes the job criteria record that was defined and
altered for the CUSTEOM job when it is selected as part of the CUSTMAST
schedule. Note that this command does not delete the entire CUSTEOM job.
Deleting the job criteria record only means that this job will be selected along
with the rest of the CUSTMAST schedule as defined on the schedule criteria
record.
Following are examples of Reasons Definition (Jobs).
// JOB DEFINE JOB REASON CODE RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE JRC NAME=endoqrtr,
SCHEDULE=invntory,
ERLY1=8,
ERLY2=18,
ERLY3=28,
/
/&
ERLY4=38
jobname from base record
schedule name from base record
first reason's early start time
second reason's early start time
third reason's early start time
fourth reason's early start time
The preceding example defines a job reason code record for the job
ENDOQRTR, which is part of the INVNTORY schedule. As part of the
INVNTORY schedule, it will be selected for processing four times a year, so a
different early start time can be defined for the job each time it is selected.
When it is selected for the first reason, it can start as early as 8:00 a.m. When
it is selected for the second reason, it cannot start until 8:00 a.m. one day after
it is selected. When it is selected for the third reason, it cannot start until 8:00
a.m. two autoscan days after it is selected. And when it is selected for the
fourth reason, it cannot start until 8:00 a.m. three autoscan days after it is
selected.
Appendix B. Batch Command Examples B-21

B.4 Jobs
B.4.3.2 Example 2: ALter JRC
B.4.3.3 Example 3: DELete JRC
// JOB ALTER JOB REASON CODE RECORD
// EXEC CAJUTIL,SIZE=24K
ALTER JRC NAME=endoqrtr, jobname from define command
SCHEDULE=invntory, schedule name from define command
ERLY1=9,
change first reason's early start time
ERLY2=19,
change second reason's early start time
ERLY3=29,
change third reason's early start time
ERLY4=39
change fourth reason's early start time
/
/&
The preceding example changes the early start times defined for the
ENDOQRTR job that is selected for processing four times a year as part of the
INVNTORY schedule. The four early start times are changed from 8:00 to 9:00
a.m. The job is still scheduled not to start until one autoscan day after
selection when it is selected for the second reason, two autoscan days after
selection when it is selected for the third reason, and three autoscan days after
selection when it is selected for the fourth reason.
// JOB DELETE JOB REASON CODE RECORD
// EXEC CAJUTIL,SIZE=24K
DELETE JRC NAME=endoqrtr,
/
/&
B.4.4 Message Definition
B.4.4.1 Example 1: Define JMR
SCHEDULE=invntory
jobname
schedule name
The preceding example deletes the reason code record that was defined and
altered for the ENDOQRTR job when it is selected as part of the INVNTORY
schedule. When this reason code record is deleted, the early start time for this
job is taken from ERLYTIME on the job base record, if one was defined, or
ERLYTIME on the schedule base record. If no ERLYTIME has been defined for
either the job or the schedule, the job becomes available for processing as soon
as the database is scanned at AUTOTIM, unless it is waiting for predecessors
or resources.
Following are examples of Message Definition.
B-22 Unicenter CA-Scheduler Reference Guide, Part 2

B.4 Jobs
B.4.4.2 Example 2: ALter JMR
// JOB DEFINE JOB MESSAGE RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE JMR NAME=cust1,
jobname from base record
JNO=2,
job number from base record
SCHEDULE=custmast, schedule name from base record
ABENDMSG=operator, send message if job abends
INTERMSG=operator, send message when job is INTERRUPTED
LATEMSG=acctg send message if job exceeds MAXTIME
/
/&
This sample job message record notifies the operator when this job abends or
ends. (Note that it will be posted as INTERRUPTED instead of COMPLETED if
it ends successfully.) The interrupt message notifies the operator that this job
requires manual intervention and must be manually completed so that its
successors can be processed.
A late message will be sent to the ACCTG userid if this job misses its
MUSTTIME or deadline or exceeds its MAXTIME. Since only one of these
values was assigned to the job on the job base record, a late message will only
be issued if the job exceeds its maximum execution time of 59 minutes. If this
happens, ACCTG can cancel the job since it is one of the userids authorized on
the CUSTMAST schedule base record to control the jobs in this schedule.
Note that late messages would be sent to the userid specified on the CAIJGEN
macro MSG option even if LATEMSG was not coded here.
// JOB ALTER JOB MESSAGE RECORD
// EXEC CAJUTIL,SIZE=24K
ALTER JMR NAME=cust1,
jobname from define command
JNO=2,
job number from define command
SCHEDULE=custmast, schedule name from define command
INTERMSG=null, delete interrupt message
ENDMSG=acctg add end message
/
/&
The preceding example changes the message record values defined for this job
when it runs for the second time as part of the CUSTMAST schedule. Since the
job base record was altered so that this job is no longer interrupted for manual
intervention, the operator need no longer receive an interrupt message.
Instead of deleting the whole job message record, it is possible to delete just
the INTERMSG keyword by changing its value to NULL. This will overlay the
INTERMSG=OPERATOR value in the job message record and have the effect
of stopping the interrupt message.
Since this job will now be posted as COMPLETE as soon as it ends
successfully, this command adds the ENDMSG keyword to the job message
record to notify ACCTG that the job has ended successfully. Note that
ENDMSG was coded for the CUSTMAST schedule message record, but end
Appendix B. Batch Command Examples B-23

B.4 Jobs
B.4.4.3 Example 3: DELete JMR
messages are only sent for individual jobs if ENDMSG is also coded on the job
message record.
// JOB DELETE JOB MESSAGE RECORD
// EXEC CAJUTIL,SIZE=24K
DELETE JMR NAME=cust1,
SCHEDULE=custmast,
/
/&
B.4.5 Info Definition
B.4.5.1 Example 1: Define JIR
JNO=2
jobname
schedule name
job number
The preceding example deletes the message record that was defined and
altered for this job when it runs for the second time as part of the CUSTMAST
schedule. Messages will no longer be sent when this job ends, abends, is late,
or fails. After this record has been deleted, late messages will still be sent to
the MSG userid specified in the CAIJGEN installation macro.
Following are examples of Info Definition.
// JOB DEFINE JOB INFORMATION RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE JIR NAME=cust1,
jobname from base record
JNO=2,
job number from base record
SCHEDULE=custmast,
schedule name from base record
COMMENT='change JCL if job fails', comment
DESC='edit job',
description
/
/&
B.4.5.2 Example 2: ALter JIR
RESP=maryjones
person reponsible
This sample job information record provides information on the CUST1 job
when it runs as part of the CUSTMAST schedule for the second time. This
information is in addition to the information already provided on the schedule
information record for all of the jobs in the CUSTMAST schedule. In this
example, the COMMENT, DESCRIPTION, and RESPONSIBLE fields have been
changed to provide information that applies specifically to this one job.
// JOB ALTER JOB INFORMATION RECORD
// EXEC CAJUTIL,SIZE=24K
ALTER JIR NAME=cust1,
JNO=2,
SCHEDULE=custmast,
/
/&
RESP=tomsmith
jobname from define command
job number from define command
schedule name from define command
change value
B-24 Unicenter CA-Scheduler Reference Guide, Part 2

B.4 Jobs
B.4.5.3 Example 3: DELete JIR
The preceding example changes the person responsible for this job from Mary
Jones to Tom Smith.
// JOB DELETE JOB INFORMATION RECORD
// EXEC CAJUTIL,SIZE=24K
DELETE JIR NAME=cust1,
SCHEDULE=custmast,
/
/&
B.4.6 Resource Definition
B.4.6.1 Example 1: Define JRR
STATION=39
jobname
schedule name
station ID
The preceding example deletes the job information record that was defined for
the CUST1 job when it is selected as part of the CUSTMAST schedule and
processed at station 39. This command does not affect the selection of this job
or its processing at station 39; it only deletes the job information record.
Following are Resource Definition examples.
// JOB DEFINE JOB RESOURCE RECORD
// EXEC CAJUTIL,SIZE=24K
DEFINE JRR NAME=cust1,
SCHEDULE=sales,
SEP=(joba,jobb,jobc),
VOLSER=work1,
/
/&
RDT=3
jobname from base record
schedule name from base record
wait until these jobs end
wait until this volume is mounted
routing delay time
This sample job resource record directs Unicenter CA-Scheduler to run CUST1
separately from JOBA, JOBB, and JOBC. (Note that SEP=CUST1 must also be
specified on each of their job records.) If CUST1 becomes available for
processing while any of these jobs is running, Unicenter CA-Scheduler will
wait to submit it until that job ends.
This resource record also directs Unicenter CA-Scheduler to wait until DASD
pack WORK01 is mounted before submitting CUST1.
A routing delay time is also assigned to the job at this station. This allows the
job a half hour to get to the CPU station from the previous station on its path,
which you can assume is the data entry station. This delay time is taken into
account on the simulation reports that map out when each job can be
processed at each station.
Appendix B. Batch Command Examples B-25

B.4 Jobs
B.4.6.2 Example 2: ALter JRR
// JOB ALTER JOB RESOURCE RECORD
// EXEC CAJUTIL,SIZE=24K
ALTER JRR NAME=cust1,
JNO=2,
SCHEDULE=custmast,
/
/&
B.4.6.3 Example 3: DELete JRR
SEP=joba
jobname from define command
job number from define command
schedule name from define command
change jobs that must run separately
The preceding example changes the value defined for the SEP keyword in the
job resource record. The jobname, schedule name, and job number are coded
exactly as they were when the job resource record was defined. The
requirements for running this job have changed so that it only has to be run
separately from one of the three jobs previously listed on the SEP keyword.
Therefore, the SEP command is coded here with only one jobname. The other
keywords defined on the job resource record remain as defined.
// JOB DELETE JOB REASON CODE RECORD
// EXEC CAJUTIL,SIZE=24K
DELETE JRR NAME=cust1,
SCHEDULE=custmast,
/
/&
JNO=2
jobname
schedule name
job number
The preceding example deletes the job resource record for the CUST1 job when
it runs for the second time as part of the CUSTMAST schedule. This means
that CUST1-2 will no longer have to wait for a volume to be mounted or for
other jobs to end. Also, any statistics defined in the job resource record will no
longer have an effect on a simulation run. The other job records for CUST1
remain in the database as defined.
B-26 Unicenter CA-Scheduler Reference Guide, Part 2

B.4 Jobs
B.4.7 Defining Resources
Following are Defining Resources examples.
B.4.7.1 Example 1: Define RESource
// JOB DEFINE RESOURCES FOR ONE SUBSTATION
// EXEC CAJUTIL,SIZE=24K
DEFINE RESOURCE SYSID=1, CPU 1
STATION=4,
station number
DASD1=(339,1),
number of 339s
DASD2=(338,12),
number of 338s
TAPE1=(342,2),
number of 342s
TAPE2=(348,16),
number of 348s
UR1=(254,11),
number of 254s
PART1=(abc,bg),
first partition's classes,header
PART2=(bcd,f2),
second partition's classes,header
PART3=(cd,f3),
third partition's classes,header
PST=8,
production start time
PET=17,
production end time
AVGTIME=2,
default process time
RDT=15,
default routing delay time
/
/&
DEFCLASS=A
default job class
The preceding example describes the DASD, tape and unit record devices that
can be used exclusively by one of the CPUs. It also specifies which class of
jobs can be run in each of the partitions: classes A, B, or C jobs can run in BG;
classes B, C, or D can run in F2, and so forth. The names of each of the
partitions are used as headers across the top of the simulation reports for this
CPU and the specific jobs that will run in each partition are listed under that
header.
The preceding example also defines the production start and end time for this
CPU: processing will begin every day at 8:00 a.m. and last until 5:00 p.m.
Therefore, Unicenter CA-Scheduler will not simulate any processing at this
CPU before 8:00 a.m. or after 5:00 p.m. The last three keywords assign a
default process time, routing delay time, and class to all jobs that do not have
these values, either on their job base records or as part of a schedule. Jobs
with no AVGTIME will be assigned the default average process time of two
hours. Jobs with no RDT will be assigned the default routing delay time from
the previous station of 15 minutes. Jobs with no CLASS will be treated as class
A jobs.
Appendix B. Batch Command Examples B-27

B.4 Jobs
B.4.7.2 Example 2: Define RESource
// JOB DEFINE RESOURCES FOR ONE STATION
// EXEC CAJUTIL,SIZE=24K
DEFINE RESOURCE STATION=2,
data entry station
UNIT1=(abc,tom),
first device's classes, header
UNIT2=(bcd,mary),
second device's classes, header
UNIT3=(cd,joe),
third device's classes, header
UNIT4=(a,sue),
fourth device's classes, header
UNIT5=(ab,jim)
fifth device's classes, header
/
/&
The preceding example defines the five keypunch units at the data entry
station. A unit, in this example, consists of a keypunch device and its operator.
The UNIT keyword assigns different classes of jobs to each unit: the first
keypunch operator can process class A, B, and C jobs, the second operator can
process class B, C, and D jobs, and so forth. Note that instead of naming the
devices, you use the names of the operators as headings on the simulation
reports. Simulation will then assign the appropriate jobs to each operator, and
the reports will map out which jobs are to be processed by each operator
throughout the day.
If operators at your site share devices, you must code the UR keyword so that
Unicenter CA-Scheduler will schedule jobs for the actual number of devices
that exist. For example, if the total number of operators (specified with UNIT=)
is different from the total number of physical devices that exist at your site,
you need to code a UR= statement in addition to the UNIT= statements.
Suppose five keypunch operators share four physical keypunch devices. After
you specify a UNIT= statement for each of the operators, code UR=(2540, 4) to
indicate that only four physical devices (type=2540) exist.
B-28 Unicenter CA-Scheduler Reference Guide, Part 2

B.4 Jobs
B.4.7.3 Example 3: ALter RESource
// JOB ALTER RESOURCES FOR ONE SUBSTATION
// EXEC CAJUTIL,SIZE=24K
ALTER RESOURCE SYSID=1, CPU 1
DASD2=(338,14),
number of 338s
PART1=(a,bg),
first partition's classes,header
PART2=(b,f2),
second partition's classes,header
PART3=(bcd,f3)
third partition's classes,header
PST=7,
production start time
/
/&
PET=19
B.4.7.4 Example 4: DELete RESource
production end time
The preceding example increases the number of 3380 disk devices that can be
used exclusively by CPU 1. It also changes the class of jobs that can be run in
each partition: now only class A jobs can run in BG, only class B jobs can run
in F2, and class B jobs can run in F3 in addition to classes C and D as
originally defined. Even though the only change to the PART03 keyword is the
addition of Class B jobs, classes C and D are repeated here. This is because
PART03 here completely overlays PART03 on the DEFINE RESOURCE
command; therefore, the two original classes must be repeated to retain them
in the database. The preceding example also changes the production start and
end time for this CPU so that processing can now be simulated from 7:00 a.m.
to 7:00 p.m.
// JOB DELETE RESOURCES FOR ONE SUBSTATION
// EXEC CAJUTIL,SIZE=24K
DELETE RESOURCE STATION=4,
SYSID=1
/
/&
The preceding example deletes the resource record that was defined for CPU 1.
If resource records were defined for other SYSIDs, they are not affected by this
DELETE command.
Appendix B. Batch Command Examples B-29

Appendix C. Editor Commands
This appendix gives the following detailed instructions on how to use the
various editor commands associated with Unicenter CA-Scheduler:
■
■
■
■
■
Line Protection and Highlighting
Input Area Commands
Prefix Area Commands
Staging Editor Commands
PF Key Settings
Appendix C. Editor Commands C-1

C.1 Line Protection and Highlighting
C.1 Line Protection and Highlighting
Use these letters to protect and highlight lines in
■
■
■
Staged JCL
Unicenter CA-Driver procedures.
Members of the documentation file
To specify one of these letters in column 73, use the RANGE command (on
page &range) to include column 73 in the range. The lines that require one of
these control characters can also be designated at their original source. For
example, a CMS JCL member needs to have a parameter card protected while
being edited in the staging library. To accomplish this, always edit the CMS
member (using a CMS editor) to place a P in column 73 of the parameter card.
To Type This In Column 73
Protect a line
Highlight a line
Both protect and highlight a line
Protect a line and keep it from displaying
P
H
F
D
Note that these letters can be changed on the installation macro. To see if they
have been changed, check the EDTPCHR, EDTHCHR, and EDTPHCHR
options in the CAIJGEN macro. To see if the column number has been
changed, check the EDTATC option. Protect and invisible are not enforced for
Unicenter CA-Scheduler's Manager type userids.
C-2 Unicenter CA-Scheduler Reference Guide, Part 2

C.2 Input Area Commands
C.2 Input Area Commands
Use these editor commands to:
■
■
■
■
Define or alter criteria records
Define or alter members of the documentation file
Alter staged JCL
Define or alter Unicenter CA-Driver procedures.
Command abbreviations are shown in upper case. Optional operands are
shown in parentheses. If you do not specify a number where a command calls
for a number, 1 is assumed.
To
Leave the panel you are editing
and enter new values in
the database or
staging file
without saving any values
Save new values without leaving the panel (not
applicable to criteria modification)
Repeat the last command you entered =
Execute a command and keep the cursor after ====>
Set a key to perform a command, where
key can be PFn, PAn, CLEAR, or ENTER
(Note: See PF key editor defaults.)
Go
to first line of file
to last line of file
backward n panels (toward first line of file)
forward n panels (toward last line of file)
Move the panel display
up n lines (toward first line of file)
down n lines (toward last line of file)
to right or left so that column n is the first
column displayed on the panel
Limit the LOCATE or CHANGE commands to specific
columns: from column c to column d
Type This After
====>
FILE
Quit
Save
&command
SET key
command
Top
BOttom
Backward (n)
Forward (n)
Up (n)
Down (n)
Next (n)
COLumn n
Range c d
Appendix C. Editor Commands C-3

C.2 Input Area Commands
To
Find the first occurrence of character string s
anywhere in the file
at the beginning of a line
(embedded blanks are not allowed)
Replace character string s with character string t
anywhere in the file
starting at line l
only from lines l to m
(embedded blanks are not allowed)
Add n blank lines after line l
Delete n lines starting with line l
Copy
line l and insert it after line m
n number of lines, starting with line l, and insert them
after line m
Move
line l after line m
n number of lines, starting with line l, and insert them
after line m
Display
numbers in the line-command area
====== in the line-command area
Type This After
====>
Locate s
FInd s
CHange s t
CHange s t l
CHange s t l m
Add l (n)
DElete 1 (n)
Copy 1 m
Copy 1 m n
Move 1 m
Move 1 m n
NUm
NOnum
C-4 Unicenter CA-Scheduler Reference Guide, Part 2

C.3 Prefix Area Commands
C.3 Prefix Area Commands
You can also add, delete, copy, and move lines by moving the cursor to the
prefix area. This area is located at the far right of the panel, beginning at the
editor-generated line number. To use the following commands, overtype this
line number.
To
Make this the current line /
Add lines
Delete
one or more lines
a block of lines
Copy
one or more lines
a block of lines
Move
one or more lines
a block of lines
Place the moved or copied lines
after this line
before this line
Duplicate a line n times
Type
A(n) or (n)A
D(n) or (n)D
DD
C(n) or (n)C
CC
M(n) or (n)M
MM
F
P
"(n) or (n)"
Examples of these prefix area commands appear on the following pages.
Appendix C. Editor Commands C-5

C.3 Prefix Area Commands
C.3.1 Examples
C.3.1.1 Changing the Current Line
For the prefix area command examples that follow, the panel width has been
reduced somewhat, to include the arrows for illustration.
To make line 6 the current line:
1...+....1....+....2....+....3... ...5....+....6....+....7...
THIS IS LINE 1.
1
THIS IS LINE 2.
2
THIS IS LINE 3.
3
THIS IS LINE 4.
4
THIS IS LINE 5.
5
THIS IS LINE 6. /6

C.3 Prefix Area Commands
C.3.1.2 Adding Lines
To add 3 lines after line 4:
1...+....1....+....2....+....3... ...5....+....6....+....7...
THIS IS LINE 1.
1
THIS IS LINE 2.
2
THIS IS LINE 3.
3
THIS IS LINE 4. a34

C.3 Prefix Area Commands
C.3.1.3 Deleting Lines
To delete 5 lines, starting at line 5:
1...+....1....+....2....+....3... ...5....+....6....+....7...
THIS IS LINE 1.
1
THIS IS LINE 2.
2
THIS IS LINE 3.
3
THIS IS LINE 4.
4
THIS IS LINE 5. 5d5

C.3 Prefix Area Commands
C.3.1.4 Copying Lines
To copy lines 4-6 to an area following line 10:
1...+....1....+....2....+....3... ...5....+....6....+....7...
THIS IS LINE 1.
1
THIS IS LINE 2.
2
THIS IS LINE 3.
3
THIS IS LINE 4. cc4

C.3 Prefix Area Commands
C.3.1.5 Moving Lines
To move the 6 lines starting at line 10 to the area preceding line 1:
1...+....1....+....2....+....3... ...5....+....6....+....7...
THIS IS LINE 1. p1

C.3 Prefix Area Commands
C.3.1.6 Duplicating Lines
To duplicate line 2 twice, and line 10 once:
1...+....1....+....2....+....3... ...5....+....6....+....7...
THIS IS LINE 1.
1
THIS IS LINE 2. 2"2

C.4 Staging Editor Commands
C.4 Staging Editor Commands
C.4.1 Overview
This topic covers the commands used with the Staging Editor and gives
examples of each.
The purposes of these commands are to manipulate staged JCL members and
to check their syntax. The commands in this section are only valid from the
following panels:
■
Display STG Member (SCHD-STGE)
Not every command is valid in each panel. See the detailed descriptions of
each command for details.
The functions of the staging editor commands are summarized following:
To
Expand and display Unicenter CA-Driver procedures
that are embedded in the JCL.
Recall the last version of the JCL as it was prior to a
DEXPAND command. (This is only valid if DEXPAND
was issued without the NOSAVE option.)
Display the current values of the reserved-name variable
parameters that are coded in all Unicenter CA-Driver
procedures embedded in the JCL. This command brings
you into the Dprompt STG Member (SCHD-DPR) panel.
Temporarily save any overtyped reserved-name variable
parameter values on the Dprompt STG Member
(SCHD-DPR) panel for a future DEXPAND command.
This command brings you into the Alter STG Member
panel.
Enter
DEXPAND
RECALL
DPROMPT
DSET
These commands are explained in detail on the following pages.
C-12 Unicenter CA-Scheduler Reference Guide, Part 2

C.4 Staging Editor Commands
C.4.2 DEXPAND
DEXPAND
Expand and display all Unicenter CA-Driver procedures
embedded in the JCL.
C.4.2.1 Option
C.4.2.2 Usage Notes
NOSAVE
Use the NOSAVE option after the DEXPAND command to erase the version of
the JCL that is currently displayed. (The DEXPAND without the NOSAVE
option saves the current version before expansion so that it can be recalled
with the RECALL command.) However, the original copy of the JCL in the
staging library is not affected. Only the copy in the editor's working storage is
erased. If you use this option, a subsequent RECALL command will NOT
recall the version of the JCL that is currently displayed. (To obtain the original
copy after issuing DEXPAND with the NOSAVE option, enter QUIT in the
editor and reselect that member.)
Use the DEXPAND command to expand Unicenter CA-Driver procedures
embedded in a JCL member. The DRIVER installation option must be set to
YES. When the command is processed, the JCL member is scanned for
embedded Unicenter CA-Driver procedure calls. Those procedures are then
expanded and displayed on the panel in place of the procedure call. JCL
statements other than Unicenter CA-Driver procedure calls remain unchanged.
All Unicenter CA-Driver procedures embedded in the member are expanded
including nested procedures. All variable parameter substitutions are resolved
including reserved-name variable parameters.
The expansion occurs on a copy of the member residing in the editor's
working storage (NOT the member in the staging library), so that any changes
that were made before the DEXPAND command will be included. The
previous version of the member prior to expansion is also saved in the editor's
storage and can be recalled again using the RECALL command (explained
later) unless you use the NOSAVE option. However, the actual member in the
staging library is not altered until a FILE or SAVE command is entered in the
Alter STG Member (SCHD-STGE) or the Dprompt STG Member (SCHD-DPR)
panel. If you enter FILE or SAVE, the expanded member is saved in the
staging library replacing the former version. A QUIT command after the
DEXPAND command leaves the member in the staging library unchanged.
The expanded member can be changed using the standard editor commands
and expanded again using the DEXPAND command. However, a second
DEXPAND command will erase the version of the member that was saved in
editor storage by the last DEXPAND command (without the NOSAVE option)
unless the NOSAVE option is used after the DEXPAND command. If the
Appendix C. Editor Commands C-13

C.4 Staging Editor Commands
C.4.2.3 Example
NOSAVE option is used, the currently displayed copy of the member in the
editor's storage is NOT saved.
The following panel shows a member containing an unexpanded Unicenter
CA-Driver procedure call.
SCHD-STGE ALTER STG MEMBER J=DRV111 JN=1 S=DRV11 CA-SCHEDULER
===>
RANGE=1-72
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
$$ JOB JNM=DRV111,DISP=D,CLASS=A, X 1
$$ PDEST=(,SETUP),LDEST=(,SETUP)
2
CARCTL OFF
3
SCSTART S=DRV11 JNO=1 J=DRV111 4
// PROC DRV111, 5
+ NUMBER=(FISRT,SECOND) 6
SCEND S=DRV11 7
$$ EOJ
8
9
1
11
12
13
14
15
16
17
18
19
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
When a DEXPAND command is issued, the expanded procedure replaces the
procedure call:
SCHD-STGE ALTER STG MEMBER J=DRV111 JN=1 S=DRV11 CA-SCHEDULER
===>
CACO314I COMMAND COMPLETED
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
$$ JOB JNM=DRV111,DISP=D,CLASS=A, X 1
$$ PDEST=(,SETUP),LDEST=(,SETUP)
2
CARCTL OFF
3
SCSTART S=DRV11 JNO=1 J=DRV111 4
CACR37I ........... BEGIN PROC ==> DRV111 EXPANSION DRV1
// JOB DRV111 DRV1
DRV1
DISPLAY OF CA-SCHEDULER RESERVED VARIABLES DRV1
DRV1
C_AUTDT (AUTOSCAN DATE).............==> 3251 DRV1
C_AUTIM (AUTOSCAN TIME).............==> 854 DRV1
C_JNAME (JOB NAME)..................==> DRV111 DRV1
C_SNAME (SCHEDULE NAME).............==> DRV11 DRV1
C_JNO (JOB JNO)...................==> 1 DRV1
C_SELRC (SELECTION REASON)..........==> 1 DRV1
C_DTAB (DATE TABLE NAME)...........==> DATETAB DRV1
C_JOBDT (JOBDATE)...................==> 3251 DRV1
C_CAL (CALENDAR)..................==> DRV1
C_SYSID (CONTOLLING SYSID)..........==> 1 DRV1
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
C-14 Unicenter CA-Scheduler Reference Guide, Part 2

C.4 Staging Editor Commands
SCHD-STGE ALTER STG MEMBER J=DRV111 JN=1 S=DRV11 CA-SCHEDULER
===>
RANGE=1-72
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
C_CMD (COMMAND)...................==> COMPLETE DRV1
C_RUNCD (RUN COMMAND DATE)..........==> DRV1
C_ABCC (ABEND CODE).................==> X'1' DRV1
C_ABCT (ABEND COUNT)................==> DRV1
C_ABSTP (ABEND STEP)................==> DRV1
C_SPWR# (PREV POWER JOB#)...........==> 7 DRV1
DRV1
DISPLAY OF CA-DRIVER EXPANSION SYSTEM VARIABLES DRV1
DRV1
C_DATE (GREGORIAN DATE)............==> 9/8/3 DRV1
C_JDATE (JULIAN DATE)...............==> 3251 DRV1
C_TIME (TIME OF THE DAY)......... ==> 12328 DRV1
C_MONTH (MONTH OF THE YEAR).........==> SEPTEMBER DRV1
C_DAY (DAY OF THE WEEK)...........==> FRIDAY DRV1
C_CPUID (CPU NUMBER)................==> 3212 DRV1
C_DYCPU (DYNAM CPU ID)..............==> A DRV1
DRV1
THIS IS THE FISRT TIME. DRV1
// TLBL F111I,'DRV111' CARMSG=I DRV1
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
SCHD-STGE ALTER STG MEMBER J=DRV111 JN=1 S=DRV11 CA-SCHEDULER
===>
RANGE=1-72
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
// TLBL F111O,'DRV111' CARMSG=O(3) DRV1
// DLBL DUMMY,'DRV111.FILE',,SD DRV1
// EXTENT ,POOL1,,,1,1 DRV1
// EXEC DUMMYSD DRV1
/ DRV1
'THIS IS THE SECOND TIME.' DRV1
// TLBL F111I,'DRV111' CARMSG=I DRV1
// TLBL F111O,'DRV111' CARMSG=O(3) DRV1
// DLBL DUMMY,'DRV111.FILE',,SD DRV1
// EXTENT ,POOL1,,,1,2 DRV1
// EXEC DUMMYSD DRV1
/ DRV1
/&
DRV1
/ CACR371I ........... END PROC ==> DRV111 EXPANSION DRV1
SCEND S=DRV11 53
$$ EOJ
54
55
56
57
....+....1....+....2....+....3....+....4....+....5....+....6....+....7..
If you now entered RECALL, the original member in its unexpanded form
would be displayed again.
Appendix C. Editor Commands C-15

C.4 Staging Editor Commands
C.4.3 DPROMPT
DPROMPT
Display current values for reserved-name variable parameters
coded in all Unicenter CA-Driver procedures embedded in the
JCL.
C.4.3.1 Usage Notes
C.4.3.2 Example
Use the DPROMPT command to display the current values for the
reserved-name variable parameters coded in all Unicenter CA-Driver
procedures embedded in the JCL. The DRIVER installation option must be set
to YES. When the command is processed, the JCL member is scanned for
embedded Unicenter CA-Driver procedure calls. All Unicenter CA-Driver
procedures embedded in the member are scanned including nested procedures.
These procedures are then scanned for reserved-name variable parameters
coded in the procedures. The parameters are resolved to their current values.
The parameters are then displayed next to their current values on the Dprompt
STG Member (SCHD-DPR) panel.
The QUIT command within the Dprompt STG Member panel leaves the
reserved-name variable parameters unchanged and returns you to the previous
panel. If you issued DPROMPT from the Alter STG Member panel (as
opposed to the Display STG Member panel), reserved-name variable
parameters values can be changed by overtyping new values and then entering
DSET.
The following panel shows a member containing a Unicenter CA-Driver
procedure call.
C-16 Unicenter CA-Scheduler Reference Guide, Part 2

C.4 Staging Editor Commands
SCHD-STGE ALTER STG MEMBER J=DRV111 JN=1 S=DRV11 CA-SCHEDULER
===>
RANGE=1-72
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
$$ JOB JNM=DRV111,DISP=D,CLASS=A, X 1
$$ PDEST=(,SETUP),LDEST=(,SETUP)
2
CARCTL OFF
3
SCSTART S=DRV11 JNO=1 J=DRV111 4
// PROC DRV111, 5
+ NUMBER=(FIRST,SECOND,THIRD) 6
SCEND S=DRV11 7
$$ EOJ
8
9
1
11
12
13
14
15
16
17
18
19
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
When a DPROMPT command is issued, the current values for the
reserved-name variable parameters within that procedure are displayed in the
following panel.
SCHD-DPR DPROMPT STG MEMBER J=DRV111 JN=1 S=DRV11 CA-SCHEDULER
===>
PROC VARIABLE CURRENT VALUE SET
|...+....1....+....2....+....3....+....4....+....5....+
DRV111 &C_AUTDT 3251
DRV111 &C_AUTIM 854
DRV111 &C_JNAME DRV111
DRV111 &C_SNAME DRV11
DRV111 &C_JNO 1
DRV111 &C_SELRC 1
DRV111 &C_DTAB DATETAB
DRV111 &C_JOBDT 3251
DRV111 &C_CAL
DRV111 &C_SYSID 1
DRV111 &C_CMD COMPLETE
DRV111 &C_RUNCD
DRV111 &C_ABCC X'1'
DRV111 &C_ABCT
DRV111 &C_ABSTP
DRV111 &C_SPWR# 7
DRV111 &C_DATE 9/8/3
DRV111 &C_JDATE 3251
|...+....1....+....2....+....3....+....4....+....5....+
Appendix C. Editor Commands C-17

C.4 Staging Editor Commands
SCHD-DPR DPROMPT STG MEMBER J=DRV111 JN=1 S=DRV11 CA-SCHEDULER
===>
PROC VARIABLE CURRENT VALUE SET
|...+....1....+....2....+....3....+....4....+....5....+
DRV111 &C_TIME 123234
DRV111 &C_MONTH SEPTEMBER
DRV111 &C_DAY FRIDAY
DRV111 &C_CPUID 3212
DRV111 &C_DYCPU A
END OF VARIABLE LIST
|...+....1....+....2....+....3....+....4....+....5....+
C-18 Unicenter CA-Scheduler Reference Guide, Part 2

C.4 Staging Editor Commands
C.4.4 DSET
DSET
Temporarily save overtyped reserved-name variable parameter
values and return to the Alter STG Member (SCHD-STGE) panel.
C.4.4.1 Usage Notes
The DSET command is only valid from the Dprompt STG Member (SCHD-DPR)
panel.
Use the DSET command from the Dprompt STG Member panel to temporarily save
any overtyped reserved-name variable parameter values for the next DEXPAND
command and return to the Alter STG Member panel. The next DEXPAND command
will use the changed values for those parameters.
Changes to parameters on the Dprompt STG Member panel are only temporary.
However, you may DEXPAND the JCL after the changes and then file the expanded
member. The expanded member will be saved in the staging library with the changed
values resolved for those parameters.
SCHD-DPR DPROMPT STG MEMBER J=DRV111 JN=1 S=DRV11 CA-SCHEDULER
===>
PROC VARIABLE CURRENT VALUE SET
|...+....1....+....2....+....3....+....4....+....5....+
DRV111 &C_AUTDT 3251
DRV111 &C_AUTIM 854
DRV111 &C_JNAME DRV111
DRV111 &C_SNAME DRV11
DRV111 &C_JNO 2
DRV111 &C_SELRC 1
DRV111 &C_DTAB DATETAB
DRV111 &C_JOBDT 3251
DRV111 &C_CAL
DRV111 &C_SYSID 1
DRV111 &C_CMD COMPLETE
DRV111 &C_RUNCD
DRV111 &C_ABCC X'1'
DRV111 &C_ABCT
DRV111 &C_ABSTP
DRV111 &C_SPWR# 7
DRV111 &C_DATE 9/8/3
DRV111 &C_JDATE 3251
|...+....1....+....2....+....3....+....4....+....5....+
Appendix C. Editor Commands C-19

C.4 Staging Editor Commands
SCHD-DPR DPROMPT STG MEMBER J=DRV111 JN=1 S=DRV11 CA-SCHEDULER
===>
PROC VARIABLE CURRENT VALUE SET
|...+....1....+....2....+....3....+....4....+....5....+
DRV111 &C_TIME 123234
DRV111 &C_MONTH SEPTEMBER
DRV111 &C_DAY FRIDAY
DRV111 &C_CPUID 3212
DRV111 &C_DYCPU A
END OF VARIABLE LIST
|...+....1....+....2....+....3....+....4....+....5....+
C.4.5 RECALL
RECALL
Recall the last version of the JCL that was saved by a command without
the NOSAVE option.
C.4.5.1 Usage Notes
C.4.5.2 Example
Use the RECALL command to recall a JCL member that was previously saved using
the DEXPAND command without the NOSAVE option. Only one member is saved by
the DEXPAND command. A RECALL command after multiple DEXPAND
commands recalls only the last member saved by the DEXPAND command.
The panel following shows a member containing a Unicenter CA-Driver procedure that
was expanded with a DEXPAND command.
C-20 Unicenter CA-Scheduler Reference Guide, Part 2

C.4 Staging Editor Commands
SCHD-STGE ALTER STG MEMBER J=DRV111 JN=1 S=DRV11 CA-SCHEDULER
===>
CACO314I COMMAND COMPLETED
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
$$ JOB JNM=DRV111,DISP=D,CLASS=A, X 1
$$ PDEST=(,SETUP),LDEST=(,SETUP)
2
CARCTL OFF
3
SCSTART S=DRV11 JNO=1 J=DRV111 4
CACR37I ........... BEGIN PROC ==> DRV111 EXPANSION DRV1
// JOB DRV111 DRV1
DRV1
DISPLAY OF CA-SCHEDULER RESERVED VARIABLES DRV1
DRV1
C_AUTDT (AUTOSCAN DATE).............==> 3251 DRV1
C_AUTIM (AUTOSCAN TIME).............==> 854 DRV1
C_JNAME (JOB NAME)..................==> DRV111 DRV1
C_SNAME (SCHEDULE NAME).............==> DRV11 DRV1
C_JNO (JOB JNO)...................==> 1 DRV1
C_SELRC (SELECTION REASON)..........==> 1 DRV1
C_DTAB (DATE TABLE NAME)...........==> DATETAB DRV1
C_JOBDT (JOBDATE)...................==> 3251 DRV1
C_CAL (CALENDAR)..................==> DRV1
C_SYSID (CONTOLLING SYSID)..........==> 1 DRV1
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
SCHD-STGE ALTER STG MEMBER J=DRV111 JN=1 S=DRV11 CA-SCHEDULER
===>
RANGE=1-72
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
C_CMD (COMMAND)...................==> COMPLETE DRV1
C_RUNCD (RUN COMMAND DATE)..........==> DRV1
C_ABCC (ABEND CODE).................==> X'1' DRV1
C_ABCT (ABEND COUNT)................==> DRV1
C_ABSTP (ABEND STEP)................==> DRV1
C_SPWR# (PREV POWER JOB#)...........==> 7 DRV1
DRV1
DISPLAY OF CA-DRIVER EXPANSION SYSTEM VARIABLES DRV1
DRV1
C_DATE (GREGORIAN DATE)............==> 9/8/3 DRV1
C_JDATE (JULIAN DATE)...............==> 3251 DRV1
C_TIME (TIME OF THE DAY)......... ==> 12328 DRV1
C_MONTH (MONTH OF THE YEAR).........==> SEPTEMBER DRV1
C_DAY (DAY OF THE WEEK)...........==> FRIDAY DRV1
C_CPUID (CPU NUMBER)................==> 3212 DRV1
C_DYCPU (DYNAM CPU ID)..............==> A DRV1
DRV1
THIS IS THE FISRT TIME. DRV1
// TLBL F111I,'DRV111' CARMSG=I DRV1
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
Appendix C. Editor Commands C-21

C.4 Staging Editor Commands
SCHD-STGE ALTER STG MEMBER J=DRV111 JN=1 S=DRV11 CA-SCHEDULER
===>
RANGE=1-72
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
// TLBL F111O,'DRV111' CARMSG=O(3) DRV1
// DLBL DUMMY,'DRV111.FILE',,SD DRV1
// EXTENT ,POOL1,,,1,1 DRV1
// EXEC DUMMYSD DRV1
/ DRV1
'THIS IS THE SECOND TIME.' DRV1
// TLBL F111I,'DRV111' CARMSG=I DRV1
// TLBL F111O,'DRV111' CARMSG=O(3) DRV1
// DLBL DUMMY,'DRV111.FILE',,SD DRV1
// EXTENT ,POOL1,,,1,2 DRV1
// EXEC DUMMYSD DRV1
/ DRV1
/&
DRV1
/ CACR371I ........... END PROC ==> DRV111 EXPANSION DRV1
SCEND S=DRV11 53
$$ EOJ
54
55
56
57
....+....1....+....2....+....3....+....4....+....5....+....6....+....7..
When a RECALL command is issued, the original member is displayed in its
unexpanded form.
SCHD-STGE ALTER STG MEMBER J=DRV111 JN=1 S=DRV11 CA-SCHEDULER
===>
RANGE=1-72
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
$$ JOB JNM=DRV111,DISP=D,CLASS=A, X 1
$$ PDEST=(,SETUP),LDEST=(,SETUP)
2
CARCTL OFF
3
SCSTART S=DRV11 JNO=1 J=DRV111 4
// PROC DRV111, 5
+ NUMBER=(FISRT,SECOND) 6
SCEND S=DRV11 7
$$ EOJ
8
9
1
11
12
13
14
15
16
17
18
19
1...+....1....+....2....+....3....+....4....+....5....+....6....+....7..
C-22 Unicenter CA-Scheduler Reference Guide, Part 2

C.5 PF Key Settings
C.5 PF Key Settings
The default PF key settings for the Unicenter CA-Scheduler online editor are as
follows:
PF Keys
Command
Function
PF1/PF13 HELP Invoke the online Help facility.
PF2/PF14
Unassigned
PF3/PF15 Quit Leave the edit panel without saving
changes.
PF4/PF16 Down Move the panel down one line.
PF5/PF17 Up Move the panel up one line.
PF6/PF18
Unassigned
PF7/PF19 Backward Scroll back one panel.
PF8/PF20 Forward Scroll forward one panel.
PF9/PF21
Unassigned
PF10/PF22 Top Go to the top of the file.
PF11/PF23 BOttom Go to the end of the file.
PF12/PF24
Unassigned
If your PF keys are not set to these defaults, see your systems programmer.
Appendix C. Editor Commands C-23

Appendix D. Advantage CA-Earl Reports
This appendix describes the following reports pertaining to Advantage CA-Earl:
■
■
■
■
■
All Reports
Database Reports
History File Reports
Tracking File Reports
Documentation or Staging Library Reports.
Appendix D. Advantage CA-Earl Reports D-1

D.1 All Reports
D.1 All Reports
All Advantage CA-Earl source members are in Unicenter CA-Scheduler library with a
type of .0.
D.1.1 CAJEPM Source Member
The CAJEPM source member sets the parameter list that allows Unicenter
CA-Scheduler to communicate with Advantage CA-Earl. It must be specified on a
COPY statement.
DEF PRMEARL = CAJCACC2 1-4 X
DEF PRMMSG = CAJCACC2 5-24 X
DEF PRMFUNC = CAJCACC2 25-28 X
DEF PRMRTCD = CAJCACC2 29-32 X
DEF PRMID = CAJCACC2 33-36 X
DEF PRMBUFL = CAJCACC2 37-4 X
DEF PRMBUFF = CAJCACC2 41-44 X
DEF PRMKEYL = CAJCACC2 45-46 B
DEF PRMKEY = CAJCACC2 47-66 X
DEF PRMNME = CAJCACC2 47-54 X
DEF PRMNUM = CAJCACC2 55-56 X
DEF PRMSTA = CAJCACC2 57-58 X
DEF PRMSCH = CAJCACC2 59-66 X
DEF PRMWRK = CAJCACC2 67-8 X
D.1.2 CAISTMD Source Member
The CAISTMD source member converts dates from American to European format.
Specify it on a COPY statement to print dates as DDMMYY instead of MMDDYY.
D-2 Unicenter CA-Scheduler Reference Guide, Part 2

D.1 All Reports
CAI_DATE_CONVERSION: PROC
!
! CAI EARL JULIAN-GREGORIAN DATE CONVERSION ROUTINE
!
! COPY MEMBER : CAISTMD
! CONTAINS : ALL EARL STATEMENTS OTHER THAN DEFINE STATEMENTS
! FOR THE DATE CONVERSION ROUTINE
!
SET CAI_OUTDATE = ' '
!
IF CAI_DAYS = THEN GOTO CAI_NODATE
ENDIF
!
SET CAI_R1 = 1
SET CAI_NDAYS = CAI_DAYS
!
SET CAI_DTAB (/2/) = 28
SET C_YEAR (3.) = (CAI_YEAR / 4)
SET C_YEAR = C_YEAR 4
IF C_YEAR = CAI_YEAR THEN
SET CAI_DTAB (/2/) = 29
ENDIF
!
SET CAI_OUTDATE = '//'
!
CAI_DATE_LOOP:
IF CAI_NDAYS < THEN GOTO CAI_LOOP_END
ENDIF
IF CAI_R1 > 12 THEN GOTO CAI_LOOP_END
ENDIF
SET CAI_NDAYS = (CAI_NDAYS - CAI_DTAB(/CAI_R1/))
SET CAI_MNTH = CAI_R1
SET CAI_R1 = CAI_R1 + 1
GOTO CAI_DATE_LOOP
CAI_LOOP_END:
!
SET CAI_OUTDD = (CAI_NDAYS + CAI_DTAB(/CAI_MNTH/))
SET CAI_OUTMM = CAI_MNTH
SET CAI_OUTYY = CAI_YEAR
!
CAI_NODATE:
!
ENDPROC
!
Appendix D. Advantage CA-Earl Reports D-3

D.2 Database Reports
D.2 Database Reports
D.2.1 CAJECRI Source Member
Following are examples of CA-Earl database reports.
The CAJECRI source member allows you to print criteria from the Unicenter
CA-Scheduler database.
! CRITERIA RECORD LAYOUT
! COPY THIS BOOK IN ANY EARL REPORT THAT USES THE CRITERIA RECORD
! FROM THE JOB MASTER DATABASE
! CHANGE THE NEXT LINE IF YOU INCREASE NO OF CRILINXX
DEF RECORDA 1-248 X
DEF CRIRDW
5-6 B
DEF CRIJNAME
13-2 X 'JOB' 'NAME'
DEF CRIJNO
21-22 X 'JOB' 'NUMBER'
DEF CRISTATION 23-24 X 'STATION'
DEF CRISCHNAME 25-32 X 'SCHEDULE' 'NAME'
DEF CRIDATETAB 33-4 X 'DATETABLE'
DEF CRICAL
41-48 X 'CALENDAR'
DEF CRILINE1 35-16 X 'CRITERIA'
DEF CRILINE2 17-178 X
DEF CRILINE3 179-25 X
DEF CRILINE4 251-322 X
DEF CRILINE5 323-394 X
DEF CRILINE6 33-466 X
DEF CRILINE7 467-538 X
DEF CRILINE8 539-61 X
DEF CRILINE9 611-682 X
DEF CRILINE1 683-754 X
DEF CRILINE11 755-826 X
DEF CRILINE12 827-898 X
DEF CRILINE13 899-97 X
DEF CRILINE14 971-142 X
DEF CRILINE15 143-1114 X
DEF CRILINE16 1115-1186 X
DEF CRILINE17 1187-1258 X
DEF CRILINE18 1259-133 X
DEF CRILINE19 1331-142 X
DEF CRILINE2 143-1474 X
D-4 Unicenter CA-Scheduler Reference Guide, Part 2

D.2 Database Reports
D.2.2 CAJEGLBL Source Member
The CAJEGLBL Source Member is a sample program to perform global changes to
the Unicenter CA-Scheduler database. The program produces the command:
! This sample program produces the command:
!
!
! ALTER JBR NAME=JNAME,
! SCHEDULE=SNAME,
! JNO=NN,
! STATION=NN,
! CLASS=A
!
!
! that can be used as input for CAJUTIL to update
! Unicenter CA-Scheduler Master Database.
!
!
!
! Set Advantage CA-Earl Options
!
OPTION LIST OFF
! SUPPRESS COMPILATION LISTING
OPTION PRINTER=8
! SET LINE WIDTH TO 8
OPTION PAGE=1
! SUPPRESS PAGE BREAKE
OPTION EXCLUDE
! SUPPRESS PAGE HEADING
OPTION SORT=SRAM
!
! File Definition for accessing Unicenter CA-Scheduler Master Database
!
CAIJMST:FILE CAJCACC2 RECORD = 248
!
! Mapping Unicenter CA-Scheduler Job Record
!
COPY CAJEJM
!
! Unicenter CA-Scheduler/Advantage CA-Earl Communication Parmlist
!
COPY CAJEPM
!
! LINE to separate commands with ''
!
DEF LINE (X 8) = ' '
!
! LINE1 will hold 'ALTER JBR NAME=JNAME,'
!
DEF LINE1 (X 8) = ' '
DEF L1ALTER = LINE1 1-5 X
DEF L1JBR = LINE1 8-1 X
DEF L1NAMEC = LINE1 13-17 X
DEF L1NAME = LINE1 18-26 X
!
! JNAME Field is redefined as an array to place ','
! at the first blank
Appendix D. Advantage CA-Earl Reports D-5

D.2 Database Reports
!
DEF L1NAMEA ARRAY 9 = L1NAME 1 X ! DEFINE 1-BYTE ARRAY
DEF L1REST = LINE1 27-8 X
!
! LINE2 will hold ' SCHEDULE=SNAME,'
!
DEF LINE2 (X 8) = ' '
DEF L2SCDC = LINE2 13-21 X
DEF L2SCD = LINE2 22-3 X
!
! SNAME Field is redefined as an array to place ','
! at the first blank
!
DEF L2SCDA ARRAY 9 = L2SCD 1 X ! DEFINE 1-BYTE ARRAY
DEF L2REST = LINE2 31-8 X
!
! LINE3 WILL HOLD ' JNO=NN,'
!
DEF LINE3 (X 8) = ' '
DEF L3JNOC = LINE3 13-16 X
DEF L3JNO = LINE3 17-18 X
DEF L3JCOMMA = LINE3 19 X
DEF L3REST = LINE3 2-8 X
!
! LINE4 WILL HOLD ' STATION=NN,'
!
DEF LINE4 (X 8) = ' '
DEF L4STNC = LINE4 13-2 X
DEF L4STN = LINE4 21-22 X
DEF L4TCOMMA = LINE4 23 X
DEF L4REST = LINE4 24-8 X
!
! LINE5 WILL HOLD ' SYSID=NULL'
!
DEF LINE5 (X 8) = ' '
DEF L5JCLASSC = LINE5 13-18 X
DEF L5JCLASS = LINE5 19-19 X
DEF L5REST = LINE5 2-8 X
!
! Set Parm list for sequential access to job records
!
COPY CAJESETM
!
! Read a record and exit at end of file
!
GET CAIJMST
GOTO EOJ CAIJMST = 'E' OR CAIJMST = 'N'
!
D-6 Unicenter CA-Scheduler Reference Guide, Part 2

D.2 Database Reports
! Set LINE
!
SET LINE = ''
!
! Set LINE1
!
SET L1ALTER = 'ALTER'
SET L1JBR = 'JBR'
SET L1NAMEC = 'NAME='
SET L1NAME = JOBNAME
PERFORM SETJCOMMA
! PLACE ',' AFTER JOBNAME
!
! Set LINE2
!
SET L2SCDC = 'SCHEDULE='
SET L2SCD = JOBSCHNAME
PERFORM SETSCOMMA
! PLACE ',' AFTER SCDNAME
!
! Set LINE3
!
SET L3JNOC = 'JNO='
SET L3JNO = JOBNUMBER
SET L3JCOMMA = ','
!
! Set LINE4
!
SET L4STNC = 'STATION='
SET L4STN = JOBSTATION
SET L4TCOMMA = ','
!
! Change here the field and its new value.
!
SET L5JCLASSC = 'CLASS='
SET L5JCLASS = 'A'
!
! Proc to place ',' at the first blank in JOB NAME
!
SETJCOMMA: PROC
SET SUB = 1
! INITIALIZE COUNTER
AAA: GOTO JOBCOMMA L1NAMEA(/SUB/) = ' ' ! TEST FOR 1ST BLANK
SET SUB = SUB + 1
! BUMP COUNTER
GOTO AAA
! CHECK NEXT CHARACTER
JOBCOMMA: SET L1NAMEA(/SUB/) = ','
! CHANGE BLANK TO COMMA
ENDPROC
Appendix D. Advantage CA-Earl Reports D-7

D.2 Database Reports
!
! Proc to place ',' at the first blank in SCHEDULE NAME
!
SETSCOMMA: PROC
SET SUB = 1
! INITIALIZE COUNTER
BBB: GOTO SCDCOMMA L2SCDA(/SUB/) = ' '
! TEST FOR 1ST BLANK
SET SUB = SUB + 1
! BUMP COUNTER
GOTO BBB
! CHECK NEXT CHARACTER
SCDCOMMA: SET L2SCDA(/SUB/) = ','
! CHANGE BLANK TO COMMA
ENDPROC
!
! Advantage CA-Earl Report Section
!
REPORT
!
PRINT LINE
PRINT LINE1
PRINT LINE2
PRINT LINE3
PRINT LINE4
PRINT LINE5
!
! End of Advantage CA-Earl Program
!
END
D.2.3 CAJESETM Source Member
D.2.3.1 Example 1
D.2.3.2 Example 2
The CAJESETM source member sets the record ID to either JOB for job records or
SCH for schedule records, and initializes the search key for either a unique, generic, or
sequential request.
SET PRMFUNC = 'GETG' Generic request for all jobs
SET PRMID = 'JOB ' with job names beginning with
SET PRMNME = 'AB ' characters 'AB'
SET PRMNUM = ' '
SET PRMSTA = ' '
SET PRMSCH = ' '
SET PRMKEYL = 2
SET PRMFUNC = 'GETU' Unique request for a job
SET PRMID = 'JOB ' with these key values:
SET PRMNME = 'ABC ' jobname = ABC
SET PRMNUM = '1' jobnumber = 1
SET PRMSTA = '4' station = 4
SET PRMSCH = 'SCD1 ' schedule = SCD1
D-8 Unicenter CA-Scheduler Reference Guide, Part 2

D.2 Database Reports
D.2.4 Job Information from Database
Advantage CA-Earl reports can include job information from the Unicenter
CA-Scheduler database. To include this information on a report, copy the CAJEJM
source member and list the fieldnames you want on the PRINT statement. See the
chapter "Reports" for samples.
Information Fieldname Field Format Heading On On Sample
Length Report Reports
Record Name
job name JOBNAME 8 NAME yes
job number JOBNUMBER 2 NUMBER yes
schedule name JOBSCHNAME 8 SCHEDULE NAME yes
station ID JOBSTATION 2 STATION yes
Defined Records
job base JOBBASEREC 1 BASE RECORD
job criteria JOBCRIREC 1 CRITERIA RECORD
job information JOBINFOREC 1 INFO RECORD
job message JOBMSGREC 1 MESSAGE RECORD
job reason code JOBREASON 1 REASON CODE
job resource JOBRESREC 1 RESOURCE RECORD
Base Record
ABEND values
alternate sname JOBABNAME 8 ABEND NAME
CONTINUE JOBCONTABEN 1 CONTINUE ABEND
AUTO START JOBAUTOUPD 1 AUTO UPDATE
BACKLOG JOBBACKLOG 1 BACKLOG
CPU JOB: NO JOBEXTERNAL 1 EXTERNAL
DISPLAY
KEY JOBDISPKEY 8 DISPLAY KEY
TIME JOBDISPTIME 9 ZZZ.ZZ.ZZ DISPLAY-TIME yes
FAIL CODE JOBFAILCODE 5 FAIL CODE
INTERRUPT JOBINTER 1 INTERRUPTABLE
Appendix D. Advantage CA-Earl Reports D-9

D.2 Database Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
POWER
PRIORITY JOBPOWPRTY 2 POWER PRIORITY
CLASS JOBCLASS 1 CLASS
LIBRARY TYPE
DRIVER JOBDRPARM 1 DRIVER PARM
other JOBLIBTYPE 8 LIBTYPE
MEMBER
NAME JOBMEMBER 8 MEMBER
SUBID JOBMEMBERSUB 8 SUB MEMBER
PASSWORD JOBMEMBERPSWD 8 MEMBER PSWD
MEMO JOBMEMO 6 MEMO
NODE ID JOBNODEID 8 NODE ID
PRIORITY JOBPRIORITY 2 PRIORITY
RECOVERABLE JOBRESTART 1 RESTARTABLE
RUN ON SYSID JOBCPUID 4 CPU ID
STAGING JOBSTAGE 1 STAGING
TIMES
EARLIEST START JOBERLYTIME 9 ZZZ.ZZ.ZZ EARLY-TIME yes
MUST START BY JOBMUSTTIME 9 ZZZ.ZZ.ZZ MUST-TIME yes
COMPLETION JOBDEADTIME 9 ZZZ.ZZ.ZZ DEAD-TIME yes
MAX EXECUTION JOBMAXTIME 9 ZZZ.ZZ.ZZ MAXIMUM-TIME yes
AVERAGE JOBAELAPTME 9 ZZZ.ZZ.ZZ AVG-ELAP-TME
simulated start JOBSIMSTME 9 ZZZ.ZZ.ZZ SIM-ST-TIME
USE SIMTIME JOBSIMSTART 1 SIMULATE START
Info Record
COMMENT JOBCOMMENT 3 COMMENT
DELIVERABLES JOBDSPEC1 8 DELIVERY SPEC1
JOBDSPEC2 8 DELIVERY SPEC2
JOBDSPEC3 8 DELIVERY SPEC3
JOBDSPEC4 8 DELIVERY SPEC4
JOBDSPEC5 8 DELIVERY SPEC5
JOBDSPEC6 8 DELIVERY SPEC6
JOBDSPEC7 8 DELIVERY SPEC7
JOBDSPEC8 8 DELIVERY SPEC8
DESCRIPTION JOBMDESC 4 MEMO DESC
D-10 Unicenter CA-Scheduler Reference Guide, Part 2

D.2 Database Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
DESTINATIONS JOBDEST1 8 DESTINATION1
JOBDEST2 8 DESTINATION2
JOBDEST3 8 DESTINATION3
JOBDEST4 8 DESTINATION4
JOBDEST5 8 DESTINATION5
JOBDEST6 8 DESTINATION6
JOBDEST7 8 DESTINATION7
JOBDEST8 8 DESTINATION8
EXITPARM JOBUFIELD 16 USER FIELD
FORM JOBFNUM 8 FORM NUMBER
NOTIFY JOBPNOTIFY 12 PERSON NOTIFY
RESPONSIBILITY JOBPRESP 12 PERSON RESPONSIBLE
ROUTE STATIONS
station1 JOBRSTAT1 2 ROUT STAT1
station2 JOBRSTAT2 2 ROUT STAT2
station3 JOBRSTAT3 2 ROUT STAT3
station4 JOBRSTAT4 2 ROUT STAT4
station5 JOBRSTAT5 2 ROUT STAT5
station6 JOBRSTAT6 2 ROUT STAT6
station7 JOBRSTAT7 2 ROUT STAT7
station8 JOBRSTAT8 2 ROUT STAT8
station9 JOBRSTAT9 2 ROUT STAT9
station1 JOBRSTAT1 2 ROUT STAT1
station11 JOBRSTAT11 2 ROUT STAT11
station12 JOBRSTAT12 2 ROUT STAT12
number listed JOBRSTAT 2 NUMBER ROUTING-ST
QUANTITY JOBQUANTITY 8 QUANTITY
SPECIFICATION JOBSPNUM 8 SPEC NUMBER
VERIFY JOBNVERIFY 1 NEEDS VERIFY
Message Record
SEND ABEND
MESSAGES
to user1 JOBAMSGU1 8 AMSG USERID1
to user2 JOBAMSGU2 8 AMSG USERID2
to user3 JOBAMSGU3 8 AMSG USERID3
to user4 JOBAMSGU4 8 AMSG USERID4
number of users JOBAMSGUS 2 AMSG USERIDS
Appendix D. Advantage CA-Earl Reports D-11

D.2 Database Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
SEND ALL MESSAGES
to user1 JOBMSGU1 8 MSG USERID1
to user2 JOBMSGU2 8 MSG USERID2
to user3 JOBMSGU3 8 MSG USERID3
to user4 JOBMSGU4 8 MSG USERID4
number of users JOBMSGUS 2 MSG USERIDS
SEND END MESSAGES
to user1 JOBEMSGU1 8 EMSG USERID1
to user2 JOBEMSGU2 8 EMSG USERID2
to user3 JOBEMSGU3 8 EMSG USERID3
to user4 JOBEMSGU4 8 EMSG USERID4
number of users JOBEMSGUS 2 EMSG USERIDS
SEND FAIL
MESSAGES
to user1 JOBFMSGU1 8 FMSG USERID1
to user2 JOBFMSGU2 8 FMSG USERID2
to user3 JOBFMSGU3 8 FMSG USERID3
to user4 JOBFMSGU4 8 FMSG USERID4
number of users JOBFMSGUS 2 FMSG USERIDS
SEND INTERRUPT
MESSAGES
to user1 JOBIMSGU1 8 IMSG USERID1
to user2 JOBIMSGU2 8 IMSG USERID2
to user3 JOBIMSGU3 8 IMSG USERID3
to user4 JOBIMSGU4 8 IMSG USERID4
number of users JOBIMSGUS 2 IMSG USERIDS
SEND LATE
MESSAGES
to user1 JOBLMSGU1 8 LMSG USERID1
to user2 JOBLMSGU2 8 LMSG USERID2
to user3 JOBLMSGU3 8 LMSG USERID3
to user4 JOBLMSGU4 8 LMSG USERID4
number of users JOBLMSGUS 2 LMSG USERIDS
SEND PURGE
MESSAGES
to user1 JOBPMSGU1 8 PMSG USERID1
to user2 JOBPMSGU2 8 PMSG USERID2
to user3 JOBPMSGU3 8 PMSG USERID3
to user4 JOBPMSGU4 8 PMSG USERID4
number of users JOBPMSGUS 2 PMSG USERIDS
D-12 Unicenter CA-Scheduler Reference Guide, Part 2

D.2 Database Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
SEND START
MESSAGES
to user1 JOBSMSGU1 8 SMSG USERID1
to user2 JOBSMSGU2 8 SMSG USERID2
to user3 JOBSMSGU3 8 SMSG USERID3
to user4 JOBSMSGU4 8 SMSG USERID4
number of users JOBSMSGUS 2 SMSG USERIDS
Reason Code Rec
AVERAGE TIME LIST
reason 1 JOBELAPTM1 9 ZZZ.ZZ.ZZ ELAP-TIME1
reason 2 JOBELAPTM2 9 ZZZ.ZZ.ZZ ELAP-TIME2
reason 3 JOBELAPTM3 9 ZZZ.ZZ.ZZ ELAP-TIME3
reason 4 JOBELAPTM4 9 ZZZ.ZZ.ZZ ELAP-TIME4
reason 5 JOBELAPTM5 9 ZZZ.ZZ.ZZ ELAP-TIME5
reason 6 JOBELAPTM6 9 ZZZ.ZZ.ZZ ELAP-TIME6
reason 7 JOBELAPTM7 9 ZZZ.ZZ.ZZ ELAP-TIME7
reason 8 JOBELAPTM8 9 ZZZ.ZZ.ZZ ELAP-TIME8
reason 9 JOBELAPTM9 9 ZZZ.ZZ.ZZ ELAP-TIME9
reason 1 JOBELAPTM1 9 ZZZ.ZZ.ZZ ELAP-TIME1
reason 11 JOBELAPTM11 9 ZZZ.ZZ.ZZ ELAP-TIME11
reason 12 JOBELAPTM12 9 ZZZ.ZZ.ZZ ELAP-TIME12
reason 13 JOBELAPTM13 9 ZZZ.ZZ.ZZ ELAP-TIME13
reason 14 JOBELAPTM14 9 ZZZ.ZZ.ZZ ELAP-TIME14
reason 15 JOBELAPTM15 9 ZZZ.ZZ.ZZ ELAP-TIME15
reason 16 JOBELAPTM16 9 ZZZ.ZZ.ZZ ELAP-TIME16
DEADLINE LIST
reason 1 JOBDTME1 9 ZZZ.ZZ.ZZ DEAD-TIME1
reason 2 JOBDTME2 9 ZZZ.ZZ.ZZ DEAD-TIME2
reason 3 JOBDTME3 9 ZZZ.ZZ.ZZ DEAD-TIME3
reason 4 JOBDTME4 9 ZZZ.ZZ.ZZ DEAD-TIME4
reason 5 JOBDTME5 9 ZZZ.ZZ.ZZ DEAD-TIME5
reason 6 JOBDTME6 9 ZZZ.ZZ.ZZ DEAD-TIME6
reason 7 JOBDTME7 9 ZZZ.ZZ.ZZ DEAD-TIME7
reason 8 JOBDTME8 9 ZZZ.ZZ.ZZ DEAD-TIME8
reason 9 JOBDTME9 9 ZZZ.ZZ.ZZ DEAD-TIME9
reason 1 JOBDTME1 9 ZZZ.ZZ.ZZ DEAD-TIME1
reason 11 JOBDTME11 9 ZZZ.ZZ.ZZ DEAD-TIME11
reason 12 JOBDTME12 9 ZZZ.ZZ.ZZ DEAD-TIME12
reason 13 JOBDTME13 9 ZZZ.ZZ.ZZ DEAD-TIME13
reason 14 JOBDTME14 9 ZZZ.ZZ.ZZ DEAD-TIME14
reason 15 JOBDTME15 9 ZZZ.ZZ.ZZ DEAD-TIME15
reason 16 JOBDTME16 9 ZZZ.ZZ.ZZ DEAD-TIME16
Appendix D. Advantage CA-Earl Reports D-13

D.2 Database Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
EARLY TIME LIST
reason 1 JOBETIME1 9 ZZZ.ZZ.ZZ EARLY-TIME1
reason 2 JOBETIME2 9 ZZZ.ZZ.ZZ EARLY-TIME2
reason 3 JOBETIME3 9 ZZZ.ZZ.ZZ EARLY-TIME3
reason 4 JOBETIME4 9 ZZZ.ZZ.ZZ EARLY-TIME4
reason 5 JOBETIME5 9 ZZZ.ZZ.ZZ EARLY-TIME5
reason 6 JOBETIME6 9 ZZZ.ZZ.ZZ EARLY-TIME6
reason 7 JOBETIME7 9 ZZZ.ZZ.ZZ EARLY-TIME7
reason 8 JOBETIME8 9 ZZZ.ZZ.ZZ EARLY-TIME8
reason 9 JOBETIME9 9 ZZZ.ZZ.ZZ EARLY-TIME9
reason 1 JOBETIME1 9 ZZZ.ZZ.ZZ EARLY-TIME1
reason 11 JOBETIME11 9 ZZZ.ZZ.ZZ EARLY-TIME11
reason 12 JOBETIME12 9 ZZZ.ZZ.ZZ EARLY-TIME12
reason 13 JOBETIME13 9 ZZZ.ZZ.ZZ EARLY-TIME13
reason 14 JOBETIME14 9 ZZZ.ZZ.ZZ EARLY-TIME14
reason 15 JOBETIME15 9 ZZZ.ZZ.ZZ EARLY-TIME15
reason 16 JOBETIME16 9 ZZZ.ZZ.ZZ EARLY-TIME16
MAXIMUM TIME LIST
reason 1 JOBMXTIME1 9 ZZZ.ZZ.ZZ MAX-TIME1
reason 2 JOBMXTIME2 9 ZZZ.ZZ.ZZ MAX-TIME2
reason 3 JOBMXTIME3 9 ZZZ.ZZ.ZZ MAX-TIME3
reason 4 JOBMXTIME4 9 ZZZ.ZZ.ZZ MAX-TIME4
reason 5 JOBMXTIME5 9 ZZZ.ZZ.ZZ MAX-TIME5
reason 6 JOBMXTIME6 9 ZZZ.ZZ.ZZ MAX-TIME6
reason 7 JOBMXTIME7 9 ZZZ.ZZ.ZZ MAX-TIME7
reason 8 JOBMXTIME8 9 ZZZ.ZZ.ZZ MAX-TIME8
reason 9 JOBMXTIME9 9 ZZZ.ZZ.ZZ MAX-TIME9
reason 1 JOBMXTIME1 9 ZZZ.ZZ.ZZ MAX-TIME1
reason 11 JOBMXTIME11 9 ZZZ.ZZ.ZZ MAX-TIME11
reason 12 JOBMXTIME12 9 ZZZ.ZZ.ZZ MAX-TIME12
reason 13 JOBMXTIME13 9 ZZZ.ZZ.ZZ MAX-TIME13
reason 14 JOBMXTIME14 9 ZZZ.ZZ.ZZ MAX-TIME14
reason 15 JOBMXTIME15 9 ZZZ.ZZ.ZZ MAX-TIME15
reason 16 JOBMXTIME16 9 ZZZ.ZZ.ZZ MAX-TIME16
MUST TIME LIST
reason 1 JOBMTIME1 9 ZZZ.ZZ.ZZ MUST-TIME1
reason 2 JOBMTIME2 9 ZZZ.ZZ.ZZ MUST-TIME2
reason 3 JOBMTIME3 9 ZZZ.ZZ.ZZ MUST-TIME3
reason 4 JOBMTIME4 9 ZZZ.ZZ.ZZ MUST-TIME4
reason 5 JOBMTIME5 9 ZZZ.ZZ.ZZ MUST-TIME5
reason 6 JOBMTIME6 9 ZZZ.ZZ.ZZ MUST-TIME6
reason 7 JOBMTIME7 9 ZZZ.ZZ.ZZ MUST-TIME7
D-14 Unicenter CA-Scheduler Reference Guide, Part 2

D.2 Database Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
MUST TIME LIST
reason 8 JOBMTIME8 9 ZZZ.ZZ.ZZ MUST-TIME8
reason 9 JOBMTIME9 9 ZZZ.ZZ.ZZ MUST-TIME9
reason 1 JOBMTIME1 9 ZZZ.ZZ.ZZ MUST-TIME1
reason 11 JOBMTIME11 9 ZZZ.ZZ.ZZ MUST-TIME11
reason 12 JOBMTIME12 9 ZZZ.ZZ.ZZ MUST-TIME12
reason 13 JOBMTIME13 9 ZZZ.ZZ.ZZ MUST-TIME13
reason 14 JOBMTIME14 9 ZZZ.ZZ.ZZ MUST-TIME14
reason 15 JOBMTIME15 9 ZZZ.ZZ.ZZ MUST-TIME15
reason 16 JOBMTIME16 9 ZZZ.ZZ.ZZ MUST-TIME16
Resource Record
DASD
EXCPS JOBDEXCPS 4 DISK EXCPS
VOLSERS
number listed JOBVNEED 2 VOLUME NUMBER
volume1 JOBVNAME1 6 VOLUME NAME1
volume2 JOBVNAME2 6 VOLUME NAME2
volume3 JOBVNAME3 6 VOLUME NAME3
volume4 JOBVNAME4 6 VOLUME NAME4
volume5 JOBVNAME5 6 VOLUME NAME5
volume6 JOBVNAME6 6 VOLUME NAME6
volume7 JOBVNAME7 6 VOLUME NAME7
volume8 JOBVNAME8 6 VOLUME NAME8
DASD1
type JOBDTYPE1 8 DASD TYPE1
number JOBDNUM1 4 DASD NUMBER1
DASD2
type JOBDTYPE2 8 DASD TYPE2
number JOBDNUM2 4 DASD NUMBER2
DASD3
type JOBDTYPE3 8 DASD TYPE3
number JOBDNUM3 4 DASD NUMBER3
DASD4
type JOBDTYPE4 8 DASD TYPE4
number JOBDNUM4 4 DASD NUMBER4
MAX CPU JOBCPUTME 9 ZZZ.ZZ.ZZ CPU TIME
ROUTE DELAY JOBRTTIME 9 ZZZ.ZZ.ZZ ROUTING TIME
Appendix D. Advantage CA-Earl Reports D-15

D.2 Database Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
SEPARATE
DSNAME JOBEDATAS 45 EXCLUSIVE DATASETS
JOBS LIST
number listed JOBESEP 2 EXCL SEPNO
job1 JOBESEP1 8 EXCL SEP1
job2 JOBESEP2 8 EXCL SEP2
job3 JOBESEP3 8 EXCL SEP3
job4 JOBESEP4 8 EXCL SEP4
job5 JOBESEP5 8 EXCL SEP5
job6 JOBESEP6 8 EXCL SEP6
job7 JOBESEP7 8 EXCL SEP7
job8 JOBESEP8 8 EXCL SEP8
TAPE EXCPS JOBTEXCPS 4 TAPE EXCPS
TAPE1
type JOBTTYPE1 8 TAPE TYPE1
number JOBTNUM1 4 TAPE NUMBER1
TAPE2
type JOBTTYPE2 8 TAPE TYPE2
number JOBTNUM2 4 TAPE NUMBER2
TAPE3
type JOBTTYPE3 8 TAPE TYPE3
number JOBTNUM3 4 TAPE NUMBER3
TAPE4
type JOBTTYPE4 8 TAPE TYPE4
number JOBTNUM4 4 TAPE NUMBER4
UNIT EXCPS JOBOEXCPS 4 OTHER EXCPS
UNIT1
type JOBUREC1 8 UNIT RECORD1
number JOBUNUM1 4 UNIT NUMBER1
UNIT2
type JOBUREC2 8 UNIT RECORD2
number JOBUNUM2 4 UNIT NUMBER2
UNIT3
type JOBUREC3 8 UNIT RECORD3
number JOBUNUM3 4 UNIT NUMBER3
UNIT4
type JOBUREC4 8 UNIT RECORD4
number JOBUNUM4 4 UNIT NUMBER4
D-16 Unicenter CA-Scheduler Reference Guide, Part 2

D.2 Database Reports
D.2.5 Schedule Information from Database
Advantage CA-Earl reports can include schedule information from the Unicenter
CA-Scheduler data base. To include this information on a report, copy the CAJESM
source member and list the fieldnames you want on the PRINT statement.
Information Fieldname Field Format Heading On On Sample
Length Report Reports
Record Name
schedule name SCHNAME 8 SCHEDULE NAME
number of jobs SCHJCOUNT 4 JOB COUNT
Defined Records
schedule base SCHBASEREC 1 BASE RECORD
schedule criteria SCHCRIREC 1 CRITERIA RECORD
schedule info SCHINFOREC 1 INFO RECORD
schedule message SCHMSGREC 1 MESSAGE RECORD
schedule reasons SCHREASON 1 REASON CODE
Base Record
AUTO SELECT SCHAUTOSLC 1 AUTO SELECT
BACKLOG SCHBACKLOG 1 BACKLOG
DATETABLE SCHDTABLE 8 DATE TABLE
JOB statement values
user SCHINFO 16 POWER-JOBCARD
USER-FIELD
notify SCHNTFY 1 POWER-JOBCARD NTFY
print destination SCHLDEST 8 POWER-JOBCARD
LIST-NODE
punch destination SCHPDEST 8 POWER-JOBCARD
PUNCH-NODE
POWER PRIORITY SCHPOWPRTY 2 JOB-CARD PRIORITY
POWER CLASS SCHCLASS 1 CLASS
LIBRARY TYPE SCHLIB 8 LIBRARY TYPE
NODE ID SCHNODEID 8 NODE ID
PRIORITY SCHPRIORITY 2 PRIORITY
RUN ON SYSID SCHCPUID 4 CPU ID
STAGING SCHSTAGE 1 STAGING
TIMES
EARLIEST START SCHERLYTIME 9 ZZZ.ZZ.ZZ EARLY-TIME
MUST START BY SCHMUSTTIME 9 ZZZ.ZZ.ZZ MUST-TIME
COMPLETION SCHDEADTIME 9 ZZZ.ZZ.ZZ DEAD-TIME
Appendix D. Advantage CA-Earl Reports D-17

D.2 Database Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
TIMES
MAX EXECUTION SCHMAXTIME 9 ZZZ.ZZ.ZZ MAXIMUM-TIME
AVERAGE SCHAELAPTME 9 ZZZ.ZZ.ZZ AVG-ELAP-TME
simulated start SCHSIMSTME 9 ZZZ.ZZ.ZZ SIM-ST-TIME
USE SIMTIME SCHSIMSTART 1 SIMULATE START
USERS
userid1 SCHUSERID1 8 SCHEDULE USER-ID1
userid2 SCHUSERID2 8 SCHEDULE USER-ID2
userid3 SCHUSERID3 8 SCHEDULE USER-ID3
userid4 SCHUSERID4 8 SCHEDULE USER-ID4
userid5 SCHUSERID5 8 SCHEDULE USER-ID5
userid6 SCHUSERID6 8 SCHEDULE USER-ID6
userid7 SCHUSERID7 8 SCHEDULE USER-ID7
userid8 SCHUSERID8 8 SCHEDULE USER-ID8
number listed SCHUSERIDS 2 SCHEDULE USER-IDS
last user to SCHUSERLST 8 LAST-USER UPD-SBR
update record
Info Record
COMMENT SCHCOMMENT 3 COMMENT
DELIVERABLES SCHDSPEC1 8 DELIVERY SPEC1
SCHDSPEC2 8 DELIVERY SPEC2
SCHDSPEC3 8 DELIVERY SPEC3
SCHDSPEC4 8 DELIVERY SPEC4
SCHDSPEC5 8 DELIVERY SPEC5
SCHDSPEC6 8 DELIVERY SPEC6
SCHDSPEC7 8 DELIVERY SPEC7
SCHDSPEC8 8 DELIVERY SPEC8
DESCRIPTION SCHMDESC 4 MEMO DESC
DESTINATIONS SCHDEST1 8 DESTINATION1
SCHDEST2 8 DESTINATION2
SCHDEST3 8 DESTINATION3
SCHDEST4 8 DESTINATION4
SCHDEST5 8 DESTINATION5
SCHDEST6 8 DESTINATION6
SCHDEST7 8 DESTINATION7
SCHDEST8 8 DESTINATION8
EXITPARM SCHUSER 16 USER EXIT FIELD
FORM SCHFNUM 8 FORM NUMBER
NOTIFY SCHPNOTIFY 12 PERSON NOTIFY
D-18 Unicenter CA-Scheduler Reference Guide, Part 2

D.2 Database Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
RESPONSIBILITY SCHPRESP 12 PERSON RESPONSIBLE
QUANTITY SCHQUANTITY 8 QUANTITY
SPECIFICATION SCHSPNUM 8 SPEC NUMBER
VERIFY SCHNVERIFY 1 NEEDS VERIFY
Message Record
SEND ALL MESSAGES
to user1 SCHMSGU1 8 MESSAGE USERID1
to user2 SCHMSGU2 8 MESSAGE USERID2
to user3 SCHMSGU3 8 MESSAGE USERID3
to user4 SCHMSGU4 8 MESSAGE USERID4
number of users SCHMSGUS 2 MESSAGE USERIDS
SEND END MESSAGES
to user1 SCHEMSGU1 8 EMESSAGE USERID1
to user2 SCHEMSGU2 8 EMESSAGE USERID2
to user3 SCHEMSGU3 8 EMESSAGE USERID3
to user4 SCHEMSGU4 8 EMESSAGE USERID4
number of users SCHEMSGUS 2 EMESSAGE USERIDS
SEND LATE
MESSAGES
to user1 SCHLMSGU1 8 LMESSAGE USERID1
to user2 SCHLMSGU2 8 LMESSAGE USERID2
to user3 SCHLMSGU3 8 LMESSAGE USERID3
to user4 SCHLMSGU4 8 LMESSAGE USERID4
number of users SCHLMSGUS 2 LMESSAGE USERIDS
SEND START
MESSAGES
to user1 SCHSMSGU1 8 SMESSAGE USERID1
to user2 SCHSMSGU2 8 SMESSAGE USERID2
to user3 SCHSMSGU3 8 SMESSAGE USERID3
to user4 SCHSMSGU4 8 SMESSAGE USERID4
number of users SCHSMSGUS 2 SMESSAGE USERIDS
Reason Code Rec
AVERAGE TIME LIST
reason 1 SCHELAPTM1 9 ZZZ.ZZ.ZZ ELAP-TIME1
reason 2 SCHELAPTM2 9 ZZZ.ZZ.ZZ ELAP-TIME2
reason 3 SCHELAPTM3 9 ZZZ.ZZ.ZZ ELAP-TIME3
Appendix D. Advantage CA-Earl Reports D-19

D.2 Database Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
AVERAGE TIME LIST
reason 4 SCHELAPTM4 9 ZZZ.ZZ.ZZ ELAP-TIME4
reason 5 SCHELAPTM5 9 ZZZ.ZZ.ZZ ELAP-TIME5
reason 6 SCHELAPTM6 9 ZZZ.ZZ.ZZ ELAP-TIME6
reason 7 SCHELAPTM7 9 ZZZ.ZZ.ZZ ELAP-TIME7
reason 8 SCHELAPTM8 9 ZZZ.ZZ.ZZ ELAP-TIME8
reason 9 SCHELAPTM9 9 ZZZ.ZZ.ZZ ELAP-TIME9
reason 1 SCHELAPTM1 9 ZZZ.ZZ.ZZ ELAP-TIME1
reason 11 SCHELAPTM11 9 ZZZ.ZZ.ZZ ELAP-TIME11
reason 12 SCHELAPTM12 9 ZZZ.ZZ.ZZ ELAP-TIME12
reason 13 SCHELAPTM13 9 ZZZ.ZZ.ZZ ELAP-TIME13
reason 14 SCHELAPTM14 9 ZZZ.ZZ.ZZ ELAP-TIME14
reason 15 SCHELAPTM15 9 ZZZ.ZZ.ZZ ELAP-TIME15
reason 16 SCHELAPTM16 9 ZZZ.ZZ.ZZ ELAP-TIME16
DEADLINE LIST
reason 1 SCHDTME1 9 ZZZ.ZZ.ZZ DEAD-TIME1
reason 2 SCHDTME2 9 ZZZ.ZZ.ZZ DEAD-TIME2
reason 3 SCHDTME3 9 ZZZ.ZZ.ZZ DEAD-TIME3
reason 4 SCHDTME4 9 ZZZ.ZZ.ZZ DEAD-TIME4
reason 5 SCHDTME5 9 ZZZ.ZZ.ZZ DEAD-TIME5
reason 6 SCHDTME6 9 ZZZ.ZZ.ZZ DEAD-TIME6
reason 7 SCHDTME7 9 ZZZ.ZZ.ZZ DEAD-TIME7
reason 8 SCHDTME8 9 ZZZ.ZZ.ZZ DEAD-TIME8
reason 9 SCHDTME9 9 ZZZ.ZZ.ZZ DEAD-TIME9
reason 1 SCHDTME1 9 ZZZ.ZZ.ZZ DEAD-TIME1
reason 11 SCHDTME11 9 ZZZ.ZZ.ZZ DEAD-TIME11
reason 12 SCHDTME12 9 ZZZ.ZZ.ZZ DEAD-TIME12
reason 13 SCHDTME13 9 ZZZ.ZZ.ZZ DEAD-TIME13
reason 14 SCHDTME14 9 ZZZ.ZZ.ZZ DEAD-TIME14
reason 15 SCHDTME15 9 ZZZ.ZZ.ZZ DEAD-TIME15
reason 16 SCHDTME16 9 ZZZ.ZZ.ZZ DEAD-TIME16
EARLY TIME LIST
reason 1 SCHETIME1 9 ZZZ.ZZ.ZZ EARLY-TIME1
reason 2 SCHETIME2 9 ZZZ.ZZ.ZZ EARLY-TIME2
reason 3 SCHETIME3 9 ZZZ.ZZ.ZZ EARLY-TIME3
reason 4 SCHETIME4 9 ZZZ.ZZ.ZZ EARLY-TIME4
reason 5 SCHETIME5 9 ZZZ.ZZ.ZZ EARLY-TIME5
reason 6 SCHETIME6 9 ZZZ.ZZ.ZZ EARLY-TIME6
reason 7 SCHETIME7 9 ZZZ.ZZ.ZZ EARLY-TIME7
reason 8 SCHETIME8 9 ZZZ.ZZ.ZZ EARLY-TIME8
reason 9 SCHETIME9 9 ZZZ.ZZ.ZZ EARLY-TIME9
reason 1 SCHETIME1 9 ZZZ.ZZ.ZZ EARLY-TIME1
reason 11 SCHETIME11 9 ZZZ.ZZ.ZZ EARLY-TIME11
D-20 Unicenter CA-Scheduler Reference Guide, Part 2

D.2 Database Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
EARLY TIME LIST
reason 12 SCHETIME12 9 ZZZ.ZZ.ZZ EARLY-TIME12
reason 13 SCHETIME13 9 ZZZ.ZZ.ZZ EARLY-TIME13
reason 14 SCHETIME14 9 ZZZ.ZZ.ZZ EARLY-TIME14
reason 15 SCHETIME15 9 ZZZ.ZZ.ZZ EARLY-TIME15
reason 16 SCHETIME16 9 ZZZ.ZZ.ZZ EARLY-TIME16
MAXIMUM TIME LIST
reason 1 SCHMXTIME1 9 ZZZ.ZZ.ZZ MAX-TIME1
reason 2 SCHMXTIME2 9 ZZZ.ZZ.ZZ MAX-TIME2
reason 3 SCHMXTIME3 9 ZZZ.ZZ.ZZ MAX-TIME3
reason 4 SCHMXTIME4 9 ZZZ.ZZ.ZZ MAX-TIME4
reason 5 SCHMXTIME5 9 ZZZ.ZZ.ZZ MAX-TIME5
reason 6 SCHMXTIME6 9 ZZZ.ZZ.ZZ MAX-TIME6
reason 7 SCHMXTIME7 9 ZZZ.ZZ.ZZ MAX-TIME7
reason 8 SCHMXTIME8 9 ZZZ.ZZ.ZZ MAX-TIME8
reason 9 SCHMXTIME9 9 ZZZ.ZZ.ZZ MAX-TIME9
reason 1 SCHMXTIME1 9 ZZZ.ZZ.ZZ MAX-TIME1
reason 11 SCHMXTIME11 9 ZZZ.ZZ.ZZ MAX-TIME11
reason 12 SCHMXTIME12 9 ZZZ.ZZ.ZZ MAX-TIME12
reason 13 SCHMXTIME13 9 ZZZ.ZZ.ZZ MAX-TIME13
reason 14 SCHMXTIME14 9 ZZZ.ZZ.ZZ MAX-TIME14
reason 15 SCHMXTIME15 9 ZZZ.ZZ.ZZ MAX-TIME15
reason 16 SCHMXTIME16 9 ZZZ.ZZ.ZZ MAX-TIME16
MUST TIME LIST
reason 1 SCHMTIME1 9 ZZZ.ZZ.ZZ MUST-TIME1
reason 2 SCHMTIME2 9 ZZZ.ZZ.ZZ MUST-TIME2
reason 3 SCHMTIME3 9 ZZZ.ZZ.ZZ MUST-TIME3
reason 4 SCHMTIME4 9 ZZZ.ZZ.ZZ MUST-TIME4
reason 5 SCHMTIME5 9 ZZZ.ZZ.ZZ MUST-TIME5
reason 6 SCHMTIME6 9 ZZZ.ZZ.ZZ MUST-TIME6
reason 7 SCHMTIME7 9 ZZZ.ZZ.ZZ MUST-TIME7
reason 8 SCHMTIME8 9 ZZZ.ZZ.ZZ MUST-TIME8
reason 9 SCHMTIME9 9 ZZZ.ZZ.ZZ MUST-TIME9
reason 1 SCHMTIME1 9 ZZZ.ZZ.ZZ MUST-TIME1
reason 11 SCHMTIME11 9 ZZZ.ZZ.ZZ MUST-TIME11
reason 12 SCHMTIME12 9 ZZZ.ZZ.ZZ MUST-TIME12
reason 13 SCHMTIME13 9 ZZZ.ZZ.ZZ MUST-TIME13
reason 14 SCHMTIME14 9 ZZZ.ZZ.ZZ MUST-TIME14
reason 15 SCHMTIME15 9 ZZZ.ZZ.ZZ MUST-TIME15
reason 16 SCHMTIME16 9 ZZZ.ZZ.ZZ MUST-TIME16
Appendix D. Advantage CA-Earl Reports D-21

D.3 History File Reports
D.3 History File Reports
Following are examples of CA-Earl History File reports.
D.3.1 CAJESETH Source Member
The CAJESETH source member sets the record ID to either HHR for job records or
THR for schedule records (sequential read only is allowed).
SET PRMFUNC = 'GETS'
SET PRMID = 'HHR '
SET PRMNME = '
SET PRMNUM = ' '
SET PRMSTA = ' '
SET PRMSCH = '
'
'
D.3.2 CAJECNVS Source Member
The CAJECNVS source member decodes the status codes stored in the history file.
Specify it on a COPY statement if you want to include STATUS as one of the fields
on the report. (If a new status is added, you will have to add it to this list.)
! DECODE LOGIC FOR JOB OR SCHEDULE STATUS CODE
DECODE_STATUS: PROC
DECODE IN_STATUS INTO OUT_STATUS
'A' = 'ABENDED '
'B' = 'NO BACKLOG CANCELLED'
'C' = 'COMPLETED '
'F' = 'FAILED '
'I' = 'INTERRUPTED '
'N' = 'OPERATOR CANCELLED '
'T' = 'WAITING START TIME '
'P' = 'WAITING PREDS '
'R' = 'WAITING RESOURCES '
'O' = 'WAITING OPER. SUBMIT'
'Q' = 'SUBMITTED '
'S' = 'STARTED '
ELSE 'UNKOWN '
ENDPROC
D.3.3 CAIDEFD Source Member
The CAIDEFD source member converts dates from Julian to Gregorian format.
Specify it on a COPY statement if you want dates to be printed as DD/MM/YY
instead of DDDYY.
D-22 Unicenter CA-Scheduler Reference Guide, Part 2

D.3 History File Reports
!
! CAI EARL JULIAN-GREGORIAN DATE CONVERSION ROUTINE
!
! COPY MEMBER : CAIDEFD
! CONTAINS : ALL EARL DEFINE STATEMENTS FOR THE
! DATE CONVERSION ROUTINE
!
!
!
DEF CAI_DTAB ARRAY 12 OF (P 2.) = 31 29 31 3 31 3 31 31 3 31 3 31
!
DEF CAI_DATE (P 5.) = 841
DEF CAI_YEAR = CAI_DATE 1 U
DEF CAI_DAYS = CAI_DATE 2-3 P
!
DEF CAI_NDAYS (P 3.) =
!
DEF CAI_R1 (P 2.) = 1
DEF CAI_MNTH (P 2.) =
!
DEF CAI_OUTDATE (X 8) = ' '
DEF CAI_OUTMM = CAI_OUTDATE 1-2 N
DEF CAI_OUTDD = CAI_OUTDATE 4-5 N
DEF CAI_OUTYY = CAI_OUTDATE 7-8 N
!
Appendix D. Advantage CA-Earl Reports D-23

D.3 History File Reports
D.3.4 Job Information from History File
Advantage CA-Earl reports can include job information from the history file. To
include this information on a report, COPY the CAJEJHR source member and list the
fieldnames you want on the PRINT statement. See the chapter "Reports" for samples.
Information Fieldname Field Format Heading On On Sample
Length Report Reports
Record Name
job name JHRJNAME 8 JOB NAME yes
job number JHRJNUMBER 2 JNO yes
schedule name JHRSCHNAME 8 SCHEDULE NAME yes
station ID JHRSTATID 2 STATION ID yes
Selection Data
reason for JHRRCODE 2 REASON CODE yes
selection
date selected JHRSDATE 8 SCHEDULED DATE yes
time selected JHRSCHTME 9 ZZZ.ZZ.ZZ SCHEDULED TIME yes
Defined Times
earliest start
date JHREDATE 8 EARLY DATE
time JHRETIME 9 ZZZ.ZZ.ZZ EARLY TIME
"must start by"
date JHRMDATE 8 MUST DATE yes
time JHRMTIME 9 ZZZ.ZZ.ZZ MUST TIME yes
completion
date JHRDDATE 8 DEADLINE DATE yes
time JHRDTIME 9 ZZZ.ZZ.ZZ DEADLINE TIME yes
Actual Times
available
date JHRADATE 8 AVAILABLE DATE
time JHRAVTME 9 ZZZ.ZZ.ZZ AVAILABLE TIME yes
start
date JHRACTSD 8 ACTUAL ST-DATE yes
time JHRACSTME 9 ZZZ.ZZ.ZZ ACTUAL ST-TIME yes
D-24 Unicenter CA-Scheduler Reference Guide, Part 2

D.3 History File Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
end
date JHRACTED 8 ACTUAL END-DATE yes
time JHRACETME 9 ZZZ.ZZ.ZZ ACTUAL END-TIME yes
elapsed time JHRELAPTME 9 ZZZ.ZZ.ZZ ELAPSED TIME yes
CPU time JHRCPUTME 9 ZZZ.ZZ.ZZ CPU TIME yes
Actual EXCPS
DASD EXCPS JHRDASDIO 4 DASD I/O
tape EXCPS JHRTAPEIO 4 TAPE I/O
unit EXCPS JHROTHERIO 4 OTHER I/O
Userid That
Issued Command
RUN JHRURUN 8 USERID RUN
HOLD JHRUHOLD 8 USERID HOLD
RELEASE JHRUREL 8 USERID RELEASE
CANCEL JHRUCNCL 8 USERID CANCEL yes
FORCE JHRUFRCE 8 USERID FORCED yes
START JHRUSTRT 8 USERID STARTED
COMPLETE JHRUCOMP 8 USERID COMPLETED
Status
completion code JHRCCODE 5 COMPLETION CODE yes
final status JHRSTATUS 1 STATUS yes
POWER job number JHRJOBNO 2 POWER JOBNO yes
Appendix D. Advantage CA-Earl Reports D-25

D.3 History File Reports
D.3.5 Schedule Information from History File
Advantage CA-Earl reports can include schedule information from the history file. To
include this information on a report, copy the CAJESHR source member and list the
fieldnames you want on the PRINT statement.
Information Fieldname Field Format Heading On On Sample
Length Report Reports
Record Name
schedule name SHRSCHNAME 8 SCHEDULE NAME
Selection Data
reason SHRRCODE 2 REASON CODE
date SHRSDATE 8 SCHEDULED DATE
time SHRSCHTME 9 ZZZ.ZZ.ZZ SCHEDULED TIME
Defined Times
earliest start
date SHREDATE 8 EARLY DATE
time SHRETIME 9 ZZZ.ZZ.ZZ EARLY TIME
"must start by"
date SHRMDATE 8 MUST DATE
time SHRMTIME 9 ZZZ.ZZ.ZZ MUST TIME
completion
date SHRDDATE 8 DEADLINE DATE
time SHRDTIME 9 ZZZ.ZZ.ZZ DEADLINE TIME
Actual Times
available
date SHRADATE 8 AVAILABLE DATE
time SHRAVTME 9 ZZZ.ZZ.ZZ AVAILABLE TIME
start
date SHRACTSD 8 ACTUAL ST-DATE
time SHRACSTME 9 ZZZ.ZZ.ZZ ACTUAL ST-TIME
end
date SHRACTED 8 ACTUAL END-DATE
time SHRACETME 9 ZZZ.ZZ.ZZ ACTUAL END-TIME
elapsed time SHRELAPTME 9 ZZZ.ZZ.ZZ ELAPSED TIME
CPU time SHRCPUTME 9 ZZZ.ZZ.ZZ CPU TIME
D-26 Unicenter CA-Scheduler Reference Guide, Part 2

D.3 History File Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
Actual EXCPS
DASD EXCPS SHRDASDIO 4 DASD I/O
tape EXCPS SHRTAPEIO 4 TAPE I/O
unit EXCPS SHROTHERIO 4 OTHER I/O
Userid That
Issued Command
RUN SHRURUN 8 USERID RUN
HOLD SHRUHOLD 8 USERID HOLD
RELEASE SHRUREL 8 USERID RELEASE
CANCEL SHRUCNCL 8 USERID CANCEL
FORCE SHRUFRCE 8 USERID FORCED
Status
completion code SHRCCODE 5 COMPLETION CODE
final status SHRSTATUS 1 STATUS
Appendix D. Advantage CA-Earl Reports D-27

D.4 Tracking File Reports
D.4 Tracking File Reports
Following are examples of CA-Earl Tracking File reports.
D.4.1 CAJESETT Source Member
This member sets the parameters for communication between Unicenter CA-Scheduler
and Advantage CA-Earl. Specify it on a COPY statement. The record ID is set to JTR
to select job records from the tracking file. Use PRMNME to define which jobs will
be selected:
To Select Specify PRMNME = Example
All jobs '*' PRMNME = '*'
One specific job 'jobname' PRMNME = 'JOBA'
A group of jobs 'jobname *' PRMNME = 'PAY*'
The following sample selects all jobs:
SET PRMFUNC = 'GETS'
SET PRMID = 'JTR '
SET PRMNME = '
SET PRMNUM = ' '
SET PRMSTA = ' '
SET PRMSCH = '
SET PRMONODE = '
'
'
'
D.4.2 CAJESETS Source Member
The CAJESETS source member sets the parameters for communication between
Unicenter CA-Scheduler and Advantage CA-Earl. Specify it on a COPY statement.
The record ID is set to STR to select schedule records from the tracking file. Use
PRMNME to define which schedules will be selected:
To Select Specify PRMSCH = Example
All schedules '*' PRMSCH = '*'
One specific schedule 'sname' PRMSCH = 'SCHDA'
A group of schedules 'sname *' PRMSCH = 'PAY*'
D-28 Unicenter CA-Scheduler Reference Guide, Part 2

D.4 Tracking File Reports
The following sample selects all schedules:
SET PRMFUNC = 'GETS'
SET PRMID = 'STR '
SET PRMNME = '
SET PRMNUM = ' '
SET PRMSTA = ' '
SET PRMSCH = '
SET PRMONODE = '
'
'
'
D.4.3 CAJECNV0 Source Member
The CAJECNV0 source member assigns hold status and run status values, determined
from mask values on the job or schedule tracking records. Specify it on a COPY
statement.
Appendix D. Advantage CA-Earl Reports D-29

D.4 Tracking File Reports
DECODE_STATUS: PROC
!
DECODE IN_HSTAT INTO OUT_HSTAT
M'' = 'ACTIVE '
M'1' = 'NOT REQUESTED '
M'1' = 'NOT REQSTD SUCCESSOR'
M'11' = 'AUTO RECOVERY HELD '
M'1' = 'HELD BY --- XXXXXXXX'
M'11' = 'CANCELED BY XXXXXXXX'
M'11' = 'NO BACKLOG CANCELLED'
M'111' = 'HELD BY SHUTDOWN '
ELSE 'UNKNOWN '
!
DECODE IN_RSTAT INTO OUT_RSTAT
M'' = 'SCHEDULED TO RUN '
M'1' = 'WAITING START TIME '
M'1' = 'WAITING PREDS '
M'11' = 'WAITING RESOURCES '
M'1' = 'UNKNOWN '
M'11' = 'SUBMIT IN PROGRESS '
M'11' = 'SUBMIT COMPLETED '
M'111' = 'SUBMIT FAILED '
M'1' = 'RECEIVED AT NODE '
M'11' = 'STARTED '
M'11' = 'FAILED '
M'111' = 'ABENDED '
M'11' = 'INTERRUPTED '
M'111' = 'COMPLETED '
M'111' = 'OS PURGED '
!
!
! IF WAITING FOR PREDS AND WAITING PRE-CPU PREDS THEN CHANGE OUT_RSTAT
!
!
CK_WAIT_PREDS:
IF IN_RSTAT NOT = M'1' THEN GOTO CK_SBMT
ENDIF
IF IN_FLG4 = M'XX1XXXXX' THEN
SET OUT_RSTAT = 'WAITING PRE-CPU END '
GOTO CK_SBMT
ENDIF
IF IN_FLG4 = M'XXX1XXXX' THEN
SET OUT_RSTAT = 'WAITING CPU JOB END '
ENDIF
!
!
! IF SUBMIT IS COMPLETED AND SCHEDULE IS EXTERNAL THEN STATUS IS
! 'WAIT NON-CPU START'
!
D-30 Unicenter CA-Scheduler Reference Guide, Part 2

D.4 Tracking File Reports
!
CK_SBMT:
IF IN_RSTAT NOT = M'11' THEN GOTO CK_SBFL
ENDIF
IF IN_FLG1 = M'XX1XXXXX' THEN
SET OUT_RSTAT = 'WAIT NON-CPU START '
ENDIF
!
!
! IF SUBMIT FAILED AND JOB IS NOT IN READER QUEUE THEN STATUS IS
! 'WAITING USER SUBMIT'
!
!
CK_SBFL:
IF IN_RSTAT NOT = M'111' THEN GOTO CK_STRT
ENDIF
IF IN_FLG4 = M'X1XXXXXX' THEN
SET OUT_RSTAT = 'WAITING USER SUBMIT '
ENDIF
!
!
! IF STARTED AND SCHEDULE IS EXTERNAL AND IT IS AN AUTOMATICALLY
! SELECTED SCHEDULE THEN STATUS IS 'AUTO STARTED'
!
!
CK_STRT:
IF IN_RSTAT NOT = M'11' THEN GOTO END_BITS_CK
ENDIF
IF IN_FLG1 NOT = M'XX1XXXXX' THEN GOTO END_BITS_CK
ENDIF
IF IN_FLG1 = M'1XXXXXXX' THEN
SET OUT_RSTAT = 'AUTO STARTED '
ENDIF
!
END_BITS_CK:
!
ENDPROC
Appendix D. Advantage CA-Earl Reports D-31

D.4 Tracking File Reports
D.4.4 Job Information from Tracking File
Advantage CA-Earl reports can include job information from the Unicenter
CA-Scheduler tracking file. To include this information on a report, copy the
CAJEJTR source member and list the fieldnames you want on the PRINT statement.
See the chapter "Reports" for samples.
Information Fieldname Field Format Heading On On Sample
Length Report Reports
Record Name
job name JTRJNAME 8 JOB NAME yes
job number JTRJNUMBER 2 JOB NMBR yes
schedule name JTRSCHNAME 8 SCHEDULE NAME yes
station ID JTRSTATID 2 STATN ID yes
node of origin JTRONODE 8 NODE ORIGIN
CPU where schedu- JTRSSID 4 CPU ID
ling was done
JCL Library Info
LIBRARY TYPE JTRLIBS 1 LIBTYPE
MEMBER NAME JTRMEMBR 8 JCL MEMBR-NAME
MBR SUBID JTRMBRSB 8 JCL MEMBR-SUBID
MEMBER PASSWORD JTRLPASS 8 JCL MEMBR-PWORD
SLI SUBLIB JTRSUBLB 1 SUBLIB TYPE
ICCF LIB NUMBER JTRICCFL 3 ICCF LIB-NUMBR
Misc Defined Info
ABEND alternate
schedule JTRABSCD 8 ABEND SCHD-NAME
BACKLOG JTRBKLOG 1 BACKLOG Y|N
DISPLAY KEY JTRDISPK 8 DOC DISPL KY
DISPLAY TIME JTRDISPT 9 ZZZ.ZZ.ZZ DOC DISPL TIME
JOB PRIORITY JTRJPRTY 2 JOB PRIORITY
MEMO JTRMEMO 6 MEMO MESSAGE
STAGE JTRSTAGE 1 STAGE Y|N
DASD VOLSERS
number listed JTRVOLS 2 VOLSERS COUNT
volume1 JTRVOLS1 6 VOLUME ONE
volume2 JTRVOLS2 6 VOLUME TWO
volume3 JTRVOLS3 6 VOLUME THREE
volume4 JTRVOLS4 6 VOLUME FOUR
volume5 JTRVOLS5 6 VOLUME FIVE
volume6 JTRVOLS6 6 VOLUME SIX
volume7 JTRVOLS7 6 VOLUME SEVEN
volume8 JTRVOLS8 6 VOLUME EIGHT
D-32 Unicenter CA-Scheduler Reference Guide, Part 2

D.4 Tracking File Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
SEPARATE
DSNAME JTRDSN 44 SEP DSN
JOBS LIST
number listed JTRJSEPS 2 SEP-JOB COUNT
job1 JTRJSEP1 8 SEP-JOB ONE
job2 JTRJSEP2 8 SEP-JOB TWO
job3 JTRJSEP3 8 SEP-JOB THREE
job4 JTRJSEP4 8 SEP-JOB FOUR
job5 JTRJSEP5 8 SEP-JOB FIVE
job6 JTRJSEP6 8 SEP-JOB SIX
job7 JTRJSEP7 8 SEP-JOB SEVEN
job8 JTRJSEP8 8 SEP-JOB EIGHT
Selection Data
reason for JTRRC 2 REASON CODE yes
selection
date selected JTRADATE 5 ACTUAL SCHED-DATE yes
time selected JTRATIME 9 ZZZ.ZZ.ZZ ACTUAL SCHDTIME yes
Defined Times
(date and time
together)
earliest start JTRERLY 9 ZZZ.ZZ.ZZ EARLY TIME
"must start by" JTRMUST 9 ZZZ.ZZ.ZZ MUST STRT TIME yes
maximum JTRMXTIM 9 ZZZ.ZZ.ZZ MAX TIME
completion JTRDEDLN 9 ZZZ.ZZ.ZZ DEADLINE TIME yes
Adjusted Times
(date and time
separated)
earliest start
date JTRERDT 5 ERLYTIME DATE
time JTRADJER 9 ZZZ.ZZ.ZZ ADJUSTED ERLYTIME
"must start by"
date JTRMUDT 5 MUSTTIME DATE
time JTRADJMU 9 ZZZ.ZZ.ZZ ADJUSTED MUSTTIME
maximum
date JTRMXDT 5 MAXTIME DATE
time JTRADJMX 9 ZZZ.ZZ.ZZ ADJUSTED MAXTIME
completion
date JTRDEDT 5 DEADLINE DATE
time JTRADJDE 9 ZZZ.ZZ.ZZ ADJUSTED DEADLINE
Appendix D. Advantage CA-Earl Reports D-33

D.4 Tracking File Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
Actual Times
available
date JTRVDATE 5 ACTUAL AVAIL-DATE
time JTRVTIME 9 ZZZ.ZZ.ZZ ACTUAL AVLTIME yes
start
date JTRSDATE 5 ACTUAL START-DATE
time JTRSTIME 9 ZZZ.ZZ.ZZ ACTUAL STRTTIME yes
end
date JTREDATE 5 ACTUAL END-DATE
time JTRETIME 9 ZZZ.ZZ.ZZ ACTUAL END-TIME yes
purge
date JTRPDATE 5 ACTUAL PRGE-DATE
time JTRPTIME 9 ZZZ.ZZ.ZZ ACTUAL PRGE-TIM
average time JTRAVGT 9 ZZZ.ZZ.ZZ AVRG RUNTIME
Jobcard Values
CLASS JTRCLASS 1 CLASS
PRIORITY JTRPRTY 2 POWER/JES PRIORITY
RUN ON SYSID JTRRSID 4 JOBCARD CPU-ID
NODE ID JTRRNODE 8 JOBCARD NODE
POWER USER info JTRJINFO 16 INFO-AFTER JOB-NAME
Actual Values
CPU JTRXSYS 4 ACTUAL SYSID
node ID JTRXNODE 8 ACTUAL NODE-ID
operating system JTRXNODT 1 ACTUAL NODE-TYPE
CPU time JTRCPUT 4 CPU TIME yes
job number JTRPWSEQ 2 SEQ-NUMBER
partition ID JTRPART 4 PARTITION ADDRESS
number of steps JTRSTEPS 4 NUMBER-OF STEPS
Actual EXCPS
DASD JTREXCPD 4 DISK EXCP-COUNT
tape JTREXCPT 4 TAPE EXCP-COUNT
unit JTREXCPO 4 OTHER EXCP-COUNT
D-34 Unicenter CA-Scheduler Reference Guide, Part 2

D.4 Tracking File Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
Userid That
Issued Command
RUN JTRCMRUN 8 USERID RUN
SUBMIT JTRCMSUB 8 USERID SUB
HOLD JTRCMHLD 8 USERID HOLD
RELEASE JTRCMRLS 8 USERID RELEASE
CANCEL JTRCMCNC 8 USERID CANCEL
FORCE JTRCMFRC 8 USERID FORCED
START JTRCMSTR 8 USERID STARTED
COMPLETE JTRCMCMP 8 USERID COMPLETED
Status
HELD JTRHSTAT 1 HOLD STATUS
STARTED JTRRSTAT 1 RUN STATUS
completion code JTRCC 5 COMPLETION CODE yes
FAIL CODE JTRFCODE 5 FAIL CODE
final status JTRSTATUS 1 STATUS
Appendix D. Advantage CA-Earl Reports D-35

D.4 Tracking File Reports
D.4.5 Schedule Information from Tracking File
Advantage CA-Earl reports can include schedule information from the tracking file. To
include this information on a report, copy the CAJESTR source member and list the
fieldnames you want on the PRINT statement.
Information Fieldname Field Format Heading On On Sample
Length Report Reports
Record Name
schedule name STRNAME 8 SCHEDULE NAME yes
CPU where sched- STRSSID 4 SCHEDULED CPU
uling was done
node where sched- STRSNODE 4 SCHEDULED NODE
uling was done
CPU of origin if STROSID 4 ORIGINAL SYSID
job came from
another node
node of origin STRONODE 8 ORIGIN NODE-NAME
jobs in schedule STRJCONT 4 NUMBER-OF JOBS
Misc Defined Info
BACKLOG STRBKLOG 1 BACKLOG Y|N
DISPLAY
KEY STRDISPK 8 DOC DISPL KY
TIME STRDISPT 9 ZZZ.ZZ.ZZ DOC DISPL TIME
LIBRARY TYPE STRLIBS 1 LIBTYPE
MEMO STRMEMO 6 MEMO MESSAGE
SCHED PRIORITY STRSPRTY 2 SCHEDULE PRIORITY
STAGE STRSTAGE 1 STAGE Y|N
USERS
number listed STRUIDS 2 USER-ID COUNT
user1 STRUID1 6 USER ONE
user2 STRUID2 6 USER TWO
user3 STRUID3 6 USER THREE
user4 STRUID4 6 USER FOUR
user5 STRUID5 6 USER FIVE
user6 STRUID6 6 USER SIX
user7 STRUID7 6 USER SEVEN
user8 STRUID8 6 USER EIGHT
D-36 Unicenter CA-Scheduler Reference Guide, Part 2

D.4 Tracking File Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
Selection Data
selection reason STRRC 2 SCHEDULING REASON yes
date selected STRADATE 5 ACTUAL SCHED-DATE
time selected STRATIME 9 ZZZ.ZZ.ZZ ACTUAL SCHDTIME
datetable STRDTAB DATE-TABLE NAME
calendar STRCALENDAR CALENDAR NAME
Defined Times
(date and time
together)
earliest start STRERLY 9 ZZZ.ZZ.ZZ EARLY TIME
"must start by" STRMUST 9 ZZZ.ZZ.ZZ MUST-STRT TIME yes
maximum STRMXTIM 9 ZZZ.ZZ.ZZ MAX-TIME
completion STRDEDLN 9 ZZZ.ZZ.ZZ DEADLINE TIME yes
Adjusted Times
(date and time
separated)
earliest start
date STRERDT 5 ERLYTIME DATE
time STRADJER 9 ZZZ.ZZ.ZZ ADJUSTED ERLYTIME
"must start by"
date STRMUDT 5 MUSTTIME DATE
time STRADJMU 9 ZZZ.ZZ.ZZ ADJUSTED MUSTTIME
maximum
date STRMXDT 5 MAXTIME DATE
time STRADJMX 9 ZZZ.ZZ.ZZ ADJUSTED MAXTIME
completion
date STRDEDT 5 DEADLINE DATE
time STRADJDE 9 ZZZ.ZZ.ZZ ADJUSTED DEADLINE
Actual Times
available
date STRVDATE 5 ACTUAL AVAIL-DATE
time STRVTIME 9 ZZZ.ZZ.ZZ ACTUAL AVLTIME yes
start
date STRSDATE 5 ACTUAL START-DATE
time STRSTIME 9 ZZZ.ZZ.ZZ ACTUAL STRTTIME yes
end
date STREDATE 5 ACTUAL END-DATE
time STRETIME 9 ZZZ.ZZ.ZZ ACTUAL END-TIME yes
average time STRAVGT 9 ZZZ.ZZ.ZZ AVG-HISTORY RUNTIME
Appendix D. Advantage CA-Earl Reports D-37

D.4 Tracking File Reports
Information Fieldname Field Format Heading On On Sample
Length Report Reports
Jobcard values
CLASS STRCLASS 1 CLASS
RUN ON SYSID STRRSID 4 CPU-RUN ID
POWER
PRIORITY STRPRTY 2 POWER PRIORITY
USER info STRJINFO 16 DEFAULT USER-INFO
Actual values
CPU time STRCPUT 4 CPU TIME
node ID STRRNODE 8 NODE ID
DASD EXCPS STREXCPD 4 DISK EXCP-COUNT
tape EXCPS STREXCPT 4 TAPE EXCP-COUNT
unit EXCPS STREXCPO 4 OTHER EXCP-COUNT
Userid That
Issued Command
RUN STRCMRUN 8 USERID RUN
HOLD STRCMHLD 8 USERID HOLD
RELEASE STRCMRLS 8 USERID RELEASE
CANCEL STRCMCNC 8 USERID CANCEL
FORCE STRCMFRC 8 USERID FORCED
Command Info.
command causing STRCOMMAND CMD-CAUSED
submit
JOB-SUBMIT
run command date STRRUNCDATE
RUN-CMD DATE
Status
HELD STRHSTAT 1 HOLD STATUS
STARTED STRRSTAT 1 RUN STATUS
completed and STREDDJB 4 CMPL/CANCLD
canceled jobs
JOB-COUNT
completion code STRCC 5 COMPLETION CODE
D-38 Unicenter CA-Scheduler Reference Guide, Part 2

D.5 Documentation or Staging Library Reports
D.5 Documentation or Staging Library Reports
Following are examples of CA-Earl Documentation or Staging Library reports.
D.5.1 CAJESETD Source Member
The CAJESETD source member sets the parameters for communication between
Unicenter CA-Scheduler and Advantage CA-Earl. Specify it on a COPY statement.
The record ID is set to DDIR for documentation library directory records. Use
PRMNME to define which jobs will be selected:
To Select Specify PRMNME = Example
All jobs '*' PRMNME = '*'
One specific job 'jobname' PRMNME = 'JOBA'
A group of jobs 'jobname *' PRMNME = 'PAY*'
The following sample selects all jobs:
SET PRMFUNC = 'GETS'
SET PRMID = 'DDIR'
SET PRMNME = '
SET PRMNUM = ' '
SET PRMSTA = ' '
SET PRMSCH = '
SET PRMDSPN = '
'
'
'
D.5.2 CAJDDIR Source Member
The CAJDDIR source member sets the parameters for selection of documentation
member records using information from the documentation directory record. Specify it
on a COPY statement.
REC_IS_DDIR: PROC
SET PRMID = 'DMBR'
SET PRMDSPN = DIRDSPN
SET PRMNME = DIRJOBN
SET PRMNUM = DIRJNUM
SET PRMSTA = DIRJSTN
SET PRMSCH = DIRSCDN
SET PRMSEQN = 1
SET OUTRECN = DIRRECN
SET OUTUPDT = DIRUPDT
SET TOT_MEMBRS = DIRRECN
SET TIME_STAMP = DIRTIME
ENDPROC
Appendix D. Advantage CA-Earl Reports D-39

D.5 Documentation or Staging Library Reports
D.5.3 CAJESETG Source Member
The CAJESETG source member sets the parameters for communication between
Unicenter CA-Scheduler and Advantage CA-Earl. Specify it on a COPY statement.
The record ID is set to SDIR for staging library directory records. Use PRMNME to
define which jobs will be selected:
To Select Specify PRMNME = Example
All jobs '*' PRMNME = '*'
One specific job 'jobname' PRMNME = 'JOBA'
A group of jobs 'jobname *' PRMNME = 'PAY*'
The following sample selects all jobs:
SET PRMFUNC = 'GETS'
SET PRMID = 'SDIR'
SET PRMNME = '
SET PRMNUM = ' '
SET PRMSTA = ' '
SET PRMSCH = '
'
'
D.5.4 CAJSDIR Source Member
The CAJSDIR source member sets the parameters for selection of staging member
records using information from the staging directory record. Specify it on a COPY
statement.
REC_IS_SDIR: PROC
SET PRMID = 'SMBR'
SET PRMNME = DIRJOBN
SET PRMNUM = DIRJNUM
SET PRMSTA = DIRJSTN
SET PRMSCH = DIRSCDX
SET PRMSEQN = 1
SET OUTRECN = DIRRECN
SET OUTUPDT = DIRUPDT
SET TOT_MEMBRS = DIRRECN
SET TIME_STAMP = DIRTIME
ENDPROC
D.5.5 CAJMBR Source Member
The CAJMBR source member advances the record sequence number and edits the
current record sequence number for output. Specify it on a COPY statement.
D-40 Unicenter CA-Scheduler Reference Guide, Part 2

D.5 Documentation or Staging Library Reports
REC_IS_MBR: PROC
!
! SET EDIT-FIELD EQUAL TO CURRENT RECORD-SEQUENCE NUMBER
! FOR PRINT-LINE (DETAIL LINE)
!
SET EDITSEQ = JCLSEQN
SET PRMSEQN = PRMSEQN + 1
ENDPROC
D.5.6 Information from Documentation or Staging Library
Advantage CA-Earl reports can include information from the Unicenter CA-Scheduler
documentation library or the JCL staging library. To include this information on a
report, copy the CAJEDIR source member and list the fieldnames you want on the
PRINT statement. See the chapter "Reports" for samples.
Information Fieldname Field Format Heading On On Sample
Length Report Reports
Record Info
member name
documentation DIRDSPN 8 DISPLY-KEY yes
MEMBR-NAME
staged JCL DIRMEMS 8 STAGING MEMBR-NAME
job name DIRJOBN 8 JOB yes
job number DIRJNUM 2 JOB NUMBER yes
library type DIRLIBS 1 LIBRARY TYPE
schedule name
documentation DIRSCDN 8 SCHEDULE yes
staging DIRSCDX 8 STAGING MEMBR-NAME yes
station ID DIRJSTN 2 STATION ID yes
last userid to DIRUUSER 8 LAST-UPDATE USERID yes
update
Library Info
number of
records DIRRECN 6 NUMBER-OF RECORDS yes
updates DIRUPDT 6 NUMBER-OF UPDATES yes
creation
date DIRCDATE 6 CREATION DATE yes
time DIRCTIME 6 CREATION TIME yes
last update
date DIRUDATE 6 LAST-UPDATE DATE yes
time DIRUTIME 6 LAST-UPDATE TIME yes
Appendix D. Advantage CA-Earl Reports D-41

D.6 Information from CAIAUDIT
D.6 Information from CAIAUDIT
Advantage CA-Earl reports can include any of the following information from the
CAIAUDIT file. To include this information on a report, copy the CAAUDCOD and
CAAUEF source members and list the field names you want on the PRINT statement.
See the chapter "Reports" for samples.
Information Fieldname Field Format Heading On On Sample
Length Report Reports
command or CAUSHSNM 8 COMMAND/ yes
schedule name
SCHD NAME
object or CAUSHJNM 8 OBJECT/ yes
job name
JOB NAME
job number CAUSHJNO 3 JOB NUMBER yes
workstation CAUSHWS 2 WS yes
message number CAUSHMNO 3 MSG NUMBER yes
Unicenter
CA-Scheduler user CAUSHSND 8 SCHD USER yes
Unicenter
CA-Scheduler user CAUSHNOD 8 SCHD NODE yes
message ID or CAUSHMSV 5 MSG ID/ yes
severity code
SEV CODE
long message text CAUSHTXT 8 MSG TEXT yes
short message text CAUSHMTX 26 MSG TEXT yes
command or CAUSHCMD 8 COMMAND/ yes
schedule name
SCHD NAME
object or CAUSHOBJ 8 OBJECT/ yes
job name
JOB NAME
command type CAUSHTYP 1 TYPE yes
database or
tracking
command class CAUSHCLS 1 CLASS yes
D-42 Unicenter CA-Scheduler Reference Guide, Part 2

D.6 Information from CAIAUDIT
Information Fieldname Field Format Heading On On Sample
Length Report Reports
internal indicators CAUSHIND 8 INDICATOR yes
long command text CAUSHDAT 8 COMMAND TEXT yes
short command text CAUSHCTX 8 COMMAND TEXT yes
response CAUSHRSP 8 RESPONSE yes
short or
long
Appendix D. Advantage CA-Earl Reports D-43

Appendix E. Event Codes
The event codes for Unicenter CA-Scheduler functions are listed following:
Code
CBD
CBI
CBM
CBU
CDD
CDI
CDU
CSD
CSI
CSU
CTD
CTI
CTU
MSG
RBD
RBM
RBU
RDU
RDD
RSD
RSU
RTD
RTI
Event Description
Database Display Commands
Invalid Database Commands
Database Maintenance Commands
Database Update Commands
Documentation Display Commands
Invalid Documentation Commands
Documentation Update Commands
Staging Display Commands
Invalid Staging Commands
Staging Update Commands
Tracking Display Commands
Invalid Tracking Commands
Tracking Update Commands
Scheduler Messages
Database Display Response
Database maintenance Response
Database Update Response
Documentation Update Response
Documentation Display Response
Staging Display Response
Staging Update Response
Tracking Display Response
Invalid Tracking Response
Appendix E. Event Codes E-1

Code
RTU
Event Description
Tracking Update Response
E-2 Unicenter CA-Scheduler Reference Guide, Part 2

Index
A
Abended Job Profile report 5-165, 5-181
Abended Job Schedule report 5-21
Accounting periods, conditions A-9
ADAY A-9
Adding
jobs 5-125
schedules 5-126
ADOM A-9
Advantage CA-Earl reports D-1
Alter STG Member (SCHD-STGE) C-12
Altering
JBR, example B-17
JCR, example B-20
JIR, example B-24
JMR, example B-23
JRC, example B-22
JRR, example B-26
resource records, example B-29
SBR, example B-7
SCR, example B-9
SIR, example B-13, B-14
SMR, example B-12
SRC, example B-11
stations, example B-2
userids, example B-4
AMOY A-9, A-10
Analyze Job report 5-6
Analyze Schedule report 5-10
AND, reserved word A-2
AT keyword
HOLD Job command 5-56
HOLD Schedule command 5-57
RELEASE Job command 5-73
RELEASE Schedule command 5-75
REQUEST Job command
forecast 5-122
simulation 5-76
REQUEST Schedule command
forecast 5-124
AT keyword (continued)
REQUEST Schedule command (continued)
simulation 5-78
RERUN Job command 5-79
RUN Job command
forecast 5-125
simulation 5-82
RUN schedule command
forecast 5-127
simulation 5-84
Audited Commands/Response report 5-231
Audited Commands/Text report 5-227
Audited Events report 5-225
Audited Messages report 5-229
Auditing events
codes E-1
AUTO SELECT 5-67
Automatic Console Reply
By Message Number report 5-155
Automatic Console Reply, By Schedule
report 5-153
Automatic Console Reports By Schedule
report 5-151
AUTOSEL keyword, OVERRIDE Schedule
command 5-67
AVGTIME keyword, OVERRIDE RESOURCE
command 5-62
AWOM A-10
B
Backlogged Schedules/Jobs report 5-93
Basic Job Information
By Schedule report 5-158
By Station report 5-160
Batch commands coding requirements 5-4
BrightStor CA-Dynam/T 5-43, 5-45
Index X-1

C
CA-Tape Manager 5-43, 5-45
CAAUE06 5-225
CAAUE07 5-227
CAAUE08 5-229
CAAUE09 5-231
CAIAUDIT
event codes E-1
printable fields D-42
reports and UPSI settings 5-225
CAIDEFD D-22
CAISTMD D-2
CAJDDIR D-39
CAJECNV0 D-29
CAJECNVS D-22
CAJECRI D-4
CAJEDIR D-41
CAJEGLBL D-5
CAJEJHR D-24
CAJEJM D-9
CAJEJTR D-32
CAJEPM D-1
CAJERA01 5-151
CAJERA02 5-153, 5-155
CAJERD01 5-208
CAJERD02 5-204
CAJERG01 5-222
CAJERG02 5-218
CAJERH01 5-175
CAJERH02 5-178
CAJERH03 5-167
CAJERH04 5-165
CAJERH05 5-171
CAJERH06 5-173
CAJERH07 5-169
CAJERM01 5-158
CAJERM02 5-160
CAJERM03 5-162
CAJERS01 5-194
CAJERS06 5-191
CAJERT01 5-197
CAJERT02 5-200
CAJERT03 5-186
CAJERT04 5-181
CAJERT06 5-188
CAJERT07 5-183
CAJERTD1 5-210
CAJESETD D-39
CAJESETG D-40
CAJESETH D-22
CAJESETM D-8
CAJESETS D-28
CAJESETT D-28
CAJESHR D-26
CAJESM D-17
CAJESTR D-36
CAJMBR D-40
CAJSDIR D-40
CAJUTIL0 commands
ANALYZE 5-6
EXCLUDE 5-53, 5-54, 5-118, 5-120
FORECAST 5-128
HOLD 5-56, 5-57
LIST 5-13
ONLY 5-59, 5-121
OVERRIDE 5-62
RELEASE 5-73, 5-75
REQUEST 5-76, 5-78, 5-122, 5-123
RERUN 5-79
RONLY 5-81
RUN 5-82, 5-84, 5-125, 5-126
SIMULATE 5-85
TAPEPULL GROUP 5-42
TAPEPULL JOB 5-44
Canceled Jobs report 5-183
CLASS keyword 5-42, 5-44
Closed Data Set report 5-23
Commands
editor C-1
forecast
EXCLUDE Job 5-118
EXCLUDE Schedule 5-120
FORECAST 5-115, 5-128
ONLY Schedule 5-121
REQUEST Job 5-122
REQUEST Schedule 5-123
RUN Job 5-125
RUN Schedule 5-126
summary 5-116
simulation
EXCLUDE Job 5-53
EXCLUDE Schedule 5-54
HOLD Job 5-56
HOLD Schedule 5-57
ONLY Schedule 5-59
OVERRIDE Job 5-60
OVERRIDE RESOURCE 5-62
OVERRIDE Schedule 5-67
OVERRIDE SHRRSR 5-68
OVERRIDE STATION 5-71
RELEASE Job 5-73
X-2 Unicenter CA-Scheduler Reference Guide, Part 2

Commands (continued)
simulation (continued)
RELEASE Schedule 5-75
REQUEST Job 5-76
REQUEST Schedule 5-78
RERUN Job 5-79
RUN Job 5-82
RUN Schedule 5-84
SIMULATE 5-49, 5-85
summary 5-50
Completed Job Profile report 5-167, 5-186
Completed Job Schedule report 5-25
Cpushut keyword, SIMULATE comand 5-86
Criteria vocabulary A-2
Cyclic scheduling 5-47, A-4
D
DAILY A-4
DASDnn keyword
OVERRIDE RESOURCE command 5-63
OVERRIDE SHRRSR command 5-69
DATASET installation option 5-25
Date Translation Report 5-29, 5-95
DATETABL installation option 5-96
DATETRAN 5-95
DATETYPE installation option 5-96
Day of
cycle A-4
month A-4
week A-7
DEFCLASS keyword, OVERRIDE RESOURCE
command 5-63
Defining
JBR, example B-15, B-16, B-17
JCR, example B-19, B-20
JIR, example B-24
JMR, example B-23
JRC, example B-21
JRR, example B-25
resource records, example B-27, B-28
SBR, example B-6, B-7
SCR, example B-8, B-9
SIR, example B-13
SMR, example B-12
SRC, example B-10
stations, example B-2
userids, example B-4
Deleting
JBR, example B-18
JCR, example B-21
Deleting (continued)
JIR, example B-25
JMR, example B-24
JOB, example B-18
JRC, example B-22
JRR, example B-26
resource records, example B-29
SBR, example B-8
SCR, example B-10
SMR, example B-12
SRC, example B-11
stations
example B-3
userids, example B-5
DEVUTIL 5-110, 5-112
DEXPAND command C-13
Displaying reserved-name variable parameter
values C-16
Documentation Directory And Member List
Report 5-204
Documentation Directory List Report 5-208
Documentation Selected By The Tracking File
Report 5-210
DOM keyword A-4
DOS keyword A-3
DPROMPT command C-16
Dprompt STG Member (SCHD-DPR) C-12
DRIVER installation option C-13, C-16
DSET command C-19
DSN keyword A-3
E
Editor
commands C-1
Input Area Commands C-3
Line Protection and Highlighting C-2
Prefix Area Commands C-5
Event codes
list E-1
reports 5-224
EVERYDAY keyword
OVERRIDE RESOURCE command 5-63
OVERRIDE SHRRSR command 5-69
SIMULATE command 5-86
Examples
ALTER
JBR B-17
JCR B-20
JIR B-24
JMR B-23
JRC B-22
Index X-3

Examples (continued)
ALTER (continued)
JRR B-26
resource records B-29
SBR B-7
SCR B-9
SIR B-13, B-14
SMR B-12
SRC B-11
stations B-2
userids B-4
DEFINE
JBR B-15, B-16, B-17
JCR B-19, B-20
JIR B-24
JMR B-23
JRC B-21
JRR B-25
resource records B-27, B-28
SBR B-6, B-7
SCR B-8, B-9
SIR B-13
SMR B-12
SRC B-10
stations B-2
userids B-4
DELETE
JBR B-18
JCR B-21
JIR B-25
JMR B-24
JOB B-18
JRC B-22
JRR B-26
resource records B-29
SBR B-8
SCR B-10
SMR B-12
SRC B-11
stations B-3
userids B-5
EXCLUDE Job command
forecast 5-118
simulation 5-53
EXCLUDE Schedule command
forecast 5-120
simulation 5-54
Excluding
forecast reports 5-128
jobs 5-53, 5-118
schedules 5-54, 5-120
Excrept keyword
FORECAST command 5-128
SIMULATE command 5-86
EXITPARM keyword, OVERRIDE RESOURCE
command 5-63
Expanding Unicenter CA-Driver procedures C-13
EXPERROR 5-114
F
FACTOR keyword
OVERRIDE Job command 5-60
OVERRIDE RESOURCE command 5-63
OVERRIDE Schedule command 5-67
File Status Report 5-31
FOR keyword
FORECAST command 5-129
SIMULATE command 5-86
Forced And Canceled Jobs report 5-169
Forecast
Commands
EXCLUDE Job 5-118
EXCLUDE Schedule 5-120
FORECAST 5-115, 5-128
ONLY Schedule 5-121
REQUEST Job 5-122
REQUEST Schedule 5-123
RUN Job 5-125
RUN Schedule 5-126
summary 5-116
overview 5-115
Reports
Job Summary 5-132
Predecessors Required For Jobs At Station
X 5-133
Resources Required For All Selected
Jobs 5-135
Resources Required For Jobs At Station
X 5-137
Run Book 5-138
Schedules/Jobs Selected For DD MM
YY 5-144
Schedules/Jobs Selected For Station X 5-147
storage requirements 5-116
FORECAST command 5-115, 5-128, 5-132
FromDate keyword
FORECAST command 5-129
SIMULATE command 5-87
FromTime keyword, SIMULATE command 5-87
X-4 Unicenter CA-Scheduler Reference Guide, Part 2

G
GBL A-3
H
HALT keyword, OVERRIDE STATION
command 5-72
HDAY keyword A-7
HOLD Job command 5-56
HOLD Schedule command 5-57
Holding
jobs 5-56
schedules 5-57
Holiday scheduling A-7
I
ID keyword, OVERRIDE STATION command 5-72
Including simulation reports 5-129
Incrept keyword
FORECAST command 5-129
SIMULATE command 5-87
Interval keyword, SIMULATE command 5-87
J
JCL
manipulation C-12
JNI file 5-43
JNO
keyword 5-44
HOLD Job command 5-56
OVERRIDE Job command 5-60
RELEASE Job command 5-74
RERUN Job command 5-79
JNO keyword
EXCLUDE Job command
forecast 5-118
simulation 5-53
REQUEST Job command
forecast 5-122
simulation 5-76
RUN Job command
forecast 5-125
simulation 5-82
Job
adding 5-82, 5-125
analyzing 5-6
Average Report 5-34
excluding 5-53, 5-118
History Report 5-35
Job (continued)
holding 5-56
listing 5-13
releasing 5-73
reports 5-2, D-9, D-24, D-32, D-41
requesting 5-76, 5-122
rerunning 5-79
Job Criteria By Schedule report 5-162
Job Summary report 5-132
L
Late Job Profile report 5-103, 5-171
LATEJOBS 5-103
LDEST keyword 5-42, 5-44
LEAPYEAR A-4
List Job report 5-13, 5-16
List Schedule report 5-16
List Station report 5-17
List Userid report 5-19
M
Maxtime keyword, SIMULATE command 5-88
Month of keyword
FORECAST command 5-129
SIMULATE command 5-88
Monthly scheduling A-4, A-7
N
NAME keyword 5-44
EXCLUDE Job command
forecast 5-118
simulation 5-53
EXCLUDE Schedule command
forecast 5-120
simulation 5-55
HOLD Job command 5-56
HOLD Schedule command 5-57
ONLY Schedule command
forecast 5-121
simulation 5-59
OVERRIDE Job command 5-60
OVERRIDE Schedule command 5-67
RELEASE Job command 5-73
RELEASE Schedule command 5-75
REQUEST Job command
forecast 5-122
simulation 5-76
REQUEST Schedule command
forecast 5-124
Index X-5

NAME keyword (continued)
REQUEST Schedule command (continued)
simulation 5-78
RERUN Job command 5-79
RONLY Schedule command simulation 5-81
RUN Job command
forecast 5-125
simulation 5-82
RUN Schedule command
forecast 5-127
simulation 5-84
NJE A-3
NOSAVE C-13
NOT A-2
O
OET keyword
OVERRIDE RESOURCE command 5-64
OVERRIDE SHRRSR command 5-70
ONLY Schedule command
forecast 5-121
simulation 5-59
OR A-2
OST keyword
OVERRIDE RESOURCE command 5-64
OVERRIDE SHRRSR command 5-70
Override
end time (OET) 5-63, 5-64, 5-70
start time (OST) 5-63, 5-64, 5-70
OVERRIDE Job command 5-60
OVERRIDE RESOURCE command 5-62
OVERRIDE Schedule command 5-67
OVERRIDE SHRRSR command 5-68
OVERRIDE STATION command 5-71
Overriding
resources 5-62
schedules 5-67
shared resources 5-68
P
Parentheses A-2
PARTnn keyword, OVERRIDE RESOURCE
command 5-64
Pending
Job Profile report 5-173, 5-188
Schedules Report 5-191
Periods A-9
PET keyword, OVERRIDE RESOURCE
command 5-65
POwerjnm keyword 5-42, 5-44
PRED A-2
Predecessor deadlock 5-8, 5-11
Predecessors Required For Jobs At Station X
report 5-133
PREDS 5-133
Procedure expansion online C-13
Production
end time (PET) 5-65
start time (PST) 5-65
PRTY keyword, TAPEPULL command 5-42, 5-44
PST keyword, OVERRIDE RESOURCE
command 5-65
R
RDnn A-7
RDT keyword, OVERRIDE RESOURCE
command 5-65
Reasons codes, reports 5-107, 5-133, 5-145
RECALL command C-20
Relative days A-7
RELEASE command
Job 5-73
Schedule 5-75
Releasing
jobs 5-73
schedules 5-75
Reports
Advantage CA-Earl
CAIAUDIT events 5-224
CAIAUDIT UPSI settings 5-225
Advantage CA-Earl Database
Automatic Console Reply By Message
Number 5-155
Automatic Console Reply By Schedule 5-153
Automatic Console Reports By
Schedule 5-151
Basic Job Information By Schedule 5-158
Basic Job Information By Station 5-160
Job Criteria By Schedule 5-162
source members D-1
Advantage CA-Earl Documentation Library
Documentation Directory and Member
List 5-204
Documentation Directory List 5-208
Documentation Selected By The Tracking
File 5-210
Advantage CA-Earl History File
Abended Job Profile 5-165
Completed Job Profile 5-167
Forced And Canceled Jobs 5-169
X-6 Unicenter CA-Scheduler Reference Guide, Part 2

Reports (continued)
Advantage CA-Earl History File (continued)
Late Job Profile 5-171
Pending Job Profile 5-173
Scheduled Job Status By Schedule 5-175
Scheduled Job Status By Station 5-178
Advantage CA-Earl Staging Library
Staged JCL Directory and Member List 5-218
Staged JCL Library Directory List 5-222
Advantage CA-Earl Tracking File
Abended Job Profile 5-181
Canceled Jobs 5-183
Completed Job Profile 5-186
Pending Job Profile 5-188
Pending Schedules Report 5-191
Schedule Status 5-194
Scheduled Job Status By Schedule 5-197
Scheduled Job Status By Station 5-200
Analysis and Display
Analyze Job 5-6
Analyze Schedule 5-10
List Job 5-13
List Schedule 5-16
List Station 5-17
List Userid 5-19
Batch Versions of Online Reports
Abended Job Schedule 5-21
Closed Data Set 5-23
Completed Job Schedule 5-25
Date Translation Report 5-29
File Status Report 5-31
Job Average Report 5-34
Job History Report 5-35
Successor Chain List 5-38
CAIAUDIT File
Audited Commands/Response 5-231
Audited Commands/Text 5-227
Audited Events 5-225
Audited Messages 5-229
Forecast
Job Summary 5-132
Predecessors Required For Jobs At Station
X 5-133
Resources Required For All Selected
Jobs 5-135
Resources Required For Jobs At Station
X 5-137
Run Book 5-138
Schedules/Jobs Selected For DD MM
YY 5-144
Schedules/Jobs Selected For Station X 5-147
Reports (continued)
overview 5-1
Simulation
Backlogged Schedules/Jobs 5-93
Date Translation Report 5-95
Late Job Profile 5-103
Resources Required For All Selected
Jobs 5-105
Schedules/Jobs Selected For DD MM
YY 5-107
Simulated Device Utilization 5-110
Simulated Execution Schedule 5-111
Simulated Shared Device Utilization 5-112
Simulated Unit Utilization 5-112
Tracking File Job Start Errors 5-114
REQUEST
JOB command
forecast 5-122
simulation 5-76
Schedule command
forecast 5-123
simulation 5-78
REQUESTED keyword A-4
RERUN
command
Job 5-79
keyword 5-44
RERun keyword 5-42
RESALL 5-105, 5-135
Reserved words A-2
Reserved-name variable parameters for Unicenter
CA-Driver C-16, C-19
Resources
Required
For All Selected Jobs report 5-105, 5-135
For Jobs At Station X report 5-137
Resources, station overriding 5-62
RESSTN 5-137
RESTART keyword, OVERRIDE STATION
command 5-72
REVISE keyword 5-44
FORECAST command 5-129
SIMULATE command 5-88
RFT keyword, SIMULATE command 5-88
RONLY Schedule command 5-81
Routing delay time (RDT) 5-65
RTT keyword, SIMULATE command 5-89
RUN
command
Job forecast 5-125
Job simulation 5-82
Schedule forecast 5-126
Index X-7

RUN (continued)
command (continued)
Schedule simulation 5-84
RUNBOOK 5-138
RUNBOOK report 5-138
Running
jobs 5-82
schedules 5-84
S
SCD keyword A-2
Schedule
adding 5-84, 5-126
analyzing 5-10
changing 5-67
excluding 5-54, 5-120
holding 5-57
keyword
EXCLUDE Job command forecast 5-118
EXCLUDE Job command, simulation 5-53
HOLD Job command 5-56
OVERRIDE Job command 5-61
RELEASE Job command 5-74
REQUEST Job command forecast 5-122
REQUEST Job command simulation 5-77
RERUN Job command 5-80
RUN Job command forecast 5-125
RUN Job command simulation 5-82
listing 5-16
releasing 5-75
reports D-17, D-26, D-36
requesting 5-78, 5-123
Status report 5-194
SCHEDULE keyword 5-44
Scheduled Job Status
By Schedule report 5-175, 5-197
By Station report 5-178, 5-200
Schedules/Jobs Selected For DD MM YY
report 5-107, 5-144
Schedules/Jobs Selected For Station X report 5-147
Scheduling
cyclic A-4
daily A-4
holiday A-7
monthly A-4, A-7
period A-9
relative day A-7
weekly A-4, A-7
yearly A-6
SELECTED 5-107, 5-144
SIMDAY keyword
EXCLUDE Job command
forecast 5-119
simulation 5-53
EXCLUDE Schedule command
forecast 5-120
simulation 5-55
HOLD Job command 5-56
HOLD Schedule command 5-58
ONLY Schedule command
forecast 5-121
simulation 5-59
RELEASE Job command 5-74
RELEASE Schedule command 5-75
REQUEST Job command
forecast 5-123
simulation 5-77
REQUEST Schedule command
forecast 5-124
simulation 5-78
RERUN Job command 5-80
RONLY Schedule command simulation 5-81
RUN Job command
forecast 5-125
simulation 5-83
RUN Schedule command
forecast 5-127
simulation 5-84
SIMEXEC 5-111
SIMULATE command 5-49, 5-85
Simulated Device Utilization report 5-110
Simulated Execution Schedule report 5-111
Simulated Shared Device Utilization report 5-112
Simulated Unit Utilization report 5-112
Simulation
commands
EXCLUDE Job 5-53
EXCLUDE Schedule 5-54
HOLD Job 5-56
HOLD Schedule 5-57
ONLY Schedule 5-59
OVERRIDE Job 5-60
OVERRIDE RESOURCE 5-62
OVERRIDE Schedule 5-67
OVERRIDE SHRRSR 5-68
OVERRIDE STATION 5-71
RELEASE Job 5-73
RELEASE Schedule 5-75
REQUEST Job 5-76
REQUEST Schedule 5-78
RERUN Job 5-79
X-8 Unicenter CA-Scheduler Reference Guide, Part 2

Simulation (continued)
commands (continued)
RONLY Schedule 5-81
RUN Job 5-82
RUN Schedule 5-84
SIMULATE 5-49, 5-85
summary 5-50
TAPEPULL GROUP 5-42
TAPEPULL JOB 5-44
overview 5-46
Reports
Backlogged Schedules/Jobs 5-93
Date Translation Report 5-95
Late Job Profile 5-103
Resources Required For All Selected
Jobs 5-105
Schedules/Jobs Selected For DD MM
YY 5-107
Simulated Device Utilization 5-110
Simulated Execution Schedule 5-111
Simulated Shared Device Utilization 5-112
Simulated Unit Utilization 5-112
Tracking File Job Start Errors 5-114
storage requirements 5-51
STAGE keyword 5-43
TAPEPULL JOB command 5-44
Staged JCL Directory and Member List
Report 5-218
Staged JCL Library Directory List Report 5-222
Staging editor commands C-12
START A-2
Station
listing 5-17
overriding resources 5-62
where jobs and schedules run 5-147
STATION keyword
EXCLUDE Job command
forecast 5-119
simulation 5-53
FORECAST command 5-130
HOLD Job command 5-56
OVERRIDE
Job command 5-61
RESOURCE command 5-62
Schedule command 5-67
SHRRSR command 5-69
RELEASE Job command 5-74
REQUEST Job command
forecast 5-123
simulation 5-77
RUN Job command
forecast 5-126
STATION keyword (continued)
RUN Job command (continued)
simulation 5-83
SIMULATE command 5-89
Storage requirements
forecasting 5-116
simulation 5-51
SUBID keyword
OVERRIDE RESOURCE command 5-62
OVERRIDE STATION command 5-72
Successor Chain List 5-38
SUMMARY option for forecasts 5-132
SYSID keyword
OVERRIDE RESOURCE command 5-62
OVERRIDE STATION command 5-72
T
TAPEnn keyword
OVERRIDE RESOURCE command 5-65
OVERRIDE SHRRSR command 5-70
TAPEPULL
command
GROUP 5-42
Job 5-44
option
BrightStor CA-Dynam/T 5-85
CA-SYSTEM/MANAGER 5-85
SIMULATE command 5-85
Traceopt keyword, SIMULATE command 5-89
Tracking file D-28
Tracking File Job Start Errors report 5-114
U
Unicenter CA-Driver
online procedure expansion C-13
parameters C-16, C-19
UNIT with simulation commands 5-65
UNITnn keyword, OVERRIDE RESOURCE
command 5-65
UNITUTIL 5-112
Update keyword, SIMULATE command 5-89
UPSI settings, CAIAUDIT reports 5-225
URnn keyword
OVERRIDE RESOURCE command 5-65
OVERRIDE SHRRSR command 5-70
Userid list 5-19
Index X-9

V
Variable parameter, reserved-name C-16, C-19
Vocabulary A-2
W
WDAY keyword A-7
WDOM keyword A-7
WDOW keyword A-7
WEEKDAY keyword A-4
WEEKEND keyword A-4
Weekly scheduling A-6, A-7
Workday A-7
WWOM keyword A-7
WWOYkeyword A-7
X
XDAY A-9
XDOM A-9
XMOY A-9, A-10
XWOM A-10
Y
Yearly scheduling A-6
X-10 Unicenter CA-Scheduler Reference Guide, Part 2