Re: loading EBCDIC with sqlload

Jim Finch (jbfinch_at_akron.infi.net) wrote:
>Jim Finch wrote:
>> I am also having problems with a WHEN clause. I am comparing columns 4:8
>> with 'BATCH' and never get it to equal eventhough I know there are
>> records that match. Do I have to convert 'BATCH' to EBCDIC?
>> > OPTIONS (direct=true)
>> > UNRECOVERABLE
>> > LOAD DATA CHARACTERSET WE8EBCDIC500
>> > INFILE '/home/ee18/data/buck.ebcdic' "FIX 64"
>> > BADFILE '/home/ee18/data/buck.bad'
>> > DISCARDFILE '/home/ee18/data/buck.dis'
>> > INSERT
>> >
>> > INTO TABLE BUCK001
>> > WHEN (4:8) = 'BATCH'
>I have the packed data converting. I am still having problems with thisk
>WHEN clause. I know that the data comming in does match this comparison.
>Does anywone have any pointers for me.

I'm not sure whether the CHARACTERSET conversion is applied at the point where the WHEN comparison is performed. You might be able to make a case that this is a bug in Loader. Or you can try doing the comparison in EBCDIC e.g.

   WHEN (4:8) = X'C2C1E3C3C8' However, I will point out that you are using Loader in a manner for which it was not designed i.e. loading data from a different platform than the one on which Loader executes. You can make it handle character data conversion but Loader has NO provision for recognizing number formats from another system. I'm surprised you were able to get the p.d. stuff to work as many of our UNIX Loader implementations seem to disagree with S/390 on details of packed representation. I can guarantee that you won't be able to load S/390 floats. And you won't be able to load S/390 binary integers if your UNIX platform uses "little-endian" ints like Intel and DEC.

/b

--
Bill Manry  -  IBM Products Division  -  Oracle Corporation
These are my opinions, not necessarily Oracle's.