Installation Worksheets

2
ce17
2
Variable Definitions Table
To help you organize and plan for the installation of
CA Endevor SCM
, use this table to review and note the detailed definitions for several of the variables that are included in the different installation JCL jobs. The definitions are grouped by type, for example, qualifiers or cluster parameters. Have this table available for reference when you install
CA Endevor SCM
.
 
Variable Definition Type
Variable
Description
Qualifiers
myiprfx
Highest-level qualifier that is used when assigning data set names for installation and execution libraries. This prefix is used for data sets that store
CA Endevor SCM
software. The software release number should be coded as part of iprfx or iqual.
The length of MYIPRFX and MYIQUAL must not exceed 16 characters.
 
myiqual
Second-level qualifier that is used when assigning data sets for installation and execution libraries. This prefix is used for data sets that store
CA Endevor SCM
software. The software release number should be coded as part of iqual or iprfx.
The length of MYIPRFX and MYIQUAL must not exceed 16 characters.
 
myuprfx
Highest-level qualifier that is used when assigning data set names for
CA Endevor SCM
user files. This prefix is used for data sets that store user modules. The software release number should not be coded as part of the prefix, because these data sets are independent of the release.
The length of MYUPRFX and MYUQUAL must not exceed 16 characters.
 
myuqual
Second-level qualifier that is used when assigning data set names to
CA Endevor SCM
user files. This prefix is used for data sets that store user modules. The software release number should not be coded as part of the prefix, because these data sets are independent of the release.
The length of MYUPRFX and MYUQUAL must not exceed 16 characters.
Sample Application Variables
SYSCLECOMP
The COBOL/LE compiler load library.
 
SYSCLERUN
The COBOL/LE runtime library.
 
SYSCLELKED
The COBOL/LE Automatic Call (link) library.
 
SYSCIICOMP
The COBOL II compiler load library.
 
SYSCIILIB
The COBOL II Automatic Call (link) library.
 
MONITOR=COMPONENTS
Indicates whether your site uses the ACM Query Facility.
  • If your site received an LMP key for product AY, Automated Configuration Option (ACM), do
    not
    change anything.
  • If your site did
    not
    receive an LMP key, change this value to MONITOR=NONE.
 
ADPROC?
Indicates whether your site uses processors.
  • If your site received an LMP key for product A9, Extended Processors, change this value to ADPROC.
  • If your site did
    not
    receive an LMP key, change this value to ADNOPROC.
 
SYSMACLIB
The data set name of the system assembler macro library. For example, SYS1.MACLIB.
 
C??
CII or CLE. Indicates the version of COBOL in use at your site.
  • If you are using COBOL/LE, change this value to CLE.
  • If you are using COBOL II, change this value to CII.
  • If your site uses COBOL/LE and COBOL II, change the value to the version of COBOL you use most often.
 
C??NBL
CIINBL or CLENBL. Indicates the default processor group for COBOL elements that are delivered with the sample application. The C?? portion of this variable should be set to the same value as the variable C??.
Symbolic Device Assignment
mycart
Symbolic device name for cartridge data sets.
 
mypdisk
Symbolic device label for permanent disk data sets.
 
mytdisk
Symbolic device label for temporary disk data sets.
Volume Serial Numbers
mysvolser
Volume serial number that is used by SMP/E for DD SMPTLIB.
 
mytvolser
Volume serial number of the
CA Endevor SCM
installation cartridge.
 
myvvolser
The volume serial number of the disk that is used to store VSAM clusters.
For more information about volumes, see the definition of VOLUMES under Master Control File (MCF) Cluster Parameters.
 
mydvolser
The volume serial number of the disk that is used to store permanent data sets.
Master Control File Cluster Parameters
CYLINDERS (
n n
)
Primary and secondary space allocations, respectively. The default value is (5 1) for Stage 1 and (5 1) for Stage 2, which is sufficient for a system with up to 750 elements in each stage.
For more information about how to calculate additional space, see Disk Space Requirements Worksheet.
Package Data Set Cluster Parameters
CYLINDERS (
n n
)
Primary and secondary space allocations, respectively. The default value is (8 2), which is sufficient for 50 packages averaging 50 elements, with BACKOUT enabled and averaging 4 outputs per element.
For more information about how to calculate additional space, see Disk Space Requirements Worksheet.
Master Control File Allocations for the Sample Application
SMPLJOB4 allocates the following VSAM structures.
Stage
Library
Data Set Name
1
VSAM cluster
iprfx.iqual.SMPLTEST.MCF
 
