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 » Message set 6.1 for integer element

Post new topic  Reply to topic
 Message set 6.1 for integer element « View previous topic :: View next topic » 
Author Message
vijayakumar
PostPosted: Thu Apr 28, 2011 11:04 am    Post subject: Message set 6.1 for integer element Reply with quote

Centurion

Joined: 01 Aug 2010
Posts: 101
I am using the message set which is having one local element name ID_NBR datatype as xsd:integer,length as 5 with default value of the local element as 0 in MB6.1 .

using MRM domain for output root which is parsed against message set .

code

Set OutputRoot.MRM.PRTCode.ID_NBR = cast(Environment.variables.NBR as Integer)

The Environment.variables.NBR value is actually '11779'

But in the output, it is coming like '00000'.

why it s coming like this.
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Apr 28, 2011 11:09 am    Post subject: Re: Message set 6.1 for integer element Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
vijayakumar wrote:
why it s coming like this.


What did you see in the user trace for this when you took one?
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
kimbert
PostPosted: Thu Apr 28, 2011 11:36 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
I agree with Vitor. Make sure that it is a debug-level user trace.
I suspect that your OutputRoot structure does not match the structure of the message definition. The user trace will tell you whether that guess is correct.
Back to top
View user's profile Send private message
vijayakumar
PostPosted: Thu Apr 28, 2011 11:51 am    Post subject: Reply with quote

Centurion

Joined: 01 Aug 2010
Posts: 101
If I convert the datatype as xsd:string and casting t to char as

Set OutputRoot.MRM.PRTCode.ID_NBR = cast(Environment.variables.NBR as char)

now the output is coming correctly as "11779"
Back to top
View user's profile Send private message
Vitor
PostPosted: Thu Apr 28, 2011 12:21 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
vijayakumar wrote:
now the output is coming correctly as "11779"


Well done you.

If you'd checked the assignment in a debug level user trace you wouldn't have had to guess (or get my illustrious associate to guess) what the problem was.

It's a useful thing to familiarise yourself with.
_________________
Honesty is the best policy.
Insanity is the best defence.
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 » Message set 6.1 for integer element
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.