| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| OTMA x'1A' |
« View previous topic :: View next topic » |
| Author |
Message
|
| Bhalchandra |
 Posted: Tue Jan 30, 2007 5:58 am Post subject: OTMA x'1A' |
 |
|
Newbie
Joined: 10 Aug 2006
Posts: 9
|
Can anybody tell me what does this error means?
Reason..................,
Code..................,00000146
Symbol................,OTMA x'1A' IMS detected error
How this can be handled? |
|
| Back to top |
|
 |
| Vitor |
| Posted: Tue Jan 30, 2007 6:13 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
Can you tell us:
Where you saw it?
What was happening at the time?
What software you're running? (I'm guessing some kind of interface into Weblogic or similar but only guessing)
What level of MQ you have?
And any other details that might give us a clue....?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| LuisFer |
| Posted: Tue Jan 30, 2007 8:20 am Post subject: Re: OTMA x'1A' |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
| Bhalchandra wrote: |
Can anybody tell me what does this error means?
Reason..................,
Code..................,00000146
Symbol................,OTMA x'1A' IMS detected error
How this can be handled? |
x'146' = 326 dec See the OTMA NAK , if i dont' remember bad it's a security issue |
|
| Back to top |
|
|
| LuisFer |
| Posted: Tue Jan 30, 2007 9:48 am Post subject: Re: OTMA x'1A' |
|
|
Partisan
Joined: 17 Aug 2002
Posts: 302
|
Sorry my last post is not correct.
| Bhalchandra wrote: |
Can anybody tell me what does this error means?
Reason..................,
Code..................,00000146
Symbol................,OTMA x'1A' IMS detected error
How this can be handled? |
http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/index.jsp?topic=/com.ibm.ims9.doc.otma/otma.htm
001A
Explanation:
IMS detected an error and canceled the message before putting it on the IMS queue for processing. Usually, an IMS message (accompanying the NAK) describes the problem.
Programmer response:
See the reason code that accompanies the NAK code.
Table 12 lists the reason codes.
Table 12. Reason codes associated with the 001A sense code Hex: Decimal: Explanation:
X'03' 03 RACF RACROUTE VERIFY call failed for incorrect input userid.
X'15' 21 The message segment length or ZZ field cannot be changed by DFSNPRT0 exit.
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. |
|
| Back to top |
|
|
| tleichen |
| Posted: Tue Jan 30, 2007 12:17 pm Post subject: Re: OTMA x'1A' |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
| Bhalchandra wrote: |
Can anybody tell me what does this error means?
Reason..................,
Code..................,00000146
Symbol................,OTMA x'1A' IMS detected error
How this can be handled? |
You did not say where this code came from and did not include the entire message. Anyway with OTMA, a X'1A' basically says that IMS NAKed the message for some reason. There is normally an IMS message accompanying the NAK that will detail the problem further. There is a reason code associated with the NAK. As I recall, there is a trick to this, because some reason codes are put out in decimal and have a bias for IMS. And some reason codes are put out in decimal in console messages, yet are in hex in the OTMA manual, so be careful. Consult the OTMA manual:
http://publib.boulder.ibm.com/infocenter/dzichelp/v2r2/topic/com.ibm.ims9.doc.pdf/dfsotmg3.pdf?noframes=true
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
| Bhalchandra |
| Posted: Sat Feb 10, 2007 2:41 am Post subject: |
|
|
Newbie
Joined: 10 Aug 2006
Posts: 9
|
Problem detected.
LL-VELD value in IIH header was short than expected. |
|
| 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
|
|
|
|
