BFGBR0001 - BFGBR9999

BFGBR0001E: An internal error has occurred. An attempt to generate a session where the end point has not been initialised.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0002E: Protocol driver <insert_0> cannot be located.
Severity: 20 : Error
Explanation: The given protocol driver cannot be located and is required to connect to the selected server.
Response: Review any class path changes that have occurred and ensure the relevant protocol bridge driver has been included.

BFGBR0003E: Protocol driver <insert_0> is not supported.
Severity: 20 : Error
Explanation: A request to connect to a server with a protocol driver which is not supported on this protocol bridge.
Response: Review the properties of this agent to ensure the correct protocol driver has been configured.

BFGBR0004E: 3rd Party protocol driver libraries for <insert_0> cannot be located.
Severity: 20 : Error
Explanation: The required 3rd party protocol driver libraries cannot be located and are required to connect to the selected server
Response: Review any class path changes that have occurred and ensure the relevant protocol bridge driver has been included.

BFGBR0005E: Attempt to connect to host <insert_0> has failed. Additional information <insert_1>
Severity: 20 : Error
Explanation: Protocol bridge attempted to connect to a host machine, but failed.
Response: Check that the named host machine is available.

BFGBR0007E: While attempting to disconnect from the server the following exception was reported <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0008E: Attempts to connect to the server host ''<insert_0>'' on port <insert_1> were rejected with the following response: ''<insert_2>''.
Severity: 20 : Error
Explanation: The protocol bridge failed to connect to the server and therefore cannot process any transfer requests.
Response: Verify the agent properties are correct and that the server is operation and listening on the expected port.

BFGBR0009E: Protocol IO exception has occurred. Exception: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0010E: Creation of a session has failed due to the maximum number of concurrent sessions (<insert_0>) has been reached.
Severity: 20 : Error
Explanation: The maximum number of concurrent sessions has been reached. As a result this transfer has been failed.
Response: Review the agent properties to ensure that the properties maxDestinationTransfer and maxSourcetransfer do not exceed the maximum number sessions for the protocol bridge.

BFGBR0011E: An invalid integer property of <insert_1> from property <insert_0> has been detected.
Severity: 20 : Error
Explanation: An agent property that is expected to have an integer value, had a value which cannot be read as an integer value.
Response: Review the agent properties and ensure the property value is an integer.

BFGBR0012E: Protocol bridge configuration property ''<insert_0>'' is a mandatory property but is missing in the agents property file.
Severity: 20 : Error
Explanation: The protocol bridge attempted to valid a mandatory property but could not locate it in the agent properties.
Response: Append the missing property to the agent's property file.

BFGBR0013E: Protocol bridge configuration property ''<insert_0>'' is a mandatory property but is missing in the agents property file.
Severity: 20 : Error
Explanation: The protocol bridge attempted to valid a mandatory property but could not locate it in the agent properties.
Response: Append the missing property to the agent's property file.

BFGBR0014E: The private key for <insert_0> is in an invalid format
Severity: 20 : Error
Explanation: The protocol bridge could not read the property of a private key as it was in the wrong format. The format is expected to be two hex digits followed by a space.
Response: Review the private key in the agent properties and ensure it has the correct format.

BFGBR0016E: A duplicate protocol driver name has been detected in the agent properties
Severity: 20 : Error
Explanation: The agent properties contains a protocol driver reference which has already been defined.
Response: Review the agent properties and ensure all protocol driver names are unique and do not match any of the pre-defined protocol drivers.

BFGBR0017E: The protocol driver named <insert_0> is not defined.
Severity: 20 : Error
Explanation: The protocol driver given is not one of the pre-defined drivers supported by the protocol bridge or it has not been defined within the agent properties.
Response: Review the protocol driver name in the agent properties and ensure it matches one of the supported names.

BFGBR0018E: The protocol driver package <insert_0> cannot be located.
Severity: 20 : Error
Explanation: The given protocol driver has been defined as supported. However the package cannot be located on the class path.
Response: Review the protocol driver package and the class path to ensure that the protocol driver package and class is on the class path.

BFGBR0019E: The protocol driver package <insert_0> has reported a security exception of <insert_1>
Severity: 20 : Error
Explanation: The protocol driver cannot be access due to a security problem.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0020E: The protocol driver package <insert_0> does not have the correct constructor for creating the necessary instance.
Severity: 20 : Error
Explanation: The given protocol driver cannot interface with the protocol bridge.
Response: Check that a supported protocol driver has been specified in the agent properties.

BFGBR0021E: The protocol driver package <insert_0> has report an exception of <insert_1>
Severity: 20 : Error
Explanation: The given protocol driver cannot interface with protocol bridge.
Response: Check that a supported protocol driver has been specified in the agent properties.

BFGBR0022E: The protocol driver has reported an exception of <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0023E: The server has rejected authentication with user ID <insert_0>.
Severity: 20 : Error
Explanation: The protocol bridge failed to connect to the server as the authentication given was rejected.
Response: Review the authentication parameters in the agent properties.

BFGBR0024E: Attempt to change directory to <insert_0> on the server has failed.
Severity: 20 : Error
Explanation: The protocol driver failed to change directory on the connected server as the requested was rejected by that server.
Response: Review the original transfer request and ensure file path names are validate for the server.

BFGBR0025W: The server has terminated the connection. Exception: <insert_0>
Severity: 10 : Warning
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection.

BFGBR0026E: Attempt to delete file <insert_0> from the connected server has failed.
Severity: 20 : Error
Explanation: The protocol driver failed to a delete a file as the requested was rejected by the server.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0027W: The server has terminated the connection with exception <insert_1> while transferring <insert_0>
Severity: 10 : Warning
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection.

