CA Dynam For VSE Installation

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

CA Product References
This document references the following CA products:
CA Dynam®/T Tape Management for z/VSE (CA Dynam/T)
CA Dynam®/D Disk Management for z/VSE (CA Dynam/D)
CA Dynam®/FI File Independence (CA Dynam/FI)
CA TLMS Tape Management (CA TLMS)
CA Common Infrastructure Services for z/VSE (CA CIS)

CA Earl™ (CA Earl)
CA ACF2™ for z/VSE (CA ACF2)
CA Top Secret® for z/VSE (CA Top Secret)
CA 1® MVS (CA 1)
Contact CA
Contact Technical Support
For online technical assistance and a complete list of locations, primary service
hours, and telephone numbers, contact Technical Support at
http://ca.com/support.
Provide Feedback
If you have comments or questions about CA product documentation, you can

send a message to techpubs@ca.com.
If you would like to provide feedback about CA product documentation, please

complete our short customer survey, which is also available on the CA Support
website.
Contents
Chapter 1: Introduction
CA Dynam/T Tape Management for VSE........................................................ 1-1
CA Dynam/D Disk Management for VSE ........................................................ 1-1
CA Dynam/FI File Independence for VSE ....................................................... 1-1
Product Names ............................................................................... 1-2
Chapter 2: Installation Process

Product Distribution........................................................................... 2-1
Using MSHP .................................................................................. 2-1
Chapter 3: System Requirements

System Adapter Requirements ................................................................ 3-1
Supervisor Requirements ..................................................................... 3-1
Storage Requirements ........................................................................ 3-2
System Directory List (SDL) ............................................................... 3-3
Initialization Requirements .................................................................... 3-4
Catalog and Audit Files ........................................................................ 3-6
Space Requirements .......................................................................... 3-7
Worksheet for Estimating Catalog File Size ................................................. 3-7
Estimated DASD Space Requirements for New Users ........................................ 3-9
CICS Requirements .......................................................................... 3-10
CICS Partition GETVIS Requirements ...................................................... 3-10
Chapter 4: Installation Materials

CA Dynam ................................................................................... 4-1
CA Dynam/T DYNVM Extension ................................................................ 4-1
CA Earl Report Program ....................................................................... 4-2
CA Common Infrastructure Services ........................................................... 4-2
Product Installation Tape ...................................................................... 4-2
CA Dynam Pregenerated System .............................................................. 4-3
Contents v
Chapter 5: Installation Steps
Standard Installation JCL ..................................................................... 5-3
Special Upgrade Considerations ............................................................... 5-4
Installation Overview Checklist ................................................................ 5-4
Step 1. Review System Requirements ......................................................... 5-5
Task 1A. Verify CA Dynam Family System Requirements .................................... 5-5
Task 1B. Review Installation Materials ..................................................... 5-6
Step 2. Remove Prior Release of Product ...................................................... 5-6
Step 3. Complete the Installation Worksheet ................................................... 5-6
Libraries and MSHP Install ................................................................ 5-7
Step 4. Install CA CIS for VSE ................................................................ 5-8
Step 5. Install CA Dynam ..................................................................... 5-9
Step 6. Modify Source Books .................................................................. 5-9
Task 6A. Punch Sample JCL ............................................................... 5-9
Task 6B. Update Skeleton JCL ............................................................ 5-11
Step 7. Update ASI Procedures .............................................................. 5-11
Procedure ............................................................................... 5-11
Step 8. Update CICS Tables.................................................................. 5-15
Task 8A. Update Program Processing Table (PPT) .......................................... 5-15
Task 8B. Migrate PPT to CICS DFHCSD.................................................... 5-15
Task 8C. Define CA Dynam Online Panels in CICS TS ...................................... 5-15
Step 9. Initialize CAICUI VSAM Database ..................................................... 5-16
Sample JCL ............................................................................. 5-17
Step 10. CAIHELP Data Set Processing ....................................................... 5-18
Task 10A. Define and Load CAIHELP Data Set ............................................. 5-18
Task 10B. Update the CAIHELP Data Set for CA Dynam .................................... 5-18
Step 11. Load CA Dynam Messages .......................................................... 5-19
Step 12. IPL the System ..................................................................... 5-19
Step 13. Data Set Initialization/Installation Verification ........................................ 5-20
Step 14. Conversion Tasks ................................................................... 5-20
Step 15. Migration of CA Products into Production ............................................. 5-20
Step 16. Install the DYNVM Extension ........................................................ 5-21
Step 17. Save All Materials and Output ....................................................... 5-21
Chapter 6: VM Installation Steps

Software Requirements ....................................................................... 6-1
DASD Space Requirements ................................................................... 6-1
Installation Overview Checklist ................................................................ 6-1
Step 1. Define Service Machine User ID ....................................................... 6-2
Step 2. Load Tape............................................................................ 6-3
vi Installation Guide
Step 3. Tailor DYNLINK EXEC .................................................................. 6-3
Step 4. Tailor TASKMAN System Profile ........................................................ 6-3
Step 5. Tailor TASKMAN CP Commands ........................................................ 6-4
Step 6. Tailor TASKMAN CMS Commands....................................................... 6-4
Step 7. Define System Adapter CPU Profile Table ............................................... 6-5
Step 8. Tailor System Adapter Options ......................................................... 6-5
Step 9. Tailor CAICMS SYSPROF for Lock File ................................................... 6-6
Step 10. Tailor DYNVM System Profile.......................................................... 6-7
Step 11. Generate DYNVM Product Control Table ............................................... 6-8
Step 12. Define DTPOOL Macro (Optional) ..................................................... 6-14
Step 13. Define DTLOCK Macro (Optional) ..................................................... 6-15
Step 14. Create XSYSTEM Macro (Optional) ................................................... 6-16
Sample Macro ........................................................................... 6-17
Step 15. Run TQINST EXEC .................................................................. 6-19
Appendix A: Special Instructions for 8K COMPOOL Records

Applicability to Installation .................................................................... A-1
COMPOOL Record Lengths..................................................................... A-1
Running CA Dynam with Special Fixes ......................................................... A-2
Appendix B: Accessing and Using Sample JCL

Extract the Product Installation JCL ............................................................ B-1
Extract from a Physical Tape: CAINSTB0 ................................................... B-1
Extract from an ESD File: CAINSTC0 ....................................................... B-2
Install the CA Product ......................................................................... B-3
Install from a Physical Tape: CAINSTB2 .................................................... B-3
Install from an ESD File: CAINSTC2 ........................................................ B-5
Migrate the CA Product into Production: CAINSTB3 ............................................. B-6
Perform a Direct CA Product Installation ....................................................... B-7
Install Directly from a Physical Tape: CAINSTQ4 ............................................ B-8
Install Directly from an ESD File: CAINSTC4 ................................................ B-8
Index
Contents vii
Chapter 1: Introduction
CA Dynam for VSE is a collection of software products designed to provide a
comprehensive file management facility for your data center. CA Dynam for
VSE is comprised of three products that work together to efficiently manage
tape and disk files and provide file independence.
CA Dynam/T Tape Management for VSE

CA Dynam/T helps you manage your tape library in the following ways:
Automatically controlling tape data set usage and retention
Preventing active tape data sets from being scratched
Controlling remote site tape movement and retention
CA Dynam/D Disk Management for VSE

CA Dynam/D efficiently manages your disk data sets in the following ways:
Allocating primary and secondary disk space
Permitting automatic space release
Protecting disk data sets from overlapping and deleting active files
Providing device independence for automatic conversion to new DASD

devices
CA Dynam/FI File Independence for VSE

CA Dynam/FI allows files to be switched from most sequential media to either
tape or disk in the following ways:
Dynamically reblocking files for specified devices
Dynamically changing record formats
Simulating unit-record to multi-record device types, such as card reader to

tape
Chapter 1: Introduction 1–1

Product Names
Additionally, the CA Dynam Catalog and Audit Trail files may be shared by all
three products. The Catalog file is required by CA Dynam/T and is used to
define and control data sets. The Audit Trail file records data set activity and
provides for disaster recovery.
Product Names
Throughout this guide and documentation set, all comments that refer to the
combined CA Dynam system apply equally to each of the three products,
regardless of their individual or combined installation. Individually, the
products are referred to by their commonly known names: CA Dynam/T, CA
Dynam/D, and CA Dynam/FI. The family of products is referred to as CA
Dynam.
1–2 Installation Guide

Chapter 2: Installation Process
CA Dynam is a family of products consisting of CA Dynam/D, CA Dynam/T and
CA Dynam/FI. This guide provides the steps required to install all components
of the CA Dynam family whether purchased individually or together.
This technique allows flexibility as follows:
The installation process has been divided into operational units called
steps. Each step completes an identifiable unit of the installation process
such as "Complete the Installation Worksheet" or "Modify Source Books."
Each step is then divided into tasks. Each task is applicable to either all
possible installation configurations or a subset of the possible installation
configurations.
Each step has an introductory paragraph describing the purpose of the

step and which components are affected by the tasks contained within the
step.
This chapter describes the installation process in general terms. The remainder
of this guide contains detailed information and instructions needed to
accomplish a successful installation. This is achieved when all components of
the product are installed and successfully tested with the supplied Installation
Verification Procedure.
Product Distribution
The machine-readable program materials required for installation are
distributed as a single, unlabeled, multifile installation tape in IBM Maintain
System History Program (MSHP) BACKUP format. This can either be a physical
tape, or a file distributed through electronic delivery. In either case, the layout
of the “tape” is the same. One tape unit is required to install the product.
The "Installation Materials" chapter provides a detailed description of the tape

format and contents.
Using MSHP
MSHP is used to perform product installation and maintenance. MSHP provides
the ability to control these activities in a consistent manner. This format also
provides an installation mechanism that systems programmers use to maintain
the VSE operating system.
Chapter 2: Installation Process 2–1

Using MSHP
MSHP is used to perform the installation and maintenance of CA Dynam for

VSE in the same way as the operating system is installed and maintained.
When using MSHP to install a product, a MSHP History File is required to
archive product information such as product identification and library
residence. The History File is subsequently used during maintenance
application for product and library identification and for archival of
maintenance information.

Chapter 3: System Requirements
The CA Dynam file management system is composed of several components
that perform various functions. Three of these components relate to the
external use of the system and may be purchased separately as individual
software packages or together as the CA Dynam integrated file management
system. These three components are:
CA Dynam/T—Tape Management System
CA Dynam/D—Disk Management System
CA Dynam/FI—File Independence System
Whether these components are purchased individually or as an integrated

system, the majority of processing is performed by internal components that
are common to all of the systems.
In the discussion that follows, all comments that refer to the combined
CA Dynam system apply equally to each of the three external components
(CA Dynam/T, CA Dynam/D and CA Dynam/FI) if installed separately or in
combination.
System Adapter Requirements

CA Dynam r7.1 requires System Adapter, r6.1 that can be found on r1.4 of
CA CIS.
Supervisor Requirements
CA Dynam r7.1 can be used on any VSE system currently supported by IBM.
CA Dynam has no specific supervisor generation requirements.
To use the CAICUI portion that has been added to CA Dynam, see CA CIS
Getting Started for specifics on CAICUI system requirements.
Chapter 3: System Requirements 3–1

Storage Requirements
The modules that comprise the runtime portion of the CA Dynam system
reside in the system GETVIS portion of the shared virtual area (SVA).
The following are the minimum storage requirements for the CA Dynam
components. An additional cushion of 50K is strongly recommended.
Component Minimum Requirement
Common Functions 16K - 24K
CA Dynam/D 100K
CA Dynam/T 119K
CA Dynam/FI 40K
CAISPI 0K
However, when running the entire CA Dynam family (including all of the above
components), due to overlapping code, the total storage required is only 360K.
If you have other CA products, see the guides for those products for their
specific storage requirements.
Important! Several CA products use the System Adapter, Catalog

Management and common functions. It is not necessary to duplicate storage
needs for multiple products that use the same components.
As an alternative, the modules may be loaded into the SVA. Copybooks

(.z books) are provided in the sublib for the following components:
.Z Member in Sublib Component
CAIYDDYT CA Dynam/T
CAIYDIXV Index VTOC
CAIYDDYD CA Dynam/D
CAIYDDYC CA Dynam Common Code
CAIYDDYF CA Dynam/FI

System Directory List (SDL)
CA Dynam requires no phases to be resident in the shared virtual area itself,

and only minimal system directory list entries. For better performance, and
proper sequence searching of private libraries, the following should be added
to the SET SDL statement preceding initialization of the CA Dynam system in
the ASI PROC:
$$BDYT$$,MOVE CA DYNAM/T Interception Transient (2K)

$$BDYD$$,MOVE CA DYNAM/D Interception Transient (2K)
$$BDYF$X,MOVE CA DYNAM/FI Interception Transient (2K)
CAFNVDAA,SVA CA DYNAM/FI VCKD Support (Optional) (8K)
XPR$CPIT,SVA CA IUCV Support VAE Mode
Only (Optional) (256 bytes)
The LIBDEF for the CA Dynam library must be issued before the SET SDL in
order for the phases to be located.
Increase the PSIZE parameter by a minimum of 2K to a maximum of 18K to

accommodate the system transients which are to be loaded there as ',MOVE',
and to accommodate the optional SVA-resident phases. Individual storage
sizes are shown above.
Ensure that SIZE commands are coded in the ASI PROC to allocate standard
partition GETVIS of greater than the IBM default of 48K to each partition. The
48K reserved for use by IBM components will become exhausted if a program
is run which opens and closes many files in the same job step and no size
parameter is present. It is recommended that 128K of partition GETVIS be
specified. This is accomplished by entering a SIZE command specifying, for
each partition, a memory size equal to that partition's virtual size minus 128K.
For example, if the virtual sizes of a 4-partition system are as follows:
F1=2048K
F2=4096K
F3=640K
BG=1024K
The proper size command would be as follows:
SIZE F1=1920K,F2=3968K,F3=512K,BG=896K
CA Dynam provides a job control exit which enhances the existing TLBL and
DLBL statements by allowing CA Dynam options to be specified. The job exit
parses all TLBL and DLBL statements and removes any CA Dynam options
(specified within the file-id field) before passing the labels to job control. If any
CA Dynam options are found, an option block is built for later access by the
individual CA Dynam products. Therefore all labels with CA Dynam options
must be added to STDLABEL, PARSTD or USRLABEL after CA Dynam is
initialized.

