IC89469: SFG SAYS DELIVERY WAS A FAILURE WHEN IT SUCCEEDED

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

APAR status

  • Closed as program error.

Error description

  • Under current programming of the FileGatewaySendMessage BP and
    the AFTRouteViaCD BP,  it is possible for SFG to sucessfully
    deliver a file via Connect Direct, but mark the delivery as a
    failure. This is the case if the first error showing in the
    Process Flow does not occur until during the Connect:Direct
    Server End Session Service. If there have been no previous
    errors in the Process Flow, then by the time the End Session
    Service starts, the file has already been delivered. Due to
    that a first error during the End Session Service can be
    allowed to still trigger an error, because it is an error, but
    it should NOT trigger any on-screen message that reports that
    the delivery was a failure, nor generate any notification
    e-mail that the delivery was a falure.
    

Local fix

  • There is no workaround. The customer has been informed that,
    for the time being, when they receive a delivery failure, they
    should examine the Process Flow, and if the first error is not
    until the End Session Service, they should confirm with their
    Trading Partner whether or not the file was received prior to
    taking any remediary action such as initiating a reply in SFG.
    

Problem summary

  • Users Affected:
    All users of FileGateway that use Connect:Direct.
    
    Problem Description:
    It is possible for a message to be successfully sent to via
    connect:direct, but for Filegateway to signal a delivery
    failure.
    
    Platforms Affected:
    All
    

Problem conclusion

  • Resolution Summary:
    Changed logic so that if the C:D copyTo step is successful, that
    delivery failure will not be signaled despite errors occurring
    after that step.
    
    Delivered In:
    5010, 5104, 5.2.4.3
    

Temporary fix

Comments

  • Published 7/20/13
    

APAR Information

  • APAR number

    IC89469

  • Reported component name

    STR FILE GATEWA

  • Reported component ID

    5725D0700

  • Reported release

    200

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2013-01-10

  • Closed date

    2013-01-11

  • Last modified date

    2013-07-19

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

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

Fix information

  • Fixed component name

    STR FILE GATEWA

  • Fixed component ID

    5725D0700

Applicable component levels

  • R200 PSY

       UP

  • R210 PSY

       UP

  • R224 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Sterling File Gateway

Software version:

2.0

Reference #:

IC89469

Modified date:

2013-07-19

Translate my page

Machine Translation

Content navigation