Browse Prior Art Database

Simple Installed Software Licence Validation regime for IBM MVS systems

IP.com Disclosure Number: IPCOM000016677D
Original Publication Date: 2003-Jul-09
Included in the Prior Art Database: 2003-Jul-09
Document File: 2 page(s) / 44K

Publishing Venue

IBM

Abstract

A license validation mechanism is described.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

Simple Installed Software Licence Validation regime for IBM MVS systems

Software licensing regimes have been around for some time. Generally, the solutions involve generating a 'user query' of some kind to ascertain a 'licence validation key', and then ensuring that the supplied key is acceptable before allowing any application processing to progress. Whilst there is no doubt that these type of solutions are very effective at preventing users from breaking their software licensing agreements, it is possible that these processes might outweigh the requirements of a new software product for several reasons:

No software licensing regime is completely bullet-proof.

The software should rely on the legal enforcement of the licence for protection. In

terms of physical protection, the software need only implement a simple regime, whereby the user will be informed when the licence period is coming to an end, and will be prevented/discouraged from employing the software after the licence period has expired. The licence validation process should not require the user to return to the vendor

for any kind of authorisation key. The licensed package must be simple and quick to install directly from its distribution CD, without the user having to suspend the exercise to await authorisation codes from the vendor. This also serves the vendor's benefit as no call centre or Web page maintenance will be required to respond to these types of queries. Whilst the validation process should be simple, preferably the establishment of

the valid software period should be executed as part of an installation process that does not require the exposure of source code to the user.

A mechanism that addresses these problems will now be described.

    When an application is installed onto a system, an installation timestamp is automatically established. When certain license controlled functions are executed, then the installation timestamp is subtracted from the execution timestamp to establish an installation period. If the installation period exceeds the value that is allowable for the appl...