Message flow <insert_1> is about to make an outbound request for method <insert_3>.
Severity
0 : Information
Explanation
The message flow <insert_1> includes a <insert_2> request node. The node is about to make a request to call method <insert_3> on the EIS system.
BIP11002
The call to method <insert_3> was successful.
Severity
0 : Information
Explanation
The message flow <insert_1> includes a <insert_2> request node. The request to call method <insert_3> was successful.
BIP11003
The call to method <insert_3> failed and the following error was received: <insert_4>.
Severity
20 : Error
Explanation
The message flow <insert_1> includes a <insert_2> request node. The request to call method <insert_3> failed because of error <insert_4>.
BIP11004
A <insert_1> Adapter has received a message, which will be processed by message flow <insert_3>.
Severity
0 : Information
Explanation
A <insert_1> WebSphere Adapter named <insert_2> received an inbound message. The business method name was <insert_5>. The message will be processed by the node <insert_4> in flow <insert_3>. The node has secondary adapters configured as <insert_6> and the details for the method were found in the adapter <insert_7>.
BIP11005
Adapter <insert_1> is about to send a synchronous reply message back to the calling EIS System.
Severity
0 : Information
Explanation
A <insert_2> WebSphere Adapter named <insert_1> received an inbound message which required a reply. This reply will be sent back to the <insert_2> system via the reply node <insert_4> in flow <insert_3>.
BIP11006
Connected to <insert_1>.
Severity
0 : Information
Explanation
The WebSphere Adapter <insert_2> has established a new connection to the <insert_1> EIS system. The connection identifier is <insert_3>.
BIP11007
Disconnected from the <insert_1> system.
Severity
0 : Information
Explanation
The Adapter <insert_2> has closed the connection to the <insert_1> system. This may be because the adapter is being undeployed, the integration node is stopping or the idle timeout for the connection has been reached.
BIP11008
Adapter <insert_1> has closed an idle connection.
Severity
0 : Information
Explanation
A WebSphere Adapter named <insert_1> maintains connections to an EIS system. The idle timeout on the connection was set to <insert_2> and that timeout has expired without the connection being reused. The connection has therefore been closed.
BIP11009
Failure in <insert_1> connection.
Severity
20 : Error
Explanation
The connection between Adapter <insert_2> and the <insert_1> system has been lost. The reason provided by the adapter is: <insert_3>.
BIP11050
CICS Connectivity Error occurred. The error was <insert_1>.
Severity
20 : Error
Explanation
There was a problem in connecting to the CICS Server.
Response
Likely errors include INVALID_PARTNER_STATE, which means that the IPIC connection with the specified applid/qualifier in the CICSConnection configurable service has already been acquired by another client application, preventing the integration server from establishing the connection itself. This is often because multiple integration servers are attempting to use such a configurable service, which is not allowed.
BIP11051
Calling CICS Program <insert_1>.
Severity
0 : Information
Explanation
Calling CICS Program <insert_1> with a CICS Channel data structure using mirror transaction <insert_2>. User ID is <insert_3> and timeout is <insert_4> seconds.
BIP11052
Calling CICS Program <insert_1>.
Severity
0 : Information
Explanation
CICS program <insert_1> is being called with a CICS COMMAREA data structure of length <insert_4>, using mirror transaction <insert_2>. The user ID is <insert_3> and the timeout is <insert_5> seconds.
BIP11053
Successfully called CICS program <insert_1>.
Severity
0 : Information
Explanation
The CICSRequest node has successfully made a call to program <insert_1> on CICS server <insert_2>.
BIP11054
Error occurred when calling CICS program <insert_1>.
Severity
20 : Error
Explanation
An error occurred when calling CICS program <insert_1> on server <insert_2>. Refer to the information center for guidance on configuring the connection to CICS. The error was <insert_3>.
BIP11055
Message contains a security identity <insert_1>, which will be propagated to CICS.
Severity
0 : Information
Explanation
The CICSRequest node has found a security identity <insert_1> within the message, and this identity will be used on the request when calling program <insert_2>.
BIP11056
Security failure occurred when calling CICS with username <insert_1>.
Severity
20 : Error
Explanation
The CICSRequest node received a security error when attempting to use username <insert_1> to call CICS program <insert_2>.
BIP11057
Communications failure when connecting to CICS server <insert_1>.
Severity
0 : Information
Explanation
The CICSRequest node received a communications failure when connecting to CICS server <insert_1>.
BIP11058
Started a new CICS Transaction as part of integration node flow processing.
Severity
0 : Information
Explanation
The integration node is coordinating a transaction that includes CICS resources. The first request to a given CICS resource <insert_1> causes a new CICS transaction to start.
BIP11059
Committed CICS Resources for flow transaction.
Severity
0 : Information
Explanation
The work sent to CICS server <insert_1>, which was associated with the integration node flow transaction, has been committed.
BIP11060
Rolled back the CICS resources associated with <insert_1> that were involved in the integration node transaction.
Severity
20 : Error
Explanation
The CICS resources <insert_1> that have been updated under the flow transaction have been rolled back.
BIP11061
CICS program <insert_1> abended with abend code <insert_2>.
Severity
20 : Error
Explanation
An abend occurred when calling CICS program <insert_1>; the abend code is <insert_2>. This abend will cause work that was done under the mirror task <insert_3> to be rolled back, which in turn will cause the flow transaction to be rolled back unless it is handled.
BIP11062
Timeout occurred during a CICS request to run <insert_1>.
Severity
20 : Error
Explanation
A timeout has occurred during a CICS request to call <insert_1>. The timeout was set to <insert_2> seconds.
BIP11063
SSL connection failure when connecting to CICS server <insert_1>.
Severity
20 : Error
Explanation
An SSL connection to CICS has been specified, but no connection could be established to the target CICS server. This might be due to network or connectivity issues, or because the trust negotiation could not occur using the keystore <insert_2>. Refer to the information center for guidance on securing the CICS connection.
BIP11064
Enlisted CICS Resource <insert_1> in a globally-coordinated transaction.
Severity
0 : Information
Explanation
The CICS Resource <insert_1> has successfully enlisted in a globally-coordinated transaction running on this thread.
BIP11065
Failed to enlist CICS Resource <insert_1> in a globally coordinated transaction.
Severity
0 : Information
Explanation
The CICS Resource <insert_1> did not receive a valid transaction ID (XID) from the transaction manager.
BIP11066
CICS Resource <insert_1> is coordinated by the global transaction manager.
Severity
0 : Information
Explanation
A successful link was established between the global transaction manager and the CICS Resource <insert_1>. This resource can be used for globally-coordinated transactions.
BIP11067
Failure to globally coordinate CICS Resource <insert_1>.
Severity
0 : Information
Explanation
The global transaction manager did not connect to the integration node, and so CICS resources cannot be transactionally coordinated. Message processing will be rolled back on this thread, and the CICSRequest node is not processed. Refer to the product documentation for how to configure the transaction manager. On z/OS, the transaction manager is RRS, and on other platforms, it is the WebSphere MQ queue manager that is associated with the integration node.
BIP11068
Resource <insert_1> has been requested to perform an XA Recovery operation. The number of in-doubt transactions returned is <insert_2>.
Severity
0 : Information
Explanation
When the global transaction manager starts, it retrieves a list of all in-doubt transactions from each resource. In this case, the resource has returned <insert_2> transactions.
BIP11069
Resource <insert_1> was requested to prepare transactional resources for commit processing. XA Return code is <insert_2>.
Severity
0 : Information
Explanation
In a globally-coordinated transaction, Multiple are coordinated as part of an XA commit operation. At this stage, the global transaction manager requested that the resources <insert_1> prepare its resources. The return code was <insert_2>, which is an XA return code. Note that XA_RDONLY(3) is a successful response, because it means that the resources were not updated and can thus use the read-only optimization in XA processing, and therefore need to take no further part in the XA processing for this UOW.
BIP11070
Resource <insert_1> was requested to commit transactional resources. XA Return code is <insert_2>.
Severity
0 : Information
Explanation
In a globally-coordinated transaction, multiple resources are coordinated as part of an XA commit operation. At this stage, the global transaction manager requested that the resource <insert_1> commit its processing. The return code was <insert_2>, which is an XA return code.
BIP11071
Resource <insert_1> was requested to rollback transactional resources. XA Return code is <insert_2>.
Severity
0 : Information
Explanation
In a globally-coordinated transaction, multiple resources are coordinated as part of an XA commit operation. At this stage, the global transaction manager requested that the resource <insert_1> is rolled back. The return code was <insert_2>, which is an XA return code.
BIP11101
Put data into map <insert_1>
Severity
0 : Information
Explanation
The message flow has successfully put data into map <insert_1>, in cache <insert_2>, using key <insert_3>.
BIP11102
Cleared all data from map <insert_1>
Severity
0 : Information
Explanation
The message flow has successfully cleared all data from map <insert_1>, in cache <insert_2>.
BIP11103
Got data from map <insert_1>
Severity
0 : Information
Explanation
The message flow has successfully got data from map <insert_1>, in cache <insert_2>, using key <insert_3>.
BIP11104
Updated data in map <insert_1>
Severity
0 : Information
Explanation
The message flow has successfully updated data in map <insert_1>, in cache <insert_2>, using key <insert_3>.
BIP11105
Inserted data into map <insert_1>
Severity
0 : Information
Explanation
The message flow has successfully inserted data into map <insert_1>, in cache <insert_2>, using key <insert_3>.
BIP11106
Removed data from map <insert_1>
Severity
0 : Information
Explanation
The message flow has successfully removed data from map <insert_1>, in cache <insert_2>, using key <insert_3>.
BIP11107
Checked whether key exists in map <insert_1>
Severity
0 : Information
Explanation
The message flow has checked whether map <insert_1> in cache <insert_2> contains key <insert_3>.
BIP11108
Failed to complete action on map <insert_1>
Severity
20 : Error
Explanation
The message flow has failed to complete an action on map <insert_1> in cache <insert_2>. Details of the exception are: <insert_3>.
BIP11109
Connected to cache <insert_1>
Severity
0 : Information
Explanation
The integration server has successfully connected to cache <insert_1>.
BIP11110
Failed to connect to cache <insert_1>
Severity
20 : Error
Explanation
The integration server has failed to connect to cache <insert_1>. Details of the exception are: <insert_2>.
BIP11111
Started catalog server
Severity
0 : Information
Explanation
The catalog server <insert_1> has successfully started.
BIP11112
Retrying start of cache components
Severity
10 : Warning
Explanation
The WebSphere eXtreme Scale server <insert_1> has not started. The start will continue retrying in the background.
BIP11113
Failed to start catalog server
Severity
20 : Error
Explanation
The catalog server <insert_1> has failed to start. Details of the exception are: <insert_2>.
BIP11114
Started container server
Severity
0 : Information
Explanation
The container server <insert_1> has successfully started.
BIP11115
Failed to start container server
Severity
20 : Error
Explanation
The container server <insert_1> has failed to start. Details of the exception are: <insert_2>.
BIP11200
Matched <insert_1> rules in the decision service <insert_2>.
Severity
0 : Information
Explanation
The decision service <insert_2> was used to evaluate <insert_3> input parameters by node <insert_4>. <insert_1> rules were matched.
BIP11201
Failed to execute the rules in the decision service <insert_1>.
Severity
0 : Information
Explanation
The decision service detected the exception <insert_2>.
BIP11202
Accessed a remote decision service repository that is defined by the configurable service <insert_1> of type DecisionServiceRepository.
Severity
0 : Information
BIP11300
<insert_1> parsers have been created and cached on this thread.
Severity
10 : Warning
Explanation
When creating a parser of type <insert_2> the parser warning threshold was reached.
BIP11301
<insert_1> fields have been created and cached on a parser of type <insert_2>.
Severity
10 : Warning
Explanation
When creating a field on a parser of type <insert_2> the field warning threshold was reached.
BIP11302
There are <insert_1> parsers cached on this thread.
Severity
0 : Information
BIP11303
A Parser of type <insert_1> has been created at address <insert_2>. This thread now has <insert_3> cached parsers.
Severity
0 : Information
BIP11304
The Parser of type <insert_1> has been deleted from address <insert_2>. This thread now has <insert_3> cached parsers.
Severity
0 : Information
BIP11305
The Parser of type <insert_1> at address <insert_2> has been reset ready for re-use. This thread has <insert_3> cached parsers.
Severity
0 : Information
BIP11306
A Parser of type <insert_1> has been created at address <insert_2>.
Severity
0 : Information
BIP11307
The Parser of type <insert_1> has been deleted from address <insert_2>.
Severity
0 : Information
BIP11308
The Parser of type <insert_1> at address <insert_2> has been reset ready for re-use.
Severity
0 : Information
BIP11309
<insert_1> XPath expressions have been created and cached.
Severity
0 : Information
Explanation
When creating an XPath expression the cache entry warning threshold was reached.
BIP11310
XPath cache flush has occurred. Previous cache size <insert_1>. New cache size <insert_2>.
Severity
0 : Information
Explanation
When creating an XPath expression the cache maximum size was reached and a cache flush occurred.
BIP11501
Received data from input node <insert_1>.
Severity
0 : Information
Explanation
The input node <insert_1> has received data and has propagated it to the message flow <insert_2>.
BIP11502
Received a message from input node <insert_1> that is the last message in a message group.
Severity
0 : Information
Explanation
The input node <insert_1> has been configured to use message groups, and has received the last message in that message group. It has propagated the message to message flow <insert_2>.
BIP11503
Received a message from input node <insert_1> that forms part of a message group.
Severity
0 : Information
Explanation
The Input node <insert_1> has been configured to use message groups, and has received a message as part of that message group. It has propagated the message to message flow <insert_2>.
BIP11504
Waiting for data from input node <insert_1>.
Severity
0 : Information
Explanation
A thread is waiting for data from input node <insert_1> in flow <insert_2>.
BIP11505
Started a globally-coordinated transaction.
Severity
0 : Information
Explanation
A globally-coordinated transaction has been started to coordinate work for the message flow thread.
BIP11506
Committed a local transaction.
Severity
0 : Information
Explanation
A local transaction has been committed for work done on the message flow thread.
BIP11507
Rolled back a local transaction.
Severity
10 : Warning
Explanation
A local transaction has been rolled back for work done on the message flow thread.
BIP11508
Committed a globally-coordinated transaction successfully.
Severity
0 : Information
Explanation
A globally-coordinated transaction has been successfully committed for work on the message flow thread.
BIP11509
Failed to commit a globally-coordinated transaction.
Severity
20 : Error
Explanation
A globally-coordinated transaction failed to commit successfully.
BIP11510
Rolled back a globally-coordinated transaction.
Severity
10 : Warning
Explanation
A globally-coordinated transaction has been rolled back for work performed on the message flow thread.
BIP11511
Failed to parse input data.
Severity
10 : Warning
Explanation
The input data produced a warning. The data might be corrupt or truncated. For further information, examine the relevant transport and the system event log.
BIP11512
Failed to read input data
Severity
20 : Error
Explanation
Data arriving at the input node has caused a failure. If the flow is processing a message group, that group will be rolled back. Otherwise, this request will fail, but previous work in the batch will be committed.
BIP11513
Flow reconfiguration or redeployment is in progress; the flow is not waiting for data from input node <insert_1>.
Severity
10 : Warning
Explanation
The flow <insert_2> is being reconfigured or redeployed, therefore this input node is not currently polling or waiting for data.
BIP11514
Warning when starting coordinated transaction. MQ Reason code <insert_1>.
Severity
10 : Warning
Explanation
Warning when starting transaction coordinated by WebSphere MQ The message flow continues, but the transaction may not be being coordinated as expected, and this may cause subsequent errors or unpredictable results.
BIP11515
Unable to start a globally-coordinated transaction. MQ Reason code <insert_1>.
Severity
10 : Warning
Explanation
Unable to start a globally-coordinated transaction coordinated by WebSphere MQ Consult the product documentation. Global Transaction support requires additional configuration as the transactional resources must be defined to the queue manager.