You have a couple of options, all of which are "less secure" than what
VESOFT recommends [but only slightly]

-- chain VESOFT's option logon UDC to yours.  Perhaps the best, BUT you may
have to redo any changes to VESOFT's UDC when you update/upgrade their
software.  Be careful here -- doing this incorrectly may cause the UDC to
not execute at all, and then users won't be properly validated.
-- chain your UDC to VESOFT's.  Same thing [almost], but if any error in
your UDC causes the execution of the UDC to stop, then users may NOT be
properly validated
-- utilize the PROCEDURE EXIT feature of VESOFT's security package.
Technically, with this enabled you DON'T need the logon UDC, but it is there
as a BACKUP to cases when procedure exits are DISABLED or if they  otherwise
fail for any reason.

Tom Emerson
Sr. Systems Analyst
NDC | e COMMERCE
[log in to unmask]
626-258-4309
626-350-3832 FAX



> -----Original Message-----
> From: Chuck Ryan [mailto:[log in to unmask]]
> Sent: Monday, November 15, 1999 10:20 AM
> To: [log in to unmask]
> Subject: Re: Logon UDC's
>
>
> 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
> >
>