[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

1997.0. "Bug in help; and how to register PhIV node?" by TAEC::HARPER (John Harper, DTN 830 3647) Thu Dec 26 1991 13:00

    I got the following error:
    
    pid 4378 (mcc_fcl_pm) was killed on an unaligned access, at pc 0x55f374
    Bus error
    
    when executing
    
    help entity phase node4 char
    
    just as it was about to enumerate the subtopics.
    
    Just thought someone might be interested. (To forestall an anticipated
    response: no, I don't plan to QAR it. I don't know how, and I'm
    not about to try and find out. But if anyone's interested in taking
    a look, fine by me, and if not, that's fine by me too).
    
    Actually I was trying to find out how to register a Phase IV node,
    but it has now defied all my efforts and I give up.
    
    (The obvious command, "register node4 osi address 1.148", fails
    with some cryptic error message; although the command itself
    seems acceptable, unlike say "register node4 osi address mumble").
    
    Actual scenario:
    
    MCC> register node4 osi address 1.148
    
    Node4 LOCAL_NS:.osi
    AT 1991-12-26-15:52:05.520Iinf
    
    The requested operation cannot be completed
                          MCC Routine Error = %MCC-E-INV_IN_P, invalid
    argument or
                                              attribute
    
    
T.RTitleUserPersonal
Name
DateLines
1997.1TOOK::SWISTJim Swist LKG2-2/T2 DTN 226-7102Thu Dec 26 1991 14:477
    register node4 <fullname>, synonym=<phase4name>
    
    in your case, fullname of .osi is probably adequate.
    
    The error message you got is horrid.   It should be fixed.
    
    
1997.2QAR 2054TOOK::MINTZErik Mintz, DECmcc DevelopmentTue Jan 07 1992 11:272
entered as QAR 2054 in mcc_internal

1997.3qar 2117 on registration messageTOOK::CALLANDERMCC = My Constant CompanionTue Jan 14 1992 10:316
    RE: .1
    
    qar 2117 has been entered against registration for the error
    message.
    
    
1997.4<try this>TOOK::JESURAJTue Jan 14 1992 17:2823
    
    Refer .0:
    
>    MCC> register node4 osi address 1.148
    
>    Node4 LOCAL_NS:.osi
>    AT 1991-12-26-15:52:05.520Iinf
>    
>    The requested operation cannot be completed
>                          MCC Routine Error = %MCC-E-INV_IN_P, invalid
 >   argument or
>                                              attribute
    
    This is a bug !! DNA4 team is  working on it. Will be fixed by SSB.
    
    The following command should work ok !!
    
       MCC> register node4 .osi, syn osi, address 1.148
              
    
    /Jesuraj
       
    
1997.5Not quite... @$@#$#@ commas!TAEC::HARPERJohn Harper, DTN 830 3647Wed Jan 15 1992 06:5121
    Not quite...
    
    MCC> register node4 .osi, syn osi, address 1.148
    %MCC-W-QUALUNKNOWN, qualifier is unknown: SYN
    
    You may think I'm being picky, but (cf my note on commas) these commas
    are a real pain in the neck, and if the implementors can't remember
    where to put them, why should anyone else be able to!
    
    In fact this case is particularly baffling, comma-wise.  The version
    that works is:
    
    MCC> register node4 .osi syn osi, address 1.148
    
    Node4 LOCAL_NS:.osi
    AT 1992-01-15-09:50:06.184Iinf
    
    yet I thought address was an attribute and not a qualifier???
    
    	John
    
1997.6comma after entity only before qualifiersTOOK::CALLANDERMCC = My Constant CompanionFri Jan 17 1992 13:3711
    the comma after the entity is not allowed *UNLESS* the next item 
    entered is a qualifier -- therefore your error.
    
    I will take a look at making that comma optionally allowed between
    entities and arguments as well. That error is probably the number
    one error that is reported against commas. It doesn't solve your
    question/concerns on commas but it should help alleviate some of the
    problems users are encountering.
    
    jill