Open topic with navigation

TIBCO® Managed File Transfer Platform Server for z/OS 8.1.0

# Transfer Interface Definition

By using Transfer Interface definition, you can specify the definitive encryption algorithm for a single transfer request.

Note: For a particular transfer request, Transfer Interface definitions always override any GLOBAL definitions and NODE definitions.

TIBCO MFT Platform Server for z/OS provides the following three user interfaces for transfer:

- ISPF
- REXX
- Batch

The REXX and Batch interfaces use the same encryption parameter. In addition, the generalizations made about the REXX and Batch interfaces must be also applied to the ISPF interface. See Interactive Interface for more information about the ISPF interface.

The format of Transfer Interface definition is as follows:

    ENCRYPT={NONE | AES | AES128 | DES | 3DES | BLOWFISH | BLOWFISH_LONG | AES}

This parameter specifies the level of encryption that is used by a particular transfer request. The following table lists the description of each parameter option:

Option | Alternate Specification | Description
--- | --- | ---
`NONE` |  | No encryption is used. This is the default setting.
`AES` |  | AES 256-bit encryption is used.
`AES128` |  | AES 128-bit encryption is used.
`DES` |  | DES encryption is used. For more information of DES encryption, see DES Encryption.
`3DES` |  | Triple DES encryption is used.
`BLOWFISH` | `BF` | Blowfish 56-bit encryption is used. For more information of Blowfish encryption, see Blowfish Encryption.
`BLOWFISH_LONG` | `BFL` | Blowfish 448-bit encryption is used.
`AES` | `RJ/AES` | AES 256-bit encryption is used. For more information of AES encryption, see AES Encryption.

For Transfer Interface definition, you can use the PASSONLY parameter to specify whether to encrypt both the password and data or just encrypt the password. This parameter has the following two valid values:

- `YES`: Only encrypts the password. Data is not encrypted.
- `NO`: Encrypts both the password and data. This is the default value of the PASSONLY parameter.

Note: The PASSONLY parameter is only valid for file transfers between z/OS and z/OS systems.

## Examples Using Transfer Interface Definition

The following examples show how to use Transfer Interface definition to specify a definitive encryption algorithm for a single transfer request.

Note: When the PASSONLY parameter is not defined, its default value, `NO`, is used.

Example 1:

    ENCRYPT=NONE

The Platform Server encrypts the password by using a proprietary algorithm. Data is not encrypted.

Example 2:

    ENCRYPT=BLOWFISH or ENCRYPT=BF

The Platform Server encrypts both the password and data by using Blowfish 56-bit encryption algorithm.

Example 3:

    ENCRYPT=AES

The Platform Server encrypts both the password and data using the AES encryption algorithm.

Copyright © 2003-2021. TIBCO Software Inc. All Rights Reserved.