Conference azur::mcc

    Here is some things I forgot, I am exporting (recording is working
    fine). I am trying to export future data for the node, it's circuits
    and it's lines. The image which crashed was MCC_EXPORTER_FM_BG.EXE.
    
    Dave.
    

    

   Dave,
 
   As I understood from 644.1 all your questions are about Exporter not
   Historian. Am I right? Anyway I'll try to answer these questions for
   both Historian and Exporter.

>    1. Does one need to use the IN DOMAIN qualifier to start recording ?

	IN DOMAIN qualifier is required for ALL directives of the Historian FM.

	For Exporter you have to specify IN DOMAIN qualifier ONLY IF you
	want to export historical data previously recorded using Historian.

>    2. If you want to record node, cir and line characterisitics do you
>    need to start an export job for the node, each line and each circuit ?

        Historian  works on per entity per attribute partition basis.
	Therefore you have to specify record request for EACH ENTITY and
	EACH ATTRIBUTE PARTITION you are interested in.

	Exporter works on per entity basis( it means that you CAN NOT export
	any particular partition, you can export only ALL attribute partitions)
	Using Exporter you have to specify export request for EACH ENTITY.

	
>    3. If I do start a job for a line, then the background job crashes
>    with an access violation.

     It's difficult to say what is wrong. Would you,please, send me
     (TOOK::SHMUYLOVICH) a mcc log file and background process log file. 
     I hope it will give some ideas.

     As the first step I can recommend to do SHOW  LINE for all attribute partitions,
     including statistics.

	Sam

    
    Thanks for your help, my understanding is getting better, but it still
    isn't working for me.
    
    1. If exporting is on an entity basis, why does it let me do an 
    export node4 wlort2 line ethernet if I am already doing an export node4
    wlort2 ? It is the export node4 wlort2 line ethernet which causes the
    access violation.
    
    2. If I do a :
    MCC> EXPORT NODE4 WLORT2 BEGIN TIME 23-JAN-1991:01:00:00, END -
    _MCC> TIME 23-JAN-1991:07:00:00, IN DOMAIN ESP
      at 9 am on the 23rd, then it goes away, starts a subprocess,
    and then hangs forever.
    
    3. I have got some data exporting , I recorded the node counters
    (future), I exported (future) and it worked. I then added recording
    the line and circuit counters, restarted the exporting, but it still
    only exported the node counters.
    
    I must be doing something pretty silly, but can't work it out. Can you
    help ?
    

    
     RE: .3

>    1. If exporting is on an entity basis, why does it let me do an 
>    export node4 wlort2 line ethernet if I am already doing an export node4
>    wlort2 ?
     
      "node4 xxx line yyy" and "node4 xxx" are different entities.

>    2. If I do a :
>    MCC> EXPORT NODE4 WLORT2 BEGIN TIME 23-JAN-1991:01:00:00, END -
>    _MCC> TIME 23-JAN-1991:07:00:00, IN DOMAIN ESP
>      at 9 am on the 23rd, then it goes away, starts a subprocess,
>    and then hangs forever.

     Let's look one more time at the interprocess communication in the
     Exporter FM.
     First, you have to start background process in the bach. In the beginning
     it starts child subprocess which is waiting for data to write them in the
     RDB file. If there is no an active exporting requests for the specified 
     RDB file, the background process just wait for such request(e.g. until
     you specify Export directive in the foreground process).
     Both background process and its child will run forever.
     
