CA-Jobtrac

Getting Started
3.5

SP1 MAN02101135E

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 . . . . . . . . . Summary of Revisions in the Second Edition Summary of Revisions . . . . . . . . . . . Product Changes . . . . . . . . . . . . . Documentation Changes . . . . . . . . . CA-Jobtrac Features and Benefits . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1-1 1-2 1-3 1-3 1-7 1-8 2-1 2-2 2-2 2-5 2-7 2-9 2-9 2-11 2-13 2-15 2-16 2-17 2-18 2-18 2-19 2-21 2-23 2-23 3-1 3-2 3-3 3-4 3-4 3-5 3-5 3-6 3-7 3-7 3-8 3-8 3-9 3-9 3-10 3-11

Chapter 2. Preparing for Installation . . . . . . . . CA-Jobtrac Concepts . . . . . . . . . . . . . . . . . . Understanding Locations . . . . . . . . . . . . . . . Understanding CA-Jobtrac Data Sets . . . . . . . . Understanding CA-Jobtrac Libraries . . . . . . . . . . . . . . . Preparing for Installation Considerations CA-Jobtrac Requirements . . . . . . . . . . . . . . Unicenter TNG Framework for OS/390 . . . . . . CA-Earl . . . . . . . . . . . . . . . . . . . . . . . . Subsystems and CA-Jobtrac . . . . . . . . . . . . . JES Usage . . . . . . . . . . . . . . . . . . . . . . Installation Tape Information . . . . . . . . . . . . SMP/E Considerations . . . . . . . . . . . . . . . . Data Set Placement Considerations . . . . . . . . . Serialization Considerations for Shared DASD Users CA-Jobtrac Interfaces with Other Products . . . . . System Considerations . . . . . . . . . . . . . . . . Security Considerations . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . .

Chapter 3. Installation Tasks . . . . . . . . . . . . . . . . . Steps to Take . . . . . . . . . . . . . . . . . . . . . . . . . . . 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) . .

Contents iii

Contents

Step 15: Installing the @JOBTRAC USS Command (Optional) . . . . . . . . . . . . . . . . . . . . . . Chapter 4. Customization Job Streams . STAGE1 Customization Job . . . . . . . . Running the STAGE1 Job . . . . . . . . STAGE2 Installation Job Stream . . . . . . Running the STAGE2 Job . . . . . . . . Ensuring APF Authorization . . . . . . Types of Data Sets Supported . . . . . . Allocating Data Sets . . . . . . . . . . . About the Sysout Capture File . . . . . Updating Procedure Libraries . . . . . . Using JOBTRAnn to Set Global Options The JOBTRAnn Options . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3-11 4-1 4-2 4-2 4-7 4-8 4-8 4-9 4-9 4-14 4-18 4-19 4-20 5-1 5-2 5-2 5-3 5-4 5-5 5-6 5-9 5-11 5-12 5-16 5-19 5-21 5-31 5-35 5-38 5-40 5-41 5-42 5-43 5-46 5-47 5-54 5-55 5-58 5-60 5-65 5-67 5-68 5-69

|

Chapter 5. Customization Tasks . . . . . . . . . . . . . Modify CA-GSS . . . . . . . . . . . . . . . . . . . . . . . . Step 1: Modify JCL . . . . . . . . . . . . . . . . . . . . Step 2: Modify CA-GSS Parameters . . . . . . . . . . . Step 3: Activate GoalNet . . . . . . . . . . . . . . . . . Step 4: REXX IMOD Sample Source (Optional) . . . . Customizing SYS1.PARMLIB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Setting Up Default Authorization Setting Up the JES3 Held Job Class . . . . . . . . . . . . . Defining Location Information (DYNAMLOC) and Initiation IMODs . . . . . . . . . . . . . . . . . . . . . . . . . . . . Updating Your TSO Procedures or CLIST . . . . . . . . . Setting Global Options . . . . . . . . . . . . . . . . . . . . Options on the CA-Jobtrac Global Options Panel . . . . Options on the Sysout Capture Options Panel . . . . . . Options on the Library Definitions Panel . . . . . . . . . Copy the PRODDATE Member . . . . . . . . . . . . . . . Copy the JMFSYM01 Member . . . . . . . . . . . . . . . . Copy the RESOURCE Member . . . . . . . . . . . . . . . Copy the EXCLPARM Member . . . . . . . . . . . . . . . Maintaining Table Modules . . . . . . . . . . . . . . . . . . Setting Up AMR Support . . . . . . . . . . . . . . . . . . . Creating IPLTABLE Entries (Optional) . . . . . . . . . . . Enabling the SPACE Command . . . . . . . . . . . . . . . CA-Jobtrac CA-11 Integration . . . . . . . . . . . . . . . . Setting Up CA-JCLTrac . . . . . . . . . . . . . . . . . . . Setting Up a UCT . . . . . . . . . . . . . . . . . . . . . Creating the DB2 Objects . . . . . . . . . . . . . . . . . Binding the DB2 Plans . . . . . . . . . . . . . . . . . . Granting Authority . . . . . . . . . . . . . . . . . . . . . Using Other Sysout Capture Products . . . . . . . . . . . .

. . . . . . . .

iv CA-Jobtrac 3.5 Getting Started

. . . . . . . . Initializing CA-Jobtrac Internals . . . . . 5-71 5-73 5-76 5-77 5-82 . . . . . Running Multiple CA-Jobtracs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 Production . . . . . . . . . . . . . . . . . 7-5 Recommended Procedures to Run 3. . . . . . . . . . . . . . . . . . . . . . .4 Production and 3. . 7-3 Checkpoint . . . Diagnostic Procedures . . . . . . . . .5 Feature Conversion Notes . . . . . . . . . . . .5 Test System . . . . . . . . . . . . . . . . . . . . . . . . . . Collecting Diagnostic Data . . . . . . . . . . . . . . . . . . . . . Accessing CA-Jobtrac . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CA-Jobtrac Cross-Platform Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2 Incompatibilities . . Accessing the Online Client Support System . . 7-3 PDS Data Sets . . . . . . . . . . . . . . . . . Upgrading. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements Table Chapter 6. . . Starting the CA-Jobtrac Task . . . . . . . . . . . 7-1 Memory Requirements . . . . . . . . . . . . . . . . . . . .4 Production to 3. . . . . . . . 8-1 8-2 8-3 8-3 8-4 8-4 8-5 8-5 8-6 8-7 Contents v . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3 Recommended Procedures for Upgrading Your 3. . . . . 7-2 Compatibilities . . . . . . . . . . . . . . . . . . . . . . . . 7-3 History . . . Accessing StarTCC . . . . . . . . . . . 7-1 Version Compatibilities and Incompatibilities . . . . . . . . . Troubleshooting . . . . . . . . . . . 7-4 Returning to Prior Version . . 7-7 Procedure to Run Multiple CA-Jobtrac STCs on Same CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Testing. . . . . . . . . . . . . . . . . . . . . . Interpreting Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . Contents of IVP . . . . . . . . . . . . . . . . . . . . . . . Global Variables for Cross-Platform Scheduling Cross-Platform Server ($UNIXPSJT) Password . Requirements for Using StarTCC . . . . . . . . . . . . . . . . . . . . . 6-1 6-2 6-2 6-3 6-3 6-4 6-5 6-5 Chapter 7. . . . . . . . . . . . . . . . . . . . . Accessing the Technical Support Phone Services Directory CA-TLC: Total License Care . . . . . . . . . . . . 7-3 Capture . . . . . . . . . . . . . . . . . . 7-10 Chapter 8. . . . . . . 7-8 Procedures for CA-Jobtrac in a Shared DASD Environment . . 7-2 Version 3.Contents Customizing CA-Jobtrac WorkStation Server . . . . . . . . . . . . . . . . . . . . CA-GSS Server IMODs . Ending the CA-Jobtrac Task . . . . . . . . . . 7-1 General Procedure . . . . . . . 7-2 . . . . . . . . . . . . . . Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . StarTCC Security . . . Startup and Verification Initialization and Startup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

. . . . . Unicenter TNG (NT) Installation and Considerations Index . . . . . . . . . . REXX Stack Information for NJE Jobs Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1 B-2 B-3 X-1 . . . . Job Submission . Product Versions and Maintenance Requesting Enhancements . . . . . . . . . . . . . Connecting Systems for Cross-Platform Scheduling . . . . . . . . . . . . . . . . . . . 8-8 8-9 8-10 A-1 A-2 A-3 A-4 A-5 A-6 A-8 A-9 A-9 Appendix A. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Contents Contacting Technical Support . Installation and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . NJE Support . . . . . . . . . . . . . Appendix B. . . . . . . . . . . . . . . . . . . . . . . . . . . .5 Getting Started . . . . . . . . . . . . . . . ISPF Interface . . . . . . . . . . . . . vi CA-Jobtrac 3. . . . Job Execution . . . . . . . . . . . . . . . OS/390 CAICCI Installation and Considerations . . . . . . . . . . . . . . Batch Archiving and JREPORT . . . . Job Termination . . .

Chapter 1. Inc. Chapter 1.5. CA-Jobtrac Version 3. and maintenance of CA-Jobtrac. This guide is written for systems software programmers and personnel responsible for the installation. implementation. Introduction This guide describes how to install the Computer Associates International.. Introduction 1-1 . proprietary software product.

1-2 CA-Jobtrac 3. ■ We made corrections to “Disabling AMR Support” on page 5-46.Summary of Revisions in the Second Edition Summary of Revisions in the Second Edition The second edition of this guide includes these changes (see revision marks in the margins): ■ We made changes to “Copy the JMFSYM01 Member” on page 5-40.5 Getting Started .

The @RSOURCE macro that maps the resource has changed to define the field RSCODE as two characters. Product Changes Version 3. and c would have previously been specified as RMG(abc). ■ Two-character Resource Codes The resource codes available in CA-Jobtrac have been expanded by allowing for two-character codes. If your exit examines this code. RSMG. returns the codes in a blank separated list. Blanks must now separate the codes if multiple codes are entered. Previously. Two affected areas require changes if you are using these features: @JOBTRAC and the REXIT user exit. This needs to be changed to RMG(a b c). CA-OPS/MVS II provides management and administration of critical path displays. this was implemented without requiring changes to your existing resources definition. At a minimum. The format of the parameter has changed to support the two-character codes. Chapter 1.5 of CA-Jobtrac contains the following new features: ■ Critical Path Monitoring Through integration with CA-OPS/MVS II. you need to make the appropriate changes to support the new format. In most cases.Summary of Revisions Summary of Revisions This topic explains changes to CA-Jobtrac and to the documentation. Also the returned stack entry for resources. instead of as a single value. For example. CA-Jobtrac can support the definition and monitoring of critical job flows within the CA-Jobtrac workload. the exit will require a reassembly to include the new @RSOURCE macro format. Unicenter TNG and Unicenter TNG MVS Event Manager Option (MEMO). CA-Jobtrac still supports the R= referback for single character resources in the RESOURCE member. b. @JOBTRAC is used from CA-GSS and GJTRABTR uses the RMG() parameter to specify the resources codes. Introduction 1-3 . codes a. the entry would have read: RSMG ABC Now it reads: RSMG A B C The REXIT resource exit needs to be altered to accommodate the two-character resources.

Second. JOBTERM. The WLM scheduling environment and WLM scheduling resource may be used to limit on which systems jobs execute.Summary of Revisions ■ UNIX System Services Interface The OS/390 UNIX System Services (USS) CA-Jobtrac interface allows communication with CA-Jobtrac from the USS environment. This new support provides increased recoverability for CA-Jobtrac. support for IBM's Automatic Restart Management Function is included in this version. ARM=. 1-4 CA-Jobtrac 3. or even what CPU resources are assigned to jobs. Also. and DSCLOSE) on remote platforms running Unicenter TNG or CA-Jobtrac Agent that do not originate with CA-Jobtrac. First. ■ DYNAMLOC Concatenations The DYNAMLOC facility for dynamically allocating the CA-Jobtrac location data sets has been enhanced to allow for data sets to be concatenated to the location DDNAMEs. CA-Jobtrac registers with ARM during initialization and deregisters at normal termination. an associated CA-Jobtrac command will be issued. This common component is distributed with Unicenter TNG Framework for OS/390 and can be used to write customized reports from the CA-Jobtrac checkpoint and history files. the ARM= keyword allows for disabling the ARM support. ■ Cross-Platform External Tracking CA-Jobtrac may be used to track external events (JOBINIT. Sample reports are provided. A new initialization keyword. When a specified event is detected.5 Getting Started . ■ ARM To improve recovery capabilities in CA-Jobtrac. ■ Workload Management and CA-Jobtrac CA-Jobtrac interfaces in two ways with IBM's Workload Manager (WLM). ■ CA-Earl Report Writing Support for the CA-Earl Report Writer product is included in this version. The interface can be called directly from the UNIX shell or from the IBM USS batch interface (BPXBATCH). which causes CA-Jobtrac to deregister from ARM if they occur. a WLM scheduling resource may be set ON when CA-Jobtrac begins execution and OFF when CA-Jobtrac terminates. a WLM scheduling environment may optionally be inserted into JCL during submission. can be used to specify abends that should not be restarted.

– CAPDMPS Allows for system dump output to be captured by the CA-Jobtrac sysout capture feature. – JCLTABL Specifies the maximum number of lines of JCL per JOB. On an IP (input) parameter. Chapter 1. – DISABLE Allows for CA-Jobtrac ISPF line commands to be disabled. dumps are not stored on the sysout capture file. – RAMAXCC Allows you to set the MAXCC default for jobs that are added using the RUN or ADD CA-Jobtrac ISPF commands. – JMFTABLE Allows you to set the size of the JCL Modification Table (JMF) to meet your needs. This value defines the maximum number of times a message is processed before the messages are considered in a loop and processing for the messages is terminated. which was not previously used. the NODE statement is checked to ensure only one NODE statement is found. – DUMPUJV Allows for suppression of dumps that are taken in the CA-Jobtrac IEFUJV exit due to problems accessing the CA-Jobtrac checkpoint. Besides a numeric value. The PROCESS PERIOD field is now syntax checked for valid process periods. Normally. – TNDOVLP Signals the CA-Jobtrac schedule load process whether to consider a TIME/DATE overlap as an error. you can specify N to indicate no condition code checking should be done. ■ Other New Options – AMRLCNT Allows you to specify the limit for processing of duplicate messages by the CA-Jobtrac Automatic Message Replies (AMR) feature. Introduction 1-5 .Summary of Revisions ■ Enhanced SCL LOAD Syntax Checking In the SCL column 58. the presence of any character in this column causes the SCL LOAD to ABORT. effectively removing the command from the online system.

Also.4 Name CHD34CLS CHD34DBR CHD34INS CHD34LIB CHD34MAC CHD34MLI CHD34PLI TRACLIB TRACCLST DBRMLIB TRACINST TRACMAC TRACMLIB TRACPLIB TRACPARM CA-Jobtrac 3.Summary of Revisions ■ SMP/E Environment Changes to Conform to Computer Associates Standards The target and distribution libraries for CA-Jobtrac now conform to the Computer Associates format.5 Getting Started .5 Name CHD35CLD CHD35XLD None. reworking the SMP/E structure placed all components in a single CSI. and CAICLIB CAIMAC CAIISPM CAIISPP PPOPTION 1-6 CA-Jobtrac 3. CAIMAC. CHD35XLD. and CHD35CLD CHD35LLD CHD35XLD CHD35MLD CHD35PLD CAILIB CAICLIB CAIMAC SAMPJCL. rather than in three CSIs. The changes in the data set names are listed below: CA-Jobtrac 3.

and Recovery Guide: User Exits. ■ Syntax diagrams are now standardized within the IBM BookManager format. This set contains a hardcopy CA-Jobtrac Getting Started guide and Version 3.5 differs from previous versions as follows: ■ The documentation set has been engineered to take advantage of the latest technology for online viewing. Introduction 1-7 .5 of CA-Jobtrac for OS/390 documentation in both IBM BookManager and Adobe Acrobat Reader format on the tape. TRACAUTH Security. book marking. Maintenance. ■ Unicenter TNG Framework for OS/390 is composed of the services formerly known as CA90s and Unicenter TNG Framework. and printing. and The Sysout Capture File. ■ These chapters and appendixes from the former CA-Jobtrac Installation and Maintenance Guide moved to the CA-Jobtrac Reports.Summary of Revisions Documentation Changes The documentation for CA-Jobtrac Version 3. See Reading Syntax Diagrams in the CA-Jobtrac Operator Guide for more information. keyword searching. ■ The CA-Jobtrac Getting Started guide replaces the CA-Jobtrac Installation and Maintenance Guide. Chapter 1. JFST Access Method.

in exact sequence. Scheduling dependencies determine if and when a given event is scheduled (for example. straightforward approach. and abort times so that events execute at peak efficiency. Execution dependencies determine when a scheduled event is submitted (for example. ■ Threshold scheduling. in the proper sequence. You can issue a single command to make sweeping adjustments to the current schedule. on the last workday of each month). after a specified data set is created). CA-Jobtrac schedules. 1-8 CA-Jobtrac 3. permanently.5 Getting Started . tracks. frequencies. submits. target. CA-Jobtrac schedules and submits events based on dependencies you define for each event.CA-Jobtrac Features and Benefits CA-Jobtrac Features and Benefits The CA-Jobtrac primary function is to automate production scheduling. with little or no manual intervention. Once an event is defined to the system. at the proper times. and dependencies for each event in a logical. ■ Dependency scheduling. no further action is required to schedule that event or set of events. ■ No complex calendar definitions. CA-Jobtrac offers diverse methods to create schedules. They will be scheduled on the proper days. without rigid time schedules. Scheduling parameters define the cycles. the first and every time. These are: ■ ISPF EDIT to code the member with SCL (Schedule Control Language) ■ GSO (Generate Schedules Online) panels that gather information and generate the SCL Production Scheduling Features The following are features of the CA-Jobtrac production scheduling component: ■ Total automation of event scheduling. CA-Jobtrac builds a dynamic calendar each workday to process scheduled events. ■ Mass schedule alterations. and records events at the proper time. CA-Jobtrac lets you set start. You can adjust submission times forward or backward up to 24 hours for a specific event or all scheduled events. automatically. Unlike schedulers that require you to build a daily processing calendar for every day of the year.

CA-Jobtrac indicates the tape volumes needed for production during the processing day. Using CA-Jobtrac. REXX CA-Jobtrac takes full advantage of Computer Associates implementation of REXX. schedule forecasting. and online or printed reports. You can schedule REXX IMODs (Intelligent Modules) just as you have always done for events. DASD space analysis. such as event submission. @JOBTRAC gives you the ability to obtain information about the current schedule and to change the current schedule using an IMOD. Included are online event documentation. event history analysis. CA-Jobtrac accommodates the dynamic realities of production control. you can quickly and easily add on-demand events to the schedule for CA-Jobtrac processing. You can specify that the creation or update of a data set triggers some event. Once an event is scheduled. Using IMODs as dependencies adds unlimited power to CA-Jobtrac by giving you complete flexibility in deciding when to schedule an event. You can have one person per group take care of their scheduling needs (up to 254 separate locations). it is automatically submitted when all dependencies are satisfied. and status reports. @JOBTRAC was created. ■ Production control tools.CA-Jobtrac Features and Benefits ■ Automatic JCL submission and event tracking. Introduction 1-9 . ■ Distributed and decentralized scheduling. or you can have one person take care of the scheduling needs of all groups. CA-GSS interacts with other Computer Associates products. The event is then tracked through completion. and you can use REXX IMODs as scheduling dependencies. giving you the ability to obtain information from even more sources and to provide CA-Jobtrac information to them. ■ Data set triggering. CA-Jobtrac provides an array of online inquiries. ■ On-demand event submission. ■ Tape volume pull lists. CA-Jobtrac also supports automatic JCL alteration in the form of overrides or date statements. Chapter 1. error-checking and reporting capabilities. @JOBTRAC uses CA-GSS (Global SubSystem). To increase this power even more.

JCL Management CA-Jobtrac offers various features that enhance JCL usage. or task modify (F) command automatically at scheduled times or at specific intervals. job step.automatically deletes or inserts specified JCL statements when an event is submitted by CA-Jobtrac. Condition code processing checks for specified condition codes being returned. you can: ■ Translate complex technical system messages into plain English messages ■ Release an event or schedule for submission when a specified system message is issued ■ Schedule a response to an outstanding message ■ Reply to system prompts System Command Scheduling CA-Jobtrac can issue any OS/390. Specifying Additional Condition Codes CA-Jobtrac gives you ways to impose condition code processing on a program. These features are: ■ AJO (Automatic JCL Override) . VTAM. ■ 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 the processor clock – Allow date arithmetic for dynamic date variables – Allow input definitions from multiple PDS libraries – Use over 40 dynamic variable assignments for date and time values 1-10 CA-Jobtrac 3. For example. or procstep.5 Getting Started .CA-Jobtrac Features and Benefits Automatic Message Recognition The CA-Jobtrac AMR (Automatic Message Recognition) facility enables you to monitor system messages and prompts and to respond to them automatically. If the condition code you define is violated. CA-Jobtrac imposes a dependency requiring you to check the event's output before successor events can be submitted. job. Even IPLs can be automated. JES.

and less than 120 cylinders of 3380 space. Additionally. ■ CA-Jobtrac uses standard PDS files. and you can specify that CA-Jobtrac automatically calculate and insert dates in the record. ■ No SVCs or IPLs are required for scheduler operation for most environments. You can then generate reports with the stored information. ■ Interval processing to submit an event multiple times during a processing period. Additionally. ■ No dedicated hardware is required. which is a powerful sysout archival and retrieval tool. Other Benefits Other important benefits include the following: ■ CA LMP. CA-Jobtrac interfaces with the CA-View product. Introduction 1-11 . you can direct CA-Jobtrac to automatically insert JCL dates and repeated records in your events.CA-Jobtrac Features and Benefits ■ By using the ADI (Automatic Date Insertion) feature. providing online access to recent sysouts and permanent archival to tape. Chapter 1. CA-JCLTrac can forecast what your JCL will look like on any given day. ■ CA-JCLTrac performs basic JCL syntax checking and gathers information about your JCL usage and stores it in a DB2 database or in a JCL extract file. ■ CA-Jobtrac requires less than 100KB of CSA below the line. no database language must be learned. Sysout Archival CA-Jobtrac automatically captures and archives specified sysout listings.

1-12 CA-Jobtrac 3.5 Getting Started .

Chapter 2. Preparing for Installation This chapter discusses ways for you to prepare for installation of CA-Jobtrac. Chapter 2. Preparing for Installation 2-1 .

Understanding Locations To effectively install and use CA-Jobtrac. and libraries. and libraries associated with location 004. workdays. workdays. it can only access calendars. Locations can be: ■ Physical. As another example. A location groups CA-Jobtrac entities to provide distributed control over production. and libraries an event uses ■ What functions a user can perform For example.CA-Jobtrac Concepts CA-Jobtrac Concepts The following topics introduce you to CA-Jobtrac locations. such as New York and Chicago ■ Logical. 2-2 CA-Jobtrac 3. The location ID is a three-digit code used by CA-Jobtrac to determine the following: ■ Which calendars. you need to understand CA-Jobtrac locations. if Susan has only location 010 associated with her with delete and add functions allowed. if schedule PAYROLL1 has location 004 associated with it.5 Getting Started . data sets. such as accounting department and shipping department What Entities Have Locations The following CA-Jobtrac entities have a location associated with them: ■ Libraries ■ Users ■ Holiday calendars ■ Cyclic calendars ■ Workdays ■ Schedules ■ Events Location IDs Locations are defined by a location ID. she can only delete an event with location 010 associated with it.

and 0JOBARCH tasks always have location 000 associated with them. – A user has specified a default location using the PROFile command. The following explains its significance: ■ In general. ■ The 0ARCHIVE. Holiday calendars are defined to CA-Jobtrac using the Holiday Calendars panel. Default Location Users have what is known as a default location. Cyclic calendars are defined to CA-Jobtrac using the Cyclic Calendars panel. 0SYSARCH. He has assigned location 226 as his default location ID. Bob has location 226. For a user. and 111 associated with him. Assigning Location IDs Location IDs are assigned to an entity as described in the following table: Entity Holiday calendars How a location ID is assigned Holiday calendar definitions include a location ID. without specifying a location ID for the event. All other entities in CA-Jobtrac are associated with one location ID only. Cyclic calendar definitions include a location ID. because that is Bob's default location. no default location ID is assumed. The default location ID is assigned by the user using the PROFile command. the user will use their default location ID. Preparing for Installation 2-3 . He adds an event to the current schedule. It is added with a location ID of 226. Cyclic calendars Chapter 2. For example. If DEFAULT0 is set to NO. 040.CA-Jobtrac Concepts Users can have multiple location IDs associated with them. This default is overridden by the following: – The JOBTRAnn option DEFAULT0 is set to NO rather than YES. Location 000 Location 000 has a significant meaning in CA-Jobtrac. the default location is 000 (zero). if a location ID is not specified for an activity.

