T.R | Title | User | Personal Name | Date | Lines |
---|
2471.1 | That doesn't sound very good | TOOK::GUERTIN | Don't fight fire with flames | Tue Mar 03 1992 09:33 | 7 |
| Do you have anything else on the VMS V5.5 system (like WAVE I / WAVE II
decnet) ? Are you using the real DNS or the Local MIR option?
We may need to analyze a dump file. So all I would recommend right now
is for you to save one.
-Matt.
|
2471.2 | DNS | COOKIE::KITTELL | Richard - Enterprise Storage Mgmt | Tue Mar 03 1992 10:37 | 9 |
|
I'll bet a bag of ILV that it is DNS. It seems that the version of DNS that
ships with VMS 5.5 does not include the patch for a bug that only DECmcc
Register seems to exercise.
We had the same problem on our systems after the V5.5 upgrade. Although
MCC_MAIN is the active image, you will find that the PC is in one of the DNS
shared images.
|
2471.3 | Gimme, gimme | CRONIC::LEMONS | And we thank you for your support. | Tue Mar 03 1992 10:50 | 3 |
| Right you are, I'm using DNS, not the MIR. So speak to me about this DNS patch.
tl
|
2471.4 | DNS Patch | COOKIE::KITTELL | Richard - Enterprise Storage Mgmt | Tue Mar 03 1992 11:11 | 27 |
| If your V5.5 system crashes accessing DNS from DECmcc, and the crash dump
indicates MCC_MAIN is the active image, and the PC at the time of crash is
in DNS$SHARE, this patch may help. Note that I have no authority to recommend
this, I can only say as a consumer of VMS, DNS and DECmcc that it worked for
the COOKIE cluster. To do the right thing, contact your support organization
or those responsible for DNS. I hear this patch came from the DNS conference.
There was no text with the patch...
$ set default sys$common:[syslib]
$ patch DNS$SHARE
SE M
I
H
EXI
RE
^X00001392
'MOVZWL B^^X00000008(R2),R1'
EXIT
'BEQL ^X000013A2'
'MOVZWL B^^X00000008(R2),R1'
EXI
U
EXI
$ exit
|
2471.5 | Check dates on DNS*.EXE | TRM::KWAK | | Tue Mar 03 1992 11:25 | 22 |
|
RE: .0
Also make sure that you have the correct dns$*.exe on your system.
Please check the dates on the following files:
Directory SYS$COMMON:[SYSLIB]
DNS$CLIENT.EXE;2 34 23-OCT-1991 17:32:30.00
DNS$SHARE.EXE;3 4 21-OCT-1991 16:06:51.00
Directory SYS$COMMON:[SYSEXE]
DNS$ADVER.EXE;2 282 27-NOV-1991 17:08:15.00
DNS$SOLICIT.EXE;2 11 9-JUN-1988 15:15:14.84
I think that the DNS V1.1 DNS*.EXE do not work on VMS 5.5.
When you install DNS V1.1 on your system, make sure that the DNS*.EXEs
in the VMS 5.5 do not get replaced/removed.
|
2471.6 | Fixed! | CRONIC::LEMONS | And we thank you for your support. | Tue Mar 03 1992 12:16 | 31 |
| I installed the patch in .4 and rebooted. It fixed it, in that performing a
REGISTER NODE4 no longer crashes the system.
Re .-1, I do not have DNS installed on my system, per se. I haven't installed
any DNS kit; rather, the DNS images on my system have been supplied with VMS and
layered products.
Here is a directory listing of the four files mentioned in .-1:
$ dir/date=create/size=all SYS$COMMON:[SYSLIB]DNS$CLIENT.EXE,DNS$SHARE.EXE,SYS$C
OMMON:[SYSEXE]DNS$ADVER.EXE,DNS$SOLICIT.EXE
Directory SYS$COMMON:[SYSLIB]
DNS$CLIENT.EXE;1 93/93 17-OCT-1991 13:39:53.27
DNS$SHARE.EXE;2 67/69 3-MAR-1992 11:30:26.03
DNS$SHARE.EXE;1 65/66 17-OCT-1991 13:39:51.64
Total of 3 files, 225/228 blocks.
Directory SYS$COMMON:[SYSEXE]
DNS$ADVER.EXE;1 109/111 17-OCT-1991 13:40:12.98
DNS$SOLICIT.EXE;1 36/36 17-OCT-1991 13:40:14.40
Total of 2 files, 145/147 blocks.
Grand total of 2 directories, 5 files, 370/375 blocks.
Thanks for the fast help!
tl
|