PM80196: FILEACT SNF / REPEATED DELIVERY ATTEMPT OF RCV FILE

A fix is available

Subscribe

You can track all active APARs for this component.

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 number

    PM80196

  • Reported component name

    MS FOR SN IA AN

  • Reported component ID

    5655FIN02

  • Reported release

    11F

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-09

  • Closed date

    2013-02-07

  • Last modified date

    2013-03-04

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

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

    PM80598

Modules/Macros

  • DNF10001
    

Fix information

  • Fixed component name

    MS FOR SN IA AN

  • Fixed component ID

    5655FIN02

Applicable component levels

  • R11F PSY UK91464

       UP13/02/08 P F302

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.



Rate this page:

(0 users)Average rating

Document information


More support for:

z/OS family

Software version:

11F

Reference #:

PM80196

Modified date:

2013-03-04

Translate my page

Machine Translation

Content navigation