[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

931.0. "MCC-E-ILVTNF during Event Monitor Setup" by GOYA::MERINO (Angel Garc�a Merino - ACT ENS Spain) Wed Apr 17 1991 15:57

Trying to setup DECmcc as a DECnet Event Monitor with the command procedure 
SYS$STARTUP:MCC_STARTUP_DNA4_EVL.COM I get the following message:

%MCC-E-ILVTNF,  specified tag not found within current constructor 

and I do not get the NCP object MCC_DNA4_EVL and its associated process
MCC_DNA4_EVL.
I am running the DECmcc BMS V1.1 SSB
=============================================================================
Procedure verify output follows:
$ @SYS$STARTUP:MCC_STARTUP_DNA4_EVL.COM

$! 	This command file can be envoked from mcc_startup_dir.com.  It is
$! commented out in the MCC_STARTUP_DIR.COM. To run it on system
$! startup, update the MCC_STARTUP_DIR.COM file to execute the statement:
$!	@SYS$STARTUP:MCC_STARTUP_DNA4_EVL.COM
	.
	.
	.
$ manage/enterprise
DECmcc (V1.1.0)
	.
	.
	.
SET node4 lince local sink MONITOR name = MCC_DNA4_EVL

Node4 63.167 Local Sink Monitor 
AT 17-APR-1991 20:47:18 Characteristics

Internal error in DECnet Phase IV AM.
                              MCC Error = %MCC-E-ILVTNF,  specified tag not 
                                          found within current constructor 
	�
	�
	�
exit
T.RTitleUserPersonal
Name		DateLines
931.1Looks like dictionary messed up by SNMP_AM installationTOOK::CAREYWed Apr 17 1991 18:5936
    
    I think you have encountered the soon to be famous SNMP-AM-in-the-dictionary
    problem!
    
    Have you installed the SNMP AM recently?
    
    The only time I have seen this error from DECnet Phase IV is after 
    SNMP has been added to the dictionary.
    
    Some arguments to directives are universal, and SNMP was setting them
    to a value different than DECnet expected.  DECnet does careful request
    validation, and the argument to the SET directive is coming in with the
    wrong value.  We reject it early, hoping to keep anything really
    serious from going on.
    
    You will find that all SET requests to DECnet Node4 entities fail.
    
    Check the release notes from the SSB kit that you have installed.  They
    contain directions for cleaning up the dictionary and rebuilding the
    parse tables.  Once you do that, you'll find that this error no longer
    occurs.
    
    There is a note in this notes file about someone else encountering this
    problem as well....  Which note?  I'll have to look around.
    
    If you haven't installed the SNMP_AM for managing TCP/IP, then let us
    know immediately.  We'll have to try to find out what is happening.
    
    If you do have the SNMP AM installed, then check the release notes,
    correct the dictionary, and you'll be up and running in short order.
    
    -Jim Carey
931.2See note 755 for more details.TOOK::CAREYWed Apr 17 1991 19:361