>    3. I have got some data exporting , I recorded the node counters
>    (future), I exported (future) and it worked. I then added recording
>    the line and circuit counters, restarted the exporting, but it still
>    only exported the node counters.
 
     I'm a little confused:

       - future exporting are NOT related to recording at all!

       - you can not export only one attribute partition for specified entity
         (in the Export directive there is no way to specify which attribute
	  partition you want to export). The only reason for having in the 
	  RDB file only counters is that Show directive for others partitions
	  fails.

       - I noted above that "node4 xxx" and "node4 xxx line yyy" are different entities.    
         So if you need to export data for "node4 xxx" you have to execute Export
	 directive for "node4 xxx". If you want to export data for "node4 xxx line yyy",
	 please, do the same for "node4 xxx line yyy".


     About accvio.
     One of the possible reasons for this is your MIR files from previuos version of MCC.
     To check this, please, try to use a new RDB file name.

	Sam

    I believe I understand what's been discussed here, but I have a
    related question.
    
    (using Iconic map)
    I open a domain, select a node4 entity, then select one of its 
    circuits. I now select the export function, give it the target
    name and other parameters, click on OK, and exporting begins.
    
    If at some point later I select show_exporting on this same entity,
    I get a message telling me that the IN DOMAIN is an insupported
    qualifier ID. I assume that the in domain qualifier (using the Iconic
    Map anyways) must somehow be implied, because I don't see any way
    of selecting that (or deselecting it for that matter).
    
    Of course with the FCL you have the option of including the In Domain
    qualifier, and I can succesfully show exporting with this PM.
    
    Am I missing something in terms of how to accomplish this with the
    Iconic Map or is there something else to this?
    
    BTW, I'm glad I read what was said in .2.
    
    
    Steve

    Please disregard my note .5. Shortly after entering my question
    I read note 621.1 and found my answer. 
    
    Steve

    
    I am having a new problem now.
    
    I am exporting future node information fine.
    I also started exported some line inforation and that worked ok.
    I then started exporting some circuit information.
    
    This is all from the same node (DEMSA).
    
    The circuit export command went ok, I set the duratin to 10 minutes.
    After abouit 15 minutes I have a look and it state has been changed to
    SUSPENDED by the system. The node and line are still ACTIVE.
    There are no poll failes or export fails.
    
    Why does this happen ? 
    
    Also are there any guidelines as to whether one should use the
    historian for data collection and then say run an export job once a
    day, or do what I am doing, exporting directly every 10 minutes without
    using the historian at all? ( I am trying to generate some daily DECnet
    reports).
    
    Thanks for any help
    
    Dave McCallum.
    

    RE: .07

>    The circuit export command went ok, I set the duratin to 10 minutes.
>    After abouit 15 minutes I have a look and it state has been changed to
>    SUSPENDED by the system. The node and line are still ACTIVE.
>    There are no poll failes or export fails.
>    
>    Why does this happen ? 
 
     The most common known problem in such situation is not right version
     of the data dictionary. To check this you can specify from Icon Map SHOW 
     directive for all attribute partitions for the named entity.
     If there is a difference between information returned by Show and
     information in the dictionary you will see the corresponding messages.
     ( Please, use Icon Map because FSL does not catch such situation.)

>    Also are there any guidelines as to whether one should use the
>    historian for data collection and then say run an export job once a
>    day, or do what I am doing, exporting directly every 10 minutes without
>    using the historian at all? ( I am trying to generate some daily DECnet
>    reports).

     It's up to the user which policy to chose. From my point of view I prefer
     to use Exporter directly. 
     The major difference between Historian and Exporter is an access to the
     collected data. Historian stores data INSIDE MCC and the user is able to 
     get them only by using SHOW directive, e.g these data are available ONLY 
     inside MCC. Exporter writes data in RDB file (OUTSIDE of MCC) and they 
     are accessible using RDB tools. 
     Now assume that the user wants to have the same data in both places: 
     inside MCC and in the RDB. I prefer to set up both recordings and 
     exportings because they run in background and automatically restart in
     such situation as system reboot (past time export runs in foreground so
     after specifying past time export request you have to wait until it
     completes; how long it takes depend on the amount of data you asked to
     export).
     I think that past time export is good to use when you need to generate 
     a reports for past time and the corresponding data are not in RDB. 
     But again, this my opinion the user is free to choose his own policy.

	Sam