ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Overriding the Expiry in the MQMD using WMB 8 Mapping Node

Post new topic  Reply to topic
 Overriding the Expiry in the MQMD using WMB 8 Mapping Node « View previous topic :: View next topic » 
Author Message
GSnyder13
PostPosted: Thu Dec 06, 2012 1:19 pm    Post subject: Overriding the Expiry in the MQMD using WMB 8 Mapping Node Reply with quote

Novice

Joined: 29 Mar 2005
Posts: 13
Location: United States

We have begun using WMB V8 and have started to refactor some of our request/reply flows to use DFDL. I have XML as the input with a DFDL xsd as the output. There is a need to override some of the MQMD and MQCIH fields as the output is going tho the mainframe. Our production flow sets, in the MQMD, the EXPIRY to 600, the CorrelId to MQCI_NEW_SESSION, and the Format to MQFMT_CICS. I have not had any luck getting the EXPIRY to be overridden in the ASSIGN to override the MQMD input. Just wondering if anyone has had any experience with this. Thanks.
Back to top
View user's profile Send private message
kimbert
PostPosted: Thu Dec 06, 2012 1:40 pm    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Quote:
We have begun using WMB V8 and have started to refactor some of our request/reply flows to use DFDL.
Hope it goes well. Are you doing this in order to get better throughput / lower CPU usage?
Quote:
I have not had any luck getting the EXPIRY to be overridden in the ASSIGN to override the MQMD input. Just wondering if anyone has had any experience with this.
I don't even know what you mean by 'the ASSIGN'. I expect somebody else does, though.
Back to top
View user's profile Send private message
GSnyder13
PostPosted: Fri Dec 07, 2012 9:41 am    Post subject: Reply with quote

Novice

Joined: 29 Mar 2005
Posts: 13
Location: United States

Thanks. When I said ASSIGN, I meant in the Mapping Node, a value can be assigned to an output field. Values in the output fields in the Message Assembly can be overridden. Sorry.
Back to top
View user's profile Send private message
kash3338
PostPosted: Fri Dec 07, 2012 10:05 am    Post subject: Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

GSnyder13 wrote:
Thanks. When I said ASSIGN, I meant in the Mapping Node, a value can be assigned to an output field. Values in the output fields in the Message Assembly can be overridden. Sorry.


May be you are missing this,

Quote:
When you first open or create a message map for the node, if you select This map is called from a message flow node and maps properties and message body, the headers in the input message are always copied to the output message without modification. To modify the message headers in a Mapping node, select This map is called from a message flow node and maps properties, headers, and message body. When you select this property, the map that is created allows additional elements, including WebSphere® MQ, HTTP, and JMS headers, to be mapped.
Back to top
View user's profile Send private message Send e-mail
GSnyder13
PostPosted: Fri Dec 07, 2012 11:59 am    Post subject: Reply with quote

Novice

Joined: 29 Mar 2005
Posts: 13
Location: United States

Thanks, kash, but I don't see that when I create a new mapping node in WMB V8.
Back to top
View user's profile Send private message
kash3338
PostPosted: Fri Dec 07, 2012 8:27 pm    Post subject: Reply with quote

Shaman

Joined: 08 Feb 2009
Posts: 709
Location: Chennai, India

GSnyder13 wrote:
Thanks, kash, but I don't see that when I create a new mapping node in WMB V8.


Sorry that was from WMB v7 infocenter.


GSnyder13 wrote:
Our production flow sets, in the MQMD, the EXPIRY to 600, the CorrelId to MQCI_NEW_SESSION, and the Format to MQFMT_CICS. I have not had any luck getting the EXPIRY to be overridden in the ASSIGN to override the MQMD input.


Do you see the other values being set correctly? Can you see the value of Expiry getting overridden in trace?
Back to top
View user's profile Send private message Send e-mail
kimbert
PostPosted: Sat Dec 08, 2012 11:25 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Sorry - I was being a bit thick there. So you have an 'Assign' transform in your v8 map that assigns a constant value to the output field 'OutputRoot.MQMD.Expiry'. And you are not seeing the correct value in the MQ output message. Right?

btw, I didn't see a response to my question about the move to DFDL...nudge.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Overriding the Expiry in the MQMD using WMB 8 Mapping Node
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.