VSAM came out in the same time frame as SMP, Yes, pre-ICF VSAM had some issues, but the way that SMP misused member name was a true gargoyle.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of Jesse 1 Robinson <jesse1.robin...@sce.com> Sent: Wednesday, May 23, 2018 5:30 PM To: IBM-MAIN@listserv.ua.edu Subject: Re: [External] Old School Maintenance Philosophy -- Never ACCEPT? Pre-E SMP consisted entirely of PDS--PO because PDSE had not been invented yet. It was, as someone pointed out, a sort of elaborate RYO data base. In those days of molasses-inspired SLED, clunky CPUs, limited expensive central memory, and a far less sophisticated MVS than we enjoy today, a 'standard' SMP install could take forever. Hours. Days. Longer even than the MTTF of the infrastructure itself. So SMP provided an alternative run mode. I forget the terminology, but it entailed reading entire PDS directories into memory, updating data in memory as required, then writing entire directories back out in one massive operation. The result was a far shorter elapsed time than the standard mode. Unless. Unless something went wrong, especially during the write-out phase. Could be a program failure; DASD error; power hiccup, spilled cup of coffee. At that point the entire SMP data base was trashed. So you restored the whole SMP environment and started over. With or without ACCEPT, modern SMP/E is a miracle. . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 323-715-0595 Mobile 626-543-6132 Office ⇐=== NEW robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Seymour J Metz Sent: Wednesday, May 23, 2018 12:59 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: [External] Old School Maintenance Philosophy -- Never ACCEPT? >SMP/E for z/OS IBM User's Guide SA23-2277-30 ... appears to say otherwise: No. Read what I actually wrote. The configuration information for an SMP4 or earlier environment is in multiple data sets, of which the CDS is only one. The CDS is the equivalent of a target zone, not of the entire CSI, and the manual you cited does not claim otherwise. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu> on behalf of Paul Gilmartin <0000000433f07816-dmarc-requ...@listserv.ua.edu> Sent: Wednesday, May 23, 2018 3:19 PM To: IBM-MAIN@listserv.ua.edu Subject: Re: [External] Old School Maintenance Philosophy -- Never ACCEPT? On Wed, 23 May 2018 18:55:21 +0000, Seymour J Metz wrote: >The CDS may have been an equivalent to a target zone, but not to the entire >CSI. You won't get very far without a PTS and ACDS. > SMP/E for z/OS IBM User's Guide SA23-2277-30 ... appears to say otherwise: The consolidated software inventory (CSI) The CSI data sets contain all the information SMP/E needs to track the distribution and target libraries. As the card catalog contains a card for each book in the library, the CSI contains an entry for each element in its libraries. The CSI entries contain the element name, type, history, how the element was introduced into the system, and a pointer to the element in the distribution and target libraries.*The*CSI*does*not*contain*the *element*itself*, but rather a description of the element it represents [emphasis added] This seems to use "CSI" to refer to the VSAM data sets, but not to PDSes that contain actual elements. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
