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 user’s informational purposes only and is subject to change or withdrawal by CA at any time. This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and protected by the copyright laws of the United States and international treaties. Notwithstanding the foregoing, licensed users may print a reasonable number of copies of the documentation for their own internal use, and may make one copy of the related software as reasonably required for back-up and disaster recovery purposes, provided that all CA copyright notices and legends are affixed to each reproduced copy. Only authorized employees, consultants, or agents of the user who are bound by the provisions of the license for the product are permitted to have access to such copies. The right to print copies of the documentation and to make a copy of the related software is limited to the period during which the applicable license for the Product remains in full force and effect. Should the license terminate for any reason, it shall be the user’s responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed. EXCEPT AS OTHERWISE STATED IN THE APPLICABLE LICENSE AGREEMENT, TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO THE END USER OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED OF SUCH LOSS OR DAMAGE. The use of any product referenced in the Documentation is governed by the end user’s applicable license agreement. The manufacturer of this Documentation is CA. Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.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.

.

.......................................................................................................... 1-14 What's Next? . 2-6 Step 7: Create SMP Data Sets ............... 1-3 CA Common Services ............................ 1-2 XCF ..................................................................................................................Contents Chapter 1: Overview of Components and Installation Components/Concepts ... 2-8 Step 10: Receive CA Scheduler ......................................................... 2-7 Step 9: Define SMP DDDEFs ................................................................................................................................................................... 1-9 Defining VTAM APPLID (NJE Only)........................................................ 1-2 CAICCI ............................. 2-4 Messages .......................................................................................................................................................................... 1-3 Hardware Requirements ............................................. 2-5 Step 5: Load SAMPJCL ..................................... 2-1 Step 2: Install CA Datacom/AD ..................................................................................................................................................................................... 2-2 Tasks ................................................................................................................................................................. 2-7 Step 8: Initialize SMP ....... 2-1 Step 3: Update CA Datacom/AD Options .............. 1-6 Compatibility with Other Products ...... 2-9 Contents v ............................................................... 1-15 Chapter 2: Installation Steps Step 1: Install CA Common Services ......... 2-4 Access ..................... 1-3 Pre-Installation Considerations ... 1-2 CAIENF ....................................................................................... 2-8 Step 11: Apply CA Scheduler .................................................................................... 2-5 Step 6: Tailor SAMPJCL Members .................................................................................................................. 2-3 LXX .................... 1-1 CA Datacom/AD ......................................................................................................... 2-4 Step 4: Install CA JCLCheck Common Component ....................................................................................................................... 2-4 Logging .................................................................. 2-2 Other TASKS Settings ............................................................................................... 1-3 Operating Environments ....................................................................................................................................................................................................... 1-3 SVC Requirements ........ 1-1 Started Task.................................................................. 2-4 FXX .....................

..... A-3 Changing System IDs ...................... 2-25 DEMOTRCK ....................... 2-14 Step 19: Update CA Datacom/AD Tables ...................................... 2-12 Step 15: Link Edit CICS Routines ........... 2-28 Step 34: Define/Update Cleanup Job ..................................................................................................................................................... 2-26 DEMORPTS ..... 2-22 Step 28: Initialize CICS Work Files ............ 2-20 Step 25: CAIENF Startup Options ......................................................................................................... 2-28 Step 33: Start and Test CA Scheduler ................. 2-9 Step 13: Load Acrobat (PDF) Files ............................................................................................................................ 2-19 Step 23: Update License Management Program (CA LMP) Key.................................................................................................. 2-22 Step 29: Install CA Scheduler Dialog ........................................................................................................................................................... 2-31 Appendix A: Releases 7......................................................... 2-10 Step 13B: Load Acrobat (PDF) Files from a TGZ File ..................................................................... 2-17 Step 21: Update System Libraries .............................................. 2-24 Details of the First Step ................................................................................................................ 2-23 Step 31: Define User IDs and Date Tables .....Step 12: Accept CA Scheduler ...... 2-24 Step 32: Define Demo Job Streams .................................................................................4 /8............. A-4 vi Getting Started .............................................. 2-21 Step 27: Tailor CICS Options ........................0 Conversion to r11 Conversion Steps ... A-1 Conversion Messages ...................... 2-29 Step 35: Automatic Startup ....................................... 2-21 Step 26: Start CAIENF........................................................................................ 2-18 Step 22: Update CAIRIM Parameters .............................................................................. 2-30 Step 37: Upgrade History .................................................... 2-13 Step 18: Define CA Datacom/AD Tables ..................... 2-10 Step 13A: Load Acrobat (PDF) Files from a ZIP File ............................ 2-15 Step 20: Update CA Datacom/AD Tables ................................................................................................................................................................................................................ 2-20 Step 24: CAIENF Database ..................................................................................................................................................... 2-30 Step 36: Save All Output ......................................... 2-13 Step 17: Start CA Datacom/AD .................................................................................................................................................... 2-27 The Resource Record ........ 2-24 DEMOHIST . 2-23 Step 30: Convert CA Scheduler Data ........................................................................ 2-12 Step 16: Tailor Procedures....... 2-11 Step 14: Assemble CICS Routines ...........................

Appendix B: Reversion Steps Index Contents vii .

.

Requirements can include time of day. and the availability of virtual resources. CA Scheduler accepts commands from a variety of sources. 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. sometimes called the monitor.Chapter 1: Overview of Components and Installation The following topics introduce the key components of CA Scheduler and discuss some pre-installation considerations. CA Scheduler displays the current status of each job (started. Components/Concepts The following topics introduce important components and concepts. successful completion of other jobs. 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. Chapter 1: Overview of Components and Installation 1–1 . The started task has several functions. including the console (modify commands). is where all of the decision making and work is performed. Tracking jobs that are executing. abended. TSO sessions. Submitting jobs whose requirements have been met. batch jobs (CAJUCMD0 utility). complete. Processing commands. and so on) along with the JES number and return code (if appropriate). Started Task The CA Scheduler started task. All such work is copied to the active workload for processing. Generating emails based on your CA Scheduler email definitions. and REXX programs (address CASCHD).

CA Scheduler uses CAICCI to communicate with other CA scheduling products on other platforms (cross-platform). and a variety of other events. CAIENF monitors the operating system for jobs starting. you can use it for CA Scheduler. ending. Because of the many current and future uses of CAICCI. If you have the separately licensed product CA Datacom/DB. To avoid confusion. CAICCI provides a simple method for CA products to communicate with each other. also called CAIENF. Otherwise. except that you cannot create your own databases in CA Datacom/AD.Components/Concepts CA Datacom/AD CA Scheduler uses CA Datacom/AD as its database. but we recommend that you do not have CA Scheduler use the same CA Datacom/DB MUF (multi-user facility) as your applications. is a component of the CA Common Services. CAIENF must run on every system where z/OS jobs are going to execute. Each event is passed to CA Scheduler and other CA products. We recommend that you use the no license fee copy of CA Datacom/AD that is included with CA Scheduler. backup-while-open. the operation and use of both CA Datacom/AD and CA Datacom/DB are the same. data integrity after a system outage. Using CAIENF allows one set of operating system intercepts to provide data to multiple CA products. The addition of the CA Scheduler workload to your existing application MUF may negatively impact the performance of your existing applications. CAICCI The Common Communication Interface. instead of each product needing to have and maintain its own set of intercepts. CA Datacom/AD is an incredibly fast database engine that allows for forward recovery. 1–2 Installation Guide . CAIENF The Event Notification Facility. it is required for CA Scheduler. among other uses. CA Datacom/AD is identical in every way to CA Datacom/DB. and with Critical Path Monitoring (CPM). and more. also called CAICCI. is a component of the CA Common Services. all references in the guides are to CA Datacom/AD.

