Re: Character set issue

Hi Joep,

Thanks for your help, but after discussions with people here we have decided to code the character values in the Cobol program using hexadecimal because the users could also have different code pages on their rumba setup. This should then stop all of these interpretation issues.

Just out of interest though, the job you referred to, I guess this is a server job that supports WDSC. What is the job name and how do I know which one relates to which user?

Best regards,

Mark Austin
IT Consultant
Universal Music Publishing International
Email: mark.austin@xxxxxxxxxx
Tel: +44 (0) 20 8742 5520
Fax: +44 (0) 20 8742 5699

Universal Music Publishing International Limited
Registered in England. Number 02050403
Registered Office: 347-353 Chiswick High Road, London W4 4HS

-----Original Message-----
From: wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx] On Behalf Of J.Beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx
Sent: 24 June 2008 13:00
To: Websphere Development Studio Client for iSeries
Subject: Re: [WDSCI-L] Character set issue

Mark,

It has to do with the CCSID (coded character set ID) of the file and the
job.

LPEX uses Unicode and knows the CCSID of the file, so it translates
between EBCDIC and Unicode.

Looking at your data it looks like the file has CCSID 1140 (US with Euro)
and Rumba uses 1146 (UK with Euro). Pound and dollar are code points x'B1'
and x'5B' in 1140; in 1146 these code points represent '[' (left square
bracket) and pound sign. I don't know Rumba, but in the Client Access
emulator you have to specify which code page the host uses.

What happens is that characters are translated from the file CCSID to the
job CCSID. Then they are sent to the output device, i.e. Rumba. Rumba then
interprets the code points and shows them. Apparently there is a mismatch
between Rumba and the job CCSID.

Things to check:
- What is the CCSID of the file?
- What exactly is in the file (DSPPFM; F10 to show hex)?
- What is the CCSID of the job?
- What code page is used by Rumba?

Joep Beckeringh





From:
"Austin, Mark" <Mark.Austin@xxxxxxxxxx>
To:
"Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx>
Date:
24-06-2008 12:05
Subject:
[WDSCI-L] Character set issue




Hi,



One of our developers has added the following code into a Cobol program
using the LPEX editor.



01 WS01-TEST-CHARACTER PIC X.

88 WS01-VALID VALUE 'a' 'b' 'c' 'd' 'e' 'f'

'g' 'h' 'i' 'j' 'k' 'l' 'm' 'n' 'o' 'p' 'q' 'r' 's' 't'

'u' 'v' 'w' 'x' 'y' 'z' 'A' 'B' 'C' 'D' 'E' 'F' 'G' 'H'

'I' 'J' 'K' 'L' 'M' 'N' 'O' 'P' 'Q' 'R' 'S' 'T' 'U' 'V'

'W' 'X' 'Y' 'Z' '0' '1' '2' '3' '4' '5' '6' '7' '8' '9'

'!' '"' '£' '$' '%' '^' '&' '*' '(' ')' '€' '_' '-' '+'

'=' '[' '{' '}' ']' ';' ':' '@' "'" '#' '~' ',' '<' '>'

'.' '?' '/' '¬' '`' '¦' '\' '|' ' '.



When he looked at the source member, using Rumba, some of the characters
have changed.



01 WS01-TEST-CHARACTER PIC X.

88 WS01-VALID VALUE 'a' 'b' 'c' 'd' 'e' 'f'

'g' 'h' 'i' 'j' 'k' 'l' 'm' 'n' 'o' 'p' 'q' 'r' 's' 't'

'u' 'v' 'w' 'x' 'y' 'z' 'A' 'B' 'C' 'D' 'E' 'F' 'G' 'H'

'I' 'J' 'K' 'L' 'M' 'N' 'O' 'P' 'Q' 'R' 'S' 'T' 'U' 'V'

'W' 'X' 'Y' 'Z' '0' '1' '2' '3' '4' '5' '6' '7' '8' '9'

'!' '"' '[' '£' '%' '¢' '&' '*' '(' ')' ' ' '_' '-' '+'

'=' '^' '{' '}' ']' ';' ':' '@' "'" '#' '¯' ',' '<' '>'

'.' '?' '/' '¬' '`' '¦' '\' '|' ' '.



The differences are highlighted in red.



I’m not sure if this is an issue with Rumba, WDSC or the iSeries.



Does anyone know why this is happening and more importantly how to stop
it?



Best regards,



Mark Austin

IT Consultant

Universal Music Publishing International

Email: mark.austin@xxxxxxxxxx

Tel: +44 (0) 208 742 5520

Fax: +44 (0) 208 742 5699



Universal Music Publishing International Limited

Registered in England. Number 02050403

Registered Office: 347-353 Chiswick High Road, London W4 4HS




Confidentiality

The information contained in this e-mail is confidential, may be
privileged and is intended solely for the use of the named addressee.
Access to this e-mail by
any other person is not authorised. If you are not the intended recipient,
you should not disclose, copy, distribute, take any action or rely on it
and you
should please notify the sender by reply. Any opinions expressed are not
necessarily those of the company.

We may monitor all incoming and outgoing emails in line with current
legislation. We have taken steps to ensure that this email and attachments
are free from any virus, but it remains your responsibility to ensure that
viruses do not adversely affect you.