| Author |
Message
|
| srinivasonmb |
 Posted: Tue Sep 24, 2013 11:32 am Post subject: esql functions are not calling from mapping node in v8 |
 |
|
Novice
Joined: 04 Jul 2013
Posts: 16
|
Hi, Good Evening,
i am using MB V8.0.0.2 for migrating my messsage flow projects from MB V6.1.
In v6 i have successfully calling esql functions which are having REFERENCE variable as argument.
i have function like below:
| Quote: |
Create function ABC(object REFERENCE, name CHARACTER)
END |
i have calling the above function successfully in V6.1
But in v8.0.0.1, i am unable to call those functions in my mapping node, it is saying as an REFERENCE variable argument functions are not migrated in latest version.
i have tried to write esql code instead of mapping node because of this problem.
but my mapping file contains huge attributes, so it will take lot of time to me write an esql code.
can anyone help me out how to use those functions in v8 mapping node.
please advise on this. |
|
| Back to top |
|
 |
| srinivasonmb |
| Posted: Sat Sep 28, 2013 11:31 pm Post subject: |
|
|
Novice
Joined: 04 Jul 2013
Posts: 16
|
i am getting below error after migrating the message map if it have above esql functions.
| Quote: |
The mapping expression esql:abc cannot be converted.
|
[/code] |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Sun Sep 29, 2013 12:58 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
As the call to the ESQL works in 8.0.0.2 why don't you upgrade to that version?
If you can't then raise a PMR and IBM may be able to provide a fix to 8.0.0.1 for you.
However I strongly advise you to go to 8.0.0.2 as there are all sorts of problems with subflows etc that are addressed in this release. Who knows if a fix for this problem won't simply uncover another one and another one?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| srinivasonmb |
| Posted: Sun Sep 29, 2013 8:54 pm Post subject: |
|
|
Novice
Joined: 04 Jul 2013
Posts: 16
|
| Sorry, i am using MB V8.0.0.2, i am getting this error in this version only. |
|
| Back to top |
|
|
| martinb |
| Posted: Mon Sep 30, 2013 1:22 am Post subject: |
|
|
Master
Joined: 09 Nov 2006
Posts: 210
Location: UK
|
Please have a look at the Info Centre topic "Considerations for converting a message map to a graphical data map" (br40815)
This states
"
Calls to ESQL procedures that use the ESQL REFERENCE data type are replaced with Task transforms in the converted graphical data map. You must replace each of these Task transforms with a Custom XPath, Custom Java, or Custom ESQL transform that provides equivalent function.
"
The facilities to call ESQL from the new Graphical Data Mapper only support calling ESQL with simple data types that are passed by value. The previous version messaging mapping was an ESQL code generator, so was deployed and executed in the runtime as ESQL. |
|
| Back to top |
|
|
| srinivasonmb |
| Posted: Tue Oct 01, 2013 8:15 pm Post subject: |
|
|
Novice
Joined: 04 Jul 2013
Posts: 16
|
| Martin, i had also seen this in info center, but is there any option to do this in a easy manner, like even using the same functions... |
|
| Back to top |
|
|
| martinb |
| Posted: Wed Oct 02, 2013 12:10 am Post subject: |
|
|
Master
Joined: 09 Nov 2006
Posts: 210
Location: UK
|
It really is a case were there is no one answer. You'll have to look into your ESQL function to see why it was taking a REF parameter.
Some of the cases I've seen it was so that the function could iterate over a repeating element and apply some conditional merging to the singleton target.
In that case we could replace the call directly in the map using ForEach or Join transforms with filter or join conditions. |
|
| Back to top |
|
|
|
|
