MQSeries.net :: View topic - sysntax error while deploying..please resolve--very urgent

srinivas Raju · Posted: Mon Apr 02, 2007 2:44 am Post subject:

Dear Members,

i would like to thank all of you for giving valuable support.

Here i am getting syntax error while deploying message flow into execution group.

s/w i am using : WBIMB V6.0, MQ V6.0 DB V8.1 with FP5

My task is to create one message flow, which could get data from database and it has to update same in another database.
Todo this i have used mapping node and dataInsert node,MQINPUT.
i have created one message set also.

here i am using mapping node to get data from database and it will map same to mesasge set fields.

then dataInsert node will collect data from messageset and insert into another database.

also i have defined DSN for databases. i have imported sourse and target databases into workspace. the i did mapping also successfully.

then i have created bar file successfully, but while deploying this bar file into execution group it's showing some syntax errors.

the errors are as follows:
1).
BIP2402E: (.DBFLOW_Mapping, 425.32) : Syntax error : ';'.

The token caused a syntax error.

Correct the syntax of your expression and redeploy the message flow.

2)

BIP4001E: Syntax error in SQL statements in node 'DBFLOW.Mapping.ComIbmCompute'.

The configuration failed due to errors in the SQL statement text. See the following messages for details of the error

The following error messages will give specific details of the location and nature of the error. Check and correct the syntax of the SQL statements and redeploy.

3).

BIP4041E: Execution group 'dbexe' 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).

Check the relevant message flow and message set definitions, check that all necessary user-defined extensions are installed, perform a complete redeploy of the broker's configuration and ensure that no applications are writing to the broker's configuration queues.

please solve it for me

thanks for ur time
regs..Raju