Hi Peter & Craig,
>Craig Berry wrote:
>
>!That's basically the whole Perl API, or all of it that DBD::MySQL
>!appears to make use of. Is the logical name PERLSHR defined? Are
>!you quite sure you've resolved all problems upstream from the link
>!failure? Since the link is one of the last things that happens,
>!something going wrong in a previous step could well be the root issue.
I think I found the problem last night lying awake in bed (don't you
hate it when that happens!). I haven't had a chance to check it yet but
my strong suspicion is that the DBD::mysql code was compiled with the
qualifier /NAMES=AS_IS (because MySQL is compiled that way) and thus
the object modules are expecting to find mixed-case names in PERLSHR.
This arouse directly from the same issue Peter found, i.e. a lack of
MYSQL_CONFIG on OpenVMS. I worked around this by hacking the DESCRIP.MMS
file and I think I got it slightly wrong (e.g. using /NAMES=AS_IS).
Peter, thanks for the tip about MMS INSTALL and MYSQL_CONFIG as a command
procedure. I'll try again tomorrow (I need to restore from Backup first
and that's off-site) and keep you all posted.
Thanks,
Jeremy Begg
