I'm a customer, with many products requiring CPU codes and other
software based licensing schemes, and they are a PITA.
* Every vendor does it differently.
* Detailed documentation needs to be written and maintained for both
DR situations and CPU push/pull activities.
* Whenever we do a CPU push/pull it usually takes us weeks if not
months for all the vendors to supply us with new permanent license
codes, while in the mean time we're using temporary codes that
have to be gotten and applied, with all the change control
activities associated with that process.
If it up to me and I had a choice between two products, one with an
software licensing mechanism, and one without, but with the legal right
to perform audits in my environment I'd pick the second vendor almost
all the time.
Mark Jacobs
On 12/27/11 13:40, zMan wrote:
On Tue, Dec 27, 2011 at 8:55 AM, Mark Zelden<m...@mzelden.com> wrote:
Obviously the point of view of someone who doesn't make a living by
selling their software.
Au contraire, I sure do make my living selling software. My point is
that in my experience, the cost of fighting the CPUID battle isn't
worth it. The counterexamples cited are pathological -- given a CPUID,
such shops would just hack it (not that hard, no matter what anyone
says). The expired SAS shop Barry cites is another example of someone
going around it.
I just don't see the point.
FWIW, I've never had to live with the customer end of CPUIDs -- only
the vendor end. But I fail to see how they would ever be seen as a
boon by customers.
--
Mark Jacobs
Time Customer Service
Tampa, FL
----
One of life's greatest mysteries is how the boy who
wasn't good enough to marry your daughter can be the
father of the smartest grandchild in the world.
Yiddish Proverb
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
