| Author |
Message |
 Topic: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
Marek
Replies: 15
Views: 13371
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Tue Apr 03, 2007 12:34 am Subject: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
Why. What would this achieve.
Complete clarity of what esql and msgflow CVS versions are running in Production incl. all external components (e.g. subflow and global variable libraries).
The BAR ... |
| Topic: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
Marek
Replies: 15
Views: 13371
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Apr 02, 2007 7:30 am Subject: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
... ref. Passthru nodes ... I don't intend creating any connections to/from the Passthru node ... just intend to leave it standalone in each flow. Are there any issue with this?
Thanks. |
| Topic: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
Marek
Replies: 15
Views: 13371
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Apr 02, 2007 6:53 am Subject: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
If you read the last line as being main flow, not subflow, then all of those cases should work. Additionally, long description is also preserved on other nodes, such as Compute.
Hope this works fo ... |
| Topic: XMLNSC parsing : empty tag problem |
Marek
Replies: 5
Views: 6117
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Mar 30, 2007 2:04 am Subject: XMLNSC parsing : empty tag problem |
| In the example why assign the tag to a char string? I don't see the point in this. If you intend to refer to 'InputRootInputRoot.XMLNSC.NS1:s_o.NS1:mr_history_data' more often then from a readibili ... |
| Topic: ESQL |
Marek
Replies: 1
Views: 2112
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Mar 30, 2007 12:53 am Subject: ESQL |
There are no such constants in esql. I guess someone has defined their own constant in the code. FoR example:
DECLARE CONSTANT_INT SHARED CONSTANT CHAR 'value'; |
| Topic: XMLNSC Declare Reference bug? Navigate XML Tree 6.0.2 |
Marek
Replies: 14
Views: 14349
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Mar 28, 2007 6:59 am Subject: XMLNSC Declare Reference bug? Navigate XML Tree 6.0.2 |
XML.Attribute should = '0x03000100'.
However, the bug is that XML.Attribute actually = '0xFF03000100'.
Sorry ... XML.Attribute should read XMLNSC.Attribute |
| Topic: XMLNSC Declare Reference bug? Navigate XML Tree 6.0.2 |
Marek
Replies: 14
Views: 14349
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Mar 28, 2007 6:51 am Subject: XMLNSC Declare Reference bug? Navigate XML Tree 6.0.2 |
For the record and using XML.Attribute as an example:
XML.Attribute should = '0x03000100'.
However, the bug is that XML.Attribute actually = '0xFF03000100'.
So I've temporarily hard coded ... |
| Topic: Problem while calling a stored procedure |
Marek
Replies: 3
Views: 4248
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Mar 27, 2007 2:17 am Subject: Problem while calling a stored procedure |
Try:
CREATE PROCEDURE amspWSTBInjectSubScriber(IN p1 CHAR, IN p2 CHAR EXTERNAL NAME "dbo.amspWSTBInjectSubScriber";
... and make sure you have the relevant authorities set (i.e. G ... |
| Topic: XMLNSC Declare Reference bug? Navigate XML Tree 6.0.2 |
Marek
Replies: 14
Views: 14349
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Mar 26, 2007 8:22 am Subject: XMLNSC Declare Reference bug? Navigate XML Tree 6.0.2 |
... and I note that if I want to refer to the Message element I need to code 'someNS:' yet again. See:
DECLARE p_xmlTree REFERENCE TO InputRoot.XMLNSC.someNS:CSL.someNS:Message;
Is ther ... |
| Topic: XMLNSC Declare Reference bug? Navigate XML Tree 6.0.2 |
Marek
Replies: 14
Views: 14349
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Mar 26, 2007 7:37 am Subject: XMLNSC Declare Reference bug? Navigate XML Tree 6.0.2 |
Much appreciated for taking the time to reply.
Your solution works (single quotes round the namespace address).
For the record, initially I tried to just suffix 'xmlns:'. See:
DECLARE p_xm ... |
| Topic: XMLNSC Declare Reference bug? Navigate XML Tree 6.0.2 |
Marek
Replies: 14
Views: 14349
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Mar 26, 2007 6:10 am Subject: XMLNSC Declare Reference bug? Navigate XML Tree 6.0.2 |
Background
WMB v.6.0.2 PTF 4
I've been having whitspace issues whist trying to dynamically navigate though an XML tree using the XML parser so I've swaped to the XMLNSC parser. So far so good, howe ... |
| Topic: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
Marek
Replies: 15
Views: 13371
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Mar 19, 2007 5:36 am Subject: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
I inserted a Passthru node into my Subflow SLI_SUBFLOW_IL_EXCEPTIONHANDLER.
Then, I pasted the following keyword into the Long Description and redeployed:
$MQSI_SLI_SUBFLOW_IL_EXCEPTIONHANDLER= ... |
| Topic: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
Marek
Replies: 15
Views: 13371
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Mar 16, 2007 4:53 am Subject: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
Hi Dave
Thanks for your mail.
I mean not showing the keywords/long description in the Admin Perspective (... Properties tab relating to a Message Flow in an Execution Group).
As requested, ... |
| Topic: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
Marek
Replies: 15
Views: 13371
|
Forum: WebSphere Message Broker (ACE) Support Posted: Thu Mar 15, 2007 2:41 am Subject: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
Dave, many thanks for the update.
We've raised PMR 43858 with IBM at our end.
Regards. |
| Topic: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
Marek
Replies: 15
Views: 13371
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Mar 14, 2007 6:08 am Subject: Keword Bug? V.6.0.2 Long Description Subflow CVS Version |
Tried the Short Description instead but the keywords were still not picked up.
Thanks for your suggestion. |
