Re: [nv-l] NVATTR_#

[Oliver Bruchhaeuser <oliver.bruchhaeuser@de.ibm.com>]

or .... we have had this recenty here .... use something like:
set | grep ^NV
in the script to dump all NetView environment variables.

Oliver

James Shanks <jshanks@us.ibm.com> Sent by: owner-nv-l@lists.us.ibm.com 11.03.2004 13:50 Please respond to nv-l

To:        nv-l@lists.us.ibm.com         cc:                 Subject:        Re: [nv-l] NVATTR_#

Paul is correct and Scott Barr's suggestion was a good one, too -- 
You need not pass the NVATTR available.   They are already passed an exported in the shell that runs your command.  All you have to do is reference them. But there is no way to say "list them all" with $NVATTR_* as you are trying to do.  That is not in the documentation.   
You can however reference $NVATTR_COUNT and then list variables up to that number in a loop. 

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

Paul <pstroud@bellsouth.net>
Sent by: owner-nv-l@lists.us.ibm.com

03/10/2004 05:05 PM

Please respond to
nv-l

To	nv-l@lists.us.ibm.com
cc
Subject	Re: [nv-l] NVATTR_#

When you run a script from a ruleset node all the
NetView and trap variables are passed to the environment
of that script.

Paul




CMazon@commercebankfl.com wrote:
> 
> Ok guys, I found several instances in the archives but I have yet to see 
> an answer for this one, (unless I missed it).  I am generating an email 
> through an action node on a ruleset.  However I want the email to 
> contain all the variables that the event has forwarded to the the action 
> node without having to include in the script $NVATTR_1-50.  Is there a 
> wildcard for the $NVATTR?  I know one exists for traps ($*) but 
> $NVATTR_* does not seem to work, or im doing something wrong?
> 
> 
> Thanks
> 
> Carlos