| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| convert pipe-delimited input messages into a MRM on WMB6.1 |
« View previous topic :: View next topic » |
| Author |
Message
|
| yhuang |
 Posted: Tue Feb 03, 2009 11:47 am Post subject: convert pipe-delimited input messages into a MRM on WMB6.1 |
 |
|
Newbie
Joined: 03 Feb 2009
Posts: 5
|
I have to convert pipe-delimited input messages into a target COBOL message set on WMB 6.1.
Input fields are all variable in size but go to a fixed size in the output COBOL copybook.
Here are the sample messages:
Input message: P|000|UL1234567|+|2988|+|231|testing
Output message: P000 UL1234567 +00002988 +00000123testing
I would like to get help on these:
1. How to build message definition file for TDS type input message set? 2. What does ESQL code look like to build a target COBOL message set from this delimited message
3. How to build COBOL copybook for output message set?
Thanks a lot for the help! |
|
| Back to top |
|
 |
| kimbert |
| Posted: Tue Feb 03, 2009 12:15 pm Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
In the best tradition of recipe books everywhere, "You will need..."
1. A message set with a TDS physical format, to parse the message
2. A message set with a TDS physical format, to write the message
3. Some ESQL/Java/Mapping logic to map the input message fields to the output message fields, and to set up the Properties folder for the writing.
Hints:
- You do not need CWF for this. TDS can write a fixed-length message for you, as long as it does not use advanced stuff like byte alignment of structures. Since you do not have a copy book, you probably just assumed that 'fixed-length' means 'CWF'.
- If your input logical structure is identical to your output logical structure, you can use a single message set with two TDS physical formats. In this case, your mapping code will consist of setting OutputRoot.Properties.MessageFormat to 'TDSFixedLength' or whatever you call your second TDS physical format.
| Quote: |
| What does ESQL code look like to build a target COBOL message set |
Ummm. You do not build a message set using ESQL! You use ESQL/Mapping nodes/Java/XSLT to create or modify a message tree |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Tue Feb 03, 2009 12:17 pm Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I think you are very confused by the concept of a message set. It is a model of a message not the message itself.
I think you should get some training in the product before atempting to use it in anger.
As a minimum, look at the samples that are included with the toolkit.
Your input is a tagged delimited message (the | is the delimiter). there isa sample message flow that deals with TDS mesages.
Your output can easily be assembled from the parsed components of the input message but (and this is the important bit) if you are going to be sending this to a mainframe or iSeries then there should already be a Cobol Copybook of the format thay are expecting. Get that and import it into a message set to create the model they are expecting.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| yhuang |
| Posted: Wed Feb 04, 2009 1:01 pm Post subject: |
|
|
Newbie
Joined: 03 Feb 2009
Posts: 5
|
 Thanks so much for the help. Finally, I have figured it out. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