Cluster data component
iprfx.iqual.SMPLTEST.MCF.DATA
 
Cluster index component
iprfx.iqual.SMPLTEST.MCF.INDEX
2
VSAM cluster
iprfx.iqual.SMPLQA.MCF
 
Cluster data component
iprfx.iqual.SMPLQA.MCF.DATA
 
Cluster index component
iprfx.iqual.SMPLQA.MCF.INDEX
3
VSAM cluster
iprfx.iqual.SMPLEMER.MCF
 
Cluster data component
iprfx.iqual.SMPLEMER.MCF.DATA
 
Cluster index component
iprfx.iqual.SMPLEMER.MCF.INDEX
4
VSAM cluster
iprfx.iqual.SMPLPROD.MCF
 
Cluster data component
iprfx.iqual.SMPLPROD.MCF.DATA
 
Cluster index component
iprfx.iqual.SMPLPROD.MCF.INDEX
Installation Worksheet
To help you organize and plan the installation of
CA Endevor SCM
, you can use the following worksheet to record the information and values you will use to install
CA Endevor SCM
at your site.
If you need clarification about variables when completing this worksheet, see Variable Definition Table.
Variable Definition Type
Variable
Your Site Value
Qualifiers
myiprfx
 
 
myiqual
 
 
myuprfx
 
 
myuqual
 
Sample Application Variables
SYSCLECOMP
 
 
SYSCLERUN
 
 
SYSCLELKED
 
 
SYSCIICOMP
 
 
SYSCIILIB
 
 
MONITOR=COMPONENTS
 
 
ADPROC?
 
 
SYSMACLIB
 
 
C??
 
 
C??NBL
 
Symbolic Device Assignment
mycart
 
 
mypdisk
 
 
mytdisk
 
Volume Serial Numbers
mysvolser
 
 
mytvolser
 
 
myvvolser
 
 
mydvolser
 
Master Control File Cluster Parameters
CYLINDERS (
n n
)
 
 
FREESPACE
Do not change the default value of (30 30) for this parameter.
 
RECORDSIZE
Do not change the default value of (640 1200) for this parameter.
 
KEYS
Do not change the default value of (28 0) for this parameter.
 
SHR
Do not change the default value of (3 3) for this parameter.
Package Data Set Cluster Parameters
CYLINDERS (
n n
)
 
 
FREESPACE
Do not change the default value of (30 30) for this parameter.
 
RECORDSIZE
Do not change the default value of (640 3070) for this parameter.
 
KEYS
Do not change the default value of (64 8) for this parameter.
 
SHR
Do not change the default value of (3 3) for this parameter.
Disk Space Requirements Worksheet
The default disk space allocations that are provided in the installation JCL are large enough to accommodate a pilot project (approximately 500 elements). The information can vary depending on factors such as the average number of lines of code per element, blocking factors, and disk device types. Use the information and examples in the Disk Space Requirements Worksheet to help you determine the requirements for your site. Have this worksheet available for reference when you install
CA Endevor SCM
. The worksheet is organized as follows:
  • Data set name and description
  • Default values, where appropriate
  • Space for your specification
