From:	CSBVAX::MRGATE!info-vax-RELAY@KL.SRI.COM@SMTP 23-JUN-1988 06:58
To:	ARISIA::EVERHART
Subj:	re: CLI$DCL_PARSE error signalling


Received: from CORNELLC.CCS.CORNELL.EDU by KL.SRI.COM with TCP; Thu, 16 Jun 88 12:04:51 PDT
Received: from UNCAEDU.BITnet by CORNELLC.CCS.CORNELL.EDU ; Thu, 16 Jun 88 14:43:23 EDT
Received: from Ins.MRC.AdhocNet.CA by UcEdu.UNCA.AdhocNet.CA with DECNET ;
          Thu, 16 Jun 88 08:10:00 MDT
Date:    Thu, 16 Jun 88 08:08:48 MDT
From:     ewilts%Ins.MRC.AdhocNet.CA%UNCAEDU.BITNET@CORNELLC.CCS.CORNELL.EDU (Ed Wilts)
Message-Id: <880616080848.018@Ins.MRC.AdhocNet.CA>
Subject: re: CLI$DCL_PARSE error signalling
To:       info-vax@kl.sri.com
X-ST-Vmsmail-To: INFOVAX

To solve your problem, you need to do the following:

CALL LIB$ESTABLISH (LIB$SIG_TO_RET)     ! Establish condition handler
STATUS = CLI$DCL_PARSE (.......)        ! Do your parsing
CALL LIB$REVERT                         ! Revert to normal

What this does is establish a condition handler that will trap all attempts
to signal errors and return the status code to the calling routine.  You can
then safely have CLI$DCL_PARSE generate whatever errors it wants and you can
handle them appropriately.  Don't forget to revert the condition handler so
that other failures dump normally.

Works for me....

        .../Ed