Hey All, (Jeremy?)
The path that fan out (Unix/Linux) business logic and commands take to
the target host is a long and winding road - driver to object services,
event journaling, and handed to the script. All these transactions have
a result code (RC=#) returned as a result, and visible in the trace. Is
there any practical way to trap the returned RC= value in the driver as
for use as a local variable?
It would be really cool if this is possible. Looking to do fall back
logic to cut a remedy ticket if the operation fails.

desertpilotjc's Profile: https://forums.netiq.com/member.php?userid=9777
View this thread: https://forums.netiq.com/showthread.php?t=56923