A deamon will have status "unstartable" if any of the other daemons it
depends upon are down.  For example, ovtopmd and netmon depend upon trapd.
If trapd is not up, or cannot come up, then the other two will have the
status "unstartable".    You need to do an ovstatus for all the daemons and
see which ones are failing to start -- usually there are exit codes and
last messages to give you a clue.

The most common daemon which has a starting problem in NetView V5.1 is
ovtopmd.  This is because it must have access to the Tivoli library path
when it starts.  If you are seeing that ovtopmd will not start when you do
ovstart and the exit code is 255, this is almost certainly the cause.   You
must source the Tivoli environment before starting any of the daemons, or
ovtopmd will not inherit the correct environment from ovspmd.  If you find
yourself in this situation, then you must stop all the daemons, source the
environment, and restart them:

(1) ovstop nvsecd    (this brings down nvsecd and every other daemon)
(2) .  /etc/Tivoli/setup_env.sh    (don't forget the dot and the space at
the start of this command)
(3) ovstart

James Shanks
Tivoli (NetView for UNIX) L3 Support



Goran Saradzic <gorans AT US.IBM DOT COM> on 02/22/99 11:34:20 AM

Please respond to Discussion of IBM NetView and POLYCENTER Manager on
      NetView <NV-L AT UCSBVM.ucsb DOT edu>

To:   NV-L AT UCSBVM.ucsb DOT edu
cc:    (bcc: James Shanks)
Subject:  Problems with ovstart on NetView 5.1: gives deamons UNSTARTABLE,
      have to reboot.





Hi everyone,

I was wondering if anyone has had similar problems and found fixes.  Many
times when we are troubleshooting NetView we restart all deamons but with
5.1, they are unstartable.



Please respond directly and to the list.



Thanks.

---------------------------------------------------------------------------
--------------------------
Goran Saradzic - IBM Global Services Network Management Group
email: gorans AT us.ibm DOT com                          phone: (303) 924-2444