🚀 go-pugleaf

=V() is not a character constant, but I see what you mean.  In the UK, that
program name as you typed it would have the graphic of the English Pound and
not the American Dollar.

If one of the other EBCDIC pages were used to type the input, then in order
to really get IND$FILE, they would have to use whatever character in that
codepage corresponds to the $ codepoint (like the pound does in the UK).  If
they typed $ in their own codepage, they would be calling a different name.

<Shrug> That's life in the codepages, we just have to learn to live with it.

Peter

-----Original Message-----
From: IBM Mainframe Assembler List [mailto:gilmap@unix.stortek.com] 
Sent: Friday, September 22, 2006 2:27 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: new type of CA for ascii strings

In a recent note, "John R. Ehrman (408-463-3543 T/543-)" said:

> Date: Fri, 22 Sep 2006 10:17:15 -0700
>
> Character self-defining terms are complex. When the assemblers
> assumed only code page 037 for input, C'$' meant X'5B'. But we
> now have dozens of EBCDIC code pages containing the $ character,
> C'$' can have values X'5B' (the HLASM default), X'67', and X'4A'
> just among the set of code pages HLASM supports for Unicode
> translation.
>
> Many EBCDIC code pages are now used to prepare input for HLASM.
> A statement with the term C'$' could contain any of the code
> points just mentioned; each has a different ASCII translation.
>
Now, I'm puzzled.  Does this mean that I say:

         L     R15,=V(IND$FILE)
         BALR  R14,R15

I'm likely to get a call to various entry points depending
on the code page in effect for input?

-- gil
--
StorageTek
INFORMATION made POWERFUL

_
This message and any attachments are intended only for the use of the addressee and
may contain information that is privileged and confidential. If the reader of the 
message is not the intended recipient or an authorized representative of the
intended recipient, you are hereby notified that any dissemination of this
communication is strictly prohibited. If you have received this communication in
error, please notify us immediately by e-mail and delete the message and any
attachments from your system.