ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Extended decimal gettinf reduced to Null

Post new topic  Reply to topic
 Extended decimal gettinf reduced to Null « View previous topic :: View next topic » 
Author Message
Sumeet Chawla
PostPosted: Tue Jan 20, 2009 12:11 pm    Post subject: Extended decimal gettinf reduced to Null Reply with quote

Newbie

Joined: 20 Jan 2009
Posts: 7
Hi All

I have a fixed format message coming from Mainfarme with an Encoding and CCSID of 785 and 500. At the end of message a group of 16 bytes is repeated. Please find attached a snap shot of the same.

00000540: F0F6 F0F0 F0F0 F0F1 F0F0 F0F0 C0F0 F0F0 '060000010000{000'
00000550: F0F1 F0F0 F0F0 F0F1 F0F0 F0F0 C0F0 F0F0 '010000010000{000'
00000560: F0F1 F0F0 F0F0 F0F1 F0F0 F0F0 C0F0 F0F0 '010000010000{000'
00000570: F0F1 F0F0 F0F0 F0F1 F0F0 F0F0 C0F0 F0F0 '010000010000{000'
00000580: F0F1 F0F0 F0F0 F0F1 F0F0 F0F0 C0F0 F0F0 '010000010000{000'
00000590: F0F1 F0F0 F0F0 F0F1 F0F0 F0F0 C0F0 F0F0 '010000010000{000'
000005A0: F0F1 F0F0 F0F0 F0F0 F0F0 F0F0 C0F0 F0F0 '010000000000{000'
000005B0: F0F0 F0F0 F0F0 F0F0 F0F0 F0F0 C0F0 F0F0 '000000000000{000'
000005C0: F0F0 F0F0 F0F0 F0F0 F0F0 F0F0 C0F0 F0F0 '000000000000{000'
000005D0: F0F0 F0F0 F0F0 F0F0 F0F0 F0F0 C0F0 F0F0 '000000000000{000'
000005E0: F0F0 F0F0 F0F0 F0F0 F0F0 F0F0 C0F0 F0F0 '000000000000{000'
000005F0: F0F0 '00 '

The 16 Byte of Data which is repeated is accomodated under two fields in Message set first of which is a Extended Decimal with a 2 Byte precision and the second is a Integer of 5 Bytes

The value logically should be as follows.
First Field :- 0000010000{
Second Field :- 00001

In the ESQL code the Data gets converted to null values and hence no XML tags are formed.

The Trace says :-

Failed to navigate to path element because it does not exist. This resolved to 'CAST(NULL AS DECIMAL(11, 2) )'. The result was 'NULL'.

As the elements get a null value XML tags are not formed. Please suggest.
Back to top
View user's profile Send private message
kimbert
PostPosted: Tue Jan 20, 2009 1:38 pm    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
Quote:
Failed to navigate to path element because it does not exist
I think you are misinterpreting the trace output. If you insert a Trace node, you will probably find that the element is missing ( 'does not exist' ). There may be previous occurrences with non-null values, but the basic problem here is that your ESQL is attempting to reference a non-existent field in the tree.
Quote:
This resolved to 'CAST(NULL AS DECIMAL(11, 2) )
It's none of my business really, but I am surprised that you need to use CAST when the tree was created by the MRM parser. Especially since you are dealing with COBOL physical types. Why do you need it?
Back to top
View user's profile Send private message
Sumeet Chawla
PostPosted: Wed Jan 21, 2009 7:35 am    Post subject: Reply with quote

Newbie

Joined: 20 Jan 2009
Posts: 7
My observation

1) I am not able to provide you the trace because of restrictions. I am not misinterpreting the trace. The esql code is considering the value as null though it is coming as 0000010000{. Will redeploying the flows help out ?

2) Some developer coded it long time back thinking of what i don't know but yeah it really doesn't need a cast if physical type is an extended decimal.


Thanks Kimbert !!! I appreciate your help on this one !!!

Regards
Sumeet Chawla
Back to top
View user's profile Send private message
kimbert
PostPosted: Wed Jan 21, 2009 8:16 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
Quote:
I am not misinterpreting the trace
Oh yes you are!

That message means that the element does not exist in the message tree. The CAST statement is using NULL because NULL is the value of a non-existent ESQL path. Re-read my previous comments for suggestions on next steps.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » Extended decimal gettinf reduced to Null
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.