 |
The Question is:
System is ES40 running Alpha OpenVMS 7.2-1.
The system was up and running for 160 days without a reboot/crash.
We decided to reboot it during the last weekend just to clear some stuff on the
server, when we had the following problem.
While rebooting, we got a message :
%%%%%%%%%%% OPCOM 18-AUG-2001 20:23:28.88 %%%%%%%%%%%
Message from user SYSTEM on SERVER
%LICENSE-E-NOAUTH, DEC OPENVMS-ALPHA use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
%%%%%%%%%%% OPCOM 18-AUG-2001 20:23:29.08 %%%%%%%%%%%
Message from user SYSTEM on SERVER
%LICENSE-E-NOAUTH, DEC VOLSHAD use is not authorized on this node
-LICENSE-F-NOLICENSE, no license is active for this software product
-LICENSE-I-SYSMGR, please see your system manager
So we checked and enabled these 2 licenses, and rebooted, when we found that
ALL of the installed licenses in the database were disabled and we had to go
through everyone to enable them.
I do not think that someone went and disabled them!!!
Is there a time frame that the LMF database disables the licenses if system is
not rebooted?.
Also is there is a limit on the length of the console cable for the ES40?
Thanx
Mohamed
The Answer is :
1: OpenVMS has no automatic mechanism for the purpose of disabling (valid)
license product authorization keys (PAKs). There are (documented) manual
mechanisms for this purpose (and a mechanism to view the command history),
of course.
2: Obviously yes. For information on EIA232 and EIA423 and similar wiring,
please see the applicable EIA standards. Environments with over-length
serial cabling, with poor-quality or failing wiring, or signal interference
will require use of shorter cable runs, shielding (or fibre optic) cabling,
terminal servers or similar "converters" or signal amplifiers, relocation
of cabling away from interference, lower baud rates (if available), etc.
3: One question per posting, please.
|
