Node Parameters

The following tables list parameters supported for the cfnode command.

Required Node Parameters to Create a Node

Note: If any of the required parameters is not defined and the prompt parameter is set to No, the cfnode command fails to create a node.

The following table lists the required parameters for the cfnode command.

Parameter (Alternate Specification) Description
HostName (h) Defines the IP name or IP address of the node.

This value can be either the IP address of the remote machine or a resolvable host name or DNS entry.

Multiple IP names or IP address can be defined, separated by a comma. When more than one IP name or IP address is defined, the following rules apply:

  • For initiator requests (that is, cfsend/cfrecv), only the first IP name or IP address is used.
  • For responder requests, when the Platform Server responder is checking for a match on the node name, each IP name or IP address is checked for a match. This feature is typically used when you want to use the same node and responder profile for incoming request from multiple platform servers.

Node (n) Defines the node name you want to add or update to the cfnode.cfg file.

The maximum length of the defined value is 256 characters, and it cannot contain any spaces.

Note: The node name is not case-sensitive.

Port (p) Defines the port number on which the remote node is listening for incoming transfer requests.
SystemType (s) Defines the system type of the node.

The valid values are SUNOS/SOLARIS, AIX, LINUX, Windows, IBMi, z/OS, Command_Center, and other system types.

Optional Node Parameters to Create a Node

Note: The cfnode command does not require any of the optional parameters to be defined if the prompt parameter is set to No.

The following table lists the optional parameters for the cfnode command.

Parameter (Alternate Specification) Description
Action (a) Defines the action you want to take with the specified node.

The valid values are Delete, List or Add.

CommandSupport (ccc) Defines the actions that the TIBCO MFT Command Center can perform on this node.

The valid values are:

  • ALL: NODE, PROFILE, AUDIT, PING,and TRANSFER are supported on this node.
  • NONE: no Internet Server function is supported on this node. This is the default value.
  • AUDIT: requests that access to the TIBCO MFT Platform Server audit file are supported on this node.
  • NODE: node list and update functions are supported on this node.
  • PING: the TIBCO MFT Platform Server fusping request is supported on this node.
  • PROFILE: profile list and update functions are supported on this node.
  • TRANSFER: TIBCO MFT Command Center transfer function that initiates file transfers is supported on this node.
  • ALTER: When Alter is set in the CC Node definition, then any incoming Command Center request to cancel an active transfer by its TRN is allowed. If this option is not set, then such a request is rejected. ComanndCenter=ALL does not include Alter.
    Alter must be added explicitly. For example:
    ComanndCenter=ALL,Alter
Compression (c) Defines the compression type for all transfers with this node.

The valid values are:

  • LZ: Limpel-Zev compression. This is not recommended due to its high CPU usage.
  • RLE: Run Length Encoding (RLE) compression.
  • ZLIB: ZLIB1 through ZLIB9. This is recommnded as it causes an optimum balance between efficient compression and low CPU usage. ZLIB2 is recommended.
  • NO: no default compression.
  • NEVER: never use compression.

Note: NEVER is the only value that cannot be overridden by cfsend or cfrecv on the command line.

CRC

- (Yes | NO | Default)

Defines whether a Cyclic Redundancy Check (CRC) is performed for transfers initiated to this node.

The valid values are:

  • Yes: performs CRC checking.
  • No: bypasses CRC checking. The default value is No.
  • Default: uses CRC value from config.txt

Description (d) Defines a text description of the node.

The maximum length of the defined value is 256 characters. If the description contains spaces, then the description must be encapsulated in double quotation marks.

Encrypt (e) Defines the encryption type for all transfers with this node.

The valid values are:

  • DES: 56-bit encryption.
  • 3DES: triple DES, 112-bit encryption.
  • BF: Blow Fish encryption, 56-bit encryption.
  • BFL: Blow Fish Long, 128-bit encryption.
  • AES: AES/Rijndael, 256-bit encryption.
  • AES128: 128-bit encryption.
  • NO: no encryption.
  • NEVER: never uses encryption.

Note:

NEVER is the only value that cannot be overridden by cfsend or cfrecv on the command line.

AES128 is supported for transferring files to z/OS only. Since AES provides superior 256-bit encryption, it is a good practice to use AES.

When using encryption, AES encryption is recommended due to its high level of security and efficient encryption.
LocalCTFile (lct)

Defines the name of the local conversion table (local translation file).

This parameter is used to translate data on the local side.

The valid values areNo or None or Translation File Name.

When LCT file is given, custom A<->E translation is used.

When LCT is No, the default A<->E translation is used.

When LCT is None, then no ASCII < - > EBCDIC translation is performed on this system.

The maximum length of the defined value is 16 characters.

NetMask (net) Defines the netmask that is applied to the remote IP address.

This parameter is defined so that you can use any IP in the specified subnet. Netmask is used to validate incoming requests against an IP address subnet, rather than against a specific IP address.
NetMask6 (net6) Defines the netmask that is applied to the remote IPv6 address.

The valid values are a number between 8 and 128 and a multiple of 8. Netmask6 is used to validate incoming requests against an IPv6 Address subnet, rather than against a specific IP address.
Prompt Defines whether to activate the cfnode command to an interactive mode.

The valid values are:

  • Yes: cfnode prompts the user for all information required to create a node. This is the default value.
  • No: cfnode does not prompt the user for all information required to create a node.

RemoteCTFile (rct) Defines the name of the remote conversion table (remote translation file).

This parameter is used to translate the data on the remote side. Valid values are filename and No. The maximum length of the defined value is 16 characters.

Responder (r) Defines whether to use a responder profile for this node.

The valid values are:

  • Yes: Check the responder profiles and do not try to log on with the remote user ID and password that are sent with the transfer request.
  • No: Do not check the responder profiles. Validate the credentials against the operating system credentials.
  • Dual | D: First, validate the credentials against the responder profiles. If no match is made, validate the credentials against the operating system credentials.
  • Do not define: ResponderProfile value from config.txt will be used.

Security (sl) Defines the security policy this node complies with.

The valid values are:

  • Default: follow what is defined for the Security Policy parameter in the $CFROOT/config/config.txt file.
  • HIPAA: comply with HIPAA standards.
  • None: not comply with any security policy.

TLS/SSL

Either T (Tunnel), No, or Yes depending on whether remote node requires a TLS/SSL connection.

The valid values are:

• No: SSL mode is not used for initiator requests
• Yes: SSL Mode is used for initiator requests
• T: TLS Tunnel mode is used for initiator requests

The TLS/SSL parameter is ignored for responder/incoming requests.
Verify (v) Defines whether a remote verified user can log on to TIBCO MFT Platform Server using only the remote user ID without a password.

TIBCO MFT Platform Server recognizes the client as verified if the client sends an internal password in the password field.

To enable this feature, the user on the client side has to provide the following parameters:

  • Userid: *VER
  • Password: this field must be left blank.

/? or -? Displays online help for the cfnode command.