| 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 |
I have a customer who will start using DECmcc. They have also been developing a trader application which uses DNS to store workstation node names, among other things. Their question is now: Do DECmcc require that they use the MCC-directory structure in DNS (eg .DNA_NODE) for storing DECnet names or could that be changed (I suppose not)?. The reason they ask is that the application uses another nodename structure. If they have to use .DNA_NODE, is soft links then the best way to go or is there any other solution? Anna-Lena
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1128.1 | DECmcc doesn't enforce naming policy | TOOK::CAREY | Thu Jun 13 1991 13:13 | 20 | |
We have worked diligently to make sure that our customer's can use
whatever naming policy they want with DECmcc and DNS. So the existing
naming policy doesn't present a problem for us.
The .DNA_NODE naming convention is supported through our setup tools,
and provides a simplified approach to getting started.
the MCC_DNS_SETUP procedure can be used to produce lists of node4s to
register, and it uses the .DNA_NODE convention. You can take the files
output from that and change the naming structure to register things, or
generate your own set of files. We frequently register DECnet nodes in
different trees.
Naming policy is a function that can be handled by network managers,
not network management tools. DECmcc simply supplies a simple
convention as a convienience.
-Jim Carey
| |||||