Man 02101135 e

CA-Jobtrac

Getting Started 3.5

SP1MAN02101135E

This documentation and related computer software program (hereinafter referred to as the “Documentation”) is for the end user’s informational purposes only and is subject to change or withdrawal by Computer Associates International, Inc. (“CA”) at any time.

This documentation may not be copied, transferred, reproduced, disclosed or duplicated, in whole or in part, without the prior written consent of CA. This documentation is proprietary information of CA and protected by the copyright laws of the United States and international treaties.

Notwithstanding the foregoing, licensed users may print a reasonable number of copies of this documentation for their own internal use, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the confidentiality provisions of the license for the software are permitted to have access to such copies.

This right to print copies is limited to the period during which the license for the product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to return to CA the reproduced copies or to certify to CA that same have been destroyed.

To the extent permitted by applicable law, CA provides this documentation “as is” without warranty of any kind, including without limitation, any implied warranties of merchantability, fitness for a particular purpose or noninfringement. In no event will CA be liable to the end user or any third party for any loss or damage, direct or indirect, from the use of this documentation, including without limitation, lost profits, business interruption, goodwill, or lost data, even if CA is expressly advised of such loss or damage.

The use of any product referenced in this documentation and this documentation is governed by the end user’s applicable license agreement.

The manufacturer of this documentation is Computer Associates International, Inc.

Provided with “Restricted Rights” as set forth in 48 C.F.R. Section 12.212, 48 C.F.R. Sections 52.227-19(c)(1) and (2) or DFARS Section 252.227-7013(c)(1)(ii) or applicable successor provisions.

2001 Computer Associates International, Inc.

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

Contents

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . 1-1Summary of Revisions in the Second Edition . . . . . . . . . . 1-2Summary of Revisions . . . . . . . . . . . . . . . . . . . . . . 1-3

Product Changes . . . . . . . . . . . . . . . . . . . . . . . . 1-3Documentation Changes . . . . . . . . . . . . . . . . . . . . 1-7

CA-Jobtrac Features and Benefits . . . . . . . . . . . . . . . . 1-8

Chapter 2. Preparing for Installation . . . . . . . . . . . . . 2-1CA-Jobtrac Concepts . . . . . . . . . . . . . . . . . . . . . . . 2-2

Understanding Locations . . . . . . . . . . . . . . . . . . . . 2-2Understanding CA-Jobtrac Data Sets . . . . . . . . . . . . . 2-5Understanding CA-Jobtrac Libraries . . . . . . . . . . . . . 2-7

Preparing for Installation Considerations . . . . . . . . . . . . 2-9CA-Jobtrac Requirements . . . . . . . . . . . . . . . . . . . 2-9Unicenter TNG Framework for OS/390 . . . . . . . . . . 2-11CA-Earl . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13Subsystems and CA-Jobtrac . . . . . . . . . . . . . . . . . 2-15JES Usage . . . . . . . . . . . . . . . . . . . . . . . . . . 2-16Installation Tape Information . . . . . . . . . . . . . . . . 2-17SMP/E Considerations . . . . . . . . . . . . . . . . . . . . 2-18Data Set Placement Considerations . . . . . . . . . . . . . 2-18Serialization Considerations for Shared DASD Users . . . 2-19CA-Jobtrac Interfaces with Other Products . . . . . . . . . 2-21System Considerations . . . . . . . . . . . . . . . . . . . . 2-23Security Considerations . . . . . . . . . . . . . . . . . . . 2-23

Chapter 3. Installation Tasks . . . . . . . . . . . . . . . . . 3-1Steps to Take . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Step 1: Unload the SAMPJCL Library . . . . . . . . . . . . 3-3Step 2: Unload CA-Jobtrac Documentation . . . . . . . . . 3-4Step 3: Create SMP/E Libraries . . . . . . . . . . . . . . . . 3-4Step 4: Create the Target and Distribution Libraries . . . . 3-5Step 5: Create SMP PROC . . . . . . . . . . . . . . . . . . 3-5Step 6: Perform RECEIVE Processing for CA-Jobtrac . . . 3-6Step 7: Perform APPLY Processing . . . . . . . . . . . . . 3-7Step 8: Perform ACCEPT Processing . . . . . . . . . . . . 3-7Step 9: Link IEFTB724 to GJTRTRT2 (Conditional) . . . . 3-8Step 10: Link CA-Panvalet Modules (Optional) . . . . . . . 3-8Step 11: Link CA-Librarian Modules (Optional) . . . . . . . 3-9Step 12: Updating License Management Program (LMP) Key 3-9Step 13: Merge the CA-Jobtrac API Table (Optional) . . . 3-10Step 14: Create a Dummy IEAVMXIT Exit (Optional) . . 3-11

Contents iii

Contents

Step 15: Installing the @JOBTRAC USS Command(Optional) . . . . . . . . . . . . . . . . . . . . . . . . . . 3-11

Chapter 4. Customization Job Streams . . . . . . . . . . . . 4-1STAGE1 Customization Job . . . . . . . . . . . . . . . . . . . 4-2

Running the STAGE1 Job . . . . . . . . . . . . . . . . . . . 4-2STAGE2 Installation Job Stream . . . . . . . . . . . . . . . . . 4-7

Running the STAGE2 Job . . . . . . . . . . . . . . . . . . . 4-8Ensuring APF Authorization . . . . . . . . . . . . . . . . . 4-8Types of Data Sets Supported . . . . . . . . . . . . . . . . . 4-9Allocating Data Sets . . . . . . . . . . . . . . . . . . . . . . 4-9About the Sysout Capture File . . . . . . . . . . . . . . . 4-14Updating Procedure Libraries . . . . . . . . . . . . . . . . 4-18Using JOBTRAnn to Set Global Options . . . . . . . . . . 4-19The JOBTRAnn Options . . . . . . . . . . . . . . . . . . . 4-20

Chapter 5. Customization Tasks . . . . . . . . . . . . . . . 5-1Modify CA-GSS . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2

Step 1: Modify JCL . . . . . . . . . . . . . . . . . . . . . . 5-2Step 2: Modify CA-GSS Parameters . . . . . . . . . . . . . 5-3Step 3: Activate GoalNet . . . . . . . . . . . . . . . . . . . 5-4Step 4: REXX IMOD Sample Source (Optional) . . . . . . 5-5

Customizing SYS1.PARMLIB . . . . . . . . . . . . . . . . . . 5-6Setting Up Default Authorization . . . . . . . . . . . . . . . . 5-9Setting Up the JES3 Held Job Class . . . . . . . . . . . . . . 5-11Defining Location Information (DYNAMLOC) and Initiation

IMODs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12Updating Your TSO Procedures or CLIST . . . . . . . . . . 5-16Setting Global Options . . . . . . . . . . . . . . . . . . . . . 5-19

Options on the CA-Jobtrac Global Options Panel . . . . . 5-21Options on the Sysout Capture Options Panel . . . . . . . 5-31Options on the Library Definitions Panel . . . . . . . . . . 5-35

Copy the PRODDATE Member . . . . . . . . . . . . . . . . 5-38| Copy the JMFSYM01 Member . . . . . . . . . . . . . . . . . 5-40

Copy the RESOURCE Member . . . . . . . . . . . . . . . . 5-41Copy the EXCLPARM Member . . . . . . . . . . . . . . . . 5-42Maintaining Table Modules . . . . . . . . . . . . . . . . . . . 5-43Setting Up AMR Support . . . . . . . . . . . . . . . . . . . . 5-46Creating IPLTABLE Entries (Optional) . . . . . . . . . . . . 5-47Enabling the SPACE Command . . . . . . . . . . . . . . . . 5-54CA-Jobtrac CA-11 Integration . . . . . . . . . . . . . . . . . 5-55Setting Up CA-JCLTrac . . . . . . . . . . . . . . . . . . . . 5-58

Setting Up a UCT . . . . . . . . . . . . . . . . . . . . . . 5-60Creating the DB2 Objects . . . . . . . . . . . . . . . . . . 5-65Binding the DB2 Plans . . . . . . . . . . . . . . . . . . . 5-67Granting Authority . . . . . . . . . . . . . . . . . . . . . . 5-68

Using Other Sysout Capture Products . . . . . . . . . . . . . 5-69

iv CA-Jobtrac 3.5 Getting Started

Contents

Customizing CA-Jobtrac WorkStation Server . . . . . . . . . 5-71CA-Jobtrac Cross-Platform Scheduling . . . . . . . . . . . . 5-73

CA-GSS Server IMODs . . . . . . . . . . . . . . . . . . . 5-76Global Variables for Cross-Platform Scheduling . . . . . . 5-77Cross-Platform Server ($UNIXPSJT) Password

Requirements Table . . . . . . . . . . . . . . . . . . . . 5-82

Chapter 6. Startup and Verification . . . . . . . . . . . . . 6-1Initialization and Startup . . . . . . . . . . . . . . . . . . . . . 6-2

Initializing CA-Jobtrac Internals . . . . . . . . . . . . . . . 6-2Starting the CA-Jobtrac Task . . . . . . . . . . . . . . . . . 6-3Accessing CA-Jobtrac . . . . . . . . . . . . . . . . . . . . . 6-3Ending the CA-Jobtrac Task . . . . . . . . . . . . . . . . . 6-4

Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5Contents of IVP . . . . . . . . . . . . . . . . . . . . . . . . 6-5

Chapter 7. Upgrading, Testing, Running MultipleCA-Jobtracs . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

General Procedure . . . . . . . . . . . . . . . . . . . . . . . 7-1Memory Requirements . . . . . . . . . . . . . . . . . . . . . 7-1

Version Compatibilities and Incompatibilities . . . . . . . . . . 7-2Compatibilities . . . . . . . . . . . . . . . . . . . . . . . . . 7-2Incompatibilities . . . . . . . . . . . . . . . . . . . . . . . . 7-2Version 3.5 Feature . . . . . . . . . . . . . . . . . . . . . . 7-2

Conversion Notes . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Checkpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3PDS Data Sets . . . . . . . . . . . . . . . . . . . . . . . . . 7-3

Recommended Procedures for Upgrading Your 3.4 Production to3.5 Production . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

Returning to Prior Version . . . . . . . . . . . . . . . . . . 7-5Recommended Procedures to Run 3.4 Production and 3.5

Test System . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7Procedure to Run Multiple CA-Jobtrac STCs on Same CPU . 7-8Procedures for CA-Jobtrac in a Shared DASD Environment . 7-10

Chapter 8. Troubleshooting . . . . . . . . . . . . . . . . . . 8-1Diagnostic Procedures . . . . . . . . . . . . . . . . . . . . . . . 8-2

Collecting Diagnostic Data . . . . . . . . . . . . . . . . . . 8-3Interpreting Diagnostic Data . . . . . . . . . . . . . . . . . . 8-3

Accessing the Online Client Support System . . . . . . . . . . 8-4Requirements for Using StarTCC . . . . . . . . . . . . . . . 8-4StarTCC Security . . . . . . . . . . . . . . . . . . . . . . . . 8-5Accessing StarTCC . . . . . . . . . . . . . . . . . . . . . . 8-5Accessing the Technical Support Phone Services Directory 8-6

CA-TLC: Total License Care . . . . . . . . . . . . . . . . . . . 8-7

Contents v

Contents

Contacting Technical Support . . . . . . . . . . . . . . . . . . 8-8Product Versions and Maintenance . . . . . . . . . . . . . . . . 8-9Requesting Enhancements . . . . . . . . . . . . . . . . . . . 8-10

Appendix A. NJE Support . . . . . . . . . . . . . . . . . . . A-1Installation and Setup . . . . . . . . . . . . . . . . . . . . . . . A-2Job Submission . . . . . . . . . . . . . . . . . . . . . . . . . . A-3Job Execution . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4Job Termination . . . . . . . . . . . . . . . . . . . . . . . . . . A-5ISPF Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6Batch Archiving and JREPORT . . . . . . . . . . . . . . . . . A-8REXX Stack Information for NJE Jobs . . . . . . . . . . . . . A-9

Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9

Appendix B. Connecting Systems for Cross-PlatformScheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

OS/390 CAICCI Installation and Considerations . . . . . . . . B-2Unicenter TNG (NT) Installation and Considerations . . . . B-3

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

vi CA-Jobtrac 3.5 Getting Started

Chapter 1. Introduction

This guide describes how to install the Computer AssociatesInternational, Inc., proprietary software product, CA-Jobtrac Version3.5.

This guide is written for systems software programmers andpersonnel responsible for the installation, implementation, andmaintenance of CA-Jobtrac.

Chapter 1. Introduction 1-1

Summary of Revisions in the Second Edition

Summary of Revisions in the Second EditionThe second edition of this guide includes these changes (see revisionmarks in the margins):

■ We made changes to “Copy the JMFSYM01 Member” onpage 5-40.

■ We made corrections to “Disabling AMR Support” on page 5-46.

1-2 CA-Jobtrac 3.5 Getting Started

Summary of Revisions

Summary of RevisionsThis topic explains changes to CA-Jobtrac and to the documentation.

Product Changes

Version 3.5 of CA-Jobtrac contains the following new features:

■ Critical Path Monitoring

Through integration with CA-OPS/MVS II, Unicenter TNG andUnicenter TNG MVS Event Manager Option (MEMO), CA-Jobtraccan support the definition and monitoring of critical job flowswithin the CA-Jobtrac workload. CA-OPS/MVS II providesmanagement and administration of critical path displays.

■ Two-character Resource Codes

The resource codes available in CA-Jobtrac have been expanded byallowing for two-character codes. In most cases, this wasimplemented without requiring changes to your existing resourcesdefinition. CA-Jobtrac still supports the R= referback for singlecharacter resources in the RESOURCE member. Two affectedareas require changes if you are using these features: @JOBTRACand the REXIT user exit.

@JOBTRAC is used from CA-GSS and GJTRABTR uses theRMG() parameter to specify the resources codes. The format of theparameter has changed to support the two-character codes. Blanksmust now separate the codes if multiple codes are entered. Forexample, codes a, b, and c would have previously been specified asRMG(abc). This needs to be changed to RMG(a b c). Also thereturned stack entry for resources, RSMG, returns the codes in ablank separated list, instead of as a single value. Previously, theentry would have read:

RSMG ABC

Now it reads:

RSMG A B C

The REXIT resource exit needs to be altered to accommodate thetwo-character resources. The @RSOURCE macro that maps theresource has changed to define the field RSCODE as twocharacters. If your exit examines this code, you need to make theappropriate changes to support the new format. At a minimum, theexit will require a reassembly to include the new @RSOURCEmacro format.



■ UNIX System Services Interface

The OS/390 UNIX System Services (USS) CA-Jobtrac interfaceallows communication with CA-Jobtrac from the USS environment.The interface can be called directly from the UNIX shell or fromthe IBM USS batch interface (BPXBATCH).

■ Workload Management and CA-Jobtrac

CA-Jobtrac interfaces in two ways with IBM's Workload Manager(WLM). First, a WLM scheduling environment may optionally beinserted into JCL during submission. Second, a WLM schedulingresource may be set ON when CA-Jobtrac begins execution andOFF when CA-Jobtrac terminates. The WLM schedulingenvironment and WLM scheduling resource may be used to limiton which systems jobs execute, or even what CPU resources areassigned to jobs.

■ ARM

To improve recovery capabilities in CA-Jobtrac, support for IBM'sAutomatic Restart Management Function is included in thisversion. CA-Jobtrac registers with ARM during initialization andderegisters at normal termination. A new initialization keyword,ARM=, can be used to specify abends that should not be restarted,which causes CA-Jobtrac to deregister from ARM if they occur.Also, the ARM= keyword allows for disabling the ARM support.This new support provides increased recoverability for CA-Jobtrac.

■ CA-Earl Report Writing

Support for the CA-Earl Report Writer product is included in thisversion. This common component is distributed with UnicenterTNG Framework for OS/390 and can be used to write customizedreports from the CA-Jobtrac checkpoint and history files. Samplereports are provided.

■ Cross-Platform External Tracking

CA-Jobtrac may be used to track external events (JOBINIT,JOBTERM, and DSCLOSE) on remote platforms runningUnicenter TNG or CA-Jobtrac Agent that do not originate withCA-Jobtrac. When a specified event is detected, an associatedCA-Jobtrac command will be issued.

■ DYNAMLOC Concatenations

The DYNAMLOC facility for dynamically allocating theCA-Jobtrac location data sets has been enhanced to allow for datasets to be concatenated to the location DDNAMEs.



■ Enhanced SCL LOAD Syntax Checking

In the SCL column 58, which was not previously used, thepresence of any character in this column causes the SCL LOAD toABORT. The PROCESS PERIOD field is now syntax checked forvalid process periods. On an IP (input) parameter, the NODEstatement is checked to ensure only one NODE statement is found.

■ Other New Options

– AMRLCNT

Allows you to specify the limit for processing of duplicatemessages by the CA-Jobtrac Automatic Message Replies (AMR)feature. This value defines the maximum number of times amessage is processed before the messages are considered in aloop and processing for the messages is terminated.

– CAPDMPS

Allows for system dump output to be captured by the CA-Jobtracsysout capture feature. Normally, dumps are not stored on thesysout capture file.

– DISABLE

Allows for CA-Jobtrac ISPF line commands to be disabled,effectively removing the command from the online system.

– DUMPUJV

Allows for suppression of dumps that are taken in theCA-Jobtrac IEFUJV exit due to problems accessing theCA-Jobtrac checkpoint.

– JCLTABL

Specifies the maximum number of lines of JCL per JOB.

– JMFTABLE

Allows you to set the size of the JCL Modification Table (JMF)to meet your needs.

– RAMAXCC

Allows you to set the MAXCC default for jobs that are addedusing the RUN or ADD CA-Jobtrac ISPF commands. Besides anumeric value, you can specify N to indicate no condition codechecking should be done.

– TNDOVLP

Signals the CA-Jobtrac schedule load process whether toconsider a TIME/DATE overlap as an error.



■ SMP/E Environment Changes to Conform to Computer AssociatesStandards

The target and distribution libraries for CA-Jobtrac now conform tothe Computer Associates format. Also, reworking the SMP/Estructure placed all components in a single CSI, rather than in threeCSIs. The changes in the data set names are listed below:

CA-Jobtrac 3.4 Name CA-Jobtrac 3.5 Name

CHD34CLS CHD35CLD

CHD34DBR CHD35XLD

CHD34INS None, CHD35XLD, andCHD35CLD

CHD34LIB CHD35LLD

CHD34MAC CHD35XLD

CHD34MLI CHD35MLD

CHD34PLI CHD35PLD

TRACLIB CAILIB

TRACCLST CAICLIB

DBRMLIB CAIMAC

TRACINST SAMPJCL, CAIMAC, andCAICLIB

TRACMAC CAIMAC

TRACMLIB CAIISPM

TRACPLIB CAIISPP

TRACPARM PPOPTION



Documentation Changes

The documentation for CA-Jobtrac Version 3.5 differs from previousversions as follows:

■ The documentation set has been engineered to take advantage ofthe latest technology for online viewing, keyword searching, bookmarking, and printing. This set contains a hardcopy CA-JobtracGetting Started guide and Version 3.5 of CA-Jobtrac for OS/390documentation in both IBM BookManager and Adobe AcrobatReader format on the tape.

■ The CA-Jobtrac Getting Started guide replaces the CA-JobtracInstallation and Maintenance Guide.

■ These chapters and appendixes from the former CA-JobtracInstallation and Maintenance Guide moved to the CA-JobtracReports, Maintenance, and Recovery Guide: User Exits,TRACAUTH Security, JFST Access Method, and The SysoutCapture File.

■ Syntax diagrams are now standardized within the IBMBookManager format. See Reading Syntax Diagrams in theCA-Jobtrac Operator Guide for more information.

■ Unicenter TNG Framework for OS/390 is composed of the servicesformerly known as CA90s and Unicenter TNG Framework.


CA-Jobtrac Features and Benefits

CA-Jobtrac Features and BenefitsThe CA-Jobtrac primary function is to automate productionscheduling. CA-Jobtrac schedules, submits, tracks, and records eventsat the proper time, in exact sequence, the first and every time, withlittle or no manual intervention.

CA-Jobtrac offers diverse methods to create schedules. These are:

■ ISPF EDIT to code the member with SCL (Schedule ControlLanguage)

■ GSO (Generate Schedules Online) panels that gather informationand generate the SCL

Production Scheduling FeaturesThe following are features of the CA-Jobtrac production schedulingcomponent:

■ Total automation of event scheduling. Once an event is definedto the system, no further action is required to schedule that eventor set of events. They will be scheduled on the proper days, at theproper times, in the proper sequence, automatically, permanently.

■ Dependency scheduling. CA-Jobtrac schedules and submits eventsbased on dependencies you define for each event. Schedulingdependencies determine if and when a given event is scheduled(for example, on the last workday of each month). Executiondependencies determine when a scheduled event is submitted (forexample, after a specified data set is created).

■ No complex calendar definitions. Scheduling parameters definethe cycles, frequencies, and dependencies for each event in alogical, straightforward approach. Unlike schedulers that requireyou to build a daily processing calendar for every day of the year,CA-Jobtrac builds a dynamic calendar each workday to processscheduled events.

■ Threshold scheduling. CA-Jobtrac lets you set start, target, andabort times so that events execute at peak efficiency, without rigidtime schedules.

■ Mass schedule alterations. You can issue a single command tomake sweeping adjustments to the current schedule. You can adjustsubmission times forward or backward up to 24 hours for aspecific event or all scheduled events.



■ Automatic JCL submission and event tracking. Once an event isscheduled, it is automatically submitted when all dependencies aresatisfied. The event is then tracked through completion.CA-Jobtrac also supports automatic JCL alteration in the form ofoverrides or date statements.

■ On-demand event submission. CA-Jobtrac accommodates thedynamic realities of production control. Using CA-Jobtrac, you canquickly and easily add on-demand events to the schedule forCA-Jobtrac processing.

■ Data set triggering. You can specify that the creation or update ofa data set triggers some event, such as event submission.

■ Distributed and decentralized scheduling. You can have oneperson per group take care of their scheduling needs (up to 254separate locations), or you can have one person take care of thescheduling needs of all groups.

■ Tape volume pull lists. CA-Jobtrac indicates the tape volumesneeded for production during the processing day.

■ Production control tools. CA-Jobtrac provides an array of onlineinquiries, error-checking and reporting capabilities, and statusreports. Included are online event documentation, event historyanalysis, DASD space analysis, schedule forecasting, and online orprinted reports.

REXXCA-Jobtrac takes full advantage of Computer Associatesimplementation of REXX. You can schedule REXX IMODs(Intelligent Modules) just as you have always done for events, andyou can use REXX IMODs as scheduling dependencies. UsingIMODs as dependencies adds unlimited power to CA-Jobtrac bygiving you complete flexibility in deciding when to schedule anevent.

To increase this power even more, @JOBTRAC was created.@JOBTRAC gives you the ability to obtain information about thecurrent schedule and to change the current schedule using an IMOD.@JOBTRAC uses CA-GSS (Global SubSystem). CA-GSS interactswith other Computer Associates products, giving you the ability toobtain information from even more sources and to provideCA-Jobtrac information to them.



Automatic Message RecognitionThe CA-Jobtrac AMR (Automatic Message Recognition) facilityenables you to monitor system messages and prompts and to respondto them automatically. For example, you can:

■ Translate complex technical system messages into plain Englishmessages

■ Release an event or schedule for submission when a specifiedsystem message is issued

■ Schedule a response to an outstanding message

■ Reply to system prompts

System Command SchedulingCA-Jobtrac can issue any OS/390, JES, VTAM, or task modify (F)command automatically at scheduled times or at specific intervals.Even IPLs can be automated.

Specifying Additional Condition CodesCA-Jobtrac gives you ways to impose condition code processing on aprogram, job, job step, or procstep. Condition code processing checksfor specified condition codes being returned. If the condition codeyou define is violated, CA-Jobtrac imposes a dependency requiringyou to check the event's output before successor events can besubmitted.

JCL ManagementCA-Jobtrac offers various features that enhance JCL usage. Thesefeatures are:

■ AJO (Automatic JCL Override) - automatically deletes or insertsspecified JCL statements when an event is submitted byCA-Jobtrac.

■ JMF (JCL Management Facility) - enables you to:

– Make global variable changes to JCL

– Insert parameter statements or values into JCL

– Provide date values based on the original schedule date or theprocessor clock

– Allow date arithmetic for dynamic date variables

– Allow input definitions from multiple PDS libraries

– Use over 40 dynamic variable assignments for date and timevalues



■ By using the ADI (Automatic Date Insertion) feature, you candirect CA-Jobtrac to automatically insert JCL dates and repeatedrecords in your events, and you can specify that CA-Jobtracautomatically calculate and insert dates in the record.

■ CA-JCLTrac performs basic JCL syntax checking and gathersinformation about your JCL usage and stores it in a DB2 databaseor in a JCL extract file. You can then generate reports with thestored information. Additionally, CA-JCLTrac can forecast whatyour JCL will look like on any given day.

Sysout ArchivalCA-Jobtrac automatically captures and archives specified sysoutlistings, providing online access to recent sysouts and permanentarchival to tape. Additionally, CA-Jobtrac interfaces with theCA-View product, which is a powerful sysout archival and retrievaltool.

Other BenefitsOther important benefits include the following:

■ CA LMP.

■ No SVCs or IPLs are required for scheduler operation for mostenvironments.

■ No dedicated hardware is required.

■ CA-Jobtrac requires less than 100KB of CSA below the line, andless than 120 cylinders of 3380 space.

■ CA-Jobtrac uses standard PDS files; no database language must belearned.

■ Interval processing to submit an event multiple times during aprocessing period.



Chapter 2. Preparing for Installation

This chapter discusses ways for you to prepare for installation ofCA-Jobtrac.

Chapter 2. Preparing for Installation 2-1

CA-Jobtrac Concepts

CA-Jobtrac ConceptsThe following topics introduce you to CA-Jobtrac locations, data sets,and libraries.

Understanding Locations

To effectively install and use CA-Jobtrac, you need to understandCA-Jobtrac locations.

A location groups CA-Jobtrac entities to provide distributed controlover production. Locations can be:

■ Physical, such as New York and Chicago

■ Logical, such as accounting department and shipping department

What Entities Have LocationsThe following CA-Jobtrac entities have a location associated withthem:

■ Libraries

■ Users

■ Holiday calendars

■ Cyclic calendars

■ Workdays

■ Schedules

■ Events

Location IDsLocations are defined by a location ID. The location ID is athree-digit code used by CA-Jobtrac to determine the following:

■ Which calendars, workdays, and libraries an event uses

■ What functions a user can perform

For example, if schedule PAYROLL1 has location 004 associatedwith it, it can only access calendars, workdays, and librariesassociated with location 004.

As another example, if Susan has only location 010 associated withher with delete and add functions allowed, she can only delete anevent with location 010 associated with it.


CA-Jobtrac Concepts

Users can have multiple location IDs associated with them. All otherentities in CA-Jobtrac are associated with one location ID only.

Location 000Location 000 has a significant meaning in CA-Jobtrac. Thefollowing explains its significance:

■ In general, the default location is 000 (zero). This default isoverridden by the following:

– The JOBTRAnn option DEFAULT0 is set to NO rather thanYES. If DEFAULT0 is set to NO, no default location ID isassumed.

– A user has specified a default location using the PROFilecommand.

■ The 0ARCHIVE, 0SYSARCH, and 0JOBARCH tasks always havelocation 000 associated with them.

Default LocationUsers have what is known as a default location. The default locationID is assigned by the user using the PROFile command. For a user,if a location ID is not specified for an activity, the user will use theirdefault location ID.

For example, Bob has location 226, 040, and 111 associated withhim. He has assigned location 226 as his default location ID. He addsan event to the current schedule, without specifying a location ID forthe event. It is added with a location ID of 226, because that is Bob'sdefault location.

Assigning Location IDsLocation IDs are assigned to an entity as described in the followingtable:

Entity How a location ID is assigned

Holidaycalendars

Holiday calendar definitions include alocation ID. Holiday calendars are definedto CA-Jobtrac using the Holiday Calendarspanel.

Cyclic calendars Cyclic calendar definitions include alocation ID. Cyclic calendars are defined toCA-Jobtrac using the Cyclic Calendarspanel.


CA-Jobtrac Concepts

Entity How a location ID is assigned

Library'sddname

The last three digits of a library's ddnamedetermine the location ID for everything inthe library. For example, TRACT002specifies a temporary-use JCL library forlocation 002.

User A user is assigned one or more location IDsusing the TRACAUTH table.

A user can have temporary location IDsassigned using the Authorization Profilepanel.

A user assigns a default location ID usingthe PROFile command.

Workdays Workdays are associated with a location IDaccording to the schedule they are used in.By default, the workdays have the samelocation ID as the schedule.

Within a schedule, you can change thelocation ID for workdays.

Schedules A schedule's location ID is assigned by thelibrary in which the schedule memberresides. For example, if the member is inthe SCL library named TRACS003, theschedule's location ID is 003. All events inthe schedule have location ID 003 assignedby default.

Within a schedule, you can change thelocation ID for events.

Events Location IDs are assigned to events whenthey are placed on the current schedule.

If an event is automatically added by aschedule, the schedule assigns the locationID.

If an event is manually added, you assignthe location ID.


CA-Jobtrac Concepts

Understanding CA-Jobtrac Data Sets

CA-Jobtrac uses a number of data sets that store working data. If yourun multiple CA-Jobtracs, each one has a set of data sets associatedwith it.

CA-Jobtrac uses the following data sets:

■ Checkpoint

■ History file

■ Data component of the history file

■ CA-Jobtrac setup files

Checkpoint Data Set

The checkpoint contains the current schedule in addition to otherCA-Jobtrac information such as global options.

The current schedule is the active schedule. It is dynamic, changingas events finish, start, and wait for execution. Loading a scheduleadds its events to the current schedule.

The DD naming convention is:

JOBTRACx (JOBTRACY is the default.)

History File Data Set

The history file is the audit backup file for CA-Jobtrac. It is aVSAM file. It tracks the history of completed events, stores changehistory, stores holiday and cyclic calendars, and table servicesinformation.


JOBHISTx (JOBHISTY is the default.)


CA-Jobtrac Concepts

History File Sequential Data Set

The history data file is the data component of the history file.CA-Jobtrac uses this data set to improve the efficiency of scanningthe history file. The history data file stores the data referenced by thehistory file.


SEQHISTx (SEQHISTY is the default.)

Capture File Data Set

The capture file is used to store the output from schedule loads andto archive SYSOUT data from CA-Jobtrac jobs.


CAPTURE (CAPTURE is the default.)

CA-Jobtrac Setup Files

The CA-Jobtrac setup files contain global information used byCA-Jobtrac while it is processing.

The DD naming convention for files in the PPOPTION data set is:

TRACPARM (TRACPARM is the default.)


CA-Jobtrac Concepts

Differentiating CA-Jobtracs

One or more TRACPARM libraries can be defined for all theCA-Jobtracs running on a system. The correct library to use isspecified on the TRACPARM DD statement in the CA-Jobtracstarted task procedure.

JOBTRAnn (JOBTRA00 is the default.)

The JOBTRAnn member describes the environment in whichCA-Jobtrac operates and customizes how CA-Jobtrac functions.

Multiple JOBTRAnn members can be defined. You can use each ofthese members to test a different configuration of options, or to runmultiple CA-Jobtracs. To activate the options in a given JOBTRAnnmember, issue the following modify command, where nn matches nnin the desired JOBTRAnn member:

F taskname,OPTS=nn

RESOURCE (RESOURCE is the default.)

The RESOURCE member contains resource definitions you canassign to events as dependencies.

Within the PPOPTION library, one EXCLPARM member is definedfor all CA-Jobtracs running on a system.

EXCLPARM (EXCLPARM is the default.)

The EXCLPARM member defines mutually exclusive events.

Within the PPOPTION library, one EXCLPARM member is definedfor all CA-Jobtracs running on a system.

Understanding CA-Jobtrac Libraries

CA-Jobtrac uses a number of PDS-type libraries to store productionJCL, schedules, job documentation, date and JCL variables, andtemporary-use JCL.

Each library is associated with a location. In this way, you canprovide distributed control over production.


CA-Jobtrac Concepts

Libraries Used

The following libraries are used in CA-Jobtrac. The last three digits(nnn) of a library's ddname correspond to a location ID. All membersin the library are associated with that location ID by default. Forexample, TRACT002 specifies a temporary-use JCL library forlocation 002.

Type DD NamingConvention

Contents

Date file DATELIB Each library contains a JMFSYM01 and aPRODDATE member (default member names).The JMFSYM01 member contains JMFvariable definitions. The PRODDATE membercontains ADI definitions.

Documentation TRACDnnn(TRACD000 isthe default.)

Each member contains the following for anevent:

■ Information about an event you want theoperator to have.

■ Messages to be printed for the event's entryon the JREPORT3 Schedule Report.

■ Manual actions the operator is to perform.

JCL TRACJnnn(TRACJ000 is thedefault.)

Each member contains the production JCL thatis run for scheduled events.

Remote Password TRACRnnn(TRACR000 isthe default.)

Member contains encrypted user ID andpassword information for events that are to besubmitted to Unicenter TNG on a remoteplatform.

SCL TRACSnnn(TRACS000 isthe default.)

Each member contains a schedule controllanguage data set.

Temporary-useJCL

TRACTnnn(TRACT000 isthe default.)

When you want to temporarily modify JCLbefore running it, a copy of the production JCLis made and put in a temporary-use JCL librarymember. The event then uses the JCL from thetemporary-use library rather than the JCLlibrary.


Preparing for Installation Considerations

Preparing for Installation ConsiderationsBefore starting the installation procedure, you should

■ Read the installation documentation.

■ Consider various preparing for installation issues.

■ Complete pre-installation worklists to plan data set names,volumes, and other installation-specific information.

CA-Jobtrac Requirements

The following sections describe the hardware and software requiredfor successful CA-Jobtrac operation.

Hardware RequirementsCA-Jobtrac is supported on any IBM supported or IBM-compatiblemainframe computer capable of supporting unmodified versions ofthe indicated operating systems.

Software RequirementsCA-Jobtrac is supported under any IBM supported operating systemsand ISPF.

CA-Jobtrac uses standard IBM interfaces to accomplish scheduling,sysout capture, and all other functions. There are no hooks, zaps toIBM code, or other nonstandard interactions with your operatingsystem.

Peripheral DevicesCA-Jobtrac supports all devices supported by unmodified versions ofthe supported operating systems.



Detailed Memory RequirementsThe following table describes the memory requirements forCA-Jobtrac:

Component ECSAUsage

CSAUsage

Total

Internals and exits 100KB 60KB 160KB

Job table 30KB -- 30KB

VMXT tables 30KB -- 30KB

JMF table 140KB -- 140KB

AMR (Automatic MessageRecognition) table

380KB -- 380KB

ADR (Automatic DatasetRecognition) table

20KB -- 20KB

SCS (System CommandScheduling) table

57KB -- 57KB

CCPF (Condition CodeProgram Filters) table

27KB -- 27KB

Checkpoint index (for a 4cylinder checkpoint)*

111KB -- 111KB

Note: * More ECSA is required for larger checkpoint files.

** ISERVEs are optional, but each one used requires 96KB ofECSA.

Summary Memory RequirementsThe following table summarizes the memory requirements forCA-Jobtrac:

ECSA Usage CSA Usage Total

903KB 60KB 963KB

FMIDCA-Jobtrac has one FMID. It is CHD3500.



Unicenter TNG Framework for OS/390

CA-Jobtrac REQUIRES the following Unicenter TNG Frameworkfor OS/390 Common Services:

■ CA LMP

