Ca7 Installation Guide 1

CA Scheduler Job Management
Installation Guide
r11
This documentation and any related computer software help programs (hereinafter referred to as the Documentation) is for the end users informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or 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 users responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION AS IS WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE. The use of any product referenced in the Documentation is governed by the end users applicable license agreement. The manufacturer of this Documentation is CA. Provided with Restricted Rights. Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.2277014(b)(3), as applicable, or their successors. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies. Copyright
2007 CA. All rights reserved.
Contact Technical Support

For online technical assistance and a list of locations, primary service hours, and telephone numbers, contact Technical Support at http://ca.com/support.
Contents
Chapter 1: Overview of Components and Installation
Components/Concepts ........................................................................ 1-1 Started Task.............................................................................. 1-1 CA Datacom/AD .......................................................................... 1-2 CAIENF .................................................................................. 1-2 CAICCI ................................................................................... 1-2 XCF ...................................................................................... 1-3 Pre-Installation Considerations ................................................................ 1-3 Operating Environments ................................................................... 1-3 SVC Requirements ........................................................................ 1-3 Hardware Requirements ................................................................... 1-3 CA Common Services ..................................................................... 1-6 Compatibility with Other Products .......................................................... 1-9 Defining VTAM APPLID (NJE Only)......................................................... 1-14 What's Next? ................................................................................ 1-15
Chapter 2: Installation Steps

Step 1: Install CA Common Services ........................................................... 2-1 Step 2: Install CA Datacom/AD ................................................................ 2-1 Step 3: Update CA Datacom/AD Options ....................................................... 2-2 Tasks .................................................................................... 2-2 Other TASKS Settings ..................................................................... 2-3 LXX ...................................................................................... 2-4 FXX ...................................................................................... 2-4 Logging .................................................................................. 2-4 Messages ................................................................................ 2-4 Access ................................................................................... 2-4 Step 4: Install CA JCLCheck Common Component .............................................. 2-5 Step 5: Load SAMPJCL ........................................................................ 2-5 Step 6: Tailor SAMPJCL Members .............................................................. 2-6 Step 7: Create SMP Data Sets ................................................................. 2-7 Step 8: Initialize SMP ......................................................................... 2-7 Step 9: Define SMP DDDEFs ................................................................... 2-8 Step 10: Receive CA Scheduler ................................................................ 2-8 Step 11: Apply CA Scheduler .................................................................. 2-9
Contents
Step 12: Accept CA Scheduler ................................................................ 2-9 Step 13: Load Acrobat (PDF) Files ............................................................ 2-10 Step 13A: Load Acrobat (PDF) Files from a ZIP File ........................................ 2-10 Step 13B: Load Acrobat (PDF) Files from a TGZ File ....................................... 2-11 Step 14: Assemble CICS Routines ............................................................ 2-12 Step 15: Link Edit CICS Routines ............................................................. 2-12 Step 16: Tailor Procedures................................................................... 2-13 Step 17: Start CA Datacom/AD .............................................................. 2-13 Step 18: Define CA Datacom/AD Tables ...................................................... 2-14 Step 19: Update CA Datacom/AD Tables ...................................................... 2-15 Step 20: Update CA Datacom/AD Tables ...................................................... 2-17 Step 21: Update System Libraries ............................................................ 2-18 Step 22: Update CAIRIM Parameters ......................................................... 2-19 Step 23: Update License Management Program (CA LMP) Key.................................. 2-20 Step 24: CAIENF Database .................................................................. 2-20 Step 25: CAIENF Startup Options ............................................................ 2-21 Step 26: Start CAIENF....................................................................... 2-21 Step 27: Tailor CICS Options ................................................................ 2-22 Step 28: Initialize CICS Work Files ........................................................... 2-22 Step 29: Install CA Scheduler Dialog ......................................................... 2-23 Step 30: Convert CA Scheduler Data ......................................................... 2-23 Step 31: Define User IDs and Date Tables .................................................... 2-24 Step 32: Define Demo Job Streams .......................................................... 2-24 Details of the First Step .................................................................. 2-24 DEMOHIST .............................................................................. 2-25 DEMOTRCK ............................................................................. 2-26 DEMORPTS ............................................................................. 2-27 The Resource Record .................................................................... 2-28 Step 33: Start and Test CA Scheduler ........................................................ 2-28 Step 34: Define/Update Cleanup Job ......................................................... 2-29 Step 35: Automatic Startup .................................................................. 2-30 Step 36: Save All Output .................................................................... 2-30 Step 37: Upgrade History .................................................................... 2-31
Appendix A: Releases 7.4 /8.0 Conversion to r11

Conversion Steps ............................................................................ A-1 Conversion Messages ......................................................................... A-3 Changing System IDs ........................................................................ A-4
vi
Getting Started
Appendix B: Reversion Steps Index
Contents
vii

The following topics introduce the key components of CA Scheduler and discuss some pre-installation considerations.
Components/Concepts
The following topics introduce important components and concepts.
Started Task
The CA Scheduler started task, sometimes called the monitor, is where all of the decision making and work is performed. The started task has several functions, such as: Scanning your workload definitions once a day in a process called autoscan to look for work that will execute in the next 24 hours. All such work is copied to the active workload for processing. Submitting jobs whose requirements have been met. Requirements can include time of day, successful completion of other jobs, and the availability of virtual resources. Tracking jobs that are executing. CA Scheduler displays the current status of each job (started, complete, abended, and so on) along with the JES number and return code (if appropriate). Processing commands. CA Scheduler accepts commands from a variety of sources, including the console (modify commands), TSO sessions, batch jobs (CAJUCMD0 utility), and REXX programs (address CASCHD). Generating emails based on your CA Scheduler email definitions. Opening requests in CA Unicenter Service Desk for failed jobs or conditions within CA Scheduler (such as the database getting full or more than a certain number of jobs in abended status). The started task must run on every system where z/OS jobs are going to execute.
11
Components/Concepts
CA Datacom/AD
CA Scheduler uses CA Datacom/AD as its database. CA Datacom/AD is an incredibly fast database engine that allows for forward recovery, data integrity after a system outage, backup-while-open, and more. If you have the separately licensed product CA Datacom/DB, you can use it for CA Scheduler, but we recommend that you do not have CA Scheduler use the same CA Datacom/DB MUF (multi-user facility) as your applications. The addition of the CA Scheduler workload to your existing application MUF may negatively impact the performance of your existing applications. We recommend that you use the no license fee copy of CA Datacom/AD that is included with CA Scheduler. CA Datacom/AD is identical in every way to 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 CA Datacom/DB are the same. To avoid confusion, all references in the guides are to CA Datacom/AD.
CAIENF
The Event Notification Facility, also called CAIENF, is a component of the CA Common Services. CAIENF monitors the operating system for jobs starting, ending, and a variety of other events. Each event is passed to CA Scheduler and other CA products. Using CAIENF allows one set of operating system intercepts to provide data to multiple CA products, instead of each product needing to have and maintain its own set of intercepts. CAIENF must run on every system where z/OS jobs are going to execute.
CAICCI
The Common Communication Interface, also called CAICCI, is a component of the CA Common Services. CAICCI provides a simple method for CA products to communicate with each other. CA Scheduler uses CAICCI to communicate with other CA scheduling products on other platforms (cross-platform), and with Critical Path Monitoring (CPM), among other uses. Because of the many current and future uses of CAICCI, it is required for CA Scheduler.
12
Installation Guide
Pre-Installation Considerations
XCF
CA Scheduler uses IBMs communication facility XCF. XCF is included as part of the base operating system and does not require any additional hardware. XCF is used when processing tracking commands and for communicating between copies of CA Scheduler in a multiple-CPU (JES MAS) environment.
The following topics discuss pre-installation considerations.
Operating Environments
CA Scheduler supports any version of z/OS supported by IBM.
SVC Requirements
CA Scheduler r11 uses an SVC. The default SVC number is 180, which is an unused SVC. SVC numbers 200-255 can be used instead of 180 if preferred. CA Scheduler r11 cannot share its SVC with earlier releases. You can run multiple releases of CA Scheduler on a given system at the same time by using a different SVC number for CA Scheduler r11 from the SVC number used for CA Scheduler Release 9.x.
Hardware Requirements
The following topics define the disk space requirements for the target and distribution libraries, the CICS temporary storage requirements, and the CA Scheduler-specific CICS file requirements, and storage requirements for components.
13
Disk Space Estimates for Target Libraries

The following table estimates disk space for the target libraries required to install CA Scheduler. Since these estimates include common components, less space may be required if some of these components have already been installed. Space Directory (BLK) Block 1000 7550 30 100 10 25 50 2000 350 50 100 1200 50 250 10 50 35 35 35 10 25 50 100 50 10 50 200 35 50 10
DDname CAICICS CAICLS0 CAIDRIVR CAIEARL CAIEMAIL CAIEVENT CAIJCL CAILOAD CAIMAC CAIMSG0 CAIOPTN CAIPNL0 CAIPROC CAISRC CAITBL0
Description CA Scheduler CICS LOADLIB CA Scheduler CLISTs CA Scheduler Driver procs CA Scheduler EARLLIB CA Scheduler email templates CA Scheduler templates for CAISDI/els (CA Unicenter Service Desk) CA Scheduler sample job streams CA Scheduler LOADLIB CA Scheduler MACLIB CA Scheduler messages CA Scheduler control cards, options CA Scheduler panels CA Scheduler procedures CA Scheduler SOURCE CA Scheduler tables
Block Size LRECL 6144 3120 3120 3120 3120 3120 3120 6144 3120 3120 3120 3120 3120 3120 3120 -80 80 80 80 80 80 -80 80 80 80 80 80 80
Note: CAILOAD is intentionally allocated without any secondary extents so that it will not be extended when maintenance is applied. New extents can cause errors for the CA Scheduler started task or CA Scheduler users who are active at the time of the new extent. CAILOAD is allocated with extra space, and SMP will automatically compress the data set should it become full while maintenance is being applied.
14
Installation Guide
Disk Space Estimates for Distribution Libraries

