Re: Software Licensing for HA systems

I looked into those APIs once for my software.  After 10
minutes (ADD kicked in) I said "I'm gonna roll my own..."

So I did.  :)  Even the 30 day period thing.  And it's set
up so if someone is testing DR, they can email me and
request a key for any amount of time (max 90 days) starting
at any date, not just today's date (which is why my site
gives them).

It's worked out great for a couple customers so far.  I
didn't ask why they wanted to set the clock back on their
DR machine for testing.  :)

Now, if there was an easy way to retrieve the LPAR ID that
is unique and would never change.  :)  I have code to do
it, but I don't dare implement it cuz it's messy.  lol...

Brad

On Tue, 14 Feb 2006 15:37:18 -0800
 "QSCANFSCTL" <QSCANFSCTL@xxxxxxxxxxx> wrote:
> The way the APIs work, the grace period starts the first
> time the code
> requests a license. So that depends on how the code is
> written. It could be
> from date of load, or the first time something is
> executed, etc. From there
> it is calendar days. The only way to reset the grace
> period is to scratch
> the disk. Otherwise the vendor has to issue a temp key
> (grace period has
> expired).
> 
> 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
> Ron-Zimmerman@xxxxxxxxxxxxxxx
> Sent: Tuesday, February 14, 2006 2:56 PM
> To: Midrange Systems Technical Discussion
> Subject: RE: Software Licensing for HA systems
> 
> 
> That is exactly what one of the vendors in question does.
>  When you 
> install their software, it will give you a 30 day grace
> period.
> 
> What I am unsure of is how and when that grace period
> starts.  Does the 
> grace period start as soon as the software is loaded on
> the machine or 
> does it start the first time a user signs on to that
> software?
> 
> Also, is that 30 calendar days or is it 30 days of usage?
>  In this case, I 
> think it's 30 calendar days, so once we are past that 30
> day window, we 
> will need to get a new key from the vendor.
> 
> Thank you,
> Ronald L. Zimmerman
> I.T. Applications Manager
> Swiss Valley Farms, Co.      http://www.swissvalley.com
> "The Good for You Company"
> Email: Ron-Zimmerman@xxxxxxxxxxxxxxx
> 
> midrange-l-bounces@xxxxxxxxxxxx wrote on 02/14/2006
> 02:36:19 PM:
> 
> > 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.
> The product runs
> > without a license key for a grace period. After the
> grace period the 
> vendor
> > can extend the grace period if necessary. This
> eliminates the need to 
> worry
> > about license keys at Sunday 3am, because the customer
> will have had 30 
> days
> > (or whatever grace period the vendor uses, in IBMs case
> it is 70 days), 
> to
> > obtain license keys during normal business hours. No
> problem.
> > 
> > For advanced testing, customers can request license
> keys for the DR 
> system
> > that will expire at some mutually agreeable date/time.
> > 
> > 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?
> > 
> > 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
> Jeff Crosby
> > Sent: Tuesday, February 14, 2006 11:34 AM
> > To: 'Midrange Systems Technical Discussion'
> > Subject: RE: Software Licensing for HA systems
> > 
> > 
> > > I was recovering the customer at a DR site, and their
> H/R 
> > > vendor had no method of getting me a software key
> over the weekend.
> > > 
> > > So I changed the system serial number, and we ran
> payroll.
> > 
> > ROTFL!
> > 
> > > IBM was really mad at me!
> > 
> > TFB.
> > 
> > -- 
> > Jeff Crosby
> > Dilgard Frozen Foods, Inc.
> > P.O. Box 13369
> > Ft. Wayne, IN 46868-3369
> > 260-422-7531
> > 
> > The opinions expressed are my own and not necessarily
> the opinion of my
> > company.  Unless I say so.
> > 
> > 
> > -- 
> > This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing 
> list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit:
> http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the
> archives
> > at http://archive.midrange.com/midrange-l.
> > 
> > CONFIDENTIALITY NOTICE:  This e-mail message and any
> attachment to 
> > this e-mail message contain information that may be
> privileged and 
> > confidential.  This e-mail and any attachments are
> intended solely 
> > for the use of the individual or entity named above
> (the recipient) 
> > and may not be forwarded to or shared with any third
> party.  If you 
> > are not the intended recipient and have received this
> e-mail in 
> > error, please notify us by return e-mail or by
> telephone at 
> > 775-851-2900 and delete this message.  This notice is
> automatically 
> > appended to each e-mail message leaving Bytware, Inc. 
> > 
> > 
> > -- 
> > This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing 
> list
> > To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> > To subscribe, unsubscribe, or change list options,
> > visit:
> http://lists.midrange.com/mailman/listinfo/midrange-l
> > or email: MIDRANGE-L-request@xxxxxxxxxxxx
> > Before posting, please take a moment to review the
> archives
> > at http://archive.midrange.com/midrange-l.
> > 
> 
> -- 
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit:
> http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/midrange-l.
> 
> CONFIDENTIALITY NOTICE:  This e-mail message and any
> attachment to this e-mail message contain information
> that may be privileged and confidential.  This e-mail and
> any attachments are intended solely for the use of the
> individual or entity named above (the recipient) and may
> not be forwarded to or shared with any third party.  If
> you are not the intended recipient and have received this
> e-mail in error, please notify us by return e-mail or by
> telephone at 775-851-2900 and delete this message.  This
> notice is automatically appended to each e-mail message
> leaving Bytware, Inc.  
> -- 
> This is the Midrange Systems Technical Discussion
> (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit:
> http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the
> archives
> at http://archive.midrange.com/midrange-l.
> 

Bradley V. Stone
BVS.Tools
www.bvstools.com