Before completing the Disk Space Requirements Worksheet, consider the following information:
  • It is assumed that your site uses 3390-type disk devices. All SPACE parameters are based on 3390 devices. If your site uses another type of device, adjust them accordingly.
  • All libraries can be defined as operating system partitioned data sets (PDS), or, except for a load library, as CA Panvalet data sets, CA Librarian data sets, or ELIB data sets. If you are defining CA Panvalet or CA Librarian data sets, confirm to allocate storage equivalent to the storage defined in the worksheet.
  • When allocating a partitioned data set, be aware that for efficiency, directory blocks are allocated in increments of 45 (which is the number that can fit on a single track of a 3390-type device). In addition, in each library, one directory block exists for every four elements.
  • CA Endevor SCM
    compresses blank spaces from the base, delta, and processor listing libraries (assuming the base and delta libraries are OS/PDS or ELIB files).
  • Routine maintenance is required on the libraries described.
  • The number of members that are stored in a single partitioned data set should not exceed 5,000. Exceeding this number can result in contention problems such as severe disk contention, heavy updating, and excessive wait time for rewriting partitioned data set directories. Up-front planning in this area helps avoid problems. Keep in mind that base and delta libraries can be defined by element types.
  • Elements can be stored in reverse delta or forward delta format. The Disk Space Requirements Worksheet provides information for both formats in the descriptions of the base library and the delta library. The
    CA Endevor SCM
    sample application uses reverse delta format for storing elements.
Element Catalog Planning
Allocate one 3390 cylinder for every 600 elements in PROD. For the element index, allocate one 3390 cylinder for every 2,000 elements in PROD.
Base Library Planning
Consider the following values when planning a base library:
  • Data Set Name
    uprfx.uqual.
    BASE
  • Description
    This library contains element source as initially defined to
    CA Endevor SCM
    . The space requirements are a function of the number of elements (members) to be stored, the number of source lines per element, and the library manager in use. For existing PDS members to be loaded into the base library, use ISPF/PDF option 3.2 (UTILITIES, then DATASETS) to estimate the space that is required. To calculate the total amount of space that is needed, multiply the estimated space by an expansion factor (such as 1.2) that is appropriate to the expected library expansion beyond these members.
  • Format
    PDS: DCB=(RECFM=VB,LRECL=259,BLKSIZE=0) (Forward Delta)
    PDS: DCB=(RECFM=FB,LRECL=80,BLKSIZE=0) (Reverse Delta)
  • Space Calculation
    To estimate the number of PDS directory blocks needed, assume that one directory block exists for every four elements. For efficiency, directory blocks should be allocated in increments of 45 for a 3390-type device (or whatever number can fit on a single track for another type of device). To calculate the number of directory blocks, divide the estimated number of elements (members) to be stored in the library by four. Round that result to an even multiple of 45 (for a 3390-type device). The number should be the same for base and delta libraries.
    For example, assume that two existing PDS libraries are placed under the control of
    CA Endevor SCM
    , and the total space that is currently occupied by members in the library takes up 100 cylinders. You can allocate a base library of 120 cylinders (100 x 1.2 = 120) to leave 20 percent free space to allow for expansion.
  • Forward Delta Format
    The following values apply if you are storing elements in forward delta format.
 
PDS Defaults
Your Site's Specification
Primary (CYL)
80
 
Secondary (CYL)
10
 
Dir Blk
180
 
  • Reverse Delta Format
    The following values apply if you are storing elements in reverse delta format.
 
PDS Defaults
Your Site's Specification
Primary (CYL)
90
 
Secondary (CYL)
15
 
Dir Blk
90
 
Delta Library Planning
Consider the following values when planning a delta library:
  • Data Set Name
    uprfx.uqual.
    DELTA
  • Description
    This library contains change levels for elements that are defined to
    CA Endevor SCM
    . The space requirements for the library are a function of the number of elements to be stored, the volatility of the elements (that is, the number of changes that are expected and the extent of those changes), and the library manager in use. A good starting point is a size that is half as large as the base library. The number of directory blocks should be the same as for the base library.
    If the Automated Configuration Manager is installed at your site, increase the file size by 33 percent and triple the number of directory blocks. In addition, you cannot use the same library as the Base and Delta library.
  • Format
    PDS: DCB=(RECFM=VB,LRECL=28332,BLKSIZE=0) (Same Format for Forward and Reverse Delta)
  • Forward Delta Format
    The following values apply if you are storing elements in forward delta format.
 
PDS Defaults
Your Site's Specification
Primary (CYL)
40
 
Secondary (CYL)
10
 
Dir Blk
180
 
  • Reverse Delta Format
    The following values apply if you are storing elements in reverse delta format.
 
PDS Defaults
Your Site's Specification
Primary (CYL)
40
 
