Guy Smith said: > [1] Does anyone like the notion of filtering console > messages? I'd like the ability to limit what gets displayed > on the console, and alternately highlight some messages. No need for it here. For the last 12+ years we have printed every line of the console, and archive it for a week or so. Settles _many_ arguments about what happened when. We have jobs that automatically go through from time to time, look at stuff we're interested in, and "tellop" the results to the console--just to make sure it's available. OTOH I think the concept Guy did for the CSL has merit in many places. Maybe HP would allow a parameter somewhere which would fork a copy of console messages into a circular file so that the implementation could be cleaner, and maybe send the primary stream somewhere other than ldev 20. Then you could have a job that did your filtering and sent the output to the physical console. Whatever, I don't think it would be a good idea to have HP doing the actual filtering. I guarantee they can't satisfy everybody, and I'd rather see their efforts going into something that is possible. I have several stories to tell about our implementation, but maybe we can save the young whippersnappers this time. We fossils have been subjecting them to too much lately. -- /\--. John Beckett "Do you remember the chip / \ ) Southern College of SDA HP wanted $5,000 for? It /----\---. (615) 238-2701 voice was a 709C. That's how \ / \ \ 238-2431 FAX you make a computer `-' `--' [log in to unmask] obsolete!"