HP OpenVMS Systems

ask the wizard
Content starts here

Cause of NOLICENSE error? (DECnet)

» close window

The Question is:

 
From one day to another my customer can not connect to another Decnet nodes but
 he can connec trought TCP/IP
All needed licentes are active and loaded
When we try to start the net we have this problem:
 
 
$ @startnet
%SYSGEN-E-NOUNLOAD, driver is not unloadable
%SYSGEN-F-DEVACTIVE, device is active
%RUN-F-CREPRC, process creation failed
-SYSTEM-F-DUPLNAM, duplicate name
%DCL-I-SUPERSEDE, previous value of MOM$SYSTEM has been superseded
%DCL-I-SUPERSEDE, previous value of MOM$SYSTEM_NOSOFTID has been superseded
%DCL-I-SUPERSEDE, previous value of MOM$SYSTEM_SOFTID has been superseded
%NCP-W-INVPVA, Invalid parameter value , Physical address
Line = SVA-0
 
%NCP-W-OPEFAI, Operation failure
Circuit = SVA-0
%SYSTEM-F-NOLICENSE, operation requires software license
%NCP-I-NOINFO, No information in database
%RUN-F-CREPRC, process creation failed
-SYSTEM-F-DUPLNAM, duplicate name
 
 
or
 
NCP> Show know node
Known Node Volatile Summary as of 28-JUN-2000 11:58:40
 
Executor node = 1.5 (VAX4)
 
State                    = on
Identification           = DECnet for OpenVMS VAX V6.1
 
 
    Node           State      Active  Delay   Circuit     Next node
                              Links
 
 1.1 (VAX5)      unreachable
 1.4 (COOP)      unreachable
 1.6 (DS90L7)    unreachable
 1.10 (DS90L6)   unreachable
 1.11 (DS90L5)   unreachable
 1.20 (DS90TL)   unreachable
 
NCP>set circuit sva-0 state on
%NCP-W-OPEFAI, Operation failure
 
%SYSTEM-F-NOLICENSE, operation requires software license
NCP>
 
But everything under TCP/IP works.
What can i do
 
 


The Answer is :

 
  Based solely on the message:
 
%SYSTEM-F-NOLICENSE, operation requires software license
 
  You clearly lack a necessary license PAK.
 
  Please contact the Compaq Customer Support Center for assistance,
  as it appears that you do not have an appropriate DVNETEND (DECnet
  end-node) or DVNETRTG (DECnet routing) license PAK loaded on and
  available on this system.  This could be due to a problem with the
  license itself (eg: expired, insufficient units, etc), or due to
  the configuration of LMF databases (eg: all node-specific licenses
  must be registered in every LMF database present in a cluster), or
  due to some other configuration- or license-specific problem.
 

answer written or last revised on ( 28-JUN-2000 )

» close window