Setting Up System Registry › Data Destinations › Create Data Destinations

Create Data Destinations

You can create data destinations that define the method that CA CSM uses to transfer the deployment data to the nonstaging target systems.

Follow these steps:

1. Click the System Registry tab, and in the Actions section click the Maintain Data destinations link.

   The Maintains Data Destinations dialog appears.

2. Click Create.

   The New Data Destination dialog appears.

3. Enter the following information, and click Save:

   Name

   Enter a meaningful name.

   Limits: 64 characters

   Note: Each data destination name must be a unique name and it is not case-sensitive. For example, DATAD1 and datad1 are the same data destination name.

   Description

   Enter the description.

   Limits: 255 characters

   Transmission Method

   Select the transmission method.

   Default: Shared DASD

   Mount Point

   (Shared DASD only) Enter the mount point directory path, which is a directory path that must exist on the target system. The user that is doing the deployment must have write permission to this directory, and mount authorization on the target system.

   Note: A mount user must have UID(0) or at least have READ access to the SUPERUSER.FILESYS.MOUNT resource found in the UNIXPRIV class.

   Limits: 120 characters

   Note: SMS is not mutually exclusive with non-SMS. They can both be specified (usually one or the other is specified, though).

   Storage Class

   (Shared DASD only) Enter the storage class.

   Limits: Eight characters

   Example: SYSPRG

   VOLSER

   (Shared DASD only) Enter the VOLSER.

   Limits: Six characters

   Example: SYSP01 and SYSP02

   GIMUNZIP Volume

   Enter the GIMUNZIP volume.

   Limits: Six characters

   Catalog Data Sets

   Specify if deployed data sets are cataloged on the target system.

   Note: If you set this field to YES, fill in the GIMUNZIP Volume field.

   Unit

   Enter the unit where the deployed data sets are allocated.

   • If you set the Catalog Data Sets field to YES, the specified unit is used for allocating all deployed data sets.
   • If you set the Catalog Data Sets field to NO, the specified unit is used for allocating empty data sets only.
   • If you do not define Unit, SYSALLDA is used.

   zFS Candidate Volumes

   Enter zFS candidate volumes.

   Limits: Six characters

   The zFS candidate volumes allow the specification of an optional list of VOLSERs used during the allocation of zFS container data sets for USS parts.

   The new data destination appears on the Data Destination list.