[Info-vax] Migrated VMS 5.X to simh - TCPWare error

[Hans Vlems]

On Feb 19, 11:01 am, "gregor.oelze" <gregor.oe... at gmail.com> wrote:
> On 19 Feb., 10:50, "gregor.oelze" <gregor.oe... at gmail.com> wrote:
>
>
>
>
>
> > On 18 Feb., 18:26, pe... at langstoeger.at (Peter 'EPLAN' LANGSTOEGER)
> > wrote:
>
> > > In article <c7e127e1-5c77-463a-837c-6a7a4989a... at n18g2000vbq.googlegroups.com>, Dave <Baxt... at tessco.com> writes:
>
> > > >On Feb 18, 11:47=A0am, pe... at langstoeger.at (Peter 'EPLAN' LANGSTOEGER)
> > > >> Don't think, that LANCP existed on VAX/VMS V5.1
>
> > > >You might be right.
>
> > > >I guess my next move would be to disable startup of DECNet and TCPWARE
> > > >in  SYSTARTUP_V5.com (??), reboot, and then run NETCONFIG.com
> > > >(including the running of the commands)    This should populate the
> > > >circuits and lines in ncp, with what OpenVMS actually sees.
>
> > > And my "next move" (after SHOW DEVICE and fixing SIMH and also the
> > > duplicate IP address) would be (if still neccessary) to @TCPWARE:CNFNET
> > > to fix TCPware and not touch DECnet at all (as the OP doesn't require it)
>
> > > --
> > > Peter "EPLAN" LANGSTÖGER
> > > Network and OpenVMS system specialist
> > > E-mail  Pe... at LANGSTOeGER.at
> > > A-1030 VIENNA  AUSTRIA              I'm not a pessimist, I'm a realist
>
> > I just re-ran the cnfnet script and the following message appeared:
>
> > Provide your distributor or Process Software Corporation with the
> > following information to obtain a software password for this system:
>
> >     o  Hardware ID: "2B-AA-BB-CC".
>
> >     o  System ID:   "01-0A".
>
> >     o  The product name and version number for the product(s)
> >        you are installing on this system.
>
> > Refer to your product documentation for more information on obtaining
> > a software password.
>
> > Enter new software password [NO CHANGE]:
>
> > I just pushed "enter" to "not change" anything - could it be, that
> > the
> > whole TCPWare problem is based on a licence problem?
>
> > Do I have to re-licence TCPWare because the hardware has changed?
>
> > best regards
>
> > Gregor Oelze
>
> Another issue might be a message that we recieve at startup of vms:
>
> %%%%%%%%%%%  OPCOM  19-FEB-2011 10:59:28.22  %%%%%%%%%%%
> Message from user SYSTEM
> %LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
> -LICENSE-F-EXCEEDED, attempted usage exceeds active license limits
> -LICENSE-I-SYSMGR, please see your system manager
>
> %LICENSE-E-NOAUTH, DEC VAX-VMS use is not authorized on this node
> -LICENSE-F-EXCEEDED, attempted usage exceeds active license limits
> -LICENSE-I-SYSMGR, please see your system manager
> Startup processing continuing...
>
> Is that also a problem?
>
> best regards
>
> Gregor Oelze- Hide quoted text -
>
> - Show quoted text -

Yes it is. Your old system probably ran with a VMS A license and, I'm
guessing, you're running the
microcode for a VAXserver 3900 on simh. VAXservers require a B
license. Two options:
IIRC trailingedge also has the VAX3900 code, or there is a hack for
the VAXserver microcode.
Once you've got that running, the system accepts a VMS A license.
And even then there may be a problem in your future: if the old system
required less license points than needed for a VAX3900.
Montagar offers hobbyist licenses and their VMS license loads on any
VAX, but I'm not sure you're operating a hobbyist system.
Hans