A frequently overlooked but very useful SMP/E publication, "Standard Packaging Rules for z/OS-Based Products", SC23-3695-10, Chapter 7, Using MCS to Define Products, page 57, provides an explanation and coding for a sample dummy delete function sysmod to purge a base function. It's even an IBM recommendation (paragraph 1) that during SMP/E product packaging, packagers "consider providing users with an example of how to package the ++VER DELETE information separately in a dummy function SYSMOD". I would amend this documentation by adding that it's prudent to inspect and fully understand beforehand all base and dependent functional sysmod relationships before coding a dummy delete function sysmod of any kind. A dummy delete function sysmod consists of two parts: (a) the dummy delete function sysmod itself, and (b) the UCLIN to purge/delete any knowledge by SMP/E within all zones of any remnants of the dummy delete function itself after it has executed. I recommend they be coded as two separate jobs. Finally, submit a SHARE requirement to have SMP/E development incorporate a formally supported and comprehensive mechanism including accompanying documentation within SMP/E itself to delete base and dependent function sysmods with all attendant clean-up of the CSI, zones, and data sets. There is valid business and regulatory justification for this: legal compliance with software licensing terms and conditions as data centers consolidate and with the retirement/withdrawal of obsolete or discontinued IBM and OEM vendor-licensed products. William J. Smith, M.A. EdFormer IBM DFSMS z/OS Integration and Product Packaging Team Lead
---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
