|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
 |
|
Hot to set Expiry & Timestamp in MQRFH2 -> jms foler |
« View previous topic :: View next topic » |
Author |
Message
|
jamesyu |
Posted: Fri Sep 24, 2010 1:37 pm Post subject: Hot to set Expiry & Timestamp in MQRFH2 -> jms foler |
|
|
Acolyte
Joined: 31 Jan 2007 Posts: 70
|
Hi All,
I use ESQL. My flow produces a MQ message wtih MQRFH2 header, plus the <jms> folder that the downstream JMS applocation can take it as a JMS message.
Problem is, how to set up the Timestamp and Expiry in the <jms> folder?
Can someone post some sample ESQL code?
Thanks,
James |
|
Back to top |
|
 |
paranoid221 |
Posted: Mon Sep 27, 2010 10:34 pm Post subject: Re: Hot to set Expiry & Timestamp in MQRFH2 -> jms fo |
|
|
 Centurion
Joined: 03 Apr 2006 Posts: 101 Location: USA
|
Quote: |
My flow produces a MQ message wtih MQRFH2 header, plus the <jms> folder that the downstream JMS applocation can take it as a JMS message. |
OK first thing. When you tack on a MQRFH2 header with the jms folder to your message, it is no longer an MQ message. For all practical purposes, it is now a JMS message.
Quote: |
Problem is, how to set up the Timestamp and Expiry in the <jms> folder?
Can someone post some sample ESQL code?
Thanks,
James |
If you've already set values for other fields(such as destination etc) in the jms folder, setting the values for the fields you described shouldn't be challenging.
What have you tried so far? What results did you get? _________________ LIFE is a series of complex calculations, somewhere multiplied by ZERO. |
|
Back to top |
|
 |
mqjeff |
Posted: Tue Sep 28, 2010 2:03 am Post subject: Re: Hot to set Expiry & Timestamp in MQRFH2 -> jms fo |
|
|
Grand Master
Joined: 25 Jun 2008 Posts: 17447
|
paranoid221 wrote: |
Quote: |
My flow produces a MQ message wtih MQRFH2 header, plus the <jms> folder that the downstream JMS applocation can take it as a JMS message. |
OK first thing. When you tack on a MQRFH2 header with the jms folder to your message, it is no longer an MQ message. For all practical purposes, it is now a JMS message. |
It's not a message at all as long as it's still inside an instance of a flow...
it's a logical message tree...  |
|
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
|
|
|
|