[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference csc32::consolemanager

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

1392.0. "PCM using a vt340" by SALEM::ARNOLD () Mon Sep 23 1996 06:56

    I'm running PCM v1.6 with ECO 2 on a 1000a with Digital Unix 3.2G.
    
    PCM was set up using a graphics monitor. The customer will be using 
    a vt terminal at the customer site.  I took the graphics monitor
    off the machine and booted using a vt terminal.  When I do a 
    console conn node I connect to the node but my output is messed up.
    
    Example:
    
    
    login: root
    root
    Password:test
    
    #
    
    #
    
    The command line recall also dosen't work because the up arrow just
    moves up a line rather than recalling the last line.  The vt terminal
    is a vt340.  I know it's not the decserver because I can create
    a service on it and connect to the node and everything works fine.
    
    DECSERVER setup:
    
    Network Access SW V1.5 for DS700-16 BL95D-34 ROM V4.0-0 Uptime 1 16:12
    
    Address:  08-00-2B-9E-A7-B3    Name: PDC            Number:      0
    
    Identification:
    
    Circuit Timer:	80	Password Limit:		3
    Console Port:	 1	Prompt:		   Local>
    Inactivity Timer:	30	Queue Limit:	      100
    Keepalive Timer:	20	Retransmit Limit:	8
    Multicast Timer:    30	Session Limit:	       64
    Node Limit:	       200	Software:          WWENG2
    
    Service Groups:	0
    
    Enable Characteristics:
    Announcements,  Broadcast,  Dump,   Lock
    
    Local> show port 2
    
    Character Size:	  	8	Input Speed:		9600
    Flow Control:	      XON	Output Speed:		9600
    Parity:		     None	Signal Control:     Disabled
    Stop Bits:		  Dynamic	Signal Select:CTS-DSR-RTS-DTR
    
    Access:		   Remote	Local Switch:		None
    Backwards Switch:	     None	Name:		      PORT_2
    Break:		   Remote	Session Limit:		   4
    Forward Switch:	     None	Type:			Ansi
    Default Protocol:         LAT	Default Menu:	        None
    
    Preferred Service: None
    
    Authorized Groups:	0
    (Current) Groups:	0
    
    Enable Characteristics:
    Failover, Input Flow Control, Lock, Loss Notification, Message Codes,
    Output Flow Control, Verification
    
    I'm also having a problem when PCM starts up.  I see the 
    
    Clearing out Temporary Directory
    
    Starting Console Manager Processes.
    
    during the startup phase but I still have to do a console_startup
    before I can connect to any of my nodes.
    
    If anyone has seen these problems before I would appricate any
    help you could provide.
    
    Howard
          
T.RTitleUserPersonal
Name
DateLines
1392.1MEOC02::sjrvms.meo.dec.com::rollersimonMon Sep 30 1996 19:1517
Howard,

I had the same problem on a customers site when I installed PCM/PSW on a 
Unix environment. I was getting corruption on the console connect. I fixed 
the problem by removing most of the terminal attributed concerning loss 
notification, flow control and messaging (ie the last two lines of the show 
port command!). I don't know if this is a supported thing to do, but it 
sure worked for me!

I can't help you with the othe problem, good luck. There have been a number 
of problems in starting up and shutting down console manager on Digital 
Unix. Have a look at the conference at problems with shared memory.

Good luck.

Simon Roller - SI Melbourne