[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

498.0. "MCCUT010_DEINSTAL.COM Question" by TAZBOY::ZIGLER (Tom Zigler, DTN 432-7541) Wed Nov 28 1990 20:34

    After studying the DECmcc BMS T1.1.0 EFT release notes, I am puzzled by
    the following statement on page 1-5:
    
    "If you have installed DECmcc before, you will need 2000 global pages
    to install it again, after running MCCUT010_DEINSTAL.COM."
    
    On my demo system in the office, I have already done the following in
    this sequence:
    
    1) Installed DECmcc BMS T1.0.1 EFT software
    
    2) Installed DECmcc BMS V1.0 SSB software
    
    Thus, since the MCCUT010_DEINSTAL.COM procedure does not exist, must I
    perform some other equivalent DEINSTAL procedure BEFORE I attempt to
    install the DECmcc BMS T1.1.0 EFT software?  
    
    Please advise.
    
    		\Thanks in Advance

T.R	Title	User	Personal Name	Date	Lines
498.1	I think you can ignore that statement	TOOK::GUERTIN	I have an in_e, you have an out_e	`Thu Nov 29 1990 15:59`	18
	Tom, I'm pretty sure you can ignore that statement. It appears as though that statement was left over from a previous kit. I have been working on the kitinstal (off and on) for the last couple of months and this is the first time I've noticed the reference to the MCCUT010_DEINSTAL.COM file. It is a requirement from SQM (at least it used to be) that we be able to install over an already installed MCC. So running the deinstall command procedure should not be needed. I can check if the deinstall command procedure is referenced in the installation guide or not. The command procedure gets placed on the kit, but I don't think it gets moved off of the kit during installation. Even if it is moved off the kit (to God knows where) it is probably hopelessly out of date. In other words: If you MUST run the deinstall procedure before reinstalling MCC then it is a bug. -Matt.
498.2	Why not DEINSTALlation procedures?	VINO::LUNDGREN	John - ISB/ASAP SSE - 297-5537	`Fri Nov 30 1990 13:54`	20
	This brings up a very interesting topic about having deinstallation procedures available. I really do not understand why ALL DEC layered products do not have a deinstallation procedure. Very few seem to. It makes so much sense to me. Instead of a customer having to poke around KITINSTAL.COM and/or the system directories to find and delete files (very risky!) to regain disk space, they could just execute a command procedure. This command procedure could even take the DCL verb(s) out of DCL tables, help modules out of HELPLIB.HLB, etc. If I want to install DECmcc EFT T1.1.0 on my system (70K Blocks) and do not have enough space, I should be able to run the XYZ product's deinstallation procedure to get some disk space back. This is, by no means, a criticism of the DECmcc product. I applaud your efforts! I understand that this is not a priority item, but it is a nice feature that should not take an excessive amount of time to implement. -John