[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

163.0. "How can I trace down a bug in MCC..." by SMAUG::BELANGER (Quality is not a mistake!) Mon Jul 02 1990 16:02

    
    	I have a prototype AM, which builds an OUT_P. occassionally when I
    return the OUT_P (with a CRV = MCC$_RESPONSE and a handle = FIRST), MCC
    fails with the errors:
    
    	%MCC-E-INVPARAM,  invalid parameter passed
    	%MCC-F-TRM_FAILURE, Fatal MCC Error'
    
    I think there may be a problem in the way I'm building OUT_P but I
    can't seem to see it in my code.  Is there a way to figure out what
    parameter is invalid?  If TRM (FCL) could indicate what it didn't like
    or I could see what TRM was playing with when it failed, would help me
    resolve this problem.  Again, I think its a problem in my code but I
    need to isolate the problem by finding out what TRM does not like.
    
    Thanx,
    
    ~Jon.
T.RTitleUserPersonal
Name		DateLines
163.1more info...SMAUG::BELANGERQuality is not a mistake!Mon Jul 02 1990 18:4821
    
    	Using the logical MCC$TRM_PM set to 8, I get some interesting
    information.  The prototype I'm working on has a global entity with a
    dynamic sub-entity.  This sub-entity has only 2 attributes defined,
    identifier and status.  Within the status attribute group, there are 7
    attributes (the first is an Enumerated type, followed by all
    Latin1Strings).  Two of the attributes have very similar names, one is
    LINE and the other is LINE GROUP (both are Latin1Strings).  Wheen I as
    to display the LINE attribute, I get the text displayed by TRM dump:
    
    	No Such Attribute Partition Exists In The Dictionary
    
    and then the expected output (this only happens the first time
    through).  If I display anyother specific attribute within this
    attribute group, everything works as expected.  If I do an ALL STATUS,
    I get the error described .0.  I looked at the code and I'm doing
    nothing different from any of the other parameters of the same type.
    Have I run across a bug or limitation?  Your help is greatl
    appreciated.
    
    ~Jon.
163.2Can't have ambiguous attribute namesTOOK::STRUTTColin StruttTue Jul 03 1990 20:0012
    I don't know the details of what MCC modules are doing to yours,
    however, there is a problem that you will need to fix. [It may
    or may not be causing the exact problem your are observing.]
    
    You are not allowed to have an attribute called LINE and another called
    LINE GROUP defined for the same class. That violates the name/code
    assignment philosophy (see SRM, section 7.4.3).  If you did this
    yourself during development, then you must fix it; if you already
    registered your attribute names, then "we" have a problem - please
    could you let me know which it is (via mail, preferably).
    
    Colin
163.3SMAUG::BELANGERQuality is not a mistake!Tue Jul 03 1990 20:574
    
    	Dealt with off-line.
    
    ~Jon.