| 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 |
Shalom,
The installation of DECMCC BMS passed with no problems,the customer tried
to installed the Toolkit twice and it failed, follow the logs.
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
The station status:
5000/120
32M memory.
ULTRIX 4.2A
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
The installation procedure:
etld -l /dev/rmt0h
Please make sure your installation tape is mounted and on-line.
Are you ready (y/n)? y
Positioning Tape
*** Enter Subset Selections ***
The subsets listed below are optional:
1) DECmcc Developers Toolkit
2) All of the Above
3) None of the Above
4) Exit without installing subsets
Enter your choice(s): 2
You are installing the following subsets:
DECmcc Developers Toolkit
Is this correct? (y/n): y
DECmcc Developers Toolkit (MCRDTKT124)
Copying from /dev/nrmt0h (tape)
Working....Mon Mar 2 14:48:21 IST 1992
Verifying
Working....Mon Mar 2 14:50:16 IST 1992
Would you like to run the IVP (y/n) [y]:
A DECmcc Developer's Toolkit for ULTRIX V1.2 license has been
registered. If any errors appear, please re-install the product.
Verification will take between 20 and 40 minutes depending CPU type.
***********************************************************************
Beginning Installation Verification Procedure for
ULTRIX DECmcc Developer's Toolkit V1.2
***********************************************************************
The IVP takes approximately 10 minutes to complete.
Do you wish to continue? (y/n) [y]
Starting the Installation Verification Procedure for
ULTRIX DECmcc Developer's Toolkit V1.2...
***********************************************************************
**** Installation Verification Procedure Failed ****
The Installation Verification Procedure for the
ULTRIX DECmcc Developer's Toolkit V1.2
failed.
Please include the following information when submitting a report:
1) Subset name,
2) ULTRIX Version,
3) Any log scripts in the /usr/mcc/ivp directory.
***********************************************************************
setld:
The subset control program for subset MCRDTKT124 failed.
Rewinding Tape...
Working....Mon Mar 2 14:51:21 IST 1992
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
The IVP log:
Creating testmm with mcc_yourmm_auto_create.script...
Checking dictionary for previous use of AM name ivp ...
Checking dictionary for previous use of global entity code 306...
Checking dictionary for previous use of MCC child entity code 306...
z: File exists.
Could not build a starter management module...
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
The previous IVP log:
Creating testmm with mcc_yourmm_auto_create.script...
Checking dictionary for previous use of AM name ivp ...
Checking dictionary for previous use of global entity code 306...
Checking dictionary for previous use of MCC child entity code 306...
rm: remove z? mcc_ivpmake_subs.ed: No such file or directory
Could not build a starter management module...
Any idea what we have done wrong??
Regards
Kalai Yael
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2468.1 | An alias may be your problem | MOLAR::BLACK | Thu Mar 05 1992 09:37 | 11 | |
I just reran the toolkit ivp on the EFT kit and it ran fine.
Our guess is that you may have an alias for the 'rm' command defined
(alias rm 'rm -i') which prompts to remove a temporary file. Since the
ivp script must be non-interactive, this causes it to fail. Worse yet,
it uses rm to remove the scratch directory; causing this to fail.
Can you unalias rm (# unalias rm) and manually delete the scratch
directory (# rm -r /usr/mcc/ivp/mccdtkivp_scratch). and then rerun the
ivp? Let us know if this fixes your problem. Thanks.
| |||||
| 2468.2 | R.1 IVP FAILED AGAIN | TAV02::KALAI | Mon Mar 09 1992 08:06 | 34 | |
Shalom, My customer tried what you suggested but ivp failed once more. -------------------------------------------------------------- We really had an alias for rm converting it to rm -i. I removed the alias but could not find the scratch directory /usr/mcc/ivp/mccdtkivp_scratch. I tried to run the ivp again but it failed. Here is the log file: Creating testmm with mcc_yourmm_auto_create.script... Checking dictionary for previous use of AM name ivp ... Checking dictionary for previous use of global entity code 306... Checking dictionary for previous use of MCC child entity code 306... z: File exists. Could not build a starter management module... I include also the listing of the /usr/mcc/ivp directory: 49 cougar:/usr/mcc/ivp# ls -l total 15 -rwxr-xr-x 1 root 7048 Dec 20 13:29 mccbmsivp -rw-r--r-- 1 root 1783 Feb 27 18:10 mccbmsivp.log -rwxr-xr-x 1 root 4778 Dec 19 16:32 mccdtkivp -rw-r--r-- 1 root 315 Mar 9 11:52 mccdtkivp.log I think there is a scratch directory that must be removed somewhere but I don't seem to find it. I'll appreciate any forther help on that subject. Best regards, Kalai Yael | |||||
| 2468.3 | /usr/mcc/ivp/mccdtkivp_scratch | MOLAR::BLACK | Tue Mar 10 1992 12:39 | 3 | |
Sorry--scratch directory got moved during one of the last kitting
efforts. Try "rm -r /usr/mcc/ivp/mccdtkivp_scratch" then rerun with
your rm alias unset.
| |||||