Re: sqlldr flaking out on ZONED and DECIMAL data

[Quoted] ZONED DECIMAL is numeric data with an implied decimal point. In COBOL it's PIC [Quoted] 9..V9...

I haven't had to use signed data so I'm not certain how it's handled, but IIRC [Quoted] it's the equivalent of COBOL's SIGN SEPARATE TRAILING. Note that 8.1.5 & 8.1.6 [Quoted] (initial release) have a bug in SQL*Loader's handling of ZONED DECIMAL data. I [Quoted] don't have the full details, I was just told that our planned upgrade to 8.1.6.1 [Quoted] would fix the problem, which was valid data being rejected for 'precision greater than allowed'.

my_element position(1,6) zoned(6,2) would read ASCII 123456 as 1234.56 hex = X'30, X'31, X'32, etc. Nothing complicated unless it's the sign & as I [Quoted] said I've never had to load signed data so I don't remember for sure how it's handled.

Mike Moore wrote:

> I am not sure if there is something wrong with sqlldr or something wrong
> with my data. This is because I don't know what "exactly" sqlldr is
> expecting to see. Frankly, the documentation is poor in this area. What I
> need is to see hex values for what is acceptable in ZONED or DECIMAL fields.
>
> I have created the data using SQL on an IBM mainframe from an IDMS database.
> Then I FTP the file onto my PC. Some of the fields are ( using COBOL terms
> here ) SIGNED ZONED DECIMAL, UNSIGNED ZONED DECIMAL, and COMP-3. I can't
> seem to get any of these to work in a consistent manner.
>
> All that I need to know is what SQLLDR is expecting to see when for example
> you
> use something like:
>
> my_element position(1,6) zoned(6,2),
>
> thanks,
> Mike
Received on Fri Mar 16 2001 - 18:56:21 CET