I'm thinking that had the packaging been originally designed using the ++MOD entry's CSECT parameter, removing a CSECT from a ++MOD would have been straightforward.
Given the packaging you've described - a reasonable way to structure the module - the solution is likely to be something like this: ++PTF(newptf) . ++VER (some value). ++DELETE(FOO) SYSLIB(name) . ++JCLIN . (new structure for load module FOO) ++MOD(FOO) . /*presumably FOO is a CSECT in lmod FOO */ object deck for current version of FOO ++MOD(FRED). object deck for current version of FRED Brian On Tue, 9 Feb 2010 18:28:47 -0600, Paul Gilmartin wrote: >We had a ++MOD (FRED) element containing a CSECT, WOMBAT, >which we want to remove (it's obsolete but contains a >harmful VCON). > >So, I thought: > > ++ JCLIN > REPLACE WOMBAT > INCLUDE DISTLIB(FRED) > NAME FOO(R) > >Simple enough. Alas, SMP/E elaborates this as: > > REPLACE WOMBAT > INCLUDE SMPPTS(FRED) Should get rid of WOMBAT > INCLUDE SYSLMOD(FOO) ... but WOMBAT comes right back. > NAME FOO(R) > >All Broken As Documented. How do I really get >rid of WOMBAT? (How do I get the REPLACE to appear >in the right place, one line lower?) > >Thanks, >gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
