Installing Your Product Using CA MSM › Setting System Registry › Data Destinations › Create Data Destinations

Create Data Destinations

You can create data destinations A data destination must be defined for every system. The data destination is how you tell CA MSM which technique to use to transport the deployment data to the remote system. Data destinations are assigned to Non-Sysplex systems, Sysplexes, and Shared DASD Clusters. Data destinations are named objects, and thus can be assigned to multiple entities in the system registry and have their own independent maintenance dialogs. that define the method that CA MSM uses to transfer the deployment data to the 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.

   Note: The asterisk indicates that the field is mandatory.

3. Enter the following and click Save:

   Name

   Enter a meaningful name.

   Limits: Maximum 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: Maximum 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: Maximum 120 characters

   Note: SMS is not mutually exclusive with non-SMS. They can both be specified (usually one or the other is specified though). This is where you specify allocation parameters for the deployment on a target system.

   Storage Class

   (Shared DASD only) Enter the Storage Class.

   Limits: Maximum 8 characters

   Example: SYSPRG

   VOLSER

   (Shared DASD only) Enter the Volser.

   Limits: Maximum 6 characters

   Example: SYSP01 and SYSP02

   GIMUNZIP Volume

   Enter the GIMUNZIP volume.

   Limits: Maximum 6 characters

   zFS Candidate Volumes

   Enter zFS Candidate volumes.

   Limits: Maximum 6 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.

   Note: Click Cancel to withdraw this create request.