Shirley you know that not only is that not true but that IEBUPDATE and IEBUPDTE have nothing to do with VM service.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <[email protected]> on behalf of Jon Perryman <[email protected]> Sent: Tuesday, September 9, 2025 4:34 PM To: [email protected] <[email protected]> Subject: Re: Product build using CMS vs TSO Was: Pipelines = you don't understand z/OS External Message: Use Caution On Tue, 9 Sep 2025 19:42:28 +0000, Seymour J Metz <[email protected]> wrote: >Right of the bat, that process works at the granularity of an entire member. >With XEDIT it's easy to have multiple people testing changes to the same >member with a merge process that's normally very quick. Surely you must know that IEBUPDTE / VMFUPDAT is considered unreliable for critical system components when trying to allow multiple users changing a member at the same time. Maybe things have changed but I suspect not. IEBUPDTE & VMFUPDAT existed for decades and product build never implemented the process. It requires the developer consider every change since the source was pulled. It's much simpler to come to an agreement than chasing down changes. If IEBUPDTE was the solution, then it could be used. ---------------------------------------------------------------------- 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