Initialization Requirements
The CA Dynam job exit will become active the first time job control is reloaded
into each partition following CA Dynam initialization. Job control is loaded into
the partition whenever a program terminates. At that time, job control
determines the address of $JOBEXIT. For subsequent job control statements,
until the next program is executed in the partition (causing job control to be
reloaded), $JOBEXIT is entered directly using a branch. If CA Dynam is
initialized while other partitions are already active, the CA Dynam job control
exit will not receive control for job control statements processed by the other
partitions until job control has been reloaded into each partition. Therefore it is
recommended that CA Dynam be initialized before POWER to avoid job control
processing before the CA Dynam job exit is activated.
By default, the job exit is CDLOAD’ed into the partition at job control time. It
is possible to load the CA Dynam job exit into the SVA thereby avoiding the
overhead of loading the job exit into the partition. The job exit will require
approximately 15K of SVA storage. In order to do this, the following should be
added to the SET SDL statement preceding initialization of the CA Dynam
system in the ASI PROC:
CADCJXTA,SVA CA Dynam COMMON JOB EXIT
Important! If the CA Dynam job exit, CADCJXTA, is not loaded into the SVA,
then the library containing CADCJXTA must be on the LIBDEF search chain
whenever a statement containing a CA Dynam option is processed.
CA Dynam initialization is performed after IPL by a startup program. This
program (CASAUTIL) should be executed from the Automatic System
Initialization (ASI) procedure. LIBDEFs will be required before the system can
be started. CASAUTIL should be executed as early in the procedure as possible
after LIBDEFs have been issued. No other partitions should be active while
CA Dynam is being initialized.
Before executing CASAUTIL, label and extent information for the CA Dynam
Catalog file and the CA Dynam Audit data set (if Audit support has been
generated) should be cataloged into the system standard label area.
The CA Dynam activation procedure dynamically locates the required 'hooks'

within the supervisor. For this reason, CA Dynam must have access to the
native IBM supervisor during startup. It is recommended that CA Dynam be
activated before other software products that are installed in the system to
assure that no other dynamic hooks interfere with CA Dynam initialization. A
two-stage startup procedure is available, if required, to allow other software
products with the same requirement to be started along with CA Dynam. For
more information, see the description of CASAUTIL in the Programming Guide.

CA Dynam makes use of a supervisor call code, SVC 255 by default, for
internal communications. The SVC code may be altered using the CAICUI
transaction if a conflict exists, but for the purpose of installation and
verification prior to customization, disabling of conflicting software is
recommended.
The following restrictions exist when using a component of CA Dynam in

conjunction with components of other file management systems:
No other file management system can be used to provide tape/disk file

independence in conjunction with any component of CA Dynam, since
CA Dynam always sees the 'OPEN' for the file first. If file independence is
required, contact CA for information about CA Dynam/FI.
If another system is to be used which performs a 'soft' rename of an IBM

component by modifying the SDL entry for the component during its
startup procedure, CASAUTIL should be executed after the other system
has been activated.
To support the // ASSGN SYSXXX, DUMMY feature of TDYNASN and the S:nnn
TLBL option CA Dynam/T requires that the appropriate dummy devices must
be added at IPL and left in DVCDN status. The dummy devices should be
added as 3420-type tape devices. The default device addresses are X'7F0'
through X'7FF'. You can change them in the Dynam/T option record in the
CAICUI data set.
To build five dummy devices for the use of TDYNASN, use the following IPL
command:
ADD 7F0:7F4,3420T9
Also use the following commands later in the ASI PROC:
DVCDN 7F0
DVCDN 7F1
DVCDN 7F2
DVCDN 7F3
DVCDN 7F4
Place these commands in the ASI procedure for the BG partition.

Catalog and Audit Files
Catalog and Audit Files

The Catalog and Audit files are highly active system files that are accessed
whenever a data set is opened or closed. The Catalog file is referred to by the
filename 'CAICATL', and the Audit data set by the filename 'CAIAUDT'. You can
use any logical unit to access the files. However, the unit you choose must be
permanently assigned to the correct DASD device in all partitions at all times.
'SYSREC' and 'SYSCAT' are recommended. Programmer logical units can be
used, but care must be taken that they are reserved for CA Dynam use only
and will never be unassigned or reassigned. Failure to observe this can result
in Catalog or Audit file abnormalities.
Place the Catalog and Audit files on the fastest separate DASD devices
available—fixed-head, if possible—to optimize performance. We do not
recommend placing the Catalog and Audit files on a DASD device with other
highly active files, especially files used by a teleprocessing system: the
amount of required I/O during OPEN/CLOSE processing is not large, but
degradation can occur when running the batch utilities (such as the scratch
and reporting functions).
Catalog and Audit DLBL and EXTENT information should be cataloged in the
system standard label area. The Catalog and Audit file labels must contain
their actual extent information; they must not be allocated by a dynamic disk
space management system. They need not be aligned on cylinder boundaries.
You might use the following job to put the Audit and Catalog data sets in the
standard label area:
// JOB LOAD STANDARD LABELS

