Closed as program error.
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.
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.
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
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, 18.104.22.168
Reported component name
STR FILE GATEWA
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fixed component name
STR FILE GATEWA
Fixed component ID
Applicable component levels