The following table estimates disk space for the distribution libraries needed to install CA Scheduler. Space (BLK) 50 50 250 400 120 1400 50 100 200 10 Directory Block 50 50 100 150 50 250 15 50 35 10
DDname ACHCLIST ACHDATA ACHLOAD ACHMAC ACHMSG ACHPNL ACHPROC ACHSAMP ACHSRC ACHTBL
Description CA Scheduler clists CA Scheduler control cards, options CA Scheduler object modules CA Scheduler macros CA Scheduler messages CA Scheduler panels CA Scheduler procedures CA Scheduler samples CA Scheduler source code CA Scheduler tables
Block Size LRECL 3120 3120 32760 3120 3120 3120 3120 3120 3120 3120 80 80 -80 80 80 80 80 80 80
CICS Temporary Storage

CA Scheduler uses two to three tracks of DFHTEMP space per CICS user. Make sure that there is sufficient space in the DFHTEMP data set. The DFHTEMP data set record size should be at least 4086 bytes.
CA Scheduler-specific CICS Files

The CA Scheduler CICS transactions use two VSAM files. The files should have roughly one cylinder of data space for each CICS user accessing CA Scheduler.
15
Storage Requirements
The storage requirements for the different components are as follows: System Component Region size for CA Scheduler Extended Common Storage Area (ECSA) Region size for TSO/ISPF user Size Required/Used (Approximate) At least 6 MB 25 KB shared by all copies of CA Scheduler r11, <1 KB for each copy of CA Scheduler running At least 4 MB, 6 MB recommended
CA Common Services
CA Scheduler requires the following services from the CA Common Services tape: CAIRIM (includes CA LMP) CA-SRAM CAIENF CAICCI CA Scheduler may optionally require these common services if certain options or add-on components are used: CA Earl CAISSF CA-XPS Note: CA Datacom requires the following additional CA Common Services: CA C Runtime CAIVPE If other CA products are installed at your site, some or all of these services may already be installed. The CA Common Services components required by CA Scheduler are described in the following topics.
16
Installation Guide
CAIRIM and CA LMP

CAIRIM, sometimes called CAS9, is the CA Resource Initialization Manager. CA Scheduler uses CAIRIM to build and manage the CA Scheduler environment, including the subsystem SSCT, common modules loaded into ECSA, and CA Scheduler installation and security options. For more information about initialization, see the Systems Programmer Guide. CA LMP is the CA License Management Program. At various points in the CA Scheduler processing, such as autoscan, a CA LMP check is performed to see if CA Scheduler is currently licensed on your processor. If not, a highlighted message is issued periodically to the console. CA Scheduler requires CAIRIM and CA LMP.
CA-SRAM
CA-SRAM is a set of sort routines used by various CA Scheduler report functions. CA-SRAM attempts to perform all sort operations in storage, only using DASD work files when large amounts of data are being sorted. CA Scheduler requires CA-SRAM.
CAIENF
CAIENF is the CA Event Identification Facility. CAIENF monitors the system for events of interest to CA Scheduler such as jobs starting and ending, steps ending, and data sets being updated. Each event is communicated to CA Scheduler allowing CA Scheduler to track jobs. Using CAIENF allows CA Scheduler to be independent of changes in SMF exits or other IBM facilities. CAIENF can record events to its database. If a recorded event occurs while CA Scheduler is not active, it is passed to CA Scheduler once it is started. CA Scheduler requires CAIENF.
CAICCI
CAICCI is the CA Common Communication Interface. CAICCI supports communication between CA Scheduler and other CA job management solutions. CA Scheduler requires CAICCI.
17
CA Earl
CA Earl is the CA Easy Access Report Language. CA Earl can be used to create reports on the data in the CA Scheduler database or active workload. Several canned reports are provided and can be tailored to site-specific needs. New reports can also be created. For more information, see the Report Reference Guide. CA Scheduler requires CA Earl if CA Scheduler/CA Earl reports are used.
CAISSF
CAISSF is the CA Standard Security Facility. CAISSF is used to validate a user's authority to issue a specific command or to associate a user ID with a job being submitted. CA Scheduler interfaces with CA ACF2, CA Top Secret, and IBM's RACF. For more information about external security, see the Interface Reference Guide. CA Scheduler requires CAISSF if you are using external security.
CA-XPS
CA-XPS is the Cross Platform Scheduling router. It is used when Unicenter NSM or CA AutoSys requests a job to be executed on z/OS. Requests are sent from the requestor to CA-XPS, which then forwards the requests to a specific scheduling product. CA-XPS allows multiple copies of CA Scheduler (or CA 7 or CA Jobtrac) to participate in cross-platform scheduling on the same z/OS image.
18
Installation Guide
Compatibility with Other Products

CA Scheduler is compatible with other software products including the following: CA ACF2 CA APCDDS Automated Report Balancing CA Dispatch CA Earl CA JCLCheck Utility CA Librarian for JCL master file CA Netman CA Opera CA OPS/MVS Event Management and Automation CA Panvalet for JCL master file CA Roscoe Interactive Environment CA Top Secret CA Unicenter Service Desk CA 11 Workload Automation Restart and Tracking CA-JobDoc for JCL master file CICS ISPF/PDF RACF TSO User database for JCL master file
Compatibility with Other Releases of CA Scheduler

All release numbers in this discussion refer to previous or current releases of CA Scheduler. r11 is a complete replacement of all earlier releases. r11 can communicate with Releases 7.4, 8.0, 9.0, or 9.1 running on another JES node. Multiple copies of CA Scheduler can run on the same z/OS image. r11 can share the z/OS image with Releases 7.4, 8.0, 9.0, or 9.1. If r11 is installed into an SMP CSI that contains an earlier release of CA Scheduler, SMP deletes the earlier release.
19
A single logical copy of CA Scheduler includes all of the started tasks running for that copy. For example, in a 3 LPAR JES MAS, a total of 3 started tasks (one on each LPAR) are executed for one logical copy of CA Scheduler. All of the started tasks for each logical copy of CA Scheduler must run the same release.
Compatibility with CA Datacom/AD

CA Scheduler requires CA Datacom/AD r11 SP2 or later. CA Scheduler can share a CA Datacom/AD Multi-User Facility (MUF) with other applications or can have its own MUF. We recommend that CA Scheduler has its own MUF for the following reasons: CA Scheduler is a systems product that must be available 24x7. Other applications may require the MUF shut down at times, which would make CA Scheduler unusable. CA Scheduler may impact performance on your existing CA Datacom/AD (or CA Datacom/DB) applications. We recommend that sites with the full CA Datacom/DB product install CA Datacom/AD for use with CA Scheduler.
JES Exit Installation Requirements

