| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| BIP2432E deploy from wbimb 5.0.1 cm to mqsi 2.1 broker |
« View previous topic :: View next topic » |
| Author |
Message
|
| hornbeam123 |
 Posted: Thu Mar 10, 2005 8:26 am Post subject: BIP2432E deploy from wbimb 5.0.1 cm to mqsi 2.1 broker |
 |
|
Centurion
Joined: 01 Nov 2003
Posts: 101
|
BIP2432E: (2, 1) : The correlation name 'CREATE' is not valid.
I see there are many other post's on this error but these do NOT help me.
This is a flow migrated into Message Broker toolkit workbench - configmgr is now at wbimb 5.0 csd4 - broker is at mqsi 2.1 broker.
We are at this level on Solaris : application wmqi-upd7 WebSphere MQ Integrator V2.1.0 for Sun Solaris
- U495343
Extract from the start of the only node with esql :
CREATE COMPUTE MODULE "TestMirrorQ_Compute1"
CREATE FUNCTION main() RETURNS BOOLEAN BEGIN
DECLARE C INTEGER;
SET C = CARDINALITY(InputRoot.*[]);
DECLARE I INTEGER;
SET I = 1;
WHILE I < C DO
SET OutputRoot.*[I] = InputRoot.*[I];
SET I=I+1;
END WHILE;
-- Enter SQL below this line. SQL above this line might be regenerated, causing any modifications to be lost.
Please help - being able to maintain 2.1 broker flows with new wbimb cm etc is crucial.
 |
|
| Back to top |
|
 |
| fschofer |
| Posted: Thu Mar 10, 2005 8:55 am Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
Hi,
you have to set the toolkit ESQL code generation setting to version 2.1
an rebuild alle your projects.
This will prevent the generation of ESQL code which a 2.1 broker cannot understand.
Greetings
Frank |
|
| Back to top |
|
|
| hornbeam123 |
| Posted: Thu Mar 10, 2005 9:43 am Post subject: BIP2432E deploy from wbimb 5.0.1 cm to mqsi 2.1 broker |
|
|
Centurion
Joined: 01 Nov 2003
Posts: 101
|
| Thanks for your response Frank but how do you set this value ? |
|
| Back to top |
|
|
| fschofer |
| Posted: Thu Mar 10, 2005 2:41 pm Post subject: |
|
|
Knight
Joined: 02 Jul 2001
Posts: 524
Location: Mainz, Germany
|
http://publib.boulder.ibm.com/infocenter/wbihelp/topic/com.ibm.etools.mft.doc/ak17710_.htm?resultof=%22%45%53%51%4c%22%20%22%65%73%71%6c%22%20%22%67%65%6e%65%72%61%74%69%6f%6e%22%20%22%67%65%6e%65%72%22%20
| Quote: |
Setting the ESQL code generation level
You can specify the level of ESQL runtime code that is generated when you add a message flow to a bar file:
If your ESQL code includes references to databases, you can specify what schema name is used to identify the database tables when the runtime code is generated.
The code that is generated must be compatible with the broker to which the bar file is deployed. If you have brokers at Version 2.1 and Version 5.0 levels in your broker domain, you must ensure that the message flows that you deploy to a broker can be executed by that broker.
To change the ESQL code generation level:
Switch to the Broker Application Development perspective.
Click Window > Preferences. The Preferences dialog is displayed.
Expand the item for ESQL and Mapping on the left and click Code Generation.
Update the settings for code generation. See ESQL editor for details of the settings and their values.
When you have completed your changes, click Apply to close the Preferences dialog, apply your changes and leave the Preferences dialog open. Click OK to apply your changes and close the dialog. Click Cancel to close the dialog and discard your changes.
If you want to return your ESQL editor preferences to the initial values, click Restore Defaults. All values are reset to the original settings.
The changes are implemented when you add a message flow to a bar file.
|
Greetings Frank |
|
| Back to top |
|
|
| hornbeam123 |
| Posted: Thu Mar 10, 2005 3:11 pm Post subject: BIP2432E deploy from wbimb 5.0.1 cm to mqsi 2.1 broker |
|
|
Centurion
Joined: 01 Nov 2003
Posts: 101
|
Frank,
We must both be workaholics.
I discovered the preferences window about the same time you must have composed your response.
We will be running in dual broker (2.1 and 5.0) mode but will NOT be using any new features.
Presumedly once the default is changed to 2.1 code generation, we can NOT deploy any flows to a 5.0 broker, unless we restore the default setting correct ?
Thanks for your help.
 |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
