| 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,
During the registration of a terminal server DECmcc TSAM creates
a link in the DNS directory MCC_Terminal_Server_BackTranslation.
This link has an attribute DNS$LinkTimeout.
DNS> sho link MCC_Terminal_Server_BackTranslation.08002B238561 attr DNS$LinkTimeout
Expiration ______________ 12-JUL-1993 05:31:04.90
Extension _______________ 20 0:0:0.0
Timestamp _ 28-JUN-1993 15:09:44.92 aa-00-04-00-5d-ca
Why does this link have an expiration date/time and what
happens if it expires?
Ton Beekman.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5276.1 | Used by DNS Skulk/Update operations | TOOK::KWAK | Mon Jun 28 1993 18:22 | 21 | |
RE: .0
> Why does this link have an expiration date/time and what
> happens if it expires?
The link has expiration date so that the 'dangling' links can
be removed by DNS skulk/update operation.
In some case, when one has a problem with MCC registration, one
deletes the corresponding DNS object (using DNS$Control), but not
the softlinks. In this case, the dangling links can be remoted
by DNS skulk/update operation. (note that it is sometimes hard to
figure out the backtraslation link name from address - e.g. phase4
node address backtraslation link)
When the DNS$LinkTimeout expires, the DNS skulk/update operation
checks if the link's target exists or not. If it does not exist,
the link is deleted. If the target exist, the DNS$LinkTimeout's
'Expiration' is extended by 'Extension' (in this case 20 days).
William
| |||||