| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Setting persistence and transactionality in DestinationList |
« View previous topic :: View next topic » |
| Author |
Message
|
| Cliff |
 Posted: Mon May 24, 2004 3:10 am Post subject: Setting persistence and transactionality in DestinationList |
 |
|
Centurion
Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire
|
Folks,
(in WBIMB 5.0 CSD 3 on Win XP) for various reasons I won't bore you with I have some error handling within a Compute node in which I am attempting to construct a message and destination list, propagate this then throw a user exception to roll back the UOW. The PUT of the 'error' message needs to be outside the UOW so I set OutputLocalEnvironment.Destination.MQ.DestinationData.transactionMode = 'No' but the PUT is still included in the UOW. Likewise attempting to control the persistence: set OutputLocalEnvironment.Destination.MQ.DestinationData.persistenceMode = 'Yes' doesn't work.
What have I missed? Or is this a bug?
Thanks -
Cliff |
|
| Back to top |
|
 |
| jefflowrey |
| Posted: Mon May 24, 2004 3:51 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I assume you're taking advantage (or trying to) of
| WBIMB online help wrote: |
You can also create a number of elements called DestinationData within MQ and MQe. Each of these can be set up with a set of name-value elements that defines a message destination and its PUT options.
...
The content of each instance of DestinationData is the same as the content of Defaults for each protocol, and can be used to override the default values in Defaults. You can therefore set up Defaults to contain values that are common to all destinations, and set only the unique values in each DestinationData subtree. If a value is not set in DestinationData, and not set in Defaults, the value that you have set for the corresponding node property is used. |
It doesn't seem to work here, either. Not if I use MQ.DestinationData OR MQDestinationList.DestinationData.
But I'm only running FixPack 2 right now, it could be fixed in FP3.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| Cliff |
| Posted: Mon May 24, 2004 4:02 am Post subject: |
|
|
Centurion
Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire
|
Hi, Jeff.
Yes, I'm trying to come up with an elegant solution controlling all the properties of the output message from the destination list, which is supposed to override any properties set elsewhere. BTW I am on CSD 3, so I can assure you it's not fixed at that code level!
I think I can feel an APAR coming on...
Cheers -
Cliff |
|
| Back to top |
|
|
| kirani |
| Posted: Mon May 24, 2004 9:05 pm Post subject: |
|
|
Jedi Knight
Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA
|
cliff,
was this working with WMQI 2.1?
_________________
Kiran
IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries
|
|
| Back to top |
|
|
| Cliff |
| Posted: Tue May 25, 2004 3:23 am Post subject: |
|
|
Centurion
Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire
|
Hi, Kiran.
I haven't tried this with v 2.1 as the client is a v 5.0 site, so there doesn't seem much point. I have raised a PMR with IBM whose suggestion so far is to set transactionality to 'No' on the MQOutput node (!). Clearly this doesn't address the problem and certainly won't meet my requirements.
Interestingly you can control the message persistence through the Properties, though this doesn't work for transactionality!
Ho hum. I'll report progress as and when it happens.
Cheers -
Cliff |
|
| Back to top |
|
|
| Cliff |
| Posted: Tue Jun 29, 2004 3:10 am Post subject: |
|
|
Centurion
Joined: 27 Jun 2001
Posts: 145
Location: Wiltshire
|
Folks,
seems there is a gap between the documentation and the reality, also when an invalid value is specified in the DesinationData it is simply ignored, rather than causing a parsing error or other exception. So, it will all work as it should but you have to specify lower case values: OutputLocalEnvironment.Destination.MQ.DestinationData.transactionMode = 'no';
Same for persistence, etc.
So now you can sleep easy at night.
Cheers -
Cliff |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
