I wonder where it is after the command mib returns the error. In my
application, if the command [mib successor name] is given an invalid
mib name "testing", I see the error message, Error : no object "testing",
but the error causes the immediate exit of procedure in which the command
is executed. I believe it happens even to the procedure that contain the
aforementioned procedure call. Actually I don't know where the script is
after mib prints out the error message. I tried "catch" and it did not work.
I really need to control the error handling. So I wonder if there is
any way I can know where the script is after mib prints out the error
message. Can I avoid the exit of the procedure if mib is given an invalid
argument?
Any help is greatly appreciated.
Regards,
--James Song
jsong@nlc.com