| Author |
Message |
 Topic: Overriding the Quantity property in Collector node dynamical |
tony_f
Replies: 16
Views: 17535
|
 Forum: WebSphere Message Broker (ACE) Support Posted: Wed Feb 19, 2014 8:47 am Subject: Triggering completion of a collector node collection |
In a reply to another post on this forum, the following was posted
You don't need to override it dynamically.
You just need to understand how collector works. You define a set of terminals to ... |
| Topic: mqconn, mqput etc missing from client installation |
tony_f
Replies: 6
Views: 5465
|
Forum: IBM MQ Installation/Configuration Support Posted: Mon Jul 29, 2013 6:30 am Subject: mqconn, mqput etc missing from client installation |
They are creating a service program and they receive an error of CPD5D02
The prototype for the API's is in a separate source member
0475.00 // Declare MQI named constants and prototypes ... |
| Topic: mqconn, mqput etc missing from client installation |
tony_f
Replies: 6
Views: 5465
|
Forum: IBM MQ Installation/Configuration Support Posted: Mon Jul 29, 2013 5:33 am Subject: mqconn, mqput etc missing from client installation |
mqconn, mqput, et.al, are API calls used by application programs.
Are you following the Quick Beginnings installation documentation?
Are you following the verification documentation?
Exactly w ... |
| Topic: mqconn, mqput etc missing from client installation |
tony_f
Replies: 6
Views: 5465
|
Forum: IBM MQ Installation/Configuration Support Posted: Mon Jul 29, 2013 4:55 am Subject: mqconn, mqput etc missing from client installation |
Hi
A customer who needs to connect to our iSeries and send MQ messages has installed MQ Client - apparently successfully - I ran DSPSFWRSC on their machine and I can see this :-
5725A49 *BASE ... |
| Topic: Error received on iSeriesPCMLCall node |
tony_f
Replies: 2
Views: 2510
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Apr 08, 2013 7:01 am Subject: Error received on iSeriesPCMLCall node |
Hi
I am having a problem with the iSeries Adapter node for message broker. I get the following error when I run a message through the flow
Apr 8 10:33:33 cor089a127 user:err|error ... |
| Topic: Error received on call to ISeriesPcmlCallNode |
tony_f
Replies: 1
Views: 1734
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Mar 25, 2013 7:43 am Subject: Error received on call to ISeriesPcmlCallNode |
Hi
I am investigating the use of iSeries Adapter nodes from message broker. I have configured the node, installed jar files etc as per the instructions from IBM and it's calling the node ok. Howeve ... |
| Topic: Problem with namespace prefix defaulting to NS1 |
tony_f
Replies: 7
Views: 8886
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 05, 2013 7:58 am Subject: Problem with namespace prefix defaulting to NS1 |
| Thanks for all the replies. I've tried to replicate the example on the link that Kimbert sent me and I can't seem to get it to work. If the first child of XMLNSC is called ParkerMsg, I was expecting t ... |
| Topic: Problem with namespace prefix defaulting to NS1 |
tony_f
Replies: 7
Views: 8886
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 05, 2013 6:12 am Subject: Problem with namespace prefix defaulting to NS1 |
I don't see anywhere in the code where it is creating an XMLNSC.NamespaceDecl.
I didn't think I needed to specify XMLNSC.NamespaceDecl as in the first ESQL it's providing the correct namespace pref ... |
| Topic: Problem with namespace prefix defaulting to NS1 |
tony_f
Replies: 7
Views: 8886
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 05, 2013 3:28 am Subject: Problem with namespace prefix defaulting to NS1 |
Hi
I have two ESQL's that are pretty much identical. They both write out to the same message set that is defined to use namespaces. The namespace declaration is defined to use a prefix of ph.
... |
| Topic: Problem with Polish character set in messages from iSeries |
tony_f
Replies: 7
Views: 8249
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Nov 19, 2012 5:22 am Subject: Problem with Polish character set in messages from iSeries |
Thanks for the quick responses 
So, if we switch the conversion off on the channel and write the message from the iSeries with a codepage of 870 (I believe that's Polish) then that should do ... |
| Topic: Problem with Polish character set in messages from iSeries |
tony_f
Replies: 7
Views: 8249
|
Forum: WebSphere Message Broker (ACE) Support Posted: Mon Nov 19, 2012 3:31 am Subject: Problem with Polish character set in messages from iSeries |
Hi
We have an iSeries application that writes MQ messages that are processed via Message Broker 7 into Siebel. It is now required that it sends data with Polish characters (possible other character ... |
| Topic: WMB Event Monitoring messages and the iSeries |
tony_f
Replies: 4
Views: 3058
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Aug 31, 2012 5:47 am Subject: WMB Event Monitoring messages and the iSeries |
| ok, thanks for that. |
| Topic: WMB Event Monitoring messages and the iSeries |
tony_f
Replies: 4
Views: 3058
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Aug 31, 2012 5:05 am Subject: WMB Event Monitoring messages and the iSeries |
Hi
Thanks for the quick response. The alias queue has a base object of a remote queue that is pointing to the queue on the iSeries. I wasn't sure whether there would be any Ascii - Ebcdic conversi ... |
| Topic: WMB Event Monitoring messages and the iSeries |
tony_f
Replies: 4
Views: 3058
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Aug 31, 2012 4:51 am Subject: WMB Event Monitoring messages and the iSeries |
Hi
I want to add event monitoring to flows I have created (on Broker 7). The monitor message would contain a payload of fields from an XMLNSC message that is processed by the flows. A subscription ... |
| Topic: Question regarding namespace stripping code |
tony_f
Replies: 5
Views: 4529
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Apr 13, 2012 5:13 am Subject: Question regarding namespace stripping code |
Then your code is working by pure luck. You should change to using XMLNSC.NamespaceDecl as soon as possible.
.
A lot of my code works that way 
Many thanks Kimbert, I'll change that code ... |
