MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » January 2013

Re: Correct CCSID for IFS File.



fixed

Well you're right, that's a x'3C' for sure. Unfortunately that's not a
valid displayable character. In EBCDIC that would be a control (like how
x'14' is an ASCII control). "Who" is writing the x'3C'? The correct
codepoint, in the CCSID of your file (37), would be x'CB'.

On Tue, Jan 22, 2013 at 11:59 AM, Michael Schutte <mschutte369@xxxxxxxxx>wrote:

SELECT hex(ONADD1), hex(substring(onadd1,17,1))
FROM onsgne WHERE onbill = 1031606

HEX ( ONADD1 ) HEX
D9E4C540D3D6E4C9E240C3C1E3E840D53CF1F0F840404040404040404040 3C


Display Attributes



Object . . . . . . : /qsys.lib/*********.lib/onsgne.file



Text . . . . . . . . . . . . . . . . . : Consignee changes for Outbound
Order
s



Type . . . . . . . . . . . . . . . . . : FILE

Type attribute . . . . . . . . . . . . : PF



Owner . . . . . . . . . . . . . . . . : *****

System object is on . . . . . . . . . : Local

Auxiliary storage pool . . . . . . . . : 1

Object overflowed . . . . . . . . . : No



Coded character set ID . . . . . . . . : 37

Hidden file . . . . . . . . . . . . . : No

PC system file . . . . . . . . . . . . : No

Read only . . . . . . . . . . . . . . : No


More...
Press Enter to continue.



F3=Exit F12=Cancel F22=Display entire field



"What is making
you think that x'3C' is a Latin small letter O with circumflex?"

Because if I run the existing process and open the CSV. That is what shows
up.


On Tue, Jan 22, 2013 at 11:59 AM, Bruce Vining <bvining@xxxxxxxxxxxxxxx
wrote:

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's
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.



http://www-03.ibm.com/systems/resources/systems_i_software_globalization_pdf_cp00819z.pdf

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
a
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
EMAILFILE.

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,
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.


--
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.









Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 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