READ.ME
MERANT DataDirect SequeLink ODBC Edition 4.51a,
OLE DB Edition 2.0, and Java Edition 2.0
October 2000
This READ.ME file provides specific information about this release.
***********************************************************************
For installation instructions for SEQUELINK ODBC EDITION:
- "SequeLink ODBC Edition Client Installation Guide"
- "SequeLink Server Installation Guide"
For installation instructions for SEQUELINK JAVA EDITION:
- "SequeLink Java Edition Client Installation Guide"
- "SequeLink Server Installation Guide"
For installation instructions for SEQUELINK OLE DB EDITION:
- "SequeLink OLE DB Edition Client Installation Guide"
- "SequeLink Server Installation Guide"
NOTE: For installation instructions for SEQUELINK SERVER FOR AS/400,
see section 3.10 in this READ.ME.
If you are installing from a CD, these books are provided as
printed documents in your package, as well as in PDF format on the CD.
If you are installing from the Web, these books are provided in PDF and
HTML formats on the Web. For more information about installing from
the Web, contact your MERANT sales representative.
***********************************************************************
This READ.ME file contains information about the following topics:
1. What's New
2. SequeLink Online Documentation
3. Installation Notes
4. Contacting DataDirect Answerline
5. SequeLink Network Notes
6. SequeLink Server Notes
7. SequeLink ODBC Edition Client Notes
8. SequeLink Java Edition Client Notes
9. SequeLink OLE DB Edition Client Notes
10. SequeLink ODBC Socket Notes
1. WHAT'S NEW
1.1 SequeLink Server for Progress on Windows NT and UNIX
--------------------------------------------------------
SequeLink Server now supports the following Progress databases: 7.3A,
7.3C, 7.3D, 7.3E, 8.0B, 8.1A, 8.2A, 8.2B, 8.2C, 8.3A, 8.3B, 8.3C, 9.0A,
9.0B, and 9.1A on Windows NT and UNIX.
1.2 SequeLink Server for OS/390
-------------------------------
SequeLink has been validated with Interlink 5.2 TCP/IP on OS/390.
Also, support for Interlink TCP/IP 4.5 has been discontinued. In
addition, TCP/IP (UDP) support has been discontinued. If you want
to upgrade from Interlink TCP/IP 4.5 to Interlink TCP/IP 5.2, you
must change your applications to use SequeLink's support for
TCP/IP instead of TCP/IP (UDP).
For more information about SequeLink Server for OS/390, refer to
the README member in the CNTL data set on your SequeLink
distribution tape.
1.3 SequeLink Server for Legacy Data Stores
-------------------------------------------
If you ordered the SequeLink Legacy Server package, the "SequeLink
Server for VSAM Installation and Administration Guide" is no longer
applicable. Instead, use the "Getting Started with the SequeLink Legacy
Server" book, which is a part of the SequeLink Legacy Server package,
for access to VSAM and other legacy data stores.
1.4 SequeLink Server for AS/400
-------------------------------
SequeLink Server for AS/400 has been validated with OS/400 V4R4 and
V4R5.
In addition, this release of SequeLink Server for AS/400 provides the
following bug fixes for the following problems:
* No results were returned when a SQLPrimaryKey or SQLStatistics
call was issued on a table that had a name longer than
10 characters.
* The system name was returned, instead of the column name, when a
SQLPrimaryKey call was performed on a column that had a name
longer than 10 characters.
* A SQLPrimaryKey call did not return primary keys that were
created using the AS/400 Data Definition Specification.
* A SQLStatistics call failed when more than 80 rows were returned
in the result set.
* A SQLStatistics call failed when executed against a corrupt table.
* On OS/400 V4R4, SQLColumns calls experienced problems because of a
change IBM made to the internal behavior of the QUSLFLD API.
* DB2 SQL errors were returned when translating outer join
clauses that contain the character ".".
1.5 SequeLink ODBC Edition 4.51a
--------------------------------
See http://www.merant.com/products/datadirect/odbc/SequeLink/
techdocs/matrix.asp for a complete list of the databases supported by
SequeLink Server and platforms supported by SequeLink ODBC Edition
Client.
1.6 SequeLink Java Edition 2.0
------------------------------
- Fully configurable and flexible security through Secure Socket Layer
(SSL) support for anonymous and X.509 certificate-based SSL cipher
suites, including DES and 3DES encryption and RC4 and RSA support.
For more information about cryptography and US export restrictions,
see section 8.1 in this READ.ME.
- Compliant with the latest JDBC 2.0 specification and Java 2 Platform.
- New Java-based installer.
- Scrollable cursors with BLOBs for Oracle7 and 8, and Informix 5, 7,
and 9.
- Batch updates to all SequeLink Server platforms.
- DBMS user name and password encryption.
- Password change mechanism for DB2 and Oracle on OS/390.
- Spy and JDBCTest updated to support JDBC 2.0.
2. SEQUELINK ONLINE DOCUMENTATION
You can view the SequeLink Online Documents using Acrobat Reader 3.0 or
higher. The Acrobat Reader software is provided on your CD-ROM or
you can download it from the Adobe Website, www.adobe.com.
NOTE: If you are installing the SequeLink Online Documents from a CD,
refer to the DataDirect CD-ROM Insert for installation instructions and
refer to the READ.ME file in the books subdirectory on the CD for more
information about Acrobat Reader. If you are installing the SequeLink
Online Documents from the Web, follow the installation instructions on
the Website.
3. INSTALLATION NOTES
3.1 Installing When You Already Have a SequeLink Server 4.5x Running
--------------------------------------------------------------------
SequeLink Server is the common server component of SequeLink ODBC
Edition, SequeLink OLE DB Edition, and SequeLink Java Edition. If you
are already running SequeLink Server 4.5x, you do not need to upgrade
your server to use the SequeLink client software provided in this
SequeLink release.
3.2 Upgrading SequeLink 4.0x/4.5x Services to 4.51a on Windows NT &
UNIX
-------------------------------------------------------------------
When you install SequeLink Server 4.51a, any existing SequeLink Server
4.0x or 4.5x installation is not overwritten. SequeLink Server 4.51a is
installed side-by-side with the existing version. You can continue to
use any SequeLink Server services that you have defined for SequeLink
Server 4.0x or 4.5x.
You can upgrade your SequeLink Server 4.0x or 4.5x services at any time
to SequeLink Server 4.51a services by using the SequeLink Server
Administrator tool's "upgrade service" command. Upgrading a service
ensures that the service uses the new SequeLink Server 4.51a
executables and allows you to use new features and any new
configuration settings. Also, it retains any attributes that you have
configured for your SequeLink Server service, such as TCP port, user
authentication level, Read Only, and SequeLink Shadow Data
Dictionaries. After upgrading a service, your client application will
automatically use the upgraded SequeLink Server 4.51a service.
During the installation of SequeLink Server 4.51a, the installation
program will create a service for SequeLink Server 4.51a. You must
specify an available TCP port (one that is not being used by another
service) for this new SequeLink Server 4.51a service.
You can use this new service to test and verify the SequeLink Server
4.51a version you installed. Note that you must specify the
correct TCP port in the SequeLink client connection parameters. For
information about how to specify the TCP port at the client, refer to
the "SequeLink Administrator's Guide". If, after upgrading your
existing services, you do not need this new service, you can delete it
using the SequeLink Server Administrator tool's "delete service"
command. For more information about using the SequeLink Server
Administrator tool and its commands, refer to the "SequeLink
Administrator's Guide".
3.3 Installing SequeLink Server on Windows NT
---------------------------------------------
IMPORTANT: If your system environment variable PATH is modified during
the installation of prerequisite software, you must reboot your Windows
NT machine to activate any changes. If you do not, the SequeLink Server
installer may generate a message, indicating that required DLLs are not
found.
SequeLink Server on Windows NT uses the content of the system PATH
environment variable to locate required DLLs. If this PATH contains
references to network machines using \\Machine\directory (UNC
notation), you will not be able to connect from a SequeLink client to
the server, and the following message will be returned to the server:
"The application failed to initialize properly. Click on OK
to terminate the application."
If this occurs, modify the system PATH and move the network reference
to the end of the PATH variable, reboot the Windows NT server, and try
again to connect to the SequeLink server.
3.4 Installing SequeLink on Solaris
-----------------------------------
When you install SequeLink ODBC Edition Client or SequeLink Server on
Solaris using unixmi.ksh, warnings may be generated when files are
extracted from the product tar file. You can ignore these warnings.
3.5 Installing SequeLink Server on HP-UX 10.01
----------------------------------------------
Because of a problem in the HP 10.01 kernel, all file names on the CD
appear in uppercase on HP-UX 10.01. Because of this, the Installer
(unixmi.ksh) cannot be used on HP-UX 10.01. To install SequeLink
Server on HP-UX 10.01, change your directory to SEQUELNK/HP/SERVER,
copy the file to your hard disk, untar the file, and invoke the
Installer using the appropriate command:
ksh install.sh SSPxxx.tar
3.6 Installing SequeLink Server for Oracle on AIX
-------------------------------------------------
SequeLink Server for Oracle7.1, 7.2, 7.3, and 8.0x are provided in the
slora.tar file as executables, each linked to their respective Oracle
libraries. If you re-link these executables using the -l parameter when
launching the SequeLink installer (for example, ksh install.sh -l),
your AIX machine must have the xlC AIX C compiler installed; otherwise,
the installation will fail.
3.7 Installing SequeLink Server for Informix Against Informix 7.3
-----------------------------------------------------------------
The SequeLink Server installer may identify an Informix 7.3
installation as Informix 7.2 when the installer checks your system for
software prerequisites. You can ignore this discrepancy. It does not
interfere with the actual installation.
3.8 Installing SequeLink Server for Oracle on Siemens SINIX
-----------------------------------------------------------
Oracle8.03 contains a bug that prevents a SequeLink client from
connecting to a default installation of SequeLink Server for Oracle8
on Siemens SINIX. The Oracle libraries do not search the library path
correctly to obtain access to the Oracle database. As a workaround, you
can copy all Oracle shared libraries to /usr/lib, because /usr/lib is
always searched. To do this, log on your UNIX server under the UNIX
oracle account and issue the following command:
cp $ORACLE_HOME/lib/*.so /usr/lib
3.9 Installing SequeLink Server for Sybase on Digital UNIX
----------------------------------------------------------
Because of a bug in one of the libraries of Sybase 11.5.0 on Digital
UNIX, SequeLink clients are unable to connect to a default SequeLink
Server installation against Sybase 11.5.0 on Digital UNIX, resulting in
the following error:
-12893 "The transport connection has been closed by the server
during the initial handshake of the SequeLink connection
establishment."
To workaround this problem, edit the SLSybase.sh file in the SequeLink
directory and insert the following two lines before the line starting
with exec:
_RLD_ARGS="-ignore_version libdnet_stub.so"
export_RLD_ARGS
3.10 Installing SequeLink Server for DB2 on AS/400
--------------------------------------------------
SequeLink Server 4.5 for DB2 on AS/400 has been fully certified on
OS/400 V4R4 and V4R5. SequeLink Server is now available for OS/400
V3R2, V3R7, V4R1, V4R2, V4R3, V4R4, and V4R5.
To install SequeLink Server for DB2 on AS/400:
1. IF INSTALLING FROM A CD: Mount the CD on a computer that has FTP
access to your SequeLink Server and change to the
sequelnk\as400\server directory on the CD.
IF INSTALLING FROM FILES DOWNLOADED FROM THE WEB: Download the
appropriate file. Download instructions are available on the
Web site.
You should see the following files:
SQINS405 (contains installation programs)
SQV3R2M0 (contains SequeLink Server objects for OS/400 V3R2)
SQV3R7M0 (contains SequeLink Server objects for OS/400 V3R7,
V4R1, V4R2, V4R3, V4R4, and V4R5)
3. On the AS/400, create two save files:
a. Log on as the user QSECOFR.
b. Issue the following command to create the first save file.
CRTSAVF QGPL/SQINS405
c. Issue one of the following commands:
For OS/400 V3R2: CRTSAVF QGPL/SQV3R2M0
For OS/400 V3R7, V4R1, V4R2, V4R3, V4R4, or V4R5:
CRTSAVF QGPL/SQV3R7M0
4. Send the files to the appropriate save files on the AS/400 using
binary FTP.
5. Restore the installation library using the following command:
RSTLIB SAVLIB(SQINS405) DEV(*SAVF)
SAVF(QGPL/SQINS405)
6. Start the installer using one of the following commands:
For OS/400 V3R2:
ADDLIBLE SQINS405
SQINSTALL FROM(*FILE) SAVF(QPGL/SQV3R2M0)
For OS/400 V3R7, V4R1, V4R2, V4R3, V4R4, or V4R5:
ADDLIBLE SQINS405
SQINSTALL FROM(*FILE) SAVF(QGPL/SQV3R7M0)
An installation screen appears.
7. Continue with the installation instructions in the "SequeLink Server
Installation Guide".
3.11 Installing SequeLink ODBC Edition Client on HP-UX
------------------------------------------------------
SequeLink ODBC Edition Client on HP-UX provides three different
versions. Depending on how your application is compiled, one of
the following versions must be used:
- cFront compiled application:
Use SequeLink ODBC Edition Client for HP 10.10 - cFront Enabled.
This version is supported on HP-UX 10.10 and 10.20.
- aCC A.01.12 compiled application:
Use SequeLink ODBC Edition Client for HP 10.20 - aCC Enabled.
This version is supported on HP-UX 10.20 and 11.
- aCC A.03.05 compiled application:
Use SequeLink ODBC Edition Client for HP 11 - aCC Enabled.
This version is supported on HP-UX 11.
NOTE: SequeLink ODBC Edition Client requires specific patches
for HP-UX. See sections 3.12, 3.13, and 3.14 for more information.
3.12 Installing SequeLink ODBC Edition Client on HP-UX 10.10 (cFront)
---------------------------------------------------------------------
For HP-UX 10.10 platforms, patches must be installed before you
install the cFront-enabled version of SequeLink ODBC Edition Client.
You must be running HP-UX 10.10.36 or higher (HP-UX 10.10 with a patch
revision level of 36 or higher).
These patches can be installed from the "HP-UX Recommended Patches
Extension Software" CD available from HP.
3.13 Installing SequeLink ODBC Edition Client on HP-UX 10.20 (aCC)
------------------------------------------------------------------
For HP-UX 10.20 platforms, HP-UX patch PHSS_15043 must be installed
before you install the aCC-enabled version of SequeLink ODBC Edition
Client.
Patch PHSS_15043 is available from HP's website (www.hp.com) or
at the FTP site: i3107ffs.exetrnal.hp.com.
3.14 Installing SequeLink ODBC Edition Client on HP-UX 11 (aCC)
---------------------------------------------------------------
For HP-UX 11 systems, HP-UX patch PHSS_14577 must be installed before
you install the aCC-enabled version of SequeLink ODBC Edition Client.
Patch PHSS_14577 is available from HP's website (www.hp.com) or
at the FTP site: i3107ffs.exetrnal.hp.com.
3.15 Installing SequeLink ODBC Edition Client on AIX
----------------------------------------------------
The default installation of SequeLink ODBC Edition Client only works
with applications built using AIX's reentrant compilers. Applications
built with the non-reentrant compilers, must replace the default ODBC
libraries with their corresponding version in the nothread directory.
To replace the default ODBC libraries, with the non-reentrant versions,
go to the SequeLink installation directory and execute the following
command:
cd nothread
cp -R * ..
NOTE: The nothread directory is not a complete ODBC installation. It
contains only the files required to replace their reentrant
counterparts.
3.16 Installing SequeLink OLE DB Edition Client on Windows 9x
-------------------------------------------------------------
SequeLink OLE DB Edition requires DCOM. DCOM is installed by default
with Windows NT; For Windows 9x, you must install DCOM. You can obtain
DCOM from Microsoft: http://www.microsoft.com/com/dcom.asp
3.17 Installing SequeLink OLE DB Edition 2.0 Client and Connect OLE DB
2.10 on the Same Machine
-----------------------------------------------------------------------
The Connect OLE DB relational data providers and the SequeLink OLE DB
Provider use the MERANT DataDirect OLE DB Administrator, formerly
called the INTERSOLV OLE DB Administrator, to create and configure data
sources. By default, Connect OLE DB 2.10 and SequeLink OLE DB Edition
2.0 create data sources into different directories.
To ensure that SequeLink OLE DB Provider data sources are saved
correctly when you install both providers on the same machine, you must
install the SequeLink OLE DB Provider BEFORE you install the Connect
OLE DB provider. After both are installed, remember that the data
sources will be stored in different directories
* Connect OLE data sources are in the install directory
(by default, \inoledb)
* SequeLink OLE DB Provider are on the system disk
Program Files\Common Files\DataDirect Shared\Admin
To view the data sources in the Administrator, select
Tools/Options/Change Current Directory and navigate to the appropriate
directory.
NOTE: Be sure to click OK; clicking Cancel will not write the correct
current directory information to the system information.
3.18 Installing SequeLink Java Edition Client
---------------------------------------------
Refer to the section 8, "SequeLink Java Edition Client Notes", for
information about installing SequeLink Java Edition Client.
4. CONTACTING DATADIRECT ANSWERLINE
Before calling DataDirect Answerline, please collect basic information
about your system to help us understand the environment in which you
are working and the exact steps we need to perform to reproduce the
problem. You can contact Answerline electronically, by FAX, or by
phone.
Our website at http://support.merant.com connects you to our online
support site. Our website also gives you access to DataDirect product
information, downloads, and online documentation.
5. SEQUELINK NETWORK NOTES
5.1 SequeLink for TCP/IP (UDP) Support
--------------------------------------
TCP/IP (UDP) support is a limited type of TCP/IP support that is
provided for backward compatibility to existing SequeLink Server for
DB2 on OS/390 installations. New installations and services should use
TCP/IP support.
5.2 Using Microsoft SNA Server
------------------------------
ON WINDOWS NT, and WINDOWS 95:
You may experience problems when a client application performs a large
number of connect/disconnect cycles. To prevent these problems, install
the service packs for Microsoft SNA Server Client, which are available
from the Microsoft FTP server, ftp.microsoft.com, in the directory:
bussys/winnt/sna-public.
SequeLink ODBC Edition Client for Microsoft SNA Server has been
verified with:
- Microsoft SNA Server Client 3.0 in combination with Microsoft SNA
Server Server 3.0
- Microsoft SNA Server Client 4.0 in combination with Microsoft SNA
Server Server 4.0
ON WINDOWS 3.1x:
After rebooting Windows 3.1x, your first connection attempt with the
Microsoft SNA Server server may not succeed, because the required
Microsoft SNA Server modules have not been loaded by the system. These
modules are loaded during this first connection request, so try to
connect again. All further connection attempts should succeed.
SequeLink ODBC Edition Client for Microsoft SNA Server has been
verified with Microsoft SNA Server Client 3.0 in combination with
Microsoft SNA Server Server 3.0.
5.3 Using IBM Personal Communications
-------------------------------------
On Windows NT and Windows 95, you must explicitly start your SNA node
before you can make a connection. This needs to be done only once after
you have booted your machine.
5.4 Network Support on Windows 98
---------------------------------
SequeLink ODBC Edition Client has been verified on Windows 98 with
TCP/IP support and with Microsoft SNA Server Client 4.0 with Microsoft
SNA Server Server 4.0.
Support for other APPC (CPIC) implementations will be verified when the
vendors of the SNA stacks officially support this platform. For more
information, contact MERANT Answerline.
6. SEQUELINK SERVER NOTES
6.1 DB2 for AS/400
------------------
- User class check during installation: To avoid problems during
installation, the Installer verifies the user class of the user running
the installation. If the user class is not *SECOFR or *SECADM, a
warning is generated and the installation ends. If this occurs, log on
with an appropriate user profile and restart the installation.
- Installation performance: On OS/400 V3R2, the restore operation
executed during the automatic installation may take a long time,
because OS/400 has trouble reading media created at a higher release
level. IBM has provided corrective PTFs for this problem. We recommend
that you install the latest CUM-pack.
- CHAR() FOR BIT DATA and VARCHAR() FOR BIT DATA: Support for binary
types has been added. When some scalar functions are applied to these
columns, DB2 for AS/400 incorrectly reports these as character columns.
- For more information about bug fixes that have been made in this
release, see section 1.3 of this READ.ME.
6.2 DB2 on OS/390
-----------------
Refer to the member README in the CNTL data set for additional
information.
6.3 INFORMIX
------------
When preparing the database during your SequeLink installation:
* Examine the Informix log files with your Informix database
administrator if the Prepare Database tool does not show that
progress is occurring. If these log files are full, the preparation
tools wait until space is freed in the database.
* ON WINDOWS NT: To prepare an Informix database for client access,
run the Prepare Informix tool. To run this tool, you first must
configure a default Informix server setup using the Informix tool
setnet32. If you receive the following error:
"-25560 Environment variable INFORMIXSERVER must be set."
check your default Informix server configuration using the Informix
tool setnet32.
6.4 OpenINGRES
--------------
- Using a pattern like "%table_name" for the szTableName parameter of
SQLTables will return an empty result set. Using "%table_name%"
returns the correct result set.
- Executing SQLForeignKeys may result in the following error:
"[INTERSOLV][ODBC SequeLink driver][OpenIngres][S1000]
Service - E_OP0002 optimizer ran out of memory before generating
execution plan."
If you receive this error, increase the size of the OpenINGRES
parameter opf_memory. For instructions, refer to your OpenINGRES
documentation.
6.5 Oracle8 and Stored Procedures
---------------------------------
A bug in Oracle8.0.4 and lower does not allow you to execute a stored
procedure in an Oracle package that is owned by an Oracle user
different than the user who is used to log on with SequeLink. For
example, suppose that you are logged on Oracle8 as the user 'DEMO' and
you execute the statement:
{call SCOTT.PACKAGENAME.PROCEDURENAME(?,?)}
where PACKAGENAME is the user's package and PROCEDURENAME is the name
of the stored procedure. Because the Oracle package is owned by 'SCOTT'
and not 'DEMO', SequeLink will not execute this procedure. This bug
has been fixed in Oracle8.05.
6.6 SQL Server
--------------
- With SequeLink 4.5 and higher, SequeLink Server for Microsoft SQL
Server supports fetching from multiple concurrent SQL statements
(unlike SequeLink Server 4.0 for Microsoft SQL Server). If you do not
want to use this functionality, set the SQL Server Session key
"MSSQL_MULTISTATEMENTS" to "FALSE".
- Because of a problem in the Microsoft SQL Server 3.60.xxxxx ODBC
driver, SequeLink, when used with this version of the Microsoft driver,
does not handle stored procedure result sets correctly when the result
set contains columns of the SQL_TIMESTAMP data type.
- SequeLink Server for Microsoft SQL Server works with Microsoft
Query 8.00 or higher only.
6.7 Sybase
----------
Default installations of Sybase SQL Server 11.0, 11.5, and 11.9.2
(Adaptive Server) provide "catalog stored procedures" for ODBC
applications. Since the release date of Sybase 11.0, 11.5, and 11.9.2,
Sybase has provided two patches to correct these "catalog stored
procedures". If you do not apply these patches to your Sybase
installation, your ODBC applications may not work correctly. You can
contact Sybase to obtain these patches or apply the patch made
available by MERANT on the DataDirect CD. Follow the instructions below
to apply the patch made available on the DataDirect CD:
- FOR UNIX USERS: Log on your UNIX machine as the user 'sybase'. From
the DataDirect CD, copy the sybodbcprocs.sql file from the etc
directory on the CD to your Sybase home directory. Then, execute the
command:
isql -Usa -isybodbcprocs.sql
NOTE: You will need the Sybase System Administrator (sa) password to
install this patch or ask your database administrator to install the
patch or patches. Also, if you use FTP to transfer this file from
another workstation to your UNIX machine, make sure that you transfer
it in ASCII mode.
- FOR WINDOWS NT USERS: Use Sybase 'SQL Advantage' to load the
sybodbcprocs.sql file. Then, connect to your Sybase database as the
Sybase System Administrator (sa) and execute the SQL.
NOTE: You will need the Sybase System Administrator (sa) password to
install this patch or ask your database administrator to install the
patch or patches.
6.8 SequeLink Server Administrator on UNIX
------------------------------------------
- When the host on which SequeLink Server is installed obtains its
services list from an NIS server, the SequeLink Server Administrator
creates a shell script that you can use to update the master services
database on the NIS server. When you run this shell script on some
UNIX versions, the following error is returned:
isl_root_1234.sh[12] : /etc/yp : not found
If you receive this error:
1. Edit the shell script and replace the line:
cd /etc/yp ; make services
with the line:
cd /var/yp ; make services
2. Then, re-execute the shell script.
- On Solaris, the truncatelog command returns the following error
message:
slsrvcfg[30]: kill:bad argument count
This message is returned when the SequeLink Server Administrator
sends a SIGHUP signal to the syslog daemon to force it to reopen
its output files. The sending of this signal fails and the syslog
daemon cannot write to the truncated log file. After issuing the
truncatelog command, refresh the syslog explicitly. For example:
kill -HUP syslogpid
where syslogpid is the process ID of the syslog daemon. You can
obtain this process ID from the file /etc/syslog.pid.
You can obtain a fix for this SequeLink Server Administrator problem
on Solaris from MERANT Answerline.
6.9 Using Stored Procedures on AS/400
-------------------------------------
* SequeLink supports SQL stored procedures (procedures based on SQL
source) and external stored procedures (procedures written with an
external program, such as C, CL, or RPG).
* SequeLink only supports defined stored procedures (procedures for
which a CREATE PROCEDURE SQL statement has been executed).
* SequeLink only supports IN, INOUT, and OUT parameters. Result sets
are not supported.
* SequeLink does not support using literals or default values for
parameters and will generate an error message when these conditions
are encountered.
* When accessing a stored procedure, SequeLink always qualifies the
stored procedure with the library name. If the client application
specifies a qualifier, this qualifier will be used. If the stored
procedure is not qualified, SequeLink will automatically use the
default library as the qualifier. The default library is the first
library in the Current Library or User Library list that does not
start with a 'Q'.
* SQLProcedures is supported, but only returns defined stored
procedures (procedures for which a CREATE PROCEDURE was executed).
* SQLProcedureColumns is supported, but only for returning defined
stored procedures (procedures for which a CREATE PROCEDURE was
executed). Also, SQLProcedureColumns does not support returning
result sets.
7. SEQUELINK ODBC EDITION CLIENT NOTES
7.1 SequeLink ODBC Driver Options
---------------------------------
The SequeLink ODBC Driver includes options that allow you to take full
advantage of the driver with ODBC-enabled applications requiring
nonstandard or extended behavior. To use these options, we recommend
that you create a separate data source for each application. Edit
ODBC.INI, and, under the section for the data source you created, add a
value WorkArounds=n. The value n is the cumulative value of all chosen
options added together.
Note that each of these options has potential side effects related to
its use. An option should only be used to address the specific problem
for which it was designed.
The ODBC 3.0 Driver, not supported on Windows 3.1, also supports a
second set of options. These options can be enabled using
WorkArounds2=n.
WorkArounds=1. If an ODBC driver reports to Access 2.0 that its
SQL_CURSOR_COMMIT_BEHAVIOR or SQL_CURSOR_ROLLBACK_BEHAVIOR is 0, Access
opens tables as read-only. If this option is on, the ODBC driver
returns 1, allowing Access to open tables as read-write.
WorkArounds=2. Some applications cannot handle database qualifiers. If
this option is on, the driver reports that qualifiers are not
supported.
WorkArounds=4. Visual Basic 4.0 sometimes requires two connections to a
database system. For database systems that support only one connection,
the second attempt fails. Turning this option on causes the driver to
detect this condition and have the two ODBC connections share a single
physical connection to the database system.
WorkArounds=8. If an ODBC driver cannot detect the number of rows
effected by an Insert, Update, or Delete statement, it may return -1 in
SQLRowCount. Some products cannot handle this. Turning this option on
causes the driver to return 1 instead.
WorkArounds=16. If an ODBC driver in SQLStatistics reports to Access
1.1 an INDEX_QUALIFIER that contains a period, Access raises a
"tablename is not a valid name" error. Turning this option on causes
the driver to return no INDEX_QUALIFIER, allowing Access to open the
table.
WorkArounds=32. Turning this option on allows users of flat-file
drivers to abort a long-running query by pressing the ESC key.
WorkArounds=64. This option results in a column name of C
where is the ordinal position in the result set. For
example, "SELECT col1, col2+col3 FROM table1" produces the column names
"col1" and C2. SQLColAttributes/SQL_COLUMN_NAME returns
for result columns that are expressions. Use this option for
applications that cannot handle column names.
WorkArounds=256. Forces SQLGetInfo/SQL_ACTIVE_CONNECTIONS to be
returned as 1.
WorkArounds=512. To prevent ROWID results, this option forces the
SQLSpecialColumns function to return a unique index as returned from
SQLStatistics.
WorkArounds=2048. This option results in SQLDriverConnect returning
Database='' instead of DB='' in the returned connection string.
WorkArounds=65536. This option strips trailing zeros from decimal
results, which prevents Microsoft Access from generating an error when
decimal columns containing trailing zeros are included in the unique
index.
WorkArounds=131072. This option turns all occurrences of the double
quote character ("") into the accent grave character (`). Some
applications always quote identifiers with double quotes. Double
quoting causes problems for data sources that do not return
SQLGetInfo/SQL_IDENTIFIER_QUOTE_CHAR = .
WorkArounds=524288. This option overrides the precision and scale
settings for SQL_DECIMAL parameters to precision 40 and scale 20.
WorkArounds=8388608. This option causes SQLGetInfo/SQL_DATABASE_NAME to
be returned as an empty string when
SQLGetInfo/SQL_MAX_QUALIFIER_NAME_LEN is 0. This option should be used
with Inprise/Borland tools, such as Delphi.
WorkArounds=536870912. This option allows SQLBindParameter to be called
after SQLExecute to change the precision of previously bound
parameters.
WorkArounds=1073741824. Microsoft Access assumes that ORDER BY columns
do not have to be in the SELECT list. This workaround addresses that
mistaken assumption for data sources such as Informix, OpenINGRES, and
DB2 on OS/390.
WorkArounds2=2. Some applications incorrectly specify the ColumnSize/
DecimalDigits when binding timestamp parameters. This workaround causes
the driver to ignore the ColumnSize/DecimalDigits specified by the
application and use the database defaults instead.
WorkArounds2=4. Microsoft Access uses the most recent native type
mapping, as returned by SQLGetTypeInfo, for a specific SQL type. This
workaround reverses the order in which types are returned, so that
Microsoft Access will use the most appropriate native type. This is a
recommended workaround if you are using Microsoft Access against an
Oracle8 or Informix 9 data source.
WorkArounds2=32. Microsoft Access does require that the characters
"DSN=" are returned by SQLDriverConnect in the connection string output
parameter.
7.2 Using Microsoft Access
--------------------------
- We recommend that users of Microsoft Access 2.0 and Visual Basic 4.0
add the line WorkArounds=25 (1+8+16) for each data source to be used
with Microsoft Access and Visual Basic.
- We recommend setting WorkArounds2=4 when using the SequeLink ODBC
Driver on Windows 9x and Windows NT against an Oracle8 or Informix 9
data source.
- When using Microsoft Access with OpenINGRES, the OpenINGRES optimizer
often runs out of memory. The OpenINGRES error message returned is:
"Service- E_OP0002 optimizer ran out of memory before generating
execution plan." If this occurs and you need read/write access to these
tables, switch the Session key/value pair ING_TidInStatistics to YES
using the SequeLink Server Administrator. Then, re-attach the remote
table in Microsoft Access. If you only need read access to these
tables, run Microsoft Access in read-only mode. For more information,
refer to the "SequeLink Administrator's Guide" (chapter "Using
SequeLink with your Database").
When using Microsoft Access with OpenINGRES, the error "Timeout
occurred on lock request" may be generated. If this occurs, change the
default lock behavior of OpenINGRES by setting ING_ReadLock to NOLOCK
using the SequeLink Server Administrator. For more information about
the key ING_ReadLock, refer to the "SequeLink Administrator's Guide"
(chapter "Using SequeLink with your Database").
- Microsoft Access does not support SQL_TIMESTAMP columns with a
fractional part of more than 3 digits. This can cause problems with
some types of data sources, for example, INFORMIX or DB2. To workaround
this Microsoft Access limitation, you can set the connection attribute
"FetchTimestampAsString" to "1". Refer to the "SequeLink ODBC Driver
Reference for Windows 9x, Windows NT, UNIX, and Macintosh" for more
information about specifying connection attributes in ODBC.INI or by
using SQLDriverConnect.
- SequeLink Server for OS/390 allows SequeLink ODBC and JDBC clients to
select from DB2 synonyms; however, a bug in Microsoft Access, caused by
DB2 not supporting schemas for synonyms, prevents Microsoft Access
users from linking to remote DB2 synonyms. A workaround is to use DB2
aliases instead of synonyms. Aliases provide a superset of the
functionality offered by synonyms and support schemas.
7.3 Using Delphi
----------------
Delphi always uses a period (.) as a qualifier separator. If the data
source specifies another separator (such as \'), Delphi will not use
it, resulting in SQL syntax errors. This can be an issue if you use the
SequeLink ODBC Socket with non-relational ODBC drivers, such as the
DataDirect Connect ODBC for Text driver.
INPRISE/BORLAND DELPHI 3.0 USERS: Delphi users connecting to SequeLink
Server for INFORMIX should set Workarounds=2 as explained in section
7.1 of this READ.ME. If you do not, SQL syntax errors will be returned
by INFORMIX.
7.4 Using RDO in Visual Basic 4.0 with Oracle
---------------------------------------------
To use parameterized SQL statements in RDO, a driver must support
SQLDescribeParam. You can enable this functionality in the SequeLink
ODBC Driver when connected to a SequeLink Server Oracle service. Set
the connection attribute, "EnableDescribeParam" to "1". For more
information about specifying connection attributes in ODBC.INI or using
SQLDriverConnect, refer to the "SequeLink ODBC Driver Reference for
Windows 9x, Windows NT, UNIX, and Macintosh".
NOTE: This implementation of SQLDescribeParam has the following
limitations:
1. It is supported on Windows 9x and Windows NT only.
2. This option should be enabled with RDO only.
3. It is supported with Oracle only; it is ignored when connecting to a
non-Oracle SequeLink Server.
4. The SequeLink ODBC Driver does not support SQLDescribeParam when
executing positioned updates.
5. SequeLink requires that Oracle DATE parameters are specified in the
following format: YYYY-MM-DD HH:MM:SS
To specify Oracle DATE parameters in a different format, you must
explicitly set Oracle's NLS_DATE_FORMAT. For example:
ALTER SESSION SET NLS_DATE_FORMAT = 'YYYY-MM-DD'
7.5 The FixCharTrim Connection Attribute
----------------------------------------
By default, and as specified in the ODBC specification, the SequeLink
ODBC Driver returns a fixed-width character date, such as the CHAR data
type, with trailing blanks. You can trim trailing blanks when data is
fetched from fixed-width character columns. Set the connection
attribute, "FixCharTrim" to "1" to trim trailing blanks. Refer to the
"SequeLink ODBC Driver Reference for Windows 3.1x" or the "SequeLink
ODBC Driver Reference for Windows 9x, Windows NT, UNIX, and Macintosh"
for more information about specifying connection attributes in ODBC.INI
or using SQLDriverConnect.
This setting only affects fixed-width character string SQL data types,
such as the CHAR data type; it has no effect on variable-length
character string SQL data types, such as VARCHAR.
7.6 Developing ODBC Applications on UNIX
----------------------------------------
All the ODBC Core Components (header files, etc.) needed for
development of ODBC applications are contained in the /include and /lib
directory of your SequeLink installation directory.
Please read the license.txt file in /include directory for the
licensing information for the ODBC Core Components. Contact your local
MERANT sales or Answerline representative if you have any questions.
7.7 SQLDriverConnect on UNIX
----------------------------
SequeLink ODBC Edition Client on UNIX does not support dialogs on UNIX.
SQLDriverConnect returns a "Driver not capable" error when prompting
is necessary.
Prompting is required in the following cases:
- SQL_DRIVER_PROMPT is specified.
- SQL_DRIVER_COMPLETE or SQL_DRIVER_COMPLETE_REQUIRED is specified and
a required key-value pair in the data source is unspecified.
7.8 SQL_C_BIGINT Support
------------------------
SequeLink ODBC Edition Client on HP-UX 10.10 (cFront-Enabled) and
Macintosh PPC do not support the ODBC C data type SQL_C_BIGINT.
Use of this C data type in ODBC applications will cause unpredictable
results.
7.9 Compiler Requirements on HP-UX 10.20 and 11
-----------------------------------------------
SequeLink ODBC Edition Client (aCC-Enabled) does require the following
versions of aCC when developing ODBC applications.
On HP 10.20, at least aCC version A.01.12 is required. Your current aCC
installation can be upgraded using patch PHSS_14263.
On HP 11, at least aCC version A.03.05 is required. Your current aCC
installation can be upgraded using patch PHSS_13391.
Both patch PHSS_14263 and PHSS_13391 are publicly available from HP's
Website (www.hp.com) or at the FTP site: i3107ffs.exetrnal.hp.com.
8. SEQUELINK JAVA EDITION CLIENT NOTES
8.1. Domestic and Export Versions of SequeLink Java Edition Client
------------------------------------------------------------------
Because US laws restrict the export of "Strong" cryptographic
technology, SequeLink Java Edition provides the following functional
versions:
DOMESTIC VERSION (For Customers in US and Canada)
- DES (56-bit)
- 3DES (168-bit)
- RC4 (128-bit) and RSA
EXPORT VERSION (For Customers in Countries Outside the US and Canada)
- DES (40-bit)
NOTE: If you are a customer outside the US and Canada and can be
categorized as one of the following classes of end users, another
version of SequeLink Java Edition is available with an intermediate
level of cryptographic function that includes DES (56-bit),
3DES (168-bit), and RSA:
a)US Subsidiaries - for the protection of internal business operations
b)Bank/Financial Institutions/Insurance Companies - to secure financial
communications or transactions
c)Health/Medical Companies - end-users, not pharmaceutical
manufacturers
d)On-Line Merchants - for the purchase or sales of goods and software,
including interactions necessary for ordering, payment, and delivery
For more information about this version of SequeLink Java Edition, call
your MERANT sales representative.
8.2 Installing SequeLink Java Edition Client on Windows NT
----------------------------------------------------------
Under certain circumstances (when you do not have administrator
privileges or when the installation directory contains a space, for
example) you may receive an error when the installation ends telling
you that the "installation failed". You can safely ignore this error
message if the installer reports on the last screen that 81 files are
installed into 18 directories. This problem is related to the software
product that MERANT licensed to develop the installer and has been
reported to the software manufacturer.
8.3 Installing SequeLink Java Edition Client on Macintosh
---------------------------------------------------------
The SequeLink Java Edition Client installer does not recognize the
colon character (:) as a directory separator and expects a forward
slash (/). Therefore, if you want to install SequeLink Java Edition
Client to the directory "Macintosh HD:slje", you would specify
"/Macintosh HD/slje".
8.4 Installing SequeLink Java Edition on UNIX
---------------------------------------------
When you install SequeLink Java Edition on UNIX, make sure that you
have your DISPLAY environment variable set correctly. If you cannot set
the DISPLAY variable or do not have a Windowing environment on UNIX,
refer to the section "Installing Without a GUI" in the "SequeLink Java
Edition Installation Guide".
8.5 Using JSafe in Netscape Communicator 4.5 (Domestic Version Only)
--------------------------------------------------------------------
When you use the JSafe implementation of the RSA or RC4 algorithms in
Netscape Communicator 4.5 you may receive a
java.lang.NoClassDefFoundError for the class
java.security.SecureRandom. This class is not supported by Netscape
Communicator 4.5.
Workarounds for this problem include:
- Using a cipher suite that does not require RSA or RC4.
- Using another implementation of these algorithms.
- Contacting RSA DSI for an implementation of these algorithms that
does not use this class.
- Using the Java Plug-In 1.2 with Netscape Navigator 4.5.
8.6 Using encrypt.bat and decrypt.bat with JDK 1.1x on Windows NT
-----------------------------------------------------------------
When using the encryption (encrypt.bat) and decryption (decrypt.bat)
tools with JDK 1.1.x, specify an additional "-p ." on the command line.
For example:
encrypt -p . mykey.der mykey_enc.der decrypt -p . mykey_enc.der
mykey.der
8.7 Tested Java Virtual Machines
--------------------------------
SequeLink Java Edition has been tested on a wide range of commercially
available Java Virtual Machines, including:
OPERATING SYSTEM JAVA VIRTUAL MACHINE
Windows NT/9x JDK 1.1.x
Solaris JDK 1.1.x
Windows NT/9x JDK 1.2 (Java 2 Platform)
Solaris JDK 1.2 (Java 2 Platform)
Windows NT/9x Jview
Windows NT/9x Microsoft Internet Explorer 4.x
Windows NT/9x Microsoft Internet Explorer 4.x
with Java Plug-in 1.2
Windows NT Microsoft Internet Explorer 5.0
Windows NT/9x Netscape Communicator 4.5
Windows NT/9x Netscape Communicator 4.5
with Java Plug-in 1.2
Solaris Netscape Communicator 4.5
Mac PPC MRJ 2.x
Window NT HotJava 1.1.5
Solaris HotJava 1.1.5
9. SEQUELINK OLE DB EDITION CLIENT NOTES
9.1 Using Linked Servers in SQL Server 7
----------------------------------------
- If you use Linked Servers in SQL Server 7 and receive the
following error when connecting to Oracle7/8:
Invalid schema or catalog specified for provider 'INTERSOLV
SequeLink OLE DB Provider'.
set the option ReturnEmptyCatalogAsNull. Using the 'Options' tab in the
data source setup dialog, set the Connect option,
ReturnEmptyCatalogAsNull=1. This option should only be set when
connecting to Oracle7/8.
- On Windows NT, a message is displayed when you make a simple query
while running the SequeLink OLE DB Provider from SQL Server 7's Query
Analyzer against a linked server. The "dllhost.exe application error"
message states that the application tried to write memory that could
not be written. If you click OK, the query processes correctly.
Workaround: On the linked server, configure the provider in-process
using the EnterPrise Manager Linked Server properties. To do
this, click the Options button; then, select the "Allow in Process"
check box. Click OK and exit the EnterPrise Manager Linked Server
properties window. To implement this change, restart SQL Server 7.
9.2 Using SequeLink OLE DB Edition 2.0 Client and Connect OLE DB 2.10
on the Same Machine
---------------------------------------------------------------------
By default, SequeLink OLE DB Edition 2.0 Client and Connect OLE DB 2.10
use different directories to create data sources. See section 3.17 of
this READ.ME for information about installing SequeLink OLE DB Edition
2.0 Client and Connect OLE DB 2.10 on the same machine.
NOTE: Installing as described in section 3.17 causes the MERANT
DataDirect OLE DB Administrator to overwrite the Intersolv OLE DB
Administrator. This does not affect the functionality of the
Administrator and you can use it exactly as you would the Intersolv
OLE DB Administrator.
10. SEQUELINK ODBC SOCKET NOTES
10.1 Installation
-----------------
The SequeLink ODBC Socket is an open SequeLink service that can load an
ODBC driver on the server to connect to a data store. If you install
the DataDirect Connect ODBC Drivers (or DataDirect ODBC Driver 3.10
Pack on Windows NT or DataDirect ODBC Driver 3.02 Pack on UNIX) and the
SequeLink ODBC Socket on the same server, SequeLink clients can access
all the data stores supported by DataDirect Connect ODBC Drivers.
To access a data store using the SequeLink ODBC Socket:
1. Check the prerequisites for the DataDirect Connect ODBC Drivers.
Refer to the "DataDirect Connect ODBC Installation Guide" and the
"DataDirect Connect ODBC Reference."
2. Install the DataDirect Connect ODBC Drivers.
3. Install the SequeLink ODBC Socket. For information about installing
the SequeLink ODBC Socket, refer to the "SequeLink Server
Installation Guide."
10.2 Supported Platforms
------------------------
The SequeLink ODBC Socket is available for the following server
operating systems:
- Solaris 2.5 or higher
- HP-UX 10.10 or higher
- AIX 4.1.4 or a higher version of 4.1
- Windows NT 3.51 and 4.0
If you are running another version of one of the listed operating
systems, contact MERANT Answerline.
On HP-UX, two versions of the SequeLink ODBC Socket are available. One
version is compiled with the HP cFront compiler and can be used to load
an ODBC driver compiled with the cFront compiler. The other version is
compiled with the HP aCC compiler and can be used to load an ODBC
driver compiled with the aCC compiler.
10.3 General Issues
-------------------
- When using the SequeLink ODBC Socket with a Microsoft Access
database, data truncation errors can occur with versions of
ODBCJT32.DLL prior to 3.50342800.
- When using the SequeLink ODBC Socket with a FoxPro database, the
SequeLink CAT incorrectly states that the Database field should contain
the Server FoxPro directory. Instead, you must specify the fully
qualified path to the FoxPro database container.
10.4 Using the Socket on Windows NT
-----------------------------------
Normally, you connect to Oracle8 using SequeLink Server for Oracle8.
Alternatively, you can connect to Oracle8 using the SequeLink ODBC
Socket and the DataDirect Connect ODBC Drivers product. To successfully
connect from a SequeLink client using this configuration, add the
following clause to the Settings field in the SequeLink CAT (on the
SequeLink client):
DSN=;SRVR=
where is a placeholder for the ODBC system data source
on the Windows NT server where the SequeLink ODBC Socket is installed.
The SequeLink ODBC Socket requires an ODBC system data source.
End of READ.ME