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 » XML-DTD to TDS format.

Post new topic  Reply to topic
 XML-DTD to TDS format. « View previous topic :: View next topic » 
Author Message
Ajju.
PostPosted: Thu Nov 14, 2002 2:42 pm    Post subject: XML-DTD to TDS format. Reply with quote

Voyager

Joined: 26 Jul 2002
Posts: 77

Hi,
I have a question.
When i Import a DTD in my message set do i need to use all elements in that DTD in my message or can i use only required elements in my message considering my message has XML and TDS format at output.

I am applying XML and TDS format layer to my out message. and the reason i am asking this question is that if suppose i import a DTD with 100 elements in it and construct a message with just 1 feild in it with TDS format i cannot deploy my stuff .. as it gives me error that TDS parsing error for all remaining feilds where i have not applied any TDS properties.




here is the error:


BIP1836E: The create wire format descriptor operation has not completed successfully.

The create wire format descriptor operation encountered one or more errors. A report file, (XXXStag.log), has been created in C:/Program Files/IBM/WebSphere MQ Integrator 2.1/log/ on the Configuration Managers machine.

See the XXXStag.log file for details of the error.




Thanks in adv,
Ajju.
Back to top
View user's profile Send private message
kirani
PostPosted: Thu Nov 14, 2002 7:29 pm    Post subject: Reply with quote

Jedi Knight

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

I guess your input message should have required elements only. You cannot output two wire format messages at the same time, i.e. XML and TDS.
Could you post the contents of XXXStag.log file here? I'd recommend that you use two different message sets for this. First message set will have XML wire format and second will have TDS.
_________________
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
Ajju.
PostPosted: Fri Nov 15, 2002 5:34 am    Post subject: Reply with quote

Voyager

Joined: 26 Jul 2002
Posts: 77

thanks Kiran,
well i need only TDS output and i have applied XML output just for debug purpose and then i switch the output using

OutputRoot.Properties.Format='XML' or 'TDS';

here is ther error

Extracting Type Members
Extracting Type Members
Extracting Type Members
Extracting Type Members
Extracting Type Members
Extracting Values
Beginning Indexing..

Creating Member IDs to Tags Index Table.
Creating Value Indexes to Tag Index table.

Beginning Validation..

Validating Project
Validating Types
ERROR: TDSValidator::ValidateType:
Invalid content value - types with Data Element Separation attribute = Fixed Length
must have content = CLOSED.
(Type ID: t_OtherOrPriorPolicy_cmType)
Return Code: -95

ERROR: TDSValidator::ValidateTypeMemberSimpleElement:
Elements of a non-Boolean simple type in a type with Data Element Separation attribute = Fixed Length
must have one of the following attributes set:
Element Level - Length
Type Member Level - Length Reference
(Element ID: PolicyCd)
(Type ID: t_OtherOrPriorPolicy_cmType)
Return Code: -80

ERROR: TDSValidator::ValidateTypeMemberSimpleElement:
Elements of a non-Boolean simple type in a type with Data Element Separation attribute = Fixed Length
must have one of the following attributes set:
Element Level - Length
Type Member Level - Length Reference
(Element ID: PolicyNumber)
(Type ID: t_OtherOrPriorPolicy_cmType)
Return Code: -80

ERROR: TDSValidator::ValidateTypeMemberSimpleElement:
Elements of a non-Boolean simple type in a type with Data Element Separation attribute = Fixed Length
must have one of the following attributes set:
Element Level - Length
Type Member Level - Length Reference
(Element ID: LOBCd)
(Type ID: t_OtherOrPriorPolicy_cmType)
Return Code: -80

ERROR: TDSValidator::ValidateTypeMemberSimpleElement:
Elements of a non-Boolean simple type in a type with Data Element Separation attribute = Fixed Length
must have one of the following attributes set:
Element Level - Length
Type Member Level - Length Reference
(Element ID: com.onebeacon_PriorCarrier)
(Type ID: t_OtherOrPriorPolicy_cmType)
Return Code: -80

ERROR: TDSValidator::ValidateTypeMemberSimpleElement:
Elements of a non-Boolean simple type in a type with Data Element Separation attribute = Fixed Length
must have one of the following attributes set:
Element Level - Length
Type Member Level - Length Reference
(Element ID: Surname)
(Type ID: t_PersonName_cmType)
Return Code: -80

ERROR: TDSValidator::ValidateTypeMemberSimpleElement:
Elements of a non-Boolean simple type in a type with Data Element Separation attribute = Fixed Length
must have one of the following attributes set:
Element Level - Length
Type Member Level - Length Reference
(Element ID: GivenName)
(Type ID: t_PersonName_cmType)
Return Code: -80

........................

Validating Messages

Trace Info
===========
EXCEPTION: TDSValidator::Validate:
TDS Validation stopped because there are too many errors.
101 errors
0 warnings
Return Code: -1


its giving error for all elements which i am not using in my newly constructed message, and this elements are imported using the DTD and is avaiable in the messageSet but not used in message.

Thanks for your help,
Ajju.
Back to top
View user's profile Send private message
kirani
PostPosted: Fri Nov 15, 2002 9:20 am    Post subject: Reply with quote

Jedi Knight

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

Ajju,
I guess you are getting this error at deploy time, correct?
If you look at ERROR text it will tell you what's wrong with the messageset. You should specify length for each TDS element when Data Element separation attribute is set fixed length.

To check whether your input message is correct or not, you should parse your input message using MRM-XML in MQInput or RCD node after successful deploy.
_________________
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
Ajju.
PostPosted: Fri Nov 15, 2002 1:11 pm    Post subject: Reply with quote

Voyager

Joined: 26 Jul 2002
Posts: 77

Thanks Kiran,
I got it... it was element properties error.
no length defined for some of the fixed element lenth feilds also some of the tag name was missing.

Thanks,
Ajit.
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 » XML-DTD to TDS format.
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.