Secondary (CYL)
15
 
Dir Blk
270
 
Package Data Set Planning
Consider the following values when planning a package data set:
  • Data Set Name
    uprfx.uqual.
    PACKAGE
  • Description
    This data set stores all packages for the entire site. The size of this file is determined by the number of packages to be stored at any time and the average size of each. The size can be difficult to calculate because packages vary greatly in size, which is based on number of actions and whether BACKOUT/BACKIN is enabled. The maximum size of a package record is 3070 bytes.
 
Defaults
Your Site's Specification
Primary (CYL)
8
 
Secondary (CYL)
2
 
  • Format
    VSAM
Processor Load Library Planning (Stage 1)
Consider the following values when planning a processor load library for Stage 1:
  • Data Set Name
    uprfx.uqual.
    PRC1LOAD
  • Description
    This library contains Stage 1 processor load modules. The GPPROCSS processor writes to this library, for elements that are defined with the element type PROCESS.
    The size of this library is a function of the number of processors added to the system with which the library is associated and the number of lines in each processor. Estimate the total number of generate, move, and delete processors to be stored for Stage 1. Allow 1.5 tracks for each processor. For example, for a library that is targeted to store 15 processors, use a primary allocation of 10 tracks and a secondary allocation of 1 track.
    To determine the number of directory blocks that are needed, assume that one directory block exists for every four processors. Then, use the previous information in Base Library to continue.
 
PDS Defaults
Your Site's Specification
Primary (CYL)
10
 
Secondary (CYL)
5
 
Dir Blk
45
 
  • Format
    DCB=(RECFM=U,LRECL=0,BLKSIZE=32760)
Listing Libraries Planning (Stage 1)
Consider the following values when planning listing libraries for Stage 1:
  • Data Set Names
    uprfx.uqual
    .LISTING1
    uprfx.uqual
    .PRC1LIST
  • Description
    These libraries contain listings that correspond to a Stage 1 user-defined listing library (
    uprfx.uqual
    .LISTING1) or the Stage 1 processor load modules (
    uprfx.uqual
    .PRC1LIST).
    Size information for each library is discussed in the following section. To determine the number of directory blocks that are needed for either library, assume that one directory block exists for every four listings. Then, use the previous information in Base Library to continue.
  • Format
    PDS: DCB=(RECFM=VBA,LRECL=28332,BLKSIZE=0)
  • User Listing Library
    The CONLIST utility writes to the user listing library, for those elements that are defined with a type associated with a processor containing this utility. To estimate the size of the user listing library, allocate one track per member. However, the item being stored can greatly influence the overall size of the library. For example, a one-page printout takes up much less space than a 600-page compile.
    A good estimate for compile listings is two tracks per member. With a user library targeted to store 100 compile listings, for example, use a primary allocation of 200 tracks and a secondary allocation of 10 tracks.
  • Processor List Library
    The GPPROCSS processor writes to the processor list library, for those elements that are defined with the type PROCESS. The size of the processor list library is a function of the number of processors added to the system with which the library is associated, and the number of lines in each processor.
    Estimate the total number of generate, move, and delete processors to be stored for Stage 1. Allow one track for each processor. For example, for a library that is targeted to store 15 processors, use a primary allocation of 15 tracks and a secondary allocation of five tracks.
    This table contains the defaults.
 
PDS Defaults (PRC1LIST)
PDS Defaults (LISTING1)
Your Site's Specification (PRC1LIST)
Your Site's Specification (LISTING1)
Primary (CYL)
10
200
 
 
Secondary (CYL)
5
10
 
 
Dir Blk
45
45
 
 
Data Set (MCF) Planning (Stage 1)
Consider the following values when planning a data set for Stage 1:
  • Data Set Name
    uprfx.uqual
    .STAGE1
  • Description
    This data set contains the Stage 1 Master Control File entries. The size of this file is based on the number of systems, subsystems, elements, types, and processor groups to be stored at Stage 1.
 
PDS Defaults
Your Site's Specification
Primary (CYL)
5
 
Secondary (CYL)
1
 
  • Format
    VSAM
