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 » Problem with 0x300000D field type

Post new topic  Reply to topic
 Problem with 0x300000D field type « View previous topic :: View next topic » 
Author Message
pmarie
PostPosted: Mon Aug 19, 2002 12:03 am    Post subject: Problem with 0x300000D field type Reply with quote

Novice

Joined: 04 Apr 2002
Posts: 23

I have created a message flow which inputs a message with a TDS physical format and outputs it with a CWF physical format (without any other changes). I have a difficulty with one of the message fields, which is considered as (0x300000D) in the logical format, while other fields are considered as (0x300000B) (according to the message trace produced by a trace node). For that reason, the output node fails to write the message out (reason given: the logical tree does not match the message definition, because of that field).
I do not know what (0x300000D) means and have no idea why this field was read as (0x300000D) instead of (0x300000B) like others.
Can anybody help me? Thanks.

Patrick MARIE


Last edited by pmarie on Mon Aug 19, 2002 3:46 am; edited 1 time in total
Back to top
View user's profile Send private message
ksilpaa
PostPosted: Mon Aug 19, 2002 1:19 am    Post subject: Reply with quote

Novice

Joined: 17 Dec 2001
Posts: 10

dd
Back to top
View user's profile Send private message
kirani
PostPosted: Mon Aug 19, 2002 8:51 am    Post subject: Reply with quote

Jedi Knight

Joined: 05 Sep 2001
Posts: 3779
Location: Torrance, CA, USA

Could you print the ExceptionList here?
The problem could be because of the field not getting set in Output message (CWF format). Make sure the mapped field is present in the input message.
_________________
Kiran


IBM Cert. Solution Designer & System Administrator - WBIMB V5
IBM Cert. Solutions Expert - WMQI
IBM Cert. Specialist - WMQI, MQSeries
IBM Cert. Developer - MQSeries

Back to top
View user's profile Send private message Visit poster's website
pmarie
PostPosted: Mon Aug 19, 2002 8:55 am    Post subject: Reply with quote

Novice

Joined: 04 Apr 2002
Posts: 23

This problem is now fixed. It was due to the fact that I had unwillingly included a blank at the front of the name of the field when defining it in the Control Center: " Ville" instead of "Ville".
This blank wasted about 3 hours of my time.
Sorry...

Patrick MARIE
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 » Problem with 0x300000D field type
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.