I thought this was the case, but could not find any documentation that
actually said this limitation existed.

I think this could easily cause a problem with third party software like
VESOFT.


> -----Original Message-----
> From: [log in to unmask] [mailto:[log in to unmask]]
> Sent: Monday, November 15, 1999 12:07 PM
> To: [log in to unmask]
> Cc: [log in to unmask]
> Subject: Re: [HP3000-L] Logon UDC's
>
>
> Re:
> > Is there a limitation on Logon UDC's?
>
> yes.
>
> > 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?
>
> At each level (system, account, and user), only the "first"
> seen logon UDC will
> be invoked at logon time.
>
> Indeed, you could well argue that SETCATALOG ought to warn
> you if there
> is one (or more) UDCs marked as "option logon" that won't get executed
> due to this restriction.  Alternatively, perhaps we should
> request a functionality
> change, to allow multiple logon UDCs at each level.
>
>
>
> Stan Sieler
> [log in to unmask]
> www.allegro.com/sieler/wanted/index.html
> www.allegro.com/sieler
>