On Friday, 12/02/2005 at 11:11 PST, "Schuh, Richard" <[EMAIL PROTECTED]> wrote: > This seems to fit in the same category as the BYUSER. If we can QUERY BYUSER > userid, then it would seem like we also ought to be able to have a query for > this or have QUERY BYUSER extended to respond ?AUTOBY userid? when applicable. > Maybe we could put it on the wish list for the next time someone is messing > with the QUERY command. It doesn?t seem major enough to call for a requirement.
A requirement might not seem like a big deal for a relatively small effort, but it is. Which is more important: Widget A which has outstanding requirements or Widget B which does not? In fact, requirements are often even MORE important for items which are directed at the productivity of the sysprog. It is very difficult to assign 'business value' to something which only affects the lives of the 23 people in the world. It's difficult because we are keenly aware that seemingly minor "pain points" can affect the Big Picture. Let's take this QUERY AUTOLOGGED thing is an example. It's not the audit trail. *That's* over in your ESM audit logs or the operator console log. OK. So you use it to send messages back to the person to autologged the server. Fair enough. But, might you want that message to go to more than one person? And did you have to do custom programming in the server to do it? What about stock servers? Is the request REALLY for an integreated capability to redirect a server's messages to other users? Or is it just a convenience you don't *need*, but "might some day"? Oh, the audit log would do, but it's hard to get to you say? Hmmm.... better system event management? We are interested in knowing where you perceive sharp corners, but we are especially interested in why you bumped into them in the first place and how the corner affects your ability to deploy solutions. Alan Altmark z/VM Development IBM Endicott
