I wouldn't be. Maybe no problem with licensing, but support is another matter. If it's not their product, how would they know? They don't license other ISV products internally, so all learning is in the field, or "handled" by sub-contracting out the work (as we often did in ITS), or by buying out the customer's IT staff (as they often did in Outsourcing). If that didn't work, or if it broke down, due to repeated downsizing and/or waves of voluntary departures, IBM then "dealt with it" by attempting to convert off of ISVs to their own "equivalents" (FSVO, equivalents). I lost count of how many times I asked, "the marketing rep told you it would do what, exactly?"
Perhaps things have improved in the 15 years since I departed, but perhaps not, given that ITS has since been disbanded, outsourcing has now been spun off, and some marketing reps are still prone to hyperbole. Art Gutowski On Tue, 1 Jun 2021 12:17:36 +0000, Seymour J Metz <sme...@gmu.edu> wrote: >Yes, like any other outsourcing and time-sharing contract, you need to define >your requirements before committing to it, and that includes license issues. >It's your responsibility to include what you need in the contract, but I would >be very surprised if IBM was unable to deal with 3rd party software. > >-- >Shmuel (Seymour J.) Metz >http://mason.gmu.edu/~smetz3 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
