Unic Job-Management PDF

Unicenter CA-Jobtrac Job
® ™
Management
Reports, Maintenance, and Recovery Guide

r11 SP2
Third Edition
This documentation and any related computer software help programs (hereinafter referred to as the
“Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by CA at
any time.
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in
part, without the prior written consent of CA. This Documentation is confidential and 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 the documentation for
their own internal use, and may make one copy of the related software as reasonably required for back-up and
disaster recovery purposes, 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 provisions of the license for
the product are permitted to have access to such copies.
The right to print copies of the documentation and to make a copy of the related software is limited to the period
during which the applicable 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 certify in writing to CA that all copies and partial copies of the
Documentation have been returned to CA or destroyed.
EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, 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 the Documentation is governed by the end user’s applicable license
agreement.
The manufacturer of this Documentation is CA.
Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the
restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-
7014(b)(3), as applicable, or their successors.
All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.
Copyright © 2006 CA. All rights reserved.

CA Product References
This document references the following CA products:
■ Unicenter® CA-Jobtrac™ Job Management (Unicenter CA-Jobtrac)
■ Unicenter® AutoSys® Job Management (Unicenter AutoSys JM)
■ Unicenter® CA-Easytrieve® Report Generator (Unicenter CA-Easytrieve)
■ Unicenter® CA-MIM Resource Sharing (Unicenter CA-MIM)
■ Unicenter® CA-MII Data Sharing (Unicenter CA-MII)
■ Unicenter® CA-MIA Tape Sharing (Unicenter CA-MIA)
■ Unicenter® CA-MIA Message Sharing (Unicenter CA-MIC)
■ Unicenter® Network and Systems Management Job Management Option (Unicenter NSM JM
Option)
■ Unicenter® CA-OPS/MVS® Event Management and Automation (Unicenter CA-OPS/MVS)
■ Unicenter® CA-Scheduler® Job Management (Unicenter CA-Scheduler)
■ Unicenter® CA-Spool™ Print Management (Unicenter CA-Spool)
■ Unicenter® CA-SYSVIEW® Realtime Perfomance Management (Unicenter CA-SYSVIEW)
■ Unicenter® Universal Job Management Agent (Unicenter Universal Job Management Agent)
■ Unicenter® CA-View® Output Archival and Viewing (Unicenter CA-View)
■ Unicenter® CA-7™ Job Management (Unicenter CA-7)
■ Unicenter® CA-11™ Restart and Tracking (Unicenter CA-11)
■ Advantage™ CA-Datacom®/DB Database (Advantage CA-Datacom/DB)
■ AllFusion® CA-Panvalet® (AllFusion CA-Panvalet)
■ AllFusion® CA-Librarian® (AllFusion CA-Librarian)
■ eTrust® CA-ACF2™ Security (eTrust CA-ACF2)
■ eTrust® CA-Examine™ Auditing (eTrust CA-Examine)
■ eTrust® CA-Top Secret® Security (eTrust CA-Top Secret)
Contact Technical Support

For online technical assistance and a complete list of locations, primary service hours, and telephone
numbers, contact Technical Support at http://ca.com/support.
3
4 Reports, Maintenance, and Recovery Guide
Contents
Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
CA-Datacom/AD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 2. Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Event Archive Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Historical Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
JTEZREPT Report Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Report Selection/Processing Options . . . . . . . . . . . . . . . . . . . . 16
Data Selection Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Reporting Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Report Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
History Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Display Schedule Report (Module GJTREZJW) . . . . . . . . . . . . . . 19
List Schedule Report (Module GJTREZJS) . . . . . . . . . . . . . . . . 23
List IPL Report (Module GJTREZIP) . . . . . . . . . . . . . . . . . . . . 28
List Audit Report (Module GJTREZAU) . . . . . . . . . . . . . . . . . . . 30
Chapter 3. Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Product Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Accessing the Current Schedule . . . . . . . . . . . . . . . . . . . . . . . 35
Using GJTRABTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
GJTRABTR Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . 48
GJTRABTR Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
ABEND Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Add Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
DELete Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
DUMP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
END Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Get Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
IMod Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Iserve Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
JTsys Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
MODify or POST Command . . . . . . . . . . . . . . . . . . . . . . . . 55
Node Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
PURge or PRG Command . . . . . . . . . . . . . . . . . . . . . . . . . 56
Query Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
STACK Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
GJTRATBR Command Parameters . . . . . . . . . . . . . . . . . . . . . 58
Coding JCL to Invoke GJTRABTR Processing . . . . . . . . . . . . . . 58
Example of a CLIST Invoking GJTRABTR . . . . . . . . . . . . . . . . . 59
Performing Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Methods of Executing the Archivals . . . . . . . . . . . . . . . . . . . . . 61
About the GJTRJARC Utility . . . . . . . . . . . . . . . . . . . . . . . . . 62
GJTRJARC PROC Parameters . . . . . . . . . . . . . . . . . . . . . . . 63
Modifying the Sysout Capture File . . . . . . . . . . . . . . . . . . . . . . . . 67
Contents 5
Deleting Members from Temporary-Use JCL Libraries . . . . . . . . . . . . 68
GJTRMAJC Utility Parameters . . . . . . . . . . . . . . . . . . . . . . . . 69
Deleting Archived Records with GJTRJPRG . . . . . . . . . . . . . . . . . . 70
Chapter 4. Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Switch Primary Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Relocate the CA-Datacom/AD MUF . . . . . . . . . . . . . . . . . . . . . . . 76
Scheduled CA-Datacom/AD Outage . . . . . . . . . . . . . . . . . . . . 76
Relocate the CA-Datacom/AD MUF for Unicenter CA-Jobtrac Using the
SUSPEND/RESUME Commands . . . . . . . . . . . . . . . . . . . . . 77
Relocate the CA-Datacom/AD MUF for Unicenter CA-Jobtrac Using the
Auto EOJ Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Unscheduled CA-Datacom/AD Outage . . . . . . . . . . . . . . . . . . . 78
Shadow MUF Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Recover the Sysout Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Recover the Status of Events . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
AMR Recovery Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Chapter 5. Database Backup, Recovery, and Utilities . . . . . . . . . . 87

CA-Datacom/AD Log File (LXX) . . . . . . . . . . . . . . . . . . . . . . . . . 89
CA-Datacom/AD Recovery File (RXX) . . . . . . . . . . . . . . . . . . . . . . 90
Hardware Backup and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . 91
DBUTLTY and Unicenter CA-11 . . . . . . . . . . . . . . . . . . . . . . . . . 92
Backup and Restore Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Provided Utility Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Spill (DBSPILL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Backups (DBBKHOT, DBBKSTAT) . . . . . . . . . . . . . . . . . . . . . 98
Restore (DBLOAD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Recovery (DBRECOV) . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
Other Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Chapter 6. User Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

TRACX01: JCL Submission Exit (After JCL Read) . . . . . . . . . . . . . 106
TRACX02: Sysout Browse Authorization Exit . . . . . . . . . . . . . . . . . 107
TRACX03: JCL Submission Exit (Before JCL Read) . . . . . . . . . . . . 108
TRACX06: Date Card Calculation and Insertion Exit . . . . . . . . . . . . 109
TRACX08: TRACAUTH Interface Exit . . . . . . . . . . . . . . . . . . . . . 110
TRACX09: Schedule Scan Exit . . . . . . . . . . . . . . . . . . . . . . . . . 112
TRACX10: GJTRABTR and @JOBTRAC Utility Exit . . . . . . . . . . . . 113
TRACX11: Sysout Capture Exit . . . . . . . . . . . . . . . . . . . . . . . . 114
TRACX12: Sysout Archive Exit . . . . . . . . . . . . . . . . . . . . . . . . . 115
TRACX13: Schedule Update Exit . . . . . . . . . . . . . . . . . . . . . . . 117
TRACX14: Operator Command Exit . . . . . . . . . . . . . . . . . . . . . . 118
TRACX16: AUTO-SCHD Exit . . . . . . . . . . . . . . . . . . . . . . . . . . 119
TRACX18: JMF Pre-resolution Exit . . . . . . . . . . . . . . . . . . . . . . 120
TRACX19: JMF Post-Processor Exit . . . . . . . . . . . . . . . . . . . . . . 121
TRACX20: Event Archive Exit . . . . . . . . . . . . . . . . . . . . . . . . . 122
TRACX21: Environmental Dependency Retry Exit . . . . . . . . . . . . . . 123
TRACX22: IMOD Submission Exit . . . . . . . . . . . . . . . . . . . . . . . 124

TRACX23: JMF Dynamic Variable Preprocessor Exit . . . . . . . . . . . . 125
TRACX24: CA-JCLTrac Standards Enforcement Exit . . . . . . . . . . . . 126
Call Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Macro Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
@JCLKEY Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
@JCLTXT Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
@ERRM Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
@PUTM Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
@SCAN Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
TRACX25: CA-JCLTrac Tape Management System Interface Exit . . . . 132
TRACX26: Security Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
TRACX28: CA-JCLTrac PROCLIB Dynamic Allocation . . . . . . . . . . . 137
TRACX29: CA-Jobtrac Library Edit Exit . . . . . . . . . . . . . . . . . . . . 138
TRACX30: NJE ROUTE/XEQ Statement Exit . . . . . . . . . . . . . . . . 139
TRACX31: Cross-Platform Support Exit . . . . . . . . . . . . . . . . . . . . 140
Chapter 7. TRACAUTH Security . . . . . . . . . . . . . . . . . . . . . . . 141

Implementing a TRACAUTH Table . . . . . . . . . . . . . . . . . . . . . . . 142
User Authorization Profile Statements . . . . . . . . . . . . . . . . . . . . . 143
Termination Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
@AUTH Macro Statement Examples . . . . . . . . . . . . . . . . . . . . . 148
Chapter 8. The Sysout Capture File . . . . . . . . . . . . . . . . . . . . 149

Contents of the Sysout Capture File . . . . . . . . . . . . . . . . . . . . . . 150
Compression Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Sizing the Sysout Capture File . . . . . . . . . . . . . . . . . . . . . . . . . 156
Chapter 9. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . 161

Diagnostic Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
Problem Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Verify the Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Collect Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Interpret Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . . . . 164
Access the Online Support System . . . . . . . . . . . . . . . . . . . . . . 165
Requirements for Using CA Support Online . . . . . . . . . . . . . . . 165
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
Contact Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Product Releases and Maintenance . . . . . . . . . . . . . . . . . . . . . . 167
Request Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Contents 7
Chapter 1. Introduction
This section contains the following topics:
CA-Datacom/AD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
This guide is written for systems software programmers and personnel

responsible for the implementation and maintenance of Unicenter®
CA-Jobtrac™ Job Management (Unicenter CA-Jobtrac).
Chapter 1. Introduction 9
CA-Datacom/AD
CA-Datacom/AD
Unicenter CA-Jobtrac uses Advantage CA-Datacom/DB as its database.
Advantage CA-Datacom/DB is an incredibly fast database engine that allows for
forward recovery, data integrity after a system outage, backup-while-open, and
more.
CA-Datacom/AD is identical in every way to Advantage CA-Datacom/DB,

except that you cannot create your own databases in CA-Datacom/AD.
Otherwise, the operation and use of both CA-Datacom/AD and Advantage
CA-Datacom/DB are the same.
To avoid confusion, all references in the guides are to CA-Datacom/AD.

Chapter 2. Reports
Event Archive Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Historical Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
JTEZREPT Report Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
History Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Chapter 2. Reports 11
Event Archive Report
Event Archive Report

The 0ARCHIVE and 0JOBARCH dynamic tasks create a history database
report and place this report on the sysout capture file.
To access this report through the Sysout Capture Facility, enter the following
command in the COMMAND field:
O ARCHIVE
For complete information about viewing and printing sysouts, see the managing
sysout information in the Operator Guide.
The following figure shows an example of an event archive report:
1/12/2yy.286 CA-JOBTRAC(CHD4) - MAINTENANCE UTILITY (C)1992,25 CA, INC. GJTRJARC-1

14:13:17 JOBTRAC4 - EVENT ARCHIVE LISTING PARM=LIST,ALL,FULL PAGE 1
EVENT TABLE CURRENT BUSINESS SCHEDULED SUBMITTED STARTED COMPLETED SYS JOB COMP EVENT NJE
NAME VERSION TYPE STATUS LOC GROUP DATE TIME DATE TIME DATE TIME DATE TIME ID NUMBER CODE TYPE -
-------- -------------- ----- ---------- --- -------- ----- ----- ----- ----- ----- ----- ----- ----- ---- ------- ----- ----- -
BOB 2535.1 +EVT WAIT DEPS USER1 3/5 17.18 1/2 17.18 1/2 17.18 1/2 17.18 .... NORML JOB N
2538.1 +EVT WAIT DEPS USER1 3/8 12.47 1/2 12.47 1/2 12.47 1/2 12.47 .... NORML JOB N
2538.2 +EVT WAIT DEPS USER1 3/8 12.48 1/2 12.48 1/2 12.48 1/2 12.48 .... NORML JOB N
USER21R 2555.2 +EVT COMPLETE USER21 5/5 16.38 5/7 16.38 5/7 16.38 5/7 16.38 XE79 657 NORML JOB N
2555.2 +EVT COMPLETE USER21 5/5 16.38 5/5 16.38 5/5 16.38 5/5 16.38 XE79 648 NORML JOB N
REPTESTA 2512.1 +EVT WAIT DEPS SCLT2 1/2 2.3 1/2 2.3 1/2 2.3 1/2 2.3 .... NORML JOB N
2512.2 +EVT WAIT DEPS SCLT2 1/2 2.3 5/7 2.3 1/2 2.3 5/7 2.3 .... NORML JOB N
REPTESTB 2512.1 +EVT WAIT DEPS SCLT2 1/2 . 1/2 . 1/2 . 1/2 . .... NORML JOB N
JARED 25517.1 +EVT WAIT DEPS USER21 5/17 8.54 1/2 8.54 1/2 8.54 1/2 8.54 SCHD NORML JOB N
SCLT 2512.1 +EVT CC CHECK USER1 1/2 12.4 1/2 12.4 1/2 12.4 1/2 12.4 SCHD 648 S/8 JOB N
SCLT2 2512.1 +EVT COMPLETE USER1 1/2 12.2 1/2 12.2 1/2 12.2 1/2 12.2 SCHD 648 NORML JOB N
2512.1 +EVT CC CHECK USER1 1/2 12.2 1/2 12.2 1/2 12.2 1/2 12.2 SCHD S/8 JOB N
2512.1 +EVT CC CHECK USER1 1/2 12.2 1/2 12.2 1/2 12.2 1/2 12.2 SCHD ....... S/8 JOB N
JOB4 25112.1 +EVT WAIT DEPS MISSINGA 1/12 1.11 1/1 1.11 1/12 1.11 1/1 1.11 JOB N
+ARG THIS IS ARG THE IS TOOOOOOOOOOOO LONG TO FIT ON ONE CARD
+CCD 3LT4
+PST/PRED JOBTEST225112.1?
14 EVENTS PROCESSED THIS PERIOD.

E N D O F R E P O R T

Historical Summary Report

The summary report is produced from the STT statistical records created and
maintained on the CA-Datacom/AD database by Unicenter CA-Jobtrac. The
STT records meeting the selection filtering are selected for summarization and,
optionally, printing in detail.
To access this report, run the JTEZREPT procedure referencing the

GJTREZST CA-Easytrieve source code that produces this report.
Symbols on the Report: The filtering criteria for selecting STT records for
participation in this report are as follows:
SYSTEM TOKEN (STT1-F-TOKEN)
Defines the one-character Unicenter CA-Jobtrac system ID to select or * for
all systems. This is required.
HISTORY INDICATOR (STT1-F-HIST)
Specifies whether to select archived records. Values are Y to include, N to
exclude, or * for both.
SYSTEM ID (STT1-F-SYSTEM)
Specifies a four-character SMF system ID to include. This can be generic
using the * character. The entry SYB* would list all system IDs starting with
SYB.
REPORTING LEVEL (STT1-F-LEVEL)
Specifies either DETL for listing individual detail STT records selected or
SUMM to list only a summary of the total of the selected detail.
REPORT DATE FORMAT (STT1-F-DATEFM)
Specifies the format of report dates in the data shown as I International
(YYYY/DD/MM) or A American (YYYY/MM/DD).
REPORTING INTERVAL (STT1-F-STTFDAT, STT1-F-STTFTIM,
STT1-F-STTTDAT, STT1-F-STTTTIM)
Specifies the FROM and THRU period for which STT records are selected.
Use the format of YYYY/MM/DD HH:MM:SS for this field.
The following figure shows an example of a historical summary, which appears

as three separate reports:
■ Report Processing Options - The filtering options in effect for the report, and
any errors found show on this report.
■ List Statistics Report - The actual statistical summary report data.
■ Totals - The count of records processed to produce the report.
1/12/yy CA, INC. - JOBTRAC R11 REPORTING

GJTREZST - LIST STATISTIC REPORT PROCESSING PAGE 1
OPTION/FILTER FILTER/ OPTIONAL OPTIONAL OPTIONAL DESCRIPTION/COMMENT/ERROR MESSAGE

TYPE BEGIN BEGIN END END
DATE TIME DATE TIME
SYSTEM TOKEN - JOBTRAC SYSTEM IDENTIFICATION TOKEN

HISTORY INDICATOR - INCLUDE ARCHIVE HISTORY DATA
SYSTEM ID - SYSTEM ID ORIGINATING STATISTICS
REPORTING LEVEL SUMM - DETAIL OR SUMMARY INFORMATION
REPORT DATE FORMAT I - INTERNATIONAL OR AMERICAN DATE FORMAT
REPORTING INTERVAL - INTERVAL OF STATISTICS
JTEZ1I - GJTREZST; NO ERRORS DETECTED.

GJTREZST - LIST STATISTICS REPORT PAGE 1
T H SYS REPORTING INTERVAL DATA EVENT COMPLETED

O S ID FROM/THRU ACTION ACTION ACTION
K T DATE TIME DATA COUNT EVENT COUNT SUBMITTED AUTO SCHD
25/27/7 2:5:7 JCL READ 216 LOCAL 41 SYSABEND

25/4/8 2:5:8 NJE(SUB)
DB OPEN 89 NJE(RCV) CONDCODE 1
DB CLOSE 285 XPLAT JCLERROR
DB COMMIT 24,34 TEMPJCL USR EXIT
DB ROLLBK 13 LATE 1
NORMAL 793
SOUT FILE DUMMY 768
SOUT LINE ARCHIVE 3 OPS PURG
IMOD OPS DELET 1
SCHD READ 1,827 SCHD LOAD SCHD FAIL 1
VSCH SECS 131 EDEP FAIL
DSN TRG RSR FAIL
MESG TRG RERUN MEXC FAIL
CMND TRG RESTAGE NJCL FAIL

GJTREZST - LIST STATISTIC REPORT TOTALS PAGE 1
TOTAL ACTIVE ARCHIVED

RECORDS RECORDS RECORDS
READ SELECTED SELECTED
82 79

JTEZREPT Report Utility

Unicenter CA-Jobtrac batch reporting uses an extremely flexible programming
language, CA-Easytrieve, to deliver history reporting. For details about using
CA-Easytrieve, see the manuals accompanying that product. The explanation
here is confined to its use in this history reporting.
This reporting utility allows users to:

■ Use keyword values to tailor reporting options to their requirements within
the existing functionality as delivered, or
■ Make a copy of the source code modules and modify the code to deliver
additional functionality, or
■ Use the delivered modules as a guide to create new modules to deliver
whatever functionality is wanted.
The reporting as delivered consists of the following reporting components:

JTEZREPT This PROC executes CA-Easytrieve Common Component
modules to produce requested reports. These modules are:
GJTREZJW Display Schedule Job report
GJTREZJS List Schedule Job report
GJTREZIP List IPL report
GJTREZAU List Audit report
Each module produces three reports in the following general categories:

processing options in effect, detail report specific to the module, and processing
totals. These reports are similar in content and format to the JREPORT3
reports (supplied in earlier releases) but provide expanded functionality. This
functionality includes mixing historical (archived) data with current active data
on the same report and showing all job dependencies in effect.
Each module also has three sections of the code where modifications can
easily be made affecting the content and format of the detail report, each of
these sections is clearly documented and enclosed in a ///////////// border so that
the sections are easily located.
Data Selection/Processing Options: You can place predefined values into a

list causing the optional processing of the module to function as specified within
the available choices.
Data Selection Filtering: You can modify the data selection code to exceed
the functions pre-programmed and allowed in the previous section. The data
selection code actually interrogates the data and selects those records to
participate in the report.
Reporting Sequence: You can modify the sort order parameters to change
the sequence of the report produced to virtually any data field the records being
processed.
Report Selection/Processing Options

Each report contains a section with the options appropriate for its processing. In
this section of data items, the DEFINE statements are preloaded with default
values. You can change these values to affect the options in effect for the
report execution. The individual options are listed in each of the report module
descriptions. Remember that any line beginning in an asterisk (*) is a comment,
and not part of the program functions.
Data Selection Filtering

Each report contains a section where the data read from the history is filtered
against the values in the previously defined table to determine what data to
select from history and how it should be processed based on the predefined
functions. In most cases, the changes made in the preceding section should be
sufficient, but these functions can be expanded by changing the source code in
this section accordingly.
Reporting Sequence
Each report module either has a section in which the report sequence is
explicitly requested by a SORT command or implicitly requested by a
SEQUENCE statement in the actual definition of the physical report layout, but
not both in the same module. In either case, the fields selected as sort control
can literally be any field defined in the records being processed.

Report Categories
Each of the four reporting modules produce 2 one-page reports in addition to
the primary detail report for which they are provided.
Processing Options: This one-page report shows what data was provided in
the Report Selection/Processing Options section of the module. Each value is
validated and shown on this report along with any errors, which will require
corrective action. Any errors found are shown immediately under the offending
data line with an indication of *** ERROR along with an explanation of the
problem detected. All errors found are shown, and any one of the shown errors
halts execution. A correction can then be made, and the job resubmitted. Any
additions or modifications to the processing code of the report module must
consider this error/validation processing, or the report results could be
adversely affected.
Report Totals: This one-page report shows the amount and type of data being
read from the database and how much of that read data is actually selected by
the filtering/selection process for reporting. This report is provided as volume or
performance information, and like the preceding report, needs to be considered
if modifying the code in the report modules.
Detail Reports: These reports show the data specific to that report as
enumerated in the preceding 2 one-page reports. Each detail report is
discussed in the following topics and consists of the following reports:
■ DISPLAY SCHEDULE JOB REPORT is intended to show all the event data
on the current schedule. All dependencies flags and associated predecessor
and successor jobs are included along with data reflecting current status.
■ LIST SCHEDULE JOB REPORT is intended to show all the event data on
the checkpoint.
■ LIST IPL REPORT is intended to show all the IPL records captured when
optionally created during startup of the system.
■ LIST AUDIT REPORT is intended to show all the changes captured when
controlled fields on the checkpoint have been modified by a user action.
History Reporting
History Reporting
The checkpoint database contains all the data used in these detail reports, both
for history and the current schedule. The checkpoint database resides in a
CA-Datacom/AD database, and the data within is accessible by numerous
indexing keys. While the history is on the same physical file, it is kept logically
separate by the use of these index keys. The checkpoint data is managed by
two history management utilities, which should be used on a regular basis to
control the growth of the checkpoint database.
■ History information is archived by the archive utility, GJTRJARC, which
selectively searches the active data and logically reassigns it to history
status, thus removing it from the active schedule. For more information
about this process and its reporting, see “About the GJTRJARC Utility” on
page 62.
■ History information is eliminated by the Purge Utility, GJTRJPRG, which
selectively searches data that has been archived and deletes it from the
database. For more information about this process and its reporting, see
“Deleting Archived Records with GJTRJPRG” on page 70.
If you are using Unicenter CA-11, see the Unicenter CA-11 Restart and
Tracking User Guide for a description of available reports concerning restart.
In the selection criteria of data for each report that follows, all the criteria
chosen must be met for the data item to participate in the report.

History Reporting
Display Schedule Report (Module GJTREZJW)

This report is intended to produce a working document from the selected
checkpoint database showing the current scheduled jobs, which assumes no
history is selected. But since it is a useful report format any of the data
available has been made optional. All dependencies, up to 14, are shown along
with all the associated predecessor and successor jobs. Additionally a section
of each schedule line can be reserved for manual remarks to allow this report
to be used as a tracking worksheet or other documentation of event processing.
The available keywords (with corresponding data fields in parentheses) for the
control of this report's content are as follows:
TOKEN (EVT1-F-TOKEN)
Defines the one-character Unicenter CA-Jobtrac system ID.
HISTORY INDICATOR (EVT1-F-HISTIND)
Specifies how to process history records in the report.
Y
Specifies history only.
N
Specifies no history.
*
Specifies both history and active.
JOB or EVENT NAME (EVT1-F-JOBNAME)
Defines 1 to 8 characters of a name or a name prefix ended by * as in *,
ABC*, or xyz123*.
LOCATION (EVT1-F-LOC)
(Optional) Defines a three-character location code.
Default: * (all locations)
BUSINESS GROUP (EVT1-F-BUSGRP)
(Optional) Defines a 1 to 8 character business group name or name prefix
in the same format as the JOB or EVENT NAME.
Default: * (all business groups)
COMPLETION CODE (EVT1-F-COMPCD)
(Optional) Defines a final Unicenter CA-Jobtrac-assigned completion or * for
all.
Default: * (all)
ABNORMAL
Specifies abnormal ends; shown as (1).
CATLG
Specifies catalog problems (1).
History Reporting
FORCED
Specifies forced completion (1).
CCnn
Specifies maximum completion code nn on a job step.
JCL
Specifies JCL fail (1).
PURGED
Specifies manually purged (1).
SYSTEM
Specifies system failures, Shhh ended (1).
S/hhh
Specifies specific system failure hhh (1).
Unnnn
Specifies specific user end nnnn.
NORMAL
Specifies any non-(1) end.
REMARKS
(Optional) Defines 0 to 20 lines of remarks lines.
Default: 4 lines
DATE FORMAT (EVT1-F-DATEFMT)
Specifies the format of printed dates:
I
Specifies the international format of YYYY/DD/MM.
A
Specifies the American format of YYYY/MM/DD.
The following optional parameters are combinations of FROM and THRU limits
for selection of data meeting all the preceding selection criteria. Any date field
can be TODAY or * that is treated as today's date (the date of the report
execution). Leaving the field blank is treated as choosing any date/time. Date
formats are yyyy/mm/dd. Time formats are hh:mm:ss.
OSD (EVT1-F-OSDFDAT, EVT1-F-OSDTDAT)
Specifies original schedule date from and through.
START (EVT1-F-STRFDAT, EVT1-F-STRFTIM, EVT1-F-STRTDAT,
EVT1-F-STRTTIM)
Specifies actual start date and time, from and through.
SUBMIT (EVT1-F-SUBFDAT, EVT1-F-SUBFTIM, EVT1-F-SUBTDAT,
EVT1-F-SUBTTIM)
Specifies submitted date and time, from and through.

History Reporting
END (EVT1-F-ENDFDAT, EVT1-F-ENDFTIM, EVT1-F-ENDTDAT,

EVT1-F-ENDTTIM)
Specifies job end date and time, from and through.
TARGET (EVT1-F-TGTFDAT, EVT1-F-TGTFTIM, EVT1-F-TGTTDAT,
EVT1-F-TGTTTIM)
Specifies target scheduled date and time, from and through. The FROM
date and time can specify ASAP to select those events that were
designated with an ASAP.
ARCHIVE (EVT1-F-ARCFDAT, EVT1-F-ARCFTIM, EVT1-F-ARCTDAT,
EVT1-F-ARCTTIM)
Specifies archive on date and time, from and through. This value is only
valid if the HISTORY INDICATOR is either Y or *.
The following are sample reports for the Display Schedule report
(CA-Easytrieve module GJTREZJW):
3/25/yy CA, INC. - JOBTRAC R11 REPORTING PAGE 1

GJTREZJW - DISPLAY SCHEDULE JOB REPORT PROCESSING OPTIONS

DATE TIME DATE TIME
SYSTEM TOKEN 4 - JOBTRAC SYSTEM IDENTIFICATION TOKEN
HISTORY FLAG - HISTORY AND/OR ACTIVE RECORDS CHOSEN
JOB/EVENT - JOB NAME OR EVENT NAME
LOCATION - LOCATION; MANAGERIAL DEFINITION
BUSINESS GROUP - BUSINESS GROUP; MANAGERIAL DEFINITION
COMPLETION CODE - COMPLETION CATEGORY OF FINAL DISPOSITION
REMARKS - UP TO 2 LINES OF REMARKS FOR EACH JOB/EVENT
DATE FORMAT A - AMERICAN OR INTERNATIONAL DATE FORMAT
OSD - ORIGINAL SCHEDULED DATE OF EVENT
STARTING - STARTING PERIOD OF EVENT
SUBMIT - SUBMIT PERIOD OF EVENT
ENDING - ENDING PERIOD OF EVENT
TARGET - TARGET SCHEDULED BEGINNING OF EVENT
HISTORY - EVENT STATUS MOVED TO HISTORY ARCHIVE
JTEZ1I - GJTREZJW; NO ERRORS DETECTED.

GJTREZJW - DISPLAY SCHEDULE JOB REPORT TOTALS; TOKEN: 4
TOTAL ACTIVE ARCHIVED TOTAL ACTIVE ARCHIVED

EVT EVT EVT PST PST PST
READ SELECTED SELECTED READ SELECTED SELECTED
195 143 52
History Reporting

GJTREZJW - DISPLAY SCHEDULE JOB REPORT; TOKEN: 4
H JOB / ORIGINAL VRSN JES ID COMP CURR SCHEDULE SYS PROCESS SUBMIT START END RUN LOC BUSINESS
S EVENT SCHED DATE CODE STAT DATE TIME ID PERD/FREQ DATE TIME DATE TIME DATE TIME TIME GROUP
T NAME DESC
Y AJO1 25/3/22 1 J6369 DELRQ TERM 3/22 18:5 XE79 D=USERB1 3/22 18:5 3/22 18:5 3/22 18:5 :<1 RJA1
Y GOBRUCE 25/3/22 1 J6368 DELRQ TERM 3/22 18:5 XE79 D=USERB1 3/22 18:5 3/22 18:5 3/22 18:5 :<1 RJA1
Y JOB5 25/3/25 1 DELRQ WMAN 3/25 13:8 D=USER11 OJO1
DEPENDENCIES: M
Y JOHN 25/3/24 1 J6258 DELRQ TERM 3/24 14:27 XE79 D=USER11 3/24 14:29 3/24 14:29 3/24 14:29 :<1 OJO1
N JOHN 25/3/24 1 WSCH 3/24 14:27 RR- OJO1
DEPENDENCIES: J
N JOHN1 25/3/24 1 J6289 U495 TERM 3/24 16:31 XE79 RR- 3/24 17:9 3/24 17:9 3/24 17:9 :<1 OJO1
N JOHN1 25/3/24 1 WSCH 3/24 16:31 RR- OJO1
DEPENDENCIES: J
Y JOHN1 25/3/24 1 J6282 DELRQ TERM 3/24 16:31 XE79 D=USER11 3/24 16:33 3/24 16:33 3/24 16:33 :<1 OJO1
Y JOHN1 25/3/24 1 J6286 DELRQ TERM 3/24 16:31 XE79 D=USER11 3/24 16:33 3/24 16:33 3/24 16:34 :1 OJO1
Y JOHN2 25/3/24 1 DELRQ TERM 3/24 18:12 D=USER11 3/24 18:12 :<1 OJO1
Y JOHN3 25/3/24 1 TERM 3/24 18:45 D=USER11 OJO1
DEPENDENCIES: J
Y JOHN3 25/3/24 1 J6298 U495 TERM 3/24 18:45 XE79 RR- 3/24 18:46 3/24 18:46 3/24 18:46 :<1 OJO1
Y JOHN3 25/3/24 1 J6295 U495 TERM 3/24 18:45 XE79 RQ-USER11 3/24 18:45 3/24 18:45 3/24 18:45 :<1 OJO1

GJTREZJW - DISPLAY SCHEDULE JOB REPORT; TOKEN: 4
H JOB / ORIGINAL VRSN JES ID COMP CURR SCHEDULE SYS PROCESS SUBMIT START END RUN LOC BUSINESS
S EVENT SCHED DATE CODE STAT DATE TIME ID PERD/FREQ DATE TIME DATE TIME DATE TIME TIME GROUP
T NAME DESC
N JOHN4 25/3/25 1 WSCH 3/25 11:52 RR- OJO1

DEPENDENCIES: D J M P ?
Y JOHN 25/3/25 1 J6325 MAXCC TERM 3/25 11:52 XE79 PREDESESSOR
Y JOHN1 25/3/25 1 J6325 MAXCC TERM 3/25 11:52 XE79 PREDESESSOR
Y JOHN8 25/3/25 1 J6325 MAXCC TERM 3/25 11:52 XE79 SUCCESSOR
Y JOHN9 25/3/25 1 J6325 MAXCC TERM 3/25 11:52 XE79 SUCCESSOR
+--------------------------------------------------------- R E M A R K S -------------------------------------------------+
+ EXAMPLE OF OPTION WORKSHEET REMARKS: REMARKS=4 +
+ +
+ +
+-------------------------------------------------------------------------------------------------------------------------+
Y JOHN4 25/3/25 1 J6325 MAXCC TERM 3/25 11:52 XE79 RR- 3/25 11:53 3/25 11:53 3/25 11:53 :<1 OJO1
+--------------------------------------------------------- R E M A R K S -------------------------------------------------+
+ +
+ +
+ +
+-------------------------------------------------------------------------------------------------------------------------+
Y JOHN4 25/3/25 1 J6324 MAXCC TERM 3/25 11:52 XE79 RR- 3/25 11:53 3/25 11:53 3/25 11:53 :<1 OJO1
+--------------------------------------------------------- R E M A R K S -------------------------------------------------+
+ +
+ +
+ +
+-------------------------------------------------------------------------------------------------------------------------+

History Reporting
List Schedule Report (Module GJTREZJS)

This report is intended to produce a report from the selected checkpoint
database showing all event data on the checkpoint.
TOKEN (EVT1-F-TOKEN)
HISTORY INDICATOR (EVT1-F-HISTIND)
Specifies how to process history records in the report.
Y
Specifies history only.
N
Specifies no history.
*
Specifies both history and active.
JOB or EVENT NAME (EVT1-F-JOBNAME)
ABC*, or xyz123*.
LOCATION (EVT1-F-LOC)
(Optional) Defines a three-character location code.
Default: * (all locations)
BUSINESS GROUP (EVT1-F-BUSGRP)
(Optional) Defines a 1 to 8 character business group name or name prefix
in the same format as the JOB or EVENT NAME.
Default: * (all business groups)
COMPLETION CODE (EVT1-F-COMPCD)
(Optional) Defines a final Unicenter CA-Jobtrac assigned completion or * for
all.
Default: * (all)
ABNORMAL
Specifies abnormal ends; shown as (1).
CATLG
Specifies catalog problems (1).
FORCED
Specifies forced completion (1).
CCnn
Specifies maximum completion code nn on a job step.
History Reporting
JCL
Specifies JCL fail (1).
PURGED
Specifies manually purged (1).
SYSTEM
Specifies system failures, Shhh ended (1).
S/hhh
Specifies specific system failure hhh (1).
Unnnn
Specifies specific user end nnnn.
NORMAL
Specifies any non-(1) end.
EVENT TYPE (EVT1-F-EVTTYPE)
(Optional) Specifies up to ten event type codes to select. Trailing blanks are
ignored. The values are as follows:
Default: * (all event types)
(blank)
Specifies a batch job.
C
Specifies a command.
D
Specifies a dummy job.
E
Specifies a remote REXX Proc.
I
Specifies a REXX IMOD.
N
Specifies NJE.
S
Specifies a schedule.
T
Specifies a task.
The following example would select all events:
EVT1-F-EVTTYPE =' '
The following example would select only batch jobs:
EVT1-F-EVTTYPE =' '

History Reporting
The following example would select commands, dummy jobs and remote
REXX PROCs (batch jobs would not be selected because the trailing
blanks are ignored):
EVT1-F-EVTTYPE ='CDE '
The following example would select batch jobs and dummy jobs (because a
blank indicating batch job is specified before a non-blank event code):
EVT1-F-EVTTYPE =' D '
DATE FORMAT (EVT1-F-DATEFMT)
I
A
The following optional parameters are combinations of FROM and THRU limits
for selection of data meeting all the preceding selection criteria. Any date field
can be TODAY or * that is treated as today's date (the date of the report
execution). Leaving the field blank is treated as choosing any date/time. Date
formats are yyyy/mm/dd. Time formats are hh:mm:ss.
OSD (EVT1-F-OSDFDAT, EVT1-F-OSDTDAT)
Specifies the original Schedule Date from and through.
START (EVT1-F-STRFDAT, EVT1-F-STRFTIM, EVT1-F-STRTDAT,
EVT1-F-STRTTIM)
Specifies the actual start date and time, from and through.
SUBMIT (EVT1-F-SUBFDAT, EVT1-F-SUBFTIM, EVT1-F-SUBTDAT,
EVT1-F-SUBTTIM)
Specifies the submitted date and time, from and through.
END (EVT1-F-ENDFDAT, EVT1-F-ENDFTIM, EVT1-F-ENDTDAT,
EVT1-F-ENDTTIM)
Specifies the job end date and time, from and through.
TARGET (EVT1-F-TGTFDAT, EVT1-F-TGTFTIM, EVT1-F-TGTTDAT,
EVT1-F-TGTTTIM)
Specifies the target scheduled date and time, from and through. The FROM
date and time can specify ASAP to select those events that were
designated with an ASAP.
ARCHIVE (EVT1-F-ARCFDAT, EVT1-F-ARCFTIM, EVT1-F-ARCTDAT,
EVT1-F-ARCTTIM)
Specifies the archive on date and time, from and through. This value is only
valid if the HISTORY INDICATOR is either Y or *.
History Reporting
The following are sample reports for the List Schedule report (CA-Easytrieve
module GJTREZJS):

GJTREZJS - LIST SCHEDULE JOB REPORT PROCESSING OPTIONS

DATE TIME DATE TIME
SYSTEM TOKEN Y - JOBTRAC SYSTEM IDENTIFICATION TOKEN
HISTORY FLAG - HISTORY AND/OR ACTIVE RECORDS CHOSEN
JOB/EVENT - JOB NAME OR EVENT NAME
LOCATION - LOCATION; MANAGERIAL DEFINITION
BUSINESS GROUP - BUSINESS GROUP; MANAGERIAL DEFINITION
COMPLETION CODE - COMPLETION CATEGORY OF FINAL DISPOSITION
EVENT TYPE(S) - TYPE OF EVENT
REPORT DATE FORMAT A - INTERNATIONAL OR AMERICAN DATE FORMAT
OSD - ORIGINAL SCHEDULED DATE OF EVENT
STARTING - STARTING PERIOD OF EVENT
SUBMIT - SUBMIT PERIOD OF EVENT
ENDING - ENDING PERIOD OF EVENT
TARGET - TARGET SCHEDULED BEGINNING OF EVENT
HISTORY - EVENT STATUS MOVED TO HISTORY ARCHIVE

History Reporting

GJTREZJS - LIST SCHEDULE JOB REPORT; TOKEN: Y
H T JOB / JES ID EVENT SCHEDULE ORIGINAL SYS COMPL CURR PROCESS SUBMIT START END RUN LOC BUSINESS
S Y EVENT VRSN DATE TIME SCHED DATE ID CODE STAT PERD/FREQ DATE TIME DATE TIME DATE TIME TIME GROUP
T P NAME NO DESC
4/3 : EST
Y APMPINF J 1 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : EST1
Y APMPINF J 2 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : EST
Y APMP1HIS J 1 4/3 : 26/4/3 .... NORML WMAN FOM 4/3 : EST1
Y APMP1HIS J 2 4/3 : 26/4/3 .... NORML WMAN FOM 4/3 : EST
Y APMP1INF J 1 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : EST1
Y APMP1INF J 2 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : EST
Y APMP1INM J 2 4/3 : 26/4/3 .... NORML WMAN FOM 4/3 : EST1
Y APMP2HIS J 1 4/3 : 26/4/3 .... NORML WMAN FOM 4/3 : EST
Y APMP2HIS J 2 4/3 : 26/4/3 .... NORML WMAN FOM 4/3 : EST1
N APMP2INF J 1 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : EST
N APMP2INF J 2 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : EST1
Y BDCDN95 J6161 34 12/29 : 25/12/29 X... NORML TERM DAILY 1/22 12:15 1/22 22:43 1/22 22:43 :<1 93
Y BDCDN98 J662 16 12/28 : 25/12/28 X... NORML TERM DAILY 1/26 18:48 1/26 18:48 1/26 18:48 :<1 93
Y BDCDO95 J678 4 12/31 : 25/12/31 X... NORML TERM M=BYPASS 1/26 22:27 1/26 22:27 1/26 22:27 :<1 93
Y BDCDO951 J6868 55 12/28 : 25/12/28 X... NORML TERM M=BYPASS 1/27 16:11 1/27 16:12 1/27 16:12 :<1 93
Y BDCDO952 J 1 9/28 : 25/9/28 .... NORML TERM DAILY 93
Y BDCDO953 J 1 9/28 : 25/9/28 .... NORML TERM DAILY 93
Y BDCDTXDL J6399 17 12/3 : 25/12/29 X... NORML TERM DAILY 1/22 12:15 1/22 23:2 1/22 23:2 :<1 93
Y BDCDT1 1 4/6 15:5 25/4/6 .... NORML TERM RQ-MISSING 4/6 15:9 4/6 15:9 4/6 15:9 :<1
Y BDCDXOP2 J6145 4 1/1 : 25/12/31 X... NORML TERM DAILY 1/2 19:22 1/2 2:9 1/2 2:9 :<1 93
Y BDCDX5 1 4/6 15:5 25/4/6 .... NORML TERM RQ-MISSING 4/6 15:1 4/6 15:1 4/6 15:1 :<1
Y BDCDX31 J6324 49 12/3 : 25/12/29 X... NORML TERM DAILY 1/22 12:15 1/22 21:47 1/22 21:47 :<1 93
N D BNADFLD1 DUMMY 4 12/31 : 25/12/31 .... NORML TERM =MTWTF.. 1/21 1:16 1/21 1:16 1/21 1:16 :<1 93
N D BNADFLD2 DUMMY 4 12/31 : 25/12/31 .... NORML TERM DAILY 1/21 1:16 1/21 1:16 1/21 1:16 :<1 93
Y BSJCP24 J17789 3 4/11 : 26/4/11 CA31 NORML TERM DAILY 4/11 1:53 4/11 1:53 4/11 1:53 :<1 SCP2
Y BSJCP24 J18143 4 4/11 : 26/4/11 CA31 NORML TERM DAILY 4/11 11:8 4/11 11:9 4/11 11:9 :<1 SCP2
Y C BSJXP15 COMMAND 1 1/18 : 26/1/18 .... NORML TERM RR-REMOT SXP5
Y C BSJXP15 COMMAND 2 1/18 : 26/1/18 C... NORML WEXE DAILY 1/18 8:15 1/18 8:16 1/18 8:16 :<1 SXP2
Y C BSJXP15 COMMAND 3 1/18 : 26/1/18 C... NORML WEXE DAILY 1/18 15:18 1/18 15:18 1/18 15:18 :<1 SXP2
Y GLMP1PYR J 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y D GLMP1RBD DUMMY 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y D GLMP1RBD DUMMY 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1SAC J 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1SAC J 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1SAS J 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1SAS J 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1SSJ J 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1SSJ J 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1STD J 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1STD J 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1UPD J 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1UPD J 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y D GLMP2COM DUMMY 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y D GLMP2COM DUMMY 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP2CYP J 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST

GJTREZJS - LIST SCHEDULE JOB REPORT TOTALS; TOKEN: Y
DESCRIPTION TOTAL
------------------------------ ---------
TOTAL RECORDS READ 13,61
ACTIVE RECORDS SELECTED 1,174
ARCHIVED RECORDS SELECTED 11,887
EVENT TYPE TOTALS:

(BLANK) - BATCH JOB 3,178
C - COMMAND 211
D - DUMMY JOB 9,657
E - REMOTE REXX PROC 11
I - REXX IMOD 3
History Reporting
List IPL Report (Module GJTREZIP)

This report is intended to produce a report from the selected IPL data on
checkpoint database showing all IPLs recorded.
TOKEN (IPL1-F-TOKEN)
SYSTEM ID (IPL1-F-SYSTEM)
Defines 1-4 characters of a system name or a name prefix ended by * as in
*, ABC*, or xyz1.
IPLED BY NAME (IPL1-F-IPLEDBY)
(Optional) Defines a 1-12 character operator name.
Default: * (all)
IPL TYPE (IPL1-F-IPLTYPE)
(Optional) Defines a one-character IPL code type.
Default: * (all)
C
Specifies a cold start IPL.
N
Specifies a normal IPL.
*
Specifies all.
IPL REASON (IPL1-F-IPLREASON)
(Optional) Defines a 1-39 character reason for the IPL. The reason can be
a character string ending in *.
Default: * (all)
IPLED (IPL1-F-IPLFDAT, IPL1-F-IPLFTIM, IPL1-F-IPLTDAT, IPL1-F-IPLTTIM)
Specifies a date and time of IPL optional parameters are FROM and THRU
limits for selection of data meeting all the preceding selection criteria. Any
date field can be TODAY or * that is treated as today's date (the date of the
report execution). Leaving the field blank is treated as choosing any
date/time. Date formats are yyyy/mm/dd. Time formats are hh:mm:ss.
DATE FORMAT (IPL1-F-DATEFMT)
I
A