CA Scheduler r11 cannot share its SVC with earlier releases. which is an unused SVC. XCF is used when processing tracking commands and for communicating between copies of CA Scheduler in a multiple-CPU (JES MAS) environment.Pre-Installation Considerations XCF CA Scheduler uses IBM’s communication facility XCF. and storage requirements for components. Hardware Requirements The following topics define the disk space requirements for the target and distribution libraries. The default SVC number is 180. 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. SVC numbers 200-255 can be used instead of 180 if preferred. Pre-Installation Considerations The following topics discuss pre-installation considerations.x. Operating Environments CA Scheduler supports any version of z/OS supported by IBM. and the CA Scheduler-specific CICS file requirements. the CICS temporary storage requirements. SVC Requirements CA Scheduler r11 uses an SVC. Chapter 1: Overview of Components and Installation 1–3 . XCF is included as part of the base operating system and does not require any additional hardware.

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.Pre-Installation Considerations Disk Space Estimates for Target Libraries The following table estimates disk space for the target libraries required to install CA Scheduler. 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. 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. less space may be required if some of these components have already been installed. and SMP will automatically compress the data set should it become full while maintenance is being applied. 1–4 Installation Guide . Since these estimates include common components. CAILOAD is allocated with extra space.

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. 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. The DFHTEMP data set record size should be at least 4086 bytes. The files should have roughly one cylinder of data space for each CICS user accessing CA Scheduler.Pre-Installation Considerations Disk Space Estimates for Distribution Libraries The following table estimates disk space for the distribution libraries needed to install CA Scheduler. CA Scheduler-specific CICS Files The CA Scheduler CICS transactions use two VSAM files. Make sure that there is sufficient space in the DFHTEMP data set. Chapter 1: Overview of Components and Installation 1–5 .

Pre-Installation Considerations 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. 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. <1 KB for each copy of CA Scheduler running At least 4 MB. 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. 1–6 Installation Guide .

CA Scheduler requires CA-SRAM. and data sets being updated. CAIENF CAIENF is the CA Event Identification Facility. only using DASD work files when large amounts of data are being sorted. steps ending.Pre-Installation Considerations CAIRIM and CA LMP CAIRIM. it is passed to CA Scheduler once it is started. a CA LMP check is performed to see if CA Scheduler is currently licensed on your processor. Chapter 1: Overview of Components and Installation 1–7 . see the Systems Programmer Guide. is the CA Resource Initialization Manager. If not. including the subsystem SSCT. and CA Scheduler installation and security options. a highlighted message is issued periodically to the console. CA-SRAM CA-SRAM is a set of sort routines used by various CA Scheduler report functions. CAICCI CAICCI is the CA Common Communication Interface. CA Scheduler requires CAICCI. CA-SRAM attempts to perform all sort operations in storage. Using CAIENF allows CA Scheduler to be independent of changes in SMF exits or other IBM facilities. If a recorded event occurs while CA Scheduler is not active. such as autoscan. common modules loaded into ECSA. For more information about initialization. At various points in the CA Scheduler processing. CA Scheduler uses CAIRIM to build and manage the CA Scheduler environment. CAICCI supports communication between CA Scheduler and other CA job management solutions. Each event is communicated to CA Scheduler allowing CA Scheduler to track jobs. CAIENF can record events to its database. CA LMP is the CA License Management Program. sometimes called CAS9. CA Scheduler requires CAIRIM and CA LMP. CAIENF monitors the system for events of interest to CA Scheduler such as jobs starting and ending. CA Scheduler requires CAIENF.

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. see the Interface Reference Guide. CA Scheduler requires CA Earl if CA Scheduler/CA Earl reports are used. and IBM's RACF. New reports can also be created. 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. CAISSF CAISSF is the CA Standard Security Facility. CA Earl can be used to create reports on the data in the CA Scheduler database or active workload. CA-XPS CA-XPS is the Cross Platform Scheduling router.Pre-Installation Considerations CA Earl CA Earl is the CA Easy Access Report Language. 1–8 Installation Guide . Several canned reports are provided and can be tailored to site-specific needs. It is used when Unicenter NSM or CA AutoSys requests a job to be executed on z/OS. CA Top Secret®. see the Report Reference Guide. For more information about external security. which then forwards the requests to a specific scheduling product. CA Scheduler interfaces with CA ACF2™. Requests are sent from the requestor to CA-XPS. CA Scheduler requires CAISSF if you are using external security. For more information.

Multiple copies of CA Scheduler can run on the same z/OS image. Chapter 1: Overview of Components and Installation 1–9 . r11 is a complete replacement of all earlier releases.4. SMP deletes the earlier release. r11 can communicate with Releases 7. 9.0.0.0. or 9.4.1 running on another JES node. 8.Pre-Installation Considerations 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 can share the z/OS image with Releases 7. 9.0. If r11 is installed into an SMP CSI that contains an earlier release of CA Scheduler.1. 8. or 9.

Other applications may require the MUF shut down at times. 1–10 Installation Guide . which would make CA Scheduler unusable. 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. Regardless of the JES exits used and the functions they perform. For example. CA Scheduler can share a CA Datacom/AD Multi-User Facility (MUF) with other applications or can have its own MUF. and are only required if the NJE feature is used. a total of 3 started tasks (one on each LPAR) are executed for one logical copy of CA Scheduler.Pre-Installation Considerations A single logical copy of CA Scheduler includes all of the started tasks running for that copy. All of the started tasks for each logical copy of CA Scheduler must run the same release. We recommend that sites with the full CA Datacom/DB product install CA Datacom/AD for use with CA Scheduler. CA Scheduler may impact performance on your existing CA Datacom/AD (or CA Datacom/DB) applications. JES Exit Installation Requirements These exits are optional. Be sure to review the section for the JES system that applies to your environment. in a 3 LPAR JES MAS. The CA Scheduler load library (CAILOAD) must be in the system link list when the NJE feature is used. the installation process differs mainly in the JES system interface (JES2 or JES3) to be installed. We recommend that CA Scheduler has its own MUF for the following reasons: CA Scheduler is a systems product that must be available 24x7. The remainder of this section discusses the installation procedures for the two JES systems. Compatibility with CA Datacom/AD CA Scheduler requires CA Datacom/AD r11 SP2 or later. Also review Defining VTAM APPLID (NJE Only) in this chapter.

Be sure to include. To apply JES2 exits to your target CAILOAD. Sites can use either or both methods for communication between JES2 nodes. In addition. 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. When installing for multiple CPUs that have different versions of JES2.7. J2CHNJ54. If your JES2 version is changed. include in the SYSLIB data set concatenation. The programs are automatically assembled to the correct level based on the SYSLIB concatenation. in the SMP procedure. CA Scheduler requires JES2 exit 4 when using NJE over SNA and requires JES2 exit 54 when using NJE over TCP/IP. The exit 4 load module is J2CHNJE4.ENABLE Chapter 1: Overview of Components and Installation 1–11 . which contains the correct version of JES2 macros for your system. you need to use a separate load library for each version to store J2CHNJE4. JES2 exit J2CHNJ54 is compatible with JES2 at or above z/OS 1. This is applicable if the JES2 version or maintenance level you are currently running has not yet been accepted by SMP. the JES2 macro library that is appropriate for your current JES2 version in the SYSLIB data set concatenation. the appropriate JES2 SMPMTS data set.ENABLE /* EXIT 54 FOR NJE VIA TCP/IP */ LOADMOD(J2CHNJ54) EXIT054 ROUTINE=CAJ254CH.7. and assembles to a short stub program at releases prior to z/OS 1. you only need to use SAMPJCL member CHJES2 with the new JES2 macro library. as in the following: EXIT004 ROUTINE=(YOUREXIT.7 and above supports NJE over either SNA or TCP/IP.Pre-Installation Considerations JES2 JES2 at z/OS 1.CAJ2X4CH). add the CA Scheduler exit to the list inside parentheses. see installation step Apply CA Scheduler and select CCHB0J2 SYSMOD. You can use the APPLY REDO in SAMPJCL member CHJES2 with the appropriate JES2 library to properly link edit to the desired library. Either or both exits can be installed.ENABLE If other exits are already installed. and CAJMJES2 modules. The exit 54 load module is J2CHNJ54. before the JES2 macro library in the search order. The JES2 exit J2CHNJE4 and the interface program CAJMJES2 are compatible with any JES2 version.

