You can never be too paranoid.

I once had a boss who asked me if he was taking too many copies of Stand-alone 
restore (SAR) to a DR test and I told him that he might hear me saying that he 
didn't have enough but that he would never hear me saying that he had too many. 
The same principle applies to asking 3rd party vendor about potential 
compatibility issues; it can only help, and not doing so can hurt.


--
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: Sunday, January 13, 2019 10:43 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: z/OS 1.12 question

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
robin...@sce.com

-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of Brian Westerman
Sent: Sunday, January 13, 2019 12:21 AM
To: IBM-MAIN@LISTSERV.UA.EDU
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 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

Reply via email to