These exits are optional, and are only required if the NJE feature is used. The NJE feature provides for cross-node scheduling capabilities by having two copies of CA Scheduler communicate through VTAM (see the NJE processing in the Systems Programmer Guide for more information): JES2 Exit 4 and/or 54 JES3 Exit 33 Related installation steps are Apply CA Scheduler and Update System Libraries. Also review Defining VTAM APPLID (NJE Only) in this chapter. The CA Scheduler load library (CAILOAD) must be in the system link list when the NJE feature is used. Regardless of the JES exits used and the functions they perform, the installation process differs mainly in the JES system interface (JES2 or JES3) to be installed. The remainder of this section discusses the installation procedures for the two JES systems. Be sure to review the section for the JES system that applies to your environment.
110
Installation Guide
JES2
JES2 at z/OS 1.7 and above supports NJE over either SNA or TCP/IP. Sites can use either or both methods for communication between JES2 nodes. CA Scheduler requires JES2 exit 4 when using NJE over SNA and requires JES2 exit 54 when using NJE over TCP/IP. Either or both exits can be installed. The exit 4 load module is J2CHNJE4. The exit 54 load module is J2CHNJ54. To apply JES2 exits to your target CAILOAD, see installation step Apply CA Scheduler and select CCHB0J2 SYSMOD. Be sure to include, in the SMP procedure, the JES2 macro library that is appropriate for your current JES2 version in the SYSLIB data set concatenation. In addition, include in the SYSLIB data set concatenation, before the JES2 macro library in the search order, the appropriate JES2 SMPMTS data set, which contains the correct version of JES2 macros for your system. This is applicable if the JES2 version or maintenance level you are currently running has not yet been accepted by SMP. If your JES2 version is changed, you only need to use SAMPJCL member CHJES2 with the new JES2 macro library. The JES2 exit J2CHNJE4 and the interface program CAJMJES2 are compatible with any JES2 version. JES2 exit J2CHNJ54 is compatible with JES2 at or above z/OS 1.7, and assembles to a short stub program at releases prior to z/OS 1.7. The programs are automatically assembled to the correct level based on the SYSLIB concatenation. When installing for multiple CPUs that have different versions of JES2, you need to use a separate load library for each version to store J2CHNJE4, J2CHNJ54, and CAJMJES2 modules. You can use the APPLY REDO in SAMPJCL member CHJES2 with the appropriate JES2 library to properly link edit to the desired library. To enable the CA Scheduler JES2 exit, add the following JES2 initialization statements to a data set member defined by the HASPPARM DD statement in the JES2 startup procedure:
/* EXIT 4 FOR NJE VIA SNA */ LOADMOD(J2CHNJE4) EXIT004 ROUTINE=CAJ2X4CH,ENABLE /* EXIT 54 FOR NJE VIA TCP/IP */ LOADMOD(J2CHNJ54) EXIT054 ROUTINE=CAJ254CH,ENABLE
If other exits are already installed, add the CA Scheduler exit to the list inside parentheses, as in the following:
EXIT004 ROUTINE=(YOUREXIT,CAJ2X4CH),ENABLE
111
JES2 requires that exit 54 be loaded in CSA. You can either copy load module J2CHNJ54 to an LPA library or create a SYS1.PARMLIB(PROGxx) member to load J2CHNJ54 dynamically into the LPA at IPL time. The PROGxx member might look like this:
LPA ADD MODNAME(J2CHNJ54) DSNAME(LNKLST)
If the PROGxx member is named PROG54, you can issue the system command T PROG=54 before the start of JES2 to load the exit into LPA. We recommend that you enable the CA Scheduler JES2 exit just before the installation step to IPL the system (see installation step Update System Libraries). The JES2 exits must be installed on every system where CA Scheduler-submitted NJE jobs will be executed.
JES3
You must decide before proceeding if you are going to use the JES3 exit driver routine provided by CA Scheduler or some other exit driver that you are already using. We recommend that you use the CA Scheduler JES3 exit driver unless you are intimately familiar with an existing driver that you already have installed. If you are using the default IBM-supplied JES3 exits, use the following instructions. Install JES3 Exits Using the CA Scheduler Driver Important! Proceed with this section only if you have decided to use the JES3 exit driver routines provided by CA Scheduler. You must identify all of your JES3 exit routines that are to be invoked by the CA Scheduler exit drivers. The exits must all have unique CSECT names and entry points. In addition, any existing exits that use entry point IATUX33 (for JES3 exit 33) need to be changed to a different name. If you have no additional JES3 exit routines, skip to Install JES3 Exits to System Library.
112
Installation Guide
After completing installation Step 11, use SAMPJCL member CHJ33 to tailor the CA Scheduler-provided IATUX33. Copy IATUX33 from CAISRC to another library, and then use the comments in IATUX33 to specify which exits should be called. Once updated, submit CHJ33. The job should end with a return code of zero or four. To generate the exits for a different version of JES3, use SAMPJCL job CHJES3 with the SYSLIB pointing to the JES3 macro library for the new version. Install JES3 Exits to System Library You need to install the JES3 exits to your system library to: Include your existing JES3 exits. Make the new JES3 exits available at execution time. Be sure to edit the sample JCL to include the correct IBM SMP procedure, zone names, module names, and load libraries. If you are using the default IBMsupplied JES3 exits only, you do not need to include these exits in the linkedit. The job should end with a zero return code. Install JES3 Exits Using Existing Driver Important! Proceed with this section only if you have decided to use an existing JES3 exit driver routine and not one that is provided with CA Scheduler. To apply the JES3 exits to your target CAILOAD, see installation step Apply CA Scheduler, and select CCHB0J3 SYSMOD. Be sure to include, in the SMP procedure, the JES3 macro library that is appropriate for your current JES3 version in the SYSLIB data set concatenation. In addition, include in the SYSLIB data set concatenation, before JES3 in the search order, the appropriate JES3 SMPMTS data set, which contains the correct version of JES3 macros for your system. This is applicable if the JES3 version or maintenance level that you are running currently has not yet been accepted by SMP. To generate the exits for a different version of JES3, use SAMPJCL job CHJES3 with the SYSLIB pointing to the JES3 macro library for the new version. Modify your existing JES3 exit driver to invoke the CA Scheduler JES3 exits. This may require a change to the source code and a reassembly and a link-edit of your existing driver module. The following linkage editor control statements are required to include the optional CA Scheduler JES3 exit 33 CSECTs for the NJE feature:
INCLUDE CAILOAD(J33CHNJE) <== CA-Scheduler exit 33 entry point
113
When installing for multiple CPUs, be sure to change the existing JES3 exit 31 and 33 driver modules, for each CPU, to include the correct CA Scheduler routines according to the JES3 version installed on that CPU. A portion of the IATUX33 exit used by CA Scheduler for NJE support runs as a JES3 subtask through a JES3 macro:
IATXCSF ENTR=entrypoint,ID=nnn,BUSY=label
(For more information, see the IBM manuals, JES3 System Programming Library User Modification and JES3 Macros.) The ID=nnn keyword identifies a unique JES3 subtask ID. Subtask IDs 151255 are reserved for clients. The CA Scheduler IATUX33 exit routine uses JES3 subtask ID 151. If you have your own, or other vendor software JES3 exits or modifications that use the same subtask ID 151 for long term processing, you may need to change one of the exits, using a different subtask ID. The following statement is to be changed:
IATXCSF ENTR=CALLJX,ID=151,BUSY=WAITOFF
Defining VTAM APPLID (NJE Only)

A VTAM connection is required between the CA Scheduler(s) on the JES node where jobs are submitted and the CA Scheduler(s) on the JES node where jobs execute. Feedback information, such as jobs starting and ending, will be sent from the CA Scheduler where the job executes back to the CA Scheduler that submitted the job. The VTAM connection is required even if you are using JES2 NJE over TCP/IP.
Local Definition
Add the following VTAM initialization statements to a member pointed to by member ATCCONxx in the data set pointed to by ddname VTAMLST in the VTAM startup procedure (see the IBM manual VTAM Installation and Resource Definition):
applnode VBUILD TYPE=APPL schdapl1 APPL EAS=nn, number of est'd concurrent sessions ACBNAME=schdapl1, MODETAB=caijmtab, DLOGMOD=caijlogm
114
Installation Guide
What's Next?
The application ID (SCHDAPL1) must be unique across the network and must be the same as the application ID specified for APPLID coded in the CAIJNJE source member.
Remote Definition
Add the following VTAM initialization statements to a member pointed to by member ATCCONxx in the data set pointed to by ddname VTAMLST in the VTAM startup procedure. For each application ID coded in the CAIJNJE source member, code a member containing a cross-domain resource definition.
applnode VBUILD TYPE=CDRSC schdapl2 CDRSC CDRM=cdrmname,ISTATUS=ACTIVE
Member CAIJMTAB in the CAIOPTN data set contains the source code for the MODETAB definition, which must be assembled and link edited into VTAMs VTAMLIB concatenation. SAMPJCL member CHMODTAB can be used to assemble and link the MODETAB.
What's Next?
This chapter introduced the CA Scheduler components and pre-installation considerations. The next chapter guides you through the installation process.
115

The following topics guide you through the installation process. Save the output of all jobs run for this install. Technical Support may need to see the job output to help resolve any problems you might have.
Step 1: Install CA Common Services

