Why does it take so long for people to use new features? HLASM has a lot of nifty things that have been around and well documented for decades.
A similar question exists for new instructions; how many shops are still running boxen that don't support the z immediate, long displacement and relative instructions, e,g.,JC, LARL, LAY? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Peter Relson <[email protected]> Sent: Sunday, December 10, 2023 9:13 AM To: [email protected] Subject: Re: Assembler optimization OPTION The starting point to almost all of these discussions tends to be to write reentrant programs (as high level languages naturally produce). If you must stick with a non-reentrant program, consider the LOCTR directive. If you don't feel like truly moving the data-defining statements within your program, you can use the LOCTR directive to help to "move" data to a separate area. You might have an area for your "code" and an area for your "static data" and an area for your "dynamic data" Peter Relson z/OS Core Technology Design ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
