Jon, I agree with you. CA's license key method is about as painless as I have seen.
One gripe I have is with a different vendor, (SAS, are you listening?). I got my SAS key and applied it to my production LPAR but got busy and forgot to apply it to the sandbox. Several months later I needed to run a SAS job on the sandbox and the job went down with a U999, no errors, no messages to indicate that the key had expired, just an abend. To me, that is definitely the wrong way to enforce a key! Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Jon Brock Sent: Monday, February 19, 2007 9:52 AM To: [email protected] Subject: Re: License keys for ISV products(What alternatives are there?) I realize this is heresy, but I like the way CA does it. Parts of it, anyway. We get warnings before a key expires. Once we get a new key, we add it to our options file in Common Services (formerly CA-90's, etc.) and rerun CAS9 -- no pain, no downtime. I have no problem with vendor implementing a license key strategy as long as it is done properly. Jon ---------------------------------------------------------------------- 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
