Try this url instead for the SHARE presentation: https://www.share.org/p/do/sd/topic=206&sid=9063
It is from SHARE 120 in San Francisco (2013). You will have to login with a SHARE userid to see it though. HTH Peter -----Original Message----- From: IBM Mainframe Assembler List <[email protected]> On Behalf Of Seymour J Metz Sent: Monday, June 1, 2020 5:45 PM To: [email protected] Subject: Re: z/OS HLASM: EQU for statement labels The URL is 404 compliant. Has anybody put up a web site with copies of John's work and a few words of tribute? We owe him a lot. The best reason to put the label on the instruction is that you get correct TEST and ADATA output. If you have to insert a statement after the label, TS is your friend (I don't recall the XEDIT equivalent.) If you're using vi I don't want to know ;-) -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List [[email protected]] on behalf of Schmitt, Michael [[email protected]] Sent: Monday, June 1, 2020 4:43 PM To: [email protected] Subject: z/OS HLASM: EQU for statement labels In John R. Ehrman's SHARE presentations on tips for modernizing IBM z/Architecture assembler programs (such as https://secure-web.cisco.com/1MDmQPGPlhl-XBk7iLilTmlMjCPG2lHl8oCpN-lY2_t1w3z5xqh2L_s533KYfGL2uox5OiYYSYNZwzp_D_uw4BIsF2SBUbJmOtK5_O0tr9TfBM_QBPGpxnwJ_sV2-Y6wLPUBnk6-K-FKHC-nuTh-kTKAd6wRAd2oyY36o8Ibd2BAtn-Gi3fpP-Ip2uBQMrgYoDu6v3F0wz_2s9EXQR4SJtEo9CxQmgkTn2O61LXMfKcvfv_VsSdw5oRgpsY6vURQMY02y_N61YWQ61wegmZwdFGy4Nc7mBoWI-CH-SR3JNJnMWImqNDdPrpYGz1O69JlL8uQfSVhDUK4NloLrTWgbDdd916U9Bsuw54CAV7hinVicbIS6QLasiEOOsokG4rzujzsCK-G7lgGCuVu6ffG6pFFKmICzl3B_XFaQwS0shjAl7BSXRtf8jN0-Jd_Qb5Tj/https%3A%2F%2Fshare.confex.com%2Fshare%2F120%2Fwebprogram%2FHandout%2FSession12522%2Fmodrnasm.pdf%29, he says that important advice from experienced assembler programmers is to: _Don't_ use EQU for statement-label creation Can anyone venture a guess as to the reason for this advice? I've been coding MVS assembler for 30 years and this is the first I've heard of this guideline. One thing I'm wondering is if the suggestion is to avoid stand alone statement labels entirely (such as LABEL EQU * or LABEL DS 0H) in favor of putting the label on the next instruction? Or is there something about EQU * that makes it a bad alternative to DS 0H? __ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
