9
9
Current components which have been built on OpenVMS
11
ODBC.OLB Driver manager as an OpenVMS static object library
12
ODBCINST.OLB ODBC installer / setup static object library
13
ODBC.EXE Driver manager shareable image
14
ODBCINST.EXE ODBC installer / setup shareable image
15
ODBCPSQL.EXE Postgres 6.5 driver
16
ISQL.EXE Command line sql tool
11
LIBODBC.OLB Driver manager as an OpenVMS static object library
12
LIBODBCINST.OLB ODBC installer / setup static object library
13
LIBODBCPSQL.OLB Postgres 6.5 driver static object library
14
LIBODBC.EXE Driver manager shareable image
15
LIBODBCINST.EXE ODBC installer / setup shareable image
16
LIBODBCPSQL.EXE Postgres 6.5 driver shareable image
17
ISQL.EXE Command line SQL tool
18
DLTEST.EXE Program to test loading shared libraries
18
20
Additional components included to perform building on OpenVMS
23
25
[.VMS]ODBCINST_AXP.OPT - Linker options file for ODBC installer shared image
24
26
[.VMS]ODBC_AXP.OPT - Linker options file for Driver manager shared image
25
27
[.VMS]ODBC2_AXP.OPT - Linker options file for ODBC 2 drivers
28
[.VMS]ODBC_SETUP.COM - DCL script to set up logicals and commands
27
30
Building unixODBC on OpenVMS
28
31
============================
30
After unpacking the backup saveset change into the unixodbc directory and
31
perform the following functions.
33
After unpacking the archive, change into the unixodbc directory and perform
34
the following functions.
35
38
$ @vmsbuild compile
37
linking and installing shared objects
44
COPYING SHARED LIBRARIES TO THEIR INSTALLED LOCATION
46
Define the logical name ODBC_LIBDIR to point to wherever you would like the
47
libraries to reside and run the build procedure again with the "install" option
48
as in the following example:
50
$ define ODBC_LIBDIR DISK$DBSTUFF:[ODBCLIB] ! will be created if it doesn't exist
39
51
$ @vmsbuild install
41
To run isql map a symbol to the binary
45
$ ISQL:==$DKA0:[MYDIR.UNIXODBC.BIN]ISQL.EXE
47
then simply type isql to run.
53
If the ODBC_LIBDIR logical is not defined, it will be defined for you
54
and a [.odbclib] directory will be created under the top level of the
57
Note that the build procedure can be run in batch if you prefer. It is
58
also possible to specify ALL as the parameter and do the compile, link,
59
and install in one fell swoop. For example:
61
$ submit/noprint/param=all vmsbuild.com
63
Post-installation tasks
64
======================================
66
To use the installed software, you need to run the command procedure
67
ODBC_SETUP.COM, which will have been installed in the same directory as
68
the libraries. This procedure defines the ODBC_LIBDIR logical name and
69
additional logical names that are needed for the image activator to
70
locate the libraries. It also defines the ISQL command. Put a line
71
similar to the following (with your own disk and directory
72
specification) in your LOGIN.COM, or (to make the software available
73
system-wide) in SYS$MANAGER:SYLOGIN.COM:
75
$ @disk$dbstuff:[odbclib]odbc_setup
77
N.B. It may be tempting to simply dump the libraries into SYS$SHARE and
78
depend on the image activator's default behavior to locate the images.
79
That works, but it's the surest way to what is known on another popular
82
If you'll be programming with ODBC rather than just using ISQL, be sure
83
to hang on to the contents of the [.include] and [.doc] directories.
84
Look at the compiler flags and link commands in vmsbuild.com for
85
examples of what you need to do to build programs using the libraries.
87
For performance reasons it may be desireable to install the libraries as
88
known images (which has nothing to do with "install" in the sense of
89
copying software to its target location). See the documentation to the
90
INSTALL command or use the command procedure [.vms]install_image.com
91
provided with this kit. Installing the images with privileges is not
92
recommended unless there is a compelling reason (Hint: failure to set up
93
file permissions properly on your .ini files is not a compelling
49
96
Locations of ODBC.INI and ODBCINST.INI
50
97
======================================
52
99
After running the @VMSBUILD INSTALL command a blank odbc.ini and odbcinst.ini
53
will be created in SYS$SHARE. To override the default locations of the user
100
will be created in ODBC_LIBDIR. To override the default locations of the user
54
101
odbc.ini or the directory where the system odbc.ini and odbcinst.ini reside
55
102
define the following logicals.
57
$ def/log ODBCINI "DKA100:[MYDIR.ODBC]ODBC.INI"
58
$ def/log ODBCSYSINI "DKA100:[MYDIR.SYS]"
104
$ define/log ODBCINI "DKA100:[MYDIR.ODBC]ODBC.INI"
105
$ define/log ODBCSYSINI "DKA100:[MYDIR.SYS]"
60
107
Example Setup With Postgres 6.5
61
108
===============================
63
SYS$SHARE:ODBCINST.INI
110
ODBC_LIBDIR:ODBCINST.INI
66
113
Description = Postgres SQL Driver
73
120
Description = Test to Postgres
74
121
Driver = PostgreSQL
added
removed
README.VMS
