Progsup
Progsup
51
OLE DB Edition 2.0
Java Edition 2.0
DataDirect ®
®
SequeLink Server
Progress Supplement
No part of this publication, with the exception of the software product user
documentation contained on a CD-ROM, may be copied, photocopied,
reproduced, transmitted, transcribed, or reduced to any electronic medium or
machine-readable form without prior written consent of MERANT.
MERANT
701 East Middlefield Road
Mountain View, California 94043
3
Table of Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
What Is DataDirect SequeLink? . . . . . . . . . . . . . . . . . . . . . . . . 5
Using This Supplement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Other Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Conventions Used in This Supplement . . . . . . . . . . . . . . . . . . . 9
Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . 9
Mouse Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Keyboard Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Preface
Other Documentation
SequeLink ODBC Edition:
■ SequeLink ODBC Edition Client Installation Guide
■ SequeLink Server Installation Guide
■ SequeLink ODBC Driver Reference for Windows 3.1x
■ SequeLink ODBC Driver Reference for Windows 9x,
Windows NT, UNIX, and Macintosh
■ SequeLink Administrator’s Guide
■ SequeLink Error Codes and Messages Reference
Using the SequeLink ODBC Drivers SequeLink ODBC Driver Reference for Windows 3.1x
SequeLink ODBC Driver Reference for Windows 9x,
Windows NT, UNIX, and Macintosh
Typographical Conventions
This supplement uses the following typographical conventions:
Convention Explanation
italics Introduces new terms with which you may not be
familiar, and is used occasionally for emphasis.
bold Emphasizes important information. Also indicates
button, menu, and icon names on which you can
act. For example, click Next.
UPPERCASE Indicates the name of a file. For operating
environments that use case-sensitive filenames, the
correct capitalization is used in information specific
to those environments.
Also indicates keys or key combinations that you
can use. For example, press the ENTER key.
monospace Indicates syntax examples, values that you specify,
or results that you receive.
monospaced Indicates names that are placeholders for values
italics that you specify. For example, filename.
forward slash / Separates menus and their associated commands.
For example, Select File / Copy means that you
should select Copy from the File menu.
The slash also separates directory levels when
specifying locations under UNIX.
vertical rule | Indicates an “OR” separator used to delineate
items.
Convention Explanation
brackets [ ] Indicates optional items. For example, in the
following statement: SELECT [DISTINCT], DISTINCT
is an optional keyword.
Also indicates sections of the Windows Registry.
braces { } Indicates that you must select one item. For
example, {yes | no} means that you must specify
either yes or no.
ellipsis . . . Indicates that the immediately preceding item can
be repeated any number of times in succession. An
ellipsis following a closing bracket indicates that all
information in that unit can be repeated.
Mouse Conventions
This action… Means to…
Click Point to an object with the mouse pointer and
momentarily press the left mouse button.
Double-click Press the left mouse button twice.
Right-click Momentarily press the right mouse button.
Drag Press and hold the left mouse button while
dragging item(s) to another part of the screen.
SHIFT+Click Click an object to select it; then, press and hold
the SHIFT key. Click another object to select the
intervening series of objects.
CTRL+Click Press and hold the CTRL key; then, click a
selection. This lets you select or deselect any
combination of objects.
Keyboard Conventions
Select menu items by using the mouse or pressing ALT+ the key
letter of the menu name or item.
Internet
Telephone
Australia 1 800 335 664 or 8:30-5:30 p.m. Local Melbourne Time (LMT)
9816 9977 for
Melbourne Metro
Belgium 0800 724 61 9:00-6:30 p.m. CET
France 0800 91 56 07 9:00-6:30 p.m. CET
When you contact us, make sure that you can provide the
following information:
This chapter describes the tasks you should perform before you
install SequeLink Server for Progress. For additional information
about tasks performed prior to installation, refer to the
SequeLink Server Installation Guide.
Note: The READ.ME file is also available from the Web site.
For example:
proserve /users/data/demo
■ To start a Progress database server on Windows NT for a
database called Demo in the C:\PROGRESS directory, enter
the following command:
proserve C:\PROGRESS\DEMO
The ProControl NT Service Program can also be used to
start a database.
6 Click Next.
9 Enter your name, company, serial number and IPE key. The
serial number and key are on the Product Registration
Information card shipped with the product. If you are
installing an evaluation copy, leave the key field empty.
12 Verify that the settings are correct; then, click OK to start the
installation.
mkdir /tmp/sqlnk
3 Transfer the SequeLink Server file.
Note: On Solaris, using the -xvf argument with the tar command
may cause warnings to appear; use the -xof argument instead.
For example, type:
cd /tmp/sqlnk
5 Enter the full path for your Progress DLC directory. The
version of Progress and the presence of the proper executable
in the tar file are verified. If the executable cannot be found,
a warning is given that another version will be installed. A
correct version can be made by restarting the installer with
the Linking option.
8 Enter your name, company name, serial number, and key. The
serial number and key are printed on the Product
Registration Information card that is shipped with the
product. If you are installing an evaluation copy of SequeLink
Server for Progress, leave the Key field empty.
------------------------------------------------------------------------
You are installing the product:
You will need approx. 5500 kBytes free diskspace in your SequeLink home
directory (depending on your platform and configuration).
------------------------------------------------------------------------
1) Start installation with these settings
Extracting files...
Extracting file: /usr/sqlnk/slsrvcfg
Extracting file: /usr/sqlnk/slsrvcfg.msg
Extracting file: /usr/sqlnk/toolkit.sh
Extracting file: /usr/sqlnk/4_50_00/msg/lediag.msg
Extracting file: /usr/sqlnk/4_50_00/msg/rldiag.msg
Extracting file: /usr/sqlnk/4_50_00/msg/prodiag.msg
Extracting file: /usr/sqlnk/4_50_00/admin/dmprogr.sql
Extracting file: ./iperegister
Extracting file: ./ipemerge
Extracting file: ./ipemsg.msg
Copying file: rscshell to /usr/sqlnk/rscshell
Extracting file: /usr/sqlnk/4_50_00/bin/slpro_82B
Extracting file: /usr/sqlnk/4_50_00/bin/slpro_82C
------------------------------------------------------------------------
The software you are installing will now be registered.
If you are installing an evaluation copy, leave the IPE key blank when
asked for.
------------------------------------------------------------------------
Name :
-----------------
YourName
Company :
-----------------
YourCompanyName
Serial Number :
-----------------
YourSerialNr
IPE Key :
-----------------
YourIPEKey
-------------------------------------------
--------- Information entered -------------
-------------------------------------------
Name: YourName
Organization: YourCompanyName
Serial Number: YourSerialNr
IPE Key: YourIPEKey
-------------------------------------------
------------------------------------------------------------------------
Enter YES to accept the above agreement:
YES
The registration file has been updated.
Registration process was successful.
Configuring syslog...
Adding service...
------------------------------------------------------------------------
DataDirect SequeLink Server installer:
Installation successfully completed.
------------------------------------------------------------------------
mkdir /tmp/sqlnk
3 Transfer the SequeLink Server file.
Note: On Solaris, using the -xvf argument with the tar command
may cause warnings to appear; use the -xof argument instead.
For example, type:
cd /tmp/sqlnk
2 Issue the following command:
5 Enter the full path for your Progress DLC directory. The
version of Progress you are running is verified.
8 Enter your name, company name, serial number, and key. The
serial number and key are printed on the Product Registration
Information card that is shipped with the product. If you are
installing an evaluation copy of SequeLink Server for Progress,
leave the Key field empty.
------------------------------------------------------------------------
You are installing the product:
You will need approx. 5500 kBytes free diskspace in your SequeLink home
directory (depending on your platform and configuration).
------------------------------------------------------------------------
1) Start installation with these settings
2) Change SequeLink home directory
3) Change Progress DLC directory
4) Change Progress version
9) Abort installation
Extracting files...
Extracting file: /progress/sqlnk45/slsrvcfg
Extracting file: /progress/sqlnk45/slsrvcfg.msg
Extracting file: /progress/sqlnk45/toolkit.sh
Extracting file: /progress/sqlnk45/4_50_00/msg/lediag.msg
Extracting file: /progress/sqlnk45/4_50_00/msg/rldiag.msg
Extracting file: /progress/sqlnk45/4_50_00/msg/prodiag.msg
Extracting file: /progress/sqlnk45/4_50_00/admin/dmprogr.sql
Extracting file: ./iperegister
Extracting file: ./ipemerge
Extracting file: ./ipemsg.msg
Copying file: rscshell to /progress/sqlnk45/rscshell
Extracting file: /progress/sqlnk45/4_50_00/bin/sbld
Extracting file: /progress/sqlnk45/4_50_00/bin/libsetcp.a
Extracting file: /progress/sqlnk45/4_50_00/bin/libslpro.a
Linking services...
ld /lib/crt0.o -s -o slpro_73D /progress/sqlnk45/4_50_00/bin/libslpro.a
/progress/sqlnk45/4_50_00/bin/libsetcp.a /progress/sqlnk45/4_50_00/bin/
libslpro.a /progress/sqlnk45/4_50_00/bin/libsetcp.a -L$ /progress/
pro73D/dlc/probuild/4gl/bklk.o/progress/pro73D/dlc/probuild/4gl/bkset.o
/progress/pro73D/dlc/probuild/4gl/dblg.o /progress/pro73D/dlc/probuild/
4gl/drargs.o /progress/pro73D/dlc/probuild/4gl/drcon.o /progress/pro73D/
dlc/probuild/4gl/drdb.o /progress/pro73D/dlc/probuild/4gl/drdbctl.o /
progress/pro73D/dlc/probuild/4gl/drdbset.o /progress/pro73D/dlc/
probuild/4gl/drmsg.o /progress/pro73D/dlc/probuild/4gl/drmsgw.o /
progress/pro73D/dlc/probuild/4gl/drpfile.o /progress/pro73D/dlc/
probuild/4gl/drppath.o /progress/pro73D/dlc/probuild/4gl/drsetup.o /
progress/pro73D/dlc/probuild/4gl/drsig.o /progress/pro73D/dlc/probuild/
4gl/fd.o /progress/pro73D/dlc/probuild/4gl/fdlist.o /progress/pro73D/
dlc/probuild/4gl/fmeval.o /progress/pro73D/dlc/probuild/4gl/hl.o/
progress/pro73D/dlc/probuild/4gl/hlidynlx.o /progress/pro73D/dlc/
probuild/4gl/hlinocpp.o /progress/pro73D/dlc/probuild/4gl/hlprodsp.o /
progress/pro73D/dlc/probuild/4gl/n1noora.o /progress/pro73D/dlc/
probuild/4gl/n1norms.o /progress/pro73D/dlc/probuild/4gl/n1nosilk.o /
progress/pro73D/dlc/probuild/4gl/nca.o /progress/pro73D/dlc/probuild/
4gl/ncs.o /progress/pro73D/dlc/probuild/4gl/ncsbsd.o /progress/pro73D/
dlc/probuild/4gl/ncslist.o /progress/pro73D/dlc/probuild/4gl/nsutil.o /
progress/pro73D/dlc/probuild/4gl/profcomp.o /progress/pro73D/dlc/
probuild/4gl/profldls.o /progress/pro73D/dlc/probuild/4gl/rlset.o /
progress/pro73D/dlc/probuild/4gl/rntmpio.o /progress/pro73D/dlc/
probuild/4gl/rtfullp.o /progress/pro73D/dlc/probuild/4gl/sldb.o /
progress/pro73D/dlc/probuild/4gl/snlkup.o /progress/pro73D/dlc/probuild/
4gl/sqlsmlpi.o /progress/pro73D/dlc/probuild/4gl/sqlsmscv.o /progress/
pro73D/dlc/probuild/4gl/svtstlk.o /progress/pro73D/dlc/probuild/4gl/
tstset.o /progress/pro73D/dlc/probuild/4gl/hliclang.o /progress/pro73D/
dlc/probuild/4gl/dblp.o /progress/pro73D/dlc/probuild/4gl/dbmanb.o /
progress/pro73D/dlc/probuild/4gl/fmsrt.o /progress/pro73D/dlc/probuild/
4gl/bfx.o /progress/pro73D/dlc/probuild/4gl/n2fulhli.o /progress/pro73D/
dlc/probuild/4gl/ncsplain.o /progress/pro73D/dlc/probuild/4gl/hlidyn.o /
progress/pro73D/dlc/probuild/4gl/dbusr.o /progress/pro73D/dlc/probuild/
4gl/dblang.o /progress/pro73D/dlc/probuild/4gl/dblksch.o /progress/
pro73D/dlc/probuild/4gl/dbflushm.o /progress/pro73D/dlc/probuild/4gl/
n1nordb.o /progress/pro73D/dlc/probuild/4gl/n1nocis.o /progress/pro73D/
dlc/probuild/4gl/n1nonis.o /progress/pro73D/dlc/probuild/4gl/n1nowi.o /
progress/pro73D/dlc/probuild/4gl/n1udsf.o /progress/pro73D/dlc/probuild/
4gl/n1nosyb.o /progress/pro73D/dlc/probuild/4gl/n1nobti.o /progress/
pro73D/dlc/probuild/4gl/n1noserv.o /progress/pro73D/dlc/probuild/4gl/
ncspip.o /progress/pro73D/dlc/probuild/4gl/n1vv.o /progress/pro73D/dlc/
probuild/4gl/n1noas4.o /progress/pro73D/dlc/probuild/4gl/sysglb.o /
progress/pro73D/dlc/probuild/4gl/ncsbstrn.o /progress/pro73D/dlc/
probuild/4gl/drdbctrn.o /progress/pro73D/dlc/probuild/4gl/ncstrn.o /
progress/pro73D/dlc/probuild/4gl/nsutltrn.o /progress/pro73D/dlc/
probuild/4gl/upprodbb.o /progress/pro73D/dlc/probuild/4gl/hlsmpat.o /
progress/pro73D/dlc/probuild/4gl/n1nodde.o /progress/pro73D/dlc/
probuild/4gl/n1nodt.o /progress/pro73D/dlc/probuild/4gl/ccread.o /
progress/pro73D/dlc/probuild/4gl/ccxlate.o /progress/pro73D/dlc/
probuild/4gl/fmebase.o /progress/pro73D/dlc/probuild/4gl/n1nosyt.o /
progress/pro73D/dlc/probuild/4gl/n1noodbc.o /progress/pro73D/dlc/
probuild/4gl/n1noas4t.o /progress/pro73D/dlc/probuild/4gl/dbsys.o /
progress/pro73D/dlc/probuild/4gl/mtsys.o /progress/pro73D/dlc/probuild/
4gl/musys.o /progress/pro73D/dlc/probuild/4gl/prsys.o /progress/pro73D/
dlc/probuild/4gl/sfsys.o /progress/pro73D/dlc/probuild/4gl/ncasys.o /
progress/pro73D/dlc/probuild/4gl/qrsys.o /progress/pro73D/dlc/probuild/
4gl/runtime.o /progress/pro73D/dlc/probuild/4gl/dbmgr.o /progress/
pro73D/dlc/probuild/4gl/compiler.o /progress/pro73D/dlc/probuild/4gl/
hlilib.o /progress/pro73D/dlc/probuild/4gl/stlib.o /progress/pro73D/dlc/
probuild/4gl/ut.o -lm -lg -ls -lc -lc
Link of slpro_73D completed
------------------------------------------------------------------------
The software you are installing will now be registered.
If you are installing an evaluation copy, leave the IPE key blank
when asked for.
------------------------------------------------------------------------
Name :
-----------------
YourName
Company :
-----------------
YourCompanyName
Serial Number :
-----------------
YourSerialNr
IPE Key :
-----------------
YourIPEKey
-------------------------------------------
--------- Information entered -------------
-------------------------------------------
Name: YourName
Organization: YourCompanyName
Serial Number: YourSerialNr
IPE Key: YourIPEKey
-------------------------------------------
------------------------------------------------------------------------
Enter YES to accept the above agreement:
YES
The registration file has been updated.
Registration process was successful.
Configuring syslog...
Adding service...
Enter SequeLink service name ? [SLProgress] :
Enter TCP port number ? [4008] :
SequeLink Server Administrator for UNIX
Version 1.7
------------------------------------------------------------------------
DataDirect SequeLink Server installer:
Installation successfully completed.
------------------------------------------------------------------------
3 Administering SequeLink
Server for Progress
Support Description
Binary large object support None
Character large object support None
Cursor commit behavior Close
Cursor rollback behavior Close
Cursor types Read, read/write, no-hold
Maximum number of concurrent
open statements 30
Catalog support None
Stored procedure support None
Transaction isolation levels Read uncommitted, read
committed
Convert functions None
Date/Time functions CURDATE, DAYOFMONTH,
DAYOFWEEK, MONTH, YEAR
Numeric functions ABS, LOG, LOG10, RAND,
ROUND, SQRT
String functions ASCII, CHAR, CONCAT, LEFT,
LTRIM, LENGTH, LCASE, REPEAT,
REPLACE, RTRIM, SPACE,
SUBSTRING, UCASE
Support Description
System functions DBNAME, USERNAME
Outer join support Progress 7: no support
Progress 8 and higher: Support
provided in addition to native
Progress out join syntax
Note: Progress 8 and 9 SQL does
not allow users to combine
equi-joins and outer joins. The
Progress native syntax must be
used for mixing inner and outer
joins.
PRO_ReadOnly = NO
■ Select
■ Connect
■ Disconnect
PRO_NotNull = NO
PRO_ShowIndexes = YES
PRO_ShowViews = NO
PRO_ShowTables = ALL
If set to ALL, every table and view defined in the database are
returned when using the data dictionary call for returning tables.
If set to USER, only the tables and views the user can access are
returned when using the data dictionary call for returning tables.
PRO_ShowHiddenTables = YES
If set to YES, all tables (including hidden ones) are returned when
using the data dictionary call for returning tables.
PRO_ShowRECID = NO
PRO_DBExcludeList =
PRO_MultipleErrors = YES
PRO_OuterJoins = YES
PRO_DecimalFunction_Precision = 30
PRO_DecimalFunction_Scale = 10
PRO_Character_Length_Fix = 240
PRO_RowCount_Report1 = YES
PRO_ReturnUsername = YES
PRO_TransClose_Level = 0
PRO_TransClose_Direction = RollBack
■ NO: No locks are used when retrieving data. Rows that are
locked by other users are read, and data from uncommitted
transactions is visible.
The SequeLink Server adds For Read Only to the SQL select
statements.
PRO_RecordLock_Maximum = NO
PRO_DataBaseConnection =
When this setting is empty, the SequeLink client must specify the
database connection parameters. If this setting is not empty, it
must contain the Progress database connection parameters,
which will overrule any client database connection parameters.
PRO_ESQLSettings =
When this setting is empty, the SequeLink client must specify any
ESQL/C settings. If this setting is not empty, it should contain the
Progress ESQL/C parameters. These parameters overrule any
client ESQL/C settings.
PRO_UserListTable =
Data Types
Table 3-2 shows how Progress SQL data types map to ODBC data
types.
Using Views
Progress allows the creation of views in a database. SequeLink
Server for Progress supports the use of these views, but it requires
some special considerations.
■ The queries for listing tables and columns are more complex
and, in turn, slower if information about views must be
displayed.
Using Dates
Progress dates are used by SequeLink Server for Progress in a
number of ways, as described in the following sections.
For example, to select the records from table Emp where the hire
date is greater than 17 Dec 1980, use the following statement:
select *
from emp
where hiredate > 12\/17\/1980
select *
from emp
where hiredate > 12/17/1980
{d 'yyyy-mm-dd'}
For example, to select the records from table Emp where the hire
date is greater than 17 Dec 1980, use the following statement:
select *
from emp
where hiredate > {d '1980-12-17'}
select *
from emp
where hiredate > 12\/17\/1980
SQL Scripts
The file containing the SQL scripts for the SSDD creation is named
DMPROGR.SQL. It can be found in the /etc directory on your
distribution CD.
SSDD Location
The shadow dictionary is created in your default Progress
database.
Because tables are created in your database at the time you run
the SSDD, the following must be considered:
DataDictionaryOwner and
DataDictionaryQualifier
When using the SSDD with SequeLink Server for Progress, the
DataDictionaryOwner field in the SequeLink Server
Configuration Resource is used for the Progress logical database
name containing the SSDD. The DataDictionaryQualifier field is
not used and must be left blank.
The SQLColumns call returns the elements from the array column
as separate columns with the array index appended between
braces.
Host user name: This is used to specify the user’s host user name.
Note: This is used only if you have specified one database in the
Database field.
Note: This is used only if you have specified one database in the
Database field.