>I don't see it as being a big deal either. When a customer licenses a
product, they are given a key. A year later (or shortly before the license
expires), the customer receives an invoice. If they pay the invoice, they
get a new key.
Really? Most of the time the customer has to discover the key is expired!
Even if you're not sent a new key ahead of time, the product should start
warning you before the key expires. If you're encountering situations where
you're not being sent a new key ahead of time and the product isn't warning
you a key is about to expire, something is seriously wrong.
>The customer replaces the old key with the new key (e.g. enters it in a
flat file or ISPF table or whatever). Nothing needs to be to
compiled/linked/refreshed/IPL'd (etc). It just takes a couple of minutes to
enter the new key, and the customer is good to go for another year
WRONGO! We have to compile/linked/refresh all of our keys!
Not all products are like that. Maybe then the issue isn't so much that keys
are required, but the way they're sometimes implemented by the vendor? If
keys were always received well before the old ones expired, and all you had
to do was enter them in a flat file, would that be a big deal?
Dave Salt
SimpList(tm) - The easiest, most powerful way to surf a mainframe!
http://www.mackinney.com/products/SIM/simplist.htm
_________________________________________________________________
Your Space. Your Friends. Your Stories. Share your world with Windows Live
Spaces. http://spaces.live.com/?mkt=en-ca
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