BFGBR0028E: Attempt to read file <insert_0> from the server has failed
Severity: 20 : Error
Explanation: The protocol driver failed to a get of a file as the request was rejected by the server.
Response: Review the original transfer request and ensure file path names are validate for the server.

BFGBR0029E: The protocol driver failed to create a local file <insert_0> Exception: <insert_1>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0030W: The server has terminated the connection. Exception: <insert_0>
Severity: 10 : Warning
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection.

BFGBR0031W: The server has terminated the connection. Exception: <insert_0>
Severity: 10 : Warning
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection.

BFGBR0032E: Attempt to read file <insert_0> from the protocol file server has failed with server error <insert_1>
Severity: 20 : Error
Explanation: The protocol driver failed to get of a file as the request was rejected by the server.
Response: Review the original transfer request and ensure file path names are valid for the server.

BFGBR0033W: The server has terminated the connection. Exception: <insert_0>
Severity: 10 : Warning
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection.

BFGBR0034E: Attempt to create directory <insert_0> of the connected server has failed.
Severity: 20 : Error
Explanation: The protocol driver failed to create a directory as the request was rejected by the server.
Response: Check that authentication the protocol bridge uses has permission for creating directories on the server.

BFGBR0035W: The server has terminated the connection. Exception: <insert_0>
Severity: 10 : Warning
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection.

BFGBR0036E: Attempt to write file <insert_0> on the server has failed
Severity: 20 : Error
Explanation: The protocol driver requested to write a file to the connected server was rejected.
Response: Review the original transfer request and ensure file path names are validate for the server.

BFGBR0037E: The protocol driver failed to read file <insert_0> Exception: <insert_1>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0038W: The server has terminated the connection. Exception: <insert_0>
Severity: 10 : Warning
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection

BFGBR0039E: Attempt to write file <insert_0> on the server has failed with server error ''<insert_1>''
Severity: 20 : Error
Explanation: The protocol driver failed to write a file as the request was rejected by the server.
Response: Review the original transfer request and ensure file path names are valid for the server.

BFGBR0040W: The server has terminated the connection. Exception: <insert_0>
Severity: 10 : Warning
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection.

BFGBR0041E: Attempt to rename file <insert_0> to <insert_1> has been rejected by the server.
Severity: 20 : Error
Explanation: The protocol driver failed to perform a rename of a file as the request was rejected by the server.
Response: Check that the protocol bridge has permissions to perform rename of files on the server.

BFGBR0042W: The server has terminated the connection. Exception: <insert_0>
Severity: 10 : Warning
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection.

BFGBR0043E: The protocol driver cannot translate file type <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0044E: The timezone of <insert_0> is not a valid timezone
Severity: 20 : Error
Explanation: The timezone property specified for the protocol bridge is invalid.
Response: Review the timezone property in the agent properties file.

BFGBR0045E: The platform of <insert_0> is not a supported platform for protocol bridge
Severity: 20 : Error
Explanation: The protocol bridge is being executed on a platform which is not supported.
Response: Review the platform type and ensure it is one of the supported platforms for protocol bridge.

BFGBR0046E: The server platform type of <insert_0> is not known
Severity: 20 : Error
Explanation: The agent properties has defined the server with an unknown platform type.
Response: Review the agent properties and ensure the server platform type is one of those supported.

BFGBR0047E: The language of <insert_0> is not a valid language
Severity: 20 : Error
Explanation: The language property specified for the protocol bridge is invalid.
Response: Review the language property in the agent properties file.

BFGBR0048E: Attempted to redefine 3rd party driver when not in unit test mode.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0049E: Attempt to append to file <insert_0> on the server has failed with server error ''<insert_1>''
Severity: 20 : Error
Explanation: The protocol driver request to append to a file on the server has been rejected.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0050W: The server has terminated the connection. Exception: <insert_0>
Severity: 10 : Warning
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection and connection

BFGBR0051E: One or more protocol bridge configuration errors have been detected. The protocol bridge cannot be started.
Severity: 20 : Error
Explanation: The protocol bridge attempted to validate its configuration properties and one or more of the mandatory properties are either not present or have invalid values.
Response: Review the previous messages logged and correct as necessary.

BFGBR0052E: Protocol bridge configuration property ''<insert_0>'' is a mandatory property but is missing in the agents property file.
Severity: 20 : Error
Explanation: The protocol bridge attempted to valid a mandatory property but could not locate it in the agent properties.
Response: Append the missing property to the agent's property file.

BFGBR0053E: Protocol bridge configuration property ''protocolBridgeMonthShortNames'' has an incorrect format of <insert_0>.
Severity: 20 : Error
Explanation: The Protocol bridge property protocolBridgeMonthShortNames has an incorrectly formatted value.
Response: Review the property and ensure twelve month names separator by | has been specified.

BFGBR0054E: A property <insert_0> has an invalid integer value of <insert_1>
Severity: 20 : Error
Explanation: Bridge attempted to define the upper limit of the number of sessions that can be opened. This is based on a number of agent properties, one of these is an invalid integer.
Response: Review the agent properties and correct the name property..

BFGBR0055E: Attempt to map file path <insert_0> for user ID <insert_1> has failed.
Severity: 20 : Error
Explanation: The file path specified in the MQMFT transfer request could not be translated to a protocol server file path.
Response: Review the file path in the associated MQMFT transfer request.

BFGBR0057E: The server has terminated the connection. Exception: <insert_0>
Severity: 20 : Error
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection.

