BIP3000-3999: Runtime components - Built-in message flow nodes

BIP3001: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3002: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3003: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3004: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3005: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3006: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3007: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3008: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3009: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3010: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3011: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3012: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3013: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3014: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3015: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3016: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3017: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3018: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3019: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3020: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3021: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3022: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3023: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3024: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3025: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3026: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3027: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3028: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3029: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3030: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3031: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3032: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3033: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3034: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3035: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3036: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3037: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3038: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3039: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3040: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3041: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3042: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3043: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3044: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3045: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3046: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3047: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3048: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3049: Exception thrown by throw node <insert_2>; text is <insert_1>.
Severity: 0 : Information
Explanation: The throw node <insert_2> has received a message and thus has thrown an exception as this is its normal behavior. The message text associated with this exception is <insert_1>.
Response: Since this is application generated (by message flow behavior), the user action is determined by the message flow and the type of exception generated.

BIP3050: the ESQL REPLICATE function has tried to create a string that is too large. The maximum size is 32*1024*1024 (33,554,432) . The size of the string to be created by replication is (<insert_4> * <insert_5>).
Severity: 20 : Error
Explanation: The expression supplying the parameter must evaluate to a value within a suitable range. The given expression does not do so.
Response: Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.

BIP3051: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3052: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3053: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3054: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3055: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3056: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3057: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3058: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3059: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3060: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3061: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3062: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3063: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3064: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3065: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3066: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3067: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3068: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3069: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3070: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3071: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3072: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3073: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3074: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3075: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3076: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3077: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3078: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3079: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3080: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3081: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3082: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3083: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3084: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3085: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3086: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3087: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3088: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3089: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3090: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3091: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3092: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3093: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3094: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3095: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3096: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3097: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3098: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3099: Error message <insert_1> from trace node <insert_2>.
Severity: 20 : Error
Explanation: The trace node <insert_2> has output the specified error message.
Response: This is an error message provided by the message flow designer. The user response will be determined by the local environment.

BIP3101: The HTTP Listener has started successfully (process <insert_1> port <insert_2>)
Severity: 0 : Information
Explanation: The HTTP Listener process has started, and is currently listening on the integration node-specific TCPIP port
Response: No user action required.

BIP3102: Unable to create a Java VM.
Severity: 30 : Severe error
Explanation: This is an internal error.
Response: Stop the integration node and contact your IBM support center.

BIP3103: Java class <insert_1> could not be found.
Severity: 20 : Error
Explanation: This is an internal error, possibly due to a faulty installation.
Response: Stop the integration node and contact your IBM support center.

BIP3104: Java method <insert_2> in class <insert_1> could not be found.
Severity: 20 : Error
Explanation: This is an internal error, possibly due to a faulty installation.
Response: Stop the integration node and contact your IBM support center.

BIP3105: An instance of Java class <insert_1> could not be created.
Severity: 30 : Severe error
Explanation: This is an internal error, possibly due to a faulty installation.
Response: Stop the integration node and contact your IBM support center.

BIP3106: Java exception caught via the JNI from the <insert_1> class: exception text <insert_2>.
Severity: 30 : Severe error
Explanation: This may be an internal error, possibly due to a faulty installation. Review of the exception text may indicate a solution.
Response: Stop the integration node and if the exception text does not allow you to solve the problem then you should contact your IBM support center.

BIP3107: Java field <insert_2> in class <insert_1> could not be found.
Severity: 20 : Error
Explanation: This is an internal error, possibly due to a faulty installation.
Response: Stop the integration node and contact your IBM support center.

BIP3108: Unable to initialize the listener environment. Exception text <insert_1>1
Severity: 30 : Severe error
Explanation: The HTTP listener detected an error whilst initializing its working environment. Examine previous error messages for details of the cause of this problem.
Response: Contact your IBM support center.

BIP3109: Invalid value (<insert_1>) for attribute (<insert_2>); node class=<insert_3>.
Severity: 20 : Error
Explanation: A configuration request was received which specified a value for the indicated attribute of the node class. However, this value could not be converted to a wide string. The configuration request is terminated.
Response: Modify the configuration request to specify a valid value for the attribute, and retry the request.

BIP3110: Integration node internal error: diagnostic information <insert_1>.
Severity: 20 : Error
Explanation: An internal software error has occurred in the integration node. Further messages will indicate the effect of this error on the integration node's transactions. The diagnostic information associated with this message is: <insert_1>.
Response: Shutdown and restart the integration node. If the problem continues to occur, then restart the system. If the problem still continues to occur contact your IBM support center.

BIP3111: An internal error has occurred in node <insert_1>.
Severity: 20 : Error
Explanation: The instance of the WebSphere MQ manager class could not be located when required by node <insert_1>. The current message flow has been terminated. This error is probably indicative of an internal software malfunction.
Response: If this occurs frequently, restart the integration node. If it continues to occur, contact your IBM support center.

BIP3112: An internal error has occurred in node <insert_4>.
Severity: 20 : Error
Explanation: A message flow node failed to connect to the WebSphere MQ queue manager <insert_1>1 with the resulting WebSphere MQ completion and reason codes of <insert_2> and <insert_3>. This queue manager is used for internal communication between the listener process and the message flow. The message flow attempts to open the queue periodically until successful. The message flow is not fully operational until this has been done.
Response: Ensure the queue manager is operational. If this problem occurs frequently, restart the integration node. If it continues to occur, contact your IBM support center.

BIP3113: Exception detected in message flow <insert_1> (integration node <insert_2>)
Severity: 20 : Error
Explanation: A fault was detected while processing a message.
Response: None.

BIP3114: An internal error has occurred in node <insert_5>.
Severity: 20 : Error
Explanation: A message flow node failed to open the WebSphere MQ queue <insert_2> owned by queue manager <insert_1>1 with the resulting WebSphere MQ completion and reason codes of <insert_3> and <insert_4>. This queue is used for internal communication between the listener process and the message flow. The message flow attempts to open the queue periodically until the queue is defined. The message flow is not fully operational until this has been done.
Response: If this occurs frequently, restart the integration node. If it continues to occur, contact your IBM support center.

BIP3115: An internal error has occurred in message flow node or resource manager <insert_3>.
Severity: 20 : Error
Explanation: Unable to get message from WebSphere MQ queue <insert_2> owned by queue manager <insert_1>. This queue is used for internal communication between the HTTP listener process and the message flow. The message flow node or resource manager periodically retries the MQGET until it is successful.
Response: Ensure that the queue manager is operational. If this problem occurs frequently, restart the integration node. If the problem continues to occur, contact your IBM support center.

BIP3116: SOAP parser has failed; reply node <insert_1>.
Severity: 20 : Error
Explanation: The IBM Integration Bus node <insert_1> has received a message tree for the reply, but the SOAP parser has failed. The reply message might have been constructed incorrectly.
Response: Check the message flow to determine whether the message is being built correctly. If the message tree was propagated from a Failure terminal, you might need to construct the message based on the content of the exception list. Correct the problem and redeploy the message flow.

BIP3117: An internal error has occurred in node <insert_5>.
Severity: 20 : Error
Explanation: A message flow node failed to write to the WebSphere MQ queue <insert_2> owned by queue manager <insert_1> with the resulting WebSphere MQ completion and reason codes of <insert_3> and <insert_4>. This queue is used for internal communication between the listener process and the message flow.
Response: Correct any problems relating to the WebSphere MQ queue manager. If this problem occurs frequently, restart the integration node. If it continues to occur, contact your IBM support center.

BIP3118: Reply message successfully sent by reply node <insert_3> to the requesting HTTP client
Severity: 0 : Information
Explanation: Reply message successfully sent by reply node <insert_3> to the requesting HTTP client via IBM Integration Bus queue <insert_2> connected to queue manager <insert_1>.
Response: No user action required.

BIP3119: An internal error has occurred in node <insert_5>.
Severity: 20 : Error
Explanation: A message flow node received a warning when writing to the WebSphere MQ queue <insert_2>2 owned by queue manager <insert_1> ; WebSphere MQ completion and reason codes were <insert_3>3 and <insert_4>. This queue is used for internal communication between the listener process and the message flow, and warning messages should not occur in normal operation.
Response: Correct any problems relating to the WebSphere MQ queue manager. If this problem occurs frequently, restart the integration node. If it continues to occur, contact your IBM support center.

BIP3120: Exception condition detected on input node <insert_1>.
Severity: 20 : Error
Explanation: The input node <insert_1> detected an error whilst processing a message. The message flow has been rolled-back and a fault message returned to the requesting client. Following messages will indicate the cause of this exception.
Response: Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.

BIP3121: An internal error was detected, and the request has not been processed. See the error logs associated with the integration node for more details.
Severity: 20 : Error
Explanation: This message is used as a faultstring in a SOAP fault message.
Response: None.

BIP3122: Message received and propagated to <insert_2> terminal of HTTP input node <insert_1>.
Severity: 0 : Information

BIP3123: Exception condition detected on input node <insert_2>: object label <insert_1>.
Severity: 20 : Error
Explanation: The input node <insert_2> detected an error whilst processing a message. The message flow has been rolled-back and a fault message returned to the requesting client. Following messages will indicate the cause of this exception which was generated in the STL container classes.
Response: Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.

BIP3124: An internal error has occurred in node <insert_4>.
Severity: 20 : Error
Explanation: A warning was received when node <insert_4> got a message from WebSphere MQ queue <insert_1>: MQCC=<insert_2>; MQRC=<insert_3>; node <insert_4>. This queue is used for internal communication between the listener process and the message flow, and warning messages should not occur in normal operation.
Response: Correct any problems relating to the WebSphere MQ queue manager. If this problem occurs frequently, restart the integration node. If it continues to occur, contact your IBM support center.

BIP3125: The HTTP Reply node has returned from waiting for an acknowledgement of the reply message from the listener process.
Severity: 30 : Severe error
Explanation: The HTTP reply node <insert_5> attempted to receive a message from the specified queue <insert_2> connected to queue manager <insert_1>. The MQCC was <insert_3> and the MQRC was <insert_4>.
Response: No action.

BIP3126: The HTTP Reply node has sent the reply message to the HTTP client via the listener process.
Severity: 0 : Information
Explanation: The HTTP reply node <insert_5> attempted to put a message to the specified queue <insert_2> connected to queue manager <insert_1>. The MQCC was <insert_3> and the MQRC was <insert_4>.
Response: No action.

BIP3127: An internal error was detected. See the error logs associated with the integration node for more details.
Severity: 20 : Error
Explanation: This message is used as a faultstring in a SOAP fault message.
Response: None.

BIP3128: Failed to locate Java class <insert_1>.
Severity: 30 : Severe error
Explanation: The Java class <insert_1> could not be found.
Response: This is an internal error and you should contact your IBM support center.

BIP3129: Failed to locate Java method <insert_1> in class <insert_2>.
Severity: 30 : Severe error
Explanation: The Java method <insert_1> in class <insert_2> could not be found.
Response: This is an internal error and you should contact your IBM support center.

BIP3130: An exception was detected during message flow processing: <insert_1>1 See the error logs associated with the integration node for more details.
Severity: 20 : Error
Explanation: This message is used as a faultstring in a SOAP fault message.
Response: None.

BIP3131: The HTTP Listener could not create a necessary working directory: <insert_1> (error code <insert_2>)
Severity: 20 : Error
Explanation: The HTTP Listener needs to create a working directory for the servlet engine to function correctly. This directory could not be created, and the listener will exit.
Response: Make sure the integration node has the necessary permissions to create the required directory.

BIP3132: The HTTP Listener has started listening on port <insert_1> for <insert_2> connections.
Severity: 0 : Information
Explanation: The HTTP Listener process is currently listening on the integration node-specific TCPIP port <insert_1> for connections of type <insert_2>
Response: No user action required.

BIP3133: The HTTP Listener has stopped listening on port <insert_1> for <insert_2> connections.
Severity: 0 : Information
Explanation: The HTTP Listener process is no longer listening on the integration node-specific TCPIP port <insert_1> for connections of type <insert_2>.
Response: No user action required.

BIP3134: A necessary working directory could not be created: <insert_1> (error code <insert_2>)
Severity: 20 : Error
Explanation: A working directory is needed for a configuration file. This directory could not be created, and proper operation of the integration node is not assured.
Response: Make sure the integration node has the necessary permissions to create the required directory.

BIP3135: An exception occurred while starting the servlet engine connector. Exception text is <insert_1>1
Severity: 30 : Severe error
Explanation: There are many possible causes of this error. Common causes are:
1: The SSL keystoreFile does not exist or could not be found at the location specified in the 'keystoreFile' property or in the default location of: (<home directory of user-id running the integration node>\.keystore)
2: The SSL keystoreFile was found but was accessed with an incorrect password.
3: The SSL key alias in the keystore has a password that is different from the keystore password.
However, this may be an internal error, possibly due to a faulty installation. A review of the exception text may indicate a solution.
Response: Stop the integration node and if the exception text does not allow you to solve the problem then you should contact your IBM support center.

BIP3136: A timeout occurred whilst sending reply data to the HTTP client. Timeout in seconds: <insert_1>1
Severity: 30 : Severe error
Explanation: This may be a transient error, such as a network timeout, or it could be that the client is no longer responding.
Response: None.

BIP3137: An exception occurred whilst sending reply data to the HTTP client: <insert_1>
Severity: 30 : Severe error
Explanation: This may be a transient error, such as a network timeout, or it could be that the client is no longer responding.
Response: Examine the exception text to determine what caused the error.

BIP3138: An attribute conflict was detected between two HTTP Input Nodes. The timeout value specified for node <insert_1> using URL selector <insert_2> was <insert_3>, but a previous HTTP Input Node has already specified a value of <insert_4> for the same URL selector. The new value of <insert_3> will be used.
Severity: 10 : Warning
Explanation: The HTTP listener process can only use one timeout value for any given URL selector. Unexpected results may occur when multiple input nodes specify different timeout values for the same URL selector.
Response: Change the timeout values for the HTTP Input Nodes to remove the conflict, and redploy the configuration.

BIP3139: A configuration file <insert_1> could not be opened for writing.
Severity: 20 : Error
Explanation: The configuration file needs to be updated to allow for correct integration node operation, but the integration node could not open the file for writing.
Response: Make sure the integration node has the necessary permissions to write to the required file.

BIP3140: The HTTP listener process could not be started. integration node name <insert_1>;
Severity: 20 : Error
Explanation: The integration node was unable to start an HTTP listener process.
Response: Ensure that the executable is available and that the integration node's service userid has permission to run the executable.

BIP3141: The integration node has detected that the HTTP listener (process ID <insert_1>), has shut down abnormally.
Severity: 20 : Error
Explanation: An HTTP listener process ended abnormally.
Response: Investigate the reasons for the problem.

BIP3142: Internal error in the Admin Agent: <insert_1>
Severity: 30 : Severe error
Explanation: An error has occurred during HTTP listener startup or shutdown.
Response: See other error messages for information on how this error happened.

BIP3143: Message does not contain valid HTTP context information
Severity: 30 : Severe error
Explanation: HTTP context information is required for reply processing to be successful. The needed information was not found in the incoming message, and no HTTP reply can be produced.
Response: Provide the required HTTP context information.

BIP3144: An error has occurred during HTTP listener startup: the specified TCPIP port (<insert_1>) is already in use.
Severity: 30 : Severe error
Explanation: The HTTP listener needs to bind to a TCPIP port for correct operation to be possible. The integration node-specific TCPIP port number <insert_1> is in use by another application.
Response: Stop other applications from using the specified port, or change the integration node-specific port.

BIP3145: Message propagated to failure terminal; node <insert_1>.
Severity: 0 : Information
Explanation: Node <insert_1> has received an HTTP request message, but an error occurred before the message could be propagated to the output terminal. The integration node is propagating the message to the failure terminal of the node.
Response: Examine the other messages and the message flow to determine why the message is not being received as expected. Correct this situation if possible. Perform any local error recovery processing required.

BIP3146: Error detected whilst processing a message <insert_1>.
Severity: 20 : Error
Explanation: The integration node detected an error whilst processing a message in node <insert_1>. The message has been augmented with an exception list and has been propagated to the node's catch terminal for further processing.
Response: See the following messages for details of the error.

BIP3147: The timeout terminal on input node <insert_1> in message flow <insert_2> is connected but will not used.
Severity: 10 : Warning
Explanation: For SOAPInput nodes the timeout terminal can only be used with the HTTP transport. For HTTPInput nodes the timeout terminal can only be used with the embedded integration server listener.
Response: If the use of the timeout terminal is required for SOAPInput nodes then select the HTTP transport. If the use of the timeout terminal is required for HTTPInput nodes then configure the integration server to use the embedded listener.

BIP3148: The Decompress input message option on HTTP input node <insert_1> in message flow <insert_2> was selected but will not be used.
Severity: 10 : Warning
Explanation: For HTTPInput nodes the Decompress input message option can only be used with the embedded integration server listener.
Response: If the use of the Decompress input message option is required for HTTPInput nodes then configure the integration server to use the embedded listener.

BIP3149: The Request Node <insert_1> failed to decompress a response using the Content-Encoding token <insert_2>.
Severity: 20 : Error
Explanation: The Request node has received a response with a Content-Encoding HTTP header. The response could not be decompressed using this Content-Encoding.
Response: The Content-Encoding HTTP header must contain a supported Content-Encoding token of gzip or deflate. The Response message must be compressed correctly using gzip or deflate. If it is not then subsequent messages may indicate why the decompression failed.

BIP3150: A socket error occurred. Operation: <insert_1>. Error Code: <insert_2>. Error Text: <insert_3>.
Severity: 30 : Severe error
Explanation: An error occurred whilst performing a TCP/IP socket operation. This may be a temporary error, such as a server not responding, or a symptom of an invalid hostname or port number.
Response: See the following messages for information pertaining to this error.

BIP3151: A socket operation timed out. Operation: <insert_1>. Error Code: <insert_2>. Timeout in milliseconds: <insert_4>. Error Text: <insert_3>.
Severity: 30 : Severe error
Explanation: A timeout occurred whilst performing a TCP/IP socket operation. This may be a transient error, such as a server is busy or it could be that the server is no longer responding.
Response: See the following messages for information pertaining to this error.

BIP3152: Socket error detected whilst invoking Web service located at host <insert_1>, port <insert_2>, path <insert_3>.
Severity: 30 : Severe error
Explanation: This may be a transient error, such as a server not responding, or a symptom of an invalid hostname or port number.
Response: Check that the hostname and port number are valid, and point to a functioning Web service.

BIP3153: Error detected whilst invoking Web service located at host <insert_1>, port <insert_2>, path <insert_3>.
Severity: 30 : Severe error
Explanation: This may be a transient error, such as a server not responding or it may be a symptom of an invalid hostname and/or port number.
Response: Check that the hostname, port number and URL path are valid, and point to a functioning Web service.

BIP3154: An error has been detected whilst initializing the windows socket dll (WS2_32.dll). This could be because the dll could not be found or the version found is back level (not 2.2 compliant). Error Code: <insert_1>, Error Text: <insert_2>.
Severity: 30 : Severe error
Explanation: Make sure that WS2_32.dll exists, and is in the system path.

BIP3155: An error was found whilst parsing HTTP header data. Invalid non-numeric data found in the Content Length Header. The Content Length value was: <insert_1>.
Severity: 30 : Severe error
Explanation: The Content Length value should only contain the digits "1234567890".
Response: Ensure the Content Length HTTP header contains only numeric data

BIP3156: An error was found when parsing <insert_2> header data. A <insert_2> header name is empty or contains unsupported characters at position <insert_1>.
Severity: 20 : Error
Explanation: A <insert_2> header name cannot be empty, nor can it contain unsupported characters.
Response: This problem typically occurs if a CRLF has been omitted. Check the header contents and correct any errors.

BIP3157: An error was found whilst parsing <insert_2> header data. Multiple occurrences of a <insert_2> Header were found, when only one is allowed, or a non-folding <insert_2> Header was folded. The header was <insert_1>.
Severity: 30 : Severe error
Explanation: The <insert_2> Header <insert_1> cannot be folded or occur multiple times. Ensure that it occurs only once, and is not folded.

BIP3158: An error was found whilst parsing HTTP header data. Bad http header data found, as the single line limit was exceeded without a CRLF found. The first few characters from the data were: <insert_1>.
Severity: 30 : Severe error
Explanation: Ensure that the HTTP data contains CF-LF characters to delimit lines, and ensure that a single line is not too long.

BIP3159: An error was found whilst parsing HTTP header data. The data is not an HTTP Request or Response. Invalid HTTP Header data. The first few characters from the data were: <insert_2>. The current index (offset) into the HTTP Header data was: <insert_1>.
Severity: 30 : Severe error
Explanation: Ensure that the HTTP data is valid.

BIP3160: A socket was closed before all expected data was received. Received: <insert_1>. Expected: <insert_4>.
Severity: 30 : Severe error
Explanation: An error occurred whilst performing a TCP/IP socket operation. The socket was closed before all expected data was received, or the Content-Length returned by the server was invalid. HTTP Content-Length: <insert_2>. HTTP Headers length: <insert_3>.

BIP3161: A socket was closed before all expected data was received. Total data received: <insert_1>.
Severity: 30 : Severe error
Explanation: An error occurred whilst performing a TCP/IP socket operation. The socket was closed before all expected data was received, as the end of the HTTP headers have not been found. Ensure that the HTTP data is valid.

BIP3162: An HTTP error occurred. The HTTP Request-Line was: <insert_5>.
Severity: 30 : Severe error
Explanation: The HTTP Request Header bitstream (if any) to be used was: <insert_1>. The HTTP Request Message Body bitstream (if any) to be used was: <insert_2>. The HTTP Reply Header bitstream (if any) received from the server was: <insert_3>. The HTTP Reply Message Body bitstream (if any) received from the server was: <insert_4>. Ensure that the HTTP data is valid.
Response: See the following messages for information pertaining to this error.

BIP3163: An HTTP error occurred with Status Code <insert_1> and Status Line <insert_2>;
Severity: 30 : Severe error
Explanation: Ensure that the HTTP data is valid.
Response: See the following messages for information pertaining to this error.

BIP3164: The HTTPRequest Node <insert_2> failed to navigate to the message location specified. The location specified was: <insert_1>.
Severity: 30 : Severe error
Explanation: Ensure that the Location <insert_1> is valid for the message tree where it is used.
Response: Correct the specified message location.

BIP3165: An error occurred whilst performing an SSL socket operation. Operation: <insert_1>. Error Text: <insert_2>.
Severity: 30 : Severe error
Explanation: This may be a temporary error, such as a server not responding, or a symptom of an invalid hostname or port number.
Response: See the following messages for information pertaining to this error.

BIP3166: An SSL socket operation timed out. Operation: <insert_1>. Error Text: <insert_3>. Timeout in seconds: <insert_2>2
Severity: 30 : Severe error
Explanation: A timeout occurred whilst performing an SSL socket operation. This may be a transient error, such as a server is busy, or it could be that the server is no longer responding.
Response: See the following messages for information pertaining to this error.

BIP3167: An internal error occurred whilst attempting to access deployed WSDL data. Error Text: <insert_1>.
Severity: 30 : Severe error
Explanation: Deployed WSDL definitions are accessed at runtime for message flows using SOAP nodes. An internal error occurred whilst attempting to do this.
Response: This is an internal error. Contact your IBM support center.

BIP3168: The <insert_4> header with the name <insert_1> contains a forbidden character <insert_2> at location <insert_3>.
Severity: 20 : Error
Explanation: A header name cannot contain the unsupported characters: ' '(32), ':'(58) or any character outside the range of 33-126.
Response: Correct the application that is generating this header so that it generates names that are valid and do not contain invalid characters.

BIP3169: The <insert_1> header contains a blank field name.
Severity: 20 : Error
Explanation: All header names in the <insert_1> header must have at least one valid non-space character.
Response: Correct the application that is generating this header so that it generates names that are valid and do not contain invalid characters.

BIP3170: An invalid SOAP message was received in the SOAPExtract node <insert_1>.
Severity: 20 : Error
Explanation: The message does not contain a valid SOAP envelope
Response: Determine why the message contains no SOAP envelope

BIP3171: A message using an incorrect parser (<insert_1>) was detected in node: <insert_2>2
Severity: 20 : Error
Explanation: Only the following parsers are allowed: mrm,xmlns,xmlnsc
Response: None.

BIP3172: The XPath envelope destination does not match an existing element.
Severity: 20 : Error
Explanation: <insert_1> does not match an existing element.
Response: None.

BIP3173: Label node <insert_1> does not exists in the message flow
Severity: 20 : Error
Explanation: The route to operation has attempted to route to label node <insert_1>. No such label node exists in the message flow
Response: None

BIP3174: Invalid XPath expression
Severity: 20 : Error
Explanation: The XPath expression assigned to the <insert_1> property does not evaluate to a nodeset.
Response: None

BIP3175: The location identified by the XPath expression <insert_1> does not exist
Severity: 20 : Error
Explanation: None.
Response: None

BIP3176: The message passed to the SOAPEnvelope node <insert_1> is empty.
Severity: 20 : Error
Explanation: None.
Response: Determine why the SOAP body is empty

BIP3177: Tried to use the same endpoint for multiple node while using RM
Severity: 30 : Severe error
Explanation: The integration node received a configuration message containing an instruction to register the node <insert_1> at the following URL <insert_2>. When using reliable messaging only one node is permistted for each URL.
Response: Either remove the policy containing reliable messaging, or choose another URL. If the problem persists, contact your IBM support center.

BIP3178: There are multiple nodes using URL <insert_1>
Severity: 10 : Warning
Explanation: The input node <insert_1> is registered to use the URL <insert_2> which is already in use. You may see undesirable behaviour if each node and flow is configured differently.
Response: Either verify each node and flow are configured correctly, or choose another URL.

BIP3179: An error occurred during configuration using the following policy <insert_1>.
Severity: 30 : Severe error
Explanation: There was an error during configuration using the defined policy. This may be because of an invalid policy. A review of the exception text may indicate a solution.
Response: Determine the cause of the error and correct it.

BIP3180: Timed out while making a Reliable Messaging request to the destination <insert_1>.
Severity: 30 : Severe error
Explanation: No response was received from the service provider within the time allowed.
Response: Determine the cause of the error and correct it.

BIP3181: Reliable messaging is not supported in combination with <insert_1>.
Severity: 30 : Severe error
Explanation: An unsupported combination of settings was attempted when Reliable Messaging was enabled.
Response: Either disable Reliable Messaging, or change the incompatible setting.

BIP3182: A SOAPAsyncResponse node did not receive a response from <insert_1> because the timeout of <insert_2> milliseconds expired before a response was received.
Severity: 20 : Error
Explanation: A timeout prevented the SOAPAsyncResponse node from receiving a response. This may be a transient error, such as a server is busy or it could be that the server is no longer responding.
Response: See the following messages for information pertaining to this error.

BIP3183: An HTTPAsyncResponse node did not receive a response from <insert_1> because the timeout of <insert_2> milliseconds expired before a response was received.
Severity: 20 : Error
Explanation: A timeout prevented the HTTPAsyncResponse node from receiving a response. This may be a transient error, such as a server is busy or it could be that the server is no longer responding.
Response: See the following messages for information pertaining to this error.

BIP3184: An exception occurred whilst sending reply data to the client: <insert_1>
Severity: 30 : Severe error
Explanation: This may be a transient error, such as a network timeout, or it could be that the client is no longer waiting for a response.
Response: Examine the exception text to determine what caused the error.

BIP3185: An error has occurred while parsing the service map file <insert_1>.
Severity: 20 : Error
Explanation: See subsequent messages for details of the error.
Response: Check that you have specified the correct map file name and see subsequent messages for details of the error.

BIP3186: An error has occurred.
Severity: 20 : Error
Explanation: An unexpected error has occurred with either a node or associated resources.
Response: See subsequent messages for details of the error.

BIP3187: An internal error has occurred.
Severity: 20 : Error
Explanation: A node or its associated resources have encountered an error at initialization time.
Response: See subsequent messages for details of the error.

BIP3188: An error has occurred while performing a service mapping for the operation <insert_1>.
Severity: 20 : Error
Explanation: A runtime error has occurred while performing a service mapping for a request message.
Response: See subsequent messages for details of the error.

BIP3189: A error has occurred while performing a service mapping for the operation <insert_1>.
Severity: 20 : Error
Explanation: A runtime error has occurred performing a service mapping for a response message.
Response: See subsequent messages for details of the error.

BIP3190: An error has occurred while performing a service mapping for the operation <insert_1>.
Severity: 20 : Error
Explanation: A runtime error has occurred performing a service mapping for a fault message.
Response: See subsequent messages for details of the error.

BIP3191: The policy set or policy set binding <insert_1> contains an unrecognized configuration.
Severity: 10 : Warning
Explanation: Unrecognized configurations can cause unexpected behavior or failures.
Response: Only policy sets and policy set bindings that were created using the policy sets and policy set bindings editor should be used. If your policy set or policy set binding was created using the editor and you still see this message, contact your IBM support center.

BIP3192: Exception occurred during parsing an HTTP message; node <insert_1>.
Severity: 0 : Information
Explanation: Node <insert_1> has received an HTTP request message, but an error occurred before the message could be propagated to the output terminal. The failure terminal is not attached to a node so the message cannot be propagated.
Response: Examine the other messages and the message flow to determine why the message is not being received as expected. Correct this situation if possible. Perform any local error recovery processing required.

BIP3193: Too much data was received for a webservices request. Received: <insert_1>. Expected: <insert_4>.
Severity: 30 : Severe error
Explanation: An error occurred whilst performing a TCP/IP socket operation. Too much data was received, or the Content-Length returned by the server was invalid. HTTP Content-Length: <insert_2>. HTTP Headers length: <insert_3>.

BIP3194: The CORS property <insert_1> on the HTTP connector could not be set to the value <insert_2>.
Severity: 20 : Error
Explanation: The property <insert_1> is a boolean property and must be set to the value 'true' or 'false'.
Response: Set the property <insert_1> to a valid value.

BIP3195: The CORS property <insert_1> on the HTTP connector could not be set to the value <insert_2>.
Severity: 20 : Error
Explanation: The property <insert_1> is a comma separated list property. The value must not contain a leading comma or a trailing comma. The list must not contain any empty values.
Response: Set the property <insert_1> to a valid value.

BIP3196: The CORS property <insert_1> on the HTTP connector could not be set to the value <insert_2>.
Severity: 20 : Error
Explanation: The property <insert_1> is an integer property. The value must be a valid integer with a minimum value of <insert_3> and a maximum value of <insert_4>.
Response: Set the property <insert_1> to a valid value.

BIP3198: Message flow <insert_2> cannot service HTTP requests because it is registered under a disabled connector.
Severity: 10 : Warning
Explanation: The node <insert_1> of flow <insert_2> is registered under the connector <insert_3> of <insert_4> listener for which the disableConnector property is set to true. As a consequence, the listener did not start and flow <insert_2> cannot service HTTP requests.
Response: Enable the connector by setting disableConnector to false and restart the integration node.

BIP3201: (<insert_1>, <insert_2>) : EXTERNAL SCHEMA clause specified for the routine <insert_3> which is not defined to be LANGUAGE DATABASE.
Severity: 20 : Error
Explanation: The EXTERNAL SCHEMA clause is only valid for routines that have an implicit or explicit LANGUAGE DATABASE clause. The routine specified is <insert_3>.
Response: Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.

BIP3202: (<insert_1>, <insert_2>) : An error occurred when trying to resolve the Java class or method <insert_3> which is referred to by the routine <insert_4>.
Severity: 20 : Error
Explanation: Further messages are generated that explain the error in more detail.
Response: Correct the syntax of your Java expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.

BIP3203: <insert_1> is not a valid FORMAT expression for converting expression <insert_2> to type <insert_3>. Parsing failed at <insert_4>.
Severity: 30 : Severe error
Explanation: The FORMAT expression contains an unrecognized character for the given conversion. This error can occur if a FORMAT expression for a numerical conversion is used to convert to or from a DATE, TIME, TIMESTAMP, GMTTIME or GMTTIMESTAMP expression. It can also occur if an invalid character has not been quoted.
Response: Either replace the FORMAT expression with one of applicable type, or remove the offending character.

BIP3204: Input expression <insert_1> does not match FORMAT expression <insert_2>. Parsing failed to match <insert_3> with <insert_4>.
Severity: 30 : Severe error
Explanation: The given expression contains data which does not match the current element of the FORMAT expression.
Response: Either rewrite the FORMAT expression to match the input data or modify the input data to match the FORMAT expression.

BIP3206: Error in parsing FORMAT expression <insert_1>, parsing failed at <insert_2> because of an unexpected '0', Cannot have 0s after #s after 0s.
Severity: 30 : Severe error
Explanation: The FORMAT expression was incorrect, and must be rewritten.
Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most likely an incorrect character used.

BIP3207: Error in parsing FORMAT expression <insert_1>, parsing failed at <insert_2> because of a grouping separator after the decimal point is illegal.
Severity: 30 : Severe error
Explanation: The FORMAT expression was incorrect, and must be rewritten.
Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most likely an incorrect character used.

BIP3208: Error in parsing FORMAT expression <insert_1>, parsing failed at <insert_2> because of multiple decimal separators cannot be specified.
Severity: 30 : Severe error
Explanation: The FORMAT expression was incorrect, and must be rewritten.
Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most likely an incorrect character used.

BIP3209: Error in parsing FORMAT expression <insert_1>, parsing failed at <insert_2> because of multiple exponential symbols cannot be specified.
Severity: 30 : Severe error
Explanation: The FORMAT expression was incorrect, and must be rewritten.
Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most likely an incorrect character used.

BIP3210: Error in parsing FORMAT expression <insert_1>, parsing failed at <insert_2> because of grouping separators and exponents are mutually exclusive.
Severity: 30 : Severe error
Explanation: The FORMAT expression was incorrect, and must be rewritten.
Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most likely an incorrect character used.

BIP3211: Error in parsing FORMAT expression <insert_1>, parsing failed at <insert_2> because of malformed exponential pattern, must have at least one '0' in the exponent and at least one '#' or '0' in the integral or mantissa.
Severity: 30 : Severe error
Explanation: The FORMAT expression was incorrect, and must be rewritten.
Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most likely an incorrect character used.

BIP3212: Error in parsing FORMAT expression <insert_1>, parsing failed at <insert_2> because of unquoted special characters in suffix.
Severity: 30 : Severe error
Explanation: The FORMAT expression was incorrect, and must be rewritten.
Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most likely an incorrect character used.

BIP3213: Error in parsing FORMAT expression <insert_1>, parsing failed at <insert_2> because of unexpected separator, separators not allowed in prefix or negative pattern.
Severity: 30 : Severe error
Explanation: The FORMAT expression was incorrect, and must be rewritten.
Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most likely an incorrect character used.

BIP3214: Error in parsing FORMAT expression <insert_1>, parsing failed at <insert_2> because of too many percent characters.
Severity: 30 : Severe error
Explanation: The FORMAT expression was incorrect, and must be rewritten.
Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most likely an incorrect character used.

BIP3215: Error in parsing FORMAT expression <insert_1>; parsing failed at <insert_2> because of too many perMill characters.
Severity: 30 : Severe error
Explanation: The FORMAT expression was incorrect, and must be rewritten.
Response: Look at the reason given, and the point at which it failed, to determine what has gone wrong. Typically an incorrect character is used. Rewrite the expression.

BIP3216: Error in parsing FORMAT expression <insert_1>, parsing failed at <insert_2> because of multiple pad specifiers, you can only pad once.
Severity: 30 : Severe error
Explanation: The FORMAT expression was incorrect, and must be rewritten.
Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most likely an incorrect character used.

BIP3217: Error in parsing FORMAT expression <insert_1>, parsing failed at <insert_2> because of syntax error, could be an unmatched quote.
Severity: 30 : Severe error
Explanation: The FORMAT expression was incorrect, and must be rewritten.
Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most likely an incorrect character used.

BIP3218: Error in parsing FORMAT expression <insert_1>, parsing failed at <insert_2> because of illegal pad position.
Severity: 30 : Severe error
Explanation: The FORMAT expression was incorrect, and must be rewritten.
Response: Look at the reason given and the point at which it failed to determine what has gone wrong. It is most likely an incorrect character used.

