| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 621.1 | | TOOK::SHMUYLOVICH | | Tue Jan 15 1991 16:11 | 39 |
|
Re: .1
Hi Roland,
Some suggestions why you could not find rdb file:
>I startet a batchqueue for the exporter
>I submited the mcc_background_exporter.com
>
>In the iconic map I selected a NODE4 and selected export function in the
>operation menu. I defined a export job (only end time and export periode), so
>the export module should take the default mcc_export.rdb. After the time is
>passed, I don't find a RDB file.
Exporter_fm has two levels of defaults:
1. logical MCC_EXP_RDB_FILE which can be defined form DCL and
2. SYS$LOGIN:MCC_EXPORT.RDB which is used if logical MCC_EXP_RDB_FILE
is not defined.
If you use the second level of defaults you must specify
/PARAMETERS = SYS$LOGIN:MCC_EXPORT.RDB in the time you submit the
mcc_background_exporter.com. Please, check this parameter.
Did you look for MCC_EXPORT.RDB file in the SYS$LOGIN directory?
>During the export job, I tried to define a new one and mcc told me
>"EXPORTING ARREADY EXISTS" this is clear to me. But if I try to do a
>"SCHOW EXPORTING" I get a message "this message connot use the in Domain"
>"Unsupported Qualifier Id In Domain"
This is a big. It is fixed in V1.1 MCS version.
In version of MCC you have the only Export function of Exporter FM works
from the Iconic Map, from FCL all functions work correctly.
Sorry for inconvenience.
Sam
|
| 621.2 | I do so | ZUR01::SCHNEIDERR | | Wed Jan 16 1991 07:59 | 26 |
|
Sam
Thanks for your answer.
That with the bug is o.k. for me. The other problem is:
I tried now via the fcl interface. I submit the background process, as i done
yesterday (parameter = sys$login:mcc_export.rdb), start the exporter
(mcc> export node4 xxxx stop time = xxx, export period = xxx).
So far it runs. But now I do:
-- mcc> show_export node4 xxx --> proper display, with job as active
-- $ show queue export --> the background process is gone, the queue is empty
-- $ dir sys$login:*.rdb --> no file
-- after the endtime is reached, mcc> show_export node4 xxx --> shows the job
as active
-- now I have to do a delete_export
Roland
|
| 621.3 | how to check RDB | TOOK::SHMUYLOVICH | | Thu Jan 17 1991 13:00 | 21 |
|
Re: .2
Roland,
Did you try to look at the queue log file?
Error message can give some ideas what is wrong.
It seems to me the problem is in RDB.
Is RDB installed on your system? To check this,
please, do the following:
- install list sys$share:rdbshr.exe and
- dir sys$library:sql$int.exe
(In the MCC V1.1 MCS release this will be done automatically)
Regards, Sam
|
| 621.4 | seems o.k | ZUR01::SCHNEIDERR | | Fri Jan 18 1991 12:52 | 28 |
|
Hello Sam,
I didn't instal RDB new, but on the same node NMCC/DECnetmonitor runs and it
uses RDB.
I've checked the installation:
$ install list sys$share:rdbshr.exe
DISK$VAXVMSRL052:<SYS0.SYSCOMMON.SYSLIB>.EXE
RDBSHR;1 Open Hdr Lnkbl
$ dir sys$library:sql$int.exe
Directory SYS$COMMON:[SYSLIB]
SQL$INT.EXE;1 754 13-JUN-1989 22:07:46.30
I found the following errormessage in the exporter logfile:
%EXPORT-F-SYNCNORESP, no response from child within time limit
%EXPORT-E-SYNCNORESP, no response from child within time limit
roland
|
| 621.5 | EXPORTER FM requires >= VAX Rdb/VMS V3.1 | TOOK::R_LANE | | Mon Jan 21 1991 15:45 | 13 |
| Hi Roland,
The EXPORTER FM requires VAX Rdb/VMS V3.1 (or higher version). Judging
from the date of SQL$INT.EXE in your reply, I'd guess that you're running
a release of VAX Rdb/VMS V3.0. This is probably causing the EXPORTER's
writer subprocess to fail due to version mismatch with the Rdb and SQL
shareable images. Once you upgrade to VAX Rdb/VMS V3.1, the writer
subprocess should execute successfully. Before testing the EXPORTER again,
you should check that the background process has adequate subprocess quota
to spawn the single writer subprocess.
Roy
|
| 621.6 | Exporter Blues.. "Background exporting process is not set up" | NOATAK::TIMMERMAN | Jim Timmerman | Wed Jan 30 1991 23:57 | 44 |
|
I have gone over my procedure pretty thoroughly about 5 times now and still can
not get exporter to work. I checked for previously mentioned clues:
o My rdb is V3.1A (Release notes say V3.1B !!) has anyone demonstrated
that V3.1A will not work ?? Previous entries say 3.1 or greater..
o I submit the MCC_EXPORTER_BACKGROUND.COM with the /param=file.rdb
on que MCC$EXPORT The batch job has a subprocess quota of 30.
Do I understand correctly that this batch job itself spawns a
subprocess which executes the actual database population ? Does
a seperate batch submission have to be initiated for every export
directive ? Or, does the batch job spawn child jobs for each export
directive from DECmcc? While SHOWing SYS, I never see additional
processes.
o My persistant symptom is as follows:
MCC> EXPORT NODE4 MTADAM END TIME = 19:00, EXPORT PERIOD = 00:00:05, -
_MCC> EXPORT TARGET = SYS$LOOGIN:MCC_EXPORT_FORBDN.RDB
Node4 MTADAM
AT 30-JAN-1991 18:24:24
Background exporting process is not set up
MCC>
The above was entered while system time was about 18:30, so this was an export
of the future variety. Even though it says that the background exporting
process is not set up, a sho que/batch shows:
GLCIER_System > show que/batch
Batch queue MCC$EXPORT
Jobname Username Entry Status
------- -------- ----- ------
MCC_EXPORTER_BACKGROUND
SYSTEM 334 Executing
...help !
|
| 621.7 | RE: .6 | TOOK::SHMUYLOVICH | | Thu Jan 31 1991 19:48 | 78 |
|
RE: .6
I'll answer your questions in the opposite order: from the button to
the top.
> o My persistant symptom is as follows:
>
>MCC> EXPORT NODE4 MTADAM END TIME = 19:00, EXPORT PERIOD = 00:00:05, -
>_MCC> EXPORT TARGET = SYS$LOOGIN:MCC_EXPORT_FORBDN.RDB
>
>
>Node4 MTADAM
>AT 30-JAN-1991 18:24:24
>
>Background exporting process is not set up
>
>MCC>
>
>
>The above was entered while system time was about 18:30, so this was an export
>of the future variety. Even though it says that the background exporting
>process is not set up, a sho que/batch shows:
>
>GLCIER_System > show que/batch
>Batch queue MCC$EXPORT
>
> Jobname Username Entry Status
> ------- -------- ----- ------
> MCC_EXPORTER_BACKGROUND
> SYSTEM 334 Executing
It can be only one reason for such situation:
EXPORT TARGET argument in the EXPORT directive and parameter in SUBMIT
are not the same. This parameter can be verified using SHOW ENTRY/FULL.
> Do I understand correctly that this batch job itself spawns a
> subprocess which executes the actual database population ?
> ... Or, does the batch job spawn child jobs for each export
> directive from DECmcc?
Every background process spawns only one child.
> ... Does
> a seperate batch submission have to be initiated for every export
> directive ?
Exporter background process works on per RDB file basis, so you
must submit a separate process for every one RDB file you use.
RDB file name is used as parameter to submit. The same RDB file
name must be specified as a "export target" argument to the all
directives of the Exporter FM.
If, for example, you export data from two different entities to
the same RDB file you need only one background process. If you
export data from one entity into two different RDB files you
need two background processes (of course, you have to specify
two EXPORT directives with corresponding "export target" arguments).
You are free to export data from several different entities into
one RDB file.
> o My rdb is V3.1A (Release notes say V3.1B !!) has anyone demonstrated
> that V3.1A will not work ?? Previous entries say 3.1 or greater..
We did not try to work with V3.1A. But your current problem is not
with rdb. In the beginning background process spawns a child which
is responsible for writing in RDB. If this child can not start
(usually it happens when something is wrong in the RDB) it notifies
its parent process and exporter background process terminates. In
your case a background process is alive.
Sam
|
| 621.8 | Ahhhh.. It's all making sense now ! | NOATAK::TIMMERMAN | Jim Timmerman | Fri Feb 01 1991 00:14 | 32 |
|
I just successfully kicked off a retry of -.2, and got a
Node4 45.864
AT 31-JAN-1991 18:58:06
Exporting started
after making sure the Directive's target agreed with the que entry's file spec.
Thanks much for the patient and careful explanations!
For those who might stumble along the same path I did, here's my recipe:
This is in my SYSTARTUP_V5.COM:
$ INITIALIZE/QUEUE/START/JOB:8/BATCH/BASE_PRIORITY=3/OWNER=[SYSTEM]-
/PROT=(S:E,O:D,G:RW,W) MCC$EXPORT
This is my command to put an export job on the batch que:
$SUBMIT/QUE=MCC$EXPORT/PARAMETERS=SYS$LOGIN:MCC_EXPORT.RDB-
SYS$MANAGER:MCC_EXPORTER_BACKGROUND.COM
This is my command to initiate the export directive:
$ MANAGE/ENT EXPORT NODE4 MTADAM END TIME = 22:00, EXPORT PERIOD = 00:00:10,-
EXPORT TARGET = SYS$LOGIN:MCC_EXPORT.RDB
This is even pretty much what the documentation says to do though for me it
wasn't obvious that the submit /param switch *had* to agree with the
"EXPORT TARGET = " specification of the directive.
|
| 621.9 | ... %MCC-E-ALERT_TERMREQ, thread termination requested | NOATAK::TIMMERMAN | Jim Timmerman | Sat Feb 02 1991 00:27 | 73 |
|
After finally getting squared away on making sure that EXPORT TARGET
and the batch parameter file specs for rdb are the same (per .5-.8),
I am stuck again with a new problem with Exporter.
*** I ***
I initially was able to get a complete future export of node_only
counters into an rdb database. I was not able to generate a report
however. Sam Shmuylovich pointed out to me that my trying to
generate a Line Traffic Bandwidth Utilization Report from a database
that only had node attribute data in it is the obvious reason that I
got the following error. He also mentioned that there might be a bug
in the Reports procedures making it necessary to put line attribute
info into the rdb file before one could generate node only reports.
I'd appreciate confirmation of this. The log file complains:
$dtr
VAX Datatrieve T5.1
DEC Query and Report System
Type HELP for help
:node4_line_bandwidth_rpt
"MCC_NODE4_LINE" is not a readied source, collection, or list.
"CURRENT" is not a readied source, collection, or list.
"CURRENT" is not a readied source, collection, or list.
"CURRENT" is not a readied source, collection, or list.
exit
$exit
SYSTEM job terminated at 1-FEB-1991 11:18:08.16 [..etc]
I was not able to continue playing the angles on this because I ran
into a new problem:
*** II ***
After having been able to successfully launch Export batch jobs via,
$ SUBMIT/QUE=MCC$EXPORT/RESTART/PARAMETERS=SYS$LOGIN:MCC_EXPORT.RDB -
SYS$MANAGER:MCC_EXPORTER_BACKGROUND.COM
all of a sudden, the batch jobs started consistantly blowing up after
some 10s of seconds with the following in the log file:
$!
$ IF P1 .NES. "" THEN GOTO START_BTS
$ START_BTS:
$!
$ BTS == "$SYS$SYSTEM:MCC_EXPORTER_FM_BG.EXE"
$ BTS "SYS$LOGIN:MCC_EXPORT.RDB"
%MCC-E-ALERT_TERMREQ, thread termination requested
SYSTEM job terminated at 1-FEB-1991 13:16:19.21
Accounting information:
Buffered I/O count: 214 Peak working set size: 2587
Direct I/O count: 126 Peak page file size: 8111
Page faults: 1496 Mounted volumes: 0
Charged CPU time: 0 00:00:05.25 Elapsed time: 0 00:00:23.57
I've tried rebooting, & taking down all unnecessary processes. From
what I can remember, the only thing I changed between the time the
first batch job ran normally with a full export cycle and now was a
DTR symbol definition and a logical assignment in the
SYSTARTUP_V5.COM file so that the reports package can use Datatrieve
in command mode (vs DECwindows):
$ DEFINE/SYSTEM DTR$NOWINDOWS TRUE
$ dtr:==DATATRIEVE/INTERFACE=CHAR
BTW, I mentioned in -.6 that I'm running rdb V3.1A...
...help....again...
|
| 621.10 | A recipe for EXPORTING and REPORTS | NOATAK::TIMMERMAN | Jim Timmerman | Mon Feb 11 1991 18:45 | 172 |
|
I have been working offline with Sam Shmuylovich and Bob Merrifield who
have patiently guided me through understanding EXPORTING to the point
where I finally understand it and can use it. To potentially save them
some repeat grief, I am documenting the steps I took to get through a
successful exporting and report generation iteration. This recipe
hopefully will expose common mistakes that lots of people make as I did.
The commands I include below are **verbatim** what I typed. You should
only need to edit them for your particular parameters like time or
particular entity specification.
The following addresses only EXPORTING for *FUTURE* attributes, and
REPORTING on same; * NOT * RECORDING, HISTORIAN, PERFORMANCE, ALARMS etc.
It is assumed that the reports setup procedures have been executed per
the release notes starting on page 2-39. There are very important useage
tips included in this section as well.
I. First clear all exporting that might be hanging around from previous
attempts:
MCC> delete_exporting node4 *
MCC> delete_exporting node4 * line *
MCC> delete_exporting node4 * circ *
;NOTE: Underscores in the command directives are required in this
; release !
II. Kill off the batch jobs from previous attempts.
$ delete/entry=xxx
; xxx is a number from "show que/bat" of the job resulting from
; "SUBMIT/RESTART/QUE=your_que_name_for_exporting-
; /PARAMETERS=SYS$LOGIN:MCC_EXPORT.RDB -
; SYS$LOGIN:MCC_EXPORTER_BACKGROUND.COM"
;
; If you haven't started such a job, then skip this step.
III. Then get rid of any trace of rdb fragments from previous attempts.
...from SYS$LOGIN:
$ del MCC_EXPORT*.RDB;*
$ del MCC_EXPORT*.RUJ;*
$ del MCC_EXPORT*.SNP;*
IV. Now, start rebuilding the exporting scenario. First start an
exporting batch job. This step assumes you've created an exporting
specific que in your SYSTARTUP_V5.COM file via something like:
"INITIALIZE/QUEUE/START/JOB:8/BATCH/BASE_PRIORITY=3/OWNER=[SYSTEM]-
/PROT=(S:E,O:D,G:RW,W) MCC$EXPORT"
$ SUBMIT/QUE=MCC$EXPORT/RESTART/PARAMETERS=SYS$LOGIN:MCC_EXPORT.RDB-
SYS$LOGIN:MCC_EXPORTER_BACKGROUND.COM
; The batch job should create new MCC_EXPORT.RDB, .RUJ, and .SNP
; files in SYS$LOGIN.
V. Now issue the exporting directives for a particular set of entities.
The commands below specify exporting for NODE, CIRC, and LINE
entities for node NOATAK, using a 10 minute export period. Be
careful that the export period is not 00:00:10, which is 10 seconds !
The exporting state will hang in SUSPENDED forever if it doesn't have
enough time to get off a complete poll sequence. Also, I have found
that the polls fail if you don't specify at least 10-15 minutes.
Otherwise you'll get lots of:
Last poll failure reason = "schedule time passed"
in your SHOW_EXPORTING status.
$ MANAGE/ENT EXPORT NODE4 NOATAK END TIME = 18:00, -
EXPORT PERIOD = 00:15:00, EXPORT TARGET = SYS$LOGIN:MCC_EXPORT.RDB
$ MANAGE/ENT EXPORT NODE4 NOATAK CIRC QNA-0 END TIME = 18:00, -
EXPORT PERIOD = 00:15:00, EXPORT TARGET = SYS$LOGIN:MCC_EXPORT.RDB
$ MANAGE/ENT EXPORT NODE4 NOATAK LINE QNA-0 END TIME = 18:00, -
EXPORT PERIOD = 00:15:00, EXPORT TARGET = SYS$LOGIN:MCC_EXPORT.RDB
; Above assumes you issue the directives prior to 18:00. Start time
; will be default of current system time.
; Note: The three commands above specify exporting for 3 different
; entities. The first is for NODE Noatak; 2nd for CIRC QNA-0 on node
; noatak; 3rd for LINE QNA-0 on node noatak.
; Note: The file spec in "EXPORT TARGET = SYS$LOGIN:MCC_EXPORT.RDB"
; in the export directives *MUST* agree precisely with the file spec in
; "SUBMIT/QUE=xxxx/PARAMETERS=SYS$LOGIN:MCC_EXPORT.RDB" from step IV
; above.
; Note: You can issue exporting directives for any number of node, line
; and circuit entities for the same rdb file as long as your
; EXPORT TARGET specification points to SYS$LOGIN:MCC_EXPORT.RDB.
;
; You could also start multiple batch jobs, each with a different rdb
; file specification and then issue export directives with the EXPORT
; TARGET pointing to these particular file specs. In order to perform
; reporting against these rdb files though, you'd have to make sure the
; DTR rdb database files unique to this export are defined per the
; installation notes (i.e., DTR DEFINE DATABASE MCC_EXPORT_private ON
; disk:[directory]MCC_EXPORT_private.RDB). I haven't tried this last
; piece, so I don't know for sure if it works.
VI. To see if your exporting is running ok, a MON PROC/TOPCPU will show
the batch job and its subprocess running pretty heavily soon after
issueing the above export directives. The following MCC directive will
show a very detailed status:
$ manage/ent show_exporting node4 noatak export target -
sys$login:mcc_export.rdb
Node4 NOATAK
AT 11-FEB-1991 10:29:11
Exporting parameters are:
Exporting state = ACTIVE,
State since = 11-FEB-1991 10:18:01.46,
Export period = 0 00:08:00.00,
Begin time = 11-FEB-1991 09:32:41.79,
End time = 11-FEB-1991 18:00:00.00,
Export target = "SYS$LOGIN:MCC_EXPORT.RDB",
Request time = 11-FEB-1991 09:32:41.79,
Requested by = "SYSTEM",
Time of last successful poll = "11-FEB-1991 10:18:14.54",
Number of successful polls = 1,
Time of last failed poll = "NONE",
Last poll failure reason = "N/A",
Number of failed polls = 0,
Last export time = "11-FEB-1991 10:18:14.54",
Time of last export failure = "NONE",
Last export failure reason = "N/A",
Number of export failures = 0,
Sequence name = "EXPORT",
Initial sequence number = 0,
Current sequence number = 7
The following 2 commands will show the same type of exporting status as
above, but for LINE and CIRC entities.
$ manage/ent show_exporting node4 noatak circ qna-0 -
export target sys$login:mcc_export.rdb
...
$ manage/ent show_exporting node4 noatak line qna-0 -
export target sys$login:mcc_export.rdb
...
VII. After the rdb database has the required information in it,
MCC_RPTS.COM can be invoked to generate reports. If the procedure
fails while trying to invoke datatrieve (look in the
MCC_RPTS_NODE4_xxxxxxxx_DTR.LOG files), make sure that the symbol
"dtr" equates to a successful invocation of a command line oriented
datatrieve session. The latest version of datatrieve comes up as a
decwindows session by default which is very confusing to MCC_RPTS.COM.
You might need to define a symbol "dtr:==DATATRIEVE/INTERFACE=CHAR"
in your startup procedure for the MCC_RPTS.COM to work correctly.
Also, if you are running DECgraph 1.6, read notes TOOK::MCC:557.* in
order to get past a glitch with using this version of DECgraph.
Other than the above contortions, this product is starting to look good
to me.
Good Luck !
|
| 621.11 | a note to the recipe | TOOK::SHMUYLOVICH | | Mon Feb 11 1991 19:44 | 54 |
|
Just a few comments to the .10:
> V. Now issue the exporting directives for a particular set of entities.
> The commands below specify exporting for NODE, CIRC, and LINE
> entities for node NOATAK, using a 10 minute export period. Be
> careful that the export period is not 00:00:10, which is 10 seconds !
> The exporting state will hang in SUSPENDED forever if it doesn't have
> enough time to get off a complete poll sequence. Also, I have found
> that the polls fail if you don't specify at least 10-15 minutes.
> Otherwise you'll get lots of:
>
> Last poll failure reason = "schedule time passed"
>
> in your SHOW_EXPORTING status.
The minimal export period depends on your system performance and the respond
time from the specified entity. It's recommended that this period will
be at least twice bigger that time required to get Show for all attribute
partitions. The smallest interval I successful used was 1.5 min.
> ; Note: The file spec in "EXPORT TARGET = SYS$LOGIN:MCC_EXPORT.RDB"
> ; in the export directives *MUST* agree precisely with the file spec in
> ; "SUBMIT/QUE=xxxx/PARAMETERS=SYS$LOGIN:MCC_EXPORT.RDB" from step IV
> ; above.
From the Exporter's release notes:
2.11.4 Suggestions
1. RDB database name -- To specify RDB database name you can:
- use export target argument in every Export directive
to specify RDB file name;
- define logical MCC_EXP_RDB_FILE;
- use default RDB name SYS$LOGIN:MCC_EXPORT.RDB.
If export target argument is not specified Exporter tries
to get RDB database name from logical MCC_EXP_RDB_FILE.
If this logical is not defined Exporter uses
SYS$LOGIN:MCC_EXPORT.RDB as a RDB database name.
As it is noted in .10 this RDB_DATABASE_NAME *MUST* agree precisely
with the file spec in
"SUBMIT/QUE=xxxx/PARAMETERS=RDB_DATABASE_NAME"
Sam
|
| 621.12 | | DFLAT::PLOUFFE | Jerry | Mon Feb 11 1991 20:34 | 19 |
| RE: .10
Jim:
First of all, I'm impressed with you're write-up and
secondly, I'm depressed that the process involved is so complex.
I hope there are plans in place to make the use of this product more
user-friendly. Historian and Exporter are two very valuable FMs and we
owe it to our customers to make these functions easier to use!
BTW, the above should not only apply to these FMs. We owe it to ourselves
and to our customers to review and improve the useability of all our MMs
(Alarms included! ;) )!!
- Jerry
(ex-Alarms PL)
|
| 621.13 | missing Datatrieve procedures | F18::ROBERT | | Tue Oct 01 1991 13:59 | 10 |
| re:10
Can someone tell me where I can find all the files needed to run the
MCC_RPTS.com file that you mention in this note. I ran this file and
it came back and said that I was missing some Datatrieve procedures.
Can someone help me. I need to get some reports out from DECmcc, i.e.
the exporting feature (I finally figured out how to use this)
Thanks ahead of time Dave
|
| 621.14 | RT_M | NSSG::R_SPENCE | Nets don't fail me now... | Tue Oct 01 1991 14:54 | 7 |
| In the DECmcc Performance Analyser Use manual there is a chapter
near the end of the book that correctly explains how to get reports
working. I followed the instructions and it worked fine for me.
Try it.
s/rob
|
| 621.15 | | F18::ROBERT | | Tue Oct 01 1991 18:17 | 27 |
| Thanks,
I got to the right place, I am not a datatrieve/rdb expert.
I got into datatrieve, and did a show all and got the following:
Dictionaries:
CDD$EXAMPLES CDD$PROTOCOLS CDD$RDB_SYSTEM_METADATA
CDD_PLUS$EXAMPLES DTR$LIB DTR$USERS
The default directory is _CDD$TOP
No established collections.
No ready sources.
No loaded tables.
I followed the examples in the book, and got the following:
"MCC_NODE4_CIRCUIT" is not a readied source, collection, or list.
"CURRENT" is not a readied source, collection, or list.
Element "CIRCUIT_GRAPH" not found in dictionary.
I need some enlightenment?
Thanks Dave
PS: is there something in datatrieve that is not setup?
|
| 621.16 | did you initialize? | PARZVL::KENNEDY | This ain't no party | Wed Oct 02 1991 14:23 | 6 |
| > PS: is there something in datatrieve that is not setup?
Sounds like it. Did you follow the instructions on Initializing the Reports
Package (in my book, it starts on p7-4)?
_MaryEllen
|
| 621.17 | Exporter | F18::ROBERT | | Fri Oct 04 1991 16:40 | 19 |
| Thanks Rob for the help.
Now that I have got things running ok, and exporting some information,
I have not been able to figure out a couple of things:
I got into export and am exporting some info into a data base called
stlouis.rdb - I went into a system I call SEE001, in DECmcc, and exported
some information without enabling anything in the entity, i.e. line or
circuit. I then went back into this entity and clicked on line and started
another exporting job to the same data base called stlouis, and I did the
same for circuit,
my ?? I do not understand how to get the information out of the database
for the line, and circuit. Am I missing something?
Thanks for the help.
Dave
|
| 621.18 | Use Reports package | TOOK::ANWARUDDIN | Anwar | Tue Oct 08 1991 11:11 | 17 |
| ...
..
I got into export and am exporting some info into a data base called
stlouis.rdb - I went into a system I call SEE001, in DECmcc, and exported
some information without enabling anything in the entity, i.e. line or
circuit. I then went back into this entity and clicked on line and started
another exporting job to the same data base called stlouis, and I did the
same for circuit,
my ?? I do not understand how to get the information out of the database
for the line, and circuit. Am I missing something?
>> You use the Reports package to get statistical information from
>> the RDB. The Reports Menus will help you in selecting the kind of
>> report you want. Chapter 7 in the "Performance Analyzer Function
>> Module Use Manual" explains the details.
|
| 621.19 | RE: .17 You can use SQL | TOOK::SHMUYLOVICH | | Tue Oct 08 1991 13:51 | 31 |
|
re: .17
In addition to the Report package you can get this data using
SQL. For example, using interactive SQL you can do the following:
1. SQL> declare schema filename <rdb_database_name>; -> connect you to
the specified
database
where <rdb_database_name> is an "export target" argument
in the Export deirective.
2. SQL> show table <table_name>; -> shows specified table and its
columns
where <table_name> is :
- MCC_NODE4 for node4;
- MCC_NODE4_LINE for line;
- MCC_NODE4_CIRCUIT for circuit;
- * gives you all tables .
3. SQL> select <column> from <table_name>; -> shows a particular column
from the specified table.
The above is a very simple example of the select statement.
For more information, please, refer to VAX Rdb/VMS reference manual.
SAm
|