BFGBR0058E: Internal error: Attempt to perform an unsupported action of <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0062E: An internal error has occurred. Request for session container for transfer Id <insert_0> occurred when it is not present.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0063E: An internal error has occurred. Request for a duplicate container for transfer Id <insert_0> occurred when already present.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0064W: The server has terminated the connection. Exception: <insert_0>
Severity: 10 : Warning
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection

BFGBR0065E: An internal error has occurred when attempting discover the current remote working directory. Server reply code <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0066W: The server has terminated the connection. Exception: <insert_0>
Severity: 10 : Warning
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection

BFGBR0069E: The transfer failed because <insert_0>.
Severity: 20 : Error
Explanation: Protocol bridge was not able to perform the transfer due to an interaction problem with the server. The description included with highlight the problem area.
Response: The additional information within the message will indicate to where the server problem is. Review this information and investigate.

BFGBR0080W: The server has terminated the connection. Exception: <insert_0>
Severity: 10 : Warning
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection.

BFGBR0081E: The property "protocolBridgeListFileRecentDateFormat" has an invalid date format of <insert_0>
Severity: 20 : Error
Explanation: The protocol bridge property defining the recent date form is not valid and cannot be used.
Response: Review the property and update as necessary.

BFGBR0082E: The property "protocolBridgeListFileOldDateFormat" has an invalid date format of <insert_0>
Severity: 20 : Error
Explanation: The protocol bridge property defining the recent date form is not valid and cannot be used.
Response: Review the property and update as necessary.

BFGBR0083E: An internal error has occurred. Attempting to close pending command when one is not present.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0084E: An internal error has occurred. Incorrect closing stream reply code of <insert_0> has been detected.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0085E: The protocol bridge default credential mapping function failed to initialize. The protocol bridge agent will be stopped.
Severity: 20 : Error
Explanation: When no protocol bridge credential user exits are defined, it is mandatory for the default credential mapping function to be successfully initialized so that a protocol bridge agent can start.
Response: Check the agent event log for any errors relating to the initialization of the default credential mapping function. For further information on the protocol bridge default credential mapping function, refer to the product documentation online at: http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/.

BFGBR0086E: The following list of protocol bridge credential exits failed to initialize: ''<insert_0>''. The protocol bridge agent will be stopped.
Severity: 20 : Error
Explanation: It is mandatory for all of the configured protocol bridge credential exits to be successfully initialized for a protocol bridge agent to start.
Response: Check the agent event log for any errors relating to the initialization of the protocol bridge credential exits. If the product supplied protocol bridge credential exit has failed, refer to the product documentation online at: http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/.

BFGBR0087E: The user ''<insert_0>'' has been denied access to the protocol bridge server by a protocol bridge credential exit
Severity: 20 : Error
Explanation: The protocol bridge agent invokes one or more credential exits to map the user ID to credentials to be used to access the protocol bridge server. The result is that one of the credential exits has denied the user access.
Response: Verify whether the user should be allowed access to the protocol bridge server or not. If the user should be allowed access modify the credential exit(s) configuration accordingly.

BFGBR0088E: No credential mapping has been found for user ''<insert_0>''.
Severity: 20 : Error
Explanation: The protocol bridge agent invokes one or more credential exits to map the user ID to credentials to be used to access the protocol bridge server. The result is that no mapping has been found for the is user.
Response: Verify whether the user should have a credential mapping or not.If the user should have a credential mapping modify the credential exit(s) configuration accordingly.

BFGBR0089I: The user ''<insert_0>'' has been successfully mapped to a set of protocol bridge credentials.
Severity: 0 : Information
Explanation: The protocol bridge agent invokes one or more credential exits to map the user ID to credentials to be used to access the protocol bridge server. The result is that the user has been successfully mapped to a set of credentials.
Response: No action required.

BFGBR0095E: The default protocol bridge credential exit has found a 'user' element with an empty or non-existent 'name' attribute in the credential mapping XML file. This element has been ignored.
Severity: 20 : Error
Explanation: It is mandatory for a 'user' element to have a 'name' attribute with a non-empty pattern as a value.
Response: Update the credential mapping XML file so that all 'user' elements have a 'name' attribute with a valid value.

BFGBR0099E: Bridge agent could not connect to ''<insert_0>'' with user ID ''<insert_1>'' as it has no home directory.
Severity: 20 : Error
Explanation: The bridge agent was not able to log on to the named server and user ID as its configuration is not complete and does not have a valid home directory.
Response: Review the given user ID on the protocol file server and ensure the configuration is valid.

BFGBR0100E: An internal error has occurred. Attempt to access a JSch session when none is present.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0101E: An internal error has occurred. Attempt to access a JSch channel when none is present.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0102E: Bridge agent could not locate and connect to protocol file server <insert_0>
Severity: 20 : Error
Explanation: The bridge agent could not connect to the named protocol file server.
Response: Review the availability of the protocol file server and check the configuration of the bridge agent.

BFGBR0103E: Bridge agent failed to authenticate the connection to host <insert_0> with user ID <insert_1>.
Severity: 20 : Error
Explanation: The bridge agent connected to the protocol file server, but was unable to authenticate the user that is was requested to connect with.
Response: Review the user ID used and ensure the protocol file server is configuration to allow that user ID access.

BFGBR0104E: Bridge agent failed to connect to host <insert_0> with credentials of <insert_1> because <insert_2>
Severity: 20 : Error
Explanation: The bridge agent connected to the protocol file server, but was unable to authenticate the user that is was requested to connect with.
Response: Review the credentials used and ensure the protocol file server is configuration to allow that user ID access.

