Conference azur::mcc

5596.0. "BMS V1.3 and CENSUS V1.0 problem?" by CSC32::W_MCGAW () Thu Sep 16 1993 19:12

    Hi,
    
    I have a customer running DECmcc-BMS V1.3 and Polycenter System Census
    V1.0.  If he enters forms mode of DECmcc and then issues a 
    
    show node <name> census 
    
    followed by a space and the PF2 key for a list of options, he gets back
    a list of valid entities that looks like the following.
    
        SERVER *
        MACHINE GROUP
    ERROR: no matching string for Entity 3
        PEER *
        NETWORK *
        PROCESSOR *
        MEMORY
        ADAPTER *
        CONTROLLER *
        PRINTER *
    ERROR: no matching string for Entity 12
        DISK PARTITION *
        TAPE *
        QUEUE *
        SOFTWARE GROUP *
    ERROR: no matching string for Entity 17
        USER GROUP *
    ERROR: no matching string for Entity 19
        LICENSE *
        FILESYSTEM *
        MOUNT INFORMATION *
    
    If we use DAP to look at class node subclass census, we see the
    entities that are showing errors in the above display.  In order, they
    are MACHINE, DISK, USER and SOFTWARE.  Can anyone explain if this is a
    problem or not and why it is occurring?
    
    Thanks,
    Walt

I assume there is a parser conflict because of names that are substrings
of other names (MACHINE vs. MACHINE GROUP, DISK vs. DISK PARTITION, 
SOFTWARE vs. SOFTWARE GROUP, USER vs. USER GROUP).

I doubt that it is legal to define subclass names like this, i.e. the
Systen Census people would have to change their naming. You could try to
hack the dictionary to change the presentation names of the subclasses
in question. 

*Robert

    Robert is correct. This management spec should never have made
    it through the registry process, or was never submitted.