Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!rutgers!ucla-cs!zen!ucbvax!DBSTU1.BITNET!I7100501
From: I7100501@DBSTU1.BITNET (Eckart Meyer)
Newsgroups: comp.os.vms
Subject: RE: VAXC SYS$OUTPUT
Message-ID: <8709141404.AA23651@ucbvax.Berkeley.EDU>
Date: Mon, 14-Sep-87 10:05:02 EDT
Article-I.D.: ucbvax.8709141404.AA23651
Posted: Mon Sep 14 10:05:02 1987
Date-Received: Tue, 15-Sep-87 04:54:08 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 17

>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? Is main() doing this? I can close the files with fclose(stdout) and
>fclose(stderr) but that still leaves me with useless files in my directory.

The answer: Use the qualifier /OUTPUT=NL: and /ERROR=NL: with the
RUN command.

-----------------------------------------------------------------------------
Eckart Meyer                            BITNET: I7100501@DBSTU1
Inst. f. Nachrichtentechnik             PHONE:  0531 / 391-2454
Technical University of Braunschweig    ADDR:   Schleinitzstr. 23
Germany                                            3300 Braunschweig
-----------------------------------------------------------------------------