This is not worthy of an apar but it is probably worth a warning, so
kids, don't try this at home:
You are trying to create a complex Smartset definition, and during
the test or the OK, it seems to hang, telling you your definition is
really bad. Rather than wait, you stop nvcold and kill the process
for the collection editor and collmap, if it has not already gone down.
Then you restart nvcold, and restart collmap using the Administer...
Start Application... collmap function.
When you finally get the definition right, it makes multiple copies
of the Smartset. Subsequent Smartsets also appear in multiples.
And members of this and other Smartsets appear in multiples.
Opening a new blue Smartset gives that popup dialog saying
that there is no child submap, but then it makes one. The multiples
disappear when you delete the Smartset symbols and they reappear
correctly.
It turns out that it is possible to get multiple instances of collmap
running. If you are not careful to kill collmap before restarting it,
it will add another one. I found 5 running the other day.
This may be new behavior in 7.1.1, maybe related to new
function for netviewd smartset processing. At any rate, if you
are going to use force, be thorough about it.
Cordially,
Leslie A. Clark
IBM Global Services - Systems Mgmt & Networking
HockeyTown
|