[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

501.0. "ENS: Display events & descriptive text " by FRSCS::ITWASP::WICH (Eckhard Wich, IT-OPS, DTN 861-3133 / @FRS) Thu Dec 01 1994 22:06

    Hi out there,
    
    I like to set up ENS in Console Manager to scan for certain ASCII strings, 
    (like error-messages etc).
    
    I there any _intelligent_ way to include parts auf the ASCI string 
    to be scanned in the descriptive text that may by given with any ENS
    event. I would like to avoid to type in any string twice! (Once in ENS
    when define a string to scan for, second time in an descriptive text
    given to the operators for example).
    
    Example:
    
    An ENS event XYZ_001 should be set up to scan message -F-WHATEVER.
    
    The descrptive text this message displayed in the ENS window should 
    - just an example - look like this:
    
    "This may be an order for the operator, message was '-F-WHATEVER'"
    
    
    Thanks for pointers & comments
    
    
    Eckhard

T.R Title User Personal
Name Date Lines

501.1 Text field and Performance SUPER7::HUGHESA Swimming against the tide @#%* Thu Dec 01 1994 22:40 19

T.R	Title	User	Personal Name	Date	Lines
501.1	Text field and Performance	SUPER7::HUGHESA	Swimming against the tide @#%*	`Thu Dec 01 1994 22:40`	19
	By default the event information field is displayed in the console eventlist (which I assume is what your operators are using ?). This field simply provides some generic information about the event. In order to see the text from the console that triggered the event it is necessary to see the text field. This can be achieved in two ways, firstly from the eventlist window you select the event and use MB3 to display the context of the event. The second method is to customise the eventlist list window to display the text field by default. This method however has some implications upon performance. In order to Console Manager to display the text field it has to read the information from the log files for each event. If you have alot of events or a large number of active eventlists you generate alot of I/O which can adversely impact performance, especially on a loaded system. SO BEWARE. Andy.

    
    By default the event information field is displayed in the console
    eventlist (which I assume is what your operators are using ?). This
    field simply provides some generic information about the event. In
    order to see the text from the console that triggered the event it is
    necessary to see the text field. 
    
    This can be achieved in two ways, firstly from the eventlist window you
    select the event and use MB3 to display the context of the event.
    
    The second method is to customise the eventlist list window to display
    the text field by default. This method however has some implications
    upon performance. In order to Console Manager to display the text field
    it has to read the information from the log files for each event. If
    you have alot of events or a large number of active eventlists you
    generate alot of I/O which can adversely impact performance, especially
    on a loaded system. SO BEWARE.
    
    Andy.