[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

1306.0. "raid monitor swxcr thru pcm ugly" by CSC32::PITT () Fri May 24 1996 10:42

    
    
    PCM 1.6-100 on Dunix. DECserver90tl (version as yet unknown). 
    
    Customer states that when he runs the raid utility "swxcr mon xcr0"
    thru a console monitor port he gets alot of garbage output and loses
    his function keys. 
    
    Has anyone else successfully run swxcr thru pcm???
    
    thanks.
T.RTitleUserPersonal
Name		DateLines
1306.1CSC32::BUTTERWORTHGun Control is a steady hand.Fri May 24 1996 16:477
    Cathy,
      I assume you mean he ran it through the CONNECT interface? The
    MONITOR interface doesn't interpret esc sequences so the output would
    look wierd. We could also try and reproduce the problem here.
    
    Regs,
       Dan
1306.2Boy, am I glad some else has seen this!PRIME8::VAUGHNMike Vaughn DTN 339-5325Tue May 28 1996 17:1120
Hello -

	I also have a customer with a SWXCR problem.  His problem is a little
different.  Apparently to accomodate VT's as consoles on the 1000A, we included
a utility on the Raid Configuration Utility diskette called SRLMGR.EXE.  This
program is analogous to the SWXCRMGR.EXE that has always been included, except
that it is designed for VTs instead of the graphics console.  We have 4 1000A
systems set up through a PCM.  from the console prompt (of the 1000A), he runs
SRLMGR, and receives (mostly) garbage output.  This seems to be the only utility
that is causing him any problems (he can manage the system normally from his
PCM).

	I'm going to the customer site early Thursday morning, and will provide
additional details (like exactly what is shown on the screen, what keys are
inoperative for typing, etc.).  In the meantime, any ideas on where to start
looking for problems?

Thanks.

mike
1306.3CSC32::BUTTERWORTHGun Control is a steady hand.Thu May 30 1996 01:5710
    Yep,
       I'd bet money that it's sending 8-bit ascii control sequences and
    they are using LAT protocol to the terminal servers. The LTA devices
    PCM creates set the terminal to NOEIGHTBIT. ECO 3 (which is currently in
    the bullpen waiting to be released) has been changed so the lta devices
    are set EIGHTBIT.
    
    
    Regs,
       Dan
1306.4TTY_DEFCHAR=402690720STAR::JFRAZIERWhat color is a chameleon on a mirror?Thu May 30 1996 10:034
Also see note 853.6


James	:-)
1306.5CSC32::BUTTERWORTHGun Control is a steady hand.Thu May 30 1996 13:243
    That'll work too!! Thanks for reminding me of that!!
    
    Dan
1306.6Thanks...PRIME8::VAUGHNMike Vaughn DTN 339-5325Thu May 30 1996 14:079
Actually, it turns out the customer didn't implement the changes I told her to
make.  It turns out that when we changed the DECterm she was using on the
workstation (via Options, General) to VT300 mode 8-bit controls, VT320 ID,
things worked fine.  The arrow keys worked, screen paints were OK, etc.

Oh, this PCM system is using Digital UNIX; the VMS modparams changes referenced
in 853.6 weren't applicable (but thanks for the pointer).

mike