Unicenter®CA-Jobtrac™ Job Management

8/9/2019 UnicenterCA-Jobtrac Job Management

1/172


2/172

This documentation and any related computer software help programs (hereinafter referred to as the

Documentation) is for the end users informational purposes only and is subject to change or withdrawal by CA at

any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or inpart, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA

and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the documentation for

their own internal use, and may make one copy of the related software as reasonably required for back-up and

disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy.

Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for

the product are permitted to have access to such copies.

The right to print copies of the documentation and to make a copy of the related software is limited to the period

during which the applicable license for the Product remains in full force and effect. Should the license terminate for

any reason, it shall be the users responsibility to certify in writing to CA that all copies and partial copies of the

Documentation have been returned to CA or destroyed.

EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY

APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING

WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE

OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY

LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT

LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY

ADVISED OF SUCH LOSS OR DAMAGE.

The use of any product referenced in the Documentation is governed by the end users applicable license

agreement.

The manufacturer of this Documentation is CA.

Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the

restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-

7014(b)(3), as applicable, or their successors.

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

Copyright 2006 CA. All rights reserved.


3/172

CA Product References

This document references the following CA products:

UnicenterCA-JobtracJob Management (Unicenter CA-Jobtrac)

UnicenterAutoSysJob Management (Unicenter AutoSys JM)

UnicenterCA-EasytrieveReport Generator (Unicenter CA-Easytrieve)

UnicenterCA-MIM Resource Sharing (Unicenter CA-MIM)

UnicenterCA-MII Data Sharing (Unicenter CA-MII)

UnicenterCA-MIA Tape Sharing (Unicenter CA-MIA)

UnicenterCA-MIA Message Sharing (Unicenter CA-MIC)

UnicenterNetwork and Systems Management Job Management Option (Unicenter NSM JMOption)

UnicenterCA-OPS/MVSEvent Management and Automation (Unicenter CA-OPS/MVS)

UnicenterCA-SchedulerJob Management (Unicenter CA-Scheduler)

UnicenterCA-SpoolPrint Management (Unicenter CA-Spool)

UnicenterCA-SYSVIEWRealtime Perfomance Management (Unicenter CA-SYSVIEW)

UnicenterUniversal Job Management Agent (Unicenter Universal Job Management Agent)

UnicenterCA-ViewOutput Archival and Viewing (Unicenter CA-View)

UnicenterCA-7Job Management (Unicenter CA-7)

UnicenterCA-11Restart and Tracking (Unicenter CA-11)

AdvantageCA-Datacom/DB Database (Advantage CA-Datacom/DB)

AllFusionCA-Panvalet(AllFusion CA-Panvalet)

AllFusionCA-Librarian(AllFusion CA-Librarian)

eTrustCA-ACF2Security (eTrust CA-ACF2)

eTrustCA-ExamineAuditing (eTrust CA-Examine)

eTrustCA-Top SecretSecurity (eTrust CA-Top Secret)

Contact Technical Support

For online technical assistance and a complete list of locations, primary service hours, and telephonenumbers, contact Technical Support at http://ca.com/support.

3


4/172

4 Reports, Maintenance, and Recovery Guide


5/172

Contents

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9CA-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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52DUMP 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 . . . . . . . . . . . . . . . . . . . . . 58Coding 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


6/172


7/172

TRACX23: JMF Dynamic Variable Preprocessor Exit . . . . . . . . . . . . 125

TRACX24: CA-JCLTrac Standards Enforcement Exit . . . . . . . . . . . . 126

Call Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

Macro Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

@JCLKEY Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

@JCLTXT Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

@ERRM Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

@PUTM Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

@SCAN Macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

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

TRACX26: Security Exit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

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

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

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

TRACX31: Cross-Platform Support Exit . . . . . . . . . . . . . . . . . . . . 140

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

Implementing a TRACAUTH Table . . . . . . . . . . . . . . . . . . . . . . . 142User Authorization Profile Statements . . . . . . . . . . . . . . . . . . . . . 143

Termination Statement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

@AUTH Macro Statement Examples . . . . . . . . . . . . . . . . . . . . . 148

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

Contents of the Sysout Capture File . . . . . . . . . . . . . . . . . . . . . . 150

Compression Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Sizing the Sysout Capture File . . . . . . . . . . . . . . . . . . . . . . . . . 156

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

Diagnostic Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162

Problem Resolution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Verify the Problem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Collect Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Interpret Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . . . . 164

Access the Online Support System . . . . . . . . . . . . . . . . . . . . . . 165

Requirements for Using CA Support Online . . . . . . . . . . . . . . . 165

Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Contact Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

Product Releases and Maintenance . . . . . . . . . . . . . . . . . . . . . . 167

Request Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Contents 7


8/172



9/172

Chapter1. Introduction

This section contains the following topics:

CA-Datacom/AD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

This guide is written for systems software programmers and personnel

responsible for the implementation and maintenance of Unicenter

CA-JobtracJob Management (Unicenter CA-Jobtrac).

Chapter 1. Introduction 9


10/172

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, andmore.

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

except that you cannot create your own databases in CA-Datacom/AD.

Otherwise, the operation and use of both CA-Datacom/AD and Advantage

CA-Datacom/DB are the same.

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



11/172

Chapter2. Reports


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

Historical Summary Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

JTEZREPT Report Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

History Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Chapter 2. Reports 11


12/172

Event Archive Report

Event Archive Report

The 0ARCHIVE and 0JOBARCH dynamic tasks create a history database

report and place this report on the sysout capture file.

To access this report through the Sysout Capture Facility, enter the following

command in the COMMAND field:

O ARCHIVE

For complete information about viewing and printing sysouts, see the managing

sysout information in the Operator Guide.

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

1/12/2yy.286 CA-JOBTRAC(CHD4) - MAINTENANCE UTILITY (C)1992,25 CA, INC. GJTRJARC-114:13:17 JOBTRAC4 - EVENT ARCHIVE LISTING PARM=LIST,ALL,FULL PAGE 1

EVENT TABLE CURRENT BUSINESS SCHEDULED SUBMITTED STARTED COMPLETED SYS JOB COMP EVENT NJENAME 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 N2538.1 +EVT WAIT DEPS USER1 3/8 12.47 1/2 12.47 1/2 12.47 1/2 12.47 .... NORML JOB N2538.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 N2555.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 N2512.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 NJARED 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 NSCLT 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 NSCLT2 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 N2512.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?

14 EVENTS PROCESSED THIS PERIOD. E N D O F R E P O R T



13/172

Historical Summary Report


The summary report is produced from the STT statistical records created and

maintained on the CA-Datacom/AD database by Unicenter CA-Jobtrac. The

STT records meeting the selection filtering are selected for summarization and,optionally, printing in detail.

