buclin%elma%CLSEPF51.@CUNYVM.CUNY.EDU.BITNET (Buclin Bertrand, Service Informatique, SI-EPFL) (06/24/88)
>Anyway, I've got the same kinda problem myself. If you don't use >the switch /notraceback when LINKing, cli$dcl_parse writes a symbolic >trace dump when it fails to parse the command line given to it. I don't >like that. More complaint: cli$dispatch adds an exception handler that >overrides mine. I can't see why that's necessary. The cli routine cli$dcl_parse returns only the non fatal errors and informational status codes in R0. Of course you can use an exception handler that will trap them (see Guide to Programming on VAX/VMS, chapter 10). I've wrote a lot of Ada applications using the cli routines and I always could handle the exception raised by cli$dcl_parse. Now, cli$dispatch is used to invoke the proper routine once the parsing of the command has been done. It has an exception handler to recover from misformed cli tables. Of course, this handler is not removed from the stack until the invoked routine is terminated. Thus, if you don't establish your own handler IN the routine and exception occurs, the Cli$dispatch handler will catch it. In this way it overrides any handler you may have declared at the top level of your program. Bertrand Buclin BITnet : BUCLIN@CLSEPF51.Bitnet Computing Services EAN,Internet : Buclin@Elma.Epfl.CH Computer Science Department SPAN/HEPnet : ELMA::BUCLIN (20.34) Swiss Federal Institute of Technology PSI : PSI%022846911008::ELMA::BUCLIN CH-1015 Lausanne X400 : S=buclin;OU=si;ORG=di; PRMD=Epfl;ADMD=arcom;C=CH