[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

527.0. "ctrl_p does not work" by JGODCL::SYS_MJANSSEN (Marc Janssen (889-9594)) Tue Dec 20 1994 21:36

    We just started using PCM version 1.5.
    
    After 1 week of usage, we noticed that 
    CTRL_P dit not work at all, to eventually get the ">>>"
    prompt after a shutdown. The keys are defined correctly.
    Can anyone think of a reason why this does not work?
    
    
    Another thing that bothers me: We had a VCS connection to a DEFENDER.
    All data got logged fine, and some reports were made from a "review"
    session.                                                      
    Since  we have started testing PCM we noticed that no "console" data is 
    logged to the logfiles, unless you actually do a "console connect defend" 
    in aninteractive session.
    What could be the problem here?
    
    
    Note: I have not yet installed the ECO.
    
    Any suggestions are welcome.
    
    Thanks in advance,
    
    Marc
T.RTitleUserPersonal
Name		DateLines
527.1OPG::PHILIPAnd through the square window...Tue Dec 20 1994 22:0016
Marc,

  I would first suggest that you install the MUP announced in note 2.last

  Next check that control_p is sending a control_p and not a break.

  Finally, do you have logging enabled, if so, is your DEFENDER set up for 
  eight bits no parity (a workaround for 7 bit, even or odd parity is in the 
  MUP, see the release notes). Also, are you sure the data is not being logged, 
  in the SSB kit, unless there was an event or someone connected to the system, 
  the data was not flushed to disk by the daemons, the MUp changes this by 
  flushing the data every 30 seconds.

Cheers,
Phil
527.2CTRL_P on VAX6000 systems...?JGODCL::SYS_MJANSSENMarc Janssen (889-9594)Wed Dec 28 1994 15:2524
    I installed the MUP today.
    
    Unfortunately I am still not able to ctrl_p some nodes. 
    
    I succeeded to ctrl_p a VAX 4000-200 system, but it seems that
    VAX6000 type of systems suffer from this problem.
    
    How do I check whether "CTRL_P" is sent and not a "BREAK"?
    
    Suggestions are highly appreciated.
    
    Btw: If I do a "show key" I get:
    
    Key         Current Value
    ---         -------------
    EXIT_KEY    CTRL_E
    ESCAPE_KEY  CTRL_G
    REFRESH_KEY CTRL_W
    BREAK_KEY   CTRL_P
    
    
    Thanks in advance...
    
    Marc
527.3OPG::PHILIPAnd through the square window...Wed Dec 28 1994 16:5711
Marc,

>>>    BREAK_KEY   CTRL_P

  This tells me that you are sending a BREAK signal when you type CONTROL-P 
  so if the system is expecting a control P it will not halt!!!

  Try doing SET BREAK CTRL_I and then see if CONTROL/P works.

Cheers,
Phil
527.4That did the trick...JGODCL::SYS_MJANSSENMarc Janssen (889-9594)Thu Dec 29 1994 11:029
    That did the trick.
    
    Thanks for your support!
    
    I must have mist it in the doc's or help. Perhaps it is a good idea
    to be more specific about this issue in future releases of
    documentation and/or on-line help.
    
    Marc
527.5OPG::PHILIPAnd through the square window...Thu Dec 29 1994 19:567
Marc,

  It will be completely different in the next release, so much so that it 
  should be almost impossible to get wrong!!

Cheers,
Phil