To access this report, run the JTEZREPT procedure referencing the

GJTREZST CA-Easytrieve source code that produces this report.

Symbols on the Report: The filtering criteria for selecting STT records for

participation in this report are as follows:

SYSTEM TOKEN (STT1-F-TOKEN)

Defines the one-character Unicenter CA-Jobtrac system ID to select or * for

all systems. This is required.

HISTORY INDICATOR (STT1-F-HIST)Specifies whether to select archived records. Values are Y to include, N to

exclude, or * for both.

SYSTEM ID (STT1-F-SYSTEM)

Specifies a four-character SMF system ID to include. This can be generic

using the * character. The entry SYB* would list all system IDs starting with

SYB.

REPORTING LEVEL (STT1-F-LEVEL)

Specifies either DETL for listing individual detail STT records selected or

SUMM to list only a summary of the total of the selected detail.

REPORT DATE FORMAT (STT1-F-DATEFM)

Specifies the format of report dates in the data shown as I International

(YYYY/DD/MM) or A American (YYYY/MM/DD).

REPORTING INTERVAL (STT1-F-STTFDAT, STT1-F-STTFTIM,

STT1-F-STTTDAT, STT1-F-STTTTIM)

Specifies the FROM and THRU period for which STT records are selected.

Use the format of YYYY/MM/DD HH:MM:SS for this field.



14/172


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

as three separate reports:

Report Processing Options - The filtering options in effect for the report, andany errors found show on this report.

List Statistics Report - The actual statistical summary report data.

Totals - The count of records processed to produce the report.

1/12/yy CA, INC. - JOBTRAC R11 REPORTINGGJTREZST - LIST STATISTIC REPORT PROCESSING PAGE 1

OPTION/FILTER FILTER/ OPTIONAL OPTIONAL OPTIONAL DESCRIPTION/COMMENT/ERROR MESSAGE TYPE BEGIN BEGIN END END

DATE TIME DATE TIME

SYSTEM TOKEN - JOBTRAC SYSTEM IDENTIFICATION TOKENHISTORY INDICATOR - INCLUDE ARCHIVE HISTORY DATASYSTEM ID - SYSTEM ID ORIGINATING STATISTICSREPORTING LEVEL SUMM - DETAIL OR SUMMARY INFORMATIONREPORT DATE FORMAT I - INTERNATIONAL OR AMERICAN DATE FORMATREPORTING INTERVAL - INTERVAL OF STATISTICS

JTEZ1I - GJTREZST; NO ERRORS DETECTED.

1/12/yy CA, INC. - JOBTRAC R11 REPORTINGGJTREZST - LIST STATISTICS REPORT PAGE 1

T H SYS REPORTING INTERVAL DATA EVENT COMPLETED O S ID FROM/THRU ACTION ACTION ACTION K T DATE TIME DATA COUNT EVENT COUNT SUBMITTED AUTO SCHD

25/27/7 2:5:7 JCL READ 216 LOCAL 41 SYSABEND 25/4/8 2:5:8 NJE(SUB) DB OPEN 89 NJE(RCV) CONDCODE 1 DB CLOSE 285 XPLAT JCLERROR DB COMMIT 24,34 TEMPJCL USR EXIT

DB ROLLBK 13 LATE 1 NORMAL 793 SOUT FILE DUMMY 768 SOUT LINE ARCHIVE 3 OPS PURG IMOD OPS DELET 1 SCHD READ 1,827 SCHD LOAD SCHD FAIL 1 VSCH SECS 131 EDEP FAIL DSN TRG RSR FAIL MESG TRG RERUN MEXC FAIL CMND TRG RESTAGE NJCL FAIL

1/12/yy CA, INC. - JOBTRAC R11 REPORTINGGJTREZST - LIST STATISTIC REPORT TOTALS PAGE 1

TOTAL ACTIVE ARCHIVEDRECORDS RECORDS RECORDS

READ SELECTED SELECTED

82 79



15/172

J TEZREPT Report Utility

JTEZREPT Report Utility

Unicenter CA-Jobtrac batch reporting uses an extremely flexible programming

language, CA-Easytrieve, to deliver history reporting. For details about using

CA-Easytrieve, see the manuals accompanying that product. The explanationhere is confined to its use in this history reporting.

This reporting utility allows users to:

Use keyword values to tailor reporting options to their requirements withinthe existing functionality as delivered, or

Make a copy of the source code modules and modify the code to deliveradditional functionality, or

Use the delivered modules as a guide to create new modules to deliverwhatever functionality is wanted.

The reporting as delivered consists of the following reporting components:

JTEZREPT This PROC executes CA-Easytrieve Common Component

modules to produce requested reports. These modules are:

GJTREZJW Display Schedule Job report

GJTREZJS List Schedule Job report

GJTREZIP List IPL report

GJTREZAU List Audit report

Each module produces three reports in the following general categories:

processing options in effect, detail report specific to the module, and processingtotals. These reports are similar in content and format to the JREPORT3

reports (supplied in earlier releases) but provide expanded functionality. This

functionality includes mixing historical (archived) data with current active data

on the same report and showing all job dependencies in effect.

Each module also has three sections of the code where modifications can

easily be made affecting the content and format of the detail report, each of

these sections is clearly documented and enclosed in a ///////////// border so that

the sections are easily located.

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

list causing the optional processing of the module to function as specified withinthe available choices.

Data Selection Filtering: You can modify the data selection code to exceed

the functions pre-programmed and allowed in the previous section. The data

selection code actually interrogates the data and selects those records to

participate in the report.



16/172


Reporting Sequence: You can modify the sort order parameters to change

the sequence of the report produced to virtually any data field the records being

processed.

Report Selection/Processing OptionsEach report contains a section with the options appropriate for its processing. In

this section of data items, the DEFINE statements are preloaded with default

values. You can change these values to affect the options in effect for the

report execution. The individual options are listed in each of the report module

descriptions. Remember that any line beginning in an asterisk (*) is a comment,

and not part of the program functions.

Data Selection Filtering

Each report contains a section where the data read from the history is filtered

against the values in the previously defined table to determine what data to

select from history and how it should be processed based on the predefined

functions. In most cases, the changes made in the preceding section should be

sufficient, but these functions can be expanded by changing the source code in

this section accordingly.

Reporting Sequence

Each report module either has a section in which the report sequence is

explicitly requested by a SORT command or implicitly requested by a

SEQUENCE statement in the actual definition of the physical report layout, but

not both in the same module. In either case, the fields selected as sort control

can literally be any field defined in the records being processed.



17/172


ReportCategories

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 dataon 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 onthe checkpoint.

LIST IPL REPORT is intended to show all the IPL records captured whenoptionally created during startup of the system.

LIST AUDIT REPORT is intended to show all the changes captured whencontrolled fields on the checkpoint have been modified by a user action.



