Fair enough. I think the best solution is a USING for R0 on the literal pool and LA 0,=x'whatever' in the table. The second two bytes of each LA is the offset of the literal into the pool.
Charles -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Windt, W.K.F. van der (Fred) Sent: Monday, December 11, 2017 12:47 AM To: [email protected] Subject: Re: Address of a =LITERAL > > Really no better than what I suggested below, but for some reason I > > find the following approach amusing. > > > > The OP's original plan was to include > > > > LABEL DC A(=x'123') > > > > in his table and then, presumably > > > > L Rn,LABEL > > > > in his executable code. Almost exactly the same effect could be > > achieved by including > > > > LABEL LA Rn,=X'123' > > > > in the table and > > > > EX 0,LABEL > > ... > What if the OP intended the construct as a static initialization or > default setting, possibly to be overlaid later by a different address? The OP intends the data structure to be language-independent: we want to be able to load- and use the structure in a COBOL program. This becomes quite weird if table doesn't contain addresses but LA instructions... Fred! ----------------------------------------------------------------- ATTENTION: The information in this e-mail is confidential and only meant for the intended recipient. If you are not the intended recipient, don't use or disclose it in any way. Please let the sender know and delete the message immediately. -----------------------------------------------------------------
