R0JOBT11PIE

Unicenter CA-Jobtrac Job Management
Planning and Implementation Guide for CA-Datacom/AD r11

r11
R0JOBT11PIE
This documentation and any related computer software help programs (hereinafter referred to as the Documentation) is for the end user's informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the documentation for their own internal use, and may make one copy of the related software as reasonably required for back-up and disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for the product are permitted to have access to such copies. The right to print copies of the documentation and to make a copy of the related software is limited to the period during which the applicable license for the Product remains in full force and effect. Should the license terminate for any reason, it shall be the user's responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE. The use of any product referenced in the Documentation is governed by the end user's applicable license agreement. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.
All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Copyright 2006 CA. All rights reserved.
CA Product References This document references the following CA products: Unicenter CA-Jobtrac Job Management (Unicenter CA-Jobtrac) Unicenter AutoSys Job Management (Unicenter AutoSys JM) Unicenter CA-Easytrieve Report Generator (Unicenter CA-Easytrieve) Unicenter CA-MIM Resource Sharing (Unicenter CA-MIM) Unicenter CA-MII Data Sharing (Unicenter CA-MII) Unicenter CA-MIA Tape Sharing (Unicenter CA-MIA) Unicenter CA-MIA Message Sharing (Unicenter CA-MIC) Unicenter Network and Systems Management Job Management Option (Unicenter NSM JM Option) Unicenter CA-OPS/MVS Event Management and Automation (Unicenter CA-OPS/MVS) Unicenter CA-Scheduler Job Management (Unicenter CA-Scheduler) Unicenter CA-Spool Print Management (Unicenter CA-Spool) Unicenter Service Desk (Unicenter Service Desk) Unicenter CA-SYSVIEW Realtime Perfomance Management (Unicenter CA-SYSVIEW) Unicenter Universal Job Management Agent (Unicenter Universal Job Management Agent) Unicenter CA-View Output Archival and Viewing (Unicenter CA-View) Unicenter CA-7 Job Management (Unicenter CA-7) Unicenter CA-11 Restart and Tracking (Unicenter CA-11) Advantage CA-Datacom/DB Database (Advantage CA-Datacom/DB) AllFusion CA-Panvalet (AllFusion CA-Panvalet) AllFusion CA-Librarian (AllFusion CA-Librarian) eTrust CA-ACF2 Security (eTrust CA-ACF2) eTrust CA-Examine Auditing (eTrust CA-Examine) eTrust CA-Top Secret Security (eTrust CA-Top Secret)
Contact Customer Support For online technical assistance and a complete list of locations, primary service hours, and telephone numbers, contact Customer Support at http://ca.com/support.
iii
Contents
Chapter 1. Welcome . . . . . . . . . . . CA-Datacom/AD . . . . . . . . . . . . . . Features and Benefits . . . . . . . . . . . Production Scheduling Features . . . Email . . . . . . . . . . . . . . . . . . Unicenter Service Desk . . . . . . . . REXX . . . . . . . . . . . . . . . . . . Automatic Message Recognition . . . System Command Scheduling . . . . Specifying Additional Condition Codes JCL Management . . . . . . . . . . . Sysout Archival . . . . . . . . . . . . Other Benefits . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 2 3 3 4 4 5 5 5 5 6 6 6
Chapter 2. Overview of Components and Installation Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . Locations . . . . . . . . . . . . . . . . . . . . . . . . . CA-Datacom/AD DASD . . . . . . . . . . . . . . . . . Unicenter CA-Jobtrac DASD . . . . . . . . . . . . . . Checkpoint Database . . . . . . . . . . . . . . . . . Capture File Data Set . . . . . . . . . . . . . . . . . Setup Files . . . . . . . . . . . . . . . . . . . . . . . Calculate Database Size . . . . . . . . . . . . . . . Differentiate Copies of Unicenter CA-Jobtrac . . . CA-Datacom Sharing . . . . . . . . . . . . . . . . . . CA-Datacom/AD Sharing Overview . . . . . . . . . Database Access Options . . . . . . . . . . . . . . . Configuration Examples . . . . . . . . . . . . . . . . Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . Pre-Installation Considerations . . . . . . . . . . . . . . . Requirements . . . . . . . . . . . . . . . . . . . . . . CA Common Services . . . . . . . . . . . . . . . . . . CA LMP . . . . . . . . . . . . . . . . . . . . . . . . . CA-C . . . . . . . . . . . . . . . . . . . . . . . . . . . CA-Datacom/AD . . . . . . . . . . . . . . . . . . . . CA-Easytrieve . . . . . . . . . . . . . . . . . . . . . CA-GSS . . . . . . . . . . . . . . . . . . . . . . . . . CA-XPS . . . . . . . . . . . . . . . . . . . . . . . . . CAICCI . . . . . . . . . . . . . . . . . . . . . . . . . CAIENF . . . . . . . . . . . . . . . . . . . . . . . . . CAISSF . . . . . . . . . . . . . . . . . . . . . . . . . CAIRIM . . . . . . . . . . . . . . . . . . . . . . . . . CAISDI/els - Service Desk Integration . . . . . . . . CAIVPE . . . . . . . . . . . . . . . . . . . . . . . . . ViewPoint . . . . . . . . . . . . . . . . . . . . . . . .
7 8 . 8 11 12 12 13 13 14 15 16 16 16 18 22 24 24 26 26 27 27 27 28 28 28 28 29 29 30 30 30
Contents v
CA-Datacom/AD Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install a User SVC for CA-Datacom/AD Install the SVC with CAIRIM . . . . . . . . . . . . . . . . . . . Edit JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . IBM CBIPO . . . . . . . . . . . . . . . . . . . . . . . . . . . . Edit SAMPJCL Using the Supplied REXX Execs Under ISPF CA-Datacom/AD Product Installation . . . . . . . . . . . . . . Products Installed . . . . . . . . . . . . . . . . . . . . . . . . List Libraries for CA-Datacom/AD Products in JCL . . . . . . Unicenter CA-Jobtrac Considerations . . . . . . . . . . . . . . . . Subsystems . . . . . . . . . . . . . . . . . . . . . . . . . . . . JES Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Tape Information . . . . . . . . . . . . . . . . . . . CA Common Services Installation Tape . . . . . . . . . . . The CA-Datacom/AD Installation Tape . . . . . . . . . . . . The Unicenter CA-Jobtrac Installation Tape . . . . . . . . . The Latest Unicenter CA-Jobtrac Service Pack Tape . . . . SMP/E Considerations . . . . . . . . . . . . . . . . . . . . . . Data Set Placement Considerations . . . . . . . . . . . . . . CA-Datacom/AD Files . . . . . . . . . . . . . . . . . . . . . . Sysout Capture File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Recovery Planning Common CA-Datacom/AD Terms . . . . . . . . . . . . . . . Log File and Recovery File . . . . . . . . . . . . . . . . . . . . . . . . . System Failure or CA-Datacom/AD MUF Failure DASD Failure or Disaster Recovery . . . . . . . . . . . . . . Backup Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Types . . . . . . . . . . . . . . . . . . . . . . . . . . Backup Frequency . . . . . . . . . . . . . . . . . . . . . . . . Forward Recovery . . . . . . . . . . . . . . . . . . . . . . . . Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . . Other Products . . . . . . . . . . . . . . . . . . . . . . . . . . Interfaces with Other Products . . . . . . . . . . . . . . . . . . AllFusion CA-Librarian . . . . . . . . . . . . . . . . . . . . . . AllFusion CA-Panvalet . . . . . . . . . . . . . . . . . . . . . . CA-Blockmaster . . . . . . . . . . . . . . . . . . . . . . . . . BrightStor CA-HyperBuf . . . . . . . . . . . . . . . . . . . . . Unicenter CA-MIM . . . . . . . . . . . . . . . . . . . . . . . . Unicenter CA-SYSVIEW . . . . . . . . . . . . . . . . . . . . Unicenter CA-View . . . . . . . . . . . . . . . . . . . . . . . . Unicenter CA-11 . . . . . . . . . . . . . . . . . . . . . . . . . Other Products Through CA-GSS . . . . . . . . . . . . . . . System Considerations . . . . . . . . . . . . . . . . . . . . . . Security Considerations . . . . . . . . . . . . . . . . . . . . . . Chapter 3. Worksheets . . . . . . . . . . . CA Common Services . . . . . . . . . . . . . CA-Datacom/AD Worksheets . . . . . . . . . Installation JCL PROCedure Parameters
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
31 31 33 36 37 38 39 39 40 41 41 42 43 43 43 44 45 45 46 46 46 47 47 48 49 49 49 50 50 50 51 52 53 53 53 53 53 53 54 54 54 54 55 55 59 60 61 61
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
vi Planning and Implementation Guide
Data Set Naming Checklist Items . . . . . . . . . . . . . . . . . . DASD and Tape Volume Names and Unit Types Checklist Items SVC and LXX/FXX Checklist Items . . . . . . . . . . . . . . . . . CA Common Services Checklist Items . . . . . . . . . . . . . . . COBOL Compiles Checklist Items . . . . . . . . . . . . . . . . . . Assembler and Link-Edits Checklist Items . . . . . . . . . . . . . CICS Usage Checklist Items . . . . . . . . . . . . . . . . . . . . . XCF Usage Checklist Items . . . . . . . . . . . . . . . . . . . . . Unicenter CA-Jobtrac Worksheets . . . . . . . . . . . . . . . . . . . . . SAMPJCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Unicenter CA-Jobtrac Tape Install . . . . . . . . . . . . . . . . . . . Unicenter CA-Jobtrac Customization STAGE1 Parameters . . . . JOB Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database IDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Database Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . CA-Datacom/AD File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sysout Capture Upgrading from r3.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . CPM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . CA Common Services and CA-GSS Unicenter CA-11 . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61 61 63 64 64 65 65 66 67 67 68 70 72 74 75 76 77 77 78 78 79 81 82 83 85 85 85 86 87 88 89 90 91 91 92 92 93 94 94 95 95 96 96 97 97 98 98 98
Chapter 4. Installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . Install CA Common Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install CA-Datacom/AD Preparing for Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading Existing Products . . . . . . . . . . . . . . . . . . . . . . . . . SAMPJCL Member Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . Installation Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Steps for All Installations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Allocate the SAMPJCL Library . . . . . . . . . . . . . . . . . . . Sample JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Download Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . Step 3. Rename SMP/E DDDEFs . . . . . . . . . . . . . . . . . . . . . . Step 4. Prepare the CA-Datacom/AD Custom Assemblies . . . . . . . . Step 5. Load CA-Datacom/AD SVC Using CAIRIM . . . . . . . . . . . . New Installation Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Add BACKUP/LOAD/INIT PROC Members . . . . . . . . . . . . Step 2. Allocate CA-Datacom/AD Data Sets . . . . . . . . . . . . . . . . Step 3. Initialize and Load the CXX, LXX, and Databases . . . . . . . . Step 4. Start the MUF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 5. Run DDUPDATE, DDCFBLD, DBUTLTY INIT, and Populate DQ Step 6. Back Up CA-Datacom/AD Databases . . . . . . . . . . . . . . . Step 7. Shut Down the MUF . . . . . . . . . . . . . . . . . . . . . . . . . Step 8. Remove Unneeded Installation Files . . . . . . . . . . . . . . . Demonstration Phase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1. Start Up the MUF . . . . . . . . . . . . . . . . . . . . . . . . . . Step 2. Execute Sample CA-Datacom/AD Programs . . . . . . . . . . .
Contents vii
Step 3. Execute Sample Dynamic SQL Programs . . . . . Step 4. Shut Down the MUF . . . . . . . . . . . . . . . . . . Post Installation Considerations . . . . . . . . . . . . . . . . . . Set up Production Jobs . . . . . . . . . . . . . . . . . . . . . Multi-User Facility Tuning . . . . . . . . . . . . . . . . . . . . Run the MUF as a Started Task . . . . . . . . . . . . . . . . Install Unicenter CA-Jobtrac . . . . . . . . . . . . . . . . . . . . Step 1: Allocate and Load the SAMPJCL Library . . . . . . Step 2: Unload 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 . . . . . . . . . . . . Step 7: Perform APPLY Processing . . . . . . . . . . . . . . Step 8: Perform ACCEPT Processing . . . . . . . . . . . . Step 9: Ensure APF Authorization . . . . . . . . . . . . . . . Step 10: Update License Management Program (LMP) Key Step 11: Update CAIENF Database . . . . . . . . . . . . . . Step 12: CAIENF Startup Options . . . . . . . . . . . . . . . Step 13: Start CAIENF . . . . . . . . . . . . . . . . . . . . . Step 14: Create a Dummy IEAVMXIT Exit . . . . . . . . . . Step 15: (Optional) Install eTrust CA-Examine Interface . . Step 16: (Optional) Link AllFusion CA-Panvalet Modules . Step 17: (Optional) Link AllFusion CA-Librarian Modules . Step 18: (Optional) Install Critical Path Monitor (CPM) . . . Step 19: (Optional) Install the @JOBTRAC USS Command Step 20: (Optional) Install the JES2 Hold Usermod . . . . . Chapter 5. Customization Job Streams . . . . . . . . . . . . . . . . . . . . STAGE1 Customization Job Run the STAGE1 Job . . . . . . . . . . . . . . . . Required TRACMAC Parameters . . . . . . . . . Optional TRACMAC Parameters . . . . . . . . . STAGE2 Installation Job Stream . . . . . . . . . . . . Run the STAGE2 Job . . . . . . . . . . . . . . . . Types of Data Sets Supported . . . . . . . . . . . Allocate Data Sets . . . . . . . . . . . . . . . . . . Description of the Unicenter CA-Jobtrac Database About the Sysout Capture File . . . . . . . . . . . Description of TRACMDS . . . . . . . . . . . . . Recommended Initial Data Set Sizes . . . . . . Update Procedure Libraries . . . . . . . . . . . . Use JOBTRAnn to Set Global Options . . . . . . New Options in Version . . . . . . . . . . . . . . Global Options in the STAGE2 Job Stream . . Location of JOBTRAnn . . . . . . . . . . . . . . Using Multiple JOBTRAnn Members . . . . . . The JOBTRAnn Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AMRLCNT
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
98 98 99 99 100 100 101 101 102 102 103 103 104 104 105 105 105 106 106 106 106 106 107 107 108 109 109 111 112 112 113 116 118 119 119 120 122 123 124 124 126 127 127 127 128 128 129 129
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
viii Planning and Implementation Guide
ARCBLK . . . . . . ARCDSN . . . . . ARCDSP . . . . . ARCRTN . . . . . . . . . . ARCUNT ARM . . . . . . . . AUNIT . . . . . . . AUTOC . . . . . . AUTOQ . . . . . . CAPDMPS . . . . CMDLIB . . . . . . CPM . . . . . . . . CPMAPPL . . . . . DATELIB . . . . . DBID . . . . . . . . DEFAULT0 . . . . DFSQUAL . . . . . DISABLE . . . . . DRDR . . . . . . . . . . . DUMPUJV E@DOMAIN . . . ECLLATE . . . . . ECLNODES . . . . ECLWTO . . . . . EMAILFROM . . . EMAILSRV . . . . EREPORT . . . . EXECTRLR . . . . FCSTDBID . . . . INSERTRMS . . . JCLTABL . . . . . JESCMD . . . . . JMFTABLE . . . . LIBPGM . . . . . . PRIORITY . . . . . RAMAXCC . . . . REMTCRED . . . REPORT . . . . . RERUN . . . . . . RESTAGEABEND RESTAGECAT . . RESTAGECC . . . RESTAGEJCLERR SCHENV . . . . . SCLMAX# . . . . . STATINTV . . . . SUBROOT . . . . SVQUAL . . . . . . SYNCSYS1 . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
129 130 130 130 131 131 133 133 134 134 135 136 136 137 137 138 138 139 139 140 140 141 141 142 142 143 143 144 144 145 146 146 147 147 148 148 149 149 150 150 151 151 151 152 152 153 153 153 154
Contents ix
SYNCSYS2 . SYNCSYS3 . SYNCTOL . . SYSDBID . . TNDOVLP . . TSCMDSPA . TSDSNSPA . TSMSGSPA . TSPGFSPA . WLMRSRC . XPLATRERUN
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
154 154 155 155 156 156 157 157 158 158 159 161 162 162 164 165 165 166 167 167 168 168 169 170 171 174 175 176 180 184 186 195 199 201 202 203 204 205 208 209 214 215 218 220 226 228 229 230
Chapter 6. Customization Tasks . . . . . . . . . . . . . . . . Modify CA-Datacom/AD for Unicenter CA-Jobtrac . . . . . . . . Startup Keywords for CUSMAC(DBDATIN1) . . . . . . . . . DBSIDPR Parameters . . . . . . . . . . . . . . . . . . . . . . Alter the CA-Datacom/AD LXX and FXX . . . . . . . . . . . . . LXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FXX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modify CA-GSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . Step 1: Modify JCL . . . . . . . . . . . . . . . . . . . . . . . Step 2: Modify CA-GSS Parameters . . . . . . . . . . . . . Parameters You Need to Modify . . . . . . . . . . . . . . . Step 3: Activate GoalNet . . . . . . . . . . . . . . . . . . . . Step 4: (Optional) Install REXX IMOD Sample Source . . . Customize SYS1.PARMLIB . . . . . . . . . . . . . . . . . . . . . Set Up Default Authorization . . . . . . . . . . . . . . . . . . . . Set Up the JES3 Held Job Class . . . . . . . . . . . . . . . . . . Define Location Information (DYNAMLOC) and Initiation IMODs . . . . . . . . . . . . . Update Your TSO Procedures or CLIST Set 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 . . . . . . . . . . . . . . . . . . . Maintain Table Modules . . . . . . . . . . . . . . . . . . . . . . . Set Up AMR Support . . . . . . . . . . . . . . . . . . . . . . . . Create IPLTABLE Entries (Optional) . . . . . . . . . . . . . . . . Enable the SPACE Command . . . . . . . . . . . . . . . . . . . Integration with Unicenter CA-11 . . . . . . . . . . . . . . . . . . Set Up CA-JCLTrac . . . . . . . . . . . . . . . . . . . . . . . . . Set Up a UCT . . . . . . . . . . . . . . . . . . . . . . . . . . Create the DB2 Objects . . . . . . . . . . . . . . . . . . . . Bind the DB2 Plans . . . . . . . . . . . . . . . . . . . . . . . Grant Authority . . . . . . . . . . . . . . . . . . . . . . . . . . Use Other Sysout Capture Products . . . . . . . . . . . . . . . .
x Planning and Implementation Guide
Cross-Platform Scheduling . . . . . . . . . . . . . . . . . . . . . . . . . . CA-GSS Server IMODs . . . . . . . . . . . . . . . . . . . . . . . . . . Global Variables for Cross-Platform Scheduling . . . . . . . . . . . . Server IMOD Selection Globals . . . . . . . . . . . . . . . . . . . . Status Tracking Server Globals (Service $UNITRKJT) . . . . . . . Command Driver Globals (Service $UNIRCVJT) . . . . . . . . . . Cross-Platform Server Globals (Service $UNIXPSJT) . . . . . . . Cross-Platform Server ($UNIXPSJT) Password Requirements Table Syntax Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Keywords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alter the Event Console Logging Message Options . . . . . . . . . . . . Update the GJTREMSG Source . . . . . . . . . . . . . . . . . . . . . Chapter 7. Startup and Verification . Initialization and Startup . . . . . . . . . Initialize Internals . . . . . . . . . . Start the Unicenter CA-Jobtrac Task Access Unicenter CA-Jobtrac . . . End the Unicenter CA-Jobtrac Task Verification . . . . . . . . . . . . . . . . . Contents of IVP . . . . . . . . . . .
. . . . . . . . . . . . .
232 235 236 236 236 238 239 241 241 242 243 244 245 247 251 252 252 253 253 253 254 254 259 259 259 260 260 260 260 261 261 261 262 262 263 264 264 264 265 266 268 271 272 273 274 275
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Chapter 8. Upgrading, Testing, Running Multiple Copies General Procedure . . . . . . . . . . . . . . . . . . . . . Memory Requirements . . . . . . . . . . . . . . . . . . . Release Compatibilities and Incompatibilities . . . . . . . . . Compatibilities . . . . . . . . . . . . . . . . . . . . . . . . Incompatibilities . . . . . . . . . . . . . . . . . . . . . . . r11 Features . . . . . . . . . . . . . . . . . . . . . . . . . Conversion Notes . . . . . . . . . . . . . . . . . . . . . . . . Checkpoint and History . . . . . . . . . . . . . . . . . . . Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . PDS Data Sets . . . . . . . . . . . . . . . . . . . . . . . . TRACAUTH . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Your Production from r3.5 to r11 . . . . . . . . . . Return to the Prior Release . . . . . . . . . . . . . . . . . . . Return to r3.5 . . . . . . . . . . . . . . . . . . . . . . . . Reverse Conversion (Optional) . . . . . . . . . . . . . . Run r3.5 Production and r11 Test System . . . . . . . . . . Run Multiple STCs on Same CPU . . . . . . . . . . . . . . . Run in a Shared Sysplex Environment . . . . . . . . . . . . Appendix A. NJE Support Installation and Setup . . . Job Submission . . . . . . . Job Execution . . . . . . . . . . . . . . Job Termination
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents xi
ISPF Interface . . . . . . . . . . . . . . Batch Archiving and JTEZRPT . . . . REXX Stack Information for NJE Jobs Keywords . . . . . . . . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
276 277 278 278 279 280 281 283
Appendix B. Connecting Systems for Cross-Platform Scheduling z/OS CAICCI Installation and Considerations . . . . . . . . . . . . . . . Remote Scheduler Installation and Considerations . . . . . . . . . . . Index
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
xii Planning and Implementation Guide
Chapter 1. Welcome
This section contains the following topics: CA-Datacom/AD . . Features and Benefits
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2 3
This guide describes how to install the CA proprietary software product, Unicenter CA-Jobtrac r11. This guide is written for systems software programmers and personnel responsible for the installation, implementation, and maintenance of Unicenter CA-Jobtrac. This guide includes the CA-Datacom/AD installation steps to provide a more focused and simplified installation for Unicenter CA-Jobtrac customers. The CA-Datacom/AD Installation and Maintenance Guide is also included in the documentation set and contains more information.
Chapter 1. Welcome 1
CA-Datacom/AD
CA-Datacom/AD
Unicenter CA-Jobtrac uses Advantage CA-Datacom/DB as its database. Advantage CA-Datacom/DB is a fast database engine that allows for forward recovery, data integrity after a system outage, backup-while-open, and more. CA-Datacom/AD is identical in every way to Advantage CA-Datacom/DB, except that you cannot create your own databases in CA-Datacom/AD. Otherwise, the operation and use of both CA-Datacom/AD and Advantage CA-Datacom/DB are the same. To avoid confusion, all references in the guides are to CA-Datacom/AD.
2 Planning and Implementation Guide
Features and Benefits

The Unicenter CA-Jobtrac primary function is to automate production scheduling. Unicenter CA-Jobtrac schedules, submits, tracks, and records events at the proper time, in exact sequence, the first and every time, with little or no manual intervention. Unicenter CA-Jobtrac creates schedules in two ways: 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 Unicenter CA-Jobtrac production scheduling component: Total automation of event scheduling. Once an event is defined to the system, no further action is required to schedule that event or set of events. Dependency scheduling. Unicenter CA-Jobtrac schedules and submits events based on dependencies you define for each event. Scheduling dependencies determine if and when a given event is scheduled (for example, on the last workday of each month). Execution dependencies determine when a scheduled event is submitted (for example, after a specified data set is created). No complex calendar definitions. Scheduling parameters define the cycles, frequencies, and dependencies for each event in a logical, straightforward approach. Unlike schedulers that require you to build a daily processing calendar for every day of the year, Unicenter CA-Jobtrac builds a dynamic calendar each workday to process scheduled events. Threshold scheduling. Unicenter CA-Jobtrac lets you set start, target, and abort times so that events execute at peak efficiency, without rigid time schedules.
Mass schedule alterations. You can issue a single command to make sweeping adjustments to the current schedule. You can adjust submission times forward or backward up to 24 hours for a specific event or all scheduled events. Automatic JCL submission and event tracking. Once an event is scheduled, it is automatically submitted when all dependencies are satisfied. The event is then tracked through completion. Unicenter CA-Jobtrac also supports automatic JCL alteration in the form of overrides or date statements. On-demand event submission. Unicenter CA-Jobtrac accommodates the dynamic realities of production control. Using Unicenter CA-Jobtrac, you can quickly and easily add on-demand events to the schedule for Unicenter CA-Jobtrac processing. Data set triggering. You can specify that the creation or update of a data set triggers some event, such as event submission. Distributed and decentralized scheduling. You can have one person per group take care of their scheduling needs (up to 254 separate locations), or you can have one person take care of the scheduling needs of all groups. Tape volume pull lists. Unicenter CA-Jobtrac indicates the tape volumes needed for production during the processing day. Production control tools. Unicenter CA-Jobtrac provides an array of online inquiries, error-checking and reporting capabilities, and status reports. Included are online event documentation, event history analysis, DASD space analysis, schedule forecasting, and online or printed reports.
Email
Unicenter CA-Jobtrac can send form emails to a specified list of addresses based on the normal or abnormal completion of a job. This feature allows multiple addresses to be specified. You can use template emails to provide additional text to include in your email. Standard email text is also included to provide the job name, business group, version, and other job-related information.
Unicenter Service Desk

Unicenter Service Desk provides two kinds of alerts. The first reports failures that occur in an event (also called jobs) that is scheduled and monitored by Unicenter CA-Jobtrac such as job abends. The second reports conditions within the Unicenter CA-Jobtrac product itself that need to be reported such as file full conditions.
REXX
Unicenter CA-Jobtrac takes full advantage of CA implementation of REXX. You can schedule REXX IMODs (Intelligent Modules) just as you have always done for events, and you can use REXX IMODs as scheduling dependencies. Using IMODs as dependencies adds unlimited power to Unicenter CA-Jobtrac by giving you complete flexibility in deciding when to schedule an event. To increase this power even more, @JOBTRAC was created. @JOBTRAC gives you the ability to obtain information about the current schedule and to change the current schedule using an IMOD. @JOBTRAC uses CA-GSS (Global SubSystem). CA-GSS interacts with other CA products, giving you the ability to obtain information from even more sources and to provide Unicenter CA-Jobtrac information to them.
Automatic Message Recognition

The Unicenter CA-Jobtrac AMR (Automatic Message Recognition) facility enables you to monitor system messages and prompts and to respond to them automatically. For example, you can do the following: 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

Unicenter CA-Jobtrac can issue any z/OS, JES, VTAM, or task modify (F) command automatically at scheduled times or at specific intervals. Even IPLs can be automated.
Specifying Additional Condition Codes

Unicenter CA-Jobtrac gives you ways to impose condition code processing on a program, job, job step, or procstep. Condition code processing checks for specified condition codes being returned. If the condition code you define is violated, Unicenter CA-Jobtrac imposes a dependency requiring you to check the event's output before successor events can be submitted.
JCL Management
Unicenter CA-Jobtrac offers various features that enhance JCL usage. These features are: AJO (Automatic JCL Override) automatically deletes or inserts specified JCL statements when an event is submitted by Unicenter CA-Jobtrac. JMF (JCL Management Facility) enables you to: Make global variable changes to JCL. Insert parameter statements or values into JCL. Provide date values based on the original schedule date or 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.
ADI (Automatic Date Insertion) can direct Unicenter CA-Jobtrac to automatically insert JCL dates and repeated records in your events, and you can specify that Unicenter CA-Jobtrac automatically calculate and insert dates in the record. 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. You can then generate reports with the stored information. Additionally, CA-JCLTrac can forecast what your JCL will look like on any given day.
Sysout Archival
Unicenter CA-Jobtrac automatically captures and archives specified sysout listings, providing online access to recent sysouts and permanent archival to tape. Additionally, Unicenter CA-Jobtrac interfaces with Unicenter CA-View, a sysout archival and retrieval tool.
Other Benefits
Other important benefits include the following: No IPLs are required for scheduler operation for most environments. No dedicated hardware is required. Unicenter CA-Jobtrac uses standard PDS files providing simplified schedule definition. Interval processing to submit an event multiple times during a processing period.
Chapter 2. Overview of Components and Installation

This section contains the following topics: Concepts . . . . . . . . . . . . . . . Pre-Installation Considerations . . . CA-Datacom/AD Considerations . . Unicenter CA-Jobtrac Considerations
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8 24 31 41
Chapter 2. Overview of Components and Installation 7
Concepts
Concepts
The following topics introduce Unicenter CA-Jobtrac locations, data sets, and libraries.
Locations
To effectively install and use Unicenter CA-Jobtrac, you need to understand Unicenter CA-Jobtrac locations. A location groups Unicenter CA-Jobtrac entities and provides distributed control over production. There are two types of locations: Physical, such as New York and Chicago Logical, such as accounting department and shipping department
The following Unicenter CA-Jobtrac entities have a location associated with them: Libraries Users Holiday calendars Cyclic calendars Workdays Schedules Events
Locations are defined by a location ID. The location ID is a three-digit code used by Unicenter CA-Jobtrac to determine the following: Which calendars, workdays, and libraries an event uses. What functions a user can perform.
For example, if schedule PAYROLL1 has location 004 associated with it, it can only access calendars, workdays, and libraries associated with location 004. As another example, if Susan has only location 010 associated with her ID with delete and add functions allowed, she can only delete an event with location 010 associated with it. Users can have multiple location IDs associated with them. All other entities in Unicenter CA-Jobtrac are associated with one location ID only. Location 000 has a significant meaning in Unicenter CA-Jobtrac. The following explains its significance:
Concepts
In general, the default location is 000 (zero). This default is overridden by the following: The JOBTRAnn option DEFAULT0 is set to NO rather than YES. If DEFAULT0 is set to NO, no default location ID is assumed. A user has specified a default location using the PROFile command.
The 0ARCHIVE, 0SYSARCH, and 0JOBARCH tasks always have location 000 associated with them.
Users have what is known as a default location. The default location ID is assigned by the user using the PROFile command. For a user, if a location ID is not specified for an activity, the user will use their default location ID. For example, Bob has location 226, 040, and 111 associated with him. He has assigned location 226 as his default location ID. He adds an event to the current schedule, without specifying a location ID for the event. It is added with a location ID of 226, because that is Bob's default location. Assigning Location IDs: Location IDs are assigned to an entity as described in the following table: Entity Holiday calendars Cyclic calendars How a location ID is assigned Holiday calendar definitions include a location ID. Holiday calendars are defined to Unicenter CA-Jobtrac using the Holiday Calendars panel. Cyclic calendar definitions include a location ID. Cyclic calendars are defined to Unicenter CA-Jobtrac using the Cyclic Calendars panel. The last three digits of a library's ddname determine the location ID for everything in the library. For example, TRACT002 specifies a temporary-use JCL library for location 002. A user is assigned one or more location IDs using the TRACAUTH table. A user can have temporary location IDs assigned using the Authorization Profile panel. A user assigns a default location ID using the PROFile command. Workdays Workdays are associated with a location ID according to the schedule they are used in. By default, the workdays have the same location ID as the schedule. Within a schedule, you can change the location ID for workdays.
Library's ddname
User
Concepts
Entity Schedules
How a location ID is assigned A schedule's location ID is assigned by the library in which the schedule member resides. For example, if the member is in the SCL library named TRACS003, the schedule's location ID is 003. All events in the schedule have location ID 003 assigned by default. Within a schedule, you can change the location ID for events.
Events
Location IDs are assigned to events when they are placed on the current schedule. If an event is automatically added by a schedule, the schedule assigns the location ID. If an event is manually added, you assign the location ID.
Concepts
CA-Datacom/AD DASD
Total disk space requirements depend on your product mix. The following table indicates the estimated blocks of DASD space required for new installation. The column heading Volume refers to the VOLSER given in the CA-Datacom/AD installation worksheet. The column heading Tracks refers to the number of tracks used with DASD type 3390. Total tracks by volume needed for new installs: Volume DASD01 DASD02 DASD03 DASD04 DASD05 DASD06 DASD07 DASD08 Total Tracks 950 500 1090 2658 305 456 1837 1045 8841
For more information about the files allocated in this space, see the CA-Datacom/AD Installation and Maintenance Guide. In most cases, you do not need this information to complete the installation.
Concepts
Unicenter CA-Jobtrac DASD

Unicenter CA-Jobtrac uses a number of data sets that store working data.
Checkpoint Database
Beginning with r11, most of the operational data resides in a database. This includes the data that was stored in both the checkpoint file and the history file in previous releases. CA-Datacom/AD is a common component database that is included with Unicenter CA-Jobtrac r11 at no additional charge. CA-Datacom/AD is distributed on a separate tape. The installation steps are included in Install CA-Datacom/AD on page 83. Unicenter CA-Jobtrac defines two databases to CA-Datacom/AD: production and forecast. Unicenter CA-Jobtrac is assigned databases 161 and 162 as defaults. The production database is used for all the normal processing of Unicenter CA-Jobtrac while running production scheduling. The forecast database is used for loading schedules outside production and for forecast reporting. Unicenter CA-Jobtrac allocates and initializes the following production database files during installation: Type DB index Event data DDname in CA-Datacom/AD IXX161 EVT161 Contents Keys and indexes in the database. Current schedule event data for production. The current schedule is the active schedule. It is dynamic, and changing as events are submitted, tracked, completed, and moved to archives. Loading a schedule adds events to the current schedule. Archive marks the events as archived, removing them from the active view. Running a batch utility removes archived jobs. System options, holiday and cyclic calendars, and table services information. Audit, IPL, and event summary information. Staging tables used during event add processing.
Options and tables
OPT161
History information Event staging
HIS161 STG161
Concepts
Unicenter CA-Jobtrac allocates and initializes the following forecast database files during installation: Type DB index DDname in CA-Datacom/AD IXX162 Contents Used by CA-Datacom/AD to maintain keys and indexes in the database. Forecast schedule event data. Copy of production system options, holiday and cyclic calendars, and table services information used by forecast. Copy of event summary information. Staging tables used during forecast event add processing.
Event data Options and tables
EVT162 OPT162
History information Event staging
HIS162 STG162
Capture File Data Set

The capture file is stores the output from schedule loads and to archive SYSOUT data from Unicenter CA-Jobtrac jobs. The DD naming convention is: CAPTURE (CAPTURE is the default.)
Setup Files
The Unicenter CA-Jobtrac setup files contain global information used by Unicenter CA-Jobtrac while it is processing. The DD naming convention for files in the PPOPTION data set is: TRACPARM (TRACPARM is the default.)
Concepts
Calculate Database Size

The Unicenter CA-Jobtrac checkpoint and history data is maintained in a CA-Datacom/AD database. The physical files that make up a database are called data areas. Each data area contains a set of tables. For the Unicenter CA-Jobtrac database, four data areas are used. EVTdbid Includes the events data for both the current checkpoint and archived history. OPTdbid Includes the options, calendars, and tables (JTS and internal) used by Unicenter CA-Jobtrac. HISdbid Includes the statistics, audit, and IPL records. STGdbid Includes the staging tables for schedule and event load processing. Due the number of factors that can affect the database size, a spreadsheet is available to help you estimate the database size. The spreadsheet is available for download from the Unicenter CA-Jobtrac Product Home Page on the CA SupportConnect website or can be received through an email by contacting Unicenter CA-Jobtrac Technical Support.
Concepts
Differentiate Copies of Unicenter CA-Jobtrac

One or more TRACPARM libraries can be defined for all the copies of Unicenter CA-Jobtrac running on a system. The correct library to use is specified on the TRACPARM DD statement in the Unicenter CA-Jobtrac started task procedure. The following are members in the TRACPARM library: JOBTRAnn (JOBTRA00 is the default.) The JOBTRAnn member describes the environment in which Unicenter CA-Jobtrac operates and customizes how Unicenter CA-Jobtrac functions. Multiple JOBTRAnn members can be defined. You can use each of these members to test a different configuration of options, or to run multiple copies of Unicenter CA-Jobtrac. To activate the options in a given JOBTRAnn member, issue the following modify command, where nn matches nn in the desired JOBTRAnn member: F taskname,OPTS=nn RESOURCE (RESOURCE is the default.) The RESOURCE member contains resource definitions you can assign to events as dependencies. TRAC310W is issued if no RESOURCE file is available. Unicenter CA-Jobtrac continues processing. Within the PPOPTION library, one RESOURCE member is defined for all copies of Unicenter CA-Jobtrac running on a system. EXCLPARM (EXCLPARM is the default.) The EXCLPARM member defines mutually exclusive events. Within the PPOPTION library, one EXCLPARM member is defined for all copies of Unicenter CA-Jobtrac running on a system.
Concepts
CA-Datacom Sharing
Unicenter CA-Jobtrac r11 introduces the use of a relational database for checkpoint and history data. CA-Datacom/AD, a common component version of Advantage CA-Datacom/DB, is distributed with CA products. CA-Datacom/AD use is limited to only those databases used by CA products and cannot be used to create non-product databases. As a common component, CA-Datacom/AD is included with Unicenter CA-Jobtrac r11 at no additional cost. This section introduces some CA-Datacom concepts and database sharing options that you should consider in your installation planning.
CA-Datacom/AD Sharing Overview

The CA-Datacom/AD database achieves its high performance by caching data to limit the I/O performed. In a sysplex sharing a database, only one CA-Datacom/AD Multi-User Facility (MUF) is active on one system of the sysplex to support all the systems. The database is accessible to all the sysplex systems. Applications such as Unicenter CA-Jobtrac use the CA-Datacom interface to access the database. This interface locates the database and uses the appropriate facility to transfer the database data to the application. Unicenter CA-Jobtrac does not need to know where the database is located.
Database Access Options

CA-Datacom/AD provides the following access options. The fastest access to a CA-Datacom/AD database is through the product SVC. This can only be used if you are running Unicenter CA-Jobtrac on the same system image as the CA-Datacom/AD Multi-User Facility (MUF). Even if another access option is used to share the database, the CA-Datacom/AD SVC is required. On the system running the MUF, the SVC is used for access. If you do not need to share the Unicenter CA-Jobtrac database, this method is all that is needed. If you plan to run Unicenter CA-Jobtrac in a sysplex with a primary submission system and monitors to track the jobs in a shared JES spool environment, additional access options are required. Almost as fast as the SVC is XCF, IBM's Cross-System Coupling Facility. It should be noted that this facility is a sysplex service and does not require a coupling facility. XCF is the best way to share the Unicenter CA-Jobtrac database. XCF is fast, easy to configure in CA-Datacom/AD, and provides an easy way to disconnect and reconnect from Unicenter CA-Jobtrac if the MUF needs to be moved or a failure on the MUF system occurs. XCF requires that all systems that share the database using XCF must be in the same sysplex.
Concepts
In addition to the preceding access options, CA-Datacom/AD supports two other options: Network access using CAICCI. CAICCI uses VTAM or TCP/IP to communicate between systems not connected in a sysplex. This is much slower than XCF and is generally not needed since Unicenter CA-Jobtrac supports access to other non-sysplexed systems through its NJE support. Data sharing through a coupling facility. In a sysplex that shares a coupling facility, data access and updates can be performed directly to the database from multiple systems, using the coupling facility to coordinate database changes. This facility is considerably more complicated to set up and maintain than XCF and adds very little benefit for the increased overhead and operational complexity. We do not recommend using either of these options with Unicenter CA-Jobtrac. CA-Datacom uses the fastest connection available when connecting to the database, which is determined by the following conditions: If the CA-Datacom/AD MUF is on the same LPAR, the SVC is used. If the SVC cannot be used, XCF is defined and the MUF is available on an XCF connected LPAR, the XCF connection is used. If neither of the previous methods is available and CAICCI is defined, CAICCI is used.
This connection method lets you define all the protocols that are used to access a CA-Datacom/AD MUF once in the CA-Datacom/AD system identification module, DBSIDPR, and use that same module in all the systems that are sharing the MUF, no matter what method is used for access. Even though the CA-Datacom/AD SVC cannot be used to access the database, it must be installed on each system that will run Unicenter CA-Jobtrac.
Concepts
Configuration Examples
Single System (Non-Shared): A single system, non-sysplex, has one CA-Datacom/AD MUF and one Unicenter CA-Jobtrac.
All Unicenter CA-Jobtrac components, the Unicenter CA-Jobtrac started task (STC), @JOBTRAC interface from CA-GSS, and the ISPF interface connect to the CA-Datacom/AD Multi-User Facility using the CA-Datacom SVC. The MUF owns the physical files (Unicenter CA-Jobtrac DB) and caches the data to improved performance. In this configuration, the database is not shared with other systems, and all access occurs on the same LPAR through the CA-Datacom SVC.
Concepts
Sysplex System (Shared): In a sysplex, multiple systems share a JES and a Unicenter CA-Jobtrac environment. Each LPAR in the sysplex has a Unicenter CA-Jobtrac started task (STC), a CA-GSS STC, and possibly one or more TSO users. The CA-Datacom MUF STC is only on one of the LPARS and is shared.
Local Unicenter CA-Jobtrac components, the Unicenter CA-Jobtrac started task (STC), @JOBTRAC interface from CA-GSS, and the ISPF interface connect to the CA-Datacom/AD Multi-User Facility using the CA-Datacom SVC. On systems without the MUF, these components are connected to the MUF using XCF. As with the single system, the MUF owns the physical files (Unicenter CA-Jobtrac DB) and caches the data to improved performance. The Unicenter CA-Jobtrac Primary submission system, indicated by (P), is shown on the same system as the MUF and the Unicenter CA-Jobtrac Monitors, indicated by (M), on the XCF connected systems. Since the primary Unicenter CA-Jobtrac accesses the database more than the monitors, running the primary where the database can be accessed with the SVC provides the best performance. In most cases, if the primary Unicenter CA-Jobtrac was on one of the XCF connected systems, XCF is fast enough that there would not be a noticeable degradation to the Unicenter CA-Jobtrac processing.
Concepts
Shadow MUF Failover Recovery: Starting with CA-Datacom/AD r11, a new facility was introduced to improve recovery in the event of a MUF or system failure. The Shadow MUF facility runs a special Shadow MUF on another system in the sysplex. The Shadow MUF connects to the primary MUF through XCF and does preliminary open processing for the databases that are on shared DASD between the systems. Once open processing is complete, the Shadow monitors the processing of the primary to detect a failure. In most cases, a failure can be positively detected, and the Shadow automatically assumes control. The Unicenter CA-Jobtrac Suspend and Resume processing is designed to work with the Shadow MUF to detect a failure and to reconnect automatically to the new Primary with minimal delay. The Shadow MUF implementation is not discussed in the Unicenter CA-Jobtrac documentation. CA-Datacom/AD recommends that you implement CA-Datacom/AD XCF sharing before introducing the Shadow MUF into your environment. Note: For more information on the Shadow MUF configuration, see CA-Datacom/AD Shadow MUF white paper at ca.com/datacom (click on the White Papers link). or contact CA-Datacom/AD Support for details.
Concepts
Suspend and Resume: In the sysplex example, with only one MUF shared between several systems, there is the possibility that the MUF could become unavailable due to a planned or unplanned MUF or system outage. To reduce the impact of a MUF outage, Unicenter CA-Jobtrac has SUSPEND and RESUME processing that will hold all of Unicenter CA-Jobtrac processing until the MUF is available again. Suspending Unicenter CA-Jobtrac can occur in the following ways. The SUSPEND operator command is issued. In this case, you have chosen to suspend Unicenter CA-Jobtrac manually. Unicenter CA-Jobtrac remains suspended until a RESUME command is entered. You can choose to use this method in the event that you are planning to move the CA-Datacom/AD MUF and want to control the process manually. If you are running monitor systems, you must enter the SUSPEND command (and RESUME) for each Monitor Unicenter CA-Jobtrac, as well as the primary Unicenter CA-Jobtrac. EOJ the CA-Datacom/AD MUF. If you issue the command to shut down the MUF, Unicenter CA-Jobtrac detects that the MUF is shutting down and automatically suspends. Both the Primary and Monitor systems detect this. CA-Datacom/AD continues processing requests until all accessors have closed their connection, and then shuts down. TSO users of Unicenter CA-Jobtrac need to press Enter or exit the Unicenter CA-Jobtrac CLIST to free their connection to the database. Following the suspend, Unicenter CA-Jobtrac enters auto resume processing to retry to connect to the database. The EOJ'ed CA-Datacom/AD refuses any connection, so that the resume does not connect to CA-Datacom/AD until the MUF has been restarted, or the Shadow MUF assumes control. MUF or System Failure. If a failure occurs, Unicenter CA-Jobtrac detects the failure and begins auto suspend. Unicenter CA-Jobtrac then enters auto resume processing to retry connecting to the database. Once the MUF is available or the Shadow MUF assumes control, Unicenter CA-Jobtrac reconnects and continues processing.
All processing that is in progress when Unicenter CA-Jobtrac is suspended continues processing from the same point when processing is resumed. Interactive processing, such as ISPF or operator commands, is not suspended. These commands receive a message that the Unicenter CA-Jobtrac is suspended.
Concepts
Libraries
Unicenter CA-Jobtrac uses a number of PDS-type libraries to store production JCL, schedules, job documentation, date and JCL variables, and temporary-use JCL. Each library is associated with a location. In this way, you can provide distributed control over production. The following libraries are used in Unicenter CA-Jobtrac. The last three digits (nnn) of a library's ddname correspond to a location ID. All members in the library are associated with that location ID by default. For example, TRACT002 specifies a temporary-use JCL library for location 002. Type Date file DD Naming Convention DATELIB Contents Each library contains a JMFSYM01 and a PRODDATE member (default member names). The JMFSYM01 member contains JMF variable definitions. The PRODDATE member contains ADI definitions. Each member contains the following for an event: Email Template TRACMnnn (TRACM000 is the default.) TRACJnnn (TRACJ000 is the default.) TRACRnnn (TRACR000 is the default.) Information about an event you want the operator to have. Manual actions the operator is to perform.
Documentation
TRACDnnn (TRACD000 is the default.)
Each member contains an email template used when a notification email is sent. Each member contains the production JCL that is run for scheduled events. Each member contains encrypted user ID and password information for events that are to be submitted to a scheduler or an agent on a remote platform. Each member contains a schedule control language data set.
JCL
Remote Password
SCL
TRACSnnn (TRACS000 is the default.)
Concepts
Type Temporary-use JCL
DD Naming Convention TRACTnnn (TRACT000 is the default.)
Contents When you want to temporarily modify JCL before running it, a copy of the production JCL is made and put in a temporary-use JCL library member. The event then uses the JCL from the temporary-use library rather than the JCL library.
Pre-Installation Considerations
Before starting the installation procedure, you should do the following: Read the installation documentation. Consider any known installation issues. Complete pre-installation worklists to plan data set names, volumes, and other installation-specific information.
Requirements
The following sections describe the hardware and software required for successful Unicenter CA-Jobtrac operation. Unicenter CA-Jobtrac is supported on any IBM supported or IBM-compatible mainframe computer capable of supporting unmodified releases of the indicated operating systems. Unicenter CA-Jobtrac is supported under any IBM supported operating systems and ISPF. Unicenter CA-Jobtrac uses standard IBM interfaces to accomplish scheduling, sysout capture, and all other functions. There are no hooks, zaps to IBM code, or other nonstandard interactions with your operating system. Unicenter CA-Jobtrac supports all devices supported by unmodified releases of the supported operating systems.
The following table describes the memory requirements for Unicenter CA-Jobtrac: Component Internals and exits 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 ECSA Usage 100 KB 30 KB 140 KB 380 KB 20 KB 57 KB 27 KB CSA Usage 60 KB ------Total 160 KB 30 KB 140 KB 380 KB 20 KB 57 KB 27 KB
The following table summarizes the memory requirements for Unicenter CA-Jobtrac: ECSA Usage 754 KB CSA Usage 60 KB Total 814 KB
Unicenter CA-Jobtrac has one FMID. It is CHDB000.
CA Common Services
Unicenter CA-Jobtrac requires the following CA Common Services: CA LMP CA-GSS/CA-GREXX CAIENF CAIRIM CA-Datacom/AD CA-C Runtime CA-Easytrieve CA-XPS CAICCI CAISSF CAISDI/els CAIVPE ViewPoint
If other CA products are installed at your site, some of these services may already be installed. This section presents an overview of each of these services. Note: For more information, see the CA Common Services Getting Started and Administrator Guide.
CA LMP
The CA License Management Program provides a standardized and automated approach to the tracking of licensed software. It uses common realtime enforcement software to validate the client's configuration. CA LMP reports on activities related to the license, usage and financials of CA products. The routines that accomplish this are integrated into the CAIRIM service.
CA-C
CA-C Runtime is a runtime facility with reentrant capabilities. Its modular architecture insulates CA-C Runtime programs from system and release dependencies. There is little, if any, system-dependent code linked with the user program, allowing for smaller user programs and easier maintenance. CA-C Runtime uses a memory manager to handle dynamic allocation requests for small pieces of storage, enabling fewer calls to be made on the operating system resulting in faster allocation and deallocation.
CA-Datacom/AD
Unicenter CA-Jobtrac uses CA-Datacom/AD as its database. CA-Datacom/AD is a database engine that allows for forward recovery, data integrity after a system outage, backup-while-open, and more.
CA-Easytrieve
The CA-Easytrieve reporting component is a report definition facility with the power of a comprehensive programming system. CA-Easytrieve lets you modify and print the contents and layout of predefined CA product reports in an English-like language. The CA-Easytrieve Common Component produces Unicenter CA-Jobtrac reports. If you have the separately licensed product Unicenter CA-Easytrieve, you can use it for Unicenter CA-Jobtrac. Otherwise, you can use the no license fee copy of CA-Easytrieve that is included with Unicenter CA-Jobtrac.
CA-GSS
The Global SubSystem (CA-GSS) is a product that offers software that performs across many of the CA product families. CA-GSS enables CA products to communicate with each other and is designed to help meet the increasing need of data center operations for quick access to information from many different sources. For example, CA-GSS lets Unicenter CA-Jobtrac access data gathered by Unicenter CA-SYSVIEW. This information can be used when determining how to schedule a particular job.
CA-XPS
CA-XPS is the Cross-Platform Scheduling router. It is used when a scheduler or an agent requests a job to be executed on z/OS. Requests are sent from a scheduler or an agent to CA-XPS, which then forwards the request to a specific scheduling product. CA-XPS lets multiple copies of Unicenter CA-Jobtrac (or Unicenter CA-7 or Unicenter CA-Scheduler) participate in cross-platform scheduling on the same z/OS image.
CAICCI
CAICCI, CAI Common Communications Interface, is a communications facility that enables CA solutions to communicate with one another. This facility provides a layer that isolates application software from the specifics of the communications environment.
CAIENF
CAIENF, CAI Event Notification Facility, is an operating system interface service that enables CA solutions to obtain data from the operating system. By centralizing operating system interfaces within CAIENF, many features that were formerly available within a single solution can be shared across the entire product line.
CAISSF
The CAI Standard Security Facility (CAISSF) lets CA products offer standardized security interfaces without regard to the particular needs of underlying access control software. CAISSF offers user authentication and resource access validation facilities, and can interface with CA security products (CA-ACF2 or eTrust CA-Top Secret) or compatible non-CA security products. CAISSF is a subservice contained within the CA z/OS Service code, S910 (CAIRIM). For CA security products, CAISSF features include: A single security mechanism Isolation of CA products from CA or vendor mechanisms
For non-CA security products, CAISSF features include: Resource class translation Access level translation Selective logging of requests Request type control Message support for failed access
Note: CA-Datacom/AD requires CAISSF.
CAIRIM
CAIRIM, CAI Resource Initialization Manager, is the common driver for a collection of dynamic initialization routines that eliminate the need for user SVCs, SMF exits, subsystems, and other installation requirements commonly encountered when installing systems software.
CAISDI/els - Service Desk Integration

CAISDI provides a set of services that open Unicenter Service Desk requests from the z/OS environment. The requests can be opened directly by CA products, or they can be opened on their behalf, depending upon the requirements of each specific product using the interface. There are three main components involved in this interface. Depending on each individual CA product using CAISDI, one or more of these components will be required. In the configuration steps, you may choose to configure only the components you currently need. Unicenter CA-Jobtrac uses the CAISDI/els (Event Library Support) component for its Unicenter Service Desk integration feature. Note: For more information about this feature, see the Extended Scheduling Services Guide and the CA Common Services Getting Started guide.
CAIVPE
The CA Virtual Processing Environment (CAIVPE) is an interproduct Service used by CA products running under Advantage CA-Roscoe, TSO, or CICS. It contains monitor-specific code and lets your CA products run independently of the environment. The routines that accomplish this are grouped under the CA z/OS Service code, WU42. CAIVPE features include: Making environment inquiries Making terminal inquiries Reading and writing directly from and to sequential files Performing uppercase and lowercase translation Issuing messages to both terminal and console Checking runaway tasks Dumping application-specific storage before giving control to the operating system
Note: CA-Datacom/AD requires CAIVPE.
ViewPoint
Viewpoint is a windowed execution environment for mainframes. It uses SAA/CUA standards to enhance the integration of your CA products.
CA-Datacom/AD Considerations
Review the following considerations before installing CA-Datacom/AD.
Install a User SVC for CA-Datacom/AD

CA-Datacom/AD requires the installation of a user SVC into the operating system for CA-Datacom/AD. You can install the SVC using the CAIRIM service of CA Common Services. The module DBRIMPR that actually installs the CA-Datacom/AD SVC issues several informational messages and error messages as needed. Note: For these error and informational messages, their meanings, and any action you need to take, see the Advantage CA-Datacom/DB Message Guide. First, determine a user SVC number that is available. User SVC numbers are between 200 and 255. The default SVC number for CA-Datacom/AD is 246. To determine which SVC numbers are available, either check with your systems programmer or, if you have a version of CA-Datacom/AD or Advantage CA-Datacom/DB installed, you can run a DBUTLTY job with the control statement REPORT MEMORY=MVS to obtain a list of all of the user SVC numbers in your operating system. This report tells you which SVC numbers are unused and which are already being loaded as the CA-Datacom/AD SVC (along with the current release and maintenance level of that SVC code). Note: For more information, see the REPORT MEMORY=MVS (SVC Report) in the Advantage CA-Datacom/DB DBUTLTY Reference Guide. If you are installing CA-Datacom/AD for the first time, you must select a currently available unused SVC number. If you are installing a second copy of CA-Datacom/AD with the same version number, another SVC number can be selected or the second CA-Datacom/AD environment can use the same SVC number, but use a different SUBID. For example, the first CA-Datacom/AD environment may be using SVC 246 with SUBID 0 whereas the second CA-Datacom/AD environment could use SVC 246 with SUBID 1. This way, depending upon which SVC/SUBID combination is referenced by the application program, communication is established with the desired CA-Datacom/AD environment.
Each Advantage CA-Datacom SVC number can support up to 256 different MUFs. This is managed through the use of a SUBID that is associated with each SVC. Each MUF uses a unique SVC/SUBID combination that is defined through the DBSYSID macro which in turn generates a unique DBSIDPR module for that MUF. The DBSIDPR module is generated on-site as one of the CA-Datacom/AD common installation job steps. SUBID values range from 0 through 255. All SUBID values except for 7, 8 and 9 are unrestricted on the amount of Extended Common Storage Area (ECSA) the MUF is allowed to use. Note: For more information about SVCs and SUBIDs, see modifying DBSIDPR parameters and establishing communication with z/OS in the Advantage CA-Datacom/DB Database and System Administrator Guide. If you are installing a different version of CA-Datacom/AD than is currently installed, there are two options available: Select a new SVC number to use for this different version. This provides the most isolation between versions available and completely eliminates any possibility of a bad or corrupted SVC for one version impacting the other version. We recommend this method. The CA-Datacom/AD use of SVC numbers is forward compatible but not backward compatible. That is, CA-Datacom/AD r10 can use an r10 SVC or an r11 SVC, but CA-Datacom/AD r11 cannot use an r10 SVC. This method allows all applications to reference the same SVC/SUBID as before without the potential JCL changes needed to access a different version of the DBSIDPR module. If this method is selected, load the new SVC/SUBID code prior to beginning the CA-Datacom/AD install or upgrade. You also need to specify the optional parameter of REINIT on the CAIRIM control statement. Refer to the following section for more information. Important! To avoid unpredictable results, do not attempt for any reason to overlay the existing r10 SVC with the r11 SVC if other DBUTLTY or MUF jobs are actively using it.
Install the SVC with CAIRIM

The CAIRIM (CA Resource Initialization Manager) is the common driver in the CA Common Services for z/OS and OS/390 for a collection of dynamic initialization routines. You can use it to install the Advantage CA-Datacom/DB SVC. For further information regarding the operation of CAIRIM, refer to the CA Common Services for z/OS and OS/390 Administrator Guide. The installation tasks temporarily install the Advantage CA-Datacom/DB SVC into your operating system environment. This SVC is valid only until the next IPL. To install the SVC automatically during each IPL, perform the following tasks. Refer to the CA Common Services for z/OS and OS/390 Administrator Guide for other ways to use CAIRIM. To install the SVC with CAIRIM: 1. Update the PARMLIB member in your CAIRIM startup JCL with the command statements using the follow format: Updating PARMLIB
(1) PRODUCT(CA-DATACOM)VERSION(BD11)INIT(DBRIMPR) -
PARM(Dnnn,DBSVCPR) 3 ,REINIT ,L=xxx ,T=2 4

Note: 1 This hyphen is a continuation character that is placed at the end of the first line.
Keywords Dnnn
Description (Required.) D is a constant for a Advantage CA-Datacom/DB installation and must precede the the SVC number (nnn) you select to use. This installation assigns 246 as the Advantage CA-Datacom/DB SVC number. If the specified SVC is already active (in-use), you will receive an error message to this effect and an available alternative SVC number is noted. Valid Entries: D200D255
Default Value: (No default.) ,TYP= ,T= (Optional.) Use the TYP= parameter to denote the SVC type as 2, 3, or 4. We strongly recommend using the default value, TYP=3. Refer to the Advantage CA-Datacom/DB Database and System Administrator Guide for information regarding SVC types. Valid Entries: 2, 3, or 4
Default Value: 3
Keywords ,REINIT
Description (Optional.) To force the original number that you selected to be used thereby replacing the currently in-use SVC, add the keyword value REINIT to the parameter specification. If you use this parameter, we strongly recommend that after the new SVC has been successfully installed you then remove this parameter. (Optional.) Use this parameter to specify a suffix value to be appended to the DBLIB DDname. The DDname derived must exist in the CAS9 procedure. You would use this parameter if you want to use CAIRIM to install multiple version of the CA-Datacom/AD SVC. For example, if you want to install the r11 SVC and also a CA-Datacom/AD r10 SVC, you could specify the control statements as follows: PRODUCT(CA-DATACOM) VERSION(BD11) INIT(DBRIMPR) PARM(D246,DBSVCPR,TYP=2) PRODUCT(CA-DATACOM) VERSION(BD1 ) INIT(DBRIMPR) PARM(D249,DBSVCPR,T=2,LSFX=1 Valid Entries: )
,LSFX= ,L=
1 to 3 alphanumeric characters
Default Value: (No default.) 2. Update the CAS9 procedure in your system PROCLIB as follows: //DBLIB DD DSN=cai.db11.loadlib,DISP=SHR or //DBLIBxxx DD DSN=cai.db11.loadlib,DISP=SHR (If the LSFX= parameter has been specified, as in the previous example, any DBLIBxxx DDname derived with a suffix value must also be added to the CAS9 procedure.) Important! If you fail to provide the DBLIB DD statement, CAIRIM could possibly install an invalid, previous release SVC module. 3. Incorporate this job: install member AXINS05 requires the CA Common Services for z/OS and OS/390 load library and the CA-Datacom/AD load library to be APF-authorized. After the initial installation, this job should be incorporated into your site-standard CAS9 procedure so that the SVC is automatically installed after an IPL.
4. Run the DBUTLTY SVC Report (REPORT MEMORY=MVS) to verify your work after defining the SVC. See the Advantage CA-Datacom/DB Database and System Administrator Guide and the Advantage CA-Datacom/DB DBUTLTY Reference Guide for information on this report. Important! You must install the SVC on every machine that might run the Multi-User Facility region, a DBUTLTY job, or make a database request through the Cross-System Coupling Facility (XCF).
Edit JCL
The first step of the installation process is to download a sample JCL PDS that contains all the JCL necessary to install the CA-Datacom/AD environment. Each job included in the sample PDS has a flower box at the top that describes the changes required to edit the JCL to meet the installation requirements for your site. The following is a sample:
// // // // // // // // // // // // // // INSTRUCTIONS: CHANGE JOB CARD AS NECESSARY FOR YOUR SITE. 1. PERFORM A GLOBAL CHANGE OF "CAI.SMPCSI.CSI" TO THE NAME OF THE SMP/E CSI DATA SET. WORKSHEET PARAMETER 1 2. PERFORM A GLOBAL CHANGE OF "CAI.SHLQ" TO THE HIGH LEVEL QUALIFIER OF THE SMP/E DATA SETS. WORKSHEET PARAMETER 2 4. PERFORM A GLOBAL CHANGE OF "AX1 SS" TO THE VOLSER OF THE INSTALL TAPE. WORKSHEET PARAMETER 24 5. PERFORM A GLOBAL CHANGE OF "TAPE" TO THE UNIT TYPE OF THE INSTALL TAPE, E.G."CART" WORKSHEET PARAMETER 25
The list of JCL edits needed is covered in Chapter 3, Worksheets on page 59. You can edit each job manually according to the flower box instructions, or you can use a PDS utility to perform the edits. In the following sections, we discuss a few available PDS editing tools. Remember to save the original sample PDS before doing any mass edits in case you want to redo your edits.
IBM CBIPO
If you have the IBM CBIPO, there is a procedure using either the IPOUPDTE or the CPPUPDTE utility to facilitate editing the install sample JCL job members. You can review sample JCL PDS members @AXIPOJC, @AXIPOIN, and @AXIPDMY to use a batch program that globally changes the sample JCL PDS for the parameter value strings to the desired values. @AXIPOJC Contains a sample job JCL to execute batch program. @AXIPOIN Contains a sample parameter string to change SYSIN member. @AXIPDMY Contains a sample prerequisite member to rename for batch program use. Use the sample member @AXIPOIN when using IPOUPDTE to edit the CA-Datacom/AD installation. The sample member provides the update parameters in the specific order needed for the installation JCL editing. Also, make sure that each line of the sample input member (@AXIPOIN) is reviewed and updated with the appropriate worksheet value according to the comments (at the right of each line). Since the batch JCL editing procedure changes all members, you may want to create a backup copy of the sample JCL PDS before executing @AXIPOJC. If necessary, rename @AXIPDMY to $$$COIBM if such a member does not exist. Although the global edit procedure eliminates the requirements for almost all manual editing of install jobs, you should still review the instruction block in each job for any optional changes.
Edit SAMPJCL Using the Supplied REXX Execs Under ISPF

If you use ISPF, the SAMPJCL file contains two REXX execs to facilitate editing the install sample JCL job members. You can use SAMPJCL PDS members $DCOMEDT and $EDITINP to make global changes in the SAMPJCL PDS for the intended worksheet parameter strings. $DCOMEDT Contains a mainline REXX exec that is executed under ISPF. $EDITINP Contains a sample REXX exec that makes the global changes. Member $DCOMEDT contains a reference to the SAMPJCL library on the second line of the exec. Simply replace the string CAI.SHLQ.SAMPJCL with the name of your SAMPJCL library. Member $EDITINP contains an edit command for each worksheet item in the form of 'ISREDIT C "STRING1" "STRING2" ALL'. In each case, STRING1 represents what is currently in the installation job members in the SAMPJCL PDS. Change STRING2 so that the worksheet values for your installation are incorporated. Once you have made the appropriate changes, simply issue the following command from any ISPF panel:
TSO EXEC 'cai.shlq.sampjcl($DCOMEDT)'
Where cai.shlq.sampjcl is the name of your SAMPJCL library. Although this global edit procedure eliminates the requirements for almost all manual editing of the installation jobs, you should still review the instruction block in each job for any optional changes.
CA-Datacom/AD Product Installation

Normally, all CA products for the z/OS environment are installed using SMP/E. While CA-Datacom/AD still uses SMP/E in its installation and maintenance, the SMP/E portion of the installation of CA-Datacom/AD has been preinstalled for you. This portion of the installation from the user's view consists only of downloading the preinstalled libraries and CSI from the product tape. The user is only required to rename the predefined DD definitions that occur in the CSI with their site-specific data set naming conventions. All users, whether installing new, or upgrading from the previous release, need to do this portion of the installation. Important! Because of this preinstallation aspect, do not change the zone names. Changing the zone names causes problems if any maintenance is to be applied using SMP/E. Periodically, standard maintenance/genlevel tapes for one or more of the CA-Datacom/AD products are distributed. Refer to the chapter about product maintenance for more information.
Products Installed
CA-Datacom/AD consists of the following product components: Advantage CA-Datacom/DB Database (with the Datadictionary component) CA-Datacom/AD Database SQL Option CA-Datacom/AD Database Option for CICS Advantage CA-Dataquery for CA-Datacom CA-IPC (Inter-Product Components)
The version and maintenance levels for these products are listed in the release letter that is shipped with the installation tape.
List Libraries for CA-Datacom/AD Products in JCL

Additional samples for JCL and programs are provided in the CAIMAC install library. You can copy and modify these samples for your specific requirements. Any JOB statements should be coded to your site standards and specifications. All data set names and library names should be specified with the correct names for the installation at your site. In many examples, a REGION= or SIZE= parameter is displayed in an EXEC statement. The value displayed should be adequate in most instances, but you can adjust the value to your specific needs. The libraries listed for searching must include the following in the order shown: 1. User libraries (CUSLIB) you may have defined for specially assembled and linked tables, such as DBMSTLST, DBSIDPR, DDSRTLM, DQSYSTBL, or User Requirements Tables (URTs) 2. CA-Datacom/AD base libraries (CAILIB): Advantage CA-Datacom/DB, Advantage CA-Datacom SQL Option, Advantage CA-Dataquery 3. CA Common Services base libraries
Unicenter CA-Jobtrac Considerations

Review the following considerations before installing Unicenter CA-Jobtrac.
Subsystems
Unicenter CA-Jobtrac uses two subsystems: GOAL and JT11. Important! Unicenter CA-Jobtrac must have CA-GSS installed. Although you can run Unicenter CA-Jobtrac without CA-GSS active, the CA-GSS CAILIB must be available to Unicenter CA-Jobtrac. Note: CA-GSS is part of CA Common Services. We require that you install CA-GSS prior to installing Unicenter CA-Jobtrac. CA-GSS uses a subsystem named GOAL. It dynamically installs a subsystem with this name. This ISET is for the product IMODs shipped with Unicenter CA-Jobtrac. Unicenter CA-Jobtrac will not install properly if the ISET is not available. You can use this ISET or define another for your own use. The Unicenter CA-Jobtrac installation procedure STAGE2 allocates and populates the Unicenter CA-Jobtrac required ISET data set. CA-GSS must be set up to include networking support for all JES nodes in which Unicenter CA-Jobtrac is to be used for NJE support. This is done using the GoalNet features of CA-GSS. Note: For information about GoalNet, see the CA Common Services documentation.
JES Usage
All systems that run scheduled batch jobs must be able to communicate with the Unicenter CA-Jobtrac checkpoint. The VINITx task is required only for pre-JES console automation and possible pre-JES startup data triggering functions. During initial testing or implementation, you usually do not need to start VINITx during IPLs (S VINITx,PARM=IPL). If you are using the BSPACE parameter in the CONDEF statement defined in the JES2INIT file using characters @, #, or $, it will conflict with the internal verification procedure job JOBT@#$J. If you are using one of these characters, change it to a different character to avoid any problems. To use JES3 with Unicenter CA-Jobtrac, add a SUBSYS(STC) statement to your SMFPRMnn member in SYS1.PARMLIB. This statement can be specified as follows: SUBSYS(STC,EXITS(IEFU83) If you already have a SUBSYS(STC) statement, you do not need to change it. The Unicenter CA-Jobtrac STC is active on all systems in the JES complex (shared spool environment). You can think of Unicenter CA-Jobtrac as a logical extension to JES. JES monitors a job from submission through printout, and Unicenter CA-Jobtrac extends those boundaries to include scheduling, submission, execution, and historical archival. The JES checkpoint indicates only those jobs that are currently queued for execution or printing. The Unicenter CA-Jobtrac checkpoint indicates events queued for submission, execution, or history archival. Unicenter CA-Jobtrac works the same way with JES3 as it does with JES2, except that the queue class and JOB statement AUTO-SCHD features are not supported. To AUTO-SCHD events in a JES3 system, you must use the step method. Note: For more information, see the Operator Guide. Unicenter CA-Jobtrac does not scan the JES spool for job status. Unicenter CA-Jobtrac uses information from SMF exits and CAIENF to establish event status. If you must cycle JES2 or JES3, you must also cycle Unicenter CA-Jobtrac. If you do not, Unicenter CA-Jobtrac will not work properly.
Installation Tape Information

During the installation for Unicenter CA-Jobtrac, you will need to access up to three installation tapes, and possibly one service pack tape (for Unicenter CA-Jobtrac). The tapes you may need are the following: The CA Common Services installation tape The CA-Datacom/AD installation tape The Unicenter CA-Jobtrac installation tape The latest Unicenter CA-Jobtrac service pack tape
CA Common Services Installation Tape

If you have not already installed all the common services components required for Unicenter CA-Jobtrac r11, you will need to access this tape to install these components. Note: For more information about this tape, see the CA Common Services Getting Started guide.
The CA-Datacom/AD Installation Tape

Unless CA-Datacom/AD r10 or higher is currently installed, you need to access this tape. If you are an existing Advantage CA-Datacom/DB customer, you may choose to use the full product instead of the common component. We recommend that you install the CA-Datacom/AD even if you have the full product to avoid any maintenance-level conflicts and limit the impact that may occur to your production database environment. Note: For more information about this tape, see the CA-Datacom/AD Installation and Maintenance Guide.
The Unicenter CA-Jobtrac Installation Tape

Unicenter CA-Jobtrac is distributed on a single, standard-label cartridge that must be installed using SMP. The cartridge is prepared in IBM SMP RELFILE (unloaded PDS) format. Note: For information about IBM SMP RELFILE format, see the IBM SMP General Information Manual. The following table describes the files on the installation tape used by Unicenter CA-Jobtrac: File 005 006 009 011 014 032 033 . . 082 Data Set Name CAI.CPM.SMPMCS Description CA-CPM SMP Modification Control Statements
CAI.CPM.MAINT.SMPMCS CA-CPM Maintenance SMP Modification Control Statements CAI.SAMPJCL REXX.SAMPLES CAI.PDFDOC SMPMCS sysmod.Fn " " " Unicenter CA-Jobtrac Sample JCL library Unicenter CA-Jobtrac Sample REXX library Unicenter CA-Jobtrac Adobe Documentation files SMP Modification Control Statements SMP RELFILEs begin here " " "
The Latest Unicenter CA-Jobtrac Service Pack Tape

Since some time may have passed between the time that Unicenter CA-Jobtrac r11 was released and the time you implement the release, one or more service packs may be available. Service packs are cumulative and contain all the maintenance for the product since the base release. Only the latest service pack tape is required. You should have received the latest service pack with the base tape for Unicenter CA-Jobtrac. The description of this tape's contents are described in the accompanying cover letter. Maintenance for CA Common Services and for CA-Datacom/AD is included in the installation tape for these components.
SMP/E Considerations
You use SMP/E to install Unicenter CA-Jobtrac. This manual assumes that you are familiar with SMP/E. If you have not previously installed program products using SMP/E, review this entire installation guide before you begin the installation. Check with your SMP/E systems programmer if you have questions about your SMP/E environment. The installation creates new global, target, and distribution zones. Two cylinders of 3390 space for each CSI should be sufficient for Unicenter CA-Jobtrac functions and allow for growth required by future maintenance.
Data Set Placement Considerations

Carefully plan the placement of the following data sets.
CA-Datacom/AD Files
The most heavily used file in CA-Datacom/AD is the LXX file. The LXX, or the Log file, is updated each time a change is made to the database. This lets CA-Datacom/AD buffer updates to the actual database and still maintain data integrity in the event of an outage. Since this file is highly used, you should place it so that it can be accessed efficiently. None of the CA-Datacom/AD databases should be placed on packs that are highly used, such as paging packs or JES spool packs. The most heavily used data area in the Unicenter CA-Jobtrac database is the EVT161 file that contains the active event processing data. Take care to ensure that this file also has adequate performance. Generally, CA-Datacom/AD databases are only accessed from one system in the sysplex. A single accessing CA-Datacom/AD address space runs in the sysplex. Locally on this system, the database is accessed using an SVC. When sharing a database with other systems in the sysplex, access to the database uses XCF. While the database can reside on any system in the sysplex, the best performance is achieved when the database is running on the same system as the Unicenter CA-Jobtrac primary submission system.
Sysout Capture File

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 Unicenter CA-Jobtrac on multiple systems that share DASD, the sysout capture file must be on a pack on your primary (event-submitting) Unicenter 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. More information: Use Other Sysout Capture Products on page 230
Database Recovery Planning

The database backup requirements you need depend on your plans for recovery. This topic discusses backup and recovery at a high level. Note: For more information about database backup, recovery, and utilities, see the Reports, Maintenance, and Recovery Guide.
Common CA-Datacom/AD Terms

The following lists some common terms used when discussing CA-Datacom/AD. pipelining Pipelining is caching database updates to reduce DASD activity and to increase database access speed. LXX The LXX is the log file. The combination of LXX and pipelining prevents data loss. All updates are logged directly to the LXX. spill The spill process removes LXX log entries that are no longer needed and copies them to a RXX recovery file. FXX The FXX is the Force Recovery Area. The FXX is used with the LXX for startup recovery. RXX The RXX is the recovery file. Actually a number of recovery files are created, generally as GDG tape files. Spilling the LXX creates the RXX files. These files can be used to run a forward recovery for a database that has been restored from a backup. MUF The MUF is the Multi-User Facility. This is the CA-Datacom/AD started task. Applications communicate though the MUF to access the database tables. load A load is the process of reloading a database from a backup. forward recovery The forward recovery process applies RXX recovery files to a database that has been loaded from a backup to restore the database to the pre-failure condition. hot backup A hot backup is a fuzzy backup taken while the database is active and being updated.
static backup A static backup is a backup taken while the database is closed and all activity is stopped. base or database A base or database is part of the MUF. In CA-Datacom/AD, a MUF can have multiple databases, or bases as CA-Datacom/AD refers to them. A unique database ID, DBID, identifies each base. Usually each product has a single database. Unicenter CA-Jobtrac allocates two bases: one for Unicenter CA-Jobtrac processing and one for forecasting. DBID A DBID is a database ID. Each database in a MUF has a unique ID. The DBID is a numeric value identifying the database. By default, the Unicenter CA-Jobtrac DBIDs are 0161 (production) and 0162 (forecast). data area The data areas represent the physical files that make up a database. These data areas, with the database index, make up the physical database files. Unicenter CA-Jobtrac has four data areas, EVT, HIS, OPT, and STG. These are paired with the DBID to make up the DDNAME and file name for these files. With the default of 161, the area DDNAMEs are EVT161, HIS161, OPT161, and STG161. index area The index area exists in a database. Each database has a single index for all tables and areas in the base, known as the IXX. Like the areas, the IXX is paired with the DBID to make up the DDNAME and file name for the index. With the default of 161, the index DDNAME is IXX161.
Log File and Recovery File

The CA-Datacom/AD log file, the LXX, is updated each time the database is changed. CA-Datacom/AD pipelines updates to the database, keeping changes in storage until they can be written to the database in a group. This decreases I/O to the database files and greatly increases the speed of access. The LXX records need to be kept in the log until the database changes are committed to the database DASD. Once this is done, these records can be removed from the LXX to allow for adding more records. The spill process removes completed records from the LXX file and writes them to a recovery file, the RXX. This process frees up space in the LXX and creates RXX recovery files that can be used to forward recover a restored database. The CA-Datacom/AD startup option, LOGRCV NO, establishes the creation of the recovery files. By default, this value is set to NEVER, which reuses the log file and does not create the recovery file. LOGRCV YES indicates to use a dedicated tape drive for the recovery file. Since this is not usually the best solution, the LOGRCV NO option indicates that no tape is allocated, and the RXX is created by running a spill job. During the installation customization, you are instructed to change LOGRCV to NO.
System Failure or CA-Datacom/AD MUF Failure

The CA-Datacom/AD database started task is called the Multi-User Facility (MUF). With CA-Datacom/AD, a system outage or MUF failure is recovered automatically when the MUF is restarted. If the system where CA-Datacom/AD runs fails, when CA-Datacom/AD is restarted on the system after IPL, or on an alternative system with shared DASD, the database is automatically recovered to the point of failure. CA-Datacom/AD processes the LXX log file and brings the database up to date to the time of failure. This occurs without the need to restore from backup or to perform a manual recovery.
DASD Failure or Disaster Recovery

DASD failure recovery and disaster recovery both require that a database backup is available to restore the database. To prepare for these types of failures, you must take regular backups.
Backup Utilities
We recommend that you use the CA-Datacom/AD DBUTLTY utility to perform backups and restores for the Unicenter CA-Jobtrac database. Though it is technically possible to use other backup utilities for backup and restore, we do not recommend it for the following reasons: These utilities do not know the database structure. The data areas and index for a database may be on multiple packs and therefore may not be backed up at the same time. Files may not be on the same backup tape if full pack backups are used. Restoration and recovery of these files becomes more difficult.
The CA-Datacom/AD DBUTLTY backup backs up all components of a database together ensuring that they are in sync with each other when they are restored.
Backup Types
You can perform two types of backups for the Unicenter CA-Jobtrac database. The hot backup can be done with the database active. This is a fuzzy backup and may contain incomplete updates. To restore from this type of backup, you must perform a forward recovery using all the RXX recovery files created since taking the restored backup. This method produces the most accurately restored database. Once forward recovery is complete, the database is in the same state as it was before the failure. A static (or cold) backup requires closing the database and shutting down all Unicenter CA-Jobtrac started tasks, Primary and Monitors. This is a stable backup taken at a single point in time. When a static backup is restored, the database is complete as of the time the backup was taken. Forward recovery can also be used to restore the static backup up to the time of failure, but it is not required as it is with a hot backup. If you do not perform forward recovery, the static backup can be used to restore your history, JTS tables, and calendars to the database and as well as the checkpoint information at the time of the backup. Once restored and the checkpoint has been examined, you may want to archive all the jobs to history, using the archive ALL,CLEAN option, so that you can start fresh with your job schedules. This method does not provide a complete restore of the database but does restore tables that are not often changed. This method also provides a quicker method for getting Unicenter CA-Jobtrac up and running.
Backup Frequency
The longer the time between backups, the longer forward recovery takes to recover the database. To reduce this recovery time, we recommend taking the database hot backups once a day.
Forward Recovery
If you have taken a hot backup, the forward recovery is required to have database integrity. With a static backup, the database is complete if no forward recovery is done, but it is not current. It reflects the status in the system at the time the backup was taken. Forward recovery requires that a final spill of the log file, the LXX, be done to have a complete set of RXX recovery files. The RXX files spilled since the backup was started must then be applied to the database in the order they were created using the recovery job.
Disaster Recovery
Disaster recovery (DR) varies depending on the hardware capabilities in your organization. If you are mirroring your DASD to a DR remote site, and all the Unicenter CA-Jobtrac and CA-Datacom/AD files are included in that mirroring, recovery on the DR site is the same as recovery from a system failure. The mirrored files would be present. By starting the CA-Datacom/AD MUF, CA-Datacom/AD would use the LXX log file to perform recovery to the point of failure. Unicenter CA-Jobtrac could then be started with PARM=HOLD to let you examine the state of your workload before releasing Unicenter CA-Jobtrac to resume processing. Some sites mirror locally, and periodically sever the mirror connections to allow for a copy of all data at the same point in time. This is sometimes called a flash copy. In this case, the LXX and the databases are captured at the same instance in time. If CA-Datacom/AD is started with these synchronized files, the database is restored the same as in the system failure, but only to the point that the flash copy was taken. Once again, you should start Unicenter CA-Jobtrac with the PARM=HOLD to examine the state of jobs when the copy was taken before resuming processing. If your DR planning is not using mirroring and you are planning to restore from a backup at your DR site, you must periodically send your backups offsite. If you are taking hot backups, you must spill the LXX to the RXX following the backup and keep the backup tape and this first RXX tape offsite to maintain your database integrity. Having these two tapes together allows the database to restore to a stable point. In the event that the files need to be restored to another site, the hot backup can be restored and the first tape applied to ensure that all transactions are in a completed status. If all the RXX tapes are sent to the DR site, a nearly complete restore of the database can be done. The final updates that were still in the LXX log file may not be available to perform a complete restore. If the LXX is available, it should be spilled to a final RXX before recovery. This brings the database up to the time of failure. If you are unable to fully recover the database, either due to using a static backup with no recovery or a hot backup with incomplete recovery, the more static components of the database such as the history, audit, JTS tables, and calendars are valuable to restore. The checkpoint data may not be as useful, and in a DR mode you may want to clear the schedule using an Archive ALL,CLEAN and begin loading schedules from a particular point.
Other Products
When planning your backup and recovery, you should consider other products that are sharing the same CA-Datacom/AD MUF. Only similar products should be sharing this environment. The one other product that you may want in the same MUF would be Unicenter CA-11. You should choose the same backup plan for all products that are sharng the same MUF because the RXX recovery file is for all products within the MUF. Since stopping Unicenter CA-11 can be difficult, we recommend that you use a hot backup if these two products share a single CA-Datacom/AD MUF. You can also include the backup of more than one database in the backup job, so that you can choose to back up the databases for all products sharing a MUF in a single job. Note: For more information about backup and recovery, see the Reports, Maintenance, and Recovery Guide.
Interfaces with Other Products

Unicenter CA-Jobtrac interacts with other products as described in the following sections.
AllFusion CA-Librarian
With Unicenter CA-Jobtrac, you can use an AllFusion CA-Librarian JCL library instead of a standard PDS JCL library. More information: Step 17: (Optional) Link AllFusion CA-Librarian Modules on page 107 Chapter 5, Customization Job Streams on page 111
AllFusion CA-Panvalet
With Unicenter CA-Jobtrac, you can use a AllFusion CA-Panvalet JCL library instead of a standard PDS JCL library. More information: Step 16: (Optional) Link AllFusion CA-Panvalet Modules on page 107 Chapter 5, Customization Job Streams on page 111
CA-Blockmaster
Exclude Unicenter CA-Jobtrac programs by adding the following to the CA-Blockmaster Exclude table: BLMTABLE BLMTABLE BLMTABLE BLMTABLE TYPE=E,PGM=GJC TYPE=E,PGM=GJTR TYPE=E,PGM=GJC3 TYPE=E,PGM=JCL3
BrightStor CA-HyperBuf
Exclude the Unicenter CA-Jobtrac files and programs. MODE=EXCLUDE PROGRAM=GJTR
Unicenter CA-MIM
Unicenter CA-MIM is a CA family of software products that makes sharing resources in multi-image and multi-system environments safe and efficient. Unicenter CA-MIM consists of Unicenter CA-MIA, Unicenter CA-MII, and Unicenter CA-MIC. Unicenter CA-MII is used to share DASD.
Unicenter CA-SYSVIEW
Unicenter CA-SYSVIEW is a powerful system tool that enables you to access information about your system and what is running on it. For example, you can check the amount of free space on a particular volume or determine the availability of tape drives. Unicenter CA-Jobtrac enables you to use Unicenter CA-SYSVIEW without exiting Unicenter CA-Jobtrac (use the Q line command). You can also use Unicenter CA-SYSVIEW with @JOBTRAC. To use Unicenter CA-SYSVIEW from Unicenter CA-Jobtrac, you must meet the following conditions: You must be a licensed Unicenter CA-SYSVIEW user. You must have Unicenter CA-SYSVIEW installed on your system. Your TSO session must have access to the Unicenter CA-SYSVIEW ISPF program and its associated files.
For more information about the Unicenter CA-SYSVIEW interface, see the Unicenter CA-SYSVIEW installation manual. For more information about @JOBTRAC, see the REXX information in the Extended Scheduling Services Guide.
Unicenter CA-View
Unicenter CA-View is a SYSOUT archival and retrieval system that stores computer output on either DASD or tape and retrieves that output on demand. More information: About the Unicenter CA-View Interface on page 230
Unicenter CA-11
When rerun/restart is required and Unicenter CA-11 is installed, you can access rerun/restart information by using the R line command. This takes you to the Unicenter CA-11 primary menu, and you navigate through the range of Unicenter CA-11 functions.
Other Products Through CA-GSS

The @JOBTRAC address environment that is available to CA-GSS is callable by other CA products that also use CA-GSS. This lets these products issue commands to examine and modify the Unicenter CA-Jobtrac workload. Unicenter CA-OPS/MVS is an example of a product that uses this interface.
System Considerations
You should consider the following system options before installing Unicenter CA-Jobtrac. Contact your systems programming staff for help. Unicenter CA-Jobtrac must execute from an APF-authorized library. SMF exits IEFUJV and IEFU83 must be active. They can be active through an IEFBR14 program. For more information, see the customizing SYS1.PARMLIB member SMFPRMxx information in Chapter 6, Customization Tasks on page 161. SMF record types 15, 26, 30, and 64 must be recorded. You can suppress the actual writing of these records to your SMF data set by coding an IEFU83, IEFU84, or IEFU85 exit. The Unicenter CA-Jobtrac SAMPJCL library contains a sample IEFU83 exit, named SAMPU83. This sample can also be linked with aliases of IEFU84 and IEFU85. For more information about use of SMF records by Unicenter CA-Jobtrac, see Chapter 6, Customization Tasks on page 161. For linkage editing requirements for the IEFU8x exits, see the appropriate IBM manuals. Exit IEAVMXIT must be activated for AMR (Automatic Message Recognition) triggers. For information about setting up the exit, see Chapter 6, Customization Tasks on page 161. The Unicenter CA-Jobtrac-started task requires both SUBMIT and UPDATE authority under your security system (eTrust CA-Top Secret, eTrust CA-ACF2, RACF, and so on). DD statements can be added to your TSO logon procedures or CLISTs to use the ISPF/PDF features of Unicenter CA-Jobtrac. For information about updating your TSO procedures, see Chapter 6, Customization Tasks on page 161 and Define Location Information (DYNAMLOC) and Initiation IMODs on page 176. If using CA-Datacom/AD security, Unicenter CA-Jobtrac STC and TSO users that access Unicenter CA-Jobtrac need to be authorized to access the Unicenter CA-Jobtrac databases (161 and 162 by default).
Security Considerations
When installing and using Unicenter CA-Jobtrac, you must consider the following: Security needed to install and run the Unicenter CA-Jobtrac product Security for using the Unicenter CA-Jobtrac features
If your installation uses a security system, your security administrator might need to authorize you to perform the following tasks: Allocate the installation libraries. Allocate and update the SMP/E libraries. Allocate the Unicenter CA-Jobtrac execution libraries (target libraries). Allocate the Unicenter CA-Jobtrac distribution data sets. Add the Unicenter CA-Jobtrac cataloged procedures to a system procedure library. Update the chosen APF linklist libraries in SYS1.PARMLIB when you are ready for execution. Enter the Unicenter CA-Jobtrac started task name in the appropriate authorized task tables. Give SUBMIT authority to the Unicenter CA-Jobtrac started task. You should give the Unicenter CA-Jobtrac task the same security attributes as production TSO user IDs. Enable or disable TSO users to update JCL, SCL, TEMPJCL, and DOC libraries. Obtain access to CA-Datacom/AD, if security is in effect.
If you are using a security system (such as eTrust CA-Top Secret, eTrust CA-ACF2, or RACF), give the Unicenter CA-Jobtrac started task SUBMIT authority. Unicenter CA-Jobtrac uses the following methods to secure its use: TRACAUTH table TRACX26 user exit
You use only one of the methods for security. Regardless of the method you use, the TRACAUTH table is still used to do the following: Specify a name for a location (optional). Specify which users are notified of abends and error conditions.
The TRACAUTH table contains entries that do the following: Define whether a user can perform specific Unicenter CA-Jobtrac functions. Assign names to locations.
The TRACAUTH table is created using the @AUTH macro. During installation, you run the job ASMAUTH to create a default entry in the TRACAUTH table. The default entry is used for all TSO users not specifically defined in other entries. For information about defining entries in the TRACAUTH table and about the ASMAUTH job, see Chapter 6, Customization Tasks on page 161. The TRACX26 user exit is called by the Unicenter CA-Jobtrac ISPF dialog and by @JOBTRAC to verify a user's authority to view, update, add, delete, or purge Unicenter CA-Jobtrac information. You can control access to the following areas using the TRACX26 exit: Events Holiday and cyclic calendars Global options Online table services Unicenter CA-Jobtrac captured sysout
Note: Take care using this exit. This is a client alteration of the product and may cause unpredictable results if not properly coded and tested. The provided sample is only a sample.
The available security methods essentially secure the same information. A few exceptions are described below. Which method you choose depends on the importance of these exceptions to you. 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. 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. The TRACX26 user exit does not offer this security.
Chapter 3. Worksheets
This section contains the following topics: CA Common Services . . . . . . CA-Datacom/AD Worksheets . . Unicenter CA-Jobtrac Worksheets
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
60 61 67
You should complete these worksheets before starting the installation process. This section contains checklists for the installation of CA-Datacom/AD and Unicenter CA-Jobtrac. Complete these checklists and use them during the product installations. These worksheets are designed to simplify specifying parameters during the installation. The parameters identified on this worksheet are required for all installation job procedures. Default values have been supplied for your convenience.
Chapter 3. Worksheets 59
CA Common Services
CA Common Services
The CA Common Services installation provides a worksheet. Check the CA Common Services (CCS) installation to obtain this worksheet. Even if you already have the CCS installed, you may want to obtain the data set information from this worksheet for reference in installing CA-Datacom/AD. Complete this worksheet at this time.
CA-Datacom/AD Worksheets
You can reproduce this worksheet or print the CA-Datacom/AD SAMPJCL PDS member @AXWKSHT.
Installation JCL PROCedure Parameters

These parameters are required for both new and upgrade install procedures:
Data Set Naming Checklist Items

Item 1 Parameter Description What data set name is used for the SMP/E CSI data set? Default: 'CAI.SMPCSI.CSI' Maximum length: 44 characters What high-level qualifier is used to prefix the SMP/E and custom data sets? Default: 'CAI.SHLQ' Maximum length: 28 characters What high-level qualifier is used to prefix the new CA-Datacom/AD data sets? If upgrading, this parameter must be different from worksheet item #6. Default: 'CAI.HLQ' Maximum length: 28 characters What high-level qualifier is used to prefix the installation backup files? Default: 'CAI.INST' Maximum length: 28 characters (Upgrade only.) What high-level qualifier is used to prefix the existing CA-Datacom/AD r10 SMP/E libraries? Default: 'CAI.PSHLQ' Maximum length: 28 characters What high-level qualifier is used to prefix the existing CA-Datacom/AD data sets for upgrade installs? Default: 'CAI.PHLQ' Maximum length: 44 characters
DASD and Tape Volume Names and Unit Types Checklist Items
Item 7 Parameter Description What DASD volume serial name is to be used for the CA-Datacom/AD SMP/E data sets? Default: 'VOL=SER=DASD01,' Maximum length: 14 characters
Item 8
Parameter Description What is the unit name of the device for temporary work DSNs? Default: 'SYSDA ' Maximum length: 8 characters What DASD type is the DASD01 volume? (for example,'SYSDA,3380,3390,9345') Default: '3390 ' Maximum length: 8 characters What DASD volume serial name is to be used for the CA-Datacom/AD target library data sets? Default: 'VOL=SER=DASD02,' Maximum length: 14 characters What DASD type is the DASD02 volume? (for example,'SYSDA,3380,3390,9345') Default: '3390 ' Maximum length: 8 characters What DASD volume serial name is to be used for the CA-Datacom/AD distribution library data sets? Default: 'VOL=SER=DASD03,' Maximum length: 14 characters What DASD type is the DASD03 volume? (for example,'SYSDA,3380,3390,9345') Default: '3390 ' Maximum length: 8 characters What DASD volume serial name is to be used for the CA-Datacom/AD VLS and backup data sets? Default: 'VOL=SER=DASD04,' Maximum length: 14 characters What DASD type is the DASD04 volume. (for example,'SYSDA,3380,3390,9345') Default: '3390 ' Maximum length: 8 characters What DASD volume serial name is to be used for the CA-Datacom/AD CXX data set? Default: 'VOL=SER=DASD05,' Maximum length: 14 characters What DASD type is the DASD05 volume? (for example,'SYSDA,3380,3390,9345') Default: '3390 ' Maximum length: 8 characters
10
11
12
13
14
15
16
17
Item 18
Parameter Description What DASD volume serial name is to be used for the CA-Datacom/AD index data sets? Default: 'VOL=SER=DASD06,' Maximum length: 14 characters What DASD type is the DASD06 volume. (for example,'SYSDA,3380,3390,9345') Default: '3390 ' Maximum length: 8 characters What DASD volume serial name is to be used for the CA-Datacom/AD database area data sets? Default: 'VOL=SER=DASD07,' Maximum length: 14 characters What DASD type is the DASD07 volume. (for example,'SYSDA,3380,3390,9345') Default: '3390 ' Maximum length: 8 characters What DASD volume serial name is to be used for the CA-Datacom/AD LXX and PXX data sets? Default: 'VOL=SER=DASD08,' Maximum length: 14 characters What DASD type is the DASD08 volume. (for example,'SYSDA,3380,3390,9345') Default: '3390 ' Maximum length: 8 characters What is the volume serial of the CA-Datacom/AD install tape? Default: 'AX11SS' Maximum length: 6 characters What unit type is the AXITVOL tape volume? Default: 'TAPE ' Maximum length: 8 characters
19
20
21
22
23
24
25
SVC and LXX/FXX Checklist Items

Item 26 Parameter Description What is the SVC number that CA-Datacom/AD is using? This SVC cannot be shared by any other products. Default: '246' Maximum length: 3 characters What is the SVC SUBID number CA-Datacom/AD is using? Default: '0' Maximum length: 1 character
27
Item 28
Parameter Description What is the SVC type CA-Datacom/AD is using? (2, 3, or 4) Default: '3' Maximum length: 1 character What is the block size used when initializing the LXX and FXX data sets? Default: 'BLKSIZE=27998' Maximum length: 13 characters
29
CA Common Services Checklist Items

Item 30 Parameter Description What is the data set name of the Target Load Library for the CA Common Services for z/OS and OS/390? Default: 'CAI.CACSS.CAILIB' Maximum length: 44 characters What is the data set name of the SMPE PPOPTION Library for the CA Products LMP Codes member? Default: 'CAI.CACSS.PPOPTION' Maximum length: 44 characters What is the CA Products LMP Codes member name in the SMPE PPOPTION Library? Default: 'LMPKEY' Maximum length: 8 characters What is the data set name of the Target Macro Library for the CA Common Services for z/OS and OS/390? Default: 'CAI.CACSS.CAIMAC' Maximum length: 44 characters
31
32
33
COBOL Compiles Checklist Items

Item 34 Parameter Description What is the data set name of the COBOL compiler library for the CA-Datacom/AD sample programs compilation? Default: 'CEE.ACEESRC1' Maximum length: 44 characters What is the data set name of the COBOL load library for the CA-Datacom/AD sample programs link-edit? Default: 'CEE.SCEELKED' Maximum length: 44 characters
35
Assembler and Link-Edits Checklist Items

Item 36 Parameter Description What is the name of the Assembler program? Default: 'ASMA90 ' Maximum length: 8 characters What is the name of Linkage Editor module for link editing? Default: 'IEWL ' Maximum length: 8 characters
37
CICS Usage Checklist Items

Unicenter CA-Jobtrac does not require CA-Datacom/AD support for CICS. Unless you have another need for CICS support (such as DataQuery), you can skip items 38-43. Item 38 Parameter Description What is the data set name of the CICS Macro Library? Default: 'CICS.MACLIB' Maximum length: 44 characters What is the data set name of the CICS Load Library? Default: 'CICS.LOADLIB' Maximum length: 44 characters What is the data set name of the CICS CSD for RDO? Default: 'USER.DFHCSD' Maximum length: 44 characters What is the group list for CICS? Default: 'CICSGRPL' Maximum length: 8 characters What is the suffix to be used for CICS table assemblies for CA-Datacom/AD? Default: '.AXSFX.' Maximum length: 2 characters What is the 3-character CICS opident of the master terminal operator for Advantage CA-Datacom CICS Services? Default: 'OPR' Maximum length: 3 characters
39
401
41
42
43
XCF Usage Checklist Items

Item 44 Parameter Description What is the name of the MUF to be used? Default: 'ADMUF01' Maximum length: 8 characters What is the group name of which the MUF is to be a member? Default: 'ADXGRP01' Maximum length: 8 characters :row, What is the internal name of the CXX? Default: 'AD11CXX' Maximum length: 8 characters
45
46
Unicenter CA-Jobtrac Worksheets

You can reproduce this worksheet or print the Unicenter CA-Jobtrac SAMPJCL PDS member @HDWKSHT.
SAMPJCL
This topic lists values to use when unloading the SAMPJCL from the Unicenter CA-Jobtrac installation tape. Item 1 Parameter Description What high-level qualifier do you plan to use for the SAMPJCL library? Default: CAI What generic unit name do you plan to use for the SAMPJCL library? Example: SYSDA What is the generic unit name to use for work files? Example: SYSDA What VOLSER do you plan to use for the SAMPJCL library? What is the VOLSER of the Unicenter CA-Jobtrac installation tape? Example: HDB000 What is the UNIT name of the tape device to use for the Unicenter CA-Jobtrac tape? Example: CART Your Value
4 5
Unicenter CA-Jobtrac Tape Install

This topic lists values to use when installing the Unicenter CA-Jobtrac tape. Item 7 Parameter Description What high-level qualifier do you plan to use for SMP/E system, distribution, and target libraries? Reference: #1 Default: CAI 8 What generic unit name do you plan to use for SMP/E system libraries? Default: DISK What VOLSER do you plan VOLSER= to use for SMP/E libraries? Default: None What generic unit name do you plan to use for temporary work files? Default: SYSDA What sysout class do you plan to use for SMP/E jobs? Default: * What VOLSER do you plan to use for SMPTLIB work libraries? Default: TAPE What generic unit name do you plan to use for the Unicenter CA-Jobtrac installation tape? Default: TAPE What is the VOLSER that is specified on the Unicenter CA-Jobtrac installation tape? Default: HDB000 What generic unit name do you plan to use for the SMP/E distribution libraries? Default: SYSDA PERMDA= Your Value CAI=
VOLSER=
10
WORK=
11
SYSOUT=
12
TLIB=
13
TAPE=
14
TAPVOL=
15
DUNIT=
Item 16
Parameter Description What VOLSER do you plan to use for the SMP/E distribution libraries? Default: None What generic unit name do you plan to use for the SMP/E target libraries? Default: SYSDA What VOLSER do you plan to use for the SMP/E target libraries? Default: None What is the name of the standard IBM System Maclib? Example: SYS1.MACLIB If you have AllFusion CA-Librarian, what is the name of your AllFusion CA-Librarian CAILIB? Default: CAI.LIBRARIAN.CAILIB If you have AllFusion CA-Panvalet, what is the name of your AllFusion CA-Panvalet CAILIB? Default: CAI.PANVALET.CAILIB What is name of IBM's LE link library? Example: CEE.SCEELKED If you plan to use the JTUSS command to access Unicenter CA-Jobtrac from UNIX Systems Services (USS), into what HFS directory should the command be installed? Example: /u/users/bin/jtuss What is the CA Common Services (CCS) SAMPJCL file name? Example: CAI.SAMPJCL
Your Value DVOL=
17
TUNIT=
18
TVOL=
19
20
21
22
23
________________/jtuss
24
Unicenter CA-Jobtrac Customization STAGE1 Parameters

This topic lists values to use with the customization STAGE1 parameters. Item 25 Parameter Description What unit do you want to use for dynamically allocated work files? Default: SYSDA What block size do you want to use for LRECL 80 PDS files? Default: 6080 Would you like to have the STEPLIBs for the Unicenter CA-Jobtrac and CA-Datacom/AD libraries commented in the generated JCL? If you do not plan to have these products' loadlibs in the linklist, set this option to N. Default: Y What high-level qualifier did you select previously for your SMP/E target libraries? Reference: #1 Default: CAI What is the fully qualified name of your Unicenter CA-Jobtrac SAMPJCL library? Default: &INDX.JT.SAMPJCL On what volume should the Unicenter CA-Jobtrac installation library be allocated? Default: None What is the JES command character that is used on your system? Default: $ What is the fully qualified name of the proclib where the Unicenter CA-Jobtrac procedures will be installed? Default: &INDX.JT.CAIPROC Your Value AUNIT=
26
BLK=
27
CMNTSTEP=
28
INDX=
29
INSTLIB=
30
INSTVOL=
31
JESCMD=
32
PROCLIB=
Item 33
Parameter Description What is SMFID of the system that will be the primary (or only) submission system for Unicenter CA-Jobtrac? Default: None What SYSOUT class do you want to use in the jobs created by the STAGE1 generation? Default: * What Unicenter CA-Jobtrac token will be used? The token is a single character that identifies a Unicenter CA-Jobtrac system. Multiple Unicenter CA-Jobtrac systems may be run on the same systems, each with a unique token. Default: Y What is the fully qualified name of the JCL library that Unicenter CA-Jobtrac will use? If NEWSITE=Y, this file will be allocated. Default: None Recommended: &indx.JT.TRACJ000 What is the fully qualified name of the temporary JCL library that Unicenter CA-Jobtrac will use? If NEWSITE=Y, this file will be allocated. Default: None Recommended: &indx.JT.TRACT000 What DASD unit names do you want to use for the jobs created by the STAGE1 generation for all other files including work? Default: SYSDA for all What tape unit name do you want to use in the jobs created by the STAGE1 generation? Default: CART
Your Value SYSID=
34
SYSOUT=
35
TOKEN=
36
TRACJCL=
37
TRACTEMP=
38
UNITD=
39
UNITC=
JOB Statements
In this topic, the keywords specify values that are added to the JOB statements of the jobs that are created by the STAGE1 generation. Keywords with no default are omitted from the JOB statement if no value is specified. Item 40 Parameter Description What job names do you want to use for the four jobs that are run in the STAGE2 job? Defaults: JOBTJB01, JOBTJB02, JOBTJB03, JOBTJB04 What account code do you want to use for the jobs created by the STAGE1 generation? Default: 1 What job class do you want to use for the jobs created by the STAGE1 generation? Default: A Optional value for the GROUP JOB statement keyword. If specified, GROUP= is added to all the generated JOB statements. Default: Keyword is omitted What MSGCLASS do you want to use in jobs created by the STAGE1? Default: A What programmer name do you want to be used on the JOB statement in jobs created by the STAGE1 generation? Default: 'CA-JOBTRAC INSTALL' What JES priority do you want to use on the JOB statement for the jobs created by the STAGE1 generation? Default: Keyword is omitted Your Value JOBTJB01= JOBTJB02= JOBTJB03= JOBTJB04= ACCT=
41
42
CLASS=
43
GROUP=
44
MSGCLASS=
45
NAME=
46
PRTY=
Item 47
Parameter Description What restart definition do you want to use on the JOB statement for the jobs created by the STAGE1 generation? Default: Keyword is omitted What region size do you want to use on the JOB statement for the jobs created by the STAGE1 generation? Default: Keyword is omitted What TSO ID do you want to use on the JOB statement for the jobs created by the STAGE1 generation? Default: Keyword is omitted What run type do you want to use on the JOB statement for the jobs created by the STAGE1 generation? Values: HOLD, SCAN, blank Default: Keyword is omitted
Your Value RD=
48
REGION=
49
NOTIFY=
50
TYPRUN=
Database IDs
The CA-Datacom databases each have a unique numeric ID called a DBID. The basic installation of Unicenter CA-Jobtrac uses two DBIDs, one for the production database, and one for the forecast database. CA-Datacom has assigned DBID's 0161 and 0162 to Unicenter CA-Jobtrac. Unicenter CA-Jobtrac also accesses information in the CA-Datacom System Tables. Item 51 Parameter Description What database ID (DBID) will you use for the production Unicenter CA-Jobtrac database? Default: 0161 What database ID (DBID) will you use for the forecast Unicenter CA-Jobtrac database? Default: 0162 What is the CA-Datacom System Table database ID (DBID)? This is defined in the CA-Datacom startup parameter SYSTEMDBID. Unless you have changed this value, it is set to 1000. Default: 1000 Your Value DBID=
52
FDBID=
53
SDBID=
Database Allocation
The following topic specifies the parameters for allocating the databases for Unicenter CA-Jobtrac. Item 54 Parameter Description What is the high-level qualifier for the production Unicenter CA-Jobtrac database data areas? Default: None What is the high-level qualifier for the forecast database data areas? Default: None What DASD unit names do you want to use for the Unicenter CA-Jobtrac database? Default: SYSDA Your Value INDXJ=
55
INDXF=
56
UNITT=
How many primary and secondary cylinders do you want to allocate for the Unicenter CA-Jobtrac data areas? For more information, see Calculate Database Size on page 14. These values are used to allocate both production and forecast databases. Item 57 58 59 60 61 Parameter Description The Database Index Default: (90,2) The Event Data Area Default: (160,20) The History Data Area Default: (125,2) The Options Data Area Default: (120,2) The Staging Data Area Default: (5,1) Your Value CYLIXX= CYLEVT= CYLHIS= CYLOPT= CYLSTG=
On what volumes do you want to allocate the Unicenter CA-Jobtrac data areas and work areas? For more information, see Data Set Placement Considerations on page 46. Item 62 63 64 65 66 67 Parameter Description The Database Index Default: None The Event Data Area Default: None The History Data Area Default: None The Options Data Area Default: None The Staging Data Area Default: None The Forecast Database (All Areas) Default: None Utility Work files Default: None Your Value VOLIXX= VOLEVT= VOLHIS= VOLOPT= VOLSTG= VOLFORE=
68
VOLUTIL=
CA-Datacom/AD File Names

This topic lists values to use for CA-Datacom/AD file names. Item 69 Parameter Description What is the fully qualified file name for the CA-Datacom/AD CXX? Default: None What is the high-level qualifier for CA-Datacom/AD SMP/E target libraries? Default: None Your Value DBCXX=
70
INDXDB=
Sysout Capture
This topic lists values for sysout capture. Item 71 Parameter Description To what VOLSER do you want to allocate the sysout capture file? Default: None How many cylinders do you want to allocate to the sysout capture file? Default: 100 What DASD unit names do you want to use for the sysout capture file? Default: SYSDA Your Value ARCHVOL=
72
ASIZE=
73
UNITA=
Upgrading from r3.5

This topic lists values for upgrades. Item 74 Parameter Description If you are upgrading, you can set NEWSITE to N to use your existing TRACJ000, TRACS000, TRACT000, TRACMDS, TRACD000, CAPTURE, and DATELIB libraries. If Y is specified, these libraries are allocated. If you are using a different high-level qualifier from your existing r3.5 system and want a new set of libraries allocated, specify Y. Default: Y If you are upgrading from Unicenter CA-Jobtrac r3.5, what is the high-level qualifier for Unicenter CA-Jobtrac r3.5 SMP/E target libraries? Default: None Your Value NEWSITE=
75
INDX35=
Item 76
Parameter Description If you are upgrading, what is the fully qualified filename for your r3.5 checkpoint file? Default: None If you are upgrading, what is the fully qualified filename for your r3.5 history file? Default: None
Your Value CHECKPT=
77
HISTORY=
CPM
Critical Path Monitoring (CPM) is a common component that is included on the Unicenter CA-Jobtrac installation tape. If you are upgrading, you may have CPM already installed. If you do not have CPM installed, Step 18: (Optional) Install Critical Path Monitor (CPM) on page 108 directs you to install it. You can choose to decide now what high-level qualifier to use for the CPM libraries or wait to fill in this section after you have installed CPM. Item 78 Parameter Description Will you be using the CA CPM component? CA CPM is included on the Unicenter CA-Jobtrac installation tape. Default: N What is, or will be, the high-level qualifier for CPM SMP/E target libraries? Default: None Your Value CPM=
79
INDXCPM=
CA Common Services and CA-GSS

This topic lists values for CA Common Services and CA-GSS. Item 80 Parameter Description What is the high-level qualifier for the Easytrieve Common Service SMP/E target libraries? Default: None Your Value INDXEZ=
Item 81
Parameter Description What is the name of the CA Common Services CAILIB where CA-GSS was installed? This can be the same as INDXEZ. Default: None What is the fully qualified file name to be assigned to the Unicenter CA-Jobtrac ISET library? ISET libraries contain REXX programs used by CA-GSS. Default: None On what volume should the Unicenter CA-Jobtrac ISET library be allocated? Default: None Is the ISET name specified as ISET=keyword a new ISET? If Y, this ISET is allocated. Default: N
Your Value GSSLOAD=
82
ISET=
83
ISETVOL=
84
NEWISET=
Unicenter CA-11
This topic lists a value for Unicenter CA-11. Item 85 Parameter Description If you have Unicenter CA-11 installed in your environment, what is the high-level qualifier for Unicenter CA-11 SMP/E target libraries? Default: None Your Value INDX11=
Chapter 4. Installation Tasks

This section contains the following topics: Install CA Common Services . . . . . Install CA-Datacom/AD Preparing for Installation . . . . SAMPJCL Member Names . . Installation Sequence . . . . . Steps for All Installations . . . New Installation Phase . . . . Demonstration Phase . . . . . Post Installation Considerations Install Unicenter CA-Jobtrac .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
82 83 85 86 87 88 93 98 99 101
New SMP/E CSIs are created during the installation. You must install into new CSIs even if you have a previous release of Unicenter CA-Jobtrac installed. Changes in DLIB allocation prevent using the previous release's CSIs. This chapter explains how to install Unicenter CA-Jobtrac using the IBM SMP/E product. If you are not familiar with SMP/E, you should have an experienced SMP/E consultant available. CA Technical Support also answers questions about SMP/E installation options. Getting Help During Installation: Keep a copy of your installation listings during the installation process. If you need assistance during Unicenter CA-Jobtrac installation, contact CA Technical Support (see the information about contacting Technical Support at the beginning of this guide). Have your listings available when you call.
Chapter 4. Installation Tasks 81
Install CA Common Services
Install CA Common Services

You can skip this step if the required components were installed for another CA product. Unicenter CA-Jobtrac and CA-Datacom/AD require several common components from the CA Common Services installation tape. The following are described in more detail in CA Common Services on page 26. Using the CA Common Services Getting Started guide (available at http://supportconnect.ca.com/sc/documentation), install and configure the required components. CA PROFILE CA-C Runtime CA-Easytrieve Service CA-GREXX CA-GSS CA-XPS CAICCI r1.1 or r2.1 CAIENF CAIENF Utilities CAIRIM CAISDI/els CAIVPE ViewPoint
Install CA-Datacom/AD
You can skip this step if CA-Datacom/AD r11 or later is already installed. If you plan to share a CA-Datacom/AD MUF with another product or application, see Compatibility with CA-Datacom/AD on page 83. This documentation addresses new installations. For information about upgrades, see the CA-Datacom/AD documentation. CA-Datacom/AD is a no-charge version of the CA database product Advantage CA-Datacom/DB. CA-Datacom/AD has all of the functions of the full Advantage CA-Datacom/DB product except that CA-Datacom/AD does not allow the use of user-defined databases. SAMPJCL: In this topic, all references to SAMPJCL refer to the CA-Datacom/AD SAMPJCL data set. Compatibility with CA-Datacom/AD: Unicenter CA-Jobtrac can share a CA-Datacom/AD MUF with other applications or can have its own MUF. We recommend that Unicenter CA-Jobtrac has its own MUF for the following reasons: Unicenter CA-Jobtrac is a systems product that must be available 24x7. Other applications may require MUF shut down at times, which would make Unicenter CA-Jobtrac unusable. Unicenter CA-Jobtrac may impact performance of your existing CA-Datacom/AD (or Advantage CA-Datacom/DB) applications. Unicenter CA-11 can use the same MUF, since it is closely tied to scheduling and has a similar requirement.
CA-Datacom/AD Compatibility with Advantage CA-Datacom/DB: If you are an existing Advantage CA-Datacom/DB customer and are considering using your existing installation, consider the following: Your Advantage CA-Datacom/DB may not be at the correct maintenance level, and any maintenance that may need to be applied to support Unicenter CA-Jobtrac will also affect your existing Advantage CA-Datacom/DB systems. If you are not licensed for Advantage CA-Datacom/DB on all systems that will run Unicenter CA-Jobtrac, you may be limited in your options for moving the MUF to other systems. A database initialized using Advantage CA-Datacom/DB cannot be opened by a CA-Datacom/AD system. You still need a separate MUF as discussed previously in the topic Compatibility with CA-Datacom/AD. If you choose to use your Advantage CA-Datacom/DB, you can skip this step.
Prior to starting this installation, be sure to read the cover letter and any Product Information Packets (PIPs) delivered with the installation tape. You should also review the applicable items on the SupportConnect website. This chapter discusses, step-by-step, the procedures required to install, customize, and demonstrate CA-Datacom/AD r11 in the z/OS environment. Contents include: SAMPJCL member names Product options Installation sequence Steps for all installations New installation phase Demonstration phase Post-installation considerations
Before you perform any installation activity, retrieve member @AXWKSHT from the sample JCL PDS or refer to Chapter 3, Worksheets. These procedure parameters are required for all CA-Datacom/AD installations. Ensure that each parameter has a valid value. Note: The DBRIMPR module that actually installs the CA-Datacom/AD SVC issues several informational messages and error messages as needed. Refer to the Advantage CA-Datacom/DB Message Guide for these messages, their meanings, and any action you might need to take.
Preparing for Installation
Preparing for Installation

The procedures required for installation at your site depend on whether this is a first time installation, or an upgrade.
New Installations
If you are installing CA-Datacom/AD for the first time, read this guide carefully before you begin the installation process. Some pre-installation considerations apply directly to new installations. After completing the steps commonly required for all installations (see Steps for All Installations on page 88), complete the New Installation Phase on page 93. When you finish the last step, you have completed your new installation. Verify the successful installation of CA-Datacom/AD as shown in the Demonstration Phase on page 98.
Upgrading Existing Products

This guide does not include upgrade instructions. If you are upgrading, use the CA-Datacom/AD Installation and Maintenance Guide to install the r11 release. When you have completed the upgrade, return to this guide to complete the installation of Unicenter CA-Jobtrac starting at Install Unicenter CA-Jobtrac on page 101.
SAMPJCL Member Names
SAMPJCL Member Names

The SAMPJCL member names can be easily identified during any installation. These names are constructed as follows: 1. Each name begins with AX to identify CA-Datacom/AD. 2. The next three characters identify the type of installation step (one of the following): INS indicates an installation step performed for all installations. NEW indicates a step for new installations only. UPG indicates a step for upgrade installations from r10 only. FBK indicates a step for returning to the previous version environment after completing the upgrade jobs. IVP indicates a step you execute to verify the installation.
3. The remainder of each name indicates the number of the step and can include a suffix. If you have a job member that has a suffix along with a same-numbered job member that does not have a suffix, run the job member that has a suffix after the job member without a suffix is complete. R suffix indicates a restore of CA-Datacom/AD data sets from a previous backup step. X suffix indicates the step is conditional and is performed on in specific instances. Read the step description to determine whether to include it in your CA-Datacom/AD installation.
Installation Sequence
Installation Sequence
Sample jobs must be executed in sequential order by name and number. Be sure to review, edit, execute, and complete each installation step before proceeding to the next step. Follow these guidelines when installing: 1. SMP/E Installation Phase Execute members whose names start with AXINS for all installations. When all AXINS jobs have executed successfully, the SMP/E phase of the product installation is complete. 2. New Installation Phase If you are installing CA-Datacom/AD for the first time, execute the members whose names start with AXNEW. After all AXNEW jobs have executed successfully, the CA-Datacom/AD r11 environment is ready for use. 3. Install Verification Phase Execute members whose names start with AXIVP. When the AXIVP jobs have executed successfully, the CA-Datacom/AD r11 sample execution is complete. 4. Post Installation Phase Make any CICS modifications necessary for your specific site. Verify the installation using Datadictionary online and Advantage CA-Dataquery.
Steps for All Installations

This is the SMP/E installation phase. These are the common steps performed by all installations. Each step must be complete before you begin the next step. For this phase of the installation, retrieve the SAMPJCL PDS members whose names start with AXINS. The following is a comprehensive list of all possible steps: Step 1 Description Enter and submit the AXINS01 SAMPJCL JCL member. Purpose Create the CA-Datacom/AD SAMPJCL library from which you receive members to complete the installation.
If you plan to run CBIPO (see Edit JCL on page 36), do so before beginning the next step. 2 Retrieve AXINS02 from SAMPJCL, perform changes as directed and submit the JCL. Retrieve AXINS03 from SAMPJCL, perform changes as directed and submit the JCL. Retrieve AXINS04 from SAMPJCL, perform changes as directed and submit the JCL. Retrieve AXINS05 from SAMPJCL, perform changes as directed and submit the JCL. Allocates and downloads the SMP/E and other required data sets. Renames the predefined DDDEFs in the SMP/E CSI to conform with your site standards. Perform CA-Datacom/AD product custom assemblies. Load the CA-Datacom/AD SVC using CAIRIM.
Step 1. Allocate the SAMPJCL Library

The sample JCL (SAMPJCL) library created in this step contains the JCL you need to complete all subsequent installation steps. The JCL you submit executes IEFBR14 (to allocate your SAMPJCL PDS) and IEBCOPY (to load the SAMPJCL library from tape to disk). To allocate the SAMPJCL library: 1. 2. 3. 4. Use the sample JCL to create the SAMPJCL library. Make all required changes for your site as shown. Submit the JCL to complete this step. Review the output for successful completion. The expected condition code is 00.
Note: You get the internal VOLSER from the external label on the tape. If there is an abend, correct the JCL and repeat the job. This entire job can be repeated provided you either delete the SAMPJCL data set that was allocated in this job, or change the high-level qualifier of the SAMPJCL data set.
Sample JCL
// //SAMPJCL PROC AXSHLQ='CAI.SHLQ', WORKSHEET #2 // AXVOL1='VOL=SER=DASD 1', WORKSHEET #7 // AXUNI1=339 , WORKSHEET #9 // AXITVOL=AX11SS, WORKSHEET #24 // AXITUNI=TAPE, WORKSHEET #25 // SYSOUT=' ' // // ALLOCATE AND COPY SAMPJCL LIBRARY // //COPYJCL EXEC PGM=IEBCOPY,REGION=1 24K //SYSPRINT DD SYSOUT=&SYSOUT //SYSUT3 DD UNIT=SYSDA,SPACE=(CYL,(1,1)), // DISP=(MOD,DELETE,DELETE) //SYSUT4 DD UNIT=SYSDA,SPACE=(CYL,(1,1)), // DISP=(MOD,DELETE,DELETE) //INDD DD DSN=CAI.SAMPJCL,DISP=OLD, // UNIT=&AXITUNI,LABEL=(9,SL), // VOL=SER=&AXITVOL //OUTDD DD DSN=&AXSHLQ..SAMPJCL, // DISP=(NEW,CATLG),DSNTYPE=PDS, // UNIT=&AXUNI1,SPACE=(TRK,(4 ,2 ,3 )),&AXVOL1, // DCB=(DSORG=PO,RECFM=FB,LRECL=8 ,BLKSIZE=312 ) // // PEND // // EXECUTE SAMPJCL PROC // //STEP1 EXEC SAMPJCL // //COPYJCL.SYSIN DD COPY OUTDD=OUTDD,INDD=INDD / //
Change the values for the SAMPJCL PROC statements to the values of the Worksheet numbers noted. Code all statements to your site and installation standards. Important! If you plan to run CBIPO (see Edit JCL on page 36), do so before beginning the next step.
Step 2. Download Libraries

Note: This step uses the install tape. This step allocates and downloads the CA-Datacom/AD SMP/E and other required data sets. CA-Datacom/AD has been pre-installed using SMP/E so that it is not necessary during the initial installation of the release until maintenance is required. To download libraries: 1. 2. 3. 4. Retrieve member AXINS02 from your SAMPJCL PDS. Make the required global changes (see the instruction block). Submit the JCL to complete this step. Review the output for successful completion. The expected condition code is 00.
If there is an abend, correct the JCL and repeat the job. This entire job can be repeated. However, any PDS members that have been previously copied are not replaced and results in a condition code other than 00.
Step 3. Rename SMP/E DDDEFs

This step executes GIMSMP to rename the predefined DDDEFs in the SMP/E CSI to your site-specific data set names. To rename SMP/E DDDEFs: 1. 2. 3. 4. Retrieve member AXINS03 from your SAMPJCL PDS. Make the required global changes (see the instruction block). Submit the JCL to complete this step. Review the output for successful completion. The expected condition code is LE 04.
Note: Make certain that the zone names do not change. See CA-Datacom/AD Product Installation on page 39 for more information. If there is an abend, correct the job and repeat. This job can be repeated at any time.
Step 4. Prepare the CA-Datacom/AD Custom Assemblies

This step prepares the CA-Datacom/AD customized assemblies. To prepare the CA-Datacom/AD custom assemblies: 1. 2. 3. 4. Retrieve member AXINS04 from your SAMPJCL PDS. Make the required global changes (see the instruction block). Submit the JCL to complete this step. Review the output for successful completion. The expected condition code is LE 04.
Review all of the CA-Datacom/AD startup option statements in the job step that adds the Multi-User Facility startup PARMs member DBDATIN1 to the CUSMAC PDS. Refer to the Advantage CA-Datacom/DB Database and System Administrator Guide for a list of the Multi-User startup option that might be applicable to your installation. If any step in this job abends, correct the problem and repeat the job. This job can be repeated at any time.
Step 5. Load CA-Datacom/AD SVC Using CAIRIM

This step loads the CA-Datacom/AD SVC using CAIRIM. Be sure to review Install a User SVC for CA-Datacom/AD on page 31 before running this step. To load the CA-Datacom/AD SVC using CAIRIM: 1. 2. 3. 4. Retrieve member AXINS05 from your SAMPJCL PDS. Make the required global changes (see the instruction block). Submit the JCL to complete this step. Review the output for successful completion. The expected condition code is 00.
This job can be repeated. However, repeated executions can require changes to the CAIRIM command statements. Review the section on installing an SVC before repeating. We recommend that this job be incorporated into your site-standard CAS9 procedure so that the CA-Datacom/AD SVC is automatically installed after an IPL.
New Installation Phase

The following is a comprehensive list of all possible steps for a new installation only. If this is your first time installing CA-Datacom/AD, perform these steps after completing those required by all installations. For this phase of the installation, run the SAMPJCL PDS members whose names start with AXNEW. Step 1 Description Retrieve AXNEW01 from SAMPJCL, perform the changes as directed, and submit the JCL. Retrieve AXNEW02 from SAMPJCL, perform the changes as directed, and submit the JCL. Retrieve AXNEW03 from SAMPJCL, perform the changes as directed, and submit the JCL. Retrieve AXNEW04 from SAMPJCL, perform the changes as directed, and submit the JCL. Retrieve AXNEW05 from SAMPJCL, perform the changes as directed, and submit the JCL, after starting the Multi-User Facility. Retrieve AXNEW06 from SAMPJCL, perform the changes as directed, and submit the JCL. Retrieve AXNEW07 from SAMPJCL, perform the changes as directed, and submit the JCL. Retrieve AXNEW08 from SAMPJCL, perform the changes as directed, and submit the JCL. Purpose Add the backup/load/initialize PROC members and allocate backup files. Allocate the CA-Datacom/AD database data sets.
Initialize and load the CXX, LXX, and the CA-Datacom/AD database data sets. Start the Multi-User Facility.
Update Datadictionary, reset the Datadictionary HSD file, and populate the Advantage CA-Dataquery database and CASYSTEMTABLES. Back up the CA-Datacom/AD r11 databases.
Shut down the Multi-User Facility.
Delete unneeded files after installation is complete.
Step 1. Add BACKUP/LOAD/INIT PROC Members

This step adds the backup, load, and initialize CUSPROC members and allocates backup and VLS data sets. To add BACKUP/LOAD/INIT PROC members: 1. 2. 3. 4. Retrieve member AXNEW01 from your SAMPJCL PDS. Make the required global changes (see the instruction block). Submit the JCL to complete this step. Review the output for successful completion. The expected condition code is 00.
If there is an abend, correct the JCL and repeat the job. This entire job can be repeated provided you either delete the data sets that were allocated in this job, or change the high-level qualifier for these data sets.
Step 2. Allocate CA-Datacom/AD Data Sets

This step executes IEFBR14 to allocate the CA-Datacom/AD database data sets. To allocate CA-Datacom/AD data sets: 1. 2. 3. 4. Retrieve member AXNEW02 from your SAMPJCL PDS. Make the required global changes (see the instruction block). Submit the JCL to complete this step. Review the output for successful completion. The expected condition code is 00.
If there is an abend, correct the JCL and repeat the job. This entire job can be repeated provided you either delete the data sets that were allocated in this job, or change the high-level qualifier for these data sets. If you want to repeat the job starting at a certain job step which had previously abended, resubmit the job, modifying the job card to include a RESTART parameter such as:
RESTART=STEP2.xxxx
Where xxxx is the stepname in the PROC. Be sure you have reviewed, edited, executed, and completed this step before continuing.
Step 3. Initialize and Load the CXX, LXX, and Databases

This step executes DBUTLTY to initialize and load the Directory (CXX), Log Area (LXX), and Datadictionary database. To initialize and load the CXX, LXX, and databases: 1. 2. 3. 4. Retrieve member AXNEW03 from your SAMPJCL PDS. Make the required global changes (see the instruction block). Submit the JCL to complete this step. Review the output for successful completion. The expected condition code is 00.
If any step in this jobs abends, correct the problem and repeat the job. This job can be repeated at any time. However, if this job is repeated after running any subsequent jobs, (for example, AXNEW05), all subsequent jobs must be repeated as well. The Multi-User Facility must not be active when this job is run.
Step 4. Start the MUF

This step executes DBMUFPR to start the Multi-User Facility. To start the MUF: 1. Retrieve member AXNEW04 from your SAMPJCL PDS. 2. Make the required global changes (see the instruction block). 3. Submit the JCL to complete this step. Note: This job remains active throughout the rest of the install and demonstration steps. Code the class parameter in your job card per your site requirements. Review, edit, and execute this step before continuing.
Step 5. Run DDUPDATE, DDCFBLD, DBUTLTY INIT, and Populate DQ

This step does the following: Executes DDUPDATE to update Datadictionary, then executes DDCFBLD to reset the Datadictionary HSD file Executes DBUTLTY to initializes the CASYSTEMTABLES and HISTORY databases Populates the Advantage CA-Dataquery database.
You must start the Multi-User Facility prior to running this step. The Multi-User Facility must be available for the rest of the installation and demonstration steps. When required, the Multi-User Facility can be terminated using SAMPJCL member AD11STOP. To run DDUPDATE, DDCFBLD, DBUTLTY INIT, and Populate DQ: 1. 2. 3. 4. Retrieve member AXNEW05 from your SAMPJCL PDS. Make the required global changes (see the instruction block). Submit the JCL to complete this step. Review the output for successful completion. The expected condition code is 00. Note: If you receive a condition code 08 on this job because of Datadictionary numbered message DDPNTF0003, indicating that in a -DEL header transaction you specified an entity-occurrence that does not exist in Datadictionary, go to the next install job. If you receive a condition code 08 on this job because of an error other than Datadictionary numbered message DDPNTF0003, review the output to determine what corrective action to take. If any step in this job abends, correct the problem and repeat the entire job. This job can be repeated at any time as needed.
Step 6. Back Up CA-Datacom/AD Databases

This step executes DBUTLTY to back up the CA-Datacom/AD databases (CXX, 002, 003, 015). To back up CA-Datacom/AD databases: 1. 2. 3. 4. Retrieve member AXNEW06 from your SAMPJCL PDS. Make the required global changes (see the instruction block). Submit the JCL to complete this step. Review the output for successful completion. The expected condition code is 00.
If any step in this job abends, correct the problem and repeat the entire job. This job can be repeated at any time as needed.
Step 7. Shut Down the MUF

(Optional.) This step executes DBUTLTY to shutdown the Multi-User Facility. You can optionally skip this step and continue to the demonstration steps. To shut down the MUF: 1. 2. 3. 4. Retrieve member AXNEW07 from your SAMPJCL PDS. Make the required global changes (see the instruction block). Submit the JCL to complete this step. Review the output for successful completion. The expected condition code is 00.
Step 8. Remove Unneeded Installation Files

(Conditional.) This step removes all files that are no longer needed after the installation is complete. Note: Do not run this job until any CICS or other post-installation jobs have been completed. To remove unneeded installation files: 1. 2. 3. 4. Retrieve member AXNEW08 from your SAMPJCL PDS. Make the required global changes (see the instruction block). Submit the JCL to complete this step. Review the output for successful completion. The expected condition code is 00.
Demonstration Phase
Demonstration Phase
When you have finished all installation steps for your site, execute the following jobs to demonstrate successful product installation for batch processing. The SAMPJCL job member names begin with AXIVP and must be performed in the following sequence.
Step 1. Start Up the MUF

As in the installation steps, edit and submit AD11STRT from the SAMPJCL library. This executes DBUTLTY and DBMUFPR to startup the Multi-User Facility.
Step 2. Execute Sample CA-Datacom/AD Programs

Edit and submit SAMPJCL member AXIVP01. This executes multiple programs for CA-Datacom/AD execution. Note: Ignore message code CSV003I if it appears.
Step 3. Execute Sample Dynamic SQL Programs

Edit and submit AXIVP02. This executes a dynamic SQL program for CA-Datacom/AD.
Step 4. Shut Down the MUF

Edit and submit SAMPJCL member AD11STOP. This executes DBUTLTY to shut down the Multi-User Facility. When this is complete, you have verified successful installation of this product.
Post Installation Considerations

The following are post installation considerations.
Set up Production Jobs

SAMPJCL members AD11STRT, AD11STOP, AD11LXXS, and AD11PXXR can be used to set production jobs for your site which are required on a daily basis to run the CA-Datacom/AD environment. You might want to make these jobs standard PROCs or started tasks for your site. SAMPJCL member AD11STRT starts up the CA-Datacom/AD environment. This job is a long running task that should be submitted to a job class without a time or CPU limit. This environment must be available for any access to the CA-Datacom/AD databases. Note: You should run the AD11STRT job/STC (where STC refers to a Started Task) at a priority just under the priority of the JES subsystem if CA-Datacom/AD is being utilized with another CA system product such as Unicenter CA-11 or Unicenter CA-Scheduler. SAMPJCL member AD11STOP shuts down the CA-Datacom/AD environment. SAMPJCL member AD11LXXS spills the inactive Log Area (LXX) records to a Recovery File. If the CA-Datacom/AD Log Area fills up, update processing against the MUF is stopped until the records are spilled. SAMPJCL member AD11PXXR prints out the Statistics and Diagnostics Area (PXX) that can be used for tuning or debugging purposes. A PXX report is also printed during the shutdown of the Multi-User Facility. SAMPJCL member AD11BKUP backs up the CA-Datacom/AD Directory (CXX) and databases to tape. SAMPJCL member AD11LOAD restores the backed-up CXX and databases from tape.
Multi-User Facility Tuning

CUSMAC member DBDATIN1 and CAIMAC member DBDATIN2 contain the startup and tuning parameters required by the Multi-User Facility at startup. Although the parameters in DBDATIN2 normally would not be changed, they can be changed as required to optimize the execution of the Multi-User Facility. See the Advantage CA-Datacom/DB Database and System Administrator Guide for more information about these parameters. Also see the CA-Datacom/AD Implementation Guide.
Run the MUF as a Started Task

You can, if preferred, run the Multi-User Facility (MUF) as a started task. To run the MUF as a started task: 1. Move the AD11STRT procedure from the CUSPROC library to the system procedure library. 2. Enter the following console command:
S AD11STRT
In the previously shown console command, 6M is the default region size. This region size can be modified as needed.
Install Unicenter CA-Jobtrac

Now that you have installed CA Common Services and CA-Datacom/AD, it is time to install Unicenter CA-Jobtrac. During the following steps, you download the Unicenter CA-Jobtrac SAMPJCL and run the jobs included in the SAMPJCL to install Unicenter CA-Jobtrac. During this process, refer to your Unicenter CA-Jobtrac worksheets completed in the previous chapter. Unless stated otherwise, all references to SAMPJCL in this section refer to the Unicenter CA-Jobtrac SAMPJCL.
Step 1: Allocate and Load the SAMPJCL Library

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

Product documentation is delivered in Adobe Acrobat format. The SAMPJCL library includes a member to unload the documentation from the installation tape in Adobe Acrobat format. To unload the documentation from the installation tape, refer to SAMPJCL member ADOBEDOC. The documentation is also available on the SupportConnect web site.
Step 3: Create SMP/E Libraries

This step creates all the SMP/E libraries and defines the SMP zones. Member CAINITE5 in your Unicenter CA-Jobtrac SAMPJCL library contains the JCL for this step. 1. Review the JCL in the CAINITE5 procedure. 2. Modify the JCL parameters to meet your installation's needs. 3. Run the CAINITE5 job to create the SMP/E libraries. You should receive a completion code of 04. New SMP/E CSIs are created during the installation. You must install into new CSIs even if you have a previous release of Unicenter CA-Jobtrac installed. Changes in the SMP/E packaging structure prevent using the previous release's CSIs. Do not install into the same SMP/E environment as CA-Datacom/AD. CA-Datacom/AD uses a replacement maintenance methodology that conflicts with Unicenter CA-Jobtrac.
Step 4: Create the Target and Distribution Libraries

This step creates all the SMP/E target and distribution libraries for Unicenter CA-Jobtrac. Member HD11ALC in your Unicenter CA-Jobtrac SAMPJCL library contains the JCL for this step. 1. Review the JCL in the HD11ALC procedure. 2. Modify the JCL parameters to meet your installation's needs. 3. Run the HD11ALC job to create the SMP/E target and distribution libraries. You should receive a completion code of 0 (zero).
Step 5: Create SMP PROC

This step sets up the SMP/E PROC that will be used for all SMP/E processing. Member CAIHD11 in your Unicenter CA-Jobtrac SAMPJCL library contains the JCL for this step. 1. Edit CAIHD11 in SAMPJCL. 2. Modify the PROC parms to specify required parameters. Do not change the PTF='DUMMY,' parameter. 3. Verify the macro libraries specified on the SYSLIB DDNAME. 4. Save the changes and move the CAIHD11 PROC into an available proclib.
Step 6: Perform RECEIVE Processing

This step performs RECEIVE processing for the Unicenter CA-Jobtrac base FMID and all its functions. Member HD11REC in your Unicenter CA-Jobtrac SAMPJCL library contains the JCL for this step. 1. Review the JCL in the HD11REC procedure. 2. Modify the JCL parameters to meet your installation's needs. 3. Run the HD11REC job to perform RECEIVE processing. You should receive a completion code of 0 (zero).
Step 7: Perform APPLY Processing

This step performs APPLY processing for Unicenter CA-Jobtrac. Member HD11APP in your Unicenter CA-Jobtrac SAMPJCL library contains the JCL for this step. 1. Review the JCL in the HD11APP procedure. 2. Modify the JCL parameters to meet your installation's needs. 3. Run the HD11APP job to perform APPLY processing. Ensure you receive a completion code of 0 (zero) or 4.
Step 8: Perform ACCEPT Processing

This step performs ACCEPT processing for Unicenter CA-Jobtrac. Member HD11ACC in your Unicenter CA-Jobtrac SAMPJCL library contains the JCL for this step. 1. Review the JCL in the HD11ACC procedure. 2. Modify the JCL parameters to meet your installation's needs. 3. Run the HD11ACC job to perform ACCEPT processing. You should receive a completion code of 0 (zero) or 4.
Step 9: Ensure APF Authorization

Important! Unicenter CA-Jobtrac modules must be executed from an APF-authorized library. Add the CAI CAILIB to the APFLIST or use IEBCOPY to move the Unicenter CA-Jobtrac modules from the installation CAILIB to an appropriate library and perform an LLA REFRESH if needed. Note: CA-GSS CAILIB must be APF-authorized for the STAGE2 jobs to run.
Step 10: Update License Management Program (LMP) Key

This product is in compliance with CA License Management Program (LMP). As a result, the PDS member referenced by the KEYS DD statement in the CAS9 procedure must be updated with the information supplied on the LMP Key Certificates for both Unicenter CA-Jobtrac and CA-Datacom/AD. The LMP Key Certificates are included as part of your distribution package. For more information about installing and tailoring the Unicenter CA-Jobtrac LMP Execution Key, see the CA Common Services Administrator Guide.
Step 11: Update CAIENF Database

SAMPJCL member HD11ENF defines events to CAIENF and makes them active. CAIENF must be shut down to run the job. Do not restart it until so instructed in Step 13: Start CAIENF on page 106. Follow the directions in the SAMPJCL member to tailor the job and submit it. The job should end with a return code of zero.
Step 12: CAIENF Startup Options

SAMPJCL member ENFPARMS contains sample CAIENF startup options. ENFPARMS can be merged into the existing CAIENF startup options. Use care, since Unicenter CA-Jobtrac may not be the only CA product using CAIENF. For information about the CAIENF startup options, see the CA Common Services Administrator Guide.
Step 13: Start CAIENF

Start (or restart) CAIENF. If you are restarting CAIENF, use the following REINIT option: S CAIENF,,,REINIT
Step 14: Create a Dummy IEAVMXIT Exit

To use the Automatic Message Recognition (AMR) feature of Unicenter CA-Jobtrac, an IEAVMXIT exit must exist in your SYS1.LINKLIB data set. Verify that this module is present. If you do not have this module, use job LINKMXIT in the SAMPJCL library to create a dummy exit. For more information, see Set Up AMR Support on page 208.
Step 15: (Optional) Install eTrust CA-Examine Interface

eTrust CA-Examine audits the z/OS operating system and reports its findings to the customer. Unicenter CA-Jobtrac has an interface to this product that is a load module residing in the Unicenter CA-Jobtrac load library (CAI.CAILIB). If eTrust CA-Examine is installed at your site, part of the install process moves the interface module, CAIXCHD$, from the Unicenter CA-Jobtrac load library to the LPA library.
Step 16: (Optional) Link AllFusion CA-Panvalet Modules

This step relinks the Unicenter CA-Jobtrac modules so that they include the AllFusion CA-Panvalet access method modules. If you are not using Unicenter CA-Jobtrac to submit JCL from AllFusion CA-Panvalet, skip this step. Member HD11LPAN in your Unicenter CA-Jobtrac SAMPJCL library contains the JCL for this step. 1. Review the JCL in the HD11LPAN procedure. 2. Modify the JCL parameters to meet your installation's needs. 3. Run the HD11LPAN job to link the AllFusion CA-Panvalet modules. You should receive a completion code of 0 (zero).
Step 17: (Optional) Link AllFusion CA-Librarian Modules

This step relinks the Unicenter CA-Jobtrac modules so that they include the AllFusion CA-Librarian access method modules. If you are not using Unicenter CA-Jobtrac to submit JCL from AllFusion CA-Librarian, skip this step. Member HD11LLIB in your Unicenter CA-Jobtrac SAMPJCL library contains the JCL for this step. 1. Review the JCL in the HD11LLIB procedure. 2. Modify the JCL parameters to meet your installation's needs. 3. Run the HD11LLIB job to link the AllFusion CA-Librarian modules. You should receive a completion code of 0 (zero).
Step 18: (Optional) Install Critical Path Monitor (CPM)

CA Critical Path Monitor (CPM) is included with the installation tape in separate files. CA CPM provides the tools to monitor Unicenter CA-Jobtrac critical path job flows. These flows can be viewed using the CA CPM ISPF application that is integrated with the Unicenter CA-Jobtrac. The Unicenter CA-Jobtrac CPM command can be used to invoke these panels. The CA Critical Path Monitor Version 3.0 User Guide is included in the documentation for Unicenter CA-Jobtrac. This document includes information about installing and using CPM. The SAMPJCL member CPMJCL in the Unicenter CA-Jobtrac SAMPJCL creates a separate CA CPM SAMPJCL library that will be used to install and maintain CA CPM. We recommend that you install CA CPM or update the maintenance for your existing CA CPM at this time. 1. If installing, modify and submit CPMJCL in the Unicenter CA-Jobtrac SAMPJCL. This job creates a separate SAMPJCL data set for CA CPM. The CA CPM SAMPJCL library contains jobs required to install CA CPM. 2. CA CPM installation or maintenance procedures must be performed as described in the CA Critical Path Monitor Version 3.0 User Guide. 3. Retain CPM install data set information. This needs to be specified later in the Stage1 job described in Chapter 5, Customization Job Streams on page 111.
Step 19: (Optional) Install the @JOBTRAC USS Command

The Unicenter CA-Jobtrac module JTUSS can be used to access Unicenter CA-Jobtrac from IBM's UNIX System Services using the @JOBTRAC commands currently used with CA-GSS and GJTRABTR. 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. The object for the module is distributed in CAIMAC. The SAMPJCL member HD11LUSS contains JCL to perform the link. Customize the JCL for your environment and submit it to install the command. Remembering that UNIX is case-sensitive, be sure to specify the path for the command in the correct case. The HD11LUSS member contains instruction for customizing the JCL. Note: For more information about using the command and UNIX, see the Extended Scheduling Services Guide.
Step 20: (Optional) Install the JES2 Hold Usermod

If you use JES3, this step does not apply. Unicenter CA-Jobtrac provides a USERMOD for customers that use JES2 and are using the AUTO-SCHD feature. AUTO-SCHD jobs are submitted from outside of Unicenter CA-Jobtrac and may be held in the JES2 input queue until the jobs requirements have been met. Traditionally, Unicenter CA-Jobtrac has used the $HJ command to hold jobs during job conversion, but later releases of JES2 delay the commands processing and can let the job start running before the command is processed. Applying USERMOD UM00001 lets Unicenter CA-Jobtrac hold jobs by setting flags directly in the JES2 control blocks. Member HD11JES2 in your Unicenter CA-Jobtrac SAMPJCL library contains the JCL for this step. 1. Review the JCL 2. Modify the JCL parameters as indicated, and as needed to meet your installation's needs. 3. Run the HD11JES2 job to apply the UM00001 USERMOD to Unicenter CA-Jobtrac. You should receive a completion code of 00. Note: For more information about the AUTO-SCHD feature, see the Operator Guide.
Chapter 5. Customization Job Streams

This section contains the following topics: STAGE1 Customization Job . STAGE2 Installation Job Stream
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
112 118
The following phases are necessary to customize, set up, and implement Unicenter CA-Jobtrac: STAGE1 customization job stream - Covered in this chapter STAGE2 installation job stream - Covered in this chapter Customization tasks - Covered in the chapter "Customization Tasks" Startup and verification tasks - Covered in the chapter "Startup and Verification"
The STAGE1 customization job stream invokes an installation macro called TRACMAC, which generates the STAGE2 installation job stream. The TRACMAC macro contains statements you use to name libraries and their locations, and to provide information for the STAGE2 job stream. For more information, see STAGE1 Customization Job on page 112. The STAGE2 job stream is necessary to install Unicenter CA-Jobtrac. The STAGE2 job stream allocates Unicenter CA-Jobtrac data sets, updates your system-cataloged procedure library, and provides the installation verification procedure for Unicenter CA-Jobtrac. For more information, see STAGE2 Installation Job Stream on page 118. The STAGE1 customization job stream invokes an installation macro called TRACMAC, which generates the STAGE2 job stream. The STAGE2 job stream is necessary to install Unicenter CA-Jobtrac. The member STAGE1 in your SAMPJCL library is a sample of the assembler JCL needed to create the STAGE2 job stream. The STAGE1 job writes the STAGE2 job stream to the data set or PDS member that you specify (default is the SAMPJCL). The STAGE2 job stream contains procedure updates, an installation verification procedure, and JCL to allocate remaining Unicenter CA-Jobtrac libraries.
Chapter 5. Customization Job Streams 111
STAGE1 Customization Job

The STAGE1 customization job stream invokes an installation macro called TRACMAC. TRACMAC defines numerous global values used to install Unicenter CA-Jobtrac and generate the STAGE2 job stream. The STAGE2 job stream is created by incorporating all the variables specified in the STAGE1 customization. Four separate jobs are created, which can be individually named by using the JOBNAMx variables: JOBNAM1 Creates and initializes the entire CA-Datacom/AD database environment. JOBNAM2 Creates and initializes the non-database files. JOBNAM3 Primarily creates the tailored run procedures and puts them into the PROCLIB. JOBNAM4 Primarily creates the tailored individual jobs needed to support the maintenance of Unicenter CA-Jobtrac and puts them into the SAMPJCL specified.
Run the STAGE1 Job

Follow these steps to run the STAGE1 job stream: 1. Edit member STAGE1 in the SAMPJCL library. 2. Review the JCL carefully, making revisions to reflect your installation's requirements. 3. Edit the STAGE1 parameter values to meet your installation requirements (see Required TRACMAC Parameters on page 113, and Optional TRACMAC Parameters on page 116). Note: By using the CMNTSTEP variable, you can select whether job step execution occurs for specified STEPLIBs or system default load libraries. This may be helpful depending on how you select to set up your installation process. 4. Be sure to specify your CAIMAC macro library in the SYSLIB DD statement. 5. Run the STAGE1 job to create the STAGE2 job stream. 6. Verify that the assembler return code from the STAGE1 job is 0 (zero). If the return code is not 0, review the assembler output for messages that indicate what caused the error. A possible cause is bad or missing parameters. Another common cause is changing a parameter and omitting the comma. All parameters except the last one should be followed by a comma.
Required TRACMAC Parameters

The following describes the TRACMAC parameters that you must include (with defaults underlined): ARCHVOL= Defines the volser of the volume on which the sysout capture file is to reside. This volume must contain enough contiguous space to satisfy the ASIZE= parameter. ASIZE=100 Defines the size in cylinders of the sysout capture file. This value must be at least 5. CMNTSTEP=Y Specifies whether to comment the //STEPLIB DD statements in the generated JCL. Y Specifies to comment the //STEPLIB DD statements. N Specifies not to comment the //STEPLIB DD statements. CYLEVT='160,20' Defines the primary,secondary cylinder size for the EVT CA-Datacom/AD area allocation on the volume specified by VOLEVT. CYLHIS='125,2' Defines the primary,secondary cylinder size for the HIS CA-Datacom/AD area allocation on the volume specified by VOLHIS. CYLIXX='90,2' Defines the primary,secondary cylinder size for the IXX CA-Datacom/AD area allocation on the volume specified by VOLIXX. CYLOPT='120,2' Defines the primary,secondary cylinder size for the OPT CA-Datacom/AD area allocation on the volume specified by VOLOPT. CYLSTG='5,1' Defines the primary,secondary cylinder size for the STG CA-Datacom/AD area allocation on the volume specified by VOLSTG. DBCXX= Defines the high and mid-level name of the installation's CA-Datacom/AD .CXX control file. DBID=0161 Defines the CA-Datacom/AD DBID that uniquely identifies the production database. FDBID=0162 Defines the CA-Datacom/AD DBID that uniquely identifies the forecast database.
INDX=CAI Defines the Unicenter CA-Jobtrac installation library high- and mid-level qualifier to be used during allocation. INDXDB= Defines the high and mid-level qualifier of the CA-Datacom/AD system files (CAILIB and CUSLIB). INDXEZ= Defines the high and mid-level qualifier of the CA-Easytrieve system file (CAILIB). INDXF= Defines the high and mid-level qualifier of the Unicenter CA-Jobtrac forecast database CA-Datacom/AD area files. INDXJ=CAI Defines the high-level qualifier for the CA-Datacom/AD areas containing the Unicenter CA-Jobtrac database. INSTVOL=10 Defines the VOLSER of the volume (INSTLIB) into which the STAGE2 job is to place all Unicenter CA-Jobtrac installation libraries. ISET= Defines the fully-qualified data set name of the IMOD ISET into which Unicenter CA-Jobtrac sample and required production IMODs will be installed. For information about IMODs and ISETs, see the CA Common Services documentation. JOBNAM1=JOBTJB01 Defines the job name to appear on the JOB statement of the first job, database setup. JOBNAM2=JOBTJB02 Defines the job name to appear on the JOB statement of the second job, non-database file setup. JOBNAM3=JOBTJB03 Defines the job name to appear on the JOB statement of the third job, PROCLIB setup. JOBNAM4=JOBTJB04 Defines the job name to appear on the JOB statement of the fourth job, SAMPJCL setup. NAME='CA-JOBTRAC INSTALL' Defines the STAGE2 job stream programmer name field. NEWSITE=Y Defines whether this is a new installation. New installations should specify Y. Reinstallations will not reallocate runtime libraries if N is used. SDBID=1000 Defines the CA-Datacom/AD DBID that uniquely identifies the CA-Datacom/AD system files used by Unicenter CA-Jobtrac.
SYSID= Defines the SMF ID of your primary Unicenter CA-Jobtrac system. The primary system is the system on which all batch work will be submitted. TOKEN=Y Defines the Unicenter CA-Jobtrac system ID identifying the copy of the system. TRACJCL= Defines the name of the library that is to contain the production JCL. TRACTEMP= Defines the name of the library that is to contain the temporary-use JCL. UNITA=SYSALLDA Defines the unit specification for the sysout capture file. For related information, see the ARCHVOL parameter. UNITC=CART Defines the unit specification for the tape device on which to take database backups. UNITD=SYSALLDA Defines the unit specification for all remaining installation libraries and data sets. For related information, see the INSTVOL parameter. UNITT=SYSALLDA Defines the unit specification for the Unicenter CA-Jobtrac production database and the forecast CA-Datacom/AD database areas. VOLEVT= Defines the VOLSER that the EVT area is to reside on. VOLFORE= Defines the VOLSER that the forecast database is to reside on. VOLHIS= Defines the VOLSER that the HIS area is to reside on. VOLIXX= Defines the VOLSER that the IXX area is to reside on. VOLOPT= Defines the VOLSER that the OPT area is to reside on. VOLSTG= Defines the VOLSER that the STG area is to reside on. VOLUTIL= Defines the VOLSER that space used by CA-Datacom/AD utilities is to reside on.
Optional TRACMAC Parameters

The following parameters are not required. Some have default values that allow the successful generation of STAGE2 JCL. Default values are underlined. You will probably need to specify nondefault parameter values to conform to your installation standards. ACCT=1 Defines a job accounting parameter. This parameter can contain parentheses and commas. AUNIT=SYSALLDA Defines a unit name for batch/STC dynamic allocation. This name should be the same as the unit name in the WORK DD statement in the JOBTRAC procedure and should be accessible to all users. BLK=6080 Defines the block size (BLKSIZE) assigned to all libraries with a logical record length of 80 (LRECL=80) allocated in the Unicenter CA-Jobtrac installation process. CHECKPT= Defines the fully qualified data set name of your r3.5 checkpoint data set. CLASS=A Defines the STAGE2 job stream execution class. CPM=N|Y Specifies whether CA CPM is installed. If CPM=Y is specified, INDXCPM= must be specified. GROUP=group Defines the JCL GROUP keyword, if required. GSSLOAD= Defines the fully-qualified load library name into which the CA-GSS associated with this Unicenter CA-Jobtrac was installed. For information about CA-GSS load libraries, see the CA Common Services Getting Started. If this parameter is omitted, it is assumed the CA-GSS load modules are in the system linklist. HISTORY= Defines the fully qualified data set name of your r3.5 history file. INDX35= Defines the high and midlevel qualifiers of your r3.5 CAILIB. INDXCPM= Defines the high and mid-level qualifier of the CA CPM libraries (CAIISPM, CAIISPP, CAIISPT, and CAIPDSE). INDX11= Defines the Unicenter CA-11 high-level index used on the Unicenter CA-11 CAIISPM, CAIISPP, and CAILIB. If you have Unicenter CA-11 installed, specify this parameter.
INSTLIB=indx.JT.SAMPJCL Defines your preallocated Unicenter CA-Jobtrac installation library. Specify the full name of this library. indx defaults to the value of INDX. ISETVOL= Defines the VOLSER on which the ISET data set is to reside. JESCMD=$ Defines your JES command character. This parameter informs Unicenter CA-Jobtrac of the correct character to use when issuing JES commands. MSGCLASS=A Defines the STAGE2 job stream message class. NEWISET=N|Y N specifies that a new ISET data set named in the ISET= keyword exists. Y specifies that a new ISET data set should be allocated. The new ISET data set name is specified in the ISET= keyword. NOTIFY=userid Defines a TSO user ID for STAGE2 JOB statement NOTIFY parameter. PROCLIB=indx.JT.CAIPROC Defines a PROCLIB library. Used for all Unicenter CA-Jobtrac online and batch execution procedures. indx defaults to the value of INDX. PRTY= Defines a STAGE2 job stream priority keyword. RD= Defines a JCL record RD statement. REGION=2048KB Defines a STAGE2 job stream region parameter. SYSOUT=* Defines a STAGE2 utility listings output class. TYPRUN= Defines a TYPRUN parameter to be used in STAGE2.
STAGE2 Installation Job Stream

The STAGE2 job stream is necessary to install Unicenter CA-Jobtrac. It is created by the STAGE1 job, and accomplishes the following: Allocates Unicenter CA-Jobtrac libraries Formats your sysout capture file Updates your system-cataloged procedure library with Unicenter CA-Jobtrac procedures Copies and compiles Unicenter CA-Jobtrac product IMODs (requires CA-GSS CAILIB) Updates your SAMPJCL data set with Unicenter CA-Jobtrac CLISTs Sets up your default global operating parameters and environment Provides the installation verification procedure for Unicenter CA-Jobtrac
The following preparation might be necessary for your installation. Review all the preparation information to continue with the STAGE2 portion of your installation. Information to Review Type of data sets supported Allocate data sets About the database See Types of Data Sets Supported on page 119 Allocate Data Sets on page 120 Description of the Unicenter CA-Jobtrac Database on page 122 About the Sysout Capture File on page 123 Update Procedure Libraries on page 126 Use JOBTRAnn to Set Global Options on page 127
About the sysout capture file Update the procedure libraries Set global options using JOBTRAnn
Run the STAGE2 Job

Follow these steps to run the STAGE2 jobs: 1. Edit member STAGE2. The SYSPUNCH statement in the STAGE1 job stream named the location of the STAGE2 job stream. 2. Review the JCL carefully, making revisions to reflect your installation's requirements. You can separate the job steps into individual jobs if you want. Note: CA-Datacom/AD must be active before running the STAGE2 job stream. 3. Review all the STAGE2 preparation information in the remainder of this chapter. Make modifications to the STAGE2 job stream based on the information. In a shared spool complex, make sure that the Unicenter CA-Jobtrac execution libraries are accessible from all systems. 4. Run the STAGE2 job stream. 5. Verify that each step of every job receives a return code of 0 (zero). All the system logic necessary to run Unicenter CA-Jobtrac is in place. Note: The STAGE2 JCL member contains three jobs.
Types of Data Sets Supported

Unicenter CA-Jobtrac supports for the DD of TRACJnnn AllFusion CA-Panvalet data sets, AllFusion CA-Librarian data sets, and standard IBM partitioned data sets (PDS) for JCL submission and editing. You must use the TEMP temporary-use JCL command to edit JCL from AllFusion CA-Panvalet or AllFusion CA-Librarian. You cannot use the JCL command to edit JCL from AllFusion CA-Panvalet or AllFusion CA-Librarian. You can select a PAN access method, a LIBR access method, or a standard PDS access method. All JCL libraries on the same ddname, however, must use the same access method. The temporary-use JCL library for each location must be a PDS.
Allocate Data Sets

The following table describes the data sets allocated earlier in the installation process: DDname SAMPJCL Data Set Name your.JT.SAMPJCL Description JCL samples, table services, SMP/E examples, exit samples, IVP job, and other information helpful during installation.
TRACPARM
your.JT.PPOPTION Unicenter CA-Jobtrac setup library containing global options, resource definitions, and exclusion definitions.
The following table describes the installation and execution data sets allocated by the STAGE2 job stream: DDname TRACJ000 Data Set Name your.PRODJCL Description JCL library. This data set can be a AllFusion CA-Panvalet data set, a AllFusion CA-Librarian data set, or a standard PDS. Temporary-use JCL library. This data set must be a standard PDS. Unicenter CA-Jobtrac SCL library. This library contains schedule members coded using SCL (Schedule Control Language). This data set must be a standard PDS. Remote (Cross-Platform) credentials file. Encrypted user ID, domains, and passwords for submitting work on remote systems (a scheduler or an agent). Unicenter CA-Jobtrac setup library containing members for Automatic Date Insertion (ADI) and JCL Modification Facility (JMF). For more information, see the text following the table.
TRACT000 TRACS000
your.TEMP your.SCL
TRACR000
your.RMTPSWD
DATELIB
your.DATELIB
DDname CAPTURE
Data Set Name your.CAPTURE
Description Sysout capture file. This data set is a formatted sequential (indexed) file that holds the compressed sysouts for Unicenter CA-Jobtrac events. An initial format of at least 15 cylinders is required to hold SCL output. PDS for holding CMDSET (command set) members. For information about using command sets, see the Extended Scheduling Services Guide. This data set must be a standard PDS. PDS library for storing event documentation and manual action information. This data set must be a standard PDS. Email template file. PDS library for storing email templates used with the email notification feature.
TRACMDS
your.TRACMDS
TRACD000
your.DOCLIB
TRACM000
your.EMAILTPL
ADI uses member PRODDATE in the DATELIB data set as the default. For location-specific overrides, specify the following DDs in your PROCs or CLISTs:
//DATELIB DD DSN=cai.DATELIB(PRODDATE),DISP=SHR //DATEL 1 DD DSN=cai.DATELIB(PRODD 1),DISP=SHR //DATEL 2 DD DSN=cai.DATELIB(PRODD 2),DISP=SHR / / / default location 1 location / 2 location / /
JMF uses member JMFSYM01 in the DATELIB data set. For other locations, use the JLOCnnn: PARM in your JMFSYM01 member. For example:
JLOC 1:CAI.DATELIB(JMFSYM 2) / 1 location /
For more information, see SAMPJCL members JMFSYM01 and PRODDATE used later in the IVP.
Description of the Unicenter CA-Jobtrac Database

The database is the key control point in the Unicenter CA-Jobtrac system. This incorporates checkpoint data, history data, and operational tables. Unicenter CA-Jobtrac uses the CA-Datacom/AD database to house this data. CA-Datacom/AD is the common component version of Advantage CA-Datacom/DB that is included with Unicenter CA-Jobtrac at no additional charge. This is a high-speed relational database that improves performance and reliability for Unicenter CA-Jobtrac by providing data caching, transaction logging, automatic rollback and recovery for application or system failures, and optionally the ability to perform backups while open, and retain transaction logs so that forward recovery can be done in the event of a DASD failure. The CA-Datacom/AD's database started task is called a Multiple User Facility or MUF. A MUF can be shared in a Sysplex using XCF, a Coupling Facility, or through the network (not recommended). Multiple copies of Unicenter CA-Jobtrac can run on the same system. A Unicenter CA-Jobtrac system is uniquely identified by a one-character token. This token is defined to the Unicenter CA-Jobtrac PROC, batch utilities, and ISPF clist by specifying a dummy DD allocation as follows: JOBTRACx DD DUMMY ALLOCATE FI(JOBTRACx) DUMMY (in JCL) (in ISPF)
The x in the ddname is the token that is used to identify this Unicenter CA-Jobtrac system. Each Unicenter CA-Jobtrac running on a system must have a unique token specified. We recommend that the token match the taskname with which Unicenter CA-Jobtrac is started. It can be A-U, W-Z, or 0-9. In the Unicenter CA-Jobtrac database, the token is part of the data key. This allows you to use the same CA-Datacom/AD MUF and Unicenter CA-Jobtrac tables to support multiple Unicenter CA-Jobtrac instances just by using a different token to logically separate the data. When running multiple systems, you should consider the database size to ensure that it is large enough to support both all of the systems. The checkpoint data contains all current schedule data. It is updated and maintained by numerous components, including dynamic schedule processors, which can add a thousand events at a time, and hundreds of local and remote TSO users who perform on-demand and exception processing. Jobs that are waiting to run or currently executing, and jobs that have completed, but have not been archived, make up the checkpoint data.
The history data is the run history and audit data for Unicenter CA-Jobtrac. Job history is added by the archive processing and can be viewed through the ISPF Event History Display or through batch reporting. In addition, audit records that detail the changes made to event records by a user or operator are part of the history data. Other operational tables are stored in the database. These include user modifiable tables such as the Jobtrac Table Services (JTS) tables. Some tables are only used for Unicenter CA-Jobtrac operation and therefore are not visible to customers. These include schedule load staging tables and the timer table.
About the Sysout Capture File

The sysout capture file can be the largest Unicenter CA-Jobtrac data set, but because of the Unicenter CA-Jobtrac compaction routines and the EXCP access method, it uses its space the most efficiently. You can expect a four-to-one ratio of compression over the JES spool. The size of the sysout capture file depends on how many jobs are processed, how many sysouts are captured, how many days are kept in the online capture, and the average line count of each listing. For example, 100 cylinders can comfortably handle up to 1.5 million lines of sysouts. You can use this figure in determining how many cylinders you actually need for your sysout archival requirements. For a more detailed discussion, see the chapter "The Sysout Capture File" in the Reports, Maintenance, and Recovery Guide. CAPTURE your.CAPTURE Sysout capture file. (CAPTURE is the default) This data set is a formatted sequential (indexed) file. Messages Associated with Sysout Capture: Error routines automatically prompt the operator and temporarily stop operation if the capture file becomes full during normal operation. The operator can optionally suspend capture or close the file to tape and archive aged sysouts. The message identifier and an explanation are found in the Operator Guide, along with appropriate replies. Differentiating Copies of Unicenter CA-Jobtrac: 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 Unicenter CA-Jobtrac on multiple systems that share DASD, the sysout capture file must be on a pack on your primary (event-submitting) Unicenter 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. For more information, also see Use Other Sysout Capture Products on page 230.
Description of TRACMDS
TRACMDS your.TRACMDS PDS for holding CMDSET (Command Set) members. For information about using command sets, see the Extended Scheduling Services Guide. This data set must be standard PDS.
Recommended Initial Data Set Sizes

The following data set sizes are recommended during initial testing and implementation. You can adjust the sizes of the data sets after installation is complete. DDname DATELIB CAPTURE TRACMDS Recommended Size 2 cylinders 100 cylinders (5 cylinders minimum) 1 cylinder
Allocating Additional Libraries: The Unicenter 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 254 additional locations and libraries. In the STAGE2 job stream, you can add definitions for the additional libraries.
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 AllFusion CA-Librarian or AllFusion 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. For more information, see Define Location Information (DYNAMLOC) and Initiation IMODs on page 176.
Update Procedure Libraries

Unicenter CA-Jobtrac requires a number of cataloged procedures. These procedures are copied into your specified cataloged procedure library by the STAGE2 job. Requirement: VINITx, JOBTRACx, and DUMPVx must be in a procedure library for started tasks. The following table describes the Unicenter CA-Jobtrac procedures contained in the CAIPROC library: Procedure JOBTRACx VINITx JTEZREPT GJTRVSCH GJTRJPRG GJTRJARC GJTRMAJC GJTRVRLD DUMPVx JCL#TCXR JCL#TDBL JCL#TDB2 JCL#TRAC Description Scanner task (started task) IPL initialization task Unicenter CA-Jobtrac report utility Batch job access to schedule updating Batch job to delete records from Unicenter CA-Jobtrac history 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
The x in the preceding procedure names represents the token value that you specified during the STAGE1 process. Process: Select a cataloged procedure library for Unicenter CA-Jobtrac (such as SYS1.PROCLIB). Include the Unicenter CA-Jobtrac procedures in it or add the CAIPROC PROCLIB to the proclib list in JES.
Use JOBTRAnn to Set Global Options

Unicenter CA-Jobtrac global options describe global values and the environment in which Unicenter CA-Jobtrac operates. Unicenter CA-Jobtrac global options are set using the JOBTRAnn member and by using the Unicenter CA-Jobtrac global options panels. Some options are set by the JOBTRAnn member only, some options are set using the global options panels only, and some options are set using either one. Additionally, some of the options set using JOBTRAnn are displayed on the global options panels, but you cannot set them on the panels. For more information about the global options panels, see the chapter "Customization Tasks."
New Options in Version

The following options are new in this release of Unicenter CA-Jobtrac: CPMAPPL E@DOMAIN ECLLATE ECLNODES ECLWTO EMAILFROM EMAILSRV EREPORT PRIORITY STATINTV REPORT
Global Options in the STAGE2 Job Stream

The STAGE2 job stream creates a default JOBTRAnn member in your SAMPJCL data set. Before customizing, copy the sample to your PPOPTION data set. After running the STAGE2 job stream, you can change the values for the JOBTRAnn options or add options not in the job stream.
Location of JOBTRAnn
Member JOBTRAnn must reside in the PPOPTION library.
Using Multiple JOBTRAnn Members

By copying the default JOBTRAnn member, you can create more than one JOBTRAnn member. The nn in each member is unique. You can use each of these members to test a different configuration of options, or if running multiple copies of Unicenter CA-Jobtrac. Once Unicenter CA-Jobtrac is started, you can activate some of the options in a given JOBTRAnn member by issuing the following modify command. In the command, taskname is the name assigned to the Unicenter CA-Jobtrac you want to affect, and nn matches nn in the desired JOBTRAnn member: F taskname,OPTS=nn
The JOBTRAnn Options

The following sections describe the options you can set in the JOBTRAnn member. Each option's syntax is also presented. The default values (such as 24 for AMRLCNT) are used if the option is omitted. All options must start in column 1 of a JOBTRAnn member.
AMRLCNT
The AMRLCNT option defines the number of identical message IDs received contiguously before deciding that a loop is occurring and issuing message TRAC029I. (AMRLCNT is an acronym for Automatic Message Recognition Tuning Parameter.) The default is 24. This option has the following syntax: 24 AMRLCNT=nnnn
To enable this option, recycle the Unicenter CA-Jobtrac STC.
ARCBLK
The ARCBLK option defines the Sysout Capture archive tape block size in multiples of 150-byte records (LRECL=150). This option has the following syntax: 327 ARCBLK=blksize
ARCDSN
The ARCDSN option defines the first 35 characters of the Sysout Capture archive tape data set name. Unicenter CA-Jobtrac appends the date and time to the job name as Thhmm.Dyyddd for volume identification. This option has the following syntax: ARCDSN=arch.tape.dsname
ARCDSP
The ARCDSP option defines the normal DSN disposition of the Sysout Capture archive tape. See ARCRTN on page 130. This option has the following syntax: CATLG ARCDSP=tapedisp
ARCRTN
The ARCRTN option defines the tape retention period in days to be used for the Sysout Capture archive tape created by a 0ARCHIVE or 0SYSARCH task. This value is also used to calculate the number of days to maintain an online copy of the sysout archive &INDEX entry. The &INDEX entry, available through the Unicenter CA-Jobtrac/ISPF dialogs, lists all sysouts captured for the defined period, a brief run history, and the archive tape volume on which they reside. This option has the following syntax: 3 ARCRTN=tapertnpd
ARCUNT
The ARCUNT option defines the Sysout Capture archive tape unit name (UNIT=unitname). See ARCRTN on page 130. This option has the following syntax: TAPE ARCUNT=tapeunit
ARM
The ARM option defines the type of IBM's Automatic Restart Management (ARM) processing you want. This option has the following syntax: NO ARM=NONE abend code list
NO Indicates that ARM processing should not take place. This is the default. NONE Indicates that ARM processing should proceed without exceptions. abend code list Is a list of abend codes that should disallow normal ARM processing, such as: 8 6,2 2,X37 In this example, the following are excluded from ARM processing: 806 abend (module not found) 0202 abend (sysout writer subtask has abended) D37, B37, etc. (various out-of-space conditions) Note in the X37 entry, the X indicates a generic abend and includes all abends that end with 37.
ARM Processing for Unicenter CA-Jobtrac: Unicenter CA-Jobtrac offers an interface to IBM's Automatic Restart Management feature (ARM). The ARM feature allows for automatic restart in the event of a product failure, which results in termination. If you are currently using ARM, the Unicenter CA-Jobtrac needs may well be met with the default profile currently defined. For the purpose of restarting Unicenter CA-Jobtrac with the same command that originally started the product, the following may be used as an example. To define the couple data set: DEFINEDS SYSPLEX(PLEX79) DSN(COUPLE.ARM.XE79P) VOLSER(MVXE79) CATALOG DATA TYPE(ARM) ITEM NAME(POLICY) NUMBER(5) ITEM NAME(MAXELEM) NUMBER(25) ITEM NAME(TOTELEM) NUMBER(2 ) DEFINEDS SYSPLEX(PLEX79) DSN(COUPLE.ARM.XE79A) VOLSER(TSO79A) CATALOG DATA TYPE(ARM) ITEM NAME(POLICY) NUMBER(6) ITEM NAME(MAXELEM) NUMBER(35) ITEM NAME(TOTELEM) NUMBER(3 ) To define the policy: DATA TYPE(ARM) REPORT(YES) DSN(COUPLE.ARM.XE79P) DEFINE POLICY NAME(POLXE79A) REPLACE(YES) ELEMENT( ) A startup parameter (ARM=) may be used to customize the restart criteria. To enable this option, recycle the Unicenter CA-Jobtrac STC.
AUNIT
The AUNIT option defines a unit name for batch/STC dynamic allocation. This name should be the same as the unit name in the WORK DD statement in the JOBTRAC procedure and should be accessible to all users. This option has the following syntax: SYSDA AUNIT=unitname
AUTOC
The AUTOC option defines the AUTO-SCHD recognition character to track jobs that are submitted outside of Unicenter CA-Jobtrac control. To use simultaneous operation of the AUTOC parameter on multiple copies of Unicenter CA-Jobtrac on the same system, define different AUTO-SCHD characters for each Unicenter CA-Jobtrac on the system. The recognition character must be either in the JCL being submitted in column 71 or the $AUTO step. To display what is being used now, from the Unicenter CA-Jobtrac ISPF Main Menu enter SYS OPTS, then select number 1. For more information, see the Operator Guide. This option has the following syntax: > AUTOC=autochar
autochar A through Z, 0 through 9, <, >, ?, $, @, #, and / are valid characters. To enable this option, recycle the Unicenter CA-Jobtrac STC.
AUTOQ
The AUTOQ option defines up to eight AUTO-QUEUE job classes in accordance with JES2, for external tracking of jobs. Once a job is submitted in this JES2 class, without the AUTOC character in column 71 or the $AUTO step, the job will be tracked and or controlled by Unicenter CA-Jobtrac. Jobs that are on the checkpoint with a 'Q' or a 'J' dependency will be controlled by Unicenter CA-Jobtrac. If no job is on the checkpoint, the job will be added and tracked by Unicenter CA-Jobtrac. To display what is being used now, from the Unicenter CA-Jobtrac ISPF Main Menu enter SYS OPTS, and then select number 1. For information about using AUTO-SCHD character, see the Operator Guide. Note: This parameter is only valid for JES2 users. This option has the following syntax: AUTOQ=JES2classlist
JES2classlist A through Z and 0 through 9 are valid characters. To enable this option, recycle the Unicenter CA-Jobtrac STC.
CAPDMPS
The CAPDMPS option specifies whether to capture system dumps to the Sysout Capture File. Y directs Sysout Capture to capture system dumps, while N will not. N is the default. Any value other than Y or N defaults to N. This option has the following syntax: N CAPDMPS=Y
CMDLIB
The CMDLIB option specifies the name of the TRACMDS PDS defined by the STAGE2 customization job stream. The TRACMDS member is a group of command sets. A command set is a group of commands executed using a single command. For more information, see the scheduling system commands (SCS) in the Extended Scheduling Services Guide. This option has the following syntax: CMDLIB=tracmds.pds
To enable this option, either shut down Unicenter CA-Jobtrac with the BACK parameter or IPL.
CPM
The CPM option specifies to activate the CPM (Critical Path Monitor) function in Unicenter CA-Jobtrac. When specified, the CAIENF events for CPM are created, and the CPM related fields and commands are available in ISPF. By default, the CPM function is inactive. This means that no CAIENF events are created and no CPM related commands or data fields are available through the ISPF interface. The CPM keywords in SCL are accepted even if CPM is inactive. For more information about CPM, see the Extended Scheduling Services Guide. This option has the following syntax: NO CPM=YES
CPMAPPL
The CPMAPPL option allows overriding of the CAICCI application name. The name specified can be 1 to 20 characters in length and must match the value defined in the CPM started task in the SET CCIAPPLNAME= command. If SET CCIAPPLANAME= is not being set in the CPM started task, the default of CpmServer is used by CPM. CpmServer is also the default if the Unicenter CA-Jobtrac CPMAPPL parameter is not specified. Under normal circumstances, neither of these values should be set, and the defaults should be used. This option has the following syntax: CPMAPPL=cci_appl_name
DATELIB
The DATELIB option specifies the name of the Automatic Date Insertion feature control library defined by the STAGE2 customization job stream. 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. For more information about JMF, see the Extended Scheduling Services Guide. Sample members PRODDATE and JMFSYM01 are copied over to the DATELIB data set later in the installation. This option has the following syntax: DATELIB=xxxxxxxx.xxxxxxxx.DATELIB
DBID
The DBID option specifies the CA-Datacom database ID used in this Unicenter CA-Jobtrac. The database ID specified is used to load the access URT, HDnnnnJT, where nnnn is the DBID specified. If not specified, the default is 0161. This option has the following syntax: 161 DBID=nnnn
DEFAULT0
The DEFAULT0 option specifies whether an event or schedule not found in a higher location than 000 can be read from location 000. YES, the default, denotes that the location does default to location 000 if the event or schedule is not found in the location specified. Otherwise, the event is posted with a JCL error, or the schedule is posted with an 'M' dependency. This does not apply to calendars. This option has the following syntax: YES DEFAULT =NO
DFSQUAL
The DFSQUAL option specifies to override default for allocation of data set names for viewing the sysout capture file. If DFSQUAL=NO is used, default sysout view qualification is not done; that is, the high-level qualifier used in SVQUAL is used for all users. This option has the following syntax: YES DFSQUAL=NO
DISABLE
The DISABLE option specifies the JOBTRAC ISPF line commands one wishes to disable. This option has the following syntax: DISABLE=cmd Example: In this example the A, @, and the C line commands are no longer valid for all Unicenter CA-Jobtrac TSO users, and the INVALID COMMAND message displays if these commands are entered. DISABLE=A@C To enable this option, either shut down Unicenter CA-Jobtrac with the BACK parameter or IPL. Also recycle TSO users.
DRDR
The DRDR option specifies to override default (DRDR=NO) for dedicated internal reader. If DRDR=YES is specified, the internal reader is allocated at startup and is retained until shutdown. If DRDR=NO is used, an internal reader is allocated and released each time a job it submitted. This option has the following syntax: N DRDR=Y
DUMPUJV
The DUMPUJV option signals GJTRUJV2 (IEFUJV SMF exit) whether to create (Y) or not to create (N) SVC dumps in the event that errors occur during allocation or access of the checkpoint. Y is the default. Any value other than Y or N defaults to Y. Messages normally issued are still issued. SVC dumps are still created in abend situations. This option has the following syntax: Y DUMPUJV=N
E@DOMAIN
The E@DOMAIN option defines a default domain to add to an email address that does not specify one. This option has the following syntax: E@DOMAIN=domain.com Example: ID ADDR:BOB is specified in a template; the email is sent to BOB@domain.com. This only applies to template addresses that do not contain an @. To enable this option, recycle the Unicenter CA-Jobtrac STC.
ECLLATE
The ECLLATE option specifies whether to report late conditions to the event console. This option has the following syntax: N ECLLATE=Y
ECLNODES
The ECLNODES option specifies one or more CAICCI nodenames to receive messages. Each nodename specified must have a UEJM Event Console or Unicenter Event Console to receive messages. You can specify multiple ECLNODES statements if you need more nodes than can fit on one statement or if you want to define each node on a separate line. This option has the following syntax: , ECLNODES=ccinodeccinode
ECLWTO
The ECLWTO option specifies whether to issue WTOs to the local system log besides sending the WTOs to the event console. Only messages in the message table that specify WTO=OPT are affected by this option. As distributed, all ECL messages have WTO=OPT specified. For more information, see Alter the Event Console Logging Message Options on page 245. This option has the following syntax: N ECLWTO=Y
EMAILFROM
The EMAILFROM option defines the from address that is put on email. This value depends on your SMTP environment and may need to be the form of a valid email address, or be an actual, defined email address. Check with your mail administrator. This option has the following syntax: 'CA-JOBTRAC@CA.COM-DO_NOT_REPLY' EMAILFROM=address
EMAILSRV
The EMAILSRV option defines the name or IP address of the server that receives and routes the emails that Unicenter CA-Jobtrac sends. If the first character is numeric, it is assumed to be an IP address in dotted decimal format (99.99.99.99). Otherwise, it is assumed to be a server name. The default is localhost. This option has the following syntax: localhost EMAILSRV=server
EREPORT
The EREPORT option specifies the option for Product Alert Reporting to Unicenter Service Desk. If YES is specified, product alerts are reported to Unicenter Service Desk. If NO is specified, no product related alerts are created. This option has the following syntax: NO EREPORT=YES
EXECTRLR
At submission time, Unicenter CA-Jobtrac flags events that it submits by adding the following step at the end of each event: //$J EXEC PGM=$A,COND=( ,xx),PARM=parm Unicenter CA-Jobtrac uses this additional step to track events. Depending on how the COND is set, the step does not execute. If EXECTRLR is set to NO (setting xx to LE), the job step does not execute. If EXECTRLR is set to YES (setting xx to GT), the job step executes. The actual COND value is changed only by the option flag. No numerical RC is added to the COND statement. Only LE or GT is added. This option has the following syntax: NO EXECTRLR=YES
FCSTDBID
The FCSTDBID option specifies the CA-Datacom database ID used for forecasts. The database ID specified is used to load the access URT, HDnnnnFC, where nnnn is the DBID specified. This is not used by the Unicenter CA-Jobtrac started task but is made available to other programs that use the forecast database. If not specified, the default is 0162. This option has the following syntax: 162 FCSTDBID=nnnn
INSERTRMS
The INSERTRMS option specifies if and when a Unicenter CA-11 U11RMS step should be inserted by Unicenter CA-Jobtrac during job submission. This applies only when RERUN=CA-11 is specified. You can identify jobs for step insertion in three ways. This option has the following syntax: INSERTRMS=ALL NO class list
ALL Specifies that all jobs submitted by Unicenter CA-Jobtrac should have the U11RMS step inserted. NO Specifies that no jobs should have the U11RMS step inserted. class list Specifies a list of job classes that should have the step inserted. The JOB statement is examined for a class that is contained in the list specified, and the step is inserted only if a matching class is found. The list is specified as a string of one-character classes, without interceding blanks (that is, AEF23 specifies that classes A, E, F, 2, and 3 are to have the step inserted). Class characters can be A-Z and 0-9. A special class character (?) is available to specify that jobs without a class specified should have the step inserted. The first three steps of a job are examined for a manually inserted Unicenter CA-11 U11RMS step before the step is inserted. If the string '11RMS' as in U11RMS or CA11RMS is found in the procname or program name of an EXEC statement, then the Unicenter CA-11 step is not inserted. To enable this option, recycle the Unicenter CA-Jobtrac STC.
JCLTABL
The JCLTABL option specifies the maximum number of lines of JCL per job. This table uses private storage below the line for submission. To calculate the amount of storage required: number of JCL lines x 80 = bytes of storage required The default is 9000. This option has the following syntax: 9 JCLTABL=nnnnn
JESCMD
The JESCMD option specifies your JES command character. This parameter informs Unicenter CA-Jobtrac of the correct character to use when issuing JES commands. This option has the following syntax: $ JESCMD=x
JMFTABLE
The JMFTABLE option specifies the number of entries in the JMF table. The default is 1000 and the ECSA usage is approximately 140 KB with this value. Specifying 2000 would use approximately 280 KB (and so on). This option has the following syntax: 1 JMFTABLE=nnnnn
LIBPGM
The LIBPGM option specifies the name for the AllFusion CA-Librarian Master Library utility program. This option has the following syntax: LIBPGM=libpgm AFOLIBR
PRIORITY
The PRIORITY option specifies the priority for each job submitted. The priority is used to control job submission by submitting jobs with the highest priority first. The value specified must be a numeric value between 0 and 100. 0 is the highest priority, and 100 is the lowest priority. The default is 100. This option has the following syntax: 1 PRIORITY=nnn
RAMAXCC
The RAMAXCC option specifies the MAXCC for a job that is added to the checkpoint using the ADD or RUN command. The value specified must either be N or one- to four-numeric characters. N effectively turns off condition code checking for these jobs. 0000 is the default. This option has the following syntax: RAMAXCC=nnnn N
REMTCRED
The REMTCRED option specifies whether the TRACRnnn password member name must match the event name or can have a different name specified using the alternate member name parameter in the SCL. ALTMEM specifies the alternate JCL field in an event can be used to specify the remote password data set member name. This name is used when retrieving the user ID, password, and domain information to be sent with the event to a scheduler or an agent. 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. If this keyword is not specified, the default is EVENT, and the event name is used to retrieve the information from the remote password data set (TRACR000). This option has the following syntax: EVENT REMTCRED=ALTMEM
REPORT
The REPORT option specifies the global default option for Event Alert Reporting to Unicenter Service Desk. If YES is specified, all jobs failures are reported to Unicenter Service Desk unless overridden in the SCL. If NO is specified, no job failures are reported unless specified in the SCL. This option has the following syntax: NO REPORT=YES
RERUN
The RERUN option specifies the product that Unicenter CA-Jobtrac is to interface to when performing job reruns and restarts. For more information, see INSERTRMS on page 145. This option has the following syntax: NONE RERUN=CA-11
RESTAGEABEND
The RESTAGEABEND option specifies whether to restage jobs on abend. The default is YES. This option has the following syntax: YES RESTAGEABEND=NO
YES Results in the following: NO Results in the following: Does not restage the event. Instead, adds an "O" dependency. When the event is restaged through ISPF, the "O" dependency is removed if not originally present, and the restaged event will have a "J" dependency. If the event is not restaged, releasing the "O" (even if originally present) or purging the job will release its successors and do a BYPASS RERUN PROFILE. Restages the event with a "J" dependency. Adds an "O" dependency to the restaged event only if originally present.
RESTAGECAT
The RESTAGECAT option specifies whether to restage jobs on catalog error. For the values of YES and NO, see RESTAGEABEND. The default is YES. This option has the following syntax: YES RESTAGECAT=NO
RESTAGECC
The RESTAGECC option specifies whether to restage jobs on condition code. For the values of YES and NO, see RESTAGEABEND. The default is YES. This option has the following syntax: YES RESTAGECC=NO
RESTAGEJCLERR
The RESTAGEJCLERR option specifies whether to restage jobs with JCL errors. For the values of YES and NO, see RESTAGEABEND. The default is YES. This option has the following syntax: YES RESTAGEJCLERR=NO
SCHENV
The SCHENV option is a 16-byte field that lets you specify a default for all jobs. Unless overridden, this value is inserted on the SCHENV JOB statement parameter by Unicenter CA-Jobtrac. This value may be verified before job submission and could result in a JCL error with a W (WLM) dependency if coded incorrectly. NO may be coded for this value so that insertion of the SCHENV parameter on the JOB statement does not occur as the default. NO is the default if the SCHENV keyword is not found. This option has the following syntax: NO SCHENV=cccccccccccccccc
SCLMAX#
The SCLMAX# option specifies the maximum number of schedules (SCL) to be loaded at the same time. Loading multiple very large SCLs at the same time may require a region size, which will never be available and cause Unicenter CA-Jobtrac to abend. This option lets you limit the number of parallel SCL loads. A value of 1, 2, or 3 can be specified. The default and maximum number is 4. Any other or invalid value for SCLMAX# will default to 4. This option has the following syntax: 4 SCLMAX#=n
STATINTV
The STATINTV option specifies the number of minutes between statistic record creation. The number can be between 1 and 1440. If the number is less than 60, it should divide evenly into 60, or it is adjusted downward to the next number that evenly divides into 60. If the number is more than 60, it should be a multiple of 60, or it is adjusted downward to the next number that evenly divides into 60. The default is 60 minutes. This option has the following syntax: 6 STATINTV=nnnn
SUBROOT
The SUBROOT option specifies if a user ID of ROOT can be used when submitting work to a scheduler or an agent on a remote platform. If not specified, the default is NO, and the user ID ROOT is not allowed to be used. This option has the following syntax: NO SUBROOT=ALLOW
SVQUAL
The SVQUAL option specifies up to an eight-byte qualifier to put on front of data set names which Unicenter CA-Jobtrac dynamically allocates for viewing. This option is used only when PROFILE NOPREFIX is set (by default). This option has the following syntax: SVQUAL=qual
To enable this option, either shut down Unicenter CA-Jobtrac with the BACK parameter or IPL. Also recycle TSO users.
SYNCSYS1
The SYNCSYS1 option defines the SMF system ID of the primary submission system. This option is only required if running multiple copies of Unicenter CA-Jobtrac. For more information, see Run in a Shared Sysplex Environment on page 268. This option has the following syntax: SYNCSYS1=sysid
SYNCSYS2
The SYNCSYS2 option defines the SMF system ID of the secondary submission system. This option is only required if running multiple copies of Unicenter CA-Jobtrac. For more information, see Run in a Shared Sysplex Environment on page 268. This option has the following syntax: SYNCSYS2=sysid
SYNCSYS3
The SYNCSYS3 option defines the SMF system ID of the backup submission system. This is only required if running multiple copies of Unicenter CA-Jobtrac. Note: For more information, see Run in a Shared Sysplex Environment on page 268. This option has the following syntax: SYNCSYS3=sysid
SYNCTOL
The SYNCTOL option defines the number of seconds the primary submission system can be idle. If the primary system is idle for more than the number of seconds defined by SYNCTOL, the secondary system automatically issues a WTO to request primary event submission duties. The operator can switch primary submission duties at any time by issuing the ACTSYS=sysid modify command on the primary system. For information about switching primary systems, see the Reports, Maintenance, and Recovery Guide. This option has the following syntax: 3 SYNCTOL=nnn
SYSDBID
The SYSDBID option specifies the CA-Datacom database ID used for system tables. This is specified in the SYSTEMDBID parameter in the CA-Datacom startup parameters and defaults to 1000. The database ID specified is used to load the access URT, HDnnnnSY, where nnnn is the DBID specified. If not specified, the default is 1000. This option has the following syntax: 1 SYSDBID=nnnn
TNDOVLP
The TNDOVLP option signals the Unicenter CA-Jobtrac schedule load process whether to consider a TIME/DATE overlap as an error. N indicates that Unicenter CA-Jobtrac will not flag a TIME/DATE overlap as an error. Y results in a TIME/DATE overlap being considered an error. Y is the default. This option has the following syntax: Y TNDOVLP=N
Example: With option TNDOVLP=N, you get: DAILY1 22 1 1D DAILY
With option TNDOVLP=Y, you get: DAILY1 22 1 1D(M) DAILY <==TIME/DATE OVERLAP: MUST HAVE DEPENDENCY
TSCMDSPA
The TSCMDSPA option specifies the maximum size for the SCS (System Command Scheduling) table. A value from 100 to 25000 can be specified. Larger values use more ECSA. Table size can only be increased after an IPL or a BACK of Unicenter CA-Jobtrac. For information about the SCS table, see the Extended Scheduling Services Guide. This option has the following syntax: 25 TSCMDSPA=nnnnn
TSDSNSPA
The TSDSNSPA option specifies the maximum size for the ADR (Automatic Dataset Recognition) table. A value from 100 to 25000 can be specified. Larger values use more ECSA. Table size can only be increased after an IPL or a BACK of Unicenter CA-Jobtrac. For information about the ADR table, see the Extended Scheduling Services Guide. This option has the following syntax: 1 TSDSNSPA=nnnnn
TSMSGSPA
The TSMSGSPA option specifies the maximum size for the AMR (Automatic Message Recognition) table. A value from 100 to 25000 can be specified. Larger values use more ECSA. Table size can only be increased after an IPL or a BACK of Unicenter CA-Jobtrac. For information about the AMR table, see the Extended Scheduling Services Guide. This option has the following syntax: 25 TSMSGSPA=nnnnn
TSPGFSPA
The TSPGFSPA option specifies the maximum size for the CCPF (Condition Code Program Filters) table. A value from 100 to 25000 can be specified. Larger values use more ECSA. Table size can only be increased after an IPL or a BACK of Unicenter CA-Jobtrac. For information about the CCPF table, see the Extended Scheduling Services Guide. This option has the following syntax: 25 TSPGFSPA=nnnnn
WLMRSRC
The WLMRSRC option specifies the WLM resource you have defined for the Unicenter CA-Jobtrac started task. Unicenter CA-Jobtrac sets the status of this resource during initialization and termination. This parameter is specified in the JOBTRA00 startup member. No validation is performed on the value specified, and this could result in an improper resource status if coded incorrectly. You may code NO for this value, and it results in the status of the resource not being changed. NO is the default if the WLMRSRC keyword is not found. This option has the following syntax: NO WLMRSRC=cccccccccccccccc
XPLATRERUN
LOCAL indicates jobs that fail are restarted from Unicenter CA-Jobtrac, rather than by a scheduler or an agent. If this option is set, a scheduler or an agent is not notified of the job's status until the job successfully completes or the job is purged or deleted on Unicenter CA-Jobtrac. The failing job is automatically restaged in the Unicenter CA-Jobtrac checkpoint and can be restarted using Unicenter CA-11. If not specified, the default is REMOTE, and a scheduler or an agent is notified of the failure when it occurs. In this case, the job is NOT restaged automatically by Unicenter CA-Jobtrac. In this mode, the Unicenter CA-11 interface does not insert the U11RMS step into the job at submission. We recommend that Unicenter CA-11 not be used when job reruns are being handled by the remote system. Jobs in the checkpoint can be restaged manually on the Unicenter CA-Jobtrac Scheduled Event Display panel with the R line command and resubmitted for execution. The change in the status of the job is sent to inform a scheduler or an agent. When restarting jobs from a scheduler or an agent, the jobs should have a small number of steps, since the jobs can only be resubmitted, not restarted. This option has the following syntax: REMOTE XPLATRERUN=LOCAL
Chapter 6. Customization Tasks

This section contains the following topics: Modify CA-Datacom/AD for Unicenter CA-Jobtrac . . . . . . . . Alter the CA-Datacom/AD LXX and FXX . . . . . . . . . . . . . Modify CA-GSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . Customize SYS1.PARMLIB . . . . . . . . . . . . . . . . . . . . . Set Up Default Authorization . . . . . . . . . . . . . . . . . . . . Set Up the JES3 Held Job Class . . . . . . . . . . . . . . . . . . Define Location Information (DYNAMLOC) and Initiation IMODs Update Your TSO Procedures or CLIST . . . . . . . . . . . . . Set Global Options . . . . . . . . . . . . . . . . . . . . . . . . . . Copy the PRODDATE Member . . . . . . . . . . . . . . . . . . . Copy the JMFSYM01 Member . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Copy the RESOURCE Member Copy the EXCLPARM Member . . . . . . . . . . . . . . . . . . . Maintain Table Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Up AMR Support Create IPLTABLE Entries (Optional) . . . . . . . . . . . . . . . . Enable the SPACE Command . . . . . . . . . . . . . . . . . . . Integration with Unicenter CA-11 . . . . . . . . . . . . . . . . . . Set Up CA-JCLTrac . . . . . . . . . . . . . . . . . . . . . . . . . Use Other Sysout Capture Products . . . . . . . . . . . . . . . . Cross-Platform Scheduling . . . . . . . . . . . . . . . . . . . . . Alter the Event Console Logging Message Options . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
162 165 167 171 174 175 176 180 184 201 202 203 204 205 208 209 214 215 218 230 232 245
The following phases complete customization, set up, and implementation of Unicenter CA-Jobtrac: Customization tasks - Covered in this chapter Startup and verification tasks - Covered in the chapter "Startup and Verification"
The customization tasks let you set up Unicenter CA-Jobtrac to meet your installation's needs. Note: For information about setting up user exits, see the Reports, Maintenance, and Recovery Guide.
Chapter 6. Customization Tasks 161
Modify CA-Datacom/AD for Unicenter CA-Jobtrac

This topic describes the changes that you need to make to CA-Datacom/AD to support Unicenter CA-Jobtrac.
Startup Keywords for CUSMAC(DBDATIN1)

CA-Datacom/AD has a large number of startup parameters that you can modify. Very few of these parameters require changes, and we recommend that you use the settings that were defined when CA-Datacom was installed for the majority of the parameters. These parameters are described in detail in the Advantage CA-Datacom/DB Database and System Administrator Guide. This section discuss only the few keywords that you need to be concerned with in implementing Unicenter CA-Jobtrac. These keywords are specified in the CA-Datacom/AD CUSMAC(DBDATIN1). MUF mufname
The MUF keyword gives a name to the MUF. You are required to specify this name if you plan to share the Unicenter CA-Jobtrac database. XCF uses this mufname to allocate the CA-Datacom/AD address space in the sysplex. It is always a good idea to specify this parameter, but it is required if the database is to be shared between systems. The optional parameters for the MUF keyword are not described here since they need not be specified. The value is 1-8 characters. Later when the DBSIDPR module is discussed, this mufname is used to define the XCF connection to the MUF. TASKS number,size,,,xcf_tasks
The TASKS keyword defines the maximum number of tasks that are available with the CA-Datacom MUF to process database connections. Each connection to the database requires a TASKS keyword. The size value should be specified as 32K. This a the required size for Unicenter CA-Jobtrac. The number is the total number of tasks that are available and includes the task specified in the xcf_tasks. The xcf_tasks is the number of tasks that are used for XCF connection to the MUF. If you will have other products, such as Unicenter CA-11, using the same MUF, you must add the task required for Unicenter CA-11 to the values needed for these other products.
To calculate the number of tasks needed, use the following formula: xcf_tasks = (# of xcf connected Unicenter CA-Jobtracs * 14) + (number of ISPF Unicenter CA-Jobtrac users * 3) + 50 number = xcf_tasks + 14 (for local) + (number of ISPF Unicenter CA-Jobtrac users * 3) + 50. The extra 50 added to each value, 100 total, allows for batch utilities, reports, and some growth in ISPF users. If additional systems are added, you should check these values to ensure that enough tasks are specified. XCFFROM jobname,XCF_group
The XCFFROM keyword defines an XCF group name to use for XCF connections. This name is defined in the DBSIDPR module that is created to access the database. This name is 1-8 characters. In addition, you can define the jobname that connects to the MUF. With Unicenter CA-Jobtrac, we recommend that this be specified as * to allow all job names that use the group to connect. Since these "jobs" may also be TSO user IDs, it is not practical to limit access to the database to a single job name or name prefix. LOGRCV option The CA-Datacom/AD startup option, LOGRCV NO, establishes the creation of the recovery files. We recommend that you use the NO option. By default, this value is set to NEVER, which reuses the log file and does not create the RXX recovery file. LOGRCV YES indicates to use a dedicated tape drive for the recovery file. Since this is not usually the best solution, the LOGRCV NO option indicates that no tape is allocated, and the RXX is created by running a spill job. The RXX recovery files are required to perform forward recovery on a database backup. The DBSPILL member of the Unicenter CA-Jobtrac SAMPJCL provides a sample spill job. For more information about logging and spill processing, see the Reports, Maintenance, and Recovery Guide.
DBSIDPR Parameters
For an application to access a CA-Datacom/AD database, an access module must be created to define the methods to use. During the installation, a DBSIDPR module was created defining the SVC access. If you have a single LPAR, this can be used as is. If you have multiple LPARs, you need to reassemble the DBSIDPR module to include the definitions for connecting using XCF. For more information about modifying and reassembling this module, see the Advantage CA-Datacom/DB Database and System Administrator Guide. For Unicenter CA-Jobtrac, you only need to add the TOGROUP and TOMUF parameters if you are sharing the database. No other parameter changes should be needed. TOGROUP= defines the same group name that was defined in the XCFFROM parameter in the DBDATIN1 startup parameters for the MUF. TOMUF= defines the mufname that was defined in the MUF parameter in the DDBDATIN1 startup parameters for the MUF. The values in the TOGROUP and TOMUF must match the DBDATIN1 values for the database to be accessible. The following is an example of a DBSIDPR modified to include the XCF parameters TOMUF and TOGROUP. TITLE 'DATACOM/AD - SYSTEM ID BLOCK' DBSYSID SVC=246,SUBID= , TOMUF=ADMUF 1,TOGROUP=ADXGRP 1 END x
Alter the CA-Datacom/AD LXX and FXX

CA-Datacom/AD has two files that you may need to adjust for Unicenter CA-Jobtrac, the LXX and the FXX.
LXX
The LXX is the log file for the CA-Datacom database. As distributed the LXX is sized with the assumption that the recovery file, the RXX, will not be created and that the LXX will wrap. As discussed in the overview of components and installation, we recommend that you create the recovery file, and therefore also recommend that you increase the size of the LXX. The size required depends on your workload and how frequently the spill job runs. Unicenter CA-Jobtrac provides you a sample job in member DBSPILL in the Unicenter CA-Jobtrac SAMPJCL data set. The more often you spill the LXX, the smaller the LXX you can have. To help you estimate the LXX size, an MS Excel spreadsheet is available from the Unicenter CA-Jobtrac product page on SupportConnect. We recommend that you download this spreadsheet to assist you with LXX sizing. We recommend that you use a minimum of 300 cylinders. CA-Datacom/AD issues the following message when the LXX is nearly full: DB00308I LOG AREA IS nn% FULL, nnnnn BLOCKS SPILLABLE You can choose to run the spill job at regular intervals such as every hour or to have the job submitted in response to the DB00308I message. Your console automation product or Unicenter CA-Jobtrac AMR facility can be set up to submit the DBSPILL job when the DB00308I message is issued. The default warning percentage in 75%. This percentage is defined in the LOGSPILL keyword in the CA-Datacom/AD CUSMAC(DBDATIN1). If the LXX fills up, all database access stops until you run the spill job. Note: For more information about the spill process, see the Reports, Maintenance, and Recovery Guide.
To resize the LXX file, you need to perform the following steps: 1. Shut down CA-Datacom/AD normally, that is, P ADxxSTRT. 2. Find the DBLXX member of the Unicenter CA-Jobtrac SAMPJCL and review the comments. 3. Rename your existing LXX data set to ...LXX.OLD. 4. Change the //LXX DD statement to specify the new size. You may want to change TRK to CYL to specify the size in cylinders. 5. Locate the input control statement similar to the following: INIT AREA=LXX,BLKSIZE=27998 6. Ensure that the size in the BLKSIZE= matches the block size used for the FXX. 7. Run this DBLXX job. Before restarting CA-Datacom/AD, read the following information about FXX.
FXX
The FXX, known as the Force Log Area, is initialized at installation to support 50 tasks. Unicenter CA-Jobtrac usually requires more than 50 tasks. In a previous topic, you defined the TASKS parameter to CA-Datacom/AD. You need to allow for at least as many tasks in the FXX as were specified in the TASKS keyword. You may want to specify a number larger than the TASKS value to prevent having to change this number in the future. To update the FXX, you need to perform the following steps: 1. Shut down CA-Datacom/AD normally, that is, P ADxxSTRT. 2. Find the DBFXX member of the Unicenter CA-Jobtrac SAMPJCL and review the comments. 3. Locate the input control statement similar to the following: INIT AREA=FXX,BLKSIZE=27998,TASKS=300 4. Specify a TASKS= value at least as large as the value specified in the CA-Datacom/AD TASKS startup parameter. 5. The size in the BLKSIZE= must match the block size used for the LXX. 6. Run this DBFXX job. 7. Restart CA-Datacom/AD.
Modify CA-GSS
Modify CA-GSS
Unicenter CA-Jobtrac uses CA-GSS facilities to extend its capabilities and to provide you with fully customizable support for job scheduling. Also, Unicenter CA-Jobtrac information is made available to other CA-GSS client software, including that provided by you. For more information, see the CA Common Services Getting Started guide.
Step 1: Modify JCL

If the Unicenter CA-Jobtrac load library (CAILIB) is not in a LINKLIST library, include it as a STEPLIB in the CA-GSS PROC. Also if the CA-Datacom/AD CUSLIB and CAILIB are not in LINKLIST, they also need to be added to the STEPLIB. The following example shows the STEPLIB for CA-GSS when no libraries are in LINKLIST: //STEPLIB // // // DD DD DD DD DSN=cai.gss.CAILIB,DISP=SHR DSN=cai.jobtrac.CAILIB,DISP=SHR DSN=cai.datacom.CUSLIB,DISP=SHR DSN=cai.datacom.CAILIB,DISP=SHR
As needed, you can predefine the Unicenter CA-Jobtrac tokens to CA-GSS. If you do not, it will be dynamically allocated when needed. Multiple DD statements, defining multiple checkpoint data sets, can be specified if desired. The issuer of ADDRESS JOBTRAC commands will specify which token (and hence, which Unicenter CA-Jobtrac) will be affected by the commands. Be sure that the token part of the ddname (n of JOBTRACn) matches the Unicenter CA-Jobtrac token ID for the associated Unicenter CA-Jobtrac. An example follows: //JOBTRACY DD DUMMY //JOBTRAC3 DD DUMMY If you are planning to use the cross-platform scheduling feature, it requires additional JCL changes and parameters. For more information, see Cross-Platform Scheduling on page 232. We recommend that the additional changes be made after the initial setup of CA-GSS is completed.
Modify CA-GSS
Step 2: Modify CA-GSS Parameters

As needed, modify the CA-GSS initialization parameters that affect CA-GSS' Unicenter CA-Jobtrac support. The JOBTRAC member of the CA-GSS PPOPTION data set contains examples of these parameters. Remember that: Most parameters in the JOBTRAC member are commented out. To activate one of them, replace its leading asterisk (*) with a blank. You can copy the JOBTRAC member's contents to your RUNPARM member, or you can simply provide an INCLUDE JOBTRAC statement. Parameters You Need to Modify on page 168 provides a summary of each parameter you need to modify. For a complete description of a CA-GSS initialization parameter, see the CA Common Services documentation.
Parameters You Need to Modify

ADDRESS Makes the ADDRESS environments provided on the Unicenter CA-Jobtrac distribution tape as load modules available to REXX IMODs. Remember that: CA-distributed IMODs expect the address name JOBTRAC. If you use another name, use the ALTNAME parameter to define JOBTRAC. The MAXTASK argument limits the number of IMODs that may simultaneously use the ADDRESS environment. The names of load modules reflect the names as shipped on the Unicenter CA-Jobtrac tape. You must ensure that these load modules reside in an APF-authorized library that is accessible to CA-GSS.
ISET Identifies ISETs (IMOD libraries that are included on the Unicenter CA-Jobtrac tape).
Modify CA-GSS
JESNODE Identifies the JES2 NJE node name in a multi-CPU environment where this copy of CA-GSS is executing. 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). WTO Executes the MSG_TRAC845 IMOD whenever the Unicenter CA-Jobtrac TRAC845E message is issued. This IMOD, which is provided in the CA-GSS sample ISET, 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, with or without shared DASD or running Unicenter CA-Jobtrac in an NJE environment, you may want to activate GoalNet so that Unicenter CA-Jobtrac can exchange information between multiple systems. For more information setting up GoalNet, see the CA Common Services documentation.
Modify CA-GSS
Step 4: (Optional) Install REXX IMOD Sample Source

The Unicenter CA-Jobtrac installation tape contains a library of REXX SAMPLES that can be used with Unicenter CA-Jobtrac and CA-GSS. To install these samples: 1. Modify job REXXCOPY in SAMPJCL to specify the volser and tape unit type for the Unicenter CA-Jobtrac installation tape, where indicated. 2. Submit REXXCOPY. This job will do the following: a. Allocate PDS JT.SAMPREXX. b. Copy the samples from the tape to JT.SAMPREXX. c. Allocate VSAM ISET JT.SAMPISET. d. Copy the IMODS from JT.SAMPREXX to JT.SAMPISET. e. Compile the IMODs and place them in Test status. Test status prevents the IMODs from loading automatically in CA-GSS. 3. Add an ISET statement for JT.SAMPISET to the RUNPARM, JOBTRAC, or ISET member of the CA-GSS PPOPTION data set. A sample ISET statement for the data set would look like the following: ISET JOBTRAC DSN cai.JT.SAMPISET LOAD DESC /CA-JOBTRAC SAMPLE IMODs/ SSID isrv For specific RUNPARM control statement formats, see the CA Common Services documentation.
Customize SYS1.PARMLIB
Unicenter CA-Jobtrac extracts tracking information during event queuing, execution, and termination. It uses SMF type-30 records and builds dynamic interfaces to exits IEFUJV and IEFU83. Exit IEAVMXIT is used to provide AMR (Automatic Message Recognition) services. This section describes how to set up these exits. Setting up IEAVMXIT is described on Set Up AMR Support on page 208. Type-30: SMF type-30 records are created at job step termination and at job termination. Unicenter CA-Jobtrac uses these records to monitor job completion. Types 15 and 64: SMF record types 15 and 64 monitor data set activity. Unicenter CA-Jobtrac uses these records for data set triggering. Type-26: Job purges create SMF type-26 records. Unicenter CA-Jobtrac uses these records to monitor purged jobs. Suppressing the Writing of Records: If you prefer not to keep the SMF records after Unicenter CA-Jobtrac uses them, you can suppress the writing of the record to the SMF data set by coding an IEFU83, IEFU84, or IEFU85 exit. The SAMPJCL library contains a sample IEFU83 exit. 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. Remember that if you suppress the records, they are not captured in your SMF data sets. The system still creates the records in an SMF buffer, Unicenter CA-Jobtrac reads them, and then Unicenter CA-Jobtrac deletes them. Important! If you specify a JES subsystem ('SUBSYS(JES')), you must include the SMF record types and exits described in the following procedure. If you do not, Unicenter CA-Jobtrac will not track events correctly.
Procedure: Follow these steps to customize SYS1.PARMLIB member SMFPRMxx and set up required exits: 1. Make sure exits IEFUJV and IEFU83 are set up in your system. You can use an IEFBR14 dummy exit for any exit not already in your system. The sample member LINKSMF in the SAMPJCL library shows how to set up a dummy exit. All exits, including IEFBR14 dummies, should be linked as RENT and REUS. 2. Make sure exits IEFUJV and IEFU83 are included in LPALIB. Exit IEFUJV must be in LPALIB to ensure proper Unicenter CA-Jobtrac operation. Exit IEFU83 must be in LPALIB for proper control of dynamic DSN triggering tables. Unicenter CA-Jobtrac operates correctly but with less function when IEFU83 is not present. 3. Make sure that Unicenter CA-Jobtrac will function with the SMF configuration in SYS1.PARMLIB member SMFPRMxx. The minimum configuration is shown in the following:
SYS(TYPE(15,26,3 ,64),EXITS(IEFUJV,IEFU83)) SUBSYS(STC,EXITS(IEFU29,IEFU83,IEFU84))
4. Perform an IPL with CLPA before starting Unicenter CA-Jobtrac if you added any exits to SYS1.LPALIB. 5. Suppress any of the following record SMF types 15, 26, 30, or 64 if you do not want to record them by coding an IEFU83, IEFU84, or IEFU85 exit. The Unicenter 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. Perform an F JOBTRAC,BACK command before refreshing SMF if you are refreshing SMF exits dynamically.
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,IEFUJV, IEFUJP,IEFUSO,IEFUTL,IEFU29),INTERVAL( 15 ),DETAIL) SUBSYS(STC,EXITS(IEFU29,IEFU83,IEFU84), 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 / / / / / / / / / /
Set Up Default Authorization
Set Up Default Authorization

The Unicenter CA-Jobtrac TRACAUTH table is used to do the following: Define the Unicenter 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 Unicenter 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 Reports, Maintenance, and Recovery Guide. Using @JOBTRAC?: A user ID assigned to the Unicenter CA-Jobtrac started task must be added to the TRACAUTH table to allow @JOBTRAC (ADDRESS JOBTRAC) to pass security checking. Important! Before modifying the TRACAUTH table for your needs, you should assemble and link it for use with the Unicenter CA-Jobtrac verification procedure, IVP. If you do not, the IVP will not work properly. The necessary procedures follow. 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 Unicenter CA-Jobtrac is started. If you are modifying the table when Unicenter CA-Jobtrac is running, issue the following command to load the modified table: F taskname,AUTH Note: For more information setting up custom authorizations, see TRACAUTH security in the Reports, Maintenance, and Recovery Guide.
Set Up the JES3 Held Job Class
Set Up the JES3 Held Job Class

Requirement: If you have not already assigned a sysout hold class for Unicenter 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 Unicenter 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 the following: ,DEST=LOCAL
Define Location Information (DYNAMLOC) and Initiation IMODs

You can define location-specific information (libraries, names, global initiation IMODs) in the DYNAMLOC member in the PPOPTION data set. The libraries no longer need to be defined to the Unicenter CA-Jobtrac started task and the user CLISTs. When Unicenter CA-Jobtrac starts, the DYNAMLOC member is read and a table is built in storage of all definitions. All libraries are immediately allocated to the Unicenter CA-Jobtrac started task. Libraries are allocated as needed to other accessors, such as TSO/ISPF. The definitions can be rescanned at any time through the use of the REFRESHLOC command. When using REFRESHLOC, it is NOT necessary to precede the ALLOC statement by a DEALLOC statement for the same DDNAME. When the ALLOC statement is encountered, the DEALLOC statement is implied. DYNAMLOC Statements ALLOCDDNAME=TRACSnnn,DATASET=dataset name TRACJnnn DSN TRACRnnn TRACDnnn TRACTnnn TRACMnnn ,NAME=location name ,VOLSER=volser
DDNAME can be one of TRACSnnn, TRACJnnn, TRACRnnn, TRACDnnn, TRACTnnn, or TRACMnnn, where nnn is the location ID (0-254). NAME is the location name on the Event Execution Detail panel and can be used instead of TRACAUTH to define location names. The location name can be 16 characters with only one name per location. DSN is a synonym for DATASET.
Optionally, other data sets may be concatenated to each currently allocated DD (except TRACTnnn) by using the following parameters: CONCATDDNAME=TRACSnnn,DATASET=dataset name TRACJnnn DSN TRACRnnn TRACDnnn TRACMnnn ,VOLSER=volser
Note: If concatenated data sets are edited using the Unicenter CA-Jobtrac ISPF interface and saved, the member is saved to the first data set in the concatenation. This is standard IBM practice. DEALLOCDDNAME=TRACSnnn TRACJnnn TRACRnnn TRACDnnn TRACTnnn TRACMnnn
DDNAME is as in the ALLOC statement. This statement can be used to free a library for maintenance and so forth. Note: If the DDNAME has more than one data set allocated in concatenation, all of the data sets in the concatenation will be released from the DDNAME. If a single data set is to be removed from a concatenation, the DDNAME should be reallocated using the ALLOC keyword instead. SET INITIMOD=imodname NONE
This command sets the default global initiation IMOD for subsequently defined locations. NONE indicates no global initiation IMOD is desired. The IMOD name can be eight characters long. This value will be applied to all subsequent locations until explicitly resent by another 'SET INITIMOD=..' statement. For more information about IMOD requirements, see the Extended Scheduling Services Guide.
INCLUDEmembername
The location definitions can be split between multiple members and referenced by INCLUDE statements. When INCLUDE statements are parsed, the member referenced is opened and the statements are read before any further statements of the original member. INCLUDE can be nested. DYNAMLOC does not allow concatenation DDs for locations. 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.TRACJ ,NAME=LOC ALLOC DD=TRACS ,DSN=your.TRACS ALLOC DD=TRACD ,DSN=your.TRACD ALLOC DD=TRACT ,DSN=your.TRACT ALLOC DD=TRACR ,DSN=your.TRACR ALLOC DD=TRACM ,DSN=your.TRACM CONCAT DD=TRACJ ,DSN=your.TRACJC CONCAT DD=TRACS ,DSN=your.TRACSC Member named LOC001 contains the following statements: SET INITIMOD=imodname|NONE ALLOC DD=TRACJ 1,DSN=your.TRACJ ALLOC DD=TRACS 1,DSN=your.TRACS ALLOC DD=TRACD 1,DSN=your.TRACD ALLOC DD=TRACT 1,DSN=your.TRACT ALLOC DD=TRACM 1,DSN=your.TRACM ALLOC DD=TRACR 1,DSN=your.TRACR 1 1 1 1 1 1,NAME=LOC
You can find samples of DYNAMLOC, LOC000, and LOC001 in the SAMPJCL library.
Using INCLUDE statements does not allow for continued lines. Most environments do not require them. You can use continuations if all the statements are placed in the DYNAMLOC member itself as follows. The member name in PPOPTION must be DYNAMLOC. ALLOC DD=TRACS ,DATASET=your.SCLLIB, NAME='LOCATION NAME',VOLSER=VOLSER ALLOC DD=TRACT ,DATASET=your.TRACT , VOLSER=VOLSER ALLOC DD=TRACJ ,DATASET=your.TRACJ , VOLSER=VOLSER ALLOC DD=TRACD ,DATASET=your.DOCLIB, VOLSER=VOLSER ALLOC DD=TRACS 6,DATASET=your.TRACS 6, VOLSER=VOLSER ALLOC DD=TRACT 6,DATASET=your.TRACT 6, VOLSER=VOLSER ALLOC DD=TRACJ 6,DATASET=your.TRACJ 6, VOLSER=VOLSER
Update Your TSO Procedures or CLIST

To access the Unicenter CA-Jobtrac ISPF interface, several steps must be performed. 1. Update your TSO procedure. 2. Customize the Unicenter CA-Jobtrac CLIST. 3. Update your ISPF master panel or site-specific application panel to include Unicenter CA-Jobtrac as an option. Updating Your TSO Procedure: The Unicenter CA-Jobtrac CLIST library CAICLIB must be added to your SYSPROC DD concatenation. //SYSPROC DD DSN=your.ispf.clist,DISP=SHR existing ISPF library // DD DSN=CAI.jobtrac.CAICLIB,DISP=SHR CA-Jobtrac CAICLIB You need to update your TSO PROC STEPLIB DD to concatenate the load libraries for Unicenter CA-Jobtrac, CA-Datacom/AD, and other optional components unless these libraries have been added to the system linklist. Linklisted data sets are available to everyone, and therefore do not need to be included. The following sample shows how the STEPLIB would look if none of the libraries were in the linklist. //STEPLIB // // // // // // DD DD DD DD DD DD DD DSN=your.ispf.loadlib,DISP=SHR DSN=CAI.jobtrac.CAILIB,DISP=SHR DSN=CAI.datacom.CUSLIB,DISP=SHR DSN=CAI.datacom.CAILIB,DISP=SHR DSN=CAI.ca-gss.CAILIB,DISP=SHR DSN=CAI.ca cpm.CAILIB,DISP=SHR DSN=CAI.ca-11.CAILIB,DISP=SHR existing ISPF library CA-Jobtrac CAILIB CA-Datacom CUSLIB CA-Datacom CAILIB CA-GSS CAILIB (optional) CA CPM CAILIB (optional) CA-11 CAILIB (optional)
Unicenter CA-Jobtrac and CA-Datacom/AD load libraries must be included or in the linklist. CA-GSS and CA CPM are included with Unicenter CA-Jobtrac and should be included if you are planning to use the ISPF facilities of these components and the libraries are not in linklist. The Unicenter CA-11 CAILIB should only be included if Unicenter CA-11 is installed in your system, and the Unicenter CA-11 CAILIB is not linklisted. Customize the Unicenter CA-Jobtrac CLIST: The Stage2 process added a CLIST to your SAMPJCL that can be used to access Unicenter CA-Jobtrac. JTCLIST uses LIBDEFs to allocate the panels, messages, tables, and link libraries to run Unicenter CA-Jobtrac. This CLIST was customized to include the libraries needed to interface with CA CPM and Unicenter CA-11, if you specified these options. Review the JTCLIST in SAMPJCL and move it a CLIST library that will be available to ISPF.
The following sample shows the CLIST with the Unicenter CA-11 and CA-CPM libraries included: PROC / SAMPLE CA-JOBTRAC CLIST W/LIBDEFS / CONTROL NOMSG / / / FREE ANY OUTSTANDING ALLOCATIONS TO CA-JOBTRAC DATASETS / / / FREE DD(JOBTRACY,CAPTURE) FREE DD(TRACJ ,TRACT ) FREE DD(TRACJ 1,TRACT 1) FREE DD(TRACM ,TRACM 1) FREE DD(TRACS ,TRACS 1) FREE DD(TRACD ,TRACR ) FREE DD(DATEFILE) FREE DD(CPMSKIP1) CONTROL MSG / / / ALLOCATE THE DATASETS THAT ARE ONLY REQUIRED WHEN / / USING CA-JOBTRAC / / / ALLOC DD(JOBTRACY) DUMMY / y = CA-Jobtrac Token / ALLOC DD(CPMSKIP1) DUMMY / REMOVE TO GET CPM SERVER LIST / / WHEN THERE IS ONLY ONE SERVER / ALLOC DD(CAPTURE) SHR DA('APC.DEVJT.CHD4 .BTINS.CAPTURE') ALLOC DD(DATEFILE) SHR DA('APC.DEVJT.CHD4 .BTINS.DATELIB') / / / ALLOCATE LIBDEFS NEEDED TO ACCESS / / CA-JOBTRAC / / CA CPM / / CA-11 / / / ISPEXEC LIBDEF ISPMLIB DATASET ID( + 'APC.DEVJT.CHD4 .BTINS.JT.CAIISPM' + / CA-JOBTRAC / 'APC.LV2.CPM3 .CAIISPM' + / CA CPM / 'APC.DEVCA11.CAIISPM' + / CA-11 / ) ISPEXEC LIBDEF ISPPLIB DATASET ID( + 'APC.DEVJT.CHD4 .BTINS.JT.CAIISPP' + / CA-JOBTRAC / 'APC.LV2.CPM3 .CAIISPP' + / CA CPM / 'APC.DEVCA11.CAIISPP' + / CA-11 / ) ISPEXEC LIBDEF ISPTLIB DATASET ID( + 'APC.LV2.CPM3 .CAIISPT' + / CA CPM / ) ISPEXEC LIBDEF ISPLLIB DATASET ID( + 'APC.LV2.CPM3 .CAIPDSE' + / CA CPM / )
/ / AS MENTIONED IN THE INSTALL GUIDE, WHEN USING LIBDEFS / YOU MUST USE THE PASSLIB PARM ON THE ISPF SELECT / STATEMENT USED TO INVOKE THE APPLICATION. IF YOU / FAIL TO DO THIS, THE CHANGED ALLOCATIONS ARE NOT / AVAILABLE TO THE APPLICATION. FOR CA-JOBTRAC, IF IT / DOES NOT HAVE BOTH THE PANEL AND MESSAGE LIBRARY, / YOUR SCREEN WILL FLASH AND RETURN TO THE SCREEN YOU / CAME FROM OR THE ISPF MAIN MENU. / ISPEXEC SELECT PGM(GJTRVSPF) NEWAPPL(JBT) PASSLIB / / NOW THAT YOU ARE FINISHED IN CA-JOBTRAC (FOR RIGHT NOW) / RESTORE THE ALTERED ALLOCATIONS BACK TO LOGON TIME / DEFAULTS SO FUTURE EXECUTIONS OF THIS CLIST DO NOT / FAIL. THIS IS DONE BY EXECUTING THE LIBDEF AGAIN / WITH ONLY THE DDNAME AS A PARM. / ISPEXEC LIBDEF ISPMLIB ISPEXEC LIBDEF ISPPLIB ISPEXEC LIBDEF ISPTLIB ISPEXEC LIBDEF ISPLLIB / / FREE DIRECTLY ALLOCATED DATASETS / FREE DD(JOBTRACY,CAPTURE) FREE DD(TRACJ ,TRACT ) FREE DD(TRACJ 1,TRACT 1) FREE DD(TRACM ,TRACM 1) FREE DD(TRACS ,TRACS 1) FREE DD(TRACD ,TRACR ) FREE DD(DATEFILE) FREE DD(CPMSKIP1) / END
/ / / / / / / / / / / / / / / / /
/ / /
Location Data Sets: We recommend that you use DYNAMLOC to define your location data sets (SCL, JCL, DOC, Temp JCL, and so forth). DYNAMLOC reduces logon time by only allocating the data sets to your TSO/ISPF session when they are accessed. If you chose not to use DYNAMLOC, you must define all your location data sets that will be used in either your TSO logon procedure or the JTCLIST CLIST. Adding Unicenter CA-Jobtrac to Your ISPF Main Menu: To add Unicenter CA-Jobtrac to your ISPF main menu, you must update your ISR@PRIM or equivalent main ISPF menu. You can use member SAMPPRIM in your SAMPJCL library as an example of the necessary additions. The following shows the TRANS statement with the J option added for Unicenter CA-Jobtrac. &ZSEL = TRANS( TRUNC (&ZCMD,'.') ,'PANEL(ISPOPTA)' 1,'PGM(ISRBRO)' 2,'PGM(ISREDIT)' 3,'PANEL(ISRUTIL)' 4,'PANEL(ISRFPA)' 5,'PGM(ISRJB1) PARM(ISRJPA) NOCHECK' 6,'PGM(ISRPTC)' 7,'PGM(ISRYXDR) NOCHECK' => J,'CMD(%JTCLIST) NEWAPPL(JBT)' / CA-Jobtrac Example C,'PGM(ISPTUTOR) PARM(ISR 5)' T,'PGM(ISPTUTOR) PARM(ISR )' ' ',' ' X,'EXIT' ,'?' )
Set Global Options
Set Global Options

Unicenter CA-Jobtrac global options describe global values and the environment in which Unicenter CA-Jobtrac operates. Unicenter CA-Jobtrac global options are set using the Unicenter CA-Jobtrac global options panels and the JOBTRAnn member. Some options are set using the global options panels only, some by the JOBTRAnn member only, and some options are set using either one. Additionally, some of the options set using JOBTRAnn are displayed on the global options panels, but they cannot be set on the panels. Note: For more information about the JOBTRAnn member, see customization job streams in this guide. Requirement: To access the options panels, the Unicenter CA-Jobtrac internal control blocks must be initialized. Since some of these options, such as the GSS Subsys name, should be specified before starting Unicenter CA-Jobtrac for the first time, we recommend that you run the VINITx procedure with PARM=INIT to initialize the Unicenter CA-Jobtrac internals without starting the Unicenter CA-Jobtrac started task. The VINITx procedure was set up in the chapter "Customization Job Streams." The following command can be issued to run VINITx. S VINITx,PARM=INIT For information about using VINITx, see the chapter "Startup and Verification." Follow these steps to change global options using the global options panels: 1. Start Unicenter CA-Jobtrac. For information about starting Unicenter CA-Jobtrac, see the chapter "Startup and Verification." 2. Issue the SYS OPTS command from any Unicenter CA-Jobtrac display to display the Global Options Menu. 3. Select option A, All of the Above. The Unicenter CA-Jobtrac Global Options panel appears, which is the first in the series of global options panels. Instead of option A, you can select a specific options panel if you want to change a selected option. 4. Change entries on the CA-Jobtrac Global Options panel so that the options are set as required for your installation. For a description of the options, see Options on the CA-Jobtrac Global Options Panel on page 186. Press Enter to save your changes, or press the End PF key to exit without saving your changes. The Sysout Capture Options panel appears.
Set Global Options
5. Change entries on the Sysout Capture Options panel so that the options are set as required for your installation. For a description of the options, see Options on the Sysout Capture Options Panel on page 195. Press Enter to save your changes, or press the End PF key to exit without saving your changes. The Library Definitions panel appears. 6. Change entries on the Library Definitions panel so that the options are set as required for your installation. For a description of the options, see Options on the Library Definitions Panel on page 199. Press Enter to save your changes, or press the End PF key to exit without saving your changes. Press the END PF key to return to the panel from which you accessed the global options panels. 7. Update Unicenter CA-Jobtrac internal components with the new global options by issuing one of the following operator commands (for more information about operator commands, see the Operator Guide): F taskname,OPTS[=nn|00] F taskname,JICAUPD Optionally, replace nn with a two-digit numeral specifying a JOBTRAnn member where nn matches the nn in JOBTRAnn. The default is member JOBTRA00. Sample Global Options Menu: The following panel shows a sample Global Options Menu.
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
Set Global Options
Options on the CA-Jobtrac Global Options Panel

The following panel shows a sample CA-Jobtrac Global Options panel.
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) 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 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 Email Notification (Y/N) => N Service Desk Report (Y/N) => Y Multisys Sync Dormancy => 999 SYSID Priority List CPU 1 => CPU 2 => CPU 3 => Prompt on Max Lines (Y/N) => N Auto-Queue Event Classes => CA-Librarian Program Name => AFOLIBR REXX Maximum Time (HHMM) => 15 REXX Retry Maximum Count => 999 ISERVE STC Procedure Name => GSSA Cross Node Query Limit =>
Press ENTER to update options or END to exit without making changes.
The panel contains the following fields: Date Format Specifies the date format to be used on some of the Unicenter CA-Jobtrac displays and in SCL (Schedule Control Language). A Specifies to accept dates in the American format of mm/dd. I Specifies to accept dates in the International format of dd/mm. Note: For the date format field for each TSO session, see the CA-Jobtrac User Profile panel in the Operator Guide. IPL Name Prompt Indicates whether the operator is to be prompted at IPL time. Y Specifies to direct Unicenter CA-Jobtrac to issue the TRAC400A and TRAC401A WTORs. N Specifies to direct Unicenter CA-Jobtrac to issue message TRAC010I with no prompt. For descriptions of messages, see the Message Guide.
Set Global Options
AUTO-SCHD Allowed Specifies whether the AUTO-SCHD feature is supported. For complete information about the AUTO-SCHD feature, see the Operator Guide. Y Specifies to direct Unicenter CA-Jobtrac to dynamically add any event that is submitted (by any means) with a special AUTO-SCHD character to the Unicenter CA-Jobtrac current schedule if the event is not already scheduled. N Specifies to prevent addition of AUTO-SCHD events to the Unicenter CA-Jobtrac current schedule. For more information, see AUTOC on page 133 and AUTOQ on page 134. Restart Support Specifies the restart/rerun system to be used. The following values are available: R Specifies to direct the restart system (Unicenter CA-11) to perform step restarts. For more information, see the Unicenter CA-11 documentation. N Specifies that no restart automation is in use. Nodelete Error Message Specifies whether to direct Unicenter CA-Jobtrac to send the following nondeletable message to the operator console when a scheduled Unicenter CA-Jobtrac event ends with an abend, JCL error, condition code exception, or NOT CATALOGED 2 error: TRACWARN - JOB jobname STEP:stepname ABENDED, CODE=abcode (or COND CODE=ccode or CATALOG ERROR NOTED) If a reader JCL error occurs or an operator purges an event, the following FLUSHED message is issued: TRACWARN - JOB jobname FLUSHED, DID NOT EXECUTE. Y Specifies to send these messages. N Specifies to suppress these messages. Archive Print Class Specifies a print class if you archive to print. Microfiche users should be aware that Unicenter 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.
Set Global Options
SPF Sysout Print Class When viewing sysouts in Unicenter CA-Jobtrac/ISPF, you can print a copy of any listing. The sysout class you specify in this field is the output class of the TSO copy. Capture Sysout Specifies your method of capturing sysout: Y Specifies to direct Unicenter CA-Jobtrac to capture sysouts for online viewing. N Specifies to direct Unicenter CA-Jobtrac to bypass sysout capture. (You should specify N if you want Unicenter CA-View to handle the sysout capture.) The capture classes are defined on the Sysout Capture Options panel. Even if you set this field to N, you must specify a primary capture class. It is used for all schedule captures. Unicenter CA-Jobtrac attempts to spool ANY SYSOUT of a Unicenter CA-Jobtrac-submitted event if Y is selected in the global options. All output classes should be specified in the Sysout Capture Options to be spooled properly. If not defined in the Sysout Capture Options, Unicenter CA-Jobtrac issues these warning messages: TRAC 98W WAITING FOR SYSOUT, JOB: eventname NONE FOUND IN ANY CLASS YET TRAC 99W SYSOUT NOT FOUND, eventname BYPASSED. JES Command Character Defines the prefix character you will use to indicate that a console command is to be processed by JES. This option is set in member JOBTRAnn (see the chapter "Customization Job Streams"). You cannot change this option on the CA-Jobtrac Global Options panel.
Set Global Options
Holiday Action Time Sets a time range for holiday days. This setting affects events already on the current schedule. The setting does not affect a schedule being loaded to the current schedule or an event with a date of +1 and a time of ASAP specified. For more information about holidays, see the holiday information in the Schedule Creation Guide. The following figure shows an example of how this option affects holiday scheduling:
Holiday Action Time global option set to Midnight 8 Thursday Friday, a holiday Event scheduled with +1 7 time, and any holiday Event is scheduled because Schedule with no Thursday is a valid workday, holiday action and the target time is less specified loaded on than the holiday action time. Friday at any time. Schedule will not load, unless a specific holiday action of S, O, W, or N is Event scheduled with used. This is regardless +1 date, 9 time of the setting of and any holiday the holiday action action time global option. Event is scheduled because Thursday is a valid workday, but since the target time is greater than the holiday action time, an M(H) holiday hold dependency is assigned to the event. Event scheduled with +1 date, ASAP time, and any holiday action Event is scheduled because Thursday is a valid workday, but since the target time is greater than the holiday action time, an M(H) holiday hold dependency is assigned to the event. 8 .
Set Global Options
REXX Retry Interval Specifies the amount of time an environmental dependency waits before executing again. This option is used with the REXX Retry Maximum Count option. This option applies to environmental dependencies. For information about using this option effectively, see the REXX information in the Extended Scheduling Services Guide. ISERVE Subsystem Name Specifies the name of the CA-GSS IMOD Facility (CA-GSS subsystem) to send REXX IMOD and environmental dependency requests to. You can have multiple subsystems defined. The Unicenter CA-Jobtrac REXX facility checks whether the subsystem is running. If not running, the facility attempts to start the subsystem. If the facility cannot start the subsystem, an error message is issued. NJE Node Specifies whether to activate the Unicenter CA-Jobtrac NJE support for this instance of Unicenter CA-Jobtrac on this system image. If you specify Y, the NJE Node Tokens field becomes significant. NJE Node Tokens A Unicenter CA-Jobtrac token is the x in JOBTRACx DD statement. The token identifies and differentiates individual copies of Unicenter CA-Jobtrac. In this field, you specify which of the Unicenter CA-Jobtrac events are recognized by this Unicenter CA-Jobtrac. This is done by listing up to 39 tokens. If you leave this field blank, all tokens (that is all events from all Unicenter CA-Jobtracs) are processed by this Unicenter CA-Jobtrac. If you leave the field blank, do one of the following: Only start up one NJE-capable Unicenter CA-Jobtrac on any single system image Specify non-overlapping tokens for each Unicenter CA-Jobtrac running
The JES /*ROUTE or /*XEQ statements identify an event as an NJE event. If you explicitly specify tokens and you submit NJE jobs to the submitting node itself, you should specify the token of the submitting Unicenter CA-Jobtrac itself in the token list. The specified NJE nodes apply only to the NJE events for the Unicenter CA-Jobtracs that are specified as being NJE nodes. All other Unicenter CA-Jobtrac instances recognize only their own tokens. Global Termination IMOD Specifies the name of the global termination IMOD. The use of a global termination IMOD is optional. The global termination IMOD executes after each event. The execution takes place immediately after Unicenter CA-Jobtrac recognizes the termination of an event, but before Unicenter CA-Jobtrac calls user exit TRACX09 or releases successors.
Set Global Options
This order of execution permits the IMOD to alter the status or attributes of the event from within the IMOD using @JOBTRAC (ADDRESS JOBTRAC). For example, you can add an output release dependency to prevent the release of successors until some user action is taken. The execution of the IMOD does not prevent Unicenter CA-Jobtrac from processing other events. Consequently, multiple instances of the global termination IMOD can execute at the same time for different events. Hold ABENDing Output Specifies whether to direct Unicenter CA-Jobtrac to issue a $HJnnnn message immediately at termination for any event that ends in an abend, condition code check, or catalog error. This prevents accidental printing of output. Y Specifies to issue the $HJnnnn message. N Specifies not to issue the $HJnnnn message. Catalog Error Check Defines the Unicenter CA-Jobtrac response to IBM messages indicating catalog errors in a batch job. Each of the four characters in the field can be set to Y (yes) or N (no) and correspond to the positional codes 2RUD, which are described in the following: 2 Not cataloged 2 R Not recataloged U Not uncataloged D Not deleted If the code is set to Y, Unicenter CA-Jobtrac checks for these messages in captured sysouts. If the message is found, Unicenter CA-Jobtrac imposes an output release dependency (code O) on the event. 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, Unicenter CA-Jobtrac will not check for these messages.
Set Global Options
Email Notification Specifies whether to send emails. For complete information about the email feature, see the Extended Scheduling Services Guide. Y Specifies to direct Unicenter CA-Jobtrac to send emails at predetermined events. N Specifies to disable the email feature. For more information, see the Extended Scheduling Services Guide. Service Desk Report Specifies whether to open Unicenter Service Desk requests for selected jobs that have unsuccessful completion and for other Unicenter CA-Jobtrac problems that may have a major impact. Y Specifies to open Unicenter Service Desk requests. N Specifies to disable the Unicenter Service Desk feature. Multisys Sync Dormancy This option is used only in multi-system installations. A Unicenter CA-Jobtrac started task runs on each system in a shared JES spool environment. If for any reason the primary system (the one designated to submit events) fails, the secondary system (the one next in priority) prompts the operator and requests dynamic transfer of primary duties (event submission, sysout capture, and so on) to the next system. 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. This option is set in member JOBTRAnn (see the chapter "Customization Job Streams"). You cannot change this option on the CA-Jobtrac Global Options panel.
Set Global Options
SYSID Priority List Indicates the priority sequence of the SMF IDs for one to three systems in a shared spool environment. System 1 is the primary CPU and assumes the duties of event submission and sysout management. System 2 is the secondary system and assumes control if system 1 loses communication with system 2. If both system 1 and system 2 are down, system 3 takes control. If primary roles are transferred and the failing system comes back up, it assumes a secondary role until the operator issues an ACTSYS=sysid command to restore or reassign the primary system. For information about switching primary systems, see the Reports, Maintenance, and Recovery Guide. This option is set in member JOBTRAnn (see the chapter "Customization Job Streams"). You cannot change this option on the CA-Jobtrac Global Options panel. Prompt On Max Lines Specifies whether to issue a TRAC196A WTOR each time it reaches the line limit for a single job in a given class. 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 195). Y Specifies to issue the WTOR. N Specifies to suppress the WTOR. Auto-Queue Job Classes Specifies up to eight auto-queue job classes for external submission of JCL for jobs scheduled by Unicenter CA-Jobtrac with dependency code Q. 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. For information about using auto-queue job classes, see the Operator Guide. This option is set in member JOBTRAnn (see the chapter "Customization Job Streams"). You cannot change this option on the CA-Jobtrac Global Options panel. CA-Librarian Program Name In installations that use AllFusion CA-Librarian for JCL editing and submission, the Master Library utility program has a customer-defined program name. This field indicates the batch utility program name. This option is set in member JOBTRAnn (see the chapter "Customization Job Streams"). You cannot change this option on the CA-Jobtrac Global Options panel.
Set Global Options
REXX Maximum Time Indicates the maximum amount of elapsed time a REXX IMOD or environmental dependency can run before it is considered to be in a loop. If the maximum amount of time is exceeded, the REXX IMOD or environmental dependency is canceled. Use zero to denote there is no time limit. For information about using this option effectively, see the REXX information in the Extended Scheduling Services Guide. REXX Retry Maximum Count Indicates the number of times an environmental dependency executes, trying to satisfy its condition. This option is used with the REXX Retry Interval option. This option applies to environmental dependencies. For information about using this option effectively, see the REXX information in the Extended Scheduling Services Guide. ISERVE STC Procedure Name Identifies the name of procedure to use to bring up the subsystem if the subsystem specified in the ISERVE Subsystem Name field is not running. Cross Node Query Limit When using the Cross Node Query panel, to query events across multiple NJE nodes, a time limit for the query can be imposed. This field specifies a global time limit for the query. Specify the time limit in minutes, up to two digits. When the time limit expires, the query ends and the information obtained to that point appears. A user can also specify a local time limit. If the user's specified time limit is more than the global time limit, the global time limit is used. If you leave this field blank or specify 0, no time limit is imposed.
Set 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. How the JES Hold Output Command Affects Sysout Capture: The JES hold output command is issued as soon as possible. When this occurs depends on if you are using the Unicenter CA-Jobtrac sysout capture feature. The following table explains when the command is issued: Using the 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, while the job is still running. Hold output commands keep output writers from accessing the output. Output writers include the TSO OUTPUT command (that report the job has no held output at some levels) and capture packages such as Unicenter CA-View or Unicenter CA-Spool. Packages such as Unicenter CA-SYSVIEW can view the output. Unicenter CA-Jobtrac cannot hold the job at the moment the job fails, or it could not capture the job's output. Instead, Unicenter CA-Jobtrac holds the job at the point that the capture subtask is told to begin work on it. This can be several seconds after the job ends, so nonheld sysout could be printed or spooled to some other writer. A better approach in this case is to ensure that all the sysouts created by your Unicenter CA-Jobtrac jobs are held sysouts. Then specify the Unicenter CA-Jobtrac sysout capture options to requeue the output to the original class if you desire. The sysout capture processor will detect the failure and will leave the output from failed jobs alone (in the sysout held class). Note: For more information, see CAPDMPS on page 134. First Definition: The first definition (class 1) is the primary definition. It is used for all schedule captures. The first Output Capture Class field must be specified, even if you are not capturing sysout (Capture Sysout field on the CA-Jobtrac Global Options panel set to N). Class A is a good class to use since it is not held anywhere, and Unicenter CA-Jobtrac does not capture nonheld sysout.
Yes
Set Global Options
Using Unicenter CA-View: If you are using Unicenter CA-View to capture your sysout, see Use Other Sysout Capture Products on page 230 for more information about defining the writer options. The following panel shows a sample Sysout Capture Options panel.
CA-Jobtrac COMMAND ===> Output Capture Class1 Disposition(P, R, N) Archive(T, P, B, N) Output Capture Class2 Disposition(P, R, N) Archive(T, P, B, N) Output Capture Class3 Disposition(P, R, N) Archive(T, P, B, N) Output Capture Class4 Disposition(P, R, N) Archive(T, P, B, N)
Sysout Capture Options => A => R => N => X => R => N => => => => => => Ret days/Vers => 3 Requeue Class => A Capture Limit => 8 Ret days/Vers => 3 Requeue Class => A Capture Limit => 8 Ret days/Vers => Requeue Class => Capture Limit => Ret days/Vers => Requeue Class => Capture Limit => SCROLL ===> PAGE yy/mm/dd hh:mm Max Lines => Req Hold (YNZM) => Y Max Lines => Req Hold (YNZM) => Y Max Lines => Req Hold (YNZM) => Max Lines => Req Hold (YNZM) =>
Disposition values (P=Purge, R=Requeue, N=None) Archive values (T=DSN, P=Print, B=Both, N=None) Press ENTER to update options or END to exit without making changes.
The panel contains the following fields: Output Capture Class Specifies a SYSOUT= class or the job MSGCLASS= for which sysouts are to be captured and retained for online viewing. The classes must be defined to JES as HELD classes. Ret days/Vers Specifies the number of days or number of versions of the sysout you want to keep online. The number of days or versions, whichever is greater, will be kept. For example, suppose you specify 2 for a sysout class. An event that runs 10 times a day in that class will be kept for two days. However, an event that runs once a year will be kept for two years (2 versions). Max Lines Specifies a maximum line count for any given sysout data set in this class. If the output limit is reached, the capture is truncated and the sysout is requeued to the requeue class. Specify 1-32767 lines. Specify 0 for an unlimited line count. If the Prompt On Max Lines entry on the CA-Jobtrac Global Options panel is Y, a message is issued to the operator requesting a decision on the capture of the excessive sysout. The operator can reply Y to the Unicenter CA-Jobtrac WTOR TRAC196A message to instruct Unicenter CA-Jobtrac to continue capture each time the maximum number of lines is exceeded.
Set Global Options
Disposition (P,R,N) Specifies a sysout disposition of P, R, or N for normal (non-abending) jobs. The following explains each disposition: P Purges captured sysouts from the JES queue R Requeues captured sysouts to the sysout requeue class in held status after successful capture N Retains captured sysouts in their held message class after capture Requeue Class Specifies the output class to which you want all requeue requests sent. It should be a print class that is not held. Unicenter CA-Jobtrac places a hold on each requeued event. Scheduled events that abend have all their output requeued to this class after it is successfully captured. You can also use this parameter to reroute output to another sysout archival product. If you are using another sysout archival product, see your product's documentation to see if the class you specify must be a held class. Req Hold (YNZM) Indicates whether to hold requeued sysout data. The following are valid values: Y Holds the sysout data regardless of whether the maximum lines or capture limit is exceeded. N Holds the sysout data if the maximum lines or capture limit is exceeded. Otherwise, the sysout data is not held. Z Does not hold the sysout data if the maximum lines or capture limit is exceeded. Otherwise, the sysout data is held. M Does not hold the sysout data regardless of whether the maximum lines or capture limit is exceeded.
Set Global Options
Archive (T,P,B,N) Indicates your archival choice using one of the following: T Specifies that a copy of any sysout not already archived be put on tape when a 0ARCHIVE or 0SYSARCH task is executed (see the Extended Scheduling Services Guide for information about scheduling dynamic maintenance). P Specifies 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. This option is designed for online microfiche output. 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. B Specifies 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. N Specifies no archival or backup of sysouts when a 0ARCHIVE or 0SYSARCH task is executed. You should always make a tape backup if Unicenter CA-Jobtrac is the only sysout archival tool in use. Unicenter CA-Jobtrac utilities provide for recovery of aged sysouts from the archive tapes. Capture Limit Specifies the number of sysout data sets that are to be captured for a given event. For example, specify 255 to capture all sysouts in the class. If you specify 3, only the first three sysouts found in the output capture class are captured. All remaining sysouts are requeued to the requeue class. Capturing the first three sysouts is useful with job-level message class output, where the first three MSGCLASS sysouts are usually (to the extent indicated by MSGLEVEL): The JES job log Converted JCL listing Step execution/allocation log
Additional sysouts are normally sent by the user to SYSOUT=*. So, to capture only the MSGCLASS listing and requeue all SYSOUT=* output, you could specify a capture limit of three.
Set Global Options
Options on the Library Definitions Panel

The Library Definitions panel lets you define libraries for use by Unicenter CA-Jobtrac. The following panel shows a sample Library Definitions panel.
CA-Jobtrac COMMAND ===> Sysout Capture | Archive Dsname |
Library Definitions SCROLL ===> PAGE yy/mm/dd hh:mm Prefix : your.TRACJCLS Unit : Disp : Retpd : Blksize: CART CATLG 3 327
Date/Override Library Auto-Commands Library
: your.DATELIB : your.TRACMDS
Press ENTER to update options or END to exit without making changes.
The panel contains the following fields: Prefix Indicates the 1-to-35-character high-level qualifier for Unicenter CA-Jobtrac to use when generating the dynamically allocated archive DSN created at each archival. This prefix is defined in member JOBTRAnn (see the chapter "Customization Job Streams"). You cannot change the prefix on the Library Definitions panel. For volume identification, 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, as shown in the following name: DSN=your.prefix.Thhmm.Dmmdd Unit Defines the archive unit name UNIT=unitname). The unit name is defined in member JOBTRAnn (see the chapter "Customization Job Streams"). You cannot change the unit name on the Library Definitions panel. Disp Indicates the normal data set disposition of the archive data set. The default disposition is defined in member JOBTRAnn (see the chapter "Customization Job Streams"). You cannot change the default disposition on the Library Definitions panel.
Set Global Options
Retpd Indicates the retention period in days to be used for the archive data set created by a 0ARCHIVE or 0SYSARCH task. This value is also used to calculate the number of days to maintain an online copy of the sysout archive &INDEX entry. The &INDEX entry, available through the Unicenter CA-Jobtrac/ISPF dialogs, lists all sysouts captured for the defined period, a brief run history, and the volume on which they reside. The retention period is defined in member JOBTRAnn (see the chapter "Customization Job Streams"). You cannot change the retention period on the Library Definitions panel. Blksize Indicates the archive data set block size, in a multiple of 150-byte records (LRECL=150). The block size is defined in member JOBTRAnn (see the chapter "Customization Job Streams"). You cannot change the block size on the Library Definitions panel. Date/Override Library Specifies 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. This library is allocated during execution of the STAGE2 job stream. This library is required for proper allocation of JMF (JCL Management Facility) at Unicenter CA-Jobtrac startup time. For more information about JMF, see the Extended Scheduling Services Guide. If this DSN is not specified when the JOBTRAC task is started, Unicenter CA-Jobtrac issues a TRAC669E DSN: message. Auto-Commands Library Indicates the name of the standard PDS (LRECL=80) that contains members called command sets. Each command set consists of a list of related commands. You can schedule execution of a command set or respond to some event with a command set. For more information about operator commands, see the Operator Guide. For more information about command set scheduling, see the Extended Scheduling Services Guide.
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. This is required for running the IVPADI job later on in the IVP. For complete information about using ADI, see the Extended Scheduling Services Guide. Procedure: Follow these steps to copy member PRODDATE from the cai.SAMPJCL to your DATELIB library member DATELIB: 1. Ensure that the CA-Jobtrac global options panels have been updated, particularly the Library Definitions panel, which defines the date file to Unicenter CA-Jobtrac. If global options or the JOBTRA00 member have been updated, proceed to Step 2. If not, update the global options, and then exit and reenter Unicenter CA-Jobtrac. 2. Issue the following command from the CA-Jobtrac primary panel to edit member PRODDATE in your DATELIB library: DATES 3. Issue the ISPF copy command, and copy the cai.SAMPJCL member PRODDATE. 4. Exit the edit panel using the END command or the END PF key. Multiple ADI Members: You can define additional automatic date insertion (ADI) members to supplement your production DATELIB. This is useful when you have multiple JCL libraries or when your users have limited access to JCL libraries. The additional members reside in your date insertion library and are specified on separate ddnames in your JOBTRAC startup procedure. You must also add these ddnames to your TSO logon procedure or CLIST. To add the members to the JOBTRAC startup procedure, use a ddname of DATELxxx, where xxx is the three-digit numeric location ID. Sample: The following figure shows sample JCL for additional ADI members:
//DATELIB DD DSN=YOUR.PROD.DATEFILE(PRODDATE),DISP=SHR //DATEL 4 DD DSN=YOUR.PROD.DATEFILE(DATEL 4),DISP=SHR <= FOR LOCATION <= FOR LOCATION 4
Copy the JMFSYM01 Member
Copy the JMFSYM01 Member

The JMF (JCL Management Facility) feature uses the JMFSYM01 member to allow the centralization and control of variable JCL information by eliminating daily updating of production JCL streams. This is required to be able to run the IVP later. For more information about using JMF, see the Extended Scheduling Services Guide. Procedure: Follow these steps to copy member JMFSYM01 from the cai.SAMPJCL to your DATELIB library member JMFSYM01. 1. Ensure that the CA-Jobtrac global options panels have been updated from the previous step. 2. Issue the following command from the CA-Jobtrac primary panel to edit member JMFSYM01 in your DATELIB library: JMF 3. Issue the ISPF copy command, and copy the cai.SAMPJCL member JMFSYM01. 4. Exit the edit panel using the END command or the END PF key.
Copy the RESOURCE Member
Copy the RESOURCE Member

The RESOURCE feature uses the resource conditions and assigns a one- or two-digit ID code to each definition by coding statements in the RESOURCE member in your Unicenter CA-Jobtrac PPOPTION library. (For more information, see the Extended Scheduling Services Guide.) Procedure: Follow these steps to copy member RESOURCE from the cai.SAMPJCL to your PPOPTION data set. 1. Issue the ISPF copy command, and copy the cai.SAMPJCL member RESOURCE. All statements in this member are samples and are comments. 2. Issue the following command from the CA-Jobtrac primary panel to edit member RESOURCE in your PPOPTION library: PARMS RESOURCE 3. Exit the edit panel using the END command or the END PF key. Note: TRAC310W is issued if no RESOURCE file is available. Unicenter CA-Jobtrac continues processing.
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 Unicenter CA-Jobtrac PPOPTION library. (For more information, see the Extended Scheduling Services Guide.) Procedure: Follow these steps to copy member EXCLPARM from the cai.SAMPJCL to your PPOPTION data set: 1. Issue the ISPF copy command, and copy the cai.SAMPJCL member EXCLPARM. 2. All statements in this member are samples and are comments. 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.
Maintain Table Modules

Some of the tables used by Unicenter CA-Jobtrac exist as load modules. Other tables exist as online tables. Load modules must be assembled and linked as described here. The online tables are maintained using the online table services described in the Extended Scheduling Services Guide. The online table services are used to schedule events based on data sets closing, create automatic message replies, schedule system commands, and specify additional condition code checking for events. Assembler Members: If you do not use SMP/E to maintain your table modules, use the assembly and link JCL provided in SAMPJCL. The following table names the SAMPJCL member to use for each table module. Use Member ASMAUTH ASMMSGT To Assemble TRACAUTH table Automatic Message Recognition table for use at IPL time Unicenter 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 Unicenter CA-Jobtrac does not have any entries in it. Some of the CA-JCLTrac functions require entries in the table. Before assembling the table, make the necessary entries in it. For more information about creating the necessary entries, see Set Up a UCT on page 220.
Converting Existing Modules to Online Tables: With the exception of the AMR table named IPLTABLE, all existing AMR, ADR, and SCS modules are converted to online tables. IPLTABLE remains a load module. For information about creating it, see Create IPLTABLE Entries (Optional) on page 209. The conversion can take place in two waysupon initialization or by request. When an existing module is initialized using the Unicenter CA-Jobtrac Table Services panels, it is automatically converted from the existing module format to the new table format. You can also convert modules prior to initialization by viewing the module on the online panels (see the Extended Scheduling Services Guide). While it is not necessary to convert modules prior to their initialization, it is a good idea to do so. This ensures that the existing modules are working correctly, since the load modules did not have error detection abilities. The online tables do have error detection abilities. Security for Online Tables: Security for the online tables is provided through the use of: The TRACAUTH table OPTA parameter (see Set Up Default Authorization on page 174) Your security package to secure program modules Unicenter CA-Jobtrac user exit TRACX26
Using Your Security Package: To use your security package, secure the use and function of the following modules: GJTRTSIF Accesses the entire online table service. GJTRTSTA Activates online tables. GJTRTSMC Updates or modifies the command (SCS) tables. GJTRTSMD Updates or modifies the automatic data set recognition (ADR) tables. GJTRTSMF Updates or modifies the condition code (CCPF) tables. GJTRTSMM Updates or modifies the message (AMR) tables. GJTRTSVC Views the active SCS table. GJTRTSVD Views the active ADR table. GJTRTSVF Views the active CCPF table. GJTRTSVM Views the active AMR table. GJTRTSVR Handles all submission tasks within Unicenter CA-Jobtrac. GJTRMSTR Handles all table setup and job submission setup. Includes calling subroutines.
Set Up AMR Support
Set Up AMR Support

To use the AMR (Automatic Message Recognition) feature, you must set up exit IEAVMXIT. This is done by ensuring IEAVMXIT is present in your SYS1.LINKLIB. If IEAVMXIT is not present, use member LINKMXIT in the Unicenter CA-Jobtrac SAMPJCL library to link it into SYS1.LINKLIB. All exits, including IEFBR14 dummies, should be linked as RENT and REUS. Exit IEAVMXIT is used and must be linked with AMODE 31. Disabling AMR Support: While Unicenter CA-Jobtrac is running, issuing any K M,UEXIT=Y/N or K M,AMRF=Y/N command disables AMR support. For information about reactivating AMR support, contact Technical Support. Also see AMR recovery procedures in the Reports, Maintenance, and Recovery Guide. For information about contacting Technical Support, see the information at the beginning of this guide.
Create 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 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 statement has the following format:
@AMRGEN 'msgtext[//]msgtextcont' [,option=value] . . . @AMRGEN END
@AMRGEN Invokes the @AMRGEN assembler macro to create an entry in the storage-resident AMR table. Required. 'msgtext[//]msgtextcont' 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 ('). // Represents any portion of the message (two forward slashes) in the message text. 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 triggers 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).
option=value Optional elements. Adds conditions to the definition. Specify one or more options per @AMRGEN statement. Specify only one value per option. For a description of each option, see the following: ACT=A|C|N|P|R|S|W|X Specifies the action to be triggered when the specified message is issued and any other conditions are satisfied. The following values are available: A Adds the trigger job to the current schedule with a manual dependency (dependency code M). If the trigger job is already on the current schedule, no action is taken. C Issues the command specified by CMD=. N Makes the message nondeletable and highlights it on the console display. P Purges the trigger job from the current schedule. The trigger job is removed from the current schedule, and any successors are released from predecessor dependency on the trigger job. If the trigger job is not on the current schedule, no action is taken. R Adds the trigger job to the current schedule with no dependencies. The trigger job is submitted immediately. If the trigger job is already on the current schedule, the manual dependency (dependency code M) is removed from the job. S Suppresses the message from appearing on the system console. W Issues the WTOR reply specified by CMD=. X Takes user exit TRACX04. Any reply is generated by the exit program. This exit is no longer supported and may not work in future versions. CHGMSG='chgtext' Specifies the text to be used in place of the original system message text. You can specify which part of the original message to replace (see CHGOFF). Specify the new message text. You must enclose the new text in single quote marks ('). No ACT= parameter is required for this action.
CHGOFF=nn 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. Offset 00 is the beginning of the message; offset 01 is the second character of the message; and so on. Specify a two-digit number specifying the offset value. If you do not specify this parameter, the default offset value 00 is assumed. CJOB=createjob 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. CMD='syscmd' Specifies the system command or WTOR reply to be issued by Unicenter CA-Jobtrac in response to the message specified by msgtext. Specify a command or WTOR reply. You must enclose the command or reply in single quote marks ('). If ACT=C is specified (see ACT=), the command or reply is issued as a standard command. If ACT=W is specified, the command or reply is issued as a WTOR reply and is automatically appended with the proper ID (for example, R nn,syscmd, where nn is the number of the message to which the reply is being made). You can specify an entry to schedule the command to be issued at the time specified by the System Command Scheduling facility. To do so, include this parameter as follows: CMD='SCHD#nnn,syscmd' The command specified by syscmd will be issued at the time defined by a System Command Scheduling statement with the SCHD#nnn parameter. For more information about using System Command Scheduling, with Automatic Message Recognition see the Extended Scheduling Services Guide. MSGOFF=nn 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.
PROCP=processp|mm/dd/yy 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 Reference Summary. You can specify a fixed date in the form mm/dd/yy, where mm is a two-digit number representing a month (01-12), 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). For example, to specify May 11, 2006, you would use PROCP=05/11/06. You can replace any part of the date with ** to define a generic date. For example, PROCP=08/**/06 specifies any day during August, 2006; PROCP=**/15/** specifies the 15th day of any month during any year. SYSID=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. TJOB=triggerjob Specifies the name of the job to be acted upon by the triggered event. TOD=hhmm{hhmm} 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 a.m. and 11 a.m. 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. @AMRGEN END Required keywords. Specifies the end of the list of @AMRGEN statements in the job.
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.
Procedure: To use the IPLTABLE and the VINITx procedure together, use the following procedure: 1. Locate sample member IPLTABLE in your SAMPJCL library. This is the sample IPLTABLE, which you can use as a model. 2. Locate sample member ASMIPLT in your SAMPJCL library. Use this job to assemble and link IPLTABLE into your Unicenter CA-Jobtrac CAILIB library. 3. Run the job. 4. After you have successfully linked the IPLTABLE into your CAILIB library, you may need to issue the following command: F LLA,REFRESH Your new IPLTABLE is now ready for use at IPL time.
Enable the SPACE Command
Enable the SPACE Command

Users must add GJTRUCBS to the AUTHTSF, AUTHCMD, and AUTHPGM table in the IKJTSOxx member of your SYS1.PARMLIB to enable the SPACE command. Use the TSO PARMLIB command to update the TSO system values.
Integration with Unicenter CA-11

This topic describes the Unicenter CA-Jobtrac and Unicenter CA-11 changes needed to implement a seamless interface between these two products. The features provided by this integration include the following: Automatic insertion of the Unicenter CA-11 U11RMS step during the Unicenter CA-Jobtrac job submission. Insertion of the step can be controlled by job class. Step insertion parameters are retrieved from the Unicenter CA-11 options table. Integration of the Unicenter CA-Jobtrac ISPF online with Unicenter CA-11 to update the Unicenter CA-11 database when Unicenter CA-Jobtrac Delete (D) and Purge (P) commands are issued. Integration of the Unicenter CA-Jobtrac ISPF online to the Unicenter CA-11 ISPF online to display the Unicenter CA-11 ISPF panels when a Unicenter CA-Jobtrac Rerun (R) command is issued. The job name of the job selected in Unicenter CA-Jobtrac is passed to the Unicenter CA-11 online. Unicenter CA-Jobtrac recognizes when the selected job is set up through the Unicenter CA-11 online for restart, and releases the job when you return to the Unicenter CA-Jobtrac panels. Restart cancel or force complete actions for the selected job are also detected by Unicenter CA-Jobtrac.
Installation Requirements: Note: A supported release of Unicenter CA-11 is required.
The Unicenter CA-Jobtrac PPOPTION initialization member (JOBTRAxx) must be updated to include the RERUN= and INSERTRMS= keywords described in RERUN on page 150 and INSERTRMS on page 145. To use the Unicenter CA-11 ISPF restart panel from the Unicenter CA-Jobtrac ISPF panels, you must allocate the Unicenter CA-11 libraries to your ISPF session. You can do this in one of two ways: Add the Unicenter 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. 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.
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 Unicenter 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 Unicenter CA-11 step insertion, verify that the Unicenter 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 Unicenter CA-Jobtrac. For more information about the Unicenter CA-11 Options Table, see the the Unicenter CA-11 Systems Programmer Guide. The INCLUDE statement is used in execution JCL to specify the name of a PDS member containing JCL statements that you want included (inserted) at the position of the INCLUDE statement. The PDS member can 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 and 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 Unicenter CA-Jobtrac that are used to schedule job submission. Presubmission syntax checking, JCL validation, Unicenter 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 Unicenter 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 Unicenter CA-11 RMS control step is not physically the first step of the job.
Be aware that Unicenter CA-11 does not process JCL statements that are placed before the Unicenter CA-11 RMS control step. Fortunately, Unicenter CA-Jobtrac implements the automatic Unicenter CA-11 RMS step insertion feature as an option. With this option turned on, Unicenter CA-Jobtrac searches the JCL for the first EXEC or PROC statement and inserts the RMS step prior to that statement. Unicenter CA-Jobtrac also checks to see if a Unicenter 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 Unicenter 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. Starting with r3.5, Unicenter CA-Jobtrac inserts the Unicenter CA-11 RMS control step prior to any INCLUDE statement positioned before the first EXEC statement. This was done to ensure that the Unicenter CA-11 RMS step was the first EXEC statement in the job. However, subsequent customer feedback with this approach and the intent of CA to maintain consistency across mainframe scheduling products allow Unicenter CA-Jobtrac to perform Unicenter CA-11 RMS step insertion as it did previously in r3.4.
Set Up CA-JCLTrac
Set Up CA-JCLTrac
CA-JCLTrac is the JCL analysis component of Unicenter 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 Unicenter 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 more information about setting up a UCT, see Set Up a UCT on page 220. Setting Up DB2 Tables: You can use the CA-JCLTrac feature of Unicenter 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 following list outlines the steps that you must take to set up the DB2 database. The following pages explain the steps in detail. 1. Create the DB2 objects (see Create the DB2 Objects on page 226) 2. Bind the DB2 plans (see Bind the DB2 Plans on page 228) 3. Grant access and select authority (see Grant Authority on page 229)
Set Up CA-JCLTrac
Enabling CA-JCLTrac: To enable CA-JCLTrac, add GJC3MCII to the AUTHTSF, AUTHCMD, and AUTHPGM table in the IKJTSOxx member of your SYS1.PARMLIB. Use the TSO PARMLIB command to update the TSO system values. Enabling Automatic JCL Checking: Automatic JCL checking requires the use of the JCLAUTO macro. This macro is installed with Unicenter CA-Jobtrac as a CLIST in the Unicenter CA-Jobtrac CAICLIB library. What is JCLAUTO?: JCLAUTO is an edit macro that redefines the END and SAVE ISPF/PDF edit commands. JCLAUTO changes the commands to invoke the CA-JCLTrac JCL Analyzer prior to saving the member you are editing. If a JCL error is found, the JCL is not saved, and a CA-JCLTrac message is issued. For more information about CA-JCLTrac, see the Extended Scheduling Services Guide. Invoking JCLAUTO: JCLAUTO is invoked in one of the following ways: Through the use of the Unicenter 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). Executing it while in an edit session
Disabling Syntax Checking: Once JCLAUTO is invoked, it remains in effect for the duration of the edit session. If you want to disable syntax checking, execute the following command: JCLAUTO OFF
Set Up CA-JCLTrac
Set Up a UCT
A UCT (User Control Table) provides control information. It accomplishes the following: Associates a Unicenter 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 do the following: 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. The following are the @JCLUCT statements: CLASS DSNAME DDNAME END
Syntax Used: The following sections show the syntax of the @JCLUCT statements. The following rules apply to the syntax: Italics are used to denote a variable. Replace the variable with the indicated information. Lowercase letters denote optional portions of literals. You do not have to include them. For example, for DSName, you only have to use DSN in the statement. [Brackets] indicate an option. You do not have to include in the statement what is shown in brackets. Punctuation that is shown must be used.
Set Up CA-JCLTrac
How to Set Up and Use a UCT: By default, a UCT is always used. The default name is GJC3TUCT. If you want to use a UCT with a different name, use the UCT keyword. Take the following steps to create and use a UCT: 1. Decide if you need to create a UCT. (Usually, you will need to use one.) If you need to create a UCT, continue with the following steps. See Set Up a UCT on page 220. 2. Create entries in a UCT using the @JCLUCT statements. See CLASS Statement on page 222 through @JCLUCT Macro Examples on page 225. 3. Compile the UCT using the member ASMUCT in your SAMPJCL library. 4. 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, see CA-JCLTrac in the Extended Scheduling Services Guide.
Set Up CA-JCLTrac
CLASS Statement: CLASS statements match a job class with its JES PROCLIB concatenation. Specify up to 35 class statements. CLASS statements have the following syntax:
[name] @JCLUCT CLASS,jobclass,ddname
name Assigns a CSECT name to the UCT. It must appear on the first @JCLUCT macro only. The default is GJC3TUCT. @JCLUCT Identifies this line as a @JCLUCT statement. CLASS Required literal. Defines this statement as a CLASS definition. jobclass Specifies the job class. Use 0-9 or A-Z. Define a job class once only. ddname Specifies the ddname of the JES PROCLIB concatenation used by the job class. For omitted job classes, the default ddname is PROC00 for JES2 IATPLBST for JES3
Set Up CA-JCLTrac
DSNAME Statement: DSNAME statements associate Unicenter CA-Jobtrac location IDs with JCL libraries. Specify as many DSNAME statements as necessary. DSNAME statements have the following syntax:
name @JCLUCT DSName,locid,dsname[,SEQ=nnn]
name Assigns a CSECT name to a UCT. It must appear on the first @JCLUCT macro only. The default is GJC3TUCT. @JCLUCT Identifies this line as a @JCLUCT statement. DSName Required literal. Defines this statement as a DSNAME definition. locid Specifies the location ID. Use any number from 0 to 254. A location ID can be defined only once. dsname Specifies the name of the JCL library associated with the specified location ID. Specify a valid data set name. SEQ=nnn Defines multiple libraries to a location. Replace nnn with any number from 0 to 254, the default is 1. The sequence number determines the order in which the libraries appear in the input concatenation.
Set Up CA-JCLTrac
DDNAME Entries: If your JES started task contains nonstandard PROCLIB ddnames, DDNAME statements are required. Use as many DDNAME statements as necessary. For JES2, CA-JCLTrac dynamically allocates all ddnames that start with PROC. DD statements are required only if your JES2 started task contains ddnames other than PROCxx. For JES3, CA-JCLTrac dynamically allocates all ddnames that start with IATPLB. DDNAME statements are required if your JES3 started task contains ddnames other than IATPLBxx. DDNAME statements have the following syntax:
name @JCLUCT DDName,ddname
name Assigns a CSECT name to a UCT. It must appear on the first @JCLUCT macro only. The default is GJC3TUCT. @JCLUCT Identifies this line as a @JCLUCT statement. DDName Required literal. Defines this statement as a DDNAME definition. ddname Specifies the nonstandard procedure library ddname to be allocated. Specify a valid ddname.
Set Up CA-JCLTrac
END Statement: The END statement terminates the @JCLUCT macro, marking the end of a UCT. Use only one END statement. It must be the last statement in the table. The END statement has the following syntax:
name @JCLUCT END
name Assigns a CSECT name to a UCT. It must appear on the first @JCLUCT macro only. The default is GJC3TUCT. @JCLUCT Identifies this line as a @JCLUCT statement. END Required literal. Defines this statement as a termination statement. @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
Set Up CA-JCLTrac
Create the DB2 Objects

This step creates the DB2 objects used to store the CA-JCLTrac data. The DDL that creates the DB2 objects is in the JCLQDDL member of your SAMPJCL library. This code requires editing before running. Required Editing: In the JCLQDDL member, there are symbolics for values you must provide. These symbolics begin with a question mark (?TSSGNME) so that they are easy to find. 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. If this storage group already exists, remove the CREATE STOGROUP DDL statement from the JCLQDDL member. The DASD volume to be used by the CA-JCLTrac tablespace storage group. If this storage group is not being created, this parameter is not relevant. The volume catalog to be used by the CA-JCLTrac tablespace storage group. If this storage group is not being created, this parameter is not relevant. The DB2 buffer pool to be used by the CA-JCLTrac tablespace. The PRIQTY value used by the CA-JCLTrac tablespace. The SECQTY value used by the CA-JCLTrac tablespace. The name of the storage group to be used for CA-JCLTrac indexes. If this storage group already exists, remove the CREATE STOGROUP DDL statement from the JCLQDDL members. The DASD volume to be used by the CA-JCLTrac index storage group. 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 this storage group is not being created, this parameter is not relevant. The DB2 buffer pool to be used by the CA-JCLTrac indexes. The PRIQTY value used by the CA-JCLTrac indexes. The SECQTY value used by the CA-JCLTrac indexes.
?TSVOLID
?TSVCAT
?TSBPOOL ?TSQPRI ?TSQSEC ?IXSGNME
?IXVOLID
?IXVCAT
?IXBPOOL ?IXQPRI ?IXQSEC
Set Up CA-JCLTrac
Symbolic ?DBNAME
Explanation The name of the CA-JCLTrac database. If the specified database already exists, remove the CREATE DATABASE DDL statement from the JCLQDDL member. The authorization ID that will become the high-level name of the CA-JCLTrac tables and indexes.
?CREATOR
Optional Editing: After you have changed the symbolics, further editing may be required. If the CA-JCLTrac tables are going to use an existing database, remove the CREATE DATABASE DDL statements 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, run it in SPUFI, DSNTEP2, or an equivalent program. If you are going to create the database and storage groups, you will need the following authority on the target DB2 subsystem: CREATEDBAcreate database CREATESGcreate storage group
If you are using an existing database and storage groups, you need the following authority on the target DB2 subsystem: CREATETScreate new tablespace CREATETABcreate new table
The DB2 subsystem in which the tables are created is the CA-JCLTrac home subsystem.
Set Up CA-JCLTrac
Bind the DB2 Plans

This step binds the DB2 plans. CA-JCLTrac uses the following plans: GJC3TDB2The Update plan. CA-JCLTrac uses this plan to insert and delete data in the DB2 tables. GJC3X*The Report plans. There are 18 plans. Each plan's name starts with GJC3X. CA-JCLTrac uses these plans to extract data for the cross-reference reports. GJC3TSPFThe Dialog Manager plan. CA-JCLTrac uses this plan for the online DB2 reports.
The JCL used to bind the plans is in the JCLBIND member in your SAMPJCL library. Required Changes: In the JCLBIND member, there are symbolics for values you must provide. These symbolics begin with a question mark so they are easy to find. For example, ?JOBCARD. 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. The name of the DB2 system that runs CA-JCLTrac. The authorization ID that is the high-level name of the CA-JCLTrac tables and indexes. This should match the ID used in the JCLQDDL job. For the bind to work, the ID must have BINDADD authority.
Procedure to Bind the Plans: Using the ISPF editor, change each symbolic. After you edit and save the JCLBIND member, submit the job to bind the plans.
Set Up CA-JCLTrac
Grant Authority
Various authorities must be granted to use the CA-JCLTrac plans and tables. This section explains what those authorities are and how to grant them. Granting Authority to Create Reports: To use the CA-JCLTrac report plans to create reports, you must grant execute and select authority to the appropriate users. Select authority is necessary because the report plans use dynamic SQL. The SQL statements used to grant execute and select authority are in the JCLQRPT member in your SAMPJCL library. In the SQL are the symbolics ?AUTHID and ?CREATOR. ?AUTHID is the ID of the person receiving the authority. If you intend to grant general access to the CA-JCLTrac tables, use an ID of PUBLIC. ?CREATOR is the authorization ID that is the high-level name of the CA-JCLTrac tables. Using the ISPF editor, replace the symbolics with valid authorization IDs. After you edit and save the JCLQRPT member, run it in SPUFI, DSNTEP2, or an equivalent program. Granting Authority to Update and Load Tables: To update and load the CA-JCLTrac tables, you must grant execute and load authority to the appropriate users. The SQL statements used to grant execute and load authority are in the JCLQUPD member in your SAMPJCL library. In the SQL are the symbolics ?DBNAME and ?AUTHID. ?AUTHID is the ID of the person receiving the authority. ?DBNAME is the name of the database for which authority is being granted. Using the ISPF editor, replace the symbolics with a valid database name and authorization ID. After you edit and save the JCLQUPD member, run it in SPUFI, DSNTEP2, or an equivalent program.
Use Other Sysout Capture Products

The Unicenter CA-Jobtrac primary function is to automate production scheduling. The purpose of the Sysout Capture feature is for short time storage of sysouts only. Long term storage should utilize an output management product such as CA-View. If you already have a sysout capture product of another kind, you can direct Unicenter CA-Jobtrac to requeue each listing to the other product as it captures the copy for on-schedule viewing. For more information about requeueing sysouts, see the Requeue Class description in Options on the Sysout Capture Options Panel on page 195. About the Unicenter CA-View Interface: Unicenter CA-Jobtrac can interface with the CA Unicenter CA-View product, r11 and higher. To use the Unicenter CA-View interface, you must be able to run Unicenter CA-View from ISPF. This means that the Unicenter 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. The Unicenter CA-View panels must be accessible. For more information, see the Unicenter CA-View Getting Started. Accessing Unicenter CA-View in Unicenter CA-Jobtrac: The first time you use the 0 (zero) line command or the Unicenter CA-View primary command, Unicenter CA-Jobtrac prompts you for the high-level name of a Unicenter CA-View database. When you respond, Unicenter CA-Jobtrac saves the name in your Unicenter CA-Jobtrac user profile. The next time you issue a 0 line command or Unicenter CA-View primary command, Unicenter CA-Jobtrac uses the high-level name that it saved to determine which database to access. For more information about these commands, see the Operator Guide.
Enabling the Unicenter CA-View Interface: To enable the Unicenter CA-View feature, take the following steps: 1. Format a capture file. We recommend 5 cylinders (the minimum). 2. Specify N for the Capture Sysout field on the CA-Jobtrac Global Options panel. This tells Unicenter CA-Jobtrac to bypass sysout capture and to route it to the Unicenter CA-View output class. 3. Specify a class that does not get held (A, for example) for the Output Capture Class 1 field on the Sysout Capture Options panel. This tells Unicenter CA-Jobtrac not to hold any sysout. 4. Specify a number of days to keep schedule captures in the Ret Days/Vers field on the Sysout Capture Options panel. This tells Unicenter CA-Jobtrac to save schedule captures for the specified number of days. 5. Specify whatever you want for the remaining fields in the first capture class definition (class 1). Unicenter CA-Jobtrac uses this primary definition for schedule captures, and it must be defined. For more information about the CA-Jobtrac Global Options and Sysout Capture Options panels, see Set Global Options on page 184.
Cross-Platform Scheduling
If you plan to implement the remote scheduling to a scheduler or an agent, the following are required: CA-GSS CA-XPS CA Common Services CAICCI must be configured with a TCPIPGW protocol TCP/IP gateway. For syntax and additional information, see the CA Common Services Administrator Guide. A sample CAICCI configuration file might look like: SYSID(localname) PROTOCOL(TCPIPGW) NODE(TCPIPGW,ip-address:port,retry,remotename) - optional CONNECT(remotename) - optional TCP/IP must exist on one of the z/OS systems to communicate with the remote platform (such as UNIX). CAICCI can route work throughout your SNA network to reach other z/OS systems. If you plan to implement remote scheduling to Unicenter CA-Jobtrac from a scheduler or an agent, the following is also required: CAIENF must be installed. CAIENF must be active for status to be returned to a scheduler or an agent. CA-XPS DCM(CAL2DCM2) must be installed into the CAIENF database. CA-XPS must be installed. For more information, see the CA Common Services Administrator Guide.
Procedure: The following steps are required to implement cross-platform scheduling: 1. CAICCI must be configured with a TCPIPGW protocol TCP/IP gateway. For syntax and information, see the CA Common Services Administrator Guide. 2. Allocate the tracking checkpoint by running the job in the ALCUNICK member of SAMPJCL (required). This DD MUST be added to the CA-GSS PROC on the CHKPOINT ddname in a following step. 3. Add the statements from the PPOPTION member JOBTRAC to the CA-GSS PPOPTION member JOBTRAC. See Global Variables for Cross-Platform Scheduling on page 236. 4. Edit the CA-GSS PROC (YS28GSSA) and add the following DD statement:
//CHKPOINT DD DISP=SHR,DSN=your.unijtckp <-specify
5. (Optional) Allocate remote platform security location data set. A location data set (TRACRnnn) can optionally be defined to Unicenter CA-Jobtrac to contain user ID, domain, and password information that is used when submitting events to a scheduler or an agent on remote systems. A remote password data set may be defined for each location. The members contained in this data set are encrypted to prevent browsing. The members are created and updated through the PASSWORD command that is available from the Unicenter CA-Jobtrac ISPF facility. The data sets can be allocated using the following JCL or what is in SAMPJCL member STAGE2.
//name JOB //STEP1 EXEC PGM=IEFBR14 //TRACRnnn DD DSN=your.TRACR,DISP=(,CATLG), // DCB=(RECFM=FB,LRECL=8 ,BLKSIZE=6 8 ),SPACE=(TRK,(15,15,1 // UNIT=uuuuu,VOL=SER=vvvvv
)),
Once allocated, you must add the data set to the DYNAMLOC PPOPTION member. Use the REFRESHLOC operator command to add the data set without restarting Unicenter CA-Jobtrac. REFRESHLOC is described in the Operator Guide. DYNAMLOC allocation is described in Define Location Information (DYNAMLOC) and Initiation IMODs on page 176. Note: The same password data set may be used by multiple locations, but multiple password data sets cannot be concatenated to a single TRACRnnn ddname. For information about updating this data set, see the PASSWORD ISPF online command in the Operator Guide. For information about optional member name processing, see REMTCRED on page 149. 6. Password requirements rules file (optional). For cross-platform work being routed to Unicenter CA-Jobtrac from other platforms, 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. This table can reside in any 80-character LRECL data set and may be a member of a PDS. The data set is referenced, as shown in the following, by ddname XPSPSWD in the CA-GSS PROC. This table is described in Cross-Platform Server ($UNIXPSJT) Password Requirements Table on page 241.
//XPSPSWD DD DISP=SHR,DSN=CAI.XPSPSWD
You are asked in the following step to specify a data set for the XPSPSWD DD. If you decide not to use this table, the file can be specified as:
//XPSPSWD DD DUMMY
This disables password requirement checking. 7. Shut down and restart CA-GSS to pick up the new CHKPOINT DD. 8. Shut down and restart Unicenter CA-Jobtrac to pick up the new DDs.
CA-GSS Server IMODs

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

This topic describes the CA-GSS globals that are used with the cross-platform scheduling server IMODs.
Server IMOD Selection Globals

GLOBVAL &UNI.$UNI2JT /Y/ Controls the starting of the server IMODs that are used for scheduler to Unicenter CA-Jobtrac processing. If Y is specified as the value, the IMOD services $UNIXPSJT and $UNIRCVJT are started whenever Unicenter CA-Jobtrac is started or the $UNIJT_INIT IMOD is executed. Any value other than Y prevents the server IMOD from starting. GLOBVAL &UNI.$JT2UNI /Y/ Controls the starting of the server IMODs that are used for Unicenter CA-Jobtrac to a scheduler or an agent processing. If Y is specified as the value, the IMOD service $UNITRKJT is started whenever Unicenter CA-Jobtrac is started, or the $UNIJT_INIT IMOD is executed. Any value other than Y prevents the server IMOD from starting.
Status Tracking Server Globals (Service $UNITRKJT)

GLOBVAL &UNI.$UNITRKJT.MON /JOBTRAC/ Specifies the monitor name to be used to identify Unicenter CA-Jobtrac when requests are received from a scheduler. If multiple CA scheduling products are installed and Unicenter CA-Jobtrac is not the primary receiver of requests, this differs from &UNI.$UNIXPSJT.MON described in the following. 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 a scheduler. In most cases, the value of JOBTRAC is appropriate. This global is required.
GLOBVAL &UNI.$UNITRKJT.IMOD /$JOBT_REMTTRACK/ Specifies the IMOD to invoke when status information is received from a scheduler. This value must be specified with the value of $JOBT_REMTTRACK and should not be changed. This global is required. GLOBVAL &UNI.$UNITRKJT.SCAN /15/ Specifies the number of seconds between controlled services. These services include testing for operator shutdown requests, physical updates to the checkpoint file that is being updated at all times in memory, and querying remote locations for job completion statistics. This value may range from 01 to 60. If this value is not supplied, a default of 15 seconds is used. GLOBVAL &UNI.$UNITRKJT.EXTTABLE/data set.name/ Specifies the name of a sequential data set or the member name of a PDS in which the external events are defined. This global is optional. GLOBVAL &UNI.$UNITRKJT.DEBUG /DEBUG/ Enables debug for this task. If this global is set to the value DEBUG, this task logs information about processing to DDs DEBUGTRK and SNAPTRK. If these DDs are not present in the GSS PROC, setting this global has no effect. We recommend that debug only be turned on at the request of Technical Support since the volume of debug information can be large.
Command Driver Globals (Service $UNIRCVJT)

GLOBVAL &UNI.$UNIRCVJT.MON /JOBTRAC/ Specifies the monitor name to be used to identify Unicenter CA-Jobtrac when requests are received from a scheduler. If multiple CA scheduling products are installed and Unicenter CA-Jobtrac is not the primary receiver of requests, this differs from &UNI.$UNIXPSJT.MON described in the following. 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 a scheduler. In most cases, the value of JOBTRAC is appropriate. This global is required. GLOBVAL &UNI.$UNIRCVJT.IMOD /$JOBT_REMTCMD/ Specifies the IMOD that is invoked when a request from a scheduler is received. This value must be specified as is. This global is required. GLOBVAL &UNI.$UNIRCVJT.SCAN /15/ Specifies the number of seconds between controlled services. These services include testing for operator shutdown requests. This value may range from 01 to 60. If this value is not supplied, a default of 15 seconds is used. GLOBVAL &UNI.$UNIRCVJT.DEBUG /DEBUG/ Enables debug for this task. If this global is set to the value DEBUG, this task logs information about processing to DDs DEBUGRCV and SNAPRCV. If these DDs are not present in the GSS PROC, setting this global has no effect. We recommend that debug only be turned on at the request of Technical Support since the volume of debug information can be large.
Cross-Platform Server Globals (Service $UNIXPSJT)

GLOBVAL &UNI.$UNIXPSJT.MON /JOBTRAC/ Specifies the monitor name to be used to identify Unicenter CA-Jobtrac when requests are received from a scheduler. If multiple CA scheduling products are installed and Unicenter CA-Jobtrac is not the primary receiver of requests, this differs from &UNI.$UNIXPSJT.MON described in the following. 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 a scheduler. In most cases, the value of JOBTRAC is appropriate. This global is required. GLOBVAL &UNI.$UNIXPSJT.SCAN /15/ Specifies the number of seconds between controlled services. These services include testing for operator shutdown requests, physical updates to the checkpoint file that is being updated at all times in memory, and querying remote locations. This value may range from 01 to 60. If this value is not supplied, a default of 15 seconds is used. GLOBVAL &UNI.$UNIXPSJT.DEBUG /pc/ Sets current Print (p) and Console (c) trace code settings for this task. The Print trace code controls both print and snap output. The Console trace code controls what WTOs are issued to the z/OS console. The print and snap DDs are defined in the GSS PROC as XPSPRINT and XPSSNAP.
Valid trace code values are: 0 Do not issue any trace WTOs. This value is only honored for the Console trace code. If entered for the Print trace code, it is interpreted the same as a code of 1. Normal messages/WTOs. These messages indicate XPS system startup and shutdown. They also indicate when communication with remote systems is first established and if such communication is lost. Communication messages/WTOs. Besides the messages issued for trace code 1, messages relating to CCI communications with other systems are issued. Also, if the snap DD is available, snap dumps are taken of the storage areas related to CCI control blocks and records. Feedback messages/WTOs. Besides the messages issued for trace code 2, messages relating to XPS CAIENF feedback events are issued. Also, if the XPS snap DD is available, snap dumps are taken of the storage areas related to CAIENF control blocks and feedback records in addition to the communication area snaps. Program path messages/WTOs. Besides the messages issued for trace code 3, messages relating to internal XPS processing are issued. Also, if the XPS snap DD is available, snap dumps are taken of the storage areas related to XPS control blocks in addition to the communication and feedback related snaps. Note: Trace code 4 should only be used at the direction of Technical Support since it produces a significant number of messages. 5-9 Currently, trace codes 5 through 9 do not have specific definitions. If entered, they are interpreted the same as trace code 4.
GLOBVAL &UNI.$UNIXPSJT.AGE /30/ Specifies the maximum age for Checkpoint entries. Entries older than the number of days specified will be deleted. This value may range from 01 to 999. If this value is not supplied, a default of 30 days is used.
Cross-Platform Server ($UNIXPSJT) Password Requirements Table

The password requirement rules for the cross-platform server on z/OS define when a password must accompany an explicit user ID in a cross-platform request. Using this table you can discriminate between trusted and non-trusted systems when receiving requests. That is, 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, you can specify a rule so that the cross-platform server will accept the user ID without a password. For other systems that 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. Requests received from these systems that have a user ID but no password are automatically rejected. Password Requirement Rules are defined in a data set pointed to by the XPSPSWD DD statement in the GSS PROC. This data set is a sequential file consisting of fixed 80-byte records (physical sequential or a member of a PDS). The records can be blocked or unblocked. If the XPSPSWD DD statement is not present, or contains no valid rules, the default processing is to accept all requests without checking for the presence of passwords. When the cross-platform server goes through initialization processing, it attempts to locate and parse the Password Requirement Rules. If found, these rules are stored in an in-storage table that is accessed during normal processing. Changes made to the rules do not take effect until the server is reinitialized. For information about stopping and starting CA-GSS server IMODs, see CA-GSS Server IMODs on page 235.
Syntax Rules
Lines beginning with a blank or an asterisk (*) are considered comment lines. Each individual rule must be contained on a single line between columns 1 through 71. Continuation lines are not supported. The rule definition consists of a series of keywords/values beginning in column 1, separated by commas with no embedded blanks.
Keywords
NODE=caicci-node-name Identifies the one- to eight-character CAICCI Node name that a Cross-Platform request can be received from. It must be specified as a specific name or an asterisk (*), which indicates all nodes. If not specified, the default is NODE=*, indicating all nodes. MONITOR=monitor-name Identifies the seven-character scheduling system monitor name that a Cross-Platform request can be received from. It must be specified as a specific name or an asterisk (*), which indicates all monitor names. In cases where a given node may have multiple scheduling systems (such as production and test copies of Unicenter CA-Jobtrac), the NODE and MONITOR combination will uniquely identify a specific scheduling system. If not specified, the default is MONITOR=*, indicating all monitor names. ID=user-id Identifies the one- to eight-character user ID that may be passed with a Cross-Platform request. It must be specified as a specific name or an asterisk (*), which indicates all user IDs. If not specified, the default is ID=*, indicating all user IDs. PSWD=YES|NO Indicates whether a Cross-Platform request that matches the NODE/MONITOR/ID parameters of the rule must have a password to accompany the user ID in the request. YES (or Y) Indicates that such requests must have a password. If not specified, the default is PSWD=YES. NO (or N) Indicates that passwords are optional for such requests.
Processing
When the server receives a cross-platform request, it checks to determine if the request contains an explicit user ID. If the request does not contain a user ID, a password requirement check is not made. If the request contains both a user ID and a password, a password requirement check is not made. If the request contains a user ID but no password, a password requirement check is made.
The XPS Router attempts to find the 'best match' between the current request and the Password Requirement Rule Table based upon the NODE, MONITOR, and user ID. A match with a rule that specifies a specific NODE, MONITOR, and/or user ID takes precedence over a generic rule. If multiple rules equally match a request, the rules that require a password take precedence over those that do not. If no match is found in the table, the request is allowed to proceed without a password.
Examples
NODE=A 4IENF,MONITOR=JOBTRAC,ID= ,PSWD=YES The preceding rule indicates that any request from CAICCI node A04IENF, scheduling system JOBTRAC, must have a password if it contains an explicit user ID. NODE= ,ID=MASTER,PSWD=YES The preceding rule indicates that any request that contains a user ID of MASTER must have a password, regardless of what CAICCI node or scheduling system sent the request. The default for MONITOR= is * if it is not specified. NODE=A 4IENF,ID=TESTUSER,PSWD=NO The preceding 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. NODE=A 4IENF,ID= ,PSWD=YES NODE= ,ID=TESTUSER,PSWD=NO If a request is received from CAICCI node A04IENF with a user ID of TESTUSER, it partially matches on both of the preceding rules. The second rule takes precedence since a specific ID match takes precedence over a specific NODE match. A password is not required. NODE=A 4IENF,MONITOR= ,ID= ,PSWD=YES NODE= ,MONITOR=JOBTRAC,ID= ,PSWD=NO If a request is received from CAICCI node A04IENF, scheduling system JOBTRAC with any user ID it partially matches on both of the preceding rules. In this case the matches have equal weight (NODE or MONITOR specific, user ID generic). In the case of a tie, the rule that requires a password takes precedence over one which does not. A password is required.
Alter the Event Console Logging Message Options

The Event Console Logging feature routes selected Unicenter CA-Jobtrac messages to one or more Unicenter Enterprise Job Management Event Consoles or Unicenter Event Consoles. The messages that are generated are defined in a load module, GJTREMSG. Defaults are set for the messages, and no modifications are required. If you want, you can customize this module to do the following: Change the default colors and attributes for each message severity. Change the color and attribute for a specific message. Change the fixed portion of the message text. Specify whether specific messages should be WTO'ed. Specify whether specific messages should be sent to the event console.
Before changing the GJTREMSG module, copy the source from CAIMAC(GJTREMSG) to a separate non-SMP/E controlled library. Once changed, the module can be added to Unicenter CA-Jobtrac by using the following job to apply the module as USERMOD UM00002. Usermods should never be accepted. This lets them be restored and re-applied if maintenance or a Unicenter CA-Jobtrac PTF ever needs to update this module.
//UM 2 JOB ... // // // APPLY CA-JOBTRAC UM 2 USERMOD FOR ECL MESSAGES // // THE FOLLOWING JCL USES YOUR EXISTING CA-JOBTRAC // SMP/E PROC. // // 1. SPECIFY A JOBCARD // 2. SPECIFY YOUR SOURCE DATASET AND MEMBER ON THE // '//EMSG DD' STATEMENT AT THE BOTTOM. // 3, RUN AND CHECK THE OUTPUT FOR ERRORS. // // //HD11APP EXEC CAIHD11 / INVOKE CA-JOBTRAC SMP PROCEDURE // //SMPPTFIN DD ++USERMOD (UM 2). ++VER (Z 38) FMID(CHDB ) PRE(xxxxxxxx). ++SRC(GJTREMSG) DISTLIB(CHDB XLD) SYSLIB(CAIMAC) DISTMOD(CHDB LLD) TXLIB(EMSG). / // //SMPCNTL DD SET BDY(GLOBAL). RECEIVE SELECT(UM 2). SET BDY(CAITGT). APPLY SELECT(UM 2). / //EMSG DD DISP=SHR,DSN=USER.PDS(GJTREMSG) <-YOUR SOURCE
Update the GJTREMSG Source

Once you have made a copy of the GJTREMSG source, you can make changes by modifying the parameters of the @ECLMSG macro as indicated in the source. The @ECLMSG macro is used to define the message table. There are six forms of the macro based on the value of MF=. Four of the macro formats are structural and should not be changed or moved in the GJTREMSG module. These are: MF=H MF=I MF=D MF=Q The table header. Generates the message pointer table for accessing the messages. Generates Dsect used by table. Generate Equates used by table.
Two MF= forms can be modified. MF=S Specifies the default attributes for each severity type.
The macro format is as follows: @ECLMSG SEV=, COLOR=, ATTR=, MF=S Severity code (I, W, or E) Color name (see color list below) Attribute (see attribute list below) Macro format: S
COLOR=, Indicates one of the following color names: BLACK, RED, ORANGE, YELLOW, GREEN, BLUE, PINK, or PURPLE. ATTR=, Indicates one of the following attributes: NORMAL, BLINK, or REVERSE. The following example shows setting the default values: - SET DEFAULT COLORS @ECLMSG SEV=I,COLOR=BLACK,ATTR=NORMAL,MF=S @ECLMSG SEV=W,COLOR=ORANGE,ATTR=NORMAL,MF=S @ECLMSG SEV=E,COLOR=RED,ATTR=REVERSE,MF=S
MF=G
Specifies the details for each message. New messages cannot be added, and not all parameters can be changed.
The macro format is as follows: @ECLMSG PREFIX=, NUM=, SEV=, SPEC=, MF=G, WTO=, Message Prefix Do Not Change Message Number Do Not Change Message Severity Do Not Change Special Processing Do Not Change Macro Format: G Do Not Change WTO Option: YES - WTO message NO - Do Not WTO OPT - Use ECLWTO JOBTRA option. Event Console: YES - send to Console log NO - don't send to Console Message Color: SEV - use default for Severity Color name - BLACK RED ORANGE YELLOW GREEN BLUE PINK PURPLE Message Attribute: SEV - use default for Severity Attribute - NORMAL BLINK REVERSE Email Event Type Flag. Do Not Change Service Desk Event ID. Do Not Change Service Desk Reporting Option: YES Create Service Desk Report for this event NO Do not create Service Desk Report for this event OPT Use the REPORT option from the startup parameters (JOBTRAnn) Fixed portion of message text. Notice that the message in most cases has additional fields added to provide specific information, such as Eventname. The format of this additional information is not defined in this table and cannot be modified.
EC=, COLOR=,
ATTR=,
EMAIL=, EVENT=, REPORT=,
TEXT=' '
The following example shows the default values: @ECLMSG PREFIX=TRAC,NUM= 5 ,SEV=W,SPEC= ,MF=G, + WTO=OPT,EC=YES,COLOR=SEV,ATTR=SEV, + TEXT='TRAC 5 W JOB is Late, Not Submitted by Target Ti+ me' This example shows a message that has been changed to always WTO, and the message appears on the Event Console in blinking purple. @ECLMSG PREFIX=TRAC,NUM= 51,SEV=E,SPEC=ABEND,MF=G, WTO=YES,EC=YES,COLOR=PURPLE,ATTR=BLINK, TEXT='TRAC 51E JOB Completed Abnormally - ' + +
Chapter 7. Startup and Verification

This section contains the following topics: Initialization and Startup Verification . . . . . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
252 254
A verification procedure is included that you can use to verify that Unicenter CA-Jobtrac is functioning properly. Use of the supplied IVP assumes you have completed the SMP/E installation process, the Unicenter CA-Jobtrac installation process (STAGE1 and STAGE2), and the customization tasks described in the chapter "Customization Tasks." If you have not completed these steps, you must do so before using the supplied IVP. This verification procedure is referred to as IVP. Before Running IVP: Before you can run IVP, you must have completed the install and customization steps up to this point and start Unicenter CA-Jobtrac, and you must follow the steps in this chapter for the IVP to work correctly. This chapter discusses these issues.
Chapter 7. Startup and Verification 251
Initialization and Startup

This topic covers multiple ways of initializing Unicenter CA-Jobtrac internals, starting the Unicenter CA-Jobtrac task, accessing Unicenter CA-Jobtrac, and ending the Unicenter CA-Jobtrac task.
Initialize Internals
S VINITx,PARM=IPL,SUB=MSTR Important! You must use this method of initializing Unicenter CA-Jobtrac ONLY during an IPL when using an IPLTABLE. Automatically Processing IPL Messages: The VINITx procedure for Unicenter CA-Jobtrac initialization can be run under the Master Subsystem to let some table processing to begin early in the IPL process, even before JES is started. With the use of a special AMR table called IPLTABLE, you can process received messages and issue commands and schedule or trigger batch jobs. By default, Unicenter CA-Jobtrac loads the IPLTABLE during IPL and switches to the regular AMR table after 15 minutes. If you do not want to wait the 15 minutes, you can activate a table using the online table services (for more information, see the Extended Scheduling Services Guide). For information about the IPLTABLE, see the chapter "Customization Tasks." For information about the other AMR tables, see the Extended Scheduling Services Guide. Using Unicenter CA-Jobtrac at Initialization Time: If you do not want to use the IPLTABLE processing feature, add this command to SYS1.PARMLIB member IEACMDxx: S JOBTRAC[.taskname,PARM=IPL] This command starts the specified Unicenter CA-Jobtrac and initializes the Unicenter CA-Jobtrac internals. The optional PARM=IPL parameter lets the IPL message prompt to the console operator as described in the global options information in the chapter "Customization Tasks." Restrictions on Using VINITx: Since VINITx running under the Master Subsystem (SUB=MSTR) is started so early in the IPL process, very few resources are available. For example, tasks running at this point in the IPL know only about data sets that are cataloged in the master catalog. Therefore, any data sets that must be accessed at this time must be cataloged in the master catalog. For other VINITx commands, see the Operator Guide.
Start the Unicenter CA-Jobtrac Task

Important! Unicenter CA-Jobtrac requires CA-GSS to be present to use its full functionality. Minimally, the CA-GSS CAILIB MUST be present. If it is not present, Unicenter CA-Jobtrac will not start. Procedure: If you do not start Unicenter CA-Jobtrac during your IPL, you can do so manually. To start the Unicenter CA-Jobtrac task, enter the following command on each system in the shared spool complex: S JOBTRAC[.taskname] Important! Normally, Unicenter CA-Jobtrac startup processing by default begins submitting jobs/events, but since the checkpoint database was just formatted, no jobs/events will submit.
Access Unicenter CA-Jobtrac

From ISPF: To access Unicenter CA-Jobtrac from ISPF, select the option set up by your systems programmer. With a CLIST: To access Unicenter CA-Jobtrac using a CLIST, enter the following command, which executes the initialization CLIST created by the STAGE2 job stream: EX your.CA-Jobtrac.SAMPJCL(TCLIST3) or EX your.CA-Jobtrac.SAMPJCL(LIBDEF) The function of TCLIST3 is to allow entry into Unicenter CA-Jobtrac until your ISPF menu has been updated to include Unicenter CA-Jobtrac as a selectable menu item (see the information about adding Unicenter CA-Jobtrac to your ISPF Main Menu in the chapter "Customization Tasks").
End the Unicenter CA-Jobtrac Task

To end the Unicenter CA-Jobtrac task, enter the following command: P taskname
Verification
Verification
This topic covers the contents and use of the installation verification procedure.
Contents of IVP
The Installation Verification Procedure (IVP) supplied with the product consists of an internal verification procedure, a dynamic schedule, JMF, ADI, AJO, and CA-Easytrieve report testing, and a series of events to be scheduled. All IVP members can be found in your SAMPJCL library. Members Supplied: The Unicenter CA-Jobtrac IVP members supplied and their contents are described in the following tables: SCL Member IVP001 Contains Unicenter CA-Jobtrac Dynamic Schedule SCL
JCL Member
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 that tests Unicenter CA-Jobtrac and related IBM exits to see that they are installed and active Sample JTEZREPT - List Schedule Sample JTEZREPT - List History IEFBR14 IEFBR14 IEFBR14
JREPI1 JREPI2 TESTI1 TESTI2 TESTI3
Yes Yes Yes Yes Yes
Dynamic Task 0ARCHIVE
Contains Tests event and sysout archival, dynamic task scheduling
Modify JOB statement No
All other jobs will need their JOB statements.
Verification
IVP Assumptions: The IVP assumes the following environment: The IVP001 schedule member resides in the location 001 SCL library. This member must be defined as the TRACS001 SCL library in the Unicenter CA-Jobtrac started task. The STAGE2 installation job stream created a Unicenter CA-Jobtrac started task with TRACS001 pointing to the library defined for the INSTLIB keyword. The Unicenter 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. This DD statement defines the JCL library for location ID 001 and contains the IVP events JOBT@#$J, TESTI1, TESTI2, TESTI3, IVPAJO, IVPJMF, IVPADI, JREPI1 and JREPI2. The ISPF CLIST for using Unicenter CA-Jobtrac should also allocate this data set, or it should be included in your TSO logon procedure. The ASMAUTH customization event must also run to generate a default TRACAUTH table with a default location ID of 1. This is needed because the IVP001 schedule member schedules events for location ID 001. The IVPAJO member must have the PRODDATE member sample in the cai.SAMPJCL library copied over to the DATELIB data set created by the STAGE2 JCL. Member IVPJMF must have the JMFSYM01 sample member from the cai.SAMPJCL copied over to the DATELIB data set. The JTEZREPT procedure as created in STAGE2 customization exists in an executable form in an accessible procedure library. Because the 0ARCHIVE dynamic task will be scheduled as part of the IVP, 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).
Verification
Using Other Libraries: If you decide to use libraries other than those generated during initial installation, modify the Unicenter CA-Jobtrac started task procedure or use a different TRACAUTH table. You should ensure that: IVP001 exists in the SCL library defined as TRACS001 in your JOBTRAC STC task. It can be copied from your SAMPJCL installation library if necessary. IVP001 schedules all events to a location ID to which you are authorized by whatever TRACAUTH table you are using. The JCL members TESTI1, TESTI2, TESTI3, IVPAJO, IVPJMF, IVPADI, JREPJ1, JREPI2, and JOBT@#$J exist in the JCL library for the location ID to which you have scheduled them. They can be copied from the SAMPJCL installation library if necessary. The proper data set definition exists for the JCL library in both the Unicenter CA-Jobtrac started task procedure and your TSO session (either allocated in your Unicenter CA-Jobtrac CLIST or added to your logon procedure) or the DYNAMLOC member. If you change the name of the internals verification procedure job (JOBT@#$J), it must be five to eight characters ending with @#$J. It is not recommended.
Procedure: Follow the steps below to use the supplied IVP: 1. Modify the JCL supplied for the sample jobs to meet your installation requirements. Check the TESTII1, TESTI2, TESTI3, IVPAJO, IVPJMF, IVPADI, JREPI1, JREPI2, and JOBT@#$J jobs for JOB statement updates. To view sysouts, 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. 2. Enter the Unicenter CA-Jobtrac ISPF interface and issue the following command in the COMMAND field on the CA-Jobtrac primary panel to begin execution of the IVP. All Unicenter CA-Jobtrac commands require dynamic schedule names and task names starting with 0 (zero). RUN IVP 1,L= 1
The command loads the dynamic schedule's SCL and performs syntax checking of the input. 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. To view the output of the schedule, you can tab to the schedule name and enter the O (Output) line command. 3. When the schedule is loaded, enter RALL or D in the COMMAND field and press Enter. This command displays all events on the schedule (after initial installation, only the IVP events should be displayed).
Verification
4. The Dep Codes (dependency) field for TESTI1 should have a manual (M) dependency. Tab to event TESTI1, enter the A (release dependency) line command, and press Enter. The A command releases the manual dependency and lets Unicenter CA-Jobtrac submit the event. Each event will run after its predecessor completes, in the following sequence: TESTI1 TESTI2 TESTI3 JOBT@#$T IVPADI IVPAJO IVPJMF JREPI1 0ARCHIVE JREPI2 Releases TESTI2 upon successful completion Releases TESTI3 upon successful completion Releases JOBT@#$T 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 Releases JREPI2 upon successful completion Last event
The following describes the members: IVP001 Tests dynamic schedule loading and Unicenter CA-Jobtrac/ISPF online processing. TESTI1, TESTI2, and TESTI3 Tests event submission, tracking, and sysout capture (IEFBR14). JOBT@#$J Tests to see the dynamic exits of Unicenter CA-Jobtrac. IVPADI Tests the Automatic Date Insertion abilities of Unicenter CA-Jobtrac. Check the output to see if the comments match with the days submission date. IVPAJO Tests the Automatic JCL Override abilities of Unicenter CA-Jobtrac. Check the output of this job to see that the STEPNAME is the day of the week this job has submitted. This should be todays. IVPJMF Tests the JCL Modification Functions. Check the output of this job to see that the Dates in the comments are correct. JREPI1 Tests the JTEZREPT utility checkpoint reporting features. JREPI2 Tests the JTEZREPT utility history reporting features.
Verification
0ARCHIVE Tests event and sysout archival, dynamic task scheduling and is not a member of SAMPJCL; it is a dynamic task used for Unicenter CA-Jobtrac file maintenance. 5. If you selected the tape option during customization, the 0ARCHIVE dynamic task might require a tape mount. After the 0ARCHIVE task has completed, the TESTI1, TESTI2, TESTI3, AVPADI, IVPAJO, IVPJMF, JREPI1, and the 0ARCHIVE events that just completed will be deleted from the current schedule and moved to history. 6. Unicenter CA-Jobtrac signals that each event is complete by indicating COMPLETED in the Current Event Stat field on the panel. Until Unicenter CA-Jobtrac finishes capturing an event's sysouts, an * (asterisk) appears to the right of the date at the end of the event's record. To view an event's sysouts after the * disappears, tab to the event and enter the O (output) line command. Press the END PF key or enter the END command to return to the Scheduled Event Display panel. At any time, you can select the detail panel to view an event's schedule detail by using the S (select) line command. Messages Received: The following sequence of messages should appear on the JES JOB LOG for the JOBT@#$J job. These messages indicate successful execution of the IVP. If you do not receive these messages, the installation of the Unicenter CA-Jobtrac internals was not successful. If you are running multiple copies of Unicenter CA-Jobtrac, in any combination, you might receive duplicates of the GJTR exit messages. IEF1961 GJTRIVP2 - IEFUJV EXIT DETECTED THE IVP JOB GJTRIVP2 - IEFUJV EXIT DETECTED THE IVP JOB GJTRIVP2 - IEAVMXIT DETECTED THE IVP WTO @#$J - GJTRIVP2 - THIS TESTS THE WTO INTERFACE
Chapter 8. Upgrading, Testing, Running Multiple Copies

This section contains the following topics: Release Compatibilities and Incompatibilities Conversion Notes . . . . . . . . . . . . . . . Upgrade Your Production from r3.5 to r11 . Return to the Prior Release . . . . . . . . . . Run r3.5 Production and r11 Test System . Run Multiple STCs on Same CPU . . . . . . Run in a Shared Sysplex Environment . . .
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
260 261 263 264 265 266 268
When using all the functions and features to their fullest, Unicenter CA-Jobtrac functions as an operating system for production control. You should treat a new Version of Unicenter 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.
General Procedure
You should test Unicenter CA-Jobtrac Version just as you tested the prior Version of Unicenter CA-Jobtrac when you first installed it. You should schedule routine maintenance, backups, archives, and so on, using Unicenter CA-Jobtrac Version for several days. Take time to familiarize yourself with the new functions and facilities. When you are comfortable with Version, make it your production system.
Memory Requirements
If you plan to run previous Versions of Unicenter CA-Jobtrac with Version, take into account the amount of CSA the previous Versions will need. Each previous Version requires at least 150 KB below the line. Extended CSA (above the line) will also grow. Note: The CSA is reused whenever Unicenter CA-Jobtrac is stopped and restarted under normal circumstances. The expanded CSA is not released or reused when Unicenter CA-Jobtrac is backed out of the system using the 'F JOBTRAC,BACK' operator command. New storage is acquired following a backout of Unicenter CA-Jobtrac.
Chapter 8. Upgrading, Testing, Running Multiple Copies 259
Release Compatibilities and Incompatibilities
Release Compatibilities and Incompatibilities

To ensure that you do not obtain Unicenter CA-Jobtrac prior Version load modules from the linklist libraries during testing, you need to STEPLIB to your r11 load library in your STC, TSO logon procedure, and all batch jobs executing Unicenter CA-Jobtrac programs. Also, due to new SCL keywords, we recommend that SCL libraries are kept separately. Note: If you are using production SCL and JCL libraries, you might get duplicate production JCL submitted. We recommend that you use different SCL and JCL libraries.
Compatibilities
The following features in r3.5 are compatible with r11: All schedules are fully supported. However, since we have updated syntax checking for schedule loads, we recommend that you test all your production SCL. Also, you should not add new r11 features to your production schedules until you have accepted r11 as a production system. All date card formats are compatible. All JCL override formats are compatible. All TRACAUTH table definitions are supported.
Incompatibilities
The r3.5 programs cannot share or access the r11 database files. Also, r11 programs cannot share or access the r3.5 checkpoint files. If you use user exits 01, 03, 06, 09, 10, 13, 16, 20, 22, 23, and 30, you need to rewrite them to process the new data formats. For exit specifications, see the Reports, Maintenance, and Recovery Guide.
r11 Features
You cannot install r11 into the same SMP/E CSI, target, and DLIB libraries as r3.5 of Unicenter CA-Jobtrac. r11 is compatible with other CA products.
Conversion Notes
Conversion Notes
This topic provides conversion notes on Unicenter CA-Jobtrac files.
Checkpoint and History

This step performs the conversion from the JFST access method to CA-Datacom/AD database tables. Member Used: The JCL for this step is in member CONVERT in your Unicenter CA-Jobtrac SAMPJCL library. Procedure: Take the following steps to convert to CA-Datacom/AD database tables: 1. Unicenter CA-Jobtrac r11 must be initialized for the token to which you are converting. If you have previously started Unicenter CA-Jobtrac r11 on the system since the IPL, this has performed the initialization. If you have not or are converting to another token, you can run the VINITx PROC with the token (x) specified in the //JOBTRACx DD DUMMY. 2. The Stage1 and Stage2 processes created this member so that all optional parameters are already incorporated in this member. However, review the JCL in the CONVERT member to verify accuracy. 3. Modify the JCL if needed. The JOBTRACx and JOBHISTx DDs should have the r3.5 checkpoint and history files you are planning to convert. You can change the token that will be used in the new database by changing the token value on these two DD statements. Assume that your current token is X, that your checkpoint file is named CAI.JOBTRACX.CHECKPT, and that history file is named CAI.JOBTRACX.HISTORY. You would then specify the following: //JOBTRACZ DD DSN=CAI.JOBTRACX.CHECKPT,DISP=SHR //JOBHISTZ DD DSN=CAI.JOBTRACX.HISTORY,DISP=SHR The r3.5 checkpoint and history data for token X is converted into the r11 database for token Z. As mentioned in Step 1, Unicenter CA-Jobtrac would have to be initialized for token Z by having run the JOBTRACZ jobs or the VINITZ job with the //JOBTRACZ DD DUMMY. 4. Run the CONVERT job to perform the conversion.
Capture
The capture file format has not changed. If you want a new capture file, build it with GJTRVFMT and point OLDCAP to the old capture file, or you can use the r3.5 capture file.
Conversion Notes
PDS Data Sets

All JCL files and SCL DSNs can be copied to new libraries or used as they are for the Unicenter CA-Jobtrac r11 STC, PROCs, and CLIST.
TRACAUTH
If you are using the Unicenter CA-Jobtrac internal security TRACAUTH table, your r3.5 version of this module is compatible with r11. You can copy your existing TRACAUTH module from your r3.5 CAILIB to your r11 CAILIB to keep your existing TRACAUTH definitions.
Upgrade Your Production from r3.5 to r11
Upgrade Your Production from r3.5 to r11

We recommend that you use the same tokens from r3.5 for the new Unicenter CA-Jobtrac r11. You can use the following as a guideline to upgrade from Unicenter CA-Jobtrac r3.5 to Unicenter CA-Jobtrac r11. To upgrade your production from r3.5 to r11 1. Complete the Unicenter CA-Jobtrac Version installation procedure. 2. Issue the Unicenter CA-Jobtrac HOLD command (F stcname,HOLD). Next shut down Unicenter CA-Jobtrac r3.5 (P stcname). 3. Submit backup jobs for the checkpoint, capture, and jobhist files. Note: See r3.5 SAMPJCL for sample JCL. If using linklist, make sure that your Unicenter CA-Jobtrac r11 CAILIB replaces the old Unicenter CA-Jobtrac r3.5 TRACLINK loadlib and refresh LLA. 4. Make sure that all the ddnames for the checkpoint and jobhist files reflect the correct names in your PROCs, CLISTs, and batch jobs executing Unicenter CA-Jobtrac programs. The JOBTRACx ddname should be a DD DUMMY. 5. You need to either IPL or back out the internals of Unicenter CA-Jobtrac (S VINIT3,PARM=BACK). When using the BACK command, see the Operator Guide for details. 6. Start the CA-Datacom/AD MUF (S stcname). 7. Start the new Unicenter CA-Jobtrac Version STC (S stcname). 8. Log on to Unicenter CA-Jobtrac Version and issue the STATUS command to verify Version. 9. Test the installation with the verification procedures in Chapter 7, Startup and Verification on page 251. 10. Release the production workload from r11 (F stcname,RELEASE).
Return to the Prior Release
Return to the Prior Release

Use these procedures to return to a prior Version of Unicenter CA-Jobtrac.
Return to r3.5
Perform the following steps to return to r3.5: 1. Shut down Unicenter CA-Jobtrac r11 with a BACK (F stcname,BACK) or IPL. Put the Unicenter CA-Jobtrac r3.5 CAILIB back in the linklist (if that is where it was). Refresh LLA if needed. Note: When using the BACK command, see the Operator Guide for details. 2. Make sure that all the ddnames for the checkpoint, jobhist, and capture files reflect the correct names in your PROCs, CLISTs, and batch jobs executing Unicenter CA-Jobtrac programs. 3. Edit any of your schedules that had been updated to use new r11 keywords and comment them out or remove them. 4. Do one of the following: Use the Unicenter CA-Jobtrac r11 capture file Use the old DSNs from Unicenter CA-Jobtrac r3.5 RESTORE the files from the backup files from Unicenter CA-Jobtrac r3.5 for the checkpoint, capture, and jobhist files from the backups created when upgrading from r3.5.
5. Start Unicenter CA-Jobtrac r3.5 (S stcname).
Reverse Conversion (Optional)

As part of the backoff procedure, perform this step to convert CA-Datacom/AD database tables to JFST checkpoint and history files. Member Used: The JCL for this step is in member CONVERTB in your Unicenter CA-Jobtrac SAMPJCL library. To reverse the file conversion: 1. The Stage1 and Stage2 processes created this member so that most optional parameters are already incorporated in this member. However, there are parameters that need to be changed before running this job. Refer to the comments in the CONVERTB member to make appropriate changes. 2. Modify the JCL. 3. Run the CONVERTB job to perform the reverse conversion.
Run r3.5 Production and r11 Test System
Run r3.5 Production and r11 Test System

We recommend the following procedures to run r3.5 production and r11 test system: 1. When starting the Unicenter CA-Jobtrac r11 installation, you need to do the folllowing: a. Choose a new token. b. Create a new CA-GSS subsystem ID. c. Choose a new AUTOSCHD character. d. Create new STC procedure, CLIST, and any batch jobs executing Unicenter CA-Jobtrac programs using the new CAILIB as a STEPLIB, all new ddnames, and tokens. Note: The JOBTRAxx member in PPOPTION data set needs the appropriate options set for the AUTOSCHD character since they are initially set to the default values. Also check other options that you want to set. 2. Files a. Token: JOBTRACx DD DUMMY must be specified in the JCL for r11. You must use a new token for the new database. b. Capture: Start with a new, empty capture data set. 3. Start the new Unicenter CA-Jobtrac STC r11. 4. Log on to Unicenter CA-Jobtrac r11. 5. Perform the installation verification procedures in Chapter 7, Startup and Verification on page 251. 6. Test the new Unicenter CA-Jobtrac r11.
Run Multiple STCs on Same CPU

Use the following procedure to run multiple Unicenter CA-Jobtrac STCs on the same CPU: 1. Do not change any of the production Unicenter CA-Jobtrac PARMs or data sets in the STC, PROCs, DYNAMLOC member, or CLIST. 2. Ensure that you have a new Unicenter CA-Jobtrac token and a new SSID for CA-GSS. 3. Update your logon CLIST for the new JOBTRACy and GSSx and any PROCs that use Unicenter CA-Jobtrac programs. //JOBTRACy DD DUMMY //CAPTURE DD DISP=SHR,DSN=your.new.capture 4. Create a new JOBTRACy PROC with a unique name such as JOBTRACy. Add a //STEPLIB DD to this PROC if needed. 5. (Optional) Create a new PPOPTION. This is not necessary, but RESOURCE and EXCLPARM would be shared otherwise. 6. You can still use the existing TRACSnnn, TRACJnnn, TRACDnnn, TRACTnnn, or TRACRnnn files if you would like. However, we suggest you just copy the existing production copies into a unique set of files for the JOBTRACy PROC. This recommendation is good sense, but Unicenter CA-Jobtrac will have no problem sharing these libraries. 7. MAKE SURE AMPLE CSA AND ECSA IS AVAILABLE if running multiple copies of Unicenter CA-Jobtrac. 8. AUTO-SCHD character and class must be unique to each Unicenter CA-Jobtrac. 9. CA-GSS Considerations a) b) c) You must create a new GSSx PROC to go with the new JOBTRACy PROC. GSSx will execute PGM=SRVSYS. Add a //STEPLIB new.CAILIB to this PROC if needed. Add a //JOBTRACy DD DUMMY GSSx can still use existing IMODS but must have a different SSNAME defined such as SSNAME IS11.
10. In JOBTRACy GLOBAL OPTIONS you must define the GSSx started task and the SSNAME IS11. (RUNPARM member.) Important! DO NOT USE SSNAME AS EXISTING PRODUCTION CA-GSS! (Unicenter CA-Jobtrac uses that SSID. If CA-GSS tries to use the same one, it will not work, except possibly if CA-GSS can be guaranteed to be up first. Do not risk it.) 11. You must copy the production Unicenter CA-Jobtrac PARMs (JOBTRA00) to the new JOBTRACy PPOPTION file. No changes should be required. 12. If you are using Unicenter CA-11 you must add the RERUN=CA-11 PARM and the INSERTRMS=x, where x is class to be monitored by Unicenter CA-11, into the JOBTRA00 member of the PPOPTION for JOBTRACy. 13. Create a new logon CLIST for the JOBTRACy logon. It should have all the new files allocated just like the original production CLIST. You will be required to add the CAILIB for the new JOBTRACy as a STEPLIB or ISPLLIB. Files should be allocated as they are for the new STC, not the old CLIST. ISPLLIB is not sufficient. STEPLIB is necessary for CAILIB. This can lead to very sneaky bugs, where modules from different levels are executed at different times. You cannot log on in split screen to multiple copies of Unicenter CA-Jobtrac. 14. Start JOBTRACy on the system. It loads the hooks dynamically and should start up GSSx as well.
Run in a Shared Sysplex Environment

Unicenter CA-Jobtrac can control the workload across multiple systems in a sysplex. You must start Unicenter CA-Jobtrac on each system where you would like the workload to be monitored. For example, SYS1 is the primary Unicenter CA-Jobtrac. The primary system is where all event submission takes place. SYS2 and SYS3 are your secondary monitor systems. The monitor systems do not submit any events. They monitor the events that run on the system that are submitted by the primary system. The primary and monitor systems share a CA-Datacom/AD database. CA-Datacom/AD must be customized to allow the database to be shared. For more information about the required changes, see Modify CA-Datacom/AD for Unicenter CA-Jobtrac on page 162. You may have already setup CA-Datacom/AD for this support. Review your CA-Datacom/AD setup to ensure that you made these changes. The following summarizes the requirement for establishing the Sysplex Sharing environment in CA-Datacom/AD: Note: If you have already installed CA-Datacom/AD and have implemented the Shadow MUF feature, some of the following statements may be different. For more information about the Shadow MUF configuration, see the CA-Datacom/AD Shadow MUF white paper at ca.com/datacom (click on the White Papers link). In the CA-Datacom/AD startup parameters in CUSMAC(DBDATIN1), be sure you have correctly defined the following keywords: MUF Defines the name of the CA-Datacom/AD MUF. This name is required when sharing the MUF. TASKS Defines the maximum number of CA-Datacom/AD internal tasks to be available. Each connection to the database requires a task. This number includes a separate value for those sessions that are connecting through XCF. The XCF value is also added to the total number of task. XCFFROM Defines the XCF group name to be used to share the MUF. This parameter lets you specify a specific job name that can connect to the MUF. For Unicenter CA-Jobtrac, the job name must be specified as *. During the installation of CA-Datacom/AD, module DBSIDPR was created. This was assembled to define the MUF address space that will be connected to and the methods that can be used to connect to it. For XCF sharing, the following parameters must be added to the DBSYSID macro in the DBSIDPR assembly and module must be reassembled to include them.
TOMUF Defines the name of the MUF that is connected to by the application (Unicenter CA-Jobtrac). This must match the MUF parameter defined in the CA-Datacom/AD startup parameters (described previously). TOGROUP Defines the XCF group that is used to connect to the MUF. This must match the value specified in the XCFFROM keyword in the CA-Datacom/AD startup parameters (described previously). For more information about setting up CA-Datacom/AD for sharing, see Modify CA-Datacom/AD for Unicenter CA-Jobtrac on page 162. Here are some Unicenter CA-Jobtrac considerations when running Unicenter CA-Jobtrac in a Sysplex environment: Define the primary and secondary monitor systems in the JOBTRAnn member of the PPOPTION data set by using the keywords SYNCSYS1, SYNCSYS2, and SYNCSYS3. SYNCSYS1 defines the primary system. SYNCSYS2 and SYNCSYS3 define the secondary monitor systems. Each keyword points to the SMF system ID of the appropriate system. Note: Updating the options SYNCSYS1 through SYNCSYS3 requires that Unicenter CA-Jobtrac on each system be recycled to switch the primary. The SMF system IDs defined in the JOBTRAnn member are stored in the database. Recycling Unicenter CA-Jobtrac has no effect on what is stored in the database. To switch the primary system, you must use the modify command F stcname,ACTSYS=xxxx Also you can view the primary and secondary definitions from ISPF by looking at the SYSID priority list (SYS OPTS) on the Unicenter CA-Jobtrac global options panel. You can have separate JES spools on your systems or a shared JES spool environment. Unicenter CA-Jobtrac database and capture files are shared between the primary and secondaries. All tokens for the DD statements must be the same. The following Unicenter CA-Jobtrac message displays in the JES log on the primary system. CA-JOBTRAC - PRIMARY SUBMISSION SYSTEM (CA11) TOKEN(B) RELEASE(11.00) LV(SP00). The following Unicenter CA-Jobtrac message displays in the JES log on the secondary systems. CA-JOBTRAC - AUTOMATION MONITOR SYSTEM (CA31) TOKEN(B) RELEASE(11.00) LV(SP00).
Changing Primary Submission System: Unicenter CA-Jobtrac lets you change the primary system. For more information about the conditions and concerns for performing this switch, see the Reports, Maintenance, and Recovery Guide.
Appendix A. NJE Support

This section contains the following topics: Installation and Setup . . . . . . . . . Job Submission . . . . . . . . . . . . . Job Execution . . . . . . . . . . . . . . Job Termination . . . . . . . . . . . . ISPF Interface . . . . . . . . . . . . . . Batch Archiving and JTEZRPT . . . . REXX Stack Information for NJE Jobs
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
272 273 274 275 276 277 278
Appendix A. NJE Support 271
Installation and Setup
Installation and Setup

Consider the following when installing and setting up CA-GSS: Unicenter CA-Jobtrac NJE support requires CA-GSS. CA-GSS must be set up to include networking support for all JES nodes in which Unicenter CA-Jobtrac is to be used for NJE support. This is done using the GoalNet features of CA-GSS. For information about GoalNet, see the CA Common Services Getting Started and the CA Common Services Administrator Guide. 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). The NJE NODE option lets you specify whether to activate the Unicenter CA-Jobtrac NJE support for this instance of Unicenter CA-Jobtrac on this system image. If you specify Y, the NJE Node Tokens field becomes significant. A Unicenter CA-Jobtrac token is the x in the Jobtracx DD statement. The token identifies and differentiates individual copies of Unicenter CA-Jobtrac. In the NJE Node Tokens field, you specify which Unicenter CA-Jobtrac events are recognized by this Unicenter CA-Jobtrac. This is done by listing up to 39 tokens. If you leave this field blank, all tokens (that is all events from all copies of Unicenter CA-Jobtrac) are processed by this Unicenter CA-Jobtrac. If you leave the field blank, do one of the following: Only start up one NJE-capable Unicenter CA-Jobtrac on any single system image Specify nonoverlapping tokens for each Unicenter CA-Jobtrac running
The JES /*ROUTE or /*XEQ statements identify an event as an NJE event. If you explicitly specify tokens and you submit NJE jobs to the submitting node itself, you should specify the token of the submitting Unicenter CA-Jobtrac itself in the token list. The specified NJE nodes apply only to the NJE events for the copies of Unicenter CA-Jobtrac that are specified as being NJE nodes. All other Unicenter CA-Jobtrac instances recognize only their own tokens. NJE systems require all Unicenter CA-Jobtracs to be primary Unicenter CA-Jobtracs and not monitor Unicenter CA-Jobtracs. It is important to use a SYSOUT package in an NJE environment. Unicenter 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).
Job Submission
Job Submission
Consider the following when submitting jobs: AUTO-SCHD jobs running on an NJE node are not supported. DUMMY jobs running on an NJE node are not supported. In an NJE environment, if NOTIFY is specified, only users on 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. Use JES /*ROUTE XEQ or /*XEQ control statements to route NJE jobs to other nodes. NJE jobs must use the JES /*ROUTE XEQ or /*XEQ control statements for Unicenter CA-Jobtrac to recognize them as NJE jobs. Unicenter CA-Jobtrac cannot properly track a manually rerouted job after it has already gone through JES conversion. Additional data in the form of dummy DD statements is added to the Unicenter CA-Jobtrac trailer step for NJE jobs. In an NJE environment, only events and resources (execution dependencies) on the local node are checked before an event can be submitted. In other words, when an event is to be submitted on a remote node and references other events and resources (execution dependencies) on the remote node, those other events and resources will not be checked by Unicenter CA-Jobtrac in determining an event's eligibility for submission. In an NJE environment, exclusion rules only work within a local node. In an NJE environment, generic resources only work within a local node. In an NJE environment, the CCPF table on the executing system is the CCPF table used for checking condition codes. In an NJE environment, the AMR table only works on the local node. In an NJE environment, the ADR table only works on the local node. NJE job status is available through the ISPF interface. TRACX09 is invoked at both the submitting and executing node.
Job Execution
Job Execution
Consider the following when executing jobs: The NJE job will be tracked by Unicenter CA-Jobtrac. An NJE surrogate checkpoint record is added to the remote Unicenter CA-Jobtrac checkpoint data set for tracking, display, and recovery purposes. The NJE surrogate contains a subset of the information from the actual checkpoint record. The information is viewable but not modifiable by the Unicenter CA-Jobtrac ISPF interface user. When the NJE job actually begins execution on the executing node, the submitting node's Unicenter CA-Jobtrac ISPF display will indicate its executing status. Any Notifies as specified in the TRACAUTH table will only be done on the executing node as defined in the executing node's TRACAUTH. TRACX09 is invoked at both the submitting and executing node.
Job Termination
Job Termination
Consider the following about terminating jobs: Successful or unsuccessful termination of a job will result in the passing of the termination status back to the originating node. Once the status is posted at the originating node, normal Unicenter CA-Jobtrac processing occurs. If the return of the termination status of a job back to its originating node is successful, the NJE surrogate checkpoint record is automatically deleted at the executing node. No history information is copied to the history database at the executing node. History information is copied to the history database at the submitting node. If the returning of termination status is unsuccessful for whatever reason (for example, networking error, originating node down), the NJE surrogate record is retained on the checkpoint. It is used to attempt to retry the returning of status at the next Unicenter CA-Jobtrac startup. The NJE surrogate can only be removed by the successful return of status or the next Unicenter CA-Jobtrac job archive run with the ALL option. It is important to use a SYSOUT package in an NJE environment. Unicenter 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).
ISPF Interface
ISPF Interface
Consider the following about the ISPF interface: NJE jobs in Awaiting Execution or Executing status have a Scheduled Event Display status of N-status-nodename, SYS=ssss where status is either NAWT for Awaiting Execution or EXE for Executing, nodename is the remote JES node name and ssss is the submitting system's SMF system ID. The event execution detail display for executing or completed jobs displays the JES node if the job was an NJE job. NJE jobs running on the executing node have an NJE surrogate checkpoint record. The status on the Scheduled Event Display for these submitted NJE jobs includes an N instead of a J preceding the JES job number. Only a subset of the normal line commands on the Scheduled Event Display are available for remotely-submitted NJE jobs. The line commands available are: @, *, ?, N, O, P, Q, S, and 0 (zero). When the S line command is used to Select an NJE submitted job, the new NJE Execution Detail panel appears that contains a subset of the information normally available when selecting an event for display. The new fields that appear on this panel for any NJE submitted jobs are the JES Node Name of the submitting node, the GSS Node Name of the submitting node, the Original Version Number of this job on the submitting node, and NJE status. For more information about the NJE Execution Detail panel, see the Operator Guide. 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. The purge command resets the completion status and places an Output Release on the job. You can now perform other appropriate actions against the job. On displays of times for NJE jobs on either the submitting or executing nodes, time zone differences are taken into consideration and all times are adjusted to reflect local time. When selecting events to display on the Scheduled Event Display, a N=nodename command is available. Specifying this command with the desired JES node name limits the display to NJE jobs submitted to or from the designated node. 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, while the S code selects only NJE surrogate jobs, those jobs which have been remotely submitted from another node.
Batch Archiving and JTEZRPT
Batch Archiving and JTEZRPT

Consider the following about archiving and reporting: You must use the ALL operand to force the archiving of NJE jobs, regardless of the special NJE status REMOTE POST ERROR. Otherwise, an NJE job with this status remains on the Unicenter CA-Jobtrac checkpoint so that a retry of posting the termination status to the originating node can be performed. When listing event information for a JTEZREPT, additional information is made available in the JES ID (JOB NUMBER field) as appropriate to the event, due to a space limitation: Jnnnnnnn Nnnnnnnn IMOD COMMAND DUMMY Normal job (where n is job number) NJE job (where n is job number) IMOD event COMMAND event DUMMY job
When listing event information for an archive or purge report, the same preceding additional information is made available in its own data columns with no space limitation: EVENT TYPE NJE Indicates JOB, IMOD, CMND, or DUMMY as appropriate. Indicates Y/N for whether this is an NJE job.
REXX Stack Information for NJE Jobs
REXX Stack Information for NJE Jobs

The following is the REXX stack information for NJE jobs: ETIM Indicates the end time and date for the event. Returns the information in the hh:mm mm/dd format including the colon and slash. NJE Indicates the the JES node name on which the event is executing or has executed if this event is an NJE job that has been submitted to another JES node. Otherwise, this is blank. ONQU Indicates the event has been submitted and recognized by Unicenter CA-Jobtrac if this is an AUTO-SCHD event. Otherwise, this is blank. SUBT Indicates the actual time and date the event is submitted for execution by Unicenter CA-Jobtrac. Returns the information in the hh:mm mm/dd format including the colon and slash.
Keywords
The following table contains the keywords and options: Keyword END_TIME or ETime JES_NODE or JESNode NJE (Yes or No) ONQueue (Yes or No) Options Same options for definition as ATime, STime, and TTime. Up to eight-character JES node name where this event is executing. Indicates whether this is an NJE job. Indicates whether the JCL associated with this AUTO-SCHD job has been submitted and recognized by Unicenter CA-Jobtrac. Same options for definition as ATime, STime, and TTime.
SUB_TIME or SUBMIT_Time
Appendix B. Connecting Systems for Cross-Platform Scheduling

This section contains the following topics: z/OS CAICCI Installation and Considerations . . . Remote Scheduler Installation and Considerations
. . . . . . . . . . . . . . . . . . . . . . . . . . .
280 281
These topics are designed to help you set set up CAICCI network connections on z/OS, NT, and UNIX to support cross-platform scheduling. Note: You can find more detailed information in the CA Reference Guide and the Unicenter Job Management Option or Unicenter AutoSys JM manuals for the specific platform.
Appendix B. Connecting Systems for Cross-Platform Scheduling 279
z/OS CAICCI Installation and Considerations

The CCIPARMS control options must be updated to activate the CAICCI gateway tasks. These options are described in the CA Common Services Administrator Guide in the CAICCI control options topic. Following is a sample of the required protocol statement: PROTOCOL(TCPIPGW,85 ,2,XE21)
Optionally, you can define the connection on z/OS for the remote scheduler system. We do not recommend this since it is more manageable to define the z/OS system on the Windows or UNIX platform. Following is an example of the CCIPARM statement necessary to define a remote node to CAICCI on z/OS: NODE(TCPIPGW,141.2 2.72.7:1721,2,USLIGPEX) CONNECT(USLIGPEX) The SYSID parameter in the CCIPARM member names specify the unique name to be used in connecting with this z/OS system. SYSID(XE21) This name is specified on the remote CAICCI system to identify CAICCI on the z/OS system. From z/OS, in the syslog, the following message indicates a successful connection to the remote scheduler computer nnnnnn: CAS96 3I - CAICCI XE21 CONNECTED TO CAICCI nnnnnn
Remote Scheduler Installation and Considerations

CAICCI connections must be defined on the remote system. This is described in the documentation for Unicenter AutoSys JM, Unicenter Job Management Option, or Unicenter Universal Job Management Agent. For information about CAICCI setup, see your scheduling product's documentation.
Appendix B. Connecting Systems for Cross-Platform Scheduling 281
Index
Special Characters
@AMRGEN statement 209 AXINS02 91 AXINS03 91 AXINS04 92 AXINS05 92 AXIVP01 98 AXIVP02 98 AXNEW01 94 AXNEW02 94 AXNEW03 95 AXNEW04 95 AXNEW05 96 AXNEW06 96 AXNEW07 97 AXNEW08 97
A
abending event output, holding 191 ACCEPT processing 105 accessing the product 253 AD11STOP 98 AD11STRT 98 ADD PROC members 94 ADD command 148 address, email 142 Adobe Acrobat PDFs 102 Advantage CA-Datacom/DB 2, 83 SVC, installing 33 Advantage CA-Roscoe 30 AllFusion CA-Librarian interface 53 modules 107 support 193 AllFusion CA-Panvalet interface 53 modules 107 Allocating data sets 94 SAMPJCL library 89 AMR support 208 APF authorization 105 APPLY processing 104 archive tape block size 200 disposition 199 high-level qualifier 199 retention period 200 unit 199 archiving NJE jobs 277 ARM (Automatic Restart Management processing) 131 auto-queue job classes 193 AUTO-SCHD, allowing 187 automatically scheduling events using JCL, allowing 187
B
backing up databases backup types 47, 96 50
C
CA Common Services CA LMP 26 CA-C 27 CA-Easytrieve 27 CA-GSS 28 CA-XPS 28 CAICCI 28 CAIENF 28 CAIRIM 29 installing 82 overview 26 ViewPoint 30 CA Common Services for z/OS and OS/390 CA LMP 26 CA-Blockmaster 53 CA-C 26, 27 CA-Datacom/AD 27 backup and recovery 47 database 122 database files 12 DBID option 137 FCSTDBID option 144 modifications 162 Multi-User Facility 83
33
Index 283
CA-Datacom/AD (continued) overview 2, 27 placement considerations 46 security 56 SYSDBID option 155 terms 47 CA-Easytrieve 27 CA-GSS accessing other products 54 and NJE 271 and Unicenter CA-Jobtrac 41 modifying 167 overview 28 requirements 232 CA-HyperBuf 53 CA-JCLTrac DB2 setup for 218 enabling 219 UCT setup 218 user control table 205 user control table setup 218 CA-Jobtrac Global Options panel 186 CA-XPS 28 CAICCI 28, 232, 279 and Event Console 245 overriding application name 136 CAIENF 28, 106 CAIMAC library 13 CAIRIM 29, 33, 36 CAISSF 29, 36 CAIVPE 30 CAS9 procedure 105 catalog error response 191 CBIPO 37 checkpoint database description 12, 122 RAMAXCC JOBTRAnn Option 148 CICS using CAIVPE 30 CLASS statement 222 CLIST allocations, updating 180 cold backup 50 command set scheduling, PDS for 200 COMMNDxx, modifying 252 Common installation steps 88 condition code checking 148 conversion notes on files 261 overview 259 Cover letter 84
CPM 136 Critical Path Monitor (CPM) 108 cross node query, NJE 194 cross-platform scheduling connecting systems 279 global variables 236 IMODs 235 implementing 232 CSV003I 98 customization job, STAGE1 112
D
DASD requirements 6 3390 11 disk space for CA-Datacom/AD 11 space requirements 11 data sets allocated by STAGE2 job stream 120 allocating 120 placement considerations 46 recommended initial sizes 124 database ID 137 DBID option 137 forecasts 144 system tables 155 date format 186 date library 22 DB2 binding plans for CA-JCLTrac 228 creating objects for CA-JCLTrac 226 granting authority for CA-JCLTrac 229 setup for CA-JCLTrac 218 DBMUFPR 95, 98 DBRIMPR 31 DBUTLTY 96, 97, 98 INIT/LOAD databases 95 Reset HSD 96 DDCFBLD 96 DDDEF, defining 103 DDNAME statement 224 Demonstration phase 98 dependencies, types of 3 disaster recovery 49 distribution libraries, creating 103 documentation libraries 22 documentation, unloading 102 domain, default 140 Downloading installation libraries from tape 91
DSNAME statement DYNAMLOC 176
223
H
hardware requirements 24 history data 12, 123 holiday action time 189 hot backup 47
E
editing SAMPJCL REXX Execs 38 email domain, default 140 from address 142 library 22, 121 mail server address 143 notification 192 END statement 225 ending Unicenter CA-Jobtrac 253 environmental dependency maximum running time 194 number of retries 194 retry interval 190 eTrust CA-Examine interface 106 Event Alert Reporting 149 Event Console nodenames to receive messages 141 reporting late conditions 141 routing messages 245 sending WTOs 142 Examples allocating SAMPJCL library 90 Executing sample programs 98 execution dependencies, definition of 3 exits, setting up 172
I
IEACMDxx, modifying 252 IEAVMXIT, setting up 208 IEFBR14 89, 94 IMOD, global termination 190 IMODs CA-GSS server 235 INIT IMOD 177 Initializing CXX, LXX and databases 95 initializing internals 252 initiation IMODs 176 installation common steps 8892 allocating SAMPJCL library 89 downloading CA-Datacom/AD libraries 91 linking INIT programs 92 loading CA-Datacom/AD SVC 92 preparing CA-Datacom/AD custom assemblies 92 renaming SMP/E DDEFs 91 demonstration execute CA-Datacom/AD programs 98 execute dynamic SQL programs 98 shut down Multi-User Facility 98 start up Multi-User Facility 98 steps 98 new 85, 9397 adding PROC members 94 allocating CA-Datacom/AD data sets 94 allocating/loading CXX, LXX, databases 95 backing up databases 96 remove unneeded files 97 Reset HSD 96 shut down Multi-User Facility 97 starting Multi-User Facility 95 post-install considerations Multi-User Facility as started task 100 Multi-User Facility tuning 100 setting up production jobs 99 sequence New Installation Phase 87 Post Installation Phase 87 SMP/E Installation Phase 87
F
forecast database 13 forecast database ID 144 forward recovery 50 fuzzy backup 47
G
global JCL variables library 22 global options in JOBTRAnn 127 setting using ISPF interface 184 global termination IMOD 190 global variables 236 GoalNet 169
Index 285
installation (continued) sequence (continued) Verification Phase 87 SVC 31 verification phase steps 98 installation job stream, STAGE2 118 installation verification procedure 254 installing Unicenter CA-Jobtrac 1 internals, initializing 252 IPL prompt field 186 IPLTABLE @AMRGEN statements 209 creating 209 maintaining 205 procedure 213 syntax rules 213 table 205 ISERVE starting procedure 194 subsystem name 190 ISPF main menu, adding Unicenter CA-Jobtrac to NJE considerations 276 using to set global options 184 IVP (Installation Verification Procedure) 254
job priority 148 JOBTRAC task, security authorization required for 56 JOBTRAnn description of options 129 setting options 127 using multiple 128
K
key, LMP 105 KEYS DD statement 105
L
libraries 22 allocating 89 libraries for CA-Datacom/AD products 40 Library Definitions panel 199 library or PDS management 119 linking AllFusion CA-Librarian modules 107 AllFusion CA-Panvalet modules 107 Linking INIT programs 92 LMP key 105 Loading CXX, LXX and databases 95 Loading CA-Datacom/AD SVC 92 location IDs 000 8 assigning 9 default 9 description 8 locations, understanding 8 log file (CA-Datacom/AD) 48 LXX 48
183
J
JCL enabling automatic checking 219 enabling checking 219 sample for loading JCLDOC 101 JCL Editing 36 JCL libraries 22, 119 JCL requirements 40 JCLDOC library description of 101 loading from the product tape 101 sample JCL for loading 101 JCLTCTL table 205 JES cycling 42 interaction 42 JES command character 188 JES held job class, defining 175 JES SYSOUT class 175 JMF PDS 200 job class, defining 175 job classes 193
M
mail server address 143 memory requirements 6, 25 messages and Event Console 245 messages, deletable 187 mirroring 51 modules, converting to tables 206 MUF keyword 162 multi-CPUs and primary Unicenter CA-Jobtrac system 192 Multi-User Facility 83, 122 new installation 95 sharing 16
Multi-User Facility (continued) shutting down 98 started task (running as) 100 starting up 96, 98 tuning 100 multiple copies of Unicenter CA-Jobtrac
122, 268
N
Naming conventions for SAMPJCL members 86 New installation phase 9397 NJE cross node query limit 194 node token, specifying 190 support 190, 271
O
options in JOBTRAnn Overview new install 93 127
remote (continued) password location entity 9 scheduling 232 Remove unneeded files 97 Renaming SMP/E DDEFs 91 reporting with Unicenter Service Desk 143, 149 requirements hardware 24 software 24 restart support 187 reverse conversion 264 REXX Execs 38 REXX IMOD, maximum running time 194 ROOT user ID 153 routing messages to Event Console 245 RUN command 148 running multiple copies of Unicenter CA-Jobtrac 268
S
S910 36 SAMPJCL allocating 89 member names 86 PDS sample 90 scheduling dependencies 3 SCL libraries 22 security 56 setting job priority 148 shadow MUF 21 shared database 162 Shut down Multi-User Facility demonstration phase 98 installation step 97 SMF records, suppressing writing of 171 SMFPRMxx customizing 171 example 173 SMP/E ACCEPT processing 105 APPLY processing 104 considerations 45 distribution libraries, creating 103 installing with 81 linking AllFusion CA-Librarian modules 107 linking AllFusion CA-Panvalet modules 107 RECEIVE processing 104 target libraries, creating 103
P
password requirement rules 241 PDFs 102 PDS for command set scheduling 200 PDS for JMF 200 PDS member 105 PDS or library management 119 pre-installation considerations 24 preinstallation considerations 36 Preparing CA-Datacom/AD custom assemblies primary Unicenter CA-Jobtrac 192, 193 print class archive 187 priority for jobs 148 procedure libraries, updating 126 proclibs, updating 126 Product Information Packets (PIPs) 84 product tape 104 Production jobs setting up 99 products installed 39 purging records 126
92
R
RECEIVE processing 104 REINIT keyword (CAIRIM install of SVC) remote password library 22 33
Index 287
software requirements 24 SPACE command 214 spill 47 STAGE1 customization job 112 STAGE2 installation job stream 118 Start up Multi-User Facility 96, 98 Started task (Multi-User Facility) starting Unicenter CA-Jobtrac 253 static backup 48 statistic records 153 Steps for SMP/E phase 88 SUBROOT keyword 153 subsystems 41 Subsystems (MVS) 36 Supervisor call (SVC) 33, 36 SUSPEND and RESUME commands 21 sysout capture defining classes for 195 enabling 188 line limit specification 193 requeue to another product 197 size specification 113 Unicenter CA-View interface for 230 unit specification 113 volser specification 113 sysout capture file creation of 120 data set placement considerations 46 determining size, general 123 messages associated with 123 setting up 123 Sysout Capture Options panel 195 sysout print class 188 system options, installation considerations
TRACMAC parameters optional 116 required 113 TRACMnnn 22 TRACRnnn 22 TSO 30 TSO procedures updating 180
U
UCT keyword, use of 221 UCT setup for CA-JCLTrac 218 Unicenter CA-11 and CA-Datacom/AD 52 high-level index 116 INSERTRMS option 145 interface 215 RERUN option 150 Unicenter CA-MIM 53 Unicenter CA-View 54, 230 Unicenter Service Desk 143, 149 Unicenter Service Desk reporting 192 UNIX 279 unloading documentation 102 updating LMP key 105 Upgrades existing products 85 upgrading 259 user control table CLASS statement 222 creating 221 DDNAME statement 224 DSNAME statement 223 END statement 225 example 225 explained 220 for CA-JCLTrac 205 setup for CA-JCLTrac 218 using 221
55
T
tables 205 target libraries, creating 103 TASKS keyword 163 TCP/IP 232, 280 templates, email 22, 121 temporary-use JCL libraries 22 termination IMOD 190 token 167, 272 TRACAUTH table assembling 205 converting 262 description 174
V
Verification phase 98 ViewPoint 30 VINITx procedure 252
W
Worksheet 84
WTOs using Event Console
142
X
XCF connections 162 XCFFROM keyword 163 XPLATRERUN option 159
Index 289

R0JOBT11PIE

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

R0JOBT11PIE

Uploaded by

Copyright:

Available Formats

Unicenter CA-Jobtrac Job Management

Planning and Implementation Guide for CA-Datacom/AD r11

vi Planning and Implementation Guide

viii Planning and Implementation Guide

x Planning and Implementation Guide

276 277 278 278 279 280 281 283

xii Planning and Implementation Guide

2 Planning and Implementation Guide

Features and Benefits

Features and Benefits

Production Scheduling Features

Features and Benefits

Unicenter Service Desk

4 Planning and Implementation Guide

Features and Benefits

Automatic Message Recognition

System Command Scheduling

Specifying Additional Condition Codes

Features and Benefits

6 Planning and Implementation Guide

Chapter 2. Overview of Components and Installation

Chapter 2. Overview of Components and Installation 7

8 Planning and Implementation Guide

Chapter 2. Overview of Components and Installation 9

10 Planning and Implementation Guide

Chapter 2. Overview of Components and Installation 11

Unicenter CA-Jobtrac DASD

Options and tables

History information Event staging

12 Planning and Implementation Guide

Event data Options and tables

History information Event staging

Capture File Data Set

Chapter 2. Overview of Components and Installation 13

Calculate Database Size

14 Planning and Implementation Guide

Differentiate Copies of Unicenter CA-Jobtrac

Chapter 2. Overview of Components and Installation 15

CA-Datacom/AD Sharing Overview

Database Access Options

16 Planning and Implementation Guide

Chapter 2. Overview of Components and Installation 17

18 Planning and Implementation Guide

Chapter 2. Overview of Components and Installation 19

20 Planning and Implementation Guide

Chapter 2. Overview of Components and Installation 21

TRACDnnn (TRACD000 is the default.)

TRACSnnn (TRACS000 is the default.)

22 Planning and Implementation Guide

Type Temporary-use JCL

DD Naming Convention TRACTnnn (TRACT000 is the default.)

Chapter 2. Overview of Components and Installation 23

24 Planning and Implementation Guide

Unicenter CA-Jobtrac has one FMID. It is CHDB000.

Chapter 2. Overview of Components and Installation 25

26 Planning and Implementation Guide

Chapter 2. Overview of Components and Installation 27

28 Planning and Implementation Guide

Note: CA-Datacom/AD requires CAISSF.

Chapter 2. Overview of Components and Installation 29

CAISDI/els - Service Desk Integration

Note: CA-Datacom/AD requires CAIVPE.

30 Planning and Implementation Guide