|
Hi,
Yes I have the license VAXSET loaded for DECSET12.1! I don't think
that the SAVESET for Ultrix would go through the whole install if it
wasn't written for VMSINSTAL. So I think I'm safe with the right
savesets (DECSET12.1).
1. I've since modified the license from REGISTER to ENABLE as follows
-------------------------------------------------------------------
2. See number 3. Below it's the install log that fails..
License Database File: SYS$COMMON:[SYSEXE]LMF$LICENSE.LDB;1
Created on: 10-DEC-1991
Created by user: SYSTEM
LMF Version: V1.0
-----------------------------------
Issuer: DIGITAL-IM&T
Authorization: BIX-PK-97028-1-LJO-WOOF-1453
Product Name: VAXSET
Producer: DEC
Units: 0
Version: 0.0
Release Date: 28-JAN-1998
PAK Termination Date: (none)
Availability: 0
Activity: 000000100
Options: MOD_UNITS
Product Token: *FOR_DIGITAL_INTERNAL_USE_ONLY*
Hardware ID:
Revision Level: 2
Status: Active
Command: ENABLE
Modified by user: SYSTEM
Modified on: 30-JAN-1997 09:37:53.77
---------------------------------------------------------------------
3. INstall log...............................................
%LICENSE-F-NOAUTH, DEC LSE 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
80442F12
80442F12
000010E0
000010E0
00001066
00001066
0008CFD0
0008CFD0
00073CE9
00073CE9
00001191
00001191
LSE$LSEDIT MAIN 622 000000E8
00000508
%DECSET-I-START_MMS, MMS installation in progress
%VMSINSTAL-I-RESTORE, Restoring product save set F ...
%DECSET-I-LINKIMAGE, Linking V3.1-03.
%VMSINSTAL-I-SYSDIR, This product creates system directory
[SYSHLP.EXAMPLES.MMS]
.
%CREATE-I-EXISTS, VMI$COMMON:[SYSHLP.EXAMPLES.MMS] already exists
***************************************************************
* *
* If this installation is performed on a cluster, you must *
* execute *
* *
* *
* $ @SYS$STARTUP:MMS$STARTUP.COM *
* *
* on all other nodes in the cluster. In addition, you must *
* add the above line to your system startup procedure. *
* *
***************************************************************
%DECSET-I-DONEMMS, The installation of MMS completed
%VMSINSTAL-I-MOVEFILES, Files will now be moved to their target
directories...
********************************************************************************
The DECset V12.1 collective installation will now run the
Installation
Verification Procedure for the each of the component you selected
to
run the IVP.
********************************************************************************
+-----------------------------------------------------------+
| Installation verification command procedure for |
| DECset Environment Manager |
+-----------------------------------------------------------+
Starting IVP for DECset Environment Manager
IVP for DECset Environment Manager completed successfully
%LICENSE-F-NOAUTH, DEC CMS 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
%CMS-E-IVPFAILURE, CMS IVP failed
%CMS-I-IVPEND, End Installation Verification Procedure
%NONAME-E-NOMSG, Message number 00000002
%VMSINSTAL-E-IVPFAIL, The IVP for DECSET V12.1 has failed.
VMSINSTAL procedure done at 10:21
|
| Hi Jim,
Guess what, I've tailored on DECWINDOWS and the install of DECSET12.1
is finished perfect!!
That was it...
p.s. Note that one down! It was the cure for me! It must have a
dependency from the Windows License? Maybe, I don't know it's depent
on some DECWindows file! Still I'm sure I told it no on interfaces
questions.
Thanks again.. Ralph
|