MQSeries.net :: View topic

thebeach · Posted: Fri Aug 12, 2005 9:34 am Post subject:

I've migrated from mqsi 2. 1to v5, and used mqsimigratemsgflows to convert the flows, but have encountered issues deploying the flow on v5.
The flows show no errors in the toolkit, but fail to deploy due to the ESQL errors below. The mqsimigratemsgflows report shows no errors.

Here's the ESQL:

CREATE COMPUTE MODULE "Example_V1_4_ST"
CREATE FUNCTION Main() RETURNS BOOLEAN
BEGIN
-- CALL CopyMessageHeaders();
-- CALL CopyEntireMessage();
RETURN TRUE;
END;

CREATE PROCEDURE CopyMessageHeaders() BEGIN
DECLARE I INTEGER 1;
DECLARE J INTEGER CARDINALITY(InputRoot.*[]);
WHILE I < J DO
SET OutputRoot.*[I] = InputRoot.*[I];
SET I = I + 1;
END WHILE;
END;

CREATE PROCEDURE CopyEntireMessage() BEGIN
SET OutputRoot = InputRoot;
END;
END MODULE;

CREATE FILTER MODULE "Example_V1_4_CH"
CREATE FUNCTION Main() RETURNS BOOLEAN
BEGIN
RETURN TRUE;
END;

END MODULE;

Here's the Error on deploying the bar file:

BIP2432E: (2, 1) : The correlation name 'CREATE' is not valid. Those in scope are: Environment, LocalEnvironment, Root, Body, Properties, ExceptionList, DestinationList.
The first element of a field reference must be a valid correlation name, from those in scope. This message may sometimes be due to an incorrectly formed or spelled expression which is not intended to be a field reference being parsed as if it were a field reference because the parser does not recognize it.
Correct the syntax of the expression and redeploy the message flow.

BIP4001E: Syntax error in SQL statements in filter node 'Example_V1_4.'.
The configuration of filter node Example_V1_4. failed due to errors in the SQL statement text. See the following messages for details of the error. The statement text was ' CREATE SCHEMA "" CREATE FILTER MODULE "Example_V1_4_CheckForDBError" CREATE FUNCTION Main() RETURNS BOOLEAN BEGIN RETURN TRUE; END; END MODULE; '.
The next error message will give specific details of where the error occurred in the statement text. Check the correct syntax for filter node SQL statements in the WebSphere Business Integration Message Brokers publications. Correct the statements and redeploy the configuration.

BIP4041E: Execution group 'Example' received an invalid configuration message. See the following messages for details of the error.
The message broker received an invalid configuration message and has not updated its configuration. This can arise as a result of errors in the specification of either message flows or message sets which the configuration manager was unable to detect. It can also result from a message flow requiring a type of node that is not supported by the broker installation, from the broker having become out of step with the configuration database or from other applications sending extraneous messages to the broker's configuration queues (SYSTEM.BROKER.ADMIN.QUEUE & SYSTEM.BROKER.EXECUTIONGROUP.QUEUE).

Advice appreciated!