[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference pamsrc::decmessageq

Title:NAS Message Queuing Bus
Notice:KITS/DOC, see 4.*; Entering QARs, see 9.1; Register in 10
Moderator:PAMSRC::MARCUSEN
Created:Wed Feb 27 1991
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2898
Total number of notes:12363

2740.0. "LICENSE-F-NOAUTH prblm on VMS" by SWETSC::EKLUND (On a clear day you can see forever) Mon Jan 20 1997 09:31

T.RTitleUserPersonal
Name		DateLines
2740.1It may be...KLOVIA::MICHELSENDECmessageQ EngineeringMon Jan 20 1997 10:086
2740.2Thanks for the idea.SWETSC::EKLUNDOn a clear day you can see foreverWed Jan 22 1997 08:0517
2740.3Fixed with V3.2B...KLOVIA::MICHELSENDECmessageQ EngineeringThu Jan 23 1997 09:354
2740.4Fixed realy?OSOEIC::NARAMOTO_�ޥ��֡���äƤʤ��ͤ�Mon May 26 1997 05:5030
Is this problem fixed ?

Today, I get DMQ3.2B kits from PAMSRC::DMQ$KITS:[DMQ32B.VMS.VAX]
and Installed to VAX/VMS V5.5-2 system.

Install was looks like successfully.

But DMQ$EXE:DMQ$CREATE_GROUP.COM was fail.
So, I executed DMQ$EXE:DMQ$CHECK_LICENSE.EXE standalone.
Then he said ........
----
Copyright � Digital Equipment Corporation 1997. All rights reserved.
%PLI-F-ERROR, PL/I ERROR condition.
-LICENSE-F-NOAUTH, DEC DMQ-DEV-V use is not authorized on this node
-LICENSE-F-INVALID_DATE, license is invalid for this product release date
-LICENSE-I-SYSMGR, please see your system manager
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           000047EF  000047EF
                                                           802F6112  802F6112
DMQ$CHECK_LICEN GO_CHECK                         1144      0000015D  00000931
DMQ$CHECK_LICEN DMQ$CHECK_LICENSE                1064      00000191  000007A9
----

Why?
Please give me some inoformation.

Regards,
Kaz.
2740.5Where did you get the PAK from?KLOVIA::MICHELSENBEA/DEC MessageQ EngineeringTue May 27 1997 10:486
  When I have seen this type of error it has always come from
a Digital internal PAK (i.e. off of VTX).  What you need to do
is to get a more recent PAK to replace the one you have.


Marty
2740.6OSOEIC::NARAMOTO_�ޥ��֡���äƤʤ��ͤ�Thu May 29 1997 20:293
Thank you Marty.

Exactly !