18/172

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 numerousindexing 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, whichselectively 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 thedatabase. 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 Guidefor 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.



19/172

History Reporting

Display Schedule Report (Module GJTREZJW)

This report is intended to produce a working document from the selected

checkpoint database showing the current scheduled jobs, which assumes no

history is selected. But since it is a useful report format any of the dataavailable has been made optional. All dependencies, up to 14, are shown along

with all the associated predecessor and successor jobs. Additionally a section

of each schedule line can be reserved for manual remarks to allow this report

to be used as a tracking worksheet or other documentation of event processing.

The available keywords (with corresponding data fields in parentheses) for the

control of this report's content are as follows:

TOKEN (EVT1-F-TOKEN)

Defines the one-character Unicenter CA-Jobtrac system ID.

HISTORY INDICATOR (EVT1-F-HISTIND)

Specifies how to process history records in the report.

Y

Specifies history only.

N

Specifies no history.

*

Specifies both history and active.

JOB or EVENT NAME (EVT1-F-JOBNAME)

Defines 1 to 8 characters of a name or a name prefix ended by * as in *,

ABC*, or xyz123*.

LOCATION (EVT1-F-LOC)(Optional) Defines a three-character location code.

Default:* (all locations)

BUSINESS GROUP (EVT1-F-BUSGRP)

(Optional) Defines a 1 to 8 character business group name or name prefix

in the same format as the JOB or EVENT NAME.

Default:* (all business groups)

COMPLETION CODE (EVT1-F-COMPCD)

(Optional) Defines a final Unicenter CA-Jobtrac-assigned completion or * for

all.

Default:* (all)

ABNORMAL

Specifies abnormal ends; shown as (1).

CATLG

Specifies catalog problems (1).



20/172

History Reporting

FORCED

Specifies forced completion (1).

CCnn

Specifies maximum completion code nnon a job step.

JCL

Specifies JCL fail (1).

PURGED

Specifies manually purged (1).

SYSTEM

Specifies system failures, Shhhended (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.

ASpecifies 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.



21/172

History Reporting

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

EVT1-F-ENDTTIM)

Specifies job end date and time, from and through.

TARGET (EVT1-F-TGTFDAT, EVT1-F-TGTFTIM, EVT1-F-TGTTDAT,

EVT1-F-TGTTTIM)Specifies target scheduled date and time, from and through. The FROM

date and time can specify ASAP to select those events that were

designated with an ASAP.

ARCHIVE (EVT1-F-ARCFDAT, EVT1-F-ARCFTIM, EVT1-F-ARCTDAT,

EVT1-F-ARCTTIM)

Specifies archive on date and time, from and through. This value is only

valid if the HISTORY INDICATOR is either Y or *.

The following are sample reports for the Display Schedule report

(CA-Easytrieve module GJTREZJW):

3/25/yy CA, INC. - JOBTRAC R11 REPORTING PAGE 1GJTREZJW - DISPLAY SCHEDULE JOB REPORT PROCESSING OPTIONS


DATE TIME DATE TIME

SYSTEM TOKEN 4 - JOBTRAC SYSTEM IDENTIFICATION TOKEN

HISTORY FLAG - HISTORY AND/OR ACTIVE RECORDS CHOSEN

JOB/EVENT - JOB NAME OR EVENT NAME

LOCATION - LOCATION; MANAGERIAL DEFINITION

BUSINESS GROUP - BUSINESS GROUP; MANAGERIAL DEFINITION

COMPLETION CODE - COMPLETION CATEGORY OF FINAL DISPOSITION

REMARKS - UP TO 2 LINES OF REMARKS FOR EACH JOB/EVENTDATE FORMAT A - AMERICAN OR INTERNATIONAL DATE FORMAT

OSD - ORIGINAL SCHEDULED DATE OF EVENT

STARTING - STARTING PERIOD OF EVENT

SUBMIT - SUBMIT PERIOD OF EVENT

ENDING - ENDING PERIOD OF EVENT

TARGET - TARGET SCHEDULED BEGINNING OF EVENT

HISTORY - EVENT STATUS MOVED TO HISTORY ARCHIVE

JTEZ1I - GJTREZJW; NO ERRORS DETECTED.

3/25/yy CA, INC. - JOBTRAC R11 REPORTING PAGE 1GJTREZJW - DISPLAY SCHEDULE JOB REPORT TOTALS; TOKEN: 4

TOTAL ACTIVE ARCHIVED TOTAL ACTIVE ARCHIVEDEVT EVT EVT PST PST PST

READ SELECTED SELECTED READ SELECTED SELECTED

195 143 52



22/172

History Reporting

3/25/yy CA, INC. - JOBTRAC R11 REPORTING PAGE 1GJTREZJW - DISPLAY SCHEDULE JOB REPORT; TOKEN: 4

H JOB / ORIGINAL VRSN JES ID COMP CURR SCHEDULE SYS PROCESS SUBMIT START END RUN LOC BUSINESSS EVENT SCHED DATE CODE STAT DATE TIME ID PERD/FREQ DATE TIME DATE TIME DATE TIME TIME GROUPT 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 :


23/172

History Reporting

List Schedule Report (Module GJTREZJS)

This report is intended to produce a report from the selected checkpoint

database showing all event data on the checkpoint.



TOKEN (EVT1-F-TOKEN)


HISTORY INDICATOR (EVT1-F-HISTIND)

Specifies how to process history records in the report.

Y

Specifies history only.

N

Specifies no history.

*

Specifies both history and active.

JOB or EVENT NAME (EVT1-F-JOBNAME)


ABC*, or xyz123*.

LOCATION (EVT1-F-LOC)

(Optional) Defines a three-character location code.

Default:* (all locations)

BUSINESS GROUP (EVT1-F-BUSGRP)

(Optional) Defines a 1 to 8 character business group name or name prefixin 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 nnon a job step.



24/172

History Reporting

JCL

Specifies JCL fail (1).

PURGED

Specifies manually purged (1).

SYSTEM

