Unicenter CA-Driver Job Management for VSE Installation · PDF fileSystem Requirements ......

Installation Guide r7.3

K01184-1E

Unicenter CA-Driver

Job Management for VSE

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

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

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

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

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

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

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

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

2005 Computer Associates International, Inc.

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

Contents

Chapter 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11.1 Product Distribution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-21.2 Use of MSHP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Chapter 2. System Requirements . . . . . . . . . . . . . . . . . . . . . . . . 2-12.1 Operating Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-22.2 Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

2.2.1 Multi-CPU Environment . . . . . . . . . . . . . . . . . . . . . . . . . 2-32.2.2 Space Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-32.2.3 Storage Requirements for Unicenter CA-Driver for VSE . . . . . . 2-52.2.4 POWER GETVIS Requirements for Unicenter CA-Driver for VSE 2-52.2.5 Compatibility with CA Products . . . . . . . . . . . . . . . . . . . . 2-5

Chapter 3. Installation Materials . . . . . . . . . . . . . . . . . . . . . . . . 3-13.1 Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-23.2 Installation Tape . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Chapter 4. VSE Installation Steps . . . . . . . . . . . . . . . . . . . . . . . 4-14.1 Standard Installation JCL . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-34.2 Preinstallation Considerations . . . . . . . . . . . . . . . . . . . . . . . . 4-44.3 Installation Overview Checklist . . . . . . . . . . . . . . . . . . . . . . . 4-54.4 Step 1. Review System Requirements . . . . . . . . . . . . . . . . . . . . 4-64.5 Step 2. Review Conversion Requirements . . . . . . . . . . . . . . . . . 4-74.6 Step 3. Complete the Installation Worksheet . . . . . . . . . . . . . . . 4-8

4.6.1 Task 3A. Common Component, Libraries, and MSHP Install . . . 4-84.6.1.1 Standard Product Installation Worksheet . . . . . . . . . . . . 4-94.6.1.2 Standard Product Installation Worksheet . . . . . . . . . . . 4-10

4.6.2 Task 3B. Unicenter CA-Driver for VSE Install Option . . . . . . 4-104.6.2.1 Unicenter CA-Driver for VSE Installation Worksheet . . . . 4-10

4.7 Step 4. Install CA Common Services for VSE Tape . . . . . . . . . . . 4-114.8 Step 5. Install Unicenter CA-Driver for VSE Tape using MSHP . . . 4-124.9 Step 6. Assemble Generation Macro . . . . . . . . . . . . . . . . . . . 4-134.10 Step 7. Install Online Transaction . . . . . . . . . . . . . . . . . . . . 4-14

4.10.1 CICS Commands from a Batch Program . . . . . . . . . . . . . 4-144.10.2 Task 7A. Update Program List Table Initialization (PLTPI) . . 4-144.10.3 Task 7B. Update CICS Program List Table Shut Down (PLTSD) 4-144.10.4 Task 7C. Update CICS Program Control Table (PCT) . . . . . . 4-154.10.5 Task 7D. Update Program Processing Table (PPT) . . . . . . . 4-154.10.6 Task 7E. Update the CSD Data Set . . . . . . . . . . . . . . . . . 4-15

Contents iii

4.11 Step 8. Change ASI Procedure . . . . . . . . . . . . . . . . . . . . . . 4-164.12 Step 9. Activate Unicenter CA-Driver for VSE . . . . . . . . . . . . . 4-174.13 Step 10. Load HELP Database . . . . . . . . . . . . . . . . . . . . . . 4-18

4.13.1 Task 10A. Create and Load HELP Database (First Time) . . . . 4-184.13.2 Task 10B. Load HELP Data into Existing Database . . . . . . . 4-184.13.3 Defining and Loading HELP (Unicenter CA-Driver for VSE) . 4-18

4.13.3.1 Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-194.13.3.2 Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19

4.14 Step 11. Migration of CAI Products into Production . . . . . . . . . 4-204.15 Step 12. Save all Materials and Output . . . . . . . . . . . . . . . . . 4-214.16 Step 13. Review CA Common Services Installation Guide . . . . . . 4-22

Chapter 5. VM/CMS Installation Steps . . . . . . . . . . . . . . . . . . . . 5-15.1 Installation Overview Checklist . . . . . . . . . . . . . . . . . . . . . . . 5-25.2 Step 1. Review System Requirements . . . . . . . . . . . . . . . . . . . . 5-35.3 Step 2. Review the Installation Materials . . . . . . . . . . . . . . . . . . 5-45.4 Step 3. Load the Product from Tape . . . . . . . . . . . . . . . . . . . . 5-55.5 Step 4. Run the Installation EXEC (CACMSGEN) . . . . . . . . . . . . 5-65.6 Step 5. Run Product Modification Facility (CACMSALT) . . . . . . . . 5-75.7 Step 6. Modify DRIV EXEC . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85.8 Step 7. Move CMS Component to Common Minidisk . . . . . . . . . . 5-95.9 Step 8. Save All Materials and Output . . . . . . . . . . . . . . . . . . 5-10

Chapter 6. Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-16.1 Diagnostic Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

6.1.1 Collecting Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . . 6-46.1.2 Interpreting Diagnostic Data . . . . . . . . . . . . . . . . . . . . . . 6-56.1.3 The -DEBUG Command (CARUTIL) . . . . . . . . . . . . . . . . . 6-5

6.2 Accessing the Online Client Support System . . . . . . . . . . . . . . . 6-86.2.1 Requirements for Using SupportConnect . . . . . . . . . . . . . . . 6-86.2.2 Accessing the Technical Support Phone Services Directory . . . . 6-96.2.3 CA-TLC: Total License Care . . . . . . . . . . . . . . . . . . . . . . 6-9

6.3 Calling Computer Associates Technical Support . . . . . . . . . . . . 6-106.4 Generating a Problem Report . . . . . . . . . . . . . . . . . . . . . . . 6-11

6.4.1 CA-ACTIVATOR Problem Reporting Facility . . . . . . . . . . . 6-116.4.2 CAISERV Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

6.5 Product Versions and Maintenance . . . . . . . . . . . . . . . . . . . . 6-146.6 Requesting Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . 6-15

Appendix A. Standard Product Installation Detail . . . . . . . . . . . . A-1A.1 Subsequent Computer Associates Product Installation . . . . . . . . A-2A.2 Migration of Computer Associates Products into Production . . . . A-3A.3 MSHP Installation JCL Customization . . . . . . . . . . . . . . . . . . A-4

Appendix B. SLI and VSE Procedure Conversion . . . . . . . . . . . . . B-1

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

iv Unicenter CA-Driver for VSE Installation Guide

Chapter 1. Introduction

This chapter describes the installation process for Unicenter® CA-Driver® JobManagement for VSE (Unicenter CA-Driver for VSE) in general terms. Theremainder of this guide contains detailed information and instructions neededto accomplish a successful installation. This is achieved when all componentsof the product are installed and successfully tested.

Chapter 1. Introduction 1-1

1.1 Product Distribution

The machine-readable program materials required for installation aredistributed as a multifile installation tape in library BACKUP format suitablefor installation via the IBM Maintain System History Program (MSHP).Chapter 3, 'Installation Materials', provides a detailed description of the tapeformat and contents.

1-2 Unicenter CA-Driver for VSE Installation Guide

1.2 Use of MSHP

MSHP, a tool which you are probably familiar with, is used to performproduct installation and maintenance. MSHP provides the ability to controlthese activities in a consistent manner. This format also provides aninstallation mechanism that system programmers use to maintain the VSEoperating system.

MSHP is used to perform the installation and maintenance of UnicenterCA-Driver for VSE in much the same way as the operating system is installedand maintained. When utilizing MSHP to install a product, a MSHP HistoryFile is required to archive product information such as product identificationand library residence. The History File is subsequently used duringmaintenance application for product and library identification and for archivalof maintenance information. The distribution tape includes the librariescontaining Unicenter CA-Driver for VSE and a corresponding History Fileidentifying these products. The target History File used to install UnicenterCA-Driver for VSE should be kept separate from the operating system'sHistory File. It is also recommended that the Unicenter CA-Driver for VSEtarget libraries be kept apart from the VSE system libraries or sublibraries.

Chapter 1. Introduction 1-3

Chapter 2. System Requirements

This chapter describes the operating environments and each of therequirements to run Unicenter CA-Driver for VSE.

Chapter 2. System Requirements 2-1

2.1 Operating Environments

Unicenter CA-Driver for VSE 7.3 can be used on any IBM-supported VSE/SPor VSE/ESA system. It is also supported by the operating systemVSE/POWER Version 2, Release 2 or above.

No changes are required to the VSE supervisor, nor are any renames ofexisting IBM components required.

