Overview

Beta products and applications check for the presence of a valid license. Normally, a single license file contains all license information and is shared by the products.

License check time

Depending on the product or application you are using, the license check is carried out when the product is started, and afterwards cyclically at midnight (or another hour if you have coded the LST parameter Bnn_LICX_CHECK_TIME=hh).

This applies to master and slave STCs and to jobs that are running as database masters (SIGNON=NO).

What happens when a license is found

When a license file is found for the Beta product that is starting, it will be checked. The following may occur:

• The license file contains a valid license. The product STC is started.
• There is a discrepancy in the license file. What happens next depends on the discrepancy and the product concerned:
  • If the license is a trial version (InstID=UNSPECIFIED, installation type=TRIAL) and the trial time has not yet expired, the product STC will be started with the appropriate message.
  • If the license is a trial version (InstID=UNSPECIFIED, installation type=TRIAL) and the trial time has already expired, the product STC will not be started and an error message will be generated.
  • If the license contains toleration parameters (depends on the license type), the product STC will be started with the appropriate message.
  • If the license file has been changed in any way, the product STC will not be started and an error message will be generated.
  • If the basic license is valid, but the add-on license for CAF/VAF/IAF is invalid, the online user will receive the appropriate message.
• If no license file is found, it will not be possible to start the product.

Termination date

"License will expire on yyyy-mm-dd" indicates the termination date of a license. yyyy-mm-dd is the last date when this license is valid. License checks carried out on a later date will detect that this license has expired. By default, the STC detects this at the very beginning of the following day (Bnn_LICX_CHECK_TIME=00). If the product license is affected, the STC will normally stop and you will be unable to restart it with this license file.

Tolerance period: If the license is permanent and its policy is non-enforced, the STC will continue to run for another 42 days after the termination date.

Goodwill period: The goodwill period does not provide any extension beyond the termination date, but it enables you to run a product for up to 30 days in a different environment, for example, on a standby machine. Reaching the end of goodwill does not invalidate the license file. It can be used when the product is transferred back to the original environment, and it can later be used on the standby machine in case of another emergency.

Product add-ons

When the database master started task is checked, all the product add-ons anchored in the product are also checked.

Usage license check

If the type of license being checked is a usage license, the check will take place globally. However, the usage values themselves will be checked by each licensed product separately.

If you have a server license

If you have a server license, you must ensure that the product STCs (database servers) or users submitting the batch job for a MASTER RFF batch job either have their own OMVS segments or use the default OMVS segment. They will need READ access to facility class BPX.DEFAULT.USER.

Automatic default OMVS segments

To set up RACF so that it automatically uses default OMVS segments for users and groups that do not have their own OMVS segments in their USER or GROUP profiles, proceed as follows:

• Create a FACILITY class profile called BPX.DEFAULT.USER with universal access READ and APPLDATA(defaultuser/defaultgroup).
• Define a RACF user profile containing an OMVS segment for defaultuser.
• Define a RACF group profile containing an OMVS segment for defaultgroup.