Conference azur::mcc

	RE: .1

	Parse table you are using does not include information about 
	export directive and node4 area entity.

	Please, check if new parse table has a right protection.
	Does MCC_SYSTEM points to DKB0:[MCC]?

	The next thing to check is your data dictionary. To be sure that
	your data dictionary  is augmented by Exporter's directives for 
	node4 area entity, please, do the following:

		DAP> show class node4 subclass area 

	
	If under node4 area there are no Export directive you should check
	the mcc_exp_node4.com file.

	BTW:

>    MCC> export node4 phx25 area * begin time 8-nov-1991:18:00 end time
>    11-nov-1991:10:00 export periond 00:15:00 export target 
>    MCC_REPORTS_FILES:TEST.RDB sequence name "PHX25 areas"
>    %MCC-W-ARGUNKNOWN, unknown argument AREA

	1. I assume that you used a comma between arguments.

	2. From the text of your note it looks to me as a Past
	   Time exporting request. In this case "in domain" must be
	   specified.

	3. If I'm wrong and this is a future time exporting request
	   be sure that MCC_REPORTS_FILES logical is defined for the
	   background process.


	Sam
    

    
    Hi,
    
    I wish any of the above were the case.  O.K. you are right, I did not
    include the commas, equals or anything...(call me Mister Syntax).
    
    when I do a circuit dump:
    
    MCC> export node4 phx25 circ * begin time=7-nov-1991:18:00:00,end
    time=11-nov-1991:10:00:00, export period=00:15:00,export
    target=mcc_report_files:test.rdb, in domain upper_merion
    
    Node4 1.20 Circuit *
    AT 12-NOV-1991 15:42:01
    
    The requested operation cannot be completed
                          MCC Routine Error = %MCC-S-NORMAL, normal
    successful
                                              completion,
                      Entity Existence Info = Entity Existence Cannot
    Be Determined
    

    Well this validates the syntax, I apparently was not recording on
    circuits for during the area test.    

    now with the area:
    
    MCC> export node4 phx25 area 5 begin time=7-nov-1991:18:00:00,end
    time=11-nov-1991:10:00:00, export period=00:15:00,export
    target=mcc_report_files:test.rdb, in domain upper_merion
    %MCC-W-ARGUNKNOWN, unknown argument AREA
    
    same thing.  Here is the DAP dump
    
       Class (1) : NODE4
    ---> Subclass (2) : AREA
           Definition (3) : PRESENTATION_NAME
           Definition (3) : INSTANCE_REQUIRED
           Definition (3) : DYNAMIC
           Definition (3) : INSTANCE_DATATYPE
           Attribute (5) : CIRCUIT 5
           Attribute (5) : COST 3
           Attribute (5) : HOPS 4
           Attribute (5) : IMPLEMENTATIONDESC 301
           Attribute (5) : LOCATION 300
           Attribute (5) : MAILACCOUNT 304
           Attribute (5) : NEXTNODE 6
           Attribute (5) : NEXTNODEADDRESS 7
           Attribute (5) : NEXTNODENAME 8
           Attribute (5) : NUMBER 1
           Attribute (5) : PHONENUMBER 303
           Attribute (5) : REMARKS 305
           Attribute (5) : RESPONSIBLEPERSON 302
           Attribute (5) : STATE 2
           Attribute (5) : TEXTFILE 306
           Directive (6) : DELETEEXPORTING 118
           Directive (6) : DELETERECORDING 111
           Directive (6) : DEREGISTER 30
    	   Directive (6) : DIRECTORY 26
           Directive (6) : ERASE 33
*          Directive (6) : EXPORT 113
           Directive (6) : GETEVENT 65
*          Directive (6) : MODIFYEXPORTING 115
*          Directive (6) : MODIFYRECORDING 108
           Directive (6) : PURGE 38
           Directive (6) : RECORD 106
           Directive (6) : REGISTER 29
*          Directive (6) : RESUMEEXPORTING 117
*          Directive (6) : RESUMERECORDING 110
           Directive (6) : SET 2
           Directive (6) : SHOW 1
*          Directive (6) : SHOWEXPORTING 114
*          Directive (6) : SHOWRECORDING 107
*          Directive (6) : SUSPENDEXPORTING 116
*          Directive (6) : SUSPENDRECORDING 109
           Event (10) : AREAREACHABILITYCHANGE 417
           Attribute_Partition (11) : IDENTIFIERS 1
           Attribute_Partition (11) : REFERENCES 5
           Attribute_Partition (11) : STATUS 2
           Event_Partition (13) : CONFIGURATION 15
    
    I assume where I have astericked (?) indicates that the directives
    have been placed in the parse tables.  The file protections are
    fine.
    
    What should I check next?
    
    Regards and thanks,
    
    Dave Comfort

    
    Is anyone looking at this or can give me additional guidance?
    
    Dave

    Actually, most developers are flat out getting V1.2 to field test so
    are not free to read the notes file very often.
    
    In any case, let me ask a dumb question... Are you referring to
    the entity in EXACTLY the same case as it was registered? This case
    restriciton is documented in the release notes.
    
    s/rob

    
    hi,
    
    sorry, I don't mean to be a pain.  At any rate I tried both cases
    and no luck.  Additionally, the same restriction is documented for
    the historian and it's working fine.  I also tried spelling out
    the full name, ie. .dna_node.phx25 in both upper and lower case,
    same result...
    
    %MCC-W-ARGUNKNOWN, unknown argument AREA
    
    but as in .2, the verb seems to be there.
    
    Dave Comfort

    Rob didn't mean upper OR lower case, he meant in the exact same
    case (which may be a combination of upper and lower case) as it
    is  registered. To find this out, the quickest method is to do
    a show all reference on the entity, the entity listed in the header
    should give you the correct info.
    
    I will have to reread the previous note again, but make sure that your
    start time for the exporting is in the past, and for starters put the
    end time also in the past by specifying a duration less than the length
    of time between the start time and NOW. Then see what happens.
    
    jill