Hmm.
I guess I'd start the discussion by showing a COBOL
layout, and then pointing to the pieces that would need
to be dealt with.
We'd need an object that took the layout as a create
arg. It would parse out all the fields, setting up
a array of field objects. Each field object would
have enough info to read/understand that field type.
I'd have a higher level structure that would take
into account the physical read/unpack of the data,
which would then be mapped back to the individual fields.
In the case of 'redefines', I'd need a higher level parent
object, then children that refer back to it, into pieces
of it. We can't just chunk out the data since either
object modifying it should be modifying the same
data.
In the case of 'occurs', we'd need arrays of objects.
If the data has no 'comp' fields, I can do an EBCDIC
to ASCII conversion of front to the entire record.
If not, we've got to deal with it against ranges of
bytes split by comp fields.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.