| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1478.1 | on his DECmcc that is | WARNUT::PURNELLR | Life's not what I thought it was! | Tue Sep 10 1991 13:09 | 6 |
|
Sorry, I was not too clear....
I mean re-register his Phase IV entities on his DECmcc...
|
| 1478.2 | Currently, reregistration required | TOOK::CAREY | | Mon Sep 23 1991 21:48 | 10 |
|
Right now, he would have to re-register the nodes as they transition
from DNA4 to DNA5.
Thanks for pointing that out, we may be able to make it easier on our
users for this situation.
Suggestions?
|
| 1478.3 | Co-ordination with transition or command procedure required | LEMAN::BIRO | Georges Biro - SR/ACT | Wed Jan 15 1992 02:15 | 19 |
| May be worth pointing out here that the problem is not so simple and
DECnet/OSI transition needs to be co-ordinated with DECmcc
deregistration/re-registration activities.
Once the the Phase IV node has changed to DECnet/OSI a) it is not any
longer manageable as a Node4 entity which is normal b) it cannot be
deregistered any longer because of the problem indicated in Note 1376
c) is not yet seen as Node (DECnet/OSI) entity.
I know this problem will be fixed in V1.2, but DECnet/OSI is
shipping now and one can anticipate quite a few sites where this
problem will be encountered. My experience is that manually accessing
DNS objects created/managed by DECmcc is source of (great) troubles
most of the times. Would it be possible to make a command procedure
available as a temporary work-around that would de-register an unreachable
Node4 entity, possibly even re-register is as Node entity?
regards,
Georges.
|
| 1478.4 | Probably not | TOOK::MINTZ | Erik Mintz, DECmcc Development | Fri Jan 31 1992 09:43 | 3 |
| This is a desirable suggestion, but it does not appear that we have
the resources to devote to writing the procedure at this time.
|