[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

1227.0. "BUG: Can't do DIRECTORY of subentities from IMPM" by TOOK::MCPHERSON (i'm only 5 foot one...) Wed Jul 10 1991 11:09

    There is a problem with performing a DIRECTORY on a sub-entity on the
    Iconic Map.  I understand that this problem has already been discovered
    by the developers, but I figured I would go ahead and post this
    information here in the interest of:	
    	1) saving other users' time in tracking down the problem, scratching
           their heads and putting a note in here, 	
        2) saving the developers' time from replying here saying
           that it was a known problem and would be fixed.

    /doug

Problem:

    I have discovered that performing a "DIRECTORY" operation on a Translan
    LINE from the Iconic Map PM causes DECmcc to return with an MCC
    "Unhandled Service Reply" and the message "MCC-F-FATAL, Fatal DECmcc
    error".    On further investigation,  it turns out that the problem was
    consistent for *all* sub-entities of registered global entities,
    regardless of class.

    Issuing the equivalent directive from the FCL interface seems to work,
    although this is not _entirely_ true, as described below.

Cause:

    The DIRECTORY directive dispatches to the Registration FM.   The
    Registration FM has a bug in it that causes it to not properly process
    the "IN DOMAIN" qualifier. (This seems to be where the problems are
    coming from.)   By virtue of the way the Iconic Map PM is designed
    (i.e. each map represents a domain view), it always appends
    (transparently) the "IN DOMAIN" qualifier to all directives, based on
    the current map (domain) that is open.   The FCL PM is not
    "domain-based". I.e. when you are issuing commands from the FCL you are
    not *required* to specify  which domain contains the entity you are
    operating on.  

    If, from the FCL PM, you do NOT specify an "IN DOMAIN" qualifier for
    the sub-entity you are doing the DIRECTORY of, you will get back the
    appropriate response (depending on whether or not the  subentity and
    it's parent have been registered).    If you DO  add the ",IN DOMAIN
    <domain_name>" to the command, you will get the same error as the one
    in the Iconic Map PM.

Solution:

    This bug is known and I understand it will be fixed in the V1.2 release
    of the DECmcc Director.  Until then (or unless a patch is issued) , it
    will remain a restriction that users can neither perform a "DIRECTORY"
    operation on sub-entities using the Iconic Map PM nor can they use the
    "IN DOMAIN" qualifier when performing a DIRECTORY operation on
    sub-entities from the FCL PM.


Sample output of the problem (using the FCL interface):

  MCC>                                   ! Note that this is NOT using the  
  MCC> DIR TRANSLAN MADGE_335 LINE 2     ! IN DOMAIN qualifier.

  TRANSLAN KAJUN_NS:.madge_335 LINE 2
  AT 10-JUL-1991 09:32:37

  Directory successful.
                              Port Number = 2



  MCC>                                  !Now,  using IN DOMAIN qualifier:
  MCC>
  MCC> DIR TRANSLAN MADGE_335 LINE 2, IN DOMAIN WALLY_WORLD
  
  TRANSLAN KAJUN_NS:.madge_335 LINE 2
  AT 10-JUL-1991 09:32:46

  The requested operation cannot be completed
              MCC Unhandled Service Reply = The requested operation cannot be
                                            completed
                        MCC Routine Error = %MCC-F-FATAL, fatal DECmcc error
  MCC> 
T.RTitleUserPersonal
Name
DateLines
1227.1MCC_INTERNAL QAR#766CHRISB::BRIENENDECmcc Bridge|Station|SNMP Management.Thu Jul 11 1991 09:480