Path: utzoo!attcan!uunet!husc6!cca!mirror!rayssd!raybed2!linus!mbunix!mhg From: mhg@mitre-bedford.ARPA (Mark H. Granoff) Newsgroups: comp.os.vms Subject: CLI$DCL_PARSE Error Output Suppression Keywords: CLI, Command Language Interface, SET MESSAGE Message-ID: <33992@linus.UUCP> Date: 9 Jun 88 15:40:15 GMT Sender: news@linus.UUCP Reply-To: mhg@mitre-bedford.ARPA Followup-To: mhg@mitre-bedford.ARPA Organization: The MITRE Corporation, Bedford, Mass. Lines: 34 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 up the display. 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 or anything slow like that. I know I could use a command procedure, but some code to do the same thing would be much niftier :-). Thanks for any help. I apologize if I'm missing the boat on something obvious. ** Please respond directly to me since I do not subscribe to comp.os.vms. +--------------------------------------------------------------------+ | 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. | +--------------------------------------------------------------------+