Conference azur::mcc

	Let's start from the bottom:

>    I have about 60 total entities that I'm recording and want to do about
>    10-20 exports... am I seeing a threshold???

	I think you mean "current" exportings (not "past time" when you
	export historical data). These numbers looks OK to me.
	Very important is not only the number of recordings and exportings
	but also polling interval and export period.

	Why are you using 5 different domains for the Historian and 5 
	different databases for the Exporter. It gives additional loading
	on your system.  

>    The problem I'm having, while using the IMPM, is the screen displays
>    the little clock and just hangs...   When I type, SHOW SYSTEM, the
>    process that points to the batch job, running the EXPORTER background
>    process is in an RWMBX state.  It just stays there until I pause and
>    then delete the EXPORT of the "second" DECrouter.

	Are you sure that it "just hangs"? The past time export is a very 
	time consuming operation especially if you recorded not all 
	attribute partitions for a target entity. (If you need more details
	on past time export, please, send me mail TOOK::SHMUYLOVICH).

	The Exporter Background process waits until the the past time 
	export which is done in foreground finishes.


	SAm

    

    Sam,
    	Thanks for your help on this one.  I created one domain,
    RECORDING_DOMAIN, and when I setup the recording(s), I pointed them to
    an alternate disk, DATA$:[RECORDING_DOMAIN].  
    	Things were honkey dorey, for about a day, I moved ALL my
    recordings into the above directory, totaling about 60-70.  I noticed
    at about 60, the batch job dies...  I tried to restart it, and was able
    to setup a couple more recordings and then it died again...  I setup
    another domain, and I for the last 10-15 recordings I used the second
    domain.  
    	I've since rebooted the system, and after coming back, the first
    HISTORIAN_BACKGROUND job was gone.  I restarted it, and it ran ok for a
    couple of minutes and then it dies again...  BTW, I submit the job with
    the /RESTART qualifier...  Any ideas?
    
    /Mic
    

	Mic,

   I think you exceeded system limits. Try to look at the log file. It should 
   be an error message there.

	Sam
    

    		Exporter Question
    
    As the basenote states, I see the EXPORTER Background Batch job go into
    an RWMBX state.  To take this question a step further, I am trying to
    do serveral consecutive EXPORTS, of LANbridge 200 CHILD ENTITIES,
    DECrouter 2000 CHILD ENTITIES, and DECNIS 600 CHILD ENTITIES, 
    approximately 30 total exports, and I see the EXPORTER job go into RWMBX.
    
    This stayed that way for over an hour, which prompted me to delete and
    restart the EXPORTER Background Batch job.  My question, is do I have
    to "re" EXPORT all the entities I have setup?  The reason I ask is
    that when I try to use the REPORTER on such things as PHASE IV line
    reports, I don't see any data...  Thanks in advance.
    
    /Mic
    

    
	Mic,

    Firstly I'll give more details about Exporter and secondly I'll try  
    to give you some ideas why Exporter Background (BG) process can be in 
    RWMBX state.

    To write collected data into RDB BG creates another process: Exporter
    Background Writer (BGW). These two processes communicate using mailbox.
    When this mailbox is full the BG is waiting until the BGW reads another
    portion from it.

    Question is why the BGW is not reading mailbox. 
    Some possible answers:
         a. BGW is blocked trying to access RDB. It can be done, for example,
            if you have reports running, or you are using interactive tools 
            to look into this RDB;
         b. You overload your system. I do not think that this your case
            because you create only 30 exporting requests ( what is a export
            period ?). You can try to suspend half of them and check how it
            affect the BG.
         c. The system parameters are not set up correctly.

    I would recommend to check the status of the BGW process. It will help
    us to identify the problem.

    BTW, are you using the "past time" export into the same RDB?

	SAm
 
    

    Sam,
    	Thanks for the prompt replies...  To answer one of your questions,
    I guess I am using past time REPORTER.
    
    This is what I'm doing, I've got a DECROUTER 2000, which I imagine is a 
    NODE4 entity (it has a DECnet address).  I click on the icon once, and
    then pull down OPERATIONS � EXPORT.  I setup the EXPORTING and ONLY
    give it an ending date, of 08-JAN-1993.  I give it an EXPORT PERIOD of
    1:00:00, and EXPORT TARGET to the ONLY Rdb database I have.  (btw, when
    I check the database size, it seems to be getting larger, it grew from
    16k to 18k since last night)
    
    Next, I am clicking twice on the icon, which displays the CHILD ENTITIES 
    of the DECROUTER.  I then click on the SYN-0 LINE, and repeat the EXPORT.
    Then I click on SYN-0 CIRCUIT and repeat the process a third time.
    
    I repeat the above step(s) for 6-8 DECROUTERS.  Next I do a similar
    excersie for 6 LANbridge 200s, 2 DECNIS 600s, and finally, I EXPORT
    data on CHILD ENTITIES for the DECmcc Server, which is a VAX 3400.
    
    I have tried a *hack* since yesterday's RWMBX episodes, but submitting
    2 EXPORTER_BACKGROUND batch jobs.  The job that went into RWMBX,
    disappeared at some point during the night, but the second batch job
    continued, and didn't display RWMBX...  Is this ok to do?  Or have I
    compounded my problem...smile.
    
    Finally, when I use the REPORTER, I try to get TRAFFIC SUMMARY data, or
    any of the menu items for a given DECROUTER.  So in this sense I'm
    doing past time reporting, right?  Well, the formats on the reports are
    ok, but it says that 12 polls were taken and 0 polls were successful...
    I don't get it?
    
    The DECmcc Server reports are fine!   Which tells me the REPORTER
    appears healthy...  for that matter, I believe the EXPORTER is healthy
    (in exporting NODE4 entity data for the VAX 3400).  Do you know if
    there's a restriction for DECROUTER 2000s in reporting?  I might add
    that the DECNIS 600s work fine as well...  meaning the REPORTER reports
    accurate data...
    
    Thanks again for taking so much time answering my questions.  I'm bound
    and determined to make this baby work...
    
    /Mic