■ CA-GSS/CA-GREXX

■ CAIRIM

CA-Jobtrac optionally uses the following Unicenter TNG Frameworkfor OS/390 Common Services:

■ CA-C Runtime

■ CA-EARL

■ CA-XPS

■ CAICCI

■ CAIENF

■ ViewPoint

If other Computer Associates products are installed at your site, someof these services may already be installed.

This section presents an overview of each of these services. See theUnicenter TNG Framework for OS/390 Getting Started andAdministrator Guide for more information.

CA LMP

The CA License Management Program provides a standardized andautomated approach to the tracking of licensed software. It usescommon realtime enforcement software to validate the client'sconfiguration. CA LMP reports on activities related to the license,usage and financials of Computer Associates products. The routineswhich accomplish this are integrated into the CAIRIM service.

CA-Jobtrac requires the CA LMP service.



CA-GSS

The Global SubSystem (CA-GSS) is a product which offers softwarethat performs across many of Computer Associates' product families.CA-GSS enables Computer Associates products to communicate witheach other easily, and is designed to help meet the increasing need ofdata center operations for quick access to information from manydifferent sources. For example, CA-GSS allows CA-Jobtrac toaccess data gathered by CA-SYSVIEW/E. This information can beused when determining how to schedule a particular job.

CA-Jobtrac requires the CA-GSS service.

CAIRIM

CAIRIM, CAI Resource Initialization Manager, is the common driverfor a collection of dynamic initialization routines that eliminate theneed for user SVCs, SMF exits, subsystems, and other installationrequirements commonly encountered when installing systemssoftware.

CA-Jobtrac requires the CAIRIM service.

CA-C

CA-C Runtime is a runtime facility with reentrant capabilities. Itsmodular architecture insulates CA-C Runtime programs from systemand version dependencies. There is little, if any, system-dependentcode linked with the user program. This allows for smaller userprograms and easier maintenance. CA-C Runtime uses a memorymanager to handle dynamic allocation requests for small pieces ofstorage. This enables fewer calls to be made on the operating systemresulting in faster allocation and deallocation.

Remote scheduling requires the CA-C Runtime service.



CA-Earl

The CA-Earl (Easy Access Report Language) Reporting Componentis a user-friendly report definition facility with the power of acomprehensive programming system. CA-Earl allows you to modifyand print the contents and layout of a predefined ComputerAssociates product report using English-like statements.

The CA-Earl service is required if you wish to produce CA-Jobtracreports using the CA-Earl facilities.

CA-XPS

CA-XPS is the Cross-Platform Scheduling router. It is used whenUnicenter TNG requests a job to be executed on OS/390. Requestsare sent from Unicenter TNG to CA-XPS, which then forwards therequest to a specific scheduling product. CA-XPS allows multiplecopies of CA-Jobtrac (or CA-7 or CA-Scheduler) to participate incross-platform scheduling on the same OS/390 image.

Remote scheduling requires the CA-XPS service.

CAICCI

CAICCI, CAI Common Communications Interface, is acommunications facility that offers a simple yet flexible approachenabling Computer Associates solutions to communicate with oneanother. This facility provides a layer that isolates applicationsoftware from the specifics of the communications environment.

Remote scheduling requires the CAICCI service and CA-JobtracWorkStation.



CAIENF

CAIENF, CAI Event Notification Facility, is an operating systeminterface service which offers a simple yet flexible approach forComputer Associates solutions to obtain data from the operatingsystem. By centralizing operating system interfaces within CAIENF,many features which were formerly available within a single solutioncan be shared across the entire product line.

Remote scheduling requires the CAIENF service.

ViewPoint

CA-Jobtrac WorkStation requires the ViewPoint service.



Subsystems and CA-Jobtrac

CA-Jobtrac uses two subsystems: GOAL and JT35.

Caution

CA-Jobtrac must have CA-GSS installed. Although you can runCA-Jobtrac without CA-GSS active, the CA-GSS CAILIB mustbe available to CA-Jobtrac.

Note: CA-GSS is part of Unicenter TNG Framework forOS/390.

CA-GSS SupportWe require that you install CA-GSS prior to installing CA-Jobtrac.

CA-GSS uses a subsystem named GOAL. It dynamically installs asubsystem with this name.

CA-GSS ISET AvailabilityThis ISET is for the product IMODs shipped with CA-Jobtrac.CA-Jobtrac will not install properly if the ISET is not available.

You can use this ISET or define another for your own use. TheCA-Jobtrac installation procedure STAGE2 allocates and populatesthe CA-Jobtrac required ISET data set.

CA-GSS must be set up to include networking support for all JESnodes in which CA-Jobtrac is to be used for NJE support. This isdone using the GoalNet features of CA-GSS.

See the Unicenter TNG Framework for OS/390 documentation forinformation about GoalNet.



JES Usage

All systems that run scheduled batch jobs must be able tocommunicate with the CA-Jobtrac checkpoint data set.

Job tracking is performed by CSA resident subroutines loaded by theCA-Jobtrac startup procedures.

Pre-JES RequirementThe VINIT3 task is required only for pre-JES console automationand possible pre-JES startup data triggering functions. During initialtesting or implementation, you usually do not need to start VINIT3during IPLs (S VINIT3,PARM=IPL).

JES2 RequirementIf you are using the BSPACE parameter in the CONDEF statementdefined in the JES2INIT file using characters @, #, or $, it willconflict with the internal verification procedure job JOBT@#$J.

JOBT@ characters. If you are using one of these characters, changeit to a different character to avoid any problems.

JES3 RequirementsAccomplish the following to use JES3 with CA-Jobtrac:

■ Add the JOBTRACx ddname to your JES3 and JES3CI procedures,or dynamically allocate it.

■ Add a SUBSYS(STC) statement to your SMFPRMnn member inSYS1.PARMLIB. This statement can be specified as follows:

