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 questions about the use of MIR troughout the DECmcc versions changes on Ultrix. My customer had to switch from DECdns to local MIR for various reasons, and they are also upgrading DECmcc bms version frequently. The problem for them is to be able to keep as much as possible of their registered network configuration when upgrading from one version to another. I saw in the MM programing guide that some registered instance knowledge could be kept in some cases, but I could not find more details. The questions are : - Can we keep the registered entity instance knowledge when installing a new DECmcc kit ? Are the mcc_dns_ent.* files destroyed at de-installation or can we keep them ? I think that at least, these could be re-used if the class definition has not been modified. What about the mcc_dns_att.* ? What happens if the class definition changes for partitions other than identifiers (registered identifiers) ? For instance when adding a new event in the class definition. For instance when adding a new characteristic. I would appreciate more information or adequate pointer to documentation. Florence
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
3014.1 | FT not for production use | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Mon May 18 1992 09:59 | 15 |
Unfortunately, there have been a number of changes between field test versions of DECmcc for ULTRIX that have not allowed versions to inter-operate. In particular, the MIR format has changed. Since field test software is not intended for production use, we have not provided conversion tools (which would be fairly expensive to build). So it has often been necessary to remove old MIR files before upgrading. There have also been a few glitches in the entity registration process, so codes have changed for some of the modules that are new for V1.2. -- Erik |