Hotfix TIB_mftps-unix&zlinux_8.0.0_HF-008_linux can be downloaded from TIBCO Support Portal (https://support.tibco.com).  

You will need to provide your TIBCO Support Portal credentials.  Once logged in you can download the hotfix by selecting the “Downloads” -> “Hotfixes” option. Then go to “/AvailableDownloads/MFT/ PlatformServer/UNIX-zLinux/8.0.0/hotfix-08/” to download the hotfix.

The folder has the Readme file inside. Please review the Readme file for instructions on how to apply the hotfix.

Introduction

This is the eighth hotfix for TIBCO Managed File Transfer (MFT) Platform Server
for Linux 8.0.0.  This is a cumulative hotfix and includes all generally
available fixes for TIBCO Managed File Transfer Platform Server for Linux 8.0.0.

================================================================================
Closed Issues in 8.0.0_HF-008 (This Release)

PSU-958
When a transfer set utf8bom:BOTH, the utf8bom settings were not correctly sent
to Platform Server for z/OS.

PSU-956
When transferring a file, if the filename contained the '%' characters, the PPA
functions that referenced the %LFILE token failed because the file name was
corrupted.

PSU-954
If the Log.txt file TLSProtocol and TLSCipher parameters contained corrupted
data, the Command Center Collection and Audit Poll failed with a core dump.

PSU-953
When a directory list command failed because a file or directory did not exist,
the transfer audit record was written as a failed transfer.

PSU-952
When a directory Send or Receive found 0 files to transfers, there was no
option to make this a successful transfer.
The following config.txt [CLIENT] parameter can be added to the config.txt:
DirTransfer0Files:      F                           { Failure|F, Success|S }
The following Template Parameter was added (TSEND, TRECV)
DirTransfer0Files:       F                           { Failure|F, Success|S } 
The following cfsend/cfrecv CLI parameter overrides the config.txt
parameter:
DirTransfer0Files:{S|F}   Shortcut: d0:{S|F}

PSU-897
When partial values on components of the certificate parameters were compared,
SSLAuth certificate incorrectly validated the authentication.

PSU-886
When Command Center executed a Platform Server transfer using the
'Add/Execute Platform Transfer' option, the command type parameter was
incorrectly validated and some transfers were not submitted.

PSU-865
When sending a single file from the current directory and the remote file name
specified *, the remote file name could be corrupted.

PSU-830
When the config.txt "RequiredNodeDefinition" parameter was set to "Y", the user
was not able to use wildcards in the "lf" and "rf" parameters.

PSU-813
When a load balancer initiated an SSL request to the Tunnel port and
"Check Client Certificate:" was not enabled, the Platform Server Service
CPU utilization was very high.

================================================================================
Closed Issues in 8.0.0_HF-007

PSU-812
When a directory receive request using a template was initiated and the
remote file name was a Universal Naming Convention (UNC) path that contained
multiple forward slashes (/) or backslashes (\), a core dump occurred and
the transfer failed.

PSU-809
When Daylight Savings Time returned to Standard time, BW initiated
"Wait for Platform Transfer Completion" requests failed with the
Command Center error: "Failed to obtain a unique transfer status record."

PSU-808
Transfers initiated by Platform Server for UNIX to Platform Server for z/OS
failed intermittently with an authentication failure.

================================================================================
Closed Issues in 8.0.0_HF-006

PSU-799
When maximum transfers for one day exceeded 1296999, the transaction number
for subsequent transfers was corrupted.

PSU-778
The CRC value specified for the transfer on the command line did not override
the global CRC value specified in the config.txt file.

PSU-768
When Platform Server for z/OS initiated a transfer with Platform Server
for UNIX and set "CRC=NO", Platform Server for UNIX incorrectly turned on
CRC processing.

PSU-746
When a UNIX-initiated send transfer restarted, the target file was corrupted
or the transfer failed.

PSU-743
Even when checkpoint restart was turned off, PQF files were created.

PSU-730
When a log.txt record was truncated, Command Center Collection caused
an exception.

PSU-728
When a send command was executed and the remote command was a Platform Server
command that included a PPA, an invalid character was added to the end of the
PPA causing the remote command to fail.

PSU-693
When Platform Server for UNIX restarted a transfer with CRC turned on,
the restart failed with the error message, "CRC Validation Failed."

================================================================================
Closed Issues in 8.0.0_HF-005

PSU-710
When files were transferred with AES encryption, the target file could be
corrupted.

================================================================================
Closed Issues in 8.0.0_HF-004

PSU-701
Tokens such as $(RemoteFileBase), $(RemoteFileExt), $(LocalFileBase),
and $(LocalFileExt) resolved incorrectly.

PSU-700
A Post Processing Action (PPA) with a long file name caused an exception, and
the PPA was not executed.

================================================================================
Closed Issues in 8.0.0_HF-003

PSU-691
Platform Server was unable to extract group membership for Active Directory
users when the Linux SSSD parameter was "ignore_group_members=True".
Note: This fix applies only to the Platform Server for Linux.

PSU-690
When TIBCO MFT Platform Server for Windows 7.2.0 sent a 0-byte file to
TIBCO MFT Platform Server for Unix 8.0.0, the transfer failed with the
message:
"File to File transfer failed."
"Failed sending error notification to partner:"
"An error occurred receiving data from partner. (d)"

================================================================================
Closed Issues in 8.0.0_HF-002

PSU-635
When the RequireNodeDefinition parameter in the config.txt of the client was set
to "Yes", initiator transfers to a node failed with the message:
"config.txt: node file does not exist".

PSU-634
When an incoming transfer was received and a node definition was not created
for the incoming IP address, the IP address/node name on the audit record
was set to "NULL".

PSU-518
When a UNC directory was received from Platform Server for Windows with
ScanSubdirectory set to "Yes", the $(SDIR) token was not resolved correctly.

================================================================================
Closed Issues in 8.0.0_HF-001

PSU-626
The TLS session negotiation failed when elliptical curve ciphers were used in
SSL or tunnel mode.

PSU-625
When the ProcessName parameter was 8 bytes long and the user data was defined,
connections to TIBCO(R) Managed File Transfer Internet Server failed with the
message: "the length is too long for ProcessName."

PSU-624
When sending a single file from the current directory with the remote file name
specified as asterisk (*) , the remote file name was set to the asterisk
character instead of the local file name.

PSU-610
Tunnel transfers failed when HIPAA=Yes was defined in the node definition.

PSU-609
When a user set the Using SSL field to "SSL" in the the Add Platform Node or
Update Platform Node page of TIBCO Managed File Transfer Command Center, the
node definition was created as TLS tunnel node instead of SSL node.

================================================================================