The Unicenter CA-Driver for VSE VM/CMS component can be used on anyIBM-supported VM/SP, VM/XA, or VM/ESA system.

The Unicenter CA-Driver for VSE DRIV transaction runs with CICS 2.3 andCICS Transaction Server.

Unicenter CA-Driver for VSE is compatible with the BrightStorCA-DYNAMBrightStor family products at the 6.0 release level, or above, andwith eTrust CA-Top Secret Security for VSE. at release 2.3 and above.

Important!

If you have installed or plan to install Unicenter CA-Scheduler for VSE,you should use the Unicenter CA-Scheduler for VSE/Unicenter CA-Driver forVSE Installation Guide instead of this manual.

2.1 Operating Environments

2.2 Hardware Requirements

This section covers the various space and storage requirements to operateUnicenter CA-Driver for VSE. Also included is a discussion of a multi-CPUenvironment and POWER GETVIS requirements.

2.2.1 Multi-CPU EnvironmentThe Unicenter CA-Driver for VSE procedure library must be on a shared diskif the procedure library is to be common between different operating systems,CPUs, or Virtual Machines under VM. Unicenter CA-Driver for VSE uses asoftware lock on its procedure library; therefore, no hardware reserves areused.

2.2.2 Space RequirementsThis table lists the data sets used to execute Unicenter CA-Driver for VSE:

The following tables estimate the disk space required for the UnicenterCA-Driver for VSE procedure library, HELP data set, and Unicenter CA-Driverfor VSE Expanded JCL file on 3350, 3375, 3380 and 3390 disk devices.Estimates are provided for different CISIZEs based on the 200 procedures inthe Unicenter CA-Driver for VSE procedure library. Estimates for theUnicenter CA-Driver for VSE Expanded JCL file are based on the use of 10active partitions, with approximately 150 statements per job. Your spacerequirements vary depending on your device type and the number ofprocedures.

3350 Cylinders Required For CISIZE

Data Set Purpose

DRIVER Procedure Library Unicenter CA-Driver for VSEprocedures

HELP Data Set HELP text for CA online HELPfacility

DRIVER Expanded JCL File Expanded JCL

Data Set 1024 2048 3072 4096 6144

DRIVER ProcedureLibrary

N/A 6 6 6 5

HELP Data Set N/A 4 N/A N/A N/A

DRIVER ExpandedJCL File

N/A N/A N/A N/A 5

Disk space calculation assumes an average procedure size of 250 statements.

CISIZEs greater than 6144 are not recommended unless they are multiples of6144.

Unicenter CA-Driver for VSE Family Library Requirements

This table estimates disk space in blocks for the target libraries required toinstall Unicenter CA-Driver for VSE.

Number of Library Tracks

3375 48

3380 39

Data Set 1024 2048 3072 4096 6144

N/A 8 8 7 8

N/A N/A N/A N/A 8

Data Set 1024 2048 3072 4096 6144

N/A 5 5 5 5

N/A N/A N/A N/A 5

Data Set 1024 2048 3072 4096 6144

N/A 4 4 4 4

N/A N/A N/A N/A 4

3390 36

9345 43

FBA 2368

Number of Library Blocks: 1174

2.2.3 Storage Requirements for Unicenter CA-Driver for VSEUse the following table to determine the amount of partition GETVIS and SVAstorage your installation requires for Unicenter CA-Driver for VSE systemcomponents and files:

The default for the NESTS option of CAIRGEN is 5.

The default CISIZE for the procedure library is 2048. You can alter this valueby using the FORMAT command in CARUINTA.

System Component Size Required

DRIVER programs 56K

DRIVER GETVIS 11K + (15K x value of NEST in CAIRGEN macro)

DRIVER Library 8K + (CISIZE of Unicenter CA-Driver for VSEprocedure library x 8) x NESTS value

DRIVER SVA 21K + (4K x number of partitions)

2.2.4 POWER GETVIS Requirements for Unicenter CA-Driver for VSEUse the table below to determine the amount of POWER GETVIS that yourinstallation requires for Unicenter CA-Driver for VSE:

System Component Size Required

DRIVER GETVIS 36K + (9K x the number of active partitions)

2.2.5 Compatibility with CA ProductsUnicenter CA-Driver for VSE r7.3 requires CA Common Services r1.4 or above.

Chapter 3. Installation Materials

This chapter describes the documentation associated with Unicenter CA-Driverfor VSE and also describes the files located on the installation tape.

Chapter 3. Installation Materials 3-1

3.1 Documentation

In addtion to this guide, the Unicenter CA-Driver for VSE documentation setconsists of the following manuals:

Unicenter CA-Driver for VSESystems Programmer Guide

Includes instructions on how to customize theproduct.

Unicenter CA-Driver for VSEReference Guide

Describes how to use the product, and liststhe Unicenter CA-Driver for VSE commandsin alphabetical order.

Unicenter CA-Scheduler forVSE/Unicenter CA-Driverfor VSE Message Guide

Contains all of the product messages, thereason for each message, and recommendeduser action.

3.2 Installation Tape

Unicenter CA-Scheduler is distributed on a single, unlabeled tape that must beinstalled through the use of MSHP.

One tape unit is required to install the product. The installation tape containsthe following files:

File No. File Description

001 Tape Mark

002 Tape Mark

003 Tape Mark Libraries - BACKUP format

004 Tape Mark

005 Tape Mark History File - BACKUP format

006 Tape Mark

007 Tape Mark reserved use

008 Tape Mark MSHP Installation JCL - VSE

Jobs to remove prior releases of Unicenter CA-Driver forVSE and components shared between UnicenterCA-Scheduler and CA-Driver for VSE from the HistoryFile.

009 Tape Mark Unicenter CA-Driver for VSE help

010 thru 019 Tape Marks

020 Tape Mark CACMSGEN -- Common CMS component,install EXECs

021 Tape Mark CACAIGEN -- Common CMS CatalogManagement and System

022 thru 025 Tape Marks reserved use

026 Tape Mark CASCHGEN -- Unicenter CA-Driver for VSECMS Components

Chapter 3. Installation Materials 3-3

Chapter 4. VSE Installation Steps

Computer Associates has developed standardized procedures for installingproducts utilizing the VSE MSHP utility. These standards for productinstallation have been developed to allow a common method of installation forall Computer Associates VSE products.

The installation process utilizes two types of history files and libraries:production and installation.

Production Library(s) and History File

The Production libraries and history file are created when the first CAI(Computer Associates International) product tape is installed utilizing thisstandard. This library or library set and history file are designed to containall Computer Associates VSE production products, and space should beallocated sufficient to contain all VSE products expected to be installed,even if only one product is being initially installed. When a product issubsequently installed or reinstalled, it cannot be merged into theproduction library set and history file until testing is complete.

Installation Library(s) and History File

The installation libraries and history file are used for subsequent productinstallation to avoid installation of a new product, or new release of anexisting product, into the user's production environment. These librariesand history file are used for product installation, verification and testing.Each product tape that is installed creates a separate libraries and historyfile that is be unique for that product tape. Once all testing has beencompleted, the product is merged into the production libraries and historyfile.

Creation of these two library sets therefore requires two differentinstallation procedures and sets of JCL, depending upon whether theinstallation is an initial or subsequent installation. When the firststandardized CAI (Computer Associates, Inc.) VSE product tape isinstalled, one job creates the production library or library set and historyfile, and installs the products into same. When a subsequent product tapeis installed, the Installation library or library set and history file are createdand utilized until the product is ready to be migrated into the productionenvironment, at which time the installation library set is deleted.

Chapter 4. VSE Installation Steps 4-1

The standard sequence of product installation is as follows:

1. Retrieving the initial install JCL.

Use the supplied JCL example to extract CAINSTB2 and CAINSTB3 fromthe installtion tape.

2. Modifying the install JCL.

Modify the variables in this JCL using an editor. A worksheet is provideddefining the variables which must be provided (VOLSER, beginning blockor track, etc.; a total of 14 variables).

3. Installing CA Common Services.

Review the CA Common Services documentation before performing thisstep.

4. Installing the products.

Submit the modified MSHP job to create the Computer Associatesproduction libraries and install the products from tape into them.

5. Tailoring and verifying the products.

Proceed with product tailoring and verification.

4.1 Standard Installation JCL

Standard installation JCL has been provided and must be used for installationof all Computer Associates VSE products.

The following table lists the JCL members and information associated witheach:

Where JobName

SourceResides

Member Description

CAINSTB2 Sourcelibrary

CAINSTB2.Z Used to perform allsubsequent CAI productinstallations.

CAINSTB3 Sourcelibrary

CAINSTB3.Z Used to merge productsinto the productionlibraries

4.2 Preinstallation Considerations

Before beginning the installation process, consider the following:

