Conference csc32::consolemanager

Andy,

  I take it this is the monitor interface I asked you to try out
  with the initialization file fixes. I will take a look.

Cheers,
Phil

See note 293 for another report on the Monitor initialization file.

I have had 2 customers today call about CTRL_P not working on their big
vaxes.  It would be solve this problem if the default value for BREAK could
be something other than CTRL_P since these are both HALT characters ... just
for different type processors.

Regards,
Connie  

Connie,

  Setting any of the control keys in the initialization file is now
  fixed, the fix will be available in the patch kit. As for the defaults
  and the confusion, I propose to leave the PCM V1.5 defaults as they
  are, I have described what I have done for the next release elsewhere
  which removes this confusion.

Cheers,
Phil

Thanks Phil!

    HELLO...
    
    	I have just installed a new copy of PCM v1.5, and the MUP 1.5a onto
    a VAX3100 model 38, with 16 meg of memory.  (the only spare machine the
    customer has at the site), and am managing the consoles of 8 Big VAXes
    9000, and 7000, and some 4000's.   
    
    I have the CTRL-P problem on the VAX 9000 and 7000 (they don't respond 
    when I answer "Y" to "Do you wish to send a break".  I have tried
    
    command: console connect /break=ctrl_K bigvax
    
    but the control-P  still gives me the break question.  I don't know
    which files are the initialilzation files.    But I would like to have
    the four VAX9000's have control-P working (Break sends a 9000 into
    SProm mode or something.)  And I would like to have the 4000 series
    VAXes use the break, since I can get the >>> prompt correctly on them.
    
    
    How do I define permanently each node's appropriate halt sequence, so
    that the system operators don't have to type long ascii strings?  My
    goal is to have them double-click the icon of a VAX900, and be able to
    halt it from the window that pops up, and not have to control-G and
    type a weird connect command each time.
    
    Also, I cannot figure out the ENS systesm to save my life.  I have read
    the users guide.  I have downloaded some sample VAX9000 scans.  I have
    looked at the console data from several VAXes, and I cannot get ANY
    events to show up in the eventlist, except CONSOLE CONNECT, DISCONNECT
    in the green text, and occasional purple RECONFIG messages, after I
    have finished creating EVENTS, filter, scans, and assigning them to a
    single or multi-line window.
    
    I would like to have an event notification show up somehow, but it does
    not.  I was thinking that my VAX might be underpowered.   It is always
    at 60 or 70%  CPU utilization.  IF I open more than ten consoles in
    Monitor mode, the response slows to three or four minutes between mouse
    click and screen update.   But with one or two windows open, the
    response is not bad.   
    
    I am going to the site again today, to help the customer get contol-p
    working, and to try to make the ENS notification work.  Since I have
    not been able to get any actions to occur, the customer wants to know
    how to see the raw console data for the last few hours.   I told him to
    try the history, or the achive, but those are just filled with the
    silly green text of CONNECT and DISCONNET messages.   Where are the
    actual scroll windows for the last two or three hours of console raw
    data ?   I found a flat ascii file with ALL of the console data from
    each node in CONSOLE$LOGFILES, but it takes forever to do a SEARCH
    command on that file, cause it seems to include all of time.
    
    What file do I edit for each node, to define the appropriate inital
    behavior for the "halt sequence?"
    
    thanks for any help.
    
    JR
    

    CONSOLE EXTRACT will allow you to review the data in the console
    logfiles. This command has /SINCE and /BEFORE qualifiers.
    
    To get ctrl-p to at least work from the Monitor do the following
    at the command prompt:
    
    Command: SET BREAK CTRL_K
    
    When you do a CONNECT from the Monitor it will now pass through 
    CTRL-P as you desire. 
    
    The Monitor init file is called CONSOLE$MONITOR_INIT.DAT and it must
    reside in SYS$LOGIN. See chapter 6, section 3 of the PCM Users
    Guide for more info.
    
    To set the defaults in the C3, you must turn C3 edit mode on. Then
    place the mouse pointer over a node icon and press MB3 and selct Modify
    from the resulting menu. From there it's pretty obvious what to do. Be
    sure and save the settings from the Options menu on th C3 menubar.
    
    Regs,
      Dan

    Thank you very much.
    
    I used the C3 method, and edited the pull-down window node BREAK sequence 
    on the big VAXes to CTRL-B, and the halt routine ^p now works as the 
    customer expects.  The Mouse button THREE stuff did not jump out at me
    from the documentation that I saw.   Now that try it, it's wonderful,
    but a shame that EXTRACT was not somewhere on some other primary
    windows menu, like all of the other options under mb3.
    
    I appreciate the help.   I had read the notes, and could not figure out
    how to make the break control stick beyond one session.
    
    I will go to another thread for help on the ENS system.
    
    
    Thanks again.
    
    JR