David,
Here are a few scenarios:
1. System A has sent System B a *SAVF containing a file CCSID tagged 37
(United States). System B restores the file and a job running under CCSID
297 (France) reads a record containing the CCSID 37 encoded character #
(x'7B'). The system will automatically convert the CCSID 37 encoded x'7B'
to x'B1' - the # in France.
2. System A has sent System B a *SAVF containing a file CCSID tagged 37
(United States). System B restores the file and a job running under CCSID
65535 (Hex) reads a record containing the CCSID 37 encoded character #
(x'7B'). The system will not automatically convert the CCSID 37 encoded
x'7B' due to the 65535 CCSID being involved. The user, if using a terminal
configured with CCSID 297, will "see" the £ character (x'7B' in CCSID 297).
3. A user on System B, with a terminal configured using CCSID 297, passes
through to System A to run an interactive application. The application on
System A runs with a job CCSID of 297 while using CCSID 37 tagged databases.
The user reads a record containing the # of scenario 1 above.
The user "sees" the # correctly on their terminal.
4. A user on System B, with a terminal configured using CCSID 297, passes
through to System A to run an interactive application. The application on
System A runs with a job CCSID of 65535 while using CCSID 37 tagged
databases. The user reads a record containing the # of scenario 1 above.
The user "sees" the £ on their terminal.
5. A user on System B, with a terminal configured using CCSID 297, passes
through to System A to run an interactive application. The application on
System A runs with a job CCSID of 37 and the *DSPF is created with the
default CHRID(*DEVD) which is essentially a *DSPF's way of saying 65535.
The user reads a record containing the # of scenario 1 above. The user
"sees" the £ on their terminal.
6. A user on System B, with a terminal configured using CCSID 297, passes
through to System A to run an interactive application. The application on
System A runs with a job CCSID of 37 and the *DSPF is created with
CHRID(*JOBCCSID) or equivalent. The user reads a record containing the # of
scenario 1 above.
The user "sees" the # correctly on their terminal.
You might notice that with 65535 involved the user consistently "sees" the
wrong character in a multi-lingual environment if the character happens to
be variant.
Bruce
----- Original Message -----
From: "David FOXWELL" <David.FOXWELL@xxxxxxxxx>
To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx>
Sent: Friday, April 17, 2009 2:22 AM
Subject: RE: Difference between CCSID 65535 and CCSID 37
Hi Scott,
-----Message d'origine-----
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de Scott Klement
Envoyé : vendredi 17 avril 2009 07:54
If someone who uses a different CCSID (such as someone using
a German, British, French, Russian, etc, terminal) needs this
data, automatically translate it from the USA type of EBCDIC
to the one they need.
I didn't understand this sentence. If I received data from you with a CCSID
of 37, what difference would there be if I had 65535 or the CCSID for
France?
We've always had 65535. Could you give an example?
Thanks.
midrange.com
