Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!mcvax!enea!erix!bengtb
From: bengtb@erix.UUCP (Bengt Baeverman)
Newsgroups: comp.os.vms
Subject: Re: VMS C SYS$OUTPUT
Message-ID: <1493@erix.UUCP>
Date: Mon, 14-Sep-87 15:04:59 EDT
Article-I.D.: erix.1493
Posted: Mon Sep 14 15:04:59 1987
Date-Received: Wed, 16-Sep-87 06:14:40 EDT
References: <8709120102.AA10824@ucbvax.Berkeley.EDU>
Reply-To: bengtb@erix.se (Bengt Baverman)
Organization: Ericsson Telecom, Stockholm, Sweden
Lines: 22

In article <8709120102.AA10824@ucbvax.Berkeley.EDU> UDCSTAFF@UDCVAX.BITNET writes:
>I have been using VAX C version 2.3 to write a program designed to be run
>as a detached process.  It runs fine, but VAX C insists on opening
>SYS$OUTPUT and SYS$ERROR even though the program does not do any output.
>There are no Output functions used in the program and when I run it /detached
>it creates files called SYS$OUTPUT. and SYS$ERROR.  Is there a way around
>this? 

If you are not interested in the output written to SYS$OUTPUT or SYS$ERROR
in a detached process it's easy; just start the process with the

	/OUTPUT=NLA0: /ERROR=NLA0:

qualifiers. They will make the output goto to the null device.

But normally you would want the output written to SYS$ERROR. Thus a better
way to handle this would be to delete the generated file SYS$ERROR only if
it larger than zero block. This file will contain the error messages written
when (not if, but when) an error occurs in your program.

			Bengt Baverman
			bengtb@erix.se