Jon, et al, they could always to a cpyf tofile(*print) outfmt(*hex) and
see where the field barriers and types fall...  Also, look at the hex
format of a dsppfm for field positioning and data typing - IFF you know
how to interpret what you're reading...:)  And this late in the day, I'm
not sure I know baudot from morse code! :)

Don in DC

Neal,

I suggest you either mail me the COBOL definition (or post it here) and
we'll translate it for you.

Currently you are translating "COMP" as meaning packed - which while it
would be true for COBOL/400 is not true for mainframe COBOL.  In mainframe
COBOL COMP means binary!  COMP is a short form in ANSI COBOL for whatever
the compiler implementer determines is the most efficient format.  It
therefore varies from platform to platform.

Jon Paris
Partner400

www.Partner400.com


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.