Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!rutgers!mit-eddie!apollo!mishkin From: mishkin@apollo.UUCP Newsgroups: comp.sys.apollo Subject: Re: Concurrency at open - (nf) Message-ID: <383c35e9.c366@apollo.uucp> Date: Mon, 2-Nov-87 08:24:00 EST Article-I.D.: apollo.383c35e9.c366 Posted: Mon Nov 2 08:24:00 1987 Date-Received: Wed, 4-Nov-87 20:00:16 EST References: <41600002@uklirb.UUCP> <382e6a52.c366@apollo.uucp> Reply-To: mishkin@apollo.UUCP (Nathaniel Mishkin) Organization: Apollo Computer, Chelmsford, MA Lines: 31 Summary: You *can* get there from here From an engineer at Apollo who wishes to remain nameless, on the topic of viewing files that are open for write: ---------------------------------------- There are many reasons beyond concurrency that prevent your approach from working. However, you may find the following to be an acceptable substitute: instead of creating your output file normally, create it using pad_$create, asking for a transcript of relative size zero, and passing the same pathname you would normally use. Then write to this stream normally. The zero size request tells the DM to not make a window at all, but to keep track of the output. Then the CV command can later be used to make a window to view the output. When you close the stream, and all the windows are gone, the end result is a normal ascii file. The drawbacks to this approach are as follows: 1) you must have a DM transcript pad somewhere to begin with, to pass to pad_$create as the related pad -- if you are running in a normal shell you can just use standard out -- if you are running via CPO or equivalent, this can be a problem -- you can call pad_$create_window, but then that really creates a window. 2) you can only append to the file -- you cannot seek and write at other places. ---------------------------------------- -- -- Nat Mishkin Apollo Computer Inc. Chelmsford, MA {decvax,mit-eddie,umix}!apollo!mishkin