|
I have no idea why the field PWRADR would have been defined with the
*HEX CCSID; an error perhaps.?
The field PWRADR has CCSID 65535 which indicates that no conversion
of characters should occur. Thus if the CPYTOXLS is honoring the
request, which from the output would appear to be the case, then the
data in the Excel file is EBCDIC being presented as ASCII. If that
feature has an option to treat *HEX CCSID as a default CCSID, then
activate that feature. Otherwise two other options are to:
- create & use a VIEW which effects for that field:
CAST(PWRADR AS CHAR(46) CCSID 37) AS PWRADR
- ALTER TABLE MyLib/DupOfQASYPWJ5
ALTER COLUMN PWRADR SET DATA TYPE CHAR (46) CCSID 37
Regards, Chuck
--
All comments provided "as is" with no warranties of any kind
whatsoever and may not represent positions, strategies, nor views of my
employer
Fabio Kang wrote:
Hi Everyone, I am having problem converting one field with ip addressis
information using the tool CPYTOXLS., which I use and it is great.
I do the following:
1- DSPJRN JRN(QAUDJRN) ENTTYP(PW) OUTPUT(*OUTFILE) OUTFILFMT(*TYPE5)
OUTFILE(mylib/crtdupobj of QASYPWJ5)
2- CPYTOXLS FILE(mylib/crtdupobj of QASYPWJ5) TOFILE(myfile.CSV)
TODIR('/mydir')
Looking the file via SQL I can see the IP address field fine, field name
PWRADR (QASYPWJ5 Remote address), but after converting with CPYTOXLS±ÒÓKÒ±KãͱKã±ã@@@@@@@@@@@.
tool, the field look more like this in excell:
Any help will be appreciate.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
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.