| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
I know that Polycenter 1.4 is on the drawing boards. I was wondering
if the engineering groups could take a couple of things into
consiceration.
1- The need to pass parameters into MCC. I have com files that set
up the all permanent characteristics of an entitiy (IE: bridge)
in case of hardware failure etc. We'll my com files start off
by using a default qualifier of by password =, but I am not able
to pass a parameter as the password into MCC. Can you add this
functionality. Maybe you could make MCC reserve a special
symbol to indicate a parameter like DCL uses '. I am sure that
there are many folks that could use this feature.
2- I feel that the capability to register characteristics would be
a good idea. How many times do you have to replace hardware
that has gone bad or somebody had accidentaly reset the entity
back to factor defaults when you have no Idea what the tailored
characteristics are supposed to be? If we had the capability
of registering characteristics, we could then restore the proper
settings. What do you think?
3- How many folks are running MCC on a FDDI connected host? I will
be shortly, and I am not looking for to using the "via port"
qualifier everytime I perform a command. Even using the default
qualifier would be laborish. All of my com files that are would
have to be modified to figure out what MCC hosts I am work on,
and wether or not it needs to set "via port" as default. I
believe that the application should always default to the
Netowrk Interconnect that is assigned during startup.
Mike
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4797.1 | Product management | TOOK::MINTZ | Erik Pavlik Mintz | Fri Apr 09 1993 13:31 | 8 |
Framework requirements should go in the NOTED::EMF_REQ conference. However, V1.4 is a network management release, not a polycenter framework release. Contact Laura (MOLAR::) Sargent or Bill Gassman to propose network managment requirements. -- Erik | |||||
| 4797.2 | thanks | BRAT::BUKOWSKI | Mon Apr 12 1993 13:54 | 5 | |
re: -1
Thank you for the pointer.
Mike
| |||||
| 4797.3 | some answers to "how to" | TOOK::CALLANDER | MCC = My Constant Companion | Wed Apr 28 1993 10:55 | 44 |
to help you in the short term, this is how I work around some of the
items you noted in .0
1- passing in arguments.
Well since I can't pass in the arguments I create a command file
using define statements and define variables that I can then use in the
action taking procedure. So that these can be used by my procedure I
put the define commands into a file and then define the mcc_init
logical to point to it so they will be defined before my action
procedure is run. For examples.
$create temp.com
define p1 <value for p1>
define p2 <value for p2>
^Z
$define mcc_init temp.com
$create action.com
show node4 p1 all char
set node4 p1 counter timer = p2
^Z
$manage/enter do action.com
$create temp1.com
define p1 <new value for p1>
define p2 <new value for p2>
^Z
$define mcc_init temp1.com
$manage/enter do action.com
2- We do not provide the ability to register the characteristics
because they can be stored and retrieved latter using the recording
functions of the historian.
Please also note that the set of reference attributes can be extended
if you want to. To extend the set of attributes you must follow the
instructions in the Managmeent Module programming manual for how to
create a management specification defining the new attributes and load
them into the dictionary. You wil now have to set the values for these
attributes yourself though. (Personally I suggest recording the values,
that was the purpose of the historian.)
jill
| |||||