The JES2 exits must be installed on every system where CA Scheduler-submitted NJE jobs will be executed. 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. 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. In addition. 1–12 Installation Guide . use the following instructions. You can either copy load module J2CHNJ54 to an LPA library or create a SYS1. The exits must all have unique CSECT names and entry points. You must identify all of your JES3 exit routines that are to be invoked by the CA Scheduler exit drivers.PARMLIB(PROGxx) member to load J2CHNJ54 dynamically into the LPA at IPL time. 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. If you are using the default IBM-supplied JES3 exits. The PROGxx member might look like this: LPA ADD MODNAME(J2CHNJ54) DSNAME(LNKLST) If the PROGxx member is named PROG54. If you have no additional JES3 exit routines. you can issue the system command T PROG=54 before the start of JES2 to load the exit into LPA. skip to Install JES3 Exits to System Library. any existing exits that use entry point IATUX33 (for JES3 exit 33) need to be changed to a different name.Pre-Installation Considerations JES2 requires that exit 54 be loaded in CSA. 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).

include in the SYSLIB data set concatenation. 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 Chapter 1: Overview of Components and Installation 1–13 . Copy IATUX33 from CAISRC to another library. To apply the JES3 exits to your target CAILOAD. see installation step Apply CA Scheduler. This may require a change to the source code and a reassembly and a link-edit of your existing driver module. the appropriate JES3 SMPMTS data set. Once updated. use SAMPJCL member CHJ33 to tailor the CA Scheduler-provided IATUX33. If you are using the default IBMsupplied JES3 exits only. Modify your existing JES3 exit driver to invoke the CA Scheduler JES3 exits. which contains the correct version of JES3 macros for your system. module names. In addition. and then use the comments in IATUX33 to specify which exits should be called.Pre-Installation Considerations After completing installation Step 11. use SAMPJCL job CHJES3 with the SYSLIB pointing to the JES3 macro library for the new version. Make the new JES3 exits available at execution time. Be sure to edit the sample JCL to include the correct IBM SMP procedure. This is applicable if the JES3 version or maintenance level that you are running currently has not yet been accepted by SMP. Be sure to include. and load libraries. use SAMPJCL job CHJES3 with the SYSLIB pointing to the JES3 macro library for the new version. the JES3 macro library that is appropriate for your current JES3 version in the SYSLIB data set concatenation. zone names. The job should end with a zero return code. in the SMP procedure. To generate the exits for a different version of JES3. The job should end with a return code of zero or four. 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. and select CCHB0J3 SYSMOD. To generate the exits for a different version of JES3. Install JES3 Exits to System Library You need to install the JES3 exits to your system library to: Include your existing JES3 exits. you do not need to include these exits in the linkedit. before JES3 in the search order. submit CHJ33.

ID=nnn.Pre-Installation Considerations When installing for multiple CPUs. number of est'd concurrent sessions ACBNAME=schdapl1. JES3 System Programming Library User Modification and JES3 Macros.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. 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. such as jobs starting and ending. MODETAB=caijmtab. be sure to change the existing JES3 exit 31 and 33 driver modules. you may need to change one of the exits. for each CPU.) The ID=nnn keyword identifies a unique JES3 subtask ID.ID=151.BUSY=label (For more information. Feedback information. using a different subtask ID. Subtask IDs 151255 are reserved for clients. see the IBM manuals. The following statement is to be changed: IATXCSF ENTR=CALLJX. DLOGMOD=caijlogm 1–14 Installation Guide . The CA Scheduler IATUX33 exit routine uses JES3 subtask ID 151. 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. If you have your own. or other vendor software JES3 exits or modifications that use the same subtask ID 151 for long term processing. will be sent from the CA Scheduler where the job executes back to the CA Scheduler that submitted the job.

SAMPJCL member CHMODTAB can be used to assemble and link the MODETAB. 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.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. applnode VBUILD TYPE=CDRSC schdapl2 CDRSC CDRM=cdrmname. Chapter 1: Overview of Components and Installation 1–15 . code a member containing a cross-domain resource definition. What's Next? This chapter introduced the CA Scheduler components and pre-installation considerations. which must be assembled and link edited into VTAM’s VTAMLIB concatenation. For each application ID coded in the CAIJNJE source member.ISTATUS=ACTIVE Member CAIJMTAB in the CAIOPTN data set contains the source code for the MODETAB definition. The next chapter guides you through the installation process.

.

