RE: [nv-l] NetView Custom Script

[James Shanks <jshanks@us.ibm.com>]

Let me amplify what Federico has said.

Basically you don't pass anything in.
 Actions driven from the NetView GUI are either parameter independent
or they work by having the operator select a node from the map first.  The
selected object is passed in the form of a selection name $OVselection1.
 Now it is up to the command or application you have specified to
do the rest.

  If the application is already
written and requires command line input, then you have to launch it with
a script.  The operator is going to select the node he wants the wants
to run the application on from the map.  You specify in the registration
file what attributes the node must have to be selected.   You then
have access to the selection name via $OVselection1.  With this you
launch a script that  queries the NetView databases using ovobjprint,
 or ovtopodump, or whatever else is needed, for the attributes you
want  and the script passes those to your pre-written application.
 

The alternative is to rewrite the application
to do the work the script does before it does the real operation you want.

I'd look at  other examples of
things we ship in /usr/OV/registration to see how it's done.  There
is a general discussion in the NetView Programmer's Guide, but its hard
to follow unless you look at a lot of examples.

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group

James Shanks
Level 3 Support  for Tivoli NetView for UNIX and Windows
Tivoli Software / IBM Software Group