[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

3332.0. "V1.2: IVP FAILED" by ANNECY::GONDINET (H�l�ne - EIC/T&N Annecy, France) Thu Jul 09 1992 06:57

    I have installed MCC BMS V1.2 on my system.
    All worked fine until end of IVP where I have the following message:
    
    The following command failed.
    
    "MANAGE/ENTERPRISE TEST MCC 0 CIRCUIT_AM, TO FILE = MCCBMS$OUT.TXT"
    
    When I issue that command  I have the following message:
    
    %MCC-E-NOTFOUND, unsupported combination of verb, entity, partition
    
    I have issued this command for other AM and all has worked perfectly.
    
    Any idea on this problem ?
    Thanks in advance,
    H�l�ne
T.RTitleUserPersonal
Name		DateLines
3332.1Same with meFRAIS::64917::SYSTEMInformation, that's all I need...Fri Jul 10 1992 08:0116
Hi,

I've got the same problem. My machine is a VAXstation 3100/48 SPX, VMS 5.5,
previous version of MCC was T1.2.4, additional modules were ELM EFT and TCP/IP
DA EFT.

My problem start with the FCL PM (TEST MCC 0 FCL) and continues with nearly 
every module. Parse table rebuild didn't help and created errors 
(log available).


Help!



Josch
3332.2Files in specific/ rebuild dispatch tables:TOOK::L_GROSSMANFri Jul 10 1992 09:1419
    
    First please make sure there are no MCC files in specific directories.
    do this by entering:
    
    $dir sys$specific:[sysexe]mcc*.*
    
    and
    
    $dir sys$specific:[syslib]mcc*.*
    
    If there are, delete them.  Even if there are no files in specific
    enter:
    
    $@sys$startup:mcc_startup_bms ENROLL
    
    Make sure to specify the "ENROLL" parameter for this case only. This
    causes the dispatch tables to be rebuilt.
    
    Then try the test command again.
3332.3Still the sameANNECY::GONDINETH�l�ne - EIC/T&N Annecy, FranceMon Jul 13 1992 10:2217
There is no MCC files in sys$specific:[sysexe] and sys$specific:[syslib].

I run the ENROLL procedure as you specified, and it works fine, 
without error messages.
I then run the IVP again, AND I still have the same message.

Did I miss something else ?

Thank in advance,
H�l�ne.


PS:
I have checked the system parameters and quotas against the values in 
the release notes.
Is there an updated version of MCC_AUDIT.COM for the release version 
of MCC1.2 ?
3332.4Parse tables have been found in mcc_specificTOOK::L_GROSSMANTue Jul 14 1992 10:5510
Reply to 3332.0

A copy of the dictionary parsetables have been found in mcc_specific.

MCC installation like MOST ALL VMS installation place images in the
system common directories. If there are files in the specific (mcc_specific
in this case) those will be read first when running the product.

This was caused from an old installation of the DECmcc TSAM product.
3332.5a bit later than the previous problem but another IVP failure...TOMLIN::ROMBERGI feel a vacation coming on...Fri Sep 04 1992 12:4645
I just installed MCC V1.2 (over T1.2.7) on a VAX running VAX/VMS V5.5-2S7.

Everything seemed to be fine until the IVP ran...


The MCC_STARTUP_BMS startup procedure for DECmcc V1.2.0 is now running.

%SYSTEM-F-ACCVIO, access violation, reason mask=05, virtual address=04835717, PC
=802DE275, PSL=03C00000

  Improperly handled condition, image exit forced.

        Signal arguments              Stack contents

        Number = 00000005                802DE22E
        Name   = 0000000C                802DE142
                 00000005                00000000
                 04835717                203C0000
                 802DE275                7FED9FFC
                 03C00000                7FED9FE8
                                         7FF6B777
                                         0000000F
                                         7FF6B489
                                         00000000

        Register dump

        R0 = 04835717  R1 = 0004EE00  R2 = 00000105  R3 = 00006800
        R4 = 0000AD7C  R5 = 00009E00  R6 = 00000000  R7 = 7FF28CB8
        R8 = 7FFECA4C  R9 = 7FFECC54  R10= 7FFED7D4  R11= 7FFE2BDC
        AP = 7FED9F7C  FP = 7FED9F3C  SP = 7FED9FB8  PC = 802DE275
        PSL= 03C00000

%DCL-W-SKPDAT, image data (records not beginning with "$") ignored


The MCC_STARTUP_BMS startup procedure for DECmcc V1.2.0 is now ending.




Any thoughts on where to look?  FWIW, the toolkit IVP ran correctly, but 
man/tool/dict also fails (same accvio)

Kathy
3332.6QAR 3412TOOK::MINTZLKG2-2 near pole X3, cube 6072, dtn 226-5033Fri Sep 04 1992 12:525
Entered as QAR 3412.

Did T1.2.7 work without problems on this same version of VMS?

-- Erik
3332.7blind patching of a more recent rtl than expected?TOMLIN::ROMBERGI feel a vacation coming on...Fri Sep 04 1992 15:306
Well, I'll answer my own question....The problem was with the vaxcrtl.  We had a 
later (more recent) version, which the MCC BMS install seems to have blindly 
patched, without carefully checking image idents, resulting in a buggered vaxcrtl. :^(


kathy
3332.8TOMLIN::ROMBERGI feel a vacation coming on...Fri Sep 04 1992 15:3210
>
>Did T1.2.7 work without problems on this same version of VMS?
>

T1.2.7 went on so long ago that I don't remember which version of VMS was 
running at the time.  This is the first problem we've had with installing
MCC (other than trying to find space for the kit...)


kmr