Configuring and Customizing Your Product › Define Destinations › Why Define Destinations?

Why Define Destinations?

Destination definitions are needed for the following reasons:

Note: XCOMPLEX destination members are no longer required and are not recommended. Connectivity is created automatically between the XCOMPLEX Admin and XCOMPLEX Worker Servers. Support for these types of members is provided only for compatibility with prior releases.

• They allow the CA XCOM Data Transport default parameters to be overridden.

  Several CA XCOM Data Transport parameters can be used both in the CONFIG member (or Default Options Table) and in the CA XCOM Data Transport control library. The parameters defined in the CA XCOM Data Transport control library take precedence over their counterparts in the CONFIG member because of the parameter evaluation hierarchy that CA XCOM Data Transport uses.

  A parameter P is assigned the value X in the CONFIG member (P=X) but a different value Y in a control library member (destination definition). When CA XCOM Data Transport performs a transfer and the XCOMCNTL destination member containing P=Y is enabled, CA XCOM Data Transport considers the P definition in the control library member and the definition in the CONFIG member is ignored. When CA XCOM Data Transport performs a transfer and the destination definition containing P=Y is disabled, CA XCOM Data Transport reads the P definition from the CONFIG member and the definition in the control library member is ignored.

• They allow trusted transfers to z/OS to be performed.

  A trusted transfer allows a remote partner to send a transfer without specifying a password. Instead, the user id of the incoming transfers is compared against any TRUSTID table entries in an XCOMCNTL destination member. For more information, see Set Up Trusted Access Security in chapter 3.

• They allow indirect transfers to be performed.

  An indirect file transfer occurs when CA XCOM Data Transport is used as an intermediate node to pass data between two LUs that are not directly connected with each other. In such a transfer, CA XCOM Data Transport stores the data received from one system and forwards it to another system.

• They are required to provide access to the CA XCOM Data Transport Process SYSOUT (PSO) interface.

  The CA XCOM Data Transport PSO interface allows output from non-CA XCOM Data Transport jobs to be forwarded from the JES queue to remote destinations.

• They allow multiple LUs to be defined as transfer destinations.

  A multi‑LU destination is either a group or a list. For a definition of the difference between these destination types, see Group Versus List Destinations in this chapter.

  Note: IP names require destination definitions if you want to override the parameters for that partner.