[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | POLYCENTER Console Manager |
Notice: | Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS: |
Moderator: | CSC32::BUTTERWORTH |
|
Created: | Thu Aug 06 1992 |
Last Modified: | Fri Jun 06 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 1541 |
Total number of notes: | 6564 |
695.0. ""Console link lost" revisited" by COMICS::MILLSS (All good things must come to an end...) Wed Apr 26 1995 18:06
I have a customer who has PCM V1.5 installed on a system that used to run VCS
V1.4. Console connections over LAT work OK, but direct, i.e. a single cable from
VAX to VAX, connections fail with the "CONSOLE LINK FOR SYSTEM LOST" message. At
the same time he gets a message from the audit server complaining of a Local
interactive login failure on the machine he's trying to connect to on the port
with the console connection, thus -
Proces name "_TXA4:"
User "<login>"
Owner Process "SYSTEM"
Terminal _TXA4:
Imagename LOGINOUT.EXE
Status %LOGIN-F-CMDINPUT, error reading command input
Any clues, anybody ?
BTW, VCS still works if he runs that up.
Simon R. Mills. VMS Group. South UK CSC.
T.R | Title | User | Personal Name | Date | Lines |
---|
695.1 | | YOSSAM::PHILIP | And through the square window... | Wed Apr 26 1995 18:14 | 8 |
| Simon,
Does you customer have the MUP installed, we did some work in the MUP (actually
I think it was in the ECO prior to the MUP) which reverted the behaviour back
to be the same as VCS.
Cheers,
Phil
|
695.2 | | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Thu Apr 27 1995 20:37 | 13 |
| The other thing you can do to prevent this is to place the following
command in SYLOGICALS.COM
SET TERM/PERM/NOTYPEAHEAD TXAx:
this turns off the typeahead buffer so that anything sent to the
console port of the service node - like opcom messages - won't induce
a login. This same thing could happen with VCS by the way.
Regs,
Dan
|