Author |
Message
|
abs_cal |
Posted: Wed May 27, 2009 7:22 am Post subject: Look at these ESQL SUBSTRING function |
|
|
Acolyte
Joined: 18 Aug 2005 Posts: 62
|
SUBSTRING('Hello World!' BEFORE 'World');
returns 'Hello '.
SUBSTRING('Hello World!' AFTER 'World');
returns '!'
These function information are from help information center of WebSphere Message Brokers Toolkit - Message Broker
Version: 6.1.0.3
Build id: 6.1.0.3-IFix003-20090305_1223
However, even the above same codes are giving Red Cross in ESQL editor.
Can anyone have any idea where I am going wrong. |
|
Back to top |
|
 |
WMBDEV1 |
Posted: Wed May 27, 2009 7:37 am Post subject: |
|
|
Sentinel
Joined: 05 Mar 2009 Posts: 888 Location: UK
|
What version of the toolkit are you using?
Make sure you have the latest one |
|
Back to top |
|
 |
mgk |
Posted: Wed May 27, 2009 8:03 am Post subject: |
|
|
 Padawan
Joined: 31 Jul 2003 Posts: 1642
|
Yes, there was a problem in the toolkit which has subsequently been fixed where these new (for 6.1.0.3) types of substring were not recognised. If you patch to the latest toolkit you should be ok. If you still have a problem, open a PMR and ask for the fix... _________________ MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
Back to top |
|
 |
abs_cal |
Posted: Wed May 27, 2009 8:42 am Post subject: |
|
|
Acolyte
Joined: 18 Aug 2005 Posts: 62
|
Ya, It seems we need another FP for this substring function...I am running Toolkit. 6.1 with FP 3.
However, if we upgrade Toolkit with another FP for this function, do we need similar FP for BORKER to recognise this new function? |
|
Back to top |
|
 |
mqjeff |
Posted: Wed May 27, 2009 8:56 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
It's not an FP for Toolkit you need, it's just an iFix.
Runtime does not need change. |
|
Back to top |
|
 |
zpat |
Posted: Wed May 27, 2009 11:08 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
I thought 6.1.0.3-IFix003 was the latest?
Are you saying that there is an interim fix 004 now? |
|
Back to top |
|
 |
|