| Author |
Message
|
| bkRaju |
 Posted: Mon Jul 16, 2012 5:48 pm Post subject: MQRC 2119 on cluster mesages. |
 |
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
Hi All,
I have created a qmgr(PR1) and made part of the cluster CLUS1. Cluster SDR channel goes to running state from QMGR1 to Full repository qmgr(FR1). However there was no communication happening from FR1 to PR1.
PR1 is not visible in FR1.
Later I noticed that there are MQ cluster admin messages in DLQ of FR1 and all these messages are related to PR1. The messages were put by repository process amqrrmfa of FR1. MQ reason code says 2119(MQRC_NOT_CONVERTED).
Please advise how to address the issue?
Thanks, |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Mon Jul 16, 2012 5:54 pm Post subject: Re: MQRC 2119 on cluster mesages. |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| bkRaju wrote: |
Hi All,
I have created a qmgr(PR1) and made part of the cluster CLUS1. Cluster SDR channel goes to running state from QMGR1 to Full repository qmgr(FR1). However there was no communication happening from FR1 to PR1.
PR1 is not visible in FR1.
Later I noticed that there are MQ cluster admin messages in DLQ of FR1 and all these messages are related to PR1. The messages were put by repository process amqrrmfa of FR1. MQ reason code says 2119(MQRC_NOT_CONVERTED).
Please advise how to address the issue?
Thanks, |
QMGR1? Where did this come from? Your OP names PR1, FR1, in a cluster(CLUS1). Is this the complete cluster? Has this cluster ever worked?
Are the two FRs fully bound to each other with CLUSSDR and CLUSRCVR channels? Are all of the channels RUNNING? Any of them have names like TEMPQMGR?
_________________
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 |
|
|
| bkRaju |
| Posted: Mon Jul 16, 2012 6:04 pm Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
sorry, it is PR1 not QMGR1.
yeah we have two FRs(FR1 and FR2). The same issue(messages goes to DLQ with 2119) is happening in FR2.
The same cluster CLUS1 works for other partialrepoitories. didnt see any issues with the connectivity.
System.Temp.Queue Manager.Object shows in PR1.
Thanks, |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Jul 16, 2012 6:14 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Check your channel definitions for errors (ip address, port, spelling of channel name. TEMPQMGR means that the pr and fr have not bound to each other.
_________________
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 |
|
|
| bkRaju |
| Posted: Mon Jul 16, 2012 6:20 pm Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
Yes, Connectivity is fine and didnt see issue with the definations.
If repository process is able to process the cluster commands then there shouldnt be the issue. Here repository process unable to process the messages and being sent to DLQ with 2119 errors...
Why the repository process is writing to DLQ with 2119? what is wrong ?which parameter I have to check? |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Mon Jul 16, 2012 6:54 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| bkRaju wrote: |
| Yes, Connectivity is fine and didnt see issue with the definations. |
Use runmqsc to display clusqmgr(*) from both PR and FR in question. Post the output here.
| bkRaju wrote: |
| If repository process is able to process the cluster commands then there shouldnt be the issue. |
What cluster commands are you talking about?
| bkRaju wrote: |
Here repository process unable to process the messages and being sent to DLQ with 2119 errors...
Why the repository process is writing to DLQ with 2119? what is wrong ?which parameter I have to check? |
Use runmqsc to display CLUSRCVR and CLUSSDR channel definitions. Post here.
Exactly what messages are ending up in the DLQ?
What errors are logged at both PR and FR?
_________________
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 |
|
|
| bkRaju |
| Posted: Tue Jul 17, 2012 2:02 pm Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
Bruce,
There are no logs at PR and FR end. As I said, the connectivity holds good. Ping of the channel and cluster paramaters on the channel defination looks good.
I would like to get more updates on 2119 error. Why the repos process sending MQADMIN messages to DLQ with 2119 errors?
If these messages are processd by repos proces, it shouldnt be the issue.
Please providfe more info.
DLQ message:
StrucId : 'MD ' Version : 2
Report : 0 MsgType : 8
Expiry : -1 Feedback : 0
Encoding : 273 CodedCharSetId : 819
Format : 'MQDEAD '
Priority : 0 Persistence : 1
BackoutCount : 0
ReplyToQ : ' '
ReplyToQMgr : 'PR1 '
** Identity Context
UserIdentifier : 'qmqm '
AccountingToken :
ApplIdentityData : ' '
** Origin Context
PutApplType : '7'
PutApplName : '206912/QMQM/AMQRRMFA '
PutDate : '20120516' PutTime : '11103724'
ApplOriginData : ' '
GroupId : X'000000000000000000000000000000000000000000000000'
MsgSeqNumber : '1'
Offset : '0'
MsgFlags : '0'
OriginalLength : '-1'
**** Message ****
length - 524 bytes
00000000: 444C 4820 0000 0001 0000 0847 5359 5354 'DLH .......GSYST'
00000010: 454D 2E43 4C55 5354 4552 2E43 4F4D 4D41 'EM.CLUSTER.COMMA'
00000020: 4E44 2E51 5545 5545 0000 0000 0000 0000 'ND.QUEUE........'
00000030: 0000 0000 0000 0000 0000 0000 4855 4252 '............FR1'
00000040: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000050: 2020 2020 2020 2020 2020 2020 2020 2020 ' '
00000060: 2020 2020 2020 2020 2020 2020 0000 0111 ' ....'
00000070: 0000 011D 4D51 4144 4D49 4E20 0000 0006 '....MQADMIN ....'
00000080: 616D 7172 726D 6661 2020 2020 2020 2020 'amqrrmfa '
00000090: 2020 2020 2020 2020 2020 2020 3230 3132 ' 2012'
000000A0: 3035 3137 3132 3338 3535 3133 0000 0001 '051712385513....'
000000B0: 0000 0024 0000 0001 0000 03F9 0000 0001 '...$............'
000000C0: 0000 0001 0000 0000 0000 0000 0000 0005 '................'
000000D0: 0000 0004 0000 0044 0000 158A 0000 0000 '.......D........'
000000E0: 0000 0030 C5E4 D9F4 F0F0 C1D8 D4E3 E2E3 '...0............'
000000F0: F0F1 6DF2 F0F1 F260 F0F3 60F1 F66D F1F4 '..m....`..`..m..'
00000100: 4BF5 F44B F2F3 4040 4040 4040 4040 4040 'K..K..@@@@@@@@@@'
00000110: 4040 4040 0000 0004 0000 0044 0000 157E '@@@@.......D...~'
00000120: 0000 0000 0000 0030 E2E8 E2E3 C5D4 4BE3 '.......0......K.'
00000130: C5D4 D7E4 E4C9 C44B 9498 9985 9796 A3F3 '.......K........'
00000140: 4B89 95A3 9981 4B81 85A7 974B 8396 944D 'K.....K....K...M'
00000150: F1F0 F0F0 F05D 4040 0000 0004 0000 0044 '.....]@@.......D'
00000160: 0000 158B 0000 0000 0000 0030 C5E4 D9F4 '...........0....'
00000170: F0F0 C1D8 D4E3 E2E3 F0F1 6DF2 F0F1 F260 '..........m....`'
00000180: F0F3 60F1 F66D F1F4 4BF5 F44B F2F3 4040 '..`..m..K..K..@@'
00000190: 4040 4040 4040 4040 4040 4040 0000 0004 '@@@@@@@@@@@@....'
000001A0: 0000 0028 0000 158D 0000 0000 0000 0014 '...(............'
000001B0: C5C5 D4E7 E7C3 D3E3 F4F3 4BC8 E4C2 D9C5 '..........K.....'
000001C0: E3F3 F140 0000 0006 0000 0048 0000 157C '...@.......H...|'
000001D0: 0000 0000 0000 0001 0000 0030 C5C5 D4E7 '...........0....'
000001E0: E7C3 D3E3 F4F3 4040 4040 4040 4040 4040 '......@@@@@@@@@@'
000001F0: 4040 4040 4040 4040 4040 4040 4040 4040 '@@@@@@@@@@@@@@@@'
00000200: 4040 4040 4040 4040 4040 4040 '@@@@@@@@@@@@ '
Thanks,. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jul 17, 2012 3:12 pm Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| bkRaju wrote: |
Bruce,
There are no logs at PR and FR end. As I said, the connectivity holds good. Ping of the channel and cluster paramaters on the channel defination looks good. |
Yes, there are error logs at both PR and FR qmgr. Do you mean that there are no errors logged for the times/dates in question? If so, say so.
Connectivity holds good is not mq terminology. I want to see the displays of your channel definitions and channel status at both ends. I want to see that the cluster is complete.
I want to see the display of cluster information known by the two ends.
_________________
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 |
|
|
| fjb_saper |
| Posted: Tue Jul 17, 2012 8:07 pm Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| Quote: |
2119 (0847) (RC2119): MQRC_NOT_CONVERTED
Explanation
An MQGET call was issued with the MQGMO_CONVERT option specified in the GetMsgOpts parameter, but an error occurred during conversion of the data in the message. The message data is returned unconverted, the values of the CodedCharSetId and Encoding fields in the MsgDesc parameter are set to those of the message returned, and the call completes with MQCC_WARNING.
If the message consists of several parts, each of which is described by its own CodedCharSetId and Encoding fields (for example, a message with format name MQFMT_DEAD_LETTER_HEADER), some parts may be converted and other parts not converted. However, the values returned in the various CodedCharSetId and Encoding fields always correctly describe the relevant message data.
This error may also indicate that a parameter to the data-conversion service is not supported.
Completion Code
MQCC_WARNING
Programmer response
Check that the message data is correctly described by the Format, CodedCharSetId and Encoding parameters that were specified when the message was put. Also check that these values, and the CodedCharSetId and Encoding specified in the MsgDesc parameter on the MQGET call, are supported for queue-manager conversion. If the required conversion is not supported, conversion must be carried out by the application.
|
The CCSIDs of the FR and the PR are "incompatible"
You need to either install the CCSID of the FR on the PR box (at OS level) or create a conversion table entry for said CCSID.
Have fun 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| bkRaju |
| Posted: Wed Jul 18, 2012 1:25 pm Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
exactly fjb_saper,
My suspection was true that something wrong with CCSID compatibilty between PR and FR. The PR built on AS400(iseries) and it's qmgr CCSID was originally set to 285 based out of UK. FR with CCSID 819 on Unix system.
Issue got fixed when CCSID of PR was cahnged to 037. All cluster updates looks fine now.
How to create a convertion table? and how to change at OS level on PR side? |
|
| Back to top |
|
|
| Vitor |
| Posted: Wed Jul 18, 2012 4:22 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| bkRaju wrote: |
| How to create a convertion table? and how to change at OS level on PR side? |
The conversion table is an OS artifact not an WMQ one, hence it can only be changed at the OS level.
Speak to your sys admin about how they want it created, and what their procedure is for installing it in the OS.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| bkRaju |
| Posted: Tue Jul 24, 2012 9:49 am Post subject: |
|
|
Centurion
Joined: 19 Aug 2008
Posts: 106
|
Thanks Vitor..
Good info and it adds learning to me  |
|
| Back to top |
|
|
|
|
