Changes for all platforms

• Extended Unicode support

  On all Unicode capable systems, file names, FTAC transfer admissions and follow-up processing may consist of Unicode characters. To permit this, the function "Encoding Mode" has been introduced in order to represent the Unicode names correctly on all involved systems.

  The command interfaces have been extended as follows:

  • All platforms:

    The new field FNC-MODE in the long output of log records displays the encoding mode for the file name (commands ftshwl, SHOW-FT-LOGGING-RECORDS and FTSHWLOG). On BS2000 systems, the OPS variables have been extended by the elements FNC-MODE and FNCCS.

  • BS2000 and z/OS systems (from openFT V12.1C): the new option FILE-NAME-ENCODING supports different character encoding for the specification of remote file names, pre, post and follow-up processing for transfer commands for the following commands:

    • TRANSFER-FILE-SYNCHRONOUS / FTSCOPY

    • TRANSFER-FILE / FTACOPY

    • CREATE-REMOTE-DIR / FTCREDIR

    • DELETE-REMOTE-DIR / FTDELDIR

    • MODIFY-REMOTE-DIR-ATTRIBUTES / FTMODDIR

    • MODIFY-REMOTE-FILE-ATTRIBUTES / FTMOD

    • SHOW-REMOTE-FILE-ATTRIBUTES / FTSHW
    • DELETE-REMOTE-FILE / FTDEL

    • EXECUTE-REMOTE-CMD / FTEXEC

    • EXECUTE-REMOTE-FTADM-CMD / FTADM.

  • Unix systems and Windows systems:

    • New option -fnc in order to set the encoding mode in a file transfer, file management or administration request. This option is available for the commands ft, ftadm, ftcredir, ftdel, ftdeldir, ftexec, ftmod, ftmoddir, ftshw and nopy.The encoding mode is displayed in the output of the following commands (in addition to ftshwl): ftshw and ftshwr (FNC-MODE field).
      The number of not mapped file names is displayed using ftshw -sif.

    • New attribute CmdMode in the configuration of remote administration server to define the (recommended) encoding mode for administered openFT instances. The encoding mode is displayed in the output of the ftshwc command (MODE field).
      This function is also available in the configuration editor of the openFT Explorer.

    • In Unix systems, it is also possible to set the character set which is to be used for inbound requests in character mode. To do this, the new option -fnccs in the ftmodo command has been introduced.

      The character set which is currently set for inbound requests in character mode is displayed in ftshwo, FN-CCS-NAME field.

    • Unicode for C and JAVA

• BS2000 and z/OS systems: for library elements the log records display the element name, type and version in addition to the library name .

• For inbound requests, the long output and CSV output of log records display the address of the partner system in the new field PTNR-ADDR. On BS2000 systems, the partner address is also displayed in the OPS variable PARTNER-ADDRESS.

• Deactivation of the restart functions

  The restart function can be deactivated for asynchronous file transfer requests via the openFT or FTAM protocol. The restart can be set partner-specifically for outbound requests and globally for inbound and outbound requests. To permit this, the following commands have been modified:

  Unix and Windows systems:

  • ftaddptn and ftmodptn: New option -rco

  • ftmodo: New options -rco and -rci

  BS2000 and z/OS systems:

  • ADD-FT-PARTNER/MODIFY-FT-PARTNER and FTADDPTN/FTMODPTN:
    New operand RECOVERY-OUTBOUND

  • MODIFY-FT-OPTIONS and FTMODOPT:
    New operands RECOVERY-OUTBOUND and RECOVERY-INBOUND

• Minimum RSA key length for openFT protocol

  An openFT instance can require a minimum RSA key length for the openFT session encryption. The minimum RSA key length can be defined in the operating parameters. To permit this, the following commands have been modified:

  Unix and Windows systems:

  • ftmodo: New option -klmin

  BS2000 and z/OS systems:

  • MODIFY-FT-OPTIONS and FTMODOPT: New parameters RSA-PROPOSED and RSA-MINIMUM for the KEY-LENGTH operand.

• Minimum AES key length for openFT protocol

  An openFT instance can require a minimum AES key length for the openFT session encryption. The minimum AES key length can be defined in the operating parameters. To permit this, the following commands have been modified:

  Unix and Windows systems:

  • ftmodo: New option -aesmin

  BS2000 and z/OS systems:

  • MODIFY-FT-OPTIONS and FTMODOPT: New parameter AES-MINIMUM for the KEY-LENGTH operand.

• Encryption for file management requests

  For file management requests the file and directory list attributes can be transferred encrypted..This property can also set in admission profiles.

  To permit this, the following commands have been modified:

  Unix and Windows systems:

  • ftshw: New option -c

  • ftcrep and ftmodp: New option -cm

  • ftshwp: New parameter FILE-AT-ENC in the long output and new parameter FileAtEnc in the csv output.

  BS2000 and z/OS systems:

  • SHOW-REMOTE-FILE -ATTRIBUTES and FTSHW:
    New operand FILE-ATTR-ENCRYPTION

  • CREATE-FT-PROFILE and MODIFY-FT-PROFILE as well as FTCREPF and FTMODPRF: New operand FILE-ATTR-ENCRYPTION

  • SHOW-FT-PROFILE and FTSHWPRF: New parameter FILE-AT-ENC in the long output and new parameter FileAtEnc in the csv output.

For getting multiple files form the remote system using ft_mget, GET-REMOTE-FILES or FTMGET the encryption option (-c or DATE-ENCRPTION) also applies to file and directory list attributes.
• From openFT V12.1C the CRYPT functionallity is integrated in openFT. Therefore openFT-CR is no longer delivered.

Changes in openFT version V12.1C10:

• For local outbound requests, the long output and CSV output of log records display the remote filename in the new field REMOTE-FN. On BS2000 systems, the remote filename is also displayed in the OPS variable F-REM-NAME.