// OPTION STDLABEL
// DLBL CAICATL,'CA DYNAM.CATALOG.FILE',2099/365,SD
// EXTENT SYSCAT,SYSCAT,1,0,5700,57
// DLBL CAIAUDT,'CA DYNAM.AUDIT.FILE',2099/365,SD
// EXTENT SYSREC,SYSREC,1,0,1900,114
.
. OTHER LABEL INFORMATION
.
.
/*
/&
When the Catalog and Audit files are to reside on an FBA device, the beginning
block number (PBN) for each extent must be evenly divisible by 8.
The system logical unit, SYSRES, may not be used for the CA Dynam Catalog
or Audit files. The files may reside on the same physical volume as the system
residence area, but another logical unit must access them. This is an
undocumented IBM restriction.

Space Requirements
Space Requirements
CA Dynam requires permanent disk space for the Catalog file. If audit support
is to be used, disk space must also be allocated to the Audit file. Use the
following worksheet to estimate the size of the Catalog file that will be
required.
Worksheet for Estimating Catalog File Size
Enter the approximate values as indicated on each line, and perform the
calculations below:
Number of data sets (tape and disk) to =_________=A

be controlled
Number of tape volumes to be =_________=B

controlled
Number of generations of data sets to =_________=C

be controlled
Number of sort key records to be =_________=D

defined
Substitute estimated values for A,B, etc., in the following equation:
(A/1.2) + (B/5) + (C/2) + (D/16) + 100 = ____=NUMBER OF BLOCKS
"NUMBER OF BLOCKS" is the total number of control intervals, or blocks,

which the CA Dynam Catalog will require if the default control interval length
(1024 bytes) is used.
A user can modify this value by specifying the CISIZE parameter on the
DYNCAT INITIAL or RESTORE functions when a new Catalog is created. For
example, the following initializes the Catalog to a CISIZE of 2048:
// EXEC DYNCAT,SIZE=128K
INITIAL DATASETS=500 SHARE=NO CISIZE=2048
/*
/&
The several record types stored in the Catalog are variable-length records
ranging in size from 56 to 288 bytes. Each block may contain various types of
records.
Valid CISIZEs for the Catalog are 1024, 2048 or 4096 bytes.

Space Requirements
For CKD-type disk devices, the track capacity of each device in 1024-byte
blocks is as follows:
Disk Device Number of Blocks Per Number of Blocks Per

Track Cylinder
3330 11 209
3340 7 84
3350 15 450
3375 25 300
3380 31 465
3390 33 495
9345 28 420
Substitute the appropriate track capacity and the calculated number of control
intervals (blocks) in the following equation to determine the size of the Catalog
required.
(number of blocks) / (track capacity) = number of tracks required
For FBA disk devices, the calculation is simpler. FBA devices use physical
blocks of an arbitrary length of 512 bytes. To determine the number of blocks
required for the Catalog on FBA devices, substitute Number of Blocks in the
following equation:
(number of blocks) * 2 = number of FBA blocks required
When the Catalog and Audit files are to reside on an FBA device, a minimum
allocation of 500 blocks is required. Because the Catalog structure is indexed
and self-reorganizing, there is no penalty for over-allocating. Too small a
Catalog can result in jobs being canceled if it becomes full. Too large a Catalog
can always be reduced in size if necessary.
When initializing the Catalog, enter an accurate estimate of the numbers of

data sets, volumes, and sort keys on the DYNCAT INITIAL or RESTORE REORG
command to allow the correct amount of index area to be reserved. Once the
Catalog has been backed up under r7.0 or higher, these values will be
maintained in the control record and need not be specified on later RESTORE
REORG runs.

Space Requirements
Estimated DASD Space Requirements for New Users
For a new user, the following table may be used as a rough guide to the initial
size of the Catalog. The Catalog will have to be enlarged as the number of
data sets and volumes under the control of the system increases.
DASD Type Requirements
3330 CKD 5 cylinders
FBA 1760 blocks
These estimates represent an average installation with a fairly even mix of

data set types. The best way to estimate an appropriate size for the Catalog is
to periodically review the DYNCAT Status report produced by the SCRATCH
function, and adjust the size of the Catalog accordingly.
If Audit support is generated, CA Dynam requires the allocation of permanent

DASD space for the Audit data set. The size of the Audit data set is entirely
dependent upon the characteristics of the particular installation, such as the
following:
Number of tapes and data sets processed daily
Number and nature of manual updates
Length of time between backups of the audit file
The best method of determining an appropriate allocation is to establish an

area the size of the Catalog file for the Audit data set, then review the file
status reports produced whenever the backup is performed for a
representative period. This information can then be used to determine the
actual space required.

CICS Requirements
CICS Requirements
Online access to the CA Dynam catalog, using CAICUI, requires entries in the
following CICS tables:
Program Control Table (PCT)
Processing Program Table (PPT)
File Control Table (FCT)
Program List Table Initialization (PLTPI)
Program List Table Shutdown (PLTSD)
Most of these entries are made during the installation of CA CIS. Samples of
the required entries are cataloged as .A members in the CA CIS and Dynam
sublibraries. For more information, see the chapter "Installation Steps" of this
guide and CA CIS Getting Started.
As an alternative to including the supplied source members for assembly of the

PCT, PPT, and programs may be defined online using CICS RDO, or migrated
using DFHCSDUP. Sample jobs and phases for use by DFHCSDUP in CICS/VSE
2.3 are supplied as described in the sublibrary member CAYDMIGR.Z. For CICS
TS, use the DFHCSDUP entries found in the sublibrary member DYNAMCSD.Z.
CICS Partition GETVIS Requirements
The following are the minimum CICS partition GETVIS requirements for some
of the VSE common components:
Component Minimum
Requirement
CAICUI 52K See Note 1
File Management 23K
CAISPI
VTOC, no sorting 2K See Note 2
IDCAMS processing 150K+ See Note 3

CICS Requirements
Note 1 52K is required by CAICUI to initialize the system. However, 25K is returned to
the system if no users are signed on to the CAICUI transaction.
Note 2 Certain CAICUI panels automatically invoke sort processing, while others
process it only optionally. 62K will automatically be allocated by the system
when sort processing is invoked.
Note 3 VSE limits anchor table entries to 51 per partition. The IDCAMS portion will
CDLOAD any necessary phases into the partition.

Chapter 4: Installation Materials
The installation materials provided for CA Dynam include the product tape, this
Installation Guide, and the remainder of the product documentation that can
be downloaded from http://ca.com/support.
CA Dynam
Title Description
Installation Guide Describes how to install the CA Dynam VSE

family.
Programming Guide Describes how to customize the CA Dynam VSE

family.
User Guide Describes how to use the CA Dynam VSE family.
Message Guide Contains all messages, the reason for each

message, and recommended user action for the
CA Dynam VSE family.
CA Dynam/T DYNVM Extension
Title Description
Administrator Guide Contains information on customizing the DYNVM

extension. This includes detailed descriptions of
the Task Manager component and all of the
DYNVM utility programs, EXECs and reporting
facilities.
Operator Guide Describes each DYNVM and Task Manager

operator command and function.
Programming Guide Discusses the planning, installation and

maintenance procedures of the CA Dynam/T VSE
DYNVM extension. Detailed descriptions of all
system features, libraries, modules and option
records are included.
Chapter 4: Installation Materials 4–1

CA Earl Report Program
CA Earl Report Program
Title Description
CA Earl Reference Guide Details the CA Earl reporting program.
CA Common Infrastructure Services
Title Description
Administration Guide A guide for CA CIS System Administrators.
Getting Started Describes how to install CA CIS for VSE.
Message Guide Presents error messages, abend codes, return

codes and diagnostic procedures for CA CIS.
Product Installation Tape

The machine-readable program materials required for installation are
distributed as a single, unlabeled, multi-file installation tape in IBM MSHP
BACKUP format. This can either be a physical tape, or a file distributed through
electronic delivery. In either case, the layout of the “tape” is the same. One
tape unit is required to install the product.
The installation tape contains the following files:
File # File Description
001 Tape Mark
002 CA Dynam for VSE history file—MSHP backup format
003 CA Dynam for VSE product library—MSHP backup format
004 to 007 Reserved use
008 MSHP Installation JCL
009 to 040 Reserved use
041 VM Extension ATTACH/DETACH VM component (on CA Dynam

for VSE Family and CA Dynam/T for VSE tapes only)

CA Dynam Pregenerated System
CA Dynam Pregenerated System

The CA Dynam system and the CA Dynam distribution package are designed to
help you install the product and make it operational as quickly as possible. In
order to accomplish this, we strongly recommend you follow the install
procedure exactly as documented. The installation will be smoothest when a
clear distinction is kept between the following two tasks:
Product installation
Product customization
The goals of installation are as follows:

Install VSE CA Dynam components
Successfully execute the supplied Installation Verification Procedure (IVP)
Customizing CA Dynam requires more time and study: over time, you will be
able to build a comprehensive file management facility after you determine
how CA Dynam will best meet the needs of your particular data center.
Chapter 4: Installation Materials 4–3

Chapter 5: Installation Steps
CA has developed standardized procedures for installing products using the
VSE MSHP utility. These standards for product installation have been
developed to allow a common method of installation for all CA VSE products.
The installation process uses two types of history files and libraries: Production
and Installation.
1. Production Libraries and History File
The production libraries and history file are created when the first CA
product tape is installed using this standard. This library or library set and
history file are designed to contain all CA VSE production products.
Sufficient space should be allocated to contain all CA VSE products
expected to be installed. When a product is subsequently installed, or
reinstalled, it will not be merged into the production library set and history
file until testing is complete.
2. Installation Libraries and History File
The installation libraries and history file are used for subsequent product
installation to avoid installation of a new product, or new release of an
existing product, into the user's production environment. These libraries
and history file are used for product installation, verification, and testing.
Each product tape that is installed will create a separate sublibrary and
history file that will be unique for that product tape. Once all testing has
been completed, the product is merged into the production libraries and
history file.
Creation of these two library sets, therefore, requires two different installation
procedures and sets of JCL, depending on whether the installation is an initial
or subsequent installation. When the first standardized CA VSE product tape is
installed, one job creates the production library or library set and history file,
and installs the product into same. When a subsequent product tape is
installed, the installation library or library set and history file are created and
used until the product is ready to be migrated into the production
environment, at which time the installation library set is deleted.
Chapter 5: Installation Steps 5–1

Standard Installation JCL
The standard sequence of product installation is as follows:
1. Retrieve the initial install JCL samples using the supplied JCL example for
either CAINSTB0 or CAINSTC0. These JCL examples are shown in Extract
the Product Installation JCL in the appendix “Accessing and Using Sample
JCL.”
2. Modifying the install JCL.
Modify the variables in this JCL using an editor. A worksheet is provided

defining the variables that must be provided (VOLSER, beginning block, or
track, for example; a total of 21 possible variables).
3. Installing CA CIS for VSE.
CA CIS for VSE must be installed before installing the individual product. If
you have already installed other CA VSE products, then you could have
already done this. If not, review CA CIS for VSE Getting Started to perform
this function.
4. Installing the product.
Submit the modified MSHP job from Step 2 to install the product from
tape.
5. Tailoring and verifying the product.
Proceed with product tailoring and verification.


Standard Installation JCL has been provided and must be used for installation
of all CA VSE products. The following table provides a brief overview of the JCL
described in the appendix “Accessing and Using Sample JCL.”
Job Name Where Source Member Description

Resides
CAINSTB0 The appendix Not supplied as a Used to retrieve CA Dynam install JCL
“Accessing source member supplied as source members in file #8 of
and Using the physical install tape. The “.Z”
Sample JCL” members will be placed into the specified
only VSE libname.subname.
CAINSTB2 source library CAINSTB2.Z Used to install CA Dynam (from a physical

tape) into a test library to allow
installation, verification, and testing prior
to migration into the production libraries.
CAINSTB3 source library CAINSTB3.Z Used to merge products into the

production library(s) and history file when
installed with either CAINSTB2 or
CAINSTC2.
CAINSTC0 The appendix Not supplied as a Used to retrieve CA Dynam install JCL
“Accessing source member supplied as source members in file #8 of
and Using the electronic delivery file. The “.Z”
Sample JCL” members will be placed into the specified
only VSE libname.subname.
CAINSTC2 source library CAINSTC2.Z Used to install CA Dynam into a test

library from an electronic delivery file
through IBM VSE Virtual Tape to allow
installation, verification, and testing prior
to migration into the production libraries.
CAINSTC4 source library CAINSTC4.Z Used to install CA Dynam distributed as an

electronic file using IBM VSE Virtual Tape
directly into an existing library and history
file.
CAINSTQ4 source library CAINSTQ4.Z Used to install CA Dynam distributed as a

physical tape directly into an existing
library and history file.

Special Upgrade Considerations
Special Upgrade Considerations

If you are upgrading from CA Dynam r6 to CA Dynam r7.1, and you expanded
the maximum record length of the COMPOOL option record from 2038 to
8192, you must complete an additional procedure during the upgrade process.
Special PTFs written for CA Dynam r6 supported COMPOOL records with a

maximum record size of 8K. The COMPOOL structure was changed in
CA Dynam r7.0. It is no longer limited to just one record but will not support a
length greater than 2038 bytes.
If your site applied these fixes, the new CA Dynam r7.1 sublibrary eliminates
all of these fixes except the two that were applied to CA CIS. These will need
to be removed manually.
For more information, see the appendix “Special Instructions for 8K COMPOOL
Records.”
Installation Overview Checklist

Use the following checklist to track your progress through the installation
process. These steps are described in detail in this chapter.
Note: If you call CA Technical Support for assistance during the installation
process, refer to the step number in question.
Step 1. Review System Requirements
Task 1A. Verify CA Dynam Family System Requirements
Task 1B. Review Installation Materials
Step 2. Remove Prior Release of Product
Step 3. Complete the Installation Worksheet
Step 4. Install CA CIS for VSE
Step 5. Install CA Dynam
Step 6. Modify Source Books
Task 6A. Punch Sample JCL
Task 6B. Update Skeleton JCL
Step 7. Update ASI Procedures
Step 8. Update CICS Tables

Task 8A. Update Program Processing Table (PPT)
Task 8B. Migrate PPT to CICS DFHCSD
Task 8C. Define CA Dynam Online Panels in CICS TS
Step 9. Initialize CAICUI VSAM Database
Step 10. CAIHELP Data Set Processing
Task 10A. Define and Load CAIHELP Data Set
Task 10B. Update CAIHELP Data Set for CA Dynam
Step 11. Load CA Dynam Messages
Step 12. IPL the System
Step 13. Data Set Initialization/Installation Verification
Step 14. Conversion Tasks
Step 15. Migration of CA Products into Production
Step 16. Install the DYNVM Extension
Step 17. Save All Materials and Output

Before attempting to complete any other installation steps for any CA Dynam
product, the VSE environment must be generated to meet the requirements of
the CA Dynam product family. Perform the following tasks in sequence.
Task 1A. Verify CA Dynam Family System Requirements
Review the chapter on System Requirements, comparing the system

specifications given there with those specified in your current VSE system.
Note any variation from the system requirements given in the "System
Requirements" chapter.
If you are planning on using the CAICUI portion of CA Dynam, see CA CIS
Getting Started for specifics on CAICUI system requirements.
If you are planning on using CAISPI, see the chapter "Systems Programmer
Interfaces (CAISPI)" of the Programming Guide for specifics on CAISPI system
requirements.

Task 1B. Review Installation Materials
Review the chapter “Installation Materials” to ensure that you have received all
of the required documentation and installation tape(s). If any discrepancies
are noted, contact your CA representative to request the missing items before
proceeding with this installation.

Before the CA Dynam generation procedure will function, any prior release of
any component of the system must be deactivated by the user. This
requirement is mandatory to avoid serious problems that can arise from
running mixed components of the system for even short periods of time.
This step should be performed only when upgrading to a new release, not
when installing a new service pack of the same release.
If you require assistance in removing library members and history file entries
for a prior release of CA Dynam, contact CA Technical Support.

Several questions concerning the environment in which CA Dynam will be
installed should be answered before proceeding with the installation process:
Which DASD packs will be used to hold libraries and installation files?
Which file IDs will be used for libraries and installation files?
What EXTENT information will be used for libraries and installation files?
The worksheet is provided to help you define these items, and should be
completed before continuing any further with the installation procedure.
The keywords on the worksheet are the same as the symbolic parameters
used in the supplied installation JCL. These keywords will then be used to
update the sample installation JCL for proper execution in your environment.
For a list of variables that must be modified, see the appendix “Accessing and
Using Sample JCL.”

Libraries and MSHP Install
The allocations given specify the library block requirements for installing
CA Dynam and include sufficient space to allow for product reinstallation and
maintenance.
The following chart should be used to calculate the appropriate number of

tracks or blocks for the specific DASD type where the libraries reside.
The calculated file sizes are to be used to complete the worksheet. For
installation of the CA Dynam family, 6700 1K library blocks are required and
the following number of library tracks:
Number of Library Tracks
3390 3380 3375 3350 3340 3330 FBA
200 215 266 443 949 604 13260
Note: Additional space will be required if other CA products are being

installed.
Standard Product Installation Worksheet

Description Keywords
1. Supply the following information used to personalize the CA production

history file:
Customer Name 1. @CUSTNME=______________

Customer Address @CUSTADD=______________
Customer Phone Number @CUSTPHN=______________
Programmer Name @PROGNME=______________
2. Supply the following information used for 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 used for 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 where the installation tape will be mounted:
Tape drive address of CUU 4. @TAPECUU=______________

5. Supply the following information used for 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 used for the install library EXTENT:
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 product code that you are installing.
PRODUCT NAME: CA Dynam for VSE @PRODUCT=______________

PRODUCT CODE: (see Note) @PRODCDE=______________
Note: The product name and code specified depends on whether this is a
family, Dynam/D, Dynam/T, or Dynam/FI installation, as follows:
Product Name @PRODUCT @PRODCDE
CA Dynam Family DYNAM AYD71
CA Dynam/D DYNAM ADD71
CA Dynam/T DYNAM ATD71
CA Dynam/FI DYNAM AFD71
8. Supply the following only if you are installing from the electronic delivery
file using IBM VSE Virtual Tape:
IP address of the machine that

currently holds the ".AWS” file @IPADDR= ______________
The fully qualified location and
name of CA Dynam .AWS file @AWSFILE=______________

CA CIS for VSE must be installed prior to installing CA Dynam. Refer to the
CA Dynam Product Maintenance Letter for minimum required release levels.
For more information about this step, see CA CIS Getting Started. To avoid
"down-leveling" any services, remember the following:
For a given release of CA CIS, never install a service pack lower than the
one already installed. For example, if r1.4, service pack 07 is already
installed, do not install r1.4, service pack 06.
Never install a release lower than the one previously installed. For
example, if r1.4 is already installed, do not install r1.3.


Extract the appropriate installation JCL member from the product library
specified during the execution of either CAINSTB0 or CAINSTC0. The JCL
should be edited according to the worksheet items and the information located
in the appendix “Accessing and Using Sample JCL.” Adhere to the following
guidelines when editing JCL into execution JCL:
1. Limit the scope of editor changes to columns 1 through 71 of the sample

JCL.
2. Remove the CATALS or CATALOG and BKEND statements that appear in

the beginning and end of each JCL sample.
3. In each JCL sample, change “@*” to “/*”, change “@&” to “/&”, change
“./” to “//”, change “.*” to “/*”, change “.&” to “/&”.
After all modifications are complete, mount the installation tape on the
specified tape drive and submit the JCL for execution.

This step will punch the skeleton sample JCL required to complete the
installation and customize the skeleton JCL into executable JCL according to
the specifications supplied in the worksheet completed in Step 3.
Task 6A. Punch Sample JCL
Your CA sample JCL (.Z books) found in the sublibrary includes all job streams
needed to proceed with the CA Dynam VSE installation. The following table
contains the member names, the respective install step, a required/optional
step indication, and a brief description.
.Z Member in Task Required/ Description

sublib Optional
CAYDVP1 13 Required Initialize Audit File
CAYDVP2 13 Required Initialize Catalog
CAYDVP3 13 Required Define Data Sets
CAYDVP4 13 Required Report on data set definitions
CADDVP1 13 Optional CA Dynam/D Verification
CADDVP2 13 Optional "

.Z Member in Task Required/ Description

sublib Optional
CAFDVP1 13 Optional CA Dynam/FI Verification
CAFDVP2 13 Optional "
CAFDVP3 13 Optional "
CATDVP1 13 Optional CA Dynam/T Verification
CATDVP2 13 Optional "
CAYDVP5 13 Required Delete Data Sets
CAINSTB3 15 Required Production Library(s) and History

File
DYNHLPL1 10A Optional Define and load the online VSAM

Help file with CA Dynam help data
DYNHLPL2 10B Optional Load CA Dynam and CAISPI help

data into the online VSAM Help file
Sample JCL
The following JCL is used to punch the sample JCL:
// JOB PUNCH DYNAM INSTALL JCL

*
* INCLUDE HERE THE APPROPRIATE DLBL AND EXTENT INFORMATION FOR THE
* LIBRARY TO WHICH THE PRODUCT WAS INSTALLED.
*
// EXEC LIBR
* INCLUDE HERE THE APPROPRIATE ACCESS LIBRARIAN COMMAND.
PUNCH XXXXXXX.Z ** Please see Note 1
/*
/&
Note 1 Insert for XXXXXXX the name of a .Z Member in the sublib.

Task 6B. Update Skeleton JCL
In this task the skeleton JCL, punched in Task 6A, will be customized to your
installation requirements as specified in Step 3, the Installation Worksheet.
Use the symbols prefixed with "@" as source data for global changes to the
values specified on your worksheet. Follow these guidelines when editing JCL
into execution JCL:
1. The output from Task 6A can be edited as a single file to perform the
changes specified on the worksheet.
2. Be sure to limit the scope of editor changes to positions 1 to 71 of the

skeleton JCL.
3. Remove the CATALOG statement from the beginning and end of each JCL
sample. Change '@*' to '/*'. Change '@&'. to '/&'.

Modify and catalog ASI Procedures with changes summarized below and
explained in detail in the "System Requirements" chapter.
Procedure
Add dummy tape devices as necessary for CA Dynam/T dummy
assignment support. For example, the following statement would add
support for five dummy tape devices:
ADD 7F0:7F4,3420T9
Note that the addresses used for dummy devices are specified by the
Dynam/T option record in the CAICUI data set. The default is 7F0 - 7FF.
Increase the GETVIS parameter of the SVA. For more information about
calculating what you will need, see Storage Requirements in the chapter
"System Requirements".
Increase the PSIZE parameter of the SVA command by a minimum of 2K

to a maximum of 18K.
BG Partition Procedure
Add or modify the SIZE command to ensure a minimum of 128K partition
GETVIS for all partitions where CA Dynam will be active.
Include the CA Dynam libraries in the LIBDEF SEARCH chain prior to the
SET SDL command.

Add the following commands to the SET SDL input stream to improve
performance (not required):
$$BDYT$$,MOVE \} For CA Dynam/T
$$BDYD$$,MOVE \} For CA Dynam/D
$$BDYF$X,MOVE \} For CA Dynam/FI
CAFNVDAA,SVA \} For VCKD support
XPR$CPIT,SVA \} For CA Dynam if using the CA Dynam/T

IUCV Interface
CAFNVDAA (for VCKD support), and XPR$CPIT (for CA IUCV Support for
VAE mode) are optional.
Add DVCDN cuu statements for each of the dummy tape devices defined
(if any).
Add permanent assignments for the programmer logical units used for the
CA Dynam Catalog and Audit files, if the system logical units SYSREC
and/or SYSCAT are not used.
Ensure these assignments are also added to the dynamic partition profiles.
If CASAUTIL is to be executed with // UPSI 01 (control statement input),

assign SYSLST to either a real printer or IGN.
Add the // EXEC CASAUTIL statement after the SET SDL input stream. To
set up initialization for the CA Dynam product, see the Programming
Guide.
Standard labels with CA Dynam options must be added after executing

CASAUTIL.
The first // JOB card should be placed in the BG ASIPROC before the
execution of CASAUTIL. If the first job card is encountered after the
execution of CASAUTIL, the permanent LIBDEF search chain, which must
include the CA Dynam library, must be established before the job card is
processed.

Sample JCL follows:
// OPTION STDLABEL
.
.
.
/*
// LIBDEF *,SEARCH= <============== Include CA Dynam libraries
SET SDL
.
.
.
/*
// EXEC CASAUTIL <=============== Start up CA Adapter Products
/*
// OPTION STDLABEL=ADD <======== See Note below
// DLBL IJSYSLN,'CPU--.==.SYSLNK.WORK',,SD
// EXTENT SYSLNK,V54WK*,1,0,1,30
// DLBL IJSYS01,'CPU--.==.SYS001.WORK',,SD
// DLBL SORTWK1,'CPU--.==.SORTWK1.WORK(X)',,SD
// EXTENT SYS001,V54WK*,1,0,1,30
/*
Note: Any JCL that uses CPU- or partition-dependent parameters or any

special CA Dynam options must be placed in standard labels or partition
standard labels after the execution of CASAUTIL.
Update Standard Labels
Update the VSE standard labels to contain label information for the following
data sets:
// DLBL CAICATL,'DYNAM.CATALOG',2099/366 ** See Notes 1, 3

// EXTENT SYSnnn,volid,1,0,sss,xxx ** See Notes 2, 4-7
// DLBL CAIAUDT,'DYNAM.AUDIT',2099/366 ** See Notes 1, 3
// DLBL SRAM1,'DYNAM.CUI.WORK FILE' ** See Note 9
The following labels may have already been added during the installation of
CA CIS and are provided here for your reference. For all of these labels, see
Notes 1 and 3.
// DLBL CAICUI,'CAI.CUI.PRODUCT.CONTROL.DATASET',,VSAM,CAT=CATNAME
// DLBL CAICUIU,'CAI.CUI.PRODUCT.CONTROL.DATASET',,VSAM,CAT=CATNAME
// DLBL CAIHLPV,'CAI.HELP.VSAM.DATASET',,VSAM,CAT=CATNAME

Note 1 Label information shown above is intended as an example only, and must be
tailored to meet installation standards before including it in the VSE ASI
Procedure.
Note 2 With respect to the CA Dynam Catalog and Audit files, logical units should be
permanently defined for them. The use of SYSREC and SYSCAT are ideal for
that purpose.
Note 3 Alter the data sets above to meet your installation standards.
Note 4 Alter SYSnnn above to contain the correct programmer logical unit(s). The
SRAM1 data set requires EXTENT and SYSnnn information. (SYSnnn must be
assigned to a DASD address whose device type matches that of the disk(s)
where the SRAM1 file will be located.)
Note 5 Alter volid above to contain the correct DASD Volume ID(s).
Note 6 Alter sss above to contain the correct starting track(s) or FBA block(s).
Note 7 Alter xxx above to contain the correct number of tracks or blocks.
Note 8 This label must be available to CICS to take advantage of CAICUI online
functions.
Note 9 If Dynam/D is installed, this file should be defined using the trigger value in
the extent. If Dynam/D is not installed, this file must be given a 0 retention. If
this is not done, and there is a failure allocating the file due to an equal file
condition, all of CUI will hang.
Fn Partition Procedures
Each Fn partition procedure must do the following:
Add the CA Dynam libraries to the permanent LIBDEF search chains.
CA Dynam Catalog and Audit files, if SYSREC and/or SYSCAT are not used.
Dynamic Partition Procedures
Users must update dynamic class profiles to include necessary

CA Dynam information. In each dynamic partition procedure, they must:
Add the CA Dynam libraries to the permanent LIBDEF search chains

(before any other job control statement).
CA Dynam Catalog and Audit files, if SYSREC and/or SYSCAT are not used.


If online access to the CA Dynam catalog is required, you need to use CAICUI.
For more information about CAICUI, see CA CIS Getting Started.
Before using the CA Dynam/CICS transaction, see Update CICS in the chapter
"VSE Installation Steps" of CA CIS Getting Started.
Task 8A. Update Program Processing Table (PPT)
If running under CICS/VSE 2.3, update the CICS Program Processing Table
(PPT). If using CICS Resource Definition Online (RDO), this task can be
omitted.
The following copybooks contain the required PPT entries to be added; they
were cataloged to the CA Dynam library during installation:
Copybook Name Description
CAYDPPT.A CA Dynam File Management
CAISPI.A CAISPI
Task 8B. Migrate PPT to CICS DFHCSD
In CICS/VSE 2.3, this task defines the required CA Dynam PPT entries in the
CICS Resource Definition data set, DFHCSD. This step can be omitted if PPT
entries were defined in Task 8A. Be sure to add the CAYDGRP group name to
the CICS startup LIST(s).
CAYDMIGR.Z Creates a single group name CAYDGRP that contains

all required PPT entries.
Task 8C. Define CA Dynam Online Panels in CICS TS
In CICS TS, this task defines the resources required to support the CA Dynam
online environment under CUI.
Note: The base CUI environment must be defined to CICS TS before you
complete this step. If you have not already done so, see the CA CIS Getting
Started Guide for instructions on setting up the CUI environment in CICS.

DYNAMCSD.Z Defines the CA Dynam CUI panels to CICS TS.

Before executing CASAUTIL to bring up CA Dynam, the product control records
must be written to the CAICUI database. At post-initialization of each product,
these control records will be read from the database and loaded into storage
for use by the appropriate product. (Post-initialization errors will occur if these
records are not found.)
If you are a new user installing CA Dynam for the first time, you can skip the
following paragraphs and proceed to the sample JCL provided below.
If you are migrating from either r5.5 or 6, and if you were using those phases
instead of the Option records defined in the CUI Product Control Dataset, these
records will be created from your existing macro phases. Otherwise, they will
be created using the system default values as documented in the guide.
Note: If you were already using the CUI Product Control Dataset to house the
Option records, the dataset CAICUI, should not be initialized. The existing
records are compatible with r7.1 and can be left in place.
If you are migrating from r5.5 or 6, it is necessary to have the macro phases
accessible at the time CACCDBU0 is run. Either your r5.5 or 6 library should be
available or the phases CATAGENA (Dynam/T), CADAGENA (Dynam/D)
CAFNCTLA (Dynam/FI), CASATABA (DYNPOOL, DYNLUB, DYNAVR) and
CASAGENA (Common Dynam options) must be copied to a sublibrary that can
be pointed to when running CACCDBU0.
When CACCDBU0 is run, it will search for these phases and create new control
records based on the existing parameters found in the old macro phases it
finds or, if a record is not found, it creates a new record with system defaults.
Each new record is a CPU-dependent record. In the case of the basic product
control records, (Dynam/T, D, FI and COMMON) a generic record is written to
serve as a default record for all CPU's served by that particular CAICUI VSAM
file. (CPU-specific records can be created for these records either through the
batch facility of CACCDBU0 or online, once the product has been successfully
initialized. The CAYD1600 screen can be used to 'clone' an existing record
with a new CPU-ID. The record can then be modified to suit particular needs).

In the case of the macros which have CPU-dependency as a parameter, control

records are be created for each CPU referenced in the old macro phase. Thus,
if a DYNPOOL macro exists which contained CPU=(A,B,F) for a particular pool
definition, then this pool would be defined in three separate records
(COMPOOLA, COMPOOLB, COMPOOLF) and written to the CAICUI database.
Each CPU-dependent record would contain all pool definitions that include that
CPU-ID.
If this macro also had a pool defined for CPU=ALL, each of the three
CPU-dependent records created would also have this CPU=ALL pool appended
to it.
Records will be created at CACCDBU0 initialization for any or all of the

following based on the availability of a corresponding macro phase, or macro
parameter within a phase, at initialization time:
Dynam/D DYNPOOL, DYNLUB, DYNAVR, DDLUBEX, DDDTFEX
Dynam/T DTLOCK, DTPOOL, DTNODET, DTDTFEX, DTLUBEX, DTNODE, DTPATH
Dynam/FI DFPROG, DFEXCL
Sample JCL
The following sample JCL is provided to initialize the CAICUI database with
product control records.
// JOB CACCDBU0 INIT CAICUI DATABASE WITH PROD CONTROL RECORDS

// DLBL IJSYSUC,'YOURCAT.VSAM.USER.CATALOG',,VSAM
* If you want new control records created from existing control
* phases from a prior release, use a LIBDEF similar to this:
// LIBDEF *,SEARCH=(NEWLIB.DYNAM71,OLDLIB.DYNAM60)
// EXEC CACCDBU0
INITIALIZE CUI DATASET(CAICUI) PROD(DYNAMT) DUPREC(DELETE)
INITIALIZE CUI DATASET(CAICUI) PROD(DYNAMD) DUPREC(DELETE)
INITIALIZE CUI DATASET(CAICUI) PROD(DYNAMF) DUPREC(DELETE)
INITIALIZE CUI DATASET(CAICUI) PROD(DYNAMCOM) DUPREC(DELETE)
/*
/
The following products should have been initialized before you execute
CASAUTIL to bring up CA Dynam. For more information, see the CA CIS for
VSE Administration Guide.
INITIALIZE CUI DATASET(CAICUI) PROD(CAT) DUPREC(DELETE)

INITIALIZE CUI DATASET(CAICUI) PROD(SYSTEM) DUPREC(DELETE)

The following statement can be used to initialize all 'CUI' products. It will
initialize all of the above products and any other products that it determines
are eligible for initialization. Consult the CA CIS for VSE Administration Guide
on the use of, and consequences of, using this control statement:
INITIALIZE CUI DATASET(CAICUI) PROD(ALL)

A VSAM Help file is required for several CA VSE products and is also used by
the CA CIS Help component, CAIHELP. This CAIHELP VSAM file (CAIHLPV)
must only be defined once. If the CAIHLPV VSAM file already exists, skip Task
10A and proceed with Task 10B.
Task 10A. Define and Load CAIHELP Data Set
To define and fully load the CAIHELP data set CAIHLPV with CA Dynam help
data, the following copybook has been provided:
Data Set Copybook Name Description

Name
CAIHLPV DYNHLPL1.Z Define and load VSAM CAIHELP data set

CAIHLPV with CA Dynam and CAISPI
help data.
Task 10B. Update the CAIHELP Data Set for CA Dynam
To update the CAIHELP file with the CA Dynam and CAISPI specific Help
information, the following copybook has been provided:
Data Set Copybook Name Description

Name
CAIHLPV DYNHLPL2.Z Load CA Dynam and CAISPI help data

into the online VSAM Help file CAIHLPV.


All CA Dynam messages are provided in a format that allows them to be
loaded into the IBM Online Message File (EXPLAIN) on VSE. If you want to
have CA Dynam messages available for online retrieval using the IBM EXPLAIN
facility, you must perform this task.
Modify the following JCL sample to your installation standards by replacing 'lib'
and 'sublib' with the name of the CA Dynam installation library and sublibrary.
* $$ JOB JNM=CAAYDMS2,DISP=D,CLASS=0
* *********************************************************************
* *********************************************************************
* * *
* * This is a sample VSE jobstream for loading the DYNAM messages *
* * into the VSE message file, IESMSGS. *
* * *
* *********************************************************************
* *********************************************************************
* * Notes - 1. This jobstep will not reset any previous user-defined *
* messages. *
* 2. The IBM EXPLAIN facility must be OFF before proceeding*
* by issuing the AR command, 'EXPLAIN OFF'. *
* *********************************************************************
// JOB CAAYDMS2 LOAD DYNAM MSGS
// SETPARM DYNLIB=lib REPLACE WITH DYNAM LIBRARY NAME
// SETPARM DYNSUB=sublib REPLACE WITH DYNAM SUBLIBRARY NAME
* *********************************************************************
// LIBDEF *,SEARCH=&DYNLIB..&DYNSUB
// EXEC PROC=DYNMSGLD
/*
/&
* $$ EOJ
Issue the AR command EXPLAIN OFF from your VSE console and run the job.
After the job completes, issue the AR command EXPLAIN ON. CA Dynam
messages (like IBM messages) will be available for online retrieval using the
VSE console or a CA FAQS/ASO for VSE console if CA FAQS/ASO for VSE is
installed at your site.
Step 12. IPL the System

An IPL is required for the installation and verification of CA Dynam products.
IPL the VSE operating system with the required options in place to support the
CA Dynam family of product features desired at your site.


This step sets up the execution environment for CA Dynam products.
The sample JCL members (.Z books) listed in Task 6A should be punched.
These jobs should then be edited, changed as specified on the installation
worksheet, and submitted for execution.
To make CA Dynam Online access available on your CICS system, you must
restart your CICS system. Be sure all JCL changes for library, Catalog and
Audit file access have been implemented and any customization required has
been performed.
Step 14. Conversion Tasks

In general, we recommend that you reinitialize the catalog and audit files, and
reorganize the catalog. Certain conversion tasks, however, depend on the
particular old and new releases in use. Review the documentation for the
release being installed, checking for specific release-to-release conversion
activities. If you are using CA Dynam/T vault control, also review the vault
processing documentation in the User Guide for possible conversion
requirements.
To upgrade from CA Dynam for VSE r6, you must perform a RESTORE REORG
on the CA Dynam for VSE r7.1 catalog before using it. If RESTORE REORG is
not completed, either of the following actions can produce unpredictable
results:
Performing a DYNCAT SCRATCH from CA Dynam for VSE r6 if the catalog

is being shared with CA Dynam for VSE r7.1.
Performing a DYNCAT SCRATCH from CA Dynam for VM if the catalog is

being shared with CA Dynam for VSE r7.1.
DYNCAT SCRATCH processing of a CA Dynam r7.1 catalog must be performed

from CA Dynam r7.1.
Step 15. Migration of CA Products into Production

CAINSTB3 is used to migrate a product into the production libraries and
history file when a product was installed into installation libraries and history
file using either CAINSTB2 or CAINSTC2. This step is executed only after
product installation, customization, verification, and testing are complete.

The sample JCL member CAINSTB3.Z is located in the library specified when
either job CAINSTB0 or CAINSTC0 was executed. For a list of variables that
must be modified, see Appendix B “Accessing and Using Sample JCL”.
After this process is complete, the installation libraries and history file can be
deleted.

Important! CA Dynam VM users can skip this step.
CA Dynam/T for VSE users can optionally install the DYNVM extension. For
more information, see the chapter "VM Installation Steps."
Step 17. Save All Materials and Output

Save all of your installation materials and all output from the installation
process. This material will be essential for timely and accurate CA maintenance
and support of the product.

Chapter 6: VM Installation Steps
Installing the DYNVM extension of CA Dynam/T VSE enables a powerful
communication facility that provides complete tape drive sharing between VSE
systems running under VM and other VM users. The DYNVM extension is
available only to CA Dynam/T users and is an optional component. It need not
be installed if you do not wish to enable it. For more information about how to
use the DYNVM extension, see the CA Dynam DYNVM Extension Administrator,
Operator, and Programming Guides.
Software Requirements
No modifications, other than the establishment of a VM system directory entry,
are required to install or operate the component.
DASD Space Requirements

The DYNVM extension requires 15 cylinders of 3390 DASD or 15,000 blocks on
FBA devices.
Installation Overview Checklist

You should have completed the VSE installation steps before proceeding with
the VM installation steps.
Use the following checklist to track your progress through the installation
process. These steps are described in detail in this chapter. Refer to the step
number in question if you must call CA Technical Support for assistance during
the installation process.
Step 1. Define Service Machine User ID
Step 2. Load Tape
Step 3. Tailor DYNLINK EXEC
Step 4. Tailor TASKMAN System Profile
Step 5. Tailor TASKMAN CP Commands
Chapter 6: VM Installation Steps 6–1

Step 6. Tailor TASKMAN CMS Commands
Step 7. Define System Adapter CPU Profile Table
Step 8. Tailor System Adapter Options
Step 9. Tailor CAICMS SYSPROF For Lock File
Step 10.Tailor DYNVM System Profile
Step 11.Generate DYNVM Product Control Table
Step 12.Define DTPOOL Macro (optional)
Step 13.Define DTLOCK Macro (optional)
Step 14.Create XSYSTEM Macro (optional)
Step 15.Run TQINST EXEC

The DYNVM extension executes in a virtual machine referred to as the DYNVM
service machine. Running under control of the Task Manager, any number of
requests may be processed at one time. One service machine can process
requests from all VSE guests in a single-CPU installation. A VM userid, usually
DYNVM, must be defined in the CP directory for the DYNVM service machine.
An example of the DYNVM service machine directory entry is as follows:
USER DYNVM password 16M 32M BCG 64

OPTION ECMODE ACCT
IUCV ANY P M 0
IUCV ALLOW
ACCOUNT nnnnnnnn SYSTEMX
IPL CMS PARM AUTOCR
CONSOLE 009 3215
SPOOL 00C 2540 READER A
SPOOL 00D 2540 PUNCH A
SPOOL 00E 1403 A
MDISK 191 3380 1391 020 VMnnnn MR ALL
LINK MAINT 190 190 RR
LINK MAINT 19E 19E RR
LINK MAINT 19D 19D RR

Step 2. Load Tape
The IDs and CUUs used in this example are for illustration purposes only. You
do not have to specify them as shown above, except where illustrated in the
installation.
Step 2. Load Tape

Note: If the DYNVM extension has already been installed and you are
upgrading to a new service pack, skip this step and proceed to Step 15.
The DYNVM extension is distributed on the CA Dynam VSE tape in CMS TAPE
DUMP format. If this is the first time you are installing the DYNVM extension,
attach a tape drive to the DYNVM service machine as 181 and type:
TAPE FSF 40
TAPE LOAD * * A
Step 3. Tailor DYNLINK EXEC

The DYNLINK EXEC, which is used to establish all CA Dynam/T catalog links
and accesses, must be tailored to your environment. Uncomment and edit
statements as necessary.
If audit support is selected, a write link is required to the CA Dynam/T VSE

audit data set.
If CA TLMS support is selected, a write link is required to the

CA TLMS message queue file.
If cross-CPU locking is enabled, a write link to the DOS lock file is

required.
If CA 1 support is selected, a write link is required to the CAIRECV file that

is accessible to MVS, as well as a read link to the CAISEND file.
Step 4. Tailor TASKMAN System Profile

Tailor the Task Manager options and identify the Task Manager operator in the
TASKMAN SYSPROF. Any valid Task Manager command may be specified in the
system profile. However, some commands are interpreted immediately and
executed during system profile processing. All other commands are processed
by the Task Manager Command Handler when initialization has been
completed.

The following commands are processed immediately from the Task Manager
system profile: GLOBAL, LOAD, NOTIFY, OPERATOR and SET.

Use XEDIT to modify the list of commands that we provide or change the
number of letters that must be specified to abbreviate a command. These CP
commands are accepted at the service machine console or from a Task
Manager operator. Only the CP commands included in this list are accepted by
the Task Manager.
The CP command file is a CMS card image file (LRECL 80 RECFM F) and must
have a file ID of TASKMAN CPFILE. Only positions 1-72 of each record will be
scanned. An asterisk in column 1 indicates a comment.
You can specify any valid CP commands within the CP command file, but do
not include any CP commands that may adversely affect the operation of the
Task Manager (for example, the CP LOGOFF command).
Every record in the CP command file must have two fields. The first field
specifies the full CP command name, and the second specifies the minimum
abbreviation required for the command.
Step 6. Tailor TASKMAN CMS Commands

Use XEDIT to modify the list of commands that we provide or change the
number of letters that must be specified to abbreviate a command. These CMS
commands are accepted at the service machine console or from a Task
Manager operator. Only commands that are transient modules or nucleus
resident should be specified. For more information about these commands, see
the IBM VM/SP CMS Command and Macro Reference Guide. Only the CMS
commands included in this list will be accepted by the Task Manager.
The CMS command file is a CMS card image file (LRECL 80 RECFM F) and must
have a file ID of TASKMAN CMSFILE. Only positions 1-72 of each record will be
scanned. An asterisk in column 1 indicates a comment.
You can specify any valid CMS commands within this file, but only those
commands that are transient modules or nucleus resident should be included.
Any CMS commands that utilize the user area can destroy Task Manager
storage.
Every record of the CMS command file must have two fields. The first field
specifies the full CMS command name, and the second specifies the minimum
abbreviation required for the command.


XEDIT the CPUPROF assemble to define the CPU ID and serial number of each
CPU. Every system ID must be unique.
Step 8. Tailor System Adapter Options

The System Adapter component provides cross-product interfaces and
application-type services for CA products. XEDIT the CASAGENC assemble file
to tailor the System Adapter to your data center standards.
1. Enter the amount of buffer space available for use by Catalog

Management. Specify a value from 0 to 1,677,215. The default is 0.
BUFSP acts as a limit for BUFNO. It should be specified as 0, unless you

receive instructions to the contrary from CA Technical Support personnel.
1. BUFSP: ________
2. Enter the default number of buffers to be requested by Catalog

Management when accessing the system data sets. Specify a number from
4 to 32,767. The default is 4.
2. BUFNO: ________
3. Specify the number of attempts allowed to obtain exclusive ownership of a

Catalog Management-controlled data set before a warning message
(CADC001W) is returned. Enter a value from 1 to 32,767. The default is
10.
3. ENQTRY1: ________
4. Specify the number of attempts allowed to obtain exclusive ownership of a

Catalog Management-controlled data set before an error message
(CADC005E) is returned. Enter a value from 1 to 32,767. The default is
255.
4. ENQTRY5: ________
5. Specify the number of seconds to wait between attempts to obtain

exclusive ownership of a Catalog Management-controlled data set. Enter a
value from 1 to 32,767. The default is 5.
5. ENQWAIT: ________
6. Indicate whether Catalog Management routines should support logging to

the audit data set by CA Dynam/T. Enter 1 to set audit logging support on.
Leave blank to set audit logging support off. The default is blank.
6. AUDIT: ________

Step 9. Tailor CAICMS SYSPROF for Lock File
7. Indicate whether Catalog Management routines should record recovery

information for the CA Dynam/T catalog in the audit data set. Enter 1 to
record recovery information. Leave blank if you do not want recovery
information recorded. Blank is the default.
7. RECOVER: ________
8. Indicate whether the CA Dynam/T utility program, DYNCAT, should log

images of manual maintenance for the audit data set. Enter 1 to record
this information. Leave blank if you do not want this information recorded.
Blank is the default.
8. AUDTMNT: ________
9. Specify the default data set type for the DYNCAT utility. Enter DISK, TAPE
or FI. The default is TAPE.
9. DEFTYPE: ________
Step 9. Tailor CAICMS SYSPROF for Lock File

Tailor the CAICMS SYSPROF for the lock file only if cross-CPU locking is
enabled. XEDIT the CAICMS SYSPROF to tailor the DLF command.
1. Specify the disk type as CYL for CKD, or BLK for FBA.
1. DEVTYP: ________
2. Enter the decimal track cylinder or block number where the lock file
resides.
2. START: ________
3. Specify the number of tracks or blocks used by the lock file extent.
3. NUMBER: ________
4. Enter the number of CPUs that can share the lock file.
4. NCPU: ________

Step 10. Tailor DYNVM System Profile
Step 10. Tailor DYNVM System Profile

This task defines the DYNVM system profile. Use this worksheet to gather the
information you need to provide. XEDIT the DYNAMAVR SYSPROF to tailor the
system profile to your data center standards.
1. Enter ON to have DYNVM generate accounting records. Enter OFF if you do

not want accounting records to be generated. The default is OFF.
1. ACCOUNT: ________
2. Enter ON to set CPMSG on. This causes the system operator console to
receive CP messages when DYNVM attaches and detaches tape drives to
and from VSE guests. Enter OFF to suppress these messages. The default
is OFF.
2. CPMSG: ________
3. Enter ON if informational messages are to be issued to the tape operator's

console. These messages include tape labeling information and work data
set release. Enter OFF to suppress these messages. The default is OFF.
3. IMSG: ________
4. Specify ON to test for a file-protect ring (write ring) on an input open

request. If a write ring exists on the requested tape, an error message is
issued. This is the default. Specify OFF to suppress the test for a write
ring.
4. RINGTEST: ________
5. Enter the userid of the DYNVM tape operator. The default is OPERATOR.
5. TAPEOPER: ________
6. Specify ON if messages are to be issued to a user waiting for service.

Specify OFF if messages are not to be issued. The default is OFF.
6. WAITMSGS: ________
7. This parameter defines the method used to disable tape volume unloading
during a DYNDET command.
Enter USERPARM LEAVE to use a user parameter. LEAVE, appended to the

DETACH command, causes CP to detach the tape without unloading it.
Enter RDEVBLOK to require that the DYNVM service machine have class C
privileges. This option results in a dynamic change to the RDEVBLOK upon
detach.
7. DETNOUNL: ________
8. Enter ON to allow non-Automated Cartridge Subsystem volumes to be

mounted on Subsystem owned drives.
Enter OFF to force Non-Subsystem volumes to be mounted on

non-Subsystem drives. This is the default.
8. ACSALLOW: ________

Step 11. Generate DYNVM Product Control Table
9. Enter ON to enable operator interaction with the Automated Cartridge

Subsystem server in command request.
Enter OFF to disable operator interaction and EJECT processing. OFF is the
default.
9. ACSDIALG: ________
10. This option specifies the time interval between checks for MAXWAIT,
OPENWAIT, and QUEWAIT expiration.
10. DISPATCH: ________
Enter the number of time units for the dispatch specification. (For example,
enter 2 for a dispatch specification of 2 minutes or 2 hours.)
# Of Time Units: ________
Enter the type of time unit, MIN for minutes, or HRS for hours.
Time Units:_______

XEDIT the DTPARMS ASSEMBLE file (which contains the Product Control Table)
to tailor the DYNAMT macro to your installation's needs. Use the following
worksheet to gather the information you need to provide.
1. Enter YES to allow input of a tape other than the one called for in a
controlled data set if the operator responds with ACCEPT to the CADT805D
message at input open. This is the default.
Enter NO to prevent use of ACCEPT in response to the CADT805D

message. (This does not prevent an ACCEPT response to the CADT810D
message.)
1. ACCEPT: ________
2. Enter NO to prevent ringing the console alarm when a message is issued

requiring operator action. This is the default.
Enter YES to ring the console alarm whenever a message is issued

requiring operator action. (This is useful if you have selected the
AUTO-RETRY facility; even though no operator action is needed, the alarm
notifies the operator that a mount is pending for a tape.)
2. ALARM: ________
3. Not used in VM. (Included for VSE consistency.)
3. ALTER: ________

4. Enter NO to disable auditing and recovery for CA Dynam/T. The default is

YES. Enter YES to support the Audit subsystem. This does the following:
− records information about each tape file OPEN/CLOSE and each

Catalog update.
− includes complete reporting.
− supports Catalog recovery.
− generates Audit OPEN/CLOSE/MAINT reporting functions.
− allows Audit recording of all Catalog activity.
4. AUDIT: ________
5. Enter NO to prevent deletion of automatically cataloged data sets and to

treat them as normal data sets. This is the default.
Enter YES to automatically delete cataloged data sets from the Catalog
when the last active version is scratched.
5. AUTCATD: ________
6. Give the default number of generations to save for an automatically

cataloged data set.
6. AUTCVER: ________
7. Enter NO to require that the AUTOCAT option be used in order for a

DYNOPEN request to be automatically cataloged. This is the default.
Enter YES to create a new Catalog entry when an output OPEN occurs for a
tape file that is not in the Catalog.
7. AUTOCAT: ________
8. Enter NO to prevent automatic scratch, regardless of the indication in the

data set record in the Catalog. This is the default.
Enter YES to perform automatic scratch only for data sets defined in the
Catalog with TAPEOPT=AUTOSCR.
Enter ALL to perform automatic scratch for all data sets.
8. AUTOSCR: ________
9. Enter NO to prevent use of the Lock File in a single CPU environment. NO

is the default.
Enter YES to issue an external, exclusive LOCK for the resource name
defined in the DTLOCK macro for any tape drive before it is accessed
during automatic volume recognition (AVR).
This lock:
− protects shared tape drives from interference by another CPU in a

multi-CPU, shared tape drive environment.
− remains in effect until the device is detached by DYNVM.

If you specify YES, you must also code the DTLOCK macros to define the
relationship between the logical resource name for each tape drive and the
physical addresses by which the drives are accessed.
9. AVRLCK: ________
10. Enter NO to temporarily build a pool of tapes with the correct Catalog
owner.
Enter YES to require that any output scratch tape selected by automatic
volume recognition have a matching Catalog owner ID (actually on the
VOL1). This ensures that the tape is owned by the requesting Catalog. The
default is YES.
The Catalog owner ID is established when the Catalog is initialized using

the id='catalog name' parameter of the DYNCAT INITIAL function. You can
modify it with the DYNCAT OWN function.
1. CATCHK: ________
11. Give a file name for a user exit during CLOSE (if a user exit is desired).
11. CLSHOOK: ________
12. Give the default density for data sets defined without a specified density
(including data sets defined with the Automatic Cataloging facility). Use
800, 1600, 6250, 90, 60, 50, 30, CART, 00, 00E, 00M, 00ME, 00MH, 00W,
00WE, 03WE, 08, 08E, 08M, 08ME, 08W, 08WE, 0BWE, 20, 20E, 20M,
20ME, 20MH, 20W, 20WE, 23WE, 28, 28E, 28M, 28MH, 28W, 28WE, or
2BWE.
12. DENSITY: ________
13. This does not apply to VM. Ignore this option.
13. LBLHOOK: ________
14. Enter YES to log significant events (allocation of the proper input volume,
and close of input volumes with catalog update) on the console at the time
they occur.
Enter NO to prevent the logging of significant events on the console. (YES

is strongly recommended.)
14. LOGINFO: ________
15. Give a file name for a user exit during message processing (if a user exit is
desired).
15. MSGHOOK: ________
16. Enter YES to generate support for multi-CPU shared tape drive protection.
YES should be specified in any multiple real or virtual CPU installation.
Enter NO for a single-CPU (or single-system) environment.
16. MULTCPU: ________

17. Enter YES to print a notification message on the Service Machine console
any time an OPEN request is received and the Catalog cannot be accessed.
Enter NO to allow tape files to be processed with Catalog access denied

and no notification given.
17. NOTIFY: ________
18. Specify the number of hours that open tapes can exist before being eligible
for scratch.
18. OPENH: ________
19. Give a file name for a user exit during OPEN (if a user exit is desired).
There is no default value for this option.
19. OPNHOOK: _______
20. Enter YES to provide data set owner checking during automatic volume
recognition.
Enter NO to prevent data set owner ID checking, reducing the data set
owner to a comment field for reporting purposes. The default value is YES.
20. OWNCHK: ________
21. Specify a default owner ID to be used for data sets with no owner ID
specification. (Up to two numeric characters may be entered.) There is no
default value for this option.
21. OWNID: ________
22. Enter YES to prevent the use of CA Dynam/T controlled scratch tapes for
uncontrolled data sets.
Enter NO to allow scratch tapes (never active data sets) to be used for
uncontrolled processing. The default value is YES.
22. PROHIBT:________
23. Enter YES to consider any volume with a serial number matching one in
the Catalog under control. YES should be entered if tapes have been
entered into the Catalog without having been written by CA Dynam/T and
if PROHIBT=YES has been specified.
Enter NO for CA Dynam/T to have under control only those tapes that
have been initialized by CA Dynam/T. The default value is NO.
23. PROTECT:________
24. Give the default length specification to be used for data sets defined
without a specific length (including data sets defined with the Automatic
Cataloging facility). Specify XS, S, M, L, or XL. There is no default value for
this option.
24. REELSIZ: ________

25. Enter YES to scratch the current version of the data set being processed if
the operator responds with RERUN to the CADT804/805D messages.
Enter NO to ignore the RERUN response, so that this maintenance must be

performed through the batch utility program. The default value is NO.
25. RERUN: ________
26. Enter the number of days to hold a data set defined to the Catalog without
an explicit retention specified. Up to four digits may be entered. The
default is 0.
26. RETAIN: ________
27. Enter YES to allow CA Dynam/T to select, for output, tapes that were
opened for output but never closed (indicating an abnormal user
termination condition).
Enter NO to retain tapes that were opened for output but never closed.
The tapes will not be used as scratch tapes until the DYNCAT scratch
function has been run. The default value is NO.
27. REUSE: ________
28. Give a filename for a message replies user exit during OPEN and CLOSE (if
a user exit is desired). There is no default value for this option.
28. RPLHOOK:_______
29. Enter YES to enable CA Dynam/T command validation by an external

security package such as CA ACF2 or CA Top Secret.
Enter NO to disable the external security package interface. The default

value is NO.
29. SECHECK:_______
30. Enter YES to cancel any OPEN request issued for a tape when the
CA Dynam catalog cannot be located.
Enter NO to allow tape files to be processed with access to the catalog file
denied. The default is NO.
30. SECURE: ________
31. Enter the default system user ID (SID) to be used for any data set defined
without one. Give the default user ID (UID) to be used as a default for any
data set defined without one. Up to two numeric characters may be
entered for each. There is no default value for this option.
31. SID: ________

UID: ________

32. Enter NO next to the word 'STOP' to require an operator response to all
action-type messages before CA Dynam/T processing can continue. Leave
second line blank.
Enter (n1,n2) to provide support for the AUTO-RETRY facility. Enter n1

next to the word 'STOP'. n1 represents a time interval (in seconds) to wait
before doing an automatic volume recognition scan. Enter n2 on the
second line. n2 represents the number of repetitions before issuing the
MOUNT message. The default value is NO.
32. STOP: ________
33. Specify a character string and position within the jobname that will signal
a request for $TEST processing. Enter a 1- to 8-character string, followed
by a single digit position at which the string will occur within the jobname.
The default is $TEST and 1.
33. TESTJOB:________
34. Enter YES to automatically log all tape information on an interface queue
when using CA Dynam/T and CA TLMS. This keeps the two tape
information databases in synchronization.
Enter NO if tapes are not to be shared between MVS and VM. The default
value is NO.
34. TLMS: ________
35. Give the user ID to be used as a default for any data set defined without
one. Up to two numeric characters may be entered.
35. UID: ________
36. Enter YES to generate support for the vault location control system.
Enter NO to consider all tapes to be in vault A.
Enter a single alphabetic character to support vault location control and

specify a default vault location for data sets defined without one. The
default is NO.
36. VAULT: ________
37. Enter ANY next to the word 'VOLSER' to permit any combination of
characters for a volume serial number. Leave the second line blank.
Enter NUMERIC next to the word 'VOLSER' to permit only numeric volume
serial numbers to be entered.
Enter (n1,n2) to permit only numeric volume serial numbers in the range
from n1 (lower limit) to n2 (upper limit). Enter n1 next to the word
'VOLSER'. Enter n2 on the second line.
Leave both lines blank to accept any volser. The default value is ANY.
37. VOLSER: ________

________

Step 12. Define DTPOOL Macro (Optional)
38. Enter the number of days retention for work tapes that are not released.
You can enter any positive integer, but any value less than two is strongly
discouraged. The default value is 2 days.
38. WORKRET: ________
39. Specify any special modification flags required for DYNVM operation.
39. MODON:__ __ __ __
40. Specify the userid of the Automated Cartridge Subsystem service machine
if the interface is to be used.
40. ACSSERV: ________
41. Specify a range of volumes to be used by the Automated Cartridge

Subsystem as controlled scratch volume by DYNVM. ALL is the default.
41. CTLSCR: ____ ____
42. Specify a range of volumes to be used by the Automated Cartridge

Subsystem as uncontrolled scratch volumes by DYNVM. ALL is the default.
42. UCTLSCR: ___ ____
Step 12. Define DTPOOL Macro (Optional)

Add this macro to the DTPARMS ASSEMBLE file to identify all CPUs and specify
the tape drives upon which automatic volume recognition (AVR) should be
performed. The following options are available:
Parameter Description
CPU Specify a character (alphabetic or numeric) to uniquely

identify each CPU being defined.
Tape Drive Specify all tape drive addresses upon which the
Addresses corresponding CPU may perform AVR.
Alternate CU Specify an alternate Channel/Control unit address for

address CA Dynam/T to use on AVR and DYNSTAT functions
when attaching drives to the service machine. This
should only be used on VM HPO5 systems where the real
tape addresses are above channel 0F.

Step 13. Define DTLOCK Macro (Optional)
Use this worksheet to gather the information you will need to provide.
CPU Tape drive/Alternate CU addresses for AVR
___ ____ ____ ____ ____ ____ ____ ____ ____
___ ____ ____ ____ ____ ____ ____ ____ ____
___ ____ ____ ____ ____ ____ ____ ____ ____
___ ____ ____ ____ ____ ____ ____ ____ ____
___ ____ ____ ____ ____ ____ ____ ____ ____
Step 13. Define DTLOCK Macro (Optional)

Add this macro to the DTPARM ASSEMBLE file to define a unique logical name
for each tape drive and to associate that name with all of the addresses
through which the drive is accessed in a multiple-CPU environment.
This table is also used to provide a mapping 4 digit vdev tape addressed to a 3
digit vdev tape address to allow such tapes to be attached to VSE. A matching
lock name for the 4 digit address on a VM CPUID and 3 digit address on a VSE
CPUID must exist to allow that address to be used by a VSE system.
The following options are available:
Parameter Description
CPU Specify a character (alphabetic or numeric) to uniquely

identify each CPU being defined.
Name Specify a unique logical name for the tape drive that will be
associated with all of the addresses through which the drive
is accessed. The name can be comprised of valid numeric or
hex digits (0-9,A-F).
Tape Specify the tape drive that is being named.

Step 14. Create XSYSTEM Macro (Optional)
Use this worksheet to gather the information you will need to provide.
CPU Name Tape
_ ___ ____
_ ___ ____
_ ___ ____
_ ___ ____
_ ___ ____
_ ___ ____
_ ___ ____

Add this macro to the DTPARMS ASSEMBLE file in conjunction with an external
tape system in order to allow sharing of volume usage information with
CA Dynam/T VSE and the DYNVM extension. This task is optional.
The following options are available:
NODEID Define the node identification of the participating system. This description may
be up to 8 alphanumeric characters. For communication with CA 1 MVS, the
nodeid of the CA 1 system must be 'CA1MVS'.
CPUID Define a CPU ID as specified in the CPUID macro. This may be one
alphanumeric character.
PATHID A required operand that identifies the inter-node communication vehicle. This
name, from 1- to 8-characters, is used as the DD/DTF name for the files and
used for cross system communication. The DD/DTF name must be the same
for both users of any PATH. For PATHs with VSE participants, logical IOCS
limits this value to 7 characters.
FROM A required operand that identifies the sending node. This value must
correspond to a CPUID specified in a NODE statement.
TO A required operand that identifies the receiving node. This value must
correspond to a CPUID specified in a NODE statement.

RWAIT An optional operand used to specify the duration of the wait following all
transactions processed by a receiver task, until the next check for incoming
activity is performed. The default is 60 seconds.
VERIFY An optional operand used to specify the number of intervals of time to wait for
a transaction to be processed by the receiver. If the transaction remains
unprocessed after the VERIFY interval has elapsed, a special verify transaction
is sent on the corresponding path as a test of the XSYSTEM network. This
value may be from 1- to 4-digits; the default is 10 intervals.
Sample Macro
The following example shows the DYNAMT macro, generated with all the
defaults, as it is cataloged upon initial installation. The DTPOOL, DTLOCK and
XSYSTEM macros are shown for syntax purposes. Standard IBM syntax rules
apply for assembling this macro.
DYNAMT , DYNAM/T OPTIONS +

ACCEPT=YES, +
ACSSERV=userid, +
ALARM=NO, +
ALTER=NO, +
AUDIT=YES, +
AUTCATD=NO, +
AUTCVER=, +
AUTOCAT=NO, +
AUTOSCR=NO, +
AVRLCK=NO, +
CATCHK=YES, +
CLSHOOK=, +
CTLSCR= ALL|(start,end), +
DENSITY=, +
FLT=YES, +
LOGINFO=YES, +
MSGHOOK=, +
MULTCPU=NO, +
NOTIFY=YES, +
OPENH=8, +
OPNHOOK=, +
OWNCHK=YES, +
OWNID=, +
PROHIBT=NO, +
PROTECT=NO, +
REELSIZ=ANY, +
RERUN=NO, +
RETAIN=, +
REUSE=NO, +
RPLHOOK=, +
SECURE=NO, +

SECHECK=NO, +
SID=, +
STOP=NO, +
TESTJOB=($TEST,1), +
TLMS=NO, +
UCTLSCR= ALL|(start,end), +
UID=, +
VAULT=NO, +
VOLSER=ANY, +
WORKRET=2, +
END=YES END OF DYNAMT OPTION
DTPOOL , TAPE POOL DEFINITION +
TAPE=(281,282,283), +
CPU=A
DTLOCK , AVR LOCK DEFINITIONS +
NAME=001, +
TAPE=(281,481)
DTLOCK , AVR LOCK DEFINITIONS +
NAME=002, +
TAPE=(282,482)
XSYSTEM TYPE=BEGIN
NODE NODEID='DYNVM.A', +
CPUID=A
NODE NODEID='DYNVSE.B', +
CPUID=B
NODE NODEID='CA1MVS', +
CPUID=Z
PATH PATHID='DYN2CA1', +
FROM=A, +
TO=Z, +
RWAIT=20, +
VERIFY=40
PATH PATHID='DYN2CA1', +
FROM=B, +
TO=Z, +
RWAIT=30, +
VERIFY=50
PATH PATHID='CA12DYN', +
FROM=Z, +
TO=A, +
RWAIT=10, +
VERIFY=20
XSYSTEM TYPE=END
END

Step 15. Run TQINST EXEC
Step 15. Run TQINST EXEC

If you are upgrading the DYNVM extension to a new service pack, attach a
tape drive as 181 and mount the service pack tape. If you are performing a
new installation, the DYNVM extension has already been loaded from tape in
Step 2, but you must run the TQINST EXEC to complete your installation.
Type TQINST to invoke the installation EXEC. If performing an upgrade, this

EXEC loads the new TXTLIBs from the tape. For both new users and users
performing an upgrade, the EXEC then generates all required modules and
TXTLIBs. These modules and TXTLIBs include all data center specified options.
Once the TQINST EXEC is complete, detach the tape drive.
If you were upgrading to a new service pack, the upgrade is complete. You can
now bring up the service machine.

Appendix A: Special Instructions for 8K
COMPOOL Records
Special PTFs written for CA Dynam r6 supported COMPOOL records with a
maximum record size of 8K.
The COMPOOL structure was changed in CA Dynam r7.0. It is no longer limited

to just one record but will not support a length greater than 2038 bytes.
Any CA Dynam r6 users that expanded the maximum record length of the
COMPOOL option record from 2038 to 8192 must follow the procedure below
when converting to r7.1.
Applicability to Installation
Use the following procedure to determine whether this situation applies to your
installation:
1. Run an IDCAMS LISTCAT ALL on the entry for the CAICUI dataset.
2. Check the value of MAXLRECL in the output:
If the value is 8192, you must complete the procedure described in

this appendix before running a CA Dynam r7.1 sublibrary.
If the value is 2038, ignore the information in this appendix. You can
proceed with the upgrade procedures and IPL with a CA Dynam r7.1
sublibrary.
COMPOOL Record Lengths

The DYNAM COMPOOL record has a maximum record size of 2038. Some
installations exceeded this limitation and needed to accommodate more pools
and volumes than could be held in one record. There were five special (Site
Specific) PTFs that were published for CA Dynam r6 to utilize a COMPOOL
record greater than 2038 bytes.
The fixes were:
LS02543
GO95871
GS95872
Appendix A: Special Instructions for 8K COMPOOL Records A–1

Running CA Dynam with Special Fixes
GS62398
GS62399
Some installations also applied special PTFs QS02463 and QS02457 that
allowed the online panel to accommodate up to 99 volumes in one pool. The
CA Dynam r7.1 sublibrary eliminates all of these fixes except the two that
were applied to CA CIS, which are GS62399 and LS02543. You must remove
these fixes manually as detailed in the following.

Use the following procedure while running CA Dynam r6 with the special fixes
applied. Do not IPL with a CA Dynam r7.1 sublibrary until all steps have been
completed.
1. Run a CAISERV from each CPU defined in the file. The output displays the
current state of the COMPOOL records: all pool characteristics and the
DASD defined to each.
// JOB CAISERV
// UPSI 10
// EXEC CAISERV
/*
/&
2. Delete the COMPOOL record by running the following job:

// JOB DELETE COMPOOL RECORD
// EXEC CACCDBU0,SIZE=CACCDBU0
DELETE COMPOOL CPU(*) REFRESH(NO)
/*
/&
3. Run the following job on a quiesced system to define and repro the CAICUI
dataset to a temp file. The temp file may be created in the same catalog.
If your COMPOOL record is currently greater than 2038, the repro step
returns the error IDC3309I ** RECORD LENGTH INVALID: X'.....' and a
return code of 8. This is normal and expected.
The example below has two different catalogs but the files can be in the
same catalog:
// JOB IDCAMS
// DLBL CAICUI,'CAI.CUI.PRODUCT.CONTROL.DATASET',,VSAM,CAT=catalog1
// DLBL TEMP,'CUI.TEMP.DATASET',,VSAM,CAT=catalog2
// DLBL catalog1,'user.catalog1.name',,VSAM
// DLBL catalog2,'user.cataloG2.name',,VSAM
// EXEC IDCAMS,SIZE=AUTO
DELETE (CUI.TEMP.DATASET) CL NOERASE PURGE -
CATALOG(catalog2)
SET MAXCC EQ 0
DEFINE CLUSTER( -
NAME(CUI.TEMP.DATASET) -
INDEXED -
A–2 Installation Guide

RECORDSIZE(1014 8192) -
allocation.type(prim sec) -
KEYS(17 0) -
FREESPACE(20 20) -
SHAREOPTIONS(4 4) -
VOLUMES(vvvvvv)) -
DATA( -
NAME(CUI.TEMP.DATASET.DATA)) -
INDEX( -
NAME(CUI.TEMP.DATASET.INDEX)) -
CATALOG(catalog2)
IF MAXCC EQ 0 THEN DO
REPRO INFILE(CAICUI) OUTFILE(TEMP)
END
DELETE (CAI.CUI.PRODUCT.CONTROL.DATASET) CL NOERASE PURGE -
CATALOG(catalog1)
END
DEFINE CLUSTER( -
NAME(CAI.CUI.PRODUCT.CONTROL.DATASET) -
INDEXED -
RECORDSIZE(1014 2038) -
allocation.type(prim sec) -
KEYS(17 0) -
FREESPACE(20 20) -
SHAREOPTIONS(4 4) -
VOLUMES(vvvvvv)) -
DATA( -
NAME(CAI.CUI.PRODUCT.CONTROL.DATASET.DATA)) -
INDEX( -
NAME(CAI.CUI.PRODUCT.CONTROL.DATASET.INDEX)) -
CATALOG(catalog1)
END
REPRO INFILE(TEMP) OUTFILE(CAICUI)
END
IF MAXCC LE 8 THEN DO
DELETE (CUI.TEMP.DATASET) CL NOERASE PURGE -
CATALOG(catalog2)
END
/*
/&
Appendix A: Special Instructions for 8K COMPOOL Records A–3

4. Remove PTFs GS62399 and LS02543 from the CIS sublibrary by running
the following job:
// JOB MSHP
// DLBL IJSYSHF,'cis.history.file',99/366
// EXTENT SYS000,volume,,,starttrack,numtracks
// ASSGN SYS000,DISK,VOL=volser,SHR
// EXEC MSHP,SIZE=1024K
UNDO 0202-SAD-01-VS3:LS02543
UNDO 0202-AUD-01-VS2:GS62399
/*
/&
5. IPL pointing to the CA Dynam r7.1 sublibrary.
Important! There is no COMPOOL record defined at this point. Therefore, no

files allocated in a CA Dynam pool can be created until this step completes.
Redefine the COMPOOL record using the output from Step 1. In the output,
locate the CADS000I COMPOOL messages and construct the input cards
needed to restore the COMPOOL record to its original state. Do this for each
CPU for which a COMPOOL is defined. The COMPOOL record can be updated for
any CPU in the CAICUI dataset from one machine. It can only be REFRESHed,
however, for the CPU of that machine.
// JOB COMPOOL
// EXEC CACCDBU0,SIZE=128K
DEF COMPOOL CPU(x) -
MEMBERS(volser,start,end,volser,start,end,...volser, start,end) -
PARTID(ALL|(BG,F1,..Fn)|NO) -
ROTATE(NO|YES) -
CLASS(ALL|C,D,...Z)|NO) -
POOLID(vvvvvv)
/*
A–4 Installation Guide

Appendix B: Accessing and Using
Sample JCL
This appendix provides instructions for performing the following tasks:
Extract the product installation JCL from a physical installation tape or

electronic software delivery (ESD) file.
Install the product into test libraries so that you can verify and test before
migrating into production libraries.
Migrate the product from the validation and test environment into the
production libraries.
Extract the Product Installation JCL

The job you use to extract the installation JCL depends on the medium on
which the product is delivered. It is one of the following:
CAINSTB0: Use this job if your product is delivered on a physical tape.
CAINSTC0: Use this job if your product is delivered as an ESD file.
These jobs are described in detail in the sections that follow.
Extract from a Physical Tape: CAINSTB0
Use the following JCL to extract the installation JCL from the physical
installation tape:
* ***************************************************************
* *** ***
* *** Update the following SETPARM statements: ***
* *** ***
* *** @LIBNAME to the name of the library you are using ***
* *** ***
* *** @SUBNAME to the name of the sublibrary you are ***
* *** using. ***
* *** ***
* *** @TAPECUU to the tape drive address where the ***
* *** physical tape is mounted. ***
* *** ***
* ***************************************************************
// JOB CAINSTB0 CATAL INSTALL JCL TO LIBRARY
// SETPARM LIBNAME=@LIBNAME REPLACE WITH LIBRARY NAME
Appendix B: Accessing and Using Sample JCL B–1

Extract the Product Installation JCL
// SETPARM SUBNAME=@SUBNAME REPLACE WITH SUBLIBRARY NAME

// SETPARM TAPECUU=@TAPECUU REPLACE WITH INSTALL TAPE ADDRESS
// MTC FSF,&TAPECUU,7
// ASSGN SYSIPT,&TAPECUU
// EXEC LIBR,SIZE=256K,PARM='ACCESS SUBLIB=&LIBNAME..&SUBNAME'
// RESET SYSIPT
/&
Extract from an ESD File: CAINSTC0
Use the following JCL to extract the installation JCL from an ESD file:
* ***************************************************************
* *** ***
* *** ***
* *** Update the following SETPARM statements: ***
* *** ***
* *** @LIBNAME to the name of the library you are using ***
* *** ***
* *** @SUBNAME to the name of the sublibrary you are ***
* *** using. ***
* *** ***
* *** @TAPECUU to the tape drive address of the IBM VSE ***
* *** Virtual Tape used to read the .AWS file. ***
* *** ***
* *** @IPADDR to the IP address of the machine that ***
* *** currently holds the .AWS file, and that ***
* *** has the IBM Virtual Tape Server running ***
* *** in JAVA. This value must be enclosed in ***
* *** single quote marks ('). For example: ***
* *** '123.231.132.321' ***
* *** ***
* *** @AWSFILE to the fully qualified location and name ***
* *** of the CA Dynam for VSE .AWS ***
* *** of the CA Dynam for VSE .AWS ***
* *** file. This value must be enclosed in ***
* *** single Quote marks ('). For example: ***
* *** 'E:\filename.AWS' ***
* *** ***
* ***************************************************************
// JOB CAINSTC0 CATAL INSTALL JCL TO LIBRARY
// SETPARM LIBNAME=@LIBNAME
// SETPARM SUBNAME=@SUBNAME
// SETPARM TAPECUU=@TAPECUU
// SETPARM IPADDR=@IPADDR
// SETPARM AWSFILE=@AWSFILE
// ON $CANCEL GOTO RELTAP
DVCDN &TAPECUU
VTAPE START,UNIT=&TAPECUU,LOC=&IPADDR, x
B–2 Installation Guide

Install the CA Product
FILE='&AWSFILE',READ
DVCUP &TAPECUU
// MTC REW,&TAPECUU
// MTC FSF,&TAPECUU,7
// ASSGN SYSIPT,&TAPECUU
// EXEC LIBR,SIZE=256K,PARM='ACCESS SUBLIB=&LIBNAME..&SUBNAME'
// RESET SYSIPT
/. RELTAP
DVCDN &TAPECUU
VTAPE STOP,UNIT=&TAPECUU
DVCUP &TAPECUU
/&

The job you use to install the product depends on the medium on which the
product is delivered. It is one of the following:
CAINSTB2: Use this job if your product is delivered on a physical tape.
CAINSTC2: Use this job if your product is delivered as an ESD file.
Either job installs the CA products into test libraries, so that you can perform
installation verification and testing prior to migrating the product into the
production libraries. For more information about installing the product directly
into an existing library and history file, see Performing a Direct CA Product
Installation.
CAINSTB2 and CAINSTC2 are described in detail in the sections that follow.
Install from a Physical Tape: CAINSTB2
Use the CAINSTB2 JCL to install the product from a physical tape into test
libraries from verification and testing.
The following describes the variable symbols for CAINSTB2:
@CUSTNME
Customer name used to personalize the MSHP history file.
@CUSTADD
Customer address used to personalize the MSHP history file.
@CUSTPHN
Customer phone number used to personalize the MSHP history file.

@PROGNME
Customer programmer name used to personalize the history file.
@INSTVOL
Volume serial number where the CA product installation history file will
reside.
@INSTREL
Relative track or block where the CA product installation history file is to

begin.
@INSTEXT
Number of tracks or blocks to be allocated to the CA product installation

history file.
@ILIBVOL
Volume serial number where the CA product installation library will reside.
@ILIBREL
Relative track or block where the CA product installation library is to begin.
@ILIBEXT

library.
@PRODCDE
CA product code for CA Dynam. For example: AYD71.
@PRODUCT
Product name: CA Dynam for VSE.
@TAPECUU
Device address where the product tape will be mounted.

Also change the following:
Change each ‘./’ to a ‘//’

Change each ‘@*’ to a ‘/*’
Change each ‘@&’ to a ‘/&’

CAINSTB2 Execution
CAINSTB2 performs the following functions:
1. Opens SYSPCH using the extents of the history file. This is a precautionary
measure to avoid errors when the history file extent resides on a newly
defined VM minidisk.
2. Creates the CA installation libraries and history file for the product being
installed from the product tape.
3. Installs the product tape to the installation history file and libraries.
Install from an ESD File: CAINSTC2
Use the CAINSTC2 JCL to install the product from an ESD file into test libraries
for verification and testing.
The following describes the variable symbols for CAINSTC2:
@PRODCDE
@INSTVOL
Volume serial number where the installation CA history file will reside.
@INSTREL
Relative track or block where the CA product installation history file is to

begin.
@INSTEXT

history file.
@TAPECUU
Device address of the IBM VSE Virtual Tape used to read the .AWS file.
@ILIBVOL
Volume serial number where the installation CA library will reside.
@ILIBREL
Relative track or block where the CA product installation library is to begin.
@ILIBEXT

library.

Migrate the CA Product into Production: CAINSTB3
@IPADDR
IP address of the machine that currently holds the .AWS file, and that has
the IBM VSE Virtual Tape Server running in JAVA. This value must be
enclosed in single quote marks (‘). For example, ‘123.231.132.321’.
@AWSFILE
Fully qualified location and name of the CA Dynam .AWS file. This value
must be enclosed in single quote marks (‘). For example,
‘E:\filename.AWS’.

Change each ‘.*’ to a ‘/*’
Change each ‘.&’ to a ‘/&’
CAINSTC2 Execution
CAINSTC2 performs the following functions:
1. Opens SYSPCH using the extents of the history file. This is a precautionary
measure to avoid errors when the history file extent resides on a newly
defined VM minidisk.
2. Creates the CA installation libraries and history file for the product being
installed from the electronic delivery files.
3. Installs the product to the installation history file and libraries.
Migrate the CA Product into Production: CAINSTB3

Use CAINSTB3 to migrate a product into production libraries and history file
after the product is installed using CAINSTB2 or CAINSTC2.
Note: A product is migrated into production only after installation,

customization, verification, and testing have been completed.
The sample JCL member CAINSTB3.Z is located in the library specified when
either job CAINSTB0 or CAINSTC0 was executed.
After this process is complete, the installation libraries and history file can be
deleted.
The following describes the variable symbols for JOB CAINSTB3:
@HISTVOL
Volume serial number where the CA production history file resides.

Perform a Direct CA Product Installation
@HISTREL
Relative track or block where the CA production history file begins.
@HISTEXT
Number of tracks or blocks allocated to the CA production history file.
@DLIBVOL
Volume serial number where the CA production library resides.
@INSTVOL
Volume serial number where the CA product installation history file

resides.
@INSTREL
Relative track or block where the CA product installation history file
begins.
@INSTEXT
Number of tracks or blocks allocated to the CA product installation history

file.
@ILIBVOL
Volume serial number where the CA product installation library resides.
@PRODCDE
CAINSTB3 Execution
CAINSTB3 merges the tested product or products into the production libraries
and history file.

A direct product installation installs the CA product into an existing library and
history file. The job you use to install the product depends on the medium on
which the product is delivered. It is on the following:
CAINSTQ4: Use this job if your product is delivered on a physical tape.
CAINSTC4: Use this job if your product is delivered on an ESD file.
CAINSTQ4 and CAINSTC4 are described in detail in the sections that follow.

Install Directly from a Physical Tape: CAINSTQ4
Use the CAINSTQ4 JCL to install the product from a physical tape directly into
an existing library and history file.
The following describes the variable symbols for JOB CAINSTQ4:
@DLIBVOL
Volume serial number of the location of the library you are using.
@DLIBREL
Starting track or block number of the library you are using.
@DLIBEXT
Number of tracks or blocks of the library you are using.
@HISTVOL
Volume serial number of the location of the history file being used.
@HISTREL
Starting track or block number for the history file being used.
@HISTEXT
Number of tracks or blocks allocated for the history file being used.
@TAPECUU
Device address where the physical tape is mounted.

CAINSTQ4 Execution
CAINSTQ4 installs CA Dynam from a physical tape into an existing library and
history file.
Install Directly from an ESD File: CAINSTC4
Use the CAINSTC4 JCL to install the product from an ESD file, using IBM VSE
Virtual Tape, directly into an existing library and history file.
The following describes the variable symbols for JOB CAINSTC4:
@DLIBVOL
Volume serial number of the location of the library you are using.

@DLIBNAM
File name of the library you are using.
@DLIBID
File-id of the library being used. This value must be enclosed in single
quote marks (‘). For example: ‘CAI.PRODUCT.LIBRARY’.
@HISTVOL
Volume serial number of the location of the history file being used.
@HISTREL
Starting track or block number for the history file being used.
@HISTEXT
Number of tracks or blocks allocated for the history file being used.
@HISTID
File-id of the history file being used. This value must be enclosed in single
quote marks (‘). For example: ‘CAI.PRODUCT.HISTORY.FILE’.
@TAPECUU
Device address of the IBM Virtual Tape used to read the .AWS file.
@IPADDR
IP address of the machine that currently holds the .AWS file, and that has
the IBM VSE Virtual Tape Server running in JAVA. This value must be
enclosed in single quote marks (‘). For example, ‘123.231.132.321’.
@AWSFILE
Fully qualified location and name of the CA Dynam .AWS file. This value
must be enclosed in single quote marks (‘). For example:
‘E.\filename.AWS’.

CAINSTC4 Execution
CAINSTC4 installs CA Dynam for VSE from an ESD file into an existing library
and history file.

Index
$ C
$$ transients, 3-3 CA Dynam

conversion considerations, 5-6, 5-20
initialization, 3-4
@ prior releases, 5-6
CA Dynam/T
@ symbols, 5-11 DYNVM, 6-1
CA DYNAM/T
tape operator, 6-7
A CA TLMS message queue file, 6-3
CADCJXTA, 3-4
Accounting records, 6-7
CAICMS SYSPROF, 6-6
Allowing non-Automated Cartridge, 6-7
CAIRECV file, 6-3
ASI PROC, 3-3
CAISEND file, 6-3
ASSGN function (TDYNASN), 3-5
CASAGENC assemble file, 6-5
Audit data set
defining, 3-6 CASAUTIL utility program
links, 6-3 startup procedure, 3-4
Auditing Catalog
of Catalog Management, 6-5 extent information, 3-6
of DYNCAT manual maintenance, 6-6 links, 6-3
space requirements, 3-7
Automatic
volume recognition, 6-9, 6-10 Catalog Management
auditing, 6-5
buffer space, 6-5
recovery information, 6-5
B
Checklist
VM installation steps, 6-1
BMX option, 6-3
VSE installation steps, 5-4
Buffer space, 6-5
CICS
restart, 5-20
table requirements, 3-10
CMS commands, Task Manager, 6-4
Common job exit, 3-3
Index–1
COMPOOL record service machine configuring, 6-2
expanded record length considerations system profile, 6-7
during upgrade, 5-4, A-1
Converting from prior releases, 5-6

E
CP
messages, 6-7
Task Manager commands, 6-4 Enabling operator interaction, 6-8
CPU Establishing catalog links, 6-3

IDs, 6-5 Extent information, 3-6
profile table, 6-5
Cross-CPU locking, 6-6
Customizing CA Dynam, 3-4, 4-3

F
file independance features, 1-1

D
File independence, 3-4
File-protect ring, 6-7

DASD space requirements
DYNVM, 6-1 First installation, 5-1
for new users, 3-9
Defining
CPU IDs, 6-5
G
logical unit names, 6-15
Disabling tape volume loading, 6-7 GETVIS requirements, 3-2
disk management features, 1-1
DLF command, 6-6 H

DOS lock file, 6-3
History file
DTLOCK macro, 6-8, 6-15
installation, 5-1
DTPARMS ASSEMBLE file, 6-8 MSHP, 2-2
production, 5-1
DTPOOL macro, 6-8, 6-14
Dummy devices, 3-5
DYNAMAVR SYSPROF, 6-7 I

DYNAMT macro, 6-8, 6-17
IBM EXPLAIN formatting messages, 5-19
DYNCAT SCRATCH, 5-20
Identifying CPUs, 6-14
DYNCAT utility program, 6-6
Informational messages, 6-7
DYNLINK EXEC, 6-3
Initializing product data set, 5-20
DYNVM Extension
DASD space requirements, 6-1 Installation
installation steps, 6-1 checklist for VM, 6-1
installation tape, 6-3 checklist for VSE, 5-4
Index–2 Installation Guide

libraries, 5-1 Messages
options informational, 6-7
DTLOCK macro, 6-8, 6-15 operator, 6-7
DTPOOL macro, 6-8, 6-14 user, 6-7
DYNAMT macro, 6-8
Messages, EXPLAIN format, 5-19
XSYSTEM macro, 6-16
standard JCL, 5-3 MSHP, 2-1, 5-1
tape, 4-2
Verification Procedure (IVP), 3-6, 4-3, 5-20
IPL O
for installation and verification, 5-19
IVP job streams, 4-3 Operator

messages, 6-7
tape, 6-7
J
P
JCL
CAINSTB2, 5-9
members, 5-3, 5-9 PCT CICS table, 3-10, 5-20
sample, 5-10
PPT CICS table, 3-10, 5-20
Job exit, 3-3
Product
control table, 6-8
customization, 4-3
L data set initialization, 5-20
distribution, 2-1
installation worksheet, 5-6
Libraries
installation, 5-1 Production libraries, 5-1
production, 5-1
PSIZE parameter, 3-3
source sublibrary (.z books), 5-9
Loading Messages, 5-19
Lock file, 6-3, 6-6 R

Logical unit assignments, 6-15
Recovery information, 6-5
Requirements
M CICS tables, 3-10
initialization, 3-4
IPL, 5-19
Macros
software, 6-1
DTLOCK, 6-8, 6-15
storage, 3-2
DTPOOL, 6-8, 6-14
supervisor, 3-1
DYNAMT, 6-8, 6-17
System Adapter, 3-1
XSYSTEM, 6-16
RESTORE REORG, 5-20
Message queue file links, 6-3
Index–3
Restrictions T
IBM, 3-6
with other file management systems, 3-5
Tables
Ring test, 6-7 .z book sublibrary members, 5-9
CICS requirements, 3-10, 5-20
JCL members, 5-3
S
Tailoring the DLF command, 6-6
tape management features, 1-1

Sample JCL members, 5-9
Tape operator, 6-7
SDL (System Directory List), 3-3
Task Manager
Sharing volume usage information, 6-16
CMS commands, 6-4
Software requirements, 6-1 CP commands, 6-4
system profile, 6-3
Source books, modifying, 5-9
Space requirements, 3-7
Specifying U
disk type, 6-6
lock file residence, 6-6
Upgrading
number of
COMPOOL record instructions, 5-4, A-1
CPUs sharing lock file, 6-6
DYNVM to new genlevel, 6-19
lock file extent blocks, 6-6
from prior releases, 5-6, 5-20
lock file extent tracks, 6-6
tape drives, 6-14 Utilities
CASAUTIL, 3-4
Storage requirements, 3-2
DYNCAT, 6-6
Supervisor
call codes, 3-4
native IBM, 3-4 V
requirements, 3-1
SVA (Shared Virtual Area), 3-2 Verifying installation, 3-6, 4-3

SVC code, 3-4 VM
SYSRES, 3-4, 3-6 DYNVM, 6-1
installation steps, 6-1
System
backup requirements, 3-4
identification list, 6-5
W
initialization, 3-4
profile
DYNVM, 6-7 Waiting, 6-7
System Adapter, 6-6
Worksheets
Task Manager, 6-3
estimating catalog size, 3-7
System Adapter for product installation, 5-6
options, 6-5
Write ring test, 6-7
profile, 6-5, 6-6
requirements, 3-1
Index–4 Installation Guide

X
XSYSTEM macro, 6-16
Index–5

CA Dynam For VSE Installation

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CA Dynam For VSE Installation

Hochgeladen von

Copyright:

Verfügbare Formate

CA Dynam for VSE

The manufacturer of this Documentation is CA.

Copyright © 2008 CA. All rights reserved.

 CA Dynam®/T Tape Management for z/VSE (CA Dynam/T)

 CA Dynam®/D Disk Management for z/VSE (CA Dynam/D)

 CA Dynam®/FI File Independence (CA Dynam/FI)

 CA TLMS Tape Management (CA TLMS)

 CA Common Infrastructure Services for z/VSE (CA CIS)

 CA ACF2™ for z/VSE (CA ACF2)

 CA Top Secret® for z/VSE (CA Top Secret)

If you have comments or questions about CA product documentation, you can

If you would like to provide feedback about CA product documentation, please

Chapter 2: Installation Process

Chapter 3: System Requirements

Chapter 4: Installation Materials

Chapter 6: VM Installation Steps

Appendix A: Special Instructions for 8K COMPOOL Records

Appendix B: Accessing and Using Sample JCL

CA Dynam/T Tape Management for VSE

 Preventing active tape data sets from being scratched

 Controlling remote site tape movement and retention

CA Dynam/D Disk Management for VSE

 Allocating primary and secondary disk space

 Permitting automatic space release

 Providing device independence for automatic conversion to new DASD

CA Dynam/FI File Independence for VSE

 Dynamically reblocking files for specified devices

 Dynamically changing record formats

 Simulating unit-record to multi-record device types, such as card reader to

Chapter 1: Introduction 1–1

1–2 Installation Guide

This technique allows flexibility as follows:

 Each step has an introductory paragraph describing the purpose of the

The "Installation Materials" chapter provides a detailed description of the tape

Chapter 2: Installation Process 2–1

MSHP is used to perform the installation and maintenance of CA Dynam for

2–2 Installation Guide

 CA Dynam/T—Tape Management System

 CA Dynam/D—Disk Management System

 CA Dynam/FI—File Independence System

Whether these components are purchased individually or as an integrated

System Adapter Requirements

Chapter 3: System Requirements 3–1

Component Minimum Requirement

Common Functions 16K - 24K

Important! Several CA products use the System Adapter, Catalog

As an alternative, the modules may be loaded into the SVA. Copybooks

.Z Member in Sublib Component

CAIYDIXV Index VTOC

CAIYDDYC CA Dynam Common Code

3–2 Installation Guide

System Directory List (SDL)

CA Dynam requires no phases to be resident in the shared virtual area itself,

$$BDYT$$,MOVE CA DYNAM/T Interception Transient (2K)

Increase the PSIZE parameter by a minimum of 2K to a maximum of 18K to

For example, if the virtual sizes of a 4-partition system are as follows:

The proper size command would be as follows:

Chapter 3: System Requirements 3–3

CADCJXTA,SVA CA Dynam COMMON JOB EXIT

The CA Dynam activation procedure dynamically locates the required 'hooks'

3–4 Installation Guide

The following restrictions exist when using a component of CA Dynam in

 No other file management system can be used to provide tape/disk file

CA Dynam®/T Tape Management for z/VSE (CA Dynam/T)

CA Dynam®/D Disk Management for z/VSE (CA Dynam/D)

CA Dynam®/FI File Independence (CA Dynam/FI)

CA TLMS Tape Management (CA TLMS)

CA Common Infrastructure Services for z/VSE (CA CIS)

CA ACF2™ for z/VSE (CA ACF2)

CA Top Secret® for z/VSE (CA Top Secret)

Preventing active tape data sets from being scratched

Controlling remote site tape movement and retention

Allocating primary and secondary disk space

Permitting automatic space release

Providing device independence for automatic conversion to new DASD

Dynamically reblocking files for specified devices

Dynamically changing record formats

Simulating unit-record to multi-record device types, such as card reader to

Each step has an introductory paragraph describing the purpose of the

CA Dynam/T—Tape Management System

CA Dynam/D—Disk Management System

CA Dynam/FI—File Independence System

No other file management system can be used to provide tape/disk file

If another system is to be used which performs a 'soft' rename of an IBM

Number of tapes and data sets processed daily

Number and nature of manual updates

Length of time between backups of the audit file

Program Control Table (PCT)

Processing Program Table (PPT)

File Control Table (FCT)

Program List Table Initialization (PLTPI)

Program List Table Shutdown (PLTSD)