| Bill,
I appreciate your problem... I've been struggling with the
REPORTER for a while now and I'll share a couple of things to look
into...
(in no certain order)
You didn't mention what 'entities' you were trying to report on, so
I'll assume you did what I did at first...
First of all, ensure that your EXPORTER background process is pointing
to a *real* .RDB database. In otherwords, when you submit your
EXPORTER background process, /PARAM='database.rdb'. You can type, SHOW
USERS/FULL and see the subprocess of your EXPORTER background proces...
Next you need to (from the IMPM) click once on the entity you want to
export, say a NODE4 (VAX system); next, click and drag the
OPERATIONS menu; next type EXPORT. When the menu comes up type, the
directory and filename, ie: disk$:[exporter]database.rdb;
At this point, you have setup the EXPORTER for all entities, JUST for
the NODE4!, ie: COUNTERS, CHARACTERISTICS, etc. Next you have to
double click on the NODE4, click once on the CHILD ENTITI(ES) you want
to EXPORT and repeat the process... for example, if you want to export
data about a particular line you'll need to click on the actual line
and then repeat the export process.
That takes care of the EXPORTER part. Now you need to play with this a
little because, the traffic in your area, the size of your
configuration, the load on your server, etc. play a factor! See my
note about RWMBX, 4009!
Now when it comes to the REPORTER....huuummm. What you'll want to do
is ensure that the LINE SPEED for ROUTERS, has been set... use the
DECNET address instead of the nodename, and remember that REPORTER
prints 132, so you'll need to have a LANDSCAPE-able printer...
If you run into more problems, please send mail to Mic JUNG::GALVIN.
I've been working with the EXPORTER/REPORTER for the past month...
I've got all kinds of GOOD/BAD news... by the way, the REPORTER does
NOT support LANbridge 200s, but does support DECNIS bridge/routers, as
NODE (Phase V) entities...smile.
Hope this helps you get by the *trauma* I've been through in the past
month...smile.
/Mic
|
| Hi Mic,
I am the guy in the field that the author of the base note is trying to
assist. I understand about setting up the exporter for the node and the
line and the circuit thanks to Bill's help however the real issue is
that when I try to create a report for the node I get the message in
the mcc_rpt_node4_node_traffic_dtr.log file "element
node4_node_traffic_rpt " not found in dictionary. I get the same
type of message when trying to create a report for the line i.e.
mcc_rpt_node4_line_traffic_dtr contains "node4_node_line_traffic_rpt"
not found in dictionary. When you run datatrieve and show for example
node4_node_traffic_rpt it shows a lengthy procedure so this means that
the proper elemnets are defined in the dictionary but when the report
creation procedure is run it doesnt see these elements. I even tried to
run the .com procedures again to redefine the phase iv elements which
ran succesfully but no luck. The owner of the exporter queue is system
and all submits to the queue and exporting from MCC is done by system.
Regards, Bob Schmitt
|
|
Bob,
Well, since I've opened Pandora's Box...smile.
I can't remember the EXACT error message(s) you describe, but here's a
few things to look for:
Make sure that the database is the same in DTR, EXPORTER
background process (ie: /PARAM='database') and the exact database
name. So, if you do:
$ DTR SHOW MCC_EXPORT;
You'll see: DATABASEABC.RDB ! the proper directory structure.
When you look at your export:
MCC> SHOW EXPORT NODE4 'blah' EXPORT
TARGET='directory':DATABASEABC.RDB
You'll see: DATABASEABC.RDB !check the menu items
Menu items I look for are obvious: ACTIVE, SUCCESSFUL POLLS, etc.
When you look at the actual file, it should be increasing over a
period of time...
$ DIR/SIZ 'directory':DATABASEABC.RDB 1000000 ! I jest!
Now I ran into an interesting problem with DECROUTERS; I had to set
the LINE SPEED for the ports I was exporting data on, may or may not be
applicable.
When you use the REPORTER you might want to try using the DECnet
Address instead of the NODENAME; I use OPTIONS 2 & 11 for line traffic
on a DECROUTER 2000. This gives me a report on BANDWIDITH UTILIZATION
and a nice GRAPH.
Of course, you need to recognize the ultimate CAVEAT! The REPORTER
is simply a "SAMPLE", and it's not to be all inclusive...smile. Not
being much of a DATATRIEVE or Rdb expert, I tend to rely on it
*exclusively*, if you know what I mean...
In the REPORTER Use book, you need to remember it states that when
you change databases, you'll need to redefine your MCC_EXPORT logical
in DTR. This one bit me a couple of times. Most of all you have to
appreciate the *complexity* of the EXPORTER, when you fire up several
exports, I have a command procedure I use to do them, look at what it
does to your system...it's quite *impressive*! The subprocesses that
are doing the writing, polling, etc. take LOTS of CPU!
I've scrapped things about 4 times, and finally have gotten to the
point where I'm using EXPORTER � REPORTER for 11 DECROUTER 2000s, and
leaving well enough alone for the time being... I haven't touched the
IMPM for 2 days!
I'm sure I've seen your Datatrieve Message before, but I can't
quite place...
Please send me mail, Mic JUNG::GALVIN if I can help... I'm
learning along with everyone else, and this conference has been
excellent!
/Mic
|