I'm having trouble finding the correct CCSID. I'm using Scott Klement's
pdf for writing directly to the IFS.
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.
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 has
hex value of 14. but displays a period instead. That could just be their
choice of how to display the character.
But anyway I need to display the ô and haven't been able to figure it out.
Any help much appreciated.
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 is
trusting the user wont screw things up (don't ask why it was designed this
way). It builds a database table. Then the user must issue the command
Email File command basically creates a file in qtemp, then issues CPYTOSTMF
command with STMFCODPAG equal to *STDASCII
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 list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This mailing list archive is Copyright 1997-2013 by MIDRANGE dot 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 here. If you have questions about this, please contact