| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQ message failing at OTMA with reason code 326. |
« View previous topic :: View next topic » |
| Author |
Message
|
| samaritan7 |
 Posted: Tue Jul 10, 2012 4:45 am Post subject: MQ message failing at OTMA with reason code 326. |
 |
|
Newbie
Joined: 30 May 2012
Posts: 6
|
Hi ,
When i am testing with my appli team , the messages are failing with 326 reason code. 
When i checked the MSTR logs, i have seen that the sense code is 001A0003
When i searched for an explanation, got this
RACF RACROUTE VERIFY call failed for incorrect input user ID.
Now, i dont know what does this mean ?? 
Please help me on this... |
|
| Back to top |
|
 |
| bruce2359 |
| Posted: Tue Jul 10, 2012 5:00 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
Please post all of the relevant stuff logged to MSTR, not just 001A0003.
Post also the output from the application.
_________________
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 |
|
|
| samaritan7 |
| Posted: Tue Jul 10, 2012 5:15 am Post subject: |
|
|
Newbie
Joined: 30 May 2012
Posts: 6
|
| I am not getting any other log other than the IMS bridge name, tpipe name, and sense code... i tried to look for any other additional info above and below that timestamp ...but in vain |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jul 10, 2012 5:49 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| samaritan7 wrote: |
| I am not getting any other log other than the IMS bridge name, tpipe name, and sense code... i tried to look for any other additional info above and below that timestamp ...but in vain |
You have provided little/no useful information so far.
I've asked you to post (cut/paste) the relevant MSTR syslog entries - and/all of them. Please do so.
I found this http://www-01.ibm.com/support/docview.wss?uid=swg21248046 when I searched google for WMQ+001A0003.
So, you have found no other additional info? No application is executing when this error occurs? No app is abending? No application reporting (sysout) problems with its data? So, other than this one MSTR-logged event, there is no evidence whatsoever that there is a problem at all?
Where exactly did you look for other info? Only MSTRs syslog? Be precise in your answer? Don't say I've looked everywhere. Did you look in IMS regions? IRLM regions?
_________________
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 |
|
|
| bruce2359 |
| Posted: Tue Jul 10, 2012 5:57 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
And another basic question:
Has this application ever worked before? If yes, what has changed? WMQ, OTMA, application code, o/s, ...?
_________________
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 |
|
|
| samaritan7 |
| Posted: Tue Jul 10, 2012 6:08 am Post subject: |
|
|
Newbie
Joined: 30 May 2012
Posts: 6
|
Actually my scope for this setup is very less.
The front end is transmitting messages over cluster and it is hitting OTMA and i dont have anything else except for this OTMA logs to find out why is it failing.
CSQ2001I ABC1+ CSQ2QCP0 OTMA REJECTED MESSAGE - 843
APPLICATION ERROR, SENSE CODE=001A0003, XCFGNAME=MQXCF
XCFMNAME=DIPOD054 TPIPE=QN1005C3 |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Tue Jul 10, 2012 6:20 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
| samaritan7 wrote: |
Actually my scope for this setup is very less.
The front end is transmitting messages over cluster and it is hitting OTMA and i dont have anything else except for this OTMA logs to find out why is it failing.
CSQ2001I ABC1+ CSQ2QCP0 OTMA REJECTED MESSAGE - 843
APPLICATION ERROR, SENSE CODE=001A0003, XCFGNAME=MQXCF
XCFMNAME=DIPOD054 TPIPE=QN1005C3 |
I suggest that you contact the sysprogs that support IMS and OTMA, to get them involved.
_________________
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 |
|
|
| Mr Butcher |
| Posted: Tue Jul 10, 2012 10:15 pm Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
|
| Back to top |
|
|
| bruce2359 |
| Posted: Wed Jul 11, 2012 5:46 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9469
Location: US: west coast, almost. Otherwise, enroute.
|
I'm going to guess that you have little experience with WMQ on z/OS, and less experience with z/OS, and problem-determination in the z/OS world.
xxxxMSTR is the name of the qmgr, and the address space where the qmgr software executes. The good and the bad for this qmgr are written to MSTRs syslog.
In your case, you have other software in other address spaces (plural) interacting (XCF, IMS, etc.).
It appears you need assistance from z/OS-experienced people who can help you diagnose this. Have you sought this kind of help?
_________________
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 |
|
|
| cicsprog |
| Posted: Thu Jul 12, 2012 8:49 am Post subject: |
|
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
Paste the below in a TXT file and add a shortcut to your desktop to the TXT file for future reference.
It looks as if your IMS has OTMA security checking. The userid associated with the message does not have authority for use of the OTMA bridge and ability to run IMS transactions. You will probably have the original message going to the DLQ and another messages in the DLQ with a message payload containing a DFSxxxxx message. Bottom line is a security issue.
OTMA Sense Codes for NAK Messages
Sense Code: 001A
Reason Codes:
_____________________________________________________________
Hex: Decimal: Explanation:
______________________________________________________________
x'03' 03 RACF INIT failure (DFSYTIB0)
x'15' 21 Msg segment length error
(see apar PQ32402)
x'1F' 31 Error with conversation. A RC greater
than 4 was returned for a call to
DFSCON00
X'16' 22 Invalid security option specified in the
message prefix.
X'17' 23 Invalid command from an OTMA client.
See DFS1285E.
X'18' 24 Transaction currently not available for
use. See DFS3470E.
X'19' 25 SMB transaction/LTERM is stopped.
See DFS065.
X'1A' 26 Invalid CPIC transaction. See
DFS1286E.
X'1B' 27 Invalid remote destination (RCNT). See
DFS1287E.
X'1C' 28 Invalid CNT name specified. See
DFS1288E.
X'1D' 29 SMB not found. See DFS064.
X'1E' 30 Invalid security. See DFS1292E.
X'1F' 31 System error requested.
X'20' 32 System error message.
X'21' 33 User error message.
X'22' 34 Single-segment message. See
DFS1290E.
X'23' 35 All messages discarded. See DFS249.
X'24' 36 Null segment sent. See DFS249. One
cause for this error maybe the length
specified on the MSGLEN key
parameter of the IXCMSGO macro
does not match the length of the
OTMA data. No extra or null data can
be padded at the end of the application
data section.
X'25' 37 Queue overflow as unsuccessful insert.
X'26' 38 Commit mode 0 not allowed for IMS
conversational or Fast Path
transaction. See DFS1291E.
X'27' 39 IMS conversation is stopped, similar to
an /EXIT command.
X'28' 40 DFSNPRT0 requested that a message
be rerouted to a remote system, but
failed. See DFS064.
X'29' 41 DFSNPRT0 requested that a message
be rerouted to a remote system, but
failed. See DFS070.
X'32' 50 The length specified in the application
data section or the segment length for
multi-segment input data exceeds the
length specified on the MSGLEN key
parameter of the XCF IXCMSGO
macro.
DFS064 08:31:04 DESTINATION CAN NOT BE FOUND OR CREATED
– Explanation: The first eight characters of the input are not recognized as a
valid transaction, logical terminal name, or command.
– Usual cause: The transaction name specified in the input request is not
recognized by the target IMS system. |
|
| Back to top |
|
|
| samaritan7 |
| Posted: Mon Jul 23, 2012 11:25 am Post subject: |
|
|
Newbie
Joined: 30 May 2012
Posts: 6
|
| bruce2359 wrote: |
I'm going to guess that you have little experience with WMQ on z/OS, and less experience with z/OS, and problem-determination in the z/OS world.
It appears you need assistance from z/OS-experienced people who can help you diagnose this. Have you sought this kind of help? |
Hi bruce,
you were right ... i am a newbie... but i got accustomed to those codes associated with 001a sense code... But i am not exactly sure what 0003 would mean in 326 and hence was not able to confirm the issue exactly.
Hi cicsprog ,
the DFS064 is for sense code of 001D and i am not sure of the DFS for the 0003 sense code...so i forgot to check for that in the DLH.
|
|
| Back to top |
|
|
| cicsprog |
| Posted: Mon Jul 23, 2012 12:55 pm Post subject: |
|
|
Partisan
Joined: 27 Jan 2002
Posts: 347
|
CSQ2001I &MQO1 CSQ2QCP0 OTMA REJECTED MESSAGE - 004
APPLICATION ERROR, SENSE CODE=001A0003, XCFGNAME=IMSOTMA
XCFMNAME=SOPT TPIPE=CSQ00057
A x'03' 03 RACF INIT failure (DFSYTIB0)
Message 1 in the DLQ:
00000000 : 0020 0B00 C4C6 E2F1 F2F9 F2C5 40E2 C5C3 `....DFS1292E SEC`
00000010 : E4D9 C9E3 E840 E5C9 D6D3 C1E3 C9D6 D540 `URITY VIOLATION `
Message 2 is the actual message in the DLQ:
00000000 : 029F 0000 D5E2 D6D7 D9E2 D740 404C 8289 `....NSOPRSP <bi`
00000010 : 9393 8995 876D A399 8195 A281 83A3 8996 `lling_transactio`
00000020 : 956D 9985 A297 9695 A285 4086 9996 947E `n_response from=`
00000030 : 7FE4 C3E2 D97F 6E4C 9985 A297 9695 A285 `"UCSR"><response`
00000040 : 6E4C 9481 9581 8785 9485 95A3 6E4C 8485 `><management><de`
...
... continue dump of msg data
...
This is from our system. The userid that the message was created under does NOT exist in RACF - thus the failure. The most common reasons for this type of a problem are:
1) The userid that the message was created under doesn't exist in RACF. This is common because the message is created from a non-mainframe MQ and delivered to a mainframe system with a security manager like RACF and the userid is not in the security manager.
2) Another common issue is that the IMS has security checking enabled and the userid associated with the message does not have the security permissions to run the IMS transaction. |
|
| 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
|
|
|
|
