Re: sequential file formats

Your requests for "hex dumps" of files isn't getting many replies. I know that
it isn't something that I am about to try and do. What you really SHOULD be
asking for (IMHO) is references to online documentation. This will (again in my
opinion) be a much better way of finding out how different compilers and
run-times handle different "things".

For example,
Check out how all the different systems handle:
COMP-1, COMP-2, COMP-3, COMP-4, COMP-5, and COMP-6 (depending upon which
they have)
COMP
Other floating-point (if available)
Binary (big-endian/little-endian among other things)
sign-nibbles (Packed-Decimal and Usage Display)
UTF-16, DBCS, other - for USAGE NATIONAL (if supported)
ASCII vs EBCDIC (or other) for USAGE DISPLAY
Do they support BIT data? (or Boolean)
Do they support unsigned packed-decimal

also, references to "compiler options/directives" that impact sequential file
formats. See (for a good starting place)
http://www.talsystems.com/tsihome_h...oads/C2IEEE.htm

and

"Introduction to COBOL Numeric Data Types
Michael Mattias has created a text and graphics based introduction to COBOL
numeric data types. It was designed for intermediate to advanced programmers not
familiar with the COBOL language or COBOL numeric data storage. A Windows Write
or compatible word processor is recommended, but an ASCII text file format is
also included). The PKZIP format file includes an executable program file as
well as PB 3.2 source code. This file is Copyrighted but free for personal use.
A compiler is NOT required to use this product.
http://www.flexus.com/ftp/cobdata.zip

--
Bill Klein
wmklein <at> ix.netcom.com
"theador" <Theador@xxxxxxxxx> wrote in message
news:1122506771.018520.173960@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> epc8@xxxxxxxx wrote:
>
>> Then dealing with the differences in record structure will be the
>> *least* of your problems. Coping with the myriad ways of encoding the
>> actual data is much more difficult.
>>
>> The easiest and most reliable way of moving data from COBOL X to COBOL
>> Y is via text files in which all of the digits in a number and its sign
>> (if present) are explicitly represented.
>
> Do you have some specific examples of different ways that different
> compilers encode data when writing to a sequential file? I would be
> especially interested in hex dumps of the differences rather than just
> a discussion. I am not doubting you, I would just like to see the
> actual examples. One that I am aware of is that IBM COBOL on AIX
> encodes the sign digit of COMP3 data differently than microfocus or IBM
> COBOL on zOS. I dont currently have access to those compilers so I am
> afraid I can not provide the hex dumps.
>
> Theador.
>


.

Relevant Pages

  • Re: IBM S/390 memory model and COBOL
    ... I have been told that the earliest COBOL compilers created Assembler Language, rather than object code. ... the letter designations were intended to specify the minimum storage required to run the ...
    (comp.lang.cobol)
  • Re: Supress Option List
    ... > This is my memory / knowledge on the subject of IBM COBOL compilers: ... > written in COBOL, so I had to learn that on my own. ... > compilers IBM offered that conformed to the 1968 ANSI COBOL Standard. ...
    (comp.lang.cobol)
  • Re: Is Micro Focus doomed?
    ... > of your first additional costs. ... both Fujitsu and MF are full fledged compilers, ... If I cannot use one of the "real" Cobol ... the customer has, to allow them to try it out free. ...
    (comp.lang.cobol)
  • Re: Interesting take on Paradigms (OO vs Procedural)
    ... describe -- or you can use procedural only compilers to write OO style ... synergy obtained when you create objects. ... The code representation is only ONE aspect of it." ... If I do that with COBOL 68 I don't have any synergy..." ...
    (comp.lang.cobol)
  • Re: GOBACK (was: Perform Thru/Go to vs. Perform - Compile Speed
    ... providing specific data to explain how you determine "most popular compilers". ... look to see which compilerare being used today to produce AND maintain COBOL ... For example (just to talk about IBM COBOL compilers) ... > This shows 94% of professional programmers are using IBM or MF. ...
    (comp.lang.cobol)