BIP3219: (<insert_1>, <insert_2>) : End of ESQL file found whilst still inside a block comment.
Severity: 20 : Error
Explanation: There were <insert_3> open block comments when the end of the ESQL file was found. Please ensure that all open block comments are closed (with the */ block comment termination sequence) before the end of the ESQL file.
Response: Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.

BIP3220: (<insert_1>, <insert_2>) : End of ESQL file found whilst still inside an executable block comment.
Severity: 20 : Error
Explanation: There were <insert_3> open executable block comments when the end of the ESQL file was found. Please ensure that all open executable block comments are closed (with the >!*/ executable block comment termination sequence) before the end of the ESQL file.
Response: Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.

BIP3221: The integration node could not bind a LOB parameter of an external stored procedure because the data was too large. The size of the data was <insert_1>.
Severity: 20 : Error
Response: Where possible retrieve CLOB and BLOB fields through a standard SQL call rather than a stored procedure. If the problem persists contact your IBM Support Centre.

BIP3222: The value <insert_1> was of an unsuitable length <insert_2> for casting from a bit array to an integer.
Severity: 20 : Error
Explanation: The operand of a casting operation was of an unsuitable length for it to be cast to the target data type. To cast a bit array to an integer the length of the array must be 64.
Response: Check the logic of the message flow and redeploy.

BIP3223: The value <insert_1> was of an unsuitable length <insert_2> for casting from a bit array to a string.
Severity: 20 : Error
Explanation: The operand of a casting operation was of an unsuitable length for it to be cast to the target data type. To cast a bit array to a string the length of the array must be divisible by 8.
Response: Check the logic of the message flow and redeploy.

BIP3224: The value <insert_1> was of an unsuitable length <insert_2> for casting from a bit array to a byte array.
Severity: 20 : Error
Explanation: The operand of a casting operation was of an unsuitable length for it to be cast to the target data type. To cast a bit array to a byte array the length of the bit array must be divisible by 8.
Response: Check the logic of the message flow and redeploy.

BIP3226: (<insert_1>, <insert_2>) : Array index evaluated to <insert_3> but must evaluate to a positive, nonzero integer value.
Severity: 20 : Error
Explanation: The array index expression must evaluate to a positive, nonzero integer value.
Response: Correct the syntax of your ESQL expression in node <insert_1>, around line and column <insert_2>, then redeploy the message flow.

BIP3234: (<insert_1>, <insert_2>) : Truncated data was returned from the database when executing statement <insert_4> against datasource <insert_3>.
Severity: 20 : Error
Explanation: The database indicated that data returned from a stored procedure call has been truncated. This can occur when large CLOB or BLOB fields are being returned. This message flow has been set to Treat warnings as errors and an exception has been raised.
Response: Retrieve CLOB and BLOB fields by using a standard SQL call rather than a stored procedure. If the problem persists, contact your IBM Support Center.

BIP3235: (<insert_1>, <insert_2>) : Truncated data was returned from the database when executing statement <insert_4> against datasource <insert_3>.
Severity: 10 : Warning
Explanation: The database indicated that data returned from a stored procedure call has been truncated. This can occur when large CLOB or BLOB fields are being returned. This message flow is not set to Treat warnings as errors and will continue processing using the truncated data.
Response: Retrieve CLOB and BLOB fields by using a standard SQL call rather than a stored procedure. If the problem persists, contact your IBM Support Center.

BIP3236: ESQL function PROPAGATE has been invoked from Database Input Node <insert_1>.
Severity: 20 : Error
Explanation: The DatabaseInput node does not support the PROPAGATE function. This behavior might change in future releases.
Response: Remove the call to the PROPAGATE function.

BIP3237: Event with key <insert_1> is a duplicate and has been removed from the list of new events.
Severity: 0 : Information
Explanation: One of the events added to NewEvents was detected as a duplicate of an event that has already been dispatched, but not yet completed. The most likely reason is that the event has not yet been deleted from the database table, and so was returned by the query in the ReadEvents procedure.
Response: No action is required.

BIP3238: Event with key <insert_1> changed to ready state.
Severity: 0 : Information
Explanation: The ReadEvents procedure has returned event with Key <insert_1>. The event, which is not a duplicate, has been changed to the ready state and is waiting to be dispatched.
Response: No action is required.

BIP3239: Event changed to ready state.
Severity: 0 : Information
Explanation: An event has been returned by ReadEvents procedure. Because the event has no key, it has not been checked for duplication. It has been changed to the ready state, and is waiting to be dispatched.
Response: No action is required.

BIP3240: Event with key <insert_1> has been dispatched.
Severity: 0 : Information
Explanation: The Event with key <insert_1> was in the ready state. A message flow instance became available, and the event has been dispatched to that message flow instance.
Response: No action is required.

BIP3241: Event with key <insert_1> has been completed.
Severity: 0 : Information
Explanation: The event with key <insert_1> was dispatched to a message flow instance. That instance has completed its processing successfully, and so the event has changed to the complete state.
Response: No action is required.

BIP3242: Event with key <insert_1> has failed.
Severity: 0 : Information
Explanation: The event with key <insert_1> was dispatched to a message flow instance. Because of an error, the event has been changed to the ready state.
Response: This message is for information only. Review other messages to determine whether this event was successfully retried, or if the error was successfully handled.

BIP3243: DatabaseInput node caught an exception caught while executing ESQL routine <insert_1> in module <insert_2>.
Severity: 20 : Error
Explanation: ESQL routine <insert_1> is invoked as part of the DatabaseInput node's processing. During the execution of this routine in module <insert_2>, an error caused an exception to be thrown.
Response: Review following error messages and take appropriate action.

BIP3244: Failure count field of event structure has unexpected type <insert_1>.
Severity: 10 : Warning
Explanation: The FailureCount element in the Event structure is expected to be INTEGER type; a type of <insert_1> was detected.
Response: Ensure that the ESQL does not modify the Failure Count element.

BIP3245: Parameter <insert_1>, of routine <insert_2> in module <insert_3> has incorrect type <insert_4> <insert_5>5
Severity: 20 : Error
Explanation: The <insert_1> parameter of <insert_2> in <insert_3> should be an IN parameter of type REFERENCE. The parameter is <insert_4>, of type <insert_5>.
Response: Correct this by changing the CREATE PROCEDURE statement.

BIP3246: Routine <insert_1> in module <insert_2> has the wrong number of parameters - <insert_3>3
Severity: 20 : Error
Explanation: The ESQL routine is expected to have 1 IN parameter of type REFERENCE but <insert_2> parameters were detected.
Response: Correct this by changing the CREATE PROCEDURE statement.

BIP3247: ESQL Routine <insert_1> missing from module <insert_2>.
Severity: 20 : Error
Explanation: Module <insert_2> is a DATABASEEVENT module, and requires a CREATE PROCEDURE statement for the <insert_1> routine. This statement does not exist.
Response: Add the <insert_1> routine to the <insert_2> module.

BIP3248: The Java Method <insert_1> could not be loaded due to a linkage error. It depends on the class <insert_2> which could not be found in the deployed bar file or in the 'workpath/shared-classes/' directory.
Severity: 20 : Error
Explanation: The specified Java Method <insert_1> belongs to a class that could not be loaded because of a linkage error with a dependent class <insert_2>. Ensure that the dependent class, or a jar that contains the dependent class, is present in the deployed bar file or in the 'workpath/shared-classes/' directory.
Response: Examine and correct the SQL program.

BIP3249: The Java Method <insert_1> could not be loaded due to a linkage error. It depends on the class <insert_2> which could not be found by the specified configurable service classloader <insert_3>.
Severity: 20 : Error
Explanation: The specified Java Method <insert_1> belongs to a class that could not be loaded because of a linkage error with a dependent class <insert_2>. Ensure that the dependent class, or a jar that contains the dependent class, can be found by the specified configurable service classloader <insert_3>.
Response: Examine and correct the SQL program.

BIP3301: <insert_4> node <insert_1> in message flow <insert_2> is unable to process files in the input directory <insert_3>.
Severity: 20 : Error
Explanation: The <insert_4> node is unable to process files in its input directory. The files or the directory might be locked or unavailable as a result of file system permissions or security settings. Alternatively, the directory path might be specified incorrectly.
Response: Ensure that the properties on the node specify the correct directory path, and that the input directory and the 'mqsitransitin' subdirectory have the correct permissions and security settings to allow the integration node to read from and write to the directory. For more information, see the "FileInput node" section of the IBM Integration Bus online documentation.

BIP3302: File node <insert_1> in message flow <insert_2> is unable to process files in the 'mqsiarchive' directory <insert_3>.
Severity: 10 : Warning
Explanation: The FileInput node is unable to process files in the 'mqsiarchive' directory. The files or the directory may be locked or unavailable due to file system permissions or security settings.
Response: Check that the archive directory exists and is accessible by the integration node. See the IBM Integration Bus online documentation section "FileInput node" for more information.

BIP3303: File node <insert_1> in message flow <insert_2> is unable to process files in the 'mqsibackout' directory <insert_3>.
Severity: 20 : Error
Explanation: The FileInput node is unable to process files in the 'mqsibackout' directory. The files or the directory may be locked or invisible to the integration node due to file system permissions or security settings.
Response: Check that the directory exists and is accessible by the integration node. See the IBM Integration Bus online documentation section "FileInput node" for more information.

BIP3304: File node <insert_1> in message flow <insert_2> cannot move file <insert_3> to the 'mqsibackout' directory because there is already a file of that name.
Severity: 20 : Error
Explanation: The FileInput node is unable to move a file to the 'mqsibackout' directory; a file of the same name already exists in that directory.
Response: If your flow will process multiple files of the same name you can set the 'Retry' panel attribute of the node to avoid name clashes. See the IBM Integration Bus online documentation section "FileInput node" for more information.

BIP3305: File node <insert_1> has reached the maximum recursion limit of <insert_2> in directory <insert_3>.
Severity: 20 : Error
Explanation: The FileInput node is unable to recurse any deeper into the named directory.
Response: If your directory structure is deeper than the named limit, change the MQSI_FILENODES_MAX_DIRECTORY_DEPTH environment variable to set the limit to the required value.

BIP3306: FileInput node <insert_1> in message flow <insert_2> is unable to process file <insert_3>. The absolute path of file <insert_3> exceeds the system limit for some systems, which is <insert_4> for path length. The FileInput node is now blocked, and will not pickup further files until this file is removed.
Severity: 20 : Error
Explanation: The FileInput node is unable to pickup the file due to the absolute path of the file name exceeding system limits. The FileInput node is now blocked, and will not pickup further files until this file is removed.
Response: Reduce the length of the file name, or reduce the length of the absolute path, so that it is within acceptable limits.

BIP3307: File node <insert_1> in message flow <insert_2> cannot create file <insert_3> in directory <insert_4>; a file of that name already exists.
Severity: 20 : Error
Explanation: 'Create a new output file' is the 'Output file action' of the FileOutput node but a file of that name already exists in the output directory.
Response: Ensure that output files are not kept in the output directory, or choose another Output file action. See the IBM Integration Bus online documentation section "FileOutput node" for more information.

BIP3309: File node <insert_1> in message flow <insert_2> cannot write to the 'mqsiarchive' directory <insert_3>.
Severity: 10 : Warning
Explanation: The FileInput node is prevented by the file subsystem from writing to the 'mqsiarchive' directory.
Response: Check that the integration node has permission to create and write to files in the 'mqsiarchive' directory. See the IBM Integration Bus online documentation section "FileInput node" for more information.

BIP3310: <insert_5> node <insert_1> in message flow <insert_2> property name <insert_4> is supplied with an invalid value <insert_3>.
Severity: 20 : Error
Explanation: The <insert_5>node cannot interpret the property value.
Response: Check that the correct property value is set on the FileOutput node in your flow definition. See the IBM Integration Bus online documentation section "FileOutput node" for more information.

BIP3311: File node <insert_1> in message flow <insert_2>. Property <insert_3> is supplied a value <insert_4> which is out of range.
Severity: 20 : Error
Explanation: The FileOutput node was supplied a property value which is not in a valid range.
Response: Check the definition of the property of the FileOutput node, and supply a value which is in the valid range. See the IBM Integration Bus online documentation section "FileOutput node" for more information.

BIP3312: <insert_5> node <insert_1> in message flow <insert_2> has set the property <insert_3> to <insert_4>.
Severity: 0 : Information
Explanation: The <insert_5> node has set the property.
Response: No action is required.

BIP3313: File node <insert_1> in message flow <insert_2> has no value for the <insert_3> property.
Severity: 10 : Warning
Explanation: The FileOutput node property is not set. In order to execute correctly this value must be supplied in the local environment of the message received by the node.
Response: If this property is to be supplied in the Local Environment of each message processed there is no user action required. Otherwise specify a property value on the node and redeploy the flow. See the IBM Integration Bus online documentation section "FileOutput node" for more information.

BIP3314: File node <insert_1> in message flow <insert_2> cannot write to output directory <insert_3>.
Severity: 10 : Warning
Explanation: The FileOutput node cannot write to the output directory because the file system prevents suitable access, which should include the abilities to: read and write files; move, create and delete files; and create subdirectories with the same properties.
Response: Check that a suitable directory exists and that the file system permits the required processing.
See the IBM Integration Bus online documentation section "FileOutput node" for more information.

BIP3315: <insert_6> node <insert_1> in message flow <insert_2> cannot move file <insert_3> from directory <insert_4> to subdirectory <insert_5>.
Severity: 20 : Error
Explanation: The <insert_6> node attempted to move a file to a subdirectory but failed. The reason might be that there is a file with the same name in the subdirectory. Alternatively, the file system might be preventing the action; for example, the file might be locked.
Response: For FileInput nodes, ensure that the 'mqsiarchive', 'mqsitransitin', and 'mqsibackout' subdirectories are available and accessible. For FileOutput nodes, ensure that the 'mqsiarchive' and 'mqsifailure' subdirectories are available and accessible, and that the correct 'Output file action' property is set. File system permissions and security settings might be preventing the correct action of the node. For more information, see the "FileInput node" and "FileOutput node" sections of the IBM Integration Bus online documentation.

BIP3316: File node <insert_1> in message flow <insert_2> has no valid filename specified as property <insert_3>.
Severity: 10 : Warning
Explanation: The FileOutput node file name property is either not specified or its value is not a valid file name.
Response: If it is intended that each message has this property specified by the flow then there is no user action required. Otherwise ensure that the flow correctly sets the file name in the local environment prior to propagation to this FileOutput node, or set the node property to specify a valid filename. See the IBM Integration Bus online documentation section "FileOutput node" for more information.

BIP3317: File node <insert_1> in message flow <insert_2> created directory <insert_3>.
Severity: 0 : Information
Explanation: The file node created a subdirectory for its own processing.
Response: No user action is required.

BIP3318: File node <insert_1> in message flow <insert_2> failed to delete file <insert_3> in directory <insert_4>.
Severity: 20 : Error
Explanation: The file node was unable to delete a file before moving a file of the same name into the directory.
Response: Ensure that the file system is working normally and that the directories used by the file nodes have the file permissions and security settings for full integration node access. See the IBM Integration Bus online documentation sections "FileInput node" and "FileOutput node" for more information.

BIP3319: File node <insert_1> in message flow <insert_2> is moving file <insert_3> to directory <insert_4> with new name <insert_5>.
Severity: 0 : Information
Explanation: The file node is about to move a file with a modified name.
Response: No user action is necessary.

BIP3320: File node <insert_1> in message flow <insert_2> encountered an I/O exception <insert_3> writing to output file <insert_4>.
Severity: 20 : Error
Explanation: The FileOutput node encountered an exception from the file system while writing to a file.
Response: Ensure that the file system is available and operating normally. In particular check that there is sufficient free space in the file system to store the file. The exception description indicates the general nature of the error. See the IBM Integration Bus online documentation section "FileOutput node" for more information.

BIP3321: File node <insert_1> in message flow <insert_2> cannot delete the file <insert_3>.
Severity: 20 : Error
Explanation: The file node failed to delete a file during normal processing.
Response: Ensure that the file system permissions and security settings permit the integration node to delete this file. For FileInput nodes the file may be an input file which is to be deleted after successful (or unsuccessful) processing. For FileOutput nodes the file may be an existing output file which is to be replaced as part of processing a file of the same name. See the IBM Integration Bus online documentation sections "FileInput node" and "FileOutput node" for more information.

BIP3322: FileInput node <insert_1> in message flow <insert_2> cannot access the file <insert_4> with the correct access permissions. Exception description: <insert_3>.
Severity: 20 : Error
Explanation: The FileInput node failed to open the file. Either the file no longer exists, or the file cannot be opened with both read and write permissions. The file input node needs read permission to access the contents of the file. The node needs write permission to move, rename, or delete the file after processing the file contents.
Response: Ensure that the input directory and the file have the correct file permissions and security settings to permit the integration node to read from and write to the file. See the IBM Integration Bus online documentation sections "FileInput node" and "FileOutput node" for more information.

BIP3323: File node <insert_1> in message flow <insert_2> does not allow more than one wildcard character '*' in the file name <insert_3>.
Severity: 20 : Error
Explanation: The FileOutput node discovered more than one wildcard character in the file name specification. Only one is allowed.
Response: Check the specification of the file name in the message flow node. Ensure that only one wildcard character is used. See the IBM Integration Bus online documentation section "FileOutput node" for more information.

BIP3324: File node <insert_1> in message flow <insert_2> was unable to process the file <insert_3> because it was too large.
Severity: 20 : Error
Explanation: Using the "Whole File" Record detection method with a FileInput node file that is greater than 2Gb in size is not supported.
Response: Select a different Record detection type, or reduce the size of the input file, and retry the message. See the IBM Integration Bus online documentation section "FileInput node" for more information.

BIP3325: File node <insert_1> in message flow <insert_2> cannot use the directory <insert_3> for file name <insert_4>.
Severity: 20 : Error
Explanation: The file node cannot create the directory or cannot move a file into or out of the directory with that name.
Response: Ensure that the file and directory names are correctly specified in the message flow. The names may contain invalid characters or the directory may be ineligible for use, or the integration node may not have the authority to perform the action required. See the IBM Integration Bus online documentation sections "FileInput node" and "FileOutput node" for more information.

BIP3327: File node <insert_1> in message flow <insert_2> will delete file <insert_3> from directory <insert_4>.
Severity: 0 : Information
Explanation: The FileOutput node will delete a file from a directory because a new file of the same name is to be created there.
Response: No user action is required. See the IBM Integration Bus online documentation section "FileOutput node" for more information.

BIP3328: File node <insert_1> in message flow <insert_2> cannot create the directory path <insert_3>.
Severity: 20 : Error
Explanation: The FileOutput node attempted to create the missing directories in a given path but cannot complete the action.
Response: Check the specification of the directory path in the message flow node and ensure that the integration node has sufficient file system authority to create the required directories. See the IBM Integration Bus online documentation section "FileOutput node" for more information.

BIP3329: File node <insert_1> in message flow <insert_2> created missing directories in the output directory path <insert_3>.
Severity: 0 : Information
Explanation: The FileOutput node created some directories in the output path that did not already exist.
Response: No user action is necessary.

BIP3330: File node <insert_1> in message flow <insert_2> encountered an I/O exception <insert_3> while reading the file <insert_4>.
Severity: 20 : Error
Explanation: The FileInput node encountered an exception from the file system while reading a file.
Response: Ensure that the file system is available and operating normally and that the file being read has not been corrupted. Text in the exception description indicates the general nature of the error. See the IBM Integration Bus online documentation section "FileInput node" for more information.

BIP3331: <insert_4> node <insert_1> in message flow <insert_2> cannot continue executing. See the following message number <insert_3> for details of the problem preventing execution.
Severity: 30 : Severe error
Explanation: The <insert_4> node encountered an exception that prevented it from running successfully. This message will be issued repeatedly until the problem is solved. No further messages will be processed by this node until the message flow is restarted.
Response: To solve the problem:
- Stop the message flow and any other message flow that refers to the directory.
- Read the referenced message, which is likely to be shown soon after this message in the event log.
- Solve the problem that is identified in that message.
- Check that the files mentioned in that message are in the correct directory, and that there are no files with the same name in the 'mqsiarchive', 'mqsitransitin', or 'mqsibackout' directories. If necessary, delete, rename, or move files so that there is only one file with that name in the input directory.
- Restart the message flow.
For more information, see the "FileInput node" section of the IBM Integration Bus online documentation.

BIP3332: <insert_4> node <insert_1> in message flow <insert_2> cannot continue executing. See the following message number <insert_3> for details of the problem preventing execution.
Severity: 20 : Error
Explanation: The <insert_4> node encountered an exception which prevented it executing successfully.
When the problem is resolved, the flow will continue processing.
This message is issued repeatedly until the problem is resolved.
Response: To resolve the problem:
- Read the referenced message, which should closely follow this message in the event log.
- Resolve the problem identified in that message.
See the IBM Integration Bus online documentation section "FileInput node" for more information.

BIP3333: The File node <insert_1> in message flow <insert_2> cannot resolve the relative file path <insert_3>.
Severity: 20 : Error
Explanation: Relative file paths are resolved by using the absolute directory path in the 'MQSI_FILENODES_ROOT_DIRECTORY' environment variable.
This environment variable is not set correctly and cannot be used to resolve the path.
Response: Either ensure that the 'MQSI_FILENODES_ROOT_DIRECTORY' environment variable contains an absolute directory path and that the directory exists and can be accessed by the integration node, or change the node configuration to use absolute directory paths.
See the IBM Integration Bus online documentation topic "FileInput node" or "FileOutput node" for more information.

BIP3334: The <insert_4> node <insert_1> in message flow <insert_2> received a message on its 'Finish File' terminal, but there is no file named <insert_3> to be finished.
Severity: 20 : Error
Explanation: All output files are written to the 'mqsitransit' subdirectory until finished. When a file is finished it is moved to the output directory.
Response: Check the message flow processing to ensure that one or more messages are sent to the 'In' terminal of the FileOutput node before sending a message to the 'Finish File' terminal.
Check that the file name used is the same in all relevant flows.
See the IBM Integration Bus online documentation section "FileOutput node" for more information.

BIP3335: File node <insert_1> in message flow <insert_2> attempted to create whole file <insert_3>, but there is already an unfinished file by that name.
Severity: 20 : Error
Explanation: A new file is being created with the 'whole file' property of the FileOutput node but there is already a file of that name. This can be because another message flow has created this file but it has not yet been finished (it is still in the transit directory). The new file is not created and an exception is thrown.
Response: Output files are written to the 'mqsitransit' subdirectory of the output directory. If the file will not be finished (and moved to the output directory) by a subsequent flow then the file may need to be removed manually. Before handling files in the 'mqsitransit' directory all flows which refer to its parent directory should be stopped. See the IBM Integration Bus online documentation section "FileOutput node" for more information.

BIP3336: <insert_5> node <insert_1> in message flow <insert_2> is moving file <insert_3> to directory <insert_4>.
Severity: 0 : Information
Explanation: The <insert_5> node is about to move a file to a different directory.
Response: No user action is necessary.

BIP3337: The node <insert_1> in message flow <insert_2> is deleting file <insert_3> from directory <insert_4>.
Severity: 0 : Information
Explanation: The node is about to delete an existing file.
Response: No user action is necessary.

BIP3338: <insert_4> node <insert_1> in message flow <insert_2> could not open file <insert_3> because another process has locked it.
Severity: 20 : Error
Explanation: The <insert_4> node needed to open the file, but process other than the integration server containing the flow has a lock on the file. The flow is unable to continue processing the file, because it needs a read-write ("rw") lock.
Response: If other processes are likely to contend for access to the file, it may help to set the Retry options on the flow's input node to allow multiple attempts.
If no other processes should be accessing the file, use your operating system's facilities to identify the process holding the lock, and stop it or prevent it from running at the same time as the flow.

BIP3339: File node <insert_1> in message flow <insert_2> could not open file <insert_3> because another thread is using it.
Severity: 20 : Error
Explanation: The flow is unable to continue processing because the file is in use. The node waited for 1 second for the file to become free, but the file remained in use. The file node needed to open the file, but another thread in the integration server containing the flow is using the file. This other thread could be an additional instance of the flow, or a different flow that uses the same file.
Response: If no other flows in the same integration server are accessing the file, reducing or eliminating additional instances for this flow may prevent file contention, at the cost of reduced throughput.
If other flows or instances are likely to contend for access to the file, it may help to set the Retry options on the flow's input node to allow multiple attempts.

BIP3340: File node <insert_1> in message flow <insert_2> could not delete file <insert_3> because another thread is using it.
Severity: 20 : Error
Explanation: The flow is unable to continue processing because the file is in use. The node waited for 1 second for the file to become free, but the file remained in use. The file node needed to delete the file, but another thread in the integration server containing the flow is using the file. This other thread could be an additional instance of the flow, or a different flow that uses the same file.
Response: If no other flows in the same integration server are accessing the file, reducing or eliminating additional instances for this flow may prevent file contention, at the cost of reduced throughput.
If other flows or instances are likely to contend for access to the file, it may help to set the Retry options on the flow's input node to allow multiple attempts.

BIP3341: File node <insert_1> in message flow <insert_2> could not rename file <insert_3> because another thread is using it.
Severity: 20 : Error
Explanation: The flow is unable to continue processing because the file is in use. The node waited for 1 second for the file to become free, but the file remained in use. The file node needed to rename the file, but another thread in the integration server containing the flow is using the file. This other thread could be an additional instance of the flow, or a different flow that uses the same file.
Response: If no other flows in the same integration server are accessing the file, reducing or eliminating additional instances for this flow may prevent file contention, at the cost of reduced throughput.
If other flows or instances are likely to contend for access to the file, it may help to set the Retry options on the flow's input node to allow multiple attempts.

BIP3342: File node <insert_1> in message flow <insert_2>. The remote server definition <insert_3> contains an invalid timeoutSec property.
Severity: 10 : Warning
Explanation: The timeoutSec property is incorrectly defined on the FtpServer configurable service that was created with the mqsicreateconfigurableservice command. This value must be a decimal integer. FTP processing for this node has been disabled.
Response: Ensure that the FtpServer definition is correct, in particular that the timeoutSec property supplied is a valid integer. Use the mqsichangeproperties command to modify this FtpServer definition property. If you modify the FtpServer definition, restart the integration node to pick up the new values. The message flow FTP processing will be re-enabled when the message flow is restarted. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus Information Center.

BIP3343: File node <insert_1> in message flow <insert_2> could not determine the last modified date of file <insert_3>.
Severity: 10 : Warning
Explanation: The flow was unable to determine the last modified date of the remote file, and the configurable service associated with this node has the preserveFileDate setting enabled. FTP processing for this node has been disabled.
Response: Ensure that the date being returned by the remote server is a valid date. If preservation of the last modified time is not required, disable the preserveFileDate setting on the FtpServer configurable service. The message flow FTP processing will be re-enabled when the message flow is restarted. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center.

BIP3344: Message flow cannot access directory <insert_1>.
Severity: 0 : Information
Explanation: The message flow is unable to access the input directory due to insufficient authority. Files within this directory and any subdirectories cannot be processed.
Response: Ensure that the integration node user ID has sufficient authority to access the directory.

BIP3345: File node <insert_1> in message flow <insert_2> was unable to process the file <insert_3> because the size of the file exceeded the limit. The exception message was <insert_4>.
Severity: 20 : Error
Explanation: By default, the FileInput node can process records up to 100 MB in size.
Response: You can increase the maximum record size that can be processed by the FileInput node (up to 2 GB) by using the MQSI_FILENODES_MAXIMUM_RECORD_LENGTH environment variable. See the IBM Integration Bus documentation topic "FileInput node" for more information.

BIP3346: File node <insert_1> in message flow <insert_2> was unable to calculate the permissions required from the LocalEnvironment string <insert_3>. The cause of the failure was <insert_4>.
Severity: 20 : Error
Explanation: The permissions set in the LocalEnvironment.Destination.PosixPermissions field must be in the form of a 3-digit octal string.
Response: Amend the input value in the LocalEnvironment.Destination.PosixPermissions field so that it is a 3-digit octal string.

BIP3347: File node <insert_1> in message flow <insert_2> was unable to apply permissions to an output file. The cause of the failure was <insert_3>.
Severity: 20 : Error
Explanation: An I/O exception was encountered when permissions were being applied to an output file.
Response: Review the cause of the error and adjust filesystem settings as appropriate.

BIP3350: File node <insert_1> in message flow <insert_2> is closing file <insert_3>.
Severity: 0 : Information
Explanation: The FileInput node is closing the input file.
Response: No action is required.

BIP3351: File node <insert_1> in message flow <insert_2> is opening file <insert_3>.
Severity: 0 : Information
Explanation: The FileInput node opens the file to read input records.
Response: No action is required.

BIP3352: <insert_7> node <insert_1> in message flow <insert_2> is propagating record <insert_4> obtained from file <insert_3> at offset <insert_5> to terminal <insert_6>.
Severity: 0 : Information
Explanation: The FileInput node read a record from the file, and will propagate it to the named terminal.
Response: No action is required.

BIP3353: <insert_4> node <insert_1> in message flow <insert_2> is creating file <insert_3>.
Severity: 0 : Information
Explanation: The <insert_4> node is about to create a new file for writing output records.
Response: No action is required.

BIP3354: <insert_5> node <insert_1> in message flow <insert_2> is adding a record to file <insert_3> at offset <insert_4>.
Severity: 0 : Information
Explanation: The <insert_5> node is about to write a record into the file, starting from the given offset.
Response: No action is required.

BIP3355: <insert_4> node <insert_1> in message flow <insert_2> finished writing to file <insert_3>.
Severity: 0 : Information
Explanation: The <insert_4> node has finished writing records to the specified file. Finish processing begins.
Response: No action is required.

BIP3356: <insert_7> node <insert_1> in message flow <insert_2> has reached the end of file <insert_3> at record number <insert_4>, file length <insert_5> and is propagating record an empty BLOB record to terminal <insert_6>.
Severity: 0 : Information
Explanation: The FileInput node has processed all the records from the file. It will propagate an empty record to the named terminal to indicate end of data.
Response: No action is required.

BIP3357: FTEOutput node <insert_1> in message flow <insert_2> has sent a request from agent <insert_3> to agent <insert_4> on queue manager <insert_5> to transfer the local file <insert_6> to remote file path <insert_7> under the transfer id <insert_8>.
Severity: 0 : Information
Explanation: The FTEOutput node is sending a request to transfer the given file from the local file system to a remote file system.
Response: No user action required.

BIP3358: The WebSphere MQ File Transfer Edition agent <insert_1> in integration server <insert_2> on integration node <insert_3> has been started. It is registered with the coordinating queue manager <insert_4> and will use the configuration stored in <insert_5>.
Severity: 0 : Information
Explanation: This integration server is running WebSphere MQ File Transfer Edition.
Response: No user action required.

BIP3359: The WebSphere MQ File Transfer Edition agent <insert_1> in integration server <insert_2> on integration node <insert_3> has been stopped.
Severity: 0 : Information
Explanation: This integration server has stopped running the WebSphere MQ File Transfer Edition agent.
Response: No user action required.

BIP3360: A temporary WebSphere MQ File Transfer Edition agent called <insert_1> in integration server <insert_2> on integration node <insert_3> has been created.
Severity: 0 : Information
Explanation: A message flow containing FTE nodes has been deployed to an integration server which does not have an FTEAgent configurable service defined. A temporary agent has been created which uses the integration node's queue manager as the coordinating queue manager. The agent will be deleted when the last node using it is stopped or deleted. See the previous message for full details of the agent.
Response: To stop this message from being displayed in the future, create an FTEAgent configurable service with the name of the integration server. Creating the configurable service will also stop the agent from being deleted and de-registered from the coordinating queue manager when all message flows using it are stopped or deleted.

BIP3361: Failed to send a request to start an FTE transfer on agent <insert_1> due to an WebSphere MQ error. Queue name= <insert_2>; MQRC = <insert_3>.
Severity: 20 : Error
Explanation: There was a problem putting a request message to WebSphere MQ
Response: Review the WebSphere MQ error code and resolve the problem.

BIP3362: Failed to stop WebSphere MQ File Transfer Edition agent <insert_2>, because of <insert_1>. The exception message was <insert_3>. Check the FTE log for more information <insert_4>.
Severity: 20 : Error
Explanation: There was a problem stopping the agent.
Response: Review the exception message. You might have to restart the integration server to resolve the problem.

BIP3363: WebSphere MQ File Transfer Edition agent <insert_1> has been stopped, and is restarting. Check the FTE log at <insert_2> for more information.
Severity: 0 : Information
Explanation: Another application stopped the agent, which is restarting.
Response: A user or application within your WebSphere MQ File Transfer Edition network is sending control messages to the agent in IBM Integration Bus.

BIP3364: WebSphere MQ File Transfer Edition agent <insert_1> has stopped because of <insert_2>. The exception message was <insert_3>. Check the FTE log for more information <insert_4>.
Severity: 20 : Error
Explanation: The WebSphere MQ File Transfer Edition agent has stopped because of an exception.

BIP3365: The configuration directory <insert_2> for WebSphere MQ File Transfer Edition agent <insert_1> cannot be deleted
Severity: 10 : Warning
Explanation: The configuration directory for the agent cannot be deleted.
Response: Check the permissions of the configuration directory. If you think that you might need to recreate the agent later, delete the directory manually.

BIP3366: Failed to create queues that are needed by agent <insert_1>. To create the queues manually, run the runmqsc script <insert_3> on the integration node queue manager <insert_2>.
Severity: 20 : Error
Explanation: Some queues that are needed to initialize the agent do not exist. The queues cannot be created, perhaps because of a lack of authority to create queues from within the integration node integration server, or the runmqsc command not being available.
Response: Create the queues manually, either by running the above script on the integration node queue manager, or by using the MQ explorer tool.

BIP3367: Failed to create queues that are needed to set up agent <insert_1>, coordinating queue manager <insert_2>. To create the queues manually, run the runmqsc script <insert_3> on the integration node queue manager.
Severity: 20 : Error
Explanation: Some queues that are needed to initialize the agent do not exist. The queues cannot be created, perhaps because of a lack of authority to create queues from within the integration node integration server, or the runmqsc command not being available.
Response: Create the queues manually, either by running the above script on the integration node queue manager, or by using the MQ explorer tool.

BIP3368: FTEInput node <insert_1> in message flow <insert_2> has received a tranfers from agent <insert_3>. Details: Job name=<insert_4>; Transfer ID=<insert_5>; File path=<insert_6>; File name=<insert_7>.
Severity: 0 : Information
Explanation: The FTEInput node is about to process the transfer.
Response: No action is required.

BIP3369: <insert_4> node <insert_1> in message flow <insert_2> has finished processing a transfer for file <insert_3>. The transfer notification will be deleted, and the file will be left unchanged.
Severity: 0 : Information
Explanation: The FTEInput node has finished processing a transfer. The file will be left in the destination directory.
Response: No action is required.

BIP3370: File node <insert_1> in message flow <insert_2> has been configured with an invalid known hosts file <insert_3> for SFTP. The error is <insert_4>.
Severity: 20 : Error
Explanation: The File node has been configured with an invalid known hosts file.
Response: If the file does not exist, create it and restart the message flow. If the file is corrupted, stop the message flow, replace the file, then restart the message flow. The message flow will not attempt SFTP remote file transfer until this problem is resolved.

BIP3371: File node <insert_1> in message flow <insert_2> has connected to host <insert_3> using SFTP with Strict Host Key checking set to <insert_4>, and the host key has changed.
Severity: 20 : Error
Explanation: The File node has connected to an SFTP server and the host key has changed.
Response: Either the SFTP host key has changed, or an attempt has been made to observe or tamper with messages in transit. Verify whether the host key has changed and, if it has, follow these steps: Stop the message flow, and any other's that are using SFTP. If strict host key checking is set to 'no', remove the host's entry in the known hosts file. If strict host key checking is set to 'yes', correct the entry in the known hosts file. Restart the message flows. In the meantime, the message flow keeps trying to connect.

BIP3372: File node <insert_1> in message flow <insert_2> has connected to host <insert_3> using SFTP with Strict Host Key checking set to <insert_4>, and the host is not in the known hosts file <insert_5>.
Severity: 20 : Error
Explanation: The File node has connected to an SFTP host that is not in the known hosts file.
Response: Stop the message flow and add the host to the known hosts file, then restart the message flow.

