TIBCO Managed File Transfer Platform Server for z/OS hotfix CZ01923 is now available

TIBCO Managed File Transfer Platform Server for z/OS hotfix CZ01923 is now available

book

Article ID: KB0104731

calendar_today

Updated On:

Products Versions
TIBCO Managed File Transfer Platform Server for zOS -
Not Applicable -

Description

Description:
This is a cumulative hotfix that resolves defects and includes defects
resolved in prior hotfixes.  It supersedes all prior hotfixes for
release 7.1.0.

Defects fixed in CZ01923:
PSZ-80  Receive intermittent abend 0C4 in module FUSIONIO on EOV
        (End of Volume) processing when new tapes are mounted.
PSZ-79  Receiving PGTF4684E out of space errors on transfer of VSAM
        KSDS datasets from the ISPF interface.
PSZ-78  Transfer fails but still catalogs GDG generation when
        RDISP=(NEW,CATLG,DELETE) is specified
PSZ-75  Resolved two issues with space allocation on VSAM files:
        1.  When sending a VSAM file, space used was calculated
            incorrectly.
        2.  When creating a VSAM file with kilo-byte or mega-byte
            allocation, the file is allocated with too much space.
PSZ-73  Fix problem where transfers received abend 013-E1 when
        transferring LBI tape files when CKPT restart is turned off.
PSZ-72  Quotes are incorrectly removed from from the Remote command
        parameter.
PSZ-71  Made changes to the FILE_EXPDT parameter(YYDDD or CCYYDDD).
        : Allow the user to enter 000 for the DDD
        : When a 5 digit date (YYDDD) is entered, set CC to 20
PSZ-70  When initiating a file transfer and the Local file is not
        defined, the started task can receive an abend 282.
PSZ-68  When initiating a directory send or directory receive, VSAM
        files were not transferred.  Two new parameter values were
        added to the SUBDIR parameter.
        : SUBDIR=ALL       Include Sequential, PDS and VSAM files
        : SUBDIR=SEQVSAM   Include Sequential and VSAM files
PSZ-66  When initiating a receive for a DBCS file and the XLATE table
        is defined as SOSI=NONE, an 0C4 or S378 exception can occur.
PSZ-64  When MFT transfers a file with RECFM=VBS and LRECL&gt32760,
        the receiving file is created with LRECL=32760 and no
        informational message is generated indicating the change
        to the LRECL.
PSZ-54  When Command Center collects Audit records from zOS Platform
        servers, the Node Name is truncated to 8 characters.
PSZ-53  When a transfer is executed with DISP=DNEW and the request fails
        because the target file is in use, the transfer is not retried
        and no message is displayed indicating the cause of the failure.
PSZ-47  When checkpoint restart is turned on for RECFM=V/VB transfers,
        the blocksize is not filled to its maximum.  This causes
        more space to be used and sometimes causes an x37 abend.
PSZ-15  Message PGTE3840I Rename target DSN can be truncated.

Defects fixed in CZ01916:
PSZ-45: Added the following GLOBAL Parameter:
        TAPE_SECURITY_EXIT={ERROR|IGNORE}
        Defines the processing when the SMS Tape Security Exit is
        invoked when a tape is mounted that has not expired:
        ERROR:  Reject the tape mount.  The transfer is terminated
                with an abend 913-34.  This error is considered a
                retry-able error.  This is the default value.
        IGNORE: Performs the default SMS operation.  Some tape
                management products will accept the tape mount.
                Others will take the SMS default and ask for a new
                tape mount.
PSZ-44: Receive the following message when an error is detected on
        a UNIX or Window platform and the error message returned is
        longer than 240 bytes:
           PGT1004E TLV VARIABLE 0004 - INVALID LENGTH
        Messages longer than 240 bytes will now be accepted and
        truncated to 240 bytes.
PSZ-43: Resolve an 0C9 abend that can occur when the NODE BPS_SEND or
        BPS_RECV parameters are defined to limit the bandwidth used.
        This problem occurs intermittently when these parameters are
        set to a value greater than 20,000,000, although it is possible
        to receive this abend when the values are set lower.
PSZ-42: When a Send transfer is initiated and the local file is not
        found, the transfer will terminate before starting the connection
        to the transfer partner.  An Audit record will be written.
        Prior to this change, the transfer was initiated to the partner.

Defects fixed in CZ01903:
PSZ-41: Platform transfers initiated by Command Center fail when using a
        Responder Profile on z/OS
PSZ-38: Resolves a 0E0 abend in module FUSASEND when Access Register 1
        is corrupted by 3rd party software.
