Resolving mapping and message reference problems when developing message flows

Advice for dealing with some common mapping and message reference problems that can arise 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

This practice is beneficial because the passed reference supports content assistance and validation for ESQL. The message type content properties open, or open defined are not used in validation, and the assumption is that this property is closed.

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.

Related concepts
Message flows overview
Related reference
Message flows
Mapping node
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2009Copyright IBM Corporation 1999, 2009.
Last updated : 2009-01-07 15:23:25

au16533_