Chapter 5:

Using the License Manager

Use the License Manager to both license and register additional products that you install after the system is up and running. Many add-on products prompt you for a license during installation, but some products (like the ability to support more memory and the SCO Update Service Enabling License) are not installed; instead, they are enabled by entering a new license.

This chapter shows you enough to get you going using the License Manager right after installation. More information is available in the online help on http://localhost:8458, by clicking on Installation and Licensing.

Starting The License Manager

Log in as root (or the system owner) and start the License Manager in one of these ways:

The scoadmin command only recognizes the spelling "license", not "licence".

Once you start the License Manager, it displays the product licenses currently installed on the system.

Licensing products

To enter a new product license, from the License Manager main screen:

1. Select License-Add from the command menu.

2. Enter your license information:

License Number
 License Code
 License Data (not provided with every license)

3. Click on License.

The License Manager main screen displays your new license, and the appropriate software should now be enabled. (Note that a SCO Update Service License is not enabled until you register the license, and enter the Registration Key into the License Manager. Some Update Service Licenses are pre-registered; a pre-registered license is enabled as soon as you add it.)

Your system software displays reminders about unregistered software. To determine which products have been licensed or registered, use the View menu command in the License Manager. See "Registering products".

Removing product licenses

To remove a license, highlight the licensed product from the License Manager's main screen, and then select License-Remove from the command menu. Once you remove a product license, that product's functionality will be unavailable on the system.

Registering products

The benefits of registering your installed software products are discussed in the section "Registration". Follow this procedure to register any installed product.

Note that you must register your UnixWare Edition License before you can register the other products on your system. If you have an Update Service Enabling License, you can register that license instead, and your Edition license will be automatically registered along with the SCO Update Service. See "Licensing Software" for more information on product licenses.

1. Start the License Manager; see "Starting The License Manager". The License Manager displays a list of installed licenses.

2. Do one of the following to bring up the Registration window:

