| 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
|
| 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?????
|