Conference azur::mcc

Yes, this sounds like a QARable problem.

Does the system on which you are running have Motif installed?

My guess is that you have DECwindows not Motif, especially if the Iconic Map
V1.2 runs (it is built on DECwindows, not Motif).

Verna

    Of course I've installed Motif V1.1. So, the window is Motif, but the 
    contents (MCC Iconic Map) is DECwindow in case of using the UID file of MCC 
    V1.2
    
    Uwe

Sorry about the basic question, but some people have made that mistake,
so we had to ask.

Something very strange is going on with your system.

Could you please post a full directory (DIR/FULL) listing for the iconic map
image and UID files that you are using?

BTW, why are you using a V1.2 UID file?  Where did it come from?

-- Erik

    
    Here is the MCC T1.3 UID file info
    
    Directory DISK$DATA:[MCC]
    
    MCC_ICONIC_MAP_PM.UID;1               File ID:  (1341,13,0)
    Size:          912/915        Owner:    [SYSTEM]
    Created:   1-DEC-1992 23:27:42.98
    Revised:  10-DEC-1992 09:29:50.36 (10)
    Expires:   <None specified>
    Backup:    <No backup recorded>
    File organization:  Sequential
    File attributes:    Allocation: 915, Extend: 16, Global buffer count: 0
                        No version limit
    Record format:      Fixed length 4096 byte records
    Record attributes:  Carriage return carriage control
    RMS attributes:     None
    Journaling enabled: None
    File protection:    System:RWED, Owner:RWED, Group:RWED, World:RE
    Access Cntrl List:  None
    
    When I use this file the error message occurs.
    Therefore I've restored the UID file from my MCC V1.2 backup.
    Now I'm using MCC T1.3 but the Iconic Map that appears if from MCC
    V1.2.
    But there are two additional UID files
    
    MCC_EM_TABLE.UID;1
    MCC_LAN_TOPOLOGY_PM.UID;1
    
    Even if I rename the to files to antoher file name and use the T1.3 UID
    file the error occurs.
    
    Uwe
    

OK, that looks like the correct UID file.
Now lets look at the map executable.  Try

DIR/DAT=ALL SYS$SHARE:MCC_ICONIC_MAP_PM.EXE;*


Also, could you try ANA/IMAGE SYS$SHARE:MCC_ICONIC_MAP_PM.EXE
and post the 4 lines following the "Image Identification Information"
heading.

    Probblem solved,
    
    it was the SYS$SHARE:MCC_ICONIC_MAP_PM.EXE !!!!
    So, be careful installing any other DECmcc Mgmt Modules.
    I will have look at all the kits I've installed, because one of them
    (or more) replace the SYS$SHARE:MCC_ICONIC_MAP_PM.EXE.
    
    
    Thanks Uwe

Please let us know as soon as possible which kit is causing the problem.
We need to get it fixed right away.

Thanks,