SUBSYS(STC,EXITS(IEFU83)

If you already have a SUBSYS(STC) statement you do not need tochange it.

JES InteractionThe CA-Jobtrac STC is active on all systems in the JES complex(shared spool environment).

You can think of CA-Jobtrac as a logical extension to JES. JESmonitors a job from submission through printout, and CA-Jobtracextends those boundaries to include scheduling, submission,execution, and historical archival. The JES checkpoint data setindicates only those jobs that are currently queued for execution orprinting. The CA-Jobtrac checkpoint data set indicates events queuedfor submission, execution, or history archival.



CA-Jobtrac works the same way with JES3 as it does with JES2,except that the queue class and JOB statement AUTO-SCHD featuresare not supported. To AUTO-SCHD events in a JES3 system, youmust use the step method. See the CA-Jobtrac Operator Guide formore information.

CA-Jobtrac does not scan the JES spool for job status. CA-Jobtracuses information from SMF exits to establish event status.

Cycling JESIf you must cycle JES2 or JES3, you must also cycle CA-Jobtrac. Ifyou do not, CA-Jobtrac will not work properly.

Installation Tape Information

CA-Jobtrac is distributed on a single, standard-label cartridge whichmust be installed using SMP. The cartridge is prepared in IBM SMPRELFILE (unloaded PDS) format. See the IBM SMP GeneralInformation Manual for information about IBM SMP RELFILEformat.

The following table describes the files on the tape used byCA-Jobtrac:

File Data Set Name Description

009 CAI.SAMPJCL CA-Jobtrac Sample JCL library

011 REXX.SAMPLES CA-Jobtrac Sample REXX library

013 CAI.BKMGR CA-Jobtrac BookManager files

014 CAI.PDFDOC CA-Jobtrac Adobe Documentation files

032 SMPMCS SMP Modification Control Statements

033 sysmod.Fn SMP RELFILEs begin here

. " "

. " "

082 " "



SMP/E Considerations

You use SMP/E to install CA-Jobtrac. This manual assumes that youare familiar with SMP/E. If you have not previously installedprogram products using SMP/E, review this entire installation guidebefore you begin the installation.

Check with your SMP/E systems programmer if you have questionsabout your SMP/E environment.

The installation creates new global, target, and distribution zones.Two cylinders of 3390 space for each CSI should be sufficient forCA-Jobtrac functions and allow for growth required by futuremaintenance.

Data Set Placement Considerations

Carefully plan the placement of the following data sets.

CA-Jobtrac CheckpointThis data set is the key control point in the CA-Jobtrac system. Thecheckpoint is a small data set that is updated by TSO users, by JES,and by events tracked through CA-Jobtrac.

Reserves are not issued against this data set. However, it should notbe placed on any pack with suspended channel programs (such aspage/swap data sets) or any pack that will draw significant reserveactivity (such as catalog packs or JES checkpoint packs).

If you plan to run CA-Jobtrac on multiple systems that share DASD,the checkpoint data set must be on a shared pack. The checkpointuses a proprietary format called JFST. (See the "JFST AccessMethod" chapter of the CA-Jobtrac Reports, Maintenance, andRecovery Guide for information about JFST.) You should place thecheckpoint on a non-SMS managed volume. The checkpointperforms best on non-CACHE devices unless you are using DASDFast Write (DFW).



CA-Jobtrac History FileThis data set is the audit backup file for CA-Jobtrac. It tracks thehistory of completed events. Although updated less frequently thanthe checkpoint, it is updated under reserves. Since some CA-Jobtraccomponents keep table information in the history file, and it isaccessed online, you should ensure reasonable I/O response times forthis file. It should not be placed on the same pack as the checkpointor on a pack with heavy I/O activity. If you plan to run CA-Jobtracon multiple systems that share DASD, the history file must be on ashared pack. The data set can be SMS or non-SMS and wouldperform well on a CACHE device with DASD Fast Write (DFW).The JOBHIST file cannot span volumes.

Sysout Capture FileThe sysout capture file stores captured sysouts for online viewing andsubsequent archival, printing, or deletion.

If you plan to use the sysout capture file as your primary sysoutcapture system, you should place it where your TSO users will getadequate response time.

If you plan to run CA-Jobtrac on multiple systems that share DASD,the sysout capture file must be on a pack on your primary(event-submitting) CA-Jobtrac system.

Most users will put it on shared DASD so that TSO users from eachsystem can view sysouts. No reserves are issued against the sysoutcapture file. You should place the sysout capture file on a non-SMSmanaged volume.

Also see “Using Other Sysout Capture Products” on page 5-69 formore information.

Serialization Considerations for Shared DASD Users

If you run CA-Jobtrac on two or more systems sharing DASD, youmight have a package that can convert reserves into enqueues. Othersimilar packages include Computer Associates Multi-Image Integrityand IBM's GRS (running with a channel-to-channel adapter).Computer Associates MSI and SDSI packages also convert reservesinto enqueues, but are precursors to CA-Multi-Image Integrity.



The following sections describe serialization considerations.

Major CA-Jobtrac SerializationThe following table describes CA-Jobtrac serialization issues:

QNAME RNAME Reserve? Comments and Recommendations

JOBHISTx HISTPOST Yes You may allow your package toconvert this reserve. Considerationsare as follows:

■ If you allow your package toconvert the reserve, there should beno adverse effect on your system.

■ If you do not allow your package toconvert the reserve, you should alsoexempt enqueue requests forQNAMES SYSDSN andSYSVSAM with RNAME of yourhistory file's components (cluster,index, and data) from globalprocessing.

Major IBM SerializationBesides the CA-Jobtrac serialization described above, IBM's normalVSAM processing involves serialization. The following tablediscusses the key points necessary for CA-Jobtrac planning.

QNAMEs Comments and Recommendations

SYSZVVDSSYSVTOC

These enqueue/reserves are used to serializevarious parts of system processing in VSAM.The important thing to note here is that theseenqueues are obtained as a set and must beprocessed consistently. That is, if yourpackage processes any of them, it shouldprocess all of them. Failure to do this cancause deadly embraces in any shared VSAMfile processing, including that of CA-Jobtrac.



CA-Jobtrac Interfaces with Other Products

CA-Jobtrac interacts with other products as described in thefollowing sections.

CA-Blockmaster

Exclude CA-Jobtrac programs by adding the following to theCA-Blockmaster Exclude table:

BLMTABLE TYPE=E,PGM=GJC�

BLMTABLE TYPE=E,PGM=GJTR�

BLMTABLE TYPE=E,PGM=GJC3�

BLMTABLE TYPE=E,PGM=JCL3�

CA-HYPER-BUF

Exclude the CA-Jobtrac files and programs.

MODE=EXCLUDE PROGRAM=GJTR�

CA-Librarian

With CA-Jobtrac, you can use a CA-Librarian JCL library instead ofa standard PDS JCL library. For more information aboutCA-Librarian, see the CA-Librarian support information inChapter 3, “Installation Tasks” and the PDS and library managementinformation in Chapter 4, “Customization Job Streams.”

CA-Multi-Image Manager

CA-Multi-Image Manager is Computer Associates family of softwareproducts that makes sharing resources in multi-image andmulti-system environments safe and efficient. CA-Multi-ImageManager consists of Multi-Image Allocation, Multi-Image Integrity,and Multi-Image Console.

Multi-Image Integrity is used to share DASD. For serializationconsiderations when using CA-Jobtrac and Multi-Image Integrity, see“Serialization Considerations for Shared DASD Users” on page 2-19.



CA-Panvalet

With CA-Jobtrac, you can use a CA-Panvalet JCL library instead ofa standard PDS JCL library. For more information aboutCA-Panvalet, see Chapter 3, “Installation Tasks” and the PDS andlibrary management information in Chapter 4, “Customization JobStreams.”

CA-SYSVIEW/E

CA-SYSVIEW/E is a powerful system tool that enables you to accessinformation about your system and what is running on it. Forexample, you can check the amount of free space on a particularvolume or determine the availability of tape drives.

CA-Jobtrac enables you to use CA-SYSVIEW/E without exitingCA-Jobtrac (use the Q line command). You can also useCA-SYSVIEW/E with @JOBTRAC. To use CA-SYSVIEW/E fromCA-Jobtrac, you must meet the following conditions:

■ You must be a licensed CA-SYSVIEW/E user.

■ You must have CA-SYSVIEW/E installed on your system.

■ Your TSO session must have access to the CA-SYSVIEW/E ISPFprogram and its associated files.

For more information about the CA-SYSVIEW/E interface, see theCA-SYSVIEW/E installation manual. For more information about@JOBTRAC, see the REXX information in the CA-Jobtrac ExtendedScheduling Services Guide.

CA-View

See the CA-View interface information in “About the CA-ViewInterface” on page 5-69 for more information about CA-View.

CA-11

When rerun/restart is required and CA-11 is installed, you mayaccess rerun/restart information by using the R line command. Thistakes you to the CA-11 primary menu, and you navigate through therange of CA-11 functions.



System Considerations

You should consider the following system options before installingCA-Jobtrac. Contact your systems programming staff for help.

■ CA-Jobtrac must execute from an APF-authorized library.

■ SMF exits IEFUJV, IEFUJI, IEFUSI, IEFACTRT, and IEFU83must be active. They can be active through an IEFBR14 program.See the customizing SYS1.PARMLIB member SMFPRMxxinformation in Chapter 5, “Customization Tasks.”

■ SMF record types 15, 26, 30, and 64 must be recorded. You cansuppress the actual writing of these records to your SMF data setby coding an IEFU83, IEFU84, or IEFU85 exit. The CA-JobtracSAMPJCL library contains a sample IEFU83 exit, namedSAMPU83. This sample can also be linked with aliases of IEFU84and IEFU85. For more information about use of SMF records byCA-Jobtrac, see Chapter 5, “Customization Tasks.” For linkageediting requirements for the IEFU8x exits, see the appropriate IBMmanuals.

■ Exit IEAVMXIT must be activated for AMR (Automatic MessageRecognition) triggers. For information about setting up the exit, seeChapter 5, “Customization Tasks.”

■ The CA-Jobtrac-started task requires both SUBMIT and UPDATEauthority under your security system (CA-Top Secret, CA-ACF2,RACF, and so on).

■ All TSO users require authority to update the CA-Jobtraccheckpoint and history data sets. For information about updatingyour TSO procedures, see Chapter 5, “Customization Tasks.”

■ DD statements can be added to your TSO logon procedures orCLISTs to use the ISPF/PDF features of CA-Jobtrac. Forinformation about updating your TSO procedures, see Chapter 5,“Customization Tasks” and “Defining Location Information(DYNAMLOC) and Initiation IMODs” on page 5-12.

Security Considerations

When installing and using CA-Jobtrac, you must consider:

■ Security needed to install and run the CA-Jobtrac product

■ Security for using the CA-Jobtrac features



Authorization Needed for InstallationIf your installation uses a security system, your security administratormight need to authorize you to perform the following tasks:

■ Allocating the installation libraries.

■ Allocating and updating the SMP/E libraries.

■ Allocating the CA-Jobtrac execution libraries (target libraries).

■ Allocating the CA-Jobtrac distribution data sets.

■ Adding the CA-Jobtrac cataloged procedures to a system procedurelibrary.

■ Updating the chosen APF linklist libraries in SYS1.PARMLIBwhen you are ready for execution.

■ Enabling all TSO users, all system initiators, and JES to update theCA-Jobtrac checkpoint data set.

■ Enabling all TSO users to update the CA-Jobtrac history file.

■ Entering the CA-Jobtrac started task name in the appropriateauthorized task tables.

■ Giving SUBMIT authority to the CA-Jobtrac started task. Youshould give the CA-Jobtrac task the same security attributes asproduction TSO user IDs.

■ Enabling or disabling TSO users to update JCL, SCL, TEMPJCL,and DOC libraries.

Authority Requirements to Run CA-JobtracIf you are using a security system (such as CA-Top Secret,CA-ACF2, or RACF), give the CA-Jobtrac started task SUBMITauthority.

Usage Security for CA-JobtracCA-Jobtrac uses the following methods to secure its use:

■ TRACAUTH table

■ TRACX26 user exit

You use only one of the methods for security. Regardless of themethod you use, the TRACAUTH table is still used to:

■ Specify a name for a location

■ Specify which users are notified of abends and error conditions



About the TRACAUTH TableThe TRACAUTH table contains entries that:

■ Define whether a user can perform specific CA-Jobtrac functions

■ Assign names to locations

The TRACAUTH table is created using the @AUTH macro. Duringinstallation, you run the job ASMAUTH to create a default entry inthe TRACAUTH table. The default entry is used for all TSO usersnot specifically defined in other entries.

See Chapter 5, “Customization Tasks” for information about definingentries in the TRACAUTH table, and about the ASMAUTH job.

About the TRACX26 Security ExitThe TRACX26 user exit is called by the CA-Jobtrac ISPF dialog andby @JOBTRAC to verify a user's authority to view, update, add,delete, or purge CA-Jobtrac information. You can control access tothe following areas using the TRACX26 exit:

■ Events

■ Holiday and cyclic calendars

■ Global options

■ Online table services

■ CA-Jobtrac captured sysout

Note: Take care using this exit. This is a client alteration of theproduct and may cause unpredictable results if not properlycoded and tested. The provided sample is only a sample.

Choosing a MethodThe available security methods essentially secure the sameinformation. A few exceptions are described below. Which methodyou choose depends on the importance of these exceptions to you.



Information Secured Discussion

Specific schedule informationfor an event

With TRACAUTH you canallow or prevent users fromchanging the following for anevent:

Date and time information(JAUTH=T)

Dependency codes (DAUTH)

The TRACX26 user exit doesnot offer this level of security.

Verification of the existenceof JCL

The OPTA=J parameter ofTRACAUTH requires thatJCL for an event being addedto the schedule using theADD or RUN commandresides in the user's defaultlocation TRACJnnn JCLlibrary.

The TRACX26 user exit doesnot offer this security.

JREPORT3 and CA-ACF2When running JREPORT3 and using ACF2 for your security packageit is possible that an S806 abend may occur for the programICEMESA. This would only occur for dynamically added sort workdata sets that are secured by ACF2. The simple way around this isthe following additions to your JREPORT3 JCL:

//$ORTPARM DD �

DYNALLOC=(SORTWK,3)

BMSG

STATREC=SYNCSTAT

This allows the sort work data sets to be allocated and the correctprogram to be called for the sort routine.

Some other messages that you may see running the JREPORT3report:

ACF999�� ACF2 LOGGING-�4,��,xxxxx,xxxxxx,SY

IFA1�4I REGISTRATION HAS BEEN DENIED FOR

PRODUCT WITH OWNER=IBM CORP NAME=OS/39�


Chapter 3. Installation Tasks

New SMP/E CSIs are created during the installation. You mustinstall into new CSIs even if you have a previous version ofCA-Jobtrac installed. Changes in DLIB allocation prevent using theprevious version's CSIs.

This chapter explains how to install CA-Jobtrac using the IBMSMP/E product. If you are not familiar with SMP/E, you should havean experienced SMP/E consultant available. Computer AssociatesTechnical Support also answers questions about SMP/E installationoptions (see the CA-Jobtrac Reports, Maintenance, and RecoveryGuide for information about contacting Computer AssociatesTechnical Support).

Getting Help During InstallationKeep a copy of your installation listings during the installationprocess.

If you need assistance during CA-Jobtrac installation, call ComputerAssociates Technical Support (see the CA-Jobtrac Reports,Maintenance, and Recovery Guide for information about contactingComputer Associates Technical Support). Have your listingsavailable when you call.

Chapter 3. Installation Tasks 3-1

Steps to Take

Steps to TakeThe following steps are required to install CA-Jobtrac.

You can use this list as a quick reference to the steps involved inSMP/E installation. You can remove the checklist from the guideand use it to record the completion of each installation step.

___ “Step 1: Unload the SAMPJCL Library.”

___ “Step 2: Unload CA-Jobtrac Documentation.”

___ “Step 3: Create SMP/E Libraries.”

___ “Step 4: Create the Target and Distribution Libraries.”

___ “Step 5: Create SMP PROC.”

___ “Step 6: Perform RECEIVE Processing for CA-Jobtrac.”

___ “Step 7: Perform APPLY Processing.”

___ “Step 8: Perform ACCEPT Processing.”

___ “Step 9: Link IEFTB724 to GJTRTRT2 (Conditional).”

___ “Step 10: Link CA-Panvalet Modules (Optional).”

___ “Step 11: Link CA-Librarian Modules (Optional).”

___ “Step 12: Updating License Management Program (LMP)Key.”

___ “Step 13: Merge the CA-Jobtrac API Table (Optional).”

___ “Step 14: Create a Dummy IEAVMXIT Exit (Optional).”

___ “Step 15: Installing the @JOBTRAC USS Command(Optional).”


Steps to Take

Step 1: Unload the SAMPJCL Library

The SAMPJCL library includes CA-Jobtrac JCL and help membersused during installation. Members in the SAMPJCL library containdetailed instructions, notes, and JCL examples.

The SAMPJCL library must be loaded to your system from theproduct tape shipped with CA-Jobtrac.

ProcedureFollow the steps below to allocate and load the SAMPJCL library:

1. Create JCL for a job to load the SAMPJCL library from theCA-Jobtrac base tape. Use the JCL shown in the figure below asan example. Where shown, specify the DSN=, UNIT=, andVOL=SER= to where the SAMPJCL library is to be loaded.

2. Run the job created in Step 1 to allocate and load the SAMPJCLlibrary.

3. Verify that the job receives a return code of 0 (zero).

Sample Load JCL for SAMPJCL

//jobname JOB (acct#),'JOBTRAC',CLASS=A,MSGCLASS=X

//�

//STEP�1 EXEC PGM=IEBCOPY,REGION=2�48K

//�

//SYSPRINT DD SYSOUT=�

//�

//SYSUT3 DD UNIT=xxx,DISP=(,PASS),SPACE=(CYL,(1�,1�))

//�

//IN1 DD DSN=CAI.SAMPJCL,DISP=(OLD,KEEP,KEEP),UNIT=unitname,

// VOL=SER=xxxxxx,LABEL=(9,SL,,EXPDT=98��)

//�

//OUT1 DD DISP=(NEW,CATLG,DELETE),DSN=CAI.JT.SAMPJCL, <== YOUR DSN

// UNIT=unitname,VOL=SER=volser, <== YOUR VOLSER

// DCB=(LRECL=8�,BLKSIZE=6�8�,RECFM=FB),

// SPACE=(TRK,(29,1�,2�),RLSE)

//�

//SYSIN DD �

COPY I=IN1,O=OUT1

/�


Steps to Take

Step 2: Unload CA-Jobtrac Documentation

CA-Jobtrac documentation is delivered three ways. A CD containingCA-Jobtrac documentation accompanies the installation tape withboth Adobe Acrobat and IBM BookManager formats. The SAMPJCLlibrary includes two members to unload the documentation from theinstallation tape either in Adobe Acrobat format or in IBMBookManager format. To unload the documentation from theinstallation tape, refer to SAMPJCL members ADOBEDOC orBKMGRDOC.

Step 3: Create SMP/E Libraries

This step accomplishes the following:

■ Creates all the SMP/E libraries

■ Defines the SMP zones

Member UsedThe JCL for this step is in member CAINITE5 in your CA-JobtracSAMPJCL library.

ProcedureTake the following steps:

1. Review the JCL in the CAINITE5 procedure.

2. Modify the JCL parameters to meet your installation's needs.

3. Run the CAINITE5 job to create the SMP/E libraries. Youshould receive a completion code of 04.

New SMP/E CSIs are created during the installation. You MUSTinstall into new CSIs even if you have a previous version ofCA-Jobtrac installed. Changes in the SMP/E packaging structureprevent using the previous version's CSIs.


Steps to Take

Step 4: Create the Target and Distribution Libraries

This step accomplishes the following:

■ Creates all the SMP/E target libraries for CA-Jobtrac

■ Creates all the SMP/E distribution libraries for CA-Jobtrac

Member UsedThe JCL for this step is in member HD35ALC in your CA-JobtracSAMPJCL library.


1. Review the JCL in the HD35ALC procedure.


3. Run the HD35ALC job to create the SMP/E target anddistribution libraries. You should receive a completion code of 0(zero).

Step 5: Create SMP PROC

This step sets up the SMP/E PROC that will be used for all SMP/Eprocessing.

Member UsedThe JCL for this step is in member CAIHD35 in your CA-JobtracSAMPJCL library.


1. Edit CAIHD35 in SAMPJCL.

2. Modify the PROC parms to specify required parameters. Do notchange the PTF='DUMMY,' parameter.

3. Verify the macro libraries specified on the SYSLIB DDNAME.

4. Verify the library specified on the AOSB3 ddname. ModuleIEFTB724 will be linked with CA-Jobtrac module GJTRTRT2during the install. If you do not specify the AOSB4 ddname, themodules will have to be linked together outside SMP/E, asspecified in “Step 9: Link IEFTB724 to GJTRTRT2(Conditional)” on page 3-8.

5. Save the changes and move the CAIHD35 PROC into anavailable proclib.


Steps to Take

Step 6: Perform RECEIVE Processing for CA-Jobtrac

This step performs RECEIVE processing for the CA-Jobtrac baseFMID and all its functions.

Member UsedThe JCL for this step is in member HD35REC in your CA-JobtracSAMPJCL library.


1. Review the JCL in the HD35REC procedure.


3. Run the HD35REC job to perform RECEIVE processing forCA-Jobtrac. You should receive a completion code of 0 (zero).


Steps to Take

Step 7: Perform APPLY Processing

This step performs APPLY processing for CA-Jobtrac.

Member UsedThe JCL for this step is in member HD35APP in your CA-JobtracSAMPJCL library.


1. Review the JCL in the HD35APP procedure.


3. Run the HD35APP job to perform APPLY processing. Ensureyou receive a completion code of 0 (zero) or 4.

Step 8: Perform ACCEPT Processing

This step performs ACCEPT processing for CA-Jobtrac.

Member UsedThe JCL for this step is in member HD35ACC in your CA-JobtracSAMPJCL library.


1. Review the JCL in the HD35ACC procedure.


3. Run the HD35ACC job to perform ACCEPT processing. Youshould receive a completion code of 0 (zero) or 4.


Steps to Take

Step 11: Link CA-Librarian Modules (Optional)

This step relinks the CA-Jobtrac modules so that they include theCA-Librarian access method modules.

If you are not using CA-Jobtrac to submit JCL from CA-Librarian,skip this step.

Member UsedThe JCL for this step is in member HD35LLIB in your CA-JobtracSAMPJCL library.


1. Review the JCL in the HD35LLIB procedure.


3. Run the HD35LLIB job to link the CA-Librarian modules. Youshould receive a completion code of 0 (zero).

Step 12: Updating License Management Program (LMP)Key

This version of CA-Jobtrac is in compliance with ComputerAssociates License Management Program (LMP). As a result, thePDS member referenced by the KEYS DD statement in the CAS9procedure must be updated with the information supplied on the LMPKey Certificate. The LMP Key Certificate is included as part of yourdistribution package.

For instructions on installing and tailoring the CA-Jobtrac LMPExecution Key, see the Unicenter TNG Framework for OS/390Administrator Guide, in the "CAIRIM Operations" chapter, underUsing CA LMP.


Steps to Take

Step 13: Merge the CA-Jobtrac API Table (Optional)

The CA-Jobtrac API (Application Programming Interface) is used forcommunication with CA-Jobtrac WorkStation. This step is onlyrequired if this interface will be used.

The Sample JCL library distributed with Unicenter TNG Frameworkfor OS/390 contains member WC20MRG, which is model JCL tomerge individual product control tables into the common API tables.The CA-Jobtrac API table that must be merged is CAHDAPPL. Thismust be merged with the common API table CA4FAPPL.

Edit WC20MRG or make a copy of it in the CA-Jobtrac SAMPJCLlibrary. Customize the JOB statement and in-stream JCL procedurevariables, if necessary. See the Unicenter TNG Framework forOS/390 documentation for installing Viewpoint tables. Set up anEXEC statement at the bottom of the JCL for CAHDAPPL. Becausethis table will establish an interface with the CA-Jobtrac addressspace, you should use the CA-Jobtrac product code (HD) for thePROD= value.

If you are installing CA-Jobtrac into a separate set of SMP targetlibraries, you need to add the CA-Jobtrac load library (CAILIB) tothe STEPLIB concatenation for the MERGE PROC step. TheCA-Jobtrac library should be added AFTER the Unicenter TNGFramework for OS/390 CAILIB.

The following should be the only EXEC statement at the bottom ofthe member. (Comment or delete any others.)

//HDAPPL EXEC WC2�MRG,TABLE=APPL,PROD=HD

Submit the job and CAREFULLY review the output to verify that themerge process ran successfully. If any of the steps completed with areturn code greater than zero, correct the problem and resubmit.

Caution

The table merge output should be directed to the Unicenter TNGFramework for OS/390 CAILIB so that all product installationsshare the same common control tables. You need to have CA-CRuntime installed.


Steps to Take

Step 14: Create a Dummy IEAVMXIT Exit (Optional)

Use job LINKMXIT in the SAMPJCL library to create a dummyexit. You can find more information in “Setting Up AMR Support”on page 5-46.

Step 15: Installing the @JOBTRAC USS Command(Optional)

The CA-Jobtrac module, JTUSS, can be used to access CA-Jobtracfrom IBM's Unix System Services using the @JOBTRAC commandscurrently used with CA-GSS and GJTRABTR. To implement thisfeature the module must be linked with the IBM LanguageEnvironment for OS390 (LE390) and stored in a UNIX HFS systemfile. The object for the module is distributed in CAIMAC. TheSAMPJCL member HD35LUSS contains JCL to perform the link.Customize the JCL for your environment and submit it to install thecommand. Remembering that Unix is case-sensitive, be sure tospecify the path for the command in the correct case. TheHD35LUSS member contains instruction for customizing the JCL.

The CA-Jobtrac Extended Scheduling Services Guide containsinformation on using the command, in the "Accessing CA-Jobtracfrom Unix System Services (USS)" chapter.



Chapter 4. Customization Job Streams

The following phases are necessary to customize, set up, andimplement CA-Jobtrac:

■ STAGE1 customization job stream - Covered in this chapter

■ STAGE2 installation job stream - Covered in this chapter

■ Customization tasks - Covered in Chapter 5

■ Startup and verification tasks - Covered in Chapter 6

STAGE1 Customization Job StreamThe STAGE1 customization job stream invokes an installation macrocalled TRACMAC, which generates the STAGE2 installation jobstream. The TRACMAC macro contains statements you use to namelibraries and their locations, and to provide information for theSTAGE2 job stream.

See “STAGE1 Customization Job” for more information.

STAGE2 Installation Job StreamThe STAGE2 job stream is necessary to install CA-Jobtrac.

The STAGE2 job stream allocates CA-Jobtrac data sets, updates yoursystem-cataloged procedure library, and provides the installationverification procedure for CA-Jobtrac.

See “STAGE2 Installation Job Stream” for more information.

The ProcessThe STAGE1 customization job stream invokes an installation macrocalled TRACMAC, which generates the STAGE2 job stream. TheSTAGE2 job stream is necessary to install CA-Jobtrac.

The member STAGE1 in your SAMPJCL library is a sample of theassembler JCL needed to create the STAGE2 job stream.

The STAGE1 job writes the STAGE2 job stream to the data set orPDS member that you specify (default is the SAMPJCL). TheSTAGE2 job stream contains procedure updates, an installationverification procedure, and JCL to allocate remaining CA-Jobtraclibraries.

Chapter 4. Customization Job Streams 4-1

STAGE1 Customization Job

STAGE1 Customization JobThe STAGE1 customization job stream invokes an installation macrocalled TRACMAC. TRACMAC defines numerous global values usedto install CA-Jobtrac and generate the STAGE2 job stream.

Running the STAGE1 Job

ProcedureFollow the steps below to run the STAGE1 job stream:

1. Edit member STAGE1 in the SAMPJCL library.

2. Review the JCL carefully, making revisions to reflect yourinstallation's requirements.

3. Edit the STAGE1 parameter values to meet your installationrequirements (see “Required TRACMAC Parameters,” and“Optional TRACMAC Parameters” on page 4-5).

4. Be sure to specify your CAIMAC macro library in the SYSLIBDD statement.

5. Run the STAGE1 job to create the STAGE2 job stream.

6. Verify that the assembler return code from the STAGE1 job is 0(zero). If the return code is not 0, review the assembler output formessages that indicate what caused the error.

A possible cause is bad or missing parameters. Another commoncause is changing a parameter and omitting the comma. Allparameters except the last one should be followed by a comma.

Required TRACMAC ParametersThe following table describes the TRACMAC parameters that youmust include:

Parameter/Default Description

ARCHVOL= The volser of the volume on which the sysout capture fileis to reside. This volume must contain enough contiguousspace to satisfy the ASIZE= parameter.

ASIZE=100 The size in cylinders of the sysout capture file. Thisvalue must be at least 5.




CKPTNAM= The mid- and low-level qualifiers of the name you want toassign to the CA-Jobtrac checkpoint data set. Thehigh-level qualifier (see the INDXJ= parameter) isautomatically added to the name.

FORECAST= The mid- and low-level qualifiers of the name you want toassign to the forecast checkpoint data set. The high-levelqualifier (see the INDXJ= parameter) is automaticallyadded to the name.

FOREVOL= The volser of the volume on which the forecastcheckpoint is to reside.

HISTVOL=CAI The volser of the volume on which the history file is toreside.

INDX=CAI CA-Jobtrac installation library high- and mid-levelqualifier to be used during allocation.

INDXJ=CAI High-level qualifier for the CA-Jobtrac checkpoint andforecast data sets. These are JFST data sets.

INDXV=CAI High-level qualifier for the CA-Jobtrac history file.

INSTVOL= The volser of the volume on which the STAGE2 job is toplace all CA-Jobtrac installation libraries. Approximately10 cylinders are required.

ISET= The fully-qualified data set name of the IMOD ISET intowhich CA-Jobtrac sample and required production IMODswill be installed. See the Unicenter TNG Framework forOS/390 documentation for information about IMODs andISETs.

JOBHIST= The mid- and low-level qualifiers of the name you want toassign to the history file. The high-level qualifier (see theINDXV= parameter) is added.

NAME='CA-JOBTRACINSTALL'

STAGE2 job stream programmer name field.

NEWSITE=Y New installations should specify Y. Reinstallations willnot reallocate runtime libraries if N is used.

SYSID= The SMF ID of your primary CA-Jobtrac system. Theprimary system is the system on which all batch work willbe submitted.

TRACJCL= The name of the library that is to contain the productionJCL.




TRACTEMP= The name of the library that is to contain thetemporary-use JCL.

TRACVOL= The volser on which the CA-Jobtrac checkpoint data set isto reside.

UNITA=SYSALLDA Unit specification for the sysout capture file. See theARCHVOL parameter for related information.

UNITD=SYSALLDA Unit specification for all remaining installation librariesand data sets. See the INSTVOL parameter for relatedinformation.

UNITT=SYSALLDA Unit specification for the CA-Jobtrac checkpoint data set.See the TRACVOL parameter for related information.



Optional TRACMAC ParametersThe parameters described below are not required. Some have defaultvalues that allow the successful generation of STAGE2 JCL. Defaultvalues are underlined. You will probably need to specify nondefaultparameter values to conform to your installation standards.


ACCT=1 Job accounting parameter. This parametercan contain parentheses and commas.

AUNIT=SYSALLDA Unit name for batch/STC dynamicallocation. This should be the same as theunit name in the WORK DD statement inthe JOBTRAC3 procedure and should beaccessible to all users.

BLK=6080 The block size (BLKSIZE) assigned to alllibraries with a logical record length of 80(LRECL=80) allocated in the CA-Jobtracinstallation process.

CLASS=A STAGE2 job stream execution class.

GROUP=group JCL GROUP keyword, if required.

GSSLOAD= The fully-qualified load library name intowhich the CA-GSS associated with thisCA-Jobtrac was installed. See theUnicenter TNG Framework for OS/390Getting Started for information aboutCA-GSS load libraries. If this parameter isomitted, it is assumed the CA-GSS loadmodules are in the system linklist.

INDX11= CA-11 high-level index used on the CA-11CAIISPM, CAIISPP, and CAILIB. If youhave CA-11 installed, specify thisparameter.

INSTLIB=indx.JT.SAMPJCL Your preallocated CA-Jobtrac installationlibrary. Specify the full name of thislibrary. indx defaults to the value ofINDX.

JESCMD=$ Your JES command character. Thisparameter informs CA-Jobtrac of thecorrect character to use when issuing JEScommands.




JFSTCNT=4 Number of cylinders required for thecheckpoint data set. The maximum size is64 cylinders. This space must becontiguous.

MSGCLASS=A STAGE2 job stream message class.

NEWISET=N|Y N specifies that a new ISET data set namedin the ISET= keyword exists.

Y specifies that a new ISET data set shouldbe allocated. The new ISET data set nameis specified in the ISET= keyword.

NOTIFY=userid TSO user ID for STAGE2 JOB statementNOTIFY parameter.

PROCLIB=indx.JT.CAIPROC PROCLIB library. Used for all CA-Jobtraconline and batch execution procedures.indx defaults to the value of INDX.

PRTY= STAGE2 job stream priority keyword.

RD= JCL record RD statement.

REGION=2048KB STAGE2 job stream region parameter.

SYSOUT=* STAGE2 utility listings output class.

TYPRUN= TYPRUN parameter to be used inSTAGE2.


STAGE2 Installation Job Stream

STAGE2 Installation Job StreamThe STAGE2 job stream is necessary to install CA-Jobtrac. It iscreated by the STAGE1 job, and accomplishes the following:

■ Allocates CA-Jobtrac libraries

■ Formats your sysout capture file

■ Formats your JFST checkpoint and forecast data sets

■ Allocates your history files

■ Updates your system-cataloged procedure library with CA-Jobtracprocedures

■ Copies and compiles CA-Jobtrac product IMODs (requiresCA-GSS CAILIB)

■ Updates your SAMPJCL data set with CA-Jobtrac CLISTs

■ Sets up your default global operating parameters and environment

■ Provides the installation verification procedure for CA-Jobtrac

STAGE2 PreparationThe following preparation might be necessary for your installation.Review all the preparation information to continue with the STAGE2portion of your installation.

Information to Review See

Ensuring APFauthorization

“Ensuring APF Authorization” onpage 4-8

Type of data setssupported

“Types of Data Sets Supported” onpage 4-9

Allocating data sets “Allocating Data Sets” on page 4-9

About the checkpointdata set

“Description of the Checkpoint DataSet” on page 4-12

About the sysout capturefile

“About the Sysout Capture File” onpage 4-14

Updating the procedurelibraries

“Updating Procedure Libraries” onpage 4-18

Setting global optionsusing JOBTRAnn

“Using JOBTRAnn to Set GlobalOptions” on page 4-19



Running the STAGE2 Job

ProcedureFollow the steps below to run the STAGE2 jobs:

1. Edit member STAGE2. The SYSPUNCH statement in theSTAGE1 job stream named the location of the STAGE2 jobstream.

2. Review the JCL carefully, making revisions to reflect yourinstallation's requirements. You can separate the job steps intoindividual jobs if you want.

3. Review all the STAGE2 preparation information in the remainderof this chapter. Make modifications to the STAGE2 job streambased on the information.

In a shared spool complex, make sure that the CA-Jobtracexecution libraries are accessible from all systems.

4. Run the STAGE2 job stream.

5. Verify that each step of every job receives a return code of 0(zero). All the system logic necessary to run CA-Jobtrac is inplace.

Note: The STAGE2 JCL member contains three jobs.

Ensuring APF Authorization

Caution

CA-Jobtrac modules must be executed from an APF-authorizedlibrary.

ProcedureAdd the CAI CAILIB to the APFLIST or use IEBCOPY to move theCA-Jobtrac modules from the installation CAILIB to an appropriatelibrary and perform an LLA REFRESH if needed.

Note: CA-GSS CAILIB must be APF-authorized for the STAGE2jobs to run.



Types of Data Sets Supported

CA-Jobtrac supports for the DD of TRACJnnn CA-Panvalet datasets, CA-Librarian data sets, and standard IBM partitioned data sets(PDSs or PDSE) for JCL submission and editing. You must use theTEMP temporary-use JCL command to edit JCL from CA-Panvaletor CA-Librarian. You cannot use the JCL command to edit JCL fromCA-Panvalet or CA-Librarian.

RestrictionsYou can choose a PAN access method, a LIBR access method, or astandard PDS access method. All JCL libraries on the same ddname,however, must use the same access method.

The temporary-use JCL library for each location must be a PDS orPDSE.

Allocating Data Sets

Data Sets Already AllocatedThe following table describes the data sets allocated earlier in theinstallation process:

DDname Data Set Name Description

SAMPJCL your.JT.SAMPJCL JCL samples, table services, SMP/Eexamples, exit samples, IVP job, andother information helpful duringinstallation.

TRACPARM your.JT.PPOPTION CA-Jobtrac setup library containing globaloptions, resource definitions, andexclusion definitions.



Data Sets Allocated by the STAGE2 Job StreamThe following table describes the installation and execution data setsallocated by the STAGE2 job stream:


TRACJ000 your.PRODJCL JCL library. This data set can be aCA-Panvalet data set, a CA-Librarian dataset, or a standard PDS or PDSE.

TRACT000 your.TEMP Temporary-use JCL library. This data setmust be a standard PDS or PDSE.

TRACS000 your.SCL CA-Jobtrac SCL library. This library willcontain schedule members coded usingSCL (Schedule Control Language). Thisdata set must be a standard PDS or PDSE.

TRACR000 your.RMTPSWD Remote (Cross-Platform) credentials file.Encrypted user ID, domains, andpasswords for submitting work on remotesystems (Unicenter TNG or CA-JobtracAgent).

JOBTRACx your.JOBTRACx CA-Jobtrac checkpoint data set.JOBTRACx is a JFST data set. xspecifies the CA-Jobtrac token. The dataset is the key control point in theCA-Jobtrac system. The checkpoint is asmall data set.

JOBHISTx your.JOBHISTx History file. This data set must be aVSAM data set. x specifies theCA-Jobtrac token.

DATELIB your.DATELIB CA-Jobtrac setup library containingmembers for Automatic Date Insertion(ADI) and JCL Modification Facility(JMF). See the text following the tablefor more information.

CAPTURE your.CAPTURE Sysout capture file. This data set is aformatted sequential (indexed) file thatholds the compressed sysouts forCA-Jobtrac events. An initial format of atleast 15 cylinders is required to hold SCLoutput.




TRACMDS your.TRACMDS PDS for holding CMDSET (command set)members. See the CA-Jobtrac ExtendedScheduling Services Guide for informationabout using command sets. This data setmust be a standard PDS or PDSE type.

FORECAST your.FORECAST Alternate JFST data set used for scheduleforecasting. This data set lets you load aschedule and produce forecast reportswithout affecting your productionschedules.

TRACD000 your.DOCLIB PDS library for storing eventdocumentation and manual actioninformation. This data set must be astandard PDS or PDSE type.

ADI uses member PRODDATE in the DATELIB data set forlocation 001. For other locations, specify the following DDs in yourPROCs or CLISTs:

//DATELIB DD DSN=cai.DATELIB(PRODDATE),DISP=SHR /� default �� location �/

//DATEL��1 DD DSN=cai.DATELIB(PRODD��1),DISP=SHR /� ��1 location �/

//DATEL��2 DD DSN=cai.DATELIB(PRODD��2),DISP=SHR /� ��2 location �/

JMF uses member JMFSYM01 in the DATELIB data set. For otherlocations, use the JLOCnnn: PARM in your JMFSYM01 member.For example:

JLOC��1:CAI.DATELIB(JMFSYM�2) /� ��2 location �/

See SAMPJCL members JMFSYM01 and PRODDATE used later inthe IVP.



Description of the Checkpoint Data Set

The data set is the key control point in the CA-Jobtrac system. Thecheckpoint is a small data set that is a relational JFST database thatcontains all current schedule data. It is updated and maintained bynumerous components, including dynamic schedule processors, whichcan add a thousand events at a time, and hundreds of local andremote TSO users who perform on-demand and exception processing.For information about JFST, see the "JFST Access Method" chapterof the CA-Jobtrac Reports, Maintenance, and Recovery Guide.

The CA-Jobtrac checkpoint data set becomes quite active duringheavy batch workloads.

In shops with an excess of 500 scheduled events per shift, thecheckpoint can accumulate DASD EXCPs at an accelerated rate. Inthat case, you should use the highest performance device possible foryour CA-Jobtrac checkpoint data set. See “Data Set PlacementConsiderations” on page 2-18.

JOBTRACx your.JOBTRACx checkpoint

Differentiating CA-JobtracsThe x in the ddname is the token that is used to identify thisCA-Jobtrac system. Each CA-Jobtrac running on a CPU must have aunique token specified. The same token must be used for thecheckpoint and the two history ddnames. We recommend that thetoken match the taskname with which CA-Jobtrac is started. It can beA-U, W-Z, or 0-9.

LocationAny non-SMS controlled DASD Reserves are not issued against thisdata set. However, it should not be placed on any pack withsuspended channel programs (such as page/swap data sets) or anypack that will draw significant reserve activity (such as catalog packsor JES checkpoint packs). If you plan to run CA-Jobtrac on multiplesystems that share DASD, the checkpoint data set must be on ashared pack. The checkpoint uses a proprietary format called JFST.(See the "JFST Access Method" chapter of the CA-Jobtrac Reports,Maintenance, and Recovery Guide for information about JFST.) Youshould place the checkpoint on a non-SMS managed volume. Thecheckpoint performs best on non-CACHE devices unless you areusing DASD Fast Write.



Description of the History File Data Set

This data set is the audit backup file for CA-Jobtrac. It tracks thehistory of completed events. Although updated less frequently thanthe checkpoint, it is updated under reserves. Some CA-Jobtraccomponents keep table information in the history file, and it isaccessed online, so you should ensure reasonable I/O response timesfor this file. It should not be placed on the same pack as thecheckpoint, or on a pack with heavy I/O activity. If you plan to runCA-Jobtrac on multiple systems that share DASD, the history filemust be on a shared pack. The data set can be SMS or non-SMS andwould perform well on a CACHE device with DASD Fast Write(DFW). The JOBHIST file cannot span volumes.

JOBHISTx your.JOBHISTx History file

This data set must be a VSAM data set. x specifies the CA-Jobtractoken.


LocationAny SMS or non-SMS controlled DASD.

Description of the History File Sequential Data Set

The history data file is the data component of the history file.CA-Jobtrac uses this data set to improve the efficiency of scanningthe history file. The history data file stores the data referenced by thehistory file.

Note: No VSAM performance software should be used for this dataset.

SEQHISTx your.SEQHISTx History file sequential data set.



This data set must be a VSAM data set. x specifies the CA-Jobtractoken.

SEQHISTx (SEQHISTY is the default.)


About the Sysout Capture File

The sysout capture file can be the largest CA-Jobtrac data set, butbecause of the CA-Jobtrac compaction routines and the EXCP accessmethod, it uses its space the most efficiently. You can expect afour-to-one ratio of compression over the JES spool.

The size of the sysout capture file depends on how many jobs areprocessed, how many sysouts are captured, how many days are keptin the online capture, and the average line count of each listing. Forexample, 100 cylinders can comfortably handle up to 1.5 millionlines of sysouts. You can use this figure in determining how manycylinders you actually need for your sysout archival requirements.

For a more detailed discussion, see the "The Sysout Capture File" inthe CA-Jobtrac Reports, Maintenance, and Recovery Guide.

CAPTURE your.CAPTURE Sysout capture file. (CAPTURE is thedefault)

This data set is a formatted sequential (indexed) file.

Messages Associated With Sysout CaptureError routines automatically prompt the operator and temporarily stopoperation if the capture file becomes full during normal operation.The operator can optionally suspend capture or close the file to tapeand archive aged sysouts. The message identifier and an explanationare found in the CA-Jobtrac Operator Guide, along with appropriatereplies.



Differentiating CA-JobtracsThe data set may be shared across systems but not within a singlesystem.

LocationAny non-SMS controlled DASD.

The sysout capture file stores captured sysouts for online viewing andsubsequent archival, printing, or deletion. If you plan to use thesysout capture file as your primary sysout capture system, you shouldplace it where your TSO users will get adequate response time. Ifyou plan to run CA-Jobtrac on multiple systems that share DASD,the sysout capture file must be on a pack on your primary(event-submitting) CA-Jobtrac system.

Most users will put it on shared DASD so that TSO users from eachsystem can view sysouts. No reserves are issued against the sysoutcapture file. You should place the sysout capture file on a non-SMSmanaged volume.

Also see “Using Other Sysout Capture Products” on page 5-69 formore information.

Description of TRACMDS

TRACMDS your.TRACMDS PDS for holding CMDSET (CommandSet) members. See the CA-Jobtrac Extended Scheduling ServicesGuide for information about using command sets. This data set mustbe standard PDS or PDSE.



Recommended Initial Data Set SizesThe data set sizes shown in the table below are recommended duringinitial testing and implementation. You can adjust the sizes of thedata sets after installation is complete.

DDname Recommended Size

JOBTRACx 15 cylinders (JFST data set) minimum

JOBHISTx 50 cylinders (VSAM KSDS)

DATELIB 2 cylinders

CAPTURE 100 cylinders (5 cylinders minimum)

TRACMDS 1 cylinder

FORECAST 2 cylinders (JFST data set)

Allocating Additional LibrariesThe CA-Jobtrac distributed processing capabilities allow multiplelibraries to support multiple locations. During initial testing andimplementation, the default libraries for location 000 are sufficient.

You can have as many as 255 additional locations and libraries. Inthe STAGE2 job stream, you can add definitions for the additionallibraries.



Library Naming ConventionsThe following table describes the naming conventions for each typeof library. In each case, nnn corresponds to the location ID for aspecific location.

Library Location 000Name

AdditionalLocations

JCL TRACJ000 TRACJnnn

Temporary-useJCL

TRACT000 TRACTnnn

SCL TRACS000 TRACSnnn

Eventdocumentation

TRACD000 TRACDnnn

Procedure to Allocate Additional LibrariesTake the following steps in the STAGE2 job stream to allocateadditional PDS-type libraries. If you use CA-Librarian orCA-Panvalet libraries, allocate the JCL libraries as recommended bythe product's documentation.

1. For each library you want to create, there is a commented outddname.

2. Change the library name in the copied definition. Each libraryshould have the same data set attributes as the location 000library.

3. For each library you allocate, add a DD statement in theJOBTRAC STC procedure and TSO CLIST or the DYNAMLOCmember. Accomplish this regardless of the type of library used.

See “Defining Location Information (DYNAMLOC) and InitiationIMODs” on page 5-12 for more information.



Updating Procedure Libraries

CA-Jobtrac requires a number of cataloged procedures. Theseprocedures are copied into your specified cataloged procedure libraryby the STAGE2 job.

RequirementVINIT3, JOBTRAC3, and DUMPV3 must be in a procedure libraryfor started tasks.

Description of the ProceduresThe following table describes the CA-Jobtrac procedures contained inthe CAIPROC library:

Procedure Description

JOBTRAC3 Scanner task (started task)

VINIT3 IPL initialization task

JREPORT3 CA-Jobtrac report utility

GJTRVSCH Batch job access to schedule updating

GJTRMAHI Batch job to delete records from theCA-Jobtrac history file

GJTRMAIV Batch schedule maintenance

GJTRMAJC Batch job to delete members fromtemporary-use JCL libraries

GJTRVRLD Sample cataloged procedure to execute thesysout capture reload utility

DUMPV3 Diagnostic snap dump

JCL#TCXR CA-JCLTrac Report Generator

JCL#TDBL IBM's DSNUTILB utility

JCL#TDB2 CA-JCLTrac DB2 Loader

JCL#TRAC CA-JCLTrac JCL Analyzer

ProcessSelect a cataloged procedure library for CA-Jobtrac (such asSYS1.PROCLIB). Include the CA-Jobtrac procedures in it or add theCAIPROC PROCLIB to the proclib list in JES.



Using JOBTRAnn to Set Global Options

CA-Jobtrac global options describe global values and theenvironment in which CA-Jobtrac operates.

CA-Jobtrac global options are set using the JOBTRAnn member andby using the CA-Jobtrac global options panels. Some options are setby the JOBTRAnn member only, some options are set using theglobal options panels only, and some options are set using either one.Additionally, some of the options set using JOBTRAnn are displayedon the global options panels, but you cannot set them on the panels.

For more information about the global options panels, see Chapter 5.

New Options in Version 3.5The following options are new in this version of CA-Jobtrac:AMRLCNT, ARM, CAPDMPS, CPM, DISABLE, DUMPUJV,JCLTABL, JMFTABL, RAMAXCC, TNDOVLP, SCHENV, andWLMRSRC.

Global Options in the STAGE2 Job StreamThe STAGE2 job stream creates a default JOBTRAnn member inyour SAMPJCL data set. Before customizing, copy the sample toyour PPOPTION data set. After running the STAGE2 job stream,you can change the values for the JOBTRAnn options or add optionsnot in the job stream.

Location of JOBTRAnnMember JOBTRAnn must reside in the PPOPTION library.

Using Multiple JOBTRAnn MembersBy copying the default JOBTRAnn member, you can create morethan one JOBTRAnn member. The nn in each member is unique.

You can use each of these members to test a different configurationof options, or if running multiple CA-Jobtracs.

Once CA-Jobtrac is started, you can activate some of the options in agiven JOBTRAnn member by issuing the following modifycommand. In the command, taskname is the name assigned to theCA-Jobtrac you want to affect, and nn matches nn in the desiredJOBTRAnn member:

F taskname,OPTS=nn



The JOBTRAnn Options

The following sections describe the options you can set in theJOBTRAnn member. Each option's syntax is also presented. Thedefault values (such as 24 for AMRLCNT) are used if the option isomitted. All options must start in column 1 of a JOBTRAnn member.

AMRLCNT

Specifies the number of identical message IDs received contiguouslybefore deciding that a loop is occurring and issuing messageTRAC029I. (AMRLCNT is an acronym for Automatic MessageRecognition Tuning Parameter.) The default is 24. The syntax is:

AMRLCNT

┌ ┐─24───��─ ──AMRLCNT= ──┴ ┴─nnnn─ ──────────────────────────�

To enable this option, recycle the CA-Jobtrac STC.

ARCBLK

Defines the archive tape block size in multiples of 150-byte records(LRECL=150). The syntax is:

ARCBLK

┌ ┐─327��───��─ ──ARCBLK= ──┴ ┴─blksize─ ────────────────────────�




ARCDSN

Defines the first 35 characters of the archive tape data set name.CA-Jobtrac appends the date and time to the job name asThhmm.Dyyddd for volume identification. The syntax is:

ARCDSN

��─ ──ARCDSN=arch.tape.dsname ─────────────────────�


ARCDSP

Defines the normal DSN disposition of the archive tape. See“ARCRTN.” The syntax is:

ARCDSP

┌ ┐─CATLG────��─ ──ARCDSP= ──┴ ┴─tapedisp─ ───────────────────────�


ARCRTN

Indicates the tape retention period in days to be used for the archivetape created by a 0ARCHIVE or 0SYSARCH task.

This value is also used to calculate the number of days to maintainan online copy of the sysout archive &INDEX entry. The &INDEXentry, available through the CA-Jobtrac/ISPF dialogs, lists all sysoutscaptured for the defined period, a brief run history, and the archivetape volume on which they reside. The syntax is:

ARCRTN

┌ ┐─3�────────��─ ──ARCRTN= ──┴ ┴─tapertnpd─ ──────────────────────�




ARCUNT

Defines the archive tape unit name (UNIT=unitname). See“ARCRTN” on page 4-21. The syntax is:

ARCUNT

┌ ┐─TAPE─────��─ ──ARCUNT= ──┴ ┴─tapeunit─ ───────────────────────�


ARM

Defines the type of IBM's Automatic Restart Management (ARM)processing you want. The syntax is:

ARM

┌ ┐─NO──────────────��─ ──ARM= ──┼ ┼─NONE──────────── ───────────────────�

└ ┘─abend code list─

where:

NOIndicates that ARM processing should not take place. This is thedefault.

NONEIndicates that ARM processing should proceed withoutexceptions.

abend code listIs a list of abend codes that should disallow normal ARMprocessing, such as:

8�6,2�2,X37

In this example, the following are excluded from ARMprocessing:

806 abend (module not found)

0202 abend (sysout writer subtask has abended)

D37, B37, etc. (various out-of-space conditions)

Note in the X37 entry, the X indicates a generic abend andincludes all abends that end with 37.



ARM Processing for CA-JobtracCA-Jobtrac offers an interface to IBM's Automatic RestartManagement feature (ARM). The ARM feature allows for automaticrestart in the event of a product failure, which results in termination.If you are currently using ARM, the CA-Jobtrac needs may well bemet with the default profile currently defined. For the purpose ofrestarting CA-Jobtrac with the same command that originally startedthe product, the following may be used as an example.

To define the couple data set:

DEFINEDS SYSPLEX(PLEX79)

DSN(COUPLE.ARM.XE79P) VOLSER(MVXE79)

CATALOG

DATA TYPE(ARM)

ITEM NAME(POLICY) NUMBER(5)

ITEM NAME(MAXELEM) NUMBER(25)

ITEM NAME(TOTELEM) NUMBER(2�)

DEFINEDS SYSPLEX(PLEX79)

DSN(COUPLE.ARM.XE79A) VOLSER(TSO79A)

CATALOG

DATA TYPE(ARM)

ITEM NAME(POLICY) NUMBER(6)

ITEM NAME(MAXELEM) NUMBER(35)

ITEM NAME(TOTELEM) NUMBER(3�)

To define the policy:

DATA TYPE(ARM) REPORT(YES)

DSN(COUPLE.ARM.XE79P)

DEFINE POLICY NAME(POLXE79A) REPLACE(YES)

ELEMENT(�)

A startup parameter (ARM=) may be used to customize the restartcriteria.


AUNIT

Indicates a unit name for batch/STC dynamic allocation. This shouldbe the same as the unit name in the WORK DD statement in theJOBTRAC3 procedure and should be accessible to all users. Thesyntax is:



AUNIT

┌ ┐─SYSDA────��─ ──AUNIT= ──┴ ┴─unitname─ ────────────────────────�


AUTOC

Defines the AUTO-SCHD recognition character to track jobs that aresubmitted outside of CA-Jobtrac control. To use simultaneousoperation of the AUTOC parameter on multiple CA-Jobtracs on thesame system, define different AUTO-SCHD characters for eachCA-Jobtrac on the system. The recognition character must be eitherin the JCL being submitted in column 71 or the $AUTO step. Todisplay what is being used now, from the CA-Jobtrac ISPF MainMenu enter SYS OPTS, then select number 1. For more information,see the CA-Jobtrac Operator Guide. The syntax is:

AUTOC

┌ ┐─>────────��─ ──AUTOC= ──┴ ┴─autochar─ ────────────────────────�

where:

autocharA through Z, 0 through 9, <, >, ?, $, @, #, and / are validcharacters.




AUTOQ

Defines up to eight AUTO-QUEUE job classes in accordance withJES2, for external tracking of jobs. Once a job is submitted in thisJES2 class, without the AUTOC character in column 71 or the$AUTO step, the job will be tracked and or controlled byCA-Jobtrac. Jobs that are on the checkpoint with a 'Q' or a 'J'dependency will be controlled by CA-Jobtrac. If no job is on thecheckpoint, the job will be added and tracked by CA-Jobtrac. Todisplay what is being used now, from the CA-Jobtrac ISPF MainMenu enter SYS OPTS, then select number 1. See the CA-JobtracOperator Guide for information about using AUTO-SCHD character.

Note: This parameter is only valid for JES2 users.

The syntax is:

AUTOQ

��─ ──AUTOQ=JES2classlist ─────────────────────────�

where:

JES2classlistA through Z and 0 through 9 are valid characters.


CAPDMPS

Specifies the option to capture system dumps to the Sysout CaptureFile. Y directs Sysout Capture to capture system dumps, while Nwill not. N is the default. Any value other than Y or N defaults toN. The syntax is:

CAPDMPS

┌ ┐─N─��─ ──CAPDMPS= ──┴ ┴─Y─ ─────────────────────────────�




CHKPT

Specifies the name of the CA-Jobtrac production checkpoint data setdefined by the STAGE2 customization job stream. The high-levelqualifier must be an alias in the master catalog, but no other namingrestrictions apply. The syntax is:

CHKPT

��─ ──CHKPT=checkpoint.dsname ─────────────────────�

To enable this option, either shut down CA-Jobtrac with the BACKparameter or IPL.

CMDLIB

Specifies the name of the TRACMDS PDS defined by the STAGE2customization job stream. The TRACMDS member is a group ofcommand sets. A command set is a group of commands executedusing a single command.

See the section about scheduling system commands (SCS) in theCA-Jobtrac Extended Scheduling Services Guide for moreinformation. The syntax is:

CMDLIB

��─ ──CMDLIB=tracmds.pds ──────────────────────────�




CPM

Specifies to activate the CPM (Critical Path Monitor) function inCA-Jobtrac. When specified, the CAIENF events for CPM arecreated, and the CPM related fields and commands are available inISPF.

By default, the CPM function is inactive. This means that noCAIENF events are created and no CPM related commands or datafields are available through the ISPF interface. The CPM keywordsin SCL are accepted even if CPM is inactive. If CPM is turned on,ALL forecasting SCL MUST have the keyword @FCAST=yyddd inthe SCL member being forecasted. For more information on CPM,see the CA-Jobtrac Extended Scheduling Services Guide. The syntaxis:

CPM

┌ ┐─NO──��─ ──CPM= ──┴ ┴─YES─ ───────────────────────────────�


DATELIB

Specifies the name of the Automatic Date Insertion feature controllibrary defined by the STAGE2 customization job stream. DATELIBis the name of the standard PDS(LRECL 88) that contains controlkeys and JCL images for date card insertion and selectable in-streamJCL parameters or SYSIN overrides. For more information on JMF,see the CA-Jobtrac Extended Scheduling Services Guide. Samplemembers PRODDATE and JMFSYM01 are copied over to theDATELIB data set later in the installation. The syntax is:

DATELIB

��─ ──DATELIB= xxxxxxxx.xxxxxxxx.DATELIB ───────────�




DEFAULT0

Specifies whether an event or schedule not found in a higher locationthan 000 can be read from location 000. YES, the default, denotesthat the location does default to location 000 if the event or scheduleis not found in the location specified. Otherwise, the event is postedwith a JCL error, or the schedule is posted with an 'M' dependency.

This does not apply to calendars. The syntax is:

DEFAULT0

┌ ┐─YES─��─ ──DEFAULT�= ──┴ ┴─NO── ──────────────────────────�


DISABLE

Specifies the JOBTRAC ISPF line commands one wishes to disable.The syntax is:

DISABLE

┌ ┐─────��─ ──DISABLE= ───

┴cmd ─────────────────────────────�

For example:

DISABLE=A@C

In this example the "A", "@", and the "C" line commands are nolonger valid for all CA-Jobtrac TSO users, and the INVALIDCOMMAND message displays if these commands are entered.

To enable this option, either shut down CA-Jobtrac with the BACKparameter or IPL. Also recycle TSO users.



DFSVQUAL

Use to override default for allocation of data set names for viewingthe sysout capture file. If DFSVQUAL=NO is used, default sysoutview qualification is not done; that is, the high-level qualifier used inSVQUAL is used for all users. The syntax is:

DFSVQUAL

┌ ┐─YES─��─ ──DFSVQUAL= ──┴ ┴─NO── ──────────────────────────�


DUMPUJV

Signals GJTRUJV2 (IEFUJV SMF exit) to create (Y) or not create(N) SVC dumps in the event that errors occur during allocation oraccess of the checkpoint. Y is the default. Any value other than Y orN defaults to Y. Messages normally issued are still issued. SVCdumps are still created in abend situations. The syntax is:

DUMPUJV

┌ ┐─Y─��─ ──DUMPUJV= ──┴ ┴─N─ ─────────────────────────────�




EXECTRLR

At submission time, CA-Jobtrac flags events that it submits byadding the following step at the end of each event:

//$J EXEC PGM=$A,COND=(�,xx),PARM=parm

CA-Jobtrac uses this additional step to track events. Depending onhow the COND is set, the step does not execute.

If EXECTRLR is set to NO (setting xx to LE), the job step does notexecute. If EXECTRLR is set to YES (setting xx to GT), the job stepexecutes.

The actual COND value is changed only by the option flag. Nonumerical RC is added to the COND statement. Only LE or GT isadded. The syntax is:

EXECTRLR

┌ ┐─NO──��─ ──EXECTRLR= ──┴ ┴─YES─ ──────────────────────────�




INSERTRMS

This keyword specifies if and when a CA-11 U11RMS step shouldbe inserted by CA-Jobtrac during job submission. This applies onlywhen RERUN=CA-11 is specified. Jobs to have the step inserted canbe identified in three ways. The syntax is:

INSERTRMS

��─ ──INSERTRMS= ──┬ ┬─ALL──────── ──────────────────� ├ ┤─NO───────── └ ┘─class list─

where:

ALLSpecifies that all jobs submitted by CA-Jobtrac should have theU11RMS step inserted.

NOSpecifies that no jobs should have the U11RMS step inserted.

class listSpecifies a list of job classes that should have the step inserted.The JOB statement is examined for a class that is contained inthe list specified, and the step is inserted only if a matching classis found. The list is specified as a string of one-character classes,without interceding blanks (that is, AEF23 specifies that classesA, E, F, 2, and 3 are to have the step inserted). Class characterscan be A-Z and 0-9. A special class character (?) is available tospecify that jobs without a class specified should have the stepinserted.

The first three steps of a job are examined for a manually insertedCA-11 U11RMS step before the step is inserted. If the string'11RMS' as in U11RMS or CA11RMS is found in the procname orprogram name of an EXEC statement, then the CA-11 step is notinserted.




JCLTABL

Specifies the maximum number of lines of JCL per job. This tableuses private storage above the line for submission. The default is9000. The syntax is:

JCLTABL

┌ ┐─9��──��─ ──JCLTABL= ──┴ ┴─nnnnn─ ─────────────────────────�


JESCMD

Specifies your JES command character. This parameter informsCA-Jobtrac of the correct character to use when issuing JEScommands. The syntax is:

JESCMD

┌ ┐─$─��─ ──JESCMD= ──┴ ┴─x─ ──────────────────────────────�


JMFTABLE

Specifies the number of entries in the JMF table. The default is 1000and the ECSA usage is approximately 140KB with this value.Specifying 2000 would use approximately 280KB (and so on). Thesyntax is:

JMFTABLE

┌ ┐─1��──��─ ──JMFTABLE= ──┴ ┴─nnnnn─ ────────────────────────�




LIBPGM

Specifies the name for the CA-Librarian Master Library utilityprogram. The syntax is:

LIBPGM

��─ ──LIBPGM= ──┬ ┬─libpgm── ────────────────────────� └ ┘─AFOLIBR─


RAMAXCC

Specifies the MAXCC for a job that is added to the checkpoint usingthe ADD or RUN command. The value specified must either be N orone- to four-numeric characters. N effectively turns off conditioncode checking for these jobs. 0000 is the default. The syntax is:

RAMAXCC

┌ ┐─��─��─ ──RAMAXCC= ──┼ ┼─nnnn─ ──────────────────────────� └ ┘─N────




REMTCRED

ALTMEM indicates the alternate JCL field in an event can be usedto specify the remote password data set member name. This name isused when retrieving the user ID, password, and domain informationto be sent with the event to Unicenter TNG or CA-Jobtrac Agent.The alternate name can be specified on the A= referback in SCL orby specifying the name in the Scheduled Event Detail panel when theevent is on the checkpoint. If this keyword is not specified, thedefault is EVENT, and the event name is used to retrieve theinformation from the remote password data set (TRACR000). Thesyntax is:

REMTCRED

┌ ┐─EVENT──��─ ──REMTCRED= ──┴ ┴─ALTMEM─ ───────────────────────�


RERUN

Indicates the product that CA-Jobtrac is to interface to whenperforming job reruns and restarts. See “INSERTRMS” onpage 4-31. The syntax is:

RERUN

┌ ┐─NONE──��─ ──RERUN= ──┴ ┴─CA-11─ ───────────────────────────�




RESTAGEABEND

Specifies whether to restage jobs on abend. The default is YES. Thesyntax is:

RESTAGEABEND

┌ ┐─YES─��─ ──RESTAGEABEND= ──┴ ┴─NO── ──────────────────────�

where:

YESResults in the following:

1. Restage the event with a "J" dependency.

2. Add an "O" dependency to the restaged event only iforiginally present.

NOResults in the following:

1. Do not restage the event. Instead, add an "O" dependency.

2. When the event is restaged through ISPF, the "O"dependency is removed if not originally present, and therestaged event will have a "J" dependency.

3. If the event is not restaged, releasing the "O" (even iforiginally present) or purging the job will release itssuccessors and do a BYPASS RERUN PROFILE.




RESTAGECAT

Specifies whether to restage jobs on catalog error. SeeRESTAGEABEND for the values of YES and NO. The default isYES. The syntax is:

RESTAGECAT

┌ ┐─YES─��─ ──RESTAGECAT= ──┴ ┴─NO── ────────────────────────�


RESTAGECC

Specifies whether to restage jobs on condition code. SeeRESTAGEABEND for the values of YES and NO. The default isYES. The syntax is:

RESTAGECC

┌ ┐─YES─��─ ──RESTAGECC= ──┴ ┴─NO── ─────────────────────────�


RESTAGEJCLERR

Specifies whether to restage jobs with JCL errors. SeeRESTAGEABEND for the values of YES and NO. The default isYES. The syntax is:

RESTAGEJCLERR

┌ ┐─YES─��─ ──RESTAGEJCLERR= ──┴ ┴─NO── ─────────────────────�




SCHENV

This is a 16-byte field that allows you to specify a default for alljobs. Unless overridden, this value will be inserted on the SCHENVJOB statement parameter by CA-Jobtrac. This value may be verifiedbefore job submission and could result in a JCL error with a W(WLM) dependency if coded incorrectly. NO may be coded for thisvalue so that insertion of the SCHENV parameter on the JOBstatement does not occur as the default. NO is the default if theSCHENV keyword is not found. The syntax is:

SCHENV

┌ ┐─NO───────────────��─ ──SCHENV= ──┴ ┴─cccccccccccccccc─ ───────────────�


SUBROOT

Indicates if a user ID of ROOT can be used when submitting work toUnicenter TNG or CA-Jobtrac Agent on remote platform. If notspecified, the default is NO, and the user ID ROOT is not allowed tobe used. The syntax is:

SUBROOT

┌ ┐─NO──��─ ──SUBROOT= ──┴ ┴─YES─ ───────────────────────────�




SVQUAL

Specifies up to an eight-byte qualifier to put on front of data setnames which CA-Jobtrac dynamically allocates for viewing. This isused only when PROFILE NOPREFIX is set (by default). The syntaxis:

SVQUAL

��─ ──SVQUAL=qual ─────────────────────────────────�

To enable this option, either shut down CA-Jobtrac with the BACKparameter or IPL. Also recycle TSO users.

SYNCSYS1

Defines the SMF system ID of the primary submission system. Thisis only required if running multiple CA-Jobtracs. See “Procedures forCA-Jobtrac in a Shared DASD Environment” on page 7-10 for moreinformation. The syntax is:

SYNCSYS1

��─ ──SYNCSYS1=sysid ──────────────────────────────�


SYNCSYS2

Defines the SMF system ID of the secondary submission system.This is only required if running multiple CA-Jobtracs. See“Procedures for CA-Jobtrac in a Shared DASD Environment” onpage 7-10 for more information. The syntax is:

SYNCSYS2

��─ ──SYNCSYS2=sysid ──────────────────────────────�




SYNCSYS3

Defines the SMF system ID of the backup submission system. Thisis only required if running multiple CA-Jobtracs. See “Procedures forCA-Jobtrac in a Shared DASD Environment” on page 7-10 for moreinformation. The syntax is:

SYNCSYS3

��─ ──SYNCSYS3=sysid ──────────────────────────────�


SYNCTOL

Defines the number of seconds the primary submission system can beidle. If the primary system is idle for more than the number ofseconds defined by SYNCTOL, the secondary system automaticallyissues a WTO to request primary event submission duties.

The operator can switch primary submission duties at any time byissuing the ACTSYS=sysid modify command on the primary system.See the CA-Jobtrac Reports, Maintenance, and Recovery Guide forinformation about switching primary systems. The syntax is:

SYNCTOL

┌ ┐─3��─��─ ──SYNCTOL= ──┴ ┴─nnn─ ───────────────────────────�




TNDOVLP

Signals the CA-Jobtrac schedule load process whether to consider aTIME/DATE overlap as an error. N indicates that CA-Jobtrac willnot flag a TIME/DATE overlap as an error. Y results in aTIME/DATE overlap being considered an error. Y is the default.The syntax is:

TNDOVLP

┌ ┐─Y─��─ ──TNDOVLP= ──┴ ┴─N─ ─────────────────────────────�

Example:

With option TNDOVLP=N, you get:

DAILY1 22�� 1�1D DAILY

With option TNDOVLP=Y, you get:

DAILY1 22�� 1�1D(M) DAILY <==TIME/DATE OVERLAP:

MUST HAVE DEPENDENCY


TSCMDSPA

Specifies the maximum size for the SCS (System CommandScheduling) table. A value from 100 to 5000 can be specified. Largervalues use more ECSA. Table size can only be increased after an IPLor a BACK of CA-Jobtrac. See the CA-Jobtrac Extended SchedulingServices Guide for information on the SCS table. The syntax is:

TSCMDSPA

┌ ┐─25�──��─ ──TSCMDSPA= ──┴ ┴─nnnn─ ─────────────────────────�




TSDSNSPA

Specifies the maximum size for the ADR (Automatic DatasetRecognition) table. A value from 100 to 5000 can be specified.Larger values use more ECSA. Table size can only be increased afteran IPL or a BACK of CA-Jobtrac. See the CA-Jobtrac ExtendedScheduling Services Guide for information on the ADR table. Thesyntax is:

TSDSNSPA

┌ ┐─1��──��─ ──TSDSNSPA= ──┴ ┴─nnnn─ ─────────────────────────�


TSMSGSPA

Specifies the maximum size for the AMR (Automatic MessageRecognition) table. A value from 100 to 5000 can be specified.Larger values use more ECSA. Table size can only be increased afteran IPL or a BACK of CA-Jobtrac. See the CA-Jobtrac ExtendedScheduling Services Guide for information on the AMR table. Thesyntax is:

TSMSGSPA

┌ ┐─25�──��─ ──TSMSGSPA= ──┴ ┴─nnnn─ ─────────────────────────�




TSPGFSPA

Specifies the maximum size for the CCPF (Condition Code ProgramFilters) table. A value from 100 to 5000 can be specified. Largervalues use more ECSA. Table size can only be increased after an IPLor a BACK of CA-Jobtrac. See the CA-Jobtrac Extended SchedulingServices Guide for information on the CCPF table. The syntax is:

TSPGFSPA

┌ ┐─25�──��─ ──TSPGFSPA= ──┴ ┴─nnnn─ ─────────────────────────�


WLMRSRC

This designates the WLM resource you have defined for theCA-Jobtrac started task. CA-Jobtrac sets the status of this resourceduring initialization and termination. This parameter is specified inthe JOBTRA00 startup member. No validation is performed on thevalue specified, and this could result in an improper resource status ifcoded incorrectly. You may code NO for this value, and it results inthe status of the resource not being changed. NO is the default if theWLMRSRC keyword is not found. The syntax is:

WLMRSRC

┌ ┐─NO───────────────��─ ──WLMRSRC= ──┴ ┴─cccccccccccccccc─ ──────────────�




XPLATRERUN

LOCAL indicates jobs that fail are restarted from CA-Jobtrac, ratherthan by Unicenter TNG. If this option is set, Unicenter TNG is notnotified of the job's status until the job successfully completes or thejob is purged or deleted on CA-Jobtrac. The failing job isautomatically restaged in the CA-Jobtrac checkpoint and can berestarted using CA-11. If not specified, the default is REMOTE, andUnicenter TNG is notified of the failure when it occurs. In this case,the job is NOT restaged automatically by CA-Jobtrac. In this mode,the CA-11 interface does not insert the U11RMS step into the job atsubmission. It is recommended that CA-11 not be used when jobreruns are being handled by the remote system. Jobs on thecheckpoint can be restaged manually on the CA-Jobtrac ScheduledEvent Display panel with the R line command and resubmitted forexecution. The change in the status of the job is sent to informUnicenter TNG. When restarting jobs from Unicenter TNG, the jobsshould have a small number of steps, since the jobs can only beresubmitted, not restarted. The syntax is:

XPLATRERUN

┌ ┐─REMOTE─��─ ──XPLATRERUN= ──┴ ┴─LOCAL── ─────────────────────�




Chapter 5. Customization Tasks

The following phases complete customization, set up, andimplementation of CA-Jobtrac:

■ Customization tasks - Covered in this chapter

■ Startup and verification tasks - Covered in Chapter 6

Customization TasksThe customization tasks let you set up CA-Jobtrac to meet yourinstallation's needs. The following tasks are covered:

“Modify CA-GSS” on page 5-2“Customizing SYS1.PARMLIB” on page 5-6“Setting Up Default Authorization” on page 5-9“Setting Up the JES3 Held Job Class” on page 5-11“Defining Location Information (DYNAMLOC) and InitiationIMODs” on page 5-12“Updating Your TSO Procedures or CLIST” on page 5-16“Setting Global Options” on page 5-19“Copy the PRODDATE Member” on page 5-38“Maintaining Table Modules” on page 5-43“Setting Up AMR Support” on page 5-46“Creating IPLTABLE Entries (Optional)” on page 5-47“Enabling the SPACE Command” on page 5-54“Setting Up CA-JCLTrac” on page 5-58“Using Other Sysout Capture Products” on page 5-69“Customizing CA-Jobtrac WorkStation Server” on page 5-71“CA-Jobtrac Cross-Platform Scheduling” on page 5-73

For information on setting up user exits, see the chapter "User Exits"in the CA-Jobtrac Reports, Maintenance, and Recovery Guide.

Chapter 5. Customization Tasks 5-1

Modify CA-GSS

Modify CA-GSSCA-Jobtrac uses CA-GSS facilities to extend its capabilities and toprovide you with fully customizable support for job scheduling. Also,CA-Jobtrac information is made available to other CA-GSS clientsoftware, including that provided by you. See the Unicenter TNGFramework for OS/390 Getting Started guide for more information.

Step 1: Modify JCL

If the CA-Jobtrac load library (CAILIB) is not in a LINKLISTlibrary, include it as a STEPLIB in the CA-GSS PROC.

As needed, you can preallocate the CA-Jobtrac checkpoint data set toCA-GSS. If you do not, it will be dynamically allocated whenneeded. Multiple DD statements, defining multiple checkpoint datasets, may be specified if desired. The issuer of ADDRESSJOBTRAC commands will specify which checkpoint (and hence,which CA-Jobtrac) will be affected by the commands.

Be sure that the token part of the ddname (n of JOBTRACn) matchesthe CA-Jobtrac token ID for the associated checkpoint data set. Anexample follows:

//JOBTRACY DD DSN=jobtrac.checkpt.sys1,DISP=SHR

//JOBTRAC3 DD DSN=jobtrac.checkpt.sys2,DISP=SHR

If you are planning to use the CA-Jobtrac cross-platform schedulingfeature, it requires additional JCL changes and parameters. See“CA-Jobtrac Cross-Platform Scheduling” on page 5-73 for details.Computer Associates recommends that the additional changes bemade after the initial setup of CA-GSS is completed.


Modify CA-GSS

Step 2: Modify CA-GSS Parameters

As needed, modify the CA-GSS initialization parameters that affectCA-GSS' CA-Jobtrac support. The JOBTRAC member of theCA-GSS PPOPTION data set contains examples of these parameters.

Remember that:

■ Most parameters in the JOBTRAC member are commented out. Toactivate one one of them, replace its leading asterisk (*) with ablank.

■ You can copy the JOBTRAC member's contents to yourRUNPARM member, or you can simply provide an INCLUDEJOBTRAC statement.

■ “Parameters You Need to Modify” provides a summary of eachparameter you need to modify. For a complete description of aCA-GSS initialization parameter, see the Unicenter TNGFramework for OS/390 documentation.

Parameters You Need to Modify

ADDRESSMakes the ADDRESS environments provided on the CA-Jobtracdistribution tape as load modules available to REXX IMODs.Remember that:

■ Computer Associates-distributed IMODs expect the addressname JOBTRAC. If you use another name, use theALTNAME parameter to define JOBTRAC.

■ The MAXTASK argument limits the number of IMODs thatmay simultaneously use the ADDRESS environment.

■ The names of load modules reflect the names as shipped onthe CA-Jobtrac tape. You must ensure that these load modulesreside in an APF-authorized library that is accessible toCA-GSS.

ISETIdentifies ISETs (IMOD libraries that are included on theCA-Jobtrac tape).


Modify CA-GSS

JESNODEIn a multi-CPU environment, identifies the JES2 NJE nodename where this copy of CA-GSS is executing.

CA-GSS currently requires this information in parametricform because there is no reliable way of obtaining theinformation directly from JES2 (the techniques required areversion and option dependent).

WTOExecutes the MSG_TRAC845 IMOD whenever the CA-JobtracTRAC845E message is issued.

This IMOD, which is provided in the CA-GSS sample ISET,issues a multi-line WTO that explains the TRAC845E messagein detail. The IMOD then sets an internal flag so that themulti-line message will not be reissued until the next timeCA-GSS is initialized.

Step 3: Activate GoalNet

If you are operating in a multi-CPU environment, with or withoutshared DASD or running CA-Jobtrac in an NJE environment, youmay want to activate GoalNet so that CA-Jobtrac can exchangeinformation between multiple systems. See the Unicenter TNGFramework for OS/390 documentation for details on setting upGoalNet.


Modify CA-GSS

Step 4: REXX IMOD Sample Source (Optional)

The CA-Jobtrac installation tape contains a library of REXXSAMPLES that can be used with CA-Jobtrac and CA-GSS. Toinstall these samples:

1. Modify job REXXCOPY in SAMPJCL to specify the volser andtape unit type for the CA-Jobtrac installation tape, whereindicated.

2. Submit REXXCOPY. This job will:

a. Allocate PDS JT.SAMPREXX.

b. Copy the samples from the tape to JT.SAMPREXX.

c. Allocate VSAM ISET JT.SAMPISET.

d. Copy the IMODS from JT.SAMPREXX to JT.SAMPISET.

e. Compile the IMODs and place them in Test status. Teststatus prevents the IMODs from loading automatically inCA-GSS.

3. Add an ISET statement for JT.SAMPISET to the RUNPARM,JOBTRAC, or ISET member of the CA-GSS PPOPTION dataset. A sample ISET statement for the data set would look likethe following:

ISET JOBTRAC DSN cai.JT.SAMPISET LOAD -

DESC /CA-JOBTRAC SAMPLE IMODs/ SSID isrv

See the Unicenter TNG Framework for OS/390 documentationfor specific RUNPARM control statement formats.


Customizing SYS1.PARMLIB

Customizing SYS1.PARMLIBCA-Jobtrac extracts tracking information during event queuing,execution, and termination. It uses SMF type-30 records and buildsdynamic interfaces to exits IEFUJV, IEFUJI, IEFUSI, IEFACTRT,and IEFU83. Exit IEAVMXIT is used to provide AMR (AutomaticMessage Recognition) services.

This section describes how to set up these exits.

Setting up IEAVMXIT is described on “Setting Up AMR Support”on page 5-46.

Type-30SMF type-30 records are created at job step termination and at jobtermination. CA-Jobtrac uses these records to monitor jobcompletion.

Types 15 and 64SMF record types 15 and 64 monitor data set activity. CA-Jobtracuses these records for data set triggering.

Type-26Job purges create SMF type-26 records. CA-Jobtrac uses theserecords to monitor purged jobs.

Suppressing the Writing of RecordsIf you prefer not to keep the SMF records after CA-Jobtrac usesthem, you can suppress the writing of the record to the SMF data setby coding an IEFU83, IEFU84, or IEFU85 exit. The CA-JobtracSAMPJCL library contains a sample IEFU83 exit. This sample canalso be linked with aliases of IEFU84 and IEFU85. For linkageediting requirements for the IEFU8x exits, see the appropriate IBMmanuals.

Remember that if you suppress the records, they are not captured inyour SMF data sets. The system still creates the records in an SMFbuffer, CA-Jobtrac reads them, and then CA-Jobtrac deletes them.



Caution

If you specify a JES subsystem ('SUBSYS(JES')), you mustinclude the SMF record types and exits described in thefollowing procedure. If you do not, CA-Jobtrac will not trackevents correctly.