A user can have temporary location IDs assigned using the Authorization Profile panel. For example. the schedule assigns the location ID. Schedules A schedule's location ID is assigned by the library in which the schedule member resides. you assign the location ID. the workdays have the same location ID as the schedule. User Workdays Workdays are associated with a location ID according to the schedule they are used in. For example. Within a schedule. Events Location IDs are assigned to events when they are placed on the current schedule. you can change the location ID for events. if the member is in the SCL library named TRACS003. you can change the location ID for workdays. TRACT002 specifies a temporary-use JCL library for location 002.5 Getting Started . All events in the schedule have location ID 003 assigned by default. A user assigns a default location ID using the PROFile command.CA-Jobtrac Concepts Entity Library's ddname How a location ID is assigned The last three digits of a library's ddname determine the location ID for everything in the library. Within a schedule. If an event is manually added. A user is assigned one or more location IDs using the TRACAUTH table. If an event is automatically added by a schedule. 2-4 CA-Jobtrac 3. the schedule's location ID is 003. By default.

) History File Data Set The history file is the audit backup file for CA-Jobtrac. If you run multiple CA-Jobtracs. The DD naming convention is: JOBTRACx (JOBTRACY is the default. and table services information. each one has a set of data sets associated with it. It is dynamic.CA-Jobtrac Concepts Understanding CA-Jobtrac Data Sets CA-Jobtrac uses a number of data sets that store working data. It tracks the history of completed events.) Chapter 2. and wait for execution. Preparing for Installation 2-5 . start. The DD naming convention is: JOBHISTx (JOBHISTY is the default. stores holiday and cyclic calendars. It is a VSAM file. 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 other CA-Jobtrac information such as global options. changing as events finish. The current schedule is the active schedule. stores change history. Loading a schedule adds its events to the current schedule.

The history data file stores the data referenced by the history file.CA-Jobtrac Concepts History File Sequential Data Set The history data file is the data component of the history file.) CA-Jobtrac Setup Files The CA-Jobtrac setup files contain global information used by CA-Jobtrac while it is processing. The DD naming convention is: CAPTURE (CAPTURE is the default. The DD naming convention for files in the PPOPTION data set is: TRACPARM (TRACPARM is the default. CA-Jobtrac uses this data set to improve the efficiency of scanning the history file.) Capture File Data Set The capture file is used to store the output from schedule loads and to archive SYSOUT data from CA-Jobtrac jobs. The DD naming convention is: SEQHISTx (SEQHISTY is the default.5 Getting Started .) 2-6 CA-Jobtrac 3.

) The RESOURCE member contains resource definitions you can assign to events as dependencies. In this way. issue the following modify command. The correct library to use is specified on the TRACPARM DD statement in the CA-Jobtrac started task procedure. To activate the options in a given JOBTRAnn member. one EXCLPARM member is defined for all CA-Jobtracs running on a system.) The JOBTRAnn member describes the environment in which CA-Jobtrac operates and customizes how CA-Jobtrac functions. where nn matches nn in the desired JOBTRAnn member: F taskname. or to run multiple CA-Jobtracs. EXCLPARM (EXCLPARM is the default. JOBTRAnn (JOBTRA00 is the default. You can use each of these members to test a different configuration of options. Within the PPOPTION library.CA-Jobtrac Concepts Differentiating CA-Jobtracs One or more TRACPARM libraries can be defined for all the CA-Jobtracs running on a system. and temporary-use JCL. schedules. date and JCL variables. Chapter 2. Each library is associated with a location.) The EXCLPARM member defines mutually exclusive events. Multiple JOBTRAnn members can be defined. Preparing for Installation 2-7 . one EXCLPARM member is defined for all CA-Jobtracs running on a system. Within the PPOPTION library. job documentation. you can provide distributed control over production. Understanding CA-Jobtrac Libraries CA-Jobtrac uses a number of PDS-type libraries to store production JCL.OPTS=nn RESOURCE (RESOURCE is the default.

a copy of the production JCL is made and put in a temporary-use JCL library member. Each member contains the following for an event: ■ Information about an event you want the operator to have. ■ Manual actions the operator is to perform.CA-Jobtrac Concepts Libraries Used The following libraries are used in CA-Jobtrac. The JMFSYM01 member contains JMF variable definitions. When you want to temporarily modify JCL before running it.) TRACTnnn (TRACT000 is the default. For example. The event then uses the JCL from the temporary-use library rather than the JCL library. Documentation TRACDnnn (TRACD000 is the default. JCL TRACJnnn (TRACJ000 is the default. The PRODDATE member contains ADI definitions. Member contains encrypted user ID and password information for events that are to be submitted to Unicenter TNG on a remote platform.) TRACRnnn (TRACR000 is the default.) TRACSnnn (TRACS000 is the default. Type Date file DD Naming Convention DATELIB Contents Each library contains a JMFSYM01 and a PRODDATE member (default member names). All members in the library are associated with that location ID by default.) Remote Password SCL Temporary-use JCL 2-8 CA-Jobtrac 3. ■ Messages to be printed for the event's entry on the JREPORT3 Schedule Report.) Each member contains the production JCL that is run for scheduled events. The last three digits (nnn) of a library's ddname correspond to a location ID.5 Getting Started . TRACT002 specifies a temporary-use JCL library for location 002. Each member contains a schedule control language data set.

CA-Jobtrac uses standard IBM interfaces to accomplish scheduling. CA-Jobtrac Requirements The following sections describe the hardware and software required for successful CA-Jobtrac operation. There are no hooks. and other installation-specific information. volumes.Preparing for Installation Considerations Preparing for Installation Considerations Before starting the installation procedure. Chapter 2. Preparing for Installation 2-9 . and all other functions. sysout capture. or other nonstandard interactions with your operating system. zaps to IBM code. ■ Complete pre-installation worklists to plan data set names. Peripheral Devices CA-Jobtrac supports all devices supported by unmodified versions of the supported operating systems. you should ■ Read the installation documentation. Hardware Requirements CA-Jobtrac is supported on any IBM supported or IBM-compatible mainframe computer capable of supporting unmodified versions of the indicated operating systems. ■ Consider various preparing for installation issues. Software Requirements CA-Jobtrac is supported under any IBM supported operating systems and ISPF.

Preparing for Installation Considerations Detailed Memory Requirements The following table describes the memory requirements for CA-Jobtrac: Component Internals and exits Job table VMXT tables JMF table AMR (Automatic Message Recognition) table ADR (Automatic Dataset Recognition) table SCS (System Command Scheduling) table CCPF (Condition Code Program Filters) table Checkpoint index (for a 4 cylinder checkpoint)* ECSA Usage 100KB 30KB 30KB 140KB 380KB 20KB 57KB 27KB 111KB CSA Usage 60KB --------Total 160KB 30KB 30KB 140KB 380KB 20KB 57KB 27KB 111KB Note: * More ECSA is required for larger checkpoint files.5 Getting Started . ** ISERVEs are optional. It is CHD3500. Summary Memory Requirements The following table summarizes the memory requirements for CA-Jobtrac: ECSA Usage 903KB FMID CA-Jobtrac has one FMID. but each one used requires 96KB of ECSA. CSA Usage 60KB Total 963KB 2-10 CA-Jobtrac 3.

CA LMP The CA License Management Program provides a standardized and automated approach to the tracking of licensed software. Chapter 2. Preparing for Installation 2-11 . It uses common realtime enforcement software to validate the client's configuration. CA-Jobtrac requires the CA LMP service. CA LMP reports on activities related to the license. some of these services may already be installed. This section presents an overview of each of these services. See the Unicenter TNG Framework for OS/390 Getting Started and Administrator Guide for more information. The routines which accomplish this are integrated into the CAIRIM service.Preparing for Installation Considerations Unicenter TNG Framework for OS/390 CA-Jobtrac REQUIRES the following Unicenter TNG Framework for OS/390 Common Services: ■ CA LMP ■ CA-GSS/CA-GREXX ■ CAIRIM CA-Jobtrac optionally uses the following Unicenter TNG Framework for OS/390 Common Services: ■ CA-C Runtime ■ CA-EARL ■ CA-XPS ■ CAICCI ■ CAIENF ■ ViewPoint If other Computer Associates products are installed at your site. usage and financials of Computer Associates products.

subsystems. CA-C CA-C Runtime is a runtime facility with reentrant capabilities. 2-12 CA-Jobtrac 3. For example. if any. CA-GSS enables Computer Associates products to communicate with each other easily. CA-Jobtrac requires the CA-GSS service. SMF exits. system-dependent code linked with the user program. CA-C Runtime uses a memory manager to handle dynamic allocation requests for small pieces of storage. This information can be used when determining how to schedule a particular job. CAI Resource Initialization Manager. There is little. CA-GSS allows CA-Jobtrac to access data gathered by CA-SYSVIEW/E.5 Getting Started .Preparing for Installation Considerations CA-GSS The Global SubSystem (CA-GSS) is a product which offers software that performs across many of Computer Associates' product families. and other installation requirements commonly encountered when installing systems software. This enables fewer calls to be made on the operating system resulting in faster allocation and deallocation. and is designed to help meet the increasing need of data center operations for quick access to information from many different sources. is the common driver for a collection of dynamic initialization routines that eliminate the need for user SVCs. Remote scheduling requires the CA-C Runtime service. Its modular architecture insulates CA-C Runtime programs from system and version dependencies. CA-Jobtrac requires the CAIRIM service. This allows for smaller user programs and easier maintenance. CAIRIM CAIRIM.

The CA-Earl service is required if you wish to produce CA-Jobtrac reports using the CA-Earl facilities. Chapter 2. Remote scheduling requires the CA-XPS service.Preparing for Installation Considerations CA-Earl The CA-Earl (Easy Access Report Language) Reporting Component is a user-friendly report definition facility with the power of a comprehensive programming system. is a communications facility that offers a simple yet flexible approach enabling Computer Associates solutions to communicate with one another. CA-XPS allows multiple copies of CA-Jobtrac (or CA-7 or CA-Scheduler) to participate in cross-platform scheduling on the same OS/390 image. which then forwards the request to a specific scheduling product. CA-XPS CA-XPS is the Cross-Platform Scheduling router. CAI Common Communications Interface. CAICCI CAICCI. It is used when Unicenter TNG requests a job to be executed on OS/390. Requests are sent from Unicenter TNG to CA-XPS. CA-Earl allows you to modify and print the contents and layout of a predefined Computer Associates product report using English-like statements. This facility provides a layer that isolates application software from the specifics of the communications environment. Preparing for Installation 2-13 . Remote scheduling requires the CAICCI service and CA-Jobtrac WorkStation.

ViewPoint CA-Jobtrac WorkStation requires the ViewPoint service. By centralizing operating system interfaces within CAIENF. Remote scheduling requires the CAIENF service. many features which were formerly available within a single solution can be shared across the entire product line. CAI Event Notification Facility. is an operating system interface service which offers a simple yet flexible approach for Computer Associates solutions to obtain data from the operating system.Preparing for Installation Considerations CAIENF CAIENF. 2-14 CA-Jobtrac 3.5 Getting Started .

Note: CA-GSS is part of Unicenter TNG Framework for OS/390. It dynamically installs a subsystem with this name. CA-GSS Support We require that you install CA-GSS prior to installing CA-Jobtrac. See the Unicenter TNG Framework for OS/390 documentation for information about GoalNet. CA-GSS must be set up to include networking support for all JES nodes in which CA-Jobtrac is to be used for NJE support. CA-GSS uses a subsystem named GOAL. Preparing for Installation 2-15 . Chapter 2. The CA-Jobtrac installation procedure STAGE2 allocates and populates the CA-Jobtrac required ISET data set. CA-Jobtrac will not install properly if the ISET is not available. This is done using the GoalNet features of CA-GSS.Preparing for Installation Considerations Subsystems and CA-Jobtrac CA-Jobtrac uses two subsystems: GOAL and JT35. Although you can run CA-Jobtrac without CA-GSS active. the CA-GSS CAILIB must be available to CA-Jobtrac. Caution CA-Jobtrac must have CA-GSS installed. You can use this ISET or define another for your own use. CA-GSS ISET Availability This ISET is for the product IMODs shipped with CA-Jobtrac.

JOBT@ characters. submission. JES2 Requirement If you are using the BSPACE parameter in the CONDEF statement defined in the JES2INIT file using characters @. and CA-Jobtrac extends those boundaries to include scheduling.5 Getting Started . and historical archival. Job tracking is performed by CSA resident subroutines loaded by the CA-Jobtrac startup procedures.EXITS(IEFU83) If you already have a SUBSYS(STC) statement you do not need to change it. or history archival.PARM=IPL). If you are using one of these characters. This statement can be specified as follows: SUBSYS(STC. you usually do not need to start VINIT3 during IPLs (S VINIT3. JES monitors a job from submission through printout.Preparing for Installation Considerations JES Usage All systems that run scheduled batch jobs must be able to communicate with the CA-Jobtrac checkpoint data set. JES3 Requirements Accomplish the following to use JES3 with CA-Jobtrac: ■ Add the JOBTRACx ddname to your JES3 and JES3CI procedures.PARMLIB. JES Interaction The CA-Jobtrac STC is active on all systems in the JES complex (shared spool environment). execution. The CA-Jobtrac checkpoint data set indicates events queued for submission. Pre-JES Requirement The VINIT3 task is required only for pre-JES console automation and possible pre-JES startup data triggering functions. 2-16 CA-Jobtrac 3. or $. #. or dynamically allocate it. The JES checkpoint data set indicates only those jobs that are currently queued for execution or printing. During initial testing or implementation. execution. ■ Add a SUBSYS(STC) statement to your SMFPRMnn member in SYS1. change it to a different character to avoid any problems. it will conflict with the internal verification procedure job JOBT@#$J. You can think of CA-Jobtrac as a logical extension to JES.

SAMPLES CAI. The following table describes the files on the tape used by CA-Jobtrac: File 009 011 013 014 032 033 . Preparing for Installation 2-17 .SAMPJCL REXX. To AUTO-SCHD events in a JES3 system. . standard-label cartridge which must be installed using SMP. except that the queue class and JOB statement AUTO-SCHD features are not supported.Preparing for Installation Considerations CA-Jobtrac works the same way with JES3 as it does with JES2. Cycling JES If you must cycle JES2 or JES3.PDFDOC SMPMCS sysmod. 082 Data Set Name CAI. CA-Jobtrac uses information from SMF exits to establish event status. If you do not. CA-Jobtrac will not work properly. you must also cycle CA-Jobtrac. Installation Tape Information CA-Jobtrac is distributed on a single. The cartridge is prepared in IBM SMP RELFILE (unloaded PDS) format. See the CA-Jobtrac Operator Guide for more information.BKMGR CAI. See the IBM SMP General Information Manual for information about IBM SMP RELFILE format. CA-Jobtrac does not scan the JES spool for job status.Fn " " " Description CA-Jobtrac Sample JCL library CA-Jobtrac Sample REXX library CA-Jobtrac BookManager files CA-Jobtrac Adobe Documentation files SMP Modification Control Statements SMP RELFILEs begin here " " " Chapter 2. you must use the step method.

Data Set Placement Considerations Carefully plan the placement of the following data sets. target. (See the "JFST Access Method" chapter of the CA-Jobtrac Reports. The checkpoint is a small data set that is updated by TSO users. However. CA-Jobtrac Checkpoint This data set is the key control point in the CA-Jobtrac system. review this entire installation guide before you begin the installation. the checkpoint data set must be on a shared pack. it should not be placed on any pack with suspended channel programs (such as page/swap data sets) or any pack that will draw significant reserve activity (such as catalog packs or JES checkpoint packs). The installation creates new global. Check with your SMP/E systems programmer if you have questions about your SMP/E environment. Reserves are not issued against this data set. and distribution zones. If you have not previously installed program products using SMP/E. This manual assumes that you are familiar with SMP/E. Two cylinders of 3390 space for each CSI should be sufficient for CA-Jobtrac functions and allow for growth required by future maintenance. If you plan to run CA-Jobtrac on multiple systems that share DASD. The checkpoint uses a proprietary format called JFST. Maintenance.) You should place the checkpoint on a non-SMS managed volume. and by events tracked through CA-Jobtrac.5 Getting Started .Preparing for Installation Considerations SMP/E Considerations You use SMP/E to install CA-Jobtrac. The checkpoint performs best on non-CACHE devices unless you are using DASD Fast Write (DFW). 2-18 CA-Jobtrac 3. by JES. and Recovery Guide for information about JFST.

You should place the sysout capture file on a non-SMS managed volume. It tracks the history of completed events. Other similar packages include Computer Associates Multi-Image Integrity and IBM's GRS (running with a channel-to-channel adapter). Most users will put it on shared DASD so that TSO users from each system can view sysouts. you should place it where your TSO users will get adequate response time. It should not be placed on the same pack as the checkpoint or on a pack with heavy I/O activity. If you plan to run CA-Jobtrac on multiple systems that share DASD. Serialization Considerations for Shared DASD Users If you run CA-Jobtrac on two or more systems sharing DASD. Sysout Capture File The sysout capture file stores captured sysouts for online viewing and subsequent archival. you might have a package that can convert reserves into enqueues. Also see “Using Other Sysout Capture Products” on page 5-69 for more information. Chapter 2. you should ensure reasonable I/O response times for this file. Computer Associates MSI and SDSI packages also convert reserves into enqueues. No reserves are issued against the sysout capture file. but are precursors to CA-Multi-Image Integrity. Preparing for Installation 2-19 . or deletion.Preparing for Installation Considerations CA-Jobtrac History File This data set is the audit backup file for CA-Jobtrac. the sysout capture file must be on a pack on your primary (event-submitting) CA-Jobtrac system. Although updated less frequently than the checkpoint. the history file must be on a shared pack. Since some CA-Jobtrac components keep table information in the history file. The data set can be SMS or non-SMS and would perform well on a CACHE device with DASD Fast Write (DFW). If you plan to run CA-Jobtrac on multiple systems that share DASD. and it is accessed online. The JOBHIST file cannot span volumes. printing. If you plan to use the sysout capture file as your primary sysout capture system. it is updated under reserves.

index. The important thing to note here is that these enqueues are obtained as a set and must be processed consistently.Preparing for Installation Considerations The following sections describe serialization considerations. including that of CA-Jobtrac. The following table discusses the key points necessary for CA-Jobtrac planning. if your package processes any of them. IBM's normal VSAM processing involves serialization. That is. ■ If you do not allow your package to convert the reserve. Major IBM Serialization Besides the CA-Jobtrac serialization described above. QNAMEs SYSZVVDS SYSVTOC Comments and Recommendations These enqueue/reserves are used to serialize various parts of system processing in VSAM. Considerations are as follows: ■ If you allow your package to convert the reserve. it should process all of them. Major CA-Jobtrac Serialization The following table describes CA-Jobtrac serialization issues: QNAME JOBHISTx RNAME HISTPOST Reserve? Yes Comments and Recommendations You may allow your package to convert this reserve. 2-20 CA-Jobtrac 3. Failure to do this can cause deadly embraces in any shared VSAM file processing. you should also exempt enqueue requests for QNAMES SYSDSN and SYSVSAM with RNAME of your history file's components (cluster. there should be no adverse effect on your system. and data) from global processing.5 Getting Started .

For more information about CA-Librarian. Chapter 2. Preparing for Installation 2-21 . “Customization Job Streams.PGM=JCL3 CA-HYPER-BUF Exclude the CA-Jobtrac files and programs. Multi-Image Integrity. you can use a CA-Librarian JCL library instead of a standard PDS JCL library.PGM=GJC TYPE=E. and Multi-Image Console. see “Serialization Considerations for Shared DASD Users” on page 2-19. MODE=EXCLUDE PROGRAM=GJTR CA-Librarian With CA-Jobtrac.” CA-Multi-Image Manager CA-Multi-Image Manager is Computer Associates family of software products that makes sharing resources in multi-image and multi-system environments safe and efficient. For serialization considerations when using CA-Jobtrac and Multi-Image Integrity. Multi-Image Integrity is used to share DASD. see the CA-Librarian support information in Chapter 3.Preparing for Installation Considerations CA-Jobtrac Interfaces with Other Products CA-Jobtrac interacts with other products as described in the following sections. “Installation Tasks” and the PDS and library management information in Chapter 4. CA-Multi-Image Manager consists of Multi-Image Allocation.PGM=GJC3 TYPE=E.PGM=GJTR TYPE=E. CA-Blockmaster Exclude CA-Jobtrac programs by adding the following to the CA-Blockmaster Exclude table: BLMTABLE BLMTABLE BLMTABLE BLMTABLE TYPE=E.

you must meet the following conditions: ■ You must be a licensed CA-SYSVIEW/E user.Preparing for Installation Considerations CA-Panvalet With CA-Jobtrac. “Installation Tasks” and the PDS and library management information in Chapter 4. This takes you to the CA-11 primary menu. see the CA-SYSVIEW/E installation manual. 2-22 CA-Jobtrac 3. CA-View See the CA-View interface information in “About the CA-View Interface” on page 5-69 for more information about CA-View. ■ You must have CA-SYSVIEW/E installed on your system. CA-Jobtrac enables you to use CA-SYSVIEW/E without exiting CA-Jobtrac (use the Q line command). you may access rerun/restart information by using the R line command. see Chapter 3. you can check the amount of free space on a particular volume or determine the availability of tape drives. you can use a CA-Panvalet JCL library instead of a standard PDS JCL library. see the REXX information in the CA-Jobtrac Extended Scheduling Services Guide. For more information about the CA-SYSVIEW/E interface. To use CA-SYSVIEW/E from CA-Jobtrac. CA-11 When rerun/restart is required and CA-11 is installed. and you navigate through the range of CA-11 functions. For example.5 Getting Started . You can also use CA-SYSVIEW/E with @JOBTRAC. For more information about CA-Panvalet. ■ Your TSO session must have access to the CA-SYSVIEW/E ISPF program and its associated files.” CA-SYSVIEW/E CA-SYSVIEW/E is a powerful system tool that enables you to access information about your system and what is running on it. For more information about @JOBTRAC. “Customization Job Streams.

IEFACTRT. CA-ACF2. and 64 must be recorded.Preparing for Installation Considerations System Considerations You should consider the following system options before installing CA-Jobtrac. IEFU84. For information about updating your TSO procedures. Preparing for Installation 2-23 . Security Considerations When installing and using CA-Jobtrac. “Customization Tasks. ■ Exit IEAVMXIT must be activated for AMR (Automatic Message Recognition) triggers. ■ CA-Jobtrac must execute from an APF-authorized library. For information about setting up the exit. see Chapter 5. IEFUSI.” ■ SMF record types 15. “Customization Tasks.” ■ The CA-Jobtrac-started task requires both SUBMIT and UPDATE authority under your security system (CA-Top Secret. “Customization Tasks” and “Defining Location Information (DYNAMLOC) and Initiation IMODs” on page 5-12. For information about updating your TSO procedures. you must consider: ■ Security needed to install and run the CA-Jobtrac product ■ Security for using the CA-Jobtrac features Chapter 2.” ■ DD statements can be added to your TSO logon procedures or CLISTs to use the ISPF/PDF features of CA-Jobtrac. IEFUJI.” For linkage editing requirements for the IEFU8x exits. They can be active through an IEFBR14 program.PARMLIB member SMFPRMxx information in Chapter 5. This sample can also be linked with aliases of IEFU84 and IEFU85. The CA-Jobtrac SAMPJCL library contains a sample IEFU83 exit. “Customization Tasks. named SAMPU83. or IEFU85 exit. For more information about use of SMF records by CA-Jobtrac. 30. RACF. see Chapter 5. and so on). ■ SMF exits IEFUJV. see Chapter 5. See the customizing SYS1. see Chapter 5. “Customization Tasks. see the appropriate IBM manuals. You can suppress the actual writing of these records to your SMF data set by coding an IEFU83. Contact your systems programming staff for help. 26. and IEFU83 must be active. ■ All TSO users require authority to update the CA-Jobtrac checkpoint and history data sets.

■ Enabling all TSO users. Authority Requirements to Run CA-Jobtrac If you are using a security system (such as CA-Top Secret. ■ Entering the CA-Jobtrac started task name in the appropriate authorized task tables. all system initiators. ■ Allocating and updating the SMP/E libraries. ■ Allocating the CA-Jobtrac distribution data sets. your security administrator might need to authorize you to perform the following tasks: ■ Allocating the installation libraries. give the CA-Jobtrac started task SUBMIT authority. TEMPJCL. SCL. ■ Enabling all TSO users to update the CA-Jobtrac history file.Preparing for Installation Considerations Authorization Needed for Installation If your installation uses a security system.5 Getting Started .PARMLIB when you are ready for execution. Usage Security for CA-Jobtrac CA-Jobtrac uses the following methods to secure its use: ■ TRACAUTH table ■ TRACX26 user exit You use only one of the methods for security. and DOC libraries. You should give the CA-Jobtrac task the same security attributes as production TSO user IDs. ■ Updating the chosen APF linklist libraries in SYS1. ■ Enabling or disabling TSO users to update JCL. ■ Adding the CA-Jobtrac cataloged procedures to a system procedure library. CA-ACF2. Regardless of the method you use. and JES to update the CA-Jobtrac checkpoint data set. ■ Giving SUBMIT authority to the CA-Jobtrac started task. the TRACAUTH table is still used to: ■ Specify a name for a location ■ Specify which users are notified of abends and error conditions 2-24 CA-Jobtrac 3. ■ Allocating the CA-Jobtrac execution libraries (target libraries). or RACF).

you run the job ASMAUTH to create a default entry in the TRACAUTH table. Which method you choose depends on the importance of these exceptions to you. Preparing for Installation 2-25 . or purge CA-Jobtrac information. The default entry is used for all TSO users not specifically defined in other entries. See Chapter 5.Preparing for Installation Considerations About the TRACAUTH Table The 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. About the TRACX26 Security Exit The TRACX26 user exit is called by the CA-Jobtrac ISPF dialog and by @JOBTRAC to verify a user's authority to view. delete. “Customization Tasks” for information about defining entries in the TRACAUTH table. update. Choosing a Method The available security methods essentially secure the same information. The provided sample is only a sample. During installation. and about the ASMAUTH job. add. Chapter 2. This is a client alteration of the product and may cause unpredictable results if not properly coded and tested. You can control access to the 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. A few exceptions are described below.

xxxxx.5 Getting Started .3) BMSG STATREC=SYNCSTAT This allows the sort work data sets to be allocated and the correct program to be called for the sort routine. JREPORT3 and CA-ACF2 When running JREPORT3 and using ACF2 for your security package it is possible that an S806 abend may occur for the program ICEMESA. The simple way around this is the following additions to your JREPORT3 JCL: //$ORTPARM DD DYNALLOC=(SORTWK. .xxxxxx. The TRACX26 user exit does not offer this security.4.Preparing for Installation Considerations Information Secured Specific schedule information for an event Discussion With TRACAUTH you can allow or prevent users from changing the following for an event: Date and time information (JAUTH=T) Dependency codes (DAUTH) The TRACX26 user exit does not offer this level of security. This would only occur for dynamically added sort work data sets that are secured by ACF2. Verification of the existence of JCL The OPTA=J parameter of TRACAUTH requires that JCL for an event being added to the schedule using the ADD or RUN command resides in the user's default location TRACJnnn JCL library. Some other messages that you may see running the JREPORT3 report: ACF999 ACF2 LOGGING.SY IFA1 4I REGISTRATION HAS BEEN DENIED FOR PRODUCT WITH OWNER=IBM CORP NAME=OS/39 2-26 CA-Jobtrac 3.

Have your listings available when you call. You must install into new CSIs even if you have a previous version of CA-Jobtrac installed. call Computer Associates Technical Support (see the CA-Jobtrac Reports. you should have an experienced SMP/E consultant available. and Recovery Guide for information about contacting Computer Associates Technical Support). Getting Help During Installation Keep a copy of your installation listings during the installation process. This chapter explains how to install CA-Jobtrac using the IBM SMP/E product. Installation Tasks 3-1 . Changes in DLIB allocation prevent using the previous version's CSIs. Computer Associates Technical Support also answers questions about SMP/E installation options (see the CA-Jobtrac Reports. If you are not familiar with SMP/E. Maintenance. Installation Tasks New SMP/E CSIs are created during the installation. Maintenance. and Recovery Guide for information about contacting Computer Associates Technical Support). Chapter 3. If you need assistance during CA-Jobtrac installation.Chapter 3.

You can remove the checklist from the guide and use it to record the completion of each installation step.” ___ “Step 3: Create SMP/E Libraries.” ___ “Step 2: Unload CA-Jobtrac Documentation.” 3-2 CA-Jobtrac 3. ___ “Step 1: Unload the SAMPJCL Library.” ___ “Step 14: Create a Dummy IEAVMXIT Exit (Optional).” ___ “Step 9: Link IEFTB724 to GJTRTRT2 (Conditional).” ___ “Step 12: Updating License Management Program (LMP) Key.” ___ “Step 13: Merge the CA-Jobtrac API Table (Optional).” ___ “Step 10: Link CA-Panvalet Modules (Optional). You can use this list as a quick reference to the steps involved in SMP/E installation.Steps to Take Steps to Take The following steps are required to install CA-Jobtrac.” ___ “Step 11: Link CA-Librarian Modules (Optional).” ___ “Step 7: Perform APPLY Processing.” ___ “Step 8: Perform ACCEPT Processing.” ___ “Step 15: Installing the @JOBTRAC USS Command (Optional).” ___ “Step 5: Create SMP PROC.” ___ “Step 4: Create the Target and Distribution Libraries.5 Getting Started .” ___ “Step 6: Perform RECEIVE Processing for CA-Jobtrac.

Create JCL for a job to load the SAMPJCL library from the CA-Jobtrac base tape.1 . Where shown. Verify that the job receives a return code of 0 (zero).DSN=CAI. // VOL=SER=xxxxxx.(29.SPACE=(CYL. UNIT=.2 ).RECFM=FB).SL. // DCB=(LRECL=8 . Use the JCL shown in the figure below as an example.DISP=(OLD..O=OUT1 / Chapter 3. The SAMPJCL library must be loaded to your system from the product tape shipped with CA-Jobtrac.REGION=2 48K // //SYSPRINT DD SYSOUT= // //SYSUT3 DD UNIT=xxx.JT.DISP=(. Run the job created in Step 1 to allocate and load the SAMPJCL library. 2.Steps to Take Step 1: Unload the SAMPJCL Library The SAMPJCL library includes CA-Jobtrac JCL and help members used during installation.(1 .LABEL=(9. Procedure Follow the steps below to allocate and load the SAMPJCL library: 1. and JCL examples.MSGCLASS=X // //STEP 1 EXEC PGM=IEBCOPY.CATLG.'JOBTRAC'.BLKSIZE=6 8 .1 )) // //IN1 DD DSN=CAI.KEEP).KEEP. notes.RLSE) // //SYSIN DD COPY I=IN1. // SPACE=(TRK.EXPDT=98 ) // //OUT1 DD DISP=(NEW.UNIT=unitname.SAMPJCL.PASS). Installation Tasks 3-3 . and VOL=SER= to where the SAMPJCL library is to be loaded. Sample Load JCL for SAMPJCL //jobname JOB (acct#). Members in the SAMPJCL library contain detailed instructions. <== YOUR DSN <== YOUR VOLSER // UNIT=unitname.DELETE).CLASS=A.VOL=SER=volser. specify the DSN=. 3.SAMPJCL.

Modify the JCL parameters to meet your installation's needs. Changes in the SMP/E packaging structure prevent using the previous version's CSIs.Steps to Take Step 2: Unload CA-Jobtrac Documentation CA-Jobtrac documentation is delivered three ways. Review the JCL in the CAINITE5 procedure. 3. refer to SAMPJCL members ADOBEDOC or BKMGRDOC. Procedure Take the following steps: 1. A CD containing CA-Jobtrac documentation accompanies the installation tape with both Adobe Acrobat and IBM BookManager formats. You MUST install into new CSIs even if you have a previous version of CA-Jobtrac installed. Run the CAINITE5 job to create the SMP/E libraries. You should receive a completion code of 04. To unload the documentation from the installation tape.5 Getting Started . The SAMPJCL library includes two members to unload the documentation from the installation tape either in Adobe Acrobat format or in IBM BookManager format. 2. New SMP/E CSIs are created during the installation. Step 3: Create SMP/E Libraries This step accomplishes the following: ■ Creates all the SMP/E libraries ■ Defines the SMP zones Member Used The JCL for this step is in member CAINITE5 in your CA-Jobtrac SAMPJCL library. 3-4 CA-Jobtrac 3.

Review the JCL in the HD35ALC procedure. Module IEFTB724 will be linked with CA-Jobtrac module GJTRTRT2 during the install. Edit CAIHD35 in SAMPJCL. Run the HD35ALC job to create the SMP/E target and distribution libraries.' parameter. 3. the modules will have to be linked together outside SMP/E. Modify the PROC parms to specify required parameters. Do not change the PTF='DUMMY. You should receive a completion code of 0 (zero). Procedure Take the following steps: 1. 3. 2. Member Used The JCL for this step is in member CAIHD35 in your CA-Jobtrac SAMPJCL library. as specified in “Step 9: Link IEFTB724 to GJTRTRT2 (Conditional)” on page 3-8. Verify the macro libraries specified on the SYSLIB DDNAME.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 Used The JCL for this step is in member HD35ALC in your CA-Jobtrac SAMPJCL library. 4. Procedure Take the following steps: 1. If you do not specify the AOSB4 ddname. Modify the JCL parameters to meet your installation's needs. Save the changes and move the CAIHD35 PROC into an available proclib. Verify the library specified on the AOSB3 ddname. Chapter 3. 5. 2. Installation Tasks 3-5 . Step 5: Create SMP PROC This step sets up the SMP/E PROC that will be used for all SMP/E processing.

Procedure Take the following steps: 1. 2. Run the HD35REC job to perform RECEIVE processing for CA-Jobtrac.5 Getting Started . 3-6 CA-Jobtrac 3. Member Used The JCL for this step is in member HD35REC in your CA-Jobtrac SAMPJCL library.Steps to Take Step 6: Perform RECEIVE Processing for CA-Jobtrac This step performs RECEIVE processing for the CA-Jobtrac base FMID and all its functions. 3. Modify the JCL parameters to meet your installation's needs. You should receive a completion code of 0 (zero). Review the JCL in the HD35REC procedure.

Run the HD35APP job to perform APPLY processing. Modify the JCL parameters to meet your installation's needs. Procedure Take the following steps: 1. Member Used The JCL for this step is in member HD35ACC in your CA-Jobtrac SAMPJCL library. Review the JCL in the HD35APP procedure. Member Used The JCL for this step is in member HD35APP in your CA-Jobtrac SAMPJCL library.Steps to Take Step 7: Perform APPLY Processing This step performs APPLY processing for CA-Jobtrac. You should receive a completion code of 0 (zero) or 4. Review the JCL in the HD35ACC procedure. Modify the JCL parameters to meet your installation's needs. Ensure you receive a completion code of 0 (zero) or 4. Procedure Take the following steps: 1. Run the HD35ACC job to perform ACCEPT processing. Installation Tasks 3-7 . Chapter 3. 3. Step 8: Perform ACCEPT Processing This step performs ACCEPT processing for CA-Jobtrac. 2. 2. 3.

Steps to Take Step 9: Link IEFTB724 to GJTRTRT2 (Conditional) This step links the IBM module IEFTB724 to the CA-Jobtrac GJTRTRT2 module. Skip this step if you included the AOSB3 ddname in 0 9rs7ac .

Run the HD35LLIB job to link the CA-Librarian modules. in the "CAIRIM Operations" chapter. Modify the JCL parameters to meet your installation's needs. If you are not using CA-Jobtrac to submit JCL from CA-Librarian. Review the JCL in the HD35LLIB procedure. Chapter 3. Step 12: Updating License Management Program (LMP) Key This version of CA-Jobtrac is in compliance with Computer Associates License Management Program (LMP). 3.Steps to Take Step 11: Link CA-Librarian Modules (Optional) This step relinks the CA-Jobtrac modules so that they include the CA-Librarian access method modules. You should receive a completion code of 0 (zero). The LMP Key Certificate is included as part of your distribution package. the PDS member referenced by the KEYS DD statement in the CAS9 procedure must be updated with the information supplied on the LMP Key Certificate. skip this step. 2. Member Used The JCL for this step is in member HD35LLIB in your CA-Jobtrac SAMPJCL library. As a result. For instructions on installing and tailoring the CA-Jobtrac LMP Execution Key. Procedure Take the following steps: 1. Installation Tasks 3-9 . under Using CA LMP. see the Unicenter TNG Framework for OS/390 Administrator Guide.

(Comment or delete any others. you should use the CA-Jobtrac product code (HD) for the PROD= value. If any of the steps completed with a return code greater than zero. you need to add the CA-Jobtrac load library (CAILIB) to the STEPLIB concatenation for the MERGE PROC step. The Sample JCL library distributed with Unicenter TNG Framework for OS/390 contains member WC20MRG. If you are installing CA-Jobtrac into a separate set of SMP target libraries. The following should be the only EXEC statement at the bottom of the member.) //HDAPPL EXEC WC2 MRG. The CA-Jobtrac library should be added AFTER the Unicenter TNG Framework for OS/390 CAILIB. correct the problem and resubmit. The CA-Jobtrac API table that must be merged is CAHDAPPL. if necessary. See the Unicenter TNG Framework for OS/390 documentation for installing Viewpoint tables.Steps to Take Step 13: Merge the CA-Jobtrac API Table (Optional) The CA-Jobtrac API (Application Programming Interface) is used for communication with CA-Jobtrac WorkStation. Because this table will establish an interface with the CA-Jobtrac address space.TABLE=APPL. 3-10 CA-Jobtrac 3. which is model JCL to merge individual product control tables into the common API tables. This step is only required if this interface will be used.5 Getting Started . Set up an EXEC statement at the bottom of the JCL for CAHDAPPL. You need to have CA-C Runtime installed. This must be merged with the common API table CA4FAPPL. Edit WC20MRG or make a copy of it in the CA-Jobtrac SAMPJCL library. Customize the JOB statement and in-stream JCL procedure variables.PROD=HD Submit the job and CAREFULLY review the output to verify that the merge process ran successfully. Caution The table merge output should be directed to the Unicenter TNG Framework for OS/390 CAILIB so that all product installations share the same common control tables.

You can find more information in “Setting Up AMR Support” on page 5-46. Installation Tasks 3-11 . be sure to specify the path for the command in the correct case. in the "Accessing CA-Jobtrac from Unix System Services (USS)" chapter. Chapter 3. The CA-Jobtrac Extended Scheduling Services Guide contains information on using the command. The HD35LUSS member contains instruction for customizing the JCL. To implement this feature the module must be linked with the IBM Language Environment for OS390 (LE390) and stored in a UNIX HFS system file. JTUSS. can be used to access CA-Jobtrac from IBM's Unix System Services using the @JOBTRAC commands currently used with CA-GSS and GJTRABTR. The object for the module is distributed in CAIMAC.Steps to Take Step 14: Create a Dummy IEAVMXIT Exit (Optional) Use job LINKMXIT in the SAMPJCL library to create a dummy exit. Step 15: Installing the @JOBTRAC USS Command (Optional) The CA-Jobtrac module. Customize the JCL for your environment and submit it to install the command. The SAMPJCL member HD35LUSS contains JCL to perform the link. Remembering that Unix is case-sensitive.

5 Getting Started .3-12 CA-Jobtrac 3.

STAGE2 Installation Job Stream The STAGE2 job stream is necessary to install CA-Jobtrac.Covered in this chapter ■ Customization tasks . The STAGE2 job stream allocates CA-Jobtrac data sets. updates your system-cataloged procedure library. The Process The STAGE1 customization job stream invokes an installation macro called TRACMAC. The STAGE2 job stream contains procedure updates. set up. See “STAGE2 Installation Job Stream” for more information. Chapter 4. See “STAGE1 Customization Job” for more information. The member STAGE1 in your SAMPJCL library is a sample of the assembler JCL needed to create the STAGE2 job stream. The TRACMAC macro contains statements you use to name libraries and their locations.Covered in Chapter 5 ■ Startup and verification tasks . which generates the STAGE2 job stream.Chapter 4. Customization Job Streams 4-1 . and to provide information for the STAGE2 job stream. and provides the installation verification procedure for CA-Jobtrac.Covered in this chapter ■ STAGE2 installation job stream . and implement CA-Jobtrac: ■ STAGE1 customization job stream . The STAGE1 job writes the STAGE2 job stream to the data set or PDS member that you specify (default is the SAMPJCL). which generates the STAGE2 installation job stream.Covered in Chapter 6 STAGE1 Customization Job Stream The STAGE1 customization job stream invokes an installation macro called TRACMAC. an installation verification procedure. The STAGE2 job stream is necessary to install CA-Jobtrac. Customization Job Streams The following phases are necessary to customize. and JCL to allocate remaining CA-Jobtrac libraries.

3. Running the STAGE1 Job Procedure Follow the steps below to run the STAGE1 job stream: 1. Edit member STAGE1 in the SAMPJCL library. Be sure to specify your CAIMAC macro library in the SYSLIB DD statement. Run the STAGE1 job to create the STAGE2 job stream.STAGE1 Customization Job STAGE1 Customization Job The STAGE1 customization job stream invokes an installation macro called TRACMAC. Review the JCL carefully.” and “Optional TRACMAC Parameters” on page 4-5). Verify that the assembler return code from the STAGE1 job is 0 (zero). This volume must contain enough contiguous space to satisfy the ASIZE= parameter. Edit the STAGE1 parameter values to meet your installation requirements (see “Required TRACMAC Parameters. 6.5 Getting Started . All parameters except the last one should be followed by a comma. Another common cause is changing a parameter and omitting the comma. This value must be at least 5. Required TRACMAC Parameters The following table describes the TRACMAC parameters that you must include: Parameter/Default ARCHVOL= Description The volser of the volume on which the sysout capture file is to reside. 2. TRACMAC defines numerous global values used to install CA-Jobtrac and generate the STAGE2 job stream. 4. making revisions to reflect your installation's requirements. If the return code is not 0. 5. The size in cylinders of the sysout capture file. ASIZE=100 4-2 CA-Jobtrac 3. A possible cause is bad or missing parameters. review the assembler output for messages that indicate what caused the error.

The high-level qualifier (see the INDXJ= parameter) is automatically added to the name. High-level qualifier for the CA-Jobtrac checkpoint and forecast data sets. The mid. New installations should specify Y. The volser of the volume on which the STAGE2 job is to place all CA-Jobtrac installation libraries. These are JFST data sets. The volser of the volume on which the forecast checkpoint is to reside. Customization Job Streams 4-3 . The name of the library that is to contain the production JCL. The fully-qualified data set name of the IMOD ISET into which CA-Jobtrac sample and required production IMODs will be installed. The volser of the volume on which the history file is to reside.and low-level qualifiers of the name you want to assign to the forecast checkpoint data set.and low-level qualifiers of the name you want to assign to the CA-Jobtrac checkpoint data set. See the Unicenter TNG Framework for OS/390 documentation for information about IMODs and ISETs. The mid. The primary system is the system on which all batch work will be submitted. CA-Jobtrac installation library high.and low-level qualifiers of the name you want to assign to the history file. STAGE2 job stream programmer name field.and mid-level qualifier to be used during allocation. FORECAST= FOREVOL= HISTVOL=CAI INDX=CAI INDXJ=CAI INDXV=CAI INSTVOL= ISET= JOBHIST= NAME='CA-JOBTRAC INSTALL' NEWSITE=Y SYSID= TRACJCL= Chapter 4.STAGE1 Customization Job Parameter/Default CKPTNAM= Description The mid. Approximately 10 cylinders are required. Reinstallations will not reallocate runtime libraries if N is used. The SMF ID of your primary CA-Jobtrac system. The high-level qualifier (see the INDXJ= parameter) is automatically added to the name. High-level qualifier for the CA-Jobtrac history file. The high-level qualifier (see the INDXV= parameter) is added.

See the TRACVOL parameter for related information. See the ARCHVOL parameter for related information. The volser on which the CA-Jobtrac checkpoint data set is to reside.5 Getting Started . See the INSTVOL parameter for related information. Unit specification for all remaining installation libraries and data sets. Unit specification for the CA-Jobtrac checkpoint data set.STAGE1 Customization Job Parameter/Default TRACTEMP= TRACVOL= UNITA=SYSALLDA UNITD=SYSALLDA Description The name of the library that is to contain the temporary-use JCL. Unit specification for the sysout capture file. UNITT=SYSALLDA 4-4 CA-Jobtrac 3.

CA-11 high-level index used on the CA-11 CAIISPM. You will probably need to specify nondefault parameter values to conform to your installation standards. Some have default values that allow the successful generation of STAGE2 JCL. See the Unicenter TNG Framework for OS/390 Getting Started for information about CA-GSS load libraries. Your preallocated CA-Jobtrac installation library. If this parameter is omitted.JT. JCL GROUP keyword. The block size (BLKSIZE) assigned to all libraries with a logical record length of 80 (LRECL=80) allocated in the CA-Jobtrac installation process. Your JES command character. This should be the same as the unit name in the WORK DD statement in the JOBTRAC3 procedure and should be accessible to all users. Parameter/Default ACCT=1 AUNIT=SYSALLDA Description Job accounting parameter. and CAILIB. Customization Job Streams 4-5 . indx defaults to the value of INDX. it is assumed the CA-GSS load modules are in the system linklist. specify this parameter. if required. The fully-qualified load library name into which the CA-GSS associated with this CA-Jobtrac was installed. This parameter can contain parentheses and commas. Default values are underlined. This parameter informs CA-Jobtrac of the correct character to use when issuing JES commands. If you have CA-11 installed. BLK=6080 CLASS=A GROUP=group GSSLOAD= INDX11= INSTLIB=indx. Specify the full name of this library. STAGE2 job stream execution class.SAMPJCL JESCMD=$ Chapter 4.STAGE1 Customization Job Optional TRACMAC Parameters The parameters described below are not required. CAIISPP. Unit name for batch/STC dynamic allocation.

JCL record RD statement. The new ISET data set name is specified in the ISET= keyword. STAGE2 job stream priority keyword. PROCLIB library. indx defaults to the value of INDX. STAGE2 job stream message class. The maximum size is 64 cylinders. STAGE2 job stream region parameter. MSGCLASS=A NEWISET=N|Y NOTIFY=userid PROCLIB=indx. Y specifies that a new ISET data set should be allocated. Used for all CA-Jobtrac online and batch execution procedures. TYPRUN parameter to be used in STAGE2.CAIPROC TSO user ID for STAGE2 JOB statement NOTIFY parameter.STAGE1 Customization Job Parameter/Default JFSTCNT=4 Description Number of cylinders required for the checkpoint data set. STAGE2 utility listings output class. N specifies that a new ISET data set named in the ISET= keyword exists.JT. This space must be contiguous. PRTY= RD= REGION=2048KB SYSOUT=* TYPRUN= 4-6 CA-Jobtrac 3.5 Getting Started .

Review all the preparation information to continue with the STAGE2 portion of your installation. 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-Jobtrac procedures ■ Copies and compiles CA-Jobtrac product IMODs (requires CA-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 Preparation The following preparation might be necessary for your installation. Information to Review Ensuring APF authorization Type of data sets supported Allocating data sets About the checkpoint data set About the sysout capture file Updating the procedure libraries Setting global options using JOBTRAnn See “Ensuring APF Authorization” on page 4-8 “Types of Data Sets Supported” on page 4-9 “Allocating Data Sets” on page 4-9 “Description of the Checkpoint Data Set” on page 4-12 “About the Sysout Capture File” on page 4-14 “Updating Procedure Libraries” on page 4-18 “Using JOBTRAnn to Set Global Options” on page 4-19 Chapter 4.STAGE2 Installation Job Stream STAGE2 Installation Job Stream The STAGE2 job stream is necessary to install CA-Jobtrac. It is created by the STAGE1 job. Customization Job Streams 4-7 .

Run the STAGE2 job stream. Review the JCL carefully. The SYSPUNCH statement in the STAGE1 job stream named the location of the STAGE2 job stream. 2. Edit member STAGE2. Note: CA-GSS CAILIB must be APF-authorized for the STAGE2 jobs to run. All the system logic necessary to run CA-Jobtrac is in place. In a shared spool complex. make sure that the CA-Jobtrac execution libraries are accessible from all systems. Note: The STAGE2 JCL member contains three jobs. 4-8 CA-Jobtrac 3. 5. making revisions to reflect your installation's requirements.STAGE2 Installation Job Stream Running the STAGE2 Job Procedure Follow the steps below to run the STAGE2 jobs: 1. Procedure Add the CAI CAILIB to the APFLIST or use IEBCOPY to move the CA-Jobtrac modules from the installation CAILIB to an appropriate library and perform an LLA REFRESH if needed.5 Getting Started . Ensuring APF Authorization Caution CA-Jobtrac modules must be executed from an APF-authorized library. Verify that each step of every job receives a return code of 0 (zero). 4. Make modifications to the STAGE2 job stream based on the information. You can separate the job steps into individual jobs if you want. Review all the STAGE2 preparation information in the remainder of this chapter. 3.

however. or a standard PDS access method. resource definitions. SMP/E examples.SAMPJCL Description JCL samples. and standard IBM partitioned data sets (PDSs or PDSE) for JCL submission and editing. Restrictions You can choose a PAN access method. IVP job. and exclusion definitions. must use the same access method. and other information helpful during installation. CA-Jobtrac setup library containing global options. TRACPARM your. Allocating Data Sets Data Sets Already Allocated The following table describes the data sets allocated earlier in the installation process: DDname SAMPJCL Data Set Name your.STAGE2 Installation Job Stream Types of Data Sets Supported CA-Jobtrac supports for the DD of TRACJnnn CA-Panvalet data sets. table services. exit samples. a LIBR access method. Customization Job Streams 4-9 . The temporary-use JCL library for each location must be a PDS or PDSE. You must use the TEMP temporary-use JCL command to edit JCL from CA-Panvalet or CA-Librarian.JT.PPOPTION Chapter 4. You cannot use the JCL command to edit JCL from CA-Panvalet or CA-Librarian.JT. CA-Librarian data sets. All JCL libraries on the same ddname.

History file. a CA-Librarian data set. Remote (Cross-Platform) credentials file. domains.PRODJCL Description JCL library. The data set is the key control point in the CA-Jobtrac system. This data set must be a standard PDS or PDSE. The checkpoint is a small data set.JOBTRACx JOBHISTx your.RMTPSWD JOBTRACx your. x specifies the CA-Jobtrac token.5 Getting Started . CA-Jobtrac SCL library.TEMP your.STAGE2 Installation Job Stream Data Sets Allocated by the STAGE2 Job Stream The following table describes the installation and execution data sets allocated by the STAGE2 job stream: DDname TRACJ000 Data Set Name your. This data set can be a CA-Panvalet data set. This data set is a formatted sequential (indexed) file that holds the compressed sysouts for CA-Jobtrac events. An initial format of at least 15 cylinders is required to hold SCL output. Encrypted user ID.DATELIB CAPTURE your. CA-Jobtrac setup library containing members for Automatic Date Insertion (ADI) and JCL Modification Facility (JMF). or a standard PDS or PDSE. This data set must be a standard PDS or PDSE. This library will contain schedule members coded using SCL (Schedule Control Language).JOBHISTx DATELIB your. and passwords for submitting work on remote systems (Unicenter TNG or CA-Jobtrac Agent). This data set must be a VSAM data set.SCL TRACR000 your. Sysout capture file. Temporary-use JCL library. CA-Jobtrac checkpoint data set. TRACT000 TRACS000 your.CAPTURE 4-10 CA-Jobtrac 3. See the text following the table for more information. JOBTRACx is a JFST data set. x specifies the CA-Jobtrac token.

DISP=SHR //DATEL 1 DD DSN=cai. For other locations. PDS library for storing event documentation and manual action information. For example: JLOC 1:CAI.DISP=SHR //DATEL 2 DD DSN=cai. Chapter 4. This data set must be a standard PDS or PDSE type.DATELIB(PRODD 1). use the JLOCnnn: PARM in your JMFSYM01 member.FORECAST TRACD000 your. For other locations. specify the following DDs in your PROCs or CLISTs: //DATELIB DD DSN=cai.DATELIB(PRODD 2). Customization Job Streams 4-11 . See the CA-Jobtrac Extended Scheduling Services Guide for information about using command sets. FORECAST your.TRACMDS Description PDS for holding CMDSET (command set) members.DISP=SHR / / / default location 1 location / 2 location / / JMF uses member JMFSYM01 in the DATELIB data set. This data set must be a standard PDS or PDSE type.STAGE2 Installation Job Stream DDname TRACMDS Data Set Name your.DOCLIB ADI uses member PRODDATE in the DATELIB data set for location 001. This data set lets you load a schedule and produce forecast reports without affecting your production schedules.DATELIB(JMFSYM 2) / 2 location / See SAMPJCL members JMFSYM01 and PRODDATE used later in the IVP.DATELIB(PRODDATE). Alternate JFST data set used for schedule forecasting.

JOBTRACx checkpoint Differentiating CA-Jobtracs The x in the ddname is the token that is used to identify this CA-Jobtrac system. Maintenance.) You should place the checkpoint on a non-SMS managed volume. and Recovery Guide. see the "JFST Access Method" chapter of the CA-Jobtrac Reports. The checkpoint performs best on non-CACHE devices unless you are using DASD Fast Write. (See the "JFST Access Method" chapter of the CA-Jobtrac Reports. and hundreds of local and remote TSO users who perform on-demand and exception processing. However. In shops with an excess of 500 scheduled events per shift. JOBTRACx your.STAGE2 Installation Job Stream Description of the Checkpoint Data Set The data set is the key control point in the CA-Jobtrac system. including dynamic schedule processors. and Recovery Guide for information about JFST. If you plan to run CA-Jobtrac on multiple systems that share DASD. The checkpoint is a small data set that is a relational JFST database that contains all current schedule data. it should not be placed on any pack with suspended channel programs (such as page/swap data sets) or any pack that will draw significant reserve activity (such as catalog packs or JES checkpoint packs). It can be A-U. Location Any non-SMS controlled DASD Reserves are not issued against this data set. the checkpoint data set must be on a shared pack. The same token must be used for the checkpoint and the two history ddnames. the checkpoint can accumulate DASD EXCPs at an accelerated rate. 4-12 CA-Jobtrac 3. or 0-9. Maintenance. you should use the highest performance device possible for your CA-Jobtrac checkpoint data set. Each CA-Jobtrac running on a CPU must have a unique token specified. For information about JFST. It is updated and maintained by numerous components.5 Getting Started . We recommend that the token match the taskname with which CA-Jobtrac is started. which can add a thousand events at a time. See “Data Set Placement Considerations” on page 2-18. The checkpoint uses a proprietary format called JFST. The CA-Jobtrac checkpoint data set becomes quite active during heavy batch workloads. W-Z. In that case.

SEQHISTx your. Chapter 4. JOBHISTx your. We recommend that the token match the taskname with which CA-Jobtrac is started. Although updated less frequently than the checkpoint. Note: No VSAM performance software should be used for this data set. W-Z. and it is accessed online. The JOBHIST file cannot span volumes. so you should ensure reasonable I/O response times for this file.SEQHISTx History file sequential data set. it is updated under reserves. The same token must be used for the checkpoint and the two history ddnames.JOBHISTx History file This data set must be a VSAM data set. or 0-9. Location Any SMS or non-SMS controlled DASD. Some CA-Jobtrac components keep table information in the history file. Customization Job Streams 4-13 . or on a pack with heavy I/O activity.STAGE2 Installation Job Stream Description of the History File Data Set This data set is the audit backup file for CA-Jobtrac. It tracks the history of completed events. the history file must be on a shared pack. Each CA-Jobtrac running on a CPU must have a unique token specified. x specifies the CA-Jobtrac token. Differentiating CA-Jobtracs The x in the ddname is the token that is used to identify this CA-Jobtrac system. It can be A-U. CA-Jobtrac uses this data set to improve the efficiency of scanning the history file. Description of the History File Sequential Data Set The history data file is the data component of the history file. It should not be placed on the same pack as the checkpoint. If you plan to run CA-Jobtrac on multiple systems that share DASD. The data set can be SMS or non-SMS and would perform well on a CACHE device with DASD Fast Write (DFW). The history data file stores the data referenced by the history file.

but because of the CA-Jobtrac compaction routines and the EXCP access method. W-Z. Messages Associated With Sysout Capture Error routines automatically prompt the operator and temporarily stop operation if the capture file becomes full during normal operation.5 Getting Started . or 0-9. how many sysouts are captured. 100 cylinders can comfortably handle up to 1. CAPTURE your. For a more detailed discussion. it uses its space the most efficiently. The size of the sysout capture file depends on how many jobs are processed. You can expect a four-to-one ratio of compression over the JES spool. You can use this figure in determining how many cylinders you actually need for your sysout archival requirements. For example. We recommend that the token match the taskname with which CA-Jobtrac is started. Each CA-Jobtrac running on a CPU must have a unique token specified. The same token must be used for the checkpoint and the two history ddnames. how many days are kept in the online capture. 4-14 CA-Jobtrac 3. SEQHISTx (SEQHISTY is the default. (CAPTURE is the default) This data set is a formatted sequential (indexed) file. and Recovery Guide. About the Sysout Capture File The sysout capture file can be the largest CA-Jobtrac data set. along with appropriate replies. and the average line count of each listing. see the "The Sysout Capture File" in the CA-Jobtrac Reports. It can be A-U. x specifies the CA-Jobtrac token. The message identifier and an explanation are found in the CA-Jobtrac Operator Guide.STAGE2 Installation Job Stream This data set must be a VSAM data set.) Differentiating CA-Jobtracs The x in the ddname is the token that is used to identify this CA-Jobtrac system.CAPTURE Sysout capture file.5 million lines of sysouts. The operator can optionally suspend capture or close the file to tape and archive aged sysouts. Maintenance.

STAGE2 Installation Job Stream

Differentiating CA-Jobtracs The data set may be shared across systems but not within a single system. Location Any non-SMS controlled DASD. The sysout capture file stores captured sysouts for online viewing and subsequent archival, printing, or deletion. If you plan to use the sysout capture file as your primary sysout capture system, you should place it where your TSO users will get adequate 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 each system can view sysouts. No reserves are issued against the sysout capture file. You should place the sysout capture file on a non-SMS managed volume. Also see “Using Other Sysout Capture Products” on page 5-69 for more information.

Description of TRACMDS
TRACMDS your.TRACMDS PDS for holding CMDSET (Command Set) members. See the CA-Jobtrac Extended Scheduling Services Guide for information about using command sets. This data set must be standard PDS or PDSE.

Chapter 4. Customization Job Streams 4-15

STAGE2 Installation Job Stream

Recommended Initial Data Set Sizes The data set sizes shown in the table below are recommended during initial testing and implementation. You can adjust the sizes of the data sets after installation is complete. DDname JOBTRACx JOBHISTx DATELIB CAPTURE TRACMDS FORECAST Recommended Size 15 cylinders (JFST data set) minimum 50 cylinders (VSAM KSDS) 2 cylinders 100 cylinders (5 cylinders minimum) 1 cylinder 2 cylinders (JFST data set)

Allocating Additional Libraries The CA-Jobtrac distributed processing capabilities allow multiple libraries to support multiple locations. During initial testing and implementation, the default libraries for location 000 are sufficient. You can have as many as 255 additional locations and libraries. In the STAGE2 job stream, you can add definitions for the additional libraries.

4-16 CA-Jobtrac 3.5 Getting Started

STAGE2 Installation Job Stream

Library Naming Conventions The following table describes the naming conventions for each type of library. In each case, nnn corresponds to the location ID for a specific location. Library JCL Temporary-use JCL SCL Event documentation Location 000 Name TRACJ000 TRACT000 TRACS000 TRACD000 Additional Locations TRACJnnn TRACTnnn TRACSnnn TRACDnnn

Procedure to Allocate Additional Libraries Take the following steps in the STAGE2 job stream to allocate additional PDS-type libraries. If you use CA-Librarian or CA-Panvalet libraries, allocate the JCL libraries as recommended by the product's documentation. 1. For each library you want to create, there is a commented out ddname. 2. Change the library name in the copied definition. Each library should have the same data set attributes as the location 000 library. 3. For each library you allocate, add a DD statement in the JOBTRAC STC procedure and TSO CLIST or the DYNAMLOC member. Accomplish this regardless of the type of library used. See “Defining Location Information (DYNAMLOC) and Initiation IMODs” on page 5-12 for more information.

Chapter 4. Customization Job Streams 4-17

STAGE2 Installation Job Stream

Updating Procedure Libraries
CA-Jobtrac requires a number of cataloged procedures. These procedures are copied into your specified cataloged procedure library by the STAGE2 job. Requirement VINIT3, JOBTRAC3, and DUMPV3 must be in a procedure library for started tasks. Description of the Procedures The following table describes the CA-Jobtrac procedures contained in the CAIPROC library: Procedure JOBTRAC3 VINIT3 JREPORT3 GJTRVSCH GJTRMAHI GJTRMAIV GJTRMAJC GJTRVRLD DUMPV3 JCL#TCXR JCL#TDBL JCL#TDB2 JCL#TRAC Process Select a cataloged procedure library for CA-Jobtrac (such as SYS1.PROCLIB). Include the CA-Jobtrac procedures in it or add the CAIPROC PROCLIB to the proclib list in JES. Description Scanner task (started task) IPL initialization task CA-Jobtrac report utility Batch job access to schedule updating Batch job to delete records from the CA-Jobtrac history file Batch schedule maintenance Batch job to delete members from temporary-use JCL libraries Sample cataloged procedure to execute the sysout capture reload utility Diagnostic snap dump CA-JCLTrac Report Generator IBM's DSNUTILB utility CA-JCLTrac DB2 Loader CA-JCLTrac JCL Analyzer

4-18 CA-Jobtrac 3.5 Getting Started

some options are set using the global options panels only. and some options are set using either one. JMFTABL. RAMAXCC. some of the options set using JOBTRAnn are displayed on the global options panels. Additionally. In the command. you can create more than one JOBTRAnn member. Global Options in the STAGE2 Job Stream The STAGE2 job stream creates a default JOBTRAnn member in your SAMPJCL data set. JCLTABL. Location of JOBTRAnn Member JOBTRAnn must reside in the PPOPTION library. Customization Job Streams 4-19 . Before customizing. you can activate some of the options in a given JOBTRAnn member by issuing the following modify command. Once CA-Jobtrac is started. CAPDMPS. Some options are set by the JOBTRAnn member only. CA-Jobtrac global options are set using the JOBTRAnn member and by using the CA-Jobtrac global options panels. and WLMRSRC. but you cannot set them on the panels. and nn matches nn in the desired JOBTRAnn member: F taskname. you can change the values for the JOBTRAnn options or add options not in the job stream. Using Multiple JOBTRAnn Members By copying the default JOBTRAnn member. For more information about the global options panels. ARM. see Chapter 5. taskname is the name assigned to the CA-Jobtrac you want to affect. copy the sample to your PPOPTION data set. The nn in each member is unique. or if running multiple CA-Jobtracs.STAGE2 Installation Job Stream Using JOBTRAnn to Set Global Options CA-Jobtrac global options describe global values and the environment in which CA-Jobtrac operates. After running the STAGE2 job stream. New Options in Version 3. You can use each of these members to test a different configuration of options. SCHENV. DISABLE.5 The following options are new in this version of CA-Jobtrac: AMRLCNT.OPTS=nn Chapter 4. CPM. TNDOVLP. DUMPUJV.

) The default is 24. recycle the CA-Jobtrac STC. The syntax is: AMRLCNT ┌─24───┐ ──AMRLCNT=─┴─nnnn─┴──────────────────────────── To enable this option. All options must start in column 1 of a JOBTRAnn member. The syntax is: ARCBLK ┌─327 ───┐ ──ARCBLK=─┴─blksize─┴────────────────────────── To enable this option.STAGE2 Installation Job Stream The JOBTRAnn Options The following sections describe the options you can set in the JOBTRAnn member. 4-20 CA-Jobtrac 3. The default values (such as 24 for AMRLCNT) are used if the option is omitted. (AMRLCNT is an acronym for Automatic Message Recognition Tuning Parameter. AMRLCNT Specifies the number of identical message IDs received contiguously before deciding that a loop is occurring and issuing message TRAC029I. recycle the CA-Jobtrac STC. Each option's syntax is also presented. ARCBLK Defines the archive tape block size in multiples of 150-byte records (LRECL=150).5 Getting Started .

Dyyddd for volume identification. This value is also used to calculate the number of days to maintain an online copy of the sysout archive &INDEX entry. The syntax is: ARCDSN ──ARCDSN=arch. available through the CA-Jobtrac/ISPF dialogs.tape.dsname────────────────────── To enable this option. and the archive tape volume on which they reside. Chapter 4. The &INDEX entry. The syntax is: ARCRTN ┌─3 ────────┐ ──ARCRTN=─┴─tapertnpd─┴──────────────────────── To enable this option. ARCDSP Defines the normal DSN disposition of the archive tape. recycle the CA-Jobtrac STC. lists all sysouts captured for the defined period. recycle the CA-Jobtrac STC. a brief run history. See “ARCRTN.” The syntax is: ARCDSP ┌─CATLG────┐ ──ARCDSP=─┴─tapedisp─┴───────────────────────── To enable this option. Customization Job Streams 4-21 . CA-Jobtrac appends the date and time to the job name as Thhmm. recycle the CA-Jobtrac STC.STAGE2 Installation Job Stream ARCDSN Defines the first 35 characters of the archive tape data set name. ARCRTN Indicates the tape retention period in days to be used for the archive tape created by a 0ARCHIVE or 0SYSARCH task.

5 Getting Started .STAGE2 Installation Job Stream ARCUNT Defines the archive tape unit name (UNIT=unitname). 4-22 CA-Jobtrac 3. ARM Defines the type of IBM's Automatic Restart Management (ARM) processing you want. such as: 8 6.2 2. The syntax is: ARM ┌─NO──────────────┐ ──ARM=─┼─NONE────────────┼───────────────────── └─abend code list─┘ where: NO Indicates that ARM processing should not take place. the X indicates a generic abend and includes all abends that end with 37. See “ARCRTN” on page 4-21. This is the default. etc.X37 In this example. The syntax is: ARCUNT ┌─TAPE─────┐ ──ARCUNT=─┴─tapeunit─┴───────────────────────── To enable this option. (various out-of-space conditions) Note in the X37 entry. B37. abend code list Is a list of abend codes that should disallow normal ARM processing. recycle the CA-Jobtrac STC. the following are excluded from ARM processing: 806 abend (module not found) 0202 abend (sysout writer subtask has abended) D37. NONE Indicates that ARM processing should proceed without exceptions.

recycle the CA-Jobtrac STC. The ARM feature allows for automatic restart in the event of a product failure.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. To enable this option. Customization Job Streams 4-23 .ARM. The syntax is: Chapter 4. AUNIT Indicates a unit name for batch/STC dynamic allocation.ARM. For the purpose of restarting CA-Jobtrac with the same command that originally started the product.STAGE2 Installation Job Stream ARM Processing for CA-Jobtrac CA-Jobtrac offers an interface to IBM's Automatic Restart Management feature (ARM). the following may be used as an example.ARM. If you are currently using ARM. the CA-Jobtrac needs may well be met with the default profile currently defined. To define the couple data set: DEFINEDS SYSPLEX(PLEX79) DSN(COUPLE. This should be the same as the unit name in the WORK DD statement in the JOBTRAC3 procedure and should be accessible to all users.XE79P) DEFINE POLICY NAME(POLXE79A) REPLACE(YES) ELEMENT( ) A startup parameter (ARM=) may be used to customize the restart criteria. which results in termination.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.

AUTOC Defines the AUTO-SCHD recognition character to track jobs that are submitted outside of CA-Jobtrac control. To display what is being used now. To enable this option. <. #. 0 through 9. $. and / are valid characters. recycle the CA-Jobtrac STC. The recognition character must be either in the JCL being submitted in column 71 or the $AUTO step. see the CA-Jobtrac Operator Guide. from the CA-Jobtrac ISPF Main Menu enter SYS OPTS. The syntax is: AUTOC ┌─>────────┐ ──AUTOC=─┴─autochar─┴────────────────────────── where: autochar A through Z.5 Getting Started .STAGE2 Installation Job Stream AUNIT ┌─SYSDA────┐ ──AUNIT=─┴─unitname─┴────────────────────────── To enable this option. @. ?. 4-24 CA-Jobtrac 3. To use simultaneous operation of the AUTOC parameter on multiple CA-Jobtracs on the same system. >. For more information. then select number 1. recycle the CA-Jobtrac STC. define different AUTO-SCHD characters for each CA-Jobtrac on the system.

To enable this option. Customization Job Streams 4-25 . the job will be added and tracked by CA-Jobtrac. Once a job is submitted in this JES2 class. CAPDMPS Specifies the option to capture system dumps to the Sysout Capture File.STAGE2 Installation Job Stream AUTOQ Defines up to eight AUTO-QUEUE job classes in accordance with JES2. N is the default. If no job is on the checkpoint. The syntax is: AUTOQ ──AUTOQ=JES2classlist────────────────────────── where: JES2classlist A through Z and 0 through 9 are valid characters. Any value other than Y or N defaults to N. To display what is being used now. for external tracking of jobs. without the AUTOC character in column 71 or the $AUTO step. recycle the CA-Jobtrac STC. Chapter 4. the job will be tracked and or controlled by CA-Jobtrac. while N will not. recycle the CA-Jobtrac STC. Y directs Sysout Capture to capture system dumps. Jobs that are on the checkpoint with a 'Q' or a 'J' dependency will be controlled by CA-Jobtrac. The syntax is: CAPDMPS ┌─N─┐ ──CAPDMPS=─┴─Y─┴─────────────────────────────── To enable this option. Note: This parameter is only valid for JES2 users. See the CA-Jobtrac Operator Guide for information about using AUTO-SCHD character. from the CA-Jobtrac ISPF Main Menu enter SYS OPTS. then select number 1.

either shut down CA-Jobtrac with the BACK parameter or IPL. CMDLIB Specifies the name of the TRACMDS PDS defined by the STAGE2 customization job stream. The high-level qualifier must be an alias in the master catalog. The syntax is: CHKPT ──CHKPT=checkpoint. either shut down CA-Jobtrac with the BACK parameter or IPL. The syntax is: CMDLIB ──CMDLIB=tracmds.pds─────────────────────────── To enable this option. but no other naming restrictions apply.5 Getting Started . The TRACMDS member is a group of command sets. A command set is a group of commands executed using a single command. See the section about scheduling system commands (SCS) in the CA-Jobtrac Extended Scheduling Services Guide for more information. 4-26 CA-Jobtrac 3.dsname────────────────────── To enable this option.STAGE2 Installation Job Stream CHKPT Specifies the name of the CA-Jobtrac production checkpoint data set defined by the STAGE2 customization job stream.

and the CPM related fields and commands are available in ISPF. If CPM is turned on. Customization Job Streams 4-27 . By default.STAGE2 Installation Job Stream CPM Specifies to activate the CPM (Critical Path Monitor) function in CA-Jobtrac. Sample members PRODDATE and JMFSYM01 are copied over to the DATELIB data set later in the installation. Chapter 4. ALL forecasting SCL MUST have the keyword @FCAST=yyddd in the SCL member being forecasted.xxxxxxxx. see the CA-Jobtrac Extended Scheduling Services Guide. When specified. the CAIENF events for CPM are created. This means that no CAIENF events are created and no CPM related commands or data fields are available through the ISPF interface. either shut down CA-Jobtrac with the BACK parameter or IPL. recycle the CA-Jobtrac STC. The syntax is: DATELIB ──DATELIB=xxxxxxxx. DATELIB is the name of the standard PDS(LRECL 88) that contains control keys and JCL images for date card insertion and selectable in-stream JCL parameters or SYSIN overrides. The syntax is: CPM ┌─NO──┐ ──CPM=─┴─YES─┴───────────────────────────────── To enable this option. For more information on JMF. The CPM keywords in SCL are accepted even if CPM is inactive. DATELIB Specifies the name of the Automatic Date Insertion feature control library defined by the STAGE2 customization job stream. For more information on CPM.DATELIB──────────── To enable this option. the CPM function is inactive. see the CA-Jobtrac Extended Scheduling Services Guide.

4-28 CA-Jobtrac 3.5 Getting Started . The syntax is: DISABLE ┌── ┐ ─── ──DISABLE=──cmd┴─────────────────────────────── For example: DISABLE=A@C In this example the "A". recycle the CA-Jobtrac STC. either shut down CA-Jobtrac with the BACK parameter or IPL. the default. the event is posted with a JCL error. Otherwise. Also recycle TSO users. "@". This does not apply to calendars. The syntax is: DEFAULT0 ┌─YES─┐ ──DEFAULT =─┴─NO──┴──────────────────────────── To enable this option. and the INVALID COMMAND message displays if these commands are entered. and the "C" line commands are no longer valid for all CA-Jobtrac TSO users. DISABLE Specifies the JOBTRAC ISPF line commands one wishes to disable. YES. To enable this option.STAGE2 Installation Job Stream DEFAULT0 Specifies whether an event or schedule not found in a higher location than 000 can be read from location 000. or the schedule is posted with an 'M' dependency. denotes that the location does default to location 000 if the event or schedule is not found in the location specified.

Messages normally issued are still issued. If DFSVQUAL=NO is used. The syntax is: DFSVQUAL ┌─YES─┐ ──DFSVQUAL=─┴─NO──┴──────────────────────────── To enable this option. Chapter 4. the high-level qualifier used in SVQUAL is used for all users. Customization Job Streams 4-29 .STAGE2 Installation Job Stream DFSVQUAL Use to override default for allocation of data set names for viewing the sysout capture file. DUMPUJV Signals GJTRUJV2 (IEFUJV SMF exit) to create (Y) or not create (N) SVC dumps in the event that errors occur during allocation or access of the checkpoint. recycle the CA-Jobtrac STC. The syntax is: DUMPUJV ┌─Y─┐ ──DUMPUJV=─┴─N─┴─────────────────────────────── To enable this option. SVC dumps are still created in abend situations. Y is the default. default sysout view qualification is not done. recycle the CA-Jobtrac STC. Any value other than Y or N defaults to Y. that is.

If EXECTRLR is set to NO (setting xx to LE). Depending on how the COND is set. The syntax is: EXECTRLR ┌─NO──┐ ──EXECTRLR=─┴─YES─┴──────────────────────────── To enable this option. 4-30 CA-Jobtrac 3. No numerical RC is added to the COND statement. the step does not execute. If EXECTRLR is set to YES (setting xx to GT).xx).STAGE2 Installation Job Stream EXECTRLR At submission time.5 Getting Started . the job step does not execute. either shut down CA-Jobtrac with the BACK parameter or IPL. CA-Jobtrac flags events that it submits by adding the following step at the end of each event: //$J EXEC PGM=$A.COND=( . Only LE or GT is added. the job step executes.PARM=parm CA-Jobtrac uses this additional step to track events. The actual COND value is changed only by the option flag.

Customization Job Streams 4-31 . The list is specified as a string of one-character classes. To enable this option. Chapter 4. Class characters can be A-Z and 0-9. The JOB statement is examined for a class that is contained in the list specified. If the string '11RMS' as in U11RMS or CA11RMS is found in the procname or program name of an EXEC statement. without interceding blanks (that is. and the step is inserted only if a matching class is found. This applies only when RERUN=CA-11 is specified. The first three steps of a job are examined for a manually inserted CA-11 U11RMS step before the step is inserted. AEF23 specifies that classes A. E. class list Specifies a list of job classes that should have the step inserted. recycle the CA-Jobtrac STC. then the CA-11 step is not inserted. and 3 are to have the step inserted). NO Specifies that no jobs should have the U11RMS step inserted. Jobs to have the step inserted can be identified in three ways. A special class character (?) is available to specify that jobs without a class specified should have the step inserted. The syntax is: INSERTRMS ──INSERTRMS=─┬─ALL────────┬──────────────────── ├─NO─────────┤ └─class list─┘ where: ALL Specifies that all jobs submitted by CA-Jobtrac should have the U11RMS step inserted. 2. F.STAGE2 Installation Job Stream INSERTRMS This keyword specifies if and when a CA-11 U11RMS step should be inserted by CA-Jobtrac during job submission.

The default is 1000 and the ECSA usage is approximately 140KB with this value. The default is 9000. recycle the CA-Jobtrac STC. 4-32 CA-Jobtrac 3.5 Getting Started . either shut down CA-Jobtrac with the BACK parameter or IPL. either shut down CA-Jobtrac with the BACK parameter or IPL. The syntax is: JESCMD ┌─$─┐ ──JESCMD=─┴─x─┴──────────────────────────────── To enable this option. JMFTABLE Specifies the number of entries in the JMF table. This table uses private storage above the line for submission. The syntax is: JMFTABLE ┌─1 ──┐ ──JMFTABLE=─┴─nnnnn─┴────────────────────────── To enable this option.STAGE2 Installation Job Stream JCLTABL Specifies the maximum number of lines of JCL per job. Specifying 2000 would use approximately 280KB (and so on). This parameter informs CA-Jobtrac of the correct character to use when issuing JES commands. The syntax is: JCLTABL ┌─9 ──┐ ──JCLTABL=─┴─nnnnn─┴─────────────────────────── To enable this option. JESCMD Specifies your JES command character.

Chapter 4. recycle the CA-Jobtrac STC.STAGE2 Installation Job Stream LIBPGM Specifies the name for the CA-Librarian Master Library utility program. 0000 is the default. Customization Job Streams 4-33 . N effectively turns off condition code checking for these jobs. The syntax is: LIBPGM ──LIBPGM=─┬─libpgm──┬────────────────────────── └─AFOLIBR─┘ To enable this option.to four-numeric characters. RAMAXCC Specifies the MAXCC for a job that is added to the checkpoint using the ADD or RUN command. recycle the CA-Jobtrac STC. The syntax is: RAMAXCC ┌─ ─┐ ──RAMAXCC=─┼─nnnn─┼──────────────────────────── └─N────┘ To enable this option. The value specified must either be N or one.

recycle the CA-Jobtrac STC. the default is EVENT. and domain information to be sent with the event to Unicenter TNG or CA-Jobtrac Agent. RERUN Indicates the product that CA-Jobtrac is to interface to when performing job reruns and restarts. and the event name is used to retrieve the information from the remote password data set (TRACR000). The syntax is: REMTCRED ┌─EVENT──┐ ──REMTCRED=─┴─ALTMEM─┴───────────────────────── To enable this option.STAGE2 Installation Job Stream REMTCRED ALTMEM indicates the alternate JCL field in an event can be used to specify the remote password data set member name. recycle the CA-Jobtrac STC. password.5 Getting Started . See “INSERTRMS” on page 4-31. The syntax is: RERUN ┌─NONE──┐ ──RERUN=─┴─CA-11─┴───────────────────────────── To enable this option. The alternate name can be specified on the A= referback in SCL or by specifying the name in the Scheduled Event Detail panel when the event is on the checkpoint. This name is used when retrieving the user ID. If this keyword is not specified. 4-34 CA-Jobtrac 3.

When the event is restaged through ISPF. 2. Add an "O" dependency to the restaged event only if originally present. Chapter 4. Do not restage the event.STAGE2 Installation Job Stream RESTAGEABEND Specifies whether to restage jobs on abend. the "O" dependency is removed if not originally present. 2. If the event is not restaged. recycle the CA-Jobtrac STC. NO Results in the following: 1. The syntax is: RESTAGEABEND ┌─YES─┐ ──RESTAGEABEND=─┴─NO──┴──────────────────────── where: YES Results in the following: 1. 3. add an "O" dependency. Instead. To enable this option. Restage the event with a "J" dependency. The default is YES. releasing the "O" (even if originally present) or purging the job will release its successors and do a BYPASS RERUN PROFILE. Customization Job Streams 4-35 . and the restaged event will have a "J" dependency.

See RESTAGEABEND for the values of YES and NO.STAGE2 Installation Job Stream RESTAGECAT Specifies whether to restage jobs on catalog error. recycle the CA-Jobtrac STC. 4-36 CA-Jobtrac 3. See RESTAGEABEND for the values of YES and NO. The syntax is: RESTAGEJCLERR ┌─YES─┐ ──RESTAGEJCLERR=─┴─NO──┴─────────────────────── To enable this option. The syntax is: RESTAGECC ┌─YES─┐ ──RESTAGECC=─┴─NO──┴─────────────────────────── To enable this option. recycle the CA-Jobtrac STC.5 Getting Started . RESTAGECC Specifies whether to restage jobs on condition code. The default is YES. The syntax is: RESTAGECAT ┌─YES─┐ ──RESTAGECAT=─┴─NO──┴────────────────────────── To enable this option. The default is YES. See RESTAGEABEND for the values of YES and NO. The default is YES. RESTAGEJCLERR Specifies whether to restage jobs with JCL errors. recycle the CA-Jobtrac STC.

this value will be inserted on the SCHENV JOB statement parameter by CA-Jobtrac.STAGE2 Installation Job Stream SCHENV This is a 16-byte field that allows you to specify a default for all jobs. SUBROOT Indicates if a user ID of ROOT can be used when submitting work to Unicenter TNG or CA-Jobtrac Agent on remote platform. the default is NO. Chapter 4. If not specified. recycle the CA-Jobtrac STC. NO may be coded for this value so that insertion of the SCHENV parameter on the JOB statement does not occur as the default. Customization Job Streams 4-37 . NO is the default if the SCHENV keyword is not found. The syntax is: SUBROOT ┌─NO──┐ ──SUBROOT=─┴─YES─┴───────────────────────────── To enable this option. recycle the CA-Jobtrac STC. and the user ID ROOT is not allowed to be used. This value may be verified before job submission and could result in a JCL error with a W (WLM) dependency if coded incorrectly. Unless overridden. The syntax is: SCHENV ┌─NO───────────────┐ ──SCHENV=─┴─cccccccccccccccc─┴───────────────── To enable this option.

This is used only when PROFILE NOPREFIX is set (by default). This is only required if running multiple CA-Jobtracs. The syntax is: SVQUAL ──SVQUAL=qual────────────────────────────────── To enable this option. This is only required if running multiple CA-Jobtracs. SYNCSYS2 Defines the SMF system ID of the secondary submission system. 4-38 CA-Jobtrac 3.5 Getting Started . either shut down CA-Jobtrac with the BACK parameter or IPL. either shut down CA-Jobtrac with the BACK parameter or IPL. SYNCSYS1 Defines the SMF system ID of the primary submission system. Also recycle TSO users. See “Procedures for CA-Jobtrac in a Shared DASD Environment” on page 7-10 for more information.STAGE2 Installation Job Stream SVQUAL Specifies up to an eight-byte qualifier to put on front of data set names which CA-Jobtrac dynamically allocates for viewing. The syntax is: SYNCSYS1 ──SYNCSYS1=sysid─────────────────────────────── To enable this option. The syntax is: SYNCSYS2 ──SYNCSYS2=sysid─────────────────────────────── To enable this option. See “Procedures for CA-Jobtrac in a Shared DASD Environment” on page 7-10 for more information. either shut down CA-Jobtrac with the BACK parameter or IPL.

If the primary system is idle for more than the number of seconds defined by SYNCTOL. Maintenance. This is only required if running multiple CA-Jobtracs. and Recovery Guide for information about switching primary systems. See “Procedures for CA-Jobtrac in a Shared DASD Environment” on page 7-10 for more information. The syntax is: SYNCSYS3 ──SYNCSYS3=sysid─────────────────────────────── To enable this option. either shut down CA-Jobtrac with the BACK parameter or IPL. Customization Job Streams 4-39 . The syntax is: SYNCTOL ┌─3 ─┐ ──SYNCTOL=─┴─nnn─┴───────────────────────────── To enable this option. See the CA-Jobtrac Reports. The operator can switch primary submission duties at any time by issuing the ACTSYS=sysid modify command on the primary system. SYNCTOL Defines the number of seconds the primary submission system can be idle. Chapter 4.STAGE2 Installation Job Stream SYNCSYS3 Defines the SMF system ID of the backup submission system. either shut down CA-Jobtrac with the BACK parameter or IPL. the secondary system automatically issues a WTO to request primary event submission duties.

Y results in a TIME/DATE overlap being considered an error.STAGE2 Installation Job Stream TNDOVLP Signals the CA-Jobtrac schedule load process whether to consider a TIME/DATE overlap as an error. See the CA-Jobtrac Extended Scheduling Services Guide for information on the SCS table. A value from 100 to 5000 can be specified. N indicates that CA-Jobtrac will not flag a TIME/DATE overlap as an error. TSCMDSPA Specifies the maximum size for the SCS (System Command Scheduling) table. Y is the default. Larger values use more ECSA. The syntax is: TNDOVLP ┌─Y─┐ ──TNDOVLP=─┴─N─┴─────────────────────────────── Example: With option TNDOVLP=N. recycle the CA-Jobtrac STC.5 Getting Started . you get: DAILY1 22 1 1D DAILY With option TNDOVLP=Y. The syntax is: TSCMDSPA ┌─25 ──┐ ──TSCMDSPA=─┴─nnnn─┴─────────────────────────── To enable this option. either shut down CA-Jobtrac with the BACK parameter or IPL. Table size can only be increased after an IPL or a BACK of CA-Jobtrac. 4-40 CA-Jobtrac 3. you get: DAILY1 22 1 1D(M) DAILY <==TIME/DATE OVERLAP: MUST HAVE DEPENDENCY To enable this option.

A value from 100 to 5000 can be specified. The syntax is: TSDSNSPA ┌─1 ──┐ ──TSDSNSPA=─┴─nnnn─┴─────────────────────────── To enable this option. See the CA-Jobtrac Extended Scheduling Services Guide for information on the AMR table. Table size can only be increased after an IPL or a BACK of CA-Jobtrac. Larger values use more ECSA. Larger values use more ECSA. Chapter 4. either shut down CA-Jobtrac with the BACK parameter or IPL. See the CA-Jobtrac Extended Scheduling Services Guide for information on the ADR table. TSMSGSPA Specifies the maximum size for the AMR (Automatic Message Recognition) table. A value from 100 to 5000 can be specified. The syntax is: TSMSGSPA ┌─25 ──┐ ──TSMSGSPA=─┴─nnnn─┴─────────────────────────── To enable this option. Customization Job Streams 4-41 .STAGE2 Installation Job Stream TSDSNSPA Specifies the maximum size for the ADR (Automatic Dataset Recognition) table. either shut down CA-Jobtrac with the BACK parameter or IPL. Table size can only be increased after an IPL or a BACK of CA-Jobtrac.

See the CA-Jobtrac Extended Scheduling Services Guide for information on the CCPF table. NO is the default if the WLMRSRC keyword is not found. This parameter is specified in the JOBTRA00 startup member.STAGE2 Installation Job Stream TSPGFSPA Specifies the maximum size for the CCPF (Condition Code Program Filters) table. either shut down CA-Jobtrac with the BACK parameter or IPL. and it results in the status of the resource not being changed. The syntax is: TSPGFSPA ┌─25 ──┐ ──TSPGFSPA=─┴─nnnn─┴─────────────────────────── To enable this option. WLMRSRC This designates the WLM resource you have defined for the CA-Jobtrac started task. 4-42 CA-Jobtrac 3. and this could result in an improper resource status if coded incorrectly. You may code NO for this value. CA-Jobtrac sets the status of this resource during initialization and termination. No validation is performed on the value specified.5 Getting Started . Table size can only be increased after an IPL or a BACK of CA-Jobtrac. recycle the CA-Jobtrac STC. Larger values use more ECSA. The syntax is: WLMRSRC ┌─NO───────────────┐ ──WLMRSRC=─┴─cccccccccccccccc─┴──────────────── To enable this option. A value from 100 to 5000 can be specified.

When restarting jobs from Unicenter TNG. Jobs on the checkpoint can be restaged manually on the CA-Jobtrac Scheduled Event Display panel with the R line command and resubmitted for execution. In this case. It is recommended that CA-11 not be used when job reruns are being handled by the remote system. rather than by Unicenter TNG. and Unicenter TNG is notified of the failure when it occurs. the CA-11 interface does not insert the U11RMS step into the job at submission. The change in the status of the job is sent to inform Unicenter TNG. not restarted. since the jobs can only be resubmitted.STAGE2 Installation Job Stream XPLATRERUN LOCAL indicates jobs that fail are restarted from CA-Jobtrac. If not specified. the jobs should have a small number of steps. Customization Job Streams 4-43 . If this option is set. Unicenter TNG is not notified of the job's status until the job successfully completes or the job is purged or deleted on CA-Jobtrac. In this mode. the default is REMOTE. The failing job is automatically restaged in the CA-Jobtrac checkpoint and can be restarted using CA-11. Chapter 4. The syntax is: XPLATRERUN ┌─REMOTE─┐ ──XPLATRERUN=─┴─LOCAL──┴─────────────────────── To enable this option. the job is NOT restaged automatically by CA-Jobtrac. recycle the CA-Jobtrac STC.

5 Getting Started .4-44 CA-Jobtrac 3.

Customization Tasks The following phases complete customization.Covered in this chapter ■ Startup and verification tasks .Chapter 5. Customization Tasks 5-1 . and Recovery Guide.Covered in Chapter 6 Customization Tasks The customization tasks let you set up CA-Jobtrac to meet your installation's needs.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 Initiation IMODs” 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. set up. Chapter 5. The following tasks are covered: “Modify CA-GSS” on page 5-2 “Customizing SYS1. and implementation of CA-Jobtrac: ■ Customization tasks . Maintenance. see the chapter "User Exits" in the CA-Jobtrac Reports.

checkpt. If you do not.DISP=SHR If you are planning to use the CA-Jobtrac cross-platform scheduling feature.checkpt. Be sure that the token part of the ddname (n of JOBTRACn) matches the CA-Jobtrac token ID for the associated checkpoint data set.5 Getting Started .Modify CA-GSS Modify CA-GSS CA-Jobtrac uses CA-GSS facilities to extend its capabilities and to provide you with fully customizable support for job scheduling. CA-Jobtrac information is made available to other CA-GSS client software. it requires additional JCL changes and parameters. Also. Step 1: Modify JCL If the CA-Jobtrac load library (CAILIB) is not in a LINKLIST library. See “CA-Jobtrac Cross-Platform Scheduling” on page 5-73 for details. including that provided by you. include it as a STEPLIB in the CA-GSS PROC. you can preallocate the CA-Jobtrac checkpoint data set to CA-GSS.DISP=SHR //JOBTRAC3 DD DSN=jobtrac. An example follows: //JOBTRACY DD DSN=jobtrac. which CA-Jobtrac) will be affected by the commands. See the Unicenter TNG Framework for OS/390 Getting Started guide for more information. defining multiple checkpoint data sets. The issuer of ADDRESS JOBTRAC commands will specify which checkpoint (and hence. may be specified if desired.sys1. it will be dynamically allocated when needed.sys2. Computer Associates recommends that the additional changes be made after the initial setup of CA-GSS is completed. 5-2 CA-Jobtrac 3. Multiple DD statements. As needed.

Customization Tasks 5-3 . For a complete description of a CA-GSS initialization parameter. replace its leading asterisk (*) with a blank. ■ “Parameters You Need to Modify” provides a summary of each parameter you need to modify. To activate one one of them.Modify CA-GSS Step 2: Modify CA-GSS Parameters As needed. modify the CA-GSS initialization parameters that affect CA-GSS' CA-Jobtrac support. ■ You can copy the JOBTRAC member's contents to your RUNPARM member. The JOBTRAC member of the CA-GSS PPOPTION data set contains examples of these parameters. or you can simply provide an INCLUDE JOBTRAC statement. If you use another name. ■ The names of load modules reflect the names as shipped on the CA-Jobtrac tape. You must ensure that these load modules reside in an APF-authorized library that is accessible to CA-GSS. see the Unicenter TNG Framework for OS/390 documentation. Remember that: ■ Computer Associates-distributed IMODs expect the address name JOBTRAC. ■ The MAXTASK argument limits the number of IMODs that may simultaneously use the ADDRESS environment. ISET Identifies ISETs (IMOD libraries that are included on the CA-Jobtrac tape). Chapter 5. Remember that: ■ Most parameters in the JOBTRAC member are commented out. use the ALTNAME parameter to define JOBTRAC. Parameters You Need to Modify ADDRESS Makes the ADDRESS environments provided on the CA-Jobtrac distribution tape as load modules available to REXX IMODs.

This IMOD.Modify CA-GSS JESNODE In a multi-CPU environment. 5-4 CA-Jobtrac 3. you may want to activate GoalNet so that CA-Jobtrac can exchange information between multiple systems.5 Getting Started . issues a multi-line WTO that explains the TRAC845E message in detail. The IMOD then sets an internal flag so that the multi-line message will not be reissued until the next time CA-GSS is initialized. Step 3: Activate GoalNet If you are operating in a multi-CPU environment. WTO Executes the MSG_TRAC845 IMOD whenever the CA-Jobtrac TRAC845E message is issued. CA-GSS currently requires this information in parametric form because there is no reliable way of obtaining the information directly from JES2 (the techniques required are version and option dependent). which is provided in the CA-GSS sample ISET. identifies the JES2 NJE node name where this copy of CA-GSS is executing. See the Unicenter TNG Framework for OS/390 documentation for details on setting up GoalNet. with or without shared DASD or running CA-Jobtrac in an NJE environment.

JT. To install these samples: 1. Test status prevents the IMODs from loading automatically in CA-GSS.SAMPREXX. c. Copy the IMODS from JT.SAMPREXX to JT. Chapter 5.SAMPISET to the RUNPARM. Submit REXXCOPY.Modify CA-GSS Step 4: REXX IMOD Sample Source (Optional) The CA-Jobtrac installation tape contains a library of REXX SAMPLES that can be used with CA-Jobtrac and CA-GSS.SAMPISET. Compile the IMODs and place them in Test status. Copy the samples from the tape to JT. Customization Tasks 5-5 . or ISET member of the CA-GSS PPOPTION data set. d. Allocate VSAM ISET JT. Add an ISET statement for JT. Allocate PDS JT.SAMPREXX. Modify job REXXCOPY in SAMPJCL to specify the volser and tape unit type for the CA-Jobtrac installation tape. This job will: a. b. 3. JOBTRAC.SAMPISET.SAMPISET LOAD DESC /CA-JOBTRAC SAMPLE IMODs/ SSID isrv See the Unicenter TNG Framework for OS/390 documentation for specific RUNPARM control statement formats. where indicated. 2. A sample ISET statement for the data set would look like the following: ISET JOBTRAC DSN cai. e.

you can suppress the writing of the record to the SMF data set by coding an IEFU83. For linkage editing requirements for the IEFU8x exits.PARMLIB CA-Jobtrac extracts tracking information during event queuing. and then CA-Jobtrac deletes them. see the appropriate IBM manuals. Exit IEAVMXIT is used to provide AMR (Automatic Message Recognition) services. CA-Jobtrac uses these records for data set triggering. 5-6 CA-Jobtrac 3. or IEFU85 exit. IEFUSI. they are not captured in your SMF data sets.PARMLIB Customizing SYS1. The system still creates the records in an SMF buffer. This section describes how to set up these exits. Types 15 and 64 SMF record types 15 and 64 monitor data set activity. IEFUJI.Customizing SYS1.5 Getting Started . It uses SMF type-30 records and builds dynamic interfaces to exits IEFUJV. Type-30 SMF type-30 records are created at job step termination and at job termination. execution. CA-Jobtrac uses these records to monitor job completion. CA-Jobtrac uses these records to monitor purged jobs. Remember that if you suppress the records. and IEFU83. CA-Jobtrac reads them. Setting up IEAVMXIT is described on “Setting Up AMR Support” on page 5-46. This sample can also be linked with aliases of IEFU84 and IEFU85. IEFU84. and termination. Suppressing the Writing of Records If you prefer not to keep the SMF records after CA-Jobtrac uses them. The CA-Jobtrac SAMPJCL library contains a sample IEFU83 exit. IEFACTRT. Type-26 Job purges create SMF type-26 records.

If you added any exits to SYS1.LPALIB. CA-Jobtrac will not track events correctly. All exits. 2.26.IEFU84. IEFUJI.IEFU83. IEFACTRT. IEFACTRT.PARMLIB member SMFPRMxx and set up required exits: 1.EXITS(IEFU29.PARMLIB Caution If you specify a JES subsystem ('SUBSYS(JES')).64). The sample member LINKSMF in the SAMPJCL library shows how to set up a dummy exit. Customization Tasks 5-7 . You can use an IEFBR14 dummy exit for any exit not already in your system.IEFUSI. Procedure Follow the steps below to customize SYS1. Chapter 5. Exit IEFU83 must be in LPALIB for proper control of dynamic DSN triggering tables. CA-Jobtrac operates correctly but with less function when IEFUSI and IEFU83 are not present. you must perform an IPL with CLPA before starting CA-Jobtrac.IEFUSI. 3. IEFUSI. Exit IEFUSI must be in LPALIB for Dynamic Resource Control. including IEFBR14 dummies.IEFU83)) SUBSYS(STC.Customizing SYS1.IEFACTRT)) 4. and IEFU83 are included in LPALIB.IEFACTRT. and IEFU83 are set up in your system. you must include the SMF record types and exits described in the following procedure. IEFUJI. IEFUJI.IEFUJI.3 . IEFUSI. Make sure exits IEFUJV. The minimum configuration is shown below: SYS(TYPE(15. should be linked as RENT and REUS. If you do not.EXITS(IEFUJV. Make sure exits IEFUJV. Make sure that CA-Jobtrac will function with the SMF configuration in SYS1. Exits IEFUJV.IEFUJI.PARMLIB member SMFPRMxx. and IEFACTRT must be in LPALIB to ensure proper CA-Jobtrac operation.

Customizing SYS1.PARMLIB

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, or IEFU85 exit. The CA-Jobtrac SAMPJCL library contains a sample IEFU83 exit, named SAMPU83. This sample can also be linked with aliases of IEFU84 and IEFU85. For linkage editing requirements for the IEFU8x exits, see the appropriate IBM manuals. 6. If you are refreshing SMF exits dynamically, you must perform an F JOBTRAC,BACK command before refreshing SMF. Example SYS1.PARMLIB Member SMFPRMxx The following figure is an example of a SYS1.PARMLIB SMFPRMxx 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 / / / / / / / / / /

/

5-8 CA-Jobtrac 3.5 Getting Started

Setting Up Default Authorization

Setting Up Default Authorization
The 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 the ASMAUTH job. ASMAUTH is then assembled and linked. You can modify the table at any time, even when CA-Jobtrac is running. Authorization Alternative Instead of using the TRACAUTH table, you can use the TRACX26 user exit to interface to your system's security software. For information, 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 to the TRACAUTH table to allow @JOBTRAC (ADDRESS JOBTRAC) to pass security checking. Caution Before modifying the TRACAUTH table for your needs, you should assemble and link it for use with the CA-Jobtrac verification procedure, IVP. If you do not, the IVP will not work properly. The necessary procedures follow.

Chapter 5. Customization Tasks 5-9

Setting Up Default Authorization

TRACAUTH Table Used for Verification Take 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 your installation's requirements. 3. Run the ASMAUTH job to assemble and link the TRACAUTH table. 4. The TRACAUTH table is automatically loaded when CA-Jobtrac is started. If you are modifying the table when CA-Jobtrac is running, 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 custom authorizations.

5-10 CA-Jobtrac 3.5 Getting Started

Setting Up the JES3 Held Job Class

Setting Up the JES3 Held Job Class
Requirement If you have not already assigned a sysout hold class for CA-Jobtrac, your JES3 system programmer must use the JES initialization parameters to do so. You cannot use the sysout capture file until the sysout hold class for CA-Jobtrac is defined. JES3 Requirement For JES3 you need to define the sysout class as follows: SYSOUT,CLASS=J,TYPE=(PRINT),HOLD=EXTWTR Optionally add ,DEST=LOCAL.

Chapter 5. Customization Tasks 5-11

.

all of the data sets in the concatenation will be released from the DDNAME. This value will be applied to all subsequent locations until explicitly resent by another 'SET INITIMOD=. This statement can be used to free a library for maintenance and so forth.VOLSER=volser─┘ Note: If concatenated data sets are edited using the CA-Jobtrac ISPF interface and saved. See the CA-Jobtrac Extended Scheduling Services Guide for more information about IMOD requirements. Chapter 5. SET INITIMOD ──SET INITIMOD=─┬─imodname─┬─────────────────── └─NONE─────┘ Sets the default global initiation IMOD for subsequently defined locations. other data sets may be concatenated to each currently allocated DD (except TRACTnnn) by using the following parameters: CONCAT ──CONCAT──DDNAME=─┬─TRACSnnn─┬────────────────── ├─TRACJnnn─┤ ├─TRACRnnn─┤ └─TRACDnnn─┘ ──. the member is saved to the first data set in the concatenation. DEALLOC ──DEALLOC──DDNAME=─┬─TRACSnnn─┬──────────────── ├─TRACJnnn─┤ ├─TRACRnnn─┤ ├─TRACDnnn─┤ └─TRACTnnn─┘ DDNAME is as in the ALLOC statement. If a single data set is to be removed from a concatenation. The IMOD name can be eight characters long. Note: If the DDNAME has more than one data set allocated in concatenation.Defining Location Information (DYNAMLOC) and Initiation IMODs Optionally. This is standard IBM practice. NONE indicates no global initiation IMOD is desired.' statement.─┬─DATASET─┬─=dataset name──────────────────── └─DSN─────┘ ──┬────────────────┬──────────────────────────── └─.. the DDNAME should be reallocated using the ALLOC keyword instead. Customization Tasks 5-13 .

When INCLUDE statements are parsed.DSN=your.TRACD ALLOC DD=TRACT .DSN=your.TRACT ALLOC DD=TRACR 1. LOC000.DSN=your.TRACJC CONCAT DD=TRACS .DSN=your. DYNAMLOC does not allow concatenation DDs for locations.TRACS ALLOC DD=TRACD .DSN=your.DSN=your.DSN=your.DSN=your.5 Getting Started . and LOC001 in the SAMPJCL library.DSN=your.NAME=LOC 1 You can find samples of DYNAMLOC. INCLUDE can be nested.TRACSC 1 Member named LOC001 contains the following statements: SET INITIMOD=imodname|NONE ALLOC DD=TRACJ 1. Example Member 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. 5-14 CA-Jobtrac 3.TRACJ ALLOC DD=TRACS 1.DSN=your.TRACD ALLOC DD=TRACT 1.TRACT ALLOC DD=TRACR .DSN=your.NAME=LOC ALLOC DD=TRACS .TRACR CONCAT DD=TRACJ . the member referenced is opened and the statements are read before any further statements of the original member.TRACJ .TRACR 1 1 1 1 1.Defining Location Information (DYNAMLOC) and Initiation IMODs INCLUDE ──INCLUDE──membername────────────────────────── The location definitions can be split between multiple members and referenced by INCLUDE statements.TRACS ALLOC DD=TRACD 1.

DATASET=your.VOLSER=VOLSER ALLOC DD=TRACT . ALLOC DD=TRACS . VOLSER=VOLSER ALLOC DD=TRACT 6.TRACJ .TRACT 6.TRACT .Defining Location Information (DYNAMLOC) and Initiation IMODs Using INCLUDE statements does not allow for continued lines. VOLSER=VOLSER ALLOC DD=TRACJ 6. VOLSER=VOLSER ALLOC DD=TRACJ .SCLLIB.DATASET=your. You can use continuations if all the statements are placed in the DYNAMLOC member itself as follows. VOLSER=VOLSER ALLOC DD=TRACS 6. The member name in PPOPTION must be DYNAMLOC.DATASET=your. VOLSER=VOLSER Chapter 5.DATASET=your.DATASET=your. Customization Tasks 5-15 .DATASET=your. Most environments do not require them.DOCLIB. VOLSER=VOLSER ALLOC DD=TRACD .DATASET=your. NAME='LOCATION NAME'.TRACJ 6.TRACS 6.

This section describes how to update these.DISP=SHR DSN=your.DATA.DISP=SHR DSN=your. .ISPPLIB. If you are using . Either concatenate our library to your SYSPROC list. To do this. Add the required DD statements shown in the TSO procedures identified in the following samples: Required DD Statements for TSO Users If you are using the DYNAMLOC member. you need to ensure all the CA-Jobtrac and CA-GSS libraries and data sets are available.CAIISPM.JOBHISTx.DISP=SHR DSN=your. 1.DISP=SHR DSN=your.5 Getting Started .DISP=SHR 5-16 CA-Jobtrac 3. Updating Your TSO Procedures Follow the steps below to update your TSO procedures to provide full-function ISPF support.CAIISPP.Updating Your TSO Procedures or CLIST Updating Your TSO Procedures or CLIST All members in the CA-Jobtrac CAICLIB library need to be in your CLIST library. determine whether allocations for ddnames ISPMLIB and ISPPLIB are in a TSO logon procedure or in a CLIST.JOBHISTx. You must update one or the other.DISP=SHR DSN=your. .DISP=SHR DSN=your. Also.DISP=SHR DSN=your.DISP=SHR DSN=your.DATELIB. //JOBTRACx //JOBHISTx //SEQHISTx //CAPTURE //DATEFILE //ISPPLIB // // //ISPMLIB // // DD DD DD DD DD DD DD DD DD DD DD DSN=your.GSSCAIISPM. Identify which TSO logon procedures need CA-Jobtrac access.DISP=SHR DSN=your.ISPMLIB.CAPTURE. or copy the members into one of the libraries in your SYSPROC list. A TSO logon procedure A logon CLIST See the following topic “Sample CLIST Using LIBDEFs” on page 5-18 The STAGE2 job stream added a sample CLIST named TCLIST3 to your SAMPJCL library. the DDs from the DYNAMLOC member are not required in the CLIST.JOBTRACx.GSSCAIISPP.DISP=SHR DSN=your. 2.

All libraries. The library that is used is controlled by location assignments in the @AUTH macro. you can choose a PAN.Updating Your TSO Procedures or CLIST Optional DD Statements for TSO Users If you are not using DYNAMLOC to allocate the location data sets. LIBR. The library that is used is controlled by location assignments in the @AUTH macro and locations assigned to each scheduled event. ■ Up to 255 TRACDnnn DD statements to define DOC libraries for separate locations.DISP=SHR DSN=your. ■ Up to 255 TRACSnnn DD statements to define SCL libraries for separate locations. The library that is used is controlled by location assignments in the @AUTH macro and locations assigned to each scheduled event.DISP=SHR DSN=your.TRACSxxx.TRACJxxx. add your location data sets also.DISP=SHR 3. Substitute a number from 000 to 254 for nnn. The temporary-use JCL and SCL libraries must be a PDS. Substitute a number from 000 to 254 for nnn. add the DD statements shown below: ■ Up to 255 TRACJnnn DD statements to define JCL libraries for separate locations.TRACRxxx.TRACTxxx. ■ Up to 255 TRACTnnn DD statements to define temporary-use JCL libraries for separate locations. Chapter 5. Substitute a number from 000 to 254 for nnn.DISP=SHR DSN=your. or standard PDS access method. Optionally. //TRACDnnn //TRACJnnn //TRACRnnn //TRACSnnn //TRACTnnn DD DD DD DD DD DSN=your. For the JCL libraries. Customization Tasks 5-17 .TRACDxxx. on the same ddname must use the same access method.DISP=SHR DSN=your. The library that is used is controlled by location assignments in the @AUTH macro. Substitute a number from 000 to 254 for nnn. however.

To access CA-Jobtrac from an ISPF menu using TCLIST3. You can use member SAMPPRIM in your SAMPJCL library as an example of the necessary additions. use member SAMPPRIM in your SAMPJCL library as an example and make the following change: J.Updating Your TSO Procedures or CLIST Updating Your CLIST Allocations If your DD statements are in an existing logon CLIST..5 Getting Started . you must update your ISR@PRIM or equivalent main ISPF menu. you must update your ISR@PRIM or equivalent main ISPF menu. Sample CLIST Using LIBDEFs See member LIBDEF in SAMPJCL for a sample CLIST.. Add the CA-Jobtrac panel library data set (CAIISPM) to the ISPPLIB DD statement.'PGM(GJTRVSPF) .'CMD(%TCLIST3) .' J. <=== From this <=== To this 5-18 CA-Jobtrac 3. Add the CA-Jobtrac message library data set (CAIISPM) to the ISPMLIB DD statement.' CA-11 Interface CLIST See “Installation Requirements” on page 5-55 for more information. 2. 3. update your CLIST by following the steps below: 1. To do this.. Adding CA-Jobtrac to Your ISPF Main Menu To add CA-Jobtrac to your ISPF main menu..

but they cannot be set on the panels. or press the End PF key to exit without saving your changes. For information about starting CA-Jobtrac. you can choose a specific options panel if you wish to change a selected option. Requirement To set some default options. For more information about the JOBTRAnn member. see Chapter 4. some of the options set using JOBTRAnn are displayed on the global options panels. Chapter 5. Customization Tasks 5-19 . Start CA-Jobtrac. Some options are set using the global options panels only. and some options are set using either one. The Sysout Capture Options panel is displayed. Issue the SYS OPTS command from any CA-Jobtrac display to display the Global Options Menu. Procedure Follow the steps below to change global options using the global options panels: 1. some by the JOBTRAnn member only. Additionally. For information about starting CA-Jobtrac. which is the first in the series of global options panels.Setting Global Options Setting Global Options CA-Jobtrac global options describe global values and the environment in which CA-Jobtrac operates. Press Enter to save your changes. CA-Jobtrac global options are set using the CA-Jobtrac global options panels and the JOBTRAnn member. 4. The CA-Jobtrac Global Options panel is displayed. See “Options on the CA-Jobtrac Global Options Panel” on page 5-21 for a description of the options. see Chapter 6. 3. see Chapter 6. Change entries on the CA-Jobtrac Global Options panel so that the options are set as required for your installation. CA-Jobtrac must be started. All of the Above. Instead of option A. 2. Select option A.

5 Getting Started . CA-Jobtrac COMMAND ===> 1 2 3 A CA-Jobtrac CAPTURE LIBRARY ALL - Global Options Menu SCROLL ===> PAGE yy/mm/dd hh:mm CA-Jobtrac Global Options Sysout Capture Options Library Definitions All of the above 5-20 CA-Jobtrac 3. or press the End PF key to exit without saving your changes. See “Options on the Sysout Capture Options Panel” on page 5-31 for a description of the options. 6.JICAUPD ] Optionally.Setting Global Options 5. 7. replace nn with a two-digit numeral specifying a JOBTRAnn member where nn matches the nn in JOBTRAnn. See “Options on the Library Definitions Panel” on page 5-35 for a description of the options. Sample Global Options Menu The following panel shows a sample Global Options Menu. The default is member JOBTRA00. Press Enter to save your changes. Change entries on the Library Definitions panel so that the options are set as required for your installation. Update CA-Jobtrac internal components with the new global options by issuing one of the following operator commands (see the CA-Jobtrac Operator Guide for more information about CA-Jobtrac operator commands): F taskname. The Library Definitions panel is displayed. Change entries on the Sysout Capture Options panel so that the options are set as required for your installation. Press the END PF key to return to the panel from which you accessed the global options panels. or press the End PF key to exit without saving your changes.OPTS[=nn| F taskname. Press Enter to save your changes.

Chapter 5. ■ Specify N to direct CA-Jobtrac to issue message TRAC010I with no prompt. Date Format Specifies the date format to be used on some of the CA-Jobtrac displays and in SCL (Schedule Control Language). Customization Tasks 5-21 . ■ Specify I to accept dates in the International format of dd/mm. CA-Jobtrac COMMAND ===> Date Format A)mer/I)ntl IPL Name Prompt (Y/N) Auto-Schd Allowed (Y/N) Restart Support (R/N) Nodelete Error Msg (Y/N) Step Sysout Footers (Y/N) Archive Print Class SPF Sysout Print Class Capture Sysout (Y/N) JES Command Character Holiday Action Time (HHMM) REXX Retry Interval (HHMM) ISERVE Subsystem Name NJE Node (Y/N) NJE Node Tokens Global Termination IMOD => => => => => => => => => => => => => => => => CA-Jobtrac Global Options A Y Y R Y Y A T Y $ 8 1 ISRV Y AT CLEANUP SCROLL ===> PAGE yy/mm/dd hh:mm Hold ABENDing Output (Y/N) => Y Catalog Error Check (2RUD) => YYYY Multisys Sync Dormancy SYSID Priority List CPU 1 CPU 2 => CPU 3 Prompt on Max Lines (Y/N) Auto-Queue Event Classes CA-Librarian Program Name REXX Maximum Time (HHMM) REXX Retry Maximum Count ISERVE STC Procedure Name Cross Node Query Limit => => => => => => => => => => 999 N AFOLIBR 15 999 GSSA Press ENTER to update options or END to exit without making changes.Setting Global Options Options on the CA-Jobtrac Global Options Panel The panel below shows a sample CA-Jobtrac Global Options panel. ■ Specify Y to direct CA-Jobtrac to issue the TRAC400A and TRAC401A WTORs. IPL Name Prompt Indicates whether the operator is to be prompted at IPL time. Note: See the CA-Jobtrac User Profile panel in the CA-Jobtrac Operator Guide for the date format field for each TSO session. See the CA-Jobtrac Message Guide for descriptions of messages. Field descriptions follow. ■ Specify A to accept dates in the American format of mm/dd.

■ Specify Y to direct CA-Jobtrac to dynamically add any event that is submitted (by any means) with a special AUTO-SCHD character to the CA-Jobtrac current schedule if the event is not already scheduled.JOB jobname STEP:stepname ABENDED. See the CA-Jobtrac Operator Guide for complete information about the AUTO-SCHD feature. DID NOT EXECUTE.Setting Global Options AUTO-SCHD Allowed Specifies whether the AUTO-SCHD feature is supported. The following table describes the available values: Value R Description Direct the restart system (CA-11) to perform step restarts. the following FLUSHED message is issued: TRACWARN . See the CA-11 documentation for more information. Restart Support Specifies the restart/rerun system to be used. condition code exception. Specify N to suppress these messages. ■ Specify N to prevent addition of AUTO-SCHD events to the CA-Jobtrac current schedule. or NOT CATALOGED 2 error: TRACWARN . N Nodelete Error Message Specify Y to direct CA-Jobtrac to send the following nondeletable message to the operator console when a scheduled CA-Jobtrac event ends with an abend. JCL error. CODE=abcode (or COND CODE=ccode or CATALOG ERROR NOTED) If a reader JCL error occurs or an operator purges an event.5 Getting Started .JOB jobname FLUSHED. 5-22 CA-Jobtrac 3. See “AUTOC” on page 4-24 and “AUTOQ” on page 4-25 for more information. No restart automation is in use.

Chapter 5. This is printed for every step of every job. Customization Tasks 5-23 .32. 1.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 .2 . SPF Sysout Print Class When viewing sysouts in CA-Jobtrac/ISPF. .34. Microfiche users should be aware that CA-Jobtrac sorts sysouts by job name and places a full frame separator page between sysouts on the archive tape for offline microfiche and between sysouts in the print queue for online microfiche.5 JOBNAME STEP STEPNAME PGM-NAME START STOP ELAPSED TCB-CPU SRB-CPU SWAPS V/R STORAGE USED TESTJOB1 1 SMP13 HMASMP 13.33 13.5 Archive Print Class Specifies a print class if you archive to print. Specify N to suppress the information.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.Setting Global Options Step Sysout Footers Specify Y to direct CA-Jobtrac to print the detailed step execution information shown in the figure below to help in problem resolution and job step tuning.31 1. The sysout class you specify in this field is the output class of the TSO copy. 4 . CA-JOBTRAC V3. you can print a copy of any listing.

CA-Jobtrac attempts to spool ANY SYSOUT of a CA-Jobtrac-submitted event if Y is selected in the global options.) The capture classes are defined on the Sysout Capture Options panel. CA-Jobtrac issues these warning messages: TRAC 98W WAITING FOR SYSOUT. it does not affect a schedule being loaded to the current schedule. eventname BYPASSED. This option is set in member JOBTRAnn (see Chapter 4). ■ Specify N to direct CA-Jobtrac to bypass sysout capture. (You should specify N if you wish SAR to handle the sysout capture. If not defined in the Sysout Capture Options.Setting Global Options Capture Sysout ■ Specify Y to direct CA-Jobtrac to capture sysouts for online viewing. Holiday Action Time Sets a time range for holiday days. It is used for all schedule captures. Even if you set this field to N. 5-24 CA-Jobtrac 3.5 Getting Started . This setting affects events already on the current schedule. You cannot change this option on the CA-Jobtrac Global Options panel. JOB: eventname NONE FOUND IN ANY CLASS YET TRAC 99W SYSOUT NOT FOUND. All output classes should be specified in the Sysout Capture Options to be spooled properly. JES Command Character This field defines the prefix character you will use to indicate that a console command is to be processed by JES. you must specify a primary capture class. or an event with a date of +1 and a time of ASAP specified.

│ ¦ but since the target time is │ ¦ greater than the holiday │ ¦ action time. │ ¦ │ ¦ ┌───────────────────────┐ │ ¦ │ Event scheduled with │──────────────■─────────────■ │ +1 date. ASAP time. Customization Tasks 5-25 . see the holiday information in the CA-Jobtrac Schedule Creation Guide. This is regardless │ +1 date. a holiday ───────────────────────────────────────────────────────── ┌────────────────────────┐ │ ¦ │ Event scheduled with │────────────■ ¦ │ +1 7 time. an M(H) holiday │ ¦ hold dependency is assigned │ ¦ to the event. or N is │ Event scheduled with │──────────────■ ¦ used. and any │ │ ¦ │ holiday │ │ ¦ └────────────────────────┘ │ ¦ │ ¦ ┌────────────────────────┐ Event is scheduled because │ ¦ │ Schedule with no │ Thursday is a valid workday. └───────────────────────┘ │ ¦ Event is scheduled because │ ¦ Thursday is a valid workday. │ │ ¦ │ and any holiday │ │ ¦ │ action │ │ ¦ └───────────────────────┘ │ ¦ Event is scheduled because │ ¦ Thursday is a valid workday. an M(H) holiday │ ¦ hold dependency is assigned │ ¦ to the event. W. 9 time │ │ ¦ of the setting of │ and any holiday │ │ ¦ the holiday action │ action │ │ ¦ time global option. O. │ ■───¦────■──│ holiday action │ and the target time is less │ ¦ │ specified loaded on │ than the holiday action time. │ ¦ unless a specific holiday ┌───────────────────────┐ │ ¦ action of S. │ │ ¦ └────────────────────────┘ │ ¦ Schedule will not load. │ ¦ │ ¦ │ ¦ 8 .Setting Global Options For additional information about holidays. │ ¦ │ Friday at any time. Chapter 5. │ ¦ but since the target time is │ ¦ greater than the holiday │ ¦ action time. The following figure shows an example of how this option affects holiday scheduling: Holiday Action Time global option set to Midnight │ 8 Thursday │ ¦ Friday.

the NJE Node Tokens field becomes significant. all tokens (that is all events from all CA-Jobtracs) are processed by this CA-Jobtrac. do one of the following: ■ Only start up one NJE-capable CA-Jobtrac on any single system image ■ Specify non-overlapping tokens for each CA-Jobtrac running The JES /*ROUTE or /*XEQ statements identify an event as an NJE event. you should specify the token of the submitting CA-Jobtrac itself in the token list. In this field. This is done by listing up to 39 tokens. You can have multiple subsystems defined. If you leave the field blank. NJE Node Specifies whether to activate the CA-Jobtrac NJE support for this instance of CA-Jobtrac on this system image. If you specify Y. 5-26 CA-Jobtrac 3. you specify which of the CA-Jobtrac events are recognized by this CA-Jobtrac.Setting Global Options REXX Retry Interval The amount of time an environmental dependency waits before executing again. This option applies to environmental dependencies. If you leave this field blank. The token identifies and differentiates individual CA-Jobtracs. NJE Node Tokens A CA-Jobtrac token is the x in JOBTRACx DD statement. the facility attempts to start it. If it cannot start it. For information on using this option effectively. This option is used with the REXX Retry Maximum Count option. an error message is issued. see the REXX information in the CA-Jobtrac Extended Scheduling Services Guide. ISERVE Subsystem Name The name of the CA-GSS IMOD Facility (CA-GSS subsystem) to send REXX IMOD and environmental dependency requests to. The specified NJE nodes apply only to the NJE events for the CA-Jobtracs which are specified as being NJE nodes. The CA-Jobtrac REXX facility checks whether the subsystem is running. If you explicitly specify tokens and you submit NJE jobs to the submitting node itself. All other CA-Jobtrac instances recognize only their own tokens.5 Getting Started . If it is not.

condition code check. The execution takes place immediately after CA-Jobtrac recognizes the termination of an event. This prevents accidental printing of output. The use of a global termination IMOD is optional. Catalog Error Check This field defines the CA-Jobtrac response to IBM messages indicating catalog errors in a batch job. or catalog error.Setting Global Options Global Termination IMOD The name of the global termination IMOD. Each of the four characters in the field can be set to Y (yes) or N (no) and correspond to the positional codes 2RUD. Consequently. which are described below: Character 2 R U D Description Not cataloged 2 Not recataloged Not uncataloged Not deleted Chapter 5. Customization Tasks 5-27 . The execution of the IMOD does not prevent CA-Jobtrac from processing other events. The global termination IMOD executes after each event. multiple instances of the global termination IMOD can execute at the same time for different events. For example. Hold ABENDing Output Specify Y to direct CA-Jobtrac to issue a $HJnnnn message immediately at termination for any event that ends in an abend. Specify N to prevent CA-Jobtrac from issuing the $HJnnnn message. but before CA-Jobtrac calls user exit TRACX09 or releases successors. This order of execution permits the IMOD to alter the status or attributes of the event from within the IMOD using @JOBTRAC (ADDRESS JOBTRAC). you can add an output release dependency to prevent the release of successors until some user action is taken.

it assumes a secondary role until the operator issues an ACTSYS=sysid command to restore or reassign the primary system. CA-Jobtrac checks for these messages in captured sysouts. System 2 is the secondary system and assumes control if system 1 loses communication with system 2. If for any reason the primary system (the one designated to submit events) fails. You cannot change this option on the CA-Jobtrac Global Options panel.Setting Global Options If the code is set to Y. and so on) to the next system. CA-Jobtrac will not check for these messages. A CA-Jobtrac started task runs on each system in a shared JES spool environment. 5-28 CA-Jobtrac 3. This option is set in member JOBTRAnn (see Chapter 4). The Multisys Sync Dormancy field indicates the number of seconds the primary system can be inactive before the secondary system prompts the operator for a decision. System 1 is the primary CPU and assumes the duties of event submission and sysout management. CA-Jobtrac imposes an output release dependency (code O) on the event. If primary roles are transferred and the failing system comes back up. This option is set in member JOBTRAnn (see Chapter 4). and Recovery Guide for information about switching primary systems. Maintenance. The operator must then issue the A line command to remove the O dependency and release any successors. If the code is set to N. Multisys Sync Dormancy This option is used only in multi-system shops. SYSID Priority List This field indicates the priority sequence of the SMF IDs for one to three systems in a shared spool environment. the secondary system (the one next in priority) prompts the operator and requests dynamic transfer of primary duties (event submission. If the message is found. system 3 takes control. sysout capture.5 Getting Started . See the CA-Jobtrac Reports. You cannot change this option on the CA-Jobtrac Global Options panel. If both system 1 and system 2 are down.

This option is set in member JOBTRAnn (see Chapter 4). Use zero to denote there is no time limit. CA-Librarian Program Name In shops that use CA-Librarian for JCL editing and submission. For information on using this option effectively. This option is set in member JOBTRAnn (see Chapter 4). the Master Library utility program has a customer-defined program name. REXX Retry Maximum Count The number of times an environmental dependency executes. REXX Maximum Time The maximum amount of elapsed time a REXX IMOD or environmental dependency can run before it is considered to be in a loop. This option is used with the REXX Retry Interval option. See the CA-Jobtrac Operator Guide for information about using auto-queue job classes. You cannot change this option on the CA-Jobtrac Global Options panel. You can limit the line count on each output class during sysout capture (see the Sysout Capture Options panel on “Options on the Sysout Capture Options Panel” on page 5-31). see the REXX information in the CA-Jobtrac Extended Scheduling Services Guide. Auto-Queue Job Classes Specifies up to eight auto-queue job classes for external submission of JCL for jobs scheduled by CA-Jobtrac with dependency code Q. ■ Specify N to suppress the WTOR.Setting Global Options 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. For information on using this option effectively. This field indicates the batch utility program name. If the maximum amount of time is exceeded. Chapter 5. An event submitted in one of these classes will be flushed with a JCL error if the event is not already on the schedule with a Q dependency code. This option applies to environmental dependencies. You cannot change this option on the CA-Jobtrac Global Options panel. the REXX IMOD or environmental dependency is canceled. Customization Tasks 5-29 . see the REXX information in the CA-Jobtrac Extended Scheduling Services Guide. trying to satisfy its condition.

This field specifies a global time limit for the query. A user can also specify a local time limit. no time limit is imposed.Setting Global Options ISERVE STC Procedure Name If the subsystem specified in the ISERVE Subsystem Name field is not running. to query events across multiple NJE nodes. 5-30 CA-Jobtrac 3. up to two digits. the query ends and the information obtained to that point is displayed.5 Getting Started . Cross Node Query Limit When using the Cross Node Query panel. a time limit for the query can be imposed. the global time limit is used. When the time limit expires. this is the name of the procedure to use to bring up the subsystem. If the user's specified time limit is more than the global time limit. Specify the time limit in minutes. If you leave this field blank or specify 0.

Chapter 5. Customization Tasks 5-31 . and capture packages such as Computer Associates CA-View. Instead. CA-Jobtrac holds the job at the point that the capture subtask is told to begin work on it. or it could not capture the job's output. so nonheld sysout could be printed or spooled to some other writer. How the JES Hold Output Command Affects Sysout Capture The JES hold output command is issued as soon as possible. Packages such as CA-SYSVIEW/E will be able to view the output. This can be several seconds after the job ends. Yes Note: See “CAPDMPS” on page 4-25. CA-Jobtrac cannot hold the job at the moment the job fails. When this occurs depends on if you are using the CA-Jobtrac sysout capture feature. Output writers include the TSO OUTPUT command (which will report the job has no held output at some levels). Hold output commands keep output writers from accessing the output. The following table explains when the command is issued: Using the CA-Jobtrac sysout capture feature? No When the hold output command is issued The hold output command is issued as soon as the job failure is detected.Setting Global Options Options on the Sysout Capture Options Panel The Sysout Capture Options panel lets you define up to four sysout capture classes with different processing characteristics. A better approach in this case is to ensure that all the sysouts created by your CA-Jobtrac jobs are held sysouts. It is used for all schedule captures. while the job is still running. The sysout capture processor will detect the failure and will leave the output from failed jobs alone (in the sysout held class). Then specify the CA-Jobtrac sysout capture options to requeue the output to the original class if you desire. First Definition The first definition (class 1) is the primary definition.

Output Capture Class Specify a SYSOUT= class or the job MSGCLASS= for which sysouts are to be captured and retained for online viewing. The number of days or versions. However. P=Print. R=Requeue. N=None) => T Output Capture Class 2 => J Ret days/Vers => 1 Disposition (P=Purge. P=Print. and CA-Jobtrac does not capture nonheld sysout. suppose you specify 2 for a sysout class. R=Requeue. For example. N=None) => P Archive (T=Tape.Setting Global Options The first Output Capture Class field must be specified. Sysout Capture Options Panel The panel below shows a sample Sysout Capture Options panel. Class A is a good class to use since it is not held anywhere. N=None) => N Output Capture Class 3 => K Ret days/Vers => 2 Disposition (P=Purge. CA-Jobtrac COMMAND ===> Sysout Capture Options SCROLL ===> PAGE yy/mm/dd hh:mm Max Lines => Requeue Class => 4 Capture Limit => 3 Max Lines => Requeue Class => 4 Capture Limit => 255 Max Lines => Requeue Class => 4 Capture Limit => 255 Max Lines => Requeue Class => 4 Capture Limit => 255 Output Capture Class 1 => T Ret days/Vers => 1 Disposition (P=Purge. R=Requeue.5 Getting Started . whichever is greater. N=None) => P Press ENTER to update options or END to exit without making changes. B=Both. B=Both. B=Both. N=None) => P Archive (T=Tape. The classes must be defined to JES as HELD classes. Using CA-View If you are using CA-View to capture your sysout. P=Print. Field descriptions follow. N=None) => R Archive (T=Tape. Ret days/Vers Specify the number of days or number of versions of the sysout you want to keep online. N=None) => P Output Capture Class 4 => 3 Ret days/Vers => 1 Disposition (P=Purge. B=Both. see “Using Other Sysout Capture Products” on page 5-69 for details about defining the writer options. an event that runs once a year will be kept for two years (2 versions). P=Print. 5-32 CA-Jobtrac 3. N=None) => P Archive (T=Tape. An event that runs 10 times a day in that class will be kept for two days. will be kept. even if you are not capturing sysout (Capture Sysout field on the CA-Jobtrac Global Options panel set to N). R=Requeue.

the capture is truncated and the sysout is requeued to the requeue class. If you are using another sysout archival product. It should be a print class that is not held. The operator can reply Y to the CA-Jobtrac WTOR TRAC196A message to instruct CA-Jobtrac to continue capture each time the maximum number of lines is exceeded. If the Prompt On Max Lines entry on the CA-Jobtrac Global Options panel is Y. see your product's documentation to see if the class you specify must be a held class. R. Specify 1-32767 lines. Specify 0 for an unlimited line count. or N for normal (non-abending) jobs. CA-Jobtrac places a hold on each requeued event.Setting Global Options Max Lines Specify a maximum line count for any given sysout data set in this class. Chapter 5. Customization Tasks 5-33 . If the output limit is reached. Scheduled events that abend have all their output requeued to this class after it is successfully captured. The following table explains each disposition: Disposition P R Explanation Purges captured sysouts from the JES queue Requeues captured sysouts to the sysout requeue class in held status after successful capture Retains captured sysouts in their held message class after capture N Requeue Class Specify the output class to which you wish all requeue requests sent. You can also use this parameter to reroute output to another sysout archival product. CA-Jobtrac issues a message to the operator requesting a decision on the capture of the excessive sysout. Disposition Specify a sysout disposition of P.

Capturing the first three sysouts is useful with job-level message class output. specify 255 to capture all sysouts in the class. All remaining sysouts are requeued to the requeue class. You should always make a tape backup if CA-Jobtrac is the only sysout archival tool in use. ■ Specify N to request no archival or backup of sysouts when a 0ARCHIVE or 0SYSARCH task is executed. to capture only the MSGCLASS listing and requeue all SYSOUT=* output. Capture Limit Specify the number of sysout data sets that are to be captured for a given event. . If you specify 3. only the first three sysouts found in the output capture class are captured. Both the archive tape and the spooled copy are sorted into job name sequence and contain separator pages and header information suitable for fiche titling. 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=*. ■ Specify P to request that a copy of any sysout not already archived be spooled to the Archive Print Class defined on the CA-Jobtrac Global Options panel when a 0ARCHIVE or 0SYSARCH task is executed. So. CA-Jobtrac utilities provide for recovery of aged sysouts from the archive tapes. you could specify a capture limit of three. For example. ■ Specify B to request that both a tape backup and a print-spooled copy be created for any sysout not already archived when a 0ARCHIVE or 0SYSARCH task is executed.Setting Global Options 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 for information about scheduling dynamic maintenance). This option is designed for online microfiche output.

Sample Library Definitions Panel The panel below shows a sample Library Definitions panel.Dmmdd Unit Defines the archive unit name (UNIT=unitname).TRACMDS :your. the time and date are appended to the data set name of the archive data set during allocation and can take up to 12 additional characters.Thhmm. For volume identification. The unit name is defined in member JOBTRAnn (see Chapter 4).JOBHIST Press ENTER to update options or END to exit without making changes. You cannot change the unit name on the Library Definitions panel.Setting Global Options Options on the Library Definitions Panel The Library Definitions panel lets you define libraries for use by CA-Jobtrac.DATELIB :your. CA-Jobtrac COMMAND ===> Library Definitions SCROLL ===> PAGE yy/mm/dd hh:mm Archive DSNAME Prefix :your. Customization Tasks 5-35 . as shown in the following name: DSN=your. Archive DSNAME Prefix Indicates the 1-to-35-character high-level qualifier for CA-Jobtrac to use when generating the dynamically allocated archive DSN created at each archival. This prefix is defined in member JOBTRAnn (see Chapter 4). Field descriptions follow.prefix. You cannot change the prefix on the Library Definitions panel. Chapter 5.TRACJCLS Unit :CART Disp :CATLG Retpd :3 Blksize:327 Date/Override Library Auto-Commands Library History Dataset Name :your.

You cannot change the retention period on the Library Definitions panel. Retpd Indicates the retention period in days to be used for the archive data set created by a 0ARCHIVE or 0SYSARCH task. This library is required for proper allocation of JMF (JCL Management Facility) at CA-Jobtrac startup time. For more information about JMF. lists all sysouts captured for the defined period. The &INDEX entry. The default disposition is defined in member JOBTRAnn (see Chapter 4). The retention period is defined in member JOBTRAnn (see Chapter 4). The block size is defined in member JOBTRAnn (see Chapter 4).Setting Global Options Disp Indicates the normal data set disposition of the archive data set. If this DSN is not specified when the JOBTRAC task is started. You cannot change the block size on the Library Definitions panel. 5-36 CA-Jobtrac 3. available through the CA-Jobtrac/ISPF dialogs. Date/Override Library Specify the name of the standard PDS (LRECL=88) that is to contain control keys and JCL images for date card insertion and selectable in-stream JCL parameters or SYSIN overrides. in a multiple of 150-byte records (LRECL=150). Blksize Indicates the archive data set block size. and the volume on which they reside. CA-Jobtrac issues a TRAC669E DSN: message. a brief run history. This library is allocated during execution of the STAGE2 job stream. see the CA-Jobtrac Extended Scheduling Services Guide.5 Getting Started . This value is also used to calculate the number of days to maintain an online copy of the sysout archive &INDEX entry. You cannot change the default disposition on the Library Definitions panel.

See the CA-Jobtrac Operator Guide for more information about operator commands. History Dataset Name Indicates the name of the history file (information display only). This subtask is run as part of normal startup processing. Customization Tasks 5-37 . You cannot change this field on the Library Definitions panel. This library is allocated during execution of the STAGE2 job stream. The INIT subtask provides the entry in this field. Chapter 5. Each command set consists of a list of related commands. See the CA-Jobtrac Extended Scheduling Services Guide for more information about command set scheduling.Setting Global Options Auto-Commands Library Indicates the name of the standard PDS (LRECL=80) that contains members called command sets. You can schedule execution of a command set or respond to some event with a command set.

SAMPJCL to your DATELIB library member DATELIB: 1. You must also add these ddnames to your TSO logon procedure or CLIST. 4. see the CA-Jobtrac Extended Scheduling Services Guide. update the global options.SAMPJCL member PRODDATE. Issue the ISPF copy command. Issue the following command from the CA-Jobtrac primary panel to edit member PRODDATE in your DATELIB library: DATES 3. The additional members reside in your date insertion library and are specified on separate ddnames in your JOBTRAC startup procedure. 5-38 CA-Jobtrac 3. To add the members to the JOBTRAC startup procedure. If global options or the JOBTRA00 member have been updated. This is required for running the IVPADI job later on in the IVP.Copy the PRODDATE Member Copy the PRODDATE Member The ADI (Automatic Date Insertion) feature uses the PRODDATE member to automatically insert JCL date records and other repeated records into your events. Exit the edit panel using the END command or the END PF key. particularly the Library Definitions panel. Ensure that the CA-Jobtrac global options panels have been updated. which defines the date file to CA-Jobtrac. proceed to Step 2. 2. use a ddname of DATELxxx. This is useful when you have multiple JCL libraries or when your users have limited access to JCL libraries. If not. and then exit and reenter CA-Jobtrac. and copy the cai. For complete information about using ADI. where xxx is the three-digit numeric location ID. Procedure Follow the steps below to copy member PRODDATE from the cai. Multiple ADI Members You can define additional automatic date insertion (ADI) members to supplement your production DATELIB.5 Getting Started .

Copy the PRODDATE Member Sample The following figure shows sample JCL for additional ADI members: //DATELIB DD DSN=YOUR.DATEFILE(PRODDATE).PROD. Customization Tasks 5-39 .PROD.DISP=SHR //DATEL 4 DD DSN=YOUR.DATEFILE(DATEL 4).DISP=SHR <= FOR LOCATION <= FOR LOCATION 4 Chapter 5.

1.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. .SAMPJCL to your DATELIB library member JMFSYM01. see the CA-Jobtrac Extended Scheduling Services Guide. For more information about using JMF. Procedure Follow the steps below to copy member JMFSYM01 from the cai. This is required to be able to run the IVP later. Ensure that the CA-Jobtrac global options panels have been updated from the previous step.

Copy the RESOURCE Member Copy the RESOURCE Member The RESOURCE feature uses the resource conditions and assigns a one. 3. Issue the following command from the CA-Jobtrac primary panel to edit member RESOURCE in your PPOPTION library: PARMS RESOURCE 4. Exit the edit panel using the END command or the END PF key. Chapter 5. 1.or two-digit ID code to each definition by coding statements in the RESOURCE member in your CA-Jobtrac PPOPTION library. and copy the cai. (See the CA-Jobtrac Extended Scheduling Services Guide for more details. 2. Customization Tasks 5-41 . Issue the ISPF copy command.) Procedure Follow the steps below to copy member RESOURCE from the cai.SAMPJCL member RESOURCE.SAMPJCL to your PPOPTION data set. All statements in this member are samples and are comments.

SAMPJCL to your PPOPTION data set: 1. (See the CA-Jobtrac Extended Scheduling Services Guide for more details.Copy the EXCLPARM Member Copy the EXCLPARM Member The EXCLUDE PARAMETER feature lists the event names or event prefixes that are grouped for mutual exclusion recognition in the EXCLPARM member in your CA-Jobtrac PPOPTION library.5 Getting Started . and copy the cai. Issue the ISPF copy command. 2.SAMPJCL member EXCLPARM. 3. 5-42 CA-Jobtrac 3. Issue the following command from the CA-Jobtrac primary panel to edit member EXCLPARM in your PPOPTION library: PARMS EXCLPARM 4. Exit the edit panel using the END command or the END PF key.) Procedure Follow the steps below to copy member EXCLPARM from the cai. All statements in this member are samples and are comments.

Chapter 5. Before assembling the table. Customization Tasks 5-43 . See “Setting Up a UCT” on page 5-60 for details about creating the necessary entries. Assembler Members If you do not use SMP/E to maintain your table modules. Load modules must be assembled and linked as described here.Maintaining Table Modules Maintaining Table Modules Some of the tables used by CA-Jobtrac exist as load modules. ADR. Other tables exist as online tables. schedule system commands. make the necessary entries in it. and SCS modules are converted to online tables. Converting Existing Modules to Online Tables With the exception of the AMR table named IPLTABLE. and specify additional condition code checking for events. Some of the CA-JCLTrac functions require entries in the table. use the assembly and link JCL provided in SAMPJCL. The online tables are maintained using the online table services described in the CA-Jobtrac Extended Scheduling Services Guide. Use Member ASMAUTH ASMMSGT To Assemble TRACAUTH table Automatic Message Recognition table for use at IPL time CA-Jobtrac user exits CA-JCLTrac User Control Table Table Name TRACAUTH IPLTABLE ASMEXIT ASMUCT N/A GJC3TUCT CA-JCLTrac User Control Table The CA-JCLTrac User Control Table (GJC3TUCT) shipped with CA-Jobtrac does not have any entries in it. The table below names the SAMPJCL member to use for each table module. IPLTABLE remains a load module. create automatic message replies. all existing AMR. The online table services are used to schedule events based on data sets closing.

When an existing module is initialized using the CA-Jobtrac Table Services panels. it is automatically converted from the existing module format to the new table format.Maintaining Table Modules See “Creating IPLTABLE Entries (Optional)” on page 5-47 for information about creating it. The conversion can take place in two ways—upon initialization or by request. uscSeo thloadrt moduledidinothhavengSe“SetistinUp Defaultle . You can also convert modules priby sn initializatior bviewusing tle idule it inothe vicsaryby so convert modules priby so tirle modu isre workusincorrectly.

View the active SCS table. Update or modify the message (AMR) tables. Update or modify the condition code (CCPF) tables. View the active AMR table. Handle all table setup and job submission setup. Update or modify the command (SCS) tables. Customization Tasks 5-45 . Include calling subroutines. View the active ADR table. Update or modify the automatic data set recognition (ADR) tables. Handle all submission tasks within CA-Jobtrac.Maintaining Table Modules Using Your Security Package To use your security package. View the active CCPF table. secure the use and function of the following: Secure this module GJTRTSIF GJTRTSTA GJTRTSMC GJTRTSMD GJTRTSMF GJTRTSMM GJTRTSVC GJTRTSVD GJTRTSVF GJTRTSVM GJTRTSVR GJTRMSTR To control the ability to Access the entire online table service. Activate online tables. Chapter 5.

UEXIT=Y/N or K M. use member LINKMXIT in the CA-Jobtrac SAMPJCL library to link it into SYS1.5 Getting Started .AMRF=Y/N command disables AMR support. Exit IEAVMXIT is used and must be linked with AMODE 31. issuing any K M. should be linked as RENT and REUS. This is done by ensuring IEAVMXIT is present in your SYS1.LINKLIB. For information about reactivating AMR support. | 5-46 CA-Jobtrac 3. and Recovery Guide for information about contacting Computer Associates Technical Support. See the CA-Jobtrac Reports. Maintenance. Disabling AMR Support While CA-Jobtrac is running.LINKLIB. you must set up exit IEAVMXIT. If IEAVMXIT is not present. All exits.Setting Up AMR Support Setting Up AMR Support To use the AMR (Automatic Message Recognition) feature. contact Computer Associates Technical Support. including IEFBR14 dummies.

Creating IPLTABLE Entries (Optional)

Creating IPLTABLE Entries (Optional)
This section describes how to create an IPLTABLE, which is an Automatic Message Recognition table for use at IPL time. Unlike other AMR tables, the IPLTABLE cannot be created using the online table services as described in the CA-Jobtrac Extended Scheduling Services 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 @AMRGEN statements. 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 each other. ■ The statement must begin in column 10 of the record. ■ Any alphanumeric character in column 72 of a record indicates that the following record is a continuation record. ■ Continuation records must begin in column 16. ■ You can include any number of @AMRGEN statements in the job member. ■ The last statement in the job member must be an @AMRGEN END statement.

Chapter 5. Customization Tasks 5-47

Creating IPLTABLE Entries (Optional)

Description of an @AMRGEN Statement The following are descriptions of the elements of an @AMRGEN statement: Element @AMRGEN Description Required keyword. Invokes the @AMRGEN assembler macro to create an entry in the storage-resident AMR table. Specifies a message ID, message text, or portion of the message text that, when issued, triggers the defined event. Replace msgtext with a message ID, message text, or portion of the message text. The msgtext must be enclosed in single quote marks ('). You can insert // (two forward slashes) in the message text to represent any portion of the message. For example, you want to automate a response to the message with ID IEF238D. The text accompanying this message ID can vary, and you want to respond only to the message that includes the text DEVICE NAME. You can specify 'IEF238D//DEVICE NAME' as the message text to trigger some response. Any message that begins with IEF238D and includes DEVICE NAME will trigger the specified event, regardless of the text between the message ID and the key text. You can use this feature to scan a message for key text without having to determine how many characters from 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 of each option. Required keywords. Specifies the end of the list of @AMRGEN statements in the job.

'msgtext[//]msgtextcont'

//

@AMRGEN END

5-48 CA-Jobtrac 3.5 Getting Started

Creating IPLTABLE Entries (Optional)

Summary of @AMRGEN Options The following options are available for use in an @AMRGEN statement: Option MSGOFF= SYSID= CJOB= TJOB= TOD= PROCP= CMD= CHGMSG= CHGOFF= ACT= Value nn sysid createjob triggerjob hhmm{hhmm} processp mm/dd/yy 'syscmd' 'chgtext' nn A R P S N C W X

MSGOFF Specifies the offset (number of characters) from the beginning of the message where the specified msgtext begins. Offset 00 is the beginning of the message; offset 01 is the second character of the message, and so on. Use a two-digit number specifying the offset value. If you do not specify this parameter, the default offset value 00 is assumed. SYSID Specifies the system on which the specified action is to be performed. Specify the ID of the system. If not specified, the event is performed on all systems.

Chapter 5. Customization Tasks 5-49

Creating IPLTABLE Entries (Optional)

TJOB Specifies the name of the job to be acted upon by the triggered event. CJOB Specifies the job that must issue the message or cause the message to be issued. If the specified job does not issue or cause the message to be issued, the defined event is not triggered. Specify the name of the job that must issue or cause the message. If CJOB is not included in the statement, any job, TSO session, or started system task can issue or cause the message. TOD Specifies the time of day range during which the message must be issued. If the message is not issued during the specified time range, the event is not triggered. If no TOD= is specified, the message can appear at any time of day. Use the form hhmm to specify a time of day, where hh is a two-digit number representing the hour (01-23) and mm is a two-digit number representing the minute of the hour (00-59). If you specify TOD=hhmmhhmm, the message must be issued between the time specified by the first hhmm and the time specified by the second hhmm. For example, TOD=01001100 specifies that the message must be issued between 1 AM and 11 AM. You can specify time ranges that cross over midnight (for example, TOD=22000300). If only one hhmm is specified, it is used as the start of the time range and 2359 is assigned as the end of the time range. For example, TOD=2030 is the same as TOD=20302359. PROCP Specifies a process period or date during which the specified message must be issued to trigger an event. For example, PROCP=MONDAY specifies that the message must be issued on a Monday or no event is triggered. Use any valid process period keyword (except UDEF). See the CA-Jobtrac Reference Summary.

5-50 CA-Jobtrac 3.5 Getting Started

For example. Specify the new message text.syscmd' The command specified by syscmd will be issued at the time defined by a System Command Scheduling statement with the parameter 'SCHD#nnn'. PROCP=08/**/01 specifies any day during August. the command or reply is issued as a standard command. 2001. To do so. dd is a two-digit number representing a day of the month (01-31). and yy is a two-digit number representing a year (00-99). See the CA-Jobtrac Extended Scheduling Services Guide for more information about using System Command Scheduling with Automatic Message Recognition. For example.syscmd. you would use PROCP=05/11/01. Specify a command or WTOR reply. You must enclose the command or reply in single quote marks ('). where mm is a two-digit number representing a month (01-12). PROCP=**/15/** specifies the 15th day of any month during any year. You can specify which part of the original message to replace (see “CHGOFF” on page 5-52). Customization Tasks 5-51 . You must enclose the new text in single quote marks ('). You can specify an entry to schedule the command to be issued at the time specified by the System Command Scheduling facility. where nn is the number of the message to which the reply is being made).Creating IPLTABLE Entries (Optional) You can specify a fixed date in the form mm/dd/yy. CMD Specifies the system command or WTOR reply to be issued by CA-Jobtrac in response to the message specified by msgtext. the command or reply is issued as a WTOR reply and is automatically appended with the proper ID (for example. If ACT=W is specified. R nn. 2001. You can replace any part of the date with ** to define a generic date. CHGMSG Specifies the text to be used in place of the original system message text. to specify May 11. If ACT=C is specified (see ACT= in “ACT” on page 5-52). No ACT= parameter is required for this action. Chapter 5. include this parameter as follows: CMD='SCHD#nnn.

offset 01 is the second character of the message. If the trigger job is already on the current schedule. If the trigger job is already on the current schedule. Purges the trigger job from the current schedule. and so on. the manual dependency (dependency code M) is removed from the job. Offset 00 is the beginning of the message. Adds the trigger job to the current schedule with no dependencies. ACT Specifies the action to be triggered when the specified message is issued and any other conditions are satisfied. Makes the message nondeletable and highlights it on the console display. The trigger job is removed from the current schedule. This exit is no longer supported and may not work in future versions. the default offset value 00 is assumed. Specify a two-digit number specifying the offset value. If the trigger job is not on the current schedule. Issues the WTOR reply specified by CMD=. Takes user exit TRACX04.Creating IPLTABLE Entries (Optional) CHGOFF Specifies the offset (number of characters) from the beginning of the original system message where the new message text specified by CHGMSG= is to begin.5 Getting Started . The following values are available: Value A Description Adds the trigger job to the current schedule with a manual dependency (dependency code M). R P S N C W X 5-52 CA-Jobtrac 3. no action is taken. If you do not specify this parameter. The trigger job is submitted immediately. and any successors are released from predecessor dependency on the trigger job. Suppresses the message from appearing on the system console. no action is taken. Issues the command specified by CMD=. Any reply is generated by the exit program.

3. Locate sample member ASMIPLT in your SAMPJCL library. which you can use as a model.REFRESH Your new IPLTABLE is now ready for use at IPL time. Use this job to assemble and link IPLTABLE into your CA-Jobtrac CAILIB library.Creating IPLTABLE Entries (Optional) Procedure To use the IPLTABLE and the VINIT3 procedure together. Customization Tasks 5-53 . you may need to issue the following command: F LLA. 2. 4. Run the job. Chapter 5. Locate sample member IPLTABLE in your SAMPJCL library. After you have successfully linked the IPLTABLE into your CAILIB library. This is the sample IPLTABLE. use the following procedure: 1.

5-54 CA-Jobtrac 3.PARMLIB to enable the SPACE command.Enabling the SPACE Command Enabling the SPACE Command Users must add GJTRUCBS to the AUTHTSF.5 Getting Started . Use the TSO PARMLIB command to update the TSO system values. AUTHCMD. and AUTHPGM table in the IKJTSOxx member of your SYS1.

CA-Jobtrac CA-11 Integration

CA-Jobtrac CA-11 Integration
This topic describes the CA-Jobtrac and CA-11 changes needed to implement a seamless interface between these two products. The features provided by this integration are: ■ Automatic insertion of the CA-11 U11RMS step during the CA-Jobtrac job submission. Insertion of the step can be controlled by job class. Step insertion parameters are retrieved from the CA-11 options table. ■ Integration of the CA-Jobtrac ISPF online with CA-11 to update the 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 ISPF online to display the CA-11 ISPF panels when a CA-Jobtrac Rerun (R) command is issued. The job name of the job selected in CA-Jobtrac is passed to the CA-11 online. CA-Jobtrac recognizes when the selected job is set up through the CA-11 online for restart, and releases the job when you return to the CA-Jobtrac panels. Restart cancel or force complete actions for the selected job are also detected by CA-Jobtrac. Installation Requirements Note: CA-11 Version 2.2 and Genlevel 9909 or higher are required. The CA-Jobtrac PPOPTION initialization member (JOBTRAxx) must be updated to include the RERUN= and INSERTRMS= keywords described in “RERUN” on page 4-34 and “INSERTRMS” on page 4-31. To use the CA-11 ISPF restart panel from the CA-Jobtrac ISPF panels, 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 and ISPPLIB allocations, respectively, in your TSO PROC or ISPF startup CLIST. The TCLIST3 CLIST distributed in the SAMPJCL library is normally used with this configuration and must be in a library defined to the SYSPROC DD of your ISPF session. 2. Use the LIBDEF CLIST in the SAMPJCL library to allocate these libraries dynamically. This CLIST must be in the library defined to the SYSPROC DD of your ISPF session.

Chapter 5. Customization Tasks 5-55

CA-Jobtrac CA-11 Integration

In either case, the JTRCCA11 CLISTs must be copied from SAMPJCL to a library defined to the SYSPROC DD of your ISPF session. If you specified the INDX11= keyword in the STAGE1 job, the CA-11 libraries were added to the LIBDEF and JTRCCA11 CLISTs that were placed in the SAMPJCL data set. Otherwise, customization of these CLISTs is required. If you are planning to use the CA-11 step insertion, verify that the CA-11 options table (U11OPT) has appropriate values specified for the INSRTPC and INSRTPM keywords. The values specified on these keywords are used to build the inserted step JCL. Also, the keyword INSRTOP should be set to NO if step insertion is to be done only by CA-Jobtrac. See the CA-11 Systems Programmer Guide for more information on the CA-11 Options Table. The INCLUDE statement is used in execution JCL to specify the name of a PDS member which contains JCL statements that you want included (inserted) at the position of the INCLUDE statement. The PDS member may contain any combination of control statements, JOBLIBs, DDs, PROCs, EXECs, SYSIN data, non-JCL, and so forth. When the job entry subsystem on the execution node converts/interprets the JCL stream, the INCLUDE statement is removed, and the JCL statements contained in the specified PDS member are inserted in the JCL stream. Products that interact with JCL PRIOR to the expansion of PROCs and/or INCLUDEs do not "see" the contents of the unexpanded members, and therefore cannot process them. This includes products such 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 when these processes occur. For instance, a referback to JCL within a PROC cannot be adequately validated prior to the expansion of the PROC. In addition, insertion of the CA-11 RMS step as the first executable job step may not be accurately done if an INCLUDE statement is placed prior to the first EXEC statement. It depends upon the contents of the PDS member that is included during expansion. If the included JCL statements contain one or more EXEC statements, then the CA-11 RMS control step is not physically the first step of the job.

5-56 CA-Jobtrac 3.5 Getting Started

CA-Jobtrac CA-11 Integration

Be aware that CA-11 does not process JCL statements that are placed before the CA-11 RMS control step. Fortunately, CA-Jobtrac implements the automatic CA-11 RMS step insertion feature as an option. With this option turned on, CA-Jobtrac searches the JCL for the first EXEC or PROC statement and inserts the RMS step prior to that statement. CA-Jobtrac also checks to see if a CA-11 RMS step is already present. If it is, the insertion does not take place. Any INCLUDE statement prior to the first EXEC or PROC statement is ignored, and the RMS step is inserted after the INCLUDE statement. If this would result in the CA-11 RMS control step NOT being inserted as the first EXEC in the job (that is, because the INCLUDEd JCL contains one or more EXEC statements), you should hard-code the RMS step in the appropriate location to ensure that it will be the first EXEC even after INCLUDE statements are expanded. CA-Jobtrac now inserts the CA-11 RMS control step prior to any INCLUDE statement positioned before the first EXEC statement. This was done to ensure that the CA-11 RMS step was the first EXEC statement in the job. However, subsequent client feedback with this approach and the intent of Computer Associates to maintain consistency across mainframe scheduling products allow CA-Jobtrac to perform CA-11 RMS step insertion as it did previously in Version 3.4.

Chapter 5. Customization Tasks 5-57

Setting Up CA-JCLTrac

Setting Up CA-JCLTrac
CA-JCLTrac is the JCL analysis component of CA-Jobtrac. CA-JCLTrac uses the operating system's own JCL C/I routines to perform syntax analysis, create records that you can load into DB2 tables, 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 UCT A UCT (User Control Table) provides control information for the dynamic allocation of the JCL and procedure libraries. It accomplishes 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 are usually sufficient. For details about setting up a UCT, see “Setting Up a UCT” on page 5-60. Setting Up DB2 Tables You can use the CA-JCLTrac feature of CA-Jobtrac to extract JCL information and store it in DB2 tables. The information can then be used to create reports about your JCL. If you plan to use CA-JCLTrac for this purpose, complete this section to set up the DB2 tables. The list below outlines the steps you must take to set up the DB2 database. The following pages explain the steps in detail. 1. Create the DB2 objects (see “Creating the DB2 Objects” on page 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” on page 5-68)

5-58 CA-Jobtrac 3.5 Getting Started

What is JCLAUTO? JCLAUTO is an edit macro that redefines the END and SAVE ISPF/PDF edit commands. execute the following command: JCLAUTO OFF Chapter 5. Invoking JCLAUTO JCLAUTO is invoked in one of the following ways: ■ Through the use of the CA-Jobtrac TRACX29 user exit (see the sample in SAMPJCL) ■ Making it the initial macro for a user's edit session. This is accomplished with the IMACRO edit command (see the IBM manual ISPF/PDF Edit and Edit Macros). and AUTHPGM table in the IKJTSOxx member of your SYS1. it remains in effect for the duration of the edit session. add GJC3MCII to the AUTHTSF. ■ Executing it while in an edit session Disabling Syntax Checking Once JCLAUTO is invoked. Enabling Automatic JCL Checking Automatic JCL checking requires the use of the JCLAUTO macro. see the CA-Jobtrac Extended Scheduling Services Guide.PARMLIB. AUTHCMD. If a JCL error is found. If you want to disable syntax checking. For more information about CA-JCLTrac. Use the TSO PARMLIB command to update the TSO system values. the JCL is not saved. Customization Tasks 5-59 .Setting Up CA-JCLTrac Enabling CA-JCLTrac To enable CA-JCLTrac. and a CA-JCLTrac message is issued. JCLAUTO changes the commands to invoke the CA-JCLTrac JCL Analyzer prior to saving the member you are editing. This macro is installed with CA-Jobtrac as a CLIST in the CA-Jobtrac CAICLIB library.

for DSName. ■ Punctuation that is shown must be used.Setting Up CA-JCLTrac Setting Up a UCT A UCT (User Control Table) provides control information. You do not have to include them.5 Getting Started . ■ Lowercase letters denote optional portions of literals. The following rules apply to the syntax: ■ Italics are used to denote a variable. you only have to use DSN in the statement. ■ [Brackets] indicate an option. Replace the variable with the indicated information. You do not have to include in the statement what is shown in brackets. For example. It accomplishes 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 Required A UCT is required when you: ■ Request dynamic allocation of JCL libraries (DYNAMJ keyword with TYPRUN(JCLSCAN) or TYPRUN(EXTRACT)) ■ Request dynamic allocation of procedure libraries (DYNAMD keyword) and use nonstandard PROCLIB ddnames in your JES started task ■ Use different JES PROCLIB concatenations for different job classes Setting Up a UCT You create entries in a UCT with the @JCLUCT macro and its statements. 5-60 CA-Jobtrac 3. The following are the @JCLUCT statements: ■ CLASS ■ DSNAME ■ DDNAME ■ END Syntax Used The following sections show the syntax of the @JCLUCT statements.

See “CLASS Statement” on page 5-62 through “@JCLUCT Macro Examples” on page 5-64.) If you need to create a UCT. (Usually.Setting Up CA-JCLTrac How to Set Up and Use a UCT By default. See “Setting Up a UCT” on page 5-60. Customization Tasks 5-61 . Take the following steps to create and use a UCT: 1. you will need to use one. Create entries in a UCT using the @JCLUCT statements. The default name is GJC3TUCT. use the UCT keyword. Compile the UCT using the member ASMUCT in your SAMPJCL library. 4. continue with the following steps. a UCT is always used. see the CA-JCLTrac chapter in the CA-Jobtrac Extended Scheduling Services Guide. 2. Chapter 5. Include the UCT keyword in your JCL to: ■ Explicitly specify the use of the GJC3TUCT UCT (this table is used if you do not include the UCT keyword) ■ Specify a UCT named something other than GJC3TUCT For information about the UCT keyword. 3. Decide if you need to create a UCT. If you want to use a UCT with a different name.

It must appear on the first @JCLUCT macro only. The default is GJC3TUCT.ddname Parameter name Explanation Assigns a CSECT name to the UCT. Identifies this line as a @JCLUCT statement. CLASS statements have the following syntax: [name] @JCLUCT CLASS. Use 0-9 or A-Z. Identifies this line as a @JCLUCT statement.locid. The default is GJC3TUCT. Define a job class once only. Required literal. Defines this statement as a CLASS definition.dsname[.SEQ=nnn] Parameter name Explanation Assigns a CSECT name to a UCT.Setting Up CA-JCLTrac CLASS Statement CLASS statements match a job class with its JES PROCLIB concatenation.jobclass. the default ddname is ■ PROC00 for JES2 ■ IATPLBST for JES3 @JCLUCT CLASS jobclass ddname DSNAME Statement DSNAME statements associate CA-Jobtrac location IDs with JCL libraries. DSNAME statements have the following syntax: name @JCLUCT DSName. It must appear on the first @JCLUCT macro only. Specifies the job class. Specify up to 35 class statements. Specify as many DSNAME statements as necessary. For omitted job classes. @JCLUCT 5-62 CA-Jobtrac 3.5 Getting Started . Specifies the ddname of the JES PROCLIB concatenation used by the job class.

DDNAME statements have the following syntax: name @JCLUCT DDName. Specify a valid data set name. For JES3. Specifies the location ID. Specifies the name of the JCL library associated with the specified location ID. The sequence number determines the order in which the libraries appear in the input concatenation. @JCLUCT Chapter 5. Use any number from 0 to 255. It must appear on the first @JCLUCT macro only. DD statements are required only if your JES2 started task contains ddnames other than PROCxx. the default is 1. For JES2. Identifies this line as a @JCLUCT statement. Use as many DDNAME statements as necessary. Defines this statement as a DSNAME definition. The default is GJC3TUCT. dsname SEQ=nnn DDNAME Entries If your JES started task contains nonstandard PROCLIB ddnames. Defines multiple libraries to a location. DDNAME statements are required. DDNAME statements are required if your JES3 started task contains ddnames other than IATPLBxx. A location ID may be defined only once. CA-JCLTrac dynamically allocates all ddnames that start with PROC. Customization Tasks 5-63 .ddname Parameter name Explanation Assigns a CSECT name to a UCT. CA-JCLTrac dynamically allocates all ddnames that start with IATPLB. Replace nnn with any number from 0 to 255.Setting Up CA-JCLTrac Parameter DSName locid Explanation Required literal.

Defines this statement as a DDNAME definition. The default is GJC3TUCT. Specifies the nonstandard procedure library ddname to be allocated. Identifies this line as a @JCLUCT statement. It must be the last statement in the table. The END statement has the following syntax: name @JCLUCT END Parameter name Explanation Assigns a CSECT name to a UCT. Use only one END statement. It must appear on the first @JCLUCT macro only. END Statement The END statement terminates the @JCLUCT macro. Defines this statement as a termination statement. marking the end of a UCT. Required literal.5 Getting Started .Setting Up CA-JCLTrac Parameter DDName ddname Explanation Required literal. Specify a valid ddname. @JCLUCT END @JCLUCT Macro Examples You can find examples of the @JCLUCT macro in the following members in your SAMPJCL library: ■ GJC3TUC2-JES2 example ■ GJC3TUC3-JES3 example 5-64 CA-Jobtrac 3.

?TSVOLID ?TSVCAT ?TSBPOOL ?TSQPRI ?TSQSEC ?IXSGNME Chapter 5. For example. so that they are easy to find. Required Editing In the JCLQDDL member. This code requires editing before running. If this storage group is not being created. this parameter is not relevant. this parameter is not relevant. If this storage group already exists. These symbolics begin with a question mark. If this storage group is not being created. ?TSSGNME. The following table explains the values you must add to the JCLQDDL member: Symbolic ?TSSGNME Explanation The name of the STORAGE GROUP to be used for the CA-JCLTrac tablespace. remove the CREATE STOGROUP DDL statement from the JCLQDDL members. remove the CREATE STOGROUP DDL statement from the JCLQDDL member. Customization Tasks 5-65 . The SECQTY value used by the CA-JCLTrac tablespace. The DASD volume to be used by the CA-JCLTrac tablespace storage group. The volume catalog to be used by the CA-JCLTrac tablespace storage group. The DB2 buffer pool to be used by the CA-JCLTrac tablespace. there are symbolics for values you must provide. The name of the storage group to be used for CA-JCLTrac indexes. The DDL that does this is in the JCLQDDL member of your SAMPJCL library.Setting Up CA-JCLTrac Creating the DB2 Objects This step creates the DB2 objects used to store the CA-JCLTrac data. The PRIQTY value used by the CA-JCLTrac tablespace. If this storage group already exists.

or an equivalent program. The authorization ID that will become the high-level name of the CA-JCLTrac tables and indexes. remove the CREATE DATABASE DDL statements from the JCLQDDL member. ?IXVCAT ?IXBPOOL ?IXQPRI ?IXQSEC ?DBNAME ?CREATOR Optional Editing After you have changed the symbolics. remove the CREATE DATABASE DDL statement from the JCLQDDL member. Procedure to Create the Objects Using the ISPF editor. change each symbolic to a valid DB2 name or parameter value. After you edit and save the JCLQDDL member.5 Getting Started . further editing may be required. If this storage group is not being created. this parameter is not relevant. The volume catalog to be used by the CA-JCLTrac index storage group. If the CA-JCLTrac tables are going to use an existing database. If this storage group is not being created. The DB2 buffer pool to be used by the CA-JCLTrac indexes. run it in SPUFI. DSNTEP2. The name of the CA-JCLTrac database. If you are going to create the database and storage groups.Setting Up CA-JCLTrac Symbolic ?IXVOLID Explanation The DASD volume to be used by the CA-JCLTrac index storage group. you will need the following authority on the target DB2 subsystem: ■ CREATEDBA—create database ■ CREATESG—create storage group 5-66 CA-Jobtrac 3. The PRIQTY value used by the CA-JCLTrac indexes. The SECQTY value used by the CA-JCLTrac indexes. If the specified database already exists. this parameter is not relevant.

?JOBCARD. The JCL used to bind the plans is in the JCLBIND member in your SAMPJCL library. The authorization ID that is the high-level name of the CA-JCLTrac tables and indexes. The following table describes the values you must add to the JCLBIND member: Symbolic ?STEPLIB ?DB2ID ?CREATOR Explanation The name of your DB2 load library. CA-JCLTrac uses this plan to insert and delete data in the DB2 tables. Customization Tasks 5-67 . the ID must have BINDADD authority. ■ GJC3TSPF—The Dialog Manager plan. Each plan's name starts with GJC3X. CA-JCLTrac uses these plans to extract data for the cross-reference reports. Binding the DB2 Plans This step binds the DB2 plans. there are symbolics for values you must provide. Chapter 5. CA-JCLTrac uses the following plans: ■ GJC3TDB2—The Update plan. For the bind to work.Setting Up CA-JCLTrac If you are using an existing database and storage groups. The name of the DB2 system that runs CA-JCLTrac. For example. CA-JCLTrac uses this plan for the online DB2 reports. There are 18 plans. Required Changes In the JCLBIND member. you need the 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 the CA-JCLTrac home subsystem. This should match the ID used in the JCLQDDL job. ■ GJC3X*—The Report plans. These symbolics begin with a question mark so they are easy to find.

use an ID of PUBLIC. replace the symbolics with a valid database name and authorization ID. or an equivalent program. Using the ISPF editor. DSNTEP2. DSNTEP2. Using the ISPF editor. you must grant execute and select authority to the appropriate users. or an equivalent program. The SQL statements used to grant execute and select authority are in the JCLQRPT member in your SAMPJCL library. 5-68 CA-Jobtrac 3. Granting Authority to Create Reports To use the CA-JCLTrac report plans to create reports. replace the symbolics with valid authorization IDs. In the SQL are the symbolics ?AUTHID and ?CREATOR. Select authority is necessary because the report plans use dynamic SQL.5 Getting Started . you must grant execute and load authority to the appropriate users. After you edit and save the JCLQUPD member. After you edit and save the JCLQRPT member. ?CREATOR is the authorization ID that is the high-level name of the CA-JCLTrac tables. After you edit and save the JCLBIND member. In the SQL are the symbolics ?DBNAME and ?AUTHID. If you intend to grant general access to the CA-JCLTrac tables. This section explains what those authorities are and how to grant them. The SQL statements used to grant execute and load authority are in the JCLQUPD member in your SAMPJCL library. submit the job to bind the plans. Granting Authority Various authorities must be granted to use the CA-JCLTrac plans and tables. ?DBNAME is the name of the database for which authority is being granted. change each symbolic. run it in SPUFI. Granting Authority to Update and Load Tables To update and load the CA-JCLTrac tables. run it in SPUFI.Setting Up CA-JCLTrac Procedure to Bind the Plans Using the ISPF editor. ?AUTHID is the ID of the person receiving the authority. ?AUTHID is the ID of the person receiving the authority.

See the CA-View installation manual for more information. CA-Jobtrac saves the name in your CA-Jobtrac user profile. CA-Jobtrac prompts you for the high-level name of a CA-View database. When you respond. This means that the CA-View load libraries must be either in a LNKLSTnn library or in a library named in the STEPLIB DD statement of the user's logon procedure. Accessing CA-View in CA-Jobtrac The first time you use the 0 (zero) line command or the CA-View primary command. Customization Tasks 5-69 . The CA-View panels must be accessible.0 and higher. CA-Jobtrac uses the high-level name that it saved to determine which database to access. you can direct CA-Jobtrac to requeue each listing to the other product as it captures the copy for on-schedule viewing. you must be able to run CA-View from ISPF.Using Other Sysout Capture Products Using Other Sysout Capture Products If you already have a sysout capture product of another kind. Version 6. see the CA-Jobtrac Operator Guide. To use the CA-View interface. Chapter 5. About the CA-View Interface CA-Jobtrac can interface with the Computer Associates CA-View product. The next time you issue a 0 line command or CA-View primary command. See the description in “Requeue Class” on page 5-33 in “Options on the Sysout Capture Options Panel” on page 5-31 for more information about requeueing sysouts. For more information about these commands.

Using Other Sysout Capture Products Enabling the CA-View Interface To enable the CA-View feature. Specify N for the Capture Sysout field on the CA-Jobtrac Global Options panel. This tells CA-Jobtrac to save schedule captures for the specified number of days. 4. 3. Specify a number of days to keep schedule captures in the Ret Days/Vers field on the Sysout Capture Options panel. See “Setting Global Options” on page 5-19 for more information about the CA-Jobtrac Global Options and Sysout Capture Options panels. take the following steps: 1. 5.5 Getting Started . This tells CA-Jobtrac not to hold any sysout. Specify whatever you want for the remaining fields in the first capture class definition (class 1). This tells CA-Jobtrac to bypass sysout capture and to route it to the CA-View output class. 5-70 CA-Jobtrac 3. We recommend 5 cylinders (the minimum). and it must be defined. for example) for the Output Capture Class 1 field on the Sysout Capture Options panel. Specify a class that doesn't get held (A. 2. CA-Jobtrac uses this primary definition for schedule captures. Format a capture file.

