[Info-vax] Migrated VMS 5.X to simh - TCPWare error
Peter 'EPLAN' LANGSTOEGER
peter at langstoeger.at
Fri Feb 18 11:27:04 EST 2011
In article <81215295-c7ce-4399-b458-acd668e7fff7 at g11g2000vbq.googlegroups.com>, "gregor.oelze" <gregor.oelze at gmail.com> writes:
>After searching through the file-system, i couldnt find a local location, called TCPWARE,
>what i did find- was SYS$SYSROOT[TCPIP]TCPIP_CONFIGURE.COM in which the
>old NIC was defined with SVA-0.
Ok. On my TCPware systems, the file is TCPWARE:TCPWARE_CONFIGURE.COM
(where TCPWARE translates - besides others - to SYS$SYSROOT:[TCPWARE])
In very old TCPWARE versions (like yours), it was [TCPIP] but I can't
remember when this changed (to avoid confusions with DEC's UCX product).
So, sorry for not providing the correct hint.
>After a long fight with the vms editor and the Gold-Key i managed tochange the
>NIC name to QNA-0. So - shutdown - restart of the machine-that is now the output.
>
>%STARTNET-F-ERROR, error during execution (NETCU START/IP QNA-0 192.9.201.130
>/FLAGS=NOTRAILERS)
>
>-STARTNET-I-SHUTNET, shutting down TCPware ...
Sorry for not guessing the correct hint.
>I am still confused. Will it be the problem with the SYS$DEVICE?
Don't think so (and it is SYS$SYSDEVICE)
--
Peter "EPLAN" LANGSTÖGER
Network and OpenVMS system specialist
E-mail Peter at LANGSTOeGER.at
A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist
More information about the Info-vax
mailing list