[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

2079.0. "Is EXPORTER case sensitive ?" by ANNECY::BONNIER (Jean-Luc ... EIC/T&N Annecy France) Mon Jan 13 1992 07:57

It seems that the Exporter FM is case sensitive for the Routing Circuit
instance name.
Example:

$ manage/enterprise
DECmcc (T1.2.3)

EXPORT NODE DSP_NS:.AEO528 ROUTING CIRCUIT CIRCUIT-1 END TIME = 13-JAN-1992 17:0
0:00 ,EXPORT PERIOD = 01:00:00.0 ,EXPORT TARGET = NSDP$ROOT:[NSDP_REPORT.T4.WORK
]NSDPRN_EXPORT.RDB

Node DSP_NS:.AEO528 Routing Circuit CIRCUIT-1
AT 10-JAN-1992 14:43:02

Can not reach the specified entity


If we specify "circuit-1" in lowercase, it works fine.

Is it a known problem ? Fixed for BMS 1.2 SSB ?

Thanks in advance.
Jean-Luc
T.RTitleUserPersonal
Name
DateLines
2079.1No, check DNA5_AMTOOK::SHMUYLOVICHMon Jan 13 1992 11:2919


	When Export command is entered the Exporter FM makes an MCC_call
  to the specified entity (verb = Show, partition = Identifiers).
	If this call is not successful it returns a specialized exception
  "Can not reach the specified entity".

	So I believe that the problem described in .0 exists in DNA5_AM.

	To verify this would you, please, specify the following commands:

	1. SHOW NODE DSP_NS:.AEO528 ROUTING CIRCUIT CIRCUIT-1

	2. NODE DSP_NS:.AEO528 ROUTING CIRCUIT circuit-1


	Sam S.
    
2079.2historian also??FACVAX::WOODCOCKMon Jan 13 1992 12:0210
re .1

While we're on the subject of case sensitivity I have noticed that
PA commands calling historian are still case sensitive for T1.2.4.
The PA commands have to be issued in the exact case the entity was
registered (or so it appears for SNMP). I thought this restriction 
was to be lifted for V1.2???    

regards,
brad...
2079.3DNA5_AM case sensitive ?ANNECY::BONNIERJean-Luc ... EIC/T&N Annecy FranceWed Jan 15 1992 05:4030
re .1

Sam, you are right ... The DNA5_AM is case sensitive.

Example:
MCC> show node aeo415 routing circuit circuit-1 =================> SUCCESS
Using default ALL IDENTIFIERS

Node DSP_NS:.aeo415 Routing Circuit circuit-1
AT 15-JAN-1992 09:34:08 Identifiers

Examination of attributes shows:
                                   Name = circuit-1

MCC> show node aeo415 routing circuit CIRCUIT-1 ==================> FAILURE
Using default ALL IDENTIFIERS

Node DSP_NS:.aeo415 Routing Circuit CIRCUIT-1
AT 15-JAN-1992 09:34:16 Identifiers

No such entity: Node DSP_NS:.aeo415 Routing Circuit CIRCUIT-1
                         Unknown Entity = Node DSP_NS:.aeo415 Routing Circuit
                                          CIRCUIT-1



Is it a known problem in the DECnet/OSI AM development team ?
Fixed for BMS V1.2 ?

Thx. Jean-Luc
2079.4RE: .2 :see 2110.2TOOK::SHMUYLOVICHThu Jan 16 1992 17:581