This step can be skipped if the required components were installed for another CA product. CA Scheduler requires several common components from the CA Common Services tape. For a list of the components required, see the topic CA Common Services in the previous chapter. Using the CA Common Services Getting Started guide (available at http://ca.com/support), install and configure the required components.
Step 2: Install CA Datacom/AD

CA Scheduler uses CA Datacom/AD for its database. CA Datacom/AD is a no-charge version of the CA database product CA Datacom/DB. CA Datacom/AD has all of the functions of the full CA Datacom/DB product, with the exception that CA Datacom/AD does not allow the use of user-defined databases. We encourage sites that have the full CA Datacom/DB r11 SP2 or later to install CA Datacom/AD r11 SP2 or later for CA Scheduler. We strongly recommend that you do not add the CA Scheduler workload to your existing full CA Datacom/DB environment for the following reasons: Adding the CA Scheduler workload may adversely impact the performance of your existing CA Datacom/DB applications. Installing CA Scheduler into a separate CA Datacom environment removes the possibility of a database definition collision (your application and CA Scheduler trying to use the same database ID). CA Scheduler must be available 24x7, so the CA Datacom it uses must also be up 24x7. Your existing CA Datacom/DB may be scheduled to come down periodically for maintenance.
21
Step 3: Update CA Datacom/AD Options
To install CA Datacom/AD, see the CA Datacom/AD Installation and Maintenance Guide.

This step is required for all sites. This step updates some CA Datacom/AD options. For details on the specified options, see the CA Datacom/DB Database and System Administrator Guide. The CA Datacom/AD options are normally stored in the CA Datacom/AD CUSMAC library in member DBDATIN2.
Tasks
Each user of CA Scheduler connects to the CA Datacom/AD MUF. The CA Datacom/AD MUF needs a connection for each user. The number of connections is specified as the first parameter on the CA Datacom/AD startup option TASKS. You can safely over allocate the TASKS number. There is no overhead for having too many tasks specified. Increasing the number of tasks later requires restarting CA Scheduler and the CA Datacom/AD MUF. Setting TASKS to 500 should be sufficient for all sites. The following formula can be used to determine the actual number of tasks required: (N*(8 +R))+(N*(S-1)*4)+U where: N is the number of CA Scheduler subsystems. R is the number of internal readers to be used (installation option SUBRDR, default is 5). S is the number of systems (z/OS images). U is the number of concurrent users. For example, a single-CPU shop with a single copy of CA Scheduler and 10 concurrent users would need:
( 1 * ( 8 + 5 ) ) + ( 1 * ( 1 1 ) * 4 ) + 10 = 23
22
Installation Guide
A shop with three z/OS systems running a production and test copy of CA Scheduler and 25 concurrent users would need:
( 2 * ( 8 + 5 ) ) + ( 2 * ( 3 1 ) * 4 ) + 25 = 90
Setting the TASKS to 500 easily satisfies both cases without incurring any additional overhead, and positions your shop for increased usage. Note: The FXX data set must be initialized with greater than or equal to the total number of tasks specified on the TASKS statement.
Other TASKS Settings

The second parameter on the TASKS option must be at least 33 KB. Multi-CPU Set Up If your site has only one z/OS image per JES node, you can skip this section. The CA Datacom/AD MUF runs on a single z/OS image. On other systems in the JES node, XCF is used to access the database. Activating the XCF interface requires changes both to the MUF startup options and to CA Datacom/AD module DBSIDPR. Set the following MUF startup options:
MUF TASKS XCFFROM SCHDMUF x,y,,,z *,CASCHED
where the TASKS statement x value is as determined in the previous section, the y value is at least 33 KB (larger is fine), and the z value is approximately 80% of the x value. A reasonable TASKS statement would be:
TASKS 500,33K,,,400
The source code for DBSIDPR is in the CA Datacom/AD CUSMAC data set. DBSIDPR is used by CA Scheduler to find the CA Datacom/AD MUF. The same DBSIDPR load module should be used on all systems in the JES node. Add the TOMUF and TOGROUP keywords to the DBSIDPR:
DBSYSID SVC=246,SUBID=0,TOMUF=SCHDMUF,TOGROUP=CASCHED
The TOMUF value must batch the MUF startup option, and the TOGROUP value must match the second value on the XCFFROM startup option. Reassemble and link edit DBSIDPR to activate the changes. Note: The "router MUF" required for CA Datacom/AD Release 9.0 to use XCF is no longer required for CA Datacom/AD r10.0.
23
For additional updates that are required for multiple CPU environments, see the multiple CPU operations in the Systems Programmer Guide.
LXX
The LXX data set must have a block size of at least 16384.
FXX
The FXX data set must have the same block size as the LXX and must be initialized with at least as many tasks as are specified on the TASKS statement.
Logging
You may want to review the logging options specified on the LOGMSGE, LOGRCV, and LOGSPILL keywords. Use of the CA Datacom/AD forward recovery feature requires specific types of backups and log options.
Messages
CA Datacom/AD issues message DB00101I every time the database is opened. The message causes the online screens to be cleared every time a user enters the CA Scheduler online screens. To suppress the message, add the following CA Datacom/AD start up option:
MESSAGE NO,DB00101
Access
You may want to review the ACCESS keyword, which controls CA Datacom/AD processing when all CA Scheduler tasks and users have ended. By default, CA Datacom/AD keeps certain control blocks active so that a later CA Scheduler task will start faster. The downside is that a manual CLOSE command must be issued before certain CA Datacom/AD functions (such as a native backup) can be done. The ACCESS keyword can be used to change this behavior. We recommend that you do not use the ACCESS keyword for the CA Scheduler database, but some sites may find its use desirable.
24
Installation Guide
Step 4: Install CA JCLCheck Common Component
Step 4: Install CA JCLCheck Common Component

This step can be skipped if your site has the full CA JCLCheck product or if the CA JCLCheck common component has been installed for another CA product. CA Scheduler expects CA JCLCheck to be at Release 7.0 or later. CA JCLCheck is used to validate JCL when the CA Scheduler SYNCHK command is used. The CA JCLCheck common component is provided at no charge to sites without the full CA JCLCheck product. The CA JCLCheck common component can only be used from another CA product. Use the CA JCLCheck Getting Started to install the CA JCLCheck common component.
Step 5: Load SAMPJCL

This step is required for all sites. This step requires that the installation tape be mounted. Use the following JCL to copy the sample JCL library from the installation tape to DASD. The remainder of the CA Scheduler installation uses these jobs.
//jobname //STEP1 //SYSUT1 // // // // //SYSUT2 // // //SYSUT3 // //SYSUT4 // //SYSIN // JOB ... EXEC PGM=IEBCOPY,REGION=4M SYSOUT=* DISP=(OLD,KEEP), DD
//SYSPRINT DD
UNIT=CART, VOL=SER=CHxxyy, LABEL=(1,SL), DSN=CAI.SAMPJCL DD DISP=(,CATLG), DSN=cai.SAMPJCL,UNIT=SYSDA, SPACE=(3120,(500,200,30)) DD DD DD UNIT=SYSDA, UNIT=SYSDA, * SPACE=(CYL,(5,5)) SPACE=(CYL,(5,5))
COPY INDD=((SYSUT1,R)),OUTDD=SYSUT2
You may need to tailor the JCL for your site's standards. The job should end with a zero return code.
25
Step 6: Tailor SAMPJCL Members
Step 6: Tailor SAMPJCL Members

The SAMPJCL members must be tailored for your shop before they can be executed. The tailoring includes your data set names and DASD volume serials and units to use. You can tailor each SAMPJCL member individually as you need it, or you can use the provided ISPF REXX EXECs to tailor all of the SAMPJCL members at once. Although the REXX EXECs eliminate the requirements for most manual editing of the SAMPJCL members, you should still review the instruction block in each job for additional tailoring that may need to be done. If you intend to tailor each SAMPJCL member as you need it, continue to the next step. To use the REXX EXECs 1. Edit SAMPJCL member $EDITCHG. Follow the instructions to update each ISREDIT C line with the desired value. For example, if you want to change the CA Scheduler high level qualifier from CAI.SCHD to MYQUAL.SCHD you would update the first ISREDIT C line from:
/* CA Scheduler high level qualifier */ /*--+----1----+----2----+----3----+----4----+----5----+----6----+----7*/ 'ISREDIT C "CAI.SCHD" "CAI.SCHD" ALL'
to:
/* CA Scheduler high level qualifier */ /*--+----1----+----2----+----3----+----4----+----5----+----6----+----7*/ 'ISREDIT C "CAI.SCHD" "MYQUALL.SCHD ALL'
Save your changes to SAMPJCL member $EDITCHG. 2. Edit SAMPJCL member $EDITJCL. Find the line that starts with sampjcl =:
sampjcl = 'CAI.SCHD.SAMPJCL'
Change the data set name to the name of the SAMPJCL data set. For example, if your SAMPJCL data set is name MYQUAL.SCHD.SAMPJCL, change the line to:
sampjcl = 'MYQUAL.SCHD.SAMPJCL'
Save your changes to SAMPJCL member $EDITJCL.
26
Installation Guide
Step 7: Create SMP Data Sets
3.
From ISPF option 6, execute $EDITJCL:

Menu List Mode Functions Utilities Help ISPF Command Shell Enter TSO or Workstation commands below: ===> ex 'cai.schd.sampjcl($editjcl)'
4.
The REXX EXEC edits each member in the SAMPJCL data set and makes all of the changes you entered in $EDITCHG.
Step 7: Create SMP Data Sets

This step is required for all sites. We recommend that you install CA Scheduler in its own CSI. SAMPJCL member ISTEP07 contains the JCL needed to create the data sets used by SMP and CA Scheduler throughout the remainder of the installation. CA encourages the use of separate SMP CSI data sets (separate global zones) for each release of each CA product. It is also possible to install multiple CA products into the same CSI. Note: If CA Scheduler r11 is installed into an SMP CSI that contains a previous release of CA Scheduler, SMP deletes the previous release. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a zero return code.
Step 8: Initialize SMP

This step can be skipped if you are installing CA Scheduler into an existing SMP CSI. SAMPJCL member ISTEP08 contains the JCL needed to create the data sets used by SMP throughout the remainder of the installation. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a zero return code in the first three steps, and a return code of zero or four in the fourth step.
27
Step 9: Define SMP DDDEFs
Step 9: Define SMP DDDEFs

This step is required for all sites. SMP has the ability to dynamically allocate all of the data sets it needs. The DDDEF entry identifies the ddname and data set name to use. SAMPJCL member ISTEP09 contains the JCL needed to create or update the DDDEF entries in SMP. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero or four.
Step 10: Receive CA Scheduler

This step is required for all sites. This step requires that the installation tape be mounted. SAMPJCL member ISTEP10 contains the JCL needed to receive CA Scheduler. RECEIVE is the SMP command to copy the installation instructions and elements from the tape to DASD. Before submitting ISTEP10 or any of the subsequent jobs, you need to edit SAMPJCL member FMIDS. Member FMIDS contains the components that make up the CA Scheduler product. You need to delete one or more components from the FMIDS member. The components are the following: CCHB000 CA Scheduler base function, required CCHB0J2 JES2 NJE interface, optional CCHB0J3 JES3 NJE interface, optional The CCHB0J2 or CCHB0J3 functions are only required if you will have CA Scheduler submit jobs on one JES node to execute on another JES node. After editing member FMIDS, follow the directions in the SAMPJCL member ISTEP10 to tailor the job, and then submit it. The job should end with a return code of zero.
28
Installation Guide
Step 11: Apply CA Scheduler
Note: The CA 11 interface is no longer a separate component. The CA 11 interface is included as part of the base product in component CCHB000.
Step 11: Apply CA Scheduler

This step is required for all sites. SAMPJCL member ISTEP11 contains the JCL needed to apply CA Scheduler. APPLY is the SMP command to assemble, link edit, and copy all of the pieces of CA Scheduler into the libraries from which they will be executed. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero. Note: It is important to save the output of this job. Technical Support will frequently want to see the output of the APPLY job when diagnosing problems. The output of all jobs in the install should be saved, but it is particularly important to save the APPLY output.
Step 12: Accept CA Scheduler

This step is required for all sites. SAMPJCL member ISTEP12 contains the JCL needed to accept CA Scheduler. ACCEPT is the SMP command to store all of the individual pieces of CA Scheduler in the distribution libraries. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero or four.
29
Step 13: Load Acrobat (PDF) Files

This step is optional for all sites. This step requires that the installation tape be mounted. CA Scheduler provides Adobe Portable Document Format (PDF) files that can be read by Adobe Acrobat Reader on various distributed platforms. The files must be transferred from z/OS to another platform before they can be read. The PDF files are provided in two formats: a ZIP file and a TGZ file. ZIP files can be processed by many distributed systems, including Windows. Some UNIX platforms cannot process ZIP files and must use the TGZ file. You can load either the ZIP file or the TGZ file (or both), depending on your installations environment.
Step 13A: Load Acrobat (PDF) Files from a ZIP File

Use this step to load the Adobe Acrobat PDF files from a ZIP file. If you need a TGZ file, you should use Step 13B instead of this step. The SAMPJCL job ISTEP13A contains the JCL needed to load the PDF ZIP file. To load PDF files from a ZIP file 1. Follow the directions in the SAMPJCL member to tailor the job, and submit the job. The job should end with a return code of zero. 2. Download the zip file to a platform that supports ZIP and Adobe Acrobat Reader. Use a binary file transfer program such as FTP with the binary option or IND$FILE with no translation. Name the file schdb0.zip. Use a ZIP utility such as WinZip 7.0 or later to uncompress the file. WinZip is available at <http://www.winzip.com>. The directory structure must be kept. Start Adobe Acrobat Reader with search capabilities to open the restored PDF files. You can find Adobe Acrobat Reader at <http://www.adobe.com>.
3.
4.
210
Installation Guide
Step 13B: Load Acrobat (PDF) Files from a TGZ File

Use this step to load the Adobe Acrobat PDF files from a TGZ file. If you need a ZIP file, you should use Step 13A instead of this step. The SAMPJCL job ISTEP13B contains the JCL needed to load the PDF TGZ file. To load PDF files from a TGZ file 1 Follow the directions in the SAMPJCL member to tailor the job, and submit the job. The job should end with return code zero. 2. Move the compressed archive file to a platform that supports Adobe Acrobat Reader. Use a binary file transfer program and download the compressed archive file to the target platform. For example, use FTP with the binary option or IND$FILE with no translation. Name the file SCHDB0.TGZ (on UNIX, schdb0.tar.z). On Windows 9x, use WinZip 7.0 or later to uncompress the file. WinZip is available at <http://www.winzip.com>. On Windows NT/2000/XP, use WinZip 7.0 or later to uncompress the file, or enter the following at a command prompt:
gzip -d schdbo.tgz tar -xvf schdb0.tar
3.
Move the files to a drive and directory of your choice. Note: gzip is a freeware utility available from www.gzip.org. An opensource version of the tar utility for Windows is available from <http://gnuwin32.sourceforge.net/packages/tar.htm>. On UNIX, use the following commands:
uncompress schdb0.tar.z tar xvf schd b0.tar
Move the files to a drive and directory of your choice. On Linux, use the following commands:
uncompress schdb0.tgz tar xvf schdb0.tar
Move the files to a drive and directory of your choice. 4. Start Adobe Acrobat Reader with search capabilities to open the restored PDF files. You can find Adobe Acrobat Reader at <http://www.adobe.com>.
211
Step 14: Assemble CICS Routines
Step 14: Assemble CICS Routines

This step is required if you will be accessing CA Scheduler from CICS. SAMPJCL member ISTEP14 contains JCL to install an SMP USERMOD. The USERMOD assembles and link edits three CICS modules. If you are using RACF and will be using the CA Scheduler external security interface, see the CA Common Services Getting Started topic, Customize CAISSF for RACF or RACF-Compatible Products. You will also need to modify CAJPLTSD and CAJPLTSI (contained in SAMPJCL member ISTEP14) to uncomment the RACF lines. See the comments in those members. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of four or less.
Step 15: Link Edit CICS Routines

This step is required if you will be accessing CA Scheduler from CICS. SAMPJCL member ISTEP15 contains JCL to link edit the CICS stub routines DFHEAI and DFHEAI0 with the CA Scheduler load modules. This is done outside of SMP to prevent ownership conflicts with the CICS stub routines. Note: You should run this job whenever CA Scheduler maintenance is applied or restored, or when the version of CICS is changed. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
212
Installation Guide
Step 16: Tailor Procedures
Step 16: Tailor Procedures

This step is required for all sites. The JCL procedures provided in CAIPROC must be copied to a JES procedure library, such as SYS1.PROCLIB. The procedures are listed in the following table. Make the changes documented in each procedure after it has been copied. Procedure CAICHERL CAJUCMD0 CAJUTIL0 CASCHD Description CA Scheduler CA Earl report driver CA Scheduler tracking command processor CA Scheduler database and report processor CA Scheduler started task
Step 17: Start CA Datacom/AD

This step is required for all sites. If CA Datacom/AD is not already running, start it now. CA Datacom/AD must be active when any CA Scheduler activity is performed.
213
Step 18: Define CA Datacom/AD Tables
Step 18: Define CA Datacom/AD Tables

Important! This step is required for all new installations of CA Scheduler, and for sites converting from CA Scheduler Release 8.0 and earlier. All release numbers in this discussion refer to previous or current releases of CA Scheduler. If you are upgrading from CA Scheduler r9.0 or r9.1, you should skip this step. This step has a series of jobs to define tables and data sets to CA Datacom/AD. To define CA Datacom/AD tables 1. SAMPJCL member ISTEP18A contains JCL to define the CA Scheduler tables to CA Datacom/AD. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero. 2. SAMPJCL member ISTEP18B contains JCL to make the CA Scheduler tables available to CA Datacom/AD. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero. 3. SAMPJCL member ISTEP18C contains JCL to define and initialize the CA Datacom/AD data and index areas for CA Scheduler. These files will hold all of the CA Scheduler data. After the files have been allocated, they will be backed up along with the CA Datacom/AD CXX and data dictionary entries. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero. Note: After the installation of CA Scheduler is complete, sites currently running Release 8.0 and earlier can use the CONVERT TEST=YES command (see the conversion appendix) to predict how much space is actually needed for your data. You can then delete the data and index areas created in this step and recreate them with the correct size by rerunning job ISTEP18C. The conversion tool, the CONVERT command, stores job and schedule history data in the Release 9.1 format. The history data will eventually need to be upgraded to the r11 format. For more information, see the upgrade history step.
214
Installation Guide
Step 19: Update CA Datacom/AD Tables

Important! This step is required only for sites currently running CA Scheduler Release 9.0. All release numbers in this discussion refer to previous or current releases of CA Scheduler. If you are installing CA Scheduler for the first time or are converting from Release 8.0 or earlier, or upgrading from Release 9.1, skip this step. The table definitions used by r11 are slightly different from the definitions used by Release 9.0. The following steps back up and reformat your existing Release 9.0 data. Releases 9.0, 9.1, and r11 can share the same physical database. The changes to the tables were made by adding columns. Release 9.0 will continue to access the columns it knows about, and will therefore not see any change to the data. Likewise, no "undo" procedure is necessary should you need to fall back from r11 to Release 9.0. Release 9.0 will simply not see the new columns. This procedure must have exclusive access to the CA Scheduler database. All copies of CA Scheduler must be shut down, and all users must be out of the CA Scheduler online. The procedure updates the table definitions for ALL copies of CA Scheduler sharing the physical database. For example, if you have two copies of CA Scheduler, one running as SCHD and one running as SCXX, you only need to run this procedure once to update both copies. You can continue run CA Scheduler Release 9.0 on either copy even after you have updated the table definitions. All copies of CA Scheduler using this copy of CA Datacom/AD must be shut down before running the following steps. To update table definitions 1. SAMPJCL member ISTEP19A estimates the size of the new history data area required by CA Scheduler r11. Job ISTEP19H uses the size information. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero. Note the estimated number of tracks needed for the history area. 2. SAMPJCL member ISTEP19B backs up your existing Release 9.0 data. The backup is not actually used in this procedure, but is taken as a safety measure. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
215
3.
SAMPJCL member ISTEP19C extracts the four tables with new columns (JBR, SBR, JTR, STR) into sequential data sets. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
4.
SAMPJCL member ISTEP19D uses IEBGENER to add space for the new columns. The utility reads the files created in ISTEP19C and creates new sequential data sets. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
5.
SAMPJCL member ISTEP19E backs up your existing Release 9.0 data, excluding the tables that are changing. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
6.
SAMPJCL member ISTEP19F defines the r11 tables to CA Datacom/AD. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
7.
SAMPJCL member ISTEP19G makes the r11 tables available to CA Datacom/AD. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
8.
SAMPJCL member ISTEP19H restores your Release 9.0 data (created in ISTEP19E and excluding the tables being updated) into CA Datacom/AD. This step also allocates the new history data area. Specify the number of tracks for the history file estimated in job ISTEP19A. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
9.
SAMPJCL member ISTEP19I loads the newly-updated tables (from ISTEP19D) into CA Datacom/AD. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
10. SAMPJCL member ISTEP19J backs up the CA Scheduler data in the new format. The backup is not actually used in this procedure but is taken as a safety measure. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero. The tables have now been updated and can be accessed by either Releases 9.0, 9.1 or r11.
216
Installation Guide

Important! This step is required only for sites currently running CA Scheduler Release 9.1. All release numbers in this discussion refer to previous or current releases of CA Scheduler. If you are installing CA Scheduler for the first time or are converting from Release 9.0 or earlier, then skip this step. Releases 9.0, 9.1, and r11 can share the same physical database. The changes to the tables were made by adding columns. Prior releases continue to access the columns they know about, and therefore do not see any change to the data. Likewise, no "undo" procedure is necessary should you need to fall back from r11 to Release 9.1. Release 9.1 simply does not see the new columns. This procedure must have exclusive access to the CA Scheduler database. All copies of CA Scheduler must be shut down, and all users must be out of the CA Scheduler online. The procedure updates the table definitions for all copies of CA Scheduler sharing the physical database. For example, if you have two copies of CA Scheduler, one running as SCHD and one running as SCXX, you only need to run this procedure once to update both copies. Note that you can continue run CA Scheduler Release 9.1 on either copy even after you have updated the table definitions. All copies of CA Scheduler using this copy of CA Datacom/AD must be shut down before running the following steps. To update table definitions 1. SAMPJCL member ISTEP20A estimates the size of the new history data area required by CA Scheduler r11. The size information will be used by job ISTEP20E. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero. Note the estimated number of tracks needed for the history area. 2. SAMPJCL member ISTEP20B backs up your existing Release 9.1 data. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero. 3. SAMPJCL member ISTEP20C defines the r11 tables to CA Datacom/AD. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
217
Step 21: Update System Libraries
4.
SAMPJCL member ISTEP20D makes the Release 9.1 tables available to CA Datacom/AD. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
5.
SAMPJCL member ISTEP20E restores your Release 9.1 data (created in ISTEP19B) into CA Datacom/AD. This step also allocates the new history data area. Specify the number of tracks for the history file estimated in job ISTEP20A. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
6.
SAMPJCL member ISTEP20F backs up the CA Scheduler data in the new format. The backup is not actually used in this procedure, but is taken as a safety measure. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
The tables have now been updated and can be accessed by Releases 9.0, 9.1 or 11.
Step 21: Update System Libraries

This step is required for all sites. Various changes are required to system libraries. Some of these changes can require an IPL to be placed into effect. Most sites can make these changes dynamically. LOADLIB Requirements The CA Scheduler load libraries, CAILOAD and CAICICS, must be APF authorized. You can add the data sets to the IEAAPFxx or PROGxx member in SYS1.PARMLIB to make the data sets authorized. We recommend that the CAILOAD data set be added to the system's linklist (SYS1.PARMLIB member LNKLSTxx). Alternatively, CAILOAD can be added as a STEPLIB to every TSO session and CICS started task that will access CA Scheduler. The CA Datacom/AD CUSLIB and CAILIB data sets should be added to the linklist or TSO STEPLIB with the CA Scheduler CAILOAD data set. If the NJE feature (jobs submitted on one JES node and to be executed and tracked on another JES node) is being used or if you want to use the IBM Health Checker for z/OS feature, the CA Scheduler CAILOAD must be in the linklist. A STEPLIB to CAICICS is required for CICS started tasks that will access CA Scheduler.
218
Installation Guide
Step 22: Update CAIRIM Parameters
NJE Requirements If the CA Scheduler NJE feature will be used (jobs submitted on one JES node to be executed on another), see the JES Exit Installation Requirements and Defining VTAM APPLID (NJE Only) in the previous chapter. TSO ISPF Requirements The CAICLS0 data set must be in the SYSPROC concatenation. CLIST SCHD must be updated with the correct data set names. The CA Scheduler and CA Datacom/AD libraries must be either in the linklist or allocated as a STEPLIB in the TSO logon PROC. ISPF ISPLLIB allocations are not sufficient. TESTLIB Requirements CAIJCL member CAJUTSTB must be copied to your PDS JCL library (started task ddname JCLMASTR). Provide a valid JOB statement and point the STEPLIB to the CA Scheduler load library (not required if the load library is in the linklist). This member is used when a job is defined to CA Scheduler as LIBTYPE=TESTLIB.
Step 22: Update CAIRIM Parameters

This step is required for all sites. The CA Scheduler environment must be initialized by CAIRIM (CAS9) before any CA Scheduler function can be performed. The following statement must be added to the CARIMPRM file:
PRODUCT(CA-SCHEDULER) VERSION(CHB0) INIT(CHB0INIT) PARM(DD=xxxxxxxx)
The PARM points to another DD statement in the CAIRIM task that contains initialization commands. For the format of the commands, see CA Scheduler initialization in the Systems Programmer Guide. CAIOPTN member CHINIT can be used as a model for the initialization commands. SAMPJCL member CHINIT can be used as a sample to initialize CA Scheduler. If you are upgrading from CA Scheduler r9.x and plan to use the same CA Scheduler subsystem that the previous release used, you must delete the previous release of CA Scheduler from the system. SAMPJCL member CHDELETE can be used as a sample to delete a prior release of CA Scheduler.
219
Step 23: Update License Management Program (CA LMP) Key
Note: CA Scheduler r11 can coexist with earlier releases of CA Scheduler on the same system. CA Scheduler r11 cannot share its SVC with earlier releases. Multiple copies of CA Scheduler r11 can use the same SVC. CA Scheduler r11 can be initialized before or after Release 9.x. No initialization statement should be used for CA Scheduler Release 8.0 and earlier.
Step 23: Update License Management Program (CA LMP) Key

This step is required for new installations of CA Scheduler. Sites upgrading from an earlier release of CA Scheduler have already performed this step. CA Scheduler participates with the CA License Management Program (CA LMP). CA Scheduler periodically (at startup and at each autoscan) verifies that it is licensed to run on the current processor. The CAIRIM (CAS9) ddname KEYS points to the list of CA LMP keys. Verify that the CA LMP keys for CA Scheduler match the CA LMP Key Certificate provided with the CA Scheduler distribution package. For instructions on installing and tailoring the CA Scheduler CA LMP key, see the CA Common Services Administrator Guide.
Step 24: CAIENF Database

This step is required for new installations of CA Scheduler and for sites upgrading from CA Scheduler Release 9.0 or earlier. Sites upgrading from CA Scheduler Release 9.1 have already performed this step. This step is only necessary if you plan to use the CA Scheduler NJE feature. SAMPJCL member ISTEP24 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 the Start CAIENF topic. Note: CA Scheduler r11 no longer requires that individual users be defined to CAIENF to run the REPORT AUDIT or REPORT MAILBOX reports. You should still have support people defined to CAIENF to run queries when requested by Technical Support. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
220
Installation Guide
Step 25: CAIENF Startup Options
Step 25: CAIENF Startup Options

This step is required for new installations of CA Scheduler and for sites upgrading from CA Scheduler Release 9.0 or earlier. Sites upgrading from CA Scheduler Release 9.1 have already performed this step. CAIOPTN member CHENFPRM contains sample CAIENF startup options. CHENFPRM can be merged into the existing CAIENF startup options. Use care, since CA Scheduler may not be the only CA product using CAIENF. For information about the CAIENF startup options, see the CA Common Services Administrator Guide. Note: Sites upgrading to CA Scheduler r11 from an earlier release should review their existing CAIENF startup options. CA Scheduler r11 can track started tasks, but your CAIENF may be set not to record events for anything except jobs.
Step 26: Start CAIENF

This step is required for all sites. Start (or restart) CAIENF. If you are restarting CAIENF, use the REINIT option:
S CAIENF,,,REINIT
221
Step 27: Tailor CICS Options
Step 27: Tailor CICS Options

This step is required if you will be accessing CA Scheduler from CICS. Several CICS CSD entries must be tailored for CA Scheduler. Sample entries are provided for each in the CAIOPTN data set, though some values, such as GROUP and LIST, may need to be changed for your site. CSD Entry FCT GROUP PCT PPT CAISRC Member CHFCT CHGROUP CHPCT CHPPTMAP (for maps) CHPPTPGM (for programs) CHPPTTAB (for tables) An additional CAIOPTN member, CHPPTRAC, is provided for sites with RACF that want to use the CA Scheduler external security interface. These entries may already be in place for other CA products.
Step 28: Initialize CICS Work Files

This step is required if you will be accessing CA Scheduler from CICS. If you performed this step for CA Scheduler Release 8.0 or later, you do not need to perform it again. SAMPJCL member ISTEP28 contains JCL to define and initialize two VSAM files for use by the CA Scheduler CICS transactions. Both files should have roughly one cylinder of space per user. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero. You need to allocate two VSAM files to the CICS started task with the ddnames CAIJVWF and CAIJVPF.
222
Installation Guide
Step 29: Install CA Scheduler Dialog
Step 29: Install CA Scheduler Dialog

This step is required for all sites. If you performed this step for CA Scheduler Release 8.0 or later, you do not need to perform it again. You can update an ISPF menu to drive the CA Scheduler dialog. Typically, you would use the ISPF main menu ISR@PRIM, but you can use another menu. In the )BODY section of the menu, add the following line:
% S+CA Scheduler-CA Scheduler Automatic Scheduling System
In the )PROC section of the menu, in the TRANS function, add the following line:
S,'CMD(%SCHD)'
You can use CAIOPTN member CHMENU as a guide to these updates. Make sure you take appropriate backups before changing your ISPF menus.
Step 30: Convert CA Scheduler Data

