Repository Utility screen


The Repository Utility screen shown in the following figure allows you to create and delete the Code Coverage Results Repository data sets used to accumulate testing coverage data. If in batch mode, a batch job using IDCAMS will be generated to do the actual allocation or deletion of the data set. This screen is accessed by entering option 1 on the Code Coverage Utilities menu.

You can also run a batch job to create or delete a Results Repository data set. Sample JCL is provided in SLXVSAMP members JCLCRERP and JCLDELRP.

Repository Utility Screen

 ----------------  CODE COVERAGE 17.02 - REPOSITORY UTILITY  -------------------
COMMAND ===>

Commands: C (Create file)    D (Delete file)

    Repository File ===>ACMJET0.V17.REPOSIT

   Management Class ===>           (optional)
      Storage Class ===>           (optional)
             Volume ===>           (optional)
               Unit ===>           (optional)

        Space Units ===> CYL       (CYL/MB)
   Primary Quantity ===> 10

          Edit JCL  ===> NO_       (Yes/No)






         Press ENTER to process  or  enter END command to terminate

Commands

The primary commands are defined as follows:

Commands

Description

C

Creates a repository data set

D

Deletes a repository data set

Input fields

The following input fields are available:

Field

Description

Repository file

Specifies the name of the data set to be created or deleted. The name can be qualified with quotes or unqualified. An unqualified name appears with your user ID as a prefix. Ensure your site’s Code Coverage users have write access to the specified data set.

Management class

Specifies the desired SMS management class. Only use this optional field or the Storage Class field when creating an SMS managed data set. When you use this field, leave the Volume and Unit fields blank. The appropriate values for those fields will be assigned by the system.

Storage class

Specifies the desired SMS storage class. Only use this optional field or the Management Class field only when creating an SMS managed data set. When you use this field, leave the Volume and Unit fields blank. The appropriate values will be assigned by the system.

Volume

Specifies the volume serial number on which to allocate the repository data set. You can also specify a generic unit name. Only use this optional field only when creating a non-SMS data set. If you use the Management Class field or the Storage Class field when creating an SMS managed data set, then leave this field blank so that the system will assign the appropriate value.

Unit

Specifies the generic unit name on which to allocate the repository data set. If you specify a unit name, a sequential data set will be dynamically allocated to a volume on that unit. This data set will then be deleted and replaced by a VSAM data set when the IDCAMS batch job is run. Only use this optional field only when creating a non-SMS data set. If you use the Management Class field or the Storage Class field when creating an SMS managed data set, then leave this field blank so that the system will assign the appropriate value.

Space units

Specifies the primary space units for the data set. A value must be entered when any repository data set is created or deleted. Valid values are cylinders (CYL) and megabytes (MB). This field is required.

Primary quantity

Specifies the number of primary space units to be allocated for the repository data set. This field is required. A valid space unit value must be entered when any repository data set is created. The default size is 10 cylinders, which provides enough space for one or more systems totaling approximately 1000 programs of 800 executable statements each. For estimating purposes, the size of each record is
(8 * number of executable verbs) + 160.

Edit JCL

Allows you to choose whether or not to edit the JCL. When you are in batch mode, specify Yes to edit the JCL of the IDCAMS allocation or deletion job prior to submittal. The default value is No. When you are in an online mode, No is automatically displayed in this field as a default and you are prohibited from entering a value.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*