| Author |
Message
|
| solomita |
 Posted: Wed Sep 08, 2004 1:19 pm Post subject: Copy and Paste from txt file |
 |
|
Voyager
Joined: 06 May 2003
Posts: 94
|
As part of learning the new product, the client wanted to create a new flow in V5 which was identical to one that was successfully running in V2.1. We were able to import the copybook into a message definition file and create a new message flow without a problem. When we tried to copy the esql from a text file into V5, we get a few warning messages that there are unresolved field references. If we import the message flow instead of recreating it, there are no warnings in the ESQL. Any ideas?
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
 |
| RocknRambo |
| Posted: Wed Sep 08, 2004 3:15 pm Post subject: |
|
|
Partisan
Joined: 24 Sep 2003
Posts: 355
|
This cud happen....
there is a descrency in the ESQL versions.
In V5.0 there is a option of ESQL version to be either 2.1 or 5.0 bydefault its 5.0.
now, when u copy paste from a txt file since its 2.1 EQSL its showing warnings ..but when u migrate & import its taking care of ESQL version. |
|
| Back to top |
|
|
| solomita |
| Posted: Wed Sep 08, 2004 6:26 pm Post subject: |
|
|
Voyager
Joined: 06 May 2003
Posts: 94
|
Is there somewhere to manually change the ESQL version if you copy/paste?
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
|
| kirani |
| Posted: Wed Sep 08, 2004 10:12 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
Yes, you will have to change the ESQL code to match your V5 syntax, like module and main function etc.
If you migrate your existing message flow then the migration tool takes care of this for you.
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| solomita |
| Posted: Thu Sep 09, 2004 5:06 am Post subject: |
|
|
Voyager
Joined: 06 May 2003
Posts: 94
|
Before we pasted the ESQL, we clicked on Compute/Open ESQL and pasted into the skeleton that it creates for you so the functions and procedures were all in place. We simply created a new procedure and pasted the ESQL into that.
_________________
IBM Certified Specialist - WebSphere MQ Integrator
IBM Certified System Administrator - WebSphere MQ V5.3
IBM Certified System Administrator - WebSphere Business Integration Message Broker V5 |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Thu Sep 09, 2004 5:56 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
You may have to change the message flow project so that it references the message set project.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| JT |
| Posted: Thu Sep 09, 2004 10:49 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
To remove the unresolved field reference warnings, try the following:- Right-click on the mesage flow project
- Select Properties
- In the left pane, click on Project References
- In the right pane, select the appropriate Message Set project
- Click okay
|
|
| Back to top |
|
|
|
|