Specifies system failures, Shhhended (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 =' '



25/172

History Reporting

The following example would select commands, dummy jobs and remote

REXX PROCs (batch jobs would not be selected because the trailing

blanks are ignored):

EVT1-F-EVTTYPE ='CDE '

The following example would select batch jobs and dummy jobs (because ablank indicating batch job is specified before a non-blank event code):

EVT1-F-EVTTYPE =' D '

DATE FORMAT (EVT1-F-DATEFMT)


I


A

Specifies the American format of YYYY/MM/DD.

The following optional parameters are combinations of FROM and THRU limitsfor 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 *.



26/172

History Reporting

The following are sample reports for the List Schedule report (CA-Easytrieve

module GJTREZJS):

3/25/yy CA, INC. - JOBTRAC R11 REPORTING PAGE 1GJTREZJS - LIST SCHEDULE JOB REPORT PROCESSING OPTIONS


DATE TIME DATE TIME

SYSTEM TOKEN Y - JOBTRAC SYSTEM IDENTIFICATION TOKEN

HISTORY FLAG - HISTORY AND/OR ACTIVE RECORDS CHOSEN

JOB/EVENT - JOB NAME OR EVENT NAME

LOCATION - LOCATION; MANAGERIAL DEFINITION

BUSINESS GROUP - BUSINESS GROUP; MANAGERIAL DEFINITION

COMPLETION CODE - COMPLETION CATEGORY OF FINAL DISPOSITION

EVENT TYPE(S) - TYPE OF EVENT

REPORT DATE FORMAT A - INTERNATIONAL OR AMERICAN DATE FORMAT

OSD - ORIGINAL SCHEDULED DATE OF EVENTSTARTING - STARTING PERIOD OF EVENT

SUBMIT - SUBMIT PERIOD OF EVENT

ENDING - ENDING PERIOD OF EVENT

TARGET - TARGET SCHEDULED BEGINNING OF EVENT

HISTORY - EVENT STATUS MOVED TO HISTORY ARCHIVE



27/172

History Reporting

3/24/yy CA, INC. - JOBTRAC R11 REPORTING PAGE 1GJTREZJS - LIST SCHEDULE JOB REPORT; TOKEN: Y

H T JOB / JES ID EVENT SCHEDULE ORIGINAL SYS COMPL CURR PROCESS SUBMIT START END RUN LOC BUSINESSS Y EVENT VRSN DATE TIME SCHED DATE ID CODE STAT PERD/FREQ DATE TIME DATE TIME DATE TIME TIME GROUPT P NAME NO DESC 4/3 : EST

Y APMPINF J 1 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : EST1Y APMPINF J 2 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : ESTY APMP1HIS J 1 4/3 : 26/4/3 .... NORML WMAN FOM 4/3 : EST1Y APMP1HIS J 2 4/3 : 26/4/3 .... NORML WMAN FOM 4/3 : ESTY APMP1INF J 1 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : EST1Y APMP1INF J 2 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : ESTY APMP1INM J 2 4/3 : 26/4/3 .... NORML WMAN FOM 4/3 : EST1Y APMP2HIS J 1 4/3 : 26/4/3 .... NORML WMAN FOM 4/3 : ESTY APMP2HIS J 2 4/3 : 26/4/3 .... NORML WMAN FOM 4/3 : EST1N APMP2INF J 1 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : ESTN APMP2INF J 2 4/3 : 26/4/3 .... NORML WMAN WORKDAYS 4/3 : EST1Y BDCDN95 J6161 34 12/29 : 25/12/29 X... NORML TERM DAILY 1/22 12:15 1/22 22:43 1/22 22:43 :


28/172

History Reporting

List IPL Report (Module GJTREZIP)

This report is intended to produce a report from the selected IPL data on

checkpoint database showing all IPLs recorded.



TOKEN (IPL1-F-TOKEN)


SYSTEM ID (IPL1-F-SYSTEM)

Defines 1-4 characters of a system name or a name prefix ended by * as in

*, ABC*, or xyz1.

IPLED BY NAME (IPL1-F-IPLEDBY)

(Optional) Defines a 1-12 character operator name.

Default:* (all)

IPL TYPE (IPL1-F-IPLTYPE)

(Optional) Defines a one-character IPL code type.

Default:* (all)

C

Specifies a cold start IPL.

N

Specifies a normal IPL.

*

Specifies all.

IPL REASON (IPL1-F-IPLREASON)(Optional) Defines a 1-39 character reason for the IPL. The reason can be

a character string ending in *.

Default:* (all)

IPLED (IPL1-F-IPLFDAT, IPL1-F-IPLFTIM, IPL1-F-IPLTDAT, IPL1-F-IPLTTIM)

Specifies a date and time of IPL optional parameters are FROM and THRU

limits for selection of data meeting all the preceding selection criteria. Any

date field can be TODAY or * that is treated as today's date (the date of the

report execution). Leaving the field blank is treated as choosing any

date/time. Date formats are yyyy/mm/dd. Time formats are hh:mm:ss.

DATE FORMAT (IPL1-F-DATEFMT)Specifies the format of printed dates:

I


A




29/172

History Reporting

The following are sample reports for the List IPL report (CA-Easytrieve module

GJTREZIP):

3/25/yy CA, INC. - JOBTRAC R11 REPORTING PAGE 1GJTREZIP - LIST IPL REPORT PROCESSING OPTIONS


DATE TIME DATE TIME

SYSTEM TOKEN - JOBTRAC SYSTEM IDENTIFICATION TOKEN

SYSTEM ID - SYSTEM IDENTIFICATION BEING IPLED

IPLED BY NAME - IPLED BY OPERATOR NAME

IPL TYPE - TYPE OF IPL PERFORMED

IPL REASON - REASON OR CAUSE REQUIRING IPL

IPLED - WHEN IPL OF JOBTRAC OCCURED

DATE FORMAT A - INTERNATIONAL OR AMERICAN DATE FORMAT

JTEZ1I - GJTREZIP; NO ERRORS DETECTED.

3/25/yy CA, INC. - JOBTRAC R11 REPORTING PAGE 1GJTREZIP - LIST IPL REPORT

T SYS OPERATOR IPL REASON IPLED IPLO ID ID :-------------------------------------: DATE TIME TYPE

K

4 XE79 SMITH1 CAUSE BECAUSE SYSTEM FAILED 2yy/3/22 13:4:37 COLD 4 XE79 JONES2 REGULAR STARTUP 2yy/3/25 13:4:37 NORMAL

3/25/yy CA, INC. - JOBTRAC R11 REPORTING PAGE 1GJTREZIP - LIST IPL REPORT TOTALS



2 2



30/172

History Reporting

List Audit Report (Module GJTREZAU)

This report is intended to produce a report from the selected audit data on

checkpoint database showing all controlled changes made to checkpoint data.



TOKEN (AUD1-F-TOKEN)


JOB or EVENT NAME (AUD1-F-JOBNAME)


ABC*, or xyz123*.

USER ID (AUD1-F-USERID)

(Optional) Defines a 1 to 8 character operator name.

Default:* (all)

OSD (AUD1-F-OSDFDAT, AUD1-F-OSDTDAT)

Specifies the original schedule date from and through.

DATE FORMAT (AUD1-F-DATEFM)


I


A


AUDIT (AUD1-F-AUDFDAT, AUD1-F-AUDFTIM, AUD1-F-AUDTDAT,

AUD1-F-AUDTTIM)(Optional) Defines a date and time of audited change. The parameters are