UNIT=SYSDA On the JOBHISTx DD specify the jobtrac token as the value for 'x' and specify the name of your history data set. Procedure The CA-Jobtrac API used by CA-Jobtrac WorkStation requires the following changes be made to the server task started by CAIENF.BLKSIZE=2 96 ). Note: If you do not have your CA-Jobtrac CAILIB data set in LINKLST you must concatenate the CAILIB data set with the //STEPLIB DD statement.DSN=your.TEST High-level qualifier (HLQ) for forecast data set. see the "Configure the Mainframe" chapter of the CA-Jobtrac WorkStation Getting Started guide.SPACE=(TRK. 1.JOBHIST. DCB=(LRECL=8 . This section only describes the changes needed for CA-Jobtrac. you should do so before continuing with this step.dataset DD SYSOUT= DD DISP=(. you must make the following changes to the CAIENF server for CA-Jobtrac to be accessible.(15. You must add the following variables to the CACCENV member of your profile data set (ddname PROFILE in the server PROC JCL).DELETE). JTFDSNHL=PUBLIC. For information on setting up CAIENF and the server task.RECFM=FB. when forecasting is requested by the workstation. Chapter 5.Customizing CA-Jobtrac WorkStation Server Customizing CA-Jobtrac WorkStation Server If you are planning to use CA-Jobtrac WorkStation. It is described earlier in this guide. CA-Jobtrac WorkStation requires that CA-Jobtrac uses DYNAMLOC. The server dynamically allocates and catalogs a temporary data set.DELETE. This should be a HLQ which is defined to your DASD management package as temporary. 2. You must add the following DD statements to the server PROC: //JOBHISTx //SYSPRTFC //WORK // DD DISP=SHR. Customization Tasks 5-71 . so that it will be cleaned up in the event that a server failure occurs and the data set is not deleted. If you have not installed the CA-Jobtrac WorkStation.5)).