BFGBR0105E: An internal error has occurred. Bridge agent was expecting a channel class from the JSch client but received <insert_0>.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0106E: An internal error has occurred. Bridge agent was unable to create a channel as the JSch client reported <insert_0>.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0107E: The JSch client has reported an exception of <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0108E: 3rd Party protocol driver libraries for <insert_0> cannot be located.
Severity: 20 : Error
Explanation: The required 3rd party protocol driver libraries cannot be located and these are required to connect to the selected protocol file server
Response: Review any class path changes that have occurred and ensure the relevant protocol bridge driver has been included.

BFGBR0109E: Failed to delete file <insert_0> from the connected protocol file server.
Severity: 20 : Error
Explanation: The protocol driver failed to delete a file as the request was rejected by the protocol file server.
Response: Check the credentials used and ensure there is permission to delete the specified file.

BFGBR0110E: Attempt to read file <insert_0> from the protocol file server has failed with server error <insert_1>
Severity: 20 : Error
Explanation: The protocol driver failed to get a file as the request was rejected by the protocol file server.
Response: Review the original transfer request and ensure file path names are valid for the protocol file server.

BFGBR0111E: Failed to create directory <insert_0> on the connected protocol file server.
Severity: 20 : Error
Explanation: The protocol driver failed to create a directory as the request was rejected by the protocol file server.
Response: Check that the credentials for the protocol bridge have permission to create directories on the protocol file server.

BFGBR0112E: Attempt to write file <insert_0> on the protocol file server has failed with server reporting error <insert_1>
Severity: 20 : Error
Explanation: The protocol driver failed to write a file as the request was rejected by the protocol file server.
Response: Review the original transfer request and ensure file path names are valid and directories have the correct permissions.

BFGBR0113E: Bridge agent failed to authenticate the connection to <insert_0> with user ID <insert_1>.
Severity: 20 : Error
Explanation: The bridge agent connected to the protocol file server, but was unable to authenticate the user that it was requested to connect with.
Response: Review the credentials used and ensure the protocol file server is configured to allow that user ID access.

BFGBR0114E: Attempt to append to file <insert_0> on the protocol file server has failed with server error <insert_1>
Severity: 20 : Error
Explanation: During a transfer recovery operation, the protocol bridge requested to append an existing file on the file protocol server. This requested was rejected by the protocol file server.
Response: Review the permissions of the file, its directory and check that the server supports opening file for append operations.

BFGBR0115W: The server has terminated the connection. Exception: <insert_0>
Severity: 10 : Warning
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection.

BFGBR0116E: Attempt to rename file <insert_0> to <insert_1> has been rejected by the protocol file server.
Severity: 20 : Error
Explanation: The protocol driver failed to perform a rename of a file as the request was rejected by the server.
Response: Check that the protocol bridge has permissions to perform rename of the named files on the server.

BFGBR0117E: An internal error has occurred. When attempting discover the current remote working directory. Server returned reply code <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0118E: Bridge agent was unable to view directory <insert_0> because <insert_1>
Severity: 20 : Error
Explanation: Bridge agent attempted to view a directory on the protocol file server but failed.
Response: Review the associated error message and investigate the health of the protocol file server.

BFGBR0119E: Bridge agent was unable to create directory <insert_0> because <insert_1>
Severity: 20 : Error
Explanation: Bridge agent was transferring files to the protocol file server and needed to create a directory. The protocol file server refused to create the directory and the transfer of the file has failed.
Response: Review the associated error message and investigate the file's permissions on the protocol file server.

BFGBR0120E: Protocol bridge agent was unable to rename file <insert_0> to <insert_1> because <insert_2>
Severity: 20 : Error
Explanation: Protocol bridge agent was attempting to rename a file on the protocol file server but received an exception from the SFTP client.
Response: Review the associated error message and investigate the file's permissions on the protocol file server.

BFGBR0121E: Bridge agent was unable to establish its current working directory because <insert_0>
Severity: 20 : Error
Explanation: Bridge agent was attempting to establish its current working directory but received an exception from the SFTP client.
Response: Review the associated error message and investigate the health of the protocol file server.

BFGBR0123E: Bridge agent was unable to collect linked file status of <insert_0> because <insert_1>
Severity: 20 : Error
Explanation: Bridge agent was attempting obtain file information of the named file but received an exception from the SFTP client.
Response: Review the associated error message and investigate the health of the protocol file server.

BFGBR0124E: Internal error detected: Attempted to redefine 3rd party driver when not in unit test mode.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0125E: Bridge agent has lost the connection with the protocol file server because <insert_0>
Severity: 20 : Error
Explanation: The connection between the Bridge agent and its protocol file server has been broken.
Response: Review the associated error message and investigate the health of the protocol file server.

BFGBR0126E: An internal error has occurred. Request for an unsupported function <insert_0>.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0127E: Bridge agent has rejected connection with <insert_0> as its supplied host key does not match the expected value. Host key returned was <insert_1>
Severity: 20 : Error
Explanation: The host key supplied by the protocol file server to the bridge agent did not match the expected value from the credentials and therefore the connection was rejected. The transfer request was failed for this reason.
Response: Review the host key in the configured credentials and ensure it is the correct value.

BFGBR0128E: An internal error has occurred. Driver failed to release Identity <insert_0> because of exception <insert_1>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0129E: Bridge agent has incomplete credentials for connecting to a FTP Server. A password is required for user ID <insert_0> on <insert_1>.
Severity: 20 : Error
Explanation: The credentials supplied for the user ID does not have a password. The Bridge agent has been configured to connect to a FTP server which requires a user ID and a password. No connection can be attempted and the transfer has been failed.
Response: If using the default credentials package review the ProtocolBridgeCredentials.xml and ensure the user ID has a password. If using a custom supplied credentials package refer to its documentation.

