On Jan 13, 2008, at 10:41 AM, Rick Fochtman wrote:
-------------------<snip>----------------
SMP/E is too efficient! It's design point is, when performing a
"mass" apply of hundreds (or even thousands) of PTFs, that it
installs only the highest level of each element being replaced.
Intermediate levels are neither created nor journaled. There is no
version to "undo" to!
Backing off any one PTF requires a RESTORE (from DLIB) of all
elements, from all interdependent PTFs, followed by re-APPLY
specifying EXCLUDE for the "problem" PTF. Granted, it would be
nice if more of this processing could be performed automatically.
------------------<unsnip>-----------------
Leave us not forget the record keeping functions that SMP/E does so
well. How many three-ring binders would be necessary just to keep
track of what PTF's were on the system, and their status. Plus all
the components of MVS, OS/390 or z/OS. Plus all the add-ons.
Rick,
Another excellent point when MVS came out (pre SMP days) a sysprog
was left to do this type of stuff *MANUALLY* We had worked on a
spreadsheet (no not Lotus 1-2-3 type) a manual spreadsheet to figure
out req & coreqs (don't remember if IFREQS were there (I don't think
so) and it was extremely time consuming and you had to sit in a room
*WITHOUT* distractions for hours at a time to get an idea what needed
to go on. Plus the research time was another intensive task but at
least you didn't need to lock your self in a room for this.
SMP and later SMP/e was a godsend relieving the sysprog of an
extremely tedious task. IBM, IMO did a great service to the sysprog
community (and maybe to their own people as well) for developing the
program. Thanks IBM (KURT?). Life as a sysprog got infinitely easier.
Ed
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