ProcedureFollow the steps below to customize SYS1.PARMLIB memberSMFPRMxx and set up required exits:

1. Make sure exits IEFUJV, IEFUJI, IEFUSI, IEFACTRT, andIEFU83 are set up in your system. You can use an IEFBR14dummy exit for any exit not already in your system. The samplemember LINKSMF in the SAMPJCL library shows how to set upa dummy exit.

All exits, including IEFBR14 dummies, should be linked asRENT and REUS.

2. Make sure exits IEFUJV, IEFUJI, IEFACTRT, IEFUSI, andIEFU83 are included in LPALIB.

Exits IEFUJV, IEFUJI, and IEFACTRT must be in LPALIB toensure proper CA-Jobtrac operation. Exit IEFUSI must be inLPALIB for Dynamic Resource Control. Exit IEFU83 must be inLPALIB for proper control of dynamic DSN triggering tables.CA-Jobtrac operates correctly but with less function whenIEFUSI and IEFU83 are not present.

3. Make sure that CA-Jobtrac will function with the SMFconfiguration in SYS1.PARMLIB member SMFPRMxx. Theminimum configuration is shown below:

SYS(TYPE(15,26,3�,64),EXITS(IEFUJV,IEFUJI,IEFUSI,IEFACTRT,IEFU83))

SUBSYS(STC,EXITS(IEFU29,IEFU83,IEFU84,IEFUJI,IEFUSI,IEFACTRT))

4. If you added any exits to SYS1.LPALIB, you must perform anIPL with CLPA before starting CA-Jobtrac.



5. If you do not want to record SMF record types 15, 26, 30, or 64,you can suppress them by coding an IEFU83, IEFU84, orIEFU85 exit. The CA-Jobtrac SAMPJCL library contains asample IEFU83 exit, named SAMPU83. This sample can also belinked with aliases of IEFU84 and IEFU85. For linkage editingrequirements for the IEFU8x exits, see the appropriate IBMmanuals.

6. If you are refreshing SMF exits dynamically, you must performan F JOBTRAC,BACK command before refreshing SMF.

Example SYS1.PARMLIB Member SMFPRMxxThe following figure is an example of a SYS1.PARMLIBSMFPRMxx member:

ACTIVE /� ACTIVE SMF RECORDING �/

DSNAME(SYS1.MAN1,SYS1.MAN2,SYS1.MAN3) /� ETS MAN1 AND MAN2 �/

NOPROMPT /� NO OPERATOR PROMPT �/

REC(PERM) /� TYPE 17 PERM RECORDS ONLY �/

MAXDORM(3��) /� WRITE AN IDLE BUFFER AFTER 3� MIN �/

STATUS(�1��) /� WRITE SMF STATS AFTER 1 HOUR �/

JWT(�2��) /� 522 AFTER 2 HOURS �/

SID(B1) /� SYSTEM ID IS B1 �/

NOLISTDSN /� NO DATASET LISTING �/

SYS(TYPE(�:255),EXITS(IEFU83,IEFU84,IEFACTRT,IEFUJV,IEFUSI,

IEFUJP,IEFUSO,IEFUJI,IEFUTL,IEFU29),INTERVAL(��15��),DETAIL)

SUBSYS(STC,EXITS(IEFU29,IEFU83,IEFU84,IEFUJI,IEFUSI,IEFACTRT),

INTERVAL(SMF,SYNC))

/� WRITE ALL RECORDS AS THE SYSTEM DEFAULT, TAKE ALL KNOWN

EXITS. THERE ARE NO DEFAULT INTERVAL RECORDS WRITTEN.

ONLY SUMMARY TYPE 32 RECORDS ARE WRITTEN FOR TSO.

NOTE:FOR JES2, JES EXITS ARE CONTROLLED BY JES. FOR

JES3, THE EXITS ARE CONTROLLED BY SMF. �/

/� WRITE ALL RECORDS AS BY SYSTEM DEFAULT, TAKE ONLY THREE

EXITS, NOTE:IEFU29 EXECUTES IN THE MASTER ASID WHICH IS A

STC ADDRESS SPACE SO IEFU29 MUST BE ON FOR STC. USE ALL OTHER

SYS PARAMETERS AS A DEFAULT �/


Setting Up Default Authorization

Setting Up Default AuthorizationThe CA-Jobtrac TRACAUTH table is used to:

■ Define the CA-Jobtrac functions a user can perform

■ Assign names to locations

■ Define who the system notifies of abends and errors

The table is created by including @AUTH macro statements in theASMAUTH job. ASMAUTH is then assembled and linked. You canmodify the table at any time, even when CA-Jobtrac is running.

Authorization AlternativeInstead of using the TRACAUTH table, you can use the TRACX26user exit to interface to your system's security software. Forinformation, see the TRACX26 exit in the CA-Jobtrac Reports,Maintenance, and Recovery Guide.

Using @JOBTRAC?A user ID assigned to the CA-Jobtrac started task must be added tothe TRACAUTH table to allow @JOBTRAC (ADDRESSJOBTRAC) to pass security checking.

Caution

Before modifying the TRACAUTH table for your needs, youshould assemble and link it for use with the CA-Jobtracverification procedure, IVP. If you do not, the IVP will not workproperly. The necessary procedures follow.


Setting Up Default Authorization

TRACAUTH Table Used for VerificationTake the following steps to modify the TRACAUTH table:

1. Edit member ASMAUTH in the SAMPJCL library.

2. Review the JCL carefully, making revisions to reflect yourinstallation's requirements.

3. Run the ASMAUTH job to assemble and link the TRACAUTHtable.

4. The TRACAUTH table is automatically loaded when CA-Jobtracis started. If you are modifying the table when CA-Jobtrac isrunning, issue the following command to load the modified table:

F taskname,AUTH

See the TRACAUTH Security chapter in the CA-Jobtrac Reports,Maintenance, and Recovery Guide for details on setting up customauthorizations.


Setting Up the JES3 Held Job Class

Setting Up the JES3 Held Job Class

RequirementIf you have not already assigned a sysout hold class for CA-Jobtrac,your JES3 system programmer must use the JES initializationparameters to do so. You cannot use the sysout capture file until thesysout hold class for CA-Jobtrac is defined.

JES3 RequirementFor JES3 you need to define the sysout class as follows:

SYSOUT,CLASS=J,TYPE=(PRINT),HOLD=EXTWTR

Optionally add ,DEST=LOCAL.


Defining Location Information (DYNAMLOC) and Initiation IMODs

Optionally, other data sets may be concatenated to each currentlyallocated DD (except TRACTnnn) by using the following parameters:

CONCAT

��──CONCAT─ ──DDNAME= ──┬ ┬──TRACSnnn ────────────────�├ ┤──TRACJnnn├ ┤──TRACRnnn└ ┘──TRACDnnn

�─ ──, ──┬ ┬─DATASET─ =dataset name ───────────────────� └ ┘─DSN─────

�─ ──┬ ┬──────────────── ───────────────────────────�└ ┘──,VOLSER=volser

Note: If concatenated data sets are edited using the CA-JobtracISPF interface and saved, the member is saved to the firstdata set in the concatenation. This is standard IBM practice.

DEALLOC

��──DEALLOC─ ──DDNAME= ──┬ ┬──TRACSnnn ──────────────�├ ┤──TRACJnnn├ ┤──TRACRnnn├ ┤──TRACDnnn└ ┘──TRACTnnn

DDNAME is as in the ALLOC statement. This statement can be usedto free a library for maintenance and so forth.

Note: If the DDNAME has more than one data set allocated inconcatenation, all of the data sets in the concatenation will bereleased from the DDNAME. If a single data set is to beremoved from a concatenation, the DDNAME should bereallocated using the ALLOC keyword instead.

SET INITIMOD

��─ ──SET INITIMOD= ──┬ ┬─imodname─ ─────────────────� └ ┘─NONE─────

Sets the default global initiation IMOD for subsequently definedlocations. NONE indicates no global initiation IMOD is desired. TheIMOD name can be eight characters long. This value will be appliedto all subsequent locations until explicitly resent by another 'SETINITIMOD=..' statement. See the CA-Jobtrac Extended SchedulingServices Guide for more information about IMOD requirements.



INCLUDE

��──INCLUDE──membername──────────────────────────�

The location definitions can be split between multiple members andreferenced by INCLUDE statements. When INCLUDE statements areparsed, the member referenced is opened and the statements are readbefore any further statements of the original member. INCLUDE canbe nested. DYNAMLOC does not allow concatenation DDs forlocations.

ExampleMember named DYNAMLOC contains the following statements:

INCLUDE LOC��

INCLUDE LOC��1

/� END OF FILE �/

Member named LOC000 contains the following statements:

SET INITIMOD=imodname|NONE

ALLOC DD=TRACJ��,DSN=your.TRACJ��,NAME=LOC��1

ALLOC DD=TRACS��,DSN=your.TRACS��

ALLOC DD=TRACD��,DSN=your.TRACD��

ALLOC DD=TRACT��,DSN=your.TRACT��

ALLOC DD=TRACR��,DSN=your.TRACR��

CONCAT DD=TRACJ��,DSN=your.TRACJC��

CONCAT DD=TRACS��,DSN=your.TRACSC��

Member named LOC001 contains the following statements:

SET INITIMOD=imodname|NONE

ALLOC DD=TRACJ��1,DSN=your.TRACJ��1

ALLOC DD=TRACS��1,DSN=your.TRACS��1

ALLOC DD=TRACD��1,DSN=your.TRACD��1

ALLOC DD=TRACT��1,DSN=your.TRACT��1

ALLOC DD=TRACR��1,DSN=your.TRACR��1,NAME=LOC��1

You can find samples of DYNAMLOC, LOC000, and LOC001 inthe SAMPJCL library.



Using INCLUDE statements does not allow for continued lines.Most environments do not require them. You can use continuationsif all the statements are placed in the DYNAMLOC member itself asfollows. The member name in PPOPTION must be DYNAMLOC.

ALLOC DD=TRACS��,DATASET=your.SCLLIB,

NAME='LOCATION NAME',VOLSER=VOLSER

ALLOC DD=TRACT��,DATASET=your.TRACT��,

VOLSER=VOLSER

ALLOC DD=TRACJ��,DATASET=your.TRACJ��,

VOLSER=VOLSER

ALLOC DD=TRACD��,DATASET=your.DOCLIB,

VOLSER=VOLSER

ALLOC DD=TRACS��6,DATASET=your.TRACS��6,

VOLSER=VOLSER

ALLOC DD=TRACT��6,DATASET=your.TRACT��6,

VOLSER=VOLSER

ALLOC DD=TRACJ��6,DATASET=your.TRACJ��6,

VOLSER=VOLSER


Updating Your TSO Procedures or CLIST

Updating Your TSO Procedures or CLISTAll members in the CA-Jobtrac CAICLIB library need to be in yourCLIST library. Either concatenate our library to your SYSPROC list,or copy the members into one of the libraries in your SYSPROC list.

Also, you need to ensure all the CA-Jobtrac and CA-GSS librariesand data sets are available. To do this, determine whether allocationsfor ddnames ISPMLIB and ISPPLIB are in a TSO logon procedureor in a CLIST. You must update one or the other. This sectiondescribes how to update these.

The STAGE2 job stream added a sample CLIST named TCLIST3 toyour SAMPJCL library.

If you are using . . . See

A TSO logon procedure the following topic

A logon CLIST “Sample CLIST UsingLIBDEFs” on page 5-18

Updating Your TSO ProceduresFollow the steps below to update your TSO procedures to providefull-function ISPF support.

1. Identify which TSO logon procedures need CA-Jobtrac access.

2. Add the required DD statements shown in the TSO proceduresidentified in the following samples:

Required DD Statements for TSO Users

If you are using the DYNAMLOC member, the DDs from theDYNAMLOC member are not required in the CLIST.

//JOBTRACx DD DSN=your.JOBTRACx,DISP=SHR

//JOBHISTx DD DSN=your.JOBHISTx,DISP=SHR

//SEQHISTx DD DSN=your.JOBHISTx.DATA,DISP=SHR

//CAPTURE DD DSN=your.CAPTURE,DISP=SHR

//DATEFILE DD DSN=your.DATELIB,DISP=SHR

//ISPPLIB DD DSN=your.ISPPLIB,DISP=SHR

// DD DSN=your.CAIISPP,DISP=SHR

// DD DSN=your.GSSCAIISPP,DISP=SHR

//ISPMLIB DD DSN=your.ISPMLIB,DISP=SHR

// DD DSN=your.CAIISPM,DISP=SHR

// DD DSN=your.GSSCAIISPM,DISP=SHR



Optional DD Statements for TSO Users

If you are not using DYNAMLOC to allocate the location datasets, add your location data sets also.

//TRACDnnn DD DSN=your.TRACDxxx,DISP=SHR

//TRACJnnn DD DSN=your.TRACJxxx,DISP=SHR

//TRACRnnn DD DSN=your.TRACRxxx,DISP=SHR

//TRACSnnn DD DSN=your.TRACSxxx,DISP=SHR

//TRACTnnn DD DSN=your.TRACTxxx,DISP=SHR

3. Optionally, add the DD statements shown below:

■ Up to 255 TRACJnnn DD statements to define JCL librariesfor separate locations. Substitute a number from 000 to 254for nnn. The library that is used is controlled by locationassignments in the @AUTH macro and locations assigned toeach scheduled event.

■ Up to 255 TRACTnnn DD statements to define temporary-useJCL libraries for separate locations. Substitute a number from000 to 254 for nnn. The library that is used is controlled bylocation assignments in the @AUTH macro and locationsassigned to each scheduled event.

■ Up to 255 TRACSnnn DD statements to define SCL librariesfor separate locations. Substitute a number from 000 to 254for nnn. The library that is used is controlled by locationassignments in the @AUTH macro.

■ Up to 255 TRACDnnn DD statements to define DOC librariesfor separate locations. Substitute a number from 000 to 254for nnn. The library that is used is controlled by locationassignments in the @AUTH macro.

For the JCL libraries, you can choose a PAN, LIBR, or standardPDS access method. All libraries, however, on the same ddnamemust use the same access method. The temporary-use JCL andSCL libraries must be a PDS.



Updating Your CLIST AllocationsIf your DD statements are in an existing logon CLIST, update yourCLIST by following the steps below:

1. Add the CA-Jobtrac message library data set (CAIISPM) to theISPMLIB DD statement.

2. Add the CA-Jobtrac panel library data set (CAIISPM) to theISPPLIB DD statement.

3. To access CA-Jobtrac from an ISPF menu using TCLIST3, youmust update your ISR@PRIM or equivalent main ISPF menu. Todo this, use member SAMPPRIM in your SAMPJCL library asan example and make the following change:

J,'PGM(GJTRVSPF) ...' <=== From this

J,'CMD(%TCLIST3) ...' <=== To this

CA-11 Interface CLISTSee “Installation Requirements” on page 5-55 for more information.

Sample CLIST Using LIBDEFsSee member LIBDEF in SAMPJCL for a sample CLIST.

Adding CA-Jobtrac to Your ISPF Main MenuTo add CA-Jobtrac to your ISPF main menu, you must update yourISR@PRIM or equivalent main ISPF menu. You can use memberSAMPPRIM in your SAMPJCL library as an example of thenecessary additions.


Setting Global Options

Setting Global OptionsCA-Jobtrac global options describe global values and theenvironment in which CA-Jobtrac operates.

CA-Jobtrac global options are set using the CA-Jobtrac globaloptions panels and the JOBTRAnn member. Some options are setusing the global options panels only, some by the JOBTRAnnmember only, and some options are set using either one.Additionally, some of the options set using JOBTRAnn are displayedon the global options panels, but they cannot be set on the panels.

For more information about the JOBTRAnn member, see Chapter 4.

RequirementTo set some default options, CA-Jobtrac must be started. Forinformation about starting CA-Jobtrac, see Chapter 6.

ProcedureFollow the steps below to change global options using the globaloptions panels:

1. Start CA-Jobtrac. For information about starting CA-Jobtrac, seeChapter 6.

2. Issue the SYS OPTS command from any CA-Jobtrac display todisplay the Global Options Menu.

3. Select option A, All of the Above. The CA-Jobtrac GlobalOptions panel is displayed, which is the first in the series ofglobal options panels.

Instead of option A, you can choose a specific options panel ifyou wish to change a selected option.

4. Change entries on the CA-Jobtrac Global Options panel so thatthe options are set as required for your installation. See “Optionson the CA-Jobtrac Global Options Panel” on page 5-21 for adescription of the options.

Press Enter to save your changes, or press the End PF key to exitwithout saving your changes. The Sysout Capture Options panelis displayed.



5. Change entries on the Sysout Capture Options panel so that theoptions are set as required for your installation. See “Options onthe Sysout Capture Options Panel” on page 5-31 for adescription of the options.

Press Enter to save your changes, or press the End PF key to exitwithout saving your changes. The Library Definitions panel isdisplayed.

6. Change entries on the Library Definitions panel so that theoptions are set as required for your installation. See “Options onthe Library Definitions Panel” on page 5-35 for a description ofthe options.

Press Enter to save your changes, or press the End PF key to exitwithout saving your changes.

Press the END PF key to return to the panel from which youaccessed the global options panels.

7. Update CA-Jobtrac internal components with the new globaloptions by issuing one of the following operator commands (seethe CA-Jobtrac Operator Guide for more information aboutCA-Jobtrac operator commands):

F taskname,OPTS[=nn|��]

F taskname,JICAUPD

Optionally, replace nn with a two-digit numeral specifying aJOBTRAnn member where nn matches the nn in JOBTRAnn. Thedefault is member JOBTRA00.

Sample Global Options MenuThe following panel shows a sample Global Options Menu.

� �CA-Jobtrac Global Options Menu

COMMAND ===> SCROLL ===> PAGE

yy/mm/dd hh:mm

1 CA-Jobtrac - CA-Jobtrac Global Options

2 CAPTURE - Sysout Capture Options

3 LIBRARY - Library Definitions

A ALL - All of the above

�

�



Options on the CA-Jobtrac Global Options Panel

The panel below shows a sample CA-Jobtrac Global Options panel.Field descriptions follow.

� �CA-Jobtrac CA-Jobtrac Global Options


yy/mm/dd hh:mm

Date Format A)mer/I)ntl => A Hold ABENDing Output (Y/N) => Y

IPL Name Prompt (Y/N) => Y Catalog Error Check (2RUD) => YYYY

Auto-Schd Allowed (Y/N) => Y

Restart Support (R/N) => R

Nodelete Error Msg (Y/N) => Y Multisys Sync Dormancy => 999

Step Sysout Footers (Y/N) => Y SYSID Priority List CPU 1 =>

Archive Print Class => A CPU 2 => CPU 3 =>

SPF Sysout Print Class => T Prompt on Max Lines (Y/N) => N

Capture Sysout (Y/N) => Y Auto-Queue Event Classes =>

JES Command Character => $ CA-Librarian Program Name => AFOLIBR

Holiday Action Time (HHMM) => �8�� REXX Maximum Time (HHMM) => ��15

REXX Retry Interval (HHMM) => ��1 REXX Retry Maximum Count => �999

ISERVE Subsystem Name => ISRV ISERVE STC Procedure Name => GSSA

NJE Node (Y/N) => Y Cross Node Query Limit =>

NJE Node Tokens => AT

Global Termination IMOD => CLEANUP

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

�

�

Date FormatSpecifies the date format to be used on some of the CA-Jobtracdisplays and in SCL (Schedule Control Language).

■ Specify A to accept dates in the American format of mm/dd.

■ Specify I to accept dates in the International format of dd/mm.

Note: See the CA-Jobtrac User Profile panel in the CA-JobtracOperator Guide for the date format field for each TSOsession.

IPL Name PromptIndicates whether the operator is to be prompted at IPL time.

■ Specify Y to direct CA-Jobtrac to issue the TRAC400A andTRAC401A WTORs.

■ Specify N to direct CA-Jobtrac to issue message TRAC010I withno prompt.

See the CA-Jobtrac Message Guide for descriptions of messages.



AUTO-SCHD AllowedSpecifies whether the AUTO-SCHD feature is supported. See theCA-Jobtrac Operator Guide for complete information about theAUTO-SCHD feature.

