Package Ship Facility › How to Enable Package Ship › Create a Destination

Create a Destination

You must define at least one destination for each remote site to which you plan to ship package outputs. CA Endevor SCM stores destination information in the package data set. Destinations can be defined for data sets or the USS supported file types HFS, zFS, or NFS.

Follow these steps:

1. Select option 4-Environment on the CA Endevor SCM menu.

   The Environment Options Menu.

2. Select option D- Destination on the Environment Options Menu. Then press Enter.

   The Destination Options Menu opens.

3. Select 2-Build. Type a fully qualified destination name in the Destination field. Press Enter.

   A Create/Modify Destination panel opens.

4. Complete the information on the panel. Then press Enter. This panel includes the following fields:

   DESTINATION

   Specifies a data set name or a USS supported path and file name.

   • For a data set name, the value can be a maximum of seven characters. The first character must be alphabetic. Remaining characters can be alphabetic or national.
   • For a USS system file, the value can be up to a 732-byte path name.

   DESCRIPTION

   Specifies a maximum 30-character description for the destination, which is treated as a comment.

   SHIP COMPLEMENTARY DATASETS

   Specifies whether to ship complementary data sets. When package outputs are shipped to a destination, a second set of staging data sets can be requested. These data sets are called complementary data sets and contain a backout of the shipment. For example, if a shipment contains the output of package A, then the complementary data sets contain the backout for package A. Conversely, if a shipment contains the backout for package B, then the complementary data sets contain the outputs for package B. Acceptable values are as follows:

   • N—Default. Do not ship complementary data sets.
   • Y—Ship complementary data sets.

   TRANSMISSION METHOD

   Specifies the transmission utility for this destination. Acceptable values are as follows:

   • XCOM—XCOM (CA)
   • B—Bulk Data Transfer, Version 2 (IBM)
   • BDTN—Bulk Data Transfer via NJE/NJI (IBM)
   • L—Local
   • NVF—NetView File Transfer Program (IBM)
   • NWD—CONNECT:Direct

   REMOTE NODENAME

   Specifies a 1-to 16-character nodename to which package outputs are to be shipped. The name must be valid for, and defined, to the chosen data transmission program. Nodename has no meaning for BDT via NJE/NJI and for local transmissions.

   REMOTE IPNAME/IPPORT

   Specifies the XCOM SERVPORT specification of the target server to which package outputs are to be shipped. IPname can be 1 to 63 characters. IPPORT can be 1 to 5 characters and range from 1 to 65535. The IPNAME and IPPORT specification is only valid for the XCOM transmission method.

   Note: For XCOM, you must specify either the IPNAME/IPPORT or the NODENAME, but not both.

   Staging Information For Data Sets

   The user must provide a prefix for the staging data sets that CA Endevor SCM builds in the first step of the ship utility. This prefix can be 1 to 14 characters, and can be different for the host and the remote sites. The prefix appears in the DSN PREFIX field, and defaults to TSOuserid.NDVR.

   Acceptable values for the other staging data set fields are shown in the following:

   Disposition

   Delete or keep. When DISPOSITION=DELETE, CA Endevor SCM includes a step in the host and/or remote JCL streams to delete the staging data sets after they have been processed. Acceptable values are:

   D—Default. Delete staging data sets

   K—Keep staging data sets

   All staging data sets are initially cataloged. Keep/Delete refers to the final disposition of:

   –Host staging data sets after they have been transmitted.

   –Remote staging data sets once they have been copied to their production counterparts.

   Unit

   Specifies the unit designation to be used when allocating staging data sets. Default is SYSDA.

   Volume Serial (Optional)

   Specifies the VOLSER to be used when allocating staging data sets. There is no default value.

   Staging Information For UNIX System Services files

   If USS files are to be shipped for this destination, host and remote path name prefixes must be specified.

   Host Path Name Prefix

   Specifies a one- to 732-byte prefix for the host path name. The prefix can be different for the host site and the remote site. The default, if not specified, is "/tmp/".

   Remote Path Name Prefix

   Specifies a one- to 732-byte prefix for the remote path name.The prefix can be different for the host site and the remote site. The default, if not specified, is "/tmp/".

   Remote Job Statement Information

   These fields provide the job card for the remote JCL execution. A ROUTE XEQ card or equivalent should be included if the transmission method is either BDT via NJE/NJI or local.

   The destination is created.