| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2985.1 | X$X0 created by DECnet transport interface | STAR::VATNE | Peter Vatne, VMS Development | Tue Jun 26 1990 14:36 | 17 |
| The X$X0 object is created by the DECnet transport interface when the
DECwindows server is started. This object will not be created under
the following conditions:
1) If you override the default list of transports through the file
SYS$MANAGER:DECW$PRIVATE_SERVER_SETUP.COM, and don't include the
DECnet transport interface. For example:
decw$server_transports == "TCPIP,LOCAL"
2) If DECnet is not started. In that case, the DECnet transport
interface will check once a minute to see if DECnet has been
started yet. As soon as DECnet is started, then the X$X0
object should be created.
I strongly suspect case #2 is your problem. What version of
VMS are you using?
|
| 2985.2 | vms 5.1 | MLNCSC::VOCI | | Wed Jun 27 1990 04:39 | 1 |
| He is using vms 5.2.
|
| 2985.3 | Suggest upgrading to VMS V5.3 | STAR::VATNE | Peter Vatne, VMS Development | Wed Jun 27 1990 14:23 | 11 |
| I definitely think your problem is a race condition between DECnet
starting and DECwindows starting. This can easily happen if in
SYSTARTUP_V5.COM, you start DECnet in a batch job instead of in-line.
In VMS V5.1 and V5.2, DECnet must be started before the DECwindows
server is started. If the server does start before DECnet, the only
workaround is to restart the server.
This is not a problem with VMS V5.3 and later. That is the version
where the DECnet transport interface will automatically check once a
minute to see if DECnet has been started. I recommend that you upgrade
to VMS V5.3.
|