The FileInput node <insert_2> started processing the file <insert_1>.
BIP13002
Finished reading the file <insert_1> and archived the file.
Severity
0 : Information
Explanation
The FileInput node <insert_2> finished reading the file <insert_1> and archived the file.
BIP13003
Finished reading the file <insert_1> and deleted the file.
Severity
0 : Information
Explanation
The FileInput node <insert_2> finished reading the file <insert_1> and deleted the file.
BIP13004
Finished reading the file <insert_1> and archived the file by adding a timestamp.
Severity
0 : Information
Explanation
The FileInput node <insert_2> fninshed reading the file <insert_1> and archived the file by adding a timestamp.
BIP13005
Read the whole file <insert_1>.
Severity
0 : Information
Explanation
The FileInput node <insert_2> treated the whole received file <insert_1> as one record, and propagated a message from it.
BIP13006
Read a record from file <insert_1>.
Severity
0 : Information
Explanation
The FileInput node <insert_2> recognized a record in the file <insert_1> and propagated a separate message from it.
BIP13007
Backed out a file <insert_1>.
Severity
0 : Information
Explanation
The FileInput node <insert_2> backed out the file <insert_1> by moving it to the mqsibackout directory. This action was taken in response to a failure to process the file.
BIP13008
Transferred the file <insert_1> from the remote server <insert_3>.
Severity
0 : Information
Explanation
The FileInput node <insert_2> transferred the file <insert_1> from the remote server <insert_3>.
BIP13009
Deleted the file <insert_1>.
Severity
0 : Information
Explanation
The FileInput node <insert_2> deleted the file <insert_1>. This action was taken in response to a failure to process the file.
BIP13010
Wrote to the file <insert_1>.
Severity
0 : Information
Explanation
The FileOutput node <insert_2> wrote to the file <insert_1> in the staging (mqsitransit) directory.
BIP13011
Appended a record directly to the output file <insert_1>.
Severity
0 : Information
Explanation
The FileOutput node <insert_2> appended a record directly to the output file <insert_1>.
BIP13012
Moved the file <insert_1> to <insert_3>.
Severity
0 : Information
Explanation
The FileOutput node <insert_2> moved the file <insert_1> from the staging (mqsitransit) directory to the directory <insert_3>.
BIP13013
Transferred the file <insert_1> to the remote server <insert_3>.
Severity
0 : Information
Explanation
The FileOutput node <insert_2> transferred the file <insert_1> to the remote server <insert_3>.
BIP13014
Transferred the file <insert_1> from the remote server <insert_3>.
Severity
0 : Information
Explanation
The FileRead node <insert_2> transferred the file <insert_1> from the remote server <insert_3>.
BIP13015
Read the whole file <insert_1>.
Severity
0 : Information
Explanation
The FileRead node <insert_2> treated the whole file <insert_1> as one record, and propagated a message from it.
BIP13016
Read a record from file <insert_1>.
Severity
0 : Information
Explanation
The FileRead node <insert_2> recognized a record in the file <insert_1> and propagated a separate message from it.
BIP13017
Deleted the file <insert_1> from the remote server <insert_3>.
Severity
0 : Information
Explanation
The FileRead node <insert_2> deleted the file <insert_1> from the remote server <insert_3> because it has been succesfully transferred.
BIP13018
Finished reading the file <insert_1> and archived the file.
Severity
0 : Information
Explanation
The FileRead node <insert_2> finished reading the file <insert_1> and archived the file.
BIP13019
Finished reading the file <insert_1> and archived the file by adding a timestamp.
Severity
0 : Information
Explanation
The FileRead node <insert_2> fninshed reading the file <insert_1> and archived the file by adding a timestamp.
BIP13020
Finished reading the file <insert_1> and deleted the file.
Severity
0 : Information
Explanation
The FileRead node <insert_2> finished reading the file <insert_1> and deleted the file.
BIP13021
Deleted the file <insert_1> from the remote server <insert_3>.
Severity
0 : Information
Explanation
The FileInput node <insert_2> deleted the file <insert_1> from the remote server <insert_3> because it has been succesfully transferred.
BIP13022
Failed to unsubscribe from topic <insert_1>.
Severity
20 : Error
Explanation
Failed to unsubscribe from topic <insert_1> because of an exception <insert_2>.
Response
Investigate the exception <insert_2>.
BIP13023
Failed to connect to WebSphere MQ queue manager <insert_1>.
Severity
20 : Error
Explanation
Failed to connect to WebSphere MQ queue manager <insert_1> because of reason code <insert_2>.
Response
Use reason code <insert_2> to determine why the connection failed, and take corrective action.
BIP13024
Disconnected from WebSphere MQ queue manager <insert_1>.
Severity
0 : Information
Explanation
Successfully disconnected from WebSphere MQ queue manager <insert_1>.
BIP13025
Connected to WebSphere MQ queue manager <insert_1>.
Severity
0 : Information
Explanation
Successfully connected to WebSphere MQ queue manager <insert_1>.
BIP13026
Read message from WebSphere MQ queue <insert_1>.
Severity
0 : Information
Explanation
Successfully read a message from WebSphere MQ queue <insert_1> on queue manager <insert_2>.
BIP13027
Wrote message to WebSphere MQ queue <insert_1>.
Severity
0 : Information
Explanation
Successfully wrote a message to WebSphere MQ queue <insert_1> on queue manager <insert_2>
BIP13028
Failed write to WebSphere MQ queue <insert_1>.
Severity
20 : Error
Explanation
Failed to write a message to WebSphere MQ queue <insert_1> on queue manager <insert_2> because of reason code <insert_3>
Response
Use reason code <insert_3> to determine why writing the message failed.
BIP13029
Failed read from WebSphere MQ queue <insert_1>.
Severity
20 : Error
Explanation
Failed to read a message from WebSphere MQ queue <insert_1> on queue manager <insert_2> because of reason code <insert_3>
Response
Use reason code <insert_3> to determine why reading the message failed.
BIP13030
Opened WebSphere MQ queue <insert_1>.
Severity
0 : Information
Explanation
Successfully opened WebSphere MQ queue <insert_1> on queue manager <insert_2>
BIP13031
Closed WebSphere MQ queue <insert_1>.
Severity
0 : Information
Explanation
Successfully closed WebSphere MQ queue <insert_1> on queue manager <insert_2>.
BIP13032
Failed to open WebSphere MQ queue <insert_1>.
Severity
20 : Error
Explanation
Failed to open WebSphere MQ queue <insert_1> on queue manager <insert_2> because of reason code <insert_3>.
Response
Use reason code <insert_3> to determine why queue <insert_1> failed to open, and take corrective action.
BIP13033
Committed a locally-coordinated transaction on WebSphere MQ queue manager <insert_1>.
Severity
0 : Information
Explanation
Successfully committed a locally-coordinated transaction on WebSphere MQ queue manager <insert_1>.
BIP13034
Rolled back a locally-coordinated transaction on WebSphere MQ queue manager <insert_1>.
Severity
0 : Information
Explanation
Successfully rolled back a locally-coordinated transaction on WebSphere MQ queue manager <insert_1>.
BIP13035
Failed to commit a locally-coordinated transaction on WebSphere MQ queue manager <insert_1>.
Severity
20 : Error
Explanation
Failed to commit a locally-coordinated transaction on WebSphere MQ queue manager <insert_1> because of reason code <insert_2>.
Response
Use the reason code <insert_2> to determine why the transaction failed to commit, and take corrective action.
BIP13036
Opened WebSphere MQ Topic <insert_1>.
Severity
0 : Information
Explanation
Successfully opened WebSphere MQ Topic <insert_1> on queue manager <insert_2>.
BIP13037
Failed to open WebSphere MQ topic <insert_1>.
Severity
20 : Error
Explanation
Failed to open WebSphere MQ topic <insert_1> on queue manager <insert_2> because of reason code <insert_3>.
Response
Use reason code <insert_3> to determine why the topic failed to open, and take corrective action.
BIP13038
Closed WebSphere MQ topic <insert_1>.
Severity
0 : Information
Explanation
Successfully closed WebSphere MQ topic <insert_1> on queue manager <insert_2>.
BIP13039
Failed to disconnect from WebSphere MQ queue manager <insert_1>.
Severity
20 : Error
Explanation
Failed to disconnect from WebSphere MQ queue manager <insert_1> because of reason code <insert_2>.
Response
Use reason code <insert_2> to determine why the queue manager failed to disconnect, and take corrective action.
BIP13040
Failed to close WebSphere MQ queue <insert_1>.
Severity
20 : Error
Explanation
Failed to close WebSphere MQ queue <insert_1> on queue manager <insert_2> because of reason code <insert_3>.
Response
Use reason code <insert_3> to determine why queue <insert_1> failed to close, and take corrective action.
BIP13041
Failed to close WebSphere MQ topic <insert_1>.
Severity
20 : Error
Explanation
Failed to close WebSphere MQ topic <insert_1> on queue manager <insert_2> because of reason code <insert_3>.
Response
Use reason code <insert_3> to determine why WebSphere MQ topic <insert_1> failed to close, and take corrective action.
BIP13042
Failed to roll back a locally-coordinated transaction on WebSphere MQ queue manager <insert_1>.
Severity
20 : Error
Explanation
Failed to roll back a locally-coordinated transaction on WebSphere MQ queue manager <insert_1> because of reason code <insert_2>.
Response
Use reason code <insert_2> to determine why the roll back failed, and take corrective action.
BIP13043
Started a globally-coordinated transaction on WebSphere MQ queue manager <insert_1>.
Severity
0 : Information
Explanation
Successfully started a globally-coordinated transaction on WebSphere MQ queue manager <insert_1>.
BIP13044
Failed to start a globally-coordinated transaction on WebSphere MQ queue manager <insert_1>.
Severity
20 : Error
Explanation
Failed to start a globally-coordinated transaction on WebSphere MQ queue manager <insert_1> because of reason code <insert_2>.
Response
Use reason code <insert_2> to determine why the roll back failed, and take corrective action.
BIP13045
Committed a globally-coordinated transaction on WebSphere MQ queue manager <insert_1>.
Severity
0 : Information
Explanation
Successfully committed a globally-coordinated transaction on WebSphere MQ queue manager <insert_1>.
BIP13046
Failed to commit a globally-coordinated transaction on WebSphere MQ queue manager <insert_1>.
Severity
20 : Error
Explanation
Failed to commit a globally-coordinated transaction on WebSphere MQ queue manager <insert_1> because of reason code <insert_2>.
Response
Use reason code <insert_2> to determine why the roll back failed, and take corrective action.
BIP13047
Rolled back a globally-coordinated transaction on WebSphere MQ queue manager <insert_1>.
Severity
0 : Information
Explanation
Successfully rolled back a globally-coordinated transaction on WebSphere MQ queue manager <insert_1>.
BIP13048
Failed to roll back a globally-coordinated transaction on WebSphere MQ queue manager <insert_1>.
Severity
20 : Error
Explanation
Failed to roll back a globally-coordinated transaction on WebSphere MQ queue manager <insert_1> because of reason code <insert_2>.
Response
Use reason code <insert_2> to determine why the roll back failed, and take corrective action.
BIP13049
Wrote message to WebSphere MQ topic <insert_1>.
Severity
0 : Information
Explanation
Successfully wrote a message to WebSphere MQ topic <insert_1> on queue manager <insert_2>
BIP13050
Failed write to WebSphere MQ topic <insert_1>.
Severity
20 : Error
Explanation
Failed to write a message to WebSphere MQ topic <insert_1> on queue manager <insert_2> because of reason code <insert_3>
Response
Use reason code <insert_3> to determine why writing the message failed.
BIP13051
Error occurred in common connector <insert_1>: <insert_2>
Severity
20 : Error
Explanation
An error has occurred in the common connector with name <insert_1>. The text of the error was <insert_2>.
Response
Check the system log or standard error output for more information.
BIP13052
The SalesforceRequest connector is about to perform the <insert_1> operation for object <insert_2> on Salesforce system <insert_3>.
Severity
0 : Information
BIP13053
The <insert_1> operation issued by the SalesforceRequest connector, for object <insert_2> with Salesforce ID <insert_3>, completed successfully.
Severity
0 : Information
Explanation
The <insert_1> operation completed successfully. The identifier might be blank if the operation does not require an identifier or did not provide one.
BIP13054
The <insert_1> operation issued by the SalesforceRequest connector, for object <insert_3> with Salesforce ID <insert_2>, failed with error <insert_4>.
Severity
20 : Error
Explanation
The <insert_1> operation failed with error code <insert_4> and error description <insert_5>. The identifier might be blank if the operation does not require an identifier or did not provide one.
Response
Use the information in the message to determine why the operation failed and take action to resolve the error.
BIP13055
The LoopBackRequest connector for data source <insert_1> is about to perform the <insert_2> operation on object <insert_3>.
Severity
0 : Information
BIP13056
The LoopBackRequest connector data source <insert_1> operation <insert_2> on object <insert_3> with ID <insert_4>, completed successfully.
Severity
0 : Information
Explanation
The <insert_2> operation completed successfully. The identifier might be blank if the operation does not require an identifier or did not provide one.
BIP13057
The LoopBackRequest connector data source <insert_1> operation <insert_2> on object <insert_3> with ID <insert_4>, failed with error <insert_5>.
Severity
20 : Error
Explanation
The <insert_2> operation failed with error code <insert_5> and error description <insert_6>. The identifier might be blank if the operation does not require an identifier or did not provide one.
Response
Use the information in the message to determine why the operation failed and take action to resolve the error.
BIP13058
Invoked the REST API operation <insert_1>. The operation was successful.
Severity
0 : Information
Explanation
HTTP method: <insert_2>
URL: <insert_3>
Request headers: <insert_4> bytes, request body: <insert_5> bytes
HTTP status code: <insert_6>
Response headers: <insert_7> bytes, response body: <insert_8> bytes
Total request time: <insert_9> ms
BIP13059
Invoked a REST API operation. The operation was successful.
Severity
0 : Information
Explanation
HTTP method: <insert_1>
URL: <insert_2>
Request headers: <insert_3> bytes, request body: <insert_4> bytes
HTTP status code: <insert_5>
Response headers: <insert_6> bytes, response body: <insert_7> bytes
Total request time: <insert_8> ms
BIP13060
Invoked the REST API operation <insert_1>. The operation was unsuccessful.
Severity
20 : Error
Explanation
HTTP method: <insert_2>
URL: <insert_3>
Request headers: <insert_4> bytes, request body: <insert_5> bytes
HTTP status code: <insert_6>
Response headers: <insert_7> bytes, response body: <insert_8> bytes
Total request time: <insert_9> ms
BIP13061
Invoked a REST API operation. The operation was unsuccessful.
Severity
20 : Error
Explanation
HTTP method: <insert_1>
URL: <insert_2>
Request headers: <insert_3> bytes, request body: <insert_4> bytes
HTTP status code: <insert_5>
Response headers: <insert_6> bytes, response body: <insert_7> bytes
Total request time: <insert_8> ms
BIP13062
Submitted a request for the REST API operation <insert_1>.
URL: <insert_1>
HTTP status code: <insert_2>
Response headers: <insert_3> bytes, response body: <insert_4> bytes
Total request time: <insert_5> ms
BIP13072
Web Service invocation was unsuccessful.
Severity
0 : Information
Explanation
URL: <insert_1>
IIB error code: <insert_2>
Total request time: <insert_3> ms
BIP13080
Started transferring a file. Source: <insert_1> Destination: <insert_2> Operation type: <insert_3> Maximum size: <insert_4>
Severity
0 : Information
Explanation
Source: <insert_1>
Destination: <insert_2>
Operation type: <insert_3>
Maximum size: <insert_4>
BIP13081
Transferring file from <insert_1> to <insert_2> using operation type <insert_3>. <insert_4> of <insert_5> bytes transferred. <insert_6> complete.
Severity
0 : Information
Explanation
A File Node is transferring a file to of from a remote system.
Source: <insert_1>
Destination: <insert_2>
Operation type: <insert_3>
Bytes transferred: <insert_4>
Size of file: <insert_5>
Percent complete: <insert_6>
BIP13082
Finished transferring a file. Source: <insert_1> Destination: <insert_2> Operation type: <insert_3> Maximum size: <insert_4>
Severity
0 : Information
Explanation
Source: <insert_1>
Destination: <insert_2>
Operation type: <insert_3>
Maximum size: <insert_4>