BIP3373: File node <insert_1> in message flow <insert_2>. FTP server definition <insert_3> contains an invalid cipher property.
Severity: 10 : Warning
Explanation: The ciphers property is incorrectly specified on the FtpServer configurable service that was created with the 'mqsicreateconfigurableservice' command. Valid values are lists containing any of the following: blowfish-cbc, 3des-cbc, aes128-cbc, aes192-cbc, aes256-cbc. Remote file transfer processing for this node has been disabled.
Response: Ensure that the FtpServer definition is correct, and that the cipher property is valid. Use the 'mqsichangeproperties' command to alter a property of an FtpServer definition. If you adjust the FtpServer definition, restart the integration node to use the new values. The message flow FTP processing is enabled again when the message flow is restarted. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center.

BIP3374: File node <insert_1> in message flow <insert_2>. FTP server definition <insert_3> contains an invalid compression property.
Severity: 10 : Warning
Explanation: The Strict Known Hosts property is incorrectly specified on the FtpServer configurable service that was created with the 'mqsicreateconfigurableservice' command. Valid values are in the range 0 to 9. Remote file transfer processing for this node has been disabled.
Response: Ensure that the FtpServer definition is correct, and that the compression property supplied is valid. Use the 'mqsichangeproperties' command to alter a property of an FtpServer definition. If you adjust the FtpServer definition, restart the integration node to use the new values. The message flow remote file transfer processing is enabled again when the message flow is restarted. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center.

BIP3375: File node <insert_1> in message flow <insert_2> has been configured for SFTP with Strict Host Key checking set to 'yes', but a known hosts file has not been specified.
Severity: 20 : Error
Explanation: The File node has been configured for Strict Host Key checking but has not been configured with a known hosts file.
Response: Ensure that the FtpServer definition is correct, and that the Strict Known Hosts property and the known hosts file property are valid. Use the 'mqsichangeproperties' command to alter a property of an FtpServer definition. If you adjust the FtpServer definition, restart the integration node to use the new values. The message flow remote file transfer processing is enabled again when the message flow is restarted. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center.

BIP3376: File node <insert_1> in message flow <insert_2>. FTP server definition <insert_3> contains an invalid Strict Known Hosts property.
Severity: 10 : Warning
Explanation: The Strict Known Hosts property is incorrectly specified on the FtpServer configurable service that was created with the 'mqsicreateconfigurableservice' command. Valid values are 'yes' or 'no'. Remote file transfer processing for this node has been disabled.
Response: Ensure that the FtpServer definition is correct, and that the Strict Known Hosts property is valid. Use the 'mqsichangeproperties' command to alter a property of an FtpServer definition. If you adjust the FtpServer definition, restart the integration node to use the new values. The flow remote file transfer processing is enabled again when the message flow is restarted. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center.

BIP3377: File node <insert_1> in message flow <insert_2>. FTP server definition <insert_3> contains an invalid protocol property.
Severity: 10 : Warning
Explanation: The protocol property is incorrectly specified on the FtpServer configurable service that was created with the 'mqsicreateconfigurableservice' command. Valid values are 'FTP' or 'SFTP'. Remote file transfer processing for this node has been disabled.
Response: Ensure that the FtpServer definition is correct, and that the protocol property is valid. Use the 'mqsichangeproperties' command to alter a property of an FtpServer definition. If you adjust the FtpServer definition, restart the integration node to use the new values. The flow remote file transfer processing is enabled again when the message flow is restarted. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center.

BIP3378: File node <insert_1> in message flow <insert_2>. FTP server definition <insert_3> contains invalid credentials for SFTP. The error is <insert_4>.
Severity: 10 : Warning
Explanation: The SFTP credentials have been incorrectly specified on the FtpServer configurable service that was created with the 'mqsicreateconfigurableservice' command. You must specify either a security identity with a valid user and password, or a valid username, passphrase, and location of a security identity file.
Response: Ensure that the FtpServer definition is correct, and that the security identity and the ssh security identity file properties are valid. Use the 'mqsichangeproperties' command to alter a property of an FtpServer definition. If you adjust the FtpServer definition, restart the integration node to use the new values. The flow remote file transfer processing is enabled again when the flow is restarted. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center.

BIP3379: File node <insert_1> in message flow <insert_2>. FTP server definition <insert_3> contains an invalid mac property.
Severity: 10 : Warning
Explanation: The mac property is incorrectly specified on the FtpServer configurable service that was created with the 'mqsicreateconfigurableservice' command. Valid values are lists containing any of the following: hmac-md5, hmac-sha1, hmac-md5-96, hmac-sha1-96. Remote file transfer processing for this node has been disabled.
Response: Ensure that the FtpServer definition is correct, and that the mac property is valid. Use the 'mqsichangeproperties' command to alter a property of an FtpServer definition. If you adjust the FtpServer definition, restart the integration node to use the new values. The flow remote file transfer processing is enabled again when the message flow is restarted. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center.

BIP3380: File node <insert_1> in message flow <insert_2> could not connect to remote <insert_5> server <insert_3>. Reason: <insert_4>.'
Severity: 20 : Error
Explanation: The FileInput or FileOutput node failed to open a connection to a remote server. Possible reasons for this failure are that the server could not be contacted, the initial FTP protocol was not observed, or an error situation exists at the server. The reason text is from the detected connection failure.
Response: Ensure that:
- The server address is correct and is locally resolved to a valid IP address.
- The server port is correctly specified (the default port for FTP is 21, and for SFTP it is port 22).
- A firewall does not block access to the remote server.
If you adjust an FtpServer configurable service definition, restart the integration node to pick up the new settings. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center.

BIP3381: File node <insert_1> in message flow <insert_2> cannot log in to remote <insert_6> server <insert_3> with user name <insert_4>. Reason: <insert_5>.
Severity: 20 : Error
Explanation: The FileInput or FileOutput node failed to log in after connecting to a remote server. Possible reasons for this failure are that the user name and password were invalid or not known at the remote system, the SFTP or FTP protocol was not observed by the server, accounting information was required but not supplied in the FtpServer definition, or that the server was too busy to respond.
Response: Ensure that:
- The user name and password defined as the 'securityIdentity' with 'mqsisetdbparms' are correct.
- The 'account information' is specified on the 'acctInfo' property of the FtpServer definition only if it is required by the remote system.
- Local firewall settings do not block access to the remote server.
If you modify an FtpServer configurable service definition, restart the integration node to pick up the new settings. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center.

BIP3382: File node <insert_1> in message flow <insert_2> reached an invalid internal state <insert_4> while connecting to server <insert_3>.
Severity: 20 : Error
Explanation: The communication with the remote server is out of sequence.
Response: Contact your IBM Support Center.

BIP3383: File node <insert_1> in message flow <insert_2> failed with reason <insert_5> when transferring <insert_4> to or from a remote <insert_6> server <insert_3>.
Severity: 20 : Error
Explanation: The transfer of a file using FTP or SFTP failed. The failure description is a summary of the problem, which might include protocol errors by the remote server, socket I/O errors, and failures while writing the file locally or remotely during the transfer. The transfer of this file has been abandoned and the processing of the file has failed.
Response: Ensure that the socket connection is valid and stable. Also ensure that the local and remote file systems have enough space and that they have the required permissions for the transfer (including, when necessary, the deletion of a local or remote file). If a protocol error is indicated, ensure that the remote FTP Server conforms to standard FTP Server protocol standards. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center, or the "FileInput node" and "FileOutput node" topics.

BIP3384: File node <insert_1> in message flow <insert_2>. An unexpected reply has been received from <insert_5> server <insert_3>. The command and reply are: <insert_4>.
Severity: 20 : Error
Explanation: The transfer of a file using SFTP or FTP failed because the server gave an unexpected reply to a client command. The command and reply are given in the message. The file transfer has been abandoned.
Response: Ensure that the socket connection is valid and stable. Also ensure that the local and remote file systems have enough space and that they have the required permissions for the transfer (including, if necessary, the deletion of a local or remote file). If a protocol error is indicated, ensure that the remote FTP Server conforms to standard FTP Server protocol standards. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center.

BIP3385: File node <insert_1> in message flow <insert_2>. Unexpected I/O exception occurred in communication with FTP server <insert_3>. I/O exception text is <insert_4>.
Severity: 20 : Error
Explanation: The transfer of a file using FTP failed with an I/O exception. The transfer is abandoned.
Response: Ensure that the socket connection is valid and stable, and that the local and remote file systems have enough space and sufficient permissions for the transfer, including, when necessary, the deletion of a local or remote file. Examine the I/O exception text for further information. See the IBM Integration Bus online documentation sections "FileInput node" and "FileOutput node" for more information.

BIP3386: File node <insert_1> in message flow <insert_2>. The remote user identifier supplied as <insert_3> is invalid.
Severity: 10 : Warning
Explanation: The user identifier supplied by a securityIdentity is not valid. Either the user identifier is missing, or no securityIdentity definition exists, or the securityIdentity registry information could not be read due to a permissions problem. FTP processing for this node has been disabled.
Response: Ensure that the securityIdentity is correctly defined using the mqsisetdbparms command. If your integration node is running on z/OS, ensure that the BIPSDBP job is run with a userid that is in the same group as the integration node userid. If you modify this definition, restart the message flow to pick up the new values. The message flow FTP processing will be re-enabled automatically. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center.

BIP3387: File node <insert_1> in message flow <insert_2>. Remote server definition <insert_3> does not supply a server address.
Severity: 10 : Warning
Explanation: The server name is not defined on the FtpServer configurable service that was created with the mqsicreateconfigurableservice command. FTP processing for this node has been disabled.
Response: Ensure that the FtpServer definition is correct, in particular that the serverName property is supplied. Use the mqsicreateconfigurableservice command to define the correct properties. If you adjust the FtpServer definition, restart the integration node to pick up the new values. The message flow FTP processing will be re-enabled when the message flow is restarted. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center.

BIP3388: File node <insert_1> in message flow <insert_2>. The FTP server definition <insert_3> supplied an invalid connectionType property.
Severity: 10 : Warning
Explanation: The connectionType property on the FtpServer configurable service, which was created with the 'mqsicreateconfigurableservice' command, is not 'ACTIVE' or 'PASSIVE'. FTP processing for this node has been disabled.
Response: Ensure that the FtpServer configurable service definition is correct, particularly the connectionType property. Use the mqsichangeproperties command to alter the properties of the FtpServer service. If you modify the FtpServer definition, restart the integration node to pick up the new values. The message flow FTP processing will be re-enabled when the message flow is restarted. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center.

BIP3389: File node <insert_1> in message flow <insert_2>. The remote server definition <insert_3> contains an invalid scanDelay property.
Severity: 10 : Warning
Explanation: The scanDelay property is incorrectly defined on the FtpServer configurable service that was created with the mqsicreateconfigurableservice command. This value must be a decimal integer. FTP processing for this node has been disabled.
Response: Ensure that the FtpServer definition is correct, in particular that the scanDelay property supplied is a valid integer. Use the mqsichangeproperties command to modify this property of the FtpServer definition. If you modify the FtpServer definition, restart the integration node to pick up the new values. The message flow FTP processing will be re-enabled when the message flow is restarted. For more information, see the "FtpServer configurable service properties" topic in the IBM Integration Bus information center.

BIP3390: File node <insert_1> in message flow <insert_2>. FTP server definition <insert_3> contains an invalid transferMode property.
Severity: 10 : Warning
Explanation: The transferMode property is incorrectly specified on the FtpServer configurable service created with the 'mqsicreateconfigurableservice' command. Valid values are 'ASCII' or 'BINARY'. FTP processing for this node has been disabled.
Response: Ensure that the FtpServer definition is correct, in particular that the transferMode property supplied is valid. Use the 'mqsichangeproperties' command to alter a property of an FtpServer definition. If you adjust the FtpServer definition, restart the integration node to pick up the new values. The flow FTP processing will be re-enabled when the flow is restarted. See the IBM Integration Bus online documentation section "FtpServer configurable service properties" for more information.

BIP3391: File node <insert_1> in message flow <insert_2> has connected to host <insert_3> using <insert_4> as user <insert_5>.
Severity: 0 : Information
Explanation: The File node has connected to a remote server.
Response: No action is required.

BIP3392: File node <insert_1> in message flow <insert_2> has disconnected from host <insert_3> using <insert_4>.
Severity: 0 : Information
Explanation: The File node has disconnected from a remote server.
Response: No action is required.

BIP3393: File node <insert_1> in message flow <insert_2> is about to send file <insert_3> to host <insert_4> using <insert_5>.
Severity: 0 : Information
Explanation: The File node is about to send a file to a remote host.
Response: No action is required.

BIP3394: File node <insert_1> in message flow <insert_2> has sent file <insert_3> to host <insert_4> using <insert_5>.
Severity: 0 : Information
Explanation: The File node has sent a file to the remote server.
Response: No action is required.

BIP3395: File node <insert_1> in message flow <insert_2> is about to transfer file <insert_3> from host <insert_4> using <insert_5>.
Severity: 0 : Information
Explanation: The File node is about to transfer a file from a remote server.
Response: No action is required.

BIP3396: File node <insert_1> in message flow <insert_2> has transferred file <insert_3> from host <insert_4> using <insert_5>.
Severity: 0 : Information
Explanation: The File has transferred a file from a remote host.
Response: No action is required.

BIP3397: File node <insert_1> in message flow <insert_2> has deleted file <insert_3> from host <insert_4> using <insert_5>.
Severity: 0 : Information
Explanation: The File node has deleted a file from a remote host.
Response: No action is required.

BIP3398: <insert_4> node <insert_1> in message flow <insert_2> has finished processing a transfer for file <insert_3>. The transfer notification and the transferred file will be deleted.
Severity: 0 : Information
Explanation: The FTEInput node has finished processing a transfer. The file will be deleted from the destination directory.
Response: No action is required.

BIP3399: <insert_4> node <insert_1> in message flow <insert_2> has finished processing a transfer for file <insert_3>. The transfer notification will be deleted, and a timestamp will be appended to the file name.
Severity: 0 : Information
Explanation: The FTEInput node has finished processing a transfer. The file name will have a timestamp added to it.
Response: No action is required.

BIP3400: The creation of adapter component <insert_1> has failed.
Severity: 20 : Error
Response: Review previous messages to find out why the error occurred.

BIP3401: Adapter component <insert_1> is not valid. Reason: <insert_2>.
Severity: 20 : Error
Explanation: The deployment of the WebSphere adapter component has failed for an unexpected reason. The most likely cause is a mismatch between versions of the IBM Integration Toolkit and the runtime components.
Response: Check that compatible versions of the runtime components and the IBM Integration Toolkit are being used. If correct versions are being used then contact IBM Support.

BIP3402: The adapter component WSDL file contains the wrong namespace. The expected namespace is <insert_1>; the actual namespace is <insert_2>.
Severity: 20 : Error
Explanation: The deployment of the WebSphere adapter component has failed for an unexpected reason. The most likely cause is a mismatch between versions of the IBM Integration Toolkit and the runtime components.
Response: Check that compatible versions of the runtime components and IBM Integration Toolkit are being used. If correct versions are being used then contact IBM Support.

BIP3403: The adapter component <insert_1> cannot be deleted because it is in use by the following message flow nodes: <insert_2>.
Severity: 20 : Error
Explanation: You have attempted to delete an adapter component that is in use by one or more message flows.
Response: Review the message flows that are using the adapter and delete any that are no longer required. Then retry deleting the adapter component.

BIP3404: The adapter node <insert_1> in message flow <insert_2> has been configured to use adapter component <insert_3>, but that adapter component has not been deployed to this integration server.
Severity: 20 : Error
Explanation: You have deployed a message flow containing an adapter node but have not yet deployed the adapter component.
Response: Deploy a bar file containing the adapter component to the integration server.

BIP3405: The adapter input node <insert_1> in message flow <insert_2> has been configured to use adapter component <insert_3>, but the node <insert_4> in message flow <insert_5> is already using it.
Severity: 20 : Error
Explanation: An inbound adapter component can only be used by one WebSphere adapter input node at a time, within a particular integration server.
Response: Review the two message flows and decide which one should be deployed to the integration node.

BIP3406: The adapter component <insert_1> does not define properties for connecting to a system of type <insert_2>, so cannot be used by the adapter <insert_3> node called <insert_4> in message flow <insert_5>.
Severity: 20 : Error
Explanation: The wrong type of adapter is being used with this node. Input nodes must use inbound adapters and Request nodes must use outbound adapters.
Response: Change the node to use the correct type of adapter.

BIP3407: The adapter node <insert_1> in message flow <insert_2> has been configured to use adapter component <insert_3>, but the adapter component has not been deployed yet.
Severity: 20 : Error
Explanation: The adapter component required by the node has not been deployed yet. The message node cannot be deployed while a component it requires is missing.
Response: Deploy the adapter component required by the node.

BIP3408: The adapter component name <insert_1> is not valid.
Severity: 20 : Error
Response: Make sure the adapter name is valid.

BIP3409: An attempt to create the adapter component <insert_1> using the class <insert_2> failed. This class is not a supported type of adapter.
Severity: 20 : Error
Explanation: An attempt was made to create an adapter component using a class not installed on the integration node. The most likely cause is a mismatch between levels of the IBM Integration Toolkit and the runtime components.
Response: Check that compatible versions of the IBM Integration Toolkit and the runtime components are being used. If correct versions are being used then contact IBM Support.

BIP3410: The instantiation of the adapter class <insert_1> failed. Reason: <insert_2>.
Severity: 20 : Error
Explanation: An attempt was made to create an adapter component but it failed while being instantiated.
Response: Check that compatible versions of the IBM Integration Toolkit and the runtime components are being used. If correct versions are being used then contact IBM Support.

BIP3411: An attempt to set the property <insert_1> on adapter component <insert_2> failed because the property is not supported.
Severity: 20 : Error
Explanation: The current version of the adapter installed on the runtime does not support a property given in the adapter component configuration file. The most likely reason for this is a mismatch between the IBM Integration Toolkit and the runtime component levels.
Response: Check that compatible versions of the IBM Integration Toolkit and the runtime components are being used. If correct versions are being used then contact IBM Support.

BIP3412: An attempt to set the property <insert_1> to value <insert_2> failed.
Severity: 20 : Error
Explanation: The current version of the adapter installed on the runtime component had a problem setting a property given in the adapter component configuration file. The most likely reason for this is a mismatch between the IBM Integration Toolkit and the runtime component levels. See the following messages for details of the error.
Response: Check that compatible versions of the IBM Integration Toolkit and the runtime components are being used. If correct versions are being used then contact IBM Support.

BIP3413: An attempt to start adapter component <insert_1> failed. Reason: <insert_2>.
Severity: 20 : Error
Response: Try redeploying the adapter component. If this continues to fail then contact IBM Support.

BIP3414: An attempt to attach the message flow node <insert_1> in message flow <insert_2> to the adapter component <insert_3> failed. Reason: <insert_4>.
Severity: 20 : Error
Explanation: The message flow node failed to register with the adapter component to receive events. The node cannot function correctly until it has attached to the adapter component.
Response: Identify the adapter that is required by the node. Ensure that it is deployed to the correct integration server, and that the connection details on the .inadapter and the configurable service are correct. In addition, check the system log or Windows Event Viewer for further errors. If the problem persists, redeploy the message flow that contains the node and the adapter component that the node requires. The reason given in the error message might provide additional information about what caused the problem.

BIP3415: The deletion of the adapter component <insert_1> failed.
Severity: 20 : Error
Response: Review previous messages to find out why the error occurred.

BIP3416: A failure occurred during the process of committing or rolling back an adapter configuration.
Severity: 20 : Error
Explanation: A failure occurred when the adapter configuration was being committed (or backed out) from the integration node repository. The integration server is now in an undefined state where some components might be deployed and others are not.
Response: Remove all deployed components from the integration server and redeploy the required components. If the problem persists, contact IBM Support.

BIP3417: Adapter component <insert_1> does not contain any method bindings.
Severity: 20 : Error
Explanation: If the adapter component does not have any method bindings then it does not contain any useful configurations. All calls to the adapter component are made using the method bindings.
Response: Review the adapter component configuration and make sure it has at least one method binding.

BIP3418: The adapter component <insert_1> does not define properties for connecting to a system of type <insert_2>, so cannot be used by the <insert_3> adapter input node <insert_4> in message flow <insert_5>.
Severity: 20 : Error
Explanation: The wrong type of adapter is being used with this node. The node must be the right type of node for the adapter it is trying to use. For example, a SAPInputNode must use a SAP adapter.
Response: Change the node to use the correct type of adapter.

BIP3419: The changes to adapter component <insert_1> might not have been successfully picked up by node <insert_2> in message flow <insert_3>.
Severity: 20 : Error
Explanation: The adapter being used by the node is in an undetermined state.
Response: Redeploy the adapter configuration. If the error persists then restart the integration node. On restart the node will use the new configuration.

BIP3420: The message flow node <insert_1> in message flow <insert_2> failed to access the adapter component <insert_3>.
Severity: 20 : Error
Explanation: The node failed to access the adapter because the adapter was in the process of being re-created due to the deployment of its configuration.
Response: Redeploy the adapter configuration. If the error persists then restart the integration node.

BIP3421: The adapter component <insert_1> is not an outbound adapter so cannot be used by the adapter request node <insert_2> in message flow <insert_3>.
Severity: 20 : Error
Explanation: The wrong type of adapter is being used with this node. Input nodes must use inbound adapters and Request nodes must use outbound adapters.
Response: Change the node to use the correct type of adapter.

BIP3422: The adapter component <insert_1> does not define properties for connecting to a system of type <insert_2>, so cannot be used by the <insert_3> adapter request node <insert_4> in message flow <insert_5>.
Severity: 20 : Error
Explanation: The wrong type of adapter is being used with this node. The node must be the right type of node for the adapter it is trying to use. For example, a SAPInputNode must use an SAP adapter.
Response: Change the node to use the correct type of adapter.

BIP3423: WebSphere Adapters nodes failed to load due to exception <insert_1>
Severity: 20 : Error
Explanation: During the startup of an integration server an error was encountered while loading the java code for the WebSphere Adapters nodes. The details of the error are: <insert_1>
Response: This is an internal error. For more information contact IBM Support.

BIP3424: Message type <insert_1> is not present in message set <insert_2>. Message types contained in the message set are: <insert_3>.
Severity: 20 : Error
Explanation: While processing a message in a WebSphere Adapters node, an attempt was made to use a message type <insert_1> that is not present in the message set <insert_2> that is being used by that node. The ESD wizard should produce an adapter component and a message set that match in terms of the message types that are used as input and output to the adapter operations.
This error can happen if the message set or the adapters component have been modified since running the ESD, or if the node is configured to use a message set and an adapter component that were produced by two separate invocations of the ESD wizard.
Response: Review the message set and ensure that the message set does include all required types. Review the adapter component and ensure that it is configured to use the correct types. Ensure that the node is configured to use an adapter component and a message set that are compatible. Rerun the ESD wizard, if necessary, to generate a message set and compatible adapter component.

BIP3425: An error occurred while reading the input to a WebSphere Adapters node. Field <insert_1>=<insert_4> could not be converted from data type <insert_2> to <insert_3>.
Severity: 20 : Error
Explanation: Part of the input message to a WebSphere Adapters node was found to be the wrong data type. The <insert_1> field was data type <insert_2> but the adapter requires it to be <insert_3>.
The value of the field is <insert_4>.
An attempt was made to convert the data type of the field, but the conversion failed.
Response: See subsequent messages for details of the error.
Ensure that the node is configured to use a compatible message set and adapter component.
Ensure that the application that produces the input message creates elements with the correct data type.

BIP3426: Field <insert_1> was converted from data type <insert_2> to <insert_3> while reading the input to a WebSphere Adapters node.
Severity: 10 : Warning
Explanation: Part of the input message to a WebSphere Adapters node was found to be the wrong data type. The <insert_1> field was data type <insert_2> but the adapter requires it to be <insert_3>.
A successful attempt was made to convert the data type of the field.
Be aware that this conversion has a performance overhead.
This situation can arise if the message set or the adapters component have been modified since running the Adapter Connection wizard, or if the node is configured to use a message set and an adapter component that were produced by running the wizard on two separate occasions.
Response: Consider if it is more efficient to create the message with the correct data type.
Ensure that the node is configured to use a compatible message set and adapter component.

BIP3427: An attempt was made by a WebSphere Adapters node to read the value of field <insert_1>, but it contains null or is not set.
Severity: 20 : Error
Explanation: A WebSphere Adapters node attempted to read the value of field <insert_1> in the integration node tree, but that field is null.
Response: Inspect other messages for an indication of the cause of this error.

BIP3428: WebSphere Adapters node <insert_1> is configured to use a message set <insert_2> that is not deployed.
Severity: 20 : Error
Explanation: While processing a message in a WebSphere Adapters node <insert_1>, an attempt was made to use a message set <insert_2>, but that message set has not been deployed. The ESD wizard should produce an adapter component and a message set, and the WebSphere Adapters node should be configured to use the adapter component and the message set. All three artifacts (the adapter component, the message set, and a flow containing the node) must be deployed to the integration server for the application to be operational.
Response: Review the integration node configuration and ensure that the message set has been deployed. Ensure that the message flow node is configured to use the correct message set.

BIP3429: It was not possible to create a message set <insert_1> for use with WebSphere Adapters nodes.
Severity: 20 : Error
Explanation: Review the following exceptions for the cause.
Response: None

BIP3430: The creation of a resource based on message set <insert_1> failed.
Severity: 20 : Error
Explanation: Review the following exception messages to find out the cause.
Response: None

BIP3431: The deletion of a resource based on message set <insert_1> failed.
Severity: 20 : Error
Explanation: Review the following exception messages to find out the cause.
Response: None

BIP3432: The node <insert_1> in message flow <insert_2> has been configured with a secondary adapter mode of <insert_3>. The primary adapter (including the methods defined by it) is <insert_5>. The set of secondary adapters (including the methods defined by it) is <insert_4>.
Severity: 0 : Information
Explanation: You can configure WebSphere Adapters nodes to use secondary adapters for interface information. This message reports all adapters in the secondary set when the node is deployed or the integration node is restarted.
Response: None

BIP3433: The node <insert_1> in message flow <insert_2> has been configured to use all secondary adapters and <insert_3> has been added to this set.
Severity: 0 : Information
Explanation: You can configure WebSphere Adapters nodes to use secondary adapters for interface information. You can extend the set of secondary adapters at operational time by deploying a new adapter that matches the criteria of adapters in the secondary set. This message reports that a new adapter is deployed that matches this criteria and therefore becomes part of the set of secondary adapters for that node.
Response: None

BIP3434: The node <insert_1> in message flow <insert_2> has been configured to use secondary message sets and the following messages sets are being used as secondary message sets for that node <insert_3>.
Severity: 0 : Information
Explanation: You can configure WebSphere Adapters nodes to use secondary message sets to define message types for input or output to methods. This message reports all message sets that are used as secondary message sets when the node is deployed or the integration node is restarted.
Response: None

BIP3435: The node <insert_1> in message flow <insert_2> has been configured to use secondary message sets and <insert_3> has been added to the list of message sets used by that node.
Severity: 0 : Information
Explanation: You can configure WebSphere Adapters nodes to use secondary message sets to define message types for input or output to methods. You can extend the set of secondary message sets at operational time by deploying a new message set that matches the criteria of message sets in the secondary set. This message reports that a new message set is deployed that matches this criteria and therefore becomes part of the set of secondary message sets for that node.
Response: None

BIP3436: Message Type <insert_1> is found in message set <insert_2> by node <insert_3> in flow <insert_4>.
Severity: 0 : Information
Explanation: You can configure WebSphere Adapters nodes to access message types from secondary message sets if they are not present in the primary message set. In this case, the node <insert_3> has accessed the message type from message set <insert_2>.
Response: Refer to the node properties to determine whether this message set is the primary message set or secondary message set. If the message set is the one from which you expect to access this type, no further action is necessary. If you expect to access this type from another message set, remove the type from the message set, or rename the name or namespace of the type.

BIP3437: When merging primary message set <insert_1> with secondary message sets, message type <insert_2> in message set <insert_3> caused a clash with the same type that is already defined in <insert_4>, therefore it was ignored.
Severity: 10 : Warning
Explanation: You can configure WebSphere Adapters nodes to access message types from secondary message sets if they are not present in the primary message set. In this case, a primary message set <insert_1> has been configured to use <insert_3> as a secondary message set but it is ignoring the type <insert_2> in that message set because it has already been defined in another message set (<insert_4>).
Response: Review earlier messages (such as BIP3435) to determine in which message set this type was first defined. Regenerate the adapter and message set, and change the name or namespace of the type in one of the message sets. The type will not necessarily be taken from the same message set when the integration node is restarted unless the type is defined in the primary message set of the node, in which case the node will always use that definition.

BIP3438: Method name <insert_1> was found in adapter <insert_2> by node <insert_3> in flow <insert_4> with an input type of <insert_5> and output type of <insert_6>.
Severity: 0 : Information
Explanation: You can configure WebSphere Adapters nodes to use secondary adapters for interface information. Interface information includes a list of method names and, for each method, the message type that is used as input, and the message type that is used as output. This message reports details of a method definition that is used by a node and it indicates which adapter provides this definition.
Response: Refer to the node properties to determine whether this adapter is the primary adapter or a secondary adapter. If this adapter set is the one from which you expect to access this method, no further action is necessary. Review later messages (such as BIP3439) to identify the condition where method names clash between two adapters.

BIP3439: Adapter <insert_2> defines method name <insert_1> with an input type of <insert_5> and output type of <insert_6> but it is being ignored by node <insert_3> in flow <insert_4>
Severity: 10 : Warning
Explanation: You can configure WebSphere Adapters nodes to use secondary adapters for interface information. Interface information includes a list of method names and, for each method, the message type that is used as input, and the message type that is used as output. This message reports that a secondary adapter has defined a method that has the same name as a method that was defined by another secondary adapter.
Response: Review earlier messages (such as BIP3438) to determine which adapter first defined this method. To avoid duplication, regenerate one of the adapters and change the name of the method. The method will not necessarily be taken from the same adapter when the integration node restarts unless the method was defined in the primary adapter of the node, in which case, the node will always use that definition.

BIP3440: An event called <insert_1>, sent from adapter component <insert_2>, has been received in adapter input node <insert_3> in message flow <insert_4>.
Severity: 0 : Information

BIP3441: Unknown event <insert_1> was received by inbound adapter <insert_2>.
Severity: 20 : Error
Explanation: The inbound adapter component <insert_2> has received an event with native method name <insert_1>, but no method bindings have been configured for this event.

BIP3442: An exception occurred in adapter node <insert_1>, which is using adapter component <insert_2>..
Severity: 20 : Error
Explanation: This message flow node <insert_1> attempted to process a message and communicate with an EIS using an adapter component <insert_2>. An error occurred during this processing.
Response: See the following messages for details of the error.

BIP3443: Message flow <insert_1> failed to process an event <insert_3> from adapter component <insert_2>.
Severity: 20 : Error
Explanation: The message flow failed to process an event delivered by an adapter. The name of the event being processed at the time of the error is <insert_3>. Review other error message to work out what went wrong.
Response: None

BIP3444: Adapter node <insert_1> in message flow <insert_2> failed to process a message because its message body was <insert_3>, which is not supported.
Severity: 20 : Error
Explanation: The adapter node requires a valid message body to construct a request to an external system. The last child was a header parser and could not be used.
Response: Make sure a correct message body is constructed before the message is propagated to the adapter node <insert_1>.

BIP3445: Adapter request node <insert_1> in message flow <insert_2> failed to process a message because it does not contain any elements with a name of type <insert_3>.
Severity: 20 : Error
Explanation: The adapter request node received a message without any fields that it could use.
Response: Make sure a correct message body is constructed before the message is propagated to the adapter request node.

BIP3446: Adapter request node <insert_1> in message flow <insert_2> failed to process a message using the method binding <insert_3>. No data types were available for this method in the adapter component <insert_4>.
Severity: 20 : Error
Explanation: The adapter request node uses the method binding to construct a request based on the incoming message. The method binding could not be found in the adapter component that was configured for this node.
Response: Check that the adapter component contains the method binding given above.

BIP3447: A message using method binding <insert_1> has been received in adapter request node <insert_2> in message flow <insert_3>.
Severity: 0 : Information

BIP3448: Adapter request node <insert_1> in message flow <insert_2> failed to create a response using the method binding <insert_3>. No data types were available for this method in the adapter component <insert_4>.
Severity: 20 : Error
Explanation: The adapter request node uses the method binding to construct a response. The method binding could not be found in the adapter component that was configured for this node.
Response: Check that the adapter component contains the method binding shown in the message.

BIP3449: An unhandled internal adapter exception occurred.
Severity: 20 : Error
Explanation: An exception was thrown from an adapter that could not be handled by IBM Integration Bus.
Response: Check that compatible versions of the runtime components and the IBM Integration Toolkit are being used. If correct versions are being used then contact IBM Support.
See the following messages for details of the error.

BIP3450: An adapter error occurred during the processing of a message. The adapter error message is <insert_1>.
Severity: 20 : Error
Explanation: This error was detected by the adapter. The following message describes the diagnostic information that is provided by the adapter <insert_1>.
Response: Inspect the diagnostic information that is provided by the adapter. Further diagnostic information might be written to user trace. Inspect user trace for further information.

BIP3451: SAPReply node <insert_1> in message flow <insert_2> has been deployed to integration server <insert_3> that has no SAPInput node.
Severity: 10 : Warning
Explanation: A SAPReply node replies to a BAPI call that a SAPInput node receives. If no SAPInput node is present, a SAPReply node does not have a BAPI request to which to respond.
Response: The message flow will deploy but an error will be thrown if a message reaches the SAPReply node. Add a SAPInput node to a flow in this integration server and re-deploy.

BIP3452: SAPReply node <insert_1> in message flow <insert_2> has received the reply identifier <insert_3>, which does not correspond to any BAPI callout in the same integration server.
Severity: 20 : Error
Explanation: An SAPReply node has received a reply identifier that does not correspond to any BAPI callout in same integration server.
Response: This situation can occur if: -The reply identifier has become corrupted. -The BAPI callout to which the reply identifier refers has already been replied to. -The BAPI callout to which the reply identifier refers comes from an SAPInput node in a different integration server. -The reply identifier has expired.

BIP3453: Adapter input node <insert_1> failed to process an event called <insert_2> from adapter component <insert_3>.
Severity: 20 : Error
Explanation: Inbound adapter component <insert_3> has delivered an event called <insert_2> to the input node <insert_1>. An error occurred during the conversion of this event to an IBM Integration Bus message. See the following message to determine the cause of the error.
Response: None

BIP3454: SAPInput Node <insert_1> in message flow <insert_2> has received an RFC call to <insert_3> but is configured to accept calls to <insert_4> only.
Severity: 20 : Error
Explanation: The SAPInput node <insert_1> in message flow <insert_2> has received an RFC call from SAP; however, the interface being called does not correspond to any of the interfaces that were discovered by the Adapter Connection wizard while creating the .inadapter for that node. The interface that was called from SAP was <insert_3> and the list of interfaces expected by this node are <insert_4>.
Response: If the SAPInput node is intended to accept this RFC call, re-run the Adapter Connection wizard for its .inadapter and discover this BAPI. If this SAPInput node is not intended to accept this RFC call, possible causes of this error are: - The incorrect RFC Destination was specified by the calling SAP program. Contact your SAP administrator. - Two inadapters have been configured with the same RFCProgram ID. In this case, it is likely that each adapter will receive RFC calls that are relevant only for the other adapter. If this is the case, either consolidate the two adapters into one adapter and a SAPInput node that can accept all RFC calls, or use two separate program IDs.

BIP3455: Adapter input node <insert_1> in message flow <insert_2> encountered an error when trying to determine the operation name.
Severity: 20 : Error
Explanation: Adapter input node <insert_1> in message flow <insert_2> has received a call from the EIS; however, an error happened when trying to determine the operation name.
Response: None

BIP3456: SAPReply node <insert_1> in message flow <insert_2> has received a message without a reply identifier in the local environment. If the corresponding SAPInput node is in the same flow, this node is used for the reply; otherwise, an exception is issued.
Severity: 0 : Information
Explanation: The SAPReply node uses a reply identifier that is generated by an SAPInput node to determine where to send the reply. If this identifier does not exist, the SAPReply node can determine where to reply to by looking for an SAPInput node in the same flow. If no SAPInput nodes exist in the flow, an error is issued by the SAPReply node.
Response: If the SAPInput node is in the same message flow, no user action is required. If the SAPInput node is in a different flow, ensure that the reply identifier is copied to the local environment so that the SAPReply node knows where to reply to.

