Professional Documents
Culture Documents
Unic Job-Management PDF
Unic Job-Management PDF
Unic Job-Management PDF
® ™
Management
Third Edition
This documentation and any related computer software help programs (hereinafter referred to as the
“Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by CA at
any time.
This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in
part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA
and protected by the copyright laws of the United States and international treaties.
Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the documentation for
their own internal use, and may make one copy of the related software as reasonably required for back-up and
disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy.
Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for
the product are permitted to have access to such copies.
The right to print copies of the documentation and to make a copy of the related software is limited to the period
during which the applicable license for the Product remains in full force and effect. Should the license terminate for
any reason, it shall be the user’s responsibility to certify in writing to CA that all copies and partial copies of the
Documentation have been returned to CA or destroyed.
EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY
APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING
WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE
OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY
LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT
LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY
ADVISED OF SUCH LOSS OR DAMAGE.
The use of any product referenced in the Documentation is governed by the end user’s applicable license
agreement.
Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the
restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-
7014(b)(3), as applicable, or their successors.
All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.
3
4 Reports, Maintenance, and Recovery Guide
Contents
Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
CA-Datacom/AD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 2. Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Event Archive Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Historical Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
JTEZREPT Report Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Report Selection/Processing Options . . . . . . . . . . . . . . . . . . . . 16
Data Selection Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Reporting Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Report Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
History Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Display Schedule Report (Module GJTREZJW) . . . . . . . . . . . . . . 19
List Schedule Report (Module GJTREZJS) . . . . . . . . . . . . . . . . 23
List IPL Report (Module GJTREZIP) . . . . . . . . . . . . . . . . . . . . 28
List Audit Report (Module GJTREZAU) . . . . . . . . . . . . . . . . . . . 30
Chapter 3. Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Product Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Accessing the Current Schedule . . . . . . . . . . . . . . . . . . . . . . . 35
Using GJTRABTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
GJTRABTR Command Syntax . . . . . . . . . . . . . . . . . . . . . . . . 48
GJTRABTR Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
ABEND Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Add Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
DELete Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
DUMP Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
END Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Get Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
IMod Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Iserve Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
JTsys Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
MODify or POST Command . . . . . . . . . . . . . . . . . . . . . . . . 55
Node Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
PURge or PRG Command . . . . . . . . . . . . . . . . . . . . . . . . . 56
Query Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
STACK Command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
GJTRATBR Command Parameters . . . . . . . . . . . . . . . . . . . . . 58
Coding JCL to Invoke GJTRABTR Processing . . . . . . . . . . . . . . 58
Example of a CLIST Invoking GJTRABTR . . . . . . . . . . . . . . . . . 59
Performing Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Methods of Executing the Archivals . . . . . . . . . . . . . . . . . . . . . 61
About the GJTRJARC Utility . . . . . . . . . . . . . . . . . . . . . . . . . 62
GJTRJARC PROC Parameters . . . . . . . . . . . . . . . . . . . . . . . 63
Modifying the Sysout Capture File . . . . . . . . . . . . . . . . . . . . . . . . 67
Contents 5
Deleting Members from Temporary-Use JCL Libraries . . . . . . . . . . . . 68
GJTRMAJC Utility Parameters . . . . . . . . . . . . . . . . . . . . . . . . 69
Deleting Archived Records with GJTRJPRG . . . . . . . . . . . . . . . . . . 70
Chapter 4. Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Switch Primary Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Relocate the CA-Datacom/AD MUF . . . . . . . . . . . . . . . . . . . . . . . 76
Scheduled CA-Datacom/AD Outage . . . . . . . . . . . . . . . . . . . . 76
Relocate the CA-Datacom/AD MUF for Unicenter CA-Jobtrac Using the
SUSPEND/RESUME Commands . . . . . . . . . . . . . . . . . . . . . 77
Relocate the CA-Datacom/AD MUF for Unicenter CA-Jobtrac Using the
Auto EOJ Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Unscheduled CA-Datacom/AD Outage . . . . . . . . . . . . . . . . . . . 78
Shadow MUF Failover . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
Recover the Sysout Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Recover the Status of Events . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
AMR Recovery Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Contents 7
8 Reports, Maintenance, and Recovery Guide
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.
Chapter 2. Reports 11
Event Archive Report
To access this report through the Sysout Capture Facility, enter the following
command in the COMMAND field:
O ARCHIVE
For complete information about viewing and printing sysouts, see the managing
sysout information in the Operator Guide.
EVENT TABLE CURRENT BUSINESS SCHEDULED SUBMITTED STARTED COMPLETED SYS JOB COMP EVENT NJE
NAME VERSION TYPE STATUS LOC GROUP DATE TIME DATE TIME DATE TIME DATE TIME ID NUMBER CODE TYPE -
-------- -------------- ----- ---------- --- -------- ----- ----- ----- ----- ----- ----- ----- ----- ---- ------- ----- ----- -
BOB 2535.1 +EVT WAIT DEPS USER1 3/5 17.18 1/2 17.18 1/2 17.18 1/2 17.18 .... NORML JOB N
2538.1 +EVT WAIT DEPS USER1 3/8 12.47 1/2 12.47 1/2 12.47 1/2 12.47 .... NORML JOB N
2538.2 +EVT WAIT DEPS USER1 3/8 12.48 1/2 12.48 1/2 12.48 1/2 12.48 .... NORML JOB N
USER21R 2555.2 +EVT COMPLETE USER21 5/5 16.38 5/7 16.38 5/7 16.38 5/7 16.38 XE79 657 NORML JOB N
2555.2 +EVT COMPLETE USER21 5/5 16.38 5/5 16.38 5/5 16.38 5/5 16.38 XE79 648 NORML JOB N
REPTESTA 2512.1 +EVT WAIT DEPS SCLT2 1/2 2.3 1/2 2.3 1/2 2.3 1/2 2.3 .... NORML JOB N
2512.2 +EVT WAIT DEPS SCLT2 1/2 2.3 5/7 2.3 1/2 2.3 5/7 2.3 .... NORML JOB N
REPTESTB 2512.1 +EVT WAIT DEPS SCLT2 1/2 . 1/2 . 1/2 . 1/2 . .... NORML JOB N
JARED 25517.1 +EVT WAIT DEPS USER21 5/17 8.54 1/2 8.54 1/2 8.54 1/2 8.54 SCHD NORML JOB N
SCLT 2512.1 +EVT CC CHECK USER1 1/2 12.4 1/2 12.4 1/2 12.4 1/2 12.4 SCHD 648 S/8 JOB N
SCLT2 2512.1 +EVT COMPLETE USER1 1/2 12.2 1/2 12.2 1/2 12.2 1/2 12.2 SCHD 648 NORML JOB N
2512.1 +EVT CC CHECK USER1 1/2 12.2 1/2 12.2 1/2 12.2 1/2 12.2 SCHD S/8 JOB N
2512.1 +EVT CC CHECK USER1 1/2 12.2 1/2 12.2 1/2 12.2 1/2 12.2 SCHD ....... S/8 JOB N
JOB4 25112.1 +EVT WAIT DEPS MISSINGA 1/12 1.11 1/1 1.11 1/12 1.11 1/1 1.11 JOB N
+ARG THIS IS ARG THE IS TOOOOOOOOOOOO LONG TO FIT ON ONE CARD
+CCD 3LT4
+PST/PRED JOBTEST225112.1?
+PST/PRED JOBTEST225112.1?
+PST/PRED JOBTEST325112.1?
+PST/PRED JOBTEST425112.1?
+PST/PRED JOBTEST525112.1?
Symbols on the Report: The filtering criteria for selecting STT records for
participation in this report are as follows:
SYSTEM TOKEN (STT1-F-TOKEN)
Defines the one-character Unicenter CA-Jobtrac system ID to select or * for
all systems. This is required.
HISTORY INDICATOR (STT1-F-HIST)
Specifies whether to select archived records. Values are Y to include, N to
exclude, or * for both.
SYSTEM ID (STT1-F-SYSTEM)
Specifies a four-character SMF system ID to include. This can be generic
using the * character. The entry SYB* would list all system IDs starting with
SYB.
REPORTING LEVEL (STT1-F-LEVEL)
Specifies either DETL for listing individual detail STT records selected or
SUMM to list only a summary of the total of the selected detail.
REPORT DATE FORMAT (STT1-F-DATEFM)
Specifies the format of report dates in the data shown as I International
(YYYY/DD/MM) or A American (YYYY/MM/DD).
REPORTING INTERVAL (STT1-F-STTFDAT, STT1-F-STTFTIM,
STT1-F-STTTDAT, STT1-F-STTTTIM)
Specifies the FROM and THRU period for which STT records are selected.
Use the format of YYYY/MM/DD HH:MM:SS for this field.
Chapter 2. Reports 13
Historical Summary Report
82 79
Each module also has three sections of the code where modifications can
easily be made affecting the content and format of the detail report, each of
these sections is clearly documented and enclosed in a ///////////// border so that
the sections are easily located.
Data Selection Filtering: You can modify the data selection code to exceed
the functions pre-programmed and allowed in the previous section. The data
selection code actually interrogates the data and selects those records to
participate in the report.
Chapter 2. Reports 15
JTEZREPT Report Utility
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.
■ History information is archived by the archive utility, GJTRJARC, which
selectively searches the active data and logically reassigns it to history
status, thus removing it from the active schedule. For more information
about this process and its reporting, see “About the GJTRJARC Utility” on
page 62.
■ History information is eliminated by the Purge Utility, GJTRJPRG, which
selectively searches data that has been archived and deletes it from the
database. For more information about this process and its reporting, see
“Deleting Archived Records with GJTRJPRG” on page 70.
If you are using Unicenter CA-11, see the Unicenter CA-11 Restart and
Tracking User Guide for a description of available reports concerning restart.
In the selection criteria of data for each report that follows, all the criteria
chosen must be met for the data item to participate in the report.
The available keywords (with corresponding data fields in parentheses) for the
control of this report's content are as follows:
TOKEN (EVT1-F-TOKEN)
Defines the one-character Unicenter CA-Jobtrac system ID.
HISTORY INDICATOR (EVT1-F-HISTIND)
Specifies how to process history records in the report.
Y
Specifies history only.
N
Specifies no history.
*
Specifies both history and active.
JOB or EVENT NAME (EVT1-F-JOBNAME)
Defines 1 to 8 characters of a name or a name prefix ended by * as in *,
ABC*, or xyz123*.
LOCATION (EVT1-F-LOC)
(Optional) Defines a three-character location code.
Default: * (all locations)
BUSINESS GROUP (EVT1-F-BUSGRP)
(Optional) Defines a 1 to 8 character business group name or name prefix
in the same format as the JOB or EVENT NAME.
Default: * (all business groups)
COMPLETION CODE (EVT1-F-COMPCD)
(Optional) Defines a final Unicenter CA-Jobtrac-assigned completion or * for
all.
Default: * (all)
ABNORMAL
Specifies abnormal ends; shown as (1).
CATLG
Specifies catalog problems (1).
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.
The following are sample reports for the Display Schedule report
(CA-Easytrieve module GJTREZJW):
195 143 52
Chapter 2. Reports 21
History Reporting
H JOB / ORIGINAL VRSN JES ID COMP CURR SCHEDULE SYS PROCESS SUBMIT START END RUN LOC BUSINESS
S EVENT SCHED DATE CODE STAT DATE TIME ID PERD/FREQ DATE TIME DATE TIME DATE TIME TIME GROUP
T NAME DESC
Y AJO1 25/3/22 1 J6369 DELRQ TERM 3/22 18:5 XE79 D=USERB1 3/22 18:5 3/22 18:5 3/22 18:5 :<1 RJA1
Y GOBRUCE 25/3/22 1 J6368 DELRQ TERM 3/22 18:5 XE79 D=USERB1 3/22 18:5 3/22 18:5 3/22 18:5 :<1 RJA1
Y JOB5 25/3/25 1 DELRQ WMAN 3/25 13:8 D=USER11 OJO1
DEPENDENCIES: M
Y JOHN 25/3/24 1 J6258 DELRQ TERM 3/24 14:27 XE79 D=USER11 3/24 14:29 3/24 14:29 3/24 14:29 :<1 OJO1
Y JOHN 25/3/24 1 J6257 DELRQ TERM 3/24 14:27 XE79 D=USER11 3/24 14:28 3/24 14:29 3/24 14:29 :<1 OJO1
Y JOHN 25/3/24 1 J6267 DELRQ TERM 3/24 14:27 XE79 D=USER11 3/24 15:12 3/24 15:12 3/24 15:12 :<1 OJO1
Y JOHN 25/3/24 1 J6266 DELRQ TERM 3/24 14:27 XE79 D=USER11 3/24 15:11 3/24 15:11 3/24 15:11 :<1 OJO1
Y JOHN 25/3/24 1 J6265 DELRQ TERM 3/24 14:27 XE79 D=USER11 3/24 15:9 3/24 15:9 3/24 15:9 :<1 OJO1
Y JOHN 25/3/24 1 J6264 DELRQ TERM 3/24 14:27 XE79 D=USER11 3/24 15:8 3/24 15:8 3/24 15:8 :<1 OJO1
Y JOHN 25/3/24 1 J6263 DELRQ TERM 3/24 14:27 XE79 D=USER11 3/24 15:7 3/24 15:7 3/24 15:7 :<1 OJO1
Y JOHN 25/3/24 1 J6261 DELRQ TERM 3/24 14:27 XE79 D=USER11 3/24 14:51 3/24 14:51 3/24 14:51 :<1 OJO1
N JOHN 25/3/24 1 WSCH 3/24 14:27 RR- OJO1
DEPENDENCIES: J
N JOHN1 25/3/24 1 J6289 U495 TERM 3/24 16:31 XE79 RR- 3/24 17:9 3/24 17:9 3/24 17:9 :<1 OJO1
N JOHN1 25/3/24 1 WSCH 3/24 16:31 RR- OJO1
DEPENDENCIES: J
Y JOHN1 25/3/24 1 J6282 DELRQ TERM 3/24 16:31 XE79 D=USER11 3/24 16:33 3/24 16:33 3/24 16:33 :<1 OJO1
Y JOHN1 25/3/24 1 J6281 DELRQ TERM 3/24 16:31 XE79 D=USER11 3/24 16:32 3/24 16:32 3/24 16:32 :<1 OJO1
Y JOHN1 25/3/24 1 J6286 DELRQ TERM 3/24 16:31 XE79 D=USER11 3/24 16:33 3/24 16:33 3/24 16:34 :1 OJO1
Y JOHN1 25/3/24 1 J6285 DELRQ TERM 3/24 16:31 XE79 D=USER11 3/24 16:33 3/24 16:33 3/24 16:33 :<1 OJO1
Y JOHN1 25/3/24 1 J6284 DELRQ TERM 3/24 16:31 XE79 D=USER11 3/24 16:33 3/24 16:33 3/24 16:33 :<1 OJO1
Y JOHN1 25/3/24 1 J6283 DELRQ TERM 3/24 16:31 XE79 D=USER11 3/24 16:33 3/24 16:33 3/24 16:33 :<1 OJO1
Y JOHN1 25/3/24 1 J6288 DELRQ TERM 3/24 16:31 XE79 D=USER11 3/24 16:34 3/24 16:34 3/24 16:34 :<1 OJO1
Y JOHN1 25/3/24 1 J6287 DELRQ TERM 3/24 16:31 XE79 D=USER11 3/24 16:34 3/24 16:34 3/24 16:34 :<1 OJO1
Y JOHN2 25/3/24 1 DELRQ TERM 3/24 18:12 D=USER11 3/24 18:12 :<1 OJO1
Y JOHN3 25/3/24 1 TERM 3/24 18:45 D=USER11 OJO1
DEPENDENCIES: J
Y JOHN3 25/3/24 1 J6298 U495 TERM 3/24 18:45 XE79 RR- 3/24 18:46 3/24 18:46 3/24 18:46 :<1 OJO1
Y JOHN3 25/3/24 1 J6297 U495 TERM 3/24 18:45 XE79 RR- 3/24 18:46 3/24 18:46 3/24 18:46 :<1 OJO1
Y JOHN3 25/3/24 1 J6296 U495 TERM 3/24 18:45 XE79 RR- 3/24 18:45 3/24 18:45 3/24 18:45 :<1 OJO1
Y JOHN3 25/3/24 1 J6295 U495 TERM 3/24 18:45 XE79 RQ-USER11 3/24 18:45 3/24 18:45 3/24 18:45 :<1 OJO1
Y JOHN3 25/3/24 1 J632 U495 TERM 3/24 18:45 XE79 RR- 3/24 18:47 3/24 18:47 3/24 18:47 :<1 OJO1
Y JOHN3 25/3/24 1 J631 U495 TERM 3/24 18:45 XE79 RR- 3/24 18:47 3/24 18:47 3/24 18:47 :<1 OJO1
Y JOHN3 25/3/24 1 J63 U495 TERM 3/24 18:45 XE79 RR- 3/24 18:46 3/24 18:46 3/24 18:46 :<1 OJO1
Y JOHN3 25/3/24 1 J6299 U495 TERM 3/24 18:45 XE79 RR- 3/24 18:46 3/24 18:46 3/24 18:46 :<1 OJO1
Y JOHN3 25/3/24 1 J6298 U495 TERM 3/24 18:45 XE79 RR- 3/24 18:46 3/24 18:46 3/24 18:46 :<1 OJO1
Y JOHN3 25/3/24 1 J6297 U495 TERM 3/24 18:45 XE79 RR- 3/24 18:46 3/24 18:46 3/24 18:46 :<1 OJO1
H JOB / ORIGINAL VRSN JES ID COMP CURR SCHEDULE SYS PROCESS SUBMIT START END RUN LOC BUSINESS
S EVENT SCHED DATE CODE STAT DATE TIME ID PERD/FREQ DATE TIME DATE TIME DATE TIME TIME GROUP
T NAME DESC
The available keywords (with corresponding data fields in parentheses) for the
control of this report's content are as follows:
TOKEN (EVT1-F-TOKEN)
Defines the one-character Unicenter CA-Jobtrac system ID.
HISTORY INDICATOR (EVT1-F-HISTIND)
Specifies how to process history records in the report.
Y
Specifies history only.
N
Specifies no history.
*
Specifies both history and active.
JOB or EVENT NAME (EVT1-F-JOBNAME)
Defines 1 to 8 characters of a name or a name prefix ended by * as in *,
ABC*, or xyz123*.
LOCATION (EVT1-F-LOC)
(Optional) Defines a three-character location code.
Default: * (all locations)
BUSINESS GROUP (EVT1-F-BUSGRP)
(Optional) Defines a 1 to 8 character business group name or name prefix
in the same format as the JOB or EVENT NAME.
Default: * (all business groups)
COMPLETION CODE (EVT1-F-COMPCD)
(Optional) Defines a final Unicenter CA-Jobtrac assigned completion or * for
all.
Default: * (all)
ABNORMAL
Specifies abnormal ends; shown as (1).
CATLG
Specifies catalog problems (1).
FORCED
Specifies forced completion (1).
CCnn
Specifies maximum completion code nn on a job step.
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 =' '
The following example would select only batch jobs:
EVT1-F-EVTTYPE =' '
The following example would select commands, dummy jobs and remote
REXX PROCs (batch jobs would not be selected because the trailing
blanks are ignored):
EVT1-F-EVTTYPE ='CDE '
The following example would select batch jobs and dummy jobs (because a
blank indicating batch job is specified before a non-blank event code):
EVT1-F-EVTTYPE =' D '
DATE FORMAT (EVT1-F-DATEFMT)
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 the original Schedule Date from and through.
START (EVT1-F-STRFDAT, EVT1-F-STRFTIM, EVT1-F-STRTDAT,
EVT1-F-STRTTIM)
Specifies the actual start date and time, from and through.
SUBMIT (EVT1-F-SUBFDAT, EVT1-F-SUBFTIM, EVT1-F-SUBTDAT,
EVT1-F-SUBTTIM)
Specifies the submitted date and time, from and through.
END (EVT1-F-ENDFDAT, EVT1-F-ENDFTIM, EVT1-F-ENDTDAT,
EVT1-F-ENDTTIM)
Specifies the job end date and time, from and through.
TARGET (EVT1-F-TGTFDAT, EVT1-F-TGTFTIM, EVT1-F-TGTTDAT,
EVT1-F-TGTTTIM)
Specifies the target scheduled date and time, from and through. The FROM
date and time can specify ASAP to select those events that were
designated with an ASAP.
ARCHIVE (EVT1-F-ARCFDAT, EVT1-F-ARCFTIM, EVT1-F-ARCTDAT,
EVT1-F-ARCTTIM)
Specifies the archive on date and time, from and through. This value is only
valid if the HISTORY INDICATOR is either Y or *.
Chapter 2. Reports 25
History Reporting
The following are sample reports for the List Schedule report (CA-Easytrieve
module GJTREZJS):
H T JOB / JES ID EVENT SCHEDULE ORIGINAL SYS COMPL CURR PROCESS SUBMIT START END RUN LOC BUSINESS
S Y EVENT VRSN DATE TIME SCHED DATE ID CODE STAT PERD/FREQ DATE TIME DATE TIME DATE TIME TIME GROUP
T P NAME NO DESC
4/3 : EST
Y APMPINF J 1 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : EST1
Y APMPINF J 2 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : EST
Y APMP1HIS J 1 4/3 : 26/4/3 .... NORML WMAN FOM 4/3 : EST1
Y APMP1HIS J 2 4/3 : 26/4/3 .... NORML WMAN FOM 4/3 : EST
Y APMP1INF J 1 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : EST1
Y APMP1INF J 2 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : EST
Y APMP1INM J 2 4/3 : 26/4/3 .... NORML WMAN FOM 4/3 : EST1
Y APMP2HIS J 1 4/3 : 26/4/3 .... NORML WMAN FOM 4/3 : EST
Y APMP2HIS J 2 4/3 : 26/4/3 .... NORML WMAN FOM 4/3 : EST1
N APMP2INF J 1 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : EST
N APMP2INF J 2 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : EST1
Y BDCDN95 J6161 34 12/29 : 25/12/29 X... NORML TERM DAILY 1/22 12:15 1/22 22:43 1/22 22:43 :<1 93
Y BDCDN98 J662 16 12/28 : 25/12/28 X... NORML TERM DAILY 1/26 18:48 1/26 18:48 1/26 18:48 :<1 93
Y BDCDO95 J678 4 12/31 : 25/12/31 X... NORML TERM M=BYPASS 1/26 22:27 1/26 22:27 1/26 22:27 :<1 93
Y BDCDO951 J6868 55 12/28 : 25/12/28 X... NORML TERM M=BYPASS 1/27 16:11 1/27 16:12 1/27 16:12 :<1 93
Y BDCDO952 J 1 9/28 : 25/9/28 .... NORML TERM DAILY 93
Y BDCDO953 J 1 9/28 : 25/9/28 .... NORML TERM DAILY 93
Y BDCDTXDL J6399 17 12/3 : 25/12/29 X... NORML TERM DAILY 1/22 12:15 1/22 23:2 1/22 23:2 :<1 93
Y BDCDT1 1 4/6 15:5 25/4/6 .... NORML TERM RQ-MISSING 4/6 15:9 4/6 15:9 4/6 15:9 :<1
Y BDCDXOP2 J6145 4 1/1 : 25/12/31 X... NORML TERM DAILY 1/2 19:22 1/2 2:9 1/2 2:9 :<1 93
Y BDCDX5 1 4/6 15:5 25/4/6 .... NORML TERM RQ-MISSING 4/6 15:1 4/6 15:1 4/6 15:1 :<1
Y BDCDX31 J6324 49 12/3 : 25/12/29 X... NORML TERM DAILY 1/22 12:15 1/22 21:47 1/22 21:47 :<1 93
Y BDCDX83 J6348 19 12/29 : 25/12/29 X... NORML TERM DAILY 1/22 12:15 1/22 21:48 1/22 21:48 :<1 93
Y BDCDX94 J6667 8 12/31 : 25/12/3 X... NORML TERM DAILY 1/22 12:15 1/22 22:7 1/22 22:7 :<1 93
Y BDCDX95 J6857 23 12/3 : 25/12/29 X... NORML TERM DAILY 1/22 12:15 1/22 22:2 1/22 22:2 :<1 93
N D BNADFLD1 DUMMY 4 12/31 : 25/12/31 .... NORML TERM =MTWTF.. 1/21 1:16 1/21 1:16 1/21 1:16 :<1 93
N D BNADFLD2 DUMMY 4 12/31 : 25/12/31 .... NORML TERM DAILY 1/21 1:16 1/21 1:16 1/21 1:16 :<1 93
Y BSJCP24 J17789 3 4/11 : 26/4/11 CA31 NORML TERM DAILY 4/11 1:53 4/11 1:53 4/11 1:53 :<1 SCP2
Y BSJCP24 J18143 4 4/11 : 26/4/11 CA31 NORML TERM DAILY 4/11 11:8 4/11 11:9 4/11 11:9 :<1 SCP2
Y C BSJXP15 COMMAND 1 1/18 : 26/1/18 .... NORML TERM RR-REMOT SXP5
Y C BSJXP15 COMMAND 2 1/18 : 26/1/18 C... NORML WEXE DAILY 1/18 8:15 1/18 8:16 1/18 8:16 :<1 SXP2
Y C BSJXP15 COMMAND 3 1/18 : 26/1/18 C... NORML WEXE DAILY 1/18 15:18 1/18 15:18 1/18 15:18 :<1 SXP2
Y GLMP1PYR J 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y D GLMP1RBD DUMMY 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y D GLMP1RBD DUMMY 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1SAC J 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1SAC J 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1SAS J 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1SAS J 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1SSJ J 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1SSJ J 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1STD J 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1STD J 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1UPD J 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP1UPD J 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y D GLMP2COM DUMMY 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y D GLMP2COM DUMMY 2 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
Y GLMP2CYP J 1 4/3 : 26/4/3 .... NORML TERM WORKDAYS 4/3 : EST
DESCRIPTION TOTAL
------------------------------ ---------
TOTAL RECORDS READ 13,61
ACTIVE RECORDS SELECTED 1,174
ARCHIVED RECORDS SELECTED 11,887
Chapter 2. Reports 27
History Reporting
The available keywords (with corresponding data fields in parentheses) for the
control of this report's content are as follows:
TOKEN (IPL1-F-TOKEN)
Defines the one-character Unicenter CA-Jobtrac system ID.
SYSTEM ID (IPL1-F-SYSTEM)
Defines 1-4 characters of a system name or a name prefix ended by * as in
*, ABC*, or xyz1.
IPLED BY NAME (IPL1-F-IPLEDBY)
(Optional) Defines a 1-12 character operator name.
Default: * (all)
IPL TYPE (IPL1-F-IPLTYPE)
(Optional) Defines a one-character IPL code type.
Default: * (all)
C
Specifies a cold start IPL.
N
Specifies a normal IPL.
*
Specifies all.
IPL REASON (IPL1-F-IPLREASON)
(Optional) Defines a 1-39 character reason for the IPL. The reason can be
a character string ending in *.
Default: * (all)
IPLED (IPL1-F-IPLFDAT, IPL1-F-IPLFTIM, IPL1-F-IPLTDAT, IPL1-F-IPLTTIM)
Specifies a date and time of IPL optional parameters are FROM and THRU
limits for selection of data meeting all the preceding selection criteria. Any
date field can be TODAY or * that is treated as today's date (the date of the
report execution). Leaving the field blank is treated as choosing any
date/time. Date formats are yyyy/mm/dd. Time formats are hh:mm:ss.
DATE FORMAT (IPL1-F-DATEFMT)
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 are sample reports for the List IPL report (CA-Easytrieve module
GJTREZIP):
2 2
Chapter 2. Reports 29
History Reporting
The available keywords (with corresponding data fields in parentheses) for the
control of this report's content are as follows:
TOKEN (AUD1-F-TOKEN)
Defines the one-character Unicenter CA-Jobtrac system ID.
JOB or EVENT NAME (AUD1-F-JOBNAME)
Defines 1 to 8 characters of a name or a name prefix ended by * as in *,
ABC*, or xyz123*.
USER ID (AUD1-F-USERID)
(Optional) Defines a 1 to 8 character operator name.
Default: * (all)
OSD (AUD1-F-OSDFDAT, AUD1-F-OSDTDAT)
Specifies the original schedule date from and through.
DATE FORMAT (AUD1-F-DATEFM)
Specifies the format of printed dates:
I
Specifies the international format of YYYY/DD/MM.
A
Specifies the American format of YYYY/MM/DD.
AUDIT (AUD1-F-AUDFDAT, AUD1-F-AUDFTIM, AUD1-F-AUDTDAT,
AUD1-F-AUDTTIM)
(Optional) Defines a date and time of audited change. The parameters are
FROM and THRU limits for selection of data meeting all the preceding
selection criteria. These date fields can be TODAY or * that is treated as
today's date (the date of the report execution). Leaving the field blank is
treated as choosing any date/time. Date formats are yyyy/mm/dd. Time
formats are hh:mm:ss.
The following are sample reports for the List Audit report (CA-Easytrieve
module GJTREZAU):
4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:2:5 USERB1 SEV ISPF ADDED SEV +
4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:4:4 USERB1 EVT ISPF CHANGED EVT +
4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:26:19 USERB1 EVT ISPF CHANGED EVT +
4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:5:33 USERB1 EVT ISPF CHANGED EVT +
11,585 154
Chapter 2. Reports 31
32 Reports, Maintenance, and Recovery Guide
Chapter 3. Maintenance
This section contains the following topics:
Product Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Performing Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Modifying the Sysout Capture File . . . . . . . . . . . . . . . . . . . . . . . . 67
Deleting Members from Temporary-Use JCL Libraries . . . . . . . . . . . . 68
Deleting Archived Records with GJTRJPRG . . . . . . . . . . . . . . . . . . 70
Chapter 3. Maintenance 33
Product Maintenance
Product Maintenance
The Unicenter CA-Jobtrac tasks and utilities offer the following capabilities:
■ Access to information on the current schedule from a batch job
■ Current schedule event archival
■ Sysout capture file archival
■ Modification to the sysout capture file
■ Deletion of members from the temporary-use JCL libraries
■ Deletion of records from the Unicenter CA-Jobtrac history database
These tasks will have a 'J' dependency that needs to be removed so that they
can execute. They also appear on an exceptions display.
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:
■ To cause an event to abend when a defined condition code occurs.
■ To interact with Unicenter CA-Jobtrac without accessing the Unicenter
CA-Jobtrac ISPF interface.
■ To test certain modifications to the current schedule.
You can invoke GJTRABTR using any of the following methods. Unicenter
CA-Jobtrac does not have to be running to use GJTRABTR.
■ Coding JCL to invoke the GJTRABTR program. The JCL can be submitted
either in batch or by Unicenter CA-Jobtrac.
■ Creating a TSO CLIST (command list) or other user program.
■ Performing an online transaction (for example, using the TSO CALL
command).
Each method requires you to specify parameters to perform the actions you
want.
When you modify, delete, purge, or search for an event, you might want to
uniquely identify the event. You can uniquely identify an event by specifying the
following parameters with a command:
■ JOBname
■ DATE
■ Version (or .vv in the JOBname parameter)
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.
GJTRABTR provides the following methods for specifying commands. You can
use one or both of them in a job.
Method Example
PARM statement IBM JCL restrictions limit GJTRABTR parameters to
100 characters, including punctuation.
//AB1 EXEC PGM=GJTRABTR,
// PARM='ADD(JOB(TESTJOB3),DEP(M))'
//AB5 EXEC PGM=GJTRABTR,
// PARM='A(JOB(TESTJ3),DEP(M?)) Q(JOB(TEST))'
//AB7 EXEC PGM=GJTRABTR,
// PARM='POST(JOB(TESTJ11),S(TESTJOB4))'
//AB3 EXEC PGM=GJTRABTR,
// PARM='PRG(JOB(TESTJOB),V(11))'
//AB8 EXEC PGM=GJTRABTR,
// PARM='Q(JOB(TESTJOB),V(2))'
//AB6 EXEC PGM=GJTRABTR,
// PARM='Query(JOB(TESTJOB3),S(TESTJOB4))'
STACK command //AB3 EXEC PGM=GJTRABTR,
and SYSIN // PARM='STACK()'
//SYSIN DD
ADD(JOB(TESTJOB3),DEP(M)) Q(JOB(TEST))
PRG(JOB(TESTJOB),V(11))
ADD(JOB(TESTJ3),DEP(M?))
POST(JOB(TESTJ11),S(TESTJOB4))
Q(JOB(TESTJOB),V(2))
Query(JOB(TESTJOB3),S(TESTJOB4))
With either method you can specify one or more commands at a time.
Follow all standard JCL syntax rules for parameters. Any syntax error in
parameters results in a message.
Chapter 3. Maintenance 37
Product Maintenance
The information in the stack is used as needed. So, if in the PARM statement
you start a command, but GJTRABTR does not find the ending parenthesis, it
will take information from the stack until it encounters the ending parenthesis. If
a new command is not started in the PARM statement after reading the first
one, GJTRABTR again takes information from the stack.
Same as
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.
All three commands are sent at one time. The stack would return the following:
■ Information about event C, if any was found, with a return code indicating
the success of obtaining information about event C.
■ A return code indicating the success of adding event D.
■ A return code indicating the success of finding event ABC.
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
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 Meaning (and Additional Information)
W Indicates waiting (retry count and retry interval.).
A Indicates abended (ID and a placeholder of a period.).
T Indicates terminated OK.
E Indicates executing.
For example:
IDEP ABCTEST W 23 1: START
IDEP XYZTEST T 72 .
IDEP AIH E 1 . END
JCNT
Identifies the job count associated with the event.
JENT
Identifies the actual end time of the event if the event already ended.
Returns the information in the hh:mm mm/dd format, including the colon
and slash.
JES#
Identifies the JES job number assigned if the event was submitted.
JOBN
Identifies the name of the event.
JSTT
Identifies the actual start time of the event if the event already started.
JLOC
Identifies the location ID assigned to the event.
JMAXC
Identifies the maximum condition code assigned to the event.
NJE
Identifies whether this event is an NJE job that has been submitted to
another JES node, the JES node name on which the event is executing or
has executed. Otherwise, this is blank.
NODE
Identifies the 16-character name of either the OS/390 GoalNet node or the
CAICCI node name for a scheduler or an agent where the event is
executing or has executed.
ONQU
Identifies whether this is an AUTO-SCHD event, indicates the event has
been submitted and recognized by Unicenter CA-Jobtrac. Otherwise, this is
blank.
PRED
Identifies the name of a predecessor the event has. There is one stack line
for each predecessor the event has. Each line contains the predecessor
name followed by the version number of the predecessor, original schedule
date, and a flag. The flag is set to C for completed and N for not
completed. For example:
PRED ABC 2 2/24 C
PRED AIH 2 2/24 C
PRED XYZ 2 2/25 N
PROP
Identifies the processing period for the event.
REXP
Identifies the argument passed to the event if this event is a REXX IMOD
and it has an argument associated with it.
RSMG
Identifies the resource codes associated with the event. Each code can be
either 1 or 2 characters in length. Each code is separated by a blank.
Note: This changed in Release 3.5.
STAT
Identifies the status of the event is as follows:
AB Abended
AG Performing post-abend tasks, such as executing a termination
IMOD
CC Condition code error
CG Performing post-condition code error tasks, such as capturing
sysout
DP Waiting for dependencies to be satisfied
EX Executing
HQ Waiting for dependencies, process period, or schedule time
requirements to be satisfied
OQ On the JES queue awaiting submission
TG Performing post-termination tasks, such as capturing sysout
TM Terminated, all post-termination tasks are completed
STIM
Identifies the scheduled start time and date for the event. Returns the
information in the hh:mm mm/dd format including the colon and slash.
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.
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.
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
┌─,──┐
parm┴──)─────────────────────────────────────────────
──command──(───
command
Identifies a GJTRABTR command.
parm
Identifies parameters that serve to qualify the command. You can use
multiple parameters, including multiples of the same parameter.
The following table explains the contents of the cells in the command summary
table:
Content Parameter is . . .
Not used with the command.
* Used with the command.
** Used with the command, but it identifies an event only.
You cannot change the information.
Additionally, the ABEND and END commands do not use any parameters.
Chapter 3. Maintenance 49
Product Maintenance
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
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.
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.
DUMP Command
The DUMP command searches the current schedule for an event and returns
information. The returned information is in typical IBM dump format showing
offsets, hexadecimal values, and character values.
Parameters you specify serve as search criteria. The information returned is for
the first event on the current schedule that matches the parameters. Dump lines
are returned in the stack, which are written to SYSPRINT, and are identified by
the MSG prefix.
END Command
The END command frees the address environment's resources. The next
GJTRABTR command reinitializes the address environment.
This is used with the Node, Iserve, and Imod commands only.
Get Command
The Get command searches the current schedule for an event and returns
information. Parameters you specify serve as search criteria. The information
returned is for the first event on the current schedule that matches the
parameters.
IMod Command
The IMod command executes the named REXX IMOD. The commands
specified in the GJTRABTR job are passed to the IMOD for its use. When the
GJTRABTR job is done, any information remaining in the stack goes to
SYSPRINT.
The IMod command must be specified before other commands (except the
Iserve, JTsys, or Node commands).
Using the IMod command invokes the use of CA-GSS. CA-GSS executes the
equivalent GJTRABTR commands in the CA-GSS address space.
──IMod(imodname)────────────────────────────────────────────────────
imodname
Defines a REXX IMOD name.
Limits: 1 to 16 characters
Chapter 3. Maintenance 53
Product Maintenance
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
──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.
JTsys Command
The JTsys command identifies the Unicenter CA-Jobtrac system you want to
use. x is the variable used in the Unicenter CA-Jobtrac checkpoint name to
distinguish multiple Unicenter CA-Jobtracs. This command identifies a Unicenter
CA-Jobtrac system that is running in the subsystem to which you submitted the
GJTRABTR job. You cannot specify a Unicenter CA-Jobtrac system in another
subsystem without using the Iserve or Node command.
The JTsys command must be specified before other commands (except the
IMod, Iserve, or Node commands).
──┬─JTsys─┬──(x)────────────────────────────────────────────────────
└─Token─┘
x
Defines a Unicenter CA-Jobtrac system variable.
Limits: 1 character. If you omit this command, the default primary
Unicenter CA-Jobtrac system in the subsystem is used.
The first event on the current schedule that matches the search criteria is
modified.
Chapter 3. Maintenance 55
Product Maintenance
Node Command
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.
──Node(nodename)────────────────────────────────────────────────────
nodename
Defines a node name.
Limits: 1 to 16 characters
The PURge command purges the event from the current schedule, and
removes the predecessor dependency from its successors. Parameters you
specify serve as search criteria. The first event on the current schedule that
matches the search criteria is purged.
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.
──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
PROC 3 C V D
/ SAMPLE SYNTAX ADD(JOB(TESTJOB1),V(1),DEP(NONE) /
CALL 'your.CAILIB(GJTRABTR)' '&C,&V,&D'
Note: You must have the JOBTRACx and JOBHISTx data sets allocated to
your TSO session. You also need to have the program name GJTRABTR
added to the AUTHPGM table in the IKJTSOxx PARMLIB member.
Chapter 3. Maintenance 59
Performing Archives
Performing Archives
Unicenter CA-Jobtrac offers the following archival abilities:
■ Clear completed events from the current schedule. This is referred to as
event history archival.
■ Archive the sysout capture file. This is referred to as sysout archival.
Event History Archival: At least once each work day, you should perform
event history archival (0JOBARCH or GJTRJARC PROC) to clear events from
the current schedule (Unicenter CA-Jobtrac checkpoint). Regular execution of
event history archival is important for smooth Unicenter CA-Jobtrac operation.
After an event is archived, you can display historical event information on the
Event History Display panel.
Note: For more information about the Event History Display panel, see the
Operator Guide.
Archived event records are retained for a specified period of time or number of
generations of each event. The time period and number of generations are
controlled by the GJTRJPRG utility (see “Deleting Archived Records with
GJTRJPRG” on page 70).
Sysout Archival: You should perform sysout archival to archive the sysout
capture file on a regular basis. Regular execution of sysout archival is important
for smooth Unicenter CA-Jobtrac operation.
During execution of the sysout archival, Unicenter CA-Jobtrac does not capture
any new sysouts. Once the archival is complete, sysout capture resumes.
Executing the Event History and Sysout Archival: You can perform event
history archival by using one of the following methods:
■ Invoking the GJTRJARC utility
■ Adding the 0ARCHIVE, 0JOBARCH, and 0SYSARCH task to the current
schedule using:
– A schedule
– The ADD command (the Event/Jobstream Addition panel)
– The RUN command
– The GJTRABTR utility
These tasks will produce a report listing all events on the current schedule
meeting specific criteria, by putting an 'O' next to the event on the status
display.
More information
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.
In the example, JS1 produces a report listing all events on the current
schedule. JS2 produces a report listing all events on the current schedule with
LATE, ABENDED, or WAITING status.
Chapter 3. Maintenance 63
Performing Archives
Chapter 3. Maintenance 65
Performing Archives
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.
Note: For more information about these optional records, see the Schedule
Creation Guide.
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.
Chapter 3. Maintenance 67
Deleting Members from Temporary-Use JCL Libraries
To use the GJTRMAJC utility, you invoke the GJTRMAJC PROC and specify
parameters to perform the required function.
──┬────────────────┬──┬───────────────────┬─────────────────────────
│ ┌─NODELETE─┐ │ │ ┌─$$$SPACE───┐ │
└──┴─DELETE───┴──┘ └─,─┴─membername─┴──┘
DELETE
Deletes any members in the TRACTnnn libraries that are not referenced by
events on the current schedule.
NODELETE
Lists members in the SYSPRINT and SYSUT2 data sets that are in the
TRACTnnn libraries and are not referenced by events on the current
schedule. Does not delete any members in TRACTnnn libraries.
Default: NODELETE
membername
Indicates the member to retain.
Default: $$$SPACE
Syntax Rule: Follow all standard JCL syntax rules for GJTRMAJC parameters.
Chapter 3. Maintenance 69
Deleting Archived Records with GJTRJPRG
You can use the GJTRJPRG PROC to delete old archived records based upon
their age, the number of records that exist for an event, or a combination of age
and number of records. The records deleted from the history database are no
longer kept except as printed output on the Purge report. Once deleted, the
records are not recoverable except from file backups.
| 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.
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
Deleting Archived Records with GJTRJPRG
SYSPRINT
(Required) This output listing should be allocated with RECFM=FBA and
LRECL=133.
SYSTERM
(Required) This output listing should be allocated with RECFM=FBA and
LRECL=133.
Syntax Rules: The following rules apply to the SYSIN control statements:
■ All keywords for an event or event name prefix must be specified on one
statement.
■ Only one of each keyword GEN= and DAYS= can be specified for each
event or event name prefix.
■ An * in column one identifies the statement as a comment. The statement is
ignored.
This section focuses on recovery of the Unicenter CA-Jobtrac database and the
sysout capture data sets.
Ensure that you route the output to a valid print class. This command generates
a batch GJTRVDMP diagnostic dump. The DUMPV3 JCL is generated during
the STAGE2 installation step and should be in your procedure library
(cai.CAIPROC).
Have this dump available when you call CA Technical Support for assistance.
Chapter 4. Recovery 73
Switch Primary Systems
What Happens When Switching Systems: When you issue the ACTSYS
command, the Unicenter CA-Jobtrac on that system immediately goes into
monitor mode from primary mode. The timer record on the database is
immediately updated to reflect the new primary system. As each Unicenter
CA-Jobtrac system wakes up and scans the database, it notices the change
and acts accordingly. The new primary system resets from monitor mode to
primary mode.
Take the following steps to safely switch your Unicenter CA-Jobtrac primary
system to another when the current primary system is running fine:
1. If you are also going to need to move the CA-Datacom/AD MUF address
space, you should complete that move first. For more information, see
“Relocate the CA-Datacom/AD MUF” on page 76. If the MUF does not
need to be relocated, skip this step.
2. Shut down the Unicenter CA-Jobtrac system you want to become the
primary system.
3. Issue the following command on the system containing the current primary
Unicenter CA-Jobtrac system:
F taskname,ACTSYS=sysid
taskname is the name of the Unicenter CA-Jobtrac started task. sysid is the
ID of your system.
4. Once the modify message issued in Step 2 is acknowledged, bring up
Unicenter CA-Jobtrac on the new primary system.
Procedure if Current System is Hung Up: Take the following steps to safely
switch your Unicenter CA-Jobtrac primary system to another when the current
primary system is hung up:
1. Shut down the Unicenter CA-Jobtrac system you want to become the
primary system.
2. On the current Unicenter CA-Jobtrac primary system, request an SVC dump
and cancel Unicenter CA-Jobtrac. If necessary, force Unicenter CA-Jobtrac.
3. Bring up the Unicenter CA-Jobtrac system you want to become the primary
system.
4. Issue the following command on the Unicenter CA-Jobtrac system you want
to become the primary system:
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
Relocate the CA-Datacom/AD MUF
You can use the Unicenter CA-Jobtrac suspend processing to accomplish this
with minimum impact. You have two options:
■ Before shutting down the MUF, issue the SUSPEND command to each of
the Unicenter CA-Jobtrac systems. Each Unicenter CA-Jobtrac then
completes any current processing and closes access to CA-Datacom/AD.
The CA-Datacom/AD MUF can then be shut down on one system and
restarted on another system. Once restarted, you can issue the Unicenter
CA-Jobtrac RESUME command to each of the Unicenter CA-Jobtrac
systems, allowing them to reestablish their database connection and
continue processing where they left off.
■ Issue the CA-Datacom/AD EOJ command. Unicenter CA-Jobtrac
automatically detects that CA-Datacom/AD is in EOJ status and suspends
automatically on all systems. Once suspended, Unicenter CA-Jobtrac
automatically begins resume processing to reconnect to the database as
soon as the MUF becomes available.
While suspended, the user interfaces return an error message to indicate that
Unicenter CA-Jobtrac is suspended. For ISPF, to close the connection to the
database, all Unicenter CA-Jobtrac users must press Enter or exit the Unicenter
CA-Jobtrac ISPF interface. Internal processing waits for the resume to be
issued. CA-Datacom/AD does not shut down until all connections to the
database have been closed.
If you also need to move the Unicenter CA-Jobtrac primary system, see the
“Procedure if Current System is Active” on page 74.
Chapter 4. Recovery 77
Relocate the CA-Datacom/AD MUF
If you also need to move the Unicenter CA-Jobtrac primary system, see the
“Procedure if Current System is Active” on page 74.
Processing remains suspended until the MUF has been restarted on the same
or another connected system. Then Unicenter CA-Jobtrac successfully connects
on the next retry. The restart considerations for the MUF on a secondary
system are the same as those discussed in the Scheduled CA-Datacom/AD
Outage topic and should be addressed when installing the system.
Note: For more information about the Shadow MUF configuration, refer to the
CA-Datacom/AD Shadow MUF white paper at ca.com/datacom (click on the
White Papers link).
Chapter 4. Recovery 79
Recover the Sysout Capture
During the archive, all sysouts that have not yet been archived are copied to
the archive, and an updated archive index is placed at the end of the tape. The
index is an exact replica of the archive index on the online sysout capture and
has entries for all sysouts still within the online capture period. For example, if
sysouts are retained online for three days, the index maintains an entry for
each event for the duration of its online capture period.
If errors occur during sysout archival, error recovery routines attempt to capture
as many sysouts as possible, even on a damaged volume or over I/O errors.
The archive tape should contain any sysouts lost from the online capture during
archival.
For more information, see the sysout management information in the Operator
Guide.
Archiving Sysouts If You Cannot Execute the Archive Task: If you cannot
execute the 0ARCHIVE or 0SYSARCH dynamic archive tasks due to abends or
capture errors, you must shut down Unicenter CA-Jobtrac and restart using the
Start JOBTRAC command with the archive parameter (ARCH). Follow these
steps:
1. Issue the @HOLD command from any Unicenter CA-Jobtrac display or F
taskname,HOLD from the console to place the schedule on hold.
2. Issue one of the following operator commands to shut down Unicenter
CA-Jobtrac:
P taskname
F taskname,STOP
3. Issue the following command to restart the Unicenter CA-Jobtrac task:
S JOBTRAC.taskname,PARM=ARCH
4. Issue the @REL command from any Unicenter CA-Jobtrac display or F
taskname,RELEASE from the console to release the schedule again.
If the sysout capture file cannot be reused following this operation, you must
reinitialize or move the capture file (see “Moving the Sysout Capture File” on
page 81).
Moving the Sysout Capture File: If you need to enlarge the sysout capture
file, or if volume errors or hardware failures prevent reuse of the sysout capture
file, you must move the capture data set. Before moving the data set, run the
archive task. Then immediately shut down Unicenter CA-Jobtrac to prevent
Unicenter CA-Jobtrac from capturing sysouts after the archive tape is created.
See SAMPJCL member CAPMOV and follow these steps to move the sysout
capture file:
1. Issue the following operator command:
F taskname,RUN=ARCHIVE
or from ISPF:
RUN ARCHIVE
2. Make sure all jobs are completed on the checkpoint database. Issue the
following operator command:
F taskname,HOLD
or from ISPF, issue
@HOLD
3. Issue the following operator command:
F taskname,BACK
This not only shuts down Unicenter CA-Jobtrac but also backs out the
internals. For details on the BACK command, see the Operator Guide.
4. Issue the following operator command immediately after issuing the
command in Step 3 (do not wait for the command in Step 3 to complete).
This step ensures that all sysouts in the capture file have been backed up.
P taskname
5. Once Unicenter CA-Jobtrac is down, submit the SAMPJCL member
CAPMOV. This will COPY the old Capture DSN to a new Capture DSN, and
it will delete the old Capture DSN. Next, it allocates and formats a new
capture data set on another pack. The capture data set must be allocated
as five or more contiguous cylinders. The last step runs the GJTRVFMT
procedure with the DD statement OLDCAP pointing to the old capture file.
Ask your Unicenter CA-Jobtrac administrator for the name of the installation
library.
6. If the GJTRVFMT procedure succeeds, your new capture file is ready to
use. If the procedure fails, run GJTRVFMT without the OLDCAP DD
statement. In this case, you will need to reload your archived sysouts (see
the following topic “Reloading Sysouts to Your Capture Data Set” on
page 82).
Chapter 4. Recovery 81
Recover the Sysout Capture
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
Chapter 4. Recovery 83
AMR Recovery Procedures
3. Issue:
S VINITx,PARM='ONLY=GJTRVMXT'
4. If loading a new AMRTABLE, issue:
F JOBTRACx,M=amrname
5. Finally, issue the following sequence of 'XON' and 'XOFF' commands:
a. Enter: XON
Output from the XON command:
21 XON
1 IEE35I XON COMMAND INVALID
b. Enter: XOFF
Output from the XOFF command:
21 XOFF
81 TRAC29I - MESSAGE EVENT PROCESSING STOPPED.
c. Enter: XON
Output from the XON command:
21 XON
81 TRAC29I - MESSAGE EVENT PROCESSING STARTED.
Chapter 4. Recovery 85
86 Reports, Maintenance, and Recovery Guide
Chapter 5. Database Backup,
Recovery, and Utilities
This section contains the following topics:
Unicenter CA-Jobtrac requires that you use the LOGRCV NO option. You were
instructed to change this setting during customization in the Planning and
Implementation Guide.
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:
The following is a sample AMR entry that could be used to submit the spill job,
DBSPILL, when the DB00308I message is issued:
The second is the backup of the Unicenter CA-Jobtrac database. The Unicenter
CA-Jobtrac database should be backed up using either the DBBKHOT or
DBBKSTAT member in the Unicenter CA-Jobtrac SAMPJCL. DBBKHOT can be
run while Unicenter CA-Jobtrac is active, creating a hot or fuzzy backup.
DBBKSTAT must be run while Unicenter CA-Jobtrac is inactive and the
Unicenter CA-Jobtrac database is closed to create a static backup.
The static backup always contains a complete and stable database image,
though this is only as current as the time it was taken. The hot backup is taken
while the database continues to be updated. The data in the backup may be
incomplete and may contain only partial updates when multiple records and
tables are updated or added as a group. To recover a hot backup to a stable
point, forward recovery is required.
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.
Before restoring, if the LXX file is intact, run the DBSPILL job to create the
latest RXX file to be used in the recovery.
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.
If you have restored multiple product databases within a MUF and want to
forward recover these databases at the same time, follow these steps.
1. Retrieve and customize the DBRECOV job in the Unicenter CA-Jobtrac
SAMPJCL.
2. Since this is usually a tape or cart job, add any site-specific requirements
you have such as a special job class.
3. Specify an ACCESS statement for each database you want to recover.
4. Specify a RECBASE statement for each database you want to recover.
5. Identify the RXX recovery files, usually tapes or carts that are needed. You
need to include all RXX recovery files that have been created since the
earliest of the restored backups started processing.
For example: if you ran two backups, one of DBID 161, and one of DBID 601,
and the backup of 161 started at 11:00 and the backup of 601 started at 11:30,
you need all RXX tapes created after 11:00.
On the RXX DD, concatenate these files in order; the oldest file first and
proceeding with the next oldest, until the most recent RXX file is added as the
last in the concatenation.
Other Functions
Unicenter CA-Jobtrac provides samples of other CA-Datacom/AD jobs for your
use. The Unicenter CA-Jobtrac SAMPJCL library contains these samples.
■ The DBFXX job increases the number of tasks that can be supported with
the FXX recovery file. This job ran during the modifying CA-Datacom/AD/AD
for Unicenter CA-Jobtrac part of the installation in the Planning and
Implementation Guide. The FXX, the Force Area data set, must be
initialized with a value that is larger than the total tasks specified in the
TASKS CA-Datacom/AD startup option.
By default, the FXX is defined for 50 tasks maximum. If the number of tasks
in the TASKS parameter of the CA-Datacom/AD startup options exceeds
50, the FXX must be reinitialized with a higher number of tasks. The default
size allocation of the FXX file should be large enough and should not need
to be reallocated.
If you need to run this job, ensure that you have shut down
CA-Datacom/AD normally before reinitializing the FXX. Because this
information is used for recovery, the database must have a normal
shutdown to ensure the FXX information is no longer needed.
Note: For more information about modifying CA-Datacom/AD/AD for
Unicenter CA-Jobtrac, see the Planning and Implementation Guide.
■ The DBLXX job increases the size of the CA-Datacom/AD log file, the LXX.
This job ran during the CA-Datacom/AD/AD customization part of the
installation. If the LXX is too small the log can fill up too quickly, requiring
frequent spilling of the LXX to the RXX. Job DBLXX in the Unicenter
CA-Jobtrac SAMPJCL library can be used to resize the LXX. Before this job
can be run, ensure that you have shut down CA-Datacom/AD normally. The
LXX contains information that is used to recover the database if
CA-Datacom/AD is abnormally terminated. If the LXX has filled, you need to
run the spill job, DBSPILL, to relieve the constraint before shutting down the
CA-Datacom/AD MUF. Once CA-Datacom/AD is shut down normally, you
can run the DBLXX to delete, redefine, and initialize a new LXX data set.
When this job has completed, you can restart the CA-Datacom/AD MUF. No
further recovery of the LXX or database is required.
Note: For more information about modifying CA-Datacom/AD/AD for
Unicenter CA-Jobtrac, see the Planning and Implementation Guide.
■ The DBMOVE job moves the Unicenter CA-Jobtrac to another pack or set
of packs. It can also be used to resize the data areas allocated for the
database.
■ The DBRETIX job rebuilds the Unicenter CA-Jobtrac database index area,
the IXX. Usually, Technical Support requests that you run this job. You may
need to run this if a PTF or service pack alters the data dictionary
definitions for the Unicenter CA-Jobtrac database. Any such change
requires running this job.
■ The DBEXTRAC copies the records from a CA-Datacom/AD table to a
sequential file. Usually, Technical Support requests that you run this job to
help diagnose a problem.
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.
This exit enables you to alter the contents of the JCL buffer in any way you
choose. This exit is usually used to supply a security parameter (USER=secid)
to the JOB statement.
For this exit to work properly, you must link the GJTRVOUT ISPF dialog to the
TRACX02 exit.
For complete information about automatic date insertion, see the Extended
Scheduling Services Guide.
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.
This exit can be used for report extraction, balancing, external triggering based
on report content, and so on. It can also set user-alterable fields.
Since this exit is called for each line of sysout captured, care should be taken
to prevent excessive overhead.
Address Contains
A(calltype) Type of call being made.
calltype Available user When taken; Other
actions comments
1 Set on Taken at the start of
WRAPX processing for each
sysout. Forces
sysout to be backed
up to tape or print.
2 Set ARHD, Taken for each line
PRNT of sysout. Force
backup of sysout to
a hard device (tape),
print, or both.
Set DELRQ Request sysout be
deleted, whether it
would have been or
not.
Set Request sysout be
NODELRQ kept, whether it
would have been or
not.
Set REWRIX Force call 3 to be
taken on the sysout,
so you can change
the index entry.
3 Change Index Taken when an
entire class of sysout
has been processed.
Change fields
marked as
changeable in the
@SCINDXV macro.
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.
This exit does not receive control for online ISPF additions.
This exit can be used to deny or alter the scheduling characteristics of any
event as it is selected for scheduling by the GJTRVSCH program.
Exit: On return, any nonzero return code denies scheduling of the event. This
exit can alter the EVT element if necessary.
This exit can be used to deny or alter the text of an operator command as it is
being executed.
Exit: On return, any nonzero return code denies execution of the AUTO-SCHD
event. A JCL error results. Message TRAC024C is issued.
Both the original unmodified JCL and the JCL after symbolic substitution are
provided. After you inspect the JCL, you can allow event submission to proceed
or request it to terminate.
This exit can prevent schedule records from being written to the history
database.
If the exit does not exist, or if it indicates upon return to use the default values,
the values specified on the CA-Jobtrac Global Options panel are used.
During the exit, do not alter the data in the event element A(EVT element).
When the Exit is Called: The TRACX24 exit is called at the following points
during syntax analysis:
■ JCL3TRAC initialization
■ Start of new job
■ Current statement
■ End of current job
■ JCL3TRAC EODAD
The exit is not called if a JCL error occurs during C/I-level checking, or a
Unicenter CA-Jobtrac submission error is detected.
Macros Used By the Exit: The TRACX24 exit uses the following macros:
■ @JCLKEY
■ @JCLTXT
■ @ERRM
■ @PUTM
■ @SCAN
Call Descriptions
JCL3TRAC Initialization Call: The TRACX24 exit is called during JCL3TRAC
startup. You should perform initialization logic at this point.
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.
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.
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.
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).
label
Defines a label name for this macro expansion.
msg-number
Defines the number assigned to the error message.
Limits: 1 to 999
msg-text
Defines the message text enclosed in single quotes.
Limits: 100 bytes
type
Defines the message type as follows:
ERROR
A JCL error message.
WARN
A JCL warning message. Warning messages are not issued if the
NOWARN option is in effect.
Default: ERROR
@PUTM Macro
The @PUTM macro merges the messages defined with the @ERRM macro
into the C/I message spool. Any program that uses this macro must have
register 10 pointing to the CA-JCLTrac work area at the time the message is
issued. When the @PUTM macro is issued, the caller must be in 24-bit mode.
label1
Defines the label name for this macro expansion.
label2
Defines the label name of the @ERRM macro that defines the message.
stmt-number
Defines a fullword containing the message number assigned to the
message by the @ERRM macro.
Coding Rules: The @PUTM coding rules vary depending upon the type of
call:
■ If it is a JCL3TRAC-initialization call, you cannot issue the @PUTM macro.
The C/I message data set is not open.
■ If it is a start-of-new-job call, you must provide a statement number.
■ If it is a current-statement call, you do not have to provide a statement
number. @PUTM uses the statement number of the current statement. You
must provide a statement number if the message applies to a previous
statement.
■ If it is an end-of-current-job call, you must provide a statement number if
you issue a message.
■ If it is a JCL3TRAC-EODAD call, you cannot issue the @PUTM. The C/I
message data set is now closed.
@SCAN Macro
The @SCAN macro scans the JCL text records for major-minor text key
combinations. The macro expands into a call to GJC3MSXT to perform the
scan. If the text unit is found, register 1 will contain the address of the text unit
upon return.
@SCAN scan-var,{,}{(text-address)]JTXTTKEY}
scan-var
Indicates what to scan for. Use one of the following:
■ major-key,minor-key
■ (REG 2-12)
■ (0)
When you use register 0, you must load the major-minor text keys as
shown in the following example.
,,
If you use major-key,minor-key for the scan-var, use one comma. If you use
one of the other values for scan-var, use two commas.
(text-address)
Optionally, the register number, enclosed in parentheses, that contains the
address of where to begin the scan. If omitted, JTXTTKEY is used, which
starts with the first text unit in the string.
Return Codes: Before returning control to your program, the macro also does
a LTR R15,R15 to test the return code from GJC3MSXT. The following return
codes are possible:
Code Explanation
0 The text unit was not found.
4 The text unit was found.
Examples: The following example scans for the GDG field of the DSN
keyword. Register 6 contains the address of the start of the CA-JCLTrac text
units.
LA R6,JTXTTKEY
@SCAN DSNAME,DGDG,(R6)
The following example starts scanning at the address in register 2, and returns
the next key in the string.
@SCAN NEXT,,(R2)
The following example scans for the status field (NEW, OLD, SHR, MOD) of the
DISP keyword. Since the text address is omitted, the scan starts at the
beginning of the string. When you use register 0, you must load the
major-minor text keys as shown in the example.
SR R,R
ICM R,2,=AL1(DISP)
ICM R,1,=AL1(DSTAT)
@SCAN ()
The following example scans for the PERFORM parameter, starting at the
beginning of the string. If the parameter is not found, return.
@SCAN PERFORM
BZ RETURN
At entry to TRACX25, the parameter list contains the volume serial number of
the tape being processed. The vault ID, slot creating job name, and creation
date are inserted in the parameter list in character format. They are printed on
the report exactly as in the parameter list. If one or more fields is omitted, it
should be filled with blanks.
Word 4 Action Codes: The following table explains what each action code
pointed to by word 4 (explained above) means for each security area:
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.
You can use this exit to provide interfaces to change management, alter the
parameters for an edit, or to bypass the edit. For example, you can use this exit
to supply an ISET name for editing IMODs, or to supply an initial macro for
editing documentation members.
The exit can also be used if you use the JES ROUTE/XEQ statement for
purposes other than routing jobs to a true NJE remote node.
Exit: On return, register 15 should contain one of the following return codes:
Code Explanation
00 Treat the job as a true NJE job.
nn Any nonzero return code treats the job as a local, non-NJE job.
User Exit Return Results: The exit may return as a result the character string
'FOREVER', which indicates retry will be continuous until transmission of the
request is successful. The exit may return as a result two numeric values
separated by at least one blank. The first value is the retry count and the
second value is the retry interval that is specified in seconds.
Note: The maximum value for the retry interval as expressed in seconds is
3600 (1 hour). The retry count is limited only by the maximum numeric value
able to be specified in CA-GSS ISERVE's implementation of REXX. If an invalid
result string is returned by the exit, the default of 10 retries every 30 seconds
will be used.
The first authorization profile statement for a user ID sets the greatest
authorization for that user. If a user is not authorized to perform a function in
the first location, the user cannot perform that function in any other location. For
example, if the first location profile does not allow event addition, no additions
can be made at any location, regardless of the JAUTH setting in subsequent
entries.
┌─,────────┐
parm=value┴──────────────────────────────────
──@AUTH──id,──locid,───
id
Specifies the user ID or group of user IDs for which the @AUTH statement
defines authority.
To define a single user, replace id with the TSO user ID of a specific user
for whom you want to define authority.
To define authority for a group of users whose IDs begin with the same
characters, replace id with the initial characters common to all users in the
group followed by an * (asterisk).
For example, USER1 specifies only the user whose ID is USER1, and
USER* specifies all users whose IDs begin with USER.
You can include as many @AUTH statements as required for a single user
ID. If you include multiple @AUTH statements for a single user ID,
Unicenter CA-Jobtrac considers the first statement used to be the greatest
authorization for that user. If a user is not authorized to perform a function
in the first location, the user cannot perform that function in any other
location. For example, if the first location profile does not allow event
addition, no additions can be made at any location, regardless of the
JAUTH setting in subsequent entries.
If you do not include any @AUTH statements for a user, the user is given
authorization only to view the current schedule and sysouts for location ID
000.
locid
Specifies the location ID for which the statement defines authority.
Replace locid with a numeral from 000 to 254, specifying a valid location
ID. The default is 000 (zero).
Each scheduled event is assigned a location ID. If a user schedules an
event using the ADD or RUN command, the user's default location ID is
assigned as the location ID. For information about assigning a location ID
to events, see the Schedule Creation Guide.
parm=value
The following are the parameters and values that are available. Specify
none or as many as you want in a statement, but only one of each
parameter in a statement.
NOTIFY
Specifies whether the user specified by the id variable is to be notified
of abends or error conditions for events in the location specified by the
locid variable. The user is notified with a SEND message. For
descriptions of the messages, see the TRACWARN messages in the
Message Guide. The available values are as follows:
Y
Notify the user.
N
The default value. Do not notify the user.
In an NJE environment, if NOTIFY is specified, only users on the node
on which the NJE job is run will be notified of abend or error conditions
for that node based upon information in the TRACAUTH table defined
for that node.
JAUTH
Specifies event-level authorizations for the user specified by the id
variable in the location specified by the locid variable. The available
values are as follows:
ALL
Authorizes the user to perform all event-level functions.
NONE
The default value. Prevents the user from performing any
event-level functions.
functions
Specify one or more of the following to permit specific event-level
functions. Do not use a separator between the letters.
A
Allow event addition
C
Allow condition code only changes
D
Allow event deletion
O
Allow event output viewing
P
Allow event purge
S
Allow successor/predecessor field only changes
T
Allow time/date alteration
DAUTH
Specifies dependency-change authorizations for the user specified by
the id variable in the location specified by the locid variable. The
available values are as follows:
ALL
Authorizes the user to alter all dependencies.
NONE
The default value. Prevents the user from altering any
dependencies.
dependencies
Specify one or more of the following to permit the user to alter
specific dependencies. Do not use a separator between the letters.
J
JCL dependency alteration is allowed
M
Manual release dependency alteration is allowed
O
Output release dependency alteration is allowed
A
Abend release dependency alteration is allowed
D
DSN dependency alteration is allowed
P
Predecessor dependency alteration is allowed
Q
Release or purge held jobs with $AJ or $PJ is allowed
R
Use of the restart/rerun section of Unicenter CA-Jobtrac/ISPF is
allowed
OPTA
Specifies options to apply to the user specified by the id variable. The
available values are as follows:
ALL
Activates all of the options specified.
NONE
The default value. Prevents the user from access to any of the
options specified.
options
Specify one or more of the following to activate the specific option
described. The L, D, E, and Y options are no longer supported or
needed. Do not use a separator between the letters.
J
Require that JCL for an event being added to the schedule
resides in the user's default location TRACJnnn JCL library.
O
Allow editing of options on the global options panels, and allow
use of the online table services for AMR, CCPF, ADR, and SCS
tables (JTS command).
P
Allow purging of an event with successors if it is confirmed with
a detail display and purge.
OPTB
Specifies options (see the following list) to apply to the user specified
by the userid parameter. The available values are as follows:
ALL
Activates all of the options specified.
NONE
The default value. Prevents the user from access to any of the
options specified.
options
Specify one or more of the following to activate the specific option
described. The D option is no longer supported or needed. Do not
use a separator between the letters.
C
Allow editing of the cyclic processing calendar using the SYS
CYC command.
H
Allow editing of the holiday calendar using the SYS HOLS
command.
S
Allow deletion of sysouts and recovery of deleted sysouts.
Termination Statement
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.
──@AUTH END─────────────────────────────────────────────────────────
TSO user TSXOPR requires authority to view event schedules and sysouts for
his location and to make any alterations to his location's events. In addition, he
must be allowed to view and alter events for four other locations and to view
events of location 6. His level of authority for schedules of other sites varies
with the site. He should not be required to enter a password. TSXOPR should
be notified of scheduled event execution errors for his default location only.
All users whose IDs begin with TSX require authority to monitor location 6.
The 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.
Sysout capture provides indexed information about which archive data set
contains sysouts for each event run during past months.
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.
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.
All the index blocks are 116 bytes long, and all the data blocks are 3860 bytes
long. The file has no hardware keys. Since the file contains absolute (CCHHR)
addresses, it has DSORG PSU (Physical Sequential Unmoveable). The
capture file cannot span volumes.
Index Structure: The index of the sysout capture file contains the following
records:
First
The first record in the index is referred to as the pointer record. This record
gives the sysout capture handling programs enough information to build all
needed channel programs. The layout of the pointer record is described in
“Layout of the Pointer Record” on page 151.
Second
The second record is reserved. It is pointed to by the FINXCHR field in the
first record. The record number is always 4. The second record is used for
the archive lock. During sysout archival, it contains the string SAR (not a
reference to that CA product). During sysout archival, online deletes are not
allowed.
Third
The third record is reserved.
Subsequent
Subsequent records are the actual index entries for the file contents.
Starting at the FINXCHR field in the first record, the index entries occur.
These are mapped by the @SCINDXV macro distributed with the product.
The entries contain information about the items captured in the sysout
capture file. The layout of the index entries is described in “Layout of the
Index Records” on page 153.
Layout of the Pointer Record: The following table describes the layout of the
pointer record in the index:
Use of the Pointer Record: If you browse the sysout capture file with HEX on,
you will probably be most interested in the number of index cylinders, the
number of data cylinders, the index blocks per track, and the data blocks per
track.
Using this information, you can calculate the total number of index blocks and
data blocks you have allocated. The difference between the first index CCHHR
(FINXCHR field) and the next index record that will be used (INDXCHR field)
determine the number of index records that are currently in use.
Similarly, the difference between the first data block CCHHR (FDATCHR field)
and the next data block that will be used (DATACHR field) determine the
number of data records that are currently in use. You may want to calculate
these and compare your results with the information shown by the Unicenter
CA-Jobtrac STATUS command.
Layout of the Index Records: The following table describes the layout of the
actual index records in the index:
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
The INXCTYP field in each index record contains a code that corresponds to
the compression algorithm used to compress the sysout capture file.
How Adaptive Dictionary Compression Works: Virtually all files have sets
of repeating strings in them. For instance, the word sysout occurs many times
in this appendix. The idea of adaptive dictionary compression is to build up a
list of shortcuts based on strings that occur repeatedly in the text. For example,
if discussing VSAM I/O, the Access Control Block (ACB) would probably be
used. In subsequent references, only ACB would be used, saving 17
characters. Adaptive dictionary compression is a formalized algorithm for doing
this.
For information about sysout archive retention, see the chapters "Installation
Tasks" and "Customization Tasks" in the Planning and Implementation Guide.
Important! Do not let the sysout capture file become completely full. This
necessitates an immediate sysout archival run and stops schedule runs and
sysout capture until the archival run occurs.
Note: Job sysouts are grouped by class. If all of Job A's output goes to one
class, a run of Job A will correspond to one sysout in the file. If Job A's output
goes to multiple classes Unicenter CA-Jobtrac captures, it will have multiple
sysouts.
Minimum Size: The minimum size of the capture file is five cylinders.
Placement: The capture file is not DFSMS compatible. We suggest that you
place the capture file on a volume that is cached and used by DFW (DASD
Fast Write).
Estimating the Size: You can start with this estimate of 100 cylinders per 1.5
million lines. If you do this and you are fairly generous with your estimate of the
number of lines you will capture, you will probably be fine. However, if you
capture many small sysouts, this estimate is too conservative.
Easily Calculating the Size: Probably the best way to size the capture file
without extensive work is to run a sample set of jobs and schedules, capture
them, and use the Unicenter CA-Jobtrac STATUS command to display the
usage statistics on the capture file.
Multiply the result for your full workload. You can use the GJTRVFMT utility to
quickly copy and enlarge your capture file, after you calculate what its full size
should be.
Capture File Allocation for an Individual Sysout: Each sysout requires one
index block and one or more data blocks.
How many lines fit into a 3860-byte data block will vary. Each data block
usually holds 60-250 lines of output, depending on how many repeating
characters and repeating strings occur in your data, and how long your print
lines are. Of course, if a sysout contains only one line, the block holds only one
line. In the extreme case of all blanks, one 3860-byte block can hold 693 lines
of 133 blanks each. The line break has to be noted also, so this is equivalent to
134 characters times 693 lines or 92,862 characters compressed into 3860,
which is over 24 characters per byte.
So How Many Lines of Output Can I Really Put in 100 Cylinders?: Let's
consider a 3380 capture file 100 cylinders in size. The default number of index
cylinders for this file is 5, and thus the default number of data cylinders for this
file is 95.
Scenario Discussion
Worst Case On a 3380, 78 * 15 * 5 = 5,850. Thus, 5,850 index blocks
will fit in 5 cylinders. This means this sysout capture file
can hold at most 5,850 sysouts. If all your sysouts
contained 1 line, this 100 cylinder file would only hold
5,850 lines. In such a circumstance, you would want to
enlarge your index to 13 cylinders. Then the index could
hold 15,210 files, and thus 15,210 lines.
Best Case The 95 cylinders of data portion of this file contain
15,675 (11 * 15 * 95) data blocks. If all of your sysout
consisted of 133-byte blank lines, this file could hold up
to 10,862,775 lines (15,675 * 693).
Normal Case If sysouts average 121 bytes per line, and compression
averages 33 percent, the average 3860-byte block holds
over 96 lines, and 15,675 blocks holds over 1.5 million
lines. (Note the implicit assumption here that the average
sysout has over 256 lines, since 1,500,000/5850 =
256.4.) Also, most people will experience better than
33% compression.
Selecting and Controlling the Index Size: The GJTRVFMT utility is used to
format and move the capture file. It uses a default index size that works well for
most users. The default is determined using the following formula:
max((floor(MAXICYLS/4),min(ceil(585/INDXIBT/TRKCYL),MAXICYLS))
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.
(The utility does not use trial and error to find MAXICYLS. Instead, it calculates
a theoretical exact maximum of index cylinders (EXMAXICYL), and rounds it up
to an even cylinder. The formula for EXMAXICYL will be given a little later.)
Also, note 5850 / 78 / 15 = 5 (comes out even) so the formula for default index
cylinders for our sample file now becomes:
max((floor(13/4) ,min(ceil(5),13)) equals
max((floor(3.25) ,min(ceil(5),13)) equals
max(( 3 ,min(ceil(5),13)) equals
max(( 3 ,min( 5 ,13)) equals
max(( 3 , 5 ) equals
5
This is why 5 cylinders is the default index size for a 100 cylinder 3380 capture
file.
In this case, the 5850 index blocks term has dominated the result. For smaller
capture files, MAXICYLS will dominate and be used for the index size. For large
capture files (over about 161 3380 cylinders) the leftmost term dominates and
the index size is 1/4 of MAXICYLS -- an assumption that each sysout averages
4 blocks or so.
Index Size Recommendation: We recommend that you use the default index
size and then observe your capture file's behavior. You can display the capture
file usage with the Unicenter CA-Jobtrac STATUS command. If your index
percentage used is consistently significantly different from your data percentage
used, you may want to adjust the allocation of index cylinders to suit your
actual usage.
To do this, first calculate the largest number of index cylinders you could
possibly need. For a capture file of size TC cylinders, the extreme maximum
number of index cylinders required (EXMAXICYL) can be determined by the
formula:
EXMAXICYTC DATADBT / (INDXIBT + DATADBT)
All the values in the formula except TC come from the pointer record (in fact,
your current TC is INDXCYL + DATACYL).
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
Before contacting Technical Support, attempt to resolve the problem using the
following steps.
From your response to these questions and the diagnostic data, try to identify
the cause and resolve the problem.
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.
If you are unable to resolve the problem, have the following information ready
before contacting Technical Support:
■ All the diagnostic information described in “Collect Diagnostic Data” on
page 163.
■ Product name, release number, operating system, and genlevel.
■ Product name and release number of any other software you suspect is
involved.
■ Release/version level and PUTLEVEL of the operating system.
■ Your name, telephone number and extension (if any).
■ Your company name.
■ Your site ID.
■ Severity code. This is a number (from 1 to 4) that you assign to the
problem. Use the following to determine the severity of the problem:
1 "System down" or inoperative condition
2 Suspected high-impact condition associated with the product
3 Question concerning product performance or an intermittent
low-impact condition associated with the product
4 Question concerning general product utilization or implementation
Request Enhancements
CA welcomes your suggestions for product enhancements. All suggestions are
considered and acknowledged. Contact your Account Manager.
Special Characters
CA-JCLTrac
standards enforcement exit 126
@AUTH macro tape management system interface exit 132
statement examples 148 CA-JCLTrac PROCLIB dynamic allocation
termination statement 147 TRACX28 137
user authorization profile statement 143 CA-Jobtrac library edit
@ERRM macro 128 TRACX29 138
@HOLD command 80 CA-TCC
@JCLKEY macro 128 See CA Support Online
@JCLTXT macro 128 CA-TLC
@JOBTRAC utility exit 113 See Licensing
@PUTM macro 129 checkpoint
@SCAN macro 130 record types 66
commands
Numerics @HOLD 80
BACK 83
0ARCHIVE task 12, 61, 80
condition code records 66
0JOBARCH task 12, 61
condition code, using to abend event 36
0SYSARCH task 80
Cross-platform support exit 140
Customer Support
A See Technical Support
adding events with GJTRABTR
Advantage CA-Datacom/DB 10
altering the schedule in batch mode 35
D
data sets
AMR recovery procedures 84
sysout capture 80
archival 60, 62
database
archive
backup 87
event exit 122
deleting records from 70
event history report 12
Date card calculation and insertion exit 109
parameter 80
DB00308I message 97
archiving event information in batch mode 62
deleting
argument records 66
events 36
authorization codes, obtaining 165
records from database 70
AUTO-SCHD exit 119
temporary-use JCL library members 68
dumps 73
B dynamic archives
BACK command 83 GJTRJARC parameters 66
backing up the database 87
E
C Environmental dependency retry exit 123
CA Support Online 165 eSupport
CA-Datacom/AD 10 See CA Support Online
CA-Easytrieve reporting 13, 15 event
archival of 60
posting 36
Index 169
event (continued) JMF (continued)
purging 36 pre-resolution exit 120
records 66 JTEZREPT Report Utility 13, 15
recovering status 83
L
Event archive exit 122
events on current schedule, listing 62
license keys, obtaining 165
listing events on current schedule 62
F log file 89
forecast database ID 98, 99 LXX file 89
fuzzy backup 98
M
G microfiche for sysout archival 60
ghost records 66 mirroring 91
GJTRABTR
N
command summary 50
command syntax 48, 49
returned information 40 NJE ROUTE/XEQ statement exit 139
uniquely identifying an event for 36
GJTRABTR and @JOBTRAC 35
GJTRABTR utility
O
Operator command exit 118
commands 52
option records 66
description of 35
invoking with CLIST 59
invoking with JCL 58 P
GJTRABTR utility exit 113 posting events 36
GJTRJARC PROC 61 primary system, switching 74
GJTRJARC utility 62 purging events 36
GJTRJPRG utility 70
GJTRMAJC utility 68
GJTRVMFT utility 67 R
GJTRVRLD procedures 80 record types, checkpoint 66
recovery file 90
H
remote access to Unicenter CA-Jobtrac 36
reports
historical summary report 13 CA-Easytrieve 13, 15
history database 60, 62 listing events on current schedule 62
hot backup 98 REXX IMOD submission exit 124
RXX file 90
I
Internet, CA site 165 S
schedule
J adding event with GJTRABTR
batch alteration of 35
36
JCL submission exit
deleting event 36
after JCL read 106
scan exit 112
before JCL read 108
update exit 117
JMF
updating information 36
dynamic variable preprocessor exit 125
post-processor exit 121
T
CA-JCLTrac tape management system interface
exit 132
Tape management system interface exit 132 TRACX26
tapes Security exit 133
using for sysout archival 60 TRACX28
temporary-use JCL library, deleting members CA-JCLTrac PROCLIB dynamic allocation 137
from 68 TRACX29
TRACAUTH interface exit 110 CA-Jobtrac library edit 138
TRACAUTH table TRACX30
assembling and linking the default 142 NJE ROUTE/XEQ statement exit 139
tracking records 66 TRACX31
TRACX01 Cross-platform support exit 140
JCL submission exit (after JCL read) 106 Troubleshooting 161—167
TRACX02
Sysout browse authorization exit 107
TRACX03 U
JCL submission exit (before JCL read) 108 Unicenter CA-11 92
TRACX06 Unicenter CA-View 149
Date card calculation and insertion exit 109 user exits 106
AUTO-SCHD exit 119
Index 171
V
version number
deleting event with 36