Let's not get in a spitting match. anyone can write bad code as an example of why someone else's style is bad. I am pretty sure I could write some pretty unintelligible code if I tried using any of the suggested methods. That doesn't mean a style is bad, it probably means I am not using it as intended.
-----Original Message----- From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU] On Behalf Of Martin Truebner Sent: Wednesday, June 06, 2012 11:58 AM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU Subject: Re: Base registers Jon, >> I suggest you learn how to use LOCTR. NO COMMENT >> It's a much simpler method than using =S(xxxx) and certainly more readable. Simpler- maybe! more readable- judge it here: ................................................ My suggestion: a SETC as intro and EX R2,=S(&PKA,QWORD,0(R10)) ................................................. or (more readable): a CODE LOCTR and DEFS LOCTR as intro and EX R2,PKA_02 DEFS LOCTR PKA_02 PKA QWORD,0(0,R10) CODE LOCTR plus the extra of inventing unique names .................................................. I like the expression "in eyeball range" ;-) -- Martin Pi_cap_CPU - all you ever need around MWLC/SCRT/CMT in z/VSE more at http://www.picapcpu.de