One product I discussed here last year. There was a change in TSO/E that caused StarTool to fail from the get-go. (Same problem with CBT PDS command.) For whatever reason the 'fix' was a whole new release of the product. I think there was some misunderstanding in our pro forma query to Microfocus, the new owner of Serena. In any case we were caught off guard.
The other product was BMC Discovery, which was quite old and the object of some benign neglect. Not that benign actually. It would not run at all. Still working on a new release. The point of my emphatic posts is that while you may get away with forging ahead and 'fixing forward', the prudent course is to seek and follow vendors' advice whether or not it's strictly necessary. My ROT is which outcome you'd rather have to explain to the boss: some zealous over-prep or a hat-in-hand interruption to the published upgrade schedule. . . 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 [email protected] -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Brian Westerman Sent: Sunday, January 13, 2019 12:21 AM To: [email protected] Subject: (External):Re: z/OS 1.12 question That's a pretty odd thing to happen from 2.1 to 2.3. What products were involved? I can see if the product had some ties into JES2 and you had to reassemble or relink the interface, but that can happen just by adding maintenance to any system. It's really odd for almost any vendor product to be tied into a specific OS especially when they are quite so close in release. Brian ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
