Subfiles, no line end in .dat

[Jeff Hoffman]

Hi

Cobol does not worry about LF all you have to do is define the record size 
and define the correct data types, although I agree putting in a LF would 
make it more visually readable. Just a thought you might consider creating 
portable subfiles, that way the data storage definitions would be more 
consistent,


Jeff

PS      If you do add a LF character to define the end of the record, do 
not forget to include it in you cobol FD.
         If you define packed decimal fields, these can generate null 
characters, and some unix commands/utilities strip these out (eg vi).

PPS     I am getting good with cobol these days ...sigh


At 08:59 PM 26/09/2005, Elisabeth wrote:
>Dear All,
>
>migrating from MPE / IMAGE / KSAM to PH 843D under UX and Eloquence, we
>were quite happy with the pilot part of the system, until we tried to
>access a QTP-written subfile with COBOL.
>
>Even printed on screen or transferred to Excel the .dat file showed the
>same data jumble; the records are not separated and the data just flows
>on and on. Obviously only PH modules see the line end and can discern
>individual records.
>
>Apologies in advance - this one must have come up before - only I
>couldn't find anything relevant...
>
>Elisabeth Corsten
>EC Datentechnik GmbH
>Germany
>
>
>
>
>--
>= = = = = = = = = = = = = = = = = = = = = = = = = = = =
>Mailing list: powerh-l at lists.sowder.com
>Subscribe: "subscribe" in message body to powerh-l-request at lists.sowder.com
>Unsubscribe: "unsubscribe <password>" in message body to 
>powerh-l-request at lists.sowder.com
>http://lists.sowder.com/mailman/listinfo/powerh-l
>This list is closed, thus to post to the list you must be a subscriber.