[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

3407.0. "BMS V1.2 SBS Failed During IVP" by MAIL::CLAYTON (Merlin Clayton DTN 445-7217) Wed Jul 22 1992 15:26

I just tried installing the BMS V1.2 SBS kit on my system (4000/300 VMS 5.5)
which superceeded the V1.2.7 EFT kit, and the installation failed during IVP.
The message is:

The following command failed.

      "MANAGE/ENTERPRISE TEST MCC 0 CIRCUIT_AM, TO FILE = MCCBMS$OUT.TXT"

   DECmcc BMS V1.2.0  Installation Failed
    

Could someone please give me some insight as to why this may have occured?

Will the other FMs and AMs work without the Circuit AM being successfully
installed, or is the whole installation corupted?

I need to get this resolved ASAP since I have a demo scheduled first thing
tomorrow morning.  Any help will be greatly appreciated.

Thanks.

Merlin

T.RTitleUserPersonal
Name
DateLines
3407.1Crash Dump With ICMPTRIGG::TRIGG::CLAYTONMerlin Clayton DTN 445-7217Wed Jul 22 1992 19:3237
RE: 0

When I tried to bring up the ICMP I got the following crash dump:


$ manage/enterprise/inter=decw
%LIB-W-STRLVL, illegal object language structure level in module
%TRACE-W-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           000528A2  000528A2
                                                           00052EFB  00052EFB
                                                           000523C6  000523C6
                                                           00052676  00052676
                                                           000C47FA  000C47FA
                                                           000C4747  000C4747
MCC_MAIN        main                             7693      00000230  000020DC
                                                           0000596F  0000596F
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE             163      00000027  000059A3
                                                           0000594A  0000594A
%LIB-W-STRLVL, illegal object language structure level in module v
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1FDEAA7E, PC
=000C45D4, PSL=03C000A0
%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           000C45D4  000C45D4
                                                           000C47C6  000C47C6
MCC_MAIN        main                             7693      00000230  000020DC
                                                           0000596F  0000596F
MCC_KERNEL_INIT MCC_KERNEL_INITIALIZE             163      00000027  000059A3
                                                           0000594A  0000594A

Any ideas?

Merlin

3407.2QAR 3304TOOK::MINTZErik Mintz, dtn 226-5033Wed Jul 22 1992 20:307
These two note are now QAR 3304.

It sounds like something has been corrupted on the system.
Did you previously have V1.1 installed on that system?
Any other AM packages installed?
Did you move any files after installing T1.2.7?

3407.3Both problems/solutions follow:TOOK::L_GROSSMANThu Jul 23 1992 15:5318
Both problems have been fixed:

1) The error during the IVP with "TEST MCC 0 CIRCUIT_AM" was caused by
an old parse table in mcc_specific ("mcc_specific:mcc_fdictionary.dat")

Solution: We renamed the file so MCC will not find it (it could have been
deleted) and reran the mcc startup "@sys$startup:mcc_startup_bms ENROLL"

2) The access violation/LIB-W-STRLVL in this case was produced by trying
to access a shared image that is not on the disk anymore.  This occurs
often in a cluster environment where not all nodes reran the DECmcc startup
file.  If this is NOT done, some nodes point to files that have been marked
for delete (because of purging files during an installation) and have somehow
been deleted.

Solution: To run the mcc startup file ON ALL NODES IN A VACLUSTER after
a successful installation.