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 » MultiPart Message (COBOL Copy book)

Post new topic  Reply to topic
 MultiPart Message (COBOL Copy book) « View previous topic :: View next topic » 
Author Message
rsashi
PostPosted: Thu Oct 23, 2008 10:13 am    Post subject: MultiPart Message (COBOL Copy book) Reply with quote

Apprentice

Joined: 29 Jan 2004
Posts: 35

Hi,

I am dealing with COBOL copy book.I get a large file with data which needs to be parsed and mapped only for few output elements.I'm hoping someone can help me in designing right way .

If we open the file , data will be structured like this:
- common header/envelope - fixed length (Only one header record)
- Data record - fixed length: (multiple records)
- Trailer record - fixed length : (Only one trailer record)

I am planning of using File nodes to deal with files.I need Your valuable responses for below questions,

1. Do i need to create multiple message sets. (One for header, one for data and one for Trailer) ?
2. How to identify the type of record in message flow.(Header or Data or Trailer)?
3. When i import COBOL book into message set...do i need to select CWF as Binary.(Data willcome from Main frame system) .
4. What will be the right design for my requirements ?

Your valuable thoughts are much appreciated.
Thanks
Back to top
View user's profile Send private message
rsashi
PostPosted: Fri Oct 24, 2008 8:18 am    Post subject: Reply with quote

Apprentice

Joined: 29 Jan 2004
Posts: 35

Let me know if the information i have provided is not clear.(Sorry)....let me know i can responde back with more details.Need your input's....its kind off urgent.
Thanks.
Back to top
View user's profile Send private message
kimbert
PostPosted: Thu Oct 30, 2008 4:26 am    Post subject: Reply with quote

Jedi Council

Joined: 29 Jul 2003
Posts: 5542
Location: Southampton

Quote:
1. Do i need to create multiple message sets. (One for header, one for data and one for Trailer) ?
No, a single message set is fine. Just import your COBOL copybooks and you should end up with one message ( in the import wizard, make sure that you specify which element to define as a message). Afterwards, if you examine the message, its top-level structure should be header/body/trailer.
Quote:
2. How to identify the type of record in message flow.(Header or Data or Trailer)?
The message tree will contains the name of the parsed element. But your message flow logic should be designed to expect a header, then a repeating body, then a trailer, as explained in my answer to question 4 below.
Quote:
3. When i import COBOL book into message set...do i need to select CWF as Binary.(Data willcome from Main frame system) .

Yes, CWF is the correct physical format.
Quote:
4. What will be the right design for my requirements ?
If the file did not have the header/trailer, then I would advise using the Parsed Record Sequence feature of the FileInput node. But you cannot use it when your file has headers/trailers.

Instead, you need to do this:
- In the FileInput node, set Parse Timing to 'On Demand'
- Use the techniques outlined here for handling large messages: http://www-128.ibm.com/developerworks/websphere/library/techarticles/0505_storey/0505_storey.html

The FileInput node is smart enough not to read the entire file into memory all at once. Instead, it will stream portions of the file into memory as they are needed.
Back to top
View user's profile Send private message
mqpaul
PostPosted: Tue Nov 04, 2008 3:49 am    Post subject: Typical CCSID and Encoding for mainframes. Reply with quote

Acolyte

Joined: 14 Jan 2008
Posts: 66
Location: Hursley, UK

You probably already know this, so for the record, typical mainframe CCSIDs are 037 and 500 (both variations of EBCDIC), or a national language EBCDIC (which I can never remember ) if you need accented characters or currency symbols.

Typical mainframe Encoding is 785 (Big-endian with S390 floating point).

Broker defaults are for the machine where the broker runs. If that's on a distributed box and not the mainframe, you get ASCII CCSIDs and different encoding.

You need to specify the correct values on the FileInput node's Input message parsing panel.
_________________
Paul
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 » MultiPart Message (COBOL Copy book)
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.