Step 1: Install CA Common Services This step can be skipped if the required components were installed for another CA product. Technical Support may need to see the job output to help resolve any problems you might have.Chapter 2: Installation Steps The following topics guide you through the installation process. Chapter 2: Installation Steps 2–1 . CA Scheduler requires several common components from the CA Common Services tape. Your existing CA Datacom/DB may be scheduled to come down periodically for maintenance. 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). so the CA Datacom it uses must also be up 24x7. with the exception that CA Datacom/AD does not allow the use of user-defined databases. Step 2: Install CA Datacom/AD CA Scheduler uses CA Datacom/AD for its database. 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.com/support). install and configure the required components. CA Datacom/AD has all of the functions of the full CA Datacom/DB product. Using the CA Common Services Getting Started guide (available at http://ca. CA Datacom/AD is a no-charge version of the CA database product CA Datacom/DB. For a list of the components required. 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. Save the output of all jobs run for this install. see the topic CA Common Services in the previous chapter. CA Scheduler must be available 24x7.

Step 3: Update CA Datacom/AD Options This step is required for all sites. The CA Datacom/AD options are normally stored in the CA Datacom/AD CUSMAC library in member DBDATIN2. U is the number of concurrent users. This step updates some CA Datacom/AD options. 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 2–2 Installation Guide . There is no overhead for having too many tasks specified. see the CA Datacom/DB Database and System Administrator Guide. For details on the specified options. R is the number of internal readers to be used (installation option SUBRDR. Setting TASKS to 500 should be sufficient for all sites. For example. default is 5). see the CA Datacom/AD Installation and Maintenance Guide.Step 3: Update CA Datacom/AD Options To install CA Datacom/AD. Increasing the number of tasks later requires restarting CA Scheduler and the CA Datacom/AD MUF. S is the number of systems (z/OS images). 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. 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. Tasks Each user of CA Scheduler connects to the CA Datacom/AD MUF. You can safely over allocate the TASKS number.

z *..Step 3: Update CA Datacom/AD Options 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. Activating the XCF interface requires changes both to the MUF startup options and to CA Datacom/AD module DBSIDPR. Note: The "router MUF" required for CA Datacom/AD Release 9. The CA Datacom/AD MUF runs on a single z/OS image. A reasonable TASKS statement would be: TASKS 500. Other TASKS Settings The second parameter on the TASKS option must be at least 33 KB. Reassemble and link edit DBSIDPR to activate the changes. XCF is used to access the database. and the TOGROUP value must match the second value on the XCFFROM startup option. The same DBSIDPR load module should be used on all systems in the JES node. DBSIDPR is used by CA Scheduler to find the CA Datacom/AD MUF. Set the following MUF startup options: MUF TASKS XCFFROM SCHDMUF x. you can skip this section.0.. Add the TOMUF and TOGROUP keywords to the DBSIDPR: DBSYSID SVC=246.. and the z value is approximately 80% of the x value. Multi-CPU Set Up If your site has only one z/OS image per JES node.400 The source code for DBSIDPR is in the CA Datacom/AD CUSMAC data set.33K.TOGROUP=CASCHED The TOMUF value must batch the MUF startup option.TOMUF=SCHDMUF. On other systems in the JES node.CASCHED where the TASKS statement x value is as determined in the previous section. Note: The FXX data set must be initialized with greater than or equal to the total number of tasks specified on the TASKS statement.. Chapter 2: Installation Steps 2–3 . the y value is at least 33 KB (larger is fine). and positions your shop for increased usage.0 to use XCF is no longer required for CA Datacom/AD r10.SUBID=0.y.

Use of the CA Datacom/AD forward recovery feature requires specific types of backups and log options. 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. see the multiple CPU operations in the Systems Programmer Guide. By default. but some sites may find its use desirable. To suppress the message. which controls CA Datacom/AD processing when all CA Scheduler tasks and users have ended. The ACCESS keyword can be used to change this behavior. The message causes the online screens to be cleared every time a user enters the CA Scheduler online screens. add the following CA Datacom/AD start up option: MESSAGE NO. Messages CA Datacom/AD issues message DB00101I every time the database is opened. Logging You may want to review the logging options specified on the LOGMSGE. 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. We recommend that you do not use the ACCESS keyword for the CA Scheduler database. LOGRCV. CA Datacom/AD keeps certain control blocks active so that a later CA Scheduler task will start faster.DB00101 Access You may want to review the ACCESS keyword. 2–4 Installation Guide . and LOGSPILL keywords.Step 3: Update CA Datacom/AD Options For additional updates that are required for multiple CPU environments. LXX The LXX data set must have a block size of at least 16384.

(500. Use the following JCL to copy the sample JCL library from the installation tape to DASD.SAMPJCL. This step requires that the installation tape be mounted.5)) COPY INDD=((SYSUT1. //jobname //STEP1 //SYSUT1 // // // // //SYSUT2 // // //SYSUT3 // //SYSUT4 // //SYSIN // JOB . VOL=SER=CHxxyy. DD //SYSPRINT DD UNIT=CART. DSN=cai.30)) DD DD DD UNIT=SYSDA. Step 5: Load SAMPJCL This step is required for all sites.SL).SAMPJCL DD DISP=(. CA Scheduler expects CA JCLCheck to be at Release 7. * SPACE=(CYL.REGION=4M SYSOUT=* DISP=(OLD..(5.KEEP).0 or later. Use the CA JCLCheck Getting Started to install the CA JCLCheck common component. The CA JCLCheck common component is provided at no charge to sites without the full CA JCLCheck product.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. EXEC PGM=IEBCOPY.R)). The job should end with a zero return code. Chapter 2: Installation Steps 2–5 .UNIT=SYSDA.OUTDD=SYSUT2 You may need to tailor the JCL for your site's standards.(5.CATLG). UNIT=SYSDA. SPACE=(3120. LABEL=(1. The CA JCLCheck common component can only be used from another CA product.200. DSN=CAI.. CA JCLCheck is used to validate JCL when the CA Scheduler SYNCHK command is used.5)) SPACE=(CYL. The remainder of the CA Scheduler installation uses these jobs.

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

From ISPF option 6. SMP deletes the previous release. and then submit it. execute $EDITJCL: Menu List Mode Functions Utilities Help ISPF Command Shell Enter TSO or Workstation commands below: ===> ex 'cai. We recommend that you install CA Scheduler in its own CSI. It is also possible to install multiple CA products into the same CSI.sampjcl($editjcl)' 4. Step 7: Create SMP Data Sets This step is required for all sites.schd. Note: If CA Scheduler r11 is installed into an SMP CSI that contains a previous release of CA Scheduler. and a return code of zero or four in the fourth step. SAMPJCL member ISTEP07 contains the JCL needed to create the data sets used by SMP and CA Scheduler throughout the remainder of the installation.Step 7: Create SMP Data Sets 3. Follow the directions in the SAMPJCL member to tailor the job. The REXX EXEC edits each member in the SAMPJCL data set and makes all of the changes you entered in $EDITCHG. SAMPJCL member ISTEP08 contains the JCL needed to create the data sets used by SMP throughout the remainder of the installation. and then submit it. Chapter 2: Installation Steps 2–7 . Follow the directions in the SAMPJCL member to tailor the job. Step 8: Initialize SMP This step can be skipped if you are installing CA Scheduler into an existing SMP CSI. The job should end with a zero return code in the first three steps. CA encourages the use of separate SMP CSI data sets (separate global zones) for each release of each CA product. The job should end with a zero return code.

Step 9: Define SMP DDDEFs Step 9: Define SMP DDDEFs This step is required for all sites. The job should end with a return code of zero. 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. The components are the following: CCHB000 CA Scheduler base function. SAMPJCL member ISTEP09 contains the JCL needed to create or update the DDDEF entries in SMP. The DDDEF entry identifies the ddname and data set name to use. and then submit it. SMP has the ability to dynamically allocate all of the data sets it needs. RECEIVE is the SMP command to copy the installation instructions and elements from the tape to DASD. This step requires that the installation tape be mounted. required CCHB0J2 JES2 NJE interface. The job should end with a return code of zero or four. optional CCHB0J3 JES3 NJE interface. Step 10: Receive CA Scheduler This step is required for all sites. Member FMIDS contains the components that make up the CA Scheduler product. follow the directions in the SAMPJCL member ISTEP10 to tailor the job. you need to edit SAMPJCL member FMIDS. 2–8 Installation Guide . and then submit it. You need to delete one or more components from the FMIDS member. SAMPJCL member ISTEP10 contains the JCL needed to receive CA Scheduler. Before submitting ISTEP10 or any of the subsequent jobs. Follow the directions in the SAMPJCL member to tailor the job. After editing member FMIDS.

The job should end with a return code of zero or four. link edit. APPLY is the SMP command to assemble. ACCEPT is the SMP command to store all of the individual pieces of CA Scheduler in the distribution libraries. 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. but it is particularly important to save the APPLY output. The CA 11 interface is included as part of the base product in component CCHB000. Step 12: Accept CA Scheduler This step is required for all sites. Step 11: Apply CA Scheduler This step is required for all sites. Chapter 2: Installation Steps 2–9 . Technical Support will frequently want to see the output of the APPLY job when diagnosing problems. Note: It is important to save the output of this job.Step 11: Apply CA Scheduler Note: The CA 11 interface is no longer a separate component. 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. SAMPJCL member ISTEP11 contains the JCL needed to apply CA Scheduler. SAMPJCL member ISTEP12 contains the JCL needed to accept CA Scheduler. and then submit it. The output of all jobs in the install should be saved.

you should use Step 13B instead of this step.Step 13: Load Acrobat (PDF) Files Step 13: Load Acrobat (PDF) Files This step is optional for all sites.com>. Some UNIX platforms cannot process ZIP files and must use the TGZ file. The files must be transferred from z/OS to another platform before they can be read. This step requires that the installation tape be mounted. The SAMPJCL job ISTEP13A contains the JCL needed to load the PDF ZIP file. You can load either the ZIP file or the TGZ file (or both). 4. CA Scheduler provides Adobe Portable Document Format (PDF) files that can be read by Adobe Acrobat Reader on various distributed platforms. To load PDF files from a ZIP file 1. Use a ZIP utility such as WinZip 7.zip.winzip. depending on your installation’s environment. 2. Start Adobe Acrobat Reader with search capabilities to open the restored PDF files. Name the file schdb0. The directory structure must be kept. and submit the job. ZIP files can be processed by many distributed systems. Follow the directions in the SAMPJCL member to tailor the job. 3. including Windows.adobe. The PDF files are provided in two formats: a ZIP file and a TGZ file. The job should end with a return code of zero. You can find Adobe Acrobat Reader at <http://www.com>. 2–10 Installation Guide . WinZip is available at <http://www. Step 13A: Load Acrobat (PDF) Files from a ZIP File Use this step to load the Adobe Acrobat PDF files from a ZIP file. Use a binary file transfer program such as FTP with the binary option or IND$FILE with no translation. Download the zip file to a platform that supports ZIP and Adobe Acrobat Reader.0 or later to uncompress the file. If you need a TGZ file.

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

Follow the directions in the SAMPJCL member to tailor the job. 2–12 Installation Guide . The USERMOD assembles and link edits three CICS modules. If you are using RACF and will be using the CA Scheduler external security interface. SAMPJCL member ISTEP14 contains JCL to install an SMP USERMOD. The job should end with a return code of four or less. This is done outside of SMP to prevent ownership conflicts with the CICS stub routines. Follow the directions in the SAMPJCL member to tailor the job. 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.Step 14: Assemble CICS Routines Step 14: Assemble CICS Routines This step is required if you will be accessing CA Scheduler from CICS. See the comments in those members. and then submit it. Note: You should run this job whenever CA Scheduler maintenance is applied or restored. The job should end with a return code of zero. SAMPJCL member ISTEP15 contains JCL to link edit the CICS stub routines DFHEAI and DFHEAI0 with the CA Scheduler load modules. or when the version of CICS is changed. Step 15: Link Edit CICS Routines This step is required if you will be accessing CA Scheduler from CICS. see the CA Common Services Getting Started topic. and then submit it.

If CA Datacom/AD is not already running. Make the changes documented in each procedure after it has been copied. start it now. 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. The JCL procedures provided in CAIPROC must be copied to a JES procedure library. CA Datacom/AD must be active when any CA Scheduler activity is performed. Chapter 2: Installation Steps 2–13 . The procedures are listed in the following table. such as SYS1.PROCLIB.Step 16: Tailor Procedures Step 16: Tailor Procedures This step is required for all sites.

After the files have been allocated. The history data will eventually need to be upgraded to the r11 format. 2. see the upgrade history step. SAMPJCL member ISTEP18B contains JCL to make the CA Scheduler tables available to CA Datacom/AD. Note: After the installation of CA Scheduler is complete.1 format. These files will hold all of the CA Scheduler data.0 and earlier. and then submit it. Follow the directions in the SAMPJCL member to tailor the job. and then submit it. sites currently running Release 8. SAMPJCL member ISTEP18C contains JCL to define and initialize the CA Datacom/AD data and index areas for CA Scheduler.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.1. you should skip this step. The conversion tool. If you are upgrading from CA Scheduler r9. and then submit it.0 or r9. The job should end with a return code of zero. Follow the directions in the SAMPJCL member to tailor the job. the CONVERT command. The job should end with a return code of zero. SAMPJCL member ISTEP18A contains JCL to define the CA Scheduler tables to CA Datacom/AD. To define CA Datacom/AD tables 1.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. This step has a series of jobs to define tables and data sets to CA Datacom/AD. stores job and schedule history data in the Release 9. 2–14 Installation Guide . For more information. All release numbers in this discussion refer to previous or current releases of CA Scheduler. Follow the directions in the SAMPJCL member to tailor the job. and for sites converting from CA Scheduler Release 8. they will be backed up along with the CA Datacom/AD CXX and data dictionary entries. The job should end with a return code of zero. 3. You can then delete the data and index areas created in this step and recreate them with the correct size by rerunning job ISTEP18C.

1.1.0 data.0 or earlier. and then submit it. The procedure updates the table definitions for ALL copies of CA Scheduler sharing the physical database. Follow the directions in the SAMPJCL member to tailor the job.0 data. no "undo" procedure is necessary should you need to fall back from r11 to Release 9.0 will simply not see the new columns. 9. Likewise. SAMPJCL member ISTEP19A estimates the size of the new history data area required by CA Scheduler r11.0 on either copy even after you have updated the table definitions. The changes to the tables were made by adding columns. and will therefore not see any change to the data. one running as SCHD and one running as SCXX. Follow the directions in the SAMPJCL member to tailor the job.0. You can continue run CA Scheduler Release 9. Release 9. if you have two copies of CA Scheduler. The backup is not actually used in this procedure. and all users must be out of the CA Scheduler online.Step 19: Update CA Datacom/AD Tables Step 19: Update CA Datacom/AD Tables Important! This step is required only for sites currently running CA Scheduler Release 9. you only need to run this procedure once to update both copies. All copies of CA Scheduler using this copy of CA Datacom/AD must be shut down before running the following steps. This procedure must have exclusive access to the CA Scheduler database. To update table definitions 1.0. The job should end with a return code of zero. Chapter 2: Installation Steps 2–15 . Releases 9. or upgrading from Release 9. The following steps back up and reformat your existing Release 9. Job ISTEP19H uses the size information. but is taken as a safety measure. and then submit it. All copies of CA Scheduler must be shut down.0.0 will continue to access the columns it knows about. If you are installing CA Scheduler for the first time or are converting from Release 8. skip this step. For example. Release 9. The job should end with a return code of zero. and r11 can share the same physical database. SAMPJCL member ISTEP19B backs up your existing Release 9.0. 2. Note the estimated number of tracks needed for the history area. All release numbers in this discussion refer to previous or current releases of CA Scheduler. The table definitions used by r11 are slightly different from the definitions used by Release 9.

and then submit it. This step also allocates the new history data area. and then submit it. 2–16 Installation Guide . SAMPJCL member ISTEP19G makes the r11 tables available to CA Datacom/AD. Follow the directions in the SAMPJCL member to tailor the job. Follow the directions in the SAMPJCL member to tailor the job. SAMPJCL member ISTEP19C extracts the four tables with new columns (JBR. 5.0 data. The job should end with a return code of zero.Step 19: Update CA Datacom/AD Tables 3. Follow the directions in the SAMPJCL member to tailor the job. and then submit it. and then submit it. The job should end with a return code of zero. 9. SAMPJCL member ISTEP19J backs up the CA Scheduler data in the new format. SAMPJCL member ISTEP19I loads the newly-updated tables (from ISTEP19D) into CA Datacom/AD. Specify the number of tracks for the history file estimated in job ISTEP19A.0 data (created in ISTEP19E and excluding the tables being updated) into CA Datacom/AD. Follow the directions in the SAMPJCL member to tailor the job. SAMPJCL member ISTEP19D uses IEBGENER to add space for the new columns. 8. Follow the directions in the SAMPJCL member to tailor the job.1 or r11. The job should end with a return code of zero. JTR. Follow the directions in the SAMPJCL member to tailor the job. 6. The job should end with a return code of zero. The job should end with a return code of zero. The tables have now been updated and can be accessed by either Releases 9. SAMPJCL member ISTEP19H restores your Release 9. 4. The job should end with a return code of zero. 10. 9. Follow the directions in the SAMPJCL member to tailor the job. SBR. and then submit it. STR) into sequential data sets.0. SAMPJCL member ISTEP19F defines the r11 tables to CA Datacom/AD. excluding the tables that are changing. Follow the directions in the SAMPJCL member to tailor the job. 7. The utility reads the files created in ISTEP19C and creates new sequential data sets. SAMPJCL member ISTEP19E backs up your existing Release 9. and then submit it. and then submit it. The job should end with a return code of zero. The backup is not actually used in this procedure but is taken as a safety measure. The job should end with a return code of zero. and then submit it.

and then submit it.1 simply does not see the new columns. All copies of CA Scheduler must be shut down. The job should end with a return code of zero. For example. SAMPJCL member ISTEP20A estimates the size of the new history data area required by CA Scheduler r11. SAMPJCL member ISTEP20C defines the r11 tables to CA Datacom/AD. To update table definitions 1.1 data. and all users must be out of the CA Scheduler online. Chapter 2: Installation Steps 2–17 . The job should end with a return code of zero. Follow the directions in the SAMPJCL member to tailor the job.0 or earlier. Note the estimated number of tracks needed for the history area. one running as SCHD and one running as SCXX. All copies of CA Scheduler using this copy of CA Datacom/AD must be shut down before running the following steps. SAMPJCL member ISTEP20B backs up your existing Release 9.1 on either copy even after you have updated the table definitions. If you are installing CA Scheduler for the first time or are converting from Release 9. Note that you can continue run CA Scheduler Release 9. Releases 9. 2. The size information will be used by job ISTEP20E.0. Follow the directions in the SAMPJCL member to tailor the job.1. no "undo" procedure is necessary should you need to fall back from r11 to Release 9. and r11 can share the same physical database. Likewise.1. Release 9. if you have two copies of CA Scheduler. The procedure updates the table definitions for all copies of CA Scheduler sharing the physical database. and then submit it. and then submit it. 3. All release numbers in this discussion refer to previous or current releases of CA Scheduler. This procedure must have exclusive access to the CA Scheduler database. and therefore do not see any change to the data. Prior releases continue to access the columns they know about. you only need to run this procedure once to update both copies.1. Follow the directions in the SAMPJCL member to tailor the job. then skip this step. The job should end with a return code of zero. 9. The changes to the tables were made by adding columns.Step 20: Update CA Datacom/AD Tables Step 20: Update CA Datacom/AD Tables Important! This step is required only for sites currently running CA Scheduler Release 9.

SAMPJCL member ISTEP20D makes the Release 9.PARMLIB member LNKLSTxx). The backup is not actually used in this procedure. Step 21: Update System Libraries This step is required for all sites. Most sites can make these changes dynamically. CAILOAD can be added as a STEPLIB to every TSO session and CICS started task that will access CA Scheduler. This step also allocates the new history data area. Specify the number of tracks for the history file estimated in job ISTEP20A. and then submit it. the CA Scheduler CAILOAD must be in the linklist. The tables have now been updated and can be accessed by Releases 9. and then submit it. Follow the directions in the SAMPJCL member to tailor the job. 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. SAMPJCL member ISTEP20F backs up the CA Scheduler data in the new format.1 data (created in ISTEP19B) into CA Datacom/AD. A STEPLIB to CAICICS is required for CICS started tasks that will access CA Scheduler. We recommend that the CAILOAD data set be added to the system's linklist (SYS1. The job should end with a return code of zero. Follow the directions in the SAMPJCL member to tailor the job. You can add the data sets to the IEAAPFxx or PROGxx member in SYS1.1 or 11. LOADLIB Requirements The CA Scheduler load libraries. and then submit it. The job should end with a return code of zero.PARMLIB to make the data sets authorized.Step 21: Update System Libraries 4.0. 2–18 Installation Guide . 9. The job should end with a return code of zero. 5. Alternatively. but is taken as a safety measure. SAMPJCL member ISTEP20E restores your Release 9. Follow the directions in the SAMPJCL member to tailor the job. Some of these changes can require an IPL to be placed into effect. 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. Various changes are required to system libraries. CAILOAD and CAICICS. 6. must be APF authorized.1 tables available to CA Datacom/AD.

you must delete the previous release of CA Scheduler from the system. SAMPJCL member CHINIT can be used as a sample to initialize CA Scheduler. Step 22: Update CAIRIM Parameters This step is required for all sites. SAMPJCL member CHDELETE can be used as a sample to delete a prior release of CA Scheduler. The CA Scheduler environment must be initialized by CAIRIM (CAS9) before any CA Scheduler function can be performed. see the JES Exit Installation Requirements and Defining VTAM APPLID (NJE Only) in the previous chapter. CLIST SCHD must be updated with the correct data set names. see CA Scheduler initialization in the Systems Programmer Guide. The CA Scheduler and CA Datacom/AD libraries must be either in the linklist or allocated as a STEPLIB in the TSO logon PROC. This member is used when a job is defined to CA Scheduler as LIBTYPE=TESTLIB. Chapter 2: Installation Steps 2–19 .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). TESTLIB Requirements CAIJCL member CAJUTSTB must be copied to your PDS JCL library (started task ddname JCLMASTR). CAIOPTN member CHINIT can be used as a model for the initialization commands. ISPF ISPLLIB allocations are not sufficient. TSO ISPF Requirements The CAICLS0 data set must be in the SYSPROC concatenation. 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. 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).x and plan to use the same CA Scheduler subsystem that the previous release used. If you are upgrading from CA Scheduler r9. For the format of the commands.