■ Specify Y to direct CA-Jobtrac to dynamically add any event thatis submitted (by any means) with a special AUTO-SCHD characterto the CA-Jobtrac current schedule if the event is not alreadyscheduled.

■ Specify N to prevent addition of AUTO-SCHD events to theCA-Jobtrac current schedule.

See “AUTOC” on page 4-24 and “AUTOQ” on page 4-25 for moreinformation.

Restart SupportSpecifies the restart/rerun system to be used. The following tabledescribes the available values:

Value Description

R Direct the restart system (CA-11) to performstep restarts. See the CA-11 documentationfor more information.

N No restart automation is in use.

Nodelete Error MessageSpecify Y to direct CA-Jobtrac to send the following nondeletablemessage to the operator console when a scheduled CA-Jobtrac eventends with an abend, JCL error, condition code exception, or NOTCATALOGED 2 error:

TRACWARN - JOB jobname STEP:stepname ABENDED, CODE=abcode

(or COND CODE=ccode or CATALOG ERROR NOTED)

If a reader JCL error occurs or an operator purges an event, thefollowing FLUSHED message is issued:

TRACWARN - JOB jobname FLUSHED, DID NOT EXECUTE.

Specify N to suppress these messages.



Step Sysout FootersSpecify Y to direct CA-Jobtrac to print the detailed step executioninformation shown in the figure below to help in problem resolutionand job step tuning. This is printed for every step of every job.

Specify N to suppress the information.

��CA-JOBTRAC V3.5 ��

� JOBNAME STEP STEPNAME PGM-NAME START STOP ELAPSED TCB-CPU SRB-CPU SWAPS V/R STORAGE USED �

� TESTJOB1 1 SMP13 HMASMP 13.32.33 13.34.�4 ��.�1.31 1.2� .45 6 678K VIRT 237K �

� PGN SRV-UNTS T-EXCPS D-EXCPS V-RCLMS RES-TIME P-INS P-OUTS VIO-P-I VIO-P-O P/SW-I P/SW-O CODE�

� 4 421 � 15 � ��.��.25 4� 54 � � � � R��

� DDNAME-----EXCPS DDNAME-----EXCPS DDNAME-----EXCPS DDNAME-----EXCPS DDNAME-----EXCPS DDNAME-----EXCPS �

� SYSIN 1� SYSPRINT 97� SYSUT1 5 DDOUT 234567 �

��CA-JOBTRAC V3.5 ��

Archive Print ClassSpecifies a print class if you archive to print. Microfiche users shouldbe aware that CA-Jobtrac sorts sysouts by job name and places a fullframe separator page between sysouts on the archive tape for offlinemicrofiche and between sysouts in the print queue for onlinemicrofiche.

SPF Sysout Print ClassWhen viewing sysouts in CA-Jobtrac/ISPF, you can print a copy ofany listing. The sysout class you specify in this field is the outputclass of the TSO copy.



Capture Sysout■ Specify Y to direct CA-Jobtrac to capture sysouts for online

viewing.

■ Specify N to direct CA-Jobtrac to bypass sysout capture. (Youshould specify N if you wish SAR to handle the sysout capture.)

The capture classes are defined on the Sysout Capture Options panel.Even if you set this field to N, you must specify a primary captureclass. It is used for all schedule captures.

CA-Jobtrac attempts to spool ANY SYSOUT of aCA-Jobtrac-submitted event if Y is selected in the global options. Alloutput classes should be specified in the Sysout Capture Options tobe spooled properly. If not defined in the Sysout Capture Options,CA-Jobtrac issues these warning messages:

TRAC�98W WAITING FOR SYSOUT, JOB: eventname -

NONE FOUND IN ANY CLASS YET

TRAC�99W SYSOUT NOT FOUND, eventname BYPASSED.

JES Command CharacterThis field defines the prefix character you will use to indicate that aconsole command is to be processed by JES.

This option is set in member JOBTRAnn (see Chapter 4). Youcannot change this option on the CA-Jobtrac Global Options panel.

Holiday Action TimeSets a time range for holiday days. This setting affects events alreadyon the current schedule, it does not affect a schedule being loaded tothe current schedule, or an event with a date of +1 and a time ofASAP specified.



For additional information about holidays, see the holidayinformation in the CA-Jobtrac Schedule Creation Guide. Thefollowing figure shows an example of how this option affects holidayscheduling:

Holiday Action Time global option set to �8��.

Midnight

��

│ �8��

Thursday │ ¦ Friday, a holiday

─────────────────────────────────────────────────────────

┌────────────────────────┐ │ ¦

│ Event scheduled with │────────────■ ¦

│ +1 �7�� time, and any │ │ ¦

│ holiday │ │ ¦

└────────────────────────┘ │ ¦

│ ¦ ┌────────────────────────┐

Event is scheduled because │ ¦ │ Schedule with no │

Thursday is a valid workday, │ ■───¦────■──│ holiday action │

and the target time is less │ ¦ │ specified loaded on │

than the holiday action time. │ ¦ │ Friday at any time. │

│ ¦ └────────────────────────┘

│ ¦ Schedule will not load,

│ ¦ unless a specific holiday

┌───────────────────────┐ │ ¦ action of S, O, W, or N is

│ Event scheduled with │──────────────■ ¦ used. This is regardless

│ +1 date, �9�� time │ │ ¦ of the setting of

│ and any holiday │ │ ¦ the holiday action

│ action │ │ ¦ time global option.

└───────────────────────┘ │ ¦

Event is scheduled because │ ¦

Thursday is a valid workday, │ ¦

but since the target time is │ ¦

greater than the holiday │ ¦

action time, an M(H) holiday │ ¦

hold dependency is assigned │ ¦

to the event. │ ¦

│ ¦

┌───────────────────────┐ │ ¦

│ Event scheduled with │──────────────■─────────────■

│ +1 date, ASAP time, │ │ ¦

│ and any holiday │ │ ¦

│ action │ │ ¦

└───────────────────────┘ │ ¦

Event is scheduled because │ ¦

Thursday is a valid workday, │ ¦

but since the target time is │ ¦

greater than the holiday │ ¦

action time, an M(H) holiday │ ¦

hold dependency is assigned │ ¦

to the event. │ ¦

│ ¦

│ ¦



REXX Retry IntervalThe amount of time an environmental dependency waits beforeexecuting again. This option is used with the REXX Retry MaximumCount option. This option applies to environmental dependencies. Forinformation on using this option effectively, see the REXXinformation in the CA-Jobtrac Extended Scheduling Services Guide.

ISERVE Subsystem NameThe name of the CA-GSS IMOD Facility (CA-GSS subsystem) tosend REXX IMOD and environmental dependency requests to. Youcan have multiple subsystems defined. The CA-Jobtrac REXXfacility checks whether the subsystem is running. If it is not, thefacility attempts to start it. If it cannot start it, an error message isissued.

NJE NodeSpecifies whether to activate the CA-Jobtrac NJE support for thisinstance of CA-Jobtrac on this system image. If you specify Y, theNJE Node Tokens field becomes significant.

NJE Node TokensA CA-Jobtrac token is the x in JOBTRACx DD statement. The tokenidentifies and differentiates individual CA-Jobtracs.

In this field, you specify which of the CA-Jobtrac events arerecognized by this CA-Jobtrac. This is done by listing up to 39tokens. If you leave this field blank, all tokens (that is all eventsfrom all CA-Jobtracs) are processed by this CA-Jobtrac. If you leavethe field blank, do one of the following:

■ Only start up one NJE-capable CA-Jobtrac on any single systemimage

■ Specify non-overlapping tokens for each CA-Jobtrac running

