On Sun, 18 Feb 2007 19:02:38 -0500, Reda, John <[EMAIL PROTECTED]> wrote:
<snip> >We offer multiple ways for the customer to install and maintain their license keys. The recommended method is having the keys in a sequential data set. This way modifications to the license keys can be as easy as updating a single data set. <snip> John, We migrated to the key data set some time ago. I don't think it was documented when / how often the data set was checked. Is it for every sort invocation? I don't think I found evidence that it was. Thanks, Mark BTW... as far as the rest of this discussion, I totally sympathize with the vendors. As someone who consulted full time for many years and also worked with a vendor directly whose product was abused due to no license control, I understand. While a lot of the abuse was not intentional (data center consolidations, then copying libraries from one environment to the other), a good deal of it was also done just because someone could. For example, it is very easy for a sysprog to copy a product like FDR from one system to another because they are more familiar with it than DFDSS (I saw lots of examples like this in data centers that went though consolidations). It would be nice if there was a common method of doing this, but not all vendors needs and pricing models are the same nor are the way their products work. Some vendors now do LPAR (size) pricing, some do only site licensing, some license by the box, the size of the box and the number of engines. You might as well ask for common installation method for all products too. I'm not holding my breath. License keys are a fact of life just like spam. Get over it. What you need to do is create good documentation for the products that require them, note whether they are date sensitive, CPU sensitive, or both and document exactly how to update them - including who to contact for scheduled updates and emergency updates (phone numbers, web sites, etc.). Manage that information / documentation how ever it suits your environment, but it does need to be managed in a modern data center. -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group: G-ITO mailto:[EMAIL PROTECTED] z/OS and OS390 expert at http://searchDataCenter.com/ateExperts/ Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html ---------------------------------------------------------------------- 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
