|
How is your database defined? You indicate that the database value is 3C (I
assume x'3C') but EBCDIC characters are x'40' and above, so it's not
EBCDIC. It's not Unicode or UTF8 as x'003C'/x'3C' is '<'. What is making
you think that x'3C' is a Latin small letter O with circumflex?
Bruce Vining
On Tue, Jan 22, 2013 at 10:32 AM, Michael Schutte <mschutte369@xxxxxxxxx
wrote:
I'm having trouble finding the correct CCSID. I'm using Scott Klement'shttp://www-03.ibm.com/systems/resources/systems_i_software_globalization_pdf_cp00819z.pdf
pdf for writing directly to the IFS.
http://www.scottklement.com/rpg/ifs_ebook/ifs_ebook.pdf
My trouble is... we have an address for an order that has a value of
RUE LOUIS CATY Nô108
Notice the ô
In the database file it's a value of 3C. But it appears when the data is
written to the ifs.
Using 819 hex value is 14. Which shows nothing on this reference table.
has
Using 1252 hex value is 14, the ifs file ends up being create as 5348
instead. I don't understand why...
In either case when I open it excel or notepad, I get a symbol that I
cannot even paste into this email.
When I upload the file to http://en.webhex.net/ from the IFS it still
atheir
hex value of 14. but displays a period instead. That could just be
choice of how to display the character.out.
But anyway I need to display the ô and haven't been able to figure it
Any help much appreciated.is
I'm rewriting a process so that it can be ran by multiple companies and
automating it a little more than it was.
The current process does fine by first RUNQRY QUERY RCDSLT(*YES). This
trusting the user wont screw things up (don't ask why it was designedthis
way). It builds a database table. Then the user must issue the commandCPYTOSTMF
EMAILFILE.
Email File command basically creates a file in qtemp, then issues
command with STMFCODPAG equal to *STDASCIIlist
I'm thinking that this is the difference. But I cannot figure out how to
get Scott's IFS example to use *STDASCII.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
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.
--
Regards,
Bruce
www.brucevining.com
www.powercl.com
--
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.