Description:
The following issues have been addressed in TIBCO Adapter for Files z/OS (MVS) (TM) 4.4.0 Hotfix 01 version.  Please refer to the hot fix Readme for additional details on this hot fix.

Issues Fixed in this Hot Fix:
1) 1-773DHT :
     Under certain conditions, FileAdapter z/OS V4.4 did not properly recognize
     EOF on large file transfers using Block Mode ECM over RV.
     This has been fixed.

2) 1-773F27 :
     FileAdapter status did not always indicate correctly the publish/subscribe
     result particularly if an error occured at the Subscriber end.
     This has been fixed.

3) 1-773F1D :
     Misconfiguring FileAdapter (such as using "totalConfirmationSubscribers"
     in a [FileType] that is not using Record Mode ECM), caused a misleading
     (erroneous) configuration error message.
     This has been fixed. The error message now mentions explicitly the
     actual cause of the configuration problem.

4) 1-77AVIE :
     CWK allocation blocksize was not flexible.
     Using the default blocksize for CWK files could, under certain
     conditions (small LRECLs), cause the CWK file to be two or three
     times the size of the final Target file. Some means of allowing the
     customer to override the Subscriber's default CWK blocksize was needed.

     This fix externalizes the CWK blocksize parameter.
     In the [FileType] definition, the parameter cwkBlockSizeAlloc="nnnn"
     can be used to override the default CWK blocksize.
     The "nnnn" is the desired size, in bytes of of the CWK block size.
     The customer should ensure that any CWK blocksize is an even
     multiple of the Publisher's number of records sent in the
     Publisher blockTransferSize= parameter. This will avoid
     creating partial buffers, avoids associated extra I/O to flush
     MVS's access services I/O buffers (which are based on Blocksize),
     and avoids any exposures that could be created if the partial buffers
     were lost during an MVS system crash.


5) 1-77AVHT :
     FileAdapter could not create output dataset on same volume, if it exists.
     Some customers pre-allocate production datasets to specific
     volumes, and want the pre-allocated datasets to always be used
     when receiving new data, rather than the current behavior
     which deletes the old file and creates a new file, when
     the Subscriberparameter appendToExistingFile is set to "false".
     This setting indicates that the current file's contents should be
     discarded, and replaced with the new incoming data.

     This fix tunes the appendToExistingFile parameter to allow
     more granularity. When the Subscriber's appendToExistingFile="false",
     the current behavior of deleting the old file, and creating a new
     files operates the same as always. This is equivalent to MVS
     JCL DISPOSITION parameters of DISP=(NEW,KEEP).

     Setting appendToExistingFile="overwriteExisting" will cause
     the Subscriber to preserve the existing pre-allocated file,
     and will just overwrite in place the existing file. This is
     equivalent to MVS JCL DISPOSITION parameters of DISP=(OLD,KEEP).

6) 1-77DH1V :
     Under certain conditions, FileAdapter z/OS V4.4 produced SOC4 when the
     timing between start and stop of the adapter is too short.
  
     A situation that could cause the SOC4 was identified and fixed.

This hot fix can be downloaded from the TIBCO Product Support ftp server, ftp://support-ftp.tibco.com/, using your username and password for the TIBCO Support Web.  Once logged on you can find the hot fix under:
available_downloads/ActiveEnterprise/Adapters/Files-OS390/4.4.0/hotfix-1

Please contact TIBCO Support if you have any problems finding or downloading this hot fix.