| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 877.1 |  | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Tue Jul 18 1995 18:43 | 10 | 
|  |     >One specific question is:  can PCM pass messages/events to PNV?
    
    Yes, but your probably going to have to write some code. Getting events
    into PCM is the easy part. It's getting things out of Netview that will
    require most of the work. Personally, I don't know of anything that
    exists already.
    
    Regards,
       Dan
     
 | 
| 877.2 |  | SNOFS1::ELLISS | Are you all sitting too comfybold square on your botty? - Then w | Wed Jul 19 1995 02:19 | 7 | 
|  |     actually, getting events from netview into PCM isn't that hard, if they
    are on the same system. You can have a pseudo terminal doing a 'tail
    -f' on the netview event log file. So, when a new event happens, you
    can pick it up. Problem is, of course, that the nodename will always be
    something like 'NETVIEW'.
    
    Shaun
 | 
| 877.3 | Piece o' cake | GLRMAI::WELLINGTON | Larry Wellington NSM Tech Support | Wed Jul 19 1995 13:44 | 23 | 
|  |     Actually, passing messages from PCM to PNV is no more difficult than
    having PCM send mail to somebody IF you have the additional software to
    do it.  The key piece is the event handling capability which ships with
    the POLYCENTER DECnet Manager kit.  If you have this, you can use an
    action routine I have developed called SEND_TRAP (shamelessly copied
    from the SEND_MAIL action routine which ships with PCM).  This can
    cause event cards to come up in the PNV display, and change the icon to
    one of six designer colors (based on the priority level set in PCM).
    
    The PCM kit ships with a registration file which automatically includes
    Console Manager in PNV's Tool Palette and Tools pull-down menu.  This
    includes basically launch of the C3 interface.  I have enhanced the
    registration file so that you can launch a console connect directly
    from PNV.
    
    You are welcome to any and all of my enhancements.  They are included
    in the POLYCENTER Integrated Demo kit, which can be obtained by
    anonymous ftp from nsmweb.tay.dec.com.  Look in directory pub/demo_v22
    for demofiles.tar.  Copy this file over, un-tar it, and look for the
    files /usr/demofiles/pcm/send_trap and /usr/demofiles/demo_control
    (look especially at the CPUconnect action).  Further instructions can
    be found in TOOK::POLYCENTER$PUBLIC:[OSFDEMO]SCRIPT2.PS.  See step 6 on
    page 2-7.
 | 
| 877.4 |  | CSC32::BUTTERWORTH | Gun Control is a steady hand. | Wed Jul 19 1995 18:58 | 10 | 
|  |     Very interesting guys!!! If I read this correctly, all of the previous
    are shell script based then? What I would like to see is an executable
    based action routine ala Mutli-Line Window that uses the PCM and PNV
    API's. For the larger enterprise that is managing a large network where
    many events are likely, it is much more efficient to have an executable
    action routine that uses the socket based IPC mechanism inherint within
    the PCM ENS facility. Is anyone working on this? 
    
    Regards,
       Dan
 | 
| 877.5 |  | SNOFS1::ELLISS | Are you all sitting too comfybold square on your botty? - Then we'll begin | Thu Jul 20 1995 01:04 | 9 | 
|  | Dan,
OSCint ( a tool the basically provides much integration between POLYCENTER
products and is about to become a European Asset) has a module (executable) for
sending events to PNV from PCM (It also integrates PSW).
I suggest you look at it
Shaun
 | 
| 877.6 |  | 52483::RIVET |  | Fri Jul 28 1995 04:36 | 12 | 
|  | Mike, Dan,
The Action Routine (an executable) provided by OSCint uses the Collector API
(mcc_send_event).
Do not hesitate to contact us if you need more information or if you want to
organize some tests/demo of this action routine (or of the whole OSCint) for
your customer.
   Christian Heusbourg - OSCint project Leader (AZUR::HEUSBOURG)
   Evelyne (AZUR::RIVET)
 |