| Author |
Message
|
| maha20 |
 Posted: Tue Feb 22, 2005 12:38 pm Post subject: Filter Node Problem while migrating to WBI 51 |
 |
|
Voyager
Joined: 23 Sep 2003
Posts: 79
|
Hi -
The ESQL statement in the migrated filter node is not being evaluated. The message is simply propogated to Unknown terminal. I see some one else in this group also experienced this type of problem. Please let me know the correction to be made .. Thanks ..
Maha |
|
| Back to top |
|
 |
| Michael Dag |
| Posted: Wed Feb 23, 2005 1:35 am Post subject: |
|
|
Jedi Knight
Joined: 13 Jun 2002
Posts: 2607
Location: The Netherlands (Amsterdam)
|
on 51? is this a typo or do you have access to something we don't know about?
_________________
Michael
MQSystems Facebook page |
|
| Back to top |
|
|
| Craig B |
| Posted: Wed Feb 23, 2005 1:48 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003
Posts: 316
Location: UK
|
Hi,
Could you provide more details relating to your problem? You say that the ESQL statement is not being evaluated? How have you determined this? Did you take a user level trace of the message flow running and see that the Filter node did not execute any expressions? Or are you basing your result on the fact that the flow took the Unknown path. Is it possible that you are referencing a message tree path that in V5 is not present (for whatever reason)?
_________________
Regards
Craig |
|
| Back to top |
|
|
| maha20 |
| Posted: Wed Feb 23, 2005 9:48 am Post subject: |
|
|
Voyager
Joined: 23 Sep 2003
Posts: 79
|
I have an input node followed by a trace with Pattern - Root and the value of a field I am checking for in the followed filter node. Like --
Input->Trace->Filter ....
In Trace I have ${Root} and ${Root.XML.SomeVal}
The filter node checks for RETURN Root.XML.SomeVal;
The results of these statements are -
.... xxxxx (Root).....
and
'PO' -> value I am checking in the filter node
' from trace node 'XXXX.Trace'.
The trace node 'XXXX.Trace' has output the specified trace data.
This is an information message provided by the message flow designer. The user response will be determined by the local environment.
2005-02-14 12:27:13.074474 8482 UserTrace BIP4067I: Message propagated to output terminal for trace node 'XXXX.Trace'.
The trace node 'XXXX.Trace' has received a message and is propagating it to any nodes connected to its output terminal.
No user action required.
2005-02-14 12:27:13.074559 8482 UserTrace BIP4006I: Message propagated to 'unknown' terminal of filter node 'XXXX.Filter'.
2005-02-14 12:27:17.938688 8996 UserTrace BIP2632I: Message received and propagated to 'out' terminal of MQ input node 'ConfigurationMessageFlow.InputNode'.
Links for the same kind of behaviour
http://www.mqseries.net/phpBB2/viewtopic.php?t=18254&highlight=filter+node+wbi5
http://www.mqseries.net/phpBB2/viewtopic.php?t=18649&highlight=filter+node+migration |
|
| Back to top |
|
|
| Craig B |
| Posted: Wed Feb 23, 2005 1:15 pm Post subject: |
|
|
Partisan
Joined: 18 Jun 2003
Posts: 316
Location: UK
|
Hi,
Good diagnostic information. Your user trace shows that the Filter node did not execute any ESQL at all. I have seen this behaviour on a number of occasions with Compute node, and this behaviour could occur with any ESQL supporting node (such as the Filter node).
When a message flow is added to a bar file, then the flows are compiled into the CMF file that appears in the bar file. During this process the ESQL file paths are constructed and the ESQL module and procedure names are added to form a file path. If the file path that is formed is greater than 256 characters (maximum file name size on Windows), then the name is truncated and no error is thrown. As a result of this, the ESQL file is not accessed and no ESQL is added to the node. This usually gives the trace that you see where no ESQL is added.
This long file name usually results from the Toolkit being installed in a long directory name, then having long ESQL file names and long module names etc. I was under the impression that a fix was made in FP04 which meant that if you had encountered this problem then the Toolkit would generate an error indicating it could not added the ESQL.
If you wanted to see whether this is a possibilty then open your bar file in a zip program and extract the CMF file. If you open this in an editor then you should be able to find the Filter node within the flow XML. For this node you will find a <filterExpression> tag which contains the ESQL for the node. If this is blank then this shows that the Toolkit has not added the ESQL correctly. just to make sure that the migration has occured correctly, go to the Filter node in the Toolkit and open the ESQL. if this opens fine, then you know that the ESQL is present for that node. (The toolkit does not ecnounter the path limit because the ESQL is relative to where the flow is in the project).
_________________
Regards
Craig |
|
| Back to top |
|
|
| maha20 |
| Posted: Thu Feb 24, 2005 9:39 am Post subject: |
|
|
Voyager
Joined: 23 Sep 2003
Posts: 79
|
| Thanks a lot Craig. When we tried by renaming the mssg flow it worked.. Thanks again .. |
|
| Back to top |
|
|
|
|
