On Thu, 18 May 2023 16:15:20 -0400, Phil Smith III wrote:
>
>    ....) Did you mean the business where hitting ERASE EOF at the start of a 
> line marks the MDT so XEDIT thinks the line has been changed?  Yeah, that's 
> always been like that, and is a bit weird.
>
>Just curious-when does it bite you? 
>
It broke a macro  I wrote.  I don't recall details.  Went to SR.  WAD.
With a sympathetic aside from development that while they sympathized
they found XEDIT logic so convoluted that they feared that any
attempted repair might  cause worse collateral damage.

>    ...  this would only matter in CMS UPDATE mode.
>
I was once a minor contributor in a distributed shareware develomment
project (Charlotte).  Patches were submitted as CMS UPDATE.
I found XEDIT UPDATE inappropriate in that if I had second thoughts
and restored the previous content of a line, it appeared regardless in
the UPDATE as a replacement by an identical line.

I abandoned XEDIT UPDATE and resorted to ISRSUPC UPDCMS8
to produce my patches.

>    ... So I'm not challenging it being weird/irritating, just curious 
> when/how you even notice it! Maybe just if it's the ONLY thing you've done, 
> and then PQUIT says 
>DMSXSU577E File has been changed; type QQUIT to quit anyway?
>
I was trying to automate that in a macro on PF3.

And ISRSUPC UPDMVS8 requires that both OLD and NEW have valkd
line numbers.  UPDCMS8 requires only that OLD have valid numbers.
In my day job we produced some customer-facing HLASM code.  Some
coders had started using desktop editors which didn't maintain numbers.
I couldn't repair them with ISRSUPC UPDMVS8; IEBUPDTE because of
that restriction.  I could use ISRSUPC UPDCMS8; REXX filter; IEBUPDTE
in order not to break customer USERMODs.

IBM has the right solution, but NIH:
<https://www.ibm.com/docs/en/zos/2.5.0?topic=descriptions-patch-change-file-using-diff-output>.

How about an RFE for SMP/E support?

-- 
gil


-- 
gil

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to