If you are upgrading from a prior release of Unicenter CA-Driver for VSE,we highly recommend that you remove it by applying the JCL supplied inthe Z.REMDRV72 and Z.REMSCD72 source books.

The system processing options available for Unicenter CA-Driver for VSEare presented in the Unicenter CA-Driver for VSE Systems Programmer Guide.Refer to that guide for details on modifying the system to suit your datacenter's needs.

4.3 Installation Overview Checklist

Use the following checklist to track your progress through the installationprocess. These steps are described in detail in this chapter. Please refer to thestep number in question if you find you must call Computer AssociatesCustomer Support for assistance during the installation process.

Step 1. Review System Requirements

Step 2. Review Conversion Requirements

Step 3. Complete The Installation Worksheet

Step 4. Install CA Common Services for VSE Tape

Step 5. Install Unicenter CA-Driver for VSE Tape via MSHP

Step 6. Assemble Generation Macro

Step 7. Install Online Transaction

Step 8. Change ASI Procedure

Step 9. Activate Unicenter CA-Driver for VSE

Step 10. Load HELP Database

Step 11. Migration Of CAI Products Into Production

Step 12. Save All Materials And Output

Step 13. Review CA Common Services Installation Guide

4.4 Step 1. Review System Requirements

Review the system requirements for installing Unicenter CA-Driver for VSE asdescribed in the chapter on "System Requirements." Your system mustconform to these requirements before you can begin installing UnicenterCA-Driver for VSE.

4.5 Step 2. Review Conversion Requirements

Unicenter CA-Driver for VSE is now installed using IBM's MSHP product. Ifyou are a current user of Unicenter CA-Driver for VSE, you must reinstall byfollowing the steps for installation described in this chapter. There is no needfor a conversion from any prior 7.x release of Unicenter CA-Driver for VSE.

Release 7.3 of Unicenter CA-Driver for VSE is a complete replacement for allprevious releases of Unicenter CA-Driver for VSE.

4.6 Step 3. Complete the Installation Worksheet

Several questions concerning the environment in which Unicenter CA-Driverfor VSE is to be installed should be answered before proceeding with theinstallation process.

Which DASD packs are to be used to hold libraries and installation files?

Which file IDs are to be used for libraries and installation files?

What extent information is to be used for libraries and installation files?

The worksheet is provided to help you define these items: it should becompleted before continuing any further with the installation procedure.The keywords on the worksheet are the same as the symbolic parametersused in the supplied installation JCL. These keywords are then used toupdate the sample installation JCL for proper execution in yourenvironment.

4.6.1 Task 3A. Common Component, Libraries, and MSHP InstallSee the tables entitled "Unicenter CA-Driver for VSE Library Requirements"and "CA-Unicenter Library Requirements" in the "Systems Requirements"chapter for specific storage allocations. All space allocations are given inblocks. This is done to allow compatibility between all DASD types. Theallocations specify the library block requirements for installing UnicenterCA-Driver for VSE or CA-Unicenter and include sufficient space to allow forproduct reinstallation and maintenance. They should be used to complete theworksheet that follows.

4.6.1.1 Standard Product Installation Worksheet

DESCRIPTION KEYWORD

1. Supply the following information usedto personalize the Computer AssociatesProduction History File:

Customer Name 1. @CUSTNME=___________ Customer Address @CUSTADD=___________

Customer Phone Number @CUSTPHN=___________ Programmer Name @PROGNME=___________

2. Supply the following information usedfor the Production History File EXTENT:

Volume id of DASD pack 2. @HISTVOL=___________Beginning relative track or block @HISTREL=___________Number of tracks or blocks @HISTEXT=___________

3. Supply the following information usedfor the Install History File EXTENT:

Volume id of DASD pack 3. @INSTVOL=___________Beginning relative track or block @INSTREL=___________Number of tracks or blocks @INSTEXT=___________

4. Supply the tape drive address wherethe installation tape is to be mounted:

4. @TAPECUU=___________

4.6.1.2 Standard Product Installation Worksheet

DESCRIPTION KEYWORD

5. Supply the following information usedfor the Production Library EXTENT:

Volume id of DASD pack 5. @DLIBVOL=___________Beginning relative track or block @DLIBREL=___________Number of tracks or blocks @DLIBEXT=___________

6. Supply the following information usedfor the Install Library:

Volume id of DASD pack 6. @ILIBVOL=___________Beginning relative track or block @ILIBREL=___________Number of tracks or blocks @ILIBEXT=___________

7. Supply the product name and productcode you are installing:

Product Name Product Code

DRIVER ARD73

Product Name 7. @PRODUCT=___________ Product Code @PRODCDE=___________

4.6.2 Task 3B. Unicenter CA-Driver for VSE Install Option

4.6.2.1 Unicenter CA-Driver for VSE Installation Worksheet

DESCRIPTION KEYWORD

The following variable is used toindicate whether this is an initialor subsequent install of any CA productvia MSHP. If this is an initial installselect INIT, if a subsequent installselect SUBS.

INIT or SUBS 1. @INSTALL=___________

4.7 Step 4. Install CA Common Services for VSE Tape

Unicenter CA-Driver for VSE requires the installation of the CA CommonServices for VSE tape at a minimum release of 1.4, genlevel 9605. If it isalready installed, proceed to the next step.

Consult the CA Common Services documentation for details on performingthis step.

Note: To avoid "down leveling" any CA Common services, remember thefollowing:

For a given release of CA Common Services, never install a genlevellower than the one already installed. For example, if r1.4, genlevel 9505is already installed, do not install r1.4, genlevel 9501.

Never install a release lower than the one previously installed. Forexample, if r1.4 is already installed, do not install r1.3.

Unicenter CA-Driver for VSE makes use of the following components, whichare supplied on the CA Common Services Tape.

Catalog Management/System Adapter CAIAUDIT CAICUI CA-SRAMAdvantage for CA-Earl CAIHELP VSE Common Code (Common to allCA-VSE products)

4.8 Step 5. Install Unicenter CA-Driver for VSE Tape using MSHP

4.8 Step 5. Install Unicenter CA-Driver for VSE Tape usingMSHP

In this task the installation JCL member CAINSTB2 for VSE should beextracted from the Z sublibrary of the CAI (Computer Associates International)Product Library that contains previously installed CAI products. Please adhereto the following guidelines when editing JCL into execution JCL:

1. Be sure to limit the scope of editor changes to positions 1 to 71 of theskeleton JCL.

