[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

2806.0. "VMS: If you have disk space problems: (VMSINSTAL AWD option)" by TOOK::L_GROSSMAN () Tue Apr 21 1992 14:36

The following disk space references/example are for DECmcc BMS T1.2.7

If the installation comes back with the following message"
(possibly different disk space requirements)

%MCCBMST-E-INSFDISK,    This kit requires at least 83150 blocks to instal.
-MCCBMST-E-INSFDISK,    With the AWD option, 22650 blocks are required,
-MCCBMST-E-INSFDISK,    and 83150 blocks are required on the AWD disk.

You therefore need to:

1) Specify some disk/directory other than the system disk for MCC_COMMON

Specify some disk other than the system disk for where to place the
MCC_COMMON files. You will need about 60,500 blocks on this disk.
If the system disk is a cluster boot disk, the specified disk for
MCC_COMMON has to be available to the satellites that want to run MCC.

2) Use the VMSINSTAL AWD kitinstal option

The VMSINSTAL AWD (Alternate Working Directory) option specifies where
to place all the kit working files (files from all savesets) before they
are placed in the appropriate destination device/directory.

BY DEFAULT, all files are FIRST placed on the system disk. In this
case the system disk would require the 83150 free blocks to instal.

By using the VMSINSTAL AWD option, you can specify where the working
directory and files are placed.

Example:

$ @sys$update:vmsinstal mccbmst012 <kit_location> -
	options awd=<working_directory>

Where:
	<kit_location> is a complete directory path specifying where
	the kit is located

	<working_directory> is a complete directory path where the
	kit has 83150 free blocks. VMSINSTAL will create a directory
	with the same name as the kit being installed.

Note: The AWD option and any other vmsinstal options should be separated
with commas and no spaces.

T.R Title User Personal
Name Date Lines

2806.1 still get insufficient disk space PARVAX::STORM Wed Jun 10 1992 22:29 14

T.R	Title	User	Personal Name	Date	Lines
2806.1	still get insufficient disk space	PARVAX::STORM		`Wed Jun 10 1992 22:29`	14
	Hi, I installed T1.2.7 the way described in .0 and it worked no problems. Now I needed to install T1.2.7 on another disk. I re-booted my workstation so MCC would not start. My disk that I need to put MCC on has 74,000 blocks free disk space. My awd disk has over 1,000,000 blocks free. I specify an area for mcc common that is different than the default value. I am still getting the message that I have insufficient disk space. Any ideas? Thanks, Karen

Hi,

I installed T1.2.7 the way described in .0 and it worked no problems.

Now I needed to install T1.2.7 on another disk.  I re-booted my workstation
so MCC would not start.  My disk that I need to put MCC on has 74,000 blocks
free disk space.  My awd disk has over 1,000,000 blocks free.  I specify
an area for mcc common that is different than the default value.
I am still getting the message that I have insufficient disk space.

Any ideas?

Thanks,
Karen