On 2/13/23 02:51:52, Jonathan Scott wrote:
Any reference to an ASCII or Unicode term where the value
contains characters outside the invariant EBCDIC character set
will clearly have a value which depends on the EBCDIC code page
in which the source was written. This means that it is not
possible to determine the binary value of such a constant from
the written or printed form of the program. This language
limitation was originally considered a possible reason not to
support ASCII and Unicode self-defining terms at all, but we
decided that it would be a useful language extension anyway.
Wouldn't that limitation have applied to EBCDIC terms contains characters
outside the invariant EBCDIC character set? such as:
CLI L,C'[' or:
DC C'['
where it is not possible to determine the binary value from the written or
printed form?
Can the macro author PUSH the CCSID on entry and POP it on exit in order to
control the CCSID non-disruptively?
... All source files and listings are
assumed to be in the local EBCDIC code page as specified on the
EBCDIC option or assumed by default.
Is this default affected by the CCSID tagging of z/OS UNIX source files?
--
Thanks,
gil
