On 3/26/2014 11:38 PM, Ed Jaffe wrote:
On 3/26/2014 9:20 AM, Charles Mills wrote:
Right. Good input. Thanks. I have shipped software with a hard-coded
expiration date. What I am looking for is a "floating" expiration date
that
would be 30 days after installation, whether installed today or a year
from
today.
Our trial software expires "n" days after download. The key is stored in
a load module. It would not be difficult to use the SHSCRIPT function of
SMP/E to create a module in a z/OS UNIX directory with expiry date
relative to install date. Food for thought for the future. :)
However, I really don't like the idea of an expiry date relative to
first execution. Implementation could get "messy."
Also, what about the shop that tries to locate the
end date and zap it? You may say it doesn't happen
but I have heard tales...
-Steve Comstock
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