-- Erik

    In my case, we had been playing games to reduce the size of the
    directory SYS$COMMON:[SYSLIB] by renaming V1.2.3 DECmcc files to 
    SYS$SPECIFIC:[SYSLIB] .  This gives DECmcc startup a performance
    boost if you have many products installed and your directory size
    is over 1000 blocks (ours was almost 2000).
        (BTW, don't try this unless you know what you are doing.)
    
    The bottom line is that the installation of T1.3 did not check the 
    SYS$SPECIFIC:[SYSLIB] directory and, as a result, I had a wrong
    version of the *PM*.EXE file mentioned in .7 .
    
    Once deleted, everything was fine.
    
    -Dan

Sorry, I haven't caught on yet. I seem to have the same problem as .0 but I'm
not sure what's up. I do not have the map exe in SYS$SPECIFIC:[SYSLIB] and the
ANALYZE commands for both the SYS$SHARE and SYS$COMMON:[SYSLIB] versions show
the following:

        Image Identification Information

                image name: "MCC_ICONIC_MAP_PM"
                image file identification: "DECMCC T1.3-0"
                link date/time:  1-DEC-1992 23:20:07.55
                linker identification: "05-05"

Do I need to delete something? What's the secret ingredient?

thanks,
brad...

My guess is that Motif is not installed on your system.  The Motif
based Iconic Map included with T1.3 requires that the motif kit be
installed on the system. There is a reply to note 4 describing this
problem.

-- Erik

> My guess is that Motif is not installed on your system.  The Motif
> based Iconic Map included with T1.3 requires that the motif kit be
> installed on the system. There is a reply to note 4 describing this
> problem.

Motif 1.1 was installed. The system was then rebooted. The motif style windows
were then apparent. At this point MCC V1.2 BMS, ELM and TSAM are still 
installed.

V1.3 was then installed, no errors. I manually ran the startup with ENROLL,
no errors. I manually ran the IVP, no errors. Bring up the map using the same
OLD command (this didn't change did it? /inter=decw). We are still running
V5.4-3.

any ideas??
brad...

Did you de-install all V1.2 DECmcc stuff (ELM, TSAM).

It would help to be at a point where you have the DECwindows Motif V1.1
installed and the only DECmcc kit installed is T1.3.0.

Is that where you are at, and if so, exactly what output are you seeing?

Verna

>Did you de-install all V1.2 DECmcc stuff (ELM, TSAM).

>It would help to be at a point where you have the DECwindows Motif V1.1
>installed and the only DECmcc kit installed is T1.3.0.

>Is that where you are at, and if so, exactly what output are you seeing?

Hi Verna,

No, ELM and TSAM files were (and are) present. How does one de-install other
kits?? Delete all files in MCC_COMMAN and SYS$COMMON:[SYSLIB]*mcc*??? Should
I do this then re-install?? Could this actually be a MOTIF problem instead??

the error was:

NOCMAN>mana/enter/inter=decw
X Toolkit Warning: DRM: I18NOpenFile: Couldn't open file mcc_uil:mcc_iconic_map_
pm.uid - UID file version mismatch - DRMNotValid
X Toolkit Warning: Drm__OpenHierarchy: @2 - DRMNotValid

 Software error: unable to open hierarchy - check logical MCC_UIL.
%MCC-F-PM_OPENHIERERR, Software error: unable to open hierarchy - check logical
MCC_UIL.

NOCMAN>show log mcc_uil
   "MCC_UIL" = "MCC_COMMON" (LNM$SYSTEM_TABLE)
1  "MCC_COMMON" = "SYS$COMMON:[MCC]" (LNM$SYSTEM_TABLE)

NOCMAN>dir mcc_uil:*.uid/prot/date

Directory SYS$COMMON:[MCC]

MCC_EM_TABLE.UID;6   27-JUN-1992 02:32:10.08  (RWED,RWED,RWED,RE)
MCC_ICONIC_MAP_PM.UID;14
                      1-DEC-1992 23:27:42.98  (RWED,RWED,RWED,RE)


thanks,
brad...

I have started fresh by deleting MCC_COMMON files and SYS$COMMON:[SYSLIB]*mcc*.*
I re-installed, re-enrolled, and re-ivp'd. There have been no errors with any of
these but I still get the UID mismatch error.

any ideas?
brad...

Well if it isn't a MOTIF problem, and it's not an MCC problem, it has just
GOT TO BE THE USER!!! I hadn't used this system since V1.2 F/T and I had a
logical in login.com and *special* .exe in sys$login which I had forgotten
about over several months of non-use.

Onward,
brad...

I also ran into problems when I installed T1.3 on a system that was
running V1.1.  The problems disappeared after I meticulously deleted
all files in the entire system disk's directory structure that appeared
to have anything to do with MCC.  This was a very time-consuming and
potentially dangerous exercise.  Could you please provide something
like a de-install procudure for old VMS versions of MCC?

	- Andy

    Hello,
    
    re .7
    
    as I mentioned one of the additional DECmcc kits replace the
    MCC_ICONIC_MAP_PM.EXE.
    The kit which will replace this file is the DECmcc SNA kit
    (MCCSNA010.B).
    This SW copy a new MCC_ICONIC_MAP_PM.EXE into SYS$COMMON:[SYSLIB]
    with the file ident
            image name: "MCC_ICONIC_MAP_PM"
            image file identification: "DECMCC V1.2-2"
            link date/time: 10-SEP-1992 18:23:44.37
            linker identification: "05-05"
    
    So be carefull to install or reinstall this kit. The best way to
    reinstall the SNA kit on DECmcc T1.3 is onlz to update the Dictionary
    and Parse table.
    
    Best regards Uwe

    
    Hello,
    
    The MCC_ICONIC_MAP_PM.EXE will only be installed by the SNA kit if the
    link date of the above image is newer than the one currently on the
    system.  Therefore, the SNA kit will *NOT* replace the V1.2-3 or later
    images.
    
    ~Jon. (developer of the SNA kitinstal)

So the conclusion is that if you see this problem, you have an
obsolete SNA kit.  Please make sure that you get a current SNA
kit before installing on T1.3

-- Erik