| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 4328.1 | fcl or callable mcc options | GOSTE::CALLANDER | | Mon Jan 04 1993 09:49 | 6 |
| since the reference data is all ascii data, you might simply want
to write a procdure to extract the data through the FCL and write
it out into some database of choice. Otherwise you could get real
fancy and write an MCC callable application that calls the registration
FM directly and requests all of the information (read this as *more*
work).
|
| 4328.2 | Easy | RACER::dave | Ahh, but fortunately, I have the key to escape reality. | Mon Jan 04 1993 09:49 | 5 |
| You can either write a simple routine that uses callable MCC to get the data
or you can issue SHOW commands with output to a file from the FCL.
An example of the first method was posted in the MCC-TOOLS conference no too
long ago.
|
| 4328.3 | use Exporter | TOOK::SHMUYLOVICH | | Tue Jan 05 1993 08:58 | 5 |
|
You can use the Exporter FM to export all attributes (including
reference attrubutes) to the data base.
Sam
|
| 4328.4 | geez sometimes we overlook the easiest solution | GOSTE::CALLANDER | | Tue Jan 05 1993 09:11 | 1 |
|
|
| 4328.5 | Exporter is too big and slow. | RACER::dave | Ahh, but fortunately, I have the key to escape reality. | Tue Jan 05 1993 11:05 | 13 |
| Exporter is the wrong way to solve the base issue. This is not a
repetitive type of event, like the exporter is designed to deal with.
Exporter can be set up to dump this data only once a week, but at a cost
of also going out and generating lots of other data, like counters,
and status, and characteristics, and
performance for every entity on the net. Thats kind of silly. All that
appears to be needed is just the information in the MIR.
Also, Exporter is fairly complex to get set up and working, and, IMHO can
eat up significant resources. Remember that the goal would be to dump
ALL of the reference data for every entity. That could take the
many exporters you need (for each domain) almost forever.
|
| 4328.6 | OK. So do this: | TOOK::MCPHERSON | pre-retinal integration | Tue Jan 05 1993 12:38 | 19 |
| re .5
Write a DECmcc command script to SHOW all the reference attributes for
<whatever> to a file.
Write a post-processor/vegamatic application (DCL/awk/TPU/SCAN/Teco/C/pick one)
to strip out all of the noise from the DECmcc output and create a 'comma
delimited file' (or whatever it is that dBase can handle...) and import *that*
into dBase...
Once it works, set it all up as a batch job to run weekly/monthly/whenever.
Then post a pointer to your hackage in the MCC-TOOLS conference so that someone
else can one-plus your hackage later...
/doug
P.S.
The phrase "IMHO" doesn't apply to Dav. None of his O are H. ;^)
|