Eric Chamba already suggested using a UDC, which can accomplish either
tracking or aliasing. In either case, you would want have to decide
whether this will be part of a system, account, or user UDC catalog.
Then you would have a label of listuser parm1,parm2,parm3,parm4,parm5,
to allow it to respond to any valid listuser syntax, followed by
whatever you want it to do, such as log the user and either execute the
listuser command (xeq listuser...) or not. If you want it to simply do
nothing, use no command, and terminate with *. This will just give them
back a prompt without doing so much as issuing an error message. Or
perhaps you want to issue a warning that the activity is being logged
(whether it is in fact or not); I understand that this is extremely
effective in encouraging compliance.

An alias would be a UDC label that is memorable but not likely to be
stumbled upon. For instance, ls could be discovered by a distracted UNIX
user; userlist could be found be a NetWare user. However, aliasing
commands can have unpleasant consequences, and is not recommended. The
former course of allowing normal function and echoing identifying
variables into a flat file would be preferable.

>----------
>From:  Robert Wu[SMTP:[log in to unmask]]
>Sent:  Wednesday, March 12, 1997 1:31 PM
>To:    [log in to unmask]
>Subject:       [HP3000-L] listuser command
>
>I'd like to track/log use of the "listuser" command.
>
>Or, I'd like to change this command's name.  Is it a program
>that I can merely rename, or is it imbedded within MPE?
>
>Ideas?
>
>Rob Wu
>