|
On 15-Jul-2016 08:19 -0500, CRPence wrote:
On 15-Jul-2016 01:57 -0500, Nihat Ezer wrote:
The CCSID of the file (/tmp/trial.xml) was 819
then I changed it to 820
<<SNIP>>
Opening the file (/tmp/trial.xml) by the command of
DSPF STMF('/tmp/trial.xml'), I have noticed the following two
messages at the bottom of the screen:
<ed:> msg CPDB607 "CCSID 00820 not supported." […] "The CCSID was
changed to 500."
msg CPDB609 "File CCSID not valid." […] "The file Coded
Character Set Identifier (CCSID) was 00500, but the data in the
file looks like ASCII. A CCSID of 00819 is being used. <<SNIP>>
<<SNIP>> The specific CCSID assigned to a file must [errr... would
in most cases, best] reflect what is the actual data stored in the
file; the value must be supported, to effect worthwhile results. To
know what value to assign for the CCSID attribute of a file
requires knowing what data was placed in the file [in hex code
points] and what value also may be implied, by knowing how the data
was placed into the file and whence the data came. <<SNIP>>
Giving it a try to your suggestion, I have seen nothing changed:
o removed the file (/tmp/trial.xml) by the command of
RMVLNK OBJLNK('/tmp/trial.xml')
o ran my program that created the file with CCSID of 819
<<SNIP>>
The diagnostics file (mydebuglog.txt) and the file (trial.xml) are
attached to the mail.
Thank you,
Nihat.
<<SNIPped some 30 lines of post-signature text>>
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.