|
I had another thought which may or may not be correct. The -m option specifies the format of the AS/400 data, right? Or is it the format that we want it converted to? I've been assuming the former. If so, can we use the DSPFFD field that has the CCSID? Should be easier than having to specify on the command line (especially since some of my files seem to have a different CCSID...) On our AS/400 at V4R2, I have: Field Level Information Data Field Buffer Buffer Field Column Field Type Length Length Position Usage Heading WHCSID PACKED 5 0 3 492 Both CCSID Field text . . . . . . . . . . . . . . . : Coded Character set Identifier Next, I wonder how useful is the buffer lengh on a packed field? We're converting to integers which means the length of our data isn't going to be the buffer length. If it's a 'P' field, shouldn't we use the field length instead? Finally, (off topic a bit) any easy way to define an SQL field type based on the buffer length or field length? I have a lot of files with a lot of fields, so it would be a nightmare to create all the tables manually. I tried dds2sql on the DDS of the file, but that was a disaster. Thanks. Sean Porterfield +--- | This is the LINUX5250 Mailing List! | To submit a new message, send your mail to LINUX5250@midrange.com. | To subscribe to this list send email to LINUX5250-SUB@midrange.com. | To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.