FROM and THRU limits for selection of data meeting all the preceding

selection criteria. These date fields can be TODAY or * that is treated as

today's date (the date of the report execution). Leaving the field blank is

treated as choosing any date/time. Date formats are yyyy/mm/dd. Time

formats are hh:mm:ss.

The following are sample reports for the List Audit report (CA-Easytrieve

module GJTREZAU):



31/172

History Reporting

3/25/yy CA, INC. - JOBTRAC R11 REPORTING PAGE 1GJTREAUD - LIST AUD REPORT PROCESSING OPTIONS


DATE TIME DATE TIME

SYSTEM TOKEN - JOBTRAC SYSTEM IDENTIFICATION TOKEN

JOB / EVENT NAME GOBRUCE - JOB OR EVENT NAME AUDITED

USER ID - USER ID MAKING CHANGE

DATE FORMAT A - INTERNATIONAL OR AMERICAN DATE FORMAT

CHANGE DATE/TIME - DATE / TIME FILE CHANGE WAS MADE

OSD - ORIGINAL SCHEDULE DATE OF JOB/EVENT

JTEZ1I - GJTREAUD; NO ERRORS DETECTED.

3/25/yy CA, INC. - JOBTRAC R11 REPORTING PAGE 1GJTREAUD - LIST AUDIT REPORT

T JOB/ ORIGINAL VRSN CHANGE OCCURRED USER ID DB SQL_FIELD_NAME BEFORE IMAGE/O EVENT SCHED DATE DATE TIME TBL AFTER IMAGEK NAME ID :------------------------------: :------------------------------:

4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:2:5 USERB1 SEV ISPF ADDED SEV +

4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:4:4 USERB1 EVT ISPF CHANGED EVT +

4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:4:4 USERB1 EVT DATE_STARTED + 1/1/ 3/22/2yy4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:4:4 USERB1 EVT MANUAL_DEPENDENCY + Y N4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:4:4 USERB1 EVT TIME_STARTED + .. 18.2.4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:22:4 USERB1 SEV ISPF ADDED SEV +


4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:26:19 USERB1 EVT DATE_STARTED + 1/1/ 3/22/2yy

4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:26:19 USERB1 EVT MANUAL_DEPENDENCY + Y N4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:26:19 USERB1 EVT TIME_STARTED + .. 18.22.4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:5:1 USERB1 SEV ISPF ADDED SEV +


4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:5:33 USERB1 EVT DATE_STARTED + 1/1/ 3/22/2yy4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:5:33 USERB1 EVT MANUAL_DEPENDENCY + Y N4 GOBRUCE 2yy/3/22 1 2yy/3/22 18:5:33 USERB1 EVT TIME_STARTED + .. 18.5.4 GOBRUCE 2yy/3/22 1 2yy/3/22 19:18:54 USERB1 EVT ISPF DELETED EVT +

4 GOBRUCE 2yy/3/22 1 2yy/3/22 19:18:54 USERB1 EVT $AJ_REQUIRED + N

4 GOBRUCE 2yy/3/22 1 2yy/3/22 19:18:54 USERB1 EVT ABEND_SUB_SUCCS + N

3/25/yy CA, INC. - JOBTRAC R11 REPORTING PAGE 1GJTREAUD - LIST AUDIT REPORT TOTALS



11,585 154



32/172



33/172

Chapter3. Maintenance


Product Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Performing Archives . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

Modifying the Sysout Capture File . . . . . . . . . . . . . . . . . . . . . . . . 67

Deleting Members from Temporary-Use JCL Libraries . . . . . . . . . . . . 68

Deleting Archived Records with GJTRJPRG . . . . . . . . . . . . . . . . . . 70

Chapter 3. Maintenance 33


34/172

Product Maintenance

ProductMaintenance

The Unicenter CA-Jobtrac tasks and utilities offer the following capabilities:

Access to information on the current schedule from a batch job Current schedule event archival

Sysout capture file archival

Modification to the sysout capture file

Deletion of members from the temporary-use JCL libraries

Deletion of records from the Unicenter CA-Jobtrac history database

Unicenter CA-Jobtrac offers the following maintenance utilities and tasks:

The Unicenter CA-Jobtrac tasks (0JOBARCH, 0SYSARCH, and 0ARCHIVE)

cannot run at the same time.

We recommend that you load no SCLs during a 0JOBARCH as it may affect

performance.

Function Task or UtilityMaintain the current schedule through

a batch job

GJTRABTR utility

Event archival 0JOBARCH task, 0ARCHIVE task, or

GJTRJARC utility

Sysout archival 0SYSARCH task or 0ARCHIVE task

Reload sysout archival GJTRVRLD utility

Modifying the sysout capture file GJTRVFMT utility

Deleting members from the

temporary-use JCL libraries

GJTRMAJC utility

Deleting records from the Unicenter

CA-Jobtrac history database

GJTRJPRG utility

Backup and recovery PROCs using

CA-Datacom/AD utilities



35/172

Product Maintenance

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

Unicenter CA-Jobtrac tasks is running, the task is marked ABENDED=SYS

DOW when Unicenter CA-Jobtrac is brought back up.

These tasks will have a 'J' dependency that needs to be removed so that they

can execute. They also appear on an exceptions display.

Accessing the Current Schedule

The GJTRABTR utility provides a batch method for querying and updating the

current schedule. You can do any of the following:

Query the system

Issue abend codes

Add an event to the current schedule

Update information on the current schedule

Delete or purge an event on the current schedule

Specify conditions that must be met before any of the above actions aretaken

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.



36/172

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 UnicenterCA-Jobtrac ISPF interface.

To test certain modifications to the current schedule.

You can use GJTRABTR to perform any of the following actions:

Add an event to the current schedule.

Modify the schedule information for an event on the current schedule.

Delete an event from the current schedule.

Purge an event from the current schedule and remove one predecessordependency from each of its successors.

You can invoke GJTRABTR using any of the following methods. Unicenter

CA-Jobtrac does not have to be running to use GJTRABTR.

Coding JCL to invoke the GJTRABTR program. The JCL can be submittedeither 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 CALLcommand).

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 .vvin the JOBname parameter)



37/172

Product Maintenance

Using GJTRABTR

Using typical JCL, you invoke the GJTRABTR utility. Within the JCL you specify

a GJTRABTR command or commands. GJTRABTR sends the commands to

the @JOBTRAC facility to execute the commands.

The @JOBTRAC facility returns information about an event that is on the

current schedule. The information is placed in SYSPRINT. The returned

information is described in Information Returned by GJTRABTR on page 40.

If you specify multiple commands, SYSPRINT contains the returned information

in the order you requested it.

A command's parameters define an event or qualify the search for an event.

