Adding (and replacing) '<' by X'0E' (SO) and '>' X'0F' (SI) solved the problem.
I think IBM should document this part better. Frankly, it's not clear anywhere in the docs that you have to code hexadecimal (e.g. ISPF "HEX ON" to accomplish this). Thanks everybody for your help. José -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of David Staudacher Sent: Monday, December 08, 2014 5:47 PM To: [email protected] Subject: Re: Assembly of G-Type constants not working for me > It's probably because the notations ".A" and ".B" represent the DBCS > codings for those double-byte characters, not the EBCDIC characters "." > and "A". Makes sense. If using a true DBCS terminal we'd probably see a DBCS "A" in the source rather than ".A" > If you can enter data in hex, try assembling G'42C142C2' (where I > wrote the hex representations of each byte) -- this is the DBCS > representation of "AB". Apparently, it's also necessary to code the Shift-In, Shift out characters as "0E" and "0F" rather than "<" and ">". With "<" and ">" I still get the error, but when I use "0E" and "0F" the error goes away. DBCS1 DC G' A B C ' CCCEF4CC4C704C4C4C07444 4232104307DE212223FD000 ----------------------- DBCS2 DC GL10' A B C ' CCCEF4CC4CDFF704C4C4C07 4232204307310DE212223FD ----------------------- DBCS3 DC GL4' A B C ' CCCEF4CC4CDF704C4C4C074 423230430734DE212223FD0 See also http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/asmr1020/FRONT_1.7 and http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/asmr1020/8.3.3.3