BIP3457: A synchronous call received by SAPInput node <insert_1> in message flow <insert_2> in integration server <insert_3> has timed out after <insert_4> seconds. The reply identifier is <insert_5>.
Severity: 20 : Error
Explanation: The SAPInput node has received a synchronous callout from SAP, which expects a reply. The input node has been configured with a timeout value and the reply has not been received by any SAPReply node in this integration server during that timeout period.
Response: Check for error BIP3452, which indicates that the reply was received but had the wrong reply identifier and could not be correlated with the outstanding callout. Check that the timeout property on the node has an appropriate value considering the period of time between the SAPInput node sending the message to be processed, and the SAPReply node receiving the reply message. If the request was sent to an external system for processing, check the system and the transport between that system and IBM Integration Bus for any indication of failures.

BIP3458: SAPReply node <insert_1> in message flow <insert_2> in integration server <insert_3> could not find a SAP reply identifier at location <insert_4>.
Severity: 20 : Error
Explanation: The SAPReply node did not find a reply identifier at the given location and no SAPInput node exists at the start of this message flow.
Response: Ensure that you have copied the SAP reply identifier to the location specified on the SAPReply node. If you have not changed this property, the default location is $LocalEnvironment/Destination/Adaper/Reply/ReplyIdentifier

BIP3459: The SAPReply node <insert_1> has found a reply identifier of <insert_2> at <insert_3>
Severity: 0 : Information
Explanation: An SAPReply node has found a reply identifier at the location specified by the SAP Reply Identifier property.
Response: No action required

BIP3460: The timeout property has been set on the SAPInput node <insert_1> in message flow <insert_2>. This node is using SAPAdapter <insert_3>, which has been configured to receive asynchronous calls only; therefore, the timeout property will be ignored.
Severity: 10 : Warning
Explanation: The timeout property of the SAPInput node is relevant for only synchronous calls from SAP. In the case of asynchronous calls, the timeout property will be ignored.
Response: If you intend to make synchronous calls from SAP, re-run the Adapter Connection wizard to generate a .inadapter component that is configured to receive synchronous calls.

BIP3461: The SAPAdapter <insert_1>, used by SAPInput node <insert_2> in message flow <insert_3> has received a synchronous call from SAP. This call increases the number of concurrent calls to <insert_4>, which is the highest number of concurrent calls since the trace was started.
Severity: 0 : Information
Explanation: The SAP adapter can receive synchronous calls from SAP. The numberOfListeners property of the SAP .inadapter component controls the maximum number of concurrent calls. The input parameters of these calls are sent to an SAPInput node for processing and the output parameters are received by an SAPReply node. The SAP call is blocked while it waits for the reply. The length of time between the SAPInput node propagating the message and the SAPReply node receiving the reply message can be affected by the additional instances properties. To avoid processing delays, tune the maximum number of listeners and the number of additional instances for the message flow that contains the SAPInput and SAPReply nodes.
Response: Use this information in conjunction with the advice offered in the help topic "Tuning the SAP adapter for scalability and performance".

BIP3462: The timeout property has been set on SAPInput node <insert_1> in message flow <insert_2>. This node is using SAPAdapter <insert_3>, which has been configured to receive asynchronous calls only; therefore, the timeout property will be ignored.
Severity: 10 : Warning
Explanation: The timeout property of the SAPInput node is relevant for only synchronous calls from SAP. In the case of asynchronous calls, the timeout property will be ignored.
Response: If you intend to make synchronous calls from SAP, re-run the Adapter Connection wizard to generate a .inadapter component that is configured to receive synchronous calls.

BIP3463: The SAPReply node <insert_1> in message flow <insert_2> has found a reply identifier of <insert_3> in location <insert_4> but can not cast it to a byte array. Its type is: <insert_5>
Severity: 20 : Error
Explanation: A SAPReply node has found a reply identifier at the location specified but it is not a byte array.
Response: Ensure that you have copied a valid reply identifier to the correct location.

BIP3464: The adapter component on node <insert_1> in message flow <insert_2> has not been specified.
Severity: 20 : Error
Explanation: The adapter component of node <insert_1> is required and must be configured for the node.
Response: Set the adapter component on the node in the IBM Integration Toolkit and redeploy the message flow.

BIP3466: SAP inbound adapter <insert_1> has been configured with a client definition file <insert_2> on z/OS.
Severity: 20 : Error
Explanation: The inadapter has been started when with a client definition file specified, but this is not supported on z/OS.
Response: Change the configurable service for the inadapter to not specify a client definition file. If you want to do SAP HA you must configure a shared queue group.

BIP3467: SAP inbound adapter <insert_1> has been configured with an invalid client definition file <insert_2>. The MQ Reason code is <insert_3>.
Severity: 20 : Error
Explanation: The inadapter has been started when with a client definition file specified, but is not a valid client definition file.
Response: Check that the client definition file exists. If it exists check that it hasn't been corrupted. If you think it has been corrupted, regenerate the file using WebSphere MQ.

BIP3468: SAP inbound adapter <insert_1> has been configured with an invalid path for its client definition file <insert_2>.
Severity: 20 : Error
Explanation: The inadapter has been started when with an invalid path for its client definition file.
Response: Correct the sharedTidStoreClientDefinitionFile property on the SAP Connection configurable service associated with the above adapter.

BIP3469: Required message set <insert_1> is not deployed in integration server <insert_2>.
Severity: 20 : Error
Explanation: A message set that is required to parse the incoming message has not been deployed.
Response: Deploy message set <insert_1> to integration server <insert_2>.

BIP3470: Adapter<insert_1> in integration server <insert_2> has been configured for high availability by using a shared Transation ID (TID) store on queue manager <insert_3>.
Severity: 0 : Information
Explanation: An adapter is using a shared TID store so that it can operate in a high availability setup.
Response: None

BIP3471: Adapter<insert_1> in integration server <insert_2> has not been configured to use a shared Transaction ID (TID) store.
Severity: 0 : Information
Explanation: An adapter is not using a shared TID store, therefore it cannot operate in a high availability setup.
Response: None

BIP3472: A DataObject parsing error occurred while parsing an SAP ALE IDoc.
Severity: 20 : Error
Explanation: The DataObject parser was called with a message format of SAP ALE IDoc, but an error has caused parsing to stop.
Response: Review further error messages to identify the cause of the errors.

BIP3473: Failed to send a request to start an FTE transfer on agent <insert_1> because the agent has reached its max queued transfers limit. Max Source Transfers=<insert_2>, Max Queued Transfers=<insert_3>.
Severity: 10 : Warning
Explanation: There was a problem starting an FTE transfer.
Response: Review FTE embedded agent properties or resend the backed out files when active transfers are complete.

BIP3480: Error starting a transaction for the adapter component <insert_1>.
Severity: 20 : Error
Explanation: There was a problem when the integration node attempted to begin a unit of work with an EIS resource that is connected to the adapter component. The request to start the unit of work might be unexpected.
Response: Check the EIS system log for errors. If no errors are found, stop and restart the integration server. If the problem persists, contact your IBM support center.

BIP3481: Error completing a transaction for the adapter component <insert_1>.
Severity: 20 : Error
Explanation: There was a problem when the integration node attempted to complete a unit of work with an EIS resource that is connected to the adapter component. The request to complete the unit of work might be unexpected.
Response: Check the EIS system log for errors. If no errors are found, stop and restart the integration server. If the problem persists, contact your IBM support center.

BIP3482: Error committing a transaction for the adapter component <insert_1>.
Severity: 20 : Error
Explanation: There was a problem when the integration node attempted to commit a unit of work with an EIS resource that is connected to the adapter component. The request to commit the unit of work might be unexpected.
Response: Check the EIS system log for errors. If no errors are found, stop and restart the integration server. If the problem persists, contact your IBM support center.

BIP3483: Error rolling back a transaction for the adapter component <insert_1>.
Severity: 20 : Error
Explanation: There was a problem when the integration node attempted to roll back a unit of work with an EIS resource that is connected to the adapter component. The request to roll back the unit of work might be unexpected.
Response: Check the EIS system log for errors. If no errors are found, stop and restart the integration node integration server. If the problem persists, contact your IBM support center.

BIP3484: <insert_1>
Severity: 20 : Error
Explanation: An embedded component has written the 'SEVERE' level diagnostic message included here.
Response: Refer to the appropriate message in the embedded component's documentation.

BIP3485: <insert_1>
Severity: 0 : Information
Explanation: An embedded component has written the 'CONFIG' level diagnostic message included here.
Response: Refer to the appropriate message in the embedded component's documentation.

BIP3486: <insert_1>
Severity: 0 : Information
Explanation: An embedded component has written the 'INFO' level diagnostic message included here.
Response: Refer to the appropriate message in the embedded component's documentation.

BIP3487: <insert_1>
Severity: 10 : Warning
Explanation: An embedded component has written the 'WARNING' level diagnostic message included here.
Response: Refer to the appropriate message in the embedded component's documentation.

BIP3491: A failure occurred during the process of accessing events stored in a persistent event store, while initializing an adapter.
Severity: 20 : Error
Explanation: The adapter failed to initialize its internal event store that it requires for assured delivery. The adapter cannot function correctly without this store.
Response: Make sure that the integration node is set up correctly and that there are no MQSeries or files system problems. If the problem persists, contact IBM support.

BIP3492: The adapter's persistent store failed to open a connection to queue manager: <insert_1>. Completion code: <insert_2>. Reason code: <insert_3>.
Severity: 20 : Error
Explanation: The adapter failed to initialize its internal event store, which it requires for assured delivery. The adapter uses MQSeries to store persistent events and it was unable to connect to the integration node's queue manager.
Response: Make sure that the integration node is set up correctly and that the MQSeries queue manager is running. If the problem persists, contact IBM support.

BIP3493: The adapter's persistent store failed to open a connection to queue: <insert_1>. Completion code: <insert_2>. Reason code: <insert_3>.
Severity: 20 : Error
Explanation: The adapter failed to initialize its internal event store, which it requires for assured delivery. The adapter uses MQSeries to store persistent events and it was unable to connect to a required queue on the queue manager.
Response: Make sure that the integration node is set up correctly and that the MQSeries queue manager is running. If the problem persists, contact IBM Support.

BIP3494: The adapter's persistent store failed to browse an event from queue: <insert_1>. Completion code: <insert_2>. Reason code: <insert_3>.
Severity: 20 : Error
Explanation: The adapter failed to browse an event from its internal event store.
Response: Check that the queue is available for browsing.

BIP3495: The adapter's persistent store failed to put an event to queue: <insert_1>. Completion code: <insert_2>. Reason code: <insert_3>.
Severity: 20 : Error
Explanation: The adapter failed to put an event to its internal event store.
Response: Check that the queue is available for putting.

BIP3496: The adapter's persistent store failed to get an event from queue: <insert_1>. Completion code: <insert_2>. Reason code: <insert_3>.
Severity: 20 : Error
Explanation: The adapter failed to get an event from its internal event store.
Response: Check that the queue is available for getting.

BIP3497: The adapter's persistent store failed to construct an event.
Severity: 20 : Error
Explanation: The adapter's persistent store contains corrupted data that cannot be processed.
Response: Contact IBM support.

BIP3498: The node <insert_1> in message flow <insert_2> is propagating username <insert_3> from the message to the EIS system..
Severity: 0 : Information
Explanation: The security profile for the <insert_1> WebSphere Adapters node is set to propagate the identity in the message to the EIS system. The identity in the message is determined to be <insert_3> and was taken from the IdentityMapped- or IdentitySource- elements in the Properties folder.
Response: None

BIP3501: The integration server <insert_1> on integration node <insert_2> has SAP adapter components deployed to it which are being used in at least one message flow.
Severity: 0 : Information
Explanation: This integration server is running WebSphere Adapter SAP nodes.
Response: None

BIP3502: The integration server <insert_1> on integration node <insert_2> has PeopleSoft adapter components deployed to it which are being used in at least one message flow.
Severity: 0 : Information
Explanation: This integration server is running WebSphere Adapter PeopleSoft nodes.
Response: None

BIP3503: The integration server <insert_1> on integration node <insert_2> has Siebel adapter components deployed to it which are being used in at least one message flow.
Severity: 0 : Information
Explanation: This integration server is running WebSphere Adapter Siebel nodes.
Response: None

BIP3504: The connection properties on adapter <insert_1> are being overridden by configurable service <insert_2> of type <insert_3>. The properties that are configured on the configurable service are <insert_4>.
Severity: 0 : Information
Explanation: You can create a configurable service to override the connection properties that are set on an adapter. In this case, the properties that were set on adapter <insert_1> have been overridden because configurable service with name <insert_2> and type <insert_3> has been created with the following properties <insert_4>.
Response: No action is required if these overriding values are correct. To change the values, use the mqsichangeproperties command and specify <insert_3> as ConfigurableService (-c parameter), and <insert_2> as ObjectName (-o parameter). To delete the configurable service and revert to using the properties that were deployed by the adapter, run the mqsideleteconfigurableservice command and specify <insert_3> as ConfigurableService (-c parameter), and <insert_2> as ObjectName (-o parameter).

BIP3505: The integration server <insert_1> on integration node <insert_2> has JDEdwards adapter components deployed to it which are being used in at least one message flow.
Severity: 0 : Information
Explanation: This integration server is running WebSphere Adapter JDEdwards nodes.
Response: None

BIP3506: The JD Edwards adapter components are using directory <insert_1> for their external software dependencies, but this directory does not contain a supported JDBC database driver.
Severity: 20 : Error
Explanation: The JD Edwards adapter components use the "JDEdwards" name-value pair from the EISProviders configurable service to determine the location of their external libraries. This location has been set to a valid location <insert_1>, but that location does not include JDBC driver libraries.
Response: Ensure that the JDBC drivers that are specified in the jdbj.ini configuration file are present in directory <insert_1>.

BIP3511: An attempt was made to access a record in the Enterprise Information System (EIS) which does not exist. Primary keys: <insert_3>. Error: <insert_4>.
Severity: 20 : Error
Explanation: The adapter received a request to access a record which does not exist in the EIS. This might be due to it being deleted by another process or due to the request message tree having incorrect data. Details: Error type = <insert_1>; Error code = <insert_2>; Primary keys: = <insert_3>; Error message = <insert_4>.
Response: Check that the record that is being be accessed exists in the EIS.

BIP3512: An attempt was made to create a record in the Enterprise Information System (EIS) which already exists. Primary keys: <insert_3>. Error: <insert_4>.
Severity: 20 : Error
Explanation: The adapter received a request to create a record which already exists in the EIS. This might be due to it being created by another process or due to the request message tree having incorrect data. Details: Error type = <insert_1>; Error code = <insert_2>; Primary keys: = <insert_3>; Error message = <insert_4>.
Response: Check that the record that is being be accessed does not already exist in the EIS.

BIP3513: An attempt was made to retrieve a record from the Enterprise Information System (EIS) but more than one record matches. Primary keys: <insert_3>. Number of matches: <insert_5>. Error: <insert_4>.
Severity: 20 : Error
Explanation: The adapter received a request to retrieve a record but more than one record exists in the EIS. This error is typically due to the primary keys not being set correctly on the request message. Details: Error type = <insert_1>; Error code = <insert_2>; Primary keys: = <insert_3>; Error message = <insert_4>.
Response: Check that only one entry exists that matches the required request. If more than one record is required to be retrieved, use retrieval instead.

BIP3514: An invalid request was sent to the adapter. Primary keys: <insert_3>. Error: <insert_4>.
Severity: 20 : Error
Explanation: The adapter received an invalid request. Details: Error type = <insert_1>; Error code = <insert_2>; Primary keys: = <insert_3>; Error message = <insert_4>.
Response: Check that the request is valid.

BIP3515: An attempt was made to retrieve <insert_5> records from Enterprise Information System (EIS) but this exceeds the maximum number of records allowed. Primary keys: <insert_3>. Error: <insert_4>.
Severity: 20 : Error
Explanation: The adapter received a request to retrieve too many records from an EIS. Details: Error type = <insert_1>; Error code = <insert_2>; Primary keys: = <insert_3>; Error message = <insert_4>.
Response: Modify the request so that it retrieves fewer records or increase the maximum number allowed.

BIP3516: A record has missing data that is required for making a request to the Enterprise Information System (EIS). Primary keys: <insert_3>. Error: <insert_4>.
Severity: 20 : Error
Explanation: The adapter received a request which has missing data. Details: Error type = <insert_1>; Error code = <insert_2>; Primary keys: = <insert_3>; Error message = <insert_4>.
Response: Check that all the required fields are set in the record.

BIP3517: A fault exception was received from the Enterprise Information System (EIS). Primary keys: <insert_3>. Error: <insert_4>.
Severity: 20 : Error
Explanation: The adapter received a fault exception from the EIS. Details: Error type = <insert_1>; Error code = <insert_2>; Primary keys: = <insert_3>; Error message = <insert_4>.
Response: Check the error code and error message for the cause of the fault.

BIP3521: The <insert_1> adapter was unable to load the Enterprise Information System (EIS) client libraries.
Severity: 20 : Error
Explanation: The <insert_1> adapter client libraries are not supplied with the IBM Integration Bus product and have to be obtained separately from the EIS provider. If the EIS client libraries have been installed and the integration node has been configured to use them then make sure they have the correct permissions and that configurable service points to the correct location. The missing resource which caused this problem was: <insert_2>.
Response: Obtain the missing client libraries from the EIS vendor and configure the integration node to have access to these files using mqsichangeproperties. If you are using SAP ensure you have JCO3 and not JCO2. Consult the documentation for the exact details (topic an09140).

BIP3522: The adapter was unable to locate a required Java library.
Severity: 20 : Error
Explanation: The most likely cause of this exception is that the client libraries for the Enterprise Information System (EIS) are missing from the system. The EIS client libraries are not supplied with the IBM Integration Bus product and have to be obtained separately from the EIS provider. If the EIS client libraries have been installed and the integration node has been configured to use them then make sure they have the correct permissions and that configurable service points to the correct location. The missing resource which caused this problem was: <insert_1>. If the problem persists then it might be due to an internal problem with the product.
Response: Obtain the missing client libraries from the EIS vendor and configure the integration node to have access to these files using mqsichangeproperties command. If you are using SAP then ensure you have JCO3 and not JCO2. Consult the documentation for the exact details (topic an09140). If this is not the cause of the missing class exception then contact IBM support.

BIP3523: The WebSphere MQ Classes for Java could not be found.
Severity: 20 : Error
Explanation: In order to function correctly, the SAP adapter requires the WebSphere MQ Java classes to be installed. The missing class is: <insert_1>
Response: Make sure the client libraries have been installed as part of WebSphere MQ and that the integration node environment has the CLASSPATH and library path set up correctly.

BIP3524: The adapter <insert_1> has been undeployed and is therefore no longer a secondary adapter for node <insert_2> in message flow <insert_3>.
Severity: 0 : Information
Explanation: You can configure WebSphere Adapters nodes to use secondary adapters for interface information. You can extend the set of secondary adapters at operational time by deploying a new adapter that matches the criteria of adapters in the secondary set. This message reports that the adapter, which was considered to be a secondary adapter for the named node, has been undeployed.
Response: None

BIP3525: The message set <insert_1> has been undeployed and is therefore no longer a secondary message set for node <insert_2> in message flow <insert_3>.
Severity: 0 : Information
Explanation: You can configure WebSphere Adapters nodes to use secondary message sets to define message types for input or output to methods. You can extend the set of secondary message sets at operational time by deploying a new message set that matches the criteria of message sets in the secondary set. This message reports that the message set, which was considered to be a secondary message set for the named node, has been undeployed.
Response: None

BIP3526: The method name has been configured incorrectly for adapter request node <insert_1>.
Severity: 20 : Error
Explanation: The method name property for the node <insert_1> has been set to a null value or an empty string and is therefore invalid.
Response: The method name can be configured by using a property on the node or in the local environment. If the name is set in both places, the local environment takes precedence over the node property.

BIP3527: The connection properties for Siebel adapters on this integration node are being overridden by a siebel.properties file <insert_1>.
Severity: 0 : Information
Explanation: You can create a siebel.properties file to override some of the Siebel adapter connection properties.
Response: No action is required if these overriding values are correct. To change the values, adjust the referenced siebel.properties file. To delete these overrides, remove the siebelPropertiesURL setting from the EISProviders configurable service.

BIP3528: The connection properties for Siebel adapters on this integration node are being overridden by a siebel.properties file <insert_1>, but this file cannot be accessed. The test for existence returned <insert_2>, the test for read permissions returned <insert_3>.
Severity: 20 : Error
Explanation: Check that the path specified to the siebel.properties file is correct and that the file permissions allow this file to be read.
Response: To allow the siebel.properties file to override the Siebel connection properties, correct these errors.

BIP3529: Integration node <insert_1> contains integration server <insert_2> that has tried to use the WebSphere Adapter <insert_3> configurable service <insert_4> but it does not exist.
Severity: 20 : Error
Explanation: The configurable service does not exist.
Response: Either ensure the integration server references a configurable service that exists or run mqsichangeproperties <insert_1> -e <insert_2> -o ComIbmSiebelManager -n <insert_3> -d to delete the reference and restart the integration server.

BIP3530: The SAP Adapter <insert_1> has made a connection to the SAP system <insert_2>.
Severity: 0 : Information
Explanation: The adapter has obtained a connection to an SAP system.
Response: None. This message is informational

BIP3531: The Adapter <insert_1> has lost a connection to the remote SAP system <insert_2>. The reason for the failure was <insert_3>. An attempt will be made to reconnect to the remote system.
Severity: 20 : Error
Explanation: A connection to a remote SAP system has been lost.
Response: The Adapter will automatically attempt to reconnect to the remote system at the interval specified in the "Connection Retry Interval" parameter in the Adapter options. Reconnection will be attempted up to the pre-configured maximum number of retries after which the flow must be restarted in order to reconnect to the SAP system. A further message will indicate if a retry attempt has succesfully reestablished a connection to the SAP system.

BIP3532: The Adapter <insert_1> has lost a connection to the remote SAP system <insert_2>. The reason for the failure was <insert_3>. The connection has been attempted the maximum number of times. No further attempt will be made to connect by this adapter until the flow is restarted.
Severity: 20 : Error
Explanation: A connection to a remote SAP system has been lost.
Response: The Adapter has exhausted the maximum permitted number of retries. The flow must be restarted in roder to attempt any further connection to the SAP System.

BIP3538: SSL handshaking failed immediately upon connect with reason <insert_1>.
Severity: 20 : Error
Explanation: SSL connections start with a handshake, and this failed immediately. Possible causes include: 1) The remote server is expecting a different SSL protocol. 2) No compatible SSL cipher suites could be negotiated. 3) The remote server is not SSL-enabled.
Response: Verify that the SSLProtocol and SSLCiphers settings are correct, and ensure that the remote host is expecting SSL connections.

BIP3539: Cannot use the specified SSL client key <insert_3> in the keystore (connecting to host <insert_1> port <insert_2>). The key is either not present, or not trusted by the server (accepted issuers: <insert_4>).
Severity: 20 : Error
Explanation: The TCP/IP SSL client configured for host <insert_1> port <insert_2> cannot create an SSL connection. Either the keystore does not contain the specified alias for the client authentication key, or the alias exists but is not issued by a Certificate Authority trusted by the server. The server trusts only issuers in the following list: <insert_4>4
Response: Ensure that a valid key with the specified alias is present in either the integration node keystore, or the integration server keystore if one has been configured.

BIP3540: Cannot find the specified SSL server key alias <insert_2> in the keystore (port <insert_1>).
Severity: 20 : Error
Explanation: The TCP/IP SSL server configured for port <insert_1> could not accept a client connection because the keystore does not contain the specified alias for the server key.
Response: Ensure that a valid key with the specified alias is present in either the integration node keystore, or the integration server keystore if one has been configured.

BIP3541: Cannot find a valid SSL server key in the keystore (port <insert_1>).
Severity: 20 : Error
Explanation: The TCP/IP SSL server configured for port <insert_1> could not accept a client connection, because the keystore does not contain a valid server key.
Response: Ensure that a valid key is present in either the integration node keystore, or the integration server keystore, if one has been configured.

BIP3542: The server on remote host <insert_1> port <insert_2> requested SSL client authentication, but no acceptable keys were found in the keystore (accepted issuers are <insert_3>)
Severity: 20 : Error
Explanation: The server on remote host <insert_1> port <insert_2> requested SSL client authentication, but the integration node could not supply an acceptable key in response. This might cause the SSL handshake to fail and the connection to be terminated. The list of issuers trusted by the remote server is (<insert_3>), and a key issued by one of these providers must be present in the keystore (either the integration node keystore, or an integration server keystore if one has been configured).
Response: Ensure that a valid key, trusted by the server, is present in the keystore.

BIP3543: The SSLClientAuth parameter <insert_2> specified for port <insert_1> is not valid, and the server cannot be started.
Severity: 20 : Error
Explanation: The value specified for SSLClientAuth is not valid. Valid values include: blank: no client authentication. "want" or "request": Ask for client authentication, but allow clients without certificates to connect. "need" or "require": Ask for client authentication, and do not allow clients without certificates to connect.
Response: Ensure that the value specified for SSLClientAuth is correct.

BIP3544: Failed to create an SSL connection to the remote host <insert_1> port <insert_2>. Reason <insert_3>.
Severity: 20 : Error
Explanation: The connection to the remote computer succeeded, but the SSL layer failed to create a secure session. This can happen for many reasons, including mismatches in SSL protocols, SSL cipher suites, and missing certificates in either keystore or truststore.
Response: Ensure that the specified SSL parameters are correct.

BIP3545: Failed to create an SSL session from a client on port <insert_1>. Reason <insert_2>.
Severity: 20 : Error
Explanation: The connection from the remote computer succeeded, but the SSL layer failed to create a secure session. This can happen for many reasons, including mismatches in SSL protocols, SSL cipher suites, and missing certificates in either keystore or truststore.
Response: Ensure that the specified SSL parameters are correct.

BIP3546: Failed to create a connection to the main address <insert_1> and to all addresses specified in the AlternativeAddresses <insert_2>.
Severity: 20 : Error
Explanation: An attempt was made to connect to all the specified addresses, but none of them succeeded. See the other error messages to find the reason for the last failure. Further attempts to retry the connections will be made at regular intervals, but this error message will be written only occasionally.
Response: Ensure that the specified addresses are correct and available.

BIP3547: Invalid AlternativeAddresses property <insert_1> specified in TCPIPClient configurable service <insert_2>.
Severity: 20 : Error
Explanation: The AlternativeAddresses property contains an incorrectly formatted string. The string must contain a list of TCP/IP addresses, each separated by a semi-colon. For example: host1:1111;host2:1113;host3;host4.
Response: Ensure that the AlternativeAddresses property contains a string in the correct format.

BIP3548: Invalid value for the length field <insert_1> found in field reference <insert_2>.
Severity: 20 : Error
Explanation: The length used to retrieve data from a TCP/IP input stream must be in the range 1 - 2147483648.
Response: Ensure that the field resolves to a value in the valid range.

BIP3549: Invalid timeout value <insert_1> found in location <insert_2>.
Severity: 20 : Error
Explanation: An invalid timeout value was found in the incoming message.
Response: Ensure that the message location contains a valid integer in the range 0 - 2147483648.

BIP3550: Invalid Connection Details property: <insert_1>.
Severity: 20 : Error
Explanation: An attempt was made to create a TCPIP node with a Connection Details property of <insert_1>. This name could not be found in configurable services and was not in the format <hostname>:<port>. The Connection Details property must be in the form of either a configurable service name (for example, TestClient) or a <hostname>:<port> string (for example, localhost:1452).
Response: Check that the Connection Details property is in the correct format (<hostname>:<port>) or that there is a configurable service with the specified name.

BIP3551: Maximum TCPIP recieve record length of <insert_1> exceeded for connection on hostname <insert_2>, port <insert_3>.
Severity: 20 : Error
Explanation: A TCPIP Node has attempted to read a message from a connection for hostname <insert_2>, port <insert_3> and that connection has been configured to have a maximum recieve record length of <insert_1>. The end of the record was not detected before the maximum record length was detected.
Response: Review the MaxReceiveRecordBytes setting on the configurable service to make sure it is large enough to accommodate all messages. Check the Records and Element panel on the node to ensure that the correct record detection mechanism is being applied for the messages on this connection. Ensure that the application which is sending the messages is demarking the records accordingly.

BIP3552: Timeout occurred on connection (Hostname <insert_1>, Port <insert_2>, Id <insert_3>) while waiting for all the data required to form a record. The timeout period was <insert_4> and the last data received was <insert_5>.
Severity: 20 : Error
Explanation: A TCP/IP node attempted to read a record from an input stream, but the time limit was reached before the full record was received. The timeout period is measured from when the first byte of data has arrived until the last byte of data has arrived. The timeout period is not reset until the full record has been received.
Response: Check that the whole record was sent in the specified length of time. Review the end application to make sure it is sending full records, and, if it is, increase the timeout period to a value that is sufficient to allow all the data to arrive.

BIP3553: Attempted to use a TCP/IP connection (Hostname = <insert_1>, Port = <insert_2>, Id = <insert_3>) that has already been closed by the remote side.
Severity: 20 : Error
Explanation: A TCP/IP node has attempted to send data to or read data from Hostname <insert_1>, Port <insert_2> through a TCP/IP connection (Id = <insert_3>). However, the connection has previously been closed by the remote application. When a connection has been closed, it cannot be used for sending or reading data and cannot be reopened.
Response: See further messages to determine which node was trying to use this connection. If the same connection needs to be reused, ensure that the connection is not closed by the end application until it is no longer required. If the same connection does not need to be reused, ensure that the node's ID Location property does not point to a field in the incoming message that might contain an ID value.

BIP3554: Reached end of stream before finding delimiter <insert_1>.
Severity: 20 : Error
Explanation: The end of the stream was found before the specified postfix delimiter.
Response: Check that the delimiter has been correctly added to the message and that the timeout value is large enough.

BIP3555: Failed to load TCPIPClient configurable service <insert_1> (which uses hostname <insert_2> and port <insert_3>) because the hostname and port are already in use by the configurable service <insert_4>.
Severity: 20 : Error
Explanation: Two configurable services have been defined on the same hostname and port. However, only one configurable service is allowed for each combination of hostname and port. The second configurable service (<insert_1>) has not been loaded and cannot be used by any node.
Response: Ensure that the two configurable services use different combinations of hostname and port, and then restart the integration node.

BIP3556: Failed to load TCPIPServer configurable service <insert_1> (which uses port <insert_2>) because the port is already in use by the configurable service <insert_3>.
Severity: 20 : Error
Explanation: Two configurable services have been defined on the same port, but only one is allowed on each port. The second configurable service (<insert_1>) has not been loaded and cannot be used by any node.
Response: Ensure that the two configurable services use different ports and then restart the integration node.

BIP3557: Message flow attempted to use <insert_1> configurable service <insert_2>, which exists but failed to be created when the integration node started.
Severity: 20 : Error
Explanation: Configurable services are created and validated when the integration node is started. The <insert_1> configurable service <insert_2> failed to be created. See the local system log on the computer that is running the integration node to find the reason for the failure.
Response: Ensure that all the configurable service attributes are valid and then restart the integration node.

BIP3558: The <insert_1> configurable service called <insert_2> has an invalid port number (<insert_3>).
Severity: 20 : Error
Explanation: The port number must be an integer in the range 1-65535.
Response: Specify a valid port number on the configurable service in the range 1-65535.

BIP3559: The TCP/IP server connection manager on port <insert_1> has reached the maximum number of connections allowed (<insert_2>).
Severity: 20 : Error
Explanation: The TCP/IP server has received more than the permitted number of requests for connections (<insert_2>) and has started to reject connections.
Response: Check why the maximum number of connections has been exceeded and, if necessary, increase the maximum number allowed.

BIP3560: A record has been received from Hostname <insert_1> on Port <insert_2> in TCPIP input node <insert_3> in message flow <insert_4>.
Severity: 0 : Information

BIP3561: The following connection was closed: ID <insert_1> on Hostname <insert_2> on Port <insert_3> in TCPIP input node <insert_4> in message flow <insert_5>.
Severity: 0 : Information

BIP3562: A record has been sent on Hostname <insert_1> on Port <insert_2> in TCPIP output node <insert_3> in message flow <insert_4>.
Severity: 0 : Information

BIP3563: A record has been received from Hostname <insert_1> on Port <insert_2> in TCPIP receive node <insert_3> in message flow <insert_4>.
Severity: 0 : Information

BIP3564: Failed to broadcast data: Hostname <insert_1> Port <insert_2>, on TCP/IP output node <insert_3> in message flow <insert_4>, to a socket with Id <insert_5>.
Severity: 0 : Information
Explanation: TCP/IP output node <insert_3> (in message flow <insert_4>) failed to broadcast data on Hostname <insert_1> on Port <insert_2>, to a socket with Id <insert_5>.
Response: Check previous error messages to identify the cause of the failure.

BIP3565: Failed to reach hostname <insert_1> within the timeout period of <insert_2> seconds.
Severity: 20 : Error
Explanation: The hostname could not be reached within the specified timeout period.
Response: Ensure that the address is valid, and that it is accessible from the computer that is trying to make the connection.

BIP3566: Failed to resolve hostname <insert_1>.
Severity: 20 : Error
Explanation: The hostname could not be resolved. A possible explanation is that the host is not accessible from the computer that is running the message flow.
Response: Ensure that the address is valid and that it is accessible from the computer that is trying to make the connection.

BIP3567: Timed out waiting to get a connection with available data, using Hostname <insert_1> and Port <insert_2>.
Severity: 20 : Error
Explanation: Valid open connections exist with the specified details, but no data arrived on any of the connections within the permitted length of time.
Response: Ensure that the end application is running correctly and sending data on this connection.

BIP3568: Timed out trying to write data to a TCP/IP socket. Connection Id: <insert_1>, Timeout time: <insert_2>.
Severity: 20 : Error
Explanation: A timeout occurred writing data to the connection. This typically occurs when the receiving application is processing data too slowly.
Response: Check that the end application is processing data and that the timeout is set to a sufficiently large value.

BIP3569: A node tried to release a connection on Hostname: <insert_1>, Port: <insert_2>, with Id: <insert_3> for output usage, but it has already been reserved by node <insert_4> until the end of the flow.
Severity: 20 : Error
Explanation: If a node reserves a connection for output usage until the end of the flow, no other node is allowed to release it.
Response: Make sure that the node is not trying to release the connection.

BIP3570: Field reference <insert_1> does not resolve to a valid integer value. Field type: <insert_2>, Field value: <insert_3>.
Severity: 20 : Error
Explanation: The field reference resolved to an existing element in the message but it was not a valid integer.
Response: Check that the field reference points to an integer field or a string field that contains a valid integer. No other type of object is supported for this property.

BIP3571: Invalid port number: <insert_1>.
Severity: 20 : Error
Explanation: An invalid port number was specified. The port number must be an integer in the range 1-65535.
Response: Specify a valid port number in the range 1-65535.

BIP3572: Unable to find a connection with the ID: <insert_1> on Hostname: <insert_2> and Port: <insert_3>.
Severity: 20 : Error
Explanation: There were no connections available with the specified details.
Response: Check that a connection with valid details was requested. Also, ensure that the connection was not closed before it was requested.

BIP3573: The connection cannot be used because it is being expired. Expiry time is <insert_1>.
Severity: 20 : Error
Explanation: The requested connection has expired due to inactivity and is in the process of being closed.
Response: Make sure that the expiry times that are set on the configurable service for the connection are long enough.

BIP3574: The following connection was opened: ID <insert_1> on Hostname <insert_2> on Port <insert_3> in TCPIP input node <insert_4> in message flow <insert_5>.
Severity: 0 : Information

BIP3575: Invalid value <insert_1> for node attribute. Valid values are: <insert_2>.
Severity: 20 : Error
Explanation: The value specified for the node attribute is not valid. A possible cause is that the versions of the Toolkit and Runtime are incompatible.
Response: Check that the versions of the Runtime and Toolkit are compatible.

BIP3576: Invalid value <insert_1> for timeout attribute.
Severity: 20 : Error
Explanation: Timeout values must be integers equal to or greater than zero.
Response: Check that the timeout attribute has a valid integer value.

