| 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 |
Could someone go into some gory detail how the historian works with the
exporter and how the exporter works with the mcc_rpts.com file that you
can use to extract iformation out of the .rdb file into readable text
files.
I am a little confused. Of all of the notes that I have read on the
historian and the exporter, the historian puts information into a
DECmcc data base internal to the program. The exporter can look at the
data that the historian is filing away, and put it into a .rdb file,
this includes past and future data.
If this is the case, why do you run the historian at all, all you have
to do is run the exporter and get the information that you want. Now
that i think about this statement, is it true that you use the
historian for gathering information/data that can be exported at any
time, in the past/now or in the future.
Thanks Dave
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 1629.1 | Ok, short course on exp and hist | TOOK::R_SPENCE | Nets don't fail me now... | Thu Oct 10 1991 09:06 | 29 |
First pass...
Yes, if all you want is data in RDB for reporting then there is no
reason to run Historian.
Data stored by Historian can be viewed from within DECmcc by
specifiying past time. An example of this might be as follows;
An alarm condition detects that some anomaly has occured on the
network. The procedure runs DECmcc and starts frequent recording of
relevent data (perhaps this happens overnight). At a later time, the
network manager could review this info (and in V1.2 graph it) to see
what was happening. After the problem was resolved, the netmgr would
stop the recording of that particular data.
Data that is exported is put in an RDB file external to DECmcc. This
can be read by any application that supports access to RDB. This
includes several languages such as Rally (spelling?) and Focus and
Datatrieve. The sample proceedures supplied with DECmcc use Datatrieve
for the data lookup.
In V1.1, exporting historical past data doesn't work. Sigh... Fixed (so
I am told) in V1.2.
Does this help?
Oh, and if other's can add to this or correct anything, please do so.
s/rob
| |||||
| 1629.2 | Historian/exporter/mcc_rpts | F18::ROBERT | Fri Oct 18 1991 15:09 | 17 | |
Another thing that is not clearly written down, is how can you get the
data that is contained in the show counters/etc. from DECwindows, into
the exporter and into the report files via mcc_rpts, that you can print
out and show to the customer?
Is this documented somewhere?
Another question, if I understand this tool, the exporter cannot
extract data from past data, this will be fixed in version 1.2,
If you setup alarms on the items that you want to keep track of, should
you setup the historian to run in the background on all of your
systems, so that you have some information to go on if and when you
have a problem, with the new release of DECmcc 1.2 coming out, you then
can use the exporter to look at past/now/future data to isolate the
problems on the network?????
| |||||
| 1629.3 | F18::ROBERT | Sat Oct 19 1991 09:51 | 8 | ||
Is there anyway of finding out how long it takes for an export job to
run on a system e.g. all I am doing is exporting circuit information
from a system called see009 for example. Also does anyone know how
much memory each one of these export jobs takes up? On a system with
32MB of memory, how many export jobs can be run?
Thanks Dave
| |||||