Path: utzoo!utgpu!water!watmath!clyde!rutgers!ucla-cs!zen!ucbvax!RITA.ACS.WASHINGTON.EDU!WIZARD From: WIZARD@RITA.ACS.WASHINGTON.EDU (The Bandit "." "." "." "", on" "RITA) Newsgroups: comp.os.vms Subject: RE: Session Logs Message-ID: Date: 6 Jan 88 23:08:00 GMT Sender: usenet@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 40 Danny Padwa writes: > Does anybody know of any ways, short of something along the lines of > SET HOST/LOG 0 > to get a copy of a terminal session (except, of course, a terminal printer). > > We are having trouble here in that many users (students, at teacher's request ) > use the SET HOST/LOG command to save a session, and then, when things don't > work try it again, without closing the first session. This creates tremendous > overhead, both for them ("Why is the machine so slow?") and the staff ("Why > is the machine so slow?") :-). > > I suspect that a solution could be found by playing with the SYS$OUTPUT > logical, but a lot of playing with that hasn't hit a viable solution (we need > to keep terminal output too!!!). Here at the University of Washington, we have a program called RECORD. RECORD, which was written by Mark W. Renton before SET HOST /LOG was invented, has its limitations, but it has served us well for a number of years. As for users forgetting that they are SET HOSTed, this doesn't happen with RECORD. A user running RECORD >knows< (s)he is running RECORD, and is not likely to forget it. I have also heard of another package, called PHOTO or something similar, which also does what is wanted. As for playing with logical names, we were never able to get this to work. If you would like more information, send me a short note. Derek Haining Academic Computing Services University of Washington Seattle, Washington (206) 543-5852 DEREK@UWARITA.BITNET -or- DEREK@RITA.ACS.WASHINGTON.EDU