Conference azur::mcc

2429.0. "DECnetIV AM and OBJECT Process Id DATAtype" by ZTOIS1::VISTA (Renato VISTA, SIS Strasbourg, France) Wed Feb 26 1992 14:24

    
    Hello,
    
    I'm working on both DECmcc/VMS V1.1.
    I want to follow throught DECnet IV AM the behavior of specific DECnet
    objects which are associated to a VMS process with a Process Id
    attribute (like PATHwork processes, for example...).
    
    If I use the FCL show command, I can obtain the Process ID attibutes.
    BUT, If I try to create an rule, ALARMS FM doesn't want to support the
    type Process Id (ie OCTET STRING) in the rule expression. Please see
    the following Captured FCL session...
    
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
%MCC-I-SAVEHEADER, DECmcc output region Wed Feb 26 17:15:40 1992
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 



show node4 stras5 obj * Process Id, with process id <> %X00000000

Node4 47.465 Object $IPCACP
AT 26-FEB-1992 17:15:26 Characteristics

                             Process ID = %X2020010E

Node4 47.465 Object SMISERVER
AT 26-FEB-1992 17:15:27 Characteristics

                             Process ID = %X20200110

Node4 47.465 Object REMACP
AT 26-FEB-1992 17:15:28 Characteristics

                             Process ID = %X20200113

Node4 47.465 Object EVL
AT 26-FEB-1992 17:15:28 Characteristics

                             Process ID = %X20200112

Node4 47.465 Object CTERM
AT 26-FEB-1992 17:15:29 Characteristics

                             Process ID = %X20200113

Node4 47.465 Object DNS$TA
AT 26-FEB-1992 17:15:30 Characteristics

                             Process ID = %X20200133

Node4 47.465 Object DNS$BACK
AT 26-FEB-1992 17:15:30 Characteristics

                             Process ID = %X20200134

    
    
    
create mcc 0 alarm rule rule_test expression = (CHANGE_OF(node4 stras5 object
DNS$TA process ID, *,*))

MCC 0 ALARMS RULE rule_test
AT 26-FEB-1992 17:15:34

Data type of the attribute in the alarm expression is currently unsupported.

capture
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
%MCC-I-SAVETRAILER, end of DECmcc output region
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * 
    
    
    I checked on a DECmcc/ULTRIX V1.1 (EFT) if the problem also occurs and
    I obtained the same message.
    
    1) 	Is it a normal case ? Is it a bug ?
    
    2)	I wanted to change the DECmcc dictionary and rebuild th Parse
    	Tables with a Process Id declared as a LATIN STRING. But I couldn't
    manage to do any change without overwritting the NODE4 class and subclasses
    hierarchy. How can I do that operation ? The aim is to be able to write
    an alarm rule with a DATATYPE recognized by the ALARM FM.
    
    
    Thank you for your help !!
    
    Renato
    

    
    
    Hello,
    
    Just a comment : of course, I tested the situation on a EFT DECmcc/ULTRIX
    V1.2 (not V1.1 !!...).
    
    Thank you for your help !
    
    Renato

    Assigned QAR number 02462
    
    s/rob

    
    
    Hello Rob,
    
    Thank you for your reply !
    
    Is it possible to have information about the QAR and about the status
    of the problem (delay? , new version ?, patchs ?)
    
    Regards,
    Renato
    
    PS : a recent note has been opened (note 2695.*) and I've also replied.

    We are discussing problems in unreleased code so I wouldn't expect
    patches or versions to fix things.
    
    The issue will be if the added function of this datatype support will
    be added to the currently under development release or deferred untill
    a later release.
    
    The QAR is a mechanisim to be sure we don't forget to address it.
    
    I believe that a reply to note 2695 has already addressed what is
    likely to be done in the short term.
    
    s/rob