T.R | Title | User | Personal Name | Date | Lines |
---|
1313.1 | need a LAT trace | HAN::HALLE | Volker Halle MCS @HAO DTN 863-5216 | Thu May 22 1997 03:41 | 9 |
|
You'll need a LAT trace to find out what's going wrong...
Did you also 'wait long enough' when the jobs were in the STALLED state ?
The queue manager puts a job in the STALLED state, if there have been
no further IOs (to the printing device) within the last 30 seconds.
Volker.
|
1313.2 | Only occurs with Decnet Phase IV loaded | KAOT01::M_LAVERGNE | | Thu May 22 1997 09:21 | 2 |
| Like I mentionned in the initial note, the problem *only* occurs if
decnet phase IV is loaded.
|
1313.3 | HANGUP = LAT session aborted | HAN::HALLE | Volker Halle MCS @HAO DTN 863-5216 | Thu May 22 1997 13:36 | 15 |
| Mike,
'data set hangup' is signalled, if an existing LAT connection will be
aborted (CONTROL_Y AST delivered). So the initial connection
establishment seems to work (you could check this on the server with
SHOW PORT or SHOW SESS ALL).
If DECnet phase IV is running, the hardware address will be overwritten
with the DECnet address (check with ANAL/SYS & SDA> SHOW LAN/FULL).
Is there any bridge between the node and the server ?
So again, a LAT trace might show different data/adresses in the packets.
Can you connect from the server to the machine, if DECnet is running ?
Volker.
|
1313.4 | see troubleshooting info in note HAN::LOOPING_LATSYM 71.2 | HAN::HALLE | Volker Halle MCS @HAO DTN 863-5216 | Thu May 22 1997 13:36 | 1 |
|
|