[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

13.0. "Instalation questions" by DSTEG2::HOSSFELD (I'm so confused!) Fri Sep 22 1989 09:35

    o	When I installed the tool kit the IVP failed but the instalation
	completed "successfully." I looked for the reason of the IVP failure
	and found that there was an MCC$SYSTEM logical in my process table 
	that pointed to a development dir I had.  

	Shouldn't this be check for before the IVP is run?

    o	The instalation guide has a list of new files and new logicals. 
	The following logicals appear after the instalation but aren't 
	listed there;
		MCC$ENET_DEVICE
		MCC$TDF
		MCC$KIT

	The AM programing guide section 3.2 is also lacking the same logical
	definations.	

    o	The instalation guide doesn't indicate that the mcc$startup.com
	file is loaded in sysman instead of systartup_v5.com and this could 
	be confusing to people who arn't familiar with the sysman setup. 

	It should be stated that the startup is in SYSMAN.

    o	When I tried th build the sample am I found the following problems;

	MCC$INCLUDE logical is not defined so the files wouldn't compile.
	The manual didn't state what its defination should be.  Shouldn't
	this be defines by the install?

	When the SAMPLE_AM_VALIDATE.C module tried to compile it couldn't
	include strdef.h.  I have not yet found that file and have looked 
	on a VMS 5.1 and 5.2 system. 

	Paul H.
T.RTitleUserPersonal
Name		DateLines
13.1Observations and comments on installationHAMRAD::DONADTFri Sep 22 1989 11:1327
    Here are my comments regarding installing the exec and toolkit:
    
    1. There is no 'Read Me First' Manual. With about 10 documents,
    this type of a guide would be helpful.
    
    2. Quotas - Both Installation Guides show a FILLM of 40 and a DIOLM
    of 18. The Release notes ask you to set these parameters at 50 and 24
    respectively. Paul Hossfeld used the lower values and I used the higher
    values. We both successfully installed the products.
    
    3. Order of Installation - There is no mention in the installation
    guides of which product should be installed first but it does make a
    difference. Tools requires a file brought in by the EXEC -
    MCC$TOOLS.CLD. Paul H. installed the EXEC first and I tried TOOLS
    first to see what would happen. Paul installed successfully and I
    did not - got a BADSPEC error message on MCC$TOOLS.CLD. (This file
    is part of the EXEC.)
    
    4. Privileges - Installation Manuals call for System Manager Privileges
    and Release Notes say no privileges needed. Paul installed with all
    privileges and I tried it without privileges. We both installed without
    problems. The only problem here with what the Release Notes say is that
    they also recommend you use the System Managers account. This account
    usually is set up with full privileges.
    
    Ray
13.2INFO has been passed onGOSTE::CALLANDERMon Sep 25 1989 12:216
    
    The information in the previous notes have been passed on to the
    "Installation Guide" writer and the person responsible for writing
    the installation procedures.
    
    Thanks for the comments.
13.3more on documentationDSTEG2::HOSSFELDI'm so confused!Wed Sep 27 1989 13:0612
The release notes (page 1-11) states that mcc$system pointes to ta dir contain- 
ing 5 files. One of them doesn't exist - MCC$MIR_INSTANCE.DAT.

The same section doesn't indicate that MCC$PTB_PARSER.DAT is also there.

In the Am programing guide page 4-7 
	[DYNAMIC = TREUE|FALSE] is missing the comma
	[DYNAMIC = TREUE|FALSE ,]
		
Page 6-7
	attribute_partition defination of allowable terms should also include 
		IDENTIFIER
13.4Installation on non-system disk?NSSG::R_SPENCEFri Apr 13 1990 14:0922
    Question on installation of MCC$UT010
    
    I don't see a supported way to install the product on a disk other than
    the system disk. Please make this possible.
    
    More and more we are finding that system disks cannot support more
    products and the best solution is to install major products like MCC
    on an application disk that can be dedicated to just a few products.
    
    Also, since the disk space requirements for MCC will grow over time due
    to history/configuration files and also new modules that become
    available, it is difficult to reserve adaquate space on a system disk.
    
    Products like MCC can easily become somewhat disk I/O intensive and
    performance will suffer if the product must compete with the system
    for I/Os.
    
    For myself, I have a workstation with 2 disks. Just VMS and a very few
    layered products leaves me only a bit over 40k blocks left. I have lots
    of space on the second disk.
    
    s/rob
13.5What needs to be done??MERCRY::SALOISFri Dec 07 1990 11:0512
    
    -.4
    .... installation on a non-system disk"
    
    Is this now possible?  I also am running out of room on the system disk
    and have loads of room on another.  Is there just one logical to change
    or would this be major reconstruction?
    
    Thanks,
    
    Gene
13.6Sure you can!TOOK::MCPHERSONMiddle-age Mutant Yiddish AccountantsFri Dec 07 1990 11:4419
    
>    -.4
>    .... installation on a non-system disk"
>    
>  Is this now possible?  I also am running out of room on the system disk
>   and have loads of room on another.  Is there just one logical to change
>   or would this be major reconstruction?

    Sure.

    If you're strapped for space on the system disk, use the AWD option for
    VMSINSTAL.   You can also specify that the MCC directories be created
    on a NON-system disk as part of the installation procedure.  

    I haven't tried moving them around "after the fact", but oyu should be
    OK as long as you make sure that all references to MCC_SYSTEM and
    MCC_COMMON point to the right disk:[directory].

    /doug
13.7Can it really install elsewhere?HAFDOM::SITZ_GLFri Dec 07 1990 13:3414
    re .6
    
    Yes you can specify a non-system-disk location for installation
    of the kits... However:
    
    The installation procedure will look at the system disk and if there
    is not 70k free blocks there it will throw up its hands and quit.
    Perhaps the "AWD" will cause the program to look elsewhere for space
    for installation work. I have not had time to explore this.
    
    Regards,
    
    Glen R.
13.8SPIDER::GOLDMANEvery choice is worth your whileFri Dec 07 1990 16:3010
>    The installation procedure will look at the system disk and if there
>    is not 70k free blocks there it will throw up its hands and quit.
>    Perhaps the "AWD" will cause the program to look elsewhere for space
>    for installation work. I have not had time to explore this.
    
    	If you use the "AWD" option, the installation procedure looks
    for 20K free on the system disk and 70K free on the alternate disk
    (i.e. the one specified in the AWD parameter).

    	amy