Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!pasteur!ucbvax!decwrl!nsc!voder!cullsj!jayz
From: jayz@cullsj.UUCP (Jay Zorzy)
Newsgroups: comp.os.vms
Subject: Re: CLI$DCL_PARSE Error Output Suppression
Message-ID: <337@cullsj.UUCP>
Date: 27 Jun 88 21:32:46 GMT
References: <8806141226.AA03010@mitre-bedford.ARPA>
Organization: Cullinet Software, San Jose, CA
Lines: 38

From article <8806141226.AA03010@mitre-bedford.ARPA>, by mhg@MITRE-BEDFORD.ARPA (Mark H. Granoff):
> ...problem is in the way CLI$DCL_PARSE works.  If the command string it
> is parsing is erroneous, it spits out an error message (not unlike DCL
> error messages).  My application uses FMS; error messages printed to
> the screen (without using FMS calls) would mess everything up.

Have you tried establishing a condition handler around your calls
to the CLI$... routines?  If not, you might try this.  For example:

(in C:)

{
	LIB$ESTABLISH (cond_handler);
	stat = CLI$DCL_PARSE (...);
	LIB$REVERT ();
	If (stat !== CLI$_NORMAL)...
	.
	.
	.
}

int
cond_handler ()
{
	return (SS$_CONTINUE);		/* To prevent resignalling */
}

In this example, 'cond_handler' will trap any errors generated by the
CLI$DCL_PARSE routine and basically ignore them.  But you're checking the
return status after the call, so you should be covered.

For more information on condition handlers, see the System Services and 
the Run-Time Library manuals.

Hope this helps.

Jay Zorzy
Cullinet Software
San Jose, CA