| Author |
Message
|
| LearnMQSI |
 Posted: Mon Jun 12, 2006 1:06 pm Post subject: Warnings in migrated message flow .esql file |
 |
|
Centurion
Joined: 20 Aug 2002
Posts: 137
|
Hi There,
I have migrated a message flow from 2.1 to v6. Everything is going good except that in .esql file for migrated message flow, showing warning for the following statement.
SET "OutputRoot"."MRM"."MQ_RATE_REQUEST_MSG"."MQ_MODE" = LTRIM(ref1."MQMode");
I did mentioned my reference before the above line is as follows:
CREATE COMPUTE MODULE Big_Msg_Request_XML_to_MRM
CREATE FUNCTION main() RETURNS BOOLEAN BEGIN
DECLARE I INTEGER;
SET I = 1;
WHILE I < CARDINALITY(InputRoot.*[]) 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.
--DECLARE VARIABLES
DECLARE ref1 REFERENCE TO InputRoot.XML.RateMessage;
Even my message flow is running but just curious WHY its showing warning?
Any help or idea would be highly appreciated!!!
_________________
IBM Certified System Administrator - WebSphere MQ 5.3 |
|
| Back to top |
|
 |
| elvis_gn |
| Posted: Mon Jun 12, 2006 8:20 pm Post subject: |
|
|
Padawan
Joined: 08 Oct 2004
Posts: 1905
Location: Dubai
|
Hi LearnMQSI,
The ESQL shows warnings on the SQL and referenced statements...becoz until runtime, it is not sure that that line of code works...it is just telling you to be careful... 
If you hardcode a value in that statement and save, u will see the warning vanish...which means that the ESQL knows that everything in that statement is defined within the module...
Dont bother about it.
Regards. |
|
| Back to top |
|
|
| LearnMQSI |
| Posted: Tue Jun 13, 2006 5:40 am Post subject: |
|
|
Centurion
Joined: 20 Aug 2002
Posts: 137
|
Hi elvis_gn,
Thank you so much your quick response and an excellent way of explainning. I really appreciate it.
So, based on your feedback, there is nothig I can do about it and I don't need to worry about it.
Thank you again!!!
_________________
IBM Certified System Administrator - WebSphere MQ 5.3 |
|
| Back to top |
|
|
| JT |
| Posted: Tue Jun 13, 2006 6:24 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
A relevant excerpt from the Information Center:
| Quote: |
Warnings are displayed for message flows that you have imported from Version 2.1 to Version 6.0- Scenario: Warning messages are displayed for message flows that you have imported from Version 2.1 to Version 6.0, such as Unresolvable message field reference Body.RootTag.ID.
- Explanation: Version 6.0 warns of any field reference that it cannot resolve. These warnings do not cause any problems with deploying or running the message flows.
- Solution: You can remove a large number of warning messages by performing the following steps:
1. Reference any MRM message sets in the message flow projects Property pane. This removes any warnings for messages that are defined in the message sets.
2. Run the rdb definition file wizard to define all the databases that are used by the message flows.
|
Basically, you need to establish a project reference between the messageflow project and the messageset project. |
|
| Back to top |
|
|
| LearnMQSI |
| Posted: Tue Jun 13, 2006 10:15 am Post subject: |
|
|
Centurion
Joined: 20 Aug 2002
Posts: 137
|
Hi JT,
Thank you for your response with the excellent information. Should I do this from Admin perspective or Application perspective. I'm fairly new to message Broker Toolkit so if you can give me little bit more details and steps would be highly appreciated!!!
Thank you again for all those who share their thoughts
_________________
IBM Certified System Administrator - WebSphere MQ 5.3 |
|
| Back to top |
|
|
| JT |
| Posted: Tue Jun 13, 2006 11:05 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
|
| Back to top |
|
|
|
|
