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 -> CSV optional field delimiters being omitted

Post new topic  Reply to topic
 XML -> CSV optional field delimiters being omitted « View previous topic :: View next topic » 
Author Message
BrisVegas
PostPosted: Thu Aug 05, 2004 5:49 pm    Post subject: XML -> CSV optional field delimiters being omitted Reply with quote

Novice

Joined: 05 Aug 2004
Posts: 14
Location: Brisbane, Australia

Hello (I'm a newbie - first post),

When outputting a CSV (MRM TDS) format, any unpopulated fields at the end of my records are being omitted, along with the delimiters. It only occurs at the end of the record. What I need to occur is that a delimiter appear for every field, regardless of where it is in the record.

POITEM,123,ABC,456,DEF,,,789,GHI*
vs.
POITEM,123,ABC,456,DEF,,,789,GHI,,,,*

I've been trolling this forum and also the google groups, but I can't find any specific workarounds for this. I am using MQSI 2.1 with CSD3. No chance of upgrading to v5 anytime soon.

I appreciate anyone's help!
Back to top
View user's profile Send private message
kirani
PostPosted: Thu Aug 05, 2004 10:05 pm    Post subject: Reply with quote

Jedi Knight

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

Is it possible to upgrade the CSD? Can you explain the properties for your MRM-TDS elements and Type?
_________________
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
BrisVegas
PostPosted: Thu Aug 05, 2004 10:41 pm    Post subject: Reply with quote

Novice

Joined: 05 Aug 2004
Posts: 14
Location: Brisbane, Australia

I think we'd be ok to go to a new CSD if that would help. I've not been here too long, but pretty sure they put CSD3 on recently.

My message definition is heirachical. Delimiter for the whole message set is defined as tilde "~". Separate messages are built for each of PO, Invoice, Receipt, ASN etc.. PO is similar to below:-

PO_TYPE - Sequence, Closed, All Elements Delimited, Delimiter <U+002A><U+000D><U+000A> ie. "* <CR><LF>")
--POHDR_TYPE - Sequence, closed, Tagged Delimited, TDS "~", Delimiter <U+002A><U+000D><U+000A> ie. "* <CR><LF>"
----POMARKER
--POBDY_TYPE - Sequence, closed, Tagged Delimited, TDS "~", Delimiter <U+002A><U+000D><U+000A> ie. "* <CR><LF>"
----POHEADER - Sequence, Closed, All Elements Delimited, Delimiter <U+002A><U+000D><U+000A> ie. "* <CR><LF>"
----POPARTY (repeats) - "
----POREF (repeats) - "
----POITEM (repeats) - "
----POITMREF (repeats) - "
--POFTR_TYPE - Sequence, closed, Tagged Delimited, TDS "~", Delimiter <U+002A><U+000D><U+000A> ie. "* <CR><LF>"
----POMARKER - Sequence, Closed, All Elements Delimited, Delimiter <U+002A><U+000D><U+000A> ie. "* <CR><LF>"

eg.
POMARKER,0001,StartPO,New,1.3*
POHEADER,0001,Buyer,Supplier,$30.00,$3.00*
POPARTY,0001,Buyer,10 Main St,,,,*
POPARTY,0001,Supplier,10 High St,,,,*
POREF,0001,Quote,Q0001*
POITEM,0001,01,Stapler,,,$15.00,$1.50,,,*
POITMREF,0001,01,Quote,Q0001,01*
POITEM,0001,02,Hole Punch,,,$15.00,$1.50,,,*
POITMREF,0001,01,Quote,Q0001,02*
POMARKER,0001,EndPO,New,1.3*
Back to top
View user's profile Send private message
Ramphart
PostPosted: Thu Aug 05, 2004 11:38 pm    Post subject: Reply with quote

Disciple

Joined: 21 Jul 2004
Posts: 150
Location: South Africa, JHB

I'm got the same result when I did a CSV TDS MRM exercise and I'm on CSD07. Dont think the CSD will sort it out.

My work around was to assign a value to the last field in the message set like a space or something or 0 for instance if it is a numeric field. All the preceeding empty commas will then be generated.

Hope this helps.
_________________
Applications Architect
Back to top
View user's profile Send private message
kimbert
PostPosted: Fri Aug 06, 2004 1:18 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

This has been fixed in v5.0 with a message set flag 'Suppress Absent Element Delimiters'. I realise that's not much use to you, because you can't upgrade, but it may help somebody searching the forum for information about the same problem.
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 -> CSV optional field delimiters being omitted
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.