Conference azur::mcc

    Yes, the T1.2.4 release notes has bugs too. And, it wasn't updated
    for X1.2.15 and, if you note at the bottom of your note it says that
    using the AWD option (alternate working directory) you only need
    22100 blocks. If you don't use the AWD option you have to have room
    on the system disk for VMSINSTAL to restore the BACKUP Saveset to
    VMSINSTAL's working directory. The "D" saveset is 73000 blocks.
    
    As an example of how to do it I include a simple comfile I use to do my
    installs.
    
    $ define tmp user$nets:[scratch]
    $ define kit USER$KITS:[MCCKIT]
    $ @sys$update:vmsinstal mccbmsx012 kit: options awd=tmp:
    
    Hope this helps.
    
    s/rob

    I did exactly what you mentioned in .1, but the installation still
    fails with "This installation requires at least 76700 block to
    install".  However, it doesn't give me the addition message to use
    the awd option.  I have 28000 blocks on my system disk and 130000
    on my scratch disk.  Is there a way to work around this problem?  Is
    there a kit that allows for installation not on the system disk?
    
    Thanks,
    
    Mike Rosen

Did you specify the awd kit installation option to point to a disk
that is NOT the same as the system disk?

Ex:

$ @sys$update:vmsinstal mccbms%%% <kit_location> options awd=ddcu:[000000]

where ddcu is some work disk that has at least 83000 blocks free.

Some old kits might also be checking for the wrong amount of disk space,
so just make sure the work disk has room for error.

    My system disk, dua0, has 28000 free blocks
    My scratch disk, dua2 has 130000 free blocks
    
    The exact command was:
    $ @sys$update:vmsinstall mccbmsx dua2:[decq.mcc] options -
      awd=dua2:[decq.scratch]
    
    (it was actually all on one line, but my stupid notes editor made me
    wrap it around)
    
    I orginally tried having the awd=dua2:[decq.mcc], but I thought there
    might be a problem with having the awd the same as the kit_location, so
    I tried a scratch directory.  I also tried dua2:[000000] and I also
    tried using a logical name to point to the awd.
    
    What I'd really like is to have mcc_common be on dua2, rather than my
    system disk.  Will/is this be supported in another kit?  Isn't a new
    one due out this week?  If not, then I'll have to figure out what the
    installation doesn't like about my system.
    
    Thanks

>    What I'd really like is to have mcc_common be on dua2, rather than my
>    system disk.  Will/is this be supported in another kit?  Isn't a new

    You can have MCC_COMMON anywhere you want.   This has been supported
    since V1.1.

    ;doug

    The problem isn't whether or not I'm supposed to be able to have
    MCC_COMMON anywhere I want.  The problem is that the kit for
    X1.2.15 fails when you try to do it.  So to rephrase my question,
    Is or will there be a kit after X1.2.15 that has this problem fixed?
    If not, is there a workaround?
    
    Thanks

Yes, if you specify an AWD to point to some disk other than the system disk,
and the answer to the first question of where mcc_common should point,
the installation WILL check for the required amount of NON- mcc_common files
on the system disk (which I believe is not more than 21,000 blocks)

I do not remember if if X1.2.15 had bugs with checking disk space, but
an EFT update kit WILL be available REAL soon, so I recommend you try
to instal the new kit when it comes out.

    X1.2.15 did have problems calculating disk space.
    I think it really needed 30k on the system disk or something.
    
    As Larry suggests, skit trying to install X1.2.15 and see
    note 3.144 (actually look at notes 3.142 - 3.145) and install
    the T1.2.7 kit.
    
    s/rob