| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Transfer messages from one xmitq to another |
« View previous topic :: View next topic » |
| Author |
Message
|
| MKHODER1 |
 Posted: Fri Jun 30, 2023 10:56 am Post subject: Transfer messages from one xmitq to another |
 |
|
Apprentice
Joined: 18 Aug 2018
Posts: 31
|
Hi,
I want to transfer messages from an xmitq xmitq1 to another xmitq xmitq2 in order to send them to another queue manager.
A message that exists in an xmitq contains a transmission queue header.
I exported the messages that exist in xmitq1 into a file with qload, then I replaced the queue manager name with the new one.
qload.sh -i xmitq1 -dt -f out.txt
sed -i 's/QM1/QM2/g' out.txt
I loaded the file into xmitq2 and got the following error:
qload.sh -o xmitq2 -f out.txt
Error: MQPUT(xmitq2) failed RC(2013) Expiry error.
Could you help me ? Is there any solution to transfer messages from xmitq to another ?
Thanks |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Fri Jun 30, 2023 12:39 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
https://www.ibm.com/docs/en/ibm-mq/8.0?topic=commands-dmpmqmsg
Search google for "mqrc 2013" to look for preventive- or corrective-service.
Other than that, I'd guess that the reason the re-load failed is that the message expiry value set in the application mqmd has elapsed.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
| Andyh |
| Posted: Sat Jul 01, 2023 6:05 am Post subject: |
|
|
Master
Joined: 29 Jul 2010
Posts: 239
|
After an MQGET the expiry field in the MQMD shows the remaining expiry time for the message.
When you do an MQPUT of a message with an explicit xmitq header the expiry time in the MQMD within the MQXMIT header MUST match the expiry time in the actual MQMD.
The MQGET issued as part of the first qload unloading the will result in the MQMD expiry field being updated, but not the corresponding field in the MQXMIT header, thus when the corresponding MQPUT when reloading the queue occurs the two expiry fields do not match and the QMgr rejects the MQPUT. |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Sat Jul 01, 2023 9:15 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
Unless you need to copy the message for the other queue manager this is a very poor way to do so.
If you just want to send the message to the second queue manager, because the original destination is no longer available, I would suggest the following
- Create a queue manager alias for the original queue manager in the target queue manager
- Create the channel to the new destination queue manager
- Enter the original XMITQ into the new channel
- Set the (new) channel name in the Trigger Data of the original XMITQ
- start the new channel
- done
_________________
MQ & Broker admin |
|
| 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
|
|
|
|
