To continue Erik's thought.  If you are overriding HP commands, make sure
that programs that call those commands are using HPCICOMMAND as an intrinsic
call.  Other wise (if you used the COMMAND intrinsic) you would perform the
actual command that you were avoiding.

Thanks!!

Ron Horner
Operations Manager
Administrative Management Group
[log in to unmask]
(847) 870-2175


        -----Original Message-----
        From:   Erik Vistica [SMTP:[log in to unmask]]
        Sent:   Monday, November 15, 1999 3:38 PM
        To:     [log in to unmask]
        Subject:        Re: Logon UDC's

        It's been a very long time since I used any VESOFT products but a
thought on
        UDCs in general. I only use UDCs for things that I cannot do in a
command file.
        These are OPTION LOGON and overriding an MPE command (the CI
searches for UDC
        then MPE command then command file/program file).

        If I need OPTION LOGON, I create a 4 line UDC that calls a command
file and put
        the guts there.

        LOGONSYSTEM
        OPTION LOGON
        XEQ SYSTEM.UDC.SYS
        *

        Chuck Ryan wrote:

        > Is there a limitation on Logon UDC's?
        >
        > On our system we have 2 system level udc files, one for VESOFT's
products
        > and one of our own. I tried to add a logon udc to our udc file,
but it does
        > not get executed at logon while the VESOFT logon udc does.
        >
        > What am I doing wrong?