For example, the Add command uses the information to define an event, while

the DELete command uses the information to find an event and delete it.

GJTRABTR Commands on page 52 starts the descriptions of the GJTRABTR

commands and parameters.

GJTRABTR provides the following methods for specifying commands. You can

use one or both of them in a job.

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.

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

and SYSIN

//AB3 EXEC PGM=GJTRABTR,// 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))



38/172

Product Maintenance

Using the STACK Command: GJTRABTR can use a stack to collect

commands and command parameters. You put information onto the stack

using SYSIN. You can put up to 100 input lines onto the stack. You use the

STACK command to instruct GJTRABTR to use the information in the stack.

You can use the STACK command alone or with other commands. You can

even start a command in the PARM statement and finish it in the stack.

A SYSIN line can contain an entire command or any portion of a command. In

this way, you can specify a large number of commands or commands with

numerous parameters that might otherwise be too long to specify because of

JCL line length restrictions. It is important to keep in mind the syntax of the

GJTRABTR commands when placing information on the stack. If you omit a

necessary parenthesis you will receive an error.

The information in the stack is used as needed. So, if in the PARM statement

you start a command, but GJTRABTR does not find the ending parenthesis, it

will take information from the stack until it encounters the ending parenthesis. If

a new command is not started in the PARM statement after reading the firstone, GJTRABTR again takes information from the stack.

Using the Stack: Example 1

/AB3 EXEC PGM=GJTRABTR,// PARM='STACK(1) Get (JOB(A)'//SYSIN DD Ver (2))

Same as

/AB3 EXEC PGM=GJTRABTR,

// PARM='Get (JOB(A) Ver(2))'

Notice the parameter put in the stack contained the ending parenthesis for the

Get command. It tells GJTRABTR the input is done. Without it, you would

receive a syntax error.

The beginning parenthesis (before JOB) is also necessary. It tells GJTRABTR

to read the next line from the stack as part of the Get command. Without it,

GJTRABTR would read the next line from the stack as a new command, and

you would receive an error.



39/172


40/172

Product Maintenance

Information Returned by GJTRABTR: GJTRABTR returns information on the

stack. The information is placed in SYSPRINT. For each GJTRABTR job, the

following is contained in SYSPRINT:

INPUT:

Exact contents of SYSIN.

ARG:

The contents of the PARM statement that is passed to the @JOBTRAC

facility.

RESULT:

Information returned by an IMOD if executing an IMOD.

OUTPUT:

GJTRABTR messages.

Obtained by GJTRABTR (one set per input command) is placed on thestack. If you specified SYSPRINT, the information in the stack is sent to

SYSPRINT.

A 4-byte prefix identifies each piece of information returned. The

table in Stack Prefixes and Information on page 41 describes the

prefixes and information. All information is returned as characters.

When using the Get command, you can obtain any or all of the

information shown in the table. All other GJTRABTR commands

return the RC information only. Additionally, the MSG information

can be returned at any time.

With the exception of the MSG and RC information, the information

is returned in alphabetical order. The MSG information is returned

as necessary. The RC information is always returned last. The

following table is arranged in alphabetical order except MSG and

RC, which are at the end of the table.



41/172

Product Maintenance

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

stack:

AMEM

Identifies the name of an alternate member in the JCL library that runs for

this event instead of the member whose name matches the event's name.

ATIM

Identifies the abort time and date for the event. Returns the information in

thehh:mmmm/ddformat including the colon and slash.

BSGP Identifies the name of the business group or schedule ID assigned

to the event.

CMPC

Identifies the for completed events, how the event completed as described

in the following list.

Code Explanation

OK Indicates the event ended typically.

SAccc Indicates the event ended with a system abend. The abend

code is denoted by ccc.

UAccc Indicates the event ended with a user abend. The abend code

is denoted by ccc.

PU Indicates the event was purged from the input queue.

FO Indicates the event was forced to completion by a user.

JC Indicates the event had a JCL error.

SCnn Indicates the event exceeded its maximum condition code. The

step within which the condition code was exceeded is denotedbynn.

CR Indicates a system crash occurred.

nnnn Indicates some other return code.

DATE

Identifies the date the event was originally put on the current schedule.

Returnsmm/ddformat including the slash.

DCNT

Identifies the data set count associated with the event.

DEP

Identifies the dependency codes if the event has any. Each code isseparated by a blank.



42/172

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: STARTIDEP 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/ddformat, including the colon

and slash.

JES#

Identifies the JES job number assigned if the event was submitted.

JOBNIdentifies 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 orhas 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.



43/172


44/172

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 5STPC 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/ddformat,

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/1SUCC AIH 2 11/22SUCC 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:mmmm/ddformat, including the colon and slash.



45/172

Product Maintenance

TYPE

Identifies the type of event. Possible values are:

IMOD

Indicates a REXX IMOD.

DUMMY

Indicates a dummy job.

JOB

Indicates a batch job.

C-RMT

Indicates a command to be executed at a particular remote node.

VER

Identifies the version number of the event.

MSG

Identifies a message up to 80 characters in length.

RC

Identifies a 4-character return code denoting the success or failure of the

Query command.



46/172

Product Maintenance

RC Explained: The RC information is returned in the following format:

RC rrrr mmmm ffff jjjjjjjj ddddd vvvvv lll ss cc y

The following explains the variables. If a specific variable is missing, a period (.)is used as a placeholder. For example, Get(JOB(ABC) Ver(2))could result in

RC 0004 CUUS GET ABC . 0002 . . ., meaning the original schedule date,

location, status, and completion code information is missing.

rrrr

Specifies a return code as follows:

0000

TRUE

0004

Event name specified by the command was found, but the specific test

was FALSE

0008

Event name specified by the command was not found

Greater than 0008

Some error occurred

mmmm

Specifies the name of the module setting the return code. For example,

SPRS or CUUS. If it is SPRS, this is a parsing error. If it is CUUS, userrrr

to determine the meaning.

ffff

Specifies the command being performed. For example, Get or DELete.

jjjjjjjjSpecifies the event's name.

ddddd

Specifies the original schedule date of the event in the formatmm/dd,

including the slash.

vvvvv

Specifies the version number of the event.

lll

Specifies the location of the event.



47/172


48/172

Product Maintenance

GJTRABTR Command Syntax

The following syntax rules apply to the GJTRABTR commands:

Parentheses are required in the following situations. Other uses of indicated

parentheses are optional.

Parentheses enclosing command parameters if specifying multiple

GJTRABTR commands in one PARM, whether in the stack or not.

Parentheses enclosing command parameters if splitting input across

stacked lines.

Parentheses enclosing parameter values if specifying multiple values.

Parentheses following the STACK command if another command

follows it or if notspecifying the number of lines (defaulting to all lines in

the stack).

