T.R | Title | User | Personal Name | Date | Lines |
---|
953.1 | a lot of questions, some answers | TOOK::CALLANDER | | Wed Apr 24 1991 17:42 | 4 |
| the owner and directory information is used by the historian to determine
the location for data storage. I don't know all of the details but the
use of these arugments are explained the the DECmcc Basic Management
system Use manual, chapter 3.
|
953.2 | local DIRECTORY the same on all systems ??? | KETJE::PACCO | | Thu Apr 25 1991 06:13 | 12 |
| I agree on how it is described, and how it is used for the MAP file,
and the historian, but
If from another node that specific domain is used, with all its
members, WHY is that second user tied to the DIRECTORY of the first
user, who created the domain, and cannot choose the location for its
map files, independently of the organisation on the first system ?
Is this a permanent restriction, temporary restriction, or a design
goal ?
Regards,
Dominique.
|
953.3 | | TOOK::F_MESSINGER | | Thu Apr 25 1991 08:09 | 6 |
| Dominique,
The DIRECTORY, and OWNER have nothing to do with the
map file. A map file is always read out of the users
directory pointed to by the logical mcc_maps:.
Fred
|
953.4 | Is DIRECTORY a local or network attribute ? | KETJE::PACCO | | Fri Apr 26 1991 16:24 | 8 |
| This still does not explain why there is a DIRECTORY pointer in the
DNS. A directory cannot be the same on different systems !
I agree somehow on the OWNER, but this should require a network
wide security (UIC) scheme !
Regards,
Dominique
|
953.5 | re:.4 | BARREL::LEMMON | | Thu May 02 1991 11:38 | 29 |
| This still does not explain why there is a DIRECTORY pointer in the
DNS. A directory cannot be the same on different systems !
> It can if the a file server is being used. This may not truly be the case for
> VAX/VMS since the Distributed File Server (DFS) software does not allow
> shared write access, but I believe it is true on ULTRIX using NFS. (Hopefully
> there is a ULTRIX guru out there who can confirm this.)
>
> The reason it is stored in DNS is because it is an attribute of the domain
> global entity. The domain global entity, and it's associated information
> (identifier attributes, characteristic attributes, member child entites,
> etc... is stored in DNS on VAX/VMS. This makes the domain global to
> the namespace.
>
> The current philosophy, which may be incorrect, is that everything is
> domain based. Data such as historical information, use the domain directory
> as the location to create it's files.
>
> I have heard, and still am hearing that it should be domain based but allow
> users to have thier own view of the domain. This, in fact, is why the
> MCC_MAPS logical was created. The maps are domain based but the user
> can specify where they want them stored.
>
> I believe a similar model is needed for other MMs such as Historian.
> That is, remove the directory and owner id attributes from the domain
> fm and require MMs that generate files to have a INITIALIZE directive
> that asks the user for this information, and then creates the data file.
>
> /Jim (also Domain FM PL)
|