|
What I mean is to be able to remove one, and have OS400 mark it internally as 'removed', or 'disabled', so that it can never be used again. The vendor would have to provide a new key (using vendor data). But the old key would not be valid anymore. I submitted this to IBM years ago. Mike Grant Bytware, Inc. 775-851-2900 http://www.bytware.com -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Bipes Sent: Tuesday, February 14, 2006 2:08 PM To: Midrange Systems Technical Discussion Subject: RE: Software Licensing for HA systems Caution, If you can remove them, someone can re-install and get another grace period without a full scratch. -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of QSCANFSCTL Sent: Tuesday, February 14, 2006 12:36 PM To: 'Midrange Systems Technical Discussion' Subject: RE: Software Licensing for HA systems If software vendors would use the OS/400 license management APIs, and give a grace period to their product definitions, the product will be able to handle a typical DR failover with no licensing issues.... Overall, I'm pretty happy with them. I wish there was a way to remove a license key, so that software transfers weren't such a PITA -- ARE YOU LISTENING IBM?
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.