BFGBR0130E: Bridge agent has incomplete credentials for connection to an SFTP Server. A password or private key is required for user ID <insert_0> on <insert_1>.
Severity: 20 : Error
Explanation: The credentials supplied for the user ID does not have a password or a private key.The Bridge agent has been configured to connect to an SFTP server which requires a user ID and a password or a user ID and private key. No connection can be attempted and the transfer has been failed.
Response: If using the default credentials package review the ProtocolBridgeCredentials.xml and ensure the user ID has a password or private key. If using a custom supplied credentials package refer to its documentation.

BFGBR0131E: The minimum value for agent property protocolBridgeMaxSessions must be <insert_0>. This value has been set to <insert_1> which is below the minimum for the bridge agent.
Severity: 20 : Error
Explanation: A request in the agent properties to set the maximum number of bridge sessions to a value below the absolute minimum to support transfer operations. This value must be set so all possible sender and receiver transfers can have access to the protocol file server. The absolute minimum value is set as the sum of the agent properties maxSourceTransfer and maxDestinationTransfer, which is the default value of protocolBridgeMaxSessions.
Response: Review the three agent properties and either increase protocolBridgeMaxSessions or reduce either maxSourceTransfer or maxDestinationTransfer, then restart the bridge agent.

BFGBR0132E: An internal error has occurred. Request for bridge information of <insert_0> has been made before this agent has been configured as a bridge agent.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0133E: The user ID <insert_0> is not valid for use with the bridge agent and the transfer has been failed.
Severity: 20 : Error
Explanation: The user ID supplied with the transfer request has not been validated by the credential package. As a result no credentials are available for connecting to the protocol file server and the transfer request has been failed.
Response: Review the protocolBridgeCredentials.xml configuration to ensure the given user ID has been configured. If the default credential package is not being used then refer to the documentation of the credential package being used.

BFGBR0134E: An internal error has occurred. Attempt to set socket timeout return exception of <insert_0>.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0135E: The server list format type of <insert_0> is not supported.
Severity: 20 : Error
Explanation: The agent properties have defined the server list format with an unsupported list format type.
Response: Review the agent properties and ensure the server list format type is one of those supported.

BFGBR0136E: An internal error has occurred. Request to use a session by <insert_0> after it has been closed.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0137E: IBM MQ Managed File Transfer does not support communication between bridge agents on a z/OS platform and an SFTP protocol file server.
Severity: 20 : Error
Explanation: An attempt was made to start a bridge agent on a z/OS platform, which has been configured to communicate with an SFTP protocol file server. This configuration is not supported.
Response: Review the bridge configuration you require and where possible use an FTP protocol file server.

BFGBR0138E: An internal error has occurred. An attempt was made to get an input or output stream while a transfer was in recovery.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0139E: An internal error has occurred. An attempt was made to get an input or output stream while a transfer was in recovery.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0140E: Protocol file server <insert_0> for user ID <insert_1> has accepted the credentials, but rejected subsequent channel requests. This may be due to an expired password on the server.
Severity: 20 : Error
Explanation: Bridge agent has successfully connected to the protocol file server and the supplied credentials have been accepted. However the server refuses any other requests which may be due to the associated password requiring maintenance.
Response: Check the user ID on the protocol file server to see if any maintenance is required. When resolved submit the transfer request again.

BFGBR0141E: The value ''<insert_0>'' ftpsType attribute in the protocol bridge properties file is invalid.
Severity: 20 : Error
Explanation: The ftpsType attribute must have a value of "implicit" or "explicit".
Response: Set the ftpsType attribute to a valid value. Then restart the agent.

BFGBR0142E: The ftpsTrustStore attribute is missing from the protocol bridge properties file.
Severity: 20 : Error
Explanation: The ftpsTrustStore attribute is mandatory when the protocol bridge is using the FTPS protocol.
Response: Set the ftpsTrustStore attribute. Then restart the agent.

BFGBR0143E: The trustStorePassword attribute is missing from the protocol bridge credentials file.
Severity: 20 : Error
Explanation: The trustStorePassword attribute is mandatory when the protocol bridge is using the FTPS protocol.
Response: Set the trustStorePassword attribute. Then restart the agent.

BFGBR0144E: The creation of the Trust Manager for FTPS authentication failed. The reason for the failure is: <insert_0>
Severity: 20 : Error
Explanation: The attempt to create the Trust Manager using the trustStore, trustStorePassword and trustStoreType attributes failed.
Response: Check the reason for the error and make any required configuration changes. Then restart the agent.

BFGBR0145E: The keyStorePassword attribute is missing from the protocol bridge credentials file.
Severity: 20 : Error
Explanation: The keyStorePassword attribute is mandatory when the protocol bridge is using the FTPS protocol and the keyStore attribute has been set.
Response: Set the keyStorePassword attribute. Then restart the agent.

BFGBR0146E: The creation of the Key Manager for FTPS authentication failed. The reason for the failure is: <insert_0>
Severity: 20 : Error
Explanation: The attempt to create the Trust Manager using the keyStore, keyStorePassword and keyStoreType attributes failed.
Response: Check the reason for the error and make any required configuration changes. Then restart the agent.

BFGBR0147E: The server has rejected authentication with user ID <insert_0>.
Severity: 20 : Error
Explanation: The protocol bridge failed to connect to the server as the authentication given was rejected.
Response: Review the protocol bridge credentials.

BFGBR0148E: Attempt to connect to server on host <insert_0> with port <insert_1> was rejected with exception <insert_2>
Severity: 20 : Error
Explanation: The protocol bridge failed to connect to the server and therefore cannot process any transfer requests.
Response: Verify the agent properties are correct and that the server is operational and listening on the expected port.

