Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

MySql for OpenVMS

60 views
Skip to first unread message

tadamsmar

unread,
Dec 18, 2009, 11:58:13 AM12/18/09
to
I want to interface to an instrument that uses MySql for TCPIP
communications.

I am downloading MySql for OpenVMS.

I wonder if I will find a programming interface in the download, or
merely a user interface.

I need a programming interface so I can get data from the instrument
into an existing Fortran program.

(the instrument also has a serial interface, but we would prefer to
use ethernet.)

Arne Vajhøj

unread,
Dec 18, 2009, 10:34:40 PM12/18/09
to

SYS$COMMON:[MYSQL051.INCLUDE]
SYS$COMMON:[MYSQL051.VMS.LIB]MYSQLCLIENT_MIXED.OLB
SYS$COMMON:[MYSQL051.VMS.LIB]MYSQLCLIENT_UPPER.OLB

should include a MySQL client lib (MySQL C API).

Arne


tadamsmar

unread,
Dec 28, 2009, 12:39:52 PM12/28/09
to

Thanks.

Do I need to run the server on VMS to use the client to access this
other system, the instrument that I want to read?

Where is the documentation on the client interface?

Arne Vajhøj

unread,
Dec 28, 2009, 10:16:53 PM12/28/09
to
On 28-12-2009 12:39, tadamsmar wrote:

> On Dec 18, 10:34 pm, Arne Vajh�j<a...@vajhoej.dk> wrote:
>> On 18-12-2009 11:58, tadamsmar wrote:
>>> I want to interface to an instrument that uses MySql for TCPIP
>>> communications.
>>
>>> I am downloading MySql for OpenVMS.
>>
>>> I wonder if I will find a programming interface in the download, or
>>> merely a user interface.
>>
>>> I need a programming interface so I can get data from the instrument
>>> into an existing Fortran program.
>>
>>> (the instrument also has a serial interface, but we would prefer to
>>> use ethernet.)
>>
>> SYS$COMMON:[MYSQL051.INCLUDE]
>> SYS$COMMON:[MYSQL051.VMS.LIB]MYSQLCLIENT_MIXED.OLB
>> SYS$COMMON:[MYSQL051.VMS.LIB]MYSQLCLIENT_UPPER.OLB
>>
>> should include a MySQL client lib (MySQL C API).

> Do I need to run the server on VMS to use the client to access this


> other system, the instrument that I want to read?

I would not think so.

> Where is the documentation on the client interface?

It is online at:
http://dev.mysql.com/doc/refman/5.1/en/c.html

Arne

tadamsmar

unread,
Jan 11, 2010, 12:02:16 PM1/11/10
to
On Dec 18 2009, 10:34 pm, Arne Vajhøj <a...@vajhoej.dk> wrote:
> On 18-12-2009 11:58,tadamsmarwrote:
>

I am trying my first links, but I get lot of errors.

I am starting with a small C program that calls mysql_init.

For some reason, I have to link to SYS$COMMON:[MYSQL051.VMS.LIB]
MYSQLCLIENT_UPPER.OLB. I am not using upper case, but I can't
link to SYS$COMMON:[MYSQL051.VMS.LIB]MYSQLCLIENT_MIXED.OLB for some
reason.

Anyway, I get messages for a bunch of unresolved symbols in client. I
have included all available .OLB files in the link, but the symbols
remain usresolved.
I have located some of the symbols in other OLB files, but they are
OLB files
with MIXED in the name. There does not seem to be a full set of OLB
files with upper case symbols. But I don't even know why I need to
link to upper case
symbols, it makes no sense to me.

The messages don't seem to be indentifying real problems for the
resulting exe file.
The exe file seems to run fine, but of course I can't fully check it
out this with only a call to mysql_init to make sure things are really
going to work.

Does anyone know how to resolve this symbols in the link?

VAXman-