For instructions on installing and tailoring the CA Scheduler CA LMP key. CA Scheduler r11 cannot share its SVC with earlier releases. Multiple copies of CA Scheduler r11 can use the same SVC. CA Scheduler periodically (at startup and at each autoscan) verifies that it is licensed to run on the current processor. see the CA Common Services Administrator Guide. CAIENF must be shut down to run the job. The job should end with a return code of zero. 2–20 Installation Guide . Sites upgrading from an earlier release of CA Scheduler have already performed this step. This step is only necessary if you plan to use the CA Scheduler NJE feature. Do not restart it until so instructed in the Start CAIENF topic. Sites upgrading from CA Scheduler Release 9. No initialization statement should be used for CA Scheduler Release 8. and then submit it.0 and earlier. You should still have support people defined to CAIENF to run queries when requested by Technical Support.1 have already performed this step. SAMPJCL member ISTEP24 defines events to CAIENF and makes them active. Step 24: CAIENF Database This step is required for new installations of CA Scheduler and for sites upgrading from CA Scheduler Release 9. Step 23: Update License Management Program (CA LMP) Key This step is required for new installations of CA Scheduler.0 or earlier. CA Scheduler participates with the CA License Management Program (CA LMP). CA Scheduler r11 can be initialized before or after Release 9. Verify that the CA LMP keys for CA Scheduler match the CA LMP Key Certificate provided with the CA Scheduler distribution package.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. The CAIRIM (CAS9) ddname KEYS points to the list of CA LMP keys. Follow the directions in the SAMPJCL member to tailor the job. Note: CA Scheduler r11 no longer requires that individual users be defined to CAIENF to run the REPORT AUDIT or REPORT MAILBOX reports.x.