3. The License Manager displays the Registration Lock for the license you selected in the last step. Mail is also sent to the logins specified in the file /var/sadm/install/default containing the Registration Lock.
 The mail's Subject: line contains the selected license's Serial Number (the License Number on the License Manager's Registration window). The mail's content contains the Registrations Web Site's URL attached with a query containing the license's Registration Lock. You need to go the the Registration Web Site, detailed in the next step, in order to obtain the Registration Key that needs to be entered in the License Manager's Registration window. It is suggested that you leave the Registration window open while you are obtaining the Registration Key from the Registration Web Site.

4. Go to the Registration Web Site using one of these methods:

5. If you still have the Registration Lock window for the appropriate product open, enter the Registration Key into the apppropriate box on the Registration Lock window. Otherwise, select the product for which you just obtained a Registration Key and click on License-Register. Enter the Registration Key into the appropriate box and click OK.
 Registration of the product is now complete.

When you register an SCO Update Enabling License, the Update License is activated and you can begin using the SCO Update Service to obtain system software updates via the web.

Once all the products on a system have been registered, registration reminder messages should no longer appear when you login.

Note: Your software generates a new System ID each time you install the operating system. If you reinstall your system, you must repeat the registration process and obtain a new Registration Key.

Troubleshooting license and registration problems

The following represent the most common difficulties with licensing and registration:

Note also that TCP/IP must be configured and running in order for the License Manager to run. If you deferred network setup during installation, enter scoadmin network at a shell prompt (as root) to launch the Network Configuration Manager, configure a networking card, and configure and start TCP/IP.

License Manager will not accept registration key

If the Registration Key is invalid or was entered incorrectly, an error message appears. Verify that you entered the Registration Key correctly and that you did not type the System ID by mistake. If you still receive the error message, contact the organization that issued your license to verify that your Registration Key is accurate.

License Manager will not accept license information

Make sure that you entered the license information correctly. Occasionally, characters on the license are difficult to read.

If you are entering a new Edition License or SCO Update License, it is also important that the callback and registration specifiers in the license match exactly. These are found in the License Data part of the license information, after the letters "k" and "q". If the digits after these letters do not match, the new license is rejected. Contact the organization that provided you with the new license, and have your existing license information ready so that the proper license can be issued to you.

Licensing Policy Manager Daemon (sco_pmd) has terminated

If the policy manager daemon terminates, you might see this message: 


The Licensing Policy Manager Daemon (sco_pmd) has ter-

minated and been restarted. This is a normal occurrence 

only when a license is removed with the License Manager 

utility.  If this is not the case, your system may have 

a problem which could lead to undesirable behavior. 

Contact your service provider if you suspect that there 

is a problem.

Or you might see this message: 


No user licenses were found on this machine. Please 

boot single-user and correct this situation. Licensed 

software will not operate until user licenses are 

installed. The License Policy Manager Daemon (sco_pmd) 

was unable to start. This is usually due to a read-only 

root filesystem, lack of user licenses or a damaged 

program image file (/etc/sco_pmd). If this is not the 

case, please contact your service provider.

The policy manager daemon is a background process that monitors licensing on the system. If you are using an Evaluation License on your system that has has expired, then your system will display this message. Contact the supplier of the software to obtain a valid license for your software. If you do not have an Evaluation License, see "Policy manager has died".

License has expired

If the License Manager indicates your operating system license is expired, check the system clock by entering the date(1) command. If the date is incorrect, you should log in as root (or the system owner) and enter this command: 


setclk

This updates the system time with that of the battery-powered hardware clock (CMOS). If date is still incorrect, use this form of the date command to update the system clock. 


date MMDDhhmmYY

where MMDDhhmmYY is the correct time in month-day-hour-minute-year format. For example, here is the correct entry for 9:31 AM on August 31, 1997: 


0831093197

Once you have changed the clock time to reflect the current time, reboot your system, start the License Manager and check to see if the license has changed from Expired to Yes. Your operating system license should be fully operational within the options specified by the license.

Checking for product license expiration

The expiration information for licenses is shown in the main display for the License Manager under Status. If you have an expiring license, the display will read Valid Until date.

No user licenses were found on this machine

If you see this message at boot time: 


No user licenses were found on this machine. Please 

boot single user and correct this situation. Licensed 

software will not operate until user licenses are 

installed. The License Policy Manager Daemon (sco_pmd) 

was unable to start. This is usually due to a read-only 

root filesystem, lack of user licenses or a damaged 

program image file (/etc/sco_pmd). If this is not the 

case, please contact your service provider.

This error message is usually caused by a system clock that is grossly out of date. It may also may result from a lack of user licenses or a corrupted policy manager daemon (/etc/sco_pmd). See "Policy manager has died" for more information.

Policy manager has died

If any application reports a license failure and you believe that this is incorrect, it is possible that either the policy manager daemon, /etc/sco_pmd, has stopped and not restarted, or some crucial file required by the policy manager to satisfy the login request is missing or corrupted.

You may be logged out and be unable to log in to troubleshoot the problem. Additional error messages may also appear. If so, simply turn the system off and reboot. If the error messages persist when the system is brought up, follow the procedures described here.

Here are possible specific sources of corruption or malfunction:

The /etc/sco_pmd binary is corrupted or missing

The policy manager (/etc/sco_pmd) must be present and running for your system to function. If the /etc/sco_pmd file is missing, restore it from backups.

Key files or directories are missing

The directory /pmd or its contents, the named streams pipes IPCCT_pipe, PMDCT_pipe, LST_pipe, and the file sco_pmd.pid, are corrupted or missing.

If /pmd exists, but any of its file contents do not, restore them by stopping and restarting /etc/sco_pmd. In order to do this, perform these steps:

1. Enter the command:
 


ps -ef | grep sco_pmd
which should return a line similar to this:
 

root    11     1  TS  70  0   Nov 26 ?     0:00 /etc/sco_pmd

root    12    11  TS  80  0   Nov 26 ?     0:03 /etc/sco_pmd
Any of the numbers shown may vary on your system, with the exception that one of the entries should have "1" in the third field (parent process ID). This is the "parent" copy of sco_pmd, and the other entry is the"child", whose parent process ID should match the second field (process ID) of the parent entry.

2. Kill the child process for sco_pmd. In the example, the command would be:
 


kill 12

3. In a few moments, run the ps command again. You should observe that a new child sco_pmd is running.

4. Check the contents of /pmd. You should see four files:
 


DCT_pipe

LST_pipe

sco_pmd.pid

If licensing problems persist, kill all of the child daemons shown in the output from step 1 and remove the contents of /pmd, then enter: 


/etc/sco_pmd

The root filesystem is mounted read-only

This has been identified as a common reason for policy manager-related failures. Of course, in this case, the policy manager errors would accompany many write failures to root filesystem, with corresponding error messages.

You can see if the root filesystem is mounted read-only by running the Filesystem Manager. The Access Mode is listed in the main display. If this is the case, modify the mount configuration to be read-write.

No user licenses exist, or there are no more licenses

First, determine how many users are already logged in to the system. A user is defined as a distinct physical keyboard or a login over the network. If indeed the system has run out of licenses to check out, the only way to avoid the error message is to add user licenses by purchasing an additional-user license product.

If the login user count has not been exceeded, it is possible that the license database itself has been corrupted. Follow the steps below to re-apply the user licenses on the system. This procedure assumes that user licenses are supplied only through the UnixWare 7 Certificate of License and Authenticity. If you have already licensed additional users with a separate user-license product, apply the procedure to that product first.

1. Use the wall(1M) command to tell all users to log off the system.

2. When all users are logged off, invoke the License Manager. Use the View menu command to view and record all license information for your UnixWare Edition license and any user license packs.

3. If any additional user license packs are installed, remove them by highlighting each one and selecting License-Remove from the command menu.

4. After removing all user license packs, highlight the UnixWare 7 Edition license, and select License-Remove from the command menu.

5. Re-license UnixWare 7 by selecting the License-Add from the command menu. Re-enter your UnixWare Edition license data.

6. Re-apply any user license packs by selecting the License-Add from the command menu. Re-enter your user license data.

7. Run the grep command discussed in "Key files or directories are missing" to check whether the policy manager daemon is running. If two instances of the /etc/sco_pmd process are not running, issue this command to restart the policy manager:
 


/etc/sco_pmd
Repeat the grep command to verify that two instances of sco_pmd are running.

8. Tell users to log back in to the system.

© Copyright 2004 The SCO Group, Inc. All Rights Reserved.