Token to indicate CA-Jobtrac to connect to (JOBTRACx). The data set will be allocated to a pack defined to the generic unit if not specified. This is optional. rather than through DD statements in the CA-Jobtrac procedure.5 Getting Started . This requires that the CA-Jobtrac location specific data sets be defined to CA-Jobtrac using the DYNAMLOC member in PPOPTION. See “Defining Location Information (DYNAMLOC) and Initiation IMODs” on page 5-12 for further information on DYNAMLOC. JTFUNIT=SYSDA JTFVOL=vvvvvvv JTTOKEN=x Note: The CA-Jobtrac location specific data sets (TRACJxxx. Volser for temporary forecast data set. Computer Associates recommends that a temporary work device be used. and so on) are accessed by the server through dynamic allocation. 5-72 CA-Jobtrac 3.Customizing CA-Jobtrac WorkStation Server JTFCYLS=x Size of temporary forecast data set in cylinders.TRACSxxx. Unit for temporary forecast data set. This should be the size of your current production checkpoint file.

8 0010 Service Pack 2 or higher.optional ■ TCP/IP must exist on one of the OS/390 systems to communicate with the remote platform (such as UNIX). CAICCI can route work throughout your SNA network to reach other OS/390 systems.CA-Jobtrac Cross-Platform Scheduling CA-Jobtrac Cross-Platform Scheduling If you plan to implement the remote scheduling to Unicenter TNG or CA-Jobtrac Agent.0 or higher must be installed. – CA-XPS must be installed. A sample CAICCI configuration file might look like: SYSID(localname) PROTOCOL(TCPIPGW) NODE(TCPIPGW.0 9909 or higher. CAIENF must be active for status to be returned to Unicenter TNG. See the Unicenter TNG Framework for OS/390 Administrator Guide for syntax and additional information. Customization Tasks 5-73 . the following is also required: – CAIENF must be installed.optional CONNECT(remotename) . Chapter 5. ■ CA-XPS 1.retry. ■ Unicenter TNG Framework for OS/390 1.ip-address:port. ■ CAICCI must be configured with a TCPIPGW protocol TCP/IP gateway. ■ If you plan to implement remote scheduling to CA-Jobtrac from Unicenter TNG or CA-Jobtrac Agent. the following are required: ■ CA-GSS Version 2. For more information. CA-XPS DCM(CAL2DCM2) must be installed into the CAIENF database. see the Unicenter TNG Framework for OS/390 Administrator Guide.remotename) .

