Setting Up System Registry › Data Destinations › Maintain Data Destinations

Maintain Data Destinations

You can maintain, delete, or create data destinations.

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.

   Note: A grayed select field indicates that the data destinations are assigned and cannot be removed. The field can be edited.

2. Select Edit from the Actions drop-down list for the data destination you want to change.

   The Edit Data Destinations dialog appears.

   Note: The asterisk indicates that the field is mandatory.

3. Update the following information 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).

   Storage Class

   (Shared DASD only) Enter the Storage Class.

   Limits: Maximum eight characters

   Example: SYSPRG

   VOLSER

   (Shared DASD only) Enter the Volser.

   Limits: Maximum six characters

   Example: SYSP01 and SYSP02

   GIMUNZIP Volume

   Enter the GIMUNZIP volume.

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

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

   The updated data destination appears on the list of data destinations.

   Note: Click Cancel to withdraw this change request.