[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

2143.0. "Problems with Enrollment." by KETJE::PACCO () Mon Jan 20 1992 12:54

An access mode can successfully be enrolled from the place where it was built,
but once copied to SYS$SHARE, it cannot be enrolled any more !

I am running DECmcc T.1.2.4
I do not remember to have seen this under DECmcc V1.1

Any hint ?
	Regards,
	Dominique.

### STEP 1 -- Environment check
Note , these 2 files are really the same files !
================================================
$
$ dir sys$share:mcc_gab_am/date

Directory SYS$COMMON:[SYSLIB]

MCC_GAB_AM.EXE;1     20-JAN-1992 18:40:12.34

Total of 1 file.
$ dir mcc_gab_am.exe/date

Directory DISK$SYSTEM_2:[MCC.GAB]

MCC_GAB_AM.EXE;1     20-JAN-1992 13:39:38.30

Total of 1 file.

### STEP 2 -- Successfull enrolment
===================================
$ def mcc_gab_am disk$system_2:[mcc.gab]mcc_gab_am.exe
$ manage/enter
DECmcc (T1.2.4)

MCC> enroll mcc_gab_am
%MCC-I-ENRDUPLENTRY, enrollment successful; duplicate entries found and replaced
MCC>  Exit

### STEP 3 -- Unsuccessfull enrolment
=====================================
$ deass mcc_gab_am
$ show log mcc_gab_am
%SHOW-S-NOTRAN, no translation for logical name MCC_GAB_AM
$ manage/enter
DECmcc (T1.2.4)

MCC> enroll mcc_gab_am
%MCC-E-ENRFILREADERR, enrollment failed: management module file read error
MCC>  Exit
$
    
    
T.RTitleUserPersonal
Name
DateLines
2143.1DIR/OWN/PROT/DATTOOK::ORENSTEINMon Jan 20 1992 14:176
    
    Can I suggest
    
    DIRECTORY/OWNER/PROTECTION/DATE
    
    	aud...
2143.2No protection problem !KETJE::PACCOTue Jan 21 1992 17:3527
    
    This should not be a protection problem, including
    SYSPRV,BYPASS,CMKRNL...
    I always can send you a saveset which shoud (will not?) install
    properly if you wish.
    
    FYI. These are the protections:
    
    Dominique.
    
$ dir sys$share:mcc_gab_am.exe/date=all/prot/owner

Directory SYS$COMMON:[SYSLIB]

MCC_GAB_AM.EXE;1     20-JAN-1992 18:40:12.34  20-JAN-1992 18:40:13.17  20-JAN-19
92 18:40:13.18   <No backup recorded>  [SYSTEM]              (RWED,RWED,RE,RE)

Total of 1 file.
$ set def [.gab]
$ dir mcc_gab_am.exe/date=all/prot/owner

Directory DISK$SYSTEM_2:[MCC.GAB]

MCC_GAB_AM.EXE;1     20-JAN-1992 13:39:38.30  20-JAN-1992 13:39:39.50  20-JAN-19
92 19:42:15.63   <No backup recorded>  [MCC]                 (RWED,RWED,RE,)
   
    
2143.3TOOK::ORENSTEINWed Jan 22 1992 11:338
    
    One last thing to try:
    
    $ INSTALL LIST SYS$LIBRARY:MCC_GAB_AM.EXE
    
    What are the results?
    
    		aud...
2143.4A stupid error !KETJE::PACCOThu Jan 23 1992 14:5540
    Aud,
    
    Finally I found the error.
    The problem has to be found elsewhere.
    The following is somehow a shortcut of the story.
    
    The thing I discovered now was a "good" and "bad" file in the play.
    
    When a "good" file was installed in sys$share, it works.
    When a "bad" file was installed in sys$share, it does not work.
    
    When a "bad" file is installed, but MCC_GAB_AM points to a "good" file
    on another directory, it works.
    
    When a "bad" file is installed, and afterwards a "good" file is copied
    to sys$share, it still does not work (I should have understood this
    earlier!)
    
    When MCC_GAB_AM.EXE was not installed, depending on "good" or "bad", it
    works or not.
    
    I did not knew however WHY a file was "good" or "bad".
    In fact I used two different link commands (one for developement, the
    other for VMSINSTAL)
    
    $ LINK MCC_GAB_AM.OPT/OPT /SHAR=MCC_GAB_AM.EXE/DEB
    $ LINK/NOTRACE/NOMAP MCC_GAB_AM.OPT/opt
    
    The first one works, the second one did not work.
    Finally I found that MCC_GAB_AM was not build as a SHARABLE IMAGE !!!
    
    Thanks Aud for your patient: although your suggestion to list how the
    file was installed had nothing to do with the problem, in trying a lot
    of combinations around that this I was lucky to find out that in case of a
    "good" file on sys$share, without a "bad" be installed showed me that
    only a wrong "link" command was the bad player.
    
    	Note: Do not try to install the file I sent !
    
    Dominique.
2143.5Good Job!!!TOOK::ORENSTEINThu Jan 23 1992 17:117
    
    I am glad that you found the problem.  I have not tried to
    install your kit.  I can delete it for you if you tell me
    where you put it.
    
    		aud...