unread,
Jan 11, 2010, 1:33:24 PM1/11/10
to
In article <ff2e158d-fb30-4246...@a6g2000yqm.googlegroups.com>, tadamsmar <tada...@yahoo.com> writes:

Publish the list of symbols here. Access to the .MAP file would also help.
You did create one, didn't you?

--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG

http://www.quirkfactory.com/popart/asskey/eqn2.png

"Well my son, life is like a beanstalk, isn't it?"

Arne Vajhøj

unread,
Jan 11, 2010, 10:55:50 PM1/11/10
to
On 11-01-2010 12:02, tadamsmar wrote:

> On Dec 18 2009, 10:34 pm, Arne Vajh�j<a...@vajhoej.dk> wrote:
>> On 18-12-2009 11:58,tadamsmarwrote:
>>
>>> I want to interface to an instrument that uses MySql for TCPIP
>>> communications.
>>
>>> I am downloading MySql for OpenVMS.
>>
>>> I wonder if I will find a programming interface in the download, or
>>> merely a user interface.
>>
>>> I need a programming interface so I can get data from the instrument
>>> into an existing Fortran program.
>>
>>> (the instrument also has a serial interface, but we would prefer to
>>> use ethernet.)
>>
>> SYS$COMMON:[MYSQL051.INCLUDE]
>> SYS$COMMON:[MYSQL051.VMS.LIB]MYSQLCLIENT_MIXED.OLB
>> SYS$COMMON:[MYSQL051.VMS.LIB]MYSQLCLIENT_UPPER.OLB
>>
>> should include a MySQL client lib (MySQL C API).
>
> I am trying my first links, but I get lot of errors.
>
> I am starting with a small C program that calls mysql_init.
>
> For some reason, I have to link to SYS$COMMON:[MYSQL051.VMS.LIB]
> MYSQLCLIENT_UPPER.OLB. I am not using upper case, but I can't
> link to SYS$COMMON:[MYSQL051.VMS.LIB]MYSQLCLIENT_MIXED.OLB for some
> reason.
>
> Anyway, I get messages for a bunch of unresolved symbols in client. I
> have included all available .OLB files in the link, but the symbols
> remain usresolved.
> I have located some of the symbols in other OLB files, but they are
> OLB files
> with MIXED in the name. There does not seem to be a full set of OLB
> files with upper case symbols. But I don't even know why I need to
> link to upper case
> symbols, it makes no sense to me.
>
> The messages don't seem to be indentifying real problems for the
> resulting exe file.
> The exe file seems to run fine, but of course I can't fully check it
> out this with only a call to mysql_init to make sure things are really
> going to work.
>
> Does anyone know how to resolve this symbols in the link?

Try:

$ cc /include=sys$common:[mysql051.include]/names=as_is foobar
$ link foobar+ -
sys$common:[mysql051.vms.lib]mysqlclient_mixed/lib+ -
sys$common:[mysql051.vms.lib]libssl_mixed/lib+ -
sys$common:[mysql051.vms.lib]libcrypto_mixed/lib

Arne

tadamsmar

unread,
Jan 13, 2010, 9:09:32 AM1/13/10
to
On Jan 11, 10:55 pm, Arne Vajhøj <a...@vajhoej.dk> wrote:
> On 11-01-2010 12:02,tadamsmarwrote:
> Arne- Hide quoted text -
>
> - Show quoted text -

Thanks!

That cleared up the bulk of the link messages. Here are the ones that
I
still get:

