This could be the IP license, or any of various other licenses related to an interactive login. There's a logical name described below that will allow you -- from the console or from some session you can get logged in -- to see what license is triggering the error.
regarding the following... I'll fix the stale LURT URL reference for the next edition of the OpenVMS FAQ. The current URL dejour for the LURT and licensing info is
http://licensing.hp.com/swl/view.slm?page=indexAnd I'll add the OpenVMS I64 OE license PAKs to the list. The FAQ home is over at
http://www.HoffmanLabs.com/vmsfaq/...
5.39 Resolving License PAK Problems?
The PAK release date, the PAK termination date, and the PAK version are the usual culprits when a license product authorization key (PAK) check failure occurs.
The PAK termination date is the date when the license PAK will expire.
The PAK release date is the date of the most recent release date of the software package that will be permitted by the particular license PAK. (The release date check is analogous to a product version check.) The PAK version indicates the most recent product version that is permitted by the license.
Having multiple license PAKs registered (and active) can also cause problems if an expired PAK gets loaded. You will want to DISABLE license PAKs you do not wish to have loaded.
Other problems include a failure to register each PAK in all license databases throughout a multiple-system-disk cluster, with a consistent set of /INCLUDE lists specified across each of the duplicated PAKs.
Additionally, you could have an invalid LMF$LICENSE logical name defined. (If no LMF$LICENSE logical name is defined, the standard license database named SYS$SYSTEM:LMF$LICENSE.LDB will be used.)
You can display license failures by defining the following logical name:
$ DEFINE/SYS/EXEC LMF$DISPLAY_OPCOM_MESSAGE TRUE
Enable your terminal as a license operator (REPLY/ENABLE=LICENSE), define the LMF$DISPLAY_OPCOM_MESSAGE logical name, and then try the failing operation again. You should see one or more OPCOM messages displayed.
If you have the LMF$DISPLAY_OPCOM_MESSAGE logical name defined, you can (will?) see spurious license check failures-various products will check for multiple licenses, and a few products will check for PAKs that either have not yet been or will not be issued. Once you figure out which license has failed, you will want to deassign this logical name.
Note
That there are no license check failures does not indicate that the particular product or operation or use is permissible per applicable licensing agreements. Please consult the applicable agreement(s) for licensing-related information and requirements.
To register a license PAK on a DECwindows system when DECwindows cannot start (because of an expired license or other licensing problem), follow the steps outlined in section Section 5.6 up through the use of the AUTHORIZE command. In place of the AUTHORIZE command, use the console to register the license PAKs. Also see Section 12.4 for licensing and troubleshooting information.
For information on licensing and on the numbers of license units required for various products and various platforms, the License Unit Requirements Table (LURT) is available at:
o
http://www.compaq.com/products/software/info/...
--
...
Some of the more common license PAKs:
DECnet Phase IV: DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP*
DECnet-Plus: DVNETRTG, DVNETEND, DVNETEXT, or NET-APP-SUP*
TCP/IP Services: UCX, or NET-APP-SUP*
OpenVMS Alpha: OPENVMS-ALPHA and OPENVMS-ALPHA-USER
OpenVMS VAX: VAX-VMS
OpenVMS Galaxy: OPENVMS-GALAXY
Cluster (Alpha): VMSCLUSTER, NET-APP-SUP*
Cluster (VAX): VAXCLUSTER, NET-APP-SUP*
...