BFGBR0149E: Attempt to connect to host <insert_0> has failed. Additional information: <insert_1>
Severity: 20 : Error
Explanation: Protocol bridge attempted to connect to a host machine, but failed.
Response: Check that the named host machine is available.

BFGBR0150E: Protocol IO exception has occurred. Exception: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0151E: The creation of the protocol bridge session failed. The reason for the failure is: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0152E: The PBSZ FTP verb has failed. The reply code is: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0153E: The PBSZ FTP verb has failed. The reply code is: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0154E: The CCC FTP verb has failed. The reply code is: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0155E: There is a duplicate entry for the protocol server with name <insert_0>.
Severity: 20 : Error
Explanation: The name for each protocol server element within the ProtocolBridgeProperties.xml file must be unique.
Response: Correct the ProtocolBridgeProperties.xml file within the protocol bridge agent's configuration directory by either removing the duplicate protocol server entry or renaming the duplicate protocol server entry to a unique name.

BFGBR0156E: No protocol server entry present for the specified default server name <insert_0>.
Severity: 20 : Error
Explanation: There must be a protocol server entry present with the same name as specified by the name attribute of the defaultServer element.
Response: Correct the ProtocolBridgeProperties.xml file within the protocol bridge agent's configuration directory such that the name attribute of the defaultServer element references a protocol server entry with the same name.

BFGBR0157E: The same target protocol server name must be specified for each file to be transferred.
Severity: 20 : Error
Explanation: The MQMFT protocol bridge only supports transfers to or from a single protocol server.
Response: Check the files specified in your transfer request to ensure they all refer to a single protocol server.

BFGBR0158E: The protocol server name <insert_0> is invalid.
Severity: 20 : Error
Explanation: The protocol server name must be at least 2 characters in length and only contain either alphanumeric characters or the following characters: ".", "_", "/" and "%". This problem is either caused by an incorrectly configured protocol bridge agent where the protocol server is defined by agent properties or by a protocol server properties user exit, installed for the protocol bridge agent, not returning a correct server name.
Response: Report the problem to the MQMFT system administrator to resolve the problem with a protocol server properties user exit. If no protocol server user exits are installed, contact the IBM support center.

BFGBR0159E: The protocol bridge file path <insert_0> is invalid.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0160E: An internal error has occurred. The bridge manager has not been initialized.
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0161E: The protocol server does not support relative file paths.
Severity: 20 : Error
Explanation: In order to support relative file paths the protocol server must support the CWD command.
Response: Change the transfer request to use an absolute file path and resubmit the request.

BFGBR0162E: The default protocol bridge properties exit failed to initialize. The protocol bridge agent will be stopped.
Severity: 20 : Error
Explanation: It is mandatory for the default protocol bridge properties exit to be successfully initialized for a protocol bridge agent to start.
Response: Check the agent event log for any errors relating to the initialization of the default protocol bridge properties exit. For further information on the default protocol bridge properties exit, refer to the product documentation online at: http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/.

BFGBR0163E: No default protocol server defined for the protocol bridge.
Severity: 20 : Error
Explanation: The transfer required the default protocol server to be used, but no default protocol server is defined for the protocol bridge agent.
Response: Either resubmit the transfer with a valid protocol server specified or reconfigure the protocol bridge agent to define a default protocol server.

BFGBR0164E: The protocol server <insert_0> is not known to the protocol bridge.
Severity: 20 : Error
Explanation: The protocol server specified for the transfer is unknown to the protocol bridge agent.
Response: Check the protocol server named within the transfer is correct. Check the protocol bridge agent's event log to ensure that there are no errors relating to the protocol server configuration, and reconfigure the agent if necessary. Resubmit the transfer after the problem has been resolved.

BFGBR0165E: The following list of protocol bridge properties exits failed to initialize: ''<insert_0>''. The protocol bridge agent will be stopped.
Severity: 20 : Error
Explanation: It is mandatory for all of the configured protocol bridge properties exits to be successfully initialized for a protocol bridge agent to start.
Response: Check the agent event log for any errors relating to the initialization of the protocol bridge properties exits. If the product supplied protocol bridge properties exit has failed, refer to the product documentation online at: http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/.

BFGBR0166W: The <insert_0> file does not exist.
Severity: 10 : Warning
Explanation: The properties file is used to define the set of protocol servers for the protocol bridge agent. If this file does not exist, properties defined in the agent properties file will be used to define a single (default) protocol server. You might see this warning if you have a protocol bridge agent setup for an MQMFT 7.0.4 or earlier installation.
Response: If required, upgrade the protocol bridge agent to define the properties file. Refer to the product documentation online at: http://publib.boulder.ibm.com/infocenter/wmqfte/v7r0/ for the XML format of the properties file.

BFGBR0167E: The ProtocolBridgeProperties.xml file is invalid.
Severity: 20 : Error
Explanation: There is problem with the ProtocolBridgeProperties.xml file and as a result the protocol bridge agent cannot be started. See previously reported error messages for the problem description.
Response: Correct the identified problem with the ProtocolBridgeProperties.xml file and attempt to start the protocol bridge agent again.

BFGBR0168E: The protocol server name has not been defined or is blank.
Severity: 20 : Error
Explanation: The protocol server name must be specified and be at least 2 characters in length and only contain either alphanumeric characters or the following characters: ".", "_", "/" and "%". This problem is either caused an incorrectly configured protocol bridge agent where the protocol server is defined by agent properties or by a protocol server properties user exit, installed for the protocol bridge agent, not returning a correct server name.
Response: Report the problem to the MQMFT system administrator to resolve the problem with a protocol server properties user exit. If no protocol server user exits are installed, contact the IBM support center.

