How Products Are Licensed
BMC Software, Inc., Confidential and Proprietary Information
Appendix A BMC Software Product Authorization A-7
Updating Product-Authorization Tables
To trigger the grace period, the license validation process must update the
authorization tables. If the product load library must be WRITE-protected,
problems could occur with updates. To avoid problems, you can place the
authorization tables in another data set and concatenate that data set to the
product load library.
The concatenated authorization-table library should have the same DCB
attributes as the product’s load library. (The RECFM for the table library
must be U.) If you have several BMC Software products, you may want to
dedicate one library that includes all authorization tables for all products.
Before updating the library that contains the authorization tables, the license
validation process determines whether the data set is in LNKLST. If the data
set is in LNKLST, the license validation process does not attempt an update.
Running a Product on an Unlicensed Processor
When you run a product on an unlicensed processor, a 15-calendar-day grace
period can be triggered. After this grace period expires, the product will not
run or will run with diminished functionality.
Note: The product will continue to function normally when run on a
licensed CPU, even if the grace period has been triggered or has
expired.
To prevent this situation, you should obtain a RESET password from BMC
Software Contracts Administration. If you apply the RESET password before
the grace period ends, it updates the product-authorization table and makes
another 15-calendar-day grace period available.
When the grace period is triggered, the Product Authorization utility (either
online or in batch mode) and the affected product issue a message that
advises you of the expiration date.
