Steve Comstock [EMAIL PROTECTED] wrote in message
news:[EMAIL PROTECTED]...
snip
And I can't figure out why they made that change,
since DBCS is, supposedly, on its eventual way
out, to be replaced by NATIONAL (Unicode). Any
idea why the default was changed? Especially since
the vast majority
I think you're confusing the DBCS value of the NSYMBOL option with the
DBCS option.
Don Imbriale
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On
Behalf
Of Steve Comstock
Sent: Wednesday, June 22, 2005 2:36 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: DBCS
Imbriale, Donald (Exchange) wrote:
I think you're confusing the DBCS value of the NSYMBOL option with the
DBCS option.
Well, it certainly is confusing. But I tried to make it
clear what I was saying is choosing the NATIONAL value
for the NSYMBOL option forces on the DBCS option. And
it still
OK, to explain ...
*ALL* the DBCS (or NODBCS) compiler option does is to determine how
X'0E' and
X'0D' are treated when they appear WITHIN an alphanumeric literal. When
it is
turned on, then they are treated as SHIFT-OUT/IN control characters (and
this
may be shifting to Unicode *or* to
Bill Klein wrote:
OK, to explain ...
*ALL* the DBCS (or NODBCS) compiler option does is to determine how
X'0E' and
X'0D' are treated when they appear WITHIN an alphanumeric literal. When
it is
turned on, then they are treated as SHIFT-OUT/IN control characters (and
this
may be shifting to
5 matches
Mail list logo
