Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!husc6!uwvax!vanvleck!uwmcsd1!ig!agate!ucbvax!MITRE-BEDFORD.ARPA!mhg
From: mhg@MITRE-BEDFORD.ARPA (Mark H. Granoff)
Newsgroups: comp.os.vms
Subject: CLI$DCL_PARSE Error Output Suppression
Message-ID: <8806141226.AA03010@mitre-bedford.ARPA>
Date: 14 Jun 88 12:25:58 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The MITRE Corporation, Bedford, Mass.
Lines: 33

[This has already been cross posted to the comp.os.vms newsgroup]

Here's what may amount to be a trivial question, but I don't see the
simple answer...

I am writing an application in which I would like to do DCL parsing,
using CLI$xxx routines, CLI tables, etc.  I know how to do this.  The
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.

I wrote a little test program (complete with test CLD) and discovered
that a SET MESSAGE/NOID/NOFAC/NOTEXT/NOSEV before invoking the image
successfully suppresses the error output (yeah!).  So, how do I
operate on the SET MESSAGE bits (to save them and change them) from
within a program.  I do not want to use LIB$SPAWN.

Thanks for any help.  I apologize if I'm missing the boat on something
obvious.  Please respond directly to me (to avoid flooding the network
with responses).

+--------------------------------------------------------------------+
| Mark H. Granoff                      Member of the Technical Staff |
+--------------------------------------------------------------------+
| USMAIL: The MITRE Corporation  | ARPAnet: mhg @ mitre-bedford.ARPA |
|         Burlington Rd.         | UUCP   : linus!mbunix!mhg         |
|         M/S B015               |-----------------------------------|
|         Bedford, MA 01730      | A T & T: (617) 271 - 7506         |
+--------------------------- Disclaimer -----------------------------+ 
|   The views expressed herein are my own and do not necessarily     |
|                    reflect those of my employer.                   |
+--------------------------------------------------------------------+