[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

1103.0. "unexpected info" by DGOSW0::GUESDON () Thu Jun 06 1991 10:08

    Another problem with the record type attributes:
    
    We have created a subentity with 55 attributes of type record.
    
    When we try to access them with the "SHOW" command within the FCL PM,
    everything works perfectly, but when we try to do the same with the
    ICONIC MAP PM, we have the message:
    
    	Unexpected Information was returned in out_p: code xxxx
    
    Where xxxx is the id code of the record attribute.
    
    Can you help us ?

T.R	Title	User	Date	Lines
1103.1		VERNA::V_GILBERT	`Thu Jun 06 1991 11:21`	14
	Unexpected Information was returned in out_p generally means that your Management Specification has some variant information incorrectly set up and for the attribute group for which the operation is being done, the depends on clause does not specify the code xxxx being returned in this case. This message is never returned by the FCL because they do not look at the variant information; they simply decode out_p. The Iconic Map creates a form with those attributes it expects to have returned; if any are not returned, the text value is --NOT RETURNED and if extra information is returned, the above message is displayed. Hope this helps. Verna
1103.2	We don't use variant records	DGOSW0::GUESDON	`Wed Jun 12 1991 04:37`	4
	Thank you for your help. I understand now the difference between the FCL an ICONIC PMs. But we're not using variant records at all in our AM. The records have all the same format (fixed). Do you have an idea in this context ?
1103.3	Variant entity not variant record	VERNA::V_GILBERT	`Wed Jun 12 1991 11:18`	6
	Variants in this case does not refer to variant records but rather variants of a particular entity class. The management specification definition DEPENDS ON contains conditions which are evaluated to see if a particular instance belongs to a specific variant of the entity class. Verna
1103.4	We don't use DEPENDS ON	DGOSW0::GUESDON	`Mon Jun 17 1991 11:17`	3
	We don't use at all the DEPENDS ON clause in our MSL... Michel.
1103.5		VERNA::V_GILBERT	`Mon Jun 17 1991 15:51`	10
	If you are not using variants at all, then the unexpected info: code xxx can refer to an inconsistency between what the MS defines as being the attributes in a particular partition and what the AM thinks are in the partition. Find the code which is displayed as having the unexpected info and see if the partition to which it is defined in the MS is the one on which you are doing a show. If not, there is your discrepancy. Verna