RE: Re: Special characters conversion

I found the root of the problem.
The screenscraper product we use has an INI file which has a CCSID entry
in it. It was set to 500. Their website said this entry must match the
systems CCSID. The i is set to 65535 so I tried that but no luck...same
results. I assumed this was because the field itself has a ccsid of 37
so I changed the ini file to 37 and everything is fine. I will have to
verify with them that a change like this will not affect anything else
before I attempt this in production though.
Just something to be aware of if anyone out there is using Seagulls
JWALK product.

Thanks everyone for the replies.
- Steve

-----Original Message-----
From: Coyle, Stephen F.
Sent: Thursday, October 21, 2010 1:54 PM
To: 'MIDRANGE-L@xxxxxxxxxxxx'
Subject: RE: Re: Special characters conversion

OK....I believe I found the problem.

The data is being entered through a screenscraper product that uses a
telnet session under the covers. When I look at the data in the telnet
session it displays as entered, in my example a left bracket. When I
look at it through a client access 5250 session, it is shown as the cent
sign.
The telnet ccsid attribute is set to *MULTINAT. It must be doing the
conversion through telnet.
I'm not sure how to get around this though. The data I ultimately
process is a cent sign.
Any ideas?

Thanks,
- Steve

-----Original Message-----
From: Coyle, Stephen F.
Sent: Thursday, October 21, 2010 1:29 PM
To: 'MIDRANGE-L@xxxxxxxxxxxx'
Subject: Re: Special characters conversion

Sorry for the confusion.

The users are entering the special characters into a display file and
saving back to the physical which stores the text. When they enter and
save a left bracket, the PF shows the cent sign with x'4A'. I'm not sure
why it becomes 4A. That's what has me confused. When I subsequently
inquire on the record from the display file, it displays correctly as a
bracket. Yes, I am not writing anything to my conversion file. I just
take the text character and lookup to my conversion file, the problem is
I read a cent sign from the text file but I have a left bracket as the
key field in my conversion file so I don't get a hit.

- Steve