BIP3577: Invalid value for <insert_1> configurable service <insert_2> MaximumConnection property. Value: <insert_3>.
Severity: 20 : Error
Explanation: The MaximumConnection property limits the number of connections that can be created. It must be a valid integer greater than or equal to 1. It must be set to no less than 1 so that it is always possible to create at least one connection.
Response: Check that the value is set to an integer greater than or equal to 1.

BIP3578: Invalid value for <insert_1> configurable service <insert_2> ExpireConnectionSec. Value: <insert_3>.
Severity: 20 : Error
Explanation: The ExpireConnectionSec property must be a valid integer greater than or equal to -1. A value of -1 signals that connections are never expired. No other negative value is supported.
Response: Ensure that the value is set to an integer greater than or equal to -1.

BIP3579: Invalid value for <insert_1> configurable service <insert_2> property name: <insert_3>, Value: <insert_4>.
Severity: 20 : Error
Explanation: The specified value is not an integer.
Response: Check that the value is set to an integer.

BIP3580: Invalid value for <insert_1> configurable service <insert_2> SO_RCVBUF Value: <insert_3>.
Severity: 20 : Error
Explanation: The SO_RCVBUF property must be a valid integer greater than or equal to zero. A value of zero signals that the operating system default is used.
Response: Check that the value is set to an integer greater than or equal to zero.

BIP3581: Invalid value for <insert_1> configurable service <insert_2> SO_SNDBUF Value: <insert_3>.
Severity: 20 : Error
Explanation: The SO_SNDBUF property must be a valid integer greater than or equal to zero. A value of zero signals that the operating system default is used.
Response: Check that the value is set to an integer greater than or equal to zero.

BIP3582: Invalid value for <insert_1> configurable service <insert_2> SO_LINGER_TIMEOUT_SEC Value: <insert_3>.
Severity: 20 : Error
Explanation: The SO_LINGER_TIMEOUT_SEC property must be a valid integer greater than or equal to -1. A value of -1 signals that the operating system default is used.
Response: Check that the value is set to an integer greater than or equal to -1.

BIP3583: Invalid value for <insert_1> configurable service <insert_2> TrafficClass Value: <insert_3>.
Severity: 20 : Error
Explanation: The TrafficClass property must be a valid integer greater than or equal to -1. A value of -1 signals that the operating system default is used.
Response: Check that the value is set to an integer greater than or equal to -1.

BIP3584: Invalid value for <insert_1> configurable service <insert_2> MinimumConnections Value: <insert_3> (MaximumConnections value: <insert_4>).
Severity: 20 : Error
Explanation: The MinimumConnections property must be a valid integer greater than or equal to zero. The value must also be less than or equal to the value of the MaximumConnections property.
Response: Check that the value is set to a valid integer.

BIP3585: Failed to create required connections in connection manager using connection details <insert_1>.
Severity: 20 : Error
Explanation: See the previous exceptions messages for the cause of this error.
Response: Fix the problem detailed in previous error messages.

BIP3586: Failed to create a client connection using hostname: <insert_1>, port: <insert_2>. Reason: <insert_3>.
Severity: 20 : Error
Explanation: The connection to the remote computer failed.
Response: Check that the connection details are correct and the remote system is listening on the correct port.

BIP3587: No connections are available on Hostname <insert_1>, Port <insert_2>.
Severity: 20 : Error
Explanation: No connections are available for the specified port and hostname. This situation can occur because the maximum number of connections has been reached and they are all in use, or because the server is either unavailable or is failing to accept connections within the required time.
Response: Ensure that the server application is running and accepting connections, and that the maximum connections limit has not been reached.

BIP3588: Attempted to use a TCP/IP connection (Hostname = <insert_1>, Port = <insert_2>, Id = <insert_3>) that has already been closed by node <insert_4>.
Severity: 20 : Error
Explanation: A TCP/IP node has attempted to send data to or read data from Hostname <insert_1>, Port <insert_2> through a TCP/IP connection (Id = <insert_3>). However, the connection has previously been closed by node <insert_4>. When a connection has been closed, it cannot be used for sending or reading data and cannot be reopened.
Response: See further messages to determine which node was trying to use this connection. If the same connection needs to be reused, ensure that the connection is not closed by any node until it is no longer required. If the same connection does not need to be reused, ensure that the node's ID Location property does not point to a field in the incoming message that might contain an ID value.

BIP3589: TCP/IP connection <insert_1> closed by node <insert_2>.
Severity: 0 : Information
Explanation: A TCP/IP node <insert_2> has completed its operation and has been configured to close the connection. The connection used by the node has ID <insert_1> and it has now been closed.
Response: No action required. This information might be useful if you see errors when other nodes try to use the connection with this ID.

BIP3590: TCP/IP connection <insert_1> closed.
Severity: 0 : Information
Explanation: A TCP/IP connection (ID = <insert_1>) has remained unused for a specified period of time and has been closed.
Response: No further action. This message might be useful if you see errors later when other nodes try to use the connection with this ID.

BIP3591: Attempted to send data to a TCP/IP connection (Hostname = <insert_1>, Port = <insert_2>, ID = <insert_3>) that has already been closed.
Severity: 20 : Error
Explanation: A TCP/IP node has attempted to send data to Hostname <insert_1>, Port <insert_2> through a TCP/IP connection (ID = <insert_3>). However, the connection has previously been closed either because the network link was broken or because the remote application closed the connection. When a connection has been closed, it cannot be used for sending data and it cannot be reopened.
Response: See further messages to determine which node was trying to use this connection. Investigate the cause of the connection closure, which might be a network fault or an intentional closure by the remote application.

BIP3592: Attempted to read from a TCP/IP input stream (Hostname <insert_1>, Port <insert_2>, connectionId <insert_3>), which has already been closed by node <insert_4>.
Severity: 20 : Error
Explanation: A TCP/IP node has attempted to read data from Hostname <insert_1>, Port <insert_2> through a TCP/IP connection (ID <insert_3>). However, the input stream has previously been closed (by node <insert_4>). When a connection's input stream has been closed, it cannot be used for reading data and it cannot be reopened.
Response: See further messages to determine which node was trying to use this connection. It is likely that the "idLocation" property of the current node is set to a field in the incoming message that identifies a connection whose input stream has previously been closed. If it is not important which connection you use (and therefore you do not need to use this particular connection), change this property or remove the field from the message. As a result the node will find any connection whose input stream is not closed and that has data waiting to be read. Alternatively, if you do need to use this particular connection, reconfigure the first node to prevent it from closing the stream.

BIP3593: Attempted to write to a TCP/IP output stream (Hostname <insert_1>, Port <insert_2>, connectionId <insert_3>) which has already been closed by node <insert_4>.
Severity: 20 : Error
Explanation: A TCP/IP node has attempted to send data to Hostname <insert_1>, Port <insert_2>, through a TCP/IP connection (ID <insert_3>). However, the output stream has previously been closed (by node <insert_4>). When a connection's output stream has been closed, it cannot be used for sending data and it cannot be reopened.
Response: See further messages to determine which node was trying to use this connection. It is likely that the "idLocation" property of the current node is set to a field in the incoming message that identifies a connection whose output stream was previously closed. If it is not important which connection you use (and therefore you do not need to use this particular connection), change this property or remove the field from the message. As a result the node will find any connection whose output stream is not closed. Alternatively, if you do need to use this particular connection, reconfigure the first node to prevent it from closing the stream.

BIP3594: Failed to bind to server port: <insert_1>. Reason: <insert_2>.
Severity: 20 : Error
Explanation: An attempt was made to listen on a server socket for client connections, but failed. The most likely cause of the failure is another server application listening on the same port.
Response: Ensure that there are no other server applications using this port, including other integration servers running message flows that are listening on the same port. Only one integration server can run a server listening on a specific port. Also ensure that the port is a valid one to use on the computer running the integration node.

BIP3595: The connection with the ID: <insert_1> on Hostname: <insert_2> and Port: <insert_3> exists but the node timed out waiting for data to arrive on the connection.
Severity: 20 : Error
Explanation: There was a connection available with the specified details but no data arrived within the permitted length of time.
Response: Ensure that the end application is running correctly and sending data on this connection.

BIP3596: Failed accessing socket. Reason: <insert_1>.
Severity: 20 : Error
Explanation: An error occurred when attempting to access the TCP/IP socket.
Response: Check that the socket is being used correctly and that the end application is not closing the connection unexpectedly.

BIP3597: Timed out waiting to aquire all available connections for broadcasting data (Connection details <insert_1>).
Severity: 20 : Error
Explanation: The node timed out waiting for all available connections for broadcasting data to. A possible cause is another thread (or node) broadcasting on the same connection.
Response: Check whether other nodes are broadcasting on the same port at the same time. If they are, ensure that the timeout is set to a large enough value.

BIP3598: Failed to find delimiter <insert_1> in input stream.
Severity: 20 : Error
Explanation: An exception occurred while trying to find delimiter <insert_1> in the input stream.
Response: Check previous exceptions for the reason why the parsing of the stream failed before the delimiter was found.

BIP3599: A node tried to release a connection on Hostname: <insert_1>, Port: <insert_2>, with Id: <insert_3> for input usage, but it has already been reserved by node <insert_4> until the end of the flow.
Severity: 20 : Error
Explanation: If a node reserves a connection for input usage until the end of the flow, no other node is allowed to release it.
Response: Make sure that the node is not trying to release the connection.

BIP3601: Operation mismatch. The SOAP payload <insert_1> corresponds to operation <insert_2> in WSDL binding <insert_3>, but the operation was previously specified as <insert_4>.
Severity: 20 : Error
Explanation: The first child of the SOAP body matches a specific WSDL operation. This operation is different from the operation specified by a Content-Type (action), SOAPAction or WS-Addressing Action header.
Response: Correct any SOAPAction or WS-Addressing Action header to match the operation identified by the SOAP payload.

BIP3602: The Web service payload <insert_1> does not match an operation described by WSDL binding <insert_2> in file <insert_3>.
Severity: 20 : Error
Explanation: The first child of the SOAP Body does not correspond to any of the operations defined in the specified WSDL definition.
Response: Check that the correct WSDL definition was deployed.

BIP3603: The SOAP logical tree is missing the required <insert_1> element.
Severity: 20 : Error
Explanation: A required element is missing from the tree.
Response: Check that the SOAP logical tree was correctly constructed.

BIP3604: The SOAP <insert_1> element in the bitstream is missing or has an invalid namespace.
Severity: 20 : Error
Explanation: The SOAP Envelope in the bitstream is invalid.
Response: Check that the bitstream supplied contains a valid SOAP Envelope.

BIP3605: The SOAP logical tree cannot be serialized.
Severity: 20 : Error
Explanation: There is a problem with the SOAP logical tree format.
Response: Review further error messages for an indication to the cause of the error. Check that the SOAP logical supplied is correctly formatted.

BIP3606: The bitstream is not an XML serialization of a SOAP logical tree.
Severity: 20 : Error
Explanation: When the SOAP parser is not invoked from a SOAP node, it expects the bitstream to be the serialized XML representation of the SOAP domain tree as generated by the asbitstream function. This representation of the SOAP tree is provided for internal integration node use in aggregation scenarios.
Response: Check the bitstream being parsed and either ensure it is a valid XML representation of the SOAP domain tree, or parse it in a different domain.

BIP3607: The bitstream includes one or more incorrectly serialized Attachments.
Severity: 20 : Error
Explanation: When the SOAP parser is not invoked from a SOAP node, it expects the bitstream to be the serialized XML representation of the SOAP domain tree as generated by the asbitstream function. The data for each child of Attachment must be held as base64 encoded character data in an element called Data.
Response: Check the bitstream being parsed and either ensure it is a valid XML representation of the SOAP domain tree, or parse it in a different domain.

BIP3608: The logical tree includes an incorrectly formatted Attachment <insert_1>.
Severity: 20 : Error
Explanation: The SOAP logical tree has an Attachment subtree with children corresponding to any attachments in a SOAP with Attachments document. Each child is named after the Content-Id of the corresponding MIME part and must have a child called BLOB as generated by the BLOB parser with a child also called BLOB and containing valid bytearray data.
Response: Check the logical tree and ensure the Attachment data is represented correctly.

BIP3609: The SOAP payload <insert_1> corresponds to operation <insert_2> in WSDL binding <insert_3>. This operation has an operation type <insert_4> which is not supported in this context.
Severity: 20 : Error
Explanation: The WSDL operation type solicit-response is not supported for SOAPInput nodes.
Response: Correct the WSDL operation definition, or use a different WSDL operation.

BIP3610: Invalid response message. The SOAP payload <insert_1> corresponds to the <insert_2> message of operation <insert_3> in WSDL binding <insert_4>. An 'out' or 'fault' message was expected.
Severity: 20 : Error
Explanation: A response to a previous Web service request was expected.
Response: Check that the WSDL operation was correctly defined and that the Web service provider correctly implements the service.

BIP3611: Operation mismatch. The SOAP payload <insert_1> corresponds to operation <insert_2> in WSDL binding <insert_3>, but the specified operation for this SOAP request was <insert_4>.
Severity: 20 : Error
Explanation: When a SOAP Request or SOAP Async Request node is configured, a particular WSDL operation is specified. The message being processed does not correspond to this operation.
Response: Correct the message flow so that the SOAP message matches the specified WSDL operation.

BIP3612: SOAP version mismatch. The WSDL binding <insert_1> specifies SOAP binding <insert_2>, but the message being processed uses SOAP binding <insert_3>.
Severity: 20 : Error
Explanation: The WSDL binding specifies the expected SOAP version, as defined by the namespace of the SOAP Envelope.
Response: Correct the WSDL binding definition or the SOAP messages so that they use the same SOAP version (SOAP 1.1 or 1.2).

BIP3613: SOAP version mismatch. The Content-Type specifies SOAP binding <insert_1>, but the message being processed uses SOAP binding <insert_2>.
Severity: 20 : Error
Explanation: The transport level Content-Type implies the expected SOAP version, as defined by the namespace of the SOAP Envelope.
Response: Correct the transport level information or the messages being sent, so that the Content-Type value correctly matches the SOAP version used by the message (SOAP 1.1 or 1.2).

BIP3614: A SOAP logical tree cannot be built from the message bitstream.
Severity: 20 : Error
Explanation: The bitstream is not a valid Web service message.
Response: Review further error messages for an indication to the cause of the error.

BIP3615: SOAP message written with <insert_1> MTOM elements.
Severity: 0 : Information

BIP3616: Node <insert_1> sending a <insert_2> fault message to the originating client.
Severity: 0 : Information
Explanation: See subsequent messages for success or failure messages relating to this reply, and for any transport-specific messages.
Response: No action required.

BIP3617: Node <insert_1> sending SOAP message to the JMS Destination <insert_2>, using the Request URI <insert_3>.
Severity: 0 : Information
Explanation: The integration node is sending data via JMS to a server provider at Destination <insert_2>. See subsequent messages for success or failure messages relating to this request.
Response: No action required.

BIP3618: Node <insert_1> received data over JMS from ReplyToDestination <insert_2>.
Severity: 0 : Information
Explanation: The integration node has received data over JMS from the server provider via the ReplyToDestination <insert_2>.
Response: No action required.

BIP3619: An exception occurred while getting data from the JMS Destination <insert_1>.
Severity: 20 : Error
Explanation: The integration node was trying to get data from the JMS Destination <insert_1> when it encountered an exception.
Response: See the following messages for information pertaining to this error.

BIP3620: An error occurred whilst sending a SOAP request over the JMS transport to the JMS Destination <insert_1>. The JMS RequestURI was <insert_2> and a response was expected from the JMS ReplyToDestination <insert_3>. The JMS provider used was <insert_6>, the target service (if any) was <insert_7> and the Initial Context Factory was <insert_9>. The timeout duration for the request was <insert_4> seconds, the request message expiry was <insert_5> and the request message was a JMS <insert_8> message.
Severity: 20 : Error
Explanation: Ensure that the data is valid.
Response: See the following messages for information pertaining to this error.

BIP3621: An error occurred whilst receiving a SOAP response message from the JMS ReplyToDestination <insert_3>. The outbound JMS RequestURI was <insert_2> and the request was made to the JMS Destination <insert_1>. The JMS provider used was <insert_6>, the target service (if any) was <insert_7> and the Initial Context Factory was <insert_9>. The timeout duration for the request was <insert_4> seconds, the request message expiry was <insert_5> and the request message was a JMS <insert_8> message.
Severity: 20 : Error
Explanation: Ensure that the data is valid.
Response: See the following messages for information pertaining to this error.

BIP3622: A SOAP request received an empty response body, when a SOAP payload was expected.
Severity: 20 : Error
Explanation: It is an error for a service provider to return an empty payload when a SOAP response is required by the Message Exchange Pattern (MEP) of the selected operation.
Response: Determine why the service provider is returning an empty response body.

BIP3623: A SOAP request received a response message which did not have a SOAPJMS_contentType message property.
Severity: 20 : Error
Explanation: It is an error for a service provider to return a payload without a SOAPJMS_contentType message property.
Response: Determine why the service provider is not returning a SOAPJMS_contentType message property.

BIP3624: A SOAP request timed out waiting for a JMS response from the ReplyToDestination <insert_1>. The timeout duration was <insert_2> seconds.
Severity: 20 : Error
Explanation: The service provider did not response within the time allowed.
Response: Determine why the service provider is not returning response or increase the timeout duration.

BIP3625: A SOAP request encountered an error sending a JMS request to the Destination <insert_1>.
Severity: 20 : Error
Explanation: An exception occurred whilst sending a SOAP request over JMS to the Destination <insert_1>.
Response: See the following messages for information pertaining to this error, and ensure the JMS configuration is correct.

BIP3626: A SOAP request encountered an error receiving a JMS response from the ReplyToDestination <insert_1>.
Severity: 20 : Error
Explanation: An exception occurred whilst trying to receive a SOAP response from the ReplyToDestination <insert_1>.
Response: See the following messages for information pertaining to this error, and ensure the JMS configuration is correct.

BIP3627: An attempt was made to send more than one SOAP reply, but a reply has already been made.
Severity: 20 : Error
Explanation: Only one reply can be sent for a SOAP message and a reply has already been made.
Response: Examine the message flow and correct the error.

BIP3628: An attempt was made to send a SOAP reply, but a previous attempt to do so failed with an exception. Therefore, only a SOAPFault can be returned for this message.
Severity: 20 : Error
Explanation: Once a reply has been attempted and failed, only a SOAPFault can be returned.
Response: Examine the message flow and correct the error.

BIP3629: An attempt was made to send a JMS Text message with attachments (MTOM or SwA) using a charset other than 'utf-8'. The charset given was <insert_1>.
Severity: 20 : Error
Explanation: JMS Text messages with attachments can only be sent in 'utf-8'.
Response: Examine the message flow and correct the error.

BIP3630: The integration node has received an HTTP message on port <insert_1> with URL path <insert_2>.
Severity: 0 : Information
Explanation: The integration node is listening on port <insert_1> and has received a message sent by a client using URL path <insert_2>. This message will be sent on to either a SOAP Input Node or a SOAP Asynchronous Response Node.
Response: No action required.

BIP3631: The integration node has received an HTTPS message on port <insert_1> with URL path <insert_2>.
Severity: 0 : Information
Explanation: The integration node is listening on port <insert_1> and has received a message sent by a client using URL path <insert_2>. This message will be sent on to either a SOAP Input Node or a SOAP Asynchronous Response Node.
Response: No action required.

BIP3632: Maximum client wait time <insert_3> reached; the integration node has sent a fault message back to a client using port <insert_1> and URL path <insert_2>.
Severity: 10 : Warning
Explanation: A flow has taken too long to process a message received on port <insert_1> and URL path <insert_2>, and the integration node has sent a fault message back to the originating client.
Response: Increase the speed of the flow, or increase the maximum client wait time for the nodes using this URL.

BIP3633: Node <insert_1> sending HTTP data to URL <insert_4> at host <insert_2> (port <insert_3>).
Severity: 0 : Information
Explanation: The integration node is sending data via HTTP to a remote server at host <insert_2> (port <insert_3>) using URL <insert_4>. See subsequent messages for success or failure messages relating to this request.
Response: No action required.

BIP3634: Node <insert_1> received HTTP data from host <insert_2> with status code of <insert_3>.
Severity: 0 : Information
Explanation: The integration node has received data via HTTP from a remote server at host <insert_2> with an HTTP status code of <insert_3>. Status codes beginning with a 2 indicate success; others imply errors in either client or server.
Response: No action required.

BIP3635: An attribute conflict was detected between two HTTP Input Nodes. The URL selector <insert_1> has the same hash value as a different URL selector specified on another deployed node. A unique hash has been generated to allow the message flow to operate correctly, but if you are using the HTTP proxy servlet (or IE01 SupportPac) in a clustering scenario then unexpected behavior is possible.
Severity: 10 : Warning
Explanation: The HTTP proxy servlet (and IE01 SupportPac) allows a single HTTP listener to forward requests to the same message flow deployed on multiple integration nodes, using the URL selector to derive an internal correlation identifier. If different instances of the message flow on different integration nodes have a different correlation identifier then the requests may not be routed correctly.
Response: No action is needed unless the integration node is in a clustered environment using the HTTP proxy servlet or IE01 SupportPac. In that case only, modify the URL selector on the HTTP Input node, redploy the configuration and check that this warning is no longer generated.

BIP3636: Node <insert_1> has compressed a message body from <insert_2> bytes to <insert_3> bytes using <insert_4>.
Severity: 0 : Information
Explanation: The node has compressed a message body.
Response: No action required.

BIP3637: Node <insert_1> has decompressed a message body from <insert_2> bytes to <insert_3> bytes using <insert_4>.
Severity: 0 : Information
Explanation: The node has decompressed a message body.
Response: No action required.

BIP3638: An exception occurred while backing out the message to the JMS backout Destination <insert_1>. The exception was <insert_2>. An attempt will now be made to send a SOAP Fault back to the originating client.
Severity: 30 : Severe error
Explanation: The integration node was trying to send the inbound message to the JMS Destination <insert_1> when it encountered the exception.
Response: Try to resolve the cause of the exception.

BIP3639: The input message was backed out to the JMS backout Destination <insert_1>. An attempt will now be made to send a SOAP Fault back to the originating client.
Severity: 0 : Information
Explanation: The integration node has sent the inbound message to the JMS backout Destination <insert_1>.
Response: No user action required.

BIP3640: An error occurred while processing a SOAP response from the JMS ReplyToDestination <insert_3>. The outbound JMS RequestURI was <insert_2> and the request was sent to the JMS Destination <insert_1>. The JMS provider used was <insert_6>, the target service (if any) was <insert_7> and the Initial Context Factory was <insert_9>. The timeout duration for the request was <insert_4> seconds, the request message expiry was <insert_5> and the request message was a JMS <insert_8> message. The amount of data received (if any) was <insert_10> bytes.
Severity: 20 : Error
Explanation: Ensure that the data is valid.
Response: See the following messages for information pertaining to this error.

BIP3641: An error occurred while processing a SOAP JMS request.
Severity: 30 : Severe error
Explanation: Ensure that the data is valid.
Response: See the following messages for information pertaining to this error.

BIP3642: An attempt was made to send a JMS Reply, but no Destination was specified. Either the inbound message did not specify a JMSReplyTo queue or an attempt to override the Destination in the LocalEnvironment evaluated to NULL.
Severity: 30 : Severe error
Explanation: Make sure that a Destination is provided. This can be the JMSReplyTo queue in the inbound message or specified in the LocalEnvironment.
Response: Please correct the flow or the inbound client and try again.

BIP3643: An attempt was made to send a JMS Request but no Destination was specified.
Severity: 30 : Severe error
Explanation: Make sure that a Destination is provided. This can be specified on the SOAPRequest or SOAPAsyncRequest node or in the LocalEnvironment.
Response: Please correct the flow and try again.

BIP3644: An attempt was made to deploy two HTTPAsyncRequest, RESTAsyncRequest, or SOAPAsyncRequest nodes with the same unique identifier <insert_1> to the same integration server
Severity: 30 : Severe error
Explanation: You cannot deploy two HTTPAsyncRequest, RESTAsyncRequest, or SOAPAsyncRequest nodes with the same unique identifier to the same integration server.
Response: Correct this error and redeploy the flow.

BIP3645: An attempt was made to deploy a SOAPAsyncRequest node that was paired with an HTTPAsyncResponse or a RESTAsyncResponse node. The unique identifier was <insert_1>.
Severity: 30 : Severe error
Explanation: It is an error to deploy a SOAPAsyncRequest node that is paired with an HTTPAsyncResponse or a RESTAsyncResponse node as it must be paired with a SOAPAsyncResponse node.
Response: Correct this error and redeploy the flow.

BIP3646: An attempt was made to deploy an HTTPAsyncRequest node that was paired with a SOAPAsyncResponse or a RESTAsyncResponse node. The unique identifier was <insert_1>.
Severity: 30 : Severe error
Explanation: It is an error to deploy an HTTPAsyncRequest node that is paired with a SOAPAsyncResponse or a RESTAsyncResponse node as it must be paired with an HTTPAsyncResponse node.
Response: Correct this error and redeploy the flow.

BIP3647: An attempt was made to deploy two HTTPAsyncResponse, RESTAsyncResponse, or SOAPAsyncResponse nodes with the same unique identifier <insert_1> to the same integration server
Severity: 30 : Severe error
Explanation: You cannot deploy two HTTPAsyncResponse, RESTAsyncResponse, or SOAPAsyncResponse nodes with the same unique identifier to the same integration server.
Response: Correct this error and redeploy the flow.

BIP3648: An attempt was made to deploy a SOAPAsyncResponse node that was paired with an HTTPAsyncRequest or a RESTAsyncRequest node. The unique identifier was <insert_1>.
Severity: 30 : Severe error
Explanation: It is an error to deploy a SOAPAsyncResponse node that is paired with an HTTPAsyncRequest or a RESTAsyncRequest node as it must be paired with a SOAPAsyncRequest node.
Response: Correct this error and redeploy the flow.

BIP3649: An attempt was made to deploy an HTTPAsyncResponse node that was paired with a SOAPAsyncRequest or a RESTAsyncRequest node. The unique identifier was <insert_1>.
Severity: 30 : Severe error
Explanation: It is an error to deploy an HTTPAsyncResponse node that is paired with a SOAPAsyncRequest or a RESTAsyncRequest node as it must be paired with an HTTPAsyncRequest node.
Response: Correct this error and redeploy the flow.

BIP3650: The HTTP Async request-response manager with the unique identifier <insert_1> has caught an exception. Please see following messages for futher details.
Severity: 30 : Severe error
Explanation: An exception was caught by the HTTP Async request-response manager with the unique identifier <insert_1>. This unique identifier could be used by either HTTPAsyncRequest or SOAPAsyncRequest nodes. See following messages for more details.
Response: If this error continues correct the error and redeploy.

BIP3651: Node <insert_1> sending an Async HTTP Request to <insert_2>.
Severity: 0 : Information
Explanation: See subsequent messages for success or failure messages relating to this request, and for any transport-specific messages.
Response: No action required.

BIP3652: An asynchronous request node with the unique identifier was <insert_1> is attempting to send a request, but its matching asynchronous response node is stopped or is not deployed.
Severity: 30 : Severe error
Explanation: An asynchronous request node cannot send a request if its paired asynchronous response node is not present when the request is made.
Response: Restart or redeploy the paired asynchronous response node with the unique identifier <insert_1>.

BIP3653: An error occurred while sending an Async HTTP Request. The HTTP Request-Line was: <insert_3>.
Severity: 30 : Severe error
Explanation: The HTTP Request Header bitstream (if any) to be used was: <insert_1>. The HTTP Request Message Body bitstream (if any) to be used was: <insert_2>. Ensure that the HTTP data is valid.
Response: See the following messages for information pertaining to this error.

BIP3654: An HTTPAsyncResponse node with the identifier <insert_1> cannot find its corresponding HTTPAsyncRequest node. It has currently checked <insert_2> times for the corresponding node, and will continue checking. It cannot receive any response messages until it can find its corresponding request Node.
Severity: 20 : Error
Explanation: An HTTPAsyncResponse Node cannot perform any work until its corresponding HTTPAsyncRequest node has been deployed.
Response: Deploy the corresponding HTTPAsyncRequest Node.

BIP3655: An HTTPAsyncResponse node with the unique identifier <insert_1> encountered an error while processing an inbound response message.
Severity: 30 : Severe error
Explanation: There was an error while an asynchronous response message was being processed.
Response: See subsequent messages for information pertinent to this error.

BIP3656: A SOAPAsyncResponse node received an http response message that it cannot process. The HTTP request was originally made to the destination <insert_2>. The HTTP status line that was returned was: <insert_1>. This node can only process responses that contain valid SOAP messages or SOAP faults.
Severity: 30 : Severe error
Explanation: The remote server returned an HTTP response message that this node cannot process.
Response: Check that the remote server is responding and that the request is specified correctly. Also ensure that the response contains a SOAP response or a SOAP fault message. See subsequent messages for information pertinent to this error.

BIP3657: A SOAPAsyncResponse node received an HTTP Error status code (5xx or 400) with an empty response body, when a SOAP payload was expected. The HTTP request was made to the destination <insert_2>. The HTTP status line that was returned was: <insert_1>.
Severity: 20 : Error
Explanation: It is an error for a remote Web server to return an empty payload when a SOAP response is required by the Message Exchange Pattern (MEP) of the selected operation.
Response: Determine why the remote Web server is returning an error.

BIP3658: A SOAPAsyncResponse node received an empty response body, when a SOAP payload was expected. The HTTP request was made to the destination <insert_2>. The HTTP status line that was returned was: <insert_1>.
Severity: 20 : Error
Explanation: It is an error for a remote Web server to return an empty payload when a SOAP response is required by the Message Exchange Pattern (MEP) of the selected operation.
Response: Determine why the remote Web server is returning an empty response body.

BIP3659: A SOAPAsyncResponse node received a response message which did not have a Content-Type HTTP header. The HTTP request was made to the destination <insert_2>. The HTTP status line that was returned was: <insert_1>.
Severity: 20 : Error
Explanation: It is an error for a remote Web server to return a payload without a Content-Type HTTP header.
Response: Determine why the remote Web server is not returning a Content-Type HTTP header.

BIP3660: A SOAPAsyncResponse node received a SOAP fault response message, but the HTTP status code was Success (2xx). The HTTP request was made to the destination <insert_2>. The HTTP status line that was returned was: <insert_1>.
Severity: 20 : Error
Explanation: It is an error for a remote Web server to return a SOAP fault message with an HTTP status code indicating Success (2xx).
Response: Determine why the remote Web server is returning a SOAP fault under an HTTP status code indicating Success.

BIP3661: The policy set <insert_1> was not found.
Severity: 20 : Error
Explanation: A policy set has been associated with a message flow or node, but the policy set has not been created in the integration node.
Response: Either correct the policy set name associated with the message flow or node so that it refers to a policy set that exists on the integration node, or create the policy set in the integration node. Stop and start the message flow or redeploy the bar file depending on the action that caused the initial error.

BIP3662: The policy set binding <insert_1> was not found.
Severity: 20 : Error
Explanation: A policy set binding has been associated with a message flow or node, but the binding has not been created in the integration node.
Response: Either correct the policy set binding name associated with the message flow or node so that it refers to a binding that exists on the integration node, or create the policy set binding in the integration node. Stop and start the message flow or redeploy the bar file depending on the action that caused the initial error.

BIP3663: The integration node registry runtime property <insert_1> required by the policy set or policy set binding <insert_2> is not defined.
Severity: 20 : Error
Explanation: A policy set or policy set binding requires an integration node registry runtime property, but the property has not been defined in the integration node.
Response: Define the integration node registry runtime property in the integration node using mqsichangeproperties. Stop and start the message flow or redeploy the bar file depending on the action that caused the initial error.

BIP3664: The mqsisetdbparms runtime property <insert_1> required by the policy set binding <insert_2> is not defined.
Severity: 20 : Error
Explanation: A policy set binding requires a mqsisetdbparms runtime property, but the property has not been defined in the integration node.
Response: Define the runtime property in the integration node using mqsisetdbparms. Stop and start the message flow or redeploy the bar file depending on the action that caused the initial error.

BIP3665: The policy set binding <insert_1> is of the wrong type for the specified node.
Severity: 20 : Error
Explanation: A policy set binding can be either a "consumer" (for SOAPRequest and SOAPAsynchronousRequest) or "provider" (for SOAPInput and SOAPReply) nodes. The specified binding is the wrong type for the node.
Response: Either correct the policy set binding name associated with the message flow or node so that it refers to a binding that is of the correct type, or change the type of the policy set binding. Stop and start the message flow or redeploy the bar file depending on the action that caused the initial error.

BIP3666: Failure in processing inbound message. Signature verification failed because it was created with relative namespace. <insert_1>.
Severity: 20 : Error
Explanation: The Ws-Security signature verification failed because the signature was created using a relative namespace. XML digital signatures using exclusive canonicalization should not use relative namespace URIs.
Response: Correct the WSDL and use absolute URIs for namespaces.

BIP3667: A SOAPAsyncResponse node received an HTTP Error Status Code <insert_1>, but the response message body was not a SOAP fault. The HTTP request was made to the destination <insert_3>. The HTTP status line that was returned was: <insert_2>.
Severity: 20 : Error
Explanation: It is an error for a remote Web server to return an HTTP Error status code (5xx or 400), without returning a SOAP fault message.
Response: Determine why the remote Web server is returning an HTTP Error status code without a SOAP fault.

BIP3668: Socket error detected while receiving data from a Web service located at host <insert_1>, port <insert_2>, path <insert_3>.
Severity: 30 : Severe error
Explanation: This may be a transient error, such as a server not responding, a server timeout or a symptom of an invalid hostname or port number.
Response: Check that the hostname and port number are valid, and point to a functioning Web service.

BIP3669: Error detected while receiving data from a Web service located at host <insert_1>, port <insert_2>, path <insert_3>.
Severity: 30 : Severe error
Explanation: This may be a transient error, such as a server not responding, a server timeout or it may be a symptom of an invalid hostname and/or port number.
Response: Check that the hostname, port number and URL path are valid, and point to a functioning Web service.

BIP3670: An HTTP error was encountered while making an HTTPS request through a proxy. The HTTP status code returned from the proxy was <insert_2> but a success (200) code was expected. The HTTPS request was made to the destination <insert_1> via the proxy server <insert_4>. The full HTTP status line that was returned from the proxy was: <insert_3>.
Severity: 30 : Severe error
Explanation: An error occurred during an HTTPS request via a proxy.
Response: Check that the remote server and the proxy are responding and that the request is specified correctly.

BIP3671: The connection, to initialize the internal WebSphere Service Registry and Repository (WSRR) cache, has failed to connect to the WebSphere Application Server hosting WSRR server on: <insert_1>.
Severity: 10 : Warning
Explanation: The connection to the WebSphere Application Server WSRR server by JMS has failed. Check the configuration of the IBM Integration Bus WSRR cache connection settings. Use the command: mqsireportproperties integrationNodeName -c ServiceRegistries -o DefaultWSRR -r.
Response: The IBM Integration Bus WSRR cache has been enabled but the connection cannot be made to the WebSphere Application Server WSRR server. For more information on the configuration required to use the WSRR nodes and the IBM Integration Bus WSRR cache, see the IBM Integration Bus information center.

BIP3672: The <insert_1> node has not received a response from WebSphere Service Registry and Repository (WSRR). The current value of the 'endpointAddress' configuration setting is: <insert_2>.
Severity: 10 : Warning
Explanation: The connection to the WSRR server has failed.
Response: Check the connections configuration details, for example the 'endpointAddress' value, by using the command: mqsireportproperties integrationNodeName -c ServiceRegistries -o DefaultWSRR -r

BIP3673: The WebSphere Service Registry and Repository (WSRR) cache update flow from the SupportPac IA9Q has been detected. You must undeploy this flow.
Severity: 10 : Warning
Explanation: The IA9Q WSRR cache update flow must be undeployed from the integration node before you use the WSRR query node support in v6.1.
Response: Undeploy the WSRR cache update flow.

