| Author |
Message
|
| PeterPotkay |
 Posted: Mon Nov 02, 2009 3:27 pm Post subject: |
 |
|
Poobah
Joined: 15 May 2001
Posts: 7723
|
| Sam Uppu wrote: |
If the queue on remote site is non-persistent and DLQ(on remote qmgr) is not defined -> you will get 2053
If the queue on remote site is persistent, full and there is no DLQ defined, the channel will go into RETRY state and msgs will stuck in the XMITQ. The link provided by Vitor says this. |
That link does not say anything like that at all.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
 |
| exerk |
| Posted: Mon Nov 02, 2009 9:40 pm Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Sam Uppu wrote: |
If the queue on remote site is non-persistent...
If the queue on remote site is persistent... |
I do hope you are not one of those people who believes that a message assumes the persistency setting of the queue on which it lands 
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| shashivarungupta |
| Posted: Tue Nov 03, 2009 4:56 am Post subject: |
|
|
Grand Master
Joined: 24 Feb 2009
Posts: 1343
Location: Floating in space on a round rock.
|
| bruce2359 wrote: |
Reread Jeevan's post:
| Quote: |
| If channel are not being used for some time(disconnect interval period) they go into inactive state. |
A channel goes into stopped state because of channel errors or operator command.
Was the channel status stopped or inactive? |
Agree.
Pls, look at this. This is the IMP to understand the state of the CHANNEL and cause of it. Pls check the LOGS of the Queue Manager. OR if any FDC being generated there.
*Pls try to PING sender channel, if QMgr sends and receives a msg back then your settings on the sender and receiver channel should be fine.
*Pls try to RESET the channel, as channel does not START when there is mismatch about the msg seq. no. of the next msg to send.
*Check the definition of XMITQ, as :
DEFINE QLOCAL(A) USAGE(XMITQ) INITQ(SYSTEM.CHANNEL.INITQ)
DEFINE CHANNEL(QM1_QM2) CHLTYPE(SDR) +
XMITQ(A) +
CONNAME('connname(1234)') +
TRPTYPE(TCP)
Thanks
_________________
*Life will beat you down, you need to decide to fight back or leave it. |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Tue Nov 03, 2009 7:18 am Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| bruce2359 wrote: |
| Not to be picky, but queues are neither persistenr nor non-persistent. Persistence is a message attribute. |
Sorry. I should say persistent msg and non persistent msg instead of persistent queue/ non persistent queue.
Thanks for the correction. |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Tue Nov 03, 2009 7:21 am Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| PeterPotkay wrote: |
| Sam Uppu wrote: |
If the queue on remote site is non-persistent and DLQ(on remote qmgr) is not defined -> you will get 2053
If the queue on remote site is persistent, full and there is no DLQ defined, the channel will go into RETRY state and msgs will stuck in the XMITQ. The link provided by Vitor says this. |
That link does not say anything like that at all. |
Peter, This was tested by IBM in one of our PMRs with IBM and they came up with the same link what Vitor specified in his post. Infact that link is not talking anything about persistent/ non persistent msgs.
Thanks. |
|
| Back to top |
|
|
| Sam Uppu |
| Posted: Tue Nov 03, 2009 7:45 am Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
I should re-phrase something like this:
1. If the msg is non persistent:
remote queue is full and there is no remote DLQ -> you will get 2053
2. If the msg is persistent:
remote queue is full and there is no DLQ, the sender channel will go into RETRY mode and msgs will be in XMIT queue. |
|
| Back to top |
|
|
| exerk |
| Posted: Tue Nov 03, 2009 7:56 am Post subject: |
|
|
Jedi Council
Joined: 02 Nov 2006
Posts: 6339
|
| Sam Uppu wrote: |
1. If the msg is non persistent:
remote queue is full and there is no remote DLQ -> you will get 2053 |
Not if NPMSPEED is set to FAST you won't...
| Sam Uppu wrote: |
2. If the msg is persistent:
remote queue is full and there is no DLQ, the sender channel will go into RETRY mode and msgs will be in XMIT queue. |
Not according to THIS (see item 3)
_________________
It's puzzling, I don't think I've ever seen anything quite like this before...and it's hard to soar like an eagle when you're surrounded by turkeys. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Nov 03, 2009 8:22 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9482
Location: US: west coast, almost. Otherwise, enroute.
|
| Quote: |
1. If the msg is non persistent:
remote queue is full and there is no remote DLQ -> you will get 2053 |
This isn't exactly accurate.
If my app opened a qr definition, my put will succeed - reasoncode none.
The downstream mca will discover that the destination queue is full, the dlq is full or does not exist.
If I have asked for exception report messages, I might get one that will tell me that the message couldn't be delivered - and why.
_________________
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 |
|
|
| Sam Uppu |
| Posted: Tue Nov 03, 2009 9:11 am Post subject: |
|
|
Yatiri
Joined: 11 Nov 2008
Posts: 610
|
| bruce2359 wrote: |
| Quote: |
1. If the msg is non persistent:
remote queue is full and there is no remote DLQ -> you will get 2053 |
This isn't exactly accurate.
If my app opened a qr definition, my put will succeed - reasoncode none.
The downstream mca will discover that the destination queue is full, the dlq is full or does not exist.
If I have asked for exception report messages, I might get one that will tell me that the message couldn't be delivered - and why. |
I didn't really validate when IBM mentioned this as I was not sure of using persistent/ non persistent options inside the client code. I believed in IBM what they said. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Nov 03, 2009 11:09 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9482
Location: US: west coast, almost. Otherwise, enroute.
|
A server- or client- app that opens a qr will get a reasoncode of none for the successful put of a msg to the xmit queue on the server platform.
_________________
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 |
|
|
|
|
