home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!nntp-server.caltech.edu!SOL1.GPS.CALTECH.EDU!CARL
- From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick)
- Newsgroups: comp.os.vms
- Subject: Re: Closing file after deassigning SYS$OUTPUT
- Date: 22 Jan 1993 12:10:59 GMT
- Organization: HST Wide Field/Planetary Camera
- Lines: 28
- Distribution: world
- Message-ID: <1joo8jINNt5t@gap.caltech.edu>
- References: <llrl3bINNm56@news.bbn.com>
- Reply-To: carl@SOL1.GPS.CALTECH.EDU
- NNTP-Posting-Host: sol1.gps.caltech.edu
-
- eIn article <llrl3bINNm56@news.bbn.com>, brosen@bbn.com (Bruce L. Rosen) writes:
- >Our application reassigns SYS$OUTPUT to a file, does a piece of work, and
- >the deassigns SYS$OUTPUT. According to BOOKREADER documentation, deassigning
- >SYS$OUTPUT causes the file to be closed. The file does get closed eventually,
- >but this appears to be happen asynchronously ... VMS apparently closes the
- >file when it gets around to it.
- >
- >Unfortunately, most of the time for our application, this is not soon enough
- >and the application fails on trying to re-open the file (using CRTL fopen());
- >
- >Is there a way to force VMS to close the file synchronously when the
- >deassignment of SYS$OUTPUT occurs? Is there some other way to jog VMS
- >into closing the file?
-
- I've just tried, without success, to reproduce your problem on my system (of
- course, I'm logged in from home over a terminal line). Since I can't, at the
- moment, reproduce your problem, I can only guess about it. My guess is that
- you might need to execute some other command (any other command; even a command
- that invokes a CLIROUTINE seems to work for me, and at the moment, I can't test
- anything less than that) in order to force closure of the file.
- --------------------------------------------------------------------------------
- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL
-
- Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My
- understanding of astronomy is purely at the amateur level (or below). So
- unless what I'm saying is directly related to VAX/VMS, don't hold me or my
- organization responsible for it. If it IS related to VAX/VMS, you can try to
- hold me responsible for it, but my organization had nothing to do with it.
-