[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

599.0. "Problems after consolemup015 being applied?" by KERNEL::BOWENS (I'm sorry BUT...) Mon Feb 06 1995 14:57

    Hello Folks,
    
    I have a customer who seems to have found a few problem areas on PCM 
    V1.5 even with the mup consolemup015 being applied.
    
    Please could somebody advise me on a workaround for any of them or
    confirm that they need to be run through the IPMT channels.
    
    Problem List:
    
    1. When events are sent they appear to be recognised by the ENS and the
       system icon is turned the appropriate colour and a shortened text
       message is displayed at the bottom of the C3. When trying to see more
       information about the event by double cliking on the system icon it 
       does not show the event in the list. The current work around is to try
       to restart the PCM.
    
    
    2. Console sometimes does not respond to the keyboard input when using
       the CONSOLE MONITOR or the CONSOLE CONNECT command. Tihs can be
       fixed by diconnecting and reconnecting the console cable which runs
       from the terminal server to the hardware console.
    
    3. When using the CONSOLE MONITOR command if the user types too quickly
       sometimes the system displays only part of what has been typed in
       and adds a character for each additional character typed in,
       including ^G which should bring the user back to the command prompt,
       and leads the user to thinking that he has not typed in all of the 
       commands and continues typing and eventually makes the command
       invalid. This is particularly annoying when attempting to shut a 
       system down.
    
    4. When PCM archieve data it does not seem to check that there is
       sufficient space on the disk which it is trying to archive to and
       can cause that disk to run out of space and the system to hang.
    
    
     Thanks in advance for any help you can give me.
    
     Regards,
    
     Susan Bowen
     Basingstoke CSC
T.RTitleUserPersonal
Name		DateLines
599.1CSC32::BUTTERWORTHGun Control is a steady hand.Mon Feb 06 1995 17:4457
>    1. When events are sent they appear to be recognised by the ENS and the
>      message is displayed at the bottom of the C3. When trying to see more
>      information about the event by double cliking on the system icon it 
>       does not show the event in the list. The current work around is to try
>       to restart the PCM.

Are you saying thatyou cannot retrieve the events context or the actual
event line itself or both? 
    
    
>    2. Console sometimes does not respond to the keyboard input when using
>       the CONSOLE MONITOR or the CONSOLE CONNECT command. Tihs can be
>       fixed by diconnecting and reconnecting the console cable which runs
>       from the terminal server to the hardware console.

This smells like a flow control issue. I'm assuming that you are using terminal
servers as the interconnect method so could you post the results of a 
SHOW PORT command from terminal server? We're looking to see if both input and
output flow control are enabled and that the flow control is set to XON.
    
>    3. When using the CONSOLE MONITOR command if the user types too quickly
>       sometimes the system displays only part of what has been typed in
>       and adds a character for each additional character typed in,
>       including ^G which should bring the user back to the command prompt,
>       and leads the user to thinking that he has not typed in all of the 
>       commands and continues typing and eventually makes the command
>       invalid. This is particularly annoying when attempting to shut a 
>       system down.

It sounds like you are really in the CONNECT interface direclty via DCL
or you CONNECTed from the MONITOR. Regardless, this could be related to 
problme 2 above. I had a similar problem once with VCS and what we found was
that the customer had set SYSGEN params TTY_ALTYPAHD = 100 and TTY_ALTALARM
to 320 and it was intended that TTY_ALTALARM be set to 1000. These parameters
define the size of the alternate typeahead buffer and it's xoff threshold.
Check the settings of these parameters.
    
>    4. When PCM archieve data it does not seem to check that there is
>       sufficient space on the diskwhich it is trying to archive to and
>       can cause that disk to run out of space and the system to hang.

What the customer needs to do is create a filter that is filtering the
event CMgr Archive Area Full. You would set the filter up to dispatch the
Archive Cleanup action command file. This file subtracts 2 days from the
current time and then deletes any archive files older than that. You can modify
the command file and change this threshold if you don't like the default. This
procedure needs only 1 argument which is the location of the archive area. 
    
    

    
     Regards,
    
        Dan
     Basingstoke CSC