[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

686.0. "Basic usage help needed" by OAW::MATUSZAK () Fri Apr 21 1995 03:02

I understand in general what PCM does (or I think I do), but I'm 
a bit at sea regarding how to effectively use the product.  Is there
an overview, cookbook, or tutorial available anywhere?  Using the c3 
interface, for example, I was able to identify the occurance of an event
(although I don't understand the hierarchical relationships among scans, 
filters, ... )
and watched the system icon change color.  But several things puzzle me.

1. Now what?  If I acknowledge the event it gets removed from the event
list (even though I can't clear it explicitly) 

2. The small "scroll" icon also changes color ???

3. If I trigger the event and later bring up the c3 interface, the
icon is normal color (as if the event had never occured)  I thought
that upon activating the display, system icons for systems that had 
experienced a "significant" event would indicate this by a color other
than the default.

Without PCM, the system manager would be advised that a problem exists,
physically go to the system console and read the output.  It made 
sense to me that PCM would function analogously.  An event occurs,
the system manager(s) are notified via an action routine, and upon 
activation of the c3 display any system "in trouble" would be flagged 
with a change in color.   The system manager could then connect to the 
problem system's console and fix the problem.  Am I missing the point?

I realize that this is very basic stuff, but I have to start somewhere.
Learning how to use PCM with bookreader is like learning to speak
a foreign language by reading a translation dictionary.  I know 
what it means to filter (as in oil filter), or filter out (as in low-pass,
high-pass, bandpass), but "filter on" ?????

Thanks in advance for any help.

Ed

T.RTitleUserPersonal
Name
DateLines
686.1CSC32::BUTTERWORTHGun Control is a steady hand.Fri Apr 21 1995 05:0891
>I understand in general what PCM does (or I think I do), but I'm 
>a bit at sea regarding how to effectively use the product.  Is there
>an overview, cookbook, or tutorial available anywhere?  Using the c3 
>interface, for example, I was able to identify the occurance of an event
>(although I don't understand the hierarchical relationships among scans, 
>filters, ... )
    
    I thought we had talked about these relationships in another note??
    
>and watched the system icon change color.  But several things puzzle me.
>
>1. Now what?  If I acknowledge the event it gets removed from the event
>list (even though I can't clear it explicitly) 
    
    You may tune eventlist so that when an event is acknowledged that it
    isn't removed from the display until you explicitly clear it. To 
    perform this customization pull up the Options menu and select
    "General". In the lower part of the screen are several buttons
    labeled "Acknowledge removes event" (which is "pushed" by default) and
    "Clear removes event (which is not pushed by default). What you want to
    do is release the former and push the latter. Don't forget to do an
    Apply and then a Save from the Options menu.

>2. The small "scroll" icon also changes color ???
    
    Thats the default icon of the Eventlist Window and it does indeed
    change color. This is tuneable also inthe General options via the
    radio buttons "Use Highest Priority Color" and "Use Latest Priority
    Color".

>3. If I trigger the event and later bring up the c3 interface, the
>icon is normal color (as if the event had never occured)  I thought
>that upon activating the display, system icons for systems that had 
>experienced a "significant" event would indicate this by a color other
>than the default.
    
    Nope. Applications such as the C3 and Eventlist receive events in
    "realtime". If they don't happen to be running when an event occurs
    then they don't see it. The event has been logged however and may
    be reviewed via CONSOLE EXTRACT/EVENT. The Mail action is good solution
    to this problem. You can setup the Mail action to send mail to 
    several users when an event occurs. This of course doesn't rely on
    the C3 or Eventlist or the user even being logged in to the PCM engine.
    You can also write your own actions to do whatever you want. Some sites
    run action routines that can page someone when an event occurs.

>Without PCM, the system manager would be advised that a problem exists,
>physically go to the system console and read the output.  It made 
>sense to me that PCM would function analogously.  
    
    Thats exactly how it functions. More below.
    
    >An event occurs, the system manager(s) are notified via an action 
    >routine, and upon activation of the c3 display any system "in trouble" 
    >would be flagged with a change in color.   The system manager could 
    >then connect to the problem system's console and fix the problem.  
    >Am I missing the point?
    
    I think that you have some misconceptions as to how it all works. The
    explanation above regarding how the applications receive events should
    help here. Another thing that you may be missing is that action
    routines such as Eventlist (aka Multi-Line Window) can tell you 
    what system caused the event to be triggered. This is a customization
    in the Startup menu which can again be gotten to from the Options menu.
    The Mail action sends you a message with the system name, time, text
    and several other fields.
    
    Knowing this, a system manager could setup eventlist to display on the 
    workstation in his/her office and only display the parts of the event he/she
    considers relevant. An event occurs, the eventlist display is updated
    or a mail message sent and the system manager would then have the
    info needed to connect to the PCM engine and look at whats coming out of 
    the console via the Monitor/Connect/Extract interfaces.
    
    
>I realize that this is very basic stuff, but I have to start somewhere.
>Learning how to use PCM with bookreader is like learning to speak
>a foreign language by reading a translation dictionary.  I know 
>what it means to filter (as in oil filter), or filter out (as in low-pass,
>high-pass, bandpass), but "filter on" ?????
    
    
    I know someone asked this just a while back and I thought it was you.
    Did you see it?
    
    Regs,
      Dan


Ed