| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2175.1 | QAR 2195 | TOOK::MINTZ | Erik Mintz, DECmcc Development | Thu Jan 23 1992 11:04 | 4 |
| Entered as QAR 2195
(I presume you mean T1.2.4 is the version you are running)
|
| 2175.2 | yes T1.2.4 | COL01::LUNT | | Fri Jan 24 1992 04:05 | 6 |
| Hello,
Yes I mean T1.2.4. Could you also please post any answers to the
posted QAr here. Our QAR account allows us only to see EXternal
QAR's.
THanks Julie Ann
|
| 2175.3 | qar moved to mcc_ext_v1_2 | TOOK::CALLANDER | MCC = My Constant Companion | Fri Jan 24 1992 10:12 | 5 |
| the qar from MCC_INTERNAL has been moved to MCC_EXT_V1_2 #176,
so that the external site can now monitor the response.
jill
|
| 2175.4 | thanks | COL01::LUNT | | Thu Jan 30 1992 11:11 | 1 |
| thanks Jill, Julie Ann
|
| 2175.5 | V1.2 Documnetation bug? | PHONE::CDUNN | Feedback is the Breakfast of Champions! | Thu Jan 30 1992 11:34 | 18 |
|
As a new user of MCC I am not sure this is a problem, but it looks like one..
In the V1.2 version of the DECmcc Management Module Programming manual, on page 6-3,
Figure 6-1, there is an example showing the relationships between the vector file and
the Sample AM entry points. The last example in the figure is:
SHOW <<SAMPLE,*> <SAMPLE_AM, *>> CHAR
mcc_sample__show char_mcc
SHOW <<SAMPLE,*> <SAMPLE_AM, *>> CHAR
mcc_sample__test_mcc
This seems to say that the same tuple has two entry points. Is the CHAR on the
second line supposed to be TEST, or somethine similar? Or have I missed something?
Thanks for the help!
-Charlie
|
| 2175.6 | There are a few typos in Figure 6.1 | NANOVX::ROBERTS | Keith Roberts - DECmcc Toolkit Team | Thu Jan 30 1992 16:24 | 23 |
| Charlie
Sorry about that, there are a few typos in Figure 6.1 -- We'll have them
fixed for the v1.2 release of the Management Module Programming guide.
Thanks for bringing this to our attention.
The text should read (taken from mcc_sample_vector.mar file):
mcc_dispatch_entry -
SHOW,-
<mcc_entity <MCC, * >,<SAMPLE_AM >>,-
CHAR,-
mcc_sample__show_char_mcc
mcc_dispatch_entry -
TEST,-
<mcc_entity <MCC, * >,<SAMPLE_AM >>,-
NULL,-
mcc_sample__test_mcc
/keith
|
| 2175.7 | Thanks for the corrected version! | PHONE::CDUNN | Feedback is the Breakfast of Champions! | Fri Jan 31 1992 15:53 | 4 |
|
No problem. Thanks for including the corrected version!
-Charlie
|
| 2175.8 | Historian Doc Comments | WELCLU::MCCALLUM | | Wed May 06 1992 10:34 | 26 |
|
A couple of comments on the historian documentation on 1.2.7
On page 2-3 there are some pictures of windows which are supposed to be
for the exporter. They look like edited versions of the screens for the
historian are are not representitive of what is displayed when one
starts the exporter, for example there is not partition field for the
exporter.
This confuses people.
The test also talks about historical data, and says things like "submit
the historian backfround process". These should all sya exporter I
think.
Also I recall (but may be wrong) that one does not have to export info
at the sub-entity level, only at the global level, ie one records node4
info and then you get all the line and circuit info.
The manual is very vague about this and only gives one example. It
seems that the manual was written by copying the historian section to
create the exporting section - but there are some significant
differences which are not clearly explained.
Dave McCallum
|
| 2175.9 | thanks, will correct HDS Use | TNPUBS::M_QUINN | | Wed May 06 1992 15:38 | 12 |
| Thanks for the comments Dave.
You're right, I was not too careful when putting together the cheat
sheets (pp 1-2, 1-3 and 2-2, 2-3) where I overdid it with the
cut-and-paste. They've been corrected.
You're wrong about exporting at the sub-entity level though; you do
have to specify the child entity. You don't get all levels when you
select the global level. But I agree, the book needs to be clearer
about that. Will clarify.
Mike
|