This step is required if you are upgrading to r11 from Release 8.0 or earlier. If you are upgrading from Release 9.0 or 9.1, skip this step. r11 stores its data in CA Datacom/AD instead of the CATMAN files used by earlier releases of CA Scheduler. For information about converting your Release 7.4 or Release 8.0 data to r11, see Appendix A. A reversion routine is provided and documented in Appendix B, which lets you revert to Release 7.4 or 8.0. Besides the database, the format of the history records (created by the BACKUP HISTORY command) has also changed. For information about converting your Release 7.4 or Release 8.0 history records, see Appendix A. After successfully converting from the previous release of CA Scheduler, we strongly recommend that you back up the data. SAMPJCL member DBBACKUP can be used as a sample. This type of CA Datacom/AD backup cannot be used when the CA Scheduler database is being accessed by a user, a batch job, or the CA Scheduler started task. CA Datacom/AD provides other types of backups. For more information, see the CA Datacom/AD manuals.
223
Step 31: Define User IDs and Date Tables
Step 31: Define User IDs and Date Tables

This step is required for new installations of CA Scheduler. Existing CA Scheduler sites can skip this step or use it as post-installation verification. SAMPJCL member ISTEP31 contains JCL to define user IDs and date tables to CA Scheduler. User IDs are required for every CA Scheduler user unless the installation option SECURITY=EXTERNAL was specified. A date table is required for the current year, previous year, and next year. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
Step 32: Define Demo Job Streams

