Allocate Files

This article describes the required and optional file allocation steps needed to configure your product. All products must allocate the PROTSYM file. File allocations specific to each product are described after the PROTSYM information.
caitsd-11-0
This article describes the required and optional file allocation steps needed to configure your product. All products must allocate the PROTSYM file. File allocations specific to each product are described after the PROTSYM information.
2
Allocate PROTSYM
Member CAVHPROT creates the PROTSYM VSAM file, which contains the symbolic information and source listings for your application programs. Edit the JCL in the CAVHJCL library to conform to your installation standards and the previously completed worksheet.
Note the following items when creating the symbolic file:
  • Do not specify a secondary space allocation.
  • The CAVHPROT utility job (running the IN25UTIL program) could run for a long time depending on the size of the file. This occurs only the first time after the file is created by the IDCAMS job.
  • Each symbolic file has an upper limit of about four million 2 KB records and holds approximately 147,000 programs.
  • The symbolic file must not reside in the LSR pool.
Concurrently Updating the PROTSYM File
The application uses the MVS RESERVE and DEQ macros to allow sharing of the PROTSYM file between regions or systems.
The resource major name used in the RESERVE and DEQ macros is INTERTST. Place the major name INTERTST into an MVS service that converts the RESERVE into a cross-system ENQ if this service is available at your site.
Populate the Symbolic File
This section applies only to CA InterTest for CICS and CA SymDump for CICS users.
If your site previously loaded a PROTSYM file with the symbolic information for CICS DSECTs and CA InterTest for CICS and CA SymDump for CICS DSECTs, you may skip this step.
Member CABALSYM, found in the CAVHJCL library, populates the PROTSYM VSAM file with symbolic information for CICS DSECTs and CA InterTest and SymDump for CICS DSECTs. Edit the JCL to conform to your installation standards.
Symbolic information and source listings for the demonstration programs will be loaded into the PROTSYM file when you prepare the programs for execution.
Update Your In-house Compile and Assemble Procedures
To update the compile and assemble procedures and create symbolic information for your Assembler, PL/I, or COBOL programs, see Symbolic Support.
CA InterTest Batch Files
Allocate PROFLIB
You must allocate a profile data set before executing the application. CAVHPROC library member CAMRPROF contains the sample allocation for the profile data set. PROFLIBs can be allocated per user or per site. Each user requires one block and one directory entry in the PROFILE library to maintain session variables. Allocate a number of blocks equal to the number of programmers who will access the application. There are three users per directory block. The number of directory blocks should be changed if the number of users is greater than 90.
The parameters you need for this JCL are as follows:
  • TGTVOL=,
    VOLSER of the PROFLIB
  • PREFIX='USER.',
    The USERID high-level qualifier (default = USER)
  • PERMDA=SYSDA
    The generic UNIT for permanent DASD (default = SYSDA)
During execution, each user requires WRITE access to the PROFILE library only. Secure all other required application files with READ access only. Be sure to give similar attention to the optional files that the application uses (for example, the session log).
Allocate ALIBs (Optional)
The product uses an ALIB data set to save allocation information. Users can have any number of ALIBs at their disposal, but they must be created manually.
CAVHPROC library member CAMRALIB creates and catalogs an ALIB. The parameters you need for this JCL are as follows:
  • TGTVOL=,
    The VOLSER of the target data sets
  • PREFIX='USER.',
    The USERID high-level qualifier (default = USER)
  • PERMDA=SYSDA
    The generic UNIT for permanent DASD
Allocate INCLIBs (Optional)
If you intend to use the INCLUDE command, you must allocate the INCLUDE library. CAVHPROC library member CAMRINCL allocates this library.
The parameters you need for this JCL are as follows:
  • TGTVOL=,
    VOLSER of the target data set
  • PREFIX='USER.',
    The SITE/USERID high-level qualifier (default = USER)
  • PERMDA=SYSDA
    The generic UNIT for permanent DASD (default = SYSDA)
