| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 1735.1 | Common question #2 | STAR::VATNE | Peter Vatne, VMS Development | Tue Nov 14 1989 11:23 | 8 |
| How to interpret system statuses:
$ write sys$output f$message(%x20e4)
%SYSTEM-F-LINKABORT, network partner aborted logical link
$ write sys$output f$message(%x20fc)
%SYSTEM-F-PATHLOST, path to network partner node lost
From this, I conclude your network is flaky.
|
| 1735.2 | The Decterms are local | CASEE::CESARO | Danielle Cesaro | Wed Nov 15 1989 04:02 | 7 |
|
>%SYSTEM-F-LINKABORT, network partner aborted logical link
The decterms are local, and created from the application menu.
I thought that in such case the transport was not decnet. Am I wrong?
Danielle
|
| 1735.3 | Your DECterms might not be using local transport | STAR::VATNE | Peter Vatne, VMS Development | Wed Nov 15 1989 13:51 | 11 |
| I've double-checked the local transport code, and just don't see how
it could ever return the SYSTEM-F-LINKABORT status. I have to conclude
that although you are running the DECterms locally, they are using the
DECnet transport.
An easy way to check this is to use ANALYZE/SYSTEM, set your process
index to the terminal controller process (e.g. DECW$TE_1), and do a
SHOW PROCESS/CHANNELS. One of the channels should be to either
DECW$TRANSPORT_LOCAL.EXE or to DECW$TRANSPORT_DECNET.EXE.
Give it a try and let us know what you find.
|
| 1735.4 | Seems to be local transport | CASEE::CESARO | Danielle Cesaro | Fri Nov 24 1989 12:31 | 73 |
| Sorry to be late answering,
Here is the result of the ANALYZE/SYSTEM; as you can see the transport
seems to be local.
I still got a lot of "connection closed" messages but
the decterm are not always lost.
Thanks for your help
Danielle
Process index: 002B Name: DECW$TE_2 Extended PID: 364002AB
--------------------------------------------------------------
Process active channels
-----------------------
Channel Window Status Device/file accessed
------- ------ ------ --------------------
0010 00000000 SUNMUM$DUA71:
0020 809CD740 SUNMUM$DUA0:[SYSCOMMON.SYSEXE]DECW$TERMINAL.EXE;1
0030 809C0EA0 SUNMUM$DUA0:[SYSCOMMON.SYSLIB]SECURESHRP.EXE;1 (section file)
0040 809BC520 SUNMUM$DUA0:[SYSCOMMON.SYSLIB]SECURESHR.EXE;1 (section file)
0050 809B8740 SUNMUM$DUA0:[SYSCOMMON.SYSLIB]LIBRTL.EXE;11 (section file)
0060 809B75A0 SUNMUM$DUA0:[SYSCOMMON.SYSLIB]VAXCRTL.EXE;29 (section file)
0070 809CA080 SUNMUM$DUA0:[SYSCOMMON.SYSLIB]UVMTHRTL.EXE;9 (section file)
0080 809D8F60 SUNMUM$DUA0:[SYSCOMMON.SYSLIB]DECW$XLIBSHR.EXE;1 (section file)
0090 809AF920
SUNMUM$DUA0:[SYSCOMMON.SYSLIB]DECW$TRANSPORT_COMMON.EXE;1 (section file)
00A0 809C35A0 SUNMUM$DUA0:[SYSCOMMON.SYSLIB]DECW$DWTLIBSHR.EXE;1 (section file)
00B0 809BF340 SUNMUM$DUA0:[SYSCOMMON.SYSLIB]LBRSHR.EXE;8 (section file)
00C0 809DA5E0 SUNMUM$DUA0:[SYSCOMMON.SYSLIB]DECW$TERMINALSHR.EXE;1 (section file)
00D0 00000000 WSA2:
00E0 809D8EA0
SUNMUM$DUA0:[SYSCOMMON.SYSLIB]DECW$TRANSPORT_LOCAL.EXE;1 (section file)
00F0 00000000 NLA0:
0100 00000000 WSA2:
0110 00000000 NLA0:
0120 00000000 NLA0:
0130 809AF3E0 SUNMUM$DUA0:[SYSCOMMON.DECW$DEFAULTS.SYSTEM]DECW$TERMINAL.UID;1
0140 00000000 Busy MBA2172:
0150 00000000 Busy MBA2174:
Press RETURN for more.
SDA>
Process index: 002B Name: DECW$TE_2 Extended PID: 364002AB
--------------------------------------------------------------
Channel Window Status Device/file accessed
------- ------ ------ --------------------
0160 00000000 Busy MBA2177:
0170 00000000 Busy PYA118:
0180 00000000 Busy MBA2184:
0190 00000000 Busy PYA119:
01A0 00000000 Busy MBA2188:
01B0 00000000 Busy PYA120:
01C0 00000000 Busy MBA2192:
01D0 00000000 Busy PYA121:
01E0 00000000 Busy MBA2197:
01F0 00000000 Busy PYA122:
0200 00000000 Busy MBA2202:
0210 00000000 Busy PYA123:
0220 00000000 Busy MBA2206:
0230 00000000 Busy PYA124:
0240 00000000 Busy MBA2210:
0250 00000000 Busy PYA125:
0260 00000000 Busy MBA2214:
0270 00000000 Busy PYA126:
0280 00000000 Busy MBA2233:
0290 00000000 Busy PYA127:
02A0 00000000 Busy MBA2245:
02B0 00000000 Busy PYA128:
02D0 00000000 Busy PYA129:
SDA>
|