Conference azur::mcc

2056.0. "Wildcard entity names for historian?" by TAEC::HARPER (John Harper, DTN 830 3647) Thu Jan 09 1992 11:49

    Is it supposed to be possible to start recording for a wildcarded
    entity? I can't find anywhere that says you can or can't, but I thought
    I'd try it anywhere, with the following result:
    
    MCC> record node4 paela circuit * partition counters, begin time 17:30,
    poll pe
    riod 5:0, in domain .blah
    
    Node4 51.1006 Circuit ETHERNET
    AT 1992-01-09-16:44:51.547Iinf
    
    Recording of "Counters" partition started
    
    
    Node4 51.1006 Circuit ETHERNET
    AT 1992-01-09-16:44:57.973Iinf
    
    Entity or Historian FM does not support the specified partition
    
    
    But I can make it work by specifying the circuits (there are two,
    ETHERNET and SYN-0) explicitly.  The command above starts recording
    just for ETHERNET:
    
    MCC> show recording node4 paela circuit * partition counters, in domain
    .blah
    
    Node4 paela Circuit ETHERNET
    AT 1992-01-09-16:45:34.078Iinf
    
    Recording parameters for the partition "Counters" :
                            Recording state = ACTIVE,
                                State since = 1992-01-09-16:44:56.894Iinf,
                             Polling period = +0-00:05:00.000Iinf,
                                 Begin time = 1992-01-09-17:30:00.000Iinf,
                                   End time = 2012-05-25-00:00:00.000Iinf,
                                   Keep age = +45-00:00:00.000Iinf,
                               Request time = 1992-01-09-16:44:51.547Iinf,
                               Requested by = "harper",
               Time of last successful poll = "NONE",
                 Number of successful polls = 0,
                   Time of last failed poll = "NONE",
                   Last poll failure reason = "N/A",
                     Number of failed polls = 0,
            Last historical expiration time = "NONE",
            Time of last expiration failure = "NONE",
             Last expiration failure reason = "N/A",
              Number of expiration failures = 0
    
    
    Is this a bug or a user expectation-error?
    
    (I'm using T1.2.4 on Ultrix).
    
    	John
    

	Thank you for pointing to this problem. This is a bug.

   The corresponding QAR is entered agains Historian.
   It will be fixed during FT.

  Sam Shmuylovich