Unicenter CA-Jobtrac Job

 

Management

Operator Guide
3.5 SP5

K00905-6E
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.

Sixth Edition, December 2004

 2004 Computer Associates International, Inc.

All rights reserved.

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

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

1.1 Summary of Revisions in the Sixth Edition . . . . . . . . . . . . . . . . 1-2
1.2 Summary of Revisions in the Third Edition . . . . . . . . . . . . . . . . 1-3
1.3 Summary of Revisions in the Second Edition . . . . . . . . . . . . . . . 1-4
1.4 Summary of Revisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.4.1 Product Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5
1.4.2 Documentation Changes . . . . . . . . . . . . . . . . . . . . . . . . . 1-9
1.5 Reading Syntax Diagrams . . . . . . . . . . . . . . . . . . . . . . . . . 1-10
1.6 Accessing CA-Jobtrac . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-16
1.7 Exiting CA-Jobtrac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-18
1.7.1 Using the END PF Key . . . . . . . . . . . . . . . . . . . . . . . . 1-18
1.8 CA-Jobtrac Primary Panel . . . . . . . . . . . . . . . . . . . . . . . . . . 1-19
1.8.1 Description of the CA-Jobtrac Primary Panel . . . . . . . . . . . 1-19
1.8.2 Issuing Commands from the CA-Jobtrac Primary Panel . . . . . 1-19
1.8.3 Defining a Default Search Command . . . . . . . . . . . . . . . . 1-21
1.9 CA-Jobtrac User Profile Panel . . . . . . . . . . . . . . . . . . . . . . . 1-22
1.9.1 Displaying the CA-Jobtrac User Profile Panel . . . . . . . . . . . 1-22
1.9.2 Description of the CA-Jobtrac User Profile Panel . . . . . . . . . 1-23
1.10 Determining Your Authorization Level . . . . . . . . . . . . . . . . . 1-25
1.10.1 Displaying the Authorization Profile Panel . . . . . . . . . . . . 1-25
1.10.2 Description of the Authorization Profile Panel . . . . . . . . . . 1-26
1.10.3 Adding or Removing Locations . . . . . . . . . . . . . . . . . . . 1-30
1.11 Description of the CA-Jobtrac Status Display . . . . . . . . . . . . . 1-34
1.12 Changing Displays and Executing Commands . . . . . . . . . . . . 1-36
1.12.1 Using the COMMAND Field . . . . . . . . . . . . . . . . . . . . 1-36
1.12.2 Using Strings of Search Keys . . . . . . . . . . . . . . . . . . . . 1-38
1.12.3 Using Line Commands . . . . . . . . . . . . . . . . . . . . . . . . 1-39
1.13 Using Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-40
1.14 Displaying the Scheduled Event Display Panel . . . . . . . . . . . . 1-41
1.14.1 Description of the Scheduled Event Display Panel . . . . . . . 1-41
1.15 Defining Your Own Program Function Keys . . . . . . . . . . . . . . 1-43
1.15.1 User Options Panel . . . . . . . . . . . . . . . . . . . . . . . . . . 1-43
1.15.2 BYTIME AND BYNAME Sort Display . . . . . . . . . . . . . . . 1-46

Chapter 2. Using Operator Commands . . . . . . . . . . . . . . . . . . . . 2-1

2.1 Documenting IPLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.1.1 IPL Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
2.1.2 Replying to IPL Messages . . . . . . . . . . . . . . . . . . . . . . . . 2-3
2.2 Starting a Scan Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

Contents iii
 2.2.1 The Start JOBTRAC Command . . . . . . . . . . . . . . . . . . . . . 2-4
2.3 Stopping a Scan Task . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
2.4 Using Task Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
2.4.1 Modifying the Current Schedule . . . . . . . . . . . . . . . . . . . . 2-7
2.4.2 Changing Target Times for Scheduled Events . . . . . . . . . . . 2-12
2.4.3 Controlling a CA-Jobtrac Task . . . . . . . . . . . . . . . . . . . . 2-14
2.4.4 Other Task Commands . . . . . . . . . . . . . . . . . . . . . . . . 2-15
2.4.5 Performance Options . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22
2.4.6 Controlling CA-Jobtrac Internals . . . . . . . . . . . . . . . . . . . 2-23
2.5 Monitoring Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
2.5.1 Enqueue Research . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-25
2.5.1.1 Finding and Sorting Information . . . . . . . . . . . . . . . . 2-26
2.5.2 Enqueue Research Commands . . . . . . . . . . . . . . . . . . . . 2-28
2.5.2.1 Using the Enqueue Research Commands . . . . . . . . . . . 2-28
2.5.2.2 Available Commands . . . . . . . . . . . . . . . . . . . . . . . 2-28
2.5.3 DASD Space Analysis . . . . . . . . . . . . . . . . . . . . . . . . . 2-31
2.5.3.1 DASD Space Analysis Command . . . . . . . . . . . . . . . . 2-32
2.5.3.2 DASD Space Analysis Panels . . . . . . . . . . . . . . . . . . 2-33
2.5.3.3 Finding and Sorting DASD Information . . . . . . . . . . . . 2-37
2.5.4 Change Audit History . . . . . . . . . . . . . . . . . . . . . . . . . 2-40
2.5.4.1 Change Audit History Commands . . . . . . . . . . . . . . . 2-40
2.5.4.2 Finding and Sorting Events . . . . . . . . . . . . . . . . . . . 2-43
2.5.5 IPL History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
2.5.5.1 IPL History Command . . . . . . . . . . . . . . . . . . . . . . 2-45
2.5.5.2 Finding and Sorting IPL Records . . . . . . . . . . . . . . . . 2-47
2.5.6 System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
2.5.6.1 System Status Command . . . . . . . . . . . . . . . . . . . . . 2-49

Chapter 3. Monitoring the Current Schedule . . . . . . . . . . . . . . . . . 3-1

3.1 Event Execution Detail Panel . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
3.1.1 Description of the Event Execution Detail Panel . . . . . . . . . . 3-2
3.2 NJE Execution Detail Panel . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9
3.2.1 Description of the NJE Execution Detail Panel . . . . . . . . . . . . 3-9
3.3 Cross Node Query-Criteria Selection Panel . . . . . . . . . . . . . . . 3-13
3.3.1 Description of the Cross Node Query-Criteria Selection Panel . 3-13
3.4 Cross Node Query Panel . . . . . . . . . . . . . . . . . . . . . . . . . . 3-17
3.4.1 Description of the Cross Node Query Panel . . . . . . . . . . . . 3-17
3.4.2 Finding and Sorting Events . . . . . . . . . . . . . . . . . . . . . . 3-20
3.5 Environmental Dependencies Panel . . . . . . . . . . . . . . . . . . . . 3-22
3.5.1 Description of the Environmental Dependencies Panel . . . . . 3-22
3.6 Business Group Status Panel . . . . . . . . . . . . . . . . . . . . . . . . 3-25
3.6.1 Description of the Business Group Status Panel . . . . . . . . . . 3-25
3.6.2 Finding and Sorting Events . . . . . . . . . . . . . . . . . . . . . . 3-27
3.7 Event History Display Panel . . . . . . . . . . . . . . . . . . . . . . . . 3-30
3.7.1 Description of the Event History Display Panel . . . . . . . . . . 3-31
3.7.2 Finding and Sorting Events . . . . . . . . . . . . . . . . . . . . . . 3-34
3.8 Event History Detail Panel . . . . . . . . . . . . . . . . . . . . . . . . . 3-36
3.8.1 Description of the Event History Detail Panel . . . . . . . . . . . 3-36
3.9 Missing Events Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42
3.9.1 Description of the Missing Events Panel . . . . . . . . . . . . . . 3-42
3.9.2 Line Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43

iv Operator Guide
 3.9.3 Finding Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43
3.9.4 Excluding Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-45
3.10 Volume Pull List Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-46
3.10.1 Description of the Volume Pull List Panel . . . . . . . . . . . . 3-47
3.10.2 Finding and Sorting Data Sets . . . . . . . . . . . . . . . . . . . . 3-48
3.11 Argument Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50

Chapter 4. Adding Events to the Current Schedule . . . . . . . . . . . . . 4-1

4.1 Schedules and Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.1.1 Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.1.2 The Current Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
4.1.3 Methods for Adding Events . . . . . . . . . . . . . . . . . . . . . . . 4-3
4.1.4 Methods Not Described in This Chapter . . . . . . . . . . . . . . . 4-3
4.2 The ADD Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-4
4.2.1 ADD Command Explained . . . . . . . . . . . . . . . . . . . . . . . 4-5
4.2.2 Using the ADD Command . . . . . . . . . . . . . . . . . . . . . . . 4-8
4.3 The RUN Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
4.3.1 RUN Command Explained . . . . . . . . . . . . . . . . . . . . . . 4-11
4.3.2 Using the RUN Command . . . . . . . . . . . . . . . . . . . . . . 4-14
4.4 The Event/Jobstream Addition Panel . . . . . . . . . . . . . . . . . . . 4-16
4.4.1 Displaying the Event/Jobstream Addition Panel . . . . . . . . . 4-17
4.4.2 Using the Event/Jobstream Addition Panel . . . . . . . . . . . . 4-22
4.5 Using Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-24
4.5.1 Using Schedules to Update the Current Schedule . . . . . . . . . 4-26
4.6 The Batch Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-28
4.6.1 Using the Batch Method . . . . . . . . . . . . . . . . . . . . . . . . 4-29
4.7 The AUTO-SCHD Feature . . . . . . . . . . . . . . . . . . . . . . . . . 4-30
4.7.1 Codes Used with AUTO-SCHD . . . . . . . . . . . . . . . . . . . 4-31
4.7.2 Sample SCL/JCL for AUTO-SCHD Jobs . . . . . . . . . . . . . . 4-34

Chapter 5. Modifying the Current Schedule . . . . . . . . . . . . . . . . . 5-1

5.1 Scheduled Event Display Panel . . . . . . . . . . . . . . . . . . . . . . . 5-2
5.1.1 Event Name Prefix Search (J=) Command . . . . . . . . . . . . . . 5-3
5.1.2 Abend Search (A=) Command . . . . . . . . . . . . . . . . . . . . . 5-4
5.1.3 Add Location (ADDLOC=) Command . . . . . . . . . . . . . . . . 5-5
5.1.4 Business Group Search (B=) Command . . . . . . . . . . . . . . . . 5-6
5.1.5 Default Display (D) Command . . . . . . . . . . . . . . . . . . . . . 5-7
5.1.6 Dependency Search (D=) Command . . . . . . . . . . . . . . . . . . 5-9
5.1.7 Date Parameter (DATE=) Command . . . . . . . . . . . . . . . . 5-11
5.1.8 FIND Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13
5.1.9 SORT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-15
5.1.10 Search Key (K=) Command . . . . . . . . . . . . . . . . . . . . . 5-16
5.1.11 Reset/Update and Display Entire Schedule (RALL) Command 5-18
5.1.12 Continuous Schedule Display (@INT) Command . . . . . . . . 5-19
5.1.13 Remove Location (REMLOC=) Command . . . . . . . . . . . . 5-20
5.1.14 Process Period Search (PP=) Command . . . . . . . . . . . . . . 5-21
5.1.15 Shift Search (SHIFT) Command . . . . . . . . . . . . . . . . . . . 5-22
5.1.16 Time Search (T=) Command . . . . . . . . . . . . . . . . . . . . . 5-23
5.1.17 Description of the Scheduled Event Display Panel . . . . . . . 5-24

Contents v
 5.1.18 Using the Scheduled Event Display to Modify the Current
Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33
5.2 Scheduled Event Detail Panel . . . . . . . . . . . . . . . . . . . . . . . 5-35
5.2.1 Displaying a Scheduled Event Detail Panel . . . . . . . . . . . . 5-35
5.2.2 Select for Detail Display (S) Command . . . . . . . . . . . . . . . 5-35
5.2.3 Description of the Scheduled Event Detail Panel . . . . . . . . . 5-36
5.2.4 Using the Scheduled Event Detail Panel . . . . . . . . . . . . . . 5-44
5.3 Scheduled Event Network Panel . . . . . . . . . . . . . . . . . . . . . . 5-47
5.3.1 Displaying the Panel . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47
5.3.2 Finding and Sorting Events . . . . . . . . . . . . . . . . . . . . . . 5-49
5.4 Step Condition Code Exceptions Panel . . . . . . . . . . . . . . . . . . 5-52
5.4.1 Displaying a Step Condition Code Exceptions Panel . . . . . . . 5-52
5.4.2 Display Step Condition Code Exceptions Panel (CC) Command 5-52
5.4.3 Description of the Step Condition Code Exceptions Panel . . . . 5-53
5.4.4 Changing Condition Codes for an Event on the Current Schedule 5-54
5.5 Manual Action Detail Panel . . . . . . . . . . . . . . . . . . . . . . . . 5-57
5.5.1 Displaying a Manual Action Detail Panel . . . . . . . . . . . . . 5-57
5.5.2 Display Manual Action Detail Panel (MANUAL) Command . . 5-58
5.5.3 Description of the Manual Action Detail Panel . . . . . . . . . . 5-58
5.5.4 Using the Manual Action Detail Panel to Remove a Manual
Dependency Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-60
5.6 Edit Argument Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61
5.7 Remote System Credentials Panel . . . . . . . . . . . . . . . . . . . . . 5-62
5.8 CPM Flow Information Panel . . . . . . . . . . . . . . . . . . . . . . . 5-64
5.9 JCL Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65
5.9.1 Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66
5.9.2 Displaying/Editing an Event's Production JCL . . . . . . . . . . 5-66
5.9.3 Display/Edit Production JCL (JCL) Command . . . . . . . . . . 5-66
5.9.4 Displaying/Editing an Event's Temporary-use JCL . . . . . . . . 5-69
5.9.5 Display/Edit Temporary-use JCL (TEMP) Command . . . . . . 5-70
5.9.6 Automatic JCL Checking . . . . . . . . . . . . . . . . . . . . . . . 5-71
5.10 SCL Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72
5.10.1 Displaying/Editing a Schedule's SCL . . . . . . . . . . . . . . . 5-72
5.10.2 Display/Edit Schedule (SCL) Command . . . . . . . . . . . . . 5-72
5.11 Using the EDIT Command to Edit JCL or SCL . . . . . . . . . . . . 5-74
5.11.1 EDIT Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75
5.12 Removing a View Documentation Dependency Code . . . . . . . . 5-76
5.12.1 Display Documentation (DOC or ?) Command . . . . . . . . . 5-77
5.13 Other Commands Used to Monitor or Modify . . . . . . . . . . . . 5-79

Chapter 6. Managing Sysouts . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

6.1 Functions of the Sysout Capture and Archival Subsystem . . . . . . . 6-2
6.1.1 Sysout Class Parameters . . . . . . . . . . . . . . . . . . . . . . . . . 6-3
6.1.2 Proper Use of Sysout Capture . . . . . . . . . . . . . . . . . . . . . 6-4
6.1.3 How the Sysout Capture and Archival Subsystem Processes
Sysouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
6.1.4 Other Sysout Capture and Archival Subsystem Actions . . . . . . 6-6
6.2 Displaying Sysout Listings and Sysouts . . . . . . . . . . . . . . . . . . 6-7
6.2.1 Sysout Capture Browse (O) Command . . . . . . . . . . . . . . . . 6-7
6.2.2 Sysout Capture Facility Menu . . . . . . . . . . . . . . . . . . . . . 6-9
6.2.3 Sysout Capture Panel . . . . . . . . . . . . . . . . . . . . . . . . . . 6-10

vi Operator Guide
 6.2.4 Finding and Sorting Events . . . . . . . . . . . . . . . . . . . . . . 6-13
6.2.5 Using the Sysout Capture Panel . . . . . . . . . . . . . . . . . . . 6-15
6.2.6 Sysout Archive Index Display . . . . . . . . . . . . . . . . . . . . 6-18
6.3 Reloading Archived Sysouts . . . . . . . . . . . . . . . . . . . . . . . . 6-23
6.3.1 The GJTRVRLD Procedure . . . . . . . . . . . . . . . . . . . . . . 6-23
6.3.2 Scheduling an Event to Reload Sysouts . . . . . . . . . . . . . . . 6-23
6.3.3 Displaying Sysouts Captured by CA-View . . . . . . . . . . . . . 6-25

Chapter 7. Restarting/Rerunning Events . . . . . . . . . . . . . . . . . . . 7-1

7.1 Setting Up and Scheduling an Event Rerun . . . . . . . . . . . . . . . . 7-2
7.1.1 Operator Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
7.1.2 Alternate Event Submission . . . . . . . . . . . . . . . . . . . . . . . 7-3
7.1.3 Using AUTO-SCHD to Track a Manually Submitted Event . . . . 7-4
7.1.4 Using the Event's Current Status to Determine CA-Jobtrac Actions 7-5
7.2 Rerunning A Schedule . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
7.2.1 @RERUN Global Control Record . . . . . . . . . . . . . . . . . . . . 7-6
7.2.2 Using the @RERUN Global Control Record . . . . . . . . . . . . . 7-7

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . X-1

Contents vii
Chapter 1. Introduction

This guide serves as the primary reference for the operator after installation of
Unicenter® CA-Jobtrac® Job Management (hereafter referred to as CA-Jobtrac).

Chapter 1. Introduction 1-1

1.1 Summary of Revisions in the Sixth Edition

1.1 Summary of Revisions in the Sixth Edition

The sixth edition of this guide includes these changes (see revision marks in
the margins):
■ TRAC310W is issued if no RESOURCE file is available. CA-Jobtrac
continues processing. For more information, see 2.2.1, “The Start JOBTRAC
Command” and 2.4.4, “Other Task Commands.”
■ The JOBID can be up to seven digits on the Sysout Archive Index Display
panel.

1-2 Operator Guide

 1.2 Summary of Revisions in the Third Edition

1.2 Summary of Revisions in the Third Edition

The third edition of this guide includes these changes (see revision marks in
the margins):
■ The explanation of Critical Path Monitoring changed in 1.4.1, “Product
Changes.” The new CA Critical Path Monitor Version 3 User Guide is
included in the documentation replacing a previous edition.
■ The Edit JCL dependency row of the table changed in “Deps.” For more
information, see 4.4.1, “Displaying the Event/Jobstream Addition Panel.”
■ We made some changes to the first two paragraphs of 5.9, “JCL Handling.”
■ We changed the A and D commands and added a note to “Line
Commands.” For more information, see 5.13, “Other Commands Used to
Monitor or Modify.”

Chapter 1. Introduction 1-3

1.3 Summary of Revisions in the Second Edition

1.3 Summary of Revisions in the Second Edition

The second edition of this guide includes these changes (see revision marks in
the margins):
■ We made some changes to QUECK and SYSCK in 2.4.5, “Performance
Options.”
■ The correct character is ">" for AUTO-SCHD. See 4.7, “The AUTO-SCHD
Feature” for more information.

1-4 Operator Guide

 1.4 Summary of Revisions

1.4 Summary of Revisions

This topic explains changes to CA-Jobtrac and to the documentation.

1.4.1 Product Changes

Version 3.5 of CA-Jobtrac contains the following new features:
■ Critical Path Monitoring
| CA-Jobtrac supports the definition and monitoring of critical job flows
| within the CA-Jobtrac workload. The Critical Path Monitor is distributed
| with CA-Jobtrac and is documented in the CA Critical Path Monitor Version
| 3 User Guide. Using the CPM component, you can track your job flows and
| estimate the completion time for the flow of jobs. The estimates are based
| on historical run times. These estimates, along with individual job status,
| are used to determine the status for the entire flow. CPM automatically
| determines the critical path in a flow and will recalculate the estimated
| completion time as jobs complete or if the critical path shifts due to an
| abnormally long running job or a job failure that introduces a significant
| delay. CPM helps you monitor your production batch environment and
| provide your users with "when will it be done" information when
| problems occur.
■ Two-character Resource Codes
The resource codes available in CA-Jobtrac have been expanded by
allowing for two-character codes. In most cases, this was implemented
without requiring changes to your existing resources definition. CA-Jobtrac
still supports the R= referback for single character resources in the
RESOURCE member. Two affected areas require changes if you are using
these features: @JOBTRAC and the REXIT user exit.
@JOBTRAC is used from CA-GSS and GJTRABTR uses the RMG()
parameter to specify the resources codes. The format of the parameter has
changed to support the two-character codes. Blanks must now separate the
codes if multiple codes are entered. For example, codes a, b, and c would
have previously been specified as RMG(abc). This needs to be changed to
RMG(a b c). Also the returned stack entry for resources, RSMG, returns the
codes in a blank separated list, instead of as a single value. Previously, the
entry would have read:
RSMG ABC
Now it reads:
RSMG A B C

Chapter 1. Introduction 1-5

1.4 Summary of Revisions

The REXIT resource exit needs to be altered to accommodate the

two-character resources. The @RSOURCE macro that maps the resource
has changed to define the field RSCODE as two characters. If your exit
examines this code, you need to make the appropriate changes to support
the new format. At a minimum, the exit requires a reassembly to include
the new @RSOURCE macro format.
■ UNIX System Services Interface
The OS/390 UNIX System Services (USS) CA-Jobtrac interface allows
communication with CA-Jobtrac from the USS environment. The interface
can be called directly from the UNIX shell or from the IBM USS batch
interface (BPXBATCH).
■ Workload Management and CA-Jobtrac
CA-Jobtrac interfaces in two ways with IBM's Workload Manager (WLM).
First, a WLM scheduling environment may optionally be inserted into JCL
during submission. Second, a WLM scheduling resource may be set ON
when CA-Jobtrac begins execution and OFF when CA-Jobtrac terminates.
The WLM scheduling environment and WLM scheduling resource may be
used to limit on which systems jobs execute, or even what CPU resources
are assigned to jobs.
See the Extended Scheduling Services Guide for more information.
■ ARM
To improve recovery capabilities in CA-Jobtrac, support for IBM's
Automatic Restart Management Function is included in this version.
CA-Jobtrac registers with ARM during initialization and deregisters at
normal termination. A new initialization keyword, ARM=, can be used to
specify abends that should not be restarted, which causes CA-Jobtrac to
deregister from ARM if they occur. Also, the ARM= keyword allows for
disabling the ARM support. This new support provides increased
recoverability for CA-Jobtrac.
■ CA-Earl Report Writing
Support for the CA-Earl Report Writer product is included in this version.
This common component is distributed with Unicenter TNG Framework
for OS/390 and can be used to write customized reports from the
CA-Jobtrac checkpoint and history files. Sample reports are provided.
■ Cross-Platform External Tracking
CA-Jobtrac may be used to track external events (JOBINIT, JOBTERM, and
DSCLOSE) on remote platforms running Unicenter TNG or CA-Jobtrac
Agent that do not originate with CA-Jobtrac. When a specified event is
detected, an associated CA-Jobtrac command will be issued.

1-6 Operator Guide

 1.4 Summary of Revisions

■ DYNAMLOC Concatenations
The DYNAMLOC facility for dynamically allocating the CA-Jobtrac
location data sets has been enhanced to allow for data sets to be
concatenated to the location DDNAMEs.
■ Enhanced SCL LOAD Syntax Checking
In the SCL column 58, which was not previously used, the presence of any
character in this column causes the SCL LOAD to ABORT. The PROCESS
PERIOD field is now syntax checked for valid process periods. On an IP
(input) parameter, the NODE statement is checked to ensure only one
NODE statement is found.
■ Cyclic Calendar Batch Load Utility
To allow you change multiple cyclic calendars at one time, a new utility
for updating the Cyclic Calendars (GJTRCYCL) in batch is being included
in this version. This utility reduces the time required when updating a
large number of calendars. See the Schedule Creation Guide for details.
■ Other New Options
– AMRLCNT
Allows you to specify the limit for processing of duplicate messages by
the CA-Jobtrac Automatic Message Replies (AMR) feature. This value
defines the maximum number of times a message is processed before
the messages are considered in a loop and processing for the messages
is terminated.
– CAPDMPS
Allows for system dump output to be captured by the CA-Jobtrac
sysout capture feature. Normally, dumps are not stored on the sysout
capture file.
– DISABLE
Allows for CA-Jobtrac ISPF line commands to be disabled, effectively
removing the command from the online system.
– DUMPUJV
Allows for suppression of dumps that are taken in the CA-Jobtrac
IEFUJV exit due to problems accessing the CA-Jobtrac checkpoint.
– JCLTABL
Specifies the maximum number of lines of JCL per JOB.
– JMFTABLE
Allows you to set the size of the JCL Modification Table (JMF) to meet
your needs.

Chapter 1. Introduction 1-7

1.4 Summary of Revisions

– RAMAXCC
Allows you to set the MAXCC default for jobs that are added using
the RUN or ADD CA-Jobtrac ISPF commands. Besides a numeric
value, you can specify N to indicate no condition code checking should
be done.
– TNDOVLP
Signals the CA-Jobtrac schedule load process whether to consider a
TIME/DATE overlap as an error.
■ SMP/E Environment Changes to Conform to Computer Associates
Standards
The target and distribution libraries for CA-Jobtrac now conform to the
Computer Associates format. Also, reworking the SMP/E structure placed
all components in a single CSI, rather than in three CSIs. The changes in
the data set names are listed below:

CA-Jobtrac 3.4 Name CA-Jobtrac 3.5 Name

CHD34CLS CHD35CLD
CHD34DBR CHD35XLD
CHD34INS None, CHD35XLD, and CHD35CLD
CHD34LIB CHD35LLD
CHD34MAC CHD35XLD
CHD34MLI CHD35MLD
CHD34PLI CHD35PLD
TRACLIB CAILIB
TRACCLST CAICLIB
DBRMLIB CAIMAC
TRACINST SAMPJCL, CAIMAC, and CAICLIB
TRACMAC CAIMAC
TRACMLIB CAIISPM
TRACPLIB CAIISPP
TRACPARM PPOPTION

1-8 Operator Guide

 1.4 Summary of Revisions

1.4.2 Documentation Changes

The documentation for CA-Jobtrac Version 3.5 differs from previous versions
as follows:
■ The documentation set has been engineered to take advantage of the latest
technology for online viewing, keyword searching, book marking, and
printing. This set contains a hardcopy Getting Started guide and Version 3.5
of CA-Jobtrac for OS/390 documentation in both IBM BookManager and
Adobe Acrobat Reader format on the tape.
■ The Getting Started guide replaces the CA-Jobtrac Installation and
Maintenance Guide.
| ■ The CA Critical Path Monitor Version 3 User Guide replaces the Critical Path
| Monitor Getting Started.
■ These chapters and appendixes from the former CA-Jobtrac Installation
and Maintenance Guide moved to the CA-Jobtrac Reports, Maintenance, and
Recovery Guide: User Exits, TRACAUTH Security, JFST Access Method, and
The Sysout Capture File.
■ Syntax diagrams are now standardized within the IBM BookManager
format. See Reading Syntax Diagrams in the CA-Jobtrac Operator Guide for
more information.
■ Unicenter TNG Framework for OS/390 is composed of the services
formerly known as CA90s and Unicenter TNG Framework.

Chapter 1. Introduction 1-9

1.5 Reading Syntax Diagrams

1.5 Reading Syntax Diagrams

The formats of all statements and some basic language elements are illustrated
using syntax diagrams. Read syntax diagrams from left to right and top to
bottom.

The following terminology, symbols, and concepts are used in syntax

diagrams.

Keywords: Appear in uppercase letters, for example, COMMAND or PARM.

These words must be entered exactly as shown.

Variables: Appear in italicized lowercase letters, for example, variable.

Required Keywords and Variables: Appear on a main line.

Optional Keywords and Variables: Appear below a main line.

Default Keywords and Variables: Appear above a main line.

Double Arrowheads Pointing to the Right: Indicate the beginning of a

statement.

Double Arrowheads Pointing to Each Other: Indicate the end of a

statement.

Single Arrowheads Pointing to the Right: Indicate a portion of a statement,

or that the statement continues in another diagram.

Punctuation Marks or Arithmetic Symbols: If punctuation marks or

arithmetic symbols are shown with a keyword or variable, they must be
entered as part of the statement or command. Punctuation marks and
arithmetic symbols can include:

, comma > greater than symbol

. period < less than symbol
( open parenthesis = equal sign
) close parenthesis ¬ not sign
+ addition − subtraction
* multiplication / division

1-10 Operator Guide

 1.5 Reading Syntax Diagrams

The following is an example of a statement without parameters.

Statement Without Parameters

──COMMAND─────────────────────────────────────────────────────

You must write:

COMMAND

Required parameters appear on the same horizontal line (the main path of the
diagram) as the command or statement. The parameters must be separated by
one or more blanks.

Statement With Required Parameters

──COMMAND──PARM1──PARM2───────────────────────────────────────

You must write:

COMMAND PARM1 PARM2

Delimiters such as parentheses around parameters or clauses must be included.

Delimiters Around Parameters

──COMMAND──(PARM1)──PARM2='variable'──────────────────────────

If the word “variable” is a valid entry, you must write:

COMMAND (PARM1) PARM2='variable'

Where you see a vertical list of parameters as shown in the following example,
you must choose one of the parameters. This indicates that one entry is
required and only one of the displayed parameters is allowed in the statement.

Choice of Required Parameters

──COMMAND──┬─PARM1─┬──────────────────────────────────────────
├─PARM2─┤
└─PARM3─┘

You can choose one of the parameters from the vertical list, such as in the
following examples:

COMMAND PARM1
COMMAND PARM2
COMMAND PARM3

Chapter 1. Introduction 1-11

1.5 Reading Syntax Diagrams

When a required parameter in a syntax diagram has a default value, it

indicates the value for the parameter if the command is not specified. If you
specify the command, you must code the parameter and specify one of the
displayed values.

Default Value for a Required Parameter

┌─YES─┐
──COMMAND──PARM1=─┴─NO──┴───PARM2─────────────────────────────

If you specify the command, you must write one of the following:

COMMAND PARM1=NO PARM2

COMMAND PARM1=YES PARM2

A single optional parameter appears below the horizontal line that marks the
main path.

Optional Parameter
──COMMAND──┬───────────┬──────────────────────────────────────
└─PARAMETER─┘

You can choose (or not) to use the optional parameter, as shown in the
following examples:

COMMAND
COMMAND PARAMETER

If you have a choice of more than one optional parameter, the parameters
appear in a vertical list below the main path.

Choice of Optional Parameters

──COMMAND──┬───────┬──────────────────────────────────────────
├─PARM1─┤
└─PARM2─┘

You can choose any of the parameters from the vertical list, or you can write
the statement without an optional parameter, such as in the following
examples:

COMMAND
COMMAND PARM1
COMMAND PARM2

For some statements, you can specify a single parameter more than once. A
repeat symbol (a backward-pointing arrow above the main horizontal line)

1-12 Operator Guide

 1.5 Reading Syntax Diagrams

indicates that you can specify multiple parameters. The following examples
include the repeat symbol.

Repeatable Variable Parameter

┌──
──────────┐
──COMMAND────variable─┴───────────────────────────────────────

In the above example, the word “variable” is in lowercase italics, indicating

that it is a value you supply, but it is also on the main path, which means that
you are required to specify at least one entry. The repeat symbol indicates that
you can specify a parameter more than once. Assume that you have three
values named VALUEX, VALUEY, and VALUEZ for the variable. Some of
your choices are:

COMMAND VALUEX
COMMAND VALUEX VALUEY
COMMAND VALUEX VALUEX VALUEZ

If the repeat symbol contains punctuation such as a comma, you must separate
multiple parameters with the punctuation. The following example includes the
repeat symbol, a comma, and parentheses.

Separator with Repeatable Variable and Delimiter

┌─,────────┐
──COMMAND──(────variable─┴──)─────────────────────────────────

In the above example, the word “variable” is in lowercase italics, indicating

that it is a value you supply. It is also on the main path, which means that
you must specify at least one entry. The repeat symbol indicates that you can
specify more than one variable and that you must separate the entries with
commas. The parentheses indicate that the group of entries must be enclosed
within parentheses. Assume that you have three values named VALUEA,
VALUEB, and VALUEC for the variable. Some of your choices are:

COMMAND (VALUEC)
COMMAND (VALUEB,VALUEC)
COMMAND (VALUEB,VALUEA)
COMMAND (VALUEA,VALUEB,VALUEC)

The following example shows a list of parameters with the repeat symbol.

Optional Repeatable Parameters

┌──
─────────┐ ┌──
─────────┐ ┌──
─────────┐
──COMMAND───┬───────┬┴───┬───────┬┴───┬───────┬┴──────────────
└─PARM1─┘ └─PARM2─┘ └─PARM3─┘

Chapter 1. Introduction 1-13

1.5 Reading Syntax Diagrams

Some choices you can make include:

COMMAND PARM1
COMMAND PARM1 PARM2 PARM3
COMMAND PARM1 PARM1 PARM3

When a parameter in a syntax diagram is above the line, for example, YES in
the following diagram, its special treatment indicates it is the default value for
the parameter. If you do not include the parameter when you write the
statement, the result is the same as if you had actually specified the parameter
with the default value.

Default Value for a Parameter

──COMMAND──┬─────────────────┬──PARM2─────────────────────────
│ ┌─YES─┐ │
└─PARM1=─┴─NO──┴──┘

Because YES is the default in the example above, if you write:

COMMAND PARM2

you have written the equivalent of:

COMMAND PARM1=YES PARM2

In some syntax diagrams, a set of several parameters is represented by a single

reference, as in this example:

Variables Representing Several Parameters

──COMMAND──┬─────────────────────┬────────────────────────────
├─PARM1───────────────┤
└─┤ parameter-block ├─┘
parameter-block:
├──┬──────────────────┬──────────────────────────────────────────┤
├─PARM2────────────┤
└─PARM3─┬───────┬──┘
├─PARM4─┤
└─PARM5─┘

The “parameter-block” can be displayed in a separate syntax diagram.

1-14 Operator Guide

 1.5 Reading Syntax Diagrams

Choices you can make from this syntax diagram therefore include (but are not
limited to) the following:

COMMAND PARM1
COMMAND PARM3
COMMAND PARM3 PARM4
Note: Before you can specify PARM4 or PARM5 in this command, you must
specify PARM3.

A note in a syntax diagram is similar to a footnote except that the note appears
at the bottom of the diagram box.

──COMMAND──┬─────────┬────────────────────────────────────────
(1)
└─PARM1─── ┘
Note:
1 This is a note about the item.

Chapter 1. Introduction 1-15

1.6 Accessing CA-Jobtrac

1.6 Accessing CA-Jobtrac

The specific steps you must follow to access CA-Jobtrac depend on how your
system was set up during installation. Contact the CA-Jobtrac administrator
for specific steps you should follow to access CA-Jobtrac.

Possible Methods for Access: The most common access methods are:
■ Using the ISPF/PDF Primary Option Menu
■ Using a TSO CLIST

Sample Procedure for Using the ISPF/PDF Primary Option Menu to Access
CA-Jobtrac: The steps below represent a common procedure for accessing
CA-Jobtrac using the ISPF/PDF Primary Option Menu. This procedure may
vary from the procedure you will use.
1. Log on to TSO.
2. Set the ISPF profile to NUMBER OFF, CAPS ON.
3. Access the ISPF/PDF Primary Option Menu (if it does not appear
automatically when you log on to TSO).
4. Select the CA-Jobtrac menu item to display the CA-Jobtrac primary panel.
The panel below shows a sample ISPF menu with a CA-Jobtrac entry. On
this menu, you would select J. The menu and the CA-Jobtrac entry may
differ at your installation.

 ----------------------- ISPF Primary Option Menu ----------------------------


OPTION --->
USERID - ID1
 ISPF PARMS - Specify terminal and user parameters TIME - hh:mm
1 BROWSE - Display source data or output listings TERMINAL - 3278
2 EDIT - Create or change source data PF KEYS - 24
3 UTILITIES - Perform utility functions
4 FOREGROUND - Invoke language processors in foreground
5 BATCH - Submit job for language processing
6 COMMAND - Enter TSO command or CLIST
7 DIALOG TEST - Perform dialog testing
C CHANGES - Display summary of changes for this release
I ISMF - Invoke interactive storage management facility
S IPCS - IPCS problem analysis services
T TUTORIAL - Display information about ISPF/PDF
U UTILITIES - Other third party or in-house supported utilities
J CA-JOBTRAC - Invoke CA-Jobtrac automated scheduling system

X EXIT - Terminate ISPF using log and list defaults

Enter END command to terminate ISPF.
 

1-16 Operator Guide

 1.6 Accessing CA-Jobtrac

Sample Procedure for Using a TSO CLIST to Access CA-Jobtrac: The steps
below represent a common procedure for accessing CA-Jobtrac using a TSO
CLIST (command list). This procedure may vary from the procedure you must
use.
1. Log on to TSO.
2. Enter the TSO CLIST that displays the CA-Jobtrac primary panel. The
following is a sample CLIST.
TSO EX 'CAI.SAMPJCL(TCLIST3)'
The library and member name you will use is probably different from the
example above.

Chapter 1. Introduction 1-17

1.7 Exiting CA-Jobtrac

1.7 Exiting CA-Jobtrac

Procedures: You can exit CA-Jobtrac by pressing the END PF key until you
return to the desired non-CA-Jobtrac display.

You can also exit CA-Jobtrac from any CA-Jobtrac display by following the
steps below:
1. Type =x in the COMMAND field of any CA-Jobtrac display.
2. Press Enter.

Procedure Results: The specific results of the above procedure depend on

how CA-Jobtrac was set up during installation on your system. In most cases,
you return to either the ISPF/PDF Primary Option Menu or to a TSO display
with a READY prompt. Contact your CA-Jobtrac administrator for specific
procedures you should follow when exiting CA-Jobtrac.

1.7.1 Using the END PF Key

You can press the END PF key (or enter the END command) to exit any
CA-Jobtrac display.

1-18 Operator Guide

 1.8 CA-Jobtrac Primary Panel

1.8 CA-Jobtrac Primary Panel

1.8.1 Description of the CA-Jobtrac Primary Panel

When you access CA-Jobtrac, the initial display is the CA-Jobtrac primary
panel. You enter commands on this panel to access various CA-Jobtrac panels
and functions.

Panel Sample: The panel below shows a sample CA-Jobtrac primary panel:

 CA-Jobtrac V 3.5

COMMAND ===> yy/mm/dd hh:mm

Primary Commands:
RALL - List all events CA-JCLTRAC- JCL analysis system
J=evnm - List events beg. w evnm ISERVE - CA-GSS IMOD facility
K=status - List events w/ status JCL - Edit production JCL
D=dep - List events w/ deps SCL - Edit SCL
B=bgname - List events of a bus. grp. SYS OPTS - Update global options
T=hhmm - List events by target time SYS HOLS - Holiday calendar maint.
BUSGRP - Business group status SYS CYCS - Cyclic calendar maint.
ADD - Add event to schedule JTS - Table services
GSO - Generate schedules online OUT - Sysout capture

 The following line commands will be available for SCHEDULED EVENT DISPLAY:
 - CA-View sysout brwse H - Event history R - Rerun/restart
A - Release dependencies I - Audit history S - Select (detail)
C - Cond code exceptions L - Dependent jobstream T - Create/edit temp JCL
D - Delete event M - Manual actions V - Volume pull list
E - Edit JCL/SCL O - Browse sysout Y - CPM info
F - Display DSN triggers P - Purge event X - Resource dependency
G - GSO Q - Sysview Jobsum ? - View documentation
 
Panel Description: Below the COMMAND field is a list of several commands
and search keys that can be entered in the COMMAND field to access other
displays and perform some functions. A complete list of commands is in the
search keys and commands section in the Reference Summary.

Also listed on this panel are many of the line commands that are available on
the Scheduled Event Display and Scheduled Event Network panels. A
complete list of commands is in the line commands section in the Reference
Summary.

1.8.2 Issuing Commands from the CA-Jobtrac Primary Panel

The CA-Jobtrac primary panel is a starting point for using CA-Jobtrac. By
entering commands at the COMMAND field, you can display other CA-Jobtrac
panels to monitor the current schedule, modify the current schedule, and
perform other functions.

Chapter 1. Introduction 1-19

1.8 CA-Jobtrac Primary Panel

For example, you:

■ Use the O command to display captured sysouts
■ Use the D= command to display events with dependencies you specify as
part of the command
■ Use the SCS command to display scheduled system commands

Most commands listed in the search keys and commands section in the
Reference Summary can be entered on the CA-Jobtrac primary panel.
Frequently-used search keys and commands are listed on the CA-Jobtrac
primary panel. For complete information about primary commands, see the
Reference Summary.

Procedure: Follow the steps below to issue commands from the CA-Jobtrac
primary panel.
1. Type the event name, prefix, search key, or command you want to execute
in the COMMAND field.
2. Press Enter to execute the search or command.

You can also enter command strings at the COMMAND field (for more
information on changing displays and executing commands, see 1.12,
“Changing Displays and Executing Commands”).

Example: You have accessed CA-Jobtrac and the CA-Jobtrac primary panel is
displayed. You want to view a list of all events on the current schedule that
are waiting to be executed. To display this list, you would type K=W in the
COMMAND field (see panel below) and press Enter. K= is the search key
command and W specifies waiting.

 CA-Jobtrac V 3.5

COMMAND ===> K=W yy/mm/dd hh:mm

Primary Commands:
RALL - List all events CA-JCLTRAC- JCL analysis system
J=evnm - List events beg. w evnm ISERVE - CA-GSS IMOD facility
K=status - List events w/ status JCL - Edit production JCL
D=dep - List events w/ deps SCL - Edit SCL
B=bgname - List events of a bus. grp. SYS OPTS - Update global options
T=hhmm - List events by target time SYS HOLS - Holiday calendar maint.
BUSGRP - Business group status SYS CYCS - Cyclic calendar maint.
ADD - Add event to schedule JTS - Table services
GSO - Generate schedules online OUT - Sysout capture

 The following line commands will be available for SCHEDULED EVENT DISPLAY:
 - CA-View sysout brwse H - Event history R - Rerun/restart
A - Release dependencies I - Audit history S - Select (detail)
C - Cond code exceptions L - Dependent jobstream T - Create/edit temp JCL
D - Delete event M - Manual actions V - Volume pull list
E - Edit JCL/SCL O - Browse sysout Y - CPM info
F - Display DSN triggers P - Purge event X - Resource dependency
G - GSO Q - Sysview Jobsum ? - View documentation
 

1-20 Operator Guide

 1.8 CA-Jobtrac Primary Panel

1.8.3 Defining a Default Search Command

Whenever you access CA-Jobtrac, the first display you see is the CA-Jobtrac
primary panel. You can bypass the CA-Jobtrac primary panel by defining a
default search command. Then, whenever you access CA-Jobtrac, the first
display is the panel that would result from entering the default command.

You can also execute the default command any time after it has been defined
by entering D in the COMMAND field of the CA-Jobtrac primary, Scheduled
Event Display, Scheduled Event Network, or Business Group Status panels.

The default search command you define affects only your sessions on
CA-Jobtrac. Other users can define their own default search commands. The
default command you define remains in effect until you change or remove it.

Procedure for Defining or Changing the Default Search Command:

Follow the steps below to define or change a default search command.
1. Position the cursor in the COMMAND field of the CA-Jobtrac primary,
Scheduled Event Display, Scheduled Event Network, or Business Group
Status panels.
2. Type D command, where command is the search command you want to be
the default.
3. Press Enter to define the specified search command as the default.

Procedure for Removing a Default Search Command: Follow the steps

below to remove the default command. If you remove the default command,
the CA-Jobtrac primary panel will be the initial display when you access
CA-Jobtrac.
1. Position the cursor in the COMMAND field of the CA-Jobtrac primary,
Scheduled Event Display, Scheduled Event Network, or Business Group
Status panels.
2. Type D OFF.
3. Press Enter to remove the default search command.

Chapter 1. Introduction 1-21

1.9 CA-Jobtrac User Profile Panel

1.9 CA-Jobtrac User Profile Panel

The CA-Jobtrac User Profile panel is a pop-up panel which allows the users to
customize their CA-Jobtrac ISPF interface options, such as default location,
enabling prompts, and default search command.

1.9.1 Displaying the CA-Jobtrac User Profile Panel

Enter the PROFile command at the COMMAND field of the CA-Jobtrac
primary, Scheduled Event Display, Scheduled Event Network, or Business
Group Status panels.

The CA-Jobtrac User Profile panel is a pop-up panel.

Syntax: The syntax of the display CA-Jobtrac User Profile panel command is
as follows:

PROFile
──┬─PROF────┬─────────────────────────────────────────────────
└─PROFILE─┘

1-22 Operator Guide

 1.9 CA-Jobtrac User Profile Panel

1.9.2 Description of the CA-Jobtrac User Profile Panel

Panel Sample: The panel below shows a sample CA-Jobtrac User Profile
panel. Field descriptions follow.

 ------------------ CA-Jobtrac User Profile --------------------- 

COMMAND ===>

Default Command ===>

Default Location ===> 
Date Format ===>A (A or 1)
CA-View Database Name ===>

Confirm Event Changes ===>  (Y,N,O)

Confirm Event Delete ===>  (Y,N,O)
Confirm Event Purges ===>  (Y,N,O)
Confirm JTS Updates ===> Y (Y,N)

(O=Only from Detail)

----------------------------------------------------------------
 
Default Command: Whenever you access CA-Jobtrac, the first display you
see is the CA-Jobtrac primary panel. You can bypass the CA-Jobtrac primary
panel by defining a default search command. Then, whenever you access
CA-Jobtrac, the first display is the panel that would result from entering the
default command.

Enter the default search command you want in this field or leave it blank if
you want the CA-Jobtrac primary panel to be displayed.

Default Location: Enter the location ID of the location you want to define as
your default location in this field.

Date Format: Enter A for American date format (mmdd) or I for

International date format (ddmm).
Note: DTFMT affects only the CA-Jobtrac-controlled dates. The current date
in the panel header is controlled by TSO/ISPF and is not affected by
this parameter.

CA-View Database Name: If you are using CA-View, enter the name of the
CA-View database you want CA-Jobtrac to access when the SAR primary
command or 0 (zero) line command is issued.

Chapter 1. Introduction 1-23

1.9 CA-Jobtrac User Profile Panel

Confirm Event Changes?: Enter Y to receive a prompt asking you whether

you want to save event changes you have made.

Enter N to suppress this prompt.

Enter O to receive this prompt only when you have made changes on the
Scheduled Event Detail panel or the Event Execution Detail panel and entered
the END command. You will not be prompted when you make changes to an
event on the Scheduled Event Display panel.

Confirm Event Deletes?: Enter Y to receive a prompt confirming whether

you want to delete an event before the deletion is actually executed.

Enter N to suppress this prompt.

Enter O to receive this prompt only when you enter the DELETE command on
the Scheduled Event Detail panel or the Event Execution Detail panel. You
will not be prompted when you issue the D line command from the Scheduled
Event Display panel.

Confirm Event Purges?: Enter Y to receive a prompt confirming whether you

want to purge an event before the purge is actually executed.

Enter N to suppress this prompt.

Enter O to receive this prompt only when you enter the PURGE command on
the Scheduled Event Detail panel or the Event Execution Detail panel. You
will not be prompted when you issue the P line command from the Scheduled
Event Display panel.

Confirm JTS Updates?: Enter Y to receive a prompt asking you whether you
want to save changes you have made on a table services panel.

Enter N to suppress this prompt.

1-24 Operator Guide

 1.10 Determining Your Authorization Level

1.10 Determining Your Authorization Level

Each CA-Jobtrac user has an authorization profile that defines the commands
and functions that can be initiated by the user. You can access an
Authorization Profile panel to find out what commands and functions you can
initiate.

You cannot change your authorization parameters from this panel.

Authorization profiles can be defined or altered only through the TRACAUTH
table. For information on the TRACAUTH table, see the Getting Started.

You can, however, temporarily add a location to your profile so that you can
monitor events for that location (for more information on adding or removing
locations, see 1.10.3, “Adding or Removing Locations”). If you use the
TRACX26 user exit, you cannot add or remove locations from your
authorization profile.

1.10.1 Displaying the Authorization Profile Panel

Follow the steps below to display an Authorization Profile panel that defines
the commands and functions you can initiate.
1. Position the cursor in the COMMAND field of the CA-Jobtrac primary,
Scheduled Event Display, Scheduled Event Network, Business Group
Status, or Authorization Profile panel.
2. Type AUTH.
3. Press Enter to display your Authorization Profile panel.

To view another user's authorization profile, follow the steps above but, in
Step 2, type AUTH= userid, where userid is the ID of the user whose profile
you want to view.

To view a profile for a group of users, follow the steps above but, in Step 2,
type AUTH= prefix*, where prefix is a user ID prefix common to all users in
the group.

Chapter 1. Introduction 1-25

1.10 Determining Your Authorization Level

1.10.2 Description of the Authorization Profile Panel

Panel Sample: The panel below shows a sample Authorization Profile panel.

 CA-Jobtrac Authorization Profile: NB1TM56 ROW 1 TO 16 OF 16


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Location Userid Command Dependency Options
Profiles Rule Restrictions Restrictions In Effect
----------------- --------- ---------------- ---------------- -----------------
 HOME LOC MKC EVENT ADD JCL ALTER NOTIFY=NO
EVENT DELETE MAN DEP ALTER
EVENT PURGE OUTRLSE ALTER SYSOPT EDIT=YES
ABN DEP ALTER JCL VERIFY=NO
TIME/DATE CHG OK DSN DEP ALTER HOLCAL ALTER=YES
OUTPUT VIEW PRED DEP CHG CYCCAL ALTER=YES
$QUEUE ALTER OK SYSOUT DEL=YES
RERUN/RESTART
1 LOC LIB 1 MKC EVENT ADD JCL ALTER NOTIFY=NO
EVENT DELETE MAN DEP ALTER
EVENT PURGE OUTRLSE ALTER SYSOPT EDIT=YES
ABN DEP ALTER JCL VERIFY=NO
TIME/DATE CHG OK DSN DEP ALTER
OUTPUT VIEW PRED DEP CHG
$QUEUE ALTER OK SYSOUT DEL=YES
RERUN/RESTART
 BOTTOM OF DATA 
 
Panel Description: The title line of the Authorization Profile panel includes
the ID of the user whose profile is displayed (in the panel above, NB1TM56).

The Location Profiles field identifies the locations for which authorization
parameters are defined in the TRACAUTH table (see the Getting Started).

If you are using the TRACX26 user exit, this panel will only display your ID
and default location. The word EXTERNAL will appear on the panel in
parentheses in the Location Profiles field. No other information will be
displayed on this panel if you are using the TRACX26 user exit.

Entries in the Location Profiles field identify the locations for which the user
has some level of authorization. Subsequent authorization parameters (up to
the next Location Profiles entry) show the user's authorization to monitor or
manipulate events with the location ID shown in the Location Profiles field.

The Userid Rule field contains a generic user ID rule, the user's ID or
ADDLOC. A user ID entry identifies the user to whom subsequent
authorization parameters apply. ADDLOC is present only if the user has
added a location to the profile (for more information on adding or removing
locations see 1.10.3, “Adding or Removing Locations”).

The authorization parameters that appear under the headings Command

Restrictions, Dependency Restrictions, and Options In Effect are described
below.

1-26 Operator Guide

 1.10 Determining Your Authorization Level

Command Restrictions: Parameters under the Command Restrictions

heading define whether the user can perform the specified command. If NO
appears before the parameter (for example, NO EVENT ADD), the user cannot
perform the specified function. If NO does not appear, the user can perform
the function.

Command restrictions apply to one location only. If the user is authorized

(other than monitor only) for multiple locations, each location will have its
own command restriction parameters.

The following table describes the function of each parameter:

With this parameter You can

EVENT ADD Add events to the current schedule.
EVENT DELETE Delete events from the current schedule.
EVENT PURGE Issue the Purge command (P) for an event. If the
event is awaiting submission, it is removed from
the current schedule and successors are released
from dependence on the event. If the event is
completed, it is removed from the current schedule.
If the event is currently executing, no action is
taken.
TIME/DATE CHG OK Alter an event's target, start, and abort time.
OUTPUT VIEW View and print sysouts selected from the Sysout
Capture panel.
MONITOR ONLY Only view events. You cannot modify the current
schedule in any way or view JCL or sysouts.

Chapter 1. Introduction 1-27

1.10 Determining Your Authorization Level

Dependency Restrictions: Parameters under the Dependency Restrictions

heading define whether the user can alter an event's execution dependencies.
If NO appears before the parameter (for example, NO JCL ALTER), the user
cannot perform the specified function. If NO does not appear, the user can
perform the function.

Dependency restrictions apply to one location only. If the user is authorized

(other than monitor only) for multiple locations, each location has its own
command restriction parameters.

The following table describes the function of each parameter:

With this parameter You can

JCL ALTER Remove a JCL dependency
(dependency code J).
MAN DEP ALTER Remove a manual dependency (M).
OUTRLSE ALTER Remove an output dependency (O)
after the event executes.
ABN DEP ALTER Remove an abend dependency (A).
DSN DEP ALTER Remove a data set dependency (D).
PRED DEP CHG Remove a predecessor dependency
(P).
$QUEUE ALTER OK Remove a queued release
dependency (Q).
RESTART/RERUN Perform an event restart or rerun.

1-28 Operator Guide

 1.10 Determining Your Authorization Level

Options in Effect: Parameters under the Options In Effect heading define

various functions and options for the user. If =YES follows the option (for
example, NOTIFY=YES), the user can perform the specified function, or the
specified feature is in effect. If =NO follows the option (for example,
NOTIFY=NO), the user cannot perform the function, or the feature is off. If
=LOC is displayed, the user can alter only events with the user's default
location ID.

The Options In Effect parameters affect all locations for which a user is
authorized (except the SYSOPT EDIT and PARM EDIT options, which are
defined for the user's default location).

The following table describes the function of each parameter:

Parameter Function
NOTIFY=YES User is notified if an event scheduled
by the user does not end normally
(for example, completes abnormally
with a system or user abend, with a
JCL error, catalog error, or condition
code check).
SYSOPT EDIT=YES User can edit the global options
panels using the SYS OPTS
command.
JCL VERIFY=YES CA-Jobtrac verifies that JCL for an
event is in the user's JCL library
before allowing the user to add the
event to the current schedule.
HOLCAL ALTER=YES User can change holiday calendars
using the Holiday Calendars panel.
CYCCAL ALTER=YES User can change cyclic calendars
using the Cyclic Calendars panel.
SYSOUT DEL=YES User can delete sysout entries from
the Sysout Capture panel.

Chapter 1. Introduction 1-29

1.10 Determining Your Authorization Level

1.10.3 Adding or Removing Locations

You can add a location to your authorization profile so that you can view
events for that location on the current schedule. If you use the TRACX26 user
exit, you cannot add or remove locations to your authorization profile.

You are limited to monitoring the events for the added location. You cannot
modify the events scheduled for that location in any way. The authorization
parameter MONITOR ONLY appears in the Command Restrictions field of the
Authorization Profile panel to indicate the restricted authorization.

ADDLOC appears in the Userid Rule field of the Authorization Profile panel
to indicate that the location was added by the user.

Locations added using the ADDLOC command are removed automatically

when you exit CA-Jobtrac. You can also use the REMLOC command to
remove the locations you add to your profile. If you use the TRACX26 user
exit, the ADDLOC and REMLOC commands are not available to you.

Using the ADDLOC Command: Follow the steps below to add a location to
your authorization profile using the ADDLOC command. The location is
added for the duration of your CA-Jobtrac session only, and allows viewing of
events for that location only.
1. Position the cursor in the COMMAND field of the CA-Jobtrac primary,
Scheduled Event Display, Scheduled Event Network, or Business Group
Status panels.
2. Type ADDLOC= nnn, where nnn is the location ID of the location you are
adding.
3. Press Enter to add the location to your authorization profile.

Using the REMLOC Command: Follow the steps below to remove a location
from your authorization profile using the REMLOC command. You can only
remove locations you added using the ADDLOC command.
1. Position the cursor in the COMMAND field of the CA-Jobtrac primary,
Scheduled Event Display, Scheduled Event Network, or Business Group
Status panels.
2. Type REMLOC=nnn, where nnn is the location ID of the location you are
removing.
3. Press Enter to remove the location from your authorization profile.

1-30 Operator Guide

 1.10 Determining Your Authorization Level

Example: Suppose that your default location is 010 (Los Angeles) but you
want to see scheduled events for location 020 (New York). To add New York
to your authorization profile, you would type ADDLOC=020 in the
COMMAND field of the Scheduled Event Display panel, as shown below.
Note: Los Angeles job names (location 10) have a prefix of AC*. New York
job names (location 20) have a prefix of AD*.

 CA-Jobtrac Scheduled Event Display ROW 1 TO 18 OF 21


COMMAND ===> ADDLOC=2 SCROLL ===> PAGE
yy/mm/dd hh:mm
Event ----Target----Successor Dep Current CMD= RALL
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ---------------------------------------
ACAP1 AS-AP 1/23 J WAITING RSTRT J 5643 LATE
ACAP15 1:5  1/21 ACGL2D J WAITING DEPENDENCIES LATE
ACAR4 1:3  1/21 ACAP15D P WAITING DEPENDENCIES LATE
ACAR4 15:6  11/1 M WAITING DEPENDENCIES LATE
ACAR41 1:5  12/18 ACAPD P WAITING DEPENDENCIES LATE
ACAR21M 1:3  1/21 P WAITING DEPENDENCIES LATE
ACGL2D 1:5  1/21 ACAR4 P WAITING DEPENDENCIES LATE
ACGL21R 1:3  1/21 ACGL41 P WAITING DEPENDENCIES LATE
ACGL41M 1:5  1/21 P WAITING DEPENDENCIES LATE
ACVP12M 16:51 1/23 JO WAITING RERUN J 5632 LATE
ACVP12M 16:51 1/23 O ABENDED=S3A, J 5632. AT 16:32- 1/23
 BOTTOM OF DATA 
 
When you press Enter, New York is added to your authorization profile and a
Scheduled Event Display including events scheduled for New York is
displayed (see the panel below).

 CA-Jobtrac Scheduled Event Display ROW 1 TO 18 OF 21


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Event ----Target----Successor Dep Current CMD= RALL
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ---------------------------------------
ACAP1 AS-AP 1/23 J WAITING RSTRT J 5643 LATE
ACAP15 1:5  1/21 ACGL2D J WAITING DEPENDENCIES LATE
ACAR4 1:3  1/21 ACAP15D P WAITING DEPENDENCIES LATE
ACAR4 15:6  11/1 M WAITING DEPENDENCIES LATE
ACAR41 1:5  12/18 ACAPD P WAITING DEPENDENCIES LATE
ACAR21M 1:3  1/21 P WAITING DEPENDENCIES LATE
ACGL2D 1:5  1/21 ACAR4 P WAITING DEPENDENCIES LATE
ACGL21R 1:3  1/21 ACGL41 P WAITING DEPENDENCIES LATE
ACGL41M 1:5  1/21 P WAITING DEPENDENCIES LATE
ACVP12M 16:51 1/23 JO WAITING RERUN J 5632 LATE
ACVP12M 16:51 1/23 O ABENDED=S3A, J 5632. AT 16:32- 1/23
ADANN2 22:2  11/13 ADANN3 P WAITING DEPENDENCIES LATE
ADANN3 22:4  11/13 ADANN4 P WAITING DEPENDENCIES LATE
ADANN4 23:  11/13 ADANN5 P WAITING DEPENDENCIES LATE
ADANN5 23:2  11/13 ADANN6 P WAITING DEPENDENCIES LATE
ADANN6 23:4  11/13 ADANN7 P WAITING DEPENDENCIES LATE
 

Chapter 1. Introduction 1-31

1.10 Determining Your Authorization Level

If you access your Authorization Profile panel, New York will appear, as
shown in the panel below.

 CA-Jobtrac Authorization Profile: NB1TM56 ROW 1 TO 17 OF 18


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Location Userid Command Dependency Options
Profiles Rule Restrictions Restrictions In Effect
----------------- --------- ---------------- ---------------- ------------------
 HOME LOC NB1TM56 EVENT ADD JCL ALTER NOTIFY=NO
EVENT DELETE MAN DEP ALTER
EVENT PURGE OUTRLSE ALTER SYSOPT EDIT=YES
ABN DEP ALTER JCL VERIFY=NO
TIME/DATE CHG OK DSN DEP ALTER HOLCAL ALTER=YES
OUTPUT VIEW PRED DEP CHG CYCCAL ALTER=YES
$QUEUE ALTER OK SYSOUT DEL=YES
RERUN/RESTART
1 LOC LIB 1 NB1TM56 EVENT ADD JCL ALTER NOTIFY=NO
EVENT DELETE MAN DEP ALTER
EVENT PURGE OUTRLSE ALTER SYSOPT EDIT=YES
ABN DEP ALTER JCL VERIFY=NO
TIME/DATE CHG OK DSN DEP ALTER
OUTPUT VIEW PRED DEP CHG
$QUEUE ALTER OK SYSOUT DEL=YES
RERUN/RESTART
2 ADDLOC MONITOR ONLY
 
Suppose you no longer want to monitor New York's current schedule. You
would type REMLOC=020 in the COMMAND field of the Scheduled Event
Display panel, as shown below.

 CA-Jobtrac Scheduled Event Display ROW 1 TO 18 OF 21


COMMAND ===> REMLOC=2 SCROLL ===> PAGE
yy/mm/dd hh:mm
Event ----Target----Successor Dep Current CMD= RALL
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ---------------------------------------
ACAP1 AS-AP 1/23 J WAITING RSTRT J 5643 LATE
ACAP15 1:5  1/21 ACGL2D J WAITING DEPENDENCIES LATE
ACAR4 1:3  1/21 ACAP15D P WAITING DEPENDENCIES LATE
ACAR4 15:6  11/1 M WAITING DEPENDENCIES LATE
ACAR41 1:5  12/18 ACAPD P WAITING DEPENDENCIES LATE
ACAR21M 1:3  1/21 P WAITING DEPENDENCIES LATE
ACGL2D 1:5  1/21 ACAR4 P WAITING DEPENDENCIES LATE
ACGL21R 1:3  1/21 ACGL41 P WAITING DEPENDENCIES LATE
ACGL41M 1:5  1/21 P WAITING DEPENDENCIES LATE
ACVP12M 16:51 1/23 JO WAITING RERUN J 5632 LATE
ACVP12M 16:51 1/23 O ABENDED=S3A, J 5632. AT 16:32- 1/23
ADANN2 22:2  11/13 ADANN3 P WAITING DEPENDENCIES LATE
ADANN3 22:4  11/13 ADANN4 P WAITING DEPENDENCIES LATE
ADANN4 23:  11/13 ADANN5 P WAITING DEPENDENCIES LATE
ADANN5 23:2  11/13 ADANN6 P WAITING DEPENDENCIES LATE
ADANN6 23:4  11/13 ADANN7 P WAITING DEPENDENCIES LATE
 

1-32 Operator Guide

 1.10 Determining Your Authorization Level

When you press Enter, New York is removed from your authorization profile
and a Scheduled Event Display panel excluding events for New York is
displayed, as shown below.

 CA-Jobtrac Scheduled Event Display ROW 1 TO 11 OF 11


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Event ----Target----Successor Dep Current CMD= RALL
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ---------------------------------------
ACAP1 AS-AP 1/23 J WAITING RSTRT J 5643 LATE
ACAP15 1:5  1/21 ACGL2D J WAITING DEPENDENCIES LATE
ACAR4 1:3  1/21 ACAP15D P WAITING DEPENDENCIES LATE
ACAR4 15:6  11/1 M WAITING DEPENDENCIES LATE
ACAR41 1:5  12/18 ACAPD P WAITING DEPENDENCIES LATE
ACAR21M 1:3  1/21 P WAITING DEPENDENCIES LATE
ACGL2D 1:5  1/21 ACAR4 P WAITING DEPENDENCIES LATE
ACGL21R 1:3  1/21 ACGL41 P WAITING DEPENDENCIES LATE
ACGL41M 1:5  1/21 P WAITING DEPENDENCIES LATE
ACVP12M 16:51 1/23 JO WAITING RERUN J 5632 LATE
ACVP12M 16:51 1/23 O ABENDED=S3A, J 5632. AT 16:32- 1/23
 BOTTOM OF DATA 
 

Chapter 1. Introduction 1-33

1.11 Description of the CA-Jobtrac Status Display

1.11 Description of the CA-Jobtrac Status Display

Type STATUS and press Enter to display status.

Panel Sample: The panel below shows a sample CA-Jobtrac System Status
Display panel. Field descriptions follow.

 CA-Jobtrac System Status Display


COMMAND ===> yy/mm/dd 15:28

CA-Jobtrac Checkpoint: your.CHECKPT

Token: Y
Recs : 7 Blksize : 5166 Extents : 1
Avail : 435

History File : your.JOBHIST

Recs : 21 CI Size : 6656 Extents : 1

Avail : 2652 CI Splits: 1 CA Splits: 

Sysout Capture : your.CAPTURE

Tracks Allocated : 315 Device Type : 339

Job Index Blocks : 3372 Used: 47 : 12. %
Job Data Blocks : 324 Used: 557 : 17.1 %

Restage Options: Abend- Cond Code- Cat Error- JCL Error-

Current CA-Jobtrac Maintenance Level: 3.5 nnnn
 

1-34 Operator Guide

 1.11 Description of the CA-Jobtrac Status Display

Fields Explained: The following table briefly describes the fields that provide
information about system status.

Field Function
CA-Jobtrac Shows the name of the data set allocated and its file
Checkpoint usage.
Token Identifies the CA-Jobtrac you are currently accessing
through ISPF.
History File Shows the name of the data set allocated and its file
usage.
Sysout Capture Shows the name of the data set allocated and its file
usage.
Restage Options Shows the options and their settings.
Current CA-Jobtrac Shows the maintenance level of CA-Jobtrac.
Maintenance Level

A mismatch flag is used when a CA-Jobtrac user's allocated checkpoint is

different than the checkpoint allocated by the CA-Jobtrac started task.

Chapter 1. Introduction 1-35

1.12 Changing Displays and Executing Commands

1.12 Changing Displays and Executing Commands

You can change CA-Jobtrac displays and perform various functions using:
■ Commands entered at the COMMAND field of the CA-Jobtrac primary,
Scheduled Event Display, Scheduled Event Network, or Business Group
Status panels
■ Line commands entered next to an item on a displayed list

You can also use PF (program function) keys to perform regular TSO ISPF
functions (such as the END PF key to return to the previous display), or to
perform functions you define for the PF keys.

1.12.1 Using the COMMAND Field

Every CA-Jobtrac display has a COMMAND field. Commands that can be
used in these fields include TSO ISPF commands and CA-Jobtrac primary
commands. For complete information about primary commands, see the
search keys and commands section in the Reference Summary. You can use
chains of TSO ISPF commands (be sure to follow TSO ISPF conventions). Not
all CA-Jobtrac primary commands are available on all CA-Jobtrac panels.

Follow the steps below to issue commands from the COMMAND field:
1. Position the cursor on the COMMAND field.
2. Type the command required to access the display or perform the function
you want.
3. Press Enter to execute the command.

1-36 Operator Guide

 1.12 Changing Displays and Executing Commands

Example: The current display is a Scheduled Event Display panel showing

only events that are late. You want to see all events that are late, abended, or
waiting submission. The command required is K=LAW (K= is the search key
command, L=late, A=abended, and W=waiting). The panel below shows the
command typed in the COMMAND field.

 CA-Jobtrac Scheduled Event Display ROW 513 TO 528 OF 76


COMMAND ===> K=LAW SCROLL ===> PAGE
yy/mm/dd hh:mm
Event ----Target----Successor Dep Current CMD= K=L
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ----------------------------------------
HOUJKXX AS-AP  12/7 M WAITING DEPENDENCIES LATE
HOUNSMT 14:3 11/15 J WAITING RERUN J 587 LATE
HOUNSMX4 9:28 11/16 J WAITING RERUN J 531 LATE
HOURAPT1 12:19 1/27 M WAITING DEPENDENCIES LATE
HRMPBQIN 23:44 11/24 HRMPLOG PM WAITING DEPENDENCIES LATE
HRMPCHGR 23:1 11/24 PM WAITING DEPENDENCIES LATE
HRMPCHGX 23:32 11/24 HRMPPTC PM WAITING DEPENDENCIES LATE
HRMPCR1P 23:33 11/24 PM WAITING DEPENDENCIES LATE
HRMPEDB1 22:27 11/24 HRMP32 P WAITING DEPENDENCIES LATE
HRMPKEYC 23:1 11/24 M WAITING DEPENDENCIES LATE
HRMPJQIN 22:3 11/24 HRMPOLCH PM WAITING DEPENDENCIES LATE
HRMPLOGR 23: 11/24 PM WAITING DEPENDENCIES LATE
HRMPLOG4 23:2 11/24 PM WAITING DEPENDENCIES LATE
HRMPOLCH 23:31 11/24 HRMPCHGX PM WAITING DEPENDENCIES LATE
HRMPPTCR 22:33 11/24 PM WAITING DEPENDENCIES LATE
HRMPPTIC 22:34 11/24 PM WAITING DEPENDENCIES LATE
 
When you press Enter, the events shown on the panel above are replaced by
events that are late, abended, or waiting submission, as shown on the panel
below.

 CA-Jobtrac Scheduled Event Display ROW 515 TO 53 OF 712


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Event ----Target----Successor Dep Current CMD= K=LAW
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ----------------------------------------
HOUJKXX AS-AP  12/7 M WAITING DEPENDENCIES LATE
HOUNSMT 14:3 11/15 J WAITING RERUN J 587 LATE
HOUNSMX 13:54 11/13 NAWT-MVSB2 J 562. SUBMITTED 13:54
HOUNSMX 14:36 11/13 NAWT-MVSB2 J 5642. SUBMITTED 14:36
HOUNSMX 14:47 11/13 NAWT-MVSB2 J 5655. SUBMITTED 14:47
HOUNSMX4 9:28 11/16 J WAITING RERUN J 531 LATE
HOURAPT1 12:19 1/27 M WAITING DEPENDENCIES LATE
HRMCPYLR 23:15 11/24 Q WAITING SUBMISSION READY
HRMCPYLR 23:16 11/24 Q WAITING SUBMISSION READY
HRMPBQIN 23:44 11/24 HRMPLOG PM WAITING DEPENDENCIES LATE
HRMPCHGR 23:1 11/24 PM WAITING DEPENDENCIES LATE
HRMPCHGX 23:32 11/24 HRMPPTC PM WAITING DEPENDENCIES LATE
HRMPCr1p 23:33 11/24 PM WAITING DEPENDENCIES LATE
HRMPEDB1 22:27 11/24 HRMP32 P WAITING DEPENDENCIES LATE
HRMPKEYC 23:1 11/24 M WAITING DEPENDENCIES LATE
HRMPJQIN 22:3 11/24 HRMPOLCH PM WAITING DEPENDENCIES LATE
 

Chapter 1. Introduction 1-37

1.12 Changing Displays and Executing Commands

1.12.2 Using Strings of Search Keys

You can use strings of search keys to display very specialized information
about events. Search parameters in the string must be separated by commas.
For example, the string shown in the panel below displays only events with
the prefix ADA (search key ADA) that are currently late (search key K=L) and
that were scheduled for submission between 10 PM and 11 PM (search key
T=2200-2300).

 CA-Jobtrac Scheduled Event Display ROW 515 TO 53 OF 712


COMMAND ===> ADA,K=L,T=22-23 SCROLL ===> PAGE
yy/mm/dd hh:mm
Event ----Target----Successor Dep Current CMD= K=LAW
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ----------------------------------------
HOUJKXX AS-AP  12/7 M WAITING DEPENDENCIES LATE
HOUNSMT 14:3 11/15 J WAITING RERUN J 587 LATE
HOUNSMX 13:54 11/13 NAWT-MVSB2 J 562. SUBMITTED 13:54
HOUNSMX 14:36 11/13 NAWT-MVSB2 J 5642. SUBMITTED 14:36
HOUNSMX 14:47 11/13 NAWT-MVSB2 J 5655. SUBMITTED 14:47
HOUNSMX4 9:28 11/16 J WAITING RERUN J 531 LATE
HOURAPT1 12:19 1/27 M WAITING DEPENDENCIES LATE
HRMCPYLR 23:15 11/24 Q WAITING SUBMISSION READY
HRMCPYLR 23:16 11/24 Q WAITING SUBMISSION READY
HRMPBQIN 23:44 11/24 HRMPLOG PM WAITING DEPENDENCIES LATE
HRMPCHGR 23:1 11/24 PM WAITING DEPENDENCIES LATE
HRMPCHGX 23:32 11/24 HRMPPTC PM WAITING DEPENDENCIES LATE
HRMPCr1p 23:33 11/24 PM WAITING DEPENDENCIES LATE
HRMPEDB1 22:27 11/24 HRMP32 P WAITING DEPENDENCIES LATE
HRMPKEYC 23:1 11/24 M WAITING DEPENDENCIES LATE
HRMPJQIN 22:3 11/24 HRMPOLCH PM WAITING DEPENDENCIES LATE
 
The panel below shows the result of entering the command shown above.

 CA-Jobtrac Scheduled Event Display ROW 1 TO 2 OF 2


COMMAND ===> ADA,K=L,T=22-23 SCROLL ===> PAGE
yy/mm/dd hh:mm
Event ----Target----Successor Dep Current CMD= ADA,K=L,T=2
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- -----------------------------------------
ADANN2 22:4  11/13 ADANN3 P WAITING DEPENDENCIES LATE
ADANN3 22:4  11/13 ADANN4 P WAITING DEPENDENCIES LATE
 BOTTOM OF DATA 
 

1-38 Operator Guide

 1.12 Changing Displays and Executing Commands

1.12.3 Using Line Commands

Most CA-Jobtrac displays show lists of events. You can use line commands to
affect a single event on the display. You can perform some action on the event
or access a display of detailed information about the event. Line commands
that can be used on Scheduled Event Display and Scheduled Event Network
panels are listed in the line commands section of the Reference Summary. Line
commands that can be used on other panels are listed with the respective
panel descriptions.

Follow the steps below to affect a specific event on a display using line
commands.
1. Position the cursor in the blank field to the left of the event you want to
affect.
2. Type the one-character line command that performs the action you want.
3. Press Enter to execute the command.

Example: The current display is a Scheduled Event Display panel showing

all events that have completed. You want to purge RANDDXX1 from the
current schedule and place it on the history archive. The panel below shows
the P line command typed on the line for RANDDXX1. When you press Enter,
RANDDXX1 is purged from the current schedule and placed on the history
archive.

 CA-Jobtrac Scheduled Event Display ROW 1 TO 25 OF 25


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Event ----Target----Successor Dep Current CMD= K=C
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ---------------------------------------
P RANDDXX1 14:1 12/6 COMPLETED. J5279. AT 14:1-126
RANDDXX1 14:16  12/6 RANDDXX COMPLETED. J5279 AT 13:56-12/6
RANDDXX1 14:18  12/6 RANDDXX COMPLETED. J5251 AT 13:59 12/6
RANDDXX1 14:19  12/6 RANDDXX COMPLETED. J5261 AT 14: 12/6
RANDDXX2 14:3  12/6 COMPLETED. J5299 AT 14:3 12/6
RANDDXX2 14:36  12/6 COMPLETED. J5243 AT 13:57 12/6
RANDDXX2 14:38  12/6 COMPLETED. J5253 AT 13:59 12/6
RANDDXX3 14:56  12/6 COMPLETED. J5253 AT 13:57 12/6
RANDDXX3 14:58  12/6 COMPLETED. J5253 AT 13:59 12/6
RANDDYY1 13:58 1/3 O COND CODE CHK. J 5113 AT 13:59 1/3
RANDDYY1 13:58 1/3 JO PURGED BY: CB1RH53 . AT 13:59 1/3
TESTJOB8 2: 1/23 TESTJOBA O COND CODE CHK. J 556 AT 2:1 1/23
DHF395 11:16 12/2 SCHEDULE UPDATED AT 11:17 12/2
FW 9:15 12/2 SCHEDULE UPDATED AT 9:15 12/2
JOBARCH 7:54 12/2 ARCHIVAL COMPLETE AT 7:55 12/2
RANDDAL 2:12 1/22 SCHEDULE UPDATED AT 13:59 12/2
 

Chapter 1. Introduction 1-39

1.13 Using Online Help

1.13 Using Online Help

You can get online information about CA-Jobtrac by either pressing the ISPF
HELP PF key or entering the HELP command.

The main help panel for that panel appears.

The HELP command can be entered in the COMMAND field of any

CA-Jobtrac panel.

Online Help for an Online Message: Whenever a message appears in the

upper right corner of a CA-Jobtrac display, you can invoke online help to
display a brief note explaining the message. For example, if LOCATION
ADDED appears in the upper right corner of a display, the HELP command
displays the message REQUESTED LOCATION HAS BEEN ADDED TO
DISPLAY.

If you press the HELP PF key or enter the HELP command again while a help
message is on the panel, the main help panel for that panel appears.

Exiting Online Help: At any point in help, press the END PF key to return to
the CA-Jobtrac panel from which you invoked online help.

1-40 Operator Guide

 1.14 Displaying the Scheduled Event Display Panel

1.14 Displaying the Scheduled Event Display Panel

The Scheduled Event Display panel is the primary source of information about
events on the current schedule. The panel is a pageable display of such
information as target time and date, successor events, and current status for
each event on the current schedule. You can use line commands on any event
on this panel to display detailed information about the event or to perform
some action on the event.

You can control which events are displayed on the Scheduled Event Display.
For example, you can display information about all events on the current
schedule by entering the command D or the command RALL (reset/update
and display entire schedule). You can also combine search key commands to
display only events with specific characteristics, such as events with a specific
prefix that are late. You can display a single event by entering the event's
name in the COMMAND field.

For more detailed information about the Scheduled Event Display panel and
how to use it, see 1.14.1, “Description of the Scheduled Event Display Panel.”

1.14.1 Description of the Scheduled Event Display Panel

The Scheduled Event Display panel is a scrollable display that lists information
about events on the current schedule. Events on the panel can be acted on
individually by line commands, by commands entered at the COMMAND
field, or by MVS console commands.

Panel Sample: The panel below shows a sample Scheduled Event Display
panel:

 CA-Jobtrac Scheduled Event Display ROW 1 TO 18 OF 21


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 14:3
Event ----Target----Successor Dep Current CMD= RALL
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ---------------------------------------
ACAPHIST 16:36  12/18 M WAITING DEPENDENCIES LATE
ACAPD 1:5 12/17 ACGL25 P WAITING DEPENDENCIES LATE
ACAP1 AS-AP 1/23 J WAITING RSTRT J 5643 LATE
ACAPD 1:3 12/17 ACAPD M WAITING DEPENDENCIES LATE
ACAP1D 1:5  12/17 ACAP15D M WAITING DEPENDENCIES LATE
ACAP11R 1:4  12/18 ACAPD J WAITING DEPENDENCIES LATE
ACAP12R 1:4  12/18 ACAPD J WAITING DEPENDENCIES LATE
ACAP15D 1:5  1/21 ACGL2D J WAITING DEPENDENCIES LATE
ACAP15D 1:5  12/17 ACGL2D PD WAITING DEPENDENCIES LATE
ACAP35R 1:4  12/18 ACAPD J WAITING DEPENDENCIES LATE
ACAR4 1:3  1/21 ACAR43 P WAITING DEPENDENCIES LATE
ACAR4 15:6 11/1 M WAITING DEPENDENCIES LATE
ACAR4 1:3  12/17 ACAR43 PM WAITING DEPENDENCIES LATE
ACAR41 1:5  1/21 ACGL21R P WAITING DEPENDENCIES LATE
ACAR41 1:5  12/17 ACGL21R PM WAITING DEPENDENCIES LATE
ACCN21M 1:3  1/21 P WAITING DEPENDENCIES LATE
 

Chapter 1. Introduction 1-41

1.14 Displaying the Scheduled Event Display Panel

Fields Explained: The following table briefly describes the fields that provide
information about each event. See 5.1, “Scheduled Event Display Panel” for
more detailed descriptions of this panel and how to use it.

Field Function
Event Name Shows name of event on current schedule.
Target Time and * Shows the event's target submission time, whether
the event's start (submit) time is the same as the
target time, and whether the event is scheduled to
run at intervals.
Target Date Shows the date for which submission of the event is
scheduled.
Successor Event(s) Shows the first successor to the event (if any). An *
(asterisk) in the last character of the event name
indicates that more than one successor exists.
Dep Codes Indicates dependencies that must be satisfied before
the event can be submitted.
Current Status Provides an abbreviated summary of the event's
current status. For example, WAITING
DEPENDENCIES indicates that the event has
dependencies that must be met before it can be
submitted. WAITING SCHEDULED TIME indicates
that no dependencies remain, but the event's
scheduled submission time has not arrived.

1-42 Operator Guide

 1.15 Defining Your Own Program Function Keys

1.15 Defining Your Own Program Function Keys

You can assign nondefault PF (Program Function) key definitions using the
User Options panel. For example, you can set a PF key to execute a
frequently-used CA-Jobtrac command, such as the search command K=LAW.

The functions you assign are in effect only while you are in CA-Jobtrac. When
you exit CA-Jobtrac, the default ISPF PF key definitions are reinstated. Your PF
key definitions apply only to your sessions. Other users can define different
functions for their PF keys.

1.15.1 User Options Panel

Displaying the Panel: You display the User Options panel by entering the
command SYS USER in the COMMAND field of the CA-Jobtrac primary,
Scheduled Event Display, Scheduled Event Network, or Business Group Status
panels.

Panel Sample: The panel below shows a sample User Options panel.

 CA-Jobtrac User Options


COMMAND ===> yy/mm/dd hh:mm

Shift 1: 8-16 Display Date: ALL

Shift 2: 161-2359
Shift 3: -759

PFK1 : HELP PFK13 : HELP

PFK2 : SPLIT PFK14 : SPLIT
PFK3 : END PFK15 : END
PFK4 : RETURN PFK16 : RETURN
PFK5 : RFIND PFK17 : RFIND
PFK6 : RCHANGE PFK18 : RCHANGE
PFK7 : UP PFK19 : UP
PFK8 : DOWN PFK2 : DOWN
PFK9 : SWAP PFK21 : SWAP
PFK1 : LEFT PFK22 : LEFT
PFK11 : RIGHT PFK23 : RIGHT
PFK12 : RETRIEVE PFK24 : RETRIEVE

Press Enter to update options or END to exit without making changes.

 
Panel Description: The top part of this panel shows:
■ The default time range to be used with the SHIFTn search key command.
Using the above panel as an example, entering the search command
SHIFT2 would display a Scheduled Event Display panel listing events
scheduled from 4:01 PM to 11:59 PM (1601-2359).
■ The default dates to be displayed on Scheduled Event Display panels.
Using DISPLAY DATE: ALL as an example, Scheduled Event Display
panels would list events scheduled for any date.

Chapter 1. Introduction 1-43

1.15 Defining Your Own Program Function Keys

The remainder of the User Options panel lists the current definitions for each
PF key.

Procedure: Follow the steps below to define PF (Program Function) keys

using the User Options panel.
1. Position the cursor in the COMMAND field of the CA-Jobtrac primary,
Scheduled Event Display, Scheduled Event Network, or Business Group
Status panels.
2. Type SYS USER and press Enter to display the User Options panel.
3. Position the cursor in the PFKnn field, where nn is the number of the PF
key you want to define.
4. Type the command you want to define for the PF key. If you want to
define more PF key functions, repeat steps 3 and 4.
5. Press Enter to save the function definitions you have entered. Press the
END PF key to exit the User Options panel without saving any of your
changes.

Example: Suppose you want to set PF13 to execute the CA-Jobtrac command
RALL (reset/update and display all events on the current schedule). The first
step is to display the User Options panel by entering the SYS USER command,
as shown in the panel below.

 CA-Jobtrac

COMMAND ===> SYS USER yy/mm/dd 16:55

Primary Commands:
RALL - List all events CA-JCLTRAC- JCL analysis system
J=evnm - List events beg. w evnm ISERVE - CA-GSS IMOD facility
K=status - List events w/ status JCL - Edit production JCL
D=dep - List events w/ deps SCL - Edit SCL
B=bgname - List events of a bus. grp. SYS OPTS - Update global options
T=hhmm - List events by target time SYS HOLS - Holiday calendar maint.
BUSGRP - Business group status SYS CYCS - Cyclic calendar maint.
ADD - Add event to schedule JTS - Table services
GSO - Generate schedules online OUT - Sysout capture

 The following line commands will be available for SCHEDULED EVENT DISPLAY:
 - CA-View sysout brwse H - Event history R - Rerun/restart
A - Release dependencies I - Audit history S - Select (detail)
C - Cond code exceptions L - Dependent jobstream T - Create/edit temp JCL
D - Delete event M - Manual actions V - Volume pull list
E - Edit JCL/SCL O - Browse sysout W - Workload analysis
F - Display DSN triggers P - Purge event Y - CPM info
G - GSO Q - Sysview Jobsum ? - View documentation
 

1-44 Operator Guide

 1.15 Defining Your Own Program Function Keys

After you enter the SYS USER command, the User Options panel is displayed.
To define PF13's function as required, you would type RALL in the PF13 field
(see the panel below). When you press Enter, the change is saved and PF13
has the RALL function. You are returned to the panel where you entered the
SYS USER command.

 CA-Jobtrac User Options ROW 1 TO 18 OF 21


COMMAND ===> yy/mm/dd hh:mm

Shift 1: 8-16 Display Date: ALL

Shift 2: 161-2359
Shift 3: -759

PFK1 : HELP PFK13 : HELP

PFK2 : SPLIT PFK14 : SPLIT
PFK3 : END PFK15 : END
PFK4 : RETURN PFK16 : RETURN
PFK5 : RFIND PFK17 : RFIND
PFK6 : RCHANGE PFK18 : RCHANGE
PFK7 : UP PFK19 : UP
PFK8 : DOWN PFK2 : DOWN
PFK9 : SWAP PFK21 : SWAP
PFK1 : LEFT PFK22 : LEFT
PFK11 : RIGHT PFK23 : RIGHT
PFK12 : RETRIEVE PFK24 : RETRIEVE

Press ENTER to update options or END to exit without making changes.

 

Chapter 1. Introduction 1-45

1.15 Defining Your Own Program Function Keys

1.15.2 BYTIME AND BYNAME Sort Display

The BYTIME and BYNAME commands have been brought back to the
Scheduled Event Display, Sysout Capture, and Change Audit History. They
work as follows (A = ascending, D= descending):

Scheduled Event Display

SORT Event-Name(A),Target-Date(A),Target-Time(A)
BYTIME Target-Date(D),Target-Time(D),Event-Name(A)
BYNAME Event-Name(A),Target-Date(D),Target-Time(D)

Sysout Capture
SORT Event-Name(A),Run-Date(A),Start-Time(A),Event-Number(A)
BYTIME Run-Date(D),Start-Time(D),Event-Name(A),Event-Number(A)
BYNAME Event-Name(A),Run-Date(D),Start-Time(D),Event-Number (A)

Change Audit History

SORT (no parameters) Event-Name(A),Version-Number(A),Altered-By(A),
Date(A),Time(A),Description(A)
BYTIME Date(D),Time(D),Event-Name(A),Version-Number(A),
Altered-By(A),Description(A)
BYNAME Event-Name(A),Version-Number(A),Altered-By(A),
Date(D),Time(D),Description(A)

BYNAME and BYTIME can be entered as search parameters on the Scheduled

Event Display. If entered by themselves, they perform an RALL and then do
the sort.

The default SORT sequences are exactly as they were in 3.2 base before they
were changed to accommodate the removal of the BYTIME and BYNAME
commands.

For Sysout Capture, a parameter of BYCAP may also be used. This will sort
the display in capture file sequence.

1-46 Operator Guide

Chapter 2. Using Operator Commands

This chapter describes using CA-Jobtrac operator commands.

Chapter 2. Using Operator Commands 2-1

2.1 Documenting IPLs

2.1 Documenting IPLs

During an IPL (Initial Program Load), CA-Jobtrac loads MVS exits that let
CA-Jobtrac provide continuous event execution information. CA-Jobtrac
records information about each IPL, such as the time, date, system ID, and IPL
type. CA-Jobtrac also records the names of any scheduled events that were
executing at the time the system stopped.

An optional CA-Jobtrac feature requires any user performing an IPL to record

his name and a brief explanation of why the IPL is being performed. This
information is added to the CA-Jobtrac IPL record. You can view it on the
&opsy. IPL History panel by entering the IPLS command on the &prodo.
primary, Scheduled Event Display, Scheduled Event Network, or Business
Group Status panels.

The IPL operator reply option is enabled during installation (for more
information, see the Getting Started).

2.1.1 IPL Messages

The following WTOR messages appear when you perform an IPL, if the IPL
operator reply option is enabled:
1 TRAC4A ENTER IPL REASON/COMMENT
2 TRAC41A ENTER YOUR LAST NAME

2-2 Operator Guide

 2.1 Documenting IPLs

2.1.2 Replying to IPL Messages

Procedure: Follow these steps to reply to prompts for IPL documentation.
1. When you perform an IPL and the WTOR message TRAC400A appears,
issue a one-line response stating the reason the IPL is being performed.
Specify the two-digit number of the WTOR message in your reply (see the
following example).
2. When the WTOR message TRAC401A appears, enter the two-digit number
of the WTOR message and your last name.

Example: You are performing an IPL following weekly IBM maintenance,

and the following message appears on the console:
1 TRAC4A ENTER IPL REASON/COMMENT

You issue the following reply, including the two-digit number assigned to the
original message (01):
1 IPL AFTER WEEKLY IBM MAINTENANCE

The following message then appears:

2 TRAC41A ENTER YOUR LAST NAME

You issue the following reply (assuming your last name is ANDERSON):
2 ANDERSON

When initialization completes successfully, a message similar to the following

appears:
CA-JOBTRAC - INTERNAL INITIALIZATION COMPLETE

Several other messages beginning with CA-JOBTRAC display the status of

other enabled or disabled components.

Chapter 2. Using Operator Commands 2-3

2.2 Starting a Scan Task

2.2 Starting a Scan Task

When to Start a Scan Task: A CA-Jobtrac scan task should be started as
soon as possible after an IPL; however, CA-Jobtrac STC should be the last
system-related task using dynamic hooks.

How to Start a Scan Task: You start a scan task by using the Start JOBTRAC
command. Parameters to the command let you perform additional functions.

Starting More Than One Scan Task: If you start more than one CA-Jobtrac
scan, you must start each one with a unique name and token. (For more
information, see the Getting Started.) This enables the various components of
CA-Jobtrac to access the proper current schedule. While using more than one
CA-Jobtrac, ensure that what you do with CA-Jobtrac uses the one you really
want.

2.2.1 The Start JOBTRAC Command

The MVS Start JOBTRAC command starts a CA-Jobtrac scan task. You can
include optional parameters to perform specific actions at startup.

Syntax: The syntax of the Start JOBTRAC command is as follows:

S JOBTRAC
──S JOBTRAC.taskname─┬─────────────────────────────┬──────────
└─,PARM=─┬─HOLD────────────┬──┘
├─ARCH────────────┤
│ ┌──┐ │
└─'OPTS=─┼────┼─'─┘
└─nn─┘

| Note: CA-Jobtrac no longer puts itself on hold automatically.

| TRAC310W is issued if no RESOURCE file is available. CA-Jobtrac

| continues processing.

Descriptions of Command Elements: Following are descriptions of the

elements of the Start JOBTRAC command:

Element Description
S JOBTRAC.taskname Required command. Starts the CA-Jobtrac task
and assigns the task name taskname. Commands
issued after the scan task is started should see
the scan task as taskname.

2-4 Operator Guide

 2.2 Starting a Scan Task

Element Description
PARM=HOLD Imposes a hold state when CA-Jobtrac is started.
A hold state prevents event submission by the
scan task, but allows all other functions,
including sysout archival and event execution
tracking, to continue.
Individual jobs can be released to run while the
schedule is on hold by using the * and FORCE
commands from the ISPF panels. See the *
(asterisk) command description in “Line
Commands.”
PARM=ARCH Invokes a sysout archival, to be executed before
any checkpoint processing. A tape mount may be
required. For more information about sysout
archival, see Chapter 6, “Managing Sysouts.”
PARM='OPTS=nn' For testing purposes, starts CA-Jobtrac with the
user-specified PPOPTION member JOBTRAnn,
where nn is a two-digit number matching the nn
in the parameter. The default member is
JOBTRA00. The member JOBTRAnn contains
initialization parameters, options, product code
security, and other information for CA-Jobtrac
and related products. This member must reside
in the PPOPTION library, and you must specify
its location on the TRACPARM DD statement in
the JOBTRAC STC.

Examples: The following command starts a CA-Jobtrac scan task and assigns
it the task name taskname:
S JOBTRAC.taskname

The following command starts a CA-Jobtrac scan task and places the task on
hold:
S JOBTRAC.taskname,PARM=HOLD

The following command starts a CA-Jobtrac scan task with the PPOPTION
member JOBTRA02:
S JOBTRAC.taskname,PARM='OPTS=2'

Chapter 2. Using Operator Commands 2-5

2.3 Stopping a Scan Task

2.3 Stopping a Scan Task

To terminate a CA-Jobtrac scan task, issue either of the following MVS
commands:
P taskname
F taskname,STOP

If a CA-Jobtrac scan task is unable to terminate normally, issue the following

MVS command:
C taskname

2-6 Operator Guide

 2.4 Using Task Commands

2.4 Using Task Commands

The following topics discuss a variety of functions performed by the task
commands.

2.4.1 Modifying the Current Schedule

In the event of a VTAM or TSO failure, you can manipulate the CA-Jobtrac
current schedule using MVS modify (F) commands.

Command Syntax: Following is the syntax of the MVS modify command

used to manipulate the current schedule:

F
──F taskname──,─┬─ADD─┬─=eventname─┬───────┬───┬────────┬──────
└─RUN─┘ └─.vvvv─┘ └─,L=nnn─┘
──┬────┬──┬──────────────────────────────┬──┬────┬──┬────┬──────
└─,A─┘ └─,A=─┬─CLPNAME,arg─────────┬──┘ └─,C─┘ └─,D─┘
├─command─────────────┤
├─imod-arg────────────┤
└─shellscriptname,arg─┘
──┬────┬──┬─────────────┬──┬────┬──────────────────────────────
└─,E─┘ └─,N=nodename─┘ └─,U─┘

F
──F taskname──,─┬─REL─┬─=eventname─┬───────────┬──────────────
├─PRG─┤ ├─.vvvv─────┤
└─DEL─┘ └─.mmddvvvv─┘

Chapter 2. Using Operator Commands 2-7

2.4 Using Task Commands

Descriptions of the Command and Parameters: The following are

descriptions of the modify command and its parameters used to manipulate
the current schedule:

Command or Description
Parameter
F taskname Required command. taskname is the name of the scan
task assigned at startup.
ADD Adds the specified event to the current schedule with
a manual dependency (code M). The .mmddvvvv
option is not valid with this parameter.
RUN Adds the specified event to the current schedule for
immediate submission (no dependencies). The
.mmddvvvv option is not valid with this parameter.
REL Releases dependencies from the specified event to
allow immediate submission. Releases all
dependencies except the ?, O, and E dependencies.
The current date must match the date of the event to
use this parameter with no date option. If the dates
do not match, use the .mmddvvvv option.
PRG Purges the specified event from the current schedule
and subtracts one from the predecessor count of any
successor to the event. The current date must match
the date of the event to use this parameter with no
date option. If the dates do not match, use the
.mmddvvvv option.
DEL Deletes the specified event from the current schedule
without updating any successors. The current date
must match the date of the event to use this
parameter with no date option. If the dates do not
match, use the .mmddvvvv option.

Description of eventname: The eventname variable specifies the name of the

event to be affected by the command.

2-8 Operator Guide

 2.4 Using Task Commands

Descriptions of the Options: The following are descriptions of the options

used with the command to manipulate the current schedule:

Option Description
.vvvv Optionally, specifies the version number of the event. Replace vvvv
with a number (1-9999). The following defaults depending upon the
parameter used:
ADD The next available version number for the event is
assigned
RUN
REL The next available version number for the event is
assigned
PRG
DEL
.mmddvvvv Optionally, specifies the month, day, and version number of the
event. Replace mm with the month (1-12), dd with the day (1-31), and
vvvv with a number (1-9999). The following defaults apply for vvvv:
ADD The next available version number for the event is
assigned
RUN
REL Version number 1 is assigned
PRG
DEL Version number 1 is assigned
,L=nnn Optionally, specifies the location ID of the event. Replace nnn with a
three-digit location ID number (000-253). This is not used with DEL,
REL, and PRG.
,A Specifies that the event is an AS/400 CLP using the CALL command.
,A={CLPname,arg| This option is now dependent upon the type of event as specified by
command|imod-arg| the options [,A] [,C] [,E] or [,U].
shellscriptname,arg}

Chapter 2. Using Operator Commands 2-9

2.4 Using Task Commands

Option Description
[,A][,A=CLPname,arg] Specifies an argument to pass to the named AS/400 CLP. Replace arg
with a 1- to 255-character argument. CLPname,arg can contain
embedded blanks and commas. To include embedded blanks or
commas, enclose CLPname,arg with single quote marks. For example,
specify 'CLPname,arg' where CLPname,arg includes embedded blanks
or commas. To include embedded single quotes, replace the
embedded single quote mark with a double quote mark in the
CLPname,arg. For example, specify 'CLPname,1"2"3' where 1'2'3 is the
argument. If the CLPname is not specified, the default CLPname that
is used is the Alternate Member name (if one is specified) or the
Event Name (if no Alternate Member Name is specified).
[,C][,A=command] Specifies the exact command to be executed at a particular remote
node. command can contain embedded blanks and commas. To
include embedded blanks or commas, enclose command with single
quote marks. For example, specify 'command' where command
includes embedded blanks or commas. To include embedded single
quotes, replace the embedded single quote mark with a double quote
mark in the command. For example, specify 'print"DAILY"' where
print'DAILY' is the command. The UNIX environment is
case-sensitive. Be aware that the ADD and RUN command
parameters of the MVS modify command (F taskname,) will translate
the command to all uppercase characters that may produce
unexpected results when passed to UNIX.
[,E][,A=imod-arg] Specifies an argument to pass to the named REXX IMOD. Replace
imod-arg with a 1- to 255-character argument. imod-arg can contain
embedded blanks and commas. To include embedded blanks or
commas, enclose imod-arg with single quote marks. For example,
specify 'imod-arg' where imod-arg includes embedded blanks or
commas. To include embedded single quotes, replace the embedded
single quote mark with a double quote mark in the imod-arg. For
example, specify 'imod-1"2"3' where 1'2'3 is the argument.

2-10 Operator Guide

 2.4 Using Task Commands

Option Description
[,U][,A=shell scriptname,arg] Specifies an argument to pass to the named UNIX Korn shell script.
Replace arg with a 1- to 255-character argument. shellscriptname,arg
can contain embedded blanks and commas. To include embedded
blanks or commas, enclose shellscriptname,arg with single quote marks.
For example, specify 'shellscriptname,arg' where shellscriptname,arg
includes embedded blanks or commas. To include embedded single
quotes, replace the embedded single quote mark with a double quote
mark in the shellscriptname,arg. For example, 'shellscriptname,1"2"3'
where 1'2'3 is the argument. If the shellscriptname is not specified, the
default shellscriptname that is used is the Alternate Member name (if
one is specified) or the Event Name (if no Alternate Member Name is
specified). The UNIX environment is case-sensitive. Be aware that the
ADD and RUN command parameters of the MVS modify command
(F taskname,) will translate the argument to all uppercase characters
that may produce unexpected results when passed to UNIX.
,C Specifies that the event defines a command to be executed at a
particular remote node.
,D Specifies that the event is a dummy job. You must use this option if
the event is a dummy job.
,E Specifies that the event is a REXX IMOD. You must use this option if
the event is a REXX IMOD.
,N=nodename Specifies the CA-GSS node name (up to 16 characters) of the
executing node for the named event.
,U Specifies that the event invokes a UNIX Korn shell script using the
UNIX ksh command.

Chapter 2. Using Operator Commands 2-11

2.4 Using Task Commands

Examples: The following command adds TESTJOB1 to the current schedule

with a manual dependency:
F taskname,ADD=TESTJOB1

The following command releases all dependencies from TESTJOBB:

F taskname,REL=TESTJOBB

The following command adds PRODJOB1 to the current schedule with a

manual dependency and a version number of 2:
F taskname,ADD=PRODJOB1.2

The following command releases all dependencies from the event named
PRODJOBA with a location ID of 020:
F taskname,REL=PRODJOBA,L=2

The following command adds the REXX IMOD IMODA to the current
schedule with a manual dependency (code M):
F taskname,ADD=IMODA,E

2.4.2 Changing Target Times for Scheduled Events

Another MVS modify (F) command lets you change the target time for events
on the current schedule. You can change the times of all events on the
schedule, a specific event, a subset of events, or events whose target times fall
within a specified time range.

Command Syntax: Following is the syntax of the MVS modify command

used to change target times for events on the current schedule:

F
──F taskname──,ADJ(─┬─ALL───────┬──┬────────────────────┬─)────
├─eventname─┤ └─,hhmmmmdd-hhmmmmdd─┘
└─prefix
───┘
──,──┬─+─┬──hh─┬────┬──────────────────────────────────────────
└─–─┘ └─mm─┘

2-12 Operator Guide

 2.4 Using Task Commands

Descriptions of Parameters: Following are descriptions of the elements of

the command used to adjust target times for scheduled events:

Element Description
F taskname,ADJ Required command. taskname is the
scan task name assigned at startup.
ALL Specifies that the target times for all
events on the current schedule are to
be adjusted.
eventname Specifies that only the event named
eventname is to have its target time
adjusted.
prefix* Specifies that any events beginning
with prefix are to have their target
times adjusted. An * (asterisk) must
follow the prefix.
hhmmmmdd-hhmmmmdd Specifies that only events having
target times within the specified time
range are to have their target times
adjusted. This variable is used with
ALL, eventname, or prefix* to further
define the events to be adjusted.
The first hhmmmmdd defines the
beginning of the period, where hhmm
is the time (0000- 2359) and mmdd is
the date (0101-1231). The second
hhmmmmdd defines the end of the
time period.
{+|-}hh[mm] Adds (+) or subtracts (-) the specified
number of hours (hh) and, optionally,
minutes (mm) from the target times
of specified events.

Examples: The following command adds one hour to the target time of the
event APJOB1 (for example, changes the target time from 0200 to 0300):
F taskname,ADJ(APJOB1),+1

The following command subtracts 30 minutes from the target times of all
events beginning with the prefix AP scheduled between 4:00 p.m. (1600) and
11:59 p.m. (2359) on October 21 (1021):
F taskname,ADJ(AP,16121-2359121),-3

Chapter 2. Using Operator Commands 2-13

2.4 Using Task Commands

2.4.3 Controlling a CA-Jobtrac Task

There are several parameters to the MVS modify (F) command with which you
control a CA-Jobtrac scan task.

Command Syntax: Following is the syntax of the MVS modify command

used to control a CA-Jobtrac scan task:

F
──F taskname──,──┬─STOP────┬──────────────────────────────────
├─HOLD────┤
├─RELEASE─┤
├─RESET───┤
└─BACK────┘

Descriptions of Parameters: Following are descriptions of the elements of

the command used to control the CA-Jobtrac scan task:

Element Description
F taskname Required command. taskname is the scan task name
assigned at startup.
STOP Terminates CA-Jobtrac (stops the scan task). This
parameter has the same effect as the command P
taskname (see 2.3, “Stopping a Scan Task”).
HOLD Prevents event submission by the scan task. All other
functions, including sysout archival and event execution
tracking, continue.
RELEASE Releases the scan task from the hold condition.
RESET Releases the checkpoint (current schedule) IN USE
attribute. The IN USE attribute is set by programs that
perform large-scale schedule updates. For more
information, see message TRAC004W in the Message
Guide. Improper use of this parameter can cause
schedule errors. Use only when instructed to do so by
Computer Associates Technical Support.
BACK Stops the CA-Jobtrac task and deactivates all resident
components. When CA-Jobtrac is restarted, it
reinitializes. Use only when instructed to do so by
Computer Associates Technical Support.
When you issue a BACK command for CA-Jobtrac to
deactivate the resident components, this leaves
approximately 90 KB of CSA and approximately 1.5 MB
of ECSA. This however depends on the sizes of the
table services such as ADR, JMF, SCS, CCPF, and AMR.

2-14 Operator Guide

 2.4 Using Task Commands

Example: The following command releases the scan task from the hold
condition:
F taskname,RELEASE

2.4.4 Other Task Commands

The following task commands perform a variety of CA-Jobtrac functions.

F
──F taskname,ACTSYS=sysid─────────────────────────────────────

Switches event submission processing from the current system to the system
specified by sysid. taskname is the name of the scan task assigned at startup.
Issue only on the current primary system. For more information, see the
Reports, Maintenance, and Recovery Guide.

F
──F taskname,AUTH─────────────────────────────────────────────

Reinitializes the TRACAUTH table for system-wide use. For more information
about the TRACAUTH table, see the Getting Started. taskname is the name of
the scan task assigned at startup.

F
──F taskname,C=scstable───────────────────────────────────────

Replaces the current storage resident SCS (System Command Scheduling) table
with the table specified by scstable. For more information about scheduling
system commands, see the Extended Scheduling Services Guide. taskname is the
name of the scan task assigned at startup.

F
──F taskname,D=adrtable───────────────────────────────────────

Replaces the current storage resident ADR (Automatic Dataset Recognition)

table with the table specified by adrtable. For more information about
scheduling events based on data sets closing, see the Extended Scheduling
Services Guide. taskname is the name of the scan task assigned at startup.

Chapter 2. Using Operator Commands 2-15

2.4 Using Task Commands

F
──F taskname,M=amrtable───────────────────────────────────────

Replaces the current storage resident AMR (Automatic Message Recognition)

table with the table specified by amrtable. For more information about
automating message replies, see the Extended Scheduling Services Guide.
taskname is the name of the scan task assigned at startup.

F
──F taskname,PFT=pfttable─────────────────────────────────────

Replaces the current storage resident PFT (Program Filter table) table with the
table specified by pfttable.

F
──F taskname,NOIPL────────────────────────────────────────────

Removes the Automatic Message Recognition table IPLTABLE from main

storage. The IPLTABLE provides AMR services during IPLs.

F
──F taskname,XON (1)
─────────────────────────────────────────────
Note:
1 See the XOFF Note.

XON starts Automatic Message Recognition services for the system on which
the command is entered.

F
──F taskname,XOFF (1)
────────────────────────────────────────────
Note:
1 See the XOFF Note.

XOFF stops Automatic Message Recognition services for the system on which
the command is entered.
Note: To use these commands, they must be placed in the TRACMDS
Partition Data Set as a member with member name of the command.
Example:
member name: XON
member data: XON

2-16 Operator Guide

 2.4 Using Task Commands

When executing this command, you should receive the TRAC029I

message as confirmation of the successful command execution. The
message will appear in the JOBTRAC STC JES JOBLOG. If an 'IEE305I
xxxx COMMAND INVALID' (where xxxx is the command) appears in
the Operating System Log, the message processing exit is not active. To
activate the message exit, enter the MVS Operating System command:
KM,UEXIT=Y

F
──F taskname,cmdmbr───────────────────────────────────────────

Initiates execution of the command set contained in the member specified by

cmdmbr. The command set member is a PDS member containing a series of
commands to be executed. For more information about creating and
scheduling command sets, see the Extended Scheduling Services Guide. taskname
is the name of the scan task assigned at startup.

F
──F taskname,DUMP─────────────────────────────────────────────

Creates a diagnostic dump for problem resolution. taskname is the name of the
scan task assigned at startup.

S
──S DUMPV3────────────────────────────────────────────────────

Uses an alternate method to create a diagnostic dump if the F taskname,DUMP

command is disabled because of a CA-Jobtrac hung condition.

Chapter 2. Using Operator Commands 2-17

2.4 Using Task Commands

F
──F taskname,─┬─OPTS──────────┬───────────────────────────────
│ ┌──┐ │
└─OPTS=─┴─nn─┴──┘

Reinitializes all internal CA-Jobtrac options. Optionally, replace nn with a

two-digit number specifying a nondefault PPOPTION member (JOBTRAnn).
The default is JOBTRA00. taskname is the name of the scan task assigned at
startup.
| Note: TRAC310W is issued if no RESOURCE file is available. CA-Jobtrac
| continues processing.

Caution
The F taskname,OPTS[=nn|00] command refreshes global options, holiday
and cyclic calendars, Resource member, and some of the options set in
JOBTRAnn. For details on which options can be updated by this
command, see the Getting Started. For a similar command, see JICAUPD.

F
──F taskname,JICAUPD──────────────────────────────────────────

Refreshes global options, holiday, and cyclic calendars. Does not refresh or
reset resources or options set in JOBTRAnn.

F
──F taskname,JMFLOD───────────────────────────────────────────

Loads the JMF table. Errors will abort the load. taskname is the name of the
scan task assigned at startup. Also see the ZJMF command.

F
──F taskname,JMFVFY───────────────────────────────────────────

Validates the JMF table. The load does not occur. Only the first error is listed.
taskname is the name of the scan task assigned at startup.

F
──F taskname,JMFFOR───────────────────────────────────────────

Forces the JMF table to load, even if there are errors. A load always occurs.
taskname is the name of the scan task assigned at startup.

2-18 Operator Guide

 2.4 Using Task Commands

F
──F taskname,ZJMF─────────────────────────────────────────────

Stops the symbolic resolution. A new load is required. This command is the
same as the F taskname,JMFST command. taskname is the name of the scan task
assigned at startup.

F
──F taskname,TRACEON──────────────────────────────────────────

Turns on the diagnostic trace facility to capture data. This can be helpful
during problem resolution. taskname is the name of the scan task assigned at
startup.

These diagnostic DDs are in the JOBTRAC STC. You need to uncomment them
to use them.
//SYSTRACE DD SYSOUT=&SOUT ----> GJTRMSTR
//SUBTRACE DD SYSOUT=&SOUT ----> GJTRSUB
//SQIOTRC DD SYSOUT=&SOUT ----> GJTRSQIO
//JFIOTRC DD SYSOUT=&SOUT ----> GJCFIO
//WTRTRACE DD SYSOUT=&SOUT ----> GJTRVWTR
//JOBVTRC DD SYSOUT=&SOUT ----> GJTRCKII
//SEQHTRC DD SYSOUT=&SOUT ----> GJTRSEQH
//TRT2TRC DD SYSOUT=&SOUT ----> GJTRTRT2

You can change the class to a different standard output print class if you wish.
You can change these statements to comments during normal CA-Jobtrac
operation to avoid unnecessary printouts. If you need the trace facility, you
can change them back to active DD statements and reinitialize CA-Jobtrac.

F
──F taskname,TRACEOFF─────────────────────────────────────────

Turns off the diagnostic trace facility. taskname is the name of the scan task
assigned at startup.

Chapter 2. Using Operator Commands 2-19

2.4 Using Task Commands

F
──F taskname,─┬─WARNPCT──────────┬────────────────────────────
│ ┌─8─┐ │
└─WARNPCT=─┴─nn─┴──┘

Sets the percentage of how full the checkpoint can be. Once this percentage is
reached, message TRACWARN - JOBTRACx CHECKPOINT OVER xx% USED
is issued. taskname is the name of the scan task assigned at startup. nn is the
percentage you want to specify. nn must be numeric, greater than 0, and less
than 100. Leading zeros are not required. The default is 80.

F
──F taskname,REFRESHLOC─┬───────────────────┬─────────────────
└─MEMBER=─┬─name─┬──┘
└─ALL──┘

Reads and refreshes dynamic location information. For more information, see
the Getting Started.

F
──F taskname,REFRESHEXCL──────────────────────────────────────

Reads and refreshes the job exclusion table from EXCLPARM member of the
PPOPTION data set.

F
──F taskname,─┬─AOPTS──────────┬──────────────────────────────
│ ┌─ON──┐ │
└─AOPTS─┴─OFF─┴──┘

Sets the CA-Jobtrac automatic option refresh on or off. If this is set ON (the
default), CA-Jobtrac automatically refreshes the global options when they are
changed. If this is set OFF, the global options are only refreshed when
CA-Jobtrac is recycled or the JICAUPD or OPTS commands are used.

2-20 Operator Guide

 2.4 Using Task Commands

F
──F taskname,DISPLAY─┬─?─────────┬────────────────────────────
├─IMODS─────┤
├─JICA──────┤
├─J1AREA────┤
├─LOCATIONS─┤
└─SMFEXITS──┘

where:
?
Displays display options.
IMODS
Displays global initiation IMODS.
JICA
Diagnostic information only. Displays the address and contents of the
CA-Jobtrac Intertask Communication Area (JICA).
J1AREA
Diagnostic information only. Displays the CA-Jobtrac J1AREA.
LOCATIONS
Displays current dynamic location information.
SMFEXITS
Diagnostic information only. Displays entry points to CA-Jobtrac SMF
exits.

Chapter 2. Using Operator Commands 2-21

2.4 Using Task Commands

2.4.5 Performance Options

F
──F taskname,─┬─SCAN──────────┬───────────────────────────────
│ ┌─3──┐ │
└─SCAN=─┴─nn─┴──┘

Resets the minimum time between scans for new work to nn seconds. The
default is 3.

F
──F taskname,─┬─QUECK──────────┬──────────────────────────────
│ ┌─ON──┐ │
└─QUECK─┴─OFF─┴──┘

By default, CA-Jobtrac checks the JES queues on each scan for all submitted
jobs. When many jobs have been submitted by CA-Jobtrac, performance may
be improved by turning this option OFF.

When this option is OFF, CA-Jobtrac is not able to detect when jobs are purged
or flushed before execution.

F
──F taskname,─┬─SYSCK──────────┬──────────────────────────────
│ ┌─ON──┐ │
└─SYSCK─┴─OFF─┴──┘

By default, CA-Jobtrac checks the JES queues when a job completes to ensure
that output exists before attempting to capture it with the sysout capture
facility. When this option is OFF, CA-Jobtrac is not able to detect requeue (JES)
conditions.

2-22 Operator Guide

 2.4 Using Task Commands

2.4.6 Controlling CA-Jobtrac Internals

You can control the CA-Jobtrac internals with several commands.

Command Syntax: Following is the syntax of the MVS command used to

control the starting and stopping of CA-Jobtrac internals.

S
──S VINIT3,PARM=─┬─BACK─┬─────────────────────────────────────
├─INIT─┤
└─IPL──┘

Note: The VINIT3 STC is a default PROC that is copied into your PROCLIB
from the STAGE2 JCL in the SAMPJCL.

Descriptions of Parameters: Following are descriptions of the elements of

the command used to control the CA-Jobtrac internals:

Element Description
S VINITn,PARM= Required command.
BACK Deactivates all resident components.
IPL Starts the specified CA-Jobtrac and initializes the
CA-Jobtrac. The optional PARM=IPL parameter
allows the IPL message prompt to the operator as
described in the global options information in the
"Customization Tasks" chapter of the Getting Started.
INIT Initializes the CA-Jobtrac internals.

Caution
Only use these commands when instructed by Computer Associates
Technical Support or if you applied maintenance to CA-Jobtrac in these
areas.

Chapter 2. Using Operator Commands 2-23

2.4 Using Task Commands

Examples
| S VINIT3,PARM='ONLY=GJTRUJI2'

This command initializes the job/step SMF exits for IEFUJI/IEFUSI. You can
issue this command while CA-Jobtrac is active to refresh the hooks, but we
recommend that CA-Jobtrac be down.
S VINIT3,PARM='ONLY=GJTRU832'

This command initializes the ADR hooks in SMF exits for IEFU83/IEFU84. You
can issue this command while CA-Jobtrac is active to refresh the hooks, but we
recommend that CA-Jobtrac be down.
S VINIT3,PARM='ONLY=GJTRVMXT'

This command initializes the AMR WTO intercept. The IBM exit IEAVMXIT is
used for this function. You can issue this command while CA-Jobtrac is active
to refresh the hooks, but we recommend that CA-Jobtrac be down.
S VINIT3,PARM='ONLY=GJTRTRT2'

This command initializes the job termination hook in SMF exit IEFACTRT.
You can issue this command while CA-Jobtrac is active to refresh the hooks,
but we recommend that CA-Jobtrac be down.
Note: When refreshing these hooks while CA-Jobtrac is running, an event in
process may not be tracked accurately.

2-24 Operator Guide

 2.5 Monitoring Commands

2.5 Monitoring Commands

The following topics discuss the monitoring commands.

2.5.1 Enqueue Research

CA-Jobtrac enqueue research provides information about the status of the data
sets or other system resources that events, TSO users, or system tasks may be
using. This information is helpful when an event is waiting on a resource or in
analyzing some system slowdowns.

Online Display: Enqueue research is done online in CA-Jobtrac using the

Enqueue Research panel.

Example Enqueue Research Panel

 &prodo. Enqueue Research ROW 1 TO 1 OF 1


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 17:28
CONFLICTS
Owner Qname Access Status RNAME
-------- -------- -------- -------- -----------------------------------------
JES2 SYSZJES2 EXCL RSV OWNER MVSB1SYS1.HASPCKPT
 BOTTOM OF DATA 
 
Description of the Enqueue Research Panel: In response to an enqueue
inquiry, the Enqueue Research panel displays the following information:

Field Description
Owner The event name, TSO user, or system task that is
accessing or trying to access a system resource.
Qname An enqueue can be a ddname from an event's JCL, a
control block, and so on.
Access This can be either EXCL for a DISP=OLD or SHR for a
DISP=SHR.
Status Indicates who controls the displayed resource. OWNER
indicates the JOBNAME/OWNER that is currently in
control of the resource. WAITING indicates an event
waiting for a resource to be released.
Rname Lists the system resource or data set name used by the
requested event name or other system task.

Chapter 2. Using Operator Commands 2-25

2.5 Monitoring Commands

2.5.1.1 Finding and Sorting Information

The primary commands FIND and SORT are available on the Enqueue
Research panel to enable specific searching and sorting of the listed
information. These commands can be used with the standard ISPF scrolling
commands to locate specific information.

FIND Command: The FIND primary command enables you to search the
listed information for a particular event or events.

The syntax of the FIND command is as follows:

FIND
┌─NEXT──┐
──FIND──┬──────────┬──┬───────────────┬──┼───────┼────────────
└─'string'─┘ └─'column-name'─┘ ├─ALL───┤
├─FIRST─┤
├─LAST──┤
└─PREV──┘

SORT Command: The SORT primary command allows you to sort the list in
either ascending or descending order based on the values in a specified
column.

The syntax of the SORT command is as follows:

SORT
┌─A─┐
──SORT─┬───────────────┬──┼───┼───────────────────────────────
└─'column-name'─┘ └─D─┘

2-26 Operator Guide

 2.5 Monitoring Commands

Column Names: The following table equates the field names on the Enqueue
Research panel to the column names used in the FIND and SORT commands:

Panel Field Name Command Column Name

Owner OWNER
Qname QNAME
Access ACCESS
Status STATUS
Rname RNAME

FIND Command Syntax Rules

■ You can limit the search for a character string to a specific column by
specifying a column name after the search argument.
■ You can enclose the search argument in single or double quotes.
■ The default FIND command is FIND {'string'} NEXT.
■ If you specify FIND {'string'} ALL, the FIND command will scan the list to
determine the number of rows that contain the character string. It will
display the results and then position the panel to the first row that
matched the search.
■ You can enter the FIND command with no parameters to repeat the
previous find.

SORT Command Syntax Rules

■ You can specify which column to sort on by specifying a column name.
■ The default SORT command sorts in ascending order.
■ You can enter the SORT command without any parameters to put the list
back in its original sequence.

Chapter 2. Using Operator Commands 2-27

2.5 Monitoring Commands

2.5.2 Enqueue Research Commands

The enqueue research commands provide information for the system on which
your user ID is active. If another system is using a resource needed by the
inquiring system, these commands display only the data set or resource that is
being affected by the other system.

These inquiry commands are informational only and cannot be used directly to
alter the use of system resources.

2.5.2.1 Using the Enqueue Research Commands

If you have CA-Jobtrac running on more than one system, determine which
system the inquiry is to be made from.

The enqueue research commands can be performed from the COMMAND field
of the CA-Jobtrac primary, Scheduled Event Display, Scheduled Event
Network, and Business Group Status panels.

2.5.2.2 Available Commands

Use the following primary commands to display various kinds of resource

information:

Command Brief Explanation

DSNQ Display data set name or data set name prefix enqueues
ENQ Display enqueue conflicts
ENQN Display all enqueue name (enqname) enqueues
JOBQ Display enqueues for a currently executing batch event
name or event name prefix, started task, or TSO user
RESV Display current DASD reserves
WAIT Display enqueue conflicts

2-28 Operator Guide

 2.5 Monitoring Commands

DSNQ Command: The DSNQ command displays enqueue conflicts by data

set name or data set name prefix. The syntax of the DSNQ command is as
follows:

DSNQ
──DSNQ=dsname─────────────────────────────────────────────────

The following rules apply to the syntax of the DSNQ command:

■ The dsname or data set name prefix must be valid.
■ You can combine the DSNQ and JOBQ commands to present a more
selective display (for example, JOBQ=PAP, DSNQ=TEST).

ENQ Command: The ENQ command displays all enqueue conflicts. The
syntax of the ENQ command is as follows:

ENQ
──ENQ─────────────────────────────────────────────────────────

ENQN Command: The ENQN command displays conflicts for the specified
enqueue name. The syntax of the ENQN command is as follows:

ENQN
──ENQN=enqname────────────────────────────────────────────────

The enqname must be valid.

Chapter 2. Using Operator Commands 2-29

2.5 Monitoring Commands

JOBQ Command: The JOBQ command displays enqueues of currently

executing tasks by event name, TSO user ID, or task name. The syntax of the
JOBQ command is as follows:

JOBQ
──JOBQ=eventname──────────────────────────────────────────────

From the Scheduled Event Display or equivalent panel, an N line command

will invoke the JOBQ display for the event indicated.

For example, suppose the Scheduled Event Display panel has the default set to
K=E and all EXECUTING events are displayed. If you select one of the
executing events with the N line command, an enqueue list for the event name
is displayed.

The following rules apply to the syntax of the JOBQ command:

■ eventname must be a valid event name or prefix, TSO user ID or prefix, or
system task name or prefix.
■ You can combine the DSNQ and JOBQ commands to present a more
selective display (for example, JOBQ=PAP,DSNQ=TEST).

RESV Command: The RESV command displays any current reserves. The
syntax of the RESV command is as follows:

RESV
──RESV────────────────────────────────────────────────────────

WAIT Command: Use this command to display any enqueue conflicts. The
syntax of the WAIT command is as follows:

WAIT
──WAIT────────────────────────────────────────────────────────

2-30 Operator Guide

 2.5 Monitoring Commands

2.5.3 DASD Space Analysis

CA-Jobtrac DASD space analysis provides information about the amount of
DASD space available by attribute, VOLSER, or channel address. This is
especially helpful when there is a recurring SB37 or a JCL error with a reason
of space requested not available.

DASD space analysis can also display the VTOC of a volume and the online
panel can be used to manipulate the volume's data sets.

Online Display: DASD space analysis is done online in CA-Jobtrac using the
DASD Space Analysis panel.

Using the DASD Space Analysis Command: The DASD space analysis
command can be performed from the following:
■ A TSO terminal, in the form TSO SPACE
■ COMMAND field of the CA-Jobtrac primary, Scheduled Event Display,
Scheduled Event Network, and Business Group Status panels

Chapter 2. Using Operator Commands 2-31

2.5 Monitoring Commands

2.5.3.1 DASD Space Analysis Command

SPACE Command Description: The SPACE command can be used to verify

that an event has enough space available before execution begins.

The SPACE command displays all available online volumes defined to the
system from which the inquiry was made.

You cannot use the SPACE command to change the status of a volume or to
free space on a volume. The SPACE command only provides information
about the DASD volumes allocated to the system.

Syntax of the SPACE Command: The syntax of the SPACE command is as

follows:

SPACE
──SPACE──;─┬─A────────┬───────────────────────────────────────
├─P────────┤
├─R────────┤
├─U unit───┤
├─V volser─┤
└─W────────┘

Available Parameters: The following parameters are available for use with
the SPACE command:

Parameter Description
;A All online volumes
;P All online scratch volumes mounted as PUBLIC
;R All online volumes that are mounted as PRIVATE
;U unit Limited to the specified CUA (Channel Unit Address) or
prefix
;V volser Limited to the specified volume serial number or prefix
;W All online work volumes mounted as STORAGE

Usage Rule: The SPACE command can be used by itself or with one
parameter.

2-32 Operator Guide

 2.5 Monitoring Commands

2.5.3.2 DASD Space Analysis Panels

The DASD space analysis panels consist of the following:

Panel Name How Obtained

DASD Analysis Using the SPACE command with no parameter
Menu
DASD Selection Using the SPACE command with a parameter, or using
List a command on the DASD Analysis panel
VTOC Selecting a volume from the DASD Selection List panel

The DASD Analysis Panel: Use the SPACE command with no parameters to
display the DASD Analysis Menu.

From the DASD Analysis Menu, you can request available space information
for all volumes or a group of volumes. The commands you can enter on this
panel are the same as the optional parameters to the SPACE command.

The following figure is an example of the DASD Analysis Menu:

 &prodo. DASD Analysis Menu


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 17:28
A ALL - Display all online volumes
P PUBLIC - Display all scratch volumes
R PRIVATE - Display all private volumes
U UNIT - Display unit CUA or prefix specified
V VOLSER - Display volume or prefix specified
W WORK - Display all work volumes
 

Chapter 2. Using Operator Commands 2-33

2.5 Monitoring Commands

The DASD Selection List Panel: Use the SPACE command with a parameter,
or enter a command on the DASD Analysis Menu, to display the DASD
Selection List panel. This detail panel shows all volumes defined to the
inquiring system that fit within the inquiry parameters. The commands you
can enter on this panel are the same as the optional parameters to the SPACE
command. The following figure shows the result of a request for space analysis
for all volumes mounted as WORK packs:

 &prodo. DASD Selection List ROW 1 TO 16 of 92


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 17:28
Volume Mount ----- Device ------ ------- Total ------ -- Largest--
Serial Status CUA Type Stat Cyls Trks Xnts Cyls Trks
-------------------------------------------------------------------------
DMP9 PRV E57 339 A 774 71 18 458 
DMP91 PRV E58 339 O 774 38 13 49 
MCIC PRV E11 338 O 81 14 3 443 
MDMP9 PRV E5 338 A 1372 4 4 128 
MHSM1 PRV E14 338 O 46 59 16 11 6
MHSM2 PRV E15 338 O 44 183 45 138 13
MHSM3 PRV E16 338 O 415 211 42 91 4
MHSM9 PRV E4 338 A 38 1812 334 4 21
MHSM91 PRV E41 339 A 632 629 159 112 9
MHSM92 PRV E45 339 A 129 1154 23 91 4
MHSM96 PRV E54 339 A 863 159 186 244 2
MMAC PRV E13 338 O     
MOPS9 PRV 82 338 O 326 11 15 156 
MPRF1 PRV E 338 A 673 41 95 632 1
MRS21 PRV E42 339 A 689 68 26 623 
MRS22 PRV E43 339 A 346 49 14 334 
 
I/O Errors on the Panel: If an I/O error occurs, RC=nn will appear in the
upper-right corner of the DASD Selection List panel. The following table
explains return codes:

Return Code Explanation

00 Successful completion
04 UCB offline, not ready, or not found
08 DYNALLOC error
12 RDJFCB error
16 Open error
20 I/O error

2-34 Operator Guide

 2.5 Monitoring Commands

Description of DASD Selection List Panel: The following table explains the
fields on the DASD Selection List panel:

Field Name Explanation

Volume Serial Volume serial number of the DASD
device
Mount Status STG—work packs mounted as
storage
PRV—packs mounted as private
including WORK
PUB—packs mounted as public
RSU—packs with a reserve on them
***—packs that are busy
Device CUA Channel Unit Address
Device Type DASD device type
Device Stat A—Available and online
O—Online
Total Cyls Total number of free cylinders
Total Trks Total number of free tracks
Total Xtnts Number of directory extents for the
free cylinders and tracks
Largest Cyls Largest available group of contiguous
cylinders
Largest Trks Largest available group of contiguous
tracks

Chapter 2. Using Operator Commands 2-35

2.5 Monitoring Commands

Using the VTOC Panel: From the DASD Selection List panel, you can display
the VTOC list of a volume by using the S line command to select the volume.
From the VTOC panel, you can select any data set for browsing, editing,
deleting, or renaming using line commands. These functions are allowed only
if you are authorized to perform them normally under TSO.

Available Line Commands on the VTOC Panel: The following table lists
the line commands available on the VTOC panel:

Function Line Command

Browse B
Edit E
Delete D
Rename R (and new data set name in the COMMAND field)

The VTOC Panel: The following figure is an example of the VTOC panel:

 &prodo. VTOC for DMP9 ROW 1 TO 17 of 42


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 17:28
Alloc Unusd Ex Org Rfm Lrecl Blksz Cdate Ldate Dataset name
----- ----- -- --- --- ----- ----- ----- ----- -------------------------
9  1 PS F 248 248 4256  SYS.VTOCIX.DMP9
1 1 1 VS  496 4258 4341 SYS.VVDS.VDMP9
3 2 1 PS VB 492 496 4319 4337 TECHSUPP.DDT67.#11154A
15 6 1 PS FB 416 416 4264 4341 TECHSUPP.DIA669.#9214A
296  1 PS VB 32756 3276 432 4342 TECHSUPP.DIC159.TWO
345 5 1 PS FB 15 327 4292 4336 TECHSUPP.DIJ354.#124A
75 75 1    438  TECHSUPP.DIO582.#1144G
3 5 1 PS VB 32756 3276 432 434 TECHSUPP.DJW99.#1294A
15 14 1 PS FB 133 13566 434 434 TECHSUPP.DKK63.#1264A
66 14 1 PS FB 133 13566 434 434 TECHSUPP.DKK63.#1264B
137  1 PS FB 416 416 4292 4341 TECHSUPP.DKV1.DUMP
1536 73 1 PS VBM 137 27998 4338 4339 TECHSUPP.DLI592.LOG
285 13 1 PS U  386 4315 434 TECHSUPP.DLM9.#1114B
15 14 1 PS U  27998 4336 4337 TECHSUPP.DLM299.#1224A
1  1 PS FB 8 616 439 4311 TECHSUPP.DLP38.#1154C
1  1 PS FB 8 32 439 4311 TECHSUPP.DLP38.#1154D
15 3 1 PS FB 133 13566 4341 4342 TECHSUPP.DMA89.#1274A
 

2-36 Operator Guide

 2.5 Monitoring Commands

2.5.3.3 Finding and Sorting DASD Information

The primary commands FIND and SORT are available on the DASD Selection
List and VTOC panels to enable specific searching and sorting of the listed
events. These commands can be used with the standard ISPF scrolling
commands to locate specific events.

FIND Command: The FIND primary command enables you to search the
listed events for a particular event or events.

The syntax of the FIND command is as follows:

FIND
┌─NEXT──┐
──FIND──┬──────────┬──┬───────────────┬──┼───────┼────────────
└─'string'─┘ └─'column-name'─┘ ├─ALL───┤
├─FIRST─┤
├─LAST──┤
└─PREV──┘

SORT Command: The SORT primary command allows you to sort the list in
either ascending or descending order based on the values in a specified
column.

The syntax of the SORT command is as follows:

SORT
┌─A─┐
──SORT─┬───────────────┬──┼───┼───────────────────────────────
└─'column-name'─┘ └─D─┘

Chapter 2. Using Operator Commands 2-37

2.5 Monitoring Commands

DASD Selection List Panel Column Names: The following table equates the
field names on the DASD Selection List panel to the column names used in the
FIND and SORT commands:

Panel Field Name Command Column Name

Volume Serial VOLUME-SERIAL
Mount Status MOUNT-STATUS
Device CUA DEVICE-CUA
Device Type DEVICE-TYPE
Device Stat DEVICE-STAT
Total Cyls TOTAL-CYLS
Total Trks TOTAL-TRKS
Total Xtnts TOTAL-XTNTS
Largest Cyls LARGEST-CYLS
Largest Trks LARGEST-TRKS

VTOC Panel Column Names: The following table equates the field names on
the VTOC panel to the column names used in the FIND and SORT commands:

Panel Field Name Command Column Name

Alloc ALLOC
Unusd UNUSD
Ex EX
Org ORG
Rfm RFM
Lrecl LRECL
Blksz BLKSZ
Cdate CDATE
Ldate LDATE
Dataset name DATASET-NAME

2-38 Operator Guide

 2.5 Monitoring Commands

FIND Command Syntax Rules

■ You can limit the search for a character string to a specific column by
specifying a column name after the search argument.
■ You can enclose the search argument in single or double quotes.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.
For example, the following command finds all occurrences of AJS.LOAD in
the Dataset name column.
FIND "AJS.LOAD" DATASET-NAME ALL
■ The default FIND command is FIND {'string'} NEXT.
■ If you specify FIND {'string'} ALL, the FIND command will scan the list to
determine the number of rows that contain the character string. It will
display the results and then position the panel to the first row that
matched the search.
■ You can enter the FIND command with no parameters to repeat the
previous find.

SORT Command Syntax Rules

■ You can specify which column to sort on by specifying a column name.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.
For example, the following command sorts on the Dataset name column.
SORT DATASET-NAME
■ The default SORT command sorts in ascending order.
■ You can enter the SORT command without any parameters to put the list
back in its original sequence.

Chapter 2. Using Operator Commands 2-39

2.5 Monitoring Commands

2.5.4 Change Audit History

Any time a schedule entry is purged or deleted, the Process Period field is
updated with the TSO user ID of the user who issued the command. This data
becomes a permanent part of the event's historical data.

Any time a schedule entry is changed, an entry is made in the CA-Jobtrac

history file. Audit records are kept by event and by TSO user ID:
■ Each job level audit record contains data on the last 200 users to make a
change on that event.
■ Each user ID record contains the names of the last 300 events changed or
significant actions taken (such as updating the system options) by each
user.

Change audit history provides information about the changes made to a

requested event. The information can be accessed by event name, altering user
ID, or security ID. You can also limit the information to tasks that have been
altered by the CA-Jobtrac function or the GJTRABTR function.

The Change Audit History panel is used as a source of information only. You
cannot change any information on it.

2.5.4.1 Change Audit History Commands

The following commands display the Change Audit History panel:

■ AUDIT primary command
■ I primary command
■ I line command

Using AUDIT Primary Command: The AUDIT primary command is used on

the Scheduled Event Detail, Event Execution Detail, or Event History Detail
panels.

A Change Audit History panel is displayed for the event.

Using the I Primary Command: The I primary command is used on the

CA-Jobtrac primary, Scheduled Event Display, Scheduled Event Network, or
Business Group Status panels.

A blank Change Audit History panel is displayed. Enter an event or task name
to display change audit history information. Optionally, you can also enter a
user ID, function, date, or time to narrow the search argument.

2-40 Operator Guide

 2.5 Monitoring Commands

Using I Line Command: The I line command is entered next to any event
name on a Scheduled Event Display panel.

It displays a Change Audit History panel with information displayed about the
event. This is the same as entering an event name only on the Change Audit
History panel.

Online Display: Change audit history is displayed online in CA-Jobtrac using

the Change Audit History panel.

Example

 &prodo. Change Audit History ROW 1 TO 9 of 9


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 17:28
Select search arguments: X (I/X) Inclusive/Exclusive

Altered Event ===> ACVP12M (Event or task name) Date ===>

Altering User ===> (Userid, Security ID) Time ===>
Altering Func ===> (CA-JOBTRAC, GJTRABTR)

Event Event Altered Change

Name Number By Date Time Description
-------- --------- -------- -------- ----- -----------------------------
ACVP12M 121.1 HOUJDH 1/23/4 16:36 JOB DELETED FROM SCHEDULE
ACVP12M 121.1 HOUJDH 1/23/4 16:27 JOB PURGED - SUCCESSORS RELEASED
ACVP12M 121.1 HOUJDH 1/23/4 16:25 JCL DEPENDENCY REMOVED
ACVP12M 121.1 HOUJDH 1/23/4 16:24 JOB DELETED FROM SCHEDULE
ACVP12M 121.1 HOUJDH 1/23/4 16:23 JCL DEPENDENCY REMOVED
ACVP12M 121.1 HOUJDH 1/23/4 16:22 JOB DELETED FROM SCHEDULE
ACVP12M 121.1 HOUJDH 1/23/4 16:19 MANUAL DEPENDENCY REMOVED
ACVP12M 121.1 HOUJDH 1/23/4 13:37 JCL SOURCE CHANGED TO TEMPORARY
ACVP12M 121.1 HOUJDH 1/23/4 13:37 MANUAL DEPENDENCY ADDED
 BOTTOM OF DATA 
 

Chapter 2. Using Operator Commands 2-41

2.5 Monitoring Commands

Description of the Change Audit History Panel: The following fields on the
Change Audit History panel are used to specify criteria for a search of the
change audit history. The remaining fields on the panel display the
information selected.

Field Name Description

Select search An inclusive search displays all audit records that
arguments meet each search criteria. For example, TASK:
TESTJOB1 and USER: TSOUSR1 display all changes
for both TESTJOB1 and TSOUSR1.
An exclusive search displays only those records that
match all criteria. The previous example would
display only those records that showed TESTJOB1
being changed by TSOUSR1.
Altered Event The name of the event (that is, schedule name) that the
audit search is to locate.
Altering User The user ID to be included in the search.
Altering Func Used for researching automated schedule changes for
sources other than TSO, such as message triggers
(CA-Jobtrac), batch event updates (GJTRABTR), and so
on.
Date Date mask for the scan. For example, a date of
02/**/04 will match only those changes recorded in
February of 2004.
Time Time mask for the scan. For example, a time of 18:**
will match only those changes recorded during the
1800 hour.

2-42 Operator Guide

 2.5 Monitoring Commands

2.5.4.2 Finding and Sorting Events

The primary commands FIND and SORT are available on the Change Audit
History panel to enable specific searching and sorting of the listed events.
These commands can be used with the standard ISPF scrolling commands to
locate specific events.

FIND Command: The FIND primary command enables you to search the
listed events for a particular event or events.

The syntax of the FIND command is as follows:

FIND
┌─NEXT──┐
──FIND──┬──────────┬──┬───────────────┬──┼───────┼────────────
└─'string'─┘ └─'column-name'─┘ ├─ALL───┤
├─FIRST─┤
├─LAST──┤
└─PREV──┘

SORT Command: The SORT primary command allows you to sort the list in
either ascending or descending order based on the values in a specified
column.

The syntax of the SORT command is as follows:

SORT
┌─A─┐
──SORT─┬───────────────┬──┼───┼───────────────────────────────
└─'column-name'─┘ └─D─┘

Column Names: The following table equates the field names on the Change
Audit History panel to the column names used in the FIND and SORT
commands:

Panel Field Name Command Column Name

Event Name EVENT-NAME
Version Number VERSION-NUMBER
Altered By ALTERED-BY
Date DATE
Time TIME
Change Description CHANGE-DESCRIPTION

Chapter 2. Using Operator Commands 2-43

2.5 Monitoring Commands

FIND Command Syntax Rules

■ You can limit the search for a character string to a specific column by
specifying a column name after the search argument.
■ You can enclose the search argument in single or double quotes.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.
For example, the following command finds all occurrences of TSOUSR2 in
the Altered By column.
FIND TSOUSR2 ALTERED-BY ALL
■ The default FIND command is FIND {'string'} NEXT.
■ If you specify FIND {'string'} ALL, the FIND command will scan the list to
determine the number of rows that contain the character string. It will
display the results and then position the panel to the first row that
matched the search.
■ You can enter the FIND command with no parameters to repeat the
previous find.

SORT Command Syntax Rules

■ You can specify which column to sort on by specifying a column name.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.
For example, the following command sorts on the Event Name column.
SORT EVENT-NAME
■ The default SORT command sorts in ascending order.
■ You can enter the SORT command without any parameters to put the list
back in its original sequence.

2-44 Operator Guide

 2.5 Monitoring Commands

2.5.5 IPL History

When the IPL tracking option is turned on, an IPL record is built every time
an IPL is performed. You can see these records using the IPL History panel.

2.5.5.1 IPL History Command

The IPLS command displays the IPL History panel.

Using the IPLS Primary Command: To display IPL history information, enter
the IPLS command from the COMMAND field of the CA-Jobtrac primary,
Scheduled Event Display, Scheduled Event Network, and Business Group
Status panels.

It displays the IPL History panel.

Syntax: The syntax of the IPLS command is as follows:

IPLS
──IPLS────────────────────────────────────────────────────────

Chapter 2. Using Operator Commands 2-45

2.5 Monitoring Commands

Online Display: IPL history information is displayed online in CA-Jobtrac

using the IPL History panel.

Example

 &prodo. IPL History ROW 1 TO 2 of 2


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 17:28

Date Time Sys Type IPLed by Reason

-------- ----- ---- ---- ------------- --------------------------------------
1/23/4 13:3 B1 CLPA SMITH WATER LEAK
1/23/4 13:21 B1 CLPA PRICE SCHEDULED
 BOTTOM OF DATA 
 
Description of the IPL History Panel: In response to an IPL inquiry, the IPL
History panel displays the following information:

Field Name Description Information from

Date Date the IPL was performed The system
Time Time the IPL was performed The system
Sys System ID of the IPLed system The system
Type Type of IPL, either CLPA or The system
Normal
IPLed by Identifier for the person Operator prompt
performing the IPL
Reason Reason the IPL was performed Operator prompt

2-46 Operator Guide

 2.5 Monitoring Commands

2.5.5.2 Finding and Sorting IPL Records

The primary commands FIND and SORT are available on the IPL History
panel to enable specific searching and sorting of the listed IPL records. These
commands can be used with the standard ISPF scrolling commands to locate
specific IPL records.

FIND Command: The FIND primary command enables you to search the
listed IPL records for a particular record.

The syntax of the FIND command is as follows:

FIND
┌─NEXT──┐
──FIND──┬──────────┬──┬───────────────┬──┼───────┼────────────
└─'string'─┘ └─'column-name'─┘ ├─ALL───┤
├─FIRST─┤
├─LAST──┤
└─PREV──┘

SORT Command: The SORT primary command allows you to sort the list in
either ascending or descending order based on the values in a specified
column.

The syntax of the SORT command is as follows:

SORT
┌─A─┐
──SORT─┬───────────────┬──┼───┼───────────────────────────────
└─'column-name'─┘ └─D─┘

Chapter 2. Using Operator Commands 2-47

2.5 Monitoring Commands

Column Names: The following table equates the field names on the IPL
History panel to the column names used in the FIND and SORT commands:

Panel Field Name Command Column Name

Date DATE
Time TIME
Sys SYS
Type TYPE
IPLed by IPLED-BY
Reason REASON

FIND Command Syntax Rules

■ You can limit the search for a character string to a specific column by
specifying a column name after the search argument.
■ You can enclose the search argument in single or double quotes.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.
For example, the following command finds all occurrences of JOE in the
IPLed By column:
FIND JOE IPLED-BY ALL
■ The default FIND command is FIND {'string'} NEXT.
■ If you specify FIND {'string'} ALL, the FIND command will scan the list to
determine the number of rows that contain the character string. It will
display the results and then position the panel to the first row that
matched the search.
■ You can enter the FIND command with no parameters to repeat the
previous find.

SORT Command Syntax Rules

■ You can specify which column to sort on by specifying a column name.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.
For example, the following command sorts on the IPLed By column:
SORT IPLED-BY
■ The default SORT command sorts in ascending order.
■ You can enter the SORT command without any parameters to put the list
back in its original sequence.

2-48 Operator Guide

 2.5 Monitoring Commands

2.5.6 System Status

The system status provides information about the resource consumption and
growth rate of major CA-Jobtrac files.

2.5.6.1 System Status Command

The STATUS command displays the System Status Display panel.

Using the Status Primary Command: To display system status information,

enter the STATUS command from the COMMAND field of the CA-Jobtrac
primary, Scheduled Event Display, Scheduled Event Network, and Business
Group Status panels.

Syntax: The syntax of the STATUS command is as follows:

STATUS
──STATUS──────────────────────────────────────────────────────

Online Display: System status information is displayed online in CA-Jobtrac

using the System Status Display panel.

Example

 &prodo. System Status Display


COMMAND ===> yy/mm/dd 15:28

CA-Jobtrac Checkpoint: your.CHECKPT

Token: Y
Recs : 29 Blksize : 5166 Extents : 1
Avail : 3833

History File : your.HISTORY

Recs : 2853 CI Size : 6656 Extents : 1

Avail : 11739 CI Splits: 33 CA Splits: 5

Sysout Capture : your.CAPTURE

Tracks Allocated : 15 Device Type : 339

Job Index Blocks : 2247 Used: 286 : 12.7 %
Job Data Blocks : 144 Used: 592 : 41.1 %

Restage Options: Abend- Y Cond Code- Y Cat Error- Y JCL Error- Y

Current CA-Jobtrac Maintenance Level: 3.5 yymm
 

Chapter 2. Using Operator Commands 2-49

2.5 Monitoring Commands

Description of the System Status Display Panel: In response to a system

status inquiry, the System Status Display panel displays the following
information. This panel is informational only. There are no input parameters.

Field Name Description

CA-Jobtrac Checkpoint The name, allocation, and utilization
of your CA-Jobtrac checkpoint data
set. Blocks used should not exceed 80
percent of the total allocated. Also
indicates if the TSO session is using
the correct checkpoint data set and
displays a *MISMATCH* message on
the same line.
Token ID of this CA-Jobtrac system. It is the
last character of the checkpoint and
history DD statements.
History File The name and utilization of your
CA-Jobtrac history file.
Sysout Capture The name and allocation of your
CA-Jobtrac sysout capture file. Job
Index Blocks denotes the number of
events for which JCL sysouts can be
retained. Job Data Blocks is the space
currently used for sysouts. Keep this
percentage below 85 percent.
Restage Options User-defined behavior for various
abnormal job completions. Each can
be Y or N. This is defined in
JOBTRAnn. For more information,
see the Getting Started.
Current CA-Jobtrac Maintenance The maintenance level of CA-Jobtrac
Level in year and month format (yymm).

2-50 Operator Guide

Chapter 3. Monitoring the Current Schedule

This chapter explains the methods available to monitor the current schedule.

Chapter 3. Monitoring the Current Schedule 3-1

3.1 Event Execution Detail Panel

3.1 Event Execution Detail Panel

The Event Execution Detail panel provides detailed information about an event
on the current schedule that is currently executing or has completed execution.
This panel displays actual run statistics, such as time submitted, time started,
and time ended. The event's version number, process period, and other
information can also be found on this panel.

The Event Execution Detail panel is used as a source of information only. You
cannot change any information on this panel.

Displaying the Panel: Use either of the following methods to display an

Event Execution Detail panel:
■ Enter the S primary command at the COMMAND field of the Scheduled
Event Display or Scheduled Event Network panels (see the S primary
command in the 5.2.2, “Select for Detail Display (S) Command”).
■ Use the S line command on an event that is currently executing or has
completed executing on Scheduled Event Display or Scheduled Event
Network panels (see the line command information in 1.12.3, “Using Line
Commands”).

3.1.1 Description of the Event Execution Detail Panel

The panel below shows a sample Event Execution Detail panel. Field
descriptions follow.

 CA-Jobtrac Event Execution Detail


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 15:23
Event Name : TESTWFC1 Status : PURGED BY HOUWFC
Version : 621.2 Process Period: P=HOUWFC Orig Schd Date: 6/21

Target Time : 17:52 Target Date : 6/21 Interval :

Submit Time : Submit Date : Range : -
Start Time : Start Date : Type : (A,E,S)
End Time : 12:3 End Date : 6/23 Interval :

JCL source : (P,T) Job Number : Event Type: C-RMT

Prod Member : TESTWFC1 System ID : Bus. Grp. : HOUWFC
Temp Member : CC Step :
Location :  Abend Code : NJE Node :
Node Name : CORS6 Schedule Environment: BDSCH1

Preds Version Status Successr Version Status Env. Dep.

-------- --------- ----------- --------- ----------- ---------- ----------
 BOTTOM OF DATA 
 

3-2 Operator Guide

 3.1 Event Execution Detail Panel

COMMAND: Lets you enter commands to display desired information or to

perform some function. See the COMMAND field information in 1.12.1, “Using
the COMMAND Field” for the procedure for using this field. See the search
keys and command information in the Reference Summary for details of each
command.

Event Name: Shows the name of the event to which all information on the
panel pertains. See “Event Name” for descriptions of possible entries in this
field.

Status: Provides an abbreviated summary of the event's current status. Some

of the possible entries are listed below.
AWAITING CONVERSION
AWAITING DEPENDENCIES
AWAITING EXECUTION
AWAITING OUTPUT RELEASE
AWAITING RERUN
AWAITING RESTART
AWAITING RESUBMISSION
AWAITING START TIME
AWAITING SUBMISSION
CATALOG ERROR
COMPLETE
CONDITION CODE CHECK
DELETED BY userid
EXECUTING
JCL ERROR
LATE - AWAITING DEPENDENCIES
LATE - AWAITING RERUN
LATE - AWAITING RESTART
LATE - AWAITING SUBMISSION
ON NJE QUEUE
OPERATOR PURGE
PURGED BY userid
SUBMIT TIME THRESHOLD EXCEEDED
SYSTEM ABEND
SYSTEM DOWN
TIME ABORT PURGE
USER ABEND

Chapter 3. Monitoring the Current Schedule 3-3

3.1 Event Execution Detail Panel

Version: Uses the form

mmdd.vvvv

The first four digits indicate the date the event was added to the current
schedule (if CA-Jobtrac assigned the version number) or a user-assigned date.
The last four digits indicate the event's version number. The number may be
user-assigned or CA-Jobtrac-assigned. If CA-Jobtrac assigned the number, it
indicates this version's place in a series of events of the same name added to
the current schedule on the date specified.

For example, suppose TESTJOB1 has a CA-Jobtrac-assigned Version field entry

of 1202.0002. The first four digits show that the event was added to the current
schedule on 12/02. The last four digits show that this event was the second
version of TESTJOB1 added to the current schedule on 12/02.

Process Period: Indicates the process period for the event. See the Schedule
Creation Guide for more information about scheduling dependencies and
process periods. See the process period tables in the Reference Summary for
descriptions of process periods (any of which could appear as entries in the
Process Period field). In addition to the process periods described in the
Reference Summary, the following entries may appear in this field.

Entry Description
AUTO-SCHD The event was added to the current schedule using
the AUTO-SCHD utility.
A=* The event was added to the current schedule using
the program GJTRABTR.
DSN-TRIGGER The event was added to the current schedule using
the Automatic Dataset Recognition facility.
MSG-TRIGGER The event was added to the current schedule using
the Automatic Message Recognition facility.
M=* The event was modified in the current schedule
using the program GJTRABTR.
RQ-userid The event was added to the current schedule by the
user userid through the ADD command, RUN
command, or Event/Jobstream Addition panel.

Orig Schd Date: Indicates the date on which the event was added to the
current schedule.

3-4 Operator Guide

 3.1 Event Execution Detail Panel

Outpt Rlse: If an event has an output release (O) dependency, this field
appears below the Orig Schd Date field. This field indicates that the event's
output should be checked after the event completes. No successors to the event
can run until the O code is manually removed.

Time and Date: Provides the following actual submission and execution
statistics for the event:

Statistic Description
Target Indicates the scheduled time and date at which a LATE
indicator would be set for the event if it had not been
submitted. The target time is used for all schedule
adherence reporting.
Submit Indicates the actual time and date at which CA-Jobtrac
submitted the event.
Start Indicates the actual time and date at which the event
began executing.
End Indicates the actual time and date at which the event
stopped executing.

Interval: Indicates the intervals at which the event was scheduled to be

submitted. The entry is in the form hhmm (hh = hours and mm = minutes). For
example, an event scheduled to run every two hours and 30 minutes would
have the entry 0230.

Range: Indicates the time period during which the event was scheduled to
run at the intervals indicated in the Interval field. The entry is in the form
hhmm- hhmm (the first hhmm indicates the start of the time period, the last
hhmm indicates the end of the time period). For example, the entry 0600-1000
indicates that the event was scheduled to run at the interval shown in the
Interval field from 6:00 AM to 10:00 AM.

The end value of the Range field can either be hhmm or blank. A blank entry
indicates that it will run continuously.

Type: Indicates from what time to calculate the target time for the next
submission of this event based on the interval. Possible entries are:

Entry Description
A Start the calculation at the time the event actually starts
running.
E Start the calculation at the time the event successfully ended.
S Start the calculation at the time defined in the Start and
Target fields.

Chapter 3. Monitoring the Current Schedule 3-5

3.1 Event Execution Detail Panel

JCL source: Indicates the source of JCL. If the entry in this field is P, the
event's JCL was submitted from the JCL library. If the entry is T, the event's
JCL was submitted from the temporary-use JCL library.

Job Number: The job number assigned to batch job-type events by JES.

Event Type: Indicates the type of event this is. Possible entries are:

Entry Description
A-RMT The event is an AS/400 CLP using the CALL command.
C-RMT The event defines a command to be executed at a
particular remote node.
D The event is a dummy job.
I The event is a REXX IMOD.
J The event is a batch job.
S The event is a schedule.
T The event is a 0ARCHIVE, 0SYSARCH, or 0JOBARCH
task.
U-RMT The event invokes a UNIX Korn shell script using the
UNIX ksh command.

Member Name

Prod Member Temp Member

Denotes the name of the member that Denotes the name of the member that
contains the production JCL for this contains a temporary copy of the JCL
event. By default, CA-Jobtrac runs that was used for this event only.
the JCL member that has the same Subsequent scheduling of events with
name as the name specified in the the same name will use the
Event Name field. production JCL. This field is
significant only when the JCL source
field is T. (See the information in 5.9,
“JCL Handling”).

These fields are valid only for job-type events.

System ID: Indicates the name of the system on which the event executed.

Bus. Grp.: Indicates the business group with which the event is associated.

CC Step: Indicates the step number (if any) that exceeded the current
maximum allowable condition code value.

3-6 Operator Guide

 3.1 Event Execution Detail Panel

Location: Indicates the three-digit location ID code assigned to the event.

Determines which JCL, SCL, and documentation libraries were used.

Abend Code: Indicates the abend code if the event abended. Possible entries
are:
■ snnn (system abend code)
■ unnnn (user abend code)

NJE Node: Indicates the JES node on which the job executed if it was an NJE
job.

GSS Node: The GSS Node field indicates the CA-GSS node name (up to 16
characters) of the executing node for the named event. An entry in this field
indicates that this event is a remote event.

Predecessor Fields: Indicates the following information about predecessors

to the event. These fields can be scrolled to view additional predecessors (if
any) using the Up and Down commands.

Field Description
Preds Indicates the event name of the predecessor.
Version Indicates the predecessor event's version (see “Version”
for more information).
Status Provides an abbreviated summary of the predecessor
event's current status. If the message (NOT SCHD)
appears, the predecessor event is not on the current
schedule. If the message (ARCHIVED) appears, the event
has been archived to the history file. See the current
event status information in “Status” for other possible
entries in this field.

Successor Fields: Indicates the following information about successors to the

event. These fields can be scrolled to view additional successors (if any) using
the Up and Down commands.

Field Description
Successr Indicates the event name of the successor.
Version Indicates the successor event's version (see “Version” for
more information).

Chapter 3. Monitoring the Current Schedule 3-7

3.1 Event Execution Detail Panel

Field Description
Status Provides an abbreviated summary of the successor
event's current status. If the message (NOT SCHD)
appears, the successor event is not on the current
schedule. If the message (ARCHIVED) appears, the event
has been archived to the history file. See the current
event status information in “Status” for other possible
entries in this field.

Env. Dep.: Indicates the name of the environmental dependencies (if any)
that exist for this event. Use the EDEP primary command to display the
Environmental Dependencies panel. For more information on dependencies,
see 3.5, “Environmental Dependencies Panel.”

3-8 Operator Guide

 3.2 NJE Execution Detail Panel

3.2 NJE Execution Detail Panel

The NJE Execution Detail panel provides detailed information about a
remotely-submitted NJE job that is currently executing or has completed
execution. This panel displays actual run statistics, such as time submitted,
time started, and time ended. The event's version number, process period, and
other information can also be found on this panel.

The NJE Execution Detail panel is used as a source of information only; you
cannot change any information on this panel.

Displaying the Panel: Use either of the following methods to display an NJE
Execution Detail panel:
■ Enter the S primary command at the COMMAND field of the Scheduled
Event Display or Scheduled Event Network panels (see the S primary
command in the 5.2.2, “Select for Detail Display (S) Command”).
■ Use the S line command on a remotely-submitted NJE job that is currently
executing or has completed executing on the Scheduled Event Display or
Scheduled Event Network panels (see the line command information in
1.12.3, “Using Line Commands”).

3.2.1 Description of the NJE Execution Detail Panel

The panel below shows a sample NJE Execution Detail panel. Field
descriptions follow.

 CA-Jobtrac NJE Execution Detail


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 14:44
Event Name : TLMNJE2 Status : COMPLETE
Version : 1113.1 Process Period: RQ-DALLAS

Schd. Date : 11/13 NJE Status : REMOTE POST ERROR

Orig. Version : 1113.1 Orig. JES Node: MVSB2
GSS Node : B2TRAC

Target Time : 13:15 Target Date : 11/23

Submit Time : 13:15 Submit Date : 11/23
Start Time : 13:57 Start Date : 11/23
End Time : 13:57 End Date : 11/23

Event Type : NJE Job Number : 1234

Business Grp : DALLAS System ID : B1
Location :  CC Step :
Abend Code :
 

Chapter 3. Monitoring the Current Schedule 3-9

3.2 NJE Execution Detail Panel

COMMAND: Lets you enter commands to display desired information or to

perform some function. See the COMMAND field information in 1.12.1, “Using
the COMMAND Field” for the procedure for using this field. See the search
keys and command information in the Reference Summary for details of each
command.

Event Name: Shows the name of the event to which all information on the
panel pertains. See Event Name in “Event Name” for descriptions of possible
entries in this field.

Status: Provides an abbreviated summary of the event's current status. Some

of the possible entries are listed below.
AWAITING CONVERSION
AWAITING DEPENDENCIES
AWAITING EXECUTION
AWAITING OUTPUT RELEASE
AWAITING RERUN
AWAITING RESTART
AWAITING RESUBMISSION
AWAITING START TIME
AWAITING SUBMISSION
CATALOG ERROR
COMPLETE
CONDITION CODE CHECK
DELETED BY userid
EXECUTING
JCL ERROR
LATE - AWAITING DEPENDENCIES
LATE - AWAITING RERUN
LATE - AWAITING RESTART
LATE - AWAITING SUBMISSION
ON NJE QUEUE
OPERATOR PURGE
PURGED BY userid
SUBMIT TIME THRESHOLD EXCEEDED
SYSTEM ABEND
SYSTEM DOWN
TIME ABORT PURGE
USER ABEND

3-10 Operator Guide

 3.2 NJE Execution Detail Panel

Version: Uses the form

mmdd.vvvv

The first four digits indicate the date the event was added to the current
schedule (if CA-Jobtrac assigned the version number) or a user-assigned date.
The last four digits indicate the event's version number. The number may be
user-assigned or CA-Jobtrac-assigned. If CA-Jobtrac assigned the number, it
indicates this version's place in a series of events of the same name added to
the current schedule on the date specified.

For example, suppose TESTJOB1 has a CA-Jobtrac-assigned Version field entry

of 1202.0002. The first four digits show that the event was added to the current
schedule on 12/02. The last four digits show that this event was the second
version of TESTJOB1 added to the current schedule on 12/02.

Process Period: Indicates the process period for the event. See the Schedule
Creation Guide for more information about scheduling dependencies and
process periods. See the process period tables in the Reference Summary for
descriptions of process periods (any of which could appear as entries in the
Process Period field). In addition to the process periods described in the
Reference Summary the following entries may appear in this field.

Entry Description
AUTO-SCHD The event was added to the current schedule using
the AUTO-SCHD utility.
RQ-userid The event was added to the current schedule by the
user userid through the ADD command, RUN
command, or Event/Jobstream Addition panel.
DSN-TRIGGER The event was added to the current schedule using
the Automatic Dataset Recognition facility.
MSG-TRIGGER The event was added to the current schedule using
the Automatic Message Recognition facility.

Schd. Date: Indicates the date on which the event was added to the current
schedule.

NJE Status: Provides an abbreviated status of the progress of CA-Jobtrac in

posting the termination status of this job back to the originating node. Some
of the possible entries are listed below.
■ AWAITING REMOTE POST
■ REMOTE POST IN PROGRESS
■ REMOTE POST ERROR

Chapter 3. Monitoring the Current Schedule 3-11

3.2 NJE Execution Detail Panel

Orig. Version: The version of the job as it exists on the originating node.

When an NJE job arrives at its destination node, CA-Jobtrac attempts to add a
checkpoint record for the job with the same version number that the job had
on its originating node.

Orig. JES Node: Indicates the JES node on which the job was submitted.

GSS Node: Indicates the CA-GSS node on which the job was submitted.

Time and Date: Provides the following actual submission and execution
statistics for the event:

Statistic Description
Target Indicates the scheduled time and date at which a LATE
indicator would be set for the event if it had not been
submitted. The target time is used for all schedule
adherence reporting.
Submit Indicates the actual time and date at which CA-Jobtrac
submitted the event.
Start Indicates the actual time and date at which the event
began executing.
End Indicates the actual time and date at which the event
stopped executing.

Event Type: Indicates the event is a remotely-submitted NJE job.

Job Number: The job number assigned to batch job-type events.

Business Grp: Indicates the business group with which the event is
associated.

System ID: Indicates the name of the system on which the event executed.

Location: Indicates the three-digit location ID code assigned to the event.

Determines which JCL, SCL, and documentation libraries were used.

CC Step: Indicates the step number (if any) that exceeded the current
maximum allowable condition code value.

Abend Code: Indicates the abend code if the event abended. Possible entries
are:
■ snnn (system abend code)
■ unnnn (user abend code)

3-12 Operator Guide

 3.3 Cross Node Query-Criteria Selection Panel

3.3 Cross Node Query-Criteria Selection Panel

The Cross Node Query-Criteria Selection panel allows you to perform a global
query of CA-Jobtrac events for each node which is defined to CA-GSS and to
which CA-Jobtrac is connected.

The selection criteria you can use in your global query is specified on this
panel. The selection criteria specified directly affects the amount of time it will
take to perform the query. The more specific the criteria, the quicker the
results are returned.

You should specify a specific or generic Event Name and a single Event Status
to perform the query more quickly. An event must meet all selection criteria to
be selected for display, except where specified otherwise in the field
descriptions.

Displaying the Panel: The Cross Node Query-Criteria Selection panel is

displayed by issuing the XNODE primary command on the CA-Jobtrac
primary, Scheduled Event Display, Scheduled Event Network, or Business
Group Status panels.

3.3.1 Description of the Cross Node Query-Criteria Selection Panel

The panel below shows a sample Cross Node Query-Criteria Selection panel.
Field descriptions follow.

 CA-Jobtrac Cross Node Query - Criteria Selection


COMMAND ===> yy/mm/dd 9:25

Event Name ===> Event Type ===> Time Limit ===>

Business Group ===> Location ===>

Event Status:
Waiting Submission ===>
Abend Bypass ===> Dataset Req. ===> Edit JCL ===>
Environ. Dep ===> JCL Required ===> Manual Rel. ===>
Output Release ===> Predecessor ===> Queued Rel. ===>
Mutual Exclusion ===> Resource ===> View Doc. ===>
Waiting Exclusion ===>
Executing ===>
Terminated ===>
Normal ===> Abnormal ===> Cond. Code ===>
Catalog Error ===>

Nodes to Search:
===> ===>
===> ===>
===> ===>
===> ===>
 

Chapter 3. Monitoring the Current Schedule 3-13

3.3 Cross Node Query-Criteria Selection Panel

Event Name: A specific name or prefix for which to search. Prefixes are
indicated by a sequence of characters followed immediately by an asterisk. If
left blank, all events qualify for selection as limited by additionally specified
criteria.

Event Type: Indicates the particular type of event to limit the search for. If
left blank, all event types qualify for selection as limited by additionally
specified criteria. The following entries are valid for this field.

Entry Description
A An AS/400 CLP using the CALL command.
C A command to be executed at a particular remote node.
D A dummy job.
E A remote REXX procedure.
I A REXX IMOD.
J A job.
S A schedule.
U An event that invokes a UNIX Korn shell script using the
UNIX ksh command.

Business Group: A specific business group to which the search should be

limited. If left blank, all business groups qualify for selection as limited by
additionally specified criteria.

Location: A specific location to which the search should be limited. If left

blank, all locations qualify for selection as limited by additionally specified
criteria.

3-14 Operator Guide

 3.3 Cross Node Query-Criteria Selection Panel

Event Status: A specific event status to which the search should be limited.
Only if all event statuses are left blank will events with all types of statuses be
selected as limited by additionally specified criteria. Multiple statuses may be
specified; in which case, events which meet any one of those specified will be
selected. Available event statuses and their subqualifiers are as follows:

Event Status Information

Waiting Submission Enter a non-blank character to select all events waiting to be submitted. You
may further limit the search to events waiting due to a specific outstanding
dependency. If multiple dependencies are specified, any event which matches
at least one dependency will be selected. If all are left blank, any event
waiting submission will qualify. Available dependencies are:
Abend Bypass Abend bypass specified
Data set Req. Data set required
Environ Dep. Environmental REXX IMOD dependency exists
JCL Required JCL required
Manual Rel. Manual release needed
Output Release Output release needed
Predecessor Waiting on completion of predecessors
Queued Rel. Waiting on external submission
Mutual Exclusion
Waiting on mutually exclusive event to complete
Resource Waiting on resource
View Doc. View of documentation
WLM The required scheduling environment is not available
Waiting Execution Enter a non-blank character to select events which have been submitted, but
have yet to start executing.
Executing Enter a non-blank character to select events which are currently in execution.
Terminated Enter a non-blank character to select events which have completed execution.
You may further limit the search to events completed with specific
termination statuses. If multiple statuses are specified, any event which
matches at least one status will be selected. If all are left blank, any event
which has completed will qualify. Available statuses are:
Normal Completed normally
Abnormal Completed abnormally; includes such statuses as abend,
JCL errors, and operator purge
Cond.Code Completed with a condition code error
Catalog Error Completed with a catalog error

Chapter 3. Monitoring the Current Schedule 3-15

3.3 Cross Node Query-Criteria Selection Panel

Nodes to Search: Enter up to eight specific GSS node names (up to 16

characters) to which the search should be limited. If all node name fields are
left blank, all nodes will be searched.

Time Limit: This value can be used to limit your query to an acceptable
response time. Enter up to a two-digit value which designates the maximum
amount of time in minutes to perform the Cross Node Query.

After this time limit has expired, the results obtained up to that point are
displayed and no further searching continues.

If this field is left blank or is zero, no time limit will be placed on the query.
Queries can take longer than anticipated due to various factors such as
network traffic and system load on remote nodes.

A global limit may have been set by your system administrator; in which case,
the lesser of the two values is used as the time limit.

3-16 Operator Guide

 3.4 Cross Node Query Panel

3.4 Cross Node Query Panel

The Cross Node Query panel displays summary information for the events
which are the results of a global query performed on the Cross Node
Query-Criteria Selection panel.

Displaying the Panel: The Cross Node Query panel is displayed by

specifying selection criteria for a global query of events on the Cross Node
Query-Criteria Selection panel.

3.4.1 Description of the Cross Node Query Panel

The panel below shows a sample Cross Node Query panel. Field descriptions
follow.

 CA-Jobtrac Cross Node Query ROW 1 TO 5 OF 5


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 14:44
Event Version T Loc Node Busgrp Deps Status
------- --------- - --- ------- --------- ----------- -----------------------
TLLM1 123.1 J  MVSB1 DOCNOTE J DEP. WAIT - AS-AP 1/23
TLLM4 121.1 J  MVSB1 VOLUME P DEP. WAIT - 1:3 1/21
TLLM4 111.1 J  MVSB1 DALLAS M DEP. WAIT - 15:6 11/1
TLLM41 121.1 J  MVSB1 TECH1 P DEP. WAIT - 1:5 1/21
TLLM21M 121.1 J  MVSB1 TECH2 J ABEND(S3A)-1:3 1/21

 BOTTOM OF DATA 

 
Event: The name of the event.

Version: The mmdd.nnnn format version of the event where mmdd is the
month and day the event was scheduled, and nnnn is a unique version of the
event for that date.

T: The event type which can be D for a Dummy event, J for a Job event, or I
for a REXX IMOD event.

Loc: The Location ID for the event.

Node: The JES Node Name associated with an event. For an event which has
not yet been submitted, this is the name of the submitting node. For an event
which has been submitted, this is the name of the execution node.

Busgrp: Indicates the business group with which the event is associated.

Chapter 3. Monitoring the Current Schedule 3-17

3.4 Cross Node Query Panel

Deps: Dependency codes which exist for the event. Possible values are:

Value Meaning
A Abend bypass
D Dataset required
E Edit of JCL required
I REXX IMOD Environmental Dependencies exist
J JCL required
M Manual release required
O Output release required
P Predecessor events exist
Q Queued release required
R Resource dependencies exist
X Exclusions exist
? View of documentation required

3-18 Operator Guide

 3.4 Cross Node Query Panel

Status: Status of the event as follows:

Status Meaning
ABEND(tnnn)-hh:mm mm/dd Event abended at the specified time
and date with the abend code tnnn,
where t is S for a system abend and
U for a user abend, and nnn is the
hexadecimal abend code.
CAT ERROR - hh:mm mm/dd Event completed at the specified time
and date but had a catalog error.
CC ERR(nnn)-hh:mm mm/dd Event encountered a condition code
error at the specified time and date
where nnn is the step number in
which the error occurred.
COMPLETED - hh:mm mm/dd Event has successfully completed at
the specified time and date.
DEP. WAIT - hh:mm mm/dd Event is waiting for dependencies to
be satisfied and has the specified
Target Time.
EXECUTING (Jnnnnn) Event is in execution and has the
specified JES Job Number.
JCL ERR - hh:mm mm/dd Event encountered a JCL error at the
specified time and date.
JES WAIT (Jnnnnn) Event is awaiting execution and has
the specified JES Job Number.
PURGED - hh:mm mm/dd Event was purged at the specified
time and date.
SYSTEM FAILURE Event status is unknown due to a
system failure.

Chapter 3. Monitoring the Current Schedule 3-19

3.4 Cross Node Query Panel

3.4.2 Finding and Sorting Events

The primary commands FIND and SORT are available on the Cross Node
Query panel to enable specific searching and sorting of the listed events. These
commands can be used with the standard ISPF scrolling commands to locate
specific events.

FIND Command: The FIND primary command enables you to search the
listed events for a particular event or events.

The syntax of the FIND command is as follows:

FIND
┌─NEXT──┐
──FIND──┬──────────┬──┬───────────────┬──┼───────┼────────────
└─'string'─┘ └─'column-name'─┘ ├─ALL───┤
├─FIRST─┤
├─LAST──┤
└─PREV──┘

SORT Command: The SORT primary command allows you to sort the list in
either ascending or descending order based on the values in a specified
column.

The syntax of the SORT command is as follows:

SORT
┌─A─┐
──SORT─┬───────────────┬──┼───┼───────────────────────────────
└─'column-name'─┘ └─D─┘

3-20 Operator Guide

 3.4 Cross Node Query Panel

Column Names: The following table equates the field names on the Cross
Node Query panel to the column names used in the FIND and SORT
commands:

Panel Field Name Command Column Name

Event EVENT
Version VERSION
T T
Loc LOC
Node NODE
Busgrp BUSGRP
Deps DEPS
Status STATUS

FIND Command Syntax Rules

■ You can limit the search for a character string to a specific column by
specifying a column name after the search argument.
■ You may enclose the search argument in single or double quotes.
■ The default FIND command is FIND {'string'} NEXT.
■ If you specify FIND {'string'} ALL, the FIND command scans the list to
determine the number of rows that contain the character string. It will
display the results and then position the panel to the first row that
matched the search.
■ You can enter the FIND command with no parameters to repeat the
previous find.

SORT Command Syntax Rules

■ You can specify which column to sort on by specifying a column name.
■ The default SORT command sorts in ascending order.
■ You can enter the SORT command without any parameters to put the list
back in its original sequence.

Chapter 3. Monitoring the Current Schedule 3-21

3.5 Environmental Dependencies Panel

3.5 Environmental Dependencies Panel

The Environmental Dependencies panel provides detailed information about
an event's environmental dependencies. Information such as the name of the
environmental dependencies and their status are found on this panel.

Displaying the Panel: The Environmental Dependencies panel is displayed

by issuing the EDEP primary command on either the Scheduled Event Detail
panel or the Event Execution Detail panel.

The Environmental Dependencies panel is a pop-up panel.

3.5.1 Description of the Environmental Dependencies Panel

The panel below shows a sample Environmental Dependencies panel. Field
descriptions follow.

 ------------------------- Environmental Dependencies -------------------------- 

COMMAND ===> ROW 1 TO 1 OF 1
yy/mm/dd 14:44

IMOD IMOD Retry Retry

S Name ID Count Interval Status
- -------- -------- ----- -------- -------------------------------------
TEST1 1A 1 1 CANCELLED DUE TO IMOD ERROR
 BOTTOM OF DATA 
 
S: Enter S in this field next to an environmental dependency for this event to
view the argument, if any, that is to be passed to this environmental
dependency.

IMOD Name: The name of the environmental dependency for this event.

IMOD ID: The ID assigned to the environmental dependency by the IMOD

Facility. If the environmental dependency has not started execution, it will not
have an ID assigned.

Retry Count: The number of times the environmental dependency will

execute. The number is set by either of the following during CA-Jobtrac
installation:
■ Global options
■ TRACX21 user exit

For more information about the retry count, see the Getting Started.

Retry Interval: The amount of time (hhmm) the environmental dependency

will wait between executions where hh is hours and mm is minutes.

3-22 Operator Guide

 3.5 Environmental Dependencies Panel

For more information about the retry interval, see the Getting Started.

Status: The status of the environmental dependency. The following are

possible:

Status Message Explanation

CANCELED BY ABEND RESULT The environmental dependency
abended.
CANCELED BY REQUEST The environmental dependency was
canceled by a user.
CANCELED DUE TO IMOD ERROR The environmental dependency
contained an error.
CANCELED DUE TO INVALID The environmental dependency
RESULT returned an invalid result.
CANCELED DUE TO RETRY The environmental dependency
COUNT unsuccessfully ran the number of
times specified by the retry count.
CANCELED DUE TO TIME LIMIT The environmental dependency
executed as long as it is allowed to
without ending. Check the
environmental dependency for a
loop. The maximum time allowed to
run is set by the CA-Jobtrac global
options (see the Getting Started.
COMPLETED SUCCESSFULLY The environmental dependency ran
successfully.
NOT SCHEDULED The environmental dependency was
not scheduled for execution.
WAITING ON RETRY INTERVAL The environmental dependency is
waiting for the time specified by the
retry interval to lapse in order to
execute again.
EXECUTING The environmental dependency is
currently executing.

Fields You Can Modify: The Environmental Dependencies panel is used as a

source of information only. You cannot change any information on it.

Chapter 3. Monitoring the Current Schedule 3-23

3.5 Environmental Dependencies Panel

Adding Dependencies: If you add another dependency to an event with an

environmental dependency and the environmental dependency is executing,
the following occurs:
■ The executing environmental dependency is canceled.
■ The retry count is reset for the environmental dependency.
■ The new dependencies are satisfied.
■ The environmental dependency or environmental dependencies are
executed again.

3-24 Operator Guide

 3.6 Business Group Status Panel

3.6 Business Group Status Panel

The Business Group Status panel provides a status for each business group on
the current schedule. The following information is displayed:
■ The consolidated status of all events in a group
■ The number of events in each status category within a group
■ The total number of events for all groups in each status category

The panel is a display only; you cannot modify it.

Displaying the Panel: The Business Group Status panel is displayed by

issuing the BUSGRP primary command on the CA-Jobtrac primary, Scheduled
Event Display, or Scheduled Event Network panels.

3.6.1 Description of the Business Group Status Panel

The panel below shows a sample Business Group Status panel. Field
descriptions follow.

 CA-Jobtrac Business Group Status ROW 1 TO 17 OF 17


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 14:44
Busgrp Busgrp ------------------------ Counts -----------------
Name Status Run Wait Late Comp Abnd Excp Jobs Schd Imod Othr
-------- ----------------- ---- ---- ---- ---- ---- ---- ---- ---- ---- ----
APRI WAITING-LATE  2 2    2   
BIGDUD WAITING-LATE  183 183    183   
CHRISTY WAITING-LATE  1 1    1   
DOUGLAS WAITING-LATE  5 5    5   
EQUADOR WAITING-LATE  2 2    2   
GORGEOUS WAITING-LATE  1 1    1   
HOUSTON WAITING-LATE  4 4    4 2  
HOUSE1 WAITING-LATE  6 6    5 1  
HOUSE2 WAITING-LATE  7 7 3 1 1 5 5  
HOUSE3 WAITING-LATE  2 2 1 1  2   1
HOUSE4 WAITING-LATE  1 1    1   
LASTDATE WAITING-LATE  5 5    5   
SYSTEM1 WAITING-LATE  1 1     1  
VERA1 WAITING-LATE  3 3    3   
VERA2 WAITING-LATE  5 5    5   

TOTAL  228 228 6 2 1 224 9  1

 BOTTOM OF DATA 
 
Busgrp Name: The name of the business group.

Chapter 3. Monitoring the Current Schedule 3-25

3.6 Business Group Status Panel

Busgrp Status: A consolidated status of the events that are on the current
schedule which belong to this business group. The following table lists the
possible statuses:

Status Explanation
WAITING None of the events in the group are
running, and at least one of the
events has not completed.
WAITING-LATE None of the events in the group are
running, and at least one of the
events is late.
RUNNING At least one of the events in the
group is running.
COMPLETED All of the events in the group have
completed, and none of them had an
error or abended.
COMPLETED-ERRORS All of the events in the group have
completed, but at least one of them
had an error or abended.

Counts: The number of events within the business group that have the
specified status. The following table lists the status categories:

Status Category Explanation

Run Events that are executing
Wait Events that are waiting submission or execution
Late Events that are waiting submission or execution and are
late
Comp Events that are complete
Abnd Events that have abended
Excp Events that encountered a condition code check or
catalog error
Jobs Events that are batch jobs
Schd Events that are schedules
Imod Events that are REXX IMODs
Othr Events that are JOBARCH, SYSARCH, ARCHIVE, or
dummy jobs

*TOTAL*: The total number of events in the specified status category for all
business groups.

3-26 Operator Guide

 3.6 Business Group Status Panel

3.6.2 Finding and Sorting Events

The primary commands FIND and SORT are available on the Business Group
Status panel to enable specific searching and sorting of the listed events. These
commands can be used with the standard ISPF scrolling commands to locate
specific events.

FIND Command: The FIND primary command enables you to search the
listed events for a particular event or events.

The syntax of the FIND command is as follows:

FIND
┌─NEXT──┐
──FIND──┬──────────┬──┬───────────────┬──┼───────┼────────────
└─'string'─┘ └─'column-name'─┘ ├─ALL───┤
├─FIRST─┤
├─LAST──┤
└─PREV──┘

SORT Command: The SORT primary command allows you to sort the list in
either ascending or descending order based on the values in a specified
column.

The syntax of the SORT command is as follows:

SORT
┌─A─┐
──SORT─┬───────────────┬──┼───┼───────────────────────────────
└─'column-name'─┘ └─D─┘

Chapter 3. Monitoring the Current Schedule 3-27

3.6 Business Group Status Panel

Column Names: The following table equates the field names on the Business
Group Status panel to the column names used in the FIND and SORT
commands:

Panel Field Name Command Column Name

Busgrp Name BUSGRP-NAME
Busgrp Status BUSGRP-STATUS
Counts Run COUNTS-RUN
Counts Wait COUNTS-WAIT
Counts Late COUNTS-LATE
Counts Comp COUNTS-COMP
Counts Abnd COUNTS-ABND
Counts Excp COUNTS-EXCP
Counts Jobs COUNTS-JOBS
Counts Schd COUNTS-SCHD
Counts Imod COUNTS-IMOD
Counts Othr COUNTS-OTHR

3-28 Operator Guide

 3.6 Business Group Status Panel

FIND Command Syntax Rules

■ You can limit the search for a character string to a specific column by
specifying a column name after the search argument.
■ You may enclose the search argument in single or double quotes.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.

For example, the following command finds all occurrences of PAYROLL in the
Busgrp Name column.
FIND PAYROLL BUSGRP-NAME ALL

■ The default FIND command is FIND {'string'} NEXT.

■ If you specify FIND {'string'} ALL, the FIND command will scan the list to
determine the number of rows that contain the character string. It will
display the results and then position the panel to the first row that
matched the search.
■ You can enter the FIND command with no parameters to repeat the
previous find.

SORT Command Syntax Rules

■ You can specify which column to sort on by specifying a column name.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.

For example, the following command sorts on the Counts Late column.
SORT COUNTS-LATE

■ The default SORT command sorts in ascending order.

■ You can enter the SORT command without any parameters to put the list
back in its original sequence.

Chapter 3. Monitoring the Current Schedule 3-29

3.7 Event History Display Panel

3.7 Event History Display Panel

The Event History Display panel provides information about events that have
been placed on the CA-Jobtrac history file. The history file is a VSAM (Virtual
Storage Access Method) file containing historical run information about events.
The information is taken from the current schedule and placed in the history
file when the 0ARCHIVE task or the 0JOBARCH task executes, when you
delete an event from the current schedule, and sometimes when you purge a
task from the current schedule (see the Reports, Maintenance, and Recovery Guide
for more information about performing CA-Jobtrac maintenance functions).

The Event History Display panel provides historical information about events
(the status of an event when it was deleted/removed from the current
schedule). You cannot change any information on this panel.

You can display an Event History Detail panel for any event on the Event
History Display panel using the S (select) line command.

Displaying the Panel: You can display an Event History Panel using one of
the following methods:
■ Use the H (history) line command on an event on a Scheduled Event
Display or Scheduled Event Network panels (see the line command
information in 1.12.3, “Using Line Commands”).
■ Use the HIST primary command on the Scheduled Event Detail or Event
Execution Detail panels
■ Use the H primary command with an event name, an event prefix, or * on
the CA-Jobtrac primary, Scheduled Event Display, Scheduled Event
Network, or Business Group Status panels. See the search keys and
commands section in the Reference Summary for a detailed listing of this
command.

Caution

Specifying * causes CA-Jobtrac to read the entire history file. The response
for this command can be slow if the history file is large.

3-30 Operator Guide

 3.7 Event History Display Panel

3.7.1 Description of the Event History Display Panel

The panel below shows a sample Event History Display panel. Field
descriptions follow.

 CA-Jobtrac Event History Detail ROW 1 TO 12 OF 12


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 14:44
Event T Start End Comp
S Name Y Loc Time Date Time Date Code Status When Archived
- -------- - --- ----- ----- ---- ----- ---- ---------------------------------
TESTJOB1 D  17:42 6/29 DELETED BY HOUWFC
TESTJOB1 J  9:36 1/7 9:37 1/7 COMPLETE
TESTJOB1 J  12:15 4/22 12:16 4/22 COMPLETE
TESTJOB1 J  8:23 5/4 COMPLETE
TESTJOB1 J  8:23 5/4 DELETED BY HOU$AK
TESTJOB1 J  8:19 5/4 DELETED BY HOU$AK
TESTJOB1 J  11:43 6/9 11:46 6/9 COMPLETE
TESTJOB1 J  12:6 6/24 DELETED BY HOUJDH
TESTJOB1 J  13:5 6/24 13:28 6/24 COMPLETE
 BOTTOM OF DATA 
 
COMMAND: Lets you enter commands to display desired information or to
perform some function. See the COMMAND field information in 1.12.1, “Using
the COMMAND Field” for the procedure for using this field. See the search
keys and command information in the Reference Summary for details of each
command.

S: Enter any of the following line commands in this field next to an event to
perform some action for that event:
B
C
E
G
I
J
O
S
W
?
0 (zero)

See the search keys and commands in the Reference Summary for a detailed
listing of these CA-Jobtrac commands.

Chapter 3. Monitoring the Current Schedule 3-31

3.7 Event History Display Panel

Event Name: Shows the name of the event on the current schedule. All
information on the same record applies to that event. See Event Name in
“Event Name” for descriptions of possible entries in this field.

TY: Indicates the type of event this is. Possible entries are:

Entry Description
D The event is a dummy job.
I The event is a REXX IMOD.
J The event is a batch job.
S The event is a schedule.
T The event is a CA-Jobtrac task.

Loc: Shows the location ID associated with the event. Determines which JCL,
SCL, and documentation libraries were used.

Time and Date: Provides the following execution statistics for the event:

Entry Description
Start Indicates the actual time and date at which the event began
executing.
End Indicates the actual time and date at which the event stopped
executing.

Comp Code: Displays either the step number that exceeded the current
maximum allowable condition code or the abend code.

3-32 Operator Guide

 3.7 Event History Display Panel

Status When Archived: Provides an abbreviated summary of the event's

status when it was put in the history file. Possible entries are listed below.
AWAITING CONVERSION
AWAITING DEPENDENCIES
AWAITING EXECUTION
AWAITING OUTPUT RELEASE
AWAITING RERUN
AWAITING RESTART
AWAITING RESUBMISSION
AWAITING START TIME
AWAITING SUBMISSION
CATALOG ERROR
COMPLETE
CONDITION CODE CHECK
DELETED BY userid
EXECUTING
JCL ERROR
LATE - AWAITING DEPENDENCIES
LATE - AWAITING RERUN
LATE - AWAITING RESTART
LATE - AWAITING SUBMISSION
ON NJE QUEUE
OPERATOR PURGE
PURGED BY userid
SUBMIT TIME THRESHOLD EXCEEDED
SYSTEM ABEND
SYSTEM DOWN
TIME ABORT PURGE
USER ABEND

Chapter 3. Monitoring the Current Schedule 3-33

3.7 Event History Display Panel

3.7.2 Finding and Sorting Events

The primary commands FIND and SORT are available on the Event History
Display panel to enable specific searching and sorting of the listed events.
These commands can be used with the standard ISPF scrolling commands to
locate specific events.

FIND Command: The FIND primary command enables you to search the
listed events for a particular event or events.

The syntax of the FIND command is as follows:

FIND
┌─NEXT──┐
──FIND──┬──────────┬──┬───────────────┬──┼───────┼────────────
└─'string'─┘ └─'column-name'─┘ ├─ALL───┤
├─FIRST─┤
├─LAST──┤
└─PREV──┘

SORT Command: The SORT primary command allows you to sort the list in
either ascending or descending order based on the values in a specified
column.

The syntax of the SORT command is as follows:

SORT
┌─A─┐
──SORT─┬───────────────┬──┼───┼───────────────────────────────
└─'column-name'─┘ └─D─┘

Column Names: The following table equates the field names on the Event
History Display panel to the column names used in the FIND and SORT
commands:

Panel Field Name Command Column Name

Event Name EVENT-NAME
TY TY
Start Time START-TIME
Start Date START-DATE
End Time END-TIME
End Date END-DATE
Comp Code COMP-CODE

3-34 Operator Guide

 3.7 Event History Display Panel

Panel Field Name Command Column Name

Status When Archived STATUS

FIND Command Syntax Rules

■ You can limit the search for a character string to a specific column by
specifying a column name after the search argument.
■ You may enclose the search argument in single or double quotes.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.

For example, the following command finds all occurrences of TESTJOB1 in the
Event Name column.
FIND TESTJOB1 EVENT-NAME ALL

■ The default FIND command is FIND {'string'} NEXT.

■ If you specify FIND {'string'} ALL, the FIND command will scan the list to
determine the number of rows that contain the character string. It will
display the results and then position the panel to the first row that
matched the search.
■ You can enter the FIND command with no parameters to repeat the
previous find.

SORT Command Syntax Rules

■ You can specify which column to sort on by specifying a column name.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.

For example, the following command sorts on the Start Time column.
SORT START-TIME

■ The default SORT command sorts in ascending order.

■ You can enter the SORT command without any parameters to put the list
back in its original sequence.

Chapter 3. Monitoring the Current Schedule 3-35

3.8 Event History Detail Panel

3.8 Event History Detail Panel

The Event History Detail panel provides detailed information about an event
that has been archived to the history file. This panel displays actual run
statistics, such as time submitted, time started, and time ended. The event's
version number, process period, and other information can also be found on
this panel.

The Event History Detail panel is used as a source of information only; you
cannot change any information on this panel.

Displaying the Panel: Use the S line command on an event on the Event
History Display panel to display an Event History Detail panel (see 1.12.3,
“Using Line Commands”).

3.8.1 Description of the Event History Detail Panel

The panel below shows a sample Event History Detail panel. Field
descriptions follow.

 CA-Jobtrac Event History Detail


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 15:23
Event Name : TESTWFC1 Status : DELETED BY HOUWFC
Version : 622.2 Process Period: D=HOUWFC Orig Schd Date: 6/21

Target Time : 1:22 Target Date : 6/22 Interval :

Submit Time : Submit Date : Range :
Start Time : Start Date : Type : (A,E,S)
End Time : 12:24 End Date : 6/23 Interval :

JCL source : (P,T) Job Number : Event Type: A-RMT

Prod Member : TESTWFC1 System ID : Bus. Grp. : HOUWFC
Temp Member : CC Step :
Location :  Abend Code : NJE Node :
GSS Node : COAS4

Preds Version Status Successr Version Status Env. Dep.

-------- --------- ----------- --------- ----------- ---------- ----------
 BOTTOM OF DATA 
 
COMMAND: Lets you enter commands to display desired information or to
perform some function. See the COMMAND field information in 1.12.1, “Using
the COMMAND Field” for the procedure for using this field. See the search
keys and command information in the Reference Summary for details of each
command.

Event Name: Shows the name of the event to which all information on the
panel pertains. See Event Name in “Event Name” for descriptions of possible
entries in this field.

3-36 Operator Guide

 3.8 Event History Detail Panel

Status: Provides an abbreviated summary of the event's status when it was

archived. Some of the possible entries are listed below.
AWAITING CONVERSION
AWAITING DEPENDENCIES
AWAITING EXECUTION
AWAITING OUTPUT RELEASE
AWAITING RERUN
AWAITING RESTART
AWAITING RESUBMISSION
AWAITING START TIME
AWAITING SUBMISSION
CATALOG ERROR
COMPLETE
CONDITION CODE CHECK
DELETED BY userid
EXECUTING
JCL ERROR
LATE - AWAITING DEPENDENCIES
LATE - AWAITING RERUN
LATE - AWAITING RESTART
LATE - AWAITING SUBMISSION
ON NJE QUEUE
OPERATOR PURGE
PURGED BY userid
SUBMIT TIME THRESHOLD EXCEEDED
SYSTEM ABEND
SYSTEM DOWN
TIME ABORT PURGE
USER ABEND

Version: Uses the form

mmdd.vvvv

The first four digits indicate the date the event was added to the current
schedule (if CA-Jobtrac assigned the version number) or a user-assigned date.
The last four digits indicate the event's version number. The number may be
user-assigned or CA-Jobtrac-assigned. If CA-Jobtrac assigned the number, it
indicates this version's place in a series of events of the same name added to
the current schedule on the date specified.

For example, suppose TESTJOB1 has a CA-Jobtrac-assigned Version field entry

of 1202.0002. The first four digits show that the event was added to the current
schedule on 12/02. The last four digits show that this event was the second
version of TESTJOB1 added to the current schedule on 12/02.

Chapter 3. Monitoring the Current Schedule 3-37

3.8 Event History Detail Panel

Process Period: Indicates the process period for the event. See the Schedule
Creation Guide for more information about scheduling dependencies and
process periods. See the process period tables in the Reference Summary for
descriptions of process periods (any of which could appear as entries in the
Process Period field). In addition to the process periods described in the
Reference Summary the following entries may appear in this field.

Entry Description
AUTO-SCHD The event was added to the current schedule using the
AUTO-SCHD utility.
RQ-userid The event was added to the current schedule by the
user userid through the ADD command, RUN
command, or Event/Jobstream Addition panel.
DSN-TRIGGER The event was added to the current schedule using the
Automatic Dataset Recognition facility.
MSG-TRIGGER The event was added to the current schedule using the
Automatic Message Recognition facility.
D=userid The event was deleted from the current schedule by the
user userid through the DELETE command.
P=userid The event was purged from the current schedule by the
user userid through the PURGE command.

Orig Schd Date: Indicates the date on which the event was added to the
current schedule.

Time and Date: Provides the following actual submission and execution
statistics for the event:

Entry Description
Target Indicates the scheduled time and date at which a LATE
indicator would be set for the event if it had not been
submitted. The target time is used for all schedule
adherence reporting.
Submit Indicates the actual time and date at which CA-Jobtrac
submitted the event.
Start Indicates the actual time and date at which the event
began executing.
End Indicates the actual time and date at which the event
stopped executing.

3-38 Operator Guide

 3.8 Event History Detail Panel

Interval: Indicates the intervals at which the event was scheduled to be

submitted. The entry is in the form hhmm (hh = hours and mm = minutes). For
example, an event scheduled to run every two hours and 30 minutes would
have the entry 0230.

Range: Indicates the time period during which the event was scheduled to
run at the intervals indicated in the Interval field. The entry is in the form
hhmm- hhmm (the first hhmm indicates the start of the time period, the last
hhmm indicates the end of the time period). For example, the entry 0600-1000
indicates that the event was scheduled to run at the interval shown in the
Interval field from 6:00 AM. to 10:00 AM.

The end value of the Range field can either be hhmm or blank. A blank entry
indicates that it will run continuously.

Type: Indicates from what time to calculate the target time for the next
submission of this event based on the interval. Possible entries are:

Entry Description
A Start the calculation at the time the event actually starts
running.
E Start the calculation at the time the event successfully
ended.
S Start the calculation at the time defined in the Start and
Target fields.

JCL source: Indicates the source of JCL. If the entry in this field is P, the
event's JCL was submitted from the JCL library. If the entry is T, the event's
JCL was submitted from the temporary-use JCL library.

Job Number: The job number assigned to batch job-type events.

Event Type: Indicates the type of event this is. Possible entries are:

Entry Description
A-RMT The event is an AS/400 CLP using the CALL command.
C-RMT The event defines a command to be executed at a particular
remote node.
D The event is a dummy job.
IMOD The event is a REXX IMOD.
JOB The event is a batch job.
SCHD The event is a schedule.

Chapter 3. Monitoring the Current Schedule 3-39

3.8 Event History Detail Panel

Entry Description
TASK The event is a CA-Jobtrac task.
U-RMT The event invokes a UNIX Korn shell script using the UNIX ksh
command.

Member Name

Prod Member Temp Member

Denotes the name of the member that Denotes the name of the member that
contains the production JCL for this contains a temporary copy of the JCL
event. By default, CA-Jobtrac runs that was used for this event only.
the JCL member that has the same Subsequent scheduling of events with
name as the name specified in the the same name will use the
Event Name field. production JCL. This field is
significant only when the JCL source
field is T. (See 5.9, “JCL Handling.”)

System ID: Indicates the name of the system on which the event executed.

Bus. Grp.: Indicates the business group with which the event is associated.

CC Step: Indicates the step number (if any) that exceeded the current
maximum allowable condition code value for any step.

Location: Indicates the three-digit location ID code assigned to the event.

Determines which JCL, SCL, and documentation libraries were used.

Abend Code: Indicates the abend code if the event abended. Possible entries
are:
■ snnn (system abend code)
■ unnnn (user abend code)

For remote events scheduled to Unicenter TNG, a Unnnn is set if the

command returns a return code higher than the max CC. The nnnn displays
the return code in decimal. A Snnn is set if the command terminates
abnormally. The nnn displays the failcode for the command in hex.

NJE Node: Indicates the JES node on which the job executed if it was an NJE
job.

GSS Node: The GSS Node field indicates the CA-GSS node name (up to 16
characters) of the executing node for the named event. An entry in this field
indicates that this event is a remote event.

3-40 Operator Guide

 3.8 Event History Detail Panel

Predecessor Fields: Indicates the following information about predecessors

to the event. These fields can be scrolled to view additional predecessors (if
any) using the Up and Down commands.

Entry Description
Preds Indicates the event name of the predecessor.
Version Indicates the predecessor event's version (for more
information, see “Version”).
Status Provides an abbreviated summary of the predecessor
event's current status. If the message (NOT ARCH)
appears, the predecessor event could not be found on
the history file. See the current event status information
in 5.2.3, “Description of the Scheduled Event Detail
Panel” for other possible entries in this field.

Successor Fields: Indicates the following information about successors to the

event. These fields can be scrolled to view additional successors (if any) using
the Up and Down commands.

Entry Description
Successr Indicates the event name of the successor.
Version Indicates the successor event's version (for more
information, see “Version”).
Status Provides an abbreviated summary of the successor
event's current status. If the message (NOT ARCH)
appears, the successor event could not be found on the
history file. See the current event status information in
“Status” for other possible entries in this field.

Env. Dep.: Indicates the name of the environmental dependencies (if any)
that exist for this event. Use the EDEP primary command to display the
Environmental Dependencies panel for more information on dependencies, see
3.5, “Environmental Dependencies Panel.”

Chapter 3. Monitoring the Current Schedule 3-41

3.9 Missing Events Panel

3.9 Missing Events Panel

The Missing Events panel lists events that are not on the current schedule, but
have been referenced as predecessors and/or successors by other events. You
may use this panel to determine if there are any events that are missing that
you may need to add manually to the current schedule. For CA-Jobtrac to
recognize these events as missing and to list them on this panel, these events
must be referenced as predecessors and/or successors by other events.

You can add or delete missing events from the Missing Events panel. You can
display the panel from the Business Group Status panel, the CA-Jobtrac
primary panel, the Scheduled Event Display panel, or the Scheduled Event
Network panel.

Displaying the Panel: Enter the MISSING command at the COMMAND field
of the Business Group Status panel, the CA-Jobtrac primary panel, the
Scheduled Event Display panel, or the Scheduled Event Network panel.

3.9.1 Description of the Missing Events Panel

The panel below shows a sample Missing Events panel. Field descriptions
follow.

 CA-Jobtrac Missing Events


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 15:23
Missing Predecessor/ Of
Event Successor Scheduled Event(s):
-------- ------------- -------------------------------------------
ABC Predecessor TESTONEA
ABCDE1 Successor FGHIJO1
ACAPULCO Predecessor TESTTWA
Successor TESTTENA
ACAPONYO Predecessor TESTONEA
ACAR4MEO Successor ACARFORU ACAR4HER
ACAR4MEO Successor ACAR4HIM
ACAR4MEO Successor ACAR4YOU
 BOTTOM OF DATA 
 
Missing Event: Name of the event that is not on the current schedule and is
referenced by another event as either a predecessor or a successor.

Predecessor/Successor: Relationship of the Missing Event to event(s) listed

under the Of Scheduled Event(s): column. The value for this field can either be
predecessor or successor. A missing event can have multiple entries under this
column and the Of Scheduled Event(s): column because an event can have a
predecessor relationship to one event and a successor relationship to another
event. See Missing Event ACAPULCO in the panel sample for an example.

Of Scheduled Event(s): The scheduled event(s) which has a predecessor(s)

and/or a successor(s) that is not on the current schedule.

3-42 Operator Guide

 3.9 Missing Events Panel

3.9.2 Line Commands

You can use the A, D, and S line commands to add, delete, and select.
■ Add - Add event with defaults (like the ADD primary command)
■ Delete - Remove all references (and adjust predecessor events)
■ Select - Shows the detail panel before adding the event

3.9.3 Finding Events

The primary command FIND is available on the Missing Events panel to
enable specific searching of the listed events. This command can be used with
the standard ISPF scrolling commands to locate specific events.

FIND Command: The FIND primary command enables you to search the
listed events for a particular event or events.

The syntax of the FIND command is as follows:

FIND
┌─NEXT──┐
──FIND──┬──────────┬──┬───────────────┬──┼───────┼────────────
└─'string'─┘ └─'column-name'─┘ ├─ALL───┤
├─FIRST─┤
├─LAST──┤
└─PREV──┘

Chapter 3. Monitoring the Current Schedule 3-43

3.9 Missing Events Panel

Column Names: The following table equates the field names on the Missing
Events panel to the column names used in the FIND command:

Panel Field Name Command Column Name

Missing Event MISSING-EVENT
Predecessor/Successor P/S
Of Scheduled Event(s) SCHEDULED-EVENTS

FIND Command Syntax Rules

■ You can limit the search for a character string to a specific column by
specifying a column name after the search argument.
■ You may enclose the search argument in single or double quotes.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.

For example, the following command finds all occurrences of TESTJOB1 in the
Missing Event column.
FIND TESTJOB1 MISSING-EVENT ALL

■ The default FIND command is FIND {'string'} NEXT.

■ If you specify FIND {'string'} ALL, the FIND command will scan the list to
determine the number of rows that contain the character string. It will
display the results and then position the panel to the first row that
matched the search.
■ You can enter the FIND command with no parameters to repeat the
previous find.

3-44 Operator Guide

 3.9 Missing Events Panel

3.9.4 Excluding Events

The primary command EXCLUDE is available on the Missing Events panel to
enable the exclusion of certain events based on whether they are referenced as
predecessors or successors from the list of events on display. This command
can be used with the standard ISPF scrolling commands to locate specific
events.

EXCLUDE Command: The EXCLUDE primary command enables you to

exclude certain events based on whether they are referenced as predecessors or
successors from the list of events on display.

The syntax of the EXCLUDE command is as follows:

EXCLUDE
──┬─EXCLUDE─┬──┬─P────────────┬───────────────────────────────
└─X───────┘ ├─PREDECESSORS─┤
├─S────────────┤
└─SUCCESSORS───┘

EXCLUDE Command Example: The following command excludes all events

that have been referenced as predecessors from the list of events on display.
EXCLUDE PREDECESSORS

Chapter 3. Monitoring the Current Schedule 3-45

3.10 Volume Pull List Panel

3.10 Volume Pull List Panel

The Volume Pull List panel function is part of CA-JCLTrac. For information
about CA-JCLTrac, see the Extended Scheduling Services Guide. The pull list
shows which tape volumes will be used as input and the approximate number
of scratch tapes required.

The Volume Pull List panel is a display panel only; you cannot modify it. You
can display the panel from the Scheduled Event Display panel, the Scheduled
Event Network panel or the Scheduled Event Detail panel.

Displaying the Panel: Use either of the following methods to display a

Volume Pull List panel:
■ Enter the VOLUME command at the COMMAND field of an event's
Scheduled Event Detail panel.
■ Use the V line command on an event on a Scheduled Event Display or the
Scheduled Event Network panel. See the line commands in the Reference
Summary for more information.

3-46 Operator Guide

 3.10 Volume Pull List Panel

3.10.1 Description of the Volume Pull List Panel

The panel below shows a sample Volume Pull List panel. Field descriptions
follow.

 CA-Jobtrac Volume Pull List ROW 1 TO 1 OF 1


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 14:44
VOLTEST1 requires  scratches

Dataset Name Volser Vault Slot Crdate

------------------------------------------- ------ --------------------------
HJS.TEST GDG3.GV 1
HJS.TEST GDG3.GV 2
HJS.TEST GDG3.GV 3
HJS.TEST GDG3.GV 4
HJS.TEST GDG3.GV 5
HJS.A9.DD46UTL.G1V 41
HJS.A9.DD1367.G1V 43
HJS.A9.CMA9113.G1V 49
HJS.A9.D1315UTL.G1V 418
HJS.A9.ADAWNERR.G1V 427

 BOTTOM OF DATA 

 
Dataset Name: Name of the data set on the tape used for input.

Volser: Volume serial number of the input tape.

Vault: Name of the vault where the input tape is stored.

This field is only significant if you use the TRACX25 user exit.

Slot: Number of the slot where the input tape is stored in the vault.

This field is only significant if you use the TRACX25 user exit.

Crdate: Creation date of the data set.

This field is only significant if you use the TRACX25 user exit.

Chapter 3. Monitoring the Current Schedule 3-47

3.10 Volume Pull List Panel

3.10.2 Finding and Sorting Data Sets

The primary commands FIND and SORT are available on the Volume Pull List
panel to enable specific searching and sorting of the listed data sets. These
commands can be used with the standard ISPF scrolling commands to locate
specific data sets.

FIND Command: The FIND primary command enables you to search the
listed data sets for a particular data set.

The syntax of the FIND command is as follows:

FIND
┌─NEXT──┐
──FIND──┬──────────┬──┬───────────────┬──┼───────┼────────────
└─'string'─┘ └─'column-name'─┘ ├─ALL───┤
├─FIRST─┤
├─LAST──┤
└─PREV──┘

SORT Command: The SORT primary command allows you to sort the list in
either ascending or descending order based on the values in a specified
column.

The syntax of the SORT command is as follows:

SORT
┌─A─┐
──SORT─┬───────────────┬──┼───┼───────────────────────────────
└─'column-name'─┘ └─D─┘

3-48 Operator Guide

 3.10 Volume Pull List Panel

Column Names: The following table equates the field names on the Volume
Pull List panel to the column names used in the FIND and SORT commands:

Panel Field Name Command Column Name

Dataset Name DATASET-NAME
Volser VOLSER
Vault VAULT
Slot SLOT
Crdate CRDATE

FIND Command Syntax Rules

■ You can limit the search for a character string to a specific column by
specifying a column name after the search argument.
■ You may enclose the search argument in single or double quotes.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.

For example, the following command finds all occurrences of TEST.TEST1 in

the Dataset Name column.
FIND TEST.TEST1 DATASET-NAME ALL

■ The default FIND command is FIND {'string'} NEXT.

■ If you specify FIND {'string'} ALL, the FIND command will scan the list to
determine the number of rows that contain the character string. It will
display the results and then position the panel to the first row that
matched the search.
■ You can enter the FIND command with no parameters to repeat the
previous find.

SORT Command Syntax Rules

■ You can specify which column to sort on by specifying a column name.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.

For example, the following command sorts on the Dataset Name column.
SORT DATASET-NAME

■ The default SORT command sorts in ascending order.

■ You can enter the SORT command without any parameters to put the list
back in its original sequence.

Chapter 3. Monitoring the Current Schedule 3-49

3.11 Argument Panel

3.11 Argument Panel

The Argument pop-up panel displays the argument to pass to an event based
on its event type. The argument is displayed for viewing only in a pop-up
panel at the bottom of the Event Execution Detail panel.

Displaying the Panel: The Argument panel is displayed by issuing the ARG
primary command from the Event Execution Detail panel.

The Argument panel is a pop-up panel displayed for viewing only.

The panel below shows a sample Argument panel.

 
------------------------------- Argument --------------------------------
ABDEFGHIJKLMNOP

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

3-50 Operator Guide

Chapter 4. Adding Events to the Current Schedule

This chapter details adding events to the current schedule, the ADD command,
the RUN command, and the batch method.

Chapter 4. Adding Events to the Current Schedule 4-1

4.1 Schedules and Events

4.1 Schedules and Events

This topic discusses schedule requirements, the current schedule, and methods
for adding events. It also refers you to other guides for methods not described
in this chapter.

4.1.1 Schedule
A schedule must be added to the current schedule before it can be executed
dynamically. For example, suppose schedule 0TESTSCH contains SCL to add
TESTJOB1, DAYSCHD, and 0ARCHIVE to the current schedule. 0TESTSCH
must be added to the current schedule and then be executed to add TESTJOB1,
DAYSCHD, and 0ARCHIVE to the current schedule.

A schedule can be added to the current schedule using any of the following
methods:
■ Using the Event/Jobstream Addition panel (for more information on
updating the current schedule, see 4.4, “The Event/Jobstream Addition
Panel”)
■ Using the ADD command (for more information, see 4.2, “The ADD
Command”)
■ Using the RUN command (for more information, see 4.3, “The RUN
Command”)
■ Using the batch method (for more information about using the batch
method to load the current schedule, see 4.6.1, “Using the Batch Method”)
■ Using a schedule (see the following topics)

4.1.2 The Current Schedule

The current schedule is contained in the CA-Jobtrac checkpoint. The
checkpoint data set contains information about events to be executed.

The CA-Jobtrac scan task uses the information in the current schedule to
determine when an event should be submitted for execution or when a
schedule or task should be executed.

4-2 Operator Guide

 4.1 Schedules and Events

4.1.3 Methods for Adding Events

CA-Jobtrac offers numerous methods for adding events to the current
schedule. This chapter describes the following methods:
■ The ADD command
■ The RUN command
■ The Event/Jobstream Addition panel
■ Schedules
■ The batch method
■ The AUTO-SCHD feature

4.1.4 Methods Not Described in This Chapter

You can also use the following methods to add events to the current schedule:
■ Using Automatic Dataset Recognition triggering, you can automatically
add an event to the current schedule when a defined data set or VSAM
data component is CLOSED after an update or create operation. Using
Automatic Dataset Recognition is described in the Extended Scheduling
Services Guide.
■ Using Automatic Message Recognition triggering, you can automatically
add an event to the current schedule when a defined console message
identification code, message text, or portion of a console message text
occurs. Using Automatic Message Recognition is described in the Extended
Scheduling Services Guide. Also see the Reports, Maintenance, and Recovery
Guide.
■ Using the GJTRABTR utility, you can add an event to the current schedule
based upon certain conditions. The GJTRABTR utility is described in the
Reports, Maintenance, and Recovery Guide.
■ Using @JOBTRAC, you can add an event to the current schedule.
@JOBTRAC is described in the Extended Scheduling Services Guide.
■ Using MVS operator console commands, you can add an event to the
current schedule in case of a TSO or VTAM failure. This method is
described in 2.4, “Using Task Commands.”
■ Using Unicenter TNG or CA-Jobtrac Agent, you can add an event to the
current schedule. This method is described in the Getting Started and the
Extended Scheduling Services Guide.

Chapter 4. Adding Events to the Current Schedule 4-3

4.2 The ADD Command

4.2 The ADD Command

You can use the ADD command to add a single event to the current schedule.
The event may not submit immediately if an existing event on the checkpoint
data set names this event as a successor. In this case, the job is given a P
dependency and waits until the defined predecessor completes.

The ADD command works like the RUN command, except that the ADD
command assigns a manual dependency to the added event.

This method is used for one-time additions to the schedule.

Conditions Created by the ADD Command: Any event you add using the
ADD command is assigned the following conditions:
■ The current time (time at which the ADD command is executed) is
assigned as the target/start time for the event.
■ The current date is assigned as the target execution date.
■ If no version number is specified in the command, version number 01 is
assigned.
■ A manual dependency is assigned (execution dependency code M).
■ A process period of RQ-userid (userid is the ID of the user adding the
event) is assigned.
■ If no location ID is specified in the command, the default location ID of the
user issuing the command is assigned.
■ The maximum condition code for the event is set as defined in the
RAMAXCC= startup parameter (described in the Getting Started).
■ The SCHEDULE ENVIRONMENT field defaults to the SCHENV startup
parameter (described in the Getting Started).

If an event requires conditions other than those listed above, you can add them
using the Scheduled Event Detail panel once the event is on the current
schedule (see the editing fields information in 5.2, “Scheduled Event Detail
Panel”).

Entering ADD with no parameters invokes the Event/Jobstream Addition

panel. See 4.4, “The Event/Jobstream Addition Panel” for more information.

4-4 Operator Guide

 4.2 The ADD Command

4.2.1 ADD Command Explained

This command adds a single event to the current schedule with a manual
dependency (dependency code M).

Syntax of the ADD Command: The syntax of the ADD command is as

follows:

ADD
──ADD───┬─eventname─┬───┬─────┬──┬────────┬──┬──────────┬──────
├─sclname──┤ └─.vv─┘ └─,L=nnn─┘ └─,─┬─A─┬──┘
└─tasknm───┘ ├─C─┤
├─D─┤
├─E─┤
└─U─┘
──┬─────────────┬──┬──────────────────────────────┬────────────
└─,N=nodename─┘ └─,A=─┬─CLPname,arg─────────┬──┘
├─command─────────────┤
├─imod-arg────────────┤
└─shellscriptname.arg─┘

Description of Command Elements

CA-Jobtrac Event Version Location Event GSS Node Argument

Command Name # ID Type Parameter
ADD eventname .vv ,L=nnn ,A ,N=nodename ,A={CLname,arg|
0sclname ,C command|imod-arg|
0tasknm ,D shellscriptname,arg}
,E
,U

Syntax Rules: The following rules apply to the syntax of the ADD command:
■ A space must separate ADD from the required variable.
■ The required variable must be no more than eight characters.
■ If specified, the version number must be separated from the required
variable by a period.
■ If specified, each of the location ID, event type indicators, GSS node name
indicator, and argument parameters must be separated by a comma.

Chapter 4. Adding Events to the Current Schedule 4-5

4.2 The ADD Command

Description of the Event Name: The following table describes the options
available for the REQUIRED variable:

Variable Description
eventname Specifies an event to be added to the current schedule.
Replace eventname with the name of the event.
0sclname Specifies a schedule to be added to the current
schedule. Replace sclname with the name of the
schedule member. A 0 (zero) must precede the sclname.
0tasknm Specifies a task to be added to the current schedule.
Replace tasknm with the name of the task. A 0 (zero)
must precede the tasknm.

Description of the Version # Parameter: The version number parameter

specifies a version number. Replace vv with a two-digit version number (01-99)
to be assigned to the event being added. If you do not assign a version
number, CA-Jobtrac assigns the next available version number.

If you assign a version number and the event is already on the current
schedule with matching event name and version number, the following
applies:
■ The event you want to add is not added to the current schedule
■ The message ALREADY EXISTS is displayed

Description of the Location ID Parameter: The location ID parameter

specifies a location ID to be assigned to the event being added. If you do not
assign a location ID, CA-Jobtrac assigns the default location ID of the user ID
issuing the command.

Description of the Event Type Parameters: The following table describes the
parameters available for the event type:

Parameter Description
,A Indicates that the named event is an AS/400 CLP using the
CALL command.
,C Indicates that the named event defines a command to be
executed at a particular remote node.
,D Indicates that the named event is a dummy job.
,E Indicates that the named event is a REXX IMOD.
,U Indicates that the named event invokes a UNIX Korn shell script
using the UNIX ksh command.

4-6 Operator Guide

 4.2 The ADD Command

Description of the GSS Node Parameter: The GSS node parameter indicates
the GSS node name (up to 16 characters) of the executing node for the named
event.

Description of the Argument Parameter: The argument parameter is

dependent upon the type of event as specified by the options [,A] [,C] [,E] or
[,U]. To include embedded blanks or commas, enclose the variable portion of
the argument with single quote marks. To include embedded single quotes,
replace the embedded single quote mark with a double quote mark.

Argument Description
[,A][,A=CLPname,arg] Specifies an argument to pass to the named AS/400 CLP. Replace
arg with a 1- to 255-character argument. CLPname,arg can contain
embedded blanks and commas.
If the CLPname is not specified, the default CLPname that is used
is the Alternate Member name (if one is specified) or the Event
Name (if no Alternate Member Name is specified).
[,C][,A=command] Specifies the exact command to be executed at a particular remote
node. command can contain embedded blanks and commas.
The UNIX environment is case-sensitive. Please be aware that the
ADD and RUN commands will translate the command to all
uppercase characters which may produce unexpected results when
passed to UNIX.
[,E][,A=imod-arg] Specifies an argument to pass to the named REXX IMOD. Replace
imod-arg with a 1- to 255-character argument. imod-arg can contain
embedded blanks and commas.
[,U][,A=shellscriptname,arg] Specifies an argument to pass to the named UNIX Korn shell
script. Replace arg with a 1- to 255-character argument.
shellscriptname,arg can contain embedded blanks and commas.
If the shellscriptname is not specified, the default shellscriptname that
is used is the Alternate Member name (if one is specified) or the
Event Name (if no Alternate Member Name is specified). The
UNIX environment is case-sensitive. Please be aware that the ADD
and RUN commands will translate the argument to all uppercase
characters which may produce unexpected results when passed to
UNIX.

Chapter 4. Adding Events to the Current Schedule 4-7

4.2 The ADD Command

4.2.2 Using the ADD Command

Procedure: Perform the steps below to add a single event to the current
schedule using the ADD command.
1. Access the CA-Jobtrac primary, Scheduled Event Display, Scheduled Event
Network, or Business Group Status panel.
2. Move the cursor to the COMMAND field.
3. Type the ADD command (see 4.2.1, “ADD Command Explained”).
4. Press Enter to execute the ADD command.
5. You proceed to the Scheduled Event Display panel with this event being
displayed.

4-8 Operator Guide

 4.2 The ADD Command

Examples: The following panel shows the ADD command used to add
PRODJOB1 to the current schedule.

 CA-Jobtrac Scheduled Event Display ROW 1 TO 18 OF 21


COMMAND ===> ADD PRODJOB1 SCROLL ===> PAGE
yy/mm/dd 14:3
Event ----Target----Successor Dep Current CMD= RALL
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ----------------------------------------
ACAPHIST 16:36  12/18 M WAITING DEPENDENCIES LATE
ACAPD 1:5 12/17 ACGL25 P WAITING DEPENDENCIES LATE
ACAP1 AS-AP 1/23 J WAITING RSTRT J 5643 LATE
ACAPD 1:3 12/17 ACAPD M WAITING DEPENDENCIES LATE
ACAP1D 1:5  12/17 ACAP15D M WAITING DEPENDENCIES LATE
ACAP11R 1:4  12/18 ACAPD J WAITING DEPENDENCIES LATE
ACAP12R 1:4  12/18 ACAPD J WAITING DEPENDENCIES LATE
ACAP15D 1:5  1/21 ACGL2D J WAITING DEPENDENCIES LATE
ACAP15D 1:5  12/17 ACGL2D PD WAITING DEPENDENCIES LATE
ACAP35R 1:4  12/18 ACAPD J WAITING DEPENDENCIES LATE
ACAR4 1:3  1/21 ACAR43 P WAITING DEPENDENCIES LATE
ACAR4 15:6 11/1 M WAITING DEPENDENCIES LATE
ACAR4 1:3  12/17 ACAR43 PM WAITING DEPENDENCIES LATE
ACAR41 1:5  1/21 ACGL21R P WAITING DEPENDENCIES LATE
ACAR41 1:5  12/17 ACGL21R PM WAITING DEPENDENCIES LATE
 
The following panel shows the ADD command required to add schedule
TESTSCD to the current schedule. Note that 0 (zero) is added at the beginning
of the schedule name.

 CA-Jobtrac

COMMAND ===> ADD TESTSCH yy/mm/dd 16:55

Primary Commands:
RALL - List all events CA-JCLTRAC-JCL analysis system
J=evnm - List events beg. w evnm ISERVE - CA-GSS IMOD facility
K=status - List events w/ status JCL - Edit production JCL
D=dep - List events w/ deps SCL - Edit SCL
B=bgname - List events of a bus. grp. SYS OPTS - Update global options
T=hhmm - List events by target time SYS HOLS - Holiday calendar maint.
BUSGRP - Business group status SYS CYCS - Cyclic calendar maint.
ADD - Add event to schedule JTS - Table services
GSO - Generate schedules online OUT - Sysout capture

 The following line commands will be available for SCHEDULED EVENT DISPLAY:
 - CA-View sysout brswe H - Event history R - Rerun/restart
A - Release dependencies I - Audit history S - Select (detail)
C - Cond code exceptions L - Dependent jobstream T - Create/edit temp JCL
D - Delete event M - Manual actions V - Volume pull list
E - Edit JCL/SCL O - Browse sysout Y - CPM info
F - Display DSN triggers P - Purge event X - Resource dependency
G - GSO Q - Sysview Jobsum ? - View documentation
 

Chapter 4. Adding Events to the Current Schedule 4-9

4.3 The RUN Command

4.3 The RUN Command

You can use the RUN command to add a single event to the current schedule.
The RUN command adds an event for immediate submission.

The event may not submit immediately if an existing event on the checkpoint
data set names this event as a successor. In this case, the job is given a P
dependency and waits until the defined predecessor completes.

The RUN command works like the ADD command, except that the RUN
command does not assign a manual dependency to the added event. Once an
event is added to the current schedule with the RUN command, the event is
ready for immediate submission.

This method is used for one-time additions to the schedule.

Conditions Created by the RUN Command: Any event you add using the
RUN command is assigned the following conditions:
■ The current time (time at which the RUN command is executed) is
assigned as the target/start time for the event.
■ The current date is assigned as the target execution date.
■ If no version number is specified in the command, the next available
version number is assigned.
■ A process period of RQ-userid (userid is the ID of the user adding the
event) is assigned.
■ If no location ID is specified in the command, the default location ID of the
user issuing the command is assigned.
■ The maximum condition code for the event is set as defined in the
RAMAXCC= startup parameter (described in the Getting Started).
■ The SCHEDULE ENVIRONMENT field defaults to the SCHENV startup
parameter (described in the Getting Started).

Entering RUN with no parameters invokes the Event/Jobstream Addition

panel. See 4.4, “The Event/Jobstream Addition Panel” for more information.

4-10 Operator Guide

 4.3 The RUN Command

4.3.1 RUN Command Explained

This command adds a single event to the current schedule with no
dependencies (ready for immediate submission).

Syntax of the RUN Command: The syntax of the RUN command is as

follows:

RUN
──RUN───┬─eventname─┬───┬─────┬──┬────────┬──┬──────────┬──────
├─sclname──┤ └─.vv─┘ └─,L=nnn─┘ └─,─┬─A─┬──┘
└─tasknm───┘ ├─C─┤
├─D─┤
├─E─┤
└─U─┘
──┬─────────────┬──┬──────────────────────────────┬────────────
└─,N=nodename─┘ └─,A=─┬─CLPname,arg─────────┬──┘
├─command─────────────┤
├─imod-arg────────────┤
└─shellscriptname.arg─┘

Description of Command Elements

CA-Jobtrac Event Version Location Event GSS Node Argument

Command Name # ID Type Parameter
RUN eventname .vv ,L=nnn ,A ,N=nodename ,A={CLname,arg|
0sclname ,C command| imod-arg|
0tasknm ,D shellscriptname,arg}
,E
,U

Syntax Rules: The following rules apply to the syntax of the RUN command:
■ A space must separate RUN from the required variable.
■ The required variable must be no more than eight characters.
■ If specified, the version number must be separated from the required
variable by a period.
■ If specified, each of the location ID, event type indicators, GSS node name
indicator, and argument parameters must be separated by a comma.

Chapter 4. Adding Events to the Current Schedule 4-11

4.3 The RUN Command

Description of the Event Name: The following table describes the options
available for the REQUIRED variable:

Variable Description
eventname Specifies an event to be added to the current schedule.
Replace eventname with the name of the event.
0sclname Specifies a schedule to be added to the current
schedule. Replace sclname with the name of the
schedule member. A 0 (zero) must precede the sclname.
0tasknm Specifies a task to be added to the current schedule.
Replace tasknm with the name of the task. A 0 (zero)
must precede the tasknm.. For example, 0ARCHIVE,
0JOBARCH, and 0SYSARCH.

Description of the Version # Parameter: The version number parameter

(optional) specifies a version number. Replace vv with a two-digit version
number (01-99) to be assigned to the event being added. If you do not assign a
version number, CA-Jobtrac assigns the next available version number.

If you assign a version number and the event is already on the current
schedule with a matching event name and version number,
■ The event you want to add is not added to the current schedule
■ The message ALREADY EXISTS is displayed

Description of the Location ID Parameter: The location ID parameter

specifies a location ID to be assigned to the event being added. If you do not
assign a location ID, CA-Jobtrac assigns the default location ID of the user ID
issuing the command.

Description of the Event Type Parameters: The following table describes the
parameters available for the event type:

Parameter Description
,A Indicates that the named event is an AS/400 CLP using
the CALL command.
,C Indicates that the named event defines a command to be
executed at a particular remote node.
,D Indicates that the named event is a dummy job.
,E Indicates that the named event is a REXX IMOD.
,U Indicates that the named event invokes a UNIX Korn
shell script using the UNIX ksh command.

4-12 Operator Guide

 4.3 The RUN Command

Description of the GSS Node Parameter: The GSS node parameter indicates
the GSS node name (up to 16 characters) of the executing node for the named
event.

Description of the Argument Parameter: The argument parameter is

dependent upon the type of event as specified by the options [,A] [,C] [,E] or
[,U]. To include embedded blanks or commas, enclose the variable portion of
the argument with single quote marks. To include embedded single quotes,
replace the embedded single quote mark with a double quote mark.

Argument Description
[,A][,A=CLPname,arg] Specifies an argument to pass to the named AS/400 CLP. Replace
arg with a 1- to 255-character argument. CLPname,arg can contain
embedded blanks and commas.
If the CLPname is not specified, the default CLPname that is used
is the Alternate Member name (if one is specified) or the Event
Name (if no Alternate Member Name is specified).
[,C][,A=command] Specifies the exact command to be executed at a particular remote
node. command can contain embedded blanks and commas.
The UNIX environment is case-sensitive. Please be aware that the
ADD and RUN commands will translate the command to all
uppercase characters which may produce unexpected results when
passed to UNIX.
[,E][,A=imod-arg] Specifies an argument to pass to the named REXX IMOD. Replace
imod-arg with a 1- to 255-character argument. imod-arg can contain
embedded blanks and commas.
[,U][,A=shellscriptname,arg] Specifies an argument to pass to the named UNIX Korn shell
script. Replace arg with a 1- to 255-character argument.
shellscriptname,arg can contain embedded blanks and commas.
If the shellscriptname is not specified, the default shellscriptname
that is used is the Alternate Member name (if one is specified) or
the Event Name (if no Alternate Member Name is specified). The
UNIX environment is case-sensitive. Please be aware that the ADD
and RUN commands will translate the argument to all uppercase
characters which may produce unexpected results when passed to
UNIX.

Chapter 4. Adding Events to the Current Schedule 4-13

4.3 The RUN Command

4.3.2 Using the RUN Command

Procedure: To add a single event to the current schedule using the RUN
command, perform the steps below.
1. Access the CA-Jobtrac primary, Scheduled Event Display, Scheduled Event
Network, or Business Group Status panel.
2. Move the cursor to the COMMAND field.
3. Type the RUN command (see 4.3, “The RUN Command”).
4. Press Enter to execute the RUN command.
5. You proceed to the Scheduled Event Display panel with this event being
displayed.

4-14 Operator Guide

 4.3 The RUN Command

Examples: Version 1 of PRODJOB1 is already on the current schedule

awaiting execution. The following panel shows the RUN command required to
add PRODJOB1 to the current schedule for immediate submission. The
command defines the event's version number (02) and location ID (LOC=003).

The same command could be entered on the CA-Jobtrac primary panel.

 CA-Jobtrac Scheduled Event Display ROW 1 TO 18 OF 21


COMMAND ===> RUN PRODJOB1.2,L=3 SCROLL ===> PAGE
yy/mm/dd 14:3
Event ----Target----Successor Dep Current CMD= RALL
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ----------------------------------------
ACAPHIST 16:36  12/18 M WAITING DEPENDENCIES LATE
ACAPD 1:5 12/17 ACGL25 P WAITING DEPENDENCIES LATE
ACAP1 AS-AP 1/23 J WAITING RSTRT J 5643 LATE
ACAPD 1:3 12/17 ACAPD M WAITING DEPENDENCIES LATE
ACAP1D 1:5  12/17 ACAP15D M WAITING DEPENDENCIES LATE
ACAP11R 1:4  12/18 ACAPD J WAITING DEPENDENCIES LATE
ACAP12R 1:4  12/18 ACAPD J WAITING DEPENDENCIES LATE
ACAP15D 1:5  1/21 ACGL2D J WAITING DEPENDENCIES LATE
ACAP15D 1:5  12/17 ACGL2D PD WAITING DEPENDENCIES LATE
ACAP35R 1:4  12/18 ACAPD J WAITING DEPENDENCIES LATE
ACAR4 1:3  1/21 ACAR43 P WAITING DEPENDENCIES LATE
ACAR4 15:6 11/1 M WAITING DEPENDENCIES LATE
ACAR4 1:3  12/17 ACAR43 PM WAITING DEPENDENCIES LATE
ACAR41 1:5  1/21 ACGL21R P WAITING DEPENDENCIES LATE
ACAR41 1:5  12/17 ACGL21R PM WAITING DEPENDENCIES LATE
 
The following panel shows the RUN command required to add schedule
TESTSCD to the current schedule for immediate submission. Note that 0 (zero)
is added at the beginning of the schedule name.

 CA-Jobtrac

COMMAND ===> RUN TESTSCH yy/mm/dd 16:55

Primary Commands:
RALL - List all events CA-JCLTRAC-JCL analysis system
J=evnm - List events beg. w evnm ISERVE - CA-GSS IMOD facility
K=status - List events w/ status JCL - Edit production JCL
D=dep - List events w/ deps SCL - Edit SCL
B=bgname - List events of a bus. grp. SYS OPTS - Update global options
T=hhmm - List events by target time SYS HOLS - Holiday calendar maint.
BUSGRP - Business group status SYS CYCS - Cyclic calendar maint.
ADD - Add event to schedule JTS - Table services
GSO - Generate schedules online OUT - Sysout capture

 The following line commands will be available for SCHEDULED EVENT DISPLAY:
 - CA-View sysout brwse H - Event history R - Rerun/restart
A - Release dependencies I - Audit history S - Select (detail)
C - Cond code exceptions L - Dependent jobstream T - Create/edit temp JCL
D - Delete event M - Manual actions V - Volume pull list
E - Edit JCL/SCL O - Browse sysout Y - CPM info
F - Display DSN triggers P - Purge event X - Resource dependency
G - GSO Q - Sysview Jobsum ? - View documentation
 

Chapter 4. Adding Events to the Current Schedule 4-15

4.4 The Event/Jobstream Addition Panel

4.4 The Event/Jobstream Addition Panel

You can use the Event/Jobstream Addition panel to add either a single event
or a job stream to the current schedule from the ADD or RUN command.

You do not need to create a schedule member to use this method. Instead,
you code scheduling and execution conditions for each event on the
Event/Jobstream Addition panel.

This method is used for one-time additions to the current schedule.

Unsupported Additions: The following are not supported for use on the
Event/Jobstream Addition panel:
■ Addition of an event or job stream that is a REXX IMOD, Unix Korn shell,
or AS/400 CLP
■ Addition of an environmental dependency for an event or job stream

Defining Dependencies Using the Event/Jobstream Addition Panel: You

can assign specific execution dependencies to the events you add to the current
schedule using the Event/Jobstream Addition panel. You assign these
conditions (such as target time and predecessors) using SCL codes on the
panel. For more information on the event/job stream addition panel, see 4.4.1,
“Displaying the Event/Jobstream Addition Panel.”

All events added to the current schedule using the Event/Jobstream Addition
panel are automatically assigned a process period of RQ-userid (userid is the ID
of the user adding the events).

If an event requires conditions that cannot be defined on the Event/Jobstream

Addition panel (such as data set count), you can add them using the
Scheduled Event Detail panel once the event is on the current schedule (see the
editing fields information in 5.2.4, “Using the Scheduled Event Detail Panel”).

The maximum condition code for the event is set as defined in the RAMAXCC
startup parameter (described in the Getting Started).

The SCHEDULE ENVIRONMENT field defaults to the SCHENV startup

parameter (described in the Getting Started).

4-16 Operator Guide

 4.4 The Event/Jobstream Addition Panel

4.4.1 Displaying the Event/Jobstream Addition Panel

You display the Event/Jobstream Addition panel using the Add command.
Enter A or ADD at the COMMAND field of the CA-Jobtrac primary,
Scheduled Event Display, Scheduled Event Network, or Business Group Status
panels to display the Event/Jobstream Addition panel, shown below.

 CA-Jobtrac Event/Jobstream Addition


COMMAND ===> Bus Group ===>
yy/mm/dd 14:44
Event--- Vers--- Target------ Deps Predecessor----- Successor ------ Cond LOC
Name Date.V Time  Date Event--- Date.V Event--- Date.V Code ID
-------- ------- ---- -- ---- ---- -------- ---- -- -------- ---- -- ---- ---
>
>
>
>
>
>
>
>
>
>
>
>

Enter ENDSAVE to update schedule or END to cancel request.

 
Fields Explained: Like the fields in schedule, Event/Jobstream Addition
panel fields are completed with SCL. As in schedules, SCL for each event is
coded in a record, with each parameter in the record aligned in columns below
a field heading. See the Schedule Creation Guide for complete information about
SCL and schedules.

Most of the fields on the Event/Jobstream Addition panel have the same
function as corresponding fields in schedules, though some of the headings are
different (see descriptions below).

COMMAND: Lets you enter commands ENDSAVE to save and add the event
to the checkpoint or END which cancels the request.

Bus Group: This field names the business group with which all events on the
panel are associated. This field's function is equivalent to the function of the
@BUSGRP global control record in schedules. The default is the user ID that is
issuing the command.

Event Name: Entries in the Event Name field specify the name of the event
to be added to the current schedule. This field has the same function as the
Event Name (EVENTNM) field in schedules.

Chapter 4. Adding Events to the Current Schedule 4-17

4.4 The Event/Jobstream Addition Panel

Vers Date.V: Two fields fall under this heading. One field (in the four
columns under Date) specifies a date to be associated with the version number
of the event named in the Event Name field. The second field (in the two
columns beginning under V) specifies a version number to be assigned to the
event.

The entry under Date must be in the form mmdd, where mm is a two-digit
number indicating the month (01-12) and dd is a two-digit number indicating
the day of the month (01-31). You can leave this field blank, in which case
CA-Jobtrac assigns the current date. This field must contain either a date, an *,
or a blank.

The entry under V must be in the form nn, where nn is a two-digit number
specifying a version number (01-99). You can leave this field blank, in which
case CA-Jobtrac assigns a version number.

If an event already exists on the current schedule with the same date and
version number specified in these fields, the event is not added to the current
schedule. The message * ALREADY EXISTS * is displayed.

Target Time **: These fields work together to define target and start times for
submission of the event being added to the current schedule. If the ** field is
blank, the Time field entry specifies the target and start time for the event
being added. If an asterisk is entered in the ** field, the Time field entry
specifies the target time only and the start time is ASAP (as soon as possible).

The entry in the Time field must be in the form hhmm, where hh is a two-digit
number specifying the hour (00-23) and mm is a two-digit number specifying
the minute (00-59). You can also complete the Time field with an * (asterisk), in
which case CA-Jobtrac assigns the time at which the event is added to the
current schedule.

The ** field can be blank, or an * (asterisk) can be entered in the second

column.

Target Date: This field specifies the date for which submission of the event
should be scheduled.

The entry in the Date field must be in the form mmdd, where mm is a two-digit
number specifying the month (01-12) and dd is a two-digit number specifying
the day of the month (01-31). An * (asterisk) can replace a date in this field, in
which case CA-Jobtrac assigns the current date.

Unlike the Date (DATE) field in schedules, you cannot enter dates in the form
*dd, mm*, or *+nn.

4-18 Operator Guide

 4.4 The Event/Jobstream Addition Panel

Deps: Entries in the Deps field specify execution dependencies to be assigned

to the event being added. Up to four execution dependency codes can be
entered. This field's function is equivalent to the function of the Execution
Dependency (DEPS) field in schedules. You can specify the following
dependency codes:

Entry Description
M Manual release dependency. The event is not eligible for
submission until the M code is removed manually or all items on
a Manual Action Detail panel checklist are satisfied. See the
Schedule Creation Guide for information about creating a Manual
Action Detail panel for an event.
P Predecessor event dependency. The event is not eligible for
submission until all predecessor events complete and CA-Jobtrac
removes the P code.
J JCL required dependency. This dependency indicates that JCL
must be supplied or altered prior to automatic submission. The
event is not eligible for submission until the J code is removed
manually, or until the event is externally submitted using
AUTO-SCHD.
D Data set required dependency. The event is not eligible for
submission until all data sets required by the event have been
created and CA-Jobtrac removes the D code.
O Output release dependency. This dependency does not affect
submission of the event, but it requires verification of the event's
output after the event completes. No successors to the event can
run until the O code is removed manually.
A Abend bypass. This is not an execution dependency, but a release
of dependencies for successors. If an event with this code abends,
the predecessor dependency is removed from successors to the
event (its successor events will be eligible for submission). JCL
errors and COND CODE checks are not considered abends for
processing of this dependency code.
| E Edit JCL dependency. This dependency prevents submission of
| the event until its JCL is edited using a J line command.
? View documentation dependency. This dependency prevents
submission of an event until its documentation is viewed using
the ? line command. The event is not eligible for submission until
the documentation is reviewed and the ? code is removed
manually.

Chapter 4. Adding Events to the Current Schedule 4-19

4.4 The Event/Jobstream Addition Panel

Entry Description
Q Queued release dependency. This dependency indicates that the
event's JCL is to be submitted outside of CA-Jobtrac. Once
submitted, the event is held in the JES queue and released
automatically by CA-Jobtrac when dependencies are met. An
AUTO-SCHD event with Q in column 70 of the first event record
must be submitted to satisfy this dependency.

Predecessor Event- Date.V: Entries in these three fields define the events
that are predecessors to the event being added to the current schedule. A
predecessor dependency is assigned to the event when it is added.

The Event Name field must contain the name of the predecessor event.

If you specify a predecessor, you must complete the Date field as follows:
■ If a date in the form mmdd is entered, only a version of the predecessor
added to the current schedule on the date specified is considered the
predecessor.
■ If the Date field is blank, only a version of the predecessor that matches
the version of the event being added is considered the predecessor.

The V field can specify a version number to be associated with the predecessor
event. The following apply to entries in this field:
■ If a version number in the form nn (two-digit version number, 01-99) is
entered, only the version of the predecessor with a matching version
number is considered the predecessor.
■ If the V field is blank, the version number of the task defining the
predecessor is assigned.
■ You can add a maximum of up to 12 predecessors per event.

Successor Event- Date.V: Entries in these three fields define the events that
are successors to the event being added to the current schedule.

The Event Name field must contain the name of the successor event.

If you specified a successor, you must complete the Date field as follows:
■ If a date in the form mmdd is entered, only a version of the successor
added to the current schedule on the date specified is considered the
successor.
■ If the Date field is blank, only a version of the successor that matches the
version of the event being added is considered the successor.

4-20 Operator Guide

 4.4 The Event/Jobstream Addition Panel

The V field can specify a version number to be associated with the successor
event. The following apply to entries in this field:
■ If a version number in the form nn (two-digit version number, 01-99) is
entered, only the version of the successor with a matching version number
is considered the successor.
■ If the V field is blank, the version number of the task defining the
successor is assigned.
■ You can add a maximum of up to 12 successors per event.

Cond Code: An entry in this field defines the maximum condition code for
the event being added. The default maximum condition code for the event is
set as defined in the RAMAXCC startup parameter (described in the Getting
Started). No step in the event may complete with a condition code higher than
the value defined in this field. The Cond Code field has the same function as
the Maximum Condition Code (CCDE) field in schedules. If the condition code
parameters you define are violated, CA-Jobtrac imposes a dependency
requiring you to check the event's output before successor events can be
submitted.

An entry in this field must be in the form nnnn, where nnnn is a four-digit
number specifying the maximum condition code allowable (0000-4095). If this
field is left blank, no condition code testing is performed. All dummy jobs are
assigned a maximum condition code of 0000.

LOC ID: The LOC ID field defines a location ID for the event being added.
This field has the same function as the Location (LOC) field in schedules.

An entry in this field must be in the form nnn, where nnn is a three-digit
number specifying a location ID. If this field is left blank, your default location
ID is assigned.

Chapter 4. Adding Events to the Current Schedule 4-21

4.4 The Event/Jobstream Addition Panel

4.4.2 Using the Event/Jobstream Addition Panel

Using Continuation Records on the Event/Jobstream Addition Panel: You
can use continuation records on the Event/Jobstream Addition panel to define
additional predecessors and/or successors.

Unlike continuation records in schedules, continuation records on the

Event/Jobstream Addition panel do not require a + in column one.

To code a continuation record, leave the Event Name field blank and code
predecessor and/or successor information.

CA-Jobtrac automatically considers a record with no event name to be a

continuation of the previous event record.

Up to 11 continuation records can be coded for a single event (a total of 12

records can be coded, the first of which must be a primary record).

Procedure: To add events to the current schedule using the Event/Jobstream

Addition panel, perform the following steps:
1. Type A or ADD in the COMMAND field of the CA-Jobtrac primary,
Scheduled Event Display, Scheduled Event Network, or Business Group
Status panel. Press Enter to display the Event/Jobstream Addition panel.
2. Code records to define conditions for the execution of each of your events.
For more information on the Event/Jobstream Addition panel, see 4.4.1,
“Displaying the Event/Jobstream Addition Panel.”
3. If the events you are adding should be associated with a non-default
business group, type the name of the schedule at the Bus Group prompt.
4. Press Enter to check the syntax.
5. If a syntax error is found, correct it and repeat Steps 4 and 5.
6. When the syntax is correct, type ENDSAVE at the COMMAND prompt
and press Enter to add the events coded in Step 2 to the current schedule.
To exit without saving your changes, type END at the COMMAND
prompt and press Enter or press PF3.

4-22 Operator Guide

 4.4 The Event/Jobstream Addition Panel

Examples: TESTJOB1 must be added to the current schedule with the current
date as the version date (blank Vers Date field) and version number 01
assigned by CA-Jobtrac (blank V field). The event's target and start times are
both 6 PM (1800 in the Time field and no entry in the ** field) and the target
date is the current date (* in the Target Date field). TESTJOB1 has no other
dependencies and no predecessors or successors. Condition code testing is not
required, and its location ID is the same as the default location ID.

TESTJOB2 requires a version date of March 12 (0312) and version number 6

(06). The event's target time is 7 PM (1900), but it should start as soon as
possible (* in the ** field). The target date is March 12 (0312). No other
dependencies are required and there are no predecessors or successors. No
step may complete with a condition code greater than 4 (0004). The location ID
should be 11 (011).

TESTJOB3 requires no specific date or version number (blanks in Vers Date.V

fields). The event's target and start time should be the time at which the event
is added to the current schedule (* in Time field and no entry in the ** field).
The event should be submitted on the current date (* in the Date field).
TESTJOB3 should be released manually, so M is coded in the Deps field. Two
events are predecessors: TESTJOB1 (any version), and Version 6 of TESTJOB2
added to the schedule March 12. The third version of TESTJOBC added to the
schedule March 12 is a successor.

All of the above events should be associated with the schedule TESTSCD. The
records required to add these events to the current schedule are shown below.
Press Enter to check the syntax and return the cursor to the COMMAND field.
Then type ENDSAVE in the COMMAND field and press Enter. The events on
the panel are added to the current schedule, and a Scheduled Event Network
panel showing the events is displayed. See 5.2, “Scheduled Event Detail Panel”
for a description of the panel.

 CA-Jobtrac Event/Jobstream Addition


COMMAND ===> Bus Group ===>
yy/mm/dd 14:44
Event--- Vers--- Target------ Deps Predecessor----- Successor ------ Cond LOC
Name Date.V Time  Date Event--- Date.V Event--- Date.V Code ID
-------- ------- ---- -- ---- ---- -------- ---- -- -------- ---- -- ---- ---
> TESTJOB1 18 
> TESTJOB2 312 6 19 312 4 11
> TESTJOB3   M TESTJOB1
> TESTJOB2 312 6
> TESTJOBC 312 6
>
>
>
>
>
>
>
>

Enter ENDSAVE to update schedule or END to cancel request.

 

Chapter 4. Adding Events to the Current Schedule 4-23

4.5 Using Schedules

4.5 Using Schedules

The current schedule maintains information about current work (for example,
events to be executed). The information in the current schedule changes to
reflect production activity.

You use schedules (and other methods) to add events to the current schedule.
Unlike the current schedule, the information in schedules does not change
unless you change it. Schedules are therefore considered permanent schedules.

Schedules contain the information used to schedule and submit events. When
a schedule is executed, CA-Jobtrac loads information from the schedule to the
current schedule.

You will add most of your events to the current schedule using schedules. You
probably will not use this method for events that have irregular process
periods (such as events that run on request only, or that run only one time),
though you may define on-request schedules ahead of time in schedules.

The Schedule Creation Guide contains complete information about creating

schedules.

Description of Schedules: Schedules are a collection of SCL (Schedule

Control Language) statements that define scheduling and execution
requirements for events. Schedules are contained in CA-Jobtrac SCL library
members. Schedules are SCL library members in which you code parameters
used to add events to the current schedule. See the Schedule Creation Guide for
more information about SCL and how to create schedule members.

4-24 Operator Guide

 4.5 Using Schedules

A sample schedule is shown in the figure below. Records beginning with 0

(zero) indicate that the event name following the 0 is either a schedule or a
dynamic task (see the Schedule Creation Guide for detailed information about
the fields in schedules). In the example below:
■ The record with event name TESTJOB1 contains parameters used to add
TESTJOB1 to the current schedule.
■ The record with event name 0DAYSCHD contains parameters used to add
the schedule DAYSCHD to the current schedule.
■ The record with event name 0ARCHIVE contains parameters used to add
the ARCHIVE task to the current schedule.

 EVENTNM TIME DATE DEPS RELEASE1RELEASE2RELEASE3RELEASE4PROCESSPOPDCCDELOCVV 

TESTJOB1 8  WORKDAYS
DAYSCHD 9  WORKDAYS
ARCHIVE 1  WORKDAYS
 
How Schedules Are Used to Update the Current Schedule: Schedules
contain SCL for events. When a schedule is executed, CA-Jobtrac checks the
SCL parameters coded for each event. If the scheduling dependencies of the
event match the current day's calendar resolution, CA-Jobtrac adds the event
to the current schedule (see the Schedule Creation Guide for more information
about scheduling dependencies).

The information added to the current schedule includes the time and date
when the event is scheduled to run, as well as other information coded in the
schedule (such as names of successors to the event).

Adding events to the current schedule using schedules is considered a

dynamic update of the current schedule since this function is performed
completely within the CA-Jobtrac task without batch execution.

Functions Not Automatically Invoked: When you use schedule members to

add an event to the current schedule, you will not invoke either condition code
checking or the program filter table if you leave fields 72-75 blank. If you
specify a certain job level in these fields, then the event is checked at that level.

Chapter 4. Adding Events to the Current Schedule 4-25

4.5 Using Schedules

4.5.1 Using Schedules to Update the Current Schedule

Procedure: To add events to the current schedule, perform the following
steps:
1. Code scheduling and execution requirements for your events in a schedule
(see the Schedule Creation Guide for complete information about creating
schedules).
2. Add the schedule created in Step 1 to the current schedule so that it can be
executed (see the following topic).

Example: An example is the best way to explain how to add a schedule to

the current schedule using a schedule.

For this example, assume the following:

■ You are adding a schedule named TESTSCD to the current schedule.
■ You are using a schedule named SCHDMEM to add TESTSCD to the
current schedule.

The first step is to use SCL to code TESTSCD's scheduling information in

SCHDMEM, as shown in the figure below. Note that the event name used for
schedules is 0 (zero) followed by the schedule name (in this case, 0TESTSCD).

 EVENTNM TIME DATE DEPS RELEASE1RELEASE2RELEASE3RELEASE4PROCESSP OPDCCDELOCVV 

TESTJOB1 8  WORKDAYS
TESTSCD 9  WORKDAYS
TESTJOB2 1  WORKDAYS
 
Once SCL for TESTSCD is added to SCHDMEM, SCHDMEM must be
executed. When SCHDMEM executes, it adds TESTSCD to the current
schedule.

You can add SCHDMEM to the current schedule using any of the methods on
4-2, including using a schedule.

One way to manage scheduling and execution of schedules is to use a master

schedule. You use SCL to code scheduling information for all of your
schedules in a single master schedule (usually called MASTSCL). Then, when
the master schedule executes, all of your schedules are added to the current
schedule.

4-26 Operator Guide

 4.5 Using Schedules

Creating a Self-Perpetuating Schedule: You can create a schedule that

perpetually reschedules itself. Whenever the schedule executes, it
automatically reschedules itself. After the schedule is initially executed, it runs
automatically until stopped.

For example, suppose you want MASTSCL to perpetually reschedule itself.

The figure below shows one way to do this. The schedule shown is MASTSCL.
When MASTSCL is executed on Monday through Thursday (=MTWT...), it
reschedules itself to execute the following morning (*+1) at 8 AM (0800). When
MASTSCL is executed on Friday (FRIDAY), it reschedules itself for the
following Monday (*+3).

 EVENTNM TIME DATE DEPS RELEASE1RELEASE2RELEASE3RELEASE4PROCESSPOPDCCDELOCVV 

TESTJOB1 9  WORKDAYS
TESTJOB2 1  WORKDAYS
MASTSCL 8 +1 =MTWT... /
+ +3 FRIDAY
 

Chapter 4. Adding Events to the Current Schedule 4-27

4.6 The Batch Method

4.6 The Batch Method

You can load events to the current schedule using a batch event. The batch
method lets you load the current schedule along with your other batch events.
One application for this method is to load events to the current schedule from
a remote location or LAN (local area network).

Using the batch method, you must use SCL to code scheduling and execution
dependencies for your events. The SCL records are then used as input to a
batch event that loads the events to the current schedule.

How the Batch Method Loads the Current Schedule: When the batch
schedule load executes, the GJTRVSCH program is invoked. GJTRVSCH checks
the SCL parameters coded for each event. If the scheduling dependencies of
the event match the current day's calendar resolution, GJTRVSCH adds the
event to the current schedule (see the Schedule Creation Guide for detailed
information about scheduling dependencies).

The information added to the current schedule includes the time and date
when the event is scheduled to run, as well as other information coded in the
SCL used as input to the batch event (such as names of successors to the
event).

Adding events to the current schedule using the batch method is not a
dynamic update of the current schedule since events are loaded from a
non-CA-Jobtrac source using batch execution.

4-28 Operator Guide

 4.6 The Batch Method

4.6.1 Using the Batch Method

Procedure: Perform the steps below to add events to the current schedule
using the batch method.
1. Create input for the batch event by coding scheduling and execution
requirements for your events (see the Schedule Creation Guide for complete
information about coding scheduling and execution requirements).
2. Code JCL as required, using the SCL created in Step 1 as input (for more
information on the JCL statement , see “JCL Statements Required to Use
the Batch Method”).
3. Submit the event to the system in batch.

JCL Statements Required to Use the Batch Method: The following JCL
statements must appear in a batch event used to add events to the current
schedule:
■ JOB statement
■ EXEC statement invoking the GJTRVSCH procedure
■ SYSIN DD statement defining the source of SCL

You can include other JCL statements as required.

Example 1: The figure below shows an example of JCL used to load events
to the current schedule using the batch method. Note that the input to this
batch event is a schedule (WDAYSCD).

//GJTRVSCH JOB ...

//EXEC EXEC GJTRVSCH,SOUT=X
//SYSIN DD DSN=your.TRACS(WDAYSCD),DISP=SHR

Example 2: The figure below shows another example of JCL used to load the
current schedule using the batch method. In this example, the SCL for the
events to be loaded is included in the JCL member.

 //GJTRVSCH JOB ... 

//EXEC EXEC GJTRVSCH
//SYSUDUMP DD SYSOUT=
//SYSIN DD 
@HOL2
@WD2=SAT
EVENTNM TIME DATE DEPS RELEASE1RELEASE2RELEASE3RELEASE4PROCESSP OPDCCDELOCVV
TESTJOB1 8  J +TESTJOB2 WORKDAYS 2
TESTSCD 9  CYCDAYM12
TESTJOB3 1  MONDAY 42
ARCHIVE 11  WORKDAYS
 

Chapter 4. Adding Events to the Current Schedule 4-29

4.7 The AUTO-SCHD Feature

4.7 The AUTO-SCHD Feature

The AUTO-SCHD feature is used to control and track:
■ Manually submitted JCL to the current schedule and track jobs' execution
■ Manually submitted JCL to remove a 'Q' or 'J' dependency of a job already
on the current schedule

Note: The AUTO-SCHD function is limited to jobs that execute within the
CA-Jobtrac complex.

AUTO-SCHD is especially useful for scheduling on-request jobs and for

submitting scheduled jobs manually from remote locations.

To submit jobs using AUTO-SCHD, you use one of the following methods:
1. In the Getting Started, see the parameter AUTOQ. This is where you define
a JES class to CA-Jobtrac. Whenever a job is submitted to that class, the
checkpoint will be checked for a job with the same name that has a 'Q' or
'J' dependency. If found, the job will satisfy that dependency. Otherwise,
the job is added to the checkpoint with no dependency codes. Valid only
for JES2 users.
2. In the Getting Started, see the parameter AUTOC. The default
| AUTO-SCHD character is '>' (greater than sign). This parameter can either
be in the JCL in column 71 of the first JOB statement or as a positional
parameter on the $AUTO step in the JCL.

The parameter in column 71 is the old method and is still available to JES2
users. Using the $AUTO step is the new and preferred method. It is the only
method available to JES3 users.

To display the AUTOQ or AUTOC parameters from CA-Jobtrac ISPF Main

Menu, enter SYS OPTS and then select number 1.
Note: CA-Jobtrac does not submit the JCL for the AUTO-SCHD feature. All
automatic JCL override parameters are passed to the internal reader by
the submitting program (for example, TSO SUBMIT). CA-Jobtrac will
not receive control until after the JCL has been submitted and cannot
act upon JCL overrides or date record insertion (AJO, ADI, and JMF
functions).

4-30 Operator Guide

 4.7 The AUTO-SCHD Feature

4.7.1 Codes Used with AUTO-SCHD

Coding AUTO-SCHD: The codes used by AUTO-SCHD to submit an event
are positional. They must be coded in one of the following two places:
■ In columns 62-71 on the first statement of the event being submitted. This
is the old method and is still available to JES2 users. The figure below
shows the form and position of the codes.

 1---+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8 
//jobname JOB ( ),... VvvCcccca>
or
//jobname JOB (), >
or
On the jobcard the CLASS=n, and n is the AUTOC PARM in the INSTALLATION option
 
or
■ In a special step that you add to the end of the event being submitted. This
is the preferred method and is available to JES2 and JES3 users. The figure
below shows the form and position of the codes.

 1---+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8 
//$AUTO EXEC PGM=$A,COND=(,LE),PARM='a>,VERS=vv,COND=cccc,LOC=nnn'
or
//$AUTO EXEC PGM=$A,COND=(,LE),PARM='>'
 
When you add this step to the JCL, you must follow these rules:
■ Code the step name, PGM=, COND=, and PARM= fields in the order
shown.
■ Code the AUTO-SCHD step on one statement. It may not be continued.
■ The first entry in the PARM field is positional and required. It must be
coded and it must be first in the PARM field. When using a blank
character for AUTO-SCHD, you cannot use the VERS, COND, and LOC
keywords.
■ The VERS, COND, and LOC keywords are optional and may be coded in
any order.
■ Leading zeros in the VERS, COND, and LOC values may be omitted.

Chapter 4. Adding Events to the Current Schedule 4-31

4.7 The AUTO-SCHD Feature

Encountering Errors: If the AUTO-SCHD step encounters an error,

CA-Jobtrac takes the following actions:

If . . . Then . . .
The step name is not $AUTO or the The step is ignored.
program is not $A
A step named $AUTO executes a It must all be on one statement, and
program named $A must contain COND=(0,LE) or
COND=(0,GT) and the required
PARM field. Otherwise, the step is
ignored.
The positional PARM field is coded The event either fails with a JCL
incorrectly error or the step is ignored.
The event has improper dependencies It fails. This situation could occur if,
for example, you submit JOBA as a
normal AUTO-SCHD event, but there
is a JOBA waiting to be submitted
from CA-Jobtrac.
Keyword parameters are miscoded The step is ignored or the parameters
and the event is recognized as a are ignored.
CA-Jobtrac event (that is, has a valid
AUTO-SCHD character)

AUTO-SCHD Code Explained: The following table describes the function of

each element from the AUTO-SCHD feature.

 1---+----1----+----2----+----3----+----4----+----5----+----6----+----7----+---- 
//jobname JOB (), ...VvvCcccca>
or
//$AUTO EXEC PGM=$A,COND=(,LE),PARM='a>,VERS=vv,COND=cccc,LOC=nnn'
 

4-32 Operator Guide

 4.7 The AUTO-SCHD Feature

Element Function
a a can be either a blank (not specified) or the letters 'Q' or 'R' or
'T'.
If this control character is a blank field or not specified and the
job is not on the current checkpoint, it adds the job to the
current checkpoint and tracks the job to its completion.
Note: VER=, COND=, and LOC= in the PARM field are
ignored when a control record is not used.
If a is replaced by T, the job on the current checkpoint has to
have a 'J' dependency. This job will be tracked to its
completion.
If a is replaced by Q, the job on the current checkpoint has to
have a 'Q' dependency. This job will be tracked to its
completion. This event can have other dependencies and will
be released when all dependencies are met.
If a is replaced by R and the job is not on the current schedule,
it is added to the schedule. After the job is added (or if it was
already on the current checkpoint), the jobs are treated exactly
like events with a Q dependency code.
> Invokes the AUTO-SCHD feature. This character may be any
character assigned during installation (see the Getting Started.
The > (greater-than symbol) is the default and is used in all
examples in this manual.
vv Optionally coded to specify a version number for the job you
are submitting. Replace vv with a two-digit version number
(01-99). Not valid with a blank 'a' code.
cccc Optionally coded to define the maximum allowable condition
code for the job you are adding. Replace cccc with a four-digit
condition code value (0000-4095). If you do not define this
value, CA-Jobtrac assigns 0000. Not valid with a blank 'a' code.
This affects jobs not already scheduled by a schedule. If the job
is already on the current schedule, its SCL specifications
override the cccc specification on the JOB statement.
nnn Optionally coded to define the Location parameter. This is
normally used for where the JCL is kept. However, in this case,
it is only used so that users with this location in the
TRACAUTH (security macro) are able to update these jobs if
needed or to check on the status of these jobs. Location 000 is
the default for job submission. All other locations must be
specified in $AUTO updates.

Chapter 4. Adding Events to the Current Schedule 4-33

4.7 The AUTO-SCHD Feature

4.7.2 Sample SCL/JCL for AUTO-SCHD Jobs

 EVENTNM TIME DATE DEPS RELEASE1RELEASE2RELEASE3RELEASE4 PROCESSP


@BUSGRP=AUTOJOBS
        
----+----1----+----2----+----3----+----4----+----5----+----6----+--
QAUTO1 ASAP  QM DAILY
TAUTO1 ASAP  J DAILY
 
Here are sample JCL members for the above jobs:

//QAUTO1 JOB (PROD),MSGCLASS=X,CLASS=A,REGION=248K

//STEP1 EXEC PGM=IEFBR14
//SYSPRINT DD SYSOUT=
//$AUTO EXEC PGM=$A,COND=(,LE),PARM='Q<,VERS=1,COND='

and

//TAUTO1 JOB (PROD),MSGCLASS=X,CLASS=A,REGION=248K

//STEP1 EXEC PGM=IEFBR14
//SYSPRINT DD SYSOUT=
//$AUTO EXEC PGM=$A,COND=(,LE),PARM='T<'

Results of Using AUTO-SCHD: The following explains the usage of

AUTO-SCHD:
■ If the control character (in column 70 of the JOB statement or in the first
positional parameter on the step statement) is not Q or T, the event is
added to the current schedule. If a duplicate of the event already exists on
the current schedule, CA-Jobtrac assigns a unique version number to the
event being added (if none is coded). If a version number is coded on the
event being added, it must be unique, or the event is not added to the
current schedule.
■ If the control character (in column 70 of the JOB statement or in the first
positional parameter on the step statement) is R and an event with the
same event name is not on the current schedule, the event is added to the
current schedule. When the event is on the schedule (regardless of how it
got there), it is treated as if Q were coded instead of R.
■ A process period of AUTO-SCHD is assigned only when the jobs are
added to the checkpoint.
■ A current event status of WAITING EXECUTION is assigned.
■ If the control character (in column 70 of the OB statement or in the first
positional parameter on the step statement) is Q, the event is not released
for execution until all dependencies are satisfied.
■ All jobs are tracked through execution to termination.

4-34 Operator Guide

 4.7 The AUTO-SCHD Feature

■ CA-Jobtrac can capture the sysout from these jobs.

■ The job and event execution history are archived.
■ Condition code testing is performed. The event is flagged on the Scheduled
Event Display panel if the maximum condition code value is exceeded. If
you do not specify a maximum condition code value, a value of 0000 is
used.
■ If the event abends or has a JCL error, it is not automatically rescheduled.

Samples of AUTO-SCHD JCL

Old Format Example 1: The figure below shows a sample event statement
used to add the event to the current schedule for immediate execution. Since
no version number is coded, CA-Jobtrac automatically assigns a unique version
number. Since no maximum condition code value is coded, the default value
0000 is used. This AUTO-SCHD method is available to JES2 users only.

 1---+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8 
//TESTJOB1 JOB (ACCTNG),'PROD CONTROL',CLASS=A >
 
Old Format Example 2: The next figure shows a JOB statement used to add
an unscheduled event to the current schedule with a specific version number
(03). A nondefault maximum condition code value (0008) is also specified. This
AUTO-SCHED method is available to JES2 users only.

 1---+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8 
//TESTJOB1 JOB (ACCTNG),'PROD CONTROL',CLASS=A V3C8 >
 
Recommended Format Example 3: The next figure shows a step statement
coded to add an unscheduled event to the current schedule using every
available feature. This AUTO-SCHD method is available to both JES2 and JES3
users.

 1---+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8 
//$AUTO EXEC PGM=$A,COND=(,LE),PARM='R>,LOC=3,VERS=2,COND=4'
 

Chapter 4. Adding Events to the Current Schedule 4-35

4.7 The AUTO-SCHD Feature

Function of the T Control Character: Manually submitting JCL with a T

control character coded in the JCL statement triggers immediate execution of
an event on the current schedule with a JCL dependency. This control
character causes AUTO-SCHD to:
■ Locate an event on the current schedule with the same event name (and, if
coded, version number) as the event being submitted.
■ Remove the JCL dependency (execution dependency code J) from the event
on the current schedule.
■ Execute the event on the schedule (the triggered event) immediately, even
if the event's scheduled time has not arrived. The JCL submitted by
AUTO-SCHD is used for execution.

Rules for Using the T Control Character: The following rules apply to using
the control character T:
■ T must be coded in either column 70 of the first JCL statement or in the
first positional parameter on the AUTO-SCHD step statement of the event
you are submitting.
■ The submitted event is assigned a JCL error if:
– The name of the event you are submitting does not match the name of
an event on the current schedule
– The event on the current schedule does not have a JCL dependency
(code J in Dep Codes field)
– The event on the current schedule has any dependencies other than J
– A version number (if any) coded for the event you are submitting does
not match the version number of the event on the schedule

Example 1: TESTJOB1 is on the current schedule with a JCL execution

dependency. You submit AUTO-SCHD JCL to supply the JCL required by
TESTJOB1, remove the JCL dependency, and execute TESTJOB1. JES2 users
may do this by coding the first statement in the JCL as shown in the figure
below. Because no maximum condition code value is specified, CA-Jobtrac
assigns the default maximum condition code value of 0000 for condition code
testing.

 1---+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8 
//TESTJOB1 JOB (ACCTNG),'PROD CONTROL',CLASS=A T>
 

4-36 Operator Guide

 4.7 The AUTO-SCHD Feature

Example 2: In this example, two versions of TESTJOB2 are on the current

schedule with JCL execution dependencies. The JCL being submitted satisfies
the JCL requirements of TESTJOB2 Version 02 only, so the version number of
the JCL being submitted is coded 02. The maximum condition code value is
defined as 0004. The figure below shows JCL that is valid for JES2 users.

 1---+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8 
//TESTJOB2 JOB (ACCTNG),'PROD CONTROL',CLASS=A V2C4T>
 
Function of the Q Control Character: Manually submitting JCL with a Q
control character removes the queued release dependency (execution
dependency code Q) from an event already on the current schedule. This
control character causes CA-Jobtrac to:
■ Locate an event on the current schedule with the same event name (and, if
coded, version number) as the JCL being submitted
■ Remove the queued release dependency (execution dependency code Q)
from the event on the current schedule
■ Hold the event in the JES (Job Entry Subsystem) queue until its scheduled
execution time, or, if execution time has arrived, until all remaining
dependencies are satisfied
■ Release the event for execution when all execution dependencies are
satisfied

Rules for Using the Q Control Character: The following rules apply to using
the control character Q:
■ Q must be coded either in column 70 of the JOB statement or as the first
positional parameter on the step statement of the event you are submitting.
■ The submitted event is assigned a JCL error if:
– The name of the event you are submitting does not match the name of
an event on the current schedule
– The event on the current schedule does not have a queued release
dependency (code Q in Dep Codes field)
– A version number (if any) coded for the event you are submitting does
not match the version number of the event on the schedule

Function of the R Control Character: Manually submitting JCL with an R

control character is almost the same as submitting JCL with a Q control
character. The only difference is that, if you use R, the event may or may not
already be on the current schedule. If an event with the same name is not
already on the current schedule, it is added. If an event with the same name is
already on the current schedule, it is not added. Either way, after the event is
on the current schedule, it is treated exactly as if it had a Q control character
coded.

Chapter 4. Adding Events to the Current Schedule 4-37

4.7 The AUTO-SCHD Feature

Using the AUTO-QUEUE Class: The Getting Started explains how to assign a
queue release (AUTOQ) job class. The queue release job class can automatically
perform the same function as coding blanks in a job's AUTO-SCHD record.

Instead of coding blanks in the job or step AUTO-SCHD statement, you code
CLASS=n in the JOB record, where n is the AUTO-QUEUE job class.

Example: TESTJOB3 is being submitted using the AUTO-QUEUE job class.

Manually submitting this JCL will add the job to the current checkpoint and be
tracked. The figure below shows a JOB statement coded as required (Q is the
defined AUTO-QUEUE class). This JOB statement may only be used by JES2
users.

 1---+----1----+----2----+----3----+----4----+----5----+----6----+----7----+----8 
//TESTJOB3 JOB (ACCTNG),'PROD CONTROL',CLASS=Q
 

4-38 Operator Guide

Chapter 5. Modifying the Current Schedule

This chapter details modifying the current schedule through online panels and
commands. It also describes JCL and SCL handling.

Chapter 5. Modifying the Current Schedule 5-1

5.1 Scheduled Event Display Panel

5.1 Scheduled Event Display Panel

The Scheduled Event Display panel is the primary source of information about
events on the current schedule. The panel displays such information as target
time and date, successor events, and current event status for each event on the
current schedule.

You can control which events are displayed on the Scheduled Event Display.
For example, you can display information about all events on the current
schedule by entering the command RALL (reset/update and display entire
schedule). You can also combine search commands to display only events with
specific characteristics, such as events with a specific prefix that are late. To
display a single event, you would enter the event's name in the COMMAND
field.

You can display detailed information about a single event or perform some
action on an event using a line command or a command issued from the
COMMAND field.

Displaying the Panel: You must enter a search command to display a

Scheduled Event Display panel (see 1.12.1, “Using the COMMAND Field” for
the procedure for entering search commands). Which events appear on the
display depend on the search command you use. For example, you can display
a single event on the current schedule, all events on the current schedule, or
only those events that have a specific characteristic (for example, late events).

If no events on the current schedule match the parameters you define in the
search command, the following messages are displayed on the Scheduled
Event Display panel:
■ NONE appears in the Event Name field.
■ NONE ON SCHEDULE appears in the message field in the upper-right
corner of the panel.

Descriptions of search commands are provided on the following pages.

5-2 Operator Guide

 5.1 Scheduled Event Display Panel

5.1.1 Event Name Prefix Search (J=) Command

If you enter a prefix (first few letters of the event name), all events beginning
with the prefix are displayed.

CA-Jobtrac treats all entries in the COMMAND field that are not specific
commands as event name prefix search commands. Any time you enter a
command, CA-Jobtrac first tries to use the entry as a command. If the entry is
not a command, CA-Jobtrac treats it as an event name prefix and searches the
current schedule for matching events.

This command can be part of a string of input commands (see 1.12.2, “Using
Strings of Search Keys”).

Syntax: The syntax of the event name prefix search command is as follows:

prefix
──prefix──────────────────────────────────────────────────────

OR

J=
──J=prefix────────────────────────────────────────────────────

Descriptions of Command Elements: Following are descriptions of the

elements of the event name prefix command:

Element Description
J= Optional search command.
prefix Replace prefix with the first few letters of the event or
events you want to display on the Scheduled Event
Display.

Example: The following command displays all events on the current

schedule having the prefix PROD:
J=PROD

Chapter 5. Modifying the Current Schedule 5-3

5.1 Scheduled Event Display Panel

5.1.2 Abend Search (A=) Command

You enter this command to display all events that abended with the code
specified, all events with condition code checks, or all events with catalog
checks.

This command can be part of a string of input commands (see 1.12.2, “Using
Strings of Search Keys”). You can only use one abend search command for
each string.

Syntax: The syntax of the abend search command is as follows:

A=
──A=─┬─abend─┬────────────────────────────────────────────────
├─CAT───┤
└─CC────┘

Descriptions of Command Elements: Following are descriptions of the

elements of the abend search command:

Element Description
A= Required command word.
abend Replace abend with the abend code of the events you
want to display on the Scheduled Event Display.
CC Displays all events with condition code checks.
CAT Displays all events with catalog checks.

Examples: The following command displays all events on the current

schedule that abended with code SD37:
A=SD37

The following command displays all events with condition code checks:
A=CC

The following command displays all events on the current schedule with
catalog checks:
A=CAT

5-4 Operator Guide

 5.1 Scheduled Event Display Panel

5.1.3 Add Location (ADDLOC=) Command

Use this command to add the location you specify to the Scheduled Event
Display. If you are authorized for the location you add (see 1.10, “Determining
Your Authorization Level”), you can perform functions on the events for the
added location. If you have no authorization for the added location, you can
only monitor the events.

If you use the TRACX26 user exit, you cannot use ADDLOC=nnn to add
locations.

This command must be issued as a stand-alone command. It cannot be part of

a string of input commands (see 1.12.2, “Using Strings of Search Keys”).

Syntax: The syntax of the ADD LOCation command is as follows:

ADDLOC=
──ADDLOC=nnn──────────────────────────────────────────────────

Descriptions of Command Elements: Following are descriptions of the

elements of the ADDLOC command:

Element Description
ADDLOC= Required command word.
nnn Required variable. Replace nnn with the location ID
(three-digit number, 000-254) of the events you want to
display on the Scheduled Event Display.

Example: The following command adds events on the current schedule for
location 003 to the Scheduled Event Display:
ADDLOC=3

Chapter 5. Modifying the Current Schedule 5-5

5.1 Scheduled Event Display Panel

5.1.4 Business Group Search (B=) Command

Use this command to display events associated with the business group name
specified in the command.

This command can be part of a string of input commands (see 1.12.2, “Using
Strings of Search Keys”). You can only use one business group search
command for each string.

Syntax: The syntax of the business group name search command is as

follows:

B=
──B=─┬─bgname──┬──────────────────────────────────────────────
└─prefix
─┘

Descriptions of Command Elements: Following are descriptions of the

elements of the business group name search command:

Element Description
B= Required command word.
bgname Required variable. Replace bgname with the business
group name of the events you want to display.
prefix* Replace prefix with the first few letters of the business
group names of the events you want to display on the
Scheduled Event Display.

Examples: The following command displays events associated with the

business group name PAYROLL:
B=PAYROLL

The following command displays events associated with business group names
beginning with AP:
B=AP

5-6 Operator Guide

 5.1 Scheduled Event Display Panel

5.1.5 Default Display (D) Command

Use this command to:
■ Set the default display command
■ Change the default display command
■ Execute the default command once it has been defined
■ Display all events on the current schedule if no default display command
has been defined

After you define a default command, the command is executed automatically

whenever you access CA-Jobtrac, bypassing the CA-Jobtrac primary panel (see
1.8.1, “Description of the CA-Jobtrac Primary Panel”).

This command must be issued as a stand-alone command: it cannot be part of

a string of input commands (see 1.12.2, “Using Strings of Search Keys”).

The default command may also be set using the PROFILE command.

Syntax: The syntax of the Default display command is as follows:

D
──D──┬─────────┬──────────────────────────────────────────────
├─command─┤
└─OFF─────┘

Chapter 5. Modifying the Current Schedule 5-7

5.1 Scheduled Event Display Panel

Descriptions of Command Elements: Following are descriptions of the

elements of the Default display command:

Element Description
D Required command word. If you do not specify a
command and a default command has already been
defined, the default command is executed. If you do
not specify a command and no default command has
been defined, all events on the current schedule are
displayed on the Scheduled Event Display.
command Replace command with the command you want to define
as the default command. This command replaces the
current default command, if one has been defined. The
default command remains in effect until changed or
removed, and it is executed automatically whenever
you access CA-Jobtrac.
OFF Removes any defined default command.

Examples: The following command defines K=LAW to be the default display

command (displays all events that are late, abended, or waiting):
D K=LAW

The following command executes a previously defined default command or, if

no default command has been defined, displays all events on the current
schedule:
D

The following command removes a previously defined default command:

D OFF

5-8 Operator Guide

 5.1 Scheduled Event Display Panel

5.1.6 Dependency Search (D=) Command

You enter this command to display all events with the dependency or
dependencies you specify.

This command can be issued as part of a string of input commands (see 1.12.2,
“Using Strings of Search Keys”). You can only use one dependency search
command for each string.

Syntax: The syntax of the Dependency search command is as follows:

D=
──D=─┬─A─┬────────────────────────────────────────────────────
├─D─┤
├─E─┤
├─I─┤
├─J─┤
├─M─┤
├─O─┤
├─P─┤
├─Q─┤
├─R─┤
├─T─┤
├─X─┤
├─?─┤
└──┘

Syntax Rule: You can use more than one of the required parameters. No
delimiter is required between the parameters. For example, you can enter the
command D=AMX.

Chapter 5. Modifying the Current Schedule 5-9

5.1 Scheduled Event Display Panel

Descriptions of Command Elements: Following are descriptions of the

elements of the Dependency search command:

Element Description
D= Required command word.
A Displays events with the abend bypass dependency
code.
D Displays events with the data set required dependency
code.
E Displays events with the edit JCL dependency code.
I Displays events with the environmental dependency
code.
J Displays events with the JCL required dependency code.
M Displays events with the manual release dependency
code.
O Displays events with the output release dependency
code.
P Displays events with the predecessor event dependency
code.
Q Displays events with the queued release dependency
code.
R Displays events with the resource dependency code.
T Displays events with time thresholds (the scheduled start
time differs from the target time).
X Displays events with the mutual exclusion dependency
code.
? Displays events with the view documentation
dependency code.
* Displays events submitted using AUTO-SCHD.

Examples: The following command displays all events on the current

schedule with the dependency code E:
D=E

The following command displays all events on the current schedule with
dependency codes D, P, and/or X:
D=DXP

5-10 Operator Guide

 5.1 Scheduled Event Display Panel

5.1.7 Date Parameter (DATE=) Command

Enter this command to define a new date parameter. CA-Jobtrac uses this
parameter to determine whether an event is shown on the Scheduled Event
Display, based on the event's target submission date. For example, if the date
parameter is set to 12/06, only events with a target date of 12/06 are displayed
on the Scheduled Event Display.

The current date parameter is shown in the Date= field on the Scheduled
Event Display panel (for more information, see 1.14, “Displaying the Scheduled
Event Display Panel.”

By default, this parameter is set to display events with any target date
(DATE=ALL). Whenever you access CA-Jobtrac, the default parameter is in
effect and all Scheduled Event Display panels show all events, regardless of
target date. If you want a specific date parameter, you must define it each time
you access CA-Jobtrac.

The date parameter that you set remains in effect until you change the
parameter or end the CA-Jobtrac session, at which time the parameter returns
to the default.

This command must be issued as a stand-alone command: it cannot be part of

a string of input commands (see 1.12.2, “Using Strings of Search Keys”).

Syntax: The syntax of the DATE parameter command is as follows:

DATE=
──DATE=─┬─dd────────┬─────────────────────────────────────────
├─mmdd──────┤
├─mmdd-mmdd─┤
└─ALL───────┘

Chapter 5. Modifying the Current Schedule 5-11

5.1 Scheduled Event Display Panel

Descriptions of Command Elements: Following are descriptions of the

elements of the DATE parameter command:

Element Description
DATE= Required command word.
dd Replace dd with a two-digit number defining a day
of the month (01-31). Subsequent Scheduled Event
Display panels will include only events with a
matching target day, regardless of the target
month.
mmdd Replace mm with a two-digit number specifying a
month (01-12). Replace dd with a two-digit number
specifying a day of the month (01-31). Subsequent
Scheduled Event Display panels will include only
events with a matching target date (both month
and day).
mmdd-mmdd Replace mm with a two-digit number specifying a
month (01-12). Replace dd with a two-digit number
specifying a day of the month (01-31). The form
mmdd-mmdd specifies a target date range for the
inclusion of events. Subsequent Scheduled Event
Display panels will include only events in the
matching target date range (both month and day).
ALL Sets the date parameter to display any event on the
Scheduled Event Display, regardless of target date.
This option is the default whenever you access
CA-Jobtrac.

Examples: The following command sets the date parameter to display any
event with a target date falling on day 10 of any month (such as 01/10 or
02/10):
DATE=1

The following command sets the date parameter to display any event with
target date 10/12:
DATE=112

The following command sets the date parameter to display any event with a
target date within the target date range of 10/12 through 10/30:
DATE=112-13

The following command displays any event on the current schedule, regardless
of target date:
DATE=ALL

5-12 Operator Guide

 5.1 Scheduled Event Display Panel

5.1.8 FIND Command

The primary command FIND is available on the Scheduled Event Display
panel to enable specific searching of the listed events. This command can be
used with the stand-ard ISPF scrolling commands to locate specific events.

FIND Command: The FIND primary command enables you to search the
listed events for a particular event or events.

The syntax of the FIND command is as follows:

FIND
┌─NEXT──┐
──FIND──┬──────────┬──┬───────────────┬──┼───────┼────────────
└─'string'─┘ └─'column-name'─┘ ├─ALL───┤
├─FIRST─┤
├─LAST──┤
└─PREV──┘

Column Names: The following table equates the field names on the
Scheduled Event Display panel to the column names used in the FIND
command:

Panel Field Name Command Column Name

Event Name EVENT-NAME
Target Time TARGET-TIME
Target * TARGET-*
Target Date TARGET-DATE
Successor Event(s) SUCCESSOR-EVENT(S)
Dep Codes DEP-CODES
Current Status CURRENT-STATUS

Chapter 5. Modifying the Current Schedule 5-13

5.1 Scheduled Event Display Panel

FIND Command Syntax Rules

■ You can limit the search for a character string to a specific column by
specifying a column name after the search argument.
■ You may enclose the search argument in single or double quotes.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.

For example, the following command finds all occurrences of TESTJOB1 in the
Event Name column.
FIND TESTJOB1 EVENT-NAME ALL
■ The default FIND command is FIND {'string'} NEXT.
■ If you specify FIND {'string'} ALL, the FIND command will scan the list to
determine the number of rows that contain the character string. It will
display the results and then position the panel to the first row that
matched the search.
■ You can enter the FIND command with no parameters to repeat the
previous find.

5-14 Operator Guide

 5.1 Scheduled Event Display Panel

5.1.9 SORT Command

The primary command SORT is available on the Scheduled Event Display
panel to enable specific sorting of the listed events. This command can be used
with the stand-ard ISPF scrolling commands to sort specific events.

SORT Command: The SORT primary command allows you to sort the list in
either ascending or descending order based on the values in a specified
column.

The syntax of the SORT command is as follows:

SORT
┌─A─┐
──SORT─┬───────────────┬──┼───┼───────────────────────────────
└─'column-name'─┘ └─D─┘

Column Names: The following table equates the field names on the
Scheduled Event Display panel to the column names used in the SORT
command:

Panel Field Name Command Column Name

Event Name EVENT-NAME
Target Time TARGET-TIME
Target * TARGET-*
Target Date TARGET-DATE
Successor Event(s) SUCCESSOR-EVENT(S)
Dep Codes DEP-CODES
Current Status CURRENT-STATUS

SORT Command Syntax Rules

■ You can specify which column to sort on by specifying a column name.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.

For example, the following command sorts on the Current Status column.
SORT CURRENT-STATUS
■ The default SORT command sorts in ascending order.
■ You can enter the SORT command without any parameters to put the list
back in its original sequence.

Chapter 5. Modifying the Current Schedule 5-15

5.1 Scheduled Event Display Panel

5.1.10 Search Key (K=) Command

You enter this command to display events with the characteristic or
characteristics you specify.

This command can be issued as part of a string of input commands (see 1.12.2,
“Using Strings of Search Keys”). You can only use one K= search command
for each string.

Syntax: The syntax of the search Key command is as follows:

K=
┌──
─────┐
──K=──┬─A─┬┴──────────────────────────────────────────────────
├─C─┤
├─D─┤
├─E─┤
├─H─┤
├─L─┤
├─N─┤
├─R─┤
├─S─┤
├─T─┤
├─V─┤
└─W─┘

Syntax Rule: You can use more than one of the required parameters. No
delimiter is required between the parameters. For example, you can enter the
command K=LAW.

5-16 Operator Guide

 5.1 Scheduled Event Display Panel

Descriptions of Command Elements: Following are descriptions of the

elements of the search Key command:

Element Description
K= Required command word.
A Displays events that terminated abnormally. This
includes events that abended, were purged, ended with
an abnormal condition code, or had a JCL error.
C Displays events that have completed. This includes
events that abended, were purged, or had a JCL error.
D Displays events with a dependency code.
E Displays events that are currently executing.
H Displays events with no incomplete predecessors.
L Displays events whose scheduled start time has passed
(late).
N Displays NJE jobs submitted on this node.
R Displays events that are awaiting rerun or step restart.
S Displays remotely-submitted NJE jobs.
T Displays events that are awaiting scheduled start time or
date.
V Displays events with Pred Count values that do not
match the number of current predecessors listed.
W Displays events that have been submitted by CA-Jobtrac
but have not begun execution (awaiting an initiator).

Examples: The following command displays all events on the current

schedule with dependency codes:
K=D

The following command displays all events on the current schedule that are
awaiting restart, executing, or completed:
K=REC

Chapter 5. Modifying the Current Schedule 5-17

5.1 Scheduled Event Display Panel

5.1.11 Reset/Update and Display Entire Schedule (RALL) Command

This command displays all events on the current schedule and updates
information on the display.

For example, suppose you enter the RALL command from a Scheduled Event
Display panel showing only events with a JCL dependency code. The RALL
command displays a Scheduled Event Display panel showing updated
information for all events on the current schedule, not just those with a JCL
dependency code.

This command must be issued as a stand-alone command: it cannot be part of

a string of input commands (see 1.12.2, “Using Strings of Search Keys”).

Syntax: The syntax of the Reset/update and display entire schedule (RALL)
command is as follows:

RALL
──RALL────────────────────────────────────────────────────────

5-18 Operator Guide

 5.1 Scheduled Event Display Panel

5.1.12 Continuous Schedule Display (@INT) Command

This command continuously updates the information on the Scheduled Event
Display panel.

This command can be issued only after the RALL command. It is not valid at
any other time.

The keyboard is locked while this command is in effect. Depending on the

type of terminal you have, you can press either the PA1 or ATTN key to
terminate the update session and wait for the panel to reappear.

Syntax: The syntax of the Continuous Schedule Display (@INT) command is

as follows:

@INT
──@INT──┬───────────┬─────────────────────────────────────────
│ ┌─5──┐ │
└─=─┴─nn─┴──┘

Descriptions of Command Elements: Following are descriptions of the

elements of the @INT command:

Element Description
@INT Required command word.
nn Use nn to set an interval time that differs from the
default time. The default time is five seconds.

Chapter 5. Modifying the Current Schedule 5-19

5.1 Scheduled Event Display Panel

5.1.13 Remove Location (REMLOC=) Command

Use this command to suppress events for a specified location from being
displayed on the Scheduled Event Display. Events for that location will not
appear on subsequent displays until you add the location using the ADDLOC
command (for more information on the add location (ADDLOC) command, see
5.1.3, “Add Location (ADDLOC=) Command”).

If you use the TRACX26 user exit, you cannot use REMLOC=nnn to remove
locations.

This command must be issued as a stand-alone command: it cannot be part of

a string of input commands (see 1.12.2, “Using Strings of Search Keys”).

Syntax: The syntax of the REMove LOCation command is as follows:

REMLOC=
──REMLOC=nnn──────────────────────────────────────────────────

Descriptions of Command Elements: Following are descriptions of the

elements of the REMLOC command:

Element Description
REMLOC= Required command word.
nnn Required variable. Replace nnn with the location ID
(three-digit number, 000-254) of the events you want to
remove from the Scheduled Event Display.

Example: The following command suppresses events for location 3 from

being displayed on Scheduled Event Displays:
REMLOC=3

5-20 Operator Guide

 5.1 Scheduled Event Display Panel

5.1.14 Process Period Search (PP=) Command

Enter this command to display events scheduled for a specific process period.

This command can be part of a string of input commands (see the search
1.12.2, “Using Strings of Search Keys”). You can only use one process period
search command for each string.

Syntax: The syntax of the Process Period search command is as follows:

PP=
──PP=procprd──────────────────────────────────────────────────

Descriptions of Command Elements: Following are descriptions of the

elements of the Process Period search command:

Element Description
PP= Required command word.
procprd Required variable. Replace procprd with the process
period of the events you want to display.

Examples: The following command displays events that were scheduled with
the process period WORKDAYS:
PP=WORKDAYS

The following command displays events that were scheduled with the process
period TUESDAY:
PP=TUESDAY

Chapter 5. Modifying the Current Schedule 5-21

5.1 Scheduled Event Display Panel

5.1.15 Shift Search (SHIFT) Command

Enter this command to display events with target times during the shift you
specify in the command. If you have not set a time range for shift displays in
the User Options panel, the entire schedule is displayed (see 1.15.1, “User
Options Panel”).

If this command is used in a string of input commands, it must be specified

last in the string (see 1.12.2, “Using Strings of Search Keys”).

The SHIFT and T primary commands are mutually exclusive.

Syntax: The syntax of the SHIFT search command is as follows:

SHIFT
──┬─SHIFT1─┬──────────────────────────────────────────────────
├─SHIFT2─┤
└─SHIFT3─┘

Syntax Rules: The following rules apply to the syntax of the SHIFT search
command:
■ Use only one of the required parameters.
■ No space or character can separate the required parameter from SHIFT.

Descriptions of Command Elements: Following are descriptions of the

elements of the SHIFT search command:

Element Description
SHIFT Required command word.
1 Displays events with target times falling during shift 1.
2 Displays events with target times falling during shift 2.
3 Displays events with target times falling during shift 3.

Example: The following command displays all events on the current

schedule with location 001 with a target time that occurs during shift 2 (as
defined on the User Options panel):
L=1,SHIFT2

5-22 Operator Guide

 5.1 Scheduled Event Display Panel

5.1.16 Time Search (T=) Command

Use this command to display events with target times during a specified time
period. You can specify either a single hour or a time range.

This command can be part of a string of input commands (see 1.12.2, “Using
Strings of Search Keys”), however, you can only use one time search command
for each string.

The T and SHIFT primary commands are mutually exclusive.

Syntax: The syntax of the Time search command is as follows:

T=
──T=hh─┬─────────┬────────────────────────────────────────────
└─mm-hhmm─┘

Descriptions of Command Elements: Following are descriptions of the

elements of the Time search command:

Element Description
T= Required command word.
hh Required variable. Replace hh with a two-digit number
specifying the hour that begins the desired time period.
Acceptable values are 00 through 23 (however, you
cannot enter the command T=00; instead, enter
T=0001-0059 to display events scheduled between
midnight and 1 AM). If you do not specify mm-hhmm
(see below), the events displayed have target times
during the hour specified by hh (hh00-hh59).
mm-hhmm Optional variable. You replace these variables as
follows:
Replace the first mm with a two-digit number (00-59)
specifying the minute you want to begin the desired
time period.
Replace hhmm with the time you want to end the
desired time period.

Examples: The following command displays all events with target times from
12:00 PM to 12:59 PM:
T=12

Chapter 5. Modifying the Current Schedule 5-23

5.1 Scheduled Event Display Panel

The following command displays all events with target times from 1:23 AM to
4:11 AM:
T=123-411

5.1.17 Description of the Scheduled Event Display Panel

The panel below shows a sample Scheduled Event Display panel. Field
descriptions follow.

 CA-Jobtrac Scheduled Event Display ROW 1 TO 18 OF 21


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Event ----Target----Successor Dep Current CMD= RALL
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ----------------------------------------
ACAPHIST 16:36  12/18 M WAITING DEPENDENCIES LATE
ACAPD 1:5 12/17 ACGL25 P WAITING DEPENDENCIES LATE
ACAP1 AS-AP 1/23 J WAITING RSTRT J 5643 LATE
ACAPD 1:3 12/17 ACAPD M WAITING DEPENDENCIES LATE
ACAP1D 1:5  12/17 ACAP15D M WAITING DEPENDENCIES LATE
ACAP11R 1:4  12/18 ACAPD J WAITING DEPENDENCIES LATE
ACAP12R 1:4  12/18 ACAPD J WAITING DEPENDENCIES LATE
ACAP15D 1:5  1/21 ACGL2D J WAITING DEPENDENCIES LATE
ACAP15D 1:5  12/17 ACGL2D PD WAITING DEPENDENCIES LATE
ACAP35R 1:4  12/18 ACAPD J WAITING DEPENDENCIES LATE
ACAR4 1:3  1/21 ACAR43 P WAITING DEPENDENCIES LATE
ACAR4 15:6 11/1 M WAITING DEPENDENCIES LATE
ACAR4 1:3  12/17 ACAR43 PM WAITING DEPENDENCIES LATE
ACAR41 1:5  1/21 ACGL21R P WAITING DEPENDENCIES LATE
ACAR41 1:5  12/17 ACGL21R PM WAITING DEPENDENCIES LATE
ACCN21M 1:3  1/21 P WAITING DEPENDENCIES LATE
 
COMMAND: Lets you enter commands to display desired information or to
perform some function. See 1.12.1, “Using the COMMAND Field” for the
procedure for using this field. See the search keys and command information
in the Reference Summary for details of each command.

Current Date and Time: (The fields near the upper-right corner.) Displays
the current system date and time.

CMD=: Indicates the display command last entered in the COMMAND field.

Date=: Indicates the DATE parameter used to create the current display. For
example, Date=ALL indicates that all events on the current schedule are
displayed, regardless of the date for which they are scheduled. DATE=12/06
indicates that only events scheduled for 12/06 are displayed.

Event Name: Shows the name of the event on the current schedule. All
information on the same row applies to that event. The Event Name field
contains one of the following entries:

5-24 Operator Guide

 5.1 Scheduled Event Display Panel

Entry Explanation
jobname Denotes a jobtype of event on the current schedule.
djobname Denotes a dummy jobtype of event on the current
schedule, where djobname is the name of an event that
has no JCL and terminates as soon as it starts with a
return code of zero.
imod Denotes a REXX IMOD event on the current schedule,
where imod is the name of the REXX IMOD. See the
Extended Scheduling Services Guide for information about
IMODs.
0schdnm Denotes a schedule on the current schedule, where
schdnm is the name of a schedule member in your SCL
library.
0ARCHIVE Denotes the ARCHIVE dynamic task on the current
schedule.
0SYSARCH Denotes the SYSARCH dynamic task on the current
schedule.
0JOBARCH Denotes the JOBARCH dynamic task on the current
schedule.

Target Time and *: Indicates the target time for the event. The target time is
the time at which the event will be flagged LATE on the Scheduled Event
Display panel if the event has not been submitted. The TIme field entry is in
the form hhmm, where hh is a two-digit number denoting the hour of the day
(01-23) and mm is a two-digit number denoting the minute of the hour (01-59).

The field with the heading * (between the Time field and the Date field)
indicates the function of the Time field entry (see below).

If the * field Then . . .

contains . . .
blank The Time field entry indicates both the target and the
start time for the event.
* The Time field entry indicates the target time for the
event. The actual start time may be different. Check the
Scheduled Event Detail panel to determine the start time
(for more information, see 5.2, “Scheduled Event Detail
Panel”).

Chapter 5. Modifying the Current Schedule 5-25

5.1 Scheduled Event Display Panel

If the * field Then . . .

contains . . .
I The event is scheduled to run at intervals, starting at the
time shown in the Time field. Check the Scheduled
Event Detail panel to determine the length of the interval
and whether the event is set to run synchronously (at
exact intervals starting at the target time).

Target Date: Shows the date for which submission of the event is scheduled.
The date is in the format mmdd, where mm is a two-digit number denoting the
month of the year (01-12) and dd is a two-digit number denoting the day of the
month (01-31).

Successor Event(s): Shows a successor to the event (if any). If an * (asterisk)

appears in the last position of this field, more than one successor event is
defined. To view all successors (and their version numbers and current status),
you must view the Scheduled Event Detail panel (for more information on the
Scheduled Event Detail panel, see 5.2, “Scheduled Event Detail Panel”).

Dep Codes: Indicates execution dependencies (if any) that must be satisfied
before the event can be submitted. The following codes may appear:

Table 5-1 (Page 1 of 4). Execution Dependency Codes

Code Description
A Abend bypass. This is not an execution dependency, but a
release of dependencies for successors. If an event with this code
abends, the predecessor dependency (code P) is removed from
successors to the event. For this application, COND CODE and
JCL errors are not considered abends.
You can assign this code when using SCL to schedule the event
or after the event is added to the current schedule.
Events that have exceeded their abort time are assigned an A
dependency code.
D Data set required dependency. One or more data sets must be
supplied before the event can execute. The number of data sets
required is shown in the DSN Count field of the Scheduled
Event Detail panel. Before the event can be submitted, the DSN
Count must be reduced to zero, which removes the D code. The
DSN Count can be reduced by the ADR (Automatic Dataset
Recognition) table (when defined data sets are created or
updated).
You can assign this code when using SCL to schedule the event
or after the event is added to the current schedule.

5-26 Operator Guide

 5.1 Scheduled Event Display Panel

Table 5-1 (Page 2 of 4). Execution Dependency Codes

Code Description
E Edit JCL dependency. This code prevents submission of the
event until its JCL is edited and saved. The E code must be
removed manually after the JCL is edited (for more information
on removing an edit JCL dependency code, see 5.9, “JCL
Handling”).
You can assign this code when using SCL to schedule the event
or after the event is added to the current schedule.
H Automatic hold dependency. This code indicates that the event
is being held from submission due to some type of threshold
crossover. The Current Status field on the Scheduled Event
Display panel may indicate the reason for the hold. The target
date may have crossed over to a holiday or the abort time
threshold may have been exceeded. The event cannot be
submitted until the H code is manually removed.
This code is assigned by CA-Jobtrac.
I Environmental dependencies exist. All environmental
dependencies for the event must complete normally before the
event is submitted.
CA-Jobtrac assigns this code when the event is added to the
current schedule if the event has an environmental dependency
defined. You can only assign environmental dependencies when
using SCL to schedule the event. You can remove or add the I
dependency code only if the event had environmental
dependencies when it was added to the current schedule.
J JCL required dependency. JCL must be supplied or altered
before the event can execute. Before the event can be submitted,
this code must be manually removed or JCL must be externally
submitted using the AUTO-SCHD feature (see 4.7, “The
AUTO-SCHD Feature”).
You can assign this code (when using SCL to schedule the event
or after the event is on the current schedule), or CA-Jobtrac can
assign it. If it is assigned by CA-Jobtrac, it notes that the JCL
was not present at submit time, and the message TRAC014E
may accompany it. Any CA-Jobtrac-controlled events submitted
with a TYPRUN=SCAN parameter are also assigned the J code.

Chapter 5. Modifying the Current Schedule 5-27

5.1 Scheduled Event Display Panel

Table 5-1 (Page 3 of 4). Execution Dependency Codes

Code Description
M Manual release dependency. You must manually remove this
dependency before the event can be submitted automatically by
CA-Jobtrac. A manual activity checklist may require further
action (for more information on the Manual Action Detail panel,
see 5.5, “Manual Action Detail Panel”). See the Schedule Creation
Guide for information about including records in an event's
documentation member to specify manual actions to be
displayed on a Manual Action Detail panel.
You can assign this code to an event (when using SCL to
schedule the event or after the event is added to the current
schedule) or CA-Jobtrac can assign the code (when you add an
event to the current schedule using the ADD command or when
an event's target date crosses over to a holiday). A manual
dependency is automatically added to an event if the event's
target time has passed and the *LATE* indicator is present.
O Output release dependency. This dependency does not affect
submission of the event. Instead, it requires verification of the
event's output (balance reports, and so on) after the event
completes. No CA-Jobtrac-controlled successors to the event can
run until the O code is manually removed.
You can assign this code (when using SCL to schedule the event
or after the event is on the current schedule), or CA-Jobtrac can
assign it. CA-Jobtrac assigns this code to an event with
successors if its JCL sysout cannot be found, if the maximum
condition code is exceeded by a job step or a dynamic schedule
update, or if a catalog error is found on the event's sysout.
P Predecessor event dependency. All predecessor events must
complete normally without abend and without exceeding the
maximum allowable step condition code before the event can be
submitted.
You can assign this code (when using SCL to schedule the event
or after the event is added to the current schedule), or
CA-Jobtrac can assign the code (if the event is defined to be a
successor to other events on the current schedule).

5-28 Operator Guide

 5.1 Scheduled Event Display Panel

Table 5-1 (Page 4 of 4). Execution Dependency Codes

Code Description
Q Queued release dependency. This dependency indicates that the
event's JCL is to be submitted outside of CA-Jobtrac. Once JCL is
submitted, the event is held in the Job Entry Subsystem queue
and released automatically by CA-Jobtrac when dependencies
are met. An AUTO-SCHD event with Q in column 70 of the first
event record can be submitted to satisfy this dependency (see
4.7, “The AUTO-SCHD Feature”). You can also assign an
optional event execution class to be automatically held and
queued for release.
The Q code is not valid for REXX IMOD or dummy jobs.
R Resource dependency. This dependency indicates that
user-defined resource conditions must be satisfied before the
event can be submitted. The conditions that must be met are
defined in the PPOPTION member RESOURCE (see the Extended
Scheduling Services Guide for information about managing generic
group resources).
This code is assigned by CA-Jobtrac if event submission is
delayed because resources are unavailable.
X Mutual exclusion dependency. This code indicates that the event
is defined to be mutually exclusive with an event that is
currently executing (see the Extended Scheduling Services Guide for
information about scheduling mutually exclusive events). Once
the executing event completes, the X code is removed and the
waiting event is eligible for submission. You can also remove the
X code manually, thereby removing the exclusion rule.
CA-Jobtrac assigns this code and issues the message TRAC089I
when an event defined as mutually exclusive is found executing.
*AUTO This dependency indicates that an event's JCL was submitted
outside of CA-Jobtrac, and CA-Jobtrac now is tracking the event.
? View documentation dependency. This dependency prevents
submission of an event until its documentation is viewed. The ?
code must be removed manually after the documentation is
viewed (for more information on removing a view
documentation dependency code, see 5.12, “Removing a View
Documentation Dependency Code”).
You can assign this code when scheduling an event using SCL
or after the event is added to the current schedule.

Current Status: Provides an abbreviated summary of the event's current

status. The following entries may appear:

Chapter 5. Modifying the Current Schedule 5-29

5.1 Scheduled Event Display Panel

Entry Description
ABENDED=xnnn The event ended abnormally with abend code
xnnn. This entry is accompanied by the event
number assigned by JES (Job Entry Subsystem) or
the word IMOD if the event is a REXX IMOD and
the time and date at which the abend occurred.
ABENDED=xnnn, A step of the event ended abnormally with abend
(EXECUTING) code xnnn, but the event is still executing. This
entry is accompanied by the event number
assigned by JES (Job Entry Subsystem).
ARCHIVAL The ARCHIVE (or JOBARCH, or SYSARCH) task
COMPLETE has completed execution. This entry is
accompanied by the time and date at which the
task completed. If an * (asterisk) appears in the last
position of the status field, CA-Jobtrac is waiting to
complete a function (usually sysout capture) for
this task.
ARCHIVAL IN The ARCHIVE task is executing but has not
PROGRESS completed.
CATALOG ERROR A catalog error occurred for the event. The number
assigned to the event and the time and date at
which execution stopped accompany this entry.
COMPLETED The event has completed execution. This entry is
accompanied by the number assigned to the event
or the word IMOD if the event is a REXX IMOD
and the time and date at which the event
completed. If an * (asterisk) appears in the last
position of the status field, CA-Jobtrac is waiting to
complete a function for this event, usually sysout
capture.
COND CODE CHK Some job step completed with a condition code
exceeding the maximum allowed value. The
number assigned to the event or the word IMOD if
the event is a REXX IMOD and the time and date
at which execution stopped accompany this entry.
EXECUTING The event has been submitted but has not
completed. This entry is accompanied by the
number assigned to the job by JES or the word
IMOD if the event is a REXX IMOD and the name
of the system on which the event is running.
Njobnumber The event is a remotely-submitted NJE job.
jobnumber is the JES job number.

5-30 Operator Guide

 5.1 Scheduled Event Display Panel

Entry Description
N-status-nodename, The event is an NJE job. status is either AWT
SYS=ssss (Awaiting Execution) or EXE (Executing). nodename
is the remote JES node name. ssss is the submitting
system's SMF system ID.
OUTPUT RELEASE The event has completed execution, but an output
release dependency code (O) is present. You must
check the event's output and remove the output
release dependency manually. The JES job number
or the word IMOD if the event is a REXX IMOD
and the time and date at which the event
completed are shown.
PURGED BY: userid The event was manually purged by the user userid.
The time and date at which the event was purged
are indicated. The userid may also specify an event
name if the purge is the result of a batch
GJTRABTR utility purge.
SCHEDULE UPDATED The schedule has completed execution. This entry
is accompanied by the time and date at which the
task completed. If an * (asterisk) appears in the last
position of the status field, CA-Jobtrac is waiting to
complete a function (usually sysout capture) for
this task.
SCHEDULE UPDATE The schedule is executing but has not completed.
IN PROGRESS
TIME ABORT PURGE The event's abort time threshold was exceeded and
the event was purged from the schedule before
submission. The event record will remain on the
current schedule until it is archived. The time and
date at which the event was purged is indicated.
WAITING The event (or task) cannot be submitted because
DEPENDENCIES one or more execution dependencies remain. A
*LATE* indicator accompanies this entry if the
event's target time has passed.
WAITING EXEC The event has been submitted and can begin
execution when an initiator is provided. The JES
job number or the word IMOD if the event is a
REXX IMOD accompanies this entry and
SUBMITTED AT hhmm indicates the time the event
was submitted.
WAITING RERUN The event abended and was automatically
rescheduled by CA-Jobtrac. The JES job number or
the word IMOD if the event is a REXX IMOD and
a *LATE* indicator accompany this entry.

Chapter 5. Modifying the Current Schedule 5-31

5.1 Scheduled Event Display Panel

Entry Description
WAITING SCHED Execution dependencies of a schedule or dynamic
UPDATE task have been met. If a *LATE* indicator appears,
the schedule's target time has passed, and the
schedule can be executed.
WAITING START All execution dependencies have been satisfied and
TIME the event can be submitted at its scheduled start
time/date.
WAITING STEP The event can be submitted after its JCL is edited
RESTART and the J dependency code is removed. A READY
indicator accompanies this entry.
WAITING All execution dependencies have been satisfied and
SUBMISSION the target time has arrived. If the event's start time
has also arrived, the event is ready to be submitted,
and a READY indicator is shown. If the start time
has not arrived, the event cannot be submitted, and
a *LATE* indicator is shown.
WAITING START The event was scheduled with an asterisk (*) in the
THRESHOLD time field. The threshold time is taken from the last
event run in the history file. The threshold time is
between the last start time (set 15 to 20 minutes
before the historical start time) and the target time
(set 15 to 20 minutes after the historical start time).
WAITING Either CA-Jobtrac is on hold or an archive is
CHECKPOINT running. Because of this situation, there is an
ARCHIVAL enqueue on the checkpoint data set. The event
cannot run until the archive finishes.
WAITING RESTART The event is waiting restart through a rerun/restart
package.

5-32 Operator Guide

 5.1 Scheduled Event Display Panel

5.1.18 Using the Scheduled Event Display to Modify the Current

Schedule
You can edit some fields on the Scheduled Event Display panel to make
changes to events on the panel (if you are authorized to do so). Any changes
you make affect only the version of the event on the current schedule: no
changes are made to permanent schedules.

Fields You Can Modify: Fields that you can modify are highlighted on the
display. They are:
■ Target Time
■ Threshold field (heading *)
■ Target Date
■ Dep Codes

Changing the Threshold Field: If you delete an asterisk from an event's

threshold field (heading *, between Time and Date fields), the time shown in
the Time field becomes both target and start time for the event. If you add an
S to this field, the time shown in the Time field becomes the target time only,
and the start time is changed to ASAP.

Changing the I Dependency Code: You can remove or add the I

dependency code. You can only add the dependency if the event had an
environmental dependency when it was added to the current schedule. You
cannot add an I code to an event if it did not originally have an environmental
dependency.

Editing Fields on the Scheduled Event Display: Follow the steps below to
change the current schedule using the Scheduled Event Display panel.
1. Position the cursor in the field you want to change on the Scheduled Event
Display panel.
2. Type over the existing entry so that the entry you want appears. If you
want to make additional changes, repeat steps 1 and 2.
3. Press Enter to save the changes. The message eventname SAVED appears.

Example: Suppose you want to remove the manual dependency code from
PRODJOB1. The first step is to display a Scheduled Event Display panel
listing PRODJOB1. The panel below was displayed by entering the event name
prefix PROD at the COMMAND field.

Chapter 5. Modifying the Current Schedule 5-33

5.1 Scheduled Event Display Panel

 CA-Jobtrac Scheduled Event Display ROW 1 TO 7 OF 7


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Event ----Target----Successor Dep Current CMD= PROD
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ----------------------------------------
PRODJOB1 1: 1/3 PRODJOB2 M WAITING DEPENDENCIES LATE
PRODJOB2 1:3  1/3 P WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 TESTJOB1 P WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 TESTJOB1 M WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 P WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 TESTJOB1 P WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 TESTJOB1 P WAITING DEPENDENCIES LATE
 BOTTOM OF DATA 
 
To remove the manual dependency (code M) from PRODJOB1, delete the M
from the Dep Codes field (type a blank over it, or use the delete key), as
shown in the panel below.

 CA-Jobtrac Scheduled Event Display ROW 1 TO 7 OF 7


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Event ----Target----Successor Dep Current CMD= PROD
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ----------------------------------------
PRODJOB1 1: 1/3 PRODJOB2 WAITING DEPENDENCIES LATE
PRODJOB2 1:3  1/3 P WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 TESTJOB1 P WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 TESTJOB1 M WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 P WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 TESTJOB1 P WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 TESTJOB1 P WAITING DEPENDENCIES LATE
 BOTTOM OF DATA 
 
When you press Enter, the change is saved and the message PRODJOB1
SAVED appears, as shown below.

You could also remove the dependency using the A line command.

 CA-Jobtrac Scheduled Event Display PRODJOB1 SAVED


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Event ----Target----Successor Dep Current CMD= PROD
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ----------------------------------------
PRODJOB1 1: 1/3 PRODJOB2 WAITING DEPENDENCIES LATE
PRODJOB2 1:3  1/3 P WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 TESTJOB1 P WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 TESTJOB1 M WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 P WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 TESTJOB1 P WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 TESTJOB1 P WAITING DEPENDENCIES LATE
 BOTTOM OF DATA 
 

5-34 Operator Guide

 5.2 Scheduled Event Detail Panel

5.2 Scheduled Event Detail Panel

The Scheduled Event Detail panel provides detailed information about an
event on the current schedule that is awaiting submission or rerun.
Information such as the event's version number, process period, and
predecessor event count can be found on this panel.

You can change various scheduling parameters for an event using the
Scheduled Event Detail panel.

5.2.1 Displaying a Scheduled Event Detail Panel

Use either of the following methods to display a Scheduled Event Detail panel:
■ Enter the Select for detail display (S) command at the COMMAND field of
any CA-Jobtrac display (for more information, see 5.2.2, “Select for Detail
Display (S) Command”).
■ Use the S line command on an event on a Scheduled Event Display (see
1.12.3, “Using Line Commands”).

5.2.2 Select for Detail Display (S) Command

This command displays a detail panel for the specified event. The display is a
Scheduled Event Detail panel, an Event Execution Detail panel if the event has
been submitted, or an NJE Execution Detail panel if the job was remotely
submitted.

This command must be issued as a stand-alone command: it cannot be part of

a string of input commands (see 1.12.2, “Using Strings of Search Keys”).

Syntax: The syntax of the Select for detail display (S) command is as follows:

S
──S ──eventname───────────────────────────────────────────────

Chapter 5. Modifying the Current Schedule 5-35

5.2 Scheduled Event Detail Panel

Descriptions of Command Elements: Following are descriptions of the

elements of the Select for detail display (S) command:

Element Description
S Required command word.
eventname Required variable. Replace eventname with the name of
the event for which you want to display a detail panel. If
the event has not yet been submitted, a Scheduled Event
Detail panel is displayed. If the event has been
submitted, an Event Execution Detail panel is displayed.
An NJE Execution Detail panel is displayed if the job
was remotely submitted.

Example: The following command invokes a detail display for PRODJOB1. If

PRODJOB1 has not yet been submitted, a Scheduled Event Detail panel is
displayed. If PRODJOB1 has been submitted, an Event Execution Detail panel
is displayed. If PRODJOB1 has been remotely submitted, an NJE Execution
Detail panel is displayed.
S PRODJOB1

5.2.3 Description of the Scheduled Event Detail Panel

The panel below shows a sample Scheduled Event Detail panel. Field
descriptions follow.

 CA-Jobtrac Scheduled Event Detail Row 1 to 4 of 2


COMMAND ===> SCROLL ===> CSR
yy/mm/dd hh:mm
Event Name: JOBQ Status : LATE - AWAITING DEPENDENCIES
Version : 92.1 Proc Per. : RQ-USERO1 LOAD DATE ===> N/A

Start Time ===> 14:23 Start Date ===> 9/2 Interval ===> (HHMM)
Target Time ===> 14:23 Target Date ===> 9/2 Range ===> -
Abort Time ===> Abort Date ===> Type ===> (A,E,S)

JCL source ===> P (P,T) Dep. Codes ===> M Event Type ===> J
Prod Member ===> JOBQ Maximum CC ===>  Bus. Grp ===> USERO1
Temp Member ===> DSN Count ===>  Event Source : PAYROLL
Location ===>  Manual Actions : 2 Pred Count ===> 
Node Name ===> USER1 Schedule Environment ===> NO
Resource Rq ===> A BB C DD EE FF G H

Preds Version Status Successr Version Status Env. Dep.

-------- --------- ------------ --------- --------- ---------- ----------
-------- --------- TESTWFC1
-------- ---------
-------- ---------
-------- ---------
-------- ---------
-------- ---------
 

5-36 Operator Guide

 5.2 Scheduled Event Detail Panel

COMMAND: Lets you enter commands to display desired information or to

perform some function. See 1.12.1, “Using the COMMAND Field” for the
procedure for using this field. See the search keys and command information
in the Reference Summary for details of each command.

Event Name: Shows the name of the event on the current schedule. All
information on the panel pertains to the entry in this field. For more
information on Event Name, see “Event Name” for descriptions of possible
entries in this field.

Status: Provides an abbreviated summary of the event's current status. The

following entries are possible.
AWAITING DEPENDENCIES
AWAITING RERUN
AWAITING RESTART
AWAITING RE-SUBMISSION
AWAITING START TIME
AWAITING SUBMISSION
LATE - AWAITING DEPENDENCIES
LATE - AWAITING RERUN
LATE - AWAITING RESTART
LATE - AWAITING SUBMISSION

This field is informational only and cannot be modified.

Version: Uses the form

mmdd.vvvv

The first four digits indicate the date the event was added to the current
schedule (if CA-Jobtrac assigned the version number) or a user-assigned date.
The last four digits indicate the event's version number. The number may be
user-assigned or CA-Jobtrac-assigned. If CA-Jobtrac assigned the number, it
indicates this version's place in a series of events of the same name added to
the current schedule on the date specified.

For example, suppose TESTJOB1 has a CA-Jobtrac-assigned Version field entry

of 1202.0002. The first four digits show that the event was added to the current
schedule on 12/02. The last four digits show that this event was the second
version of TESTJOB1 added to the current schedule on 12/02.

This field is informational only and cannot be modified.

Chapter 5. Modifying the Current Schedule 5-37

5.2 Scheduled Event Detail Panel

Proc Per.: Indicates the process period for the event. See the process period
tables in the Reference Summary for descriptions of process periods (any of
which could appear as entries in the Proc Per. field). In addition to the
process periods, the following entries may appear in this field.

Element Description
AUTO-SCHD The event was added to the current schedule using the
AUTO-SCHD utility.
RQ-userid The event was added to the current schedule by the user
userid through the ADD command, RUN command, or
Event/Jobstream Addition panel.
DSN-TRIGGER The event was added to the current schedule using the
Automatic Dataset Recognition facility.
MSG-TRIGGER The event was added to the current schedule using the
Automatic Message Recognition facility.
RRUN-nnnnn The event completed abnormally. Action by operator is
required.
RSTR-nnnnn The event completed abnormally and was restaged with
the 'T' line command.

This field is informational only and cannot be modified.

Load Date: Indicates the date (format: mm/dd/yyyy) on which the event
was loaded. For example, if the TODAY statement was used in an SCL
member to schedule an event for a certain day (being different from today's
date), then the Load Date field reflects the actual day of the loading of the
event. If no loading date is available, the panel displays N/A.

5-38 Operator Guide

 5.2 Scheduled Event Detail Panel

Time and Date: Provides the following scheduled times:

Element Description
Start Indicates the time and date at which the event is first
eligible for submission if all other dependencies are
satisfied. If you erase the value in the Start Time field or
leave the field blank, the field will display ASAP when
you save your changes.
Target Indicates the scheduled time and date at which a LATE
indicator would be set for the event if it has not been
submitted. The target time is used for all schedule
adherence reporting. If you erase the value in the Target
Time field or leave the field blank, the field will display
the value of the Start Time field when you save your
changes.
Abort Indicates the time and date at which the event will be
purged from the schedule if dependencies have not been
met.

Interval: Indicates the intervals at which the event will be rescheduled. The
entry is in the form hhmm (hh = hours and mm = minutes). For example, an
event scheduled to run every two hours and 30 minutes would have the entry
0230. The event will be rescheduled with a new start and target time when it
completes successfully.

Range: Indicates the time period during which the event was scheduled to
run at the intervals indicated in the Interval field. The entry is in the form
hhmm-hhmm (the first hhmm indicates the start of the time period, the last
hhmm indicates the end of the time period). For example, the entry 0600-1000
indicates that the event will be rescheduled to run at the interval shown in the
Interval field from 6:00 AM to 10:00 AM.

You cannot modify the start value of the Range field. The end value of the
Range field can either be hhmm or blank. A blank entry indicates that the event
will be rescheduled continuously.

Type: Indicates from what time to calculate the target and start time for the
next submission of this event based on the interval. Possible entries are:

Element Description
A Start the calculation at the time the event actually starts
running.
E Start the calculation at the time the event successfully
ended.

Chapter 5. Modifying the Current Schedule 5-39

5.2 Scheduled Event Detail Panel

Element Description
S Start the calculation at the time defined in the Target
Time field.

JCL source: Indicates the source of JCL. If the entry in this field is P, the
event's JCL is submitted from the JCL library. If the entry is T, the event's JCL
is submitted from the temporary-use JCL library. This field is valid only for
jobtype events.

Dep. Codes: Indicates execution dependencies that must be satisfied before

the event can be submitted. For more information on Dep. Codes, see “Dep
Codes” for descriptions of possible entries in this field. If the field contains an
I code, see 3.5, “Environmental Dependencies Panel” for information about
displaying environmental dependency information.

Event Type: Indicates the type of event this is. Possible entries are:

Element Description
A The event is an AS/400 CLP using the CALL command.
C The event defines a command to be executed at a
particular remote node.
D The event is a dummy job.
I The event is a REXX IMOD.
J The event is a batch job.
S The event is a schedule.
T The event is a 0ARCHIVE, 0SYSARCH, or 0JOBARCH
task.
U The event invokes a UNIX Korn shell script using the
UNIX ksh command.

You cannot change an event's type to or from S or T.

5-40 Operator Guide

 5.2 Scheduled Event Detail Panel

Member Name

Prod Member Temp Member

Denotes the name of the member that Denotes the name of the member that
contains the production JCL for this contains a temporary copy of the JCL
event. By default, CA-Jobtrac runs that is to be used for this event only.
the JCL member that has the same Subsequent scheduling of events with
name as the name specified in the the same name will use the
Event Name field. production JCL. This field is
significant only when the JCL source
field is T. (For more information
about JCL handling, see 5.9, “JCL
Handling”).

These fields are valid only for jobtype events.

Maximum CC: Indicates the maximum condition code value for all steps in
the event. CA-Jobtrac monitors the event during execution and imposes an
output release dependency (code O) on the event if any step exceeds the
maximum condition code. CA-Jobtrac does not stop execution of the event if
the maximum condition code value is exceeded. If the entry in the Maximum
CC field is N/A, CA-Jobtrac does not monitor condition codes for this event.

Bus. Grp.: Indicates the business group with which the event is associated.

DSN Count: Indicates the number of data sets that must be created or
updated and then closed before this event can be submitted. The required data
sets are defined in storage-resident tables (see the Extended Scheduling Services
Guide for information about Automatic Dataset Recognition). As each data set
requirement is met, the count is reduced by one. When the count reaches 000,
the data set required dependency code (D) is removed and the event will be
submitted.

Event Source: Provides the source of the event. The field codes are as
follows:
Blank Blank indicates the TSO ADD or NEW commands added the job,
or the job was added prior to the application of PTFs.
0ccccccc Zero-prefixed name indicates an internal schedule load added the
job.
cccccccc Nonzero first character indicates a batch schedule load job or TSO
ADD or NEW command added the job.

Location: Indicates the three-digit location ID code assigned to the event.

Determines which JCL, SCL, and documentation libraries are used.

Chapter 5. Modifying the Current Schedule 5-41

5.2 Scheduled Event Detail Panel

Manual Actions : x: Indicates the number (if any) of manual actions

required. If this field appears immediately following the Location field and
below the DSN Count field, manual actions are listed on a Manual Action
Detail panel for this event (see 5.5.4, “Using the Manual Action Detail Panel to
Remove a Manual Dependency Code”).

Pred Count: Indicates the number of predecessor events that must complete
successfully before this event can be submitted. As each predecessor completes,
the count is reduced by one. When the count reaches 000, the predecessor
dependency code (P) is removed and the event can be submitted.

GSS Node: The GSS Node field indicates the GSS node name (up to 16
characters) of the executing node for the named event. An entry in this field
indicates that this event is a remote event.

Resource Rq: Indicates user-defined resource conditions that must be met

before the event can be submitted. The codes are defined in the PPOPTION
member RESOURCE (see the Extended Scheduling Services Guide for information
about managing generic group resources).

5-42 Operator Guide

 5.2 Scheduled Event Detail Panel

Predecessor Fields: Indicates the following information about predecessors

to the event. These fields can be scrolled to view additional predecessors (if
any) using the Up and Down commands.

Element Description
Preds Indicates the event name of the predecessor.
Version Indicates the predecessor event's version (for more
information on Version, see “Version”).
Status Provides an abbreviated summary of the predecessor
event's current status. If the message (NOT SCHD)
appears, the predecessor event is not on the current
schedule. If the message (ARCHIVED) appears, the event
has been archived to the history file. For more
information on the current event status, see “Status” for
other possible entries in this field.

Successor Fields: Indicates the following information about successors to the

event. These fields can be scrolled to view additional successors (if any) using
the Up and Down commands.

Element Description
Successr Indicates the event name of the successor.
Version Indicates the successor event's version (for more
information on Version, see “Version”).
Status Provides an abbreviated summary of the successor
event's current status. If the message (NOT SCHD)
appears, the successor event is not on the current
schedule. If the message (ARCHIVED) appears, the event
has been archived to the history file. For more
information on current event status, see “Status” for
other possible entries in this field.

Env. Dep.: Indicates the name of the environmental dependencies (if any)
that exist for this event. Display the Environmental Dependencies panel for
information on the dependencies (see 3.5, “Environmental Dependencies
Panel”).

Chapter 5. Modifying the Current Schedule 5-43

5.2 Scheduled Event Detail Panel

5.2.4 Using the Scheduled Event Detail Panel

You can edit some fields on the Scheduled Event Detail panel to make changes
to the event (if you are authorized to do so). Any changes that you make affect
only the version of the event on the detail panel: no permanent changes are
made to the SCL used to schedule the event.

Fields You Can Modify: Fields that you can modify are highlighted on the
display. They are:
■ Time and Date (Start, Target, and Abort)
■ Interval
■ Range
■ Interval Type
■ JCL source
■ Dep Codes
■ Event Type
■ Prod Member
■ Temp Member
■ Maximum CC
■ Bus. Grp
■ DSN Count
■ Resrce Req
■ Location
■ Pred Count
■ GSS Node
■ Preds and Predecessor Version
■ Successr and Successor Version

Changing the I Dependency Code: You can remove or add the I

dependency code. You can only add the dependency if the event had an
environmental dependency when it was added to the current schedule. You
cannot add an I code to an event if it did not originally have an environmental
dependency.

5-44 Operator Guide

 5.2 Scheduled Event Detail Panel

Procedure: Follow the steps below to change the current schedule using the
Scheduled Event Detail panel.
1. Select the event's Scheduled Event Detail panel using the S line command
next to the event's entry on the Scheduled Event Display panel.
2. Position the cursor in the field you want to change on the Scheduled Event
Detail panel.
3. Type over the existing entry so that the entry you want appears. If you
want to make additional changes, repeat steps 1 and 2.
4. Type SAVE in the COMMAND field of the Scheduled Event Detail panel
to save the changes you have made.
5. Press Enter to save the change(s).

Example: A sample current Scheduled Event Detail panel for event

PMAND004 is shown below.

 CA-Jobtrac Scheduled Event Detail ROW 1 TO 6 OF 21


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Event Name : PMAND4 Status : LATE - AWAITING DEPENDENCIES
Version : 811.1 Proc Per. : WORKDAYS LOAD DATE ===> N/A

Start Time ===> 14:5 Start Date ===> 8/13 Interval ===> (HHMM)
Target Time ===> 14:5 Target Date ===> 8/13 Range ===> -
Abort Time ===> Abort Date ===> Type ===> (A,E,S)

JCL source ===> T (P,T) Dep. Codes ===> P Event Type ===> J
Prod Member ===> PMAND4 Maximum CC ===> N/A Bus. Grp ===> PMANRUN
Temp Member ===> A211617 DSN Count ===>  Resrce Req ===>
Location ===>  Pred Count ===> 1
Node Name ===> USER1 Schedule Environment ===> NO

Preds Version Status Successr Version Status Env. Dep.

-------- --------- ----------- --------- --------- ---------- ----------
PMAND3 811.1 (NOT SCHD) PMASUCC1 9.1 (NOT SCHD)
-------- ---------
-------- ---------
 

Chapter 5. Modifying the Current Schedule 5-45

5.2 Scheduled Event Detail Panel

Suppose you want to change event PMAND004's start time to 13:30 and
change the predecessor version number to 0811.0002. As shown on the
Scheduled Event Detail panel below, you would
■ Type 13:30 over the current start time (14:05)
■ Type 0811.0002 over the current predecessor version (0811.0001)
■ Type SAVE in the COMMAND field and press Enter.

 CA-Jobtrac Scheduled Event Detail ROW 1 TO 6 OF 21


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Event Name : PMAND4 Status : LATE - AWAITING DEPENDENCIES
Version : 811.1 Proc Per. : WORKDAYS LOAD DATE ===> N/A

Start Time ===> 13:3 Start Date ===> 8/13 Interval ===> (HHMM)
Target Time ===> 14:5 Target Date ===> 8/13 Range ===> -
Abort Time ===> Abort Date ===> Type ===> (A,E,S)

JCL source ===> T (P,T) Dep. Codes ===> P Event Type ===> J
Prod Member ===> PMAND4 Maximum CC ===> N/A Bus. Grp ===> PMANRUN
Temp Member ===> A211617 DSN Count ===>  Resrce Req ===>
Location ===>  Pred Count ===> 1
Node Name ===> USER1 Schedule Environment ===> NO

Preds Version Status Successr Version Status Env. Dep.

-------- --------- ----------- --------- --------- ---------- ----------
PMAND3 811.2 (NOT SCHD) PMASUCC1 9.1 (NOT SCHD)
-------- ---------
-------- ---------
 

5-46 Operator Guide

 5.3 Scheduled Event Network Panel

5.3 Scheduled Event Network Panel

The Scheduled Event Network panel lists an event's primary predecessor and
successor event network in primary execution sequence. For example, suppose
event TESTJOB2 has one predecessor, event TESTJOB1, and one successor,
event TESTJOB3. If you display a Scheduled Event Network panel for
TESTJOB2, the resulting panel would show all three events in the following
order: TESTJOB1, TESTJOB2, TESTJOB3.

The information displayed for each event on a Scheduled Event Network panel
is the same as the information provided by a Scheduled Event Display.

You can display detailed information about a single event or perform some
action on an event using a line command or a command issued from the
COMMAND field. You can use the same commands as you use on a
Scheduled Event Display.

5.3.1 Displaying the Panel

You can use either of the following methods to display a Scheduled Event
Network panel:
■ Use the L line command on any event that has predecessors or successors
on a Scheduled Event Display (see 1.12.3, “Using Line Commands”).
■ Using the Event/Jobstream Addition panel to add related events. When
you type ENDSAVE at the COMMAND field of the Event/Jobstream
Addition panel and press Enter, you display a Scheduled Event Network
panel showing the predecessor and successor relationships of the events
you have just added to the current schedule. See 4.4, “The
Event/Jobstream Addition Panel” for more information about its use.

Chapter 5. Modifying the Current Schedule 5-47

5.3 Scheduled Event Network Panel

Description of the Scheduled Event Network Panel: The panel below

shows a sample Scheduled Event Network panel. The fields on Scheduled
Event Network panels are the same as the fields on Scheduled Event Display
panels. For more information on the Scheduled Event Display panel, see 5.1.17,
“Description of the Scheduled Event Display Panel.”

 CA-Jobtrac Scheduled Event Network ROW 1 TO 5 OF 5


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Event ----Target----Successor Dep Current CMD= D=P
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ----------------------------------------
TESTJOB1 AS-AP 1/3 TESTJOB1 M WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 TESTJOB1 P WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 TESTJOB1 P WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 TESTJOB1 P WAITING DEPENDENCIES LATE
TESTJOB1 AS-AP 1/3 P WAITING DEPENDENCIES LATE
 BOTTOM OF DATA 
 

5-48 Operator Guide

 5.3 Scheduled Event Network Panel

5.3.2 Finding and Sorting Events

The primary commands FIND and SORT are available on the Scheduled Event
Network panel to enable specific searching and sorting of the listed events.
These commands can be used with the stand-ard ISPF scrolling commands to
locate specific events.

FIND Command: The FIND primary command enables you to search the
listed events for a particular event or events.

The syntax of the FIND command is as follows:

FIND
┌─NEXT──┐
──FIND──┬──────────┬──┬───────────────┬──┼───────┼────────────
└─'string'─┘ └─'column-name'─┘ ├─ALL───┤
├─FIRST─┤
├─LAST──┤
└─PREV──┘

SORT Command: The SORT primary command allows you to sort the list in
either ascending or descending order based on the values in a specified
column.

The syntax of the SORT command is as follows:

SORT
┌─A─┐
──SORT─┬───────────────┬──┼───┼───────────────────────────────
└─'column-name'─┘ └─D─┘

Chapter 5. Modifying the Current Schedule 5-49

5.3 Scheduled Event Network Panel

Column Names: The following table equates the field names on the panel to
the column names used in the FIND and SORT commands:

Field Name Command Column Name

Event Name EVENT-NAME
Target Time TARGET-TIME
Target * TARGET-*
Target Date TARGET-DATE
Successor Event(s) SUCCESSOR-EVENT(S)
Dep Codes DEP-CODES
Current Status CURRENT-STATUS

FIND Command Syntax Rules

■ You can limit the search for a character string to a specific column by
specifying a column name after the search argument.
■ You may enclose the search argument in single or double quotes.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.

For example, the following command finds all occurrences of TESTJOB1 in the
Event Name column.
FIND TESTJOB1 EVENT-NAME ALL
■ The default FIND command is FIND {'string'} NEXT.
■ If you specify FIND {'string'} ALL, the FIND command will scan the list to
determine the number of rows that contain the character string. It will
display the results and then position the panel to the first row that
matched the search.
■ You can enter the FIND command with no parameters to repeat the
previous find.

5-50 Operator Guide

 5.3 Scheduled Event Network Panel

SORT Command Syntax Rules

■ You can specify which column to sort on by specifying a column name.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.

For example, the following command sorts on the Current Status column.
SORT CURRENT-STATUS
■ The default SORT command sorts in ascending order.
■ You can enter the SORT command without any parameters to put the list
back in its original sequence.

Chapter 5. Modifying the Current Schedule 5-51

5.4 Step Condition Code Exceptions Panel

5.4 Step Condition Code Exceptions Panel

The Step Condition Code Exceptions panel displays the condition code
parameters that have been defined for an event. CA-Jobtrac monitors the
condition codes produced when the event executes and assigns the status
COND CODE CHK if any condition code parameters are violated.

You can use the Step Condition Code Exceptions panel to:
■ View condition code parameters that have been set for an event
■ Change or remove existing condition code parameters for the event
■ Add condition code parameters for the event

5.4.1 Displaying a Step Condition Code Exceptions Panel

Use either of the following methods to display a Step Condition Code
Exceptions panel:
■ Enter the command CC at the COMMAND field of an event's Scheduled
Event Detail panel, Event Execution Detail panel, or Event History Detail
panel (for more information on the display Step Condition Code
Exceptions panel (CC) command, see 5.4.2, “Display Step Condition Code
Exceptions Panel (CC) Command”).
■ Use the C line command on an event on a Scheduled Event Display, a
Scheduled Event Network, or an Event History Display panel (see 1.12.3,
“Using Line Commands”).

The Step Condition Code Exceptions panel is a pop-up panel.

5.4.2 Display Step Condition Code Exceptions Panel (CC)

Command
You can enter this command only on a Scheduled Event Detail panel, an Event
Execution Detail panel, or an Event History Detail panel. Entering the
command displays a Step Condition Code Exceptions panel for the event on
the detail panel.

For example, suppose you are viewing a Scheduled Event Detail panel for
TESTJOB1. Entering the CC command displays a Step Condition Code
Exceptions panel for TESTJOB1.

Syntax: The syntax of the display Step Condition Code Exceptions panel
command is as follows:

CC
──CC──────────────────────────────────────────────────────────

5-52 Operator Guide

 5.4 Step Condition Code Exceptions Panel

5.4.3 Description of the Step Condition Code Exceptions Panel

The panel below shows a sample Step Condition Code Exceptions panel. Field
descriptions follow.

 --------------------------- Step Condition Code Exceptions -------------------- 

COMMAND ===> ROW 1 TO 12 OF 12

Max CC for TESTJOB1 ===> 

Step Relation Condition
Number (EQ,LT,GT,LE) Code
-------- ------------- ---------
4 LT 4
14 LE 8
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
 BOTTOM OF DATA 
 
COMMAND: Lets you enter commands to display desired information or to
perform some function. See 1.12.1, “Using the COMMAND Field” for the
procedure for using this field.

The only CA-Jobtrac primary command available is CANcel. CANcel exits the
panel without saving any modifications you have made.

Max CC for jobname: Includes the jobname of the job that the information on
the panel describes. Indicates the current maximum allowable condition code
value for any step in the job. If any step exceeds this value, CA-Jobtrac
imposes an output release dependency (code O) and assigns the status COND
CODE CHK. If the entry in this field is N/A, no value has been specified, and
CA-Jobtrac does not perform condition code monitoring. This field is also
displayed on the Scheduled Event Detail panel.

Step Number: Specifies the step number (three digits) to which the following
condition code exception rule applies.

Chapter 5. Modifying the Current Schedule 5-53

5.4 Step Condition Code Exceptions Panel

Relation: Conditional operator associated with the condition code. The

operator determines whether the condition code is the minimum or maximum
allowed for the step. Use one of the following.

Element Description
EQ The step may complete with a condition code equal to
the value specified in the Condition Code field.
LT The step may complete with any condition code less
than the value specified in the Condition Code field.
GT The step may complete with any condition code greater
than the value specified in the Condition Code field.
LE The step may complete with any condition code less
than or equal to the value specified in the Condition
Code field.

Condition Code: Defines the condition code the step is allowed to return
before any action is taken. The condition code is combined with the Relation
field to determine the allowable condition code that varies from the maximum
condition code value for the event (Max CC for jobname). This combination is
known as a condition code exception rule. Valid codes are 0 through 4095.

5.4.4 Changing Condition Codes for an Event on the Current

Schedule
You can make the following changes on the Step Condition Code Exceptions
panel:
■ Change the Max CC for jobname value to any value except N/A
■ Change any Step Number, Relation, Condition Code, or all three
■ Add step condition code exception rules
■ Remove step condition code exception rules

Any changes you make apply only to the version of the event currently on the
current schedule (the event's SCL is not affected). A total of 12 step condition
code exception rules can be specified.

If any step condition code exceptions exist, the Max CC must not be N/A.
Default is 0000.

If the Max CC is greater than 0000, a maximum of 11 Step CC exceptions is

allowed.

You cannot save changes to an event that has already been submitted.

5-54 Operator Guide

 5.4 Step Condition Code Exceptions Panel

Editing Fields on the Step Condition Code Exceptions Panel: Follow the
steps below to change condition code parameters for a job using the Step
Condition Code Exceptions panel.
1. Position the cursor in the field you want to change on the Step Condition
Code Exceptions panel. (If you are adding a step exception rule, position
the cursor in a blank field.)
2. Type the entry you want to appear in the field. If you want to make
additional changes, repeat steps 1 and 2.
3. Take one of the following actions:
If you want to save your changes and you . . .
■ Accessed the Step Condition Code Exceptions panel from the
Scheduled Event Detail panel using the CC primary command
Then . . .
– Type END in the COMMAND field to return to the Scheduled
Event Detail panel. You can type SAVE in the COMMAND field
on the Scheduled Event Detail panel to save any changes you
made on the Step Condition Code Exceptions panel.
OR
– Type END in the COMMAND field to return to the Scheduled
Event Detail panel. When you exit the Scheduled Event Detail
panel, you will be prompted to save all changes you have made
for the event.
■ Accessed the Step Condition Code Exceptions panel from the
Scheduled Event Display panel using the C line command
– Type END in the COMMAND field to return to the Scheduled
Event Display panel. You will be prompted to save any changes
you have made.
OR
Type CANCEL in the COMMAND field to exit the Step Condition Code
Exceptions panel and cancel any Step CC changes you have made.

Chapter 5. Modifying the Current Schedule 5-55

5.4 Step Condition Code Exceptions Panel

Example: A sample Step Condition Code Exceptions panel for TESTJOB1 is

shown below.

 --------------------------- Step Condition Code Exceptions -------------------- 

COMMAND ===> ROW 1 TO 12 OF 12

Max CC for TESTJOB1 ===> 

Step Relation Condition
Number (EQ,LT,GT,LE) Code
-------- ------------- ---------
4 LT 4
14 LE 8
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
 BOTTOM OF DATA 
 
Suppose you want to change the maximum condition code value for any step
in the job to 0004, remove the step exception rule for job Step 14, and add a
rule allowing Step 10 to complete with any condition code value greater than
0004. You would change the Max CC for TESTJOB1 value to 0004 and change
the step condition code exception rule for Step 14 to show the rule for Step 10.
The panel below shows the changes required.

 --------------------------- Step Condition Code Exceptions -------------------- 

COMMAND ===> ROW 1 TO 12 OF 12

Max CC for TESTJOB1 ===> 

Step Relation Condition
Number (EQ,LT,GT,LE) Code
-------- ------------- ---------
4 LT 4
1 GT 4
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
... ... ....
 BOTTOM OF DATA 
 

5-56 Operator Guide

 5.5 Manual Action Detail Panel

5.5 Manual Action Detail Panel

The Manual Action Detail panel specifies tasks to be performed before an
event is executed. As you complete each task on the checklist, you remove an
X from the field to the left of the task. When you remove the last X on the list,
the event's manual dependency code (M) is automatically removed.

Not every event with a manual dependency has a Manual Action Detail panel.
This panel can be displayed for an event only if the event's documentation
member was coded to require manual actions (see the Schedule Creation Guide
for information about coding documentation members to communicate with
users).

To determine whether you must complete the Manual Action Detail panel for
an event, look at the event's Scheduled Event Detail panel. If the field Manual
Actions : x (x specifies the number of manual actions required) appears
following the Location field and below the DSN Count field, the event's
Manual Action Detail panel must be completed.

If the field Manual Actions : x does not appear following the Location field
and below the DSN Count field, you can remove a manual dependency code
manually without using the Manual Action Detail panel.

To ensure that events execute properly, you should use the Manual Action
Detail panel to remove manual dependency codes whenever the Manual
Actions : x entry appears on an event's Scheduled Event Detail panel.

Defining Manual Actions: For information about defining manual actions for
an event, see the documenting events information in the Schedule Creation
Guide.

5.5.1 Displaying a Manual Action Detail Panel

To display a Manual Action Detail panel, either:
■ Enter the command MANUAL or MACT at the COMMAND field of an
event's Scheduled Event Detail panel if the entry Manual Actions : x
appears on the panel (for more information on the display Manual Action
Detail panel (MANUAL) command, see 5.5.2, “Display Manual Action
Detail Panel (MANUAL) Command”).
■ Use the M line command on an event with a manual dependency code (M)
on a Scheduled Event Display or Scheduled Event Network panel (see
1.12.3, “Using Line Commands”). This line command will not display a
Manual Action Detail panel if no manual actions exist for the event.

Chapter 5. Modifying the Current Schedule 5-57

5.5 Manual Action Detail Panel

5.5.2 Display Manual Action Detail Panel (MANUAL) Command

You can enter this command only on a Scheduled Event Detail panel to
display a Manual Action Detail panel for the event.

For example, suppose you are viewing a Scheduled Event Detail panel for
TESTJOB1 and the message Manual Actions : 3 is shown. Entering the
MANUAL command displays a Manual Action Detail panel for TESTJOB1.

The Manual Action Detail panel is a pop-up panel.

Syntax: The syntax of the display Manual Action Detail panel command is as
follows:

MANUAL
──┬─MANUAL─┬──────────────────────────────────────────────────
└─MACT───┘

5.5.3 Description of the Manual Action Detail Panel

The panel below shows a sample Manual Action Detail panel. Field
descriptions follow.

 ------------------------------- Manual Action Detail Check List --------------- 

COMMAND ===>

Event Name: TESTJOB1 Status : LATE - AWAITING DEPENDENCIES

Version : 718.1 Process Period: DAILY

Remove X when manual action is complete:

CONTACT ADMIN MANAGER TO VERIFY DAILY CLOSING WEDNESDAY

BALANCE DAILY MAN REPORTS DAILY
BALANCE WEEKLY MAN REPORTS
X KEEP IN TOUCH WITH YOUR MOTHER THURSDAY
TODAY IS YOUR WIFE'S BIRTHDAY. DRESS SIZE 7
-------------------------------------------------------------------------------
 
COMMAND: Lets you enter commands to display desired information or to
perform some function. See 1.12.1, “Using the COMMAND Field” for the
procedure for using this field. See the search keys and command information
in the Reference Summary for details of each command.

Event Name: Shows the name of the event on the current schedule. All
information on the panel pertains to the entry in this field. For more
information on Event Name, see 5.1.17, “Description of the Scheduled Event
Display Panel.”

5-58 Operator Guide

 5.5 Manual Action Detail Panel

Status: Provides an abbreviated summary of the event's current status. For

more information on current event status, see 5.1.17, “Description of the
Scheduled Event Display Panel.”

Version: Uses the form

mmdd.vvvv

The first four digits indicate the date the event was added to the current
schedule (if CA-Jobtrac assigned the version number) or a user-assigned date.
The last four digits indicate the event's version number. The number may be
user-assigned or CA-Jobtrac-assigned. If CA-Jobtrac assigned the number, the
number indicates this version's place in a series of events of the same name
added to the current schedule on the specified date.

For example, suppose TESTJOB1 has a CA-Jobtrac-assigned Version field entry

of 1202.0002. The first four digits show that the event was added to the current
schedule on 12/02. The last four digits show that this event was the second
version of TESTJOB1 added to the current schedule on 12/02.

Process Period: Indicates the process period for the event. See the Schedule
Creation Guide for information about scheduling dependencies and process
periods. See the process period keywords and cyclic process period keywords
in the Reference Summary for descriptions of process periods (any of which
could appear as entries in the Process Period field). In addition to the process
periods described in the Reference Summary the following entries may appear in
this field:

Element Description
AUTO-SCHD The event was added to the current schedule using the
AUTO-SCHD utility.
RQ-userid The event was added to the current schedule by the user
userid through the ADD command, RUN command, or
Event/Jobstream Addition panel.
DSN-TRIGGER The event was added to the current schedule using the
Automatic Dataset Recognition facility.
MSG-TRIGGER The event was added to the current schedule using the
Automatic Message Recognition facility.
A=eventname The event eventname was added to the current schedule
using the GJTRABTR utility.

Chapter 5. Modifying the Current Schedule 5-59

5.5 Manual Action Detail Panel

Checklist: Lists manual tasks to be performed before the event is submitted.

An X in the field to the left of the task indicates that the task must be
completed. If a process period appears to the right of the task, an X appears
only when the process period is matched.

Up to eight tasks may be listed.

5.5.4 Using the Manual Action Detail Panel to Remove a Manual

Dependency Code
Procedure: Follow the steps below to remove a manual dependency code
using the Manual Action Detail panel.
1. Display the Manual Action Detail panel.
2. Perform the first task on the checklist.
3. Delete the X from the field to the left of the task completed in Step 2 by
overtyping it with a blank or using the delete key and then pressing Enter.
4. Repeat steps 2 and 3 for each task on the checklist. When you press Enter
after removing the last X, the manual dependency code is automatically
removed from the event.
5. Take one of the following actions:
If you want to save your changes and you . . .
■ Accessed the Manual Action Detail panel from the Scheduled Event
Detail panel using the MANUAL primary command
Then
– Type END in the COMMAND field to return to the Scheduled
Event Detail panel. You can type SAVE in the COMMAND field
on the Scheduled Event Detail panel to save any changes you
made on the Manual Action Detail panel.
OR
– Type END in the COMMAND field to return to the Scheduled
Event Detail panel. When you exit the Scheduled Event Detail
panel, you will be prompted to save all changes you have made
for the event.
■ Accessed the Manual Action Detail panel from the Scheduled Event
Display panel using the M line command
– Type END in the COMMAND field to return to the Scheduled
Event Display panel. You will be prompted to save any changes
you have made.
OR
Type CANCEL in the COMMAND field to exit the Manual Action Detail
panel and cancel any changes you have made.

5-60 Operator Guide

 5.6 Edit Argument Panel

5.6 Edit Argument Panel

The Edit Argument pop-up panel displays the argument to pass to an event
based on its event type. The argument is displayed for editing purposes in a
pop-up panel at the bottom of the Scheduled Event Detail panel.

The argument can be edited using this pop-up panel. The 1- to 255-character
argument can contain blanks, commas, and quotes. Use the CANCEL
command to exit this panel without saving any changes you have made. Use
the END command to exit this panel and save any changes you have made.

Displaying the Panel: The Edit Argument panel is displayed by issuing the
ARG primary command from the Scheduled Event Detail panel.

The Edit Argument panel is a pop-up panel displayed for editing purposes.

Panel Sample: The panel below shows a sample Edit Argument panel.

 ---------------------------------------Edit Argument -------------------------- 

COMMAND ===>

Argument:
backup

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

Chapter 5. Modifying the Current Schedule 5-61

5.7 Remote System Credentials Panel

5.7 Remote System Credentials Panel

The Remote System Credentials pop-up panel is used with cross-platform
events (event type C) to specify the user ID, domain (NT), and password to be
used for the remote submission.

You can enter the security information using this panel. You may specify any
valid userid and password. You may also provide the NT domain name. Use
Enter to save the information or End to cancel the changes made.

Displaying the Panel: The Remote System Credentials panel can be

displayed by:
■ Issuing the PASSWORD primary command from the Scheduled Event
Detail panel. The panel is displayed using the event name (or alternate
member name if allowed) and the event location.
■ Issuing "PASSWORD member,loc" from the CA-Jobtrac main menu panel
or the Scheduled Event Display panel where:
membername
Is the member name of the password data set that is to be
added or changed. This is the event name or alternate member
name if allowed.
,loc The location number for the remote password data set
(TRACRnnn).
■ Issuing the line command # on the Scheduled Event Display panel. The
panel is displayed using the event name (or alternate member name if
allowed) and the event location.

See the REMTCRED keyword in the Setting Global Options topic of the
"Customization Tasks" chapter of the Getting Started for information on
allowing the alternate member name to be used.

Panel Sample: The panel below shows a sample Remote System Credentials
panel.

 -----------------------Remote System Credentials------------------------------- 

Member: XXX Location: 

User ID:
Domain: (NT Only)
Password:
Verify:

Press ENTER to save, END to cancel

 

5-62 Operator Guide

 5.7 Remote System Credentials Panel

The panel displays the member name and location for reference. You may
update the following fields:

User ID: The user ID to be sent to the remote Unicenter.

Domain: The domain name that the user is defined to. You may specify
domain for any remote system, but it is only used by Windows NT.

Password: The password to be sent to the remote system. When editing an

existing member, the password is set to nulls and must be respecified. The
password field is nondisplay.

Verify: Verify field for the password. This must match the password field
before an update is made. The verify field is nondisplay.

Chapter 5. Modifying the Current Schedule 5-63

5.8 CPM Flow Information Panel

5.8 CPM Flow Information Panel

The CPM Flow Information pop-up panel is used to display the flow names
with which an event is associated. The display is sorted first by the Start/End
column and then by the Flow Name column, so that start and end events are
displayed at the top.

Displaying the Panel: The CPM Flow Information panel can be displayed by:
■ Issuing the CPM primary command from the Scheduled Event Detail panel
or the Event Execution Detail panel.
■ Issuing the Y line command from the Scheduled Event Display panel.

Panel Sample: The panel below shows a sample CPM Flow Information
panel.

 ------- CPM Flow Information --------


Event: CPM11 Row 1 of 3
Command ==>
Scroll ==> CSR Press END to exit

Flow Name Start/End SLA

--------- --------- -----
FLOW1 START
FLOW4
FLOW5
 Bottom of data 

 
The panel displays the following information:

Event: Displays the event name to which the information applies.

Flow Name: The name of the CPM flows associated with the event.

Start/End: Indicates, for a particular flow, if the job is the start or end of the
flow. The values are:
START Job is start of CPM flow.
END Job is end of CPM flow.
Blank Job is neither start nor end of the flow but is to be considered by
the CPM flow.

SLA: The target SLA time for a flow. This only displays if the event is the
END of a flow. The value is in 24-hour HH:MM format.

5-64 Operator Guide

 5.9 JCL Handling

5.9 JCL Handling

| Before you remove an edit JCL dependency from an event, you must first edit
| the event's JCL. No actual changes are necessary; the JCL simply needs to be
| processed by the EDIT command. If you do not wish to affect the edit JCL
| dependency, then use the BROWSE command.

| If you attempt to remove the edit JCL dependency code (E) without first
| editing event's JCL, the message EDIT JCL appears.

You can edit the production JCL for an event using either the JCL primary
command or the E line command on the Scheduled Event Display or
Scheduled Event Network panel.

You can use the TEMP primary command on the Scheduled Event Detail panel
or the T line command on the Scheduled Event Display or Scheduled Event
Network panel to either create or access a member containing a temporary-use
copy of the event's JCL for editing.

Why Do I Use Temporary-use JCL?: Temporary-use JCL allows for

protection of the integrity of an event's production JCL. You would want to
use temporary-use JCL when you need to change an event's JCL for only one
run of the event.

You must use the temporary-use JCL TEMP command to edit JCL from
CA-Panvalet or CA-Librarian.

Example: An operator is required to make a change to an event's JCL, but

the operator does not have authority to edit the event's production JCL. The
operator may use the T line command to create a copy of the JCL for only that
run of the event. This copy is called the temporary-use JCL.

The Temp Member field on the event's Scheduled Event Detail panel will now
display the name of the member that contains this temporary-use JCL. The
JCL source field on the event's Scheduled Event Detail panel will now display
T indicating the JCL for this event is submitted from the temporary-use JCL
library.

After the event runs successfully, the temporary-use JCL is no longer

referenced. Use the GJTRMAJC utility to maintain unused members in the
temporary-use JCL library (see the Reports, Maintenance, and Recovery Guide).

Chapter 5. Modifying the Current Schedule 5-65

5.9 JCL Handling

5.9.1 Procedure
Follow the steps below to remove an edit JCL dependency code (E) from an
event.
1. Edit JCL for the event. See the following pages for information about
editing JCL.
2. Save the JCL changes and exit the JCL member.
3. Manually remove the edit JCL dependency code (E) from the event (for
more information on editing fields, see 5.1.18, “Using the Scheduled Event
Display to Modify the Current Schedule,” for the Scheduled Event Display
panel, or see 5.2.4, “Using the Scheduled Event Detail Panel” for the
Scheduled Event Detail Panel).

5.9.2 Displaying/Editing an Event's Production JCL

JCL Command: To display and edit (if you have edit authority) an event's
JCL:
■ Enter the JCL primary command at the COMMAND field of the
CA-Jobtrac primary, Scheduled Event Display, Scheduled Event Network,
or Business Group Status panel for more information see 5.9.3,
“Display/Edit Production JCL (JCL) Command.”
■ Enter the JCL primary command from an event's Scheduled Event Detail
or Event Execution Detail panel.
■ Use the E line command on an event on the Scheduled Event Display or
Scheduled Event Network panel (see 1.12.3, “Using Line Commands”).

Once the event's JCL is displayed, you can edit the JCL member using regular
ISPF/PDF commands.

You cannot use the JCL commands to edit JCL from CA-Panvalet or
CA-Librarian.

5.9.3 Display/Edit Production JCL (JCL) Command

This command displays the production JCL member for the event specified. If
you are authorized, you can then edit the production JCL. If the event has an
alternate JCL member name defined, you must specify the alternate JCL
member name.

Syntax: The syntax of the JCL command takes several forms. If you use the
command to display or edit a production JCL member from the CA-Jobtrac
primary, Scheduled Event Display, Scheduled Event Network, or Business
Group status panel, the command has the following syntax:

5-66 Operator Guide

 5.9 JCL Handling

JCL
──JCL─┬───────────┬──┬─────┬──────────────────────────────────
├─eventname─┤ └─nnn─┘
├─prefix
───┤
└─
─────────┘

If you use the command to display or edit a production JCL member from the
Scheduled Event Detail or Event Execution Detail panel, the JCL command has
the following syntax:

JCL
──JCL─────────────────────────────────────────────────────────

When you are using the JCL command from the Scheduled Event Display
panel or the Scheduled Event Network panel to display or edit a production
JCL member, you must specify the event name, not just a prefix, to satisfy the
E dependency:

JCL
──JCL──eventname──┬─────┬─────────────────────────────────────
└─nnn─┘

Syntax Explained: The following table describes the syntax of the command:

Element Description
JCL Required command word.
eventname Optional variable. Replace eventname with the name of
the event whose production JCL member you want to
display.
Required variable when you are using the JCL
command from the Scheduled Event Display panel to
display or edit a production JCL member to satisfy the
E dependency.
prefix* Replace prefix with the first few letters of the event
whose production JCL member you want to
display/update. A listing of all the JCL members
whose names start with the partial event name is
displayed. Select the member from the list.
* Use * without a prefix to display a listing of all the
JCL members. Select a member from the list.

Chapter 5. Modifying the Current Schedule 5-67

5.9 JCL Handling

Element Description
nnn Optionally use to specify a location.
If displaying an event, this is the location ID of the
event whose production JCL member you want to
display.
If you do not specify a location, your default location
is used. You must have authorization for the location
you specify.

Examples: The following command displays the JCL member for PRODJOB1:
JCL PRODJOB1

The following command displays the JCL members for events having the
prefix TEST:
JCL TEST

The following command displays all the JCL members for location 002:
JCL  2

5-68 Operator Guide

 5.9 JCL Handling

5.9.4 Displaying/Editing an Event's Temporary-use JCL

TEMP Command: To display and edit (if you have edit authority) an event's
temporary-use JCL:
■ Enter the T line command on an event on the Scheduled Event Display or
Scheduled Event Network panel (see 1.12.3, “Using Line Commands”).
■ Enter the TEMP primary command from an event's Scheduled Event Detail
or Event Execution Detail panel.
■ Change the JCL source field from a P (production JCL library) to a T
(temporary-use JCL) on the Scheduled Event Detail panel.

If you use the above commands or if you change an event's JCL source field
from a P to a T on the Scheduled Event Detail panel, you are indicating to
CA-Jobtrac that you want to edit a temporary-use copy of this event's JCL. If
the event does not already have temporary-use JCL, a copy of the production
JCL for the event is created and stored in a temporary-use JCL member. The
temporary-use JCL member is displayed for editing.

Once the event's temporary-use JCL is displayed, you can edit the JCL member
using regular ISPF/PDF commands.

If you save the temporary-use JCL member, the Temp Member field on the
event's Scheduled Event Detail panel will display the name of the member that
contains this temporary-use JCL. The JCL source field on the event's Scheduled
Event Detail panel will display T indicating the JCL for this event is submitted
from the temporary-use JCL library.

Changing the JCL source field on the event's Scheduled Event Detail panel
from P to T is comparable to entering the TEMP command.

You must use the temporary-use JCL TEMP command to edit JCL from
CA-Panvalet or CA-Librarian.

Chapter 5. Modifying the Current Schedule 5-69

5.9 JCL Handling

5.9.5 Display/Edit Temporary-use JCL (TEMP) Command

This command displays the temporary-use JCL member for the event specified.
If you are authorized, you can then edit the temporary-use JCL.

Syntax: Use the command to display or edit a temporary-use JCL member

from the Scheduled Event Detail panel, the command has the following syntax:

TEMP
──TEMP────────────────────────────────────────────────────────

Syntax Explained: The following table describes the syntax of the command:

Element Description
TEMP Required command word. Use this in the COMMAND
field on the Scheduled Event Detail panel for the event
whose temporary-use JCL member you want to display.

Example: The following command displays the temporary-use JCL member

for an event when entered in the COMMAND field on the event's Scheduled
Event Detail panel:
TEMP

5-70 Operator Guide

 5.9 JCL Handling

5.9.6 Automatic JCL Checking

Automatic JCL checking requires the use of the JCLAUTO macro. This macro
is installed with CA-Jobtrac as a CLIST in the CA-Jobtrac TRACCLST library.

What is JCLAUTO: JCLAUTO is an edit macro that redefines the END and
SAVE ISPF/PDF edit commands. JCLAUTO changes the commands to invoke
the CA-JCLTrac JCL Analyzer prior to saving the member you are editing.

If a JCL error is found, the JCL is not saved, and a CA-JCLTrac message is
issued. For more information about CA-JCLTrac, see the Extended Scheduling
Services Guide.

Invoking JCLAUTO: JCLAUTO is invoked in one of the following ways:

■ Through the use of the CA-Jobtrac TRACX29 user exit (see the sample in
TRACINST).
■ Making it the initial macro for a user's edit session. This is accomplished
with the IMACRO edit command (see the IBM manual ISPF/PDF Edit and
Edit Macros).
■ Executing it while in an edit session.

Disabling Syntax Checking: Once JCLAUTO is invoked, it remains in affect

for the duration of the edit session. If you want to disable syntax checking,
execute the following command:
JCLAUTO OFF

Chapter 5. Modifying the Current Schedule 5-71

5.10 SCL Handling

5.10 SCL Handling

Use the SCL command to display or edit a schedule's SCL.

5.10.1 Displaying/Editing a Schedule's SCL

SCL Command: To display and edit (if you have edit authority) a schedule
member's SCL, either:
■ Enter the SCL primary command at the COMMAND field of the
CA-Jobtrac primary, Scheduled Event Display, Scheduled Event Network,
or Business Group Status panel.
■ Enter the SCL primary command from a schedule's Scheduled Event Detail
panel.

Once the schedule member's SCL is displayed, you can edit the SCL member
using regular ISPF/PDF commands.

5.10.2 Display/Edit Schedule (SCL) Command

This command displays the schedule member specified. If you are authorized,
you can then edit the schedule member.

Syntax: The syntax of the SCL command takes several forms. If you use the
command to display or edit a schedule member from the CA-Jobtrac primary,
Scheduled Event Display, Scheduled Event Network, or Business Group Status
panel, the command has the following syntax:

SCL
──SCL─┬───────────┬──┬─────┬──────────────────────────────────
├─eventname─┤ └─nnn─┘
├─prefix
───┤
└──────────┘

If you use the command to display or edit a schedule member from the
Scheduled Event Detail panel, the command has the following syntax:

SCL
──SCL─────────────────────────────────────────────────────────

5-72 Operator Guide

 5.10 SCL Handling

When you are using the SCL command from the Scheduled Event Display
panel or the Scheduled Event Network panel to display or edit a schedule
member, you must use the following syntax to satisfy the E dependency:

SCL
──SCL──eventname──┬─────┬─────────────────────────────────────
└─nnn─┘

Syntax Explained: The following table describes the syntax of the command:

Element Description
SCL Required command word.
eventname Optional variable. Replace eventname with the name of
the event whose schedule member you want to display.
Required variable when you are using the SCL
command from the Scheduled Event Display panel to
display or edit a schedule member to satisfy the E
dependency.
prefix* Replace prefix with the first few letters of the event
whose schedule member you want to display/update. A
listing of all the schedule members whose names start
with the partial event name is displayed. Select the
member from the list.
* Use * without a prefix to display a listing of all the
schedule members. Select a member from the list.
nnn Optionally use to specify a location.
If displaying an event, this is the location ID of the event
whose schedule member you want to display.
If you do not specify a location, your default location is
used. You must have authorization for the location you
specify.

Example: The following command displays all the schedule members for
location 002:
SCL  2

Chapter 5. Modifying the Current Schedule 5-73

5.11 Using the EDIT Command to Edit JCL or SCL

5.11 Using the EDIT Command to Edit JCL or SCL

If authorized, you can use the EDIT command to edit JCL for an event or SCL
for a schedule. The JCL may be either temporary-use or production JCL. You
can also display the IMOD Facility of CA-GSS if the event is a REXX IMOD.

EDIT Command and Production JCL: If an event is a job type event and the
JCL source field displays P, enter the EDIT primary command at the
COMMAND field of an event's Scheduled Event Detail panel to display and
edit (if you have edit authority) an event's production JCL.

When the JCL source field on the event's Scheduled Event Detail panel
displays P, the JCL source for the event is the member that contains the
production JCL for this event.

Once the event's JCL is displayed, you can edit the JCL member using regular
ISPF/PDF commands.

You cannot use the EDIT command to edit JCL from CA-Panvalet or
CA-Librarian.

EDIT Command and Temporary-use JCL: If an event is a job type event and
the JCL source field displays T, enter the EDIT primary command at the
COMMAND field of an event's Scheduled Event Detail panel to display and
edit (if you have edit authority) an event's temporary-use JCL.

When the JCL source field on the event's Scheduled Event Detail panel
displays T, the JCL source for the event is the member that contains a
temporary copy of the JCL that is to be used for this event only.

Once the event's JCL is displayed, you can edit the JCL member using regular
ISPF/PDF commands.

You cannot use the EDIT command to edit JCL from CA-Panvalet or
CA-Librarian.

EDIT Command and SCL: If an event is a schedule, enter the EDIT primary
command at the COMMAND field of an event's Scheduled Event Detail panel
to display and edit (if you have edit authority) a schedule member's SCL.

Once the schedule member's SCL is displayed, you can edit the SCL member
using regular ISPF/PDF commands.

EDIT Command and IMODs: If an event is a REXX IMOD, enter the EDIT
primary command at the COMMAND field of an event's Scheduled Event
Detail panel to display the IMOD Facility of CA-GSS.

5-74 Operator Guide

 5.11 Using the EDIT Command to Edit JCL or SCL

5.11.1 EDIT Command

This command allows you to edit JCL for an event or SCL for a schedule. The
JCL may be either temporary-use or production JCL.

Syntax: Use the command on the Scheduled Event Detail panel to display or
edit JCL or SCL for an event, the command has the following syntax:

EDIT
──EDIT────────────────────────────────────────────────────────

Syntax Explained: The following table describes the syntax of the command:

Element Description
EDIT Required command word. Use this in the COMMAND
field on the Scheduled Event Detail panel for the event
whose JCL or SCL member you want to display.

Example: The following command displays the JCL or SCL member for an
event when entered in the COMMAND field on the event's Scheduled Event
Detail panel:
EDIT

Chapter 5. Modifying the Current Schedule 5-75

5.12 Removing a View Documentation Dependency Code

5.12 Removing a View Documentation Dependency Code

Before you remove a view documentation dependency from an event, you
must first display the event's documentation.

If you attempt to remove the view documentation dependency code (?) using
the Scheduled Event Display panel without first displaying the event's
documentation member, the message VIEW DOC appears. If you attempt to
remove the ? code using the Scheduled Event Detail panel without first
displaying the event's documentation member, a warning message will be
displayed on the panel.

Procedure: Follow the steps below to remove a view documentation

dependency code (?) from an event.
1. Display the documentation for a specific event by using the ? line
command next to the event or the DOC or ? primary command with the
eventname parameter (for more information on Displaying Event
Documentation, see the topic below).
2. Exit the event documentation.
3. Manually remove the view documentation dependency code (?) from the
event (for more information on the editing field, see 5.1.18, “Using the
Scheduled Event Display to Modify the Current Schedule,” or 5.2.4, “Using
the Scheduled Event Detail Panel”).

Displaying Event Documentation: To display an event's documentation,

either:
■ Enter the DOC or ? primary command with no parameters on the event's
Scheduled Event Detail panel or on the event's Execution Event Detail
panel; for more information see 5.12.1, “Display Documentation (DOC or ?)
Command.”
■ Enter the DOC or ? primary command on the CA-Jobtrac primary,
Scheduled Event Display, Scheduled Event Network, or Business Group
Status panels.
■ Use the ? line command on an event on the Scheduled Event Display or
Scheduled Event Network panel (see 1.12.3, “Using Line Commands”).

5-76 Operator Guide

 5.12 Removing a View Documentation Dependency Code

5.12.1 Display Documentation (DOC or ?) Command

This command displays documentation for the event specified.

Syntax: The syntax of the DOC or ? primary command takes two forms. If
you use the command to display an event's documentation from the
CA-Jobtrac primary, Scheduled Event Display, Scheduled Event Network, or
Business Group Status panel, the command has the following syntax:

DOC or ?
──┬─DOC─┬──┬───────────┬──┬─────┬─────────────────────────────
└─?───┘ ├─eventname─┤ └─nnn─┘
├─prefix
───┤
└──────────┘

If you use the command to display an event's documentation from the

Scheduled Event Detail panel or the Event Execution Detail panel, the
command has the following syntax:

DOC or ?
──┬─DOC─┬─────────────────────────────────────────────────────
└─?───┘

Chapter 5. Modifying the Current Schedule 5-77

5.12 Removing a View Documentation Dependency Code

Syntax Explained: Following are descriptions of the elements of the display

documentation command:

Element Description
DOC or ? Required command word.
eventname Optional variable when issuing the display
documentation command from the CA-Jobtrac primary,
Scheduled Event Display, Scheduled Event Network, or
Business Group Status panel. Replace eventname with the
name of the event whose documentation member you
want to display/update.
prefix* Replace prefix with the first few letters of the event
whose documentation member you want to display. A
listing of all the documentation members whose names
start with the partial event name is displayed. Select the
member from the list.
* Use * without a prefix to display a listing of all the
documentation members. Select a member from the list.
nnn Use nnn to optionally specify a documentation library by
location where nnn is the location ID. If you do not
specify a location, CA-Jobtrac uses your default location's
documentation library. It is this option that allows you
to access multiple documentation libraries.

Examples: The following command displays event documentation for

PRODJOB1:
DOC PRODJOB1

The following command displays a list of documentation members for your

default location's documentation library:
? 

5-78 Operator Guide

 5.13 Other Commands Used to Monitor or Modify

5.13 Other Commands Used to Monitor or Modify

The line commands and input commands described in this section can be used
to monitor or modify information on the current schedule or related
information. These commands are not mentioned in the remainder of this
chapter.

Some commands described in other chapters also are used to monitor or

change the current schedule. All commands are listed in the search keys and
commands and line commands sections in the Reference Summary.

Line Commands: Following are descriptions of line commands that are used
to monitor or modify the current schedule. See 1.12.3, “Using Line
Commands”) for the procedure for using line commands.

Command Explanation
| A Release dependencies. When you enter A for events
| awaiting dependencies, all dependencies except abend
| bypass dependency (code A) and predecessor
| dependency (code P) are removed. For completed events,
| the output release dependency (code O) is removed. For
| events awaiting execution, CA-Jobtrac issues a $AJnnnn
| command. If an event has environmental dependencies
| executing, they are canceled.
| D Delete event from the current schedule and place it on
| the history file. Successors to deleted events are not
| affected. The history file entry notes the user ID of the
| user who deleted the event. See the note.
E Display JCL for the selected event or SCL for the
selected schedule. If authorized, you can edit the JCL or
SCL. The JCL may be either temporary-use or
production JCL. Display the IMOD Facility of CA-GSS if
the event is a REXX IMOD.
F List file trigger. Displays the files (data set names)
required to trigger the event's submission.
H Display history. Displays the event on the history file.
J Edit temporary-use JCL. Displays the temporary-use JCL
for an event for editing. If the temporary-use JCL does
not exist, it is created.
L List dependent job stream. The primary predecessor and
successor event network for the event is listed in
primary execution sequence.

Chapter 5. Modifying the Current Schedule 5-79

5.13 Other Commands Used to Monitor or Modify

Command Explanation
M Display Manual Action Detail panel. If a Manual Action
Detail panel is available for the event, the Manual Action
Detail panel is displayed.
N Enqueue research. Displays resources (data set names)
for an event that is currently executing.
P Purge event. The event is purged from the current
schedule. If the event is awaiting execution, CA-Jobtrac
issues a $PJnnnn command. If the event is awaiting
submission, all successors are released from dependence
on the event.
T Edit temporary-use JCL. Displays the temporary-use JCL
for an event for editing. If the temporary-use JCL does
not exist, it is created.
Q Display Command (incorporating SYSVIEW/E) JOBSUM
panel. Allows you to view a selected event and to issue
Command commands. To exit from Command, enter
PF03. You will be returned to the panel from which you
issued the Q command. This command is only valid if
you are a licensed Command user and if your TSO
session has access to the Command ISPF program and its
files.
* Special Processing. The asterisk has two functions.
* and FORCE It allows jobs to be submitted for execution even if
CA-Jobtrac is on hold. To issue this command, place the
* on the line next to the job to be forced, then type
FORCE on the command line and press Enter. The job is
allowed to run, even if CA-Jobtrac is on hold. The job is
still subject to any dependencies that it may have and is
only released when all of its dependencies are satisfied.
This command does not force jobs to run when the
checkpoint is locked.
The * line command, when specified without the FORCE
command, displays a hex dump of the checkpoint record
for the event. This is typically not useful to operators
and is intended for use at the request of Computer
Associates Technical Support.

5-80 Operator Guide

 5.13 Other Commands Used to Monitor or Modify

| Note: CA-Jobtrac will deny permission to delete or purge (D line command)

| on events that show a Jobtrac status of EXECuting or AWAITING
| EXECution. This is done to force status synchronization between Jobtrac
| and the operating system. If you want to delete or purge an event with
| either Jobtrac status, you need to perform that function through SDSF.
| This will cause the appropriate SMF records to be cut and processed by
| CA-Jobtrac.

Input Commands: This section describes the commands that you can enter
in the COMMAND field to monitor CA-Jobtrac information other than current
schedule information. See 1.12.1, “Using the COMMAND Field” for the
procedure for using these commands.

See the Reports, Maintenance, and Recovery Guide for more detailed descriptions
of these commands.

Syntax Description
DSNQ={dsname|dsprefix} Displays enqueue research for a DSN
(data set name) or prefix you specify
in the command. The resulting
display lists all users of the data set.
Element Description
dsname Required variable.
Replace dsname with the
name of the data set for
which you want to
display enqueue
research.
dsprefix Required variable.
Replace dsprefix with the
initial letters common to
all data sets for which
you want to display
enqueue research.
For example, the following command
displays enqueue research for the
data set PROD.PRODJOB.DAILY:
DSNQ=PROD.PRODJOB.DAILY
As another example, the following
command displays enqueue research
for all data sets beginning with
PROD.ACCT:
DSNQ=PROD.ACCT

Chapter 5. Modifying the Current Schedule 5-81

5.13 Other Commands Used to Monitor or Modify

Syntax Description
JOBQ=eventname Displays enqueue research for an
event you specify in the command.
The resulting display lists all data
sets and resources used by the event.
The event must be currently
executing.
Element Description
eventname Required variable.
Replace eventname with
the name of the event for
which you want to
display enqueue
research.
For example, the following command
displays enqueue research for the
event TESTJOB1:
JOBQ=TESTJOB1
RESV Displays a list of any DASD (Direct
Access Storage Device) reserves in
effect.
SPACE Displays an analysis of free DASD
(Direct Access Storage Device) space.
WAIT Displays enqueue conflicts.

5-82 Operator Guide

Chapter 6. Managing Sysouts

This chapter describes managing sysouts through sysout archive and sysout
capture.

Chapter 6. Managing Sysouts 6-1

6.1 Functions of the Sysout Capture and Archival Subsystem

6.1 Functions of the Sysout Capture and Archival

Subsystem
Sysouts are system output streams produced by a program and stored in a JES
(Job Entry Subsystem) spool. When the sysout capture and archival subsystem
is used, CA-Jobtrac attempts to capture sysouts for all events scheduled or
submitted by CA-Jobtrac. Sysouts are captured from reserved CA-Jobtrac
sysout classes and stored in the CA-Jobtrac sysout capture file.

You can view captured sysouts online for a predefined number of days or
event generations following capture. After this period of online availability, the
sysouts can be archived to tape or microfiche (or both), spooled to print, or
deleted all together. How CA-Jobtrac processes sysouts for a specific event
depends on the event's sysout class.

CA-View Interface: An interface to Computer Associates CA-View

(incorporating SAR) package is available. This interface allows you to bypass
the CA-Jobtrac sysout capture and route output to CA-View instead. You can
define a CA-View output class on the Writer Options panel (see the Getting
Started for more information).

6-2 Operator Guide

 6.1 Functions of the Sysout Capture and Archival Subsystem

6.1.1 Sysout Class Parameters

You can define up to four sysout classes for use by the CA-Jobtrac sysout
capture and archival subsystem. All classes must be held classes (classes not
spooled to print).

The first sysout capture class defined to CA-Jobtrac must be the MSGCLASS
for CA-Jobtrac events.

Each class can have different parameters, allowing sysouts for different classes
to be processed differently. The following parameters can be defined for each
class:
■ The maximum number of lines of sysout to be captured for a class in an
event.
■ The maximum number of sysouts to be captured for a class in an event.
■ The action to be taken following sysout capture (for example, purge
captured sysouts from the JES spool).
■ The number of days and the number of versions of an event for which
sysouts are maintained in the sysout capture file. For example, if you
specify online retention for TESTJOB1's sysouts to be 3, then no sysouts for
TESTJOB1 are deleted from the capture database until they are more than
three days old and there are more than three sets of TESTJOB1 sysouts.
■ Archival options specifying whether the sysouts are to be archived to tape,
spooled to print, or deleted all together after the specified number of days
online.

Parameters for CA-Jobtrac sysout classes are defined during installation and
can be redefined using the Writer Options panel (see the Getting Started for
information about this panel and other system options). If you do not have
authority to view system options, ask the CA-Jobtrac administrator what
classes have been defined for sysout capture.

Chapter 6. Managing Sysouts 6-3

6.1 Functions of the Sysout Capture and Archival Subsystem

6.1.2 Proper Use of Sysout Capture

You should not direct normal event reports to a MSGCLASS class. SYSOUT=*
causes the MSGCLASS class to be used as an output class, with subsequent
archival by CA-Jobtrac. The sysout capture and archival function is not
designed as a report distribution tool. You should capture the JES Job Log, the
Expanded JCL Allocation Listing, and the Step Execution Allocation Log.

| The CA-Jobtrac primary function is to automate production scheduling. The

| purpose of the Sysout Capture feature is for short time storage of sysouts only.
| Long term storage should use an output management product such as
| CA-View.

It is important to use a SYSOUT package in an NJE environment. CA-Jobtrac

can only successfully capture sysout in an NJE environment if the JES job
number ranges on the submitting and executing nodes do not overlap and
output is returned to the submitting node in a timely manner.

6-4 Operator Guide

 6.1 Functions of the Sysout Capture and Archival Subsystem

6.1.3 How the Sysout Capture and Archival Subsystem Processes

Sysouts
The diagram below shows how sysouts from CA-Jobtrac-controlled events are
processed by the sysout capture and archival subsystem.

┌───────────────────────────────┐
│ Job scheduled through │
│CA─Jobtrac completes execution │
└───────────────┬───────────────┘
│

┌───────────────────────────────┐
│ CA─Jobtrac attempts to │
│ capture job's sysout │
└───────────────┬───────────────┘
│

┌───────────────────────────────┐
│ Is job's sysout │
│ captured immediately? │ ┌──────────────────────────────────┐
├──────────────────┬────────────┤ │ CA─Jobtrac makes two attempts, │
│ YES │ NO ├──────│ 15 seconds apart, to capture │
└──────┬───────────┴────────────┘ │ job's sysout │
│ └───────────────┬──────────────────┘
│ │

┌───────────────────────────────┐ ┌──────────────────────────────────┐
│ CA─Jobtrac retains sysouts │ │ Is job's sysout captured? │
│ in sysout capture file or │──────┤────────────────┬─────────────────┤
│ routes them to SAR or │ │ YES │ NO │
│ other sysout package │ └────────────────┴───────┬─────────┘
└────────────────┬──────────────┘ │
│
│ ┌──────────────────────────────────┐
│ Job is bypassed and sysout pro─ │
┌────────────────────────────────┐ │ cessing continues for other jobs │
│ When archive task executes, │ └──────────────┬───────────────────┘
│ sysouts are archived to │ │
│ tape, spooled to print, or │
│ deleted, depending on │ ┌──────────────────────────────────┐
│ MSGCLASS definitions │ │If bypassed job is scheduled with │
└────────────────────────────────┘ │successors. CA─Jobtrac places an │
│ output release dependency │
│ (code ) on the job │
└──────────────────────────────────┘

Chapter 6. Managing Sysouts 6-5

6.1 Functions of the Sysout Capture and Archival Subsystem

6.1.4 Other Sysout Capture and Archival Subsystem Actions

The sysout capture and archival subsystem also requeues a copy of sysouts for
abended events to a printable class, in addition to capturing sysouts in the
capture file.

6-6 Operator Guide

 6.2 Displaying Sysout Listings and Sysouts

6.2 Displaying Sysout Listings and Sysouts

After CA-Jobtrac captures sysouts, you can display panels listing the events
having sysouts in the capture file, or a specific event's sysouts, or both. You
can display:
■ The Sysout Capture Facility Menu
■ The Sysout Capture panel
■ The sysout archive index display
■ An event's sysouts

Commands Used to Display Sysout Listings and Sysouts: You can display
sysout listings and sysouts by:
■ Using the O line command on an event on the Scheduled Event Display or
Scheduled Event Network panel (see 1.12.3, “Using Line Commands”).
Entering the O line command displays one of the following:
– A Sysout Capture panel listing all events with sysouts in the capture
file that have the event name you entered in the command.
– The sysouts of the event for which you entered the command. The
actual sysouts are displayed only if no other events with the same
event name exist in the sysout capture file.
■ Entering the sysout capture browse (O) command at the COMMAND field
of the CA-Jobtrac primary, Scheduled Event Display, Scheduled Event
Network, or Business Group Status panels (for more information on the O
command see 6.2.1, “Sysout Capture Browse (O) Command”).

6.2.1 Sysout Capture Browse (O) Command

Description: This command is used to display one of the following:
■ Sysout Capture Facility Menu
■ Sysout Capture panel showing a list of all sysouts in the capture file
■ Sysout archive index
■ Sysout Capture panel showing a list of sysouts for a specified event name
or event name prefix
■ Sysouts of the event specified in the command (only if no other sysouts for
events with the same event name exist in the sysout capture file)

Chapter 6. Managing Sysouts 6-7

6.2 Displaying Sysout Listings and Sysouts

Syntax: The syntax of the sysout capture browse (O) command is as follows:

O
──┬─O───┬──┬──────────┬──────────────────────────────────────
└─OUT─┘ ├─&─────────┤
├─eventname─┤
└─prefix────┘

Descriptions of Command Elements: Following are descriptions of the

elements of the sysout capture browse (O) command:

Element Description
O Required command word. If you enter this command
with no option, the Sysout Capture Facility Menu is
displayed.
OUT Optional form of the command word. If you enter this
command with no option, the Sysout Capture Facility
Menu is displayed.
* This option displays a Sysout Capture panel listing all
events with sysouts in the capture database.
& This option displays the sysout archive index.
eventname You replace eventname with the name of the event for
which you want to display sysouts. If sysouts for only
one event matching eventname exist on the capture
database, the sysouts for the event are displayed. If
sysouts for more than one event matching eventname are
on the capture database, a Sysout Capture panel listing
the matching events is displayed.
prefix You replace prefix with the first few letters of the event
or events for which you want to display sysouts. If
sysouts for only one event matching prefix exist on the
capture database, the sysouts for the event are displayed.
If sysouts for more than one event matching prefix are on
the capture database, a Sysout Capture panel listing the
matching events is displayed.

6-8 Operator Guide

 6.2 Displaying Sysout Listings and Sysouts

6.2.2 Sysout Capture Facility Menu

You can use the Sysout Capture Facility Menu to display:
■ A Sysout Capture panel showing a list of all sysouts in the capture
database
■ A sysout archive index (for more information on the Sysout Archive Index
Display, see 6.2.6, “Sysout Archive Index Display”)
■ A Sysout Capture panel showing a list of sysouts for a specific event name
or event name prefix
■ Sysouts of a specified event

Displaying the Sysout Capture Facility Menu: You display the Sysout
Capture Facility Menu by entering the sysout capture browse (O) command at
the COMMAND field of the CA-Jobtrac primary, Scheduled Event Display,
Scheduled Event Network, or Business Group Status panels (for more
information on the sysout capture browse (O) command, see 6.2.1, “Sysout
Capture Browse (O) Command”).

Description of the Sysout Capture Facility Menu: The panel below shows a
sample Sysout Capture Facility Menu. Field descriptions follow.

 CA-Jobtrac Sysout Capture


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Enter event name or prefix:

Event/Prefix ===> Enter "" for all entries.

Enter "&" for index entry.
 
Event/Prefix: You enter one of the following options in this field:

Element Description
* Displays a Sysout Capture panel listing all events with
sysouts in the capture database.
& Displays the sysout archive index.
eventname The name of the event for which you want to display
sysouts. If sysouts for only one event matching eventname
exist on the capture database, the sysouts for the event are
displayed. If sysouts for more than one event matching
eventname are found, a Sysout Capture panel listing the
matching events is displayed.

Chapter 6. Managing Sysouts 6-9

6.2 Displaying Sysout Listings and Sysouts

Element Description
prefix The first few letters of the event or events for which you
want to display sysouts. If sysouts for only one event
matching prefix exist on the capture database, the sysouts for
the event are displayed. If sysouts for more than one event
matching prefix are found, a Sysout Capture panel listing the
matching events is displayed.

Using the Sysout Capture Facility Menu: Follow the steps below to use the
Sysout Capture Facility Menu:
1. Type an entry in the Event/Prefix field.
2. Press Enter to display the desired information.

6.2.3 Sysout Capture Panel

The Sysout Capture panel displays a list of events having sysouts in the sysout
capture file. The panel can list all events in the capture database, events with a
specified event name, or events with a specified event name prefix.

You can use this panel to display sysouts for any event listed on the panel.

Displaying a Sysout Capture Panel: You can display a Sysout Capture

panel by:
■ Entering the sysout capture browse (O) command at the COMMAND field
of the CA-Jobtrac primary, Scheduled Event Display, Scheduled Event
Network, or Business Group Status panels (for more information on the
sysout capture browse (O) command, see 6.2.1, “Sysout Capture Browse
(O) Command”).
■ Using the O line command on an event on a Scheduled Event Display or
Scheduled Event Network panels (see 1.12.3, “Using Line Commands”).
■ Using the Sysout Capture Facility Menu (for more information, see 6.2.2,
“Sysout Capture Facility Menu”).

Description of the Sysout Capture Panel: The panel below shows a sample
Sysout Capture panel. Field descriptions follow.

 CA-Jobtrac Sysout Capture ROW 1 TO 3 OF 3


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Event Event Run Start Stop SYS Comp Line
Name Num Date Time Time ID Code Count Class
-------- ----- ----- ----- ------- ---- ---- ------- -----
CRWTSTK 5423 11/4 21:38 21:38 # B1 S 18 K
CRWTST3 5427 11/4 21:38 21:38 # B1 S 18 3
TESTWCF1 5643 : 15:22 # B1 S 77 T
 

6-10 Operator Guide

 6.2 Displaying Sysout Listings and Sysouts

COMMAND: You can enter the following commands in this field:

Element Description
eventname/prefix Displays a Sysout Capture panel listing events named
eventname or whose names begin with prefix.
S eventname Displays sysouts for the first event on the Sysout
Capture panel named eventname.
* Displays a Sysout Capture panel listing all events
having sysouts in the capture database.
& Displays the sysout capture index.

Event Name: Indicates the names of events with sysouts in the sysout
capture file. All information on a line pertains to the event named in this field.

The entry &INDEX is a special entry denoting the sysout archival index. The
&INDEX entry appears at the end of sysouts that have been archived (see
"Archived Indicator" below). The only other field completed on the line with
this entry is LINE COUNT.

Event Num: Possible entries in this field are:

Element Description
nnnn Indicates the number assigned to the event by JES (Job
Entry Subsystem) or by the IMOD Facility if the event is
a REXX IMOD.
SCHD Indicates that the sysout is the result of a dynamic
execution of a schedule. Since schedule updates are
executed entirely within CA-Jobtrac, no JES job number
is assigned.
ARCH Indicates that the sysout is the result of execution of an
archive task. Since the archive task is executed entirely
within CA-Jobtrac, no JES job number is assigned.

Run Date: Indicates the date the event executed (in the form mm/dd, where
mm is a two-digit number indicating the month and dd is a two-digit number
indicating the day of the month).

Start Time: Indicates the time at which execution began (in the form hh:mm,
where hh is a two-digit number indicating the hour and mm is a two-digit
number indicating the minute of the hour).

Stop Time: Indicates the time at which execution ended (in the form hh:mm,
where hh is a two-digit number indicating the hour and mm is a two-digit
number indicating the minute of the hour).

Chapter 6. Managing Sysouts 6-11

6.2 Displaying Sysout Listings and Sysouts

Archived Indicator: (Before the SYS ID field) Indicates that a copy of the
event's sysouts have been archived. The sysouts remain in the capture file for
online access for the number of days and versions specified by system options.
However, archival of this event's sysouts is not repeated.

SYS ID: Possible entries are:

Element Description
sysname Indicates the name of the system (sysname) on which the
event executed.
SCHD Indicates that the sysout is the result of a dynamic
execution of a schedule.
ARCH Indicates that the sysout is the result of execution of an
archive task. The sysout is an Event Archive Report (see
the job archive report information in the Reports,
Maintenance, and Recovery Guide).

Comp Code: Indicates how the event completed. Possible entries are:

Element Description
S000 Indicates that the event completed normally.
xnnn Indicates that the event abended with the abend code
specified by xnnn.
CTLG Indicates that a catalog error was found.
Cnnn Indicates that a condition code parameter was violated
for the job step specified by nnn.
JCL Indicates that a JCL error was detected for the event.

Line Count: Indicates the number of lines of sysouts captured for the event.

Class: Indicates the held sysout class to which the event's sysouts were
directed.

6-12 Operator Guide

 6.2 Displaying Sysout Listings and Sysouts

6.2.4 Finding and Sorting Events

The primary commands FIND and SORT are available on the Sysout Capture
panel to enable specific searching and sorting of the listed events. These
commands can be used with the standard ISPF scrolling commands to locate
specific events.

FIND Command: The FIND primary command enables you to search the
listed events for a particular event or events.

The syntax of the FIND command is as follows:

FIND
┌─NEXT──┐
──FIND──┬──────────┬──┬───────────────┬──┼───────┼────────────
└─'string'─┘ └─'column-name'─┘ ├─ALL───┤
├─FIRST─┤
├─LAST──┤
└─PREV──┘

SORT Command: The SORT primary command allows you to sort the list in
either ascending or descending order based on the values in a specified
column.

The syntax of the SORT command is as follows:

SORT
┌─A─┐
──SORT─┬───────────────┬──┼───┼───────────────────────────────
└─'column-name'─┘ └─D─┘

Column Names: The following table equates the field names on the Sysout
Capture panel to the column names used in the FIND and SORT commands:

Panel Field Name Command Column Name

Event Name EVENT-NAME
Event Num EVENT-NUM
Run Date RUN-DATE
Start Time START-TIME
Stop Time STOP-TIME
SYS ID SYS-ID
Comp Code COMP-CODE
Line Count LINE-COUNT

Chapter 6. Managing Sysouts 6-13

6.2 Displaying Sysout Listings and Sysouts

Panel Field Name Command Column Name

Class CLASS

FIND Command Syntax Rules

■ You can limit the search for a character string to a specific column by
specifying a column name after the search argument.
■ You may enclose the search argument in single or double quotes.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.

For example, the following command finds all occurrences of TESTJOB1 in the
Event Name column.
FIND TESTJOB1 EVENT-NAME ALL
■ The default FIND command is FIND {'string'}NEXT.
■ If you specify FIND {'string'}ALL, the FIND command will scan the list to
determine the number of rows that contain the character string. It will
display the results and then position the panel to the first row that
matched the search.
■ You can enter the FIND command with no parameters to repeat the
previous find.

SORT Command Syntax Rules

■ You can specify which column to sort on by specifying a column name.
■ Specify a column name that is longer than one word in
columnname1-columnname2-columnname3 format.

For example, the following command sorts on the Line Count column.
SORT LINE-COUNT
■ The default SORT command sorts in ascending order.
■ You can enter the SORT command without any parameters to put the list
back in its original sequence.

6-14 Operator Guide

 6.2 Displaying Sysout Listings and Sysouts

6.2.5 Using the Sysout Capture Panel

Displaying Sysouts Using the S Line Command: Follow the steps below to
display sysouts for any event on the Sysout Capture panel. You can follow the
same steps to display the sysout archive index, if the entry &INDEX appears
on the Sysout Capture panel.
1. Type S in the field to the left of the event for which you want to display
sysouts (or next to &INDEX, if you want to display the sysout archive
index).
2. Press Enter to display the event's sysouts (or the sysout archive index).

Example: Suppose you want to display the sysouts for the event ACAP000D.
On the Sysout Capture panel, type S in the field to the left of the event name
ACAP000D, as shown in the panel below.

 CA-Jobtrac Sysout Capture ROW 1 TO 15 OF 15


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd hh:mm
Event Event Run Start Stop SYS Comp Line
Name Num Date Time Time ID Code Count Class
-------- ----- ----- ----- ------- ---- ---- ------- -----
S ACAPD 5423 11/4 21:38 21:38 # B1 S 18 K
CRWTST3 5427 11/4 21:38 21:38 # B1 S 115 3
crawfc1 5643 : 15:22 # B1 S 77 T
CRW1 5575 11/1 2:35 2:35 # B1 S 74 K
DW14 5635 11/1 21:56 21:56 # B1 S 5 K
OJWAM359 5575 11/13 11:38 11:39 # B1 S 57 K
OJWATEST SCHD : : # SCHD S8 14
OJWATEST SCHD : : # SCHD S8 14
PBIAD363 543 11/13 13:23 13:24 # B1 S 57 K
RBJOB1 5828 11/24 11:25 11:25 # B1 S 245 K
RBJOB2 5831 11/24 11:25 11:25 # B1 S 73 K
RBJOB3 5832 11/24 11:26 11:26 # B1 S 73 K
RBJOBA 5861 11/24 14:35 14:35 # B1 S 73 K
RBJOBB 5865 11/24 14:36 14:36 # B1 S 73 K
&INDEX  INDEX ENTRY  483
 BOTTOM OF ENTRY 
 
When you press Enter, the event's sysouts are displayed, as shown in the panel
below. You can then scroll through the sysouts, or use standard TSO ISPF
commands to browse the sysouts, or both.

Chapter 6. Managing Sysouts 6-15

6.2 Displaying Sysout Listings and Sysouts

 BROWSE -- TSOUSR.SYSOUT.T9539 --------------------- LINE  COL 1 8 

COMMAND ===> SCROLL ===> PAGE
 TOP OF DATA 
1 J E S 2 J O B L O G -- S Y S T E M B S I A - - N O D

18.1.23 JOB 386 TRAC2I - ACAPD (J 386) GOALSYS PROD JCL SUBMITTED BY J
18.1.28 JOB 386 $HASP373 ACAPD STARTED - INIT A - CLASS A - SYS BSIA
18.1.31 JOB 386 RUN27I - TRACKING INITIALIZATION COMPLETE FOR: ACAPD
18.1.32 JOB 386 IEF43I ACAPD - STARTED - TIME=18.1.32
18.2.8 JOB 386 - --TIMINGS (MINS.)--
18.2.8 JOB 386 -JOBNAME STEPNAME PROCSTEP RC EXCP TCB SRB CLOC
18.2.8 JOB 386 -ACAPD STEP1  3 . .
18.2.8 JOB 386 IEF44I ACAPD - ENDED - TIME=18.2.8
18.2.1 JOB 386 -ACAPD ENDED. NAME-USER 31 TOTAL TCB CPU TI
18.2.1 JOB 386 $HASP395 ACAPD ENDED
------ JES2 JOB STATISTICS -------
- 19 JUL 4 JOB EXECUTION DATE
- 6 CARDS READ
- 45 SYSOUT PRINT RECORDS
-  SYSOUT PUNCH RECORDS
- 3 SYSOUT SPOOL KBTYES
- .71 MINUTES EXECUTION TIME
1 1 //ACAPD JOB (DEPT4)
// 'USER 31'
 
Printing Sysouts Using the O Line Command: Follow the steps below to
print sysouts for any event on the Sysout Capture panel.
1. Type O in the field to the left of the event for which you want to print
sysouts.
2. Press Enter to print the event's sysouts. The sysouts will be printed from
your TSO session.

Deleting Sysouts Using the D Line Command: You can prevent an event's
entry from appearing on any sysout capture display by deleting the entry on
the Sysout Capture panel. The event's actual sysouts are retained on the sysout
capture file until the 0ARCHIVE or 0SYSARCH task is executed. During sysout
archival, any deleted sysouts are removed from the online capture.

Follow the steps below to delete sysouts from the sysout capture display. You
cannot delete sysouts while sysout archival is underway.
1. Type D in the field to the left of the event for which you want to delete
sysouts.
2. Press Enter to delete the event's sysouts.

Recovering Deleted Sysouts: Because the sysouts for a deleted Sysout

Capture panel entry remain on the capture database until archival, you can
continue to access deleted sysouts until archival. Following archival, you must
reload deleted sysouts from archives (for more information on the reloading
archived sysouts, see 6.3, “Reloading Archived Sysouts”).

6-16 Operator Guide

 6.2 Displaying Sysout Listings and Sysouts

The following sections describe how to redisplay deleted sysout entries, how to
view or print the actual sysouts for deleted entries, and how to restore
(undelete) deleted sysout entries.

Redisplaying Deleted Sysouts: You can display a Sysout Capture panel

listing deleted sysout entries by adding ,D to any command that displays a
Sysout Capture panel. For example, the following commands display the
deleted sysout entries indicated:

This command Displays

O *,D All deleted sysout entries
O TESTJOB1,D Deleted sysout entries for TESTJOB1
O TEST,D Deleted sysout entries for any event beginning with
TEST

You can also list deleted sysout entries by adding ,D to an entry made on the
Sysout Capture Facility Menu. For example, the following entries display the
sysout entries indicated:

This entry Displays

*,D All deleted sysout entries
TESTJOB1,D Deleted sysout entries for TESTJOB1
TEST,D Deleted sysout entries for any event beginning with
TEST

Displaying or Printing Deleted Sysouts: After redisplaying deleted sysout

entries, you can display the actual sysouts online or print them. Follow the
steps below.
1. Redisplay the sysout Capture panel entry for the deleted sysout you want
to display or print.
2. To display the sysouts online, type S in the field to the left of the event
whose sysouts you want to display.
To print the sysouts, type O in the field to the left of the event whose
sysouts you want to print.
3. Press Enter to display or print the sysouts.

Restoring Deleted Sysout Entries to the Sysout Capture Panel: After a

sysout entry is deleted and before the archive task removes the sysouts from
the online capture database, you can restore the entry to the Sysout Capture
panel.

Chapter 6. Managing Sysouts 6-17

6.2 Displaying Sysout Listings and Sysouts

Follow the steps below to restore deleted sysouts. You cannot restore sysouts
while sysout archival is underway.
1. Redisplay the deleted sysout entry you want to restore to the Sysout
Capture panel.
2. Type U (undelete) in the field to the left of the entry you want to restore.
3. Press Enter to restore the entry to the Sysout Capture panel.

6.2.6 Sysout Archive Index Display

The sysout archive index display shows a list of events that have been
archived.

Each time the archive task is executed, an index entry is appended to the index
file. Each index entry on the display begins with a line showing the date and
time at which the listed events were archived. The initial line of each entry
also shows the volume serial number of the tape on which the sysouts were
archived.

Each entry ends with a line showing the number of events for which sysouts
were archived, kept online, and purged.
| Note: Storing an excessive number of sysouts may cause the index to grow to
| a size that is not viewable online.

Displaying the Sysout Archive Index Display: You can display the sysout
archive index display by:
■ Entering the sysout capture browse (O &) command at the COMMAND
field of the CA-Jobtrac primary, Scheduled Event Display, Scheduled Event
Network, or Business Group Status panels (for more information, see 6.2.1,
“Sysout Capture Browse (O) Command”).
■ Entering & in the COMMAND field of a Sysout Capture panel.
■ Using the S line command on the &INDEX entry on the Sysout Capture
panel (for more information, see “Displaying Sysouts Using the S Line
Command”).
■ Using the Sysout Capture Facility Menu (for more information, see 6.2.2,
“Sysout Capture Facility Menu”).

6-18 Operator Guide

 6.2 Displaying Sysout Listings and Sysouts

Description of the Sysout Archive Index Display: The panel below shows a
sample sysout archive index display. Field descriptions follow.

 BROWSE -- TSOUSR.SYSOUT.T9539 --------------------- LINE  COL 1 8 

COMMAND ===> SCROLL ===> PAGE
 TOP OF DATA 
_______________ ARCHIVE DATE=yy21 TIME=1112 VOL=T198 ____________
JOBNAME JOBID CLASS DATE TIME SYSID CCODE LINES STATUS
ACAPD 386 X 7/18 18:1 BSIA S 45 PURGED
ACAPD 899 X 7/19 18:1 BSIA S 45 KEPT ON-LINE
ACAP1 436 X 7/18 18:32 BSIA S 22 KEPT.VOL=T198
ACAP1 921 X 7/19 18:3 BSIA S 22 KEPT ON-LINE

JOBS ARCHIVED: 1. JOBS KEPT ON-LINE: 4. JOBS PURGED: 1

_______________ ARCHIVE DATE=yy2 TIME=111 VOL=T692 ____________

JOBNAME JOBID CLASS DATE TIME SYSID CCODE LINES STATUS
ACAP11R 323 X 7/18 15:32 BSIA S 38 KEPT.VOL=T692
ACAP11R 795 X 7/19 14: BSIA S 38 KEPT ON-LINE
ACAP12R 3547 X 7/17 14: BSIA S 48 KEPT ON-LINE
ACAP12R 324 X 7/18 15:42 BSIA S 49 PURGED
ACAP12R 796 X 7/19 14: BSIA S 49 PURGED
ACAP13R 3548 X 7/17 14: BSIA S 48 KEPT. PRINTED
ACAP13R 325 X 7/18 15:42 BSIA S 49 KEPT ON-LINE
ACAP13R 797 X 7/19 14: BSIA S 49 KEPT ON-LINE
ACAP15D 388 X 7/18 18:2 BSIA S 49 KEPT ON-LINE
ACAP15D 9 X 7/19 18:2 BSIA S 49 KEPT ON-LINE
 
COMMAND: Lets you enter commands to display desired information or to
perform some function. See 1.12.1, “Using the COMMAND Field” for the
procedure for using this field. See the search keys and command information
in the Reference Summary for details of each command.

ARCHIVE DATE: Indicates the date on which the archive task was executed
for the events subsequently listed.

TIME: Indicates the time at which the archive task was executed for the events
subsequently listed.

VOL: Indicates the volume serial number of the tape on which sysouts for
subsequently listed events are archived.

JOBNAME: Indicates the names of events acted upon by the archive task. All
information on a line pertains to the event named in this field.

Chapter 6. Managing Sysouts 6-19

6.2 Displaying Sysout Listings and Sysouts

JOBID: Possible entries in this field are:

Element Description
| nnnnnnn Indicates the up to seven-digit number assigned to the
| event by JES (Job Entry Subsystem) or by the IMOD
| Facility if the event is an REXX IMOD.
SCHD Indicates that the sysout is the result of a dynamic
execution of a schedule. Since schedule updates are
executed entirely within CA-Jobtrac, no JES job number
is assigned.
ARCH Indicates that the sysout is the result of execution of an
archive task. Since the archive task is executed entirely
within CA-Jobtrac, no JES job number is assigned.

CLASS: Indicates the held class to which the event's sysouts were directed.

DATE: Indicates the date the event executed (in the form mm/dd, where mm is
a two-digit number indicating the month and dd is a two-digit number
indicating the day of the month).

TIME: Indicates the time at which execution ended (in the form hh:mm, where
hh is a two-digit number indicating the hour and mm is a two-digit number
indicating the minute of the hour).

6-20 Operator Guide

 6.2 Displaying Sysout Listings and Sysouts

SYSID: Possible entries are:

Element Description
sysname Indicates the name of the system (sysname) on which the
event executed.
SCHD Indicates that the sysout is the result of a dynamic
execution of a schedule.
ARCH Indicates that the sysout is the result of execution of an
archive task. The sysout is a Job Archive Report (see the
Reports, Maintenance, and Recovery Guide).

CCODE: Indicates how the event completed. Possible entries are:

Element Description
S000 Indicates that the event completed normally.
xnnn Indicates that the event abended with the abend code
specified by xnnn.
CTLG Indicates that a catalog error was found.
Cnnn Indicates that a condition code parameter was violated
for the job step specified by nnn.
JCL Indicates that a JCL error was detected for the event.

LINES: Indicates the number of lines of sysouts captured for the event.

Chapter 6. Managing Sysouts 6-21

6.2 Displaying Sysout Listings and Sysouts

STATUS: Indicates the action taken by the archive task. Possible entries are:

Element Description
KEPT ON-LINE Sysouts were retained in the sysout
capture file because the defined time
period for online availability had not
ended.
KEPT, PRINTED Sysouts were retained in the sysout
capture file and were spooled to
print.
KEPT, VOL=nnnn Sysouts were retained in the sysout
capture file and were archived to the
tape with volume serial number
nnnn.
PURGED,VOL=nnnn Sysouts were manually purged from
the sysout capture file and were
archived to the tape with volume
serial number nnnn.
PURGED Sysouts were purged from the sysout
capture file after they were archived
and online availability ended.
PURGED, PRINTED Sysouts were purged from the sysout
capture file and spooled to print.

6-22 Operator Guide

 6.3 Reloading Archived Sysouts

6.3 Reloading Archived Sysouts

You can reload sysouts to the capture database for online review after they
have been purged, if the sysouts are archived on tape. To reload one or more
of the following to the capture database, use the GJTRVRLD procedure:
■ The sysout archive index entry
■ Sysouts for all events on the archive tape (except the index)
■ Sysouts for all events with a specified event name
■ Sysouts for all events with a specified event name prefix
■ Sysouts for an event with a specified event name and event number

The GJTRVRLD procedure must be run as a CA-Jobtrac-scheduled event.

Reloaded sysouts remain on the sysout capture file only until the next time the
capture file is archived.

6.3.1 The GJTRVRLD Procedure

GJTRVRLD directs CA-Jobtrac to do the following:
■ Reload the sysouts, or sysout archive index, or both, as specified by
parameters to the GJTRVRLD procedure (if you schedule an event to
reload sysouts).
■ Request the event name and event number of the event whose sysouts you
want to reload (if you issue an MVS command to reload an event's
sysouts).

6.3.2 Scheduling an Event to Reload Sysouts

You can create JCL for an event that, when executed, reloads sysouts to the
sysout capture file. The event must be scheduled on CA-Jobtrac (for example,
using the ADD command or RUN command) so the sysouts can be reloaded to
the sysout capture file.

The event's JCL must contain both of the following:

■ A JOB statement (you can give any event name to the event)
■ An EXEC statement that invokes the GJTRVRLD procedure, including a
parameter specifying what is to be reloaded

The volume serial number of the archive tape to be used. You can determine
the volume serial number using the sysout archive index display; see 6.2.6,
“Sysout Archive Index Display.”

Chapter 6. Managing Sysouts 6-23

6.3 Reloading Archived Sysouts

You do not need to specify an output class. CA-Jobtrac automatically directs

the event's output (sysouts) to the default CA-Jobtrac capture MSGCLASS class
(the default is the first class defined in system options). However, you can
specify an output class to override the default.

Parameters to the GJTRVRLD Procedure: You must include parameters to

the GJTRVRLD procedure in the EXEC statement of your reload JCL. The
following parameters can be used to specify which sysouts are to be reloaded
and whether the archive index is to be reloaded.

Element Description
&INDEX Reloads only the sysout archive index entry.
* Reloads all sysouts, but not the archive index entry.
eventname Reloads all sysouts for events with names matching
eventname.
eventname/event# Reloads only the sysouts for the event with the name
specified by eventname and the event number specified
by event# (leading zeros can be omitted).
event* Reloads all sysouts for events whose event names begin
with the characters specified by event.

Procedure: Follow the steps below to schedule an event to reload sysouts to

the capture database.
1. Create JCL for the event that will reload sysouts. Include a JOB statement
and an EXEC statement invoking GJTRVRLD (see the reloading 6.3,
“Reloading Archived Sysouts” and “Examples”).
2. Add the event created in Step 1 to the CA-Jobtrac current schedule (see
Chapter 4, “Adding Events to the Current Schedule”).
3. When prompted, mount the required tape volume.

6-24 Operator Guide

 6.3 Reloading Archived Sysouts

Examples: The figure below shows JCL for the event RELOAD01. When
RELOAD01 is added to the CA-Jobtrac current schedule and executed, sysouts
for the event with event name TESTJOB1 and event number 938
(PARM='TESTJOB1/938') are reloaded from archive tape volume 028733
(V=028733) to the CA-Jobtrac sysout capture file.

//RELOAD1 JOB ("ACCTNG"),'PROGRAMMER',CLASS=A

//STEP1 EXEC GJTRVRLD,PARM='TESTJOB1/938',V=28733

The figure below shows JCL for the event RELOAD02. When RELOAD02 is
added to the CA-Jobtrac current schedule and executed, sysouts for all events
(PARM='*') and the archive index (PARM='&INDEX') are reloaded from
archive tape volume 100100 (V=100100) to the CA-Jobtrac sysout capture file.

//GJTRVRLD JOB ...

//STEP1 EXEC GJTRVRLD,PARM='&INDEX',V=11
//STEP2 EXEC GJTRVRLD,PARM='',V=11

6.3.3 Displaying Sysouts Captured by CA-View

The commands in this section display sysouts captured by CA-View. These
commands are valid only if you have CA-View and if you route output to a
CA-View class instead of to a CA-Jobtrac sysout capture class.

0 (Zero) Line Command: This command browses sysouts that have been
captured by CA-View. Use the following steps to invoke it:
1. Display the Scheduled Event Display or Scheduled Event Network panels.
2. Type 0 (zero) in the field to the left of the entry that you wish to display.
3. Press Enter.
4. If this is the first time you have issued this command, you are prompted
for a CA-View high-level database name. Enter the first and second
high-level index of the CA-View database that you wish to access (up to 17
characters). This name is saved in your CA-Jobtrac user profile.
5. View the sysout that is displayed. You may enter any SAR command that
you wish. See the CA-View documentation for information about CA-View
commands.

Chapter 6. Managing Sysouts 6-25

6.3 Reloading Archived Sysouts

SAR Primary Command: Issue this command on the CA-Jobtrac primary,

Scheduled Event Display, Scheduled Event Network, or Business Group Status
panels to display the SAR Primary Selection panel.

The first time you issue this command, CA-View prompts you for a high-level
database name. Enter the first and second high-level index of the CA-View
database that you wish to access (up to 17 characters). This name is saved in
your ISPF profile.

SARDB Primary Command: This command allows you to specify a different

CA-View database for CA-Jobtrac to interface with. When you issue this
command on the CA-Jobtrac primary, Scheduled Event Display, Scheduled
Event Network, or Business Group Status panels, CA-Jobtrac displays the SAR
Database Selection panel where you can specify a different high-level database
name.

Enter the first and second high-level index of the CA-View database that you
wish to access (up to 17 characters). The new name is saved in your
CA-Jobtrac user profile.

6-26 Operator Guide

Chapter 7. Restarting/Rerunning Events

This chapter explains setting up and scheduling and event rerun and
rerunning a schedule.

Chapter 7. Restarting/Rerunning Events 7-1

7.1 Setting Up and Scheduling an Event Rerun

7.1 Setting Up and Scheduling an Event Rerun

Batch jobs may abend at some time due to a system failure, user error,
incomplete data transmission, and so on. CA-Jobtrac gives you several options
for rerunning or restarting an abended event.

CA-Jobtrac will automatically set up and schedule the rerun of an event that
has had an abend.

Use CA-Jobtrac to set up the rerun or restart of an abended event. The tasks
that CA-Jobtrac performs for you are illustrated in the following example.

The panel below shows a sample CA-Jobtrac Scheduled Event Display after an
event abended:

 CA-Jobtrac Scheduled Event Display ROW 1 TO 2 OF 2


COMMAND ===> SCROLL ===> PAGE
yy/mm/dd 17:28
Event ----Target----Successor Dep Current CMD= ACVP
Name Time  Date Event(s) Codes Status Date= ALL
-------- ----- - ----- -------- ----- ----------------------------------------
TESTJOB5 16:51 1/23 J WAITING RERUN J 91 LATE
TESTJOB5 16:51 1/23 ABENDED=S3A J 91. AT 16:52-1/23
 BOTTOM OF DATA 
 
In the above example, TESTJOB5, event number 0091, had an S30A abend at
16:52.

CA-Jobtrac took the following steps:

■ Marked the original event on the current schedule as abended.
■ Rescheduled the abended event to the current schedule with a JCL
dependency and updated its status as follows:
– CURRENT EVENT STATUS—Waiting Rerun *LATE*
– DEP CODES—J
If the abended event had other dependencies, these are transferred to the
rerun event when it is scheduled.
■ Determined the calendar date for the originally scheduled event and
resolved any date cards and JCL overrides.

7-2 Operator Guide

 7.1 Setting Up and Scheduling an Event Rerun

7.1.1 Operator Tasks

Rerun Preparation: Before CA-Jobtrac can rerun an event, you need to:
■ Make any necessary changes to the temporary-use JCL, such as overrides
and symbolic resolution
■ Perform data set catalog management, to include passed and temporary
data sets, GDG data set values, and so on
■ Schedule and run any special events that CA-Jobtrac has not set up, such
as database reloads
■ Manually release the rerun event (with the A line command)

Reruns of completed events can be scheduled quickly from TSO using

CA-Jobtrac/ISPF. Any completed event on the current schedule can be selected
for rerun. CA-Jobtrac automatically reconstructs the event's original scheduling
criteria and adds the rerun event to the current schedule.

7.1.2 Alternate Event Submission

Sometimes you may need to resubmit an abended event from a location other
than the JCL library or from a library that is not defined by a location ID. You
can change the submission location by use of either the location ID parameter
or the AUTO-SCHD parameter.

Changing an Event's Location ID: When the abended event's JCL must be
submitted from a location other than the JCL or temporary-use JCL library, an
authorized user can change the location ID for the rerun event, as shown in
the following steps:
1. Select the Awaiting Rerun event by using the S line command. CA-Jobtrac
displays the Scheduled Event Detail panel.
2. Change the Location field to point to the desired submission library.
3. If you are using CA-11 for restart/rerun, specify the R line command to
invoke CA-11 (see the CA-11 User Guide); otherwise, go to Step 4.
4. To submit the event through CA-Jobtrac, release it for execution with the
A line command. CA-Jobtrac submits the event using the JCL from the
specified JCL library.

Chapter 7. Restarting/Rerunning Events 7-3

7.1 Setting Up and Scheduling an Event Rerun

7.1.3 Using AUTO-SCHD to Track a Manually Submitted Event

If an abended event needs to be manually submitted but you want CA-Jobtrac
to track it, use the AUTO-SCHD feature.

CA-Jobtrac will treat a manually submitted AUTO-SCHD event as the

regularly scheduled event, manually submitted, if another event with the same
name is on the current schedule with only a JCL dependency. The manually
submitted event is executed immediately and must contain the following
AUTO-SCHD characters (otherwise, the event may receive a JCL error):
■ A character T (for trigger) in column 70
■ The AUTO-SCHD control character (>) or your defined character in
column 71

These characters are recognized only when they are on the first line of the JOB
statement.

For more complete information on placement of control characters, other

controls that can be placed on a manually submitted event, and errors that
may occur, see 4.7, “The AUTO-SCHD Feature.”

7-4 Operator Guide

 7.1 Setting Up and Scheduling an Event Rerun

7.1.4 Using the Event's Current Status to Determine CA-Jobtrac

Actions
The current status of the selected event determines the actions attempted by
CA-Jobtrac (and the restart system). You can view an event's current status
from the Scheduled Event Display panel or the Scheduled Event Network
panel.

In response to a restart line command (R), CA-Jobtrac displays the options

available for restarting the requested event, as shown below.

Normally Completed Event: If the status on the Restart panel is one of the
following, the event completed normally:
■ Tracking Initialization Completed
■ Rerun Completed From Request
■ Rerun Completed From Abend

No restart action is assumed.

Abended Event Awaiting Rerun: If the status on the Restart panel is one of
the following, the abended event is awaiting rerun:
■ Job is Set for Restart
■ Rerun Pending From Abend
■ Rerun Abended With Abend

A step execution list is displayed.

An assumed step restart PARM is constructed, noting the most probable

(nearest) restart step. (The restart package assumes the event is to be run
through the last step.)

Executing or Waiting Event: You cannot invoke restart action until the event
is in a completed status.

Chapter 7. Restarting/Rerunning Events 7-5

7.2 Rerunning A Schedule

7.2 Rerunning A Schedule

At times an entire job stream may have to be reloaded to the schedule. You
can stage a schedule for a rerun using the @RERUN option. Select the schedule
that needs to be rerun and determine the original run date. Any job stream or
repetitive set of job streams can be rescheduled so that all scheduled date
resolutions (for overrides, date parameters, and so on) appear exactly as they
did on the original run.

7.2.1 @RERUN Global Control Record

The @RERUN=yyddd global control record is used to reload a batch or
dynamic schedule. A schedule run with this parameter will:
■ Add the events from the rerun schedule to the current day's schedule
■ Resolve all necessary parameters (date cards, overrides, and so on) to the
rerun date

Syntax: The syntax of the @RERUN control record is as follows:

@RERUN
──@RERUN=yyddd────────────────────────────────────────────────

Syntax Rules: The following rules apply to the syntax of this schedule control
parameter:
■ The @RERUN parameter must be coded on the first input line for a batch
schedule or the first line of a schedule for a dynamic schedule.
■ The @RERUN parameter must begin in column one.
■ The Julian date may be for any valid previous or current day.

For example, the following entry loads the rerun schedule into the current
day's schedule using the same date cards and JCL overrides that were used on
January 26, 2004:
@RERUN=426

Descriptions of the Control Record Elements: Following are descriptions of

the elements of the @RERUN control record:

Element Description
@RERUN Required keyword.
yyddd Julian date for which the schedule is to be reloaded. This
can be any date up to the current date.

7-6 Operator Guide

 7.2 Rerunning A Schedule

7.2.2 Using the @RERUN Global Control Record

Procedure: To use the @RERUN control record, perform the following steps:
1. Determine which schedule needs to be reloaded.
2. Enter the @RERUN parameter into one of the following:
■ The SCL library member (for a dynamic run)
■ The SCL input section of your JCL (for a batch run)
3. Run the schedule. The schedule can be submitted from the Scheduled
Event Display panel or the Scheduled Event Network panel. For example,
you might enter RUN 0SCHED01 or RUN SCHED01.
4. View the schedule output through the Sysout Capture panel or print a
hardcopy.

Example: The following batch schedule, residing in any library, is set to

reload TESTJOB1, 2, 3, and 4, according to their process periods, to the current
day's schedule. It will use the rerun date of January 26, 2004, as the calendar
setup date for the date cards and overrides of the events to be loaded.

 //GJTRVSCH JOB ... 

//EXEC2 EXEC GJTRVSCH
//SYSIN DD 
@RERUN=426 INDICATES RERUN USING JAN 26TH AS THE RERUN DATE
EVENTNM TIME DATE DEPS RELEASE1RELEASE2RELEASE3RELEASE4 PROCESSP OPDCCDELOC
          
TESTJOB1 13  J TESTJOB2 WORKDAYS 
TESTJOB2 14  TESTJOB3 WORKDAYS 
TESTJOB3 15  TESTJOB4 WORKDAYS 4
TESTJOB4 16 15 =MTWTF 
TESTJOB4 16 14 FRIDAY 
TESTJOB4 16 16 MONDAY 
 

Chapter 7. Restarting/Rerunning Events 7-7

Index

Special Characters B
@RERUN Global Control Record 7-6, 7-7 Batch method of loading schedule 4-28
Business group 3-6, 3-40, 5-41
displaying status 3-25
A name 5-6
Abend dependencies, assigning 4-19 Business Group Status Panel 3-25
Abends
displaying 5-4
requeuing sysouts 6-6 C
tracking 7-2 CA-Jobtrac
Accessing CA-Jobtrac exiting 1-18
through ISPF 1-16 ISPF interface 1-16
through TSO CLIST 1-17 TSO CLIST interface 1-17
ADD command 4-4 CA-Jobtrac Primary Panel 1-19
ADR 4-3 CA-Jobtrac User Profile Panel 1-22
Alternate member name 3-6, 3-40, 5-41 Catalog errors 6-6
AMR 2-16, 4-3 Change audit history
Argument Panel 3-50 AUDIT 2-40
Argument, displaying 3-50, 5-61 commands 2-40
Argument, editing 5-61 I 2-40, 2-41
Arithmetic symbols (syntax diagrams) 1-10 panel 2-41, 2-42
audit records 2-40 purpose 2-40
Authorization level changing target times for scheduled events 2-12
determining 1-25 Comma
for monitoring other locations 1-25 repeat symbol, use in 1-13
in effect 1-29 COMMAND field 1-36
Authorization Profile Panel 1-25 Commands
AUTO-QUEUE 4-38 @INT (continuously display schedule) 5-19
AUTO-SCHD A= (abend search) 5-4
adding events with 4-30, 4-34 ADD 4-4
overview of 4-30 ADDLOC 1-30, 5-5
Q control character 4-37 AUDIT 2-40
R control character 4-37 B= (business group name search) 5-6
submitting events with 4-30, 4-31, 4-34 CC (display Cond Code Exceptions panel) 5-52
T control character 4-36 CPM 5-64
using with reruns 7-4 D (default search) 1-21, 5-7
Automatic JCL syntax checking 5-71 D= (dependency search) 5-9
DATE= (date parameter) 5-11
DOC 5-77

Index X-1
Commands (continued) CPM Flow Information Panel 5-64
DSNQ 2-29, 5-81 CPU switching 2-15
EDIT 5-74, 5-76 Cross Node Query Panel 3-17
ENQ 2-29 Cross Node Query-Criteria Selection Panel 3-13
ENQN 2-29 current schedule
event name/prefix search 5-3 displaying 5-2
EXCLUDE 3-45 displaying events on 5-35
F 5-13 loading 4-28
taskname 2-6, 2-7 modifying 2-7, 5-79
FIND 2-26, 2-37, 2-43, 2-47, 3-20, 3-27, 3-34, 3-43, one-time additions 4-10
3-48, 5-13, 5-49, 6-13 purging event from 5-80
FORCE 5-80 updating 4-4, 4-10, 4-16, 4-24
I 2-40, 2-41 using AUTO-SCHD with 4-34
IPLS 2-45
JCL 5-66
JCL (display/edit production JCL 5-66 D
JCL (display/edit production JCL member 5-66 DASD
JCL (display/edit temporary-use JCL 5-70 displaying free space 2-31, 5-82
JCL (display/edit temporary-use JCL displaying reserves 2-31
member 5-70 DASD Analysis panel 2-33
JOBQ 2-30, 5-81 DASD Selection List panel 2-34, 2-35
K= (search key) 5-16 DASD space analysis
M (display Manual Action Detail Panel) 5-57 command 2-32
O (sysout capture browse) 6-7 I/O errors 2-34
P taskname 2-6 purpose 2-31
PP= (process period search) 5-21 VTOC list 2-36
RALL (reset/update entire schedule) 5-18 Data set
REMLOC 1-30 displaying names of 5-79
REMLOC= (remove location) 5-20 enqueue display 5-81
restrictions 1-27 history 3-30
RESV 2-30, 5-82 Data set dependencies, assigning 4-19
RUN 4-10 Date parameter 5-11
S (select for detail display) 5-35 Default command 5-7
S JOBTRAC 2-4 Default values (syntax diagrams) 1-14
SAR 6-26 Delimiters
SARDB 6-26 syntax diagrams, use in 1-11
SCL 5-72 Dependencies
SCL (display/edit SCL member) 5-72 displaying events with 5-9
SHIFT (shift search) 5-22 requiring manual action 5-57
SORT 2-26, 2-37, 2-43, 2-47, 3-20, 3-27, 3-34, 3-48, restrictions 1-28
5-15, 5-49, 6-13 types of 5-26
SPACE 2-32, 5-82 Documentation
STATUS 1-34, 2-49 of an event 5-76
T= (time search) 5-23 Documentation for events 5-57
TEMP 5-69 dump 2-17
WAIT 2-30, 5-82
Condition codes
changing 5-54
E
Edit Argument Panel 5-61
defining maximum 4-17, 4-21
Edit JCL dependencies
displaying 5-52
assigning 4-19

X-2 Operator Guide

Enhancements 1-5
Enqueue research G
commands 2-28 GJTRABTR utility 4-3
displaying data set names 5-79, 5-81 GJTRVRLD procedure 6-23
displaying event name 5-81 GJTRVSCH program 4-28
DSNQ 2-29 Global control records
ENQ 2-29 @RERUN 7-6, 7-7
ENQN 2-29
JOBQ 2-30
panel 2-25
H
Help, online 1-40
purpose 2-25
History file 3-30, 5-79
RESV 2-30
WAIT 2-30
Enqueues I
displaying conflicts 5-82 I dependency, changing 5-33, 5-44
Environmental Dependencies Panel 3-22 internals, controlling 2-23
Environmental dependencies, displaying IPL 2-2, 2-16
status 3-22 IPL history
Errors, catalog 6-6 command 2-45
Event IPLS 2-45
adding to schedule 4-3 panel 2-46
AUTO-QUEUE class 4-38 purpose 2-45
deleting 5-79 IPLTABLE 2-16
displaying 3-2, 3-36, 5-2, 5-6, 5-16, 5-18, 5-21, ISPF
5-22, 5-23, 5-35 interface 1-16
documentation of 5-77
enqueue display 5-81
execution sequence 5-47 J
finding on display 5-13 JCL
history 3-30 displaying 5-66, 5-70, 5-74, 5-76
online sysout 6-7 for loading schedule 4-28
purging 5-80 submitting with AUTO-SCHD 4-30, 4-34
sorting display of 5-15 JCL dependencies
submission 4-31, 4-34 assigning 4-19
Event documentation 5-57 JCL member, displaying 5-74, 5-76
Event History Detail Panel 3-36 JCL syntax checking 5-71
Event History Display Panel 3-30 Jobs
Event type 3-6, 3-39, 5-40 submission 4-30
Event/Jobstream Addition panel 4-16
Execution dependencies
alteration restrictions 1-28 K
assigning 4-16, 4-19 Keywords (syntax diagrams) 1-10
types of 4-19, 5-26
Exiting CA-Jobtrac 1-18
L
Line commands 1-39, 5-79
F Loading current schedule
with AUTO-SCHD 4-30
FORCE command 5-80
with batch event 4-28
Locations
adding 1-30, 5-5

Index X-3
Locations (continued) Panels (continued)
assigning ID to 4-21 Cross Node Query-Criteria Selection 3-13
changing for rerun 7-3 DASD Analysis 2-33
monitoring 1-30 DASD Selection List 2-34, 2-35
removing 1-30, 5-20 DASD Space Analysis 2-31
Edit Argument 5-61
Enqueue Research 2-25
M Environmental Dependencies 3-22
Manual Action Detail Panel 5-57 Event Execution Detail 3-2, 5-35
Manual dependencies Event History Detail 3-36
assigning 4-19, 5-80 Event History Display 3-30
removing 5-60 Event/Jobstream Addition 4-16
Member name, alternate 3-6, 3-40, 5-41 IPL History 2-46
messages, at IPL 2-2 Location Profile 1-26
Microfiche for sysout archival 6-2 Manual Action Detail 5-57
Missing Events Panel 3-42 Missing Events 3-42
Modifying current schedule NJE Execution Detail 3-9
with line commands 5-79 Remote System Credentials 5-62
MSGCLASS 6-3, 6-4 Scheduled Event Detail 5-35
MVS commands Scheduled Event Display 1-41, 5-2, 5-24
for adding events to schedule 4-3 Scheduled Event Network 5-47
for adding schedules to the current schedule 4-3 Step Condition Code Exceptions 5-52
for JMF 2-18 Sysout Archive Index Display 6-18
for miscellaneous CA-Jobtrac functions 2-15 Sysout Capture 6-10
to change target times 2-12 Sysout Capture Facility Menu 6-9
to control CA-Jobtrac scan task 2-14 System Status Display 1-34, 2-49, 2-50
to modify current schedule 2-7 User Options 1-43
to start CA-Jobtrac 2-4 Volume Pull List 3-46
to stop CA-Jobtrac 2-6 VTOC 2-36
Writer Options 6-3
N Parentheses
syntax diagrams, use in 1-11
NJE Execution Detail Panel 3-9
PF keys
defining 1-43
O END 1-18
options, reinitializing internal 2-18 using 1-36
Output release dependencies Predecessor dependencies
assigning 4-19 assigning 4-19, 4-20
removing 5-79 removing 5-79
Predecessor event
defining 4-20, 4-22
P displaying execution sequence 5-47
Panels displaying number of 5-35
Argument 3-50 process period
Authorization Profile 1-25 as historical data 2-40
Business Group Status 3-25 AUTO-SCHD 4-34
CA-Jobtrac Primary 1-19 displaying 5-35
CA-Jobtrac User Profile 1-22 displaying schedule for 5-21
Change Audit History 2-41, 2-42 RQ-userid 4-16
CPM Flow Information 5-64 types of 5-59
Cross Node Query 3-17

X-4 Operator Guide

Programs Syntax checking 5-71
comma Syntax diagrams
repeat symbol, use in 1-13 reading (how to) 1-10—1-15
parentheses Sysout
syntax diagrams, use in 1-11 archival 6-1
punctuation capture 6-1
syntax diagrams, use in 1-10 classes 6-3
Punctuation marks (syntax diagrams) 1-10 definition of 6-2
deleting 6-16
displaying after archival 6-18
Q displaying after deletion 6-17
Queued release dependencies, assigning 4-20 online display of 6-2, 6-7, 6-9, 6-15
printing 6-16
R printing after deleting 6-17
recovering after deleting 6-16
reinitializing internal options 2-18
reloading after archival 6-23
Remote System Credentials Panel 5-62
requeuing after abend 6-6
RUN command 4-10
restoring after deletion 6-17
Sysout Archive Index Display 6-18
S Sysout Capture Facility Menu 6-9
scan task Sysout Capture Panel 6-10
starting 2-4 system status 2-49
starting multiple 2-4 System Status Display 1-34
stopping 2-6 System Status Display panel 2-49, 2-50
using MVS commands to control 2-14
Schedule
member 4-16, 4-24
T
Tapes
permanent 4-24
for sysout archival 6-2
rerunning 7-6
target times
self-perpetuating 4-27
changing 2-12
Scheduled Event Detail Panel 5-35
displaying events with 5-23
Scheduled Event Display Panel 1-41
using MVS commands to change 2-12
Scheduled Event Network Panel 5-47
task commands 2-15
SCL
TRACAUTH tables 1-25, 2-15
displaying 5-72, 5-74, 5-76
TSO interface to CA-Jobtrac 1-17
using to load schedule 4-28
SCL member, displaying 5-72, 5-74, 5-76
Search key strings 1-38, 5-16 U
Self-perpetuating schedule 4-27 Updating current schedule
Sequence of execution 5-47 with ADD 4-4
Shift schedule 5-22 with AUTO-SCHD 4-30
SPACE command 2-32 with Event/Jobstream Addition panel 4-16
Step Condition Code Exceptions Panel 5-52 with RUN 4-10
stopping CA-Jobtrac 2-6 with schedules 4-24
Successor event User Options Panel 1-43
assigning 4-22
defining 4-20
displaying execution sequence 5-47 V
Summary of version enhancements 1-5 Variables (syntax diagrams) 1-10

Index X-5
Version 4-20, 4-21, 5-35
Version enhancements summary 1-5
View documentation dependencies
assigning 4-19
removing 5-76
VTOC list, displaying 2-36
VTOC panel 2-36

W
WTOR messages 2-2

X-6 Operator Guide