BIP3674: The <insert_1> file is of the wrong version level and cannot be loaded.
Severity: 30 : Severe error
Explanation: All the files used by the WebSphere Service Registry and Repository (WSRR) lookup nodes and the IBM Integration Bus WSRR cache must be of a compatible level. The <insert_1> file is not compatible.
Response: Match the level of the <insert_1> file with the level of the file required to enable the WSRR connection.

BIP3675: The 'endpointAddress' configuration setting has not been set. This a mandatory setting for the WebSphere Service Registry and Repository (WSRR) lookup nodes.
Severity: 30 : Severe error
Explanation: The location or endpoint address of the WSRR server must be configured in the WSRR configurable service profile.
Response: Use the mqsichangeproperties command to set this value.

BIP3676: The query string from node <insert_1> that will be used to query the WebSphere Service Registry and Repository (WSRR) is: <insert_2>2
Severity: 0 : Information
Explanation: This is the query string that has been generated to query the WSRR.
Response: No user action required.

BIP3677: <insert_1>: <insert_2>, <insert_3>: <insert_4>, <insert_5>: <insert_6>, <insert_7>: <insert_8>, <insert_9>: <insert_10>0
Severity: 0 : Information
Explanation: User Trace
Response: No user action required.

BIP3678: A WSRR query has failed. The configuration is: EndpointAddress: <insert_1>; UserId, pw = <insert_2>, <insert_3>; TrustStore, pw = <insert_4>, <insert_5>; KeyStore, pw = <insert_6>, <insert_7>. The WSRR exception is: <insert_8>8
Severity: 30 : Severe error
Explanation: The query sent to WebSphere Service Registry and Repository (WSRR) has failed. This may be because the connection is not available, or because the query was badly formed. The EndpointAddress is the URL to the WSRR server. The other configuration settings listed in the message text specify details for the JMS connection: the name of the security identity (the UserId) and TrustStore and KeyStore in use, together with an indication whether their passwords are set.
Response: Check the WSRR Node configuration is set correctly. If security is enabled, make sure the user id, password and, if required by chosen security implementation, the integration node trust store and key store are set.

BIP3679: <insert_1>: <insert_2>, <insert_3>: <insert_4>, <insert_5>: <insert_6>, <insert_7>: <insert_8>, <insert_9>: <insert_10>0
Severity: 0 : Information
Explanation: User Trace
Response: No user action required.

BIP3680: The following error was returned by WSRR: <insert_1>1
Severity: 30 : Severe error
Explanation: The query sent to WebSphere Service Registry and Repository (WSRR) has failed and WSRR provided the message above.
Response: Refer to the WSRR documentation for details of the error message returned. The query sent to WSRR is written to user trace.

BIP3681: Error in information passed to WSRR. <insert_1>: <insert_2>. <insert_3>: <insert_4>.
Severity: 30 : Severe error
Explanation: The specified data is badly formed.
Response: Correct the data and retry the operation.

BIP3682: <insert_1>: <insert_2>, <insert_3>: <insert_4>, <insert_5>: <insert_6>, <insert_7>: <insert_8>, <insert_9>: <insert_10>0
Severity: 0 : Information
Explanation: User Trace
Response: No user action required.

BIP3683: A WSRR query has been timed out. The configured timeout value is <insert_1>. The endpoint address is <insert_2>.
Severity: 30 : Severe error
Explanation: A query was sent to WebSphere Service Registry and Repository (WSRR), but no response was received within the configured timeout period.
Response: Check that the WSRR server for the endpoint address is processing correctly, refer to the WSRR online help for more information. Consider increasing the connectionTimeout value using the mqsichangeproperties command. Note that this setting applies to all WSRR queries for this integration node.

BIP3684: Invalid value specified on the ServiceRegistries configurable service. The connectionTimeout value is currently set to <insert_1>, so the documented default value will be used.
Severity: 10 : Warning
Explanation: An mqsichangeproperties command specified an invalid value for the connectionTimeout property on the ServiceRegistries configurable service. The connectionTimeout value specified will be ignored and the documented default will apply.
Response: Run the mqsichangeproperties command, specifying the connectionTimeout property value (in seconds) as a positive integer.

BIP3685: The following details will be used to query WebSphere Service Registry and Repository (WSRR) from node <insert_1>: query string=<insert_2>, depth=<insert_3>. The Depth Policy that controls how the retrieved data will be displayed is <insert_4>.
Severity: 0 : Information
Explanation: The specified query string and depth are sent to WSRR. The information returned from WSRR is added to the LocalEnvironment as specified by the DepthPolicy.
Response: If these are not the settings you expected, check whether the node properties are being overridden in the LocalEnvironment, being careful to check the spelling of the DepthPolicy override value if this is being used.

BIP3686: One or more service endpoints retrieved from WSRR by the EndpointLookup node <insert_1> could not be processed. The number of endpoints not processed was <insert_2>.
Severity: 10 : Warning
Explanation: A number of service endpoint entities were retrieved from WSRR, but one or more of these did not have a relationship that is required for it to be processed by the EndpointLookup node. An entity that is not processed will not appear in the LocalEnvironment and is therefore not available to subsequent nodes.
Response: See User Trace for information on the individual WSRR entities that were not processed. The User Trace also shows the query sent to WSRR.

BIP3687: An error occurred whilst evaluating the following <insert_1> expression for User Property <insert_2>: <insert_3>.
Severity: 30 : Severe error
Explanation: The node properties define an ESQL or XPath expression to retrieve the value for the specified property from the message. The expression did not evaluate successully.
Response: Check that you have defined a valid expression of the specified type (XPath or ESQL) and that it correctly identifies a simple string value in the message.

BIP3688: A SOAPAsyncResponse node did not receive a response from <insert_1> because the timeout of <insert_2> milliseconds expired before a response was received.
Severity: 20 : Error
Explanation: A timeout prevented the SOAP Async Response node from receiving a response. This may be a transient error, such as a server is busy or it could be that the server is no longer responding.
Response: See the following messages for information pertaining to this error.

BIP3689: WS-RM conflict detected for URL <insert_1>.
Severity: 20 : Error
Explanation: Only one node in a single integration server can use WS-RM for each URL. An invalid configuration has been detected when using the integration node wide HTTP Listener
Response: Change the URLs so they don't conflict.

BIP3690: An attribute conflict was detected between two different nodes types using the same URL. The integration server <insert_1> is using the path suffix <insert_2> for the URL.
Severity: 10 : Warning
Explanation: The HTTP listener process allows different node types using HTTP to use the same URL. Are you sure an HTTP node and a SOAP node flow should process the same messages?
Response: Change the URLs so they don't conflict.

BIP3691: A SOAP request encountered an HTTP error while making an HTTP request. The HTTP request was made to the destination <insert_2>. The HTTP status line that was returned was: <insert_1>.
Severity: 30 : Severe error
Explanation: An error occurred during an HTTP request.
Response: Check that the remote server is responding and that the request is specified correctly. See subsequent messages for information pertinent to this error.

BIP3692: An asynchronous request encountered an HTTP error while making an HTTP request. The HTTP request was made to the destination <insert_2>. The HTTP status line that was returned was: <insert_1>.
Severity: 30 : Severe error
Explanation: An error occurred during an HTTP request.
Response: Check that the remote server is responding and that the request is specified correctly. See subsequent messages for information pertinent to this error.

BIP3693: A SOAP reply encountered an HTTP error while making an asynchronous HTTP reply. The HTTP reply was made to the destination <insert_2>. The HTTP status line that was returned was: <insert_1>.
Severity: 30 : Severe error
Explanation: An error occurred during an HTTP request.
Response: Check that the remote server is responding and that the WS-Addressing ReplyTo address is specified correctly. See subsequent messages for information pertinent to this error.

BIP3694: An HTTP error was encountered while an asynchronous SOAP fault reply was being sent over HTTP. The HTTP reply was made to the destination <insert_2>. The HTTP status line that was returned was: <insert_1>.
Severity: 30 : Severe error
Explanation: An error occurred during an HTTP request.
Response: Check that the remote server is responding and that the WS-Addressing FaultTo address is specified correctly. See subsequent messages for information pertinent to this error.

BIP3695: An attempt was made to deploy two SOAP Async Request Nodes with the same unique identifier <insert_1> to the same integration server
Severity: 30 : Severe error
Explanation: It is an error to deploy two SOAP Async Request Nodes with the same unique identifier to the same integration server.
Response: Correct this error and redeploy the flow.

BIP3696: An attempt was made to deploy two SOAP Async Response Nodes with the same unique identifier <insert_1> to the same integration server
Severity: 30 : Severe error
Explanation: It is an error to deploy two SOAP Async Response Nodes with the same unique identifier to the same integration server.
Response: Correct this error and redeploy the flow.

BIP3697: An attempt was made to deploy an asynchronous node which had an invalid unique identifier <insert_1>.
Severity: 30 : Severe error
Explanation: It is an error to deploy an asynchronous node with an invalid unique identifier. The identifier cannot be zero length.
Response: Correct this error and redeploy the flow.

BIP3698: A SOAPAsyncResponse node with the identifier <insert_1> cannot find its corresponding SOAPAsyncRequest node. It has currently checked <insert_2> times for the corresponding node, and will continue checking. It cannot receive any asynchronous response messages until it can find its corresponding SOAPAsyncRequest node.
Severity: 20 : Error
Explanation: It is an error to deploy a SOAPAsyncResponse node without its corresponding Async Request node.
Response: Deploy the corresponding SOAPAsyncRequest node.

BIP3699: An asynchronous response node with unique identifier <insert_1> has received a message that it cannot process.
Severity: 20 : Error
Explanation: Either the host processing the message does not implement the WS-Addressing 'Final' specification correctly, or an unexpected message was received in error.
Response: See subsequent messages for information pertinent to this error.

BIP3701: A Java exception was thrown whilst calling the Java JNI method <insert_1>. The Java exception was <insert_2>. The Java stack trace was <insert_3>.
Severity: 20 : Error
Explanation: Correct the error, and if necessary redeploy the flow.

BIP3702: A Fatal Java exception was thrown whilst calling the Java JNI method <insert_1>. The Java exception was <insert_2>. The Java stack trace was <insert_3>.
Severity: 20 : Error
Explanation: Correct the error, and if necessary redeploy the flow.

BIP3703: An unexpected null value was returned whilst calling the Java JNI method <insert_1>.
Severity: 20 : Error
Explanation: Correct the error, and if necessary redeploy the flow.

BIP3704: Message does not contain a valid SOAP Reply Identifier.
Severity: 20 : Error
Explanation: A valid SOAP Reply Identifier is required for SOAP Reply processing to be successful. The needed information was not found in the incoming message, and no SOAP reply can be made
Response: Provide the required SOAP Reply Identifier.

BIP3705: An attempt was made to send a reply when the inbound message was a One-Way WSDL Operation.
Severity: 20 : Error
Explanation: The Message Exchange Pattern (MEP) is already completed, and no additional reply is needed or allowed.
Response: Do not send a reply when a OneWay MEP is used.

BIP3706: An asynchronous request node with the identifier <insert_1> cannot find its corresponding asynchronous response node.
Severity: 20 : Error
Explanation: It is an error to deploy an asynchronous request node without its corresponding asynchronous response node.
Response: Deploy the corresponding asynchronous response node.

BIP3707: A SOAP request received an empty response body, when a SOAP payload was expected. The HTTP request was made to the destination <insert_2>. The HTTP status line that was returned was: <insert_1>.
Severity: 20 : Error
Explanation: It is an error for a remote Web server to return an empty payload when a SOAP response is required by the Message Exchange Pattern (MEP) of the selected operation.
Response: Determine why the remote Web server is returning an empty response body.

BIP3708: A SOAP request received a response message body when one was not expected because a one-way Messsage Exchange Pattern (MEP) was being used. The HTTP request was made to the destination <insert_2>. The HTTP status line that was returned was: <insert_1>.
Severity: 20 : Error
Explanation: It is an error for a remote Web server to return a payload when the selected operation is a one-way MEP.
Response: Determine why the remote Web server is returning a response body.

BIP3709: A SOAP request received a response message which did not have a Content-Type HTTP header. The HTTP request was made to the destination <insert_2>. The HTTP status line that was returned was: <insert_1>.
Severity: 20 : Error
Explanation: It is an error for a remote Web server to return a payload without a Content-Type HTTP header.
Response: Determine why the remote Web server is not returning a Content-Type HTTP header.

BIP3710: A SOAP request received a SOAP fault response message, but the HTTP status code was Success (2xx). The HTTP request was made to the destination <insert_2>. The HTTP status line that was returned was: <insert_1>.
Severity: 20 : Error
Explanation: It is an error for a remote Web server to return a SOAP fault message with an HTTP status code indicating Success (2xx).
Response: Determine why the remote Web server is returning a SOAP fault under an HTTP status code indicating Success.

BIP3711: A SOAP request received an HTTP Error Status Code <insert_1>, but the response message body was not a SOAP fault. The HTTP request was made to the destination <insert_3>. The HTTP status line that was returned was: <insert_2>.
Severity: 20 : Error
Explanation: It is an error for a remote Web server to return an HTTP Error status code (5xx or 400), without returning a SOAP fault message.
Response: Determine why the remote Web server is returning an HTTP Error status code without a SOAP fault.

BIP3712: A SOAP request received an invalid HTTP response. The HTTP request was made to the destination <insert_2>. The HTTP status line that was returned was: <insert_1>.
Severity: 20 : Error
Explanation: It is an error for a remote Web server to return an invalid HTTP response.
Response: Determine why the remote Web server is returning an invalid HTTP response.

BIP3713: A SOAP request received an HTTP Error status code (5xx or 400) with an empty response body, when a SOAP payload was expected. The HTTP request was made to the destination <insert_2>. The HTTP status line that was returned was: <insert_1>.
Severity: 20 : Error
Explanation: It is an error for a remote Web server to return an empty payload when a SOAP response is required by the Message Exchange Pattern (MEP) of the selected operation.
Response: Determine why the remote Web server is returning an error.

BIP3714: A SOAPAsyncRequest Node encountered an HTTP error whilst making an HTTP Request. An HTTP error was returned when an HTTP '202 Accepted' acknowledgement response was expected. The HTTP Status-Line returned was: <insert_1>.
Severity: 30 : Severe error
Explanation: An error occurred whilst performing an HTTP Request. Check that the remote server is responding and that the request is specified correctly.
Response: See the following messages for information pertaining to this error.

BIP3715: A SOAPRequest Node encountered an HTTP error whilst making an HTTP Request. An HTTP error was returned when an HTTP '202 Accepted' acknowledgement response was expected. The HTTP Status-Line returned was: <insert_1>.
Severity: 30 : Severe error
Explanation: An error occurred whilst performing an HTTP Request. Check that the remote server is responding and that the request is specified correctly.
Response: See the following messages for information pertaining to this error.

BIP3716: A SOAP Fault occurred whilst processing an inbound message. The operation name associated with the inbound message was: <insert_1>.
Severity: 30 : Severe error
Explanation: The inbound bitstream being processed was: <insert_2>.
Response: See the following messages for information pertaining to this error.

BIP3717: An asynchronous response node with unique identifier <insert_1> encountered an error while processing an inbound response message. The operation name associated with the inbound response message was: <insert_2>.
Severity: 30 : Severe error
Explanation: There was an error while an asynchronous response message was being processed.
Response: See subsequent messages for information pertinent to this error.

BIP3718: A SOAP fault occurred when an asynchronous response node with the unique identifier <insert_1> was processing an inbound response message. The operation name associated with the inbound response message was: <insert_2>.
Severity: 30 : Severe error
Explanation: The inbound response bit stream being processed was: <insert_3>.
Response: See subsequent messages for information pertinent to this error.

BIP3719: Node <insert_1> sending SOAP request via transport <insert_2> (<insert_3>) for operation <insert_4> of type <insert_5>.
Severity: 0 : Information
Explanation: See subsequent messages for success or failure messages relating to this request, and for any transport-specific messages.
Response: No action required.

BIP3720: Node <insert_1> received a SOAP response message via transport <insert_2> (<insert_3>) for operation <insert_4>.
Severity: 0 : Information
Explanation: The integration node sent a SOAP request, and has received a response.
Response: No action required.

BIP3721: Node <insert_1> received a SOAP acknowledge message via transport <insert_2> (<insert_3>) for operation <insert_4>.
Severity: 0 : Information
Explanation: The integration node sent a SOAP request, and has received an acknowledgement from the server that the request was received. This may be because the message was sent as an asynchronous request, and therefore the response message will be sent elsewhere, or because the request message was a one-way message exchange pattern, and therefore no response message should be expected.
Response: No action required.

BIP3722: Node <insert_1> sending a <insert_2> reply message to the originating client.
Severity: 0 : Information
Explanation: See subsequent messages for success or failure messages relating to this reply, and for any transport-specific messages.
Response: No action required.

BIP3723: Node <insert_1> sending a SOAP reply message via transport <insert_2> (<insert_3>).
Severity: 0 : Information
Explanation: This message is used when sending non-anonymous replies to SOAP clients. A new connection is made to the remote server if required, and the reply is sent to the server. See subsequent messages for success or failure messages relating to this reply, and for any transport-specific messages.
Response: No action required.

BIP3724: Node <insert_1> sending a SOAP fault message to the originating client.
Severity: 0 : Information
Explanation: See subsequent messages for success or failure messages relating to this reply, and for any transport-specific messages.
Response: No action required.

BIP3725: Node <insert_1> sending a SOAP fault message via transport <insert_2> (<insert_3>).
Severity: 0 : Information
Explanation: This message is used when sending non-anonymous faults to SOAP clients. A new connection is made to the remote server if required, and the fault is sent to the server. See subsequent messages for success or failure messages relating to this reply, and for any transport-specific messages.
Response: No action required.

BIP3726: Failed to setup SOAP transport for node <insert_1>.
Severity: 20 : Error
Explanation: The SOAP nodes rely on the configuration of the SOAP transport layer within the integration node, and this has not been initialised correctly. The node will not be operational until the problems have been corrected.
Response: Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3727: <insert_1>1
Severity: 20 : Error
Explanation: The SOAP nodes are built on top of the integration node WS-Security layer, and this layer has returned a configuration exception, the text of which is included in the message.
Response: Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3728: Configuration of WS-Security layer using policy set <insert_1> and policy set binding <insert_2> failed.
Severity: 20 : Error
Explanation: WS-Security configuration requires correctly initialised policy set and policy set binding information in order to succeed. An error has occurred whilst attempting to use policy set <insert_1> and policy set binding <insert_2>. Common causes are:
1: Either the policy set name or policy set binding name is missing from the node (or flow) configuration.
2: If X.509 tokens are being used, including implicit usage such as signing or encryption, the keystore and/or truststore is not be set correctly.
However, this may be an internal error, possibly due to a faulty installation. A review of the exception text may indicate a solution.
Response: Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3729: A key store error has occurred with file <insert_1>.
Severity: 20 : Error
Explanation: The WS-Security layer is trying to use a key store for X.509-based security, but has encountered an error whilst doing so. Common causes are:
1: The key store does not exist, or the integration node lacks permission to access it.
2: The password for the key store is incorrect.
3: The key store type has been set incorrectly.
Subsequent error messages may contain more information.
Response: Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3730: A UsernameToken is required by the configuration of the WS-Security layer, but the integration node security manager has not provided a username.
Severity: 20 : Error
Explanation: The WS-Security layer is trying to create a UsernameToken, and needs a username to do so. Common causes are:
1: No username has been provided in the Properties folder of the message tree passed into the node. One of IdentitySourceToken or IdentityMappedToken should be provided.
2: Identity propagation is not enabled for this node. This is controlled by the security profile associated with the node.
Subsequent error messages may contain more information.
Response: Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3731: An error occurred during WS-Security processing using policy set <insert_1> and policy set binding <insert_2> with security profile <insert_3>.
Severity: 20 : Error
Explanation: WS-Security operation requires correctly configured policy set and policy set binding information in order to succeed. An error has occurred whilst attempting to use policy set <insert_1> and policy set binding <insert_2> with security profile <insert_3>. See subsequent error messages for more information.
Response: Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3732: The specified WSDL binding <insert_1> could not be found in the supplied WSDL file <insert_2>.
Severity: 20 : Error
Explanation: The WSDL binding <insert_1> from the target namespace <insert_4> associated with message set <insert_3> was not found in the WSDL file <insert_2>. This could be because the WSDL file is missing, invalid or corrupt.
Response: Determine the cause of the error and correct it. Ensure that the WSDL file is valid and that it validates correctly.

BIP3733: An exception occurred whilst registering the WSDL operation <insert_4> from the specified binding <insert_1> in the supplied WSDL file <insert_2>. The deployed WSDL may be invalid.
Severity: 20 : Error
Explanation: The WSDL binding <insert_1> from the target namespace <insert_3> contained the operation <insert_4> that could not be registered for a WSDL consumer (SOAPRequest or SOAPAsyncRequest) node. This is normally a symptom of an invalid or corrupt WSDL file. Ensure that the WSDL file is valid and that it validates correctly.
Response: Determine the cause of the error and correct it.

BIP3734: An exception occurred whilst registering the WSDL service <insert_1> from the WSDL file <insert_2> with the target namespace <insert_3>.
Severity: 20 : Error
Explanation: There was an exception whilst registering the WSDL service <insert_1> for a WSDL consumer (SOAPRequest or SOAPAsyncRequest) node.
Response: Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3735: An exception occurred whilst registering the WSDL service <insert_1> from the WSDL file <insert_2> with the target namespace <insert_3>.
Severity: 20 : Error
Explanation: There was an exception whilst registering the WSDL service <insert_1> for a WSDL provider (SOAPInput) node.
Response: Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3736: Unable to register the selected operation <insert_1>. The operation was not found in the WSDL.
Severity: 20 : Error
Explanation: The selected operation <insert_1> could not be found in the WSDL.
Response: Determine the cause of the error and correct it.

BIP3737: An invalid Message Exchange Pattern (MEP) <insert_1> was found when registering the operation <insert_2> for a SOAPAsyncRequestNode.
Severity: 20 : Error
Explanation: It is invalid to select a 'One-way' or 'Notification' MEP for use in a SOAPAsyncRequest node.
Response: Correct the error and redeploy the flow.

BIP3738: There was an error whilst loading or configuring the module <insert_1> from location <insert_2>.
Severity: 20 : Error
Explanation: An error occurred whilst trying to load or configure the requested module <insert_1> from the location <insert_2>. This may be an internal error, possibly due to a faulty installation. A review of the exception text may indicate a solution.
Response: Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3739: Cache preload from WSRR has failed: <insert_1> of <insert_2> queries failed to load.
Severity: 30 : Severe error
Explanation: The integration node encountered one or more problems when preloading the cache from WebSphere Service Registry and Repository (WSRR).
Response: See User Trace for information on the individual WSRR queries that failed to load. Check that you have configured predefinedCacheQueries correctly and that any <insert_depth=N> specifiers are correctly formatted. Use the mqsireportproperties and mqsichangeproperties commands to check and change this option.

BIP3740: An attempt was made to use an invalid <insert_3> message identifier <insert_1>.
Severity: 20 : Error
Explanation: This may be caused by the identifier being corrupted or misused, for example by an invalid CAST. The internal error code was <insert_2>.
Response: Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3741: An attempt was made to use a <insert_2> message <insert_3> but the <insert_3> was locked for reply by another reply node.
Severity: 20 : Error
Explanation: This can be caused by sending the same <insert_3> to two different <insert_2> Reply nodes at the same time, which is an error as a <insert_3> can only be used once. The <insert_3> was <insert_1>.
Response: Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3742: An attempt was made to use a <insert_2> message <insert_3> after it had already been used.
Severity: 20 : Error
Explanation: A <insert_2> message <insert_3> may only be used once to send a single reply (or a single async response). The <insert_2> message <insert_3> was <insert_1>.
Response: Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3743: An attempt was made to use a <insert_2> message <insert_3> after it had timed out. The <insert_2> message <insert_3> was <insert_1>.
Severity: 20 : Error
Explanation: Once a <insert_2> message <insert_3> expires it can no longer be used.
Response: Determine the cause of the error and correct it. Subsequent error messages may contain more information.

BIP3744: The node <insert_2> made an attempt to send a SOAP fault, but the reply identifier was invalid.
Severity: 20 : Error
Explanation: Either the reply identifier has already been used to send a reply or the reply identifier timed out. Each reply identifier can only be used to send one reply, and cannot be used after it has timed out. The SOAP message reply identifier used was <insert_1>.
Response: Determine the cause of the error and correct it. Subsequent error messages might contain more information.

BIP3745: The node <insert_2> received a message with an invalid <insert_3> <insert_4>.
Severity: 20 : Error
Explanation: A valid <insert_3> <insert_4> is required for <insert_3> Reply processing to be successful and as one was not found in the incoming message, no <insert_3> reply can be made. Either the <insert_4> has already been used to send a reply or the <insert_4> timed out. Each <insert_4> can only be used to send one reply, and cannot be used after it has timed out. The <insert_3> message <insert_4> received was <insert_1>.
Response: Determine the cause of the error and correct it. Subsequent error messages might contain more information.

BIP3746: An asynchronous response node <insert_3> with the unique identifier <insert_1> has received a message that it cannot process because the context in the message was invalid.
Severity: 20 : Error
Explanation: This might be caused by the context handle being corrupted or misused, or because the host processing the message does not implement the WS-Addressing 1.0 'Final' specification correctly, or because an unexpected message was received in error, or because a response was accidently sent more than once. The SOAP message handle identifier was <insert_2>.
Response: Determine the cause of the error and correct it. Subsequent error messages might contain more information.

BIP3747: The SOAP Input node <insert_1> encountered an error while initializing the environment.
Severity: 20 : Error
Explanation: An internal error occurred during initialization.
Response: See previous error messages to determine the cause of the error.

BIP3748: The SOAP Input node <insert_1> encountered an error while processing the inbound SOAP message.
Severity: 20 : Error
Explanation: An error occurred during inbound message processing.
Response: See previous error messages to determine the cause of the error.

BIP3749: The SOAP Input node <insert_1> encountered an error while validating an inbound message.
Severity: 20 : Error
Explanation: An internal error occurred during message validation.
Response: See previous error messages to determine the cause of the error.

BIP3750: The SOAP Input node <insert_1> encountered an error while processing the inbound SOAP message header.
Severity: 20 : Error
Explanation: An internal error occurred during the processing of security information in the message header.
Response: See previous error messages to determine the cause of the error.

BIP3751: The SOAP Reply node <insert_1> encountered an error while initializing the environment.
Severity: 20 : Error
Explanation: An internal error occurred during initialization.
Response: See previous error messages to determine the cause of the error.

BIP3752: The SOAP Reply node <insert_1> encountered an error while processing a reply message.
Severity: 20 : Error
Explanation: An error occurred during reply message processing.
Response: See previous error messages to determine the cause of the error.

BIP3753: The SOAP Request node <insert_1> encountered an error while processing the node properties.
Severity: 20 : Error
Explanation: An internal error occurred during the processing of node properties.
Response: See previous error messages to determine the cause of the error.

BIP3754: The SOAP Request Node or SOAP Async Request Node <insert_1> encountered an error while processing the outbound SOAP request.
Severity: 20 : Error
Explanation: An error occurred while processing the SOAP Request.
Response: See previous error messages for an indication to the cause of the errors.

BIP3755: The SOAP Async Request node <insert_1> encountered an error while initializing the environment.
Severity: 20 : Error
Explanation: An internal error occurred during initialization.
Response: See previous error messages to determine the cause of the error.

BIP3756: The SOAP Async Response node <insert_1> encountered an error while processing the node properties.
Severity: 20 : Error
Explanation: An internal error occurred during the processing of node properties.
Response: See previous error messages to determine the cause of the error.

BIP3757: The SOAP Async Response node <insert_1> encountered an error while processing the inbound SOAP response message.
Severity: 20 : Error
Explanation: An internal error occurred during message processing.
Response: See previous error messages to determine the cause of the error.

BIP3758: The SOAP Async Request node <insert_1> encountered an error while processing the node properties.
Severity: 20 : Error
Explanation: An internal error occurred during the processing of node properties.
Response: See previous error messages to determine the cause of the error.

BIP3759: The SOAP Async Response node <insert_1> encountered an error while validating an inbound response message.
Severity: 20 : Error
Explanation: An internal error occurred during response message validation.
Response: See previous error messages to determine the cause of the error.

BIP3760: The SOAP Input node <insert_1> encountered an error while processing the node properties.
Severity: 20 : Error
Explanation: An internal error occurred during the processing of node properties.
Response: See previous error messages to determine the cause of the error.

BIP3761: The input node <insert_1> did not make an attempt to send a fault, because a reply had already been sent.
Severity: 20 : Error
Explanation: Only one reply can be sent for a request. Either a Reply node sent a reply already, or the message timed out and a timeout reply was sent automatically.
Response: Determine the cause of the error and correct it. Subsequent error messages might contain more information.

BIP3762: An attempt was made to use a <insert_1> that has the transport type <insert_2> where the transport type of <insert_3> was expected.
Severity: 20 : Error
Explanation: A reply node has received an identifier that does not match the transport being used in the node.
Response: If this is a HTTPReply node then the identifier must have been created by a HTTPInput node. If this is a SOAPReply node then the identifier must have been created by a SOAPInput node.

BIP3763: A request for WSDL data was received for URI <insert_1>, but the input node <insert_2> in message flow <insert_3> is not configured to allow ?wsdl.
Severity: 10 : Warning
Explanation: An HTTP GET request with a query string has been received for a message flow implementing a Web service, but the associated input node is not configured to allow ?wsdl.
Response: Set the appropriate input node property and redeploy the message flow.

BIP3764: A request for WSDL data was received for URI <insert_1>, but the query string <insert_2> is not recognised.
Severity: 20 : Error
Explanation: An HTTP GET request with a query string has been received for a message flow implementing a Web service, but the specified query string is not recognised.
Response: Correct the query string. Only ?wsdl is always valid. Other query strings are only valid if they appear in a previously returned WSDL or XML Schema document for this URI.

BIP3765: A request for WSDL data was received for URI <insert_1>, but the data is not available. The query string was <insert_2> and the message set name was <insert_3>.
Severity: 20 : Error
Explanation: An HTTP GET request with a query string has been received for a message flow implementing a Web service, but the requested data cannot be found. This may be because the files have been moved or renamed after deployment.
Response: Redeploy the message set containing the WSDL that was used to configure the flow and retry the request.

BIP3766: When sending a request in Gateway Mode, the WS-Adressing Action property was not set in the LocalEnvironment so the request cannot be sent.
Severity: 20 : Error
Explanation: In Gateway mode when using WS-Addressing (WSA), the WSA Action must be set in the LocalEnvironment before the request can be sent. An example of this in ESQL would be: SET OutputLocalEnvironment.Destination.SOAP.Request.WSA.Action = 'myAction';
Response: Set the WSA Action to correct the problem and redeploy the flow.

BIP3767: A SOAPReply node was asked to send a reply but the input message was determined (by a SOAPInput node configured as a Gateway) to be a one-way operation, and no reply is needed or allowed.
Severity: 20 : Error
Explanation: In Gateway Mode, the SOAP Input Node determines if the message is a one-way message automatically where possible. Once a message is determined to be one-way, then the Message Exchange Pattern (MEP) is completed, and no reply is needed or allowed.
Response: Do not send a reply when a one-way MEP is used.

BIP3768: An invalid message has been injected into an HTTP node causing a fault.
Severity: 20 : Error
Explanation: A fault has been caused by an injected message.
Response: If a fault was not expected then the input message must be corrected.

BIP3769: Service Federation SCMP listener initialized. Additional information : <insert_1> <insert_2>
Severity: 0 : Information
Explanation: The Service Federation SCMP listener has been initialized and is listening for requests at the stated URL.
Response: No action required.

BIP3770: Service Federation Management SCMP listener initialization failed. Additional information : <insert_1> <insert_2>
Severity: 30 : Severe error
Explanation: The Service Federation Management SCMP listener initialization failed. The reason for the failure is shown in the additional information.
Response: Contact your IBM support center.

BIP3771: Internal error in Service Federation Management SCMP listener initialization: <insert_1>
Severity: 30 : Severe error
Explanation: An error has occurred during Service Federation Management SCMP listener initialization.
Response: Contact your IBM support center.

BIP3772: Internal error in the Service Federation Management SCMP processing: <insert_1>
Severity: 30 : Severe error
Explanation: An error has occurred in Service Federation Management SCMP listener processing.
Response: Contact your IBM support center.

BIP3773: Service Federation Management proxy processing has sent a fault message to URL <insert_1>
Severity: 20 : Error
Explanation: An error has occurred in Service Federation Management proxy listener processing. A fault message has been sent to URL <insert_1>.
Response: No action required.

BIP3774: The Service Federation Manager proxy listener has stopped listening on port <insert_1> for <insert_2> connections.
Severity: 0 : Information
Explanation: The Service Federation Manager proxy listener is no longer listening on the TCPIP port <insert_1> for connections of type <insert_2>.
Response: No user action required.

BIP3775: The Service Federation Manager proxy listener has started listening on port <insert_1> for <insert_2> connections.
Severity: 0 : Information
Explanation: The Service Federation Manager proxy listener is currently listening on the TCPIP port <insert_1> for connections of type <insert_2>
Response: No user action required.

BIP3776: An error has occurred during Service Federation Manager proxy listener startup: the specified TCPIP port (<insert_1>) is already in use.
Severity: 30 : Severe error
Explanation: The Service Federation Manager proxy listener needs to bind to a TCPIP port for correct operation to be possible. The TCPIP port number <insert_1> is in use by another application.
Response: Stop other applications from using the specified port, or delete any created proxy groups and configure the Service Federation Manager to use an unused port.

BIP3777: The Service Federation Manager proxy listener has received an HTTP message on port <insert_1> with URL path <insert_2>.
Severity: 0 : Information
Explanation: The Service Federation Manager proxy listener is listening on port <insert_1> and has received a message sent by a client using URL path <insert_2>. This message will be forwarded to the target service by a Service Federation proxy.
Response: No action required.

BIP3778: The Service Federation Manager proxy listener has received an HTTPS message on port <insert_1> with URL path <insert_2>.
Severity: 0 : Information
Explanation: The Service Federation Manager proxy listener is listening on port <insert_1> and has received a message sent by a client using URL path <insert_2>. This message will be forwarded to the target service by a Service Federation proxy.
Response: No action required.

BIP3779: Maximum client wait time <insert_3> reached; the Service Federation Manager proxy listener has sent a fault message back to a client using port <insert_1> and URL path <insert_2>.
Severity: 10 : Warning
Explanation: A Service Federation proxy has taken too long to forward a request received on port <insert_1> and URL path <insert_2> to the target service. The Service Federation Manager proxy listener has sent a fault message back to the originating client to terminate the request.
Response: Either increase the speed of the proxy flow, or increase the maximum client wait time for the nodes using this URL.

BIP3780: A Service Federation proxy group already exists with uuid <insert_1> (existing group label <insert_2>).
Severity: 20 : Error
Explanation: A request to create a new Service Federation proxy group has been received. However, a proxy group with uuid <insert_1> already exists. The existing group label is <insert_2>.
Response: Change the uuid of the new proxy group and resubmit the create request.

BIP3781: Service Federation proxy group <insert_2> (uuid=<insert_1>) successfully created.
Severity: 0 : Information
Explanation: The integration node received a configuration message containing an instruction to create the Service Federation proxy group <insert_2> (uuid=<insert_1>), and successfully performed this action.
Response: No user action required.

BIP3782: Service Federation proxy group <insert_2> (uuid=<insert_1>) successfully changed.
Severity: 0 : Information
Explanation: The integration node received a configuration message containing an instruction to change the Service Federation proxy group <insert_2> (uuid=<insert_1>), and successfully performed this action.
Response: No user action required.

BIP3783: Request to change Service Federation proxy group <insert_2> (uuid=<insert_1>): proxy group does not exist.
Severity: 10 : Warning
Explanation: The integration node received a configuration message containing an instruction to change Service Federation proxy group <insert_2> (uuid=<insert_1>) but this can not be completed because the proxy group does not exist.
Response: Either correct the details of the proxy group to be changed and resubmit, or submit a create request for a new proxy group. If the problem persists, contact your IBM support center.

BIP3784: Service Federation proxy group <insert_2> (uuid=<insert_1>) successfully deleted.
Severity: 0 : Information
Explanation: The integration node received a configuration message containing an instruction to delete the Service Federation proxy group <insert_2> (uuid=<insert_1>), and successfully performed this action.
Response: No user action required.

