| 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 |
Quick question regarding the following commands : 1) Deregister and Erase. My question is ... what is the difference ? (i've already looked at the manual). Bipin.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1125.1 | Partial answer... | CHRISB::BRIENEN | DECmcc Bridge|Station|SNMP Management. | Thu Jun 13 1991 09:20 | 5 |
From the standpoint of AMs, there is NO DIFFERENCE. There may be a difference between DEREGISTER and ERASE as they relate to past data (ERASE may blow away past data, whereas DEREGISTER might not). Anyone from the "upper half" of MCC care to comment? | |||||
| 1125.2 | Chris is right | TOOK::KOHLS | Ruth Kohls | Thu Jun 13 1991 10:30 | 12 |
In section 15.4.1.7 of the SRM "Erase" is defined as causing all knowledge of the entity to be removed from MCC's configuration, plus any previous information is no longer available via mcc_call. In 15.4.1.4, "Deregister" is defined as removing entities from the configuration, but previously gathered information remains accessible via mcc_call. So, Chris is right. It makes no difference to AMs. Ruth | |||||
| 1125.3 | deregister/erase | MCC1::MULLIGAN | Thu Jun 13 1991 12:45 | 20 | |
The ERASE directive dispatches to the CONFIG/REGISTRATION FM which removes the entity from all domains of which it is a member then calls the AM with an ERASE directive (the AM is not required to support this directive) then it deletes the entity from the configuration. The DEREGISTER directive dispatches to the CONFIG/REGISTRATION FM which removes the entity from all domains of which it is a member then calls the AM with an DEREGISTER directive (the AM is not required to support this directive) then it deletes the entity from the configuration. In the beginning the MCC/VMS instance repository was the MIR and the behavior of deregister and erase were different. Deregister marked the entity as deregister were erase deleted the entry from the MIR. Today with the MCC/VMS instance repository being DNS an entity is either in or out. So deregister and erase produce the same result. | |||||