Dawn M. Wolthuis wrote:
I think someone posted the name of the voc entry required if you want
to do something at the time of an ODBC login, such as initializing
named common memory. Otherwise, I suspect it is in the doc somewhere
(sorry I don't have more details). Check the voc on your
You'll need to search the archives for this (I don't have any of the
stuff you mention :-) but there was discussion about calling virtual
fields from ODBC a little while ago.
I think at least one of the points was does it rely on environment
variables or stuff set up by LOGIN? It appears that
I think someone posted the name of the voc entry required if you want to do
something at the time of an ODBC login, such as initializing named common
memory. Otherwise, I suspect it is in the doc somewhere (sorry I don't have
more details). Check the voc on your previous system for an entry like
Ken,
At the risk of stating the obvious, have you checked that the
correct version of the SUBR is cataloged?
Sorry to have to throw this out without fully researching it first, but
I've got a client with a pressing problem.
They are in the final stages of preparing to switch over from their
Wol wrote:
I think at least one of the points was does it rely on environment
variables or stuff set up by LOGIN? It appears that ODBC has a
different login setup to a normal user - maybe even that UD needs a
correct $PATH to find the executable for SUBR? I dunno. Or do the
SUBRoutines rely