BFGBR0169E: No credential exit found for protocol server ''<insert_1>'' for mapping user ID ''<insert_0>''.
Severity: 20 : Error
Explanation: The protocol bridge agent invokes one or more credential exits to map the user ID to credentials to be used to access the protocol bridge server. The required protocol server is not the default and no ProtocolBridgeCredentialExit2 type credential user exits have been configured, which can be used to map user IDs for non-default protocol servers. The result is that no mapping can be found for the user.
Response: Report the problem to the MQMFT system administrator to resolve the problem with the credential user exits.

BFGBR0170W: The ProtocolBridgeProperties.xml file does not define any servers.
Severity: 10 : Warning
Explanation: There must be at least one server defined in the ProtocolBridgeProperties.xml file before a transfer can take place.
Response: Report the problem to the MQMFT system administrator to define servers in the ProtocolBridgeProperties.xml file before attempting transfers.

BFGBR0171E: The FTP protocol server ''<insert_0>'' was unable to enter passive mode. The FTP reply code is: <insert_1>
Severity: 20 : Error
Explanation: Passive mode was enabled by the passiveMode protocol bridge attribute but the FTP server was unable to enter passive mode.
Response: Check the reason for the failure. Make any necessary changes to the FTP server configuration. Then restart the protocol bridge agent.

BFGBR0172E: The FTPS protocol server ''<insert_0>'' was unable to enter passive mode. The FTP reply code is: <insert_1>
Severity: 20 : Error
Explanation: The FTPS server was unable to enter passive mode, which is required for the protocol bridge to connect to the FTPS server.
Response: Check the reason for the failure. Make any necessary changes to the FTPS server configuration. Then restart the protocol bridge agent.

BFGBR0173E: The attempt to connect to the server on host <insert_0> with port <insert_1> was rejected with exception <insert_2>
Severity: 20 : Error
Explanation: The protocol bridge failed to connect to the server and therefore cannot process the transfer request.
Response: Verify the agent properties are correct and that the server is configured to match the agent properties. Verify that the server is operational and listening on the expected port.

BFGBR0174E: No credentials could be found for agent ''<insert_0>'' in credentials file ''<insert_1>''
Severity: 20 : Error
Explanation: When searching for credentials information associated with the supplied agent name in the specified credentials file, none could be found. Correctly defined credentials are required for the agent to function so the agent will be stopped.
Response: Check the supplied credentials file to ensure it contains definitions for the supplied agent. If no definitions are found, create some and restart the agent.

BFGBR0175E: An attempt to open the truststore <insert_0> has failed because the file could not be found.
Severity: 20 : Error
Explanation: The protocol bridge has been configured to operate with a truststore, however the agent could not locate the named truststore.
Response: Verify that the truststore is at the correct location and that the agent has permission to read the store.

BFGBR0176E: An attempt to read the truststore <insert_0> has failed with exception <insert_1>
Severity: 20 : Error
Explanation: The protocol bridge agent found a problem when attempting to read the truststore and was unable to load and use the truststore.
Response: Review the underlying exception regarding the truststore and correct the condition before restarting the agent.

BFGBR0177E: An attempt to load the truststore <insert_0> has resulted in a general security exception of <insert_1>
Severity: 20 : Error
Explanation: The protocol bridge has been configured to use a truststore and when the agent attempted to load the truststore, it failed with a general security exception.
Response: Review the general security exception and correct as necessary before restarting the agent.

BFGBR0178E: An attempt to open the keystore <insert_0> has failed because the file could not be found.
Severity: 20 : Error
Explanation: The protocol bridge has been configured to operate with a keystore, however the agent could not locate the named keystore.
Response: Verify that the keystore is at the correct location and that the agent has permission to read the store.

BFGBR0179E: An attempt to read the keystore <insert_0> has failed with exception <insert_1>
Severity: 20 : Error
Explanation: The protocol bridge agent found a problem when attempting to read the keystore and was unable to load and use the keystore.
Response: Review the underlying exception regarding the keystore and correct the condition before restarting the agent.

BFGBR0180E: An attempt to load the keystore <insert_0> has resulted in a general security exception of <insert_1>
Severity: 20 : Error
Explanation: The protocol bridge has been configured to use a keystore and when the agent attempted to load the keystore, it failed with a general security exception.
Response: Review the general security exception and correct as necessary before restarting the agent.

BFGBR0181E: The file <insert_1> referenced by <insert_0> cannot be located or read.
Severity: 20 : Error
Explanation: The ProtocolBridgeServerProperties.xml contains a configuration which has a referenced to a file which cannot be located or read on the file system.
Response: Review the entry in the ProtocolBridgeServerProperties.xml and either correct the path name or make the named file available.

BFGBR0182E: The transfer of the file has failed due to a 522 (Protocol not supported) error returned by the FTPS server. The reason is: <insert_0>
Severity: 20 : Error
Explanation: The FTPS server has returned a 522 error in response to an FTPS command sent by the agent.
Response: Review the error message returned and make any necessary configuration changes. If the error is due to a 'session reuse required' error from a vsftpd server, disable the 'require_ssl_reuse' option on the vsftpd server. Then submit the transfer again.

BFGBR0183E: Protocol file server <insert_0> has rejected an open channel request. This may be because the maximum number of channels open for the protocol file server has been reached. Full reason given: <insert_1>
Severity: 20 : Error
Explanation: Bridge agent has successfully connected to the protocol file server but the server has refused an open channel request. Some protocol file servers limit the number of concurrent open channels. The reason for this error may be because the maximum number of channels open for the protocol file server has been reached.
Response: If available, check the protocol file server logs for more information on the reason for the open channel request failure, and take appropriate action. When resolved the transfer request should automatically recover from the error.

