James,
Thanks for the direction and explanation. I will read it up on the ovw
process too. Thanks a bunch.
Our applications do not connect to the Netview map at all. I am just trying
to let our users close the Netview map and stop our own applications at the
same time for a bit nicer user interface. That is all.
> ----------
> From: James_Shanks@TIVOLI.COM[SMTP:James_Shanks@TIVOLI.COM]
> Reply To: IBM NetView Discussion
> Sent: Tuesday, October 10, 2000 9:00 AM
> To: IBM NetView Discussion
> Subject: Re: [NV-L] To exit netview gracefully as a Netview end user
> ( not root).
>
> I don't know which of us is more confused here, you or I. Let me try to
> elaborate on what puzzles me and perhaps I will answer your questions in
> the process or at lest allow you to clarify them. Perhaps if you told us
> (me) more exactly what your applications are trying to do, or how they
> work, this would be easier.
>
> (1). "ovw" is the overall map GUI. In actuality, the ovw command starts a
> process called ovw_binary and goes away. ovw_binary is the NetView GUI
> itself. It is all started with the "netview" command, which makes sure
> the
> environment is correct before calling ovw. If your application is not
> doing an OVwInit, then why would you need to kill an ovw process? That
> means it has no connection to the map. Presumably you did not start one.
> So why should you kill it? Normally, it is ovw which starts the
> application via a registration file. Then the application just exits and
> doesn't worry about ovw. The paradigm here is that he user starts ovw
> when he or she is ready, using the "netview" command, and determines when
> to bring it down the same way, with File -- Exit or the exit hot key.
> There is no automatic closure mechanism, and in fact, it normally pauses
> for confirmation on the way down, and to let all its subordinate apps
> close first. You can kill an ovw_binary process but that may leave such
> apps as ipmap and collmap, which are started by ovw, out there hanging.
> They should go away in time, but what you are doing here still doesn't
> make
> any sense so far.
>
> (2) f.exit is not available as a programming interface. In the ovw
> registration file this just provides a way to designate a hot key to close
> the window.
>
> (3) "ovstatus" can only be used for daemons, background processes, which
> have no connection to the ovw GUI. They have to be started by ovspmd and
> defined in the ovsuf file (you do ovaddobj to get then there after
> creating
> an lrf file). Such processes run independently of any GUI. Exiting a map
> has no effect on them.
>
>
> James Shanks
> Team Leader, Level 3 Support
> Tivoli NetView for UNIX and NT
>
>
>
> "Yang, Peter" <peter.yang@lmco.com> on 10/10/2000 07:18:58 AM
>
> Please respond to IBM NetView Discussion <nv-l@tkg.com>
>
> To: "'nv-l@tkg.com'" <nv-l@tkg.com>
> cc: (bcc: James Shanks/Tivoli Systems)
> Subject: [NV-L] To exit netview gracefully as a Netview end user ( not
> root).
>
>
>
>
>
> I am trying to figure out a way to exit Netview map gracefully along with
> my
> own applications. My own applications do not need to connect to "ovw" at
> all
> (i.e. no need of OVwInit() call).
> By reading the programmer's guide , my understanding is that I may use
> following appproach,
>
> 1. Find out my own "ovw" process and stop it with kill -9 < my ovw
> process>.
> This can be implemented by using a shell script file in the UNIX
> environment. But I am not sure what are the side effects ? This is a very
> simple approach and it works so far.
>
> Do I need to make sure the Netview database is closed properly at all ? If
> so, what is the proper Netview command to use ?
>
>
> 2. Find out and use Netview API calls to implement something like "
> f.exit"
> used in the ovw registration file. I have not found the proper call yet.
>
> 3. By following Netview process management method so "ovstatus" can even
> monitor my own applications process. So hopefully, when I exit Netview
> map,
> my applications will exit too.
>
> Thanks for any comment and direction.
>
>
>
>
> _________________________________________________________________________
> NV-L List information and Archives: http://www.tkg.com/nv-l
>
>
> _________________________________________________________________________
|