| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3406.1 | what version? | BARREL::LEMMON | | Wed Jul 29 1992 12:33 | 4 |
| Are you running a field test version of VMS 5.5? Also,
are you running WAVE2.
/Jim
|
| 3406.2 | | MUCTEC::APPS | I'd rather be sailing... | Thu Jul 30 1992 06:52 | 59 |
| <<< Note 3406.1 by BARREL::LEMMON >>>
-< what version? >-
Since I am experiencing the same problem as .0, I thought I would include
details on the version of VMS we are running on our VAXCluster.
>> Are you running a field test version of VMS 5.5? Also,
>> are you running WAVE2.
------
VMS
VAX/VMS T5.5-1E7 on node MUCXEE 30-JUL-1992 08:50:54.65 Uptime 21 00:36:21
------
Since I am not sure how one ascertains whether the system is running WAVE2,
I am including the output from "NCP SHO EXE CHAR".
------
DECnet
Node Volatile Characteristics as of 30-JUL-1992 08:52:18
Executor node = 49.355 (MUCXEE)
Identification = DECnet-VAX V5.5, VMS T5.5-1E7
Management version = V4.0.0
Incoming timer = 45
Outgoing timer = 60
Incoming Proxy = Enabled
Outgoing Proxy = Enabled
NSP version = V4.1.0
Maximum links = 200
Delay factor = 80
Delay weight = 5
Inactivity timer = 120
Retransmit factor = 10
Routing version = V2.0.0
Type = routing IV
Routing timer = 600
Broadcast routing timer = 180
Maximum address = 1023
Maximum circuits = 16
Maximum cost = 1022
Maximum hops = 30
Maximum visits = 63
Maximum area = 63
Max broadcast nonrouters = 64
Max broadcast routers = 32
Maximum path splits = 1
Area maximum cost = 1022
Area maximum hops = 30
Maximum buffers = 100
Buffer size = 576
Nonprivileged user id = DECNET
Default access = incoming and outgoing
Pipeline quota = 32000
Alias incoming = Enabled
Alias maximum links = 32
Alias node = 49.226 (MUCTEC)
Path split policy = Normal
Maximum Declared Objects = 400
DNS interface = Enabled
IDP of ISO address = 49
DNS namespace = DEC
|
| 3406.3 | Same rev of VMS FT! | EPAVAX::CARLOTTI | Rick Carlotti, DTN 440-2194, Sales Support | Thu Jul 30 1992 12:55 | 7 |
| Very interesting...
I am running VMS v5.5-1E7 also!
What is WAVE2?
Rick C
|
| 3406.4 | | POLE::LEMMON | | Thu Aug 06 1992 22:13 | 8 |
| Risking sounding like an idiot, WAVE 2 has something to to do with Phase V decnet.
Hopefully someone out there has a better description of the Phase V
WAVEn releases.
There was a problem in the v5.5-E7 vms kit that caused this error to occur. I
was told it was fixed in a later release.
/jim
|
| 3406.5 | Thank you! | MUCTEC::APPS | I'd rather be sailing... | Fri Aug 07 1992 08:02 | 0 |
| 3406.6 | | TOOK::PURRETTA | | Fri Aug 07 1992 13:54 | 8 |
| I also saw this problem while running VMS v5.5-1E7.
I'm running an AMBER release of VMS now (VAX/VMS T5.5-2E3)
and the problem went away.
WaveII is the VMS DECnet/OSI implementation. You can run vms 5.5
without running DECnet/OSI, i.e. you could be running DECnet phaseIV.
I believe the problem mentioned in .0 has to do with VMS and is
independent of which version of DECnet is running.
|
| 3406.7 | Making progress, but still no MCC windows! | EPAVAX::CARLOTTI | Rick Carlotti, DTN 440-2194, Sales Support | Mon Aug 10 1992 17:22 | 14 |
| Okay... I've installed VMS v5.5-2E7 and I get the following error:
$ mcc
%DCL-W-ACTIMAGE, error activating image CMA$RTL
-CLI-E-IMGNAME, image file TSMCC$DKA0:[SYS0.SYSCOMMON.][SYSLIB]CMA$RTL.EXE;4
-SYSTEM-F-NOTINSTALL, writable shareable images must be installed
Should I add an install statement somewhere in my startup files? If so, what
switches should be used?
Thanks in advance,
Rick C
|
| 3406.8 | Reinstalled MCC AFTER VMS upgrade! | EPAVAX::CARLOTTI | Rick Carlotti, DTN 440-2194, Sales Support | Wed Aug 19 1992 02:48 | 7 |
| Problem solved...
I reinstalled DECmcc BMS v1.2 AFTER installing VMS v5.5-2e7 and everything
worked fine. I noticed that the DECmcc installation patches the image
VAXCRTL.EXE (maybe that's what fixed the problem?).
Rick C
|
| 3406.9 | Glad to hear it worked | TOOK::MINTZ | Erik Mintz, dtn 226-5033 | Wed Aug 19 1992 12:01 | 8 |
| Yes, re-installing DECmcc will fix the problem.
No, it is not related to the VAXCRTL. The problem is that the
VMS installation installs an older, (in this case broken) version of CMA.
The DECmcc installation installs a more current version.
-- Erik
|