| 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 |
Hello,
Can we still enroll new management modules dynamically
with DECmcc V1.2 ?
Or do we have to kill all DECmcc process mcc_kill,
re-install a new version and reenroll ?
Regards
Catherine
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3470.1 | Still works | TOOK::MINTZ | Erik Mintz, dtn 226-5033 | Thu Jul 30 1992 13:37 | 7 |
You can re-enroll a management module while the system is running. However, since the dictionary requires single user access for writes, you may have to shut down other modueles if you need to update the dictionary. -- Erik | |||||
| 3470.2 | So, automatic shutdown of other modules required.. | TAEC::HAYES | Tu quoque mi fili ! C.Hayes SVP @VBE | Mon Aug 03 1992 05:21 | 33 |
You never know, someone may use another AM while
you are currently installing a new one provided
you have not made it inaccessible (i.e disallow manage,
remove licence...).
Sending a broadcast message "Instal in progress, please
do not use DECmcc..." is NOT sufficient.
Moreover, the means of making DECmcc inaccessible must
be inside or at least documented in the new module
installation procedure.
So...
1- Is there a way on Ultrix to make sure no user is using
other modules while installing a new Access Module ??
2- Can I shutdown other Access Module in the installation
procedure of the one I am currently installing ?
3- What about on VMS ?
Thanks to help
/CjH
| |||||
| 3470.3 | Why? | TOOK::MINTZ | Erik Mintz, dtn 226-5033 | Mon Aug 03 1992 09:54 | 20 |
I don't understand your point. There is no problem enrolling a module
while a DIFFERENT module is running. There are already locks to protect
the dispatch table file.
> 1- Is there a way on Ultrix to make sure no user is using
> other modules while installing a new Access Module ??
No
> 2- Can I shutdown other Access Module in the installation
> procedure of the one I am currently installing ?
root can use "mcc_kill ALL" to terminate all MM processes on the system,
regardless of who owns them. You can do this from inside an installation
procedure if you choose (but be sure to warn the installer...)
> 3- What about on VMS ?
I know of no convenient way to do this on VMS.
| |||||