Join the COBOL 6 modernization features survey

[SUBSCRIBE ASSEMBLER-LIST Dan Zhang]

Take our quick survey on IBM Enterprise COBOL for z/OS (COBOL) 6 modernization 
features: https://ibmxm.qualtrics.com/jfe/form/SV_5zhKYEpP68L4Yjc

Share your feedback on learning and using the latest advancements in COBOL 6. 
It only takes 5 minutes to complete. Your insights will shape the future of our 
products and services to better serve you.

Re: Complex immediate fields

[Ngan, Robert (DXC Luxoft)]

Assuming you have an assembly listing, you just need to look at the "R-Loc" 
(i.e. offset) value.

We use two LOCTR's  for data, one for data that needs to be within 4K of the 
base register, and another for data referenced with relative long, or long 
displacement instructions. That single base register will handle both LOCTR's.

Robert Ngan
DXC/Luxoft

-Original Message-
From: IBM Mainframe Assembler List  On Behalf 
Of Paul Gilmartin
Sent: Monday, April 15, 2024 22:07
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Complex immediate fields

On 4/15/24 20:31:33, Seymour J Metz wrote:
> Expect a performance hit if you modify instructions. I like to use LOCTR to 
> keep data physically remote but visually near the instructions that use them.
>  .
LOCTR is a boon for reading source.  Perhaps less so for reading dumps.
Are any symbolic debuggers LOCTR-savvy, perhaps assisted by ADATA?

--
gil