BIP3785: Request to report on Service Federation proxy group <insert_2> (uuid <insert_1>): proxy group does not exist.
Severity: 10 : Warning
Explanation: The integration node received a configuration message containing an instruction to obtain a report of the Service Federation proxy group <insert_2> (uuid <insert_1>), but this proxy group does not exist.
Response: Correct the name of the proxy group you wish to be reported and resubmit your request. If the problem persists, contact your IBM support center.

BIP3786: Service Federation proxy group <insert_2> (uuid=<insert_1>) successfully started.
Severity: 0 : Information
Explanation: The integration node received a configuration message containing an instruction to start the Service Federation proxy group <insert_2> (uuid=<insert_1>), and successfully performed this action.
Response: No user action required.

BIP3787: Request to start Service Federation proxy group <insert_2> (uuid=<insert_1>): proxy group does not exist.
Severity: 10 : Warning
Explanation: The integration node received a configuration message containing an instruction to start Service Federation proxy group <insert_2> (uuid=<insert_1>) but this cannot be completed because the proxy group does not exist.
Response: Correct the details of the proxy group to be started and resubmit the request. If the problem persists, contact your IBM support center.

BIP3788: Service Federation proxy group <insert_2> (uuid=<insert_1>) successfully stopped.
Severity: 0 : Information
Explanation: The integration node received a configuration message containing an instruction to stop the Service Federation proxy group <insert_2> (uuid=<insert_1>), and successfully performed this action.
Response: No user action required.

BIP3789: Request to stop Service Federation proxy group <insert_2> (uuid=<insert_1>): proxy group does not exist.
Severity: 10 : Warning
Explanation: The integration node received a configuration message containing an instruction to stop Service Federation proxy group <insert_2> (uuid=<insert_1>) but this cannot be completed because the proxy group does not exist.
Response: Correct the details of the proxy group to be stopped and resubmit the request. If the problem persists, contact your IBM support center.

BIP3790: Request to establish the status of Service Federation proxy group <insert_2> (uuid=<insert_1>): proxy group does not exist.
Severity: 10 : Warning
Explanation: The integration node received a configuration message containing an instruction to establish the status of Service Federation proxy group <insert_2> (uuid=<insert_1>) but this can not be completed because the proxy group does not exist.
Response: Correct the details of the proxy group and resubmit the request. If the problem persists, contact your IBM support center.

BIP3791: Request to delete Service Federation proxy group <insert_1>: proxy group does not exist.
Severity: 10 : Warning
Explanation: The integration node received a configuration message containing an instruction to delete Service Federation proxy group <insert_1> but this cannot be completed because the proxy group does not exist.
Response: Correct the details of the proxy group to be deleted and resubmit the request. If the problem persists, contact your IBM support center.

BIP3792: Error loading Service Federation proxy group <insert_1>. Exception details: <insert_2>2
Severity: 20 : Error
Explanation: The integration node's internal record for Service Federation proxy group <insert_1> is not valid. The exception raised was <insert_2>. The active integration node state might not be as expected.
Response: See the following message or messages for further details of the error. If the problem persists, contact your IBM support center for assistance.

BIP3793: Service Federation proxy <insert_3> (uuid=<insert_2>) type <insert_1> successfully created.
Severity: 0 : Information
Explanation: The integration node received a configuration message containing an instruction to create a Service Federation proxy and successfully performed this action.
Response: No user action required.

BIP3794: Service Federation proxy <insert_2> (uuid=<insert_1>) successfully changed.
Severity: 0 : Information
Explanation: The integration node received a configuration message containing an instruction to change a Service Federation proxy and successfully performed this action.
Response: No user action required.

BIP3795: Request to change Service Federation proxy <insert_2> (uuid=<insert_1>): proxy does not exist.
Severity: 10 : Warning
Explanation: The integration node received a configuration message containing an instruction to change Service Federation proxy <insert_2> (uuid=<insert_1>) but this cannot be completed because the proxy does not exist.
Response: Correct the details of the proxy to be changed and resubmit the request. If the problem persists, contact your IBM support center.

BIP3796: Service Federation proxy <insert_2> (uuid=<insert_1>) successfully deleted.
Severity: 0 : Information
Explanation: The integration node received a configuration message containing an instruction to delete a Service Federation proxy and successfully performed this action.
Response: No user action required.

BIP3797: Request to report on Service Federation proxy <insert_2> (uuid=<insert_1>): proxy does not exist.
Severity: 10 : Warning
Explanation: The integration node received a configuration message containing an instruction to report on Service Federation proxy <insert_2> (uuid=<insert_1>) but this cannot be completed because the proxy does not exist.
Response: Correct the details of the proxy and resubmit the request. If the problem persists, contact your IBM support center.

BIP3798: A Service Federation proxy already exists with uuid <insert_1> (existing proxy label <insert_2>).
Severity: 20 : Error
Explanation: A request to create a new Service Federation proxy has been received. However, a proxy with uuid <insert_1> already exists. The existing proxy label is <insert_2>.
Response: Change the uuid of the new proxy and resubmit the create request.

BIP3799: Request to delete Service Federation proxy <insert_1>: proxy does not exist.
Severity: 10 : Warning
Explanation: The integration node received a configuration message containing an instruction to delete Service Federation proxy <insert_1> but this cannot be completed because the proxy does not exist.
Response: Correct the details of the proxy to be deleted and resubmit the request. If the problem persists, contact your IBM support center.

BIP3800: The SCAInput node <insert_2> has attempted to propagate a message with operation name <insert_1> which does not correspond to an output terminal of the same name.
Severity: 30 : Severe error
Response: On the SCAInput node, create a dynamic output terminal with the correct operation name.

BIP3801: An SCAAsyncResponse node with the identifier <insert_1> cannot find its corresponding SCAAsyncRequest node with Broker SCA definition <insert_2>. The SCAAsyncResponse node cannot receive any asynchronous response messages until it finds its corresponding Broker SCA definition on the SCAAsyncRequest node.
Severity: 30 : Severe error
Explanation: It is an error to deploy an SCAAsyncResponse node and corresponding SCAAsyncRequest node which use different Broker SCA definitions.
Response: Deploy the corresponding SCAAsyncRequest node with the correct Broker SCA definition.

BIP3802: An SCAAsyncResponse node with the identifier <insert_1> cannot find its corresponding SCAAsyncRequest node with SCA binding <insert_2>. The SCAAsyncResponse node cannot receive any asynchronous response messages until it finds its corresponding SCA binding on the SCAAsyncRequest node.
Severity: 30 : Severe error
Explanation: It is an error to deploy an SCAAsyncResponse node and corresponding SCAAsyncRequest node which use different SCA bindings.
Response: Deploy the corresponding SCAAsyncRequest node with the correct SCA binding.

BIP3803: An attempt was made to deploy an SCAAsyncRequest node or SCAAsyncResponse node with an invalid unique identifier <insert_1>.
Severity: 30 : Severe error
Explanation: It is an error to deploy an SCAAsyncRequest node or SCAAsyncResponse node with an invalid unique identifier. The identifier must not be zero length.
Response: Correct the error and redeploy the flow.

BIP3804: The SCARequest node or SCAAsyncRequest node <insert_1>, which is using a Web services SCA binding, encountered an error while processing the outbound SOAP request.
Severity: 20 : Error
Explanation: An internal error occurred during the processing of the SOAP request.
Response: See previous error messages to determine the cause of the error.

BIP3805: An SCAAsyncResponse node with the identifier <insert_1> cannot find its corresponding SCAAsyncRequest node. It has checked <insert_2> times for the corresponding node, and will continue checking. The SCAAsyncResponse node cannot receive any asynchronous response messages until it finds its corresponding SCAAsyncRequest node.
Severity: 20 : Error
Explanation: It is an error to deploy a SCAAsyncResponse node without its corresponding SCAAsyncRequest node.
Response: Deploy the corresponding SCAAsyncRequest node.

BIP3806: An attempt was made to deploy two SCAAsyncRequest nodes with the same unique identifier <insert_1> to the same integration server.
Severity: 30 : Severe error
Explanation: It is an error to deploy two SCAAsyncRequest nodes with the same unique identifier to the same integration server.
Response: Correct the error and redeploy the flow.

BIP3807: An attempt was made to deploy two SCAAsyncResponse nodes with the same unique identifier <insert_1> to the same integration server.
Severity: 30 : Severe error
Explanation: It is an error to deploy two SCAAsyncResponse nodes with the same unique identifier to the same integration server.
Response: Correct the error and redeploy the flow.

BIP3808: The SCAInput node <insert_1>, which is using a Web services SCA binding, encountered an error while validating an inbound message.
Severity: 20 : Error
Explanation: An internal error occurred during message validation.
Response: See previous error messages to determine the cause of the error.

BIP3809: The SCAInput node <insert_1>, which is using a Web services SCA binding, encountered an error while determining to which output terminal to propagate the message.
Severity: 20 : Error
Explanation: An internal error occurred during message processing.
Response: See previous error messages to determine the cause of the error.

BIP3810: The SCAInput node <insert_1>, which is using a Web services SCA binding, encountered an error while processing the inbound SOAP message.
Severity: 20 : Error
Explanation: An internal error occurred during message processing.
Response: See previous error messages to determine the cause of the error.

BIP3811: The SCAInput node <insert_1>, which is using a Web services SCA binding, encountered an error while initializing the environment.
Severity: 20 : Error
Explanation: An internal error occurred during initialization.
Response: See previous error messages to determine the cause of the error.

BIP3812: The SCAInput node <insert_1>, which is using a Web services SCA binding, encountered an error while processing the node properties.
Severity: 20 : Error
Explanation: An internal error occurred during the processing of node properties.
Response: See previous error messages to determine the cause of the error.

BIP3813: The SCAInput node <insert_1>, which is using a Web services SCA binding, encountered an error while propagating the inbound SOAP message to its output terminal.
Severity: 20 : Error
Explanation: An internal error occurred during message propagation.
Response: See previous error messages to determine the cause of the error.

BIP3814: The SCAInput node <insert_1>, which is using a Web services SCA binding, encountered an error while processing the inbound SOAP message header.
Severity: 20 : Error
Explanation: An internal error occurred during the processing of security information in the message header.
Response: See previous error messages to determine the cause of the error.

BIP3815: The SCAReply node <insert_1>, which is using a Web services SCA binding, encountered an error while initializing the environment.
Severity: 20 : Error
Explanation: An internal error occurred during initialization.
Response: See previous error messages to determine the cause of the error.

BIP3816: The SCAReply node <insert_1>, which is using a <insert_2> SCA binding, encountered an error while processing a reply message.
Severity: 20 : Error
Explanation: An error occurred during reply message processing.
Response: See previous error messages to determine the cause of the error.

BIP3817: The SCARequest node <insert_1>, which is using a Web services SCA binding, encountered an error while initializing the environment.
Severity: 20 : Error
Explanation: An internal error occurred during initialization.
Response: See previous error messages to determine the cause of the error.

BIP3818: The SCARequest node <insert_1>, which is using a Web services SCA binding, encountered an error while processing the node properties.
Severity: 20 : Error
Explanation: An internal error occurred during the processing of node properties.
Response: See previous error messages to determine the cause of the error.

BIP3819: The SCAAsyncRequest node <insert_1> encountered an error while processing the node properties.
Severity: 20 : Error
Explanation: An internal error occurred during the processing of node properties.
Response: See previous error messages to determine the cause of the error.

BIP3820: The SCAAsyncRequest node <insert_1>, which is using a <insert_2> binding, encountered an error while initializing the environment.
Severity: 20 : Error
Explanation: An internal error occurred during initialization.
Response: See previous error messages to determine the cause of the error.

BIP3821: The SCAAsyncResponse node <insert_1>, which is using a <insert_2> binding, encountered an error while processing the node properties.
Severity: 20 : Error
Explanation: An internal error occurred during the processing of node properties.
Response: See previous error messages to determine the cause of the error.

BIP3822: The SCAAsyncResponse node <insert_1>, which is using a <insert_2> SCA binding, encountered an error while processing an inbound response message.
Severity: 20 : Error
Explanation: An error occurred during message processing.
Response: See previous error messages to determine the cause of the error.

BIP3823: The SCAAsyncResponse node <insert_1>, which is using a Web services SCA binding, encountered an error while validating an inbound response message.
Severity: 20 : Error
Explanation: An internal error occurred during response message validation.
Response: See previous error messages to determine the cause of the error.

BIP3824: The message received at SCA node <insert_5> (binding <insert_6>) contains no data. (SQLSTATE <insert_2>)
Severity: 20 : Error
Explanation: The IBM Integration Bus node <insert_5> has received a message for writing to a queue, but the bit stream of the message is too short to be a valid message. This situation can occur when a message is built incorrectly by a Compute node.
Response: Check the message flow to determine whether the message is being built correctly. Correct the problem and redeploy.

BIP3825: A SCAAsyncResponse node with the identifier <insert_1> cannot not find its corresponding SCAAsyncRequest node. The number of checks so far is: <insert_2>. No messages can be received until the request node is available.
Severity: 20 : Error
Explanation: A SCAAsyncResponse node must be deployed with a corresponding SCAAsyncRequest node. The node will continue to check for the request node.
Response: Deploy the corresponding SCAAsyncRequest node.

BIP3826: A message without a valid reply identifier reached SCAReply node <insert_1>.
Severity: 20 : Error
Explanation: A valid SCA Reply Identifier is required for SCA Reply processing to be successful. The incoming message does not contain this information, and no SCA reply can be made.
Response: Provide the required SCA Reply Identifier in LocalEnvironment.Destination.SCA.Reply.ReplyIdentifier.

BIP3827: A message with more than one message body reached SCA node <insert_1> (binding <insert_6>). Extraneous body parser name is <insert_7>.
Severity: 20 : Error
Explanation: The IBM Integration Bus node <insert_5> has received a message for writing to a queue, but there is more than one message body present in the tree. This situation can occur when a message is built incorrectly by a Compute node.
Response: Modify previuos nodes to only create one message body and redeploy.

BIP3828: The inbound message is a one-way WSDL operation; no reply will be sent.
Severity: 0 : Information
Explanation: The message flow includes a SCAReply node <insert_1>, but incoming messages use a one-way Message Exchange Pattern (MEP), and no reply is expected.
Response: Remove the SCAReply node <insert_1> from the message flow.

BIP3829: SCARequest node <insert_1>, which is using a MQ SCA binding, did not receive a response message within the timeout period.
Severity: 20 : Error
Explanation: The SCARequest node sent a request message, and is configured to receive a response. However, the response message did not arrive before the specified timeout period elapsed.
Response: Check the logs on WebSphere Process Server to see why the response message was not sent. Possible reasons include: 1) The properties in the SCA Export component on WebSphere Process Server have been changed, and the response queue or response queue manager is different from that specified in the SCARequest node properties. In this case, export the Project Interchange file from WebSphere Integration Developer and import it into IBM Integration Bus. This import operation updates the Broker SCA Definition, which you can then use to re-configure the SCARequest node. 2) The interface used by the SCA Export has changed, and the request operation has been removed or renamed, but has not been updated in IBM Integration Bus. In this case, export the Project Interchange file from WebSphere Integration Developer and import it into IBM Integration Bus. This import operation updates the Broker SCA Definition, which you can then use to re-configure the SCARequest node. 3) The application running in WebSphere Process Server requires human intervention, which takes longer to complete than the specified timeout period on the SCARequest node. In this case, increase the timeout period specified on the SCARequest node.

BIP3830: The SCARequest or SCAAsyncRequest node <insert_2>, which is using an MQ SCA binding, could not find the specified operation <insert_1> in the interface that is defined in the Broker SCA Definition. The request message cannot be sent to WebSphere Process Server.
Severity: 20 : Error
Explanation: An operation specified in the Local Environment was not found in the interface that is defined in the Broker SCA Definition. The request message cannot be sent because the operation does not exist in the application that is running on WebSphere Process Server.
Response: Correct the value for the specified operation in the Local Environment. If necessary, re-export the project interchange file from WebSphere Integration Developer, and then import it into IBM Integration Bus. This import operation updates the Broker SCA Definition, which can then be used to reconfigure the SCARequest or SCAAsyncRequest node.

BIP3831: The SCAAsyncRequest node <insert_2> cannot be used to send a request message for a one-way operation <insert_1>.
Severity: 20 : Error
Explanation: An operation specified in the Local Environment is defined as a one-way operation in the Broker SCA Definition. The request message cannot be sent because SCAAsyncRequest node supports only request-response (two-way) operations.
Response: If you want to send a request for a one-way operation, use the SCARequest node. If the specified operation was wrong, correct the value for the operation in the Local Environment. If necessary, re-export the project interchange file from WebSphere Integration Developer, and then import it into IBM Integration Bus. This import operation updates the Broker SCA Definition, which can then be used to reconfigure the SCARequest or SCAAsyncRequest node.

BIP3832: Exception encountered while parsing the query string <insert_1> with CCSID <insert_2> and separator <insert_3>.
Severity: 20 : Error
Explanation: An attempt was made to parse the query string, but it contained invalid data.
Response: Other messages will give an indication of the context of this error.

BIP3833: Error converting the query string token <insert_1>.
Severity: 20 : Error
Explanation: An attempt was made to parse a query string token, but it contained invalid data.
Response: Other messages will give an indication of the context of this error.

BIP3834: The percent-encoded pair , <insert_1>, cannot be converted.
Severity: 20 : Error
Explanation: An attempt was made to convert a percent-encoded pair, but the pair was invalid.
Response: A percent-encoded pair must consist of two characters from the range: 0-9, A-F, a-f.

BIP3835: The web UI extension <insert_1> is installed and is available at <insert_2>.
Severity: 0 : Information
Explanation: The MQSI_ADDITIONAL_CONTEXT_ROOTS environment variable has been applied to install web extension <insert_1> at <insert_2>.
Response: No user action required.

BIP3836: An exception occurred when applying the MQSI_ADDITIONAL_CONTEXT_ROOTS environment variable because web UI extension <insert_1> does not exist.
Severity: 20 : Error
Explanation: An attempt was made to install a web UI extension that is defined in MQSI_ADDITIONAL_CONTEXT_ROOTS, but the defined directory does not exist or cannot be read.
Response: Ensure the required directory exists and can be read.

BIP3837: An exception occurred when applying the MQSI_ADDITIONAL_CONTEXT_ROOTS environment variable because URL <insert_1> is already used by web UI extension <insert_2> and so cannot be used by web UI extension <insert_3>.
Severity: 20 : Error
Explanation: An attempt was made to install a web UI extension that is defined in MQSI_ADDITIONAL_CONTEXT_ROOTS, but the URL is already used by another web UI extension.
Response: Change the MQSI_ADDITIONAL_CONTEXT_ROOTS environment variable so that each web UI extension uses a unique URL.

BIP3838: The specified WSDL binding <insert_1> could not be found in the supplied WSDL file <insert_2>.
Severity: 20 : Error
Explanation: The WSDL binding <insert_1> from the target namespace <insert_4> associated with shared library <insert_3> was not found in the WSDL file <insert_2>. This could be because the WSDL file is missing, invalid or corrupt.
Response: Determine the cause of the error and correct it. Ensure that the WSDL file is valid and that it validates correctly.

BIP3839: <insert_1> reply identifiers have expired for node <insert_2>.
Severity: 0 : Information
Explanation: Reply identifiers have expired and have been removed from the in-flight list. This might result in subsequent errors if processing of the reply messages is later attempted.
Response: Check why the replies have not been processed within the timeout period. If necessary, increase the asynchronous message handle timeout using the 'mqsichangeproperties' command: 'mqsichangeproperties [integrationNodeName] -e [integrationServerName] -o ComIbmSOAPHandleManager -n asyncHandleTimeoutSeconds -v [new timeout value]'

BIP3840: The Environment Variable <insert_1> was already set to something different to the value of the secureJNDIPropertiesFiles property in the DefaultWSRR Configurable Service. Therefore, the value specified by secureJNDIPropertiesFiles will not be used.
Severity: 10 : Warning
Explanation: The secureJNDIPropertiesFiles property in the DefaultWSRR was set to enable a Secure JNDI connection to the WSRR JMS Cache notification topic. However, the environment variable <insert_1> has all ready been set in a another location. To avoid breaking an existing configuration, the <insert_1> variable was not set. This action might lead to the WSRR JMS Cache connection failing.
Response: The secureJNDIPropertiesFiles property has been set, but can not be used for the WSRR JMS Cache connection. For more information on the configuration required to use the WSRR Cache Updates see the IBM Integration Bus product documentation.

BIP3841: Failed to setup any Connectors because more than one provider has been installed. Name of providers installed: <insert_1>.
Severity: 20 : Error
Explanation: Only one Connector can be installed at a given time.
Response: Check the Connector configurable services and ensure only one Connector is configured.

BIP3842: Failed to setup the Connector <insert_1> because the connectorClassName is missing from the configurable service.
Severity: 20 : Error
Explanation: The Connector configurable service called <insert_1> has the connectorClassName set to an invalid value.
Response: Ensure the Connector configurable service called <insert_1> has the connectorClassName set to a valid value.

BIP3843: Failed to setup any Connector.
Severity: 20 : Error
Explanation: See previous errors for the reason why no connectors were initialized. The integration node will continue to function but with out the provider function being available.
Response: Review the previous errors and correct any issues shown. The integration server will need to be restarted once any issue is resolved.

BIP3844: Failed to terminate the installed Connector <insert_1>.
Severity: 20 : Error
Explanation: See previous errors for the reason why the Connector failed to be terminated. The integration node will still be stopped.
Response: Review the previous errors and correct any issues shown.

BIP3845: Failed to find a connector <insert_1> to use with output session <insert_2>.
Severity: 20 : Error
Explanation: There are no connectors installed on the integration node that the output session can use.
Response: Ensure that the connector required by the node is installed on the integration node. Connector providers are installed by creating a MessagingProvider configurable service with details of the providers libraries.

BIP3846: The Connector jarsUrl <insert_1> is malformed.
Severity: 20 : Error
Explanation: The jarsUrl is not a valid set of directories.
Response: Ensure that the connector provider jarsUrl points to a correct list of directories containing jar files.

BIP3847: The Connector provider class <insert_1> can not be found in the jarsUrl path <insert_2>, in the shared classes directory or in the classpath.
Severity: 20 : Error
Explanation: The jar containing the Connector class must be available in the jarsUrlpath, in the shared classes directory or in the integration node classpath.
Response: Ensure that the Connector provider jarsUrl points to a jar file that contains the provider class.

BIP3848: The Connector class <insert_1> has no valid zero parameter constructor.
Severity: 20 : Error
Explanation: The Connector class must have a valid zero parameter constructor because it can not be created by the integration node integration server.
Response: Ensure that the messaging provider class is defined with a zero parameter constructor.

BIP3849: Failed to load the Connector <insert_1>.
Severity: 20 : Error
Explanation: Failed to load the Connector <insert_1>. See the previous error for the cause of the failure. The integration server will continue to operate but this this providers function will be disabled.
Response: Review the previous errors and correct which ever problems they report. The integration server will need to be restarted for the provider to be re-initialized.

BIP3850: Unexpected java exception thrown from the Connector method <insert_1>.
Severity: 20 : Error
Explanation: The Connector threw an unexpected type of exception. See previous errors for the detail of the java exception thrown.
Response: The Connector provider is throwing a type of exception that can not be handled by integration node. Contact the supplier of the Connector.

BIP3851: Failed to start input node called <insert_1>.
Severity: 20 : Error
Explanation: Failed to start the input node <insert_1>. Attempts will be made to start the node until it does start.
Response: Review previous messages for the cause of the failure to start the node.

BIP3852: The following connector type is not supported <insert_1>.
Severity: 20 : Error
Explanation: Change requests can only be made against connectors of type Input or Output.
Response: Ensure that either Input or Output is specified as the connector type.

BIP3853: There is no connector available of type <insert_1> called <insert_2>.
Severity: 20 : Error
Explanation: There is no input or output node using the connector called <insert_2>.
Response: Ensure that either the Input or Output connector specified is being used by a deployed node.

BIP3854: The connector factory <insert_1> is missing an attribute named <insert_2>.
Severity: 20 : Error
Explanation: A mandatory attribute <insert_2> was missing from a connector factory.
Response: Ensure that the attribute <insert_2> is specified and try again.

BIP3855: The callback function for the JavaScript request interaction <insert_1> was called with the wrong number of arguments: <insert_2>.
Severity: 20 : Error
Explanation: The callback function for a JavaScript request interaction was called with the wrong number of arguments; only 1 or 2 are valid.
Response: Ensure that the callback function is called with only response data and, optionally, an error.

BIP3856: A JavaScript error occurred: <insert_1>.
Severity: 20 : Error
Explanation: An error occurred while executing JavaScript code.
Response: Check the error messages that follow to determine why the exception was generated, and take action as suggested by those messages.

BIP3857: The JavaScript request connector <insert_1> timed out while waiting for a response.
Severity: 20 : Error
Explanation: A request was made by a JavaScript request connector, but the response was not received in the required time period.
Response: Check the error messages that follow to determine why the exception was generated, and take action as suggested by those messages.

BIP3858: The SalesforceRequest node received error code <insert_1> while performing the <insert_2> operation. Error: <insert_3>.
Severity: 20 : Error
Explanation: An error was received when establishing the connection to Salesforce or performing the Salesforce operation.
Response: Check the error information to determine why the error occurred and take the appropriate action to resolve the error. The error code might be a Salesforce error code.

BIP3859: The property <insert_1>=<insert_2> supplied to the SalesforceRequest node is invalid.
Severity: 20 : Error
Explanation: A node property or a local environment property supplied to the SalesforceRequest node does not have a valid value.
Response: Use the information in the message and any preceding error messages to determine why the error was generated, and take action to resolve the error.

BIP3860: The SalesforceRequest node received data that was not in JSON format while it was performing the <insert_1> operation.
Severity: 20 : Error
Explanation: A JSON message was expected as input to the SalesforceRequest node. The message body contained data that was not in JSON format, so the SalesforceRequest node was unable to perform the <insert_1> operation.
Response: Check that a JSON message body is passed to the SalesforceRequest node.

BIP3861: A Salesforce ID must be supplied to the SalesforceRequest node when performing the <insert_1> operation, but no ID was provided.
Severity: 20 : Error
Explanation: A Salesforce ID must be specified in LocalEnvironment.Destination.Salesforce.Request.id, in order to perform the <insert_1> operation.
Response: Check that the Salesforce ID is set in the correct location in the local environment before the message is processed by the SalesforceRequest node.

BIP3862: The property <insert_1> supplied to the SalesforceRequest node must have one key with a valid value.
Severity: 20 : Error
Explanation: The property <insert_1> is incorrectly specified. It must contain one key and the value for the key must be of the correct type.
Response: Verify that the property has only one key and ensure that the value is of the correct type and meets any restrictions on valid values.

BIP3863: The <insert_2> operation was sent to Salesforce for object <insert_3> with Salesforce ID <insert_1>, but no Salesforce record could be found with that ID.
Severity: 20 : Error
Explanation: The Salesforce <insert_3> record with ID <insert_1> could not be found. Either the specified record does not exist for that object in Salesforce or an incorrect Salesforce ID was specified.
Response: Check that the record exists in Salesforce for the object and, if it does, ensure that you have specified the correct Salesforce ID in your message flow.

BIP3864: The SalesforceRequest node received data that was a JSON array while it was performing the <insert_1> operation, but a JSON object was expected. The request cannot be sent to Salesforce.
Severity: 20 : Error
Explanation: A JSON object was expected as input to the SalesforceRequest node. The JSON.Data element in the message tree contained data that was a JSON array, so the SalesforceRequest node was unable to process the <insert_1> operation.
Response: Ensure that the JSON message body that is passed to the SalesforceRequest node is a JSON object and not a JSON array.

BIP3865: A JavaScript exception <insert_2> was caught in module <insert_3> at line <insert_4>, offset <insert_5>-<insert_6>. Stack: <insert_7>.
Severity: 20 : Error
Explanation: An exception occurred while executing JavaScript module <insert_3> which was not handled within the module and was caught by Node.js.
Response: Use the information contained in the message to identify the cause and rectify the failure. If the problem persists, contact your IBM support center.

BIP3866: An identifier must be supplied to the SalesforceRequest node when performing the <insert_1> operation, but none was provided.
Severity: 20 : Error
Explanation: Either a Salesforce ID must be specified in LocalEnvironment.Destination.Salesforce.Request.id or in the message body, or an external ID must be specified in LocalEnvironment.Destination.Salesforce.Request.externalId, in order to perform the <insert_1> operation.
Response: Check that an identifier is set in the correct location in the local environment or message body before the message is processed by the SalesforceRequest node.

BIP3867: The <insert_2> operation on the <insert_3> object, which was issued by the SalesforceRequest node to <insert_4>, did not complete within the <insert_1> millisecond timeout period.
Severity: 20 : Error
Explanation: The SalesforceRequest node did not receive a response from <insert_4> within the required <insert_1> millisecond timeout period.
Response: Verify that there are no connectivity problems to Salesforce at the <insert_4> location. If the problem is intermittent, consider increasing the timeout value or reducing the amount of data being exchanged with Salesforce.

BIP3868: The LoopBackRequest node received error code <insert_1> while performing the <insert_2> operation. Error: <insert_3>.
Severity: 20 : Error
Explanation: An error was received when establishing the connection to the configured LoopBack connector or performing the requested operation.
Response: Check the error information to determine why the error occurred and take the appropriate action to resolve the error. The error code might be a LoopBack connector error code.

BIP3869: The property <insert_1>=<insert_2> supplied to the LoopBackRequest node is invalid.
Severity: 20 : Error
Explanation: A node property or a local environment property supplied to the LoopBackRequest node does not have a valid value.
Response: Use the information in the message and any preceding error messages to determine why the error was generated, and take action to resolve the error.

BIP3870: The LoopBackRequest node received data that was not in JSON format while it was performing the <insert_1> operation.
Severity: 20 : Error
Explanation: A JSON message was expected as input to the LoopBackRequest node. The message body contained data that was not in JSON format, so the LoopBackRequest node was unable to perform the <insert_1> operation.
Response: Check that a JSON message body is passed to the LoopBackRequest node.

BIP3871: A LoopBack 'Id' or 'externalId' must be supplied to the LoopBackRequest node when performing the <insert_1> operation, but neither was provided.
Severity: 20 : Error
Explanation: A LoopBack 'Id' or 'externalId' must be specified in 'LocalEnvironment.Destination.Loopback.Request', in order to perform the <insert_1> operation.
Response: Check that the LoopBack 'Id' or 'externalId' is set in the correct location in the local environment before the message is processed by the LoopBackRequest node.

BIP3872: The property <insert_1> supplied to the LoopBackRequest node must have one key with a valid value.
Severity: 20 : Error
Explanation: The property <insert_1> is incorrectly specified. It must contain one key and the value for the key must be of the correct type.
Response: Verify that the property has only one key and ensure that the value is of the correct type and meets any restrictions on valid values.

BIP3873: The <insert_2> operation was sent to the configured LoopBack connector for object <insert_3> with LoopBack ID <insert_1>, but no record could be found with that ID.
Severity: 20 : Error
Explanation: The LoopBack <insert_3> record with ID <insert_1> could not be found. Either the specified record does not exist for that object in the LoopBack connector or an incorrect LoopBack ID was specified.
Response: Check that the record exists in the configured LoopBack connector for the object and, if it does, ensure that you have specified the correct LoopBack ID in your message flow.

BIP3874: The LoopBackRequest node received data that was a <insert_1> while it was performing the <insert_2> operation, but a JSON object is required. The request cannot be sent to the LoopBack connector.
Severity: 20 : Error
Explanation: A JSON object is required as input to the LoopBackRequest node. The JSON.Data element in the message tree contained data that was a <insert_1>, so the LoopBackRequest node was unable to process the <insert_2> operation.
Response: Ensure that the JSON message body that is passed to the LoopBackRequest node is a valid JSON object.

BIP3875: An identifier must be supplied to the LoopBackRequest node when performing the <insert_1> operation, but none was provided.
Severity: 20 : Error
Explanation: Either a LoopBack ID must be specified in LocalEnvironment.Destination.Loopback.Request.id or in the message body, or an external ID must be specified in LocalEnvironment.Destination.Loopback.Request.externalId, in order to perform the <insert_1> operation.
Response: Check that an identifier is set in the correct location in the local environment or message body before the message is processed by the LoopBackRequest node.

BIP3876: The <insert_2> operation on the <insert_3> object, issued by the LoopBackRequest node, did not complete within the <insert_1> millisecond timeout period.
Severity: 20 : Error
Explanation: The LoopBackRequest node did not receive a response from the configured LoopBack connector within the required <insert_1> millisecond timeout period.
Response: Verify that there are no connectivity problems to the configured LoopBack connector. If the problem is intermittent, consider increasing the timeout value or reducing the amount of data being exchanged with LoopBack.

BIP3877: The <insert_1> file <insert_2> cannot be loaded. Error details: <insert_3>.
Severity: 20 : Error
Explanation: The <insert_1> file in the Integration node workpath location cannot be read or does not have valid content.
Response: Use the information in the message to resolve the LoopBackRequest node configuration error.

BIP3878: The data source <insert_1> cannot be located in the datasources.json file <insert_2>.
Severity: 20 : Error
Explanation: The datasources.json file in the Integration node workpath can be read as valid JSON but does not contain a stanza for the data source name configured on the LoopBackRequest node.
Response: Use the information in the message to resolve the LoopBackRequest node configuration error.

BIP3879: The LoopBackRequest node received an error from LoopBack when attempting to connect to the data source name <insert_1>. Detail: <insert_2>.
Severity: 20 : Error
Explanation: An error was received when establishing the connection to the configured LoopBack connector data source.
Response: Check the error information to determine why the error occurred and take the appropriate action to resolve the error. The error detail is a LoopBack connector error message.

BIP3880: The LoopBackRequest node for the data source name <insert_1> has loaded a LoopBack model definition file <insert_2> which sets the object name <insert_3>.
Severity: 10 : Warning
Explanation: The LoopBack connector will interact with the object named <insert_3> as a result of loading the model definition file <insert_2>.
Response: Check the object name <insert_3> is correct for the data source name <insert_1>.

BIP3881: The Kafka connector requires that the property <insert_1> is supplied and contains a valid value.
Severity: 20 : Error
Explanation: The property <insert_1> was not provided.
Response: Verify that the property has been correctly specified.

BIP3882: The value <insert_2> supplied for property <insert_1> to the Kafka connector is invalid.
Severity: 20 : Error
Explanation: The value for property <insert_1> is invalid.
Response: Correct the supplied value.

BIP3883: The Kafka client failed to connect to the Kafka server as the security credentials <insert_1> have not been configured for the Integration Server.
Severity: 20 : Error
Explanation: The Kafka client requested a userid and password in order to authenticate the connection to the Kafka server but no Kafka security credentials have been configured for the Integration Server.
Response: Use the mqsisetdbparms command to configure the security credentials for the Integration server using the resource name <insert_1>.

BIP3884: The Kafka connector received a security credential of a type <insert_1> which is not supported by this connector.
Severity: 20 : Error
Explanation: During the initialization of the Kafka connector it received a security credential of type <insert_1> which is not supported by the connector.
Response: None.

BIP3885: The Kafka connector received the security identity <insert_1> which is different from the security identity <insert_2> which is already in use.
Severity: 20 : Error
Explanation: An instance of a Kafka connector was created which has attempted to use a different security identity <insert_1> from the security identity <insert_2> already used by an existing instance of the Kafka connector.
Response: In order to change the security identity used by a Kafka connector then all previous instances of the connector must be stopped before the new connector instance is created.

BIP3886: Kafka connector unable to release use of security identity <insert_1>.
Severity: 20 : Error
Explanation: The Kafka connector attempted to release its use of security identity <insert_1> but the security identity is not in use by this connector.
Response: None.

BIP3887: The connection for Kafka consumer <insert_1> on topic <insert_2> to the Kafka server has been reinitialised following a connection error.
Severity: 10 : Warning
Explanation: An error occurred which required that the connection to the Kafka server was restarted. When this occurs the consumer position within the log of messages is reset to the last committed position.
Response: None.

