Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Management
Third Edition
This documentation and any related computer software help programs (hereinafter referred to as the
Documentation) is for the end users 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 users 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 users 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.2277014(b)(3), as applicable, or their successors.
All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.
Copyright
CA Product References
This document references the following CA products:
Unicenter Network and Systems Management Job Management Option (Unicenter NSM JM
Option)
Unicenter Universal Job Management Agent (Unicenter Universal Job Management Agent)
Contents
Chapter 1. Introduction
CA-Datacom/AD . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 2. Reports . . . . . . . . . . . . . . . . .
Event Archive Report
. . . . . . . . . . . . . . . .
Historical Summary Report . . . . . . . . . . . . .
JTEZREPT Report Utility . . . . . . . . . . . . . .
Report Selection/Processing Options . . . . .
Data Selection Filtering . . . . . . . . . . . . .
Reporting Sequence . . . . . . . . . . . . . . .
Report Categories . . . . . . . . . . . . . . . .
History Reporting . . . . . . . . . . . . . . . . . . .
Display Schedule Report (Module GJTREZJW)
.
List Schedule Report (Module GJTREZJS)
List IPL Report (Module GJTREZIP) . . . . .
List Audit Report (Module GJTREZAU) . . . .
. . . . . . . . . . . . . . .
Chapter 3. Maintenance . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
Product Maintenance
Accessing the Current Schedule . . . . . . . .
Using GJTRABTR . . . . . . . . . . . . . . . .
GJTRABTR Command Syntax . . . . . . . . .
GJTRABTR Commands
. . . . . . . . . . . .
ABEND Command . . . . . . . . . . . . . . .
Add Command . . . . . . . . . . . . . . . . .
DELete Command . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
DUMP Command
END Command . . . . . . . . . . . . . . . . .
Get Command . . . . . . . . . . . . . . . . .
IMod Command
. . . . . . . . . . . . . . . .
Iserve Command . . . . . . . . . . . . . . . .
JTsys Command . . . . . . . . . . . . . . . .
MODify or POST Command . . . . . . . . .
Node Command . . . . . . . . . . . . . . . .
PURge or PRG Command . . . . . . . . . .
Query Command . . . . . . . . . . . . . . . .
STACK Command . . . . . . . . . . . . . . .
GJTRATBR Command Parameters . . . . . .
Coding JCL to Invoke GJTRABTR Processing
Example of a CLIST Invoking GJTRABTR . .
Performing Archives . . . . . . . . . . . . . . . . .
Methods of Executing the Archivals . . . . . .
About the GJTRJARC Utility . . . . . . . . . .
GJTRJARC PROC Parameters . . . . . . . .
Modifying the Sysout Capture File . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
9
10
11
12
13
15
16
16
16
17
18
19
23
28
30
33
34
35
37
48
52
52
52
52
53
53
53
53
54
55
55
56
56
57
57
58
58
59
60
61
62
63
67
Contents 5
. . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
Chapter 4. Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Switch Primary Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Relocate the CA-Datacom/AD MUF . . . . . . . . . . . . . . . . . . . . . . .
Scheduled CA-Datacom/AD Outage
. . . . . . . . . . . . . . . . . . . .
Relocate the CA-Datacom/AD MUF for Unicenter CA-Jobtrac Using the
SUSPEND/RESUME Commands . . . . . . . . . . . . . . . . . . . . .
Relocate the CA-Datacom/AD MUF for Unicenter CA-Jobtrac Using the
Auto EOJ Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unscheduled CA-Datacom/AD Outage . . . . . . . . . . . . . . . . . . .
Shadow MUF Failover
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recover the Sysout Capture . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recover the Status of Events . . . . . . . . . . . . . . . . . . . . . . . . . . .
AMR Recovery Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 5. Database Backup, Recovery, and Utilities
CA-Datacom/AD Log File (LXX) . . . . . . . . . . . . . .
CA-Datacom/AD Recovery File (RXX) . . . . . . . . . . .
Hardware Backup and Recovery . . . . . . . . . . . . . .
DBUTLTY and Unicenter CA-11 . . . . . . . . . . . . . .
Backup and Restore Overview . . . . . . . . . . . . . . .
Provided Utility Jobs . . . . . . . . . . . . . . . . . . . . .
Spill (DBSPILL)
. . . . . . . . . . . . . . . . . . . . .
Backups (DBBKHOT, DBBKSTAT) . . . . . . . . . .
Restore (DBLOAD) . . . . . . . . . . . . . . . . . . .
Recovery (DBRECOV) . . . . . . . . . . . . . . . . .
Other Functions . . . . . . . . . . . . . . . . . . . . .
Chapter 6. User Exits . . . . . . . . . . . . . . . .
TRACX01: JCL Submission Exit (After JCL Read)
TRACX02: Sysout Browse Authorization Exit . . . .
TRACX03: JCL Submission Exit (Before JCL Read)
TRACX06: Date Card Calculation and Insertion Exit
TRACX08: TRACAUTH Interface Exit . . . . . . . .
TRACX09: Schedule Scan Exit . . . . . . . . . . . .
TRACX10: GJTRABTR and @JOBTRAC Utility Exit
TRACX11: Sysout Capture Exit
. . . . . . . . . . .
TRACX12: Sysout Archive Exit . . . . . . . . . . . .
TRACX13: Schedule Update Exit
. . . . . . . . . .
TRACX14: Operator Command Exit . . . . . . . . .
TRACX16: AUTO-SCHD Exit . . . . . . . . . . . . .
TRACX18: JMF Pre-resolution Exit
. . . . . . . . .
TRACX19: JMF Post-Processor Exit . . . . . . . . .
TRACX20: Event Archive Exit
. . . . . . . . . . . .
TRACX21: Environmental Dependency Retry Exit .
TRACX22: IMOD Submission Exit . . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
68
69
70
73
74
76
76
77
78
78
79
80
83
84
87
89
90
91
92
93
96
96
98
100
101
103
105
106
107
108
109
110
112
113
114
115
117
118
119
120
121
122
123
124
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
Chapter 9. Troubleshooting . . . . . . . . .
Diagnostic Procedures . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
Problem Resolution
Verify the Problem . . . . . . . . . . . . . .
Collect Diagnostic Data . . . . . . . . . . .
Interpret Diagnostic Data . . . . . . . . . .
Access the Online Support System . . . . . .
Requirements for Using CA Support Online
Licensing . . . . . . . . . . . . . . . . . . .
Contact Technical Support . . . . . . . . . . .
Product Releases and Maintenance . . . . . .
Request Enhancements . . . . . . . . . . . . .
Index
. . . . .
125
126
126
127
128
128
128
129
130
132
133
137
138
139
140
141
142
143
147
148
149
150
155
156
. . . . . . . . . . . . . . . .
161
162
163
163
163
164
165
165
165
166
167
168
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
169
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . .
Contents 7
Chapter 1. Introduction
This section contains the following topics:
CA-Datacom/AD
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10
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
This section contains the following topics:
Event Archive Report
. .
Historical Summary Report
JTEZREPT Report Utility
History Reporting . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12
13
15
18
Chapter 2. Reports 11
GJTRJARC-1
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
USER21R
REPTESTA
REPTESTB
JARED
SCLT
SCLT2
JOB4
2535.1
2538.1
2538.2
2555.2
2555.2
2512.1
2512.2
2512.1
25517.1
2512.1
2512.1
2512.1
2512.1
25112.1
14
USER1 3/5 17.18 1/2 17.18 1/2 17.18 1/2 17.18
USER1 3/8 12.47 1/2 12.47 1/2 12.47 1/2 12.47
USER1 3/8 12.48 1/2 12.48 1/2 12.48 1/2 12.48
USER21 5/5 16.38 5/7 16.38 5/7 16.38 5/7 16.38
USER21 5/5 16.38 5/5 16.38 5/5 16.38 5/5 16.38
SCLT2 1/2 2.3 1/2 2.3 1/2 2.3 1/2 2.3
SCLT2 1/2 2.3 5/7 2.3 1/2 2.3 5/7 2.3
SCLT2 1/2 . 1/2 . 1/2 . 1/2 .
USER21 5/17 8.54 1/2 8.54 1/2 8.54 1/2 8.54
USER1 1/2 12.4 1/2 12.4 1/2 12.4 1/2 12.4
USER1 1/2 12.2 1/2 12.2 1/2 12.2 1/2 12.2
USER1 1/2 12.2 1/2 12.2 1/2 12.2 1/2 12.2
USER1 1/2 12.2 1/2 12.2 1/2 12.2 1/2 12.2
MISSINGA 1/12 1.11 1/1 1.11 1/12 1.11 1/1 1.11
THIS IS ARG THE IS TOOOOOOOOOOOO LONG TO FIT ON ONE CARD
3LT4
JOBTEST225112.1?
JOBTEST225112.1?
JOBTEST325112.1?
JOBTEST425112.1?
JOBTEST525112.1?
E N D
O F
R E P O R T
....
....
....
XE79
XE79
....
....
....
SCHD
SCHD
SCHD
SCHD
SCHD
657
648
648
648
.......
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
S/8
NORML
S/8
S/8
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
JOB
N
N
N
N
N
N
N
N
N
N
N
N
N
N
Chapter 2. Reports 13
Report Processing Options - The filtering options in effect for the report, and
any errors found show on this report.
1/12/yy
SYSTEM TOKEN
HISTORY INDICATOR
SYSTEM ID
REPORTING LEVEL
REPORT DATE FORMAT
REPORTING INTERVAL
FILTER/
BEGIN
DATE
OPTIONAL
BEGIN
TIME
OPTIONAL
END
DATE
OPTIONAL
END
TIME
PAGE
SUMM
I
PAGE
DESCRIPTION/COMMENT/ERROR MESSAGE
1/12/yy
T
O
K
H
S
T
SYS
ID
REPORTING INTERVAL
FROM/THRU
DATE
TIME
25/27/7 2:5:7
25/4/8 2:5:8
DATA
ACTION
EVENT
ACTION
DATA COUNT
JCL READ
DB
DB
DB
DB
EVENT COUNT
216
OPEN
CLOSE
COMMIT
ROLLBK
LOCAL
NJE(SUB)
NJE(RCV)
XPLAT
TEMPJCL
LATE
41
89
285
24,34
13
768
3
1,827
131
DUMMY
ARCHIVE
IMOD
SCHD LOAD
EDEP FAIL
SOUT FILE
SOUT LINE
SCHD READ
VSCH SECS
DSN TRG
MESG TRG
CMND TRG
1/12/yy
COMPLETED
ACTION
RERUN
RESTAGE
ACTIVE
RECORDS
SELECTED
ARCHIVED
RECORDS
SELECTED
79
SUBMITTED
AUTO SCHD
SYSABEND
CONDCODE
JCLERROR
USR EXIT
NORMAL
1
1
793
OPS PURG
OPS DELET
SCHD FAIL
1
1
RSR FAIL
MEXC FAIL
NJCL FAIL
PAGE
Make a copy of the source code modules and modify the code to deliver
additional functionality, or
GJTREZJS
GJTREZIP
GJTREZAU
Chapter 2. Reports 15
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.
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.
Chapter 2. Reports 17
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.
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
Chapter 2. Reports 19
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
FILTER/
BEGIN
DATE
OPTIONAL
BEGIN
TIME
OPTIONAL
END
DATE
OPTIONAL
END
TIME
PAGE
DESCRIPTION/COMMENT/ERROR MESSAGE
SYSTEM TOKEN
HISTORY FLAG
JOB/EVENT
LOCATION
BUSINESS GROUP
COMPLETION CODE
REMARKS
DATE FORMAT
OSD
STARTING
SUBMIT
ENDING
TARGET
HISTORY
3/25/yy
ACTIVE
EVT
SELECTED
ARCHIVED
EVT
SELECTED
143
52
TOTAL
PST
READ
PAGE
ACTIVE
PST
SELECTED
ARCHIVED
PST
SELECTED
Chapter 2. Reports 21
History Reporting
3/25/yy
H
S
T
JOB /
EVENT
NAME
Y AJO1
25/3/22
Y GOBRUCE 25/3/22
Y JOB5
25/3/25
DEPENDENCIES: M
Y JOHN
25/3/24
Y JOHN
25/3/24
Y JOHN
25/3/24
Y JOHN
25/3/24
Y JOHN
25/3/24
Y JOHN
25/3/24
Y JOHN
25/3/24
Y JOHN
25/3/24
N JOHN
25/3/24
DEPENDENCIES: J
N JOHN1
25/3/24
N JOHN1
25/3/24
DEPENDENCIES: J
Y JOHN1
25/3/24
Y JOHN1
25/3/24
Y JOHN1
25/3/24
Y JOHN1
25/3/24
Y JOHN1
25/3/24
Y JOHN1
25/3/24
Y JOHN1
25/3/24
Y JOHN1
25/3/24
Y JOHN2
25/3/24
Y JOHN3
25/3/24
DEPENDENCIES:
Y JOHN3
25/3/24
Y JOHN3
25/3/24
Y JOHN3
25/3/24
Y JOHN3
25/3/24
Y JOHN3
25/3/24
Y JOHN3
25/3/24
Y JOHN3
25/3/24
Y JOHN3
25/3/24
Y JOHN3
25/3/24
Y JOHN3
25/3/24
JES ID
COMP
CODE
DESC
JOB /
EVENT
NAME
SCHEDULE
DATE TIME
SYS
ID
PROCESS
PERD/FREQ
SUBMIT
DATE TIME
START
DATE TIME
END
DATE TIME
RUN
TIME
1
1
1
1
1
1
1
1
1
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
:<1
:<1
:<1
:<1
:<1
:<1
:<1
:<1
J6258
J6257
J6267
J6266
J6265
J6264
J6263
J6261
DELRQ
DELRQ
DELRQ
DELRQ
DELRQ
DELRQ
DELRQ
DELRQ
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
WSCH
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
14:27
14:27
14:27
14:27
14:27
14:27
14:27
14:27
14:27
XE79
XE79
XE79
XE79
XE79
XE79
XE79
XE79
D=USER11
D=USER11
D=USER11
D=USER11
D=USER11
D=USER11
D=USER11
D=USER11
RR-
14:29
14:28
15:12
15:11
15:9
15:8
15:7
14:51
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
14:29
14:29
15:12
15:11
15:9
15:8
15:7
14:51
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
14:29
14:29
15:12
15:11
15:9
15:8
15:7
14:51
OJO1
OJO1
OJO1
OJO1
OJO1
OJO1
OJO1
OJO1
OJO1
1
1
1
1
1
1
1
1
1
1
J
1
1
1
1
1
1
1
1
1
1
J6282
J6281
J6286
J6285
J6284
J6283
J6288
J6287
DELRQ
DELRQ
DELRQ
DELRQ
DELRQ
DELRQ
DELRQ
DELRQ
DELRQ
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
16:31
16:31
16:31
16:31
16:31
16:31
16:31
16:31
18:12
18:45
XE79
XE79
XE79
XE79
XE79
XE79
XE79
XE79
D=USER11
D=USER11
D=USER11
D=USER11
D=USER11
D=USER11
D=USER11
D=USER11
D=USER11
D=USER11
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
16:33
16:32
16:33
16:33
16:33
16:33
16:34
16:34
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
16:33
16:32
16:33
16:33
16:33
16:33
16:34
16:34
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
16:33
16:32
16:34
16:33
16:33
16:33
16:34
16:34
18:12
:<1
:<1
:1
:<1
:<1
:<1
:<1
:<1
:<1
OJO1
OJO1
OJO1
OJO1
OJO1
OJO1
OJO1
OJO1
OJO1
OJO1
J6298
J6297
J6296
J6295
J632
J631
J63
J6299
J6298
J6297
U495
U495
U495
U495
U495
U495
U495
U495
U495
U495
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
18:45
18:45
18:45
18:45
18:45
18:45
18:45
18:45
18:45
18:45
XE79
XE79
XE79
XE79
XE79
XE79
XE79
XE79
XE79
XE79
RRRRRRRQ-USER11
RRRRRRRRRRRR-
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
18:46
18:46
18:45
18:45
18:47
18:47
18:46
18:46
18:46
18:46
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
18:46
18:46
18:45
18:45
18:47
18:47
18:46
18:46
18:46
18:46
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
3/24
18:46
18:46
18:45
18:45
18:47
18:47
18:46
18:46
18:46
18:46
:<1
:<1
:<1
:<1
:<1
:<1
:<1
:<1
:<1
:<1
OJO1
OJO1
OJO1
OJO1
OJO1
OJO1
OJO1
OJO1
OJO1
OJO1
JES ID
COMP
CODE
DESC
CURR
STAT
SCHEDULE
DATE TIME
SYS
ID
PROCESS
PERD/FREQ
SUBMIT
DATE TIME
START
DATE TIME
PAGE
END
DATE TIME
RUN
TIME
LOC BUSINESS
GROUP
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 RR3/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 RR3/25 11:53 3/25 11:53 3/25 11:53
:<1 OJO1
+--------------------------------------------------------- R E M A R K S -------------------------------------------------+
+
+
+
+
+
+
+-------------------------------------------------------------------------------------------------------------------------+
LOC BUSINESS
GROUP
3/25/yy
H
S
T
CURR
STAT
PAGE
History Reporting
Chapter 2. Reports 23
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 ='
'
'
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
'
Chapter 2. Reports 25
History Reporting
The following are sample reports for the List Schedule report (CA-Easytrieve
module GJTREZJS):
3/25/yy
FILTER/
BEGIN
DATE
OPTIONAL
BEGIN
TIME
OPTIONAL
END
DATE
OPTIONAL
END
TIME
PAGE
DESCRIPTION/COMMENT/ERROR MESSAGE
SYSTEM TOKEN
HISTORY FLAG
JOB/EVENT
LOCATION
BUSINESS GROUP
COMPLETION CODE
EVENT TYPE(S)
- TYPE OF EVENT
OSD
STARTING
SUBMIT
ENDING
TARGET
HISTORY
History Reporting
3/24/yy
H T
S Y
T P
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
N
N
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
Y
D
D
C
C
C
D
D
D
D
JOB /
EVENT
NAME
JES ID
EVENT
VRSN
NO
APMPINF
APMPINF
APMP1HIS
APMP1HIS
APMP1INF
APMP1INF
APMP1INM
APMP2HIS
APMP2HIS
APMP2INF
APMP2INF
BDCDN95
BDCDN98
BDCDO95
BDCDO951
BDCDO952
BDCDO953
BDCDTXDL
BDCDT1
BDCDXOP2
BDCDX5
BDCDX31
BDCDX83
BDCDX94
BDCDX95
BNADFLD1
BNADFLD2
BSJCP24
BSJCP24
BSJXP15
BSJXP15
BSJXP15
GLMP1PYR
GLMP1RBD
GLMP1RBD
GLMP1SAC
GLMP1SAC
GLMP1SAS
GLMP1SAS
GLMP1SSJ
GLMP1SSJ
GLMP1STD
GLMP1STD
GLMP1UPD
GLMP1UPD
GLMP2COM
GLMP2COM
GLMP2CYP
J
J
J
J
J
J
J
J
J
J
J
J6161
J662
J678
J6868
J
J
J6399
1
2
1
2
1
2
2
1
2
1
2
34
16
4
55
1
1
17
1
4
1
49
19
8
23
4
4
3
4
1
2
3
2
1
2
1
2
1
2
1
2
1
2
1
2
1
2
1
3/25/yy
J6145
J6324
J6348
J6667
J6857
DUMMY
DUMMY
J17789
J18143
COMMAND
COMMAND
COMMAND
J
DUMMY
DUMMY
J
J
J
J
J
J
J
J
J
J
DUMMY
DUMMY
J
SCHEDULE
DATE TIME
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
12/29
12/28
12/31
12/28
9/28
9/28
12/3
4/6
1/1
4/6
12/3
12/29
12/31
12/3
12/31
12/31
4/11
4/11
1/18
1/18
1/18
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
15:5
:
15:5
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
ORIGINAL SYS
SCHED DATE ID
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
25/12/29
25/12/28
25/12/31
25/12/28
25/9/28
25/9/28
25/12/29
25/4/6
25/12/31
25/4/6
25/12/29
25/12/29
25/12/3
25/12/29
25/12/31
25/12/31
26/4/11
26/4/11
26/1/18
26/1/18
26/1/18
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
26/4/3
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
NORML
....
....
....
....
....
....
....
....
....
....
....
X...
X...
X...
X...
....
....
X...
....
X...
....
X...
X...
X...
X...
....
....
CA31
CA31
....
C...
C...
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
....
WMAN
WMAN
WMAN
WMAN
WMAN
WMAN
WMAN
WMAN
WMAN
WMAN
WMAN
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
WEXE
WEXE
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
TERM
WORKDAYS
WORKDAYS
FOM
FOM
WORKDAYS
WORKDAYS
FOM
FOM
FOM
WORKDAYS
WORKDAYS
DAILY
DAILY
M=BYPASS
M=BYPASS
DAILY
DAILY
DAILY
RQ-MISSING
DAILY
RQ-MISSING
DAILY
DAILY
DAILY
DAILY
=MTWTF..
DAILY
DAILY
DAILY
RR-REMOT
DAILY
DAILY
WORKDAYS
WORKDAYS
WORKDAYS
WORKDAYS
WORKDAYS
WORKDAYS
WORKDAYS
WORKDAYS
WORKDAYS
WORKDAYS
WORKDAYS
WORKDAYS
WORKDAYS
WORKDAYS
WORKDAYS
WORKDAYS
SUBMIT
DATE TIME
START
DATE TIME
1/22
1/26
1/26
1/27
12:15
18:48
22:27
16:11
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
4/3
1/22
1/26
1/26
1/27
1/22
4/6
1/2
4/6
1/22
1/22
1/22
1/22
1/21
1/21
4/11
4/11
12:15
15:9
19:22
15:1
12:15
12:15
12:15
12:15
1:16
1:16
1:53
11:8
1/22
4/6
1/2
4/6
1/22
1/22
1/22
1/22
1/21
1/21
4/11
4/11
PAGE
END
DATE TIME
:
:
:
:
:
:
:
:
:
:
:
:
22:43
18:48
22:27
16:12
1/22
1/26
1/26
1/27
22:43
18:48
22:27
16:12
:<1
:<1
:<1
:<1
23:2
15:9
2:9
15:1
21:47
21:48
22:7
22:2
1:16
1:16
1:53
11:9
1/22
4/6
1/2
4/6
1/22
1/22
1/22
1/22
1/21
1/21
4/11
4/11
23:2
15:9
2:9
15:1
21:47
21:48
22:7
22:2
1:16
1:16
1:53
11:9
:<1
:<1
:<1
:<1
:<1
:<1
:<1
:<1
:<1
:<1
:<1
:<1
:<1
:<1
93
93
93
93
93
93
93
93
93
93
93
93
93
93
EST
EST1
EST
EST1
EST
EST1
EST
EST1
EST
EST1
EST
EST1
PAGE
SCP2
SCP2
SXP5
SXP2
SXP2
EST
EST
EST
EST
EST
EST
EST
EST
EST
EST
EST
EST
EST
EST
EST
EST
TOTAL
--------13,61
1,174
11,887
3,178
211
9,657
11
3
Chapter 2. Reports 27
History Reporting
History Reporting
The following are sample reports for the List IPL report (CA-Easytrieve module
GJTREZIP):
3/25/yy
FILTER/
BEGIN
DATE
OPTIONAL
BEGIN
TIME
OPTIONAL
END
DATE
OPTIONAL
END
TIME
PAGE
DESCRIPTION/COMMENT/ERROR MESSAGE
SYSTEM TOKEN
SYSTEM ID
IPLED BY NAME
IPL TYPE
IPL REASON
IPLED
DATE FORMAT
3/25/yy
3/25/yy
SYS
ID
OPERATOR
ID
4
4
XE79 SMITH1
XE79 JONES2
IPL REASON
:-------------------------------------:
CAUSE BECAUSE SYSTEM FAILED
REGULAR STARTUP
ACTIVE
RECORDS
SELECTED
PAGE
IPL
TYPE
TIME
2yy/3/22 13:4:37
2yy/3/25 13:4:37
IPLED
DATE
PAGE
COLD
NORMAL
ARCHIVED
RECORDS
SELECTED
2
Chapter 2. Reports 29
History Reporting
History Reporting
3/25/yy
FILTER/
BEGIN
DATE
OPTIONAL
BEGIN
TIME
OPTIONAL
END
DATE
OPTIONAL
END
TIME
PAGE
DESCRIPTION/COMMENT/ERROR MESSAGE
SYSTEM TOKEN
GOBRUCE
USER ID
DATE FORMAT
CHANGE DATE/TIME
OSD
3/25/yy
T
O
K
JOB/
EVENT
NAME
GOBRUCE
SEV
ISPF
ADDED
SEV
GOBRUCE
EVT
ISPF
CHANGED
EVT
GOBRUCE
EVT DATE_STARTED
GOBRUCE
EVT MANUAL_DEPENDENCY
GOBRUCE
EVT TIME_STARTED
GOBRUCE
SEV
ISPF
ADDED
SEV
+ 1/1/
3/22/2yy
+ Y
N
+ ..
18.2.
+
GOBRUCE
EVT
ISPF
CHANGED
EVT
GOBRUCE
EVT DATE_STARTED
GOBRUCE
EVT MANUAL_DEPENDENCY
GOBRUCE
EVT TIME_STARTED
GOBRUCE
SEV
ISPF
ADDED
SEV
+ 1/1/
3/22/2yy
+ Y
N
+ ..
18.22.
+
GOBRUCE
EVT
ISPF
CHANGED
EVT
GOBRUCE
EVT DATE_STARTED
GOBRUCE
EVT MANUAL_DEPENDENCY
GOBRUCE
EVT TIME_STARTED
GOBRUCE
EVT
EVT
+ 1/1/
3/22/2yy
+ Y
N
+ ..
18.5.
+
GOBRUCE
EVT $AJ_REQUIRED
+ N
GOBRUCE
EVT ABEND_SUB_SUCCS
+ N
3/25/yy
ORIGINAL VRSN
SCHED DATE
CHANGE OCCURRED
DATE
TIME
USER ID
PAGE
DB
SQL_FIELD_NAME
TBL
ID :------------------------------:
ISPF
DELETED
ACTIVE
RECORDS
SELECTED
154
BEFORE IMAGE/
AFTER IMAGE
:------------------------------:
PAGE
ARCHIVED
RECORDS
SELECTED
Chapter 2. Reports 31
Chapter 3. Maintenance
This section contains the following topics:
Product Maintenance
. . . . . . . . . . . . . . . . . .
Performing Archives . . . . . . . . . . . . . . . . . . .
Modifying the Sysout Capture File . . . . . . . . . . .
Deleting Members from Temporary-Use JCL Libraries
Deleting Archived Records with GJTRJPRG . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . . .
. . . . . . . . . . . .
. . . . . . . . . . . . .
34
60
67
68
70
Chapter 3. Maintenance 33
Product Maintenance
Product Maintenance
The Unicenter CA-Jobtrac tasks and utilities offer the following capabilities:
Task or Utility
GJTRABTR utility
Event archival
Sysout archival
GJTRVRLD utility
GJTRVFMT utility
GJTRMAJC utility
GJTRJPRG utility
Product Maintenance
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.
Chapter 3. Maintenance 35
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:
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.
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
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
STACK command
and SYSIN
EXEC PGM=GJTRABTR,
PARM='ADD(JOB(TESTJOB3),DEP(M))'
EXEC PGM=GJTRABTR,
PARM='A(JOB(TESTJ3),DEP(M?)) Q(JOB(TEST))'
EXEC PGM=GJTRABTR,
PARM='POST(JOB(TESTJ11),S(TESTJOB4))'
EXEC PGM=GJTRABTR,
PARM='PRG(JOB(TESTJOB),V(11))'
EXEC PGM=GJTRABTR,
PARM='Q(JOB(TESTJOB),V(2))'
EXEC PGM=GJTRABTR,
PARM='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.
Chapter 3. Maintenance 37
Product Maintenance
Same as
/AB3
//
EXEC PGM=GJTRABTR,
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
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.
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.
Chapter 3. Maintenance 39
Product Maintenance
GJTRABTR messages.
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.
Product Maintenance
Explanation
OK
SAccc
UAccc
Indicates the event ended with a user abend. The abend code
is denoted by ccc.
PU
FO
JC
SCnn
CR
nnnn
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.
Chapter 3. Maintenance 41
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
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
CC
CG
DP
EX
Executing
HQ
OQ
TG
TM
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.
Chapter 3. Maintenance 43
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.
Chapter 3. Maintenance 45
Product Maintenance
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.
Chapter 3. Maintenance 47
Product Maintenance
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.
Note: For more information about reading syntax diagrams, see the Operator
Guide.
Product Maintenance
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.
**
Additionally, the ABEND and END commands do not use any parameters.
Chapter 3. Maintenance 49
Product Maintenance
D
E
L
D
U
M
P
G
e
t
*
*
I
M
o
d
I
s
e
r
v
e
J
T
s
y
s
M
OP
DO
I S
f T
y
N
o
d
e
P
UP
RR
gG
e
Q
u
e
r
y
S
T
A
C
K
**
**
**
BUSGrp (bgrp-name)
**
**
**
COMPLETION_Code
(code)
**
**
**
**
**
CURPP (processp)
**
**
**
**
DATE (org_schd_date)
**
**
**
DCNT (count)
**
**
**
Dependency ([action]
{deps})
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
E
L
D
U
M
P
G
e
t
I
M
o
d
I
s
e
r
v
e
J
T
s
y
s
M
OP
DO
I S
f T
y
N
o
d
e
P
UP
RR
gG
e
Q
u
e
r
y
S
T
A
C
K
**
**
**
RMG (x ...)
**
**
**
STATus (stats)
STEPCc ({NA|}stnum
logop cccc...)
**
**
**
**
**
**
**
SUBsystem (n)
Successors
([ac]name[.vv[.date]]...)
**
**
**
SYSTEM_id (sysid)
TJCL (tmem)
**
**
**
TYPE (etype)
**
**
**
**
Version (vv)
**
**
Used with the command, but it identifies an event only. You cannot change
the information.
Chapter 3. Maintenance 51
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.
This command has the following format:
IMod(imodname)
imodname
Defines a REXX IMOD name.
Limits: 1 to 16 characters
Chapter 3. Maintenance 53
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
equivalent GJTRABTR commands in the CA-GSS address space.
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
This command has the following format:
Iserve(iservename)
iservname
Defines a subsystem name.
Limits: 1 to 8 characters
*
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).
This command has the following format:
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.
Chapter 3. Maintenance 55
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
equivalent GJTRABTR commands in the CA-GSS address space.
This command has the following format:
Node(nodename)
nodename
Defines a node name.
Limits: 1 to 16 characters
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.
This command has the following format:
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
Chapter 3. Maintenance 57
Product Maintenance
JOB ...
EXEC PGM=GJTRABTR,
PARM=('ADD(JOB(TESTJOB3.31)','DEP(M)',
'S(TEST1,T1,TJX1,TESTJOB5))')
DD
SYSOUT=
Product Maintenance
/
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.
Chapter 3. Maintenance 59
Performing Archives
Performing Archives
Unicenter CA-Jobtrac offers the following archival abilities:
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.
Performing Archives
A schedule
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.
Chapter 3. Maintenance 61
Performing Archives
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
Chapter 3. Maintenance 63
Performing Archives
Performing Archives
Restricted-Use Operands
(use one only, the default is
underlined)
Valid Operands
(use as many as you want)
ARCH,
C
ALL
ALLC
FULL
LAW
SUMM
T=hhmm/mmdd-hhmm/mmdd
B=busgrp
S=busgrp
B=prefix*
S=prefix*
E=eventname
J=eventname
E=prefix*
J=prefix*
L=nnn
CLEAN|NOCLEAN
EXCP,
LIST,
T=hhmm/mmdd-hhmm/mmdd
B=busgrp
S=busgrp
B=prefix*
S=prefix*
J=eventname
J=prefix*
L=nnn
C
ALL
ALLC
FULL
LAW
SUMM
T=hhmm/mmdd-hhmm/mmdd
B=busgrp
S=busgrp
B=prefix*
S=prefix*
E=eventname
J=eventname
E=prefix*
J=prefix*
L=nnn
The default for EXCP is all events that have a status of LATE, ABENDED,
or WAITING.
Chapter 3. Maintenance 65
Performing Archives
8
IP=ARCH,C
2
IP=ARCH,ALLC,B=ABC
22
IP=ARCH,ALLC
DAILY
DAILY
SUNDAY
SUNDAY
EOM
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
Environmental
dependency records
(EDT)
Predecessor/ successor
records (PST)
Resource dependency
records (RSC)
Note: For more information about these optional records, see the Schedule
Creation Guide.
Formatting a new sysout capture file and copying your existing data into it
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.
Chapter 3. Maintenance 67
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.
Chapter 3. Maintenance 69
|
|
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
(Required) A dummy DD used to provide the system token (x) for the
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.
Chapter 3. Maintenance 71
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.
Chapter 4. Recovery
This section contains the following topics:
Switch Primary Systems . . . . . .
Relocate the CA-Datacom/AD MUF
Recover the Sysout Capture . . .
Recover the Status of Events . . .
AMR Recovery Procedures . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . .
74
76
80
83
84
Chapter 4. Recovery 73
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:
F taskname,ACTSYS=sysid
taskname is the name of the Unicenter CA-Jobtrac started task. sysid is the
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:
F taskname,ACTSYS=sysid
taskname is the name of the Unicenter CA-Jobtrac started task. sysid is the
ID of your system.
Chapter 4. Recovery 75
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.
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.
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.
Chapter 4. Recovery 77
Chapter 4. Recovery 79
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).
Chapter 4. Recovery 81
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
IMODs
Cross-platform events
NJE jobs
IMODs
Cross-platform events
NJE jobs
Chapter 4. Recovery 83
AUTO TOKEN
EXIT
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
NO
YES
NO
NO
NO
NO
NO
NO
|== ACTIVE STA
ACTIVE<=====
FIELD
-MPF COLOR HLIGHT
IMEDACTN -DFL WHITE NONE
GENMSG
-DFL GREEN NONE
SELPEN
-DFL BLUE
NONE
ENTRYARA -DFL GREEN NONE
WARNRGEN -DFL BLUE
NONE
OOLCNTL -DFL TURQU NONE
OOLDATA -DFL GREEN NONE
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
1
XON
IEE35I XON
COMMAND INVALID
b. Enter: XOFF
Output from the XOFF command:
21
81
XOFF
TRAC29I - MESSAGE EVENT PROCESSING STOPPED.
c. Enter: XON
Output from the XON command:
21
81
XON
TRAC29I - MESSAGE EVENT PROCESSING STARTED.
Chapter 4. Recovery 85
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
89
90
91
92
93
96
Note: For more information about database recovery planning, see the
Planning and Implementation Guide.
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
CA-Jobtrac
COMMAND ===>
AMR Table
Row 1 of 1
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
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.
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= 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.
2. Since this is usually a tape or cart job, add any site-specific requirements
you have such as a special job class.
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.
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.
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
106
107
108
109
110
112
113
114
115
117
118
119
120
121
122
123
124
125
126
132
133
137
138
139
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.
Contains
A(eventname)
A(JCL_buffer)
A(end_buffer)
A(EVT element)
A(time/date)
A(Greg_date)
Explanation
Contains
A(eventname)
A(user_ID)
A(temp_dsname)
A(volser)
Explanation
Contains
A(eventname)
A(JCL_buffer)
A(end_buffer)
A(EVT element)
A(time/date)
A(Greg_date)
Explanation
Use the JCL in the JCL buffer as the production JCL for the event.
Contains
A(first_date_card)
A(last_date_card)
A(orig_schd_date)
A(orig_Julian_date)
A(EVT element)
A(eventname)
Explanation
Contains
A(request_code)
04
08
12
16
20
A(caller's_@AUTH)
A(return_buffer)
Explanation
00
04
08
12
Reserved.
16
Contains
A(eventname)
A(EVT element)
A(current_T/D)
Contains
A(EVT element)
A(eventname)
A(jobname)
A(user_ID)
A(parms)
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.
Contains
A(calltype)
XL1 flag:
1
A(index_rec)
A(line_len)
A(line_buffer)
Contains
A(calltype)
Set ARHD,
PRNT
Set DELRQ
Set
NODELRQ
Set REWRIX
A(isa)
A(index)
Change Index
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.
Contains
A(eventname)
A(EVT element)
A(flag)
A(var)
Exit: On return, any nonzero return code denies scheduling of the event. This
exit can alter the EVT element if necessary.
Contains
A(cmd_buffer)
A(flagbyte)
A(cmdset_name)
x'20'
x'40'
x'80'
Operator request
Contains
A (jobname&userid)
A(EVT element)
Exit: On return, any nonzero return code denies execution of the AUTO-SCHD
event. A JCL error results. Message TRAC024C is issued.
Contains
A(eventname)
A(JMF_name)
A(date)
A(data_area)
Explanation
00
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
Contains
A(eventname)
A(jclinit)
A(jclfin)
Explanation
00
04
Contains
A(eventname)
A(EVT element)
Explanation
00
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.
Contains
A(busgrp)
A(eventname)
A(name)
A(rtrycnt)
A(rtryint)
Explanation
00
04
Contains
A(busgrp)
A(eventname)
A(EVT element)
Explanation
00
04
Contains
A(eventname)
A(jmf_name)
A(date)
A(data_area)
A(EVT element)
Explanation
00
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
JCL3TRAC initialization
Current statement
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.
The following input parameters are used:
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.
The following input parameters are used:
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.
The following input parameters are used:
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.
The following input parameters are used:
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.
This macro has the following format:
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:
Explanation
The warning message was not written because the NOWARN option
was in effect.
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.
This macro has the following format:
@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
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
ICM
ICM
@SCAN ()
R,R
R,2,=AL1(DISP)
R,1,=AL1(DSTAT)
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
Contains
A(volser)
A(vault)
A(slot)
A(jobname)
A(date)
Events
Global options
Contains
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'
x'06'
x'07'
x'08'
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
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).
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
attempting
to view
the
details of
an event
User is
attempting
to update
an event
User is
attempting
to add an
event
User is
attempting
to delete
an event
User is
attempting
to purge
an event
User is
attempting
to list
events
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
attempting
to view
an ADR,
AMR,
SCS, or
CCPF
table
--
--
User is
attempting
to update,
add, or
delete an
ADR,
AMR,
SCS, or
CCPF
table
--
--
Security Area
x'01'
x'02'
x'04'
x'08'
x'10'
x'20'
Sysouts
User is
attempting
to view a
Unicenter
CA-Jobtrac
captured
sysout
--
--
User is
attempting
to delete
or
undelete
a
Unicenter
CA-Jobtrac
captured
sysout
--
--
NJE
Remotely-Submitted
jobs
User is
attempting
to view
the
details of
an event
User is
attempting
to update
an event
--
--
--
User is
attempting
to list
events
Remote
Credentials
User is
attempting
to view
current
remote
credentials
User is
attempting
to update
a remote
credentials
member
User is
attempting
to add a
new
remote
credentials
member
--
--
User is
attempting
to list
events
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.
Contains
A(dsname)
A(ddname)
A(userid)
User ID.
Explanation
00
08
Contains
A(type)
Documentation library
C'I'
IMOD
C'J'
JCL library
C'P'
C'S'
SCL library
C'T'
A(locid)
A(membername)
A(macroname)
A(ddname)
8-byte ddname.
A(isetname)
A(messageid)
Explanation
Continue the edit, but use the parameters returned by the exit.
12
Do not continue the edit. The exit has handled the edit. Display the
returned message if unequal to blank.
Contains
A(eventname)
A(EVT element)
A(jcl_image)
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
nn
Any nonzero return code treats the job as a local, non-NJE job.
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . .
142
143
147
148
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
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.
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
150
155
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.
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'
INDXBB
DC XL2'00'
2-3
INDXCHR
DS CL5
Index CCHHR
4-8
INDXKLDL
DC AL3(L'POINTER)
9 - 11
--
DC XL1'0'
Reserved
12
INDXIBT
DC H'0'
13 - 14
INDXCYL
DC H'0'
15 - 16
DATACYL
DC H'0'
17 - 18
--
DS CL2
Reserved
19 - 20
DATALSCC
DS XL2
21 - 22
DATAM
DC XL1'00'
23
DATABB
DC XL2'00'
24 - 25
DATACHR
DS XL5
Data CCHHR
26 - 30
DATABLEN
EQU 3860
--
--
DATAKLDL
DC AL3(DATABLEN)
31 - 33
--
DC XL1'0'
Reserved
34
DATADBT
DC H'0'
35 - 36
TRKCYL
DC H'0'
37 - 38
MYREL
DC C'21X'
39 - 41
--
DC CL8' '
Reserved
42 - 49
MYSKM
DC X'00'
50
MYSKBB
DC XL2'00'
51 - 52
MYSKCHR
DS XL5
53 - 57
MYDEVICE
DS CL6
58 - 63
MYUCBT4
DS C
UCBTYP byte 4
64
FINXCHR
DS XL5
65 - 69
Field
Description
Comments
Position
FDATCHR
DS XL5
70 - 74
--
DC CL42' '
Reserved
75 - 116
Layout of the Index Records: The following table describes the layout of the
actual index records in the index:
Field
Description
Comments
Position
INXJOBNM
DS CL8
Jobname
1- 8
INXJOBID
DS CL8
JES job ID
9 - 16
INXRIYR
DS CL2
17 - 18
INXRDAT
DS CL6
19 - 24
INXBTM
DS CL6
25 - 30
INXETM
DS CL6
31 - 36
INXCMPC
DS CL2
37 - 38
INXCPID
DS CL4
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
53 - 57
INXDAT@
DS CL5
58 - 62
INXTYPE
DS CL3
Record INXTYPE
63 - 65
INXCTYP
DS C
66
INXBCT
DS H
67 - 68
INXWRAP
DS C
69
INXDELF
DS C
70
INXPP
DS CL10
71 - 80
INXLN#
DS PL4
81 - 84
INXFORM
DS CL4
85 - 88
INXDEST
DS CL8
Job destination ID
89 - 96
INXUWTR
DS CL8
User writer ID
97 - 104
INXCOPY
DS H
105 - 106
INXMLREC
DS H
Maximum LRECL
107 - 108
INXSQ
DS CL1
109
--
DS CL3
Reserved
110 - 112
INXUSER
DS F
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
4
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
Best Case
Normal Case
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
13 78 15 = 1521
<
>
88 11 15 = 1452, but
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)
max((floor(3.25)
max((
3
max((
3
max((
3
,min(ceil(5),13))
,min(ceil(5),13))
,min(ceil(5),13))
,min( 5
,13))
,
5
)
5
equals
equals
equals
equals
equals
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
This section contains the following topics:
Diagnostic Procedures . . . . . . .
. . . . . . . .
Problem Resolution
Access the Online Support System
Contact Technical Support . . . .
Product Releases and Maintenance
Request Enhancements . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . .
162
163
165
166
167
168
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.
Procedure
Installation
Problem Resolution
What circumstances existed when the problem occurred and what action did
you take?
Did the problem occur after a particular PTF was applied or after a new
release of the software was installed?
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.
Knowledge Base
Solution downloads
Product downloads
E-News newsletters
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.
Product name and release number of any other software you suspect is
involved.
Request Enhancements
Request Enhancements
CA welcomes your suggestions for product enhancements. All suggestions are
considered and acknowledged. Contact your Account Manager.
Index
Special Characters
@AUTH macro
statement examples 148
termination statement 147
user authorization profile statement
@ERRM macro 128
@HOLD command 80
@JCLKEY macro 128
@JCLTXT macro 128
@JOBTRAC utility exit 113
@PUTM macro 129
@SCAN macro 130
143
Numerics
0ARCHIVE task 12, 61, 80
0JOBARCH task 12, 61
0SYSARCH task 80
A
adding events with GJTRABTR
Advantage CA-Datacom/DB 10
altering the schedule in batch mode 35
AMR recovery procedures 84
archival 60, 62
archive
event exit 122
event history report 12
parameter 80
archiving event information in batch mode
argument records 66
authorization codes, obtaining 165
AUTO-SCHD exit 119
B
BACK command 83
backing up the database
87
C
CA Support Online 165
CA-Datacom/AD 10
CA-Easytrieve reporting 13, 15
CA-JCLTrac
standards enforcement exit 126
tape management system interface exit
CA-JCLTrac PROCLIB dynamic allocation
TRACX28 137
CA-Jobtrac library edit
TRACX29 138
CA-TCC
See CA Support Online
CA-TLC
See Licensing
checkpoint
record types 66
commands
@HOLD 80
BACK 83
condition code records 66
condition code, using to abend event 36
Cross-platform support exit 140
Customer Support
See Technical Support
132
62
data sets
sysout capture 80
database
backup 87
deleting records from 70
Date card calculation and insertion exit 109
DB00308I message 97
deleting
events 36
records from database 70
temporary-use JCL library members 68
dumps 73
dynamic archives
GJTRJARC parameters 66
E
Environmental dependency retry exit
eSupport
See CA Support Online
event
archival of 60
posting 36
123
Index 169
event (continued)
purging 36
records 66
recovering status 83
Event archive exit 122
events on current schedule, listing
JMF (continued)
pre-resolution exit 120
JTEZREPT Report Utility 13, 15
62
F
forecast database ID
fuzzy backup 98
98, 99
G
ghost records 66
GJTRABTR
command summary 50
command syntax 48, 49
returned information 40
uniquely identifying an event for
GJTRABTR and @JOBTRAC 35
GJTRABTR utility
commands 52
description of 35
invoking with CLIST 59
invoking with JCL 58
GJTRABTR utility exit 113
GJTRJARC PROC 61
GJTRJARC utility 62
GJTRJPRG utility 70
GJTRMAJC utility 68
GJTRVMFT utility 67
GJTRVRLD procedures 80
60
N
NJE ROUTE/XEQ statement exit
36
118
P
posting events 36
primary system, switching
purging events 36
74
R
record types, checkpoint 66
recovery file 90
remote access to Unicenter CA-Jobtrac 36
reports
CA-Easytrieve 13, 15
listing events on current schedule 62
REXX IMOD submission exit 124
RXX file 90
13
165
J
JCL submission exit
after JCL read 106
before JCL read 108
JMF
dynamic variable preprocessor exit
post-processor exit 121
139
Internet, CA site
62
125
schedule
adding event with GJTRABTR
batch alteration of 35
deleting event 36
scan exit 112
update exit 117
updating information 36
36
security
TRACX26 security exit 133
spill jobs 96
Standards enforcement exit 126
StarTCC
See CA Support Online
static backup 98
status, recovering event 83
sysout
archival 80
archival of 60
archive exit 115
browse authorization exit 107
capture 80
capture exit 114
moving capture data set 81
recovering 80
reloading after archive 82
viewing 149
sysout capture file
compression methods 155
contents described 150
copying 67
determining size, detail 156
enlarging 67
formatting 67
increasing index size 67
moving 67
overview 149
structure described 150
T
Tape management system interface exit 132
tapes
using for sysout archival 60
temporary-use JCL library, deleting members
from 68
TRACAUTH interface exit 110
TRACAUTH table
assembling and linking the default 142
tracking records 66
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
REXX 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 138
TRACX30
NJE ROUTE/XEQ statement exit 139
TRACX31
Cross-platform support exit 140
Troubleshooting 161167
U
Unicenter CA-11 92
Unicenter CA-View 149
user exits 106
AUTO-SCHD exit 119
Index 171
V
version number
deleting event with
36