use the REINIT option: S CAIENF.. Start (or restart) CAIENF. Step 26: Start CAIENF This step is required for all sites.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. 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. CHENFPRM can be merged into the existing CAIENF startup options.0 or earlier. Sites upgrading from CA Scheduler Release 9.1 have already performed this step. For information about the CAIENF startup options.REINIT Chapter 2: Installation Steps 2–21 . since CA Scheduler may not be the only CA product using CAIENF. but your CAIENF may be set not to record events for anything except jobs. CAIOPTN member CHENFPRM contains sample CAIENF startup options.. Use care. If you are restarting CAIENF.

The job should end with a return code of zero. you do not need to perform it again. These entries may already be in place for other CA products. such as GROUP and LIST. Follow the directions in the SAMPJCL member to tailor the job. Sample entries are provided for each in the CAIOPTN data set. may need to be changed for your site. is provided for sites with RACF that want to use the CA Scheduler external security interface. If you performed this step for CA Scheduler Release 8. CSD Entry FCT GROUP PCT PPT CAISRC Member CHFCT CHGROUP CHPCT CHPPTMAP (for maps) CHPPTPGM (for programs) CHPPTTAB (for tables) An additional CAIOPTN member. and then submit it. 2–22 Installation Guide . 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. Step 28: Initialize CICS Work Files This step is required if you will be accessing CA Scheduler from CICS. CHPPTRAC. You need to allocate two VSAM files to the CICS started task with the ddnames CAIJVWF and CAIJVPF.0 or later.Step 27: Tailor CICS Options Step 27: Tailor CICS Options This step is required if you will be accessing CA Scheduler from CICS. though some values. Several CICS CSD entries must be tailored for CA Scheduler.

