Resolving ESQL problems when developing message flows

This topic contains advice for dealing with some common ESQL problems that can arise 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

The CAST function does not provide the expected DST offset for non-GMT time zones

Error message BIP3205 is issued: The use of a FORMAT expression is not allowed when converting

Related reference
ESQL reference
Message flows
Notices | Trademarks | Downloads | Library | Support | Feedback

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

au16532_