Installing Your Product Using CA MSM › Deploying Products › Custom Data Sets › Add a Custom Data Set

Add a Custom Data Set

You can add custom data sets to a deployment.

Follow these steps:

1. Click the Deployments tab.

   The Deployments window appears.

2. On the right, in the Deployments panel, click the Current Deployment link.

   A list of current deployments appears.

3. Click the deployment name link.
4. In the Custom Data Sets List panel, click Add Data Sets.

   The Add Custom Data Sets dialog appears.

   Note: The asterisk indicates that the field is mandatory.

5. Select a Product from the drop-down list.

   Note: When there are instructions, they are required and supplied by CA Support.

6. Select the Data Set Type, either data set (step 7) or USS (step 10).

   Default: data set

7. For data set, enter the data set name.

   Limits: Maximum 44 characters.

   Note: This is the existing z/OS data set name that you want CA MSM to include in the deployment when it is deployed on the target systems.

8. Enter the data set name mask, click the file icon, and select a symbolic name.

   Mask

   This is the mask that will be used to name the data sets that are being deployed. They can contain symbolic qualifiers. For example, if you enter CAPRODS.&SYSID, the &SYSID is replaced by its values, and if the SYSID that is being deployed to is XX16, the DSN mask will be CAPRODS.XX16

   Limits: Maximum 64 characters.

   Note: Each deployed target data set is named using the resolved content of the data set name mask followed by the low-level qualifier of the source data set. Appending the low-level qualifier from the source data set helps ensure uniqueness of the final data set name. Verify that the mask that you entered does not exceed 35 characters when it is translated.

   The mask consists of one or more qualifiers that are separated by periods. The maximum number of characters is 64, including the periods. While you are entering the mask, CA MSM validates the mask by replacing symbolics with the minimum possible values first, and then with the maximum values. If the validation with the minimum possible values fails, an error message appears at the top of the dialog, and you cannot proceed. If the validation with the maximum values fails, a warning message appears, and you can proceed.

   When the mask is translated, it has a maximum length of 44 characters including the periods and the low-level qualifier from the source data set. The low-level qualifier from the source data set has a maximum length of nine characters including a period.

   Two consecutive periods are required to separate the two masks.

9. Enter the Mask and click OK.
10. For USS data set type, enter the Local Path. The local path is the directory are where files are to be copied from.

    Limit: Maximum 255 characters.

    Note: The asterisk indicates that the field is mandatory.

11. Enter the Remote Path and/or click the file icon and select a symbolic name. The remote path is the path where the files are to be copied to.

    Limit: Maximum 255 characters.

12. Select the Type of Copy:
    • If you select Container Copy, proceed to step 14.
    • If you select File-by-file Copy, proceed to step 15, and ensure that the USS path exists on all of the remote systems of this deployment, and that there is sufficient space to hold these target libraries.

    Default: Container Copy

13. Click OK.
14. For Container Copy, enter the container name and/or click the file icon and select a symbolic name.

    Limit: Maximum 64 characters.

    Note: It consists of one or more qualifiers separated by periods, and has a maximum input length of 64 characters, including the periods. When it is translated, it has a maximum length of 44 characters, including the periods.

    Note: For Container Copy, the following occurs during the deployment process:

    1. A file system of the requested type is created.
    2. The size of the file system is computed as follows:
       • The size off all of the constituent files and directories in the local path are added up as bytes.
       • These bytes are converted to tracks and used as the primary allocation value.
       • If there is a non-zero percent of free space entered, it is used to calculate the secondary allocation.
    3. All of the directories in the mount point are dynamically created.
    4. The file system is mounted at the requested mount point.

       Note: The mount is not permanent. You will need to update your BPXPARMS to make this mount point permanent.

    5. The content from the local path is copied into the newly created and mounted file system.

       Note: The asterisk indicates that the field is mandatory.

15. Select the Type of Container from the drop-down list.
16. Enter the Mount Point and/or click the file icon and select a symbolic name.

    Limit: Maximum 255 characters.

    Note: The container is created and it is mounted at a position in the USS file system hierarchy. The place in the hierarchy where it is mounted is known as that containers mount point. Most nodes in the USS file system can be mount points, for any one container.

17. Enter the percentage of Free Space needed.

    The percentage of free space is the amount of space to leave in the file system, after the size has been computed. This is done by specifying secondary space on the allocation. For example, the computed space was determined to be 100 tracks. Then 35 would be 35% free space and the space allocations would be in tracks, 100 primary 35 secondary. While 125 would be 125% over and allocation would be in tracks, 100 primary 125 secondary.

    Limit: 0 to 1000.

18. Click OK.

    The custom data set is added.