[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

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

4111.0. "RFI on Registration FM." by KETJE::PACCO (Gallia divisa est in partes tres) Wed Nov 18 1992 14:30

    This is just a remark I hope will reach
    the group or person developing or maintaining the
    Registration FM.
    
    It would be nice to be able to (RE)REGISTER an entity, even if it was
    already registered.
    
    This wish becomes very important in e.g the following case.
    
    The modifications which were applied on the NODE AM makes a child
    entity STATIC where originally it was DYNAMIC.  This simple update
    in the dictionary, which is applied during the  BMS V1.2.3 installation
    results in unusable DECnet phase V nodes in DECmcc.  The only way is to
    deregister and reregister ALL registered NODES.  It would be handy to
    be able to just isse a REGISTER command, which would have the effect of
    keeping all relevant data untouched (Read but Rewritten), but which
    would write the additional information if required, as it is in this
    very case.
    
    	Dominique.

T.R	Title	User	Personal Name	Date	Lines
4111.1		TOOK::STRUTT	Management - the one word oxymoron	`Tue Nov 24 1992 10:34`	17
	It's worth noting that the Registration FM, in v1.0 and v1.1, was designed to allow REGISTER to perform an intial register operation as well as a subsequent re-register operation. However, when support for partial registration was added in v1.2, the re-register feature was inadvertently dropped. This was recently QARd as #14 in MCC013_INT - it has been converted into a suggestion to add a new directive to handle re-registraion. This probably means it won't be implemented in V1.3 However, if you consult the V1.3 release notes, a procedure has been defined (setting a registration log bit 1000000) to enable reregistration to occur for Phase V nodes, avoiding the problem with losing all other DNS information. Colin
4111.2	Reregistration very appreciated.	KETJE::PACCO	Gallia divisa est in partes tres	`Wed Nov 25 1992 11:08`	23
	Is it in V.1.3 or already in BMS V1.2.3 ? If it is only in V1.3 please document it clearly. I had difficult times to deregister and reregister all V nodes, following the release notes "You will need to deregister and reregister all DECnet Phase V nodes to use this feature". Release notes were further not very explanatory: "Digital recommends using the repository population routines conatined in the kit." I havent found these, and I wonder if these could work because: e.g. If you create a node and you are able to specify all access information correctly as it was before in DNS, the towers of routers and X.25 gateways are still not filled. Also the standard WANrouter or X25gateway software does not allow to update the towers if you already have the DNS_Backtranslation address specified ... For the OSI systems each one has to give the LOCAL ncl command UPADTE SESSION CONTROL TOWER MAINTENANCE * To summarize, passing from BMS V1.2 to BMS V1.2.3 was not easy at all. Dominique.