ITEM: AT9592

NetView - OVwInit problems (OVw_CONNECT_ERROR)

Question:

we developped an application integrated with NetView6000
in which some sub-application starts as initial command.

We had no problems within OpenView environment, but running
in NetView6000 some initial applications died as they called
"OVwInit()" API function, which is the very first call they do.

The number of applications calling OVwInit is 10.
Note that after a reboot all the applications start correctly,
but if we close ovw and re-call it, we can't avoid to obtain
OVw_CONNECT_ERROR from OVwInit for the three last applications
invoked at ovw-startup. This error is present in all subsequent
close-and-restart operation on ovw until reboot...

Answer:You might want to ensure that all of your applications call
OVwDone when they exit.  It is usually recommended that your
apps register for the ovwEndSession event, so that they can
call OVwDone and terminate when the user interface is closed.

If that is already being done, or if it does not solve the
problem, try stopping the user interface, the daemons (ovstop),
and tracing and loggin (nettl -stop), then deleting all files
in the /usr/OV/sockets subdirectory.




Support Line: NetView - OVwInit problems (OVw_CONNECT_ERROR) ITEM: AT9592

Dated: January 1996 Category: N/A

This HTML file was generated 99/06/24~13:30:24

Comments or suggestions?
Contact us