History Reporting
The following are sample reports for the List IPL report (CA-Easytrieve module
GJTREZIP):

GJTREZIP - LIST IPL REPORT PROCESSING OPTIONS

DATE TIME DATE TIME
SYSTEM ID - SYSTEM IDENTIFICATION BEING IPLED
IPLED BY NAME - IPLED BY OPERATOR NAME
IPL TYPE - TYPE OF IPL PERFORMED
IPL REASON - REASON OR CAUSE REQUIRING IPL
IPLED - WHEN IPL OF JOBTRAC OCCURED
DATE FORMAT A - INTERNATIONAL OR AMERICAN DATE FORMAT
JTEZ1I - GJTREZIP; NO ERRORS DETECTED.

GJTREZIP - LIST IPL REPORT
T SYS OPERATOR IPL REASON IPLED IPL

O ID ID :-------------------------------------: DATE TIME TYPE
K
4 XE79 SMITH1 CAUSE BECAUSE SYSTEM FAILED 2yy/3/22 13:4:37 COLD

4 XE79 JONES2 REGULAR STARTUP 2yy/3/25 13:4:37 NORMAL

GJTREZIP - LIST IPL REPORT TOTALS

2 2
History Reporting
List Audit Report (Module GJTREZAU)

This report is intended to produce a report from the selected audit data on
checkpoint database showing all controlled changes made to checkpoint data.
TOKEN (AUD1-F-TOKEN)
JOB or EVENT NAME (AUD1-F-JOBNAME)
ABC*, or xyz123*.
USER ID (AUD1-F-USERID)
(Optional) Defines a 1 to 8 character operator name.
Default: * (all)
OSD (AUD1-F-OSDFDAT, AUD1-F-OSDTDAT)
Specifies the original schedule date from and through.
DATE FORMAT (AUD1-F-DATEFM)
I
A
AUDIT (AUD1-F-AUDFDAT, AUD1-F-AUDFTIM, AUD1-F-AUDTDAT,
AUD1-F-AUDTTIM)
(Optional) Defines a date and time of audited change. The parameters are
FROM and THRU limits for selection of data meeting all the preceding
selection criteria. These date fields can be TODAY or * that is treated as
today's date (the date of the report execution). Leaving the field blank is
treated as choosing any date/time. Date formats are yyyy/mm/dd. Time
formats are hh:mm:ss.
The following are sample reports for the List Audit report (CA-Easytrieve
module GJTREZAU):

History Reporting

GJTREAUD - LIST AUD REPORT PROCESSING OPTIONS

DATE TIME DATE TIME
JOB / EVENT NAME GOBRUCE - JOB OR EVENT NAME AUDITED
USER ID - USER ID MAKING CHANGE
DATE FORMAT A - INTERNATIONAL OR AMERICAN DATE FORMAT
CHANGE DATE/TIME - DATE / TIME FILE CHANGE WAS MADE
OSD - ORIGINAL SCHEDULE DATE OF JOB/EVENT
JTEZ1I - GJTREAUD; NO ERRORS DETECTED.

GJTREAUD - LIST AUDIT REPORT
T JOB/ ORIGINAL VRSN CHANGE OCCURRED USER ID DB SQL_FIELD_NAME BEFORE IMAGE/

O EVENT SCHED DATE DATE TIME TBL AFTER IMAGE
K NAME ID :------------------------------: :------------------------------:
4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:2:5 USERB1 SEV ISPF ADDED SEV +
4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:4:4 USERB1 EVT ISPF CHANGED EVT +
4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:4:4 USERB1 EVT DATE_STARTED + 1/1/

3/22/2yy
4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:4:4 USERB1 EVT MANUAL_DEPENDENCY + Y
N
4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:4:4 USERB1 EVT TIME_STARTED + ..
18.2.

3/22/2yy
N
18.22.

3/22/2yy
N
18.5.
4 GOBRUCE 2yy/3/22 1 2yy/3/22 19:18:54 USERB1 EVT ISPF DELETED EVT +
4 GOBRUCE 2yy/3/22 1 2yy/3/22 19:18:54 USERB1 EVT $AJ_REQUIRED + N
4 GOBRUCE 2yy/3/22 1 2yy/3/22 19:18:54 USERB1 EVT ABEND_SUB_SUCCS + N

GJTREAUD - LIST AUDIT REPORT TOTALS

11,585 154
Chapter 3. Maintenance
Product Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Performing Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Modifying the Sysout Capture File . . . . . . . . . . . . . . . . . . . . . . . . 67
Deleting Members from Temporary-Use JCL Libraries . . . . . . . . . . . . 68
Deleting Archived Records with GJTRJPRG . . . . . . . . . . . . . . . . . . 70
Chapter 3. Maintenance 33
Product Maintenance
Product Maintenance
The Unicenter CA-Jobtrac tasks and utilities offer the following capabilities:
■ Access to information on the current schedule from a batch job
■ Current schedule event archival
■ Sysout capture file archival
■ Modification to the sysout capture file
■ Deletion of members from the temporary-use JCL libraries
■ Deletion of records from the Unicenter CA-Jobtrac history database
Unicenter CA-Jobtrac offers the following maintenance utilities and tasks:
Function Task or Utility

Maintain the current schedule through GJTRABTR utility
a batch job
Event archival 0JOBARCH task, 0ARCHIVE task, or
GJTRJARC utility
Sysout archival 0SYSARCH task or 0ARCHIVE task
Reload sysout archival GJTRVRLD utility
Modifying the sysout capture file GJTRVFMT utility
Deleting members from the GJTRMAJC utility
temporary-use JCL libraries
Deleting records from the Unicenter GJTRJPRG utility
CA-Jobtrac history database
Backup and recovery PROCs using
CA-Datacom/AD utilities
The Unicenter CA-Jobtrac tasks (0JOBARCH, 0SYSARCH, and 0ARCHIVE)

cannot run at the same time.
We recommend that you load no SCLs during a 0JOBARCH as it may affect

performance.

Product Maintenance
If Unicenter CA-Jobtrac is shut down, canceled, or abends, and one of the

