[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

6372.0. "Case sensitive or insensitive names ?" by KETJE::PACCO (Horum omnium fortissimi sunt Belgae) Mon Sep 04 1995 12:49

    	According the SRM is partial wildcarding on SimpleName case
    sensitive.  This means
    
    	A*	will find e.g A100, Aabc, ABC etc...
    		but not       a100, aabc, aBC etc...
    
    I was looking to the identifier of NODE, CSMA-CD, STATION.  This
    identifier attribute 'Name' is of type SimpleName.
    
    QUESTION 1:
    Why can I , under these circumstances, do
    	sho node rpl109 csma sta C* all id
    or	sho node rpl109 csma sta c* all id
    and in both cases receive the result:
    
    Node bc:.rpl109 CSMA-CD station csmacd-0
    AT 1995-09-04-11:21:58.477 Identifiers
    
    Examination of attributes shows:
                                       Name = csmacd-0
    
    The same is true for other NODE child entities.
    
    QUESTION 2:
    Which is in DECmcc and TeMIP the 'suggested' data type to name an
    object if is is there only to access the object.  Should be chosen
    a priori for a case sensitive or case insensitive name?
    
    Regards,
    	Dominique.

T.R	Title	User	Personal Name	Date	Lines
6372.1	DNS is case sensitive...I think !	DSVB03::TABONE		`Mon Sep 04 1995 13:23`	7
	Hello Dominique, To answer your question 1, I think that DNS is case insensitive. So, it's a normal behaviour you receive both results. Best regards, Philippe
6372.2	Simple Names alone ...	KETJE::PACCO	Horum omnium fortissimi sunt Belgae	`Mon Sep 04 1995 20:18`	9
	Philippe, A SimpleName has nothing to do with DNS. The different 'fields' of a FullName are SimpleNames, but in that context the SRM states the 'FullName' is case insensitive for searches. The question was, when You use simplenames as simple names. Dominique.
6372.3	TeMIP point of view .	TAEC::BACCAR	Notes	`Wed Sep 06 1995 10:17`	18
	Some case sensitivity/insensitivity problems have been fixed in TeMIP. Fullname is case insensitive because of DNS, and this works well under DNS selection equals to DNS. But in the case of DNS selection equals to MIR, the following changes have been made in the framework code to have the same behaviour as with the DNS selection equals to DNS : 1 new MIR routines (Cisam) where fullname is case insensitive (as DNS) 2 Bug in the match object routine of the framework ( strcmp -> strcasecmp etc ...) 3 remove the lowercase translation of all fullname by the NSM DNS code ... Best Regards, ___Hedi_ ps: TeMIP SSB V3.0 on DIGITAL UNIX, of course ...
6372.4	SimpleNames ? not FullNames !	KETJE::PACCO	Horum omnium fortissimi sunt Belgae	`Thu Sep 07 1995 20:10`	5
	I do not have problems with fullnames (yet), but what with the SimpleNames ??? and this in respect of DNA phase V ? Regards, Dominique.
6372.5		AZUR::DURIF		`Mon Sep 11 1995 14:46`	36
	Hi Dominique, > QUESTION 1: > Why can I , under these circumstances, do > sho node rpl109 csma sta C* all id > or sho node rpl109 csma sta c* all id > and in both cases receive the result: > > Node bc:.rpl109 CSMA-CD station csmacd-0 > AT 1995-09-04-11:21:58.477 Identifiers > > Examination of attributes shows: > > Name = csmacd-0 In my understanding the SRM documents how routines mcc_* work not how directives such as show work. Do you expect an output such as Csmacd-0 ? What happens is that an entity identifies itself. Even if you enter a command with C* an agent may know about an entity with csmacd-0 name. The Access Module returns the name known by the agent not the name used to make the request. > QUESTION 2: My advice is to use a simple name (or full name when applicable) to name object. Simple names use a rectricted character set. Character such as comma may not be used. Using a string datype for names will certainly be ok but you may face some problems if special characters are entered. Regards, Benoit