[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

1092.0. "Please elaborate on %MCC-E-INV_IN_Q invalid qualifier" by SUBWAY::YANNIOS (N�MAT NYO8/E2 DTN:352-3197) Tue Jun 04 1991 17:15

    What is wrong with this command?
    
    RECORD  NODE4 .dna_node.52BRTR CIRC * PARTITION = COUNTERS,  POLL
    PERIOD = 00:10, keep age = 14
    %MCC-E-INV_IN_Q, invalid qualifier
    
    
    Thank you.
             
    Nick
T.RTitleUserPersonal
Name
DateLines
1092.1Domain must be specifiedTOOK::SHMUYLOVICHWed Jun 05 1991 10:188
    
    Historian FM works on per domain basis. All Historian directive must
    include IN DOMAIN qualifier. So simple add ", in domain = domain_name"
    to your command. Do not forget to start background process for the same
    domain.
    
    Sam
    
1092.2thanks...SUBWAY::YANNIOSN�MAT NYO8/E2 DTN:352-3197Wed Jun 05 1991 11:488
    Thanks.  Will the historian and the exporter accept wildcards for
    the circuit, line, exec counters partitions?  
    
    Also, as a suggestion, the diagnostic "invalid qualifier" seems
    misleading.  Perhaps it shoud report "missing qualifier ..."
    
    Nick
    
1092.3misuse of inv_inq cvrTOOK::CALLANDERJill Callander DTN 226-5316Wed Jun 05 1991 13:038
The invalid in_q cvr saiys that the in_q passed was an invalid argument. It
was not invalid, instead your module (the historian) required that a specific
value be supplied in in_q. Please note that you should be returning an
exception in this condition and NOT an inv_ cvr. Those cvr's are set as
fatal, currently the PMs are coded around the fact that a number of modules
are using them to signal non fatal conditions. Please change this for V1.2

jill
1092.4Historian/Exporter and wildcardTOOK::SHMUYLOVICHWed Jun 05 1991 15:0524
    

  >   Will the historian and the exporter accept wildcards for
  >  the circuit, line, exec counters partitions?  

	Yes, you can specify wildcard for the subentity instance, for 
     example, RECORD NODE4 rudone LINE * PART = .... or
              EXPORT NODE4 rudone LINE * ....

     In order to expend wildcard Historian and Exporter do 
     SHOW NODE4 rudone LINE * ALL IDENTIFIERS and create recording/exporting
     request for every line instance being returned from this call.
     Did I answer your question?
     BTW, you can specify partition ONLY in Record command( Historian);
     Exporter works on per entity basis and exports ALL partitions.

  >  Also, as a suggestion, the diagnostic "invalid qualifier" seems
  >  misleading.  Perhaps it shoud report "missing qualifier ..."

	I have a QAR against this (thanks to Jill) and it will be corrected 
	in V1.2.

	Sam
    
1092.5SUBWAY::YANNIOSN�MAT NYO8/E2 DTN:352-3197Thu Jun 06 1991 17:383
    Thanks!
    Nick