A location data set (TRACRnnn) can optionally be defined to CA-Jobtrac to contain user ID.DISP=(. Allocate the tracking checkpoint by running the job in the ALCUNICK member of SAMPJCL (required).DSN=your. See the Unicenter TNG Framework for OS/390 Administrator Guide for syntax and information. See “Global Variables for Cross-Platform Scheduling” on page 5-77. //DCB=(LRECL=8 .(15. 3.BLKSIZE=8 . Allocate remote platform security location data set (optional). and password information that is used when submitting events to Unicenter TNG on remote systems.1 )) //UNIT=uuuuu. The data sets can be allocated using the following JCL or what is in SAMPJCL member STAGE2. 4.VOL=vvvvv 5-74 CA-Jobtrac 3.CATLG).RECFM=FB). //name JOB //STEP1 EXEC PGM=IEFBR14 //TRACR DD DSN==your. The members are created and updated through the PASSWORD command that is available from the CA-Jobtrac ISPF facility.15.unijtckp <-specify 5.CA-Jobtrac Cross-Platform Scheduling Procedure The following steps are required to implement cross-platform scheduling: 1. 2. Edit the CA-GSS PROC (YS28GSSA) and add the following DD statement: //CHKPOINT DD DISP=SHR. domain.SPACE=(TRK.TRACR . This DD MUST be added to the CA-GSS PROC on the CHKPOINT ddname in a following step. The members contained in this data set are encrypted to prevent browsing. A remote password data set may be defined for each location. CAICCI must be configured with a TCPIPGW protocol TCP/IP gateway. Add the statements from the PPOPTION member JOBTRAC to the CA-GSS PPOPTION member JOBTRAC.5 Getting Started .

the file can be specified as: //XPSPSWD DD DUMMY This disables password requirement checking. Use the REFRESHLOC operator command to add the data set without restarting CA-Jobtrac.CA-Jobtrac Cross-Platform Scheduling Once allocated. REFRESHLOC is described in the CA-Jobtrac Operator Guide. an optional table is available to specify the password requirements for the sending system. This allows for systems to be identified as "trusted" or "untrusted" systems.XPSPSWD You are asked in the following step to specify a data set for the XPSPSWD DD. The data set is referenced. by ddname XPSPSWD in the CA-GSS PROC. If you decide not to use this table. Customization Tasks 5-75 . See the PASSWORD ISPF online command in the CA-Jobtrac Operator Guide for information on updating this data set. For cross-platform work being routed to CA-Jobtrac from other platforms. DYNAMLOC allocation is described in “Defining Location Information (DYNAMLOC) and Initiation IMODs” on page 5-12. Note: The same password data set may be used by multiple locations. you must add the data set to the DYNAMLOC PPOPTION member. but multiple password data sets cannot be concatenated to a single TRACRnnn ddname. This table can reside in any 80-character LRECL data set and may be a member of a PDS. Chapter 5. This table is described in “Cross-Platform Server ($UNIXPSJT) Password Requirements Table” on page 5-82.DSN=CAI. Shut down and restart CA-GSS to pick up the new CHKPOINT DD. See “REMTCRED” on page 4-34 for information on optional member name processing. Password requirements rules file (optional). //XPSPSWD DD DISP=SHR. 7. Shut down and restart CA-Jobtrac to pick up the new DDs. as is shown below. 8. 6.

This task is described in “Cross-Platform Server ($UNIXPSJT) Password Requirements Table” on page 5-82. Remote execution status tracker. This server handles receiving the status for commands that have been sent to Unicenter TNG for execution by CA-Jobtrac.SERVER DISPLAY ■ To display all active IMODs (including servers): F GSSA. and next starts an IMOD to update CA-Jobtrac with the request.5 Getting Started .SERVER STOP $UNITRKJT ■ To start a server IMOD with the service name $UNITRKJT: F GSSA. You can also control these tasks using CA-GSS operator commands. $UNIRCVJT service $UNI_RECEIVE IMOD Command driver.CA-Jobtrac Cross-Platform Scheduling CA-GSS Server IMODs The following describes server IMODs used by cross-platform scheduling.$UNI2JT globals are set to a Y value.$JT2UNI and &UNI. This server handles both receiving request and return status to Unicenter TNG for requests sent from TNG to CA-Jobtrac. You can execute this IMOD manually using the CA-GSS SCHEDULE operator command or GSSEDIT to start these service IMODs. $UNIXPSJT service and $UNI_REMOTE IMOD cross-platform server.SERVER START $UNITRKJT ■ To run the $UNIJT_INIT IMOD: F GSSA. $UNITRKJT service and $UNI_TRACK IMOD. CA-Jobtrac starts these services during initialization if the &UNI.DISPLAY ACTIVE ■ To stop a server IMOD with the service name $UNITRKJT: F GSSA. This server preprocesses commands. Some of the CA-GSS commands of interest include: ■ To display defined servers: F GSSA.SCHEDULE $UNIJT_INIT 5-76 CA-Jobtrac 3. CA-Jobtrac invokes IMOD $UNIJT_INIT at startup to check the status of the server IMODs and define and start the IMODs as needed. These globals are described later in this chapter.

the IMOD service $UNITRKJT is started whenever CA-Jobtrac is started. See Defining Events to Unicenter TNG in the CA-Jobtrac Extended Scheduling Services Guide for more information. or the $UNIJT_INIT IMOD is executed.MON /JOBTRAC/ Specifies the monitor name to be used to identify CA-Jobtrac when requests are received from Unicenter TNG. Server IMOD Selection Globals GLOBVAL &UNI. In most cases. Any value other than Y prevents the server IMOD from starting. A monitor name can be specified in the File field using the MONITOR keyword following the job name when a job is being scheduled from Unicenter TNG.$UNITRKJT. Status Tracking Server Globals (Service $UNITRKJT) GLOBVAL &UNI. If Y is specified as the value. If Y is specified as the value.CA-Jobtrac Cross-Platform Scheduling Global Variables for Cross-Platform Scheduling This topic describes the CA-GSS globals that are used with the cross-platform scheduling server IMODs. This global is required. Any value other than Y prevents the server IMOD from starting. Chapter 5. the value of JOBTRAC is appropriate.$JT2UNI /Y/ This global controls the starting of the server IMODs that are used for CA-Jobtrac to Unicenter TNG scheduling. the IMOD services $UNIXPSJT and $UNIRCVJT are started whenever CA-Jobtrac is started or the $UNIJT_INIT IMOD is executed. If multiple Computer Associates scheduling products are installed and CA-Jobtrac is not the primary receiver of requests. Customization Tasks 5-77 . GLOBVAL &UNI.$UNI2JT /Y/ This global controls the starting of the server IMODs that are used for Unicenter TNG to CA-Jobtrac scheduling.$UNIXPSJT. this differs from &UNI.MON described below.

If this value is not supplied. We recommend that debug only be turned on at the request of Computer Associates Technical Support since the volume of debug information can be large.EXTTABLE/dataset. GLOBVAL &UNI. This value may range from 01 to 60.CA-Jobtrac Cross-Platform Scheduling GLOBVAL &UNI.DEBUG /DEBUG/ Enables debug for this task. If this global is set to the value DEBUG. a default of 15 seconds is used. setting this global has no effect. If these DDs are not present in the GSS PROC. These services include testing for operator shutdown requests. This global is optional. this task logs information on processing to DDs DEBUGTRK and SNAPTRK.$UNITRKJT. 5-78 CA-Jobtrac 3.$UNITRKJT. physical updates to the checkpoint file that is being updated at all times in memory.$UNITRKJT.SCAN /15/ The number of seconds that is to be used as a time interval between controlled services. This global is required. This value must be specified with the value of $JOBT_REMTTRACK and should not be changed. GLOBVAL &UNI. and querying Unicenter TNG remote locations for job completion statistics.name/ Specifies the name of a sequential data set or the member name of a PDS in which the external events are defined.$UNITRKJT.IMOD /$JOBT_REMTTRACK/ Specifies the IMOD to invoke when status information is received from Unicenter TNG.5 Getting Started . GLOBVAL &UNI.

SCAN /15/ Specifies the number of seconds that is to be used as a time interval between controlled services. A monitor name can be specified in the File field using the MONITOR keyword following the job name when a job is being scheduled from Unicenter TNG. We recommend that debug only be turned on at the request of Computer Associates Technical Support since the volume of debug information can be large. GLOBVAL &UNI. See Defining Events to Unicenter TNG in the CA-Jobtrac Extended Scheduling Services Guide for more information. This value may range from 01 to 60.$UNIRCVJT. This global is required.MON /JOBTRAC/ Specifies the monitor name to be used to identify CA-Jobtrac when requests are received from Unicenter TNG.$UNIRCVJT. In most cases. If this global is set to the value DEBUG. setting this global has no effect. This global is required.MON described below. a default of 15 seconds is used.$UNIXPSJT. If multiple Computer Associates scheduling products are installed and CA-Jobtrac is not the primary receiver of requests. This value must be specified as is. If this value is not supplied. These services include testing for operator shutdown requests. this task logs information on processing to DDs DEBUGRCV and SNAPRCV. Customization Tasks 5-79 .CA-Jobtrac Cross-Platform Scheduling Command Driver Globals (Service $UNIRCVJT) GLOBVAL &UNI. If these DDs are not present in the GSS PROC. GLOBVAL &UNI. this differs from &UNI. Chapter 5.IMOD /$JOBT_REMTCMD/ Specifies the IMOD that is invoked when a request from Unicenter TNG is received.DEBUG /DEBUG/ Enables debug for this task.$UNIRCVJT. the value of JOBTRAC is appropriate. GLOBVAL &UNI.$UNIRCVJT.

The Print trace code controls both print and snap output. A monitor name can be specified in the File field using the MONITOR keyword following the job name when a job is being scheduled from Unicenter TNG.CA-Jobtrac Cross-Platform Scheduling Cross-Platform Server Globals (Service $UNIXPSJT) GLOBVAL &UNI.SCAN /15/ Specifies the number of seconds that is to be used as a time interval between controlled services. GLOBVAL &UNI. These services include testing for operator shutdown requests. This global is required.5 Getting Started . 5-80 CA-Jobtrac 3. the value of JOBTRAC is appropriate. See Defining Events to Unicenter TNG in the CA-Jobtrac Extended Scheduling Services Guide for more information. The print and snap DDs are defined in the GSS PROC as XPSPRINT and XPSSNAP.$UNIXPSJT. physical updates to the checkpoint file that is being updated at all times in memory. If multiple Computer Associates scheduling products are installed and CA-Jobtrac is not the primary receiver of requests. a default of 15 seconds is used. this differs from &UNI.$UNIXPSJT. If this value is not supplied. and querying Unicenter TNG remote locations. This value may range from 01 to 60. The Console trace code controls what WTOs are issued to the OS/390 console.MON described below.$UNIXPSJT.MON /JOBTRAC/ Specifies the monitor name to be used to identify CA-Jobtrac when requests are received from Unicenter TNG. GLOBVAL &UNI. In most cases.$UNIXPSJT.DEBUG /pc/ Sets current Print (p) and Console (c) trace code settings for this task.

Program path messages/WTOs. 1 2 3 4 Chapter 5. They also indicate when communication with remote systems is first established and if such communication is lost. messages relating to CCI communications with other systems are issued. Feedback messages/WTOs.CA-Jobtrac Cross-Platform Scheduling Valid trace code values are: 0 Do not issue any trace WTOs. snap dumps are taken of the storage areas related to XPS control blocks in addition to the communication and feedback related snaps. If entered for the Print trace code. Also. messages relating to XPS CAIENF feedback events are issued. if the snap DD is available. if the XPS snap DD is available. Note: Trace code 4 should only be used at the direction of Computer Associates Technical Support since it produces a significant number of messages. it is interpreted the same as a code of 1. Also. Normal messages/WTOs. Communication messages/WTOs. These messages indicate XPS system startup and shutdown. In addition to the messages issued for trace code 3. they are interpreted the same as trace code 4. If entered. In addition to the messages issued for trace code 1. In addition to the messages issued for trace code 2. snap dumps are taken of the storage areas related to CCI control blocks and records. snap dumps are taken of the storage areas related to CAIENF control blocks and feedback records in addition to the communication area snaps. 5-9 Currently. messages relating to internal XPS processing are issued. Customization Tasks 5-81 . This value is only honored for the Console trace code. Also. if the XPS snap DD is available. trace codes 5 through 9 do not have specific definitions.

If the XPSPSWD DD statement is not present. Changes made to the rules do not take effect until the server is reinitialized. Requests received from these systems which have a user ID but no password will be automatically rejected. Continuation lines are not supported. it attempts to locate and parse the Password Requirement Rules. if you are confident that requests from a given system have already gone through security checks to ensure that the user ID passed with the request should be honored. separated by commas with no embedded blanks. or contains no valid rules. the default processing is to accept all requests without checking for the presence of passwords. ■ Each individual rule must be contained on a single line between columns 1 through 71.CA-Jobtrac Cross-Platform Scheduling Cross-Platform Server ($UNIXPSJT) Password Requirements Table The password requirement rules for the cross-platform server on OS/390 define when a password must accompany an explicit user ID in a cross-platform request. you can specify a rule so that the cross-platform server will accept the user ID without a password. For other systems which are not 'trusted' you can write rules so that any request from them which contains a user ID must also carry a password that can be validated by the cross-platform server. these rules are stored in an in-storage table that is accessed during normal processing. That is. See “CA-GSS Server IMODs” on page 5-76 for information on stopping and starting CA-GSS server IMODs. This data set is a sequential file consisting of fixed 80-byte records (physical sequential or a member of a PDS). ■ The rule definition consists of a series of keywords/values beginning in column 1. Password Requirement Rules are defined in a data set pointed to by the XPSPSWD DD statement in the GSS PROC. If found. The records can be blocked or unblocked. When the cross-platform server goes through initialization processing. Syntax Rules ■ Lines beginning with a blank or an asterisk (*) are considered comment lines. 5-82 CA-Jobtrac 3. Using this table you can discriminate between trusted and non-trusted systems when receiving requests.5 Getting Started .

If not specified. It must be specified as a specific name or an asterisk (*). NO (or N) Indicates that passwords are optional for such requests. the default is MONITOR=*. If not specified. the default is NODE=*. It must be specified as a specific name or an asterisk (*). indicating all user IDs. Chapter 5. Customization Tasks 5-83 .to eight-character user ID that may be passed with a Cross-Platform request. If not specified. It must be specified as a specific name or an asterisk (*). which indicates all monitor names. YES (or Y) Indicates that such requests must have a password. the default is PSWD=YES. which indicates all nodes. indicating all monitor names.CA-Jobtrac Cross-Platform Scheduling Keywords NODE=caicci-node-name This keyword identifies the one. If not specified. MONITOR=monitor-name This keyword identifies the seven-character scheduling system monitor name that a Cross-Platform request can be received from.to eight-character CAICCI Node name that a Cross-Platform request can be received from. PSWD=YES|NO This keyword indicates whether a Cross-Platform request which matches the NODE/MONITOR/ID parameters of the rule must have a password to accompany the user ID in the request. indicating all nodes. ID=user-id This keyword identifies the one. the NODE and MONITOR combination will uniquely identify a specific scheduling system. In cases where a given node may have multiple scheduling systems (such as production and test copies of CA-Jobtrac). which indicates all user IDs. the default is ID=*.

the request is allowed to proceed without a password. If no match is found in the table. 1. it checks to determine if the request contains an explicit user ID. 3. If the request contains a user ID but no password. A match with a rule that specifies a specific NODE. 5-84 CA-Jobtrac 3. The XPS Router attempts to find the 'best match' between the current request and the Password Requirement Rule Table based upon the NODE. a password requirement check is not made. If multiple rules equally match a request. and/or user ID takes precedence over a generic rule. MONITOR. If the request does not contain a user ID. If the request contains both a user ID and a password. 2. a password requirement check is made. a password requirement check is not made. then the rule(s) which require a password takes precedence over those that do not. MONITOR.5 Getting Started . and user ID.CA-Jobtrac Cross-Platform Scheduling Processing When the server receives a cross-platform request.

In this case the matches have equal weight (NODE or MONITOR specific.ID= . A password is required.CA-Jobtrac Cross-Platform Scheduling Examples NODE=A 4IENF. the rule which requires a password takes precedence over one which does not. must have a password if it contains an explicit user ID. In the case of a tie. regardless of what CAICCI node or scheduling system sent the request.ID= .PSWD=NO If a request is received from CAICCI node A04IENF with a user ID of TESTUSER.ID= . NODE=A 4IENF. user ID generic).PSWD=YES NODE= . The default for MONITOR= is * if it is not specified.PSWD=NO If a request is received from CAICCI node A04IENF. Chapter 5. A password is not required.ID=TESTUSER.PSWD=NO The above rule indicates that a request from CAICCI node A04IENF with a user ID of TESTUSER is not required to have a password associated with it.MONITOR=JOBTRAC. it partially matches on both of the above rules.PSWD=YES NODE= . NODE= . scheduling system JOBTRAC.ID=MASTER. scheduling system JOBTRAC with any user ID it partially matches on both of the above rules. Customization Tasks 5-85 .MONITOR= .ID=TESTUSER. NODE=A 4IENF.PSWD=YES The above rule indicates that any request which contains a user ID of MASTER must have a password.PSWD=YES The above rule indicates that any request from CAICCI node A04IENF. The second rule takes precedence since a specific ID match takes precedence over a specific NODE match.ID= .MONITOR=JOBTRAC. NODE=A 4IENF.

5-86 CA-Jobtrac 3.5 Getting Started .

the CA-Jobtrac installation process (STAGE1 and STAGE2). Startup and Verification CA-Jobtrac includes a verification procedure you can use to verify that CA-Jobtrac is functioning properly. This chapter discusses these issues. you must do so before using the supplied IVP. and you must follow the steps in this chapter for the IVP to work correctly. If you have not completed these steps. Chapter 6. Startup and Verification 6-1 . This verification procedure is referred to as IVP. you must have completed the install and customization steps up to this point and start CA-Jobtrac. and the customization tasks described in Chapter 5. Use of the supplied IVP assumes you have completed the SMP/E installation process. Before Running IVP Before you can run IVP.Chapter 6.

see Chapter 5.PARM=IPL. If you do not want to wait the 15 minutes.PARM=IPL] This command starts the specified CA-Jobtrac and initializes the CA-Jobtrac internals. see the CA-Jobtrac Extended Scheduling Services Guide.Initialization and Startup Initialization and Startup This topic covers multiple ways of initializing CA-Jobtrac internals. starting the CA-Jobtrac task. accessing CA-Jobtrac. even before JES is started. you can process received messages and issue commands and schedule or trigger batch jobs. The optional PARM=IPL parameter allows the IPL message prompt to the console operator as described in the global options information in Chapter 5. add this command to SYS1. For information about the other AMR tables.SUB=MSTR You must use this method of initializing CA-Jobtrac ONLY during an IPL when using an IPLTABLE. and ending the CA-Jobtrac task. CA-Jobtrac loads the IPLTABLE during IPL and switches to the regular AMR table after 15 minutes. For information about the IPLTABLE. Automatically Processing IPL Messages The VINIT3 procedure for CA-Jobtrac initialization can be run under the Master Subsystem to allow some table processing to begin early in the IPL process. Initializing CA-Jobtrac Internals S VINIT3. 6-2 CA-Jobtrac 3. Using CA-Jobtrac at Initialization Time If you do not wish to use the IPLTABLE processing feature.5 Getting Started .PARMLIB member IEACMDxx (for SP2 and SP3 systems): S JOBTRAC3[. With the use of a special AMR table called IPLTABLE. By default.taskname. you can activate a table using the online table services (see the CA-Jobtrac Extended Scheduling Services Guide for more information).

no jobs/events will submit. enter the following command on each system in the shared spool complex: S JOBTRAC3[.taskname] Normally. CA-Jobtrac will not start. To start the CA-Jobtrac task. Accessing CA-Jobtrac From ISPF To access CA-Jobtrac from ISPF. any data sets that must be accessed at this time (such as the CA-Jobtrac JOBHISTx VSAM cluster) must be cataloged in the master catalog. CA-Jobtrac startup processing by default begins submitting jobs/events. you can do so manually. tasks running at this point in the IPL know only about data sets that are cataloged in the master catalog. very few resources are available. For example. If it is not present. See the CA-Jobtrac Operator Guide for other VINIT3 commands. Therefore. Minimally. the CA-GSS CAILIB MUST be present. but since the checkpoint file was just formatted.Initialization and Startup Restrictions on Using VINIT3 Since VINIT3 running under the Master Subsystem (SUB=MSTR) is started so early in the IPL process. Procedure If you do not start CA-Jobtrac during your IPL. Chapter 6. Starting the CA-Jobtrac Task Caution CA-Jobtrac requires CA-GSS to be present to use its full functionality. Startup and Verification 6-3 . select the option set up by your systems programmer.

enter the following command: P taskname 6-4 CA-Jobtrac 3.Initialization and Startup With a CLIST To access CA-Jobtrac using a CLIST.CA-Jobtrac. which executes the initialization CLIST created by the STAGE2 job stream: EX your.SAMPJCL(TCLIST3) or EX your. Ending the CA-Jobtrac Task To end the CA-Jobtrac task.5 Getting Started .CA-Jobtrac. enter the following command.SAMPJCL(LIBDEF) The function of TCLIST3 is to allow entry into CA-Jobtrac until your ISPF menu has been updated to include CA-Jobtrac as a selectable menu item (see the information about adding CA-Jobtrac to your ISPF Main Menu on Chapter 5).

List History TESTI1 TESTI2 TESTI3 JREPI1 JREPI2 Yes Yes Yes Yes Yes Chapter 6. JMF. All IVP members can be found in your SAMPJCL library. and a series of events to be scheduled. Contents of IVP The CA-Jobtrac IVP supplied with the product consists of an internal verification procedure. ADI.Verification Verification This topic covers the contents and use of the installation verification procedure. Startup and Verification 6-5 .List Schedule Sample JREPORT3 . Members Supplied The CA-Jobtrac IVP members supplied and their contents are described in the following tables: SCL Member IVP001 JCL Member Contains CA-Jobtrac Dynamic Schedule SCL Contains Modify JOB Statement Yes Yes Yes No IVPADI IVPAJO IVPJMF JOBT@#$J Sample ADI job Sample AJO job Sample JMF job Internal verification procedure which tests CA-Jobtrac and related IBM exits to see that they are installed and active IEFBR14 IEFBR14 IEFBR14 Sample JREPORT3 . AJO and JREPORT testing. a dynamic schedule.

■ Because the 0ARCHIVE dynamic task will be scheduled as part of the IVP. or it should be included in your TSO logon procedure. TESTI3. IVPADI. TESTI1.Verification Dynamic Task 0ARCHIVE Contains Tests event and sysout archival. This is needed because the IVP001 schedule member schedules events for location ID 001. IVP Assumptions The IVP assumes the following environment: ■ The IVP001 schedule member resides in the location 001 SCL library. IVPAJO. This must be defined as the TRACS001 SCL library in the CA-Jobtrac started task.SAMPJCL library copied over to the DATELIB data set created by the STAGE2 JCL. The ISPF CLIST for using CA-Jobtrac should also allocate this data set. IVPJMF. ■ The IVPAJO member must have the DATELIB member sample in the cai. The STAGE2 installation job stream created a CA-Jobtrac started task with TRACS001 pointing to the library defined for the INSTLIB keyword.SAMPJCL copied over to the PPOPTION data set. ■ The ASMAUTH customization event must also run to generate a default TRACAUTH table with a default location ID of 1. JREPI1 and JREPI2. you might need a tape drive if you have chosen to archive sysouts to tape as specified on the Sysout Capture Options panel (global options). ■ The CA-Jobtrac started task procedure in your procedure library contains a TRACJ001 DD statement naming the same data set as in the last item above. TESTI2. Member IVPJMF must have the JMFSYM01 sample member from the cai. 6-6 CA-Jobtrac 3. dynamic task scheduling Modify JOB statement No All other jobs will need their JOB statements. This DD statement defines the JCL library for location ID 001 and contains the IVP events JOBT@#$J.5 Getting Started . ■ The JREPORT3 procedure as created in STAGE2 customization exists in an executable form in an accessible procedure library.

IVPJMF. JREPI2. JREPJ1. make sure the specified MSGCLASS is one of the sysout capture classes you specified on the Sysout Capture Options panel (global options) and the Capture Sysout option on the CA-Jobtrac Global Options panel is set to Y. Procedure Follow the steps below to use the supplied IVP: 1. modify the CA-Jobtrac started task procedure or use a different TRACAUTH table. Startup and Verification 6-7 . It can be copied from your SAMPJCL installation library if necessary. IVPADI. RUN IVP 1. You should ensure that: ■ IVP001 exists in the SCL library defined as TRACS001 in your JOBTRAC STC task. TESTI3. Modify the JCL supplied for the sample jobs to meet your installation requirements. and JOBT@#$J jobs for JOB statement updates. They can be copied from the SAMPJCL installation library if necessary. TESTI2. JREPI2. IVPAJO. enter the CA-Jobtrac ISPF interface and issue the following command in the COMMAND field on the CA-Jobtrac primary panel. ■ The JCL members TESTI1. it must be five to eight characters ending with @#$J.Verification Using Other Libraries If you decide to use libraries other than those generated during initial installation. It is not recommended. ■ If you change the name of the internals verification procedure job (JOBT@#$J). IVPJMF. TESTI2. To begin execution of the IVP. All CA-Jobtrac commands require dynamic schedule names and task names to begin with 0 (zero). IVPADI. TESTI3. 2. To view sysouts. ■ The proper data set definition exists for the JCL library in both the CA-Jobtrac started task procedure and your TSO session (either allocated in your CA-Jobtrac CLIST or added to your logon procedure) or the DYNAMLOC member. JREPI1.L= 1 Chapter 6. ■ IVP001 schedules all events to a location ID to which you are authorized by whatever TRACAUTH table you are using. and JOBT@#$J exist in the JCL library for the location ID to which you have scheduled them. IVPAJO. Check the TESTII1.

The A command releases the manual dependency and lets CA-Jobtrac submit the event. This command displays all events on the schedule (after initial installation. 3. and press Enter. and sysout capture (IEFBR14). To view the output of the schedule. tracking. TESTI2. Tab to event TESTI1. only the IVP events should be displayed).5 Getting Started . Tests to see the dynamic exits of CA-Jobtrac. When the schedule is loaded. type RALL or D in the COMMAND field and press Enter.Verification This loads the dynamic schedule's SCL and performs syntax checking of the input. The Dep Codes (dependency) field for TESTI1 should have a manual (M) dependency. in the following sequence: TESTI1 TESTI2 TESTI3 JOBT@ IVPADI IVPAJO IVPJMF JREPI1 Releases TESTI2 upon successful completion Releases TESTI3 upon successful completion Releases JOBT@ Releases IVPADI upon successful completion Releases IVPAJO upon successful completion Releases IVPJMF upon successful completion Releases JREPI1 upon successful completion Releases the 0ARCHIVE task upon successful completion 0ARCHIVE Releases JREPI2 upon successful completion JREPI2 Member IVP001 TESTI1. you can tab to the schedule name and enter the O (Output) line command. 4. type the A (release dependency) line command. You can follow the progress of the schedule load by pressing Enter and watching the Current Event Status field on the right side of the panel. and TESTI3 JOBT@#$J Last event Functions Tests dynamic schedule loading and CA-Jobtrac/ISPF online processing. Tests event submission. 6-8 CA-Jobtrac 3. Each event will run after its predecessor completes.

AVPADI. To view a event's sysouts after the * disappears. Press the END PF key or enter the END command to return to the Scheduled Event Display panel. JREPI1. and the 0ARCHIVE events which just completed will be deleted from the current schedule and moved to the history file. an * (asterisk) appears to the right of the date at the end of the event's record. If you selected the tape option during customization. After the 0ARCHIVE task has completed. At any time. Until CA-Jobtrac finishes capturing an event's sysouts. Check the output to see if the comments match with the days submission date. IVPJMF. the TESTI1. CA-Jobtrac signals that each event is complete by indicating COMPLETED in the Current Event Stat field on the panel. 6. the 0ARCHIVE dynamic task might require a tape mount. you can select the detail panel to view an event's schedule detail by using the S (select) line command. Check the output of this job to see that the STEPNAME is the day of the week this job has submitted.Verification Member IVPADI Functions Tests the Automatic Date Insertion abilities of CA-Jobtrac. IVPAJO. tab to the event and enter the O (output) line command. TESTI3. This should be todays. Tests the JCL Modification Functions. Tests the Automatic JCL Override abilities of CA-Jobtrac. Check the k IVPAJO IVPJMF 5. . TESTI2.

IEFACTRT EXIT DETECTED THE IVP JOB GJTRIVP2 .5 Getting Started . in any combination. If you are running multiple CA-Jobtracs.IEFACTRT EXIT DETECTED THE IVP JOB 6-10 CA-Jobtrac 3. the installation of the CA-Jobtrac internals was not successful.Verification Messages Received The following sequence of messages should appear on the JES JOB LOG for the JOBT@#$J job.IEFUJV EXIT DETECTED THE IVP JOB GJTRIVP2 .THIS TESTS THE WTO INTERFACE GJTRIVP2 . These messages indicate successful execution of the IVP.IEFUJI EXIT DETECTED THE IVP JOB GJTRIVP2 . If you do not receive these messages.IEAVMXIT DETECTED THE IVP WTO @#$J .IEFUJV EXIT DETECTED THE IVP JOB GJTRIVP2 . IEF1961 GJTRIVP2 . you might receive duplicates of the GJTR exit messages.GJTRIVP2 .

CA-Jobtrac functions as an operating system for production control. Testing. New storage is acquired following a backout of CA-Jobtrac. archives. Chapter 7. The expanded CSA is not released or reused when CA-Jobtrac is backed out of the system using the 'F JOBTRAC. Add approximately 535KB plus 25KB per checkpoint cylinder (4 cyl x 25KB = 100KB) for each version. Extended CSA (above the line) will also grow.5 for several days. make it your production system. You should schedule routine maintenance. and so on. using CA-Jobtrac Version 3. Running Multiple CA-Jobtracs 7-1 . Note: The CSA is reused whenever CA-Jobtrac is stopped and restarted under normal circumstances. You should treat a new version of CA-Jobtrac just as you would a new version of any major product. Do your installation and testing at times that allow the most thorough testing with the least impact on your data center. Testing.5 just as you tested the prior version of CA-Jobtrac when you first installed it. take into account the amount of CSA the previous versions will need.5. Each previous version requires at least 150KB below the line.BACK' operator command. Take time to familiarize yourself with the new functions and facilities. When you are comfortable with Version 3.5. backups. Upgrading. General Procedure You should test CA-Jobtrac Version 3. Upgrading.Chapter 7. Memory Requirements If you plan to run previous versions of CA-Jobtrac with Version 3. Running Multiple CA-Jobtracs When using all the functions and features to their fullest.

you might get duplicate production JCL submitted. and DLIB libraries as Version 3. Version 3. Incompatibilities Version 3. TSO logon procedure. ■ All JCL override formats are compatible. Now Version 3.5 CANNOT be installed into the same SMP/E CSI. 7-2 CA-Jobtrac 3. Note: If you are using production SCL and JCL libraries.5 is compatible with other Computer Associates products.Version Compatibilities and Incompatibilities Version Compatibilities and Incompatibilities To ensure that you do not obtain CA-Jobtrac prior version load modules from the linklist libraries during testing.5 Feature Version 3.4 programs CANNOT share or access the Version 3. target.5 Getting Started .4 of CA-Jobtrac.4 checkpoint files.4 are compatible with Version 3.5 load library in your STC. we recommend that you test all your product SCL.5 as a production system. due to new SCL keywords. Compatibilities The following features in Version 3. ■ History file is both forward and backward compatible. Version 3. ■ All date card formats are the are compatible. since we have updated syntax checking for schedule loads. ■ Capture file is both forward and backward compatible. ■ All TRACAUTH table definitions are supported.5 features to your production schedules until you have accepted Version 3. you need to STEPLIB to your 3. Also. we recommend that SCL libraries are kept separately. However. you should not add new Version 3.5 programs CANNOT share or access the Version 3.5 checkpoint files. and all batch jobs executing CA-Jobtrac programs. We recommend that you use different SCL and JCL libraries.5: ■ All schedules are fully supported. Also. Also.

but if a new jobhist file is desired.4 of CA-Jobtrac for this job. and STEPLIB to the Version 3.4 jobhist. Use the backup file created from Step A as input. Testing. but if a new capture file is desired. and STEPLIB to the Version 3. you must: A) Use utility GCJFULDN to unload current checkpoint. Checkpoint ■ If using Version 3.5 STC. B) ■ If using below Version 3. or you can use the Version 3. Chapter 7. or you can use the 3.5 of CA-Jobtrac for this job. PDS Data Sets All JCL files and SCL DSNs can be copied to new libraries or used as they are for the CA-Jobtrac Version 3. PROCs. Capture The capture file format has not changed. History The jobhist file format has not changed.4 capture file.5 CAILIB for this job. Use GCJFFMT to format a new checkpoint. you can use IDCAMS REPRO to move data from old jobhist to the new HISTORY data set.4 9910 Service Pack 1. Running Multiple CA-Jobtracs 7-3 .Conversion Notes Conversion Notes This topic provides conversion notes on CA-Jobtrac files. build it with GJTRVFMT and point OLDCAP to the old capture file. and CLIST. Upgrading. Use utility GCJFRLDN to reload the checkpoint. you MUST use a formatted checkpoint file. and STEPLIB to the CA-Jobtrac 3. This job creates a backup of the checkpoint.4 9910 Service Pack 1 or above.

