Resolving problems when developing message flows
Advice for dealing with some common problems that can arise when developing message flows.
Resolving migration problems when developing message flows
Your migrated message flow project contains .msgnode files
You do not know whether you need to migrate the Version 2.1 IBM primitives
An error message is issued when you save a message flow that contains MQe nodes
MRM field is seen as NULL in Version 5.0 or later versions of the product
Resolving ESQL problems when developing message flows
A Routine not defined error message is issued in ESQL when you move a routine
The product fails to respond when you paste ESQL statements from Adobe Reader
You do not know how message flows handle the code page of ESQL files
You do not know the naming restrictions for ESQL procedures and functions
Error message BIP5431 is issued and the broker fails
You are unable to call Java from ESQL
Error message BIP3203 is issued: Format expression is not a valid FORMAT expression for converting expression to type
Error message BIP3204 is issued: Input expression does not match FORMAT expression. Parsing failed to match
Error message BIP3205 is issued: The use of a FORMAT expression is not allowed when converting
Resolving mapping and message reference problems when developing message flows
Resources that are referenced by the mapping file cannot be resolved
Errors are issued when you import table schemas into the Message Mapping editor
Warnings or errors are issued for message references
A $db:select out of scope error is generated when you map from a database source
Target is not referencing a valid variable warning when you set the value of a target
There are missing or unexpected targets in a message map
Error message BIP6118 is issued: The remaining bitstream is too small contain the indicated structure.
Error message BIP4680 is issued: Unsupported message domain encountered in mapping node.
Resolving implementation problems when developing message flows
Messages are directed to the Failure terminal of an MQInput node
Error message BIP2211 is issued in z/OS by the MQInput node
Messages enter the message flow but do not exit
Your execution group is not reading messages from the input queues
The DataFlowEngine terminates while processing messages
Your execution group hangs, or terminates with a core dump
Your XMLTransformation node is not working after deployment and errors are issued indicating that the style sheet could not be processed
Output messages are not sent to expected destinations
You experience problems when sending a message to an HTTP node's URL
Error message BIP5347 is issued on AIX when you run a message flow that uses a message set
Error message BIP2130 is issued with code page value of -1 or -2
QoS1 and QoS2 SCADA messages are not being processed
Resolving trace problems when developing message flows
You cannot determine which node is being referenced in your trace file
You cannot see any alerts when you change user trace
Resolving appearance problems when developing message flows
The task list does not update when you make corrections to your files
You rename a flow that contains errors, but the task list entries remain
Terminals on a subflow get out of sync as changes are made
Resolving other problems when developing message flows
The values of your promoted properties are lost after editing
The Message Flow editor experiences problems when opening a message flow, and opens in error mode
You get an exception when saving changes to a .tblxmi file
You do not know when to use the MQeMbMsgObject object