%LINK-W-MULPSC, conflicting attributes for psect mysql_port
in module client file DSA0:[VMS$COMMON.MYSQL051.VMS.LIB]
MYSQLCLIENT_MIXE
D.OLB;1
%LINK-W-MULPSC, conflicting attributes for psect mysql_unix_port
in module client file DSA0:[VMS$COMMON.MYSQL051.VMS.LIB]
MYSQLCLIENT_MIXE
D.OLB;1
%LINK-W-MULPSC, conflicting attributes for psect sql_protocol_typelib
in module client file DSA0:[VMS$COMMON.MYSQL051.VMS.LIB]
MYSQLCLIENT_MIXE
D.OLB;1
%LINK-W-NUDFSYMS, 2 undefined symbols:
%LINK-I-UDFSYM, compress
%LINK-I-UDFSYM, uncompress
%LINK-W-USEUNDEF, undefined symbol compress referenced
in psect $LINK$ offset %X00000050
in module my_compress file DSA0:[VMS$COMMON.MYSQL051.VMS.LIB]
MYSQLCLIENT
_MIXED.OLB;1
%LINK-W-USEUNDEF, undefined symbol uncompress referenced
in psect $LINK$ offset %X000000B0
in module my_compress file DSA0:[VMS$COMMON.MYSQL051.VMS.LIB]
MYSQLCLIENT
_MIXED.OLB;1

Jan-Erik Soderholm

unread,
Jan 13, 2010, 9:34:09 AM1/13/10
to
tadamsmar wrote:

Note that you could get more responses on the "MySQL for OpenVMS"
forum here : http://www.pi-net.dyndns.org/piforum/index.php

Bob Koehler

unread,
Jan 13, 2010, 8:40:05 AM1/13/10
to
In article <4717c8d9-4c28-4996...@a15g2000yqm.googlegroups.com>, tadamsmar <tada...@yahoo.com> writes:

> %LINK-W-MULPSC, conflicting attributes for psect mysql_port
> in module client file DSA0:[VMS$COMMON.MYSQL051.VMS.LIB]
> MYSQLCLIENT_MIXE
> D.OLB;1
> %LINK-W-MULPSC, conflicting attributes for psect mysql_unix_port
> in module client file DSA0:[VMS$COMMON.MYSQL051.VMS.LIB]
> MYSQLCLIENT_MIXE
> D.OLB;1
> %LINK-W-MULPSC, conflicting attributes for psect sql_protocol_typelib
> in module client file DSA0:[VMS$COMMON.MYSQL051.VMS.LIB]
> MYSQLCLIENT_MIXE
> D.OLB;1

You need to find where the attributes are set for mysql_port
mysql_unix_port, and sql_protocol_typelib, and make them match.
If they are set in code that you can't change, you can force them
to match via a LINK options file.

> %LINK-W-NUDFSYMS, 2 undefined symbols:
> %LINK-I-UDFSYM, compress
> %LINK-I-UDFSYM, uncompress

These two symbols are not part of any library you used. They may
have been compiled to COMPRESS and UNCOMPRESS, or they may just be
missing.

You can libr/list/names to see if they are in any of the libraries
you used, and whether they were built with or without case
preservation.

tadamsmar

unread,
Jan 13, 2010, 11:54:06 AM1/13/10
to
On Jan 13, 8:40 am, koeh...@eisner.nospam.encompasserve.org (Bob
Koehler) wrote:

uncompress is not in any of the libraries.

from a google search of "mysql uncompress", it looks like I need the
zlib library to resolve that symbol.

Mike Rechtman

unread,
Jan 13, 2010, 12:32:59 PM1/13/10
to
From the MySQL installation guide: (I think a rather old version... 2005)
Software Requirements
1. JFP OPENSSL 0.9.7E
2. JFP ZLIB 1.2.2

--
Mike R.
Home: http://alpha.mike-r.com/
QOTD: http://alpha.mike-r.com/php/qotd.php
No Micro$oft products were used in the URLs above, or in preparing this message.
Recommended reading: http://www.catb.org/~esr/faqs/smart-questions.html#before

tadamsmar

unread,
Jan 15, 2010, 12:28:07 PM1/15/10
to
> _MIXED.OLB;1- Hide quoted text -

>
> - Show quoted text -

The psect conflicts were because I compiling with CC/EXTER=COMMON

0 new messages