Unicenter CA-Jobtrac tasks is running, the task is marked ABENDED=SYS
DOW when Unicenter CA-Jobtrac is brought back up.
These tasks will have a 'J' dependency that needs to be removed so that they
can execute. They also appear on an exceptions display.
Accessing the Current Schedule

The GJTRABTR utility provides a batch method for querying and updating the
current schedule. You can do any of the following:
■ Query the system
■ Issue abend codes
■ Add an event to the current schedule
■ Update information on the current schedule
■ Delete or purge an event on the current schedule
■ Specify conditions that must be met before any of the above actions are
taken
To use the GJTRABTR utility, you invoke the GJTRABTR program and specify
commands to perform required actions.
GJTRABTR and @JOBTRAC use the @JOBTRAC facility to access the current
schedule. The two features use most of the same commands. The primary
differences between the two features is how they use the commands to access
the current schedule.
GJTRABTR uses the commands in a batch job and the @JOBTRAC facility
executes the commands. GJTRABTR can also use CA-GSS (Global
SubSystem) to access other subsystems or to execute an IMOD. GJTRABTR
gives you the advantage of executing as a step of a batch job.
@JOBTRAC uses the commands in IMODs. CA-GSS executes the IMODs and
the @JOBTRAC facility executes the commands. @JOBTRAC has the
advantage of giving you the power of REXX.
Product Maintenance
You can use GJTRABTR any time you want to perform some action through a
batch job, TSO CLIST, or online transaction. Some possible applications follow:
■ To cause an event to abend when a defined condition code occurs.
■ To interact with Unicenter CA-Jobtrac without accessing the Unicenter
CA-Jobtrac ISPF interface.
■ To test certain modifications to the current schedule.
You can use GJTRABTR to perform any of the following actions:

■ Add an event to the current schedule.
■ Modify the schedule information for an event on the current schedule.
■ Delete an event from the current schedule.
■ Purge an event from the current schedule and remove one predecessor
dependency from each of its successors.
You can invoke GJTRABTR using any of the following methods. Unicenter
CA-Jobtrac does not have to be running to use GJTRABTR.
■ Coding JCL to invoke the GJTRABTR program. The JCL can be submitted
either in batch or by Unicenter CA-Jobtrac.
■ Creating a TSO CLIST (command list) or other user program.
■ Performing an online transaction (for example, using the TSO CALL
command).
Each method requires you to specify parameters to perform the actions you
want.
When you modify, delete, purge, or search for an event, you might want to
uniquely identify the event. You can uniquely identify an event by specifying the
following parameters with a command:
■ JOBname
■ DATE
■ Version (or .vv in the JOBname parameter)

Product Maintenance
Using GJTRABTR
Using typical JCL, you invoke the GJTRABTR utility. Within the JCL you specify
a GJTRABTR command or commands. GJTRABTR sends the commands to
the @JOBTRAC facility to execute the commands.
The @JOBTRAC facility returns information about an event that is on the

current schedule. The information is placed in SYSPRINT. The returned
information is described in “Information Returned by GJTRABTR” on page 40.
If you specify multiple commands, SYSPRINT contains the returned information
in the order you requested it.
A command's parameters define an event or qualify the search for an event.

For example, the Add command uses the information to define an event, while
the DELete command uses the information to find an event and delete it.
“GJTRABTR Commands” on page 52 starts the descriptions of the GJTRABTR
commands and parameters.
GJTRABTR provides the following methods for specifying commands. You can
use one or both of them in a job.
Method Example
PARM statement IBM JCL restrictions limit GJTRABTR parameters to
100 characters, including punctuation.
//AB1 EXEC PGM=GJTRABTR,
// PARM='ADD(JOB(TESTJOB3),DEP(M))'
// PARM='A(JOB(TESTJ3),DEP(M?)) Q(JOB(TEST))'
// PARM='POST(JOB(TESTJ11),S(TESTJOB4))'
// PARM='PRG(JOB(TESTJOB),V(11))'
// PARM='Q(JOB(TESTJOB),V(2))'
// PARM='Query(JOB(TESTJOB3),S(TESTJOB4))'
STACK command //AB3 EXEC PGM=GJTRABTR,
and SYSIN // PARM='STACK()'
//SYSIN DD
ADD(JOB(TESTJOB3),DEP(M)) Q(JOB(TEST))
PRG(JOB(TESTJOB),V(11))
ADD(JOB(TESTJ3),DEP(M?))
POST(JOB(TESTJ11),S(TESTJOB4))
Q(JOB(TESTJOB),V(2))
Query(JOB(TESTJOB3),S(TESTJOB4))
With either method you can specify one or more commands at a time.
Follow all standard JCL syntax rules for parameters. Any syntax error in
parameters results in a message.
Product Maintenance
Using the STACK Command: GJTRABTR can use a stack to collect

commands and command parameters. You put information onto the stack
using SYSIN. You can put up to 100 input lines onto the stack. You use the
STACK command to instruct GJTRABTR to use the information in the stack.
You can use the STACK command alone or with other commands. You can
even start a command in the PARM statement and finish it in the stack.
A SYSIN line can contain an entire command or any portion of a command. In

this way, you can specify a large number of commands or commands with
numerous parameters that might otherwise be too long to specify because of
JCL line length restrictions. It is important to keep in mind the syntax of the
GJTRABTR commands when placing information on the stack. If you omit a
necessary parenthesis you will receive an error.
The information in the stack is used as needed. So, if in the PARM statement
you start a command, but GJTRABTR does not find the ending parenthesis, it
will take information from the stack until it encounters the ending parenthesis. If
a new command is not started in the PARM statement after reading the first
one, GJTRABTR again takes information from the stack.
Using the Stack: Example 1
/AB3 EXEC PGM=GJTRABTR,

// PARM='STACK(1) Get (JOB(A)'
//SYSIN DD
Ver (2))
Same as

// PARM='Get (JOB(A) Ver(2))'
Notice the parameter put in the stack contained the ending parenthesis for the
Get command. It tells GJTRABTR the input is done. Without it, you would
receive a syntax error.
The beginning parenthesis (before JOB) is also necessary. It tells GJTRABTR

to read the next line from the stack as part of the Get command. Without it,
GJTRABTR would read the next line from the stack as a new command, and
you would receive an error.

Product Maintenance
Using the Stack: Example 2

// PARM='STACK()'
//SYSIN DD
Get (JOB(C)
STAT(AB))
Add JOB D DATE 7/27
Query JOB ABC
All three commands are sent at one time. The stack would return the following:
■ Information about event C, if any was found, with a return code indicating
the success of obtaining information about event C.
■ A return code indicating the success of adding event D.
■ A return code indicating the success of finding event ABC.
GJTRABTR Produced WTO: GJTRABTR produces a WTO for each command

that successfully changes the Unicenter CA-Jobtrac checkpoint (return code of
zero).
This WTO has the following format:
ABTR JOBTRACx EVENT name.vvv (date) action BY userid.
x
Defines the Unicenter CA-Jobtrac subsystem where the action occurred.
name
Defines the name of the event affected.
vvv
Defines the version number of the event affected.
date
Defines the original schedule date for the event.
action
Defines the type of modification made: MODIFIED, DELETED, ADDED,
PURGED.
userid
Defines the user ID of the person or job making the modification.
Product Maintenance
Information Returned by GJTRABTR: GJTRABTR returns information on the

stack. The information is placed in SYSPRINT. For each GJTRABTR job, the
following is contained in SYSPRINT:
INPUT:
Exact contents of SYSIN.
ARG:
The contents of the PARM statement that is passed to the @JOBTRAC
facility.
RESULT:
Information returned by an IMOD if executing an IMOD.
OUTPUT:
■ GJTRABTR messages.
■ Obtained by GJTRABTR (one set per input command) is placed on the
stack. If you specified SYSPRINT, the information in the stack is sent to
SYSPRINT.
– A 4-byte prefix identifies each piece of information returned. The
table in “Stack Prefixes and Information” on page 41 describes the
prefixes and information. All information is returned as characters.
– When using the Get command, you can obtain any or all of the
information shown in the table. All other GJTRABTR commands
return the RC information only. Additionally, the MSG information
can be returned at any time.
– With the exception of the MSG and RC information, the information
is returned in alphabetical order. The MSG information is returned
as necessary. The RC information is always returned last. The
following table is arranged in alphabetical order except MSG and
RC, which are at the end of the table.

Product Maintenance
Stack Prefixes and Information: The following information is returned on the

stack:
AMEM
Identifies the name of an alternate member in the JCL library that runs for
this event instead of the member whose name matches the event's name.
ATIM
Identifies the abort time and date for the event. Returns the information in
the hh:mm mm/dd format including the colon and slash.
BSGP Identifies the name of the business group or schedule ID assigned
to the event.
CMPC
Identifies the for completed events, how the event completed as described
in the following list.
Code Explanation
OK Indicates the event ended typically.
SAccc Indicates the event ended with a system abend. The abend
code is denoted by ccc.
UAccc Indicates the event ended with a user abend. The abend code
is denoted by ccc.
PU Indicates the event was purged from the input queue.
FO Indicates the event was forced to completion by a user.
JC Indicates the event had a JCL error.
SCnn Indicates the event exceeded its maximum condition code. The
step within which the condition code was exceeded is denoted
by nn.
CR Indicates a system crash occurred.
nnnn Indicates some other return code.
DATE
Identifies the date the event was originally put on the current schedule.
Returns mm/dd format including the slash.
DCNT
Identifies the data set count associated with the event.
DEP
Identifies the dependency codes if the event has any. Each code is
separated by a blank.
Product Maintenance
IDEP
Identifies the name of an environmental dependency the event has. There
is one field for each environmental dependency the event has. Each field
contains the environmental dependency name, its status, and an argument
if it has one. The status determines additional information contained in the
field as shown in the following table. The ID is assigned when the IMOD
Facility runs the IMOD.
Status Meaning (and Additional Information)
W Indicates waiting (retry count and retry interval.).
A Indicates abended (ID and a placeholder of a period.).
T Indicates terminated OK.
E Indicates executing.
For example:
IDEP ABCTEST W 23 1: START
IDEP XYZTEST T 72 .
IDEP AIH E 1 . END
JCNT
Identifies the job count associated with the event.
JENT
Identifies the actual end time of the event if the event already ended.
Returns the information in the hh:mm mm/dd format, including the colon
and slash.
JES#
Identifies the JES job number assigned if the event was submitted.
JOBN
Identifies the name of the event.
JSTT
Identifies the actual start time of the event if the event already started.
JLOC
Identifies the location ID assigned to the event.
JMAXC
Identifies the maximum condition code assigned to the event.
NJE
Identifies whether this event is an NJE job that has been submitted to
another JES node, the JES node name on which the event is executing or
has executed. Otherwise, this is blank.
NODE
Identifies the 16-character name of either the OS/390 GoalNet node or the
CAICCI node name for a scheduler or an agent where the event is
executing or has executed.

Product Maintenance
ONQU
Identifies whether this is an AUTO-SCHD event, indicates the event has
been submitted and recognized by Unicenter CA-Jobtrac. Otherwise, this is
blank.
PRED
Identifies the name of a predecessor the event has. There is one stack line
for each predecessor the event has. Each line contains the predecessor
name followed by the version number of the predecessor, original schedule
date, and a flag. The flag is set to C for completed and N for not
completed. For example:
PRED ABC 2 2/24 C
PRED AIH 2 2/24 C
PRED XYZ 2 2/25 N
PROP
Identifies the processing period for the event.
REXP
Identifies the argument passed to the event if this event is a REXX IMOD
and it has an argument associated with it.
RSMG
Identifies the resource codes associated with the event. Each code can be
either 1 or 2 characters in length. Each code is separated by a blank.
Note: This changed in Release 3.5.
STAT
Identifies the status of the event is as follows:
AB Abended
AG Performing post-abend tasks, such as executing a termination
IMOD
CC Condition code error
CG Performing post-condition code error tasks, such as capturing
sysout
DP Waiting for dependencies to be satisfied
EX Executing
HQ Waiting for dependencies, process period, or schedule time
requirements to be satisfied
OQ On the JES queue awaiting submission
TG Performing post-termination tasks, such as capturing sysout
TM Terminated, all post-termination tasks are completed
STIM
Identifies the scheduled start time and date for the event. Returns the
information in the hh:mm mm/dd format including the colon and slash.
Product Maintenance
STPC
Identifies the step condition codes assigned to the event. There is one
stack line for each step condition code the event has. Each field contains
the relative step number followed by the logical operator and condition
code used. Possible logical operators are:
LT
Less than
GT
Greater than
EQ
Equal to
LE
Less than or equal to
For example:
STPC 1 LT 5
STPC 1 EQ
SUBT
Identifies the actual time and date the event is submitted for execution by
Unicenter CA-Jobtrac. Returns the information in hh:mm mm/dd format,
including the colon and slash.
SUCC
Identifies the name of a successor the event has. There is one field for
each successor the event has. Each field contains the successor name
followed by the version number of the successor and the original schedule
date. For example:
SUCC ABC 2 11/1
SUCC AIH 2 11/22
SUCC XYZ 2 11/28
SYSI
Identifies the system ID to which the event was submitted.
TJCL
Identifies the name of a member in the temporary-use JCL library that runs
for this event instead of the production JCL.
TTIM
Identifies the target time and date for the event. Returns the information in
the hh:mm mm/dd format, including the colon and slash.

Product Maintenance
TYPE
Identifies the type of event. Possible values are:
IMOD
Indicates a REXX IMOD.
DUMMY
Indicates a dummy job.
JOB
Indicates a batch job.
C-RMT
Indicates a command to be executed at a particular remote node.
VER
Identifies the version number of the event.
MSG
Identifies a message up to 80 characters in length.
RC
Identifies a 4-character return code denoting the success or failure of the
Query command.
Product Maintenance
RC Explained: The RC information is returned in the following format:
RC rrrr mmmm ffff jjjjjjjj ddddd vvvvv lll ss cc y
The following explains the variables. If a specific variable is missing, a period (.)
is used as a placeholder. For example, Get(JOB(ABC) Ver(2)) could result in
RC 0004 CUUS GET ABC . 0002 . . ., meaning the original schedule date,
location, status, and completion code information is missing.
rrrr
Specifies a return code as follows:
0000
TRUE
0004
Event name specified by the command was found, but the specific test
was FALSE
0008
Event name specified by the command was not found
Greater than 0008
Some error occurred
mmmm
Specifies the name of the module setting the return code. For example,
SPRS or CUUS. If it is SPRS, this is a parsing error. If it is CUUS, use rrrr
to determine the meaning.
ffff
Specifies the command being performed. For example, Get or DELete.
jjjjjjjj
Specifies the event's name.
ddddd
Specifies the original schedule date of the event in the format mm/dd,
including the slash.
vvvvv
Specifies the version number of the event.
lll
Specifies the location of the event.

Product Maintenance
ss
Indicates the status of the event is as follows:
AB
Abended
AG
Performing post-abend tasks, such as executing a termination IMOD
CC
Condition code error
CG
Performing post-condition code error tasks, such as capturing sysout
DP
Waiting for dependencies to be satisfied
EX
Executing
HQ
Waiting for dependencies, process period, or schedule time
requirements to be satisfied
OQ
On the JES queue awaiting submission
TG
Performing post-termination tasks, such as capturing sysout
TM
Terminated, all post-termination tasks are completed
cc
Specifies the event's completion code.
y
Indicates the Unicenter CA-Jobtrac subsystem code identifying on which the
Unicenter CA-Jobtrac system runs.
Product Maintenance
GJTRABTR Command Syntax

The following syntax rules apply to the GJTRABTR commands:
■ Parentheses are required in the following situations. Other uses of indicated
parentheses are optional.
– Parentheses enclosing command parameters if specifying multiple
GJTRABTR commands in one PARM, whether in the stack or not.
– Parentheses enclosing command parameters if splitting input across
stacked lines.
– Parentheses enclosing parameter values if specifying multiple values.
– Parentheses following the STACK command if another command
follows it or if not specifying the number of lines (defaulting to all lines in
the stack).
■ Separate commands with a blank or a comma. You can use any number of
blanks, but only one comma.
■ Separate parameters with a blank or a comma. You can use any number of
blanks, but only one comma. The exception to this is parameters containing
periods (.). For example, the vv and L= parameters. You must use these as
shown in the syntax.
■ The syntax is free-form. Specify command parameters in any order.
Note: For more information about reading syntax diagrams, see the Operator
Guide.

Product Maintenance
This command has the following format:
┌─,──┐
parm┴──)─────────────────────────────────────────────
──command──(───
command
Identifies a GJTRABTR command.
parm
Identifies parameters that serve to qualify the command. You can use
multiple parameters, including multiples of the same parameter.
The following table explains the contents of the cells in the command summary
table:
Content Parameter is . . .
Not used with the command.
* Used with the command.
** Used with the command, but it identifies an event only.
You cannot change the information.
Additionally, the ABEND and END commands do not use any parameters.
Product Maintenance
Command Summary: The following table summarizes the GJTRABTR

commands and parameters and indicates which parameters you can use with
which commands:
Ad D D G I I J M N P Q S (See page 52 for

d E U e M s T OP o UP u T commands.)
L M t o e s DO d RR e A
(For parameters, see
P d r y I S e gG r C
the @JOBTRAC
v s f T e y K
parameters in the
e y
Extended Scheduling
Services Guide.)
* * ATime (time [date])
* * ** ** * * ** BUSGrp (bgrp-name)
* ** ** * * ** COMPLETION_Code
(code)
** ** ** ** ** CURPP (processp)
* * ** ** ** * ** DATE (org_schd_date)
* * ** ** * * ** DCNT (count)
* * ** ** * * ** Dependency ([action]
{deps})
* * END_TIME (time [date])
* * GSS_Node (nodename)
* * IDEP
([ac]name[.rc[.ri[.arg]]]...)
* * JCL_Member (amem)
* * ** ** * * ** JCNT (count)
* * JES_Node (nodename)
* * ** ** ** * ** JOBname
(eventname[.vv][,L=nnn])
* * ** ** * * ** JOB_Number (number)
* * ** ** * * ** JOBPP (processp)
* * ** ** ** * ** Location (nnn)
* * MAXCc ({NA|}nnnn})
* * NJE (yn)
* * ONQueue (yn)
* * Predecessor
([ac]name[.vv[.date]]...)