see the CA Datacom/AD manuals. r11 stores its data in CA Datacom/AD instead of the CATMAN files used by earlier releases of CA Scheduler. which lets you revert to Release 7. we strongly recommend that you back up the data.1.0. You can update an ISPF menu to drive the CA Scheduler dialog. see Appendix A. SAMPJCL member DBBACKUP can be used as a sample.'CMD(%SCHD)' You can use CAIOPTN member CHMENU as a guide to these updates. If you performed this step for CA Scheduler Release 8. CA Datacom/AD provides other types of backups.4 or Release 8. For more information. Besides the database. Typically. you do not need to perform it again. skip this step. you would use the ISPF main menu ISR@PRIM. the format of the history records (created by the BACKUP HISTORY command) has also changed. A reversion routine is provided and documented in Appendix B.0 or 9. For information about converting your Release 7. In the )BODY section of the menu.4 or Release 8.4 or 8.0 history records. or the CA Scheduler started task. but you can use another menu. add the following line: % S+CA Scheduler-CA Scheduler Automatic Scheduling System In the )PROC section of the menu.0 or earlier.Step 29: Install CA Scheduler Dialog Step 29: Install CA Scheduler Dialog This step is required for all sites. Step 30: Convert CA Scheduler Data This step is required if you are upgrading to r11 from Release 8. see Appendix A. For information about converting your Release 7. add the following line: S. in the TRANS function. This type of CA Datacom/AD backup cannot be used when the CA Scheduler database is being accessed by a user.0 data to r11. Chapter 2: Installation Steps 2–23 .0 or later. If you are upgrading from Release 9. a batch job. Make sure you take appropriate backups before changing your ISPF menus. After successfully converting from the previous release of CA Scheduler.

It will run automatically when CA Scheduler is started for the first time (and for every autoscan after that). and next year. SAMPJCL member ISTEP32 contains JCL to copy the demonstration jobs to your JCL library and defines the demonstration job stream to CA Scheduler. and then submit it. CAJDEM1 Is a simple IEFBR14 job with no dependency. The job should end with a return code of zero. Existing CA Scheduler sites can skip this step or use it as post-installation verification. The demonstration job stream is described in the following topics. You must edit the demonstration jobs after they are copied to provide a valid JOB statement. CAJDEM2. The job should end with a return code of zero. 2–24 Installation Guide . Follow the directions in the SAMPJCL member to tailor the job. CAJDEM2 Execute CAJUCMD0 to display the current status of schedules and jobs on SYSPRINT. CAJDEM3. SAMPJCL member ISTEP31 contains JCL to define user IDs and date tables to CA Scheduler. previous year. Follow the directions in the SAMPJCL member to tailor the job. A date table is required for the current year.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. and CAJDEM4. It contains four jobs: CAJDEM1. User IDs are required for every CA Scheduler user unless the installation option SECURITY=EXTERNAL was specified. Details of the First Step DEMO Is the first defined schedule. Step 32: Define Demo Job Streams This step is optional for all sites. The job name must be the same as the member name. and then submit it.

CAJDEM4 Has CAJDEM3 as its predecessor. All of the DEMOHIST jobs execute the CAICHERL procedure to produce the CA Earl canned reports.DSN as its predecessors. The demo schedules never create the data set.Step 32: Define Demo Job Streams CAJDEM3 Has CAJDEM2 and the data set DEMO. Job CAJDEM4 in schedule DEMO is its predecessor. since it executes a nonexistent program. DEMOHIST DEMOHIST is the second defined schedule. Change the JCL online on the CA Scheduler staging file to execute IEFBR14. The first run abends with an S806. It contains 11 jobs. 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 Chapter 2: Installation Steps 2–25 . therefore. The JCL is staged to the staging file. This job executes the CAJUTIL0 procedure to back up the HISTORY file to a sequential data set for the next schedule. using the online RERUN command. so that the job successfully completes. thus. Then rerun. you must force this job using the online FORCE command. none of the DEMOHIST jobs can run until CAJDEM4 successfully completes.

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 2–26 Installation Guide . All of the DEMOTRCK jobs execute the CAICHERL PROC to produce the CA Earl canned reports. It contains 13 jobs. none of the DEMOTRCK jobs can run until DEMOHIST successfully completes.Step 32: Define Demo Job Streams 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. DEMOHIST is its predecessor. therefore.

DEMOTRCK is its predecessor. none of the DEMORPTS jobs can run until DEMOTRCK successfully completes. 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 Chapter 2: Installation Steps 2–27 . All of the DEMORPTS jobs execute the CAJUTIL0 procedure. It contains 17 jobs.Step 32: Define Demo Job Streams CAJELS01 Schedule Status CAJELS06 Pending Schedules Report DEMORPTS DEMORPTS is the fourth defined schedule. therefore.

2–28 Installation Guide . Enter P next to job CAJDEM3 at station 40 to see its predecessors. POST the data set. SAMPJCL member ISTEP33 contains JCL to turn off the demonstration jobs. If you did not. 8.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. 4. Step 33: Start and Test CA Scheduler This step is required for all sites. 6. Enter J next to a schedule to see the status of the jobs in that schedule. Press Enter without modifying the screen. Verify that CAIENF is running. 7. Issue the START and COMPLETE commands for job CAJDEM3 at station 39. Select option 1. 3. To test the CA Scheduler Dialog 1. 5. you should see your normal workload only. you may want to prevent the job stream from running again. Several jobs intentionally receive errors to show different statuses. 2. The remaining steps discuss the demonstration job stream. After running the demonstration job stream. Select the CA Scheduler Dialog from the ISPF menu updated in the Install CA Scheduler Dialog topic. If this is a new install and you defined the demonstration job stream in Step 32.1. Start the CA Scheduler started task (S CASCHD). then the job stream should already have started.

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

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.

2–30

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.

Chapter 2: Installation Steps

2–31

DSN=master.0 to r11 1. and documentation files. Error messages are issued listing each CATMAN record that is not being converted.4/8.4/8. The CA Scheduler started task does not need to be shut down. We recommend that all errors in the CATMAN database be corrected before you switch from Releases 7.backup //CAIJBCM DD DISP=SHR. Conversion Steps All release numbers in this discussion refer to previous or current releases of CA Scheduler.Appendix A: Releases 7.0 to r11. To convert from Release 7.DSN=doc.backup //CAIJBTG DD DISP=SHR. and why. or jobs are defined without a schedule. This may take several iterations of running the conversion test. besides storing the records in CA Datacom/AD instead of CATMAN. Using the Release 7.backup //SYSIN DD * CONVERT TEST=YES /* 2.DSN=tracking. Use the following r11 JCL to test the conversion: //stepname EXEC CAJUTIL0 //CAIJBST DD DISP=SHR.backup //CAIJBRK DD DISP=SHR.DSN=stage. Only complete schedule and job definitions will be converted.4 /8. A schedule or job is considered incomplete if subrecords are defined with the base record.0.0 CAJUTIL0 utility. tracking. take a backup of the master. staging. 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. Appendix A: Releases 7. A conversion test facility is provided to assist in cleaning up the CATMAN database before converting.4 or 8.4 or 8.4 /8.0 Conversion to r11 CA Scheduler r11 uses a different format for the various record types.0 Conversion to r11 A–1 .

4/8. You may have set alternate ddnames in Release 7. Shut down the production Release 7. We strongly recommend correcting all reported problems in the Release 7. tracking. 6.0 started task left off.4/8.0 CA Scheduler started task. Repeat Steps 1-3 as many times as necessary to correct the errors in the CATMAN files.4/8.DSN=new. Run the r11 CAJUTIL0 utility to convert your archived history records to the new format: //stepname EXEC CAJUTIL0 //HISTIN //HISTOUT //SYSIN /* DD DISP=SHR.backup DD * 8. see the topic Conversion Messages. When no errors are detected. 3.4/8.0. CONVERT HISTORY The new history file can be used with the CA-Earl reporting interface. The ddnames are fixed. you must still have the DD statements present. You can use DD DUMMY for the allocation. Start the r11 CA Scheduler started task. 9. 4. This will populate the CA Scheduler records in the CA Datacom/AD database. but remove the TEST=YES from the CONVERT command. Run the Release 7.4/8.0 CATMAN database.Conversion Steps If you do not use the documentation or staging files in Release 7. Jobs and schedules with errors will not be converted. Use the same JCL as Step 2. It will resume work where the Release 7. After correcting the errors.0 CAJUTIL0 utility to back up the master. proceed to Step 5. and documentation files (same job as Step 1). an additional 50%) to allow for growth. staging.backup(s) DD DISP=(NEW.CATLG). The format of the CA Scheduler history records (created by the BACKUP HISTORY command) has also changed. We recommend making the files larger than necessary (that is.4/8.history. 5. A–2 Installation Guide . Use the error messages from the CONVERT TEST=YES command to correct the Release 7. 7.0 for the backup files. 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).DSN=history. go back to Step 1 to make sure all of the errors are now gone. For detailed information about the messages and how to correct the problems. but in r11 the names must be as shown. Notice the space estimate at the end of the report.0 CATMAN database before proceeding. Run the r11 CAJUTIL0 utility to convert the records.4/8.

