Description:
The following issues have been addressed in TIBCO Adapter for Files z/OS (MVS) (TM) Hotfix 04 version

1) 1-6XUGYN :
     RV data sent on genFilePublishSubject does not correspond
     to previous releases, causing existing monitoring applications
     to fail.
    
    This was due to a coding error when new functions were added
     for EMS support.

2) 1-6Y3NZF :
     Errors on Subscriber side when processing EMS records.
     Symptoms:
       (a) Message "Error trying to get map field by name: Conversion failed"
           in trace.
       (b) End of file logic not being properly invoked.

     This is composed of several issues on the Subscriber side
       (1) Error message when Subscriber is extracting fields from
           a received EMS record

       (2) Data logic to extract EndMsg 'filename' used to invoke
           EOF processing was not being executed.

     Both of these were due to coding errors when new functions were added
     for EMS support.


3) 1-6Y3U4T :
     Error in how EMS messages are handled when both the normal data and
     the END message are being sent to the same destination.
     Symptoms:
       (a) EndMsg not being sent to configured endPublishDestination.
       (b) Race condition between last data record and EndMsg signifying EOF.
       (c) End of file logic not being properly invoked at Subscriber side.
     This is composed of several issues on the Publisher side
       (1) Configuration logic was not properly setting the
           endPublish field when EMS was being used.
       (2) EMS logic was always creating a new, separate session
           for endPublish messages, even when routed to the same
           destination. This was causing race conditions.
       (3) Logic to send EndMsg 'filename' was not being properly
           invoked, so this field was never being sent to Subscriber.

     These were due to coding errors when new functions were added
     for EMS support.