| 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 |
It's my understanding that when MCC is started from DCL, the kernel and the TRM PM are the only components initially activated. Other MM's are image-merged the first time they are needed. I'd like to know how I can force specific MM's to be image-merged. For instance, does the command MCC> show mcc DNA4_AM all characteristics cause the DNA4_AM to be image-merged? How about the command MCC> test mcc DNA4_AM Ideally I'd like to force each MM to be image-merged with the least amount of extraneous activity. I don't want to invoke any functions in the MM, I just want it to be image-merged. I particularly don't want to generate any network activity. Thanks in advance... Jack
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 61.1 | TEST will do it | GOSTE::CALLANDER | Fri Feb 23 1990 18:02 | 16 | |
I figure you want to do this for performance testing reasons; and
you are on the right track. Since the self management section of
each module is part of the module itself, then calling the test
command for each module (and you must do the TRM too!) will do the
trick.
TEST MCC DECNET_AM
TEST MCC TRM
TEST MCC ALARMS
TEST MCC DNA5_AM
TEST MCC CONFIG
TEST MCC CONTROL
TEST MCC ........
| |||||
| 61.2 | QUESTION - TRM too? | DSTEG::MCCANN | Mon Feb 26 1990 10:32 | 20 | |
RE: .1 > Since the self management section of > each module is part of the module itself, then calling the test > command for each module (and you must do the TRM too!) will do the > trick. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ When I invoke MCC from DCL at a terminal, and I get the MCC> prompt, hasn't the TRM PM already been merged? If not, then what is presenting the MCC> prompt to me? Perhaps I've misunderstood what the TRM PM does. If I issue the command TEST MCC TRM, doesn't the TRM PM parse the command line? And if it's parsing the command line (and whatever it does after that), hasn't it already been merged? So many questions... So little time... Thanks again, Jack | |||||
| 61.3 | INFO - TRM self management functions | GOSTE::CALLANDER | Wed Feb 28 1990 17:00 | 19 | |
Each module, including PMs, must provide a set of services for self
management. These services are available via the call function/access
(actually in the access dispatch tables) routines.
When you first start the director up the PM functions are immediately
availble, but the self management functions must be enrolled. Do
this by entering the:
MCC> ENROLL MCC$UI_TRM
command. After this you will be able to get at the SHOW MCC TRM xxx
functions.
Now also note that if you run the mcc$startup procedure you will
find that everything is enrolled for you.
jill
| |||||