CA SymDump Batch
Allocate CAIPRINT Repository Library
Make a copy of
CAI
.CAVHJCL(CARXREPO) and update it to conform to your installation standards.
Use CARXREPO to create and initialize a new CAIPRINT repository library. The data set name for your CAIPRINT repository is defined in the PRTLIB option of CAOETABL. This data set name will be defined in the next step, . Specify the same dsname when customizing CARXREPO.
CARXREPO consists of the following two steps:
Step
Program
Description
1
IDCAMS
Allocate the CAIPRINT repository.
2
CAOUPRTU
Initialize the CAIPRINT repository.
RESERVE and DEQ macros are used when updating the CAIPRINT repository to enable sharing of files between regions and systems. The resource major name used in the RESERVE and DEQ macros is CAOUPRTA. If your installation uses a service that converts RESERVEs into cross-system ENQs, define the major name CAOUPRTA to the service.
Estimated Size of the CAIPRINT Repository Library
An individual CAIPRINT report's size varies greatly depending on the number of active programs, the size of the data in each active program, the number of allocated files, and so on. Because of this, it is difficult to determine how much space to allocate for the repository.
As a guideline, using CAOEDEMO and a repository of one cylinder, you can store 17 reports in the repository. This report contains only one active COBOL program, but contains a large data division of approximately 500 KB.
Because of the number of factors that affect the determination of the size of your repository, we suggest that you determine the amount of space you want to dedicate to saving abend reports. You can migrate the reports to a larger repository later using the CAOUPRTU utility COPY function.
Do not specify a secondary space allocation when creating the repository because the capacity of the repository is fixed by the allocation job and cannot be increased using secondary extents.
The LE option TERMTHDACT(UADUMP) generates a U4039 abend when an unhandled condition occurs of severity 2 or greater. CA SymDump Batch will not report on this abend.
CA InterTest for CICS and CA SymDump for CICS
Install the Help Facility
The member DEFHELP, found in the CAVHJCL library, creates and loads the VSAM file that contains the CA InterTest and SymDump for CICS online help information. Edit the JCL to conform to your installation standards and the previously completed worksheet. This member and other referenced members are found in the CAI.CAVHJCL library after the APPLY step.
Create the User-Defined Abend Description File
The member DEFUHLP, found in the CAVHJCL library creates the VSAM file that contains the user-defined abend description information. Edit the JCL to conform to your installation standards and the previously completed worksheet. This member and other referenced members are found in the CAI.CAVHJCL library after the APPLY step.
CA InterTest for CICS
Create the Debug Session File
The member DEFMLOG, found in the CAI.CAVHJCL library creates the file that is used to record breakpoints and keeps set when monitor logging is turned on. These records can later be loaded for another debug session without having to set breakpoints and keeps again. Edit the JCL to conform to your installation standards. If you decide to use the optional PROTMLOG feature, then a unique MLOG dataset is required for each CICS region.
For more information on the Monitor Logging facility, see Monitoring Menu Options.
Create the Checkpoint File
The member DEFCKPT, found in the CAVHJCL library creates the checkpoint file that is used to periodically record the status of CA InterTest for CICS for a possible restart. This member and other referenced members are found in the CAI.CAVHJCL library. Edit the JCL to conform to your installation standards.
For more information on the checkpoint recording facility, see Monitoring Menu Options.
CA SymDump for CICS
Create the PROTDMP File
The CA SymDump for CICS VSAM file, PROTDMP, is the CA SymDump for CICS dump data set. This file contains all of the dumps that will be viewed and maintained with CA SymDump for CICS. PROTDMP files that were initialized using a release of CA SymDump for CICS after r8.0 are compatible with this release.
Use member SYMFILE in CAI.CAVHJCL to create and initialize the file with program IN25INIT. Be aware of the following:
  • The maximum number of dumps the CA SymDump for CICS dump data set can hold depends on the CI (Control Interval) size. For more information, see the SYMFILE member in the CAVHJCL.
  • Do not specify a secondary space allocation.
  • The SYMFILE job may run for a long period of time depending on the size of the file.
  • Two or more concurrently active CICS regions cannot share the same CA SymDump for CICS PROTDMP file for update.
You cannot run IN25INIT on a previously initialized PROTDMP file. IN25INIT can only be run against a newly defined VSAM file.
Estimating the Size of the PROTDMP File
The size of an individual dump varies greatly depending on the number of active programs, the size of the data in each active program, and so on. Because of these issues, it is difficult to determine how much space to allocate for the PROTDMP file.
Therefore, CA suggests that you determine the amount of space you are willing to dedicate to saving dumps. Dumps can always be migrated at a later date to a larger PROTDMP file using the COPY function of the IN25DMPU utility.
Do not specify a secondary space allocation when creating the PROTDMP file because the capacity of the PROTDMP file is fixed by the allocation job and cannot be increased using secondary extents.