Separate commands with a blank or a comma. You can use any number ofblanks, but only one comma.

Separate parameters with a blank or a comma. You can use any number ofblanks, but only one comma. The exception to this is parameters containing

periods (.). For example, the vvand L= parameters. You must use these as

shown in the syntax.

The syntax is free-form. Specify command parameters in any order.

Note: For more information about reading syntax diagrams, see the Operator

Guide.



49/172

Product Maintenance

This command has the following format:

,command( parm )

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:

Additionally, the ABEND and END commands do not use any parameters.

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.



50/172

Product Maintenance

Command Summary: The following table summarizes the GJTRABTR

commands and parameters and indicates which parameters you can use with

which commands:

A dd

DE

L

DU

M

P

Ge

t

IM

o

d

Is

e

r

v

e

JT

s

y

s

MO P

D O

I S

f T

y

No

d

e

PU P

R R

g G

e

Qu

e

r

y

ST

A

C

K

(See page 52 forcommands.)

(For parameters, see

the @JOBTRAC

parameters in the

Extended Scheduling

Services Guide.)

* * ATime (time[date])

* * ** ** * * ** BUSGrp (bgrp-name)

* ** ** * * ** COMPLETION_Code

(code)** ** ** ** ** CURPP (processp)

* * ** ** ** * ** DATE (org_schd_date)

* * ** ** * * ** DCNT (count)

* * ** ** * * ** Dependency ([action]

{deps})

* * END_TIME (time[date])

* * GSS_Node (nodename)

* * IDEP

([ac]name[.rc[.ri[.arg]]]...)* * JCL_Member (amem)

* * ** ** * * ** JCNT (count)

* * JES_Node (nodename)

* * ** ** ** * ** JOBname

(eventname[.vv][,L=nnn])

* * ** ** * * ** JOB_Number (number)

* * ** ** * * ** JOBPP (processp)

* * ** ** ** * ** Location (nnn)

* * MAXCc ({NA|}nnnn})

* * NJE (yn)

* * ONQueue (yn)

* * Predecessor

([ac]name[.vv[.date]]...)



51/172


52/172

Product Maintenance

GJTRABTRCommands

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

ABENDCommand

The ABEND command frees the address environment's resources and

produces a dump.

The ABEND command produces a SOC3-type abend.

Add Command

The Add command adds the event to the current schedule. Parameters you

specify define the event (except SUBsystem). Default values are used for

parameters you do not specify.

If you specify dependency code R or X with the Dependency parameter, they

are ignored.

DELete Command

The DELete command deletes an event from the current schedule. Parameters

you specify serve as search criteria. The first event on the current schedule that

matches the search criteria is deleted.



53/172


54/172

Product Maintenance

Iserve Command

The Iserve command specifies an ISERVE name. It identifies the CA-GSS

subsystem to which you want to submit the GJTRABTR commands specified in

the job. While the request is directed to this subsystem, it might not run here.

This is because if the Node command is used, it takes precedence over the

Iserve command.

The Iserve command must be specified before other commands (except the

IMod, JTsys, or Node commands).

Using the Iserve command invokes the use of CA-GSS. CA-GSS executes the

equivalent GJTRABTR commands in the CA-GSS address space.

If you are using Iserve or Node command, and have multiple Unicenter

CA-Jobtracs running in the subsystem or this is an NJE job, the checkpoint

used is determined in this order

1. The SUBsystem parameter specification

2. The first Unicenter CA-Jobtrac started

3. The default primary Unicenter CA-Jobtrac


Iserve( iservename )

iservnameDefines 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.



55/172

Product Maintenance

JTsys Command

The JTsys command identifies the Unicenter CA-Jobtrac system you want to

use. xis the variable used in the Unicenter CA-Jobtrac checkpoint name to

distinguish multiple Unicenter CA-Jobtracs. This command identifies a Unicenter

CA-Jobtrac system that is running in the subsystem to which you submitted the

GJTRABTR job. You cannot specify a Unicenter CA-Jobtrac system in another

subsystem without using the Iserve or Node command.

The JTsys command must be specified before other commands (except the

IMod, Iserve, or Node commands).


JTsys (x) Token

x

Defines a Unicenter CA-Jobtrac system variable.

Limits:1 character. If you omit this command, the default primary

Unicenter CA-Jobtrac system in the subsystem is used.

MODify or POST Command

The MODify command updates an event on the current schedule. Parameters

you specify replace or define the information in the event's definition. The

DATE, JOBname, Location, SUBsystem, and Version parameters are used to

identify the event only. They cannot be defined or replaced.

The first event on the current schedule that matches the search criteria is

modified.

You cannot specify dependency code R or X with the Dependency parameter.



56/172

Product Maintenance

Node Command

The Iserve command specifies a node name. It identifies the CA-GSS

subsystem to which you want to submit the GJTRABTR commands specified in

the job.

The Node command must be specified before other commands (except the

IMod, Iserve, or JTsys commands).

Using the Node command invokes the use of CA-GSS. CA-GSS executes the

equivalent GJTRABTR commands in the CA-GSS address space.


Node(nodename)

nodename

Defines a node name.

Limits:1 to 16 characters

PURge or PRG Command

The PURge command purges the event from the current schedule, and

removes the predecessor dependency from its successors. Parameters you

specify serve as search criteria. The first event on the current schedule that

matches the search criteria is purged.



57/172

Product Maintenance

Query Command

The Query command searches the current schedule for the existence of the

specified event. If you specify parameters (other than the event name), they

determine the exact definitions the event must have to satisfy the search. The

first event on the current schedule that matches the parameters satisfies the

search.

The Query command returns a return code only. It is identified by the RC prefix

in the stack.

STACKCommand

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 parameterswith a command.

If you do not specify numlines, all the information in the stack is used.

Information is put onto the stack using SYSIN.


STACK( ALL ) numlines

numlines

Defines the number of lines of information on the stack for GJTRABTR.

Limits:1 to 100

Default:All information in the stack



58/172

Product Maintenance

GJTRATBR Command Parameters

You can invoke GJTRABTR processing by coding JCL or using a CLIST.

Note: For GJTRATBR command parameters, see the parameter descriptions

for the @JOBTRAC command in the Extended Scheduling Services Guide.

Coding JCL to Invoke GJTRABTR Processing

Use the following steps to code JCL invoking GJTRABTR processing to perform

the actions you specify.

1. Display the JCL member you want to code to invoke GJTRABTR so that

you can edit it.

2. Insert an EXEC statement invoking the GJTRABTR program (see the

following example).

3. Add the command or commands that perform the actions you want. Use aPARM statement with or without SYSIN.

4. Optionally, insert a DD statement specifying the Unicenter CA-Jobtrac