BIP3888: The Logmet connector for the Bluemix logging service encountered a communication issue when sending data to <insert_1>. Error details: <insert_2>
Severity: 20 : Error
Explanation: The Logmet connector for the Bluemix logging service cannot complete a data send operation due to the reported error.
Response: Verify that the Bluemix logging service is available. Review the configuration properties by using the 'mqsireportbluemixreporting' command. Alter values by using the 'mqsichangebluemixreporting' command, and then restart the integration server.

BIP3889: The Logmet connector for Bluemix logging service requires that the property <insert_1> is supplied and contains a valid value.
Severity: 20 : Error
Explanation: The property <insert_1> was not provided with a valid value.
Response: Verify that the Bluemix logging service properties have been correctly specified.

BIP3890: Failed to initialise Kafka input connector for client <insert_2>. Reason <insert_1>.
Severity: 20 : Error
Explanation: Initialising the Kafka input connector failed with reason <insert_1>. Possible causes are:
1) None of the Kafka servers defined in 'Bootstrap Servers' property can be contacted.
2) If using an SSL connection, the SSL configuration is incorrect.
3) The Kafka client could not be loaded.
Response: Verify the Kafka servers are available at tha addresses specified in the 'Bootstrap Servers' property. If connecting to Kafka using an SSL connection, verify the SSL configuration properties match those required by the Kafka server. If connecting to Kafka using an SSL connection and have configured a SSL truststore, verify the truststore contains certificates which can validate those provided by the Kafka server. Further information on the cause of the failure may be available by enabling more detailed logging from the Kafka client in the log4j properties file.

BIP3891: The Kafka input connector was unable to subscribe to topic <insert_1> on Kafka server at address <insert_2>. Explanation <insert_3>.
Severity: 20 : Error
Explanation: The Kafka input connector attempted to subscribe to the topic <insert_1> but no response was received within the timeout period. Possible reasons for this are:
1) The Kafka server is not running at the server address.
2) The security credentials supplied are invalid.
The Kafka input connector will retry the operation.
Response: If the problem persists, investigate and rectify the cause of the failure using the information in the message explanation and retry the operation. Further information on the cause of the failure may be available by enabling more detailed logging from the Kafka client by modifying the log4j properties file.

BIP3892: Request to receive messages from the Kafka topic <insert_1> failed. Explanation <insert_3>.
Severity: 20 : Error
Explanation: The Kafka input connector requested to receive messages from Kafka but no response was received. A previous request to contact the Kafka server succeeded so possible causes are:
1) The topic no longer exists.
2) The Kafka server is no longer running at the server address.
3) The security credentials supplied are no longer valid.
The Kafka input connector will retry the operation.
Response: If the problem persists, investigate and rectify the cause of the failure using the information in the message explanation and retry the operation. Further information on the cause of the failure may be available by enabling more detailed logging from the Kafka client by modifying the log4j properties file.

BIP3893: The Kafka publish operation failed because details for topic <insert_1> could not be retrieved from the Kafka server at address <insert_2>. Explanation <insert_3>.
Severity: 20 : Error
Explanation: The Kafka output connector attempted to retrieve meta-data information for the topic <insert_1> but no response was received. Possible reasons for this are
1) The security configuration or the security credentials are invalid.
2) The topic does not exist.
Response: Investigate and rectify the causes of the failure using the information in the message explanation and retry the operation. Further information on the cause of the failure may be available by enabling more detailed logging from the Kafka client by modifying the log4j properties file.

BIP3894: Request to publish message to the Kafka topic <insert_1> failed. Explanation <insert_3>.
Severity: 20 : Error
Explanation: The Kafka output connector attempt to publish a message to Kafka but no response was received. A previous request to connect to the Kafka server succeeded so possible causes are:
1) The topic no longer exists.
2) The Kafka server is no longer running at the server address.
3) The security credentials supplied are no longer valid.
Response: Investigate and rectify the cause of the failure using the information in the message explanation and retry the operation. Further information on the cause of the failure may be available by enabling more detailed logging from the Kafka client by modifying the log4j properties file.

BIP3895: Failed to initialise Kafka output connector. Reason <insert_1>.
Severity: 20 : Error
Explanation: Initialising the Kafka output connector failed with reason <insert_1>. Possible causes are:
1) None of the Kafka servers defined in 'Bootstrap Servers' property can be contacted.
2) If using an SSL connection, the SSL configuration is incorrect.
3) If using SASL authentication, the credentials are incorrectly configured.
4) The Kafka client could not be loaded.
Response: Verify the Kafka servers are available at tha addresses specified in the 'Bootstrap Servers' property. If connecting to Kafka using an SSL connection, verify the SSL configuration properties match those required by the Kafka server. If connecting to Kafka using an SSL connection and have configured a SSL truststore, verify the truststore contains certificates which can validate those provided by the Kafka server. Further information on the cause of the failure may be available by enabling more detailed logging from the Kafka client in the log4j properties file.

BIP3896: Kafka message <insert_2> on topic <insert_1> received for client <insert_3> could not be processed because the consumer node was unable to confirm receipt of the message to the Kafka server.
Severity: 10 : Warning
Explanation: This situation can occur when the message offset position for the consumer is being committed on the Kafka server and the time that is taken to begin processing a message exceeds the session timeout value. The consumer will be automatically restarted and continue processing messages.
Response: If consuming messages in batches, consider reducing the batch size to reduce the time between requests for messages to the Kafka server, or increase the Session Timeout value that is defined for the Kafka consumer node.

BIP3897: Failed to commit message position <insert_2> on topic <insert_1> for client id <insert_3> to Kafka due to exception <insert_4>.
Severity: 20 : Error
Explanation: An exception occurred when the message flow attempted to commit the processing of a message to the Kafka server.
Response: If the problem persists, investigate and rectify the cause of the failure using the information in the message and retry the operation. Further information on the cause of the failure may be available by enabling more detailed logging from the Kafka client by modifying the log4j properties file.

BIP3898: The value supplied for the Session timeout property (<insert_1>) is invalid as it must be less than the value supplied for the Connection timeout property (<insert_2>).
Severity: 20 : Error
Explanation: The The value <insert_1> supplied for the Session timeout property must be less than the value of <insert_2> supplied for the Connection timeout property.
Response: Alter the value of either the Session timeout property or the Connection timeout property so that the value of the Session timeout property is less than the value of the Connection timeout property.

BIP3899: The Kafka input connector was unable to retrieve the details for topic <insert_1>.
Severity: 20 : Error
Explanation: The Kafka input connector attempted to retrieve details for the topic <insert_1> but no details were received from the Kafka server. The Kafka input connector will retry the operation.
Response: Verify the topic <insert_1> exists on the Kafka server and if security credentials are required to access the topic that the provided credentials have sufficient authority.

BIP3901: Exception condition detected on input node <insert_1>.
Severity: 0 : Information
Explanation: The input node <insert_1> detected an error whilst processing a message. The default message recovery processing of the node will have been invoked. The message being processed may have been reinstated on the input device or external software resource which provides the input data. This will be dependant on the capabilities of such devices or resources and, in the case of user-defined input nodes, on the features of the node itself. Other messages may be associated with this message which further describe the error condition.
Response: Check the error messages which follow to determine why the exception was generated, and take action as described by those messages.

BIP3903: Node (class=<insert_1>, name=<insert_2>) propagating to <insert_3> terminal.
Severity: 0 : Information
Explanation: The specified node is about to propagate a message to the specified terminal.
Response: No user action required. This is an information message.

BIP3904: Invoking the evaluate() method of node (class=<insert_1>, name=<insert_2>, label=<insert_3>).
Severity: 0 : Information
Explanation: About to pass a message to the evaluate() method of the specified node.
Response: No user action required.

BIP3905: Invoking the cniEvaluate() implementation function of node (class=<insert_1>, name=<insert_2>).
Severity: 0 : Information
Explanation: About to pass a message to the cniEvaluate() implementation function of the specified node.
Response: No user action required.

BIP3906: The node <insert_2> failed to navigate to the message location specified. The location specified was: <insert_1>.
Severity: 30 : Severe error
Explanation: Ensure that the location <insert_1> is valid for the message tree where it is used.
Response: Correct the specified message location.

BIP3907: Message received and propagated to <insert_2> terminal of input node <insert_1>.
Severity: 0 : Information

BIP3908: The field reference <insert_1> could not be used to resolve the data location in the incoming message.
Severity: 20 : Error
Explanation: An attempt was made to use the specified field reference to resolve a data location in the incoming message. However the resulting data location failed to resolve to a location in the incoming message tree that contains data that can be processed by the node.
Response: Review the data location property on the node and make sure that it points to a valid location.

BIP3909: The field reference <insert_1> could not be used to construct an outgoing message.
Severity: 20 : Error
Explanation: The output data location on the node could not be used to construct an outgoing message.
Response: Review the output data location property on the node and make sure that it points to a valid location in the outgoing tree.

BIP3910: Input node <insert_1> has retried a message the maximum number of times. The message is now propagated to the failure terminal.
Severity: 0 : Information
Explanation: An input message has failed normal propagation, and has also failed to be propagated to the catch terminal (if one is attached to the node). The message has been retried according to the retry properties and has exceeded the maximum number of retries specified. The message is now be propagated to the failure terminal. If you have not defined retry properties for this node, the message is propagated to the failure terminal after the first failure.
Response: No action is required. The message will be propagated to the failure terminal. If it is not attached, or if the propagation fails, the message will follow the "mark as failed" processing that is appropriate for the node.

BIP3911: The input node <insert_1> detected an error while processing a message and the processing of the failure resulted in a further error.
Severity: 20 : Error
Explanation: Previous messages will have indicated cause of the original error, and following messages will indicate the cause of this later error.
Response: Check the error messages that follow to determine why the exception was generated, and take action as suggested by those messages.

BIP3912: Message flow <insert_1> emitted a monitoring event of type <insert_2> from node <insert_3>.
Severity: 0 : Information

BIP3913: No default transaction id available on this transport. Monitoring event will not contain a local transaction id. Message flow <insert_1>, node <insert_2>.
Severity: 0 : Information
Explanation: The message flow emitted a monitoring event, but it was unable to populate the local transaction id in the event because the transport does not provide a suitable field.
It may not be possible for a monitoring application to correlate messages which were emitted as part of the same transaction.
Response: If the message flow is not associated with a monitoring profile then create a monitoring profile and associate it with the message flow using the mqsichangeflowmonitoring command.
Edit the monitoring profile to specify a query for the local transaction id.

BIP3914: No bitstream available for this transport. Monitoring event will not contain the bitstream. Message flow <insert_1>, node <insert_2>.
Severity: 0 : Information
Explanation: The message flow emitted a monitoring event, but it was unable to populate the bitstreamData element in the event because the transport does not provide bitstream.
Response: If the message flow is not associated with a monitoring profile then create a monitoring profile and associate it with the message flow using the mqsichangeflowmonitoring command.
Edit the monitoring profile and set the bitstream encoding to 'None'.

BIP3915: Message flow <insert_1> failed to emit a monitoring event from event source <insert_2>.
Severity: 0 : Information
Explanation: The message flow tried to emit a monitoring event, but failed.
Response: Check the error messages that follow this message to determine what caused the problem, and take action as appropriate.

BIP3916: The query expression <insert_1> given for event name returned an empty result.
Severity: 20 : Error
Explanation: The query returned an empty result. An event must have a valid event name.
Response: Check that the query expression is correct.

BIP3917: Message flow <insert_1> received an empty result for query expression <insert_2> when generating the event payload at event source <insert_3>.
Severity: 10 : Warning
Explanation: The query returned an empty result. No application data was added to the event payload.
Response: If an empty result is not expected, check that the query expression is correct.

BIP3918: Message flow <insert_1> failed to load event sources from configurable service monitoring profile <insert_2>. All event sources for the message flow have been deleted. Monitoring events will not be produced for the message flow.
Severity: 10 : Warning
Explanation: Errors occurred when the configurable service monitoring profile <insert_2> for message flow <insert_1> was loaded. All event sources for the message flow have been deleted. Monitoring events will not be produced for the message flow.
Response: Check the configurable service monitoring profile source and correct it as necessary.

BIP3919: Message flow <insert_1> emitted a monitoring event of type <insert_2> from node <insert_3>. The message was not coordinated with any unit of work.
Severity: 0 : Information
Explanation: The message flow emitted a monitoring event that is immediately available to the monitoring application, even if a long-running unit of work is in progress.
Response: No action is required.

BIP3920: Message flow <insert_1> emitted a monitoring event of type <insert_2> from node <insert_3>. The event was coordinated with the message flow transaction.
Severity: 0 : Information
Explanation: The message flow emitted a monitoring event that will be available when the message flow's unit of work is committed. If the message flow fails, this event will not become available, unless it is a transaction start event in which case it will be included in a separate unit of work used for events marked as independent.
Response: No action is required.

BIP3921: Message flow <insert_1> emitted a monitoring event of type <insert_2> from node <insert_3>. The event was coordinated with a separate unit of work used for events marked as independent.
Severity: 0 : Information
Explanation: The message flow emitted a monitoring event that will be available when the message flow's independent unit of work is committed.
Response: No action is required.

BIP3922: Message flow <insert_1> was unable to emit monitoring events in an independent unit of work. The events were emitted out of syncpoint.
Severity: 0 : Information
Explanation: The message flow was instructed to emit one or more monitoring events in an independent unit of work. A new unit of work could not be started because an existing unit of work has not committed or rolled back. This could be because "Commit count" is greater than 1 or "Commit by message group" is set. The events were emitted, but they were not coordinated with any unit of work.
Response: No action is required.

BIP3923: Message flow <insert_1> has failed and rolled back its unit of work. The monitoring events included in the message flow unit of work will not be available.
Severity: 0 : Information
Explanation: The message flow's transaction has been backed out. This includes any monitoring events coordinated with the message flow unit of work, unless the event was a transaction start event, which will be included in a separate unit of work used for events marked as independent.
Response: No action is required.

BIP3924: Message flow <insert_1> has defined the monitoring event for event source address <insert_2> to be in the <insert_3> unit of work. This has been overridden to the <insert_4> unit of work.
Severity: 0 : Information
Explanation: The event unit of work option that you have chosen for the event cannot be used with the <insert_2> event source address, and the integration node has substituted the default event unit of work <insert_4> for this type of monitoring event. Typically, this occurs if the event unit of work is 'Message Flow' and the event is of type 'transaction.Rollback'. Rollback events must be either be 'None' or 'Independent'.
Response: No action is required.

BIP3925: Application data included in the monitoring event might not conform to the original XML Schema.
Severity: 0 : Information
Explanation: The monitoring event contains application data from an MRM message tree. Attributes in the original message are represented as elements in the monitoring event.
Response: If your message contains attributes, edit the XML Schemas used by the monitoring application so that attributes are defined as elements.

BIP3928: Invalid CICS COMMAREA length: <insert_1>.
Severity: 20 : Error
Explanation: An invalid CICS COMMAREA length was specified. The length must be an integer in the range 0-32767 and must equal the COMMAREA length of the CICS program to be run.
Response: Specify a valid CICS COMMAREA length in the range 0-32767.

BIP3929: Attribute <insert_1> has not been supplied for CICSRequest node <insert_2> in message flow <insert_3>.
Severity: 20 : Error
Explanation: The attribute <insert_1> is required for the CICSRequest node but has not been supplied.
Response: Specify attribute <insert_1> for this node.

BIP3930: The CICS Connection configurable service <insert_1> has not been found.
Severity: 20 : Error
Explanation: The CICS Connection configurable service <insert_1> was not found.
Response: Specify a valid CICS Connection configurable service name.

BIP3931: The CICSRequest node <insert_2> contains an invalid CICS server property <insert_1> in message flow <insert_3>.
Severity: 20 : Error
Explanation: The CICSRequest node CICS server property must be a valid URL or a configurable service name. If it is a URL, it must be made up of the structure [protocol]://[hostname]:[port]. Where 'protocol' can be either 'tcp' or 'ssl', 'hostname' must be the IPv4 TCP/IP address or DNS-resolvable hostname of the CICS host, and 'port' is the port number of the TCPIPSERVICE listener in CICS.
Response: Correct the CICSConnection configurable service cicsServer property or the CICSRequest node CICS server property.

BIP3932: The CICSConnection configurable service <insert_2> cicsServer property contains an invalid URL <insert_1>.
Severity: 20 : Error
Explanation: The CICSConnection configurable service <insert_2> cicsServer property must be a valid URL. The URL must be made up of the structure [protocol]://[hostname]:[port]. Where 'protocol' can be either 'tcp' or 'ssl', 'hostname' must be the IPv4 TCP/IP address or DNS-resolvable hostname of the CICS host, and 'port' is the port number of the TCPIPSERVICE listener in CICS.
Response: Correct the CICSConnection configurable service cicsServer property.

BIP3933: The CICSConnection configurable service <insert_2> gatewayURL property contains an invalid CICS Transaction Gateway URL <insert_1>.
Severity: 20 : Error
Explanation: The CICSConnection configurable service <insert_2> gatewayURL property must contain a valid CICS Transaction Gateway URL value. The URL must be made up of the structure [protocol]://[hostname]:[port]. Where 'protocol' can be either 'tcp' or 'ssl', 'hostname' must be the IPv4 TCP/IP address or DNS-resolvable hostname of the CICS Transaction Gateway daemon process, and 'port' is the port number of the protocol listener in CICS Transaction Gateway.
Response: Correct the CICSConnection configurable service gatewayURL property.

BIP3934: The field reference <insert_1> could not be used to retrieve a field from result message.
Severity: 20 : Error
Explanation: The result data location on the node could not be used to find a field in the result message. The most likely cause is that the field does not exist.
Response: Review the result data location property on the node and make sure that it points to a valid location in the result tree.

BIP3935: The integration node evaluated expression <insert_1> against the current record to decide whether to propagate the record. The result was <insert_2>.
Severity: 0 : Information
Explanation: If the result is true, the record is propagated to the rest of the flow. Otherwise, it is ignored.
Response: None

BIP3936: <insert_6> node <insert_1> in message flow <insert_2> has skipped a record in file <insert_3> at record number <insert_4>, offset <insert_5> and will not propagate the record to any terminal.
Severity: 0 : Information
Explanation: The <insert_6> node skipped a record because of properties set on the node. The node will not propagate the record to any terminal.
Response: No action is required.

BIP3937: Directory name <insert_1> has been rejected because it points to the root of the file system.
Severity: 0 : Information
Explanation: To safeguard your system, by default the file nodes cannot access files from the root of the file system. For example, the FileInput node deletes or moves all the files in the directory.
Response: Either change the directory being used, or set the environment variable MQSI_FILENODES_ALLOW_FILE_SYSTEM_ROOT to allow the root of the file system to be used.

BIP3938: An attempt was made to access the file <insert_1>, but it has already been opened by the FileRead <insert_2> node.
Severity: 20 : Error
Explanation: By default, when a FileRead node reads data from a file, it reads it in a streaming mode. Data is not read from the file until it is requested to by the parser. This error might occur in a node, for example, an MQOutput or Compute node, that is after the original FileRead node in the message flow. This error might also occur if an attempt is made to access data in the file and the file being used is deleted or archived by another FileRead node, or by an external process. For example, if one FileRead node reads data followed by another FileRead node archiving the file, and if the message is not fully parsed by the time the second FileRead node is reached, then a following MQOutput node can cause this error.
Response: Ensure the parser is not required to access the file after it has been deleted. This can be done by either configuring the "Parse timing" property in the Parser Options tab in the original FileRead node to "Immediate", so that the message is fully parsed before leaving the node; or ensuring that the message tree is not accessed after the file has been deleted (any copies of the tree can be accessed).

BIP3939: The file <insert_1> is too large (exceeds <insert_2> bytes) to process in the FileRead node when deleting or archiving the file.
Severity: 20 : Error
Explanation: If the FileRead node deletes or archives the file then it must read all the data into memory at once rather than streaming it as needed and it can not exceed <insert_2> bytes.
Response: To correct the problem either use a smaller file or read the file in with a FileRead node which does not delete or archive the file and then use another FileRead node to archive or delete the file once all the data has been processed. The second node must be after all other processing on the message in the flow has been completed or an error might occur due to the file no longer being available.

BIP3940: The map QName <insert_1> is invalid.
Severity: 20 : Error
Explanation: An invalid QName was supplied by a Mapping node.
Response: Check that the Mapping node properties and any Local Environment overrides are set correctly.

BIP3941: Error occurred whilst processing map <insert_1>.
Severity: 20 : Error
Explanation: The specified map resource was found, but could not be processed.
Response: Check that the map and its associated XML Schema resources are deployed correctly.

BIP3942: Internal error whilst processing map QName <insert_1>.
Severity: 20 : Error
Explanation: An internal error occurred whilst processing the specified map.
Response: Check that the map and its associated XML Schema resources are valid.

BIP3943: The map resource specified by QName <insert_1> cannot be located.
Severity: 20 : Error
Explanation: No map with the specified QName has been deployed.
Response: Check that all the required maps have been deployed.

BIP3944: The map script generation for QName <insert_1> has failed, with the following details: Location: <insert_3> Internal Error Number: <insert_2> Error Message: <insert_4>.
Severity: 20 : Error
Explanation: The generation of the map has failed.
Response: Review and resolve the problems indicated in the message from the map generation.

BIP3945: The map script generation for QName <insert_1> has failed. There is a problem with XPath expression <insert_2>; the details are: <insert_3>.
Severity: 20 : Error
Explanation: The generation of the map has failed.
Response: Review and resolve the problems indicated in the message from the map generation.

BIP3946: The map script generation for QName <insert_1> has failed, with the following details: <insert_2>.
Severity: 20 : Error
Explanation: The generation of the map has failed.
Response: Review and resolve the problems indicated in the message from the map generation.

BIP3947: The map processing for QName <insert_1> has failed, with the following details: <insert_2>.
Severity: 20 : Error
Explanation: The processing of the map has failed.
Response: Review and resolve the problems indicated in the message from the map processing.

BIP3948: The output domain <insert_1> for the Mapping node is not supported.
Severity: 20 : Error
Explanation: The processing of the map has failed because the output domain is not supported.
Response: Check the domain of the output message in the Mapping editor.

BIP3949: An error occurred during the processing of a message. The error message is <insert_1>.
Severity: 20 : Error
Explanation: An error occurred during message processing. Additional diagnostic information might be written to the user trace.
Response: Inspect the diagnostic information, and check the user trace for further information.

BIP3950: The Mapping node is about to run an SQL statement <insert_1> on DataSource <insert_2>.
Severity: 0 : Information
Explanation: The Mapping node is about to invoke an SQL statement through one of the Database transforms.
Response: Check the following messages to see the results of this SQL statement.

BIP3951: The Mapping node has run an SQL statement, which returned the following ResultSet Row <insert_1>.
Severity: 0 : Information
Explanation: The Mapping node has successfully returned data from the database.
Response: More ResultSet rows might be reported following this message.

BIP3952: The Mapping node has run an SQL statement <insert_1>, which has failed with the following exception: <insert_2>. The map has been configured to handle this exception within the Failure transform associated with this operation.
Severity: 10 : Warning
Explanation: The Mapping node has run an SQL statement, which threw an exception. The exception information was passed to the Failure transform in the map.
Response: Review the contents of the exception and ensure that there is appropriate processing of the Failure transform in the map.

BIP3953: The Mapping node has run an SQL statement <insert_1>, which has failed with the following exception: <insert_2>. The map has not been configured to handle this exception, so the processing of the map will be stopped and the exception will be thrown upstream from this node.
Severity: 10 : Warning
Explanation: The Mapping node has run an SQL statement, which threw an exception. The processing of the map will stop.
Response: Review the contents of the exception for further information.

BIP3954: An error occurred while processing map <insert_1>. A map file was found with the correct name, but it contained an incorrect namespace.
Severity: 20 : Error
Explanation: The specified map resource was found, but the content of the map file was defined with the wrong namespace.
Response: Ensure that the deployed map is using the correct namespace.

BIP3955: The Mapping node is entering the transform <insert_1>.
Severity: 0 : Information
Explanation: The Mapping node is about to process the named transform that is configured in the map.
Response: Check the following messages to see the progression of the mapping process.

BIP3956: The Mapping node is exiting the transform <insert_1>.
Severity: 0 : Information
Explanation: The Mapping node has finished processing the named transform that is configured in the map.
Response: Check the following messages to see the progression of the mapping process.

BIP3957: The Mapping node has bound the variable <insert_1> to the value <insert_2>.
Severity: 0 : Information
Explanation: The Mapping node has bound a variable. This variable is required by the transform that is being processed.
Response: Check the following messages to see when this variable goes out of scope.

BIP3958: The Mapping node has removed the binding of the variable <insert_1>.
Severity: 0 : Information
Explanation: The binding of this variable has gone out of scope. If this variable is used within a loop, then it will be re-bound with a new value when it is required.
Response: Check the following messages to see the progression of the mapping process.

BIP3959: The Mapping node is traversing the input tree by using the nodetest <insert_1> and the relationship <insert_2>. The number of matching elements is <insert_3>.
Severity: 0 : Information
Explanation: The Mapping node is traversing the input tree as part of the processing of the current transform.
Response: Check the following messages to see the progression of the mapping process.

BIP3960: The Mapping node is adding a new element with name <insert_1> into the output tree.
Severity: 0 : Information
Explanation: The Mapping node is adding a new element to the output tree, as defined in the transform that is being processed. If this element is assigned a value, then this assignment will be reported in an additional message.
Response: Check the following messages to see the progression of the mapping process.

BIP3961: The Mapping node is adding a new attribute with name <insert_1> and value <insert_2> into the output tree.
Severity: 0 : Information
Explanation: The Mapping node is adding a new attribute to the output tree, as defined in the transform that is being processed.
Response: Check the following messages to see the progression of the mapping process.

BIP3962: The Mapping node is assigning the value <insert_1> to the current output element.
Severity: 0 : Information
Explanation: The Mapping node is assigning the value of the current output element, as defined in the transform that is being processed.
Response: Check the following messages to see the progression of the mapping process.

BIP3963: The Mapping node is performing a deep copy of the input tree element <insert_1> into the output tree.
Severity: 0 : Information
Explanation: The Mapping node is copying the named input tree element, and all its descendents, into the output tree.
Response: Check the following messages to see the progression of the mapping process.

BIP3964: The Mapping node <insert_1> in message flow <insert_2> is about to process the mapping routine <insert_3>.
Severity: 0 : Information
Explanation: The Mapping node is about to process the named mapping routine.
Response: Check the following messages to see the progression of the mapping process.

BIP3965: The Mapping node <insert_1> in message flow <insert_2> has completed processing the mapping routine <insert_3> and is about to propagate the resultant message assembly.
Severity: 0 : Information
Explanation: The Mapping node has completed processing the named mapping routine.
Response: This message is reported for each message assembly that is generated by the mapping routine.

BIP3966: The Mapping node has evaluated the condition predicate <insert_1> to be 'true'. The Mapping node will now step into this 'if' transform.
Severity: 0 : Information
Explanation: The Mapping node is about to process the nested transforms in this 'if' block.
Response: Check the following messages to see the progression of the mapping process.

BIP3967: The Mapping node has evaluated the condition predicate <insert_1> to be 'false'. The next 'Else if' condition will be tested.
Severity: 0 : Information
Explanation: The Mapping node will not process the nested transforms in this 'if' block. The next condition in the current condition group will be tested.
Response: Check the following messages to see the progression of the mapping process.

BIP3968: The Mapping node has evaluated the condition predicate <insert_1> to be 'false'. The Mapping node will now step into the 'Else' transform.
Severity: 0 : Information
Explanation: The Mapping node will process the nested transforms within the 'Else' transform of this condition group.
Response: Check the following messages to see the progression of the mapping process.

BIP3969: The Mapping node has evaluated the condition predicate <insert_1> to be 'false'. The Mapping node will not process the nested transforms.
Severity: 0 : Information
Explanation: The Mapping node will not process the nested transforms within the condition group.
Response: Check the following messages to see the progression of the mapping process.

BIP3970: A Database Policy error was issued because the input into the database column <insert_1> is missing.
Severity: 20 : Error
Explanation: This error was configured via the Database Policy to be issued by the mapping node when it detected a missing input. Additional diagnostic information might be written to the user trace.
Response: Inspect the diagnostic information, and check the user trace for further information.

BIP3971: A Database Policy error was issued because the input into the database column <insert_1> is empty.
Severity: 20 : Error
Explanation: This error was configured via the Database Policy to be issued by the mapping node when it detected an empty input. Additional diagnostic information might be written to the user trace.
Response: Inspect the diagnostic information, and check the user trace for further information.

BIP3972: A Database Policy error was issued because the input into the database column <insert_1> is nil.
Severity: 20 : Error
Explanation: This error was configured via the Database Policy to be issued by the mapping node when it detected a nil input. Additional diagnostic information might be written to the user trace.
Response: Inspect the diagnostic information, and check the user trace for further information.

BIP3973: A data type conversion error occurred when attempting to convert the value <insert_1> to the SQL type <insert_2>.
Severity: 20 : Error
Explanation: This conversion error was created by the mapping node when assigning a value to a database column.
Response: Inspect the diagnostic information, and check the user trace for further information.

BIP3974: A data type conversion error occurred when attempting to convert a value <insert_1> to the type <insert_2>.
Severity: 20 : Error
Explanation: This error was created by the mapping node when performing data type conversion on a value in the input tree.
Response: Inspect the diagnostic information, and check the user trace for further information.

BIP3975: A data type conversion error occurred when attempting to convert a null value to the type <insert_1>.
Severity: 20 : Error
Explanation: This error was created by the mapping node when performing data type conversion on a null value in the input tree.
Response: Inspect the diagnostic information, and check the user trace for further information.

BIP3976: A database update operation was attempted without any specified column values. The datasource name is <insert_1> and table name is <insert_2>.
Severity: 20 : Error
Explanation: The mapping node attempted to update a database table without any column values. This could be caused by the database policy settings on each of the mapped inputs excluding all of the values.
Response: Inspect the diagnostic information, and check the user trace for further information.

BIP3977: A database insert operation was attempted without any specified column values. The datasource name is <insert_1> and table name is <insert_2>.
Severity: 20 : Error
Explanation: The mapping node attempted to insert a row to a database table without any specified column values. This could be caused by the database policy settings on each of the mapped inputs excluding all of the values.
Response: Inspect the diagnostic information, and check the user trace for further information.

BIP3978: The parameter count for procedure <insert_1> is <insert_2>. The required number of parameters is <insert_3>.
Severity: 20 : Error
Explanation: A stored procedure with that name exists, but it expects a different number of parameters. Additional diagnostic information might be written to the user trace.
Response: Ensure that the definition of the procedure in the database matches the parameter list that is provided in the mapping.

BIP3979: The procedure <insert_1> is not unique.
Severity: 20 : Error
Explanation: More than one stored procedure exists with that name and the correct number of parameters. Additional diagnostic information might be written to the user trace.
Response: Procedures are differentiated by number of parameters, regardless of type. Delete or rename one of the procedure definitions in the database.

BIP3980: The procedure <insert_1> cannot be found.
Severity: 20 : Error
Explanation: A stored procedure with that name is not present in the database. Additional diagnostic information might be written to the user trace.
Response: Ensure that the stored procedure is present in the database and matches the name and number of parameters that you are supplying in the mapping.

BIP3981: No database connection is available for the procedure to access datasource <insert_1>.
Severity: 20 : Error
Explanation: A procedure was invoked to access a datasource. No database connection was available and therefore the access failed. Additional diagnostic information might be written to the user trace.
Response: Verify that you have a valid JDBC connection configured as described in the IBM Integration Bus Mapping node documentation.

BIP3982: The parameter count for database access to datasource <insert_1> is <insert_2>. The required number of parameters is <insert_3>.
Severity: 20 : Error
Explanation: A database access (insert, update, delete or procedure call) was invoked with the wrong number of parameters. Additional diagnostic information might be written to the user trace.
Response: The mapping must place a value in each parameter that does not have a default value. Ensure that all database function parameters or columns have input elements that are present in the input message.

BIP3983: The shared library <insert_1> cannot be deployed. The shared library <insert_1> contains a map resource with the name <insert_2> However, shared library <insert_1> references shared library <insert_3> that also contains a map resource with the name <insert_2>.
Severity: 20 : Error
Explanation: A map resource must not exist more than once in a shared library and any referenced shared libraries.
Response: Remove the specified map resource from one of the specified shared libraries. Alternatively, rename the specified map resource in one of the specified shared libraries so that the map resource has a unique name.

BIP3984: The map script generation has reported a non-fatal message, with the following details: <insert_1>.
Severity: 0 : Information
Explanation: The generation of the map will continue.
Response: Review the the message from the map generation.

BIP3985: The node of type <insert_1> is not supported on this platform.
Severity: 20 : Error
Explanation: The integration node received a configuration message that contains an instruction to create a message flow node of type <insert_1>. The node cannot be created because the node type is not supported on this platform.
Response: Review the documentation and remove any nodes from your message flows that are not supported on the target platform.

BIP3989: The map script generation for <insert_1> has failed because the Message Set <insert_3> schema file cannot be loaded. Error Detail: <insert_4>.
Severity: 20 : Error
Explanation: The generation of the map has failed because a required schema file for a message model could not be located.
Response: The map generation requires XML schemas. Ensure the Message Set referenced by the map is deployed and XMLNSC is set as a supported domain in the message set.

BIP3990: The Mapping node will run the operation for the <insert_1> Transform passing the map name <insert_2> and key <insert_3>.
Severity: 0 : Information
Explanation: The Mapping node will invoke an operation through one of the Global Cache transforms.
Response: Check the following messages to see the results of this operation.

BIP3991: The Mapping node successfully ran an operation for the <insert_1> Transform, and will return the data <insert_2>.
Severity: 0 : Information
Explanation: The Mapping node will return data from a successful Global Cache operation.
Response: Check the following messages to see any mapping of the returned data.

BIP3992: The Mapping node failed to run an operation for the <insert_1> Transform due to the exception: <insert_2>. The map is configured to handle exceptions in a Failure transform.
Severity: 10 : Warning
Explanation: The Mapping node failed to run a Global Cache operation due to an exception. The exception will be passed to the Failure transform in the map.
Response: Review the contents of the exception and check the following messages to see any mapping of the exception data.

BIP3993: The Mapping node failed to run an operation for the <insert_1> Transform due to exception <insert_2>. The map is not configured with a Failure transform, so the exception will be thrown upstream from the node.
Severity: 20 : Error
Explanation: The Mapping node failed to run a Global Cache operation, due to an exception. The processing of the map will end as there is no Failure transform.
Response: Review the contents of the exception for further information.

BIP3994: The Mapping node was unable to run an operation for the <insert_1> Transform, because the mandatory parameter <insert_2> did not have a value. The processing of the map will end.
Severity: 20 : Error
Explanation: The Mapping node was unable to run a Global Cache operation, because the mapping to one of the mandatory parameters did not yield a data value.
Response: Review the mapping of the mandatory parameter and ensure a suitable value is provided.

BIP3995: The Mapping node was unable to run an operation for the <insert_1> Transform, because the parameters <insert_2> and <insert_3> both had a value. The processing of the map will end.
Severity: 20 : Error
Explanation: The Mapping node was unable to run a Global Cache operation, because the mapping provides values to parameters that are exclusive.
Response: Review the mapping of the optional parameters and ensure that only valid combinations are provided with values.

BIP3996: The Mapping node was unable to run an operation for the <insert_1> Transform, because the parameter <insert_2> requires that the <insert_3> has a value. The processing of the map will end.
Severity: 20 : Error
Explanation: The Mapping node was unable to run a Global Cache operation, because the mapping does not provide a value to a parameter that is required when using the another parameter.
Response: Review the mapping of the optional parameters and ensure that only valid combinations are provided with values.

BIP3997: The Mapping node cannot run an operation for the <insert_1> Transform due to exception <insert_2>. The map is not correctly configured to provide the required data to run the operation and will stop. An exception will be thrown upstream from the node.
Severity: 20 : Error
Explanation: The Mapping node failed to run a Global Cache operation, due to an exception. The processing of the map will end.
Response: Review the contents of the exception and the mapping of the Global Cache parameters to ensure that parameters are provided with required values.

BIP3998: The Mapping node successfully ran an operation for the <insert_1> Transform. No entry was matched.
Severity: 0 : Information
Explanation: The Mapping node will return no data from the Global Cache operation.
Response: If a matching entry is expected, check that the inputs to the transform and the contents of the Global Cache map are correct.