This step is optional for all sites. SAMPJCL member ISTEP32 contains JCL to copy the demonstration jobs to your JCL library and defines the demonstration job stream to CA Scheduler. You must edit the demonstration jobs after they are copied to provide a valid JOB statement. The job name must be the same as the member name. The demonstration job stream is described in the following topics. It will run automatically when CA Scheduler is started for the first time (and for every autoscan after that). Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
Details of the First Step

DEMO Is the first defined schedule. It contains four jobs: CAJDEM1, CAJDEM2, CAJDEM3, and CAJDEM4. CAJDEM1 Is a simple IEFBR14 job with no dependency. CAJDEM2 Execute CAJUCMD0 to display the current status of schedules and jobs on SYSPRINT.
224
Installation Guide
CAJDEM3 Has CAJDEM2 and the data set DEMO.DSN as its predecessors. The demo schedules never create the data set; thus, you must force this job using the online FORCE command. The JCL is staged to the staging file. The first run abends with an S806, since it executes a nonexistent program. Change the JCL online on the CA Scheduler staging file to execute IEFBR14. Then rerun, using the online RERUN command, so that the job successfully completes. CAJDEM4 Has CAJDEM3 as its predecessor. This job executes the CAJUTIL0 procedure to back up the HISTORY file to a sequential data set for the next schedule.
DEMOHIST
DEMOHIST is the second defined schedule. It contains 11 jobs. Job CAJDEM4 in schedule DEMO is its predecessor; therefore, none of the DEMOHIST jobs can run until CAJDEM4 successfully completes. All of the DEMOHIST jobs execute the CAICHERL procedure to produce the CA Earl canned reports. These jobs are the following: CAJELH01 Scheduled Job Status (by Schedule) Report CAJELH02 Scheduled Job Status (by Station) Report CAJELH03 Completed Job Profile Report CAJELH04 Abended Job Profile Report CAJELH05 Late Job Profile Report CAJELH06 Pending Job Profile Report CAJELH07 Forced And Canceled Report CAJELM01 Basic Job Information (by Schedule) Report
225
CAJELM02 Basic Job Information (by Station) Report CAJELM03 Job Criteria (by Schedule) Report CAJELM04 Job Step Records (by Schedule) Report
DEMOTRCK
DEMOTRCK is the third defined schedule. It contains 13 jobs. DEMOHIST is its predecessor; therefore, none of the DEMOTRCK jobs can run until DEMOHIST successfully completes. All of the DEMOTRCK jobs execute the CAICHERL PROC to produce the CA Earl canned reports. These jobs are the following: CAJELT01 Scheduled Job Status (by Schedule) Report CAJELT02 Scheduled Job Status (by Station) Report CAJELT03 Completed Job Profile Report CAJELT04 Abended Job Profile Report CAJELT06 Pending Job Profile Report CAJELT07 Canceled Jobs Report CAJELTD1 Documentation Selected by the Tracking File Report CAJELD01 Documentation Directory List Report CAJELD02 Documentation Directory and Member List Report CAJELG01 Staged JCL Library Directory List Report CAJELG02 Staged JCL Directory and Member List Report
226
Installation Guide
CAJELS01 Schedule Status CAJELS06 Pending Schedules Report
DEMORPTS
DEMORPTS is the fourth defined schedule. It contains 17 jobs. DEMOTRCK is its predecessor; therefore, none of the DEMORPTS jobs can run until DEMOTRCK successfully completes. All of the DEMORPTS jobs execute the CAJUTIL0 procedure. These jobs are the following: DEMOABND Abend Report DEMOANAL Analyze Report DEMOAUDT Audit Trail Report DEMOCOMP Complete Report DEMODATE Date Translation Report DEMOFORE Forecast Reports DEMOJAVG Job Average Reports DEMOJCHN Job Chain Report DEMOJHST Job History Report DEMOLJOB List Job Report DEMOLSCD List Schedule Report DEMOLSTA List Station Report
227
Step 33: Start and Test CA Scheduler
DEMOLUSR List User Report DEMOMAIL Mailbox Report DEMOSCHN Schedule Chain Report DEMOSIM Simulation Report
The Resource Record

