We install our 'serious' user exits via SMPE usermods. As a part of each new release, we update the MCS cards for the new FMIDs, reapply, and lunge forward. Do we test every single exit individually? Of course not. We manage the environment by exception. Once a new release is IPLed and running like a banshee, the *absence* of problem reports is an endorsement to move ahead.
Long gone are the days of the luxurious army of dirt cheap testers thrown against the wall of new software just to see what sticks. Modern software is dear, but way more so the people who use it. Life is short. So are life cycles. . . . J.O.Skip Robinson Southern California Edison Company Electric Dragon Team Paddler SHARE MVS Program Co-Manager 626-302-7535 Office 323-715-0595 Mobile [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Shmuel Metz (Seymour J.) Sent: Thursday, September 10, 2015 1:08 AM To: [email protected] Subject: Re: Effort to upgrade V1R13 to V2R1? In <[email protected]>, on 09/09/2015 at 11:45 PM, Brian Westerman <[email protected]> said: >Upgrading can be a whole different animal because there can (and >will) be a number of exits and other site specific items which have to >be altered. How do they not need to checked, altered (or not) and reinstalled either way? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see <http://patriot.net/~shmuel/resume/brief.html> We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of 2003) ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