PSZ-37: Resolves a problem when an error message is received from a
        transfer partner that exceeds 120 bytes, the message displayed
        is truncated at 120 bytes.
PSZ-35: Display a more descriptive message when abend 913-34 is received.
PSZ-34: Resolves problems with the following parameters when collected by
        MFT Command Center: Delimiter(LF) and Type (Text/Binary).
PSZ-33: Resolves a problem where Active and Inactive transfers were
        incorrectly returned on the ISPF "Manage File Transfers" page when
        the Remote Transaction Number was entered.
PSZ-32: Resolves a problem where message "PGT1002I" is displayed when
        initiating a request to a Windows Platform Server.
PSZ-31: Resolved problem on the ISPF Transfer Audit detail page where the
        Compressed Byte count is displayed incorrectly when the compressed
        byte count exceeds 2GB.
PSZ-25: Added support to the FUSUTIL utility to DELETE or RENAME migrated
        datasets.
PSZ-22: Resolved a problem with managing a z/OS Platform Server from
        Command Center when the z/OS password has lower case characters.
PSZ-16: Adds new Transfer parameter: CRLF=USSLF.
        This parameter allows you to send a z/OS DSN to a z/OS USS file
        and terminate the USS file records with an ASCII LF (0x0A).
PSZ-13: Resolved a problem where message PGTM7247E was incorrectly issued
        when the local file name was too long.
PSZ-8 : Resolved a problem with corrupted data when the following parameter
        is specified:
        SENDRECFMU=NOBDW
        This parameter is now restricted to files with RECFM=V or VB.  If
        this parameter is used on a file with a different RECFM value, the
        transfer will be terminated with an error.

Defects fixed in CZ01900:
PSZ-8 : Added a new value to the batch SENDRECFMU parameter: NOBDW
  SENDRECFMU={YES|NO|NOBDW}   Default=NO
  : When YES is specified for a SEND, the file will be opened using
    RECFM=U.  Each block will be written as an individual record.  The
    main usage of this parameter is to retain the RECFM=VB block and record
    structure when sending to a UNIX or Windows platform.
  : When NOBDW is specified for a SEND, the file will be opened using
    RECFM=U.  Each block will be written as an individual record.  This
    parameter is the same as YES, except that the BDW is not sent.
  Note: This parameter should only be used when TYPE=BINARY is specified

Defects fixed in CZ01874:
: Default for EMAILSUBGOOD and EMAILSUBFAIL incorrectly references
  token #(TR).  The correct token is #(TID).
: 0C4 abend at OSISGLBL+ADC0 occurs when trying to display
  message PGTS1502I at startup
: XCOMJOB alias for member FUSXJOB was corrupted
: When queuing transfers through Cross memory and using the
  LOCAL_USER (LUSER) parameter, the authorization check is incorrectly
  performed against the user that submitted the request, sometimes
  resulting in an Authorization error.
: Added new batch parameter:
  SENDRECFMU={YES|NO|NOBDW}   Default=NO
  When YES is specified for a SEND, the file will be opened using
  RECFM=U.  Each block will be written as an individual record.  The
  main usage of this parameter is to retain the RECFM=VB block and record
  structure when sending to a UNIX or Windows platform.
  When NOBDW is specified for a SEND, the file will be opened using
  RECFM=U.  Each block will be written as an individual record.  This
  parameter is the same as YES, except that the BDW is not sent.
  Note: This parameter should only be used when TYPE=BINARY is specified
: ISPF Local File Name was translated to upper case incorrectly.  This
  caused problems when transmitting HFS files.

Defects fixed in CZ01871:
: Resolves a dynamic allocation error when VSAM MAXLRECL > 32760.
  Transfers will now fail if the VSAM MAXLRECL is > 32760.
: 0C4 abend received under following circumstances:
  : Transfer is using compression
  : Transfer starts sending compressed bytes
  : Transfer terminates with an error

Defects fixed in CZ01869:
: Fixes a problem where PPA defined in DNI members enabled
  at startup only get executed for the first DNI member enabled.
  If you disable and enable the DNI member, PPA is executed.
: Resolves an 0C4 abend when the VSAM MAXLRECL is > 32760.
  Transfers will now fail if the VSAM MAXLRECL is > 32760.

Defects fixed in CZ01866:
: Resolves a loop that occurs under the following conditions:
  : Send a PDS or PDSE with a wildcard in the local file name
  : The Sender is not authorized to access the input dataset

Please contact TIBCO Support to download this hotfix.

Environment

Product: TIBCO Managed File Transfer Platform Server for z/OS Version: 7.1.0 OS: --------------------

Issue/Introduction

TIBCO Managed File Transfer Platform Server for z/OS hotfix CZ01923 is now available