BFGBR0184E: The creation of the protocol bridge FIPS SSLContext failed. The reason for the failure is: <insert_0>
Severity: 20 : Error
Explanation: This exception is unexpected. The cause is not immediately known.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0185E: An internal error has occurred. No configuration information can be found for server <insert_0>
Severity: 20 : Error
Explanation: The agent maintains an internal table containing configuration information for the servers defined in the ProtocolBridgeProperties.xml file. While processing a transfer request, the agent was unable to find an entry in this internal table for the required server.
Response: If the problem persists, see problem determination information in the product documentation.

BFGBR0186E: The server has terminated the connection. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The connection between the protocol bridge and the file server has been terminated. This may have occurred due to either the file server or communication to the file server being no longer available.
Response: No action required as the protocol bridge will attempt to create a new session and connection

BFGBR0187E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The size of the source file exceeds the allocated storage for the current directory or dataset on the server.
Response: Review the error message returned and make any necessary changes.

BFGBR0188E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The page type specified for the source file is unknown to server.
Response: Review the error message returned and make any necessary changes.

BFGBR0189E: The transfer of the file encountered a temporary error. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The server encountered an unexpected local error while processing the data.
Response: No action required as the protocol bridge will attempt to create a new session and connection.

BFGBR0190E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: An attempt was made to access a file that either does not exist or that the user does not have access rights to the file.
Response: Review the error message returned and make any necessary changes.

BFGBR0191E: The transfer of the file encountered a temporary error. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The server was unable to gain access to the specified file as the file is exclusively accessed by another process.
Response: No action required as the protocol bridge will attempt to create a new session and connection.

BFGBR0192E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The server does not have sufficient storage space on the system to complete the transfer.
Response: Make enough storage space available on the server and resubmit the transfer request.

BFGBR0193E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The filename does not confirm to file naming policies of the server.
Response: Check the file naming policies on the server. Modify filename to match the policies and resubmit the transfer request.

BFGBR0194E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The server does not support the specified command.
Response: The file server does not implement the minimum set of commands as per FTP specification.Ensure the protocol bridge agent connects to a file server that implements minimum FTP specification.

BFGBR0195E: The transfer of the file encountered a temporary error. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The server is not available to process the request as it will be shutting down after finishing any pending file transfers.
Response: No action required as the protocol bridge will attempt to create a new session and connection.

BFGBR0196E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The server received an erroneous command from the protocol bridge agent. Possible reasons are:(1) Command is unrecognised. (2) Command has syntax errors. (3) Command along with its parameters is too long.
Response: Contact the IBM support center.

BFGBR0197E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The server received a command that has syntax errors from the protocol bridge agent.
Response: Contact the IBM support center.

BFGBR0198E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The server received an incorrect sequence of commands from the protocol bridge agent.
Response: Contact the IBM support center.

BFGBR0199E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The server does not implement the command sent by the protocol bridge agent.
Response: The file server does not implement the minimum set of commands as per the FTP specification.Ensure the protocol bridge agent connects to a file server that implements minimum FTP specification.

BFGBR0200E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The user is not logged in.
Response: Verify if a valid user id and password has been specified in ProtocolBridgeCredentials.xml file for the agent.

BFGBR0201E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: Account information for storing files was not provided by the protocol bridge agent.
Response: Contact the IBM support center.

BFGBR0202E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The server requires a change in security negotiation.
Response: No action required as the protocol bridge agent will attempt to create a new session and connection.

BFGBR0203E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The protocol bridge agent requested a change in the command channel protection level that cannot be processed due to the security policy in place on the server.
Response: No action required as the protocol bridge will attempt to create a new session and connection.

BFGBR0204E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The server is unwilling to process a request due to its security policy as the server requires a certain level of security exists on the connection before processing the request.
Response: Review the error message returned and make any necessary changes.

BFGBR0205E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: A data protection check failed at the server possibly because the server received a buffer size greater than the negotiated value.
Response: Review the error message returned and make any necessary changes.

BFGBR0206E: The transfer of the file failed. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The protection level requested by the protocol bridge agent is not supported by the current security mechanism of server.
Response: Review the error message returned and make any necessary changes.

BFGBR0207E: An unrecoverable error occurred when communicating with the file server. The reply string sent back by the server was ''<insert_0>''
Severity: 20 : Error
Explanation: The server encountered an unexpected local error while processing the data.
Response: Review the error message returned and take appropriate action.

BFGBR0208E: A protocol bridge configuration error has been detected, associated with the option "requestUTF8ControlEncoding". The file server return code was ''<insert_0>''
Severity: 20 : Error
Explanation: The protocol bridge agent requested that the FTP/FTPS server use UTF-8 character encoding for data encoded over the control channel. However the FTP(s) server returned a negative response.
Response: Review the FTP/FTPS server response and consider disabling the "requestUTF8ControlEncoding" option if the file server does not support it.

BFGBR0209E: Bridge agent was unable to create directory <insert_0>
Severity: 20 : Error
Explanation: Bridge agent was transferring files to the protocol file server and needed to create a directory. The protocol file server refused to create the directory and the transfer of the file has failed.
Response: Investigate the file's permissions on the protocol file server. If the issue persists, contact the IBM support center.

BFGBR9999E: <insert_0>
Severity: 20 : Error
Explanation: If this message does not give enough information, check the accompanying error messages for further information.
Response: For further information on resolving this error, see the problem determination information on the product Web site.