Hotfix CZ02035 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/zOS/7.2.0/” to download the hotfix.
 
The .zip file has the Readme file inside. Please unzip the file and review the Readme file for instructions on how to apply the hotfix.
 
PreReq HotFix: CZ02021
Supersedes:    CZ02028
 
Note: Hotfix CZ02021 MUST be applied before applying this hotfix.
 
Problem Description:
This hotfix resolves defects that have been fixed since hotfix CZ02028
was released.
 
Defects fixed in CZ02035:
PSZ-281 %YDATE and %YGDATE Script variables can return an incorrect date
PSZ-280 Abend 0E0 received in module OSIAINT0 due to corrupted AR6
PSZ-278 Transfer fails with error "PGTM7344E" after altering the start
        time of a transfer through the ISPF interface
PSZ-277 After upgrading to z/OS 2.2, a 0E0 abend occurred in FUSASNAR+6232
        due to a corrupted AR15
PSZ-276 Script interface received error: "PGTS4204E OSIUC000 Parameter
        error on SYSIN record" after applying hotfix CZ02028
 
Defects fixed in CZ02028:
PSZ-274 After upgrading to z/OS 2.2, intermittent abends occurred in
        module OSINBDAP due to corrupted AR15
PSZ-272 Two modules incorrectly used 24 bit storage; changed to use
        31 bit storage.
PSZ-271 Highly utilized systems received message:
        PGTS0023I LOG Slot full: Overwriting previous message in log file
                  In=xxxxxxxx Out=yyyyyyyy
PSZ-270 Created scripting variables for yesterday's date.  The following
        new script variables were created and reflect one day prior to
        the current date at the time of execution.
         : %YDATE     CCYYDDD
         : %YGDATE    CCYYMMDD
         : %YGDATE1   1YYMMDD
         : %YGDATE2   YYYYDDMM
         : %YGDATE3   MMDDYYYY
         : %YGDATE4   DDMMYYYY
PSZ-267 PPA SUBMIT fails due to Dynamic Allocation failure allocating
        source JCL dataset.
        Note: Additional debugging messages were added to identify the
              job holding the ENQ on the source JCL dataset
PSZ-265 When executing a directory RECEIVE with an IPName > 24 characters,
        the transfer fails with error:
        PGTF3213E Receive Directory Failed: Network error on ALLOC
PSZ-262 Received intermittent abend 0E0 in OSIADIR0+15F0 when executing
        Directory Transfer
PSZ-261 When a Job or DNI uses TRANS_TYPE=JOB, the PPA %LFILE token is not
        resolved correctly
 
Defects fixed in CZ02025:
PSZ-260 Unable to delete or update files when the file expiration date is
        set to PERMANENT or to a future date
        Added the following GLOBAL parameters:
        UNEXPIRED_DISK_FILE_DELETE={YES|NO}
        Defines whether MFT will allow Receive Transfers defined with
        a disposition of DNEW to delete a file that has not expired:
        YES: Allow MFT to delete unexpired files when DISP=DNEW
        NO:  Do not allow MFT to delete unexpired files when DISP=DNEW
             No is the default value
        UNEXPIRED_DISK_FILE_UPDATE={YES|NO}
        Defines whether MFT will allow Receive Transfers to update
        a file that has not expired:
        YES: Allow MFT to update unexpired files
        NO:  Do not allow MFT to update unexpired files
             No is the default value
        Note: If this parameter is set to YES, message IEC507D will
              be displayed and will wait for an operator response.
              Until the operator responds, subsequent dynamic allocations
              will hang.  We suggest not setting this parameter to YES
              unless you have defined an automatic response to the IEC507D
              message.
PSZ-259 Receive error when following Process Statements are defined:
          FILE_EXPDT=1999365 or FILE_EXPDT=99365
          FILE_EXPDT=1999366 or FILE_EXPDT=99366
        PGTB4102E Invalid parameter value in next record
PSZ-258 Command Center detects Protocol Error when SSL Audit Poll or
        Collection request returns 0 records
PSZ-257 When GLOBAL ENFORCE_SECURITY_POLICY set to FIPS140, the MFT STC
        displays message PGTS1393E and terminates
        A new value was added to parameter to ENFORCE_SECURITY_POLICY:
            ENFORCE_SECURITY_POLICY=TLSFIPS
        This value ensures that all SSL/TLS connections are executed
        using FIPS 140 protocols and ciphers, but will not require the
        entire STC to execute in FIPS 140 mode.
PSZ-256 When using the ISPF panels and specifying an IPV4 IP Address as
        the Remote System name, the connection fails with a connection
        error to IP Address 0.0.0.0