Re: Null byte in source physical file

["rick baird" <rick.baird@xxxxxxxxx>]

This reminds me of something that's been bothering me for a while.

how does the OS differenciate between a x'00' and the beginnings of a
packed numeric field?

for instance:

0000
000F

represents a packed 0, 7 bytes long.  but it also would appear to have
a null value in position 1 (2 and 3 as well).

Curious minds want to know.

On 4/13/06, David Gibbs <david@xxxxxxxxxxxx> wrote:
> I encountered the oddest thing the other day ... I found a source
> physical file member, of DDS source for a print file (created RLU, I
> think), that had a null byte (x'00') in the MIDDLE of a record.
>
> It was on one of the marker lines ... "A*%%RI 00000".  The null byte was
> at the end of the text (after the last 0).
>
> This was NOT a fluke either ... a bunch of DDS source files encountered
> have this null byte.
>
> The source members are pretty old (created as demo data for
> Implementer), so I don't know if it was the remnants of a bug in RLU, or
> what.
>
> Pretty weird.
>
> david
>
> --
> Any decision, made in haste, is invariably flawed...
> regardless of the outcome.
> --
> 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.
>
>