Conference csc32::consolemanager

    Didier,
      The problem here is within the Multi-Line Window action. It can
    either use the "default" acknowledge string or you can change the
    string via the Options-> General menu path.  Bear in mind that this is
    a "fixed" value - you can't feed arguments to it.  
      
    
    Now, I've got an idea how you can sort of accomplish what you want but
    you'll have to write some code to do it. The Multi-Line Window allows
    you to display "who" acknowledged or cleared a message via the
    Options->Startup menu path. The CMUserAcknowledgeEvent routine allows
    you the user to specify "who" is acknowledging the event. So, you will
    have to write an action routine to receive events that you are
    interested in. You'll also have to provide that action routine with a 
    "user" interface so that an operator can acknowledge an event.
    
    Regards,
       dan

Dan,

isn't it possible to add other 'actions' to the list of things you can
do, such as clear events, etc. So, you could write an action here that
send an acknowledge event from there.

Shaun

    
    Hi Shaun/M ,
    
    Yes you can , it is undocumented and unsupported but works just fine
    We are managing On-line help as well as Dynamic action menu with it.
    Contact me by mail if you need it.
     
    Hope you're well down under
    
    Pierre

    Shaun,
      I'm assuming you mean having a filter that traps the Acknowledge
    internal event? If so then yeah you could do it that. This may be what
    -1 is talking about.
    
    or do you mean augmenting the Eventlist' pop-up menu?
    
    Regs,
      Dan

Dan,

I was talking about what Pierre refers to in .3, extending the drop down
menus.

Pierre,

Ca va, mon ami?

Life here is good - no, better than that - great! ;^) What can I say?

More money
Less Tax
Better Weather
Better way of Life
Friendly People
Great Scenery

Other than that - it sucks!

Yes, I'd like to get hold of what you've done with PCM

Why don't you document it and make it available, or get it added to OSCint?

Shaun

    Dan, Pierre, Shaun,
    
    If it is possible to add an option to the pop-up window, which
    currently contains the 4 options:
    - Acknowledge selected event
    - Clear selected event
    - show context of selected event
    - remove events ...
    then I would be glad to know how to do it. 
    
    A customer recently asked me if it would be possible to select an event
    and to feed it in a call-handling system or a knowledge base. If the
    undocument/unsupported feature exists that makes it possible to add
    your own options in there, I'll love the multi-line eventlists even
    more.
    
    Thanks a lot in advance for the info.
    
    Johan
    

    
    	Shaun, Dan, Johan,
    
    	
    	Yes , it was planned by Christian Heusbourg to add these features
    to the next Oscint Release but now things have changed due to
    CA-alliance (see with Christian if you need a new Oscint release with
    it and if he can handle this).
    
    
    	Meanwhile you will find below instructions to add actions to the
    	eventlist popup window , thanks a lot to phil Baxter (who didn't have
    time to add more parameters to it which he planned to do !
    
    ****************************************
    	If you create the file CONSOLE$EVENTLIST_POPUP.DAT in your
    SYS$LOGIN:
      directory (.console_eventlist_popup in the users home directory on
    Unix), and populate this file with entries which look something like
    the following:-
    
    MENU_ENTRY:
      MENU_NAME: Repair
      MENU_COMMAND: OSC$SYSTEM:OSC$MANUAL_REPAIR.COM
    MENU_END:
    
    MENU_ENTRY:
      MENU_NAME: Another menu entry
      MENU_COMMAND: OSC$SYSTEM:OSC$another_one.COM
    MENU_END:
    
      Now, if the Eventlist window is started interactively and not as an
    action,
      i.e. $ CONSOLE EVENTLIST/NODE=xxx/SERVER=0/SCREEN=0/TRANSPORT=TCPIP,
    then
      one you use mouse button 3 with the cursor positioned over an event,
    the
      popup menu will (in this example) have one extra entry, "Action"
    and then two sub-entries "repair" and "Another menu entry". 
    Selecting one of these menu entries will spawn a
      process to run the command specified in the menu entry.
    When the command runs, it is passed as P1, P2 ( $1, $2..)etc the following
    items...
    
            "Event Name" "System" "Sub-system" "Priority" "Info"
    
      (then you can get the Class and Group information if needed)
    
      If you want to use it thru a multi-line window started thru a filter
    	place the menu file in console$app-defaults or
    /var/opt/console/app-defaults.
    
    **************************************************************
    
    Some remarks :
    
    	- Date and time of the event is not passed as a parameter which
    makes the log of an event to a Caal-handling system less easyer (but 
    based on oscint histo log there are ways of doing this)
    
    	- Some customers are using this to get an on-line doc thru the
    eventlist which appears to be very useful (even one of these customers
    has defined the doc based on system and event like
    nodename_eventname.doc file opened thru dxnotepad to tell what to do if
    something happens on a specific system)
    
    	- for another one we are printing on-demand problem form with all
    	the information related to the event
    
    	- another asked us to see the last occurences of this kind of event
    	which is "i can do it when scrolling-up because it is too late",
    	Then the search/grep in oscint$histo and dxnotepad makes it easy to
    do.
    
    	- re-direction of the display has to be done when starting this
    from a non-pcm host (we managed to make it work on Vms and Unix thru
    some scripts)
    
    	- A customer was requesting a dynamic menu activated from the popup
    	menu to select and start an action interactively. Using the filter
    	and defining no time in the dispatch table we managed to make this
    	works : any action with no time specified which matches the filter
    	of the selected event of the evntlist will be displayed in a Menu
    	and can be started (oscint poke does the rest). Contact me by mail 
    	for exec and details.
    
    
    Lastly these features gives the customer the opportunity to go
    increasingly towards automatic action :
    
    	- first document the action , operator will do it
    
    	- then make it available thru menus , operator will start it
    
    	- if Ok make it automatic which is simply put valid timeframe in
    	the filter dispatch table.
    
    
    I am sure you will find many other actions to add to the popup menu.
    
    
    But remember what Phil said it is unsupported ( but it works and it was
    missing in our products and available in other ...hp, Patrol....)
    
    Hope i made myself clear
    
    Enjoy it
    
    Glad you're well Shaun 
    
    Pierre 
    

    Since this is a nice feature I would suggest you send a message to
    
    ALEXWS::LASER
    
    to suggest that this feature be supported and documented.
    
    Regards,
       Dan

    Pierre, Dan, Shaun,
    
    That's indeed great stuff. Thanks a lot.
    
    I'm sure many of our customers will be interested in exploring this
    feature. 
    
    Documenting and supporting would indeed be highly recommended.
    
    Thanks again and best regards,
    
    Johan

    	Hello,
    
    	I tried the new multiligne window with help on line on Unix
    	V3.2D. It works fine at the beginning but as soon as I receive
    	a lot of messages, my window disapears.
    	Thanks for any idea
    
    	Didier