Conference azur::mcc

	RE: .0  
    >1. With V1.1 ALL attribute partitions of an entity-specification are exported 
>   at a time. Is it also true with V1.2 ? Will it be possible to export only
>   specific attributes ?

	In V1.2 the Exporter FM works on per entity basis (e.g all attribute
    partitions are exported in one request). We have no current plans to convert
    exporting requests to partition basis. This is the second time during last
    month when I'm answering this question so it goes to our "investigation"
    list. If it turns out that it's more useful to have an exporting request 
    per each partition we will modify the Exporter FM in the future version.

>2. privilege problem :
>	:
>	:
>   Which privilege/protection to be set for exporting from the NSDP account ?   

	The account you run MCC and submit the background process must have
    the following privileges(this is described in release notes for V1.1):

	a. read/write to files MCC_MIR_DIRECTORY.DAT and MCC_MIR_ATTRIBUTE.DAT;
	b. create files in the MCC_COMMON directory.	

>3. What are the possible "Exporting State" ? (ACTIVE, SUSPENDED and ?)
>   I would be interested to have a state-transition table.
>   When and under which conditions the exporting state is changing ?
>
>   For example, if end time is 17:00, the last poll is done at 17:00 and
>   the exporting state becomes SUSPENDED at 18:00 if we defaulted the 
>   export period to 1 hour.

	The "Exporting State" has two values: ACTIVE and SUSPENDED.

	The ACTIVE state means that exporting request is in progress or
	is waiting for Begin Time.

	The Create Exporting directive assigns state as ACTIVE. It is switched
        to SUSPENDED under the following conditions:

		a. by Suspend Exporting directive;

		b. by reaching the End Time;

		c. by detecting the fact that entity whose attributes are exported
		   has been deregistered;

		d. by detecting the fact that entity whose attributes are exported
		   is not reachable more that 1000 times in a raw.

	A SUSPENDED state is switched to an ACTIVE by Resume Exporting directive.

	If End Time is 17:00 and Export Period is 1 hour the Export State becomes
        SUSPENDED at about 18:00 for V1.1 and shortly after 17:00 in V1.2.

	This difference is due to the different ways how Exporter FM handles 
	statistics attribute partition in V1.1 and V1.2.
	In V1.1 one relation in the database contains all attribute partitions 
	from the same poll. For example, at 17:00 Exporter calls to Show Identifiers,
	after this is done it calls to Show Status and so on. The last partition  
	to call is Statistics. The duration for statistics is calculated as close
	as possible to the specified export period (we have to keep in mind that 
	response from Show Statistics must come before the time of the next poll). 
	If export period is one hour the response from Show Statistics is received 
	at about 18:00. At this time all required data are ready to be written into
	the database and Exporter FM is ready to the next poll. This is a time when 
	Exporter FM checks if it reaches the End Time.
	In V1.2 one relation in the database contains all attributes except 
	Statistics from one poll and Statistics from the previous poll.
	It allows data to be ready shortly after calling to Show Identifiers
	and Exporter FM does not need to wait for Statistics.

	
>4. I need to know when a exporting job has completed.
>   Of course I can poll testing the end time but not very clever.
>   Is there any mechanism to notify the user of job completion ?

	If exporting request is suspended because an entity has been deregistered
	or is not reachable Exporter FM generates an event Operation Stopped.
	One of the arguments of this event is entity whose exporting operation is 
	stopped.

    
	I hope this answers will help you.

	Regards, Sam