IEBUPDTE depends on 'standard' line numbers in columns 73 - 80 to identify lines for modification, deletion, or insert location. IBM guarantees that source and macro line numbers remain fixed for the life of an FMID. There are few if any other elements that have reliable line numbers even for files that are FB 80. Those have to be changed via complete replacement.
. . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-302-7535 Office [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Paul Gilmartin Sent: Wednesday, November 16, 2016 6:17 PM To: [email protected] Subject: (External):SMP/E and IEBUPDTE On Wed, 16 Nov 2016 19:29:47 -0600, Edward Gould wrote: >> On Nov 16, 2016, at 12:28 PM, Paul Gilmartin wrote: >> >> How is this still a thing!? >> >> What's a "utility"? IEBGENER and IEBCOPY and Rexx support VB. I'd >> substitute "not all" for "no”. >IBM won’t re-open the code for IEBUPDTE its stabilized. Plus it was never >designed for VB records. >IBM didn’t want to reship the entire member (IEBCOPY) . >This was design issue (architect) of IBM’s This has been an issue since >day 1 of SMP. IBM its in your corner. > And: o SMP/E has ++MACUPD and ++SRCUPD but no facility to UPDate general text files, even FB 80. o I don't believe PTFS using IEBUPDTE can be RESTORED. But now that z/OS has UNIX System Services, there's patch(1) which has no FB 80 limitation and has an option to undo a patch. No need to re-open IEBUPDTE when there's a better featured alternative available. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
