PM80598: FILEACT SNF / REPEATED DELIVERY ATTEMPT OF RCV FILE

Download PTFs for WBIFN for Multiplatforms V3.1.1- MSIF

APAR status

• Closed as program error.

Error description

• For test purposes the customer closes the output channel
  manually, whilst he was sending a file.
  About an hour later, the time period of max. number of automatic
  retries of the transfer of this
  FILE+RCV scenario is expired, and Error Message DNFO1002E is
  reported in the DNI_A_EVENT
  
  The customer re-opend the output channel a couple of hours
  later, and SWIFT tries to re-deliver the file with PDM,
  but the request is rejected, because WBI FN had only checked the
  Condition 'finished' and State 'Invalid' and sent only a local
  Error Response.
  
  Solution:
  Now we generates an new FILE+RCV Scenario and beside the check
  of Condition 'Finished' and State 'Invalid'
  we also check now the Condition 'Finished' and State 'Error'
  

Local fix

• Apply APAR
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users                                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: FILEACT SNF / REPEATED DELIVERY         *
  *                      ATTEMPT OF RCV FILE                     *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  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.
  

Problem conclusion

• 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
  the file.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PM80196

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  MS FOR SW IA AN

• Fixed component ID

  5724D9633

Applicable component levels

• R311 PSY

     UP