ALBCRAJ@YaleVM.YCC.Yale.Edu (Craig Albert) (02/01/91)
I need a utility which will write a complete log of a session on my pc to a fi le, including my session on my remote mainframe. Any suggestions?
ts@uwasa.fi (Timo Salmi) (02/05/91)
In article <91032.031739ALBCRAJ@YaleVM.YCC.Yale.Edu> ALBCRAJ@YaleVM.YCC.Yale.Edu (Craig Albert) writes: >I need a utility which will write a complete log of a session on my pc to a fi >le, including my session on my remote mainframe. Any suggestions? Sure. For capturing the text on the PC screen first read /pc/ts/tsfaq17.arc available by anonymous ftp eg from garbo.uwasa.fi. But what is the problem anyway. For logging into a mainframe, you need a terminal emulation, or a telecommunication program, and all such modern programs have a logging option. ................................................................... Prof. Timo Salmi Moderating at garbo.uwasa.fi anonymous ftp archives 128.214.12.37 School of Business Studies, University of Vaasa, SF-65101, Finland Internet: ts@chyde.uwasa.fi Funet: gado::salmi Bitnet: salmi@finfun
valley@uchicago (Doug Dougherty) (02/05/91)
ts@uwasa.fi (Timo Salmi) writes: >In article <91032.031739ALBCRAJ@YaleVM.YCC.Yale.Edu> ALBCRAJ@YaleVM.YCC.Yale.Edu (Craig Albert) writes: >>I need a utility which will write a complete log of a session on my pc to a fi >>le, including my session on my remote mainframe. Any suggestions? > Sure. For capturing the text on the PC screen first read >/pc/ts/tsfaq17.arc available by anonymous ftp eg from >garbo.uwasa.fi. > But what is the problem anyway. For logging into a mainframe, >you need a terminal emulation, or a telecommunication program, and >all such modern programs have a logging option. You can never be sure. Of course simple logging of CON: to a file is trivial and obviously an FAQ (even though I myself posted such a question a short while ago, because I was too lazy to look around [heh] Actually, I just didn't think of looking in the "SCREEN" directory of the various FTP sites... But I digress) But of course the problem is programs that break the rules (I.e., most of them) And, sad to say, not every "connect" type program can do logging. In fact, at this point, I am sorely in need of a program (TSR) that can take the output of a program that does all its output to screen via INT 10, fn 9, and translate that into standard hardcopy. Talk about trying to put toothpaste back into the tube...