Re: sequential file formats
- From: "theador" <Theador@xxxxxxxxx>
- Date: 27 Jul 2005 16:26:11 -0700
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.
.
- Follow-Ups:
- Re: sequential file formats
- From: William M. Klein
- Re: sequential file formats
- References:
- sequential file formats
- From: theador
- Re: sequential file formats
- From: William M. Klein
- Re: sequential file formats
- From: theador
- Re: sequential file formats
- From: epc8
- sequential file formats
- Prev by Date: Re: Telecommute Contracting
- Next by Date: Re: Diffence between two CICS READ ; FILE & DATASET
- Previous by thread: Re: sequential file formats
- Next by thread: Re: sequential file formats
- Index(es):
Relevant Pages
|