[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

1815.0. "SYS$ERROR.;1" by SMAUG::MENDEL (What've we done to our fair sister?) Wed Nov 29 1989 15:20

    I've been starting some DECWindows applications on my VMS 5.1 
    VAXstation 2000, like CLOCK, RAGS, BANNER, etc., as detached
    processes. Like this:

	RUN /OUT=NL: /PROC="Clock" SYS$SYSTEM:DECW$CLOCK
	
    They work fine. Except I get these bogus files created.

	DIR SYS$LOGIN:SYS$* /COL=1

	SYS$ERROR.;3
	SYS$ERORR.;2
	SYS$ERROR.;1

    They are all open to the detached processes, and I cannot delete 
    them except by zapping the process first.

    So, now-a-days I do this:

    	RUN /OUT=NL: /ERR=NL: /PROC="Clock" SYS$SYSTEM:DECW$CLOCK
	
    But I never remember having to bother redirecting SYS$ERROR to avoid
    getting those files created when creating a detached process.
    
    Is this particular to DECWindows? And is this "planned"? Or am I just doing
    something strange? ( careful ... ;^} )

    Kevin

T.RTitleUserPersonal
Name
DateLines
1815.1/ERRORCOOKIE::KITTELLRichard - Architected Info MgmtWed Nov 29 1989 23:551
	Just add /ERROR=NL: to the RUN.
1815.2SMAUG::MENDELWhat've we done to our fair sister?Thu Nov 30 1989 12:403
    As I said in .0, that's what I'm now doing.

    I was wondering why it was happening.
1815.3A guessIOSG::MARCHANTAnd there's more...Thu Nov 30 1989 20:3411
    Since you didn't specify /ERROR, the detached process doesn't have a
    SYS$ERROR logical. This implies that a program opening/writing to
    SYS$ERROR will create a file like "SYS$ERROR.;1"

    Most DECwindows programs are written in `C', and C of course has `stdin',
    `stdout' and `stderr'. So, either these are being pre-opened, or the
    program is writing to stderr (assuming the program is written in C).

    Q: Are these files empty? (you might have to do a $SET FILE/END on them)

    Paul.
1815.4SMAUG::MENDELWhat've we done to our fair sister?Fri Dec 01 1989 12:298
    They files are empty when I check them.

    I have not had lots of practice with C, which would explain why this hasn't
    happened to me before. Your explanation sounds good.

    Thanks.

    kevin