The JES /*ROUTE or /*XEQ statements identify an event as an NJEevent.

If you explicitly specify tokens and you submit NJE jobs to thesubmitting node itself, you should specify the token of the submittingCA-Jobtrac itself in the token list.

The specified NJE nodes apply only to the NJE events for theCA-Jobtracs which are specified as being NJE nodes. All otherCA-Jobtrac instances recognize only their own tokens.



Global Termination IMODThe name of the global termination IMOD. The use of a globaltermination IMOD is optional.

The global termination IMOD executes after each event. Theexecution takes place immediately after CA-Jobtrac recognizes thetermination of an event, but before CA-Jobtrac calls user exitTRACX09 or releases successors.

This order of execution permits the IMOD to alter the status orattributes of the event from within the IMOD using @JOBTRAC(ADDRESS JOBTRAC). For example, you can add an output releasedependency to prevent the release of successors until some useraction is taken. The execution of the IMOD does not preventCA-Jobtrac from processing other events. Consequently, multipleinstances of the global termination IMOD can execute at the sametime for different events.

Hold ABENDing OutputSpecify Y to direct CA-Jobtrac to issue a $HJnnnn messageimmediately at termination for any event that ends in an abend,condition code check, or catalog error. This prevents accidentalprinting of output.

Specify N to prevent CA-Jobtrac from issuing the $HJnnnn message.

Catalog Error CheckThis field defines the CA-Jobtrac response to IBM messagesindicating catalog errors in a batch job. Each of the four charactersin the field can be set to Y (yes) or N (no) and correspond to thepositional codes 2RUD, which are described below:

Character Description

2 Not cataloged 2

R Not recataloged

U Not uncataloged

D Not deleted



If the code is set to Y, CA-Jobtrac checks for these messages incaptured sysouts. If the message is found, CA-Jobtrac imposes anoutput release dependency (code O) on the event. The operator mustthen issue the A line command to remove the O dependency andrelease any successors.

If the code is set to N, CA-Jobtrac will not check for these messages.

Multisys Sync DormancyThis option is used only in multi-system shops.

A CA-Jobtrac started task runs on each system in a shared JES spoolenvironment. If for any reason the primary system (the onedesignated to submit events) fails, the secondary system (the one nextin priority) prompts the operator and requests dynamic transfer ofprimary duties (event submission, sysout capture, and so on) to thenext system.

The Multisys Sync Dormancy field indicates the number of secondsthe primary system can be inactive before the secondary systemprompts the operator for a decision.


SYSID Priority ListThis field indicates the priority sequence of the SMF IDs for one tothree systems in a shared spool environment. System 1 is the primaryCPU and assumes the duties of event submission and sysoutmanagement. System 2 is the secondary system and assumes controlif system 1 loses communication with system 2. If both system 1 andsystem 2 are down, system 3 takes control.

If primary roles are transferred and the failing system comes back up,it assumes a secondary role until the operator issues anACTSYS=sysid command to restore or reassign the primary system.See the CA-Jobtrac Reports, Maintenance, and Recovery Guide forinformation about switching primary systems.




Prompt On Max Lines■ Specify Y to direct CA-Jobtrac to issue a TRAC196A WTOR each

time it reaches the line limit for a single job in a given class. Youcan limit the line count on each output class during sysout capture(see the Sysout Capture Options panel on “Options on the SysoutCapture Options Panel” on page 5-31).

■ Specify N to suppress the WTOR.

Auto-Queue Job ClassesSpecifies up to eight auto-queue job classes for external submissionof JCL for jobs scheduled by CA-Jobtrac with dependency code Q.An event submitted in one of these classes will be flushed with aJCL error if the event is not already on the schedule with a Qdependency code. See the CA-Jobtrac Operator Guide forinformation about using auto-queue job classes.


CA-Librarian Program NameIn shops that use CA-Librarian for JCL editing and submission, theMaster Library utility program has a customer-defined program name.This field indicates the batch utility program name.


REXX Maximum TimeThe maximum amount of elapsed time a REXX IMOD orenvironmental dependency can run before it is considered to be in aloop. If the maximum amount of time is exceeded, the REXX IMODor environmental dependency is canceled. Use zero to denote there isno time limit. For information on using this option effectively, seethe REXX information in the CA-Jobtrac Extended SchedulingServices Guide.

REXX Retry Maximum CountThe number of times an environmental dependency executes, tryingto satisfy its condition. This option is used with the REXX RetryInterval option. This option applies to environmental dependencies.For information on using this option effectively, see the REXXinformation in the CA-Jobtrac Extended Scheduling Services Guide.



ISERVE STC Procedure NameIf the subsystem specified in the ISERVE Subsystem Name field isnot running, this is the name of the procedure to use to bring up thesubsystem.

Cross Node Query LimitWhen using the Cross Node Query panel, to query events acrossmultiple NJE nodes, a time limit for the query can be imposed.

This field specifies a global time limit for the query. Specify the timelimit in minutes, up to two digits. When the time limit expires, thequery ends and the information obtained to that point is displayed. Auser can also specify a local time limit. If the user's specified timelimit is more than the global time limit, the global time limit is used.

If you leave this field blank or specify 0, no time limit is imposed.



Options on the Sysout Capture Options Panel

The Sysout Capture Options panel lets you define up to four sysoutcapture classes with different processing characteristics.

How the JES Hold Output Command Affects Sysout CaptureThe JES hold output command is issued as soon as possible. Whenthis occurs depends on if you are using the CA-Jobtrac sysoutcapture feature. The following table explains when the command isissued:

Using theCA-Jobtracsysoutcapturefeature?

When the hold output command is issued

No The hold output command is issued as soon as the job failure is detected,while the job is still running. Hold output commands keep outputwriters from accessing the output. Output writers include the TSOOUTPUT command (which will report the job has no held output atsome levels), and capture packages such as Computer AssociatesCA-View. Packages such as CA-SYSVIEW/E will be able to view theoutput.

Yes CA-Jobtrac cannot hold the job at the moment the job fails, or it couldnot capture the job's output. Instead, CA-Jobtrac holds the job at thepoint that the capture subtask is told to begin work on it. This can beseveral seconds after the job ends, so nonheld sysout could be printed orspooled to some other writer.

A better approach in this case is to ensure that all the sysouts created byyour CA-Jobtrac jobs are held sysouts. Then specify the CA-Jobtracsysout capture options to requeue the output to the original class if youdesire. The sysout capture processor will detect the failure and will leavethe output from failed jobs alone (in the sysout held class).

Note: See “CAPDMPS” on page 4-25.

First DefinitionThe first definition (class 1) is the primary definition. It is used forall schedule captures.



The first Output Capture Class field must be specified, even if youare not capturing sysout (Capture Sysout field on the CA-JobtracGlobal Options panel set to N). Class A is a good class to use sinceit is not held anywhere, and CA-Jobtrac does not capture nonheldsysout.

Using CA-ViewIf you are using CA-View to capture your sysout, see “Using OtherSysout Capture Products” on page 5-69 for details about defining thewriter options.

Sysout Capture Options PanelThe panel below shows a sample Sysout Capture Options panel.Field descriptions follow.

� �CA-Jobtrac Sysout Capture Options


yy/mm/dd hh:mm

Output Capture Class 1 => T Ret days/Vers => 1 Max Lines => �

Disposition (P=Purge, R=Requeue, N=None) => R Requeue Class => 4

Archive (T=Tape, P=Print, B=Both, N=None) => T Capture Limit => 3

Output Capture Class 2 => J Ret days/Vers => 1 Max Lines => �

Disposition (P=Purge, R=Requeue, N=None) => P Requeue Class => 4

Archive (T=Tape, P=Print, B=Both, N=None) => N Capture Limit => 255

Output Capture Class 3 => K Ret days/Vers => 2 Max Lines => �


Archive (T=Tape, P=Print, B=Both, N=None) => P Capture Limit => 255

Output Capture Class 4 => 3 Ret days/Vers => 1 Max Lines => �


Archive (T=Tape, P=Print, B=Both, N=None) => P Capture Limit => 255


�

�

Output Capture ClassSpecify a SYSOUT= class or the job MSGCLASS= for whichsysouts are to be captured and retained for online viewing. Theclasses must be defined to JES as HELD classes.

Ret days/VersSpecify the number of days or number of versions of the sysout youwant to keep online. The number of days or versions, whichever isgreater, will be kept.

For example, suppose you specify 2 for a sysout class. An event thatruns 10 times a day in that class will be kept for two days. However,an event that runs once a year will be kept for two years (2 versions).



Max LinesSpecify a maximum line count for any given sysout data set in thisclass. If the output limit is reached, the capture is truncated and thesysout is requeued to the requeue class.

Specify 1-32767 lines. Specify 0 for an unlimited line count.

If the Prompt On Max Lines entry on the CA-Jobtrac Global Optionspanel is Y, CA-Jobtrac issues a message to the operator requesting adecision on the capture of the excessive sysout. The operator canreply Y to the CA-Jobtrac WTOR TRAC196A message to instructCA-Jobtrac to continue capture each time the maximum number oflines is exceeded.

DispositionSpecify a sysout disposition of P, R, or N for normal (non-abending)jobs. The following table explains each disposition:

Disposition Explanation

P Purges captured sysouts from the JESqueue

R Requeues captured sysouts to the sysoutrequeue class in held status after successfulcapture

N Retains captured sysouts in their heldmessage class after capture

Requeue ClassSpecify the output class to which you wish all requeue requests sent.It should be a print class that is not held. CA-Jobtrac places a holdon each requeued event. Scheduled events that abend have all theiroutput requeued to this class after it is successfully captured.

You can also use this parameter to reroute output to another sysoutarchival product. If you are using another sysout archival product, seeyour product's documentation to see if the class you specify must bea held class.



Archive■ Specify T to request that a copy of any sysout not already archived

be put on tape when a 0ARCHIVE or 0SYSARCH task is executed(see the CA-Jobtrac Extended Scheduling Services Guide forinformation about scheduling dynamic maintenance).

■ Specify P to request that a copy of any sysout not already archivedbe spooled to the Archive Print Class defined on the CA-JobtracGlobal Options panel when a 0ARCHIVE or 0SYSARCH task isexecuted. This option is designed for online microfiche output.Both the archive tape and the spooled copy are sorted into jobname sequence and contain separator pages and header informationsuitable for fiche titling.

■ Specify B to request that both a tape backup and a print-spooledcopy be created for any sysout not already archived when a0ARCHIVE or 0SYSARCH task is executed.

■ Specify N to request no archival or backup of sysouts when a0ARCHIVE or 0SYSARCH task is executed.

You should always make a tape backup if CA-Jobtrac is the onlysysout archival tool in use. CA-Jobtrac utilities provide for recoveryof aged sysouts from the archive tapes.

Capture LimitSpecify the number of sysout data sets that are to be captured for agiven event. For example, specify 255 to capture all sysouts in theclass. If you specify 3, only the first three sysouts found in the outputcapture class are captured. All remaining sysouts are requeued to therequeue class.

Capturing the first three sysouts is useful with job-level messageclass output, where the first three MSGCLASS sysouts are usually(to the extent indicated by MSGLEVEL):

■ The JES job log

■ Converted JCL listing

■ Step execution/allocation log

Additional sysouts are normally sent by the user to SYSOUT=*. So,to capture only the MSGCLASS listing and requeue all SYSOUT=*output, you could specify a capture limit of three.


Options on the Library Definitions Panel

The Library Definitions panel lets you define libraries for use byCA-Jobtrac.

Sample Library Definitions PanelThe panel below shows a sample Library Definitions panel. Fielddescriptions follow.

� �CA-Jobtrac Library Definitions


yy/mm/dd hh:mm

Archive DSNAME Prefix :your.TRACJCLS

Unit :CART

Disp :CATLG

Retpd :3�

Blksize:327��

Date/Override Library :your.DATELIB

Auto-Commands Library :your.TRACMDS

History Dataset Name :your.JOBHIST


�

�

Archive DSNAME PrefixIndicates the 1-to-35-character high-level qualifier for CA-Jobtrac touse when generating the dynamically allocated archive DSN createdat each archival. This prefix is defined in member JOBTRAnn (seeChapter 4). You cannot change the prefix on the Library Definitionspanel.

For volume identification, the time and date are appended to the dataset name of the archive data set during allocation and can take up to12 additional characters, as shown in the following name:

DSN=your.prefix.Thhmm.Dmmdd

UnitDefines the archive unit name (UNIT=unitname).

The unit name is defined in member JOBTRAnn (see Chapter 4).You cannot change the unit name on the Library Definitions panel.



DispIndicates the normal data set disposition of the archive data set.

The default disposition is defined in member JOBTRAnn (seeChapter 4). You cannot change the default disposition on the LibraryDefinitions panel.

RetpdIndicates the retention period in days to be used for the archive dataset created by a 0ARCHIVE or 0SYSARCH task.

This value is also used to calculate the number of days to maintainan online copy of the sysout archive &INDEX entry. The &INDEXentry, available through the CA-Jobtrac/ISPF dialogs, lists all sysoutscaptured for the defined period, a brief run history, and the volumeon which they reside.

The retention period is defined in member JOBTRAnn (see Chapter4). You cannot change the retention period on the Library Definitionspanel.

BlksizeIndicates the archive data set block size, in a multiple of 150-byterecords (LRECL=150).

The block size is defined in member JOBTRAnn (see Chapter 4).You cannot change the block size on the Library Definitions panel.

Date/Override LibrarySpecify the name of the standard PDS (LRECL=88) that is to containcontrol keys and JCL images for date card insertion and selectablein-stream JCL parameters or SYSIN overrides.

This library is allocated during execution of the STAGE2 job stream.

This library is required for proper allocation of JMF (JCLManagement Facility) at CA-Jobtrac startup time. For moreinformation about JMF, see the CA-Jobtrac Extended SchedulingServices Guide.

If this DSN is not specified when the JOBTRAC task is started,CA-Jobtrac issues a TRAC669E DSN: message.



Auto-Commands LibraryIndicates the name of the standard PDS (LRECL=80) that containsmembers called command sets. Each command set consists of a listof related commands.

You can schedule execution of a command set or respond to someevent with a command set.

See the CA-Jobtrac Operator Guide for more information aboutoperator commands. See the CA-Jobtrac Extended SchedulingServices Guide for more information about command set scheduling.

History Dataset NameIndicates the name of the history file (information display only).

The INIT subtask provides the entry in this field. This subtask is runas part of normal startup processing. You cannot change this field onthe Library Definitions panel.

This library is allocated during execution of the STAGE2 job stream.


Copy the PRODDATE Member

Copy the PRODDATE MemberThe ADI (Automatic Date Insertion) feature uses the PRODDATEmember to automatically insert JCL date records and other repeatedrecords into your events. This is required for running the IVPADIjob later on in the IVP. For complete information about using ADI,see the CA-Jobtrac Extended Scheduling Services Guide.

ProcedureFollow the steps below to copy member PRODDATE from thecai.SAMPJCL to your DATELIB library member DATELIB:

1. Ensure that the CA-Jobtrac global options panels have beenupdated, particularly the Library Definitions panel, which definesthe date file to CA-Jobtrac. If global options or the JOBTRA00member have been updated, proceed to Step 2. If not, update theglobal options, and then exit and reenter CA-Jobtrac.

2. Issue the following command from the CA-Jobtrac primary panelto edit member PRODDATE in your DATELIB library:

DATES

3. Issue the ISPF copy command, and copy the cai.SAMPJCLmember PRODDATE.

4. Exit the edit panel using the END command or the END PF key.

Multiple ADI MembersYou can define additional automatic date insertion (ADI) members tosupplement your production DATELIB. This is useful when you havemultiple JCL libraries or when your users have limited access to JCLlibraries.

The additional members reside in your date insertion library and arespecified on separate ddnames in your JOBTRAC startup procedure.You must also add these ddnames to your TSO logon procedure orCLIST.

To add the members to the JOBTRAC startup procedure, use addname of DATELxxx, where xxx is the three-digit numeric locationID.


Copy the PRODDATE Member

SampleThe following figure shows sample JCL for additional ADI members:

//DATELIB DD DSN=YOUR.PROD.DATEFILE(PRODDATE),DISP=SHR <= FOR LOCATION ��

//DATEL��4 DD DSN=YOUR.PROD.DATEFILE(DATEL��4),DISP=SHR <= FOR LOCATION ��4


Copy the JMFSYM01 Member

|Copy the JMFSYM01 Member| The JMF (JCL Management Facility) feature uses the JMFSYM01| member to allow the centralization and control of variable JCL

information by eliminating daily updating of production JCL streams.This is required to be able to run the IVP later. For more informationabout using JMF, see the CA-Jobtrac Extended Scheduling ServicesGuide.

ProcedureFollow the steps below to copy member JMFSYM01 from thecai.SAMPJCL to your DATELIB library member JMFSYM01.

1. Ensure that the CA-Jobtrac global options panels have beenupdated from the previous step.

Copy the RESOURCE Member

Copy the RESOURCE MemberThe RESOURCE feature uses the resource conditions and assigns aone- or two-digit ID code to each definition by coding statements inthe RESOURCE member in your CA-Jobtrac PPOPTION library.(See the CA-Jobtrac Extended Scheduling Services Guide for moredetails.)

ProcedureFollow the steps below to copy member RESOURCE from thecai.SAMPJCL to your PPOPTION data set.

1. Issue the ISPF copy command, and copy the cai.SAMPJCLmember RESOURCE.

2. All statements in this member are samples and are comments.

3. Issue the following command from the CA-Jobtrac primary panelto edit member RESOURCE in your PPOPTION library:

PARMS RESOURCE



Copy the EXCLPARM Member

Copy the EXCLPARM MemberThe EXCLUDE PARAMETER feature lists the event names or eventprefixes that are grouped for mutual exclusion recognition in theEXCLPARM member in your CA-Jobtrac PPOPTION library. (Seethe CA-Jobtrac Extended Scheduling Services Guide for more details.)

ProcedureFollow the steps below to copy member EXCLPARM from thecai.SAMPJCL to your PPOPTION data set:

1. Issue the ISPF copy command, and copy the cai.SAMPJCLmember EXCLPARM.

2. All statements in this member are samples and are comments.

3. Issue the following command from the CA-Jobtrac primary panelto edit member EXCLPARM in your PPOPTION library:

PARMS EXCLPARM



Maintaining Table Modules

Maintaining Table ModulesSome of the tables used by CA-Jobtrac exist as load modules. Othertables exist as online tables. Load modules must be assembled andlinked as described here. The online tables are maintained using theonline table services described in the CA-Jobtrac ExtendedScheduling Services Guide.

The online table services are used to schedule events based on datasets closing, create automatic message replies, schedule systemcommands, and specify additional condition code checking forevents.

Assembler MembersIf you do not use SMP/E to maintain your table modules, use theassembly and link JCL provided in SAMPJCL. The table belownames the SAMPJCL member to use for each table module.

Use Member To Assemble Table Name

ASMAUTH TRACAUTH table TRACAUTH

ASMMSGT AutomaticMessageRecognition tablefor use at IPL time

IPLTABLE

ASMEXIT CA-Jobtrac userexits

N/A

ASMUCT CA-JCLTrac UserControl Table

GJC3TUCT

CA-JCLTrac User Control TableThe CA-JCLTrac User Control Table (GJC3TUCT) shipped withCA-Jobtrac does not have any entries in it. Some of the CA-JCLTracfunctions require entries in the table. Before assembling the table,make the necessary entries in it.

See “Setting Up a UCT” on page 5-60 for details about creating thenecessary entries.

Converting Existing Modules to Online TablesWith the exception of the AMR table named IPLTABLE, all existingAMR, ADR, and SCS modules are converted to online tables.IPLTABLE remains a load module.


Maintaining Table Modules

Using Your Security PackageTo use your security package, secure the use and function of thefollowing:

Secure thismodule

To control the ability to

GJTRTSIF Access the entire online table service.

GJTRTSTA Activate online tables.

GJTRTSMC Update or modify the command (SCS)tables.

GJTRTSMD Update or modify the automatic data setrecognition (ADR) tables.

GJTRTSMF Update or modify the condition code(CCPF) tables.

GJTRTSMM Update or modify the message (AMR)tables.

GJTRTSVC View the active SCS table.

GJTRTSVD View the active ADR table.

GJTRTSVF View the active CCPF table.

GJTRTSVM View the active AMR table.

GJTRTSVR Handle all submission tasks withinCA-Jobtrac.

GJTRMSTR Handle all table setup and job submissionsetup. Include calling subroutines.


Setting Up AMR Support

Setting Up AMR SupportTo use the AMR (Automatic Message Recognition) feature, you mustset up exit IEAVMXIT.

This is done by ensuring IEAVMXIT is present in yourSYS1.LINKLIB. If IEAVMXIT is not present, use memberLINKMXIT in the CA-Jobtrac SAMPJCL library to link it intoSYS1.LINKLIB.

All exits, including IEFBR14 dummies, should be linked as RENTand REUS. Exit IEAVMXIT is used and must be linked withAMODE 31.

Disabling AMR Support| While CA-Jobtrac is running, issuing any K M,UEXIT=Y/N or K

M,AMRF=Y/N command disables AMR support.

For information about reactivating AMR support, contact ComputerAssociates Technical Support. See the CA-Jobtrac Reports,Maintenance, and Recovery Guide for information about contactingComputer Associates Technical Support.


Creating IPLTABLE Entries (Optional)

Creating IPLTABLE Entries (Optional)This section describes how to create an IPLTABLE, which is anAutomatic Message Recognition table for use at IPL time. Unlikeother AMR tables, the IPLTABLE cannot be created using the onlinetable services as described in the CA-Jobtrac Extended SchedulingServices Guide. This section contains the following information:

■ Statements used to describe the table

■ Procedure used to create the table

■ Example of an IPLTABLE job

@AMRGEN Statement Syntax@AMRGEN statements are used to describe the IPLTABLE. The@AMRGEN END statement identifies the end of the @AMRGENstatements. The syntax of an @AMRGEN statement is as follows:

@AMRGEN 'msgtext[//]msgtextcont' [,option=value]

.

.

.

@AMRGEN END

Syntax Rules■ A space must separate @AMRGEN from the remainder of the

statement.

■ Commas separate remaining elements of the statement from eachother.

■ The statement must begin in column 10 of the record.

■ Any alphanumeric character in column 72 of a record indicates thatthe following record is a continuation record.

■ Continuation records must begin in column 16.

■ You can include any number of @AMRGEN statements in the jobmember.

■ The last statement in the job member must be an @AMRGENEND statement.



Description of an @AMRGEN StatementThe following are descriptions of the elements of an @AMRGENstatement:

Element Description

@AMRGEN Required keyword. Invokes the @AMRGEN assemblermacro to create an entry in the storage-resident AMRtable.

'msgtext[//]msgtextcont' Specifies a message ID, message text, or portion of themessage text that, when issued, triggers the defined event.Replace msgtext with a message ID, message text, orportion of the message text. The msgtext must be enclosedin single quote marks (').

// You can insert // (two forward slashes) in the messagetext to represent any portion of the message. For example,you want to automate a response to the message with IDIEF238D. The text accompanying this message ID canvary, and you want to respond only to the message thatincludes the text DEVICE NAME. You can specify'IEF238D//DEVICE NAME' as the message text to triggersome response.

Any message that begins with IEF238D and includesDEVICE NAME will trigger the specified event,regardless of the text between the message ID and the keytext. You can use this feature to scan a message for keytext without having to determine how many charactersfrom the beginning of the message the key text begins(see “MSGOFF” on page 5-49).

option=value Optional elements. Adds conditions to the definition.Specify one or more options per @AMRGEN statement.Specify only one value per option. See “Summary of@AMRGEN Options” on page 5-49 for a description ofeach option.

@AMRGEN END Required keywords. Specifies the end of the list of@AMRGEN statements in the job.



Summary of @AMRGEN OptionsThe following options are available for use in an @AMRGENstatement:

Option Value

MSGOFF= nn

SYSID= sysid

CJOB= createjob

TJOB= triggerjob

TOD= hhmm{hhmm}

PROCP= processpmm/dd/yy

CMD= 'syscmd'

CHGMSG= 'chgtext'

CHGOFF= nn

ACT= ARPSNCWX

MSGOFFSpecifies the offset (number of characters) from the beginning of themessage where the specified msgtext begins. Offset 00 is thebeginning of the message; offset 01 is the second character of themessage, and so on.

Use a two-digit number specifying the offset value. If you do notspecify this parameter, the default offset value 00 is assumed.

SYSIDSpecifies the system on which the specified action is to beperformed. Specify the ID of the system. If not specified, the event isperformed on all systems.



TJOBSpecifies the name of the job to be acted upon by the triggered event.

CJOBSpecifies the job that must issue the message or cause the message tobe issued. If the specified job does not issue or cause the message tobe issued, the defined event is not triggered. Specify the name of thejob that must issue or cause the message.

If CJOB is not included in the statement, any job, TSO session, orstarted system task can issue or cause the message.

TODSpecifies the time of day range during which the message must beissued. If the message is not issued during the specified time range,the event is not triggered. If no TOD= is specified, the message canappear at any time of day.

Use the form hhmm to specify a time of day, where hh is a two-digitnumber representing the hour (01-23) and mm is a two-digit numberrepresenting the minute of the hour (00-59).

If you specify TOD=hhmmhhmm, the message must be issuedbetween the time specified by the first hhmm and the time specifiedby the second hhmm. For example, TOD=01001100 specifies that themessage must be issued between 1 AM and 11 AM. You can specifytime ranges that cross over midnight (for example, TOD=22000300).

If only one hhmm is specified, it is used as the start of the timerange and 2359 is assigned as the end of the time range. Forexample, TOD=2030 is the same as TOD=20302359.

PROCPSpecifies a process period or date during which the specified messagemust be issued to trigger an event. For example, PROCP=MONDAYspecifies that the message must be issued on a Monday or no event istriggered.

Use any valid process period keyword (except UDEF). See theCA-Jobtrac Reference Summary.



You can specify a fixed date in the form mm/dd/yy, where mm is atwo-digit number representing a month (01-12), dd is a two-digitnumber representing a day of the month (01-31), and yy is atwo-digit number representing a year (00-99). For example, tospecify May 11, 2001, you would use PROCP=05/11/01.

You can replace any part of the date with ** to define a generic date.For example, PROCP=08/**/01 specifies any day during August,2001; PROCP=**/15/** specifies the 15th day of any month duringany year.

CMDSpecifies the system command or WTOR reply to be issued byCA-Jobtrac in response to the message specified by msgtext. Specifya command or WTOR reply. You must enclose the command orreply in single quote marks (').

If ACT=C is specified (see ACT= in “ACT” on page 5-52), thecommand or reply is issued as a standard command. If ACT=W isspecified, the command or reply is issued as a WTOR reply and isautomatically appended with the proper ID (for example, Rnn,syscmd, where nn is the number of the message to which thereply is being made).

You can specify an entry to schedule the command to be issued atthe time specified by the System Command Scheduling facility. Todo so, include this parameter as follows:

CMD='SCHD#nnn,syscmd'

The command specified by syscmd will be issued at the time definedby a System Command Scheduling statement with the parameter'SCHD#nnn'. See the CA-Jobtrac Extended Scheduling Services Guidefor more information about using System Command Scheduling withAutomatic Message Recognition.

CHGMSGSpecifies the text to be used in place of the original system messagetext. You can specify which part of the original message to replace(see “CHGOFF” on page 5-52). Specify the new message text. Youmust enclose the new text in single quote marks ('). No ACT=parameter is required for this action.



CHGOFFSpecifies the offset (number of characters) from the beginning of theoriginal system message where the new message text specified byCHGMSG= is to begin. Offset 00 is the beginning of the message;offset 01 is the second character of the message; and so on.

Specify a two-digit number specifying the offset value. If you do notspecify this parameter, the default offset value 00 is assumed.

ACTSpecifies the action to be triggered when the specified message isissued and any other conditions are satisfied. The following valuesare available:

Value Description

A Adds the trigger job to the current schedule witha manual dependency (dependency code M). Ifthe trigger job is already on the current schedule,no action is taken.

R Adds the trigger job to the current schedule withno dependencies. The trigger job is submittedimmediately. If the trigger job is already on thecurrent schedule, the manual dependency(dependency code M) is removed from the job.

P Purges the trigger job from the current schedule.The trigger job is removed from the currentschedule, and any successors are released frompredecessor dependency on the trigger job. If thetrigger job is not on the current schedule, noaction is taken.

S Suppresses the message from appearing on thesystem console.

N Makes the message nondeletable and highlights iton the console display.

C Issues the command specified by CMD=.

W Issues the WTOR reply specified by CMD=.

X Takes user exit TRACX04. Any reply isgenerated by the exit program. This exit is nolonger supported and may not work in futureversions.



ProcedureTo use the IPLTABLE and the VINIT3 procedure together, use thefollowing procedure:

1. Locate sample member IPLTABLE in your SAMPJCL library.This is the sample IPLTABLE, which you can use as a model.

2. Locate sample member ASMIPLT in your SAMPJCL library.Use this job to assemble and link IPLTABLE into yourCA-Jobtrac CAILIB library.

3. Run the job.

4. After you have successfully linked the IPLTABLE into yourCAILIB library, you may need to issue the following command:

F LLA,REFRESH

Your new IPLTABLE is now ready for use at IPL time.


Enabling the SPACE Command

Enabling the SPACE CommandUsers must add GJTRUCBS to the AUTHTSF, AUTHCMD, andAUTHPGM table in the IKJTSOxx member of yourSYS1.PARMLIB to enable the SPACE command.

Use the TSO PARMLIB command to update the TSO system values.


CA-Jobtrac CA-11 Integration

CA-Jobtrac CA-11 IntegrationThis topic describes the CA-Jobtrac and CA-11 changes needed toimplement a seamless interface between these two products. Thefeatures provided by this integration are:

■ Automatic insertion of the CA-11 U11RMS step during theCA-Jobtrac job submission. Insertion of the step can be controlledby job class. Step insertion parameters are retrieved from theCA-11 options table.

■ Integration of the CA-Jobtrac ISPF online with CA-11 to updatethe CA-11 database when CA-Jobtrac Delete (D) and Purge (P)commands are issued.

■ Integration of the CA-Jobtrac ISPF online to the CA-11 ISPFonline to display the CA-11 ISPF panels when a CA-Jobtrac Rerun(R) command is issued. The job name of the job selected inCA-Jobtrac is passed to the CA-11 online. CA-Jobtrac recognizeswhen the selected job is set up through the CA-11 online forrestart, and releases the job when you return to the CA-Jobtracpanels. Restart cancel or force complete actions for the selected jobare also detected by CA-Jobtrac.

Installation RequirementsNote: CA-11 Version 2.2 and Genlevel 9909 or higher are required.

The CA-Jobtrac PPOPTION initialization member (JOBTRAxx) mustbe updated to include the RERUN= and INSERTRMS= keywordsdescribed in “RERUN” on page 4-34 and “INSERTRMS” onpage 4-31.

To use the CA-11 ISPF restart panel from the CA-Jobtrac ISPFpanels, you must allocate the CA-11 libraries to your ISPF session.You can do this in one of two ways:

1. Add the CA-11 CAIISPM and CAIISPP to your ISPMLIB andISPPLIB allocations, respectively, in your TSO PROC or ISPFstartup CLIST. The TCLIST3 CLIST distributed in theSAMPJCL library is normally used with this configuration andmust be in a library defined to the SYSPROC DD of your ISPFsession.

2. Use the LIBDEF CLIST in the SAMPJCL library to allocatethese libraries dynamically. This CLIST must be in the librarydefined to the SYSPROC DD of your ISPF session.



In either case, the JTRCCA11 CLISTs must be copied fromSAMPJCL to a library defined to the SYSPROC DD of your ISPFsession.

If you specified the INDX11= keyword in the STAGE1 job, theCA-11 libraries were added to the LIBDEF and JTRCCA11 CLISTsthat were placed in the SAMPJCL data set. Otherwise, customizationof these CLISTs is required.

If you are planning to use the CA-11 step insertion, verify that theCA-11 options table (U11OPT) has appropriate values specified forthe INSRTPC and INSRTPM keywords. The values specified onthese keywords are used to build the inserted step JCL. Also, thekeyword INSRTOP should be set to NO if step insertion is to bedone only by CA-Jobtrac. See the CA-11 Systems Programmer Guidefor more information on the CA-11 Options Table.

The INCLUDE statement is used in execution JCL to specify thename of a PDS member which contains JCL statements that youwant included (inserted) at the position of the INCLUDE statement.The PDS member may contain any combination of controlstatements, JOBLIBs, DDs, PROCs, EXECs, SYSIN data, non-JCL,and so forth. When the job entry subsystem on the execution nodeconverts/interprets the JCL stream, the INCLUDE statement isremoved, and the JCL statements contained in the specified PDSmember are inserted in the JCL stream.

Products that interact with JCL PRIOR to the expansion of PROCsand/or INCLUDEs do not "see" the contents of the unexpandedmembers, and therefore cannot process them. This includes productssuch as CA-Jobtrac that are used to schedule job submission.Presubmission syntax checking, JCL validation, CA-11 step insertion,and other similar facilities are limited to the data available whenthese processes occur. For instance, a referback to JCL within aPROC cannot be adequately validated prior to the expansion of thePROC. In addition, insertion of the CA-11 RMS step as the firstexecutable job step may not be accurately done if an INCLUDEstatement is placed prior to the first EXEC statement. It dependsupon the contents of the PDS member that is included duringexpansion. If the included JCL statements contain one or more EXECstatements, then the CA-11 RMS control step is not physically thefirst step of the job.



Be aware that CA-11 does not process JCL statements that are placedbefore the CA-11 RMS control step. Fortunately, CA-Jobtracimplements the automatic CA-11 RMS step insertion feature as anoption. With this option turned on, CA-Jobtrac searches the JCL forthe first EXEC or PROC statement and inserts the RMS step prior tothat statement. CA-Jobtrac also checks to see if a CA-11 RMS stepis already present. If it is, the insertion does not take place. AnyINCLUDE statement prior to the first EXEC or PROC statement isignored, and the RMS step is inserted after the INCLUDE statement.If this would result in the CA-11 RMS control step NOT beinginserted as the first EXEC in the job (that is, because the INCLUDEdJCL contains one or more EXEC statements), you should hard-codethe RMS step in the appropriate location to ensure that it will be thefirst EXEC even after INCLUDE statements are expanded.

CA-Jobtrac now inserts the CA-11 RMS control step prior to anyINCLUDE statement positioned before the first EXEC statement.This was done to ensure that the CA-11 RMS step was the firstEXEC statement in the job. However, subsequent client feedbackwith this approach and the intent of Computer Associates to maintainconsistency across mainframe scheduling products allow CA-Jobtracto perform CA-11 RMS step insertion as it did previously in Version3.4.


Setting Up CA-JCLTrac

Setting Up CA-JCLTracCA-JCLTrac is the JCL analysis component of CA-Jobtrac.

CA-JCLTrac uses the operating system's own JCL C/I routines toperform syntax analysis, create records that you can load into DB2tables, and generate cross-reference reports.

To use CA-JCLTrac, complete the following:

■ Set up a UCT, User Control Table, (optional)

■ Set up DB2 tables (optional)

■ Enable CA-JCLTrac

Setting Up a UCTA UCT (User Control Table) provides control information for thedynamic allocation of the JCL and procedure libraries. Itaccomplishes the following:

■ Associates a CA-Jobtrac location with a JCL library

■ Identifies nonstandard ddnames in your JES started task

■ Matches a job class with its JES PROCLIB concatenation

Note: You are not required to build a UCT. The default tables areusually sufficient.

For details about setting up a UCT, see “Setting Up a UCT” onpage 5-60.

Setting Up DB2 TablesYou can use the CA-JCLTrac feature of CA-Jobtrac to extract JCLinformation and store it in DB2 tables. The information can then beused to create reports about your JCL.

If you plan to use CA-JCLTrac for this purpose, complete thissection to set up the DB2 tables.

The list below outlines the steps you must take to set up the DB2database. The following pages explain the steps in detail.

1. Create the DB2 objects (see “Creating the DB2 Objects” onpage 5-65)

2. Bind the DB2 plans (see “Binding the DB2 Plans” on page 5-67)

3. Grant access and select authority (see “Granting Authority” onpage 5-68)



Enabling CA-JCLTracTo enable CA-JCLTrac, add GJC3MCII to the AUTHTSF,AUTHCMD, and AUTHPGM table in the IKJTSOxx member ofyour SYS1.PARMLIB.

Use the TSO PARMLIB command to update the TSO system values.

Enabling Automatic JCL CheckingAutomatic JCL checking requires the use of the JCLAUTO macro.This macro is installed with CA-Jobtrac as a CLIST in theCA-Jobtrac CAICLIB library.

What is JCLAUTO?JCLAUTO is an edit macro that redefines the END and SAVEISPF/PDF edit commands. JCLAUTO changes the commands toinvoke the CA-JCLTrac JCL Analyzer prior to saving the memberyou are editing.

If a JCL error is found, the JCL is not saved, and a CA-JCLTracmessage is issued. For more information about CA-JCLTrac, see theCA-Jobtrac Extended Scheduling Services Guide.

Invoking JCLAUTOJCLAUTO is invoked in one of the following ways:

■ Through the use of the CA-Jobtrac TRACX29 user exit (see thesample in SAMPJCL)

■ Making it the initial macro for a user's edit session. This isaccomplished with the IMACRO edit command (see the IBMmanual ISPF/PDF Edit and Edit Macros).

■ Executing it while in an edit session

Disabling Syntax CheckingOnce JCLAUTO is invoked, it remains in effect for the duration ofthe edit session. If you want to disable syntax checking, execute thefollowing command:

JCLAUTO OFF



Setting Up a UCT

A UCT (User Control Table) provides control information. Itaccomplishes the following:

■ Associates a CA-Jobtrac location with a JCL library

■ Identifies nonstandard ddnames

■ Matches a JCL job class with its JES PROCLIB concatenation

When a UCT is RequiredA UCT is required when you:

■ Request dynamic allocation of JCL libraries (DYNAMJ keywordwith TYPRUN(JCLSCAN) or TYPRUN(EXTRACT))

■ Request dynamic allocation of procedure libraries (DYNAMDkeyword) and use nonstandard PROCLIB ddnames in your JESstarted task

■ Use different JES PROCLIB concatenations for different jobclasses

Setting Up a UCTYou create entries in a UCT with the @JCLUCT macro and itsstatements. The following are the @JCLUCT statements:

■ CLASS

■ DSNAME

■ DDNAME

■ END

Syntax UsedThe following sections show the syntax of the @JCLUCT statements.The following rules apply to the syntax:

■ Italics are used to denote a variable. Replace the variable with theindicated information.

■ Lowercase letters denote optional portions of literals. You do nothave to include them. For example, for DSName, you only have touse DSN in the statement.

■ [Brackets] indicate an option. You do not have to include in thestatement what is shown in brackets.

■ Punctuation that is shown must be used.



How to Set Up and Use a UCTBy default, a UCT is always used. The default name is GJC3TUCT.If you want to use a UCT with a different name, use the UCTkeyword.

Take the following steps to create and use a UCT:

1. Decide if you need to create a UCT. (Usually, you will need touse one.) If you need to create a UCT, continue with thefollowing steps. See “Setting Up a UCT” on page 5-60.

2. Create entries in a UCT using the @JCLUCT statements. See“CLASS Statement” on page 5-62 through “@JCLUCT MacroExamples” on page 5-64.

3. Compile the UCT using the member ASMUCT in yourSAMPJCL library.

4. Include the UCT keyword in your JCL to:

■ Explicitly specify the use of the GJC3TUCT UCT (this table isused if you do not include the UCT keyword)

■ Specify a UCT named something other than GJC3TUCT

For information about the UCT keyword, see the CA-JCLTracchapter in the CA-Jobtrac Extended Scheduling Services Guide.



CLASS StatementCLASS statements match a job class with its JES PROCLIBconcatenation. Specify up to 35 class statements. CLASS statementshave the following syntax:

[name] @JCLUCT CLASS,jobclass,ddname

Parameter Explanation

name Assigns a CSECT name to the UCT. It mustappear on the first @JCLUCT macro only.

The default is GJC3TUCT.

@JCLUCT Identifies this line as a @JCLUCT statement.

CLASS Required literal. Defines this statement as aCLASS definition.

jobclass Specifies the job class. Use 0-9 or A-Z.Define a job class once only.

ddname Specifies the ddname of the JES PROCLIBconcatenation used by the job class.

For omitted job classes, the default ddname is

■ PROC00 for JES2

■ IATPLBST for JES3

DSNAME StatementDSNAME statements associate CA-Jobtrac location IDs with JCLlibraries. Specify as many DSNAME statements as necessary.DSNAME statements have the following syntax:

name @JCLUCT DSName,locid,dsname[,SEQ=nnn]


name Assigns a CSECT name to a UCT. It mustappear on the first @JCLUCT macro only.


@JCLUCT Identifies this line as a @JCLUCTstatement.




DSName Required literal. Defines this statement as aDSNAME definition.

locid Specifies the location ID. Use any numberfrom 0 to 255. A location ID may bedefined only once.

dsname Specifies the name of the JCL libraryassociated with the specified location ID.Specify a valid data set name.

SEQ=nnn Defines multiple libraries to a location.Replace nnn with any number from 0 to255, the default is 1. The sequence numberdetermines the order in which the librariesappear in the input concatenation.

DDNAME EntriesIf your JES started task contains nonstandard PROCLIB ddnames,DDNAME statements are required. Use as many DDNAMEstatements as necessary.

For JES2, CA-JCLTrac dynamically allocates all ddnames that startwith PROC. DD statements are required only if your JES2 startedtask contains ddnames other than PROCxx.

For JES3, CA-JCLTrac dynamically allocates all ddnames that startwith IATPLB. DDNAME statements are required if your JES3started task contains ddnames other than IATPLBxx.

DDNAME statements have the following syntax:

name @JCLUCT DDName,ddname








DDName Required literal. Defines this statement as aDDNAME definition.

ddname Specifies the nonstandard procedure libraryddname to be allocated. Specify a validddname.

END StatementThe END statement terminates the @JCLUCT macro, marking theend of a UCT. Use only one END statement. It must be the laststatement in the table.

The END statement has the following syntax:

name @JCLUCT END





END Required literal. Defines this statement as atermination statement.

@JCLUCT Macro ExamplesYou can find examples of the @JCLUCT macro in the followingmembers in your SAMPJCL library:

■ GJC3TUC2-JES2 example

■ GJC3TUC3-JES3 example



Creating the DB2 Objects

This step creates the DB2 objects used to store the CA-JCLTrac data.The DDL that does this is in the JCLQDDL member of yourSAMPJCL library. This code requires editing before running.

Required EditingIn the JCLQDDL member, there are symbolics for values you mustprovide. These symbolics begin with a question mark. For example,?TSSGNME, so that they are easy to find. The following tableexplains the values you must add to the JCLQDDL member:

Symbolic Explanation

?TSSGNME The name of the STORAGE GROUP to beused for the CA-JCLTrac tablespace. Ifthis storage group already exists, removethe CREATE STOGROUP DDL statementfrom the JCLQDDL member.

?TSVOLID The DASD volume to be used by theCA-JCLTrac tablespace storage group. Ifthis storage group is not being created, thisparameter is not relevant.

?TSVCAT The volume catalog to be used by theCA-JCLTrac tablespace storage group. Ifthis storage group is not being created, thisparameter is not relevant.

?TSBPOOL The DB2 buffer pool to be used by theCA-JCLTrac tablespace.

?TSQPRI The PRIQTY value used by theCA-JCLTrac tablespace.

?TSQSEC The SECQTY value used by theCA-JCLTrac tablespace.

?IXSGNME The name of the storage group to be usedfor CA-JCLTrac indexes. If this storagegroup already exists, remove the CREATESTOGROUP DDL statement from theJCLQDDL members.




?IXVOLID The DASD volume to be used by theCA-JCLTrac index storage group. If thisstorage group is not being created, thisparameter is not relevant.

?IXVCAT The volume catalog to be used by theCA-JCLTrac index storage group. If thisstorage group is not being created, thisparameter is not relevant.

?IXBPOOL The DB2 buffer pool to be used by theCA-JCLTrac indexes.

?IXQPRI The PRIQTY value used by theCA-JCLTrac indexes.

?IXQSEC The SECQTY value used by theCA-JCLTrac indexes.

?DBNAME The name of the CA-JCLTrac database. Ifthe specified database already exists,remove the CREATE DATABASE DDLstatement from the JCLQDDL member.

?CREATOR The authorization ID that will become thehigh-level name of the CA-JCLTrac tablesand indexes.

Optional EditingAfter you have changed the symbolics, further editing may berequired. If the CA-JCLTrac tables are going to use an existingdatabase, remove the CREATE DATABASE DDL statements fromthe JCLQDDL member.

Procedure to Create the ObjectsUsing the ISPF editor, change each symbolic to a valid DB2 name orparameter value.

After you edit and save the JCLQDDL member, run it in SPUFI,DSNTEP2, or an equivalent program.

If you are going to create the database and storage groups, you willneed the following authority on the target DB2 subsystem:

■ CREATEDBA—create database

■ CREATESG—create storage group



If you are using an existing database and storage groups, you needthe following authority on the target DB2 subsystem:

■ CREATETS—create new tablespace

■ CREATETAB—create new table

The DB2 subsystem in which the tables are created is theCA-JCLTrac home subsystem.

Binding the DB2 Plans

This step binds the DB2 plans. CA-JCLTrac uses the followingplans:

■ GJC3TDB2—The Update plan. CA-JCLTrac uses this plan toinsert and delete data in the DB2 tables.

■ GJC3X*—The Report plans. There are 18 plans. Each plan's namestarts with GJC3X. CA-JCLTrac uses these plans to extract datafor the cross-reference reports.

■ GJC3TSPF—The Dialog Manager plan. CA-JCLTrac uses this planfor the online DB2 reports.

The JCL used to bind the plans is in the JCLBIND member in yourSAMPJCL library.

Required ChangesIn the JCLBIND member, there are symbolics for values you mustprovide. These symbolics begin with a question mark so they areeasy to find. For example, ?JOBCARD. The following tabledescribes the values you must add to the JCLBIND member:


?STEPLIB The name of your DB2 load library.

?DB2ID The name of the DB2 system that runsCA-JCLTrac.

?CREATOR The authorization ID that is the high-levelname of the CA-JCLTrac tables andindexes. This should match the ID used inthe JCLQDDL job. For the bind to work,the ID must have BINDADD authority.



Procedure to Bind the PlansUsing the ISPF editor, change each symbolic.

After you edit and save the JCLBIND member, submit the job tobind the plans.

Granting Authority

Various authorities must be granted to use the CA-JCLTrac plans andtables. This section explains what those authorities are and how togrant them.

Granting Authority to Create ReportsTo use the CA-JCLTrac report plans to create reports, you must grantexecute and select authority to the appropriate users. Select authorityis necessary because the report plans use dynamic SQL. The SQLstatements used to grant execute and select authority are in theJCLQRPT member in your SAMPJCL library.

In the SQL are the symbolics ?AUTHID and ?CREATOR. ?AUTHIDis the ID of the person receiving the authority. If you intend to grantgeneral access to the CA-JCLTrac tables, use an ID of PUBLIC.?CREATOR is the authorization ID that is the high-level name of theCA-JCLTrac tables. Using the ISPF editor, replace the symbolicswith valid authorization IDs.

After you edit and save the JCLQRPT member, run it in SPUFI,DSNTEP2, or an equivalent program.

Granting Authority to Update and Load TablesTo update and load the CA-JCLTrac tables, you must grant executeand load authority to the appropriate users. The SQL statements usedto grant execute and load authority are in the JCLQUPD member inyour SAMPJCL library.

In the SQL are the symbolics ?DBNAME and ?AUTHID. ?AUTHIDis the ID of the person receiving the authority. ?DBNAME is thename of the database for which authority is being granted. Using theISPF editor, replace the symbolics with a valid database name andauthorization ID.

After you edit and save the JCLQUPD member, run it in SPUFI,DSNTEP2, or an equivalent program.


Using Other Sysout Capture Products

Using Other Sysout Capture ProductsIf you already have a sysout capture product of another kind, you candirect CA-Jobtrac to requeue each listing to the other product as itcaptures the copy for on-schedule viewing.

See the description in “Requeue Class” on page 5-33 in “Options onthe Sysout Capture Options Panel” on page 5-31 for moreinformation about requeueing sysouts.

About the CA-View InterfaceCA-Jobtrac can interface with the Computer Associates CA-Viewproduct, Version 6.0 and higher.

To use the CA-View interface, you must be able to run CA-Viewfrom ISPF. This means that the CA-View load libraries must beeither in a LNKLSTnn library or in a library named in the STEPLIBDD statement of the user's logon procedure. The CA-View panelsmust be accessible. See the CA-View installation manual for moreinformation.

Accessing CA-View in CA-JobtracThe first time you use the 0 (zero) line command or the CA-Viewprimary command, CA-Jobtrac prompts you for the high-level nameof a CA-View database. When you respond, CA-Jobtrac saves thename in your CA-Jobtrac user profile. The next time you issue a 0line command or CA-View primary command, CA-Jobtrac uses thehigh-level name that it saved to determine which database to access.For more information about these commands, see the CA-JobtracOperator Guide.


Using Other Sysout Capture Products

Enabling the CA-View InterfaceTo enable the CA-View feature, take the following steps:

1. Format a capture file. We recommend 5 cylinders (the minimum).

2. Specify N for the Capture Sysout field on the CA-Jobtrac GlobalOptions panel. This tells CA-Jobtrac to bypass sysout capture andto route it to the CA-View output class.

3. Specify a class that doesn't get held (A, for example) for theOutput Capture Class 1 field on the Sysout Capture Optionspanel. This tells CA-Jobtrac not to hold any sysout.

4. Specify a number of days to keep schedule captures in the RetDays/Vers field on the Sysout Capture Options panel. This tellsCA-Jobtrac to save schedule captures for the specified number ofdays.

5. Specify whatever you want for the remaining fields in the firstcapture class definition (class 1). CA-Jobtrac uses this primarydefinition for schedule captures, and it must be defined.

See “Setting Global Options” on page 5-19 for more informationabout the CA-Jobtrac Global Options and Sysout Capture Optionspanels.


Customizing CA-Jobtrac WorkStation Server

Customizing CA-Jobtrac WorkStation ServerIf you are planning to use CA-Jobtrac WorkStation, you must makethe following changes to the CAIENF server for CA-Jobtrac to beaccessible. This section only describes the changes needed forCA-Jobtrac. If you have not installed the CA-Jobtrac WorkStation,you should do so before continuing with this step. For information onsetting up CAIENF and the server task, see the "Configure theMainframe" chapter of the CA-Jobtrac WorkStation Getting Startedguide.

CA-Jobtrac WorkStation requires that CA-Jobtrac usesDYNAMLOC. It is described earlier in this guide.

ProcedureThe CA-Jobtrac API used by CA-Jobtrac WorkStation requires thefollowing changes be made to the server task started by CAIENF.

1. You must add the following DD statements to the server PROC:

//JOBHISTx DD DISP=SHR,DSN=your.JOBHIST.dataset

//SYSPRTFC DD SYSOUT=�

//WORK DD DISP=(,DELETE,DELETE),SPACE=(TRK,(15,5)),

// DCB=(LRECL=8�,RECFM=FB,BLKSIZE=2�96�),UNIT=SYSDA

On the JOBHISTx DD specify the jobtrac token as the value for'x' and specify the name of your history data set.

Note: If you do not have your CA-Jobtrac CAILIB data set inLINKLST you must concatenate the CAILIB data setwith the //STEPLIB DD statement.

2. You must add the following variables to the CACCENV memberof your profile data set (ddname PROFILE in the server PROCJCL).

JTFDSNHL=PUBLIC.TEST High-level qualifier (HLQ) forforecast data set. The server dynamicallyallocates and catalogs a temporary dataset, when forecasting is requested by theworkstation. This should be a HLQwhich is defined to your DASDmanagement package as temporary, sothat it will be cleaned up in the eventthat a server failure occurs and the dataset is not deleted.


Customizing CA-Jobtrac WorkStation Server

JTFCYLS=x Size of temporary forecast data set incylinders. This should be the size ofyour current production checkpoint file.

JTFUNIT=SYSDA Unit for temporary forecast data set.Computer Associates recommends that atemporary work device be used.

JTFVOL=vvvvvvv Volser for temporary forecast data set.This is optional. The data set will beallocated to a pack defined to the genericunit if not specified.

JTTOKEN=x Token to indicate CA-Jobtrac to connectto (JOBTRACx).

Note: The CA-Jobtrac location specific data sets(TRACJxxx,TRACSxxx, and so on) are accessed by theserver through dynamic allocation. This requires that theCA-Jobtrac location specific data sets be defined toCA-Jobtrac using the DYNAMLOC member in PPOPTION,rather than through DD statements in the CA-Jobtracprocedure. See “Defining Location Information(DYNAMLOC) and Initiation IMODs” on page 5-12 forfurther information on DYNAMLOC.


CA-Jobtrac Cross-Platform Scheduling

CA-Jobtrac Cross-Platform SchedulingIf you plan to implement the remote scheduling to Unicenter TNG orCA-Jobtrac Agent, the following are required:

■ CA-GSS Version 2.8 0010 Service Pack 2 or higher.

■ CA-XPS 1.0 9909 or higher.

■ Unicenter TNG Framework for OS/390 1.0 or higher must beinstalled.

■ CAICCI must be configured with a TCPIPGW protocol TCP/IPgateway. See the Unicenter TNG Framework for OS/390Administrator Guide for syntax and additional information. Asample CAICCI configuration file might look like:

SYSID(localname)

PROTOCOL(TCPIPGW)

NODE(TCPIPGW,ip-address:port,retry,remotename) - optional

CONNECT(remotename) - optional

■ TCP/IP must exist on one of the OS/390 systems to communicatewith the remote platform (such as UNIX). CAICCI can route workthroughout your SNA network to reach other OS/390 systems.

■ If you plan to implement remote scheduling to CA-Jobtrac fromUnicenter TNG or CA-Jobtrac Agent, the following is alsorequired:

– CAIENF must be installed. CAIENF must be active for status tobe returned to Unicenter TNG. CA-XPS DCM(CAL2DCM2)must be installed into the CAIENF database.

– CA-XPS must be installed. For more information, see theUnicenter TNG Framework for OS/390 Administrator Guide.



ProcedureThe following steps are required to implement cross-platformscheduling:

1. CAICCI must be configured with a TCPIPGW protocol TCP/IPgateway. See the Unicenter TNG Framework for OS/390Administrator Guide for syntax and information.

2. Allocate the tracking checkpoint by running the job in theALCUNICK member of SAMPJCL (required).

This DD MUST be added to the CA-GSS PROC on theCHKPOINT ddname in a following step.

3. Add the statements from the PPOPTION member JOBTRAC tothe CA-GSS PPOPTION member JOBTRAC.

See “Global Variables for Cross-Platform Scheduling” onpage 5-77.

4. Edit the CA-GSS PROC (YS28GSSA) and add the following DDstatement:

//CHKPOINT DD DISP=SHR,DSN=your.unijtckp <-specify

5. Allocate remote platform security location data set (optional).

A location data set (TRACRnnn) can optionally be defined toCA-Jobtrac to contain user ID, domain, and password informationthat is used when submitting events to Unicenter TNG on remotesystems. A remote password data set may be defined for eachlocation.

The members contained in this data set are encrypted to preventbrowsing. The members are created and updated through thePASSWORD command that is available from the CA-JobtracISPF facility. The data sets can be allocated using the followingJCL or what is in SAMPJCL member STAGE2.

//name JOB

//STEP1 EXEC PGM=IEFBR14

//TRACR DD DSN==your.TRACR ,DISP=(,CATLG),

//DCB=(LRECL=8 ,BLKSIZE=8 ,RECFM=FB),SPACE=(TRK,(15,15,1 ))

//UNIT=uuuuu,VOL=vvvvv



Once allocated, you must add the data set to the DYNAMLOCPPOPTION member. Use the REFRESHLOC operator commandto add the data set without restarting CA-Jobtrac. REFRESHLOCis described in the CA-Jobtrac Operator Guide. DYNAMLOCallocation is described in “Defining Location Information(DYNAMLOC) and Initiation IMODs” on page 5-12.

Note: The same password data set may be used by multiplelocations, but multiple password data sets cannot beconcatenated to a single TRACRnnn ddname.

See the PASSWORD ISPF online command in the CA-JobtracOperator Guide for information on updating this data set. See“REMTCRED” on page 4-34 for information on optionalmember name processing.

6. Password requirements rules file (optional).

For cross-platform work being routed to CA-Jobtrac from otherplatforms, an optional table is available to specify the passwordrequirements for the sending system. This allows for systems tobe identified as "trusted" or "untrusted" systems. This table canreside in any 80-character LRECL data set and may be a memberof a PDS. The data set is referenced, as is shown below, byddname XPSPSWD in the CA-GSS PROC. This table isdescribed in “Cross-Platform Server ($UNIXPSJT) PasswordRequirements Table” on page 5-82.

//XPSPSWD DD DISP=SHR,DSN=CAI.XPSPSWD

You are asked in the following step to specify a data set for theXPSPSWD DD. If you decide not to use this table, the file canbe specified as:

//XPSPSWD DD DUMMY

This disables password requirement checking.

7. Shut down and restart CA-GSS to pick up the new CHKPOINTDD.

8. Shut down and restart CA-Jobtrac to pick up the new DDs.



CA-GSS Server IMODs

The following describes server IMODs used by cross-platformscheduling.

$UNITRKJT service and $UNI_TRACK IMOD. Remote executionstatus tracker. This server handles receiving the status for commandsthat have been sent to Unicenter TNG for execution by CA-Jobtrac.

$UNIXPSJT service and $UNI_REMOTE IMOD cross-platformserver. This server handles both receiving request and return status toUnicenter TNG for requests sent from TNG to CA-Jobtrac. This taskis described in “Cross-Platform Server ($UNIXPSJT) PasswordRequirements Table” on page 5-82.

$UNIRCVJT service $UNI_RECEIVE IMOD Command driver. Thisserver preprocesses commands, and next starts an IMOD to updateCA-Jobtrac with the request.

CA-Jobtrac starts these services during initialization if the&UNI.$JT2UNI and &UNI.$UNI2JT globals are set to a Y value.These globals are described later in this chapter. CA-Jobtrac invokesIMOD $UNIJT_INIT at startup to check the status of the serverIMODs and define and start the IMODs as needed. You can executethis IMOD manually using the CA-GSS SCHEDULE operatorcommand or GSSEDIT to start these service IMODs. You can alsocontrol these tasks using CA-GSS operator commands.

Some of the CA-GSS commands of interest include:

■ To display defined servers:

F GSSA,SERVER DISPLAY

■ To display all active IMODs (including servers):

F GSSA,DISPLAY ACTIVE

■ To stop a server IMOD with the service name $UNITRKJT:

F GSSA,SERVER STOP $UNITRKJT

■ To start a server IMOD with the service name $UNITRKJT:

F GSSA,SERVER START $UNITRKJT

■ To run the $UNIJT_INIT IMOD:

F GSSA,SCHEDULE $UNIJT_INIT



Global Variables for Cross-Platform Scheduling

This topic describes the CA-GSS globals that are used with thecross-platform scheduling server IMODs.

Server IMOD Selection Globals

GLOBVAL &UNI.$UNI2JT /Y/

This global controls the starting of the server IMODs that are usedfor Unicenter TNG to CA-Jobtrac scheduling. If Y is specified as thevalue, the IMOD services $UNIXPSJT and $UNIRCVJT are startedwhenever CA-Jobtrac is started or the $UNIJT_INIT IMOD isexecuted. Any value other than Y prevents the server IMOD fromstarting.

GLOBVAL &UNI.$JT2UNI /Y/

This global controls the starting of the server IMODs that are usedfor CA-Jobtrac to Unicenter TNG scheduling. If Y is specified as thevalue, the IMOD service $UNITRKJT is started wheneverCA-Jobtrac is started, or the $UNIJT_INIT IMOD is executed. Anyvalue other than Y prevents the server IMOD from starting.

Status Tracking Server Globals (Service $UNITRKJT)

GLOBVAL &UNI.$UNITRKJT.MON /JOBTRAC/

Specifies the monitor name to be used to identify CA-Jobtrac whenrequests are received from Unicenter TNG. If multiple ComputerAssociates scheduling products are installed and CA-Jobtrac is notthe primary receiver of requests, this differs from&UNI.$UNIXPSJT.MON described below. A monitor name can bespecified in the File field using the MONITOR keyword followingthe job name when a job is being scheduled from Unicenter TNG.See Defining Events to Unicenter TNG in the CA-Jobtrac ExtendedScheduling Services Guide for more information. In most cases, thevalue of JOBTRAC is appropriate.

This global is required.



GLOBVAL &UNI.$UNITRKJT.IMOD /$JOBT_REMTTRACK/

Specifies the IMOD to invoke when status information is receivedfrom Unicenter TNG. This value must be specified with the value of$JOBT_REMTTRACK and should not be changed.


GLOBVAL &UNI.$UNITRKJT.SCAN /15/

The number of seconds that is to be used as a time interval betweencontrolled services. These services include testing for operatorshutdown requests, physical updates to the checkpoint file that isbeing updated at all times in memory, and querying Unicenter TNGremote locations for job completion statistics. This value may rangefrom 01 to 60. If this value is not supplied, a default of 15 secondsis used.

GLOBVAL &UNI.$UNITRKJT.EXTTABLE/dataset.name/

Specifies the name of a sequential data set or the member name of aPDS in which the external events are defined.

This global is optional.

GLOBVAL &UNI.$UNITRKJT.DEBUG /DEBUG/

Enables debug for this task. If this global is set to the value DEBUG,this task logs information on processing to DDs DEBUGTRK andSNAPTRK. If these DDs are not present in the GSS PROC, settingthis global has no effect. We recommend that debug only be turnedon at the request of Computer Associates Technical Support since thevolume of debug information can be large.



Command Driver Globals (Service $UNIRCVJT)

GLOBVAL &UNI.$UNIRCVJT.MON /JOBTRAC/



GLOBVAL &UNI.$UNIRCVJT.IMOD /$JOBT_REMTCMD/

Specifies the IMOD that is invoked when a request from UnicenterTNG is received. This value must be specified as is.


GLOBVAL &UNI.$UNIRCVJT.SCAN /15/

Specifies the number of seconds that is to be used as a time intervalbetween controlled services. These services include testing foroperator shutdown requests. This value may range from 01 to 60. Ifthis value is not supplied, a default of 15 seconds is used.

GLOBVAL &UNI.$UNIRCVJT.DEBUG /DEBUG/

Enables debug for this task. If this global is set to the value DEBUG,this task logs information on processing to DDs DEBUGRCV andSNAPRCV. If these DDs are not present in the GSS PROC, settingthis global has no effect. We recommend that debug only be turnedon at the request of Computer Associates Technical Support since thevolume of debug information can be large.



Cross-Platform Server Globals (Service $UNIXPSJT)

GLOBVAL &UNI.$UNIXPSJT.MON /JOBTRAC/



GLOBVAL &UNI.$UNIXPSJT.SCAN /15/

Specifies the number of seconds that is to be used as a time intervalbetween controlled services. These services include testing foroperator shutdown requests, physical updates to the checkpoint filethat is being updated at all times in memory, and querying UnicenterTNG remote locations. This value may range from 01 to 60. If thisvalue is not supplied, a default of 15 seconds is used.

GLOBVAL &UNI.$UNIXPSJT.DEBUG /pc/

Sets current Print (p) and Console (c) trace code settings for thistask. The Print trace code controls both print and snap output. TheConsole trace code controls what WTOs are issued to the OS/390console. The print and snap DDs are defined in the GSS PROC asXPSPRINT and XPSSNAP.



Valid trace code values are:

0 Do not issue any trace WTOs. This value is onlyhonored for the Console trace code. If entered for thePrint trace code, it is interpreted the same as a code of 1.

1 Normal messages/WTOs. These messages indicate XPSsystem startup and shutdown. They also indicate whencommunication with remote systems is first establishedand if such communication is lost.

2 Communication messages/WTOs. In addition to themessages issued for trace code 1, messages relating toCCI communications with other systems are issued. Also,if the snap DD is available, snap dumps are taken of thestorage areas related to CCI control blocks and records.

3 Feedback messages/WTOs. In addition to the messagesissued for trace code 2, messages relating to XPSCAIENF feedback events are issued. Also, if the XPSsnap DD is available, snap dumps are taken of thestorage areas related to CAIENF control blocks andfeedback records in addition to the communication areasnaps.

4 Program path messages/WTOs. In addition to themessages issued for trace code 3, messages relating tointernal XPS processing are issued. Also, if the XPS snapDD is available, snap dumps are taken of the storageareas related to XPS control blocks in addition to thecommunication and feedback related snaps.

Note: Trace code 4 should only be used at the directionof Computer Associates Technical Support sinceit produces a significant number of messages.

5-9 Currently, trace codes 5 through 9 do not have specificdefinitions. If entered, they are interpreted the same astrace code 4.



Cross-Platform Server ($UNIXPSJT) PasswordRequirements Table

The password requirement rules for the cross-platform server onOS/390 define when a password must accompany an explicit user IDin a cross-platform request. Using this table you can discriminatebetween trusted and non-trusted systems when receiving requests.That is, if you are confident that requests from a given system havealready gone through security checks to ensure that the user IDpassed with the request should be honored, you can specify a rule sothat the cross-platform server will accept the user ID without apassword. For other systems which are not 'trusted' you can writerules so that any request from them which contains a user ID mustalso carry a password that can be validated by the cross-platformserver. Requests received from these systems which have a user IDbut no password will be automatically rejected.

Password Requirement Rules are defined in a data set pointed to bythe XPSPSWD DD statement in the GSS PROC. This data set is asequential file consisting of fixed 80-byte records (physical sequentialor a member of a PDS). The records can be blocked or unblocked. Ifthe XPSPSWD DD statement is not present, or contains no validrules, the default processing is to accept all requests without checkingfor the presence of passwords.

When the cross-platform server goes through initialization processing,it attempts to locate and parse the Password Requirement Rules. Iffound, these rules are stored in an in-storage table that is accessedduring normal processing. Changes made to the rules do not takeeffect until the server is reinitialized. See “CA-GSS Server IMODs”on page 5-76 for information on stopping and starting CA-GSSserver IMODs.

Syntax Rules

■ Lines beginning with a blank or an asterisk (*) are consideredcomment lines.

■ Each individual rule must be contained on a single line betweencolumns 1 through 71. Continuation lines are not supported.

■ The rule definition consists of a series of keywords/valuesbeginning in column 1, separated by commas with no embeddedblanks.



Keywords

NODE=caicci-node-nameThis keyword identifies the one- to eight-character CAICCI Nodename that a Cross-Platform request can be received from. It mustbe specified as a specific name or an asterisk (*), whichindicates all nodes. If not specified, the default is NODE=*,indicating all nodes.

MONITOR=monitor-nameThis keyword identifies the seven-character scheduling systemmonitor name that a Cross-Platform request can be receivedfrom. It must be specified as a specific name or an asterisk (*),which indicates all monitor names. In cases where a given nodemay have multiple scheduling systems (such as production andtest copies of CA-Jobtrac), the NODE and MONITORcombination will uniquely identify a specific scheduling system.If not specified, the default is MONITOR=*, indicating allmonitor names.

ID=user-idThis keyword identifies the one- to eight-character user ID thatmay be passed with a Cross-Platform request. It must bespecified as a specific name or an asterisk (*), which indicatesall user IDs. If not specified, the default is ID=*, indicating alluser IDs.

PSWD=YES|NOThis keyword indicates whether a Cross-Platform request whichmatches the NODE/MONITOR/ID parameters of the rule musthave a password to accompany the user ID in the request.

YES (or Y)Indicates that such requests must have a password. If notspecified, the default is PSWD=YES.

NO (or N)Indicates that passwords are optional for such requests.



Processing

When the server receives a cross-platform request, it checks todetermine if the request contains an explicit user ID.

1. If the request does not contain a user ID, a password requirementcheck is not made.

2. If the request contains both a user ID and a password, a passwordrequirement check is not made.

3. If the request contains a user ID but no password, a passwordrequirement check is made.

The XPS Router attempts to find the 'best match' between the currentrequest and the Password Requirement Rule Table based upon theNODE, MONITOR, and user ID. A match with a rule that specifies aspecific NODE, MONITOR, and/or user ID takes precedence over ageneric rule. If multiple rules equally match a request, then therule(s) which require a password takes precedence over those that donot. If no match is found in the table, the request is allowed toproceed without a password.



Examples

NODE=A�4IENF,MONITOR=JOBTRAC,ID=�,PSWD=YES

The above rule indicates that any request from CAICCI nodeA04IENF, scheduling system JOBTRAC, must have a password if itcontains an explicit user ID.

NODE=�,ID=MASTER,PSWD=YES

The above rule indicates that any request which contains a user ID ofMASTER must have a password, regardless of what CAICCI node orscheduling system sent the request. The default for MONITOR= is *if it is not specified.

NODE=A�4IENF,ID=TESTUSER,PSWD=NO

The above rule indicates that a request from CAICCI node A04IENFwith a user ID of TESTUSER is not required to have a passwordassociated with it.

NODE=A�4IENF,ID=�,PSWD=YES

NODE=�,ID=TESTUSER,PSWD=NO

If a request is received from CAICCI node A04IENF with a user IDof TESTUSER, it partially matches on both of the above rules. Thesecond rule takes precedence since a specific ID match takesprecedence over a specific NODE match. A password is not required.

NODE=A�4IENF,MONITOR=�,ID=�,PSWD=YES

NODE=�,MONITOR=JOBTRAC,ID=�,PSWD=NO

If a request is received from CAICCI node A04IENF, schedulingsystem JOBTRAC with any user ID it partially matches on both ofthe above rules. In this case the matches have equal weight (NODEor MONITOR specific, user ID generic). In the case of a tie, the rulewhich requires a password takes precedence over one which does not.A password is required.



Chapter 6. Startup and Verification

CA-Jobtrac includes a verification procedure you can use to verifythat CA-Jobtrac is functioning properly. Use of the supplied IVPassumes you have completed the SMP/E installation process, theCA-Jobtrac installation process (STAGE1 and STAGE2), and thecustomization tasks described in Chapter 5. If you have notcompleted these steps, you must do so before using the supplied IVP.This verification procedure is referred to as IVP.

Before Running IVPBefore you can run IVP, you must have completed the install andcustomization steps up to this point and start CA-Jobtrac, and youmust follow the steps in this chapter for the IVP to work correctly.

This chapter discusses these issues.

Chapter 6. Startup and Verification 6-1

Initialization and Startup

Initialization and StartupThis topic covers multiple ways of initializing CA-Jobtrac internals,starting the CA-Jobtrac task, accessing CA-Jobtrac, and ending theCA-Jobtrac task.

Initializing CA-Jobtrac Internals

S VINIT3,PARM=IPL,SUB=MSTR

You must use this method of initializing CA-Jobtrac ONLYduring an IPL when using an IPLTABLE.

Automatically Processing IPL MessagesThe VINIT3 procedure for CA-Jobtrac initialization can be run underthe Master Subsystem to allow some table processing to begin earlyin the IPL process, even before JES is started. With the use of aspecial AMR table called IPLTABLE, you can process receivedmessages and issue commands and schedule or trigger batch jobs.

By default, CA-Jobtrac loads the IPLTABLE during IPL andswitches to the regular AMR table after 15 minutes. If you do notwant to wait the 15 minutes, you can activate a table using the onlinetable services (see the CA-Jobtrac Extended Scheduling ServicesGuide for more information).

For information about the IPLTABLE, see Chapter 5. Forinformation about the other AMR tables, see the CA-JobtracExtended Scheduling Services Guide.

Using CA-Jobtrac at Initialization TimeIf you do not wish to use the IPLTABLE processing feature, add thiscommand to SYS1.PARMLIB member IEACMDxx (for SP2 andSP3 systems):

S JOBTRAC3[.taskname,PARM=IPL]

This command starts the specified CA-Jobtrac and initializes theCA-Jobtrac internals. The optional PARM=IPL parameter allows theIPL message prompt to the console operator as described in theglobal options information in Chapter 5.



Restrictions on Using VINIT3Since VINIT3 running under the Master Subsystem (SUB=MSTR) isstarted so early in the IPL process, very few resources are available.For example, tasks running at this point in the IPL know only aboutdata sets that are cataloged in the master catalog. Therefore, any datasets that must be accessed at this time (such as the CA-JobtracJOBHISTx VSAM cluster) must be cataloged in the master catalog.

See the CA-Jobtrac Operator Guide for other VINIT3 commands.

Starting the CA-Jobtrac Task

Caution

CA-Jobtrac requires CA-GSS to be present to use its fullfunctionality. Minimally, the CA-GSS CAILIB MUST be present.If it is not present, CA-Jobtrac will not start.

ProcedureIf you do not start CA-Jobtrac during your IPL, you can do somanually. To start the CA-Jobtrac task, enter the following commandon each system in the shared spool complex:

S JOBTRAC3[.taskname]

Normally, CA-Jobtrac startup processing by default begins submittingjobs/events, but since the checkpoint file was just formatted, nojobs/events will submit.

Accessing CA-Jobtrac

From ISPFTo access CA-Jobtrac from ISPF, select the option set up by yoursystems programmer.



With a CLISTTo access CA-Jobtrac using a CLIST, enter the following command,which executes the initialization CLIST created by the STAGE2 jobstream:

EX your.CA-Jobtrac.SAMPJCL(TCLIST3)

or

EX your.CA-Jobtrac.SAMPJCL(LIBDEF)

The function of TCLIST3 is to allow entry into CA-Jobtrac untilyour ISPF menu has been updated to include CA-Jobtrac as aselectable menu item (see the information about adding CA-Jobtracto your ISPF Main Menu on Chapter 5).

Ending the CA-Jobtrac Task

To end the CA-Jobtrac task, enter the following command:

P taskname


Verification

VerificationThis topic covers the contents and use of the installation verificationprocedure.

Contents of IVP

The CA-Jobtrac IVP supplied with the product consists of an internalverification procedure, a dynamic schedule, JMF, ADI, AJO andJREPORT testing, and a series of events to be scheduled. All IVPmembers can be found in your SAMPJCL library.

Members SuppliedThe CA-Jobtrac IVP members supplied and their contents aredescribed in the following tables:

SCL Member Contains

IVP001 CA-Jobtrac Dynamic Schedule SCL

JCL Member Contains ModifyJOBStatement

IVPADI Sample ADI job Yes

IVPAJO Sample AJO job Yes

IVPJMF Sample JMF job Yes

JOBT@#$J Internal verification procedurewhich tests CA-Jobtrac andrelated IBM exits to see thatthey are installed and active

No

TESTI1 IEFBR14 Yes

TESTI2 IEFBR14 Yes

TESTI3 IEFBR14 Yes

JREPI1 Sample JREPORT3 - ListSchedule

Yes

JREPI2 Sample JREPORT3 - ListHistory

Yes


Verification

All other jobs will need their JOB statements.

Dynamic Task Contains Modify JOBstatement

0ARCHIVE Tests event and sysoutarchival, dynamic taskscheduling

No

IVP AssumptionsThe IVP assumes the following environment:

■ The IVP001 schedule member resides in the location 001 SCLlibrary. This must be defined as the TRACS001 SCL library in theCA-Jobtrac started task. The STAGE2 installation job streamcreated a CA-Jobtrac started task with TRACS001 pointing to thelibrary defined for the INSTLIB keyword.

■ The CA-Jobtrac started task procedure in your procedure librarycontains a TRACJ001 DD statement naming the same data set asin the last item above. This DD statement defines the JCL libraryfor location ID 001 and contains the IVP events JOBT@#$J,TESTI1, TESTI2, TESTI3, IVPAJO, IVPJMF, IVPADI, JREPI1and JREPI2. The ISPF CLIST for using CA-Jobtrac should alsoallocate this data set, or it should be included in your TSO logonprocedure.

■ The ASMAUTH customization event must also run to generate adefault TRACAUTH table with a default location ID of 1. This isneeded because the IVP001 schedule member schedules events forlocation ID 001.

■ The IVPAJO member must have the DATELIB member sample inthe cai.SAMPJCL library copied over to the DATELIB data setcreated by the STAGE2 JCL. Member IVPJMF must have theJMFSYM01 sample member from the cai.SAMPJCL copied overto the PPOPTION data set.

■ The JREPORT3 procedure as created in STAGE2 customizationexists in an executable form in an accessible procedure library.

■ Because the 0ARCHIVE dynamic task will be scheduled as part ofthe IVP, you might need a tape drive if you have chosen to archivesysouts to tape as specified on the Sysout Capture Options panel(global options).


Verification

Using Other LibrariesIf you decide to use libraries other than those generated during initialinstallation, modify the CA-Jobtrac started task procedure or use adifferent TRACAUTH table. You should ensure that:

■ IVP001 exists in the SCL library defined as TRACS001 in yourJOBTRAC STC task. It can be copied from your SAMPJCLinstallation library if necessary.

■ IVP001 schedules all events to a location ID to which you areauthorized by whatever TRACAUTH table you are using.

■ The JCL members TESTI1, TESTI2, TESTI3, IVPAJO, IVPJMF,IVPADI, JREPJ1, JREPI2, and JOBT@#$J exist in the JCL libraryfor the location ID to which you have scheduled them. They canbe copied from the SAMPJCL installation library if necessary.

■ The proper data set definition exists for the JCL library in both theCA-Jobtrac started task procedure and your TSO session (eitherallocated in your CA-Jobtrac CLIST or added to your logonprocedure) or the DYNAMLOC member.

■ If you change the name of the internals verification procedure job(JOBT@#$J), it must be five to eight characters ending with @#$J.It is not recommended.

ProcedureFollow the steps below to use the supplied IVP:

1. Modify the JCL supplied for the sample jobs to meet yourinstallation requirements. Check the TESTII1, TESTI2, TESTI3,IVPAJO, IVPJMF, IVPADI, JREPI1, JREPI2, and JOBT@#$Jjobs for JOB statement updates. To view sysouts, make sure thespecified MSGCLASS is one of the sysout capture classes youspecified on the Sysout Capture Options panel (global options)and the Capture Sysout option on the CA-Jobtrac Global Optionspanel is set to Y.

2. To begin execution of the IVP, enter the CA-Jobtrac ISPFinterface and issue the following command in the COMMANDfield on the CA-Jobtrac primary panel. All CA-Jobtrac commandsrequire dynamic schedule names and task names to begin with 0(zero).

RUN �IVP��1,L=��1


Verification

This loads the dynamic schedule's SCL and performs syntaxchecking of the input. You can follow the progress of theschedule load by pressing Enter and watching the Current EventStatus field on the right side of the panel. To view the output ofthe schedule, you can tab to the schedule name and enter the O(Output) line command.

3. When the schedule is loaded, type RALL or D in theCOMMAND field and press Enter. This command displays allevents on the schedule (after initial installation, only the IVPevents should be displayed).

4. The Dep Codes (dependency) field for TESTI1 should have amanual (M) dependency. Tab to event TESTI1, type the A(release dependency) line command, and press Enter. The Acommand releases the manual dependency and lets CA-Jobtracsubmit the event.

Each event will run after its predecessor completes, in thefollowing sequence:

TESTI1 Releases TESTI2 upon successful completion

TESTI2 Releases TESTI3 upon successful completion

TESTI3 Releases JOBT@

JOBT@ Releases IVPADI upon successful completion

IVPADI Releases IVPAJO upon successful completion

IVPAJO Releases IVPJMF upon successful completion

IVPJMF Releases JREPI1 upon successful completion

JREPI1 Releases the 0ARCHIVE task upon successfulcompletion

0ARCHIVE Releases JREPI2 upon successful completion

JREPI2 Last event

Member Functions

IVP001 Tests dynamic schedule loading andCA-Jobtrac/ISPF online processing.

TESTI1,TESTI2, andTESTI3

Tests event submission, tracking, and sysoutcapture (IEFBR14).

JOBT@#$J Tests to see the dynamic exits of CA-Jobtrac.


Verification

5. If you selected the tape option during customization, the0ARCHIVE dynamic task might require a tape mount. After the0ARCHIVE task has completed, the TESTI1, TESTI2, TESTI3,AVPADI, IVPAJO, IVPJMF, JREPI1, and the 0ARCHIVEevents which just completed will be deleted from the currentschedule and moved to the history file.

6. CA-Jobtrac signals that each event is complete by indicatingCOMPLETED in the Current Event Stat field on the panel. UntilCA-Jobtrac finishes capturing an event's sysouts, an * (asterisk)appears to the right of the date at the end of the event's record.To view a event's sysouts after the * disappears, tab to the eventand enter the O (output) line command.

Press the END PF key or enter the END command to return tothe Scheduled Event Display panel. At any time, you can selectthe detail panel to view an event's schedule detail by using the S(select) line command.

Member Functions

IVPADI Tests the Automatic Date Insertion abilitiesof CA-Jobtrac. Check the output to see if thecomments match with the days submissiondate.

Verification

Messages ReceivedThe following sequence of messages should appear on the JES JOBLOG for the JOBT@#$J job. These messages indicate successfulexecution of the IVP. If you do not receive these messages, theinstallation of the CA-Jobtrac internals was not successful.

If you are running multiple CA-Jobtracs, in any combination, youmight receive duplicates of the GJTR exit messages.

IEF1961 GJTRIVP2 - IEFUJV EXIT DETECTED THE IVP JOB

GJTRIVP2 - IEFUJV EXIT DETECTED THE IVP JOB

GJTRIVP2 - IEFUJI EXIT DETECTED THE IVP JOB

GJTRIVP2 - IEAVMXIT DETECTED THE IVP WTO

@#$J - GJTRIVP2 - THIS TESTS THE WTO INTERFACE

GJTRIVP2 - IEFACTRT EXIT DETECTED THE IVP JOB

GJTRIVP2 - IEFACTRT EXIT DETECTED THE IVP JOB


Chapter 7. Upgrading, Testing, RunningMultiple CA-Jobtracs

When using all the functions and features to their fullest, CA-Jobtracfunctions as an operating system for production control. You shouldtreat a new version of CA-Jobtrac just as you would a new version ofany major product. Do your installation and testing at times thatallow the most thorough testing with the least impact on your datacenter.

General Procedure

You should test CA-Jobtrac Version 3.5 just as you tested the priorversion of CA-Jobtrac when you first installed it. You shouldschedule routine maintenance, backups, archives, and so on, usingCA-Jobtrac Version 3.5 for several days. Take time to familiarizeyourself with the new functions and facilities. When you arecomfortable with Version 3.5, make it your production system.

Memory Requirements

If you plan to run previous versions of CA-Jobtrac with Version 3.5,take into account the amount of CSA the previous versions will need.Each previous version requires at least 150KB below the line.Extended CSA (above the line) will also grow. Add approximately535KB plus 25KB per checkpoint cylinder (4 cyl x 25KB = 100KB)for each version.

Note: The CSA is reused whenever CA-Jobtrac is stopped andrestarted under normal circumstances. The expanded CSA isnot released or reused when CA-Jobtrac is backed out of thesystem using the 'F JOBTRAC,BACK' operator command.New storage is acquired following a backout of CA-Jobtrac.

Chapter 7. Upgrading, Testing, Running Multiple CA-Jobtracs 7-1

Version Compatibilities and Incompatibilities

Version Compatibilities and IncompatibilitiesTo ensure that you do not obtain CA-Jobtrac prior version loadmodules from the linklist libraries during testing, you need toSTEPLIB to your 3.5 load library in your STC, TSO logonprocedure, and all batch jobs executing CA-Jobtrac programs. Also,due to new SCL keywords, we recommend that SCL libraries arekept separately.

Note: If you are using production SCL and JCL libraries, you mightget duplicate production JCL submitted. We recommend thatyou use different SCL and JCL libraries.

Compatibilities

The following features in Version 3.4 are compatible with Version3.5:

■ All schedules are fully supported. However, since we haveupdated syntax checking for schedule loads, we recommend thatyou test all your product SCL. Also, you should not add newVersion 3.5 features to your production schedules until you haveaccepted Version 3.5 as a production system.

■ All date card formats are the are compatible.

■ All JCL override formats are compatible.

■ All TRACAUTH table definitions are supported.

■ History file is both forward and backward compatible.

■ Capture file is both forward and backward compatible.

Incompatibilities

Version 3.4 programs CANNOT share or access the Version 3.5checkpoint files. Also, Version 3.5 programs CANNOT share oraccess the Version 3.4 checkpoint files.

Version 3.5 Feature

Version 3.5 CANNOT be installed into the same SMP/E CSI, target,and DLIB libraries as Version 3.4 of CA-Jobtrac. Now Version 3.5 iscompatible with other Computer Associates products.


Conversion Notes

Conversion NotesThis topic provides conversion notes on CA-Jobtrac files.

Checkpoint

■ If using Version 3.4 9910 Service Pack 1 or above, you must:

A) Use utility GCJFULDN to unload current checkpoint, andSTEPLIB to the Version 3.4 of CA-Jobtrac for this job.This job creates a backup of the checkpoint.

B) Use utility GCJFRLDN to reload the checkpoint, andSTEPLIB to the Version 3.5 of CA-Jobtrac for this job.Use the backup file created from Step A as input.

■ If using below Version 3.4 9910 Service Pack 1, you MUST use aformatted checkpoint file.

Use GCJFFMT to format a new checkpoint, and STEPLIB to theCA-Jobtrac 3.5 CAILIB for this job.

Capture

The capture file format has not changed, but if a new capture file isdesired, build it with GJTRVFMT and point OLDCAP to the oldcapture file, or you can use the Version 3.4 capture file.

History

The jobhist file format has not changed, but if a new jobhist file isdesired, you can use IDCAMS REPRO to move data from old jobhistto the new HISTORY data set, or you can use the 3.4 jobhist.

PDS Data Sets

All JCL files and SCL DSNs can be copied to new libraries or usedas they are for the CA-Jobtrac Version 3.5 STC, PROCs, and CLIST.


Recommended Procedures for Upgrading Your 3.4 Production to 3.5 Production

Recommended Procedures for Upgrading Your 3.4Production to 3.5 Production

These procedures recommend that the same tokens from Version 3.4be used for the new CA-Jobtrac Version 3.5. Use the following as aguideline to upgrade from CA-Jobtrac Version 3.4 to CA-JobtracVersion 3.5:

1. Complete the CA-Jobtrac Version 3.5 installation procedure.

2. Issue the CA-Jobtrac HOLD command (F stcname,HOLD). Nextshut down CA-Jobtrac 3.4 (P stcname).

3. Submit backup jobs for the checkpoint, capture, and jobhist files.

Note: See Version 3.4 SAMPJCL for sample JCL.

If using linklist, make sure that your CA-Jobtrac 3.5CAILIB replaces the old CA-Jobtrac 3.4 TRACLINKloadlib and refresh LLA.

4. Make sure that all the ddnames for the checkpoint, jobhist, andcapture files reflect the correct names in your PROCs, CLISTs,and batch jobs executing CA-Jobtrac programs.

5. You need to either IPL or back out the internals of CA-Jobtrac (SVINIT3,PARM=BACK). When using the BACK command, seethe CA-Jobtrac Operator Guide for details.

6. Start the new CA-Jobtrac 3.5 STC (S stcname).

7. Log on to CA-Jobtrac 3.5 and issue the STATUS command toverify version.

8. Test the installation with the verification procedures inChapter 6, “Startup and Verification.”

9. Release the production workload from 3.5 (Fstcname,RELEASE).



Returning to Prior Version

Use one of these procedures to return to a prior version ofCA-Jobtrac.

Returning to 3.4

1. Shut down CA-Jobtrac 3.5 with a BACK (F stcname,BACK) orIPL. Put the CA-Jobtrac 3.4 TRACLINK back in the linklist (ifthat is where it was). Refresh LLA if needed.

Note: When using the BACK command, see the CA-JobtracOperator Guide for details.

2. Make sure that all the ddnames for the checkpoint, jobhist, andcapture files reflect the correct names in your PROCs, CLISTs,and batch jobs executing CA-Jobtrac programs.

3. Edit the RESOURCE member of PPOPTION and remove orcomment any two-character resource codes that you have defined.Or use the table that you had defined resources in the CA-Jobtrac3.4 TRACPARM(RESOURCE). Two-character resourcesgenerate errors when CA-Jobtrac attempts to load the resourcetable.

4. Edit any of your schedules that had been updated to use the RS=,@FLOW=, FLOWSTART= or FLOWEND= keywords andcomment them out or remove them.

5. Run the GJTRSC35 utility with no PARM (or PARM=DETAIL)to remove the CPM and two-character resource information thatwill not be properly handled by Release 3.4.

6. You can use the CA-Jobtrac 3.5 capture and jobhist files, or youcan use the old DSNs from CA-Jobtrac 3.4, or you canRESTORE the files from the backup files from CA-Jobtrac 3.4for the checkpoint, capture, and jobhist files from the backupscreated when upgrading from 3.4.

7. Start CA-Jobtrac 3.4 (S stcname).



The GJTRSC35 Utility

The GJTRSC35 utility removes data from the checkpoint that wasintroduced by CA-Jobtrac Release 3.5 and is not properly handled byCA-Jobtrac Release 3.4. This is only intended to be used in the eventthat you need to return to 3.4 using the same checkpoint file that 3.5had been using.

Sample JCL for running the GJTRSC35 utility is inSAMPJCL(GJTRSC35). The sample shows passing a PARM ofTEST to the program. The following parameters may be specified onthe EXEC statement PARM= keyword.

TESTProcesses the checkpoint and reports the changes that would bemade, without updating the checkpoint. The default is to updatethe checkpoint with the changes.

DETAILReports all the records in the checkpoint, whether they had tohave data removed or not. The default is to report only therecords that had data removed.



Recommended Procedures to Run 3.4 Production and 3.5Test System

1. When starting the CA-Jobtrac Version 3.5 installation, you needto:

a. Choose a new token.

b. Create a new CA-GSS subsystem ID.

c. Choose a new AUTOSCHD character.

d. Create new STC procedure, CLIST, and any batch jobsexecuting CA-Jobtrac programs using the new CAILIB as aSTEPLIB, all new ddnames, and tokens.

Note: The JOBTRAxx member in PPOPTION data set needsthe appropriate options set for the new checkpoint andAUTOSCHD character since they are initially set to thedefault values. Also check other options that you want toset.

2. Files

a. Checkpoint: Start with a new, empty checkpoint data set. YouHAVE to use the new token for the new checkpoint file.

b. Capture: Start with a new, empty capture data set.

c. Jobhist: Start with a new, empty jobhist data set. You cancopy over your ADR, AMR, CCPF, and SCS tables for thenew jobhist since they are initially set to the default values.Otherwise, you can use the defaults. You HAVE to use thenew token for the new jobhist file.

3. Start the new CA-Jobtrac STC 3.5.

4. Log on to CA-Jobtrac 3.5.

5. Perform the installation verification procedures in Chapter 6,“Startup and Verification.”

6. Test the new CA-Jobtrac 3.5.


Procedure to Run Multiple CA-Jobtrac STCs on Same CPU

Procedure to Run Multiple CA-Jobtrac STCs onSame CPU

1. Do NOT change any of the production CA-Jobtrac PARMs ordata sets in the STC, PROCs, DYNAMLOC member, or CLIST.

2. You need to have a new CA-Jobtrac token and a new SSID forCA-GSS.

3. Make the following changes:

a) Allocate new files with the new token. Look at SAMPJCLmember STAGE2.

//JOBTRACy DD DISP=SHR,DSN=your.new.checkpoint

//JOBHISTy DD DISP=SHR,DSN=your.new.histfile

//CAPTURE DD DISP=SHR,DSN=your.new.capture

b) Similar updates need to be added to your logon CLIST forthe new JOBTRACy and GSSx and any PROCs that useCA-Jobtrac programs.

//JOBTRACy DD DISP=SHR,DSN=your.checkpoint

//JOBHISTy DD DISP=SHR,DSN=your.histfile

//SEQHISTy DD DISP=SHR,DSN=your.histfile.DATA

//CAPTURE DD DISP=SHR,DSN=your.new.capture

4. Create a new JOBTRACy PROC with a unique name such asJOBTRACy. Add a //STEPLIB DD if needed to this PROC.

5. Consider creating a new PPOPTION. This is not necessary, butRESOURCE and EXCLPARM would be shared otherwise.

6. You can still use the existing TRACSnnn, TRACJnnn,TRACDnnn, TRACTnnn, or TRACRnnn files if you would like.However, we suggest you just copy the existing productioncopies into a unique set of files for the JOBTRACy PROC.

This recommendation is good sense, but CA-Jobtrac will have noproblem sharing these libraries.

7. MAKE SURE AMPLE CSA AND ECSA IS AVAILABLE ifrunning multiple CA-Jobtracs.

8. AUTO-SCHD character and class must be unique to eachCA-Jobtrac.


Procedure to Run Multiple CA-Jobtrac STCs on Same CPU

9. CA-GSS Considerations

a) You must create a new GSSx PROC to go with the newJOBTRACy PROC.

b) GSSx will execute PGM=SRVSYS. Add a //STEPLIBnew.CAILIB to this PROC if needed. Add a //JOBTRACyDD DISP=SHR,DSN=new.checkpoint

c) GSSx can still use existing IMODS but MUST have adifferent SSNAME defined such as SSNAME IS35.

10. In JOBTRACy GLOBAL OPTIONS you must define the GSSxstarted task and the SSNAME IS35. (RUNPARM member.)

Caution

DO NOT USE SSNAME AS EXISTING PRODUCTIONCA-GSS!!!!

(CA-Jobtrac uses that SSID. If CA-GSS tries to use the sameone, it will not work, except possibly if CA-GSS can beguaranteed to be up first. Do not risk it.)

11. You must copy the production CA-Jobtrac PARMs (JOBTRA00)to the new JOBTRACy PPOPTION file. No changes should berequired.

12. If you are using CA-11 you must add the RERUN=CA-11PARM and the INSERTRMS=x, where x is class to be monitoredby CA-11, into the JOBTRA00 member of the PPOPTION forJOBTRACy.

13. Create a new logon CLIST for the JOBTRACy logon. It shouldhave all the new files allocated just like the original productionCLIST. You will be required to add the CAILIB for the newJOBTRACy as a STEPLIB or ISPLLIB.

Files should be allocated as they are for the new STC, not the oldCLIST. ISPLLIB is not sufficient. STEPLIB is necessary forCAILIB. This can lead to very sneaky bugs, where modules fromdifferent levels are executed at different times.

You cannot log on in split screen to multiple CA-Jobtracs.

14. Start JOBTRACy on the system. It loads the hooks dynamicallyand should start up GSSx as well.


Procedures for CA-Jobtrac in a Shared DASD Environment

Procedures for CA-Jobtrac in a Shared DASDEnvironment

CA-Jobtrac is capable of controlling the workload across multiplesystems with shared DASD. You must start CA-Jobtrac on eachsystem where you would like the workload to be monitored. Forexample, SYS1 is the primary CA-Jobtrac. The primary system iswhere all event submission takes place. SYS2 and SYS3 are yoursecondary monitor systems. The monitor systems do not submit anyevents. They monitor the events that run on the system that aresubmitted by the primary system.

These considerations assume that you need at least two or moresystems with shared DASD, and you plan to start CA-Jobtrac taskson both of them. When installing CA-Jobtrac in a multiple-systemenvironment, the following considerations apply:

1. Define the primary and secondary monitor systems in theJOBTRAnn member of the PPOPTION data set by using thekeywords SYNCSYS1, SYNCSYS2, and SYNCSYS3.SYNCSYS1 defines the primary system. SYNCSYS2 andSYNCSYS3 define the secondary monitor systems. Each keywordpoints to the SMF system ID of the appropriate system.

Note: Updating the options SYNCSYS1 through SYNCSYS3requires that ALL CA-Jobtracs on each system berecycled to switch the primary. The SMF system IDsdefined in the JOBTRAnn member are stored in theCA-Jobtrac checkpoint data set. Recycling CA-Jobtrac hasno effect on what is stored in the checkpoint data set. Toswitch the primary system, you MUST use the modifycommand

F stcname,ACTSYS=xxxx

2. Also view the primary and secondary definitions from ISPF bylooking at the SYSID priority list (SYS OPTS) on theCA-Jobtrac global options panel.

3. You can have separate JES spools on your systems or a sharedJES spool environment.

4. CA-Jobtrac checkpoint, jobhist, and capture files are sharedbetween the primary and secondaries. When using a sharedDASD system, review “Serialization Considerations for SharedDASD Users” on page 2-19.

5. All tokens for the DD statements MUST be the same.


Procedures for CA-Jobtrac in a Shared DASD Environment

The following CA-Jobtrac message displays in the JES log on theprimary system.

STC�5657 JOBTRAC - PRIMARY SUBMISSION SYSTEM (SYS1).

The following CA-Jobtrac message displays in the JES log on thesecondary systems.

STC�1195 JOBTRAC - AUTOMATION MONITOR SYSTEM (SYS2).

Changing Primary Submission SystemCA-Jobtrac gives you the ability to change the primary system. Youcan issue the modify command:

F stcname,ACTSYS=xxxx

(where stcname is the CA-Jobtrac started task name and xxxx is theSMF ID of the system you would like to make the primary.) Forexample, if SYS1 is currently the primary and you would like tomake SYS3 the primary, you would issue the command:

F stcname,ACTSYS=SYS3

You get the following WTOR on your console:

F JOBTRACY,ACTSYS=SYS1

�49 TRAC737W - VERIFY THAT THE PRIMARY JOBTRAC IS INACTIVE

AND REPLY TO CONTINUE (Y/N)

R 49,Y

JOBTRAC - PRIMARY SUBMISSION SYSTEM ASSIGNED.

TRAC1�68I ACTSYS=SYS1 command processing complete

You should reply yes, and the primary will be switched.



Chapter 8. Troubleshooting

This chapter contains information about:

■ Identifying and resolving problems

■ Contacting Computer Associates Technical Support

■ Receiving a new version of a product and ongoing maintenance

■ Requesting product enhancements

Chapter 8. Troubleshooting 8-1

Diagnostic Procedures

Diagnostic ProceduresSee the flowchart below for a summary of the procedures you shouldfollow if you have a problem with a Computer Associates softwareproduct. Each of these procedures is detailed on the following pages.


Diagnostic Procedures

Collecting Diagnostic Data

In the table below, use the left column to categorize the problemyour site has encountered. Then, follow the instructions in thecorresponding right column to generate useful diagnostic data.

Type of Problem Procedure

Installation Save all SMP/E RECEIVE,APPLY, and ACCEPT outputand any other outputgenerated from any otherinstallation step.

User and system abends Obtain SYSMDUMP anddump to tape. Followprocedures (later in thischapter) to generate a problemreport. Collect the tape,listing, and problem report andcontact Computer AssociatesTechnical Support.

Interpreting Diagnostic Data

When you have collected the specified diagnostic data, write downyour answers to the following questions:

1. What was the sequence of events prior to the error condition?

2. What circumstances existed when the problem occurred and whataction did you take?

3. Has this situation occurred before? What was different then?

4. Did the problem occur after a particular PTF was applied or aftera new version of the software was installed?

5. Have you recently installed a new version of the operatingsystem?

6. Has the hardware configuration (tape drives, disk drives, and soforth) changed?

From your response to these questions and the diagnostic data, try toidentify the cause and resolve the problem.


Accessing the Online Client Support System

Accessing the Online Client Support SystemComputer Associates is making extensive use of the Internet for yourbenefit. Computer Associates encourages you to "surf the net" to theComputer Associates home page at ca.com and the support site ateSupport.ca.com. The Computer Associates Internet site provides agreat variety of information about Computer Associates products andservices, including:

■ Service and support■ Product information and sales■ CA-World conference information■ Press releases■ Computer Associates user groups

StarTCC, the web-based portion of CA-TCC (CA-Total Client Care),gives you real time, interactive access to Computer Associatesproduct support information through the Internet. Using StarTCC,you can:

■ Open new issues■ Browse or update your existing issues and enhancement requests■ Perform keyword searches■ Download solutions, PTFs, and important notices regarding

Computer Associates products, maintenance, and documentation

Requirements for Using StarTCC

The following are the requirements to use StarTCC:

■ You must be a Computer Associates client with a currentmaintenance agreement.

■ You must register through the Computer Associates Internet site.

■ You must access the Internet with a browser that supports theHTML specification 2.0 or higher, such as Netscape Navigator 2.0or higher or Microsoft Internet Explorer 3.0 or higher.

Browsers that meet the HTML requirement support the followingfunctions, which are required for StarTCC:

– Secure sockets layer (SSL) to encrypt your transaction traffic– Encrypted data records (known as COOKIES)– HTML tables



StarTCC Security

StarTCC runs as a secured server (SSL). You may need to configureyour browser to enable SSL. Guidelines for doing this are providedon the Computer Associates Technical Support page.

Accessing StarTCC

To access StarTCC, go to eSupport.ca.com The StarTCC options are:

■ StarTCC Information■ StarTCC Registration■ Access StarTCC

These options are described below.

StarTCC InformationSelect the information option to view background information forStarTCC, details about the prerequisites, and instructions forconfiguring your browser. Be sure to review this section for updatesor information not included here.

StarTCC RegistrationSelect the registration option to identify yourself to StarTCC. Youmust register before you can access StarTCC online. There areprompts for all required information, including your name, site ID,CA-StarTrak PIN, company name, E-Mail address, postal address,and desired password for accessing StarTCC.

Note: If you do not have a CA-StarTrak PIN, StarTCC providesone for you when you register.

Access StarTCCSelect the access option to begin using StarTCC. When prompted,enter your user ID and password. Once your sign-on is validated,you can perform the following:

Open a new issueOpen an issue for, or request an enhancement to, one ofyour Computer Associates products.

Browse your issues and enhancement requestsDisplay all issues for your site. The issues are groupedinto three categories: Open, Closed, and EnhancementRequests (DARs).



Browse and/or download solutionsSpecify criteria for selecting solutions, which you can thenview or download.

Search the Computer Associates knowledge baseSpecify criteria for searching the Computer Associatesdatabase for solutions, problems, and keywords that canprovide you with immediate answers to your productsupport questions and concerns.

Update your StarTCC profileMake changes to your default E-mail address, phonenumber, and password whenever necessary.

Display your site's licensesView a list of all the Computer Associates products forwhich your company site is currently licensed.

Display StarTCC news itemsView and download recently published solutions forComputer Associates products, instructions for downloadingfrom StarTCC, and helpful information for usingCA-StarTrak, StarTCC, or other Computer Associatesproducts.

Accessing the Technical Support Phone ServicesDirectory

The Computer Associates Technical Support Phone ServicesDirectory lists each Computer Associates product and the telephonenumber to call for primary support for that product. To access theSupport Phone Services Directory, set your browser foreSupport.ca.com and click on Contact Us.


CA-TLC: Total License Care

CA-TLC: Total License CareMany Computer Associates software solutions use license keys orauthorization codes to validate your hardware configuration. If youneed assistance obtaining a license key or authorization code, contactthe CA-TLC: Total License Care group through eSupport.ca.com.


Contacting Technical Support

Contacting Technical SupportFor further technical assistance with this product, please contactComputer Associates Technical Support at eSupport.ca.com for acomplete list of Computer Associates locations and phone numbers.Technical Support is available 24 hours a day, seven days a week.

If you are unable to resolve the problem, please have the followinginformation ready before contacting Computer Associates TechnicalSupport:

■ All the diagnostic information described in “Collecting DiagnosticData” on page 8-3

■ Product name, version number, operating system, and genlevel.

■ Product name and version number of any other software yoususpect is involved.

■ Version level and PUTLEVEL of the operating system.

■ Your name, telephone number and extension (if any).

■ Your company name.

■ Your site ID.

■ A severity code. This is a number (from 1 to 4) that you assign tothe problem. Use the following to determine the severity of theproblem:

1 a "system down" or inoperative condition

2 a suspected high-impact condition associated with theproduct

3 a question concerning product performance or an intermittentlow-impact condition associated with the product

4 a question concerning general product utilization orimplementation


Product Versions and Maintenance

Product Versions and MaintenanceClients are requested to operate only under currently supportedversions of the product.

Clients with current maintenance agreements also receive ongoingproduct maintenance. When a new version of the system isavailable, a notice is sent to all current clients.


Requesting Enhancements

Requesting EnhancementsComputer Associates welcomes your suggestions for productenhancements. All suggestions are considered and acknowledged.You can use either of two methods to request enhancements:

■ Contact your Account Manager who will initiate a DemandAnalysis Request (DAR) for you.

■ Enter your request through StarTCC, the Computer Associatesweb-based, interactive support system at eSupport.ca.com.


Appendix A. NJE Support

The following sections describe changes or additions to CA-Jobtracas a result of adding NJE support.

Appendix A. NJE Support A-1

Installation and Setup

Installation and Setup■ CA-Jobtrac NJE support requires CA-GSS. CA-GSS must be set

up to include networking support for all JES nodes in whichCA-Jobtrac is to be used for NJE support. This is done using theGoalNet features of CA-GSS. See the Unicenter TNG Frameworkfor OS/390 Getting Started and the Unicenter TNG Framework forOS/390 Administrator Guide for information about GoalNet.

■ The CA-Jobtrac global options panel of the CA-Jobtrac globaloptions menu includes two fields for NJE support: NJE NODE(Y/N) and NJE Node Tokens (see Options on the CA-Jobtracglobal options panel in this guide for more information). The NJENODE option allows you to specify whether to activate theCA-Jobtrac NJE support for this instance of CA-Jobtrac on thissystem image. If you specify Y, the NJE Node Tokens fieldbecomes significant.

■ A CA-Jobtrac token is the x in the Jobtracx DD statement. Thetoken identifies and differentiates individual CA-Jobtracs. In theNJE Node Tokens field, you specify which CA-Jobtrac events arerecognized by this CA-Jobtrac. This is done by listing up to 39tokens. If you leave this field blank, all tokens (that is all eventsfrom all CA-Jobtracs) are processed by this CA-Jobtrac. If youleave the field blank, do one of the following:

– Only start up one NJE-capable CA-Jobtrac on any single systemimage

– Specify nonoverlapping tokens for each CA-Jobtrac running

The JES /*ROUTE or /*XEQ statements identify an event as anNJE event.

If you explicitly specify tokens and you submit NJE jobs to thesubmitting node itself, you should specify the token of thesubmitting CA-Jobtrac itself in the token list.

The specified NJE nodes apply only to the NJE events for theCA-Jobtracs which are specified as being NJE nodes. All otherCA-Jobtrac instances recognize only their own tokens.

■ NJE systems require all CA-Jobtracs to be primary CA-Jobtracsand not monitor CA-Jobtracs. It is important to use a SYSOUTpackage in an NJE environment. CA-Jobtrac can only successfullycapture sysout in an NJE environment if the JES job numberranges on the submitting and executing nodes do not overlap andoutput is returned to the submitting node in a timely manner (lessthan 15 seconds).

A-2 CA-Jobtrac 3.5 Getting Started

Job Submission

Job Submission■ AUTO-SCHD jobs running on an NJE node are not supported.

■ DUMMY jobs running on an NJE node are not supported.

■ In an NJE environment, if NOTIFY is specified, only users on thenode on which the NJE job is run will be notified of abend or errorconditions for that node based on information in the TRACAUTHtable defined for that node.

■ Use JES /*ROUTE XEQ or /*XEQ control statements to route NJEjobs to other nodes. NJE jobs must use the JES /*ROUTE XEQ or

Job Execution

Job Execution■ The NJE job will be tracked by CA-Jobtrac.

■ An NJE surrogate checkpoint record is added to the remoteCA-Jobtrac checkpoint data set for tracking, display, and recoverypurposes.

■ The NJE surrogate contains a subset of the information from theactual checkpoint record. The information is viewable but notmodifiable by the CA-Jobtrac ISPF interface user.

■ When the NJE job actually begins execution on the executingnode, the submitting node's CA-Jobtrac ISPF display will indicateits executing status.

■ Any Notifies as specified in the TRACAUTH table will only bedone on the executing node as defined in the executing node'sTRACAUTH.

■ TRACX09 is invoked at both the submitting and executing node.


Job Termination

Job Termination■ Successful or unsuccessful termination of a job will result in the

passing of the termination status back to the originating node. Oncethe status is posted at the originating node, normal CA-Jobtracprocessing occurs.

■ If the return of the termination status of a job back to itsoriginating node is successful, the NJE surrogate checkpoint recordis automatically deleted at the executing node. No historyinformation is copied to the history file at the executing node.History information is copied to the history file at the submittingnode.

■ If the returning of termination status is unsuccessful for whateverreason (for example, networking error, originating node down), theNJE surrogate record is retained on the checkpoint. It is used toattempt to retry the returning of status at the next CA-Jobtracstartup.

■ The NJE surrogate can only be removed by the successful return ofstatus or the next CA-Jobtrac job archive run with the ALL option.

■ It is important to use a SYSOUT package in an NJE environment.CA-Jobtrac can only successfully capture sysout in an NJEenvironment if the JES job number ranges on the submitting andexecuting nodes do not overlap and output is returned to thesubmitting node in a timely manner (less than 15 seconds).


ISPF Interface

ISPF Interface■ NJE jobs in Awaiting Execution or Executing status have a

Scheduled Event Display status of N-status-nodename, SYS=sssswhere status is either NAWT for Awaiting Execution or EXE forExecuting, nodename is the remote JES node name and ssss is thesubmitting system's SMF system ID.

■ The event execution detail display for executing or completed jobsdisplays the JES node if the job was an NJE job.

■ NJE jobs running on the executing node have an NJE surrogatecheckpoint record. The status on the Scheduled Event Display forthese submitted NJE jobs includes an N instead of a J precedingthe JES job number.

■ Only a subset of the normal line commands on the ScheduledEvent Display are available for remotely-submitted NJE jobs. Theline commands available are: @, *, ?, N, O, P, Q, S, and 0 (zero).

■ When the S line command is used to Select an NJE submitted job,the new NJE Execution Detail panel is displayed which contains asubset of the information normally available when selecting anevent for display. The new fields which are displayed on this panelfor any NJE submitted jobs are the JES Node Name of thesubmitting node, the GSS Node Name of the submitting node, theOriginal Version Number of this job on the submitting node, andNJE status. See the CA-Jobtrac Operator Guide for moreinformation about the NJE Execution Detail panel.

■ The P (purge) line command can be used to release an NJE job onthe submitting node when it is in a hung condition with either anNAWT or EXE status because the NJE node failed to post thetermination status. The purge command resets the completionstatus and places an Output Release on the job. You are now ableto perform other appropriate actions against the job.

■ On displays of times for NJE jobs on either the submitting orexecuting nodes, time zone differences are taken into considerationand all times are adjusted to reflect local time.


ISPF Interface

■ When selecting events to display on the Scheduled Event Display,a N=nodename command is available. Specifying this commandwith the desired JES node name limits the display to NJE jobssubmitted to or from the designated node.

■ The K= primary command supports two selection types of N andS. The N code selects for display only NJE jobs on this nodesubmitted to other nodes, while the S code selects only NJEsurrogate jobs, those jobs which have been remotely submittedfrom another node.


Batch Archiving and JREPORT

Batch Archiving and JREPORT■ 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 remains on the CA-Jobtraccheckpoint so that a retry of posting the termination status to theoriginating node can be performed.

■ When listing event information for an archive or JREPORT, an *next to an event name denotes the event is a REXX IMOD. An @next to an event name denotes the event is a dummy job. A % nextto an event name denotes the event is an NJE job submitted toanother system. A # next to an event name denotes the event is anNJE job submitted from another system.


REXX Stack Information for NJE Jobs

REXX Stack Information for NJE Jobs

Prefix Information

ETIM End time and date for the event. Returns theinformation in the hh:mm mm/dd formatincluding the colon and slash.

NJE If this event is an NJE job which has beensubmitted to another JES node, the JES nodename on which the event is executing or hasexecuted. Otherwise, this is blank.

ONQU If this is an AUTO-SCHD event, indicates theevent has been submitted and recognized byCA-Jobtrac. Otherwise, this is blank.

SUBT Actual time and date the event is submitted forexecution by CA-Jobtrac. Returns theinformation in the hh:mm mm/dd formatincluding the colon and slash.

Keywords

Keyword Options

END_TIME or ETime Same options for definition asATime, STime, and TTime.

JES_NODE or JESNode Up to eight-character JESnode name where this event isexecuting.

NJE (Yes or No) Indicates whether this is anNJE job.

ONQueue (Yes or No) Indicates whether the JCLassociated with thisAUTO-SCHD job has beensubmitted and recognized byCA-Jobtrac.

SUB_TIME orSUBMIT_Time

Same options for definition asATime, STime, and TTime.



Appendix B. Connecting Systems forCross-Platform Scheduling

This appendix is designed to assist you in setting up CAICCInetwork connections on OS/390, NT, and UNIX to supportcross-platform scheduling. You can find more detailed informationin the CA Reference Guide and the Unicenter TNG manuals for thespecific platform.

Appendix B. Connecting Systems for Cross-Platform Scheduling B-1

OS/390 CAICCI Installation and Considerations

OS/390 CAICCI Installation and ConsiderationsFor CAICCI to support peer networking, CAICCI must be linkedwith the TCP/IP product. This is described in the Unicenter TNGGetting Started in the Link-edit CAICCI for TCP/IP topic. Ensurethat the link for the appropriate TCP/IP product has been completed.

The CCIPARMS control options must be updated to activate theCAICCI gateway tasks. These are described in Unicenter TNGFramework for OS/390 Administrator Guide in the CAICCI controloptions topic. Following is a sample of the required protocolstatement:

PROTOCOL(TCPIPGW,85��,2,XE21)

Optionally, you can define the connection on OS/390 for the remoteUnicenter TNG system. This is not recommended since it is moremanageable to define the OS/390 system on the NT or UNIXplatform. Following is an example of the CCIPARM statementnecessary to define a remote node to CAICCI on OS/390:

NODE(TCPIPGW,141.2�2.72.7:1721,2,USLIGPEX)

CONNECT(USLIGPEX)

The SYSID parameter in the CCIPARM member names specify theunique name to be used in connecting with this OS/390 system.

SYSID(XE21)

This name is specified on the remote CAICCI system to identifyCAICCI on the OS/390 system.

From OS/390, in the syslog, the following message indicates asuccessful connection to the remote Unicenter TNG machinennnnnn:

CAS96�3I - CAICCI XE21 CONNECTED TO CAICCI nnnnnn

B-2 CA-Jobtrac 3.5 Getting Started


Unicenter TNG (NT) Installation and Considerations

The following components must be installed and configured:

Unicenter TNG (NT)The Unicenter TNG installation process is clearly outlined inthe Unicenter TNG Getting Started.

Workload AgentThe Unicenter TNG Getting Started, Chapter 4, discussesconfiguration options for the Workload Agent(s). You mustensure that the Workload Management Server Activated fieldis set to NO and the Workload Management Agent Activatedfield is set to YES.

Communication Transport ProtocolBy default, CAICCI uses NetBEUI (NetBIOS). This must bechanged to use TCP/IP to communicate with OS/390. AllUnicenter TNG systems must use the same CommunicationTransport Protocol.

Remote CAICCIFor cross-platform scheduling to be done, remote CAICCImust be installed and configured to connect to any machinethat is part of cross-platform scheduling.

Ensure that you can ping the OS/390 system. If not, modifythe TCP/IP setup on the PC as well as on OS/390 to makeadjustments to make the ping successful.

1. To install CAICCI remote, issue the following command:ccicntrol install rmt <path> -where path represents the$CAIGLBL000\bin (for example, ccintrl rmt x:\tng\bin).

2. Verify that thexxxxxxxx\system32\drivers\etc\SERVICES file has anentry for CAICCI with the following port # assigned.

# CA-Unicenter remote daemon

# CCI must be shut down and restarted if port is chgd.

caicci 1721/tcp

Note: xxxxxxxx = Your Windows NT Directory Path.This entry is added when CAICCI remote servicesis installed. Also, the default PORT # must not bechanged as CAICCI on the OS/390 system usesthis for CAICCI communications. The PORTnumbers on OS/390 and NT must match.



3. The \TNG directory must have a ccirmtd.rc file.

CCIRMTD is the name of the CAICCI configuration file.It contains a 'local' statement that applies to the localcomputer and 'remote' statements that apply to the remotenodes that exchange information with CAICCI. You mayuse this file to indicate aliases for node names; see thealias options field below.

The format for the statement is:

LOCAL <TCP/IP name><CCI name><buffersize<startup

options><alias options><port options><retry interval>

REMOTE <TCP/IP name><CCI name><buffersize<startup

options><alias options><port options><retry interval>

TCP/IP name—either an IP address or a name that is usedas input to a name service to retrieve an IP address. This(TCP/IP name) is the same name that may be provided tothe ping utility to determine whether a remote connectionis live. The default value is the TCP/IP host name.

CCI name—a logical name that Unicenter TNGapplications may use to insulate themselves from thenetwork and any protocols being used. The default valueis the TCP/IP host name.

buffer size—a value between 1024 and 32768 used forsegmenting the data transfer. It is generally not necessaryto alter this field.

Important!

Contact Computer Associates Technical Supportbefore changing the buffer size.

startup options—either STARTUP or NOSTARTUP.STARTUP tells CAICCI to attempt a remote connectionwhen activated. NOSTART has the opposite meaning.NOSTART implies that the remote system will beinitiating the connection to this node.

alias options—used to differentiate multiple remotecomputers having exactly the same first eight characters(when their host names exceed eight characters). Thisfield is optional and is not provided by default. Theformat is ALIAS=<aliasname>.



port options—optional numeric value set by default to1721. If this value is changed, all systems incommunication must be changed likewise. The format isPORT=<TCP/IP port number>.

retry option—number of seconds between retry connectattempts. The format is n=0 (no retry), -1 (exponential),>0 (seconds between retry).

LOCAL Statements

The following are examples of LOCAL statements:

LOCAL=PAYROLL PAYROLL 1�24 STARTUP

This statement tells CAICCI that the local machine'sTCP/IP name is PAYROLL and that any remote systemwishing to communicate with this system can do so byreferencing PAYROLL as the name. Any Unicenter TNGsystem within the network can send and receive messagesto this system independent of hardware or protocols, ifthey use the name PAYROLL.

LOCAL BACKUPCLIENT��1 BKCLI��1 1�24 STARTUP

This statement tells CAICCI that the local machine'sTCP/IP name is BACKUPCLIENT001 and its networkindependent name is BKCLI001. BKCLI001 will be thename foreign computers can use to send and receivemessages with this computer.

REMOTE Statements

Remote statements are used for connection with UNIXand OS/390 machines. The following are examples ofREMOTE statements:

REMOTE=141.222.111.121 PAYROLL 1�24 STARTUP

This statement tells CAICCI to attempt a connection to141.222.111.121 and to internally register PAYROLL asthe CAICCI name. This means that any Unicenter TNGsystem within the network can send and receive messagesto this system if they use the name PAYROLLindependent of hardware or protocols. A DNS definedname could be used instead of an IP address.

Once the REMOTE statements have been defined, thenext startup of CAICCI should produce connectionsbetween all nodes listed in the REMOTE statements andthe machines where the REMOTE statements reside.



4. The Unicenter TNG REMOTE Service must be running.This can be verified either through the Services task underControl Panel or by issuing the command:

ccicntrl start rmt (starts the rmt service)

If you need to start the Unicenter TNG REMOTE Service,issue the following commands:

ccicntrl start rmt (starts the rmt service)

ccicntrl start nrs (starts nrs service for CCII)

To verify that CAICCI has established communications,from the NT machine, issue the following command froma MS-DOS prompt:

ccii

Sample output:

time = 4�

Old(LVL1NT ,CAUWV.Daemon.WNT ) Did( , ) type (L)

Old(LVL1NT ,UniappServer ) Did( , ) type (L)

Old(LVL1NT ,CA_Cal_Chk ) Did( , ) type (L)

Old(LVL1NT ,Sam.Daemon.WNT ) Did( , ) type (L)

Old(LVL1NT ,SUBMITC Server ) Did( , ) type (L)

Old(LVL1NT ,CAU9SET SetUp Mgr ) Did( , ) type (L)

Old(LVL1NT ,CAI_OPR_DAEMON ) Did( , ) type (L)

Old(LVL1NT ,ROUTER_SERVER ) Did( , ) type (L)

Old(LVL1NT ,CA7PROD Job track ) Did( , ) type (L)

Old(XE21 ,SPMAGP_Y.XE21UHD ) Did( , ) type (R)

Old(XE21 ,CA_WHD_IMCA_CICSADG3) Did( , ) type (R)

Old(XE21 ,DSMFA21IDISP ) Did( , ) type (R)

Old(XE21 ,S9CICICSBAG1CICSBAG1) Did( , ) type (R)

Old(XE21 ,MUFBAG1_SERVER ) Did( , ) type (R)

Old(XE21 ,S9CICICSBAG3CICSBAG3) Did( , ) type (R)

Old(XE21 ,AK�.NTM49DB ) Did( , ) type (R)

Old(XE21 ,S9CICICSSMS1CICSSMS1) Did( , ) type (R)

Old(XE21 ,S9CICICSIMS1CICISMS1) Did( , ) type (R)

Old(XE21 ,CAAPCDDSMAIN ) Did( , ) type (R)

Old(XE21 ,MUFSMS1_SERVER ) Did( , ) type (R)

Old(XE21 ,B_HTO_PC_SERVER_1 ) Did( , ) type (R)

Old(XE21 ,HTO_PC_SERVER_1 ) Did( , ) type (R)

Old(XE21 ,CA_PC_SERVER_1 ) Did( , ) type (R)

Old(XE21 ,PCNET.MAIN ) Did( , ) type (R)

Old(XE21 ,B_CA_PC_SERVER_1 ) Did( , ) type (R)

Old(XE21 ,CA-OPERA PRODUCT ) Did( , ) type (R)

Old(XE21 ,CA-OPERACAIWXLOG��89) Did( , ) type (R)

Old(XE21 ,CA-OPERACAIWEMAL ESI) Did( , ) type (R)

Old(XE21 ,MVS_START_SERVER ) Did( , ) type (R)

Old(XE21 ,CAS9VTAMCW41�� ) Did( , ) type (R)

Old(XE21 ,W41�_SPAWN_SERVER ) Did( , ) type (R)

Old(XE21 ,#CAIENF EXTRACT ) Did( . , ) type (R)

In this example, the lines with XE21 indicate that the CAICCIconnection has been made to TSO21. LVL1NT is the NT machinewhere Unicenter TNG is installed.


Index

Special Characters@AMRGEN statement 5-47

AAbending event output, holding 5-27ACCEPT processing for CA-JobtracAccessing CA-Jobtrac

using a CLIST 6-4using ISPF 6-3

Adobe Acrobat PDFs 3-4AMR

disabling support for 5-46enabling support for 5-46

APF authorization 4-8API (Application Programming

Interface) 3-10APPLY processing for CA-Jobtrac 3-7Archive tape

block size 5-36disposition 5-36high-level qualifier 5-35retention period 5-36unit 5-35

Archiving NJE jobs A-8ARM (Automatic Restart Management

processing) 4-22Auto-queue job classes 5-29AUTO-SCHD, allowing 5-22Automatically scheduling events using

JCL, allowing 5-22

BBookManager files 3-4

C

CA LMP 2-11CA-11 4-5, 5-55CA-Blockmaster 2-21CA-C 2-11, 2-12CA-EARL 2-13CA-GSS

and CA-Jobtrac 2-15and NJE A-1modifying 5-2overview 2-12requirements 5-73

CA-HYPER-BUF 2-21CA-JCLTrac

DB2 setup for 5-58enabling 5-59UCT setup 5-58user control table 5-43user control table setup 5-58

CA-Jobtractoken 4-12

CA-Jobtrac Global Options paneldescription of options on 5-21sample panel 5-21

CA-Jobtrac subsystem 2-15CA-Jobtrac WorkStation 3-10, 5-71CA-Librarian 3-9

interaction with CA-Jobtrac 2-21modules 3-9

CA-Librarian supportsupport 5-29

CA-Multi-Image Integrity, interaction withCA-Jobtrac 2-21

CA-Multi-Image Manager, interaction withCA-Jobtrac 2-21

CA-Panvaletinteraction with CA-Jobtrac 2-22modules 3-8

CA-TCC (CA-Total Client Care) 8-4

Index X-1

CA-TLC: Total License Care 8-7CA-View

interaction with CA-Jobtrac 5-69interface 2-22interface with 5-69

CA-XPS 2-13CAICCI 2-13, 5-73, B-1CAIENF 2-14CAIMAC library 2-6CAIRIM 2-12CAS9 procedure 3-9Catalog error response 5-27Checkpoint data set

description 2-5placement considerations 2-18RAMAXCC JOBTRAnn Option 4-33

CLASS statement 5-62CLIST allocations, updating 5-18Command set scheduling, PDS for 5-37COMMNDxx, modifying 6-2Condition code checking 4-33Conversion

general procedure 7-1notes 7-3security issues 7-1

CPM 4-27Cross node query, NJE 5-30Cross-Platform Scheduling

and Unicenter 5-73connecting systems B-1global variables 5-77IMODs 5-76

Customization job, STAGE1 4-2Customizing CA-Jobtrac WorkStation

Server 5-71

DDASD, required by CA-Jobtrac 1-11Data sets

allocated by STAGE2 job stream 4-10allocating 4-9

Data sets (continued)placement considerations 2-18recommended initial sizes 4-16

Data sets, CA-Jobtrac 2-5Date format 5-21Date library 2-8DB2

binding plans for CA-JCLTrac 5-67creating objects for CA-JCLTrac 5-65granting authority for

CA-JCLTrac 5-68DB2 setup for CA-JCLTrac 5-58DDDEF, defining 3-5DDNAME statement 5-63Dependencies, types of 1-8Distribution libraries, creating 3-5Documentation libraries 2-8documentation, unloading 3-4DSNAME statement 5-62DYNAMLOC 5-12

EEND statement 5-64Ending CA-Jobtrac 6-4Enhancements 1-3Environmental dependency

maximum running time 5-29number of retries 5-29retry interval 5-26

Execution dependencies, definition of 1-8exits, setting up 5-7

GGJTRTRT2, IEFTB724 linked to 3-8Global JCL variables library 2-8Global options

in JOBTRAnn 4-19procedure for using ISPF interface to

set 5-19setting using ISPF interface 5-19

X-2 CA-Jobtrac 3.5 Getting Started

Global termination IMOD 5-27Global variables 5-77GoalNet 5-4

HHardware requirements 2-9History data set name 5-37History file data set 2-5History file sequential data set 2-6History file, data set placement

considerations 2-19Holiday action time 5-24

IIEACMDxx, modifying 6-2IEAVMXIT, setting up 5-46IMOD, global termination 5-27IMODs

CA-GSS server 5-76INIT IMOD 5-13Initializing CA-Jobtrac internals 6-2initiation IMODs 5-12Installation

SMP/E tasks 3-2Installation job stream, STAGE2 4-7Installation Verification Procedure

contents of 6-5how to use 6-6preparing to perform 6-6procedure 6-7

Installing CA-Jobtrac 1-1Internals, initializing CA-Jobtrac 6-2Internet, Computer Associates site 8-4IPL 1-11IPL prompt 5-21IPLTABLE

@AMRGEN option descriptions 5-49@AMRGEN statement

descriptions 5-48@AMRGEN statements 5-47

IPLTABLE (continued)creating 5-47maintaining 5-43procedure 5-53syntax rules 5-47table 5-43

ISERVEstarting procedure 5-30subsystem name 5-26

ISPF interface, NJE considerations A-6ISPF interface, using to set global

options 5-19ISPF main menu, adding CA-Jobtrac

to 5-18IVP

contents of 6-5how to use 6-6preparing to perform 6-6procedure 6-7

JJCL

enabling automatic checking 5-59enabling checking 5-59sample for loading JCLDOC 3-3

JCL libraries 2-8, 4-9JCL library, production 2-8JCL library, temporary-use 2-8JCLDOC library

description of 3-3loading from the product tape 3-3sample JCL for loading 3-3

JCLTCTL table 5-43JES

cycling with CA-Jobtrac 2-17interaction with CA-Jobtrac 2-16

JES command character 5-24JES held job class, defining 5-11JES SYSOUT class 5-11JMF PDS 5-36

Index X-3

job class, defining 5-11Job classes 5-29Jobflow 3-10JOBTRAC task, security authorization

required for 2-24JOBTRACx data set

description 4-12JOBTRAnn

description of options 4-20setting options 4-19using multiple 4-19

KKey, LMP 3-9KEYS DD statement 3-9

LLibraries

CA-Jobtrac 2-7documentation 2-8JCL 2-8remote password library 2-8SCL 2-8temporary-use JCL 2-8

Library Definitions paneldescription of options on 5-35sample panel 5-35

Library or PDS management 4-9Link CA-Librarian modules 3-9Link CA-Panvalet modules 3-8Link IEFTB724 to GJTRTRT2 3-8LMP key 3-9Location IDs

000 2-3assigning 2-3default 2-3description 2-2

Locations, understanding 2-2

MMemory requirements 1-11

detailed 2-10summary 2-10

Merge the CA-Jobtrac API table 3-10Messages, deletable 5-22MIM, interaction with CA-Jobtrac 2-21Modules, converting to tables 5-43Multi-CPUs and primary CA-Jobtrac

system 5-28Multiple CA-Jobtracs 7-10

NNJE

cross node query limit 5-30node token, specifying 5-26support 5-26, A-1

OOptions in JOBTRAnn 4-19Overview of SMP/E installation 3-2

PPassword

requirement rules 5-82PDFs 3-4PDS for command set scheduling 5-37PDS for JMF 5-36PDS member 3-9PDS or library management 4-9Phone Services Directory 8-6Pre-installation considerations 2-9Primary CA-Jobtrac 5-28Print class archive 5-23Procedure libraries, updating 4-18Proclibs, updating 4-18Product tape

receiving for CA-Jobtrac 3-6


RRECEIVE

performing for CA-Jobtrac 3-6Receiving

CA-Jobtrac product tape 3-6Release enhancements summary 1-3Remote

password library 2-8password location entity 2-3

Remote scheduling 5-73Requirements

hardware 2-9software 2-9

Restart support 5-22REXX IMOD

maximum running time 5-29ROOT user ID 4-37RUN command

ADD commandCondition code checking 4-33

Running multiple CA-Jobtracs 7-10

SScheduling dependencies, definition

of 1-8SCL libraries 2-8Security

authorization required for JOBTRACtask 2-24

installation tasks requiringauthorization 2-24

Serializationby CA-Jobtrac 2-20by IBM VSAM processing 2-20

SMF records, suppressing writing of 5-6SMFPRMxx

customizing 5-6example 5-8

SMP/EACCEPT processing for

CA-Jobtrac 3-7

SMP/E (continued)APPLY processing for CA-Jobtrac 3-7considerations 2-18distribution libraries, creating 3-5installing CA-Jobtrac using 3-1Link CA-Librarian modules 3-9Link CA-Panvalet modules 3-8Link IEFTB724 to GJTRTRT2 3-8overview of installation procedure 3-2RECEIVE processing for

CA-Jobtrac 3-6target libraries, creating 3-5

Software requirements 2-9SPACE command

enabling 5-54STAGE1 customization job

description 4-2running 4-2

STAGE2 installation job streamdescription 4-7modifying and running 4-7running 4-7

StarTCC, through CA-TCC (CA-TotalClient Care) 8-4

Starting CA-Jobtrac 6-3Step execution detail, printing 5-23SUBROOT keyword 4-37Summary of release enhancements 1-3Support Phone Services Directory 8-6SVCs not required 1-11Sysout capture

CA-View interface for 5-69defining classes for 5-31enabling 5-24line limit specification 5-29requeue to another product 5-33size specification 4-2unit specification 4-2volser specification 4-2

Sysout capture filecreation of 4-10data set placement considerations 2-19

Index X-5

Sysout capture file (continued)determining size, general 4-14messages associated with 4-14setting up 4-14

Sysout Capture Options paneldescription of options on 5-31

Sysout print class 5-23System options, installation

considerations 2-23

TTables 5-43Target libraries, creating 3-5TCP/IP 5-73, B-2Technical Support Phone Services

Directory 8-6Temporary-use JCL libraries 2-8Termination IMOD 5-27TNG

communicating with 3-10cross-platform scheduling 5-73optional DD statements for TSO

users 5-17remote password library 2-8REMTCRED JOBTRAnn Option 4-34SUBROOT JOBTRAnn Option 4-37XPLATRERUN JOBTRAnn

Option 4-43token 4-12, 5-2, 5-71, A-2TRACAUTH table 5-43

description 5-9TRACMAC parameters

optional 4-5required 4-2

TRACRnnn 2-8Troubleshooting 8-1—8-9TSO procedures

optional DD statements for users 5-17required DD statements for users 5-16updating 5-16

UUCT keyword, use of 5-61UCT setup for CA-JCLTrac 5-58Unicenter TNG

communicating with 3-10, B-1cross-platform scheduling 3-10, 5-73,

B-1optional DD statements for TSO

users 5-17remote password library 2-8REMTCRED JOBTRAnn Option 4-34SUBROOT JOBTRAnn Option 4-37XPLATRERUN JOBTRAnn

Option 4-43Unicenter TNG Framework for OS/390

componentsCA LMP 2-11CA-C 2-12CA-EARL 2-13CA-GSS 2-12CA-XPS 2-13CAICCI 2-13CAIENF 2-14CAIRIM 2-12

overview 2-11UNIX B-1unloading documentation 3-4Updating

LMP key 3-9Upgrading

overview 7-1User control table

CLASS statement 5-62creating 5-61DDNAME statement 5-63DSNAME statement 5-62END statement 5-64example 5-64explained 5-60for CA-JCLTrac 5-43setup for CA-JCLTrac 5-58


User control table (continued)using 5-61

VVersion 3.4

compatibilities with Version 3.5 7-2incompatibilities with Version 3.5 7-2

VINIT3using to process IPL messages 6-2using under the master subsystem 6-3

WWorkStation 3-10

XXPLATRERUN option 4-43

Index X-7

Man 02101135 e

Documents

dd naming

computer associates

dasd fast

audit backup

unicenter

automatic

computer associates

automatic