[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

1148.0. "Problem with RENAME directive" by EMASS::BOYD () Fri Jun 14 1991 18:10

I am currently working with BBN, and we are having a some problems with the
"RENAME" directive. We are using MCC V1.1 and VMS V5.3 The global entity we
    are using is a "PSN" which has four identifiers defined in its MSL.

    GLOBAL ENTITY PSN = 501 :
        IDENTIFIER = ( subnet address, name, dns full name, property number ),
        SYMBOL = class_psn,


The dns full name is defined as the primary name, the name is defined as not
used, and the others are defined as alternate names.

	IDENTIFIER ATTRIBUTES

	    ATTRIBUTE dns full name = 3 : FULLNAME
		DNS_IDENT = PRIMARY_NAME,

	    ATTRIBUTE name = 1 : SIMPLENAME
		DNS_IDENT = NOT_USED,

	    ATTRIBUTE subnet address = 4 : IPADDRESS
		DNS_IDENT = ALTERNATE_NAME,

	    ATTRIBUTE property number = 5 : DT_BBNASSET
		DNS_IDENT = ALTERNATE_NAME,

	    END ATTRIBUTES;

(I can send the complete MSL if required, but didn't want to put it all in a 
notes file.)

The PSN  access module uses a private MIR where the identifiers are also kept. 
Following are the characteristics exhibited when an identifier is renamed:

 - Subnet address - This seems to work as expected. Both DNS and the MIR are 
		    updated and no errors are returned.

 - Name - When name is renamed the following error message occurs:

		OUT_P from AM RENAME:


		[  1 ] (
		    )Error condition at step 15

		** ROLLING BACK RENAME: **

	Rollback  also seems to recall the AM with the old identifier 
	(which has been	already modified), and the AM can not find it to 
	correctly do the rollback. The result is that the MIR value is renamed 
	and the DNS value is not.

 - DNS full name - This results in the same "step 15" error message, but DNS
	now has both the old and the new value for the dns full name, but the 
	MIR only has the new value (because the rollback passed the old value 
	which was already removed from the MIR).

 - Property number - Not tried. The identifier is not supported in the MSL by 
	the RENAME directive.

There seems to be two problems. One with the error recovery performing 
rollback, and the other is a "step 15" error whatever that is. Can someone 
give me a pointer of where to get more information or has someone else had
this kind of problem with the rename directive?

T.R	Title	User	Personal Name	Date	Lines
1148.1	Could you send more output?	TOOK::TAN	Ed Tan	`Wed Jun 19 1991 14:54`	26
	I am currently looking into your two RENAME problems. You are right about the problem of rollback, in that in V1.1 whenever there is a rollback in RENAME the AM is called with the old identifier. This has been a known bug and will be fixed for V1.2. In order to help me understand your other problem, could you do the following and send the output to me (TOOK::TAN) or post it here. Thanks: 1. Turn on the debug output again by defining the logical mcc_config_fm_log to 6. 2. Re-do the RENAME command on global entity PSN using the two identifiers (dns full name) and (name). Include in the output to me all the commands you type, debug output and DECmcc response. Step 15 error is during a call to mcc_dns_rename_identifier. Could you check your AM rename code and make sure that the in_entity passed to you is not modified in your code (it should be read only). Also could you briefly explain what your AM rename code does when called (such as writing to MIR, and do you write anything to DNS?) Thanks, Ed
1148.2	DNS_IDENT can't be NOT_USED to look into DNS	TOOK::TAN	Ed Tan	`Tue Jun 25 1991 00:19`	54
	In 0: the identifier called name is define with id = 1, datatype is simplename and DNS_IDENT is NOT_USED. The following is part of the output sent by the author of 0:, $ manage/ent DECmcc (V1.1.0) .... MCC> dir psn * .... PSN DEMO_NS:.bbn.node.CDL33 AT 20-JUN-1991 17:39:35 Directory successful. dns full name = DEMO_NS:.bbn.node.CDL33 name = CDL33 property number = "bbncc00-33" subnet address = 8.255.0.33 .... MCC> rename psn CDL33 name CDL88 PSN CDL33 AT 20-JUN-1991 17:40:25 The requested operation cannot be completed MCC Routine Error = %MCC-E-INV_DNSIDENT, specified identifier attribute is not valid for instance lookup In the SRM section 7.5.1.8 Syntax of an Attribute and Attribute Partition Definition, DNS_IDENT is defined as: "...If the identifier is not to be the PRIMARY_NAME or is not a valid ALTERNATE_NAME used for lookup in the DECdns namespace, then DNS_IDENT = NOT_USED. These identifiers will not be added as alternate identifiers in the namespace and are not valid to be used as lookup keys..." What this means is if an identifier is defined as DNS_IDENT = NOT_USED, it cannot be used to look up an entity in dns. (the error status MCC_S_INV_DNSIDENT is returned by kernel routine mcc_dns_rename_identifier in the above example) However, such an identifier is still displayed using the DIRECTORY directive. If you want RENAME (or other directives that deal with dns) to work on the identifier called name, set its DNS_IDENT to ALTERNATE_NAME in msl.