Get all system messages

Question

Hello Everybody,
Well, I need to do an application to get all system messages and filter the messages I will need. The application run lotusscript codes from a Notes database, the application just do a database instance, choose the lotus agent and run it. What I need is get all those messages that will come from the lotus agent. I done a piece of the code to redirect all System messages for a file:
printStream = new PrintStream( new BufferedOutputStream( new FileOutputStream("OutFile.txt") ), true );           
System.setOut( printStream );
System.setErr( printStream );The messages from lotus agent continue goes to console.By the way, this code can not get the messages from lotus agent, I guess with JMS I can intercept these message. My doubt is: Can I do it with JMS? If so, Could you advise me, please?

Answer 1

Don't bash csh!LOL!I'm glad some people like puns. Some of my friends do, some can't stand them!
I don't know ksh. Our target system uses it--makes me type a lot, because I don't know how to use ksh
history as well as I can use csh history. That's just setup though--must of it runs as a GUI.I don't like ksh either. Never had much luck with its history.
I use bash and zsh. Both have csh-like history, plus arrow key command recall.I don't think I've used either. I don't even think we have them on our system [from a quick check] (not sure I'ved heard of zsh before). I used to use tcsh (which had arrow key command recall) in college, but then some of my jobs didn't have it, so I learned csh history, and can do quite a lot. Confuses some people, but is really quite easy once you get the hang of it. The system administrator at my first job did all sorts of things with sed/awk/nawk/etc.--drove everyone nuts, because no one knew what he was doing. I can do basic sed, and can use awk/nawk if I read the man page.
Considering all the C programming I've done, you'd think I'd like the csh family more, but for some
reason I ended up gravitating toward bash and the more I used it, the more I didn't want to switch to csh.Yeah--I stuck with what I learned first, since it does the job. I don't do shell script programming much, so I don't need to know too many gory details of that. I can do the "foreach" on the command line. I learned vi well in college, so I later never felt like learning emacs (even a console version). So, I do everything in vi now. I push a few extra escape and append characters sometimes if I have to write an MS Word document, but I like vi for my code editing. I tried typing Dvorak for a while when my job was writing requirements in MS Word. It worked well on my split keyboard, but couldn't adjust to a flat keyboard I got stuck with for a while. And vi and Dvorak just don't mix...so I'm back to QWERTY.