new type of CA for ascii strings

Thread View: bit.listserv.asm370

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by John R. Ehrman (408-463-3543 T/5... Fri, 22 Sep 2006 17:17

#275

Author: John R. Ehrman (408-463-3543 T/5...
Date: Fri, 22 Sep 2006 17:17

41 lines
2667 bytes

The easy explanation is that HLASM doesn't support CA terms.

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.

A possible solution would be to make *all* character terms and
constants subject to translation, but the impact on existing
applications is very difficult to determine.

Your thoughts and suggestions are welcomed.

John Ehrman
    (------------------ Referenced Note Follows --------------------)
Date:         Fri, 22 Sep 2006 15:33:43 +0200
From: Martin <martin@pi-sysprog.de>

To: those that teach HLASM

how do you "sell"/"explain" this to your students?

It is totaly okay to use

     MVI  FIELD,C'A'

to move the EBCDIC constant A to a field

but it is not okay to use

     MVI  FIELD,CA'A'

to move the ASCII constant A to a field.

ASCII is certainly not UNICODE-16.

Re: new type of CA for ascii strings

#282

Author: Martin
Date: Sat, 23 Sep 2006 05:17

25 lines
2325 bytes

John,

How about allowing only the code-points that are the same accross all
codepages and fixed in ASCII and EBCDIC
(upper-lower-digits-blank-tic-doubletic-ampersand-tic-open-close-aster-plus-coma
and so on) but certainly not the dollar.

I could easy live with a solution that would cover just the
code-positions that are the same accross all codepages.

I could still have my piece of the fun with square brackets and pound.

And about braking written code:

My code broke with
  TR HEX,=C'0123456789ABCDEF'-240
     and
  EX R1,=S(&MVC,RECEIVER,SENDER)

on more than one point and at more than one site.
--
Martin
--
XML2PDF - the way to get all features of PDF into your documents
on mainframe or PC systems; more at http://www.pi-sysprog.de

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads