Ref: Your note of Wed, 15 Jan 2014 09:00:56 -0700 Paul Gilmartin wrote: > On 2014-01-15, at 01:43, Jonathan Scott wrote: > > > > Constants with type CA are currently translated from EBCDIC > > codepage 037 to the 7-bit displayable ASCII codes hex 20 through > > 7E, not to code page 819. Anything which does not translate to a > > valid ASCII character in that range is left untranslated. > > > Does this use ASMALTAS, or somthing else, internal?
It uses a fixed table, as documented. The effects of DC CA and of DC C with TRANSLATE are accurately documented in the reference manual, although in different places. I guess that the main problem is that users may optimistically expect it to work in a more general way but the book doesn't document what doesn't happen, so it may require a little research to check that properly. > > (The 7E tilde character was missing until quite recently, which I > > spotted and fixed when testing the changes for PM75317, which was > > mainly to ensure that the HLASM source code could be stored in a > > UTF-8 repository if necessary). > > > I'm puzzled. Does HLASM itself participate in storing code > in a UTF-8 repository, or in extracting such code? Can > HLASM directly assemble code in UTF-8 (perhaps on Linux; > almost certainly not on traditional systems. I was referring to the code of the HLASM product itself, which used to contain unprintable or obscure EBCDIC codes that caused problems when we first tried to store it in a UTF-8 repository. Jonathan Scott
