RE: Fixing bad data in a numeric field

Ron,

The fact that your data came from a System/36 (or S/36 environment)
could very easily explain the 'corrupted' packed fields.  Because the
S/36 defined its data within the programs (except for indexes), it was
common to not initialize all packed fields when a record was added to a
file.  Bad system design perhaps, but there is nothing in the system to
prevent it.

Somewhere, perhaps during a conversion, your packed fields got
translated from x'404040' to x'000000'.

This makes sense to me when I remember my S/36 days.

Regards,
Andy Nolen-Parkhouse

> On Behalf Of Klein, Ron
> Subject: RE: Fixing bad data in a numeric field
>
> I am very concerned about how the corruption had occurred also.  But
it
> seems that the majority of the corruption and probably all of it
occured
> during a conversion since the data goes up to 1999.  This was a S36
> package
> and still uses mostly S36 Cobol.  Recently though we have been
> implementing
> the reporting process in Sequel which is SQL based and when we
encounter
> one
> of these situations it generates huge joblogs.