checkpoint (current schedule) to access. If this is omitted, GJTRABTR uses

the default primary checkpoint. Some commands (Iserve, JTsys, and Node)

and a parameter (SUBsystem) override this default.

5. Insert a DD statement for SYSPRINT to receive output from the job.

Example: In the following figure, jobstep A1 invokes the GJTRABTR program.

Parameters to the GJTRABTR program are specified on the following two

continuation statements. Since no JOBTRACxstatement is specified, your

default primary Unicenter CA-Jobtrac is used. The SYSUDUMP DD statement

assigns sysout class H for system dumps.

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



59/172

Product Maintenance

Example of a CLIST Invoking GJTRABTR

The following figure shows a CLIST that invokes the GJTRABTR program with

a parameter and two operands.

PROC 3 C V D/ SAMPLE SYNTAX ADD(JOB(TESTJOB1),V(1),DEP(NONE) /

CALL 'your.CAILIB(GJTRABTR)' '&C,&V,&D'

Note: You must have the JOBTRACxand JOBHISTxdata sets allocated to

your TSO session. You also need to have the program name GJTRABTR

added to the AUTHPGM table in the IKJTSOxxPARMLIB member.



60/172

Performing Archives

Performing Archives

Unicenter CA-Jobtrac offers the following archival abilities:

Clear completed events from the current schedule. This is referred to asevent 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 theOperator Guide.

Archived event records are retained for a specified period of time or number of

generations of each event. The time period and number of generations are

controlled by the GJTRJPRG utility (see Deleting Archived Records with

GJTRJPRG on page 70).

Sysout Archival: You should perform sysout archival to archive the sysout

capture file on a regular basis. Regular execution of sysout archival is important

for smooth Unicenter CA-Jobtrac operation.

During execution of the sysout archival, Unicenter CA-Jobtrac does not capture

any new sysouts. Once the archival is complete, sysout capture resumes.

After a sysout is archived, you can reload it for online review.

Note: For more information about managing sysouts, see the the Operator

Guide.

Actions Performed by Sysout Archival: During sysout archival, the following

actions are performed. The sysouts are archived, allowing you to archive

sysouts to tape or DASD.

You are prompted to mount a tape for the archival if the SYS OPTS optionis set.

Note: For more information about the SYS OPTS option, see the Planning

and Implementation Guide.

Sysouts not previously archived are dumped from the sysout capture file tothe archive tape.

The sysout archive index is updated.



61/172

Performing Archives

Methods of Executing the Archivals

Unicenter CA-Jobtrac offers a number of ways to perform event history archival

and sysout archival. There are several Unicenter CA-Jobtrac tasks and a utility.

Additionally, there are several ways to start the Unicenter CA-Jobtrac tasks orutility.

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 currentschedule using:

A schedule

The ADD command (the Event/Jobstream Addition panel)

The RUN command

The GJTRABTR utility

These tasks will produce a report listing all events on the current schedule

meeting specific criteria, by putting an 'O' next to the event on the status

display.

More information

About the GJTRJARC Utility on page 62

Using GJTRABTR on page 37

Note: For more information about other methods, see the Operator Guide.

The 0ARCHIVE task performs both the event history archival and the sysout

archival. The 0JOBARCH task performs only the event history archival. The

0SYSARCH task performs only the sysout archival.



62/172


63/172

Performing Archives

Example: The following figure shows sample statements to invoke the

GJTRJARC PROC:

//UTILITY JOB ........//JS1 EXEC GJTRJARC,'LIST,ALL'

//JS2 EXEC GJTRJARC,'LIST,LAW'

In the example, JS1 produces a report listing all events on the current

schedule. JS2 produces a report listing all events on the current schedule with

LATE, ABENDED, or WAITING status.

GJTRJARC PROC Parameters

The GJTRJARC parameters let you specify the action to perform. The

following are the parameters:

ARCH

Archive events from the current schedule to the history database.

EXCP

Produce a report listing all events with a status of LATE, ABENDED, or

WAITING. Events are listed alphabetically by event name. (Produces the

same results as using the parameters LIST,LAW.)

LIST

Produce a list of all events on the current schedule. Events are listed

alphabetically by event name.



64/172

Performing Archives

Descriptions of Operands: The following are the GJTRJARC operands:

ALL

Selects all events, regardless of status.

ALLC

Selects all completed events, regardless of the successors' status.

B=busgrpor S=busgrp

Selects events with the specified business group name.

B=prefix* or S=prefix*

Selects events with the specified business group prefix.

C

Selects only completed events that have no successors waiting.

CLEAN|NOCLEAN

CLEAN removes old, missing events, and orphaned event-related table

records.

E=eventnameor J=eventname

Selects events with the specified event name.

E=prefix* or J=prefix*

Selects events with the specified event name prefix.

FULL|SUMM

FULL lists all the records that are a supplement to the primary EVT and will

participate in the archive. In the new database structure, each scheduled

event is composed of multiple records. The primary record is the EVT, and

all the other records are supplementary.

SUMM lists only the predecessor (PST/PRED) and successor (PST/SUCC)

records that supplement the EVT, while all the other records that alsoparticipate in the archive are not shown.

If neither FULL or SUMM is selected, only the primary record, the EVT, is

listed.

L=nnn

Selects events with the specified location.

LAW

Selects events with a status of LATE, ABENDED, and WAITING.

T=hhmm/mmdd-hhmm/mmdd

Selects completed events that have a target time within the time and date

range specified. The first hhmm/mmddspecifies the start of the range, andthe secondhhmm/mmddspecifies the end of the range. Replacehhmm

with a four-digit number specifying the time (0001-2359), and replace mmdd

with a four-digit number specifying the date (0101-1231).



65/172

Performing Archives

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

Operands: The syntax of the GJTRJARC parameters is as follows:

Parameters Restricted-Use Operands

(use one only, the default isunderlined)

Valid Operands

(use as many as you want)

ARCH, C

ALL

ALLC

FULL

LAW

SUMM


B=busgrp

S=busgrp

B=prefix*

S=prefix*

E=eventname

J=eventname

E=prefix*

J=prefix*

L=nnn

CLEAN|NOCLEAN

EXCP, T=hhmm/mmdd-hhmm/mmdd

B=busgrp

S=busgrp

B=prefix*

S=prefix*

J=eventname

J=prefix*

L=nnn

LIST, C

ALL

ALLCFULL

LAW

SUMM


B=busgrp

S=busgrpB=prefix*

S=prefix*

E=eventname

J=eventname

E=prefix*

J=prefix*

L=nnn

Syntax Rules: The following rules apply to GJTRJARC parameters:

Follow all standard JCL syntax rules for parameters.

The default operand for ARCH is C.

The default operand for LIST is

Documents

Unicenter®CA-Jobtrac™ Job Management