| Author |
Message
|
| vani_cool |
 Posted: Mon Jan 05, 2015 11:53 pm Post subject: RC 2021 during MQGet over an Alias queue |
 |
|
Novice
Joined: 15 Jul 2009
Posts: 17
|
Hi
Look for your inputs over a MQ error.
Environment:
Alias queue of a MQ over zOS
Calling application - COBOL Program,
Problem SUmmary
Our cobol application/program is trying to read a message from Alias QUeue of a MQ. It is working fine since 2008, but all of a sudden it start giving Reason Code 2021 error, this week.
looked in MQ 2021, but there are no MQ iNQ or MQ Set that we are doing in the code.
Look forward to your responses or in case need any more info let me know |
|
| Back to top |
|
 |
| PaulClarke |
| Posted: Tue Jan 06, 2015 12:07 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
Have you considered taking an MQ trace and seeing which MQI call causes the reason code and what the call looks like?
Cheers,
Paul
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| vani_cool |
| Posted: Tue Jan 06, 2015 12:35 am Post subject: |
|
|
Novice
Joined: 15 Jul 2009
Posts: 17
|
Hi there
Thanks for the reply,
We are using MQGET call from the cobol program which is giving this MQ2021 error.
Call 'MQGET' USING QHA-HConn
QHA-HRecv
MQMD
MQGMO
Datalen
MQ-INBUF
RecvLen
QHA-QCC
QHA-QRC.
::MQGMO options:::
MQGMO-SYNCPOINT
---Our cobol program is calling the mq asyncronously.
--- We have logic of maintaining the Backout count and increasing the backout count when the read fails.
-- We will put the MQ trace also in the meantime,,
but this code is working fine since 2008, and we havent touched the code a bit,
- is there any issues with date changes, year changes etc?
Regards |
|
| Back to top |
|
|
| PaulClarke |
| Posted: Tue Jan 06, 2015 12:41 am Post subject: |
|
|
Grand Master
Joined: 17 Nov 2005
Posts: 1002
Location: New Zealand
|
It would surprise me if MQGET returned 2021 without something odd happening.
Is it possible that something has changed underneath you. For example, has someone installed an API exit which is issuing some form of MQINQ call (which is failing)? Or, are you going over an MQ Client link and have a channel exit doing something similar?
Cheers,
Paul.
_________________
Paul Clarke
MQGem Software
www.mqgem.com |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 06, 2015 6:27 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| vani_cool wrote: |
...
but this code is working fine since 2008, and we havent touched the code a bit. |
You know this because you dumped the cobol application load-module, and looked at the data/time stamp at the beginning of the load-module?
| vani_cool wrote: |
| --Our cobol program is calling the mq asyncronously. |
What does this mean? Does your cobol app call a sub-program? Is the sub-program receiving the r/c 2021 from an MQINQ or MQSET? What is the date/time stamp of the called sub-program?
_________________
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 |
|
|
| hughson |
| Posted: Tue Jan 06, 2015 7:36 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
| vani_cool wrote: |
| but this code is working fine since 2008, and we havent touched the code a bit |
What has changed in your environment between when it was working and when you started to see the error? Have you applied any maintenance, upgraded a version of something?
Trace is a good place to start here
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| tczielke |
| Posted: Tue Jan 06, 2015 7:50 am Post subject: |
|
|
Guardian
Joined: 08 Jul 2010
Posts: 941
Location: Illinois, USA
|
| My two cents. I would open a PMR and work with IBM. I have done a fair bit of work with MQ traces, and although the distributed tracing facility is very robust and something an administrator could leverage on their own, I have found the exact opposite for z/OS. If you have a vendor product like Mainview that can run their own API traces, then that would be helpful. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jan 06, 2015 8:05 am Post subject: Re: RC 2021 during MQGet over an Alias queue |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| vani_cool wrote: |
Our cobol application/program is trying to read a message from Alias QUeue of a MQ. It is working fine since 2008, but all of a sudden it start giving Reason Code 2021 error, this week.
looked in MQ 2021, but there are no MQ iNQ or MQ Set that we are doing in the code. |
If a rc 2021 is returned from an MQGET call, then it's definitely time to open a PMR.
_________________
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 |
|
|
| hughson |
| Posted: Wed Jan 07, 2015 1:33 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1959
Location: Bay of Plenty, New Zealand
|
I see you have now asked this same question on another forum. This forum is probably the most active one, you will get the best advice on here.
Did you have any answers to the queries made on this forum that you could share on here - keep it all in one place? For example, did you find out what, if anything, changed in your environment? Did you take a trace? Have you opened a PMR to provide IBM with your trace?
Cheers
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
|
|
