MQSeries.net :: View topic - Using second field as record identifier for CSV MessageSet

willlko · Posted: Thu May 10, 2007 11:23 pm Post subject:

Hi All,
Regarding: Message Set
Environment: Message Brokers Toolkit for WebSphere Studio - 5.0.8
I have had experience with message sets before. I typically create a Cobal copybook and import by creating a new Message Set Definition File within the project. Typically our flat file have a record indicator in the first field e.g. EDIFACT â€“ UNB UNA â€¦ The problem I have with this latest message it is the second field that determines the record structureâ€¦. Not the first..
Input File: CSV, comma declaimed with each record ending with â€œEnd of Line Characterâ€ and â€œNew Line Characterâ€ (reference to java for record delimiter â€œ\r\nâ€);

Example input document:
1234,A, Serial Number, Batch Number, Data
5678,B, Type, Location, Reference
AB12,C, 345/56 Sample Street3, City3, Country3,Other Data3
CD34,B, Type2, Location2, Reference2
AB78,C, 345/56 Sample Street5, City5, Country5,Other Data5
CD78,C, 345/56 Sample Street6, City6, Country6,Other Data6

Input Document Structure Notes:
The second field (of size 1) which contains either A,B or C indicates the record type.
Structure and group represented below (Its not pretty sorry):
A (1)
|---------B (1 or Many)
|---- C (1 or Many)
Structure of Sample document:
A
|---------B (1 or Many)
|--------C (1 or Many)
|---------B (1 or Many)
|--------C (1 or Many)
|--------C (1 or Many)

The issue:
At present I am not sure how to specify in the message set that the first field should be ignored and have the second field indicate the record type and allow it to be read correctly into the message set. This is the first document structure that has the recorded indicator located in the second field rather then the first.

The indented output after a â€œReset Content Descriptor should hopefully be translated as displayed below:(Note some tag names are same as sample data for readability)
<Segment_A>
<SerialNumber> Serial Number</SerialNumber>
<BatchNumber> Batch Number</BatchNumber>
<Data> Data</Data>
<Segment_B>
<Type> Type</Type>
<Location> Location</Location>
<Reference> Reference</Reference>
<Segment_C>
<Street> 345/56 Sample Street3</Street>
<City> City3</City>
<Country> Country3</Country>
<Other>Other Data3</Other>
</Segment_C>
</Segment_B>
<Segment_B>
<Type> Type2</Type>
<Location> Location2</Location>
<Reference> Reference2</Reference>
<Segment_C>
<Street> 345/56 Sample Street5</Street>
<City> City5</City>
<Country> Country5</Country>
<Other>Other Data5</Other>
</Segment_C>
<Segment_C>
<Street> 345/56 Sample Street6</Street>
<City> City6</City>
<Country> Country6</Country>
<Other>Other Data6</Other>
</Segment_C>
</Segment_B>
</Segment_A>