This is for station 40 (the CPU station) for the simulation run.
Step 33: Start and Test CA Scheduler

This step is required for all sites. To test the CA Scheduler Dialog 1. 2. 3. 4. Verify that CAIENF is running. Start the CA Scheduler started task (S CASCHD). Select the CA Scheduler Dialog from the ISPF menu updated in the Install CA Scheduler Dialog topic. Select option 1.1. Press Enter without modifying the screen. If this is a new install and you defined the demonstration job stream in Step 32, then the job stream should already have started. If you did not, you should see your normal workload only. The remaining steps discuss the demonstration job stream. Enter J next to a schedule to see the status of the jobs in that schedule. Issue the START and COMPLETE commands for job CAJDEM3 at station 39. Enter P next to job CAJDEM3 at station 40 to see its predecessors. POST the data set. Several jobs intentionally receive errors to show different statuses.
5. 6. 7. 8.
After running the demonstration job stream, you may want to prevent the job stream from running again. SAMPJCL member ISTEP33 contains JCL to turn off the demonstration jobs.
228
Installation Guide
Step 34: Define/Update Cleanup Job
Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
Step 34: Define/Update Cleanup Job

Sites upgrading to CA Scheduler r11 from Release 9.0 or 9.1 must update the daily cleanup job (CHCLEAN). See CAIJCL member CHCLEAN for a sample job, noting the new required DELETE HISTORY command. Verify that the CHCLEAN job is running daily for every CA Scheduler subsystem. Sites upgrading from Release 8.0 or earlier must define the CHCLEAN job to run daily. CA Scheduler writes audit and mailbox records to the CA Datacom/AD database. These records are used by the REPORT AUDIT and REPORT MAILBOX commands, and should be deleted after a certain number of days. CA Scheduler also writes history records detailing when jobs and schedules start, end, fail, and other events. The REPORT JOBHIST, REPORT SCDHIST, REPORT JOBAVG, and REPORT SCDAVG commands use records. CAIJCL member CHCLEAN contains sample JCL to delete expired audit, mailbox, and history records. This job should be copied to your normal JCL library, whether that is a PDS or some other library type. Provide the job with a valid JOB statement. SAMPJCL member ISTEP34 contains JCL to define the job to CA Scheduler so it will run every day immediately after autoscan. You can schedule the job to run at any time, but we recommend that it be run daily. For more information about the REPORT commands, see the Report Reference Guide. For more information about the DELETE commands, see the Command Reference Guide. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero.
229
Step 35: Automatic Startup
Step 35: Automatic Startup

This step is required for all sites. Update the CAIRIM ddname CAUTOCMD to automatically start CA Datacom/AD, CAIENF, and CA Scheduler.
S CAIENF S datacom-stc-name S CASCHD
CAIENF should be active before any initiators are started. This ensures that CAIENF will track any job activity that happens before CA Scheduler starts.
Step 36: Save All Output

This step is required for all sites. Save the output of all jobs run for this installation. Technical Support may need to see one or more of the jobs to resolve a problem.
230
Installation Guide
Step 37: Upgrade History
Step 37: Upgrade History

This step is required for sites upgrading from a prior release of CA Scheduler. CA Scheduler stores history data for jobs and schedules in a different format for r11 than the format used in previous releases. History data in the old record format is not available to commands such as REPORT JOBHIST. SAMPJCL member HISTUP can be used to upgrade your existing job and schedule history and make it available to r11 REPORT JOBHIST and REPORT SCDHIST commands. This step does not need to be done immediately. In fact, we recommend that you do not upgrade your existing history until you are sure that you will be staying on r11. Follow the directions in the SAMPJCL member to tailor the job, and then submit it. The job should end with a return code of zero. Note that the job will issue a WTOR, to which an operator must respond, before upgrading the history records. If, after upgrading your history record, you decide that you must fall back to Release 9.0 or 9.1, you may use SAMPJCL member HISTDOWN to downgrade the history data back to the old format. HISTDOWN does not need to be done as part of the fallback to the old release, but may be run hours or days later.
231

CA Scheduler r11 uses a different format for the various record types, besides storing the records in CA Datacom/AD instead of CATMAN. A conversion must be done to move the data from the CATMAN files to CA Datacom/AD. A reversion routine is also available in Appendix B to revert to Release 7.4 or 8.0. Only complete schedule and job definitions will be converted. A schedule or job is considered incomplete if subrecords are defined with the base record, or jobs are defined without a schedule. Error messages are issued listing each CATMAN record that is not being converted, and why. A conversion test facility is provided to assist in cleaning up the CATMAN database before converting. We recommend that all errors in the CATMAN database be corrected before you switch from Releases 7.4/8.0 to r11. This may take several iterations of running the conversion test.
Conversion Steps
All release numbers in this discussion refer to previous or current releases of CA Scheduler. To convert from Release 7.4 or 8.0 to r11 1. Using the Release 7.4/8.0 CAJUTIL0 utility, take a backup of the master, tracking, staging, and documentation files. The CA Scheduler started task does not need to be shut down. Use the following r11 JCL to test the conversion:
//stepname EXEC CAJUTIL0 //CAIJBST DD DISP=SHR,DSN=master.backup //CAIJBRK DD DISP=SHR,DSN=tracking.backup //CAIJBCM DD DISP=SHR,DSN=doc.backup //CAIJBTG DD DISP=SHR,DSN=stage.backup //SYSIN DD * CONVERT TEST=YES /*
2.
A1
Conversion Steps
If you do not use the documentation or staging files in Release 7.4/8.0, you must still have the DD statements present. You can use DD DUMMY for the allocation. The ddnames are fixed. You may have set alternate ddnames in Release 7.4/8.0 for the backup files, but in r11 the names must be as shown. 3. Use the error messages from the CONVERT TEST=YES command to correct the Release 7.4/8.0 CATMAN database. For detailed information about the messages and how to correct the problems, see the topic Conversion Messages. Jobs and schedules with errors will not be converted. We strongly recommend correcting all reported problems in the Release 7.4/8.0 CATMAN database before proceeding. 4. After correcting the errors, go back to Step 1 to make sure all of the errors are now gone. Repeat Steps 1-3 as many times as necessary to correct the errors in the CATMAN files. When no errors are detected, proceed to Step 5. Notice the space estimate at the end of the report. You may use the estimates in determining how big the CA Datacom/AD data area and index area files should be (created in CA Scheduler SAMPJCL member ISTEP18C). We recommend making the files larger than necessary (that is, an additional 50%) to allow for growth. 5. 6. 7. Shut down the production Release 7.4/8.0 CA Scheduler started task. Run the Release 7.4/8.0 CAJUTIL0 utility to back up the master, tracking, staging, and documentation files (same job as Step 1). Run the r11 CAJUTIL0 utility to convert the records. Use the same JCL as Step 2, but remove the TEST=YES from the CONVERT command. This will populate the CA Scheduler records in the CA Datacom/AD database. Start the r11 CA Scheduler started task. It will resume work where the Release 7.4/8.0 started task left off. The format of the CA Scheduler history records (created by the BACKUP HISTORY command) has also changed. Run the r11 CAJUTIL0 utility to convert your archived history records to the new format:
//stepname EXEC CAJUTIL0 //HISTIN //HISTOUT //SYSIN /* DD DISP=SHR,DSN=history.backup(s) DD DISP=(NEW,CATLG),DSN=new.history.backup DD *
8. 9.
CONVERT HISTORY
The new history file can be used with the CA-Earl reporting interface.
A2
Installation Guide
Conversion Messages
Conversion Messages
The goal of the CONVERT command is to have a completely clean database under CA Scheduler r11. Previous conditions may have caused database records to become lost. For example a job base record may have been deleted while the job criteria record may still exist. Once under CA Scheduler r11 these situations can no longer occur. The CONVERT command ensures that all jobs have a schedule and that all subrecords (criteria, message, node, and so on) have a base record. If any job lacks a schedule, or subrecord lacks a base record, CONVERT does not carry the offending record to the CA Datacom/AD database. CONVERT treats the record as if it never existed. This method may cause many error messages for a single error in the CATMAN file. For example, if a schedule base record is not found for a schedule named SCHDA, error messages might be issued for the schedule message record and criteria for SCHDA, and also for each and every job defined to SCHDA, and for each of those job's subrecords. You have two options to correct most problems: Either define the missing record (the base record for SCHDA in the previous example), or delete the record listed on the error message. Many cases may require multiple steps to correct. For example, in the SCHDA example above, Release 8.0 will not let you modify the jobs without the schedule being present. Thus, you would have to define the schedule, delete all of the jobs, and then delete the schedule. Note: When deleting schedules and jobs, always use the DELETE SCHEDULE and DELETE JOB commands instead of deleting each individual subrecord. Because a single error may cause many error messages, you may find it easier to correct only a single type of error, then repeat conversion Steps 1 and 2 to generate a new list of errors. You may find that correcting a small group of errors drastically reduces the size of the error report. Correcting the problems in the order that they are listed is probably the most efficient method. Most of the messages should make it obvious what record is being displayed. For example:
CACU217E JOB NOT FOUND,JCR NOT CONVERTED JOBA 01 SCHDA
refers to a job criteria record for job JOBA, JNO 01, station 40 (the blanks after the 01), schedule SCHDA. (Station 40, the CPU station, is stored as two blanks. All other stations are stored as the two-digit station number, such as 39.)
A3
Changing System IDs
You may see error messages referring to record types JSD and JDR. These record types are created and maintained with criteria records. If you still have JSD or JDR error messages after all JCR and SCR error messages have been corrected, contact Technical Support for assistance.
Changing System IDs

