Where I am on the learning curve: true/false

The parent needs to be "Down" to trigger suppression events, it looks like yours is going "Critical" when it is at 1.  I'm assuming you are using a custom script monitor, in which case you should just exit with a 1 to force the monitor down, which would then cause the dependency to kick in.

The Basics of PowerShell (part 3)

So I have the output correct (ones and zeroes) but the exit codes are not right.

Outer shell:
[
E:\bin\GVSW.ps1 $global
]
Inner shell:
[
cd e:\bin
E:\"Program Files (x86)"\CA\"Workload Automation AE"\JRE_WA\bin\java GVSW $global
]

I need to pass the inner exit code to the outer shell, and then out to the monitor call.  Right wavelength?

I'm not familiar with this inner and outer shell trickery you are describing, but that sounds about right.  something like an If $value = 1 then exit 1 else blah blah

Inner/outer is like one subroutine that calls another.  I needed to pass the innermost return code back to the outermost calling routine.  As mentioned in the Java app thread, the inner code was easier (for me) to get working since paths with spaces can ended up being parsed wrong.

The exit routine I found that worked is (no if/then needed since that is done in Java):

Exit $LASTEXITCODE

Too many years with UNIX shells, where the exit code of the last statement in the shell is passed as the shell exit code. 

Almost there...

The exit code now sets the status as Down (red light/green light).

There is a warning saying "The return code is different than expected. Testing on node '127.0.0.1' failed with 'Down' status ('Down' might be different if script exits with a different exit code)."

Can I ignore that, or no?

To my eyes it seems to be working, assuming you still get an exit 0 with a statistic when the stat is good then I would feel reasonable comfortable ignoring that.  It would mean that your 0-1 chart won't show up anymore the way it did, but thats just a design limitation that when solarwinds gets an exit code 1 it won't even collect any statistics, just downs the object and you are done with it.

With that app being down it should trigger the dependency relationships for the children now where they get marked as unreachable and solarwinds stops polling them.  Is that happening for you?

> ... Is that happening for you?

It looks like the disk volumes I was testing with are in an Unknown state, for reasons other than my up/down check.  I'll find other test cases.

Thanks again!