Fixes for the following APARs are contained in this PTF:
PM77310 MSIF MISSING ACK RESPONSE IN FILEACT SNF RECEIVE MUST NOT LEAD TO
NOTIFICATION STATE "FAILED"
Formerly, when MSIF failed to receive in time SWIFT's response
to an ACK of an SnF FileReceived scenario, MSIF re-sent the
ACK which led to an error response containing error
code Sw.SnF.InvalidSnFRef. This error caused MSIF to change
the notification state to 'Failed'.
Now, on receiving error code Sw.SnF.InvalidSnFRef for the
FileReceived scenario, MSIF changes the notification state
from 'Sent' to 'Complete' as the provided error code
indicates that the corresponding FileReceived scenario has
already been acknowledged.
PM80196 MSIF FILEACT SNF / REPEATED DELIVERY ATTEMPT OF RCV FILE
Formerly, when an SnF FileReceived scenario using an output
channel was interrupted by closing the output channel and
the FileReceived scenario had expired (ending in condition
'Finished' and state 'Error'), an re-send attempt from
SWIFT (after the output channel was opened again) would cause
an error and the correspondent would have to re-send the file
in another transfer again. This false behavior was caused by
WebSphere BI for FN which tried to re-activate the initial
scenario again, even if this scenario had reached the
final 'Error' state.
Now, WebSphere BI for FN correctly recognizes that the initial
transfer attempt ended in an error state when the re-sending
is done by SWIFT. A new scenario will be opened to receive
WBIFN V3.1.1 Messaging Services for SWIFTNet InterAct and FileAct for z/OS