2. Remove the CATALS or CATALOG and BKEND statements from thebeginning and end of each JCL sample. Change @* to /* and change @&to /&.

After all modifications are complete, mount the installation tape on thespecified tape drive and submit the JCL for execution.

4.9 Step 6. Assemble Generation Macro

Assemble the generation macro for Unicenter CA-Driver for VSE. TheSAMPLE member is CARGEND in the Z sublibrary of the source statementlibrary. The installation options are described in detail in the UnicenterCA-Driver for VSE Systems Programmer Guide.

4.10 Step 7. Install Online Transaction

Unicenter CA-Driver for VSE provides its users with an online transaction thataccesses the Unicenter CA-Driver for VSE procedure library for updates anddisplays. This transaction allows you to display or alter Unicenter CA-Driverfor VSE procedures.

The CICS tables, PCT and PPT, must be updated to reflect the entries requiredto execute the DRIV transaction for Unicenter CA-Driver. Steps 7C and 7D areaccurate as written for CICS 2.3 and earlier releases of CICS. Support forTransaction Server r1.1.0 and above are provided with the new ZBOOKDRIVCSD (see Task 7E).

4.10.1 CICS Commands from a Batch ProgramUnicenter CA-Driver for VSE allows you to issue CICS commands from abatch program called CARUCMDA. The CICS PCT, PPT, and PLT tables mustbe updated to reflect the entries required to use this feature.

4.10.2 Task 7A. Update Program List Table Initialization (PLTPI)The following copybook contains the required PLTPI entry to be added; it wascataloged to the Unicenter CA-Driver library during installation.

Note: Skip this step if Unicenter CA-Scheduler is installed.

CICS Table Source Statement Member(In aSublibrary)

PLTPI DRIVPLT1.A

4.10.3 Task 7B. Update CICS Program List Table Shut Down (PLTSD)The following copybook contains the required PLTSD entries to be added; theywere cataloged to the Unicenter CA-Driver library during installation.

Note: Skip this step if Unicenter CA-Scheduler is installed.

CICS Table Source Statement Member(In aSublibrary)

PLTPSD DRIVPLT1.A

4.10 Step 7. Install Online Transaction

4.10.4 Task 7C. Update CICS Program Control Table (PCT)Update the CICS Program Control Table (PCT). If using CICS ResourceDefinition online, this step can be omitted.

The following copybooks contain the required PCT entries to be added; theywere cataloged to the common component library during installation:

Copybook name CICS 2.3 and below

Unicenter CA-Driver DRIVPCT.A

Unicenter CA-Driver DRIVPCT1.A

4.10.5 Task 7D. Update Program Processing Table (PPT)Update the CICS Program Processing Table (PPT). If using CICS ResourceDefinition online, this task can be omitted.

The following copybooks contain the required PPT entries to be added; theywere cataloged to the common component library during installation:

If a new PLTPI or PLTSD phase has been generated, DFHPPT statements mustbe inserted into the PPT at this time.

If using the CA-CIS Common Services Audit feature, the following copybookis needed to view these entries through the CICS CUI transaction.

Copybook name CICS 2.3 and below

Unicenter CA-Driver DRIVPPT.A

Unicenter CA-Driver DRIVPPT1.A

Copybook Name CICS 2.3 and below

Unicenter CA-Driver CARDPPT.A

4.10.6 Task 7E. Update the CSD Data SetThe CSD data set must be updated to reflect the presence of UnicenterCA-Driver in the system. The DRIVCSD ZBOOK should be used to add onlinesupport to the appropriate client CSD data set.

4.11 Step 8. Change ASI Procedure

Before activating Unicenter CA-Driver for VSE, make the following changes toyour ASI procedure.

1. Add an execute of the CA system initialization program CASAUTIL to thebackground ASI. (Make sure the library containing the UnicenterCA-Driver for VSE component is in the LIBDEF string before executingCASAUTIL.) If POWER is automatically started by the ASI, add theexecution of CASAUTIL before the START command for the POWERpartition.

2. Add labels for the procedure library, HELP data set, and the ExpandedJCL file to the standard label area.

3. Add labels for CA-SRAM work file (WORK1) to the appropriate label area.

4. Add ASSGN statements for SYS numbers used in the DRIVER Procedurelibrary, HELP data set, expanded JCL file, and work files to all partitions.

5. Make the necessary changes to your SDL LOADLIST. Remove anyUnicenter CA-Driver for VSE phases from the provided copybookSCHDRSDL in the Z sublibrary.

6. VSE job accounting must be activated by coding JA=YES on the SYS IPLcommand.

Filename Data Set

CAIHELP HELP

CAIJDRV DRIVER Procedure

CAITDRV Unicenter CA-Driver for VSE Expanded JCL File

4.12 Step 9. Activate Unicenter CA-Driver for VSE

Unicenter CA-Driver for VSE is now installed but cannot be activated until anIPL is performed and the procedure library is initialized. If you are convertingfrom r2.1, backup the DRIVER procedure library using the 2.1 utility beforeIPLing the system.

1. IPL the system.

This brings the Unicenter CA-Driver for VSE modules into core. Reviewthe Systems Programmer Guide and make the necessary changes to theASI PROC prior to the IPL.

2. Initialize the procedure library.

Member DRIVFMT in the Z sublibrary of the source statement libraryinitializes the procedure library. (If you are reinstalling UnicenterCA-Driver for VSE r7.3 or have a prior 7.x version, skip this step.) Referto the Systems Programmer guide for information on initializing theUnicenter CA-Driver for VSE procedure library.

3. Define Unicenter CA-Driver for VSE to the CAIAUDIT system.

Member DRIVAFMT in the Z library of the source statement librarydefines Unicenter CA-Driver for VSE to the CAIAUDIT system.

4. Initialize Unicenter CA-Driver for VSE.

Unicenter CA-Driver for VSE will be activated the next time POWER isinitialized.

5. Re-IPL your system or bring POWER up at this time.

4.13 Step 10. Load HELP Database

Loading the Unicenter CA-Driver for VSE HELP data enables you to accessHELP information online.

1. Task 10A -- Applies to a new installation of the CA HELP database.

2. Task 10B -- Applies if you have already created the HELP database.

4.13.1 Task 10A. Create and Load HELP Database (First Time)Member CAHLINTC, in the Z sublibrary of the source statement library,creates the HELP database and load the data from the installation tape. Editthis JCL to conform to your installation's standard, then submit the job andreview the output.

Caution!

CAHLINTC needs to be run only once for all Computer Associatesproducts that use a non-VSAM HELP data set. If a non-VSAM HELP dataset has already been defined at your site for another Computer Associatesproduct, submit book CAHLMRGC to merge the Unicenter CA-Driver forVSE HELP data into the existing non-VSAM HELP data set.

4.13.2 Task 10B. Load HELP Data into Existing DatabaseMember CAHLMRGC, in the Z sublibrary of the source statement library,loads the Unicenter CA-Driver for VSE HELP data into a HELP database thathas already been created for another Computer Associates product, such asBrightStor CA-Dynam/T Tape Management or eTrust CA-Top Secret Securityfor VSE. Edit this JCL to conform to your installation's standard, then submitthe job and review the output.

4.13.3 Defining and Loading HELP (Unicenter CA-Driver for VSE)Use CAIHELP to define and load the HELP data set. The CAIHELP programis used to load a Catalog HELP file from a Computer Associates installationtape. CAIHELP requires a TLBL with the file name of CAIHLPT for the inputtape (product install tape) and uses SYS005 for the tape logical unit. Theoutput file name is CAIHELP.

The following input parameters are accepted by CAIHELP:

CATALOG Indicates a catalog file is being used for the HELP file.

INITIAL Indicates HELP file is to be initialized during loading input data.

4.13 Step 10. Load HELP Database

MERGE Indicates input HELP data is being merged with the existing HELPCatalog.

Note: INITIAL and MERGE are mutually exclusive parameters.

PRINT Print the HELP data from the install tape. It can be specified aloneor while loading or merging the HELP file.

UPPER Used in conjunction with PRINT parameter to convert print outputto uppercase.

4.13.3.1 Example 1

The following is an example of the JCL needed to create a catalogHELP file from a product installation tape. This sample JCL can also be foundin Source Library member CAHLINTC in the Z sublibrary of the productlibraries.

// JOB LOAD CA-CATALOG NON-VSAM HELP FILE// DLBL CAIHELP,'CAI.HELP.FILE',99/365,SD// EXTENT SYS 19,volser,,,69 ,3 <==== Volume to contain file// ASSGN SYS 19,cuu <==== CUU of above volume// PAUSE MOUNT CA PRODUCT DISTRIBUTION TAPE// TLBL CAIHLPT// ASSGN SYS 5,cuu <==== Assign to Tape Drive// MTC REW,SYS 5// MTC FSF,SYS 5,8// EXEC CAIHELP,SIZE=128K

CATALOG INITIAL CISIZE=2 48//&

Note: If a CA catalog is being created, the system adapter must be up beforeattempting to initialize or merge the HELP file.

4.13.3.2 Example 2

The following is an example of the JCL needed to merge a catalog HELP filefrom a product installation tape. This sample JCL can also be found in theSource Library member CAHLINTC in Z sublibrary of the product library.

// JOB CAHLMRGC - MERGE HELP DATA TO EXISTING NON-VSAM HELP FILE// PAUSE MOUNT DISTRIBUTION TAPE// ASSGN SYS 5,CUU <==== TAPE CUU// MTC REW,SYS 5// MTC FSF,SYS 5,8// TLBL CAIHLPT// DLBL CAIHELP,'CAI.HELP.FILE',99/365// EXTENT SYSnnn,xxxxxx,1, ,nnn,nn <==== EXTENT INFO// ASSGN SYSnnn,DISK,VOL=xxxxxx,SHR// EXEC CAIHELP

CATALOG MERGE CISIZE=2 48//&

Note: If a catalog HELP file is being created or updated, the System Adaptermust be up before attempting to initialize or merge the HELP file.

4.14 Step 11. Migration of CAI Products into Production

This step applies to subsequent installs only.

CAINSTB3 is used to migrate a product into the production libraries andhistory file when a product was installed to an installation libraries and historyfile using CAINSTB2. This step is executed only after product installation,customization, verification and testing is complete.

The JCL is located on the restored source library in the Z sublibrary and isnamed CAINSTB3.

Ensure that all modifications have been made according to the InstallationWorksheet and submit the JCL for execution.

After this process is complete, the installation libraries and history file can bedeleted.

4.15 Step 12. Save all Materials and Output

Be sure to save all of your installation materials and all output from theinstallation process. This material is essential for timely and accurate ComputerAssociates maintenance and support of the product.

4.16 Step 13. Review CA Common Services Installation Guide

4.16 Step 13. Review CA Common Services InstallationGuide

Review the "Installation Overview Checklist" in the CA Common ServicesInstallation Guide to ensure that all of its steps have been completed.

Chapter 5. VM/CMS Installation Steps

This chapter gives step-by-step instructions on installing the VM/CMScomponent of Unicenter CA-Driver for VSE.

Chapter 5. VM/CMS Installation Steps 5-1

5.1 Installation Overview Checklist

The installation procedure for the VM/CMS component of UnicenterCA-Driver for VSE is designed to be fast and easy to use: the tape provides thenecessary CMS EXECs to perform the actual installation.

The following checklist should be used as you proceed through the installationprocess. These steps are discussed in further detail in this chapter.

Step 1. Review System Requirements

Step 2. Review The Installation Materials

Step 3. Load the Product From Tape

Step 4. Run The Installation EXEC (CACMSGEN)

Step 5. Run Product Modification Facility (CACMSALT)

Step 6. Modify DRIV EXEC

Step 7. Move CMS Component to A Common Minidisk

Step 8. Save All Materials And Output

5.2 Step 1. Review System Requirements

The Unicenter CA-Driver for VSE VM/CMS component requires no specialfacilities other than DASD storage for the DRIV EXEC, the UnicenterCA-Driver for VSE CMS transaction program, and supporting material. Allsuch material may reside on any CMS minidisk.

Ten cylinders of 3350 DASD (or equivalent space) should be reserved for this.It is recommended that this material be moved to a commonly accessed CMSdisk (for example, the CMS Y-disk) if the DRIV CMS transaction is to begenerally available to CMS users.

If the DRIV transaction is to be available to CMS users, the disk containing theUnicenter CA-Driver for VSE procedure library and the Unicenter CA-Driverfor VSE HELP data set must be accessible in multi-write mode by means of theCP LINK command. In addition, the procedure library must be formatted inthe VSE system with the parameter SHARE=YES.

5.3 Step 2. Review the Installation Materials

The Unicenter CA-Driver for VSE distribution tape includes several files inCMS TAPE DUMP format, following the standard installation and HELPmaterial.

These files are located on the 20th, 21st, and 26th logical files on your tape.

5.4 Step 3. Load the Product from Tape

1. Log onto the VM userid where the VM/CMS component is to be installedand have the Unicenter CA-Driver for VSE distribution tape mounted andattached to the virtual machine at address x'181'.

2. Issue the following CMS commands:

TAPE REW

TAPE FSF 19

TAPE LOAD

Some files will be written to the CMS A-disk. These are necessary tocomplete the installation, and should be maintained when the installationis complete.

5.5 Step 4. Run the Installation EXEC (CACMSGEN)

Leave the tape as positioned after Step 3 and issue the command CACMSGEN.Respond correctly to the messages issued by this installation EXEC.

When the selection screen is displayed, enter:

DRIVER

to install the Unicenter CA-Driver for VSE VM/CMS component

Respond correctly to all messages issued by this installation EXEC. If aninvalid response is detected, the initial selection must be performed again.

A user override library, CAUSRLIB TXTLIB, is automatically created duringinstallation if none is found on any currently accessed CMS disks. This libraryis created only during installation and should not be moved or deleted, as itwill be used by the product modification facility, CACMSALT EXEC, to holddetails of all altered processing options.

5.6 Step 5. Run Product Modification Facility (CACMSALT)

Alter, as required, all product control tables (i.e., CAIRGEN) using thecommand, CACMSALT. This EXEC operates in a manner similar to theinstallation EXEC, CACMSGEN, and any incorrect response causes theselection screen to be redisplayed.

When the selection screen is displayed, enter DRIVDOS to alter the CAIRGENmacro.

When the correct selection is made, the CACMSALT EXEC invokes the CMSSystem Editor to assist tailoring of the product control tables. Make allnecessary alterations, and enter FILE when complete. The message whichfollows must be responded to with GO in order that the macros be assembledand the resultant control table be inserted into the user override library,CAUSRLIB TXTLIB. Upon successful completion of these steps, the CA systemnucleus is regenerated to reflect all installation tailoring. It is necessary to IPLCMS to insure that these new generation options take effect.

Note that the distributed VM/CMS component is preconfigured for successfulCMS operation, and consequently differs from the distributed VSE defaultoptions. This is achieved by specifying the parameters, GENPHAS=NO, andTYPE=NOCSECT in the CAIRGEN macro. These parameters should not bealtered.

Note: The parameter values must agree with those specified in the VSECAIRGEN macro in order to ensure consistency in displays andupdates to the database.

5.7 Step 6. Modify DRIV EXEC

Enter the command CACMSALT to select the DRIV EXEC for modification.The CMS file, DRIV EXEC, is used to execute the DRIV full-screen transactionin a CMS environment.

Consequently, this EXEC must be modified to reflect the Unicenter CA-Driverfor VSE procedure library. The procedure library and HELP files are describedin the sample EXEC by the following CP/CMS commands:

CP LINK DOSVSE 2 1 2 1 MW MULTPASSACCESS 2 1 UFILEDEF CAIJDRV U DSN CAI DRIVERFILEDEF CAIHELP U DSN CAI HELP

As the EXEC may be used in any CMS virtual machine to execute the DRIVtransaction, ensure that the DASD address and the CMS filemode conflict aslittle as possible with installation standards. Note that the UnicenterCA-Driver for VSE procedure library must be initialized with the parameter'SHARE=YES'.

The DRIV EXEC is self-documenting by means of extensive comments. Alterall necessary parameters for procedure library access before issuing the editorcommand, FILE.

5.8 Step 7. Move CMS Component to Common Minidisk

If it is necessary to move the CMS component to a common CMS minidisk forgeneral access, use the CMS COPYFILE command to copy all files with afiletype of MODULE or TXTLIB and the file DRIV EXEC.

5.9 Step 8. Save All Materials and Output

Save your installation materials and output from the installation process. Thismaterial is essential for timely and accurate Computer Associates maintenanceand support of the product. Also, please do not erase any files which arecreated during the installation process. Many files have a filetype of'LOADMAP', 'TAPEMAP' or 'TXTMAP', and may be necessary for futureproblem determination.

Chapter 6. Troubleshooting

This chapter contains information about:

Identifying and resolving problemsContacting Computer Associates Technical SupportReceiving ongoing product releases and maintenanceRequesting product enhancements

Chapter 6. Troubleshooting 6-1

6.1 Diagnostic Procedures

Refer to the flowchart below for a summary of the procedures to follow if youhave a problem with a Computer Associates software product. Each of theseprocedures is detailed on the following pages.

6.1.1 Collecting Diagnostic DataIn the following table, use the left column to categorize the problem your sitehas encountered. Then, follow the instructions in the corresponding rightcolumn to generate useful diagnostic data.

For Be Sure To Check

All Problems The DUMP, if an abend has occurred.

All JCL, Console Logs and messages for thefailure.

Listings of all user-coded UnicenterCA-Driver for VSE exits in use.

The SYSLST output from the execution ofCAISERV.

The SYSLST output from the execution ofDRIVER using option LIST=PRINT.

Installation All output produced by MSHP when theproduct was installed.

The output of a MSHP retrace from theComputer Associates history file.

Online Abends The items listed above for All Problems.Online abends require a full partition dump.

CICS startup JCL if failure was under CICS orUnicenter CA-Driver for VSE startup EXECunder CMS.

A description of the online function that wasbeing used at the time of the failure.

Job Routing Failures Check the SUBCLAS option in the CAIRGENMacro and make sure that it is a CLASS thatis not assigned to a POWER partition.

Check the CPUID option in the CAIRGENMacro and if it is defined, make sure that it isa valid CPU number.

Make sure that the POWER CLASSes definedin the CAIRGEN Macro, CLASS (n) option forstatic partitions and DYNCLS(n) for dynamicpartitions, are correct.

For Be Sure To Check

Procedure ExpansionFailures

Verify that the Reader/Job Exit is in thePOWER Macro and the macro's assembly waserror free.

Check that the partition in which the job isrunning has not had Unicenter CA-Driver forVSE disabled. This can be done by running a//CARCTL STATUS job to check allpartitions defined to Unicenter CA-Driver forVSE.

Check that Unicenter CA-Driver for VSE hasnot been disabled completely.

6.1.2 Interpreting Diagnostic DataWhen you have collected the specified diagnostic data, write down youranswers to the following questions:

1. What was the sequence of events prior to the error condition?

2. What circumstances existed when the problem occurred and what actiondid you take?

3. Has this situation occurred before? What was different then?

4. Did the problem occur after a particular PTF was applied or after a newrelease of the software was installed?

5. Have you recently installed a new release of the operating system?

6. Has the hardware configuration (tape drives, disk drives, and so forth)changed?

From your response to these questions and the diagnostic data, try to identifythe cause and resolve the problem.

6.1.3 The -DEBUG Command (CARUTIL)There are three options of the -DEBUG command: CSECT, REG, and DUMP.Descriptions of each follow:

-DEBUG ENABLE SYSTEM,CSECT

This displays the user information, along with the failing CSECT name andapproximate address of the error in the CSECT. For example, the followingcould be displayed:

Unicenter CA-Driver for VSE DEBUG HAS BEEN ENABLEDCURRENT RETURN CODE= 8, CSECT NAME/LOC= CARU 2 / 62914

-DEBUG ENABLE SYSTEM,REG

This displays the user information, the failing CSECT name, and theapproximate address of the error in the CSECT. In addition, the contents ofall registers are displayed. For example:

Unicenter CA-Driver for VSE DEBUG HAS BEEN ENABLEDCURRENT RETURN CODE= 8, CSECT NAME/LOC= CARU 2 / 62914DEBUG INFORMATION ERROR LOCATION = 62914DEBUG INFORMATION REG-SAVE LOCATION = 2EB6DEBUG INFORMATION PHASE OFFSET = 139 CDEBUG INFORMATION BASE REGISTER = 6257DEBUG INFORMATION REGISTER R = 64B7CDEBUG INFORMATION REGISTER R 1 = 65138DEBUG INFORMATION REGISTER R 2 = 64AADEBUG INFORMATION REGISTER R 3 = 4 8DEBUG INFORMATION REGISTER R 4 = 64AE4DEBUG INFORMATION REGISTER R 5 = 64B7CDEBUG INFORMATION REGISTER R 6 = 64B7CDEBUG INFORMATION REGISTER R 7 = 8DEBUG INFORMATION REGISTER R 8 = DEBUG INFORMATION REGISTER R 9 = 2E1ABDEBUG INFORMATION REGISTER R1 = 64 8DEBUG INFORMATION REGISTER R11 = 65 8DEBUG INFORMATION REGISTER R12 = 6257DEBUG INFORMATION REGISTER R14 = 62914DEBUG INFORMATION REGISTER R15 = 8

-DEBUG ENABLE SYSTEM,DUMP

This option is for VSE only and displays the same information as the REGoption described above. VSE PDUMP command is also issued to giveTechnical Services a SNAP dump of the control areas.

6.2 Accessing the Online Client Support System

SupportConnect is an online product support and service system available onthe Internet from Computer Associates. It contains an extensive KnowledgeBase that allows you to retrieve many types of product-related informationwith a single search. SupportConnect also provides full product downloadsand an easy-to-use Suggestion Box for you to submit enhancement ideas foryour licensed products.

The best features of CA's prior online support systems are fully integrated intoSupportConnect. These include:

Solution downloadsTechnical Support issue managementLicense key downloadsVirus signature downloads

Product-specific FAQsProduct documentation downloadsNewsgroup open forums

E-News newsletters

SupportConnect offers everything that the previous online sites(eSupport.ca.com, support.ca.com, and webtrack.ca.com) offered, and muchmore. For the differences between SupportConnect and Webtrak andeSupport, see the comparison documents that are accessible from theSupportConnect home page.

6.2.1 Requirements for Using SupportConnectWith a current version of a browser and without logging in, you have access toa considerable amount of information on the website. This includes access toFAQs, published solutions (for channel products only), compatibilities, virussignatures, news, CA user group information, and support services, and toperform general Knowledge Base searches.

For full access to all the services related to your licensed products, includingpublished solutions, license keys, newsgroups, Hyper Subscriptions, productand documentation downloads, issue management, and Suggestion Box, youmust log in. These areas require that you are a registered SupportConnectuser. You can convert your Webtrack or eSupport login and password to aSupportConnect account; just click on Convert Existing Account when you firstaccess SupportConnect.

If you enrolled at AccountConnect.ca.com, you can log into SupportConnectusing your AccountConnect digital certificate rather than entering a loginname and password. However, this works only on the PC where the digitalcertificate resides, and only if you are using Microsoft Internet Explorer 5.5 orlater. If you need to access SupportConnect from another PC, or if you areusing Netscape Navigator, you must provide a login name and password.

6.2 Accessing the Online Client Support System

6.2.2 Accessing the Technical Support Phone Services DirectoryThe Computer Associates Technical Support Phone Services Directory listseach Computer Associates product and the telephone number to call forprimary support for that product. To access the Support Phone ServicesDirectory, click on the Support Services link on the SupportConnect webpage.

6.2.3 CA-TLC: Total License CareMany Computer Associates software solutions use license keys orauthorization codes to validate your hardware configuration. If you needassistance obtaining a license key or authorization code, contact the CA-TLC:Total License Care group through SupportConnect.

6.3 Calling Computer Associates Technical Support

For further technical assistance with this product, Technical Support isavailable 24 hours a day, seven days a week. You can obtain a complete list ofComputer Associates locations and phone numbers by product atSupportConnect.ca.com at the Support Services link.

If you are unable to resolve the problem, please have the followinginformation ready before contacting Computer Associates Technical Support:

All the diagnostic information described in 6.1.1, “Collecting DiagnosticData” on page 6-4.

Product name, version number, operating system, and genlevel.

Product name and version number of any other software you suspect isinvolved.

Version level and PUTLEVEL of the operating system.

Your name, telephone number and extension (if any).

Your company name.

Your site ID.

A severity code. This is a number (from 1 to 4) that you assign to theproblem. Use the following to determine the severity of the problem:

1 a "system down" or inoperative condition

2 a suspected high-impact condition associated with the product

3 a question concerning product performance or an intermittentlow-impact condition associated with the product

4 a question concerning general product utilization or implementation

6.4 Generating a Problem Report

CAPP999E –(no number)

Once a Computer Associates Technical Support representative has determinedthat your problem requires further investigation, you can use the following togenerate a problem report.

6.4.1 CA-ACTIVATOR Problem Reporting FacilityThe CA-ACTIVATOR problem reporting facility allows you to provide adescription of the problem. It automatically produces a report on:

Your current system environmentComputer Associates product installation and maintenance informationThe product runtime options in effect

6.4.2 CAISERV UtilityThe CAISERV diagnostic facility produces a problem report for you to fill outand send in with all problem documentation.

CAISERV also produces a short report on the Computer Associates VSEproducts that you have installed. This information should also be sent to aidin solving your problem.

To invoke CAISERV, execute the CAISERV procedure in your sample JCLlibrary:

// JOB CAISERV // EXEC CAISERV / /&

Edit the JCL to your installation's standards, and submit the job.

The messages you may encounter when running CAISERV are:

CAPP999E INSUFFICIENT STORAGE TO PROCESS CAISERV

Explanation: Sufficient storage was not allocated to execute CAISERV.

User Response: Use at least 100 KB of storage for executing CAISERV.

(no number) ** PRODUCT CAISERV MODULE 'modulename' NOT ACCESSIBLE ***

Explanation: Libraries are not properly concatenated.

User Response: Review and modify the JCL. Execute CAISERV.

The CAISERV job will produce a report similar to the following to SYSPRINT:

CAISERV 1 COMPUTER ASSOCIATES PRODUCT STATUS REPORT 1/ 8/ 3 (MM/DD/YY) 9.33.25 (HH.MM.SS) PAGE 1

COMPUTER ASSOCIATES PROBLEM REPORT SHEET

(ALWAYS COMPLETE THIS AND SUBMIT IT AND THE FOLLOWING PAGES WITH ANY PROBLEM)

COMPANY NAME COMPANY ADDRESS -------------------------------------- ------------------------------- ------------------------------- ------------------------------- CONTACT NAME TELEPHONE NUMBER ------------------------- -------------------------

OPERATING SYSTEM PUT LEVEL I/O DEVICES ATTACHED UNDER VSE/ESA 6.7. ----------------- ON CPU FF21 15 3 9 ---------------------------- ---------------------------- OTHER SYSTEM SOFTWARE(VENDOR AND/OR IBM) ----------------------------------------------------------------------------

PROBLEM SEVERITY PROBLEM TYPE (CRITICAL, COSMETIC, ETC) -------------------- (INTERMITTENT, REPRODUCIBLE, ETC) ------------------

DESCRIPTION OF PROBLEM

Fill in the form completely. This information will be logged into the ComputerAssociates Technical Support system and will be tracked from the time it isreported to the time it is closed.

The last page of the problem report provides a status of the ComputerAssociates products that you have installed. In most instances, this reportincludes the product release number, genlevel, and installation options.

The following is a sample Unicenter CA-Scheduler report:

CAISERV 1 COMPUTER ASSOCIATES PRODUCT STATUS REPORT 1/ 8/ 3 (MM/DD/YY) 12.14. 5 (HH.MM.SS) PAGE 1 CA SCHEDULER/VSE VERSION/LEVEL:VM=7.3 GENERATION LEVEL:96 5SH73

GLOBAL FLAGS: XECBS ADDRESS : CDADB8 MONITOR TERMINATING : NO ADDR OF ANCHOR TABLE : CE6EB JOB WAIT--RESOURCES : NO FIRST PCB ADDRESS : CE65E8 JOB WAIT--TIME RSRC : NO FIRST SCB ADDRESS : 6C417 JOB WAIT--GBL VAR : YES COMMON AREA ADDRESS : 538

$DYNNM = $DYN SCHEDULE PREFIX FOR DYNAMICALLY ADDED JOBSABNMSG = (MAILBOX) ABEND MESSAGE USERID LISTABNROUT = (MAILBOX) ABEND MESSAGE ROUTE TO NODE LISTAUDIT = YES CA-AUDIT LOGGING SUPPORTAUDTSEC = YES CAICUI SECURITY CHECKINGAUDTSHT = NO CA-AUDIT IS SHUTDOWN BY SCHEDULERAUTOINT = NO MONITOR INIT WHEN VSE/POWER ACTIVATEDAUTOTIM = 8 MONITOR SCAN TIME(HHMM) FOR SCHEDULE SELECTIONAUTRPLY = YES AUTOMATIC CONSOLE REPLY SUPPORTBACKOUT = (R,8) BACKOUT OPTION (CHARACTER,POSITION)CICS = UPDATE ONLINE MONITOR ACCESS ALLOWEDCMS = YES VM/CMS SUPPORT OPTIONCMSFT = (DOSJCL) VM/CMS JCL FILETYPECMSMXWT = 3 CMS SCHD TRANSACTION MAX REPLY WAIT TIME(SECONDS)CMSRDRC = S VM VIRTUAL READER CLASSCMSRSYS = 13 VM LOGICAL READER DEVICE ADDRESSCONDNAM = GACLIB CONDOR LIBRARY FILE NAMECONDOR = YES CONDOR LIBRARY SUPPORTCONSYS = 3 CONDOR PROGRAMMER LOGICAL UNITCPUST = 4 CPU STATION IDCRILIMT = CRITERIA LINES ADDITIONAL MAX LIMITDATETAB = ADATETAB DEFAULT DATE TABLE NAMEDCMBKNM = CAIJBCM DOCUMENTATION LIB BACKUP TAPE NAMEDCMBUFN = 4 DOCUMENTATION LIBRARY BUFFERS NO.DCMCISZ = 1 24 DOCUMENTATION LIBRARY CONTROL INTERVAL SIZEDCMNAME = CAIJDCM DOCUMENTATION LIBRARY NAMEDEADLST = Y CTLSPOOL VSE/POWER DEFAULT LST CLASSDJOB = 3 MAXIMUM NO. OF DAILY SCHEDULED JOBSDOC = YES DOCUMENTATION LIBRARY SUPPORTDRIVER = YES CA-DRIVER PARAMETER SUBSTITUTIONDRVBKNM = CAIJBRV CA-DRIVER LIBRARY BACKUP TAPE NAMEDRVBUFN = 4 CA-DRIVER LIBRARY BUFFERS NO.DRVCISZ = 1 24 CA-DRIVER LIBRARY CONTROL INTERVAL SIZEDRVNAME = CAIJDRV CA-DRIVER LIBRARY NAMEDSN = YES DATA SET INFORMATION COLLECTIONDYNAM = YES CA-DYNAM INSTALLEDEDTATC = 73 EDITOR ATTRIBUTES COLUMNEDTHCHR = H EDITOR HIGHLIGHT LINE ATTRIBUTE CODEEDTPCHR = P EDITOR PROTECT LINE ATTRIBUTE CODEEDTPHCH = F EDITOR PROTECT/HIGHLIGHT LINE ATTRIBUTE CODEENDMSG = (MAILBOX) END MESSAGE USERID LISTENDROUT = END MESSAGE ROUTE TO NODE LISTERRMSG = (MAILBOX) ERROR MESSAGE USERID LISTERRROUT = ERROR MESSAGE ROUTE TO NODE LISTFALMSG = (MAILBOX) FAIL MESSAGE USERID LISTFALROUT = FAIL MESSAGE ROUTE TO NODE LISTICCF = YES ICCF LIBRARY SUPPORTICCFCOM = 13 ICCF SYSTEM COMMON LIBRARY NUMBERICCFJOB = 39 ICCF JOB SUBMISSION LIBRARY NUMBERIMBED = ++INCLUDE CONSTANT FOR CMS IMBEDDED FILESINSRDRV = YES POWER GEN INCLUDE DRIVER RDR EXITINSROUT = YES NODE ID CONTROL CARD INSERTED IN JCLINSRSYS = YES SYSID CONTROL CARD INSERTED IN JCLINTMSG = (MAILBOX) INTER MESSAGE USERID LISTINTROUT = INTER MESSAGE ROUTE TO NODE LIST

6.5 Product Versions and Maintenance

Customers are requested to operate only under currently supported versions ofthe product.

Customers with current maintenance agreements also receive ongoingmaintenance. When a new version of the system is available, a notice is sentto all current customers.

6.6 Requesting Enhancements

Computer Associates welcomes your suggestions for product enhancements.All suggestions are considered and acknowledged. You can use either of twomethods to request enhancements:

Enter your request through the Suggestion Box at SupportConnect, theComputer Associates web-based, interactive support system.

Contact your Account Manager who will initiate the request for you.

Appendix A. Standard Product Installation Detail

This appendix covers the following topics:

Initial Product Installation

Subsequent Computer Associates Product Installation

Migration of Computer Associates Products into Production

MSHP Installation JCL Customization

Appendix A. Standard Product Installation Detail A-1

A.1 Subsequent Computer Associates Product Installation

CAINSTB2: CAINSTB2 is used to install a product into test libraries to allowinstallation verification and testing prior to migration into the productionlibraries.

After the product tape has been successfully installed, proceed with the stepsin this Installation Guide.

CAINSTB2 performs the following functions:

1. Open SYSPCH using the extents of the history file. This is a precautionarymeasure to avoid errors when the history file extent resides on a newlydefined VM minidisk.

2. Create the Computer Associates installation libraries and history file forthe product tape being installed.

3. Install the product tape to the installation history file and libraries.

CAINSTB2 Execution

A-2 Unicenter CA-Driver for VSE Installation Guide

A.2 Migration of Computer Associates Products into Production

A.2 Migration of Computer Associates Products intoProduction

CAINSTB3: CAINSTB3 is used to migrate a product into the productionlibraries and history file when a product was installed to an installation libraryand history file. This step is executed only after product installation,customization, verification and testing are complete.

The sample JCL members are located on the restored source library in the Zsublibrary.

After this process is complete, the installation libraries and history file can bedeleted.

CAINSTB3 performs the following function:

CAINSTB3 merges the tested product or products into the production librariesand history file.

CAINSTB3 Execution

A.3 MSHP Installation JCL Customization

The MSHP installation JCL contains variables that must be modified to tailorthe JCL to your specific environment. The variables are specified in aworksheet contained in this Installation Guide. These variables will bemanually changed using a user editor.

Variable symbols present in the MSHP installation JCL follow:

FOR JOB CAINSTB2 and CAINSTB3

Variable Description

@CUSTNME Customer name used to personalize the MSHP historyfiles.

@CUSTADD Customer address used to personalize the MSHP historyfiles.

@CUSTPHN Customer phone number used to personalize the MSHPhistory files.

@PROGNME Customer programmer name used to personalize thehistory files.

@HISTVOL Volume serial number where the Computer Associatesproduction history file will reside.

@HISTREL Relative track or block where the Computer Associatesproduction history file is to begin.

@HISTEXT Number of tracks or blocks to be allocated to theComputer Associates production history file.

@INSTVOL Volume serial number where the temporary installationhistory file will reside.

@INSTREL Relative track or block where the temporary installationhistory file is to begin.

@INSTEXT Number of tracks or blocks to be allocated to thetemporary installation history file.

@DLIBVOL Volume serial number where the Computer Associatesproduction library will reside.

@DLIBREL Relative track or block where the Computer Associatesproduction library is to begin.

@DLIBEXT Number of tracks or blocks to be allocated to theComputer Associates production library.

@TAPECUU The device address where the product tape will bemounted.

FOR JOB CAINSTB2

@CUSTNME Customer name used to personalize the MSHP historyfiles.

@CUSTADD Customer address used to personalize the MSHP historyfiles.

@CUSTPHN Customer phone number used to personalize the MSHPhistory files.

@PROGNME Customer programmer name used to personalize thehistory files.

@INSTVOL Volume serial number where the Computer Associatesproduct installation history file will reside.

@INSTREL Relative track or block where the Computer Associatesproduct installation history file is to begin.

@INSTEXT Number of tracks or blocks to be allocated to theComputer Associates product installation history file.

@ILIBVOL Volume serial number where the Computer Associatesproduct installation library will reside.

@ILIBREL Relative track or block where the Computer Associatesproduct installation library is to begin.

@ILIBEXT Number of tracks or blocks to be allocated to theComputer Associates product installation library.

@PRODCDE Product code for the product tape to be installed. Forexample, YD540 for BrightStor CA-Dynam/T TapeManagement for VSE version 5.4.

@PRODUCT Product name. For example DYNAM for the BrightStorCA-Dynam/T Tape Management for VSE product.

FOR JOB CAINSTB3

@HISTVOL Volume serial number where the Computer Associatesproduction history file will reside.

@HISTREL Relative track or block where the Computer Associatesproduction history file is to begin.

@HISTEXT Number of tracks or blocks to be allocated to theComputer Associates production history file.

@DLIBVOL Volume serial # where the Computer Associatesproduction library will reside.

@INSTVOL Volume serial # where the Computer Associates productinstallation history file will reside.

@INSTREL Relative track or block where the Computer Associatesproduct installation history file is to begin.

@INSTEXT Number of tracks or blocks to be allocated to theComputer Associates product installation history file.

@ILIBVOL Volume serial # where the Computer Associates productinstallation library will reside.

@PRODCDE Product code for the product tape to be installed. Forexample, YD540 for BrightStor CA-Dynam/T TapeManagement for VSE version 5.4.

Appendix B. SLI and VSE Procedure Conversion

The supplied program CARUCNVT processes a SYSPCH tape created by theprogram SSERV for POWER SLI books, or by PSERV for DOS/VSEprocedures. It also outputs a tape that can be used as input to CARUTIL.CARUCNVT reads the input tape using SYS004 and creates the the outputtape using SYS005. This output tape may be processed by CARUTIL in orderto actually catalog the converted procedures.

Nested SLI statements and partition dependent SLI names ($$) must be dealtwith manually since Unicenter CA-Driver for VSE uses &P for partitiondependent procedure names rather than $$.

The following job stream demonstrates the use of CARUCNVT.

// JOB CARCNVT// ASSGN SYSPCH,X'28 '// MTC REW,SYSPCH// EXEC SSERV PUNCH P.ALL/// MTC WTM,SYSPCH,2// MTC REW,SYSPCH// RESET SYSPCH// ASSGN SYS 4,X'28 '// ASSGN SYS 5,X'281'// TLBL TAPOUT,'ANY NAME'// EXEC CARUCNVT,SIZE=128K/// ASSGN SYSIPT,X'281'// EXEC CARUTIL,SIZE=128K//&

Appendix B. SLI and VSE Procedure Conversion B-1

Special Characters-DEBUG 6-5

AAccountConnect 6-8Activating Unicenter CA-Driver for VSE 4-17ASI PROC 4-16Assembling

generation macro 4-13authorization codes, obtaining 6-9AUTOINT 4-13

BBrightStor CA-Dynam/T Tape Management for

VSE 2-5

CCA Products 4-20CA-TCC (CA Total Client Care)

See SupportConnectCA-TLC (CA Total License Care) 6-9CACMSALT 5-8CACMSGEN 5-6CAINSTB2 4-3CAINSTB3 4-3CAJAGENA 4-13CARUCNVT B-1CARUTIL commands

-DEBUG 6-5Changing ASI procedure 4-16Checklist

VM/CMS installation steps 5-2VSE installation steps 4-4

CICSrequirements 2-2tables 4-14

Commoncomponents

CMS 5-9Unicenter CA-Driver for VSE 4-8

libraries 4-8Conversion instructions 4-7CPUs, multiple 2-3

devices 2-3space required 2-3

Data sets 2-3Distribution tape 4-12Documentation 3-2DRIV modify exec 5-8

EeSupport

See SupportConnecteTrust CA-Top Secret Security for VSE. 2-5

FFiles

for VM/CMS component 5-4on installation tape 3-3

Full-screen transaction 5-8

GGeneration macros 4-13GETVIS requirements for POWER 2-5

HHardware requirements 2-3

Index X-1

HELP database 4-18History files 1-3, 4-1

IInitialize databases 4-17Installation

checklistVM/CMS 5-2VSE 4-4

conversion 4-7JCL 4-1, 4-3libraries 4-1materials 3-1online transaction 4-14overview 1-1requirements 2-2standard

JCL 4-3sequence 4-2

steps 4-6VM/CMS 5-3VSE 4-1

tape 3-3Unicenter CA-Driver for VSE options 4-13verification procedure 1-1worksheet 4-8

Internet, Computer Associates site 6-8IPL 4-17

CAINSTA2 4-12CAINSTA3 4-20CAINSTB2 4-12CAINSTB3 4-20installation 4-3members 4-3

LLibraries

common 4-8installation 4-1production 4-1Unicenter CA-Driver for VSE 1-3VSE 1-3

license keys, obtaining 6-9Loading HELP database 4-18

MMigration of products into production 4-20Moving CMS component 5-9MSHP 1-3, 3-3, 4-1, 4-8Multi-CPUs 2-3

OOnline transaction 4-14Operating systems 2-2Options for Unicenter CA-Driver for VSE 4-10

PPCT entries 4-14Phone Services Directory 6-9POWER GETVIS requirements 2-5PPT entries 4-14Product

distribution 1-2options 4-10

ProductionCAI Products 4-20libraries 4-1

RReinstallation 4-7Requirements

CICS 2-2conversion 4-7hardware 2-3installation 2-3PCT 4-14VM/CMS 5-3VSE 4-6

SSDL/SVA requirements 4-16SLI B-1Space requirements 2-3Standard

installation JCL 4-3Product Installation Worksheet 4-9, 4-10

StarTCCSee SupportConnect

Storage requirements 2-5Support Phone Services Directory 6-9SupportConnect 6-8

X-2 Unicenter CA-Driver for VSE Installation Guide

System Adapter compatibility 2-5System overview 2-2

TTechnical Support Phone Services Directory 6-9Total License Care (CA-TLC) 6-9

UUnicenter CA-Driver for VSE options 4-10Upgrading 4-7

VVM/CMS component

installation checklist 5-2requirements 5-3

VSEinstallation

checklist 4-4steps 4-1

libraries 1-3procedure conversion B-1

WWorksheet, installation 4-8

Index X-3

Unicenter CA-Driver Job Management for VSE Installation · PDF fileSystem Requirements ......

Documents

IBM IPv6/VSE 1.2 What's New? · IBM IPv6/VSE 1.2 Reminder ... While the product is named IPv6/VSE, the product supports both IPv4 and IPv6 communications. IPv6/VSE provides a full-function

z/VSE Connectors Update Ingo Franzki, IBM©2012 IBM Corporation IBM System z –Live Virtual Class 4 z/VSE V5.1: VSE Script Connector Overview Part of the z/VSE Connectors since z/VSE

VSE Investor Overview - content.stockpr.comcontent.stockpr.com/vsecorp/db/Presentations/523/pdf/VSE+Q4+FY14+IR... · VSE Investor Overview & 10-Year Retrospective FY 2014 Christine

Unicenter NSM r11 Classic 2D Map Basic Scalability Tests

WorldView Tunneling (WVDBT) Insights for Unicenter NSM r11.1

AppManager Connector for CA Unicenter NSM

Unicenter AutoSys Job Management - Write Trends

Think Outside The Hive...BURT'S BEES coq BEE VSE . coq BEE VSE . BEE coq BEE VSE . coq BEE VSE . coq BEE VSE . edËÎ EAST CHILDREN'S INITIATIVE coq BEE VSE . coq BEE VSE . coq BEE

Unicenter CA-Scheduler Job Management for VSE … CA-Scheduler Job Management for VSE . This documentation and related computer software program (hereinafter referred to as the “Documentation”)

The Color Run 2016 | Unicenter & Portal Rosario

Unicenter AutoSys Job Management for UNIX User Guide

Unicenter Service Desk Itil User Guide3758

Unicenter AutoSys 4.5 Job Management for Windows User Guide

Local control unit DLP-VSE- DLP-VSE--DP DLP-VSE--ASI · 2020-03-31 · Festo P.BE-DLP-VSE-... en0206a 1-7 1.2.3 Housingblockwith integrated air supply The housing block isformed ofa

Unicenter NSM Tips & Tricks Release r11.x

CA IT Process Automation Manager - support.ca.com · Management User Guide and the Unicenter AutoSys Job Management Reference Guide. Terminology 10 Unicenter AutoSys JM Connector

Unicenter AutoSys Job Management - Cluster

VSE/POWER, all the news since z/VSE 4.2

Unicenter CA-Explore Performance Management for CICS ... · Getting Started Guide Release 7.0 K01098-1E Unicenter CA-Explore Performance Management for CICS

Unicenter CA-Sort for VSE · and optimizes virtual storage management. ... CA-Sort in any programming language. ... (phases). Each part is loaded from the