[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

771.0. "Toolkit without the Director..." by VINO::LUNDGREN (John - ISB/ASAP SSE - 297-5537) Tue Mar 05 1991 14:50

I would like to be able to install the DECmcc Toolkit on
our main development cluster but cannot have DECmcc Director or 
BMS on it because it uses the DEC: default namespace. The reason
is that we perform all of our source code builds on this cluster and
I want to be able to automatically process the MSL files through
MMS if they have changed. It would then automatically invoke DAP
to update a private dictionary that we also have on this cluster.

I realize that currently the Toolkit requires DECmcc Director or
BMS to be previously installed in order to install. Can this requirement
change in the future? Can anyone suggest a quick (and preferably clean)
way of being able to run both the MSL translator and DAP on this cluster
without the Director?

Regards,

John

T.R Title User Personal
Name Date Lines

771.1 partial answer TOOK::KOHLS Ruth Kohls Tue Mar 12 1991 15:36 21

T.R	Title	User	Personal Name	Date	Lines
771.1	partial answer	TOOK::KOHLS	Ruth Kohls	`Tue Mar 12 1991 15:36`	21
	>I realize that currently the Toolkit requires DECmcc Director or >BMS to be previously installed in order to install. Can this requirement >change in the future? Can anyone suggest a quick (and preferably clean) >way of being able to run both the MSL translator and DAP on this cluster >without the Director? First, DAP comes with the Director and BMS kits, not the Toolkit. Next, the BMS and DIR kits create directories and an "environment" that the Toolkit tools use. I, personally, don't see that the tools are much use without the API. A better solution to the problem the way you've stated it might be to improve DECmcc's usage of, and relationship to, DNS. That problem is being worked, but that is a future, though not all that distant. For the present, you could make yourself a distributed build environment using MMS, CMS, DFS, and DECmcc Director or BMS and Toolkit, the DECmcc pieces on a cluster or system where you don't have namespace restrictions. I've sent you mail about this. Ruth Kohls

>I realize that currently the Toolkit requires DECmcc Director or
>BMS to be previously installed in order to install. Can this requirement
>change in the future? Can anyone suggest a quick (and preferably clean)
>way of being able to run both the MSL translator and DAP on this cluster
>without the Director?

First, DAP comes with the Director and BMS kits, not the Toolkit.  Next,
the BMS and DIR kits create directories and an "environment" that the Toolkit 
tools use.  I, personally, don't see that the tools are much
use without the API.  A better solution to the problem the way you've
stated it might be to improve DECmcc's usage of, and relationship to, DNS.
That problem is being worked, but that is a future, though not all that distant.

For the present, you could make yourself a distributed build environment
using MMS, CMS, DFS, and DECmcc Director or BMS and Toolkit, the DECmcc 
pieces on a cluster or system where you don't have namespace restrictions.

I've sent you mail about this.

Ruth Kohls