|
On Thursday 08 November 2001 4:17 pm, bvining@vnet.ibm.com wrote: > Just as a warning, treating the record as one large field could result > in mis-identifications. The asterisk has a value of x'5C' and this > value could easily be found in integer/binary fields within the record, > and potentially in packed fields (though this is not real likely if > the data was generated on an iSeries). To avoid this you would need > to use APIs such as List Fields (QUSLFLD) to determine which offsets > and lengths within each record correspond to character fields. > > Bruce Ray I don't know if would be of any use, but my CRTCSVDTA will convert a database file to .csv format by using the above technique of APIs & QUSLFLD. It already gives the option of specifying the delimiter, and replacing those found in character strings with an alternative, so it should be easy to have it replace all 'dodgy' characters if required. The routine works using the big program described file with a override to the selected external file as others have mentioned. See http://www.dbg400.net/crtcsv.html for details & source code download. Regards, Martin -- martin@dbg400.net jamaro@firstlinux.net http://www.dbg400.net /"\ DBG/400 - DataBase Generation utilities - AS/400 / iSeries Open \ / Source free test environment tools and others (file/spool/misc) X [this space for hire] ASCII Ribbon Campaign against HTML mail & news / \
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.