COPYLIB Planning (Stage 1)
Consider the following values when planning a COPYLIB for Stage 1:
  • Data Set Name
    uprfx.uqual
    .COPYLIB1
  • Description
    This library contains the latest full source of each element that is created during output management at Stage 1. The size of this library is a function of the exact amount of space the members consume outside of
    CA Endevor SCM
    .
    For existing partitioned data set members, use the ISPF/PDF option 3.2 (UTILITIES, then DATASETS) to estimate the space that is required. Multiply the space that is required by an expansion factor (such as 1.2) that is appropriate to the expected library growth beyond these members.
    To determine the number of directory blocks that are needed, assume that one directory block exists for every four members. Then, use the previous information in Base Library to continue.
    If you are using forward deltas, a source output library must be defined. In addition, if you are using reverse deltas, defining a source output library is optional. The base image library performs the same function as the source output library.
 
Your Site's Specification
Primary (CYL)
 
Secondary (CYL)
 
  • Format
    DCB=(RECFM=FB,LRECL=80,BLKSIZE=0)
Processor Load Library Planning (Stage 2)
Consider the following values when planning a processor load library for Stage 2:
  • Data Set Name
    uprfx.uqual
    .PRC2LOAD
  • Description
    This library contains Stage 2 processor load modules. Determine the size and number of directory blocks for this file as you would for the Stage 1 library, 
    uprfx.uqual
    .PRC1LOAD. For more information, see Processor Load Library Planning (Stage 1).
 
PDS Defaults
Your Site's Specification
Primary (CYL)
10
 
Secondary (CYL)
5
 
Dir Blk
45
 
  • Format
    DCB=(RECFM=U,LRECL=0,BLKSIZE=32760)
Listing Libraries Planning (Stage 2)
Consider the following values when planning listing libraries for Stage 2:
  • Data Set Names
    uprfx.uqual
    .LISTING2
    uprfx.uqual
    .PRC2LIST
  • Description
    These libraries contain listings that correspond to a Stage 2 user-defined listing library
     (uprfx.uqual
    .LISTING2) or the Stage 2 processor load modules (
    uprfx.uqual
    .PRC2LIST).
    Determine the size and number of directory blocks for this file as you would for the Stage 1 libraries, 
    uprfx.uqual
    .LISTING1 and 
    uprfx.uqual
    .PRC1LIST. For more information, see Listing Libraries Planning (Stage 1).
 
PDS Defaults (PRC2LIST)
PDS Defaults (LISTING2)
Your Site's Specification (PRC2LIST)
Your Site's Specification (LISTING2)
Primary (CYL)
10
200
 
 
Secondary (CYL)
5
10
 
 
Dir Blk
45
45
 
 
  • Format
    PDS: DCB=(RECFM=VBA,LRECL=28332,BLKSIZE=0)
Data Set (MCF) Planning (Stage 2)
Consider the following values when planning a data set for Stage 2:
  • Data Set Name
    uprfx.uqual
    .STAGE2
  • Description
    This data set contains the Stage 2 Master Control File entries. Determine the size of this file as you would for the Stage 1 data set, 
    uprfx.uqual
    .STAGE1. For more information, see Data Set (MCF) Planning (Stage 1).
    This table contains the defaults:
 
Defaults
Your Site's Specification
Primary (CYL)
5
 
Secondary (CYL)
1
 
  • Format
    VSAM
COPYLIB Planning (Stage 2)
Consider the following values when planning a COPYLIB for Stage 2:
  • Data Set Name
    uprfx.uqual
    .COPYLIB2
  • Description
    This library contains the latest full source of each element that is created during output management at Stage 2. Determine the size of this library as you would for the Stage 1 library, 
    uprfx.uqual
    .COPYLIB1. For more information, see COPYLIB Planning (Stage 1).
    If you are using forward deltas, a source output library must be defined. In addition, if you are using reverse deltas that are
    not
    encrypted, defining a source output library is optional. The base image library performs the same function as the source output library.
 
Your Site's Specification
Primary (CYL)
 
Secondary (CYL)
 
  • Format
    DCB=(RECFM=FB,LRECL=80,BLKSIZE=0)