| 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 |
When you create a new domain from the Iconic interface it gives you the option to specify the directory you want the map file to be in. However it doesn't matter what directory specification you give, because the map file is always written to the directory you were in when you fired up MCC (you can even give a directory which doesn't exist and it won't complain). Another problem/feature is why have the logical mcc_maps defined as a search list to locate the map file when opening a domain? Why can't MCC read the attributes of the domain to determine the map file location? The problem arises when you have multiple users accessing the same domain - the person who originally created the map gets the correct icons displayed, other users just get the domain members autoplaced on the screen - there is no error message that says that the map file hasn't been located. That user can then modify/add members to the domain and update the map. When he has finished he saves the changes made to the map and exits. This new updated map is then saved to his own directory. It therefore appears to be possible for x users to have x different copies of what should be the same map file. If MCC read the attributes of the domain then this problem would not arise. Ian
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 245.1 | a bit of history... | BARREL::LEMMON | Thu Aug 09 1990 12:35 | 27 | |
At one time we had discussions whether there should be one map per domain or whether each user could their own map of the same domain. (Quite a religious one I might add!) The outcome was the following: o Maps can be per user where the user could define MCC_MAPS to point a specific directory where the maps are to reside. o Maps can be per system (or even multiple systems if DFS is used.) by defining MCC_MAPS system wide. The default definition of MCC_MAPS is look in the local directory first, If it is not there, look in MCC_SYSTEM. Now to reply to your note... The directory argument to the create domain operation is not used by the iconic map. I believe fms like Historical Occurrence Recorder uses it. We would use this argument only if there is one map per domain, which as stated above, is not the case. If you want more than one user to access the map file you have a common location for the map files. Everyone who wishes to use it could define MCC_MAPS to point to a common directory. You could even edit the SYS$STARTUP:MCC_START_BMS2.COM startup file and define MCC_MAPS system wide. | |||||
| 245.2 | This could be confusing... | RDGENG::PRATT | Thu Aug 09 1990 14:22 | 5 | |
If the Iconic map doesn't use the directory argument, why include it in the create domain window display? I am sure that customers will be confused by this as well - why display a field which you can modify, but has no effect? Ian | |||||
| 245.3 | Yes it is confusing... | BARREL::LEMMON | Thu Aug 09 1990 18:15 | 7 | |
I believe there are other management modules that will use this argument. As I understand it the historical occurrence recorder FM is using it. I agree that it is a bit confusing and will check to see who on the MCC team is using it. Maybe we can hide it from the user. /Jim | |||||