| Can I put domain definitions somewhere other than in the root
directory? If so, how do I refer to a map file using a domain name
with a period in it? That is, domain is IT.SRPC but I cannot create an
initial map filename of MCC$_IT.SRPC.DAT as VMS would dislike this.
>>> The name map file name reflects the domain id and also the last simple name
>>> of the domain. For domain aus.andrew the map file woild be:
>>>
>>> mcc_<32_hex_char_domain_uid>.mcc_map_andrew
>>>
>>> Caution: If you create a domain, poulate it with members, save
>>> the map file, delete the domain (and all of its members), recreate the
>>> same domain with all of the previous members, and try to use the old
>>> map file, it won't work. The newly created domain will have a different
>>> uid.
Thought !!!! can I create the domain then save the (empty) map and
just look at the filename, copy the world map into that file and go?
>>> Yes. Just be sure you place the geographical data at the end of the file.
>>> And for the current version, don't muck around with any of the objects!
>>> The code that reads the map file is a little too sensitive to things like
>>> the number of blanks between words on a line.
Another question.. if I want to use NODE4 names somewhere other
than in DNA_NODE directory (say IT.AP) dor I need to cretae special
backtranslation directories ... mind racing ahead.. maybe that's what
the command procedure does you dolt!! Okay will use that.
More esoterically, where is all the sexy map information stored? In
the map file?
>>> Yes.
(if so does that mean remote use of the domain requires
remote access to the map file?)
>>> If all systems are using the same name space, the domain uid will be the
>>> same, so in that case, you could mail the map file from one system to
>>> another
Please excuse this sudden rush of enthusiasm but we've got VCS, DCM
and MCC running here and the combinations are mind-boggling.
>>> No problem.
|