I never had trouble with XEDIT, but I missed having two kinds of shifts.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Assembler List <ASSEMBLER-LIST@LISTSERV.UGA.EDU> on behalf of Phil Smith III <li...@akphs.com> Sent: Monday, September 8, 2025 12:05 PM To: ASSEMBLER-LIST@LISTSERV.UGA.EDU <ASSEMBLER-LIST@LISTSERV.UGA.EDU> Subject: Re: HLASM and VM (was RE: Using (0) to suppress alignment checks in HLASM) External Message: Use Caution Paul Gilmartin wrote, in part: >I was dissatisfied with XEDIT UPDATE: it included lines >I had touched but not modified. Rather, I used >ISRSUPC UPDCMS8 ti create the updates I submitted. Hm. Part of rigorous use of updates for me has always been to look at the update deck and verify that I understood every change. If there was a line that I touched but put back/didn't actually modify, I'd just remove it from the update deck, re-XEDIT in update mode, refile, look again. But yes, it COULD have been smart enough to say "Huh, that didn't actually change". For <checks source deck> over 35 years I've also used a tool I wrote that looks at the lines in memory and sets their selection level if they've been modified. This lets me have an UPDATES XEDIT that does essentially an "all changed" (also "just modified" or "added"), making it easy to find some of those accidental changes before I even file: if I see one, or suspect it, I can mark it manually with a ? or something, making it even easier to find in the update deck. But I understand anyone used to ISPF having trouble with XEDIT--the two are too close yet not the same, making it sometimes quite irritating! For me it's mostly in the opposite direction, but I've found myself doing a FIND in XEDIT when I meant a LOCATE, so it cuts both ways for sure. There have been abortive discussions at times of a PROFILE for XEDIT that would make it behave like ISPF, but there are too many subtleties and I've never found the right ISPF maven--someone with the deep knowledge AND the interest/time. My XEDIT knowledge is there; ISPF, not so much.
