Resolution:
Description
==========
When TIBCO BusinessConnect receives an incoming file from the trading partner, if the file name contains two consecutive underscore (_) characters, BC will attempt to trigger an operation with the name of the file that precedes the double underscore (__) instead of the identifying operation. This operation gets rejected as it forms an unknown operation name.

Example, using the EZComm protocol for a 'Notify' operation, if the received file name is: 20111214153400044-CAR__2011_12_13_230114.zip, then BC triggers an operation with id "20111214153400044-CAR".  As this operation name is not identified by BC it gets rejected and an error is generated.

Environment
===========
TIBCO BusinessConnect 5.2.X onwards.
All protocols

Cause
======
Prior to BC 5.2.X, there was no way to specify the operationID for Inbound transfers. BC 5.2.x introduced new functionality to specify the operationID as part of a file name. The syntax for specifying the operation in Filename is to use the following syntax:  &ltInterfaceName>_&ltversion>_&ltcategory>__&ltfileName>.&ltextension>.

When BC finds two underscores in a file name, it treats the fist part of the file name as operation id and replaces _ with / to create an operation name.

Example: If the file name is BC_1.0_Notify__sample.txt, the file name will be sample.txt and the operation would be BC/1.0/Notify.

Resolution
========
To avoid this error, use only a single underscore in the file name.

Inbound transactions with double underscore in file name gets failed.