Release the production workload from 3. When using the BACK command.4 Production to 3.5 installation procedure. Make sure that all the ddnames for the checkpoint.5 CAILIB replaces the old CA-Jobtrac 3.PARM=BACK).5 Getting Started . Test the installation with the verification procedures in Chapter 6. CLISTs.” 9. Start the new CA-Jobtrac 3. and batch jobs executing CA-Jobtrac programs. Use the following as a guideline to upgrade from CA-Jobtrac Version 3. 4. 6. Issue the CA-Jobtrac HOLD command (F stcname. 7. Next shut down CA-Jobtrac 3.4 to CA-Jobtrac Version 3. Submit backup jobs for the checkpoint. see the CA-Jobtrac Operator Guide for details.5 STC (S stcname). capture. 5.4 TRACLINK loadlib and refresh LLA. and capture files reflect the correct names in your PROCs. Log on to CA-Jobtrac 3.5 Production These procedures recommend that the same tokens from Version 3.5: 1. “Startup and Verification. 8. Note: See Version 3.4 be used for the new CA-Jobtrac Version 3.5 and issue the STATUS command to verify version. You need to either IPL or back out the internals of CA-Jobtrac (S VINIT3.5. Complete the CA-Jobtrac Version 3. 7-4 CA-Jobtrac 3. and jobhist files. If using linklist.4 Production to 3.4 SAMPJCL for sample JCL.4 (P stcname). jobhist. make sure that your CA-Jobtrac 3. 2.5 Production Recommended Procedures for Upgrading Your 3. 3.5 (F stcname.HOLD).RELEASE).Recommended Procedures for Upgrading Your 3.

or you can RESTORE the files from the backup files from CA-Jobtrac 3.BACK) or IPL. CLISTs. or you can use the old DSNs from CA-Jobtrac 3.4 TRACPARM(RESOURCE). FLOWSTART= or FLOWEND= keywords and comment them out or remove them. @FLOW=. capture. Refresh LLA if needed. Make sure that all the ddnames for the checkpoint.Recommended Procedures for Upgrading Your 3.5 with a BACK (F stcname.5 capture and jobhist files. Note: When using the BACK command. jobhist. Put the CA-Jobtrac 3. Start CA-Jobtrac 3.5 Production Returning to Prior Version Use one of these procedures to return to a prior version of CA-Jobtrac. 2.4.4 (S stcname). Shut down CA-Jobtrac 3.4 TRACLINK back in the linklist (if that is where it was). Edit the RESOURCE member of PPOPTION and remove or comment any two-character resource codes that you have defined. Two-character resources generate errors when CA-Jobtrac attempts to load the resource table. 7. Testing. Returning to 3. 5. and batch jobs executing CA-Jobtrac programs. and jobhist files from the backups created when upgrading from 3. 6. Chapter 7.4. You can use the CA-Jobtrac 3. Run the GJTRSC35 utility with no PARM (or PARM=DETAIL) to remove the CPM and two-character resource information that will not be properly handled by Release 3.4 Production to 3.4 for the checkpoint. see the CA-Jobtrac Operator Guide for details. Upgrading.4 1. 4. and capture files reflect the correct names in your PROCs. Or use the table that you had defined resources in the CA-Jobtrac 3. Running Multiple CA-Jobtracs 7-5 .4. Edit any of your schedules that had been updated to use the RS=. 3.

The default is to report only the records that had data removed. The default is to update the checkpoint with the changes.4 Production to 3. DETAIL Reports all the records in the checkpoint.4. The sample shows passing a PARM of TEST to the program. without updating the checkpoint.Recommended Procedures for Upgrading Your 3.4 using the same checkpoint file that 3. The following parameters may be specified on the EXEC statement PARM= keyword. This is only intended to be used in the event that you need to return to 3.5 Production The GJTRSC35 Utility The GJTRSC35 utility removes data from the checkpoint that was introduced by CA-Jobtrac Release 3. whether they had to have data removed or not.5 had been using. TEST Processes the checkpoint and reports the changes that would be made.5 Getting Started .5 and is not properly handled by CA-Jobtrac Release 3. 7-6 CA-Jobtrac 3. Sample JCL for running the GJTRSC35 utility is in SAMPJCL(GJTRSC35).

Test the new CA-Jobtrac 3. you can use the defaults. Running Multiple CA-Jobtracs 7-7 .Recommended Procedures for Upgrading Your 3. you need to: a.5 Test System 1.5 Production Recommended Procedures to Run 3. Files a. AMR. You HAVE to use the new token for the new jobhist file.4 Production and 3. empty capture data set.5. CLIST. Jobhist: Start with a new. When starting the CA-Jobtrac Version 3. 2. Choose a new AUTOSCHD character. 3. c.” 6. empty jobhist data set. Testing.5. 4.4 Production to 3. Otherwise. b. empty checkpoint data set. You can copy over your ADR. d. Note: The JOBTRAxx member in PPOPTION data set needs the appropriate options set for the new checkpoint and AUTOSCHD character since they are initially set to the default values. all new ddnames. Perform the installation verification procedures in Chapter 6. Upgrading. and tokens. Chapter 7. Log on to CA-Jobtrac 3.5. b. Also check other options that you want to set. and SCS tables for the new jobhist since they are initially set to the default values. Create new STC procedure.5 installation. CCPF. Start the new CA-Jobtrac STC 3. Checkpoint: Start with a new. Choose a new token. c. You HAVE to use the new token for the new checkpoint file. and any batch jobs executing CA-Jobtrac programs using the new CAILIB as a STEPLIB. Capture: Start with a new. 5. Create a new CA-GSS subsystem ID. “Startup and Verification.

Do NOT change any of the production CA-Jobtrac PARMs or data sets in the STC. //JOBTRACy DD DISP=SHR. Look at SAMPJCL member STAGE2. 7-8 CA-Jobtrac 3. Add a //STEPLIB DD if needed to this PROC.checkpoint DISP=SHR.capture b) Similar updates need to be added to your logon CLIST for the new JOBTRACy and GSSx and any PROCs that use CA-Jobtrac programs.DSN=your. we suggest you just copy the existing production copies into a unique set of files for the JOBTRACy PROC.DATA DISP=SHR. You can still use the existing TRACSnnn.DSN=your. Create a new JOBTRACy PROC with a unique name such as JOBTRACy. 8. TRACTnnn.histfile //CAPTURE DD DISP=SHR. AUTO-SCHD character and class must be unique to each CA-Jobtrac.DSN=your. but RESOURCE and EXCLPARM would be shared otherwise. DYNAMLOC member. but CA-Jobtrac will have no problem sharing these libraries. PROCs. MAKE SURE AMPLE CSA AND ECSA IS AVAILABLE if running multiple CA-Jobtracs.Procedure to Run Multiple CA-Jobtrac STCs on Same CPU Procedure to Run Multiple CA-Jobtrac STCs on Same CPU 1.new. TRACDnnn. 2. This recommendation is good sense.histfile DISP=SHR. However.new.DSN=your.checkpoint //JOBHISTy DD DISP=SHR. or TRACRnnn files if you would like. 5. 6.DSN=your.histfile.DSN=your.DSN=your. 7. or CLIST. Make the following changes: a) Allocate new files with the new token.5 Getting Started .capture 4. 3. This is not necessary. //JOBTRACy //JOBHISTy //SEQHISTy //CAPTURE DD DD DD DD DISP=SHR. You need to have a new CA-Jobtrac token and a new SSID for CA-GSS.new. Consider creating a new PPOPTION.new. TRACJnnn.

Add a //JOBTRACy DD DISP=SHR. Chapter 7. where modules from different levels are executed at different times. Upgrading.) 11. 14. Create a new logon CLIST for the JOBTRACy logon. This can lead to very sneaky bugs. it will not work. You will be required to add the CAILIB for the new JOBTRACy as a STEPLIB or ISPLLIB. CA-GSS Considerations a) b) You must create a new GSSx PROC to go with the new JOBTRACy PROC. You must copy the production CA-Jobtrac PARMs (JOBTRA00) to the new JOBTRACy PPOPTION file. Files should be allocated as they are for the new STC. c) 10. Running Multiple CA-Jobtracs 7-9 .) Caution DO NOT USE SSNAME AS EXISTING PRODUCTION CA-GSS!!!! (CA-Jobtrac uses that SSID. STEPLIB is necessary for CAILIB. not the old CLIST. 12. It loads the hooks dynamically and should start up GSSx as well.checkpoint GSSx can still use existing IMODS but MUST have a different SSNAME defined such as SSNAME IS35. Testing. If CA-GSS tries to use the same one. If you are using CA-11 you must add the RERUN=CA-11 PARM and the INSERTRMS=x. except possibly if CA-GSS can be guaranteed to be up first. GSSx will execute PGM=SRVSYS. In JOBTRACy GLOBAL OPTIONS you must define the GSSx started task and the SSNAME IS35.CAILIB to this PROC if needed. (RUNPARM member. It should have all the new files allocated just like the original production CLIST. You cannot log on in split screen to multiple CA-Jobtracs.DSN=new. where x is class to be monitored by CA-11.Procedure to Run Multiple CA-Jobtrac STCs on Same CPU 9. into the JOBTRA00 member of the PPOPTION for JOBTRACy. Start JOBTRACy on the system. Do not risk it. Add a //STEPLIB new. ISPLLIB is not sufficient. 13. No changes should be required.

You can have separate JES spools on your systems or a shared JES spool environment.Procedures for CA-Jobtrac in a Shared DASD Environment Procedures for CA-Jobtrac in a Shared DASD Environment CA-Jobtrac is capable of controlling the workload across multiple systems with shared DASD. The SMF system IDs defined in the JOBTRAnn member are stored in the CA-Jobtrac checkpoint data set. To switch the primary system. and SYNCSYS3. and you plan to start CA-Jobtrac tasks on both of them. SYNCSYS1 defines the primary system. You must start CA-Jobtrac on each system where you would like the workload to be monitored. Also view the primary and secondary definitions from ISPF by looking at the SYSID priority list (SYS OPTS) on the CA-Jobtrac global options panel. When installing CA-Jobtrac in a multiple-system environment. They monitor the events that run on the system that are submitted by the primary system. jobhist. Recycling CA-Jobtrac has no effect on what is stored in the checkpoint data set.ACTSYS=xxxx 2. When using a shared DASD system. SYS1 is the primary CA-Jobtrac. CA-Jobtrac checkpoint. Each keyword points to the SMF system ID of the appropriate system. Define the primary and secondary monitor systems in the JOBTRAnn member of the PPOPTION data set by using the keywords SYNCSYS1. SYS2 and SYS3 are your secondary monitor systems. the following considerations apply: 1. SYNCSYS2 and SYNCSYS3 define the secondary monitor systems. review “Serialization Considerations for Shared DASD Users” on page 2-19. 5. All tokens for the DD statements MUST be the same. 4.5 Getting Started . 3. and capture files are shared between the primary and secondaries. The monitor systems do not submit any events. Note: Updating the options SYNCSYS1 through SYNCSYS3 requires that ALL CA-Jobtracs on each system be recycled to switch the primary. The primary system is where all event submission takes place. 7-10 CA-Jobtrac 3. SYNCSYS2. These considerations assume that you need at least two or more systems with shared DASD. you MUST use the modify command F stcname. For example.

PRIMARY SUBMISSION SYSTEM ASSIGNED. Running Multiple CA-Jobtracs 7-11 .) For example. Testing.Procedures for CA-Jobtrac in a Shared DASD Environment The following CA-Jobtrac message displays in the JES log on the primary system. if SYS1 is currently the primary and you would like to make SYS3 the primary.VERIFY THAT THE PRIMARY JOBTRAC IS INACTIVE AND REPLY TO CONTINUE (Y/N) R 49. The following CA-Jobtrac message displays in the JES log on the secondary systems.ACTSYS=SYS3 You get the following WTOR on your console: F JOBTRACY. STC 5657 JOBTRAC .PRIMARY SUBMISSION SYSTEM (SYS1). STC 1195 JOBTRAC .ACTSYS=xxxx (where stcname is the CA-Jobtrac started task name and xxxx is the SMF ID of the system you would like to make the primary.AUTOMATION MONITOR SYSTEM (SYS2). TRAC1 68I ACTSYS=SYS1 command processing complete You should reply yes. Chapter 7.Y JOBTRAC . Upgrading. and the primary will be switched. Changing Primary Submission System CA-Jobtrac gives you the ability to change the primary system. You can issue the modify command: F stcname.ACTSYS=SYS1 49 TRAC737W . you would issue the command: F stcname.

5 Getting Started .7-12 CA-Jobtrac 3.

Troubleshooting 8-1 .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.

Each of these procedures is detailed on the following pages.Diagnostic Procedures Diagnostic Procedures See the flowchart below for a summary of the procedures you should follow if you have a problem with a Computer Associates software product. 8-2 CA-Jobtrac 3.5 Getting Started .

Troubleshooting 8-3 . try to identify the cause and resolve the problem. and problem report and contact Computer Associates Technical Support. and so forth) changed? From your response to these questions and the diagnostic data. Has this situation occurred before? What was different then? 4. What was the sequence of events prior to the error condition? 2. Type of Problem Installation Procedure Save all SMP/E RECEIVE. listing. Then. and ACCEPT output and any other output generated from any other installation step. follow the instructions in the corresponding right column to generate useful diagnostic data. Have you recently installed a new version of the operating system? 6. APPLY. User and system abends Interpreting Diagnostic Data When you have collected the specified diagnostic data. Collect the tape. Follow procedures (later in this chapter) to generate a problem report. disk drives. Chapter 8. What circumstances existed when the problem occurred and what action did you take? 3.Diagnostic Procedures Collecting Diagnostic Data In the table below. Obtain SYSMDUMP and dump to tape. use the left column to categorize the problem your site has encountered. Has the hardware configuration (tape drives. write down your answers to the following questions: 1. Did the problem occur after a particular PTF was applied or after a new version of the software was installed? 5.

0 or higher or Microsoft Internet Explorer 3. you can: ■ ■ ■ ■ Open new issues Browse or update your existing issues and enhancement requests Perform keyword searches Download solutions. and documentation Requirements for Using StarTCC The following are the requirements to use StarTCC: ■ You must be a Computer Associates client with a current maintenance agreement. Browsers that meet the HTML requirement support the following functions. PTFs. Computer Associates encourages you to "surf the net" to the Computer Associates home page at ca. including: ■ ■ ■ ■ ■ Service and support Product information and sales CA-World conference information Press releases Computer Associates user groups StarTCC.5 Getting Started .com.Accessing the Online Client Support System Accessing the Online Client Support System Computer Associates is making extensive use of the Internet for your benefit. interactive access to Computer Associates product support information through the Internet.0 or higher. and important notices regarding Computer Associates products. which are required for StarTCC: – Secure sockets layer (SSL) to encrypt your transaction traffic – Encrypted data records (known as COOKIES) – HTML tables 8-4 CA-Jobtrac 3.0 or higher.com and the support site at eSupport. maintenance. Using StarTCC. such as Netscape Navigator 2. The Computer Associates Internet site provides a great variety of information about Computer Associates products and services.ca. ■ You must register through the Computer Associates Internet site. gives you real time. ■ You must access the Internet with a browser that supports the HTML specification 2. the web-based portion of CA-TCC (CA-Total Client Care).

com The StarTCC options are: ■ StarTCC Information ■ StarTCC Registration ■ Access StarTCC These options are described below. and instructions for configuring your browser. site ID. StarTCC Information Select the information option to view background information for StarTCC. You may need to configure your browser to enable SSL. There are prompts for all required information. StarTCC provides one for you when you register. E-Mail address. StarTCC Registration Select the registration option to identify yourself to StarTCC. Be sure to review this section for updates or information not included here. CA-StarTrak PIN. Access StarTCC Select the access option to begin using StarTCC. Once your sign-on is validated. When prompted. you can perform the following: Open a new issue Open an issue for. Chapter 8. and Enhancement Requests (DARs). Guidelines for doing this are provided on the Computer Associates Technical Support page. one of your Computer Associates products. or request an enhancement to. including your name. enter your user ID and password.ca. Closed. You must register before you can access StarTCC online. go to eSupport. postal address. Accessing StarTCC To access StarTCC. Troubleshooting 8-5 . company name. and desired password for accessing StarTCC. Note: If you do not have a CA-StarTrak PIN.Accessing the Online Client Support System StarTCC Security StarTCC runs as a secured server (SSL). The issues are grouped into three categories: Open. Browse your issues and enhancement requests Display all issues for your site. details about the prerequisites.

Display StarTCC news items View and download recently published solutions for Computer Associates products. To access the Support Phone Services Directory. Display your site's licenses View a list of all the Computer Associates products for which your company site is currently licensed. phone number. problems.Accessing the Online Client Support System Browse and/or download solutions Specify criteria for selecting solutions. Update your StarTCC profile Make changes to your default E-mail address. StarTCC.ca. and password whenever necessary. Search the Computer Associates knowledge base Specify criteria for searching the Computer Associates database for solutions.5 Getting Started .com and click on Contact Us. set your browser for eSupport. instructions for downloading from StarTCC. 8-6 CA-Jobtrac 3. which you can then view or download. and helpful information for using CA-StarTrak. and keywords that can provide you with immediate answers to your product support questions and concerns. Accessing the Technical Support Phone Services Directory The Computer Associates Technical Support Phone Services Directory lists each Computer Associates product and the telephone number to call for primary support for that product. or other Computer Associates products.

If you need assistance obtaining a license key or authorization code. contact the CA-TLC: Total License Care group through eSupport.CA-TLC: Total License Care CA-TLC: Total License Care Many Computer Associates software solutions use license keys or authorization codes to validate your hardware configuration. Chapter 8.com. Troubleshooting 8-7 .ca.

please have the following information ready before contacting Computer Associates Technical Support: ■ All the diagnostic information described in “Collecting Diagnostic Data” on page 8-3 ■ Product name.Contacting Technical Support Contacting Technical Support For further technical assistance with this product. Technical Support is available 24 hours a day.ca.com for a complete list of Computer Associates locations and phone numbers. please contact Computer Associates Technical Support at eSupport. ■ A severity code.5 Getting Started . ■ Product name and version number of any other software you suspect is involved. seven days a week. ■ Your company name. Use the following to determine the severity of the problem: 1 2 3 4 a "system down" or inoperative condition a suspected high-impact condition associated with the product a question concerning product performance or an intermittent low-impact condition associated with the product a question concerning general product utilization or implementation 8-8 CA-Jobtrac 3. ■ Your name. ■ Version level and PUTLEVEL of the operating system. operating system. version number. telephone number and extension (if any). If you are unable to resolve the problem. ■ Your site ID. and genlevel. This is a number (from 1 to 4) that you assign to the problem.

a notice is sent to all current clients. When a new version of the system is available. Chapter 8.Product Versions and Maintenance Product Versions and Maintenance Clients are requested to operate only under currently supported versions of the product. Clients with current maintenance agreements also receive ongoing product maintenance. Troubleshooting 8-9 .

■ Enter your request through StarTCC.5 Getting Started . You can use either of two methods to request enhancements: ■ Contact your Account Manager who will initiate a Demand Analysis Request (DAR) for you. All suggestions are considered and acknowledged.com.ca. the Computer Associates web-based. 8-10 CA-Jobtrac 3.Requesting Enhancements Requesting Enhancements Computer Associates welcomes your suggestions for product enhancements. interactive support system at eSupport.

NJE Support The following sections describe changes or additions to CA-Jobtrac as a result of adding NJE support.Appendix A. Appendix A. NJE Support A-1 .

Installation and Setup Installation and Setup ■ CA-Jobtrac NJE support requires CA-GSS. ■ A CA-Jobtrac token is the x in the Jobtracx DD statement. you should specify the token of the submitting CA-Jobtrac itself in the token list. A-2 CA-Jobtrac 3. If you explicitly specify tokens and you submit NJE jobs to the submitting node itself. ■ NJE systems require all CA-Jobtracs to be primary CA-Jobtracs and not monitor CA-Jobtracs. CA-Jobtrac can only successfully capture sysout in an NJE environment if the JES job number ranges on the submitting and executing nodes do not overlap and output is returned to the submitting node in a timely manner (less than 15 seconds). This is done by listing up to 39 tokens. the NJE Node Tokens field becomes significant. If you leave the field blank. The token identifies and differentiates individual CA-Jobtracs. See the Unicenter TNG Framework for OS/390 Getting Started and the Unicenter TNG Framework for OS/390 Administrator Guide for information about GoalNet. If you leave this field blank. The NJE NODE option allows you to specify whether to activate the CA-Jobtrac NJE support for this instance of CA-Jobtrac on this system image. do one of the following: – Only start up one NJE-capable CA-Jobtrac on any single system image – Specify nonoverlapping tokens for each CA-Jobtrac running The JES /*ROUTE or /*XEQ statements identify an event as an NJE event. The specified NJE nodes apply only to the NJE events for the CA-Jobtracs which are specified as being NJE nodes. If you specify Y. CA-GSS must be set up to include networking support for all JES nodes in which CA-Jobtrac is to be used for NJE support. ■ The CA-Jobtrac global options panel of the CA-Jobtrac global options menu includes two fields for NJE support: NJE NODE (Y/N) and NJE Node Tokens (see Options on the CA-Jobtrac global options panel in this guide for more information). This is done using the GoalNet features of CA-GSS. you specify which CA-Jobtrac events are recognized by this CA-Jobtrac.5 Getting Started . all tokens (that is all events from all CA-Jobtracs) are processed by this CA-Jobtrac. All other CA-Jobtrac instances recognize only their own tokens. In the NJE Node Tokens field. It is important to use a SYSOUT package in an NJE environment.

CA-Jobtrac cannot properly track a manually rerouted jobo5cthe he talready gonecogall ■ In In an NJE enviroion ADR TjT* uiedworksy users localmissNJE■ an NJE enviroion AMR TjT* uiedworksy users localmissNJE■ ■ ■ In In an NJE enviroion tCPF TjT* users executSs rsystemJiTute ws333. an NJE enviroifiedev stata ofresources (executSubmissNJEjn NJE .Job Submission Job Submission ■ AUTO-SCHD jobs running on an NJE node are not supported.t su otted joboafremot corTjtherported. NJE jobs must use the JES /*ROUTE XEQ or /*XEQ control statements for CA-Jobtrac to recognize them as NJE jobs. ■ DUMMY jobs running on an NJE node are not supported. if NOTIFY is specified. ■ In an NJE environment. ■ Use JES /*ROUTE XEQ or /*XEQ control statements to route NJE jobs to other nodes. only users on the node on which the NJE job is run will be notified of abend or error conditions for that node based on information in the TRACAUTH table defined for that node.

■ The NJE surrogate contains a subset of the information from the actual checkpoint record. the submitting node's CA-Jobtrac ISPF display will indicate its executing status. ■ When the NJE job actually begins execution on the executing node. ■ TRACX09 is invoked at both the submitting and executing node. and recovery purposes. display.5 Getting Started . ■ Any Notifies as specified in the TRACAUTH table will only be done on the executing node as defined in the executing node's TRACAUTH.Job Execution Job Execution ■ The NJE job will be tracked by CA-Jobtrac. The information is viewable but not modifiable by the CA-Jobtrac ISPF interface user. A-4 CA-Jobtrac 3. ■ An NJE surrogate checkpoint record is added to the remote CA-Jobtrac checkpoint data set for tracking.

originating node down). NJE Support A-5 . CA-Jobtrac can only successfully capture sysout in an NJE environment if the JES job number ranges on the submitting and executing nodes do not overlap and output is returned to the submitting node in a timely manner (less than 15 seconds). networking error. ■ If the return of the termination status of a job back to its originating node is successful. No history information is copied to the history file at the 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. the NJE surrogate checkpoint record is automatically deleted at the executing node. the NJE surrogate record is retained on the checkpoint. History information is copied to the history file at the submitting node. Once the status is posted at the originating node. It is used to attempt to retry the returning of status at the next CA-Jobtrac startup. ■ If the returning of termination status is unsuccessful for whatever reason (for example. ■ It is important to use a SYSOUT package in an NJE environment. normal CA-Jobtrac processing occurs. ■ The NJE surrogate can only be removed by the successful return of status or the next CA-Jobtrac job archive run with the ALL option. Appendix A.

Q. time zone differences are taken into consideration and all times are adjusted to reflect local time. N. A-6 CA-Jobtrac 3. S. ■ The P (purge) line command can be used to release an NJE job on the submitting node when it is in a hung condition with either an NAWT or EXE status because the NJE node failed to post the termination status. O. The status on the Scheduled Event Display for these submitted NJE jobs includes an N instead of a J preceding the JES job number. the Original Version Number of this job on the submitting node. and 0 (zero). The new fields which are displayed on this panel for any NJE submitted jobs are the JES Node Name of the submitting node. *.ISPF Interface ISPF Interface ■ NJE jobs in Awaiting Execution or Executing status have a Scheduled Event Display status of N-status-nodename. ■ On displays of times for NJE jobs on either the submitting or executing nodes. ■ Only a subset of the normal line commands on the Scheduled Event Display are available for remotely-submitted NJE jobs. ■ NJE jobs running on the executing node have an NJE surrogate checkpoint record. the new NJE Execution Detail panel is displayed which contains a subset of the information normally available when selecting an event for display. nodename is the remote JES node name and ssss is the submitting system's SMF system ID. ■ When the S line command is used to Select an NJE submitted job. SYS=ssss where status is either NAWT for Awaiting Execution or EXE for Executing. P. the GSS Node Name of the submitting node. You are now able to perform other appropriate actions against the job. The line commands available are: @. ■ The event execution detail display for executing or completed jobs displays the JES node if the job was an NJE job. and NJE status. The purge command resets the completion status and places an Output Release on the job.5 Getting Started . ?. See the CA-Jobtrac Operator Guide for more information about the NJE Execution Detail panel.

NJE Support A-7 .ISPF Interface ■ When selecting events to display on the Scheduled Event Display. those jobs which have been remotely submitted from another node. while the S code selects only NJE surrogate jobs. a N=nodename command is available. Appendix A. ■ The K= primary command supports two selection types of N and S. The N code selects for display only NJE jobs on this node submitted to other nodes. Specifying this command with the desired JES node name limits the display to NJE jobs submitted to or from the designated node.

an NJE job with this status remains on the CA-Jobtrac checkpoint so that a retry of posting the termination status to the originating node can be performed. Otherwise. A % next to an event name denotes the event is an NJE job submitted to another system. A-8 CA-Jobtrac 3.Batch Archiving and JREPORT Batch Archiving and JREPORT ■ You must use the ALL operand to force the archiving of NJE jobs. A # next to an event name denotes the event is an NJE job submitted from another system.5 Getting Started . ■ When listing event information for an archive or JREPORT. An @ next to an event name denotes the event is a dummy job. regardless of the special NJE status REMOTE POST ERROR. an * next to an event name denotes the event is a REXX IMOD.

this is blank. and TTime. this is blank. Returns the information in the hh:mm mm/dd format including the colon and slash. STime. Indicates whether the JCL associated with this AUTO-SCHD job has been submitted and recognized by CA-Jobtrac.REXX Stack Information for NJE Jobs REXX Stack Information for NJE Jobs Prefix ETIM Information End time and date for the event. If this event is an NJE job which has been submitted to another JES node. If this is an AUTO-SCHD event. Otherwise. and TTime. Returns the information in the hh:mm mm/dd format including the colon and slash. Same options for definition as ATime. Otherwise. Indicates whether this is an NJE job. the JES node name on which the event is executing or has executed. NJE Support A-9 . indicates the event has been submitted and recognized by CA-Jobtrac. NJE (Yes or No) ONQueue (Yes or No) SUB_TIME or SUBMIT_Time Appendix A. Actual time and date the event is submitted for execution by CA-Jobtrac. NJE ONQU SUBT Keywords Keyword END_TIME or ETime JES_NODE or JESNode Options Same options for definition as ATime. STime. Up to eight-character JES node name where this event is executing.

5 Getting Started .A-10 CA-Jobtrac 3.

NT. Connecting Systems for Cross-Platform Scheduling B-1 . and UNIX to support cross-platform scheduling. Appendix B.Appendix B. Connecting Systems for Cross-Platform Scheduling This appendix is designed to assist you in setting up CAICCI network connections on OS/390. You can find more detailed information in the CA Reference Guide and the Unicenter TNG manuals for the specific platform.

Following is an example of the CCIPARM statement necessary to define a remote node to CAICCI on OS/390: NODE(TCPIPGW.XE21) Optionally.72.2 2. the following message indicates a successful connection to the remote Unicenter TNG machine nnnnnn: CAS96 3I .5 Getting Started . you can define the connection on OS/390 for the remote Unicenter TNG system. From OS/390. Ensure that the link for the appropriate TCP/IP product has been completed.141.2.85 .OS/390 CAICCI Installation and Considerations OS/390 CAICCI Installation and Considerations For CAICCI to support peer networking.CAICCI XE21 CONNECTED TO CAICCI nnnnnn B-2 CA-Jobtrac 3.USLIGPEX) CONNECT(USLIGPEX) The SYSID parameter in the CCIPARM member names specify the unique name to be used in connecting with this OS/390 system. in the syslog. This is described in the Unicenter TNG Getting Started in the Link-edit CAICCI for TCP/IP topic. This is not recommended since it is more manageable to define the OS/390 system on the NT or UNIX platform. The CCIPARMS control options must be updated to activate the CAICCI gateway tasks.2.7:1721. CAICCI must be linked with the TCP/IP product. These are described in Unicenter TNG Framework for OS/390 Administrator Guide in the CAICCI control options topic. SYSID(XE21) This name is specified on the remote CAICCI system to identify CAICCI on the OS/390 system. Following is a sample of the required protocol statement: PROTOCOL(TCPIPGW.

Ensure that you can ping the OS/390 system. CAICCI uses NetBEUI (NetBIOS). This entry is added when CAICCI remote services is installed. ccintrl rmt x:\tng\bin). Appendix B. Chapter 4. To install CAICCI remote. remote CAICCI must be installed and configured to connect to any machine that is part of cross-platform scheduling. Connecting Systems for Cross-Platform Scheduling B-3 . issue the following command: ccicntrol install rmt <path> -where path represents the $CAIGLBL000\bin (for example. You must ensure that the Workload Management Server Activated field is set to NO and the Workload Management Agent Activated field is set to YES. The PORT numbers on OS/390 and NT must match. If not. modify the TCP/IP setup on the PC as well as on OS/390 to make adjustments to make the ping successful. Remote CAICCI For cross-platform scheduling to be done. discusses configuration options for the Workload Agent(s). Workload Agent The Unicenter TNG Getting Started. 2. Communication Transport Protocol By default. All Unicenter TNG systems must use the same Communication Transport Protocol. caicci 1721/tcp Note: xxxxxxxx = Your Windows NT Directory Path. Verify that the xxxxxxxx\system32\drivers\etc\SERVICES file has an entry for CAICCI with the following port # assigned. Also.OS/390 CAICCI Installation and Considerations 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 in the Unicenter TNG Getting Started. the default PORT # must not be changed as CAICCI on the OS/390 system uses this for CAICCI communications. 1. This must be changed to use TCP/IP to communicate with OS/390. # CA-Unicenter remote daemon # CCI must be shut down and restarted if port is chgd.

OS/390 CAICCI Installation and Considerations 3. The default value is the TCP/IP host name. startup options—either STARTUP or NOSTARTUP. This field is optional and is not provided by default. You may use this file to indicate aliases for node names. buffer size—a value between 1024 and 32768 used for segmenting the data transfer. B-4 CA-Jobtrac 3. The default value is the TCP/IP host name. It contains a 'local' statement that applies to the local computer and 'remote' statements that apply to the remote nodes that exchange information with CAICCI. CCI name—a logical name that Unicenter TNG applications may use to insulate themselves from the network and any protocols being used. NOSTART implies that the remote system will be initiating the connection to this node. CCIRMTD is the name of the CAICCI configuration file.5 Getting Started . Important! Contact Computer Associates Technical Support before changing the buffer size. The \TNG directory must have a ccirmtd. NOSTART has the opposite meaning.rc file. STARTUP tells CAICCI to attempt a remote connection when activated. The format is ALIAS=<aliasname>. alias options—used to differentiate multiple remote computers having exactly the same first eight characters (when their host names exceed eight characters). see the alias 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 used as input to a name service to retrieve an IP address. It is generally not necessary to alter this field. This (TCP/IP name) is the same name that may be provided to the ping utility to determine whether a remote connection is live.

A DNS defined name could be used instead of an IP address. If this value is changed.111. Once the REMOTE statements have been defined.OS/390 CAICCI Installation and Considerations port options—optional numeric value set by default to 1721. Connecting Systems for Cross-Platform Scheduling B-5 . all systems in communication must be changed likewise. if they use the name PAYROLL. This means that any Unicenter TNG system within the network can send and receive messages to this system if they use the name PAYROLL independent of hardware or protocols. LOCAL BACKUPCLIENT 1 BKCLI 1 1 24 STARTUP This statement tells CAICCI that the local machine's TCP/IP name is BACKUPCLIENT001 and its network independent name is BKCLI001. the next startup of CAICCI should produce connections between all nodes listed in the REMOTE statements and the machines where the REMOTE statements reside. REMOTE Statements Remote statements are used for connection with UNIX and OS/390 machines. LOCAL Statements The following are examples of LOCAL statements: LOCAL=PAYROLL PAYROLL 1 24 STARTUP This statement tells CAICCI that the local machine's TCP/IP name is PAYROLL and that any remote system wishing to communicate with this system can do so by referencing PAYROLL as the name. The format is n=0 (no retry).121 and to internally register PAYROLL as the CAICCI name.111.222. BKCLI001 will be the name foreign computers can use to send and receive messages with this computer.222. >0 (seconds between retry). Appendix B. The format is PORT=<TCP/IP port number>.121 PAYROLL 1 24 STARTUP This statement tells CAICCI to attempt a connection to 141. -1 (exponential). The following are examples of REMOTE statements: REMOTE=141. Any Unicenter TNG system within the network can send and receive messages to this system independent of hardware or protocols. retry option—number of seconds between retry connect attempts.

.CA_Cal_Chk ) . This can be verified either through the Services task under Control Panel or by issuing the command: ccicntrl start rmt (starts the rmt service) If you need to start the Unicenter TNG REMOTE Service.Daemon. . . . B-6 CA-Jobtrac 3. .AK .CA_WHD_IMCA_CICSADG3) . .MAIN ) . . ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) ) type (L) type (L) type (L) type (L) type (L) type (L) type (L) type (L) type (L) type (R) type (R) type (R) type (R) type (R) type (R) type (R) type (R) type (R) type (R) type (R) type (R) type (R) type (R) type (R) type (R) type (R) type (R) type (R) type (R) type (R) type (R) ) type (R) In this example. .XE21UHD ) .SUBMITC Server ) .CAAPCDDSMAIN ) .WNT ) .UniappServer ) . . The Unicenter TNG REMOTE Service must be running.#CAIENF EXTRACT Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( Did( ) Did( .S9CICICSIMS1CICISMS1) .DSMFA21IDISP ) .B_HTO_PC_SERVER_1 ) .MUFSMS1_SERVER ) . issue the following commands: ccicntrl start rmt ccicntrl start nrs (starts the rmt service) (starts nrs service for CCII) To verify that CAICCI has established communications.B_CA_PC_SERVER_1 ) .CA-OPERA PRODUCT ) . . . .NTM49DB ) . .CA-OPERACAIWXLOG 89) . .SPMAGP_Y. .CAI_OPR_DAEMON ) . . .5 Getting Started . . .OS/390 CAICCI Installation and Considerations 4. .Daemon. .MVS_START_SERVER ) . .CAU9SET SetUp Mgr ) .WNT ) .CAUWV. .Sam. .HTO_PC_SERVER_1 ) . from the NT machine.S9CICICSBAG1CICSBAG1) . . .CA_PC_SERVER_1 ) . .CAS9VTAMCW41 ) . . the lines with XE21 indicate that the CAICCI connection has been made to TSO21. issue the following command from a MS-DOS prompt: ccii Sample output: time = 4 Old(LVL1NT Old(LVL1NT Old(LVL1NT Old(LVL1NT Old(LVL1NT Old(LVL1NT Old(LVL1NT Old(LVL1NT Old(LVL1NT Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 Old(XE21 . .ROUTER_SERVER ) .PCNET. LVL1NT is the NT machine where Unicenter TNG is installed.MUFBAG1_SERVER ) .S9CICICSBAG3CICSBAG3) . .CA-OPERACAIWEMAL ESI) . .W41 _SPAWN_SERVER ) .CA7PROD Job track ) . .S9CICICSSMS1CICSSMS1) .

Index Special Characters @AMRGEN statement 5-47 CA LMP 2-11 CA-11 4-5. 5-71 CA-Librarian 3-9 interaction with CA-Jobtrac 2-21 modules 3-9 CA-Librarian support support 5-29 CA-Multi-Image Integrity. allowing 5-22 B BookManager files 3-4 C Index X-1 . 2-12 CA-EARL 2-13 CA-GSS and CA-Jobtrac 2-15 and NJE A-1 modifying 5-2 overview 2-12 requirements 5-73 CA-HYPER-BUF 2-21 CA-JCLTrac DB2 setup for 5-58 enabling 5-59 UCT setup 5-58 user control table 5-43 user control table setup 5-58 CA-Jobtrac token 4-12 CA-Jobtrac Global Options panel description of options on 5-21 sample panel 5-21 CA-Jobtrac subsystem 2-15 CA-Jobtrac WorkStation 3-10. interaction with CA-Jobtrac 2-21 CA-Panvalet interaction with CA-Jobtrac 2-22 modules 3-8 CA-TCC (CA-Total Client Care) 8-4 A Abending event output. holding 5-27 ACCEPT processing for CA-Jobtrac Accessing CA-Jobtrac using a CLIST 6-4 using ISPF 6-3 Adobe Acrobat PDFs 3-4 AMR disabling support for 5-46 enabling support for 5-46 APF authorization 4-8 API (Application Programming Interface) 3-10 APPLY processing for CA-Jobtrac 3-7 Archive tape block size 5-36 disposition 5-36 high-level qualifier 5-35 retention period 5-36 unit 5-35 Archiving NJE jobs A-8 ARM (Automatic Restart Management processing) 4-22 Auto-queue job classes 5-29 AUTO-SCHD. 5-55 CA-Blockmaster 2-21 CA-C 2-11. allowing 5-22 Automatically scheduling events using JCL. interaction with CA-Jobtrac 2-21 CA-Multi-Image Manager.

definition of exits.5 Getting Started . PDS for 5-37 COMMNDxx. NJE 5-30 Cross-Platform Scheduling and Unicenter 5-73 connecting systems B-1 global variables 5-77 IMODs 5-76 Customization job. creating 3-5 Documentation libraries 2-8 documentation. modifying 6-2 Condition code checking 4-33 Conversion general procedure 7-1 notes 7-3 security issues 7-1 CPM 4-27 Cross node query.CA-TLC: Total License Care 8-7 CA-View interaction with CA-Jobtrac 5-69 interface 2-22 interface with 5-69 CA-XPS 2-13 CAICCI 2-13. setting up 5-7 1-8 G GJTRTRT2. 5-73. unloading 3-4 DSNAME statement 5-62 DYNAMLOC 5-12 E END statement 5-64 Ending CA-Jobtrac 6-4 Enhancements 1-3 Environmental dependency maximum running time 5-29 number of retries 5-29 retry interval 5-26 Execution dependencies. STAGE1 4-2 Customizing CA-Jobtrac WorkStation Server 5-71 Data sets (continued) placement considerations 2-18 recommended initial sizes 4-16 Data sets. required by CA-Jobtrac 1-11 Data sets allocated by STAGE2 job stream 4-10 allocating 4-9 X-2 CA-Jobtrac 3. types of 1-8 Distribution libraries. IEFTB724 linked to 3-8 Global JCL variables library 2-8 Global options in JOBTRAnn 4-19 procedure for using ISPF interface to set 5-19 setting using ISPF interface 5-19 D DASD. defining 3-5 DDNAME statement 5-63 Dependencies. updating 5-18 Command set scheduling. CA-Jobtrac 2-5 Date format 5-21 Date library 2-8 DB2 binding plans for CA-JCLTrac 5-67 creating objects for CA-JCLTrac 5-65 granting authority for CA-JCLTrac 5-68 DB2 setup for CA-JCLTrac 5-58 DDDEF. B-1 CAIENF 2-14 CAIMAC library 2-6 CAIRIM 2-12 CAS9 procedure 3-9 Catalog error response 5-27 Checkpoint data set description 2-5 placement considerations 2-18 RAMAXCC JOBTRAnn Option 4-33 CLASS statement 5-62 CLIST allocations.

data set placement considerations 2-19 Holiday action time 5-24 I IEACMDxx.Global termination IMOD Global variables 5-77 GoalNet 5-4 5-27 H Hardware requirements 2-9 History data set name 5-37 History file data set 2-5 History file sequential data set 2-6 History file. adding CA-Jobtrac to 5-18 IVP contents of 6-5 how to use 6-6 preparing to perform 6-6 procedure 6-7 J JCL enabling automatic checking 5-59 enabling checking 5-59 sample for loading JCLDOC 3-3 JCL libraries 2-8. using to set global options 5-19 ISPF main menu. STAGE2 4-7 Installation Verification Procedure contents of 6-5 how to use 6-6 preparing to perform 6-6 procedure 6-7 Installing CA-Jobtrac 1-1 Internals. defining 5-11 JES SYSOUT class 5-11 JMF PDS 5-36 Index X-3 . NJE considerations A-6 ISPF interface. production 2-8 JCL library. modifying 6-2 IEAVMXIT. temporary-use 2-8 JCLDOC library description of 3-3 loading from the product tape 3-3 sample JCL for loading 3-3 JCLTCTL table 5-43 JES cycling with CA-Jobtrac 2-17 interaction with CA-Jobtrac 2-16 JES command character 5-24 JES held job class. Computer Associates site 8-4 IPL 1-11 IPL prompt 5-21 IPLTABLE @AMRGEN option descriptions 5-49 @AMRGEN statement descriptions 5-48 @AMRGEN statements 5-47 IPLTABLE (continued) creating 5-47 maintaining 5-43 procedure 5-53 syntax rules 5-47 table 5-43 ISERVE starting procedure 5-30 subsystem name 5-26 ISPF interface. initializing CA-Jobtrac 6-2 Internet. global termination 5-27 IMODs CA-GSS server 5-76 INIT IMOD 5-13 Initializing CA-Jobtrac internals 6-2 initiation IMODs 5-12 Installation SMP/E tasks 3-2 Installation job stream. setting up 5-46 IMOD. 4-9 JCL library.

security authorization required for 2-24 JOBTRACx data set description 4-12 JOBTRAnn description of options 4-20 setting options 4-19 using multiple 4-19 M Memory requirements 1-11 detailed 2-10 summary 2-10 Merge the CA-Jobtrac API table 3-10 Messages. understanding 2-2 O Options in JOBTRAnn 4-19 Overview of SMP/E installation 3-2 P Password requirement rules 5-82 PDFs 3-4 PDS for command set scheduling 5-37 PDS for JMF 5-36 PDS member 3-9 PDS or library management 4-9 Phone Services Directory 8-6 Pre-installation considerations 2-9 Primary CA-Jobtrac 5-28 Print class archive 5-23 Procedure libraries.5 Getting Started . updating 4-18 Product tape receiving for CA-Jobtrac 3-6 X-4 CA-Jobtrac 3. interaction with CA-Jobtrac 2-21 Modules. specifying 5-26 support 5-26.job class. deletable 5-22 MIM. defining 5-11 Job classes 5-29 Jobflow 3-10 JOBTRAC task. converting to tables 5-43 Multi-CPUs and primary CA-Jobtrac system 5-28 Multiple CA-Jobtracs 7-10 K Key. LMP 3-9 KEYS DD statement 3-9 N NJE cross node query limit 5-30 node token. A-1 L Libraries CA-Jobtrac 2-7 documentation 2-8 JCL 2-8 remote password library 2-8 SCL 2-8 temporary-use JCL 2-8 Library Definitions panel description of options on 5-35 sample panel 5-35 Library or PDS management 4-9 Link CA-Librarian modules 3-9 Link CA-Panvalet modules 3-8 Link IEFTB724 to GJTRTRT2 3-8 LMP key 3-9 Location IDs 000 2-3 assigning 2-3 default 2-3 description 2-2 Locations. updating 4-18 Proclibs.

definition of 1-8 SCL libraries 2-8 Security authorization required for JOBTRAC task 2-24 installation tasks requiring authorization 2-24 Serialization by CA-Jobtrac 2-20 by IBM VSAM processing 2-20 SMF records. printing 5-23 SUBROOT keyword 4-37 Summary of release enhancements 1-3 Support Phone Services Directory 8-6 SVCs not required 1-11 Sysout capture CA-View interface for 5-69 defining classes for 5-31 enabling 5-24 line limit specification 5-29 requeue to another product 5-33 size specification 4-2 unit specification 4-2 volser specification 4-2 Sysout capture file creation of 4-10 data set placement considerations 2-19 Index X-5 .R RECEIVE performing for CA-Jobtrac 3-6 Receiving CA-Jobtrac product tape 3-6 Release enhancements summary 1-3 Remote password library 2-8 password location entity 2-3 Remote scheduling 5-73 Requirements hardware 2-9 software 2-9 Restart support 5-22 REXX IMOD maximum running time 5-29 ROOT user ID 4-37 RUN command ADD command Condition code checking 4-33 Running multiple CA-Jobtracs 7-10 S Scheduling dependencies. creating 3-5 installing CA-Jobtrac using 3-1 Link CA-Librarian modules 3-9 Link CA-Panvalet modules 3-8 Link IEFTB724 to GJTRTRT2 3-8 overview of installation procedure 3-2 RECEIVE processing for CA-Jobtrac 3-6 target libraries. creating 3-5 Software requirements 2-9 SPACE command enabling 5-54 STAGE1 customization job description 4-2 running 4-2 STAGE2 installation job stream description 4-7 modifying and running 4-7 running 4-7 StarTCC. suppressing writing of 5-6 SMFPRMxx customizing 5-6 example 5-8 SMP/E ACCEPT processing for CA-Jobtrac 3-7 SMP/E (continued) APPLY processing for CA-Jobtrac 3-7 considerations 2-18 distribution libraries. through CA-TCC (CA-Total Client Care) 8-4 Starting CA-Jobtrac 6-3 Step execution detail.

installation considerations 2-23 U UCT keyword. A-2 TRACAUTH table 5-43 description 5-9 TRACMAC parameters optional 4-5 required 4-2 TRACRnnn 2-8 Troubleshooting 8-1—8-9 TSO procedures optional DD statements for users 5-17 required DD statements for users 5-16 updating 5-16 X-6 CA-Jobtrac 3. creating 3-5 TCP/IP 5-73. B-1 optional DD statements for TSO users 5-17 remote password library 2-8 REMTCRED JOBTRAnn Option 4-34 SUBROOT JOBTRAnn Option 4-37 XPLATRERUN JOBTRAnn Option 4-43 Unicenter TNG Framework for OS/390 components CA LMP 2-11 CA-C 2-12 CA-EARL 2-13 CA-GSS 2-12 CA-XPS 2-13 CAICCI 2-13 CAIENF 2-14 CAIRIM 2-12 overview 2-11 UNIX B-1 unloading documentation 3-4 Updating LMP key 3-9 Upgrading overview 7-1 User control table CLASS statement 5-62 creating 5-61 DDNAME statement 5-63 DSNAME statement 5-62 END statement 5-64 example 5-64 explained 5-60 for CA-JCLTrac 5-43 setup for CA-JCLTrac 5-58 T Tables 5-43 Target libraries. 5-73.5 Getting Started . 5-71. general 4-14 messages associated with 4-14 setting up 4-14 Sysout Capture Options panel description of options on 5-31 Sysout print class 5-23 System options. 5-2. B-1 cross-platform scheduling 3-10. use of 5-61 UCT setup for CA-JCLTrac 5-58 Unicenter TNG communicating with 3-10.Sysout capture file (continued) determining size. B-2 Technical Support Phone Services Directory 8-6 Temporary-use JCL libraries 2-8 Termination IMOD 5-27 TNG communicating with 3-10 cross-platform scheduling 5-73 optional DD statements for TSO users 5-17 remote password library 2-8 REMTCRED JOBTRAnn Option 4-34 SUBROOT JOBTRAnn Option 4-37 XPLATRERUN JOBTRAnn Option 4-43 token 4-12.

4 compatibilities with Version 3.5 7-2 VINIT3 using to process IPL messages 6-2 using under the master subsystem 6-3 W WorkStation 3-10 X XPLATRERUN option 4-43 Index X-7 .5 7-2 incompatibilities with Version 3.User control table (continued) using 5-61 V Version 3.

Sign up to vote on this title
UsefulNot useful