Product Maintenance
Ad D D G I I J M N P Q S (See page 52 for

d E U e M s T OP o UP u T commands.)
L M t o e s DO d RR e A
(For parameters, see
P d r y I S e gG r C
the @JOBTRAC
v s f T e y K
parameters in the
e y
Extended Scheduling
Services Guide.)
* * REXX_Parms (argument)
* * ** ** * * ** RMG (x ...)
* * ** ** * * ** STATus (stats)
* * STEPCc ({NA|}stnum
logop cccc...)
* * STime (time [date])
** ** ** ** ** ** ** SUBsystem (n)
* * SUB_Time (time [date])
* * Successors
([ac]name[.vv[.date]]...)
* * ** ** * * ** SYSTEM_id (sysid)
* * TJCL (tmem)
* * TTime (time [date])
* * ** ** * * ** TYPE (etype)
* * ** ** ** * ** Version (vv)
** (imodname) (see “IMod
Command” on page 53)
** (iservename) (see “Iserve
** (jtsyschar) (see “JTsys
** (nodename) (see “Node
** ([numlines]) (see “STACK
* Used with the command.

** Used with the command, but it identifies an event only. You cannot change
the information.
Product Maintenance
GJTRABTR Commands
GJTRABTR provides several valid commands that enable you to communicate
with the current schedule. The commands are in jobs that invoke GJTRABTR.
The commands are:
ABEND
Add
DELete
DUMP
END
Get
IMod
Iserve
JTsys or Token
MODify or POST
Node
PURge or PRG
Query
STACK
ABEND Command
The ABEND command frees the address environment's resources and

produces a dump.
The ABEND command produces a SOC3-type abend.
Add Command
The Add command adds the event to the current schedule. Parameters you
specify define the event (except SUBsystem). Default values are used for
parameters you do not specify.
If you specify dependency code R or X with the Dependency parameter, they

are ignored.
DELete Command
The DELete command deletes an event from the current schedule. Parameters
you specify serve as search criteria. The first event on the current schedule that
matches the search criteria is deleted.

Product Maintenance
DUMP Command
The DUMP command searches the current schedule for an event and returns
information. The returned information is in typical IBM dump format showing
offsets, hexadecimal values, and character values.
Parameters you specify serve as search criteria. The information returned is for
the first event on the current schedule that matches the parameters. Dump lines
are returned in the stack, which are written to SYSPRINT, and are identified by
the MSG prefix.
END Command
The END command frees the address environment's resources. The next
GJTRABTR command reinitializes the address environment.
This is used with the Node, Iserve, and Imod commands only.
Get Command
The Get command searches the current schedule for an event and returns
information. Parameters you specify serve as search criteria. The information
returned is for the first event on the current schedule that matches the
parameters.
IMod Command
The IMod command executes the named REXX IMOD. The commands
specified in the GJTRABTR job are passed to the IMOD for its use. When the
GJTRABTR job is done, any information remaining in the stack goes to
SYSPRINT.
The IMod command must be specified before other commands (except the
Iserve, JTsys, or Node commands).
Using the IMod command invokes the use of CA-GSS. CA-GSS executes the
equivalent GJTRABTR commands in the CA-GSS address space.
──IMod(imodname)────────────────────────────────────────────────────
imodname
Defines a REXX IMOD name.
Limits: 1 to 16 characters
Product Maintenance
Iserve Command
The Iserve command specifies an ISERVE name. It identifies the CA-GSS

subsystem to which you want to submit the GJTRABTR commands specified in
the job. While the request is directed to this subsystem, it might not run here.
This is because if the Node command is used, it takes precedence over the
Iserve command.
The Iserve command must be specified before other commands (except the
IMod, JTsys, or Node commands).
Using the Iserve command invokes the use of CA-GSS. CA-GSS executes the
If you are using Iserve or Node command, and have multiple Unicenter
CA-Jobtracs running in the subsystem or this is an NJE job, the checkpoint
used is determined in this order
1. The SUBsystem parameter specification
2. The first Unicenter CA-Jobtrac started
3. The default primary Unicenter CA-Jobtrac
──Iserve(─┬─iservename─┬─)──────────────────────────────────────────
└───────────┘
iservname
Defines a subsystem name.
*
Indicates to submit the request to the default subsystem named in the
Unicenter CA-Jobtrac global options.

Product Maintenance
JTsys Command
The JTsys command identifies the Unicenter CA-Jobtrac system you want to
use. x is the variable used in the Unicenter CA-Jobtrac checkpoint name to
distinguish multiple Unicenter CA-Jobtracs. This command identifies a Unicenter
CA-Jobtrac system that is running in the subsystem to which you submitted the
GJTRABTR job. You cannot specify a Unicenter CA-Jobtrac system in another
subsystem without using the Iserve or Node command.
The JTsys command must be specified before other commands (except the
IMod, Iserve, or Node commands).
──┬─JTsys─┬──(x)────────────────────────────────────────────────────
└─Token─┘
x
Defines a Unicenter CA-Jobtrac system variable.
Limits: 1 character. If you omit this command, the default primary
Unicenter CA-Jobtrac system in the subsystem is used.
MODify or POST Command
The MODify command updates an event on the current schedule. Parameters

you specify replace or define the information in the event's definition. The
DATE, JOBname, Location, SUBsystem, and Version parameters are used to
identify the event only. They cannot be defined or replaced.
The first event on the current schedule that matches the search criteria is
modified.
You cannot specify dependency code R or X with the Dependency parameter.
Product Maintenance
Node Command
The Iserve command specifies a node name. It identifies the CA-GSS

subsystem to which you want to submit the GJTRABTR commands specified in
the job.
The Node command must be specified before other commands (except the
IMod, Iserve, or JTsys commands).
Using the Node command invokes the use of CA-GSS. CA-GSS executes the
──Node(nodename)────────────────────────────────────────────────────
nodename
Defines a node name.
PURge or PRG Command
The PURge command purges the event from the current schedule, and
removes the predecessor dependency from its successors. Parameters you
specify serve as search criteria. The first event on the current schedule that
matches the search criteria is purged.

Product Maintenance
Query Command
The Query command searches the current schedule for the existence of the
specified event. If you specify parameters (other than the event name), they
determine the exact definitions the event must have to satisfy the search. The
first event on the current schedule that matches the parameters satisfies the
search.
The Query command returns a return code only. It is identified by the RC prefix
in the stack.
STACK Command
The STACK command specifies the number of lines (numlines) to use from the
stack. The stack should contain GJTRABTR commands and parameters to be
processed. If placing multiple parameters for a command on the stack, be sure
to include the command's required parentheses or you will receive a syntax
error. Using the stack is the only way to specify a large number of parameters
with a command.
If you do not specify numlines, all the information in the stack is used.
Information is put onto the stack using SYSIN.
──STACK──(──┬─ALL──────┬──)─────────────────────────────────────────
└─numlines─┘
numlines
Defines the number of lines of information on the stack for GJTRABTR.
Limits: 1 to 100
Default: All information in the stack
Product Maintenance
GJTRATBR Command Parameters

You can invoke GJTRABTR processing by coding JCL or using a CLIST.
Note: For GJTRATBR command parameters, see the parameter descriptions
for the @JOBTRAC command in the Extended Scheduling Services Guide.
Coding JCL to Invoke GJTRABTR Processing

Use the following steps to code JCL invoking GJTRABTR processing to perform
the actions you specify.
1. Display the JCL member you want to code to invoke GJTRABTR so that
you can edit it.
2. Insert an EXEC statement invoking the GJTRABTR program (see the
following example).
3. Add the command or commands that perform the actions you want. Use a
PARM statement with or without SYSIN.
4. Optionally, insert a DD statement specifying the Unicenter CA-Jobtrac
checkpoint (current schedule) to access. If this is omitted, GJTRABTR uses
the default primary checkpoint. Some commands (Iserve, JTsys, and Node)
and a parameter (SUBsystem) override this default.
5. Insert a DD statement for SYSPRINT to receive output from the job.
Example: In the following figure, jobstep A1 invokes the GJTRABTR program.

Parameters to the GJTRABTR program are specified on the following two
continuation statements. Since no JOBTRACx statement is specified, your
default primary Unicenter CA-Jobtrac is used. The SYSUDUMP DD statement
assigns sysout class H for system dumps.
//GJTRABTR JOB ...

//A1 EXEC PGM=GJTRABTR,
// PARM=('ADD(JOB(TESTJOB3.31)','DEP(M)',
// 'S(TEST1,T1,TJX1,TESTJOB5))')
//SYSPRINT DD SYSOUT=
//

Product Maintenance
Example of a CLIST Invoking GJTRABTR

The following figure shows a CLIST that invokes the GJTRABTR program with
a parameter and two operands.
PROC 3 C V D
/ SAMPLE SYNTAX ADD(JOB(TESTJOB1),V(1),DEP(NONE) /
CALL 'your.CAILIB(GJTRABTR)' '&C,&V,&D'
Note: You must have the JOBTRACx and JOBHISTx data sets allocated to
your TSO session. You also need to have the program name GJTRABTR
added to the AUTHPGM table in the IKJTSOxx PARMLIB member.
Performing Archives
Performing Archives
Unicenter CA-Jobtrac offers the following archival abilities:
■ Clear completed events from the current schedule. This is referred to as
event history archival.
■ Archive the sysout capture file. This is referred to as sysout archival.
Event History Archival: At least once each work day, you should perform
event history archival (0JOBARCH or GJTRJARC PROC) to clear events from
the current schedule (Unicenter CA-Jobtrac checkpoint). Regular execution of
event history archival is important for smooth Unicenter CA-Jobtrac operation.
After an event is archived, you can display historical event information on the
Event History Display panel.
Note: For more information about the Event History Display panel, see the
Operator Guide.
Archived event records are retained for a specified period of time or number of
generations of each event. The time period and number of generations are
controlled by the GJTRJPRG utility (see “Deleting Archived Records with
GJTRJPRG” on page 70).
Sysout Archival: You should perform sysout archival to archive the sysout
capture file on a regular basis. Regular execution of sysout archival is important
for smooth Unicenter CA-Jobtrac operation.
During execution of the sysout archival, Unicenter CA-Jobtrac does not capture
any new sysouts. Once the archival is complete, sysout capture resumes.
After a sysout is archived, you can reload it for online review.

Note: For more information about managing sysouts, see the the Operator
Guide.
Actions Performed by Sysout Archival: During sysout archival, the following

actions are performed. The sysouts are archived, allowing you to archive
sysouts to tape or DASD.
■ You are prompted to mount a tape for the archival if the SYS OPTS option
is set.
Note: For more information about the SYS OPTS option, see the Planning
and Implementation Guide.
■ Sysouts not previously archived are dumped from the sysout capture file to
the archive tape.
■ The sysout archive index is updated.

Performing Archives
Methods of Executing the Archivals

Unicenter CA-Jobtrac offers a number of ways to perform event history archival
and sysout archival. There are several Unicenter CA-Jobtrac tasks and a utility.
Additionally, there are several ways to start the Unicenter CA-Jobtrac tasks or
utility.
Executing the Event History and Sysout Archival: You can perform event
history archival by using one of the following methods:
■ Invoking the GJTRJARC utility
■ Adding the 0ARCHIVE, 0JOBARCH, and 0SYSARCH task to the current
schedule using:
– A schedule
– The ADD command (the Event/Jobstream Addition panel)
– The RUN command
– The GJTRABTR utility
These tasks will produce a report listing all events on the current schedule
meeting specific criteria, by putting an 'O' next to the event on the status
display.
More information
“About the GJTRJARC Utility” on page 62
“Using GJTRABTR” on page 37

Note: For more information about other methods, see the Operator Guide.
The 0ARCHIVE task performs both the event history archival and the sysout
archival. The 0JOBARCH task performs only the event history archival. The
0SYSARCH task performs only the sysout archival.
Performing Archives
About the GJTRJARC Utility

The GJTRJARC utility provides a batch method for the following tasks:
■ Archiving event information from the current schedule to the history
database
■ Producing a report listing all events on the current schedule
■ Producing a report listing all events on the current schedule meeting
specific criteria
To use the GJTRJARC utility, you invoke the GJTRJARC PROC and specify
parameters to perform the required function.
The GJTRJARC PROC is located in the cai.CAIPROC data set. Update this
PROC with the correct DDs and token from the following table. You can run a
batch archival while still having Unicenter CA-Jobtrac process as usual. This is
accomplished by using the ARCH,C parameter with the GJTRJARC PROC and
the correct DDs.
The following explains the ddnames:

JOBTRACx
(Required) A dummy DD used to provide the system token (x) for the
Unicenter CA-Jobtrac being processed.
SYSPRINT
(Required) Report that lists all events selected.
IPLPRINT
(Optional) Report summary of archived IPL records.
SYSTERM
(Optional) Report of errors resulting from either the deletion of a record
from the current schedule or the addition of a record to the history
database. Also reports the cleanup activity that may be necessary, for
example, after a system crash.

Performing Archives
Example: The following figure shows sample statements to invoke the

GJTRJARC PROC:
//UTILITY JOB ........
//JS1 EXEC GJTRJARC,'LIST,ALL'
//JS2 EXEC GJTRJARC,'LIST,LAW'
In the example, JS1 produces a report listing all events on the current
schedule. JS2 produces a report listing all events on the current schedule with
LATE, ABENDED, or WAITING status.
GJTRJARC PROC Parameters

The GJTRJARC parameters let you specify the action to perform. The
following are the parameters:
ARCH
Archive events from the current schedule to the history database.
EXCP
Produce a report listing all events with a status of LATE, ABENDED, or
WAITING. Events are listed alphabetically by event name. (Produces the
same results as using the parameters LIST,LAW.)
LIST
Produce a list of all events on the current schedule. Events are listed
alphabetically by event name.
Performing Archives
Descriptions of Operands: The following are the GJTRJARC operands:

ALL
Selects all events, regardless of status.
ALLC
Selects all completed events, regardless of the successors' status.
B=busgrp or S=busgrp
Selects events with the specified business group name.
B=prefix* or S=prefix*
Selects events with the specified business group prefix.
C
Selects only completed events that have no successors waiting.
CLEAN|NOCLEAN
CLEAN removes old, missing events, and orphaned event-related table
records.
E=eventname or J=eventname
Selects events with the specified event name.
E=prefix* or J=prefix*
Selects events with the specified event name prefix.
FULL|SUMM
FULL lists all the records that are a supplement to the primary EVT and will
participate in the archive. In the new database structure, each scheduled
event is composed of multiple records. The primary record is the EVT, and
all the other records are supplementary.
SUMM lists only the predecessor (PST/PRED) and successor (PST/SUCC)
records that supplement the EVT, while all the other records that also
participate in the archive are not shown.
If neither FULL or SUMM is selected, only the primary record, the EVT, is
listed.
L=nnn
Selects events with the specified location.
LAW
Selects events with a status of LATE, ABENDED, and WAITING.
T=hhmm/mmdd-hhmm/mmdd
Selects completed events that have a target time within the time and date
range specified. The first hhmm/mmdd specifies the start of the range, and
the second hhmm/mmdd specifies the end of the range. Replace hhmm
with a four-digit number specifying the time (0001-2359), and replace mmdd
with a four-digit number specifying the date (0101-1231).

Performing Archives
Syntax of GJTRJARC, 0JOBARCH, and 0ARCHIVE Parameters and

Operands: The syntax of the GJTRJARC parameters is as follows:
Parameters Restricted-Use Operands Valid Operands

(use one only, the default is (use as many as you want)
underlined)
ARCH, C T=hhmm/mmdd-hhmm/mmdd
ALL B=busgrp
ALLC S=busgrp
FULL B=prefix*
LAW S=prefix*
SUMM E=eventname
J=eventname
E=prefix*
J=prefix*
L=nnn
CLEAN|NOCLEAN
EXCP, T=hhmm/mmdd-hhmm/mmdd
B=busgrp
S=busgrp
B=prefix*
S=prefix*
J=eventname
J=prefix*
L=nnn
LIST, C T=hhmm/mmdd-hhmm/mmdd
ALL B=busgrp
ALLC S=busgrp
FULL B=prefix*
LAW S=prefix*
SUMM E=eventname
J=eventname
E=prefix*
J=prefix*
L=nnn
Syntax Rules: The following rules apply to GJTRJARC parameters:

■ Follow all standard JCL syntax rules for parameters.
■ The default operand for ARCH is C.
■ The default operand for LIST is ALL.
■ The default for EXCP is all events that have a status of LATE, ABENDED,
or WAITING.
Performing Archives
Parameters on Dynamic Archives: Dynamic archive events 0JOBARCH and

0ARCHIVE provide the ability to specify input parameters to the GJTRJARC
archive utility. These parameters are specified as "arguments" of the
0JOBARCH or 0ARCHIVE event definitions. The following is an example of
SCL to supply specific archive parameters for 0JOBARCH processing:
JOBARCH 8 DAILY
+ IP=ARCH,C DAILY
JOBARCH 2 SUNDAY
+ IP=ARCH,ALLC,B=ABC SUNDAY
ARCHIVE 22 EOM
+ IP=ARCH,ALLC EOM
Note: You must use the ALL operand to force the archiving of NJE jobs,
regardless of the special NJE status REMOTE POST ERROR. Otherwise, an
NJE job with this status will remain on the Unicenter CA-Jobtrac checkpoint so
that a retry of posting the termination status to the originating node can be
performed.
Checkpoint Record Types
Record Type Description

Event records (EVT) Required and only one exists for each event (JOB,
IMOD, and so forth).
Argument records (ARG) Optional and can occur multiple times supplying
data for event processes (IP=).
Condition code records Optional and can occur multiple times providing
(CCD) condition code processing criteria (CC=).
Critical Path Monitoring Optional and can occur multiple times to define
records (CPM) event relationship flow (@FLOW).
Environmental Optional and can occur multiple times to define
dependency records system conditions (ED=).
(EDT)
Predecessor/ successor Optional and can occur multiple times to define
records (PST) event relationships and dependencies.
Resource dependency Optional and can occur multiple times to
records (RSC) determine availibility of resources (RS=).
Note: For more information about these optional records, see the Schedule
Creation Guide.

Modifying the Sysout Capture File
Modifying the Sysout Capture File

The GJTRVFMT utility provides a batch method for:
■ Increasing or decreasing the size of the sysout capture file
■ Formatting a new sysout capture file and copying your existing data into it
■ Moving your sysout capture file from one device to another
Enlarging the Sysout Capture File: If the index of your sysout capture file
begins to approach its maximum, you may need to increase the index's size. To
do this, you must allocate a new sysout capture file and specify the number of
cylinders required for the index. For details on sizing the Capture file, see
Chapter 8, “The Sysout Capture File” on page 149. For sample JCL member,
see SAMPJCL member DEFINEC.
Enlarging or Moving the Sysout Capture File: To enlarge or move your

sysout capture file, you should back it up first. Then allocate a new file and
format it. Finally, copy your data into the new file. For sample JCL member,
see SAMPJCL member CAPMOVE.
Deleting Members from Temporary-Use JCL Libraries

The GJTRMAJC utility provides a batch method for deleting members from
Unicenter CA-Jobtrac temporary-use JCL libraries that are no longer in use.
This utility cross-checks the members in the temporary-use JCL libraries

against events on the Unicenter CA-Jobtrac checkpoint database. Any
members that are not referenced by events on the current schedule are
deleted. Unicenter CA-Jobtrac does not delete defined members that should
always be retained, such as the PDSMAN $$$SPACE member. If the PDSMAN
member name has been changed, the name can be specified in the parameters
to GJTRMAJC. For more information, see “GJTRMAJC Utility Parameters” on
page 69.
To use the GJTRMAJC utility, you invoke the GJTRMAJC PROC and specify
parameters to perform the required function.
Descriptions of DDnames: Following are descriptions of ddnames used with

the GJTRMAJC utility:
JOBTRACx
Unicenter CA-Jobtrac being processed. It is important that this token is for
the Unicenter CA-Jobtrac in which the temporary-use JCL libraries are
defined.
TRACTnnn
(Required) One or more temporary-use JCL libraries can be specified in
multiple TRACTnnn DD statements where nnn is the location ID. Specify
only one data set for each TRACTnnn DD statement. Data sets cannot be
concatenated.
SYSPRINT
(Required) This output listing must be allocated with RECFM=FBA and
LRECL=133.

GJTRMAJC Utility Parameters

The GJTRMAJC parameters let you specify the action to perform. The following
describes the parameters.
GJTRMAJC Parameters: The syntax of the GJTRMAJC parameters is as

follows:
──┬────────────────┬──┬───────────────────┬─────────────────────────
│ ┌─NODELETE─┐ │ │ ┌─$$$SPACE───┐ │
└──┴─DELETE───┴──┘ └─,─┴─membername─┴──┘
DELETE
Deletes any members in the TRACTnnn libraries that are not referenced by
events on the current schedule.
NODELETE
Lists members in the SYSPRINT and SYSUT2 data sets that are in the
TRACTnnn libraries and are not referenced by events on the current
schedule. Does not delete any members in TRACTnnn libraries.
Default: NODELETE
membername
Indicates the member to retain.
Default: $$$SPACE
Syntax Rule: Follow all standard JCL syntax rules for GJTRMAJC parameters.
Deleting Archived Records with GJTRJPRG

The GJTRJPRG PROC provides a batch method for deleting old records from
the Unicenter CA-Jobtrac database.
You can use the GJTRJPRG PROC to delete old archived records based upon
their age, the number of records that exist for an event, or a combination of age
and number of records. The records deleted from the history database are no
longer kept except as printed output on the Purge report. Once deleted, the
records are not recoverable except from file backups.
| Be aware that GJTRJPRG processes two separate types of data:

| Event-oriented data and Unicenter CA-Jobtrac environmental statistics. Both
| types can be processed with a single SYSIN statement, but to avoid confusion,
| we recommend processing each type independently.
| If you want to delete statistics, STTDAYS=nnn,DELETE should be used.
| If you need to remove event information, do not code STTDAYS=.
| Also, remember that the use of EVENT=* deletes all history data for all events
| and should be used with care.
To use the GJTRJPRG utility, you invoke the GJTRJPRG PROC and specify
parameters to perform the required function. A sample GJTRJPRG PROC is
located in cai.CAIPROC library.
Following are descriptions of ddnames used with the GJTRJPRG utility:

JOBTRACx
Unicenter CA-Jobtrac being processed.
SYSIN
(Required) 80-byte card images specifying which history records to delete.
Each SYSIN statement is considered a separate report and must start in
column 1. The options specified only apply to those events selected for that
statement. The statements are processed in sorted sequence. Events are
processed by the first statement selecting it. Subsequent statements do not
reprocess an event previously selected by another statement. The following
keywords can be specified:
EVENT={evname|prefix|}[,GEN=nnnn]|[,DAYS=nnnn]
[,DELETE|NODELETE][,DTFMT={A|I}][,FULL|SUMM]
[STTDAYS=nnn]
[AUDDAYS=nnnn]
EVENT
The events for which history records are to be deleted.

GEN
The number of history records to keep for the specified events. nnnn
can be 0-9999. The most recently archived records are kept based on
this count. The default is zero.
DAYS
The age in days of the history records to keep for the specified events.
nnnn can be 0-9999. The age in days is based on the archive date and
time. The default is zero.
DELETE|NODELETE
DELETE deletes all history records meeting the criteria specified in the
SYSIN data set. Lists deleted records in the SYSPRINT and SYSUT2
data sets.
NODELETE, the default, lists history records in the SYSPRINT and
SYSUT2 data sets that meet the criteria specified in the SYSIN data
set. Does not delete any records in the history database.
DTFMT
Indicates the date format to use in the SYSPRINT output listing.
Specify A to print dates in the American format of mm/dd.
Specify I to print dates in the International format of dd/mm.
FULL|SUMM
FULL lists all the records that are a supplement to the primary EVT
and will participate in the archive. In the new database structure, each
scheduled event is composed of multiple records. The primary record is
the EVT, and all other records are supplementary.
SUMM lists only the predecessor (PST/PRED) and successor
(PST/SUCC) records that supplement the EVT, while all the other
records that also participate in the archive are not shown.
If neither FULL nor SUMM is selected, only the primary record, the
EVT, is listed.
STTDAYS
Defines the age in days of the statistics records to keep. nnn can be
1-999. There is no default. If no value is specified, statistics records are
not deleted.
AUDDAYS
Defines the age in days of the audit records to keep. nnnn can be
1-9999. There is no default. If no value is specified, audit records are
not deleted.
If both GEN= and DAYS= are specified, the number of history records
deleted is calculated so that the most history is kept.
If neither GEN= nor DAYS= is specified, no history records are deleted for
the specified event.
SYSPRINT
(Required) This output listing should be allocated with RECFM=FBA and
LRECL=133.
SYSTERM
(Required) This output listing should be allocated with RECFM=FBA and
LRECL=133.
Syntax Rules: The following rules apply to the SYSIN control statements:
■ All keywords for an event or event name prefix must be specified on one
statement.
■ Only one of each keyword GEN= and DAYS= can be specified for each
event or event name prefix.
■ An * in column one identifies the statement as a comment. The statement is
ignored.

Chapter 4. Recovery
Switch Primary Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Relocate the CA-Datacom/AD MUF . . . . . . . . . . . . . . . . . . . . . . . 76
Recover the Sysout Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Recover the Status of Events . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
AMR Recovery Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
In the production environment, system errors or abends may occur. These

errors or abends can affect various Unicenter CA-Jobtrac data sets. But the
most vulnerable data sets are the Unicenter CA-Jobtrac database and the
sysout capture file. Errors affecting these files can greatly affect Unicenter
CA-Jobtrac operations.
This section focuses on recovery of the Unicenter CA-Jobtrac database and the
sysout capture data sets.
Sources of Problems: Most problems do not originate with Unicenter

CA-Jobtrac errors. Recovery situations usually arise from system outages,
unscheduled IPLs, I/O errors, equipment checks, and operator cancellation of
events that update the Unicenter CA-Jobtrac checkpoint or sysout capture data
set.
Diagnostic Snap Dump: If you are unable to obtain a Unicenter CA-Jobtrac

diagnostic dump using the F taskname,DUMP command, issue the following
command:
S DUMPV3
Ensure that you route the output to a valid print class. This command generates
a batch GJTRVDMP diagnostic dump. The DUMPV3 JCL is generated during
the STAGE2 installation step and should be in your procedure library
(cai.CAIPROC).
Have this dump available when you call CA Technical Support for assistance.
Chapter 4. Recovery 73
Switch Primary Systems

For those running Unicenter CA-Jobtrac on multiple systems sharing a
CA-Datacom/AD database, there are times you might need to switch your
primary Unicenter CA-Jobtrac system to a secondary Unicenter CA-Jobtrac
system. If the CA-Datacom/AD database also resides on the same system as
the primary Unicenter CA-Jobtrac, this switching also requires relocating the
CA-Datacom/AD database.
This section describes the procedure to accomplish the switch, including

relocating CA-Datacom/AD.
What Happens When Switching Systems: When you issue the ACTSYS
command, the Unicenter CA-Jobtrac on that system immediately goes into
monitor mode from primary mode. The timer record on the database is
immediately updated to reflect the new primary system. As each Unicenter
CA-Jobtrac system wakes up and scans the database, it notices the change
and acts accordingly. The new primary system resets from monitor mode to
primary mode.
Procedure if Current System is Active: If you incorrectly switch your primary

Unicenter CA-Jobtrac system to a Unicenter CA-Jobtrac running on another
system, you can lose data in your sysout capture file. This can happen when
telling one Unicenter CA-Jobtrac it is primary when another Unicenter
CA-Jobtrac is already designated as primary. To avoid this loss, follow the
procedures in this section to switch primary systems.
Take the following steps to safely switch your Unicenter CA-Jobtrac primary
system to another when the current primary system is running fine:
1. If you are also going to need to move the CA-Datacom/AD MUF address
space, you should complete that move first. For more information, see
“Relocate the CA-Datacom/AD MUF” on page 76. If the MUF does not
need to be relocated, skip this step.
2. Shut down the Unicenter CA-Jobtrac system you want to become the
primary system.
3. Issue the following command on the system containing the current primary
Unicenter CA-Jobtrac system:
F taskname,ACTSYS=sysid
taskname is the name of the Unicenter CA-Jobtrac started task. sysid is the
ID of your system.
4. Once the modify message issued in Step 2 is acknowledged, bring up
Unicenter CA-Jobtrac on the new primary system.

Procedure if Current System is Hung Up: Take the following steps to safely
switch your Unicenter CA-Jobtrac primary system to another when the current
primary system is hung up:
1. Shut down the Unicenter CA-Jobtrac system you want to become the
primary system.
2. On the current Unicenter CA-Jobtrac primary system, request an SVC dump
and cancel Unicenter CA-Jobtrac. If necessary, force Unicenter CA-Jobtrac.
3. Bring up the Unicenter CA-Jobtrac system you want to become the primary
system.
4. Issue the following command on the Unicenter CA-Jobtrac system you want
to become the primary system:
ID of your system.
Procedure if the System is Down: Take the following steps to switch your
Unicenter CA-Jobtrac primary system to another when the system the current
primary is on has taken an unexpected outage:
1. If the CA-Datacom/AD MUF address space is also on this system, you
should complete that move first. For more information, see “Relocate the
CA-Datacom/AD MUF” on page 76. If the MUF does not need to be
relocated, skip this step.
2. Issue the following command on the Unicenter CA-Jobtrac system you want
to become the primary system:
ID of your system.
Relocate the CA-Datacom/AD MUF

This topic outlines some steps to take when relocating the MUF.
Scheduled CA-Datacom/AD Outage

Periodically, there is a need to take a system out of service. If a single
CA-Datacom/AD MUF is servicing multiple systems, and the system that is
running the MUF is the one that needs to be taken out or IPLed, you need to
move the MUF to another system to allow the remaining systems to continue
processing.
You can use the Unicenter CA-Jobtrac suspend processing to accomplish this
with minimum impact. You have two options:
■ Before shutting down the MUF, issue the SUSPEND command to each of
the Unicenter CA-Jobtrac systems. Each Unicenter CA-Jobtrac then
completes any current processing and closes access to CA-Datacom/AD.
The CA-Datacom/AD MUF can then be shut down on one system and
restarted on another system. Once restarted, you can issue the Unicenter
CA-Jobtrac RESUME command to each of the Unicenter CA-Jobtrac
systems, allowing them to reestablish their database connection and
continue processing where they left off.
■ Issue the CA-Datacom/AD EOJ command. Unicenter CA-Jobtrac
automatically detects that CA-Datacom/AD is in EOJ status and suspends
automatically on all systems. Once suspended, Unicenter CA-Jobtrac
automatically begins resume processing to reconnect to the database as
soon as the MUF becomes available.
While suspended, the user interfaces return an error message to indicate that
Unicenter CA-Jobtrac is suspended. For ISPF, to close the connection to the
database, all Unicenter CA-Jobtrac users must press Enter or exit the Unicenter
CA-Jobtrac ISPF interface. Internal processing waits for the resume to be
issued. CA-Datacom/AD does not shut down until all connections to the
database have been closed.

Some considerations for moving the MUF are the following:

■ The systems that the MUF can be moved to must share DASD. The
CA-Datacom/AD files and data areas must be on that shared DASD.
■ The CA-Datacom/AD SVC must be installed on the target system. The
CAS9 PROC that runs during IPL does this. For more information, see the
CA-Datacom/AD Installation and Maintenance Guide.
■ The same PROC can be used if the systems share a PROCLIB.
■ If you are an Advantage CA-Datacom/DB customer and you need to move
the MUF to a system that is not licensed for Advantage CA-Datacom/DB,
we recommend that you install and use CA-Datacom/AD for Unicenter
CA-Jobtrac on all systems. Databases that are initialized and populated
under Advantage CA-Datacom/DB are not usable in a CA-Datacom/AD
MUF.
Relocate the CA-Datacom/AD MUF for Unicenter CA-Jobtrac Using

the SUSPEND/RESUME Commands
You can relocate the CA-Datacom/AD MUF using the SUSPEND and RESUME
commands.
To relocate the CA-Datacom/AD MUF

1. Issue the status command to CA-Datacom/AD to identify ISPF users
connected to the database. Ask all users to exit the Unicenter CA-Jobtrac
ISPF panels. If you have changed from the default proc name, AD11STRT,
you need to specify the appropriate MUF proc name.
f ad11strt,status
2. Issue the following command to Unicenter CA-Jobtrac on each system
sharing the database.
f Jobtracx,suspend
3. Once the copies of Unicenter CA-Jobtrac are suspended, you can shut
down the MUF. Use the following command to shut down CA-Datacom/AD
where ad11strt is the name of the MUF PROC:
P ad11strt,status
4. Start the MUF on a secondary system.
5. Issue the following command to Unicenter CA-Jobtrac on each system
sharing the database to resume processing:
f Jobtracx,resume
If you also need to move the Unicenter CA-Jobtrac primary system, see the
“Procedure if Current System is Active” on page 74.
Relocate the CA-Datacom/AD MUF for Unicenter CA-Jobtrac Using

the Auto EOJ Detection
You can relocate the CA-Datacom/AD MUF using the Auto EOJ detection.
To relocate the CA-Datacom/AD MUF

1. Issue the status command to CA-Datacom/AD to identify ISPF users
connected to the database. Ask all users to exit the Unicenter CA-Jobtrac
ISPF panels. If you have changed from the default proc name, AD11STRT,
you need to specify the appropriate MUF proc name.
f ad11strt,status
2. Shut down the MUF. Use the following command to shut down
CA-Datacom/AD where ad11strt is the name of the MUF PROC:
P ad11strt
3. Unicenter CA-Jobtrac automatically suspends on all systems accessing the
MUF, allowing the MUF to complete termination. Unicenter CA-Jobtrac then
begins auto-resume processing.
4. Start the MUF on a secondary system.
5. Unicenter CA-Jobtrac automatically reconnects to the restarted MUF.
If you also need to move the Unicenter CA-Jobtrac primary system, see the
“Procedure if Current System is Active” on page 74.
Unscheduled CA-Datacom/AD Outage

Failure of the CA-Datacom/AD MUF affects all systems that are connected to
that MUF. In Unicenter CA-Jobtrac, the absence of the MUF causes the
Unicenter CA-Jobtrac task to automatically enter a suspended state. A
message is issued to console for each sharing system:
TRAC049I - DATABASE ACCESS SUSPENDED
Processing remains suspended until the MUF has been restarted on the same
or another connected system. Then Unicenter CA-Jobtrac successfully connects
on the next retry. The restart considerations for the MUF on a secondary
system are the same as those discussed in the Scheduled CA-Datacom/AD
Outage topic and should be addressed when installing the system.

Shadow MUF Failover

If you have implemented the Shadow MUF feature of CA-Datacom/AD, this
affects the preceding procedures in the following way.
Relocate the MUF
When shutting down the MUF, you should shut down the the Shadow MUF
first, and then shut down the Primary MUF. When restarting the MUF, the
first MUF that starts is the Primary MUF, and the second MUF assumes the
Shadow role.
Unscheduled CA-Datacom/AD Outage
If the Primary MUF fails, the Shadow MUF automatically takes over.
Unicenter CA-Jobtrac is notified of the failure and begins to retry the
connection. With the shadow active, Unicenter CA-Jobtrac connects to the
new MUF and resumes processing. This switch occurs without any operator
intervention, in most cases.
Note: For more information about the Shadow MUF configuration, refer to the
CA-Datacom/AD Shadow MUF white paper at ca.com/datacom (click on the
White Papers link).
Recover the Sysout Capture

The sysout capture file is backed up by the sysout archive task. The sysout
archive task backs up captured sysouts that you can then restore using the
GJTRVRLD procedures or the SAMPJCL member SAMPRELO that are
described in “Reloading Sysouts to Your Capture Data Set” on page 82.
Summary of Sysout Archival: The sysout archive task is performed by

executing either the 0ARCHIVE task or the 0SYSARCH task.
During the archive, all sysouts that have not yet been archived are copied to
the archive, and an updated archive index is placed at the end of the tape. The
index is an exact replica of the archive index on the online sysout capture and
has entries for all sysouts still within the online capture period. For example, if
sysouts are retained online for three days, the index maintains an entry for
each event for the duration of its online capture period.
If errors occur during sysout archival, error recovery routines attempt to capture
as many sysouts as possible, even on a damaged volume or over I/O errors.
The archive tape should contain any sysouts lost from the online capture during
archival.
For more information, see the sysout management information in the Operator
Guide.
Archiving Sysouts If You Cannot Execute the Archive Task: If you cannot
execute the 0ARCHIVE or 0SYSARCH dynamic archive tasks due to abends or
capture errors, you must shut down Unicenter CA-Jobtrac and restart using the
Start JOBTRAC command with the archive parameter (ARCH). Follow these
steps:
1. Issue the @HOLD command from any Unicenter CA-Jobtrac display or F
taskname,HOLD from the console to place the schedule on hold.
2. Issue one of the following operator commands to shut down Unicenter
CA-Jobtrac:
P taskname
F taskname,STOP
3. Issue the following command to restart the Unicenter CA-Jobtrac task:
S JOBTRAC.taskname,PARM=ARCH
4. Issue the @REL command from any Unicenter CA-Jobtrac display or F
taskname,RELEASE from the console to release the schedule again.
If the sysout capture file cannot be reused following this operation, you must
reinitialize or move the capture file (see “Moving the Sysout Capture File” on
page 81).

Moving the Sysout Capture File: If you need to enlarge the sysout capture
file, or if volume errors or hardware failures prevent reuse of the sysout capture
file, you must move the capture data set. Before moving the data set, run the
archive task. Then immediately shut down Unicenter CA-Jobtrac to prevent
Unicenter CA-Jobtrac from capturing sysouts after the archive tape is created.
See SAMPJCL member CAPMOV and follow these steps to move the sysout
capture file:
1. Issue the following operator command:
F taskname,RUN=ARCHIVE
or from ISPF:
RUN ARCHIVE
2. Make sure all jobs are completed on the checkpoint database. Issue the
following operator command:
F taskname,HOLD
or from ISPF, issue
@HOLD
3. Issue the following operator command:
F taskname,BACK
This not only shuts down Unicenter CA-Jobtrac but also backs out the
internals. For details on the BACK command, see the Operator Guide.
4. Issue the following operator command immediately after issuing the
command in Step 3 (do not wait for the command in Step 3 to complete).
This step ensures that all sysouts in the capture file have been backed up.
P taskname
5. Once Unicenter CA-Jobtrac is down, submit the SAMPJCL member
CAPMOV. This will COPY the old Capture DSN to a new Capture DSN, and
it will delete the old Capture DSN. Next, it allocates and formats a new
capture data set on another pack. The capture data set must be allocated
as five or more contiguous cylinders. The last step runs the GJTRVFMT
procedure with the DD statement OLDCAP pointing to the old capture file.
Ask your Unicenter CA-Jobtrac administrator for the name of the installation
library.
6. If the GJTRVFMT procedure succeeds, your new capture file is ready to
use. If the procedure fails, run GJTRVFMT without the OLDCAP DD
statement. In this case, you will need to reload your archived sysouts (see
the following topic “Reloading Sysouts to Your Capture Data Set” on
page 82).
Reloading Sysouts to Your Capture Data Set: Use the following steps to
load archived sysouts from tape to your capture data set.
1. Member SAMPRELO in SAMPJCL executes the GJTRVRLD procedure.
This procedure reloads the archive index to the sysout capture file. Include
the following statement, replacing vvvvvv with the volume serial number of
the tape containing the most recently archived sysouts:
//RELOAD EXEC GJTRVRLD,PARM='&INDEX',V=vvvvvv
For more information about the GJTRVRLD procedure, see the Operator
Guide.
2. Execute the job created in Step 1 to reload the most recent archive index to
the new capture data set. Only the latest archive index needs to be
reloaded, since the index contains entries for all sysouts within the online
capture time period.
3. Create JCL to execute the GJTRVRLD procedure. This procedure reloads
the sysouts that you require. For example, if your online sysout retention
period is two days, you would create two sets of JCL, each including one of
the following statements, where vvvvvv is the volume serial number of the
tape containing the most recently archived sysouts and bbbbbb is the
volume serial number of the tape containing the previous day's sysouts:
//CURRENT EXEC GJTRVRLD,PARM='',V=vvvvvv
//LAST1 EXEC GJTRVRLD,PARM='',V=bbbbbb
4. Execute the jobs created in Step 3 to reload the specified sysouts to the
new capture data set.
5. Restart the Unicenter CA-Jobtrac task by issuing the following operator
command:
S JOBTRAC.taskname

Recover the Status of Events
Recover the Status of Events

You can determine the status of events after an unscheduled IPL or a
shutdown of Unicenter CA-Jobtrac with a BACK command.
Events that are in a status of 'EXECUTING' or 'WAITING EXEC' before

(unscheduled IPL or BACK command) and these events either complete or start
AFTER the IPL but BEFORE Unicenter CA-Jobtrac is started would have the
following status:
Event Type Status After Restart

IMODs 'J' DEP with a ABENDED=4092 status.
Cross-platform events Will complete with correct status.
Non-NJE Jobs submitted to 'J' DEP with a ABENDED=U4084.
JES
NJE jobs See the Planning and Implementation Guide.
Events that are in a status of 'EXECUTING' or 'WAITING EXEC' before

(unscheduled IPL or BACK command) and these events either complete or start
AFTER the IPL and AFTER Unicenter CA-Jobtrac is started would have the
following status:
Event Type Status After Restart

IMODs 'J' DEP with a ABENDED=4092 status.
Cross-platform events Will complete with correct status.
Non-NJE Jobs submitted to Will complete with correct status.
JES
NJE jobs See the Planning and Implementation Guide.
A usual recycle or IPL of Unicenter CA-Jobtrac should return correct status.
Remember that TRACWARN messages are displayed on the console if SYS

OPTS option Nodelete Error Msg is set to Y.
Note: Jobs submitted before the BACK command or the unscheduled IPL and
are PURGED before Unicenter CA-Jobtrac internals are loaded could cause a
U4084 status.
AMR Recovery Procedures

If the Unicenter CA-Jobtrac Automatic Message Recognition (AMR) facility
stops intercepting messages, it is usually because the IBM IEAVMXIT WTO
Intercept user exit has abended. Since this exit is used by many software
products, the problem determination and resolution process must include
careful examination of each product that uses this exit. After the cause of the
abend has been determined and resolved, the AMR facility must be
reestablished.
Use the following procedure to reestablish the AMR facility:

1. Issue a 'D MPF' command from the OS console. If the output indicates that
IEAVMXIT is in ABENDED status, issue a 'K M,UEXIT=Y'.
2. Issue a 'D MPF' again. It should show ACTIVE status, as seen in the
following sample display. If the status is INACTIVE, an IPL may be required
to resolve the problem.
21 D MPF
1 IEE677I 12.55.54 MPF DISPLAY 971
1 MESSAGE ID -MPF SUPPRESS RETAIN AUTO TOKEN EXIT
1 CAIWDBUG - YES YES NO
1 CAJR3I - YES YES NO
1 CAS9115I - YES YES NO
1 DFH1523 - YES YES NO
1 DSI9I - YES YES NO
1 IEC7I - YES YES NO
1 IEF236I - YES YES NO
1 IOS427A - YES YES YES
1 IST53I - YES YES NO
1 IST532I - YES YES NO
1 VCS21E - YES YES NO
1 CAINEXIT - YES NO NO
1 CASNTRAC - YES YES NO
1 CAS9TRAC - YES YES NO |== ACTIVE STA
1 GENERAL WTO USER EXIT (IEAVMXIT) ACTIVE<=====
1 FIELD -MPF COLOR HLIGHT INTEN FIELD -MPF COLOR HLIGHT
1 URGATTN -DFL RED NONE HIGH IMEDACTN -DFL WHITE NONE
1 EVETACTN -DFL GREEN NONE NORM GENMSG -DFL GREEN NONE
1 PPMSG -DFL GREEN NONE NORM SELPEN -DFL BLUE NONE
1 INSTRERR -DFL WHITE NONE HIGH ENTRYARA -DFL GREEN NONE
1 WARNLGEN -DFL BLUE NONE NORM WARNRGEN -DFL BLUE NONE
1 WARNRURG -DFL RED BLINK HIGH OOLCNTL -DFL TURQU NONE
1 OOLLABEL -DFL TURQU NONE NORM OOLDATA -DFL GREEN NONE
1 COMMAND USER EXITS NOT FOUND

3. Issue:
S VINITx,PARM='ONLY=GJTRVMXT'
4. If loading a new AMRTABLE, issue:
F JOBTRACx,M=amrname
5. Finally, issue the following sequence of 'XON' and 'XOFF' commands:
a. Enter: XON
Output from the XON command:
21 XON
1 IEE35I XON COMMAND INVALID
b. Enter: XOFF
Output from the XOFF command:
21 XOFF
81 TRAC29I - MESSAGE EVENT PROCESSING STOPPED.
c. Enter: XON
Output from the XON command:
21 XON
81 TRAC29I - MESSAGE EVENT PROCESSING STARTED.
Chapter 5. Database Backup,
Recovery, and Utilities
CA-Datacom/AD Log File (LXX) . . . . . . . . . . . . . . . . . . . . . . . . . 89

CA-Datacom/AD Recovery File (RXX) . . . . . . . . . . . . . . . . . . . . . . 90
Hardware Backup and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . 91
DBUTLTY and Unicenter CA-11 . . . . . . . . . . . . . . . . . . . . . . . . . 92
Backup and Restore Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 93
Provided Utility Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
This section describes the processes necessary to perform a backup and

restore of the Unicenter CA-Jobtrac database and describes other database
processes you may need to use with CA-Datacom/AD and Unicenter
CA-Jobtrac. During installation, the following sample jobs were added to your
Unicenter CA-Jobtrac SAMPJCL library. These jobs assist you in performing
various CA-Datacom/AD processes and are discussed in more detail later in
this topic.
DBBKHOT
Backs up the database while Unicenter CA-Jobtrac is active (hot backup).
DBBKSTAT
Backs up the database while Unicenter CA-Jobtrac is not active (static
backup).
DBEXTRAC
Extracts the contents of a table to a flat file.
DBFXX
Initializes the FXX to support more CA-Datacom/AD tasks.
DBLOAD
Loads a database from a backup.
DBLXX
Reallocates the LXX to a larger size.
DBMOVE
Moves or resizes the Unicenter CA-Jobtrac database.
DBRECOV
Performs forward recovery.
DBRETIX
Performs Unicenter CA-Jobtrac database index rebuild.
DBSPILL
Performs CA-Datacom/AD spill of the LXX to the RXX recovery files.
Chapter 5. Database Backup, Recovery, and Utilities 87

Note: For more information about database recovery planning, see the
Planning and Implementation Guide.

CA-Datacom/AD Log File (LXX)
CA-Datacom/AD Log File (LXX)

CA-Datacom/AD uses a log file, known as the LXX, to allow data to be cached
while maintaining the data's integrity. As updates are made to the database, the
LXX is updated with each change that is made. The updates themselves may
not be written to the database at the time they are made. They are kept in
storage and written to the database periodically. This limits I/O and increases
the performance of the database accesses. In the event of a system failure or
CA-Datacom/AD MUF outage, the LXX is used to fill in the gaps that may have
existed due to this caching. This occurs at CA-Datacom/AD startup if the MUF
was not shut down normally. In other words, database recovery is automatic
after an outage if the DASD files are intact. No restore process is necessary. If
the database DASD is lost, a restore process is needed.

CA-Datacom/AD Recovery File (RXX)
CA-Datacom/AD Recovery File (RXX)

The CA-Datacom/AD recovery file allows you to perform forward recovery for a
database that has been restored from a backup. By default, CA-Datacom/AD is
installed with this option turned off. The LOGRCV options in the
CA-Datacom/AD CUSMAC(DBDATIN1) determine the creation of this file.
Unicenter CA-Jobtrac requires that you use the LOGRCV NO option. You were
instructed to change this setting during customization in the Planning and
Implementation Guide.

Hardware Backup and Recovery
Hardware Backup and Recovery

Some installations have invested in hardware mirroring of volumes to speed in
recovery of DASD. This can be local mirroring or across a Geographically
Dispersed Parallel Sysplex (GDPS). If you have mirroring and want to use it
with Unicenter CA-Jobtrac and CA-Datacom/AD, check CA Support Online for
technical articles about CA-Datacom/AD and mirroring. For more information,
contact CA-Datacom/AD Technical Support.

DBUTLTY and Unicenter CA-11
DBUTLTY and Unicenter CA-11

DBUTLTY is the primary program used for all database utility functions,
including spill, backup, load, and recovery. We recommend that you run these
jobs without Unicenter CA-11 control. These jobs are not restartable and do not
have data sets that should be cleaned up by Unicenter CA-11.

Backup and Restore Overview

The backup and restore jobs are discussed individually later in this chapter. The
following is intended to give you an overview of the backup and restore
process.



Provided Utility Jobs

The following topics provide information about Unicenter CA-Jobtrac provided
CA-Datacom/AD utility jobs.
Spill (DBSPILL)
To create a recovery file, you must run a spill job to remove completed
transactions from the database log, the LXX, and to write them to the recovery
file, the RXX. This saves the recovery information for forward recovery and
frees up space in the LXX. Unicenter CA-Jobtrac provides a sample spill job,
DBSPILL, in SAMPJCL. You can run the spill job on a periodic basis or through
automation when the LXX reaches a defined threshold.
Important! If the LXX is allowed to fill up, the database stops processing until
the spill job is run. This causes the Unicenter CA-Jobtrac processing to hang
until space is freed in the LXX.
When the LXX has reached the reporting percentage specified in the LXXSPILL
CA-Datacom/AD startup options, the following message is issued:
DB00308I LOG AREA IS nnn% FULL, nnnnnn BLOCKS SPILLABLE

To prepare the DBSPILL job:

1. Retrieve and customize the DBSPILL job in the Unicenter CA-Jobtrac
SAMPJCL.
2. Review the job and check the RXX DD to see whether the file name and
unit information are correct for your environment. If you are using a GDG for
this file, ensure that the GDG base is defined.
3. Since this is usually a tape or cart job, add any site-specific requirements,
such as a special job class.
4. Once you have run this job successfully, you should copy it to Unicenter
CA-Jobtrac and schedule it to run regularly.
The following is a sample AMR entry that could be used to submit the spill job,
DBSPILL, when the DB00308I message is issued:
CA-Jobtrac AMR Table Row 1 of 1

COMMAND ===> SCROLL ===> CSR
6/3/3 15:48
Table: MSGTBLXX
-------------------------------------------------------------------------------
Msg Text : 'DB38I' Offset=
Command/Reply:
Altered Text : Offset=
Process Pe : Create Event: AD1STRT Trigger Event: DBSPILL
TOD Range : SYS: Trg Act: ( RUN )
Bottom of data


Backups (DBBKHOT, DBBKSTAT)

You should be concerned with two backups when using CA-Datacom/AD. The
first is the backup of the CA-Datacom/AD system files. A backup of these files
was done during the installation of CA-Datacom/AD. These files are relatively
static when compared to those of Unicenter CA-Jobtrac or other products'
databases. A backup of these files should be done after the installation of a
product that uses CA-Datacom/AD, since these products, including Unicenter
CA-Jobtrac, update the data dictionary or meta data that describes the format
of the product's database. Periodically, a product may also update this
information to add additional elements or keys to the database. You should
back up this information whenever these changes are made or on a periodic
basis in case these system files are lost. Job AXNEW06 in the CA-Datacom/AD
SAMPJCL data set backs up these system files.
The second is the backup of the Unicenter CA-Jobtrac database. The Unicenter
CA-Jobtrac database should be backed up using either the DBBKHOT or
DBBKSTAT member in the Unicenter CA-Jobtrac SAMPJCL. DBBKHOT can be
run while Unicenter CA-Jobtrac is active, creating a hot or fuzzy backup.
DBBKSTAT must be run while Unicenter CA-Jobtrac is inactive and the
Unicenter CA-Jobtrac database is closed to create a static backup.
The static backup always contains a complete and stable database image,
though this is only as current as the time it was taken. The hot backup is taken
while the database continues to be updated. The data in the backup may be
incomplete and may contain only partial updates when multiple records and
tables are updated or added as a group. To recover a hot backup to a stable
point, forward recovery is required.
To prepare the DBBKHOT job:

1. Retrieve and customize the DBBKHOT job in the Unicenter CA-Jobtrac
SAMPJCL.
2. Review the job and check the TRACOUT DD to see whether the file name
and unit information are correct for your environment. If using a GDG for
this file, ensure the GDG base has been defined.
3. Since this is usually a tape or cart job, add any site-specific requirements
you have such as a special job class.
4. Ensure the correct database ID is specified on the DBID= keyword. The
default, unless changed during installation, is 161.
Note: The forecast database, 162 by default, is not included in the backup
since this data is usually not considered vital.

To perform a hot backup:

1. Run the DBBKHOT backup job. Unicenter CA-Jobtrac continues to process.
2. Run a DBSPILL job to spill completed transactions. If a restore becomes
necessary, this would be the first tape that is needed for forward recovery.
To prepare the DBBKSTAT job:

1. Retrieve and customize the DBBKSTAT job in the Unicenter CA-Jobtrac
SAMPJCL.
2. Review the job and check the TRACOUT DD to see whether the file name
and unit information are correct for your environment. If using a GDG for
this file, ensure the GDG base has been defined.
4. Ensure the correct database ID is specified on the DBID= keyword. The
default, unless changed during installation, is 161.
Note: The forecast database, 162 by default, is not included in the backup
since this data is usually not considered vital.
To perform a static backup:

1. Shut down Unicenter CA-Jobtrac.
2. Issue the /f AD10STRT,COMM STATUS command to identify any batch
jobs of TSO users that may be connected to the database. Only the ones
that are connected to the Unicenter CA-Jobtrac database, default 161, are a
concern.
3. Request that the listed TSO users exit the Unicenter CA-Jobtrac ISPF
panels.
4. Wait until the batch jobs terminate or cancel them.
5. Run the DBBKSTAT backup job.
6. When complete, restart Unicenter CA-Jobtrac and allow your TSO users to
reconnect.

Restore (DBLOAD)
The DBLOAD job restores a database from a backup tape created by
DBBKHOT or DBBKSTAT. The restore process is the same for either type
backup, hot or static. The Unicenter CA-Jobtrac SAMPJCL library contains a
DBLOAD job.
Important! CA-Datacom/AD Technical Support suggests that before you begin

recovery, call and open a severity 1 issue so that they can assist you with the
recovery process.
Before restoring, if the LXX file is intact, run the DBSPILL job to create the
latest RXX file to be used in the recovery.
To prepare the DBLOAD job:

1. Retrieve and customize the DBLOAD job in the Unicenter CA-Jobtrac
SAMPJCL.
2. Review the job and check the TRACIN DD to see whether the file name
and unit information are correct for your environment and for the backup
tape you are planning to restore.
4. Ensure the correct database ID is specified on the DBID= keywords in all
the control statements. This occurs several times, ensure all of the
occurrences are set to the same value. The default, unless changed during
installation, is 161.
Running the job:

1. The load of the database is the same for either hot or static backup.
2. Ensure CA-Datacom/AD MUF is active.
3. Ensure Unicenter CA-Jobtrac and all other accessors, such as TSO users,
are disconnected.
4. Run the DBLOAD job.

Recovery (DBRECOV)
DBRECOV can forward recover your database after it has been reloaded by
DBLOAD. If you restored from a hot backup, you must perform forward
recovery to ensure the integrity of the database. If you have taken a static
backup, you can also perform forward recovery, but it is not required.
As mentioned in the DBLOAD job, the LXX should have been spilled before the
database was loaded. This is your most recent RXX recovery file.
Since the RXX recovery files contain log data for all databases in the MUF, if
multiple databases were reloaded, you can recover multiple databases in one
forward recovery. The following discusses running DBRECOV for a single
database and for multiple databases.
To prepare the DBRECOV job to recover a single Unicenter CA-Jobtrac

database:
1. Retrieve and customize the DBRECOV job in the Unicenter CA-Jobtrac
SAMPJCL.
3. Ensure the correct database ID is specified on the DBID= keywords in all
the control statements. Since this occurs several times, ensure all of the
occurrences are set to the same value. The default, unless changed during
installation, is 161.
4. Identify the RXX recovery files, usually tapes or carts that are needed. You
need to include all RXX recovery files that have been created since the job
that created the restored backup started. On the RXX DD, concatenate
these files in order; the oldest file first and proceeding with the next oldest,
until the most recent RXX file is added as the last in the concatenation.
Important! These files must be processed in order to correctly restore the
database.

To prepare the DBRECOV job to recover multiple databases:
If you have restored multiple product databases within a MUF and want to
forward recover these databases at the same time, follow these steps.
1. Retrieve and customize the DBRECOV job in the Unicenter CA-Jobtrac
SAMPJCL.
3. Specify an ACCESS statement for each database you want to recover.
4. Specify a RECBASE statement for each database you want to recover.
5. Identify the RXX recovery files, usually tapes or carts that are needed. You
need to include all RXX recovery files that have been created since the
earliest of the restored backups started processing.
For example: if you ran two backups, one of DBID 161, and one of DBID 601,
and the backup of 161 started at 11:00 and the backup of 601 started at 11:30,
you need all RXX tapes created after 11:00.
On the RXX DD, concatenate these files in order; the oldest file first and
proceeding with the next oldest, until the most recent RXX file is added as the
last in the concatenation.
Important! These files must be processed in order to correctly restore the

database.
Running the job:

1. Open a Severity 1 Issue with CA-Datacom/AD Technical Support before
running the recovery.
2. Ensure CA-Datacom/AD MUF is active.
3. Ensure Unicenter CA-Jobtrac and all other accessors, such as TSO users,
are disconnected.
4. Working with CA-Datacom/AD Technical Support, run the DBRECOV job.

Other Functions
Unicenter CA-Jobtrac provides samples of other CA-Datacom/AD jobs for your
use. The Unicenter CA-Jobtrac SAMPJCL library contains these samples.
■ The DBFXX job increases the number of tasks that can be supported with
the FXX recovery file. This job ran during the modifying CA-Datacom/AD/AD
for Unicenter CA-Jobtrac part of the installation in the Planning and
Implementation Guide. The FXX, the Force Area data set, must be
initialized with a value that is larger than the total tasks specified in the
TASKS CA-Datacom/AD startup option.
By default, the FXX is defined for 50 tasks maximum. If the number of tasks
in the TASKS parameter of the CA-Datacom/AD startup options exceeds
50, the FXX must be reinitialized with a higher number of tasks. The default
size allocation of the FXX file should be large enough and should not need
to be reallocated.
If you need to run this job, ensure that you have shut down
CA-Datacom/AD normally before reinitializing the FXX. Because this
information is used for recovery, the database must have a normal
shutdown to ensure the FXX information is no longer needed.
Note: For more information about modifying CA-Datacom/AD/AD for
Unicenter CA-Jobtrac, see the Planning and Implementation Guide.
■ The DBLXX job increases the size of the CA-Datacom/AD log file, the LXX.
This job ran during the CA-Datacom/AD/AD customization part of the
installation. If the LXX is too small the log can fill up too quickly, requiring
frequent spilling of the LXX to the RXX. Job DBLXX in the Unicenter
CA-Jobtrac SAMPJCL library can be used to resize the LXX. Before this job
can be run, ensure that you have shut down CA-Datacom/AD normally. The
LXX contains information that is used to recover the database if
CA-Datacom/AD is abnormally terminated. If the LXX has filled, you need to
run the spill job, DBSPILL, to relieve the constraint before shutting down the
CA-Datacom/AD MUF. Once CA-Datacom/AD is shut down normally, you
can run the DBLXX to delete, redefine, and initialize a new LXX data set.
When this job has completed, you can restart the CA-Datacom/AD MUF. No
further recovery of the LXX or database is required.
Note: For more information about modifying CA-Datacom/AD/AD for
Unicenter CA-Jobtrac, see the Planning and Implementation Guide.

■ The DBMOVE job moves the Unicenter CA-Jobtrac to another pack or set
of packs. It can also be used to resize the data areas allocated for the
database.
■ The DBRETIX job rebuilds the Unicenter CA-Jobtrac database index area,
the IXX. Usually, Technical Support requests that you run this job. You may
need to run this if a PTF or service pack alters the data dictionary
definitions for the Unicenter CA-Jobtrac database. Any such change
requires running this job.
■ The DBEXTRAC copies the records from a CA-Datacom/AD table to a
sequential file. Usually, Technical Support requests that you run this job to
help diagnose a problem.

Chapter 6. User Exits
TRACX01: JCL Submission Exit (After JCL Read) . . . . . . . . . . . . . 106

TRACX02: Sysout Browse Authorization Exit . . . . . . . . . . . . . . . . . 107
TRACX03: JCL Submission Exit (Before JCL Read) . . . . . . . . . . . . 108
TRACX06: Date Card Calculation and Insertion Exit . . . . . . . . . . . . 109
TRACX08: TRACAUTH Interface Exit . . . . . . . . . . . . . . . . . . . . . 110
TRACX09: Schedule Scan Exit . . . . . . . . . . . . . . . . . . . . . . . . . 112
TRACX10: GJTRABTR and @JOBTRAC Utility Exit . . . . . . . . . . . . 113
TRACX11: Sysout Capture Exit . . . . . . . . . . . . . . . . . . . . . . . . 114
TRACX12: Sysout Archive Exit . . . . . . . . . . . . . . . . . . . . . . . . . 115
TRACX13: Schedule Update Exit . . . . . . . . . . . . . . . . . . . . . . . 117
TRACX14: Operator Command Exit . . . . . . . . . . . . . . . . . . . . . . 118
TRACX16: AUTO-SCHD Exit . . . . . . . . . . . . . . . . . . . . . . . . . . 119
TRACX18: JMF Pre-resolution Exit . . . . . . . . . . . . . . . . . . . . . . 120
TRACX19: JMF Post-Processor Exit . . . . . . . . . . . . . . . . . . . . . . 121
TRACX20: Event Archive Exit . . . . . . . . . . . . . . . . . . . . . . . . . 122
TRACX21: Environmental Dependency Retry Exit . . . . . . . . . . . . . . 123
TRACX22: IMOD Submission Exit . . . . . . . . . . . . . . . . . . . . . . . 124
TRACX23: JMF Dynamic Variable Preprocessor Exit . . . . . . . . . . . . 125
TRACX24: CA-JCLTrac Standards Enforcement Exit . . . . . . . . . . . . 126
TRACX25: CA-JCLTrac Tape Management System Interface Exit . . . . 132
TRACX26: Security Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
TRACX28: CA-JCLTrac PROCLIB Dynamic Allocation . . . . . . . . . . . 137
TRACX29: CA-Jobtrac Library Edit Exit . . . . . . . . . . . . . . . . . . . . 138
TRACX30: NJE ROUTE/XEQ Statement Exit . . . . . . . . . . . . . . . . 139
TRACX31: Cross-Platform Support Exit . . . . . . . . . . . . . . . . . . . . 140
With user exits, you can customize the functions that are important to your
installation. This chapter describes the usage of each exit, the parameter list
passed to each exit, and the return codes or data returned from each exit.
Chapter 6. User Exits 105

TRACX01: JCL Submission Exit (After JCL Read)
TRACX01: JCL Submission Exit (After JCL Read)

This exit is taken after the master scan task has located a valid JCL member,
read its contents into the JCL buffer, and resolved all overrides and date cards.
The JCL is ready for submission.
This exit enables you to alter the contents of the JCL buffer in any way you
choose. This exit is usually used to supply a security parameter (USER=secid)
to the JOB statement.
A sample of this exit is in your SAMPJCL library as member TRACX01.
Entry: At entry, register 1 points to the following list of 4-byte addresses:

Address Contains
A(eventname) Address of the 8-character event name.
A(JCL_buffer) Address of a buffer area for up to 9000 JCL statements.
A(end_buffer) Address of the last record in that buffer (must be set to last
JCL at exit).
A(EVT element) Address of event's element mapped by @HDEVTEL.
A(time/date) Address of current date and time in the Unicenter
CA-Jobtrac time format X'hhmmmmdd' (packed and
unsigned).
A(Greg_date) Gregorian date in the character format C'mmddyy'.
Exit: On return, register 15 contains one of the following return codes:

Code Explanation
0 Submit the JCL in the JCL buffer as is.
4 Cancel the event submission.
Note: GJTRSUB calls this exit in supervisor state.

TRACX02: Sysout Browse Authorization Exit
TRACX02: Sysout Browse Authorization Exit

This exit is taken after the GJTRVOUT ISPF dialog has read and
decompressed a selected sysout into a temporary data set in preparation for
browse. This exit can deny access to the sysout.
For this exit to work properly, you must link the GJTRVOUT ISPF dialog to the
TRACX02 exit.

Address Contains
A(eventname) Address of the 8-character event name.
A(user_ID) Address of the 7-character TSO user ID.
A(temp_dsname) Address of the data set name containing the sysout to be
viewed.
A(volser) Address of the volser on which the sysout data set resides.

Code Explanation
0 Allow viewing of the sysout data set.
4 Do not allow viewing of the sysout data set.

TRACX03: JCL Submission Exit (Before JCL Read)
TRACX03: JCL Submission Exit (Before JCL Read)

This exit is taken before the master scan task has located or read JCL into the
JCL buffer for an event ready to submit. This exit can read external JCL into
the JCL buffer and request Unicenter CA-Jobtrac to treat it as production JCL.
Unicenter CA-Jobtrac still resolves any overrides or date cards before
submission.

Address Contains
A(eventname) An 8-character event name.
A(JCL_buffer) Address of a buffer area for up to 9000 JCL statements.
A(end_buffer) Address of the last record in that buffer (must be set to last
JCL upon exit).
A(time/date) Address of current date and time in the Unicenter
CA-Jobtrac time format X'hhmmmmdd' (packed and
unsigned).
A(Greg_date) Gregorian date in the character format C'mmddyy'.

Code Explanation
0 Continue to read JCL from Unicenter CA-Jobtrac JCL library.
4 Cancel the event submission.
8 Use the JCL in the JCL buffer as the production JCL for the event.

TRACX06: Date Card Calculation and Insertion Exit
TRACX06: Date Card Calculation and Insertion Exit

This exit is taken after the Unicenter CA-Jobtrac GJTRDATV routine has
extracted a date control record from the DATELIB.
Each date control record in a JCL member (//:(ctlname)) refers to a card-image

record in the DATELIB. This exit can alter or calculate the date generations as
required. One control name can pull several concatenated cards into the date
card buffer passed to this exit.
For complete information about automatic date insertion, see the Extended
Scheduling Services Guide.

Address Contains
A(first_date_card) Address of the first date card in the current date buffer.
A(last_date_card) Address of last date card in the date buffer.
A(orig_schd_date) Address of the original scheduled date in mmddyy
format.
A(orig_Julian_date) Address of the original scheduled date in yyddd Julian
format.
A(eventname) Address of the 8-character event name for this event.

Code Explanation
0 Date insertion or alteration complete. Continue with JCL.
4 Error. Date or JCL invalid. Deny submission. Event appears on
schedule with JCL dependency and message TRAC014E RC=9.

TRACX08: TRACAUTH Interface Exit

This exit is taken before Unicenter CA-Jobtrac loads the TRACAUTH table from
a LNKLST library. Under standard Unicenter CA-Jobtrac operating conditions,
the TRACAUTH table provides data on levels of command, dependency, and
option authority for ISPF and GJTRABTR users. TRACAUTH also supplies
information on location ID names and NOTIFY=userid lists.
Keyed by user ID within location ID, TRACAUTH can be front-ended by

TRACX08. You can allow TRACAUTH to continue performing some functions,
while SAF security interfaces supply all other information. TRACX08 can
control six types of security or option usages.
Request codes 04 through 12 must supply requested data to any Unicenter

CA-Jobtrac caller in the TRACAUTH DSECT format as mapped by the @AUTH
macro.

Address Contains
A(request_code) Request code for this call to TRACAUTH. Possible
values are:
00 Reserved for internal use.
04 Return user's default entry and location ID.
08 Return user's authorization entry for this location
ID.
12 Return a location ID for location name.
16 Return a user ID list for location ID NOTIFY=.
20 Return a location ID list for user ID access.
A(caller's_@AUTH) Address of the caller's @AUTH DSECT entry. All
requests for @AUTH formatted information are also
returned to this address.
A(return_buffer) Address of the return data area (for request codes 16
and 20).


Code Explanation
00 Allow standard TRACAUTH processing. Exit does nothing.
04 Requested information located and returned.
08 User ID not located.
12 Reserved.
16 SAF/security severe error.

TRACX09: Schedule Scan Exit
TRACX09: Schedule Scan Exit

This exit is taken each time a scheduled event completes, including abends,
JCL errors, queue purges, and so on. The exit point is just after sysout capture
but before event termination processing (such as abend rescheduling or
successor release).
Additional user interfaces to other event-driven products (such as change

management systems or internal reporting systems) might need this exit.
The schedule record can be altered to indicate an output release or other

requirement. No return code processing is supported.

Address Contains
A(eventname) Address of the event name completed.
A(current_T/D) Address of the current time and date in Unicenter
CA-Jobtrac format hhmmmmdd (packed and unsigned).
Exit: On return, no return code processing is performed.

TRACX10: GJTRABTR and @JOBTRAC Utility Exit
TRACX10: GJTRABTR and @JOBTRAC Utility Exit

This exit is taken each time the GJTRABTR or @JOBTRAC utility runs. This
exit can be used to provide additional security to GJTRABTR and @JOBTRAC.
When resolving schedule update authority, the standard TRACAUTH structure

is used as well as the GJTRVAUT exit TRACX08. The information on the JOB
statement USER= parameter is used as the user ID. If no security user is
defined, the event name is used.
If the event running GJTRABTR or @JOBTRAC is a scheduled event, the

location ID of the event is used. If not on the schedule, location 0 (zero) is
assumed.

Address Contains
A(eventname) Address of the event name to be altered.
A(jobname) For GJTRABTR, the address of the job name attempting
the alteration. For @JOBTRAC, always contains
GJTRCUUS.
A(user_ID) Address of the USER=userid of the event attempting the
alteration.
A(parms) For GJTRABTR, the address of the image of the input
PARMS= field. For @JOBTRAC, always contains blanks.
Exit: On return, any nonzero return code denies this request. GJTRABTR and
@JOBTRAC do not abend. GJTRABTR and @JOBTRAC issue a nonzero step
condition code (RC=12) if the value in register 15 is nonzero. If you want an
abend, this exit can issue the abend macro.

TRACX11: Sysout Capture Exit
TRACX11: Sysout Capture Exit

This exit is taken when capture of a sysout is started, and as each line in an
event's sysout is captured.
This exit can be used for report extraction, balancing, external triggering based
on report content, and so on. It can also set user-alterable fields.
Since this exit is called for each line of sysout captured, care should be taken
to prevent excessive overhead.

Address Contains
A(calltype) XL1 flag:
1 Schedule capture begin
2 Sysout capture begin
3 &INDEX capture begin
4 Sysout line available
5 About to write sysout index
A(index_rec) Mapped by @SCINDXV macro.
A(line_len) Length of line (only good at call 4).
A(line_buffer) Current line (only good at call 4).
Exit: No return codes are expected from this exit.

TRACX12: Sysout Archive Exit

This exit is taken three times for each sysout in the capture file. This exit can
be used to reduce or to extend the online retention period for specific event
sysouts.
Exit TRACX12 is called with a CALLTYPE of 1, 2, or 3. At calls 1 and 2, you

can set on certain bits in the ISA. At call 3, you can alter fields in the index
area. For more details, see the @SCINDXV and @SCISA macros. Since this
exit is called at CALLTYPE 2 for each line of sysout being processed, care
should be taken to prevent long delays in sysout capture processing.

Address Contains
A(calltype) Type of call being made.
calltype Available user When taken; Other
actions comments
1 Set on Taken at the start of
WRAPX processing for each
sysout. Forces
sysout to be backed
up to tape or print.
2 Set ARHD, Taken for each line
PRNT of sysout. Force
backup of sysout to
a hard device (tape),
print, or both.
Set DELRQ Request sysout be
deleted, whether it
would have been or
not.
Set Request sysout be
NODELRQ kept, whether it
would have been or
not.
Set REWRIX Force call 3 to be
taken on the sysout,
so you can change
the index entry.
3 Change Index Taken when an
entire class of sysout
has been processed.
Change fields
marked as
changeable in the
@SCINDXV macro.
A(isa) Index sort area, mapped by @SCISA macro.

A(index) Index data, mapped by @SCINDXV macro.
Exit: No return code is expected from this exit. All changes the exit might have
are implemented by changes in the data areas.
Most events will have at least three sysouts: the JES JOB LOG, the JES
MESSAGES, and the JCL.

TRACX13: Schedule Update Exit
TRACX13: Schedule Update Exit

This exit is taken each time a dynamic or batch schedule update is performed.
As each event is selected for scheduling, this exit is given control.
This exit does not receive control for online ISPF additions.
This exit can be used to deny or alter the scheduling characteristics of any
event as it is selected for scheduling by the GJTRVSCH program.

Address Contains
A(eventname) Address of the event name being considered for
scheduling.
A(flag) Address of a 1-byte flag indicating to what the A(var)
parameter address points.
If the x'80' bit is set, the A(var) parameter address points to
8 bytes of blanks..
If the x'40' bit is set, the A(var) parameter address points to
the 7-character user ID associated with a batch schedule
update.
A(var) Either the address of 8 blanks or the address of a 7-byte
user ID. For more information, see the A(flag) parameter
description.
Exit: On return, any nonzero return code denies scheduling of the event. This
exit can alter the EVT element if necessary.

TRACX14: Operator Command Exit
TRACX14: Operator Command Exit

This exit is taken each time a scheduled operator command (from the System
Command Scheduling table or from the TRACMDS library) is issued.
Commands defined in AMR tables are not passed to this exit.
This exit can be used to deny or alter the text of an operator command as it is
being executed.

Address Contains
A(cmd_buffer) Address of buffer containing the command about to be
issued.
A(flagbyte) Address of internal command type flag. This flag contains
one of the following values:
x'20' Command from a command set
x'40' Scheduled table command
x'80' Operator request
A(cmdset_name) Address of member name of TRACMDS that this command
is defined in, or zero if it is not a component of a command
set.
Exit: On return, any nonzero return code denies command execution.

TRACX16: AUTO-SCHD Exit
TRACX16: AUTO-SCHD Exit

This exit is taken each time an AUTO-SCHD event completes JCL conversion
and is about to be released for execution.
The schedule record can be altered by the exit.

Address Contains
A (jobname&userid) Address of an 8-byte job name immediately followed by
a 7-byte user ID.
A(EVT element) Address of the event's element mapped by @HDEVTEL.
Exit: On return, any nonzero return code denies execution of the AUTO-SCHD
event. A JCL error results. Message TRAC024C is issued.

TRACX18: JMF Pre-resolution Exit
TRACX18: JMF Pre-resolution Exit

This exit is invoked each time Unicenter CA-Jobtrac resolves a JMF symbolic
during event submission. This exit is also invoked during the JCL check
process.
TRACX18 is called by the JMF symbol resolution routine named GJMFSRES. If

symbolic processing is not available, TRACX18 is not called.

Address Contains
A(eventname) Address of an 8-byte area containing the event name.
A(JMF_name) Address of an 8-byte JMF symbol name.
A(date) Address of the date for which the JMF symbol is to be
resolved. This is a 4-byte packed decimal field. The hex
representation is in the form 0091033C.
A(data_area) Address of a 48-byte area that you can use to replace the
resolution date or to provide a data and length value for the
JMF symbol. Note that when the user exit overrides the
date or data, JMF does not perform a table lookup.

Code Explanation
00 Continue with lookup and allow event submission. No user-supplied
data is provided. Data areas that were passed are not significant.
04 The exit changed the lookup date. A new OSD (original schedule date)
is contained in the area pointed to by word 4 of the lookup parameters.
This field must be in packed decimal format. The first 4 bytes of the
data area contain the new Julian date.
08 The user exit provided a value and length for the symbol name pointed
to by word 2 of the input parameters. The value and length are in the
area pointed to by word 4 of the input parameters. The data returned is
in the form of a 4-byte length (from 0 to 44) and up to 44 bytes of data.
A zero length indicates a null value for the JMF symbol and is a valid
JMF symbol value.
12 Do not allow this event to submit. No data lookup is performed.

TRACX19: JMF Post-Processor Exit
TRACX19: JMF Post-Processor Exit

This exit is invoked each time a JMF symbolic is resolved. The main JMF
lookup task, GJMFPRIM, calls this exit before it returns control to Unicenter
CA-Jobtrac submit processing.
Both the original unmodified JCL and the JCL after symbolic substitution are
provided. After you inspect the JCL, you can allow event submission to proceed
or request it to terminate.
TRACX19 is called by GJMFPRIM, which is the main JMF program. If symbolic

processing is not initialized, the exit is not called.

Address Contains
A(jclinit) Address of an 80-byte JCL statement containing the
unmodified JCL.
A(jclfin) Address of an 80-byte JCL statement containing the JCL
image after substitution.

Code Explanation
00 Continue with event submission.
04 Deny event submission.

TRACX20: Event Archive Exit
TRACX20: Event Archive Exit

This exit is invoked during the archival process before the schedule record is
written to the history database.
This exit can prevent schedule records from being written to the history
database.

Address Contains
A(eventname) Address of an 8-character event name.

Code Explanation
00 Archive the element and delete it from the active checkpoint.
04 Do not archive the element, but delete it from the active checkpoint.
08 Do not archive the element, and do not delete it from the active
checkpoint.

TRACX21: Environmental Dependency Retry Exit
TRACX21: Environmental Dependency Retry Exit

This exit is invoked each time an environmental dependency is added to an
event on the current schedule. The exit can modify the retry count and retry
interval used for the environmental dependency.
If the exit does not exist, or if it indicates upon return to use the default values,
the values specified on the CA-Jobtrac Global Options panel are used.

Address Contains
A(busgrp) Address of an 8-byte area containing the business group
name assigned to the event.
A(name) Address of an 8-byte area containing the name of the
environmental dependency.
A(rtrycnt) Address of a halfword containing the retry count. If
modified, the value must be in the range 0-1439 or the
default value will be used.
A(rtryint) Address of a halfword containing the retry interval in
minutes. If modified, the value must be in the range 0-1439
or the default value is used.

Code Explanation
00 Use the default values.
04 Use the values supplied by the exit.

TRACX22: IMOD Submission Exit
TRACX22: IMOD Submission Exit

This exit is invoked when a REXX IMOD event is ready to be scheduled for
execution. The exit can determine whether to allow the REXX IMOD event to
be scheduled for execution.

Address Contains
A(busgrp) Address of an 8-byte area containing the business group
name assigned to the event.

Code Explanation
00 Continue with the REXX IMOD execution.
04 Deny the REXX IMOD execution.

TRACX23: JMF Dynamic Variable Preprocessor Exit
TRACX23: JMF Dynamic Variable Preprocessor Exit

This exit is invoked for expansion of all dynamic JMF symbolic names.
During the exit, do not alter the data in the event element A(EVT element).

Address Contains
A(eventname) Address of an 8-byte area containing the event name. If
this is a simulation, it contains the value 0.
A(jmf_name) Address of an 8-byte area containing the JMF symbolic
name to expand.
A(date) Address of an 8-byte area containing the current date.
A(data_area) Address of a 48-byte area containing text to replace the
symbolic.
A(EVT element) Address of this event's element. If this is a simulation, it
contains the value 0.

Code Explanation
00 Continue with the JMF lookup.
04 Continue with expansion using the 4 byte length and data supplied by
this exit in the address pointed to by A(data_area).
>04 Do not continue the JMF lookup, and fail the event.

TRACX24: CA-JCLTrac Standards Enforcement Exit

This exit is called by the JCL Analyzer component of CA-JCLTrac (JCL3TRAC).
It scans the JCL text records to look for conditions that do not conform to your
JCL coding standards. The exit runs in either 24-bit or 31-bit mode as long as it
is loaded below the line.
When the Exit is Called: The TRACX24 exit is called at the following points
during syntax analysis:
■ JCL3TRAC initialization
■ Start of new job
■ Current statement
■ End of current job
■ JCL3TRAC EODAD
The exit is not called if a JCL error occurs during C/I-level checking, or a
Unicenter CA-Jobtrac submission error is detected.
Macros Used By the Exit: The TRACX24 exit uses the following macros:
■ @JCLKEY
■ @JCLTXT
■ @ERRM
■ @PUTM
■ @SCAN
Call Descriptions
JCL3TRAC Initialization Call: The TRACX24 exit is called during JCL3TRAC
startup. You should perform initialization logic at this point.
The following input parameters are used:

RO = F'O'
R1 = F'O'

Start of New Job Call: The TRACX24 exit is called each time a job completes
successful JCL conversion. You should perform new job processing at this
point. Register 1 points to a fullword containing the address of the JCT built for
this job by the interpreter. The JCT is below the line.

R = F'1'
R1 = A(WORD1) -----> WORD1 is DC A(JCT)
Current Statement Call: The TRACX24 exit is called each time a JCL
statement is processed for the current job. You should scan the text records at
this point. Register 1 points to a fullword containing the address of the current
JCL text record.

R = F'2'
R1 = A(WORD1) -----> WORD1 is DC A(@JCLTXT)
End of Current Job Call: The TRACX24 exit is called each time a job
completes standards enforcement processing. You should perform end-of-job
processing at this point.

R = F'3'
R1 = F''
JCL3TRAC EODAD Call: The TRACX24 exit is called during JCL3TRAC

EODAD. You should perform end-of-processing logic at this point.

R = F'4'
R1 = F''
Macro Descriptions
This topic describes the following macros:
■ @JCLKEY
■ @JCLTXT
■ @ERRM
■ @PUTM
■ @SCAN

@JCLKEY Macro
The @JCLKEY macro provides equates for the text units in the JCL text
records.
@JCLTXT Macro
The @JCLTXT macro maps the JCL text records. JCL text records are a
simplified form of the C/I's internal text formatted as variable-length records.
The maximum record length is 8254. The records passed to this exit are the
same records captured by the JCL Analyzer.
@ERRM Macro
The @ERRM macro defines error messages you can merge into the C/I
message spool. The @PUTM macro is used to merge the messages.
Messages defined by this macro are issued with a number in the form:
STDxxxxt. xxxx is the message number you assign, and t is the type of
message (E for error and W for warning).
This macro has the following format:
label @ERRM msg-number,msg-text,TYPE=type
label
Defines a label name for this macro expansion.
msg-number
Defines the number assigned to the error message.
Limits: 1 to 999
msg-text
Defines the message text enclosed in single quotes.
Limits: 100 bytes
type
Defines the message type as follows:
ERROR
A JCL error message.
WARN
A JCL warning message. Warning messages are not issued if the
NOWARN option is in effect.
Default: ERROR

@PUTM Macro
The @PUTM macro merges the messages defined with the @ERRM macro
into the C/I message spool. Any program that uses this macro must have
register 10 pointing to the CA-JCLTrac work area at the time the message is
issued. When the @PUTM macro is issued, the caller must be in 24-bit mode.
label1 @PUTM label2{,stmt-number}
label1
Defines the label name for this macro expansion.
label2
Defines the label name of the @ERRM macro that defines the message.
stmt-number
Defines a fullword containing the message number assigned to the
message by the @ERRM macro.
Coding Rules: The @PUTM coding rules vary depending upon the type of
call:
■ If it is a JCL3TRAC-initialization call, you cannot issue the @PUTM macro.
The C/I message data set is not open.
■ If it is a start-of-new-job call, you must provide a statement number.
■ If it is a current-statement call, you do not have to provide a statement
number. @PUTM uses the statement number of the current statement. You
must provide a statement number if the message applies to a previous
statement.
■ If it is an end-of-current-job call, you must provide a statement number if
you issue a message.
■ If it is a JCL3TRAC-EODAD call, you cannot issue the @PUTM. The C/I
message data set is now closed.
Return Codes: The following return codes are possible:

Code Explanation
0 The message was successfully written.
4 The warning message was not written because the NOWARN option
was in effect.
8 You issued a message without supplying a statement number when
there was no JCL statement in the current buffer.
12 You issued a message when the C/I message data set was closed.

@SCAN Macro
The @SCAN macro scans the JCL text records for major-minor text key
combinations. The macro expands into a call to GJC3MSXT to perform the
scan. If the text unit is found, register 1 will contain the address of the text unit
upon return.
@SCAN scan-var,{,}{(text-address)]JTXTTKEY}
scan-var
Indicates what to scan for. Use one of the following:
■ major-key,minor-key
■ (REG 2-12)
■ (0)
When you use register 0, you must load the major-minor text keys as
shown in the following example.
,,
If you use major-key,minor-key for the scan-var, use one comma. If you use
one of the other values for scan-var, use two commas.
(text-address)
Optionally, the register number, enclosed in parentheses, that contains the
address of where to begin the scan. If omitted, JTXTTKEY is used, which
starts with the first text unit in the string.

Return Codes: Before returning control to your program, the macro also does
a LTR R15,R15 to test the return code from GJC3MSXT. The following return
codes are possible:
Code Explanation
0 The text unit was not found.
4 The text unit was found.
Examples: The following example scans for the GDG field of the DSN
keyword. Register 6 contains the address of the start of the CA-JCLTrac text
units.
LA R6,JTXTTKEY
@SCAN DSNAME,DGDG,(R6)
The following example starts scanning at the address in register 2, and returns
the next key in the string.
@SCAN NEXT,,(R2)
The following example scans for the status field (NEW, OLD, SHR, MOD) of the
DISP keyword. Since the text address is omitted, the scan starts at the
beginning of the string. When you use register 0, you must load the
major-minor text keys as shown in the example.
SR R,R
ICM R,2,=AL1(DISP)
ICM R,1,=AL1(DSTAT)
@SCAN ()
The following example scans for the PERFORM parameter, starting at the
beginning of the string. If the parameter is not found, return.
@SCAN PERFORM
BZ RETURN

TRACX25: CA-JCLTrac Tape Management System Interface Exit
TRACX25: CA-JCLTrac Tape Management System Interface

Exit
This exit is called by the JCL Analyzer (JCL3TRAC) for each tape volume listed
on the volume pull list. It obtains the vault ID, slot creating job name, and
creation date from a tape management system's database.
At entry to TRACX25, the parameter list contains the volume serial number of
the tape being processed. The vault ID, slot creating job name, and creation
date are inserted in the parameter list in character format. They are printed on
the report exactly as in the parameter list. If one or more fields is omitted, it
should be filled with blanks.

Address Contains
A(volser) Address of a 6-byte area containing the volume serial
number.
A(vault) Address of an 8-byte area containing the vault ID.
A(slot) Address of a 4-byte area containing the slot number.
A(jobname) Address of an 8-byte area containing the creating job
name.
A(date) Address of an 8-byte area containing the creation date.
Exit: On return to the JCL Analyzer (JCL3TRAC), the contents of register 15

are not significant.

TRACX26: Security Exit

This exit is called by the Unicenter CA-Jobtrac ISPF dialog and by @JOBTRAC
to verify a user's authority to view, update, add, delete, or purge Unicenter
CA-Jobtrac information. You can control access to the following areas using
the TRACX26 exit:
■ Events
■ Holiday and cyclic calendars
■ Global options
■ Online table services
■ Unicenter CA-Jobtrac captured sysout
Relationship to TRACAUTH Table: If using this exit, most functions of the

TRACAUTH table no longer apply. The TRACAUTH table is still used to specify
which users are notified of abends and error conditions (NOTIFY= parameter of
@AUTH).
Entry: At entry, register 1 points to the address of a fullword. This fullword

contains the address of a list of fullword addresses. This list of fullword
addresses is explained in the following table:
Word Contains
1 The address of a 1-byte code indicating what area of the security are a
the user is attempting to access. The codes are:
x'01' Event
x'02' Holiday calendar
x'03' Cyclic calendar
x'04' Global options
x'05' Online table services
x'06' Unicenter CA-Jobtrac sysout
x'07' NJE remotely-submitted job
x'08' Remote credentials update
2 The address of a 1-byte Unicenter CA-Jobtrac token. The token
distinguishes which Unicenter CA-Jobtrac is being affected when
running multiple copies of Unicenter CA-Jobtrac. The token is the last
character in the Unicenter CA-Jobtrac ddname. For example, if a
Unicenter CA-Jobtrac is designated as JobtracY, the token is Y.

3 The address of a 1-byte location ID. The location ID is a value from 0

to 254. This is used for event and sysout security only. Security for
calendars, global options, and table services is always associated with
location ID 000.
4 The address of a 1-byte action code. This is the action the user is
trying to perform. The action codes are:
x'01' View
x'02' Update
x'04' Add
x'08' Delete
x'10' Purge
x'20' List
For an explanation of each action code, see “Word 4 Action Codes” on
page 135.
You can translate this code to the appropriate ATTR= parameter of a
RACROUT REQUEST=AUTH macro.
5 If the caller is @JOBTRAC, this contains the address of an 8-byte user
ID used in the security checking. Otherwise, this word contains 0
(zero). If the @JOBTRAC request is associated with a request from
another platform, the 8-byte user ID can be followed by an 8-byte
password. If the password is not provided, the 8 bytes following the
user ID contain hex zeros.
6 If the code addressed by word 1 is x'01', x'06', or x'07' and the action
code addressed by word 4 is not x'20', this word contains the address
of the 8-byte event name. Otherwise, this word contains 0 (zero).
7 If the code addressed by word 1 is x'08' (remote password update),
this word contains the address of the membername in the remote
password file (TRACRnnn) that is being accessed.
Note: Do not use this word unless the value in word 1 is x'08'.
Otherwise, the value is unpredictable.
8 If the code addressed by word 1 is x'08' (remote password update),
this word contains the address of the remote user ID that is being
updated. If word 4 is x'01' (view), the word is set to zero.
Note: Do not use this word unless the value in word 1 is x'08'.
Otherwise, the value is unpredictable.

Word 4 Action Codes: The following table explains what each action code
pointed to by word 4 (explained above) means for each security area:
Security Area x'01' x'02' x'04' x'08' x'10' x'20'

Events User is User is User is User is User is User is
attempting attempting attempting attempting attempting attempting
to view to update to add an to delete to purge to list
the an event event an event an event events
details of
an event
Holiday Calendars -- -- -- User is -- --
attempting
to view,
update,
add, or
delete a
holiday
calendar
Cyclic Calendars -- -- -- User is -- --
attempting
to view,
update,
add, or
delete a
holiday
calendar
Global Options -- User is -- -- -- --
attempting
to view or
update
the global
options
Table Services User is -- -- User is -- --
attempting attempting
to view to update,
an ADR, add, or
AMR, delete an
SCS, or ADR,
CCPF AMR,
table SCS, or
CCPF
table

Security Area x'01' x'02' x'04' x'08' x'10' x'20'

Sysouts User is -- -- User is -- --
attempting attempting
to view a to delete
Unicenter or
CA-Jobtrac undelete
captured a
sysout Unicenter
CA-Jobtrac
captured
sysout
NJE User is User is -- -- -- User is
Remotely-Submitted attempting attempting attempting
jobs to view to update to list
the an event events
details of
an event
Remote User is User is User is -- -- User is
Credentials attempting attempting attempting attempting
to view to update to add a to list
current a remote new events
remote credentials remote
credentials member credentials
member
Exit: On return, any nonzero return code denies the user access to the
requested area.
Linking the Exit: This exit must be linked AC(1), and it must reside in an
APF-authorized library.
Installing the Exit: The Unicenter CA-Jobtrac ISPF dialog uses the TSO
service facility to call this exit. To install this exit, take the following steps:
1. Define the security profiles for Unicenter CA-Jobtrac (see the supplied
sample exit).
2. Assemble and link the exit into an APF-authorized linklist library.
3. Add TRACX26 to the AUTHTSF TSO table in the IKJTSOxx member of
SYS1.PARMLIB.
4. Use the TSO PARMLIB command to update the TSO system values.

TRACX28: CA-JCLTrac PROCLIB Dynamic Allocation
TRACX28: CA-JCLTrac PROCLIB Dynamic Allocation

This exit is taken each time CA-JCLTrac adds a procedure library to the
dynamic allocation parameter list (DYNAMP). The name of the procedure
library, the procedure library ddname, and the user ID are passed to this exit. If
the exit issues a nonzero return code, the procedure library is not dynamically
allocated.

Address Contains
A(dsname) Procedure library data set name.
A(ddname) Procedure library ddname (PROC00, PROC01, and so on).
A(userid) User ID.
Exit: On return to CA-JCLTrac, register 15 contains one of the following return

codes:
Code Explanation
00 Add the procedure library to the dynamic allocation parameter list.
08 Do not add the procedure library to the dynamic allocation parameter
list.

TRACX29: CA-Jobtrac Library Edit Exit
TRACX29: CA-Jobtrac Library Edit Exit

This exit is taken before the ISPF/PDF edit is called when a user attempts to
edit a Unicenter CA-Jobtrac library using the Unicenter CA-Jobtrac panels.
You can use this exit to provide interfaces to change management, alter the
parameters for an edit, or to bypass the edit. For example, you can use this exit
to supply an ISET name for editing IMODs, or to supply an initial macro for
editing documentation members.

Address Contains
A(type) 1-byte data set type as follows:
C'D' Documentation library
C'I' IMOD
C'J' JCL library
C'P' Unicenter CA-Jobtrac CAIMAC library
C'S' SCL library
C'T' Temporary-use JCL library
A(locid) 3-byte location ID (in zoned format).
A(membername) 8-byte member name or member name mask.
A(macroname) 8-byte initial macro name, or blanks if there is no initial
macro.
A(ddname) 8-byte ddname.
A(isetname) 16-bytes of blanks. If the data set type is I, the exit can
return the ISET name in this space.
A(messageid) 8-bytes of blanks. In case of a return code of 12, a
message ID can be returned to the calling program.
Exit: On return to the Unicenter CA-Jobtrac dialog, register 15 contains one of

the following return codes:
Code Explanation
0 Continue the edit with the original parameters.
4 Continue the edit, but use the parameters returned by the exit.
8 Do not continue the edit.
12 Do not continue the edit. The exit has handled the edit. Display the
returned message if unequal to blank.

TRACX30: NJE ROUTE/XEQ Statement Exit
TRACX30: NJE ROUTE/XEQ Statement Exit

This exit is invoked for each JES2 /*ROUTE XEQ and /*XEQ statement and for
the JES3 //*ROUTE XEQ statement. The exit allows you to analyze the JES
statement and indicate to Unicenter CA-Jobtrac whether the job should be
considered an NJE job.
The exit can also be used if you use the JES ROUTE/XEQ statement for
purposes other than routing jobs to a true NJE remote node.

Address Contains
A(eventname) An 8-character event name.
A(jcl_image) Address of the first character of the JCL record.
A(node_name) Address of the first byte of the node name within the JCL
record.
Exit: On return, register 15 should contain one of the following return codes:
Code Explanation
00 Treat the job as a true NJE job.
nn Any nonzero return code treats the job as a local, non-NJE job.

TRACX31: Cross-Platform Support Exit
TRACX31: Cross-Platform Support Exit

This user exit is an IMOD ($JOBT_EXIT31). It must be placed in an ISET
accessible to the GSS task associated with the appropriate Unicenter
CA-Jobtrac as defined in the Global Options. To be recognized, the IMOD must
be compiled, in production status and must have been defined as callable. A
default $JOBT_EXIT31 is provided and is installed into a user-specified ISET
during Stage 2 of the Unicenter CA-Jobtrac installation process. This IMOD is
used to provide the retry count and retry interval for remote nodes. If an event
cannot be initiated, due to some failure in communication with the remote node,
it is retried the number of times and at a time interval specified by this exit.
The name of the GSS node for which the retry count and retry interval are to be
returned is provided to the exit as a single input argument.
User Exit Return Results: The exit may return as a result the character string
'FOREVER', which indicates retry will be continuous until transmission of the
request is successful. The exit may return as a result two numeric values
separated by at least one blank. The first value is the retry count and the
second value is the retry interval that is specified in seconds.
Note: The maximum value for the retry interval as expressed in seconds is
3600 (1 hour). The retry count is limited only by the maximum numeric value
able to be specified in CA-GSS ISERVE's implementation of REXX. If an invalid
result string is returned by the exit, the default of 10 retries every 30 seconds
will be used.

Chapter 7. TRACAUTH Security
Implementing a TRACAUTH Table . . . . . . . . . . . . . . . . . . . . . . . 142

User Authorization Profile Statements . . . . . . . . . . . . . . . . . . . . . 143
Termination Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
@AUTH Macro Statement Examples . . . . . . . . . . . . . . . . . . . . . 148
Chapter 7. TRACAUTH Security 141

Implementing a TRACAUTH Table
Implementing a TRACAUTH Table

Take the following steps to assemble and link the default TRACAUTH table:
1. Review the existing @AUTH statements in member AUTHTAB in the
SAMPJCL library. These statements define the default authorization entry
used for TSO users who are not otherwise specifically specified.
2. Add @AUTH statements to meet your installation requirements. The
following types of statements are available:
■ User authorization profile statements (see “User Authorization Profile
Statements” on page 143).
■ @AUTH macro termination statement (see “@AUTH Macro Statement
Examples” on page 148).
3. Edit member ASMAUTH in the SAMPJCL library.
4. Review the JCL carefully, making revisions to reflect your installation's
requirements.
5. Run the ASMAUTH job to assemble and link the TRACAUTH table.
6. You should perform an LLA REFRESH command to ensure that the
TRACAUTH table is available:
F LLA,REFRESH
7. The TRACAUTH table is automatically loaded when Unicenter CA-Jobtrac is
started. If you are modifying the table when Unicenter CA-Jobtrac is
running, issue the following command to load the modified table:
F taskname,AUTH

User Authorization Profile Statements

User authorization profile statements define authorization for individual users. If
a user requires authorization for more than one location, you must include one
of these statements for each location. Individuals without specific profile
statements use the default settings.
The first authorization profile statement for a user ID sets the greatest
authorization for that user. If a user is not authorized to perform a function in
the first location, the user cannot perform that function in any other location. For
example, if the first location profile does not allow event addition, no additions
can be made at any location, regardless of the JAUTH setting in subsequent
entries.
User authorization profile statements have the following format:
┌─,────────┐
parm=value┴──────────────────────────────────
──@AUTH──id,──locid,───
id
Specifies the user ID or group of user IDs for which the @AUTH statement
defines authority.
To define a single user, replace id with the TSO user ID of a specific user
for whom you want to define authority.
To define authority for a group of users whose IDs begin with the same
characters, replace id with the initial characters common to all users in the
group followed by an * (asterisk).
For example, USER1 specifies only the user whose ID is USER1, and
USER* specifies all users whose IDs begin with USER.
You can include as many @AUTH statements as required for a single user
ID. If you include multiple @AUTH statements for a single user ID,
Unicenter CA-Jobtrac considers the first statement used to be the greatest
authorization for that user. If a user is not authorized to perform a function
in the first location, the user cannot perform that function in any other
location. For example, if the first location profile does not allow event
addition, no additions can be made at any location, regardless of the
JAUTH setting in subsequent entries.
If you do not include any @AUTH statements for a user, the user is given
authorization only to view the current schedule and sysouts for location ID
000.

locid
Specifies the location ID for which the statement defines authority.
Replace locid with a numeral from 000 to 254, specifying a valid location
ID. The default is 000 (zero).
Each scheduled event is assigned a location ID. If a user schedules an
event using the ADD or RUN command, the user's default location ID is
assigned as the location ID. For information about assigning a location ID
to events, see the Schedule Creation Guide.
parm=value
The following are the parameters and values that are available. Specify
none or as many as you want in a statement, but only one of each
parameter in a statement.
NOTIFY
Specifies whether the user specified by the id variable is to be notified
of abends or error conditions for events in the location specified by the
locid variable. The user is notified with a SEND message. For
descriptions of the messages, see the TRACWARN messages in the
Message Guide. The available values are as follows:
Y
Notify the user.
N
The default value. Do not notify the user.
In an NJE environment, if NOTIFY is specified, only users on the node
on which the NJE job is run will be notified of abend or error conditions
for that node based upon information in the TRACAUTH table defined
for that node.
JAUTH
Specifies event-level authorizations for the user specified by the id
variable in the location specified by the locid variable. The available
values are as follows:
ALL
Authorizes the user to perform all event-level functions.
NONE
The default value. Prevents the user from performing any
event-level functions.
functions
Specify one or more of the following to permit specific event-level
functions. Do not use a separator between the letters.
A
Allow event addition
C
Allow condition code only changes

D
Allow event deletion
O
Allow event output viewing
P
Allow event purge
S
Allow successor/predecessor field only changes
T
Allow time/date alteration
DAUTH
Specifies dependency-change authorizations for the user specified by
the id variable in the location specified by the locid variable. The
available values are as follows:
ALL
Authorizes the user to alter all dependencies.
NONE
The default value. Prevents the user from altering any
dependencies.
dependencies
Specify one or more of the following to permit the user to alter
specific dependencies. Do not use a separator between the letters.
J
JCL dependency alteration is allowed
M
Manual release dependency alteration is allowed
O
Output release dependency alteration is allowed
A
Abend release dependency alteration is allowed
D
DSN dependency alteration is allowed
P
Predecessor dependency alteration is allowed
Q
Release or purge held jobs with $AJ or $PJ is allowed
R
Use of the restart/rerun section of Unicenter CA-Jobtrac/ISPF is
allowed

OPTA
Specifies options to apply to the user specified by the id variable. The
available values are as follows:
ALL
Activates all of the options specified.
NONE
The default value. Prevents the user from access to any of the
options specified.
options
Specify one or more of the following to activate the specific option
described. The L, D, E, and Y options are no longer supported or
needed. Do not use a separator between the letters.
J
Require that JCL for an event being added to the schedule
resides in the user's default location TRACJnnn JCL library.
O
Allow editing of options on the global options panels, and allow
use of the online table services for AMR, CCPF, ADR, and SCS
tables (JTS command).
P
Allow purging of an event with successors if it is confirmed with
a detail display and purge.
OPTB
Specifies options (see the following list) to apply to the user specified
by the userid parameter. The available values are as follows:
ALL
Activates all of the options specified.
NONE
The default value. Prevents the user from access to any of the
options specified.
options
Specify one or more of the following to activate the specific option
described. The D option is no longer supported or needed. Do not
use a separator between the letters.
C
Allow editing of the cyclic processing calendar using the SYS
CYC command.
H
Allow editing of the holiday calendar using the SYS HOLS
command.
S
Allow deletion of sysouts and recovery of deleted sysouts.

Termination Statement
Termination Statement
The @AUTH macro termination statement ends the @AUTH macro. It inserts
table terminators, time and date stamps, and table size information.
Only one termination statement can be included. It must be the last @AUTH
statement.
The @AUTH macro termination statement has the following syntax:
──@AUTH END─────────────────────────────────────────────────────────

@AUTH Macro Statement Examples
@AUTH Macro Statement Examples

Example 1: TSO user TSXJWB, at location 6, requires authority to view event
schedules and sysouts for his location. He is not authorized to alter the
schedule. His initial password is PSWD1. The following @AUTH statements
show the coding required for user TSXJWB:
@AUTH TSXJWB,6,JAUTH=O,DAUTH=NONE
Example 2: TSO user TSXMGR requires authority to view event schedules

and sysouts for her location and to make alterations to her location's events.
She must be allowed to make any changes to scheduled events except
complete deletion from the schedule or predecessor dependency changes. User
TSXMGR should be notified of any scheduled event execution errors. She is at
location 6, and her initial password is A1A. The following @AUTH statements
show the coding required for user TSXMGR (X is a continuation character in
column 72):
@AUTH TSXMGR,6,JAUTH=APTO,DAUTH=JMOADRQ, X
NOTIFY=Y
Example 3: This example shows @AUTH statements that define authorization

for user TSXOPR and all users whose IDs begin with TSX.
TSO user TSXOPR requires authority to view event schedules and sysouts for
his location and to make any alterations to his location's events. In addition, he
must be allowed to view and alter events for four other locations and to view
events of location 6. His level of authority for schedules of other sites varies
with the site. He should not be required to enter a password. TSXOPR should
be notified of scheduled event execution errors for his default location only.
All users whose IDs begin with TSX require authority to monitor location 6.
The following @AUTH statements meet the requirements described above (X is

a continuation character in column 72):
@AUTH TSXOPR,1,JAUTH=ALL,DAUTH=ALL,NOTIFY=Y, X
OPTA=O
@AUTH TSXOPR,2,JAUTH=TO,DAUTH=JMOPD
@AUTH TSXOPR,3,JAUTH=TO,DAUTH=JMO
@AUTH TSXOPR,4,JAUTH=PT,DAUTH=M
@AUTH TSXOPR,5,JAUTH=PTO,DAUTH=MO
@AUTH TSX,6,JAUTH=O,DAUTH=NONE
The generic entries (TSX*) entries should be the last entries in the table. The
table entries are processed in the order in which they are entered.
These names are displayed in the SYS HOLS panel display, the SYS CYCS
panel display, and the AUTH panel display. For ISPF displays, see the
Operator Guide.

Chapter 8. The Sysout Capture File
Contents of the Sysout Capture File . . . . . . . . . . . . . . . . . . . . . . 150

Compression Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155
Sizing the Sysout Capture File . . . . . . . . . . . . . . . . . . . . . . . . . 156
Sysout capture provides indexed information about which archive data set
contains sysouts for each event run during past months.
Since easy access to sysouts is so important, Unicenter CA-Jobtrac

automatically captures sysouts, provides the means for online research of
sysouts, and archives sysouts for future reference. The capture file must reside
on non-SMS DASD.
Capture and Archival: You can define up to four separate sysout classes for
capture and subsequent archival. Each class can have its own online aging
and archival criteria. The archive data set format is designed for optimum
production control use, with events sorted in event name sequence, complete
with separator pages and event header information suitable for microfiche
titling.
For information about the placement of the sysout capture file, see the chapter
"Preparing for Installation" in the Planning and Implementation Guide. For
information about setting up the sysout capture file and sysout classes, see the
chapter "Customization Tasks" in the Planning and Implementation Guide.
Sysout Viewing: With the online panels, you can view recent sysouts. If you
request a printed copy, Unicenter CA-Jobtrac supplies a special separator
during printing.
For information about managing and viewing sysouts, see the Operator Guide.
Other Sysout Archival Products: If you already have a sysout archival

product of another kind, you can direct Unicenter CA-Jobtrac to requeue each
listing to the other product as it captures the copy for on-schedule viewing. For
more information about requeueing sysouts to another product, see the
description of the Requeue Class field in the chapter "Customization Tasks" in
the Planning and Implementation Guide.
Unicenter CA-Jobtrac can interface with Unicenter CA-View r11 and higher.
Unicenter CA-View is a powerful sysout archival and retrieval tool, which
includes a PC interface. For information about setting up the Unicenter
CA-View interface, see the chapter "Customization Tasks" in the Planning and
Implementation Guide.
Chapter 8. The Sysout Capture File 149

Contents of the Sysout Capture File

The sysout capture file contains index entries and data entries. You can view
the file using ISPF's browse feature. You will probably want to set HEX and
COLS on while viewing the file, and a hexadecimal calculator will come in
handy.
This section describes the entries in the sysout capture file.
Overall Structure: The sysout capture file must be allocated in contiguous

cylinders, beginning on an even cylinder boundary. It consists of index blocks at
the front, followed by data blocks. The index portion and the data portion are
each an even number of cylinders.
All the index blocks are 116 bytes long, and all the data blocks are 3860 bytes
long. The file has no hardware keys. Since the file contains absolute (CCHHR)
addresses, it has DSORG PSU (Physical Sequential Unmoveable). The
capture file cannot span volumes.
Index Structure: The index of the sysout capture file contains the following
records:
First
The first record in the index is referred to as the pointer record. This record
gives the sysout capture handling programs enough information to build all
needed channel programs. The layout of the pointer record is described in
“Layout of the Pointer Record” on page 151.
Second
The second record is reserved. It is pointed to by the FINXCHR field in the
first record. The record number is always 4. The second record is used for
the archive lock. During sysout archival, it contains the string SAR (not a
reference to that CA product). During sysout archival, online deletes are not
allowed.
Third
The third record is reserved.
Subsequent
Subsequent records are the actual index entries for the file contents.
Starting at the FINXCHR field in the first record, the index entries occur.
These are mapped by the @SCINDXV macro distributed with the product.
The entries contain information about the items captured in the sysout
capture file. The layout of the index entries is described in “Layout of the
Index Records” on page 153.

Layout of the Pointer Record: The following table describes the layout of the
pointer record in the index:
Field Description Comments Position

INDXM DC XL1'00' Index pointer (M) 1
INDXBB DC XL2'00' Index pointer (BB) 2-3
INDXCHR DS CL5 Index CCHHR 4-8
INDXKLDL DC AL3(L'POINTER) Key length, data length 9 - 11
-- DC XL1'0' Reserved 12
INDXIBT DC H'0' Index blocks per track 13 - 14
INDXCYL DC H'0' Number of index cylinders 15 - 16
DATACYL DC H'0' Number of data cylinders 17 - 18
-- DS CL2 Reserved 19 - 20
DATALSCC DS XL2 Cylinder number of the last 21 - 22
cylinder
DATAM DC XL1'00' Data pointer (M) 23
DATABB DC XL2'00' Data pointer (BB) 24 - 25
DATACHR DS XL5 Data CCHHR 26 - 30
DATABLEN EQU 3860 -- --
DATAKLDL DC AL3(DATABLEN) Key length, data length 31 - 33
-- DC XL1'0' Reserved 34
DATADBT DC H'0' Data blocks per track 35 - 36
TRKCYL DC H'0' Tracks per cylinder 37 - 38
MYREL DC C'21X' Supporting version number 39 - 41
-- DC CL8' ' Reserved 42 - 49
MYSKM DC X'00' Pointer record (M) 50
MYSKBB DC XL2'00' Pointer record (BB) 51 - 52
MYSKCHR DS XL5 Pointer record CCHHR 53 - 57
MYDEVICE DS CL6 Type of device the file is on 58 - 63
MYUCBT4 DS C UCBTYP byte 4 64
FINXCHR DS XL5 Pointer to first index record 65 - 69
CCHHR


FDATCHR DS XL5 Pointer to first data record 70 - 74
CCHHR
-- DC CL42' ' Reserved 75 - 116
Meaning of CCHHR: The following explains CCHHR:

CC
2-byte cylinder number
HH
2-byte track number
R
1-byte record number. The record numbers start with 1 because IBM uses
record 0. Record 0 is not counted in the blocks-per-track figures in the
pointer record.
Use of the Pointer Record: If you browse the sysout capture file with HEX on,
you will probably be most interested in the number of index cylinders, the
number of data cylinders, the index blocks per track, and the data blocks per
track.
Using this information, you can calculate the total number of index blocks and
data blocks you have allocated. The difference between the first index CCHHR
(FINXCHR field) and the next index record that will be used (INDXCHR field)
determine the number of index records that are currently in use.
Similarly, the difference between the first data block CCHHR (FDATCHR field)
and the next data block that will be used (DATACHR field) determine the
number of data records that are currently in use. You may want to calculate
these and compare your results with the information shown by the Unicenter
CA-Jobtrac STATUS command.

Layout of the Index Records: The following table describes the layout of the
actual index records in the index:

INXJOBNM DS CL8 Jobname 1- 8
INXJOBID DS CL8 JES job ID 9 - 16
INXRIYR DS CL2 Run year (binary YYYY) 17 - 18
INXRDAT DS CL6 Run date (' MM/DD') 19 - 24
INXBTM DS CL6 Job start time (' HH:MM') 25 - 30
INXETM DS CL6 Job end time (' HH:MM') 31 - 36
INXCMPC DS CL2 2-byte completion code 37 - 38
INXCPID DS CL4 ID of system job ran on 39 - 42
INXNETID DS C Network ID (unused) 43
INXLOCID DS C Location ID 44
INXSCID DS CL8 Schedule ID/requester 45 - 52
INXINX@ DS CL5 CCHHR of this record 53 - 57
INXDAT@ DS CL5 CCHHR of first data record 58 - 62
INXTYPE DS CL3 Record INXTYPE 63 - 65
INXCTYP DS C Compression algorithm code (see “Compression 66
Methods” on page 155).
INXBCT DS H Data blocks in sysout 67 - 68
INXWRAP DS C A # indicates the record is not to be backed up 69
INXDELF DS C A D indicates the record was logically deleted 70
INXPP DS CL10 Process period of job 71 - 80
INXLN# DS PL4 Number of lines of job 81 - 84
INXFORM DS CL4 Job forms code 85 - 88
INXDEST DS CL8 Job destination ID 89 - 96
INXUWTR DS CL8 User writer ID 97 - 104
INXCOPY DS H Number of copies required 105 - 106
INXMLREC DS H Maximum LRECL 107 - 108
INXSQ DS CL1 Sysout queue (class) 109
-- DS CL3 Reserved 110 - 112
INXUSER DS F Reserved for your use 113 - 116

Locating the First Data Entry: Take the following steps to locate the first data
entry in the sysout capture file. You will need the information in the index
pointer record and a hexadecimal calculator.
1. Multiply the number of index blocks per track (INDXIBT) by the number of
cylinders per track (TRKCYL) to determine the number of index blocks per
cylinder.
2. Multiply the number of index blocks per cylinder (from Step 1) by the
number of index cylinders (INDXCYL) to determine the total number of
index blocks.
3. Convert the number from Step 2 to decimal and subtract 2.
From the top of your capture file, scroll down the number from Step 3.
You will see the last 1 or 2 index blocks and the first data block at the top
of your screen. The last index blocks will probably be hexadecimal zeros. If
you scroll right, you see where the index blocks end and the data blocks
begin, since the data blocks are longer.
The data blocks will be unreadable, unless you are looking at a capture file
that has recently been converted from CA-Jobtrac Version 1.3.

Compression Methods
Compression Methods
The INXCTYP field in each index record contains a code that corresponds to
the compression algorithm used to compress the sysout capture file.
Compression Algorithm Codes Explained: The INXCTYP field in the index

records contains a code that corresponds to the compression algorithm used to
compress the file. The following explains the codes:
0 Files compressed in CA-Jobtrac 1.3 use this algorithm, which
simply removes all blanks.
4 Files compressed in CA-Jobtrac 2.2 use this algorithm, which is a
version of Ziv and Lempel's second universal compression
algorithm (LZ78).
8 Files compressed in CA-Jobtrac 3.1 and above use this algorithm,
which is a version of Ziv and Lempel's second universal
compression algorithm (LZ78). Algorithm 8 gets somewhat better
compression with less CPU usage than algorithm 4.
The version of Ziv and Lempel's second universal compression algorithm

(LZ78) being used is known as adaptive dictionary compression.
How Adaptive Dictionary Compression Works: Virtually all files have sets
of repeating strings in them. For instance, the word sysout occurs many times
in this appendix. The idea of adaptive dictionary compression is to build up a
list of shortcuts based on strings that occur repeatedly in the text. For example,
if discussing VSAM I/O, the Access Control Block (ACB) would probably be
used. In subsequent references, only ACB would be used, saving 17
characters. Adaptive dictionary compression is a formalized algorithm for doing
this.
As repeated strings are encountered, they are abbreviated in a dictionary, and

the next time they are seen, the abbreviation is written instead of the original
text. Since both the compression and decompression routines build the
dictionary using the same rules, the dictionary does not have to be saved.
Compression algorithms 4 and 8 typically reduce sysout files to 18-35 percent

of their original size. The use of this compression also has a side benefit:
people are not able to browse the capture file and read the sysouts unless they
can use the sysout browse commands discussed in the Operator Guide.

Sizing the Sysout Capture File

Before determining the size of your sysout capture file, make sure you
understand how sysout archive retention works. For instance, a retention of 2
means that at least two copies of a sysout will be kept, and that any sysout will
be kept until it is over two days old. This means that a one-time job's output
remains in the capture file until it is deleted by the online delete command.
For information about sysout archive retention, see the chapters "Installation
Tasks" and "Customization Tasks" in the Planning and Implementation Guide.
Important! Do not let the sysout capture file become completely full. This
necessitates an immediate sysout archival run and stops schedule runs and
sysout capture until the archival run occurs.
Note: Job sysouts are grouped by class. If all of Job A's output goes to one
class, a run of Job A will correspond to one sysout in the file. If Job A's output
goes to multiple classes Unicenter CA-Jobtrac captures, it will have multiple
sysouts.
Minimum Size: The minimum size of the capture file is five cylinders.
Placement: The capture file is not DFSMS compatible. We suggest that you
place the capture file on a volume that is cached and used by DFW (DASD
Fast Write).
Estimating the Size: You can start with this estimate of 100 cylinders per 1.5
million lines. If you do this and you are fairly generous with your estimate of the
number of lines you will capture, you will probably be fine. However, if you
capture many small sysouts, this estimate is too conservative.
Easily Calculating the Size: Probably the best way to size the capture file
without extensive work is to run a sample set of jobs and schedules, capture
them, and use the Unicenter CA-Jobtrac STATUS command to display the
usage statistics on the capture file.
Multiply the result for your full workload. You can use the GJTRVFMT utility to
quickly copy and enlarge your capture file, after you calculate what its full size
should be.

Capture File Allocation for an Individual Sysout: Each sysout requires one
index block and one or more data blocks.
How many lines fit into a 3860-byte data block will vary. Each data block
usually holds 60-250 lines of output, depending on how many repeating
characters and repeating strings occur in your data, and how long your print
lines are. Of course, if a sysout contains only one line, the block holds only one
line. In the extreme case of all blanks, one 3860-byte block can hold 693 lines
of 133 blanks each. The line break has to be noted also, so this is equivalent to
134 characters times 693 lines or 92,862 characters compressed into 3860,
which is over 24 characters per byte.
So How Many Lines of Output Can I Really Put in 100 Cylinders?: Let's
consider a 3380 capture file 100 cylinders in size. The default number of index
cylinders for this file is 5, and thus the default number of data cylinders for this
file is 95.
Scenario Discussion
Worst Case On a 3380, 78 * 15 * 5 = 5,850. Thus, 5,850 index blocks
will fit in 5 cylinders. This means this sysout capture file
can hold at most 5,850 sysouts. If all your sysouts
contained 1 line, this 100 cylinder file would only hold
5,850 lines. In such a circumstance, you would want to
enlarge your index to 13 cylinders. Then the index could
hold 15,210 files, and thus 15,210 lines.
Best Case The 95 cylinders of data portion of this file contain
15,675 (11 * 15 * 95) data blocks. If all of your sysout
consisted of 133-byte blank lines, this file could hold up
to 10,862,775 lines (15,675 * 693).
Normal Case If sysouts average 121 bytes per line, and compression
averages 33 percent, the average 3860-byte block holds
over 96 lines, and 15,675 blocks holds over 1.5 million
lines. (Note the implicit assumption here that the average
sysout has over 256 lines, since 1,500,000/5850 =
256.4.) Also, most people will experience better than
33% compression.

Selecting and Controlling the Index Size: The GJTRVFMT utility is used to
format and move the capture file. It uses a default index size that works well for
most users. The default is determined using the following formula:
max((floor(MAXICYLS/4),min(ceil(585/INDXIBT/TRKCYL),MAXICYLS))
The following explains the values in the formula:

max
Largest of two numbers.
min
Smallest of two numbers.
floor
Largest integer less than or equal to the number (for example, floor(4.25) =
floor(4) = 4).
ceil
Smallest integer greater than or equal to the number.
MAXICYLS
Number of cylinders in the largest index that could possibly be required.
That is, the smallest number of cylinders such that the number of index
blocks is greater than or equal to the number of data blocks.
Other values
Obtained from the pointer record.
Example Index Size: For instance, in the case of a 3380 file with 100
cylinders, INDXIBT (index blocks per track) is 78, DATADBT (data blocks per
track) is 11, and TRKCYL (tracks per cylinder) is 15.
MAXICYLS is selected as 13, since 12 is too small and 13 is not, as shown in

the following:
12 78 15 = 144 < 88 11 15 = 1452, but
13 78 15 = 1521 > 87 11 15 = 14355
(The utility does not use trial and error to find MAXICYLS. Instead, it calculates
a theoretical exact maximum of index cylinders (EXMAXICYL), and rounds it up
to an even cylinder. The formula for EXMAXICYL will be given a little later.)

Also, note 5850 / 78 / 15 = 5 (comes out even) so the formula for default index
cylinders for our sample file now becomes:
max((floor(13/4) ,min(ceil(5),13)) equals
max((floor(3.25) ,min(ceil(5),13)) equals
max(( 3 ,min(ceil(5),13)) equals
max(( 3 ,min( 5 ,13)) equals
max(( 3 , 5 ) equals
5
This is why 5 cylinders is the default index size for a 100 cylinder 3380 capture
file.
In this case, the 5850 index blocks term has dominated the result. For smaller
capture files, MAXICYLS will dominate and be used for the index size. For large
capture files (over about 161 3380 cylinders) the leftmost term dominates and
the index size is 1/4 of MAXICYLS -- an assumption that each sysout averages
4 blocks or so.
Index Size Recommendation: We recommend that you use the default index
size and then observe your capture file's behavior. You can display the capture
file usage with the Unicenter CA-Jobtrac STATUS command. If your index
percentage used is consistently significantly different from your data percentage
used, you may want to adjust the allocation of index cylinders to suit your
actual usage.
To do this, first calculate the largest number of index cylinders you could
possibly need. For a capture file of size TC cylinders, the extreme maximum
number of index cylinders required (EXMAXICYL) can be determined by the
formula:
EXMAXICYTC DATADBT / (INDXIBT + DATADBT)
All the values in the formula except TC come from the pointer record (in fact,
your current TC is INDXCYL + DATACYL).
At this point, EXMAXICYL is probably not an even number. Divide it by the

result of dividing the index blocks used by the data blocks used. You can get
these numbers from the Unicenter CA-Jobtrac STATUS command. Round up if
there is any remainder. This gives an estimate of the number of index cylinders
you should use for a capture file of size TC, assuming your ratio of data blocks
to index blocks remains as it is now. You can force the format utility to use this
number of index cylinders by coding it in the parameter field of the program, for
example, PARM=6 or PARM=06 will force 6 index cylinders.

Chapter 9. Troubleshooting
Diagnostic Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Problem Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Access the Online Support System . . . . . . . . . . . . . . . . . . . . . . 165
Contact Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
Product Releases and Maintenance . . . . . . . . . . . . . . . . . . . . . . 167
Request Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168
Chapter 9. Troubleshooting 161

Diagnostic Procedures
Diagnostic Procedures
The following flowchart provides a summary of the procedures you should
follow if you have a problem with a CA product. These procedures are detailed
on the following pages.

Problem Resolution
Problem Resolution
Before contacting Technical Support, attempt to resolve the problem using the
following steps.
Verify the Problem

1. Examine the procedure that you used and compare it to the documented
procedure for performing the required activity.
2. If you find no discrepancies between your procedures and the documented
procedures, repeat the activity under conditions similar to those that existed
when the problem first appeared. (If you no longer get unsatisfactory
results, an inadvertent error may have caused the problem.)
3. If the same error occurs when you repeat a given activity, and you can find
nothing in the documentation to suggest that your procedure is flawed,
check with others at your site to determine if they have had the same or
similar problem and how they handled it.
Collect Diagnostic Data

In the following table, use the left column to categorize the problem your site
has encountered. Then, follow the instructions in the corresponding right
column to generate useful diagnostic data.
Type of Problem Procedure

Installation Save all SMP/E RECEIVE, APPLY,
and ACCEPT output and any other
output generated from any other
installation step.
User and system abends Obtain SYSMDUMP and dump to
tape. Follow procedures (later in this
chapter) to generate a problem
report. Collect the installation media,
listing, and problem report and
contact CA Technical Support.

Problem Resolution
Interpret Diagnostic Data

When you have collected the specified diagnostic data, write down your
answers to the following questions.
■ What was the sequence of events prior to the error condition?
■ What circumstances existed when the problem occurred and what action did
you take?
■ Has this situation occurred before? What was different then?
■ Did the problem occur after a particular PTF was applied or after a new
release of the software was installed?
■ Have you recently installed a new release of the operating system?
■ Has the hardware configuration (tape drives, disk drives, and so forth)
changed?
From your response to these questions and the diagnostic data, try to identify
the cause and resolve the problem.
If you determine that the problem is a result of an error in a CA product, you

can make use of the CA online support system to see if a fix (APAR or PTF) or
other solution to your problem has been published. Otherwise, call Technical
Support.

Access the Online Support System
Access the Online Support System

CA Support Online is CA's online product support and service system available
on the Internet. Enter http://ca.com/support in your browser to connect to the
site. These include the following:
■ Knowledge Base
■ Solution downloads
■ Technical Support issue management
■ License key downloads
■ Virus signature downloads
■ Product downloads
■ Product documentation downloads
■ Newsgroup open forums
■ E-News newsletters
Requirements for Using CA Support Online

For full access to all the services related to your licensed products, you must
log in. Many areas on the website require that you are a registered CA Support
Online user. You can enroll on the site.
Licensing
Many CA products use license keys or authorization codes to validate your
hardware configuration. If you need assistance obtaining a license key or
authorization code, click the Licensing link on CA Support Online.


For online technical assistance and a complete list of locations, primary service
hours, and telephone numbers, contact Technical Support at
http://ca.com/support.
Note: Only your local CA Support Center can provide native language
assistance. Please use English when contacting any North American center.
If you are unable to resolve the problem, have the following information ready
before contacting Technical Support:
■ All the diagnostic information described in “Collect Diagnostic Data” on
page 163.
■ Product name, release number, operating system, and genlevel.
■ Product name and release number of any other software you suspect is
involved.
■ Release/version level and PUTLEVEL of the operating system.
■ Your name, telephone number and extension (if any).
■ Your company name.
■ Your site ID.
■ Severity code. This is a number (from 1 to 4) that you assign to the
problem. Use the following to determine the severity of the problem:
1 "System down" or inoperative condition
2 Suspected high-impact condition associated with the product
3 Question concerning product performance or an intermittent
low-impact condition associated with the product
4 Question concerning general product utilization or implementation

Product Releases and Maintenance
Product Releases and Maintenance

Customers are requested to operate only under currently supported releases of
the product.
Customers with current maintenance agreements also receive ongoing product

maintenance. When a new release of the system is available, a notice is sent
to all current customers.

Request Enhancements
Request Enhancements
CA welcomes your suggestions for product enhancements. All suggestions are
considered and acknowledged. Contact your Account Manager.

Index
Special Characters
CA-JCLTrac
standards enforcement exit 126
@AUTH macro tape management system interface exit 132
statement examples 148 CA-JCLTrac PROCLIB dynamic allocation
termination statement 147 TRACX28 137
user authorization profile statement 143 CA-Jobtrac library edit
@ERRM macro 128 TRACX29 138
@HOLD command 80 CA-TCC
@JCLKEY macro 128 See CA Support Online
@JCLTXT macro 128 CA-TLC
@JOBTRAC utility exit 113 See Licensing
@PUTM macro 129 checkpoint
@SCAN macro 130 record types 66
commands
Numerics @HOLD 80
BACK 83
0ARCHIVE task 12, 61, 80
condition code records 66
0JOBARCH task 12, 61
condition code, using to abend event 36
0SYSARCH task 80
Cross-platform support exit 140
Customer Support
A See Technical Support
adding events with GJTRABTR
Advantage CA-Datacom/DB 10
altering the schedule in batch mode 35
D
data sets
AMR recovery procedures 84
sysout capture 80
archival 60, 62
database
archive
backup 87
event exit 122
deleting records from 70
event history report 12
Date card calculation and insertion exit 109
parameter 80
DB00308I message 97
archiving event information in batch mode 62
deleting
argument records 66
events 36
authorization codes, obtaining 165
records from database 70
AUTO-SCHD exit 119
temporary-use JCL library members 68
dumps 73
B dynamic archives
BACK command 83 GJTRJARC parameters 66
backing up the database 87
E
C Environmental dependency retry exit 123
CA Support Online 165 eSupport
CA-Datacom/AD 10 See CA Support Online
CA-Easytrieve reporting 13, 15 event
archival of 60
posting 36
Index 169
event (continued) JMF (continued)
purging 36 pre-resolution exit 120
records 66 JTEZREPT Report Utility 13, 15
recovering status 83
L
Event archive exit 122
events on current schedule, listing 62
license keys, obtaining 165
listing events on current schedule 62
F log file 89
forecast database ID 98, 99 LXX file 89
fuzzy backup 98
M
G microfiche for sysout archival 60
ghost records 66 mirroring 91
GJTRABTR
N
command summary 50
command syntax 48, 49
returned information 40 NJE ROUTE/XEQ statement exit 139
uniquely identifying an event for 36
GJTRABTR and @JOBTRAC 35
GJTRABTR utility
O
Operator command exit 118
commands 52
option records 66
description of 35
invoking with CLIST 59
invoking with JCL 58 P
GJTRABTR utility exit 113 posting events 36
GJTRJARC PROC 61 primary system, switching 74
GJTRJARC utility 62 purging events 36
GJTRJPRG utility 70
GJTRMAJC utility 68
GJTRVMFT utility 67 R
GJTRVRLD procedures 80 record types, checkpoint 66
recovery file 90
H
remote access to Unicenter CA-Jobtrac 36
reports
historical summary report 13 CA-Easytrieve 13, 15
history database 60, 62 listing events on current schedule 62
hot backup 98 REXX IMOD submission exit 124
RXX file 90
I
Internet, CA site 165 S
schedule
J adding event with GJTRABTR
batch alteration of 35
36
JCL submission exit
deleting event 36
after JCL read 106
scan exit 112
before JCL read 108
update exit 117
JMF
updating information 36
dynamic variable preprocessor exit 125
post-processor exit 121

security TRACX08
TRACX26 security exit 133 TRACAUTH interface exit 110
spill jobs 96 TRACX09
Standards enforcement exit 126 Schedule scan exit 112
StarTCC TRACX10
See CA Support Online GJTRABTR and @JOBTRAC utility exit 113
static backup 98 TRACX11
status, recovering event 83 Sysout capture exit 114
sysout TRACX12
archival 80 Sysout archive exit 115
archival of 60 TRACX13
archive exit 115 Schedule update exit 117
browse authorization exit 107 TRACX14
capture 80 Operator command exit 118
capture exit 114 TRACX16
moving capture data set 81 AUTO-SCHD exit 119
recovering 80 TRACX18
reloading after archive 82 JMF pre-resolution exit 120
viewing 149 TRACX19
sysout capture file JMF post-processor exit 121
compression methods 155 TRACX20
contents described 150 Event archive exit 122
copying 67 TRACX21
determining size, detail 156 Environmental dependency retry exit 123
enlarging 67 TRACX22
formatting 67 REXX IMOD submission exit 124
increasing index size 67 TRACX23
moving 67 JMF dynamic variable preprocessor exit 125
overview 149 TRACX24
structure described 150 CA-JCLTrac standards enforcement exit 126
TRACX25
T
CA-JCLTrac tape management system interface
exit 132
Tape management system interface exit 132 TRACX26
tapes Security exit 133
using for sysout archival 60 TRACX28
temporary-use JCL library, deleting members CA-JCLTrac PROCLIB dynamic allocation 137
from 68 TRACX29
TRACAUTH interface exit 110 CA-Jobtrac library edit 138
TRACAUTH table TRACX30
assembling and linking the default 142 NJE ROUTE/XEQ statement exit 139
tracking records 66 TRACX31
TRACX01 Cross-platform support exit 140
JCL submission exit (after JCL read) 106 Troubleshooting 161—167
TRACX02
Sysout browse authorization exit 107
TRACX03 U
JCL submission exit (before JCL read) 108 Unicenter CA-11 92
TRACX06 Unicenter CA-View 149
Date card calculation and insertion exit 109 user exits 106
AUTO-SCHD exit 119
Index 171
V
version number
deleting event with 36

Unic Job-Management PDF

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Unic Job-Management PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Unicenter CA-Jobtrac Job

Reports, Maintenance, and Recovery Guide

The manufacturer of this Documentation is CA.

Copyright © 2006 CA. All rights reserved.

Contact Technical Support

Chapter 5. Database Backup, Recovery, and Utilities . . . . . . . . . . 87

Chapter 6. User Exits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

6 Reports, Maintenance, and Recovery Guide

Chapter 7. TRACAUTH Security . . . . . . . . . . . . . . . . . . . . . . . 141

Chapter 8. The Sysout Capture File . . . . . . . . . . . . . . . . . . . . 149

Chapter 9. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . 161

This guide is written for systems software programmers and personnel

CA-Datacom/AD is identical in every way to Advantage CA-Datacom/DB,

To avoid confusion, all references in the guides are to CA-Datacom/AD.

10 Reports, Maintenance, and Recovery Guide

Event Archive Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Event Archive Report

The following figure shows an example of an event archive report:

1/12/2yy.286 CA-JOBTRAC(CHD4) - MAINTENANCE UTILITY (C)1992,25 CA, INC. GJTRJARC-1

14 EVENTS PROCESSED THIS PERIOD.

12 Reports, Maintenance, and Recovery Guide

Historical Summary Report

To access this report, run the JTEZREPT procedure referencing the

The following figure shows an example of a historical summary, which appears

1/12/yy CA, INC. - JOBTRAC R11 REPORTING

OPTION/FILTER FILTER/ OPTIONAL OPTIONAL OPTIONAL DESCRIPTION/COMMENT/ERROR MESSAGE

SYSTEM TOKEN - JOBTRAC SYSTEM IDENTIFICATION TOKEN

JTEZ1I - GJTREZST; NO ERRORS DETECTED.

1/12/yy CA, INC. - JOBTRAC R11 REPORTING

T H SYS REPORTING INTERVAL DATA EVENT COMPLETED

25/27/7 2:5:7 JCL READ 216 LOCAL 41 SYSABEND

1/12/yy CA, INC. - JOBTRAC R11 REPORTING

TOTAL ACTIVE ARCHIVED

14 Reports, Maintenance, and Recovery Guide

JTEZREPT Report Utility

This reporting utility allows users to:

The reporting as delivered consists of the following reporting components:

Each module produces three reports in the following general categories:

Data Selection/Processing Options: You can place predefined values into a

Report Selection/Processing Options

Data Selection Filtering

16 Reports, Maintenance, and Recovery Guide

18 Reports, Maintenance, and Recovery Guide

Display Schedule Report (Module GJTREZJW)

20 Reports, Maintenance, and Recovery Guide

END (EVT1-F-ENDFDAT, EVT1-F-ENDFTIM, EVT1-F-ENDTDAT,

3/25/yy CA, INC. - JOBTRAC R11 REPORTING PAGE 1

OPTION/FILTER FILTER/ OPTIONAL OPTIONAL OPTIONAL DESCRIPTION/COMMENT/ERROR MESSAGE

SYSTEM TOKEN 4 - JOBTRAC SYSTEM IDENTIFICATION TOKEN

HISTORY FLAG - HISTORY AND/OR ACTIVE RECORDS CHOSEN

JOB/EVENT - JOB NAME OR EVENT NAME

LOCATION - LOCATION; MANAGERIAL DEFINITION

BUSINESS GROUP - BUSINESS GROUP; MANAGERIAL DEFINITION

COMPLETION CODE - COMPLETION CATEGORY OF FINAL DISPOSITION

REMARKS - UP TO 2 LINES OF REMARKS FOR EACH JOB/EVENT

DATE FORMAT A - AMERICAN OR INTERNATIONAL DATE FORMAT

OSD - ORIGINAL SCHEDULED DATE OF EVENT

STARTING - STARTING PERIOD OF EVENT

SUBMIT - SUBMIT PERIOD OF EVENT

ENDING - ENDING PERIOD OF EVENT

TARGET - TARGET SCHEDULED BEGINNING OF EVENT

HISTORY - EVENT STATUS MOVED TO HISTORY ARCHIVE

JTEZ1I - GJTREZJW; NO ERRORS DETECTED.