Many sites choose to copy the production workload to a z/OS test system when testing CA Scheduler. The CONVERT command can change all references of production SMF IDs to test IDs. Up to 32 SMF IDs can be changed. On the CONVERT command, add the following keyword:
SYSID=('old-smf-id,new-smf-id')
SMF IDs must be specified as four-byte fields. If your SMF IDs are less than four bytes, left justify the ID and pad it with blanks. You must specify the parentheses, quotes, and comma. To change more than one sysid, repeat the 'old-smf-id,new-smf-id' section, separating each with a comma. For example, to change SMF IDs PRD1 and PRD2 to TST1 and TST2, specify:
SYSID=('PRD1,TST1','PRD2,TST2')
A4
Installation Guide
Appendix B: Reversion Steps

Use this procedure to revert from r11 to Release 7.4 or 8.0. The UNCONVRT command extracts the CA Scheduler records from CA Datacom/AD and stores them in sequential data sets suitable for the Release 7.4 or 8.0 RESTORE command. Note: CA Scheduler Release 7.4 must be at Genlevel 9807. To revert from r11 to Release 7.4 or 8.0 1. 2. Stop the r11 started task. Use the following r11 JCL to extract the data from CA Datacom/AD:
//stepname EXEC CAJUTIL0 //CAIJBST DD DISP=(NEW,CATLG),DSN=new.master.backup //CAIJBRK DD DISP=(NEW,CATLG),DSN=new.tracking.backup //CAIJBCM DD DISP=(NEW,CATLG),DSN=new.doc.backup //CAIJBTG DD DISP=(NEW,CATLG),DSN=new.stage.backup //SYSIN UNCONVRT /* DD *
3.
Run the Release 7.4 or 8.0 CAJUTIL0 command with the appropriate RESTORE commands to restore the CATMAN files from the newly created sequential files. Start the Release 7.4 or 8.0 CA Scheduler started task.
4.
Appendix B: Reversion Steps
B1
Index
A
accepting CA Scheduler, 2-9 Acrobat files, 2-10 APPLID parameter, 1-14 applying CA Scheduler, 2-9 assembling CICS routines, 2-12 automatic startup, 2-30
C
CA Common Services components CA LMP, 1-7 CA-Earl, 1-8 CAICCI, 1-7 CAIENF, 1-7 CAIRIM, 1-7 CAISSF, 1-8 CA-SRAM, 1-7 CA-XPS, 1-8 installing, 2-1 overview, 1-6 CA Datacom/AD starting, 2-13 updating options, 2-2 CA Datacom/AD tables defining, 2-14 updating, 2-15 CA JCLCheck, 2-5 CA LMP overview, 1-7 updating, 2-20 CA-C, 1-6 CA-Earl, 1-6, 1-8 CAICCI, 1-7 CAIENF
Index1
database, 2-20 overview, 1-6, 1-7 starting, 2-21 CAIJMTAB member, 1-14 CAIRIM overview, 1-7 updating parameters, 2-19 CAISSF, 1-8 CA-SRAM, 1-6, 1-7 CA-XPS, 1-8 changing system IDs, A-4 CICS assembling routines, 2-12 initializing work files, 2-22 link-edit routines, 2-12 tailoring options, 2-22 cleanup jobs, 2-29 compatability with other products, 1-9 CONVERT command, A-4 converting CA Scheduler data, 2-23 creating SMP data sets, 2-7 CSA storage requirements, 1-6
D
defining CA Datacom/AD tables, 2-14 cleanup jobs, 2-29 demo job streams, 2-24 SMP DDDEFs, 2-8 user IDs and date tables, 2-24 demonstrating CA Scheduler, 2-24 DEMORPTS schedule, 2-27 distribution libraries, 1-5
E
exits, JES, 1-10
Index2
Installation Guide
I
IATXCSF, 1-13 initializing CICS work files, 2-22 SMP, 2-7 installing CA Common Services, 2-1 CA JCLCheck, 2-5 CA Scheduler dialog, 2-23
J
JES exits installation requirements, 1-10 JES2, 1-11 JES3 Driver, 1-12 Subtask ID, 1-13
L
libraries distribution, 1-5 target, 1-4 link editing CICS routines, 2-12 loading Acrobat files, 2-10 SAMPJCL, 2-5
M
MODETAB definition, 1-14
N
NJE requirements, 1-10
Index3
O
operating environments, 1-3
R
reports, demonstrating with DEMORPTS, 2-27 requirements system, 1-3 resource records, 2-28
S
SAMPJCL, loading, 2-5 SMP accepting CA Scheduler, 2-9 applying CA Scheduler, 2-9 creating data sets, 2-7 defining DDDEFs, 2-8 initializing, 2-7 receiving CA Scheduler, 2-8 software compatability, 1-9 supported products, 1-9 starting CA Datacom/AD, 2-13 CA Scheduler, 2-28 CAIENF, 2-21 storage requirements, 1-6 system components, 1-6 requirements, 1-3
T
tailoring CICS options, 2-22 procedures, 2-13 target libraries, 1-4
Index4
Installation Guide
U
updating CA Datacom/AD, 2-2 CA LMP key, 2-20 CAIRIM parameters, 2-19 system libraries, 2-18
V
VTAM communications, 1-10 initialization statements, 1-14
X
XCF communication facility, 1-3
Index5

Ca7 Installation Guide 1

Caricato da

Informazioni sul documento

Descrizione originale:

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Ca7 Installation Guide 1

Caricato da

Copyright:

Formati disponibili

CA Scheduler Job Management

2007 CA. All rights reserved.

Contact Technical Support

Chapter 2: Installation Steps

Appendix A: Releases 7.4 /8.0 Conversion to r11

Appendix B: Reversion Steps Index

Chapter 1: Overview of Components and Installation

Chapter 1: Overview of Components and Installation

Chapter 1: Overview of Components and Installation

Disk Space Estimates for Target Libraries

Disk Space Estimates for Distribution Libraries

CICS Temporary Storage

CA Scheduler-specific CICS Files

Chapter 1: Overview of Components and Installation

CAIRIM and CA LMP

Chapter 1: Overview of Components and Installation

Compatibility with Other Products

Compatibility with Other Releases of CA Scheduler

Chapter 1: Overview of Components and Installation

Compatibility with CA Datacom/AD

JES Exit Installation Requirements

Chapter 1: Overview of Components and Installation

Chapter 1: Overview of Components and Installation

Defining VTAM APPLID (NJE Only)

Chapter 1: Overview of Components and Installation

Chapter 2: Installation Steps

Step 1: Install CA Common Services

Step 2: Install CA Datacom/AD

Chapter 2: Installation Steps

Step 3: Update CA Datacom/AD Options

To install CA Datacom/AD, see the CA Datacom/AD Installation and Maintenance Guide.

Step 3: Update CA Datacom/AD Options

Step 3: Update CA Datacom/AD Options

Other TASKS Settings

Chapter 2: Installation Steps

Step 3: Update CA Datacom/AD Options

Step 4: Install CA JCLCheck Common Component

Step 4: Install CA JCLCheck Common Component

Step 5: Load SAMPJCL

Chapter 2: Installation Steps

Step 6: Tailor SAMPJCL Members

Step 6: Tailor SAMPJCL Members

Save your changes to SAMPJCL member $EDITJCL.

Step 7: Create SMP Data Sets

From ISPF option 6, execute $EDITJCL:

Step 7: Create SMP Data Sets

Step 8: Initialize SMP

Chapter 2: Installation Steps

Step 9: Define SMP DDDEFs

Step 9: Define SMP DDDEFs

Step 10: Receive CA Scheduler

Step 11: Apply CA Scheduler

Step 11: Apply CA Scheduler

Step 12: Accept CA Scheduler

Chapter 2: Installation Steps

Step 13: Load Acrobat (PDF) Files

Step 13: Load Acrobat (PDF) Files

Step 13A: Load Acrobat (PDF) Files from a ZIP File

Step 13: Load Acrobat (PDF) Files

Step 13B: Load Acrobat (PDF) Files from a TGZ File

Chapter 2: Installation Steps

Step 14: Assemble CICS Routines

Step 14: Assemble CICS Routines