such as 39. This method may cause many error messages for a single error in the CATMAN file. Correcting the problems in the order that they are listed is probably the most efficient method.0 will not let you modify the jobs without the schedule being present.) Appendix A: Releases 7. (Station 40.0 Conversion to r11 A–3 . Many cases may require multiple steps to correct. is stored as two blanks. or delete the record listed on the error message. the CPU station. Release 8. and then delete the schedule. Because a single error may cause many error messages. Note: When deleting schedules and jobs. CONVERT treats the record as if it never existed. or subrecord lacks a base record. Thus. you may find it easier to correct only a single type of error. You may find that correcting a small group of errors drastically reduces the size of the error report. and also for each and every job defined to SCHDA. then repeat conversion Steps 1 and 2 to generate a new list of errors. always use the DELETE SCHEDULE and DELETE JOB commands instead of deleting each individual subrecord. For example a job base record may have been deleted while the job criteria record may still exist. JNO 01. and so on) have a base record. For example. If any job lacks a schedule. Previous conditions may have caused database records to become lost.Conversion Messages Conversion Messages The goal of the CONVERT command is to have a completely clean database under CA Scheduler r11. and for each of those job's subrecords.4 /8. you would have to define the schedule. You have two options to correct most problems: Either define the missing record (the base record for SCHDA in the previous example). station 40 (the blanks after the 01). For example: CACU217E JOB NOT FOUND.JCR NOT CONVERTED JOBA 01 SCHDA refers to a job criteria record for job JOBA. Once under CA Scheduler r11 these situations can no longer occur. if a schedule base record is not found for a schedule named SCHDA. CONVERT does not carry the offending record to the CA Datacom/AD database. in the SCHDA example above. schedule SCHDA. All other stations are stored as the two-digit station number. For example. message. delete all of the jobs. Most of the messages should make it obvious what record is being displayed. error messages might be issued for the schedule message record and criteria for SCHDA. The CONVERT command ensures that all jobs have a schedule and that all subrecords (criteria. node.

add the following keyword: SYSID=('old-smf-id. specify: SYSID=('PRD1.TST2') A–4 Installation Guide .new-smf-id') SMF IDs must be specified as four-byte fields. To change more than one sysid.TST1'. contact Technical Support for assistance. If you still have JSD or JDR error messages after all JCR and SCR error messages have been corrected. These record types are created and maintained with criteria records. quotes. The CONVERT command can change all references of production SMF IDs to test IDs. repeat the 'old-smf-id. separating each with a comma. On the CONVERT command. and comma. For example.'PRD2. You must specify the parentheses. Changing System IDs Many sites choose to copy the production workload to a z/OS test system when testing CA Scheduler.new-smf-id' section.Changing System IDs You may see error messages referring to record types JSD and JDR. to change SMF IDs PRD1 and PRD2 to TST1 and TST2. left justify the ID and pad it with blanks. Up to 32 SMF IDs can be changed. If your SMF IDs are less than four bytes.

Appendix B: Reversion Steps Use this procedure to revert from r11 to Release 7.CATLG).DSN=new.0 RESTORE command. Appendix B: Reversion Steps B–1 .CATLG).backup //CAIJBTG DD DISP=(NEW.0 CAJUTIL0 command with the appropriate RESTORE commands to restore the CATMAN files from the newly created sequential files.master.backup //CAIJBCM DD DISP=(NEW.4 or 8.4 or 8. Use the following r11 JCL to extract the data from CA Datacom/AD: //stepname EXEC CAJUTIL0 //CAIJBST DD DISP=(NEW.0 CA Scheduler started task.tracking. 2.4 or 8.4 or 8. The UNCONVRT command extracts the CA Scheduler records from CA Datacom/AD and stores them in sequential data sets suitable for the Release 7. To revert from r11 to Release 7.0.4 must be at Genlevel 9807.backup //CAIJBRK DD DISP=(NEW.DSN=new.backup //SYSIN UNCONVRT /* DD * 3.DSN=new. Start the Release 7.DSN=new. Run the Release 7.stage.doc.CATLG). 4. Stop the r11 started task.0 1.CATLG).4 or 8. Note: CA Scheduler Release 7.

.

1-6 CA Datacom/AD starting. 2-13 updating options. 1-7 CAIRIM. 1-7 CA-Earl. 1-6 CA-Earl. 2-12 automatic startup. 1-8 CAICCI. 2-9 assembling CICS routines. 1-7 CAISSF.Index A accepting CA Scheduler. 2-14 updating. 1-6. 2-1 overview. 2-2 CA Datacom/AD tables defining. 2-9 Acrobat files. 2-15 CA JCLCheck. 1-7 CA-XPS. 1-7 CAIENF. 1-14 applying CA Scheduler. 2-5 CA LMP overview. 2-20 CA-C. 1-8 CAICCI. 1-7 updating. 1-8 CA-SRAM. 1-8 installing. 2-10 APPLID parameter. 1-7 CAIENF Index–1 . 2-30 C CA Common Services components CA LMP.

A-4 converting CA Scheduler data. 2-8 user IDs and date tables. 1-10 Index–2 Installation Guide . 2-24 SMP DDDEFs. 2-12 tailoring options. 1-5 E exits. JES. 1-6. 1-6. 1-14 CAIRIM overview. 2-19 CAISSF.database. 2-23 creating SMP data sets. 2-22 link-edit routines. 1-7 CA-XPS. 2-22 cleanup jobs. 2-24 demonstrating CA Scheduler. 1-6 D defining CA Datacom/AD tables. 1-9 CONVERT command. 2-29 demo job streams. 2-27 distribution libraries. 2-21 CAIJMTAB member. 1-7 updating parameters. 2-20 overview. A-4 CICS assembling routines. 2-7 CSA storage requirements. 2-14 cleanup jobs. 1-8 CA-SRAM. 1-8 changing system IDs. 2-24 DEMORPTS schedule. 1-7 starting. 2-12 initializing work files. 2-29 compatability with other products.

2-1 CA JCLCheck. 1-5 target. 2-5 M MODETAB definition. 1-13 initializing CICS work files. 2-23 J JES exits installation requirements.I IATXCSF. 2-7 installing CA Common Services. 2-22 SMP. 1-13 L libraries distribution. 1-14 N NJE requirements. 1-10 Index–3 . 2-10 SAMPJCL. 1-11 JES3 Driver. 1-12 Subtask ID. 2-5 CA Scheduler dialog. 1-10 JES2. 2-12 loading Acrobat files. 1-4 link editing CICS routines.

2-27 requirements system. 1-3 resource records. 1-6 requirements. 2-22 procedures. 1-6 system components. 2-28 S SAMPJCL. 2-28 CAIENF. 2-7 receiving CA Scheduler. demonstrating with DEMORPTS. 2-8 software compatability. loading. 2-7 defining DDDEFs. 2-8 initializing. 2-13 target libraries. 1-3 T tailoring CICS options. 1-3 R reports. 2-13 CA Scheduler.O operating environments. 2-9 applying CA Scheduler. 2-21 storage requirements. 2-5 SMP accepting CA Scheduler. 1-4 Index–4 Installation Guide . 1-9 supported products. 2-9 creating data sets. 1-9 starting CA Datacom/AD.

2-19 system libraries.U updating CA Datacom/AD. 1-10 initialization statements. 2-18 V VTAM communications. 2-2 CA LMP key. 2-20 CAIRIM parameters. 1-3 Index–5 . 1-14 X XCF communication facility.

Sign up to vote on this title
UsefulNot useful